[Kernel-packages] [Bug 1796443]
Fixed in Linus's tree with commit 60c8144afc28 ("x86/MCE/AMD: Fix the thresholding machinery initialization order"). -- 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/1796443 Title: HP EliteBook 745 G5 (Ryzen 2500U) fails to boot unless `mce=off` is set on command line Status in Linux: Fix Released Status in linux package in Ubuntu: Confirmed Bug description: My new Elitebook, with the latest bios 1.03.01, refuses to boot any kernel later than 4.10 unless mce=off is appended to the kernel command line. As in, there are no kernel messages at all after grub (yes, quiet and splash were removed from the command line). Perhaps it crashes before the efifb kicks in? System operates fine if mce=off is added to the kernel command line (and iommu=soft, but that's a separate issue, and fails with kernel output in that case). I opened upstream bug here : https://bugzilla.kernel.org/show_bug.cgi?id=201291 I bisected the problem down to this commit (and the few before it, which also added extra MCE output, but didn't actually crash): 18807ddb7f88d4ac3797302bafb18143d573e66f is the first bad commit commit 18807ddb7f88d4ac3797302bafb18143d573e66f Author: Yazen Ghannam Date: Tue Nov 15 15:13:53 2016 -0600 x86/mce/AMD: Reset Threshold Limit after logging error The error count field in MCA_MISC does not get reset by hardware when the threshold has been reached. Software is expected to reset it. Currently, the threshold limit only gets reset during init or when a user writes to sysfs. If the user is not monitoring threshold interrupts and resetting the limit then the user will only see 1 interrupt when the limit is first hit. So if, for example, the limit is set to 10 then only 1 interrupt will be recorded after 10 errors even if 100 errors have occurred. The user may then assume that only 10 errors have occurred. There are threads online about this being related to the latest bios. The upstream bug has acpidump attached. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-8-generic 4.18.0-8.9 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: john 2015 F pulseaudio /dev/snd/pcmC1D0p: john 2015 F...m pulseaudio /dev/snd/controlC0: john 2015 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Oct 5 23:24:45 2018 InstallationDate: Installed on 2018-09-30 (5 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180927) Lsusb: Bus 005 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP EliteBook 745 G5 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic root=UUID=5cf73665-d2a3-4203-80fd-659faf1afea4 ro quiet splash iommu=soft mce=off RelatedPackageVersions: linux-restricted-modules-4.18.0-8-generic N/A linux-backports-modules-4.18.0-8-generic N/A linux-firmware1.175 RfKill: 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux StagingDrivers: r8822be UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/26/2018 dmi.bios.vendor: HP dmi.bios.version: Q81 Ver. 01.03.01 dmi.board.name: 83D5 dmi.board.vendor: HP dmi.board.version: KBC Version 08.47.00 dmi.chassis.asset.tag: 5CG838305Y dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrQ81Ver.01.03.01:bd07/26/2018:svnHP:pnHPEliteBook745G5:pvr:rvnHP:rn83D5:rvrKBCVersion08.47.00:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP EliteBook dmi.product.name: HP EliteBook 745 G5 dmi.product.sku: 2MG23AV dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1796443/+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 1796443] Re: HP EliteBook 745 G5 (Ryzen 2500U) fails to boot unless `mce=off` is set on command line
** Changed in: linux Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1796443 Title: HP EliteBook 745 G5 (Ryzen 2500U) fails to boot unless `mce=off` is set on command line Status in Linux: Fix Released Status in linux package in Ubuntu: Confirmed Bug description: My new Elitebook, with the latest bios 1.03.01, refuses to boot any kernel later than 4.10 unless mce=off is appended to the kernel command line. As in, there are no kernel messages at all after grub (yes, quiet and splash were removed from the command line). Perhaps it crashes before the efifb kicks in? System operates fine if mce=off is added to the kernel command line (and iommu=soft, but that's a separate issue, and fails with kernel output in that case). I opened upstream bug here : https://bugzilla.kernel.org/show_bug.cgi?id=201291 I bisected the problem down to this commit (and the few before it, which also added extra MCE output, but didn't actually crash): 18807ddb7f88d4ac3797302bafb18143d573e66f is the first bad commit commit 18807ddb7f88d4ac3797302bafb18143d573e66f Author: Yazen Ghannam Date: Tue Nov 15 15:13:53 2016 -0600 x86/mce/AMD: Reset Threshold Limit after logging error The error count field in MCA_MISC does not get reset by hardware when the threshold has been reached. Software is expected to reset it. Currently, the threshold limit only gets reset during init or when a user writes to sysfs. If the user is not monitoring threshold interrupts and resetting the limit then the user will only see 1 interrupt when the limit is first hit. So if, for example, the limit is set to 10 then only 1 interrupt will be recorded after 10 errors even if 100 errors have occurred. The user may then assume that only 10 errors have occurred. There are threads online about this being related to the latest bios. The upstream bug has acpidump attached. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-8-generic 4.18.0-8.9 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: john 2015 F pulseaudio /dev/snd/pcmC1D0p: john 2015 F...m pulseaudio /dev/snd/controlC0: john 2015 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Oct 5 23:24:45 2018 InstallationDate: Installed on 2018-09-30 (5 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180927) Lsusb: Bus 005 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP EliteBook 745 G5 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic root=UUID=5cf73665-d2a3-4203-80fd-659faf1afea4 ro quiet splash iommu=soft mce=off RelatedPackageVersions: linux-restricted-modules-4.18.0-8-generic N/A linux-backports-modules-4.18.0-8-generic N/A linux-firmware1.175 RfKill: 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux StagingDrivers: r8822be UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/26/2018 dmi.bios.vendor: HP dmi.bios.version: Q81 Ver. 01.03.01 dmi.board.name: 83D5 dmi.board.vendor: HP dmi.board.version: KBC Version 08.47.00 dmi.chassis.asset.tag: 5CG838305Y dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrQ81Ver.01.03.01:bd07/26/2018:svnHP:pnHPEliteBook745G5:pvr:rvnHP:rn83D5:rvrKBCVersion08.47.00:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP EliteBook dmi.product.name: HP EliteBook 745 G5 dmi.product.sku: 2MG23AV dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1796443/+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 1806177] [NEW] Display resolution with later kernels
Public bug reported: Hardware - thinkpad T430, 3rd gen integrated graphics, external LG ultrawide monitor (2560x1080). OS linux mint. Any kernel later than 4.5.7. will not correctly identify the monitor resolution only giving 1920x1080 as the max. No problems with the earlier kernels. Further information: https://forums.linuxmint.com/viewtopic.php?f=46&t=280143 While not hard fact, it would appear that other older thinkpads, e.g. X220 and 4k screens have the same problem. ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1806177 Title: Display resolution with later kernels Status in linux package in Ubuntu: Incomplete Bug description: Hardware - thinkpad T430, 3rd gen integrated graphics, external LG ultrawide monitor (2560x1080). OS linux mint. Any kernel later than 4.5.7. will not correctly identify the monitor resolution only giving 1920x1080 as the max. No problems with the earlier kernels. Further information: https://forums.linuxmint.com/viewtopic.php?f=46&t=280143 While not hard fact, it would appear that other older thinkpads, e.g. X220 and 4k screens have the same problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1806177/+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 1806177] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1806177 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1806177 Title: Display resolution with later kernels Status in linux package in Ubuntu: Incomplete Bug description: Hardware - thinkpad T430, 3rd gen integrated graphics, external LG ultrawide monitor (2560x1080). OS linux mint. Any kernel later than 4.5.7. will not correctly identify the monitor resolution only giving 1920x1080 as the max. No problems with the earlier kernels. Further information: https://forums.linuxmint.com/viewtopic.php?f=46&t=280143 While not hard fact, it would appear that other older thinkpads, e.g. X220 and 4k screens have the same problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1806177/+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 1779173] Re: Dell D6000 dock lacks multicast Ethernet functionality
I think I've hit the same bug (Debian testing 4.18.0-2-amd64, with an i-tec docking station: https://i-tec.cz/en/produkt/cadua4kdockpdl-2/, but same driver and problems: IPv6 RA and IPv4+IPv6 mdns not working). I think this shows an overview of the patches you submitted: https://patchwork.kernel.org/project/linux- usb/list/?submitter=181339&state=%2A&archive=both It seems patchwork can't figure out a patch series for your patches, and I'm also lost which patches I'd have to apply if I wanted to try them. Also all patches are "archived" (no idea what that means, but by default the search only looks for non-archived patches). Thanks for your work so far anyway! At least I know now it isn't my fault it isn't working :) -- 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/1779173 Title: Dell D6000 dock lacks multicast Ethernet functionality Status in Linux: Confirmed Status in linux package in Ubuntu: Triaged Bug description: Dell D6000 exposes a CDC_NCM device for Ethernet traffic. However, multicast Ethernet traffic is not processed making IPv6 not functional. Other services, like mDNS used for LAN service discovery are also hindered. The actual reason is that CDC_NCM driver was not processing requests to filter (admit) multicast traffic. I provide two patches to the linux kernel that admit all Ethernet multicast traffic whenever a multicast group is being joined. The solution is not optimal, as it makes the system receive more traffic than that strictly needed, but otherwise this only happens when the computer is connected to a dock and thus is running on AC power. I believe it is not worth the hassle to join only the requested groups. This is the same that is done in the CDN_ETHER driver. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1779173/+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 1803678] Re: linux-oem: 4.15.0-1028.33 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Incomplete => Fix Released ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1803592 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Testing FAILED certification-testing: Testing in progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1803678 Title: linux-oem: 4.15.0-1028.33 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: In Progress Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-oem package in Ubuntu: Invalid Status in linux-oem source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1803592 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1803678/+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 1795292] Re: ELAN469D touch pad not working
Hi all) Thanks for the good work, but same problem here. The model is ideapad 330-15arr (the same ryzen but without the S prefix) 5E80: 50 44 30 08 5F 48 49 44 0D 4D 53 46 54 30 30 30 PD0._HID.MSFT000 5E90: 31 00 08 5F 43 49 44 0D 50 4E 50 30 43 35 30 00 1.._CID.PNP0C50. 5EA0: 14 4F 04 5F 49 4E 49 00 A0 16 93 54 50 54 59 01 .O._INITPTY. 5EB0: 70 0D 45 4C 41 4E 30 36 31 45 00 5F 48 49 44 A0 p.ELAN061E._HID. 5EC0: 17 93 54 50 54 59 0A 02 70 0D 53 59 4E 41 32 42 ..TPTY..p.SYNA2B 5ED0: 34 41 00 5F 48 49 44 A0 16 93 54 50 54 59 0A 03 4A._HID...TPTY.. 5EE0: 70 0D 41 55 49 31 36 36 38 00 5F 48 49 44 A4 00 p.AUI1668._HID.. ELAN061E in acpidump latest 4.19.6 kernel from ukuu ivrs_ioapic[32]=00:14.0 did not help. Followed the tutorial on ivrs_table and now I have no errors in dmesg)) Still no touchpad. But I did not recompile the kernel... hope for an update -- 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/1795292 Title: ELAN469D touch pad not working Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: I installed Bionic Beaver and now upgraded to Cosmic Cuttlefish on this Lenovo Ideapad 330S-15ARR laptop. The touch pad doesn't work in either. Some possibly relevant info from dmesg: i2c_hid i2c-ELAN469D:00: i2c-ELAN469D:00 supply vdd not found, using dummy regulator i2c_designware AMDI0010:01: controller timed out ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-7-generic 4.18.0-7.8 ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5 Uname: Linux 4.18.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: xorbit 2086 F pulseaudio /dev/snd/pcmC1D0p: xorbit 2086 F...m pulseaudio /dev/snd/controlC0: xorbit 2086 F pulseaudio CurrentDesktop: GNOME Date: Sun Sep 30 23:14:26 2018 InstallationDate: Installed on 2018-09-20 (10 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 81FB ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-7-generic root=UUID=4d91f09e-6122-4dd4-81fc-482465f8f0e7 ro noapic processor.max_cstate=1 rcu_nocbs=0-7 pcie_aspm=off pci=noaer quiet splash vt.handoff=1 elan_i2c.dyndbg=+p RelatedPackageVersions: linux-restricted-modules-4.18.0-7-generic N/A linux-backports-modules-4.18.0-7-generic N/A linux-firmware1.175 SourcePackage: linux UpgradeStatus: Upgraded to cosmic on 2018-09-30 (0 days ago) dmi.bios.date: 06/08/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 7WCN22WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 330S-15ARR dmi.modalias: dmi:bvnLENOVO:bvr7WCN22WW:bd06/08/2018:svnLENOVO:pn81FB:pvrLenovoideapad330S-15ARR:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad330S-15ARR: dmi.product.family: ideapad 330S-15ARR dmi.product.name: 81FB dmi.product.sku: LENOVO_MT_81FB_BU_idea_FM_ideapad 330S-15ARR dmi.product.version: Lenovo ideapad 330S-15ARR dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-09-20 (13 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Tags: cosmic Uname: Linux 4.19.0-041900rc6-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to cosmic on 2018-09-30 (2 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1795292/+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 1776563] Re: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash
Ubuntu 18.10 can boot with acpi=noirq kernel parameter from liveUSB. At first glance it works well (HDMI, ethernet and suspend had not been tested). While dmesg is hugely different from "noapic", /proc/interrupts still shows no APIC controller in use. -- 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/1776563 Title: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash Status in amd: Fix Released Status in Linux: Incomplete Status in linux package in Ubuntu: Triaged Status in linux-firmware package in Ubuntu: Confirmed Bug description: CPU: Ryzen 5 2500U VGA: Radeon 535 Notebook: Acer Aspire A315 This is a brand new notebook on the market with Ryzen 5/Radeon. The default kernel of Ubuntu(18.04) hangs at loading with message: tsc: Refined TSC clocksource calibration: 1996.250 MHz clocksource: tsc: mask: 0x max_cycles: (...), max_idle_ns: (...) Soft lockup Using pci=noacpi kernel parameter kernel loads without any problem but my notebook produces more heat than on Win10. If I know right Acer notebooks need ACPI to the correct power management. The same thing happens on mainline 4.17,4.18rc1-2. BIOS upgrade to the latest version: 1.08 hasn't helped This problem has been reported upstream: https://bugzilla.kernel.org/show_bug.cgi?id=200087 The latest correctly working kernel was 4.13.* but the heat problem was present with this too. To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1776563/+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 1806177] Re: Display resolution with later kernels
** 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/1806177 Title: Display resolution with later kernels Status in linux package in Ubuntu: Confirmed Bug description: Hardware - thinkpad T430, 3rd gen integrated graphics, external LG ultrawide monitor (2560x1080). OS linux mint. Any kernel later than 4.5.7. will not correctly identify the monitor resolution only giving 1920x1080 as the max. No problems with the earlier kernels. Further information: https://forums.linuxmint.com/viewtopic.php?f=46&t=280143 While not hard fact, it would appear that other older thinkpads, e.g. X220 and 4k screens have the same problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1806177/+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 1748565] Re: Kernel regularly logs: Bluetooth: hci0: last event is not cmd complete (0x0f)
$ tail -f /var/log/syslog Dec 1 21:28:26 localhost kernel: [ 683.235091] Bluetooth: hci0: last event is not cmd complete (0x0f) $ dmesg | grep -i bluetooth [3.368473] bluetooth hci0: Direct firmware load for brcm/BCM20702A1-13d3-3404.hcd failed with error -2 [3.368475] Bluetooth: hci0: BCM: Patch brcm/BCM20702A1-13d3-3404.hcd not found I use the step to fix, now I can send file to my phone with bluetooth, and use AirPods :) https://unix.stackexchange.com/questions/359979/broadcom-bcm4352 -bluetooth-does-not-connect?answertab=votes#tab-top my step: $ cd /lib/firmware/brcm $ sudo wget https://github.com/winterheart/broadcom-bt-firmware/raw/master/brcm/BCM20702A1-13d3-3404.hcd $ sudo modprobe -r btusb $ sudo modprobe btusb -- 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/1748565 Title: Kernel regularly logs: Bluetooth: hci0: last event is not cmd complete (0x0f) Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Status in Fedora: New Bug description: Hello, dmesg: [ 3363.056494] Bluetooth: hci0: last event is not cmd complete (0x0f) Regards, -- Cristian ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-9-generic 4.15.0-9.10 ProcVersionSignature: Ubuntu 4.15.0-9.10-generic 4.15.2 Uname: Linux 4.15.0-9-generic x86_64 ApportVersion: 2.20.8-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: caravena 1811 F pulseaudio CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME Date: Fri Feb 9 20:35:29 2018 InstallationDate: Installed on 2017-10-13 (119 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-9-generic root=UUID=707d0f89-4b1d-4432-9d50-6058dc4c1ee9 ro rootflags=subvol=@ quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-9-generic N/A linux-backports-modules-4.15.0-9-generic N/A linux-firmware1.170 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P14AAJ dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: SAMSUNG_NP1234567890 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.family: ChiefRiver System dmi.product.name: 530U3C/530U4C dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1748565/+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 1806188] [NEW] NVIDIA package driver problems
Public bug reported: GPU GTXX 750 ti; Ubuntu 64bit full update. Encounter an issue when I install the NVIDIA proprietary drivers (sudo apt install nvidia-driver-410): I also try with: sudo apt -f install, but no problem: emanu@emanuc:~$ sudo apt -f install [sudo] password di emanu: Lettura elenco dei pacchetti... Fatto Generazione albero delle dipendenze Lettura informazioni sullo stato... Fatto Correzione delle dipendenze... Fatto I seguenti pacchetti aggiuntivi saranno inoltre installati: libnvidia-gl-410:i386 libnvidia-ifr1-410 I seguenti pacchetti NUOVI saranno installati: libnvidia-gl-410:i386 libnvidia-ifr1-410 0 aggiornati, 2 installati, 0 da rimuovere e 0 non aggiornati. 21 non completamente installati o rimossi. È necessario scaricare 0 B/16,6 MB di archivi. Dopo quest'operazione, verranno occupati 69,4 MB di spazio su disco. Continuare? [S/n] (Lettura del database... 226360 file e directory attualmente installati.) Preparativi per estrarre .../libnvidia-gl-410_410.78-0ubuntu1_i386.deb... Estrazione di libnvidia-gl-410:i386 (410.78-0ubuntu1)... dpkg: errore nell'elaborare l'archivio /var/cache/apt/archives/libnvidia-gl-410_410.78-0ubuntu1_i386.deb (--unpack): tentata sovrascrittura di "/usr/share/doc/libnvidia-gl-410/changelog.Debian.gz" (condiviso), diverso da altre istanze del pacchetto libnvidia-gl-410:i386 Preparativi per estrarre .../libnvidia-ifr1-410_410.78-0ubuntu1_amd64.deb... Estrazione di libnvidia-ifr1-410:amd64 (410.78-0ubuntu1)... dpkg: errore nell'elaborare l'archivio /var/cache/apt/archives/libnvidia-ifr1-410_410.78-0ubuntu1_amd64.deb (--unpack): tentata sovrascrittura di "/usr/share/doc/libnvidia-ifr1-410/changelog.Debian.gz" (condiviso), diverso da altre istanze del pacchetto libnvidia-ifr1-410:amd64 Si sono verificati degli errori nell'elaborazione: /var/cache/apt/archives/libnvidia-gl-410_410.78-0ubuntu1_i386.deb /var/cache/apt/archives/libnvidia-ifr1-410_410.78-0ubuntu1_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: nvidia-driver-410 410.78-0ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Dec 1 15:26:48 2018 InstallationDate: Installed on 2018-04-29 (215 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180421.1) ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: nvidia-graphics-drivers-410 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-410 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco third-party-packages ** Description changed: - Encounter an issue when I install the NVIDIA proprietary drivers (sudo - apt install nvidia-driver-410): + Incontrare un problema quando installo i driver proprietari NVIDIA: sudo + apt install nvidia-driver-410 - emanu@emanuc:~$ sudo apt -f install + I also try with: sudo apt -f install, but no problem: + + emanu @ emanuc: ~ $ sudo apt -f install [sudo] password di emanu: - Lettura elenco dei pacchetti... Fatto - Generazione albero delle dipendenze - Lettura informazioni sullo stato... Fatto - Correzione delle dipendenze... Fatto - I seguenti pacchetti aggiuntivi saranno inoltre installati: - libnvidia-gl-410:i386 libnvidia-ifr1-410 - I seguenti pacchetti NUOVI saranno installati: - libnvidia-gl-410:i386 libnvidia-ifr1-410 - 0 aggiornati, 2 installati, 0 da rimuovere e 0 non aggiornati. - 21 non completamente installati o rimossi. - È necessario scaricare 0 B/16,6 MB di archivi. - Dopo quest'operazione, verranno occupati 69,4 MB di spazio su disco. - Continuare? [S/n] - (Lettura del database... 226360 file e directory attualmente installati.) - Preparativi per estrarre .../libnvidia-gl-410_410.78-0ubuntu1_i386.deb... - Estrazione di libnvidia-gl-410:i386 (410.78-0ubuntu1)... - dpkg: errore nell'elaborare l'archivio /var/cache/apt/archives/libnvidia-gl-410_410.78-0ubuntu1_i386.deb (--unpack): - tentata sovrascrittura di "/usr/share/doc/libnvidia-gl-410/changelog.Debian.gz" (condiviso), diverso da altre istanze del pacchetto libnvidia-gl-410:i386 - Preparativi per estrarre .../libnvidia-ifr1-410_410.78-0ubuntu1_amd64.deb... - Estrazione di libnvidia-ifr1-410:amd64 (410.78-0ubuntu1)... - dpkg: errore nell'elaborare l'archivio /var/cache/apt/archives/libnvidia-ifr1-410_410.78-0ubuntu1_amd64.deb (--unpack): - tentata sovrascrittura di "/usr/share/doc/libnvidia-ifr1-410/changelog.Debian.gz" (condiviso), diverso da altre istanze del pacchetto libnvidia-ifr1-410:amd64 - Si sono verificati degli errori nell'elaborazione: - /var/cache/apt/archives/libnvidia-gl-410_410.78-0ubuntu1_i386.deb - /var/cache/apt/archives/libnvidia-ifr1-410_410.78-0ubuntu1_amd64.deb - E: Sub-process /usr/bin/dpkg
Re: [Kernel-packages] [Bug 1779173] Re: Dell D6000 dock lacks multicast Ethernet functionality
Just use the ones attached to this bug report. They should work fine. El 1/12/18 a las 12:03, Stefan Bühler escribió: > I think I've hit the same bug (Debian testing 4.18.0-2-amd64, with an i-tec > docking station: https://i-tec.cz/en/produkt/cadua4kdockpdl-2/, but > same driver and problems: IPv6 RA and IPv4+IPv6 mdns not working). > > I think this shows an overview of the patches you submitted: > > https://patchwork.kernel.org/project/linux- > usb/list/?submitter=181339&state=%2A&archive=both > > It seems patchwork can't figure out a patch series for your patches, and I'm > also lost which patches I'd have to apply if I wanted to try them. Also all > patches are "archived" (no idea what that means, but by default the search > only looks for non-archived patches). > > Thanks for your work so far anyway! At least I know now it isn't my fault it > isn't working :) > -- 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/1779173 Title: Dell D6000 dock lacks multicast Ethernet functionality Status in Linux: Confirmed Status in linux package in Ubuntu: Triaged Bug description: Dell D6000 exposes a CDC_NCM device for Ethernet traffic. However, multicast Ethernet traffic is not processed making IPv6 not functional. Other services, like mDNS used for LAN service discovery are also hindered. The actual reason is that CDC_NCM driver was not processing requests to filter (admit) multicast traffic. I provide two patches to the linux kernel that admit all Ethernet multicast traffic whenever a multicast group is being joined. The solution is not optimal, as it makes the system receive more traffic than that strictly needed, but otherwise this only happens when the computer is connected to a dock and thus is running on AC power. I believe it is not worth the hassle to join only the requested groups. This is the same that is done in the CDN_ETHER driver. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1779173/+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 1804874] Re: can't reconnect USB mouse/ USB mouse stops working after a while
This happened before upgrade to 18.04- 4.15.0-39-generic #42-Ubuntu SMP Tue Oct 23 15:43:58 UTC 2018 i686 i686 i686 GNU/Linux is what I have now, I don't think I will test latest upstream kernel, sorry. -- 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/1804874 Title: can't reconnect USB mouse/ USB mouse stops working after a while Status in linux package in Ubuntu: Incomplete Bug description: https://wiki.ubuntu.com/DebuggingMouseDetection#generalinfo - used this tutorial "entered following commands : LANG=C dmesg > ~/dmesg diff -ns ~/dmesg_boot ~/dmesg > ~/dmesg_diff cp /var/log/Xorg.0.log ~/Xorg.0.log_tmp diff -ns ~/Xorg.0.log ~/Xorg.0.log_tmp > ~/Xorg.0.log_diff " Output files are compressed and attached to this bug report. Ubuntu 18.04.1, gnome and kde installed. --- ProblemType: Bug .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.5 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu DkmsStatus: i915-4.6.3-4.4.0, 1, 4.4.0-36-generic, i686: installed GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 2nd Generation Core Processor Family Integrated Graphics Controller [1043:1652] InstallationDate: Installed on 2014-08-26 (1550 days ago) InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 (20140204) MachineType: ASUSTeK Computer Inc. K53E Package: xorg 1:7.7+19ubuntu7.1 PackageArchitecture: i386 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-39-generic root=UUID=5faedd29-769a-4472-935e-602675fb441d ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18 Tags: third-party-packages bionic ubuntu Uname: Linux 4.15.0-39-generic i686 UpgradeStatus: Upgraded to bionic on 2018-11-22 (0 days ago) UserGroups: adm cdrom dip libvirt libvirtd lpadmin plugdev sambashare sudo www-data _MarkForUpload: True dmi.bios.date: 08/10/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: K53E.221 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: K53E 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.:bvrK53E.221:bd08/10/2012:svnASUSTeKComputerInc.:pnK53E:pvr1.0:rvnASUSTeKComputerInc.:rnK53E:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.family: K dmi.product.name: K53E dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Thu Oct 11 13:44:11 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 732 vendor LGD xserver.version: 2:1.18.4-0ubuntu0.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1804874/+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 1779173] Re: Dell D6000 dock lacks multicast Ethernet functionality
Thanks. So I went ahead and created an environment to build some affected modules out of tree (also includes a dkms package): https://github.com/stbuehler/fixed-cdc-ether-ncm mDNS and IPv6 working fine so far. -- 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/1779173 Title: Dell D6000 dock lacks multicast Ethernet functionality Status in Linux: Confirmed Status in linux package in Ubuntu: Triaged Bug description: Dell D6000 exposes a CDC_NCM device for Ethernet traffic. However, multicast Ethernet traffic is not processed making IPv6 not functional. Other services, like mDNS used for LAN service discovery are also hindered. The actual reason is that CDC_NCM driver was not processing requests to filter (admit) multicast traffic. I provide two patches to the linux kernel that admit all Ethernet multicast traffic whenever a multicast group is being joined. The solution is not optimal, as it makes the system receive more traffic than that strictly needed, but otherwise this only happens when the computer is connected to a dock and thus is running on AC power. I believe it is not worth the hassle to join only the requested groups. This is the same that is done in the CDN_ETHER driver. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1779173/+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 1804874] Re: can't reconnect USB mouse/ USB mouse stops working after a while
Okay, I'm testing 4.19.6-041906-generic #201812010432 SMP Sat Dec 1 09:46:14 UTC 2018 i686 i686 i686 GNU/Linux. Did not go trough compiling manually. -- 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/1804874 Title: can't reconnect USB mouse/ USB mouse stops working after a while Status in linux package in Ubuntu: Incomplete Bug description: https://wiki.ubuntu.com/DebuggingMouseDetection#generalinfo - used this tutorial "entered following commands : LANG=C dmesg > ~/dmesg diff -ns ~/dmesg_boot ~/dmesg > ~/dmesg_diff cp /var/log/Xorg.0.log ~/Xorg.0.log_tmp diff -ns ~/Xorg.0.log ~/Xorg.0.log_tmp > ~/Xorg.0.log_diff " Output files are compressed and attached to this bug report. Ubuntu 18.04.1, gnome and kde installed. --- ProblemType: Bug .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.5 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu DkmsStatus: i915-4.6.3-4.4.0, 1, 4.4.0-36-generic, i686: installed GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 2nd Generation Core Processor Family Integrated Graphics Controller [1043:1652] InstallationDate: Installed on 2014-08-26 (1550 days ago) InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 (20140204) MachineType: ASUSTeK Computer Inc. K53E Package: xorg 1:7.7+19ubuntu7.1 PackageArchitecture: i386 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-39-generic root=UUID=5faedd29-769a-4472-935e-602675fb441d ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18 Tags: third-party-packages bionic ubuntu Uname: Linux 4.15.0-39-generic i686 UpgradeStatus: Upgraded to bionic on 2018-11-22 (0 days ago) UserGroups: adm cdrom dip libvirt libvirtd lpadmin plugdev sambashare sudo www-data _MarkForUpload: True dmi.bios.date: 08/10/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: K53E.221 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: K53E 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.:bvrK53E.221:bd08/10/2012:svnASUSTeKComputerInc.:pnK53E:pvr1.0:rvnASUSTeKComputerInc.:rnK53E:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.family: K dmi.product.name: K53E dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Thu Oct 11 13:44:11 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 732 vendor LGD xserver.version: 2:1.18.4-0ubuntu0.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1804874/+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 1804874] Re: can't reconnect USB mouse/ USB mouse stops working after a while
4.19.6-041906-generic - still can't reconnect mouse after disconnect. -- 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/1804874 Title: can't reconnect USB mouse/ USB mouse stops working after a while Status in linux package in Ubuntu: Incomplete Bug description: https://wiki.ubuntu.com/DebuggingMouseDetection#generalinfo - used this tutorial "entered following commands : LANG=C dmesg > ~/dmesg diff -ns ~/dmesg_boot ~/dmesg > ~/dmesg_diff cp /var/log/Xorg.0.log ~/Xorg.0.log_tmp diff -ns ~/Xorg.0.log ~/Xorg.0.log_tmp > ~/Xorg.0.log_diff " Output files are compressed and attached to this bug report. Ubuntu 18.04.1, gnome and kde installed. --- ProblemType: Bug .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.5 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu DkmsStatus: i915-4.6.3-4.4.0, 1, 4.4.0-36-generic, i686: installed GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 2nd Generation Core Processor Family Integrated Graphics Controller [1043:1652] InstallationDate: Installed on 2014-08-26 (1550 days ago) InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 (20140204) MachineType: ASUSTeK Computer Inc. K53E Package: xorg 1:7.7+19ubuntu7.1 PackageArchitecture: i386 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-39-generic root=UUID=5faedd29-769a-4472-935e-602675fb441d ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18 Tags: third-party-packages bionic ubuntu Uname: Linux 4.15.0-39-generic i686 UpgradeStatus: Upgraded to bionic on 2018-11-22 (0 days ago) UserGroups: adm cdrom dip libvirt libvirtd lpadmin plugdev sambashare sudo www-data _MarkForUpload: True dmi.bios.date: 08/10/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: K53E.221 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: K53E 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.:bvrK53E.221:bd08/10/2012:svnASUSTeKComputerInc.:pnK53E:pvr1.0:rvnASUSTeKComputerInc.:rnK53E:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.family: K dmi.product.name: K53E dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Thu Oct 11 13:44:11 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 732 vendor LGD xserver.version: 2:1.18.4-0ubuntu0.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1804874/+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 1742658] Re: linux-generic-hwe-16.04 OOPS in nouveau after security update
Hi, I've been running Ubuntu 18.04 for a while now on this machine, so I do not know whether 16.04 would work, it certainly didn't work at all when I filed this bugreport. I would suggest that if anyone else runs into this issue they should upgrade to 18.04 or 18.10. -- 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/1742658 Title: linux-generic-hwe-16.04 OOPS in nouveau after security update Status in linux package in Ubuntu: Confirmed Status in linux-hwe package in Ubuntu: New Status in linux-hwe-edge package in Ubuntu: New Status in linux-meta-hwe package in Ubuntu: New Status in linux-meta-hwe-edge package in Ubuntu: New Bug description: Description: Ubuntu 16.04.3 LTS Release: 16.04 After upgrading linux-generic-hwe-16.04 to 4.13.0.26.46 I get a black screen with nouveau. Previously I was running 4.10.0-42-generic, and that kernel still works fine. Here is the OOPS: an 11 09:39:18 edvin-tower kernel: [3.079986] [drm] Initialized nouveau 1.3.1 20120801 for :02:00.0 on minor 0 Jan 11 09:39:18 edvin-tower kernel: [3.100591] BUG: unable to handle kernel NULL pointer dereference at (null) Jan 11 09:39:18 edvin-tower kernel: [3.100606] IP: (null) Jan 11 09:39:18 edvin-tower kernel: [3.100610] PGD 0 Jan 11 09:39:18 edvin-tower kernel: [3.100611] P4D 0 Jan 11 09:39:18 edvin-tower kernel: [3.100615] Jan 11 09:39:18 edvin-tower kernel: [3.100620] Oops: 0010 [#1] SMP PTI Jan 11 09:39:18 edvin-tower kernel: [3.100623] Modules linked in: hid_generic usbhid hid nouveau mxm_wmi video i2c_algo_bit ttm drm_kms_helper syscopyarea sysfillrect e1000e sysimgblt fb_sys_fops drm ptp ahci pps_core pata_acpi libahci wmi Jan 11 09:39:18 edvin-tower kernel: [3.100643] CPU: 4 PID: 238 Comm: kworker/u16:7 Not tainted 4.13.0-26-generic #29~16.04.2-Ubuntu Jan 11 09:39:18 edvin-tower kernel: [3.100649] Hardware name: Dell Inc. Precision Tower 5810/0K240Y, BIOS A05 12/16/2014 Jan 11 09:39:18 edvin-tower kernel: [3.100688] Workqueue: nvkm-disp gf119_disp_super [nouveau] Jan 11 09:39:18 edvin-tower kernel: [3.100694] task: 9d8982d25d00 task.stack: ac9ec2134000 Jan 11 09:39:18 edvin-tower kernel: [3.100698] RIP: 0010: (null) Jan 11 09:39:18 edvin-tower kernel: [3.100701] RSP: 0018:ac9ec2137bd8 EFLAGS: 00010206 Jan 11 09:39:18 edvin-tower kernel: [3.100706] RAX: c0416f20 RBX: RCX: 0016 Jan 11 09:39:18 edvin-tower kernel: [3.100710] RDX: RSI: RDI: 9d898140d180 Jan 11 09:39:18 edvin-tower kernel: [3.100715] RBP: ac9ec2137c70 R08: R09: Jan 11 09:39:18 edvin-tower kernel: [3.100719] R10: 1000 R11: R12: Jan 11 09:39:18 edvin-tower kernel: [3.100724] R13: R14: ac9ec2137d00 R15: 9d898c542600 Jan 11 09:39:18 edvin-tower kernel: [3.100728] FS: () GS:9d899fd0() knlGS: Jan 11 09:39:18 edvin-tower kernel: [3.100733] CS: 0010 DS: ES: CR0: 80050033 Jan 11 09:39:18 edvin-tower kernel: [3.100737] CR2: CR3: 00029ac0a006 CR4: 001606e0 Jan 11 09:39:18 edvin-tower kernel: [3.100742] Call Trace: Jan 11 09:39:18 edvin-tower kernel: [3.100771] ? nvkm_dp_train_drive+0x214/0x300 [nouveau] Jan 11 09:39:18 edvin-tower kernel: [3.100798] nvkm_dp_train+0x582/0x970 [nouveau] Jan 11 09:39:18 edvin-tower kernel: [3.100824] nvkm_dp_acquire+0xd4/0x390 [nouveau] Jan 11 09:39:18 edvin-tower kernel: [3.100850] nv50_disp_super_2_2+0x6d/0x430 [nouveau] Jan 11 09:39:18 edvin-tower kernel: [3.100872] ? nvkm_devinit_pll_set+0xf/0x20 [nouveau] Jan 11 09:39:18 edvin-tower kernel: [3.100897] gf119_disp_super+0x1b7/0x300 [nouveau] Jan 11 09:39:18 edvin-tower kernel: [3.100904] ? __schedule+0x3ca/0x890 Jan 11 09:39:18 edvin-tower kernel: [3.100911] process_one_work+0x156/0x410 Jan 11 09:39:18 edvin-tower kernel: [3.100915] worker_thread+0x4b/0x460 Jan 11 09:39:18 edvin-tower kernel: [3.100920] kthread+0x109/0x140 Jan 11 09:39:18 edvin-tower kernel: [3.100924] ? process_one_work+0x410/0x410 Jan 11 09:39:18 edvin-tower kernel: [3.100928] ? kthread_create_on_node+0x70/0x70 Jan 11 09:39:18 edvin-tower kernel: [3.100934] ret_from_fork+0x1f/0x30 Jan 11 09:39:18 edvin-tower kernel: [3.100938] Code: Bad RIP value. Jan 11 09:39:18 edvin-tower kernel: [3.100944] RIP: (null) RSP: ac9ec2137bd8 Jan 11 09:39:18 edvin-tower kernel: [3.100948] CR2: Jan 11 09:39:18 edvin-tower kernel: [3.100952] ---[ end trace 93a79dae0d3ec749
[Kernel-packages] [Bug 1798921] Re: sky2 ethernet card don't work after returning from suspension
Would this bug effect WoL functionality? I've not experienced connectivity problems after resuming from suspend (using power button) but I only log into one account and use a pre- assigned IP address. Bios and WoL flags are set correctly withing netplan yaml config file but I cannot get the computer to wake using WoL. I can see that the router is sending the magic packet information as well. This leads to conclude that this bug could be affecting this functionality? dump of lsci -vvnn: --- 02:00.0 Ethernet controller [0200]: Marvell Technology Group Ltd. 88E8056 PCI-E Gigabit Ethernet Controller [11ab:4364] (rev 12) Subsystem: ASUSTeK Computer Inc. Motherboard [1043:81f8] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- https://bugs.launchpad.net/bugs/1798921 Title: sky2 ethernet card don't work after returning from suspension Status in linux package in Ubuntu: Confirmed Bug description: Bug very similar to #1752772 (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752772) but affecting the sky2 driver instead of r8169. After system suspend the ethernet connection stops working. The card is still up and the modem can see it is connected, but the card doesn't get an ip address. Ifconfig down/up and restarting network- manager does not solve the issue. Similarly to the other bug, "sudo modprobe sky2 -r" an then "sudo modprobe sky2" solves the issue. Relevant: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752772/comments/107 Linux 4.15.0-36-generic #39-Ubuntu SMP Mon Sep 24 16:19:09 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux *-network description: Ethernet interface product: 88E8040 PCI-E Fast Ethernet Controller vendor: Marvell Technology Group Ltd. physical id: 0 bus info: pci@:09:00.0 logical name: enp9s0 version: 13 serial: size: 100Mbit/s capacity: 100Mbit/s width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=sky2 driverversion=1.30 duplex=full latency=0 link=yes multicast=yes port=twisted pair speed=100Mbit/s resources: irq:24 memory:f68fc000-f68f ioport:de00(size=256) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798921/+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 1451387] Re: [Fujitsu LIFEBOOK LH532] UEFI firmware becomes locked after installing Ubuntu in UEFI mode
This saved my life. Followed the instructions in below link to reset the BIOS and things worked fine thereafter to load Ubuntu https://ubuntuforums.org/showthread.php?t=2257720 -- 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/1451387 Title: [Fujitsu LIFEBOOK LH532] UEFI firmware becomes locked after installing Ubuntu in UEFI mode Status in linux package in Ubuntu: Confirmed Bug description: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1082418/comments/74 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.16.0-30-generic 3.16.0-30.40~14.04.1 ProcVersionSignature: Ubuntu 3.16.0-30.40~14.04.1-generic 3.16.7-ckt3 Uname: Linux 3.16.0-30-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 CurrentDesktop: Unity Date: Mon May 4 16:57:39 2015 InstallationDate: Installed on 2010-01-01 (1949 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) SourcePackage: linux-lts-utopic UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rut1480 F pulseaudio rut7079 F pulseaudio DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=d4bb392e-90ed-41a3-9d30-fa457fefb25b InstallationDate: Installed on 2010-01-01 (1949 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) MachineType: FUJITSU LIFEBOOK LH532 Package: linux (not installed) ProcFB: 0 inteldrmfb 1 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-30-generic.efi.signed root=UUID=e8258103-326b-4708-b64f-6306d0eb0a01 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.16.0-30.40~14.04.1-generic 3.16.7-ckt3 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.16.0-30-generic N/A linux-backports-modules-3.16.0-30-generic N/A linux-firmware 1.127.11 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: trusty Uname: Linux 3.16.0-30-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 05/24/2012 dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd. dmi.bios.version: Version 1.10 dmi.board.name: FJNBB1F dmi.board.vendor: FUJITSU dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.10:bd05/24/2012:svnFUJITSU:pnLIFEBOOKLH532:pvr:rvnFUJITSU:rnFJNBB1F:rvr:cvnFUJITSU:ct10:cvr: dmi.product.name: LIFEBOOK LH532 dmi.sys.vendor: FUJITSU --- ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rut2207 F pulseaudio DistroRelease: Ubuntu 15.04 HibernationDevice: RESUME=UUID=8fd2670c-4060-4d14-8f27-b9f806fe2ce7 InstallationDate: Installed on 2015-05-06 (0 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: FUJITSU LIFEBOOK LH532 Package: linux (not installed) ProcFB: 0 inteldrmfb 1 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-15-generic.efi.signed root=UUID=3129a485-81a2-48ef-be95-ef9c9a57be3e ro quiet splash ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.19.0-15-generic N/A linux-backports-modules-3.19.0-15-generic N/A linux-firmware 1.143 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: vivid UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 3.19.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 05/24/2012 dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd. dmi.bios.version: Version 1.10 dmi.board.name: FJNBB1F dmi.board.vendor: FUJITSU dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.10:bd05/24/2012:svnFUJITSU:pnLIFEBOOKLH532:pvr:rvnFUJITSU:rnFJNBB1F:rvr:cvnFUJITSU:ct10:cvr: dmi.product.name: LIFEBOOK LH532 dmi.sys.vendor: FUJITSU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/14
[Kernel-packages] [Bug 1774950] Re: Suspend fails in Ubuntu and Kubuntu 18.04 but works fine in Ubuntu and Kubuntu 17.10 (and on Kubuntu 18.04 using kernel 4.14.47)
Same thing here – Thinkpad X240 (Intel graphics and SSD). Should we create a new bug? In my case it is somehow correlated with ethernet. I can reproduce it in this way: 1. No WiFi connection only ethernet connection. 2. Suspend two times, after third time laptop won't suspend and ethernet stops working. -- 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/1774950 Title: Suspend fails in Ubuntu and Kubuntu 18.04 but works fine in Ubuntu and Kubuntu 17.10 (and on Kubuntu 18.04 using kernel 4.14.47) Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Bug description: ===SRU Justification=== [Impact] Systems with acpi-lpss can't do S3/S4 on Bionic. [Test] Users confirmed these patches work for them. [Fix] Commit a192aa923b66a (ACPI / LPSS: Consolidate runtime PM and system sleep handling) applies quirks for both runtime and system suspend. This causes problems for some systems, so avoid using quirks on S3 and S4. [Regression Potential] Low. These patches are in upstream stable, and it brings back driver's old behavior. ===Original Bug Report=== I have installed Kubuntu 18.04 on 3 different machines (my friend's and my own) with no suspend problems but my HP Pavilion 11 x360 does not suspend. It suspends fine with Ubuntu 17.10, Kubuntu 17.10, Devuan Jesse, Devuan ASCII and Windows 10 but fails with Ubuntu 18.04 and Kubuntu 18.04. I have also tried suspend using a live USB of 18.04 on this machine and it fails in the same way, so does not appear to be caused by any additional programs that I had installed. By installing an older kernel (4.14) on Kubuntu 18.04 the suspend function works as expected. Running Kubuntu 18.04 with kernels 4.15, 4.16, 4.17 results in the suspend failure that freezes the machine and requires a hard reset. Correct behaviour is - Screen goes blank, fan goes off, power LED flashes to show machine is in suspend. Pressing power button triggers 'resume' function. What happens - Screen goes blank, fan stays on, power LED stays on. Machine stays in this state and does not respond to any keyboard interaction, mouse movement or power button presses. Ctrl + Alt + f1 (or f2, f3, f4 etc) does not get any response. The only way to use the machine is to shut down by holding down the power button. Checking the logs suggests that the machine believes it is in suspend mode sleep [deep] when it isn't. Having to hard reset to get any response means that the kernel logs say no more than sleep [deep] pm-suspend also results in the same problems with kernels 4.15 and 4.16, but works fine with 4.14. It is curious that a machine that suspends fine on an earlier 4.14 kernel no longer works with 4.15 and above, whilst 3 other machines (including one with pretty similar hardware) do not exhibit this problem. There are only a handful of questions about it on the forums but at least 3 other people have the same problem: https://askubuntu.com/questions/1029405/ubuntu-18-04-crashes-on- resuming-from-suspend https://askubuntu.com/questions/1041369/after-upgrading- from-17-10-ubuntu-18-04-wont-sleep-suspend I am attempting to round up anyone else with the same issue and point them to this bug report. My laptop is HP Pavilion x360 11-n013na Matalaks is Acer Aspire ES1-511 collisionTwo has XPS 9560 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774950/+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 1806222] [NEW] package linux-firmware 1.173 failed to install/upgrade: unable to make backup link of './lib/firmware/intel/dsp_fw_kbl_v701.bin' before installing new version: In
Public bug reported: fyi ProblemType: Package DistroRelease: Ubuntu 18.04 Package: linux-firmware 1.173 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic i686 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: i386 CasperVersion: 1.394 Date: Sun Dec 2 09:52:01 2018 Dependencies: DuplicateSignature: package:linux-firmware:1.173 Unpacking linux-firmware (1.173.2) over (1.173) ... dpkg: error processing archive /tmp/apt-dpkg-install-sxxph2/255-linux-firmware_1.173.2_all.deb (--unpack): unable to make backup link of './lib/firmware/intel/dsp_fw_kbl_v701.bin' before installing new version: Input/output error ErrorMessage: unable to make backup link of './lib/firmware/intel/dsp_fw_kbl_v701.bin' before installing new version: Input/output error LiveMediaBuild: Lubuntu 18.04 LTS "Bionic Beaver" - Release i386 (20180426) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.6 SourcePackage: linux-firmware Title: package linux-firmware 1.173 failed to install/upgrade: unable to make backup link of './lib/firmware/intel/dsp_fw_kbl_v701.bin' before installing new version: Input/output error UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package bionic i386 -- 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/1806222 Title: package linux-firmware 1.173 failed to install/upgrade: unable to make backup link of './lib/firmware/intel/dsp_fw_kbl_v701.bin' before installing new version: Input/output error Status in linux-firmware package in Ubuntu: New Bug description: fyi ProblemType: Package DistroRelease: Ubuntu 18.04 Package: linux-firmware 1.173 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic i686 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: i386 CasperVersion: 1.394 Date: Sun Dec 2 09:52:01 2018 Dependencies: DuplicateSignature: package:linux-firmware:1.173 Unpacking linux-firmware (1.173.2) over (1.173) ... dpkg: error processing archive /tmp/apt-dpkg-install-sxxph2/255-linux-firmware_1.173.2_all.deb (--unpack): unable to make backup link of './lib/firmware/intel/dsp_fw_kbl_v701.bin' before installing new version: Input/output error ErrorMessage: unable to make backup link of './lib/firmware/intel/dsp_fw_kbl_v701.bin' before installing new version: Input/output error LiveMediaBuild: Lubuntu 18.04 LTS "Bionic Beaver" - Release i386 (20180426) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.6 SourcePackage: linux-firmware Title: package linux-firmware 1.173 failed to install/upgrade: unable to make backup link of './lib/firmware/intel/dsp_fw_kbl_v701.bin' before installing new version: Input/output error UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1806222/+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 1806222] Re: package linux-firmware 1.173 failed to install/upgrade: unable to make backup link of './lib/firmware/intel/dsp_fw_kbl_v701.bin' before installing new version: Inpu
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1806222 Title: package linux-firmware 1.173 failed to install/upgrade: unable to make backup link of './lib/firmware/intel/dsp_fw_kbl_v701.bin' before installing new version: Input/output error Status in linux-firmware package in Ubuntu: New Bug description: fyi ProblemType: Package DistroRelease: Ubuntu 18.04 Package: linux-firmware 1.173 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic i686 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: i386 CasperVersion: 1.394 Date: Sun Dec 2 09:52:01 2018 Dependencies: DuplicateSignature: package:linux-firmware:1.173 Unpacking linux-firmware (1.173.2) over (1.173) ... dpkg: error processing archive /tmp/apt-dpkg-install-sxxph2/255-linux-firmware_1.173.2_all.deb (--unpack): unable to make backup link of './lib/firmware/intel/dsp_fw_kbl_v701.bin' before installing new version: Input/output error ErrorMessage: unable to make backup link of './lib/firmware/intel/dsp_fw_kbl_v701.bin' before installing new version: Input/output error LiveMediaBuild: Lubuntu 18.04 LTS "Bionic Beaver" - Release i386 (20180426) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.6 SourcePackage: linux-firmware Title: package linux-firmware 1.173 failed to install/upgrade: unable to make backup link of './lib/firmware/intel/dsp_fw_kbl_v701.bin' before installing new version: Input/output error UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1806222/+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 1795659] Re: kernel panic using CIFS share smb2_push_mandatory_locks
[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/1795659 Title: kernel panic using CIFS share smb2_push_mandatory_locks Status in linux package in Ubuntu: Expired Bug description: Description:Ubuntu 16.04.5 LTS Release:16.04 Kernel: 4.15.0-36-generic #39~16.04.1-Ubuntu SMP Tue Sep 25 08:59:23 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux Under load, getting a system crash when accessing files on an SMB3 share. dmesg from crash attached. I can upload the crash dump if needed. Share is mounted with the following options: "ro,_netdev,username=*,password=*,domain=*,vers=3.02,sec=ntlmsspi,nounix,noserverino,nobrl,cache=none" Dmesg points to the cifs module [ 2192.662345] BUG: unable to handle kernel NULL pointer dereference at 0038 [ 2192.662407] IP: smb2_push_mandatory_locks+0x10e/0x3b0 [cifs] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1795659/+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 1794078] Re: Rebooting / booting and battery charging
[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/1794078 Title: Rebooting / booting and battery charging Status in linux package in Ubuntu: Expired Bug description: Does not reboot and battery does not charge fully. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 NonfreeKernelModules: wl .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Mon Sep 24 08:41:54 2018 DistUpgraded: 2018-09-23 21:15:55,906 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.15.0-34-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 4.4.0-135-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a26] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. Haswell-ULT Integrated Graphics Controller [106b:011b] InstallationDate: Installed on 2018-09-23 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Apple Inc. MacBookAir6,2 ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-34-generic root=UUID=4add3271-ffc7-4961-97a0-f796b33a7d0f ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-09-24 (0 days ago) dmi.bios.date: 04/11/2018 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBA61.88Z.0107.B00.180437 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-7DF21CB3ED6977E5 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookAir6,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-7DF21CB3ED6977E5 dmi.modalias: dmi:bvnAppleInc.:bvrMBA61.88Z.0107.B00.180437:bd04/11/2018:svnAppleInc.:pnMacBookAir6,2:pvr1.0:rvnAppleInc.:rnMac-7DF21CB3ED6977E5:rvrMacBookAir6,2:cvnAppleInc.:ct10:cvrMac-7DF21CB3ED6977E5: dmi.product.family: MacBook Air dmi.product.name: MacBookAir6,2 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Mon Sep 24 08:29:25 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1794078/+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 1794866] Re: package linux-image-4.15.0-34-generic 4.15.0-34.37 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/zz-update-grub exited with return code 127
[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/1794866 Title: package linux-image-4.15.0-34-generic 4.15.0-34.37 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/zz-update-grub exited with return code 127 Status in linux package in Ubuntu: Expired Bug description: i have no idea what's going on ProblemType: Package DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-34-generic 4.15.0-34.37 ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18 NonfreeKernelModules: nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Wed Sep 26 22:38:45 2018 DuplicateSignature: package:linux-image-4.15.0-34-generic:4.15.0-34.37 Setting up grub-pc (2.02-2ubuntu8.4) ... /var/lib/dpkg/info/grub-pc.config: 1: /etc/default/grub: If: not found dpkg: error processing package grub-pc (--configure): installed grub-pc package post-installation script subprocess returned error exit status 127 ErrorMessage: installed linux-image-4.15.0-34-generic package post-installation script subprocess returned error exit status 1 HibernationDevice: RESUME=UUID=f9fb9b45-15fd-4aaf-9d86-621c8a0f148d InstallationDate: Installed on 2016-09-05 (751 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic root=UUID=79e61542-0ff4-4917-8222-5239af1a5fe3 ro nouveau.modeset=0 quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: grub-pc 2.02-2ubuntu8.4 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux-signed Title: package linux-image-4.15.0-34-generic 4.15.0-34.37 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/zz-update-grub exited with return code 127 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1794866/+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 1793373] Re: package linux-image-extra-4.4.0-119-generic 4.4.0-119.143 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before at
[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/1793373 Title: package linux-image-extra-4.4.0-119-generic 4.4.0-119.143 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in linux package in Ubuntu: Expired Bug description: I was trying run the OS updates and got the error above? ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-extra-4.4.0-119-generic 4.4.0-119.143 ProcVersionSignature: Ubuntu 4.4.0-133.159-generic 4.4.134 Uname: Linux 4.4.0-133-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: steven 1897 F pulseaudio Date: Wed Sep 19 14:17:52 2018 DuplicateSignature: package:linux-image-extra-4.4.0-119-generic:4.4.0-119.143 Processing triggers for dbus (1.10.6-1ubuntu3.3) ... dpkg: error processing package linux-image-extra-4.4.0-119-generic (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration HibernationDevice: RESUME=UUID=8b487a35-1a21-4674-9720-185dd8bfd41c InstallationDate: Installed on 2016-05-25 (847 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04f2:b52b Chicony Electronics Co., Ltd Bus 001 Device 003: ID 0bda:b721 Realtek Semiconductor Corp. Bus 001 Device 002: ID 046d:c52f Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X540SA ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-133-generic.efi.signed root=UUID=1c9ef1ae-d7a6-4e81-b5c5-76f25af8c7ef ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc N/A SourcePackage: linux Title: package linux-image-extra-4.4.0-119-generic 4.4.0-119.143 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: Upgraded to xenial on 2018-09-19 (0 days ago) dmi.bios.date: 11/25/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X540SA.207 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X540SA 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.:bvrX540SA.207:bd11/25/2015:svnASUSTeKCOMPUTERINC.:pnX540SA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX540SA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X540SA 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/1793373/+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 1786906] Re: "ACPI unsupported"
[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/1786906 Title: "ACPI unsupported" Status in linux package in Ubuntu: Expired Bug description: While I'm using Ubuntu Server version on my laptop(HP omen 15, CPU:i5-8300H,GPU:GTX1050Ti), it always says "[ time.time] acpi INT3400:00: Unsupported event [0x86]", In Ubuntu Desktop version, after I turn on my computer, it'll not going on but stay at a screen and says "[ time.time] acpi INT3400:00: Unsupported event [0x86]" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786906/+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 1794488] Re: Reuse unpacked src tree when running autopkgtests
[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/1794488 Title: Reuse unpacked src tree when running autopkgtests Status in autopkgtest package in Ubuntu: Invalid Status in linux package in Ubuntu: Expired Bug description: src:linux ships broken debian/tests/* that do not use the unpacked debian source tree and instead DDoS launchpad with git clone requests of the identical kernel tree for no reason -- original bug report -- When running autopkgtests one is located at the top of the unpacked debian source tree. There is no location given as to where that is, in an environment variable, but it is trivial to cache it. Also, one is supposed to use AUTOPKGTEST_TMP directory for most of the disk space. Currently linux ubuntu_kernel_selftests clones linux git tree, instead of using the locally unpacked tree instead. Here is proposal to fix this. In git clone git://kernel.ubuntu.com/ubuntu/kernel-testing In run-dep8-tests do something like this: if [ -n "$AUTOPKGTEST_TMP" ]; then export ADT_LINUX_TREE=`pwd` cd $AUTOPKGTEST_TMP fi Then in git://kernel.ubuntu.com/ubuntu/autotest-client-tests, ubuntu_kernel_selftests/ubuntu_kernel_selftests.py in the setup() function add code to use ADT_LINUX_TREE if set in the envrionment, similar to how ~/ubuntu/ubuntu-%s is used. I'm not sure if symlink will do there, or if one needs to do `cp -a $ADT_LINUX_TREE linux` or some such. Alternatively, I guess debian/tests/ubuntu-regression-suite could initialize a git repo out of PWD and clone it into ~/ubuntu/ubuntu-%s to trick autotest-client-tests into using that later. Environment variables set during autopkgtest run: ADTTMP: /tmp/autopkgtest.RvYSiJ/autopkgtest_tmp ADT_ARTIFACTS: /tmp/autopkgtest.RvYSiJ/run-installed-artifacts ADT_TEST_TRIGGERS: glibc/2.28-0ubuntu1 AUTOPKGTEST_ARTIFACTS: /tmp/autopkgtest.RvYSiJ/run-installed-artifacts AUTOPKGTEST_TMP: /tmp/autopkgtest.RvYSiJ/autopkgtest_tmp HOME: /home/ubuntu OLDPWD: /home/ubuntu PWD: /tmp/autopkgtest.RvYSiJ/build.yTe/src To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autopkgtest/+bug/1794488/+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 1793849] Re: dazzle dvc 80 usb video capture card
[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/1793849 Title: dazzle dvc 80 usb video capture card Status in linux package in Ubuntu: Expired Bug description: this is my first bug report hope I did alright see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/302728 my dazzle card didn't give any input into vlc open capture device tv analog. lsb_release -rd Description: Ubuntu 18.04.1 LTS Release: 18.04 apt-cache policy vlc vlc: Installed: 3.0.3-1-1ubuntu1 Candidate: 3.0.3-1-1ubuntu1 Version table: *** 3.0.3-1-1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/universe amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/universe amd64 Packages 100 /var/lib/dpkg/status 3.0.1-3build1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-34-generic 4.15.0-34.37 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: mitch 3894 F...m pulseaudio /dev/snd/controlC0: mitch 3894 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Sep 22 00:27:26 2018 HibernationDevice: RESUME=UUID=d312420c-13df-48ae-9f72-e529f9de1a33 InstallationDate: Installed on 2017-04-24 (515 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: System76, Inc. Kudu ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-34-generic root=UUID=7a07e949-7c6b-40db-bff1-f3ae8ef18501 ro acpi_backlight=vendor quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-34-generic N/A linux-backports-modules-4.15.0-34-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/31/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.08RSA1 dmi.board.asset.tag: Tag 12345 dmi.board.name: Kudu dmi.board.vendor: System76, Inc. dmi.board.version: kudu2 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: System76, Inc. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.08RSA1:bd03/31/2016:svnSystem76,Inc.:pnKudu:pvrkudu2:rvnSystem76,Inc.:rnKudu:rvrkudu2:cvnSystem76,Inc.:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: Kudu dmi.product.version: kudu2 dmi.sys.vendor: System76, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1793849/+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 1797538] Re: watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kworker/0:1:85]
Still happening on 4.19.6-041906. -- 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/1797538 Title: watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kworker/0:1:85] Status in linux package in Ubuntu: Confirmed Bug description: Dell XPS 15 9570 ProblemType: KernelOops DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-8-generic 4.18.0-8.9 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rob2250 F pulseaudio Date: Fri Oct 12 08:54:08 2018 Failure: oops InstallationDate: Installed on 2018-10-12 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. XPS 15 9570 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic root=UUID=b1c8d7c6-d9ec-495c-9770-18e7120e87d5 ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: kerneloops-daemon N/A SourcePackage: linux Title: watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kworker/0:1:85] UpgradeStatus: Upgraded to cosmic on 2018-10-12 (0 days ago) dmi.bios.date: 09/03/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.0 dmi.board.name: 0D0T05 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.0:bd09/03/2018:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0D0T05:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9570 dmi.product.sku: 087C dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797538/+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 1797538] Re: watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kworker/0:1:85]
Still happening on 4.20.0-042000rc4 as well. http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.20-rc4/ -- 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/1797538 Title: watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kworker/0:1:85] Status in linux package in Ubuntu: Confirmed Bug description: Dell XPS 15 9570 ProblemType: KernelOops DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-8-generic 4.18.0-8.9 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rob2250 F pulseaudio Date: Fri Oct 12 08:54:08 2018 Failure: oops InstallationDate: Installed on 2018-10-12 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. XPS 15 9570 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic root=UUID=b1c8d7c6-d9ec-495c-9770-18e7120e87d5 ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: kerneloops-daemon N/A SourcePackage: linux Title: watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kworker/0:1:85] UpgradeStatus: Upgraded to cosmic on 2018-10-12 (0 days ago) dmi.bios.date: 09/03/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.0 dmi.board.name: 0D0T05 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.0:bd09/03/2018:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0D0T05:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9570 dmi.product.sku: 087C dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797538/+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 1805244] Re: linux-azure: 4.18.0-1006.6 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Incomplete => Fix Released ** Description changed: This bug is for tracking the 4.18.0-1006.6 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1802743 phase: Promoted to proposed phase-changed: Tuesday, 27. November 2018 15:36 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Testing FAILED + promote-to-security: Master bug not ready for release + promote-to-updates: Master bug not ready for release stakeholder-signoff: Waiting for signoff -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1805244 Title: linux-azure: 4.18.0-1006.6 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Cosmic: Confirmed Bug description: This bug is for tracking the 4.18.0-1006.6 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1802743 phase: Promoted to proposed phase-changed: Tuesday, 27. November 2018 15:36 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Master bug not ready for release promote-to-updates: Master bug not ready for release stakeholder-signoff: Waiting for signoff To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1805244/+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 1594023] Re: Poweroff or reboot hangs. Laptop won't shutdown. 16.04
The same issue is also reproducible for me on my HP Pavilion N004tx laptop. I'm using Ubuntu 18.10. -- 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/1594023 Title: Poweroff or reboot hangs. Laptop won't shutdown. 16.04 Status in linux package in Ubuntu: Confirmed Bug description: This is about a fresh Ubuntu 16.04 install on a new laptop (asus x540sa). After pressing the shutdown button in the start menu; the shutdown procedure starts and in the final splash screen the system just hangs. Tried a second time by pressing Esc once the splash screen showed up and I saw that it reaches the line "Reached target shutdown" and just stops there, no matter how long I leave it there the machine won't turn off. I also tried a Kubuntu 16.04 fresh install on the same machine and it hanged too at the final splash screen where the pulsating logo stopped. Then I tried with Esc only to see the exact same line in the end. The issue seems to affect lately quite many users as shown by the google results of the past month / week or so. I have also tried shutting down from the console with shutdown -and all the parameters after that suggested online- and sudo poweroff but unfortunately they didn't do the trick. The exact same situation occurred. Unmounting the swap as suggested online doesn't work. Also rebooting the system is not working either due to the same issue. So right now the only way for me to poweroff the machine is to press the power button on the keyboard continuously. Reproducible: Always Steps to Reproduce: 1.Install OS 2.Do something, anything or nothing 3.Try to shutdown or reboot Actual Results: The computer is not shutting down: "Reached target shutdown" and hangs there. Expected Results: Powering off the machine. For what it's worth, closing the lid won't suspend the system, but using the menu buttons for suspension will do it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1594023/+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