[Kernel-packages] [Bug 1914543] Re: Missing device id for Intel TGL-H ISH [8086:43fc] in intel-ish-hid driver
SRU: https://lists.ubuntu.com/archives/kernel-
team/2021-February/117147.html (U/G/F/OEM-5.10)
** Description changed:
+ [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/20210204083315.122952-1-vicamo.y...@canonical.com/
+
+ [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: HID v2.00 Device
[hid-ishtp 8087:0AC2] on
+ hid-generic 001F:8087:0AC2.0004: hidraw3: HID v2.00 Device
[hid-ishtp 8087:0AC2] on
+ hid-generic 001F:8087:0AC2.0005: hidraw4: 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- SERR-
+ 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- SERR-
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:
- USERPID ACCESS COMMAND
- /dev/snd/controlC0: u 1900 F pulseaudio
+ USERPID 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
+ # 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
+ 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.
--
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:
In Progress
Status in linux-oem-5.10 package in Ubuntu:
Invalid
Status in linux source package in Focal:
In Progress
Status in linux-oem-5.10 source package in Focal:
In Progress
Status in linux source package in Groovy:
In Progress
Status in linux-oem-5.10 source package in Groovy:
Invalid
Status in linux source package in Hirsute:
In Progr
[Kernel-packages] [Bug 1905742] Re: Add support for AMD Sienna Cichlid (RX6000)
** Changed in: linux-firmware (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1905742 Title: Add support for AMD Sienna Cichlid (RX6000) Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Focal: Confirmed Status in linux-firmware source package in Groovy: Confirmed Bug description: [Impact] RX6000 series gfx cards do not work on Ubuntu at the moment. They need new firmware recently pushed upstream. [Test case] Install the updates, see that the desktop session is running with the native driver. [Where things could go wrong] ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1905742/+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 1914543] Re: Missing device id for Intel TGL-H ISH [8086:43fc] in intel-ish-hid driver
[2.485650] ish-hid {33AECD58-B679-4E54-9BD9-A04D34F0C226}:
[hid-ish]: enum_devices_done OK, num_hid_devices=3
[2.497337] hid-generic 001F:8087:0AC2.0003: hidraw2: HID
v2.00 Device [hid-ishtp 8087:0AC2] on
[2.506945] hid-generic 001F:8087:0AC2.0004: hidraw3: HID
v2.00 Device [hid-ishtp 8087:0AC2] on
[2.512127] hid-generic 001F:8087:0AC2.0005: hidraw4: HID
v2.00 Device [hid-ishtp 8087:0AC2] on
$ ls /sys/bus/iio/devices/
iio:device0 iio:device1 trigger0 trigger1
One of them is an ambient light sensor, and it works only with this
patch applied.
--
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:
In Progress
Status in linux-oem-5.10 package in Ubuntu:
Invalid
Status in linux source package in Focal:
In Progress
Status in linux-oem-5.10 source package in Focal:
In Progress
Status in linux source package in Groovy:
In Progress
Status in linux-oem-5.10 source package in Groovy:
Invalid
Status in linux source package in Hirsute:
In Progress
Status in linux-oem-5.10 source package in Hirsute:
Invalid
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- SERR-
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:
USERPID 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 : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1875437] Re: Qualcomm Atheros QCA6174 [168c:003e] subsystem: Killer 1535 [1a56:1535] WIFI stops working and system breaks
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- 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/1875437 Title: Qualcomm Atheros QCA6174 [168c:003e] subsystem: Killer 1535 [1a56:1535] WIFI stops working and system breaks Status in linux package in Ubuntu: Expired Bug description: I have a dell XPS 15 9570 laptop. I have been using Ubuntu (18, 19 and 20) for the last two years. Everything work fine except for the wifi, which randomly stops working. Sometimes I can just turn off and on the wifi and it comes to work until next random crash. However, other times, when it happens, I cannot turn off wifi, it seems like the system breaks, I have to hard shutdown the laptop and after boot it works again. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-26-generic 5.4.0-26.30 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pedrolarben 1800 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Apr 27 18:19:56 2020 InstallationDate: Installed on 2020-04-25 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. XPS 15 9570 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-26-generic root=UUID=1a07689c-3362-41b2-b2e1-ae28e49f5384 ro quiet splash acpi_rev_override=1 acpi_osi=Linux nouveau.modeset=0 pcie_aspm=force drm.vblankoffdelay=1 scsi_mod.use_blk_mq=1 nouveau.runpm=0 mem_sleep_default=deep mitigations=off vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-26-generic N/A linux-backports-modules-5.4.0-26-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 0D0T05 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd12/25/2019:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0D0T05:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9570 dmi.product.sku: 087C dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875437/+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 1906983] Re: Touchpad not detected
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- 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/1906983 Title: Touchpad not detected Status in linux package in Ubuntu: Expired Bug description: Hey guys, I have a laptop Diginnos Note Critea DX4 (japanese brand) and after installing Ubuntu for the first time (after formating it of course), my touchpad is not detected at all. Here is attached the result of the cat /proc/bus/input/devices command. Thx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1906983/+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 1907018] Re: Dell G3 3590 Kernel Update Fails
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- 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/1907018 Title: Dell G3 3590 Kernel Update Fails Status in linux package in Ubuntu: Expired Bug description: After updating the Kernel to version 5.4.0-56-generic, the operating system did not boot correctly, entering emergency mode and asking to run the journalctl -xb command and asking for the systemctl reboot and systemctl default commands to be executed. Going back to the Kernel version 5.4.0-54-generic the problem does not happen, the fault messages are addressed to the Hard Disk NVME m2 that I have on this hardware. Dell G3 3590 NVME M2 Samsung EVO 970 500GB Running the command: journalctl -xb the main error messages are. FAT-fs (nvme0n1p1): IO charset iso8859-1 not found Failed to find module lp, ppdev, parpot_pc, videodev, v412loopback_dc, v412loopback and coretemp EFI /boot/ efi partition mount failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1907018/+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 1914685] Re: Please enable CONFIG_UBSAN_BOUNDS
This is a CONFIG request, do no apport collection required. :) ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Also affects: linux (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Hirsute) Importance: Undecided Status: Confirmed ** Changed in: linux (Ubuntu Groovy) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1914685 Title: Please enable CONFIG_UBSAN_BOUNDS Status in linux package in Ubuntu: Confirmed Status in linux source package in Groovy: Confirmed Status in linux source package in Hirsute: Confirmed Bug description: Enabling CONFIG_UBSAN_BOUNDS is fast and provides good coverage for out-of-bounds array indexing (i.e. it catchings the things that CONFIG_FORTIFY doesn't). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1914685/+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 1914221] Re: dev test in ubuntu_stress_smoke_test hang with G-5.8 lowlatency
Remove the blocker tag as it's not a regression. ** Tags removed: kqa-blocker -- 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/1914221 Title: dev test in ubuntu_stress_smoke_test hang with G-5.8 lowlatency Status in Stress-ng: New Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Bug description: Issue found on Groovy 5.8.0-42.47 lowlatency kernel with node "spitfire" on Intel cloud. Reproduce rate: 2/2 The ubuntu_stress_smoke_test hang with the dev test on it: dentry STARTING dentry RETURNED 0 dentry PASSED dev STARTING Timer expired (2100 sec.), nuking pid 15918 ERROR ubuntu_stress_smoke_test.stress-smoke-test ubuntu_stress_smoke_test.stress-smoke-test timestamp=1612262460 localtime=Feb 02 10:41:00 Test timeout expired, rc=15 However, this issue didn't happen on this node with Groovy 5.8 generic kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/stress-ng/+bug/1914221/+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 1894454] Re: [nvidia] Screen freeze
Daniel, Please open your own bug by running: ubuntu-bug gnome-shell so we can investigate your issue. ** Also affects: nvidia-graphics-drivers-440 (Ubuntu) Importance: Undecided Status: New ** Changed in: nvidia-graphics-drivers-440 (Ubuntu) Status: New => Confirmed ** Summary changed: - [nvidia] Screen freeze + [nvidia] Screen freeze (GPU MMU faults reported by the kernel driver) ** Summary changed: - [nvidia] Screen freeze (GPU MMU faults reported by the kernel driver) + [nvidia] Screen freeze (GPU MMU faults reported by the kernel driver) on Quadro K620 -- 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/1894454 Title: [nvidia] Screen freeze (GPU MMU faults reported by the kernel driver) on Quadro K620 Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-450 package in Ubuntu: Confirmed Bug description: Ubuntu 20.04 freezes randomly ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55 Uname: Linux 5.4.0-45-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Bir dizin: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Bir dizin: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Bir dizin: '/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 450.66 Wed Aug 12 19:42:48 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 BootLog: Error: [Errno 13] Erişim engellendi: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Sep 7 01:22:46 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 450.66, 5.4.0-45-generic, x86_64: installed virtualbox, 6.1.10, 5.4.0-42-generic, x86_64: installed virtualbox, 6.1.10, 5.4.0-45-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a day GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Since a couple weeks or more GraphicsCard: NVIDIA Corporation GM107GL [Quadro K620] [10de:13bb] (rev a2) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation GM107GL [Quadro K620] [10de:1098] InstallationDate: Installed on 2020-04-26 (133 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. Precision Tower 3620 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=tr_TR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-generic root=UUID=5abcce6c-0eb6-4ef4-bf1b-0a62c2924a2d ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/25/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.15.0 dmi.board.name: 0MWYPT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.15.0:bd03/25/2020:svnDellInc.:pnPrecisionTower3620:pvr:rvnDellInc.:rn0MWYPT:rvrA00:cvnDellInc.:ct3:cvr: dmi.product.family: Precision dmi.product.name: Precision Tower 3620 dmi.product.sku: 06B7 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.3 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/ubuntu/+source/nvidia-graphics-drivers-440/+bug/1894454/+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 1912033] Re: Thinkpad - add palm sensor support needed for WWAN
** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- 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/1912033 Title: Thinkpad - add palm sensor support needed for WWAN Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.10 source package in Focal: Fix Committed Bug description: [Impact] Add new palm sensor supports to Lenovo Thinkpad systems [Fix] thinkpad_acpi is updated to check palm sensor presence and its events [Test] Tested on Thinkpad systems [Where problems could occur] Low risks. Only thinkpad systems are affected. Also thinkpad systems without palm sensor and without TP_HKEY_EV_PALM_DETECTED & TP_HKEY_EV_PALM_UNDETECTED events won't be affected either. There can an issue as discussed in commit log of "thinkpad_acpi: Add palm sensor support" Note: On some platforms, because of an issue in the HW implementation, the palm sensor presence may be incorrectly advertised as always enabled even if a palm sensor is not present. The palm sensor is intended for WWAN transmission power control and should be available and correct on all WWAN enabled systems. It is not recommended to use this interface for other use cases. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1912033/+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 1914668] Re: Exploitable vulnerabilities in AF_VSOCK implementation
** Changed in: linux (Ubuntu Groovy)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu Hirsute)
Status: In Progress => Fix Committed
** Also affects: linux-riscv (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-riscv (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1914668
Title:
Exploitable vulnerabilities in AF_VSOCK implementation
Status in linux package in Ubuntu:
Fix Committed
Status in linux-hwe-5.8 package in Ubuntu:
New
Status in linux-riscv package in Ubuntu:
Fix Committed
Status in linux-hwe-5.8 source package in Focal:
In Progress
Status in linux source package in Groovy:
Fix Committed
Status in linux source package in Hirsute:
Fix Committed
Bug description:
https://www.openwall.com/lists/oss-security/2021/02/04/5
The following mainline patch is required for all kernels >= v5.8:
{focal hwe-5.8, groovy, hirsute}:
[linux] c518adafa39f vsock: fix the race conditions in multi-transport
support
or [linux-5.10-y] 55d900415b81 vsock: fix the race conditions in
multi-transport support
[Impact]
* Patches an exploitable vulnerability.
[Test Case]
* See disclosure article.
[Regression Potential]
* Low: straightforward race condition fix; upstream cherry-pick.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1914668/+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 1914685] 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 1914685 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1914685 Title: Please enable CONFIG_UBSAN_BOUNDS Status in linux package in Ubuntu: Incomplete Bug description: Enabling CONFIG_UBSAN_BOUNDS is fast and provides good coverage for out-of-bounds array indexing (i.e. it catchings the things that CONFIG_FORTIFY doesn't). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1914685/+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 1914685] [NEW] Please enable CONFIG_UBSAN_BOUNDS
Public bug reported: Enabling CONFIG_UBSAN_BOUNDS is fast and provides good coverage for out- of-bounds array indexing (i.e. it catchings the things that CONFIG_FORTIFY doesn't). ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1914685 Title: Please enable CONFIG_UBSAN_BOUNDS Status in linux package in Ubuntu: New Bug description: Enabling CONFIG_UBSAN_BOUNDS is fast and provides good coverage for out-of-bounds array indexing (i.e. it catchings the things that CONFIG_FORTIFY doesn't). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1914685/+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 1914668] Re: Exploitable vulnerabilities in AF_VSOCK implementation
https://lists.ubuntu.com/archives/kernel-team/2021-February/117143.html
** Changed in: linux (Ubuntu Groovy)
Status: Incomplete => In Progress
** Changed in: linux (Ubuntu Hirsute)
Status: Incomplete => In Progress
** Changed in: linux (Ubuntu Groovy)
Importance: Undecided => High
** Changed in: linux (Ubuntu Hirsute)
Importance: Undecided => High
** Also affects: linux-hwe-5.8 (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: linux-hwe-5.8 (Ubuntu Groovy)
** No longer affects: linux-hwe-5.8 (Ubuntu Hirsute)
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: linux-hwe-5.8 (Ubuntu Focal)
Importance: Undecided
Status: New
** No longer affects: linux (Ubuntu Focal)
** Changed in: linux-hwe-5.8 (Ubuntu Focal)
Status: New => In Progress
** Changed in: linux-hwe-5.8 (Ubuntu Focal)
Importance: Undecided => High
** Changed in: linux (Ubuntu Groovy)
Assignee: (unassigned) => Kamal Mostafa (kamalmostafa)
** Changed in: linux (Ubuntu Hirsute)
Assignee: (unassigned) => Kamal Mostafa (kamalmostafa)
** Changed in: linux-hwe-5.8 (Ubuntu Focal)
Assignee: (unassigned) => Kamal Mostafa (kamalmostafa)
--
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/1914668
Title:
Exploitable vulnerabilities in AF_VSOCK implementation
Status in linux package in Ubuntu:
In Progress
Status in linux-hwe-5.8 package in Ubuntu:
New
Status in linux-hwe-5.8 source package in Focal:
In Progress
Status in linux source package in Groovy:
In Progress
Status in linux source package in Hirsute:
In Progress
Bug description:
https://www.openwall.com/lists/oss-security/2021/02/04/5
The following mainline patch is required for all kernels >= v5.8:
{focal hwe-5.8, groovy, hirsute}:
[linux] c518adafa39f vsock: fix the race conditions in multi-transport
support
or [linux-5.10-y] 55d900415b81 vsock: fix the race conditions in
multi-transport support
[Impact]
* Patches an exploitable vulnerability.
[Test Case]
* See disclosure article.
[Regression Potential]
* Low: straightforward race condition fix; upstream cherry-pick.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1914668/+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 1914668] Re: Exploitable vulnerabilities in AF_VSOCK implementation
** Description changed:
https://www.openwall.com/lists/oss-security/2021/02/04/5
The following mainline patch is required for >= groovy:
[linux] c518adafa39f vsock: fix the race conditions in multi-transport support
[linux-5.10-y] 55d900415b81 vsock: fix the race conditions in multi-transport
support
+
+
+ [Impact]
+
+ * Patches an exploitable vulnerability.
+
+ [Test Case]
+
+ * See disclosure article.
+
+ [Regression Potential]
+
+ * Low: straightforward race condition fix; upstream cherry-pick.
** Description changed:
https://www.openwall.com/lists/oss-security/2021/02/04/5
The following mainline patch is required for >= groovy:
[linux] c518adafa39f vsock: fix the race conditions in multi-transport support
[linux-5.10-y] 55d900415b81 vsock: fix the race conditions in multi-transport
support
-
[Impact]
- * Patches an exploitable vulnerability.
+ * Patches an exploitable vulnerability.
[Test Case]
- * See disclosure article.
+ * See disclosure article.
[Regression Potential]
- * Low: straightforward race condition fix; upstream cherry-pick.
+ * Low: straightforward race condition fix; upstream cherry-pick.
** Description changed:
https://www.openwall.com/lists/oss-security/2021/02/04/5
- The following mainline patch is required for >= groovy:
+ The following mainline patch is required for all kernels >= v5.8: {focal
+ hwe-5.8, groovy, hirsute}:
- [linux] c518adafa39f vsock: fix the race conditions in multi-transport support
- [linux-5.10-y] 55d900415b81 vsock: fix the race conditions in multi-transport
support
+ [linux] c518adafa39f vsock: fix the race conditions in multi-transport
+ support
+
+ or [linux-5.10-y] 55d900415b81 vsock: fix the race conditions in multi-
+ transport support
+
[Impact]
* Patches an exploitable vulnerability.
[Test Case]
* See disclosure article.
[Regression Potential]
* Low: straightforward race condition fix; upstream cherry-pick.
--
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/1914668
Title:
Exploitable vulnerabilities in AF_VSOCK implementation
Status in linux package in Ubuntu:
Incomplete
Status in linux source package in Groovy:
Incomplete
Status in linux source package in Hirsute:
Incomplete
Bug description:
https://www.openwall.com/lists/oss-security/2021/02/04/5
The following mainline patch is required for all kernels >= v5.8:
{focal hwe-5.8, groovy, hirsute}:
[linux] c518adafa39f vsock: fix the race conditions in multi-transport
support
or [linux-5.10-y] 55d900415b81 vsock: fix the race conditions in
multi-transport support
[Impact]
* Patches an exploitable vulnerability.
[Test Case]
* See disclosure article.
[Regression Potential]
* Low: straightforward race condition fix; upstream cherry-pick.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1914668/+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 1914668] 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 1914668
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
** Changed in: linux (Ubuntu Groovy)
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/1914668
Title:
Exploitable vulnerabilities in AF_VSOCK implementation
Status in linux package in Ubuntu:
Incomplete
Status in linux source package in Groovy:
Incomplete
Status in linux source package in Hirsute:
Incomplete
Bug description:
https://www.openwall.com/lists/oss-security/2021/02/04/5
The following mainline patch is required for all kernels >= v5.8:
{focal hwe-5.8, groovy, hirsute}:
[linux] c518adafa39f vsock: fix the race conditions in multi-transport
support
or [linux-5.10-y] 55d900415b81 vsock: fix the race conditions in
multi-transport support
[Impact]
* Patches an exploitable vulnerability.
[Test Case]
* See disclosure article.
[Regression Potential]
* Low: straightforward race condition fix; upstream cherry-pick.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1914668/+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 1914668] [NEW] Exploitable vulnerabilities in AF_VSOCK implementation
Public bug reported: https://www.openwall.com/lists/oss-security/2021/02/04/5 The following mainline patch is required for >= groovy: [linux] c518adafa39f vsock: fix the race conditions in multi-transport support [linux-5.10-y] 55d900415b81 vsock: fix the race conditions in multi-transport support ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Affects: linux (Ubuntu Groovy) Importance: Undecided Status: Incomplete ** Affects: linux (Ubuntu Hirsute) Importance: Undecided Status: Incomplete ** Also affects: linux (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Groovy) 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/1914668 Title: Exploitable vulnerabilities in AF_VSOCK implementation Status in linux package in Ubuntu: Incomplete Status in linux source package in Groovy: Incomplete Status in linux source package in Hirsute: Incomplete Bug description: https://www.openwall.com/lists/oss-security/2021/02/04/5 The following mainline patch is required for >= groovy: [linux] c518adafa39f vsock: fix the race conditions in multi-transport support [linux-5.10-y] 55d900415b81 vsock: fix the race conditions in multi-transport support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1914668/+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 1914656] 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 1914656 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1914656 Title: Microphone mute key is not functional on Dell systems Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Bug description: [Steps to reproduce] 1 Press microphone mute key 2.Check microphone mute should be enabled & disabled is sound settings [Expected result] Microphone mute should be enabled & disabled [Actual result] Microphone mute never changes [Analysis] A new driver is required, ex. "dell-privacy: Add support for Dell hardware privacy" (still WIP?) To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1914656/+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 1914656] [NEW] Microphone mute key is not functional on Dell systems
Public bug reported: [Steps to reproduce] 1 Press microphone mute key 2.Check microphone mute should be enabled & disabled is sound settings [Expected result] Microphone mute should be enabled & disabled [Actual result] Microphone mute never changes [Analysis] A new driver is required, ex. "dell-privacy: Add support for Dell hardware privacy" (still WIP?) ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: oem-priority originate-from-1909076 somerville ** Tags added: oem-priority originate-from-1909076 somerville -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1914656 Title: Microphone mute key is not functional on Dell systems Status in HWE Next: New Status in linux package in Ubuntu: New Bug description: [Steps to reproduce] 1 Press microphone mute key 2.Check microphone mute should be enabled & disabled is sound settings [Expected result] Microphone mute should be enabled & disabled [Actual result] Microphone mute never changes [Analysis] A new driver is required, ex. "dell-privacy: Add support for Dell hardware privacy" (still WIP?) To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1914656/+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 1910813] Re: Error when install libnvidia-compute-390_390.141-0ubuntu0.20.10.1_amd64.deb
** Changed in: nvidia-graphics-drivers-390 (Ubuntu) Status: New => Confirmed -- 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/1910813 Title: Error when install libnvidia-compute- 390_390.141-0ubuntu0.20.10.1_amd64.deb Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Bug description: Preparing to unpack ... / libnvidia-compute-390_390.141-0ubuntu0.20.10.1_amd64.deb ... Unpacking libnvidia-compute-390: amd64 (390.141-0ubuntu0.20.10.1) ... dpkg: error processing archive /var/cache/apt/archives/libnvidia-compute-390_390.141-0ubuntu0.20.10.1_amd64.deb (--unpack): trying to overwrite the generic "/etc/OpenCL/vendors/nvidia.icd" which is different from other instances of the libnvidia-compute-390: amd64 package dpkg-deb: error: insert subprocess was interrupted by signal (Broken pipe) Errors occurred while processing the following packets: /var/cache/apt/archives/libnvidia-compute-390_390.141-0ubuntu0.20.10.1_amd64.deb E: subprocess / usr / bin / dpkg returned error code (1) ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: libnvidia-compute-390 (not installed) ProcVersionSignature: Ubuntu 5.8.0-36.40-generic 5.8.18 Uname: Linux 5.8.0-36-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Jan 8 23:10:43 2021 InstallationDate: Installed on 2020-11-01 (68 days ago) InstallationMedia: Ubuntu-MATE 20.10 "Groovy Gorilla" - Release amd64 (20201022) ProcEnviron: LANGUAGE=ru TERM=xterm-256color PATH=(custom, no user) LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: nvidia-graphics-drivers-390 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1910813/+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 1903790] Re: SSD and Bluetooth conflict (Bluetooth AR3011 doesn't work)
I tested the latest kernel 5.11rc6. The error persisted. Nothing has changed. [ 10.303394] Bluetooth: Can't change to loading configuration err [ 10.303548] ath3k: probe of 2-1.3:1.0 failed with error -110 [ 10.303586] usbcore: registered new interface driver ath3k ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1903790 Title: SSD and Bluetooth conflict (Bluetooth AR3011 doesn't work) Status in linux package in Ubuntu: Confirmed Bug description: Bluetooth stops working when I plug in the SSD. Bluetooth - Qualcomm Atheros Communications AR3011. SSD - OCZ Vector 180 256. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-28-generic 5.8.0-28.30 ProcVersionSignature: Ubuntu 5.8.0-28.30-generic 5.8.14 Uname: Linux 5.8.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: navycat1951 F pulseaudio /dev/snd/controlC0: navycat1951 F pulseaudio /dev/snd/controlC1: navycat1951 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Wed Nov 11 05:26:13 2020 InstallationDate: Installed on 2020-11-01 (9 days ago) InstallationMedia: Ubuntu-MATE 20.10 "Groovy Gorilla" - Release amd64 (20201022) IwConfig: lono wireless extensions. eno1 no wireless extensions. MachineType: BASE_BOARD_MANUFACTURER MODEL_NAME ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-28-generic root=UUID=54e2fb85-ed43-4ffd-a361-504ddf86a0de ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-28-generic N/A linux-backports-modules-5.8.0-28-generic N/A linux-firmware1.190.1 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/09/2018 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 150-SE-E789 dmi.board.vendor: EVGA dmi.board.version: Patsburg dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd04/09/2018:br4.6:svnBASE_BOARD_MANUFACTURER:pnMODEL_NAME:pvrBASE_BOARD_VERSION:rvnEVGA:rn150-SE-E789:rvrPatsburg: dmi.product.family: X86 AT dmi.product.name: MODEL_NAME dmi.product.sku: PROJECT_SUB_TAG dmi.product.version: BASE_BOARD_VERSION dmi.sys.vendor: BASE_BOARD_MANUFACTURER To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1903790/+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 1910996] Re: SSD and Bluetooth conflict (Bluetooth AR3011 doesn't work)
** Changed in: linux-firmware (Ubuntu) Status: New => Confirmed -- 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/1910996 Title: SSD and Bluetooth conflict (Bluetooth AR3011 doesn't work) Status in linux-firmware package in Ubuntu: Confirmed Bug description: Bluetooth stops working when I plug in the SSD. Bluetooth - Qualcomm Atheros Communications AR3011. SSD - OCZ Vector 180 256. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-firmware 1.190.2 ProcVersionSignature: Ubuntu 5.8.0-36.40-generic 5.8.18 Uname: Linux 5.8.0-36-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: navycat2034 F pulseaudio /dev/snd/controlC0: navycat2034 F pulseaudio /dev/snd/controlC1: navycat2034 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Mon Jan 11 16:10:52 2021 Dependencies: InstallationDate: Installed on 2020-11-01 (71 days ago) InstallationMedia: Ubuntu-MATE 20.10 "Groovy Gorilla" - Release amd64 (20201022) IwConfig: lono wireless extensions. eno1 no wireless extensions. MachineType: BASE_BOARD_MANUFACTURER MODEL_NAME PackageArchitecture: all ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-36-generic root=UUID=54e2fb85-ed43-4ffd-a361-504ddf86a0de ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-36-generic N/A linux-backports-modules-5.8.0-36-generic N/A linux-firmware1.190.2 RfKill: SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/09/2018 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 150-SE-E789 dmi.board.vendor: EVGA dmi.board.version: Patsburg dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd04/09/2018:br4.6:svnBASE_BOARD_MANUFACTURER:pnMODEL_NAME:pvrBASE_BOARD_VERSION:rvnEVGA:rn150-SE-E789:rvrPatsburg: dmi.product.family: X86 AT dmi.product.name: MODEL_NAME dmi.product.sku: PROJECT_SUB_TAG dmi.product.version: BASE_BOARD_VERSION dmi.sys.vendor: BASE_BOARD_MANUFACTURER To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1910996/+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 1914654] [NEW] Focal update: v5.4.91 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.4.91 upstream stable release from git://git.kernel.org/ kbuild: enforce -Werror=return-type btrfs: prevent NULL pointer dereference in extent_io_tree_panic ASoC: dapm: remove widget from dirty list on free x86/hyperv: check cpu mask after interrupt has been disabled tracing/kprobes: Do the notrace functions check without kprobes on ftrace UBUNTU: [Config] update annotations for KPROBE_EVENTS_ON_NOTRACE mips: fix Section mismatch in reference mips: lib: uncached: fix non-standard usage of variable 'sp' MIPS: boot: Fix unaligned access with CONFIG_MIPS_RAW_APPENDED_DTB MIPS: relocatable: fix possible boot hangup with KASLR enabled RDMA/ocrdma: Fix use after free in ocrdma_dealloc_ucontext_pd() ACPI: scan: Harden acpi_device_add() against device ID overflows mm/hugetlb: fix potential missing huge page size info dm raid: fix discard limits for raid1 dm snapshot: flush merged data before committing metadata dm integrity: fix the maximum number of arguments r8152: Add Lenovo Powered USB-C Travel Hub btrfs: tree-checker: check if chunk item end overflows drm/i915/backlight: fix CPU mode backlight takeover on LPT ext4: fix bug for rename with RENAME_WHITEOUT ext4: don't leak old mountpoint samples cifs: fix interrupted close commands dm integrity: fix flush with external metadata device ARC: build: remove non-existing bootpImage from KBUILD_IMAGE ARC: build: add uImage.lzma to the top-level target ARC: build: add boot_targets to PHONY ARC: build: move symlink creation to arch/arc/Makefile to avoid race netfilter: ipset: fixes possible oops in mtype_resize btrfs: fix transaction leak and crash after RO remount caused by qgroup rescan regulator: bd718x7: Add enable times ethernet: ucc_geth: fix definition and size of ucc_geth_tx_global_pram habanalabs: register to pci shutdown callback habanalabs: Fix memleak in hl_device_reset hwmon: (pwm-fan) Ensure that calculation doesn't discard big period values lib/raid6: Let $(UNROLL) rules work with macOS userland bfq: Fix computation of shallow depth arch/arc: add copy_user_page() to to fix build error on ARC misdn: dsp: select CONFIG_BITREVERSE net: ethernet: fs_enet: Add missing MODULE_LICENSE nvme-pci: mark Samsung PM1725a as IGNORE_DEV_SUBNQN nvmet-rdma: Fix list_del corruption on queue establishment failure drm/amdgpu: fix a GPU hang issue when remove device usb: typec: Fix copy paste error for NVIDIA alt-mode description ACPI: scan: add stub acpi_create_platform_device() for !CONFIG_ACPI drm/msm: Call msm_init_vram before binding the gpu ARM: picoxcell: fix missing interrupt-parent properties perf intel-pt: Fix 'CPU too large' error dump_common_audit_data(): fix racy accesses to ->d_name ASoC: meson: axg-tdm-interface: fix loopback ASoC: meson: axg-tdmin: fix axg skew offset ASoC: Intel: fix error code cnl_set_dsp_D0() nvme-tcp: fix possible data corruption with bio merges NFS4: Fix use-after-free in trace_event_raw_event_nfs4_set_lock pNFS: We want return-on-close to complete when evicting the inode pNFS: Mark layout for return if return-on-close was not sent pNFS: Stricter ordering of layoutget and layoutreturn NFS/pNFS: Fix a leak of the layout 'plh_outstanding' counter NFS: nfs_igrab_and_active must first reference the superblock ext4: fix superblock checksum failure when setting password salt RDMA/restrack: Don't treat as an error allocation ID wrapping RDMA/usnic: Fix memleak in find_free_vf_and_create_qp_grp bnxt_en: Improve stats context resource accounting with RDMA driver loaded. RDMA/mlx5: Fix wrong free of blue flame register on error IB/mlx5: Fix error unwinding when set_has_smi_cap fails drm/i915/dsi: Use unconditional msleep for the panel_on_delay when there is no reset-deassert MIPI-sequence mm, slub: consider rest of partial list if acquire_slab() fails iommu/vt-d: Fix unaligned addresses for intel_flush_svm_range_dev() net: sunrpc: interpret the return value of kstrtou32 correctly dm: eliminate potential source of excessive kernel log noise ALSA: fireface: Fix integer overflow in transmit_midi_msg() ALSA: firewire-tascam: Fix integer overflow in midi_port_work() netfilter: conntrack: fix reading nf_conntrack_buckets netfilter: nf_nat: Fix memleak in nf_nat_init netfilter: nft_compat: remove flush counter optimization Linux 5.4.91 UBUNTU: upstream stable to v5.4.91 ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: linux (Ubuntu Focal) Importance: Undecided Assignee: Kamal Mostafa (kamalmostafa) Status: In Pr
[Kernel-packages] [Bug 1881757] Re: webcam is detected but not working with kernel 5.4.0.33
v4l2-ctl --list-devices produces USB camera (usb-:00:14.0-11): /dev/video0 Only web-based cam tests with Firefox do work (I see the video feed just fine). Cheese and Wemcamoid claim "no device found", neither before, during, or after the online cam test. uname -a Linux Neko 5.4.0-65-generic #73-Ubuntu SMP Mon Jan 18 17:25:17 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1881757 Title: webcam is detected but not working with kernel 5.4.0.33 Status in linux-signed package in Ubuntu: Fix Released Bug description: webcam is detected not working under kernel 5.4.0.33 and 5.4.0.31 . The webcam is functional with kernels 5.0 and 5.6.15 . -usb:1 description: Video product: USB 2.0 Web Camera vendor: Alcor Micro, Corp. physical id: 2 bus info: usb@1:1.2 version: 0.08 capabilities: usb-2.00 configuration: driver=uvcvideo maxpower=200mA speed=480Mbit/s susb; lsb_release -a; uname -a Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 1d0b:0021 HAN HUA CABLE & WIRE TECHNOLOGY (J.X.) CO., LTD. Bus 001 Device 003: ID 058f:5608 Alcor Micro Corp. Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 20.04 LTS Release: 20.04 Codename: focal Linux afsal-Excelance 5.4.0-33-generic #37-Ubuntu SMP Thu May 21 12:53:59 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux more info : https://answers.launchpad.net/ubuntu/+question/691070 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1881757/+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 1904293] Re: [i915] GPU hangs on Haswell (Acer 720p)
Good news, I am running 5.11.0-5c5 from ubuntu kernel ppa and the problem seems to be resolved . -- 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/1904293 Title: [i915] GPU hangs on Haswell (Acer 720p) Status in linux package in Ubuntu: Confirmed Status in linux package in Fedora: Confirmed Bug description: Since linux kernel 5.7 Haswell GPU's hang after logging in with sddm. This affects Groovy (linux 5.8) both with Ubuntu and Kubuntu. A work around is to boot with and earlier (5.6). The issue is known as: https://gitlab.freedesktop.org/drm/intel/-/issues/2413 and probable duplicates: https://gitlab.freedesktop.org/drm/intel/-/issues/2584 https://gitlab.freedesktop.org/drm/intel/-/issues/1805 Apparently the problem is resolved by: https://patchwork.freedesktop.org/patch/395580/?series=82783&rev=1 Please consider backporting this patch. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ferry 1098 F pulseaudio /dev/snd/controlC0: ferry 1102 F pipewire-media- /dev/snd/seq:ferry 1097 F pipewire CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2017-07-13 (1220 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Lsusb: Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 003: ID 0489:e056 Foxconn / Hon Hai Bus 002 Device 002: ID 1bcf:2c67 Sunplus Innovation Technology Inc. HD WebCam Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Peppy Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/@boot/vmlinuz-5.6.0-1032-oem root=UUID=17d2cd1d-cc37-446d-ac0b-933def63c867 ro rootflags=subvol=@ quiet splash tpm_tis.force=1 tpm_tis.interrupts=0 modprobe.blacklist=ehci_hcd,ehci-pci mitigations=off vt.handoff=7 ProcVersionSignature: Ubuntu 5.6.0-1032.33-oem 5.6.19 RelatedPackageVersions: linux-restricted-modules-5.6.0-1032-oem N/A linux-backports-modules-5.6.0-1032-oem N/A linux-firmware 1.190.1 Tags: groovy Uname: Linux 5.6.0-1032-oem x86_64 UpgradeStatus: Upgraded to groovy on 2020-10-25 (20 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/02/2017 dmi.bios.vendor: coreboot dmi.chassis.type: 3 dmi.chassis.vendor: Acer dmi.modalias: dmi:bvncoreboot:bvr:bd03/02/2017:svnAcer:pnPeppy:pvr1.0:cvnAcer:ct3:cvr: dmi.product.name: Peppy dmi.product.version: 1.0 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904293/+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 1902457] Re: regression: no sound cards detected on lenovo yoga c930 after focal->groovy upgrade
still no sound. see attached dmesg. ** Attachment added: "modsort-5.11.0-7-generic" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902457/+attachment/5460056/+files/modsort-5.11.0-7-generic -- 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/1902457 Title: regression: no sound cards detected on lenovo yoga c930 after focal->groovy upgrade Status in linux package in Ubuntu: Confirmed Bug description: After upgrading to Groovy, my sound cards no longer work. Alsa-info says "no soundcards detected" --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: XFCE DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2019-07-25 (465 days ago) InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 007: ID 8087:0025 Intel Corp. Wireless-AC 9260 Bluetooth Adapter Bus 001 Device 006: ID 06cb:0081 Synaptics, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M |__ Port 5: Dev 6, If 0, Class=Vendor Specific Class, Driver=, 12M |__ Port 8: Dev 7, If 1, Class=Wireless, Driver=btusb, 12M |__ Port 8: Dev 7, If 0, Class=Wireless, Driver=btusb, 12M MachineType: LENOVO 81C4 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-26-generic root=/dev/mapper/xubuntu--c930-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 RelatedPackageVersions: linux-restricted-modules-5.8.0-26-generic N/A linux-backports-modules-5.8.0-26-generic N/A linux-firmware1.190 Tags: groovy Uname: Linux 5.8.0-26-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: Upgraded to groovy on 2020-10-30 (2 days ago) UserGroups: adm cdrom dialout dip i2c input lpadmin plugdev sambashare sudo video _MarkForUpload: False dmi.bios.date: 10/09/2018 dmi.bios.release: 1.32 dmi.bios.vendor: LENOVO dmi.bios.version: 8GCN32WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo YOGA C930-13IKB dmi.ec.firmware.release: 1.32 dmi.modalias: dmi:bvnLENOVO:bvr8GCN32WW:bd10/09/2018:br1.32:efr1.32:svnLENOVO:pn81C4:pvrLenovoYOGAC930-13IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct31:cvrLenovoYOGAC930-13IKB: dmi.product.family: YOGA C930-13IKB dmi.product.name: 81C4 dmi.product.sku: LENOVO_MT_81C4_BU_idea_FM_YOGA C930-13IKB dmi.product.version: Lenovo YOGA C930-13IKB dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.1 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2019-07-25 (487 days ago) InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Package: linux (not installed) Tags: groovy Uname: Linux 5.10.0-051000rc5-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to groovy on 2020-10-30 (24 days ago) UserGroups: adm cdrom dialout dip i2c input lpadmin plugdev sambashare sudo video _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: XFCE DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2019-07-25 (496 days ago) InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 008: ID 8087:0025 Intel Corp. Wireless-AC 9260 Bluetooth Adapter Bus 001 Device 007: ID 10c4:ea60 Silicon Labs CP210x UART Bridge Bus 001 Device 006: ID 06cb:0081 Synaptics, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81C4 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-31-generic root=/dev/mapper/xubuntu--c930-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-31.33-generic 5.8.17 RelatedPackageVersions: linux-restricted-modules-5.8.0-31-generic N/A linux-backports-modules-5.8.0-31-generic N/A
[Kernel-packages] [Bug 1914648] [NEW] Xenial update: v4.4.254 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v4.4.254 upstream stable release from git://git.kernel.org/ ALSA: seq: oss: Fix missing error check in snd_seq_oss_synth_make_info() ALSA: hda/via: Add minimum mute flag ACPI: scan: Make acpi_bus_get_device() clear return pointer on error dm: avoid filesystem lookup in dm_get_dev_t() ASoC: Intel: haswell: Add missing pm_ops scsi: ufs: Correct the LUN used in eh_device_reset_handler() callback drm/nouveau/bios: fix issue shadowing expansion ROMs drm/nouveau/i2c/gm200: increase width of aux semaphore owner fields can: dev: can_restart: fix use after free bug iio: ad5504: Fix setting power-down state ehci: fix EHCI host controller initialization sequence usb: bdc: Make bdc pci driver depend on BROKEN UBUNTU: [Config] updateconfigs for USB_BDC_PCI xhci: make sure TRB is fully written before giving it to the controller compiler.h: Raise minimum version of GCC to 5.1 for arm64 netfilter: rpfilter: mask ecn bits before fib lookup sh: dma: fix kconfig dependency for G2_DMA sh_eth: Fix power down vs. is_opened flag ordering skbuff: back tiny skbs with kmalloc() in __netdev_alloc_skb() too ipv6: create multicast route with RTPROT_KERNEL net_sched: avoid shift-out-of-bounds in tcindex_set_parms() Revert "mm/slub: fix a memory leak in sysfs_slab_add()" tracing: Fix race in trace_open and buffer resize call xen-blkback: set ring->xenblkd to NULL after kthread_stop() x86/boot/compressed: Disable relocation relaxation Linux 4.4.254 UBUNTU: upstream stable to v4.4.254 ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: linux (Ubuntu Xenial) Importance: Undecided Assignee: Kamal Mostafa (kamalmostafa) Status: In Progress ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Status: New => In Progress ** Changed in: linux (Ubuntu Xenial) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) ** Description changed: + SRU Justification - SRU Justification + Impact: + The upstream process for stable tree updates is quite similar + in scope to the Ubuntu SRU process, e.g., each patch has to + demonstrably fix a bug, and each patch is vetted by upstream + by originating either directly from a mainline/stable Linux tree or + a minimally backported form of that patch. The following upstream + stable patches should be included in the Ubuntu kernel: - Impact: -The upstream process for stable tree updates is quite similar -in scope to the Ubuntu SRU process, e.g., each patch has to -demonstrably fix a bug, and each patch is vetted by upstream -by originating either directly from a mainline/stable Linux tree or -a minimally backported form of that patch. The following upstream -stable patches should be included in the Ubuntu kernel: + v4.4.254 upstream stable release + from git://git.kernel.org/ -v4.4.254 upstream stable release -from git://git.kernel.org/ + ALSA: seq: oss: Fix missing error check in snd_seq_oss_synth_make_info() + ALSA: hda/via: Add minimum mute flag + ACPI: scan: Make acpi_bus_get_device() clear return pointer on error + dm: avoid filesystem lookup in dm_get_dev_t() + ASoC: Intel: haswell: Add missing pm_ops + scsi: ufs: Correct the LUN used in eh_device_reset_handler() callback + drm/nouveau/bios: fix issue shadowing expansion ROMs + drm/nouveau/i2c/gm200: increase width of aux semaphore owner fields + can: dev: can_restart: fix use after free bug + iio: ad5504: Fix setting power-down state + ehci: fix EHCI host controller initialization sequence + usb: bdc: Make bdc pci driver depend on BROKEN + UBUNTU: [Config] updateconfigs for USB_BDC_PCI + xhci: make sure TRB is fully written before giving it to the controller + compiler.h: Raise minimum version of GCC to 5.1 for arm64 + netfilter: rpfilter: mask ecn bits before fib lookup + sh: dma: fix kconfig dependency for G2_DMA + sh_eth: Fix power down vs. is_opened flag ordering + skbuff: back tiny skbs with kmalloc() in __netdev_alloc_skb() too + ipv6: create multicast route with RTPROT_KERNEL + net_sched: avoid shift-out-of-bounds in tcindex_set_parms() + Revert "mm/slub: fix a memory leak in sysfs_slab_add()" + tracing: Fix race in trace_open and buffer resize call + xe
[Kernel-packages] [Bug 1914647] [NEW] Xenial update: v4.4.253 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v4.4.253 upstream stable release from git://git.kernel.org/ ASoC: dapm: remove widget from dirty list on free mm/hugetlb: fix potential missing huge page size info ext4: fix bug for rename with RENAME_WHITEOUT ARC: build: add boot_targets to PHONY ethernet: ucc_geth: fix definition and size of ucc_geth_tx_global_pram arch/arc: add copy_user_page() to to fix build error on ARC misdn: dsp: select CONFIG_BITREVERSE net: ethernet: fs_enet: Add missing MODULE_LICENSE ACPI: scan: add stub acpi_create_platform_device() for !CONFIG_ACPI ARM: picoxcell: fix missing interrupt-parent properties Input: uinput - avoid FF flush when destroying device dump_common_audit_data(): fix racy accesses to ->d_name NFS: nfs_igrab_and_active must first reference the superblock ext4: fix superblock checksum failure when setting password salt RDMA/usnic: Fix memleak in find_free_vf_and_create_qp_grp mm, slub: consider rest of partial list if acquire_slab() fails net: sunrpc: interpret the return value of kstrtou32 correctly usb: ohci: Make distrust_firmware param default to false iio: buffer: Fix demux update nfsd4: readdirplus shouldn't return parent of export net: cdc_ncm: correct overhead in delayed_ndp_size netxen_nic: fix MSI/MSI-x interrupts rndis_host: set proper input size for OID_GEN_PHYSICAL_MEDIUM request net: dcb: Validate netlink message in DCB handler net: dcb: Accept RTM_GETDCB messages carrying set-like DCB commands net: sit: unregister_netdevice on newlink's error path rxrpc: Fix handling of an unsupported token type in rxrpc_read() net: avoid 32 x truesize under-estimation for tiny skbs spi: cadence: cache reference clock rate during probe Linux 4.4.253 UBUNTU: upstream stable to v4.4.253 ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: linux (Ubuntu Xenial) Importance: Undecided Assignee: Kamal Mostafa (kamalmostafa) Status: In Progress ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Status: New => In Progress ** Changed in: linux (Ubuntu Xenial) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) ** Description changed: + SRU Justification - SRU Justification + Impact: + The upstream process for stable tree updates is quite similar + in scope to the Ubuntu SRU process, e.g., each patch has to + demonstrably fix a bug, and each patch is vetted by upstream + by originating either directly from a mainline/stable Linux tree or + a minimally backported form of that patch. The following upstream + stable patches should be included in the Ubuntu kernel: - Impact: -The upstream process for stable tree updates is quite similar -in scope to the Ubuntu SRU process, e.g., each patch has to -demonstrably fix a bug, and each patch is vetted by upstream -by originating either directly from a mainline/stable Linux tree or -a minimally backported form of that patch. The following upstream -stable patches should be included in the Ubuntu kernel: + v4.4.253 upstream stable release + from git://git.kernel.org/ -v4.4.253 upstream stable release -from git://git.kernel.org/ + ASoC: dapm: remove widget from dirty list on free + mm/hugetlb: fix potential missing huge page size info + ext4: fix bug for rename with RENAME_WHITEOUT + ARC: build: add boot_targets to PHONY + ethernet: ucc_geth: fix definition and size of ucc_geth_tx_global_pram + arch/arc: add copy_user_page() to to fix build error on ARC + misdn: dsp: select CONFIG_BITREVERSE + net: ethernet: fs_enet: Add missing MODULE_LICENSE + ACPI: scan: add stub acpi_create_platform_device() for !CONFIG_ACPI + ARM: picoxcell: fix missing interrupt-parent properties + Input: uinput - avoid FF flush when destroying device + dump_common_audit_data(): fix racy accesses to ->d_name + NFS: nfs_igrab_and_active must first reference the superblock + ext4: fix superblock checksum failure when setting password salt + RDMA/usnic: Fix memleak in find_free_vf_and_create_qp_grp + mm, slub: consider rest of partial list if acquire_slab() fails + net: sunrpc: interpret the return value of kstrtou32 correctly + usb: ohci: Make distrust_firmware param default to false + iio: buffer: Fix demux u
[Kernel-packages] [Bug 1883511] Re: High load from process irq/65-i2c-INT3 - kernel module tps6598x
** Tags removed: verification-needed-focal ** Tags added: verification-failed-focal -- 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/1883511 Title: High load from process irq/65-i2c-INT3 - kernel module tps6598x Status in linux package in Ubuntu: Confirmed Bug description: There seems to be an issue with the kernel module tps6598x which puts the CPU on a high load: https://forums.intel.com/s/question/0D50P4fWnUeSAK/nuc10i3-irq- problem As soon as the module is unloaded, cpu load is back to normal. According to a post in the link above the issue is the following: "My guess is that the IRQ resource is not correct for the PD controller causing you to see irq flood. The problem is that the ACPI device entry (the node) on this platform has 4 I2CSerialBus resources and 4 IRQ resources. The idea is that the single ACPI device entry can represent up to 4 USB PD controllers. The problem is that there is no way to know which IRQ resource belongs to which I2CSerialBus resource :-(. Andy, this is one of those multi-instantiate I2C slave devices with HID INT3515. The only solution I can think of is that we start maintaining DMI quirk table in drivers/platform/x86/i2c-multi-instantiate.c where we supply the correct i2c to irq resource mapping for every platform that has this device(s)." Description: Ubuntu 20.04 LTS Release: 20.04 Hardware: Intel NUC10i5FNK ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-37-generic 5.4.0-37.41 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-37-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: pass Date: Mon Jun 15 11:04:57 2020 InstallationDate: Installed on 2020-04-26 (49 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Intel(R) Client Systems NUC10i5FNK ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-37-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro RelatedPackageVersions: linux-restricted-modules-5.4.0-37-generic N/A linux-backports-modules-5.4.0-37-generic N/A linux-firmware1.187 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/18/2020 dmi.bios.vendor: Intel Corp. dmi.bios.version: FNCML357.0041.2020.0518.1045 dmi.board.asset.tag: Default string dmi.board.name: NUC10i5FNB dmi.board.vendor: Intel Corporation dmi.board.version: K61361-302 dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrFNCML357.0041.2020.0518.1045:bd05/18/2020:svnIntel(R)ClientSystems:pnNUC10i5FNK:pvrK61339-302:rvnIntelCorporation:rnNUC10i5FNB:rvrK61361-302:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: FN dmi.product.name: NUC10i5FNK dmi.product.sku: BXNUC10i5FNK dmi.product.version: K61339-302 dmi.sys.vendor: Intel(R) Client Systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1883511/+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 1910927] Re: Suspend stopped working since kernel 5.4 (ubuntu 20.04)
As a temporary workaround, exists a lts kernel ppa from ubuntu 18.04 which I can use at 20.04? -- 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/1910927 Title: Suspend stopped working since kernel 5.4 (ubuntu 20.04) Status in linux package in Ubuntu: Confirmed Bug description: Suspend was working on ubuntu 18.04 with kernel 4.15.0-128. After upgrade to ubuntu 20.04, suspend is not working. The device is on black screen, fully powered and not responding any longer. I can still boot the old kernel 4.15.0-128 from ubuntu 18.04, suspend is working with this kernel! I tested kernel 5.4.0-60 and 5.8.0-36 from hwe. With both kernels, suspend is broken on my older device with Core2Duo. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: xubuntu4020 F pulseaudio CasperMD5CheckResult: pass CasperVersion: 1.445 CurrentDesktop: XFCE DistroRelease: Ubuntu 20.04 LiveMediaBuild: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: SAMSUNG ELECTRONICS CO., LTD. R510/P510 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair 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 nouveaudrmfb ProcKernelCmdLine: file=/cdrom/preseed/username.seed initrd=/casper/initrd quiet splash --- maybe-ubiquity ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 RelatedPackageVersions: linux-restricted-modules-5.4.0-26-generic N/A linux-backports-modules-5.4.0-26-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-26-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: 04/01/2010 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: 10LI.M008.20100401.KSJ dmi.board.name: R510/P510 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr10LI.M008.20100401.KSJ:bd04/01/2010:svnSAMSUNGELECTRONICSCO.,LTD.:pnR510/P510:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnR510/P510:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A: dmi.product.name: R510/P510 dmi.product.version: Not Applicable dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1910927/+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 1914643] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1914643 Title: my touchpad is not installed in ubuntu 14.10 Status in linux package in Ubuntu: Confirmed Bug description: my touchpad is not installed in ubuntu 14.10 ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-23-generic 3.16.0-23.31 [modified: boot/vmlinuz-3.16.0-23-generic] ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4 Uname: Linux 3.16.0-23-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sourour2153 F pulseaudio CurrentDesktop: Unity Date: Thu Feb 4 19:45:11 2021 HibernationDevice: RESUME=UUID=e5ecc18c-65d9-4871-b962-da0e0a03a841 InstallationDate: Installed on 2021-02-04 (0 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 04ca:3010 Lite-On Technology Corp. Bus 001 Device 004: ID 04f2:b52b Chicony Electronics Co., Ltd Bus 001 Device 002: ID 17ef:608d Lenovo Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X541UJ ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-23-generic root=UUID=daeaa0a1-bc6f-416d-bbe4-cdc031210896 ro i8042.reset quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.16.0-23-generic N/A linux-backports-modules-3.16.0-23-generic N/A linux-firmware 1.138 SourcePackage: linux UpgradeStatus: Upgraded to utopic on 2021-02-04 (0 days ago) dmi.bios.date: 04/18/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X541UJ.310 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X541UJ dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX541UJ.310:bd04/18/2019:svnASUSTeKCOMPUTERINC.:pnX541UJ:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX541UJ:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X541UJ dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1914643/+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 1914643] [NEW] my touchpad is not installed in ubuntu 14.10
Public bug reported: my touchpad is not installed in ubuntu 14.10 ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-23-generic 3.16.0-23.31 [modified: boot/vmlinuz-3.16.0-23-generic] ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4 Uname: Linux 3.16.0-23-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sourour2153 F pulseaudio CurrentDesktop: Unity Date: Thu Feb 4 19:45:11 2021 HibernationDevice: RESUME=UUID=e5ecc18c-65d9-4871-b962-da0e0a03a841 InstallationDate: Installed on 2021-02-04 (0 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 04ca:3010 Lite-On Technology Corp. Bus 001 Device 004: ID 04f2:b52b Chicony Electronics Co., Ltd Bus 001 Device 002: ID 17ef:608d Lenovo Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X541UJ ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-23-generic root=UUID=daeaa0a1-bc6f-416d-bbe4-cdc031210896 ro i8042.reset quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.16.0-23-generic N/A linux-backports-modules-3.16.0-23-generic N/A linux-firmware 1.138 SourcePackage: linux UpgradeStatus: Upgraded to utopic on 2021-02-04 (0 days ago) dmi.bios.date: 04/18/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X541UJ.310 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X541UJ dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX541UJ.310:bd04/18/2019:svnASUSTeKCOMPUTERINC.:pnX541UJ:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX541UJ:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X541UJ dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug utopic -- 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/1914643 Title: my touchpad is not installed in ubuntu 14.10 Status in linux package in Ubuntu: New Bug description: my touchpad is not installed in ubuntu 14.10 ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-23-generic 3.16.0-23.31 [modified: boot/vmlinuz-3.16.0-23-generic] ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4 Uname: Linux 3.16.0-23-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sourour2153 F pulseaudio CurrentDesktop: Unity Date: Thu Feb 4 19:45:11 2021 HibernationDevice: RESUME=UUID=e5ecc18c-65d9-4871-b962-da0e0a03a841 InstallationDate: Installed on 2021-02-04 (0 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 04ca:3010 Lite-On Technology Corp. Bus 001 Device 004: ID 04f2:b52b Chicony Electronics Co., Ltd Bus 001 Device 002: ID 17ef:608d Lenovo Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X541UJ ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-23-generic root=UUID=daeaa0a1-bc6f-416d-bbe4-cdc031210896 ro i8042.reset quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.16.0-23-generic N/A linux-backports-modules-3.16.0-23-generic N/A linux-firmware 1.138 SourcePackage: linux UpgradeStatus: Upgraded to utopic on 2021-02-04 (0 days ago) dmi.bios.date: 04/18/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X541UJ.310 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X541UJ dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX541UJ.310:bd04/18/2019:svnASUSTeKCOMPUTERINC.:pnX541UJ:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX541UJ:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X541UJ dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1914643/+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/ListH
[Kernel-packages] [Bug 1914146] Re: package zfsutils-linux 0.8.3-1ubuntu12.6 failed to install/upgrade: installed zfsutils-linux package post-installation script subprocess returned error exit status
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: zfs-linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1914146 Title: package zfsutils-linux 0.8.3-1ubuntu12.6 failed to install/upgrade: installed zfsutils-linux package post-installation script subprocess returned error exit status 1 Status in zfs-linux package in Ubuntu: Confirmed Bug description: none ProblemType: Package DistroRelease: Ubuntu 20.04 Package: zfsutils-linux 0.8.3-1ubuntu12.6 ProcVersionSignature: Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Feb 1 18:51:48 2021 ErrorMessage: installed zfsutils-linux package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2020-12-09 (54 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.4 SourcePackage: zfs-linux Title: package zfsutils-linux 0.8.3-1ubuntu12.6 failed to install/upgrade: installed zfsutils-linux package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1914146/+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 1749961] Re: xhci_hcd: TRB DMA errors reported with ASMedia ASM1142 USB 3.1 Controller
I did a little bit of research on the Razer Core Chroma usb card. This card uses 3 ASM1142 pcie to usb bridges (let's call them IC_0, IC_1, IC_2) and the PCIe 4x connector is wired in a non-standard way. IC_0 is wired up to the PCIe in a normal fashion using only the pcie lane 0 (TX and RX) and the "usual" clock lane. IC_1 data lanes are wired to pci lane 1 (TX and RX) but the clock lane has been wired to lane 3 RX. IC_2 data lanes are wired to pci lane 2 (TX and RX) but the clock lane has been wired to lane 3 TX. Furthermore IC_2 has one of it's two USB interfaces wired to an USB to Ethernet bridge (ASIX AX88179), while the other one is connected to another micro-controller on the Chroma's main board that I presume controls the LED colours, in windows this IC is detected as some sort of mouse so I would say that Razer have recycled some code to implement this... All clock lanes merge together in another IC (IC_4) that is on the Chroma's main board. I would say that they are doing some sort of Time-division to share the same PCIe port for three different devices and this is provoking all the mess. I have read people having trouble in every single OS (MacOS, Windows and Linux) with this device. I would expeted such junkie desing on low budged development, but never in a company as Razer. And their response to they issue is been horrendous... something to bare in mind in future acquisitions Anyway it would be interesting to know if other people having trouble has more of one ASM1142 or not -- 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/1749961 Title: xhci_hcd: TRB DMA errors reported with ASMedia ASM1142 USB 3.1 Controller Status in linux package in Ubuntu: In Progress Status in linux source package in Trusty: Won't Fix Status in linux source package in Xenial: Confirmed Status in linux source package in Bionic: Confirmed Status in linux source package in Focal: Confirmed Status in linux package in Debian: Confirmed Bug description: It was observed that while trying to use a 4K USB webcam connected to USB port provided by ASMedia ASM1142 USB 3.1 Controller, the webcam does not work and kernel log shows the following messages: [431.928016] xhci_hcd :12:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13 [431.928021] xhci_hcd :12:00.0: Looking for event-dma 003f3330e020 trb-start 003f3330e000 trb-end 003f3330e000 seg-start 003f3330e000 seg-end 003f3330eff0 [431.928024] xhci_hcd :12:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13 [431.928026] xhci_hcd :12:00.0: Looking for event-dma 003f3330e030 trb-start 003f3330e000 trb-end 003f3330e000 seg-start 003f3330e000 seg-end 003f3330eff0 [431.928027] xhci_hcd :12:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13 [431.928029] xhci_hcd :12:00.0: Looking for event-dma 003f3330e050 trb-start 003f3330e000 trb-end 003f3330e000 seg-start 003f3330e000 seg-end 003f3330eff0 [431.928386] xhci_hcd :12:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13 A similar issue was already reported on Launchpad: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1667750 The fix to this issue seems to be the following patch: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=9da5a109 Tests in our scenario with this patch proved still broken. Our next approach is to modify the patch a bit and re-test. This LP will be used to document our progress in the investigation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1749961/+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 1914221] 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 1914221 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1914221 Title: dev test in ubuntu_stress_smoke_test hang with G-5.8 lowlatency Status in Stress-ng: New Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Bug description: Issue found on Groovy 5.8.0-42.47 lowlatency kernel with node "spitfire" on Intel cloud. Reproduce rate: 2/2 The ubuntu_stress_smoke_test hang with the dev test on it: dentry STARTING dentry RETURNED 0 dentry PASSED dev STARTING Timer expired (2100 sec.), nuking pid 15918 ERROR ubuntu_stress_smoke_test.stress-smoke-test ubuntu_stress_smoke_test.stress-smoke-test timestamp=1612262460 localtime=Feb 02 10:41:00 Test timeout expired, rc=15 However, this issue didn't happen on this node with Groovy 5.8 generic kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/stress-ng/+bug/1914221/+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
** 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 1914221] Re: dev test in ubuntu_stress_smoke_test hang with G-5.8 lowlatency
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Colin Ian King (colin-king) ** Changed in: stress-ng Assignee: (unassigned) => Colin Ian King (colin-king) ** Changed in: ubuntu-kernel-tests Assignee: (unassigned) => Colin Ian King (colin-king) -- 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/1914221 Title: dev test in ubuntu_stress_smoke_test hang with G-5.8 lowlatency Status in Stress-ng: New Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Bug description: Issue found on Groovy 5.8.0-42.47 lowlatency kernel with node "spitfire" on Intel cloud. Reproduce rate: 2/2 The ubuntu_stress_smoke_test hang with the dev test on it: dentry STARTING dentry RETURNED 0 dentry PASSED dev STARTING Timer expired (2100 sec.), nuking pid 15918 ERROR ubuntu_stress_smoke_test.stress-smoke-test ubuntu_stress_smoke_test.stress-smoke-test timestamp=1612262460 localtime=Feb 02 10:41:00 Test timeout expired, rc=15 However, this issue didn't happen on this node with Groovy 5.8 generic kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/stress-ng/+bug/1914221/+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 1910211] Re: Fix the video can't output through WD19TB connected with TGL platform during cold-boot
** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- 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/1910211 Title: Fix the video can't output through WD19TB connected with TGL platform during cold-boot 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 source package in Focal: Invalid Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux source package in Hirsute: In Progress Status in linux-oem-5.10 source package in Hirsute: Invalid Bug description: [Impact] After Apply the patches from https://www.spinics.net/lists/intel-gfx/msg248700.html, the TGL platform would have the failure rate(1/20) on outputting the video through WD19TB. [Fix] The patch is provided by Imre(https://gitlab.freedesktop.org/drm/intel/-/issues/2801#note_740352). If there's no lttpr in the link chain, the DRM driver wouldn't configure the transparent mode again. [Test Case] 1. Connected the WD19TB with the TGL platform and connected the external monitor on WD19TB with HDMI/Displayport. 2. Don't plug the external monitor on the TGL platform, so there's only one monitor on WD19TB. 3. Cold boot the TGL platform. 4. Check the monitor can be blinked and the video can output to the monitor. [Where problems could occur] As per Imre's comment, this may be caused by the dock. In the future if the WD19TB's firmware is updated, we may encounter the same issue again. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1910211/+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 1869763] Re: Huawei Kunpeng 920 arm64 machine KVM guest frequently crash
>From description this issue happens with Ubuntu 18.04.4 LTS, 4.15.0-91-generic and can not reproduce with HWE kernel. Is there any qemu options needed to reproduce? I am going to create a KVM guest on Ubuntu 18.04 GA kernel with kunpeng920 machines and see if I can reproduce. -- 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/1869763 Title: Huawei Kunpeng 920 arm64 machine KVM guest frequently crash Status in kunpeng920: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: Hardware spec: 64 core 64 G ram arm64 OS & kernel version: Ubuntu 18.04.4 LTS, 4.15.0-91-generic `virt-host-validate qemu` output: QEMU: Checking if device /dev/kvm exists : PASS QEMU: Checking if device /dev/kvm is accessible : PASS QEMU: Checking if device /dev/vhost-net exists : PASS QEMU: Checking if device /dev/net/tun exists : PASS QEMU: Checking for cgroup 'memory' controller support : PASS QEMU: Checking for cgroup 'memory' controller mount-point : PASS QEMU: Checking for cgroup 'cpu' controller support : PASS QEMU: Checking for cgroup 'cpu' controller mount-point : PASS QEMU: Checking for cgroup 'cpuacct' controller support : PASS QEMU: Checking for cgroup 'cpuacct' controller mount-point : PASS QEMU: Checking for cgroup 'cpuset' controller support : PASS QEMU: Checking for cgroup 'cpuset' controller mount-point : PASS QEMU: Checking for cgroup 'devices' controller support : PASS QEMU: Checking for cgroup 'devices' controller mount-point : PASS QEMU: Checking for cgroup 'blkio' controller support : PASS QEMU: Checking for cgroup 'blkio' controller mount-point : PASS WARN (Unknown if this platform has IOMMU support) libvirt version: 4.0.0-1ubuntu8.14 qemu version: 1:2.11+dfsg-1ubuntu7.23arm64 guest vm kernel version: 4.15.0-64-generic aarch64 dmesg log: kvm [49132]: Unexpected L2 read permission error libvirt log: ubuntu libvirtd: 2020-03-20 03:04.474+: 42934: warning : qemuDomainObjTaint:5602 : Domain id=38 name='vm-157' uuid=3d447d79-c2a1-4351-b607-6698a2cd6c5f is tainted: host-cpu When "Unexpected L2 read permission error" this error occured, one of guest machines will become "paused" state, need to `virsh reset PAUSED_VM_NAME` to reset then start it. Those guest vm hang/crash occured very frequently, sometimes several times per hour. To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1869763/+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 1911376] Re: [ssbs-0118] backport SSBS bug (arm64: cpufeature: Detect SSBS and advertise to userspace)
** Description changed:
+ [Impact]
+ The SSBS patch in 4.14 stable kernel, and mainline kernel adds snippet
+ into arm64_cpufeatures but in bionic kernel, it is landed into
arm64_elf_hwcaps.
+
+ [Fix]
+ Move SSBS snippet from arm64_elf_hwcaps back to arm64_features
+
+ [Test]
+ No known tool for SSB attack. Regression test only.
+
+ [Regression Potential]
+ Regression might be on all arm64 platforms. Regression test on all arm64
platform we have is recommended.
+
+ =
[Bug Description]
ubuntu 18.04.1 fail to enable this SSBS function, this sys log will call
trace as follow:
-
- [0.662089] Call trace:
- [0.662870] setup_elf_hwcaps+0xb8/0xd4
- [0.664023] setup_cpu_features+0x60/0xf8
- [0.665216] smp_cpus_done+0x34/0xa8
- [0.666547] smp_init+0x120/0x138
- [0.667555] kernel_init_freeable+0xf4/0x260
- [0.668860] kernel_init+0x18/0x110
- [0.670025] ret_from_fork+0x10/0x18
-
+
+ [0.662089] Call trace:
+ [0.662870] setup_elf_hwcaps+0xb8/0xd4
+ [0.664023] setup_cpu_features+0x60/0xf8
+ [0.665216] smp_cpus_done+0x34/0xa8
+ [0.666547] smp_init+0x120/0x138
+ [0.667555] kernel_init_freeable+0xf4/0x260
+ [0.668860] kernel_init+0x18/0x110
+ [0.670025] ret_from_fork+0x10/0x18
[Steps to Reproduce]
1) boot this system
2) uname -a
Ubuntu 4.15.0-99.100-generic 4.15.18
+ [Actual Results]
+ boot error:
+ [0.662089] Call trace:
+ [0.662870] setup_elf_hwcaps+0xb8/0xd4
+ [0.664023] setup_cpu_features+0x60/0xf8
+ [0.665216] smp_cpus_done+0x34/0xa8
+ [0.666547] smp_init+0x120/0x138
+ [0.667555] kernel_init_freeable+0xf4/0x260
+ [0.668860] kernel_init+0x18/0x110
+ [0.670025] ret_from_fork+0x10/0x18
- [Actual Results]
- boot error:
- [0.662089] Call trace:
- [0.662870] setup_elf_hwcaps+0xb8/0xd4
- [0.664023] setup_cpu_features+0x60/0xf8
- [0.665216] smp_cpus_done+0x34/0xa8
- [0.666547] smp_init+0x120/0x138
- [0.667555] kernel_init_freeable+0xf4/0x260
- [0.668860] kernel_init+0x18/0x110
- [0.670025] ret_from_fork+0x10/0x18
-
[Expected Results]
no error
[Reproducibility]
NA
[Additional information]
(Firmware version, kernel version, affected hardware, etc. if required):
arm64: cpufeature: Detect SSBS and advertise to userspace
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=d71be2b6c0e19180b5f80a6d42039cc074a693a2
backport this following code into "static const struct
arm64_cpu_capabilities arm64_elf_hwcaps[]" which will be error.
1274 #ifdef CONFIG_ARM64_SSBD
1275 {
1276 .desc = "Speculative Store Bypassing Safe (SSBS)",
1277 .capability = ARM64_SSBS,
1278 .type = ARM64_CPUCAP_WEAK_LOCAL_CPU_FEATURE,
1279 .matches = has_cpuid_feature,
1280 .sys_reg = SYS_ID_AA64PFR1_EL1,
1281 .field_pos = ID_AA64PFR1_SSBS_SHIFT,
1282 .sign = FTR_UNSIGNED,
1283 .min_field_value = ID_AA64PFR1_SSBS_PSTATE_ONLY,
1284 .cpu_enable = cpu_enable_ssbs,
1285 },
[Resolution]
Can you backport aboving code into "static const struct
arm64_cpu_capabilities arm64_features[] = {"?
--
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/1911376
Title:
[ssbs-0118] backport SSBS bug (arm64: cpufeature: Detect SSBS and
advertise to userspace)
Status in kunpeng920:
In Progress
Status in kunpeng920 ubuntu-18.04 series:
In Progress
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Bionic:
In Progress
Bug description:
[Impact]
The SSBS patch in 4.14 stable kernel, and mainline kernel adds snippet
into arm64_cpufeatures but in bionic kernel, it is landed into
arm64_elf_hwcaps.
[Fix]
Move SSBS snippet from arm64_elf_hwcaps back to arm64_features
[Test]
No known tool for SSB attack. Regression test only.
[Regression Potential]
Regression might be on all arm64 platforms. Regression test on all arm64
platform we have is recommended.
=
[Bug Description]
ubuntu 18.04.1 fail to enable this SSBS function, this sys log wi
[Kernel-packages] [Bug 1910928] Re: Bluetooth (Intel AX201 / AX1650i) won't go live after suspend Lenovo Thinkbook 14 IIL
[9.102388] usb 3-10: new full-speed USB device number 6 using xhci_hcd [9.252438] usb 3-10: New USB device found, idVendor=8087, idProduct=0026, bcdDevice= 0.02 [9.252442] usb 3-10: New USB device strings: Mfr=0, Product=0, SerialNumber=0 ... [ 77.844238] usb 3-10: USB disconnect, device number 6 It seems for some reason your usb device is dropped and didn't re-appear in `lsusb -t` in comment #27. Please append following kernel boot parameters, reboot and attach output of `journalctl -b`: dyndbg="file drivers/bluetooth/* +plft" dyndbg="file drivers/acpi/power.c +plft" log_buf_len=32M ignore_loglevel initcall_debug For detailed steps, please see https://wiki.ubuntu.com/Kernel/KernelBootParameters#Temporarily_Add_a_Kernel_Boot_Parameter_for_Testing . ** Tags added: hwe-bluetooth ** Summary changed: - Bluetooth (Intel AX201 / AX1650i) won't go live after suspend Lenovo Thinkbook 14 IIL + Intel Killer AX1650i [8086:34f0] Subsystem [8086:0074] Bluetooth won't go live after suspend Lenovo Thinkbook 14 IIL ** 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/1910928 Title: Intel Killer AX1650i [8086:34f0] Subsystem [8086:0074] Bluetooth won't go live after suspend Lenovo Thinkbook 14 IIL Status in linux package in Ubuntu: Incomplete Bug description: After I have installed the Ubuntu - I have noticed, that Bluetooth won't go turn on after Suspend. The only way to get it working - reboot the system. WiFi Adapter - AX201 I have tried the latest kernel (5.11.rc2) - no luck. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.455 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InterestingModules: rfcomm bnep btusb bluetooth LiveMediaBuild: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: LENOVO 20SL NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: bluez 5.55-0ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Tags: groovy Uname: Linux 5.8.0-25-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: 11/18/2020 dmi.bios.release: 1.22 dmi.bios.vendor: LENOVO dmi.bios.version: DJCN22WW dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ThinkBook 14-IIL dmi.ec.firmware.release: 1.18 dmi.modalias: dmi:bvnLENOVO:bvrDJCN22WW:bd11/18/2020:br1.22:efr1.18:svnLENOVO:pn20SL:pvrLenovoThinkBook14-IIL:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoThinkBook14-IIL: dmi.product.family: Thinkbook 14-IIL dmi.product.name: 20SL dmi.product.sku: LENOVO_MT_20SL_BU_idea_FM_Thinkbook 14-IIL dmi.product.version: Lenovo ThinkBook 14-IIL dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: 18:26:49:C4:B9:6C ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:19913 acl:0 sco:0 events:3169 errors:0 TX bytes:770617 acl:0 sco:0 commands:3167 errors:0 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.455 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InterestingModules: rfcomm bnep btusb bluetooth LiveMediaBuild: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: LENOVO 20SL NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: bluez 5.55-0ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Tags: groovy Uname: Linux 5.8.0-25-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: 11/18/2020 dmi.bios.release: 1.22 dmi.bios.vendor: LENOVO dmi.bios.version: DJCN22WW dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ThinkBook 14-IIL dmi.ec.firmware.release: 1.18 dmi.modalias: dmi:bvnLENOVO:bvrDJCN22WW:bd11/18/20
[Kernel-packages] [Bug 1914608] Re: no console during boot on UC20
** Changed in: linux-raspi (Ubuntu) Status: New => Confirmed ** Also affects: linux-raspi (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-raspi (Ubuntu Hirsute) Importance: Undecided Status: Confirmed ** Also affects: linux-raspi (Ubuntu Groovy) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1914608 Title: no console during boot on UC20 Status in linux-raspi package in Ubuntu: Confirmed Status in linux-raspi source package in Focal: New Status in linux-raspi source package in Groovy: New Status in linux-raspi source package in Hirsute: Confirmed Bug description: when booting UC20 on a Pi4 the screen backlight is completely off and no signal is produced. inspecting the boot a little closer it seems the necessary modules for bringing up the vc4 framebuffer are not included in the initramfs on ubuntu core. once they get loaded (after boot) the backlight and signal turn on. The initrd should include the modules and load them during boot. this is also required to bring any kind of bootsplash back to UC20 which is a reason all our digital signage customers currently hold back on going forward to UC20. the modules required are: ogra@ubuntu:~$ lsmod|grep vc4 vc4 290816 3 drm_kms_helper225280 3 vc4 snd_soc_core 262144 1 vc4 snd_pcm 143360 5 vc4,snd_bcm2835,snd_soc_core,snd_pcm_dmaengine drm 565248 7 gpu_sched,drm_kms_helper,v3d,vc4 the loading during boot in the journal is shown below: ogra@ubuntu:~$ sudo journalctl -b | grep vc4 Apr 01 17:23:45 ubuntu kernel: vc4-drm gpu: bound fe60.firmwarekms (ops vc4_fkms_ops [vc4]) Apr 01 17:23:45 ubuntu kernel: fb0: switching to vc4drmfb from simple Apr 01 17:23:45 ubuntu kernel: [drm] Initialized vc4 0.0.0 20140616 for gpu on minor 1 Apr 01 17:23:45 ubuntu kernel: vc4-drm gpu: fb0: vc4drmfb frame buffer device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1914608/+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 1914608] [NEW] no console during boot on UC20
Public bug reported: when booting UC20 on a Pi4 the screen backlight is completely off and no signal is produced. inspecting the boot a little closer it seems the necessary modules for bringing up the vc4 framebuffer are not included in the initramfs on ubuntu core. once they get loaded (after boot) the backlight and signal turn on. The initrd should include the modules and load them during boot. this is also required to bring any kind of bootsplash back to UC20 which is a reason all our digital signage customers currently hold back on going forward to UC20. the modules required are: ogra@ubuntu:~$ lsmod|grep vc4 vc4 290816 3 drm_kms_helper225280 3 vc4 snd_soc_core 262144 1 vc4 snd_pcm 143360 5 vc4,snd_bcm2835,snd_soc_core,snd_pcm_dmaengine drm 565248 7 gpu_sched,drm_kms_helper,v3d,vc4 the loading during boot in the journal is shown below: ogra@ubuntu:~$ sudo journalctl -b | grep vc4 Apr 01 17:23:45 ubuntu kernel: vc4-drm gpu: bound fe60.firmwarekms (ops vc4_fkms_ops [vc4]) Apr 01 17:23:45 ubuntu kernel: fb0: switching to vc4drmfb from simple Apr 01 17:23:45 ubuntu kernel: [drm] Initialized vc4 0.0.0 20140616 for gpu on minor 1 Apr 01 17:23:45 ubuntu kernel: vc4-drm gpu: fb0: vc4drmfb frame buffer device ** Affects: linux-raspi (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: linux-raspi (Ubuntu Focal) Importance: Undecided Status: New ** Affects: linux-raspi (Ubuntu Groovy) Importance: Undecided Status: New ** Affects: linux-raspi (Ubuntu Hirsute) Importance: Undecided Status: Confirmed ** Description changed: when booting UC20 on a Pi4 the screen backlight is completely off and no signal is produced. inspecting the boot a little closer it seems the necessary modules for bringing up the vc4 framebuffer are not included in the initramfs on ubuntu core. once they get loaded (after boot) the backlight and signal turn on. The initrd should include the modules and load them during boot. - this is also required to bring any kind of bootsplash back to UC20 with + this is also required to bring any kind of bootsplash back to UC20 which is a reason all our digital signage customers currently hold back on going forward to UC20. the modules required are: ogra@ubuntu:~$ lsmod|grep vc4 vc4 290816 3 drm_kms_helper225280 3 vc4 snd_soc_core 262144 1 vc4 snd_pcm 143360 5 vc4,snd_bcm2835,snd_soc_core,snd_pcm_dmaengine drm 565248 7 gpu_sched,drm_kms_helper,v3d,vc4 the loading during boot in the journal is shown below: ogra@ubuntu:~$ sudo journalctl -b | grep vc4 Apr 01 17:23:45 ubuntu kernel: vc4-drm gpu: bound fe60.firmwarekms (ops vc4_fkms_ops [vc4]) Apr 01 17:23:45 ubuntu kernel: fb0: switching to vc4drmfb from simple Apr 01 17:23:45 ubuntu kernel: [drm] Initialized vc4 0.0.0 20140616 for gpu on minor 1 Apr 01 17:23:45 ubuntu kernel: vc4-drm gpu: fb0: vc4drmfb frame buffer device -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1914608 Title: no console during boot on UC20 Status in linux-raspi package in Ubuntu: Confirmed Status in linux-raspi source package in Focal: New Status in linux-raspi source package in Groovy: New Status in linux-raspi source package in Hirsute: Confirmed Bug description: when booting UC20 on a Pi4 the screen backlight is completely off and no signal is produced. inspecting the boot a little closer it seems the necessary modules for bringing up the vc4 framebuffer are not included in the initramfs on ubuntu core. once they get loaded (after boot) the backlight and signal turn on. The initrd should include the modules and load them during boot. this is also required to bring any kind of bootsplash back to UC20 which is a reason all our digital signage customers currently hold back on going forward to UC20. the modules required are: ogra@ubuntu:~$ lsmod|grep vc4 vc4 290816 3 drm_kms_helper225280 3 vc4 snd_soc_core 262144 1 vc4 snd_pcm 143360 5 vc4,snd_bcm2835,snd_soc_core,snd_pcm_dmaengine drm 565248 7 gpu_sched,drm_kms_helper,v3d,vc4 the loading during boot in the journal is shown below: ogra@ubuntu:~$ sudo journalctl -b | grep vc4 Apr 01 17:23:45 ubuntu kernel: vc4-drm gpu: bound fe60.firmwarekms (ops vc4_fkms_ops [vc4]) Apr 01 17:23:45 ubuntu kernel: fb0: switching to vc4drmfb from simple Apr 01 17:23:45 ubuntu kernel: [drm] Initialized vc4 0.0.0 20140616 for gpu on minor 1 Apr 01 17:23:45 ubuntu kernel: vc4-drm gpu: fb0: vc4drmfb frame buffer device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-rasp
[Kernel-packages] [Bug 1883511] Re: High load from process irq/65-i2c-INT3 - kernel module tps6598x
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- 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/1883511 Title: High load from process irq/65-i2c-INT3 - kernel module tps6598x Status in linux package in Ubuntu: Confirmed Bug description: There seems to be an issue with the kernel module tps6598x which puts the CPU on a high load: https://forums.intel.com/s/question/0D50P4fWnUeSAK/nuc10i3-irq- problem As soon as the module is unloaded, cpu load is back to normal. According to a post in the link above the issue is the following: "My guess is that the IRQ resource is not correct for the PD controller causing you to see irq flood. The problem is that the ACPI device entry (the node) on this platform has 4 I2CSerialBus resources and 4 IRQ resources. The idea is that the single ACPI device entry can represent up to 4 USB PD controllers. The problem is that there is no way to know which IRQ resource belongs to which I2CSerialBus resource :-(. Andy, this is one of those multi-instantiate I2C slave devices with HID INT3515. The only solution I can think of is that we start maintaining DMI quirk table in drivers/platform/x86/i2c-multi-instantiate.c where we supply the correct i2c to irq resource mapping for every platform that has this device(s)." Description: Ubuntu 20.04 LTS Release: 20.04 Hardware: Intel NUC10i5FNK ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-37-generic 5.4.0-37.41 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-37-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: pass Date: Mon Jun 15 11:04:57 2020 InstallationDate: Installed on 2020-04-26 (49 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Intel(R) Client Systems NUC10i5FNK ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-37-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro RelatedPackageVersions: linux-restricted-modules-5.4.0-37-generic N/A linux-backports-modules-5.4.0-37-generic N/A linux-firmware1.187 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/18/2020 dmi.bios.vendor: Intel Corp. dmi.bios.version: FNCML357.0041.2020.0518.1045 dmi.board.asset.tag: Default string dmi.board.name: NUC10i5FNB dmi.board.vendor: Intel Corporation dmi.board.version: K61361-302 dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrFNCML357.0041.2020.0518.1045:bd05/18/2020:svnIntel(R)ClientSystems:pnNUC10i5FNK:pvrK61339-302:rvnIntelCorporation:rnNUC10i5FNB:rvrK61361-302:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: FN dmi.product.name: NUC10i5FNK dmi.product.sku: BXNUC10i5FNK dmi.product.version: K61339-302 dmi.sys.vendor: Intel(R) Client Systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1883511/+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 1907160] Re: intel-hid is not loaded on new Intel platform
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- 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/1907160 Title: intel-hid is not loaded on new Intel platform Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux source package in Focal: In Progress Status in linux-oem-5.10 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 Bug description: [Impact] intel-hid is not loaded on Intel Tiger Lake and Rocket Lake platforms because the existing hardware ids "INT33D5" aren't used in BIOS. [Fix] New ids "INTC1051" and "INTC1054" are to be added to intel-hid kernel driver. [Test Case] This was tested on a Rocket Lake platform and intel-hid was loaded correctly as kernel log below: [ 2.938964] input: Intel HID 5 button array as /devices/platform/INT1054:00/input/input11 [Where problems could occur] None. New IDs were added for new platforms. Previous platforms will not be affected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1907160/+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 1910211] Re: Fix the video can't output through WD19TB connected with TGL platform during cold-boot
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- 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/1910211 Title: Fix the video can't output through WD19TB connected with TGL platform during cold-boot 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 source package in Focal: Invalid Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux source package in Hirsute: In Progress Status in linux-oem-5.10 source package in Hirsute: Invalid Bug description: [Impact] After Apply the patches from https://www.spinics.net/lists/intel-gfx/msg248700.html, the TGL platform would have the failure rate(1/20) on outputting the video through WD19TB. [Fix] The patch is provided by Imre(https://gitlab.freedesktop.org/drm/intel/-/issues/2801#note_740352). If there's no lttpr in the link chain, the DRM driver wouldn't configure the transparent mode again. [Test Case] 1. Connected the WD19TB with the TGL platform and connected the external monitor on WD19TB with HDMI/Displayport. 2. Don't plug the external monitor on the TGL platform, so there's only one monitor on WD19TB. 3. Cold boot the TGL platform. 4. Check the monitor can be blinked and the video can output to the monitor. [Where problems could occur] As per Imre's comment, this may be caused by the dock. In the future if the WD19TB's firmware is updated, we may encounter the same issue again. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1910211/+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 1865402] Re: Stop using get_scalar_status command in Dell AIO uart backlight driver
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- 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/1865402 Title: Stop using get_scalar_status command in Dell AIO uart backlight driver 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-osp1 package in Ubuntu: Fix Released Status in linux 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 Status in linux source package in Focal: In Progress Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux source package in Groovy: In Progress Status in linux source package in Hirsute: In Progress Bug description: [Impact] The get_scalar_status command was provided by ODM engineer and was newly introduced to determinate whether scalar is responsible for the backlight adjustment. That guy asked the scalar vendor to add this command and the command works as expected. But there is already a command in the Dell AIO scalar UART command spec. which can do the same thing since 2015, and the newly introduced get_scalar_status command is undocumented. To prevent from introducing regression in the future and to align with what Windows uses, replace this command with get_display_mode command. [Fix] Replace get_scalar_status command with get_display_mode command. [Test] Verified on new Dell AIO platforms. [Regression Potential] Low, the command is already in the spec. since 2015. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1865402/+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 1908499] Re: udpgro.sh in net from ubuntu_kernel_selftests seems not reflecting sub-test result
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
focal' to 'verification-done-focal'. If the problem still exists, change
the tag 'verification-needed-focal' to 'verification-failed-focal'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: verification-needed-focal
--
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/1908499
Title:
udpgro.sh in net from ubuntu_kernel_selftests seems not reflecting
sub-test result
Status in ubuntu-kernel-tests:
In Progress
Status in linux package in Ubuntu:
Fix Committed
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:
Fix Committed
Status in linux-oem-5.10 source package in Focal:
Fix Committed
Status in linux-oem-5.6 source package in Focal:
In Progress
Status in linux source package in Groovy:
Fix Committed
Status in linux source package in Hirsute:
Fix Committed
Bug description:
[Impact]
In udpgro.sh, the exit value is 0 even if there are some failed sub
test cases:
$ sudo ./udpgro.sh
ipv4
no GRO
BTF debug data section '.BTF' rejected: Invalid argument (22)!
- Length: 568
Verifier analysis:
magic: 0xeb9f
version: 1
flags: 0x0
hdr_len: 24
type_off: 0
type_len: 256
str_off: 256
str_len: 288
btf_total_size: 568
[1] PTR (anon) type_id=2
[2] STRUCT xdp_md size=20 vlen=5
data type_id=3 bits_offset=0
data_end type_id=3 bits_offset=32
data_meta type_id=3 bits_offset=64
ingress_ifindex type_id=3 bits_offset=96
rx_queue_index type_id=3 bits_offset=128
[3] TYPEDEF __u32 type_id=4
[4] INT unsigned int size=4 bits_offset=0 nr_bits=32 encoding=(none)
[5] FUNC_PROTO (anon) return=6 args=(1 ctx)
[6] INT int size=4 bits_offset=0 nr_bits=32 encoding=SIGNED
[7] FUNC xdp_dummy_prog type_id=5
[8] INT char size=1 bits_offset=0 nr_bits=8 encoding=SIGNED
[9] ARRAY (anon) type_id=8 index_type_id=10 nr_elems=4
[10] INT __ARRAY_SIZE_TYPE__ size=4 bits_offset=0 nr_bits=32 encoding=(none)
[11] VAR _license type_id=9 linkage=1
[12] DATASEC license size=0 vlen=1 size == 0
./udpgso_bench_rx: poll: 0x0 expected 0x1
failed
./udpgso_bench_tx: write: Connection refused
...
multiple GRO socks
BTF debug data section '.BTF' rejected: Invalid argument (22)!
- Length: 568
Verifier analysis:
magic: 0xeb9f
version: 1
flags: 0x0
hdr_len: 24
type_off: 0
type_len: 256
str_off: 256
str_len: 288
btf_total_size: 568
[1] PTR (anon) type_id=2
[2] STRUCT xdp_md size=20 vlen=5
data type_id=3 bits_offset=0
data_end type_id=3 bits_offset=32
data_meta type_id=3 bits_offset=64
ingress_ifindex type_id=3 bits_offset=96
rx_queue_index type_id=3 bits_offset=128
[3] TYPEDEF __u32 type_id=4
[4] INT unsigned int size=4 bits_offset=0 nr_bits=32 encoding=(none)
[5] FUNC_PROTO (anon) return=6 args=(1 ctx)
[6] INT int size=4 bits_offset=0 nr_bits=32 encoding=SIGNED
[7] FUNC xdp_dummy_prog type_id=5
[8] INT char size=1 bits_offset=0 nr_bits=8 encoding=SIGNED
[9] ARRAY (anon) type_id=8 index_type_id=10 nr_elems=4
[10] INT __ARRAY_SIZE_TYPE__ size=4 bits_offset=0 nr_bits=32 encoding=(none)
[11] VAR _license type_id=9 linkage=1
[12] DATASEC license size=0 vlen=1 size == 0
./udpgso_bench_rx: poll: 0x0 expected 0x1
./udpgso_bench_rx: poll: 0x0 expected 0x1
failed
$ echo $?
0
[Fix]
* 3503ee6c0bec5f ("selftests: fix the return value for UDP GRO test")
We have this test since Focal.
This patch can be cherry-picked into all the affected kernels.
[Test]
Run this test with:
sudo ./udpgro.sh
And check its final return value with:
echo $?
If there is any failure, the return value should not be 0.
[Where problems could occur]
If this fix is incorrect it might affect the test execution, but it
should be fine as this is just affecting the test tool. Also, with
this patch, we are expecting to see this test case to fail until
bug 1908501 got fixed.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1908499/+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 1911359] Re: Boot fails: failed to validate module [nls_iso8859_1] BTF: -22
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- 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/1911359 Title: Boot fails: failed to validate module [nls_iso8859_1] BTF: -22 Status in linux package in Ubuntu: Fix Committed Bug description: I just updated to an unstable kernel build from the kernels team Repo it´s the 5.11-2.3 package (5.11 RC3) The mount of /dev/boot fails with a message: IO charset iso8859-1 not found this is probably due to the kernel being unable to load the nls_iso8859-1 module. I see multiple messages with BPF:No data and for the nls_iso8859-1 module a message: failed to validate module [nls_iso8859_1] BTF: -22 this is probably introduced by this patch: https://lkml.org/lkml/2020/11/6/1143 I don´t undestand what BTF validation is and whether this is an issue with linux 5.11-rc3 or with how the kernel modules are packaged in Ubuntu. My machine is a Renoir (zen2) based Acer Laptop running in UEFI mode, with a fat32 /boot partition and a ext4 / root partition. The root partition gets mounted, but once the /boot should be mounted, this fails with the mentioned error.. Other modules seem to load fine, things like "amdgpu" are already loaded! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1911359/+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 1912033] Re: Thinkpad - add palm sensor support needed for WWAN
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- 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/1912033 Title: Thinkpad - add palm sensor support needed for WWAN Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.10 source package in Focal: Fix Committed Bug description: [Impact] Add new palm sensor supports to Lenovo Thinkpad systems [Fix] thinkpad_acpi is updated to check palm sensor presence and its events [Test] Tested on Thinkpad systems [Where problems could occur] Low risks. Only thinkpad systems are affected. Also thinkpad systems without palm sensor and without TP_HKEY_EV_PALM_DETECTED & TP_HKEY_EV_PALM_UNDETECTED events won't be affected either. There can an issue as discussed in commit log of "thinkpad_acpi: Add palm sensor support" Note: On some platforms, because of an issue in the HW implementation, the palm sensor presence may be incorrectly advertised as always enabled even if a palm sensor is not present. The palm sensor is intended for WWAN transmission power control and should be available and correct on all WWAN enabled systems. It is not recommended to use this interface for other use cases. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1912033/+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 1912803] Re: switch to an autogenerated nvidia series based core via dkms-versions
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- 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/1912803 Title: switch to an autogenerated nvidia series based core via dkms-versions Status in linux package in Ubuntu: In Progress Status in linux-restricted-modules package in Ubuntu: In Progress Bug description: Switch the linux-restricted-modules payload to an autogenerated core based on the contents of the debian/dkms-versions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912803/+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 1913263] Re: Remove scary stack trace from Realtek WiFi driver
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- 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/1913263 Title: Remove scary stack trace from Realtek WiFi driver Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.10 package in Ubuntu: Won't Fix Status in linux source package in Focal: Confirmed Status in linux-oem-5.10 source package in Focal: Fix Committed Status in linux source package in Groovy: Confirmed Status in linux-oem-5.10 source package in Groovy: Won't Fix Bug description: [Impact] Scary stack trace spamming by Realtek WiFi driver. [Fix] The issue is actually harmless, so replace the WARN macro with dbg macro. [Test] No more scary stack trace in dmesg after applying the patch. [Where problems could occur] This patch doesn't bring any behavior change, so there won't be any regression risk. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1913263/+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 1913520] Re: Restore palm ejection on multi-input devices
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- 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/1913520 Title: Restore palm ejection on multi-input devices Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.10 package in Ubuntu: Won't Fix Status in linux source package in Focal: Won't Fix Status in linux-oem-5.10 source package in Focal: Fix Committed Status in linux source package in Groovy: In Progress Status in linux-oem-5.10 source package in Groovy: Won't Fix Bug description: [Impact] Palm ejection stops working on Elan and Synaptics touchpads with pointstick. [Fix] Re-apply "confidence" quirk on those devices. [Test] Move the palm on touchpad, cursor moves too. With the fix applied, moving palm on touchpad won't move the cursor and won't generate click events. [Where problems could occur] Not that I can think of. Originally these touchpads are working fine with palm ejection, it's just overlooked when enabling pointsticks. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1913520/+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 1913682] Re: Fix no screen show on display after S3 on CML-R
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- 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/1913682 Title: Fix no screen show on display after S3 on CML-R Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.10 package in Ubuntu: New Status in linux source package in Focal: Invalid Status in linux-oem-5.10 source package in Focal: Fix Committed Status in linux source package in Groovy: Invalid Status in linux-oem-5.10 source package in Groovy: New Status in linux source package in Hirsute: In Progress Status in linux-oem-5.10 source package in Hirsute: New Bug description: [Impact] On CML-R, after S3, No screen show on all three connector(3*DP). [Fix] The patch is got from https://patchwork.freedesktop.org/patch/416162/. For Legacy S3 suspend/resume GEN9 BC needs to enable and setup TGP PCH. [Test Case] 1. Connected the monitor on one of 3*DP on CML-R. 2. Suspend&resume the machine. 3. Check the monitor can output something. [Where problems could occur] Just Enable the hpd detection in IRQ installer and during suspend&resume. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1913682/+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 1869763] Re: Huawei Kunpeng 920 arm64 machine KVM guest frequently crash
** Changed in: kunpeng920 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/1869763 Title: Huawei Kunpeng 920 arm64 machine KVM guest frequently crash Status in kunpeng920: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: Hardware spec: 64 core 64 G ram arm64 OS & kernel version: Ubuntu 18.04.4 LTS, 4.15.0-91-generic `virt-host-validate qemu` output: QEMU: Checking if device /dev/kvm exists : PASS QEMU: Checking if device /dev/kvm is accessible : PASS QEMU: Checking if device /dev/vhost-net exists : PASS QEMU: Checking if device /dev/net/tun exists : PASS QEMU: Checking for cgroup 'memory' controller support : PASS QEMU: Checking for cgroup 'memory' controller mount-point : PASS QEMU: Checking for cgroup 'cpu' controller support : PASS QEMU: Checking for cgroup 'cpu' controller mount-point : PASS QEMU: Checking for cgroup 'cpuacct' controller support : PASS QEMU: Checking for cgroup 'cpuacct' controller mount-point : PASS QEMU: Checking for cgroup 'cpuset' controller support : PASS QEMU: Checking for cgroup 'cpuset' controller mount-point : PASS QEMU: Checking for cgroup 'devices' controller support : PASS QEMU: Checking for cgroup 'devices' controller mount-point : PASS QEMU: Checking for cgroup 'blkio' controller support : PASS QEMU: Checking for cgroup 'blkio' controller mount-point : PASS WARN (Unknown if this platform has IOMMU support) libvirt version: 4.0.0-1ubuntu8.14 qemu version: 1:2.11+dfsg-1ubuntu7.23arm64 guest vm kernel version: 4.15.0-64-generic aarch64 dmesg log: kvm [49132]: Unexpected L2 read permission error libvirt log: ubuntu libvirtd: 2020-03-20 03:04.474+: 42934: warning : qemuDomainObjTaint:5602 : Domain id=38 name='vm-157' uuid=3d447d79-c2a1-4351-b607-6698a2cd6c5f is tainted: host-cpu When "Unexpected L2 read permission error" this error occured, one of guest machines will become "paused" state, need to `virsh reset PAUSED_VM_NAME` to reset then start it. Those guest vm hang/crash occured very frequently, sometimes several times per hour. To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1869763/+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 1913520] Re: Restore palm ejection on multi-input devices
** Changed in: linux (Ubuntu Groovy) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1913520 Title: Restore palm ejection on multi-input devices Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.10 package in Ubuntu: Won't Fix Status in linux source package in Focal: Won't Fix Status in linux-oem-5.10 source package in Focal: Fix Committed Status in linux source package in Groovy: In Progress Status in linux-oem-5.10 source package in Groovy: Won't Fix Bug description: [Impact] Palm ejection stops working on Elan and Synaptics touchpads with pointstick. [Fix] Re-apply "confidence" quirk on those devices. [Test] Move the palm on touchpad, cursor moves too. With the fix applied, moving palm on touchpad won't move the cursor and won't generate click events. [Where problems could occur] Not that I can think of. Originally these touchpads are working fine with palm ejection, it's just overlooked when enabling pointsticks. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1913520/+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 1914604] Re: Add support for new Realtek ethernet NIC
** Tags added: oem-priority originate-from-1913677 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/1914604 Title: Add support for new Realtek ethernet NIC Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.10 package in Ubuntu: Won't Fix Status in linux source package in Focal: Won't Fix Status in linux-oem-5.10 source package in Focal: Confirmed Bug description: [Impact] New Realtek ethernet NIC doesn't work. [Fix] Add support for new Realtek NIC. [Test] With the patch applied, network interface is created, and can reach 1G speed. [Where problems could occur] This patch doesn't bring any functional change, and it doesn't touch any older hardwares. So there's no chance to bring regression. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1914604/+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 1869763] 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 1869763 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1869763 Title: Huawei Kunpeng 920 arm64 machine KVM guest frequently crash Status in kunpeng920: New Status in linux package in Ubuntu: Incomplete Bug description: Hardware spec: 64 core 64 G ram arm64 OS & kernel version: Ubuntu 18.04.4 LTS, 4.15.0-91-generic `virt-host-validate qemu` output: QEMU: Checking if device /dev/kvm exists : PASS QEMU: Checking if device /dev/kvm is accessible : PASS QEMU: Checking if device /dev/vhost-net exists : PASS QEMU: Checking if device /dev/net/tun exists : PASS QEMU: Checking for cgroup 'memory' controller support : PASS QEMU: Checking for cgroup 'memory' controller mount-point : PASS QEMU: Checking for cgroup 'cpu' controller support : PASS QEMU: Checking for cgroup 'cpu' controller mount-point : PASS QEMU: Checking for cgroup 'cpuacct' controller support : PASS QEMU: Checking for cgroup 'cpuacct' controller mount-point : PASS QEMU: Checking for cgroup 'cpuset' controller support : PASS QEMU: Checking for cgroup 'cpuset' controller mount-point : PASS QEMU: Checking for cgroup 'devices' controller support : PASS QEMU: Checking for cgroup 'devices' controller mount-point : PASS QEMU: Checking for cgroup 'blkio' controller support : PASS QEMU: Checking for cgroup 'blkio' controller mount-point : PASS WARN (Unknown if this platform has IOMMU support) libvirt version: 4.0.0-1ubuntu8.14 qemu version: 1:2.11+dfsg-1ubuntu7.23arm64 guest vm kernel version: 4.15.0-64-generic aarch64 dmesg log: kvm [49132]: Unexpected L2 read permission error libvirt log: ubuntu libvirtd: 2020-03-20 03:04.474+: 42934: warning : qemuDomainObjTaint:5602 : Domain id=38 name='vm-157' uuid=3d447d79-c2a1-4351-b607-6698a2cd6c5f is tainted: host-cpu When "Unexpected L2 read permission error" this error occured, one of guest machines will become "paused" state, need to `virsh reset PAUSED_VM_NAME` to reset then start it. Those guest vm hang/crash occured very frequently, sometimes several times per hour. To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1869763/+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 1914604] [NEW] Add support for new Realtek ethernet NIC
Public bug reported: [Impact] New Realtek ethernet NIC doesn't work. [Fix] Add support for new Realtek NIC. [Test] With the patch applied, network interface is created, and can reach 1G speed. [Where problems could occur] This patch doesn't bring any functional change, and it doesn't touch any older hardwares. So there's no chance to bring regression. ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: High Status: Confirmed ** Affects: linux-oem-5.10 (Ubuntu) Importance: Undecided Status: Won't Fix ** Affects: linux (Ubuntu Focal) Importance: Undecided Status: Won't Fix ** Affects: linux-oem-5.10 (Ubuntu Focal) Importance: High Status: Confirmed ** Tags: oem-priority originate-from-1913677 stella ** Also affects: linux-oem-5.10 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-oem-5.10 (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Focal) Status: New => Won't Fix ** Changed in: linux-oem-5.10 (Ubuntu) Status: New => Won't Fix ** Changed in: linux-oem-5.10 (Ubuntu Focal) Status: New => Confirmed ** Changed in: linux-oem-5.10 (Ubuntu Focal) Importance: Undecided => High ** Changed in: linux (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1914604 Title: Add support for new Realtek ethernet NIC Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.10 package in Ubuntu: Won't Fix Status in linux source package in Focal: Won't Fix Status in linux-oem-5.10 source package in Focal: Confirmed Bug description: [Impact] New Realtek ethernet NIC doesn't work. [Fix] Add support for new Realtek NIC. [Test] With the patch applied, network interface is created, and can reach 1G speed. [Where problems could occur] This patch doesn't bring any functional change, and it doesn't touch any older hardwares. So there's no chance to bring regression. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1914604/+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 1903048] Re: [SRU] Bluetooth won't activate on the pi 400
Thanks Dave, the updated patches have been uploaded now, removing the block-proposed ** Tags removed: block-proposed -- 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/1903048 Title: [SRU] Bluetooth won't activate on the pi 400 Status in bluez package in Ubuntu: Triaged Status in bluez source package in Groovy: Fix Released Status in bluez source package in Hirsute: Triaged Bug description: [Impact] Without these patches, Bluetooth is inoperable on the recently released Raspberry Pi 400. [Test Case] * Boot the Ubuntu Desktop for Pi image on a Pi 400. * Start the Settings application and switch to the Bluetooth tab * Verify that Bluetooth is not enabled and attempting to activate it fails * Enable the -proposed repository for the release (groovy) * sudo apt update * sudo apt install bluez * sudo reboot * Start the Settings application and switch to the Bluetooth tab * Verify that Bluetooth is active and that Bluetooth devices (e.g. mice, mobile phones, headphones, etc.) can connect and operate correctly [Regression Potential] Extremely low (on groovy in particular, this has the same version of bluez as hirsute). The only significant risk is to non-Pi platforms or dongles which also use the Broadcom 43xx (or Cypress 305) chips for Bluetooth which might be inadvertently affected by these patches. [Original Description] The new Pi 400 has a slightly different Wifi/BT chip to the Pi4. Whilst wifi works happily, Bluetooth fails to operate. This doesn't appear to be an issue with either the firmware (the latest versions from upstream Raspbian have been tried), or the kernel (a known-good raspi kernel has been tested under Ubuntu), but with Bluez itself. Specifically, tracing the initialization with btmon on Raspbian and Ubuntu, the stack consistently fails when attempting to "Set Default PHY" on the latter. Curiously, under Ubuntu the adapter also appears to lack a MAC address. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1903048/+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 1869763] Re: Huawei Kunpeng 920 arm64 machine KVM guest frequently crash
https://lists.cs.columbia.edu/pipermail/kvmarm/2020-September/042543.html this patch will slove this bug。 Can you test it？ ** Changed in: linux (Ubuntu) Status: Expired => New ** Also affects: kunpeng920 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/1869763 Title: Huawei Kunpeng 920 arm64 machine KVM guest frequently crash Status in kunpeng920: New Status in linux package in Ubuntu: New Bug description: Hardware spec: 64 core 64 G ram arm64 OS & kernel version: Ubuntu 18.04.4 LTS, 4.15.0-91-generic `virt-host-validate qemu` output: QEMU: Checking if device /dev/kvm exists : PASS QEMU: Checking if device /dev/kvm is accessible : PASS QEMU: Checking if device /dev/vhost-net exists : PASS QEMU: Checking if device /dev/net/tun exists : PASS QEMU: Checking for cgroup 'memory' controller support : PASS QEMU: Checking for cgroup 'memory' controller mount-point : PASS QEMU: Checking for cgroup 'cpu' controller support : PASS QEMU: Checking for cgroup 'cpu' controller mount-point : PASS QEMU: Checking for cgroup 'cpuacct' controller support : PASS QEMU: Checking for cgroup 'cpuacct' controller mount-point : PASS QEMU: Checking for cgroup 'cpuset' controller support : PASS QEMU: Checking for cgroup 'cpuset' controller mount-point : PASS QEMU: Checking for cgroup 'devices' controller support : PASS QEMU: Checking for cgroup 'devices' controller mount-point : PASS QEMU: Checking for cgroup 'blkio' controller support : PASS QEMU: Checking for cgroup 'blkio' controller mount-point : PASS WARN (Unknown if this platform has IOMMU support) libvirt version: 4.0.0-1ubuntu8.14 qemu version: 1:2.11+dfsg-1ubuntu7.23arm64 guest vm kernel version: 4.15.0-64-generic aarch64 dmesg log: kvm [49132]: Unexpected L2 read permission error libvirt log: ubuntu libvirtd: 2020-03-20 03:04.474+: 42934: warning : qemuDomainObjTaint:5602 : Domain id=38 name='vm-157' uuid=3d447d79-c2a1-4351-b607-6698a2cd6c5f is tainted: host-cpu When "Unexpected L2 read permission error" this error occured, one of guest machines will become "paused" state, need to `virsh reset PAUSED_VM_NAME` to reset then start it. Those guest vm hang/crash occured very frequently, sometimes several times per hour. To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1869763/+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 1914279] Re: linux from security may force reboots without complete dkms modules
adding breaks on linux-meta in -security, on dkms package versions that are in -updates only, would result in the kernel being held back and not get autoinstalled. -- 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/1914279 Title: linux from security may force reboots without complete dkms modules Status in apt package in Ubuntu: Invalid Status in dkms package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Status in linux-meta package in Ubuntu: New Status in unattended-upgrades package in Ubuntu: Invalid Status in update-manager package in Ubuntu: Invalid Bug description: Whilst discussing https://discourse.ubuntu.com/t/improvements-for-hardware-support-in- ubuntu-desktop-installation-media/20606 We have noticed a reference to somebody not having working backport- iwlwifi-dkms, whilst SRU of that happened before the v5.4 -> v5.8 switch. However, kernel meta switch was pushed to security pocket, but the dkms modules are all in -updates only. This may result in people automatically installing the new kernel with unatanded upgrades; dkms modules failing to build; and a reboot required flag left on disk. At this point launching update manager will not offer to install dkms modules from updates, and will guide the users to reboot. which will then cause them to boot the new kernel without the dkms modules that might be providing networking for them. Should dkms modules SRUs always getting published into -security pocket, as well as the -updates pocket? Should linux maintainer scripts prevent touching reboot required flag if any dkms modules fail to build? Should apt / unattanded-upgrades / update-manager always update dkms modules with kernels? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1914279/+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 1914279] Re: linux from security may force reboots without complete dkms modules
@seth-arnold @mdeslaur Mostly the dkms packages ship source code only, without strict binary deps on packages/libraries from updates. It should be safe to publish them into -security pocket. It is correct that there were a few bugs with dkms modules, which are now resolved in -updates. But one can still upgrade from offline installation using 20.04.1 media to something broken. -- 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/1914279 Title: linux from security may force reboots without complete dkms modules Status in apt package in Ubuntu: Invalid Status in dkms package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Status in linux-meta package in Ubuntu: New Status in unattended-upgrades package in Ubuntu: Invalid Status in update-manager package in Ubuntu: Invalid Bug description: Whilst discussing https://discourse.ubuntu.com/t/improvements-for-hardware-support-in- ubuntu-desktop-installation-media/20606 We have noticed a reference to somebody not having working backport- iwlwifi-dkms, whilst SRU of that happened before the v5.4 -> v5.8 switch. However, kernel meta switch was pushed to security pocket, but the dkms modules are all in -updates only. This may result in people automatically installing the new kernel with unatanded upgrades; dkms modules failing to build; and a reboot required flag left on disk. At this point launching update manager will not offer to install dkms modules from updates, and will guide the users to reboot. which will then cause them to boot the new kernel without the dkms modules that might be providing networking for them. Should dkms modules SRUs always getting published into -security pocket, as well as the -updates pocket? Should linux maintainer scripts prevent touching reboot required flag if any dkms modules fail to build? Should apt / unattanded-upgrades / update-manager always update dkms modules with kernels? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1914279/+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 1899132] Re: complete freeze with focal 20.04
Thanks, can I test the oem kernel in 20.10 too? There is only a dummy package in the groovy repository. I recently upgraded from 20.04 to 20.10 in the hope that something will improve. Otherwise I need to reinstall :/ -- 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/1899132 Title: complete freeze with focal 20.04 Status in linux package in Ubuntu: Confirmed Bug description: Hi, my notebook Dell G3 3590 has xubuntu 20.04 installed. The notebook is freezing randomly at boot, with the boot logo. At lock screen or a few minutes after login. I can not reboot,, not even with Magic SysRq key. Could not found a specific error with that caused this in the logs. Tested with nouveau driver and the nvidia driver (450, tested) from the software & updates panel. Logs are captured after a system freeze. Since nothing reacts anymore, I have to restart the system to capture the logs. After the dell community forum, I am not the only one with this problem. --- The workaround with boot option "snd_hda_intel.dmic_detect=0" from the dell forum is working, but there is no microphone! pavucontrol: Internal microphone is not working (no input) and an external microphone is not recognized (one entry is listed as unplugged, even if connected ). --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: hannibal 2093 F pulseaudio /dev/snd/controlC0: hannibal 2093 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-13 (148 days ago) InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. G3 3590 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-49-generic root=/dev/mapper/vgxubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-49.53-generic 5.4.65 RelatedPackageVersions: linux-restricted-modules-5.4.0-49-generic N/A linux-backports-modules-5.4.0-49-generic N/A linux-firmware1.187.3 Tags: focal Uname: Linux 5.4.0-49-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: 08/28/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.1 dmi.board.name: 0CVWRM dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.1:bd08/28/2019:svnDellInc.:pnG33590:pvr:rvnDellInc.:rn0CVWRM:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: GSeries dmi.product.name: G3 3590 dmi.product.sku: 0949 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899132/+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 1908150] Re: Groovy update: upstream stable patchset 2020-12-14
** Also affects: linux-aws (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1908150 Title: Groovy update: upstream stable patchset 2020-12-14 Status in linux package in Ubuntu: Confirmed Status in linux-aws package in Ubuntu: New Status in linux source package in Groovy: Fix Committed Status in linux-aws source package in Groovy: New Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2020-12-14 Ported from the following upstream stable releases: v5.4.75, v5.9.5 from git://git.kernel.org/ xen/events: avoid removing an event channel while handling it xen/events: add a proper barrier to 2-level uevent unmasking xen/events: fix race in evtchn_fifo_unmask() xen/events: add a new "late EOI" evtchn framework xen/blkback: use lateeoi irq binding xen/netback: use lateeoi irq binding xen/scsiback: use lateeoi irq binding xen/pvcallsback: use lateeoi irq binding xen/pciback: use lateeoi irq binding xen/events: switch user event channels to lateeoi model xen/events: use a common cpu hotplug hook for event channels xen/events: defer eoi in case of excessive number of events xen/events: block rogue events for some time firmware: arm_scmi: Fix ARCH_COLD_RESET firmware: arm_scmi: Expand SMC/HVC message pool to more than one tee: client UUID: Skip REE kernel login method as well firmware: arm_scmi: Add missing Rx size re-initialisation x86/unwind/orc: Fix inactive tasks with stack pointer in %sp on GCC 10 compiled kernels x86/alternative: Don't call text_poke() in lazy TLB mode ionic: no rx flush in deinit RDMA/mlx5: Fix devlink deadlock on net namespace deletion mlxsw: core: Fix use-after-free in mlxsw_emad_trans_finish() tracing, synthetic events: Replace buggy strcat() with seq_buf operations afs: Fix a use after free in afs_xattr_get_acl() afs: Fix afs_launder_page to not clear PG_writeback RDMA/qedr: Fix memory leak in iWARP CM ata: sata_nv: Fix retrieving of active qcs arm64: efi: increase EFI PE/COFF header padding to 64 KB afs: Fix to take ref on page when PG_private is set afs: Fix page leak on afs_write_begin() failure afs: Fix where page->private is set during write afs: Wrap page->private manipulations in inline functions afs: Alter dirty range encoding in page->private mm: add thp_order mm: add thp_size afs: Fix afs_invalidatepage to adjust the dirty region afs: Fix dirty-region encoding on ppc32 with 64K pages interconnect: qcom: sdm845: Enable keepalive for the MM1 BCM usb: host: ehci-tegra: Fix error handling in tegra_ehci_probe() futex: Fix incorrect should_fail_futex() handling powerpc/vmemmap: Fix memory leak with vmemmap list allocation failures. powerpc/powernv/smp: Fix spurious DBG() warning RDMA/core: Change how failing destroy is handled during uobj abort f2fs: allocate proper size memory for zstd decompress powerpc/watchpoint/ptrace: Fix SETHWDEBUG when CONFIG_HAVE_HW_BREAKPOINT=N UBUNTU: [Config] update config for ARCH_WANT_IRQS_OFF_ACTIVATE_MM mm: fix exec activate_mm vs TLB shootdown and lazy tlb switching race powerpc: select ARCH_WANT_IRQS_OFF_ACTIVATE_MM sparc64: remove mm_cpumask clearing to fix kthread_use_mm race f2fs: add trace exit in exception path f2fs: do sanity check on zoned block device path f2fs: fix uninit-value in f2fs_lookup f2fs: fix to check segment boundary during SIT page readahead s390/startup: avoid save_area_sync overflow f2fs: compress: fix to disallow enabling compress on non-empty file um: change sigio_spinlock to a mutex f2fs: handle errors of f2fs_get_meta_page_nofail afs: Don't assert on unpurgeable server records powerpc/64s: handle ISA v3.1 local copy-paste context switches ARM: 8997/2: hw_breakpoint: Handle inexact watchpoint addresses NFS4: Fix oops when copy_file_range is attempted with NFS4.0 source xfs: Set xfs_buf type flag when growing summary/bitmap files xfs: Set xfs_buf's b_ops member when zeroing bitmap/summary files xfs: log new intent items created as part of finishing recovered intent items power: supply: bq27xxx: report "not charging" on all types xfs: change the order in which child and parent defer ops are finished xfs: fix realtime bitmap/summary file truncation when growing rt volume ath10k: fix retry packets update in station
[Kernel-packages] [Bug 1911235] Re: Groovy update: upstream stable patchset 2021-01-12
** Also affects: linux-aws (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1911235 Title: Groovy update: upstream stable patchset 2021-01-12 Status in linux package in Ubuntu: Confirmed Status in linux-aws package in Ubuntu: New Status in linux-gcp package in Ubuntu: New Status in linux-raspi package in Ubuntu: New Status in linux-riscv package in Ubuntu: New Status in linux source package in Groovy: Fix Committed Status in linux-aws source package in Groovy: New Status in linux-gcp source package in Groovy: Fix Committed Status in linux-raspi source package in Groovy: Fix Committed Status in linux-riscv source package in Groovy: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2021-01-12 Ported from the following upstream stable releases: v5.4.79, v5.9.10 v5.4.80, v5.9.11 v5.4.81, v5.9.12 v5.4.82, v5.9.13 v5.4.83, v5.9.14 from git://git.kernel.org/ powerpc: Only include kup-radix.h for 64-bit Book3S leds: lm3697: Fix out-of-bound access Input: sunkbd - avoid use-after-free in teardown paths mac80211: always wind down STA state can: proc: can_remove_proc(): silence remove_proc_entry warning powerpc/smp: Call rcu_cpu_starting() earlier KVM: x86: clflushopt should be treated as a no-op by emulation ACPI: GED: fix -Wformat net: lantiq: Add locking for TX DMA channel UBUNTU: upstream stable to v5.4.79, v5.9.10 ah6: fix error return code in ah6_input() atm: nicstar: Unmap DMA on send error bnxt_en: read EEPROM A2h address using page 0 devlink: Add missing genlmsg_cancel() in devlink_nl_sb_port_pool_fill() enetc: Workaround for MDIO register access issue Exempt multicast addresses from five-second neighbor lifetime inet_diag: Fix error path to cancel the meseage in inet_req_diag_fill() ipv6: Fix error path to cancel the meseage lan743x: fix issue causing intermittent kernel log warnings lan743x: prevent entire kernel HANG on open, for some platforms mlxsw: core: Use variable timeout for EMAD retries net: b44: fix error return code in b44_init_one() net: bridge: add missing counters to ndo_get_stats64 callback netdevsim: set .owner to THIS_MODULE net: dsa: mv88e6xxx: Avoid VTU corruption on 6097 net: ethernet: mtk-star-emac: fix error return code in mtk_star_enable() net: ethernet: mtk-star-emac: return ok when xmit drops net: ethernet: ti: am65-cpts: update ret when ptp_clock is ERROR net: ethernet: ti: cpsw: fix cpts irq after suspend net: ethernet: ti: cpsw: fix error return code in cpsw_probe() net: ftgmac100: Fix crash when removing driver net: Have netpoll bring-up DSA management interface net: ipa: lock when freeing transaction netlabel: fix our progress tracking in netlbl_unlabel_staticlist() netlabel: fix an uninitialized warning in netlbl_unlabel_staticlist() net: lantiq: Wait for the GPHY firmware to be ready net/mlx4_core: Fix init_hca fields offset net/mlx5e: Fix refcount leak on kTLS RX resync net/ncsi: Fix netlink registration net: phy: mscc: remove non-MACSec compatible phy net: qualcomm: rmnet: Fix incorrect receive packet handling during cleanup net/smc: fix direct access to ib_gid_addr->ndev in smc_ib_determine_gid() net: stmmac: Use rtnl_lock/unlock on netif_set_real_num_rx_queues() call net/tls: fix corrupted data in recvmsg net: x25: Increase refcnt of "struct x25_neigh" in x25_rx_call_request page_frag: Recover from memory pressure qed: fix error return code in qed_iwarp_ll2_start() qed: fix ILT configuration of SRC block qlcnic: fix error return code in qlcnic_83xx_restart_hw() sctp: change to hold/put transport for proto_unreach_timer tcp: only postpone PROBE_RTT if RTT is < current min_rtt estimate vsock: forward all packets to the host when no H2G is registered net/mlx5e: Fix check if netdev is bond slave net/mlx5: Add handling of port type in rule deletion net/mlx5: Clear bw_share upon VF disable net/mlx5: Disable QoS when min_rates on all VFs are zero PM: runtime: Add pm_runtime_resume_and_get to deal with usage counter net: fec: Fix reference count leak in fec series ops net/tls: Fix wrong record sn in async mode of device resync net: usb: qmi_wwan: Se
[Kernel-packages] [Bug 1911476] Re: Groovy update: upstream stable patchset 2021-01-13
** Also affects: linux-aws (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1911476 Title: Groovy update: upstream stable patchset 2021-01-13 Status in linux package in Ubuntu: Confirmed Status in linux-aws package in Ubuntu: New Status in linux-gcp package in Ubuntu: New Status in linux-kvm package in Ubuntu: New Status in linux-raspi package in Ubuntu: New Status in linux-riscv package in Ubuntu: New Status in linux source package in Groovy: Fix Committed Status in linux-aws source package in Groovy: New Status in linux-gcp source package in Groovy: Fix Committed Status in linux-kvm source package in Groovy: New Status in linux-raspi source package in Groovy: Fix Committed Status in linux-riscv source package in Groovy: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2021-01-13 Ported from the following upstream stable releases: v5.4.84, v5.9.15, v5.4.85, v5.9.16 from git://git.kernel.org/ Kbuild: do not emit debug info for assembly with LLVM_IAS=1 mm/zsmalloc.c: drop ZSMALLOC_PGTABLE_MAPPING UBUNTU: [Config] updateconfigs for ZSMALLOC_PGTABLE_MAPPING kprobes: Remove NMI context check kprobes: Tell lockdep about kprobe nesting ASoC: Intel: bytcr_rt5640: Fix HP Pavilion x2 Detachable quirks tools/bootconfig: Fix to check the write failure correctly net, xsk: Avoid taking multiple skbuff references bpftool: Fix error return value in build_btf_type_table vhost-vdpa: fix page pinning leakage in error path (rework) powerpc/64s: Fix hash ISA v3.0 TLBIEL instruction generation batman-adv: Consider fragmentation for needed_headroom batman-adv: Reserve needed_*room for fragments batman-adv: Don't always reallocate the fragmentation skb head ipvs: fix possible memory leak in ip_vs_control_net_init ibmvnic: handle inconsistent login with reset ibmvnic: stop free_all_rwi on failed reset ibmvnic: avoid memset null scrq msgs ibmvnic: delay next reset if hard reset fails ibmvnic: track pending login ibmvnic: send_login should check for crq errors ibmvnic: reduce wait for completion time drm/rockchip: Avoid uninitialized use of endpoint id in LVDS drm/panel: sony-acx565akm: Fix race condition in probe can: m_can: tcan4x5x_can_probe(): fix error path: remove erroneous clk_disable_unprepare() can: sja1000: sja1000_err(): don't count arbitration lose as an error can: sun4i_can: sun4i_can_err(): don't count arbitration lose as an error can: c_can: c_can_power_up(): fix error handling can: kvaser_pciefd: kvaser_pciefd_open(): fix error handling samples/ftrace: Mark my_tramp[12]? global scsi: storvsc: Fix error return in storvsc_probe() net: broadcom CNIC: requires MMU iwlwifi: pcie: invert values of NO_160 device config entries perf/x86/intel: Fix a warning on x86_pmu_stop() with large PEBS zlib: export S390 symbols for zlib modules phy: usb: Fix incorrect clearing of tca_drv_sel bit in SETUP reg for 7211 arm64: dts: rockchip: Remove system-power-controller from pmic on Odroid Go Advance iwlwifi: pcie: limit memory read spin time arm64: dts: rockchip: Assign a fixed index to mmc devices on rk3399 boards. arm64: dts: rockchip: Reorder LED triggers from mmc devices on rk3399-roc-pc. iwlwifi: sta: set max HE max A-MPDU according to HE capa iwlwifi: pcie: set LTR to avoid completion timeout iwlwifi: mvm: fix kernel panic in case of assert during CSA powerpc: Drop -me200 addition to build flags arm64: dts: broadcom: clear the warnings caused by empty dma-ranges ARC: stack unwinding: don't assume non-current task is sleeping scsi: ufs: Fix unexpected values from ufshcd_read_desc_param() scsi: ufs: Make sure clk scaling happens only when HBA is runtime ACTIVE interconnect: qcom: msm8916: Remove rpm-ids from non-RPM nodes interconnect: qcom: qcs404: Remove GPU and display RPM IDs ibmvnic: skip tx timeout reset while in resetting irqchip/gic-v3-its: Unconditionally save/restore the ITS state on suspend drm/exynos: depend on COMMON_CLK to fix compile tests spi: spi-nxp-fspi: fix fspi panic by unexpected interrupts arm-smmu-qcom: Ensure the qcom_scm driver has finished probing btrfs: do nofs allocations when adding and removing qgroup relations btrfs: fix lockdep splat when enabli
[Kernel-packages] [Bug 1911331] Re: Bionic update: upstream stable patchset 2021-01-12
** Also affects: linux-aws (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-snapdragon in Ubuntu. https://bugs.launchpad.net/bugs/1911331 Title: Bionic update: upstream stable patchset 2021-01-12 Status in linux package in Ubuntu: Confirmed Status in linux-aws package in Ubuntu: New Status in linux-raspi2 package in Ubuntu: New Status in linux-snapdragon package in Ubuntu: New Status in linux source package in Bionic: Fix Committed Status in linux-aws source package in Bionic: New Status in linux-raspi2 source package in Bionic: Fix Committed Status in linux-snapdragon source package in Bionic: New Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2021-01-12 Ported from the following upstream stable releases: v4.14.213, v4.19.164 from git://git.kernel.org/ spi: bcm2835aux: Fix use-after-free on unbind spi: bcm2835aux: Restore err assignment in bcm2835aux_spi_probe iwlwifi: pcie: limit memory read spin time arm64: dts: rockchip: Assign a fixed index to mmc devices on rk3399 boards. iwlwifi: mvm: fix kernel panic in case of assert during CSA ARC: stack unwinding: don't assume non-current task is sleeping scsi: ufs: Make sure clk scaling happens only when HBA is runtime ACTIVE soc: fsl: dpio: Get the cpumask through cpumask_of(cpu) platform/x86: acer-wmi: add automatic keyboard background light toggle key as KEY_LIGHTS_TOGGLE Input: cm109 - do not stomp on control URB Input: i8042 - add Acer laptops to the i8042 reset list pinctrl: amd: remove debounce filter setting in IRQ type setting kbuild: avoid static_assert for genksyms scsi: be2iscsi: Revert "Fix a theoretical leak in beiscsi_create_eqs()" x86/mm/mem_encrypt: Fix definition of PMD_FLAGS_DEC_WP PCI: qcom: Add missing reset for ipq806x net: stmmac: free tx skb buffer in stmmac_resume() tcp: fix cwnd-limited bug for TSO deferral where we send nothing net/mlx4_en: Avoid scheduling restart task if it is already running net/mlx4_en: Handle TX error CQE net: stmmac: delete the eee_ctrl_timer after napi disabled net: stmmac: dwmac-meson8b: fix mask definition of the m250_sel mux net: bridge: vlan: fix error return code in __vlan_add() mac80211: mesh: fix mesh_pathtbl_init() error path USB: dummy-hcd: Fix uninitialized array use in init() USB: add RESET_RESUME quirk for Snapscan 1212 ALSA: usb-audio: Fix potential out-of-bounds shift ALSA: usb-audio: Fix control 'access overflow' errors from chmap xhci: Give USB2 ports time to enter U3 in bus suspend USB: UAS: introduce a quirk to set no_write_same USB: sisusbvga: Make console support depend on BROKEN UBUNTU: [Config] updateconfigs for USB_SISUSBVGA_CON ALSA: pcm: oss: Fix potential out-of-bounds shift serial: 8250_omap: Avoid FIFO corruption caused by MDR1 access drm: fix drm_dp_mst_port refcount leaks in drm_dp_mst_allocate_vcpi pinctrl: merrifield: Set default bias in case no particular value given pinctrl: baytrail: Avoid clearing debounce value when turning it off ARM: dts: sun8i: v3s: fix GIC node memory range gpio: mvebu: fix potential user-after-free on probe scsi: bnx2i: Requires MMU can: softing: softing_netdev_open(): fix error handling RDMA/cm: Fix an attempt to use non-valid pointer when cleaning timewait kernel/cpu: add arch override for clear_tasks_mm_cpumask() mm handling drm/tegra: sor: Disable clocks on error in tegra_sor_init() vxlan: Add needed_headroom for lower device vxlan: Copy needed_tailroom from lowerdev scsi: mpt3sas: Increase IOCInit request timeout to 30s dm table: Remove BUG_ON(in_interrupt()) soc/tegra: fuse: Fix index bug in get_process_id USB: serial: option: add interface-number sanity check to flag handling USB: gadget: f_acm: add support for SuperSpeed Plus USB: gadget: f_midi: setup SuperSpeed Plus descriptors usb: gadget: f_fs: Re-use SS descriptors for SuperSpeedPlus USB: gadget: f_rndis: fix bitrate for SuperSpeed and above usb: chipidea: ci_hdrc_imx: Pass DISABLE_DEVICE_STREAMING flag to imx6ul ARM: dts: exynos: fix roles of USB 3.0 ports on Odroid XU ARM: dts: exynos: fix USB 3.0 VBUS control and over-current pins on Exynos5410 ARM: dts: exynos: fix USB 3.0 pins supply being turned off on Odroid XU HID: i2c-hid: add Vero K147 to descriptor override serial_core: Check for port state when tty is in error
[Kernel-packages] [Bug 1914543] Re: Missing device id for Intel TGL-H ISH [8086:43fc] in intel-ish-hid driver
https://patchwork.kernel.org/project/linux- input/patch/20210204083315.122952-1-vicamo.y...@canonical.com/ -- 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: In Progress Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux source package in Focal: In Progress Status in linux-oem-5.10 source package in Focal: In Progress Status in linux source package in Groovy: In Progress Status in linux-oem-5.10 source package in Groovy: Invalid Status in linux source package in Hirsute: In Progress Status in linux-oem-5.10 source package in Hirsute: Invalid 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- SERR- 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: USERPID 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 : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1913499] Re: Bluetooth input doesn't work w/ Bose QC35 ii
*** This bug is a duplicate of bug 1838151 *** https://bugs.launchpad.net/bugs/1838151 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: bluez (Ubuntu) Status: New => Confirmed -- 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/1913499 Title: Bluetooth input doesn't work w/ Bose QC35 ii Status in bluez package in Ubuntu: Confirmed Bug description: When connecting the Bose QC35 ii, the bluetooth audio works just fine initially, but the microphone does not. When I go to the sound settings and change the mic input to use the QC35 ii bluetooth input, the audio changes from stereo to mono and sounds terrible and cannot understand anything. Also the mic picks up some input, but the result output sounds about the same, completely un-understandable, a stuttering digitized version of the input. > lsb_release -rd Description: Ubuntu 20.10 Release: 20.10 Linux dan-xps-9700 5.10.5-051005-generic #202101061537 SMP Wed Jan 6 15:43:53 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux 3. I expected the microphone input and headset output to both work simultaneously via bluetooth. 4. Only the headset output worked well, when enabling microphone both sounded terrible (unusable). ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: bluez 5.55-0ubuntu1.1 Uname: Linux 5.10.5-051005-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jan 27 17:53:00 2021 InstallationDate: Installed on 2021-01-06 (21 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) InterestingModules: rfcomm bnep bluetooth MachineType: Dell Inc. XPS 17 9700 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.5-051005-generic root=UUID=d87c0f2c-adf4-493f-95dc-e2df02f584b3 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/03/2020 dmi.bios.release: 1.4 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.0 dmi.board.name: 03CPGC dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.4.0:bd09/03/2020:br1.4:svnDellInc.:pnXPS179700:pvr:rvnDellInc.:rn03CPGC:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 17 9700 dmi.product.sku: 098F dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: UART BD Address: 28:C2:1F:87:52:EC ACL MTU: 1024:8 SCO MTU: 240:4 UP RUNNING PSCAN RX bytes:1599 acl:0 sco:0 events:91 errors:0 TX bytes:198368 acl:0 sco:0 commands:849 errors:0 mtime.conffile..etc.bluetooth.main.conf: 2021-01-27T17:24:11.108718 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1913499/+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 1914571] 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 1914571 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1914571 Title: my wifi is not working and wifi is not showing in settings Status in linux package in Ubuntu: Incomplete Bug description: i can to see wifi option in my pc and settings it is not working ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Feb 4 14:43:21 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- InstallationDate: Installed on 2020-10-29 (98 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: ubiquity Symptom: installation UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1914571/+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 1914279] Re: linux from security may force reboots without complete dkms modules
The false positives on kernel ADT matrix were caused by an issue in dkms-autopkgtest shipped by the dkms package, as we discussed here: https://lists.ubuntu.com/archives/kernel-team/2021-February/116985.html All the dkms packages which were failing to build in Focal with the hwe-5.8 kernel are now fixed. We need now to fix dkms to make sure this won't happen again. -- 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/1914279 Title: linux from security may force reboots without complete dkms modules Status in apt package in Ubuntu: Invalid Status in dkms package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Status in linux-meta package in Ubuntu: New Status in unattended-upgrades package in Ubuntu: Invalid Status in update-manager package in Ubuntu: Invalid Bug description: Whilst discussing https://discourse.ubuntu.com/t/improvements-for-hardware-support-in- ubuntu-desktop-installation-media/20606 We have noticed a reference to somebody not having working backport- iwlwifi-dkms, whilst SRU of that happened before the v5.4 -> v5.8 switch. However, kernel meta switch was pushed to security pocket, but the dkms modules are all in -updates only. This may result in people automatically installing the new kernel with unatanded upgrades; dkms modules failing to build; and a reboot required flag left on disk. At this point launching update manager will not offer to install dkms modules from updates, and will guide the users to reboot. which will then cause them to boot the new kernel without the dkms modules that might be providing networking for them. Should dkms modules SRUs always getting published into -security pocket, as well as the -updates pocket? Should linux maintainer scripts prevent touching reboot required flag if any dkms modules fail to build? Should apt / unattanded-upgrades / update-manager always update dkms modules with kernels? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1914279/+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 1914571] Re: my wifi is not working and wifi is not showing in settings
** Package changed: ubiquity (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/1914571 Title: my wifi is not working and wifi is not showing in settings Status in linux package in Ubuntu: New Bug description: i can to see wifi option in my pc and settings it is not working ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Feb 4 14:43:21 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- InstallationDate: Installed on 2020-10-29 (98 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: ubiquity Symptom: installation UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1914571/+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 1914571] [NEW] my wifi is not working and wifi is not showing in settings
You have been subscribed to a public bug: i can to see wifi option in my pc and settings it is not working ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Feb 4 14:43:21 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- InstallationDate: Installed on 2020-10-29 (98 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: ubiquity Symptom: installation UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubiquity-20.04.15.2 -- my wifi is not working and wifi is not showing in settings https://bugs.launchpad.net/bugs/1914571 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1894454] Re: [nvidia] Screen freeze
Bump, any solution? I'm experiencing the same issue. -- 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/1894454 Title: [nvidia] Screen freeze Status in nvidia-graphics-drivers-450 package in Ubuntu: Confirmed Bug description: Ubuntu 20.04 freezes randomly ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55 Uname: Linux 5.4.0-45-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Bir dizin: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Bir dizin: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Bir dizin: '/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 450.66 Wed Aug 12 19:42:48 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 BootLog: Error: [Errno 13] Erişim engellendi: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Sep 7 01:22:46 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 450.66, 5.4.0-45-generic, x86_64: installed virtualbox, 6.1.10, 5.4.0-42-generic, x86_64: installed virtualbox, 6.1.10, 5.4.0-45-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a day GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Since a couple weeks or more GraphicsCard: NVIDIA Corporation GM107GL [Quadro K620] [10de:13bb] (rev a2) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation GM107GL [Quadro K620] [10de:1098] InstallationDate: Installed on 2020-04-26 (133 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. Precision Tower 3620 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=tr_TR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-generic root=UUID=5abcce6c-0eb6-4ef4-bf1b-0a62c2924a2d ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/25/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.15.0 dmi.board.name: 0MWYPT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.15.0:bd03/25/2020:svnDellInc.:pnPrecisionTower3620:pvr:rvnDellInc.:rn0MWYPT:rvrA00:cvnDellInc.:ct3:cvr: dmi.product.family: Precision dmi.product.name: Precision Tower 3620 dmi.product.sku: 06B7 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.3 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/ubuntu/+source/nvidia-graphics-drivers-450/+bug/1894454/+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 1914568] [NEW] Azure kernel for focal misses binder and ashmem kernel modules
Public bug reported: For the purpose of Anbox Cloud we package both the binder and ashmem kernel modules in the Ubuntu kernel. The generic kernel ships it and all clouds specific kernels should too. However the azure kernel doesn't include the prebuilt binder_linux.ko and ashmem_linux.ko modules: ubuntu@ac0:~$ uname -r 5.4.0-1039-azure ubuntu@ac0:~$ dpkg -L linux-modules-extra-5.4.0-1039-azure | grep binder ubuntu@ac0:~$ dpkg -L linux-modules-extra-5.4.0-1039-azure | grep ashmem Can we please get both kernel modules added to azure kernel and at the same time double check that the modules are packaged in all other cloud kernels? Thanks! ** Affects: linux-azure (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1914568 Title: Azure kernel for focal misses binder and ashmem kernel modules Status in linux-azure package in Ubuntu: New Bug description: For the purpose of Anbox Cloud we package both the binder and ashmem kernel modules in the Ubuntu kernel. The generic kernel ships it and all clouds specific kernels should too. However the azure kernel doesn't include the prebuilt binder_linux.ko and ashmem_linux.ko modules: ubuntu@ac0:~$ uname -r 5.4.0-1039-azure ubuntu@ac0:~$ dpkg -L linux-modules-extra-5.4.0-1039-azure | grep binder ubuntu@ac0:~$ dpkg -L linux-modules-extra-5.4.0-1039-azure | grep ashmem Can we please get both kernel modules added to azure kernel and at the same time double check that the modules are packaged in all other cloud kernels? Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1914568/+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
