[Kernel-packages] [Bug 1775412] Re: no internet on resume from suspend
If the ethernet is r8169, then it's probably LP: #1752772. -- 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/1775412 Title: no internet on resume from suspend Status in linux package in Ubuntu: Incomplete Bug description: Whenever I suspend my system (in Ubuntu Budgie 18.04) and then resume from suspend, I have no internet connection until I reboot. Restarting the networking service and unplugging/replugging doesn't fix it. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-22-generic 4.15.0-22.24 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Wed Jun 6 10:31:10 2018 InstallationDate: Installed on 2018-06-04 (1 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775412/+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 1776052] [NEW] package linux-generic 4.15.0.22.23 failed to install/upgrade: problèmes de dépendances - laissé non configuré
Public bug reported: The bug was at the launch of the system ProblemType: Package DistroRelease: Ubuntu 18.04 Package: linux-generic 4.15.0.22.23 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: kpatch_livepatch_Ubuntu_4_15_0_20_21_generic_39 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1142 F pulseaudio pierre 1485 F pulseaudio Date: Sun Jun 10 09:56:58 2018 ErrorMessage: problèmes de dépendances - laissé non configuré MachineType: Hewlett-Packard HP EliteBook 2530p ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=2dd1a5f1-67b2-413f-a65f-399333defd20 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. Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.02-2ubuntu8 SourcePackage: linux Title: package linux-generic 4.15.0.22.23 failed to install/upgrade: problèmes de dépendances - laissé non configuré UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/04/2013 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68PSU Ver. F.22 dmi.board.name: 30E1 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 03.27 dmi.chassis.asset.tag: CZC09040J8 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68PSUVer.F.22:bd01/04/2013:svnHewlett-Packard:pnHPEliteBook2530p:pvrF.22:rvnHewlett-Packard:rn30E1:rvrKBCVersion03.27:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.name: HP EliteBook 2530p dmi.product.version: F.22 dmi.sys.vendor: Hewlett-Packard ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- 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/1776052 Title: package linux-generic 4.15.0.22.23 failed to install/upgrade: problèmes de dépendances - laissé non configuré Status in linux package in Ubuntu: New Bug description: The bug was at the launch of the system ProblemType: Package DistroRelease: Ubuntu 18.04 Package: linux-generic 4.15.0.22.23 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: kpatch_livepatch_Ubuntu_4_15_0_20_21_generic_39 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1142 F pulseaudio pierre 1485 F pulseaudio Date: Sun Jun 10 09:56:58 2018 ErrorMessage: problèmes de dépendances - laissé non configuré MachineType: Hewlett-Packard HP EliteBook 2530p ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=2dd1a5f1-67b2-413f-a65f-399333defd20 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. Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.02-2ubuntu8 SourcePackage: linux Title: package linux-generic 4.15.0.22.23 failed to install/upgrade: problèmes de dépendances - laissé non configuré UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/04/2013 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68PSU Ver. F.22 dmi.board.name: 30E1 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 03.27 dmi.chassis.asset.tag: CZC09040J8 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68PSUVer.F.22:bd01/04/2013:svnHewlett-Packard:pnHPEliteBook2530p:pvrF.22:rvnHewlett-Packard:rn30E1:rvrKBCVersion03.27:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.name: HP EliteBook 2530p dmi.product.version: F.22 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776052/+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 1734243] Re: Intel 9260/9462/9560 firmware support
What is the support status of 9462 on Bionic? Does not appear to be working. -- 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/1734243 Title: Intel 9260/9462/9560 firmware support Status in HWE Next: Fix Released Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Xenial: Fix Released Status in linux-firmware source package in Zesty: Won't Fix Status in linux-firmware source package in Artful: Fix Released Bug description: SRU Justification [Impact] Intel 9260/9462/9560 require new firmwares to enable them. [ 7.492326] iwlwifi :00:0c.0: Direct firmware load for iwlwifi-9000-pu-a0-jf-b0-33.ucode failed with error -2 [ 7.492349] iwlwifi :00:0c.0: Direct firmware load for iwlwifi-9000-pu-a0-jf-b0-32.ucode failed with error -2 [ 7.492362] iwlwifi :00:0c.0: Direct firmware load for iwlwifi-9000-pu-a0-jf-b0-31.ucode failed with error -2 [ 7.492375] iwlwifi :00:0c.0: Direct firmware load for iwlwifi-9000-pu-a0-jf-b0-30.ucode failed with error -2 [ 7.492378] iwlwifi :00:0c.0: no suitable firmware found! For v4.13 kernel, it uses firmware version 33, so we only need this. commit c4276b65390d32d33c8263a7e3c8be0db8cccad4 (tag: refs/tags/iwlwifi-fw-2017-11-03) Author: Luca Coelho Date: Fri Oct 13 14:22:26 2017 +0300 iwlwifi: add firmware version 33 for new 9000 series Build number: WFFW53774_R30_FW610294 Revision number: 610294 Signed-off-by: Luca Coelho [Test Case] After applying the firmwares, confirm the 9260/9560 can connect to 6 different APs(bg/n/ac * open/wap) [Regression Potential] There is no regression for the new devices and new firmwares. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1734243/+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 1776052] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1776052 Title: package linux-generic 4.15.0.22.23 failed to install/upgrade: problèmes de dépendances - laissé non configuré Status in linux package in Ubuntu: Confirmed Bug description: The bug was at the launch of the system ProblemType: Package DistroRelease: Ubuntu 18.04 Package: linux-generic 4.15.0.22.23 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: kpatch_livepatch_Ubuntu_4_15_0_20_21_generic_39 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1142 F pulseaudio pierre 1485 F pulseaudio Date: Sun Jun 10 09:56:58 2018 ErrorMessage: problèmes de dépendances - laissé non configuré MachineType: Hewlett-Packard HP EliteBook 2530p ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=2dd1a5f1-67b2-413f-a65f-399333defd20 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. Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.02-2ubuntu8 SourcePackage: linux Title: package linux-generic 4.15.0.22.23 failed to install/upgrade: problèmes de dépendances - laissé non configuré UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/04/2013 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68PSU Ver. F.22 dmi.board.name: 30E1 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 03.27 dmi.chassis.asset.tag: CZC09040J8 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68PSUVer.F.22:bd01/04/2013:svnHewlett-Packard:pnHPEliteBook2530p:pvrF.22:rvnHewlett-Packard:rn30E1:rvrKBCVersion03.27:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.name: HP EliteBook 2530p dmi.product.version: F.22 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776052/+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 1771749] Re: Ethernet connection lost after few minutes since starting
What's kernel version do you use in Xenial LTS? -- 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/1771749 Title: Ethernet connection lost after few minutes since starting Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: This is the same bug I notified at Bug #1770848 but with a more precise selection of (what I think it is) the package affected and a better description. I made a few days ago a fresh install of the Kubuntu 18.04 LTS and it is most everything Ok, but -I think that- the network-manager has a problem. In the last LTS version, Kubuntu 16.04, nor in any Linux version if I remember well, I never lost connection through Ethernet (the only Internet connection with our desktop PC), but the Bionic Beaver loses the connection every now and then, perhaps within few minutes or hours, but several times per day. When the connection is lost, I note that it disappears any info even mention to any network into the network window and the network manager icon becomes red color. Not matter if I unplug and then plug the ethernet cable again, the ethernet connection is not longer detected and only restarting the PC makes the connection to work again. Incidentally, I also have noticed with this version of Kubuntu 18.04 that in my laptop there is also now a similar problem with the scanner: If I plug it in some USB port of the laptop once Kubuntu 18.04 is already running, it's not detected by Xsane. I have to plug it in before than pressing the power button or at the time of starting the OS, for the scanner to be detected by the scanning program (and then only works with Xsane, not if I use Simple Scan or Skanlite, even when it works under Xsane), as I said in the Bug #1771525 and, evenly, if I unplug the scanner cable from the USB port it is not detected anymore when plugging it again, and only restarting the laptop makes it to be detected. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.6-2ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: KDE Date: Thu May 17 08:24:23 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-05-11 (5 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IpRoute: default via 192.168.1.1 dev enp0s7 proto static metric 100 169.254.0.0/16 dev enp0s7 scope link metric 1000 192.168.1.0/24 dev enp0s7 proto kernel scope link src 192.168.1.3 metric 100 IwConfig: enp0s7no wireless extensions. lono wireless extensions. NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true PciNetwork: RfKill: SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE Conexión cableada 1 1cc37db8-0db8-3887-acf2-59fbbcd0cb1c ethernet 1526538083 jue 17 may 2018 08:21:23 CEST yes 4294967196 no/org/freedesktop/NetworkManager/Settings/1 yes enp0s7 activated /org/freedesktop/NetworkManager/ActiveConnection/1 -- nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH enp0s7 ethernet connected /org/freedesktop/NetworkManager/Devices/2 Conexión cableada 1 1cc37db8-0db8-3887-acf2-59fbbcd0cb1c /org/freedesktop/NetworkManager/ActiveConnection/1 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.6 connected started full enabled enabled enabled enabled enabled --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nosotros 1116 F pulseaudio /dev/snd/controlC1: nosotros 1116 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=bb1531db-e7c0-48eb-a5b7-5afe3df47ba3 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback I
[Kernel-packages] [Bug 1748853] Re: Intel 9462 A370:42A4 doesn't work
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1748853 Title: Intel 9462 A370:42A4 doesn't work Status in HWE Next: Fix Released Status in Linux: Incomplete Status in linux package in Ubuntu: Confirmed Status in linux-oem package in Ubuntu: Invalid Status in linux source package in Xenial: Invalid Status in linux-oem source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Committed Status in linux-oem source package in Bionic: Invalid Bug description: [Impact] The PCI ID [A370:42A4] is not included in iwlwifi driver, so that Intel 9462 with that ID won't work. [Fix] According the 2 patches sent to 4.15 stable, which were not be included before 4.15 EOL, so we cherry pick the 2 patches to Ubuntu 4.15 kernel. https://www.spinics.net/lists/stable/msg235420.html [Regression Potential] Adding IDs, no regression could be happened To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1748853/+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 1767324] Re: Extreme regression in battery autonomy with kernel 4.15
As per jacob's comment have added the tag and changed to Confirmed, Joseph do you know how this bug should be progressed? Where it should be forwarded upstream or what further debug work could be done? A test against a yet newer kernel probably wouldn't go amiss but not sure not doing that should put the bug back to Incomplete since then we may always be behind. ** Tags added: kernel-bug-exists-upstream ** 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/1767324 Title: Extreme regression in battery autonomy with kernel 4.15 Status in linux package in Ubuntu: Confirmed Bug description: Since upgrading to kernel 4.15, my laptop (HP Elitebook 850 G3) lasts less than one hour on a fully charged battery. On Ubuntu 17.10 with kernel 4.13, the autonomy was typically in excess of 5 hours. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-lowlatency 4.15.0.20.23 ProcVersionSignature: Ubuntu 4.15.0-20.21-lowlatency 4.15.17 Uname: Linux 4.15.0-20-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jzimm 3538 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Apr 27 20:10:02 2018 InstallationDate: Installed on 2018-04-03 (24 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180402) MachineType: HP HP EliteBook 850 G3 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/bionic/vmlinuz-4.15.0-20-lowlatency root=UUID=b6480aee-7c63-4ce4-9e8d-cdbef768b982 ro rootflags=subvol=@,relatime,autodefrag,space_cache quiet splash module.sig_enforce=1 intel_pstate=skylake_hwp radeon.si_support=0 radeon.cik_support=0 amdgpu.si_support=1 amdgpu.cik_support=1 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-lowlatency N/A linux-backports-modules-4.15.0-20-lowlatency N/A linux-firmware1.173 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/31/2016 dmi.bios.vendor: HP dmi.bios.version: N75 Ver. 01.10 dmi.board.name: 8079 dmi.board.vendor: HP dmi.board.version: KBC Version 85.6F dmi.chassis.asset.tag: 5CG6351LQL dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrN75Ver.01.10:bd07/31/2016:svnHP:pnHPEliteBook850G3:pvr:rvnHP:rn8079:rvrKBCVersion85.6F:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI dmi.product.name: HP EliteBook 850 G3 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1767324/+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 1734243] Re: Intel 9260/9462/9560 firmware support
Bug #1748853 “Intel 9462 A370:42A4 doesn't work” is tracking the issue for Bionic -- 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/1734243 Title: Intel 9260/9462/9560 firmware support Status in HWE Next: Fix Released Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Xenial: Fix Released Status in linux-firmware source package in Zesty: Won't Fix Status in linux-firmware source package in Artful: Fix Released Bug description: SRU Justification [Impact] Intel 9260/9462/9560 require new firmwares to enable them. [ 7.492326] iwlwifi :00:0c.0: Direct firmware load for iwlwifi-9000-pu-a0-jf-b0-33.ucode failed with error -2 [ 7.492349] iwlwifi :00:0c.0: Direct firmware load for iwlwifi-9000-pu-a0-jf-b0-32.ucode failed with error -2 [ 7.492362] iwlwifi :00:0c.0: Direct firmware load for iwlwifi-9000-pu-a0-jf-b0-31.ucode failed with error -2 [ 7.492375] iwlwifi :00:0c.0: Direct firmware load for iwlwifi-9000-pu-a0-jf-b0-30.ucode failed with error -2 [ 7.492378] iwlwifi :00:0c.0: no suitable firmware found! For v4.13 kernel, it uses firmware version 33, so we only need this. commit c4276b65390d32d33c8263a7e3c8be0db8cccad4 (tag: refs/tags/iwlwifi-fw-2017-11-03) Author: Luca Coelho Date: Fri Oct 13 14:22:26 2017 +0300 iwlwifi: add firmware version 33 for new 9000 series Build number: WFFW53774_R30_FW610294 Revision number: 610294 Signed-off-by: Luca Coelho [Test Case] After applying the firmwares, confirm the 9260/9560 can connect to 6 different APs(bg/n/ac * open/wap) [Regression Potential] There is no regression for the new devices and new firmwares. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1734243/+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 1748853] Re: Intel 9462 A370:42A4 doesn't work
Installed kernel 4.15.0-23.25 from bionic-proposed, Intel 9462NGW started working (Network controller [0280]: Intel Corporation Device [8086:a370] (rev 10)) For those with Nvidia binary driver, install linux-header-generic as well from bionic-proposed and reinstall nvidia driver to let dkms build the module for new kernel. -- 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/1748853 Title: Intel 9462 A370:42A4 doesn't work Status in HWE Next: Fix Released Status in Linux: Incomplete Status in linux package in Ubuntu: Confirmed Status in linux-oem package in Ubuntu: Invalid Status in linux source package in Xenial: Invalid Status in linux-oem source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Committed Status in linux-oem source package in Bionic: Invalid Bug description: [Impact] The PCI ID [A370:42A4] is not included in iwlwifi driver, so that Intel 9462 with that ID won't work. [Fix] According the 2 patches sent to 4.15 stable, which were not be included before 4.15 EOL, so we cherry pick the 2 patches to Ubuntu 4.15 kernel. https://www.spinics.net/lists/stable/msg235420.html [Regression Potential] Adding IDs, no regression could be happened To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1748853/+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 1625610] Re: Renesas USB3 (uPD720200) does not recognize USB3 devices
I have followed instructions on https://askubuntu.com/questions/161862 /nec-upd720200-usb-3-0-not-working-on-ubuntu-12-04 . Firmware update did not change anything: board is recognized, but plugging a device has no effect, no log in dmesg, nothing. lsusb -t reports no device attached. -- 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/1625610 Title: Renesas USB3 (uPD720200) does not recognize USB3 devices Status in linux package in Ubuntu: Expired Bug description: first: the whole system runs fine with windows 7 and USB3 devices on the USB3 host controller. i am now running Ubuntu 16.04 on this MSI MS-7666 x58 Big Bang XPower (2x USB3 sockets on the backplane outlet). i have switched to the latest firmware (3.0.3.4) for NEC/Renesas uPD720200 by flashing it but no evidence with "lsusb -t" that the plugged USB3 device is present at all. plugging the device to some USB2 port makes it work nicely. the bios (latest AMI BIOS 1.17) does not offer anything looking at least barely useful to me for this USB3 problem other than "legacy support at boot time" but this had no effect at all - as i feared. (this lack of options is probably unlike what other Board/BIOS do offer.) excerpt from kern.log: Sep 19 22:35:23 dtaa-flc21 kernel: [ 57.575918] usb 2-5: USB disconnect, device number 3 Sep 19 22:35:27 dtaa-flc21 kernel: [ 62.009193] usb 10-2: Device not responding to setup address. Sep 19 22:35:27 dtaa-flc21 kernel: [ 62.213145] usb 10-2: Device not responding to setup address. Sep 19 22:35:27 dtaa-flc21 kernel: [ 62.417026] usb 10-2: device not accepting address 2, error -71 Sep 19 22:35:28 dtaa-flc21 kernel: [ 62.997097] usb 10-2: new SuperSpeed USB device number 3 using xhci_hcd Sep 19 22:35:33 dtaa-flc21 kernel: [ 68.016941] usb 10-2: device descriptor read/all, error -110 Sep 19 22:35:36 dtaa-flc21 kernel: [ 70.564860] usb 10-2: new SuperSpeed USB device number 5 using xhci_hcd Sep 19 22:35:41 dtaa-flc21 kernel: [ 75.580568] usb 10-2: unable to get BOS descriptor Sep 19 22:35:41 dtaa-flc21 kernel: [ 75.581491] usb 10-2: unable to read config index 0 descriptor/start: -71 Sep 19 22:35:41 dtaa-flc21 kernel: [ 75.581496] usb 10-2: can't read configurations, error -71 Sep 19 22:43:43 dtaa-flc21 kernel: [ 558.099596] xhci_hcd :0d:00.0: port 1 resume PLC timeout note: a similar problem but for a different USB3 host controller model can be found here. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1242321?comments=all To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1625610/+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 1776075] [NEW] Bluetooth Problem
You have been subscribed to a public bug: Ich kann Bluetooth nicht Aktivieren ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-127.153-generic 4.4.128 Uname: Linux 4.4.0-127-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sun Jun 10 14:59:59 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7400G] [1002:9994] (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd Trinity [Radeon HD 7400G] [144d:c660] InstallationDate: Installed on 2015-11-17 (935 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) MachineType: SAMSUNG ELECTRONICS CO., LTD. 535U3C ProcEnviron: LANGUAGE=de_DE PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-127-generic.efi.signed root=UUID=5b7ab83e-d739-434f-afc7-78ed793a51a1 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/25/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P04RAS.W68.121025.LEO dmi.board.asset.tag: No Asset Tag dmi.board.name: NP535U3C-A03DE dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SEC_SW_REVISION_1234567890ABCD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP04RAS.W68.121025.LEO:bd10/25/2012:svnSAMSUNGELECTRONICSCO.,LTD.:pn535U3C:pvrP04RAS:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP535U3C-A03DE:rvrSEC_SW_REVISION_1234567890ABCD:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A: dmi.product.name: 535U3C dmi.product.version: P04RAS dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Sun Jun 10 14:07:04 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.7 xserver.video_driver: radeon ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial -- Bluetooth Problem https://bugs.launchpad.net/bugs/1776075 You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1776075] Re: Bluetooth Problem
** Package changed: xorg (Ubuntu) => bluez (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1776075 Title: Bluetooth Problem Status in bluez package in Ubuntu: New Bug description: Ich kann Bluetooth nicht Aktivieren ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-127.153-generic 4.4.128 Uname: Linux 4.4.0-127-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sun Jun 10 14:59:59 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7400G] [1002:9994] (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd Trinity [Radeon HD 7400G] [144d:c660] InstallationDate: Installed on 2015-11-17 (935 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) MachineType: SAMSUNG ELECTRONICS CO., LTD. 535U3C ProcEnviron: LANGUAGE=de_DE PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-127-generic.efi.signed root=UUID=5b7ab83e-d739-434f-afc7-78ed793a51a1 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/25/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P04RAS.W68.121025.LEO dmi.board.asset.tag: No Asset Tag dmi.board.name: NP535U3C-A03DE dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SEC_SW_REVISION_1234567890ABCD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP04RAS.W68.121025.LEO:bd10/25/2012:svnSAMSUNGELECTRONICSCO.,LTD.:pn535U3C:pvrP04RAS:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP535U3C-A03DE:rvrSEC_SW_REVISION_1234567890ABCD:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A: dmi.product.name: 535U3C dmi.product.version: P04RAS dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Sun Jun 10 14:07:04 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.7 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1776075/+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 1771749] Re: Ethernet connection lost after few minutes since starting
I don't know which kernel version I did use in Xenial (initially I used the normal one, the kernel installed by default, but then I installed UKUU so couldn't remember, but I never had this problem with previous versions of Kubuntu nor any other flavor of Ubuntu nor in any Linux distro, for the case. -- 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/1771749 Title: Ethernet connection lost after few minutes since starting Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: This is the same bug I notified at Bug #1770848 but with a more precise selection of (what I think it is) the package affected and a better description. I made a few days ago a fresh install of the Kubuntu 18.04 LTS and it is most everything Ok, but -I think that- the network-manager has a problem. In the last LTS version, Kubuntu 16.04, nor in any Linux version if I remember well, I never lost connection through Ethernet (the only Internet connection with our desktop PC), but the Bionic Beaver loses the connection every now and then, perhaps within few minutes or hours, but several times per day. When the connection is lost, I note that it disappears any info even mention to any network into the network window and the network manager icon becomes red color. Not matter if I unplug and then plug the ethernet cable again, the ethernet connection is not longer detected and only restarting the PC makes the connection to work again. Incidentally, I also have noticed with this version of Kubuntu 18.04 that in my laptop there is also now a similar problem with the scanner: If I plug it in some USB port of the laptop once Kubuntu 18.04 is already running, it's not detected by Xsane. I have to plug it in before than pressing the power button or at the time of starting the OS, for the scanner to be detected by the scanning program (and then only works with Xsane, not if I use Simple Scan or Skanlite, even when it works under Xsane), as I said in the Bug #1771525 and, evenly, if I unplug the scanner cable from the USB port it is not detected anymore when plugging it again, and only restarting the laptop makes it to be detected. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.6-2ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: KDE Date: Thu May 17 08:24:23 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-05-11 (5 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IpRoute: default via 192.168.1.1 dev enp0s7 proto static metric 100 169.254.0.0/16 dev enp0s7 scope link metric 1000 192.168.1.0/24 dev enp0s7 proto kernel scope link src 192.168.1.3 metric 100 IwConfig: enp0s7no wireless extensions. lono wireless extensions. NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true PciNetwork: RfKill: SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE Conexión cableada 1 1cc37db8-0db8-3887-acf2-59fbbcd0cb1c ethernet 1526538083 jue 17 may 2018 08:21:23 CEST yes 4294967196 no/org/freedesktop/NetworkManager/Settings/1 yes enp0s7 activated /org/freedesktop/NetworkManager/ActiveConnection/1 -- nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH enp0s7 ethernet connected /org/freedesktop/NetworkManager/Devices/2 Conexión cableada 1 1cc37db8-0db8-3887-acf2-59fbbcd0cb1c /org/freedesktop/NetworkManager/ActiveConnection/1 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.6 connected started full enabled enabled enabled enabled enabled --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nosotros 1116 F pulseaudio /dev/snd/controlC1: nosotros 11
[Kernel-packages] [Bug 1726159] Re: PCIe BUS Error causing really slow laptop performance
I fixed the slow booting problem by editing "/etc/hdparm.conf" and changing "apm_battery" value to "255". Now my laptop boots normally on battery mode (same speed as plugged in AC). Now, for the AER problem, just ignore it. Add pci=noaer as kernel boot parameter. I hope I helped. -- 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/1726159 Title: PCIe BUS Error causing really slow laptop performance Status in linux package in Ubuntu: Confirmed Bug description: I recently bought the following laptop: Asus VivoBook X542UQ-DM148T - 15.6" (i7-7500U/8GB/256GB/GT 940MX 2GB) It came pre-installed with Win10 and I did a fresh install of Ubuntu 16.04 LTS. The screen was flickering for some reason and installing Ubuntu 17.04 fixed the issue. The real problem is that when I'm booting the laptop, the following error is being shown on my screen: [ 12.866073] pcieport :00:1c.5: can't find device of ID00e5 [ 12.898481] pcieport :00:1c.5: AER: Multiple Corrected error received: id=00e5 [ 12.898488] pcieport :00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID) [ 12.898491] pcieport :00:1c.5: device [8086:9d15] error status/mask=2041/2000 [ 12.898492] pcieport :00:1c.5:[ 0] Receiver Error (First) [ 12.898493] pcieport :00:1c.5:[ 6] Bad TLP I know that this error can be hid with one of the following kernel boot arguments: pci=nomsi / pci=noaer / pcie_aspm=off / pci=nommconf. The weird thing is that the above output is only being shown when the laptop is on AC Power (charging). When the laptop is not connected to AC (battery-mode), it has performance issues (slow boot and slow application launching). I was trying all day long to fix the problem. I removed everything that had to do with power-saving, reinstalled, re-tweaked for performance, tried different kernels but had no luck. While diagnosing, I had the idea to benchmark the "M2 SATA-3 SSD" that my laptop had. The results are: * On AC Power: 522MB/s (READ) | 416MB/s (WRITE) * On Battery Power: 32MB/s (READ) | 31MB/s (WRITE) This explains everyting. That's why I'm having a slow boot and slow application launching! Commands "lspci" and "dmesg" say that the error comes from the following device: 00:1c.5 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #6 (rev f1) I will attach lspci and dmesg output on a tar.gz file. -- UPDATE: When the laptop is fully charged and still on AC (but not charging since it is 100% charged), the errors appear again but the SSD speed is normal (~500 Read/Write). -- UPDATE: I installed 'tlp' Advanced Power Management package and when using the command 'tlp ac', the SSD speed gets back to normal! The option does not persist across reboots. -- ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-37-generic 4.10.0-37.41 ProcVersionSignature: Ubuntu 4.10.0-37.41-generic 4.10.17 Uname: Linux 4.10.0-37-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: georgem2557 F pulseaudio CurrentDesktop: Unity:Unity7 Date: Sun Oct 22 23:17:57 2017 InstallationDate: Installed on 2017-10-20 (2 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 13d3:3496 IMC Networks Bus 001 Device 003: ID 13d3:5a01 IMC Networks Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X542UQ ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-37-generic.efi.signed root=UUID=38d32efc-d0cb-4a82-9e6c-e6a3bd62e51d ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.10.0-37-generic N/A linux-backports-modules-4.10.0-37-generic N/A linux-firmware 1.164.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/18/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X542UQ.202 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X542UQ dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX542UQ.202:bd05/18/2017:svnASUS
[Kernel-packages] [Bug 1776108] [NEW] Resume after hibernate/suspend fails
Public bug reported: Fresh/clean install of 18.04 resulted in hibernation working (after it being broken on an upgrade install). Now after rebooting after recent package upgrades (last 4-5 days) resuming from suspend/hibernate fails. Have to force hard reboot Last message in syslog is: PM: suspend entry (deep) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-22-generic 4.15.0-22.24 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: petter 1475 F pulseaudio /dev/snd/controlC0: petter 1475 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Jun 10 22:34:32 2018 HibernationDevice: RESUME=UUID=8f436028-c350-445e-85dc-115d58d47796 InstallationDate: Installed on 2018-05-18 (23 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IwConfig: lono wireless extensions. enp5s0no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=sv_SE.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=bc80c3a6-55ef-4636-ac7a-d7bd837b6320 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173.1 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/14/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F22 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z77-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF22:bd11/14/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ77-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Attachment added: "lspci-vnvn.log" https://bugs.launchpad.net/bugs/1776108/+attachment/5151020/+files/lspci-vnvn.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1776108 Title: Resume after hibernate/suspend fails Status in linux package in Ubuntu: New Bug description: Fresh/clean install of 18.04 resulted in hibernation working (after it being broken on an upgrade install). Now after rebooting after recent package upgrades (last 4-5 days) resuming from suspend/hibernate fails. Have to force hard reboot Last message in syslog is: PM: suspend entry (deep) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-22-generic 4.15.0-22.24 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: petter 1475 F pulseaudio /dev/snd/controlC0: petter 1475 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Jun 10 22:34:32 2018 HibernationDevice: RESUME=UUID=8f436028-c350-445e-85dc-115d58d47796 InstallationDate: Installed on 2018-05-18 (23 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IwConfig: lono wireless extensions. enp5s0no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=sv_SE.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=bc80c3a6-55ef-4636-ac7a-d7bd837b6320 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173.1 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/14/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F22 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z77-D3H dmi.board.vendor: Gigabyte T
[Kernel-packages] [Bug 1776108] Re: Resume after hibernate/suspend fails
** Attachment added: "version.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776108/+attachment/5151034/+files/version.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1776108 Title: Resume after hibernate/suspend fails Status in linux package in Ubuntu: New Bug description: Fresh/clean install of 18.04 resulted in hibernation working (after it being broken on an upgrade install). Now after rebooting after recent package upgrades (last 4-5 days) resuming from suspend/hibernate fails. Have to force hard reboot Last message in syslog is: PM: suspend entry (deep) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-22-generic 4.15.0-22.24 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: petter 1475 F pulseaudio /dev/snd/controlC0: petter 1475 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Jun 10 22:34:32 2018 HibernationDevice: RESUME=UUID=8f436028-c350-445e-85dc-115d58d47796 InstallationDate: Installed on 2018-05-18 (23 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IwConfig: lono wireless extensions. enp5s0no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=sv_SE.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=bc80c3a6-55ef-4636-ac7a-d7bd837b6320 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173.1 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/14/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F22 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z77-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF22:bd11/14/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ77-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776108/+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 1776108] Re: Resume after hibernate/suspend fails
Tried both 390 and 396 versions of nvidia-driver, both fail suspend resume. Tried Nouveau and resume works. So suspend resume worked on nvidia-390 w/ kernel 4.15.0-20, possibly not but probably with -22... -- 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/1776108 Title: Resume after hibernate/suspend fails Status in linux package in Ubuntu: Confirmed Bug description: Fresh/clean install of 18.04 resulted in hibernation working (after it being broken on an upgrade install). Now after rebooting after recent package upgrades (last 4-5 days) resuming from suspend/hibernate fails. Have to force hard reboot Last message in syslog is: PM: suspend entry (deep) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-22-generic 4.15.0-22.24 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: petter 1475 F pulseaudio /dev/snd/controlC0: petter 1475 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Jun 10 22:34:32 2018 HibernationDevice: RESUME=UUID=8f436028-c350-445e-85dc-115d58d47796 InstallationDate: Installed on 2018-05-18 (23 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IwConfig: lono wireless extensions. enp5s0no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=sv_SE.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=bc80c3a6-55ef-4636-ac7a-d7bd837b6320 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173.1 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/14/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F22 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z77-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF22:bd11/14/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ77-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776108/+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 1776108] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1776108 Title: Resume after hibernate/suspend fails Status in linux package in Ubuntu: Confirmed Bug description: Fresh/clean install of 18.04 resulted in hibernation working (after it being broken on an upgrade install). Now after rebooting after recent package upgrades (last 4-5 days) resuming from suspend/hibernate fails. Have to force hard reboot Last message in syslog is: PM: suspend entry (deep) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-22-generic 4.15.0-22.24 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: petter 1475 F pulseaudio /dev/snd/controlC0: petter 1475 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Jun 10 22:34:32 2018 HibernationDevice: RESUME=UUID=8f436028-c350-445e-85dc-115d58d47796 InstallationDate: Installed on 2018-05-18 (23 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IwConfig: lono wireless extensions. enp5s0no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=sv_SE.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=bc80c3a6-55ef-4636-ac7a-d7bd837b6320 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173.1 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/14/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F22 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z77-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF22:bd11/14/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ77-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776108/+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 1776113] [NEW] Laptop does not suspend when lid is closed
Public bug reported: $ lsb_release -rd Description:Ubuntu 18.04 LTS Release:18.04 In Tweaks > Power, "Suspend when laptop lid is closed" is ON, but my laptop does not suspend when the lid is closed. The laptop is a Thinkpad P50. When closing the laptop lid, no events show up in dmesg. This is my /etc/systemd/login.conf: [Login] #NAutoVTs=6 #ReserveVT=6 #KillUserProcesses=no #KillOnlyUsers= #KillExcludeUsers=root #InhibitDelayMaxSec=5 #HandlePowerKey=poweroff #HandleSuspendKey=suspend #HandleHibernateKey=hibernate HandleLidSwitch=suspend HandleLidSwitchDocked=suspend #PowerKeyIgnoreInhibited=no #SuspendKeyIgnoreInhibited=no #HibernateKeyIgnoreInhibited=no #LidSwitchIgnoreInhibited=yes #HoldoffTimeoutSec=30s #IdleAction=ignore #IdleActionSec=30min #RuntimeDirectorySize=10% #RemoveIPC=yes #InhibitorsMax=8192 #SessionsMax=8192 #UserTasksMax=33% ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-22-generic 4.15.0-22.24 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Jun 10 14:16:10 2018 InstallationDate: Installed on 2018-03-26 (76 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed UpgradeStatus: Upgraded to bionic on 2018-05-17 (24 days ago) ** Affects: linux-signed (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1776113 Title: Laptop does not suspend when lid is closed Status in linux-signed package in Ubuntu: New Bug description: $ lsb_release -rd Description: Ubuntu 18.04 LTS Release: 18.04 In Tweaks > Power, "Suspend when laptop lid is closed" is ON, but my laptop does not suspend when the lid is closed. The laptop is a Thinkpad P50. When closing the laptop lid, no events show up in dmesg. This is my /etc/systemd/login.conf: [Login] #NAutoVTs=6 #ReserveVT=6 #KillUserProcesses=no #KillOnlyUsers= #KillExcludeUsers=root #InhibitDelayMaxSec=5 #HandlePowerKey=poweroff #HandleSuspendKey=suspend #HandleHibernateKey=hibernate HandleLidSwitch=suspend HandleLidSwitchDocked=suspend #PowerKeyIgnoreInhibited=no #SuspendKeyIgnoreInhibited=no #HibernateKeyIgnoreInhibited=no #LidSwitchIgnoreInhibited=yes #HoldoffTimeoutSec=30s #IdleAction=ignore #IdleActionSec=30min #RuntimeDirectorySize=10% #RemoveIPC=yes #InhibitorsMax=8192 #SessionsMax=8192 #UserTasksMax=33% ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-22-generic 4.15.0-22.24 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Jun 10 14:16:10 2018 InstallationDate: Installed on 2018-03-26 (76 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed UpgradeStatus: Upgraded to bionic on 2018-05-17 (24 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1776113/+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 1753510] Re: Cannot boot/install AMD Ryzen 2400G
OK, now it dumps into the (initramfs) prompt but at least it doesn´t crash just sitting at that prompt. any suggestions what to do once at the initramfs prompt? -- 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/1753510 Title: Cannot boot/install AMD Ryzen 2400G Status in linux package in Ubuntu: Confirmed Bug description: Did a motherboard swap on a trusty old computer that ran ubuntu for 10 years or so. Now it only runs windows (same hardware fresh installs windows with no issue). brand new ryzen 2nd gen with graphics. I know about graphics drivers issues, wasn't expecting that to be dealt with. Just trying to use it as a cpu. So I put in an older (RADEON HD 7850 pitcairn) video card to get some functionality. Without the video card, it boots, but the display is unusable. I can ssh in and see that it works fine as a server, but cannot use terminal or graphical display. With the video card, Put daily ubuntu Bionic image, and "Try Ubuntu", and it goes into an infinite loop. photo attached. I tried 16.04.4 and I think it just went into a blank screen. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753510/+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 1721987]
>From the given alsa-info.sh output, there is nothing wrong there. So it must be some vendor-specific initialization, and only Huawei knows. Try to contact your vendor. -- 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/1721987 Title: No sound from right audio channel Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: No audio comes out of the right speaker on the laptop. When playing a test video such as https://www.youtube.com/watch?v=hTvJoYnpeRQ the right-channel audio is never heard (i.e., it does not get converted into mono and played through the left speaker). When plugging in headphones, audio is heard from both channels. In Windows, both speakers work, so it is not a physical problem with the speakers. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-12-generic 4.13.0-12.13 [modified: boot/vmlinuz-4.13.0-12-generic] ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 1127 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Oct 7 12:58:01 2017 InstallationDate: Installed on 2017-10-07 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) MachineType: HUAWEI HUAWEI MateBook X ProcEnviron: PATH=(custom, no username) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-12-generic.efi.signed root=UUID=f0a69f35-7c1e-4280-b325-6b7fec6e174a ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-12-generic N/A linux-backports-modules-4.13.0-12-generic N/A linux-firmware 1.168 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/14/2017 dmi.bios.vendor: HUAWEI dmi.bios.version: 1.12 dmi.board.name: HUAWEI MateBook X dmi.board.vendor: HUAWEI dmi.board.version: 2.0 dmi.chassis.type: 10 dmi.chassis.vendor: HUAWEI dmi.modalias: dmi:bvnHUAWEI:bvr1.12:bd08/14/2017:svnHUAWEI:pnHUAWEIMateBookX:pvr2.0:rvnHUAWEI:rnHUAWEIMateBookX:rvr2.0:cvnHUAWEI:ct10:cvr: dmi.product.family: HUAWEI MateBook dmi.product.name: HUAWEI MateBook X dmi.product.version: 2.0 dmi.sys.vendor: HUAWEI To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1721987/+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 1719795]
(In reply to RussianNeuroMancer from comment #15) > As I proceed with bisect (due to various reasons now I have to build inside > virtual machine instead of bare metal hardware, so this slow down building > by few times) I have difficulties with determining what build have to be > marked as good, and what build have to be marked as bad. For example, with > 4.9.44 I seen issue reproduced couple of times, but most of the time it > doesn't happen with this release. With 4.9.3 issue seems like doesn't happen > at all, but if I boot 4.17.0 and then reboot to 4.9.3 - it's there. this is important, please attach the output of "turbostat --debug" and "powertop --html=foo" for both good and bad case, in 4.9.3 kernel. As the problem can also be reproduced on 4.9.3, remove the regression flag for now. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1719795 Title: Dell 7140 avarage power consumption in idle increased by 1.3-1.5 times due to events by INT3432 Status in Linux: Incomplete Status in linux package in Ubuntu: New Bug description: On Dell Venue 11 Pro 7140 average power consumption in idle increased by 1.3-1.5 times due to events coming from INT343A. According to powertop since Linux 4.10 INT3432:00 generate around two hundred events on average, in /sys/devices/pci:00/INT3432:00/i2c-6 there is two devices: INT343A and SMO91D0. AFAIK INT343A is rt286. With Linux 4.9.0-4.9.45, Linux 4.11.0-4.11.12 in idle there is around 100 wakeups per second in sum, battery discharge rate around 3-3.5 Watts per second. But with Linux 4.9.46-4.9.51, Linux 4.10.0-4.10.17, Linux 4.12.0rc1-4.13.3 - around 300 wakeups per second on average, due to events coming from INT3432:00. With Linux 4.13.3 battery discharge rate around 4.5 Watts per second. Probably some commit was backported to Linux 4.9 between .45 and .46 releases. I have no idea why issue is not reproducible on any Linux 4.11 release I tried. Sometimes INT3432 events rate fall from two hundred to one hundred for shorts period of time (for example I observe this right now on Linux 4.10.0 while removing/installing packages). Message like this sometimes appear in dmesg: [ 731.226730] i2c_hid i2c-SMO91D0:00: i2c_hid_get_input: incomplete report (53/13568) Complete dmesg with Linux 4.13.3 is attached. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1719795/+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 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)
I'm having the exact same problem in a clean installation of Ubuntu 18.04. I'm on a Lenovo Legion Y720. Even suspending by command or by closing the lid, it hangs. I can see a dash blinking in top left of the screen. In that stage, the laptop is not completely dead: the numlock button stills toggles the numlock led. But when I hit ctrl-alt-F1, then the blinking dash disappears and numlock button doesn't even work any more. From then, I have to hard reset the machine. My logs look just like the OP described, so the machine actually thinks it went to sleep. It's odd that it doesn't happen all the time. Sometimes it suspends correctly. I'm using nVidia drivers. Some said that driver might be the problem, although some people report having the same problem with intel cards. Not sure if related, but I got LOTS of these on dmesg: [dom jun 10 20:55:04 2018] pcieport :00:1c.4: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=00e4(Transmitter ID) [dom jun 10 20:55:04 2018] pcieport :00:1c.4: device [8086:a114] error status/mask=1000/2000 [dom jun 10 20:55:04 2018] pcieport :00:1c.4:[12] Replay Timer Timeout Also, in those cases where it actually suspends ok, sometimes it randomly wakes up as if someone would have opened the lid (many times I double checked it was actually suspended before putting the laptop in my backpack and then found it freakingly hot because it turned on by itself). I'm running Ubuntu on Samsung SSD 850 Pro and I also have a WD Black M.2 on the pci express slot with a different SO. -- 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: Confirmed Bug description: 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 1690085]
On 2018-06-09 07:33 AM, bugzilla-dae...@bugzilla.kernel.org wrote: > https://bugzilla.kernel.org/show_bug.cgi?id=196683 > > --- Comment #352 from Kai-Heng Feng (kai.heng.f...@canonical.com) --- > Is there anyone not affected by this when Package C6 is enabled? > Otherwise I intent to send the patch, which has the same effect as "typical > current". > There are multiple reports above that disabling package C6 is not the same as setting typical current in Bios. ISTR there is even a report that setting typical current did not disable C6 for that particular bios. The theory that this power bug is related to motherboard is gaining prominence, because different motherboards seem to have different tweaks for "typical current". If only AMD would just tell us what is going on. Meanwhile, I am more than content with my Ryzen setup now that it is apparently stable, but discontented with AMDs lack of disclosure. Not to the point of swearing off AMD, but it got close. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1690085 Title: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Hi, We aregetting various kernel crash on a pretty new config. We're using Ryzen 1800X CPU with X370 Gaming Pro Carbon MB (7A32V1) using latest BIOS available (1.52) We are running Ubuntu 17.04 (amd64), we've tried different kernel version, native one and releases from http://kernel.ubuntu.com/~kernel-ppa/mainline/ too. Tested kernel version: native 17.04 kernel 4.10.15 Issues are the same, we're getting random freeze on the machine. Here is kern.log entry when happening : May 10 22:41:56 dev2 kernel: [24366.186246] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:41:56 dev2 kernel: [24366.187618] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=913449 May 10 22:41:56 dev2 kernel: [24366.188977] (detected by 12, t=1860207 jiffies, g=10001, c=1, q=4656) May 10 22:41:56 dev2 kernel: [24366.190344] Task dump for CPU 0: May 10 22:41:56 dev2 kernel: [24366.190345] swapper/0 R running task 0 0 0 0x0008 May 10 22:41:56 dev2 kernel: [24366.190348] Call Trace: May 10 22:41:56 dev2 kernel: [24366.190354] ? native_safe_halt+0x6/0x10 May 10 22:41:56 dev2 kernel: [24366.190355] ? default_idle+0x20/0xd0 May 10 22:41:56 dev2 kernel: [24366.190358] ? arch_cpu_idle+0xf/0x20 May 10 22:41:56 dev2 kernel: [24366.190360] ? default_idle_call+0x23/0x30 May 10 22:41:56 dev2 kernel: [24366.190362] ? do_idle+0x16f/0x200 May 10 22:41:56 dev2 kernel: [24366.190364] ? cpu_startup_entry+0x71/0x80 May 10 22:41:56 dev2 kernel: [24366.190366] ? rest_init+0x77/0x80 May 10 22:41:56 dev2 kernel: [24366.190368] ? start_kernel+0x464/0x485 May 10 22:41:56 dev2 kernel: [24366.190369] ? early_idt_handler_array+0x120/0x120 May 10 22:41:56 dev2 kernel: [24366.190371] ? x86_64_start_reservations+0x24/0x26 May 10 22:41:56 dev2 kernel: [24366.190372] ? x86_64_start_kernel+0x14d/0x170 May 10 22:41:56 dev2 kernel: [24366.190373] ? start_cpu+0x14/0x14 May 10 22:44:56 dev2 kernel: [24546.188093] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:44:56 dev2 kernel: [24546.189461] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=935027 May 10 22:44:56 dev2 kernel: [24546.190823] (detected by 14, t=1905212 jiffies, g=10001, c=1, q=4740) May 10 22:44:56 dev2 kernel: [24546.192191] Task dump for CPU 0: May 10 22:44:56 dev2 kernel: [24546.192192] swapper/0 R running task 0 0 0 0x0008 May 10 22:44:56 dev2 kernel: [24546.192195] Call Trace: May 10 22:44:56 dev2 kernel: [24546.192199] ? native_safe_halt+0x6/0x10 May 10 22:44:56 dev2 kernel: [24546.192201] ? default_idle+0x20/0xd0 May 10 22:44:56 dev2 kernel: [24546.192203] ? arch_cpu_idle+0xf/0x20 May 10 22:44:56 dev2 kernel: [24546.192204] ? default_idle_call+0x23/0x30 May 10 22:44:56 dev2 kernel: [24546.192206] ? do_idle+0x16f/0x200 May 10 22:44:56 dev2 kernel: [24546.192208] ? cpu_startup_entry+0x71/0x80 May 10 22:44:56 dev2 kernel: [24546.192210] ? rest_init+0x77/0x80 May 10 22:44:56 dev2 kernel: [24546.192211] ? start_kernel+0x464/0x485 May 10 22:44:56 dev2 kernel: [24546.192213] ? early_idt_handler_array+0x120/0x120 May 10 22:44:56 dev2 kernel: [24546.192214] ? x86_64_start_reservations+0x24/0x26 May 10 22:44:56 dev2 kernel: [24546.192215] ? x86_64_start_kernel+0x14d/0x170 May 10 22:44:56 dev2 kernel: [24546.192217] ? start_cpu+0x14/0x14 Depending on the kernel version, we've got NMI watchdog errors related to CPU stuck (mentioning the CPU core id, which is random). Crash is happening randomly, but in general after some hours (3-4h). Now, we've installed kernel 4.11.0-04
[Kernel-packages] [Bug 1609750] Re: Audio not working on Acer Chromebook R11
Launchpad has imported 31 comments from the remote bug at https://bugzilla.kernel.org/show_bug.cgi?id=151521. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2016-08-05T07:04:52+00:00 timo.jyrinki wrote: Created attachment 227601 dmesg It's a Braswell 14nm platform with Coreboot and SeaBIOS as a payload to boot Ubuntu 16.10 (+ mainline 4.7 kernel). Sound does not work and the UIs don't show any devices either since pulseaudio fails so start with "failed to detect any sound hardware". According to Chromebook community person, there might be some required initialization missing that the ChromeOS payload ("depthcharge") is usually responsible for. alsa-info at: http://www.alsa- project.org/db/?f=c193a12f53608b68d259f574b4791d18a522a000 dmesg, dmidecode, lshw, lspci as attachments. Reply at: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1609750/comments/20 On 2016-08-05T07:05:21+00:00 timo.jyrinki wrote: Created attachment 227611 dmidecode Reply at: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1609750/comments/21 On 2016-08-05T07:05:44+00:00 timo.jyrinki wrote: Created attachment 227621 lshw Reply at: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1609750/comments/22 On 2016-08-05T07:06:03+00:00 timo.jyrinki wrote: Created attachment 227631 lspci Reply at: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1609750/comments/23 On 2016-08-08T14:06:46+00:00 timo.jyrinki wrote: It seems these should get merged? https://github.com/plbossart/sound/branches/all?query=byt-cht Reply at: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1609750/comments/24 On 2016-08-09T20:03:04+00:00 tiwai wrote: The relevant codes have been already merged to upstream recently. Could you try 4.8-rc1? Reply at: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1609750/comments/25 On 2016-08-10T13:57:03+00:00 timo.jyrinki wrote: Created attachment 228161 dmesg 4.8rc1 No change, no sound and cht-bsw-max98090 cht-bsw-max98090: snd_soc_register_card failed -517 Reply at: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1609750/comments/26 On 2016-08-22T09:49:19+00:00 vinod.koul wrote: (In reply to Timo Jyrinki from comment #6) > Created attachment 228161 [details] > dmesg 4.8rc1 > > No change, no sound and cht-bsw-max98090 cht-bsw-max98090: > snd_soc_register_card failed -517 SST driver seems to initialze well. This i2c seems to fail.. [ 19.972195] cht-bsw-max98090 cht-bsw-max98090: ASoC: i2c-104C227E:00 not registered [ 19.972207] cht-bsw-max98090 cht-bsw-max98090: snd_soc_register_card failed -517 I will check the codec on this device, if you know please do let me know... Reply at: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1609750/comments/27 On 2016-08-24T08:21:35+00:00 vinod.koul wrote: okay I checked. With coreboot this seems to work fine. Cna you check the SeaBIOS used and get it to create the I2C device 104C227E so codec can be loaded thus completing the sound card Reply at: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1609750/comments/28 On 2016-08-24T09:27:31+00:00 timo.jyrinki wrote: Thank you, sounds like a very useful bit of information. I've passed on the info to the G+ coreboot on Chromebooks community where the people creating the SeaBIOS images are. Reply at: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1609750/comments/29 On 2016-08-24T10:51:23+00:00 timo.jyrinki wrote: And copy-pasting here (from https://plus.google.com/u/0/+TimoJyrinki/posts/R1AqYCSPru8 ): "SeaBIOS doesn't do hardware initialisation, that's down to coreboot, so no, I can't. Obviously, the sound hardware works under the ChromeOS kernel so I would guess they need to figure out what the ChromeOS kernel is doing that upstream isn't." Reply at: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1609750/comments/30 On 2016-08-26T09:07:20+00:00 timo.jyrinki wrot
[Kernel-packages] [Bug 1773718] Re: mouse pointer disappear after screen off
I haven't tried with other DE, since it is an old computer I have only tried lxde. I could easily try with openbox alone, installing another DE could be a little longer. Is there one better to test with? -- 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/1773718 Title: mouse pointer disappear after screen off Status in linux package in Ubuntu: Confirmed Bug description: With nouveau driver (doesn't happened with propietary nvidia) after screen switch off because of power management, the mouse pointer disappear. Mouse still works, you can hover, select, click, but the pointer is invisible. In a dual monitor configuration, this only happened in the screen where the mouse was when it turned off. If It firs happened in one monitor and tehn I left the mouse in the other and it also turn off, mouse end up disappearing in both. My video card is an nvidia GeForce Go6150 (NV4E C51). Ubuntu 4.13.0-43.48~16.04.1-generic 4.13.16 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1773718/+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 1645540] Re: [Feature] Crystal Ridge 2LM error reporting
** Description changed: In 2LM configurations we need to error reports to differentiate between errors in the "near" memory (DRAM used as cache) and "far" memory (Crystal ridge memory) HW: Apache Pass Upstream schedule: - kernel: 4.17 + kernel: 4.19 Target Release: 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/1645540 Title: [Feature] Crystal Ridge 2LM error reporting Status in intel: New Status in linux package in Ubuntu: Fix Released Status in linux source package in Artful: Invalid Status in linux source package in Bionic: Fix Released Bug description: In 2LM configurations we need to error reports to differentiate between errors in the "near" memory (DRAM used as cache) and "far" memory (Crystal ridge memory) HW: Apache Pass Upstream schedule: kernel: 4.19 Target Release: 18.10 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1645540/+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 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)
Thanks @kaihengfeng for the bisection instructions and @jail-j for pointing me in the right direction. (It's probably worth mentioning that sudo make -j`nproc` deb-pkg was needed for the build to work) Here's the most recent result: git bisect bad a192aa923b66a435aae56983c4912ee150bc9b32 is the first bad commit commit a192aa923b66a435aae56983c4912ee150bc9b32 Author: Rafael J. Wysocki Date: Mon Oct 16 03:29:55 2017 +0200 ACPI / LPSS: Consolidate runtime PM and system sleep handling Move the LPSS-specific code from acpi_lpss_runtime_suspend() and acpi_lpss_runtime_resume() into separate functions, acpi_lpss_suspend() and acpi_lpss_resume(), respectively, and make acpi_lpss_suspend_late() and acpi_lpss_resume_early() use them too in order to unify the runtime PM and system sleep handling in the LPSS driver. Signed-off-by: Rafael J. Wysocki Acked-by: Greg Kroah-Hartman Reviewed-by: Ulf Hansson :04 04 b4ef369c698a10cec8d6224fdc3b8f287eb853b1 20327192ca09ecc0cf0b24b62fdb915ea303b988 M drivers wasn't sure if I'm meant to keep going so I've run sudo make -j`nproc` deb-pkg again to see what it comes up with. -- 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: Confirmed Bug description: 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@lis
[Kernel-packages] [Bug 1763748] Re: Integrated Webcam Realtek Integrated_Webcam_HD (0bda:58f4) not working in DELL XPS 13 9370 with firmware 1.50
"Proposed" needs to be enabled in APT to use the new kernel. -- 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/1763748 Title: Integrated Webcam Realtek Integrated_Webcam_HD (0bda:58f4) not working in DELL XPS 13 9370 with firmware 1.50 Status in Dell Sputnik: New Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem package in Ubuntu: Confirmed Status in linux source package in Xenial: Fix Committed Status in linux-oem source package in Xenial: In Progress Status in linux source package in Artful: Fix Committed Status in linux-oem source package in Artful: Invalid Status in linux source package in Bionic: Fix Committed Status in linux-oem source package in Bionic: In Progress Bug description: ===SRU Justification=== [Impact] UVC1.5 Realtek webcam on XPS 9370 does not work. [Test] Both the bug reporter and I can confirm the patch from Realtek works. [Fix] Use correct version control length for UVC1.5. [Regression Potential] Low. This only affects UVC1.5 webcams, which is quite rare in the wild. ===Original Bug Report=== The webcam is detected by the system, but no applications detect it. sudo lsusb -v: (relevant part) Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 2.01 bDeviceClass 239 Miscellaneous Device bDeviceSubClass 2 ? bDeviceProtocol 1 Interface Association bMaxPacketSize064 idVendor 0x0bda Realtek Semiconductor Corp. idProduct 0x58f4 bcdDevice 72.79 iManufacturer 3 CN0FFMHCLOG0081SB0M1A01 iProduct1 Integrated_Webcam_HD iSerial 2 200901010001 In syslog (firmware can be seen in first line - 1.50): Apr 13 12:36:25 XPS-13-9370 kernel: [2.126546] uvcvideo: Found UVC 1.50 device Integrated_Webcam_HD (0bda:58f4) Apr 13 12:36:25 XPS-13-9370 kernel: [2.126908] usbcore: registered new interface driver btusb Apr 13 12:36:25 XPS-13-9370 kernel: [2.127128] uvcvideo: UVC non compliance - GET_DEF(PROBE) not supported. Enabling workaround. Apr 13 12:36:25 XPS-13-9370 kernel: [2.127462] uvcvideo: Failed to query (129) UVC probe control : -75 (exp. 34). Apr 13 12:36:25 XPS-13-9370 kernel: [2.127464] uvcvideo: Failed to initialize the device (-5). Apr 13 12:36:25 XPS-13-9370 kernel: [2.128061] uvcvideo: Unknown video format 0032-0002-0010-8000-00aa00389b71 Apr 13 12:36:25 XPS-13-9370 kernel: [2.128065] uvcvideo: Found UVC 1.50 device Integrated_Webcam_HD (0bda:58f4) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-13-generic 4.15.0-13.14 [modified: boot/vmlinuz-4.15.0-13-generic] ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: wgarcia2145 F pulseaudio CurrentDesktop: Unity:Unity7:ubuntu Date: Fri Apr 13 16:59:02 2018 HibernationDevice: RESUME=UUID=a6f64150-e0a5-4c6b-9097-b8f98b14bdcc InstallationDate: Installed on 2018-04-09 (4 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180408) MachineType: Dell Inc. XPS 13 9370 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed root=UUID=226e4127-5c15-4a18-8062-74ba83b57515 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-13-generic N/A linux-backports-modules-4.15.0-13-generic N/A linux-firmware 1.173 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/21/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.1 dmi.board.name: 0F6P3V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.1:bd02/21/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1763748/+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 1753510] Re: Cannot boot/install AMD Ryzen 2400G
Isn't Ryzen 2400G a 8 threads processor? -- 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/1753510 Title: Cannot boot/install AMD Ryzen 2400G Status in linux package in Ubuntu: Confirmed Bug description: Did a motherboard swap on a trusty old computer that ran ubuntu for 10 years or so. Now it only runs windows (same hardware fresh installs windows with no issue). brand new ryzen 2nd gen with graphics. I know about graphics drivers issues, wasn't expecting that to be dealt with. Just trying to use it as a cpu. So I put in an older (RADEON HD 7850 pitcairn) video card to get some functionality. Without the video card, it boots, but the display is unusable. I can ssh in and see that it works fine as a server, but cannot use terminal or graphical display. With the video card, Put daily ubuntu Bionic image, and "Try Ubuntu", and it goes into an infinite loop. photo attached. I tried 16.04.4 and I think it just went into a blank screen. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753510/+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 1763041] Re: BUG: unable to handle kernel NULL pointer dereference at 0000000000000070
[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/1763041 Title: BUG: unable to handle kernel NULL pointer dereference at 0070 Status in linux package in Ubuntu: Expired Bug description: Error occurred on startup. ProblemType: KernelOops DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-13-generic 4.15.0-13.14 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: Cannot stat file /proc/7581/fd/1023: Permission denied USERPID ACCESS COMMAND /dev/snd/controlC0: gdm5478 F pulseaudio cseeley6982 F pulseaudio Date: Wed Apr 11 08:58:24 2018 DuplicateSignature: BUG: unable to handle kernel NULL pointer dereference at location RIP: vbox_crtc_mode_set+0x3f6/0x420 [vboxvideo] RSP: a116c553b8a0 Failure: oops InstallationDate: Installed on 2018-02-28 (41 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180202) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox ProcFB: 0 vboxdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic root=UUID=faff59a2-db4a-433c-adda-fa5829520ea1 ro quiet splash 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 RfKill: SourcePackage: linux Title: BUG: unable to handle kernel NULL pointer dereference at 0070 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1763041/+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 1749207] Re: kernel is reporting Nintendo USB microphone as an output device
[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/1749207 Title: kernel is reporting Nintendo USB microphone as an output device Status in linux package in Ubuntu: Expired Bug description: Kernel is reporting Nintendo USB microphone as an output device.And because that alsa will use every time as a output device ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.13.0-32-generic 4.13.0-32.35 [modified: boot/vmlinuz-4.13.0-32-generic] ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.8-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: a 1438 F pulseaudio /dev/snd/controlC0: a 1438 F pulseaudio /dev/snd/controlC1: a 1438 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Feb 13 16:48:49 2018 InstallationDate: Installed on 2018-02-12 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180212) IwConfig: lono wireless extensions. enp1s0no wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed root=UUID=e1fa3a67-c257-4f26-b6fc-b72b872c2370 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.13.0-32-generic N/A linux-backports-modules-4.13.0-32-generic N/A linux-firmware 1.170 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/05/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.40 dmi.board.name: A88M-G/3.1 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.40:bd05/05/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnA88M-G/3.1:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. --- ApportVersion: 2.20.8-0ubuntu9 Architecture: amd64 CurrentDesktop: MATE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-02-13 (0 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180213) Package: linux (not installed) Tags: bionic Uname: Linux 4.16.0-041600rc1-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-05 (5 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) Package: linux (not installed) Tags: bionic Uname: Linux 4.16.0-999-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1749207/+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 1762816] Re: chaoskey interferes with suspend on thinkpad
[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/1762816 Title: chaoskey interferes with suspend on thinkpad Status in linux package in Ubuntu: Expired Bug description: Thinkpad T450s, docking station, Altus Metrum Chaoskey plugged into the docking station - suspend fails often (more than half the time, maybe not 100% but easily duplicated in my setup) in that it doesn't seem to go all the way down - and on wakeup, lsusb output doesn't update, `lsusb -t` hangs when run. It *may* require "suspend, undock, unsuspend" but I'm not convinced... Interesting logs include a "blocked for more than 120 seconds" traceback after restore that goes through chaoskey_disconnect even though the laptop is undocked so it's no longer attached: [17038.103142] Call Trace: __schedule+0x297/0x8b0 schedule+0x2c/0x80 schedule_timeout+0x1cf/0x350 ? ttwu_do_activate+0x7a/0x90 wait_for_completion+0xba/0x140 ? wake_up_q+0x80/0x80 hwrng_unregister+0x8f/0xa0 *** chaoskey_disconnect+0xbe/0x110 [chaoskey] *** usb_unbind_interface+0x77/0x290 device_release_driver_internal+0x15b/0x220 device_release_driver+0x12/0x20 bus_remove_device+0xec/0x160 device_del+0x13d/0x360 ? usb_remove_ep_devs+0x1f/0x30 usb_disable_device+0x9f/0x270 usb_disconnect+0xc6/0x270 hub_quiesce+0x48/0xa0 hub_event+0xfb/0xb10 process_one_work+0x1de/0x410 worker_thread+0x32/0x410 kthread+0x121/0x140 ? process_one_work+0x410/0x410 ? kthread_create_worker_on_cpu+0x70/0x70 ? do_syscall_64+0x73/0x130 ? SyS_exit_group+0x14/0x20 ret_from_fork+0x35/0x40 Kernel is most recently `4.15.0-13-generic #14-Ubuntu` but it's been going on for the last month of bionic, and *possibly* longer but I only recently caught that the Chaoskey was related. $ lsb_release -rd Description:Ubuntu Bionic Beaver (development branch) Release:18.04 $ uname -a Linux workbench 4.15.0-13-generic #14-Ubuntu SMP Sat Mar 17 13:44:27 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ dpkg --status linux-image-4.15.0-13-generic Package: linux-image-4.15.0-13-generic Status: install ok installed Priority: optional Section: kernel Installed-Size: 72167 Maintainer: Ubuntu Kernel Team Architecture: amd64 Source: linux Version: 4.15.0-13.14 Provides: aufs-dkms, fuse-module, ivtv-modules, kvm-api-4, linux-image, redhat-cluster-modules, spl-dkms, spl-modules, virtualbox-guest-modules, zfs-dkms, zfs-modules Depends: kmod Recommends: grub-pc | grub-efi-amd64 | grub-efi-ia32 | grub | lilo, initramfs-tools | linux-initramfs-tool Suggests: fdutils, linux-doc-4.15.0 | linux-source-4.15.0, linux-tools, linux-headers-4.15.0-13-generic Description: Linux kernel image for version 4.15.0 on 64 bit x86 SMP This package contains the Linux kernel image for version 4.15.0 on 64 bit x86 SMP. . Also includes the corresponding System.map file, the modules built by the packager, and scripts that try to ensure that the system is not left in an unbootable state after an update. . Supports Generic processors. . Geared toward desktop and server systems. . You likely do not want to install this package directly. Instead, install the linux-generic meta-package, which will ensure that upgrades work correctly, and that supporting packages are also installed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762816/+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 1762725] Re: Linux reports Samson Meteor USB mic as an output device
[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/1762725 Title: Linux reports Samson Meteor USB mic as an output device Status in linux package in Ubuntu: Expired Bug description: Whenever I reboot my system, pulseaudio selects my Samson Meteor USB mic as the default output device. I have to manually select the analog output every time. Also, the Default effect sound does not make any noise. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: guru 2355 F pulseaudio /dev/snd/controlC1: guru 2355 F pulseaudio /dev/snd/controlC0: guru 2355 F pulseaudio CurrentDesktop: Budgie:GNOME Date: Tue Apr 10 08:54:30 2018 InstallationDate: Installed on 2018-04-07 (2 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/06/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.52 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B350M MORTAR ARCTIC (MS-7A37) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 4 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.52:bd06/06/2017:svnMSI:pnMS-7A37:pvr2.0:rvnMSI:rnB350MMORTARARCTIC(MS-7A37):rvr2.0:cvnMSI:ct4:cvr2.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A37 dmi.product.version: 2.0 dmi.sys.vendor: MSI --- ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: guru 2402 F pulseaudio /dev/snd/controlC1: guru 2402 F pulseaudio /dev/snd/controlC0: guru 2402 F pulseaudio CurrentDesktop: Budgie:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-07 (3 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) IwConfig: enp30s0 no wireless extensions. lono wireless extensions. MachineType: MSI MS-7A37 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed root=UUID=9407e2de-9df6-494d-8d4a-ab6fd82dbe85 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 RelatedPackageVersions: linux-restricted-modules-4.15.0-13-generic N/A linux-backports-modules-4.15.0-13-generic N/A linux-firmware 1.173 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 4.15.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/06/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.52 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B350M MORTAR ARCTIC (MS-7A37) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 4 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.52:bd06/06/2017:svnMSI:pnMS-7A37:pvr2.0:rvnMSI:rnB350MMORTARARCTIC(MS-7A37):rvr2.0:cvnMSI:ct4:cvr2.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A37 dmi.product.version: 2.0 dmi.sys.vendor: MSI --- ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: guru 2402 F pulseaudio /dev/snd/controlC1: guru 2402 F pulseaudio /dev/snd/controlC0: guru 2402 F pulseaudio CurrentDesktop: Budgie:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-07 (3 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) IwConfig: enp30s0 no wireless extensions. lono wireless extensions. MachineType: MSI MS-7A37 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed root=UUID=9407e2de-9df6-494d-8d4a-ab6fd82dbe85 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 RelatedPackageVersions: linux-restricted-modules-4.15.0-13-gener
[Kernel-packages] [Bug 1760851] Re: ethernet wired adapter lost
[Expired for linux (Ubuntu Xenial) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu Xenial) 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/1760851 Title: ethernet wired adapter lost Status in linux package in Ubuntu: Expired Status in linux source package in Xenial: Expired Bug description: When i upgraded kernel from linux-image-4.4.0-112-generic to linux- image-4.4.0-116-generic, my dell xps lost the wired network adapter. On this laptop the ethernet wired adapter is on usb-c extension. When i boot on my old kernel : * The device is named enxd481d74f12bb. * The address looks to be /sys/devices/pci:00/:00:1c.0/:01:00.0/:02:02.0/:39:00.0/usb4/4-1/4-1.4/4-1.4:1.0/net/enxd481d74f12bb ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-112-generic 4.4.0-112.135 ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98 Uname: Linux 4.4.0-112-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fcombernous 7044 F pulseaudio Date: Tue Apr 3 14:18:14 2018 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 HibernationDevice: RESUME=UUID=7c5d4db9-e495-4d8b-ac3e-12534cd9fdd2 InstallationDate: Installed on 2017-05-19 (319 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. XPS 13 9360 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic.efi.signed root=UUID=ce828ede-44e4-4f8a-a8c4-422e1815674d 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: linux-restricted-modules-4.4.0-112-generic N/A linux-backports-modules-4.4.0-112-generic N/A linux-firmware 1.157.17 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/18/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.2 dmi.board.name: 00GCYR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.2:bd01/18/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn00GCYR:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9360 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1760851/+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 1760851] Re: ethernet wired adapter lost
[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/1760851 Title: ethernet wired adapter lost Status in linux package in Ubuntu: Expired Status in linux source package in Xenial: Expired Bug description: When i upgraded kernel from linux-image-4.4.0-112-generic to linux- image-4.4.0-116-generic, my dell xps lost the wired network adapter. On this laptop the ethernet wired adapter is on usb-c extension. When i boot on my old kernel : * The device is named enxd481d74f12bb. * The address looks to be /sys/devices/pci:00/:00:1c.0/:01:00.0/:02:02.0/:39:00.0/usb4/4-1/4-1.4/4-1.4:1.0/net/enxd481d74f12bb ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-112-generic 4.4.0-112.135 ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98 Uname: Linux 4.4.0-112-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fcombernous 7044 F pulseaudio Date: Tue Apr 3 14:18:14 2018 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 HibernationDevice: RESUME=UUID=7c5d4db9-e495-4d8b-ac3e-12534cd9fdd2 InstallationDate: Installed on 2017-05-19 (319 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. XPS 13 9360 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic.efi.signed root=UUID=ce828ede-44e4-4f8a-a8c4-422e1815674d 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: linux-restricted-modules-4.4.0-112-generic N/A linux-backports-modules-4.4.0-112-generic N/A linux-firmware 1.157.17 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/18/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.2 dmi.board.name: 00GCYR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.2:bd01/18/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn00GCYR:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9360 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1760851/+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 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)
@pHeLiOn -- Matalak has joined! Sorry for the delayed response. Thanks for putting this bug report together! Here's the linked answer, as requested: https://askubuntu.com/questions/1029405/ubuntu-18-04-crashes- on-resuming-from-suspend/1043397#1043397 . -- 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: Confirmed Bug description: 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 1762725] Re: Linux reports Samson Meteor USB mic as an output device
Any idea when that kernel will be pushed out to regular users? I am still experiencing this issue. -- 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/1762725 Title: Linux reports Samson Meteor USB mic as an output device Status in linux package in Ubuntu: Expired Bug description: Whenever I reboot my system, pulseaudio selects my Samson Meteor USB mic as the default output device. I have to manually select the analog output every time. Also, the Default effect sound does not make any noise. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: guru 2355 F pulseaudio /dev/snd/controlC1: guru 2355 F pulseaudio /dev/snd/controlC0: guru 2355 F pulseaudio CurrentDesktop: Budgie:GNOME Date: Tue Apr 10 08:54:30 2018 InstallationDate: Installed on 2018-04-07 (2 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/06/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.52 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B350M MORTAR ARCTIC (MS-7A37) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 4 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.52:bd06/06/2017:svnMSI:pnMS-7A37:pvr2.0:rvnMSI:rnB350MMORTARARCTIC(MS-7A37):rvr2.0:cvnMSI:ct4:cvr2.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A37 dmi.product.version: 2.0 dmi.sys.vendor: MSI --- ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: guru 2402 F pulseaudio /dev/snd/controlC1: guru 2402 F pulseaudio /dev/snd/controlC0: guru 2402 F pulseaudio CurrentDesktop: Budgie:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-07 (3 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) IwConfig: enp30s0 no wireless extensions. lono wireless extensions. MachineType: MSI MS-7A37 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed root=UUID=9407e2de-9df6-494d-8d4a-ab6fd82dbe85 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 RelatedPackageVersions: linux-restricted-modules-4.15.0-13-generic N/A linux-backports-modules-4.15.0-13-generic N/A linux-firmware 1.173 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 4.15.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/06/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.52 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B350M MORTAR ARCTIC (MS-7A37) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 4 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.52:bd06/06/2017:svnMSI:pnMS-7A37:pvr2.0:rvnMSI:rnB350MMORTARARCTIC(MS-7A37):rvr2.0:cvnMSI:ct4:cvr2.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A37 dmi.product.version: 2.0 dmi.sys.vendor: MSI --- ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: guru 2402 F pulseaudio /dev/snd/controlC1: guru 2402 F pulseaudio /dev/snd/controlC0: guru 2402 F pulseaudio CurrentDesktop: Budgie:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-07 (3 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) IwConfig: enp30s0 no wireless extensions. lono wireless extensions. MachineType: MSI MS-7A37 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed root=UUID=9407e2de-9df6-494d-8d4a-ab6fd82dbe85 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 RelatedPackageVersions: linux-restricted-modules-4.15.0-13-generic N/A linux-backports-modules-4.15.0-13-ge
[Kernel-packages] [Bug 1776155] [NEW] Hantick HTT5288 touchpad wrongly detected as SYNA3602, does not work at all.
Public bug reported: On my cheaper-end laptop/netbook the touchpad, which I believe is the Hantick HT 5288, is wrongly detected by Linux to be the SYNA 3602. Accordingly it does not work at all, neither touchpad nor buttons. Freshly installed Ubuntu 18.04 system. I belive the issue is, as reported previously other places by vendors of such computers, that the touchpad is not being reset properly on boot. martin@alanah:~$ cat /proc/bus/input/devices I: Bus=0019 Vendor= Product=0005 Version= N: Name="Lid Switch" P: Phys=PNP0C0D/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:13/PNP0C09:00/PNP0C0D:00/input/input0 U: Uniq= H: Handlers=event0 B: PROP=0 B: EV=21 B: SW=1 I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=PNP0C0C/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input1 U: Uniq= H: Handlers=kbd event1 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0011 Vendor=0001 Product=0001 Version=ab83 N: Name="AT Translated Set 2 keyboard" P: Phys=isa0060/serio0/input0 S: Sysfs=/devices/platform/i8042/serio0/input/input2 U: Uniq= H: Handlers=sysrq kbd event2 leds B: PROP=0 B: EV=120013 B: KEY=40200 3803078f800d001 fedfffef fffe B: MSC=10 B: LED=7 I: Bus=0019 Vendor= Product=0006 Version= N: Name="Video Bus" P: Phys=LNXVIDEO/video/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input3 U: Uniq= H: Handlers=kbd event3 B: PROP=0 B: EV=3 B: KEY=3e000b 0 0 0 I: Bus=0019 Vendor= Product= Version= N: Name="Intel HID events" P: Phys= S: Sysfs=/devices/platform/INT33D5:00/input/input4 U: Uniq= H: Handlers=rfkill kbd event4 B: PROP=0 B: EV=13 B: KEY=810003 504000 1e29400020 0 B: MSC=10 I: Bus=0019 Vendor= Product= Version= N: Name="Intel HID 5 button array" P: Phys= S: Sysfs=/devices/platform/INT33D5:00/input/input5 U: Uniq= H: Handlers=kbd event5 B: PROP=0 B: EV=33 B: KEY=1 0 201c 0 B: MSC=10 B: SW=1000 I: Bus=0003 Vendor=058f Product=5608 Version=0009 N: Name="VGA Webcam: VGA Webcam" P: Phys=usb-:00:15.0-8/button S: Sysfs=/devices/pci:00/:00:15.0/usb1/1-8/1-8:1.0/input/input6 U: Uniq= H: Handlers=kbd event6 B: PROP=0 B: EV=3 B: KEY=10 0 0 0 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH Mic" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:0e.0/sound/card0/input7 U: Uniq= H: Handlers=event7 B: PROP=0 B: EV=21 B: SW=10 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH Headphone" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:0e.0/sound/card0/input8 U: Uniq= H: Handlers=event8 B: PROP=0 B: EV=21 B: SW=4 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=3" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:0e.0/sound/card0/input9 U: Uniq= H: Handlers=event9 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=7" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:0e.0/sound/card0/input10 U: Uniq= H: Handlers=event10 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=8" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:0e.0/sound/card0/input11 U: Uniq= H: Handlers=event11 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=9" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:0e.0/sound/card0/input12 U: Uniq= H: Handlers=event12 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=10" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:0e.0/sound/card0/input13 U: Uniq= H: Handlers=event13 B: PROP=0 B: EV=21 B: SW=140 I: Bus=0018 Vendor=0911 Product=5288 Version=0100 N: Name="SYNA3602:00 0911:5288 Touchpad" P: Phys=i2c-SYNA3602:00 S: Sysfs=/devices/pci:00/:00:16.1/i2c_designware.1/i2c-5/i2c-SYNA3602:00/0018:0911:5288.0001/input/input15 U: Uniq= H: Handlers=mouse0 event14 B: PROP=5 B: EV=1b B: KEY=e420 3 0 0 0 0 B: ABS=2608003 B: MSC=20 I: Bus=0003 Vendor=045e Product=00b9 Version=0111 N: Name="Microsoft Microsoft USB Wireless Mouse" P: Phys=usb-:00:15.0-1/input0 S: Sysfs=/devices/pci:00/:00:15.0/usb1/1-1/1-1:1.0/0003:045E:00B9.0002/input/input16 U: Uniq= H: Handlers=mouse1 event15 B: PROP=0 B: EV=17 B: KEY=1f 0 0 0 0 B: REL=1c3 B: MSC=10 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-20-generic 4.15.0-20.21 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: MATE Date: Mon Jun 11 07:57:56 2018 InstallationDate: Installed on 2018-04-25 (46 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) SourcePackage: linux-signed Upgra
[Kernel-packages] [Bug 1771919] Re: Support Realtek Bluetooth [0bda:c024]
Tested on ThinkCentre M720t and ThinkCentre M920z, it work fine. ** Tags removed: verification-needed-xenial ** Tags added: verification-done-xenial ** Attachment added: "M710t.journalctl.log" https://bugs.launchpad.net/ubuntu/+source/linux-oem/+bug/1771919/+attachment/5151187/+files/M710t.journalctl.log -- 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/1771919 Title: Support Realtek Bluetooth [0bda:c024] Status in HWE Next: New Status in linux-oem package in Ubuntu: In Progress Status in linux-oem source package in Xenial: Fix Committed Bug description: The driver rtk-btusb is already in ubuntu/rtl8821ce-bt. All we need to support this device is to add the ID to the driver and blacklist it in btusb. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1771919/+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 1771919] Re: Support Realtek Bluetooth [0bda:c024]
** Attachment added: "M920z.journal.log" https://bugs.launchpad.net/ubuntu/+source/linux-oem/+bug/1771919/+attachment/5151188/+files/M920z.journal.log -- 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/1771919 Title: Support Realtek Bluetooth [0bda:c024] Status in HWE Next: New Status in linux-oem package in Ubuntu: In Progress Status in linux-oem source package in Xenial: Fix Committed Bug description: The driver rtk-btusb is already in ubuntu/rtl8821ce-bt. All we need to support this device is to add the ID to the driver and blacklist it in btusb. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1771919/+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 1775126] Re: System keeps briefly freezing with kernel errors "snd_hda_intel 0000:01:00.1: Disabling via vga_switcheroo" and "snd_hda_intel 0000:01:00.1: Cannot lock devices!"
The warning message isn't harmful and should not cause hang. This should be a pure Gnome bug. -- 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/1775126 Title: System keeps briefly freezing with kernel errors "snd_hda_intel :01:00.1: Disabling via vga_switcheroo" and "snd_hda_intel :01:00.1: Cannot lock devices!" Status in linux package in Ubuntu: Incomplete Status in linux package in Fedora: Unknown Bug description: When using Wayland, I observe sub-second freezes a couple of times per minute. It just freezes the mouse and everything for a split second, and continues as if nothing happened. When using Xorg, everything runs smoothly. (hence I did not pick Xorg in ubuntu-bug) I suspect this is a GPU issue. My laptop has a hybrid GPU, and dmesg is filled with vga_switcheroo messages [ 2640.943598] snd_hda_intel :01:00.1: Disabling via vga_switcheroo [ 2641.243870] snd_hda_intel :01:00.1: Cannot lock devices! [ 2641.260536] ACPI: \_SB_.PCI0.PEG0.VID_: failed to evaluate _DSM [ 2658.996392] snd_hda_intel :01:00.1: Enabling via vga_switcheroo I tried to manually switch to the dedicated graphics card, and that completely froze my session. Now I can't even log in using Wayland anymore, as it straight up crashes and goes back to the login screen. Xorg is still fine... Now there are other weird messages such as [ 2777.002437] nouveau :01:00.0: gr: DATA_ERROR 009c [] ch 8 [001f998000 systemd-logind[855]] subc 0 class 9297 mthd 0d78 data 0004 [ 2889.648718] snd_hda_codec_hdmi hdaudioC1D0: out of range cmd 0:5:707: And I suppose these are from the crash that I caused myself (not sure if related to the short freezes) [ 2551.513519] gnome-shell[5179]: segfault at 128 ip 7f409effeab0 sp 7ffcf4af1148 error 4 in libmutter-clutter-2.so[7f409efba000+161000] [ 2570.239129] Chrome_~dThread[6018]: segfault at 0 ip 7ff90a3494cd sp 7ff9086c9b00 error 6 in libxul.so[7ff90958f000+6111000] [ 2628.443468] gnome-shell[6348]: segfault at 0 ip 7f6349eb6c90 sp 7ffe5acd8bc8 error 4 in libgbm.so.1.0.0[7f6349eb4000+c000] [ 2777.424194] gnome-shell[6913]: segfault at 0 ip 7ff1e8550c90 sp 7ffe6cddb228 error 4 in libgbm.so.1.0.0[7ff1e854e000+c000] ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Jun 5 08:14:17 2018 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'command-history' redacted by apport b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2018-04-27 (38 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pepijn 1259 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-27 (38 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Dell Inc. Latitude E6420 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=0bfd26c3-7ff7-4c73-8c5b-aaeca648e5f3 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-22-generic N/A linux-backports-modules-4.15.0-22-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/04/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: A23 dmi.board.name: 032T9K dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA23:bd01/04/2016:svnDellInc.:pnLatitudeE6420:pvr01:rvnDellInc.:rn032T9K:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6420 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775126/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.n