[Kernel-packages] [Bug 1888385] Re: FRITZ!WLAN USB Stick v2 (Product: FRITZ!WLAN N2.4) [057c:8403] does not work with Linux version 4.4.0-186-generic (Last working version 4.4.0-185-generic and 4.4.0-
Could you try the kernel in https://launchpad.net/~vicamo/+archive/ubuntu/ppa-1888385 ? It's based on 4.4.0-187 with one additional commit from https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-4.4.y=e27a1e3d9c9ac453a94ab5646f7b92492a685c04, which is to be included in 4.4.0-188. The PPA is scheduled for build and may take a couple hours to finish. Please post a comment here whether that fixes this bug and reset bug status to confirmed. ** 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/1888385 Title: FRITZ!WLAN USB Stick v2 (Product: FRITZ!WLAN N2.4) [057c:8403] does not work with Linux version 4.4.0-186-generic (Last working version 4.4.0-185-generic and 4.4.0-184-generic) Status in linux package in Ubuntu: Incomplete Bug description: Dear all, the USB WLAN Stick (FRITZ!WLAN USB Stick v2) worked flawlessly up to the Linux Kernel version 4.4.0-185-generic, so I assume some problem has been introduced moving from Linux version 4.4.0-185-generic to the Linux version 4.4.0-186-generic. Operating system and release can be found below. Description:Ubuntu 16.04.6 LTS Release:16.04 Attached are the files for the currently working version (4.4.0-185-generic): dmesg, version signature, lspci and uname output). I provide too the dmesg output of the failing kernel version (4.4.0-185-generic). I am happy to provide more details. Apparently the module is not loaded anymore. Kind regards, Stephan To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888385/+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 1889342] Re: Thunderbolt Dock Loses Monitors
Some additional details: I'm using a Dell WD19TB dock. The lock screen seems to be the tipping point, with that disabled I'm able to continually use external monitors. If I hit win+l to lock then I have to unplug the dock in order to get external monitors working again. -- 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/1889342 Title: Thunderbolt Dock Loses Monitors Status in linux package in Ubuntu: Confirmed Bug description: After a suspend or locking the only way to regain external monitors is to unplug and replug the thunderbolt dock back in. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-42-generic 5.4.0-42.46 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: john 2682 F pulseaudio /dev/snd/controlC0: john 2682 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jul 29 00:22:26 2020 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 InstallationDate: Installed on 2020-07-13 (15 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. XPS 13 9300 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=5e141eb0-e03b-4c39-b826-f94e0d2715ea ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/08/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.11 dmi.board.name: 0WX9VX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.11:bd05/08/2020:svnDellInc.:pnXPS139300:pvr:rvnDellInc.:rn0WX9VX:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9300 dmi.product.sku: 096D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1889342/+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 1888385] Re: FRITZ!WLAN USB Stick v2 (Product: FRITZ!WLAN N2.4) does not work with Linux version 4.4.0-186-generic (Last working version 4.4.0-185-generic and 4.4.0-184-generic)
** Tags added: hwe-networking-wifi ** Summary changed: - FRITZ!WLAN USB Stick v2 (Product: FRITZ!WLAN N2.4) does not work with Linux version 4.4.0-186-generic (Last working version 4.4.0-185-generic and 4.4.0-184-generic) + FRITZ!WLAN USB Stick v2 (Product: FRITZ!WLAN N2.4) [057c:8403] does not work with Linux version 4.4.0-186-generic (Last working version 4.4.0-185-generic and 4.4.0-184-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/1888385 Title: FRITZ!WLAN USB Stick v2 (Product: FRITZ!WLAN N2.4) [057c:8403] does not work with Linux version 4.4.0-186-generic (Last working version 4.4.0-185-generic and 4.4.0-184-generic) Status in linux package in Ubuntu: Confirmed Bug description: Dear all, the USB WLAN Stick (FRITZ!WLAN USB Stick v2) worked flawlessly up to the Linux Kernel version 4.4.0-185-generic, so I assume some problem has been introduced moving from Linux version 4.4.0-185-generic to the Linux version 4.4.0-186-generic. Operating system and release can be found below. Description:Ubuntu 16.04.6 LTS Release:16.04 Attached are the files for the currently working version (4.4.0-185-generic): dmesg, version signature, lspci and uname output). I provide too the dmesg output of the failing kernel version (4.4.0-185-generic). I am happy to provide more details. Apparently the module is not loaded anymore. Kind regards, Stephan To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888385/+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 1791427] Re: Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1 Carbon 6th
@Kai-Heng Please be clear. I take it that by your last post you mean this: I should stick to s2idle in the sense, not of (i) sending you only the log for that, but in the sense of (ii) not contributing to the fix. However: will someone who uploads both logs here be contributing to the fix? Subordinate questions: (1) you are a kernel engineer, yes? (2) is there much of a prospect of this bug ever being fixed? Thank you for your time. -- 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/1791427 Title: Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1 Carbon 6th Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu 18.04.1 Terminology in case we use different terms: touchpad - just the rectangular touch-sensitive surface below the keyboard (xinput lists it as Synaptics TM3288-011) trackpoint - the red thingy built into the keyboard + 3 physical buttons below the keyboard (trackpoint and buttons are integrated together; listed in xinput as TPPS/2 Elan TrackPoint) On September 7th, 2018, Lenovo has issued a BIOS update (v1.30), which enables proper S3 deep sleep state - users no longer have to patch DSDT tables to get it. It can be enabled in the BIOS settings. In X1 carbon 6th generation models that have NFC, when laptop wakes from suspend by opening the lid, in most cases both touchpad and trackpoint stop working completely. They are also no longer listed when running xinput command. Sometimes just one of them stops working, usually the trackpoint. In some rare cases it is possible to bring them back by using these commands: echo -n none > /sys/devices/platform/i8042/serio1/drvctl echo -n reconnect > /sys/devices/platform/i8042/serio1/drvctl rmmod psmouse modprobe psmouse These worked properly when waking up from S2Idle sleep state (had these in a script that runs after waking the machine from suspend), but with S3 deep sleep these rarely work and the only way to bring back touchpad and/or trackpoint is turning off the machine and turning it on (restart does not help). I could not find any pattern that would show when the input devices stop working or start working again using the commands mentioned above. It's completely random from my perspective. This is happening on the standard issue 4.15.0-33-generic kernel that shipped with my Ubuntu 18.04 (with updates), as well as with newer mainline kernels, such as the newest point versions of 4.17, 4.18 and 4.19 RC2. This happens regardless of whether "blacklist i2c_i801" is commented out in /etc/modprobe.d/blacklist.conf or not. It happens regardless of whether "psmouse.synaptics_intertouch=1" is passed as grub parameter. Presence of TLP does not make it better, nor worse. It appears that non-NFC models are not affected. I know at least one Arch Linux user who has the exact same model, but without this issue. I'm using synaptics driver (no libinput installed), he uses libinput and doesn't have synaptics, if that information is of any use. Libinput does not seem to help. This forum thread also has more details from users who updated their BIOS to get S3 suspend: https://forums.lenovo.com/t5/Linux- Discussion/X1-Carbon-Gen-6-cannot-enter-deep-sleep-S3-state-aka- Suspend-to/td-p/3998182/page/27 Another related thread: https://bbs.archlinux.org/viewtopic.php?id=236367 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-33-generic 4.15.0-33.36 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: maciej 2651 F...m pulseaudio /dev/snd/controlC0: maciej 2651 F pulseaudio CurrentDesktop: i3 Date: Sat Sep 8 13:45:43 2018 HibernationDevice: RESUME=UUID=3116dcb0-d91e-4b2a-8166-43b7a9a9d36e InstallationDate: Installed on 2018-07-21 (49 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 13d3:56b2 IMC Networks Bus 001 Device 002: ID 04b4:0060 Cypress Semiconductor Corp. Wireless optical mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20KH006KPB ProcFB: 0 EFI VGA 1 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-33-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash psmouse.synaptics_intertouch=1 vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-33-generic N/A linux-backports-modules-4.15.0-33-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh
[Kernel-packages] [Bug 1887607] Re: NFSv4.1: Interrupted connections cause high bandwidth RPC ping-pong between client and server
** Description changed: BugLink: https://bugs.launchpad.net/bugs/1887607 [Impact] There is a bug in NFS v4.1 that causes a large amount of RPC calls between a client and server when a previous RPC call is interrupted. This uses a large amount of bandwidth and can saturate the network. The symptoms are so: * On NFS clients: Attempts to access mounted NFS shares associated with the affected server block indefinitely. * On the network: A storm of repeated RPCs between NFS client and server uses a lot of bandwidth. Each RPC is acknowledged by the server with an NFS4ERR_SEQ_MISORDERED error. * Other NFS clients connected to the same NFS server: Performance drops dramatically. This occurs during a "false retry", when a client attempts to make a new RPC call using a slot+sequence number that references an older, cached call. This happens when a user process interrupts an RPC call that is in progress. I had previously fixed this for Disco in bug 1828978, and now a customer has run into the issue in Bionic. A reproducer is supplied in the testcase section, which was something missing from bug 1828978, since we never determined how the issue actually occurred back then. [Fix] This was fixed in 5.1 upstream with the below commit: commit 3453d5708b33efe76f40eca1c0ed60923094b971 Author: Trond Myklebust Date: Wed Jun 20 17:53:34 2018 -0400 Subject: NFSv4.1: Avoid false retries when RPC calls are interrupted The fix is to pre-emptively increment the sequence number if an RPC call is interrupted, and to address corner cases we interpret the NFS4ERR_SEQ_MISORDERED error as a sign we need to locate an appropriate sequence number between the value we sent, and the last successfully acked SEQUENCE call. The commit also requires two fixup commits, which landed in 5.5 and 5.8-rc6 respectively: commit 5c441544f045e679afd6c3c6d9f7aaf5fa5f37b0 Author: Trond Myklebust Date: Wed Nov 13 08:34:00 2019 +0100 Subject: NFSv4.x: Handle bad/dead sessions correctly in nfs41_sequence_process() commit 913fadc5b105c3619d9e8d0fe8899ff1593cc737 Author: Anna Schumaker Date: Wed Jul 8 10:33:40 2020 -0400 Subject: NFS: Fix interrupted slots by sending a solo SEQUENCE operation Commits 3453d5708b33efe76f40eca1c0ed60923094b971 and 913fadc5b105c3619d9e8d0fe8899ff1593cc737 require small backports to bionic, as struct rpc_cred changed to const struct cred in 5.0, and the backports swap them back to struct rpc_cred since that is how 4.15 works. [Testcase] You will need four machines. The first, is a kerberos KDC. Set up Kerberos correctly and create new service principals for the NFS server and for the client. I used: nfs/nfskerb.mydomain.com and nfs/client.mydomain.com. The second machine will be a NFS server with the krb5p share. Add the nfs server kerberos keys to the system's keytab, and set up a NFS server that exports a directory with sec=krb5p. Example export: /mnt/secretfolder *.mydomain.com(rw,sync,no_subtree_check,sec=krb5p) The third machine is a regular NFS server. Export a directory with normal sec=sys security. Example export: /mnt/sharedfolder *.mydomain.com(rw,sync) The fourth is a desktop machine. Add the client kerberos keys to the system's keytab. Mount both NFS shares, making sure to use the NFS v4.2 protocol. I used the commands: mount -t nfs4 nfskerb.mydomain.com:/mnt/secretfolder /mnt/secretfolder_client/ mount -t nfs4 nfs.mydomain.com:/mnt/sharedfolder /mnt/sharedfolder_client Check "mount -l" to ensure that NFS v4.2 is used: nfskerb.mydomain.com:/mnt/secretfolder on /mnt/secretfolder_client type nfs4 (rw,relatime,vers=4.2,<...>,sec=krb5p,<...>) nfs.mydomain.com:/mnt/sharedfolder on /mnt/sharedfolder_client type nfs4 (rw,relatime,vers=4.2,<...>,sec=sys,<...>) Generate some files full of random data. I found 20MB from /dev/random works great. Open each NFS share up in tabs in Nautilus. Copy the random data files to the sec=sys NFS share. When they are done, one at a time cut and then paste the file into the sec=krb5p NFS share. The bug will trigger either on the first, or subsequent tries, but less than 10 tries are needed usually. There is a test kernel available in the following PPA: https://launchpad.net/~mruffell/+archive/ubuntu/sf285439-test If you install the test kernel, files will cut and paste correctly, and NFS will work as expected. [Regression Potential] The changes are localised to NFS v4.1 and v4.2 only, and other versions of NFS are not affected. If a regression occurs, users can downgrade NFS versions to v4.0 or v3.x until a fix is made. The changes only impact when connections are interrupted, and under typical blue sky scenarios would not be invoked. - There have been no fixup commits or commits near the requested commit in - newer kernels, which points
[Kernel-packages] [Bug 1887607] Re: NFSv4.1: Interrupted connections cause high bandwidth RPC ping-pong between client and server
** Description changed: BugLink: https://bugs.launchpad.net/bugs/1887607 [Impact] There is a bug in NFS v4.1 that causes a large amount of RPC calls between a client and server when a previous RPC call is interrupted. This uses a large amount of bandwidth and can saturate the network. The symptoms are so: * On NFS clients: Attempts to access mounted NFS shares associated with the affected server block indefinitely. * On the network: - A storm of repeated RPCs between NFS client and server uses a lot of bandwidth. Each RPC is acknoledged by the server with an NFS4ERR_SEQ_MISORDERED error. + A storm of repeated RPCs between NFS client and server uses a lot of bandwidth. Each RPC is acknowledged by the server with an NFS4ERR_SEQ_MISORDERED error. * Other NFS clients connected to the same NFS server: Performance drops dramatically. This occurs during a "false retry", when a client attempts to make a new RPC call using a slot+sequence number that references an older, cached call. This happens when a user process interrupts an RPC call that is in progress. I had previously fixed this for Disco in bug 1828978, and now a customer has run into the issue in Bionic. A reproducer is supplied in the testcase section, which was something missing from bug 1828978, since we - never determined how the issue actually occured back then. + never determined how the issue actually occurred back then. [Fix] This was fixed in 5.1 upstream with the below commit: commit 3453d5708b33efe76f40eca1c0ed60923094b971 Author: Trond Myklebust Date: Wed Jun 20 17:53:34 2018 -0400 Subject: NFSv4.1: Avoid false retries when RPC calls are interrupted The fix is to pre-emptively increment the sequence number if an RPC call is interrupted, and to address corner cases we interpret the - NFS4ERR_SEQ_MISORDERED error as a sign we need to locate an approperiate + NFS4ERR_SEQ_MISORDERED error as a sign we need to locate an appropriate sequence number between the value we sent, and the last successfully acked SEQUENCE call. The commit also requires two fixup commits, which landed in 5.5 and 5.8-rc6 respectively: commit 5c441544f045e679afd6c3c6d9f7aaf5fa5f37b0 Author: Trond Myklebust Date: Wed Nov 13 08:34:00 2019 +0100 Subject: NFSv4.x: Handle bad/dead sessions correctly in nfs41_sequence_process() commit 913fadc5b105c3619d9e8d0fe8899ff1593cc737 Author: Anna Schumaker Date: Wed Jul 8 10:33:40 2020 -0400 Subject: NFS: Fix interrupted slots by sending a solo SEQUENCE operation Commits 3453d5708b33efe76f40eca1c0ed60923094b971 and 913fadc5b105c3619d9e8d0fe8899ff1593cc737 require small backports to bionic, as struct rpc_cred changed to const struct cred in 5.0, and the backports swap them back to struct rpc_cred since that is how 4.15 works. [Testcase] You will need four machines. The first, is a kerberos KDC. Set up Kerberos correctly and create new service principals for the NFS server and for the client. I used: nfs/nfskerb.mydomain.com and nfs/client.mydomain.com. The second machine will be a NFS server with the krb5p share. Add the nfs server kerberos keys to the system's keytab, and set up a NFS server that exports a directory with sec=krb5p. Example export: /mnt/secretfolder *.mydomain.com(rw,sync,no_subtree_check,sec=krb5p) The third machine is a regular NFS server. Export a directory with normal sec=sys security. Example export: /mnt/sharedfolder *.mydomain.com(rw,sync) The fourth is a desktop machine. Add the client kerberos keys to the system's keytab. Mount both NFS shares, making sure to use the NFS v4.2 protocol. I used the commands: mount -t nfs4 nfskerb.mydomain.com:/mnt/secretfolder /mnt/secretfolder_client/ mount -t nfs4 nfs.mydomain.com:/mnt/sharedfolder /mnt/sharedfolder_client Check "mount -l" to ensure that NFS v4.2 is used: nfskerb.mydomain.com:/mnt/secretfolder on /mnt/secretfolder_client type nfs4 (rw,relatime,vers=4.2,<...>,sec=krb5p,<...>) nfs.mydomain.com:/mnt/sharedfolder on /mnt/sharedfolder_client type nfs4 (rw,relatime,vers=4.2,<...>,sec=sys,<...>) Generate some files full of random data. I found 20MB from /dev/random works great. Open each NFS share up in tabs in Nautilus. Copy the random data files to the sec=sys NFS share. When they are done, one at a time cut and then paste the file into the sec=krb5p NFS share. The bug will trigger either on the first, or subsequent tries, but less than 10 tries are needed usually. There is a test kernel available in the following PPA: https://launchpad.net/~mruffell/+archive/ubuntu/sf285439-test If you install the test kernel, files will cut and paste correctly, and NFS will work as expected. [Regression Potential] The changes are localised to NFS v4.1 and v4.2 only, and other versions of NFS are not affected. If a regression occurs, users
[Kernel-packages] [Bug 1889342] [NEW] Thunderbolt Dock Loses Monitors
Public bug reported: After a suspend or locking the only way to regain external monitors is to unplug and replug the thunderbolt dock back in. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-42-generic 5.4.0-42.46 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: john 2682 F pulseaudio /dev/snd/controlC0: john 2682 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jul 29 00:22:26 2020 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 InstallationDate: Installed on 2020-07-13 (15 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. XPS 13 9300 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=5e141eb0-e03b-4c39-b826-f94e0d2715ea ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/08/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.11 dmi.board.name: 0WX9VX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.11:bd05/08/2020:svnDellInc.:pnXPS139300:pvr:rvnDellInc.:rn0WX9VX:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9300 dmi.product.sku: 096D dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug 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/1889342 Title: Thunderbolt Dock Loses Monitors Status in linux package in Ubuntu: Confirmed Bug description: After a suspend or locking the only way to regain external monitors is to unplug and replug the thunderbolt dock back in. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-42-generic 5.4.0-42.46 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: john 2682 F pulseaudio /dev/snd/controlC0: john 2682 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jul 29 00:22:26 2020 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 InstallationDate: Installed on 2020-07-13 (15 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. XPS 13 9300 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=5e141eb0-e03b-4c39-b826-f94e0d2715ea ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/08/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.11 dmi.board.name: 0WX9VX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.11:bd05/08/2020:svnDellInc.:pnXPS139300:pvr:rvnDellInc.:rn0WX9VX:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9300 dmi.product.sku: 096D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1889342/+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 1889342] 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/1889342 Title: Thunderbolt Dock Loses Monitors Status in linux package in Ubuntu: Confirmed Bug description: After a suspend or locking the only way to regain external monitors is to unplug and replug the thunderbolt dock back in. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-42-generic 5.4.0-42.46 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: john 2682 F pulseaudio /dev/snd/controlC0: john 2682 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jul 29 00:22:26 2020 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 InstallationDate: Installed on 2020-07-13 (15 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. XPS 13 9300 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=5e141eb0-e03b-4c39-b826-f94e0d2715ea ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/08/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.11 dmi.board.name: 0WX9VX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.11:bd05/08/2020:svnDellInc.:pnXPS139300:pvr:rvnDellInc.:rn0WX9VX:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9300 dmi.product.sku: 096D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1889342/+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 1878574] Re: very slow boot with new kernel 5.3.0-51
[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/1878574 Title: very slow boot with new kernel 5.3.0-51 Status in linux package in Ubuntu: Expired Bug description: I already reported the but using "ubuntu-bug linux" but could see nowhere to tell you what the problem actually was. In summary it is relatively new system, 18.04.4LTS 64bit and Maté 1.20.1 dual-booting with Windows 10 v.1909, built on a Gigabyte Aorus B450M mainboard, Ryzen 5 3400G with Radeon Vega Graphics × 8, Kingston A2000 M2 main drive and a supplementary 4TB data drive. A wired connexion to BT Hub 6 via BT Powerline is used and gives no trouble on any other system. The system started with kernel 5.3.0-46 generic and was fine for a few months, booting in a few seconds. A couple of days ago the kernel upgraded itself to 5.3.0-51 generic and boot immediately became a minute or more. Reverting to kernel 5.3.0-46 generic restores the fast boot time. I can continue like this for a while but my main fear is that when the LTS update to 20.04 arrives the new kernel will contain the bug and reversion to 5.3.0-46 will no longer be possible. I attach several files, tarred because you do not seem to provide the facility to attach more then one file. There are a copy of the current fstab, the output of hwinfo (taken with kernel v.51) and for each of the two kernels the data asked for on the Ubuntu website. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: david 2069 F pulseaudio /dev/snd/controlC0: david 2069 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-01-05 (129 days ago) InstallationMedia: Ubuntu-MATE 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IwConfig: eno1 no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. B450 AORUS M Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-51-generic root=UUID=ea9bdbd1-0964-411e-b2c3-45fad2b77eae ro quiet splash fastboot vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-51-generic N/A linux-backports-modules-5.3.0-51-generic N/A linux-firmware1.173.18 RfKill: Tags: bionic Uname: Linux 5.3.0-51-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/22/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F41 dmi.board.asset.tag: Default string dmi.board.name: B450 AORUS M dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF41:bd07/22/2019:svnGigabyteTechnologyCo.,Ltd.:pnB450AORUSM:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450AORUSM:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: B450 AORUS M dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1878574/+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 1852084] Re: Backlight brightness not working correctly after waking from Suspend Mode
[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/1852084 Title: Backlight brightness not working correctly after waking from Suspend Mode Status in linux package in Ubuntu: Expired Bug description: The brightness level works correctly, but when the system goes to sleep mode and then I wake it up, I am not able to increase/decrease the brightness level using the keyboard controls (Fn + F11/F12), it works as a On/Off switch pretty much. When it wakes up, the brightness level is the same level as it was before entering the suspend mode. But when I try to lower the brightness level (through the keyboard controls), it completely shuts off, going to the lowest level directly (pretty much shutting off the screen), even though it is not even close to that on the slider control. And then, when I increase the brightness level (on the keyboard), it goes back to the previous level, working like a On/Off switch instead of a smooth operation. This looks to be related to the kernel, as the GUI (GNOME) presents the slider control correctly, but the setting isn't been correctly applied. On the slider control on the pop-up box on the top right corner (GNOME 3.34), when I change the level, it works correctly, just as it should. But, when I try to use the keyboard controls (Fn + F11/F12), the issue presented previously happens again. The only way to fix that bug is restarting the system. Again, this just happens when I put the system in Suspend Mode. System Info: 1) Description: Ubuntu 19.10 Release: 19.10 2) Hardware: CPU: AMD Ryzen 5 2500U GPU: AMD Raven Ridge (Vega 8) Laptop model: Lenovo IdeaPad 330S (330S-15ARR) ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-19-generic 5.3.0-19.20 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: matheus1379 F pulseaudio /dev/snd/controlC0: matheus1379 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Nov 11 10:06:32 2019 InstallationDate: Installed on 2019-09-22 (49 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 81JQ ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic root=UUID=0f9fdad5-0ee7-4039-acba-801eda1522f0 ro iommu=soft quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-19-generic N/A linux-backports-modules-5.3.0-19-generic N/A linux-firmware1.183.1 SourcePackage: linux UpgradeStatus: Upgraded to eoan on 2019-10-15 (26 days ago) dmi.bios.date: 05/22/2019 dmi.bios.vendor: LENOVO dmi.bios.version: 7WCN37WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40679WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 330S-15ARR dmi.modalias: dmi:bvnLENOVO:bvr7WCN37WW:bd05/22/2019:svnLENOVO:pn81JQ:pvrLenovoideapad330S-15ARR:rvnLENOVO:rnLNVNB161216:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad330S-15ARR: dmi.product.family: ideapad 330S-15ARR dmi.product.name: 81JQ dmi.product.sku: LENOVO_MT_81JQ_BU_idea_FM_ideapad 330S-15ARR dmi.product.version: Lenovo ideapad 330S-15ARR dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1852084/+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 1880103] Re: Awaking problem after suspend mode still happens
[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/1880103 Title: Awaking problem after suspend mode still happens Status in linux package in Ubuntu: Expired Bug description: 101 kernel seems to be better than 99, when the problem happened almost every time. Nevertheless, it happened again with 2+days uptime and suspending over night. Maybe it depends on my wireless keyboard? I tried Alt+SysRq reisub twice, but it didn't work. Mint Cinnamon 19.1, desktop. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC2D0c: waldi 1668 F...m pulseaudio /dev/snd/controlC2: waldi 1668 F pulseaudio /dev/snd/controlC0: waldi 1668 F pulseaudio /dev/snd/controlC1: waldi 1668 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.1 HibernationDevice: RESUME=UUID=018b3f92-7678-b1d9-8157-f8388f5198a2 InstallationDate: Installed on 2019-02-27 (449 days ago) InstallationMedia: Linux Mint 19.1 "Tessa" - Release amd64 20181217 IwConfig: lono wireless extensions. enp6s0no wireless extensions. enp5s0no wireless extensions. MachineType: System manufacturer System Product Name Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-101-generic root=UUID=e74e78ea-7a9d-41a9-839b-e32c0343041f ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-101.102-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-101-generic N/A linux-backports-modules-4.15.0-101-generic N/A linux-firmware 1.173.18 RfKill: Tags: tessa Uname: Linux 4.15.0-101-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 01/18/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0501 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8H61-M LX2 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0501:bd01/18/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H61-MLX2:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1880103/+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 1879760] Re: PCI/internal sound card 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/1879760 Title: PCI/internal sound card not detected Status in linux package in Ubuntu: Expired Bug description: after updating ubuntu kernel pc cant detect sound its show dummy output but when i select from boot previous kernel the sound working ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed May 20 21:20:11 2020 InstallationDate: Installed on 2020-05-10 (10 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/03/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1302 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: RAMPAGE V EXTREME dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1302:bd03/03/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnRAMPAGEVEXTREME:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879760/+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 1878338] Re: Laptop freezes whenever it runs out of battery
[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/1878338 Title: Laptop freezes whenever it runs out of battery Status in linux package in Ubuntu: Expired Bug description: New behaviour for Ubuntu 20.04 LTS - as soon as it runs out of battery, the laptop locks up. Any audio that was playing will be played repeatedly on a short loop. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-29-generic 5.4.0-29.33 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vadi 3163 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed May 13 07:40:48 2020 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=8c0e25d4-6e36-428e-b354-4c71b99db752 InstallationDate: Installed on 2017-02-15 (1182 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Dell Inc. Latitude E7470 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-29-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-29-generic N/A linux-backports-modules-5.4.0-29-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-05-07 (5 days ago) dmi.bios.date: 10/08/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.22.8 dmi.board.name: 0T6HHJ dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.22.8:bd10/08/2019:svnDellInc.:pnLatitudeE7470:pvr:rvnDellInc.:rn0T6HHJ:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: Latitude dmi.product.name: Latitude E7470 dmi.product.sku: 06DC dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1878338/+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 1877388] Re: If DVD drive is present system very often fails to start-up
[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/1877388 Title: If DVD drive is present system very often fails to start-up Status in linux package in Ubuntu: Expired Bug description: Whenever I power down, upon next boot the system just hangs with Ubuntu at the bottom of the screen and the circle above going around and around forever. It happens nearly every ime I power down, but not every single time. Rebooting rather that powering down works quite often. At first when thing hung I would just hard power off by holding down the power key. Then I'd use the live usb I installed with to run Disks app. More often than not the vfat W95 FAT32 partition at sda1 was damaged. The first repair would fail. The second repair would succeed. And then I'd be able to boot into my system again. After chatting about it a little with EriC^^ in #ubuntu on IRC I learned how to do Alt+Fn+PrtSc S, U, B or S, U, O. Sometimes just doing either of those on the hang screen would result in it booting up fine next time. Sometimes not. After installing 20.04 (a fresh install on a brand new Samsung 860 EVO 1TB sdd hard drive) I copied back all the files in my home direct that I'd backed from 18.04, including hidden files. This confused Firefox so I had to delete related folders and then unintall and reinstall to stop Firefox being confused. This might have nothing whatsoever to do with this issue, just mentioning it just in case something else is similarly confused. EriC^^ suggested I try adding another user and seeing if the issue went away. On the first test (and some but not all subsequent tests) it did seem that TestUser could power down and reboot fine. But actually it didn't seem that different. I powered down, rebooted, used live usb to repair Disk over and over again for hours trying to find a pattern as to when it happened and when it didn't, but failed to find any fixed pattern. Eventually at one point it was taking a while to power down (or reboot, I forget) and so I hit Esc and spotted that it had failed to unmount /cdrom ... ... so then I thought I'd try completely removing my DVD/CDRW drive and that made the issue go away. Before filing this I put the DVD drive back in (but haven't since rebooted), so not sure if apport has picked up it's details or not? Perhaps I'll need to re-file the bug after booting with it present? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: plymouth 0.9.4git20200323-0ubuntu6 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu May 7 15:09:23 2020 DefaultPlymouth: /usr/share/plymouth/themes/bgrt/bgrt.plymouth InstallationDate: Installed on 2020-04-26 (11 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 147e:2016 Upek Biometric Touchchip/Touchstrip Fingerprint Sensor Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub 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=ehci-pci/3p, 480M |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/8p, 480M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/3p, 480M |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/6p, 480M |__ Port 3: Dev 3, If 0, Class=Vendor Specific Class, Driver=, 12M MachineType: LENOVO 4384WCV ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=9ce94e7a-53bd-4507-ae31-93a2392b2da2 ro quiet splash vt.handoff=7 ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=9ce94e7a-53bd-4507-ae31-93a2392b2da2 ro quiet splash vt.handoff=7 SourcePackage: plymouth TextPlymouth: /usr/share/plymouth/themes/ubuntu-text/ubuntu-text.plymouth UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/26/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 6MET81WW (1.41 ) dmi.board.name: 4384WCV dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias:
[Kernel-packages] [Bug 1881176] Re: MEDIATEK MT7630e [14c3:7630] Subsystem [105b:e074] Wireless problem in my laptop
[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/1881176 Title: MEDIATEK MT7630e [14c3:7630] Subsystem [105b:e074] Wireless problem in my laptop Status in linux package in Ubuntu: Expired Bug description: dont have a wireless driver to update OS, before have connection to wireless internet but after the update no. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-33-generic 5.4.0-33.37 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: agreda 1661 F pulseaudio /dev/snd/controlC1: agreda 1661 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu May 28 13:13:16 2020 InstallationDate: Installed on 2020-05-27 (1 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) IwConfig: lono wireless extensions. enx00e04c3638fe no wireless extensions. docker0 no wireless extensions. MachineType: ASUSTeK COMPUTER INC. TP300LA ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=8ca40dff-7c72-4b88-9b61-147718b3aadb ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-33-generic N/A linux-backports-modules-5.4.0-33-generic N/A linux-firmware1.187 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/16/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: TP300LA.206 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: TP300LA 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.:bvrTP300LA.206:bd04/16/2019:svnASUSTeKCOMPUTERINC.:pnTP300LA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnTP300LA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: TP dmi.product.name: TP300LA dmi.product.sku: ASUS-NotebookSKU 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/1881176/+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 1881062] Re: Mouse pointer disappeared after upgrade
[Expired for xorg-server (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg-server (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/1881062 Title: Mouse pointer disappeared after upgrade Status in linux package in Ubuntu: Expired Status in xorg-server package in Ubuntu: Expired Bug description: Mouse vendor: Elecom Mouse name: Deft M-DT20R S/N 99011158 S/N 9700261B I have two sets of this model and both are not working any more. Wireless USB mouse stopped working after 'sudo apt upgrade' on 0:00 UTC 28th May 2020. I also upgraded BIOS of ThinkStation P500 from A4KT89US to A4KTA7US just an hour before the upgrade. However I plugged in an old wired Elecom USB mouse and this is working. And also I tried another wireless USB mouse Logicool M570, this model is working except the left-click or right-click (means unstable). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-34.38-generic 5.4.41 Uname: Linux 5.4.0-34-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..03.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:03: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 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity:Unity7:ubuntu Date: Thu May 28 13:14:27 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GM107GL [Quadro K2200] [10de:13ba] (rev a2) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation GM107GL [Quadro K2200] [10de:1097] InstallationDate: Installed on 2020-05-25 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 30A6S45A16 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-34-generic root=UUID=822191be-6b70-4841-97dc-e4c008d418b2 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/13/2020 dmi.bios.vendor: LENOVO dmi.bios.version: A4KTA7AUS dmi.board.name: 102F dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN 3425060692537 dmi.chassis.type: 7 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnLENOVO:bvrA4KTA7AUS:bd04/13/2020:svnLENOVO:pn30A6S45A16:pvrThinkStationP500:rvnLENOVO:rn102F:rvrSDK0J40705WIN3425060692537:cvnToBeFilledByO.E.M.:ct7:cvrToBeFilledByO.E.M.: dmi.product.family: ThinkStation P500 dmi.product.name: 30A6S45A16 dmi.product.sku: LENOVO_MT_30A6_BU_Think_FM_ThinkStation P500 dmi.product.version: ThinkStation P500 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1 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/linux/+bug/1881062/+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 1881256] Re: TOUCHPAD NOT WORKING
[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/1881256 Title: TOUCHPAD NOT WORKING Status in linux package in Ubuntu: Expired Bug description: fresh install of ubuntu 20.04 touch screen works but touchpad not working at all make is acer model V3-112P ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-31-generic 5.4.0-31.35 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: garyfez 958 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri May 29 09:12:23 2020 InstallationDate: Installed on 2020-05-20 (9 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Acer Aspire V3-112P ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic root=UUID=0b1f79f9-ec31-444b-815b-07c46cb8d3f0 ro quiet splash RelatedPackageVersions: linux-restricted-modules-5.4.0-31-generic N/A linux-backports-modules-5.4.0-31-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/20/2015 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.16 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: R2 dmi.board.vendor: Acer dmi.board.version: Type2 - A01 Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.16:bd10/20/2015:svnAcer:pnAspireV3-112P:pvrV1.16:rvnAcer:rnR2:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: BTM dmi.product.name: Aspire V3-112P dmi.product.sku: Aspire V3-112P_0843_1_16 dmi.product.version: V1.16 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881256/+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 1881062] Re: Mouse pointer disappeared after upgrade
[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/1881062 Title: Mouse pointer disappeared after upgrade Status in linux package in Ubuntu: Expired Status in xorg-server package in Ubuntu: Expired Bug description: Mouse vendor: Elecom Mouse name: Deft M-DT20R S/N 99011158 S/N 9700261B I have two sets of this model and both are not working any more. Wireless USB mouse stopped working after 'sudo apt upgrade' on 0:00 UTC 28th May 2020. I also upgraded BIOS of ThinkStation P500 from A4KT89US to A4KTA7US just an hour before the upgrade. However I plugged in an old wired Elecom USB mouse and this is working. And also I tried another wireless USB mouse Logicool M570, this model is working except the left-click or right-click (means unstable). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-34.38-generic 5.4.41 Uname: Linux 5.4.0-34-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..03.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:03: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 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity:Unity7:ubuntu Date: Thu May 28 13:14:27 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GM107GL [Quadro K2200] [10de:13ba] (rev a2) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation GM107GL [Quadro K2200] [10de:1097] InstallationDate: Installed on 2020-05-25 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 30A6S45A16 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-34-generic root=UUID=822191be-6b70-4841-97dc-e4c008d418b2 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/13/2020 dmi.bios.vendor: LENOVO dmi.bios.version: A4KTA7AUS dmi.board.name: 102F dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN 3425060692537 dmi.chassis.type: 7 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnLENOVO:bvrA4KTA7AUS:bd04/13/2020:svnLENOVO:pn30A6S45A16:pvrThinkStationP500:rvnLENOVO:rn102F:rvrSDK0J40705WIN3425060692537:cvnToBeFilledByO.E.M.:ct7:cvrToBeFilledByO.E.M.: dmi.product.family: ThinkStation P500 dmi.product.name: 30A6S45A16 dmi.product.sku: LENOVO_MT_30A6_BU_Think_FM_ThinkStation P500 dmi.product.version: ThinkStation P500 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1 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/linux/+bug/1881062/+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 1877757] Re: No sound, Dummy output on Acer Swift 3 SF314-57G with Ice Lake core-i7 CPU
** Description changed: + [Impact] + On this machine, after booting up, there is no valid sound card, the + gnome-control-center shows a dummy output only. check the dmesg, the alsa + sof driver fails to initialize. + + [Fix] + Backport a patch from upstream, after applying this patch, the sof driver + will not fail anymore even the codec driver is hda_generic + + [Test Case] + A couple of users already test this patch on their machines, after booting + up, there is a valid sound card, and could output sound from output devices. + + [Regression Risk] + Low, this is cherry-picked from upstream, and this just adds a new kind of + codec (generic) support, and a couple of ubuntu users already verified this + patch. + + New focal installation on a new Acer Swift 3 laptop with core i7-1065G7. No sound detected, KDE/pavucontrol shows Dummy output. External headset also not detected. I've googled around and tried to reinstall alsa and pulseaudio, tried alsa force-reload as well. Nothing helps. With snd_hda_intel.dmic_detect=0 speakers start working but microphone is not detected. External headset detected with both headphones and mic. I use this as a workaround for a time being. I've checked https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860697 bug. It is closed and use recent kernel and firmware but it does not fix my issue. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-29-generic 5.4.0-29.33 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Sat May 9 18:56:15 2020 InstallationDate: Installed on 2020-04-24 (15 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Acer Swift SF314-57G ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-29-generic root=UUID=faf6a132-de60-44fa-a1a7-4cce8ef83b87 ro quiet splash vt.handoff=7 RelatedPackageVersions: - linux-restricted-modules-5.4.0-29-generic N/A - linux-backports-modules-5.4.0-29-generic N/A - linux-firmware1.187 + linux-restricted-modules-5.4.0-29-generic N/A + linux-backports-modules-5.4.0-29-generic N/A + linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/24/2019 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.09 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Floris_IL dmi.board.vendor: IL dmi.board.version: V1.09 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.09:bd09/24/2019:svnAcer:pnSwiftSF314-57G:pvrV1.09:rvnIL:rnFloris_IL:rvrV1.09:cvnAcer:ct10:cvrChassisVersion: dmi.product.family: Swift 3 dmi.product.name: Swift SF314-57G dmi.product.sku: dmi.product.version: V1.09 dmi.sys.vendor: Acer ** Changed in: linux (Ubuntu Focal) Assignee: (unassigned) => Hui Wang (hui.wang) ** Changed in: linux-oem-5.6 (Ubuntu Focal) Assignee: (unassigned) => Hui Wang (hui.wang) -- 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/1877757 Title: No sound, Dummy output on Acer Swift 3 SF314-57G with Ice Lake core-i7 CPU Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.6 package in Ubuntu: New Status in linux source package in Focal: New Status in linux-oem-5.6 source package in Focal: New Bug description: [Impact] On this machine, after booting up, there is no valid sound card, the gnome-control-center shows a dummy output only. check the dmesg, the alsa sof driver fails to initialize. [Fix] Backport a patch from upstream, after applying this patch, the sof driver will not fail anymore even the codec driver is hda_generic [Test Case] A couple of users already test this patch on their machines, after booting up, there is a valid sound card, and could output sound from output devices. [Regression Risk] Low, this is cherry-picked from upstream, and this just adds a new kind of codec (generic) support, and a couple of ubuntu users already verified this patch. New focal installation on a new Acer Swift 3 laptop with core i7-1065G7. No sound detected, KDE/pavucontrol shows Dummy output. External headset also not detected. I've googled around and tried to reinstall alsa and pulseaudio, tried alsa force-reload as well. Nothing helps. With snd_hda_intel.dmic_detect=0 speakers start working but microphone is not detected. External headset
[Kernel-packages] [Bug 1887607] Re: NFSv4.1: Interrupted connections cause high bandwidth RPC ping-pong between client and server
** Summary changed: - NFS4.2: Cutting and Pasting files from NFS sec=sys to NFS sec=krb5p causes NFS to hang + NFSv4.1: Interrupted connections cause high bandwidth RPC ping-pong between client and server ** Description changed: BugLink: https://bugs.launchpad.net/bugs/1887607 [Impact] - If you have a desktop system, with two NFS v4.2 mounts: - - One that uses the baseline IP based security, aka sec=sys, - - and the other that uses Kerberos sec=krb5p based security, + There is a bug in NFS v4.1 that causes a large amount of RPC calls + between a client and server when a previous RPC call is interrupted. + This uses a large amount of bandwidth and can saturate the network. - If you try and cut a file from the normal NFS mount, and paste it to a - directory on the kerberos krb5p mount (using Nautilus), the NFS - subsystem will lock up, Nautilus will hang, and the file won't be moved. + The symptoms are so: - The problem only reproduces if you cut and paste. Copying and pasting - does not trigger any problems. Using mv in terminal doesn't reproduce - either, you need to use Nautilus. + * On NFS clients: + Attempts to access mounted NFS shares associated with the affected server block indefinitely. - The issue was introduced into 4.15.0-60-generic, by the commit: + * On the network: + A storm of repeated RPCs between NFS client and server uses a lot of bandwidth. Each RPC is acknoledged by the server with an NFS4ERR_SEQ_MISORDERED error. - commit 594d1644cd59447f4fceb592448d5cd09eb09b5e - Author: Chris Perl - Date: Mon Dec 17 10:56:38 2018 -0500 - Subject: NFS: nfs_compare_mount_options always compare auth flavors. - Link: https://github.com/torvalds/linux/commit/594d1644cd59447f4fceb592448d5cd09eb09b5e + * Other NFS clients connected to the same NFS server: + Performance drops dramatically. - It was backported to 4.15.0-60-generic from upstream -stable, and landed - in 4.4.175, 4.14.99 and 4.19.21. The commit itself does not actually - cause the problem, it simply removes a check for NFS server security - settings, which simply reveals a broken codepath which the testcase - triggers. + This occurs during a "false retry", when a client attempts to make a new + RPC call using a slot+sequence number that references an older, cached + call. This happens when a user process interrupts an RPC call that is in + progress. - Xenial 4.4.0-185-generic is not affected, only Bionic 4.15.0-60-generic - onward. + I had previously fixed this for Disco in bug 1828978, and now a customer + has run into the issue in Bionic. A reproducer is supplied in the + testcase section, which was something missing from bug 1828978, since we + never determined how the issue actually occured back then. [Fix] - The fix landed in 5.1-rc1, in the following commit: + This was fixed in 5.1 upstream with the below commit: - commit 02ef04e432babf8fc703104212314e54112ecd2d - Author: Chuck Lever - Date: Mon Feb 11 11:25:25 2019 -0500 - Subject: NFS: Account for XDR pad of buf->pages - Link: https://github.com/torvalds/linux/commit/02ef04e432babf8fc703104212314e54112ecd2d + commit 3453d5708b33efe76f40eca1c0ed60923094b971 + Author: Trond Myklebust + Date: Wed Jun 20 17:53:34 2018 -0400 + Subject: NFSv4.1: Avoid false retries when RPC calls are interrupted - The above commit more or less relies on the below commit as a - dependency, and is included in the SRU: + The fix is to pre-emptively increment the sequence number if an RPC call + is interrupted, and to address corner cases we interpret the + NFS4ERR_SEQ_MISORDERED error as a sign we need to locate an approperiate + sequence number between the value we sent, and the last successfully + acked SEQUENCE call. - commit cf500bac8fd48b57f38ece890235923d4ed5ee91 - Author: Chuck Lever - Date: Mon Feb 11 11:25:20 2019 -0500 - Subject: SUNRPC: Introduce rpc_prepare_reply_pages() - Link: https://github.com/torvalds/linux/commit/cf500bac8fd48b57f38ece890235923d4ed5ee91 + The commit also requires two fixup commits, which landed in 5.5 and + 5.8-rc6 respectively: - Also, as Andrea Righi pointed out, we need the following fixes commit: + commit 5c441544f045e679afd6c3c6d9f7aaf5fa5f37b0 + Author: Trond Myklebust + Date: Wed Nov 13 08:34:00 2019 +0100 + Subject: NFSv4.x: Handle bad/dead sessions correctly in nfs41_sequence_process() - commit 29e7ca715f2a0b6c0a99b1aec1b0956d1f271955 - Author: Chuck Lever - Date: Tue Apr 9 10:44:16 2019 -0400 - Subject: NFS: Fix handling of reply page vector - Link: https://github.com/torvalds/linux/commit/29e7ca715f2a0b6c0a99b1aec1b0956d1f271955 + commit 913fadc5b105c3619d9e8d0fe8899ff1593cc737 + Author: Anna Schumaker + Date: Wed Jul 8 10:33:40 2020 -0400 + Subject: NFS: Fix interrupted slots by sending a solo SEQUENCE operation - It appears that some NFS calls return a NFS payload which is not a - multiple of 4 bytes, but any payload sent over the network needs to be - padded to an exact multiple
[Kernel-packages] [Bug 1882248] Re: [SRU] plug headset won't proper reconfig ouput to it on machine with default output
Manually download pulseaduio 1:11.1-1ubuntu7.10 and kernel 4.15.0-1093-oem into oem bionic image tested on the target that previously can reproduce this issue. In first boot, plug-in headset, and pop-up windows is properly display. After select headset, the output is correctly selected, and use the test in gnome-control-center it can properly output left/right audio. So I verified passed. ** Changed in: oem-priority Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1882248 Title: [SRU] plug headset won't proper reconfig ouput to it on machine with default output Status in HWE Next: New Status in OEM Priority Project: Fix Committed Status in linux-oem package in Ubuntu: New Status in pulseaudio package in Ubuntu: Fix Released Status in linux-oem source package in Bionic: Fix Released Status in pulseaudio source package in Bionic: Fix Committed Bug description: This is for pulseaudio bionic: [Impact] On a Dell machine without internal spk and internal mic, after freshly install the bionic on it, the active profile is Off, after users plug a headset to it and users select the headset from the pop-up dialogue, users expect the profile changes to analog-stereo (headset is on it), but the active_profile is still Off. [Fix] Upstream already has a patch to fix it, cherrypiack that patch to bionic. And that patch is already in the eoan, focal, ... [Test Case] freshly install the bionic with this patch on that dell machine, plug headset and select the headset from UI, the profile changes to analog-stereo, and play some sound, we could hear it from the headset [Regression Risk] Low, this patch is already in the upstream for a long time, and it is already in the eoan and focal. For linux kernel (oem-b): [Impact] On a Dell machine without internal spk and internal mic, after freshly install the bionic on it, and users plug a headset, the sound couldn't output from headset. [Fix] reverse the order of headset mic and headphone mic [Test Case] freshly install the bionic with this patch on that dell machine, plug headset and play sound, we could hear the sound from headset. [Regression Risk] Low, this patch only affects the machine without internal mic and internal spk, and I already tested this patch on the machine without internal mic and internal spk, it worked well. target machine does not have built-in speaker, and the monitor does not have an audio output (like d-sub VGA) As first boot, there will be a "dummy output" in g-c-c. After plug-in headset, there will be a headset appear in g-c-c, but it won't be automatically selected even it's chosen in the pop-up window. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1882248/+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 1791427] Re: Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1 Carbon 6th
Yea they need to come from the same system. I guess just stick to s2idle then. ** Changed in: linux (Ubuntu) Status: Triaged => 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/1791427 Title: Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1 Carbon 6th Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu 18.04.1 Terminology in case we use different terms: touchpad - just the rectangular touch-sensitive surface below the keyboard (xinput lists it as Synaptics TM3288-011) trackpoint - the red thingy built into the keyboard + 3 physical buttons below the keyboard (trackpoint and buttons are integrated together; listed in xinput as TPPS/2 Elan TrackPoint) On September 7th, 2018, Lenovo has issued a BIOS update (v1.30), which enables proper S3 deep sleep state - users no longer have to patch DSDT tables to get it. It can be enabled in the BIOS settings. In X1 carbon 6th generation models that have NFC, when laptop wakes from suspend by opening the lid, in most cases both touchpad and trackpoint stop working completely. They are also no longer listed when running xinput command. Sometimes just one of them stops working, usually the trackpoint. In some rare cases it is possible to bring them back by using these commands: echo -n none > /sys/devices/platform/i8042/serio1/drvctl echo -n reconnect > /sys/devices/platform/i8042/serio1/drvctl rmmod psmouse modprobe psmouse These worked properly when waking up from S2Idle sleep state (had these in a script that runs after waking the machine from suspend), but with S3 deep sleep these rarely work and the only way to bring back touchpad and/or trackpoint is turning off the machine and turning it on (restart does not help). I could not find any pattern that would show when the input devices stop working or start working again using the commands mentioned above. It's completely random from my perspective. This is happening on the standard issue 4.15.0-33-generic kernel that shipped with my Ubuntu 18.04 (with updates), as well as with newer mainline kernels, such as the newest point versions of 4.17, 4.18 and 4.19 RC2. This happens regardless of whether "blacklist i2c_i801" is commented out in /etc/modprobe.d/blacklist.conf or not. It happens regardless of whether "psmouse.synaptics_intertouch=1" is passed as grub parameter. Presence of TLP does not make it better, nor worse. It appears that non-NFC models are not affected. I know at least one Arch Linux user who has the exact same model, but without this issue. I'm using synaptics driver (no libinput installed), he uses libinput and doesn't have synaptics, if that information is of any use. Libinput does not seem to help. This forum thread also has more details from users who updated their BIOS to get S3 suspend: https://forums.lenovo.com/t5/Linux- Discussion/X1-Carbon-Gen-6-cannot-enter-deep-sleep-S3-state-aka- Suspend-to/td-p/3998182/page/27 Another related thread: https://bbs.archlinux.org/viewtopic.php?id=236367 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-33-generic 4.15.0-33.36 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: maciej 2651 F...m pulseaudio /dev/snd/controlC0: maciej 2651 F pulseaudio CurrentDesktop: i3 Date: Sat Sep 8 13:45:43 2018 HibernationDevice: RESUME=UUID=3116dcb0-d91e-4b2a-8166-43b7a9a9d36e InstallationDate: Installed on 2018-07-21 (49 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 13d3:56b2 IMC Networks Bus 001 Device 002: ID 04b4:0060 Cypress Semiconductor Corp. Wireless optical mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20KH006KPB ProcFB: 0 EFI VGA 1 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-33-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash psmouse.synaptics_intertouch=1 vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-33-generic N/A linux-backports-modules-4.15.0-33-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/31/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET55W (1.30 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KH006KPB dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10
[Kernel-packages] [Bug 1889337] 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/1889337 Title: touchpad Status in linux package in Ubuntu: Confirmed Bug description: Touchpad on Lenovo t440s not functioning, listed as ps/2 generic touchpad in devices ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-42-generic 5.4.0-42.46 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alek 2383 F pulseaudio /dev/snd/controlC2: alek 2383 F pulseaudio /dev/snd/controlC1: alek 2383 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Jul 28 22:16:21 2020 MachineType: LENOVO 20AQ005QUS ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=deb11b00-3188-4914-a1e0-ad0d7d36cbe5 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/20/2014 dmi.bios.vendor: LENOVO dmi.bios.version: GJET77WW (2.27 ) dmi.board.asset.tag: Not Available dmi.board.name: 20AQ005QUS dmi.board.vendor: LENOVO dmi.board.version: 0B98401 PRO dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGJET77WW(2.27):bd05/20/2014:svnLENOVO:pn20AQ005QUS:pvrThinkPadT440s:rvnLENOVO:rn20AQ005QUS:rvr0B98401PRO:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T440s dmi.product.name: 20AQ005QUS dmi.product.sku: LENOVO_MT_20AQ_BU_Think_FM_ThinkPad T440s dmi.product.version: ThinkPad T440s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1889337/+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 1889337] [NEW] touchpad
Public bug reported: Touchpad on Lenovo t440s not functioning, listed as ps/2 generic touchpad in devices ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-42-generic 5.4.0-42.46 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alek 2383 F pulseaudio /dev/snd/controlC2: alek 2383 F pulseaudio /dev/snd/controlC1: alek 2383 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Jul 28 22:16:21 2020 MachineType: LENOVO 20AQ005QUS ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=deb11b00-3188-4914-a1e0-ad0d7d36cbe5 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/20/2014 dmi.bios.vendor: LENOVO dmi.bios.version: GJET77WW (2.27 ) dmi.board.asset.tag: Not Available dmi.board.name: 20AQ005QUS dmi.board.vendor: LENOVO dmi.board.version: 0B98401 PRO dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGJET77WW(2.27):bd05/20/2014:svnLENOVO:pn20AQ005QUS:pvrThinkPadT440s:rvnLENOVO:rn20AQ005QUS:rvr0B98401PRO:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T440s dmi.product.name: 20AQ005QUS dmi.product.sku: LENOVO_MT_20AQ_BU_Think_FM_ThinkPad T440s dmi.product.version: ThinkPad T440s dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug 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/1889337 Title: touchpad Status in linux package in Ubuntu: Confirmed Bug description: Touchpad on Lenovo t440s not functioning, listed as ps/2 generic touchpad in devices ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-42-generic 5.4.0-42.46 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alek 2383 F pulseaudio /dev/snd/controlC2: alek 2383 F pulseaudio /dev/snd/controlC1: alek 2383 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Jul 28 22:16:21 2020 MachineType: LENOVO 20AQ005QUS ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=deb11b00-3188-4914-a1e0-ad0d7d36cbe5 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/20/2014 dmi.bios.vendor: LENOVO dmi.bios.version: GJET77WW (2.27 ) dmi.board.asset.tag: Not Available dmi.board.name: 20AQ005QUS dmi.board.vendor: LENOVO dmi.board.version: 0B98401 PRO dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGJET77WW(2.27):bd05/20/2014:svnLENOVO:pn20AQ005QUS:pvrThinkPadT440s:rvnLENOVO:rn20AQ005QUS:rvr0B98401PRO:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T440s dmi.product.name: 20AQ005QUS dmi.product.sku: LENOVO_MT_20AQ_BU_Think_FM_ThinkPad T440s dmi.product.version: ThinkPad T440s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1889337/+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 1868243] Re: ld_abs+vlan_push/pop from ubuntu_bpf_jit will fail on X s390x
This is also affecting the net test in ubuntu_kernel_selftests on s390x,
as it will try to insert that module for the test. (test_bpf.sh)
** Tags added: sru-20200629 sru-20200720
** Tags added: ubuntu-kernel-selftests
** Summary changed:
- ld_abs+vlan_push/pop from ubuntu_bpf_jit will fail on X s390x
+ ld_abs+vlan_push/pop from test_bpf in ubuntu_bpf_jit will fail on X s390x
--
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/1868243
Title:
ld_abs+vlan_push/pop from test_bpf in ubuntu_bpf_jit will fail on X
s390x
Status in ubuntu-kernel-tests:
New
Status in linux package in Ubuntu:
Incomplete
Status in linux source package in Xenial:
Incomplete
Bug description:
Issue separated from bug 1768452
The ubuntu_bpf_jit will report the following failure on Xenial s390x:
* test_bpf: #250 BPF_MAXINSNS: ld_abs+vlan_push/pop FAIL to select_runtime
err=-524
This test has been moved to the test_verifier test in bpf of kselftests:
https://github.com/torvalds/linux/commit/93731ef086cee90af594e62874bb98ae6d6eee91
"Remove all eBPF tests involving LD_ABS/LD_IND from test_bpf.ko. Reason
is that the eBPF tests from test_bpf module do not go via BPF verifier
and therefore any instruction rewrites from verifier cannot take place.
Therefore, move them into test_verifier which runs out of user space,
so that verfier can rewrite LD_ABS/LD_IND internally in upcoming patches.
It will have the same effect since runtime tests are also performed from
there. This also allows to finally unexport bpf_skb_vlan_{push,pop}_proto
and keep it internal to core kernel."
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1868243/+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 1791427] Re: Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1 Carbon 6th
@Kai-Heng Do you need those two desmgs from one and the same machine? I will not provide that, because I have had enough of rebooting my non-working machine when I enable S3. I am happy to attach a S2Idle log, though. -- 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/1791427 Title: Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1 Carbon 6th Status in linux package in Ubuntu: Triaged Bug description: Ubuntu 18.04.1 Terminology in case we use different terms: touchpad - just the rectangular touch-sensitive surface below the keyboard (xinput lists it as Synaptics TM3288-011) trackpoint - the red thingy built into the keyboard + 3 physical buttons below the keyboard (trackpoint and buttons are integrated together; listed in xinput as TPPS/2 Elan TrackPoint) On September 7th, 2018, Lenovo has issued a BIOS update (v1.30), which enables proper S3 deep sleep state - users no longer have to patch DSDT tables to get it. It can be enabled in the BIOS settings. In X1 carbon 6th generation models that have NFC, when laptop wakes from suspend by opening the lid, in most cases both touchpad and trackpoint stop working completely. They are also no longer listed when running xinput command. Sometimes just one of them stops working, usually the trackpoint. In some rare cases it is possible to bring them back by using these commands: echo -n none > /sys/devices/platform/i8042/serio1/drvctl echo -n reconnect > /sys/devices/platform/i8042/serio1/drvctl rmmod psmouse modprobe psmouse These worked properly when waking up from S2Idle sleep state (had these in a script that runs after waking the machine from suspend), but with S3 deep sleep these rarely work and the only way to bring back touchpad and/or trackpoint is turning off the machine and turning it on (restart does not help). I could not find any pattern that would show when the input devices stop working or start working again using the commands mentioned above. It's completely random from my perspective. This is happening on the standard issue 4.15.0-33-generic kernel that shipped with my Ubuntu 18.04 (with updates), as well as with newer mainline kernels, such as the newest point versions of 4.17, 4.18 and 4.19 RC2. This happens regardless of whether "blacklist i2c_i801" is commented out in /etc/modprobe.d/blacklist.conf or not. It happens regardless of whether "psmouse.synaptics_intertouch=1" is passed as grub parameter. Presence of TLP does not make it better, nor worse. It appears that non-NFC models are not affected. I know at least one Arch Linux user who has the exact same model, but without this issue. I'm using synaptics driver (no libinput installed), he uses libinput and doesn't have synaptics, if that information is of any use. Libinput does not seem to help. This forum thread also has more details from users who updated their BIOS to get S3 suspend: https://forums.lenovo.com/t5/Linux- Discussion/X1-Carbon-Gen-6-cannot-enter-deep-sleep-S3-state-aka- Suspend-to/td-p/3998182/page/27 Another related thread: https://bbs.archlinux.org/viewtopic.php?id=236367 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-33-generic 4.15.0-33.36 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: maciej 2651 F...m pulseaudio /dev/snd/controlC0: maciej 2651 F pulseaudio CurrentDesktop: i3 Date: Sat Sep 8 13:45:43 2018 HibernationDevice: RESUME=UUID=3116dcb0-d91e-4b2a-8166-43b7a9a9d36e InstallationDate: Installed on 2018-07-21 (49 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 13d3:56b2 IMC Networks Bus 001 Device 002: ID 04b4:0060 Cypress Semiconductor Corp. Wireless optical mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20KH006KPB ProcFB: 0 EFI VGA 1 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-33-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash psmouse.synaptics_intertouch=1 vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-33-generic N/A linux-backports-modules-4.15.0-33-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/31/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET55W (1.30 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KH006KPB dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN
[Kernel-packages] [Bug 1889306] Re: Resuming from deep suspend on Thinkpad T14 crashes system (readonly filesystem)
Verified on the same T14 Gen 1 with Samsung NVME, not reproduced. BIOS version 19W. Could you update BIOS: https://pcsupport.lenovo.com/us/en/products/laptops-and-netbooks/thinkpad-t-series-laptops/thinkpad-t14-type-20s0-20s1/downloads/DS544549 After updated BIOS, please set BIOS -> optimized = Enabled then load default setting. After reboot change config -> power -> sleep = Linux. -- 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/1889306 Title: Resuming from deep suspend on Thinkpad T14 crashes system (readonly filesystem) Status in linux package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Make sure that "deep" suspend is used instead of `s2idle` suspend (`echo deep | sudo tee /sys/power/mem_sleep`). This is always the case when the "Power->Suspend State" is set to "Linux" instead of "Windows 10" in the BIOS. 2. Trigger suspend, e.g. with GUI or `systemctl suspend -i` 3. System suspends successfully. Power light starts fading in and out, as it should. 4. Wake up the system. This is only possible with the power button instead of keys, which is a difference from `s2idle` suspends. 5. Unlock lock screen 6. Notice that the system will behave buggy/abnormal as the filesystem is remounted as read-only. Shortly after resuming, applications will start to crash or show nonsensical output. Expected behavior: (From step 4) System wakes up and can be used normally. The main filesystem should of course be writable. Ubuntu version: 20.04, latest updates as of 2020-07-28 Kernel: Linux nicolai-t14 5.4.0-42-generic #46-Ubuntu SMP Fri Jul 10 00:24:02 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux Computer: Thinkpad T14 (Intel), M2 NVMe SSD `dmesg | grep ACPI | grep supports`: [0.511722] ACPI: (supports S0 S3 S4 S5) tlp: tlp was running during some tests but deactivated during others. The problem still appeared in both cases. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-42-generic 5.4.0-42.46 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: nicolai1472 F pulseaudio /dev/snd/controlC0: nicolai1472 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Jul 28 21:55:33 2020 HibernationDevice: RESUME=UUID=d4f9a6e6-e186-4b67-92fc-fb3bdf13921c resume_offset=34816 # Resume from /swapfile InstallationDate: Installed on 2020-06-12 (46 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20S1S06C00 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=d4f9a6e6-e186-4b67-92fc-fb3bdf13921c ro resume=UUID=d4f9a6e6-e186-4b67-92fc-fb3bdf13921c resume_offset=34816 quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/27/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2XET15W (1.05 ) dmi.board.asset.tag: Not Available dmi.board.name: 20S1S06C00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2XET15W(1.05):bd04/27/2020:svnLENOVO:pn20S1S06C00:pvrThinkPadT14Gen1:rvnLENOVO:rn20S1S06C00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T14 Gen 1 dmi.product.name: 20S1S06C00 dmi.product.sku: LENOVO_MT_20S1_BU_Think_FM_ThinkPad T14 Gen 1 dmi.product.version: ThinkPad T14 Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1889306/+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 1791427] Re: Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1 Carbon 6th
Can someone attach dmesg when it uses S2Idle and when it uses S3? -- 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/1791427 Title: Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1 Carbon 6th Status in linux package in Ubuntu: Triaged Bug description: Ubuntu 18.04.1 Terminology in case we use different terms: touchpad - just the rectangular touch-sensitive surface below the keyboard (xinput lists it as Synaptics TM3288-011) trackpoint - the red thingy built into the keyboard + 3 physical buttons below the keyboard (trackpoint and buttons are integrated together; listed in xinput as TPPS/2 Elan TrackPoint) On September 7th, 2018, Lenovo has issued a BIOS update (v1.30), which enables proper S3 deep sleep state - users no longer have to patch DSDT tables to get it. It can be enabled in the BIOS settings. In X1 carbon 6th generation models that have NFC, when laptop wakes from suspend by opening the lid, in most cases both touchpad and trackpoint stop working completely. They are also no longer listed when running xinput command. Sometimes just one of them stops working, usually the trackpoint. In some rare cases it is possible to bring them back by using these commands: echo -n none > /sys/devices/platform/i8042/serio1/drvctl echo -n reconnect > /sys/devices/platform/i8042/serio1/drvctl rmmod psmouse modprobe psmouse These worked properly when waking up from S2Idle sleep state (had these in a script that runs after waking the machine from suspend), but with S3 deep sleep these rarely work and the only way to bring back touchpad and/or trackpoint is turning off the machine and turning it on (restart does not help). I could not find any pattern that would show when the input devices stop working or start working again using the commands mentioned above. It's completely random from my perspective. This is happening on the standard issue 4.15.0-33-generic kernel that shipped with my Ubuntu 18.04 (with updates), as well as with newer mainline kernels, such as the newest point versions of 4.17, 4.18 and 4.19 RC2. This happens regardless of whether "blacklist i2c_i801" is commented out in /etc/modprobe.d/blacklist.conf or not. It happens regardless of whether "psmouse.synaptics_intertouch=1" is passed as grub parameter. Presence of TLP does not make it better, nor worse. It appears that non-NFC models are not affected. I know at least one Arch Linux user who has the exact same model, but without this issue. I'm using synaptics driver (no libinput installed), he uses libinput and doesn't have synaptics, if that information is of any use. Libinput does not seem to help. This forum thread also has more details from users who updated their BIOS to get S3 suspend: https://forums.lenovo.com/t5/Linux- Discussion/X1-Carbon-Gen-6-cannot-enter-deep-sleep-S3-state-aka- Suspend-to/td-p/3998182/page/27 Another related thread: https://bbs.archlinux.org/viewtopic.php?id=236367 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-33-generic 4.15.0-33.36 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: maciej 2651 F...m pulseaudio /dev/snd/controlC0: maciej 2651 F pulseaudio CurrentDesktop: i3 Date: Sat Sep 8 13:45:43 2018 HibernationDevice: RESUME=UUID=3116dcb0-d91e-4b2a-8166-43b7a9a9d36e InstallationDate: Installed on 2018-07-21 (49 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 13d3:56b2 IMC Networks Bus 001 Device 002: ID 04b4:0060 Cypress Semiconductor Corp. Wireless optical mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20KH006KPB ProcFB: 0 EFI VGA 1 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-33-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash psmouse.synaptics_intertouch=1 vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-33-generic N/A linux-backports-modules-4.15.0-33-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/31/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET55W (1.30 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KH006KPB dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias:
[Kernel-packages] [Bug 1854298] Re: ubuntu_unionmount_ovlfs failed on X/T-LTS-X with latest update in upstream testsuite
Contacted upstream, this issue has been fixed with the following commit: https://github.com/amir73il/unionmount-testsuite/commit/019085f43d7e6426378ccfd3deeb23e127449e3e ** Changed in: linux-signed (Ubuntu) Status: Confirmed => Invalid ** Changed in: ubuntu-kernel-tests Status: Triaged => Fix Released -- 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/1854298 Title: ubuntu_unionmount_ovlfs failed on X/T-LTS-X with latest update in upstream testsuite Status in ubuntu-kernel-tests: Fix Released Status in linux-signed package in Ubuntu: Invalid Bug description: A bisect shows this test is failing since commit 2104e51db38 (Simplify initialization of __upper) The test will fail with: *** *** ./run --ov --ts=0 rmtree *** TEST rmtree.py:4: Recursive remove populated lower dir with lower files - rmtree /mnt/a/dir100 *** *** ./run --ov --ts=0 rmtree-new *** TEST rmtree-new.py:4: Recursive remove populated lower dir with new subdir ./run --mkdir /mnt/a/dir100/b 0755 - rmtree /mnt/a/dir100 *** *** ./run --ov --ts=0 hard-link *** TEST hard-link.py:10: Hard link file ./run --link /mnt/a/foo100 /mnt/a/no_foo100 stderr: /mnt/a/foo100: File unexpectedly on upper layer For the complete test log, please refer the attachment. HEAD now is 1724ef2 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-169-generic 4.4.0-169.198 ProcVersionSignature: User Name 4.4.0-169.198-generic 4.4.197 Uname: Linux 4.4.0-169-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.21 Architecture: amd64 Date: Thu Nov 28 04:21:52 2019 SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1854298/+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 1873961] Autopkgtest regression report (iproute2/4.15.0-2ubuntu1.2)
All autopkgtests for the newly accepted iproute2 (4.15.0-2ubuntu1.2) for bionic have finished running. The following regressions have been reported in tests triggered by the package: libreswan/unknown (armhf) ubuntu-fan/0.12.10 (amd64) systemd/237-3ubuntu10.41 (amd64, ppc64el) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#iproute2 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to iproute2 in Ubuntu. Matching subscriptions: iproute2 https://bugs.launchpad.net/bugs/1873961 Title: tc filter show tcp_flags wrong mask value Status in The Ubuntu-power-systems project: Fix Committed Status in iproute2 package in Ubuntu: Fix Released Status in iproute2 source package in Bionic: Fix Committed Bug description: [SRU Justification] Impact: The tc command does not show the correct values for tcp_flags (and ip_tos) on filter rules. This might break other scripts parsing that output but at least confuses users. Fix: Backport of "tc: fix bugs for tcp_flags and ip_attr hex output" from upstream iproute2. Testcase: tc qdisc add dev lo ingress tc filter add dev lo parent : prio 3 proto ip flower ip_tos 0x8/32 tc filter add dev lo parent : prio 5 proto ip flower ip_proto tcp \ tcp_flags 0x909/f00 tc filter show dev lo parent : filter protocol ip pref 3 flower chain 0 filter protocol ip pref 3 flower chain 0 handle 0x1 eth_type ipv4 ip_tos a9606c10 <-- bad, should be 0x8/32 not_in_hw filter protocol ip pref 5 flower chain 0 filter protocol ip pref 5 flower chain 0 handle 0x1 eth_type ipv4 ip_proto tcp tcp_flags 909909 <-- bad, should be 0x909/f00 not_in_hw Note that the ip_tos value in the -j[son] output is correct, while the tcp_flags value is is incorrect in both cases. Risk of Regression: Low: Usually scripts would use the json output and that has at least the ip output correct. And the values shown in the bad case seem to be little useful. So it seems unlikely anybody relied on them. But cannot completely be ruled out. === Original description === ---Problem Description--- Problem Descriptions "tc" utility does not show correct TC rule's tcp_flags mask correctly in current "iproute2" package shipped on Genesis. # dpkg -l |grep iproute2 ii iproute2 4.15.0-2ubuntu1 ppc64el networking and traffic control tools ---Steps to Reproduce--- Steps to reproduce the problem: 1) Add a tc rule to the testing VF (i.e. p0v2_r): # tc filter add dev p0v2 protocol ip parent : pref 5 chain 1 handle 0x1 flower src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff ip_proto tcp tcp_flags 2 skip_sw action mirred egress redirect dev p0v0_r 2) Validate the added TC rule: # tc filter show dev p0v2_r root filter protocol ip pref 5 flower chain 1 filter protocol ip pref 5 flower chain 1 handle 0x1 src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff eth_type ipv4 ip_proto tcp tcp_flags 22 /* <--- Wrong */ skip_sw in_hw action order 1: mirred (Egress Redirect to device p0v0_r) stolen 3) If we add the tcp_flags using explicit mask 0x7: # tc filter add dev p0v2 protocol ip parent : pref 5 chain 1 handle 0x1 flower src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff ip_proto tcp tcp_flags 0x2/7 skip_sw action mirred egress redirect dev p0v0_r After that, using "tc filter show dev p0v2_r root" to verify, we still see the same output (tcp_flags 22) as shown in 2) above, which is wrong. Userspace tool common name: tc The userspace tool has the following bit modes: 64-bit Userspace package: iproute2 == Fixes: There are 2 patches to fix the issue: patch 1: commit b85076cd74e77538918d35992b1a9cd17ff86af8 Author: Stephen Hemminger Date: Tue Sep 11 08:29:33 2018 -0700 lib: introduce print_nl Common pattern in iproute commands is to print a line seperator in non-json mode. Make that a simple function. /* This patch declares global variable "const char *_SL_ = "\n";" in lib/utils.c to be used by 2nd patch */ patch 2: commit e8bd395508cead5a81c2bebd9d3705a9e41ea8bc Author: Keara Leibovitz Date: Thu Jul 26 09:45:30 2018 -0400 tc: fix bugs for tcp_flags and ip_attr hex output Fix hex output for both the ip_attr and tcp_flags print functions. With the above 2 patches pull in, the new "tc" utility will show the correct tcp_flags mask: # tc filter show dev p0v2 root filter protocol ip pref 5 flower chain 1 filter protocol ip pref 5 flower chain 1 handle 0x1 src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff eth_type ipv4 ip_proto tcp
[Kernel-packages] [Bug 1889217] Re: Make digital mic on the AMD renoir machines work under gnome desktop
** Tags added: renoir ** Tags added: focal groovy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1889217 Title: Make digital mic on the AMD renoir machines work under gnome desktop Status in alsa-lib package in Ubuntu: New Status in alsa-ucm-conf package in Ubuntu: New Status in pulseaudio package in Ubuntu: New Status in alsa-lib source package in Focal: New Status in alsa-ucm-conf source package in Focal: New Status in pulseaudio source package in Focal: New Status in alsa-lib source package in Groovy: New Status in alsa-ucm-conf source package in Groovy: New Status in pulseaudio source package in Groovy: New Bug description: This is for tracking purpose. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1889217/+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 1888088] Re: [amdgpu] [AMD Renoir] Display won't rotate, nor do fractional scaling, but amdgpu.exp_hw_support=1 fixes it
** Tags added: renoir -- 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/1888088 Title: [amdgpu] [AMD Renoir] Display won't rotate, nor do fractional scaling, but amdgpu.exp_hw_support=1 fixes it Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-video-amdgpu package in Ubuntu: New Bug description: Opening Settings -> Display and selecting an orientation other than Landscape doesn't work. Similarly, selecting Fractional Scaling and then picking a scale factor has no effect. This is a recently installed Ubuntu 20.04, fully updated, on a recently released laptop/tablet that uses an AMD Ryzen 4500U integrated CPU/GPU. It is possible that the GPU is not being detected by Ubuntu and that is the root cause of the problem. I couldn't find an easy explanation online about how to tell whether a GPU was detected or is in use. I did try running "tlp-stat -g" to get graphics status, but it returns without printing anything except its version number (1.3.1). When I choose an orientation, such as Portrait Right, the setting changes and an "Apply" button appears in the top of the Settings window. When I press it, up pops up a dialog asking whether I want to "Keep these display settings?" with two options, keep or revert. The rest of the screen goes grey behind the dialog box, but I can already see behind the popup that the screen did not change its orientation, and the "Orientation" setting back in the Settings->Display window has been reverted to "Landscape" without me doing it. Whether I choose keep or revert, or merely let it time out after 20 seconds, the result remains the same -- the display stays in Landscape mode and the setting that I had made is reverted. Regarding scaling, I can set the display scale to 100% (default) or 200%, successfully. But when I turn on the "Fractional Scaling" slider, the graphics around the edge of the screen immediately increase in size (the icons in the left-hand dock, the text in the top bar), even though I have not changed the scale setting. I have included two screenshots (original screen, and with Fractional Scaling on). There is also some strangeness about whether sliding the Fractional Scaling slider updates the Scale menu to allow more scales - sometimes it does, sometimes it doesn't. When I attempt to set a fractional scale such as 125%, the "Apply" button appears in the upper right corner. When I press that, the display does not actually scale, and a pop-up asks if I want to keep or revert the setting. But looking back at the Displays settings, the Scale has already reverted to 100% (as above with the Orientation). Screenshot enclosed. The display has been rock-solid before this, but now it started showing artifacts, such as previous copies of the Displays window. I've enclosed a screen shot, which shows checkerboard in the screen locations that (in reality) were displaying prior versions of the window. Hmm, examining that screenshot, it looks like the display DID start occupying 25% more space horizontally and vertically, but something about the video scanning versus the screen updating got out of whack. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 BootLog: CasperMD5CheckResult: skip CompositorRunning: None Date: Sat Jul 18 14:00:38 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c3) (prog-if 00 [VGA controller]) Subsystem: Lenovo Renoir [17aa:3f1a] InstallationDate: Installed on 2020-07-16 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81X2 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic root=/dev/mapper/vgubuntu-root ro quiet splash acpi_enforce_resources=lax vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/08/2020 dmi.bios.vendor: LENOVO dmi.bios.version: EECN20WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad Flex 5 14ARE05 dmi.modalias: dmi:bvnLENOVO:bvrEECN20WW:bd04/08/2020:svnLENOVO:pn81X2:pvrIdeaPadFlex514ARE05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct31:cvrIdeaPadFlex514ARE05:
[Kernel-packages] [Bug 1888571] Re: [Ice Lake] Screen flickering and glitching after install
It's *probably* a kernel bug and probably already fixed in a newer kernel. So you might want to try one of those: https://kernel.ubuntu.com/~kernel-ppa/mainline/?C=M;O=D -- 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/1888571 Title: [Ice Lake] Screen flickering and glitching after install Status in linux package in Ubuntu: Confirmed Bug description: Intel integrated driver causes screen flickering with Ubuntu install. Windows did not have this issue ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jul 22 15:41:42 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Iris Plus Graphics G7 [8086:8a52] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Iris Plus Graphics G7 [103c:875a] InstallationDate: Installed on 2020-07-22 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: HP HP ENVY Laptop 13-ba0xxx 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.4.0-42-generic root=UUID=9f807172-2b35-4ad1-9f33-5a912ad7c579 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/04/2020 dmi.bios.vendor: Insyde dmi.bios.version: F.10 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 875A dmi.board.vendor: HP dmi.board.version: 07.34 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.10:bd06/04/2020:svnHP:pnHPENVYLaptop13-ba0xxx:pvrType1ProductConfigId:rvnHP:rn875A:rvr07.34:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Envy dmi.product.name: HP ENVY Laptop 13-ba0xxx dmi.product.sku: 8KD13AV dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP 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 N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888571/+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 1884255] Re: [AMD/ATI] SBx00 Azalia (Intel HDA) Audio Ubuntu 20.04 not working
** Bug watch added: gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues #956 https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/956 ** Also affects: pulseaudio via https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/956 Importance: Unknown Status: Unknown -- 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/1884255 Title: [AMD/ATI] SBx00 Azalia (Intel HDA) Audio Ubuntu 20.04 not working Status in PulseAudio: Unknown Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: New Bug description: When you start playing some audio, the sound disappears. 00:14.2 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 Azalia (Intel HDA) Subsystem: ASUSTeK Computer Inc. M5A78L LE Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel uname -a Linux Marcelo-STI-FX6300 5.4.0-37-generic #41-Ubuntu SMP Wed Jun 3 18:57:02 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux alsa-info !! !!ALSA Information Script v 0.4.65 !! !!Script ran on: Fri Jun 19 13:38:12 UTC 2020 !!Linux Distribution !!-- Ubuntu 20.04 LTS \n \l DISTRIB_ID=Ubuntu DISTRIB_DESCRIPTION="Ubuntu 20.04 LTS" NAME="Ubuntu" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.04 LTS" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies /privacy-policy" UBUNTU_CODENAME=focal !!DMI Information !!--- Manufacturer: System manufacturer Product Name: System Product Name Product Version: System Version Firmware Version: 1201 Board Vendor: ASUSTeK Computer INC. Board Name:M5A78L-M LX/BR !!ACPI Device Status Information !!--- /sys/bus/acpi/devices/ATK0110:00/status15 /sys/bus/acpi/devices/PNP0103:00/status15 /sys/bus/acpi/devices/PNP0400:00/status15 /sys/bus/acpi/devices/PNP0501:00/status15 /sys/bus/acpi/devices/PNP0C0C:00/status11 /sys/bus/acpi/devices/PNP0C0F:00/status9 /sys/bus/acpi/devices/PNP0C0F:01/status9 /sys/bus/acpi/devices/PNP0C0F:02/status9 /sys/bus/acpi/devices/PNP0C0F:03/status9 /sys/bus/acpi/devices/PNP0C0F:04/status9 /sys/bus/acpi/devices/PNP0C0F:05/status9 /sys/bus/acpi/devices/PNP0C0F:06/status9 /sys/bus/acpi/devices/PNP0C0F:07/status9 /sys/bus/acpi/devices/device:20/status 15 /sys/bus/acpi/devices/device:21/status 15 !!Kernel Information !!-- Kernel release:5.4.0-37-generic Operating System: GNU/Linux Architecture: x86_64 Processor: x86_64 SMP Enabled: Yes !!ALSA Version !! Driver version: k5.4.0-37-generic Library version:1.2.3 Utilities version: 1.2.2 !!Loaded ALSA modules !!--- snd_hda_intel !!Sound Servers on this system !! Pulseaudio: Installed - Yes (/usr/bin/pulseaudio) Running - Yes !!Soundcards recognised by ALSA !!- 0 [SB ]: HDA-Intel - HDA ATI SB HDA ATI SB at 0xfe9f4000 irq 16 !!PCI Soundcards installed in the system !!-- 00:14.2 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 Azalia (Intel HDA) [1002:4383] Subsystem: ASUSTeK Computer Inc. M5A78L LE [1043:8445] !!Modprobe options (Sound related) !! snd_pcsp: index=-2 snd_usb_audio: index=-2 snd_atiixp_modem: index=-2 snd_intel8x0m: index=-2 snd_via82xx_modem: index=-2 snd_atiixp_modem: index=-2 snd_intel8x0m: index=-2 snd_via82xx_modem: index=-2 snd_usb_audio: index=-2 snd_usb_caiaq: index=-2 snd_usb_ua101: index=-2 snd_usb_us122l: index=-2 snd_usb_usx2y: index=-2 snd_cmipci: mpu_port=0x330 fm_port=0x388 snd_pcsp: index=-2 snd_usb_audio: index=-2 snd_hda_intel: model=auto snd_hda_intel: dmic detect=0 !!Loaded sound module options !!--- !!Module: snd_hda_intel align_buffer_size : -1 bdl_pos_adj : -1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1 beep_mode : N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N dmic_detect : Y enable : Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y enable_msi : -1 id :
[Kernel-packages] [Bug 1888385] Re: FRITZ!WLAN USB Stick v2 (Product: FRITZ!WLAN N2.4) does not work with Linux version 4.4.0-186-generic (Last working version 4.4.0-185-generic and 4.4.0-184-generic)
I experience the identical problem, but with TP-LINK TL-WN722N (Atheros) WiFi USB stick. -- 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/1888385 Title: FRITZ!WLAN USB Stick v2 (Product: FRITZ!WLAN N2.4) does not work with Linux version 4.4.0-186-generic (Last working version 4.4.0-185-generic and 4.4.0-184-generic) Status in linux package in Ubuntu: Confirmed Bug description: Dear all, the USB WLAN Stick (FRITZ!WLAN USB Stick v2) worked flawlessly up to the Linux Kernel version 4.4.0-185-generic, so I assume some problem has been introduced moving from Linux version 4.4.0-185-generic to the Linux version 4.4.0-186-generic. Operating system and release can be found below. Description:Ubuntu 16.04.6 LTS Release:16.04 Attached are the files for the currently working version (4.4.0-185-generic): dmesg, version signature, lspci and uname output). I provide too the dmesg output of the failing kernel version (4.4.0-185-generic). I am happy to provide more details. Apparently the module is not loaded anymore. Kind regards, Stephan To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888385/+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 1877757] Re: No sound, Dummy output on Acer Swift 3 SF314-57G with Ice Lake core-i7 CPU
** Also affects: linux-oem-5.6 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-oem-5.6 (Ubuntu Focal) Importance: Undecided Status: New -- 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/1877757 Title: No sound, Dummy output on Acer Swift 3 SF314-57G with Ice Lake core-i7 CPU Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.6 package in Ubuntu: New Status in linux source package in Focal: New Status in linux-oem-5.6 source package in Focal: New Bug description: New focal installation on a new Acer Swift 3 laptop with core i7-1065G7. No sound detected, KDE/pavucontrol shows Dummy output. External headset also not detected. I've googled around and tried to reinstall alsa and pulseaudio, tried alsa force-reload as well. Nothing helps. With snd_hda_intel.dmic_detect=0 speakers start working but microphone is not detected. External headset detected with both headphones and mic. I use this as a workaround for a time being. I've checked https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860697 bug. It is closed and use recent kernel and firmware but it does not fix my issue. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-29-generic 5.4.0-29.33 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Sat May 9 18:56:15 2020 InstallationDate: Installed on 2020-04-24 (15 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Acer Swift SF314-57G ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-29-generic root=UUID=faf6a132-de60-44fa-a1a7-4cce8ef83b87 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-29-generic N/A linux-backports-modules-5.4.0-29-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/24/2019 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.09 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Floris_IL dmi.board.vendor: IL dmi.board.version: V1.09 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.09:bd09/24/2019:svnAcer:pnSwiftSF314-57G:pvrV1.09:rvnIL:rnFloris_IL:rvrV1.09:cvnAcer:ct10:cvrChassisVersion: dmi.product.family: Swift 3 dmi.product.name: Swift SF314-57G dmi.product.sku: dmi.product.version: V1.09 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1877757/+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 1863116] Re: debian/rules editconfigs does not work on s390x to change s390x only configs
Only "linux-5.4" task was changed to invalid before it was removed. The "linux" task was and still is confirmed. Launchpad bug tracker supports tracking multiple states across multiple packages simultaniously. You can always see the correct status of the bug, for each task, at the top of the page. It is currently 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/1863116 Title: debian/rules editconfigs does not work on s390x to change s390x only configs Status in Ubuntu on IBM z Systems: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: On s390x pull-lp-source linux-5.4 cd linux-* fakeroot ./debian/rules clean ./debian/rules editconfig dh_testdir; /bin/bash -e debian/scripts/misc/kernelconfig editconfigs Do you want to edit config: amd64/config.flavour.generic? [Y/n] n ... scripts/Kconfig.include:35: compiler 'x86_64-linux-gnu-gcc' not found make[3]: *** [../scripts/kconfig/Makefile:73: syncconfig] Error 1 make[2]: *** [/home/ubuntu/linux-5.4-5.4.0/Makefile:594: syncconfig] Error 2 make[2]: Leaving directory '/home/ubuntu/linux-5.4-5.4.0/build' make[1]: *** [Makefile:179: sub-make] Error 2 make[1]: Leaving directory '/home/ubuntu/linux-5.4-5.4.0' make: *** [debian/rules.d/1-maintainer.mk:44: editconfigs] Error 2 And indeed i do not have x86_64-linux-gnu-gcc crosscompiler available to build on s390x for amd64, and also I don't want to touch amd64 configs. Only s390x ones. As a user, I should be able to rebuild ports architecture kernel with tweaked config for testing, self-hosted without cross-compilers. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1863116/+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 1877757] Re: No sound, Dummy output on Acer Swift 3 SF314-57G with Ice Lake core-i7 CPU
I thought the fix will be merged to ubuntu kernel automatically with the stable patches. Since this doesn't happen, I will backport it to ubuntu kernel. -- 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/1877757 Title: No sound, Dummy output on Acer Swift 3 SF314-57G with Ice Lake core-i7 CPU Status in linux package in Ubuntu: Confirmed Bug description: New focal installation on a new Acer Swift 3 laptop with core i7-1065G7. No sound detected, KDE/pavucontrol shows Dummy output. External headset also not detected. I've googled around and tried to reinstall alsa and pulseaudio, tried alsa force-reload as well. Nothing helps. With snd_hda_intel.dmic_detect=0 speakers start working but microphone is not detected. External headset detected with both headphones and mic. I use this as a workaround for a time being. I've checked https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860697 bug. It is closed and use recent kernel and firmware but it does not fix my issue. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-29-generic 5.4.0-29.33 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Sat May 9 18:56:15 2020 InstallationDate: Installed on 2020-04-24 (15 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Acer Swift SF314-57G ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-29-generic root=UUID=faf6a132-de60-44fa-a1a7-4cce8ef83b87 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-29-generic N/A linux-backports-modules-5.4.0-29-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/24/2019 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.09 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Floris_IL dmi.board.vendor: IL dmi.board.version: V1.09 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.09:bd09/24/2019:svnAcer:pnSwiftSF314-57G:pvrV1.09:rvnIL:rnFloris_IL:rvrV1.09:cvnAcer:ct10:cvrChassisVersion: dmi.product.family: Swift 3 dmi.product.name: Swift SF314-57G dmi.product.sku: dmi.product.version: V1.09 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1877757/+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 1852119] Re: Please add zfs modules to linux-raspi2
Raspberry Pi4 is already available with 8GB of memory. Now that we are way over the minimal memory requirements of ZFS, I think this topic should be reconsidered. Using zfs-dkms is a bit tedious, having the ZFS kernel modules available with the arm64 standard kernel would make the life much easier. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1852119 Title: Please add zfs modules to linux-raspi2 Status in linux-raspi2 package in Ubuntu: Won't Fix Bug description: The 4gb RPI4 is more than capable of handling zfs. ( Even zfs root can be enabled manually with arm64 eoan builds using a variant of the steps at https://github.com/zfsonlinux/zfs/wiki/Ubuntu-18.04-Root-on-ZFS . ) Currently one has to install zfs-dkms for zfs support, but ideally one would have zfs modules come with the standard arm64 kernel so that one does not have to recompile zfs on the pi. Example: uname -a Linux rpi4 5.3.0-1011-raspi2 #12-Ubuntu SMP Fri Nov 1 09:07:06 UTC 2019 aarch64 aarch64 aarch64 GNU/Linux @rpi4:~$ zpool status pool: bpool state: ONLINE status: Some supported features are not enabled on the pool. The pool can still be used, but some features are unavailable. action: Enable all features using 'zpool upgrade'. Once this is done, the pool may no longer be accessible by software that does not support the features. See zpool-features(5) for details. scan: scrub repaired 0B in 0 days 00:00:00 with 0 errors on Mon Nov 11 13:50:14 2019 config: NAME STATE READ WRITE CKSUM bpool ONLINE 0 0 0 usb-Samsung_Flash_Drive_FIT_0309318110004882-0:0-part3 ONLINE 0 0 0 errors: No known data errors pool: rpool state: ONLINE scan: scrub repaired 0B in 0 days 00:01:21 with 0 errors on Mon Nov 11 13:51:39 2019 config: NAMESTATE READ WRITE CKSUM rpool ONLINE 0 0 0 sda4 ONLINE 0 0 0 errors: No known data errors dkms status zfs, 0.8.1, 5.3.0-1011-raspi2, aarch64: installed @rpi4:~$ cat /proc/cpuinfo processor : 0 BogoMIPS: 108.00 Features: fp asimd evtstrm crc32 cpuid CPU implementer : 0x41 CPU architecture: 8 CPU variant : 0x0 CPU part: 0xd08 CPU revision: 3 processor : 1 BogoMIPS: 108.00 Features: fp asimd evtstrm crc32 cpuid CPU implementer : 0x41 CPU architecture: 8 CPU variant : 0x0 CPU part: 0xd08 CPU revision: 3 processor : 2 BogoMIPS: 108.00 Features: fp asimd evtstrm crc32 cpuid CPU implementer : 0x41 CPU architecture: 8 CPU variant : 0x0 CPU part: 0xd08 CPU revision: 3 processor : 3 BogoMIPS: 108.00 Features: fp asimd evtstrm crc32 cpuid CPU implementer : 0x41 CPU architecture: 8 CPU variant : 0x0 CPU part: 0xd08 CPU revision: 3 Hardware: BCM2835 Revision: c03111 Serial : --- Model : Raspberry Pi 4 Model B Rev 1.1 @rpi4:~$ free -m totalusedfree shared buff/cache available Mem: 3791 8832612 18 295 2836 Swap: 4095 04095 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1852119/+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 1888570] Re: poweroff not working after apt upgrade
Thanks. Next one is https://people.canonical.com/~alexhung/LP1888570/0affe1fa22b2/ -- 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/1888570 Title: poweroff not working after apt upgrade Status in linux package in Ubuntu: Confirmed Bug description: System-Information: Description: Ubuntu 18.04.4 LTS Release: 18.04 ## Working packages: - Kernel 5.3.0.61.114 - linux-firmware 1.173.18 Problem occurs when upgrading (anyone of) these packages - Kernel 5.3.0-62.56 - linux-firmware 1.173.19 I use an Acer Aspire E5-771G Notebook with a fresh installation of Ubuntu 18.04. Till the last upgrade everything works as expected. The last upgrade brings two new kernel versions (as mentioned above). Now the system stucks at the very end of the power down sequence. Even SysReq-O will not work (only SysReq-B will work). Because I use Systemback, I time shift to the previous system and then install package by package to see what will bring in the problem. If I install any of the mentioned kernel updates the problem will show up. I had ask the above question on "askubuntu.com". I was directed to upgrade the BIOS, But even after doing so the problem still persist. I am not sure if I do it right (APT pinning). I currently create a file /etc/apt/prefereces.d/kernel. I add an entry for every of the following packages to block the version mentioned above (Pin: version: Pin-Priority: -1): linux-generic-hwe-18.04 linux-headers-generic-hwe-18.04 linux-image-generic-hwe-18.04 linux-modules-nvidia-440-generic-hwe-18.04 linux-firmware After doing so "apt list --upgradeable" will not list the packages in question and the PC will power down normally (and SysReq-O WILL work). In the meanwhile there are newer versions of the kernel online, so the above mentioned pinning will allow the newer kernels to get installed and the problem will show up again. So I block these versions too. BTW: Due to the stuck I am able to see some other error messages that are not reported in the journal. The very last 3-5 lines show: shutdown [1]: Failed to wait for process: Protocol error These lines are present although in the working kernels, but hard to see, because the system powers down some ms after these lines are displayed! This problem seams to be solved more than one year ago in the upstream kernel! --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gneiss 1929 F pulseaudio /dev/snd/controlC0: gneiss 1929 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-05-02 (448 days ago) InstallationMedia: MachineType: Acer Aspire E5-771G NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: LANG=de_DE.UTF-8 SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, no user) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-61-generic root=UUID=0b245afe-758b-4e45-a473-ad2077260d8f ro noplymouth resume=UUID=79a9e809-6ba1-491b-acfc-1816057c2dee ProcVersionSignature: Ubuntu 5.3.0-61.55~18.04.1-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-61-generic N/A linux-backports-modules-5.3.0-61-generic N/A linux-firmware1.173.18 Tags: bionic Uname: Linux 5.3.0-61-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip input lpadmin plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 09/02/2015 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.23 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: EA70_HB dmi.board.vendor: Acer dmi.board.version: Type2 - A01 Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.23:bd09/02/2015:svnAcer:pnAspireE5-771G:pvrV3.72:rvnAcer:rnEA70_HB:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: BDW dmi.product.name: Aspire E5-771G dmi.product.sku: Aspire E5-771G_0884_1_23 dmi.product.version: V3.72 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888570/+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 1889306] Re: Resuming from deep suspend on Thinkpad T14 crashes system (readonly filesystem)
The automatically generated information above was after a fresh boot. The photos are after a resume when the system showed the problematic behavior. -- 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/1889306 Title: Resuming from deep suspend on Thinkpad T14 crashes system (readonly filesystem) Status in linux package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Make sure that "deep" suspend is used instead of `s2idle` suspend (`echo deep | sudo tee /sys/power/mem_sleep`). This is always the case when the "Power->Suspend State" is set to "Linux" instead of "Windows 10" in the BIOS. 2. Trigger suspend, e.g. with GUI or `systemctl suspend -i` 3. System suspends successfully. Power light starts fading in and out, as it should. 4. Wake up the system. This is only possible with the power button instead of keys, which is a difference from `s2idle` suspends. 5. Unlock lock screen 6. Notice that the system will behave buggy/abnormal as the filesystem is remounted as read-only. Shortly after resuming, applications will start to crash or show nonsensical output. Expected behavior: (From step 4) System wakes up and can be used normally. The main filesystem should of course be writable. Ubuntu version: 20.04, latest updates as of 2020-07-28 Kernel: Linux nicolai-t14 5.4.0-42-generic #46-Ubuntu SMP Fri Jul 10 00:24:02 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux Computer: Thinkpad T14 (Intel), M2 NVMe SSD `dmesg | grep ACPI | grep supports`: [0.511722] ACPI: (supports S0 S3 S4 S5) tlp: tlp was running during some tests but deactivated during others. The problem still appeared in both cases. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-42-generic 5.4.0-42.46 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: nicolai1472 F pulseaudio /dev/snd/controlC0: nicolai1472 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Jul 28 21:55:33 2020 HibernationDevice: RESUME=UUID=d4f9a6e6-e186-4b67-92fc-fb3bdf13921c resume_offset=34816 # Resume from /swapfile InstallationDate: Installed on 2020-06-12 (46 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20S1S06C00 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=d4f9a6e6-e186-4b67-92fc-fb3bdf13921c ro resume=UUID=d4f9a6e6-e186-4b67-92fc-fb3bdf13921c resume_offset=34816 quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/27/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2XET15W (1.05 ) dmi.board.asset.tag: Not Available dmi.board.name: 20S1S06C00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2XET15W(1.05):bd04/27/2020:svnLENOVO:pn20S1S06C00:pvrThinkPadT14Gen1:rvnLENOVO:rn20S1S06C00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T14 Gen 1 dmi.product.name: 20S1S06C00 dmi.product.sku: LENOVO_MT_20S1_BU_Think_FM_ThinkPad T14 Gen 1 dmi.product.version: ThinkPad T14 Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1889306/+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 1889306] Re: Resuming from deep suspend on Thinkpad T14 crashes system (readonly filesystem)
** Attachment added: "Trying to create a file shows that filesystem is r-o; mount" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1889306/+attachment/5396713/+files/after-resume-touch-and-mount.jpg -- 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/1889306 Title: Resuming from deep suspend on Thinkpad T14 crashes system (readonly filesystem) Status in linux package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Make sure that "deep" suspend is used instead of `s2idle` suspend (`echo deep | sudo tee /sys/power/mem_sleep`). This is always the case when the "Power->Suspend State" is set to "Linux" instead of "Windows 10" in the BIOS. 2. Trigger suspend, e.g. with GUI or `systemctl suspend -i` 3. System suspends successfully. Power light starts fading in and out, as it should. 4. Wake up the system. This is only possible with the power button instead of keys, which is a difference from `s2idle` suspends. 5. Unlock lock screen 6. Notice that the system will behave buggy/abnormal as the filesystem is remounted as read-only. Shortly after resuming, applications will start to crash or show nonsensical output. Expected behavior: (From step 4) System wakes up and can be used normally. The main filesystem should of course be writable. Ubuntu version: 20.04, latest updates as of 2020-07-28 Kernel: Linux nicolai-t14 5.4.0-42-generic #46-Ubuntu SMP Fri Jul 10 00:24:02 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux Computer: Thinkpad T14 (Intel), M2 NVMe SSD `dmesg | grep ACPI | grep supports`: [0.511722] ACPI: (supports S0 S3 S4 S5) tlp: tlp was running during some tests but deactivated during others. The problem still appeared in both cases. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-42-generic 5.4.0-42.46 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: nicolai1472 F pulseaudio /dev/snd/controlC0: nicolai1472 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Jul 28 21:55:33 2020 HibernationDevice: RESUME=UUID=d4f9a6e6-e186-4b67-92fc-fb3bdf13921c resume_offset=34816 # Resume from /swapfile InstallationDate: Installed on 2020-06-12 (46 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20S1S06C00 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=d4f9a6e6-e186-4b67-92fc-fb3bdf13921c ro resume=UUID=d4f9a6e6-e186-4b67-92fc-fb3bdf13921c resume_offset=34816 quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/27/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2XET15W (1.05 ) dmi.board.asset.tag: Not Available dmi.board.name: 20S1S06C00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2XET15W(1.05):bd04/27/2020:svnLENOVO:pn20S1S06C00:pvrThinkPadT14Gen1:rvnLENOVO:rn20S1S06C00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T14 Gen 1 dmi.product.name: 20S1S06C00 dmi.product.sku: LENOVO_MT_20S1_BU_Think_FM_ThinkPad T14 Gen 1 dmi.product.version: ThinkPad T14 Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1889306/+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 1889306] Re: Resuming from deep suspend on Thinkpad T14 crashes system (readonly filesystem)
** Attachment added: "journalctl -r (part 2)" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1889306/+attachment/5396712/+files/after-resume-journalctl-r2.jpg -- 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/1889306 Title: Resuming from deep suspend on Thinkpad T14 crashes system (readonly filesystem) Status in linux package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Make sure that "deep" suspend is used instead of `s2idle` suspend (`echo deep | sudo tee /sys/power/mem_sleep`). This is always the case when the "Power->Suspend State" is set to "Linux" instead of "Windows 10" in the BIOS. 2. Trigger suspend, e.g. with GUI or `systemctl suspend -i` 3. System suspends successfully. Power light starts fading in and out, as it should. 4. Wake up the system. This is only possible with the power button instead of keys, which is a difference from `s2idle` suspends. 5. Unlock lock screen 6. Notice that the system will behave buggy/abnormal as the filesystem is remounted as read-only. Shortly after resuming, applications will start to crash or show nonsensical output. Expected behavior: (From step 4) System wakes up and can be used normally. The main filesystem should of course be writable. Ubuntu version: 20.04, latest updates as of 2020-07-28 Kernel: Linux nicolai-t14 5.4.0-42-generic #46-Ubuntu SMP Fri Jul 10 00:24:02 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux Computer: Thinkpad T14 (Intel), M2 NVMe SSD `dmesg | grep ACPI | grep supports`: [0.511722] ACPI: (supports S0 S3 S4 S5) tlp: tlp was running during some tests but deactivated during others. The problem still appeared in both cases. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-42-generic 5.4.0-42.46 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: nicolai1472 F pulseaudio /dev/snd/controlC0: nicolai1472 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Jul 28 21:55:33 2020 HibernationDevice: RESUME=UUID=d4f9a6e6-e186-4b67-92fc-fb3bdf13921c resume_offset=34816 # Resume from /swapfile InstallationDate: Installed on 2020-06-12 (46 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20S1S06C00 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=d4f9a6e6-e186-4b67-92fc-fb3bdf13921c ro resume=UUID=d4f9a6e6-e186-4b67-92fc-fb3bdf13921c resume_offset=34816 quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/27/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2XET15W (1.05 ) dmi.board.asset.tag: Not Available dmi.board.name: 20S1S06C00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2XET15W(1.05):bd04/27/2020:svnLENOVO:pn20S1S06C00:pvrThinkPadT14Gen1:rvnLENOVO:rn20S1S06C00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T14 Gen 1 dmi.product.name: 20S1S06C00 dmi.product.sku: LENOVO_MT_20S1_BU_Think_FM_ThinkPad T14 Gen 1 dmi.product.version: ThinkPad T14 Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1889306/+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 1889306] Re: Resuming from deep suspend on Thinkpad T14 crashes system (readonly filesystem)
No available firmware updates: > fwupdmgr update • Thunderbolt Controller has no available firmware updates • Integrated Camera has no available firmware updates • SAMSUNG MZVLB1T0HBLR-000L7 has no available firmware updates • System Firmware has no available firmware updates • ThinkPad USB-C Dock Gen2 USB Audio has no available firmware updates • UEFI Device Firmware has no available firmware updates • UEFI Device Firmware has no available firmware updates • UEFI Device Firmware has no available firmware updates • UEFI Device Firmware has no available firmware updates • UEFI Device Firmware has no available firmware updates • USB2.0 Hub has no available firmware updates • USB2.0 Hub has no available firmware updates • USB3.1 Hub has no available firmware updates • USB3.1 Hub has no available firmware updates • VMM5322 inside ThinkPad USB-C Dock Gen2 has no available firmware updates No updatable devices -- 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/1889306 Title: Resuming from deep suspend on Thinkpad T14 crashes system (readonly filesystem) Status in linux package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Make sure that "deep" suspend is used instead of `s2idle` suspend (`echo deep | sudo tee /sys/power/mem_sleep`). This is always the case when the "Power->Suspend State" is set to "Linux" instead of "Windows 10" in the BIOS. 2. Trigger suspend, e.g. with GUI or `systemctl suspend -i` 3. System suspends successfully. Power light starts fading in and out, as it should. 4. Wake up the system. This is only possible with the power button instead of keys, which is a difference from `s2idle` suspends. 5. Unlock lock screen 6. Notice that the system will behave buggy/abnormal as the filesystem is remounted as read-only. Shortly after resuming, applications will start to crash or show nonsensical output. Expected behavior: (From step 4) System wakes up and can be used normally. The main filesystem should of course be writable. Ubuntu version: 20.04, latest updates as of 2020-07-28 Kernel: Linux nicolai-t14 5.4.0-42-generic #46-Ubuntu SMP Fri Jul 10 00:24:02 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux Computer: Thinkpad T14 (Intel), M2 NVMe SSD `dmesg | grep ACPI | grep supports`: [0.511722] ACPI: (supports S0 S3 S4 S5) tlp: tlp was running during some tests but deactivated during others. The problem still appeared in both cases. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-42-generic 5.4.0-42.46 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: nicolai1472 F pulseaudio /dev/snd/controlC0: nicolai1472 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Jul 28 21:55:33 2020 HibernationDevice: RESUME=UUID=d4f9a6e6-e186-4b67-92fc-fb3bdf13921c resume_offset=34816 # Resume from /swapfile InstallationDate: Installed on 2020-06-12 (46 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20S1S06C00 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=d4f9a6e6-e186-4b67-92fc-fb3bdf13921c ro resume=UUID=d4f9a6e6-e186-4b67-92fc-fb3bdf13921c resume_offset=34816 quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/27/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2XET15W (1.05 ) dmi.board.asset.tag: Not Available dmi.board.name: 20S1S06C00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2XET15W(1.05):bd04/27/2020:svnLENOVO:pn20S1S06C00:pvrThinkPadT14Gen1:rvnLENOVO:rn20S1S06C00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T14 Gen 1 dmi.product.name: 20S1S06C00 dmi.product.sku: LENOVO_MT_20S1_BU_Think_FM_ThinkPad T14 Gen 1 dmi.product.version: ThinkPad T14 Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1889306/+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 1889306] Re: Resuming from deep suspend on Thinkpad T14 crashes system (readonly filesystem)
** Attachment added: "/var/log/syslog (part 1)" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1889306/+attachment/5396714/+files/after-resume-var-log-syslog1.jpg -- 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/1889306 Title: Resuming from deep suspend on Thinkpad T14 crashes system (readonly filesystem) Status in linux package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Make sure that "deep" suspend is used instead of `s2idle` suspend (`echo deep | sudo tee /sys/power/mem_sleep`). This is always the case when the "Power->Suspend State" is set to "Linux" instead of "Windows 10" in the BIOS. 2. Trigger suspend, e.g. with GUI or `systemctl suspend -i` 3. System suspends successfully. Power light starts fading in and out, as it should. 4. Wake up the system. This is only possible with the power button instead of keys, which is a difference from `s2idle` suspends. 5. Unlock lock screen 6. Notice that the system will behave buggy/abnormal as the filesystem is remounted as read-only. Shortly after resuming, applications will start to crash or show nonsensical output. Expected behavior: (From step 4) System wakes up and can be used normally. The main filesystem should of course be writable. Ubuntu version: 20.04, latest updates as of 2020-07-28 Kernel: Linux nicolai-t14 5.4.0-42-generic #46-Ubuntu SMP Fri Jul 10 00:24:02 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux Computer: Thinkpad T14 (Intel), M2 NVMe SSD `dmesg | grep ACPI | grep supports`: [0.511722] ACPI: (supports S0 S3 S4 S5) tlp: tlp was running during some tests but deactivated during others. The problem still appeared in both cases. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-42-generic 5.4.0-42.46 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: nicolai1472 F pulseaudio /dev/snd/controlC0: nicolai1472 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Jul 28 21:55:33 2020 HibernationDevice: RESUME=UUID=d4f9a6e6-e186-4b67-92fc-fb3bdf13921c resume_offset=34816 # Resume from /swapfile InstallationDate: Installed on 2020-06-12 (46 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20S1S06C00 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=d4f9a6e6-e186-4b67-92fc-fb3bdf13921c ro resume=UUID=d4f9a6e6-e186-4b67-92fc-fb3bdf13921c resume_offset=34816 quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/27/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2XET15W (1.05 ) dmi.board.asset.tag: Not Available dmi.board.name: 20S1S06C00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2XET15W(1.05):bd04/27/2020:svnLENOVO:pn20S1S06C00:pvrThinkPadT14Gen1:rvnLENOVO:rn20S1S06C00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T14 Gen 1 dmi.product.name: 20S1S06C00 dmi.product.sku: LENOVO_MT_20S1_BU_Think_FM_ThinkPad T14 Gen 1 dmi.product.version: ThinkPad T14 Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1889306/+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 1889306] Re: Resuming from deep suspend on Thinkpad T14 crashes system (readonly filesystem)
** Attachment added: "/var/log/syslog (part 2)" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1889306/+attachment/5396715/+files/after-resume-var-log-syslog2.jpg -- 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/1889306 Title: Resuming from deep suspend on Thinkpad T14 crashes system (readonly filesystem) Status in linux package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Make sure that "deep" suspend is used instead of `s2idle` suspend (`echo deep | sudo tee /sys/power/mem_sleep`). This is always the case when the "Power->Suspend State" is set to "Linux" instead of "Windows 10" in the BIOS. 2. Trigger suspend, e.g. with GUI or `systemctl suspend -i` 3. System suspends successfully. Power light starts fading in and out, as it should. 4. Wake up the system. This is only possible with the power button instead of keys, which is a difference from `s2idle` suspends. 5. Unlock lock screen 6. Notice that the system will behave buggy/abnormal as the filesystem is remounted as read-only. Shortly after resuming, applications will start to crash or show nonsensical output. Expected behavior: (From step 4) System wakes up and can be used normally. The main filesystem should of course be writable. Ubuntu version: 20.04, latest updates as of 2020-07-28 Kernel: Linux nicolai-t14 5.4.0-42-generic #46-Ubuntu SMP Fri Jul 10 00:24:02 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux Computer: Thinkpad T14 (Intel), M2 NVMe SSD `dmesg | grep ACPI | grep supports`: [0.511722] ACPI: (supports S0 S3 S4 S5) tlp: tlp was running during some tests but deactivated during others. The problem still appeared in both cases. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-42-generic 5.4.0-42.46 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: nicolai1472 F pulseaudio /dev/snd/controlC0: nicolai1472 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Jul 28 21:55:33 2020 HibernationDevice: RESUME=UUID=d4f9a6e6-e186-4b67-92fc-fb3bdf13921c resume_offset=34816 # Resume from /swapfile InstallationDate: Installed on 2020-06-12 (46 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20S1S06C00 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=d4f9a6e6-e186-4b67-92fc-fb3bdf13921c ro resume=UUID=d4f9a6e6-e186-4b67-92fc-fb3bdf13921c resume_offset=34816 quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/27/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2XET15W (1.05 ) dmi.board.asset.tag: Not Available dmi.board.name: 20S1S06C00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2XET15W(1.05):bd04/27/2020:svnLENOVO:pn20S1S06C00:pvrThinkPadT14Gen1:rvnLENOVO:rn20S1S06C00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T14 Gen 1 dmi.product.name: 20S1S06C00 dmi.product.sku: LENOVO_MT_20S1_BU_Think_FM_ThinkPad T14 Gen 1 dmi.product.version: ThinkPad T14 Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1889306/+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 1889306] Re: Resuming from deep suspend on Thinkpad T14 crashes system (readonly filesystem)
** Attachment added: "dmesg" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1889306/+attachment/5396710/+files/after-resume-dmesg.jpg -- 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/1889306 Title: Resuming from deep suspend on Thinkpad T14 crashes system (readonly filesystem) Status in linux package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Make sure that "deep" suspend is used instead of `s2idle` suspend (`echo deep | sudo tee /sys/power/mem_sleep`). This is always the case when the "Power->Suspend State" is set to "Linux" instead of "Windows 10" in the BIOS. 2. Trigger suspend, e.g. with GUI or `systemctl suspend -i` 3. System suspends successfully. Power light starts fading in and out, as it should. 4. Wake up the system. This is only possible with the power button instead of keys, which is a difference from `s2idle` suspends. 5. Unlock lock screen 6. Notice that the system will behave buggy/abnormal as the filesystem is remounted as read-only. Shortly after resuming, applications will start to crash or show nonsensical output. Expected behavior: (From step 4) System wakes up and can be used normally. The main filesystem should of course be writable. Ubuntu version: 20.04, latest updates as of 2020-07-28 Kernel: Linux nicolai-t14 5.4.0-42-generic #46-Ubuntu SMP Fri Jul 10 00:24:02 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux Computer: Thinkpad T14 (Intel), M2 NVMe SSD `dmesg | grep ACPI | grep supports`: [0.511722] ACPI: (supports S0 S3 S4 S5) tlp: tlp was running during some tests but deactivated during others. The problem still appeared in both cases. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-42-generic 5.4.0-42.46 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: nicolai1472 F pulseaudio /dev/snd/controlC0: nicolai1472 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Jul 28 21:55:33 2020 HibernationDevice: RESUME=UUID=d4f9a6e6-e186-4b67-92fc-fb3bdf13921c resume_offset=34816 # Resume from /swapfile InstallationDate: Installed on 2020-06-12 (46 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20S1S06C00 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=d4f9a6e6-e186-4b67-92fc-fb3bdf13921c ro resume=UUID=d4f9a6e6-e186-4b67-92fc-fb3bdf13921c resume_offset=34816 quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/27/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2XET15W (1.05 ) dmi.board.asset.tag: Not Available dmi.board.name: 20S1S06C00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2XET15W(1.05):bd04/27/2020:svnLENOVO:pn20S1S06C00:pvrThinkPadT14Gen1:rvnLENOVO:rn20S1S06C00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T14 Gen 1 dmi.product.name: 20S1S06C00 dmi.product.sku: LENOVO_MT_20S1_BU_Think_FM_ThinkPad T14 Gen 1 dmi.product.version: ThinkPad T14 Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1889306/+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 1889306] Re: Resuming from deep suspend on Thinkpad T14 crashes system (readonly filesystem)
** Attachment added: "journalctl -r (part 1)" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1889306/+attachment/5396711/+files/after-resume-journalctl-r1.jpg -- 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/1889306 Title: Resuming from deep suspend on Thinkpad T14 crashes system (readonly filesystem) Status in linux package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Make sure that "deep" suspend is used instead of `s2idle` suspend (`echo deep | sudo tee /sys/power/mem_sleep`). This is always the case when the "Power->Suspend State" is set to "Linux" instead of "Windows 10" in the BIOS. 2. Trigger suspend, e.g. with GUI or `systemctl suspend -i` 3. System suspends successfully. Power light starts fading in and out, as it should. 4. Wake up the system. This is only possible with the power button instead of keys, which is a difference from `s2idle` suspends. 5. Unlock lock screen 6. Notice that the system will behave buggy/abnormal as the filesystem is remounted as read-only. Shortly after resuming, applications will start to crash or show nonsensical output. Expected behavior: (From step 4) System wakes up and can be used normally. The main filesystem should of course be writable. Ubuntu version: 20.04, latest updates as of 2020-07-28 Kernel: Linux nicolai-t14 5.4.0-42-generic #46-Ubuntu SMP Fri Jul 10 00:24:02 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux Computer: Thinkpad T14 (Intel), M2 NVMe SSD `dmesg | grep ACPI | grep supports`: [0.511722] ACPI: (supports S0 S3 S4 S5) tlp: tlp was running during some tests but deactivated during others. The problem still appeared in both cases. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-42-generic 5.4.0-42.46 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: nicolai1472 F pulseaudio /dev/snd/controlC0: nicolai1472 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Jul 28 21:55:33 2020 HibernationDevice: RESUME=UUID=d4f9a6e6-e186-4b67-92fc-fb3bdf13921c resume_offset=34816 # Resume from /swapfile InstallationDate: Installed on 2020-06-12 (46 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20S1S06C00 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=d4f9a6e6-e186-4b67-92fc-fb3bdf13921c ro resume=UUID=d4f9a6e6-e186-4b67-92fc-fb3bdf13921c resume_offset=34816 quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/27/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2XET15W (1.05 ) dmi.board.asset.tag: Not Available dmi.board.name: 20S1S06C00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2XET15W(1.05):bd04/27/2020:svnLENOVO:pn20S1S06C00:pvrThinkPadT14Gen1:rvnLENOVO:rn20S1S06C00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T14 Gen 1 dmi.product.name: 20S1S06C00 dmi.product.sku: LENOVO_MT_20S1_BU_Think_FM_ThinkPad T14 Gen 1 dmi.product.version: ThinkPad T14 Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1889306/+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 1889306] 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/1889306 Title: Resuming from deep suspend on Thinkpad T14 crashes system (readonly filesystem) Status in linux package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Make sure that "deep" suspend is used instead of `s2idle` suspend (`echo deep | sudo tee /sys/power/mem_sleep`). This is always the case when the "Power->Suspend State" is set to "Linux" instead of "Windows 10" in the BIOS. 2. Trigger suspend, e.g. with GUI or `systemctl suspend -i` 3. System suspends successfully. Power light starts fading in and out, as it should. 4. Wake up the system. This is only possible with the power button instead of keys, which is a difference from `s2idle` suspends. 5. Unlock lock screen 6. Notice that the system will behave buggy/abnormal as the filesystem is remounted as read-only. Shortly after resuming, applications will start to crash or show nonsensical output. Expected behavior: (From step 4) System wakes up and can be used normally. The main filesystem should of course be writable. Ubuntu version: 20.04, latest updates as of 2020-07-28 Kernel: Linux nicolai-t14 5.4.0-42-generic #46-Ubuntu SMP Fri Jul 10 00:24:02 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux Computer: Thinkpad T14 (Intel), M2 NVMe SSD `dmesg | grep ACPI | grep supports`: [0.511722] ACPI: (supports S0 S3 S4 S5) tlp: tlp was running during some tests but deactivated during others. The problem still appeared in both cases. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-42-generic 5.4.0-42.46 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: nicolai1472 F pulseaudio /dev/snd/controlC0: nicolai1472 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Jul 28 21:55:33 2020 HibernationDevice: RESUME=UUID=d4f9a6e6-e186-4b67-92fc-fb3bdf13921c resume_offset=34816 # Resume from /swapfile InstallationDate: Installed on 2020-06-12 (46 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20S1S06C00 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=d4f9a6e6-e186-4b67-92fc-fb3bdf13921c ro resume=UUID=d4f9a6e6-e186-4b67-92fc-fb3bdf13921c resume_offset=34816 quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/27/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2XET15W (1.05 ) dmi.board.asset.tag: Not Available dmi.board.name: 20S1S06C00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2XET15W(1.05):bd04/27/2020:svnLENOVO:pn20S1S06C00:pvrThinkPadT14Gen1:rvnLENOVO:rn20S1S06C00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T14 Gen 1 dmi.product.name: 20S1S06C00 dmi.product.sku: LENOVO_MT_20S1_BU_Think_FM_ThinkPad T14 Gen 1 dmi.product.version: ThinkPad T14 Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1889306/+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 1889306] [NEW] Resuming from deep suspend on Thinkpad T14 crashes system (readonly filesystem)
Public bug reported: Steps to reproduce: 1. Make sure that "deep" suspend is used instead of `s2idle` suspend (`echo deep | sudo tee /sys/power/mem_sleep`). This is always the case when the "Power->Suspend State" is set to "Linux" instead of "Windows 10" in the BIOS. 2. Trigger suspend, e.g. with GUI or `systemctl suspend -i` 3. System suspends successfully. Power light starts fading in and out, as it should. 4. Wake up the system. This is only possible with the power button instead of keys, which is a difference from `s2idle` suspends. 5. Unlock lock screen 6. Notice that the system will behave buggy/abnormal as the filesystem is remounted as read-only. Shortly after resuming, applications will start to crash or show nonsensical output. Expected behavior: (From step 4) System wakes up and can be used normally. The main filesystem should of course be writable. Ubuntu version: 20.04, latest updates as of 2020-07-28 Kernel: Linux nicolai-t14 5.4.0-42-generic #46-Ubuntu SMP Fri Jul 10 00:24:02 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux Computer: Thinkpad T14 (Intel), M2 NVMe SSD `dmesg | grep ACPI | grep supports`: [0.511722] ACPI: (supports S0 S3 S4 S5) tlp: tlp was running during some tests but deactivated during others. The problem still appeared in both cases. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-42-generic 5.4.0-42.46 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: nicolai1472 F pulseaudio /dev/snd/controlC0: nicolai1472 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Jul 28 21:55:33 2020 HibernationDevice: RESUME=UUID=d4f9a6e6-e186-4b67-92fc-fb3bdf13921c resume_offset=34816 # Resume from /swapfile InstallationDate: Installed on 2020-06-12 (46 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20S1S06C00 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=d4f9a6e6-e186-4b67-92fc-fb3bdf13921c ro resume=UUID=d4f9a6e6-e186-4b67-92fc-fb3bdf13921c resume_offset=34816 quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/27/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2XET15W (1.05 ) dmi.board.asset.tag: Not Available dmi.board.name: 20S1S06C00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2XET15W(1.05):bd04/27/2020:svnLENOVO:pn20S1S06C00:pvrThinkPadT14Gen1:rvnLENOVO:rn20S1S06C00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T14 Gen 1 dmi.product.name: 20S1S06C00 dmi.product.sku: LENOVO_MT_20S1_BU_Think_FM_ThinkPad T14 Gen 1 dmi.product.version: ThinkPad T14 Gen 1 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug 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/1889306 Title: Resuming from deep suspend on Thinkpad T14 crashes system (readonly filesystem) Status in linux package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Make sure that "deep" suspend is used instead of `s2idle` suspend (`echo deep | sudo tee /sys/power/mem_sleep`). This is always the case when the "Power->Suspend State" is set to "Linux" instead of "Windows 10" in the BIOS. 2. Trigger suspend, e.g. with GUI or `systemctl suspend -i` 3. System suspends successfully. Power light starts fading in and out, as it should. 4. Wake up the system. This is only possible with the power button instead of keys, which is a difference from `s2idle` suspends. 5. Unlock lock screen 6. Notice that the system will behave buggy/abnormal as the filesystem is remounted as read-only. Shortly after resuming, applications will start to crash or show nonsensical output. Expected behavior: (From step 4) System wakes up and can be used normally. The main filesystem should of course be writable. Ubuntu version: 20.04, latest updates as of 2020-07-28 Kernel: Linux nicolai-t14 5.4.0-42-generic #46-Ubuntu SMP Fri Jul 10 00:24:02 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux Computer: Thinkpad T14 (Intel), M2 NVMe SSD `dmesg | grep ACPI | grep supports`: [0.511722] ACPI: (supports S0 S3 S4 S5) tlp: tlp was running during some tests but deactivated during others. The problem still appeared in both cases. ProblemType: Bug
[Kernel-packages] [Bug 1884997] Re: no touchpad detected, not working at all
Hello, I can confirm this is a kernel bug which manifests on the Lenovo IdeaPad 3 15IIL05. Attached is a tarball from the Fedora "Problem Reporting" tool which includes the dmesg and other system data. I realize this isn't a Fedora bug tracker but this is a kernel bug and there doesn't seem to be any other discussion about it. Below is the relevant log telling us no handlers are registered for the hardware: [9.187109] irq 9: nobody cared (try booting with the "irqpoll" option) [9.187113] CPU: 1 PID: 848 Comm: rngd Not tainted 5.6.6-300.fc32.x86_64 #1 [9.187113] Hardware name: LENOVO 81WE/LNVNB161216, BIOS EMCN13WW 03/06/2020 [9.187114] Call Trace: [9.187116] [9.187123] dump_stack+0x64/0x88 [9.187126] __report_bad_irq+0x35/0xa7 [9.187128] note_interrupt.cold+0xb/0x6a [9.187129] handle_irq_event+0x88/0x8a [9.187130] handle_fasteoi_irq+0x78/0x1c0 [9.187132] do_IRQ+0x50/0xe0 [9.187133] common_interrupt+0xf/0xf [9.187134] ** Attachment added: "oops-2020-07-28-14.tar.gz" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884997/+attachment/5396681/+files/oops-2020-07-28-14.tar.gz -- 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/1884997 Title: no touchpad detected, not working at all Status in linux package in Ubuntu: Incomplete Bug description: hello, i bought a new pc and installed ubuntu 20.04 and windows 10 on it. on ubuntu os my touchpad doesn't work at all, since installation process but it does on windows. the pc is a lenovo pc and one of the latest released one. when i plug in a usb mouse the mouse works fine but the touchpad still don't. it even doesn't show the touchpad when i type in (1) "cat /proc/bus/input/devices". only the usb mouse twice. i tryed a lot and don't know how to help myself any further. i attached a file "devices" where printed my output of (1). thanks for any help. 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 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fabian 1032 F pulseaudio /dev/snd/pcmC0D0p: fabian 1032 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jun 24 18:21:17 2020 InstallationDate: Installed on 2020-06-17 (6 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81WE ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=a65a602e-ae73-4354-94f9-2f99e2bff055 ro i8042.reset quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-37-generic N/A linux-backports-modules-5.4.0-37-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/06/2020 dmi.bios.vendor: LENOVO dmi.bios.version: EMCN13WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 3 15IIL05 dmi.modalias: dmi:bvnLENOVO:bvrEMCN13WW:bd03/06/2020:svnLENOVO:pn81WE:pvrIdeaPad315IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrIdeaPad315IIL05: dmi.product.family: IdeaPad 3 15IIL05 dmi.product.name: 81WE dmi.product.sku: LENOVO_MT_81WE_BU_idea_FM_IdeaPad 3 15IIL05 dmi.product.version: IdeaPad 3 15IIL05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884997/+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 1888715] Re: UDP data corruption caused by buggy udp_recvmsg() -> skb_copy_and_csum_datagram_msg()
https://lore.kernel.org/netdev/20200728015505.37830-1-de...@microsoft.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/1888715
Title:
UDP data corruption caused by buggy udp_recvmsg() ->
skb_copy_and_csum_datagram_msg()
Status in linux package in Ubuntu:
Incomplete
Bug description:
The Xenial v4.4 kernel (https://kernel.ubuntu.com/git/ubuntu/ubuntu-
xenial.git/tag/?h=Ubuntu-4.4.0-184.214) lacks this upstream bug
fix("make skb_copy_datagram_msg() et.al. preserve ->msg_iter on erro"
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=3278682123811dd8ef07de5eb701fc4548fcebf2);
as a result, the v4.4 kernel can deliver corrupt data to the
application when a corrupt packet is closely followed by a valid
packet, and actually the UDP payload of the corrupt packet is
delivered to the application with the "from IP/Port" of the valid
packet, so this is actually a security vulnerability that can be used
to trick the application to think the corrupt packet’s payload is sent
from the valid packet’s IP address/port, i.e. a source IP based
security authentication mechanism can be bypassed.
Details:
For a packet longer than 76 bytes (see line 3951,
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/include/linux/skbuff.h?h=v5.8-rc6#n3948),
Linux delays the UDP checksum verification until the application
invokes the syscall recvmsg().
In the recvmsg() syscall handler, while Linux is copying the UDP
payload to the application’s memory, it calculates the UDP checksum.
If the calculated checksum doesn’t match the received checksum, Linux
drops the corrupt UDP packet, and then starts to process the next
packet (if any), and if the next packet is valid (i.e. the checksum is
correct), Linux will copy the valid UDP packet's payload to the
application’s receiver buffer.
The bug is: before Linux starts to copy the valid UDP packet, the data
structure used to track how many more bytes should be copied to the
application memory is not reset to what it was when the application
just entered the kernel by the syscall! Consequently, only a small
portion or none of the valid packet’s payload is copied to the
application’s receive buffer, and later when the application exits
from the kernel, actually most of the application’s receive buffer
contains the payload of the corrupt packet while recvmsg() returns the
size of the UDP payload of the valid packet. Note: this is actually a
security vulnerability that can be used to trick the application to
think the corrupt packet’s payload is sent from the valid packet’s IP
address/port -- so a source IP based security authentication mechanism
can be bypassed.
The bug was fixed in this 2017 patch “make skb_copy_datagram_msg()
et.al. preserve ->msg_iter on error
(https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=3278682123811dd8ef07de5eb701fc4548fcebf2)”,
but unluckily the patch is only backported to the upstream v4.9+
kernels. I'm reporting this bug to request the bugfix to be backported
to the v4.4 Xenial kernel, which is still used by some users and has
not been EOL'ed (https://ubuntu.com/about/release-cycle).
I have the below one-line workaround patch to force the recvmsg() syscall
handler to return to the userspace when Linux detects a corrupt UDP packet, so
the application will invoke the syscall again to receive the next good UDP
packet:
--- a/net/ipv4/udp.c
+++ b/net/ipv4/udp.c
@@ -1367,6 +1367,7 @@ csum_copy_err:
/* starting over for a new packet, but check if we need to yield */
cond_resched();
msg->msg_flags &= ~MSG_TRUNC;
+ return -EAGAIN;
goto try_again;
}
Note: the patch may not work well with blocking sockets, for which
typically the application doesn’t expect an error of -EAGAIN. I guess
it would be safer to return -EINTR instead.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888715/+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 1873961] Re: tc filter show tcp_flags wrong mask value
** Changed in: ubuntu-power-systems Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to iproute2 in Ubuntu. Matching subscriptions: iproute2 https://bugs.launchpad.net/bugs/1873961 Title: tc filter show tcp_flags wrong mask value Status in The Ubuntu-power-systems project: Fix Committed Status in iproute2 package in Ubuntu: Fix Released Status in iproute2 source package in Bionic: Fix Committed Bug description: [SRU Justification] Impact: The tc command does not show the correct values for tcp_flags (and ip_tos) on filter rules. This might break other scripts parsing that output but at least confuses users. Fix: Backport of "tc: fix bugs for tcp_flags and ip_attr hex output" from upstream iproute2. Testcase: tc qdisc add dev lo ingress tc filter add dev lo parent : prio 3 proto ip flower ip_tos 0x8/32 tc filter add dev lo parent : prio 5 proto ip flower ip_proto tcp \ tcp_flags 0x909/f00 tc filter show dev lo parent : filter protocol ip pref 3 flower chain 0 filter protocol ip pref 3 flower chain 0 handle 0x1 eth_type ipv4 ip_tos a9606c10 <-- bad, should be 0x8/32 not_in_hw filter protocol ip pref 5 flower chain 0 filter protocol ip pref 5 flower chain 0 handle 0x1 eth_type ipv4 ip_proto tcp tcp_flags 909909 <-- bad, should be 0x909/f00 not_in_hw Note that the ip_tos value in the -j[son] output is correct, while the tcp_flags value is is incorrect in both cases. Risk of Regression: Low: Usually scripts would use the json output and that has at least the ip output correct. And the values shown in the bad case seem to be little useful. So it seems unlikely anybody relied on them. But cannot completely be ruled out. === Original description === ---Problem Description--- Problem Descriptions "tc" utility does not show correct TC rule's tcp_flags mask correctly in current "iproute2" package shipped on Genesis. # dpkg -l |grep iproute2 ii iproute2 4.15.0-2ubuntu1 ppc64el networking and traffic control tools ---Steps to Reproduce--- Steps to reproduce the problem: 1) Add a tc rule to the testing VF (i.e. p0v2_r): # tc filter add dev p0v2 protocol ip parent : pref 5 chain 1 handle 0x1 flower src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff ip_proto tcp tcp_flags 2 skip_sw action mirred egress redirect dev p0v0_r 2) Validate the added TC rule: # tc filter show dev p0v2_r root filter protocol ip pref 5 flower chain 1 filter protocol ip pref 5 flower chain 1 handle 0x1 src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff eth_type ipv4 ip_proto tcp tcp_flags 22 /* <--- Wrong */ skip_sw in_hw action order 1: mirred (Egress Redirect to device p0v0_r) stolen 3) If we add the tcp_flags using explicit mask 0x7: # tc filter add dev p0v2 protocol ip parent : pref 5 chain 1 handle 0x1 flower src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff ip_proto tcp tcp_flags 0x2/7 skip_sw action mirred egress redirect dev p0v0_r After that, using "tc filter show dev p0v2_r root" to verify, we still see the same output (tcp_flags 22) as shown in 2) above, which is wrong. Userspace tool common name: tc The userspace tool has the following bit modes: 64-bit Userspace package: iproute2 == Fixes: There are 2 patches to fix the issue: patch 1: commit b85076cd74e77538918d35992b1a9cd17ff86af8 Author: Stephen Hemminger Date: Tue Sep 11 08:29:33 2018 -0700 lib: introduce print_nl Common pattern in iproute commands is to print a line seperator in non-json mode. Make that a simple function. /* This patch declares global variable "const char *_SL_ = "\n";" in lib/utils.c to be used by 2nd patch */ patch 2: commit e8bd395508cead5a81c2bebd9d3705a9e41ea8bc Author: Keara Leibovitz Date: Thu Jul 26 09:45:30 2018 -0400 tc: fix bugs for tcp_flags and ip_attr hex output Fix hex output for both the ip_attr and tcp_flags print functions. With the above 2 patches pull in, the new "tc" utility will show the correct tcp_flags mask: # tc filter show dev p0v2 root filter protocol ip pref 5 flower chain 1 filter protocol ip pref 5 flower chain 1 handle 0x1 src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff eth_type ipv4 ip_proto tcp tcp_flags 0x2/7 /* <--- Correct */ skip_sw in_hw action order 1: mirred (Egress Redirect to device p0v0_r) stolen This bug affects tc in Ubuntu 18.04.1 stock image. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1873961/+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 1888507] Re: [UBUNTU 18.04] BPF programs fail on Ubuntu s390x
Yep, and the commit that first fixes up these probe_read vs
probe_read_kernel/probe_read_user problems is:
6ae08ae3dea2cfa03dd3665a3c8475c2d429ef47 "bpf: Add probe_read_{user,
kernel} and probe_read_{user, kernel}_str helpers"
So, these helpers are not available until 5.5. We may consider this a
bug, but BPF code will still need to be changed to use the new helpers,
otherwise they will keep failing on s390x.
Cascardo.
--
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/1888507
Title:
[UBUNTU 18.04] BPF programs fail on Ubuntu s390x
Status in Ubuntu on IBM z Systems:
In Progress
Status in linux package in Ubuntu:
New
Status in linux source package in Bionic:
In Progress
Bug description:
We need to run BPF filters to analyse and monitor network traffic. The
BPF filters are created by skydive (http://skydive.network). Currently
skydive fails to install BPF filters on s390x (using Ubuntu 18.04
currently, soon moving to Ubuntu 20.04).
Because of these failures, we decided to try the BPF samples that come
with the kernel first. These samples also fail on s390x while they
work fine on Intel.
shense@boe-build:~/bionic/samples/bpf$ uname -a
Linux boe-build 4.15.0-112-generic #113-Ubuntu SMP Thu Jul 9 23:40:36 UTC
2020 s390x s390x s390x GNU/Linux
Example instructions:
sudo apt install -y dpkg-dev clang llvm libelf-dev
sudo apt-get source linux-image-unsigned-$(uname -r)
cd linux-4.15.0/
make headers_install
make samples/bpf/
Errors:
shense@boe-build:~/bionic/samples/bpf$ sudo ./test_map_in_map
[sudo] password for shense:
invalid relo for insn[4].code 0x85
bpf_load_program() err=22
0: (bf) r7 = r1
1: (b7) r1 = 0
2: (63) *(u32 *)(r10 -32) = r1
3: (bf) r1 = r7
4: (85) call unknown#-1
BPF_CALL uses reserved fields
0: (bf) r7 = r1
1: (b7) r1 = 0
2: (63) *(u32 *)(r10 -32) = r1
3: (bf) r1 = r7
4: (85) call unknown#-1
BPF_CALL uses reserved fields
shense@boe-build:~/bionic/samples/bpf$ sudo ./map_perf_test
invalid relo for insn[22].code 0x85
bpf_load_program() err=22
0: (bf) r7 = r1
1: (18) r1 = 0x207265743a25646e
3: (7b) *(u64 *)(r10 -16) = r1
4: (18) r1 = 0x705f616c6c6f632e
6: (7b) *(u64 *)(r10 -24) = r1
7: (18) r1 = 0x5f6c72755f686d61
9: (7b) *(u64 *)(r10 -32) = r1
10: (18) r1 = 0x7420737472657373
12: (7b) *(u64 *)(r10 -40) = r1
13: (18) r1 = 0x4661696c65642061
15: (7b) *(u64 *)(r10 -48) = r1
16: (b7) r1 = 0
17: (73) *(u8 *)(r10 -8) = r1
18: (b7) r2 = 1
19: (7b) *(u64 *)(r10 -72) = r2
20: (63) *(u32 *)(r10 -76) = r1
21: (bf) r1 = r7
22: (85) call unknown#-1
BPF_CALL uses reserved fields
0: (bf) r7 = r1
1: (18) r1 = 0x207265743a25646e
3: (7b) *(u64 *)(r10 -16) = r1
4: (18) r1 = 0x705f616c6c6f632e
6: (7b) *(u64 *)(r10 -24) = r1
7: (18) r1 = 0x5f6c72755f686d61
9: (7b) *(u64 *)(r10 -32) = r1
10: (18) r1 = 0x7420737472657373
12: (7b) *(u64 *)(r10 -40) = r1
13: (18) r1 = 0x4661696c65642061
15: (7b) *(u64 *)(r10 -48) = r1
16: (b7) r1 = 0
17: (73) *(u8 *)(r10 -8) = r1
18: (b7) r2 = 1
19: (7b) *(u64 *)(r10 -72) = r2
20: (63) *(u32 *)(r10 -76) = r1
21: (bf) r1 = r7
22: (85) call unknown#-1
BPF_CALL uses reserved fields
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1888507/+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 1791427] Re: Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1 Carbon 6th
'Anyone tried a very recent kernel and can confirm the issue is still there [..]?' I tried 5.6.19, I think it was (so, moderately recently) and I can confirm the problem is there. Also, I've looked at the release notes for various 5.7 kernels and not seen a sign of the patch. -- 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/1791427 Title: Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1 Carbon 6th Status in linux package in Ubuntu: Triaged Bug description: Ubuntu 18.04.1 Terminology in case we use different terms: touchpad - just the rectangular touch-sensitive surface below the keyboard (xinput lists it as Synaptics TM3288-011) trackpoint - the red thingy built into the keyboard + 3 physical buttons below the keyboard (trackpoint and buttons are integrated together; listed in xinput as TPPS/2 Elan TrackPoint) On September 7th, 2018, Lenovo has issued a BIOS update (v1.30), which enables proper S3 deep sleep state - users no longer have to patch DSDT tables to get it. It can be enabled in the BIOS settings. In X1 carbon 6th generation models that have NFC, when laptop wakes from suspend by opening the lid, in most cases both touchpad and trackpoint stop working completely. They are also no longer listed when running xinput command. Sometimes just one of them stops working, usually the trackpoint. In some rare cases it is possible to bring them back by using these commands: echo -n none > /sys/devices/platform/i8042/serio1/drvctl echo -n reconnect > /sys/devices/platform/i8042/serio1/drvctl rmmod psmouse modprobe psmouse These worked properly when waking up from S2Idle sleep state (had these in a script that runs after waking the machine from suspend), but with S3 deep sleep these rarely work and the only way to bring back touchpad and/or trackpoint is turning off the machine and turning it on (restart does not help). I could not find any pattern that would show when the input devices stop working or start working again using the commands mentioned above. It's completely random from my perspective. This is happening on the standard issue 4.15.0-33-generic kernel that shipped with my Ubuntu 18.04 (with updates), as well as with newer mainline kernels, such as the newest point versions of 4.17, 4.18 and 4.19 RC2. This happens regardless of whether "blacklist i2c_i801" is commented out in /etc/modprobe.d/blacklist.conf or not. It happens regardless of whether "psmouse.synaptics_intertouch=1" is passed as grub parameter. Presence of TLP does not make it better, nor worse. It appears that non-NFC models are not affected. I know at least one Arch Linux user who has the exact same model, but without this issue. I'm using synaptics driver (no libinput installed), he uses libinput and doesn't have synaptics, if that information is of any use. Libinput does not seem to help. This forum thread also has more details from users who updated their BIOS to get S3 suspend: https://forums.lenovo.com/t5/Linux- Discussion/X1-Carbon-Gen-6-cannot-enter-deep-sleep-S3-state-aka- Suspend-to/td-p/3998182/page/27 Another related thread: https://bbs.archlinux.org/viewtopic.php?id=236367 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-33-generic 4.15.0-33.36 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: maciej 2651 F...m pulseaudio /dev/snd/controlC0: maciej 2651 F pulseaudio CurrentDesktop: i3 Date: Sat Sep 8 13:45:43 2018 HibernationDevice: RESUME=UUID=3116dcb0-d91e-4b2a-8166-43b7a9a9d36e InstallationDate: Installed on 2018-07-21 (49 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 13d3:56b2 IMC Networks Bus 001 Device 002: ID 04b4:0060 Cypress Semiconductor Corp. Wireless optical mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20KH006KPB ProcFB: 0 EFI VGA 1 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-33-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash psmouse.synaptics_intertouch=1 vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-33-generic N/A linux-backports-modules-4.15.0-33-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/31/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET55W (1.30 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KH006KPB
[Kernel-packages] [Bug 1873961] Re: tc filter show tcp_flags wrong mask value
Hello bugproxy, or anyone else affected, Accepted iproute2 into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/iproute2/4.15.0-2ubuntu1.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: iproute2 (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to iproute2 in Ubuntu. Matching subscriptions: iproute2 https://bugs.launchpad.net/bugs/1873961 Title: tc filter show tcp_flags wrong mask value Status in The Ubuntu-power-systems project: In Progress Status in iproute2 package in Ubuntu: Fix Released Status in iproute2 source package in Bionic: Fix Committed Bug description: [SRU Justification] Impact: The tc command does not show the correct values for tcp_flags (and ip_tos) on filter rules. This might break other scripts parsing that output but at least confuses users. Fix: Backport of "tc: fix bugs for tcp_flags and ip_attr hex output" from upstream iproute2. Testcase: tc qdisc add dev lo ingress tc filter add dev lo parent : prio 3 proto ip flower ip_tos 0x8/32 tc filter add dev lo parent : prio 5 proto ip flower ip_proto tcp \ tcp_flags 0x909/f00 tc filter show dev lo parent : filter protocol ip pref 3 flower chain 0 filter protocol ip pref 3 flower chain 0 handle 0x1 eth_type ipv4 ip_tos a9606c10 <-- bad, should be 0x8/32 not_in_hw filter protocol ip pref 5 flower chain 0 filter protocol ip pref 5 flower chain 0 handle 0x1 eth_type ipv4 ip_proto tcp tcp_flags 909909 <-- bad, should be 0x909/f00 not_in_hw Note that the ip_tos value in the -j[son] output is correct, while the tcp_flags value is is incorrect in both cases. Risk of Regression: Low: Usually scripts would use the json output and that has at least the ip output correct. And the values shown in the bad case seem to be little useful. So it seems unlikely anybody relied on them. But cannot completely be ruled out. === Original description === ---Problem Description--- Problem Descriptions "tc" utility does not show correct TC rule's tcp_flags mask correctly in current "iproute2" package shipped on Genesis. # dpkg -l |grep iproute2 ii iproute2 4.15.0-2ubuntu1 ppc64el networking and traffic control tools ---Steps to Reproduce--- Steps to reproduce the problem: 1) Add a tc rule to the testing VF (i.e. p0v2_r): # tc filter add dev p0v2 protocol ip parent : pref 5 chain 1 handle 0x1 flower src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff ip_proto tcp tcp_flags 2 skip_sw action mirred egress redirect dev p0v0_r 2) Validate the added TC rule: # tc filter show dev p0v2_r root filter protocol ip pref 5 flower chain 1 filter protocol ip pref 5 flower chain 1 handle 0x1 src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff eth_type ipv4 ip_proto tcp tcp_flags 22 /* <--- Wrong */ skip_sw in_hw action order 1: mirred (Egress Redirect to device p0v0_r) stolen 3) If we add the tcp_flags using explicit mask 0x7: # tc filter add dev p0v2 protocol ip parent : pref 5 chain 1 handle 0x1 flower src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff ip_proto tcp tcp_flags 0x2/7 skip_sw action mirred egress redirect dev p0v0_r After that, using "tc filter show dev p0v2_r root" to verify, we still see the same output (tcp_flags 22) as shown in 2) above, which is wrong. Userspace tool common name: tc The userspace tool has the following bit modes: 64-bit Userspace package: iproute2 == Fixes: There are 2 patches to fix the issue: patch 1: commit b85076cd74e77538918d35992b1a9cd17ff86af8 Author: Stephen Hemminger Date: Tue Sep 11 08:29:33 2018 -0700 lib: introduce print_nl Common pattern in iproute
[Kernel-packages] [Bug 1889155] 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 1889155 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: eoan -- 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/1889155 Title: after recent upgrade, hdmi secondary monitor is not detected Status in linux package in Ubuntu: Incomplete Bug description: It is often hard to connect secondary monitors to my laptop because it uses nvidia. In ubuntu it worked without needing configuration, however, yesterday it just stopped detecting it. I will start downgrading the latest updates to see if I can find the culprit. The monitor does detect that something was plugged in. My laptop is "hp omen 15 ax201ns" (Specs: https://support.hp.com/rs-en/document/c05411183) I don't know what package caused the regression, but I attach the history of the last upgrades: Start-Date: 2020-07-22 20:27:48 Commandline: packagekit role='update-packages' Requested-By: joaquin (1000) Upgrade: libavresample-dev:amd64 (7:3.4.6-0ubuntu0.18.04.1, 7:3.4.8-0ubuntu0.2), libavformat57:amd64 (7:3.4.6-0ubuntu0.18.04.1, 7:3.4.8-0ubuntu0.2), libavfilter6:amd64 (7:3.4.6-0ubuntu0.18.04.1, 7:3.4.8-0ubuntu0.2), ffmpeg:amd64 (7:3.4.6-0ubuntu0.18.04.1, 7:3.4.8-0ubuntu0.2), libswresample2:amd64 (7:3.4.6-0ubuntu0.18.04.1, 7:3.4.8-0ubuntu0.2), libavformat-dev:amd64 (7:3.4.6-0ubuntu0.18.04.1, 7:3.4.8-0ubuntu0.2), libswresample-dev:amd64 (7:3.4.6-0ubuntu0.18.04.1, 7:3.4.8-0ubuntu0.2), libpostproc54:amd64 (7:3.4.6-0ubuntu0.18.04.1, 7:3.4.8-0ubuntu0.2), libavutil-dev:amd64 (7:3.4.6-0ubuntu0.18.04.1, 7:3.4.8-0ubuntu0.2), libavcodec-dev:amd64 (7:3.4.6-0ubuntu0.18.04.1, 7:3.4.8-0ubuntu0.2), libavcodec57:amd64 (7:3.4.6-0ubuntu0.18.04.1, 7:3.4.8-0ubuntu0.2), libavutil55:amd64 (7:3.4.6-0ubuntu0.18.04.1, 7:3.4.8-0ubuntu0.2), libavdevice57:amd64 (7:3.4.6-0ubuntu0.18.04.1, 7:3.4.8-0ubuntu0.2), libswscale4:amd64 (7:3.4.6-0ubuntu0.18.04.1, 7:3.4.8-0ubuntu0.2), libswscale-dev:amd64 (7:3.4.6-0ubuntu0.18.04.1, 7:3.4.8-0ubuntu0.2), libavresample3:amd64 (7:3.4.6-0ubuntu0.18.04.1, 7:3.4.8-0ubuntu0.2) End-Date: 2020-07-22 20:28:11 Start-Date: 2020-07-27 09:16:45 Commandline: /usr/bin/unattended-upgrade Remove: linux-image-5.3.0-61-generic:amd64 (5.3.0-61.55~18.04.1), linux-modules-extra-5.3.0-61-generic:amd64 (5.3.0-61.55~18.04.1), linux-modules-5.3.0-61-generic:amd64 (5.3.0-61.55~18.04.1) End-Date: 2020-07-27 09:18:33 Start-Date: 2020-07-27 09:18:35 Commandline: /usr/bin/unattended-upgrade Remove: linux-headers-5.3.0-61-generic:amd64 (5.3.0-61.55~18.04.1) End-Date: 2020-07-27 09:19:08 Start-Date: 2020-07-27 09:19:09 Commandline: /usr/bin/unattended-upgrade Remove: linux-headers-5.3.0-61:amd64 (5.3.0-61.55~18.04.1) End-Date: 2020-07-27 09:19:15 Start-Date: 2020-07-27 09:19:20 Commandline: /usr/bin/unattended-upgrade Upgrade: libseccomp2:amd64 (2.4.3-1ubuntu3.18.04.2, 2.4.3-1ubuntu3.18.04.3) End-Date: 2020-07-27 09:19:24 Start-Date: 2020-07-27 09:19:25 Commandline: /usr/bin/unattended-upgrade Upgrade: libvncclient1:amd64 (0.9.11+dfsg-1ubuntu1.2, 0.9.11+dfsg-1ubuntu1.3) End-Date: 2020-07-27 09:19:32 Start-Date: 2020-07-27 09:19:34 Commandline: /usr/bin/unattended-upgrade Upgrade: openjdk-11-jre-headless:amd64 (11.0.7+10-2ubuntu2~18.04, 11.0.8+10-0ubuntu1~18.04.1), openjdk-11-jre:amd64 (11.0.7+10-2ubuntu2~18.04, 11.0.8+10-0ubuntu1~18.04.1) End-Date: 2020-07-27 09:19:48 Start-Date: 2020-07-27 20:05:42 Commandline: apt-get upgrade Requested-By: joaquin (1000) Upgrade: librsvg2-common:amd64 (2.40.20-2, 2.40.20-2ubuntu0.1), librsvg2-2:amd64 (2.40.20-2, 2.40.20-2ubuntu0.1) End-Date: 2020-07-27 20:05:53 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1889155/+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 1884255] Re: [AMD/ATI] SBx00 Azalia (Intel HDA) Audio Ubuntu 20.04 not working
Ok. Thanks for the help and guidance. Hugs. -- 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/1884255 Title: [AMD/ATI] SBx00 Azalia (Intel HDA) Audio Ubuntu 20.04 not working Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: New Bug description: When you start playing some audio, the sound disappears. 00:14.2 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 Azalia (Intel HDA) Subsystem: ASUSTeK Computer Inc. M5A78L LE Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel uname -a Linux Marcelo-STI-FX6300 5.4.0-37-generic #41-Ubuntu SMP Wed Jun 3 18:57:02 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux alsa-info !! !!ALSA Information Script v 0.4.65 !! !!Script ran on: Fri Jun 19 13:38:12 UTC 2020 !!Linux Distribution !!-- Ubuntu 20.04 LTS \n \l DISTRIB_ID=Ubuntu DISTRIB_DESCRIPTION="Ubuntu 20.04 LTS" NAME="Ubuntu" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.04 LTS" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies /privacy-policy" UBUNTU_CODENAME=focal !!DMI Information !!--- Manufacturer: System manufacturer Product Name: System Product Name Product Version: System Version Firmware Version: 1201 Board Vendor: ASUSTeK Computer INC. Board Name:M5A78L-M LX/BR !!ACPI Device Status Information !!--- /sys/bus/acpi/devices/ATK0110:00/status15 /sys/bus/acpi/devices/PNP0103:00/status15 /sys/bus/acpi/devices/PNP0400:00/status15 /sys/bus/acpi/devices/PNP0501:00/status15 /sys/bus/acpi/devices/PNP0C0C:00/status11 /sys/bus/acpi/devices/PNP0C0F:00/status9 /sys/bus/acpi/devices/PNP0C0F:01/status9 /sys/bus/acpi/devices/PNP0C0F:02/status9 /sys/bus/acpi/devices/PNP0C0F:03/status9 /sys/bus/acpi/devices/PNP0C0F:04/status9 /sys/bus/acpi/devices/PNP0C0F:05/status9 /sys/bus/acpi/devices/PNP0C0F:06/status9 /sys/bus/acpi/devices/PNP0C0F:07/status9 /sys/bus/acpi/devices/device:20/status 15 /sys/bus/acpi/devices/device:21/status 15 !!Kernel Information !!-- Kernel release:5.4.0-37-generic Operating System: GNU/Linux Architecture: x86_64 Processor: x86_64 SMP Enabled: Yes !!ALSA Version !! Driver version: k5.4.0-37-generic Library version:1.2.3 Utilities version: 1.2.2 !!Loaded ALSA modules !!--- snd_hda_intel !!Sound Servers on this system !! Pulseaudio: Installed - Yes (/usr/bin/pulseaudio) Running - Yes !!Soundcards recognised by ALSA !!- 0 [SB ]: HDA-Intel - HDA ATI SB HDA ATI SB at 0xfe9f4000 irq 16 !!PCI Soundcards installed in the system !!-- 00:14.2 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 Azalia (Intel HDA) [1002:4383] Subsystem: ASUSTeK Computer Inc. M5A78L LE [1043:8445] !!Modprobe options (Sound related) !! snd_pcsp: index=-2 snd_usb_audio: index=-2 snd_atiixp_modem: index=-2 snd_intel8x0m: index=-2 snd_via82xx_modem: index=-2 snd_atiixp_modem: index=-2 snd_intel8x0m: index=-2 snd_via82xx_modem: index=-2 snd_usb_audio: index=-2 snd_usb_caiaq: index=-2 snd_usb_ua101: index=-2 snd_usb_us122l: index=-2 snd_usb_usx2y: index=-2 snd_cmipci: mpu_port=0x330 fm_port=0x388 snd_pcsp: index=-2 snd_usb_audio: index=-2 snd_hda_intel: model=auto snd_hda_intel: dmic detect=0 !!Loaded sound module options !!--- !!Module: snd_hda_intel align_buffer_size : -1 bdl_pos_adj : -1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1 beep_mode : N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N dmic_detect : Y enable : Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y enable_msi : -1 id : (null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null) index : -1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1 jackpoll_ms :
[Kernel-packages] [Bug 1889155] Re: after recent upgrade, hdmi secondary monitor is not detected
** 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/1889155 Title: after recent upgrade, hdmi secondary monitor is not detected Status in linux package in Ubuntu: New Bug description: It is often hard to connect secondary monitors to my laptop because it uses nvidia. In ubuntu it worked without needing configuration, however, yesterday it just stopped detecting it. I will start downgrading the latest updates to see if I can find the culprit. The monitor does detect that something was plugged in. My laptop is "hp omen 15 ax201ns" (Specs: https://support.hp.com/rs-en/document/c05411183) I don't know what package caused the regression, but I attach the history of the last upgrades: Start-Date: 2020-07-22 20:27:48 Commandline: packagekit role='update-packages' Requested-By: joaquin (1000) Upgrade: libavresample-dev:amd64 (7:3.4.6-0ubuntu0.18.04.1, 7:3.4.8-0ubuntu0.2), libavformat57:amd64 (7:3.4.6-0ubuntu0.18.04.1, 7:3.4.8-0ubuntu0.2), libavfilter6:amd64 (7:3.4.6-0ubuntu0.18.04.1, 7:3.4.8-0ubuntu0.2), ffmpeg:amd64 (7:3.4.6-0ubuntu0.18.04.1, 7:3.4.8-0ubuntu0.2), libswresample2:amd64 (7:3.4.6-0ubuntu0.18.04.1, 7:3.4.8-0ubuntu0.2), libavformat-dev:amd64 (7:3.4.6-0ubuntu0.18.04.1, 7:3.4.8-0ubuntu0.2), libswresample-dev:amd64 (7:3.4.6-0ubuntu0.18.04.1, 7:3.4.8-0ubuntu0.2), libpostproc54:amd64 (7:3.4.6-0ubuntu0.18.04.1, 7:3.4.8-0ubuntu0.2), libavutil-dev:amd64 (7:3.4.6-0ubuntu0.18.04.1, 7:3.4.8-0ubuntu0.2), libavcodec-dev:amd64 (7:3.4.6-0ubuntu0.18.04.1, 7:3.4.8-0ubuntu0.2), libavcodec57:amd64 (7:3.4.6-0ubuntu0.18.04.1, 7:3.4.8-0ubuntu0.2), libavutil55:amd64 (7:3.4.6-0ubuntu0.18.04.1, 7:3.4.8-0ubuntu0.2), libavdevice57:amd64 (7:3.4.6-0ubuntu0.18.04.1, 7:3.4.8-0ubuntu0.2), libswscale4:amd64 (7:3.4.6-0ubuntu0.18.04.1, 7:3.4.8-0ubuntu0.2), libswscale-dev:amd64 (7:3.4.6-0ubuntu0.18.04.1, 7:3.4.8-0ubuntu0.2), libavresample3:amd64 (7:3.4.6-0ubuntu0.18.04.1, 7:3.4.8-0ubuntu0.2) End-Date: 2020-07-22 20:28:11 Start-Date: 2020-07-27 09:16:45 Commandline: /usr/bin/unattended-upgrade Remove: linux-image-5.3.0-61-generic:amd64 (5.3.0-61.55~18.04.1), linux-modules-extra-5.3.0-61-generic:amd64 (5.3.0-61.55~18.04.1), linux-modules-5.3.0-61-generic:amd64 (5.3.0-61.55~18.04.1) End-Date: 2020-07-27 09:18:33 Start-Date: 2020-07-27 09:18:35 Commandline: /usr/bin/unattended-upgrade Remove: linux-headers-5.3.0-61-generic:amd64 (5.3.0-61.55~18.04.1) End-Date: 2020-07-27 09:19:08 Start-Date: 2020-07-27 09:19:09 Commandline: /usr/bin/unattended-upgrade Remove: linux-headers-5.3.0-61:amd64 (5.3.0-61.55~18.04.1) End-Date: 2020-07-27 09:19:15 Start-Date: 2020-07-27 09:19:20 Commandline: /usr/bin/unattended-upgrade Upgrade: libseccomp2:amd64 (2.4.3-1ubuntu3.18.04.2, 2.4.3-1ubuntu3.18.04.3) End-Date: 2020-07-27 09:19:24 Start-Date: 2020-07-27 09:19:25 Commandline: /usr/bin/unattended-upgrade Upgrade: libvncclient1:amd64 (0.9.11+dfsg-1ubuntu1.2, 0.9.11+dfsg-1ubuntu1.3) End-Date: 2020-07-27 09:19:32 Start-Date: 2020-07-27 09:19:34 Commandline: /usr/bin/unattended-upgrade Upgrade: openjdk-11-jre-headless:amd64 (11.0.7+10-2ubuntu2~18.04, 11.0.8+10-0ubuntu1~18.04.1), openjdk-11-jre:amd64 (11.0.7+10-2ubuntu2~18.04, 11.0.8+10-0ubuntu1~18.04.1) End-Date: 2020-07-27 09:19:48 Start-Date: 2020-07-27 20:05:42 Commandline: apt-get upgrade Requested-By: joaquin (1000) Upgrade: librsvg2-common:amd64 (2.40.20-2, 2.40.20-2ubuntu0.1), librsvg2-2:amd64 (2.40.20-2, 2.40.20-2ubuntu0.1) End-Date: 2020-07-27 20:05:53 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1889155/+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 1389077] Re: [HP ProBook 4530s / Lenovo G580] Intel Powerclamp is Slowing CPU
I'm on 18.04, and saw huge cpu use all of a sudden by 4 tasks called kidle_inject running at 40% CPU each. I'm quite used to having this Thinkpad x230 tablet run hot since graphics e.g. for video don't seem to be accelerated. But in this case, the CPU and temperature as reported by psensor was not elevated before the kidle_inject processes went into overdrive. I'm not used to seeing them running normally. I followed the advice at kidle_inject causing very high load - Ask Ubuntu https://askubuntu.com/questions/584636/kidle-inject-causing-very-high-load to rmmod intel_powerclamp, and that killed the processes, but the temperature went up a bit, now to 100 degrees C, again despite low CPU load. So something is going wrong here... -- 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/1389077 Title: [HP ProBook 4530s / Lenovo G580] Intel Powerclamp is Slowing CPU Status in linux package in Ubuntu: Confirmed Bug description: I upgraded from KUbuntu 14.04 to 14.10. Immediately, while playing minecraft with my daughter, I noticed the game was running very slowly. Even after closing the game, my web browsing slowed to a crawl. Looking at the processes in top, I noticed there were 4 tasks called kidle_inject running at 50% CPU each. After spending a long time figuring out what caused this, I found out this is caused by the Intel Powerclamp driver. I never did anything to enable this, and haven't observed this slowdown before the upgrade. I found the powerclamp driver in the /sys/class/thermal/cooling_device5 directory: root@bkat-HP-ProBook-4530s:/sys/class/thermal/cooling_device5# cat type intel_powerclamp root@bkat-HP-ProBook-4530s:/sys/class/thermal/cooling_device5# cat cur_state -1 root@bkat-HP-ProBook-4530s:/sys/class/thermal/cooling_device5# cat max_state 50 I tried to echo 0 to cur_state, but it still reported -1 when I catted the value. There seems to be no obvious way to disable this, and this should not have been enabled in the first place. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-24-generic 3.16.0-24.32 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bkat 2780 F pulseaudio CurrentDesktop: KDE Date: Mon Nov 3 23:16:04 2014 HibernationDevice: RESUME=UUID=35e1d874-a3bd-4227-acab-16f3e929d993 InstallationDate: Installed on 2012-04-22 (925 days ago) InstallationMedia: Kubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) MachineType: Hewlett-Packard HP ProBook 4530s ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic root=UUID=743f1686-bfe7-4e32-911d-5371633ccec8 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.16.0-24-generic N/A linux-backports-modules-3.16.0-24-generic N/A linux-firmware 1.138 SourcePackage: linux UpgradeStatus: Upgraded to utopic on 2014-11-03 (0 days ago) dmi.bios.date: 05/13/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68SRR Ver. F.09 dmi.board.name: 167C dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 22.1A dmi.chassis.asset.tag: CNU1284V1X dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68SRRVer.F.09:bd05/13/2011:svnHewlett-Packard:pnHPProBook4530s:pvrA0001D02:rvnHewlett-Packard:rn167C:rvrKBCVersion22.1A:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP ProBook 4530s dmi.product.version: A0001D02 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1389077/+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 1889155] [NEW] after recent upgrade, hdmi secondary monitor is not detected
You have been subscribed to a public bug: It is often hard to connect secondary monitors to my laptop because it uses nvidia. In ubuntu it worked without needing configuration, however, yesterday it just stopped detecting it. I will start downgrading the latest updates to see if I can find the culprit. The monitor does detect that something was plugged in. My laptop is "hp omen 15 ax201ns" (Specs: https://support.hp.com/rs-en/document/c05411183) I don't know what package caused the regression, but I attach the history of the last upgrades: Start-Date: 2020-07-22 20:27:48 Commandline: packagekit role='update-packages' Requested-By: joaquin (1000) Upgrade: libavresample-dev:amd64 (7:3.4.6-0ubuntu0.18.04.1, 7:3.4.8-0ubuntu0.2), libavformat57:amd64 (7:3.4.6-0ubuntu0.18.04.1, 7:3.4.8-0ubuntu0.2), libavfilter6:amd64 (7:3.4.6-0ubuntu0.18.04.1, 7:3.4.8-0ubuntu0.2), ffmpeg:amd64 (7:3.4.6-0ubuntu0.18.04.1, 7:3.4.8-0ubuntu0.2), libswresample2:amd64 (7:3.4.6-0ubuntu0.18.04.1, 7:3.4.8-0ubuntu0.2), libavformat-dev:amd64 (7:3.4.6-0ubuntu0.18.04.1, 7:3.4.8-0ubuntu0.2), libswresample-dev:amd64 (7:3.4.6-0ubuntu0.18.04.1, 7:3.4.8-0ubuntu0.2), libpostproc54:amd64 (7:3.4.6-0ubuntu0.18.04.1, 7:3.4.8-0ubuntu0.2), libavutil-dev:amd64 (7:3.4.6-0ubuntu0.18.04.1, 7:3.4.8-0ubuntu0.2), libavcodec-dev:amd64 (7:3.4.6-0ubuntu0.18.04.1, 7:3.4.8-0ubuntu0.2), libavcodec57:amd64 (7:3.4.6-0ubuntu0.18.04.1, 7:3.4.8-0ubuntu0.2), libavutil55:amd64 (7:3.4.6-0ubuntu0.18.04.1, 7:3.4.8-0ubuntu0.2), libavdevice57:amd64 (7:3.4.6-0ubuntu0.18.04.1, 7:3.4.8-0ubuntu0.2), libswscale4:amd64 (7:3.4.6-0ubuntu0.18.04.1, 7:3.4.8-0ubuntu0.2), libswscale-dev:amd64 (7:3.4.6-0ubuntu0.18.04.1, 7:3.4.8-0ubuntu0.2), libavresample3:amd64 (7:3.4.6-0ubuntu0.18.04.1, 7:3.4.8-0ubuntu0.2) End-Date: 2020-07-22 20:28:11 Start-Date: 2020-07-27 09:16:45 Commandline: /usr/bin/unattended-upgrade Remove: linux-image-5.3.0-61-generic:amd64 (5.3.0-61.55~18.04.1), linux-modules-extra-5.3.0-61-generic:amd64 (5.3.0-61.55~18.04.1), linux-modules-5.3.0-61-generic:amd64 (5.3.0-61.55~18.04.1) End-Date: 2020-07-27 09:18:33 Start-Date: 2020-07-27 09:18:35 Commandline: /usr/bin/unattended-upgrade Remove: linux-headers-5.3.0-61-generic:amd64 (5.3.0-61.55~18.04.1) End-Date: 2020-07-27 09:19:08 Start-Date: 2020-07-27 09:19:09 Commandline: /usr/bin/unattended-upgrade Remove: linux-headers-5.3.0-61:amd64 (5.3.0-61.55~18.04.1) End-Date: 2020-07-27 09:19:15 Start-Date: 2020-07-27 09:19:20 Commandline: /usr/bin/unattended-upgrade Upgrade: libseccomp2:amd64 (2.4.3-1ubuntu3.18.04.2, 2.4.3-1ubuntu3.18.04.3) End-Date: 2020-07-27 09:19:24 Start-Date: 2020-07-27 09:19:25 Commandline: /usr/bin/unattended-upgrade Upgrade: libvncclient1:amd64 (0.9.11+dfsg-1ubuntu1.2, 0.9.11+dfsg-1ubuntu1.3) End-Date: 2020-07-27 09:19:32 Start-Date: 2020-07-27 09:19:34 Commandline: /usr/bin/unattended-upgrade Upgrade: openjdk-11-jre-headless:amd64 (11.0.7+10-2ubuntu2~18.04, 11.0.8+10-0ubuntu1~18.04.1), openjdk-11-jre:amd64 (11.0.7+10-2ubuntu2~18.04, 11.0.8+10-0ubuntu1~18.04.1) End-Date: 2020-07-27 09:19:48 Start-Date: 2020-07-27 20:05:42 Commandline: apt-get upgrade Requested-By: joaquin (1000) Upgrade: librsvg2-common:amd64 (2.40.20-2, 2.40.20-2ubuntu0.1), librsvg2-2:amd64 (2.40.20-2, 2.40.20-2ubuntu0.1) End-Date: 2020-07-27 20:05:53 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- after recent upgrade, hdmi secondary monitor is not detected https://bugs.launchpad.net/bugs/1889155 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 1887916] Re: Got kernel panic on clean install of Ubuntu 20.04 LTS with external HDMI display connected to integrated intel graphics adapter in Asustek UX32A laptop
Please file an upstream bug at intel graphics upstream: https://gitlab.freedesktop.org/drm/intel/wikis/How-to-file-i915-bugs -- 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/1887916 Title: Got kernel panic on clean install of Ubuntu 20.04 LTS with external HDMI display connected to integrated intel graphics adapter in Asustek UX32A laptop Status in linux package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Download Ubuntu 20.04 LTS installation media 2. Run the installation on the Asustek UX32A laptop without external display connected 3. Finish the installation, boot installed system, install all updates 4. Connect external monitor to the HDMI output of the laptop 5. Boot Ubuntu 20.04 LTS with monitor attached Expected results: * Ubuntu founds two screens, user is able to use both of them Actual results: * Ubuntu freezes during boot. Workaround (very ill variant) - boot the system with `nomodeset`. It is ill variant because of single monitor configuration. It is hard to get logs for the freeze, below is the OCR version of the log obtained with `verbose INIT_VERBOSE=y noplymouth`: ``` [ 43.500044] Hardware name: ASUSTeK COMPUTER INC. UX32A/UX32A. BIOS UX32A.216 02/12/2014 [ 43.5000491 Workqueue: events_unbound_async_run_entry_fn [ 43.500098] RIP: 0010:intel_disable_pipe+0x1c8/0x1d0 [i915] [ 43.500099J Code: e9 b2 fe ff fr 31 f6 1c 89 c? e0 23 cb ff ff 18 8d 65 d8 5b 41 5c 41 Sd 41 5e 41 5f 5d c3 40 c7 c7 de b4 44 c0 e8 33 9b 54 fb <0f> 0b e9 63 ff ff ff 90 0f If 44 00 00 55 48 8d 46 30 48 89 cl 18 [ 43.500100] RSP: 0018:b93d400737a0 EFLAGS: 00010286 [ 43.500101] RAX: RBX: 98ff027c RCX: [ 43.500102] RDX: RSI: 0002 RDI: 0202 [ 43.500102] RBP: b93d400737c8 R08: 000a20ccb1d7 R09: bd394dc4 [ 43.500103] R10: 041d R11: 0002aef0 R12: 98ff027c077B [ 43.500103] R13: 98ff120e8000 R14: 00070008 R15: [ 43.500105] FS: () GS:98ff14e0() knlGS: [ 43.500105] CS: 0010 DS: ES: CR0: 60050033 [ 43.500106] CR2 : 55ad3bd4f668 CR3: 000ld720a005 CR4: 001606f0 [ 43.500107] Call Trace: [ 43.500153]ironlake_crtc_disable+0x7e/0x540 [i915] [ 43.500198]intel_atomic_commit_tail+0x261/0x12e0 [i915] [ 43.500201]? flush_workqueue_prep_pwqs+0x12e/0x140 [ 43.500245]intel_atomic_commit+0x204/0x2b0 [i915] [ 43.500267]drm_atomic_commit+0x4a/0x50 [drm] [ 43.500280]drm_client_modeset_commit_atomic+0x1d0/0x1f0 [drm] [ 43.500292]drm_client_modeset_commit_force+0x55/0x160 [drm] [ 43.500361]drm_fb_helper_pan_display+0xfc/0x230 [drm_kms_helper] [ 43.500348]intel_fbdev_pan_display+0x1b/0x40 [i915] [ 43.506352]fb_pan_display+0x0c/0x110 [ 43.500353]bit_update_start +0x20/0x50 [ 43.500355]fbcon_switch+0x3e5/0x5d0 [ 43.500359]redraw_screen+0xfe/0x270 [ 43.500360]do_bind_con_driver.cold+0x94/0xe4 [ 43.500362]do_take_over_console+0x12f/0x1a0 [ 43.500364]do_fbcon_takeover+0x5c/0xb0 [ 43.500365]fbcon_fb_registered+0xf4/0x100 [ 43.500366]register_framebuffer+0x207/0x310 [ 43.500373]__drm_fb_helper_initial_config_and_unlock+0x303/0x440 [drm_kms_helper] [ 43.500379]drm_fb_helper_initial_config+0x36/0x40 [drm_kms_helper] [ 43.500421]intel_fbdev_initial_config+0x18/0x30 [i915] [ 43.500425]async_run_entry_fn+0x3c/0x150 [ 43.500426]process_one_work+0x1eb/0x3b0 [ 43.500428]worker_thread+0x4d/0x400 [ 43.500429]kthread+0x104/0x140 [ 43.500431]? process_one_work+0x3b0/0x3b0 [ 43.500432]? kthread_park+0x90/0x90 [ 43.500434]ret_from_fork+0x35/0x40 [ 43.500436] --- [ end trace 32c5f2079451ea7c ] --- [ 44.604015] [drm:ironlake_crtc_enable [i915]] *ERROR* mode set failed: pipe A stuck [ 54.659975] [drm:drm_atomic_helper_wait_for_flip_done [drm_kms_helper]] *ERROR* [CRTC:42:pipe A] flip_done timed out [ 54.766978] i915 :00:02.0: fb0: i915drmfb frame buffer device ``` ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-modules-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mate 1144 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Fri Jul 17 12:15:08 2020 Dependencies: MachineType: ASUSTeK COMPUTER INC. UX32A ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz
[Kernel-packages] [Bug 1875199] Re: [NUC8CCHK][HDA-Intel - HDA Intel PCH, playback] No sound at all
Please test the kernel here: https://people.canonical.com/~khfeng/lp1875199/ -- 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/1875199 Title: [NUC8CCHK][HDA-Intel - HDA Intel PCH, playback] No sound at all Status in linux package in Ubuntu: Incomplete Bug description: No sound output. Only a 'Dummy' audio output device is listed in the Gnome Sound application. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rboerner 1205 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Apr 26 12:12:49 2020 InstallationDate: Installed on 2020-04-25 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rboerner 1205 F pulseaudio Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: No sound at all Title: [HDA-Intel - HDA Intel PCH, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/25/2020 dmi.bios.vendor: Intel Corp. dmi.bios.version: CHAPLCEL.0048.2020.0225.1640 dmi.board.name: NUC8CCHB dmi.board.vendor: Intel Corporation dmi.board.version: K44767-502 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrCHAPLCEL.0048.2020.0225.1640:bd02/25/2020:svnIntel(R)ClientSystems:pnNUC8CCHK:pvrK44798-502:rvnIntelCorporation:rnNUC8CCHB:rvrK44767-502:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: CH dmi.product.name: NUC8CCHK dmi.product.sku: BKNUC8CCHKR dmi.product.version: K44798-502 dmi.sys.vendor: Intel(R) Client Systems --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rboerner 1215 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-25 (6 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Intel(R) Client Systems NUC8CCHK Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-generic root=UUID=afbb0f64-e729-46a8-82e4-a060e9e729c4 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 RelatedPackageVersions: linux-restricted-modules-5.4.0-28-generic N/A linux-backports-modules-5.4.0-28-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-28-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: 02/25/2020 dmi.bios.vendor: Intel Corp. dmi.bios.version: CHAPLCEL.0048.2020.0225.1640 dmi.board.name: NUC8CCHB dmi.board.vendor: Intel Corporation dmi.board.version: K44767-502 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrCHAPLCEL.0048.2020.0225.1640:bd02/25/2020:svnIntel(R)ClientSystems:pnNUC8CCHK:pvrK44798-502:rvnIntelCorporation:rnNUC8CCHB:rvrK44767-502:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: CH dmi.product.name: NUC8CCHK dmi.product.sku: BKNUC8CCHKR dmi.product.version: K44798-502 dmi.sys.vendor: Intel(R) Client Systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875199/+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 1886920] Re: Battery drain during sleep. System suspended before kernel suspends all tasks. Lenovo ThinkPad T460
Nothing suspicious, really. And the system seems to be too old to support pmc_core, so we can't check the SoC state easily. Please install latest mainline kernel: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.8-rc7/ Then boot with kernel parameter "dyndbg='file drivers/pci/* +p; file drivers/usb/* +p' log_buf_len=16M", do a S3, then attach dmesg. -- 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/1886920 Title: Battery drain during sleep. System suspended before kernel suspends all tasks. Lenovo ThinkPad T460 Status in linux package in Ubuntu: Confirmed Bug description: The same as https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825636. kaihengfeng closed that one "Because there's no response from the original bug reporter." and asked to file a report for all devices affected, so here I am, duplicating the report. On Ubuntu MATE 18.04, as well as after the update to 20.04, the battery drains about 1,25% per hour of sleep (if I just close the lid). $ cat /sys/power/mem_sleep s2idle [deep] tlp was initially installed on my machine. However, this behaviour also occurs if I $ sudo apt purge tlp acpi-call-dkms && sudo reboot now also, it occurs when booting from a freshly made MATE 20.04 live usb stick, so TLP shouldn't be the culprit. All the log files look in all relevant aspects similar to what was reported in the old report. I'm happy to provide log files from my machine, if any are necessary. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: richard1511 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: MATE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2018-07-12 (735 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b52c Chicony Electronics Co., Ltd Integrated Camera 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 10: Dev 3, If 0, Class=Video, Driver=uvcvideo, 480M |__ Port 10: Dev 3, If 1, Class=Video, Driver=uvcvideo, 480M MachineType: LENOVO 20FMS03600 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic root=/dev/mapper/ubuntu--mate--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 Tags: focal Uname: Linux 5.4.0-40-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-05-22 (55 days ago) UserGroups: adm cdrom dialout dip docker lpadmin plugdev sambashare sudo tty uucp _MarkForUpload: True dmi.bios.date: 09/21/2018 dmi.bios.vendor: LENOVO dmi.bios.version: R06ET64W (1.38 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FMS03600 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR06ET64W(1.38):bd09/21/2018:svnLENOVO:pn20FMS03600:pvrThinkPadT460:rvnLENOVO:rn20FMS03600:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460 dmi.product.name: 20FMS03600 dmi.product.sku: LENOVO_MT_20FM_BU_Think_FM_ThinkPad T460 dmi.product.version: ThinkPad T460 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886920/+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 1791427] Re: Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1 Carbon 6th
Anyone know what happened to Aaron's patch? The discussion at https://patchwork.kernel.org/patch/10822515/ ends on November last year with this question from Kai-Heng: > Users reported that patch [1/2] alone can solve the issue. > > Do we need more information before making this fix merged? > > Kai-Heng Would be really great if it could be merged :( Anyone tried a very recent kernel and can confirm the issue is still there BTW? -- 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/1791427 Title: Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1 Carbon 6th Status in linux package in Ubuntu: Triaged Bug description: Ubuntu 18.04.1 Terminology in case we use different terms: touchpad - just the rectangular touch-sensitive surface below the keyboard (xinput lists it as Synaptics TM3288-011) trackpoint - the red thingy built into the keyboard + 3 physical buttons below the keyboard (trackpoint and buttons are integrated together; listed in xinput as TPPS/2 Elan TrackPoint) On September 7th, 2018, Lenovo has issued a BIOS update (v1.30), which enables proper S3 deep sleep state - users no longer have to patch DSDT tables to get it. It can be enabled in the BIOS settings. In X1 carbon 6th generation models that have NFC, when laptop wakes from suspend by opening the lid, in most cases both touchpad and trackpoint stop working completely. They are also no longer listed when running xinput command. Sometimes just one of them stops working, usually the trackpoint. In some rare cases it is possible to bring them back by using these commands: echo -n none > /sys/devices/platform/i8042/serio1/drvctl echo -n reconnect > /sys/devices/platform/i8042/serio1/drvctl rmmod psmouse modprobe psmouse These worked properly when waking up from S2Idle sleep state (had these in a script that runs after waking the machine from suspend), but with S3 deep sleep these rarely work and the only way to bring back touchpad and/or trackpoint is turning off the machine and turning it on (restart does not help). I could not find any pattern that would show when the input devices stop working or start working again using the commands mentioned above. It's completely random from my perspective. This is happening on the standard issue 4.15.0-33-generic kernel that shipped with my Ubuntu 18.04 (with updates), as well as with newer mainline kernels, such as the newest point versions of 4.17, 4.18 and 4.19 RC2. This happens regardless of whether "blacklist i2c_i801" is commented out in /etc/modprobe.d/blacklist.conf or not. It happens regardless of whether "psmouse.synaptics_intertouch=1" is passed as grub parameter. Presence of TLP does not make it better, nor worse. It appears that non-NFC models are not affected. I know at least one Arch Linux user who has the exact same model, but without this issue. I'm using synaptics driver (no libinput installed), he uses libinput and doesn't have synaptics, if that information is of any use. Libinput does not seem to help. This forum thread also has more details from users who updated their BIOS to get S3 suspend: https://forums.lenovo.com/t5/Linux- Discussion/X1-Carbon-Gen-6-cannot-enter-deep-sleep-S3-state-aka- Suspend-to/td-p/3998182/page/27 Another related thread: https://bbs.archlinux.org/viewtopic.php?id=236367 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-33-generic 4.15.0-33.36 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: maciej 2651 F...m pulseaudio /dev/snd/controlC0: maciej 2651 F pulseaudio CurrentDesktop: i3 Date: Sat Sep 8 13:45:43 2018 HibernationDevice: RESUME=UUID=3116dcb0-d91e-4b2a-8166-43b7a9a9d36e InstallationDate: Installed on 2018-07-21 (49 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 13d3:56b2 IMC Networks Bus 001 Device 002: ID 04b4:0060 Cypress Semiconductor Corp. Wireless optical mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20KH006KPB ProcFB: 0 EFI VGA 1 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-33-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash psmouse.synaptics_intertouch=1 vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-33-generic N/A linux-backports-modules-4.15.0-33-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install)
[Kernel-packages] [Bug 1889282] [NEW] add pvtime support for arm64 guests
Public bug reported: The mainline patch set "arm64: Stolen time support" and its prerequisites are required to support future AWS instance types: Reference: https://lore.kernel.org/kvm/20191011125930.40834-1-steven.pr...@arm.com/ The list of patches (from mainline) needed for linux-aws/focal is: e0685fa228fd arm64: Retrieve stolen time as paravirtualized guest ce4d5ca2b9dd arm/arm64: Make use of the SMCCC 1.1 wrapper 541625ac47ce arm/arm64: Provide a wrapper for SMCCC 1.1 calls 58772e9a3db7 KVM: arm64: Provide VCPU attributes for stolen time 8538cb22bbce KVM: Allow kvm_device_ops to be const 8564d6372a7d KVM: arm64: Support stolen time reporting via shared structure cac0f1b7285e KVM: Implement kvm_put_guest() b48c1a45a190 KVM: arm64: Implement PV_TIME_FEATURES call 55009c6ed2d2 KVM: arm/arm64: Factor out hypercall handling from PSCI code 6a7458485b39 KVM: arm64: Document PV-time interface e6ea46511b1a firmware: arm_sdei: use common SMCCC_CONDUIT_* a5520eac4d2d firmware/psci: use common SMCCC_CONDUIT_* 6848253ddeae arm: spectre-v2: use arm_smccc_1_1_get_conduit() c98bd2991728 arm64: errata: use arm_smccc_1_1_get_conduit() 6b7fe77c334a arm/arm64: smccc/psci: add arm_smccc_1_1_get_conduit() ** Affects: linux-aws (Ubuntu) Importance: Undecided Assignee: Kamal Mostafa (kamalmostafa) Status: In Progress ** Affects: linux-aws-5.4 (Ubuntu) Importance: Undecided Assignee: Kamal Mostafa (kamalmostafa) Status: In Progress ** Affects: linux-aws-5.4 (Ubuntu Bionic) Importance: Undecided Assignee: Kamal Mostafa (kamalmostafa) Status: In Progress ** Affects: linux-aws (Ubuntu Focal) Importance: Undecided Assignee: Kamal Mostafa (kamalmostafa) Status: In Progress ** Also affects: linux-aws (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-aws-5.4 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-aws (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux-aws-5.4 (Ubuntu Bionic) Importance: Undecided Status: New ** No longer affects: linux-aws-5.4 (Ubuntu Focal) ** No longer affects: linux-aws (Ubuntu Bionic) ** Changed in: linux-aws (Ubuntu Focal) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) ** Changed in: linux-aws-5.4 (Ubuntu) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) ** Changed in: linux-aws-5.4 (Ubuntu Bionic) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) ** Changed in: linux-aws (Ubuntu Focal) Status: New => In Progress ** Changed in: linux-aws-5.4 (Ubuntu) Status: New => In Progress ** Changed in: linux-aws-5.4 (Ubuntu Bionic) Status: New => In Progress -- 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/1889282 Title: add pvtime support for arm64 guests Status in linux-aws package in Ubuntu: In Progress Status in linux-aws-5.4 package in Ubuntu: In Progress Status in linux-aws-5.4 source package in Bionic: In Progress Status in linux-aws source package in Focal: In Progress Bug description: The mainline patch set "arm64: Stolen time support" and its prerequisites are required to support future AWS instance types: Reference: https://lore.kernel.org/kvm/20191011125930.40834-1-steven.pr...@arm.com/ The list of patches (from mainline) needed for linux-aws/focal is: e0685fa228fd arm64: Retrieve stolen time as paravirtualized guest ce4d5ca2b9dd arm/arm64: Make use of the SMCCC 1.1 wrapper 541625ac47ce arm/arm64: Provide a wrapper for SMCCC 1.1 calls 58772e9a3db7 KVM: arm64: Provide VCPU attributes for stolen time 8538cb22bbce KVM: Allow kvm_device_ops to be const 8564d6372a7d KVM: arm64: Support stolen time reporting via shared structure cac0f1b7285e KVM: Implement kvm_put_guest() b48c1a45a190 KVM: arm64: Implement PV_TIME_FEATURES call 55009c6ed2d2 KVM: arm/arm64: Factor out hypercall handling from PSCI code 6a7458485b39 KVM: arm64: Document PV-time interface e6ea46511b1a firmware: arm_sdei: use common SMCCC_CONDUIT_* a5520eac4d2d firmware/psci: use common SMCCC_CONDUIT_* 6848253ddeae arm: spectre-v2: use arm_smccc_1_1_get_conduit() c98bd2991728 arm64: errata: use arm_smccc_1_1_get_conduit() 6b7fe77c334a arm/arm64: smccc/psci: add arm_smccc_1_1_get_conduit() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1889282/+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 1888570] Re: poweroff not working after apt upgrade
@alexhung, Thanks, same result: bad -- 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/1888570 Title: poweroff not working after apt upgrade Status in linux package in Ubuntu: Confirmed Bug description: System-Information: Description: Ubuntu 18.04.4 LTS Release: 18.04 ## Working packages: - Kernel 5.3.0.61.114 - linux-firmware 1.173.18 Problem occurs when upgrading (anyone of) these packages - Kernel 5.3.0-62.56 - linux-firmware 1.173.19 I use an Acer Aspire E5-771G Notebook with a fresh installation of Ubuntu 18.04. Till the last upgrade everything works as expected. The last upgrade brings two new kernel versions (as mentioned above). Now the system stucks at the very end of the power down sequence. Even SysReq-O will not work (only SysReq-B will work). Because I use Systemback, I time shift to the previous system and then install package by package to see what will bring in the problem. If I install any of the mentioned kernel updates the problem will show up. I had ask the above question on "askubuntu.com". I was directed to upgrade the BIOS, But even after doing so the problem still persist. I am not sure if I do it right (APT pinning). I currently create a file /etc/apt/prefereces.d/kernel. I add an entry for every of the following packages to block the version mentioned above (Pin: version: Pin-Priority: -1): linux-generic-hwe-18.04 linux-headers-generic-hwe-18.04 linux-image-generic-hwe-18.04 linux-modules-nvidia-440-generic-hwe-18.04 linux-firmware After doing so "apt list --upgradeable" will not list the packages in question and the PC will power down normally (and SysReq-O WILL work). In the meanwhile there are newer versions of the kernel online, so the above mentioned pinning will allow the newer kernels to get installed and the problem will show up again. So I block these versions too. BTW: Due to the stuck I am able to see some other error messages that are not reported in the journal. The very last 3-5 lines show: shutdown [1]: Failed to wait for process: Protocol error These lines are present although in the working kernels, but hard to see, because the system powers down some ms after these lines are displayed! This problem seams to be solved more than one year ago in the upstream kernel! --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gneiss 1929 F pulseaudio /dev/snd/controlC0: gneiss 1929 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-05-02 (448 days ago) InstallationMedia: MachineType: Acer Aspire E5-771G NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: LANG=de_DE.UTF-8 SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, no user) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-61-generic root=UUID=0b245afe-758b-4e45-a473-ad2077260d8f ro noplymouth resume=UUID=79a9e809-6ba1-491b-acfc-1816057c2dee ProcVersionSignature: Ubuntu 5.3.0-61.55~18.04.1-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-61-generic N/A linux-backports-modules-5.3.0-61-generic N/A linux-firmware1.173.18 Tags: bionic Uname: Linux 5.3.0-61-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip input lpadmin plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 09/02/2015 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.23 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: EA70_HB dmi.board.vendor: Acer dmi.board.version: Type2 - A01 Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.23:bd09/02/2015:svnAcer:pnAspireE5-771G:pvrV3.72:rvnAcer:rnEA70_HB:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: BDW dmi.product.name: Aspire E5-771G dmi.product.sku: Aspire E5-771G_0884_1_23 dmi.product.version: V3.72 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888570/+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 887793] Re: [HP 6710b] Kworker constantly taking about 100% CPU
For anyone finding this the problem has re-appeared with Ubuntu 20.04 on a
Fujitsu Lifebook A544 after upgrading to BIOS version 1.24 (or 1.25). It shows
itself as workers kacpid and acpid_notify hogging most of a core. the fix (or
workaround?) is to run
sudo sh -c 'echo "disable" > /sys/firmware/acpi/interrupts/gpe13'
which works until a reboot, or to make it persistent add to the root crontab
(using sudo crontab -e)
@reboot echo "disable" > /sys/firmware/acpi/interrupts/gpe13
Whether this has any side effects I don't know.
--
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/887793
Title:
[HP 6710b] Kworker constantly taking about 100% CPU
Status in linux package in Ubuntu:
Confirmed
Bug description:
I've this issue since the latest Ubuntu 11.10 version, all updates
applied till today, and it's still there. Ubuntu 11.04 did not have
this issue.
If I run top there is a Kworker constantly taking much CPU, I don't
know how to research where this comes from.
ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: linux-image-3.0.0-12-generic 3.0.0-12.20
ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
Uname: Linux 3.0.0-12-generic i686
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
AplayDevices:
List of PLAYBACK Hardware Devices
card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
ApportVersion: 1.23-0ubuntu4
Architecture: i386
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: kp 1473 F pulseaudio
CRDA: Error: [Errno 2] Bestand of map bestaat niet
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xe4404000 irq 46'
Mixer name : 'Analog Devices AD1981'
Components : 'HDA:11d41981,103c30c0,00100200
HDA:11c11040,103c1378,00100200'
Controls : 11
Simple ctrls : 9
Date: Tue Nov 8 22:29:10 2011
HibernationDevice: RESUME=UUID=ad8d4a18-9fe4-4246-ba44-85cf6b4dace5
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
MachineType: Hewlett-Packard HP Compaq 6710b (GB891ET#ABH)
PccardctlIdent:
Socket 0:
no product info available
PccardctlStatus:
Socket 0:
no card
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-12-generic
root=UUID=686d2155-83a9-4743-a2a4-8e9570ee3da6 ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-3.0.0-12-generic N/A
linux-backports-modules-3.0.0-12-generic N/A
linux-firmware1.60
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/15/2009
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68DDU Ver. F.15
dmi.board.name: 30C0
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 71.2E
dmi.chassis.asset.tag: CNU72913PH
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias:
dmi:bvnHewlett-Packard:bvr68DDUVer.F.15:bd01/15/2009:svnHewlett-Packard:pnHPCompaq6710b(GB891ET#ABH):pvrF.15:rvnHewlett-Packard:rn30C0:rvrKBCVersion71.2E:cvnHewlett-Packard:ct10:cvr:
dmi.product.name: HP Compaq 6710b (GB891ET#ABH)
dmi.product.version: F.15
dmi.sys.vendor: Hewlett-Packard
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/887793/+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
Re: [Kernel-packages] [Bug 1888571] Re: [Ice Lake] Screen flickering and glitching after install
Yep - I’ve tried removing nomodeset after this update but it hasn’t seemed to take away the flickering, leaving it on for the time being until the bug is fixed. On Mon, Jul 27, 2020 at 9:50 PM Daniel van Vugt <1888...@bugs.launchpad.net> wrote: > Oh, you do have that fix already. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1888571 > > Title: > [Ice Lake] Screen flickering and glitching after install > > Status in linux package in Ubuntu: > Confirmed > > Bug description: > Intel integrated driver causes screen flickering with Ubuntu install. > Windows did not have this issue > > ProblemType: Bug > DistroRelease: Ubuntu 20.04 > Package: xorg 1:7.7+19ubuntu14 > ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 > Uname: Linux 5.4.0-42-generic x86_64 > ApportVersion: 2.20.11-0ubuntu27.4 > Architecture: amd64 > BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' > CasperMD5CheckResult: skip > CompositorRunning: None > CurrentDesktop: ubuntu:GNOME > Date: Wed Jul 22 15:41:42 2020 > DistUpgraded: Fresh install > DistroCodename: focal > DistroVariant: ubuntu > ExtraDebuggingInterest: Yes, if not too technical > GraphicsCard: >Intel Corporation Iris Plus Graphics G7 [8086:8a52] (rev 07) (prog-if > 00 [VGA controller]) > Subsystem: Hewlett-Packard Company Iris Plus Graphics G7 [103c:875a] > InstallationDate: Installed on 2020-07-22 (0 days ago) > InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 > (20200423) > MachineType: HP HP ENVY Laptop 13-ba0xxx > 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.4.0-42-generic > root=UUID=9f807172-2b35-4ad1-9f33-5a912ad7c579 ro quiet splash vt.handoff=7 > SourcePackage: xorg > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 06/04/2020 > dmi.bios.vendor: Insyde > dmi.bios.version: F.10 > dmi.board.asset.tag: Type2 - Board Asset Tag > dmi.board.name: 875A > dmi.board.vendor: HP > dmi.board.version: 07.34 > dmi.chassis.asset.tag: Chassis Asset Tag > dmi.chassis.type: 10 > dmi.chassis.vendor: HP > dmi.chassis.version: Chassis Version > dmi.modalias: > dmi:bvnInsyde:bvrF.10:bd06/04/2020:svnHP:pnHPENVYLaptop13-ba0xxx:pvrType1ProductConfigId:rvnHP:rn875A:rvr07.34:cvnHP:ct10:cvrChassisVersion: > dmi.product.family: 103C_5335KV HP Envy > dmi.product.name: HP ENVY Laptop 13-ba0xxx > dmi.product.sku: 8KD13AV > dmi.product.version: Type1ProductConfigId > dmi.sys.vendor: HP > 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 N/A > version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 > version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A > version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 > version.xserver-xorg-video-intel: xserver-xorg-video-intel > 2:2.99.917+git20200226-1 > version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888571/+subscriptions > -- Drew Erikson University of Minnesota - Twin Cities Computer Science & Mathematics | 2020 eriks...@umn.edu -- 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/1888571 Title: [Ice Lake] Screen flickering and glitching after install Status in linux package in Ubuntu: Confirmed Bug description: Intel integrated driver causes screen flickering with Ubuntu install. Windows did not have this issue ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jul 22 15:41:42 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Iris Plus Graphics G7 [8086:8a52] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Iris Plus Graphics G7 [103c:875a] InstallationDate: Installed on 2020-07-22 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: HP HP ENVY Laptop 13-ba0xxx ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine:
[Kernel-packages] [Bug 1886920] Re: Battery drain during sleep. System suspended before kernel suspends all tasks. Lenovo ThinkPad T460
I commented out the three lines in /etc/rc.local and did the following: $ echo "blacklist btusb" | sudo tee /etc/modprobe.d/blacklist-btusb.conf $ sudo update-initramfs -u $ sudo reboot now output of dmesg does not contain "Bluetooth" (case sensitive) anymore and `lsmod | grep bt` gives no results. The battery consumption while sleeping is still the same. Syslog unchanged. -- 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/1886920 Title: Battery drain during sleep. System suspended before kernel suspends all tasks. Lenovo ThinkPad T460 Status in linux package in Ubuntu: Confirmed Bug description: The same as https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825636. kaihengfeng closed that one "Because there's no response from the original bug reporter." and asked to file a report for all devices affected, so here I am, duplicating the report. On Ubuntu MATE 18.04, as well as after the update to 20.04, the battery drains about 1,25% per hour of sleep (if I just close the lid). $ cat /sys/power/mem_sleep s2idle [deep] tlp was initially installed on my machine. However, this behaviour also occurs if I $ sudo apt purge tlp acpi-call-dkms && sudo reboot now also, it occurs when booting from a freshly made MATE 20.04 live usb stick, so TLP shouldn't be the culprit. All the log files look in all relevant aspects similar to what was reported in the old report. I'm happy to provide log files from my machine, if any are necessary. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: richard1511 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: MATE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2018-07-12 (735 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b52c Chicony Electronics Co., Ltd Integrated Camera 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 10: Dev 3, If 0, Class=Video, Driver=uvcvideo, 480M |__ Port 10: Dev 3, If 1, Class=Video, Driver=uvcvideo, 480M MachineType: LENOVO 20FMS03600 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic root=/dev/mapper/ubuntu--mate--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 Tags: focal Uname: Linux 5.4.0-40-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-05-22 (55 days ago) UserGroups: adm cdrom dialout dip docker lpadmin plugdev sambashare sudo tty uucp _MarkForUpload: True dmi.bios.date: 09/21/2018 dmi.bios.vendor: LENOVO dmi.bios.version: R06ET64W (1.38 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FMS03600 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR06ET64W(1.38):bd09/21/2018:svnLENOVO:pn20FMS03600:pvrThinkPadT460:rvnLENOVO:rn20FMS03600:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460 dmi.product.name: 20FMS03600 dmi.product.sku: LENOVO_MT_20FM_BU_Think_FM_ThinkPad T460 dmi.product.version: ThinkPad T460 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886920/+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 1888950] Re: Touchpad doesn't work
Sure I'll try to do that in the next few days. Once I boot with those params should I reattach /proc/bus/input/devices? Also my touchpad started working all of a sudden. I turned my laptop on and the touchpad was just working for some reason. I see the touchpad entry in /proc/bus/input/devices as well now. -- 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/1888950 Title: Touchpad doesn't work Status in linux package in Ubuntu: Confirmed Bug description: I just reinstalled kubuntu and while using my laptop my touchpad stopped working. I restarted my computer and now the touchpad doesn't show up at all and doesn't work. I followed the instructions here https://wiki.ubuntu.com/DebuggingTouchpadDetection#In_case_your_Touchpad_doesn.27t_work_at_all_.28No_response_from_the_Touchpad.29 and the instructions say to file a bug since I don't see a synaptics touchpad entry in /proc/bus/input/devices. As instructed, I will also attach that file. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-42-generic 5.4.0-42.46 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chris 977 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Sat Jul 25 10:33:04 2020 InstallationDate: Installed on 2020-07-25 (0 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20KH002RUS ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=a844f512-56a4-4f99-a77e-b86a753812f7 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/16/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET68W (1.43 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KH002RUS dmi.board.vendor: LENOVO dmi.board.version: SDK0K17763 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN23ET68W(1.43):bd10/16/2019:svnLENOVO:pn20KH002RUS:pvrThinkPadX1Carbon:rvnLENOVO:rn20KH002RUS:rvrSDK0K17763WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon dmi.product.name: 20KH002RUS dmi.product.sku: LENOVO_MT_20KH_BU_Think_FM_ThinkPad X1 Carbon dmi.product.version: ThinkPad X1 Carbon dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888950/+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
Re: [Kernel-packages] [Bug 1888963] Re: My touchpad is not working at all on ubuntu
Hi, thanks for your answer. Now I know that is a security issue and not a bug. How can I fix this to be able to use the touchpad on Ubuntu on my laptop ? Le mar. 28 juil. 2020 à 16:35, Mark Morlino <1888...@bugs.launchpad.net> a écrit : > Thanks for taking the time to report this bug and helping to make Ubuntu > better. We appreciate the difficulties you are facing, but this appears > to be a "regular" (non-security) bug. I have unmarked it as a security > issue since this bug does not show evidence of allowing attackers to > cross privilege boundaries nor directly cause loss of data/privacy. > Please feel free to report any other bugs you may find. > > ** Information type changed from Private Security to Public > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1888963 > > Title: > My touchpad is not working at all on ubuntu > > Status in linux package in Ubuntu: > New > > Bug description: > I have followed this tutorial > https://wiki.ubuntu.com/DebuggingTouchpadDetection#In_case_your_Touchpad_doesn.27t_work_at_all_.28No_response_from_the_Touchpad.29 > But no touchpad device appears when I execute at terminal cat > /proc/bus/input/devices > > My laptop is a Lenovo ThinkBook 15-IIL (20SM000GFR) > > Thank you for your help > > ProblemType: Bug > DistroRelease: Ubuntu 20.04 > Package: linux-image-5.4.0-42-generic 5.4.0-42.46 > ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 > Uname: Linux 5.4.0-42-generic x86_64 > ApportVersion: 2.20.11-0ubuntu27.4 > Architecture: amd64 > AudioDevicesInUse: >USERPID ACCESS COMMAND >/dev/snd/controlC0: marieange 1416 F pulseaudio >/dev/snd/pcmC0D0p: marieange 1416 F...m pulseaudio > CasperMD5CheckResult: skip > CurrentDesktop: ubuntu:GNOME > Date: Sat Jul 25 22:54:21 2020 > InstallationDate: Installed on 2020-07-25 (0 days ago) > InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 > (20200423) > MachineType: LENOVO 20SM > ProcEnviron: >TERM=xterm-256color >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=fr_FR.UTF-8 >SHELL=/bin/bash > ProcFB: 0 i915drmfb > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic > root=UUID=789e8893-9607-4401-b5ee-6c4bc8aaad64 ro i8042.reset i8042.nomux > i8042.nopnp i8042.noloop quiet splash psmouse.proto=bare vt.handoff=7 > RelatedPackageVersions: >linux-restricted-modules-5.4.0-42-generic N/A >linux-backports-modules-5.4.0-42-generic N/A >linux-firmware1.187.2 > SourcePackage: linux > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 04/15/2020 > dmi.bios.vendor: LENOVO > dmi.bios.version: DJCN17WW > dmi.board.name: LVAC/LVAD > dmi.board.vendor: LENOVO > dmi.board.version: SDK0J40697 WIN > dmi.chassis.type: 10 > dmi.chassis.vendor: LENOVO > dmi.chassis.version: Lenovo ThinkBook 15-IIL > dmi.modalias: > dmi:bvnLENOVO:bvrDJCN17WW:bd04/15/2020:svnLENOVO:pn20SM:pvrLenovoThinkBook15-IIL:rvnLENOVO:rnLVAC/LVAD:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrLenovoThinkBook15-IIL: > dmi.product.family: Thinkbook 15-IIL > dmi.product.name: 20SM > dmi.product.sku: LENOVO_MT_20SM_BU_idea_FM_Thinkbook 15-IIL > dmi.product.version: Lenovo ThinkBook 15-IIL > dmi.sys.vendor: LENOVO > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888963/+subscriptions > -- 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/1888963 Title: My touchpad is not working at all on ubuntu Status in linux package in Ubuntu: Confirmed Bug description: I have followed this tutorial https://wiki.ubuntu.com/DebuggingTouchpadDetection#In_case_your_Touchpad_doesn.27t_work_at_all_.28No_response_from_the_Touchpad.29 But no touchpad device appears when I execute at terminal cat /proc/bus/input/devices My laptop is a Lenovo ThinkBook 15-IIL (20SM000GFR) Thank you for your help ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-42-generic 5.4.0-42.46 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: marieange 1416 F pulseaudio /dev/snd/pcmC0D0p: marieange 1416 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jul 25 22:54:21 2020 InstallationDate: Installed on 2020-07-25 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20SM ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine:
[Kernel-packages] [Bug 1850439] Re: No sound on ASUS UX534FT
Please test the kernel without any workaround: https://people.canonical.com/~khfeng/lp1850439-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/1850439 Title: No sound on ASUS UX534FT Status in linux package in Ubuntu: Confirmed Bug description: Hi, after instal Ubuntu in dual boot alongside Windows 10, I've realised there is no sound coming out of mine new ASUS Zenbook 15 UX534FT- AA024R in Ubuntu. In Windows there is no problem. Found this topic https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810214 which had the same problem with driver for Realtek ALC294 which is also mine sound card. But even with this fix it is not working on UX534FT. Can you please add fix also for this newer model? Description: Ubuntu 18.04.3 LTS Release: 18.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.0.0-32-generic 5.0.0-32.34~18.04.2 ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 29 15:11:25 2019 InstallationDate: Installed on 2019-10-29 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) SourcePackage: linux-signed-hwe UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850439/+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 1888963] 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/1888963 Title: My touchpad is not working at all on ubuntu Status in linux package in Ubuntu: Confirmed Bug description: I have followed this tutorial https://wiki.ubuntu.com/DebuggingTouchpadDetection#In_case_your_Touchpad_doesn.27t_work_at_all_.28No_response_from_the_Touchpad.29 But no touchpad device appears when I execute at terminal cat /proc/bus/input/devices My laptop is a Lenovo ThinkBook 15-IIL (20SM000GFR) Thank you for your help ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-42-generic 5.4.0-42.46 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: marieange 1416 F pulseaudio /dev/snd/pcmC0D0p: marieange 1416 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jul 25 22:54:21 2020 InstallationDate: Installed on 2020-07-25 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20SM ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=789e8893-9607-4401-b5ee-6c4bc8aaad64 ro i8042.reset i8042.nomux i8042.nopnp i8042.noloop quiet splash psmouse.proto=bare vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2020 dmi.bios.vendor: LENOVO dmi.bios.version: DJCN17WW dmi.board.name: LVAC/LVAD dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ThinkBook 15-IIL dmi.modalias: dmi:bvnLENOVO:bvrDJCN17WW:bd04/15/2020:svnLENOVO:pn20SM:pvrLenovoThinkBook15-IIL:rvnLENOVO:rnLVAC/LVAD:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrLenovoThinkBook15-IIL: dmi.product.family: Thinkbook 15-IIL dmi.product.name: 20SM dmi.product.sku: LENOVO_MT_20SM_BU_idea_FM_Thinkbook 15-IIL dmi.product.version: Lenovo ThinkBook 15-IIL dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888963/+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 1888995] 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/1888995 Title: Wifi Driver Not Working Status in linux package in Ubuntu: Confirmed Bug description: Wifi Driver Notworking for my machine ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-42-generic 5.4.0-42.46 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: karunakaran 1880 F pulseaudio /dev/snd/controlC0: karunakaran 1880 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jul 26 18:42:09 2020 InstallationDate: Installed on 2020-07-24 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. Latitude E5440 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=9883cc48-63b9-4f51-8573-fc4713863296 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/06/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: A14 dmi.board.name: 03CHJ4 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA14:bd01/06/2016:svnDellInc.:pnLatitudeE5440:pvr00:rvnDellInc.:rn03CHJ4:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5440 dmi.product.sku: 05DE dmi.product.version: 00 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888995/+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 1888963] Re: My touchpad is not working at all on ubuntu
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- 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/1888963 Title: My touchpad is not working at all on ubuntu Status in linux package in Ubuntu: New Bug description: I have followed this tutorial https://wiki.ubuntu.com/DebuggingTouchpadDetection#In_case_your_Touchpad_doesn.27t_work_at_all_.28No_response_from_the_Touchpad.29 But no touchpad device appears when I execute at terminal cat /proc/bus/input/devices My laptop is a Lenovo ThinkBook 15-IIL (20SM000GFR) Thank you for your help ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-42-generic 5.4.0-42.46 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: marieange 1416 F pulseaudio /dev/snd/pcmC0D0p: marieange 1416 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jul 25 22:54:21 2020 InstallationDate: Installed on 2020-07-25 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20SM ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=789e8893-9607-4401-b5ee-6c4bc8aaad64 ro i8042.reset i8042.nomux i8042.nopnp i8042.noloop quiet splash psmouse.proto=bare vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2020 dmi.bios.vendor: LENOVO dmi.bios.version: DJCN17WW dmi.board.name: LVAC/LVAD dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ThinkBook 15-IIL dmi.modalias: dmi:bvnLENOVO:bvrDJCN17WW:bd04/15/2020:svnLENOVO:pn20SM:pvrLenovoThinkBook15-IIL:rvnLENOVO:rnLVAC/LVAD:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrLenovoThinkBook15-IIL: dmi.product.family: Thinkbook 15-IIL dmi.product.name: 20SM dmi.product.sku: LENOVO_MT_20SM_BU_idea_FM_Thinkbook 15-IIL dmi.product.version: Lenovo ThinkBook 15-IIL dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888963/+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 1888995] Re: Wifi Driver Not Working
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- 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/1888995 Title: Wifi Driver Not Working Status in linux package in Ubuntu: New Bug description: Wifi Driver Notworking for my machine ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-42-generic 5.4.0-42.46 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: karunakaran 1880 F pulseaudio /dev/snd/controlC0: karunakaran 1880 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jul 26 18:42:09 2020 InstallationDate: Installed on 2020-07-24 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. Latitude E5440 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=9883cc48-63b9-4f51-8573-fc4713863296 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/06/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: A14 dmi.board.name: 03CHJ4 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA14:bd01/06/2016:svnDellInc.:pnLatitudeE5440:pvr00:rvnDellInc.:rn03CHJ4:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5440 dmi.product.sku: 05DE dmi.product.version: 00 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888995/+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 1848831]
Hi, I'm having the same issue with this card (integrated into the motherboard) and I dug a bit inside the code. The code in (iwlmvm/fw.c) waits for an alive notification and then times out. iwl_mvm_load_ucode_wait_alive will runn iwl_wait_notification which times out with err -110. I don't know exactly how it works but iwlmvm starts the firmware (which does not error) and then waits for the firmware to ping that it's alive so it can continue with the setup. This alive ping is not being received hence it times out. -- 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/1848831 Title: Intel WiFi AX200 [8086:08b1] subsystem [8086:4070] firmware loading error resulting in no wifi Status in Gaming Edition: In Progress Status in linux-firmware package in Ubuntu: Confirmed Bug description: Ubuntu 19.10 - stock kernel - Intel AX200 PCI card in a desktop PC uname -a Linux nahuatl 5.3.0-18-generic #19-Ubuntu SMP Tue Oct 8 20:14:06 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux The card is detected OK as dmesg shows, however the card's firmware fails immediately after loading (see dmesg output below) and wifi doesn't work at all. Big disappointment since the AX200 chip was supposed to be supported on 19.10. Ubuntu includes two ax200 firmware versions, version 48 loads by default in my system (and fails). I tried version 46 (by renaming the version 48 file) and it failed in the exact same manner $ ls /lib/firmware/iwlwifi-cc-* /lib/firmware/iwlwifi-cc-a0-46.ucode /lib/firmware/iwlwifi-cc-a0-48.ucode The card's Bluetooth functionality is also detected and it works fine. It's just the wifi FW loading what seems broken in ubuntu's 5.3 kernel. $ rfkill list 0: hci0: Bluetooth Soft blocked: yes Hard blocked: no ~$ dmesg | grep iwl [ 12.312443] iwlwifi :01:00.0: enabling device ( -> 0002) [ 12.321098] iwlwifi :01:00.0: TLV_FW_FSEQ_VERSION: FSEQ Version: 43.2.23.17 [ 12.321101] iwlwifi :01:00.0: Found debug destination: EXTERNAL_DRAM [ 12.321102] iwlwifi :01:00.0: Found debug configuration: 0 [ 12.321309] iwlwifi :01:00.0: loaded firmware version 48.4fa0041f.0 op_mode iwlmvm [ 12.390389] iwlwifi :01:00.0: Detected Intel(R) Wi-Fi 6 AX200 160MHz, REV=0x340 [ 12.400654] iwlwifi :01:00.0: Applying debug destination EXTERNAL_DRAM [ 12.400893] iwlwifi :01:00.0: Allocated 0x0040 bytes for firmware monitor. [ 13.414781] iwlwifi :01:00.0: Collecting data: trigger 15 fired. [ 13.414908] iwlwifi :01:00.0: Start IWL Error Log Dump: [ 13.414910] iwlwifi :01:00.0: Status: 0x, count: 6 [ 13.414911] iwlwifi :01:00.0: Loaded firmware version: 48.4fa0041f.0 [ 13.414912] iwlwifi :01:00.0: 0x0071 | NMI_INTERRUPT_UMAC_FATAL [ 13.414913] iwlwifi :01:00.0: 0x002022F0 | trm_hw_status0 [ 13.414913] iwlwifi :01:00.0: 0x | trm_hw_status1 [ 13.414914] iwlwifi :01:00.0: 0x004F8E3C | branchlink2 [ 13.414915] iwlwifi :01:00.0: 0x004E4FF4 | interruptlink1 [ 13.414915] iwlwifi :01:00.0: 0x004E4FF4 | interruptlink2 [ 13.414916] iwlwifi :01:00.0: 0x004F3DB0 | data1 [ 13.414917] iwlwifi :01:00.0: 0x1000 | data2 [ 13.414917] iwlwifi :01:00.0: 0xF000 | data3 [ 13.414918] iwlwifi :01:00.0: 0x | beacon time [ 13.414919] iwlwifi :01:00.0: 0x795F | tsf low [ 13.414919] iwlwifi :01:00.0: 0x | tsf hi [ 13.414920] iwlwifi :01:00.0: 0x | time gp1 [ 13.414921] iwlwifi :01:00.0: 0xDFD5 | time gp2 [ 13.414921] iwlwifi :01:00.0: 0x0001 | uCode revision type [ 13.414922] iwlwifi :01:00.0: 0x0030 | uCode version major [ 13.414923] iwlwifi :01:00.0: 0x4FA0041F | uCode version minor [ 13.414923] iwlwifi :01:00.0: 0x0340 | hw version [ 13.414924] iwlwifi :01:00.0: 0x18C89000 | board version [ 13.414925] iwlwifi :01:00.0: 0x8002FF03 | hcmd [ 13.414925] iwlwifi :01:00.0: 0x0002 | isr0 [ 13.414926] iwlwifi :01:00.0: 0x | isr1 [ 13.414926] iwlwifi :01:00.0: 0x08F2 | isr2 [ 13.414927] iwlwifi :01:00.0: 0x00CC | isr3 [ 13.414928] iwlwifi :01:00.0: 0x | isr4 [ 13.414928] iwlwifi :01:00.0: 0x | last cmd Id [ 13.414929] iwlwifi :01:00.0: 0x004F3DB0 | wait_event [ 13.414930] iwlwifi :01:00.0: 0x | l2p_control [ 13.414930] iwlwifi :01:00.0: 0x0020 | l2p_duration [ 13.414931] iwlwifi :01:00.0: 0x | l2p_mhvalid [ 13.414932] iwlwifi :01:00.0: 0x | l2p_addr_match [ 13.414932] iwlwifi :01:00.0: 0x0009 | lmpm_pmg_sel [ 13.414933] iwlwifi :01:00.0: 0x | timestamp [ 13.414934] iwlwifi :01:00.0:
[Kernel-packages] [Bug 1861610] Re: 'Elan touchpad' not detected on 'Lenovo ThinkBook 15 IIL'
Does not work on 5.4.0-42.46 focal (although I have ThinkBook 14-ILL). -- 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/1861610 Title: 'Elan touchpad' not detected on 'Lenovo ThinkBook 15 IIL' Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.6 package in Ubuntu: Fix Released Status in linux-oem-osp1 package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Released Status in linux-oem-5.6 source package in Bionic: Invalid Status in linux-oem-osp1 source package in Bionic: Fix Released Status in linux source package in Eoan: Fix Released Status in linux-oem-5.6 source package in Eoan: Invalid Status in linux-oem-osp1 source package in Eoan: Fix Released Status in linux source package in Focal: Fix Released Status in linux-oem-5.6 source package in Focal: Fix Released Status in linux-oem-osp1 source package in Focal: Invalid Bug description: [SRU Justification] [Impact] Touchpad function unavailable on some platforms with new ELAN touchpad HIDs. [Fix] https://lore.kernel.org/linux-input/000201d5a8bd$9fead3f0$dfc07bd0$@emc.com.tw/ required to match these currently unsupported IDs. [Test Case] 1. check if platform is affected, e.g. with ELAN0634: $ sudo acpidump | grep -C3 ELAN 2A060: 49 4E 54 31 70 0A 20 49 44 41 44 A4 84 53 42 46 INT1p.IDAD..SBF 2A070: 53 53 42 46 49 00 5B 82 42 0E 54 50 44 32 08 5F SSBFI.[.B.TPD2._ 2A080: 41 44 52 00 08 49 44 41 44 00 08 48 49 44 32 00 ADR..IDAD..HID2. 2A090: 08 5F 48 49 44 0D 45 4C 41 4E 30 36 33 34 00 08 ._HID.ELAN0634.. 2A0A0: 5F 43 49 44 0D 50 4E 50 30 43 35 30 00 08 5F 55 _CID.PNP0C50.._U 2A0B0: 49 44 01 14 4B 04 5F 44 53 4D 04 A0 3C 93 68 11 ID..K._DSM..<.h. 2A0C0: 13 0A 10 F7 F6 DF 3C 67 42 55 45 AD 05 B3 0A 3D ..https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861610/+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 1889223] [NEW] vc4-kms-v3d boot failure focal armhf preinstalled server
Public bug reported: Booting 20.04 armhf preinstalled-server on Pi3b+ with vc4-kms-v3d selected [1] causes boot failure with [2] output on UART. Further system info in [3] Side note: Booting with the same usercfg.txt but with the 18.04 vc4-kms- v3d.dtbo file "works": the boot is normal without the errors shown in [2]. [1] ubuntu@ubuntu:~$ cat /boot/firmware/usercfg.txt # Place "config.txt" changes (dtparam, dtoverlay, disable_overscan, etc.) in # this file. Please refer to the README file for a description of the various # configuration files on the boot partition. dtoverlay=vc4-kms-v3d [2] Starting kernel ... [0.039873] cma: CMA area linux,cma could not be activated [0.043189] DMA: failed to allocate 1024 KiB pool for atomic coherent allocation [0.308022] kobject_add_internal failed for 3e513000.framebuffer with -EEXIST, don't try to register things with the s. [1.141370] kvm [1]: Error, CPU 0 not supported! [1.235565] raspberrypi-exp-gpio soc:firmware:expgpio: Failed to get GPIO 0 config (-12 80) [1.236723] raspberrypi-exp-gpio soc:firmware:expgpio: Failed to get GPIO 1 config (-12 81) [1.237882] raspberrypi-exp-gpio soc:firmware:expgpio: Failed to get GPIO 2 config (-12 82) [1.239014] raspberrypi-exp-gpio soc:firmware:expgpio: Failed to get GPIO 3 config (-12 83) [1.240139] raspberrypi-exp-gpio soc:firmware:expgpio: Failed to get GPIO 4 config (-12 84) [1.241263] raspberrypi-exp-gpio soc:firmware:expgpio: Failed to get GPIO 5 config (-12 85) [1.242412] raspberrypi-exp-gpio soc:firmware:expgpio: Failed to get GPIO 6 config (-12 86) [1.243526] raspberrypi-exp-gpio soc:firmware:expgpio: Failed to get GPIO 7 config (-12 87) [1.831440] spi-bcm2835 3f204000.spi: could not get clk: -517 [1.849256] raspberrypi-exp-gpio soc:firmware:expgpio: Failed to get GPIO 2 config (-12 82) [1.850523] raspberrypi-exp-gpio soc:firmware:expgpio: Failed to get GPIO 2 config (-12 82) [1.852205] bcm2835_vchiq 3f00b840.mailbox: could not allocate DMA memory [2.369653] spi-bcm2835 3f204000.spi: cannot prepare fill_tx_desc - not using DMA mode [2.412710] sdhost: failed to allocate log buf ext4 [3] ubuntu@ubuntu:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 20.04.1 LTS Release:20.04 Codename: focal ubuntu@ubuntu:~$ uname -a Linux ubuntu 5.4.0-1015-raspi #15-Ubuntu SMP Fri Jul 10 05:37:25 UTC 2020 armv7l armv7l armv7l GNU/Linux Initial part of lshw: ubuntu description: ARMv7 Processor rev 4 (v7l) product: Raspberry Pi 3 Model B Plus Rev 1.3 serial: 92021ecd width: 32 bits capabilities: smp ** Affects: linux-raspi (Ubuntu) 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/1889223 Title: vc4-kms-v3d boot failure focal armhf preinstalled server Status in linux-raspi package in Ubuntu: New Bug description: Booting 20.04 armhf preinstalled-server on Pi3b+ with vc4-kms-v3d selected [1] causes boot failure with [2] output on UART. Further system info in [3] Side note: Booting with the same usercfg.txt but with the 18.04 vc4 -kms-v3d.dtbo file "works": the boot is normal without the errors shown in [2]. [1] ubuntu@ubuntu:~$ cat /boot/firmware/usercfg.txt # Place "config.txt" changes (dtparam, dtoverlay, disable_overscan, etc.) in # this file. Please refer to the README file for a description of the various # configuration files on the boot partition. dtoverlay=vc4-kms-v3d [2] Starting kernel ... [0.039873] cma: CMA area linux,cma could not be activated [0.043189] DMA: failed to allocate 1024 KiB pool for atomic coherent allocation [0.308022] kobject_add_internal failed for 3e513000.framebuffer with -EEXIST, don't try to register things with the s. [1.141370] kvm [1]: Error, CPU 0 not supported! [1.235565] raspberrypi-exp-gpio soc:firmware:expgpio: Failed to get GPIO 0 config (-12 80) [1.236723] raspberrypi-exp-gpio soc:firmware:expgpio: Failed to get GPIO 1 config (-12 81) [1.237882] raspberrypi-exp-gpio soc:firmware:expgpio: Failed to get GPIO 2 config (-12 82) [1.239014] raspberrypi-exp-gpio soc:firmware:expgpio: Failed to get GPIO 3 config (-12 83) [1.240139] raspberrypi-exp-gpio soc:firmware:expgpio: Failed to get GPIO 4 config (-12 84) [1.241263] raspberrypi-exp-gpio soc:firmware:expgpio: Failed to get GPIO 5 config (-12 85) [1.242412] raspberrypi-exp-gpio soc:firmware:expgpio: Failed to get GPIO 6 config (-12 86) [1.243526] raspberrypi-exp-gpio soc:firmware:expgpio: Failed to get GPIO 7 config (-12 87) [1.831440] spi-bcm2835 3f204000.spi: could not get clk: -517 [1.849256] raspberrypi-exp-gpio soc:firmware:expgpio: Failed to get GPIO
[Kernel-packages] [Bug 1888090] Re: Frequent Kernel panic in 5.4.0-40 but not 5.4.0-29 on Gemini Lake cpu and r8169r
I've been testing it for the past 3 days and no crashes. -- 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/1888090 Title: Frequent Kernel panic in 5.4.0-40 but not 5.4.0-29 on Gemini Lake cpu and r8169r Status in linux package in Ubuntu: Incomplete Bug description: Crashes occur more frequently with heavy network traffic and can happen every 5 minutes to 24+ hours. Stacktrace usually involves TCP. Same behavior on two new motherboards (Asrock J4105M and Asrock J5005-ITX) with different RAM type and brand. All other peripherals removed and changed PSU (still crashed). Enabled kdump and got a dozen dumps, will attach some. Went from 5.4.0-40 to 5.4.0-29 and no crashes at all. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: akom 2403 F pulseaudio CasperMD5CheckResult: pass Date: Sat Jul 18 17:28:40 2020 InstallationDate: Installed on 2020-07-04 (14 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0781:5571 SanDisk Corp. Cruzer Fit 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/7p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/9p, 480M |__ Port 2: Dev 2, If 0, Class=Mass Storage, Driver=usb-storage, 480M MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: TERM=screen PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=2ef70f32-e7d2-4fed-992a-6a236076a72f ro crashkernel=512M-:512M PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/06/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.40 dmi.board.name: J5005-ITX dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.40:bd08/06/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnJ5005-ITX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888090/+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 1861284] Re: Build and ship a signed wireguard.ko
** 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) => Andy Whitcroft (apw) -- 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/1861284 Title: Build and ship a signed wireguard.ko Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: In Progress Status in linux source package in Bionic: Fix Released Status in linux source package in Eoan: Fix Released Bug description: .. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861284/+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 1875199] Re: [NUC8CCHK][HDA-Intel - HDA Intel PCH, playback] No sound at all
@Kai-Heng, Apologies for the delay in my reply... I tested to the best of my ability using the Audacity audio application in both Linux Mint 19.3 (where audio output works) and Ubuntu 20.04 (where audio output does not work) and it appears that audio input via microphones is not supported. I tested with a standard microphone as well as with a combination headset with an integrated microphone. Based on the block diagram on page 35 (printed page 27) of the technical specifications for the unit --> https://www.intel.com/content/dam/support/us/en/documents/mini- pcs/NUC8CCH_TechProdSpec.pdf it appears that the audio port is only a line out jack. I attempted to use the "hdajackretask" application you mention, however when attempting to do so I receive an error message 'Device or resource busy' when I attempt to apply the override. I have attached a screenshot of the specific error. Please let me know if I can provide any additional information, and thank you as always for the help! ** Attachment added: "hdajackretask_error.png" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875199/+attachment/5396553/+files/hdajackretask_error.png -- 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/1875199 Title: [NUC8CCHK][HDA-Intel - HDA Intel PCH, playback] No sound at all Status in linux package in Ubuntu: Incomplete Bug description: No sound output. Only a 'Dummy' audio output device is listed in the Gnome Sound application. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rboerner 1205 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Apr 26 12:12:49 2020 InstallationDate: Installed on 2020-04-25 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rboerner 1205 F pulseaudio Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: No sound at all Title: [HDA-Intel - HDA Intel PCH, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/25/2020 dmi.bios.vendor: Intel Corp. dmi.bios.version: CHAPLCEL.0048.2020.0225.1640 dmi.board.name: NUC8CCHB dmi.board.vendor: Intel Corporation dmi.board.version: K44767-502 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrCHAPLCEL.0048.2020.0225.1640:bd02/25/2020:svnIntel(R)ClientSystems:pnNUC8CCHK:pvrK44798-502:rvnIntelCorporation:rnNUC8CCHB:rvrK44767-502:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: CH dmi.product.name: NUC8CCHK dmi.product.sku: BKNUC8CCHKR dmi.product.version: K44798-502 dmi.sys.vendor: Intel(R) Client Systems --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rboerner 1215 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-25 (6 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Intel(R) Client Systems NUC8CCHK Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-generic root=UUID=afbb0f64-e729-46a8-82e4-a060e9e729c4 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 RelatedPackageVersions: linux-restricted-modules-5.4.0-28-generic N/A linux-backports-modules-5.4.0-28-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-28-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: 02/25/2020 dmi.bios.vendor: Intel Corp. dmi.bios.version: CHAPLCEL.0048.2020.0225.1640 dmi.board.name: NUC8CCHB dmi.board.vendor: Intel Corporation dmi.board.version: K44767-502 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias:
[Kernel-packages] [Bug 1861610] Re: 'Elan touchpad' not detected on 'Lenovo ThinkBook 15 IIL'
I also face the same issue on Ubuntu 20.04. Will this fix available on Ubuntu 20.04 -- 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/1861610 Title: 'Elan touchpad' not detected on 'Lenovo ThinkBook 15 IIL' Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.6 package in Ubuntu: Fix Released Status in linux-oem-osp1 package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Released Status in linux-oem-5.6 source package in Bionic: Invalid Status in linux-oem-osp1 source package in Bionic: Fix Released Status in linux source package in Eoan: Fix Released Status in linux-oem-5.6 source package in Eoan: Invalid Status in linux-oem-osp1 source package in Eoan: Fix Released Status in linux source package in Focal: Fix Released Status in linux-oem-5.6 source package in Focal: Fix Released Status in linux-oem-osp1 source package in Focal: Invalid Bug description: [SRU Justification] [Impact] Touchpad function unavailable on some platforms with new ELAN touchpad HIDs. [Fix] https://lore.kernel.org/linux-input/000201d5a8bd$9fead3f0$dfc07bd0$@emc.com.tw/ required to match these currently unsupported IDs. [Test Case] 1. check if platform is affected, e.g. with ELAN0634: $ sudo acpidump | grep -C3 ELAN 2A060: 49 4E 54 31 70 0A 20 49 44 41 44 A4 84 53 42 46 INT1p.IDAD..SBF 2A070: 53 53 42 46 49 00 5B 82 42 0E 54 50 44 32 08 5F SSBFI.[.B.TPD2._ 2A080: 41 44 52 00 08 49 44 41 44 00 08 48 49 44 32 00 ADR..IDAD..HID2. 2A090: 08 5F 48 49 44 0D 45 4C 41 4E 30 36 33 34 00 08 ._HID.ELAN0634.. 2A0A0: 5F 43 49 44 0D 50 4E 50 30 43 35 30 00 08 5F 55 _CID.PNP0C50.._U 2A0B0: 49 44 01 14 4B 04 5F 44 53 4D 04 A0 3C 93 68 11 ID..K._DSM..<.h. 2A0C0: 13 0A 10 F7 F6 DF 3C 67 42 55 45 AD 05 B3 0A 3D ..https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861610/+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 1889217] [NEW] Make digital mic on the AMD renoir machines work under gnome desktop
Public bug reported: This is for tracking purpose. ** Affects: alsa-lib (Ubuntu) Importance: High Status: New ** Affects: alsa-ucm-conf (Ubuntu) Importance: High Status: New ** Affects: pulseaudio (Ubuntu) Importance: High Assignee: Hui Wang (hui.wang) Status: New ** Affects: alsa-lib (Ubuntu Focal) Importance: High Status: New ** Affects: alsa-ucm-conf (Ubuntu Focal) Importance: High Status: New ** Affects: pulseaudio (Ubuntu Focal) Importance: High Status: New ** Affects: alsa-lib (Ubuntu Groovy) Importance: High Status: New ** Affects: alsa-ucm-conf (Ubuntu Groovy) Importance: High Status: New ** Affects: pulseaudio (Ubuntu Groovy) Importance: High Assignee: Hui Wang (hui.wang) Status: New ** Also affects: alsa-lib (Ubuntu) Importance: Undecided Status: New ** Also affects: alsa-ucm-conf (Ubuntu) Importance: Undecided Status: New ** Changed in: alsa-lib (Ubuntu) Importance: Undecided => High ** Changed in: alsa-ucm-conf (Ubuntu) Importance: Undecided => High ** Changed in: pulseaudio (Ubuntu) Importance: Undecided => High ** Also affects: alsa-lib (Ubuntu Groovy) Importance: High Status: New ** Also affects: pulseaudio (Ubuntu Groovy) Importance: High Assignee: Hui Wang (hui.wang) Status: New ** Also affects: alsa-ucm-conf (Ubuntu Groovy) Importance: High Status: New ** Also affects: alsa-lib (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: pulseaudio (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: alsa-ucm-conf (Ubuntu Focal) Importance: Undecided Status: New ** Summary changed: - Make digital mic on the AMD renoir machines work under gnome environment + Make digital mic on the AMD renoir machines work under gnome desktop ** Changed in: alsa-lib (Ubuntu Focal) Importance: Undecided => High ** Changed in: alsa-ucm-conf (Ubuntu Focal) Importance: Undecided => High ** Changed in: pulseaudio (Ubuntu Focal) Importance: Undecided => High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1889217 Title: Make digital mic on the AMD renoir machines work under gnome desktop Status in alsa-lib package in Ubuntu: New Status in alsa-ucm-conf package in Ubuntu: New Status in pulseaudio package in Ubuntu: New Status in alsa-lib source package in Focal: New Status in alsa-ucm-conf source package in Focal: New Status in pulseaudio source package in Focal: New Status in alsa-lib source package in Groovy: New Status in alsa-ucm-conf source package in Groovy: New Status in pulseaudio source package in Groovy: New Bug description: This is for tracking purpose. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1889217/+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 1857938] Re: Extreme touchpad lag on HP Envy X360 13-ag0xxx on startup/awakening from suspended state
Can you please attach `dmesg` when the kernel parameter was added? Thanks! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1857938 Title: Extreme touchpad lag on HP Envy X360 13-ag0xxx on startup/awakening from suspended state Status in linux package in Ubuntu: Incomplete Bug description: I am using Ubuntu 20.04 with kernel 5.4.4 on my HP Envy X360 13-ag0xxx. The touchpad works fine under most conditions, however whenever the system wakes up from a suspended state (on startup) in the first 15-20 seconds the touchpad is quite laggy (everything else is smooth) and very hard to use. I am using Libinput 1.14.1. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: user 2340 F pulseaudio /dev/snd/controlC0: user 2340 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-25 (83 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: HP HP ENVY x360 Convertible 13-ag0xxx Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=5cd8ac1d-85c5-4ed5-84c6-fb958f99ee4c ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 Tags: focal Uname: Linux 5.4.0-40-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: 05/13/2019 dmi.bios.vendor: AMI dmi.bios.version: F.42 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8496 dmi.board.vendor: HP dmi.board.version: 92.46 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.42:bd05/13/2019:svnHP:pnHPENVYx360Convertible13-ag0xxx:pvr:rvnHP:rn8496:rvr92.46:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Envy dmi.product.name: HP ENVY x360 Convertible 13-ag0xxx dmi.product.sku: 4JV79EA#ABU dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1857938/+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 1878194] Re: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa
*** This bug is a duplicate of bug 1871794 *** https://bugs.launchpad.net/bugs/1871794 It probably is a kernel driver or firmware's regression, could you run the 19.10's kernel + 19.10's firmware under 20.04 to test? -- 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/1878194 Title: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: After updating the release from Ubuntu 19.10 to 20.04, the bluetooth headset doesn't work anymore when HSP/HFP profile is selected. With Ubuntu 19.10 the headset was working, there was audio and the mic was perfect for video conferencing. [Steps to reproduce] 1. Connect headset (used blueman to setup and connect) 1.1. When connected the system automatically selects A2DP profile 2. Start playing audio (browser or other) 3. Change profile to HSP/HFP with pavucontrol (or blueman) 4. The audio disappears and microphone is not working (no input) 5. Optionally switch back to A2DP and the audio comes back [Expected] When switching to HSP/HFP the audio should keep playing and the microphone should start working [Notes] I tried with pavucontrol to switch between profiles while playing audio from a browser. As side note there's a led in the headset that still blinks when switching profile. I tried deleting the pulse folder under user's profile .config without success, also reinstalled packages and did a `sudo alsa force-reload` and rebooting several times. Note: not sure this is a duplicate of [Bug #1576559], it looks quite different since the profile changes but the headset stops working. [System info] Ubuntu: 20.04 - Linux 5.4.0-29-generic x86_64 pulseaudio: 1:13.99.1-1ubuntu3 bluez: 5.53-0ubuntu3 Headset: Sennheiser HD 4.50 BTNC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1878194/+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 1886920] Re: Battery drain during sleep. System suspended before kernel suspends all tasks. Lenovo ThinkPad T460
[ 33.395006] Bluetooth: hci0: command 0x0c03 tx timeout [ 34.316133] usb 1-7: USB disconnect, device number 2 [ 34.316302] Bluetooth: hci0: HCI reset during shutdown failed Can you please try blacklisting "btusb" instead of the custom script? -- 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/1886920 Title: Battery drain during sleep. System suspended before kernel suspends all tasks. Lenovo ThinkPad T460 Status in linux package in Ubuntu: Confirmed Bug description: The same as https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825636. kaihengfeng closed that one "Because there's no response from the original bug reporter." and asked to file a report for all devices affected, so here I am, duplicating the report. On Ubuntu MATE 18.04, as well as after the update to 20.04, the battery drains about 1,25% per hour of sleep (if I just close the lid). $ cat /sys/power/mem_sleep s2idle [deep] tlp was initially installed on my machine. However, this behaviour also occurs if I $ sudo apt purge tlp acpi-call-dkms && sudo reboot now also, it occurs when booting from a freshly made MATE 20.04 live usb stick, so TLP shouldn't be the culprit. All the log files look in all relevant aspects similar to what was reported in the old report. I'm happy to provide log files from my machine, if any are necessary. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: richard1511 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: MATE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2018-07-12 (735 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b52c Chicony Electronics Co., Ltd Integrated Camera 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 10: Dev 3, If 0, Class=Video, Driver=uvcvideo, 480M |__ Port 10: Dev 3, If 1, Class=Video, Driver=uvcvideo, 480M MachineType: LENOVO 20FMS03600 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic root=/dev/mapper/ubuntu--mate--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 Tags: focal Uname: Linux 5.4.0-40-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-05-22 (55 days ago) UserGroups: adm cdrom dialout dip docker lpadmin plugdev sambashare sudo tty uucp _MarkForUpload: True dmi.bios.date: 09/21/2018 dmi.bios.vendor: LENOVO dmi.bios.version: R06ET64W (1.38 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FMS03600 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR06ET64W(1.38):bd09/21/2018:svnLENOVO:pn20FMS03600:pvrThinkPadT460:rvnLENOVO:rn20FMS03600:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460 dmi.product.name: 20FMS03600 dmi.product.sku: LENOVO_MT_20FM_BU_Think_FM_ThinkPad T460 dmi.product.version: ThinkPad T460 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886920/+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 1886920] Re: Battery drain during sleep. System suspended before kernel suspends all tasks. Lenovo ThinkPad T460
It is not possible to disable the Intel ME from the BIOS set up. I attached the result of running $ dmesg > dmesg.log after booting I rarely use bluetooth, so I keep it disabled. To automatically disable it after boot, I use rfkill in the rc.local file: ``` $ cat /etc/rc.local #!/bin/bash sleep 10 rfkill block bluetooth exit 0 ``` that might explain what you found about it not working right? After clicking "Turn Bluetooth On" in the blueman-applet, I can connect to bluetooth speakers and play music. ** Attachment added: "output of dmesg after booting" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886920/+attachment/5396547/+files/dmesg.log -- 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/1886920 Title: Battery drain during sleep. System suspended before kernel suspends all tasks. Lenovo ThinkPad T460 Status in linux package in Ubuntu: Confirmed Bug description: The same as https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825636. kaihengfeng closed that one "Because there's no response from the original bug reporter." and asked to file a report for all devices affected, so here I am, duplicating the report. On Ubuntu MATE 18.04, as well as after the update to 20.04, the battery drains about 1,25% per hour of sleep (if I just close the lid). $ cat /sys/power/mem_sleep s2idle [deep] tlp was initially installed on my machine. However, this behaviour also occurs if I $ sudo apt purge tlp acpi-call-dkms && sudo reboot now also, it occurs when booting from a freshly made MATE 20.04 live usb stick, so TLP shouldn't be the culprit. All the log files look in all relevant aspects similar to what was reported in the old report. I'm happy to provide log files from my machine, if any are necessary. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: richard1511 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: MATE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2018-07-12 (735 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b52c Chicony Electronics Co., Ltd Integrated Camera 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 10: Dev 3, If 0, Class=Video, Driver=uvcvideo, 480M |__ Port 10: Dev 3, If 1, Class=Video, Driver=uvcvideo, 480M MachineType: LENOVO 20FMS03600 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic root=/dev/mapper/ubuntu--mate--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 Tags: focal Uname: Linux 5.4.0-40-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-05-22 (55 days ago) UserGroups: adm cdrom dialout dip docker lpadmin plugdev sambashare sudo tty uucp _MarkForUpload: True dmi.bios.date: 09/21/2018 dmi.bios.vendor: LENOVO dmi.bios.version: R06ET64W (1.38 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FMS03600 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR06ET64W(1.38):bd09/21/2018:svnLENOVO:pn20FMS03600:pvrThinkPadT460:rvnLENOVO:rn20FMS03600:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460 dmi.product.name: 20FMS03600 dmi.product.sku: LENOVO_MT_20FM_BU_Think_FM_ThinkPad T460 dmi.product.version: ThinkPad T460 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886920/+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 1857938] Re: Extreme touchpad lag on HP Envy X360 13-ag0xxx on startup/awakening from suspended state
I have just tried that and the result is the same. One thing I would like to point out is that situation has slightly improved from 18 to 20, however when the laptop is suspended and I move the touchpad diagonally instead the cursor is jumpy and does not follow the finger correctly (this only happens when the system is resume from a suspended state, with a full reboot everything works fine). -- 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/1857938 Title: Extreme touchpad lag on HP Envy X360 13-ag0xxx on startup/awakening from suspended state Status in linux package in Ubuntu: Incomplete Bug description: I am using Ubuntu 20.04 with kernel 5.4.4 on my HP Envy X360 13-ag0xxx. The touchpad works fine under most conditions, however whenever the system wakes up from a suspended state (on startup) in the first 15-20 seconds the touchpad is quite laggy (everything else is smooth) and very hard to use. I am using Libinput 1.14.1. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: user 2340 F pulseaudio /dev/snd/controlC0: user 2340 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-25 (83 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: HP HP ENVY x360 Convertible 13-ag0xxx Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=5cd8ac1d-85c5-4ed5-84c6-fb958f99ee4c ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 Tags: focal Uname: Linux 5.4.0-40-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: 05/13/2019 dmi.bios.vendor: AMI dmi.bios.version: F.42 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8496 dmi.board.vendor: HP dmi.board.version: 92.46 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.42:bd05/13/2019:svnHP:pnHPENVYx360Convertible13-ag0xxx:pvr:rvnHP:rn8496:rvr92.46:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Envy dmi.product.name: HP ENVY x360 Convertible 13-ag0xxx dmi.product.sku: 4JV79EA#ABU dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1857938/+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 1888507] Comment bridged from LTC Bugzilla
--- Comment From i...@de.ibm.com 2020-07-28 08:05 EDT--- Interesting, this might explain why the relocation issue did not trigger for me. In the meantime I posted fixes to other bpf/samples issues: https://lore.kernel.org/bpf/20200728120059.132256-1-...@linux.ibm.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/1888507 Title: [UBUNTU 18.04] BPF programs fail on Ubuntu s390x Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: New Status in linux source package in Bionic: In Progress Bug description: We need to run BPF filters to analyse and monitor network traffic. The BPF filters are created by skydive (http://skydive.network). Currently skydive fails to install BPF filters on s390x (using Ubuntu 18.04 currently, soon moving to Ubuntu 20.04). Because of these failures, we decided to try the BPF samples that come with the kernel first. These samples also fail on s390x while they work fine on Intel. shense@boe-build:~/bionic/samples/bpf$ uname -a Linux boe-build 4.15.0-112-generic #113-Ubuntu SMP Thu Jul 9 23:40:36 UTC 2020 s390x s390x s390x GNU/Linux Example instructions: sudo apt install -y dpkg-dev clang llvm libelf-dev sudo apt-get source linux-image-unsigned-$(uname -r) cd linux-4.15.0/ make headers_install make samples/bpf/ Errors: shense@boe-build:~/bionic/samples/bpf$ sudo ./test_map_in_map [sudo] password for shense: invalid relo for insn[4].code 0x85 bpf_load_program() err=22 0: (bf) r7 = r1 1: (b7) r1 = 0 2: (63) *(u32 *)(r10 -32) = r1 3: (bf) r1 = r7 4: (85) call unknown#-1 BPF_CALL uses reserved fields 0: (bf) r7 = r1 1: (b7) r1 = 0 2: (63) *(u32 *)(r10 -32) = r1 3: (bf) r1 = r7 4: (85) call unknown#-1 BPF_CALL uses reserved fields shense@boe-build:~/bionic/samples/bpf$ sudo ./map_perf_test invalid relo for insn[22].code 0x85 bpf_load_program() err=22 0: (bf) r7 = r1 1: (18) r1 = 0x207265743a25646e 3: (7b) *(u64 *)(r10 -16) = r1 4: (18) r1 = 0x705f616c6c6f632e 6: (7b) *(u64 *)(r10 -24) = r1 7: (18) r1 = 0x5f6c72755f686d61 9: (7b) *(u64 *)(r10 -32) = r1 10: (18) r1 = 0x7420737472657373 12: (7b) *(u64 *)(r10 -40) = r1 13: (18) r1 = 0x4661696c65642061 15: (7b) *(u64 *)(r10 -48) = r1 16: (b7) r1 = 0 17: (73) *(u8 *)(r10 -8) = r1 18: (b7) r2 = 1 19: (7b) *(u64 *)(r10 -72) = r2 20: (63) *(u32 *)(r10 -76) = r1 21: (bf) r1 = r7 22: (85) call unknown#-1 BPF_CALL uses reserved fields 0: (bf) r7 = r1 1: (18) r1 = 0x207265743a25646e 3: (7b) *(u64 *)(r10 -16) = r1 4: (18) r1 = 0x705f616c6c6f632e 6: (7b) *(u64 *)(r10 -24) = r1 7: (18) r1 = 0x5f6c72755f686d61 9: (7b) *(u64 *)(r10 -32) = r1 10: (18) r1 = 0x7420737472657373 12: (7b) *(u64 *)(r10 -40) = r1 13: (18) r1 = 0x4661696c65642061 15: (7b) *(u64 *)(r10 -48) = r1 16: (b7) r1 = 0 17: (73) *(u8 *)(r10 -8) = r1 18: (b7) r2 = 1 19: (7b) *(u64 *)(r10 -72) = r2 20: (63) *(u32 *)(r10 -76) = r1 21: (bf) r1 = r7 22: (85) call unknown#-1 BPF_CALL uses reserved fields To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1888507/+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
Re: [Kernel-packages] [Bug 1889008] Re: Ubuntu 20.04.1 - EXT4-fs error ... last week I updated my system with core (kernel) updates
Thanks, I'll check it out. On Tue, Jul 28, 2020 at 2:15 PM Daniel van Vugt <1889...@bugs.launchpad.net> wrote: > OK, your disk is corrupt, which is also not a software bug sorry :( > > Reinstalling Ubuntu (and wiping the old disk contents) might fix it. If > reinstalling does not fix it then you may need to replace the SSD. > > ** Changed in: linux (Ubuntu) >Status: Incomplete => Invalid > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1889008 > > Title: > Ubuntu 20.04.1 - EXT4-fs error ... last week I updated my system with > core (kernel) updates > > Status in linux package in Ubuntu: > Invalid > > Bug description: > Ubuntu 20.04.1 > Kernel: 5.4.0-42-generic > > After updating my ubuntu last week my computer gets freeze after some > time and then showing this below error continuously... > > EXT-fs error (device nvme0n1p6): __extf4_find_entry:1531 inode #6439215: > comm main: reading > directory Iblock 0 > > ProblemType: Bug > DistroRelease: Ubuntu 20.04 > Package: linux-image-5.4.0-42-generic 5.4.0-42.46 > ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 > Uname: Linux 5.4.0-42-generic x86_64 > ApportVersion: 2.20.11-0ubuntu27.4 > Architecture: amd64 > AudioDevicesInUse: >USERPID ACCESS COMMAND >/dev/snd/controlC0: anonymous 2901 F pulseaudio > CasperMD5CheckResult: skip > CurrentDesktop: ubuntu:GNOME > Date: Sun Jul 26 23:21:34 2020 > Lsusb: >Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub >Bus 001 Device 003: ID 8087:0a2a Intel Corp. >Bus 001 Device 002: ID 0bda:5620 Realtek Semiconductor Corp. HP Wide > Vision HD Camera >Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > MachineType: HP HP ENVY Laptop 13-ad1xx > ProcFB: 0 i915drmfb > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic > root=UUID=443886f2-cf99-4eee-9116-c6c603c14437 ro quiet splash vt.handoff=7 > RelatedPackageVersions: >linux-restricted-modules-5.4.0-42-generic N/A >linux-backports-modules-5.4.0-42-generic N/A >linux-firmware1.187.2 > SourcePackage: linux > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 04/22/2019 > dmi.bios.vendor: Insyde > dmi.bios.version: F.28 > dmi.board.asset.tag: Type2 - Board Asset Tag > dmi.board.name: 83A7 > dmi.board.vendor: HP > dmi.board.version: KBC Version 39.35 > dmi.chassis.type: 10 > dmi.chassis.vendor: HP > dmi.chassis.version: Chassis Version > dmi.modalias: > dmi:bvnInsyde:bvrF.28:bd04/22/2019:svnHP:pnHPENVYLaptop13-ad1xx:pvrType1ProductConfigId:rvnHP:rn83A7:rvrKBCVersion39.35:cvnHP:ct10:cvrChassisVersion: > dmi.product.family: 103C_5335KV HP Envy > dmi.product.name: HP ENVY Laptop 13-ad1xx > dmi.product.sku: 2VL79PA#ACJ > dmi.product.version: Type1ProductConfigId > dmi.sys.vendor: HP > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1889008/+subscriptions > -- 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/1889008 Title: Ubuntu 20.04.1 - EXT4-fs error ... last week I updated my system with core (kernel) updates Status in linux package in Ubuntu: Invalid Bug description: Ubuntu 20.04.1 Kernel: 5.4.0-42-generic After updating my ubuntu last week my computer gets freeze after some time and then showing this below error continuously... EXT-fs error (device nvme0n1p6): __extf4_find_entry:1531 inode #6439215: comm main: reading directory Iblock 0 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-42-generic 5.4.0-42.46 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: anonymous 2901 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jul 26 23:21:34 2020 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 0bda:5620 Realtek Semiconductor Corp. HP Wide Vision HD Camera Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP ENVY Laptop 13-ad1xx ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=443886f2-cf99-4eee-9116-c6c603c14437 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/22/2019 dmi.bios.vendor: Insyde
[Kernel-packages] [Bug 1877958] Re: Do not treat unresolved test case in ftrace from ubuntu_kernel_selftests as failure
** Changed in: ubuntu-kernel-tests
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1877958
Title:
Do not treat unresolved test case in ftrace from
ubuntu_kernel_selftests as failure
Status in ubuntu-kernel-tests:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Xenial:
Fix Released
Status in linux source package in Bionic:
Fix Released
Status in linux source package in Eoan:
Fix Released
Status in linux source package in Focal:
Fix Released
Bug description:
== SRU Justification ==
There are some test cases in ftrace from ubuntu_kernel_selftests that
would need some kernel configs to be enabled or have some special HW
requirements:
* https://pad.lv/1869347 - missing CONFIG_SAMPLE_TRACE_PRINTK=m
* https://pad.lv/1869349 - missing CONFIG_SAMPLE_TRACE_PRINTK=m
* https://pad.lv/1874198 - nproc > 1
If the requirement was not met, these test will fail with "unresolved"
and return 1. So even these is no failed test case, the ftrace test
will still be marked as "failed" with the presence of unresolved test:
# # of passed: 28
# # of failed: 0
# # of unresolved: 1
# # of untested: 0
# # of unsupported: 58
# # of xfailed: 0
# # of undefined(test bug): 0
not ok 1 selftests: ftrace: ftracetest # exit=1
== Fix ==
* b730d668138c ("ftrace/selftest: make unresolved cases cause failure if
--fail-unresolved set")
This patch will only make unresolved test case return 1 if we ask it
to fail with unresolved test case.
It can be cherry-picked to kernels starting from Disco.
For Bionic and Xenial it needs to be backported with some context
adjustment as they're missing some other patches to the testing tool.
== Test ==
With the patch applied, the ftrace test will not be marked as failed
with the presence of unresolved test case:
# # of passed: 28
# # of failed: 0
# # of unresolved: 1
# # of untested: 0
# # of unsupported: 58
# # of xfailed: 0
# # of undefined(test bug): 0
ok 1 selftests: ftrace: ftracetest
== Regression Potential ==
Low, changes limited to testing tools, no actual impacts to our kernels.
The worst case is to cause false negative in test reports, but in that
case it's probably a test case issue since a failed case should be
treated as a failed one, instead of unresolved.
== Original Bug Report ==
There are some test cases in ftrace from ubuntu_kernel_selftests that would
need some kernel configs to be enabled.
bug 1869347
bug 1869349
We should not treat unresolved test case as a failure, as it's
expected to fail with no correlated configs enabeled.
https://github.com/torvalds/linux/commit/b730d668138cb3dd9ce78f8003986d1adae5523a
#diff-33d74da785cbc5da20f71eb1af106d68
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1877958/+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 1888510] Re: xen-netfront: potential deadlock in xennet_remove()
This bug was fixed in the package linux-aws-5.3 - 5.3.0-1032.34~18.04.2
---
linux-aws-5.3 (5.3.0-1032.34~18.04.2) bionic; urgency=medium
* bionic/linux-aws-5.3: 5.3.0-1032.34~18.04.2 -proposed tracker (LP:
#115)
* xen-netfront: potential deadlock in xennet_remove() (LP: #1888510)
- SAUCE: xen-netfront: fix potential deadlock in xennet_remove()
linux-aws-5.3 (5.3.0-1032.34~18.04.1) bionic; urgency=medium
* bionic/linux-aws-5.3: 5.3.0-1032.34~18.04.1 -proposed tracker (LP:
#1887074)
[ Ubuntu: 5.3.0-1032.34 ]
* eoan/linux-aws: 5.3.0-1032.34 -proposed tracker (LP: #1887075)
* eoan/linux: 5.3.0-64.58 -proposed tracker (LP: #1887088)
* linux 4.15.0-109-generic network DoS regression vs -108 (LP: #1886668)
- SAUCE: Revert "netprio_cgroup: Fix unlimited memory leak of v2 cgroups"
linux-aws-5.3 (5.3.0-1031.33~18.04.1) bionic; urgency=medium
* bionic/linux-aws-5.3: 5.3.0-1031.33~18.04.1 -proposed tracker (LP:
#1885480)
[ Ubuntu: 5.3.0-1031.33 ]
* eoan/linux-aws: 5.3.0-1031.33 -proposed tracker (LP: #1885481)
* eoan/linux: 5.3.0-63.57 -proposed tracker (LP: #1885495)
* seccomp_bpf fails on powerpc (LP: #1885757)
- SAUCE: selftests/seccomp: fix ptrace tests on powerpc
* The thread level parallelism would be a bottleneck when searching for the
shared pmd by using hugetlbfs (LP: #1882039)
- hugetlbfs: take read_lock on i_mmap for PMD sharing
* Eoan update: upstream stable patchset 2020-06-30 (LP: #1885775)
- ipv6: fix IPV6_ADDRFORM operation logic
- net_failover: fixed rollback in net_failover_open()
- bridge: Avoid infinite loop when suppressing NS messages with invalid
options
- vxlan: Avoid infinite loop when suppressing NS messages with invalid
options
- tun: correct header offsets in napi frags mode
- Input: mms114 - fix handling of mms345l
- ARM: 8977/1: ptrace: Fix mask for thumb breakpoint hook
- sched/fair: Don't NUMA balance for kthreads
- Input: synaptics - add a second working PNP_ID for Lenovo T470s
- drivers/net/ibmvnic: Update VNIC protocol version reporting
- powerpc/xive: Clear the page tables for the ESB IO mapping
- ath9k_htc: Silence undersized packet warnings
- RDMA/uverbs: Make the event_queue fds return POLLERR when disassociated
- x86/cpu/amd: Make erratum #1054 a legacy erratum
- perf probe: Accept the instance number of kretprobe event
- mm: add kvfree_sensitive() for freeing sensitive data objects
- aio: fix async fsync creds
- x86_64: Fix jiffies ODR violation
- x86/PCI: Mark Intel C620 MROMs as having non-compliant BARs
- x86/speculation: Prevent rogue cross-process SSBD shutdown
- x86/reboot/quirks: Add MacBook6,1 reboot quirk
- efi/efivars: Add missing kobject_put() in sysfs entry creation error path
- ALSA: es1688: Add the missed snd_card_free()
- ALSA: hda/realtek - add a pintbl quirk for several Lenovo machines
- ALSA: usb-audio: Fix inconsistent card PM state after resume
- ALSA: usb-audio: Add vendor, product and profile name for HP Thunderbolt
Dock
- ACPI: sysfs: Fix reference count leak in acpi_sysfs_add_hotplug_profile()
- ACPI: CPPC: Fix reference count leak in acpi_cppc_processor_probe()
- ACPI: GED: add support for _Exx / _Lxx handler methods
- ACPI: PM: Avoid using power resources if there are none for D0
- nilfs2: fix null pointer dereference at nilfs_segctor_do_construct()
- spi: dw: Fix controller unregister order
- spi: bcm2835aux: Fix controller unregister order
- spi: bcm-qspi: when tx/rx buffer is NULL set to 0
- PM: runtime: clk: Fix clk_pm_runtime_get() error path
- crypto: cavium/nitrox - Fix 'nitrox_get_first_device()' when ndevlist is
fully iterated
- ALSA: pcm: disallow linking stream to itself
- x86/{mce,mm}: Unmap the entire page if the whole page is affected and
poisoned
- KVM: x86: Fix APIC page invalidation race
- KVM: x86/mmu: Consolidate "is MMIO SPTE" code
- KVM: x86: only do L1TF workaround on affected processors
- x86/speculation: Avoid force-disabling IBPB based on STIBP and enhanced
IBRS.
- x86/speculation: PR_SPEC_FORCE_DISABLE enforcement for indirect branches.
- spi: Fix controller unregister order
- spi: pxa2xx: Fix controller unregister order
- spi: bcm2835: Fix controller unregister order
- spi: pxa2xx: Fix runtime PM ref imbalance on probe error
- crypto: virtio: Fix use-after-free in
virtio_crypto_skcipher_finalize_req()
- crypto: virtio: Fix src/dst scatterlist calculation in
__virtio_crypto_skcipher_do_req()
- crypto: virtio: Fix dest length calculation in
__virtio_crypto_skcipher_do_req()
- selftests/net: in rxtimestamp getopt_long needs terminating null entry
- ovl: initialize error in ovl_copy_xattr
- proc: Use new_inode not new_inode_pseudo
- video: fbdev: w100fb: Fix a potential double free.
- KVM: nSVM:
[Kernel-packages] [Bug 1888510] Re: xen-netfront: potential deadlock in xennet_remove()
This bug was fixed in the package linux-aws - 5.4.0-1021.21 --- linux-aws (5.4.0-1021.21) focal; urgency=medium * focal/linux-aws: 5.4.0-1021.21 -proposed tracker (LP: #111) * xen-netfront: potential deadlock in xennet_remove() (LP: #1888510) - SAUCE: xen-netfront: fix potential deadlock in xennet_remove() -- Stefan Bader Fri, 24 Jul 2020 11:24:21 +0200 -- 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/1888510 Title: xen-netfront: potential deadlock in xennet_remove() Status in linux-aws package in Ubuntu: Invalid Status in linux-aws-5.3 package in Ubuntu: Invalid Status in linux-aws source package in Bionic: Incomplete Status in linux-aws-5.3 source package in Bionic: Fix Released Status in linux-aws source package in Focal: Fix Released Status in linux-aws-5.3 source package in Focal: Invalid Bug description: [Impact] During our AWS testing we were experiencing deadlocks on hibernate across all Xen instance types. The trace was showing that the system was stuck in xennet_remove(): [ 358.109087] Freezing of tasks failed after 20.006 seconds (1 tasks refusing to freeze, wq_busy=0): [ 358.115102] modprobeD0 4892 4833 0x4004 [ 358.115104] Call Trace: [ 358.115112] __schedule+0x2a8/0x670 [ 358.115115] schedule+0x33/0xa0 [ 358.115118] xennet_remove+0x1f0/0x230 [xen_netfront] [ 358.115121] ? wait_woken+0x80/0x80 [ 358.115124] xenbus_dev_remove+0x51/0xa0 [ 358.115126] device_release_driver_internal+0xe0/0x1b0 [ 358.115127] driver_detach+0x49/0x90 [ 358.115129] bus_remove_driver+0x59/0xd0 [ 358.115131] driver_unregister+0x2c/0x40 [ 358.115132] xenbus_unregister_driver+0x12/0x20 [ 358.115134] netif_exit+0x10/0x7aa [xen_netfront] [ 358.115137] __x64_sys_delete_module+0x146/0x290 [ 358.115140] do_syscall_64+0x5a/0x130 [ 358.115142] entry_SYSCALL_64_after_hwframe+0x44/0xa9 This prevented hibernation to complete. The reason of this problem is a race condition in xennet_remove(): the system is reading the current state of the bus, it's requesting to change the state to "Closing", and it's waiting for the state to be changed to "Closing". However, if the state becomes "Closed" between reading the state and requesting the state change, we are stuck forever, because the state will never change from "Closed" back to "Closing". [Test case] Create any Xen-based instance in AWS, hibernate/resume multiple times. Some times the system gets stuck (hung task timeout). [Fix] Prevent the deadlock by changing the wait condition to check also for state == Closed. [Regression potential] Minimal, this change affects only Xen, more exactly only the xen- netfront driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1888510/+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 1889080] Re: ubuntu 18.04 dell OEM install broke after it auto upgraded to linux-image-gke 5.3
Your system should be using the 4.15 oem kernel and it's not expected to switch to the gke kernel. Did the 5.3 gke kernel mysteriously pushed to you after system upgrade? -- 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/1889080 Title: ubuntu 18.04 dell OEM install broke after it auto upgraded to linux- image-gke 5.3 Status in Sputnik: New Status in linux package in Ubuntu: Incomplete Bug description: Hi, as summary says, today I got an upgrade to gke which broke my 18.04 oem install (dell xps 13)... After upgrade i had ii linux-image-4.15.0-1093-oem 4.15.0-1093.103 amd64 Signed kernel image oem ii linux-image-5.3.0-1030-gke5.3.0-1030.32~18.04 amd64 Signed kernel image GKE and had to use advanced boot options to get back to a usable setup... maybe useful: dpkg -l linux* | grep ^ii ii linux-base 4.5ubuntu1.2 all Linux image base package ii linux-firmware 1.173.19 all Firmware for Linux kernel drivers ii linux-headers-4.15.0-1030-oem4.15.0-1030.35amd64 Linux kernel headers for version 4.15.0 on 64 bit x86 SMP ii linux-headers-4.15.0-1091-oem4.15.0-1091.101 amd64 Linux kernel headers for version 4.15.0 on 64 bit x86 SMP ii linux-headers-4.15.0-1093-oem4.15.0-1093.103 amd64 Linux kernel headers for version 4.15.0 on 64 bit x86 SMP ii linux-headers-oem4.15.0.1093.96amd64 OEM Linux kernel headers ii linux-image-4.15.0-1030-oem 4.15.0-1030.35amd64 Signed kernel image oem ii linux-image-4.15.0-1091-oem 4.15.0-1091.101 amd64 Signed kernel image oem ii linux-image-4.15.0-1093-oem 4.15.0-1093.103 amd64 Signed kernel image oem ii linux-image-5.3.0-1030-gke 5.3.0-1030.32~18.04.1 amd64 Signed kernel image GKE ii linux-image-oem 4.15.0.1093.96amd64 OEM Linux kernel image ii linux-libc-dev:amd64 4.15.0-112.113amd64 Linux Kernel Headers for development ii linux-libc-dev:i386 4.15.0-112.113i386 Linux Kernel Headers for development ii linux-modules-4.15.0-1030-oem4.15.0-1030.35amd64 Linux kernel extra modules for version 4.15.0 on 64 bit x86 SMP ii linux-modules-4.15.0-1091-oem4.15.0-1091.101 amd64 Linux kernel extra modules for version 4.15.0 on 64 bit x86 SMP ii linux-modules-4.15.0-1093-oem4.15.0-1093.103 amd64 Linux kernel extra modules for version 4.15.0 on 64 bit x86 SMP ii linux-modules-5.3.0-1030-gke 5.3.0-1030.32~18.04.1 amd64 Linux kernel extra modules for version 5.3.0 on 64 bit x86 SMP ii linux-oem4.15.0.1093.96amd64 Complete OEM Linux kernel and headers ii linux-oem-headers-4.15.0-10304.15.0-1030.35all Header files related to Linux kernel version 4.15.0 ii linux-oem-headers-4.15.0-10904.15.0-1090.100 all Header files related to Linux kernel version 4.15.0 ii linux-oem-headers-4.15.0-10914.15.0-1091.101 all Header files related to Linux kernel version 4.15.0 ii linux-oem-headers-4.15.0-10934.15.0-1093.103 all Header files related to Linux kernel version 4.15.0 ii linux-sound-base 1.0.25+dfsg-0ubuntu5 all base package for ALSA and OSS sound systems To manage notifications about this bug go to: https://bugs.launchpad.net/sputnik/+bug/1889080/+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 1878194] Re: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa
*** This bug is a duplicate of bug 1871794 *** https://bugs.launchpad.net/bugs/1871794 Also having issues here after upgrading to ubuntu 20.04 (it was a clean install, everything worked fine in 19.10) Also having issues after upgrading to 20.04 (A clean install did not help it) Everything worked fine on 19.10. Headphones Boose: QC35 Jabra evolve 65 stereo Laptop: Dell XPS13 9380 Ubuntu 20.04 - 5.4.0-42-generic Bluez - 5.53-0ubuntu3 PulseAudio - 13.99.1 -- 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/1878194 Title: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: After updating the release from Ubuntu 19.10 to 20.04, the bluetooth headset doesn't work anymore when HSP/HFP profile is selected. With Ubuntu 19.10 the headset was working, there was audio and the mic was perfect for video conferencing. [Steps to reproduce] 1. Connect headset (used blueman to setup and connect) 1.1. When connected the system automatically selects A2DP profile 2. Start playing audio (browser or other) 3. Change profile to HSP/HFP with pavucontrol (or blueman) 4. The audio disappears and microphone is not working (no input) 5. Optionally switch back to A2DP and the audio comes back [Expected] When switching to HSP/HFP the audio should keep playing and the microphone should start working [Notes] I tried with pavucontrol to switch between profiles while playing audio from a browser. As side note there's a led in the headset that still blinks when switching profile. I tried deleting the pulse folder under user's profile .config without success, also reinstalled packages and did a `sudo alsa force-reload` and rebooting several times. Note: not sure this is a duplicate of [Bug #1576559], it looks quite different since the profile changes but the headset stops working. [System info] Ubuntu: 20.04 - Linux 5.4.0-29-generic x86_64 pulseaudio: 1:13.99.1-1ubuntu3 bluez: 5.53-0ubuntu3 Headset: Sennheiser HD 4.50 BTNC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1878194/+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 1879707] Re: [UBUNTU 20.04] mke2fs dasd(fba), Failing CCW, default ERP has run out of retries and failed
And btw. @Jan which Ubuntu release and kernel version did you had in use? -- 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/1879707 Title: [UBUNTU 20.04] mke2fs dasd(fba),Failing CCW,default ERP has run out of retries and failed Status in Ubuntu on IBM z Systems: Incomplete Status in linux package in Ubuntu: New Bug description: mke2fs,dasd(fba) guest edevices FBA,default ERP has run out of retries and failed,Failing CCW ---uname output--- xx - 5.4.0-29-generic #33-Ubuntu SMP Wed Apr 29 14:27:18 UTC 2020 s390x s390x s390x GNU/Linux Machine Type = IBM 3906 ---Debugger--- A debugger is not configured ---Steps to Reproduce--- mke2fs to dasd(fba) devices Stack trace output: no Oops output: no System Dump Info: The system is not configured to capture a system dump. -Post a private note with access information to the machine that the bug is occuring on. -Attach sysctl -a output output to the bug. dasd(fba),Failing CCW,default ERP has run out of retries and failed between the following syslog events, mke2fs running, before mounting and starting IO to dasd(fba) devices May 14 14:33:32 ilabg13 root: ILAB_IO_FROM_MSDI_START May 14 14:48:34 ilabg13 root: ILAB_IO_FROM_MSDI_RUNNING To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1879707/+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 1879707] Re: [UBUNTU 20.04] mke2fs dasd(fba), Failing CCW, default ERP has run out of retries and failed
So I took the time to re-test this again.
My z/VM guest has 4 CPUs (but SMT on), and 4 DASD FBA devices that equally
split a 64GB zFCP/SCSI LUN in 4 16GB FBA chunks.
I've tested (in comment #8) with 2GB RAM where things worked and I wasn't able
to recreate the error situation.
I then moved to 6GB RAM and things still worked for me.
Then 8GB - where everything was still fine.
And finally 10GB - still don't see the issue.
$ grep -i 'error\|crash\|crit\|panic\|I\/O\|erp\|sense\|fba' /var/log/syslog
ul 28 10:05:23 hwe0005 systemd[1]: Stopping LSB: automatic crash report
generation...
Jul 28 10:05:23 hwe0005 systemd[1]: Stopping Configure dump on panic for System
z...
Jul 28 10:07:36 hwe0005 systemd-udevd[514]: dasd-fba:
/etc/udev/rules.d/41-generic-ccw-0.0.0009.rules:7 Failed to write
ATTR{/sys/devices/css0/0.0.0007/0.0.0009/online}, ignoring: Invalid argument
Jul 28 10:07:36 hwe0005 systemd-udevd[511]: 0.0.0102:
/etc/udev/rules.d/41-dasd-fba-0.0.0102.rules:7 Failed to write
ATTR{/sys/devices/css0/0.0.0001/0.0.0102/online}, ignoring: Invalid argument
Jul 28 10:07:36 hwe0005 systemd-udevd[522]: 0.0.0101:
/etc/udev/rules.d/41-dasd-fba-0.0.0101.rules:7 Failed to write
ATTR{/sys/devices/css0/0.0./0.0.0101/online}, ignoring: Invalid argument
Jul 28 10:07:36 hwe0005 systemd-udevd[522]: 0.0.0103:
/etc/udev/rules.d/41-dasd-fba-0.0.0103.rules:7 Failed to write
ATTR{/sys/devices/css0/0.0.0002/0.0.0103/online}, ignoring: Invalid argument
Jul 28 10:07:36 hwe0005 systemd-udevd[505]: 0.0.0104:
/etc/udev/rules.d/41-dasd-fba-0.0.0104.rules:7 Failed to write
ATTR{/sys/devices/css0/0.0.0003/0.0.0104/online}, ignoring: Invalid argument
Jul 28 10:07:36 hwe0005 kernel: [4.983272] dasd-fba.f36f2f: 0.0.0101: New
FBA DASD 9336/10 (CU 6310/80) with 16383 MB and 512 B/blk
Jul 28 10:07:36 hwe0005 kernel: [4.988020] dasd-fba.f36f2f: 0.0.0102: New
FBA DASD 9336/10 (CU 6310/80) with 16383 MB and 512 B/blk
Jul 28 10:07:36 hwe0005 kernel: [4.990317] dasd-fba.f36f2f: 0.0.0103: New
FBA DASD 9336/10 (CU 6310/80) with 16383 MB and 512 B/blk
Jul 28 10:07:36 hwe0005 kernel: [4.992370] dasd-fba.f36f2f: 0.0.0104: New
FBA DASD 9336/10 (CU 6310/80) with 16384 MB and 512 B/blk
Jul 28 10:07:36 hwe0005 systemd[1]: Condition check resulted in Process error
reports when automatic reporting is enabled (file watch) being skipped.
Jul 28 10:07:36 hwe0005 systemd[1]: Condition check resulted in Unix socket for
apport crash forwarding being skipped.
Jul 28 10:07:36 hwe0005 systemd[1]: Starting LSB: automatic crash report
generation...
Jul 28 10:07:36 hwe0005 systemd[1]: Starting Configure dump on panic for System
z...
Jul 28 10:07:36 hwe0005 apport[764]: * Starting automatic crash report
generation: apport
Jul 28 10:07:36 hwe0005 dumpconf[770]: stop on panic configured.
Jul 28 10:07:36 hwe0005 systemd[1]: Finished Configure dump on panic for System
z.
Jul 28 10:07:36 hwe0005 systemd[1]: Started LSB: automatic crash report
generation.
I'm wondering a bit about the systemd msgs and the sysfs device tree.
But other than that no ERP, sense, or panics so far ...
$ dmesg | grep -i 'error\|fail\|crash\|warn\|crit\|panic\|erp\|fba'
[4.983272] dasd-fba.f36f2f: 0.0.0101: New FBA DASD 9336/10 (CU 6310/80)
with 16383 MB and 512 B/blk
[4.988020] dasd-fba.f36f2f: 0.0.0102: New FBA DASD 9336/10 (CU 6310/80)
with 16383 MB and 512 B/blk
[4.990317] dasd-fba.f36f2f: 0.0.0103: New FBA DASD 9336/10 (CU 6310/80)
with 16383 MB and 512 B/blk
[4.992370] dasd-fba.f36f2f: 0.0.0104: New FBA DASD 9336/10 (CU 6310/80)
with 16384 MB and 512 B/blk
[5.075981] random: 7 urandom warning(s) missed due to ratelimiting
I always did a quick check of the partition data:
ubuntu@hwe0005:~$ sudo fdisk -l /dev/dasde1
Disk /dev/dasde1: 15.102 GiB, 17178902528 bytes, 33552544 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
And then created a ext3 file system using -F on all 4 FBA devices one
after the other:
ubuntu@hwe0005:~$ sudo mkfs.ext3 -F /dev/dasde1
mke2fs 1.45.5 (07-Jan-2020)
/dev/dasde1 contains a ext3 file system
created on Tue Jul 28 09:45:37 2020
Discarding device blocks: done
Creating filesystem with 4194068 4k blocks and 1048576 inodes
Filesystem UUID: c34e7583-1dc9-4b8a-8494-7a100338a7e6
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000
Allocating group tables: done
Writing inode tables: done
Creating journal (16384 blocks): done
Writing superblocks and filesystem accounting information: done
Does it have a dependency on a certain z/VM version:
And I'm running this z/VM version:
00: CP Q CPLEVEL
00: z/VM Version 6 Release 4.0, service level 1901 (64-bit)
00: Generated at 2019-06-14 14:15:49 UTC
I do the FBA devices always have to be
[Kernel-packages] [Bug 1887916] Re: Got kernel panic on clean install of Ubuntu 20.04 LTS with external HDMI display connected to integrated intel graphics adapter in Asustek UX32A laptop
>Please test latest mainline kernel: >https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.8-rc7/ It does not help. ** 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/1887916 Title: Got kernel panic on clean install of Ubuntu 20.04 LTS with external HDMI display connected to integrated intel graphics adapter in Asustek UX32A laptop Status in linux package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Download Ubuntu 20.04 LTS installation media 2. Run the installation on the Asustek UX32A laptop without external display connected 3. Finish the installation, boot installed system, install all updates 4. Connect external monitor to the HDMI output of the laptop 5. Boot Ubuntu 20.04 LTS with monitor attached Expected results: * Ubuntu founds two screens, user is able to use both of them Actual results: * Ubuntu freezes during boot. Workaround (very ill variant) - boot the system with `nomodeset`. It is ill variant because of single monitor configuration. It is hard to get logs for the freeze, below is the OCR version of the log obtained with `verbose INIT_VERBOSE=y noplymouth`: ``` [ 43.500044] Hardware name: ASUSTeK COMPUTER INC. UX32A/UX32A. BIOS UX32A.216 02/12/2014 [ 43.5000491 Workqueue: events_unbound_async_run_entry_fn [ 43.500098] RIP: 0010:intel_disable_pipe+0x1c8/0x1d0 [i915] [ 43.500099J Code: e9 b2 fe ff fr 31 f6 1c 89 c? e0 23 cb ff ff 18 8d 65 d8 5b 41 5c 41 Sd 41 5e 41 5f 5d c3 40 c7 c7 de b4 44 c0 e8 33 9b 54 fb <0f> 0b e9 63 ff ff ff 90 0f If 44 00 00 55 48 8d 46 30 48 89 cl 18 [ 43.500100] RSP: 0018:b93d400737a0 EFLAGS: 00010286 [ 43.500101] RAX: RBX: 98ff027c RCX: [ 43.500102] RDX: RSI: 0002 RDI: 0202 [ 43.500102] RBP: b93d400737c8 R08: 000a20ccb1d7 R09: bd394dc4 [ 43.500103] R10: 041d R11: 0002aef0 R12: 98ff027c077B [ 43.500103] R13: 98ff120e8000 R14: 00070008 R15: [ 43.500105] FS: () GS:98ff14e0() knlGS: [ 43.500105] CS: 0010 DS: ES: CR0: 60050033 [ 43.500106] CR2 : 55ad3bd4f668 CR3: 000ld720a005 CR4: 001606f0 [ 43.500107] Call Trace: [ 43.500153]ironlake_crtc_disable+0x7e/0x540 [i915] [ 43.500198]intel_atomic_commit_tail+0x261/0x12e0 [i915] [ 43.500201]? flush_workqueue_prep_pwqs+0x12e/0x140 [ 43.500245]intel_atomic_commit+0x204/0x2b0 [i915] [ 43.500267]drm_atomic_commit+0x4a/0x50 [drm] [ 43.500280]drm_client_modeset_commit_atomic+0x1d0/0x1f0 [drm] [ 43.500292]drm_client_modeset_commit_force+0x55/0x160 [drm] [ 43.500361]drm_fb_helper_pan_display+0xfc/0x230 [drm_kms_helper] [ 43.500348]intel_fbdev_pan_display+0x1b/0x40 [i915] [ 43.506352]fb_pan_display+0x0c/0x110 [ 43.500353]bit_update_start +0x20/0x50 [ 43.500355]fbcon_switch+0x3e5/0x5d0 [ 43.500359]redraw_screen+0xfe/0x270 [ 43.500360]do_bind_con_driver.cold+0x94/0xe4 [ 43.500362]do_take_over_console+0x12f/0x1a0 [ 43.500364]do_fbcon_takeover+0x5c/0xb0 [ 43.500365]fbcon_fb_registered+0xf4/0x100 [ 43.500366]register_framebuffer+0x207/0x310 [ 43.500373]__drm_fb_helper_initial_config_and_unlock+0x303/0x440 [drm_kms_helper] [ 43.500379]drm_fb_helper_initial_config+0x36/0x40 [drm_kms_helper] [ 43.500421]intel_fbdev_initial_config+0x18/0x30 [i915] [ 43.500425]async_run_entry_fn+0x3c/0x150 [ 43.500426]process_one_work+0x1eb/0x3b0 [ 43.500428]worker_thread+0x4d/0x400 [ 43.500429]kthread+0x104/0x140 [ 43.500431]? process_one_work+0x3b0/0x3b0 [ 43.500432]? kthread_park+0x90/0x90 [ 43.500434]ret_from_fork+0x35/0x40 [ 43.500436] --- [ end trace 32c5f2079451ea7c ] --- [ 44.604015] [drm:ironlake_crtc_enable [i915]] *ERROR* mode set failed: pipe A stuck [ 54.659975] [drm:drm_atomic_helper_wait_for_flip_done [drm_kms_helper]] *ERROR* [CRTC:42:pipe A] flip_done timed out [ 54.766978] i915 :00:02.0: fb0: i915drmfb frame buffer device ``` ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-modules-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mate 1144 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Fri Jul 17 12:15:08 2020 Dependencies: MachineType: ASUSTeK COMPUTER INC. UX32A ProcFB:
