[Kernel-packages] [Bug 1909062] Re: qede: Kubernetes Internal DNS Failure due to QL41xxx NIC not supporting IPIP tx csum offload
Thanks Manish! I am building a test kernel now, and I will let you know once it is ready to test. If we get good test results, I will submit the patch for SRU to the Ubuntu kernels once the patch has hit mainline. ** Description changed: - With QL41xxx and Ubuntu DNS server DNS failures are seen when updated to - the latest Ubuntu kernel 20.04.1 LTS version 5.4.0-52-generic. Issue was - not observed with 4.5 ubuntu-linux. + BugLink: https://bugs.launchpad.net/bugs/1909062 - Problem Definition: - OS Version: /etc/os-release shows Ubuntu 18.04.4 LTS, but Booted kernel is the latest Ubuntu 20.04.1 LTS version 5.4.0-52-generic - NIC: 2 dual-port (4) QLogic Corp. FastLinQ QL41000 Series 10/25/40/50GbE Controller [1077:8070] (rev 02) - Inbox driver qede v8.37.0.20 + [Impact] - Complete Detailed Problem Description: - Anything that uses the internal Kubernetes DNS server fails. If an external DNS server is used resolution works for non-Kubernetes IPs. + For users with QLogic QL41xxx series NICs, such as the FastLinQ QL41000 + Series 10/25/40/50GbE Controller, when they upgrade from the 4.15 kernel + to the 5.4 kernel, Kubernetes Internal DNS requests will fail, due to + these packets getting corrupted. - Similar issue is described in this article. - https://github.com/kubernetes/kubernetes/issues/95365 + Kubernetes uses IPIP tunnelled packets for internal DNS resolution, and + this particular packet type is not supported for hardware tx checksum + offload, and the packets end up corrupted when the qede driver attempts + to checksum them. - Below patch recently on upstream fixes this - - [Note that issue was introduced by driver's tunnel offload support which was added in after 4.5 kernel] + This only affects internal Kubernetes DNS, as regular DNS lookups to + regular external domains will succeed, due to them not using IPIP packet + types. + + [Fix] + + Marvell has developed a fix for the qede driver, which checks the packet + type, and if it is IPPROTO_IPIP, then csum offloads are disabled for + socket buffers of type IPIP. commit 5d5647dad259bb416fd5d3d87012760386d97530 Author: Manish Chopra - Date: Mon Dec 21 06:55:30 2020 -0800 + Date: Mon Dec 21 06:55:30 2020 -0800 + Subject: qede: fix offload for IPIP tunnel packets + Link: https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/?id=5d5647dad259bb416fd5d3d87012760386d97530 - qede: fix offload for IPIP tunnel packets + This commit is currently in the netdev tree, awaiting merge to mainline. + The commit is queued for upstream stable. - IPIP tunnels packets are unknown to device, - hence these packets are incorrectly parsed and - caused the packet corruption, so disable offlods - for such packets at run time. + [Testcase] - Signed-off-by: Manish Chopra - Signed-off-by: Sudarsana Kalluru - Signed-off-by: Igor Russkikh - Link: https://lore.kernel.org/r/20201221145530.7771-1-mani...@marvell.com - Signed-off-by: Jakub Kicinski + The system must have a QLogic QL41xxx series NIC fitted, and needs to be + a part of a Kubernetes cluster. - Thanks, - Manish + Firstly, get a list of all devices in the system: + + $ sudo ifconfig + + Next, set all devices down with: + + $ sudo ifconfig down + + Next, bring up the QLogic QL41xxx device: + + $ sudo ifconfig up + + Then, attempt to lookup an internal Kubernetes domain: + + $ nslookup + + Without the patch, the connection will time out: + + ;; connection timed out; no servers could be reached + + If we look at packet traces with tcpdump, we see it leaves the source, + but never arrives at the destination. + + There is a test kernel available in the following ppa: + + https://launchpad.net/~mruffell/+archive/ubuntu/sf297772-test + + If you install it, then Kubernetes internal DNS lookups will succeed. + + [Where problems could occur] + + If a regression were to occur, then users of the qede driver would be + affected. This is limited to those with QLogic QL41xxx series NICs. The + patch explicitly checks for IPIP type packets, so only those particular + packets would be affected. + + Since IPIP type packets are uncommon, it would not cause a total outage + on regression, since most packets are not IPIP tunnelled. It could + potentially cause problems for users who frequently handle VPN or + Kubernetes internal DNS traffic. + + A workaround would be to use ethtool to disable tx csum offload for all + packet types, or to revert to an older kernel. ** Tags added: sts -- 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/1909062 Title: qede: Kubernetes Internal DNS Failure due to QL41xxx NIC not supporting IPIP tx csum offload Status in linux package in Ubuntu: Confirmed Status in linux source package in Focal: In Progress Status in linux source package in Groovy: In Progress Bug description:
[Kernel-packages] [Bug 1883493] Re: amdgpu hangs from time to time with *ERROR* Waiting for fences timed out!
for people using stable 20.04: I used apt-cache to notice kernel 5.8 was in the repos (no special ones in use.) I don't get why it is there and not used, but decided to try it. I did: sudo apt install linux-image-5.8.0-33-generic then rebooted, and had no networking... then did: sudo apt install linux-modules-extra-5.8.0-33-generic and everything is working again, and I can use google maps without fear. not sure If I will get kernel updates 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/1883493 Title: amdgpu hangs from time to time with *ERROR* Waiting for fences timed out! Status in linux package in Ubuntu: Incomplete Bug description: un 15 08:30:42 alhazen kernel: [ 1566.155810] [drm:amdgpu_dm_commit_planes.constprop.0 [amdgpu]] *ERROR* Waiting for fences timed out! Jun 15 08:30:47 alhazen kernel: [ 1566.159792] [drm:amdgpu_dm_commit_planes.constprop.0 [amdgpu]] *ERROR* Waiting for fences timed out! Jun 15 08:30:47 alhazen kernel: [ 1571.020144] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx_0.0.0 timeout, signaled seq=535493, emitted seq=535495 Jun 15 08:30:47 alhazen kernel: [ 1571.020216] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process Xorg pid 3664 thread Xorg:cs0 pid 3694 Jun 15 08:30:47 alhazen kernel: [ 1571.020218] [drm] GPU recovery disabled. Mouse pointer still moves, but apart from that the display is frozen. Music keeps playing. 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.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Jun 15 09:09:56 2020 InstallationDate: Installed on 2020-05-28 (17 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: enp4s0no wireless extensions. lono wireless extensions. MachineType: System manufacturer System Product Name ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-37-generic root=/dev/mapper/vgubuntu-root ro quiet splash acpi-enforce-resources=lax 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 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/02/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0604 dmi.board.asset.tag: Default string dmi.board.name: PRIME X570-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0604:bd07/02/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX570-PRO:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU 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/1883493/+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 1909062] Re: Ubuntu kernel 5.x QL41xxx NIC (qede driver) Kubernetes internal DNS failure
** Changed in: linux (Ubuntu Focal) Status: New => In Progress ** Changed in: linux (Ubuntu Groovy) Status: New => In Progress ** Changed in: linux (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Groovy) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Focal) Assignee: (unassigned) => Matthew Ruffell (mruffell) ** Changed in: linux (Ubuntu Groovy) Assignee: (unassigned) => Matthew Ruffell (mruffell) ** Summary changed: - Ubuntu kernel 5.x QL41xxx NIC (qede driver) Kubernetes internal DNS failure + qede: Kubernetes Internal DNS Failure due to QL41xxx NIC not supporting IPIP tx csum offload -- 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/1909062 Title: qede: Kubernetes Internal DNS Failure due to QL41xxx NIC not supporting IPIP tx csum offload Status in linux package in Ubuntu: Confirmed Status in linux source package in Focal: In Progress Status in linux source package in Groovy: In Progress Bug description: With QL41xxx and Ubuntu DNS server DNS failures are seen when updated to the latest Ubuntu kernel 20.04.1 LTS version 5.4.0-52-generic. Issue was not observed with 4.5 ubuntu-linux. Problem Definition: OS Version: /etc/os-release shows Ubuntu 18.04.4 LTS, but Booted kernel is the latest Ubuntu 20.04.1 LTS version 5.4.0-52-generic NIC: 2 dual-port (4) QLogic Corp. FastLinQ QL41000 Series 10/25/40/50GbE Controller [1077:8070] (rev 02) Inbox driver qede v8.37.0.20 Complete Detailed Problem Description: Anything that uses the internal Kubernetes DNS server fails. If an external DNS server is used resolution works for non-Kubernetes IPs. Similar issue is described in this article. https://github.com/kubernetes/kubernetes/issues/95365 Below patch recently on upstream fixes this - [Note that issue was introduced by driver's tunnel offload support which was added in after 4.5 kernel] commit 5d5647dad259bb416fd5d3d87012760386d97530 Author: Manish Chopra Date: Mon Dec 21 06:55:30 2020 -0800 qede: fix offload for IPIP tunnel packets IPIP tunnels packets are unknown to device, hence these packets are incorrectly parsed and caused the packet corruption, so disable offlods for such packets at run time. Signed-off-by: Manish Chopra Signed-off-by: Sudarsana Kalluru Signed-off-by: Igor Russkikh Link: https://lore.kernel.org/r/20201221145530.7771-1-mani...@marvell.com Signed-off-by: Jakub Kicinski Thanks, Manish To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1909062/+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 1908829] package linux-headers-5.4.0-58 5.4.0-58.64 failed to install/upgrade: unable to create new file '/var/lib/dpkg/info/linux-headers-5.4.0-58.list-new': Operation not
-- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1908829 Title: package linux-headers-5.4.0-58 5.4.0-58.64 failed to install/upgrade: unable to create new file '/var/lib/dpkg/info/linux-headers-5.4.0-58 .list-new': Operation not permitted Status in linux package in Ubuntu: Confirmed Bug description: ...no idea??? ...we had trojans in wine and notepad++ ...microshaft #$%@^#%^# ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-headers-5.4.0-58 5.4.0-58.64 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip Date: Fri Dec 18 11:58:30 2020 ErrorMessage: unable to create new file '/var/lib/dpkg/info/linux-headers-5.4.0-58.list-new': Operation not permitted MachineType: Dell Inc. PowerEdge 2950 PackageArchitecture: all ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic root=UUID=cb5457a6-bd17-11e8-b405-001c23d6bf93 ro maybe-ubiquity PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: grub-pc 2.04-1ubuntu26.7 RfKill: SourcePackage: linux Title: package linux-headers-5.4.0-58 5.4.0-58.64 failed to install/upgrade: unable to create new file '/var/lib/dpkg/info/linux-headers-5.4.0-58.list-new': Operation not permitted UpgradeStatus: Upgraded to focal on 2020-12-17 (3 days ago) dmi.bios.date: 10/27/2007 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.0.1 dmi.board.name: 0CU542 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.0.1:bd10/27/2007:svnDellInc.:pnPowerEdge2950:pvr:rvnDellInc.:rn0CU542:rvrA01:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge 2950 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1908829/+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 1909062] Re: Ubuntu kernel 5.x QL41xxx NIC (qede driver) Kubernetes internal DNS failure
** Also affects: linux (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1909062 Title: Ubuntu kernel 5.x QL41xxx NIC (qede driver) Kubernetes internal DNS failure Status in linux package in Ubuntu: Confirmed Status in linux source package in Focal: New Status in linux source package in Groovy: New Bug description: With QL41xxx and Ubuntu DNS server DNS failures are seen when updated to the latest Ubuntu kernel 20.04.1 LTS version 5.4.0-52-generic. Issue was not observed with 4.5 ubuntu-linux. Problem Definition: OS Version: /etc/os-release shows Ubuntu 18.04.4 LTS, but Booted kernel is the latest Ubuntu 20.04.1 LTS version 5.4.0-52-generic NIC: 2 dual-port (4) QLogic Corp. FastLinQ QL41000 Series 10/25/40/50GbE Controller [1077:8070] (rev 02) Inbox driver qede v8.37.0.20 Complete Detailed Problem Description: Anything that uses the internal Kubernetes DNS server fails. If an external DNS server is used resolution works for non-Kubernetes IPs. Similar issue is described in this article. https://github.com/kubernetes/kubernetes/issues/95365 Below patch recently on upstream fixes this - [Note that issue was introduced by driver's tunnel offload support which was added in after 4.5 kernel] commit 5d5647dad259bb416fd5d3d87012760386d97530 Author: Manish Chopra Date: Mon Dec 21 06:55:30 2020 -0800 qede: fix offload for IPIP tunnel packets IPIP tunnels packets are unknown to device, hence these packets are incorrectly parsed and caused the packet corruption, so disable offlods for such packets at run time. Signed-off-by: Manish Chopra Signed-off-by: Sudarsana Kalluru Signed-off-by: Igor Russkikh Link: https://lore.kernel.org/r/20201221145530.7771-1-mani...@marvell.com Signed-off-by: Jakub Kicinski Thanks, Manish To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1909062/+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 1909884] [NEW] tracker-extract crashes with SIGSYS when adding pdf to filesystem
Public bug reported: Almost daily, _usr_libexec_tracker-extract.1000.crash shows up in /var/crash. I'm using Raspberry Pi 4B 8GB with Ubuntu 20.10 Desktop and lxqt as Desktop. uname -a: Linux myRaspi 5.8.0-1010-raspi #13-Ubuntu SMP PREEMPT Wed Dec 9 17:14:07 UTC 2020 aarch64 aarch64 aarch64 GNU/Linux I saw in a previous backtrace that a pdf was the problem. So i downloaded some pdf with firefox to /home/username/Documents. In my case it was https://www.who.int/ceh/capacity/sanitation_hygiene.pdf After doing that, a crash-report was dumped by apport to /var/crash. A backtrace and full backtrace is in the attachment. ** Affects: linux-raspi (Ubuntu) Importance: Undecided Status: New ** Tags: apport crash pdf tracker-extract ** Attachment added: "backtrace.txt" https://bugs.launchpad.net/bugs/1909884/+attachment/5448771/+files/backtrace.txt -- 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/1909884 Title: tracker-extract crashes with SIGSYS when adding pdf to filesystem Status in linux-raspi package in Ubuntu: New Bug description: Almost daily, _usr_libexec_tracker-extract.1000.crash shows up in /var/crash. I'm using Raspberry Pi 4B 8GB with Ubuntu 20.10 Desktop and lxqt as Desktop. uname -a: Linux myRaspi 5.8.0-1010-raspi #13-Ubuntu SMP PREEMPT Wed Dec 9 17:14:07 UTC 2020 aarch64 aarch64 aarch64 GNU/Linux I saw in a previous backtrace that a pdf was the problem. So i downloaded some pdf with firefox to /home/username/Documents. In my case it was https://www.who.int/ceh/capacity/sanitation_hygiene.pdf After doing that, a crash-report was dumped by apport to /var/crash. A backtrace and full backtrace is in the attachment. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1909884/+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 1909871] [NEW] package nvidia-dkms-455 455.38-0ubuntu0.20.04.1 failed to install/upgrade: installed nvidia-dkms-455 package post-installation script subprocess returned error ex
Public bug reported: what happened: == updated kernel from 5.4 to 5.10.4, reinstalled nvidia-driver-455 and it failed details: = lsb_release -rd Description:Ubuntu 20.04.1 LTS Release:20.04 apt-cache policy nvidia-driver-455 nvidia-driver-455: Installed: 455.38-0ubuntu0.20.04.1 Candidate: 455.38-0ubuntu0.20.04.1 Version table: *** 455.38-0ubuntu0.20.04.1 500 500 http://in.archive.ubuntu.com/ubuntu focal-updates/multiverse amd64 Packages 100 /var/lib/dpkg/status what should happen: == install successfully ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-dkms-455 455.38-0ubuntu0.20.04.1 Uname: Linux 5.10.4-051004-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip Date: Sun Jan 3 00:38:29 2021 ErrorMessage: installed nvidia-dkms-455 package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2020-12-27 (6 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.2 SourcePackage: nvidia-graphics-drivers-455 Title: package nvidia-dkms-455 455.38-0ubuntu0.20.04.1 failed to install/upgrade: installed nvidia-dkms-455 package post-installation script subprocess returned error exit status 10 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-455 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-455 in Ubuntu. https://bugs.launchpad.net/bugs/1909871 Title: package nvidia-dkms-455 455.38-0ubuntu0.20.04.1 failed to install/upgrade: installed nvidia-dkms-455 package post-installation script subprocess returned error exit status 10 Status in nvidia-graphics-drivers-455 package in Ubuntu: New Bug description: what happened: == updated kernel from 5.4 to 5.10.4, reinstalled nvidia-driver-455 and it failed details: = lsb_release -rd Description: Ubuntu 20.04.1 LTS Release: 20.04 apt-cache policy nvidia-driver-455 nvidia-driver-455: Installed: 455.38-0ubuntu0.20.04.1 Candidate: 455.38-0ubuntu0.20.04.1 Version table: *** 455.38-0ubuntu0.20.04.1 500 500 http://in.archive.ubuntu.com/ubuntu focal-updates/multiverse amd64 Packages 100 /var/lib/dpkg/status what should happen: == install successfully ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-dkms-455 455.38-0ubuntu0.20.04.1 Uname: Linux 5.10.4-051004-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip Date: Sun Jan 3 00:38:29 2021 ErrorMessage: installed nvidia-dkms-455 package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2020-12-27 (6 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.2 SourcePackage: nvidia-graphics-drivers-455 Title: package nvidia-dkms-455 455.38-0ubuntu0.20.04.1 failed to install/upgrade: installed nvidia-dkms-455 package post-installation script subprocess returned error exit status 10 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-455/+bug/1909871/+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 1715861] Re: r592 & r852 IRQ: DMA errors cause excessive log file entries
Still happens in kernel 5.8. -- 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/1715861 Title: r592 & r852 IRQ: DMA errors cause excessive log file entries Status in linux package in Ubuntu: Expired Bug description: -- /var/log/syslog and /var/log/kern.log grow to 100s of MiB in less than a day. -- Typical excessive syslog entry is attached (hostname redacted). I am not making hardware changes at the times these entries are made. Entires are of the form: Sep 7 20:05:55 kernel: [14098.011547] r592: IRQ: card added Sep 7 20:05:55 kernel: [14098.011548] r592: IRQ: DMA error followed by 38 lines of trace information The laptop reports itself as having the problematic Ricoh devices. Relevant hwinfo attached. grepped extract follows Model: "Ricoh R5C832 IEEE 1394 Controller" Vendor: pci 0x1180 "Ricoh Co Ltd" Model: "Ricoh xD-Picture Card Controller" Vendor: pci 0x1180 "Ricoh Co Ltd" Model: "Ricoh R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter" Vendor: pci 0x1180 "Ricoh Co Ltd" Model: "Ricoh R5C592 Memory Stick Bus Host Adapter" Vendor: pci 0x1180 "Ricoh Co Ltd" WORKAROUND: Blacklist devices by adding the following lines at the end of /etc/modprobe.d/blacklist.conf # Stop errors filling up log - see # https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1530187 # Blacklist Ricoh card reader blacklist r592 blacklist r852 This stops messages from appearing in /var/log/kern.log and /var/log/syslog. The Ricoh cardreader built into the laptop still reads SD cards after such blacklisting. --- ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: pgrb 2220 F pulseaudio /dev/snd/controlC1: pgrb 2220 F pulseaudio /dev/snd/controlC0: pgrb 2220 F pulseaudio DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=2b7792b7-4eda-4b10-b21c-ad775ff397b3 InstallationDate: Installed on 2017-09-05 (3 days ago) InstallationMedia: Lubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: LENOVO 0769BMG Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-33-generic root=/dev/mapper/herd-root ro cryptdevice=/dev/disk/by-uuid/081dc90a-6dbc-486a-8141-6635c99caca5:mithraeum quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.10.0-33-generic N/A linux-backports-modules-4.10.0-33-generic N/A linux-firmware 1.157.12 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: yes Tags: xenial Uname: Linux 4.10.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 08/15/2007 dmi.bios.vendor: LENOVO dmi.bios.version: 68ET24WW dmi.board.name: IEL10 dmi.board.vendor: LENOVO dmi.board.version: REFERENCE dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnLENOVO:bvr68ET24WW:bd08/15/2007:svnLENOVO:pn0769BMG:pvr3000N200:rvnLENOVO:rnIEL10:rvrREFERENCE:cvnNoEnclosure:ct10:cvrN/A: dmi.product.name: 0769BMG dmi.product.version: 3000 N200 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1715861/+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 1856608] Re: [Regression] usb usb2-port2: Cannot enable. Maybe the USB cable is bad?
** Changed in: linux (Ubuntu Focal) 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/1856608 Title: [Regression] usb usb2-port2: Cannot enable. Maybe the USB cable is bad? Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Fix Released Status in linux source package in Disco: Fix Released Status in linux source package in Eoan: Fix Released Status in linux source package in Focal: Confirmed Bug description: This appears to be a regression between 4.15.0-70.79 and 4.15.0-72.81. This bug was fixed by simply reverting the offending change. Bug 1859873 tracks root causing the issue and reapplying the change w/ any necessary fixes. [Impact] USB port unusable and boot time takes ~5 minutes longer to complete. Kernel emits messages like: usb usb2-port2: Cannot enable. Maybe the USB cable is bad? [Test Case] dmesg | grep "Cannot enable" [Fix] [Regression Risk] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856608/+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 1856608] Re: [Regression] usb usb2-port2: Cannot enable. Maybe the USB cable is bad?
I'm also affected by this bug. I just did a fresh install of Xubuntu 20.04.1 and see the issue. In my case it's "usb usb2-port1: Cannot enable. Maybe the USB cable is bad?". There are no USB devices connected at all, so I get the bug with only the motherboard root hub present. I can make the log messages to syslog stop by inserting a USB3 device in one of the ports connected to usb2 (a USB2 device connected to the same physical port on the PC gets connected to a different bus so that will not make the log messages stop). Booting Matthew's test kernel (5.4.0-42.46+TEST1856608v20200805b1) makes the bug go away. Booting the regular kernel (in this case 5.4.0-58-generic) and the bug is back. So please revert the git commit on 20.04 (Focal) also until a fix is found. I'll be happy to provide further info if needed. -- 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/1856608 Title: [Regression] usb usb2-port2: Cannot enable. Maybe the USB cable is bad? Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Fix Released Status in linux source package in Disco: Fix Released Status in linux source package in Eoan: Fix Released Status in linux source package in Focal: Confirmed Bug description: This appears to be a regression between 4.15.0-70.79 and 4.15.0-72.81. This bug was fixed by simply reverting the offending change. Bug 1859873 tracks root causing the issue and reapplying the change w/ any necessary fixes. [Impact] USB port unusable and boot time takes ~5 minutes longer to complete. Kernel emits messages like: usb usb2-port2: Cannot enable. Maybe the USB cable is bad? [Test Case] dmesg | grep "Cannot enable" [Fix] [Regression Risk] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856608/+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 1894329] Re: ZFS revert from grub menu not working.
Yes!
Used the Software Updater to add the groovy-proposed repository.
Selected and installed the ZFS packages (from Software Updater).
Installed a small package (using "apt install") to force a grub update.
Rebooted.
"df -h" showed root mounted on the correct filesystem (instead of the
previous, truncated "rpool/ROOT/ubuntu_").
Thank folks!!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1894329
Title:
ZFS revert from grub menu not working.
Status in coreutils package in Ubuntu:
Incomplete
Status in zfs-linux package in Ubuntu:
Fix Released
Status in coreutils source package in Focal:
Incomplete
Status in zfs-linux source package in Focal:
Fix Committed
Status in coreutils source package in Groovy:
Incomplete
Status in zfs-linux source package in Groovy:
Fix Committed
Bug description:
[Impact]
* Users can’t revert to previous snapshots when enabling the hw enablement
stack kernel on focal or using any more recent version.
* The option is available on grub and will let you with a broken system,
partially cloned.
[Test Case]
* Boot on a system, using ZFS and ZSys.
* In grub, select "History" entry
* Select one of the "Revert" option: the system should boot after being
reverted with an older version.
[Where problems could occur]
* The code is in the initramfs, where the generated id suffix for all our
ZFS datasets was empty due to new coreutils/kernels.
* We replace dd with another way (more robust and simple) for generating
this ID.
-
@coreutils maintainers, any idea why dd is being flagged as having an
executable stack?
When I try to revert to a previous state from the grub menu, the boot
fails. The system drops me to a repair modus.
zfs-mount-generator fails with the message:
couldn't ensure boot: Mounted clone bootFS dataset created by initramfs
doesn't have a valid _suffix (at least .*_): \"rpool/ROOT/ubuntu_\"".
After a reboot I have an extra clone called "rpool/ROOT/ubuntu_", indeed
without a suffix.
After a little investigation I found the problem in
/usr/share/initramfs-tools/scripts/zfs at the end in function
uid()
{
dd if=/dev/urandom of=/dev/stdout bs=1 count=100 2>/dev/null | tr -dc
'a-z0-9' | cut -c-6
}, the dd command fails during boot with the message "process 'dd' started
with executable stack.
After this an empty uid is returned which explains the dataset without a
proper suffix.
Replacing the function with:
uid()
{
grep -a -m10 -E "\*" /dev/urandom 2>/dev/null | tr -dc 'a-z0-9' | cut -c-6
}
fixes the problem.
Ubuntu version is:
Description:Ubuntu Groovy Gorilla (development branch)
Release:20.10
zfs-initramfs version is:
0.8.4-1ubuntu11
With regards,
Usarin Heininga
ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: zfs-initramfs 0.8.4-1ubuntu11
ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4
Uname: Linux 5.8.0-18-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu45
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: KDE
Date: Fri Sep 4 20:23:44 2020
InstallationDate: Installed on 2020-09-02 (2 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200831)
ProcEnviron:
LANGUAGE=
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=nl_NL.UTF-8
SHELL=/bin/bash
SourcePackage: zfs-linux
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1894329/+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 1909856] Re: amdgpu intermittently fails to resume correctly
Ah, the included dmesg output doesn't actually have the useful snippet in it. Please see attached section of log output which runs from when I attempted to resume the system to when it was rebooted. ** Attachment added: "amd-gpu-resume-fail-syslog.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1909856/+attachment/5448706/+files/amd-gpu-resume-fail-syslog.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/1909856 Title: amdgpu intermittently fails to resume correctly Status in linux package in Ubuntu: Confirmed Bug description: I started seeing my system fail to resume from suspend over the last couple of weeks. It happens about 1 in 5 times maybe? I press the power button on my system to resume it and my screens stay blank. I am able to connect to the system remotely over ssh and check syslog to find out what went wrong. I then try to reboot the system with `sudo reboot`, the ssh session disconnects but it never actually reboots. I have to press the reset button after waiting a while to make it start up again. dmesg log is attached which contains more info and the call trace. I think the interesting part is this: kernel: amdgpu :0d:00.0: [drm:amdgpu_ring_test_helper [amdgpu]] *ERROR* ring gfx test failed (-110) kernel: [drm:amdgpu_device_ip_resume_phase2 [amdgpu]] *ERROR* resume of IP block failed -110 kernel: [drm:amdgpu_device_resume [amdgpu]] *ERROR* amdgpu_device_ip_resume failed (-110). kernel: PM: dpm_run_callback(): pci_pm_resume+0x0/0xf0 returns -110 kernel: PM: Device :0d:00.0 failed to resume async: error -110 It first happened on 20.04 with kernel 5.4 (can't remember exactly what version of 5.4) a couple of weeks ago. I saw 20.10 was available with 5.8 so thought I'd try upgrading as there was a variety of amdgpu fixes go in between 5.4 and 5.8 but sadly no dice. From some research, I think what I'm seeing is similar to this bug, but that one looks like 5.4 solved it, whereas I guess some minor upgrade on 5.4 appeared to break it for me. https://bugs.freedesktop.org/show_bug.cgi?id=112221 I'm running a Ryzen 3700X on an X570 board with an AMD Radeon Pro WX 4100 GPU. Currently using Kubuntu 20.10. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-33-generic 5.8.0-33.36 ProcVersionSignature: Ubuntu 5.8.0-33.36-generic 5.8.17 Uname: Linux 5.8.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Sat Jan 2 12:40:36 2021 InstallationDate: Installed on 2020-06-18 (197 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-33-generic root=/dev/mapper/vgkubuntu-root ro quiet splash usbcore.autosuspend=-1 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-33-generic N/A linux-backports-modules-5.8.0-33-generic N/A linux-firmware1.190.2 SourcePackage: linux UpgradeStatus: Upgraded to groovy on 2020-12-30 (3 days ago) dmi.bios.date: 09/09/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.10 dmi.board.name: X570 Taichi 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.:bvrP2.10:bd09/09/2019:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX570Taichi: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/1909856/+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 1909856] 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/1909856 Title: amdgpu intermittently fails to resume correctly Status in linux package in Ubuntu: Confirmed Bug description: I started seeing my system fail to resume from suspend over the last couple of weeks. It happens about 1 in 5 times maybe? I press the power button on my system to resume it and my screens stay blank. I am able to connect to the system remotely over ssh and check syslog to find out what went wrong. I then try to reboot the system with `sudo reboot`, the ssh session disconnects but it never actually reboots. I have to press the reset button after waiting a while to make it start up again. dmesg log is attached which contains more info and the call trace. I think the interesting part is this: kernel: amdgpu :0d:00.0: [drm:amdgpu_ring_test_helper [amdgpu]] *ERROR* ring gfx test failed (-110) kernel: [drm:amdgpu_device_ip_resume_phase2 [amdgpu]] *ERROR* resume of IP block failed -110 kernel: [drm:amdgpu_device_resume [amdgpu]] *ERROR* amdgpu_device_ip_resume failed (-110). kernel: PM: dpm_run_callback(): pci_pm_resume+0x0/0xf0 returns -110 kernel: PM: Device :0d:00.0 failed to resume async: error -110 It first happened on 20.04 with kernel 5.4 (can't remember exactly what version of 5.4) a couple of weeks ago. I saw 20.10 was available with 5.8 so thought I'd try upgrading as there was a variety of amdgpu fixes go in between 5.4 and 5.8 but sadly no dice. From some research, I think what I'm seeing is similar to this bug, but that one looks like 5.4 solved it, whereas I guess some minor upgrade on 5.4 appeared to break it for me. https://bugs.freedesktop.org/show_bug.cgi?id=112221 I'm running a Ryzen 3700X on an X570 board with an AMD Radeon Pro WX 4100 GPU. Currently using Kubuntu 20.10. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-33-generic 5.8.0-33.36 ProcVersionSignature: Ubuntu 5.8.0-33.36-generic 5.8.17 Uname: Linux 5.8.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Sat Jan 2 12:40:36 2021 InstallationDate: Installed on 2020-06-18 (197 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-33-generic root=/dev/mapper/vgkubuntu-root ro quiet splash usbcore.autosuspend=-1 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-33-generic N/A linux-backports-modules-5.8.0-33-generic N/A linux-firmware1.190.2 SourcePackage: linux UpgradeStatus: Upgraded to groovy on 2020-12-30 (3 days ago) dmi.bios.date: 09/09/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.10 dmi.board.name: X570 Taichi 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.:bvrP2.10:bd09/09/2019:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX570Taichi: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/1909856/+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 1909856] [NEW] amdgpu intermittently fails to resume correctly
Public bug reported: I started seeing my system fail to resume from suspend over the last couple of weeks. It happens about 1 in 5 times maybe? I press the power button on my system to resume it and my screens stay blank. I am able to connect to the system remotely over ssh and check syslog to find out what went wrong. I then try to reboot the system with `sudo reboot`, the ssh session disconnects but it never actually reboots. I have to press the reset button after waiting a while to make it start up again. dmesg log is attached which contains more info and the call trace. I think the interesting part is this: kernel: amdgpu :0d:00.0: [drm:amdgpu_ring_test_helper [amdgpu]] *ERROR* ring gfx test failed (-110) kernel: [drm:amdgpu_device_ip_resume_phase2 [amdgpu]] *ERROR* resume of IP block failed -110 kernel: [drm:amdgpu_device_resume [amdgpu]] *ERROR* amdgpu_device_ip_resume failed (-110). kernel: PM: dpm_run_callback(): pci_pm_resume+0x0/0xf0 returns -110 kernel: PM: Device :0d:00.0 failed to resume async: error -110 It first happened on 20.04 with kernel 5.4 (can't remember exactly what version of 5.4) a couple of weeks ago. I saw 20.10 was available with 5.8 so thought I'd try upgrading as there was a variety of amdgpu fixes go in between 5.4 and 5.8 but sadly no dice. >From some research, I think what I'm seeing is similar to this bug, but that one looks like 5.4 solved it, whereas I guess some minor upgrade on 5.4 appeared to break it for me. https://bugs.freedesktop.org/show_bug.cgi?id=112221 I'm running a Ryzen 3700X on an X570 board with an AMD Radeon Pro WX 4100 GPU. Currently using Kubuntu 20.10. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-33-generic 5.8.0-33.36 ProcVersionSignature: Ubuntu 5.8.0-33.36-generic 5.8.17 Uname: Linux 5.8.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Sat Jan 2 12:40:36 2021 InstallationDate: Installed on 2020-06-18 (197 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-33-generic root=/dev/mapper/vgkubuntu-root ro quiet splash usbcore.autosuspend=-1 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-33-generic N/A linux-backports-modules-5.8.0-33-generic N/A linux-firmware1.190.2 SourcePackage: linux UpgradeStatus: Upgraded to groovy on 2020-12-30 (3 days ago) dmi.bios.date: 09/09/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.10 dmi.board.name: X570 Taichi 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.:bvrP2.10:bd09/09/2019:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX570Taichi: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. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug groovy -- 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/1909856 Title: amdgpu intermittently fails to resume correctly Status in linux package in Ubuntu: Confirmed Bug description: I started seeing my system fail to resume from suspend over the last couple of weeks. It happens about 1 in 5 times maybe? I press the power button on my system to resume it and my screens stay blank. I am able to connect to the system remotely over ssh and check syslog to find out what went wrong. I then try to reboot the system with `sudo reboot`, the ssh session disconnects but it never actually reboots. I have to press the reset button after waiting a while to make it start up again. dmesg log is attached which contains more info and the call trace. I think the interesting part is this: kernel: amdgpu :0d:00.0: [drm:amdgpu_ring_test_helper [amdgpu]] *ERROR* ring gfx test failed (-110) kernel: [drm:amdgpu_device_ip_resume_phase2 [amdgpu]] *ERROR* resume of IP block failed -110 kernel: [drm:amdgpu_device_resume [amdgpu]] *ERROR* amdgpu_device_ip_resume failed (-110). kernel: PM: dpm_run_callback(): pci_pm_resume+0x0/0xf0 returns -110 kernel: PM: Device :0d:00.0 failed to resume async: error -110 It first happened on 20.04 with kernel 5.4 (can't remember exactly what version of 5.4) a couple of weeks ago. I saw 20.10 was available with 5.8 so thought I'd try upgrading as there was a variety of
[Kernel-packages] [Bug 1871794] Re: [Bluetooth] No audio output/input in HSP/HFP mode
Problem has NOT been fixed for my setup: - Kernel: 5.4.0-58.64-generic - OS: Ubuntu 20.04.1 LTS - Machine: Dell Inspiron 7559 (0706) - Headset: Anker Soundcore Liberty Air 2 -- 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/1871794 Title: [Bluetooth] No audio output/input in HSP/HFP mode Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: I'm testing with Sony bluetooth headset SBH20, works fine in A2DP profile, but I can't get audio input and output work in HSP/HFP profile. [Reproduce steps] 1. Scan and pair BT headset in Bluetooth setting 2. Switch to HSP/HFP profile in Sound setting 3. Test sound output/input [Machine information] ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Apr 9 16:26:52 2020 InstallationDate: Installed on 2020-04-09 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) SourcePackage: pulseaudio Symptom: audio Symptom_Card: SBH20 Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio Symptom_Type: No sound at all Title: [SBH20, recording] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/17/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.13 dmi.board.name: 0188D1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.13:bd09/17/2019:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn0188D1:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 2-in-1 dmi.product.sku: 08B0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1871794/+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 Problem has NOT been fixed for my setup: - Kernel: 5.4.0-58.64-generic - OS: Ubuntu 20.04.1 LTS - Machine: Dell Inspiron 7559 (0706) - Headset: Anker Soundcore Liberty Air 2 -- 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 1901089] Re: Ubuntu kernels 5.4.0-51 and 5.4.0-52 break ir-keytable loading
I've submitted a PR https://lore.kernel.org/linux-media/20210102101209.ga32...@gofer.mess.org/T/#t This has to be merged by Mauro (linux-media). Then Linus has to merge it. Finally, it needs to be merged into the stable tree. So it may be some 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/1901089 Title: Ubuntu kernels 5.4.0-51 and 5.4.0-52 break ir-keytable loading Status in linux package in Ubuntu: Incomplete Bug description: I run mythtv on Ubuntu 20.04 and I used a custom remote control keymap in /etc/rc_keymaps to correctly map buttons on my IR remote. The above kernel seems to break custom keymap loading for my remote (certain buttons no longer work in mythtv). Reverting to kernel 5.4.0-48 corrects the problem. Description: Ubuntu 20.04.1 LTS Release: 20.04 linux-image-5.4.0-52-generic: Installed: 5.4.0-52.57 Candidate: 5.4.0-52.57 Version table: *** 5.4.0-52.57 500 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 100 /var/lib/dpkg/status belongs to the linux source package ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-52-generic 5.4.0-52.57 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: pdaniel1552 F pulseaudio /dev/snd/controlC0: pdaniel1552 F pulseaudio CasperMD5CheckResult: skip Date: Thu Oct 22 16:16:58 2020 InstallationDate: Installed on 2017-04-17 (1284 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: MSI MS-7792 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic root=UUID=38b7dfb0-9848-4919-890b-fdc027e936f1 ro radeon.dpm=0 quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.4.0-48-generic N/A linux-backports-modules-5.4.0-48-generic N/A linux-firmware1.187.3 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-05-11 (164 days ago) dmi.bios.date: 02/12/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V2.4 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: FM2-A75IA-E53 (MS-7792) dmi.board.vendor: MSI dmi.board.version: 1.0 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.:bvrV2.4:bd02/12/2015:svnMSI:pnMS-7792:pvr1.0:rvnMSI:rnFM2-A75IA-E53(MS-7792):rvr1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7792 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901089/+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 1909840] 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 1909840 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1909840 Title: SDXC card reader not working properly Status in linux package in Ubuntu: Incomplete Bug description: I have tried to use a 8GB flash and it works without any flaw in ubuntu 20.04, kernel 5.4.0-58-generic (machine: Ideapad 130s-11IGM), but i need to use my 128GB SDXC card and it only works in my windows system in the same machine. I am "able" to copy files to it in ubuntu (to the 128GB SDXC card) but most of the copies appear as corrupted files, which does not happen in windows. The 8GB card had been tested by f3 in ubuntu and h2testw in windows, and the SDXC had been tested by h2testw in windows (testing the SDXC with f3 in ubuntu causes input/output error), so i assume there are no problems in the sd cards. I think that this problem is related to (or almost the same as) https://bugzilla.kernel.org/show_bug.cgi?id=202473 by lspci i get 00:00.0 Host bridge: Intel Corporation Gemini Lake Host Bridge (rev 03) 00:00.1 Signal processing controller: Intel Corporation Celeron/Pentium Silver Processor Dynamic Platform and Thermal Framework Processor Participant (rev 03) 00:00.3 System peripheral: Intel Corporation Device 3190 (rev 03) 00:02.0 VGA compatible controller: Intel Corporation UHD Graphics 605 (rev 03) 00:0e.0 Audio device: Intel Corporation Device 3198 (rev 03) 00:0f.0 Communication controller: Intel Corporation Celeron/Pentium Silver Processor Trusted Execution Engine Interface (rev 03) 00:12.0 SATA controller: Intel Corporation Device 31e3 (rev 03) 00:13.0 PCI bridge: Intel Corporation Gemini Lake PCI Express Root Port (rev f3) 00:14.0 PCI bridge: Intel Corporation Gemini Lake PCI Express Root Port (rev f3) 00:14.1 PCI bridge: Intel Corporation Gemini Lake PCI Express Root Port (rev f3) 00:15.0 USB controller: Intel Corporation Device 31a8 (rev 03) 00:17.0 Signal processing controller: Intel Corporation Device 31b4 (rev 03) 00:1c.0 SD Host controller: Intel Corporation Celeron/Pentium Silver Processor SDA Standard Compliant SD Host Controller (rev 03) 00:1f.0 ISA bridge: Intel Corporation Device 31e8 (rev 03) 00:1f.1 SMBus: Intel Corporation Celeron/Pentium Silver Processor Gaussian Mixture Model (rev 03) - 02:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5229 PCI Express Card Reader (rev 01) - 03:00.0 Network controller: Intel Corporation Dual Band Wireless-AC 3165 Plus Bluetooth (rev 99) booting up and putting the SDXC card and removing it gives by dmesg [ 119.612298] mmc1: cannot verify signal voltage switch [ 119.737024] mmc1: new ultra high speed SDR104 SDXC card at address [ 119.737955] mmcblk1: mmc1: SB128 119 GiB [ 119.755488] mmcblk1: p1 [ 208.417246] mmc1: card removed The module used is rtsx_pci. by lspci -nnk|grep -A2 RTS5229 02:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5229 PCI Express Card Reader [10ec:5229] (rev 01) Subsystem: Realtek Semiconductor Co., Ltd. RTS5229 PCI Express Card Reader [10ec:5229] Kernel driver in use: rtsx_pci Kernel modules: rtsx_pci Sorry for the lack of information, i tried to use ubuntu-bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1909840/+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 1909840] Re: SDXC card reader not working properly
** Package changed: ubuntu => linux (Ubuntu) ** Tags added: 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/1909840 Title: SDXC card reader not working properly Status in linux package in Ubuntu: Incomplete Bug description: I have tried to use a 8GB flash and it works without any flaw in ubuntu 20.04, kernel 5.4.0-58-generic (machine: Ideapad 130s-11IGM), but i need to use my 128GB SDXC card and it only works in my windows system in the same machine. I am "able" to copy files to it in ubuntu (to the 128GB SDXC card) but most of the copies appear as corrupted files, which does not happen in windows. The 8GB card had been tested by f3 in ubuntu and h2testw in windows, and the SDXC had been tested by h2testw in windows (testing the SDXC with f3 in ubuntu causes input/output error), so i assume there are no problems in the sd cards. I think that this problem is related to (or almost the same as) https://bugzilla.kernel.org/show_bug.cgi?id=202473 by lspci i get 00:00.0 Host bridge: Intel Corporation Gemini Lake Host Bridge (rev 03) 00:00.1 Signal processing controller: Intel Corporation Celeron/Pentium Silver Processor Dynamic Platform and Thermal Framework Processor Participant (rev 03) 00:00.3 System peripheral: Intel Corporation Device 3190 (rev 03) 00:02.0 VGA compatible controller: Intel Corporation UHD Graphics 605 (rev 03) 00:0e.0 Audio device: Intel Corporation Device 3198 (rev 03) 00:0f.0 Communication controller: Intel Corporation Celeron/Pentium Silver Processor Trusted Execution Engine Interface (rev 03) 00:12.0 SATA controller: Intel Corporation Device 31e3 (rev 03) 00:13.0 PCI bridge: Intel Corporation Gemini Lake PCI Express Root Port (rev f3) 00:14.0 PCI bridge: Intel Corporation Gemini Lake PCI Express Root Port (rev f3) 00:14.1 PCI bridge: Intel Corporation Gemini Lake PCI Express Root Port (rev f3) 00:15.0 USB controller: Intel Corporation Device 31a8 (rev 03) 00:17.0 Signal processing controller: Intel Corporation Device 31b4 (rev 03) 00:1c.0 SD Host controller: Intel Corporation Celeron/Pentium Silver Processor SDA Standard Compliant SD Host Controller (rev 03) 00:1f.0 ISA bridge: Intel Corporation Device 31e8 (rev 03) 00:1f.1 SMBus: Intel Corporation Celeron/Pentium Silver Processor Gaussian Mixture Model (rev 03) - 02:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5229 PCI Express Card Reader (rev 01) - 03:00.0 Network controller: Intel Corporation Dual Band Wireless-AC 3165 Plus Bluetooth (rev 99) booting up and putting the SDXC card and removing it gives by dmesg [ 119.612298] mmc1: cannot verify signal voltage switch [ 119.737024] mmc1: new ultra high speed SDR104 SDXC card at address [ 119.737955] mmcblk1: mmc1: SB128 119 GiB [ 119.755488] mmcblk1: p1 [ 208.417246] mmc1: card removed The module used is rtsx_pci. by lspci -nnk|grep -A2 RTS5229 02:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5229 PCI Express Card Reader [10ec:5229] (rev 01) Subsystem: Realtek Semiconductor Co., Ltd. RTS5229 PCI Express Card Reader [10ec:5229] Kernel driver in use: rtsx_pci Kernel modules: rtsx_pci Sorry for the lack of information, i tried to use ubuntu-bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1909840/+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 1909840] [NEW] SDXC card reader not working properly
You have been subscribed to a public bug: I have tried to use a 8GB flash and it works without any flaw in ubuntu 20.04, kernel 5.4.0-58-generic (machine: Ideapad 130s-11IGM), but i need to use my 128GB SDXC card and it only works in my windows system in the same machine. I am "able" to copy files to it in ubuntu (to the 128GB SDXC card) but most of the copies appear as corrupted files, which does not happen in windows. The 8GB card had been tested by f3 in ubuntu and h2testw in windows, and the SDXC had been tested by h2testw in windows (testing the SDXC with f3 in ubuntu causes input/output error), so i assume there are no problems in the sd cards. I think that this problem is related to (or almost the same as) https://bugzilla.kernel.org/show_bug.cgi?id=202473 by lspci i get 00:00.0 Host bridge: Intel Corporation Gemini Lake Host Bridge (rev 03) 00:00.1 Signal processing controller: Intel Corporation Celeron/Pentium Silver Processor Dynamic Platform and Thermal Framework Processor Participant (rev 03) 00:00.3 System peripheral: Intel Corporation Device 3190 (rev 03) 00:02.0 VGA compatible controller: Intel Corporation UHD Graphics 605 (rev 03) 00:0e.0 Audio device: Intel Corporation Device 3198 (rev 03) 00:0f.0 Communication controller: Intel Corporation Celeron/Pentium Silver Processor Trusted Execution Engine Interface (rev 03) 00:12.0 SATA controller: Intel Corporation Device 31e3 (rev 03) 00:13.0 PCI bridge: Intel Corporation Gemini Lake PCI Express Root Port (rev f3) 00:14.0 PCI bridge: Intel Corporation Gemini Lake PCI Express Root Port (rev f3) 00:14.1 PCI bridge: Intel Corporation Gemini Lake PCI Express Root Port (rev f3) 00:15.0 USB controller: Intel Corporation Device 31a8 (rev 03) 00:17.0 Signal processing controller: Intel Corporation Device 31b4 (rev 03) 00:1c.0 SD Host controller: Intel Corporation Celeron/Pentium Silver Processor SDA Standard Compliant SD Host Controller (rev 03) 00:1f.0 ISA bridge: Intel Corporation Device 31e8 (rev 03) 00:1f.1 SMBus: Intel Corporation Celeron/Pentium Silver Processor Gaussian Mixture Model (rev 03) - 02:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5229 PCI Express Card Reader (rev 01) - 03:00.0 Network controller: Intel Corporation Dual Band Wireless-AC 3165 Plus Bluetooth (rev 99) booting up and putting the SDXC card and removing it gives by dmesg [ 119.612298] mmc1: cannot verify signal voltage switch [ 119.737024] mmc1: new ultra high speed SDR104 SDXC card at address [ 119.737955] mmcblk1: mmc1: SB128 119 GiB [ 119.755488] mmcblk1: p1 [ 208.417246] mmc1: card removed The module used is rtsx_pci. by lspci -nnk|grep -A2 RTS5229 02:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5229 PCI Express Card Reader [10ec:5229] (rev 01) Subsystem: Realtek Semiconductor Co., Ltd. RTS5229 PCI Express Card Reader [10ec:5229] Kernel driver in use: rtsx_pci Kernel modules: rtsx_pci Sorry for the lack of information, i tried to use ubuntu-bug. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- SDXC card reader not working properly https://bugs.launchpad.net/bugs/1909840 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 1876856] Re: xenial: soft lockup in check_unsafe_exec()
issue was reproduced once again, now on 4.4.0-197 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/1876856
Title:
xenial: soft lockup in check_unsafe_exec()
Status in linux package in Ubuntu:
In Progress
Bug description:
Endless cycle was detected few times during ubuntu 16.04 testing insied
openvz VMs
dmesg output and crash dump ivestigation shows that foolowing ubuntu
16.04.patch is guilty
commit d6572202d986a84feda4cf7e6ce0bebaa18cb8fe
Author: Colin Ian King
Date: Fri May 12 15:51:56 2017 +0100
UBUNTU:SAUCE: exec: ensure file system accounting in check_unsafe_exec is
correct
BugLink: http://bugs.launchpad.net/bugs/1672819
fs/exec.c:: check_unsafe_exec()
...
recheck:
fs_recheck = false;
t = p;
n_fs = 1;
spin_lock(>fs->lock);
rcu_read_lock();
while_each_thread(p, t) {
if (t->fs == p->fs)
n_fs++;
if (t->flags & (PF_EXITING | PF_FORKNOEXEC))
fs_recheck = true;
}
rcu_read_unlock();
if (p->fs->users > n_fs) {
if (fs_recheck) {
spin_unlock(>fs->lock);
goto recheck; << cycles forever
}
bprm->unsafe |= LSM_UNSAFE_SHARE;
} else
p->fs->in_exec = 1;
spin_unlock(>fs->lock);
dmesg example is attached,
let me know if you want to look at crash dump image.
Bug is xenial-specific (4.4 kernel), other kernel branches seems are not
affected.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1876856/+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
