[Kernel-packages] [Bug 1881525] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1881525/+attachment/5379211/+files/ProcEnviron.txt -- 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/1881525 Title: in kernel amdgpu failed with W5500 [1002:7341] Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Bionic: In Progress Bug description: [Impact] [Fix] X-HWE-Bug: Bug #1880678 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 Dependencies: DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-hotpie+X34 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-05-25 (6 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 Package: linux-firmware 1.173.18+navi14 [origin: LP-PPA-shanelin-linux-firmware] PackageArchitecture: all ProcVersionSignature: Ubuntu 5.4.0-31.35~18.04.2-generic 5.4.34 Tags: bionic uec-images third-party-packages Uname: Linux 5.4.0-31-generic x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1881525/+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 1881525] Re: in kernel amdgpu failed with W5500 [1002:7341]
apport information ** Tags added: apport-collected bionic third-party-packages uec-images ** Description changed: [Impact] [Fix] X-HWE-Bug: Bug #1880678 + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.14 + Architecture: amd64 + Dependencies: + + DistributionChannelDescriptor: + # This is the distribution channel descriptor for the OEM CDs + # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor + canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-hotpie+X34 + DistroRelease: Ubuntu 18.04 + InstallationDate: Installed on 2020-05-25 (6 days ago) + InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 + Package: linux-firmware 1.173.18+navi14 [origin: LP-PPA-shanelin-linux-firmware] + PackageArchitecture: all + ProcVersionSignature: Ubuntu 5.4.0-31.35~18.04.2-generic 5.4.34 + Tags: bionic uec-images third-party-packages + Uname: Linux 5.4.0-31-generic x86_64 + UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1881525/+attachment/5379210/+files/ProcCpuinfoMinimal.txt -- 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/1881525 Title: in kernel amdgpu failed with W5500 [1002:7341] Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Bionic: In Progress Bug description: [Impact] [Fix] X-HWE-Bug: Bug #1880678 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 Dependencies: DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-hotpie+X34 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-05-25 (6 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 Package: linux-firmware 1.173.18+navi14 [origin: LP-PPA-shanelin-linux-firmware] PackageArchitecture: all ProcVersionSignature: Ubuntu 5.4.0-31.35~18.04.2-generic 5.4.34 Tags: bionic uec-images third-party-packages Uname: Linux 5.4.0-31-generic x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1881525/+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 1879630] Re: No sound output from HDMI audio
apport is not supported in uc20 (tried beta apport snap, not working), please let me know what kind of log could 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/1879630 Title: No sound output from HDMI audio Status in snapd: New Status in linux package in Ubuntu: Confirmed Bug description: There is no sound output from HDMI audio. System: Intel NUC7CJYH Image: 20200519.2 Steps to reproduce: 1. $ sudo snap install alsa-utils 2. $ sudo amixer set Master 100 unmute 3. $ sudo amixer set IEC958 100 unmute 4. $ sudo speaker-test -c2 There is no sound output from HDMI audio. To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1879630/+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 1881525] Re: in kernel amdgpu failed with W5500 [1002:7341]
** Description changed: [Impact] [Fix] + + X-HWE-Bug: Bug #1880678 -- 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/1881525 Title: in kernel amdgpu failed with W5500 [1002:7341] Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Bionic: In Progress Bug description: [Impact] [Fix] X-HWE-Bug: Bug #1880678 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1881525/+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 1874685] Re: Killer(R) Wi-Fi 6 AX1650i 160MHz Wireless Network Adapter (201NGW), REV=0x354 [8086:a0f0] subsystem id [1a56:1651] wireless adapter not found due to firmware crash
@Daniel, please file a new bug via apport-bug instead. -- 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/1874685 Title: Killer(R) Wi-Fi 6 AX1650i 160MHz Wireless Network Adapter (201NGW), REV=0x354 [8086:a0f0] subsystem id [1a56:1651] wireless adapter not found due to firmware crash Status in HWE Next: New Status in linux package in Ubuntu: In Progress 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: Invalid 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 Committed Status in linux-oem-5.6 source package in Eoan: Invalid Status in linux-oem-osp1 source package in Eoan: Invalid Status in linux source package in Focal: Fix Committed Status in linux-oem-5.6 source package in Focal: Fix Released Status in linux-oem-osp1 source package in Focal: Invalid Status in linux source package in Groovy: In Progress Status in linux-oem-5.6 source package in Groovy: Fix Released Status in linux-oem-osp1 source package in Groovy: Invalid Bug description: [9.924130] iwlwifi :00:14.3: enabling device ( -> 0002) [ 10.031456] iwlwifi :00:14.3: TLV_FW_FSEQ_VERSION: FSEQ Version: 58.3.35.22 [ 10.031480] iwlwifi :00:14.3: Found debug destination: EXTERNAL_DRAM [ 10.031489] iwlwifi :00:14.3: Found debug configuration: 0 [ 10.033948] iwlwifi :00:14.3: loaded firmware version 50.3e391d3e.0 op_mode iwlmvm [ 10.218293] iwlwifi :00:14.3: Detected Killer(R) Wi-Fi 6 AX1650i 160MHz Wireless Network Adapter (201NGW), REV=0x354 [ 10.232843] iwlwifi :00:14.3: Applying debug destination EXTERNAL_DRAM [ 10.235398] iwlwifi :00:14.3: Allocated 0x0040 bytes for firmware monitor. [ 11.241180] iwlwifi :00:14.3: Collecting data: trigger 15 fired. [ 11.489274] iwlwifi :00:14.3: Start IWL Error Log Dump: [ 11.489293] iwlwifi :00:14.3: Status: 0x, count: -673266569 [ 11.489303] iwlwifi :00:14.3: Loaded firmware version: 50.3e391d3e.0 [ 11.489315] iwlwifi :00:14.3: 0x90F1F96A | ADVANCED_SYSASSERT [ 11.489323] iwlwifi :00:14.3: 0x7A7986FC | trm_hw_status0 [ 11.489331] iwlwifi :00:14.3: 0x09E990EC | trm_hw_status1 [ 11.489338] iwlwifi :00:14.3: 0x3073F272 | branchlink2 [ 11.489345] iwlwifi :00:14.3: 0xD569005D | interruptlink1 [ 11.489352] iwlwifi :00:14.3: 0xFEA17D01 | interruptlink2 [ 11.489359] iwlwifi :00:14.3: 0x4BBD0C7B | data1 [ 11.489367] iwlwifi :00:14.3: 0xB33DAF15 | data2 [ 11.489375] iwlwifi :00:14.3: 0xC8E4188F | data3 [ 11.489382] iwlwifi :00:14.3: 0xDEC3F4B3 | beacon time [ 11.489389] iwlwifi :00:14.3: 0xD5B7AAC7 | tsf low [ 11.489395] iwlwifi :00:14.3: 0x00073EAF | tsf hi [ 11.489402] iwlwifi :00:14.3: 0xB943A8DA | time gp1 [ 11.489409] iwlwifi :00:14.3: 0x6CCF8627 | time gp2 [ 11.489417] iwlwifi :00:14.3: 0x7944BDC6 | uCode revision type [ 11.489424] iwlwifi :00:14.3: 0x3C9DCF39 | uCode version major [ 11.489431] iwlwifi :00:14.3: 0xAF537547 | uCode version minor [ 11.489439] iwlwifi :00:14.3: 0xBC11442E | hw version [ 11.489447] iwlwifi :00:14.3: 0x160C9445 | board version [ 11.489453] iwlwifi :00:14.3: 0x276F21F6 | hcmd [ 11.489460] iwlwifi :00:14.3: 0x022688AB | isr0 [ 11.489466] iwlwifi :00:14.3: 0xEBF64685 | isr1 [ 11.489473] iwlwifi :00:14.3: 0x9D16A85F | isr2 [ 11.489480] iwlwifi :00:14.3: 0x606C870F | isr3 [ 11.489488] iwlwifi :00:14.3: 0x1B3967BF | isr4 [ 11.489495] iwlwifi :00:14.3: 0xFFBCEAB8 | last cmd Id [ 11.489503] iwlwifi :00:14.3: 0xAEB80995 | wait_event [ 11.489512] iwlwifi :00:14.3: 0x95AD6DCD | l2p_control [ 11.489518] iwlwifi :00:14.3: 0x06D3D9B3 | l2p_duration [ 11.489526] iwlwifi :00:14.3: 0x51B4EEA2 | l2p_mhvalid [ 11.489533] iwlwifi :00:14.3: 0x51B8C323 | l2p_addr_match [ 11.489540] iwlwifi :00:14.3: 0x81E0114B | lmpm_pmg_sel [ 11.489548] iwlwifi :00:14.3: 0xF4D75F29 | timestamp [ 11.489555] iwlwifi :00:14.3: 0x1AFE14FD | flow_handler [ 11.489635] iwlwifi :00:14.3: Start IWL Error Log Dump: [ 11.489643] iwlwifi :00:14.3: Status: 0x, count: 7 [ 11.489652] iwlwifi :00:14.3: 0x201013F1 | ADVANCED_SYSASSERT [ 11.489659] iwlwifi :00:14.3: 0x | umac branchlink1 [ 11.489666] iwlwifi :00:14.3: 0x80465E6A | umac branchlink2 [ 11.489674] iwlwifi :00:14.3: 0x | umac interruptlink1 [ 11.489681] iwlwifi :00:14.3: 0x | umac interruptlink2 [ 11.489688] iwlwifi :00:14.3: 0x0003 |
[Kernel-packages] [Bug 1881525] [NEW] in kernel amdgpu failed with W5500 [1002:7341]
Public bug reported: [Impact] [Fix] X-HWE-Bug: Bug #1880678 ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux-firmware (Ubuntu Bionic) Importance: Undecided Assignee: Hsuan-Yu Lin (shanelin) Status: In Progress ** Also affects: linux-oem-osp1 (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux-oem-osp1 (Ubuntu Bionic) Assignee: (unassigned) => Hsuan-Yu Lin (shanelin) ** Also affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** No longer affects: linux-oem-osp1 (Ubuntu) ** No longer affects: linux-oem-osp1 (Ubuntu Bionic) ** Changed in: linux-firmware (Ubuntu Bionic) Assignee: (unassigned) => Hsuan-Yu Lin (shanelin) ** Changed in: linux-firmware (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux-firmware (Ubuntu) Status: New => Invalid -- 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/1881525 Title: in kernel amdgpu failed with W5500 [1002:7341] Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Bionic: In Progress Bug description: [Impact] [Fix] X-HWE-Bug: Bug #1880678 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1881525/+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 1867916] Re: Regression in kernel 4.15.0-91 causes kernel panic with Bcache
Works on focal! Linux nibbler 5.4.0-34-generic #38+lp1867916b1 SMP Sun May 31 21:41:06 -03 2020 x86_64 x86_64 x86_64 GNU/Linux Thanks! I'm curious to see the patch; I tried root causing it myself and suspected it had to do with something like an overflow in an unanticipated block size, but never got anywhere on that. Also keep in mind I filed an upstream bug (https://bugzilla.kernel.org/show_bug.cgi?id=207811), so please make sure to reference that when submitting the fix upstream. Again, thank you Mauricio! -- 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/1867916 Title: Regression in kernel 4.15.0-91 causes kernel panic with Bcache Status in Linux: Unknown Status in linux package in Ubuntu: In Progress Bug description: After upgrading from kernel 4.15.0-88 to 4.15.0-91 one of our systems does not boot any longer. It always crashes during boot with a kernel panic. I suspect that this crash might be related to Bcache because this is the only one of our systems where we use Bcache and the kernel panic appears right after Bcache initialization. I already checked that this bug still exists in the 4.15.0-92.93 kernel from proposed. Unfortunately, I cannot do a bisect because this is a critical production system and we do not have any other system with a similar configuration. I attached a screenshot with the trace of the kernel panic. The last message that appears before the kernel panic (or rather the last one that I can see - there is a rather long pause between that message and the panic and I cannot scroll up far enough to ensure that there are no other messages in between) is: bcache: register_bcache() error /dev/dm-0: device already registered When booting with kernel 4.15.0-88 that does not have this problem, the next message is bcache: register_bcache() error /dev/dm-12: device already registered (emitting change event) After that the next message is: Begin: Loading essential drivers ... done This message also appears after the kernel panic, but the boot process stalls and the system can only be recovered by doing a hardware reset. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-88-generic 4.15.0-88.88 ProcVersionSignature: Ubuntu 4.15.0-88.88-generic 4.15.18 Uname: Linux 4.15.0-88-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 17 21:08 seq crw-rw 1 root audio 116, 33 Mar 17 21:08 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Wed Mar 18 12:55:18 2020 HibernationDevice: RESUME=UUID=40512ea2-9fce-40f5-8362-5daf955cc26a InstallationDate: Installed on 2013-07-02 (2450 days ago) InstallationMedia: Ubuntu-Server 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130214) MachineType: HP ProLiant DL160 G6 PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-88-generic root=/dev/mapper/vg0-root ro nosmt nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw RelatedPackageVersions: linux-restricted-modules-4.15.0-88-generic N/A linux-backports-modules-4.15.0-88-generic N/A linux-firmware 1.173.16 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-09-23 (541 days ago) dmi.bios.date: 11/06/2009 dmi.bios.vendor: HP dmi.bios.version: O33 dmi.chassis.asset.tag: 0191525 dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrO33:bd11/06/2009:svnHP:pnProLiantDL160G6:pvr:cvnHP:ct23:cvr: dmi.product.name: ProLiant DL160 G6 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1867916/+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 1869919] Re: Kernel 5.3.0-40-generic cannot boot from PATA drive
[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/1869919 Title: Kernel 5.3.0-40-generic cannot boot from PATA drive Status in linux package in Ubuntu: Expired Bug description: Ubuntu-Budgie 18.04.4 amd64 kernel linux-image-5.3.0-40-generic I build a Ubuntu PC and I used PATA notebook disk (44 PIN connector, SSD) PROBLEM DESCRIPTION PC works fine with kernel "linux-image-5.3.0-28-generic" but when I try to use updated kernel "linux-image-5.3.0-40-generic", it fails to boot and reports it cannot find disk. I have to manually select older kernel in GRUB during boot process. Kernel linux- image-5.3.0-40-generic starts but when it tries to mount root partition it fails and reports it cannot find it (to have exact message I have to reboot PC). Are PATA disk drivers included with updated kernel? INFO # uname -a Linux fah 5.3.0-28-generic #30~18.04.1-Ubuntu SMP Fri Jan 17 06:14:09 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux # inxi -F # HW info System:Host: fah Kernel: 5.3.0-28-generic x86_64 bits: 64 Console: tty 2 Distro: Ubuntu 18.04.4 LTS Machine: Device: desktop Mobo: Gigabyte model: GA-MA78G-DS3H serial: N/A BIOS: Award v: F9 date: 11/16/2012 CPU: Dual core AMD Athlon 64 X2 3800+ (-MCP-) cache: 1024 KB clock speeds: max: 2000 MHz 1: 2000 MHz 2: 2000 MHz Graphics: Card-1: Advanced Micro Devices [AMD/ATI] RS780 [Radeon HD 3200] Card-2: NVIDIA GP106 [GeForce GTX 1060 3GB] Display Server: X.org 1.20.5 drivers: ati,radeon (unloaded: modesetting,nvidia,fbdev,vesa,nouveau) tty size: 114x33 Advanced Data: N/A for root out of X Audio: Card-1 Advanced Micro Devices [AMD/ATI] RS780 HDMI Audio [Radeon 3000/3100 / HD 3200/3300] driver: snd_hda_intel Card-2 NVIDIA GP106 High Definition Audio Controller driver: snd_hda_intel Card-3 Advanced Micro Devices [AMD/ATI] SBx00 Azalia (Intel HDA) driver: snd_hda_intel Sound: Advanced Linux Sound Architecture v: k5.3.0-28-generic Network: Card: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller driver: r8169 IF: enp3s0 state: up speed: 1000 Mbps duplex: full mac: 00:1f:d0:97:b9:42 Drives:HDD Total Size: 64.0GB (32.6% used) ID-1: /dev/sda model: TS64GPSD320 size: 64.0GB Partition: ID-1: / size: 59G used: 16G (29%) fs: ext4 dev: /dev/sda1 ID-2: swap-1 size: 1.95GB used: 0.00GB (0%) fs: swap dev: /dev/zram0 ID-3: swap-2 size: 1.95GB used: 0.00GB (0%) fs: swap dev: /dev/zram1 RAID: No RAID devices: /proc/mdstat, md_mod kernel module present Sensors: System Temperatures: cpu: 90.0C mobo: 43.0C Fan Speeds (in rpm): cpu: 1956 fan-2: 0 fan-3: 0 Info: Processes: 216 Uptime: 11 days Memory: 2416.1/7456.3MB Init: systemd runlevel: 5 Client: Shell (bash) inxi: 2.3.56 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.13 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC2', '/dev/snd/hwC2D0', '/dev/snd/pcmC2D8p', '/dev/snd/pcmC2D7p', '/dev/snd/pcmC2D3p', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 IwConfig: enp3s0no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. GA-MA78G-DS3H NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-28-generic root=UUID=f9f74101-cc1d-4d7e-9621-9a012e09c9c8 ro quiet splash ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 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.3.0-28-generic N/A linux-backports-modules-5.3.0-28-generic N/A linux-firmware1.173.16 RfKill: Tags: bionic Uname: Linux 5.3.0-28-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: False dmi.bios.date: 11/16/2012 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F9 dmi.board.name: GA-MA78G-DS3H dmi.board.vendor: Gigabyte Technology Co., Ltd.
[Kernel-packages] [Bug 1867916] Re: Regression in kernel 4.15.0-91 causes kernel panic with Bcache
Hi Ryan and Sebastian, Could you please verify whether these test kernels resolve the problem? There's 5.4 for Focal/20.04 and 4.15 for Bionic/18.04. https://people.canonical.com/~mfo/lp1867916/focal/ https://people.canonical.com/~mfo/lp1867916/bionic/ Thank you, Mauricio -- 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/1867916 Title: Regression in kernel 4.15.0-91 causes kernel panic with Bcache Status in Linux: Unknown Status in linux package in Ubuntu: In Progress Bug description: After upgrading from kernel 4.15.0-88 to 4.15.0-91 one of our systems does not boot any longer. It always crashes during boot with a kernel panic. I suspect that this crash might be related to Bcache because this is the only one of our systems where we use Bcache and the kernel panic appears right after Bcache initialization. I already checked that this bug still exists in the 4.15.0-92.93 kernel from proposed. Unfortunately, I cannot do a bisect because this is a critical production system and we do not have any other system with a similar configuration. I attached a screenshot with the trace of the kernel panic. The last message that appears before the kernel panic (or rather the last one that I can see - there is a rather long pause between that message and the panic and I cannot scroll up far enough to ensure that there are no other messages in between) is: bcache: register_bcache() error /dev/dm-0: device already registered When booting with kernel 4.15.0-88 that does not have this problem, the next message is bcache: register_bcache() error /dev/dm-12: device already registered (emitting change event) After that the next message is: Begin: Loading essential drivers ... done This message also appears after the kernel panic, but the boot process stalls and the system can only be recovered by doing a hardware reset. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-88-generic 4.15.0-88.88 ProcVersionSignature: Ubuntu 4.15.0-88.88-generic 4.15.18 Uname: Linux 4.15.0-88-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 17 21:08 seq crw-rw 1 root audio 116, 33 Mar 17 21:08 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Wed Mar 18 12:55:18 2020 HibernationDevice: RESUME=UUID=40512ea2-9fce-40f5-8362-5daf955cc26a InstallationDate: Installed on 2013-07-02 (2450 days ago) InstallationMedia: Ubuntu-Server 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130214) MachineType: HP ProLiant DL160 G6 PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-88-generic root=/dev/mapper/vg0-root ro nosmt nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw RelatedPackageVersions: linux-restricted-modules-4.15.0-88-generic N/A linux-backports-modules-4.15.0-88-generic N/A linux-firmware 1.173.16 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-09-23 (541 days ago) dmi.bios.date: 11/06/2009 dmi.bios.vendor: HP dmi.bios.version: O33 dmi.chassis.asset.tag: 0191525 dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrO33:bd11/06/2009:svnHP:pnProLiantDL160G6:pvr:cvnHP:ct23:cvr: dmi.product.name: ProLiant DL160 G6 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1867916/+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 1775717] Re: CPU/GPU Fans suddenly go 100% RPM on Asus ROG G752VT
PC3 will be really hot, it should normally reach PC8.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to thermald in Ubuntu.
https://bugs.launchpad.net/bugs/1775717
Title:
CPU/GPU Fans suddenly go 100% RPM on Asus ROG G752VT
Status in linux package in Ubuntu:
Incomplete
Status in thermald package in Ubuntu:
Confirmed
Bug description:
After upgrading from Ubuntu 16.04 to 18.04, I've noticed that CPU and
GPU fans suddenly go full throttle. It doesn't seem to depend on
temperature, could happen when 32 °C reported, sometimes the laptop
can work for day or two without this issue, but eventually it happens.
The only way to stop fans is to power off the laptop, power on (fans
go 100% at this point again), power off during BIOS splash screen and
power on again. Seems to happen more often after waking up from a
sleep.
Things tried:
Upgrading BIOS to latest available on ASUS site to the date of
writing. No change.
asus-fan kernel module (https://github.com/daringer/asus-fan). Detects
both fans and shows correct speed in /sys/class/hwmon/*/fan{1,2}*, but
does not seem to control it and does not prevent going full throttle.
4.17.0 kernel from Ubuntu mainline builds. Doesn't seem to affect the
issue.
Userspace fan control software (https://github.com/hirschmann/nbfc).
Can control speed of both fans to the point where they go full
throttle, after that has no effect on them.
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: whale 3068 F pulseaudio
/dev/snd/controlC0: whale 3068 F pulseaudio
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 18.04
HibernationDevice: RESUME=UUID=ada9b595-bbf2-40a3-8575-5908492bb969
InstallationDate: Installed on 2014-10-20 (1333 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64+mac
(20140722.2)
MachineType: ASUSTeK COMPUTER INC. G752VT
NonfreeKernelModules: nvidia_modeset nvidia wl
Package: linux (not installed)
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic
root=UUID=f6509d56-6183-464c-90bb-9c3be2c8abdf ro quiet splash
acpi_backlight=vendor vt.handoff=1
ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
RelatedPackageVersions:
linux-restricted-modules-4.15.0-23-generic N/A
linux-backports-modules-4.15.0-23-generic N/A
linux-firmware 1.173.1
Tags: bionic
Uname: Linux 4.15.0-23-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm audio cdrom dip docker lpadmin plugdev sambashare sudo tty
video
_MarkForUpload: True
dmi.bios.date: 06/29/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: G752VT.304
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: G752VT
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: ATN12345678901234567
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrG752VT.304:bd06/29/2017:svnASUSTeKCOMPUTERINC.:pnG752VT:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG752VT:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: G
dmi.product.name: G752VT
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/1775717/+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 1881214] Re: syslog and kern.log grow endlessly - related to Intel wifi?
same here, on two machines; one with 02:00.0 Network controller: Intel Corporation Dual Band Wireless-AC 3168NGW [Stone Peak] (rev 10) and the other with: 08:00.0 Network controller: Intel Corporation Wireless 8260 (rev 3a) the syslog is full of messages like this: WARNING: CPU: 0 PID: 172105 at net/mac80211/driver-ops.h:17 drv_sta_state+0x254/0x3f0 [mac80211] i've changed to kernel 5.6.15-050615-generic with no luck, the bug is still happening -- 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/1881214 Title: syslog and kern.log grow endlessly - related to Intel wifi? Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu Mate 20.04, with all supplied kernels up to 5.4.0.33 I occasionally see a message on my screen that disk space is low. I try rebooting since my computer is unresponsive. Normal reboot does not work, sudo reboot does not work. I have to power off the machine using power button. Machine boots but hangs because its trying to repair journal info. I can't see what causes that since I was not using my computer at the time. So with a live session, I can see that syslog and kern.log files have grown to several GB until the drive is full. When using an upstream kernel 5.4.43-050443-generic x86_64, I haven't had any problem so far. edit: not true actually, this happened again using this upstream kernel. Never had this issue with previous Ubuntu versions with the very same hardware configuration, since 16.04. Included: partial syslog and kern.log with the same message repeated over and over. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881214/+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 1881214] Re: syslog and kern.log grow endlessly - related to Intel wifi?
Unlike what I thought or hoped, using an upstream kernel (5.4.43-050443-generic x86_64) is not a workaround. I just had the same issue again. ** Description changed: Ubuntu Mate 20.04, with all supplied kernels up to 5.4.0.33 I occasionally see a message on my screen that disk space is low. I try rebooting since my computer is unresponsive. Normal reboot does not work, sudo reboot does not work. I have to power off the machine using power button. Machine boots but hangs because its trying to repair journal info. I can't see what causes that since I was not using my computer at the time. So with a live session, I can see that syslog and kern.log files have grown to several GB until the drive is full. When using an upstream kernel 5.4.43-050443-generic x86_64, I haven't had any problem so far. - Never had this issue with previous Ubuntu versions with the very same hardware configuration, since 16.04. + edit: not true actually, this happened again using this upstream kernel. + + Never had this issue with previous Ubuntu versions with the very same + hardware configuration, since 16.04. Included: partial syslog and kern.log with the same message repeated over and over. -- 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/1881214 Title: syslog and kern.log grow endlessly - related to Intel wifi? Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu Mate 20.04, with all supplied kernels up to 5.4.0.33 I occasionally see a message on my screen that disk space is low. I try rebooting since my computer is unresponsive. Normal reboot does not work, sudo reboot does not work. I have to power off the machine using power button. Machine boots but hangs because its trying to repair journal info. I can't see what causes that since I was not using my computer at the time. So with a live session, I can see that syslog and kern.log files have grown to several GB until the drive is full. When using an upstream kernel 5.4.43-050443-generic x86_64, I haven't had any problem so far. edit: not true actually, this happened again using this upstream kernel. Never had this issue with previous Ubuntu versions with the very same hardware configuration, since 16.04. Included: partial syslog and kern.log with the same message repeated over and over. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881214/+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 1775717] Re: CPU/GPU Fans suddenly go 100% RPM on Asus ROG G752VT
It seems the fan speed became uncontrolled once the temperature is too
high. Even though it became lower in near future. see attach
** Attachment added: "Screenshot from 2020-05-31 23-45-57.png"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775717/+attachment/5379187/+files/Screenshot%20from%202020-05-31%2023-45-57.png
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to thermald in Ubuntu.
https://bugs.launchpad.net/bugs/1775717
Title:
CPU/GPU Fans suddenly go 100% RPM on Asus ROG G752VT
Status in linux package in Ubuntu:
Incomplete
Status in thermald package in Ubuntu:
Confirmed
Bug description:
After upgrading from Ubuntu 16.04 to 18.04, I've noticed that CPU and
GPU fans suddenly go full throttle. It doesn't seem to depend on
temperature, could happen when 32 °C reported, sometimes the laptop
can work for day or two without this issue, but eventually it happens.
The only way to stop fans is to power off the laptop, power on (fans
go 100% at this point again), power off during BIOS splash screen and
power on again. Seems to happen more often after waking up from a
sleep.
Things tried:
Upgrading BIOS to latest available on ASUS site to the date of
writing. No change.
asus-fan kernel module (https://github.com/daringer/asus-fan). Detects
both fans and shows correct speed in /sys/class/hwmon/*/fan{1,2}*, but
does not seem to control it and does not prevent going full throttle.
4.17.0 kernel from Ubuntu mainline builds. Doesn't seem to affect the
issue.
Userspace fan control software (https://github.com/hirschmann/nbfc).
Can control speed of both fans to the point where they go full
throttle, after that has no effect on them.
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: whale 3068 F pulseaudio
/dev/snd/controlC0: whale 3068 F pulseaudio
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 18.04
HibernationDevice: RESUME=UUID=ada9b595-bbf2-40a3-8575-5908492bb969
InstallationDate: Installed on 2014-10-20 (1333 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64+mac
(20140722.2)
MachineType: ASUSTeK COMPUTER INC. G752VT
NonfreeKernelModules: nvidia_modeset nvidia wl
Package: linux (not installed)
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic
root=UUID=f6509d56-6183-464c-90bb-9c3be2c8abdf ro quiet splash
acpi_backlight=vendor vt.handoff=1
ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
RelatedPackageVersions:
linux-restricted-modules-4.15.0-23-generic N/A
linux-backports-modules-4.15.0-23-generic N/A
linux-firmware 1.173.1
Tags: bionic
Uname: Linux 4.15.0-23-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm audio cdrom dip docker lpadmin plugdev sambashare sudo tty
video
_MarkForUpload: True
dmi.bios.date: 06/29/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: G752VT.304
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: G752VT
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: ATN12345678901234567
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrG752VT.304:bd06/29/2017:svnASUSTeKCOMPUTERINC.:pnG752VT:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG752VT:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: G
dmi.product.name: G752VT
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/1775717/+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 1850439] Re: No sound on ASUS UX534FT
More traces: Transition from speakers to headphones (w/o a microphone, not a headset) while audio is playing on Windows VM. CORB and RIRBWP only, vfio_region_write events filtered to make trace cleaner. ** Attachment added: "trace_spk_to_hp.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850439/+attachment/5379185/+files/trace_spk_to_hp.txt -- 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 1850439] Re: No sound on ASUS UX534FT
More traces: Transition from headphones (w/o a microphone, not a headset) back to the speakers while audio is playing on Windows VM. CORB and RIRBWP only, vfio_region_write events filtered to make trace cleaner. ** Attachment added: "trace_hp_to_spk.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850439/+attachment/5379184/+files/trace_hp_to_spk.txt -- 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 1881505] [NEW] Sound w/SOF driver sporadically fails on Lenovo Carbon X1 gen 7
Public bug reported: Now and then, the notebooks stops producing any sound, and program that try to use sound output freeze for many seconds. There is a repeating sequence on messages in `dmesg`: [116525.402057] sof-audio-pci :00:1f.3: error: ipc timed out for 0x8001 size 120 [116525.402081] sof-audio-pci :00:1f.3: status: fw entered - code 0005 [116525.402338] sof-audio-pci :00:1f.3: error: can't enter idle [116525.402342] sof-audio-pci :00:1f.3: error: trace point 4000 [116525.402346] sof-audio-pci :00:1f.3: error: panic at src/lib/agent.c:50 [116525.402350] sof-audio-pci :00:1f.3: error: DSP Firmware Oops [116525.402356] sof-audio-pci :00:1f.3: EXCCAUSE 0x003f EXCVADDR 0x PS 0x00060925 SAR 0x [116525.402361] sof-audio-pci :00:1f.3: EPC1 0x EPC2 0xbe00d30e EPC3 0x EPC40x [116525.402365] sof-audio-pci :00:1f.3: EPC5 0x EPC6 0x EPC7 0x DEPC0x [116525.402369] sof-audio-pci :00:1f.3: EPS2 0x00060d20 EPS3 0x EPS4 0x EPS50x [116525.402374] sof-audio-pci :00:1f.3: EPS6 0x EPS7 0x INTENABL 0x INTERRU 0x0222 [116525.402378] sof-audio-pci :00:1f.3: stack dump from 0xbe04f5b0 [116525.402385] sof-audio-pci :00:1f.3: 0xbe04f5b0: be00fc00 be04f5e0 be062180 0001 [116525.402391] sof-audio-pci :00:1f.3: 0xbe04f5b4: 0032 [116525.402396] sof-audio-pci :00:1f.3: 0xbe04f5b8: 69cd0100 15655b6c 602aeaf8 93a4 [116525.402401] sof-audio-pci :00:1f.3: 0xbe04f5bc: 93a4 303a3030 [116525.402406] sof-audio-pci :00:1f.3: 0xbe04f5c0: 0078 602aea98 93a4 [116525.402411] sof-audio-pci :00:1f.3: 0xbe04f5c4: 6bdcfb58 93a4 5d006830 93a4 [116525.402416] sof-audio-pci :00:1f.3: 0xbe04f5c8: 6ba37218 93a4 82317aaf bca5 [116525.402421] sof-audio-pci :00:1f.3: 0xbe04f5cc: 6ba37220 93a4 023179f8 bca5 [116525.402446] sof-audio-pci :00:1f.3: error: hda irq intsts 0x intlctl 0xc081 rirb 00 [116525.402450] sof-audio-pci :00:1f.3: error: dsp irq ppsts 0x adspis 0x [116525.402471] sof-audio-pci :00:1f.3: error: host status 0x dsp status 0x mask 0x0003 [116525.402475] sof-audio-pci :00:1f.3: error: waking up any trace sleepers [116525.402481] sof-audio-pci :00:1f.3: error: failed to set dai config for iDisp1 [116525.402486] sof-audio-pci :00:1f.3: ASoC: can't set iDisp1 Pin hw params: -110 [116525.402498] iDisp1: ASoC: hw_params BE failed -110 [116525.402502] HDMI1: ASoC: hw_params BE failed -110 This _might_ be the upstream bug https://github.com/thesofproject/sof/issues/2828 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: crosser 42712 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun May 31 20:40:20 2020 InstallationDate: Installed on 2020-01-02 (149 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190802) MachineType: LENOVO 20QDCTO1WW ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-33-generic root=/dev/mapper/vgubuntu-root 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 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/13/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2HET50W (1.33 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QDCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2HET50W(1.33):bd05/13/2020:svnLENOVO:pn20QDCTO1WW:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QDCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 7th dmi.product.name: 20QDCTO1WW dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th dmi.product.version: ThinkPad X1 Carbon 7th 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/1881505 Title: Sound w/SOF driver sporadically fails on Lenovo Carbon X1 gen 7 Status in linux package in Ubuntu: Confirmed Bug description: Now and then, the notebooks stops
[Kernel-packages] [Bug 1881505] 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/1881505 Title: Sound w/SOF driver sporadically fails on Lenovo Carbon X1 gen 7 Status in linux package in Ubuntu: Confirmed Bug description: Now and then, the notebooks stops producing any sound, and program that try to use sound output freeze for many seconds. There is a repeating sequence on messages in `dmesg`: [116525.402057] sof-audio-pci :00:1f.3: error: ipc timed out for 0x8001 size 120 [116525.402081] sof-audio-pci :00:1f.3: status: fw entered - code 0005 [116525.402338] sof-audio-pci :00:1f.3: error: can't enter idle [116525.402342] sof-audio-pci :00:1f.3: error: trace point 4000 [116525.402346] sof-audio-pci :00:1f.3: error: panic at src/lib/agent.c:50 [116525.402350] sof-audio-pci :00:1f.3: error: DSP Firmware Oops [116525.402356] sof-audio-pci :00:1f.3: EXCCAUSE 0x003f EXCVADDR 0x PS 0x00060925 SAR 0x [116525.402361] sof-audio-pci :00:1f.3: EPC1 0x EPC2 0xbe00d30e EPC3 0x EPC40x [116525.402365] sof-audio-pci :00:1f.3: EPC5 0x EPC6 0x EPC7 0x DEPC0x [116525.402369] sof-audio-pci :00:1f.3: EPS2 0x00060d20 EPS3 0x EPS4 0x EPS50x [116525.402374] sof-audio-pci :00:1f.3: EPS6 0x EPS7 0x INTENABL 0x INTERRU 0x0222 [116525.402378] sof-audio-pci :00:1f.3: stack dump from 0xbe04f5b0 [116525.402385] sof-audio-pci :00:1f.3: 0xbe04f5b0: be00fc00 be04f5e0 be062180 0001 [116525.402391] sof-audio-pci :00:1f.3: 0xbe04f5b4: 0032 [116525.402396] sof-audio-pci :00:1f.3: 0xbe04f5b8: 69cd0100 15655b6c 602aeaf8 93a4 [116525.402401] sof-audio-pci :00:1f.3: 0xbe04f5bc: 93a4 303a3030 [116525.402406] sof-audio-pci :00:1f.3: 0xbe04f5c0: 0078 602aea98 93a4 [116525.402411] sof-audio-pci :00:1f.3: 0xbe04f5c4: 6bdcfb58 93a4 5d006830 93a4 [116525.402416] sof-audio-pci :00:1f.3: 0xbe04f5c8: 6ba37218 93a4 82317aaf bca5 [116525.402421] sof-audio-pci :00:1f.3: 0xbe04f5cc: 6ba37220 93a4 023179f8 bca5 [116525.402446] sof-audio-pci :00:1f.3: error: hda irq intsts 0x intlctl 0xc081 rirb 00 [116525.402450] sof-audio-pci :00:1f.3: error: dsp irq ppsts 0x adspis 0x [116525.402471] sof-audio-pci :00:1f.3: error: host status 0x dsp status 0x mask 0x0003 [116525.402475] sof-audio-pci :00:1f.3: error: waking up any trace sleepers [116525.402481] sof-audio-pci :00:1f.3: error: failed to set dai config for iDisp1 [116525.402486] sof-audio-pci :00:1f.3: ASoC: can't set iDisp1 Pin hw params: -110 [116525.402498] iDisp1: ASoC: hw_params BE failed -110 [116525.402502] HDMI1: ASoC: hw_params BE failed -110 This _might_ be the upstream bug https://github.com/thesofproject/sof/issues/2828 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: crosser 42712 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun May 31 20:40:20 2020 InstallationDate: Installed on 2020-01-02 (149 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190802) MachineType: LENOVO 20QDCTO1WW ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-33-generic root=/dev/mapper/vgubuntu-root 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 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/13/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2HET50W (1.33 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QDCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2HET50W(1.33):bd05/13/2020:svnLENOVO:pn20QDCTO1WW:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QDCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 7th dmi.product.name: 20QDCTO1WW dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th
[Kernel-packages] [Bug 1850439] Re: No sound on ASUS UX534FT
On the negative side: the sound has strange artifacts on speakers. And headphones are not working properly once inserted. If you want to experiment yourself - please use previous traces and the following Python scripts: - annotate trace with verb names for known verbs: https://gist.github.com/s-kostyuk/192ce5d0fc8276652d6568f757291e3a - convert all hda commands from qemu trace to the shell script: https://gist.github.com/s-kostyuk/e33f26f20f609d1dd0911dd56a0c17bc -- 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 1850439] Re: No sound on ASUS UX534FT
This crazy script contains all SET and unknown commands sent from the Windows to the audio, with some commands stripped (using a try-and-check method). And this crazy script allows to enable the speakers somehow!!! Now here is the question: Can somebody filter excess commands and find the bare minimum needed to enable speakers? ** Attachment added: "A crazy script that allows to enable the speakers" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850439/+attachment/5379134/+files/vm_trace_qemu_raw_after_reboot.win10.corb_rsp_annotated_set_only.txt.sh -- 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 1848496] Re: [zfs-root] "device-mapper: reload ioctl on osprober-linux-sdaX failed: Device or resource busy" against devices owned by ZFS
@fermulator at the moment this is bug breaks dualboot anyway, since it will not probe my Windows os before failing and stopping. So I have to resort to using f12 to select the disk. I suppose it will be worse for people with dual boot on one drive, but they will not be able to install ZoL as easily via the installer. -- 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/1848496 Title: [zfs-root] "device-mapper: reload ioctl on osprober-linux-sdaX failed: Device or resource busy" against devices owned by ZFS Status in os-prober package in Ubuntu: Confirmed Status in zfs-linux package in Ubuntu: Confirmed Bug description: On a 19.10 (pre-release, 20191016 daily) zfs installation, running 'os-prober' (as 'update-grub' does by default) triggers the following error message: x@x:~$ sudo os-prober; echo $? device-mapper: reload ioctl on osprober-linux-sda5 failed: Device or resource busy Command failed. 0 x@x:~$ The exit code is 0, so update-grub does not fail as a result. Partitions on the only available storage (automatically setup by installer): x@x:~$ sudo fdisk /dev/sda -l Disk /dev/sda: 10 GiB, 10737418240 bytes, 20971520 sectors Disk model: VBOX HARDDISK Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt Disk identifier: AB7BECFB-5946-48B2-9C59-D2B1261E29A5 Device Start End Sectors Size Type /dev/sda1 2048 1050623 1048576 512M EFI System /dev/sda2 1050624 1153023 102400 50M Linux filesystem /dev/sda3 1153024 2070527 917504 448M Linux swap /dev/sda4 2070528 6264831 41943042G Solaris boot /dev/sda5 6264832 20971486 147066557G Solaris root x@x:~$ ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: os-prober 1.74ubuntu2 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Oct 17 14:19:59 2019 InstallationDate: Installed on 2019-10-17 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191016.5) SourcePackage: os-prober UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/os-prober/+bug/1848496/+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 1848496] Re: [zfs-root] "device-mapper: reload ioctl on osprober-linux-sdaX failed: Device or resource busy" against devices owned by ZFS
@fermulator Thanks will keep that in Mind But I am doing Single Boot only. -- 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/1848496 Title: [zfs-root] "device-mapper: reload ioctl on osprober-linux-sdaX failed: Device or resource busy" against devices owned by ZFS Status in os-prober package in Ubuntu: Confirmed Status in zfs-linux package in Ubuntu: Confirmed Bug description: On a 19.10 (pre-release, 20191016 daily) zfs installation, running 'os-prober' (as 'update-grub' does by default) triggers the following error message: x@x:~$ sudo os-prober; echo $? device-mapper: reload ioctl on osprober-linux-sda5 failed: Device or resource busy Command failed. 0 x@x:~$ The exit code is 0, so update-grub does not fail as a result. Partitions on the only available storage (automatically setup by installer): x@x:~$ sudo fdisk /dev/sda -l Disk /dev/sda: 10 GiB, 10737418240 bytes, 20971520 sectors Disk model: VBOX HARDDISK Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt Disk identifier: AB7BECFB-5946-48B2-9C59-D2B1261E29A5 Device Start End Sectors Size Type /dev/sda1 2048 1050623 1048576 512M EFI System /dev/sda2 1050624 1153023 102400 50M Linux filesystem /dev/sda3 1153024 2070527 917504 448M Linux swap /dev/sda4 2070528 6264831 41943042G Solaris boot /dev/sda5 6264832 20971486 147066557G Solaris root x@x:~$ ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: os-prober 1.74ubuntu2 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Oct 17 14:19:59 2019 InstallationDate: Installed on 2019-10-17 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191016.5) SourcePackage: os-prober UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/os-prober/+bug/1848496/+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 1878726] Re: Live USB Installer not working Samsung Notebook 9 Pro 15"
I have same laptop with same problem on 20.04. Works great on 19.10. Every once in awhile I can get it to systemd.unit=emergency.target. But it hangs soon after if even doing an "lsmod". -- 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/1878726 Title: Live USB Installer not working Samsung Notebook 9 Pro 15" Status in linux package in Ubuntu: Incomplete Bug description: Live USB made from ubuntu-20.04-desktop-amd64 fails to boot. System hangs with watchdog: BUG: soft lockup - CPU# and rcu: INFO: rcu_sched self-detected stall on CPU. System specs: Intel(R) i7-7500U running AMD discrete graphics Have tested the Live USB on other systems with no problems, appears to be hardware related with the Samsung Notebook 9 Pro and other systems (Dell, etc.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1878726/+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 1872001] Re: 5.3.0-46-generic - i915 - frequent GPU hangs / resets rcs0
Hi, with 5.3.0-53 generic, i've encountered 2 errors that have frozen the system during 2 or 3 minutes. After this error, the system came back to normal. These 2 errors has been observed with Kodi at the "beginning" of the session (in the firts minutes after a boot), and only once per boot. I'm still testing. Here is the syslog when an error occurs: May 30 23:30:57 hystKodi kernel: [ 150.872582] i915 :00:10.0: GPU HANG: ecode 9:0:0x, hang on rcs0 May 30 23:30:57 hystKodi kernel: [ 150.873591] i915 :00:10.0: Resetting rcs0 for hang on rcs0 May 30 23:31:05 hystKodi kernel: [ 158.851005] i915 :00:10.0: Resetting rcs0 for hang on rcs0 May 30 23:31:13 hystKodi kernel: [ 166.850875] i915 :00:10.0: Resetting rcs0 for hang on rcs0 May 30 23:31:21 hystKodi kernel: [ 174.850907] i915 :00:10.0: Resetting rcs0 for hang on rcs0 May 30 23:31:23 hystKodi kernel: [ 176.866911] i915 :00:10.0: Resetting rcs0 for hang on rcs0 May 30 23:31:31 hystKodi kernel: [ 184.866958] i915 :00:10.0: Resetting rcs0 for hang on rcs0 May 30 23:31:39 hystKodi kernel: [ 192.866879] i915 :00:10.0: Resetting rcs0 for hang on rcs0 May 30 23:31:41 hystKodi kernel: [ 194.850880] i915 :00:10.0: Resetting rcs0 for hang on rcs0 May 30 23:31:43 hystKodi kernel: [ 196.866960] i915 :00:10.0: Resetting rcs0 for hang on rcs0 May 30 23:31:45 hystKodi kernel: [ 198.850929] i915 :00:10.0: Resetting rcs0 for hang on rcs0 May 30 23:31:53 hystKodi kernel: [ 206.850890] i915 :00:10.0: Resetting rcs0 for hang on rcs0 May 30 23:31:55 hystKodi kernel: [ 208.866949] i915 :00:10.0: Resetting rcs0 for hang on rcs0 May 30 23:31:57 hystKodi kernel: [ 210.850916] i915 :00:10.0: Resetting rcs0 for hang on rcs0 May 30 23:31:59 hystKodi kernel: [ 212.866937] i915 :00:10.0: Resetting rcs0 for hang on rcs0 May 30 23:32:01 hystKodi kernel: [ 214.850973] i915 :00:10.0: Resetting rcs0 for hang on rcs0 May 30 23:32:03 hystKodi kernel: [ 216.866919] i915 :00:10.0: Resetting rcs0 for hang on rcs0 May 30 23:32:05 hystKodi kernel: [ 218.850958] i915 :00:10.0: Resetting rcs0 for hang on rcs0 May 30 23:32:07 hystKodi kernel: [ 220.866897] i915 :00:10.0: Resetting rcs0 for hang on rcs0 May 30 23:32:09 hystKodi kernel: [ 222.850968] i915 :00:10.0: Resetting rcs0 for hang on rcs0 May 30 23:32:11 hystKodi kernel: [ 224.866970] i915 :00:10.0: Resetting rcs0 for hang on rcs0 May 30 23:32:13 hystKodi kernel: [ 226.850920] i915 :00:10.0: Resetting rcs0 for hang on rcs0 May 30 23:32:15 hystKodi kernel: [ 228.866923] i915 :00:10.0: Resetting rcs0 for hang on rcs0 May 30 23:32:17 hystKodi kernel: [ 230.850905] i915 :00:10.0: Resetting rcs0 for hang on rcs0 May 30 23:32:19 hystKodi kernel: [ 232.866958] i915 :00:10.0: Resetting rcs0 for hang on rcs0 May 30 23:32:21 hystKodi kernel: [ 234.850911] i915 :00:10.0: Resetting rcs0 for hang on rcs0 May 30 23:32:23 hystKodi kernel: [ 236.866940] i915 :00:10.0: Resetting rcs0 for hang on rcs0 May 30 23:32:25 hystKodi kernel: [ 238.850895] i915 :00:10.0: Resetting rcs0 for hang on rcs0 May 30 23:32:27 hystKodi kernel: [ 240.866943] i915 :00:10.0: Resetting rcs0 for hang on rcs0 May 30 23:32:29 hystKodi kernel: [ 242.850947] i915 :00:10.0: Resetting rcs0 for hang on rcs0 May 30 23:32:31 hystKodi kernel: [ 244.866933] i915 :00:10.0: Resetting rcs0 for hang on rcs0 May 30 23:32:33 hystKodi kernel: [ 246.850946] i915 :00:10.0: Resetting rcs0 for hang on rcs0 May 30 23:32:35 hystKodi kernel: [ 248.866978] i915 :00:10.0: Resetting rcs0 for hang on rcs0 May 30 23:32:37 hystKodi kernel: [ 250.850881] i915 :00:10.0: Resetting rcs0 for hang on rcs0 May 30 23:32:39 hystKodi kernel: [ 252.866942] i915 :00:10.0: Resetting rcs0 for hang on rcs0 May 30 23:32:41 hystKodi kernel: [ 254.850872] i915 :00:10.0: Resetting rcs0 for hang on rcs0 May 30 23:32:43 hystKodi kernel: [ 256.866970] i915 :00:10.0: Resetting rcs0 for hang on rcs0 May 30 23:32:45 hystKodi kernel: [ 258.850881] i915 :00:10.0: Resetting rcs0 for hang on rcs0 May 30 23:32:47 hystKodi kernel: [ 260.866945] i915 :00:10.0: Resetting rcs0 for hang on rcs0 May 30 23:32:49 hystKodi kernel: [ 262.849868] i915 :00:10.0: GPU recovery timed out, cancelling all in-flight rendering. May 30 23:32:49 hystKodi kernel: [ 262.851192] i915 :00:10.0: Resetting chip for hang on rcs0 -- 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/1872001 Title: 5.3.0-46-generic - i915 - frequent GPU hangs / resets rcs0 Status in linux package in Ubuntu: Confirmed Status in linux source package in Eoan: Fix Released Bug description: Hi, Since update to HWE kernel 5.3.0-46-generic I am experiencing frequent (every couple of minutes) GPU hangs and reset manifesting as
[Kernel-packages] [Bug 1850439] Re: No sound on ASUS UX534FT
Uploaded more logs from VMs: - notebook power cycle - start Ubuntu VM (live CD) - no sound in VM - start Windows VM - disable device in Windows VM - shutdown Windows VM - start Ubuntu VM (live CD) - sound is present in VM ** Attachment added: "qemu_pci_rtk_audio_trace_from_ubuntu2004_after_windows_vm.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850439/+attachment/5379056/+files/vm_trace_qemu_raw.ubuntu20_after_windows.txt -- 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 1850439] Re: No sound on ASUS UX534FT
** Attachment added: "qemu_pci_rtk_audio_trace_from_ubuntu2004_after_power_cycle.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850439/+attachment/5379055/+files/vm_trace_qemu_raw.ubuntu20_clean_boot.txt -- 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 1850439] Re: No sound on ASUS UX534FT
** Attachment added: "qemu_pci_rtk_audio_trace_from_windows10_after_power_cycle.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850439/+attachment/5379054/+files/vm_trace_qemu_raw.win10_clean_boot.txt -- 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 1853044] Re: 5.3.0-23-generic causes fans to spin when idle
This happens to me on 5.4.0-33-generic (focal). Do you want me to test these 5.3 kernels? -- 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/1853044 Title: 5.3.0-23-generic causes fans to spin when idle Status in linux package in Ubuntu: Fix Released Status in linux source package in Eoan: Fix Released Status in linux source package in Focal: Fix Released Bug description: SRU Justification Impact: "drm/i915/gen8+: Add RC6 CTX corruption WA" makes it effectively impossible to enter RC6 for some Intel GPUs when a display server is running. This results in increased energy usage and temperature. Fix: Upstream has changed too much to make the fixes there applicable, but Chris Wilson has provided a patch for 5.3, here: https://gitlab.freedesktop.org/drm/intel/issues/614#note_366057 Test Case: See test results below. On an affected machine powertop will show increased RC6 usage on an idle desktop after the patch, and other symptoms of excessive power use should also subside. Regression Potential: The 5.3 patch is pretty straightforward, and only adds running of an existing delayed worker to retire GPU requests. No regressions have been reported in testing so far. --- After upgrading to 5.3.0-23-generic the fans in my machine don't stop running. They always sound like something is utilizing CPU - even with no applications running after boot. If I boot back to 5.3.0-19-generic it's fine. My microcode version is reported as 0xd4 and iucode-tool reports: iucode-tool: system has processor(s) with signature 0x000506e3 Let me know if you need anything else. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-23-generic 5.3.0-23.25 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: dean 2898 F pulseaudio /dev/snd/pcmC2D0p: dean 2898 F...m pulseaudio /dev/snd/controlC0: dean 2898 F pulseaudio /dev/snd/controlC1: dean 2898 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Nov 18 13:03:34 2019 HibernationDevice: RESUME=UUID=55a42c82-50bf-4e75-a133-dbd3aa93611b InstallationDate: Installed on 2018-07-24 (482 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180724) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-23-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-23-generic N/A linux-backports-modules-5.3.0-23-generic N/A linux-firmware1.183.2 SourcePackage: linux UpgradeStatus: Upgraded to eoan on 2019-07-19 (121 days ago) dmi.bios.date: 05/16/2018 dmi.bios.vendor: Intel Corp. dmi.bios.version: KYSKLi70.86A.0055.2018.0516.1629 dmi.board.name: NUC6i7KYB dmi.board.vendor: Intel Corporation dmi.board.version: H90766-406 dmi.chassis.type: 3 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnIntelCorp.:bvrKYSKLi70.86A.0055.2018.0516.1629:bd05/16/2018:svn:pn:pvr:rvnIntelCorporation:rnNUC6i7KYB:rvrH90766-406:cvnIntelCorporation:ct3:cvr1.0: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853044/+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 1881319] Re: Touchpad not recognized (probably falsely as touch panel)
Updated kernel to mainline 5.6.15-050615-generic. Helps with other issues but touchpad still not responsive. At least error messages in dmesg are gone. -- 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/1881319 Title: Touchpad not recognized (probably falsely as touch panel) Status in linux package in Ubuntu: Confirmed Bug description: Touchpad isn't reacting at all 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/controlC1: andreas1223 F pulseaudio /dev/snd/controlC0: andreas1223 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: Budgie:GNOME Date: Fri May 29 18:05:01 2020 InstallationDate: Installed on 2020-05-29 (0 days ago) InstallationMedia: Ubuntu-Budgie 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81YQ ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=4197e5c6-f903-46c3-bc16-3013c5650810 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 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/25/2020 dmi.bios.vendor: LENOVO dmi.bios.version: E7CN24WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: No DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 5 15ARE05 dmi.modalias: dmi:bvnLENOVO:bvrE7CN24WW:bd03/25/2020:svnLENOVO:pn81YQ:pvrIdeaPad515ARE05:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrIdeaPad515ARE05: dmi.product.family: IdeaPad 5 15ARE05 dmi.product.name: 81YQ dmi.product.sku: LENOVO_MT_81YQ_BU_idea_FM_IdeaPad 5 15ARE05 dmi.product.version: IdeaPad 5 15ARE05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881319/+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 1880334] Re: Cloud-init causes potentially huge boot delays with 4.15 kernels Edit
** Also affects: cloud-init (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1880334
Title:
Cloud-init causes potentially huge boot delays with 4.15 kernels Edit
Status in cloud-init package in Ubuntu:
New
Status in linux package in Ubuntu:
Incomplete
Bug description:
portion of bug report for bionic:
Newer 4.15 kernels contain the following fix for CVE-2018-1108:
43838a23a05fb ("random: fix crng_ready() test")
This causes cloud-init to stall for a potentially long time during
boot (waiting for entropy I presume). Google reported boot delays of
75 minutes.
I've tracked this down to the following import in templater.py which causes
the delay:
from jinja2 import Template as JTemplate
Which is called when cc_update_etc_hosts is imported.
NOTE: I'm experiencing this with focal repeatedly - just hangs
forever!
ubunutu 20.04 server - live
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1880334/+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 1881214] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed ** 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/1881214 Title: syslog and kern.log grow endlessly - related to Intel wifi? Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu Mate 20.04, with all supplied kernels up to 5.4.0.33 I occasionally see a message on my screen that disk space is low. I try rebooting since my computer is unresponsive. Normal reboot does not work, sudo reboot does not work. I have to power off the machine using power button. Machine boots but hangs because its trying to repair journal info. I can't see what causes that since I was not using my computer at the time. So with a live session, I can see that syslog and kern.log files have grown to several GB until the drive is full. When using an upstream kernel 5.4.43-050443-generic x86_64, I haven't had any problem so far. Never had this issue with previous Ubuntu versions with the very same hardware configuration, since 16.04. Included: partial syslog and kern.log with the same message repeated over and over. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881214/+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 1860806] Re: Ubuntu 18.04 and 19.04 new ethernet problem
@JamesH, my only involvement in this bug report was to inform you that you were using an "End of Line" Ubuntu release and to ensure that the report was assigned to the correct project/package/Ubuntu release so that others who have a much better knowledge and experience of such issues could look at your report. Anyone looking at the bug reports that you raise may not have the level of expertise that can actually fix issues. Several people may look at or change the report before it reaches someone who might be able to suggest a fix. Comments such as yours will only drive Ubuntu users/volunteers such as myself away from helping to assign bug reports to users and teams that can actually help. As you have not replied to Kai-Heng's request in comment #21 I'm closing this report as "Invalid". If you still have an issue with the problem that you reported then perhaps issuing the following command in a terminal window ubuntu-bug linux when your connection is working would probably be the best way forward. ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid -- 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/1860806 Title: Ubuntu 18.04 and 19.04 new ethernet problem Status in linux package in Ubuntu: Invalid Status in network-manager package in Ubuntu: Invalid Bug description: Ubuntu 19.04 (64 bit) on OptiPlex-7010 On every power on I have no wired Ethernet connection or even an icon to enable it. After a restart (soft boot) it comes back again. This appears to be different from another bug reported which states that the Ethernet cable has to be unplugged during power on. In my issue, I can leave the Ethernet cable plugged in and it works fine. It just doesn't work during first power on boot. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2020-01-26 (2 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IpRoute: default via 192.168.1.1 dev eno1 proto dhcp metric 100 169.254.0.0/16 dev eno1 scope link metric 1000 192.168.1.0/24 dev eno1 proto kernel scope link src 192.168.1.156 metric 100 IwConfig: lono wireless extensions. eno1 no wireless extensions. NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true Package: network-manager 1.10.6-2ubuntu1.2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18 RfKill: Tags: bionic Uname: Linux 4.15.0-74-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE Wired connection 1 bea41631-df6c-3de0-ac4c-7606d1313303 ethernet 1580229876 Tue 28 Jan 2020 08:44:36 AM PST yes 4294966297 no/org/freedesktop/NetworkManager/Settings/1 yes eno1activated /org/freedesktop/NetworkManager/ActiveConnection/1 -- nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH eno1ethernet connected /org/freedesktop/NetworkManager/Devices/2 Wired connection 1 bea41631-df6c-3de0-ac4c-7606d1313303 /org/freedesktop/NetworkManager/ActiveConnection/1 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.6 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860806/+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 1881214] Re: syslog and kern.log grow endlessly - related to Intel wifi?
** 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/1881214 Title: syslog and kern.log grow endlessly - related to Intel wifi? Status in linux package in Ubuntu: New Bug description: Ubuntu Mate 20.04, with all supplied kernels up to 5.4.0.33 I occasionally see a message on my screen that disk space is low. I try rebooting since my computer is unresponsive. Normal reboot does not work, sudo reboot does not work. I have to power off the machine using power button. Machine boots but hangs because its trying to repair journal info. I can't see what causes that since I was not using my computer at the time. So with a live session, I can see that syslog and kern.log files have grown to several GB until the drive is full. When using an upstream kernel 5.4.43-050443-generic x86_64, I haven't had any problem so far. Never had this issue with previous Ubuntu versions with the very same hardware configuration, since 16.04. Included: partial syslog and kern.log with the same message repeated over and over. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881214/+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 1881214] [NEW] syslog and kern.log grow endlessly - related to Intel wifi?
You have been subscribed to a public bug: Ubuntu Mate 20.04, with all supplied kernels up to 5.4.0.33 I occasionally see a message on my screen that disk space is low. I try rebooting since my computer is unresponsive. Normal reboot does not work, sudo reboot does not work. I have to power off the machine using power button. Machine boots but hangs because its trying to repair journal info. I can't see what causes that since I was not using my computer at the time. So with a live session, I can see that syslog and kern.log files have grown to several GB until the drive is full. When using an upstream kernel 5.4.43-050443-generic x86_64, I haven't had any problem so far. Never had this issue with previous Ubuntu versions with the very same hardware configuration, since 16.04. Included: partial syslog and kern.log with the same message repeated over and over. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- syslog and kern.log grow endlessly - related to Intel wifi? https://bugs.launchpad.net/bugs/1881214 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 1877889] Re: Intermittent hangs on boot Ubuntu 20.04 on Lenovo E595
So far so good with me using the standard 5.4 kernel and the nomodeset parameter. I wonder if the freezes during usage that viperomega experiences might be unrelated to the hang on boot issue (that we both saw without nomodeset). -- 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/1877889 Title: Intermittent hangs on boot Ubuntu 20.04 on Lenovo E595 Status in linux package in Ubuntu: Confirmed Bug description: Hello, I see occasional hangs on boot. The hangs occur after entering the LUKS decryption password for the root filesystem, and before the login screen is displayed. The "/boot" filesystem is not encrypted, so the initramfs is loading fine etc. The hangs are intermittent. Sometimes I don't see a hang for 10+ boots in a row, and sometimes I'll get a hang 5 times in a row. When the hang occurs the boot splash screen is visible (not the login screen). The system is still responsive to SysRq keys, so I can somewhat safely issue S+U+S+B sequence to try booting again without corrupting much. I have tried removing the "quiet splash" kernel parameters that are enabled by default on Ubuntu desktop to see if any interesting messages occur that way. So far however I have not experienced a hang with "quiet splash" removed. This system is a Lenovo E595 (Ryzen 3500U) with the latest BIOS from Lenovo installed (v1.16), running Ubuntu 20.04 desktop. I am submitting this bug using `ubuntu-bug linux-image-generic`, but I don't know for sure if this is a kernel issue or something else. I suspect my bug might be the same as this one already reported ( https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873594 ), but I'm filing my own anyway as a means to capture more details of my system. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-generic 5.4.0.29.34 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/controlC1: paul 2507 F pulseaudio /dev/snd/controlC0: paul 2507 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun May 10 20:09:53 2020 MachineType: LENOVO 20NFCTO1WW ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-29-generic root=UUID=f466d4ea-c251-4721-b071-bd70c82f00e1 ro rootflags=subvol=@ splash quiet 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-04-24 (15 days ago) dmi.bios.date: 03/30/2020 dmi.bios.vendor: LENOVO dmi.bios.version: R11ET36W (1.16 ) dmi.board.asset.tag: Not Available dmi.board.name: 20NFCTO1WW 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:bvrR11ET36W(1.16):bd03/30/2020:svnLENOVO:pn20NFCTO1WW:pvrThinkPadE595:rvnLENOVO:rn20NFCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad E595 dmi.product.name: 20NFCTO1WW dmi.product.sku: LENOVO_MT_20NF_BU_Think_FM_ThinkPad E595 dmi.product.version: ThinkPad E595 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1877889/+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 1855188] Re: Switching user while using VMware Workstation Player with vmware additions crashes guest
same here. XFCE's the culprit. XFCE has weird bug with returning from sleep (suspend) and it breaks the nvidia driver. i have a resolution issue after screen is locked (drops to 800x600). So apparently it also applies to automatic lock screen. When I log back in the resolution changeds back to normal and this is where VMware fails. a lot about it on google. https://forums.developer.nvidia.com/t/solved-resume-from-suspend-not-working-with-980-ti-drivers-352-370-kernels-3-16-4-4/41631 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-435 in Ubuntu. https://bugs.launchpad.net/bugs/1855188 Title: Switching user while using VMware Workstation Player with vmware additions crashes guest Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Bug description: I'm aware that VMware Workstation Player isn't supported by Ubuntu (or VMware if you use the free version) but this seems to be related to the other Nvidia binary driver bugs around switching user. Using vmware additions for a Windows guest with the binary Nvidia drivers gives you accerated OpenGL 3.3 capability that plenty of programs need on the guest. But if you switch user, the virtual machine crashes: "VMware Player unrecoverable error: (svga) GLRenderer: GLFBOCreateFBO: FBO assembly failed! status = 0x8CDD A log file is available in "/home/user/vmware/Windows 10 x64/vmware.log". You can request support. To collect data to submit to VMware technical support, run "vm-support". We will respond on the basis of your support entitlement." vmware.log file attached. Ubuntu MATE 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-435/+bug/1855188/+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 1879704] Re: [UBUNTU 20.04] s390x/pci: implement linking between PF and VF for multifunction devices
Test package(s) for s390x available at this PPA:
https://launchpad.net/~fheimes/+archive/ubuntu/lp1879704 |
ppa:fheimes/lp1879704
--
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/1879704
Title:
[UBUNTU 20.04] s390x/pci: implement linking between PF and VF for
multifunction devices
Status in Ubuntu on IBM z Systems:
Triaged
Status in linux package in Ubuntu:
Triaged
Bug description:
SRU Justification:
==
[Impact]
* It's currently not possible on s390x to verify the relationships
between PFs and VFs of network interfaces (neither natively nor in
libvirt).
* So s390x currently behaves differently here compared to other
architectures, but but shouldn't, since this is needed for proper
management.
* On top the creation of not only the sysfs, but also the in-kernel
link (struct pci_dev->physfn) allows the use of a common code path for
disabling/shutdown of PFs.
* This code path is right now fenced off by the struct
pci_dev->no_vf_scan flag of which s390x is currently the only user.
* This allows to gracefully and orderly shutdown VFs associated with a
PF as triggered by '/sys/bus/pci/devices//sriov_numvfs'
* Previously this could leave the card in an unresponsive error state.
[Fix]
* a1ceea67f2e5b73cebd456e7fb463b3052bc6344 a1ceea67f2e5 "PCI/IOV:
Introduce pci_iov_sysfs_link() function"
* e5794cf1a270d813a5b9373a6876487d4d154195 e5794cf1a270 "s390/pci:
create links between PFs and VFs"
[Test Case]
* Setup an s390x LPAR with at least one SR-IOV card and assign PF and
VFs to that system.
* Determine if a device is a virtual function: for other architectures
this is currently available in the file 'physfn' which is a link to
the parent PF's device.
* Determine virtual functions of a physical function: for other
architectures this is currently available as 'virtfn{index}' links
under the PF device's directory.
* Determine the physical function of a virtual function: on x86 this
is currently available in the file 'physfn' which is a link to the
parent PF.
* This verification needs to be done by IBM on a system with SR-IOV
(PCI-based) hardware.
[Regression Potential]
* There is a certain regression risk with having code changes in the
PCI/IOV space.
* Especially because this (one of the two patches) touches common
code.
* The changes in pci.h are very minimal, and the iov.c changes are
traceable, too. Everything else is s390x specific.
* Nevertheless, it could be that PCI hardware get harmed, here
especially (SR-)IOV hardware.
* The patches got cross-company verified (IBM and Google).
* They were brought upstream and are currently tagged with 20200521,
and are planned to be included in 5.8.
[Other]
* Since the fix/patch is planned to be included in kernel v5.8, it
will later automatically land in groovy.
* But because groovy is not there yet (5.8 is not yet out), this SRU
request is for focal and groovy.
* This SRU depends on the SRU from LP 1874056, and this has already two ACKs.
So LP 1874056 needs to be applied before this one!
__
As with other architectures, we must be able on s390x to verify the
following relationships between PFs and VFs for proper management
(including by libvirt) of network interfaces:
1. Determine if a device is a virtual function: for other architectures this
is currently available in the file `physfn` which is a link to the parent PF's
device.
2. Determine virtual functions of a physical function: for other
architectures this is currently available as `virtfn{index}` links under the PF
device's directory.
3. Determine the physical function of a virtual function: on x86 this is
currently available in the file `physfn` which is a link to the parent PF
More details for the already existing parameters mentioned above can
be found here: https://www.kernel.org/doc/Documentation/ABI/testing
/sysfs-bus-pci
Moreover creating not just the sysfs but also the in-kernel link
(struct pci_dev->physfn) also allows us to use the common code path
for disabling/shutdown of PFs.
This code path is currently fenced off by the
struct pci_dev->no_vf_scan flag of which s390 is currently the only user.
This in turn allows for a graceful and orderly shutdown of VFs
associated with a VF as triggered by:
echo 0 > /sys/bus/pci/devices//sriov_numvfs
Previously this could leave the card in an unresponsive error state.
The patches for this have been discussed and Acked-by the
responsible upstream maintainer here:
[RFC 0/2] Enable PF-VF linking with pdev->no_vf_scan (s390)
https://lore.kernel.org/linux-pci/20200506154139.90609-1-schne...@linux.ibm.com/
[RFC 1/2] PCI/IOV: Introduce pci_iov_sysfs_link() function
[Kernel-packages] [Bug 1861610] Re: 'Elan touchpad' not detected on 'Lenovo ThinkBook 15 IIL'
Hi vicamo, I've updated my kernel to 5.4.0-34.38 and tried booting off of that. The bug persists, however. What steps can I take from here? Many thanks for your effort. -- 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/1861610 Title: 'Elan touchpad' not detected on 'Lenovo ThinkBook 15 IIL' Status in linux package in Ubuntu: Confirmed 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 Committed 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 Committed Status in linux-oem-5.6 source package in Eoan: Invalid Status in linux-oem-osp1 source package in Eoan: Confirmed Status in linux source package in Focal: Fix Committed 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 1879973] Re: There is no sound from the built-in speakers and does not see the built-in microphone
I had to downgrade to Ubuntu 18.04, so I cannot check it. -- 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/1879973 Title: There is no sound from the built-in speakers and does not see the built-in microphone Status in linux package in Ubuntu: Confirmed Bug description: After update my Inspiron 5490 from Ubuntu 18.04 to 20.04 system see only "Dummy Sound". I updated kernel to 5.6.13-050613-lowlatency, reinstall pulseaudio, add "options snd-hda-intel dmic_detect=0" to /etc/modprobe.d/alsa- base.con, add "blacklist snd_soc_skl" to /etc/modprobe.d/blacklist.conf. I applied the solution from this source: https://bugs.launchpad.net/ubuntu/+source/alsa- driver/+bug/1876238. I still have this problem. Audio: Device-1: Intel driver: sof-audio-pci Sound Server: ALSA v: k5.6.13-050613-lowlatency $ aplay -l List of PLAYBACK Hardware Devices card 0: sofhdadsp [sof-hda-dsp], device 0: HDA Analog (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: sofhdadsp [sof-hda-dsp], device 1: HDA Digital (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: sofhdadsp [sof-hda-dsp], device 3: HDMI1 (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: sofhdadsp [sof-hda-dsp], device 4: HDMI2 (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: sofhdadsp [sof-hda-dsp], device 5: HDMI3 (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: evince 3.36.0-2 Uname: Linux 5.6.13-050613-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu May 21 17:18:36 2020 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1+X00 InstallationDate: Installed on 2020-01-31 (111 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 SourcePackage: evince UpgradeStatus: Upgraded to focal on 2020-05-18 (2 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1+X00 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-01-31 (113 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) Tags: focal Uname: Linux 5.6.13-050613-lowlatency x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D5p', '/dev/snd/pcmC0D4p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D7c', '/dev/snd/pcmC0D6c', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1+X00 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-01-31 (113 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0bda:5538 Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 003: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 5490 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=4b1d1189-110f-4f43-a4ad-eaf0b866e9c4 ro mem_sleep_default=deep quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 RelatedPackageVersions: linux-restricted-modules-5.4.0-33-generic N/A
[Kernel-packages] [Bug 1861294] Re: Gpu watchdog segfault and video+kbd+mouse freeze on optiplex 7060 intel gpu
It seems it's related to kernel version. Latest kernel-5.6.14-300 crashed (at least) daily. Booting kernel-5.0.9-301 helps a lot - no crash for 2 days. Before upgrade I used kernel-5.3.11-100 for 5 months and it was stable with no GpuWatchdog segfault in chrome errors at all. -- 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/1861294 Title: Gpu watchdog segfault and video+kbd+mouse freeze on optiplex 7060 intel gpu Status in linux package in Ubuntu: Incomplete Bug description: Running up-to-date Ubuntu-18.04.3 with kernel 5.3.0-26 on a Dell Optiplex 7060 with an i7-8700 CPU and Intel UHD Graphics 630 (Coffeelake 3x8 GT2). I had chrome, slack and vmware-player running in Gnome. While doing some git clone, screen+mouse+keyboard froze for 2 minutes after which xorg and everything else recovered. I saw this in dmesg: kernel: show_signal_msg: 2 callbacks suppressed kernel: GpuWatchdog[20399]: segfault at 0 ip 556fd1665ded sp 7efbf17e46c0 error 6 in chrome[556fcd72a000+7171000] kernel: Code: 48 c1 c9 03 48 81 f9 af 00 00 00 0f 87 c9 00 00 00 48 8d 15 a9 5a 9c fb f6 04 11 20 0f 84 b8 00 00 00 be 01 00 00 00 ff 50 30 04 25 00 00 00 00 37 13 00 00 c6 05 c1 6d kernel: nvme nvme0: I/O 202 QID 6 timeout, aborting kernel: nvme nvme0: I/O 203 QID 6 timeout, aborting kernel: nvme nvme0: I/O 204 QID 6 timeout, aborting kernel: nvme nvme0: I/O 205 QID 6 timeout, aborting kernel: nvme nvme0: Abort status: 0x0 kernel: nvme nvme0: Abort status: 0x0 kernel: nvme nvme0: Abort status: 0x0 kernel: nvme nvme0: Abort status: 0x0 kernel: nvme nvme0: I/O 202 QID 6 timeout, reset controller kernel: nvme nvme0: 12/0/0 default/read/poll queues While writing this bug report, the system froze again, and this time it didn't recover. After a cold reset I didn't see any other GpuWatchdog messages in journalctl. Ubuntu applied a BIOS firmware update before the first freeze, so my BIOS was updated as part of the cold reset I did. Not sure if this is relevant to reproducing the freeze. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861294/+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 1827466] Re: Display corrupted on resume from suspend
*** This bug is a duplicate of bug 1809407 *** https://bugs.launchpad.net/bugs/1809407 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-418 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-418 in Ubuntu. https://bugs.launchpad.net/bugs/1827466 Title: Display corrupted on resume from suspend Status in gnome-shell package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-418 package in Ubuntu: Confirmed Bug description: Ubuntu Desktop EE On resume from suspend the background is corrupted both in the screen lock and on the gnome shell session. Screenshot attached. Reloading the shell fixes the issue. 01:00.0 3D controller: NVIDIA Corporation GP108M [GeForce MX150] (rev a1) Subsystem: Dell GP108M [GeForce MX150] Flags: bus master, fast devsel, latency 0, IRQ 141 Memory at d200 (32-bit, non-prefetchable) [size=16M] Memory at c000 (64-bit, prefetchable) [size=256M] Memory at d000 (64-bit, prefetchable) [size=32M] I/O ports at e000 [size=128] [virtual] Expansion ROM at d300 [disabled] [size=512K] Capabilities: Kernel driver in use: nvidia Kernel modules: nvidiafb, nouveau, nvidia_drm, nvidia ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: nvidia-driver-418 418.56-0ubuntu1 ProcVersionSignature: User Name 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri May 3 07:30:36 2019 InstallationDate: Installed on 2019-04-29 (3 days ago) InstallationMedia: Ubuntu 19.10 "Eoan EANIMAL" - Alpha amd64 (20190428) SourcePackage: nvidia-graphics-drivers-418 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1827466/+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 1827466] Re: Display corrupted on resume from suspend
*** This bug is a duplicate of bug 1809407 *** https://bugs.launchpad.net/bugs/1809407 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-418 in Ubuntu. https://bugs.launchpad.net/bugs/1827466 Title: Display corrupted on resume from suspend Status in gnome-shell package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-418 package in Ubuntu: Confirmed Bug description: Ubuntu Desktop EE On resume from suspend the background is corrupted both in the screen lock and on the gnome shell session. Screenshot attached. Reloading the shell fixes the issue. 01:00.0 3D controller: NVIDIA Corporation GP108M [GeForce MX150] (rev a1) Subsystem: Dell GP108M [GeForce MX150] Flags: bus master, fast devsel, latency 0, IRQ 141 Memory at d200 (32-bit, non-prefetchable) [size=16M] Memory at c000 (64-bit, prefetchable) [size=256M] Memory at d000 (64-bit, prefetchable) [size=32M] I/O ports at e000 [size=128] [virtual] Expansion ROM at d300 [disabled] [size=512K] Capabilities: Kernel driver in use: nvidia Kernel modules: nvidiafb, nouveau, nvidia_drm, nvidia ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: nvidia-driver-418 418.56-0ubuntu1 ProcVersionSignature: User Name 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri May 3 07:30:36 2019 InstallationDate: Installed on 2019-04-29 (3 days ago) InstallationMedia: Ubuntu 19.10 "Eoan EANIMAL" - Alpha amd64 (20190428) SourcePackage: nvidia-graphics-drivers-418 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1827466/+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
