[Kernel-packages] [Bug 1775772] Re: Atheros Wireless ath9k random segmentation fault ath9k_cmn_rx_skb_postprocess+0x4b/0x130 [ath9k_common]
Does this still happen to latest mainline kernel v4.20-rc7? -- 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/1775772 Title: Atheros Wireless ath9k random segmentation fault ath9k_cmn_rx_skb_postprocess+0x4b/0x130 [ath9k_common] Status in linux package in Ubuntu: Triaged Bug description: Hello, I got random segmentation fault on my Wireless card Atheros QCA9565 / AR9565 here I also attached dmesg and another logs. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CRDA: global country 98: DFS-UNSET (2402 - 2472 @ 20), (N/A, 20), (N/A) (5735 - 5815 @ 20), (N/A, 23), (N/A) CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-14 (64 days ago) InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: LENOVO 20369 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic root=UUID=a14e83f1-8214-4bdd-a01d-d6cebd312997 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-23-generic N/A linux-backports-modules-4.15.0-23-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-23-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-04-27 (50 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 10/20/2014 dmi.bios.vendor: LENOVO dmi.bios.version: 9ACN29WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lancer 4A2 dmi.board.vendor: LENOVO dmi.board.version: NANANANANO DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G40-70 dmi.modalias: dmi:bvnLENOVO:bvr9ACN29WW:bd10/20/2014:svnLENOVO:pn20369:pvrLenovoG40-70:rvnLENOVO:rnLancer4A2:rvrNANANANANODPK:cvnLENOVO:ct10:cvrLenovoG40-70: dmi.product.family: IDEAPAD dmi.product.name: 20369 dmi.product.version: Lenovo G40-70 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775772/+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 1775230] Re: [TP-LINK TL-WN722N v1] Plugging USB device in causes stack traces + 100% CPU
Does this still happen to latest mainline kernel v4.20-rc7? -- 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/1775230 Title: [TP-LINK TL-WN722N v1] Plugging USB device in causes stack traces + 100% CPU Status in linux package in Ubuntu: Triaged Bug description: Hello. Running Ubuntu 18.04 (4.15.0-22-generic), after plugging my TP-LINK TL-WN722N into the USB port, the CPU usage goes to 100%, and there are multiple reports of "stack traces" in dmesg. The attached snippet repeats multiple consecutive times in the dmesg output (albeit with a different trace id). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775230/+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 1757218] Re: QCA9377 isn't being recognized sometimes
** Changed in: linux (Ubuntu) Assignee: (unassigned) => Kai-Heng Feng (kaihengfeng) -- 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/1757218 Title: QCA9377 isn't being recognized sometimes Status in linux package in Ubuntu: Confirmed Bug description: Sometimes, the Wireless Network Card QCA9377 is not recognized on boot. This caused, on prior versions, a kernel panic at boot. With Bionic, the system boots but is unable to use wireless network. On dmesg there are messages like: [2.680590] usb 1-7: new full-speed USB device number 7 using xhci_hcd [2.808640] usb 1-7: device descriptor read/64, error -71 [3.044337] usb 1-7: device descriptor read/64, error -71 [3.280064] usb 1-7: new full-speed USB device number 8 using xhci_hcd [3.408245] usb 1-7: device descriptor read/64, error -71 [3.644244] usb 1-7: device descriptor read/64, error -71 [3.752193] usb usb1-port7: attempt power cycle [4.404591] usb 1-7: new full-speed USB device number 9 using xhci_hcd [4.404904] usb 1-7: Device not responding to setup address. [4.612478] usb 1-7: Device not responding to setup address. [4.820588] usb 1-7: device not accepting address 9, error -71 [4.948591] usb 1-7: new full-speed USB device number 10 using xhci_hcd [4.949109] usb 1-7: Device not responding to setup address. [5.156893] usb 1-7: Device not responding to setup address. [5.364589] usb 1-7: device not accepting address 10, error -71 [5.364655] usb usb1-port7: unable to enumerate USB device And lspci and lsusb don't show the wireless network card. The alternative is to turn the system off. Reboot don't work and reboot to Windows 10 also don't. The system must be powered off to restore functionality. Then, on the next boot, it works properly. However, after the system is turned off, it may cause the issue again. This is not 100% consistent, but mostly it cycles between powering off and powering on the notebook as: Work -> Don't work -> Work -> Don't work On Windows 10 this doesn't happen but when happens on Ubuntu, it's possible to reboot and see the status on Windows 10 too: on Device Manager it's shown a unidentified USB device at 1-7. Sometimes, on Windows 10's Network Devices it's shown, instead of the QCA9377, from four to six different devices with generic names and Bluetooth and/or Wireless don't work. When turning Ubuntu off, there are messages that appears a few instants before the system is turned off: Mar 18 18:27:26 usuario-Lenovo-ideapad-310-14ISK kernel: [14146.403388] ath10k_pci :02:00.0: failed to install key for vdev 0 peer xx:xx:xx:xx:xx:xx: -110 Mar 18 18:27:26 usuario-Lenovo-ideapad-310-14ISK kernel: [14146.403399] wlp2s0: failed to remove key (0, xx:xx:xx:xx:xx:xx) from hardware (-110) Generally, only the second message appears (but both are recorded on kern.log). The MAC adress is the one from the router, not from the wireless card. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-12-generic 4.15.0-12.13 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: usuario1364 F pulseaudio /dev/snd/seq:usuario1258 F timidity CurrentDesktop: XFCE Date: Tue Mar 20 14:43:42 2018 HibernationDevice: RESUME=UUID=9f36068f-c6d6-4fd6-87d5-46f1f5247563 InstallationDate: Installed on 2017-06-13 (279 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: LENOVO 80UG ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic.efi.signed root=UUID=6b4ae5c0-c78c-49a6-a1ba-029192618a7a ro quiet RelatedPackageVersions: linux-restricted-modules-4.15.0-12-generic N/A linux-backports-modules-4.15.0-12-generic N/A linux-firmware 1.173 SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2017-10-20 (151 days ago) dmi.bios.date: 07/10/2017 dmi.bios.vendor: LENOVO dmi.bios.version: 0XCN43WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Toronto 4A2 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40679 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 310-14ISK dmi.modalias: dmi:bvnLENOVO:bvr0XCN43WW:bd07/10/2017:svnLENOVO:pn80UG:pvrLenovoideapad310-14ISK:rvnLENOVO:rnToronto4A2:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad310-14ISK: dmi.product.family: IDEAPAD dmi.product.name: 80UG dmi.product.version: Lenovo ideapad 310-14ISK dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net
[Kernel-packages] [Bug 1777863] Re: [drm:intel_wait_ddi_buf_idle [i915]] *ERROR* Timeout waiting for DDI BUF C idle bit
Does this still happen to latest mainline kernel v4.20-rc7? -- 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/1777863 Title: [drm:intel_wait_ddi_buf_idle [i915]] *ERROR* Timeout waiting for DDI BUF C idle bit Status in linux package in Ubuntu: Confirmed Bug description: System reboot. This could be related to putting the NB back into the docking station. Search for [ cut here ] to find the final error message before reboot. Linux mymachine4 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 18:02:16 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux Jun 20 12:05:00 mymachine /usr/lib/gdm3/gdm-x-session[4443]: (II) modeset(0): Using vrefresh ranges from config file Jun 20 12:05:00 mymachine /usr/lib/gdm3/gdm-x-session[4443]: (II) modeset(0): Printing DDC gathered Modelines: Jun 20 12:05:00 mymachine /usr/lib/gdm3/gdm-x-session[4443]: (II) modeset(0): Modeline "1920x1080"x0.0 148.50 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync (67.5 kHz eP) Jun 20 12:05:00 mymachine /usr/lib/gdm3/gdm-x-session[4443]: (II) modeset(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e) Jun 20 12:05:00 mymachine /usr/lib/gdm3/gdm-x-session[4443]: (II) modeset(0): Modeline "640x480"x0.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e) Jun 20 12:05:00 mymachine /usr/lib/gdm3/gdm-x-session[4443]: (II) modeset(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e) Jun 20 12:05:00 mymachine /usr/lib/gdm3/gdm-x-session[4443]: (II) modeset(0): Modeline "720x400"x0.0 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e) Jun 20 12:05:00 mymachine /usr/lib/gdm3/gdm-x-session[4443]: (II) modeset(0): Modeline "1280x1024"x0.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz e) Jun 20 12:05:00 mymachine /usr/lib/gdm3/gdm-x-session[4443]: (II) modeset(0): Modeline "1024x768"x0.0 78.75 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.0 kHz e) Jun 20 12:05:00 mymachine /usr/lib/gdm3/gdm-x-session[4443]: (II) modeset(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e) Jun 20 12:05:00 mymachine /usr/lib/gdm3/gdm-x-session[4443]: (II) modeset(0): Modeline "800x600"x0.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e) Jun 20 12:05:00 mymachine /usr/lib/gdm3/gdm-x-session[4443]: (II) modeset(0): Modeline "1152x864"x0.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz e) Jun 20 12:05:00 mymachine /usr/lib/gdm3/gdm-x-session[4443]: (II) modeset(0): Modeline "1280x1024"x0.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz e) Jun 20 12:05:00 mymachine /usr/lib/gdm3/gdm-x-session[4443]: (II) modeset(0): Modeline "1600x900"x60.0 119.00 1600 1696 1864 2128 900 901 904 932 -hsync +vsync (55.9 kHz e) Jun 20 12:05:00 mymachine /usr/lib/gdm3/gdm-x-session[4443]: (II) modeset(0): Modeline "1920x1080"x60.0 172.80 1920 2040 2248 2576 1080 1081 1084 1118 -hsync +vsync (67.1 kHz e) Jun 20 12:05:18 mymachine kernel: [drm:intel_wait_ddi_buf_idle [i915]] *ERROR* Timeout waiting for DDI BUF C idle bit Jun 20 12:05:18 mymachine kernel: [ cut here ] Jun 20 12:05:18 mymachine kernel: vblank wait timed out on crtc 2 Jun 20 12:05:18 mymachine kernel: WARNING: CPU: 2 PID: 4445 at /build/linux-uT8zSN/linux-4.15.0/drivers/gpu/drm/drm_vblank.c:1073 drm_wait_one_vblank+0x181/0x190 [drm] Jun 20 12:05:18 mymachine kernel: Modules linked in: msr rfcomm ccm veth nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo br_netfilter bridge stp llc overlay thunderbolt cmac bnep btusb btrtl btbcm uvcvideo Jun 20 12:05:18 mymachine kernel: intel_cstate mac80211 intel_rapl_perf snd_compress ac97_bus snd_pcm_dmaengine snd_seq_midi snd_seq_midi_event snd_hda_intel snd_rawmidi snd_hda_codec snd_hda_core snd_hwdep i Jun 20 12:05:18 mymachine kernel: pps_core drm nvme_core wmi video Jun 20 12:05:18 mymachine kernel: CPU: 2 PID: 4445 Comm: Xorg Tainted: G W4.15.0-23-generic #25-Ubuntu Jun 20 12:05:18 mymachine kernel: Hardware name: LENOVO 20HGS30X00/20HGS30X00, BIOS N1WET34W (1.13 ) 06/26/2017 Jun 20 12:05:18 mymachine kernel: RIP: 0010:drm_wait_one_vblank+0x181/0x190 [drm] Jun 20 12:05:18 mymachine kernel: RSP: 0018:a32ac3b83a68 EFLAGS: 00010282 Jun 20 12:05:18 mymachine kernel: RAX: RBX: 8c5175a38000 RCX: 0006 Jun 20 12:05:18 mymachine kernel: RDX: 0007 RSI: 0096 RDI: 8c519e516490 Jun 20 12:05:18 mymachine kernel: RBP: a32ac3b83ac0 R08: 0001 R09: 06aa Jun 20 12:05:18 mymachine kernel: R10: R11: R12: 0002
[Kernel-packages] [Bug 1808418] Re: Thinkpad T430u won't boot without noapic workaround
The next step is to find the last working -rc kernel and first non- working -rc kernel. >From your description, both of them should be <= v4.13. The kernels can be found in [1]. [1] https://kernel.ubuntu.com/~kernel-ppa/mainline/ -- 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/1808418 Title: Thinkpad T430u won't boot without noapic workaround Status in linux package in Ubuntu: Confirmed Bug description: I've used Ubuntu on this specific machine for years without problems, but starting with the 4.13 kernel that came with the 17.10 HWE and continuing into 18.04 kernels my computer would no longer boot, hanging at various screens: - A blank screen with a flashing cursor - A screen with this message: Loading Linux 4.13.0.36-generic ... Loading initial ramdisk ... - A screen with kernel messages, ending in: APCI: EC: interrupt blocked I've encountered the bug in a number of kernels, including: - 4.13.0-32 - 4.13.0-36 - 4.13.0-37 - 4.15.0-24 - 4.15.0-34 - 4.15.0-36 - 4.15.0-38 - 4.15.0-42 - 4.20.0-rc7 I was able to work around the issue by adding noapic to GRUB_CMDLINE_LINUX_DEFAULT in /etc/default grub, e.g.: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash noapic" I'm not entirely sure of the consequences of this workaround, but one thing I've noticed is significantly reduced battery life. This bug seems very similar to what's described here for the Thinkpad E485/E585: https://evilazrael.de/node/401 I'll attach screenshots of various times I've encountered this bug over the last year. $ lsb_release -rd Description:Ubuntu 18.04.1 LTS Release:18.04 $ apt-cache policy linux-image-4.15.0-42-generic linux-image-4.15.0-42-generic: Installed: 4.15.0-42.45 Candidate: 4.15.0-42.45 Version table: *** 4.15.0-42.45 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-42-generic 4.15.0-42.45 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bryan 2349 F pulseaudio CurrentDesktop: XFCE Date: Thu Dec 13 15:31:15 2018 HibernationDevice: RESUME=UUID=4afa8032-cfe5-45f4-a626-738ab33904ac InstallationDate: Installed on 2014-05-08 (1680 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: LENOVO 3351CTO ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic root=UUID=cffbc87d-956b-4986-94df-b3b64ae5237f ro quiet splash noapic vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-42-generic N/A linux-backports-modules-4.15.0-42-generic N/A linux-firmware 1.173.2 SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-07-12 (154 days ago) dmi.bios.date: 06/01/2018 dmi.bios.vendor: LENOVO dmi.bios.version: H6ETA0WW (2.18 ) dmi.board.asset.tag: Not Available dmi.board.name: 3351CTO dmi.board.vendor: LENOVO dmi.board.version: Win8 STD DPK TPG dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrH6ETA0WW(2.18):bd06/01/2018:svnLENOVO:pn3351CTO:pvrThinkPadT430u:rvnLENOVO:rn3351CTO:rvrWin8STDDPKTPG:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T430u dmi.product.name: 3351CTO dmi.product.version: ThinkPad T430u dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808418/+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 1803929] Re: Summary: Kernel bug (unhandled paging request) on "udisksctl power-off"
4.4.0-141 syncs to upstream stable 4.4.162. So not to 4.4.165 yet. -- 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/1803929 Title: Summary: Kernel bug (unhandled paging request) on "udisksctl power- off" Status in linux package in Ubuntu: Confirmed Bug description: lsb_release -rd Description: Ubuntu 16.04.5 LTS Release: 16.04 uname -a Linux metabox 4.4.0-139-generic #165-Ubuntu SMP Wed Oct 24 10:58:50 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux Steps (1) to reproduce: 1) Plug in a USB3 hard drive. 2) Right click on launcher icon. 3) Select "Safely Remove". After finding this: https://askubuntu.com/a/532691 ...the following steps also reproduce the problem. Steps (2) to reproduce: 1) Plugin in a USB3 hard drive. 2) udisksctl unmount -b /dev/sdXY 3) udisksctl power-off -b /dev/sdX System completely locks and becomes unresponsive, such that even the Magic SysRq key combination does nothing. Most of the time the fans on my laptop go crazy (so the CPU must get stuck in some loop), but once they did not and the system was just locked (without the fans going nuts). I can't get a textual copy of the kernel bug log (because I have to do a hard reset to regain control of the system and the output doesn't get flushed to disk), but I did manage to get a photo of some of it (please refer to attachment). --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: matt 2754 F...m pulseaudio /dev/snd/controlC1: matt 2754 F pulseaudio /dev/snd/controlC0: matt 2754 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=f00235c0-ba8a-4403-91b1-64e9d87b76e0 InstallationDate: Installed on 2016-04-23 (940 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Notebook N150SD/N155SD NonfreeKernelModules: zfs zunicode zcommon znvpair zavl Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-139-generic root=UUID=beb9b9ce-39a7-464a-978c-ac4fb82a5a81 ro quiet splash ProcVersionSignature: Ubuntu 4.4.0-139.165-generic 4.4.160 RelatedPackageVersions: linux-restricted-modules-4.4.0-139-generic N/A linux-backports-modules-4.4.0-139-generic N/A linux-firmware 1.157.20 Tags: xenial Uname: Linux 4.4.0-139-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark _MarkForUpload: True dmi.bios.date: 03/31/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.03.05 dmi.board.asset.tag: Tag 12345 dmi.board.name: N150SD/N155SD dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.03.05:bd03/31/2015:svnNotebook:pnN150SD/N155SD:pvrNotApplicable:rvnNotebook:rnN150SD/N155SD:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.name: N150SD/N155SD dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1803929/+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 1802821] Re: Serious design flaw using large external drives.
Please try kernel parameter "usb-storage.quirks=vid:pid:u", replace vid and pid to the USB device ids. This disables UAS mode, which makes the IO slower but possibly more reliable. -- 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/1802821 Title: Serious design flaw using large external drives. Status in linux package in Ubuntu: Confirmed Bug description: I am trying to recover data from an HFS+ files system on a 4TB external USB 3 drive. Copying 3TB from the 4TB HFS+ drive to a 4TB NTFS drive using MATE Terminal cp -anR from to took 2 days. When I try to copy the same data to a 6TB NTFS USB 3 drive the results are glacial. 750GB has taken over 6 days. Obviously there is a problem of scale drive in Ubuntu MATE. I invite the developers to plug in a 12TB drive and see just how glacial (no - not glacial, more on the order of plate techtonics) slow their design is. Robert Pearson ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-38-generic 4.15.0-38.41 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: robert 2102 F pulseaudio /dev/snd/controlC0: robert 2102 F pulseaudio CurrentDesktop: MATE Date: Sun Nov 11 23:50:13 2018 HibernationDevice: RESUME=UUID=aa95f07d-f769-44ca-8b33-0c5b3c78bdeb InstallationDate: Installed on 2018-10-25 (18 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: System manufacturer System Product Name ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic root=UUID=26dc3ca5-f3ae-47eb-92b6-4f02ed5ba4f0 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-38-generic N/A linux-backports-modules-4.15.0-38-generic N/A linux-firmware 1.173.1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1301 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: A88XM-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1301:bd04/01/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA88XM-A:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802821/+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 1790454] Re: Bluetooth (btintel) stops working after suspend/resume
Bas, Does "enable_autosuspend=0" alone fix your issue? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1790454 Title: Bluetooth (btintel) stops working after suspend/resume Status in linux package in Ubuntu: Confirmed Bug description: I run cosmic on my Dell Latitude E7470, which has an intel usb bluetooth device (8087:0a2b). Sometimes (not every time) after a suspend/resume cycle, my laptop's bluetooth stops working. hciconfig shows: hci0: Type: Primary Bus: USB BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0 DOWN RX bytes:0 acl:0 sco:0 events:0 errors:0 TX bytes:3 acl:0 sco:0 commands:1 errors:0 and dmesg tells me (various combinations of): [237660.728312] Bluetooth: hci0: command tx timeout [237732.339965] Bluetooth: hci0: command 0xfc05 tx timeout [237925.202500] Bluetooth: hci0: Reading Intel version information failed (-110) Trying to reinitialize the device by reloading the driver has no effect: ╰─▶ modprobe -r btusb; modprobe -r btintel; modprobe btintel; modprobe btusb shows in dmesg: [237938.219190] usbcore: deregistering interface driver btusb [237938.601731] usbcore: registered new interface driver btusb [237940.626392] Bluetooth: hci0: Reading Intel version information failed (-110) [237940.626426] Bluetooth: hci0: command tx timeout Strangely enough, reloading the module sometimes does work, upon which the kernel tells me : aug 20 15:36:08 regan kernel: usbcore: deregistering interface driver btusb aug 20 15:36:30 regan kernel: Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014 aug 20 15:36:30 regan kernel: usbcore: registered new interface driver btusb aug 20 15:36:30 regan kernel: Bluetooth: hci0: Device revision is 5 aug 20 15:36:30 regan kernel: Bluetooth: hci0: Secure boot is enabled aug 20 15:36:30 regan kernel: Bluetooth: hci0: OTP lock is enabled aug 20 15:36:30 regan kernel: Bluetooth: hci0: API lock is enabled aug 20 15:36:30 regan kernel: Bluetooth: hci0: Debug lock is disabled aug 20 15:36:30 regan kernel: Bluetooth: hci0: Minimum firmware build 1 week 10 2014 aug 20 15:36:30 regan kernel: Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi aug 20 15:36:31 regan kernel: Bluetooth: hci0: Waiting for firmware download to complete aug 20 15:36:31 regan kernel: Bluetooth: hci0: Firmware loaded in 1590852 usecs aug 20 15:36:31 regan kernel: Bluetooth: hci0: Waiting for device to boot aug 20 15:36:31 regan kernel: Bluetooth: hci0: Device booted in 11654 usecs aug 20 15:36:31 regan kernel: Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-11-5.ddc aug 20 15:36:31 regan kernel: Bluetooth: hci0: Applying Intel DDC parameters completed Looking further back in the kernel log, the difference between failed and successful resumes seems to be this: Resume with broken bt: [236481.370814] Restarting tasks ... [236491.580841] Bluetooth: hci0: Reading Intel boot parameters failed (-110) Resume with working bt: [16562.706263] Restarting tasks ... [16562.709034] Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014 [16562.716050] Bluetooth: hci0: Device revision is 5 [16562.716052] Bluetooth: hci0: Secure boot is enabled [16562.716053] Bluetooth: hci0: OTP lock is enabled [16562.716054] Bluetooth: hci0: API lock is enabled [16562.716055] Bluetooth: hci0: Debug lock is disabled [16562.716056] Bluetooth: hci0: Minimum firmware build 1 week 10 2014 [16562.716404] Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi [16564.202470] Bluetooth: hci0: Waiting for firmware download to complete [16564.203017] Bluetooth: hci0: Firmware loaded in 1459449 usecs [16564.203091] Bluetooth: hci0: Waiting for device to boot [16564.215021] Bluetooth: hci0: Device booted in 11693 usecs [16564.215080] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-11-5.ddc [16564.219033] Bluetooth: hci0: Applying Intel DDC parameters completed and everything works fine after that. The first kernel on which this error occurred was 4.17.0-6-generic. Before that, I used 4.15.0-25-generic which works perfectly. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: bas4871 F...m pulseaudio /dev/snd/controlC0: bas4871 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 18.10 HibernationDevice: RESUME=UUID=16195e13-9fb3-41b2-9671-fb4e1df1ff93 #RESUME=/dev/dm-2 #RESUME=/dev/mapper/regan-swap InstallationDate: Installed on 2016-12-22 (619 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: Dell Inc. Latitude E7470 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_I
[Kernel-packages] [Bug 1790454] Re: Bluetooth (btintel) stops working after suspend/resume
DH, I think this can workaround your issue: [1] https://github.com/endlessm/linux/pull/424 -- 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/1790454 Title: Bluetooth (btintel) stops working after suspend/resume Status in linux package in Ubuntu: Confirmed Bug description: I run cosmic on my Dell Latitude E7470, which has an intel usb bluetooth device (8087:0a2b). Sometimes (not every time) after a suspend/resume cycle, my laptop's bluetooth stops working. hciconfig shows: hci0: Type: Primary Bus: USB BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0 DOWN RX bytes:0 acl:0 sco:0 events:0 errors:0 TX bytes:3 acl:0 sco:0 commands:1 errors:0 and dmesg tells me (various combinations of): [237660.728312] Bluetooth: hci0: command tx timeout [237732.339965] Bluetooth: hci0: command 0xfc05 tx timeout [237925.202500] Bluetooth: hci0: Reading Intel version information failed (-110) Trying to reinitialize the device by reloading the driver has no effect: ╰─▶ modprobe -r btusb; modprobe -r btintel; modprobe btintel; modprobe btusb shows in dmesg: [237938.219190] usbcore: deregistering interface driver btusb [237938.601731] usbcore: registered new interface driver btusb [237940.626392] Bluetooth: hci0: Reading Intel version information failed (-110) [237940.626426] Bluetooth: hci0: command tx timeout Strangely enough, reloading the module sometimes does work, upon which the kernel tells me : aug 20 15:36:08 regan kernel: usbcore: deregistering interface driver btusb aug 20 15:36:30 regan kernel: Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014 aug 20 15:36:30 regan kernel: usbcore: registered new interface driver btusb aug 20 15:36:30 regan kernel: Bluetooth: hci0: Device revision is 5 aug 20 15:36:30 regan kernel: Bluetooth: hci0: Secure boot is enabled aug 20 15:36:30 regan kernel: Bluetooth: hci0: OTP lock is enabled aug 20 15:36:30 regan kernel: Bluetooth: hci0: API lock is enabled aug 20 15:36:30 regan kernel: Bluetooth: hci0: Debug lock is disabled aug 20 15:36:30 regan kernel: Bluetooth: hci0: Minimum firmware build 1 week 10 2014 aug 20 15:36:30 regan kernel: Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi aug 20 15:36:31 regan kernel: Bluetooth: hci0: Waiting for firmware download to complete aug 20 15:36:31 regan kernel: Bluetooth: hci0: Firmware loaded in 1590852 usecs aug 20 15:36:31 regan kernel: Bluetooth: hci0: Waiting for device to boot aug 20 15:36:31 regan kernel: Bluetooth: hci0: Device booted in 11654 usecs aug 20 15:36:31 regan kernel: Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-11-5.ddc aug 20 15:36:31 regan kernel: Bluetooth: hci0: Applying Intel DDC parameters completed Looking further back in the kernel log, the difference between failed and successful resumes seems to be this: Resume with broken bt: [236481.370814] Restarting tasks ... [236491.580841] Bluetooth: hci0: Reading Intel boot parameters failed (-110) Resume with working bt: [16562.706263] Restarting tasks ... [16562.709034] Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014 [16562.716050] Bluetooth: hci0: Device revision is 5 [16562.716052] Bluetooth: hci0: Secure boot is enabled [16562.716053] Bluetooth: hci0: OTP lock is enabled [16562.716054] Bluetooth: hci0: API lock is enabled [16562.716055] Bluetooth: hci0: Debug lock is disabled [16562.716056] Bluetooth: hci0: Minimum firmware build 1 week 10 2014 [16562.716404] Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi [16564.202470] Bluetooth: hci0: Waiting for firmware download to complete [16564.203017] Bluetooth: hci0: Firmware loaded in 1459449 usecs [16564.203091] Bluetooth: hci0: Waiting for device to boot [16564.215021] Bluetooth: hci0: Device booted in 11693 usecs [16564.215080] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-11-5.ddc [16564.219033] Bluetooth: hci0: Applying Intel DDC parameters completed and everything works fine after that. The first kernel on which this error occurred was 4.17.0-6-generic. Before that, I used 4.15.0-25-generic which works perfectly. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: bas4871 F...m pulseaudio /dev/snd/controlC0: bas4871 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 18.10 HibernationDevice: RESUME=UUID=16195e13-9fb3-41b2-9671-fb4e1df1ff93 #RESUME=/dev/dm-2 #RESUME=/dev/mapper/regan-swap InstallationDate: Installed on 2016-12-22 (619 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: Dell Inc. Latitude E7470 Package: linux (not installed) ProcFB: 0 in
[Kernel-packages] [Bug 1807250] Re: At some point in the 18.04 cycle, /sys/bus/iio has disappeared from my system
Please find the first -rc kernel that fixes the issue between v4.15 and v4.18. Kernels can be downloaded at [1]. [1] https://kernel.ubuntu.com/~kernel-ppa/mainline/ -- 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/1807250 Title: At some point in the 18.04 cycle, /sys/bus/iio has disappeared from my system Status in gdm3 package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: I have a Yoga 900-13ISK and a Thinkpad T470s. Both have had working screen rotation in the past. However, I noticed today while supporting a user in #ubuntu, neither do now. No icon in the Gnome menu and: # G_MESSAGES_DEBUG=all iio-sensor-proxy ** (process:14877): DEBUG: 12:31:21.603: Could not find any supported sensors Indeed, /sys/bus/iio does not exist! I believe this is distinct from LP: #1792813, as I have just tested mainline 4.19 and it also does not work. I am working on getting more data, including testing older kernels from 18.04, but it might take me some time. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1807250/+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 1796693] Re: PCI/internal sound card not detected
[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/1796693 Title: PCI/internal sound card not detected Status in linux package in Ubuntu: Expired Bug description: I can't hear anything. And in the settings isn't any device like speaker or headphones. I run Ubuntu on ASUS X205TA. Thank you so much for your help. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 4.10.0-041000-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Mon Oct 8 16:51:54 2018 InstallationDate: Installed on 2018-10-07 (0 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=cs_CZ.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/04/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X205TA.212 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X205TA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX205TA.212:bd09/04/2015:svnASUSTeKCOMPUTERINC.:pnX205TA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX205TA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X205TA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796693/+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 1799181] Re: Can't find my touchpad
[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/1799181 Title: Can't find my touchpad Status in linux package in Ubuntu: Expired Bug description: It seems like Ubuntu 18.04 can't read my touchpad. This problem has been there since i started using ubuntu 18.10 LTS I'm currently using Ubuntu 18.04.1 LTS. Pc model: XPS 15 9560 Touchpad model: Palmrest KKD96 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-29-generic 4.15.0-29.31 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 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tin1149 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Oct 22 11:30:01 2018 InstallationDate: Installed on 2018-10-22 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. XPS 15 9560 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic root=UUID=e3ebc230-b8c9-45a6-a3a9-0ab2d8f88fda ro acpi=off quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-29-generic N/A linux-backports-modules-4.15.0-29-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/23/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.0 dmi.board.name: 05FFDN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.4.0:bd08/23/2017:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9560 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1799181/+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 1799058] Re: Samsung S7 U3 SDCARD access locks up Nautilus
[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/1799058 Title: Samsung S7 U3 SDCARD access locks up Nautilus Status in linux package in Ubuntu: Expired Bug description: Trying to attach a photo for another bug report I connected my android phone and opened up [SAMSUNG Android][Card][DCIM][Camera] and around 5 minutes of appearing to be locked up (without a single icon showing) Nautilus eventually showed some icons (none with picture thumbnail) initially. Also filed at: https://gitlab.gnome.org/GNOME/nautilus/issues/703 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-10-generic 4.18.0-10.11 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: scott 2470 F pulseaudio /dev/snd/controlC1: scott 2470 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Oct 21 08:06:49 2018 GvfsMonitorError: This tool has been deprecated, use 'gio mount' instead. See 'gio help mount' for more info. HotplugNewDevices: HotplugNewMounts: InstallationDate: Installed on 2018-10-20 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) IwConfig: lono wireless extensions. eno1 no wireless extensions. MachineType: System manufacturer System Product Name ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=31f5be02-c37e-43e6-96f2-8c912726514e ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 RfKill: SourcePackage: linux Symptom: storage UdevMonitorLog: monitor will print the received events for: UDEV - the event which udev sends out after rule processing UdisksMonitorLog: Monitoring the udisks daemon. Press Ctrl+C to exit. 08:07:01.469: The udisks-daemon is running (name-owner :1.8). UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/13/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2104 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: SABERTOOTH Z77 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2104:bd08/13/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTHZ77:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1799058/+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 1799039] Re: Apple Facetime HD PCI (Broadcom 1570) not accessible
[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/1799039 Title: Apple Facetime HD PCI (Broadcom 1570) not accessible Status in linux package in Ubuntu: Expired Bug description: This is a reopened bug report related to #1716673: Apple Facetime HD PCI (Broadcom 1570) not accessible The camera still is not accessible. In the old report some suggested that I should try the latest kernel. Well, with 18.10 the kernel is even newer than the one available at the time of reporting. If no one writes a driver for the camera, there will never be a module for it. The module that ships with Ubuntu is not working. I do understand that rolling out a new version is tedious. But it should be possible to a) not permanently produce regressions and b) include some improvements beyond some irrelevant GUI overhauls. btw. My machine was purchased in 2015. I don't think that PCIe is such a new technology. (sorry for my serious frustration about 18.10. I thought with 18.04 onward Canonical might have cought on) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-10-generic 4.18.0-10.11 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: wolf 1914 F pulseaudio /dev/snd/controlC0: wolf 1914 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Oct 21 12:00:56 2018 HibernationDevice: RESUME=UUID=539744c7-33c6-44da-a8b5-8bcf95f7845d InstallationDate: Installed on 2018-04-30 (174 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 05ac:0273 Apple, Inc. Bus 001 Device 002: ID 05ac:8290 Apple, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Apple Inc. MacBookPro12,1 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 SourcePackage: linux UpgradeStatus: Upgraded to cosmic on 2018-10-20 (0 days ago) dmi.bios.date: 08/08/2017 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP121.88Z.0171.B00.1708080033 dmi.board.name: Mac-E43C1C25D4880AD6 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro12,1 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-E43C1C25D4880AD6 dmi.modalias: dmi:bvnAppleInc.:bvrMBP121.88Z.0171.B00.1708080033:bd08/08/2017:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro12,1 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/1799039/+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 1799359] Re: Network remains disabled after waking up laptop from sleep
[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/1799359 Title: Network remains disabled after waking up laptop from sleep Status in linux package in Ubuntu: Expired Bug description: The reconnection to network works in linux 4.13.0-45 but not in 4.15.0-x so far. Latest vesion 38. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1799359/+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 1807250] Re: At some point in the 18.04 cycle, /sys/bus/iio has disappeared from my system
The issue now appears resolved with hwe-18.04/4.18.0-13, /sys/bus/iio is now present and the functionality has been restored. Summary: /sys/bus/iio appears to be missing on all the bionic 4.15.* kernel releases (including 4.15.0-43) but is present on xenial 4.4 and cosmic 4.18 (at least as of 4.18.0-13). Here is to hoping there is not a similar kerfuffle with RNGs and stuff :P -- 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/1807250 Title: At some point in the 18.04 cycle, /sys/bus/iio has disappeared from my system Status in gdm3 package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: I have a Yoga 900-13ISK and a Thinkpad T470s. Both have had working screen rotation in the past. However, I noticed today while supporting a user in #ubuntu, neither do now. No icon in the Gnome menu and: # G_MESSAGES_DEBUG=all iio-sensor-proxy ** (process:14877): DEBUG: 12:31:21.603: Could not find any supported sensors Indeed, /sys/bus/iio does not exist! I believe this is distinct from LP: #1792813, as I have just tested mainline 4.19 and it also does not work. I am working on getting more data, including testing older kernels from 18.04, but it might take me some time. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1807250/+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 1808625] Re: Lenovo Ideapad 330 touchpad isn't being recognised by Ubuntu. To work I have to use an external mouse.
*** This bug is a duplicate of bug 1802712 *** https://bugs.launchpad.net/bugs/1802712 I didn't understood the solution you gave me. The input command you provided, where should it be entered ? On Tuesday, 18 December, 2018, 12:36:24 PM IST, Kai-Heng Feng wrote: Should be fixed by this commit: commit 938f45008d8bc391593c97508bc798cc95a52b9b Author: Donald Shanty III Date: Wed Jul 4 15:50:47 2018 + Input: elan_i2c - add ACPI ID for lenovo ideapad 330 This allows Elan driver to bind to the touchpad found in Lenovo Ideapad 330 series laptops. Signed-off-by: Donald Shanty III Cc: sta...@vger.kernel.org Signed-off-by: Dmitry Torokhov -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1808625 Title: Lenovo Ideapad 330 touchpad isn't being recognised by Ubuntu. To work I have to use an external mouse. Status in linux package in Ubuntu: Confirmed Bug description: My laptop is Lenovo Ideapad 330. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.29 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sat Dec 15 17:13:44 2018 InstallationDate: Installed on 2018-12-11 (3 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: ankit 1270 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-12-11 (5 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 174f:241a Syntek Bus 001 Device 002: ID 0cf3:e500 Atheros Communications, Inc. Bus 001 Device 004: ID :3825 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81DE Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic root=UUID=32510822-c7f5-4d12-bb6d-9457af6abf37 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-42-generic N/A linux-backports-modules-4.15.0-42-generic N/A linux-firmware 1.173.2 Tags: bionic Uname: Linux 4.15.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/13/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 8TCN44WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0Q55722 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 330-15IKB dmi.modalias: dmi:bvnLENOVO:bvr8TCN44WW:bd06/13/2018:svnLENOVO:pn81DE:pvrLenovoideapad330-15IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55722WIN:cvnLENOVO:ct10:cvrLenovoideapad330-15IKB: dmi.product.family: ideapad 330-15IKB dmi.product.name: 81DE dmi.product.version: Lenovo ideapad 330-15IKB dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808625/+subscriptions -- 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/1808625 Title: Lenovo Ideapad 330 touchpad isn't being recognised by Ubuntu. To work I have to use an external mouse. Status in linux package in Ubuntu: Confirmed Bug description: My laptop is Lenovo Ideapad 330. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.29 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sat Dec 15 17:13:44 2018 InstallationDate: Installed on 2018-12-11 (3 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStat
[Kernel-packages] [Bug 1797975] Re: [armhf+raspi2] Error: Driver 'sdhost-bcm2835' is already registered, aborting
I reported this back in April (bug 1762835) and sent a patch to the mailing list. -- 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/1797975 Title: [armhf+raspi2] Error: Driver 'sdhost-bcm2835' is already registered, aborting Status in linux package in Ubuntu: Triaged Bug description: The follow error is shown in dmesg on my Raspberry Pi 2: [4.380151] device-mapper: uevent: version 1.0.3 [4.388525] device-mapper: ioctl: 4.39.0-ioctl (2018-04-03) initialised: dm-de...@redhat.com [4.396718] bcm2835-cpufreq: min=60 max=90 [4.407362] sdhci: Secure Digital Host Controller Interface driver [4.412699] sdhci: Copyright(c) Pierre Ossman [4.418378] sdhost-bcm2835 3f202000.mmc: could not get clk, deferring probe [4.423879] Error: Driver 'sdhost-bcm2835' is already registered, aborting... This may not be an issue at all, I don't know. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 22 11:11 seq crw-rw 1 root audio 116, 33 Jun 22 11:11 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu13 Architecture: armhf ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A DistroRelease: Ubuntu 18.10 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Package: linux (not installed) PciMultimedia: ProcFB: 0 BCM2708 FB ProcKernelCmdLine: dma.dmachans=0x7f35 bcm2708_fb.fbwidth=1824 bcm2708_fb.fbheight=984 bcm2709.boardrev=0xa01041 bcm2709.serial=0x17b63586 smsc95xx.macaddr=B8:27:EB:B6:35:86 bcm2708_fb.fbswap=1 bcm2709.uart_clock=4800 bcm2709.disk_led_gpio=47 bcm2709.disk_led_active_low=0 vc_mem.mem_base=0x3dc0 vc_mem.mem_size=0x3f00 net.ifnames=0 dwc_otg.lpm_enable=0 console=ttyAMA0,115200 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 elevator=deadline rootwait ProcVersionSignature: User Name 4.18.0-1004.6-raspi2 4.18.7 RelatedPackageVersions: linux-restricted-modules-4.18.0-1004-raspi2 N/A linux-backports-modules-4.18.0-1004-raspi2 N/A linux-firmware 1.175 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: cosmic uec-images Uname: Linux 4.18.0-1004-raspi2 armv7l UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy netdev plugdev sudo video _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797975/+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 1798400]
Still present in 6.2.0 RC 1 -- 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/1798400 Title: Regression: cannot use impress remote over bluetooth with ubuntu bionic Status in LibreOffice: New Status in bluez package in Ubuntu: Confirmed Status in libreoffice package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in libreoffice package in Fedora: Unknown Bug description: Trying to use the impress remote (https://wiki.documentfoundation.org/Impress_Remote) over bluetooth with libreoffice over ubuntu bionic fails. The handset errors out that it cannot connect with Libreoffice on the computer even if the bluetooth adapter on the handset and on the computer are correctly paired. This does not seem to be an issue in the Libreoffice or in the impress remote code: - I have tested also past LibO versions - The Impress remote codebase has not changed recently This used to work on the same hardware (headset and laptop) with ubuntu 16.04. Hence the issue seems to be in a regression in the ubuntu bluetooth stack. To replicate: 1) Install Libreoffice on Ubuntu bionic (either from the ubuntu repo or with the deb packages from the document fundation) 2) Assure that your computer has bluetooth 3) Install impress remote on an android handset (either from the play store of via fdroid) 4) Assure that "remote control" is enabled in impress Tools>Options>Impress>General 5) Pair the bluetooth adapters in the laptop and in the computer 6) Open a presentation on the laptop 7) Open the remote on the handset, got to the bluetooth pane see the computer there, touch it 8) See the impress remote erroring out Most likely you will also get a bluetooth error on dmesg RFCOMM server failed for LibreOffice Impress Remote: rfcomm_bind: Address already in use (98) Same issue was reported for fedora ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: KDE Date: Wed Oct 17 16:57:29 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-12 (1769 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Notebook W740SU ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-36-generic root=/dev/mapper/zagar_ssd--vg-root ro quiet splash resume=/dev/zagar_ssd-vg/swap_1 acpi_backlight=vendor vt.handoff=1 SourcePackage: bluez UpgradeStatus: Upgraded to bionic on 2018-06-08 (131 days ago) dmi.bios.date: 10/02/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W740SU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd10/02/2013:svnNotebook:pnW740SU:pvrNotApplicable:rvnNotebook:rnW740SU:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: W740SU dmi.product.version: Not Applicable dmi.sys.vendor: Notebook hciconfig: hci0:Type: Primary Bus: USB BD Address: 00:C2:C6:1A:28:71 ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN ISCAN RX bytes:245088 acl:15156 sco:0 events:1266 errors:0 TX bytes:15571 acl:402 sco:1 commands:131 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1798400/+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 1801743] Re: Suspend fails in Kubuntu 18.04 but works fine in Kubuntu 17.10
Everyone affected by this bug, please try 4.15.0-43. This fixes the issue completely for me (without needing to blacklist mei). This seems to have been the culprit: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1803942 System randomly hangs during suspend when mei_wdt is loaded (LP: #1803942) - SAUCE: base/dd: limit release function changes to vfio driver only @ Nadi: God jul! -- 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/1801743 Title: Suspend fails in Kubuntu 18.04 but works fine in Kubuntu 17.10 Status in linux package in Ubuntu: Confirmed Bug description: After upgrading to kubuntu 18.04 resuming from suspend fails in most cases on my laptop. When trying to resume the power LED is turned on, but the screen stays black and the system does not respond at all. Switching to another virtual terminal is not possible and closing the lid again does not show any effect. The hardware is a Dell Latitude e7440 with core i7 4600U and intel graphics only. The only way to change the status is a hard shut-down by long pressing the power button. The last message in kern.log is: PM: suspend entry (deep) The described problem is similar to bug #1774950. However, the latter is considered to be fixed with kernel 4.15.0-38 while my problem persists with this kernel. Output of 'sudo lspci -vnvn' is attached, the result of 'cat /proc/version_signature' is: Ubuntu 4.15.0-38.41-generic 4.15.18 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: graeser2116 F pulseaudio /dev/snd/controlC0: graeser2116 F pulseaudio CurrentDesktop: KDE DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20130203-1 DistroRelease: Ubuntu 18.04 EcryptfsInUse: Yes HibernationDevice: RESUME=none InstallationDate: Installed on 2014-03-20 (1690 days ago) InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 20130203-13:50 MachineType: Dell Inc. Latitude E7440 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic root=UUID=25e09413-4977-401f-a034-0465b444518b ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-38-generic N/A linux-backports-modules-4.15.0-38-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-38-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-10-15 (20 days ago) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/02/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A14 dmi.board.name: 0WK2DM dmi.board.vendor: Dell Inc. dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA14:bd02/02/2015:svnDellInc.:pnLatitudeE7440:pvr01:rvnDellInc.:rn0WK2DM:rvr:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E7440 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801743/+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 1808886] Re: Microcode SW error detected. Restarting 0x0.
shat about 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/1808886 Title: Microcode SW error detected. Restarting 0x0. Status in linux package in Ubuntu: Confirmed Bug description: intel-microcode: Installed: 3.20180807a.0ubuntu0.18.04.1 Candidate: 3.20180807a.0ubuntu0.18.04.1 Version table: *** 3.20180807a.0ubuntu0.18.04.1 500 500 http://ru.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 3.20180312.0~ubuntu18.04.1 500 500 http://ru.archive.ubuntu.com/ubuntu bionic/main amd64 Packages Version: Ubuntu 4.15.0-42.45-generic 4.15.18 Error: [ 3136.084499] rtsx_pci :06:00.0: VPD access failed. This is likely a firmware bug on this device. Contact the card vendor for a firmware update [ 3136.085614] r8169 :06:00.1: invalid short VPD tag 00 at offset 1 [ 3136.085624] dpc :00:1d.0:pcie010: DPC containment event, status:0x1f00 source:0x [ 3136.085662] pcieport :00:1d.0: AER: Multiple Corrected error received: id=00e8 [ 3136.085683] pcieport :00:1d.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e8(Transmitter ID) [ 3136.085694] pcieport :00:1d.0: device [8086:a335] error status/mask=1101/2000 [ 3136.085701] pcieport :00:1d.0:[ 0] Receiver Error (First) [ 3136.085722] pcieport :00:1d.0:[ 8] RELAY_NUM Rollover [ 3136.085741] pcieport :00:1d.0:[12] Replay Timer Timeout [ 3166.625429] iwlwifi :00:14.3: Microcode SW error detected. Restarting 0x0. [ 3166.625797] iwlwifi :00:14.3: Start IWL Error Log Dump: [ 3166.625805] iwlwifi :00:14.3: Status: 0x0100, count: 6 [ 3166.625810] iwlwifi :00:14.3: Loaded firmware version: 34.0.0 [ 3166.625817] iwlwifi :00:14.3: 0x1007 | ADVANCED_SYSASSERT [ 3166.625823] iwlwifi :00:14.3: 0x0080A614 | trm_hw_status0 [ 3166.625828] iwlwifi :00:14.3: 0x | trm_hw_status1 [ 3166.625834] iwlwifi :00:14.3: 0x00456D06 | branchlink2 [ 3166.625839] iwlwifi :00:14.3: 0x0046064A | interruptlink1 [ 3166.625844] iwlwifi :00:14.3: 0x | interruptlink2 [ 3166.625850] iwlwifi :00:14.3: 0x00030400 | data1 [ 3166.625855] iwlwifi :00:14.3: 0x040B | data2 [ 3166.625860] iwlwifi :00:14.3: 0x | data3 [ 3166.625866] iwlwifi :00:14.3: 0xAD418817 | beacon time [ 3166.625871] iwlwifi :00:14.3: 0x6A2317EF | tsf low [ 3166.625876] iwlwifi :00:14.3: 0x0184 | tsf hi [ 3166.625881] iwlwifi :00:14.3: 0x | time gp1 [ 3166.625887] iwlwifi :00:14.3: 0x0ADF380D | time gp2 [ 3166.625892] iwlwifi :00:14.3: 0x0001 | uCode revision type [ 3166.625897] iwlwifi :00:14.3: 0x0022 | uCode version major [ 3166.625903] iwlwifi :00:14.3: 0x | uCode version minor [ 3166.625908] iwlwifi :00:14.3: 0x0312 | hw version [ 3166.625913] iwlwifi :00:14.3: 0x00C89008 | board version [ 3166.625918] iwlwifi :00:14.3: 0x0A9E001C | hcmd [ 3166.625924] iwlwifi :00:14.3: 0xA4022002 | isr0 [ 3166.625929] iwlwifi :00:14.3: 0x0100 | isr1 [ 3166.625934] iwlwifi :00:14.3: 0x08001802 | isr2 [ 3166.625939] iwlwifi :00:14.3: 0x0041B8C5 | isr3 [ 3166.625944] iwlwifi :00:14.3: 0x | isr4 [ 3166.625950] iwlwifi :00:14.3: 0x00EC019C | last cmd Id [ 3166.625955] iwlwifi :00:14.3: 0x | wait_event [ 3166.625960] iwlwifi :00:14.3: 0x0080 | l2p_control [ 3166.625965] iwlwifi :00:14.3: 0x00012034 | l2p_duration [ 3166.625971] iwlwifi :00:14.3: 0x003F | l2p_mhvalid [ 3166.625976] iwlwifi :00:14.3: 0x00CE | l2p_addr_match [ 3166.625981] iwlwifi :00:14.3: 0x000F | lmpm_pmg_sel [ 3166.625987] iwlwifi :00:14.3: 0x12111721 | timestamp [ 3166.625992] iwlwifi :00:14.3: 0x9090 | flow_handler [ 3166.626141] iwlwifi :00:14.3: Start IWL Error Log Dump: [ 3166.626147] iwlwifi :00:14.3: Status: 0x0100, count: 7 [ 3166.626152] iwlwifi :00:14.3: 0x0070 | ADVANCED_SYSASSERT [ 3166.626158] iwlwifi :00:14.3: 0x | umac branchlink1 [ 3166.626163] iwlwifi :00:14.3: 0xC0087D08 | umac branchlink2 [ 3166.626168] iwlwifi :00:14.3: 0xC0083A08 | umac interruptlink1 [ 3166.626173] iwlwifi :00:14.3: 0xC0083A08 | umac interruptlink2 [ 3166.626178] iwlwifi :00:14.3: 0x0800 | umac data1 [ 3166.626184] iwlwifi :00:14.3: 0xC0083A08 | umac data2 [ 3166.626189] iwlwifi :00:14.3: 0xDEADBEEF | umac data3 [ 3166.626194] iwlwifi :00:14.3: 0x0022 | umac major [ 3166.626199] iwlwifi :00:14.3: 0x | umac minor [ 3166.626204] iwlwifi :00:14.3: 0
[Kernel-packages] [Bug 1458204] Re: removing kernels should not require a restart afterward
I also can verify 1.1ubuntu1.18.04.7~16.04.1. Yesterday new kernels were installed and a reboot performed. Today old kernel was removed and no reboot performed. This test also used the new update-notifier-common version 3.168.10. Yesterday I received an email telling me that new kernels had been installed and a reboot was performed, as it should, but today I received no email stating the old kernel had been removed. I expected one. Is this a new 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/1458204 Title: removing kernels should not require a restart afterward Status in unattended-upgrades: New Status in update notifier: New Status in linux package in Ubuntu: Confirmed Status in unattended-upgrades package in Ubuntu: Fix Released Status in update-notifier package in Ubuntu: Fix Released Status in unattended-upgrades source package in Xenial: Fix Committed Status in update-notifier source package in Xenial: Fix Committed Status in linux source package in Artful: Won't Fix Status in unattended-upgrades source package in Artful: Won't Fix Status in update-notifier source package in Artful: Won't Fix Bug description: [Impact] The rationale behind the SRU to Xenial is that with latest unattended- upgrades SRU it starts removing unused kernels, but all older kernels are not removed in a single run. With update-notifier and u-u not fixed they place /var/run/reboot-required asking for a reboot when it is not needed. [Test Case] 1. Perform a kernel upgrade normally via "apt-get dist-upgrade". 2. Reboot. 3. Run "apt-get autoremove" to delete the old kernel packages. 4. "System Notification Helper" now reports that the computer requires a reboot. The "autoremove" operation shouldn't require a reboot, logically speaking, because it's just removing files that are unused by the OS. [ Regression Potential ] If the check for skipping placing the /var/run/reboot-required file is too broad it may make kernel upgrades fail to ask for reboot. The fix changes a hook called by maintainer scripts and a failure in the hook can make kernel package installations fail. The fix is simple and was tested in several releases thus regressing in these ways is unlikely. [ Original Bug Text ] ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: apt 1.0.1ubuntu2.7 ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19 Uname: Linux 3.13.0-53-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CurrentDesktop: KDE Date: Sat May 23 12:47:15 2015 InstallationDate: Installed on 2013-08-31 (629 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: apt UpgradeStatus: Upgraded to trusty on 2014-04-26 (391 days ago) --- ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=66f11ff7-00bb-4452-9168-003cf9078308 InstallationDate: Installed on 2013-08-31 (632 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: System manufacturer System Product Name Package: linux (not installed) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-53-generic root=UUID=02741f1f-8107-4a0f-b9a6-31ef470b1389 ro libata.force=noncq quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19 RelatedPackageVersions: linux-restricted-modules-3.13.0-53-generic N/A linux-backports-modules-3.13.0-53-generic N/A linux-firmware 1.127.12 RfKill: Tags: trusty Uname: Linux 3.13.0-53-generic x86_64 UpgradeStatus: Upgraded to trusty on 2014-04-26 (395 days ago) UserGroups: adm cdrom dialout dip fuse lightdm lpadmin plugdev sambashare sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 08/12/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4210 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P9X79 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4210:bd08/12/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP9X79:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/unattended-upgrades/+bug/1458204/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-package
[Kernel-packages] [Bug 1790454] Re: Bluetooth (btintel) stops working after suspend/resume
If the enable_autosuspend option doesn't fix your issue, I think you are encountering a different bug (with overlapping symptoms). For clarity, it might be best to open a separate bug report for your issue. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1790454 Title: Bluetooth (btintel) stops working after suspend/resume Status in linux package in Ubuntu: Confirmed Bug description: I run cosmic on my Dell Latitude E7470, which has an intel usb bluetooth device (8087:0a2b). Sometimes (not every time) after a suspend/resume cycle, my laptop's bluetooth stops working. hciconfig shows: hci0: Type: Primary Bus: USB BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0 DOWN RX bytes:0 acl:0 sco:0 events:0 errors:0 TX bytes:3 acl:0 sco:0 commands:1 errors:0 and dmesg tells me (various combinations of): [237660.728312] Bluetooth: hci0: command tx timeout [237732.339965] Bluetooth: hci0: command 0xfc05 tx timeout [237925.202500] Bluetooth: hci0: Reading Intel version information failed (-110) Trying to reinitialize the device by reloading the driver has no effect: ╰─▶ modprobe -r btusb; modprobe -r btintel; modprobe btintel; modprobe btusb shows in dmesg: [237938.219190] usbcore: deregistering interface driver btusb [237938.601731] usbcore: registered new interface driver btusb [237940.626392] Bluetooth: hci0: Reading Intel version information failed (-110) [237940.626426] Bluetooth: hci0: command tx timeout Strangely enough, reloading the module sometimes does work, upon which the kernel tells me : aug 20 15:36:08 regan kernel: usbcore: deregistering interface driver btusb aug 20 15:36:30 regan kernel: Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014 aug 20 15:36:30 regan kernel: usbcore: registered new interface driver btusb aug 20 15:36:30 regan kernel: Bluetooth: hci0: Device revision is 5 aug 20 15:36:30 regan kernel: Bluetooth: hci0: Secure boot is enabled aug 20 15:36:30 regan kernel: Bluetooth: hci0: OTP lock is enabled aug 20 15:36:30 regan kernel: Bluetooth: hci0: API lock is enabled aug 20 15:36:30 regan kernel: Bluetooth: hci0: Debug lock is disabled aug 20 15:36:30 regan kernel: Bluetooth: hci0: Minimum firmware build 1 week 10 2014 aug 20 15:36:30 regan kernel: Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi aug 20 15:36:31 regan kernel: Bluetooth: hci0: Waiting for firmware download to complete aug 20 15:36:31 regan kernel: Bluetooth: hci0: Firmware loaded in 1590852 usecs aug 20 15:36:31 regan kernel: Bluetooth: hci0: Waiting for device to boot aug 20 15:36:31 regan kernel: Bluetooth: hci0: Device booted in 11654 usecs aug 20 15:36:31 regan kernel: Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-11-5.ddc aug 20 15:36:31 regan kernel: Bluetooth: hci0: Applying Intel DDC parameters completed Looking further back in the kernel log, the difference between failed and successful resumes seems to be this: Resume with broken bt: [236481.370814] Restarting tasks ... [236491.580841] Bluetooth: hci0: Reading Intel boot parameters failed (-110) Resume with working bt: [16562.706263] Restarting tasks ... [16562.709034] Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014 [16562.716050] Bluetooth: hci0: Device revision is 5 [16562.716052] Bluetooth: hci0: Secure boot is enabled [16562.716053] Bluetooth: hci0: OTP lock is enabled [16562.716054] Bluetooth: hci0: API lock is enabled [16562.716055] Bluetooth: hci0: Debug lock is disabled [16562.716056] Bluetooth: hci0: Minimum firmware build 1 week 10 2014 [16562.716404] Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi [16564.202470] Bluetooth: hci0: Waiting for firmware download to complete [16564.203017] Bluetooth: hci0: Firmware loaded in 1459449 usecs [16564.203091] Bluetooth: hci0: Waiting for device to boot [16564.215021] Bluetooth: hci0: Device booted in 11693 usecs [16564.215080] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-11-5.ddc [16564.219033] Bluetooth: hci0: Applying Intel DDC parameters completed and everything works fine after that. The first kernel on which this error occurred was 4.17.0-6-generic. Before that, I used 4.15.0-25-generic which works perfectly. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: bas4871 F...m pulseaudio /dev/snd/controlC0: bas4871 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 18.10 HibernationDevice: RESUME=UUID=16195e13-9fb3-41b2-9671-fb4e1df1ff93 #RESUME=/dev/dm-2 #RESUME=/dev/mapper/regan-swap InstallationDate: Installed on 2016-12-22 (619 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak"
[Kernel-packages] [Bug 1802050] Re: Kernel module crash 4.18.0-10 after upgrade from 18.04 to 18.10
** Changed in: linux (Ubuntu) Status: Triaged => 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/1802050 Title: Kernel module crash 4.18.0-10 after upgrade from 18.04 to 18.10 Status in linux package in Ubuntu: Confirmed Bug description: [ 56.996976] [ cut here ] [ 56.996978] Bad or missing usercopy whitelist? Kernel memory exposure attempt detected from SLUB object 'nvidia_stack_cache' (offset 11440, size 3)! [ 56.996985] WARNING: CPU: 3 PID: 2547 at mm/usercopy.c:81 usercopy_warn+0x81/0xa0 [ 56.996985] Modules linked in: ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter devlink bpfilter pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) nvidia_uvm(POE) eeepc_wmi asus_wmi snd_hda_codec_hdmi mxm_wmi wmi_bmof sparse_keymap nvidia_drm(POE) nvidia_modeset(POE) snd_hda_codec_realtek intel_rapl nvidia(POE) snd_hda_codec_generic x86_pkg_temp_thermal intel_powerclamp coretemp snd_hda_intel kvm_intel kvm snd_hda_codec joydev snd_hda_core snd_usb_audio snd_usbmidi_lib irqbypass snd_hwdep input_leds crct10dif_pclmul crc32_pclmul ghash_clmulni_intel snd_pcm pcbc aesni_intel snd_seq_midi snd_seq_midi_event aes_x86_64 snd_rawmidi crypto_simd cryptd snd_seq glue_helper drm_kms_helper intel_cstate drm ipmi_devintf ipmi_msghandler intel_rapl_perf snd_seq_device snd_timer fb_sys_fops [ 56.997003] syscopyarea sysfillrect sysimgblt snd mac_hid soundcore wmi video mei_me mei acpi_pad sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables autofs4 raid10 multipath linear raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq raid0 libcrc32c raid1 hid_generic usbhid hid gpio_ich r8169 i2c_i801 mii lpc_ich ahci libahci [ 56.997016] CPU: 3 PID: 2547 Comm: Xorg Tainted: P OE 4.18.0-10-generic #11-Ubuntu [ 56.997017] Hardware name: ASUS All Series/Z97-K, BIOS 2902 03/31/2016 [ 56.997018] RIP: 0010:usercopy_warn+0x81/0xa0 [ 56.997018] Code: b0 aa 41 51 4d 89 d8 48 c7 c0 89 8d af aa 49 89 f1 48 89 f9 48 0f 45 c2 48 c7 c7 f0 a1 b0 aa 4c 89 d2 48 89 c6 e8 f1 cf df ff <0f> 0b 48 83 c4 18 c9 c3 48 c7 c6 b2 8a b2 aa 49 89 f1 49 89 f3 eb [ 56.997030] RSP: 0018:b9550248bb08 EFLAGS: 00010286 [ 56.997031] RAX: RBX: 90fdc8535cb0 RCX: 0006 [ 56.997032] RDX: 0007 RSI: 0096 RDI: 90fdded964b0 [ 56.997032] RBP: b9550248bb20 R08: 0001 R09: 038f [ 56.997032] R10: 0004 R11: R12: 0003 [ 56.997033] R13: 0001 R14: 90fdc8535cb3 R15: 90fdc8535cf8 [ 56.997033] FS: 7f854792ba80() GS:90fdded8() knlGS: [ 56.997034] CS: 0010 DS: ES: CR0: 80050033 [ 56.997034] CR2: 7f8543fd2110 CR3: 000406668006 CR4: 001606e0 [ 56.997035] Call Trace: [ 56.997038] __check_heap_object+0xc2/0x110 [ 56.997039] __check_object_size+0x14c/0x178 [ 56.997148] os_memcpy_to_user+0x26/0x50 [nvidia] [ 56.997254] _nv009384rm+0xbf/0xe0 [nvidia] [ 56.997255] WARNING: kernel stack frame pointer at 8fe294b8 in Xorg:2547 has bad value 5fea09aa [ 56.997256] unwind stack type:0 next_sp: (null) mask:0x2 graph_idx:0 [ 56.997257] 1bbff756: b9550248bb30 (0xb9550248bb30) [ 56.997258] 21ffd201: a9c69a82 (__check_heap_object+0xc2/0x110) [ 56.997258] 2ec89026: b9550248bb60 (0xb9550248bb60) [ 56.997259] 297b0120: a9c91abc (__check_object_size+0x14c/0x178) [ 56.997259] 8569feab: 0003 (0x3) [ 56.997260] b2feea66: 90fdc8535cb0 (0x90fdc8535cb0) [ 56.997260] a5345c20: 55924226a63e (0x55924226a63e) [ 56.997260] 798de38a: ... [ 56.997261] 871cf253: b9550248bb88 (0xb9550248bb88) [ 56.997311] 5645fcd2: c0b305b6 (os_memcpy_to_user+0x26/0x50 [nvidia]) [ 56.997311] 929e7969: 0003 (0x3) [ 56.997312] cbb9721c: 55924226a63e (0x55924226a63e) [ 56.997312] cf624d15: 90fdc8535cb0 (0x90fdc8535cb0) [ 56.997312] 8fe294b8: 90fdc8535ca8 (0x90fdc8535ca8) [ 56.997417] 7dbcdd8d: c110087f (_nv009384rm+0xbf/0xe0 [nvidia]) [ 56.997418] c0dd2ba2: 90fdc8535c88 (0x90fdc8535c88) [ 56.997418] a931d446: ... [ 56.997418] 28151017: 90fda8ed62e8 (0x90fda8ed62e8) [ 56.997419] f1c853ed: 90fdc8535db8 (0x90fdc8535db8) [ 56.997419] 761fa9f3: 7ffe66b4aa10 (0x7ffe66b4aa10) [ 56.997505] 9e2ac77b: c0cfa259 (_nv028097rm+0x79
[Kernel-packages] [Bug 1801743] Re: Suspend fails in Kubuntu 18.04 but works fine in Kubuntu 17.10
Hei Magnus, Yes it solved my problem as well. Using kernel 4.19.11, I blacklisted mei_me as you pointed out, now I have no crash when resuming from sleep S3, finally!! Thanks a lot, God Jul! :-) -- 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/1801743 Title: Suspend fails in Kubuntu 18.04 but works fine in Kubuntu 17.10 Status in linux package in Ubuntu: Confirmed Bug description: After upgrading to kubuntu 18.04 resuming from suspend fails in most cases on my laptop. When trying to resume the power LED is turned on, but the screen stays black and the system does not respond at all. Switching to another virtual terminal is not possible and closing the lid again does not show any effect. The hardware is a Dell Latitude e7440 with core i7 4600U and intel graphics only. The only way to change the status is a hard shut-down by long pressing the power button. The last message in kern.log is: PM: suspend entry (deep) The described problem is similar to bug #1774950. However, the latter is considered to be fixed with kernel 4.15.0-38 while my problem persists with this kernel. Output of 'sudo lspci -vnvn' is attached, the result of 'cat /proc/version_signature' is: Ubuntu 4.15.0-38.41-generic 4.15.18 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: graeser2116 F pulseaudio /dev/snd/controlC0: graeser2116 F pulseaudio CurrentDesktop: KDE DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20130203-1 DistroRelease: Ubuntu 18.04 EcryptfsInUse: Yes HibernationDevice: RESUME=none InstallationDate: Installed on 2014-03-20 (1690 days ago) InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 20130203-13:50 MachineType: Dell Inc. Latitude E7440 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic root=UUID=25e09413-4977-401f-a034-0465b444518b ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-38-generic N/A linux-backports-modules-4.15.0-38-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-38-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-10-15 (20 days ago) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/02/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A14 dmi.board.name: 0WK2DM dmi.board.vendor: Dell Inc. dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA14:bd02/02/2015:svnDellInc.:pnLatitudeE7440:pvr01:rvnDellInc.:rn0WK2DM:rvr:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E7440 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801743/+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]
That's not an AMD specific problem, I'm getting the same issue on a Intel I7 8700 -- 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 2017-05-09 (1 days ago) InstallationMedia: Ubuntu-Server 17.04 "Zesty Zapus" - Release amd64 (20170412) Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash Tags: zesty Uname: Linux 4.11.0-041100-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1690085/+subscriptions -- Mailing list:
[Kernel-packages] [Bug 1752437]
I have installed archlinux and kernel 4.19.11-arch1-1-ARCH on my HP ENVY x360 – 15-bq101ng. I also installed Gnome and Gnome-extra, but still my Stylus and touchscreen do not work. Can some one help me please ? Thanks -- 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/1752437 Title: [HP ENVY x360 - 15-bq102ng] Touchscreen does not work Status in linux: Fix Released Status in linux package in Ubuntu: Confirmed Bug description: The touch screen on my HP ENVY x360 15-bq102ng does not work with stock kernel or with mainline kernel 4.16-rc3. marc@snapbug:~$ xinput ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ SynPS/2 Synaptics TouchPad id=13 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] ↳ Power Buttonid=9[slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=12 [slave keyboard (3)] ↳ HP Wireless hotkeys id=14 [slave keyboard (3)] ↳ HP WMI hotkeys id=15 [slave keyboard (3)] ↳ HP Wide Vision FHD Camera: HP I id=11 [slave keyboard (3)] ↳ HP Wide Vision FHD Camera: HP W id=10 [slave keyboard (3)] WORKAROUND: Use the following patch with 4.17-rc3: https://bugzilla.kernel.org/attachment.cgi?id=275381 ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 Uname: Linux 4.16.0-041600rc2-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 BootLog: No key available with this passphrase. /dev/mapper/nvme0n1p2_crypt: clean, 621596/15597568 files, 54013381/62389248 blocks CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Feb 28 22:34:50 2018 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:15dd] (rev c4) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:83c6] InstallationDate: Installed on 2018-01-16 (42 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) MachineType: HP HP ENVY x360 Convertible 15-bq1xx ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.16.0-041600rc2-generic root=UUID=415eb027-1fd5-4b75-9860-5cac88a630db ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/26/2018 dmi.bios.vendor: AMI dmi.bios.version: F.16 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 83C6 dmi.board.vendor: HP dmi.board.version: 63.18 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.16:bd01/26/2018:svnHP:pnHPENVYx360Convertible15-bq1xx:pvr:rvnHP:rn83C6:rvr63.18:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Envy dmi.product.name: HP ENVY x360 Convertible 15-bq1xx dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.85-4~a~padoka0 version.libgl1-mesa-dri: libgl1-mesa-dri 1:17.3.2-0~a~padoka0 version.libgl1-mesa-glx: libgl1-mesa-glx 1:17.3.2-0~a~padoka0 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel/+bug/1752437/+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]
(In reply to Vladyslav Yamkovyi from comment #453) > Let's face it: I really, really don't think measuring time before a freeze > makes any sense. It just occurs under certain circumstances or even randomly > due to some hardware bug - 4.19 will work 4 days for the first time, 3 hours > for the second time and 23 hours for the third. That's for sure - it's not > related to a specific version, it just persists across all kernel versions. I confirm that, tested on kernel 3.x, 4.12, 4.15, 4.19 -- 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 2017-05-09 (1 days ago) InstallationMedia: Ubuntu-Server 17.04 "Zesty Zapus" - Release amd64 (20170412) Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user)
[Kernel-packages] [Bug 1752437]
(In reply to Thomas from comment #110) > I have installed archlinux and kernel 4.19.11-arch1-1-ARCH on my HP ENVY > x360 – 15-bq101ng. I also installed Gnome and Gnome-extra, but still my > Stylus and touchscreen do not work. Can some one help me please ? > Thanks I now even installed Ubuntu 18.10 with kernel 4.19.11 through ukuu but it still not 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/1752437 Title: [HP ENVY x360 - 15-bq102ng] Touchscreen does not work Status in linux: Fix Released Status in linux package in Ubuntu: Confirmed Bug description: The touch screen on my HP ENVY x360 15-bq102ng does not work with stock kernel or with mainline kernel 4.16-rc3. marc@snapbug:~$ xinput ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ SynPS/2 Synaptics TouchPad id=13 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] ↳ Power Buttonid=9[slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=12 [slave keyboard (3)] ↳ HP Wireless hotkeys id=14 [slave keyboard (3)] ↳ HP WMI hotkeys id=15 [slave keyboard (3)] ↳ HP Wide Vision FHD Camera: HP I id=11 [slave keyboard (3)] ↳ HP Wide Vision FHD Camera: HP W id=10 [slave keyboard (3)] WORKAROUND: Use the following patch with 4.17-rc3: https://bugzilla.kernel.org/attachment.cgi?id=275381 ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 Uname: Linux 4.16.0-041600rc2-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 BootLog: No key available with this passphrase. /dev/mapper/nvme0n1p2_crypt: clean, 621596/15597568 files, 54013381/62389248 blocks CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Feb 28 22:34:50 2018 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:15dd] (rev c4) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:83c6] InstallationDate: Installed on 2018-01-16 (42 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) MachineType: HP HP ENVY x360 Convertible 15-bq1xx ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.16.0-041600rc2-generic root=UUID=415eb027-1fd5-4b75-9860-5cac88a630db ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/26/2018 dmi.bios.vendor: AMI dmi.bios.version: F.16 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 83C6 dmi.board.vendor: HP dmi.board.version: 63.18 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.16:bd01/26/2018:svnHP:pnHPENVYx360Convertible15-bq1xx:pvr:rvnHP:rn83C6:rvr63.18:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Envy dmi.product.name: HP ENVY x360 Convertible 15-bq1xx dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.85-4~a~padoka0 version.libgl1-mesa-dri: libgl1-mesa-dri 1:17.3.2-0~a~padoka0 version.libgl1-mesa-glx: libgl1-mesa-glx 1:17.3.2-0~a~padoka0 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel/+bug/1752437/+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 1752437]
Ok it work the problem was, that I start Windows 10 and restart the PC to Archlinux or Ubuntu. In Archlinux there is a log 'Disabling IRQ #7' when the bug appears, in the startup time. My work around: If I cam from Windows shutdown for 10s and then start Archlinux/Ubuntu and the Stylus and Touchscreen works.(In reply to Thomas from comment #111) > (In reply to Thomas from comment #110) > > I have installed archlinux and kernel 4.19.11-arch1-1-ARCH on my HP ENVY > > x360 – 15-bq101ng. I also installed Gnome and Gnome-extra, but still my > > Stylus and touchscreen do not work. Can some one help me please ? > > Thanks > > I now even installed Ubuntu 18.10 with kernel 4.19.11 through ukuu but it > still not work. Ok it work the problem was, that I start Windows 10 and restart the PC to Archlinux or Ubuntu. In Archlinux there is a log 'Disabling IRQ #7' when the bug appears, in the startup time. My work around: If I cam from Windows shutdown for 10s and then start Archlinux/Ubuntu and the Stylus and Touchscreen works. -- 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/1752437 Title: [HP ENVY x360 - 15-bq102ng] Touchscreen does not work Status in linux: Fix Released Status in linux package in Ubuntu: Confirmed Bug description: The touch screen on my HP ENVY x360 15-bq102ng does not work with stock kernel or with mainline kernel 4.16-rc3. marc@snapbug:~$ xinput ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ SynPS/2 Synaptics TouchPad id=13 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] ↳ Power Buttonid=9[slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=12 [slave keyboard (3)] ↳ HP Wireless hotkeys id=14 [slave keyboard (3)] ↳ HP WMI hotkeys id=15 [slave keyboard (3)] ↳ HP Wide Vision FHD Camera: HP I id=11 [slave keyboard (3)] ↳ HP Wide Vision FHD Camera: HP W id=10 [slave keyboard (3)] WORKAROUND: Use the following patch with 4.17-rc3: https://bugzilla.kernel.org/attachment.cgi?id=275381 ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 Uname: Linux 4.16.0-041600rc2-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 BootLog: No key available with this passphrase. /dev/mapper/nvme0n1p2_crypt: clean, 621596/15597568 files, 54013381/62389248 blocks CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Feb 28 22:34:50 2018 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:15dd] (rev c4) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:83c6] InstallationDate: Installed on 2018-01-16 (42 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) MachineType: HP HP ENVY x360 Convertible 15-bq1xx ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.16.0-041600rc2-generic root=UUID=415eb027-1fd5-4b75-9860-5cac88a630db ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/26/2018 dmi.bios.vendor: AMI dmi.bios.version: F.16 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 83C6 dmi.board.vendor: HP dmi.board.version: 63.18 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.16:bd01/26/2018:svnHP:pnHPENVYx360Convertible15-bq1xx:pvr:rvnHP:rn83C6:rvr63.18:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Envy dmi.product.name: HP ENVY x360 Convertible 15-bq1xx dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.85-4~a~padoka0 version.libgl1-mesa-dri: libgl1-mesa-dri 1:17.3.2-0~a~padoka0 version.libgl1-mesa-glx: libgl1-mesa-glx 1:17.3.2-0~a~padoka0 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xor
[Kernel-packages] [Bug 1752437]
it is now working with vanilla kernel 4.9.10 and BIOS F.19 :smile: -- 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/1752437 Title: [HP ENVY x360 - 15-bq102ng] Touchscreen does not work Status in linux: Fix Released Status in linux package in Ubuntu: Confirmed Bug description: The touch screen on my HP ENVY x360 15-bq102ng does not work with stock kernel or with mainline kernel 4.16-rc3. marc@snapbug:~$ xinput ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ SynPS/2 Synaptics TouchPad id=13 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] ↳ Power Buttonid=9[slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=12 [slave keyboard (3)] ↳ HP Wireless hotkeys id=14 [slave keyboard (3)] ↳ HP WMI hotkeys id=15 [slave keyboard (3)] ↳ HP Wide Vision FHD Camera: HP I id=11 [slave keyboard (3)] ↳ HP Wide Vision FHD Camera: HP W id=10 [slave keyboard (3)] WORKAROUND: Use the following patch with 4.17-rc3: https://bugzilla.kernel.org/attachment.cgi?id=275381 ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 Uname: Linux 4.16.0-041600rc2-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 BootLog: No key available with this passphrase. /dev/mapper/nvme0n1p2_crypt: clean, 621596/15597568 files, 54013381/62389248 blocks CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Feb 28 22:34:50 2018 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:15dd] (rev c4) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:83c6] InstallationDate: Installed on 2018-01-16 (42 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) MachineType: HP HP ENVY x360 Convertible 15-bq1xx ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.16.0-041600rc2-generic root=UUID=415eb027-1fd5-4b75-9860-5cac88a630db ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/26/2018 dmi.bios.vendor: AMI dmi.bios.version: F.16 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 83C6 dmi.board.vendor: HP dmi.board.version: 63.18 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.16:bd01/26/2018:svnHP:pnHPENVYx360Convertible15-bq1xx:pvr:rvnHP:rn83C6:rvr63.18:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Envy dmi.product.name: HP ENVY x360 Convertible 15-bq1xx dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.85-4~a~padoka0 version.libgl1-mesa-dri: libgl1-mesa-dri 1:17.3.2-0~a~padoka0 version.libgl1-mesa-glx: libgl1-mesa-glx 1:17.3.2-0~a~padoka0 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel/+bug/1752437/+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
