[Kernel-packages] [Bug 1822394] Re: [Dell BIOSes dated 27 Mar 2019] laptop keyboard & touchpad not working at gdm screen after boot
OK, after compiling 5.0.7 mainline + Ubuntu Patches + this patch from here (https://patchwork.freedesktop.org/patch/296411/) to fix the link training issue for my laptop panel, I am able to boot with modesetting. Now I *am* noticing the problem. As others have suggested, bending back the laptop panel on it's hinge "resets" the keyboard and trackpad, then I can bend it back to a normal position and everything starts working. One other thing worth mentioning is that the problem also exhibits itself in lightdm, not just gdm3. -- 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/1822394 Title: [Dell BIOSes dated 27 Mar 2019] laptop keyboard & touchpad not working at gdm screen after boot Status in linux package in Ubuntu: Confirmed Bug description: On a dell XPS 15 2-in-1 with the latest 1.4.0 bios, my touchpad and keyboard are unresponsive at the gdm login screen. Keyboard works to unlock encrypted harddrive before that though. If I plug in a USB keyboard or activate my bluetooth mouse, I can use those to log in, and then after logging in the laptop touchpad and keyboard work again. Logging out of the desktop results in the laptop touchpad and keyboard working on the gdm screen. Did not see this behavior before upgrading from 1.2.0 bios to 1.4.0 bios, but also had not rebooted in a while, so not sure if bios or package upgrades triggered this behavior. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gdm3 3.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Mar 29 17:51:00 2019 InstallationDate: Installed on 2018-09-26 (184 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gdm3 UpgradeStatus: Upgraded to disco on 2019-03-11 (18 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822394/+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 1824216] Re: Linux 5.0 black screen on boot, display flickers (i915 regression with certain laptop panels)
I've compiled a mainline build from here: https://kernel.ubuntu.com /~kernel-ppa/mainline/v5.0.7/. I applied all the Ubuntu patches as well as the patch from here: https://patchwork.freedesktop.org/patch/296411/ Raw patch download here: https://patchwork.freedesktop.org/patch/296411/raw/ And things are working correctly again. It looks like Intel devs have cherry picked this fix into intel-drm-fixes, so hopefully this gets into mainline 5.0.8 and eventually trickles down to the Ubuntu kernels. If possible it would be great to manually apply this patch to the release kernel for 19.04 so people won't have problems installing. -- 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/1824216 Title: Linux 5.0 black screen on boot, display flickers (i915 regression with certain laptop panels) Status in linux package in Ubuntu: Confirmed Bug description: On my Dell XPS 9575, I get a black screen on boot when running the 19.04 live image, OR after updating from 18.10 to 19.04. It appears to be a kernel related bug that was introduced in 5.0 that is affected by certain laptop panels not conforming to their stated specifications. Several other Dell systems exhibit the same issue, and it's very possible that there are other panels used on other systems that will also have the same issues. Intel is aware of this issue and has already created a patch. You can see the relevant threads here: https://bugs.freedesktop.org/show_bug.cgi?id=109959 And the patch here: https://patchwork.freedesktop.org/patch/296411/ It would be fantastic to get this patch applied before release, as it would be very difficult install 19.04 on the affected systems otherwise. I was able to get the live image booted by adding the nomodeset kernel parameter to grub, so as a work around you can use this approach to install. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824216/+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 1822441]
I just received Kernel 5.0.0-11-generic via Ubuntu update and the issue seems to be solved :-) -- 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/1822441 Title: [Intel® HD Graphics 3000] Blank screen after startup. Xorg reports "(EE) modeset(0): failed to set mode: Invalid argument" when using kernel 4.19.26 and later (but 4.19.25 and earlier works) Status in Linux: Confirmed Status in linux package in Ubuntu: Triaged Bug description: Updated from kubuntu 18.10 to 19.04 beta without problems. After first reboot, first the kubuntu logo, then just a blank screen, no login screen. Switching to console and log in there possible. All seems fine, including wlan etc. systemd status sddm says sddm is running, any attempt to start KDE (including startkde) however fails with "could not connect to any x display". This happens with Kernel 5.0.0. Starting with 4.18.0-16-generic, the login screen comes up and all is fine. Anything I can contribute? Description:Ubuntu Disco Dingo (development branch) Release:19.04 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Sat Mar 30 21:51:04 2019 DistUpgraded: 2019-03-30 14:41:04,209 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: disco DistroVariant: ubuntu DkmsStatus: acpi-call, 1.1.0, 4.18.0-16-generic, x86_64: installed acpi-call, 1.1.0, 5.0.0-8-generic, x86_64: installed tp_smapi, 0.43, 5.0.0-8-generic, x86_64: installed virtualbox, 6.0.4, 5.0.0-8-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics Controller [17aa:21dd] InstallationDate: Installed on 2017-07-07 (631 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: LENOVO 78545HG ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-8-generic root=UUID=ce827244-1d04-4bdd-99bf-d70675baefef ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to disco on 2019-03-30 (0 days ago) dmi.bios.date: 04/12/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 8GET44WW (1.21 ) dmi.board.name: 78545HG dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8GET44WW(1.21):bd04/12/2013:svnLENOVO:pn78545HG:pvrThinkPadL420:rvnLENOVO:rn78545HG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad L420 dmi.product.name: 78545HG dmi.product.version: ThinkPad L420 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.1-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1822441/+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 1824216] Re: Linux 5.0 black screen on boot, display flickers (i915 regression with certain laptop panels)
** Summary changed: - Linux 5.0 regression i915 module, black screen on boot for certain laptop panels + Linux 5.0 black screen on boot, display flickers (i915 regression with certain laptop panels) -- 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/1824216 Title: Linux 5.0 black screen on boot, display flickers (i915 regression with certain laptop panels) Status in linux package in Ubuntu: Confirmed Bug description: On my Dell XPS 9575, I get a black screen on boot when running the 19.04 live image, OR after updating from 18.10 to 19.04. It appears to be a kernel related bug that was introduced in 5.0 that is affected by certain laptop panels not conforming to their stated specifications. Several other Dell systems exhibit the same issue, and it's very possible that there are other panels used on other systems that will also have the same issues. Intel is aware of this issue and has already created a patch. You can see the relevant threads here: https://bugs.freedesktop.org/show_bug.cgi?id=109959 And the patch here: https://patchwork.freedesktop.org/patch/296411/ It would be fantastic to get this patch applied before release, as it would be very difficult install 19.04 on the affected systems otherwise. I was able to get the live image booted by adding the nomodeset kernel parameter to grub, so as a work around you can use this approach to install. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824216/+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 1812561] Re: [MacBookPro11, 5] wakes up and suspends in a loop while closed
[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/1812561 Title: [MacBookPro11,5] wakes up and suspends in a loop while closed Status in linux package in Ubuntu: Expired Bug description: Similar bug: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1507472/ The first time suspending works great but after that suspending causes the laptop to wake up regardless of the method used to suspend. Workaround: use kernel 4.19.4. Sidenote: thanks to penalvch for explaining how to report this! ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-13-generic 4.18.0-13.14 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: siilwyn1852 F pulseaudio /dev/snd/controlC1: siilwyn1852 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Jan 20 13:40:14 2019 InstallationDate: Installed on 2019-01-19 (1 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 05ac:8290 Apple, Inc. Bus 001 Device 003: ID 05ac:0274 Apple, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Apple Inc. MacBookPro11,5 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic root=UUID=57f2dc4c-30f7-40b6-a9db-9b6f93c214cb ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-13-generic N/A linux-backports-modules-4.18.0-13-generic N/A linux-firmware 1.175.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/18/2017 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP114.88Z.0172.B25.1706181512 dmi.board.name: Mac-06F11F11946D27C5 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro11,5 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-06F11F11946D27C5 dmi.modalias: dmi:bvnAppleInc.:bvrMBP114.88Z.0172.B25.1706181512:bd06/18/2017:svnAppleInc.:pnMacBookPro11,5:pvr1.0:rvnAppleInc.:rnMac-06F11F11946D27C5:rvrMacBookPro11,5:cvnAppleInc.:ct9:cvrMac-06F11F11946D27C5: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro11,5 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1812561/+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 1822394] Re: [Dell BIOSes dated 27 Mar 2019] laptop keyboard & touchpad not working at gdm screen after boot
I also run a Dell XPS 9575 2 in 1, with BIOS 1.40 and my system is *not* exhibiting this particular problem after a fresh 19.04 install. Keyboard and mouse work fine with GDM, but this is also after booting with the nomodeset kernel boot parameter. Note: for other folks reading this thread wondering how I even got 19.04 installed, I had to install with nomodeset because of a kernel bug with the i915 module with certain laptop panels. I don't think the 4K panels are impacted by this 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/1822394 Title: [Dell BIOSes dated 27 Mar 2019] laptop keyboard & touchpad not working at gdm screen after boot Status in linux package in Ubuntu: Confirmed Bug description: On a dell XPS 15 2-in-1 with the latest 1.4.0 bios, my touchpad and keyboard are unresponsive at the gdm login screen. Keyboard works to unlock encrypted harddrive before that though. If I plug in a USB keyboard or activate my bluetooth mouse, I can use those to log in, and then after logging in the laptop touchpad and keyboard work again. Logging out of the desktop results in the laptop touchpad and keyboard working on the gdm screen. Did not see this behavior before upgrading from 1.2.0 bios to 1.4.0 bios, but also had not rebooted in a while, so not sure if bios or package upgrades triggered this behavior. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gdm3 3.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Mar 29 17:51:00 2019 InstallationDate: Installed on 2018-09-26 (184 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gdm3 UpgradeStatus: Upgraded to disco on 2019-03-11 (18 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822394/+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 1813820] Re: Waking from Suspend causes screen to appear with grey static (like a TV with no signal)
tested the kernel from here today with the same result: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.1-rc4/ generic amd64 -- 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/1813820 Title: Waking from Suspend causes screen to appear with grey static (like a TV with no signal) Status in linux package in Ubuntu: Confirmed Bug description: I am running Kubuntu 18.10. This is the PH517-61 Acer Predator Helios 500 with the Ryzen processor. My first issue I need to deal with is Suspend. I have temporarily disabled suspend in the kcmshell5 configuration. If I do let the laptop suspend and then hit the keyboard I get what appears to be a 1950s TV with no signal. At this point I manually power down and then power up again and am able to view things on screen. Running these commands I get this information: $ journalctl -b -g suspend Compiled without pattern matching support $ journalctl -b -p3 -- Logs begin at Sun 2019-01-27 22:00:42 CST, end at Mon 2019-01-28 21:01:54 CST. -- Jan 28 20:40:33 craig-Predator-PH517-61 kernel: tpm_crb MSFT0101:00: can't request region for resource [mem 0xdf775000-0xdf778fff] Jan 28 20:40:42 craig-Predator-PH517-61 spice-vdagent[2100]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0 $ uname -a Linux craig-Predator-PH517-61 4.18.0-13-generic #14-Ubuntu SMP Wed Dec 5 09:04:24 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux This is a Vega 56 card but Kubuntu seems to think it is a Vega 64: $ lspci -k | grep -EA3 'VGA|3D|Display' 08:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Vega 10 XT [Radeon RX Vega 64] (rev c7) Subsystem: Acer Incorporated [ALI] Vega 10 XT [Radeon RX Vega 64] Kernel driver in use: amdgpu Kernel modules: amdgpu $ glxinfo | grep "OpenGL version" OpenGL version string: 4.4 (Compatibility Profile) Mesa 18.2.2 I will attempt to flesh this out more when I get home. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: craig 2094 F pulseaudio /dev/snd/controlC0: craig 2094 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2019-01-28 (1 days ago) InstallationMedia: Kubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) MachineType: Acer Predator PH517-61 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic root=UUID=5f69d6c1-716a-41ac-a88c-b271a71ce5a0 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 RelatedPackageVersions: linux-restricted-modules-4.18.0-13-generic N/A linux-backports-modules-4.18.0-13-generic N/A linux-firmware 1.175.1 Tags: cosmic Uname: Linux 4.18.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: 10/12/2018 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Cayman_PRS dmi.board.vendor: PRS dmi.board.version: V1.07 dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.07:bd10/12/2018:svnAcer:pnPredatorPH517-61:pvrV1.07:rvnPRS:rnCayman_PRS:rvrV1.07:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: Predator Helios 500 dmi.product.name: Predator PH517-61 dmi.product.sku: dmi.product.version: V1.07 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813820/+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 1824038] Re: Network adapter doesn't work after returning from suspend
Confirmed. The same behaviour in the original kernel 4.18.0-17. -- 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/1824038 Title: Network adapter doesn't work after returning from suspend Status in linux package in Ubuntu: Confirmed Bug description: Fresh install of Ubuntu 18.04 (Linux kernel 4.18.0-17-generic #18~18.04.1-Ubuntu SMP Fri Mar 15 15:27:12 UTC 2019). Network adapter does not resume after suspend. Wifi not available. References to a fix for r8169 driver found. Tried the following fixes: 1. sudo service network-manager restart. This did not work. 2. Script in /lib/systemd/system-sleep/r8169-refresh as described in https://askubuntu.com/questions/1029250/ubuntu-18-04-ethernet-disconnected-after-suspend This did not work. 3. Updated kernel to 4.20.17. This did not work. There is reference to r8169 fixes in version 4.21, but this is not available on the ubuntu mainline kernels https://kernel.ubuntu.com/~kernel-ppa/mainline/ Possibly related to bug #1752772 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-04-08 (2 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Package: linux (not installed) Tags: bionic Uname: Linux 4.20.17-042017-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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824038/+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 1824038] Re: Network adapter doesn't work after returning from suspend
An update on this. I installed kernel 5.0, but the same issue occured. I did notice that my wi-fi can be re-activated using the keyboard wireless switch (Fn-Wifi). I have 2 wi-fi networks available, the normal one and the 5G one. I had been using the 5G one, but switched to use the normal one. My wi-fi came back up, and resumes ok after being in standby. I re-booted using the kernel 5.1.rc4, and it works ok as above. I don't remember trying the physical wi-fi function key before, so it is possible it would have worked in the Ubuntu current mainline kernel 4.18, which I will test next. Could the issue be 5G wifi specific? -- 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/1824038 Title: Network adapter doesn't work after returning from suspend Status in linux package in Ubuntu: Confirmed Bug description: Fresh install of Ubuntu 18.04 (Linux kernel 4.18.0-17-generic #18~18.04.1-Ubuntu SMP Fri Mar 15 15:27:12 UTC 2019). Network adapter does not resume after suspend. Wifi not available. References to a fix for r8169 driver found. Tried the following fixes: 1. sudo service network-manager restart. This did not work. 2. Script in /lib/systemd/system-sleep/r8169-refresh as described in https://askubuntu.com/questions/1029250/ubuntu-18-04-ethernet-disconnected-after-suspend This did not work. 3. Updated kernel to 4.20.17. This did not work. There is reference to r8169 fixes in version 4.21, but this is not available on the ubuntu mainline kernels https://kernel.ubuntu.com/~kernel-ppa/mainline/ Possibly related to bug #1752772 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-04-08 (2 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Package: linux (not installed) Tags: bionic Uname: Linux 4.20.17-042017-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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824038/+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 1821820] Re: Cannot boot or install - have to use nomodeset
Sorry for the spam, last post for now I promise! Reading this bug report more closely, it does appear different than the bug I am encountering. With *this* bug, one sees a black screen *with* a cursor, my symptoms are different, as the laptop panel is failing display link training, so nothing is displayed, it flickers a couple of times and nothing every appears. *This* bug appears to be Xorg related, but the bug I'm encountering (which is known on bugs.freedesktop.org) is a bug with the i915 kernel module. For now I've removed the duplicate status of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824216 and will add comments there moving forward. Again apologies for posting so many times, I honestly thought this was the same issue I'm encountering. -- 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/1821820 Title: Cannot boot or install - have to use nomodeset Status in linux package in Ubuntu: Fix Released Status in xorg-server package in Ubuntu: Fix Committed Bug description: On this 19.04 beta I have to use nomodeset to boot & install Ubuntu Budgie. This is different behaviour from 18.04 and 18.10 where it booted and installed just fine without nomodeset. Without nomodeset, grub/efi disappears, and after a while a solid rather than blinking cursor on a black screen is seen. It does not boot into a live session, nor displays the ubiquity window ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xserver-xorg-video-intel 2:2.99.917+git20180925-2 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: Budgie:GNOME Date: Tue Mar 26 23:40:49 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:22b1] (rev 21) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [103c:80bf] InstallationDate: Installed on 2019-03-26 (0 days ago) InstallationMedia: Ubuntu-Budgie 19.04 "Disco Dingo" - Alpha amd64 (20190326.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0a5c:216d Broadcom Corp. BCM43142A0 Bluetooth 4.0 Bus 001 Device 003: ID 05c8:022a Cheng Uei Precision Industry Co., Ltd (Foxlink) Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Notebook ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic root=UUID=62ab7c7b-50c8-4719-98c6-55991179ff20 ro nomodeset quiet splash SourcePackage: xserver-xorg-video-intel UpgradeStatus: No upgrade log present (probably fresh install) XorgLogOld: dmi.bios.date: 02/15/2016 dmi.bios.vendor: Insyde dmi.bios.version: F.1F dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80BF dmi.board.vendor: HP dmi.board.version: 95.16 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.1F:bd02/15/2016:svnHP:pnHPNotebook:pvr:rvnHP:rn80BF:rvr95.16:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook dmi.product.sku: N9S73EA#ABU dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821820/+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 1824216] Re: Linux 5.0 regression i915 module, black screen on boot for certain laptop panels
OK reading the original bug reports more closely, this *does* appear to be a different bug entirely. Because we never see a cursor on the screen, the laptop panel literally fails link training. ** This bug is no longer a duplicate of bug 1821820 Cannot boot or install - have to use nomodeset -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1824216 Title: Linux 5.0 regression i915 module, black screen on boot for certain laptop panels Status in linux package in Ubuntu: Confirmed Bug description: On my Dell XPS 9575, I get a black screen on boot when running the 19.04 live image, OR after updating from 18.10 to 19.04. It appears to be a kernel related bug that was introduced in 5.0 that is affected by certain laptop panels not conforming to their stated specifications. Several other Dell systems exhibit the same issue, and it's very possible that there are other panels used on other systems that will also have the same issues. Intel is aware of this issue and has already created a patch. You can see the relevant threads here: https://bugs.freedesktop.org/show_bug.cgi?id=109959 And the patch here: https://patchwork.freedesktop.org/patch/296411/ It would be fantastic to get this patch applied before release, as it would be very difficult install 19.04 on the affected systems otherwise. I was able to get the live image booted by adding the nomodeset kernel parameter to grub, so as a work around you can use this approach to install. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824216/+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 1821820] Re: Cannot boot or install - have to use nomodeset
Here are drm messages from logs booting up with drm.debug=14 with 5.0.0-11.12. You can see the link training issues are still present. 21:00:11 kernel: [drm:intel_dp_get_link_train_fallback_values [i915]] Retrying Link training for eDP with same parameters 21:00:11 kernel: [drm:intel_dp_start_link_train [i915]] [CONNECTOR:85:eDP-1] Link Training failed at link rate = 324000, lane count = 1 21:00:11 kernel: [drm:intel_dp_set_signal_levels [i915]] Using pre-emphasis level 0 21:00:11 kernel: [drm:intel_dp_program_link_training_pattern [i915]] Using DP training pattern TPS1 21:00:11 kernel: [drm:intel_dp_set_signal_levels [i915]] Using pre-emphasis level 0 21:00:11 kernel: [drm:intel_dp_start_link_train [i915]] Using LINK_RATE_SET value 04 ** Attachment added: "dmesg with drm.debug=14" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821820/+attachment/527/+files/log%20messages -- 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/1821820 Title: Cannot boot or install - have to use nomodeset Status in linux package in Ubuntu: Fix Released Status in xorg-server package in Ubuntu: Fix Committed Bug description: On this 19.04 beta I have to use nomodeset to boot & install Ubuntu Budgie. This is different behaviour from 18.04 and 18.10 where it booted and installed just fine without nomodeset. Without nomodeset, grub/efi disappears, and after a while a solid rather than blinking cursor on a black screen is seen. It does not boot into a live session, nor displays the ubiquity window ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xserver-xorg-video-intel 2:2.99.917+git20180925-2 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: Budgie:GNOME Date: Tue Mar 26 23:40:49 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:22b1] (rev 21) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [103c:80bf] InstallationDate: Installed on 2019-03-26 (0 days ago) InstallationMedia: Ubuntu-Budgie 19.04 "Disco Dingo" - Alpha amd64 (20190326.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0a5c:216d Broadcom Corp. BCM43142A0 Bluetooth 4.0 Bus 001 Device 003: ID 05c8:022a Cheng Uei Precision Industry Co., Ltd (Foxlink) Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Notebook ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic root=UUID=62ab7c7b-50c8-4719-98c6-55991179ff20 ro nomodeset quiet splash SourcePackage: xserver-xorg-video-intel UpgradeStatus: No upgrade log present (probably fresh install) XorgLogOld: dmi.bios.date: 02/15/2016 dmi.bios.vendor: Insyde dmi.bios.version: F.1F dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80BF dmi.board.vendor: HP dmi.board.version: 95.16 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.1F:bd02/15/2016:svnHP:pnHPNotebook:pvr:rvnHP:rn80BF:rvr95.16:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook dmi.product.sku: N9S73EA#ABU dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821820/+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 1824216] Re: Linux 5.0 regression i915 module, black screen on boot for certain laptop panels
*** This bug is a duplicate of bug 1821820 *** https://bugs.launchpad.net/bugs/1821820 So I'm not sure if this bug is actually a duplicate after all. I've done a fresh install of 19.04 and upgraded to kernel 5.0.0-11.12 (which supposedly fixed the other bug), and the link training issues with my Dell XPS 9575 laptop panel are still present. So it looks like the primary issue i'm experiencing has not yet been resolved. -- 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/1824216 Title: Linux 5.0 regression i915 module, black screen on boot for certain laptop panels Status in linux package in Ubuntu: Confirmed Bug description: On my Dell XPS 9575, I get a black screen on boot when running the 19.04 live image, OR after updating from 18.10 to 19.04. It appears to be a kernel related bug that was introduced in 5.0 that is affected by certain laptop panels not conforming to their stated specifications. Several other Dell systems exhibit the same issue, and it's very possible that there are other panels used on other systems that will also have the same issues. Intel is aware of this issue and has already created a patch. You can see the relevant threads here: https://bugs.freedesktop.org/show_bug.cgi?id=109959 And the patch here: https://patchwork.freedesktop.org/patch/296411/ It would be fantastic to get this patch applied before release, as it would be very difficult install 19.04 on the affected systems otherwise. I was able to get the live image booted by adding the nomodeset kernel parameter to grub, so as a work around you can use this approach to install. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824216/+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 1824216] Re: Linux 5.0 regression i915 module, black screen on boot for certain laptop panels
*** This bug is a duplicate of bug 1821820 *** https://bugs.launchpad.net/bugs/1821820 Here are the relevant portions of my dmesg with drm.debug=14 as a boot paramater. You can see my laptops display panel is still failing link training. 21:00:11 kernel: [drm:intel_dp_get_link_train_fallback_values [i915]] Retrying Link training for eDP with same parameters 21:00:11 kernel: [drm:intel_dp_start_link_train [i915]] [CONNECTOR:85:eDP-1] Link Training failed at link rate = 324000, lane count = 1 21:00:11 kernel: [drm:intel_dp_set_signal_levels [i915]] Using pre-emphasis level 0 21:00:11 kernel: [drm:intel_dp_program_link_training_pattern [i915]] Using DP training pattern TPS1 21:00:11 kernel: [drm:intel_dp_set_signal_levels [i915]] Using pre-emphasis level 0 21:00:11 kernel: [drm:intel_dp_start_link_train [i915]] Using LINK_RATE_SET value 04 ** Attachment added: "dmesg with drm.debug=14" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824216/+attachment/5255576/+files/log%20messages -- 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/1824216 Title: Linux 5.0 regression i915 module, black screen on boot for certain laptop panels Status in linux package in Ubuntu: Confirmed Bug description: On my Dell XPS 9575, I get a black screen on boot when running the 19.04 live image, OR after updating from 18.10 to 19.04. It appears to be a kernel related bug that was introduced in 5.0 that is affected by certain laptop panels not conforming to their stated specifications. Several other Dell systems exhibit the same issue, and it's very possible that there are other panels used on other systems that will also have the same issues. Intel is aware of this issue and has already created a patch. You can see the relevant threads here: https://bugs.freedesktop.org/show_bug.cgi?id=109959 And the patch here: https://patchwork.freedesktop.org/patch/296411/ It would be fantastic to get this patch applied before release, as it would be very difficult install 19.04 on the affected systems otherwise. I was able to get the live image booted by adding the nomodeset kernel parameter to grub, so as a work around you can use this approach to install. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824216/+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 1821820] Re: Cannot boot or install - have to use nomodeset
I just tested with a fresh install of 19.04 (booted up with nomodeset and installed). After installation I confirmed I was running 5.0.0-11.12, but the laptop panel link training issue is still present (Dell XPS 9575) causing a black screen on boot. The only way to boot is with nomodeset as a kernel boot parameter. Note: as a side issue it was virtually impossible to bring up the grub menu now in 19.04 (I think because the timeout is set to zero). I had to make sure to chroot into the newly installed system (after installing) and then edit the /boot/grub/grub.cfg file and manually edit the timeout value. I thought that the this Ubuntu bug was referring to this bug (REGRESSION: black screen with linux 5.0 when starting X) https://bugs.freedesktop.org/show_bug.cgi?id=109959), but perhaps it's referencing another issue entirely? Not sure, but either way the failed link training bug still appears to be present with 5.0.0-11.12 causing black screens on bootups with certain laptop panels. Reading through that thread on bugs.freedesktop.org, Intel realized the problem was caused by certain laptop panels not reporting their specifications correctly (Dell XPS systems appear affected, but other laptops will most likely also be affected), so the code they added to optimize the link (fast and narrow vs. slow and wide) would cause certain laptop panels to never display anything with modesetting. Towards the end of the thread to posted a 5.0 backport patch which completely removes the link optimizations, https://patchwork.freedesktop.org/patch/296411/. Based on the Ubuntu kernel changelog I'm not sure exactly what patch was reverted. My guess is it's for another issue entirely. I'll probably try to compile the Ubuntu kernel with their the freedesktop.org backport patch applied and report back. I can also post my dmeg here for reference. ** Bug watch added: freedesktop.org Bugzilla #109959 https://bugs.freedesktop.org/show_bug.cgi?id=109959 -- 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/1821820 Title: Cannot boot or install - have to use nomodeset Status in linux package in Ubuntu: Fix Released Status in xorg-server package in Ubuntu: Fix Committed Bug description: On this 19.04 beta I have to use nomodeset to boot & install Ubuntu Budgie. This is different behaviour from 18.04 and 18.10 where it booted and installed just fine without nomodeset. Without nomodeset, grub/efi disappears, and after a while a solid rather than blinking cursor on a black screen is seen. It does not boot into a live session, nor displays the ubiquity window ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xserver-xorg-video-intel 2:2.99.917+git20180925-2 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: Budgie:GNOME Date: Tue Mar 26 23:40:49 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:22b1] (rev 21) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [103c:80bf] InstallationDate: Installed on 2019-03-26 (0 days ago) InstallationMedia: Ubuntu-Budgie 19.04 "Disco Dingo" - Alpha amd64 (20190326.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0a5c:216d Broadcom Corp. BCM43142A0 Bluetooth 4.0 Bus 001 Device 003: ID 05c8:022a Cheng Uei Precision Industry Co., Ltd (Foxlink) Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Notebook ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic root=UUID=62ab7c7b-50c8-4719-98c6-55991179ff20 ro nomodeset quiet splash SourcePackage: xserver-xorg-video-intel UpgradeStatus: No upgrade log present (probably fresh install) XorgLogOld: dmi.bios.date: 02/15/2016 dmi.bios.vendor: Insyde dmi.bios.version: F.1F dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80BF dmi.board.vendor: HP dmi.board.version: 95.16 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.1F:bd02/15/2016:svnHP:pnHPNotebook:pvr:rvnHP:rn80BF:rvr95.16:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook dmi.product.sku: N9S73EA#ABU dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2
[Kernel-packages] [Bug 1821820] Re: Cannot boot or install - have to use nomodeset
As a side note, this was the bug I had originally opened up in launchpad, which I thought might have been a duplicate of this bug (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824216) -- 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/1821820 Title: Cannot boot or install - have to use nomodeset Status in linux package in Ubuntu: Fix Released Status in xorg-server package in Ubuntu: Fix Committed Bug description: On this 19.04 beta I have to use nomodeset to boot & install Ubuntu Budgie. This is different behaviour from 18.04 and 18.10 where it booted and installed just fine without nomodeset. Without nomodeset, grub/efi disappears, and after a while a solid rather than blinking cursor on a black screen is seen. It does not boot into a live session, nor displays the ubiquity window ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xserver-xorg-video-intel 2:2.99.917+git20180925-2 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: Budgie:GNOME Date: Tue Mar 26 23:40:49 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:22b1] (rev 21) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [103c:80bf] InstallationDate: Installed on 2019-03-26 (0 days ago) InstallationMedia: Ubuntu-Budgie 19.04 "Disco Dingo" - Alpha amd64 (20190326.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0a5c:216d Broadcom Corp. BCM43142A0 Bluetooth 4.0 Bus 001 Device 003: ID 05c8:022a Cheng Uei Precision Industry Co., Ltd (Foxlink) Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Notebook ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic root=UUID=62ab7c7b-50c8-4719-98c6-55991179ff20 ro nomodeset quiet splash SourcePackage: xserver-xorg-video-intel UpgradeStatus: No upgrade log present (probably fresh install) XorgLogOld: dmi.bios.date: 02/15/2016 dmi.bios.vendor: Insyde dmi.bios.version: F.1F dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80BF dmi.board.vendor: HP dmi.board.version: 95.16 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.1F:bd02/15/2016:svnHP:pnHPNotebook:pvr:rvnHP:rn80BF:rvr95.16:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook dmi.product.sku: N9S73EA#ABU dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821820/+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 1759836]
I fix the problem with this approach:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1759836/comments/70
from "Florian Dittmer (fd81)"
"
Following the instructions mentioned by one user in the comments helped me to
solve the cpu load issue with udev-239 and kernel 4.18.17, while Bluetooth
still works.
Run the following command:
/lib/systemd/systemd-udevd -D
This should print garbage in endless loop containing
".../97-hid2hci.rules:"
If so, edit /lib/udev/rules.d/97-hid2hci.rules
and add
ACTION=="add",
in front of line mentioned by above command.
In my case, I had to change the following lines in 97-hid2hci.rules
from:
ATTR{bInterfaceClass}=="03", ATTR{bInterfaceSubClass}=="01",
ATTR{bInterfaceProtocol}=="02", \
ATTRS{bDeviceClass}=="00", ATTRS{idVendor}=="413c",
ATTRS{bmAttributes}=="e0", \
RUN+="hid2hci --method=dell --devpath=%p", ENV{HID2HCI_SWITCH}="1"
to:
ACTION=="add", ATTR{bInterfaceClass}=="03", ATTR{bInterfaceSubClass}=="01",
ATTR{bInterfaceProtocol}=="02", \
ATTRS{bDeviceClass}=="00", ATTRS{idVendor}=="413c",
ATTRS{bmAttributes}=="e0", \
RUN+="hid2hci --method=dell --devpath=%p", ENV{HID2HCI_SWITCH}="1"
And this fixed the issue (after reboot).
"
from
--
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/1759836
Title:
systemd-udevd consumes 100% of CPU
Status in linux:
Confirmed
Status in The Ubuntu Power Consumption Project:
New
Status in bluez package in Ubuntu:
Invalid
Status in linux package in Ubuntu:
Incomplete
Status in systemd package in Ubuntu:
Confirmed
Bug description:
The systemd-udevd proccess consumes 100% of a thread everytime, but
i'm not noticing any difference in my computer.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: systemd 237-3ubuntu6
ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
Uname: Linux 4.15.0-13-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.9-0ubuntu2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Mar 29 08:52:54 2018
InstallationDate: Installed on 2018-03-05 (23 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180304)
MachineType: Dell Inc. Inspiron N5010
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic
root=UUID=3c29e292-f1ae-45e1-a0ed-a82524278ce1 ro quiet splash vt.handoff=1
SourcePackage: systemd
SystemdDelta:
[EXTENDED] /lib/systemd/system/rc-local.service →
/lib/systemd/system/rc-local.service.d/debian.conf
[EXTENDED] /lib/systemd/system/user@.service →
/lib/systemd/system/user@.service.d/timeout.conf
2 overridden configuration files found.
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/25/2011
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A12
dmi.board.name: 08R0GW
dmi.board.vendor: Dell Inc.
dmi.board.version: A12
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: A12
dmi.modalias:
dmi:bvnDellInc.:bvrA12:bd01/25/2011:svnDellInc.:pnInspironN5010:pvrA12:rvnDellInc.:rn08R0GW:rvrA12:cvnDellInc.:ct8:cvrA12:
dmi.product.name: Inspiron N5010
dmi.product.version: A12
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel/+bug/1759836/+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 1759836]
These nerd-level suggestions all work but the root cause (the real problem) is not solved and will pop up again. How is the non-nerd supposed to do this? ...would you want your neighbor editing your system files Someone needs to fix this permanently! -- 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/1759836 Title: systemd-udevd consumes 100% of CPU Status in linux: Confirmed Status in The Ubuntu Power Consumption Project: New Status in bluez package in Ubuntu: Invalid Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Confirmed Bug description: The systemd-udevd proccess consumes 100% of a thread everytime, but i'm not noticing any difference in my computer. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu6 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 29 08:52:54 2018 InstallationDate: Installed on 2018-03-05 (23 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180304) MachineType: Dell Inc. Inspiron N5010 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic root=UUID=3c29e292-f1ae-45e1-a0ed-a82524278ce1 ro quiet splash vt.handoff=1 SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/25/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 08R0GW dmi.board.vendor: Dell Inc. dmi.board.version: A12 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A12 dmi.modalias: dmi:bvnDellInc.:bvrA12:bd01/25/2011:svnDellInc.:pnInspironN5010:pvrA12:rvnDellInc.:rn08R0GW:rvrA12:cvnDellInc.:ct8:cvrA12: dmi.product.name: Inspiron N5010 dmi.product.version: A12 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/kernel/+bug/1759836/+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 1759836]
I agree with you, its not the best solution. This bug impact many users! At next release of this softwares this bug has to be fixed. But I lost many days to fix this problem, and I'm sharing this 'hard approach' at forums I had visited before. So other people do not waste so much time! -- 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/1759836 Title: systemd-udevd consumes 100% of CPU Status in linux: Confirmed Status in The Ubuntu Power Consumption Project: New Status in bluez package in Ubuntu: Invalid Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Confirmed Bug description: The systemd-udevd proccess consumes 100% of a thread everytime, but i'm not noticing any difference in my computer. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu6 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 29 08:52:54 2018 InstallationDate: Installed on 2018-03-05 (23 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180304) MachineType: Dell Inc. Inspiron N5010 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic root=UUID=3c29e292-f1ae-45e1-a0ed-a82524278ce1 ro quiet splash vt.handoff=1 SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/25/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 08R0GW dmi.board.vendor: Dell Inc. dmi.board.version: A12 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A12 dmi.modalias: dmi:bvnDellInc.:bvrA12:bd01/25/2011:svnDellInc.:pnInspironN5010:pvrA12:rvnDellInc.:rn08R0GW:rvrA12:cvnDellInc.:ct8:cvrA12: dmi.product.name: Inspiron N5010 dmi.product.version: A12 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/kernel/+bug/1759836/+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 1788018]
An update: The problem I reported in January went away on its own after a few weeks of having the problem every single day when I booted each morning. I was installing Ubuntu software updates when they became available during that time. There is something going on during boot that causes this problem. "my speculation" is that I suspect a timing issue with the way things are initialized during boot up that leads to the problem. Some strange timing issue is occurring which causes systemd-udevd to fall into an infinite loop (continuously looking for something or to be notified about an action completion) and drive one of the processor cores to 100%. When a new kernel was installed or something was done to change initialization activity during boot the problem went away because the timing problem that created it was changed. I believe that some kind of race condition may be at the root of the problem. >From my earlier search on the problem symptoms, it seems that when systemd-udevd isn't working correctly you can get numerous confusing symptoms that mysteriously go away when the something changes timing conditions during boot. Since the problem is in the kernel then it effects other systems besides Ubuntu. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1788018 Title: udevd keeps binding and unbinding some usb device und uses all cpu Status in Linux: Confirmed Status in linux package in Ubuntu: Incomplete Bug description: It first appeared when I upgraded ubuntu studio to 18.04 udevd started to use all available cpu. now I'm running ubuntu desktop from a usb key and it's still the same udevadm monitor returns: KERNEL[2512.539491] unbind /devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb) UDEV [2512.540201] bind /devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb) KERNEL[2512.566574] bind /devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb) KERNEL[2512.566866] unbind /devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb) UDEV [2512.567499] unbind /devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb) KERNEL[2512.594050] bind /devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb) KERNEL[2512.594310] unbind /devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb) UDEV [2512.596510] bind /devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb) KERNEL[2512.620736] bind /devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb) KERNEL[2512.624606] unbind /devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb) UDEV [2512.634706] unbind /devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb) ... WORKAROUND: Remove file: /lib/udev/rules.d/97-hid2hci.rules ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: udev 237-3ubuntu10.3 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CasperVersion: 1.394 CustomUdevRuleFiles: 70-snap.core.rules Date: Mon Aug 20 18:54:48 2018 ExecutablePath: /lib/systemd/systemd-udevd LiveMediaBuild: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. Vostro 3300 ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/10/2010 dmi.bios.vendor: Dell Inc. dmi.bios.version: A01 dmi.board.name: 07JC8T dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA01:bd02/10/2010:svnDellInc.:pnVostro3300:pvrNotSpecified:rvnDellInc.:rn07JC8T:rvrA00:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Vostro 3300 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1788018/+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 1788018]
These nerd-level suggestions all work but the root cause (the real problem) is not solved and will pop up again. How is the non-nerd supposed to do this? ...would you want your neighbor editing your system files Someone needs to fix this permanently! -- 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/1788018 Title: udevd keeps binding and unbinding some usb device und uses all cpu Status in Linux: Confirmed Status in linux package in Ubuntu: Incomplete Bug description: It first appeared when I upgraded ubuntu studio to 18.04 udevd started to use all available cpu. now I'm running ubuntu desktop from a usb key and it's still the same udevadm monitor returns: KERNEL[2512.539491] unbind /devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb) UDEV [2512.540201] bind /devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb) KERNEL[2512.566574] bind /devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb) KERNEL[2512.566866] unbind /devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb) UDEV [2512.567499] unbind /devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb) KERNEL[2512.594050] bind /devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb) KERNEL[2512.594310] unbind /devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb) UDEV [2512.596510] bind /devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb) KERNEL[2512.620736] bind /devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb) KERNEL[2512.624606] unbind /devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb) UDEV [2512.634706] unbind /devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb) ... WORKAROUND: Remove file: /lib/udev/rules.d/97-hid2hci.rules ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: udev 237-3ubuntu10.3 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CasperVersion: 1.394 CustomUdevRuleFiles: 70-snap.core.rules Date: Mon Aug 20 18:54:48 2018 ExecutablePath: /lib/systemd/systemd-udevd LiveMediaBuild: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. Vostro 3300 ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/10/2010 dmi.bios.vendor: Dell Inc. dmi.bios.version: A01 dmi.board.name: 07JC8T dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA01:bd02/10/2010:svnDellInc.:pnVostro3300:pvrNotSpecified:rvnDellInc.:rn07JC8T:rvrA00:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Vostro 3300 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1788018/+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 1759836]
I have the same problem, that John related. I have dell n5010, with SSD. Run F30 and suffer to connect bluedio t4. If I Uninstall the package bluez-hid2hci, the problem of boot cpu with systemd-udevd dissappear. But at same time, I lost the connection of bluetooth device. -- 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/1759836 Title: systemd-udevd consumes 100% of CPU Status in linux: Confirmed Status in The Ubuntu Power Consumption Project: New Status in bluez package in Ubuntu: Invalid Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Confirmed Bug description: The systemd-udevd proccess consumes 100% of a thread everytime, but i'm not noticing any difference in my computer. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu6 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 29 08:52:54 2018 InstallationDate: Installed on 2018-03-05 (23 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180304) MachineType: Dell Inc. Inspiron N5010 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic root=UUID=3c29e292-f1ae-45e1-a0ed-a82524278ce1 ro quiet splash vt.handoff=1 SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/25/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 08R0GW dmi.board.vendor: Dell Inc. dmi.board.version: A12 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A12 dmi.modalias: dmi:bvnDellInc.:bvrA12:bd01/25/2011:svnDellInc.:pnInspironN5010:pvrA12:rvnDellInc.:rn08R0GW:rvrA12:cvnDellInc.:ct8:cvrA12: dmi.product.name: Inspiron N5010 dmi.product.version: A12 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/kernel/+bug/1759836/+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 1759836]
An update: The problem I reported in January went away on its own after a few weeks of having the problem every single day when I booted each morning. I was installing Ubuntu software updates when they became available during that time. There is something going on during boot that causes this problem. "my speculation" is that I suspect a timing issue with the way things are initialized during boot up that leads to the problem. Some strange timing issue is occurring which causes systemd-udevd to fall into an infinite loop (continuously looking for something or to be notified about an action completion) and drive one of the processor cores to 100%. When a new kernel was installed or something was done to change initialization activity during boot the problem went away because the timing problem that created it was changed. I believe that some kind of race condition may be at the root of the problem. >From my earlier search on the problem symptoms, it seems that when systemd-udevd isn't working correctly you can get numerous confusing symptoms that mysteriously go away when the something changes timing conditions during boot. Since the problem is in the kernel then it effects other systems besides 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/1759836 Title: systemd-udevd consumes 100% of CPU Status in linux: Confirmed Status in The Ubuntu Power Consumption Project: New Status in bluez package in Ubuntu: Invalid Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Confirmed Bug description: The systemd-udevd proccess consumes 100% of a thread everytime, but i'm not noticing any difference in my computer. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu6 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 29 08:52:54 2018 InstallationDate: Installed on 2018-03-05 (23 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180304) MachineType: Dell Inc. Inspiron N5010 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic root=UUID=3c29e292-f1ae-45e1-a0ed-a82524278ce1 ro quiet splash vt.handoff=1 SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/25/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 08R0GW dmi.board.vendor: Dell Inc. dmi.board.version: A12 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A12 dmi.modalias: dmi:bvnDellInc.:bvrA12:bd01/25/2011:svnDellInc.:pnInspironN5010:pvrA12:rvnDellInc.:rn08R0GW:rvrA12:cvnDellInc.:ct8:cvrA12: dmi.product.name: Inspiron N5010 dmi.product.version: A12 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/kernel/+bug/1759836/+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 1788018]
I agree with you, its not the best solution. This bug impact many users! At next release of this softwares this bug has to be fixed. But I lost many days to fix this problem, and I'm sharing this 'hard approach' at forums I had visited before. So other people do not waste so much time! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1788018 Title: udevd keeps binding and unbinding some usb device und uses all cpu Status in Linux: Confirmed Status in linux package in Ubuntu: Incomplete Bug description: It first appeared when I upgraded ubuntu studio to 18.04 udevd started to use all available cpu. now I'm running ubuntu desktop from a usb key and it's still the same udevadm monitor returns: KERNEL[2512.539491] unbind /devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb) UDEV [2512.540201] bind /devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb) KERNEL[2512.566574] bind /devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb) KERNEL[2512.566866] unbind /devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb) UDEV [2512.567499] unbind /devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb) KERNEL[2512.594050] bind /devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb) KERNEL[2512.594310] unbind /devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb) UDEV [2512.596510] bind /devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb) KERNEL[2512.620736] bind /devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb) KERNEL[2512.624606] unbind /devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb) UDEV [2512.634706] unbind /devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb) ... WORKAROUND: Remove file: /lib/udev/rules.d/97-hid2hci.rules ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: udev 237-3ubuntu10.3 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CasperVersion: 1.394 CustomUdevRuleFiles: 70-snap.core.rules Date: Mon Aug 20 18:54:48 2018 ExecutablePath: /lib/systemd/systemd-udevd LiveMediaBuild: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. Vostro 3300 ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/10/2010 dmi.bios.vendor: Dell Inc. dmi.bios.version: A01 dmi.board.name: 07JC8T dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA01:bd02/10/2010:svnDellInc.:pnVostro3300:pvrNotSpecified:rvnDellInc.:rn07JC8T:rvrA00:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Vostro 3300 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1788018/+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 1788018]
I fix the problem with this approach:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1759836/comments/70
from "Florian Dittmer (fd81)"
"
Following the instructions mentioned by one user in the comments helped me to
solve the cpu load issue with udev-239 and kernel 4.18.17, while Bluetooth
still works.
Run the following command:
/lib/systemd/systemd-udevd -D
This should print garbage in endless loop containing
".../97-hid2hci.rules:"
If so, edit /lib/udev/rules.d/97-hid2hci.rules
and add
ACTION=="add",
in front of line mentioned by above command.
In my case, I had to change the following lines in 97-hid2hci.rules
from:
ATTR{bInterfaceClass}=="03", ATTR{bInterfaceSubClass}=="01",
ATTR{bInterfaceProtocol}=="02", \
ATTRS{bDeviceClass}=="00", ATTRS{idVendor}=="413c",
ATTRS{bmAttributes}=="e0", \
RUN+="hid2hci --method=dell --devpath=%p", ENV{HID2HCI_SWITCH}="1"
to:
ACTION=="add", ATTR{bInterfaceClass}=="03", ATTR{bInterfaceSubClass}=="01",
ATTR{bInterfaceProtocol}=="02", \
ATTRS{bDeviceClass}=="00", ATTRS{idVendor}=="413c",
ATTRS{bmAttributes}=="e0", \
RUN+="hid2hci --method=dell --devpath=%p", ENV{HID2HCI_SWITCH}="1"
And this fixed the issue (after reboot).
"
from
--
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/1788018
Title:
udevd keeps binding and unbinding some usb device und uses all cpu
Status in Linux:
Confirmed
Status in linux package in Ubuntu:
Incomplete
Bug description:
It first appeared when I upgraded ubuntu studio to 18.04
udevd started to use all available cpu.
now I'm running ubuntu desktop from a usb key and it's still the same
udevadm monitor returns:
KERNEL[2512.539491] unbind
/devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb)
UDEV [2512.540201] bind
/devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb)
KERNEL[2512.566574] bind
/devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb)
KERNEL[2512.566866] unbind
/devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb)
UDEV [2512.567499] unbind
/devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb)
KERNEL[2512.594050] bind
/devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb)
KERNEL[2512.594310] unbind
/devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb)
UDEV [2512.596510] bind
/devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb)
KERNEL[2512.620736] bind
/devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb)
KERNEL[2512.624606] unbind
/devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb)
UDEV [2512.634706] unbind
/devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb)
...
WORKAROUND: Remove file:
/lib/udev/rules.d/97-hid2hci.rules
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: udev 237-3ubuntu10.3
ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
Uname: Linux 4.15.0-29-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
CasperVersion: 1.394
CustomUdevRuleFiles: 70-snap.core.rules
Date: Mon Aug 20 18:54:48 2018
ExecutablePath: /lib/systemd/systemd-udevd
LiveMediaBuild: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
MachineType: Dell Inc. Vostro 3300
ProcEnviron:
LANG=C.UTF-8
PATH=(custom, no user)
ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper
initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/10/2010
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A01
dmi.board.name: 07JC8T
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: Not Specified
dmi.modalias:
dmi:bvnDellInc.:bvrA01:bd02/10/2010:svnDellInc.:pnVostro3300:pvrNotSpecified:rvnDellInc.:rn07JC8T:rvrA00:cvnDellInc.:ct8:cvrNotSpecified:
dmi.product.name: Vostro 3300
dmi.product.version: Not Specified
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1788018/+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 1788018]
I have the same problem, that John related. I have dell n5010, with SSD. Run F30 and suffer to connect bluedio t4. If I Uninstall the package bluez-hid2hci, the problem of boot cpu with systemd-udevd dissappear. But at same time, I lost the connection of bluetooth device. -- 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/1788018 Title: udevd keeps binding and unbinding some usb device und uses all cpu Status in Linux: Confirmed Status in linux package in Ubuntu: Incomplete Bug description: It first appeared when I upgraded ubuntu studio to 18.04 udevd started to use all available cpu. now I'm running ubuntu desktop from a usb key and it's still the same udevadm monitor returns: KERNEL[2512.539491] unbind /devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb) UDEV [2512.540201] bind /devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb) KERNEL[2512.566574] bind /devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb) KERNEL[2512.566866] unbind /devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb) UDEV [2512.567499] unbind /devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb) KERNEL[2512.594050] bind /devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb) KERNEL[2512.594310] unbind /devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb) UDEV [2512.596510] bind /devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb) KERNEL[2512.620736] bind /devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb) KERNEL[2512.624606] unbind /devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb) UDEV [2512.634706] unbind /devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb) ... WORKAROUND: Remove file: /lib/udev/rules.d/97-hid2hci.rules ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: udev 237-3ubuntu10.3 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CasperVersion: 1.394 CustomUdevRuleFiles: 70-snap.core.rules Date: Mon Aug 20 18:54:48 2018 ExecutablePath: /lib/systemd/systemd-udevd LiveMediaBuild: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. Vostro 3300 ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/10/2010 dmi.bios.vendor: Dell Inc. dmi.bios.version: A01 dmi.board.name: 07JC8T dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA01:bd02/10/2010:svnDellInc.:pnVostro3300:pvrNotSpecified:rvnDellInc.:rn07JC8T:rvrA00:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Vostro 3300 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1788018/+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 1824259] Re: Headphone jack switch sense is inverted: plugging in headphones disables headphone output
Please install this deb for kernel-5.0.0-8-generic, and remove quirk=0x21 for that module, reboot and redo the test. In this deb, the codec driver of rt5645.c handles the comment #4. let us see test if it works or not. dpkg -i this.deb remove the quirk=0x21 reboot thx. ** Attachment added: "oem-audio-asoc-daily-dkms_0.1_all.deb" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824259/+attachment/524/+files/oem-audio-asoc-daily-dkms_0.1_all.deb -- 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/1824259 Title: Headphone jack switch sense is inverted: plugging in headphones disables headphone output Status in linux package in Ubuntu: Confirmed Bug description: My machine is a LattePanda board, which uses a "chtrt5645" device as a sound card. It has a single headphone output jack, which I think is a TRRS jack, with a mic input, such as is normally used on phones. When I don't have headphones plugged in, the system thinks headphones *are* plugged in. Gnome Control Center shows my audio device as being headphones. If I insert a headphone connector partway into the jack, I can even get sound in the headphones. But if I plug the headphones all the way in, the system decided that I have *un*plugged the headphones, and switches output over to "Speaker". The system doesn't actually have a speaker, only a headphone jack. And when the system switches over to "Speaker", I get no sound out of the headphones, even if I open "pavucontrol" and swap over to "Headphones (unplugged)" on the "Output Devices" tab. This is what "pacmd"'s "list-cards" command says with my headphones *unplugged*: 2 card(s) available. index: 0 name: driver: owner module: 7 properties: alsa.card = "1" alsa.card_name = "Intel HDMI/DP LPE Audio" alsa.long_card_name = "Intel HDMI/DP LPE Audio" alsa.driver_name = "snd_hdmi_lpe_audio" device.bus_path = "pci-:00:02.0-platform-hdmi-lpe-audio" sysfs.path = "/devices/pci:00/:00:02.0/hdmi-lpe-audio/sound/card1" device.bus = "pci" device.vendor.id = "8086" device.vendor.name = "Intel Corporation" device.product.id = "22b0" device.product.name = "Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers" device.string = "1" device.description = "Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers" module-udev-detect.discovered = "1" device.icon_name = "audio-card-pci" profiles: output:hdmi-stereo: Digital Stereo (HDMI) Output (priority 5900, available: no) output:hdmi-surround: Digital Surround 5.1 (HDMI) Output (priority 800, available: no) output:hdmi-surround71: Digital Surround 7.1 (HDMI) Output (priority 800, available: no) output:hdmi-stereo-extra1: Digital Stereo (HDMI 2) Output (priority 5700, available: no) output:hdmi-surround-extra1: Digital Surround 5.1 (HDMI 2) Output (priority 600, available: no) output:hdmi-surround71-extra1: Digital Surround 7.1 (HDMI 2) Output (priority 600, available: no) output:hdmi-stereo-extra2: Digital Stereo (HDMI 3) Output (priority 5700, available: no) output:hdmi-surround-extra2: Digital Surround 5.1 (HDMI 3) Output (priority 600, available: no) output:hdmi-surround71-extra2: Digital Surround 7.1 (HDMI 3) Output (priority 600, available: no) off: Off (priority 0, available: unknown) active profile: ports: hdmi-output-0: HDMI / DisplayPort (priority 5900, latency offset 0 usec, available: no) properties: device.icon_name = "video-display" hdmi-output-1: HDMI / DisplayPort 2 (priority 5800, latency offset 0 usec, available: no) properties: device.icon_name = "video-display" hdmi-output-2: HDMI / DisplayPort 3 (priority 5700, latency offset 0 usec, available: no) properties: device.icon_name = "video-display" index: 1 name: driver: owner module: 8 properties: alsa.card = "0" alsa.card_name = "chtrt5645" alsa.long_card_name = "AMICorporation-Defaultstring-Defaultstring-CherryTrailCR" alsa.driver_name = "snd_soc_sst_cht_bsw_rt5645" device.bus_path = "platform-cht-bsw-rt5645" sysfs.path =
[Kernel-packages] [Bug 1813537] Re: Wifi + bluetooth adapters are gone after sleep/wake
Definitely support uefi capsule update. 2.10 is posted here: https://fwupd.org/lvfs/device/com.dell.uefi5ffdbc0d.firmware Are you installed in uefi mode? If so, capsule update might be turned off in bios setup. If you are installed in legacy mode you'll have to manually download exe and place in fat32 USB disk. Then go into F12 menu at POST and select bios update. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1813537 Title: Wifi + bluetooth adapters are gone after sleep/wake Status in linux package in Ubuntu: Confirmed Bug description: the only fix I found was to power down and power back on. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-44-generic 4.15.0-44.47 ProcVersionSignature: Ubuntu 4.15.0-44.47-generic 4.15.18 Uname: Linux 4.15.0-44-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: uri2238 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Jan 28 11:15:43 2019 HibernationDevice: RESUME=UUID=c88d6aec-cb91-4ff5-a406-52c6187e06a5 InstallationDate: Installed on 2018-01-13 (380 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) MachineType: Dell Inc. XPS 13 9360 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-44-generic root=UUID=dc909762-dd6b-4c9c-84da-f8e16a647a3f ro nouveau.modeset=0 quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-44-generic N/A linux-backports-modules-4.15.0-44-generic N/A linux-firmware 1.173.3 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: 0T3FTF 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.:rn0T3FTF:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS 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/1813537/+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 1824632] Re: Linux 5 regression causes no video out on some laptops in 19.04 beta
Can confirm that daily mainline 2019-04-13 fixes the issue on Dell XPS 15 2-in-1 9575. Output of uname -a Linux laptop 5.1.0-999-generic #201904122202 SMP Sat Apr 13 02:06:36 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux Basic HW info: CPU - Intel® Core™ i7-8705G CPU GPU - Intel® HD Graphics 630 (Kaby Lake GT2) / AMD® Vegam -- 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/1824632 Title: Linux 5 regression causes no video out on some laptops in 19.04 beta Status in linux package in Ubuntu: Confirmed Bug description: There is a known regression in the v5 kernel that causes laptop video to fail on some panels. I can attest this happens on a Dell XPS 15 2-in-1 (9575) and wanted to give a heads up as this affects the current 19.04 beta. Upstream tracking is here: https://bugs.freedesktop.org/show_bug.cgi?id=109959 With a patch here: https://patchwork.freedesktop.org/patch/296411/ I'm not sure what else I can include that was not already covered in those reports and tracking, but will do anything I can. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824632/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1822363] Re: Booting hangs when USB 3.0 Etron EJ168 PCI card is detected
Kai-Heng Feng pisze: > Do you mean bisection in bisection (blank screen bisection), or the > original bisection (xHC bisection)? > > For the blank screen one, the current commit is "bad". > > For the xHC one, we don't know yet. Cherry pick the fix on top of the > current commit then we can decide it's good or bad. > I found git cherry-pick command but the situation is that I have passed 2 git bisect good on "4.9-rc8" and I have no boot problem on 4.10-rc2+3 which I now is somehow corrected on 4.10-rc8 because system hangs on USB 3.0 PCI again. But 4.10-rc8 is 11 steps ahead now (4.10-rc2+3). What should I set to git cherry-pick? -- 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/1822363 Title: Booting hangs when USB 3.0 Etron EJ168 PCI card is detected Status in linux package in Ubuntu: Confirmed Bug description: I have installed Etron EJ168 PCI USB 3.0 [1B6F:7023] which briliantly works in any Windows OS (I use multiboot PC) on my Conroe865PE AGP/PCI Intel Kentsfield QX6800 system with classic BIOS (non UEFI). There are no devices connected to PCI USB card during boot. The desktop Ubuntu 18.04 kernel 4.15.0-46-generic freezes with this card during boot (see attached "photo log" with boot and grub options). I can't access/login Ubuntu or console. It was checked and confirmed on ubuntu-18.04.1-desktop-amd64.iso LIVE CD desktop (with acpi=off option too). Previously I was used and removed USB 3.0 NEC Renesas upd720200 PCI card [1033:0194], which was partially workable under my installation of Ubuntu 18.04 and Windows. It had problems from time to time with FW load from card on start and not detecting USB devices connected even if FW present. I tried and also removed USB 3.0 NEC Renesas upd720202 PCI card [1912:0015] which also was partially workable in the same way (other card bios and newer NEC chip). System was fully bootable with NEC cards. The Etron EJ168 works superb on Windows OS's with directly or with hub connections with USB devices. I can assist in any way to solve this bug as IT Professional. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822363/+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 1824632] Re: Linux 5 regression causes no video out on some laptops in 19.04 beta
It appears the patch has been merged into mainline here https://git.launchpad.net/~ubuntu-kernel-test/ubuntu/+source/linux/+git /mainline-crack/commit/?id=788f07ebe040922c89e38f609b7890ba52a09db2 It also looks like a daily has been cut for this so I’ll give that a shot -- 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/1824632 Title: Linux 5 regression causes no video out on some laptops in 19.04 beta Status in linux package in Ubuntu: Confirmed Bug description: There is a known regression in the v5 kernel that causes laptop video to fail on some panels. I can attest this happens on a Dell XPS 15 2-in-1 (9575) and wanted to give a heads up as this affects the current 19.04 beta. Upstream tracking is here: https://bugs.freedesktop.org/show_bug.cgi?id=109959 With a patch here: https://patchwork.freedesktop.org/patch/296411/ I'm not sure what else I can include that was not already covered in those reports and tracking, but will do anything I can. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824632/+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 1824662] 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/1824662 Title: package linux-image-5.0.0-11-generic 5.0.0-11.12 failed to install/upgrade: triggers looping, abandoned Status in linux package in Ubuntu: Confirmed Bug description: Upgrade to DD from 18.10 - IBM P51 48GB RAM ProblemType: Package DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-11-generic 5.0.0-11.12 ProcVersionSignature: Ubuntu 4.18.0-14.15-generic 4.18.20 Uname: Linux 4.18.0-14-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Sat Apr 13 18:58:24 2019 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2018-10-28 (167 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: LENOVO 20HH002NUS ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-14-generic root=UUID=0cce19d5-d7fe-44c8-82ca-6dfef74069bf 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.7, Python 3.7.3, python3-minimal, 3.7.3-1 PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.15-3 RelatedPackageVersions: grub-pc 2.02+dfsg1-12ubuntu2 SourcePackage: linux Title: package linux-image-5.0.0-11-generic 5.0.0-11.12 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to disco on 2019-04-13 (0 days ago) dmi.bios.date: 07/18/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N1UET71W (1.45 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HH002NUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1UET71W(1.45):bd07/18/2018:svnLENOVO:pn20HH002NUS:pvrThinkPadP51:rvnLENOVO:rn20HH002NUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P51 dmi.product.name: 20HH002NUS dmi.product.sku: LENOVO_MT_20HH_BU_Think_FM_ThinkPad P51 dmi.product.version: ThinkPad P51 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824662/+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 1824662] Re: package linux-image-5.0.0-11-generic 5.0.0-11.12 failed to install/upgrade: triggers looping, abandoned
** Tags removed: need-duplicate-check -- 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/1824662 Title: package linux-image-5.0.0-11-generic 5.0.0-11.12 failed to install/upgrade: triggers looping, abandoned Status in linux package in Ubuntu: New Bug description: Upgrade to DD from 18.10 - IBM P51 48GB RAM ProblemType: Package DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-11-generic 5.0.0-11.12 ProcVersionSignature: Ubuntu 4.18.0-14.15-generic 4.18.20 Uname: Linux 4.18.0-14-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Sat Apr 13 18:58:24 2019 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2018-10-28 (167 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: LENOVO 20HH002NUS ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-14-generic root=UUID=0cce19d5-d7fe-44c8-82ca-6dfef74069bf 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.7, Python 3.7.3, python3-minimal, 3.7.3-1 PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.15-3 RelatedPackageVersions: grub-pc 2.02+dfsg1-12ubuntu2 SourcePackage: linux Title: package linux-image-5.0.0-11-generic 5.0.0-11.12 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to disco on 2019-04-13 (0 days ago) dmi.bios.date: 07/18/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N1UET71W (1.45 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HH002NUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1UET71W(1.45):bd07/18/2018:svnLENOVO:pn20HH002NUS:pvrThinkPadP51:rvnLENOVO:rn20HH002NUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P51 dmi.product.name: 20HH002NUS dmi.product.sku: LENOVO_MT_20HH_BU_Think_FM_ThinkPad P51 dmi.product.version: ThinkPad P51 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824662/+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 1824662] [NEW] package linux-image-5.0.0-11-generic 5.0.0-11.12 failed to install/upgrade: triggers looping, abandoned
Public bug reported: Upgrade to DD from 18.10 - IBM P51 48GB RAM ProblemType: Package DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-11-generic 5.0.0-11.12 ProcVersionSignature: Ubuntu 4.18.0-14.15-generic 4.18.20 Uname: Linux 4.18.0-14-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Sat Apr 13 18:58:24 2019 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2018-10-28 (167 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: LENOVO 20HH002NUS ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-14-generic root=UUID=0cce19d5-d7fe-44c8-82ca-6dfef74069bf 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.7, Python 3.7.3, python3-minimal, 3.7.3-1 PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.15-3 RelatedPackageVersions: grub-pc 2.02+dfsg1-12ubuntu2 SourcePackage: linux Title: package linux-image-5.0.0-11-generic 5.0.0-11.12 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to disco on 2019-04-13 (0 days ago) dmi.bios.date: 07/18/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N1UET71W (1.45 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HH002NUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1UET71W(1.45):bd07/18/2018:svnLENOVO:pn20HH002NUS:pvrThinkPadP51:rvnLENOVO:rn20HH002NUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P51 dmi.product.name: 20HH002NUS dmi.product.sku: LENOVO_MT_20HH_BU_Think_FM_ThinkPad P51 dmi.product.version: ThinkPad P51 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package disco -- 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/1824662 Title: package linux-image-5.0.0-11-generic 5.0.0-11.12 failed to install/upgrade: triggers looping, abandoned Status in linux package in Ubuntu: New Bug description: Upgrade to DD from 18.10 - IBM P51 48GB RAM ProblemType: Package DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-11-generic 5.0.0-11.12 ProcVersionSignature: Ubuntu 4.18.0-14.15-generic 4.18.20 Uname: Linux 4.18.0-14-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Sat Apr 13 18:58:24 2019 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2018-10-28 (167 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: LENOVO 20HH002NUS ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-14-generic root=UUID=0cce19d5-d7fe-44c8-82ca-6dfef74069bf 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.7, Python 3.7.3, python3-minimal, 3.7.3-1 PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.15-3 RelatedPackageVersions: grub-pc 2.02+dfsg1-12ubuntu2 SourcePackage: linux Title: package linux-image-5.0.0-11-generic 5.0.0-11.12 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to disco on 2019-04-13 (0 days ago) dmi.bios.date: 07/18/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N1UET71W (1.45 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HH002NUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1UET71W(1.45):bd07/18/2018:svnLENOVO:pn20HH002NUS:pvrThinkPadP51:rvnLENOVO:rn20HH002NUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P51 dmi.product.name: 20HH002NUS dmi.product.sku: LENOVO_MT_20HH_BU_Think_FM_ThinkPad P51 dmi.product.version: ThinkPad P51 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824662/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net
[Kernel-packages] [Bug 1821641] Re: [HP Elitebook 840 G1] Screen is upside down on 19.04 daily
Absolutely, you mentioned bug 1726160 in an earlier comment and it contained a functioning workaround - removing iio-sensor-proxy. The problem seems to originate from systemd mount matrix issues on HP laptops using the lis3lv02d accelerometer, however determining the status of the github issue (and whether it applies to me) is beyond my skills. https://github.com/systemd/systemd/issues/5160 https://github.com/systemd/systemd/commit/0d1a2be93e16aa03026f1c36e81951097e8dad2c ** Bug watch added: github.com/systemd/systemd/issues #5160 https://github.com/systemd/systemd/issues/5160 -- 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/1821641 Title: [HP Elitebook 840 G1] Screen is upside down on 19.04 daily Status in linux package in Ubuntu: Confirmed Bug description: On the 19.04 daily image (2019-03-24), the screen on my laptop is completely upside down, from the moment the GUI loads. This does not happen on 18.04 and 18.10. It appears to be an accelerometer issue since holding the laptop upside down flips the image to its correct orientation - basically the functionality of the accelerometer is suddenly inverted. Please contact me if you want me to help testing the issue on my hardware. Thanks! --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sharper1380 F pulseaudio /dev/snd/controlC1: sharper1380 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-03-30 (6 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190330) MachineType: Hewlett-Packard HP EliteBook 840 G1 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=sv_SE.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-8-generic root=UUID=1e4bdc5f-0616-42f3-8da2-4ec27df3fc55 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 RelatedPackageVersions: linux-restricted-modules-5.0.0-8-generic N/A linux-backports-modules-5.0.0-8-generic N/A linux-firmware 1.178 Tags: disco Uname: Linux 5.0.0-8-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/12/2018 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: L71 Ver. 01.44 dmi.board.name: 198F dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 15.59 dmi.chassis.asset.tag: 5CG4430MGN dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrL71Ver.01.44:bd04/12/2018:svnHewlett-Packard:pnHPEliteBook840G1:pvrA3009DD10203:rvnHewlett-Packard:rn198F:rvrKBCVersion15.59:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI dmi.product.name: HP EliteBook 840 G1 dmi.product.sku: D1F44AV dmi.product.version: A3009DD10203 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821641/+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 1823029] Re: [Dell XPS 15 9575] Occasionally fails to suspend and locks up instead
linux-modules-extra package looks corrupt: (Reading database ... 367458 files and directories currently installed.) Preparing to unpack linux-modules-extra-5.0.0-11-generic_5.0.0-11.12~lp1823029_amd64.deb ... Unpacking linux-modules-extra-5.0.0-11-generic (5.0.0-11.12~lp1823029) ... dpkg-deb (subprocess): cannot copy archive member from 'linux-modules-extra-5.0.0-11-generic_5.0.0-11.12~lp1823029_amd64.deb' to decompressor pipe: unexpected end of file or stream dpkg-deb (subprocess): decompressing archive member: lzma error: unexpected end of input dpkg-deb: error: subprocess returned error exit status 2 dpkg: error processing archive linux-modules-extra-5.0.0-11-generic_5.0.0-11.12~lp1823029_amd64.deb (--install): cannot copy extracted data for './lib/modules/5.0.0-11-generic/kernel/drivers/net/wireless/marvell/mwifiex/mwifiex.ko' to '/lib/modules/5.0.0-11-generic/kernel/drivers/net/wireless/marvell/mwifiex/mwifiex.ko.dpkg-new': unexpected end of file or stream Errors were encountered while processing: linux-modules-extra-5.0.0-11-generic_5.0.0-11.12~lp1823029_amd64.deb -- 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/1823029 Title: [Dell XPS 15 9575] Occasionally fails to suspend and locks up instead Status in linux package in Ubuntu: Confirmed Bug description: Sometimes when suspending, the suspend process fails, and the machine becomes unresponsive to any input, has nothing but a black/off display, and fans kick in and run high (which is actually 'good' for detecting the issue has happened). journalctl output from an unsuccessful suspend: Apr 02 13:39:54 taplop systemd-logind[1067]: Suspending... Apr 02 13:39:54 taplop NetworkManager[4083]: [1554237594.5332] manager: sleep: sleep requested (sleeping: no en Apr 02 13:39:54 taplop NetworkManager[4083]: [1554237594.5333] device (40:4E:36:47:ED:D1): state change: disconn Apr 02 13:39:54 taplop NetworkManager[4083]: [1554237594.5358] manager: NetworkManager state is now ASLEEP Apr 02 13:39:54 taplop whoopsie[1779]: [13:39:54] offline Apr 02 13:39:55 taplop gnome-shell[5521]: Failed to flip onscreen: Tried to flip inactive CRTC Apr 02 13:39:56 taplop kernel: [drm] PCIE GART of 256M enabled (table at 0x00F4). Apr 02 13:39:56 taplop kernel: [drm] UVD and UVD ENC initialized successfully. Apr 02 13:39:56 taplop kernel: [drm] VCE initialized successfully. Apr 02 13:39:57 taplop systemd[1]: Starting TLP suspend/resume... Apr 02 13:39:57 taplop systemd[1]: Started TLP suspend/resume. Apr 02 13:39:57 taplop systemd[1]: Reached target Sleep. Apr 02 13:39:57 taplop systemd[1]: Starting Suspend... Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9078] caught SIGTERM, shutting down normally. Apr 02 13:39:57 taplop systemd[1]: Stopping Network Manager... Apr 02 13:39:57 taplop gnome-shell[5521]: Removing a network device that was not added Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9485] dhcp4 (wlp2s0): canceled DHCP transaction, DHCP c Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9486] dhcp4 (wlp2s0): state changed bound -> done Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9486] device (wlp2s0): DHCPv4: 480 seconds grace period Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9570] exiting (success) Apr 02 13:39:57 taplop gnome-shell[5521]: JS WARNING: [resource:///org/gnome/shell/ui/status/network.js 1187]: reference Apr 02 13:39:57 taplop systemd[1]: NetworkManager.service: Succeeded. Apr 02 13:39:57 taplop systemd[1]: Stopped Network Manager. Apr 02 13:39:57 taplop gnome-shell[5521]: Object NM.ActiveConnection (0x55d340e8f5a0), has been already deallocated — im Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: == Stack trace for context 0x55d34160e1e0 == Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: #0 55d345364700 i resource:///org/gnome/shell/ui/status/networ Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: #1 55d345364680 i resource:///org/gnome/shell/ui/status/networ Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: #2 7ffe97451d00 b self-hosted:979 (7fc3d4350a60 @ 440) Apr 02 13:39:58 taplop gnome-shell[5521]: Failed to flip onscreen: Tried to flip inactive CRTC Apr 02 13:39:58 taplop kernel: wlp2s0: deauthenticating from f0:9f:c2:6e:e1:aa by local choice (Reason: 3=DEAUTH_LEAVING Apr 02 13:39:58 taplop wpa_supplicant[1069]: wlp2s0: CTRL-EVENT-DISCONNECTED bssid=f0:9f:c2:6e:e1:aa reason=3 locally_ge Apr 02 13:39:58 taplop gnome-shell[5521]: Failed to flip onscreen: Tried to flip inactive CRTC Apr 02 13:39:58 taplop avahi-daemon[1068]: Interface wlp2s0.IPv6 no longer relevant for mDNS. Apr 02 13:39:58 taplop avahi-daemon[1068]: Leaving mDNS multicast group on interface wlp2s0.IPv6 with address fe80::1c45 Apr 02
[Kernel-packages] [Bug 1490713] Re: The Debian control file's "modaliases" is too generic
** Tags added: verification-needed-trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1490713 Title: The Debian control file's "modaliases" is too generic Status in bcmwl package in Ubuntu: Fix Released Status in bcmwl source package in Trusty: Fix Committed Bug description: Software-properties-gtk offers wl as the driver for all Broadcom wifi cards, regardless of whether they are supported or not. This is due to the modaliases field used by the bcmwl-kernel-source package. Although in reality I know very little about such things, I'll attach a proposed debian/bcmwl-kernel-source.modaliases file based on the info here: http://www.broadcom.com/docs/linux_sta/README_6.30.223.248.txt Users are going through needless painful procedures to get the correct working driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1490713/+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 1415880] Re: 14e4:4365 bcmwl-kernel source: fix for null pointer crash
** Tags added: verification-needed-trusty ** No longer affects: bcmwl (Ubuntu Trusty) ** Also affects: bcmwl (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: bcmwl (Ubuntu Trusty) Status: New => Fix Committed ** Changed in: bcmwl (Ubuntu Trusty) Importance: Undecided => High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1415880 Title: 14e4:4365 bcmwl-kernel source: fix for null pointer crash Status in bcmwl package in Ubuntu: Fix Released Status in bcmwl source package in Precise: Won't Fix Status in bcmwl source package in Trusty: Fix Committed Status in bcmwl source package in Vivid: Won't Fix Status in bcmwl source package in Wily: Fix Released Bug description: [Impact] * bcmwl does not compile on new kernels (or HWE kernels) * bcmwl suffers from null reference bug [Test Case] * public PPA provided to community and feedback * based on patch available to other distros * comment #42 [Regression Potential] * for changes on kernel support it may not compile (tested with 3.2, 3.13, 3.18 and 4.2) * for the null reference change -> proved to fix problem for community based on feedback [Other Info] Original bug description: The bcmwl package as of now misses one patch for a bug that occurs with BCM43142 and possibly other broadcom chipsets that will look like random disconnects, poor wifi signal and kernel warnings, See also #1379524. Adding the patch is a fairly simple process: * put the patch file in /usr/src/bcmwl-6.30.223.248+bdcom/patches * add the following line to /usr/src/bcmwl-6.30.223.248+bdcom/dkms.conf PATCH[7]="0014-null-pointer-crash.patch" * run: /usr/lib/dkms/common.postinst bcmwl 6.30.223.248+bdcom /usr/share/bcmwl x86_64 $(uname -r) This has fixed the issue for me. Edit: I just wanted to add that I did not write the patch; I merely downloaded it from a paste that was linked from the respective AUR package. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu1 [modified: usr/src/bcmwl-6.30.223.248+bdcom/dkms.conf] ProcVersionSignature: Ubuntu 3.16.0-29.39-generic 3.16.7-ckt2 Uname: Linux 3.16.0-29-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.7-0ubuntu8.1 Architecture: amd64 CurrentDesktop: LXDE Date: Thu Jan 29 13:15:17 2015 InstallationDate: Installed on 2015-01-26 (3 days ago) InstallationMedia: Lubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) SourcePackage: bcmwl UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1415880/+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 1491070] Re: On removal the package should warn a reboot is needed
** Tags added: verification-needed-trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1491070 Title: On removal the package should warn a reboot is needed Status in bcmwl package in Ubuntu: Fix Released Status in bcmwl source package in Trusty: Fix Committed Bug description: When the bcmwl-kernel-source package is removed it should communicate that a reboot is needed. This will be picked up by software- properties-gtk and be communicated to the user. Attached is a patch. This will help with this bug https://bugs.launchpad.net/ubuntu/+source/b43-fwcutter/+bug/1490212 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1491070/+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 1424676] Re: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu2: bcmwl kernel module failed to build with kernel 4.0 [error: ‘STATION_INFO_TX_BITRATE’ undeclared (first use in this
** No longer affects: bcmwl (Ubuntu Trusty) ** Also affects: bcmwl (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: bcmwl (Ubuntu Trusty) Status: New => Fix Committed ** Changed in: bcmwl (Ubuntu Trusty) Importance: Undecided => High ** Tags added: verification-needed-trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1424676 Title: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu2: bcmwl kernel module failed to build with kernel 4.0 [error: ‘STATION_INFO_TX_BITRATE’ undeclared (first use in this function)] Status in bcmwl package in Ubuntu: Fix Released Status in bcmwl source package in Precise: Won't Fix Status in bcmwl source package in Trusty: Fix Committed Status in bcmwl source package in Vivid: Won't Fix Bug description: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu2: bcmwl kernel module failed to build ProblemType: Package DistroRelease: Ubuntu 15.04 Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu2 ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5 Uname: Linux 3.18.0-13-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.16.1-0ubuntu2 Architecture: amd64 DKMSKernelVersion: 4.0.0-04rc1-generic Date: Mon Feb 23 18:14:07 2015 DuplicateSignature: dkms:bcmwl-kernel-source:6.30.223.248+bdcom-0ubuntu2:/var/lib/dkms/bcmwl/6.30.223.248+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:1444:20: error: ‘STATION_INFO_TX_BITRATE’ undeclared (first use in this function) InstallationDate: Installed on 2014-11-22 (93 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20141121) PackageVersion: 6.30.223.248+bdcom-0ubuntu2 SourcePackage: bcmwl Title: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu2: bcmwl kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1424676/+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 1342645] Re: upgrade bcmwl-kernel-source to 6.30.223.248
** Tags added: verification-needed-trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1342645 Title: upgrade bcmwl-kernel-source to 6.30.223.248 Status in bcmwl package in Ubuntu: Fix Released Status in bcmwl source package in Trusty: Fix Committed Bug description: The latest version from broadcom is 6.30.223.248 http://www.broadcom.com/support/802.11/linux_sta.php Release notes: WHAT'S NEW IN RELEASE 6.30.223.23X - + Upgraded to Support 3.11 kernels + Added cfg80211 wowlan support for Magic Packets and Disconnect WHAT'S NEW IN RELEASE 6.30.223.126 -- + Upgraded to Support 3.8.x + Added 43142 support + Added 4352 support + Dropped WEXT support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1342645/+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 1173761] Re: 14e4:43b1 Broadcom Corporation Device 43b1 (rev 03) - not supported
** Tags added: verification-needed-trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1173761 Title: 14e4:43b1 Broadcom Corporation Device 43b1 (rev 03) - not supported Status in bcmwl package in Ubuntu: Fix Released Status in bcmwl source package in Trusty: Fix Committed Bug description: Both during and after installation, 13.04 doesn't support the Broadcom-based 802.11ac wifi chipsets. lspci reports it as "Network controller: Broadcom Corporation Device 43b1 (rev 03)". WORKAROUND: 6_30_223_95 driver in http://people.canonical.com/~ypwong/drivers/broadcom/ , install an old version: https://launchpad.net/ubuntu/saucy/amd64/bcmwl-kernel- source/6.30.223.30+bdcom-0ubuntu3 (found at http://gaspuu.blogspot.no/2014/05/dell-precision-m4800-with-ubuntu- linux.html), or simply replace the wifi module with another one with better driver support (if laptop has no whitelist for modules). --- ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 DistroRelease: Ubuntu 13.04 EcryptfsInUse: Yes InstallationDate: Installed on 2013-04-27 (0 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True NonfreeKernelModules: nvidia Package: linux (not installed) Tags: raring Uname: Linux 3.9.0-030900rc8-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 --- ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: atrauzzi 2141 F pulseaudio /dev/snd/controlC0: atrauzzi 2141 F pulseaudio CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CurrentDmesg: [ 176.287266] atl1c :04:00.0: vpd r/w failed. This is likely a firmware bug on this device. Contact the card vendor for a firmware update. DistroRelease: Ubuntu 13.04 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=90e84f80-b3fc-4480-b4cd-21d15e3abc6d InstallationDate: Installed on 2013-04-27 (0 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: ASUSTeK COMPUTER INC. G75VX MarkForUpload: True NonfreeKernelModules: nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-19-generic root=UUID=b0911040-5a49-4581-9a7a-bac9d830a0ba ro nomodeset quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 RelatedPackageVersions: linux-restricted-modules-3.8.0-19-generic N/A linux-backports-modules-3.8.0-19-generic N/A linux-firmware1.106 StagingDrivers: r8712u Tags: raring staging Uname: Linux 3.8.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 10/23/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: G75VX.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G75VX 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.:bvrG75VX.203:bd10/23/2012:svnASUSTeKCOMPUTERINC.:pnG75VX:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG75VX:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: G75VX dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1173761/+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 1358966] Re: Broadcom kernel module failed to build [error: macro "alloc_netdev" requires 4 arguments, but only 3 given]
** Tags added: verification-needed-trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1358966 Title: Broadcom kernel module failed to build [error: macro "alloc_netdev" requires 4 arguments, but only 3 given] Status in bcmwl package in Ubuntu: Fix Released Status in bcmwl source package in Trusty: Fix Committed Bug description: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu1 will not build with linux-3.17-rc1 from Ubuntu kernel ppa (Mainline). Tried custom kernel as well from kernel archives 3.17-rc1. APPORT ERROR ProblemType: Package DistroRelease: Ubuntu 14.10 Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu1 Uname: Linux 3.16.1-custom x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 2.14.6-0ubuntu1 Architecture: amd64 DKMSKernelVersion: 3.17.0-031700rc1-generic Date: Tue Aug 19 19:42:02 2014 DuplicateSignature: dkms:bcmwl-kernel-source:6.30.223.248+bdcom-0ubuntu1:/var/lib/dkms/bcmwl/6.30.223.248+bdcom/build/src/wl/sys/wl_linux.c:1316:64: error: macro "alloc_netdev" requires 4 arguments, but only 3 given InstallationDate: Installed on 2014-07-05 (45 days ago) InstallationMedia: Ubuntu "Utopic" - Build amd64 LIVE Binary 20140703-15:52 PackageVersion: 6.30.223.248+bdcom-0ubuntu1 SourcePackage: bcmwl Title: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu1: bcmwl kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1358966/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1776563]
I don't need to map ivrs to boot 5.1 successfully 100% times. Seems like you need to have secure boot disabled (i did it like last summer) and iommu ENABLED (my laptop comes with it disabled cuz i only have 1 gpu integrated in CPU). Please confirm that 5.1 boots for you without any tricks without any issues -- 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/1776563 Title: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash Status in amd: Fix Released Status in Linux: Incomplete Status in linux package in Ubuntu: Triaged Bug description: CPU: Ryzen 5 2500U VGA: Radeon 535 Notebook: Acer Aspire A315 This is a brand new notebook on the market with Ryzen 5/Radeon. The default kernel of Ubuntu(18.04) hangs at loading with message: tsc: Refined TSC clocksource calibration: 1996.250 MHz clocksource: tsc: mask: 0x max_cycles: (...), max_idle_ns: (...) Soft lockup Using pci=noacpi kernel parameter kernel loads without any problem but my notebook produces more heat than on Win10. If I know right Acer notebooks need ACPI to the correct power management. The same thing happens on mainline 4.17,4.18rc1-2. BIOS upgrade to the latest version: 1.08 hasn't helped This problem has been reported upstream: https://bugzilla.kernel.org/show_bug.cgi?id=200087 The latest correctly working kernel was 4.13.* but the heat problem was present with this too. To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1776563/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1690085]
Created attachment 282319 Threadripper 2920x soft lockup I've went through this thread, and tried to disable c6 state, add idle=halt with no effect. Followed this excellent reprod steps in https://www.reddit.com/r/Amd/comments/apw8im/ryzen_freezes_in_linux_even_if_linux_is_in_vm/ It is pretty consistent. However, switching to gcc-8 seems resolved this for this particular reprod steps. With dmesg -w, I was able to capture and verify this is indeed a soft lockup. Attached the dmesg output. It is a Threadripper 2920x with MSI x399 Gaming Pro Carbon AC with latest BIOS on Ubuntu 18.04.2 LTS. Linux sz77 4.15.0-47-generic #50-Ubuntu SMP Wed Mar 13 10:44:52 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/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-041100-generic #201705041534 this morning and waiting for crash... For now, the machine is not "used", at least, it's not CPU stressed... Thanks --- ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 DistroRelease: Ubuntu 17.04 InstallationDate: Installed on
[Kernel-packages] [Bug 1776563]
i can boot latest 5.0 with no parameters in manjaro, i bet i can boot 5.1 just as well,i am not willing to download and try an in-development kernel right 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/1776563 Title: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash Status in amd: Fix Released Status in Linux: Incomplete Status in linux package in Ubuntu: Triaged Bug description: CPU: Ryzen 5 2500U VGA: Radeon 535 Notebook: Acer Aspire A315 This is a brand new notebook on the market with Ryzen 5/Radeon. The default kernel of Ubuntu(18.04) hangs at loading with message: tsc: Refined TSC clocksource calibration: 1996.250 MHz clocksource: tsc: mask: 0x max_cycles: (...), max_idle_ns: (...) Soft lockup Using pci=noacpi kernel parameter kernel loads without any problem but my notebook produces more heat than on Win10. If I know right Acer notebooks need ACPI to the correct power management. The same thing happens on mainline 4.17,4.18rc1-2. BIOS upgrade to the latest version: 1.08 hasn't helped This problem has been reported upstream: https://bugzilla.kernel.org/show_bug.cgi?id=200087 The latest correctly working kernel was 4.13.* but the heat problem was present with this too. To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1776563/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1776563]
you see you shouldnt panick right away, secure boot also causes suspend\hibernation issues for me so if you have further problems disable that too. -- 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/1776563 Title: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash Status in amd: Fix Released Status in Linux: Incomplete Status in linux package in Ubuntu: Triaged Bug description: CPU: Ryzen 5 2500U VGA: Radeon 535 Notebook: Acer Aspire A315 This is a brand new notebook on the market with Ryzen 5/Radeon. The default kernel of Ubuntu(18.04) hangs at loading with message: tsc: Refined TSC clocksource calibration: 1996.250 MHz clocksource: tsc: mask: 0x max_cycles: (...), max_idle_ns: (...) Soft lockup Using pci=noacpi kernel parameter kernel loads without any problem but my notebook produces more heat than on Win10. If I know right Acer notebooks need ACPI to the correct power management. The same thing happens on mainline 4.17,4.18rc1-2. BIOS upgrade to the latest version: 1.08 hasn't helped This problem has been reported upstream: https://bugzilla.kernel.org/show_bug.cgi?id=200087 The latest correctly working kernel was 4.13.* but the heat problem was present with this too. To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1776563/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1776563]
Could there be that my ivrs_table values differs from others? How to check that 00:14.0 and 00:00.2 are good for me? -- 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/1776563 Title: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash Status in amd: Fix Released Status in Linux: Incomplete Status in linux package in Ubuntu: Triaged Bug description: CPU: Ryzen 5 2500U VGA: Radeon 535 Notebook: Acer Aspire A315 This is a brand new notebook on the market with Ryzen 5/Radeon. The default kernel of Ubuntu(18.04) hangs at loading with message: tsc: Refined TSC clocksource calibration: 1996.250 MHz clocksource: tsc: mask: 0x max_cycles: (...), max_idle_ns: (...) Soft lockup Using pci=noacpi kernel parameter kernel loads without any problem but my notebook produces more heat than on Win10. If I know right Acer notebooks need ACPI to the correct power management. The same thing happens on mainline 4.17,4.18rc1-2. BIOS upgrade to the latest version: 1.08 hasn't helped This problem has been reported upstream: https://bugzilla.kernel.org/show_bug.cgi?id=200087 The latest correctly working kernel was 4.13.* but the heat problem was present with this too. To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1776563/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1776563]
you need to get and see an iommu dump, but i dont think that's the issue just disable secure boot and your fine -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1776563 Title: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash Status in amd: Fix Released Status in Linux: Incomplete Status in linux package in Ubuntu: Triaged Bug description: CPU: Ryzen 5 2500U VGA: Radeon 535 Notebook: Acer Aspire A315 This is a brand new notebook on the market with Ryzen 5/Radeon. The default kernel of Ubuntu(18.04) hangs at loading with message: tsc: Refined TSC clocksource calibration: 1996.250 MHz clocksource: tsc: mask: 0x max_cycles: (...), max_idle_ns: (...) Soft lockup Using pci=noacpi kernel parameter kernel loads without any problem but my notebook produces more heat than on Win10. If I know right Acer notebooks need ACPI to the correct power management. The same thing happens on mainline 4.17,4.18rc1-2. BIOS upgrade to the latest version: 1.08 hasn't helped This problem has been reported upstream: https://bugzilla.kernel.org/show_bug.cgi?id=200087 The latest correctly working kernel was 4.13.* but the heat problem was present with this too. To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1776563/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1776563]
also why do you not remap the ivrs tables? there is no drawback in doing 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/1776563 Title: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash Status in amd: Fix Released Status in Linux: Incomplete Status in linux package in Ubuntu: Triaged Bug description: CPU: Ryzen 5 2500U VGA: Radeon 535 Notebook: Acer Aspire A315 This is a brand new notebook on the market with Ryzen 5/Radeon. The default kernel of Ubuntu(18.04) hangs at loading with message: tsc: Refined TSC clocksource calibration: 1996.250 MHz clocksource: tsc: mask: 0x max_cycles: (...), max_idle_ns: (...) Soft lockup Using pci=noacpi kernel parameter kernel loads without any problem but my notebook produces more heat than on Win10. If I know right Acer notebooks need ACPI to the correct power management. The same thing happens on mainline 4.17,4.18rc1-2. BIOS upgrade to the latest version: 1.08 hasn't helped This problem has been reported upstream: https://bugzilla.kernel.org/show_bug.cgi?id=200087 The latest correctly working kernel was 4.13.* but the heat problem was present with this too. To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1776563/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1776563]
Turns out my iommu was disabled in bios. I turned it on and ivrs mapping fixes all the issues for me. -- 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/1776563 Title: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash Status in amd: Fix Released Status in Linux: Incomplete Status in linux package in Ubuntu: Triaged Bug description: CPU: Ryzen 5 2500U VGA: Radeon 535 Notebook: Acer Aspire A315 This is a brand new notebook on the market with Ryzen 5/Radeon. The default kernel of Ubuntu(18.04) hangs at loading with message: tsc: Refined TSC clocksource calibration: 1996.250 MHz clocksource: tsc: mask: 0x max_cycles: (...), max_idle_ns: (...) Soft lockup Using pci=noacpi kernel parameter kernel loads without any problem but my notebook produces more heat than on Win10. If I know right Acer notebooks need ACPI to the correct power management. The same thing happens on mainline 4.17,4.18rc1-2. BIOS upgrade to the latest version: 1.08 hasn't helped This problem has been reported upstream: https://bugzilla.kernel.org/show_bug.cgi?id=200087 The latest correctly working kernel was 4.13.* but the heat problem was present with this too. To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1776563/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1776563]
When i remap ivrs then my sleep\hibernation doesn't work. -- 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/1776563 Title: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash Status in amd: Fix Released Status in Linux: Incomplete Status in linux package in Ubuntu: Triaged Bug description: CPU: Ryzen 5 2500U VGA: Radeon 535 Notebook: Acer Aspire A315 This is a brand new notebook on the market with Ryzen 5/Radeon. The default kernel of Ubuntu(18.04) hangs at loading with message: tsc: Refined TSC clocksource calibration: 1996.250 MHz clocksource: tsc: mask: 0x max_cycles: (...), max_idle_ns: (...) Soft lockup Using pci=noacpi kernel parameter kernel loads without any problem but my notebook produces more heat than on Win10. If I know right Acer notebooks need ACPI to the correct power management. The same thing happens on mainline 4.17,4.18rc1-2. BIOS upgrade to the latest version: 1.08 hasn't helped This problem has been reported upstream: https://bugzilla.kernel.org/show_bug.cgi?id=200087 The latest correctly working kernel was 4.13.* but the heat problem was present with this too. To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1776563/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1776563]
remap the tables and disable secure boot and suspend\hibernate will work on any linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1776563 Title: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash Status in amd: Fix Released Status in Linux: Incomplete Status in linux package in Ubuntu: Triaged Bug description: CPU: Ryzen 5 2500U VGA: Radeon 535 Notebook: Acer Aspire A315 This is a brand new notebook on the market with Ryzen 5/Radeon. The default kernel of Ubuntu(18.04) hangs at loading with message: tsc: Refined TSC clocksource calibration: 1996.250 MHz clocksource: tsc: mask: 0x max_cycles: (...), max_idle_ns: (...) Soft lockup Using pci=noacpi kernel parameter kernel loads without any problem but my notebook produces more heat than on Win10. If I know right Acer notebooks need ACPI to the correct power management. The same thing happens on mainline 4.17,4.18rc1-2. BIOS upgrade to the latest version: 1.08 hasn't helped This problem has been reported upstream: https://bugzilla.kernel.org/show_bug.cgi?id=200087 The latest correctly working kernel was 4.13.* but the heat problem was present with this too. To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1776563/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1776563]
[petrovich@aspire-a315-41g ~]$ cat /proc/cpuinfo | grep MHz cpu MHz : 2994.548 cpu MHz : 2994.549 cpu MHz : 2994.347 cpu MHz : 2994.346 cpu MHz : 2994.540 cpu MHz : 2994.543 cpu MHz : 2994.400 cpu MHz : 2994.400 Kernel 5.1-rc4 (archlinuxcn) fails to boot 3 times out of 4, but CPU boost is OK. CMDline same as in last my message. AFAIK AMD already merged their fixes for ACPI in RC4 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1776563 Title: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash Status in amd: Fix Released Status in Linux: Incomplete Status in linux package in Ubuntu: Triaged Bug description: CPU: Ryzen 5 2500U VGA: Radeon 535 Notebook: Acer Aspire A315 This is a brand new notebook on the market with Ryzen 5/Radeon. The default kernel of Ubuntu(18.04) hangs at loading with message: tsc: Refined TSC clocksource calibration: 1996.250 MHz clocksource: tsc: mask: 0x max_cycles: (...), max_idle_ns: (...) Soft lockup Using pci=noacpi kernel parameter kernel loads without any problem but my notebook produces more heat than on Win10. If I know right Acer notebooks need ACPI to the correct power management. The same thing happens on mainline 4.17,4.18rc1-2. BIOS upgrade to the latest version: 1.08 hasn't helped This problem has been reported upstream: https://bugzilla.kernel.org/show_bug.cgi?id=200087 The latest correctly working kernel was 4.13.* but the heat problem was present with this too. To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1776563/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1824650] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1824650 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1824650 Title: Ubuntu freezes when AC 430 WiFi Dongle is plugged in Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu crashes after a short time after plugging in the WiFi stick "AC430". The kernel fails to load the driver and the following message appears repeatedly: [ 800.177462] mt76x0u 1-1.1.3.2:1.0: rx urb failed: -32 [ 800.177711] mt76x0u 1-1.1.3.2:1.0: rx urb failed: -32 [ 800.177961] mt76x0u 1-1.1.3.2:1.0: rx urb failed: -32 [ 800.178211] mt76x0u 1-1.1.3.2:1.0: rx urb failed: -32 [ 800.178461] mt76x0u 1-1.1.3.2:1.0: rx urb failed: -32 [ 800.178712] mt76x0u 1-1.1.3.2:1.0: rx urb failed: -32 [ 800.181962] mt76x0u 1-1.1.3.2:1.0: rx urb failed: -32 ... Tested with Kernel 4.19 and 5.0 (5.0.2) Tested with the following distributions: Ubuntu Cosmic Cuttlefish 18.10 Ubuntu Studio 18.10 Ubuntu Disco Dingo 19.04 40-usb_modeswitch.rules was already modified to load the driver, otherwise the system chooses Driver=option. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824650/+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 1824650] [NEW] Ubuntu freezes when AC 430 WiFi Dongle is plugged in
Public bug reported: Ubuntu crashes after a short time after plugging in the WiFi stick "AC430". The kernel fails to load the driver and the following message appears repeatedly: [ 800.177462] mt76x0u 1-1.1.3.2:1.0: rx urb failed: -32 [ 800.177711] mt76x0u 1-1.1.3.2:1.0: rx urb failed: -32 [ 800.177961] mt76x0u 1-1.1.3.2:1.0: rx urb failed: -32 [ 800.178211] mt76x0u 1-1.1.3.2:1.0: rx urb failed: -32 [ 800.178461] mt76x0u 1-1.1.3.2:1.0: rx urb failed: -32 [ 800.178712] mt76x0u 1-1.1.3.2:1.0: rx urb failed: -32 [ 800.181962] mt76x0u 1-1.1.3.2:1.0: rx urb failed: -32 ... Tested with Kernel 4.19 and 5.0 (5.0.2) Tested with the following distributions: Ubuntu Cosmic Cuttlefish 18.10 Ubuntu Studio 18.10 Ubuntu Disco Dingo 19.04 40-usb_modeswitch.rules was already modified to load the driver, otherwise the system chooses Driver=option. ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1824650 Title: Ubuntu freezes when AC 430 WiFi Dongle is plugged in Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu crashes after a short time after plugging in the WiFi stick "AC430". The kernel fails to load the driver and the following message appears repeatedly: [ 800.177462] mt76x0u 1-1.1.3.2:1.0: rx urb failed: -32 [ 800.177711] mt76x0u 1-1.1.3.2:1.0: rx urb failed: -32 [ 800.177961] mt76x0u 1-1.1.3.2:1.0: rx urb failed: -32 [ 800.178211] mt76x0u 1-1.1.3.2:1.0: rx urb failed: -32 [ 800.178461] mt76x0u 1-1.1.3.2:1.0: rx urb failed: -32 [ 800.178712] mt76x0u 1-1.1.3.2:1.0: rx urb failed: -32 [ 800.181962] mt76x0u 1-1.1.3.2:1.0: rx urb failed: -32 ... Tested with Kernel 4.19 and 5.0 (5.0.2) Tested with the following distributions: Ubuntu Cosmic Cuttlefish 18.10 Ubuntu Studio 18.10 Ubuntu Disco Dingo 19.04 40-usb_modeswitch.rules was already modified to load the driver, otherwise the system chooses Driver=option. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824650/+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 1824648] 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/1824648 Title: black screen after upgrade to kernel 4.15.0-47 Status in linux package in Ubuntu: Confirmed Bug description: I install Xubuntu 18.04.2 in kvm(debian 9.8 host), and upgrade to latest 4.15.0-47 kernel recently. I get a black screen after grub boot menu. I had tried to downgrade to 4.15.0-46 kernel, and it's also black screen, but it's ok after downgrade to 4.15.0-45 kernel. Finally, I find I only get black screen after start with 4.15.0-47 kernel(or 4.15.0-46 kernel) if I set my VM display to spice/qxl. My Xubuntu VM can boot normally if I set display to spice/vmvga or any other options. Any help would be appreciated. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-47-generic 4.15.0-47.50 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tony 1096 F pulseaudio CurrentDesktop: XFCE Date: Sun Apr 14 03:05:38 2019 InstallationDate: Installed on 2018-12-24 (110 days ago) InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IwConfig: ens3 no wireless extensions. lono wireless extensions. Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) ProcFB: 0 qxldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic root=UUID=5b6b407c-d00b-4e08-9921-ce2e5612555c ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-45-generic N/A linux-backports-modules-4.15.0-45-generic N/A linux-firmware 1.173.3 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.10.2-1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-2.8 dmi.modalias: dmi:bvnSeaBIOS:bvr1.10.2-1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.8:cvnQEMU:ct1:cvrpc-i440fx-2.8: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-2.8 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824648/+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 1778844] Re: nvme multipath does not report path relationships
** No longer affects: linux (Ubuntu) ** No longer affects: linux (Ubuntu Bionic) ** No longer affects: linux (Ubuntu Cosmic) ** No longer affects: linux (Ubuntu Disco) -- 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/1778844 Title: nvme multipath does not report path relationships Status in The Ubuntu-power-systems project: In Progress Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Bionic: In Progress Status in initramfs-tools source package in Cosmic: In Progress Status in initramfs-tools source package in Disco: Fix Released Bug description: [Impact] initramfs created with MODULES=dep or kdump initrd won't boot a system with root filesystem on a multipath nvme. [Test case] Systems with nvme multipath were able to boot with the created initramfs. Also tested on systems with non-multipath nvme, and non nvme systems. [Regression potential] A system could fail to boot because the generated initramfs was broken. The code should just add modules, which is safer than removing modules or doing any other changes. In any case, it was tested to boot on multipath nvme, non multipath nvme and non nvme systems. - Problem Description: === After triggering crash ,kdump is not working & system enters into initramfs state Steps to re-create: == >. woo is installed ubuntu180401 kernel root@woo:~# uname -a Linux woo 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 17:59:00 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux root@woo:~# >. Crashkernel value as below root@woo:~# free -h totalusedfree shared buff/cache available Mem: 503G2.0G501G 13M279M 499G Swap: 2.0G 0B2.0G root@woo:~# cat /proc/cmdline root=UUID=45bb7eb2-4c61-425d-8bf9-4e6f16829ddb ro splash quiet crashkernel=8192M > kdump status root@woo:~# kdump-config status current state : ready to kdump root@woo:~# kdump-config show DUMP_MODE:kdump USE_KDUMP:1 KDUMP_SYSCTL: kernel.panic_on_oops=1 KDUMP_COREDIR:/var/crash crashkernel addr: /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.15.0-23-generic kdump initrd: /var/lib/kdump/initrd.img: symbolic link to /var/lib/kdump/initrd.img-4.15.0-23-generic current state:ready to kdump kexec command: /sbin/kexec -p --command-line="root=UUID=45bb7eb2-4c61-425d-8bf9-4e6f16829ddb ro splash quiet nr_cpus=1 systemd.unit=kdump-tools.service irqpoll noirqdistrib nousb" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz root@woo:~# dmesg | grep Reser [0.00] Reserving 8192MB of memory at 128MB for crashkernel (System RAM: 524288MB) [0.00] cma: Reserved 26224 MiB at 0x20399500 [3.545490] Copyright (C) 2017-2018 Broadcom. All Rights Reserved. The term "Broadcom" refers to Broadcom Limited and/or its subsidiaries. > Triggered crash root@woo:~# echo 1 > /proc/sys/kernel/sysrq root@woo:~# echo c > /proc/sysrq-trigger [ 73.056308] sysrq: SysRq : Trigger a crash [ 73.056357] Unable to handle kernel paging request for data at address 0x [ 73.056459] Faulting instruction address: 0xc07f24c8 [ 73.056543] Oops: Kernel access of bad area, sig: 11 [#1] [ 73.056609] LE SMP NR_CPUS=2048 NUMA PowerNV [ 73.056668] Modules linked in: rdma_ucm(OE) ib_ucm(OE) rdma_cm(OE) iw_cm(OE) ib_ipoib(OE) ib_cm(OE) ib_uverbs(OE) ib_umad(OE) esp6_offload esp6 esp4_offload esp4 xfrm_algo mlx5_fpga_tools(OE) mlx4_en(OE) mlx4_ib(OE) mlx4_core(OE) rpcsec_gss_krb5 nfsv4 nfs fscache binfmt_misc idt_89hpesx vmx_crypto crct10dif_vpmsum ofpart cmdlinepart ipmi_powernv ipmi_devintf at24 powernv_flash ipmi_msghandler ibmpowernv mtd opal_prd uio_pdrv_genirq uio nfsd auth_rpcgss nfs_acl lockd sch_fq_codel grace sunrpc knem(OE) ip_tables x_tables autofs4 btrfs xor zstd_compress raid6_pq mlx5_ib(OE) ib_core(OE) nouveau lpfc ast i2c_algo_bit ttm mlx5_core(OE) drm_kms_helper mlxfw(OE) nvmet_fc devlink syscopyarea nvmet mlx_compat(OE) sysfillrect cxl nvme_fc sysimgblt fb_sys_fops nvme_fabrics nvme ahci crc32c_vpmsum drm scsi_transport_fc [ 73.057601] tg3 libahci nvme_core pnv_php [ 73.057652] CPU: 44 PID: 4626 Comm: bash Tainted: G OE 4.15.0-23-generic #25-Ubuntu [ 73.057767] NIP: c07f24c8 LR: c07f3568 CTR: c07f24a0 [ 73.057868] REGS: c03f8269f9f0 TRAP: 0300 Tainted: G OE (4.15.0-23-generic) [ 73.057986] MSR: 90009033 CR: 2822 XER: 2004 [ 73.058099] CFAR: c07f3564 DAR: DSISR: 4200 SOFTE: 1 [ 73.058099] GPR00: c07f3568 c03f8269fc70 c16eaf00
[Kernel-packages] [Bug 1824648] [NEW] black screen after upgrade to kernel 4.15.0-47
Public bug reported: I install Xubuntu 18.04.2 in kvm(debian 9.8 host), and upgrade to latest 4.15.0-47 kernel recently. I get a black screen after grub boot menu. I had tried to downgrade to 4.15.0-46 kernel, and it's also black screen, but it's ok after downgrade to 4.15.0-45 kernel. Finally, I find I only get black screen after start with 4.15.0-47 kernel(or 4.15.0-46 kernel) if I set my VM display to spice/qxl. My Xubuntu VM can boot normally if I set display to spice/vmvga or any other options. Any help would be appreciated. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-47-generic 4.15.0-47.50 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tony 1096 F pulseaudio CurrentDesktop: XFCE Date: Sun Apr 14 03:05:38 2019 InstallationDate: Installed on 2018-12-24 (110 days ago) InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IwConfig: ens3 no wireless extensions. lono wireless extensions. Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) ProcFB: 0 qxldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic root=UUID=5b6b407c-d00b-4e08-9921-ce2e5612555c ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-45-generic N/A linux-backports-modules-4.15.0-45-generic N/A linux-firmware 1.173.3 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.10.2-1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-2.8 dmi.modalias: dmi:bvnSeaBIOS:bvr1.10.2-1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.8:cvnQEMU:ct1:cvrpc-i440fx-2.8: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-2.8 dmi.sys.vendor: QEMU ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug 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/1824648 Title: black screen after upgrade to kernel 4.15.0-47 Status in linux package in Ubuntu: Confirmed Bug description: I install Xubuntu 18.04.2 in kvm(debian 9.8 host), and upgrade to latest 4.15.0-47 kernel recently. I get a black screen after grub boot menu. I had tried to downgrade to 4.15.0-46 kernel, and it's also black screen, but it's ok after downgrade to 4.15.0-45 kernel. Finally, I find I only get black screen after start with 4.15.0-47 kernel(or 4.15.0-46 kernel) if I set my VM display to spice/qxl. My Xubuntu VM can boot normally if I set display to spice/vmvga or any other options. Any help would be appreciated. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-47-generic 4.15.0-47.50 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tony 1096 F pulseaudio CurrentDesktop: XFCE Date: Sun Apr 14 03:05:38 2019 InstallationDate: Installed on 2018-12-24 (110 days ago) InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IwConfig: ens3 no wireless extensions. lono wireless extensions. Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) ProcFB: 0 qxldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic root=UUID=5b6b407c-d00b-4e08-9921-ce2e5612555c ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-45-generic N/A linux-backports-modules-4.15.0-45-generic N/A linux-firmware 1.173.3 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.10.2-1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-2.8
[Kernel-packages] [Bug 1824259] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1824259/+attachment/5255462/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1824259 Title: Headphone jack switch sense is inverted: plugging in headphones disables headphone output Status in linux package in Ubuntu: Confirmed Bug description: My machine is a LattePanda board, which uses a "chtrt5645" device as a sound card. It has a single headphone output jack, which I think is a TRRS jack, with a mic input, such as is normally used on phones. When I don't have headphones plugged in, the system thinks headphones *are* plugged in. Gnome Control Center shows my audio device as being headphones. If I insert a headphone connector partway into the jack, I can even get sound in the headphones. But if I plug the headphones all the way in, the system decided that I have *un*plugged the headphones, and switches output over to "Speaker". The system doesn't actually have a speaker, only a headphone jack. And when the system switches over to "Speaker", I get no sound out of the headphones, even if I open "pavucontrol" and swap over to "Headphones (unplugged)" on the "Output Devices" tab. This is what "pacmd"'s "list-cards" command says with my headphones *unplugged*: 2 card(s) available. index: 0 name: driver: owner module: 7 properties: alsa.card = "1" alsa.card_name = "Intel HDMI/DP LPE Audio" alsa.long_card_name = "Intel HDMI/DP LPE Audio" alsa.driver_name = "snd_hdmi_lpe_audio" device.bus_path = "pci-:00:02.0-platform-hdmi-lpe-audio" sysfs.path = "/devices/pci:00/:00:02.0/hdmi-lpe-audio/sound/card1" device.bus = "pci" device.vendor.id = "8086" device.vendor.name = "Intel Corporation" device.product.id = "22b0" device.product.name = "Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers" device.string = "1" device.description = "Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers" module-udev-detect.discovered = "1" device.icon_name = "audio-card-pci" profiles: output:hdmi-stereo: Digital Stereo (HDMI) Output (priority 5900, available: no) output:hdmi-surround: Digital Surround 5.1 (HDMI) Output (priority 800, available: no) output:hdmi-surround71: Digital Surround 7.1 (HDMI) Output (priority 800, available: no) output:hdmi-stereo-extra1: Digital Stereo (HDMI 2) Output (priority 5700, available: no) output:hdmi-surround-extra1: Digital Surround 5.1 (HDMI 2) Output (priority 600, available: no) output:hdmi-surround71-extra1: Digital Surround 7.1 (HDMI 2) Output (priority 600, available: no) output:hdmi-stereo-extra2: Digital Stereo (HDMI 3) Output (priority 5700, available: no) output:hdmi-surround-extra2: Digital Surround 5.1 (HDMI 3) Output (priority 600, available: no) output:hdmi-surround71-extra2: Digital Surround 7.1 (HDMI 3) Output (priority 600, available: no) off: Off (priority 0, available: unknown) active profile: ports: hdmi-output-0: HDMI / DisplayPort (priority 5900, latency offset 0 usec, available: no) properties: device.icon_name = "video-display" hdmi-output-1: HDMI / DisplayPort 2 (priority 5800, latency offset 0 usec, available: no) properties: device.icon_name = "video-display" hdmi-output-2: HDMI / DisplayPort 3 (priority 5700, latency offset 0 usec, available: no) properties: device.icon_name = "video-display" index: 1 name: driver: owner module: 8 properties: alsa.card = "0" alsa.card_name = "chtrt5645" alsa.long_card_name = "AMICorporation-Defaultstring-Defaultstring-CherryTrailCR" alsa.driver_name = "snd_soc_sst_cht_bsw_rt5645" device.bus_path = "platform-cht-bsw-rt5645" sysfs.path = "/devices/pci:00/808622A8:00/cht-bsw-rt5645/sound/card0" device.form_factor = "internal" device.string = "0" device.description = "Built-in Audio" module-udev-detect.discovered = "1" device.icon_name = "audio-card" profiles:
[Kernel-packages] [Bug 1824259] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1824259/+attachment/5255463/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1824259 Title: Headphone jack switch sense is inverted: plugging in headphones disables headphone output Status in linux package in Ubuntu: Confirmed Bug description: My machine is a LattePanda board, which uses a "chtrt5645" device as a sound card. It has a single headphone output jack, which I think is a TRRS jack, with a mic input, such as is normally used on phones. When I don't have headphones plugged in, the system thinks headphones *are* plugged in. Gnome Control Center shows my audio device as being headphones. If I insert a headphone connector partway into the jack, I can even get sound in the headphones. But if I plug the headphones all the way in, the system decided that I have *un*plugged the headphones, and switches output over to "Speaker". The system doesn't actually have a speaker, only a headphone jack. And when the system switches over to "Speaker", I get no sound out of the headphones, even if I open "pavucontrol" and swap over to "Headphones (unplugged)" on the "Output Devices" tab. This is what "pacmd"'s "list-cards" command says with my headphones *unplugged*: 2 card(s) available. index: 0 name: driver: owner module: 7 properties: alsa.card = "1" alsa.card_name = "Intel HDMI/DP LPE Audio" alsa.long_card_name = "Intel HDMI/DP LPE Audio" alsa.driver_name = "snd_hdmi_lpe_audio" device.bus_path = "pci-:00:02.0-platform-hdmi-lpe-audio" sysfs.path = "/devices/pci:00/:00:02.0/hdmi-lpe-audio/sound/card1" device.bus = "pci" device.vendor.id = "8086" device.vendor.name = "Intel Corporation" device.product.id = "22b0" device.product.name = "Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers" device.string = "1" device.description = "Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers" module-udev-detect.discovered = "1" device.icon_name = "audio-card-pci" profiles: output:hdmi-stereo: Digital Stereo (HDMI) Output (priority 5900, available: no) output:hdmi-surround: Digital Surround 5.1 (HDMI) Output (priority 800, available: no) output:hdmi-surround71: Digital Surround 7.1 (HDMI) Output (priority 800, available: no) output:hdmi-stereo-extra1: Digital Stereo (HDMI 2) Output (priority 5700, available: no) output:hdmi-surround-extra1: Digital Surround 5.1 (HDMI 2) Output (priority 600, available: no) output:hdmi-surround71-extra1: Digital Surround 7.1 (HDMI 2) Output (priority 600, available: no) output:hdmi-stereo-extra2: Digital Stereo (HDMI 3) Output (priority 5700, available: no) output:hdmi-surround-extra2: Digital Surround 5.1 (HDMI 3) Output (priority 600, available: no) output:hdmi-surround71-extra2: Digital Surround 7.1 (HDMI 3) Output (priority 600, available: no) off: Off (priority 0, available: unknown) active profile: ports: hdmi-output-0: HDMI / DisplayPort (priority 5900, latency offset 0 usec, available: no) properties: device.icon_name = "video-display" hdmi-output-1: HDMI / DisplayPort 2 (priority 5800, latency offset 0 usec, available: no) properties: device.icon_name = "video-display" hdmi-output-2: HDMI / DisplayPort 3 (priority 5700, latency offset 0 usec, available: no) properties: device.icon_name = "video-display" index: 1 name: driver: owner module: 8 properties: alsa.card = "0" alsa.card_name = "chtrt5645" alsa.long_card_name = "AMICorporation-Defaultstring-Defaultstring-CherryTrailCR" alsa.driver_name = "snd_soc_sst_cht_bsw_rt5645" device.bus_path = "platform-cht-bsw-rt5645" sysfs.path = "/devices/pci:00/808622A8:00/cht-bsw-rt5645/sound/card0" device.form_factor = "internal" device.string = "0" device.description = "Built-in Audio" module-udev-detect.discovered = "1" device.icon_name = "audio-card" profiles: HiFi:
[Kernel-packages] [Bug 1824259] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1824259/+attachment/5255461/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1824259 Title: Headphone jack switch sense is inverted: plugging in headphones disables headphone output Status in linux package in Ubuntu: Confirmed Bug description: My machine is a LattePanda board, which uses a "chtrt5645" device as a sound card. It has a single headphone output jack, which I think is a TRRS jack, with a mic input, such as is normally used on phones. When I don't have headphones plugged in, the system thinks headphones *are* plugged in. Gnome Control Center shows my audio device as being headphones. If I insert a headphone connector partway into the jack, I can even get sound in the headphones. But if I plug the headphones all the way in, the system decided that I have *un*plugged the headphones, and switches output over to "Speaker". The system doesn't actually have a speaker, only a headphone jack. And when the system switches over to "Speaker", I get no sound out of the headphones, even if I open "pavucontrol" and swap over to "Headphones (unplugged)" on the "Output Devices" tab. This is what "pacmd"'s "list-cards" command says with my headphones *unplugged*: 2 card(s) available. index: 0 name: driver: owner module: 7 properties: alsa.card = "1" alsa.card_name = "Intel HDMI/DP LPE Audio" alsa.long_card_name = "Intel HDMI/DP LPE Audio" alsa.driver_name = "snd_hdmi_lpe_audio" device.bus_path = "pci-:00:02.0-platform-hdmi-lpe-audio" sysfs.path = "/devices/pci:00/:00:02.0/hdmi-lpe-audio/sound/card1" device.bus = "pci" device.vendor.id = "8086" device.vendor.name = "Intel Corporation" device.product.id = "22b0" device.product.name = "Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers" device.string = "1" device.description = "Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers" module-udev-detect.discovered = "1" device.icon_name = "audio-card-pci" profiles: output:hdmi-stereo: Digital Stereo (HDMI) Output (priority 5900, available: no) output:hdmi-surround: Digital Surround 5.1 (HDMI) Output (priority 800, available: no) output:hdmi-surround71: Digital Surround 7.1 (HDMI) Output (priority 800, available: no) output:hdmi-stereo-extra1: Digital Stereo (HDMI 2) Output (priority 5700, available: no) output:hdmi-surround-extra1: Digital Surround 5.1 (HDMI 2) Output (priority 600, available: no) output:hdmi-surround71-extra1: Digital Surround 7.1 (HDMI 2) Output (priority 600, available: no) output:hdmi-stereo-extra2: Digital Stereo (HDMI 3) Output (priority 5700, available: no) output:hdmi-surround-extra2: Digital Surround 5.1 (HDMI 3) Output (priority 600, available: no) output:hdmi-surround71-extra2: Digital Surround 7.1 (HDMI 3) Output (priority 600, available: no) off: Off (priority 0, available: unknown) active profile: ports: hdmi-output-0: HDMI / DisplayPort (priority 5900, latency offset 0 usec, available: no) properties: device.icon_name = "video-display" hdmi-output-1: HDMI / DisplayPort 2 (priority 5800, latency offset 0 usec, available: no) properties: device.icon_name = "video-display" hdmi-output-2: HDMI / DisplayPort 3 (priority 5700, latency offset 0 usec, available: no) properties: device.icon_name = "video-display" index: 1 name: driver: owner module: 8 properties: alsa.card = "0" alsa.card_name = "chtrt5645" alsa.long_card_name = "AMICorporation-Defaultstring-Defaultstring-CherryTrailCR" alsa.driver_name = "snd_soc_sst_cht_bsw_rt5645" device.bus_path = "platform-cht-bsw-rt5645" sysfs.path = "/devices/pci:00/808622A8:00/cht-bsw-rt5645/sound/card0" device.form_factor = "internal" device.string = "0" device.description = "Built-in Audio" module-udev-detect.discovered = "1" device.icon_name = "audio-card" profiles: HiFi: Default (priority
[Kernel-packages] [Bug 1824259] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1824259/+attachment/5255466/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1824259 Title: Headphone jack switch sense is inverted: plugging in headphones disables headphone output Status in linux package in Ubuntu: Confirmed Bug description: My machine is a LattePanda board, which uses a "chtrt5645" device as a sound card. It has a single headphone output jack, which I think is a TRRS jack, with a mic input, such as is normally used on phones. When I don't have headphones plugged in, the system thinks headphones *are* plugged in. Gnome Control Center shows my audio device as being headphones. If I insert a headphone connector partway into the jack, I can even get sound in the headphones. But if I plug the headphones all the way in, the system decided that I have *un*plugged the headphones, and switches output over to "Speaker". The system doesn't actually have a speaker, only a headphone jack. And when the system switches over to "Speaker", I get no sound out of the headphones, even if I open "pavucontrol" and swap over to "Headphones (unplugged)" on the "Output Devices" tab. This is what "pacmd"'s "list-cards" command says with my headphones *unplugged*: 2 card(s) available. index: 0 name: driver: owner module: 7 properties: alsa.card = "1" alsa.card_name = "Intel HDMI/DP LPE Audio" alsa.long_card_name = "Intel HDMI/DP LPE Audio" alsa.driver_name = "snd_hdmi_lpe_audio" device.bus_path = "pci-:00:02.0-platform-hdmi-lpe-audio" sysfs.path = "/devices/pci:00/:00:02.0/hdmi-lpe-audio/sound/card1" device.bus = "pci" device.vendor.id = "8086" device.vendor.name = "Intel Corporation" device.product.id = "22b0" device.product.name = "Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers" device.string = "1" device.description = "Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers" module-udev-detect.discovered = "1" device.icon_name = "audio-card-pci" profiles: output:hdmi-stereo: Digital Stereo (HDMI) Output (priority 5900, available: no) output:hdmi-surround: Digital Surround 5.1 (HDMI) Output (priority 800, available: no) output:hdmi-surround71: Digital Surround 7.1 (HDMI) Output (priority 800, available: no) output:hdmi-stereo-extra1: Digital Stereo (HDMI 2) Output (priority 5700, available: no) output:hdmi-surround-extra1: Digital Surround 5.1 (HDMI 2) Output (priority 600, available: no) output:hdmi-surround71-extra1: Digital Surround 7.1 (HDMI 2) Output (priority 600, available: no) output:hdmi-stereo-extra2: Digital Stereo (HDMI 3) Output (priority 5700, available: no) output:hdmi-surround-extra2: Digital Surround 5.1 (HDMI 3) Output (priority 600, available: no) output:hdmi-surround71-extra2: Digital Surround 7.1 (HDMI 3) Output (priority 600, available: no) off: Off (priority 0, available: unknown) active profile: ports: hdmi-output-0: HDMI / DisplayPort (priority 5900, latency offset 0 usec, available: no) properties: device.icon_name = "video-display" hdmi-output-1: HDMI / DisplayPort 2 (priority 5800, latency offset 0 usec, available: no) properties: device.icon_name = "video-display" hdmi-output-2: HDMI / DisplayPort 3 (priority 5700, latency offset 0 usec, available: no) properties: device.icon_name = "video-display" index: 1 name: driver: owner module: 8 properties: alsa.card = "0" alsa.card_name = "chtrt5645" alsa.long_card_name = "AMICorporation-Defaultstring-Defaultstring-CherryTrailCR" alsa.driver_name = "snd_soc_sst_cht_bsw_rt5645" device.bus_path = "platform-cht-bsw-rt5645" sysfs.path = "/devices/pci:00/808622A8:00/cht-bsw-rt5645/sound/card0" device.form_factor = "internal" device.string = "0" device.description = "Built-in Audio" module-udev-detect.discovered = "1" device.icon_name = "audio-card" profiles: HiFi: Default (priority
[Kernel-packages] [Bug 1824259] Re: Headphone jack switch sense is inverted: plugging in headphones disables headphone output
apport information ** Tags added: apport-collected ** Description changed: My machine is a LattePanda board, which uses a "chtrt5645" device as a sound card. It has a single headphone output jack, which I think is a TRRS jack, with a mic input, such as is normally used on phones. When I don't have headphones plugged in, the system thinks headphones *are* plugged in. Gnome Control Center shows my audio device as being headphones. If I insert a headphone connector partway into the jack, I can even get sound in the headphones. But if I plug the headphones all the way in, the system decided that I have *un*plugged the headphones, and switches output over to "Speaker". The system doesn't actually have a speaker, only a headphone jack. And when the system switches over to "Speaker", I get no sound out of the headphones, even if I open "pavucontrol" and swap over to "Headphones (unplugged)" on the "Output Devices" tab. This is what "pacmd"'s "list-cards" command says with my headphones *unplugged*: 2 card(s) available. index: 0 name: driver: owner module: 7 properties: alsa.card = "1" alsa.card_name = "Intel HDMI/DP LPE Audio" alsa.long_card_name = "Intel HDMI/DP LPE Audio" alsa.driver_name = "snd_hdmi_lpe_audio" device.bus_path = "pci-:00:02.0-platform-hdmi-lpe-audio" sysfs.path = "/devices/pci:00/:00:02.0/hdmi-lpe-audio/sound/card1" device.bus = "pci" device.vendor.id = "8086" device.vendor.name = "Intel Corporation" device.product.id = "22b0" device.product.name = "Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers" device.string = "1" device.description = "Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers" module-udev-detect.discovered = "1" device.icon_name = "audio-card-pci" profiles: output:hdmi-stereo: Digital Stereo (HDMI) Output (priority 5900, available: no) output:hdmi-surround: Digital Surround 5.1 (HDMI) Output (priority 800, available: no) output:hdmi-surround71: Digital Surround 7.1 (HDMI) Output (priority 800, available: no) output:hdmi-stereo-extra1: Digital Stereo (HDMI 2) Output (priority 5700, available: no) output:hdmi-surround-extra1: Digital Surround 5.1 (HDMI 2) Output (priority 600, available: no) output:hdmi-surround71-extra1: Digital Surround 7.1 (HDMI 2) Output (priority 600, available: no) output:hdmi-stereo-extra2: Digital Stereo (HDMI 3) Output (priority 5700, available: no) output:hdmi-surround-extra2: Digital Surround 5.1 (HDMI 3) Output (priority 600, available: no) output:hdmi-surround71-extra2: Digital Surround 7.1 (HDMI 3) Output (priority 600, available: no) off: Off (priority 0, available: unknown) active profile: ports: hdmi-output-0: HDMI / DisplayPort (priority 5900, latency offset 0 usec, available: no) properties: device.icon_name = "video-display" hdmi-output-1: HDMI / DisplayPort 2 (priority 5800, latency offset 0 usec, available: no) properties: device.icon_name = "video-display" hdmi-output-2: HDMI / DisplayPort 3 (priority 5700, latency offset 0 usec, available: no) properties: device.icon_name = "video-display" index: 1 name: driver: owner module: 8 properties: alsa.card = "0" alsa.card_name = "chtrt5645" alsa.long_card_name = "AMICorporation-Defaultstring-Defaultstring-CherryTrailCR" alsa.driver_name = "snd_soc_sst_cht_bsw_rt5645" device.bus_path = "platform-cht-bsw-rt5645" sysfs.path = "/devices/pci:00/808622A8:00/cht-bsw-rt5645/sound/card0" device.form_factor = "internal" device.string = "0" device.description = "Built-in Audio" module-udev-detect.discovered = "1" device.icon_name = "audio-card" profiles: HiFi: Default (priority 8000, available: unknown) off: Off (priority 0, available: unknown) active profile: sinks: alsa_output.platform-cht-bsw-rt5645.HiFi__hw_chtrt5645__sink/#0: Built-in Audio Headphones + Speaker sources: alsa_output.platform-cht-bsw-rt5645.HiFi__hw_chtrt5645__sink.monitor/#0: Monitor of Built-in Audio
[Kernel-packages] [Bug 1824259] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1824259/+attachment/5255459/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1824259 Title: Headphone jack switch sense is inverted: plugging in headphones disables headphone output Status in linux package in Ubuntu: Confirmed Bug description: My machine is a LattePanda board, which uses a "chtrt5645" device as a sound card. It has a single headphone output jack, which I think is a TRRS jack, with a mic input, such as is normally used on phones. When I don't have headphones plugged in, the system thinks headphones *are* plugged in. Gnome Control Center shows my audio device as being headphones. If I insert a headphone connector partway into the jack, I can even get sound in the headphones. But if I plug the headphones all the way in, the system decided that I have *un*plugged the headphones, and switches output over to "Speaker". The system doesn't actually have a speaker, only a headphone jack. And when the system switches over to "Speaker", I get no sound out of the headphones, even if I open "pavucontrol" and swap over to "Headphones (unplugged)" on the "Output Devices" tab. This is what "pacmd"'s "list-cards" command says with my headphones *unplugged*: 2 card(s) available. index: 0 name: driver: owner module: 7 properties: alsa.card = "1" alsa.card_name = "Intel HDMI/DP LPE Audio" alsa.long_card_name = "Intel HDMI/DP LPE Audio" alsa.driver_name = "snd_hdmi_lpe_audio" device.bus_path = "pci-:00:02.0-platform-hdmi-lpe-audio" sysfs.path = "/devices/pci:00/:00:02.0/hdmi-lpe-audio/sound/card1" device.bus = "pci" device.vendor.id = "8086" device.vendor.name = "Intel Corporation" device.product.id = "22b0" device.product.name = "Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers" device.string = "1" device.description = "Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers" module-udev-detect.discovered = "1" device.icon_name = "audio-card-pci" profiles: output:hdmi-stereo: Digital Stereo (HDMI) Output (priority 5900, available: no) output:hdmi-surround: Digital Surround 5.1 (HDMI) Output (priority 800, available: no) output:hdmi-surround71: Digital Surround 7.1 (HDMI) Output (priority 800, available: no) output:hdmi-stereo-extra1: Digital Stereo (HDMI 2) Output (priority 5700, available: no) output:hdmi-surround-extra1: Digital Surround 5.1 (HDMI 2) Output (priority 600, available: no) output:hdmi-surround71-extra1: Digital Surround 7.1 (HDMI 2) Output (priority 600, available: no) output:hdmi-stereo-extra2: Digital Stereo (HDMI 3) Output (priority 5700, available: no) output:hdmi-surround-extra2: Digital Surround 5.1 (HDMI 3) Output (priority 600, available: no) output:hdmi-surround71-extra2: Digital Surround 7.1 (HDMI 3) Output (priority 600, available: no) off: Off (priority 0, available: unknown) active profile: ports: hdmi-output-0: HDMI / DisplayPort (priority 5900, latency offset 0 usec, available: no) properties: device.icon_name = "video-display" hdmi-output-1: HDMI / DisplayPort 2 (priority 5800, latency offset 0 usec, available: no) properties: device.icon_name = "video-display" hdmi-output-2: HDMI / DisplayPort 3 (priority 5700, latency offset 0 usec, available: no) properties: device.icon_name = "video-display" index: 1 name: driver: owner module: 8 properties: alsa.card = "0" alsa.card_name = "chtrt5645" alsa.long_card_name = "AMICorporation-Defaultstring-Defaultstring-CherryTrailCR" alsa.driver_name = "snd_soc_sst_cht_bsw_rt5645" device.bus_path = "platform-cht-bsw-rt5645" sysfs.path = "/devices/pci:00/808622A8:00/cht-bsw-rt5645/sound/card0" device.form_factor = "internal" device.string = "0" device.description = "Built-in Audio" module-udev-detect.discovered = "1" device.icon_name = "audio-card" profiles: HiFi: Default
[Kernel-packages] [Bug 1824259] Re: Headphone jack switch sense is inverted: plugging in headphones disables headphone output
I set the bug to Confirmed, despite being the original reporter, because the bot told me to. The Apport logs I posted are form the system with my workaround enabled. I also blacklisted the HDMI audio module, since I don't use HDMI audio, and I thought it might help. It didn't seem to, but I never unblacklisted it. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1824259 Title: Headphone jack switch sense is inverted: plugging in headphones disables headphone output Status in linux package in Ubuntu: Confirmed Bug description: My machine is a LattePanda board, which uses a "chtrt5645" device as a sound card. It has a single headphone output jack, which I think is a TRRS jack, with a mic input, such as is normally used on phones. When I don't have headphones plugged in, the system thinks headphones *are* plugged in. Gnome Control Center shows my audio device as being headphones. If I insert a headphone connector partway into the jack, I can even get sound in the headphones. But if I plug the headphones all the way in, the system decided that I have *un*plugged the headphones, and switches output over to "Speaker". The system doesn't actually have a speaker, only a headphone jack. And when the system switches over to "Speaker", I get no sound out of the headphones, even if I open "pavucontrol" and swap over to "Headphones (unplugged)" on the "Output Devices" tab. This is what "pacmd"'s "list-cards" command says with my headphones *unplugged*: 2 card(s) available. index: 0 name: driver: owner module: 7 properties: alsa.card = "1" alsa.card_name = "Intel HDMI/DP LPE Audio" alsa.long_card_name = "Intel HDMI/DP LPE Audio" alsa.driver_name = "snd_hdmi_lpe_audio" device.bus_path = "pci-:00:02.0-platform-hdmi-lpe-audio" sysfs.path = "/devices/pci:00/:00:02.0/hdmi-lpe-audio/sound/card1" device.bus = "pci" device.vendor.id = "8086" device.vendor.name = "Intel Corporation" device.product.id = "22b0" device.product.name = "Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers" device.string = "1" device.description = "Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers" module-udev-detect.discovered = "1" device.icon_name = "audio-card-pci" profiles: output:hdmi-stereo: Digital Stereo (HDMI) Output (priority 5900, available: no) output:hdmi-surround: Digital Surround 5.1 (HDMI) Output (priority 800, available: no) output:hdmi-surround71: Digital Surround 7.1 (HDMI) Output (priority 800, available: no) output:hdmi-stereo-extra1: Digital Stereo (HDMI 2) Output (priority 5700, available: no) output:hdmi-surround-extra1: Digital Surround 5.1 (HDMI 2) Output (priority 600, available: no) output:hdmi-surround71-extra1: Digital Surround 7.1 (HDMI 2) Output (priority 600, available: no) output:hdmi-stereo-extra2: Digital Stereo (HDMI 3) Output (priority 5700, available: no) output:hdmi-surround-extra2: Digital Surround 5.1 (HDMI 3) Output (priority 600, available: no) output:hdmi-surround71-extra2: Digital Surround 7.1 (HDMI 3) Output (priority 600, available: no) off: Off (priority 0, available: unknown) active profile: ports: hdmi-output-0: HDMI / DisplayPort (priority 5900, latency offset 0 usec, available: no) properties: device.icon_name = "video-display" hdmi-output-1: HDMI / DisplayPort 2 (priority 5800, latency offset 0 usec, available: no) properties: device.icon_name = "video-display" hdmi-output-2: HDMI / DisplayPort 3 (priority 5700, latency offset 0 usec, available: no) properties: device.icon_name = "video-display" index: 1 name: driver: owner module: 8 properties: alsa.card = "0" alsa.card_name = "chtrt5645" alsa.long_card_name = "AMICorporation-Defaultstring-Defaultstring-CherryTrailCR" alsa.driver_name = "snd_soc_sst_cht_bsw_rt5645" device.bus_path = "platform-cht-bsw-rt5645" sysfs.path = "/devices/pci:00/808622A8:00/cht-bsw-rt5645/sound/card0" device.form_factor = "internal" device.string = "0"
[Kernel-packages] [Bug 1824259] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1824259/+attachment/5255467/+files/WifiSyslog.txt ** 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/1824259 Title: Headphone jack switch sense is inverted: plugging in headphones disables headphone output Status in linux package in Ubuntu: Confirmed Bug description: My machine is a LattePanda board, which uses a "chtrt5645" device as a sound card. It has a single headphone output jack, which I think is a TRRS jack, with a mic input, such as is normally used on phones. When I don't have headphones plugged in, the system thinks headphones *are* plugged in. Gnome Control Center shows my audio device as being headphones. If I insert a headphone connector partway into the jack, I can even get sound in the headphones. But if I plug the headphones all the way in, the system decided that I have *un*plugged the headphones, and switches output over to "Speaker". The system doesn't actually have a speaker, only a headphone jack. And when the system switches over to "Speaker", I get no sound out of the headphones, even if I open "pavucontrol" and swap over to "Headphones (unplugged)" on the "Output Devices" tab. This is what "pacmd"'s "list-cards" command says with my headphones *unplugged*: 2 card(s) available. index: 0 name: driver: owner module: 7 properties: alsa.card = "1" alsa.card_name = "Intel HDMI/DP LPE Audio" alsa.long_card_name = "Intel HDMI/DP LPE Audio" alsa.driver_name = "snd_hdmi_lpe_audio" device.bus_path = "pci-:00:02.0-platform-hdmi-lpe-audio" sysfs.path = "/devices/pci:00/:00:02.0/hdmi-lpe-audio/sound/card1" device.bus = "pci" device.vendor.id = "8086" device.vendor.name = "Intel Corporation" device.product.id = "22b0" device.product.name = "Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers" device.string = "1" device.description = "Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers" module-udev-detect.discovered = "1" device.icon_name = "audio-card-pci" profiles: output:hdmi-stereo: Digital Stereo (HDMI) Output (priority 5900, available: no) output:hdmi-surround: Digital Surround 5.1 (HDMI) Output (priority 800, available: no) output:hdmi-surround71: Digital Surround 7.1 (HDMI) Output (priority 800, available: no) output:hdmi-stereo-extra1: Digital Stereo (HDMI 2) Output (priority 5700, available: no) output:hdmi-surround-extra1: Digital Surround 5.1 (HDMI 2) Output (priority 600, available: no) output:hdmi-surround71-extra1: Digital Surround 7.1 (HDMI 2) Output (priority 600, available: no) output:hdmi-stereo-extra2: Digital Stereo (HDMI 3) Output (priority 5700, available: no) output:hdmi-surround-extra2: Digital Surround 5.1 (HDMI 3) Output (priority 600, available: no) output:hdmi-surround71-extra2: Digital Surround 7.1 (HDMI 3) Output (priority 600, available: no) off: Off (priority 0, available: unknown) active profile: ports: hdmi-output-0: HDMI / DisplayPort (priority 5900, latency offset 0 usec, available: no) properties: device.icon_name = "video-display" hdmi-output-1: HDMI / DisplayPort 2 (priority 5800, latency offset 0 usec, available: no) properties: device.icon_name = "video-display" hdmi-output-2: HDMI / DisplayPort 3 (priority 5700, latency offset 0 usec, available: no) properties: device.icon_name = "video-display" index: 1 name: driver: owner module: 8 properties: alsa.card = "0" alsa.card_name = "chtrt5645" alsa.long_card_name = "AMICorporation-Defaultstring-Defaultstring-CherryTrailCR" alsa.driver_name = "snd_soc_sst_cht_bsw_rt5645" device.bus_path = "platform-cht-bsw-rt5645" sysfs.path = "/devices/pci:00/808622A8:00/cht-bsw-rt5645/sound/card0" device.form_factor = "internal" device.string = "0" device.description = "Built-in Audio" module-udev-detect.discovered = "1"
[Kernel-packages] [Bug 1824259] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1824259/+attachment/5255458/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1824259 Title: Headphone jack switch sense is inverted: plugging in headphones disables headphone output Status in linux package in Ubuntu: Confirmed Bug description: My machine is a LattePanda board, which uses a "chtrt5645" device as a sound card. It has a single headphone output jack, which I think is a TRRS jack, with a mic input, such as is normally used on phones. When I don't have headphones plugged in, the system thinks headphones *are* plugged in. Gnome Control Center shows my audio device as being headphones. If I insert a headphone connector partway into the jack, I can even get sound in the headphones. But if I plug the headphones all the way in, the system decided that I have *un*plugged the headphones, and switches output over to "Speaker". The system doesn't actually have a speaker, only a headphone jack. And when the system switches over to "Speaker", I get no sound out of the headphones, even if I open "pavucontrol" and swap over to "Headphones (unplugged)" on the "Output Devices" tab. This is what "pacmd"'s "list-cards" command says with my headphones *unplugged*: 2 card(s) available. index: 0 name: driver: owner module: 7 properties: alsa.card = "1" alsa.card_name = "Intel HDMI/DP LPE Audio" alsa.long_card_name = "Intel HDMI/DP LPE Audio" alsa.driver_name = "snd_hdmi_lpe_audio" device.bus_path = "pci-:00:02.0-platform-hdmi-lpe-audio" sysfs.path = "/devices/pci:00/:00:02.0/hdmi-lpe-audio/sound/card1" device.bus = "pci" device.vendor.id = "8086" device.vendor.name = "Intel Corporation" device.product.id = "22b0" device.product.name = "Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers" device.string = "1" device.description = "Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers" module-udev-detect.discovered = "1" device.icon_name = "audio-card-pci" profiles: output:hdmi-stereo: Digital Stereo (HDMI) Output (priority 5900, available: no) output:hdmi-surround: Digital Surround 5.1 (HDMI) Output (priority 800, available: no) output:hdmi-surround71: Digital Surround 7.1 (HDMI) Output (priority 800, available: no) output:hdmi-stereo-extra1: Digital Stereo (HDMI 2) Output (priority 5700, available: no) output:hdmi-surround-extra1: Digital Surround 5.1 (HDMI 2) Output (priority 600, available: no) output:hdmi-surround71-extra1: Digital Surround 7.1 (HDMI 2) Output (priority 600, available: no) output:hdmi-stereo-extra2: Digital Stereo (HDMI 3) Output (priority 5700, available: no) output:hdmi-surround-extra2: Digital Surround 5.1 (HDMI 3) Output (priority 600, available: no) output:hdmi-surround71-extra2: Digital Surround 7.1 (HDMI 3) Output (priority 600, available: no) off: Off (priority 0, available: unknown) active profile: ports: hdmi-output-0: HDMI / DisplayPort (priority 5900, latency offset 0 usec, available: no) properties: device.icon_name = "video-display" hdmi-output-1: HDMI / DisplayPort 2 (priority 5800, latency offset 0 usec, available: no) properties: device.icon_name = "video-display" hdmi-output-2: HDMI / DisplayPort 3 (priority 5700, latency offset 0 usec, available: no) properties: device.icon_name = "video-display" index: 1 name: driver: owner module: 8 properties: alsa.card = "0" alsa.card_name = "chtrt5645" alsa.long_card_name = "AMICorporation-Defaultstring-Defaultstring-CherryTrailCR" alsa.driver_name = "snd_soc_sst_cht_bsw_rt5645" device.bus_path = "platform-cht-bsw-rt5645" sysfs.path = "/devices/pci:00/808622A8:00/cht-bsw-rt5645/sound/card0" device.form_factor = "internal" device.string = "0" device.description = "Built-in Audio" module-udev-detect.discovered = "1" device.icon_name = "audio-card" profiles: HiFi: Default (priority 8000,
[Kernel-packages] [Bug 1824259] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1824259/+attachment/5255460/+files/IwConfig.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1824259 Title: Headphone jack switch sense is inverted: plugging in headphones disables headphone output Status in linux package in Ubuntu: Confirmed Bug description: My machine is a LattePanda board, which uses a "chtrt5645" device as a sound card. It has a single headphone output jack, which I think is a TRRS jack, with a mic input, such as is normally used on phones. When I don't have headphones plugged in, the system thinks headphones *are* plugged in. Gnome Control Center shows my audio device as being headphones. If I insert a headphone connector partway into the jack, I can even get sound in the headphones. But if I plug the headphones all the way in, the system decided that I have *un*plugged the headphones, and switches output over to "Speaker". The system doesn't actually have a speaker, only a headphone jack. And when the system switches over to "Speaker", I get no sound out of the headphones, even if I open "pavucontrol" and swap over to "Headphones (unplugged)" on the "Output Devices" tab. This is what "pacmd"'s "list-cards" command says with my headphones *unplugged*: 2 card(s) available. index: 0 name: driver: owner module: 7 properties: alsa.card = "1" alsa.card_name = "Intel HDMI/DP LPE Audio" alsa.long_card_name = "Intel HDMI/DP LPE Audio" alsa.driver_name = "snd_hdmi_lpe_audio" device.bus_path = "pci-:00:02.0-platform-hdmi-lpe-audio" sysfs.path = "/devices/pci:00/:00:02.0/hdmi-lpe-audio/sound/card1" device.bus = "pci" device.vendor.id = "8086" device.vendor.name = "Intel Corporation" device.product.id = "22b0" device.product.name = "Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers" device.string = "1" device.description = "Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers" module-udev-detect.discovered = "1" device.icon_name = "audio-card-pci" profiles: output:hdmi-stereo: Digital Stereo (HDMI) Output (priority 5900, available: no) output:hdmi-surround: Digital Surround 5.1 (HDMI) Output (priority 800, available: no) output:hdmi-surround71: Digital Surround 7.1 (HDMI) Output (priority 800, available: no) output:hdmi-stereo-extra1: Digital Stereo (HDMI 2) Output (priority 5700, available: no) output:hdmi-surround-extra1: Digital Surround 5.1 (HDMI 2) Output (priority 600, available: no) output:hdmi-surround71-extra1: Digital Surround 7.1 (HDMI 2) Output (priority 600, available: no) output:hdmi-stereo-extra2: Digital Stereo (HDMI 3) Output (priority 5700, available: no) output:hdmi-surround-extra2: Digital Surround 5.1 (HDMI 3) Output (priority 600, available: no) output:hdmi-surround71-extra2: Digital Surround 7.1 (HDMI 3) Output (priority 600, available: no) off: Off (priority 0, available: unknown) active profile: ports: hdmi-output-0: HDMI / DisplayPort (priority 5900, latency offset 0 usec, available: no) properties: device.icon_name = "video-display" hdmi-output-1: HDMI / DisplayPort 2 (priority 5800, latency offset 0 usec, available: no) properties: device.icon_name = "video-display" hdmi-output-2: HDMI / DisplayPort 3 (priority 5700, latency offset 0 usec, available: no) properties: device.icon_name = "video-display" index: 1 name: driver: owner module: 8 properties: alsa.card = "0" alsa.card_name = "chtrt5645" alsa.long_card_name = "AMICorporation-Defaultstring-Defaultstring-CherryTrailCR" alsa.driver_name = "snd_soc_sst_cht_bsw_rt5645" device.bus_path = "platform-cht-bsw-rt5645" sysfs.path = "/devices/pci:00/808622A8:00/cht-bsw-rt5645/sound/card0" device.form_factor = "internal" device.string = "0" device.description = "Built-in Audio" module-udev-detect.discovered = "1" device.icon_name = "audio-card" profiles: HiFi: Default
[Kernel-packages] [Bug 1824259] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1824259/+attachment/5255465/+files/PulseList.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1824259 Title: Headphone jack switch sense is inverted: plugging in headphones disables headphone output Status in linux package in Ubuntu: Confirmed Bug description: My machine is a LattePanda board, which uses a "chtrt5645" device as a sound card. It has a single headphone output jack, which I think is a TRRS jack, with a mic input, such as is normally used on phones. When I don't have headphones plugged in, the system thinks headphones *are* plugged in. Gnome Control Center shows my audio device as being headphones. If I insert a headphone connector partway into the jack, I can even get sound in the headphones. But if I plug the headphones all the way in, the system decided that I have *un*plugged the headphones, and switches output over to "Speaker". The system doesn't actually have a speaker, only a headphone jack. And when the system switches over to "Speaker", I get no sound out of the headphones, even if I open "pavucontrol" and swap over to "Headphones (unplugged)" on the "Output Devices" tab. This is what "pacmd"'s "list-cards" command says with my headphones *unplugged*: 2 card(s) available. index: 0 name: driver: owner module: 7 properties: alsa.card = "1" alsa.card_name = "Intel HDMI/DP LPE Audio" alsa.long_card_name = "Intel HDMI/DP LPE Audio" alsa.driver_name = "snd_hdmi_lpe_audio" device.bus_path = "pci-:00:02.0-platform-hdmi-lpe-audio" sysfs.path = "/devices/pci:00/:00:02.0/hdmi-lpe-audio/sound/card1" device.bus = "pci" device.vendor.id = "8086" device.vendor.name = "Intel Corporation" device.product.id = "22b0" device.product.name = "Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers" device.string = "1" device.description = "Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers" module-udev-detect.discovered = "1" device.icon_name = "audio-card-pci" profiles: output:hdmi-stereo: Digital Stereo (HDMI) Output (priority 5900, available: no) output:hdmi-surround: Digital Surround 5.1 (HDMI) Output (priority 800, available: no) output:hdmi-surround71: Digital Surround 7.1 (HDMI) Output (priority 800, available: no) output:hdmi-stereo-extra1: Digital Stereo (HDMI 2) Output (priority 5700, available: no) output:hdmi-surround-extra1: Digital Surround 5.1 (HDMI 2) Output (priority 600, available: no) output:hdmi-surround71-extra1: Digital Surround 7.1 (HDMI 2) Output (priority 600, available: no) output:hdmi-stereo-extra2: Digital Stereo (HDMI 3) Output (priority 5700, available: no) output:hdmi-surround-extra2: Digital Surround 5.1 (HDMI 3) Output (priority 600, available: no) output:hdmi-surround71-extra2: Digital Surround 7.1 (HDMI 3) Output (priority 600, available: no) off: Off (priority 0, available: unknown) active profile: ports: hdmi-output-0: HDMI / DisplayPort (priority 5900, latency offset 0 usec, available: no) properties: device.icon_name = "video-display" hdmi-output-1: HDMI / DisplayPort 2 (priority 5800, latency offset 0 usec, available: no) properties: device.icon_name = "video-display" hdmi-output-2: HDMI / DisplayPort 3 (priority 5700, latency offset 0 usec, available: no) properties: device.icon_name = "video-display" index: 1 name: driver: owner module: 8 properties: alsa.card = "0" alsa.card_name = "chtrt5645" alsa.long_card_name = "AMICorporation-Defaultstring-Defaultstring-CherryTrailCR" alsa.driver_name = "snd_soc_sst_cht_bsw_rt5645" device.bus_path = "platform-cht-bsw-rt5645" sysfs.path = "/devices/pci:00/808622A8:00/cht-bsw-rt5645/sound/card0" device.form_factor = "internal" device.string = "0" device.description = "Built-in Audio" module-udev-detect.discovered = "1" device.icon_name = "audio-card" profiles: HiFi: Default
[Kernel-packages] [Bug 1824259] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1824259/+attachment/5255464/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1824259 Title: Headphone jack switch sense is inverted: plugging in headphones disables headphone output Status in linux package in Ubuntu: Confirmed Bug description: My machine is a LattePanda board, which uses a "chtrt5645" device as a sound card. It has a single headphone output jack, which I think is a TRRS jack, with a mic input, such as is normally used on phones. When I don't have headphones plugged in, the system thinks headphones *are* plugged in. Gnome Control Center shows my audio device as being headphones. If I insert a headphone connector partway into the jack, I can even get sound in the headphones. But if I plug the headphones all the way in, the system decided that I have *un*plugged the headphones, and switches output over to "Speaker". The system doesn't actually have a speaker, only a headphone jack. And when the system switches over to "Speaker", I get no sound out of the headphones, even if I open "pavucontrol" and swap over to "Headphones (unplugged)" on the "Output Devices" tab. This is what "pacmd"'s "list-cards" command says with my headphones *unplugged*: 2 card(s) available. index: 0 name: driver: owner module: 7 properties: alsa.card = "1" alsa.card_name = "Intel HDMI/DP LPE Audio" alsa.long_card_name = "Intel HDMI/DP LPE Audio" alsa.driver_name = "snd_hdmi_lpe_audio" device.bus_path = "pci-:00:02.0-platform-hdmi-lpe-audio" sysfs.path = "/devices/pci:00/:00:02.0/hdmi-lpe-audio/sound/card1" device.bus = "pci" device.vendor.id = "8086" device.vendor.name = "Intel Corporation" device.product.id = "22b0" device.product.name = "Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers" device.string = "1" device.description = "Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers" module-udev-detect.discovered = "1" device.icon_name = "audio-card-pci" profiles: output:hdmi-stereo: Digital Stereo (HDMI) Output (priority 5900, available: no) output:hdmi-surround: Digital Surround 5.1 (HDMI) Output (priority 800, available: no) output:hdmi-surround71: Digital Surround 7.1 (HDMI) Output (priority 800, available: no) output:hdmi-stereo-extra1: Digital Stereo (HDMI 2) Output (priority 5700, available: no) output:hdmi-surround-extra1: Digital Surround 5.1 (HDMI 2) Output (priority 600, available: no) output:hdmi-surround71-extra1: Digital Surround 7.1 (HDMI 2) Output (priority 600, available: no) output:hdmi-stereo-extra2: Digital Stereo (HDMI 3) Output (priority 5700, available: no) output:hdmi-surround-extra2: Digital Surround 5.1 (HDMI 3) Output (priority 600, available: no) output:hdmi-surround71-extra2: Digital Surround 7.1 (HDMI 3) Output (priority 600, available: no) off: Off (priority 0, available: unknown) active profile: ports: hdmi-output-0: HDMI / DisplayPort (priority 5900, latency offset 0 usec, available: no) properties: device.icon_name = "video-display" hdmi-output-1: HDMI / DisplayPort 2 (priority 5800, latency offset 0 usec, available: no) properties: device.icon_name = "video-display" hdmi-output-2: HDMI / DisplayPort 3 (priority 5700, latency offset 0 usec, available: no) properties: device.icon_name = "video-display" index: 1 name: driver: owner module: 8 properties: alsa.card = "0" alsa.card_name = "chtrt5645" alsa.long_card_name = "AMICorporation-Defaultstring-Defaultstring-CherryTrailCR" alsa.driver_name = "snd_soc_sst_cht_bsw_rt5645" device.bus_path = "platform-cht-bsw-rt5645" sysfs.path = "/devices/pci:00/808622A8:00/cht-bsw-rt5645/sound/card0" device.form_factor = "internal" device.string = "0" device.description = "Built-in Audio" module-udev-detect.discovered = "1" device.icon_name = "audio-card" profiles: HiFi: Default
[Kernel-packages] [Bug 1776563]
try running mprime to check cpu frequency scaling,mine could run at 3.6ghz and after i disable turbo boost runs max at 2.5ghz -- 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/1776563 Title: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash Status in amd: Fix Released Status in Linux: Incomplete Status in linux package in Ubuntu: Triaged Bug description: CPU: Ryzen 5 2500U VGA: Radeon 535 Notebook: Acer Aspire A315 This is a brand new notebook on the market with Ryzen 5/Radeon. The default kernel of Ubuntu(18.04) hangs at loading with message: tsc: Refined TSC clocksource calibration: 1996.250 MHz clocksource: tsc: mask: 0x max_cycles: (...), max_idle_ns: (...) Soft lockup Using pci=noacpi kernel parameter kernel loads without any problem but my notebook produces more heat than on Win10. If I know right Acer notebooks need ACPI to the correct power management. The same thing happens on mainline 4.17,4.18rc1-2. BIOS upgrade to the latest version: 1.08 hasn't helped This problem has been reported upstream: https://bugzilla.kernel.org/show_bug.cgi?id=200087 The latest correctly working kernel was 4.13.* but the heat problem was present with this too. To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1776563/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1776563]
So, manjaro 5.0.7 boot with this cmdline BOOT_IMAGE=/boot/vmlinuz-5.0-x86_64 root=UUID=7185a279-f7e5-4189-b218-39f49eedce8a rw quiet loglevel=3 vga=current rd.systemd.show_status=auto rd.udev.log-priority=3 pcie_aspm=off vt.global_cursor_default=0 resume=UUID=12aa527f-2e4d-4587-bae6-d99a220acf6c CPU doesn't boost itself any further than 2.0 ghz. Gonna check 5.1-rc4 with AMD fixes later -- 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/1776563 Title: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash Status in amd: Fix Released Status in Linux: Incomplete Status in linux package in Ubuntu: Triaged Bug description: CPU: Ryzen 5 2500U VGA: Radeon 535 Notebook: Acer Aspire A315 This is a brand new notebook on the market with Ryzen 5/Radeon. The default kernel of Ubuntu(18.04) hangs at loading with message: tsc: Refined TSC clocksource calibration: 1996.250 MHz clocksource: tsc: mask: 0x max_cycles: (...), max_idle_ns: (...) Soft lockup Using pci=noacpi kernel parameter kernel loads without any problem but my notebook produces more heat than on Win10. If I know right Acer notebooks need ACPI to the correct power management. The same thing happens on mainline 4.17,4.18rc1-2. BIOS upgrade to the latest version: 1.08 hasn't helped This problem has been reported upstream: https://bugzilla.kernel.org/show_bug.cgi?id=200087 The latest correctly working kernel was 4.13.* but the heat problem was present with this too. To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1776563/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1824642] Re: nvidia card disabled after upgrading to 5.0.0-11-generic
I have just upgraded to 5.0.0-11 on my other laptop also with hybrid Intel+Nvidia GPU stack (a different Nvidia GPU though) - the same thing happened, Linux+nouveau completely ignores the nvidia GPU. -- 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/1824642 Title: nvidia card disabled after upgrading to 5.0.0-11-generic Status in linux package in Ubuntu: Confirmed Bug description: After upgrading from 5.0.0.8-generic to 5.0.0.11-generic, the nvidia card suddenly became "disabled". I own a laptop with hybrid GPU stack, intel + nvidia; nvidia is in charge of display ports. On 5.0.0.8-generic I had only nvidia GPU enabled (discrete mode) and nouveau was able to properly control nvidia and send the signal to my monitor. In hybrid mode this worked as well properly. On 5.0.0.11-generic in discrete mode, linux booted to 640x480 resolution only. When I enabled hybrid mode back, the computer boots into 1920x1200 mode properly, however the display port ports don't work at all, and the "About" screen only lists the Intel GPU, not nvidia. lspci still lists nvidia though. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-11-generic 5.0.0-11.12 ProcVersionSignature: Ubuntu 5.0.0-11.12-generic 5.0.6 Uname: Linux 5.0.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mavi 2324 F pulseaudio /dev/snd/controlC1: mavi 2324 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Apr 13 20:09:25 2019 HibernationDevice: RESUME=/dev/mapper/vg0-lv0--swap InstallationDate: Installed on 2016-09-05 (950 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: LENOVO 20EN0005MS ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-11-generic root=/dev/mapper/vg0-lv1--root ro splash ipv6.disable=1 vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.0.0-11-generic N/A linux-backports-modules-5.0.0-11-generic N/A linux-firmware1.178 SourcePackage: linux UpgradeStatus: Upgraded to disco on 2019-03-12 (32 days ago) dmi.bios.date: 02/21/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N1EET83W (1.56 ) dmi.board.asset.tag: Not Available dmi.board.name: 20EN0005MS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1EET83W(1.56):bd02/21/2019:svnLENOVO:pn20EN0005MS:pvrThinkPadP50:rvnLENOVO:rn20EN0005MS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P50 dmi.product.name: 20EN0005MS dmi.product.sku: LENOVO_MT_20EN_BU_Think_FM_ThinkPad P50 dmi.product.version: ThinkPad P50 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824642/+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 1824641] Re: Blank screen after booting 4.4.0-145
Sorry I cannot collect log files for the kernel giving the bug. If I can collect any useful information using the kernel that does work, please let me know ** Changed in: mutter (Ubuntu) Status: New => Incomplete ** 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/1824641 Title: Blank screen after booting 4.4.0-145 Status in linux package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Incomplete Bug description: Having run update on my i386 Asus Eee PC with Intel Atom N550 Dual core CPU running 16.04.06 LTS, it installed linux 4.4.0-145. If I boot this kernel everything is blank. Just a black screen. If I change to a terminal using Ctrl Alt F4 it is still a black screen but I can carefully type in my user name and password and then the shutdown command and it shuts down Using Advanced options in grub neither the upstart or the recovery option work. The screen is still black. The recovery option does, however, display the boot sequence before going black. I can boot the previous kernel 4.4.0-143 and all is OK. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824641/+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 1824641] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1824641 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1824641 Title: Blank screen after booting 4.4.0-145 Status in linux package in Ubuntu: Incomplete Status in mutter package in Ubuntu: New Bug description: Having run update on my i386 Asus Eee PC with Intel Atom N550 Dual core CPU running 16.04.06 LTS, it installed linux 4.4.0-145. If I boot this kernel everything is blank. Just a black screen. If I change to a terminal using Ctrl Alt F4 it is still a black screen but I can carefully type in my user name and password and then the shutdown command and it shuts down Using Advanced options in grub neither the upstart or the recovery option work. The screen is still black. The recovery option does, however, display the boot sequence before going black. I can boot the previous kernel 4.4.0-143 and all is OK. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824641/+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 1824642] 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/1824642 Title: nvidia card disabled after upgrading to 5.0.0-11-generic Status in linux package in Ubuntu: Confirmed Bug description: After upgrading from 5.0.0.8-generic to 5.0.0.11-generic, the nvidia card suddenly became "disabled". I own a laptop with hybrid GPU stack, intel + nvidia; nvidia is in charge of display ports. On 5.0.0.8-generic I had only nvidia GPU enabled (discrete mode) and nouveau was able to properly control nvidia and send the signal to my monitor. In hybrid mode this worked as well properly. On 5.0.0.11-generic in discrete mode, linux booted to 640x480 resolution only. When I enabled hybrid mode back, the computer boots into 1920x1200 mode properly, however the display port ports don't work at all, and the "About" screen only lists the Intel GPU, not nvidia. lspci still lists nvidia though. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-11-generic 5.0.0-11.12 ProcVersionSignature: Ubuntu 5.0.0-11.12-generic 5.0.6 Uname: Linux 5.0.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mavi 2324 F pulseaudio /dev/snd/controlC1: mavi 2324 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Apr 13 20:09:25 2019 HibernationDevice: RESUME=/dev/mapper/vg0-lv0--swap InstallationDate: Installed on 2016-09-05 (950 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: LENOVO 20EN0005MS ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-11-generic root=/dev/mapper/vg0-lv1--root ro splash ipv6.disable=1 vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.0.0-11-generic N/A linux-backports-modules-5.0.0-11-generic N/A linux-firmware1.178 SourcePackage: linux UpgradeStatus: Upgraded to disco on 2019-03-12 (32 days ago) dmi.bios.date: 02/21/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N1EET83W (1.56 ) dmi.board.asset.tag: Not Available dmi.board.name: 20EN0005MS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1EET83W(1.56):bd02/21/2019:svnLENOVO:pn20EN0005MS:pvrThinkPadP50:rvnLENOVO:rn20EN0005MS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P50 dmi.product.name: 20EN0005MS dmi.product.sku: LENOVO_MT_20EN_BU_Think_FM_ThinkPad P50 dmi.product.version: ThinkPad P50 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824642/+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 1824642] Re: nvidia card disabled after upgrading to 5.0.0-11-generic
Just rebooted to 5.0.0-8, to rule out hardware failure. Under 5.0.0-8 nouveau+nvidia works flawlessly, under 5.0.0-11 nvidia card seem to be completely ignored by Linux, both in "hybrid" and "discrete" laptop mode. -- 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/1824642 Title: nvidia card disabled after upgrading to 5.0.0-11-generic Status in linux package in Ubuntu: Confirmed Bug description: After upgrading from 5.0.0.8-generic to 5.0.0.11-generic, the nvidia card suddenly became "disabled". I own a laptop with hybrid GPU stack, intel + nvidia; nvidia is in charge of display ports. On 5.0.0.8-generic I had only nvidia GPU enabled (discrete mode) and nouveau was able to properly control nvidia and send the signal to my monitor. In hybrid mode this worked as well properly. On 5.0.0.11-generic in discrete mode, linux booted to 640x480 resolution only. When I enabled hybrid mode back, the computer boots into 1920x1200 mode properly, however the display port ports don't work at all, and the "About" screen only lists the Intel GPU, not nvidia. lspci still lists nvidia though. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-11-generic 5.0.0-11.12 ProcVersionSignature: Ubuntu 5.0.0-11.12-generic 5.0.6 Uname: Linux 5.0.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mavi 2324 F pulseaudio /dev/snd/controlC1: mavi 2324 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Apr 13 20:09:25 2019 HibernationDevice: RESUME=/dev/mapper/vg0-lv0--swap InstallationDate: Installed on 2016-09-05 (950 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: LENOVO 20EN0005MS ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-11-generic root=/dev/mapper/vg0-lv1--root ro splash ipv6.disable=1 vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.0.0-11-generic N/A linux-backports-modules-5.0.0-11-generic N/A linux-firmware1.178 SourcePackage: linux UpgradeStatus: Upgraded to disco on 2019-03-12 (32 days ago) dmi.bios.date: 02/21/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N1EET83W (1.56 ) dmi.board.asset.tag: Not Available dmi.board.name: 20EN0005MS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1EET83W(1.56):bd02/21/2019:svnLENOVO:pn20EN0005MS:pvrThinkPadP50:rvnLENOVO:rn20EN0005MS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P50 dmi.product.name: 20EN0005MS dmi.product.sku: LENOVO_MT_20EN_BU_Think_FM_ThinkPad P50 dmi.product.version: ThinkPad P50 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824642/+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 1824641] Re: Blank screen after booting 4.4.0-145
Please not that Launchpad has automatically assigned this bug to mutter, but mutter is not installed on the notebook in question, so I have added linux ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1824641 Title: Blank screen after booting 4.4.0-145 Status in linux package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: Having run update on my i386 Asus Eee PC with Intel Atom N550 Dual core CPU running 16.04.06 LTS, it installed linux 4.4.0-145. If I boot this kernel everything is blank. Just a black screen. If I change to a terminal using Ctrl Alt F4 it is still a black screen but I can carefully type in my user name and password and then the shutdown command and it shuts down Using Advanced options in grub neither the upstart or the recovery option work. The screen is still black. The recovery option does, however, display the boot sequence before going black. I can boot the previous kernel 4.4.0-143 and all is OK. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824641/+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 1824642] [NEW] nvidia card disabled after upgrading to 5.0.0-11-generic
Public bug reported: After upgrading from 5.0.0.8-generic to 5.0.0.11-generic, the nvidia card suddenly became "disabled". I own a laptop with hybrid GPU stack, intel + nvidia; nvidia is in charge of display ports. On 5.0.0.8-generic I had only nvidia GPU enabled (discrete mode) and nouveau was able to properly control nvidia and send the signal to my monitor. In hybrid mode this worked as well properly. On 5.0.0.11-generic in discrete mode, linux booted to 640x480 resolution only. When I enabled hybrid mode back, the computer boots into 1920x1200 mode properly, however the display port ports don't work at all, and the "About" screen only lists the Intel GPU, not nvidia. lspci still lists nvidia though. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-11-generic 5.0.0-11.12 ProcVersionSignature: Ubuntu 5.0.0-11.12-generic 5.0.6 Uname: Linux 5.0.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mavi 2324 F pulseaudio /dev/snd/controlC1: mavi 2324 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Apr 13 20:09:25 2019 HibernationDevice: RESUME=/dev/mapper/vg0-lv0--swap InstallationDate: Installed on 2016-09-05 (950 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: LENOVO 20EN0005MS ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-11-generic root=/dev/mapper/vg0-lv1--root ro splash ipv6.disable=1 vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.0.0-11-generic N/A linux-backports-modules-5.0.0-11-generic N/A linux-firmware1.178 SourcePackage: linux UpgradeStatus: Upgraded to disco on 2019-03-12 (32 days ago) dmi.bios.date: 02/21/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N1EET83W (1.56 ) dmi.board.asset.tag: Not Available dmi.board.name: 20EN0005MS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1EET83W(1.56):bd02/21/2019:svnLENOVO:pn20EN0005MS:pvrThinkPadP50:rvnLENOVO:rn20EN0005MS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P50 dmi.product.name: 20EN0005MS dmi.product.sku: LENOVO_MT_20EN_BU_Think_FM_ThinkPad P50 dmi.product.version: ThinkPad P50 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco -- 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/1824642 Title: nvidia card disabled after upgrading to 5.0.0-11-generic Status in linux package in Ubuntu: New Bug description: After upgrading from 5.0.0.8-generic to 5.0.0.11-generic, the nvidia card suddenly became "disabled". I own a laptop with hybrid GPU stack, intel + nvidia; nvidia is in charge of display ports. On 5.0.0.8-generic I had only nvidia GPU enabled (discrete mode) and nouveau was able to properly control nvidia and send the signal to my monitor. In hybrid mode this worked as well properly. On 5.0.0.11-generic in discrete mode, linux booted to 640x480 resolution only. When I enabled hybrid mode back, the computer boots into 1920x1200 mode properly, however the display port ports don't work at all, and the "About" screen only lists the Intel GPU, not nvidia. lspci still lists nvidia though. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-11-generic 5.0.0-11.12 ProcVersionSignature: Ubuntu 5.0.0-11.12-generic 5.0.6 Uname: Linux 5.0.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mavi 2324 F pulseaudio /dev/snd/controlC1: mavi 2324 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Apr 13 20:09:25 2019 HibernationDevice: RESUME=/dev/mapper/vg0-lv0--swap InstallationDate: Installed on 2016-09-05 (950 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: LENOVO 20EN0005MS ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-11-generic root=/dev/mapper/vg0-lv1--root ro splash ipv6.disable=1 vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.0.0-11-generic N/A linux-backports-modules-5.0.0-11-generic N/A linux-firmware1.178 SourcePackage: linux UpgradeStatus: Upgraded to disco on 2019-03-12 (32 days ago) dmi.bios.date: 02/21/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N1EET83W (1.56 ) dmi.board.asset.tag: Not Available dmi.board.name: 20EN0005MS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information
[Kernel-packages] [Bug 1823029] Re: [Dell XPS 15 9575] Occasionally fails to suspend and locks up instead
Please test this kernel: https://people.canonical.com/~khfeng/lp1823029/ -- 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/1823029 Title: [Dell XPS 15 9575] Occasionally fails to suspend and locks up instead Status in linux package in Ubuntu: Confirmed Bug description: Sometimes when suspending, the suspend process fails, and the machine becomes unresponsive to any input, has nothing but a black/off display, and fans kick in and run high (which is actually 'good' for detecting the issue has happened). journalctl output from an unsuccessful suspend: Apr 02 13:39:54 taplop systemd-logind[1067]: Suspending... Apr 02 13:39:54 taplop NetworkManager[4083]: [1554237594.5332] manager: sleep: sleep requested (sleeping: no en Apr 02 13:39:54 taplop NetworkManager[4083]: [1554237594.5333] device (40:4E:36:47:ED:D1): state change: disconn Apr 02 13:39:54 taplop NetworkManager[4083]: [1554237594.5358] manager: NetworkManager state is now ASLEEP Apr 02 13:39:54 taplop whoopsie[1779]: [13:39:54] offline Apr 02 13:39:55 taplop gnome-shell[5521]: Failed to flip onscreen: Tried to flip inactive CRTC Apr 02 13:39:56 taplop kernel: [drm] PCIE GART of 256M enabled (table at 0x00F4). Apr 02 13:39:56 taplop kernel: [drm] UVD and UVD ENC initialized successfully. Apr 02 13:39:56 taplop kernel: [drm] VCE initialized successfully. Apr 02 13:39:57 taplop systemd[1]: Starting TLP suspend/resume... Apr 02 13:39:57 taplop systemd[1]: Started TLP suspend/resume. Apr 02 13:39:57 taplop systemd[1]: Reached target Sleep. Apr 02 13:39:57 taplop systemd[1]: Starting Suspend... Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9078] caught SIGTERM, shutting down normally. Apr 02 13:39:57 taplop systemd[1]: Stopping Network Manager... Apr 02 13:39:57 taplop gnome-shell[5521]: Removing a network device that was not added Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9485] dhcp4 (wlp2s0): canceled DHCP transaction, DHCP c Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9486] dhcp4 (wlp2s0): state changed bound -> done Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9486] device (wlp2s0): DHCPv4: 480 seconds grace period Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9570] exiting (success) Apr 02 13:39:57 taplop gnome-shell[5521]: JS WARNING: [resource:///org/gnome/shell/ui/status/network.js 1187]: reference Apr 02 13:39:57 taplop systemd[1]: NetworkManager.service: Succeeded. Apr 02 13:39:57 taplop systemd[1]: Stopped Network Manager. Apr 02 13:39:57 taplop gnome-shell[5521]: Object NM.ActiveConnection (0x55d340e8f5a0), has been already deallocated — im Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: == Stack trace for context 0x55d34160e1e0 == Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: #0 55d345364700 i resource:///org/gnome/shell/ui/status/networ Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: #1 55d345364680 i resource:///org/gnome/shell/ui/status/networ Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: #2 7ffe97451d00 b self-hosted:979 (7fc3d4350a60 @ 440) Apr 02 13:39:58 taplop gnome-shell[5521]: Failed to flip onscreen: Tried to flip inactive CRTC Apr 02 13:39:58 taplop kernel: wlp2s0: deauthenticating from f0:9f:c2:6e:e1:aa by local choice (Reason: 3=DEAUTH_LEAVING Apr 02 13:39:58 taplop wpa_supplicant[1069]: wlp2s0: CTRL-EVENT-DISCONNECTED bssid=f0:9f:c2:6e:e1:aa reason=3 locally_ge Apr 02 13:39:58 taplop gnome-shell[5521]: Failed to flip onscreen: Tried to flip inactive CRTC Apr 02 13:39:58 taplop avahi-daemon[1068]: Interface wlp2s0.IPv6 no longer relevant for mDNS. Apr 02 13:39:58 taplop avahi-daemon[1068]: Leaving mDNS multicast group on interface wlp2s0.IPv6 with address fe80::1c45 Apr 02 13:39:58 taplop whoopsie[1779]: [13:39:58] Cannot reach: https://daisy.ubuntu.com Apr 02 13:39:58 taplop whoopsie[1779]: [13:39:58] Cannot reach: https://daisy.ubuntu.com Apr 02 13:39:58 taplop avahi-daemon[1068]: Interface wlp2s0.IPv4 no longer relevant for mDNS. Apr 02 13:39:58 taplop avahi-daemon[1068]: Leaving mDNS multicast group on interface wlp2s0.IPv4 with address 10.30.2.26 Apr 02 13:39:58 taplop avahi-daemon[1068]: Withdrawing address record for fe80::1c45:b634:dc94:8f5f on wlp2s0. Apr 02 13:39:58 taplop avahi-daemon[1068]: Withdrawing address record for 10.30.2.26 on wlp2s0. Apr 02 13:39:58 taplop wpa_supplicant[1069]: nl80211: deinit ifname=p2p-dev-wlp2s0 disabled_11b_rates=0 Apr 02 13:39:58 taplop wpa_supplicant[1069]: Could not read interface p2p-dev-wlp2s0 flags: No such device Apr 02 13:39:58 taplop systemd-sleep[9790]: Suspending system... Apr 02 13:39:58 taplop kernel: PM: suspend entry (deep) Apr 02 13:39:59 taplop kernel: PM: Syncing filesystems ... done. Apr 02 13:39:59
[Kernel-packages] [Bug 1823346] Re: SD card stays locked even when unlocked
This may be a regression introduced by this commit: commit 20bd1d026aacc5399464f8328f305985c493cde3 Author: Jeremy Cline Date: Tue Mar 6 21:47:32 2018 + scsi: sd: Keep disk read-only when re-reading partition If the read-only flag is true on a SCSI disk, re-reading the partition table sets the flag back to false. To observe this bug, you can run: 1. blockdev --setro /dev/sda 2. blockdev --rereadpt /dev/sda 3. blockdev --getro /dev/sda This commit reads the disk's old state and combines it with the device disk-reported state rather than unconditionally marking it as RW. Reported-by: Li Ning Signed-off-by: Jeremy Cline Signed-off-by: Martin K. Petersen -- 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/1823346 Title: SD card stays locked even when unlocked Status in linux package in Ubuntu: Confirmed Bug description: Description:Ubuntu 18.04.2 LTS Release:18.04 After card reader device is used with write-protected SD card, write- protection incorrectly persists to future SD cards, even non-protected ones. To reproduce: 1) Insert non-protected SD card in card reader (confirm system normal): $ sudo hdparm -r /dev/sdd /dev/sdd: readonly = 0 (off) [result is correct] 2) Eject card, set physical lock on side of card, reinsert: $ sudo hdparm -r /dev/sdd /dev/sdd: readonly = 1 (on) [result is correct - card read-only] 3) Eject card again, unlock card, reinsert $ sudo hdparm -r /dev/sdd /dev/sdd: readonly = 1 (on) [result is **incorrect** (card still locked)] Because the lock is still set, the device always appears read-only. (For example, I cannot "dd" to /dev/sdd) Workaround: after removing the locked card, issue "sudo hdparm -r0" to turn off the lock. Then insert the unlocked card and the device will appear read/write. (I don't know if this is the right package to report against.) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: udisks2 2.7.6-3ubuntu0.2 ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: XFCE CustomUdevRuleFiles: 69-basler-cameras.rules 99-realsense-libusb.rules Date: Fri Apr 5 14:50:32 2019 InstallationDate: Installed on 2016-09-28 (919 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Hewlett-Packard HP Z620 Workstation ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic root=UUID=1a9272d2-8838-4bb4-8f63-ce571641c48c ro quiet splash vt.handoff=1 SourcePackage: udisks2 Symptom: storage Title: No permission to access files on storage device UpgradeStatus: Upgraded to bionic on 2019-01-14 (81 days ago) dmi.bios.date: 05/27/2015 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: J61 v03.88 dmi.board.asset.tag: CZC4086C7Q dmi.board.name: 158A dmi.board.vendor: Hewlett-Packard dmi.board.version: 0.00 dmi.chassis.asset.tag: CZC4086C7Q dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrJ61v03.88:bd05/27/2015:svnHewlett-Packard:pnHPZ620Workstation:pvr:rvnHewlett-Packard:rn158A:rvr0.00:cvnHewlett-Packard:ct6:cvr: dmi.product.family: 103C_53335X G=D dmi.product.name: HP Z620 Workstation dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823346/+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 1823346] Re: SD card stays locked even when unlocked
Please see if this issue doesn't happen on kernel version < Ubuntu-4.15.0-33.36. -- 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/1823346 Title: SD card stays locked even when unlocked Status in linux package in Ubuntu: Confirmed Bug description: Description:Ubuntu 18.04.2 LTS Release:18.04 After card reader device is used with write-protected SD card, write- protection incorrectly persists to future SD cards, even non-protected ones. To reproduce: 1) Insert non-protected SD card in card reader (confirm system normal): $ sudo hdparm -r /dev/sdd /dev/sdd: readonly = 0 (off) [result is correct] 2) Eject card, set physical lock on side of card, reinsert: $ sudo hdparm -r /dev/sdd /dev/sdd: readonly = 1 (on) [result is correct - card read-only] 3) Eject card again, unlock card, reinsert $ sudo hdparm -r /dev/sdd /dev/sdd: readonly = 1 (on) [result is **incorrect** (card still locked)] Because the lock is still set, the device always appears read-only. (For example, I cannot "dd" to /dev/sdd) Workaround: after removing the locked card, issue "sudo hdparm -r0" to turn off the lock. Then insert the unlocked card and the device will appear read/write. (I don't know if this is the right package to report against.) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: udisks2 2.7.6-3ubuntu0.2 ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: XFCE CustomUdevRuleFiles: 69-basler-cameras.rules 99-realsense-libusb.rules Date: Fri Apr 5 14:50:32 2019 InstallationDate: Installed on 2016-09-28 (919 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Hewlett-Packard HP Z620 Workstation ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic root=UUID=1a9272d2-8838-4bb4-8f63-ce571641c48c ro quiet splash vt.handoff=1 SourcePackage: udisks2 Symptom: storage Title: No permission to access files on storage device UpgradeStatus: Upgraded to bionic on 2019-01-14 (81 days ago) dmi.bios.date: 05/27/2015 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: J61 v03.88 dmi.board.asset.tag: CZC4086C7Q dmi.board.name: 158A dmi.board.vendor: Hewlett-Packard dmi.board.version: 0.00 dmi.chassis.asset.tag: CZC4086C7Q dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrJ61v03.88:bd05/27/2015:svnHewlett-Packard:pnHPZ620Workstation:pvr:rvnHewlett-Packard:rn158A:rvr0.00:cvnHewlett-Packard:ct6:cvr: dmi.product.family: 103C_53335X G=D dmi.product.name: HP Z620 Workstation dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823346/+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 1824632] Re: Linux 5 regression causes no video out on some laptops in 19.04 beta
Cannot run apport-collect against linux, dpkg-query reports no packages found matching linux ** 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/1824632 Title: Linux 5 regression causes no video out on some laptops in 19.04 beta Status in linux package in Ubuntu: Confirmed Bug description: There is a known regression in the v5 kernel that causes laptop video to fail on some panels. I can attest this happens on a Dell XPS 15 2-in-1 (9575) and wanted to give a heads up as this affects the current 19.04 beta. Upstream tracking is here: https://bugs.freedesktop.org/show_bug.cgi?id=109959 With a patch here: https://patchwork.freedesktop.org/patch/296411/ I'm not sure what else I can include that was not already covered in those reports and tracking, but will do anything I can. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824632/+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 1824632] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1824632 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1824632 Title: Linux 5 regression causes no video out on some laptops in 19.04 beta Status in linux package in Ubuntu: Incomplete Bug description: There is a known regression in the v5 kernel that causes laptop video to fail on some panels. I can attest this happens on a Dell XPS 15 2-in-1 (9575) and wanted to give a heads up as this affects the current 19.04 beta. Upstream tracking is here: https://bugs.freedesktop.org/show_bug.cgi?id=109959 With a patch here: https://patchwork.freedesktop.org/patch/296411/ I'm not sure what else I can include that was not already covered in those reports and tracking, but will do anything I can. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824632/+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 1824632] Re: Linux 5 regression causes no video out on some laptops in 19.04 beta
** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1824632 Title: Linux 5 regression causes no video out on some laptops in 19.04 beta Status in linux package in Ubuntu: Incomplete Bug description: There is a known regression in the v5 kernel that causes laptop video to fail on some panels. I can attest this happens on a Dell XPS 15 2-in-1 (9575) and wanted to give a heads up as this affects the current 19.04 beta. Upstream tracking is here: https://bugs.freedesktop.org/show_bug.cgi?id=109959 With a patch here: https://patchwork.freedesktop.org/patch/296411/ I'm not sure what else I can include that was not already covered in those reports and tracking, but will do anything I can. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824632/+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 1824632] [NEW] Linux 5 regression causes no video out on some laptops in 19.04 beta
You have been subscribed to a public bug: There is a known regression in the v5 kernel that causes laptop video to fail on some panels. I can attest this happens on a Dell XPS 15 2-in-1 (9575) and wanted to give a heads up as this affects the current 19.04 beta. Upstream tracking is here: https://bugs.freedesktop.org/show_bug.cgi?id=109959 With a patch here: https://patchwork.freedesktop.org/patch/296411/ I'm not sure what else I can include that was not already covered in those reports and tracking, but will do anything I can. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment disco -- Linux 5 regression causes no video out on some laptops in 19.04 beta https://bugs.launchpad.net/bugs/1824632 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1776563]
Manjaro 5.0.2 kernel here. As i reported before most of my bootings w\o any kernel parameters are fine, but today i found out that my 2500u won't boost any further 2.0ghz. Idk whether it caused by sleep or my cpu was like that right after boot sequence. I used to write ivrs_table argument with 4.20 kernel and then sleep\hibernation went off, but CPU were boosting up to 3.6 ghz as supposed to. -- 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/1776563 Title: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash Status in amd: Fix Released Status in Linux: Incomplete Status in linux package in Ubuntu: Triaged Bug description: CPU: Ryzen 5 2500U VGA: Radeon 535 Notebook: Acer Aspire A315 This is a brand new notebook on the market with Ryzen 5/Radeon. The default kernel of Ubuntu(18.04) hangs at loading with message: tsc: Refined TSC clocksource calibration: 1996.250 MHz clocksource: tsc: mask: 0x max_cycles: (...), max_idle_ns: (...) Soft lockup Using pci=noacpi kernel parameter kernel loads without any problem but my notebook produces more heat than on Win10. If I know right Acer notebooks need ACPI to the correct power management. The same thing happens on mainline 4.17,4.18rc1-2. BIOS upgrade to the latest version: 1.08 hasn't helped This problem has been reported upstream: https://bugzilla.kernel.org/show_bug.cgi?id=200087 The latest correctly working kernel was 4.13.* but the heat problem was present with this too. To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1776563/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1776563]
tl;dr even if it would be possible to boot without any tricks in kernel arguments some features of cpu would still be borken -- 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/1776563 Title: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash Status in amd: Fix Released Status in Linux: Incomplete Status in linux package in Ubuntu: Triaged Bug description: CPU: Ryzen 5 2500U VGA: Radeon 535 Notebook: Acer Aspire A315 This is a brand new notebook on the market with Ryzen 5/Radeon. The default kernel of Ubuntu(18.04) hangs at loading with message: tsc: Refined TSC clocksource calibration: 1996.250 MHz clocksource: tsc: mask: 0x max_cycles: (...), max_idle_ns: (...) Soft lockup Using pci=noacpi kernel parameter kernel loads without any problem but my notebook produces more heat than on Win10. If I know right Acer notebooks need ACPI to the correct power management. The same thing happens on mainline 4.17,4.18rc1-2. BIOS upgrade to the latest version: 1.08 hasn't helped This problem has been reported upstream: https://bugzilla.kernel.org/show_bug.cgi?id=200087 The latest correctly working kernel was 4.13.* but the heat problem was present with this too. To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1776563/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1776563]
I'm using Elementary OS 5 on Acer Aspire A315-41 with kernel 5.0.7 and the workaround indicated by Erik (#156). After the workaround everything worked well but noticed a strong battery drain. Installed tlp, restarted the machine and the battery lasts around twice as much, comparable to a windows machine. I can say it solved the battery issue for me. -- 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/1776563 Title: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash Status in amd: Fix Released Status in Linux: Incomplete Status in linux package in Ubuntu: Triaged Bug description: CPU: Ryzen 5 2500U VGA: Radeon 535 Notebook: Acer Aspire A315 This is a brand new notebook on the market with Ryzen 5/Radeon. The default kernel of Ubuntu(18.04) hangs at loading with message: tsc: Refined TSC clocksource calibration: 1996.250 MHz clocksource: tsc: mask: 0x max_cycles: (...), max_idle_ns: (...) Soft lockup Using pci=noacpi kernel parameter kernel loads without any problem but my notebook produces more heat than on Win10. If I know right Acer notebooks need ACPI to the correct power management. The same thing happens on mainline 4.17,4.18rc1-2. BIOS upgrade to the latest version: 1.08 hasn't helped This problem has been reported upstream: https://bugzilla.kernel.org/show_bug.cgi?id=200087 The latest correctly working kernel was 4.13.* but the heat problem was present with this too. To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1776563/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1813537] Re: Wifi + bluetooth adapters are gone after sleep/wake
Hmm, as I recall XPS 9360 should support UEFI capsule update. Need help from Mario here. [0.00] DMI: Dell Inc. XPS 13 9360/0T3FTF, BIOS 1.3.2 01/18/2017 BIOS 2.10 here: https://www.dell.com/support/home/us/en/19/drivers/driversdetails?driverid=t7xjf=biosa=xps-13-9360-laptop -- 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/1813537 Title: Wifi + bluetooth adapters are gone after sleep/wake Status in linux package in Ubuntu: Confirmed Bug description: the only fix I found was to power down and power back on. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-44-generic 4.15.0-44.47 ProcVersionSignature: Ubuntu 4.15.0-44.47-generic 4.15.18 Uname: Linux 4.15.0-44-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: uri2238 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Jan 28 11:15:43 2019 HibernationDevice: RESUME=UUID=c88d6aec-cb91-4ff5-a406-52c6187e06a5 InstallationDate: Installed on 2018-01-13 (380 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) MachineType: Dell Inc. XPS 13 9360 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-44-generic root=UUID=dc909762-dd6b-4c9c-84da-f8e16a647a3f ro nouveau.modeset=0 quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-44-generic N/A linux-backports-modules-4.15.0-44-generic N/A linux-firmware 1.173.3 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: 0T3FTF 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.:rn0T3FTF:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS 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/1813537/+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 1743908] Re: MODSIGN: Couldn't get UEFI db list
Present on 19.04 Disco Dingo with kernel: Linux 5.0.0-11-generic #12-Ubuntu SMP Thu Apr 11 16:41:13 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux Errors in dmesg show: [1.116542] Loading compiled-in X.509 certificates [1.117339] Loaded X.509 cert 'Build time autogenerated kernel key: x' [1.117966] Couldn't get size: 0x800e [1.117968] MODSIGN: Couldn't get UEFI db list [1.118307] Couldn't get size: 0x800e [1.118307] MODSIGN: Couldn't get UEFI MokListRT [1.118661] Couldn't get size: 0x800e [1.118661] MODSIGN: Couldn't get UEFI dbx list [1.118685] zswap: loaded using pool lzo/zbud Also seeing this further down: [5.538136] cfg80211: Loaded X.509 cert 'sforshee: ' [5.546340] PKCS#7 signature not signed with a trusted key [5.546348] razerkbd: loading out-of-tree module taints kernel. [5.546563] PKCS#7 signature not signed with a trusted key [5.553517] PKCS#7 signature not signed with a trusted key [5.612458] PKCS#7 signature not signed with a trusted key [5.612471] nvidia: module license 'NVIDIA' taints kernel. [5.612472] Disabling lock debugging due to kernel taint and: [5.721288] iwlwifi :03:00.0: base HW address: blah blah blah [5.725326] PKCS#7 signature not signed with a trusted key [5.733135] NVRM: loading NVIDIA UNIX x86_64 Kernel Module 418.56 Fri Mar 15 12:59:26 CDT 2019 [5.738319] PKCS#7 signature not signed with a trusted key [5.738401] PKCS#7 signature not signed with a trusted key [5.739168] nvidia-modeset: Loading NVIDIA Kernel Mode Setting Driver for UNIX platforms 418.56 Fri Mar 15 12:32:40 CDT 2019 [5.739843] PKCS#7 signature not signed with a trusted key [5.740612] PKCS#7 signature not signed with a trusted key [5.740786] [drm] [nvidia-drm] [GPU ID 0x0100] Loading driver [5.740787] [drm] Initialized nvidia-drm 0.0.0 20160202 for :01:00.0 on minor 0 [5.746905] PKCS#7 signature not signed with a trusted key [5.748945] nvidia-uvm: Loaded the UVM driver in 8 mode, major device number 509 and: [ 12.040933] PKCS#7 signature not signed with a trusted key [ 12.046672] vboxdrv: Found 12 processor cores [ 12.064917] vboxdrv: TSC mode is Invariant, tentative frequency 369693 Hz [ 12.064917] vboxdrv: Successfully loaded version 6.0.4_Ubuntu (interface 0x00290008) [ 12.068244] PKCS#7 signature not signed with a trusted key [ 12.068449] VBoxNetFlt: Successfully started. [ 12.071204] PKCS#7 signature not signed with a trusted key [ 12.071325] VBoxNetAdp: Successfully started. [ 12.074109] PKCS#7 signature not signed with a trusted key [ 12.074463] VBoxPciLinuxInit -- 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/1743908 Title: MODSIGN: Couldn't get UEFI db list Status in linux package in Ubuntu: Fix Released Bug description: Kernel is having problem loading or validating certificates. Looking over the internet looks like this is a kernel issue. Patchs from other distro: https://bugzilla.redhat.com/show_bug.cgi?id=1497559 - 0001-Make-get_cert_list-not-complain-about-cert-lists-tha.patch - 0002-Add-efi_status_to_str-and-rework-efi_status_to_err.patch - 0003-Make-get_cert_list-use-efi_status_to_str-to-print-er.patch [1.203191] Loaded X.509 cert 'Build time autogenerated kernel key: ecdf0c3ef21a8b4ca325a4d1db7d45108ca78734' [1.203352] Couldn't get size: 0x800e [1.203354] MODSIGN: Couldn't get UEFI db list [1.205030] Loaded UEFI:MokListRT cert 'Canonical Ltd. Master Certificate Authority: ad91990bc22ab1f517048c23b6655a268e345a63' linked to secondary sys keyring [1.205102] Couldn't get size: 0x800e [1.205103] MODSIGN: Couldn't get UEFI dbx list ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-25-generic 4.13.0-25.29 ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13 Uname: Linux 4.13.0-25-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: wellington 1429 F pulseaudio /dev/snd/pcmC1D3p: wellington 1429 F...m pulseaudio /dev/snd/controlC1: wellington 1429 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Jan 17 22:37:13 2018 HibernationDevice: RESUME=UUID=192fbe7e-0dbf-47fc-8277-75569f69f16e InstallationDate: Installed on 2018-01-16 (1 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) IwConfig: lono wireless extensions. enp7s0no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-25-generic.efi.signed
[Kernel-packages] [Bug 1778087] Re: ELAN1200 touchpad jumps around and disconnects
Please test this kernel: https://people.canonical.com/~khfeng/lp1778087-pinctrl/ -- 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/1778087 Title: ELAN1200 touchpad jumps around and disconnects Status in linux package in Ubuntu: Confirmed Bug description: This is on an ASUS GL503VD laptop and would probably affect other ASUS laptops equipped with the ELAN1200 touchpad. I am on Kernel 4.17.2 because older kernels did not enable the touchpad at all(It was just unrecognized or i2c-hid stopped the computer from booting) The touchpad works but it has erratic behaviour and disconnects randomly. After it disconnects the only way to bring it back is to `modprobe -r hid-multitouch && modprobe hid-multitouch` Libinput and synaptics can handle the touchpad though I found synaptics to be more stable. dmesg gets spammed with this whenever I move the touchpad: [timestamp] i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535) I tried to compile: https://github.com/mishurov/linux_elan1200_touchpad Because from what I understand the "jumpy/disconnect" problem is associated to the incomplete reports and Mishurov managed to mitigate those. Unfortunately some symbols were deprecated in kernel 4.17.2 and it did not compile for my system. While I can use my touchpad as is right now, and "restart" it with modprobe when needed, it would be nice to have it function bug-free. (Right after I typed this my touchpad disconnected and I needed to modprobe again, I am considering making a cronjob for that) Let me know if anything else is needed. Will wait for an apport collection to add log files. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-06-10 (11 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash Tags: bionic Uname: Linux 4.17.2 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/1778087/+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 1810416] Re: SD card error mmc0: error -110 whilst initialising SD card
For anyone experiencing this issue with a Realtek RTL8411 card reader: 04:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTL8411B PCI Express Card Reader (rev 01) Subsystem: CLEVO/KAPOK Computer RTL8411B PCI Express Card Reader Flags: bus master, fast devsel, latency 0, IRQ 19 Memory at a4215000 (32-bit, non-prefetchable) [size=4K] Expansion ROM at a420 [disabled] [size=64K] Capabilities: Kernel driver in use: rtsx_pci Kernel modules: rtsx_pci the out-of-tree rts_bpp module appears to work fine with kernel version 4.15.0-47: https://github.com/Ri0n/rts_bpp -- 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/1810416 Title: SD card error mmc0: error -110 whilst initialising SD card Status in linux package in Ubuntu: Confirmed Bug description: When inserting card to internal card reader: laurynas@laurynas-ThinkPad-T450:~$ dmesg [342809.333716] mmc0: error -110 whilst initialising SD card laurynas@laurynas-ThinkPad-T450:~$ uname -a Linux laurynas-ThinkPad-T450 4.15.0-43-generic #46-Ubuntu SMP Thu Dec 6 14:45:28 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux SanDisk Extreme 64GB UHS 3. Working fine on windows 10. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-43-generic 4.15.0-43.46 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: laurynas 3963 F pulseaudio /dev/snd/controlC0: laurynas 3963 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Jan 3 16:09:26 2019 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=6d87ff4e-c0ef-4f84-a96e-19a22e4acce4 InstallationDate: Installed on 2017-02-18 (683 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: LENOVO 20BUS3GN07 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=a0b409bc-4664-443b-b5be-7941f78d50a8 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.173.2 SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-10-04 (90 days ago) dmi.bios.date: 02/27/2018 dmi.bios.vendor: LENOVO dmi.bios.version: JBET68WW (1.32 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BUS3GN07 dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET68WW(1.32):bd02/27/2018:svnLENOVO:pn20BUS3GN07:pvrThinkPadT450:rvnLENOVO:rn20BUS3GN07:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T450 dmi.product.name: 20BUS3GN07 dmi.product.version: ThinkPad T450 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810416/+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 1824378] Re: linux-kvm: 5.0.0-1003.3 -proposed tracker
All tasks have been completed and the bug is being set to Fix Released ** Changed in: kernel-sru-workflow/promote-to-release Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow Status: In Progress => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1824383 phase: Ready for Release phase-changed: Saturday, 13. April 2019 12:43 UTC proposed-announcement-sent: true proposed-testing-requested: true - reason: - promote-to-release: Pending -- ready to copy ** Tags removed: kernel-release-tracking-bug-live -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1824378 Title: linux-kvm: 5.0.0-1003.3 -proposed tracker Status in Kernel SRU Workflow: Fix Released Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-release series: Fix Released Status in Kernel SRU Workflow regression-testing series: Fix Released Status in linux-kvm package in Ubuntu: Fix Released Status in linux-kvm source package in Disco: Fix Released Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1824383 phase: Ready for Release phase-changed: Saturday, 13. April 2019 12:43 UTC proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1824378/+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 1824378] Re: linux-kvm: 5.0.0-1003.3 -proposed tracker
This bug was fixed in the package linux-kvm - 5.0.0-1003.3 --- linux-kvm (5.0.0-1003.3) disco; urgency=medium * linux-kvm: 5.0.0-1003.3 -proposed tracker (LP: #1824378) [ Ubuntu: 5.0.0-11.12 ] * linux: 5.0.0-11.12 -proposed tracker (LP: #1824383) * hns3: PPU_PF_ABNORMAL_INT_ST over_8bd_no_fe found [error status=0x1] (LP: #1824194) - net: hns3: fix for not calculating tx bd num correctly * disco: unable to use iptables/enable ufw under -virtual kernel (LP: #1823862) - [Packaging] add bpfilter to linux-modules * Make shiftfs a module rather than built-in (LP: #1824354) - [Config] CONFIG_SHIFT_FS=m * shiftfs: chown sets untranslated ids in lower fs (LP: #1824350) - SAUCE: shiftfs: use translated ids when chaning lower fs attrs * [Hyper-V] KVP daemon fails to start on first boot of disco VM (LP: #1820063) - [Packaging] bind hv_kvp_daemon startup to hv_kvp device -- Thadeu Lima de Souza Cascardo Thu, 11 Apr 2019 16:32:02 -0300 ** Changed in: linux-kvm (Ubuntu Disco) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1824378 Title: linux-kvm: 5.0.0-1003.3 -proposed tracker Status in Kernel SRU Workflow: Fix Released Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-release series: Fix Released Status in Kernel SRU Workflow regression-testing series: Fix Released Status in linux-kvm package in Ubuntu: Fix Released Status in linux-kvm source package in Disco: Fix Released Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1824383 phase: Ready for Release phase-changed: Saturday, 13. April 2019 12:43 UTC proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1824378/+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 1810416] Re: SD card error mmc0: error -110 whilst initialising SD card
Same issue here, also with a SanDisk Extreme microSD card (128GB). Possibly relevant: https://bugzilla.kernel.org/show_bug.cgi?id=202473 ** Bug watch added: Linux Kernel Bug Tracker #202473 https://bugzilla.kernel.org/show_bug.cgi?id=202473 -- 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/1810416 Title: SD card error mmc0: error -110 whilst initialising SD card Status in linux package in Ubuntu: Confirmed Bug description: When inserting card to internal card reader: laurynas@laurynas-ThinkPad-T450:~$ dmesg [342809.333716] mmc0: error -110 whilst initialising SD card laurynas@laurynas-ThinkPad-T450:~$ uname -a Linux laurynas-ThinkPad-T450 4.15.0-43-generic #46-Ubuntu SMP Thu Dec 6 14:45:28 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux SanDisk Extreme 64GB UHS 3. Working fine on windows 10. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-43-generic 4.15.0-43.46 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: laurynas 3963 F pulseaudio /dev/snd/controlC0: laurynas 3963 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Jan 3 16:09:26 2019 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=6d87ff4e-c0ef-4f84-a96e-19a22e4acce4 InstallationDate: Installed on 2017-02-18 (683 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: LENOVO 20BUS3GN07 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=a0b409bc-4664-443b-b5be-7941f78d50a8 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.173.2 SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-10-04 (90 days ago) dmi.bios.date: 02/27/2018 dmi.bios.vendor: LENOVO dmi.bios.version: JBET68WW (1.32 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BUS3GN07 dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET68WW(1.32):bd02/27/2018:svnLENOVO:pn20BUS3GN07:pvrThinkPadT450:rvnLENOVO:rn20BUS3GN07:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T450 dmi.product.name: 20BUS3GN07 dmi.product.version: ThinkPad T450 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810416/+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 1824378] Re: linux-kvm: 5.0.0-1003.3 -proposed tracker
** Tags added: regression-testing-passed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1824378 Title: linux-kvm: 5.0.0-1003.3 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-release series: Confirmed Status in Kernel SRU Workflow regression-testing series: Fix Released Status in linux-kvm package in Ubuntu: New Status in linux-kvm source package in Disco: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1824383 phase: Ready for Release phase-changed: Saturday, 13. April 2019 12:43 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-release: Pending -- ready to copy To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1824378/+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 1824378] Re: linux-kvm: 5.0.0-1003.3 -proposed tracker
** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/promote-to-release Status: New => Confirmed ** Tags removed: block-proposed-disco ** Tags removed: block-proposed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1824383 - phase: Ready for Testing - phase-changed: Friday, 12. April 2019 23:10 UTC + phase: Ready for Release + phase-changed: Saturday, 13. April 2019 12:43 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - regression-testing: Ongoing -- testing in progress + promote-to-release: Pending -- ready to copy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1824378 Title: linux-kvm: 5.0.0-1003.3 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-release series: Confirmed Status in Kernel SRU Workflow regression-testing series: Fix Released Status in linux-kvm package in Ubuntu: New Status in linux-kvm source package in Disco: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1824383 phase: Ready for Release phase-changed: Saturday, 13. April 2019 12:43 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-release: Pending -- ready to copy To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1824378/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1822363] Re: Booting hangs when USB 3.0 Etron EJ168 PCI card is detected
Kai-Heng Feng pisze: > Cherry pick the fix on top of the > current commit then we can decide it's good or bad I don't know how to do it. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1822363 Title: Booting hangs when USB 3.0 Etron EJ168 PCI card is detected Status in linux package in Ubuntu: Confirmed Bug description: I have installed Etron EJ168 PCI USB 3.0 [1B6F:7023] which briliantly works in any Windows OS (I use multiboot PC) on my Conroe865PE AGP/PCI Intel Kentsfield QX6800 system with classic BIOS (non UEFI). There are no devices connected to PCI USB card during boot. The desktop Ubuntu 18.04 kernel 4.15.0-46-generic freezes with this card during boot (see attached "photo log" with boot and grub options). I can't access/login Ubuntu or console. It was checked and confirmed on ubuntu-18.04.1-desktop-amd64.iso LIVE CD desktop (with acpi=off option too). Previously I was used and removed USB 3.0 NEC Renesas upd720200 PCI card [1033:0194], which was partially workable under my installation of Ubuntu 18.04 and Windows. It had problems from time to time with FW load from card on start and not detecting USB devices connected even if FW present. I tried and also removed USB 3.0 NEC Renesas upd720202 PCI card [1912:0015] which also was partially workable in the same way (other card bios and newer NEC chip). System was fully bootable with NEC cards. The Etron EJ168 works superb on Windows OS's with directly or with hub connections with USB devices. I can assist in any way to solve this bug as IT Professional. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822363/+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
