[Kernel-packages] [Bug 1927808] Re: rtw88_8821ce causes freeze
** Also affects: linux-oem-5.14 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-oem-5.14 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: Confirmed ** Also affects: linux-oem-5.14 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: linux-oem-5.14 (Ubuntu Impish) Importance: Undecided Status: New ** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: New => Confirmed ** Changed in: linux-oem-5.14 (Ubuntu Jammy) Status: New => Invalid ** Changed in: linux (Ubuntu Focal) Status: New => Won't Fix ** Changed in: linux-oem-5.14 (Ubuntu Impish) Status: New => Invalid ** Changed in: linux (Ubuntu Impish) Status: New => Confirmed ** Changed in: linux (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Impish) Importance: Undecided => Medium ** Changed in: linux-oem-5.14 (Ubuntu Focal) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1927808 Title: rtw88_8821ce causes freeze Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.14 source package in Focal: Confirmed Status in linux source package in Impish: Confirmed Status in linux-oem-5.14 source package in Impish: Invalid Status in linux source package in Jammy: Confirmed Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: My laptop (Ollee L116HTN6SPW) has a Realtek 8821CE WiFi card. Now at hirsute, this is "supported" in the linux-image-5.11.0-16-generic kernel,and it works "well" for both WiFi and Bluetooth. However, this module (driver) causes frequent freezes, randomly but usually within a few minutes of running (thus very soon after boot): screen display remains frozen, no response to either keyboard or mouse input. All I can do is to hold the power button to power off, then reboot. After reboot, I do not see any crash reports, nor logs about the freeze. Please let me know if I should try to collect some info, and how. For now I use the DKMS module/driver from https://github.com/tomaspinho/rtl8821ce (having blacklisted rtw88_8821ce), and it seems to work perfectly. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-16-generic 5.11.0-16.17 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: psz1189 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat May 8 16:58:19 2021 InstallationDate: Installed on 2021-04-23 (14 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 058f:5608 Alcor Micro Corp. USB 2.0 Camera Bus 001 Device 003: ID 0bda:c821 Realtek Semiconductor Corp. Bluetooth Radio Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Protempo Ltd L116HTN6SPW ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=f3700d1b-be99-4cb7-baef-c0f157487c64 ro quiet splash pci=noaer vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/26/2020 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: YHSM-BI-11.6-X116AR300-AA55C-195-A dmi.board.asset.tag: Default string dmi.board.name: Default string dmi.board.vendor: Default string dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.ec.firmware.release: 1.6 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrYHSM-BI-11.6-X116AR300-AA55C-195-A:bd05/26/2020:br5.12:efr1.6:svnProtempoLtd:pnL116HTN6SPW:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring: dmi.product.family: Notebook dmi.product.name: L116HTN6SPW dmi.product.sku: Default string dmi.product.version: Default string
[Kernel-packages] [Bug 1943560] Re: cpufreq_boost in ubuntu_ltp.kernel_misc test failure on ppc64el
*** This bug is a duplicate of bug 1943732 ***
https://bugs.launchpad.net/bugs/1943732
This issue can be found on ARM64 node kuzzle as well, with impish kernel
5.13.0-23.23:
cpufreq_boost1 TFAIL : cpufreq_boost.c:189: compare time spent with and
without boost (-2%)
** Summary changed:
- ubuntu_ltp.kernel_misc test failure on ppc64el
+ cpufreq_boost in ubuntu_ltp.kernel_misc test failure on ppc64el
** Tags added: 5.13 impish sru-20211129 ubuntu-ltp-kernel-misc
** This bug has been marked a duplicate of bug 1943732
cpufreq_boost from ubuntu_ltp.kernel_misc failed on P9 node baltar with
Focal 5.4
--
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/1943560
Title:
cpufreq_boost in ubuntu_ltp.kernel_misc test failure on ppc64el
Status in ubuntu-kernel-tests:
New
Status in linux package in Ubuntu:
Expired
Status in linux source package in Impish:
Expired
Bug description:
ubuntu_ltp.kernel_misc test failure on impish linux 5.13:
STARTubuntu_ltp.kernel_miscubuntu_ltp.kernel_misc
02:33:58 DEBUG| [stdout] cpufreq_boost1 TFAIL : cpufreq_boost.c:189:
compare time spent with and without boost (-2%)
...
384612 Traceback (most recent call last):
384613 File "/home/ubuntu/autotest/client/shared/test.py",
line 411, in _exec
384614 _call_test_function(self.execute, *p_args,
**p_dargs)
384615 File "/home/ubuntu/autotest/client/shared/test.py",
line 823, in _call_test_function
384616 return func(*args, **dargs)
384617 File "/home/ubuntu/autotest/client/shared/test.py",
line 291, in execute
384618 postprocess_profiled_run, args, dargs)
384619 File "/home/ubuntu/autotest/client/shared/test.py",
line 212, in _call_run_once
384620 self.run_once(*args, **dargs)
384621 File
"/home/ubuntu/autotest/client/tests/ubuntu_ltp/ubuntu_ltp.py", line 151, in
run_once
384622 raise error.TestError('Test failed for ' +
test_name)
384623 TestError: Test failed for kernel_misc
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1943560/+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 1943560] Re: ubuntu_ltp.kernel_misc test failure on ppc64el
** Also affects: ubuntu-kernel-tests
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/1943560
Title:
cpufreq_boost in ubuntu_ltp.kernel_misc test failure on ppc64el
Status in ubuntu-kernel-tests:
New
Status in linux package in Ubuntu:
Expired
Status in linux source package in Impish:
Expired
Bug description:
ubuntu_ltp.kernel_misc test failure on impish linux 5.13:
STARTubuntu_ltp.kernel_miscubuntu_ltp.kernel_misc
02:33:58 DEBUG| [stdout] cpufreq_boost1 TFAIL : cpufreq_boost.c:189:
compare time spent with and without boost (-2%)
...
384612 Traceback (most recent call last):
384613 File "/home/ubuntu/autotest/client/shared/test.py",
line 411, in _exec
384614 _call_test_function(self.execute, *p_args,
**p_dargs)
384615 File "/home/ubuntu/autotest/client/shared/test.py",
line 823, in _call_test_function
384616 return func(*args, **dargs)
384617 File "/home/ubuntu/autotest/client/shared/test.py",
line 291, in execute
384618 postprocess_profiled_run, args, dargs)
384619 File "/home/ubuntu/autotest/client/shared/test.py",
line 212, in _call_run_once
384620 self.run_once(*args, **dargs)
384621 File
"/home/ubuntu/autotest/client/tests/ubuntu_ltp/ubuntu_ltp.py", line 151, in
run_once
384622 raise error.TestError('Test failed for ' +
test_name)
384623 TestError: Test failed for kernel_misc
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1943560/+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 1948446] Re: failure is observed in remapping BARs 20.04
[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/1948446 Title: failure is observed in remapping BARs 20.04 Status in linux package in Ubuntu: Expired Bug description: In Ubuntu, CONFIG_PCI_REALLOC_ENABLE_AUTO config option is enabled by default. As a result, OS tries to remap BAR addresses and a failure is observed in remapping BARs. The issue is observed only when the SRIOV flag is disabled in BIOS. The issue can be worked by disabling BAR remapping bypassing “pci=realloc=off” kernel parameter. It has been tested with positive results. Dmesg also shows the following messages indicating that the setting up of standard BAR registers for the GPGPUs has failed. Jun 21 06:14:47 R750XAS kernel: [ 70.384361] pci :17:00.0: BAR 1: no space for [mem size 0x20 64bit pref] Jun 21 06:14:47 R750XAS kernel: [ 70.476810] pci :17:00.0: BAR 1: failed to assign [mem size 0x20 64bit pref] Jun 21 06:14:47 R750XAS kernel: [ 71.041877] pci :17:00.0: BAR 0: no space for [mem size 0x0100] Jun 21 06:14:47 R750XAS kernel: [ 71.120838] pci :17:00.0: BAR 0: failed to assign [mem size 0x0100] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948446/+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 1955513] 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 1955513 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: impish -- 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/1955513 Title: NUC11PAHi7-Tiger Lake Status in linux package in Ubuntu: Incomplete Bug description: in Ubuntu Jammy Jellyfish 22.04, with kernel 5.13.0-22-generic running on the NUC11PAHi7 hardware platform, the audio is broken. No audio is output over HDMI or headphone jack despite the sound hardware being detected. The issue is with the OS/Kernel since I booted the hardware with Windows 10 and it worked. Another issue is that the machine constantly drops the WiFi connection, again this is behavior not observed when I booted into Win 10. BIOS is the stock default version PATGL357.0041 and there is no other current update available. Please fix. Thank You. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1955513/+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 1955513] [NEW] NUC11PAHi7-Tiger Lake
Public bug reported: in Ubuntu Jammy Jellyfish 22.04, with kernel 5.13.0-22-generic running on the NUC11PAHi7 hardware platform, the audio is broken. No audio is output over HDMI or headphone jack despite the sound hardware being detected. The issue is with the OS/Kernel since I booted the hardware with Windows 10 and it worked. Another issue is that the machine constantly drops the WiFi connection, again this is behavior not observed when I booted into Win 10. BIOS is the stock default version PATGL357.0041 and there is no other current update available. Please fix. Thank You. ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: impish ** Description changed: in Ubuntu Jammy Jellyfish 22.04, with kernel 5.13.0-22-generic running on the NUC11PAHi7 hardware platform, the audio is broken. No audio is output over HDMI or headphone jack despite the sound hardware being detected. The issue is with the OS/Kernel since I booted the hardware - with Windows 10 and it worked. Another issues is that the machine + with Windows 10 and it worked. Another issue is that the machine constantly drops the WiFi connection, again this is behavior not observed when I booted into Win 10. BIOS is the stock default version PATGL357.0041 and there is no other current update available. Please fix. Thank You. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1955513 Title: NUC11PAHi7-Tiger Lake Status in linux package in Ubuntu: Incomplete Bug description: in Ubuntu Jammy Jellyfish 22.04, with kernel 5.13.0-22-generic running on the NUC11PAHi7 hardware platform, the audio is broken. No audio is output over HDMI or headphone jack despite the sound hardware being detected. The issue is with the OS/Kernel since I booted the hardware with Windows 10 and it worked. Another issue is that the machine constantly drops the WiFi connection, again this is behavior not observed when I booted into Win 10. BIOS is the stock default version PATGL357.0041 and there is no other current update available. Please fix. Thank You. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1955513/+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 1778087] Re: ELAN1200 touchpad jumps around and disconnects
@mirh I just installed 5.14.0-1011-oem from APT and still no dice. Had to install nvidia-470 to get it to work and broke something with openGL. So I am now going to revert back to 5.11. 5.15 is slated to release with Ubuntu 22.04 so I have no way to test it yet since I am still on 20.04. This bug persists. -- 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/1778087 Title: ELAN1200 touchpad jumps around and disconnects Status in linux package in Ubuntu: Confirmed Bug description: This is on an ASUS GL503VD laptop and would probably affect other ASUS laptops equipped with the ELAN1200 touchpad. I am on Kernel 4.17.2 because older kernels did not enable the touchpad at all(It was just unrecognized or i2c-hid stopped the computer from booting) The touchpad works but it has erratic behaviour and disconnects randomly. After it disconnects the only way to bring it back is to `modprobe -r hid-multitouch && modprobe hid-multitouch` Libinput and synaptics can handle the touchpad though I found synaptics to be more stable. dmesg gets spammed with this whenever I move the touchpad: [timestamp] i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535) I tried to compile: https://github.com/mishurov/linux_elan1200_touchpad Because from what I understand the "jumpy/disconnect" problem is associated to the incomplete reports and Mishurov managed to mitigate those. Unfortunately some symbols were deprecated in kernel 4.17.2 and it did not compile for my system. While I can use my touchpad as is right now, and "restart" it with modprobe when needed, it would be nice to have it function bug-free. (Right after I typed this my touchpad disconnected and I needed to modprobe again, I am considering making a cronjob for that) Let me know if anything else is needed. Will wait for an apport collection to add log files. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-06-10 (11 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash Tags: bionic Uname: Linux 4.17.2 x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1778087/+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 1798363] Re: i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535)
"Acpi_osi=" to the kernel command line is supposed to make a difference on razer laptops. https://old.reddit.com/r/pop_os/comments/pkeh4r/i2c_hid_get_input_flooding/ But first try 5.15. It should have fixed a very long regression chain in ELAN i2c touchpads. -- 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/1798363 Title: i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535) Status in Linux: Confirmed Status in linux package in Ubuntu: Fix Released Bug description: Oct 17 20:07:57 blurhy-FX503VD kernel: [ 1133.740053] i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535) Oct 17 20:07:57 blurhy-FX503VD kernel: [ 1133.740764] i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535) Oct 17 20:07:57 blurhy-FX503VD kernel: [ 1133.741478] i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535) Oct 17 20:07:57 blurhy-FX503VD kernel: [ 1133.742205] i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535) Oct 17 20:07:57 blurhy-FX503VD kernel: [ 1133.742921] i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535) Oct 17 20:07:57 blurhy-FX503VD kernel: [ 1133.743624] i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535) Oct 17 20:07:57 blurhy-FX503VD kernel: [ 1133.744321] i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535) Oct 17 20:07:57 blurhy-FX503VD kernel: [ 1133.745026] i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535) Oct 17 20:07:57 blurhy-FX503VD kernel: [ 1133.745714] i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535) Oct 17 20:07:57 blurhy-FX503VD kernel: [ 1133.746420] i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535) Lots of these things ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-10-generic 4.18.0-10.11 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: blurhy 2908 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Oct 17 20:07:13 2018 InstallationDate: Installed on 2018-10-10 (6 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180927) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0b05:1869 ASUSTek Computer, Inc. Bus 001 Device 003: ID 13d3:5666 IMC Networks Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. FX503VD ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=ad490863-aaf6-49d0-8508-514c07335e07 ro nouveau.runpm=0 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/03/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FX503VD.302 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: FX503VD 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.:bvrFX503VD.302:bd10/03/2017:svnASUSTeKCOMPUTERINC.:pnFX503VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFX503VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: FX dmi.product.name: FX503VD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1798363/+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 1784152] Re: i2c_hid_get_input floods system logs
Check bug 1798363 if you have a new shiny computer.. This was only ever to ask backporting of a supposedly-not-enough-in-other-cases fix. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1784152 Title: i2c_hid_get_input floods system logs Status in linux package in Ubuntu: Fix Released Bug description: Ubuntu 4.15.0-29.31-generic 4.15.18 After upgrading to kernel version 4.15.0-29 from 4.15.0-23, the system logs are flooded whenever I move the cursor with my touchpad. It looks like this: i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535) i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535) i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535) i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535) etc... This problem did not occur on the previous kernel version so there must have been a change to the "drivers/hid/i2c-hid/i2c-hid.c" file. This seems to be fixed in a recent commit here: https://github.com/torvalds/linux/commit/ef6eaf27274c0351f7059163918f3795da13199c I am currently running the older kernel version but would still like to be up to date without this flooding happening. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784152/+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 1778087] Re: ELAN1200 touchpad jumps around and disconnects
The fix to bug 1937056 was committed 3 days after the last post. Check 5.14+. If that still doesn't do the trick, I would otherwise close this as duplicate of bug 1798363. -- 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/1778087 Title: ELAN1200 touchpad jumps around and disconnects Status in linux package in Ubuntu: Confirmed Bug description: This is on an ASUS GL503VD laptop and would probably affect other ASUS laptops equipped with the ELAN1200 touchpad. I am on Kernel 4.17.2 because older kernels did not enable the touchpad at all(It was just unrecognized or i2c-hid stopped the computer from booting) The touchpad works but it has erratic behaviour and disconnects randomly. After it disconnects the only way to bring it back is to `modprobe -r hid-multitouch && modprobe hid-multitouch` Libinput and synaptics can handle the touchpad though I found synaptics to be more stable. dmesg gets spammed with this whenever I move the touchpad: [timestamp] i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535) I tried to compile: https://github.com/mishurov/linux_elan1200_touchpad Because from what I understand the "jumpy/disconnect" problem is associated to the incomplete reports and Mishurov managed to mitigate those. Unfortunately some symbols were deprecated in kernel 4.17.2 and it did not compile for my system. While I can use my touchpad as is right now, and "restart" it with modprobe when needed, it would be nice to have it function bug-free. (Right after I typed this my touchpad disconnected and I needed to modprobe again, I am considering making a cronjob for that) Let me know if anything else is needed. Will wait for an apport collection to add log files. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-06-10 (11 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash Tags: bionic Uname: Linux 4.17.2 x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1778087/+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 1955504] 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 1955504 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/1955504 Title: firmware bug on bootup Status in linux package in Ubuntu: Incomplete Bug description: I am getting a DMAR firmware bug everytime I boot up. I am using the latest upgrade of Ubuntu Budgie. Can you fix this in the next upgrade. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1955504/+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 1955504] Re: firmware bug on bootup
** Package changed: 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/1955504 Title: firmware bug on bootup Status in linux package in Ubuntu: New Bug description: I am getting a DMAR firmware bug everytime I boot up. I am using the latest upgrade of Ubuntu Budgie. Can you fix this in the next upgrade. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1955504/+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 1955504] [NEW] firmware bug on bootup
You have been subscribed to a public bug: I am getting a DMAR firmware bug everytime I boot up. I am using the latest upgrade of Ubuntu Budgie. Can you fix this in the next upgrade. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- firmware bug on bootup https://bugs.launchpad.net/bugs/1955504 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 1950903] Re: kernel package does not build nvme-tcp module
Tim, We indeed attempted what seems to be an old AMI, I think we can categorize this as a false alarm. Sorry. Thanks for the turn-around. -- 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/1950903 Title: kernel package does not build nvme-tcp module Status in linux-aws package in Ubuntu: Confirmed Status in linux-aws source package in Focal: Confirmed Status in linux-aws source package in Hirsute: Confirmed Status in linux-aws source package in Impish: Confirmed Status in linux-aws source package in Jammy: Confirmed Bug description: linux-image-5.4.0-1059-aws does not build nvme-tcp kernel module so there is no option to use it. The fix is trivial, just add CONFIG_NVME_TCP=m in the kernel config file used to build the kernel image. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1950903/+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 1955493] 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 1955493 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/1955493 Title: Intel Wi-Fi 6E AX210 - Network adapter - M.2 2230 - 802.11ac, 802.11ax (Wi-Fi 6) does not work with kernel 5.13 Status in linux package in Ubuntu: Incomplete Bug description: Intel Wi-Fi 6E AX210 - Network adapter - M.2 2230 - 802.11ac, 802.11ax (Wi-Fi 6) does not work with kernel 5.13 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1955493/+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 1955493] [NEW] Intel Wi-Fi 6E AX210 - Network adapter - M.2 2230 - 802.11ac, 802.11ax (Wi-Fi 6) does not work with kernel 5.13
Public bug reported: Intel Wi-Fi 6E AX210 - Network adapter - M.2 2230 - 802.11ac, 802.11ax (Wi-Fi 6) does not work with kernel 5.13 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: ax210 -- 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/1955493 Title: Intel Wi-Fi 6E AX210 - Network adapter - M.2 2230 - 802.11ac, 802.11ax (Wi-Fi 6) does not work with kernel 5.13 Status in linux package in Ubuntu: New Bug description: Intel Wi-Fi 6E AX210 - Network adapter - M.2 2230 - 802.11ac, 802.11ax (Wi-Fi 6) does not work with kernel 5.13 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1955493/+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 903602] Re: CIFS automount with "nounix" option create empty directories
funny, just saw, that the bug is quite exactly 10years old, which is why it looked like from this month. The problem still looks very similar but it isn't a regression from 5.4.0.89 to 5.4.0.91 at all. The kernel seems to get confused though if you mount a share once with and later withouth unix extensions. In such a situation unmounting *all* cifs shares helped to solve it. But it still looks buggy that area. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/903602 Title: CIFS automount with "nounix" option create empty directories Status in linux-meta package in Ubuntu: Confirmed Bug description: Hi, I'm trying to mount two CIFS shares from my Verbatim NAS. Because of permission problem, I need to use the "nounix" option when I mount them. If I do that with the command: sudo mount.cifs //X.X.X.X/media /mnt/media/ -o credentials=/etc/samba/credentials,iocharset=utf8,uid=1000,gid=100,dir_mode=0775,file_mode=0775,nounix everything works well. If I write the same command in my auto.home file: media -fstype=cifs,credentials=/etc/samba/credentials,iocharset=utf8,uid=1000,gid=100,dir_mode=0775,file_mode=0775,nounix ://192.168.1.253/media I get a "media" directory empty. Can you help me? Ubuntu Maverick 10.10 Linux 2.6.35-31-generic autofs5 5.0.5-0ubuntu2.1 cifs-utils 2:4.5-2ubuntu0.10.10.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/903602/+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 1690085]
Brands N Behind, one of the Best Advertising agencies in Chennai. We are a Branding and Advertising company. https://www.brandsnbehind.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/1690085 Title: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks Status in Linux: Expired Status in linux package in Ubuntu: Confirmed Bug description: Hi, We aregetting various kernel crash on a pretty new config. We're using Ryzen 1800X CPU with X370 Gaming Pro Carbon MB (7A32V1) using latest BIOS available (1.52) We are running Ubuntu 17.04 (amd64), we've tried different kernel version, native one and releases from http://kernel.ubuntu.com/~kernel-ppa/mainline/ too. Tested kernel version: native 17.04 kernel 4.10.15 Issues are the same, we're getting random freeze on the machine. Here is kern.log entry when happening : May 10 22:41:56 dev2 kernel: [24366.186246] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:41:56 dev2 kernel: [24366.187618] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=913449 May 10 22:41:56 dev2 kernel: [24366.188977] (detected by 12, t=1860207 jiffies, g=10001, c=1, q=4656) May 10 22:41:56 dev2 kernel: [24366.190344] Task dump for CPU 0: May 10 22:41:56 dev2 kernel: [24366.190345] swapper/0 R running task 0 0 0 0x0008 May 10 22:41:56 dev2 kernel: [24366.190348] Call Trace: May 10 22:41:56 dev2 kernel: [24366.190354] ? native_safe_halt+0x6/0x10 May 10 22:41:56 dev2 kernel: [24366.190355] ? default_idle+0x20/0xd0 May 10 22:41:56 dev2 kernel: [24366.190358] ? arch_cpu_idle+0xf/0x20 May 10 22:41:56 dev2 kernel: [24366.190360] ? default_idle_call+0x23/0x30 May 10 22:41:56 dev2 kernel: [24366.190362] ? do_idle+0x16f/0x200 May 10 22:41:56 dev2 kernel: [24366.190364] ? cpu_startup_entry+0x71/0x80 May 10 22:41:56 dev2 kernel: [24366.190366] ? rest_init+0x77/0x80 May 10 22:41:56 dev2 kernel: [24366.190368] ? start_kernel+0x464/0x485 May 10 22:41:56 dev2 kernel: [24366.190369] ? early_idt_handler_array+0x120/0x120 May 10 22:41:56 dev2 kernel: [24366.190371] ? x86_64_start_reservations+0x24/0x26 May 10 22:41:56 dev2 kernel: [24366.190372] ? x86_64_start_kernel+0x14d/0x170 May 10 22:41:56 dev2 kernel: [24366.190373] ? start_cpu+0x14/0x14 May 10 22:44:56 dev2 kernel: [24546.188093] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:44:56 dev2 kernel: [24546.189461] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=935027 May 10 22:44:56 dev2 kernel: [24546.190823] (detected by 14, t=1905212 jiffies, g=10001, c=1, q=4740) May 10 22:44:56 dev2 kernel: [24546.192191] Task dump for CPU 0: May 10 22:44:56 dev2 kernel: [24546.192192] swapper/0 R running task 0 0 0 0x0008 May 10 22:44:56 dev2 kernel: [24546.192195] Call Trace: May 10 22:44:56 dev2 kernel: [24546.192199] ? native_safe_halt+0x6/0x10 May 10 22:44:56 dev2 kernel: [24546.192201] ? default_idle+0x20/0xd0 May 10 22:44:56 dev2 kernel: [24546.192203] ? arch_cpu_idle+0xf/0x20 May 10 22:44:56 dev2 kernel: [24546.192204] ? default_idle_call+0x23/0x30 May 10 22:44:56 dev2 kernel: [24546.192206] ? do_idle+0x16f/0x200 May 10 22:44:56 dev2 kernel: [24546.192208] ? cpu_startup_entry+0x71/0x80 May 10 22:44:56 dev2 kernel: [24546.192210] ? rest_init+0x77/0x80 May 10 22:44:56 dev2 kernel: [24546.192211] ? start_kernel+0x464/0x485 May 10 22:44:56 dev2 kernel: [24546.192213] ? early_idt_handler_array+0x120/0x120 May 10 22:44:56 dev2 kernel: [24546.192214] ? x86_64_start_reservations+0x24/0x26 May 10 22:44:56 dev2 kernel: [24546.192215] ? x86_64_start_kernel+0x14d/0x170 May 10 22:44:56 dev2 kernel: [24546.192217] ? start_cpu+0x14/0x14 Depending on the kernel version, we've got NMI watchdog errors related to CPU stuck (mentioning the CPU core id, which is random). Crash is happening randomly, but in general after some hours (3-4h). Now, we've installed kernel 4.11.0-041100-generic #201705041534 this morning and waiting for crash... For now, the machine is not "used", at least, it's not CPU stressed... Thanks --- ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-05-09 (1 days ago) InstallationMedia: Ubuntu-Server 17.04 "Zesty Zapus" - Release amd64 (20170412) Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash Tags: zesty Uname: Linux 4.11.0-041100-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to:
[Kernel-packages] [Bug 903602] Re: CIFS automount with "nounix" option create empty directories
I've CCd kernel package maintainer Stefan Bader also. I've seen this problem on a customer machine also with current linux- image hwe-18.04 (5.4.0.91) kernels. Directories with nounix mount option are empty. Previous 5.4.0.89 seems to have issues *with* unix extensions here though, that one wan not able to mount at all if the unix mount option is added. The current bug with "successful" but empty cifs mounts is worse though. ** Package changed: autofs (Ubuntu) => linux-meta (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/903602 Title: CIFS automount with "nounix" option create empty directories Status in linux-meta package in Ubuntu: Confirmed Bug description: Hi, I'm trying to mount two CIFS shares from my Verbatim NAS. Because of permission problem, I need to use the "nounix" option when I mount them. If I do that with the command: sudo mount.cifs //X.X.X.X/media /mnt/media/ -o credentials=/etc/samba/credentials,iocharset=utf8,uid=1000,gid=100,dir_mode=0775,file_mode=0775,nounix everything works well. If I write the same command in my auto.home file: media -fstype=cifs,credentials=/etc/samba/credentials,iocharset=utf8,uid=1000,gid=100,dir_mode=0775,file_mode=0775,nounix ://192.168.1.253/media I get a "media" directory empty. Can you help me? Ubuntu Maverick 10.10 Linux 2.6.35-31-generic autofs5 5.0.5-0ubuntu2.1 cifs-utils 2:4.5-2ubuntu0.10.10.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/903602/+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 903602] [NEW] CIFS automount with "nounix" option create empty directories
You have been subscribed to a public bug: Hi, I'm trying to mount two CIFS shares from my Verbatim NAS. Because of permission problem, I need to use the "nounix" option when I mount them. If I do that with the command: sudo mount.cifs //X.X.X.X/media /mnt/media/ -o credentials=/etc/samba/credentials,iocharset=utf8,uid=1000,gid=100,dir_mode=0775,file_mode=0775,nounix everything works well. If I write the same command in my auto.home file: media -fstype=cifs,credentials=/etc/samba/credentials,iocharset=utf8,uid=1000,gid=100,dir_mode=0775,file_mode=0775,nounix ://192.168.1.253/media I get a "media" directory empty. Can you help me? Ubuntu Maverick 10.10 Linux 2.6.35-31-generic autofs5 5.0.5-0ubuntu2.1 cifs-utils 2:4.5-2ubuntu0.10.10.1 ** Affects: linux-meta (Ubuntu) Importance: Medium Status: Confirmed -- CIFS automount with "nounix" option create empty directories https://bugs.launchpad.net/bugs/903602 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta 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 1802056] Re: Unable to start KVM, timed out waiting for dnsmasq lease
Spotted on Trusty 3.13.0-189.240, with i386 instances only. ** Tags added: sru-20211129 ** Tags added: hinted ** Summary changed: - Unable to start KVM, timed out waiting for dnsmasq lease + Unable to start KVM, timed out waiting for dnsmasq lease on Trusty i386 -- 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/1802056 Title: Unable to start KVM, timed out waiting for dnsmasq lease on Trusty i386 Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Invalid Bug description: On node gonzo with Trusty + uvtool (0~bzr92-0ubuntu1.1) and 0~bzr99~ubuntu14.04.1 from ppa, the kvm smoke test failed with dnsmasq lease time out. ubuntu@gonzo:~$ uvt-kvm create trusty release=trusty arch=amd64 ubuntu@gonzo:~$ uvt-kvm wait trusty --insecure --ssh-private-key-file /home/ubuntu/.ssh/id_rsa uvt-kvm: error: timed out waiting for dnsmasq lease for 52:54:00:c9:fe:f5. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-161-generic 3.13.0-161.211 ProcVersionSignature: User Name 3.13.0-161.211-generic 3.13.11-ckt39 Uname: Linux 3.13.0-161-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 7 03:48 seq crw-rw 1 root audio 116, 33 Nov 7 03:48 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Wed Nov 7 07:03:48 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Dell Inc. PowerEdge R415 PciMultimedia: ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-161-generic root=UUID=3e0e190e-d425-4d00-a9a9-deb0c452399b ro console=ttyS0,115200n8 RelatedPackageVersions: linux-restricted-modules-3.13.0-161-generic N/A linux-backports-modules-3.13.0-161-generic N/A linux-firmware 1.127.24 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/26/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.9.3 dmi.board.name: 08WNM9 dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.9.3:bd04/26/2012:svnDellInc.:pnPowerEdgeR415:pvr:rvnDellInc.:rn08WNM9:rvrA02:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R415 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1802056/+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 1955016] Re: devices on thunderbolt dock are not recognized on adl-p platform
** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1955016 Title: devices on thunderbolt dock are not recognized on adl-p platform Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux source package in Jammy: In Progress Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [Impact] When booting up with the TBT dock is plugged, the devices(USB, Ethernet) on the dock can't be recognized. It requires to run lspci command to wake up the PCI devices to make the devices on the dock work. [Fix] The patchset fix this runtime pm issue. https://patchwork.kernel.org/project/linux-usb/cover/20211125073733.74902-1-mika.westerb...@linux.intel.com/ [Test] Verified on Dell ADL-P platform with TBT dock. [Where the problems could occur] Hard to evaluate, but after some cold boot/warm boot, plug/un-plug the devices on the dock, didn't observe any regressions. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1955016/+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 1955472] [NEW] package linux-firmware 1.187.20 failed to install/upgrade: unable to open '/lib/firmware/qcom/sdm845/modem.mbn.dpkg-new': Operation not permitted
Public bug reported: package linux-firmware 1.187.20 failed to install/upgrade: unable to open '/lib/firmware/qcom/sdm845/modem.mbn.dpkg-new': Operation not permitted ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187.20 ProcVersionSignature: Ubuntu 5.11.0-41.45~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: michele.mcdonald 2081 F pulseaudio CasperMD5CheckResult: skip Date: Fri Dec 17 11:56:30 2021 Dependencies: DuplicateSignature: package:linux-firmware:1.187.20 Unpacking linux-firmware (1.187.23) over (1.187.20) ... dpkg: error processing archive /tmp/apt-dpkg-install-JkBnFw/19-linux-firmware_1.187.23_all.deb (--unpack): unable to open '/lib/firmware/qcom/sdm845/modem.mbn.dpkg-new': Operation not permitted ErrorMessage: unable to open '/lib/firmware/qcom/sdm845/modem.mbn.dpkg-new': Operation not permitted HibernationDevice: RESUME=UUID=057550e0-f8b1-4003-9694-cc6af708a598 InstallationDate: Installed on 2021-04-16 (248 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0cf3:e007 Qualcomm Atheros Communications Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 0bda:5689 Realtek Semiconductor Corp. Integrated Webcam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude 3590 PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-41-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.04-1ubuntu26.13 SourcePackage: linux-firmware Title: package linux-firmware 1.187.20 failed to install/upgrade: unable to open '/lib/firmware/qcom/sdm845/modem.mbn.dpkg-new': Operation not permitted UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/24/2019 dmi.bios.release: 1.9 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.9.9 dmi.board.name: 0J8D23 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.9.9:bd05/24/2019:br1.9:svnDellInc.:pnLatitude3590:pvr:sku083A:rvnDellInc.:rn0J8D23:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 3590 dmi.product.sku: 083A dmi.sys.vendor: Dell Inc. ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal need-duplicate-check -- 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/1955472 Title: package linux-firmware 1.187.20 failed to install/upgrade: unable to open '/lib/firmware/qcom/sdm845/modem.mbn.dpkg-new': Operation not permitted Status in linux-firmware package in Ubuntu: New Bug description: package linux-firmware 1.187.20 failed to install/upgrade: unable to open '/lib/firmware/qcom/sdm845/modem.mbn.dpkg-new': Operation not permitted ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187.20 ProcVersionSignature: Ubuntu 5.11.0-41.45~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: michele.mcdonald 2081 F pulseaudio CasperMD5CheckResult: skip Date: Fri Dec 17 11:56:30 2021 Dependencies: DuplicateSignature: package:linux-firmware:1.187.20 Unpacking linux-firmware (1.187.23) over (1.187.20) ... dpkg: error processing archive /tmp/apt-dpkg-install-JkBnFw/19-linux-firmware_1.187.23_all.deb (--unpack): unable to open '/lib/firmware/qcom/sdm845/modem.mbn.dpkg-new': Operation not permitted ErrorMessage: unable to open '/lib/firmware/qcom/sdm845/modem.mbn.dpkg-new': Operation not permitted HibernationDevice: RESUME=UUID=057550e0-f8b1-4003-9694-cc6af708a598 InstallationDate: Installed on 2021-04-16 (248 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0cf3:e007 Qualcomm Atheros Communications Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 0bda:5689 Realtek Semiconductor Corp. Integrated Webcam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
[Kernel-packages] [Bug 1943033] Re: ubuntu_kvm_smoke_test: uvt-kvm: error: libvirt: XML error: No PCI buses available on s390x
** Tags added: hinted sru-20211129
--
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/1943033
Title:
ubuntu_kvm_smoke_test: uvt-kvm: error: libvirt: XML error: No PCI
buses available on s390x
Status in ubuntu-kernel-tests:
New
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Xenial:
Confirmed
Bug description:
02:56:35 DEBUG| stdout:
02:56:35 DEBUG| INFO: /dev/kvm exists
02:56:35 DEBUG| KVM acceleration can be used
02:56:35 DEBUG| stderr:
02:56:35 DEBUG| + SUT=bjf-test
02:56:35 DEBUG| + SSH_KEY=/home/ubuntu/.ssh/id_rsa
02:56:35 DEBUG| + SSH_OPTIONS='-o StrictHostKeyChecking=no -o
UserKnownHostsFile=/dev/null -o LogLevel=quiet -i /home/ubuntu/.ssh/id_rsa'
02:56:35 DEBUG| ++ lsb_release -c
02:56:35 DEBUG| ++ awk '{print$2}'
02:56:35 DEBUG| + DISTRO=xenial
02:56:35 DEBUG| + ARCHITECTURE=s390x
02:56:35 DEBUG| + trap cleanup EXIT
02:56:35 DEBUG| + '[' -z s390x ']'
02:56:35 DEBUG| + kvm-ok
02:56:35 DEBUG| + '[' 0 '!=' 0 ']'
02:56:35 DEBUG| + set -e
02:56:35 DEBUG| + '[' '!' -f /home/ubuntu/.ssh/id_rsa ']'
02:56:35 DEBUG| + '[' s390x = ppc64el ']'
02:56:35 DEBUG| ++ uvt-simplestreams-libvirt query
02:56:35 DEBUG| ++ grep -P 'xenial.*s390x'
02:56:35 DEBUG| + image='release=xenial arch=s390x label=daily (20210203)'
02:56:35 DEBUG| + '[' -z 'release=xenial arch=s390x label=daily (20210203)'
']'
02:56:35 DEBUG| + uvt-kvm create bjf-test release=xenial arch=s390x
02:56:35 DEBUG| uvt-kvm: error: libvirt: XML error: No PCI buses available
02:56:35 DEBUG| + cleanup
02:56:35 DEBUG| + uvt-kvm destroy bjf-test
02:56:36 INFO | ERROR ubuntu_kvm_smoke_test.kvm_smoke_test
ubuntu_kvm_smoke_test.kvm_smoke_testtimestamp=1630983396localtime=Sep
07 02:56:36 Command
failed, rc=1, Command returned non-zero exit status
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1943033/+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 1749427] Re: Unable to create KVM with uvtool on arm64 system (Cirrus VGA not available)
** Summary changed: - Unable to create KVM with uvtool on arm64 system + Unable to create KVM with uvtool on arm64 system (Cirrus VGA not available) -- 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/1749427 Title: Unable to create KVM with uvtool on arm64 system (Cirrus VGA not available) Status in ubuntu-kernel-tests: Invalid Status in linux package in Ubuntu: Invalid Bug description: Not sure if this is related to bug 1452016, or just a HW issue: With the uvt-kvm create command on this Artful system, it returns: uvt-kvm: error: libvirt: unsupported configuration: ACPI requires UEFI on this architecture With the same command running on a Xenail system + Artful kernel, it returns: qemu-system-aarch64: Cirrus VGA not available ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-32-generic 4.13.0-32.35 ProcVersionSignature: User Name 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic aarch64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Feb 14 11:01 seq crw-rw 1 root audio 116, 33 Feb 14 11:01 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.7-0ubuntu3.7 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: Date: Wed Feb 14 11:09:44 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: console=ttyS0,9600n8r ro RelatedPackageVersions: linux-restricted-modules-4.13.0-32-generic N/A linux-backports-modules-4.13.0-32-generic N/A linux-firmware 1.169.3 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1749427/+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
