[Kernel-packages] [Bug 1768452] Re: Unable to insert test_bpf module for ubuntu_bpf_jit on Xenial s390x
** Summary changed: - Unable to insert test_bpf module on Xenial s390x + Unable to insert test_bpf module for ubuntu_bpf_jit on Xenial s390x -- 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/1768452 Title: Unable to insert test_bpf module for ubuntu_bpf_jit on Xenial s390x Status in ubuntu-kernel-tests: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Confirmed Bug description: After the test_bpf insert issue for Xenial was fixed in bug 1765698 But it looks like the s390x needs some extra work. $ sudo modprobe test_bpf modprobe: ERROR: could not insert 'test_bpf': Invalid argument 4 tests failed here: test_bpf: #243 BPF_MAXINSNS: Ctx heavy transformations FAIL to prog_create err=-524 len=4096 test_bpf: #244 BPF_MAXINSNS: Call heavy transformations FAIL to prog_create err=-524 len=4096 test_bpf: #249 BPF_MAXINSNS: ld_abs+get_processor_id FAIL to prog_create err=-524 len=4096 test_bpf: #250 BPF_MAXINSNS: ld_abs+vlan_push/pop FAIL to select_runtime err=-524 Complete test result: https://pastebin.ubuntu.com/p/zMDwVjwF7X/ ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-123-generic 4.4.0-123.147 ProcVersionSignature: Ubuntu 4.4.0-123.147-generic 4.4.128 Uname: Linux 4.4.0-123-generic s390x NonfreeKernelModules: zfs zunicode zcommon znvpair zavl AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.16 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Wed May 2 03:45:22 2018 HibernationDevice: RESUME=UUID=f578fa27-1d57-41c9-bb1d-7ff64c1c9345 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb' ProcKernelCmdLine: root=UUID=f26894a2-496d-4891-aa9a-f66344c9 crashkernel=196M BOOT_IMAGE=0 RelatedPackageVersions: linux-restricted-modules-4.4.0-123-generic N/A linux-backports-modules-4.4.0-123-generic N/A linux-firmware 1.157.17 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1768452/+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 1801642] Re: Bluetooth mouse sleep after 5 seconds of inactivity
My apology, I found the issue is due to canonical-livepatch (which is LTS-only). Issue resolved after removing it. ** Changed in: bluez (Ubuntu) Status: Incomplete => Invalid -- 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/1801642 Title: Bluetooth mouse sleep after 5 seconds of inactivity Status in bluez package in Ubuntu: Invalid Bug description: I'm having bluetooth mouse lag issue. After leaving it stationary for 5 seconds, I have to move it for 2 seconds before the pointer starts moving. I recently upgraded to Cosmic 3 days ago (from Bionic). There was no issue in the first 3 days, including after suspend/restart/shutdown. This issue only appears starting today. I tried: 1. Running 'bluetoothctl' and then 'scan off'. The command failed to run with 'Failed to stop discovery: org.bluez.Error.Failed'. 2. modprobe -r btusb, then modprobe it again. 3. sudo sh -c 'echo N > /sys/module/drm_kms_helper/parameters/poll' 4. Disabling wifi. $ apt-cache policy bluez 5.50-0ubuntu1 $uname -a; lspci -nnk | grep -iA2 net; lsusb; dmesg | grep -i bluetooth; dmesg | grep -i firmware; lsmod | grep bluetooth 4.18.0-10-generic #11 02:00.0 Network controller [0280]: Intel Corporation Wireless 7260 [8086:08b1] (rev 73) Subsystem: Intel Corporation Dual Band Wireless-N 7260 [8086:4460] Kernel driver in use: iwlwifi 03:00.1 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 12) Subsystem: Dell RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [1028:05f9] Kernel driver in use: r8169 Kernel modules: r8169 Bus 001 Device 002: ID 8087:8000 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 003: ID 17e9:4301 DisplayLink Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 047: ID 04f3:0206 Elan Microelectronics Corp. Bus 002 Device 006: ID 8087:07dc Intel Corp. Bus 002 Device 034: ID 0461:4d51 Primax Electronics, Ltd 0Y357C PMX-MMOCZUL (B) [Dell Laser Mouse] Bus 002 Device 118: ID 0853:0132 Topre Corporation Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub [ 287.361153] hid-generic 0005:046D:B012.0005: input,hidraw2: BLUETOOTH HID v0.14 Keyboard [MX Master] on FC:F8:AE:33:C7:31 bluetooth 548864 33 btrtl,btintel,btbcm,bnep,btusb,rfcomm ecdh_generic 24576 2 bluetooth ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: bluez 5.50-0ubuntu1 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 CurrentDesktop: MATE Date: Mon Nov 5 13:40:01 2018 InstallationDate: Installed on 2018-07-08 (119 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. Inspiron 7537 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic root=/dev/mapper/ubuntu--mate--vg-root ro ipv6.disable=1 quiet splash i915.enable_psr=0 SourcePackage: bluez UpgradeStatus: Upgraded to cosmic on 2018-11-02 (3 days ago) dmi.bios.date: 10/31/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 07PF9F dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA05:bd10/31/2013:svnDellInc.:pnInspiron7537:pvr:rvnDellInc.:rn07PF9F:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.family: Shark Bay ULT dmi.product.name: Inspiron 7537 dmi.product.sku: Inspiron 7537 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: FC:F8:AE:33:C7:31 ACL MTU: 1021:5 SCO MTU: 96:5 UP RUNNING RX bytes:2380 acl:32 sco:0 events:208 errors:0 TX bytes:28560 acl:29 sco:0 commands:170 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1801642/+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 1633223] Comment bridged from LTC Bugzilla
--- Comment From vipar...@in.ibm.com 2018-11-05 00:32 EDT--- (In reply to comment #37) > We haven't seen the problem since moving to (and beyond) the kernel and > NVIDIA driver levels in my previous update. > > Feel free to close. Thank you! Closing in LTC bugzilla. -- 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/1633223 Title: rcu_sched detected stalls with kernel 3.19.0-58, NVIDIA driver, and docker Status in linux package in Ubuntu: Invalid Bug description: ---Problem Description--- Seeing occasional rcu_sched detected stalls on 14.04 LTS with kernel 3.19.0-58. The system is running docker containers, and has the NVIDIA GPU driver loaded. We've seen about 4 stalls in the last month, all with the 3.19.0-58 kernel, and with the NVIDIA 352.93 and 361.49 drivers. ---uname output--- Linux dldev1 3.19.0-58-generic #64~14.04.1-Ubuntu SMP Fri Mar 18 19:05:01 UTC 2016 ppc64le ppc64le ppc64le GNU/Linux ---Additional Hardware Info--- 2 x NVIDIA K80 GPU adapter: $ lspci | grep NV 0002:03:00.0 3D controller: NVIDIA Corporation GK210GL [Tesla K80] (rev a1) 0002:04:00.0 3D controller: NVIDIA Corporation GK210GL [Tesla K80] (rev a1) 0006:03:00.0 3D controller: NVIDIA Corporation GK210GL [Tesla K80] (rev a1) 0006:04:00.0 3D controller: NVIDIA Corporation GK210GL [Tesla K80] (rev a1) Machine Type = 8247-42L ---System Hang--- Usual symptom is that the system is unresponsive except maybe for ping and writing the stall-detection messages to the console. Login/getty isn't available either via ssh nor on the console. System must be power cycled to recover. Attached is the kernel log from a stall detection on May 18th. The detection first occurs at: May 18 15:17:55. The system is later rebooted and those messages indicate the kernel (3.19.0-58) and NVIDIA driver version (352.93) that were active at the time. We've suffered 3 or 4 stalls since, all with the same kernel, but some with a newer NVIDIA driver (361.49). Unfortunately, information about the newer stalls wasn't preserved in the various log files (and we're not capturing the console constantly), so we don't have detailed data for those. We'd welcome any suggestions for how to collect additional data for these occurrences. I can't say for sure that we haven't seen the stalls on other systems, but they're occuring fairly frequently on this system, and it's unusual in that it's running both Docker and NVIDIA GPU driver. So maybe aufs or the NVIDIA driver are somehow involved. From the kern.log, The Call trace points to some kind of deadlock in aufs - May 18 15:17:55 dldev1 kernel: [713670.798624] Task dump for CPU 3: May 18 15:17:55 dldev1 kernel: [713670.798628] cc1 R running task0 99183 99173 0x00040004 May 18 15:17:55 dldev1 kernel: [713670.798633] Call Trace: May 18 15:17:55 dldev1 kernel: [713670.798643] [c00fa64673a0] [c00cf004] wake_up_worker+0x44/0x60 (unreliable) May 18 15:17:55 dldev1 kernel: [713670.798671] [c00fa6467570] [c00fa64675d0] 0xc00fa64675d0 May 18 15:17:55 dldev1 kernel: [713670.798676] [c00fa64675d0] [c0a1b050] __schedule+0x370/0x900 May 18 15:17:55 dldev1 kernel: [713670.798679] [c00fa64677f0] [c00fa6467850] 0xc00fa6467850 May 18 15:17:55 dldev1 kernel: [713670.798682] Task dump for CPU 75: May 18 15:17:55 dldev1 kernel: [713670.798684] cc1 D 105d9410 0 99427 99405 0x00040004 May 18 15:17:55 dldev1 kernel: [713670.798688] Call Trace: May 18 15:17:55 dldev1 kernel: [713670.798691] [c017efdd3460] [c017efdd34a0] 0xc017efdd34a0 (unreliable) May 18 15:17:55 dldev1 kernel: [713670.798695] [c017efdd3630] [c017efdd3690] 0xc017efdd3690 May 18 15:17:55 dldev1 kernel: [713670.798698] [c017efdd3690] [c0a1b050] __schedule+0x370/0x900 May 18 15:17:55 dldev1 kernel: [713670.798702] [c017efdd38b0] [c0a1f128] rwsem_down_write_failed+0x288/0x400 May 18 15:17:55 dldev1 kernel: [713670.798706] [c017efdd3940] [c0a1e538] down_write+0x88/0x90 May 18 15:17:55 dldev1 kernel: [713670.798716] [c017efdd3970] [d0001ead562c] do_ii_write_lock+0x8c/0xd0 [aufs] May 18 15:17:55 dldev1 kernel: [713670.798724] [c017efdd39a0] [d0001eac0e98] aufs_read_lock+0xb8/0xd0 [aufs] May 18 15:17:55 dldev1 kernel: [713670.798733] [c017efdd39e0] [d0001ead8208] aufs_d_revalidate+0x98/0x7a0 [aufs] May 18 15:17:55 dldev1 kernel: [713670.798737] [c017efdd3aa0] [c02c88f8] lookup_fast+0x368/0x3b0 May 18 15:17:55 dldev1 kernel: [713670.798740] [c017efdd3b10] [c02cb620] path_lookupat+0x180/0x970 May 18 15:17:55 dldev1 kernel: [713670.798743] [c017efdd3be0] [c02cbe68] filename_lookup+0x58/0x140 May 18 15:17:55
[Kernel-packages] [Bug 1787197] Re: Touchpad doesn't work well after upgrade to 18.04
[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/1787197 Title: Touchpad doesn't work well after upgrade to 18.04 Status in linux package in Ubuntu: Expired Bug description: I upgraded my laptop (Dell XPS 13, older version) to 18.04. Now the touchpad doesn't work, unless I hit it very hard. How do I increase the sensitivity of the touchpad so I can use it like I've always done? It always worked well, until the upgrade. --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: christine 3495 F pulseaudio /dev/snd/controlC0: christine 3495 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=1212abb0-90f7-4f0a-94bf-0d790e8b3593 InstallationDate: Installed on 2015-12-13 (975 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: MSI MS-7881 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-124-generic.efi.signed root=UUID=eea1d4c7-5f21-40a5-b73d-fed6b0a48f69 ro noprompt persistent quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-124.148-generic 4.4.117 RelatedPackageVersions: linux-restricted-modules-4.4.0-124-generic N/A linux-backports-modules-4.4.0-124-generic N/A linux-firmware 1.157.20 RfKill: Tags: xenial Uname: Linux 4.4.0-124-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip libvirtd lpadmin plugdev sambashare staff sudo _MarkForUpload: True dmi.bios.date: 10/30/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.80 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X99S XPOWER AC (MS-7881) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.80:bd10/30/2015:svnMSI:pnMS-7881:pvr1.0:rvnMSI:rnX99SXPOWERAC(MS-7881):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.name: MS-7881 dmi.product.version: 1.0 dmi.sys.vendor: MSI --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: christine 3495 F pulseaudio /dev/snd/controlC0: christine 3495 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=1212abb0-90f7-4f0a-94bf-0d790e8b3593 InstallationDate: Installed on 2015-12-13 (975 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: MSI MS-7881 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-124-generic.efi.signed root=UUID=eea1d4c7-5f21-40a5-b73d-fed6b0a48f69 ro noprompt persistent quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-124.148-generic 4.4.117 RelatedPackageVersions: linux-restricted-modules-4.4.0-124-generic N/A linux-backports-modules-4.4.0-124-generic N/A linux-firmware 1.157.20 RfKill: Tags: xenial Uname: Linux 4.4.0-124-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip libvirtd lpadmin plugdev sambashare staff sudo _MarkForUpload: True dmi.bios.date: 10/30/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.80 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X99S XPOWER AC (MS-7881) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.80:bd10/30/2015:svnMSI:pnMS-7881:pvr1.0:rvnMSI:rnX99SXPOWERAC(MS-7881):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.name: MS-7881 dmi.product.version: 1.0 dmi.sys.vendor: MSI --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: christine 2392 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=c69aa18c-fc75-4cb1-bc81-92c17d2866a9 InstallationDate: Installed on 2014-01-04 (1683 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: Dell Inc. Dell System XPS L322X Package: linux (not installe
[Kernel-packages] [Bug 1790288] Re: package linux-modules-4.15.0-33-generic 4.15.0-33.36 failed to install/upgrade: unable to create new file '/var/lib/dpkg/info/linux-modules-4.15.0-33-generic.list-n
[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/1790288 Title: package linux-modules-4.15.0-33-generic 4.15.0-33.36 failed to install/upgrade: unable to create new file '/var/lib/dpkg/info/linux- modules-4.15.0-33-generic.list-new': Operation not permitted Status in linux package in Ubuntu: Expired Bug description: Auto updating from GUI ProblemType: Package DistroRelease: Ubuntu 18.04 Package: linux-modules-4.15.0-33-generic 4.15.0-33.36 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Sat Sep 1 07:08:50 2018 Dependencies: DuplicateSignature: package:linux-modules-4.15.0-33-generic:4.15.0-33.36 Unpacking linux-modules-4.15.0-33-generic (4.15.0-33.36) ... dpkg: error processing archive /tmp/apt-dpkg-install-1UNenn/28-linux-modules-4.15.0-33-generic_4.15.0-33.36_amd64.deb (--unpack): unable to create new file '/var/lib/dpkg/info/linux-modules-4.15.0-33-generic.list-new': Operation not permitted ErrorMessage: unable to create new file '/var/lib/dpkg/info/linux-modules-4.15.0-33-generic.list-new': Operation not permitted InstallationDate: Installed on 2018-08-21 (10 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. Inspiron 7547 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic root=UUID=523d3588-b4ed-4731-b7dc-308a13f2fa0b ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: grub-pc 2.02-2ubuntu8.3 SourcePackage: linux Title: package linux-modules-4.15.0-33-generic 4.15.0-33.36 failed to install/upgrade: unable to create new file '/var/lib/dpkg/info/linux-modules-4.15.0-33-generic.list-new': Operation not permitted UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/20/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0AM680 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA08:bd10/20/2015:svnDellInc.:pnInspiron7547:pvrNotSpecified:rvnDellInc.:rn0AM680:rvrA00:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.family: Shark Bay ULT dmi.product.name: Inspiron 7547 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1790288/+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 1789946] Re: DHCP server and client not working since kernel 4.15.0-32
[Expired for linux (Ubuntu Bionic) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu Bionic) 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/1789946 Title: DHCP server and client not working since kernel 4.15.0-32 Status in linux package in Ubuntu: Expired Status in linux source package in Bionic: Expired Bug description: I installed Ubuntu server 18.04 on HP Proliant BL460c Gen8 server blades. I set up DHCP server for PXE boot. It was working, but since kernel update with version 4.15.0-32, PXE boot no longer works. DHCP server logs show "5 bad udp checksums in 5 packets" in a row. DHCP client is also not working on the machine due to similar errors. I switched back to kernel version 4.15-0-29 and it works again. I suspect the newer kernel might have introduced a bug about the network adapter driver. Thanks. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-32-generic 4.15.0-32.35 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Aug 30 08:56 seq crw-rw 1 root audio 116, 33 Aug 30 08:56 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Thu Aug 30 09:08:11 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: HP ProLiant BL460c Gen8 PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic root=UUID=0a9aa0b0-9a67-11e8-a1dc-fc15b41d0ee0 ro maybe-ubiquity RelatedPackageVersions: linux-restricted-modules-4.15.0-32-generic N/A linux-backports-modules-4.15.0-32-generic N/A linux-firmware 1.173.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/20/2013 dmi.bios.vendor: HP dmi.bios.version: I31 dmi.chassis.type: 28 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrI31:bd12/20/2013:svnHP:pnProLiantBL460cGen8:pvr:cvnHP:ct28:cvr: dmi.product.family: ProLiant dmi.product.name: ProLiant BL460c Gen8 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1789946/+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 1790029] Re: Static white noise and slight popping in headphones after suspend
[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/1790029 Title: Static white noise and slight popping in headphones after suspend Status in linux package in Ubuntu: Expired Bug description: Whenever I resume from suspend, there is a very slight high pitched white noise in my headphones when I plug it in that was not present when I first boot the computer. Sounds still play fine on top of the white noise, but it persists. Various solutions online, such as messing with alsa-tools and alsamixer and powersave and hda-verb don't work. 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 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: claiye 2660 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Aug 30 22:12:51 2018 InstallationDate: Installed on 2018-08-27 (3 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 8087:0a2a Intel Corp. Bus 001 Device 002: ID 04f2:b3fd Chicony Electronics Co., Ltd Bus 001 Device 004: ID 0457:10cc Silicon Integrated Systems Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. N501VW ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic root=UUID=b3941e7c-43a6-4455-8a79-ad5bf33c75d7 ro 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: 04/19/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N501VW.305 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N501VW dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN501VW.305:bd04/19/2017:svnASUSTeKCOMPUTERINC.:pnN501VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN501VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: N dmi.product.name: N501VW 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/1790029/+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 1789756] Re: Swap not being used, RAM not being released, CPU use at 100%
[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/1789756 Title: Swap not being used, RAM not being released, CPU use at 100% Status in linux package in Ubuntu: Expired Bug description: Memory usage continues to climb to 100%, even as applications are shut down. Swap file is not being used. CPU usage climbs to %100 even as applications are shut down. After reboot, system will operate normally for a number of hours, until a virtual machine (Virtual Box) is run. At this point memory and CPU usage will climb until %100. Exiting programs and closing the VM does not resolve the issue. More information in this thread, started by me: https://discourse.ubuntubudgie.org/t/high-ram-use-no-swap-use/940/9 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-33-generic 4.15.0-33.36 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: cortimi1688 F pulseaudio /dev/snd/controlC1: cortimi1688 F pulseaudio /dev/snd/controlC0: cortimi1688 F pulseaudio CurrentDesktop: Budgie:GNOME Date: Wed Aug 29 17:39:45 2018 InstallationDate: Installed on 2018-08-23 (6 days ago) InstallationMedia: Ubuntu-Budgie 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725.1) MachineType: MSI MS-7817 ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic root=UUID=10f46365-0845-48bb-a427-fe155f6085c0 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-33-generic N/A linux-backports-modules-4.15.0-33-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: 03/30/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V1.9 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-P33 (MS-7817) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV1.9:bd03/30/2015:svnMSI:pnMS-7817:pvr1.0:rvnMSI:rnH81M-P33(MS-7817):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7817 dmi.product.version: 1.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1789756/+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 1790354] Re: Display refresh rate is not stored
[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/1790354 Title: Display refresh rate is not stored Status in linux package in Ubuntu: Expired Bug description: After upgrade from 16.04 to 18.04, I cannot store the manual refresh rate any longer. When I go to the display settings, advanced, and store e.g. 25,00 Hz, 'Apply', go elsewhere and back to advanced display settings, it has fallen back to 'Auto'. i tried a number of times, including reboots, but it used to come back as 'Auto'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1790354/+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 1789946] Re: DHCP server and client not working since kernel 4.15.0-32
[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/1789946 Title: DHCP server and client not working since kernel 4.15.0-32 Status in linux package in Ubuntu: Expired Status in linux source package in Bionic: Expired Bug description: I installed Ubuntu server 18.04 on HP Proliant BL460c Gen8 server blades. I set up DHCP server for PXE boot. It was working, but since kernel update with version 4.15.0-32, PXE boot no longer works. DHCP server logs show "5 bad udp checksums in 5 packets" in a row. DHCP client is also not working on the machine due to similar errors. I switched back to kernel version 4.15-0-29 and it works again. I suspect the newer kernel might have introduced a bug about the network adapter driver. Thanks. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-32-generic 4.15.0-32.35 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Aug 30 08:56 seq crw-rw 1 root audio 116, 33 Aug 30 08:56 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Thu Aug 30 09:08:11 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: HP ProLiant BL460c Gen8 PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic root=UUID=0a9aa0b0-9a67-11e8-a1dc-fc15b41d0ee0 ro maybe-ubiquity RelatedPackageVersions: linux-restricted-modules-4.15.0-32-generic N/A linux-backports-modules-4.15.0-32-generic N/A linux-firmware 1.173.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/20/2013 dmi.bios.vendor: HP dmi.bios.version: I31 dmi.chassis.type: 28 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrI31:bd12/20/2013:svnHP:pnProLiantBL460cGen8:pvr:cvnHP:ct28:cvr: dmi.product.family: ProLiant dmi.product.name: ProLiant BL460c Gen8 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1789946/+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 1775487] Re: Sandisk Ultra USB 3.0 Flash Drive doesn't work in USB 3 ports
[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/1775487 Title: Sandisk Ultra USB 3.0 Flash Drive doesn't work in USB 3 ports Status in linux package in Ubuntu: Expired Bug description: I have a 128 GB Sandisk Ultra USB Flash Drive. It works when I plug it into a USB 2.0 port, or if I partially insert it into a USB 3.0 port (so the USB 3 pins don't make contact). Here's what lsusb says about it: Bus 001 Device 005: ID 0781:5581 SanDisk Corp. Ultra And dmesg from a successful connection: [ 1269.667097] usb 3-1.4: new high-speed USB device number 6 using xhci_hcd [ 1269.779871] usb 3-1.4: New USB device found, idVendor=0781, idProduct=5581 [ 1269.779875] usb 3-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 1269.779878] usb 3-1.4: Product: Ultra [ 1269.779880] usb 3-1.4: Manufacturer: SanDisk [ 1269.779883] usb 3-1.4: SerialNumber: 4C530001080228105161 [ 1269.780937] usb-storage 3-1.4:1.0: USB Mass Storage device detected [ 1269.781346] scsi host10: usb-storage 3-1.4:1.0 [ 1270.800187] scsi 10:0:0:0: Direct-Access SanDisk Ultra 1.00 PQ: 0 ANSI: 6 [ 1270.800733] sd 10:0:0:0: Attached scsi generic sg3 type 0 [ 1270.800919] sd 10:0:0:0: [sdd] 240254976 512-byte logical blocks: (123 GB/115 GiB) [ 1270.801887] sd 10:0:0:0: [sdd] Write Protect is off [ 1270.801891] sd 10:0:0:0: [sdd] Mode Sense: 43 00 00 00 [ 1270.802269] sd 10:0:0:0: [sdd] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA [ 1270.811703] sdd: sdd1 [ 1270.813869] sd 10:0:0:0: [sdd] Attached SCSI removable disk But if I insert the drive all the way into a USB 3.0 port on a hub, I get nothing. And on a USB 3.0 port on the machine directly, I get this in dmesg: [ 1395.230629] xhci_hcd :03:00.0: Cannot set link state. [ 1395.230641] usb usb2-port4: cannot disable (err = -32) [ 1396.966273] xhci_hcd :03:00.0: Cannot set link state. [ 1396.966285] usb usb2-port4: cannot disable (err = -32) [ 1398.706493] xhci_hcd :03:00.0: Cannot set link state. [ 1398.706505] usb usb2-port4: cannot disable (err = -32) [ 1400.446161] xhci_hcd :03:00.0: Cannot set link state. [ 1400.446172] usb usb2-port4: cannot disable (err = -32) [ 1402.182073] xhci_hcd :03:00.0: Cannot set link state. [ 1402.182085] usb usb2-port4: cannot disable (err = -32) ...repeats until unplugged... It doesn't show up in lsusb in the USB 3.0 port. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-22-generic 4.15.0-22.24 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jun 6 18:22:35 2018 GvfsMonitorError: This tool has been deprecated, use 'gio mount' instead. See 'gio help mount' for more info. HotplugNewDevices: HotplugNewMounts: InstallationDate: Installed on 2017-08-06 (304 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed Symptom: storage UpgradeStatus: Upgraded to bionic on 2018-05-29 (8 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775487/+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 1790506] Re: Upgrading to 18.04.1 from 17.10
[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/1790506 Title: Upgrading to 18.04.1 from 17.10 Status in linux package in Ubuntu: Expired Bug description: I have a HP Mini 210-1170NR that I have been using since Ubuntu 14 I believe. I have at it at 16 and currently (recently re-install 17.10 because of the possible "bug" in upgrading to 18.10.1 or even a fresh install of 18.10.1 on this same system. I believe I do remembering upgrading to 18.10 with success, but when it tries to go to 18.10.1 that is where the issue occurs. Through at least 3 attempts to upgrade my laptop to 18.10.1 it will go through the upgrade with out any errors or warnings until it does the last reboot into the updated version. It will bring up the screen that just has Ubuntu on it with the row of dots, it will go through at least one cycle of changing the colors of the dots, it will display the mouse pointer, which will not move when the mouse is moved, there will be some activity on the drive (the drive light will flash for about 5 minutes, but not sure of the exact time) then even it will not flash anymore. The screen will go blank after no activity, but moving the mouse or clicking on keys will not cause the screen to turn the display back on. Since the information gathered here is more for a working system and not the system that is having issues, and I seem to be able to re-create the issue at will, I will try and proceed with the upgrade to 18.10.1 and see if it "works" this time. What I can use from you is maybe an iso or instructions to possibly gather additional information that could be used to determine why it is not completing the update process. Any assistants you can provide will be gratefully appreciated. This is an old windows system that I put Ubuntu on and it could be I go back to 16.. and leave it there. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-46-generic 4.13.0-46.51 ProcVersionSignature: Ubuntu 4.13.0-46.51-generic 4.13.16 Uname: Linux 4.13.0-46-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: james 1317 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Sep 3 09:08:40 2018 HibernationDevice: RESUME=UUID=393e2e20-215e-4082-bca5-cc6f1a2f5b85 InstallationDate: Installed on 2018-09-02 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) MachineType: Hewlett-Packard HP Mini 210-1100 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-46-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-46-generic N/A linux-backports-modules-4.13.0-46-generic N/A linux-firmware 1.169.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/18/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.24 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 3660 dmi.board.vendor: Hewlett-Packard dmi.board.version: 48.26 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: N/A dmi.modalias: dmi:bvnHewlett-Packard:bvrF.24:bd03/18/2011:svnHewlett-Packard:pnHPMini210-1100:pvr049111202B030:rvnHewlett-Packard:rn3660:rvr48.26:cvnHewlett-Packard:ct10:cvrN/A: dmi.product.family: 103C_5335KV dmi.product.name: HP Mini 210-1100 dmi.product.version: 049111202B030 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1790506/+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 1790560] Re: package linux-headers-4.4.0-47-generic 4.4.0-47.68 failed to install/upgrade: package linux-headers-4.4.0-47-generic is not ready for configuration cannot configure
[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/1790560 Title: package linux-headers-4.4.0-47-generic 4.4.0-47.68 failed to install/upgrade: package linux-headers-4.4.0-47-generic is not ready for configuration cannot configure (current status 'half-installed') Status in linux package in Ubuntu: Expired Bug description: can't boot up Ubuntu in regular startup mode ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-headers-4.4.0-47-generic 4.4.0-47.68 ProcVersionSignature: Ubuntu 4.4.0-134.160-generic 4.4.140 Uname: Linux 4.4.0-134-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jp 1816 F pulseaudio Date: Mon Sep 3 21:03:59 2018 DpkgHistoryLog: Start-Date: 2018-09-03 21:02:47 Requested-By: jp (1000) Upgrade: update-manager-core:amd64 (1:16.04.12, 1:16.04.13), libsystemd0:amd64 (229-4ubuntu21.2, 229-4ubuntu21.4), update-manager:amd64 (1:16.04.12, 1:16.04.13), gnome-software:amd64 (3.20.5-0ubuntu0.16.04.10, 3.20.5-0ubuntu0.16.04.11), udev:amd64 (229-4ubuntu21.2, 229-4ubuntu21.4), libudev1:amd64 (229-4ubuntu21.2, 229-4ubuntu21.4), ubuntu-software:amd64 (3.20.5-0ubuntu0.16.04.10, 3.20.5-0ubuntu0.16.04.11), python3-update-manager:amd64 (1:16.04.12, 1:16.04.13), systemd-sysv:amd64 (229-4ubuntu21.2, 229-4ubuntu21.4), libpam-systemd:amd64 (229-4ubuntu21.2, 229-4ubuntu21.4), systemd:amd64 (229-4ubuntu21.2, 229-4ubuntu21.4), gnome-software-common:amd64 (3.20.5-0ubuntu0.16.04.10, 3.20.5-0ubuntu0.16.04.11) DuplicateSignature: package:linux-headers-4.4.0-47-generic:4.4.0-47.68 Processing triggers for hicolor-icon-theme (0.15-0ubuntu1.1) ... dpkg: error processing package linux-headers-4.4.0-47-generic (--configure): package linux-headers-4.4.0-47-generic is not ready for configuration ErrorMessage: package linux-headers-4.4.0-47-generic is not ready for configuration cannot configure (current status 'half-installed') HibernationDevice: RESUME=UUID=e6421112-f714-4d3d-8304-e7118d3a9a84 InstallationDate: Installed on 2016-08-03 (761 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: Dell Inc. Vostro 1000 ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-134-generic root=UUID=aeb7db14-ed22-4d5e-9a0f-58f0b72e8be5 ro recovery nomodeset PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.18 SourcePackage: linux Title: package linux-headers-4.4.0-47-generic 4.4.0-47.68 failed to install/upgrade: package linux-headers-4.4.0-47-generic is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/07/2007 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.6.3 dmi.board.name: 0WY383 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr2.6.3:bd12/07/2007:svnDellInc.:pnVostro1000:pvrNotSpecified:rvnDellInc.:rn0WY383:rvr:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Vostro 1000 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1790560/+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 1801642] Re: Bluetooth mouse sleep after 5 seconds of inactivity
1. If you have 'tlp' installed then please try removing that. 2. If #1 has not solved the problem then please install 'powertop'. Now run: sudo powertop and keep pressing Tab till you reach the "Tunables" section. Find your mouse in that list ("Autosuspend for USB device..."). Does it show a "Good" or "Bad" value? ** Changed in: bluez (Ubuntu) Status: New => Incomplete -- 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/1801642 Title: Bluetooth mouse sleep after 5 seconds of inactivity Status in bluez package in Ubuntu: Incomplete Bug description: I'm having bluetooth mouse lag issue. After leaving it stationary for 5 seconds, I have to move it for 2 seconds before the pointer starts moving. I recently upgraded to Cosmic 3 days ago (from Bionic). There was no issue in the first 3 days, including after suspend/restart/shutdown. This issue only appears starting today. I tried: 1. Running 'bluetoothctl' and then 'scan off'. The command failed to run with 'Failed to stop discovery: org.bluez.Error.Failed'. 2. modprobe -r btusb, then modprobe it again. 3. sudo sh -c 'echo N > /sys/module/drm_kms_helper/parameters/poll' 4. Disabling wifi. $ apt-cache policy bluez 5.50-0ubuntu1 $uname -a; lspci -nnk | grep -iA2 net; lsusb; dmesg | grep -i bluetooth; dmesg | grep -i firmware; lsmod | grep bluetooth 4.18.0-10-generic #11 02:00.0 Network controller [0280]: Intel Corporation Wireless 7260 [8086:08b1] (rev 73) Subsystem: Intel Corporation Dual Band Wireless-N 7260 [8086:4460] Kernel driver in use: iwlwifi 03:00.1 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 12) Subsystem: Dell RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [1028:05f9] Kernel driver in use: r8169 Kernel modules: r8169 Bus 001 Device 002: ID 8087:8000 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 003: ID 17e9:4301 DisplayLink Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 047: ID 04f3:0206 Elan Microelectronics Corp. Bus 002 Device 006: ID 8087:07dc Intel Corp. Bus 002 Device 034: ID 0461:4d51 Primax Electronics, Ltd 0Y357C PMX-MMOCZUL (B) [Dell Laser Mouse] Bus 002 Device 118: ID 0853:0132 Topre Corporation Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub [ 287.361153] hid-generic 0005:046D:B012.0005: input,hidraw2: BLUETOOTH HID v0.14 Keyboard [MX Master] on FC:F8:AE:33:C7:31 bluetooth 548864 33 btrtl,btintel,btbcm,bnep,btusb,rfcomm ecdh_generic 24576 2 bluetooth ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: bluez 5.50-0ubuntu1 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 CurrentDesktop: MATE Date: Mon Nov 5 13:40:01 2018 InstallationDate: Installed on 2018-07-08 (119 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. Inspiron 7537 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic root=/dev/mapper/ubuntu--mate--vg-root ro ipv6.disable=1 quiet splash i915.enable_psr=0 SourcePackage: bluez UpgradeStatus: Upgraded to cosmic on 2018-11-02 (3 days ago) dmi.bios.date: 10/31/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 07PF9F dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA05:bd10/31/2013:svnDellInc.:pnInspiron7537:pvr:rvnDellInc.:rn07PF9F:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.family: Shark Bay ULT dmi.product.name: Inspiron 7537 dmi.product.sku: Inspiron 7537 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: FC:F8:AE:33:C7:31 ACL MTU: 1021:5 SCO MTU: 96:5 UP RUNNING RX bytes:2380 acl:32 sco:0 events:208 errors:0 TX bytes:28560 acl:29 sco:0 commands:170 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1801642/+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 1800877] Re: iproute2/xenial: Add support for the VF Trust setting (fix IPv6 multicast under SR-IOV on Mellanox adapters)
Sponsored ! It is now waiting on SRU team for approval for the package to start building and be published in xenial-proposed. Once the package found in xenial-proposed, please keep an eye here : (to make sure everything looks good) https://people.canonical.com/~ubuntu-archive/pending-sru.html Thanks Mauricio ! - Eric -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to iproute2 in Ubuntu. Matching subscriptions: iproute2 https://bugs.launchpad.net/bugs/1800877 Title: iproute2/xenial: Add support for the VF Trust setting (fix IPv6 multicast under SR-IOV on Mellanox adapters) Status in iproute2 package in Ubuntu: Fix Released Status in iproute2 source package in Xenial: In Progress Bug description: [Impact] * An VM's VF cannot receive IPv6 multicast traffic from other VMs' VFs in the same Mellanox adapter _if_ its VF trust setting is not enabled, and on Xenial currently iproute2 _cannot_ enable it. * This breaks IPv6 NDP (Neighbor Discovery Protocol) in that scenario. * This upload adds three iproute2 upstream commits to enable/disable the VF setting, which resolves that problem/limitation. [Test Case] * Check 'ip link help' for the 'trust' option: Before: # ip link help 2>&1 | grep trust After: # ip link help 2>&1 | grep trust [ trust { on | off} ] ] * Check 'ip link show dev PF' for 'trust on|off' field in VFs. Before: (trust field _is not_ present) # ip link show dev ens1f0 ... vf 0 MAC 00:00:00:00:00:00, spoof checking on, link-state auto vf 1 MAC 00:00:00:00:00:00, spoof checking on, link-state auto After: (trust field _is_ present) # ip link show dev ens1f0 ... vf 0 MAC 00:00:00:00:00:00, spoof checking on, link-state auto, trust off vf 1 MAC 00:00:00:00:00:00, spoof checking on, link-state auto, trust off * Set the VF trust on/off and check it: Set VF 0 trust on: # ip link set ens1f0 vf 0 trust on # ip link show dev ens1f0 | grep trust vf 0 MAC 00:00:00:00:00:00, spoof checking on, link-state auto, trust on vf 1 MAC 00:00:00:00:00:00, spoof checking on, link-state auto, trust off Set VF 0 trust off: # ip link set ens1f0 vf 0 trust off # ip link show dev ens1f0 | grep trust vf 0 MAC 00:00:00:00:00:00, spoof checking on, link-state auto, trust off vf 1 MAC 00:00:00:00:00:00, spoof checking on, link-state auto, trust off [Regression Potential] * Regression potential is low because the commits just add the netlink attribute for the userspace-kernel interface and the ways to set/clear it, and show the current value to the user. * Regressions could happen _if_ the user turns the setting on (it's disabled by default) and there's a problem/bug likely in _other_ component that depends on that setting (which is something to fix on such component). [Other Info] * The users that reported this problem have verified the test package with these changes, and confirmed that it now works correctly for IPv6 NDP/multicast. * Upstream commits: https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=dddf1b44126e https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=fe9322781e63 https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=b6d77d9ee312 * Only affect Xenial release : # rmadison iproute2 iproute2 | 4.3.0-1ubuntu3.16.04.3 | xenial-updates iproute2 | 4.15.0-2ubuntu1| bionic iproute2 | 4.18.0-1ubuntu2| cosmic iproute2 | 4.18.0-1ubuntu2| disco # iproute2 upstream vcs $ git describe --contains dddf1b44126e v4.4.0~67 $ git describe --contains b6d77d9ee312 v4.5.0~47 $ git describe --contains fe9322781e63 v4.6.0~32 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1800877/+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 1801573] Re: pc randomly freeze
Look like this is an issue of graphic driver (amdgpu). Please do a test: add nomodeset in the boot parameter from grub, then boot the system. Make sure the X11 is working in framebuffer mode. (lsmod | grep amdgpu; make sure the amdgpu is not loaded). Then test if it still hang randomly. -- 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/1801573 Title: pc randomly freeze Status in linux package in Ubuntu: Confirmed Bug description: pc with ubuntu 18.04 randomly freeze and i'm forced to turn it off. This often happens while playing VLC 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: plraska8379 F pulseaudio /dev/snd/controlC0: plraska8379 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Nov 4 08:23:54 2018 InstallationDate: Installed on 2018-10-03 (31 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: HP HP Laptop 15-db0xxx ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic root=UUID=c1c43279-03a7-4d7e-8b7e-9b999190af0a 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 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/26/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.03 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 84AE dmi.board.vendor: HP dmi.board.version: 86.19 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.03:bd04/26/2018:svnHP:pnHPLaptop15-db0xxx:pvrType1ProductConfigId:rvnHP:rn84AE:rvr86.19:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15-db0xxx dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801573/+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 1801642] [NEW] Bluetooth mouse sleep after 5 seconds of inactivity
Public bug reported: I'm having bluetooth mouse lag issue. After leaving it stationary for 5 seconds, I have to move it for 2 seconds before the pointer starts moving. I recently upgraded to Cosmic 3 days ago (from Bionic). There was no issue in the first 3 days, including after suspend/restart/shutdown. This issue only appears starting today. I tried: 1. Running 'bluetoothctl' and then 'scan off'. The command failed to run with 'Failed to stop discovery: org.bluez.Error.Failed'. 2. modprobe -r btusb, then modprobe it again. 3. sudo sh -c 'echo N > /sys/module/drm_kms_helper/parameters/poll' 4. Disabling wifi. $ apt-cache policy bluez 5.50-0ubuntu1 $uname -a; lspci -nnk | grep -iA2 net; lsusb; dmesg | grep -i bluetooth; dmesg | grep -i firmware; lsmod | grep bluetooth 4.18.0-10-generic #11 02:00.0 Network controller [0280]: Intel Corporation Wireless 7260 [8086:08b1] (rev 73) Subsystem: Intel Corporation Dual Band Wireless-N 7260 [8086:4460] Kernel driver in use: iwlwifi 03:00.1 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 12) Subsystem: Dell RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [1028:05f9] Kernel driver in use: r8169 Kernel modules: r8169 Bus 001 Device 002: ID 8087:8000 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 003: ID 17e9:4301 DisplayLink Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 047: ID 04f3:0206 Elan Microelectronics Corp. Bus 002 Device 006: ID 8087:07dc Intel Corp. Bus 002 Device 034: ID 0461:4d51 Primax Electronics, Ltd 0Y357C PMX-MMOCZUL (B) [Dell Laser Mouse] Bus 002 Device 118: ID 0853:0132 Topre Corporation Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub [ 287.361153] hid-generic 0005:046D:B012.0005: input,hidraw2: BLUETOOTH HID v0.14 Keyboard [MX Master] on FC:F8:AE:33:C7:31 bluetooth 548864 33 btrtl,btintel,btbcm,bnep,btusb,rfcomm ecdh_generic 24576 2 bluetooth ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: bluez 5.50-0ubuntu1 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 CurrentDesktop: MATE Date: Mon Nov 5 13:40:01 2018 InstallationDate: Installed on 2018-07-08 (119 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. Inspiron 7537 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic root=/dev/mapper/ubuntu--mate--vg-root ro ipv6.disable=1 quiet splash i915.enable_psr=0 SourcePackage: bluez UpgradeStatus: Upgraded to cosmic on 2018-11-02 (3 days ago) dmi.bios.date: 10/31/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 07PF9F dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA05:bd10/31/2013:svnDellInc.:pnInspiron7537:pvr:rvnDellInc.:rn07PF9F:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.family: Shark Bay ULT dmi.product.name: Inspiron 7537 dmi.product.sku: Inspiron 7537 dmi.sys.vendor: Dell Inc. hciconfig: hci0: Type: Primary Bus: USB BD Address: FC:F8:AE:33:C7:31 ACL MTU: 1021:5 SCO MTU: 96:5 UP RUNNING RX bytes:2380 acl:32 sco:0 events:208 errors:0 TX bytes:28560 acl:29 sco:0 commands:170 errors:0 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic -- 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/1801642 Title: Bluetooth mouse sleep after 5 seconds of inactivity Status in bluez package in Ubuntu: New Bug description: I'm having bluetooth mouse lag issue. After leaving it stationary for 5 seconds, I have to move it for 2 seconds before the pointer starts moving. I recently upgraded to Cosmic 3 days ago (from Bionic). There was no issue in the first 3 days, including after suspend/restart/shutdown. This issue only appears starting today. I tried: 1. Running 'bluetoothctl' and then 'scan off'. The command failed to run with 'Failed to stop discovery: org.bluez.Error.Failed'. 2. modprobe -r btusb, then modprobe it again. 3. sudo sh -c 'echo N > /sys/module/drm_kms_helper/parameters/poll' 4. Disabling wifi. $ apt-cache policy bluez 5.50-0ubuntu1 $uname -a; lspci -nnk | grep -iA2 net; lsusb; dmesg | grep -i bluetooth; dmesg | grep -i firmware; lsmod | grep bluetooth 4.18.0-10-generic #11 02:00.0 Network controller [0280]: Intel Corporation Wireless 7260 [8086:08b1] (rev 73) Subsystem: Intel Corporation Dual Band Wireless-N 7260 [8086:4460] Kernel driver in use: iwlwifi 03:00.1 Ethernet cont
[Kernel-packages] [Bug 1795292] Re: ELAN469D touch pad not working
Hmm I am out of any idea. Would it be possible to ask support from Lenovo? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1795292 Title: ELAN469D touch pad not working Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Bug description: I installed Bionic Beaver and now upgraded to Cosmic Cuttlefish on this Lenovo Ideapad 330S-15ARR laptop. The touch pad doesn't work in either. Some possibly relevant info from dmesg: i2c_hid i2c-ELAN469D:00: i2c-ELAN469D:00 supply vdd not found, using dummy regulator i2c_designware AMDI0010:01: controller timed out ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-7-generic 4.18.0-7.8 ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5 Uname: Linux 4.18.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: xorbit 2086 F pulseaudio /dev/snd/pcmC1D0p: xorbit 2086 F...m pulseaudio /dev/snd/controlC0: xorbit 2086 F pulseaudio CurrentDesktop: GNOME Date: Sun Sep 30 23:14:26 2018 InstallationDate: Installed on 2018-09-20 (10 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 81FB ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-7-generic root=UUID=4d91f09e-6122-4dd4-81fc-482465f8f0e7 ro noapic processor.max_cstate=1 rcu_nocbs=0-7 pcie_aspm=off pci=noaer quiet splash vt.handoff=1 elan_i2c.dyndbg=+p RelatedPackageVersions: linux-restricted-modules-4.18.0-7-generic N/A linux-backports-modules-4.18.0-7-generic N/A linux-firmware1.175 SourcePackage: linux UpgradeStatus: Upgraded to cosmic on 2018-09-30 (0 days ago) dmi.bios.date: 06/08/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 7WCN22WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 330S-15ARR dmi.modalias: dmi:bvnLENOVO:bvr7WCN22WW:bd06/08/2018:svnLENOVO:pn81FB:pvrLenovoideapad330S-15ARR:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad330S-15ARR: dmi.product.family: ideapad 330S-15ARR dmi.product.name: 81FB dmi.product.sku: LENOVO_MT_81FB_BU_idea_FM_ideapad 330S-15ARR dmi.product.version: Lenovo ideapad 330S-15ARR dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-09-20 (13 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Tags: cosmic Uname: Linux 4.19.0-041900rc6-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to cosmic on 2018-09-30 (2 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1795292/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1645540] Re: [Feature] Crystal Ridge 2LM error reporting
here are all commits: 4cf841e398503990df640f7a7c5b2ea56f11c08c 93ac57540e9129004b569beee54e50b3519b0b07 a324e9396ca3d00e1101476ba067b412e0aba232 ad6e16059d8e00de0887885db11d87cba0bd1512 e5276b1ffa97e3883802f40a5e3a167fe1cb1d20 ** Changed in: intel Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1645540 Title: [Feature] Crystal Ridge 2LM error reporting Status in intel: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Artful: Invalid Status in linux source package in Bionic: Fix Released Bug description: In 2LM configurations we need to error reports to differentiate between errors in the "near" memory (DRAM used as cache) and "far" memory (Crystal ridge memory) HW: Apache Pass Upstream schedule: kernel: 4.19 Target Release: 19.04 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1645540/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1801623] Re: Bluetooth keeps starting by default on boot, prefer it's off by default
*** This bug is a duplicate of bug 1635831 *** https://bugs.launchpad.net/bugs/1635831 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1635831, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** Package changed: bluez (Ubuntu) => unity-control-center (Ubuntu) ** This bug has been marked a duplicate of bug 1635831 Bluetooth does not stay turned off after reboot -- 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/1801623 Title: Bluetooth keeps starting by default on boot, prefer it's off by default Status in unity-control-center package in Ubuntu: New Bug description: Bluetooth keeps starting by default on boot, I turn it off, and it's not set to start in startup applications. Need a way for it to be always off by default, but still be able to turn it on when I need it. I've been seeing this for many major Ubuntu versions for years. Finally submitting this. Ubuntu 18.04 currently. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3.1 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 CurrentDesktop: Unity:Unity7:ubuntu Date: Sun Nov 4 16:03:12 2018 InstallationDate: Installed on 2017-02-18 (624 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 239242U ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic root=UUID=aacb9562-db8b-4a32-8e9b-47530c8c0331 ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: Upgraded to bionic on 2018-04-28 (189 days ago) dmi.bios.date: 05/29/2012 dmi.bios.vendor: LENOVO dmi.bios.version: G4ET37WW (1.12 ) dmi.board.asset.tag: Not Available dmi.board.name: 239242U dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG4ET37WW(1.12):bd05/29/2012:svnLENOVO:pn239242U:pvrThinkPadT530:rvnLENOVO:rn239242U:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T530 dmi.product.name: 239242U dmi.product.version: ThinkPad T530 dmi.sys.vendor: LENOVO hciconfig: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1801623/+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 1801564] Re: Can't connect second monitor on NVidia over adapter DVI->VGA
> Can't connect second monitor Can you please explain in more detail what problem you experience? What are you doing? What do you expect to happen? What do you see? ** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers-390 (Ubuntu) ** Also affects: xorg-server (Ubuntu) Importance: Undecided Status: New ** Tags added: nvidia ** Changed in: nvidia-graphics-drivers-390 (Ubuntu) Status: New => Incomplete ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1801564 Title: Can't connect second monitor on NVidia over adapter DVI->VGA Status in nvidia-graphics-drivers-390 package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: NVidia GF108 (10de:0df8) Quadro 600 xserver-xorg-video-nouveau,nvidia-graphics-drivers : DisplayPort=Samsung 27" DVI->VGA=Acer V193HQ INTEL : DVI=BenQ FP93G X ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Это каталог: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.77 Tue Jul 10 18:28:52 PDT 2018 GCC version: gcc version 7.3.0 (Ubuntu 7.3.0-27ubuntu1~18.04) .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CompositorRunning: None Date: Sun Nov 4 07:43:17 2018 DistUpgraded: 2018-10-29 18:00:47,682 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 390.77, 4.15.0-38-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Subsystem: ASUSTeK Computer Inc. HD Graphics 630 [1043:8694] NVIDIA Corporation GF108GL [Quadro 600] [10de:0df8] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation GF108GL [Quadro 600] [10de:0835] MachineType: System manufacturer System Product Name ProcEnviron: PATH=(custom, no user) LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-38-generic root=UUID=bc343c51-118f-49ba-a3a5-283e6bbd0290 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-10-29 (5 days ago) dmi.bios.date: 09/08/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0810 dmi.board.asset.tag: Default string dmi.board.name: STRIX B250F GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0810:bd09/08/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnSTRIXB250FGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: 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 version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Sun Nov 4 07:41:21 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1801564/+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 1801540] Re: Microphone distorted sound on ALC892
** Tags added: cosmic ** Package changed: alsa-driver (Ubuntu) => pulseaudio (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1801540 Title: Microphone distorted sound on ALC892 Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: New Bug description: Not sure if I'll report this upstream but there is definitely an issue with microphone recording on my desktop, this is not happening on my laptop which has a different codec. Already tried all workarounds possible, no luck. Only with my desktop with this particular motherboard. No issues in Windows, the sound recorded in there is distorted and has some static and robotic tone on high-pitch. alsa-info on the attachments To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801540/+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 1800413] Re: It can not use nvidia-settings to switch from the power saving mode to the performance mode
set to high as the bug only happen to package in ppa (not in update channel). ** Changed in: oem-priority Importance: Undecided => High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1800413 Title: It can not use nvidia-settings to switch from the power saving mode to the performance mode Status in NVIDIA Drivers Ubuntu: Confirmed Status in OEM Priority Project: Confirmed Status in nvidia-settings package in Ubuntu: Confirmed Bug description: I try to use nvidia-settings 410.73-0ubuntu0~gpu18.04.1 in ppa:graphics-drivers/ppa to switch from the power saving mode to the performance mode on Ubuntu 18.04. But it failed. $ nvidia-settings ERROR: NVIDIA driver is not loaded ERROR: Unable to load info from any available system However `prime-select nvidia` still works fine and there is no such issue by nvidia-settings 390.77-0ubuntu0.18.04.1 in bionic-updates. Private Bug: https://bugs.launchpad.net/bugs/1800081 To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1800413/+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 1801564] [NEW] Can't connect second monitor on NVidia over adapter DVI->VGA
You have been subscribed to a public bug: NVidia GF108 (10de:0df8) Quadro 600 xserver-xorg-video-nouveau,nvidia-graphics-drivers : DisplayPort=Samsung 27" DVI->VGA=Acer V193HQ INTEL : DVI=BenQ FP93G X ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Это каталог: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.77 Tue Jul 10 18:28:52 PDT 2018 GCC version: gcc version 7.3.0 (Ubuntu 7.3.0-27ubuntu1~18.04) .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CompositorRunning: None Date: Sun Nov 4 07:43:17 2018 DistUpgraded: 2018-10-29 18:00:47,682 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 390.77, 4.15.0-38-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Subsystem: ASUSTeK Computer Inc. HD Graphics 630 [1043:8694] NVIDIA Corporation GF108GL [Quadro 600] [10de:0df8] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation GF108GL [Quadro 600] [10de:0835] MachineType: System manufacturer System Product Name ProcEnviron: PATH=(custom, no user) LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-38-generic root=UUID=bc343c51-118f-49ba-a3a5-283e6bbd0290 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-10-29 (5 days ago) dmi.bios.date: 09/08/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0810 dmi.board.asset.tag: Default string dmi.board.name: STRIX B250F GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0810:bd09/08/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnSTRIXB250FGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: 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 version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Sun Nov 4 07:41:21 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4.2 ** Affects: nvidia-graphics-drivers-390 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic possible-manual-nvidia-install ubuntu -- Can't connect second monitor on NVidia over adapter DVI->VGA https://bugs.launchpad.net/bugs/1801564 You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1801540] Re: Microphone distorted sound on ALC892
Does this issue happen on Front Mic, Rear Mic or LineIn? set the input volume lower, is the recorded sound better? -- 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/1801540 Title: Microphone distorted sound on ALC892 Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: Not sure if I'll report this upstream but there is definitely an issue with microphone recording on my desktop, this is not happening on my laptop which has a different codec. Already tried all workarounds possible, no luck. Only with my desktop with this particular motherboard. No issues in Windows, the sound recorded in there is distorted and has some static and robotic tone on high-pitch. alsa-info on the attachments To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1801540/+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 1717796] Re: Bluetoothd fills 100% CPU when bluetooth keyboard goes in idle
** Also affects: ubuntu-power-consumption Importance: Undecided Status: New ** Changed in: ubuntu-power-consumption Importance: Undecided => Medium ** Changed in: bluez (Ubuntu) Importance: Undecided => Medium ** Changed in: ubuntu-power-consumption Status: New => Confirmed -- 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/1717796 Title: Bluetoothd fills 100% CPU when bluetooth keyboard goes in idle Status in The Ubuntu Power Consumption Project: Confirmed Status in bluez package in Ubuntu: Confirmed Bug description: When bluetooth keyboard goes in idle bluetoothd fills 100% CPU. At this point you have to press any key to reconnect the device and let bluetoothd to return to work normally. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: bluez 5.37-0ubuntu5.1 ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79 Uname: Linux 4.4.0-93-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 Date: Sun Sep 17 19:02:40 2017 ExecutablePath: /usr/lib/bluetooth/bluetoothd InstallationDate: Installed on 2016-08-06 (406 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: GIGABYTE GB-BXBT-2807 ProcEnviron: LANG=it_IT.UTF-8 PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-93-generic.efi.signed root=UUID=8931ead4-8d43-4aef-8946-c7845c63c7d3 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/22/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F8 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MZBAYAP-00 dmi.board.vendor: GIGABYTE dmi.board.version: 1.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF8:bd10/22/2015:svnGIGABYTE:pnGB-BXBT-2807:pvr1.x:rvnGIGABYTE:rnMZBAYAP-00:rvr1.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: GB-BXBT-2807 dmi.product.version: 1.x dmi.sys.vendor: GIGABYTE hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: DC:85:DE:FD:2F:BC ACL MTU: 820:8 SCO MTU: 255:16 UP RUNNING PSCAN ISCAN RX bytes:528225 acl:32183 sco:0 events:1134 errors:0 TX bytes:33849 acl:338 sco:0 commands:388 errors:1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-consumption/+bug/1717796/+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 1745032] Re: AC adapter status not detected on Asus ZenBook UX410UAK
The issue persist on 18.10 (4.18.0-10-generic). ** Changed in: linux (Ubuntu) Status: Fix Released => In Progress -- 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/1745032 Title: AC adapter status not detected on Asus ZenBook UX410UAK Status in linux package in Ubuntu: In Progress Status in linux source package in Artful: In Progress Bug description: === SRU Justification === [Impact] Some Asus laptops report "discharging" when the battery is full and AC is plugged [Test] Charge battery to full, the issue appears. Users report with the patch the behaviour is correct. [Fix] The discharge rate is 0 on those machines. Use that to detect the wrong status report. [Regression Potential] Low. The quirk uses strict DMI to match affected systems. === Original Bug Report === The AC adapter status is incorrectly reported when the battery is fully charged. It always shows as if the adapter is not plugged in. If the battery is drained for a while, the adapter status is shown correctly (both connects and disconnects are shown). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-31-generic 4.13.0-31.34 ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13 Uname: Linux 4.13.0-31-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: abarto 1388 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Jan 23 18:26:18 2018 InstallationDate: Installed on 2018-01-23 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 04f2:b57a Chicony Electronics Co., Ltd Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX410UAK ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed root=UUID=58ea0561-3f74-4566-9332-5e7021275160 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-31-generic N/A linux-backports-modules-4.13.0-31-generic N/A linux-firmware 1.169.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX410UAK.306 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX410UAK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX410UAK.306:bd08/08/2017:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX410UAK 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/1745032/+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 1745032] Re: AC adapter status not detected on Asus ZenBook UX410UAK
The issue persist on 18.10 (4.18.0-10-generic). ** Changed in: linux (Ubuntu Artful) Status: Fix Released => In Progress -- 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/1745032 Title: AC adapter status not detected on Asus ZenBook UX410UAK Status in linux package in Ubuntu: In Progress Status in linux source package in Artful: In Progress Bug description: === SRU Justification === [Impact] Some Asus laptops report "discharging" when the battery is full and AC is plugged [Test] Charge battery to full, the issue appears. Users report with the patch the behaviour is correct. [Fix] The discharge rate is 0 on those machines. Use that to detect the wrong status report. [Regression Potential] Low. The quirk uses strict DMI to match affected systems. === Original Bug Report === The AC adapter status is incorrectly reported when the battery is fully charged. It always shows as if the adapter is not plugged in. If the battery is drained for a while, the adapter status is shown correctly (both connects and disconnects are shown). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-31-generic 4.13.0-31.34 ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13 Uname: Linux 4.13.0-31-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: abarto 1388 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Jan 23 18:26:18 2018 InstallationDate: Installed on 2018-01-23 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 04f2:b57a Chicony Electronics Co., Ltd Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX410UAK ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed root=UUID=58ea0561-3f74-4566-9332-5e7021275160 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-31-generic N/A linux-backports-modules-4.13.0-31-generic N/A linux-firmware 1.169.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX410UAK.306 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX410UAK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX410UAK.306:bd08/08/2017:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX410UAK 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/1745032/+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 1499858] Re: bluetoothd[650]: Failed to obtain handles for "Service Changed" characteristic
Hello, Just to chime in here. I compiled bluez-5.43 and installed it on ubuntu 16.04 and it got rid of all the "Not enough free handles to register service" errors except this one "Failed to obtain handles for "Service Changed" characteristic. Before doing this there were many "Not enough free handles to register service". Any ideas on this last error "Failed to obtain handles for "Service Changed"?? Singtoh -- 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/1499858 Title: bluetoothd[650]: Failed to obtain handles for "Service Changed" characteristic Status in bluez package in Ubuntu: Confirmed Bug description: sep 25 11:03:01 username-530U3C-530U4C bluetoothd[650]: Failed to obtain handles for "Service Changed" characteristic sep 25 11:03:01 username-530U3C-530U4C bluetoothd[650]: Not enough free handles to register service sep 25 11:03:01 username-530U3C-530U4C bluetoothd[650]: Error adding Link Loss service sep 25 11:03:01 username-530U3C-530U4C bluetoothd[650]: Not enough free handles to register service sep 25 11:03:01 username-530U3C-530U4C bluetoothd[650]: Not enough free handles to register service sep 25 11:03:01 username-530U3C-530U4C bluetoothd[650]: Not enough free handles to register service sep 25 11:03:01 username-530U3C-530U4C bluetoothd[650]: Current Time Service could not be registered sep 25 11:03:01 username-530U3C-530U4C bluetoothd[650]: gatt-time-server: Input/output error (5) sep 25 11:03:01 username-530U3C-530U4C bluetoothd[650]: Not enough free handles to register service sep 25 11:03:01 username-530U3C-530U4C bluetoothd[650]: Not enough free handles to register service sep 25 11:03:01 username-530U3C-530U4C bluetoothd[650]: Sap driver initialization failed. sep 25 11:03:01 username-530U3C-530U4C bluetoothd[650]: sap-server: Operation not permitted (1) ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: bluez 5.34-0ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-11.13-generic 4.2.1 Uname: Linux 4.2.0-11-generic x86_64 ApportVersion: 2.19-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Sep 25 16:37:42 2015 InstallationDate: Installed on 2015-07-26 (61 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150723) InterestingModules: rfcomm bnep btusb bluetooth MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-11-generic root=UUID=4f4435ca-b877-47a5-9065-3dd624c0514e ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: bluez UdevLog: Error: [Errno 2] No existe el archivo o el directorio: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P14AAJ dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: SAMSUNG_NP1234567890 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.name: 530U3C/530U4C dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: C4:85:08:6C:01:0A ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN RX bytes:12620731 acl:54193 sco:0 events:799035 errors:0 TX bytes:447934374 acl:1637190 sco:0 commands:1459 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1499858/+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 1801623] [NEW] Bluetooth keeps starting by default on boot, prefer it's off by default
Public bug reported: Bluetooth keeps starting by default on boot, I turn it off, and it's not set to start in startup applications. Need a way for it to be always off by default, but still be able to turn it on when I need it. I've been seeing this for many major Ubuntu versions for years. Finally submitting this. Ubuntu 18.04 currently. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3.1 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 CurrentDesktop: Unity:Unity7:ubuntu Date: Sun Nov 4 16:03:12 2018 InstallationDate: Installed on 2017-02-18 (624 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 239242U ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic root=UUID=aacb9562-db8b-4a32-8e9b-47530c8c0331 ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: Upgraded to bionic on 2018-04-28 (189 days ago) dmi.bios.date: 05/29/2012 dmi.bios.vendor: LENOVO dmi.bios.version: G4ET37WW (1.12 ) dmi.board.asset.tag: Not Available dmi.board.name: 239242U dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG4ET37WW(1.12):bd05/29/2012:svnLENOVO:pn239242U:pvrThinkPadT530:rvnLENOVO:rn239242U:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T530 dmi.product.name: 239242U dmi.product.version: ThinkPad T530 dmi.sys.vendor: LENOVO hciconfig: ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1801623 Title: Bluetooth keeps starting by default on boot, prefer it's off by default Status in bluez package in Ubuntu: New Bug description: Bluetooth keeps starting by default on boot, I turn it off, and it's not set to start in startup applications. Need a way for it to be always off by default, but still be able to turn it on when I need it. I've been seeing this for many major Ubuntu versions for years. Finally submitting this. Ubuntu 18.04 currently. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3.1 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 CurrentDesktop: Unity:Unity7:ubuntu Date: Sun Nov 4 16:03:12 2018 InstallationDate: Installed on 2017-02-18 (624 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 239242U ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic root=UUID=aacb9562-db8b-4a32-8e9b-47530c8c0331 ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: Upgraded to bionic on 2018-04-28 (189 days ago) dmi.bios.date: 05/29/2012 dmi.bios.vendor: LENOVO dmi.bios.version: G4ET37WW (1.12 ) dmi.board.asset.tag: Not Available dmi.board.name: 239242U dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG4ET37WW(1.12):bd05/29/2012:svnLENOVO:pn239242U:pvrThinkPadT530:rvnLENOVO:rn239242U:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T530 dmi.product.name: 239242U dmi.product.version: ThinkPad T530 dmi.sys.vendor: LENOVO hciconfig: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1801623/+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 1734147] Re: corrupted BIOS due to Intel SPI bug in kernel
1) You must give UUID stored in broken BIOS - via USB boot if you can boot Linux and use in terminal "efibootmgr -v" - in Windows can be some software for check efibootmg from BIOS - if is not chance to boot (HDD formated etc.) try to find via Hxx Freeware hex editor and disk editor (i used it from formated HDD find worked UUID) 2) Install ubuntu on another PC 3) Backup partition "sfdisk -d /dev/sda > x.txt" 4) Replace UUID for EFI System Partition with same UUID stored in BIOS in file x.txt 5) Replace Partition with new UUID "sfdisk -f /dev/sda < x.txt" 6) now you have installed Ubuntu and can use Fix from first post -- 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/1734147 Title: corrupted BIOS due to Intel SPI bug in kernel Status in Linux: Unknown Status in linux package in Ubuntu: Fix Released Status in linux-hwe-edge source package in Xenial: Fix Released Status in linux-oem source package in Xenial: Fix Released Status in linux source package in Artful: Fix Released Bug description: An update to linux kernel on Ubuntu 17.10 that enabled the Intel SPI drivers results in a serial flash that is read only in Intel Broadwell and Haswell machines with serial flashes with SPI_NOR_HAS_LOCK set. Symptoms: * BIOS settings cannot be saved * USB Boot impossible * EFI entries read-only. --- Fix: The issue was fixed in kernel version 4.13.0-21 by configuring the kernel so it is not compiled with Intel SPI support. But previous affected machines still suffered from a broken BIOS. Repair: If you still can boot into Ubuntu, you can recover your BIOS with the following steps: 1. Boot into Ubuntu 2. Download http://people.canonical.com/~ypwong/lp1734147/linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+20170103+1_amd64.deb 3. Install the downloaded package: $ sudo dpkg -i linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+20170103+1_amd64.deb 4. Make sure the kernel is installed without any error. Once installed, reboot. 5. At grub, choose the newly installed kernel. You can choose the "recovery" mode. 6. Reboot and go to BIOS settings to confirm your BIOS has been recovered. 7. In case your BIOS is not recovered, reboot to the new kernel, then reboot *once again* to the new kernel, do not enter BIOS settings before the reboot. After the second reboot, check BIOS. 8. If your BIOS issue remains, download another kernel from http://people.canonical.com/~ypwong/lp1734147/linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+clear+debug_amd64.deb, and use dpkg to install it, then repeat steps 4 to 6. After your BIOS is fixed, the kernel packages you just installed are no longer needed, you can remove it by running 'sudo dpkg -r linux- image-4.15.0-041500rc6-generic'. The patch used to build the linux v4.15 kernel in step 8 can be found at https://goo.gl/xUKJFR. --- Test Case: Fix has been verified by our HWE team on affected hardware. Regression Potential: Minimal, it's unlikely anyone is actually doing anything which requires this driver. --- Affected Machines: Lenovo B40-70 Lenovo B50-70 Lenovo B50-80 Lenovo Flex-3 Lenovo Flex-10 Lenovo G40-30 Lenovo G50-30 Lenovo G50-70 Lenovo G50-80 Lenovo S20-30 Lenovo U31-70 Lenovo Y50-70 Lenovo Y70-70 Lenovo Yoga Thinkpad (20C0) Lenovo Yoga 2 11" - 20332 Lenovo Yoga 3 11" Lenovo Z50-70 Lenovo Z51-70 Lenovo ideapad 100-15IBY Acer Aspire E5-771G Acer Aspire ES1-111M-C1LE (fixed following your new instruction (thank you)) Acer TravelMate B113 Acer Swift SF314-52 (Fixed by 4.14.9) Toshiba Satellite S55T-B5233 Toshiba Satellite L50-B-1R7 Toshiba Satellite S50-B-13G Toshiba Satellite L70-A-13M Dell Inspiron 15-3531 Mediacom Smartbook 14 Ultra M-SB14UC (fixed with official fix) Acer Aspire E3-111-C0UM HP 14-r012la --- Affected serial flash devices by manufacturer part number, JEDEC ID (SPI_NOR_HAS_LOCK set in drivers/mtd/spi-nor/spi-nor.c) /* ESMT */ f25l32pa, 0x8c2016 f25l32qa, 0x8c4116 f25l64qa, 0x8c4117 /* GigaDevice */ gd25q16, 0xc84015 gd25q32, 0xc84016 gd25lq32, 0xc86016 gd25q64, 0xc84017 gd25lq64c, 0xc86017 gd25q128, 0xc84018 gd25q256, 0xc84019 /* Winbond */ w25q16dw, 0xef6015 w25q32dw, 0xef6016 w25q64dw, 0xef6017 w25q128fw, 0xef6018 --- Original Description: Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users reported a corrupted BIOS. It's not possible to save new settings in BIOS anymore and after rebooting, the system starts with the old settings. Moreover (and most important) USB booting is not possible anymore since USB is not recognized. It's very serious, since our machines do not ha
[Kernel-packages] [Bug 1798921] Re: sky2 ethernet card don't work after returning from suspension
uname -a Linux kris-R780 4.15.0-39-generic #42~lp1798921 SMP Wed Oct 24 05:59:26 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux after waking up with the option suspend helps only: rmmod sky2 modprobe sky2 :-) -- 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/1798921 Title: sky2 ethernet card don't work after returning from suspension Status in linux package in Ubuntu: Incomplete Bug description: Bug very similar to #1752772 (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752772) but affecting the sky2 driver instead of r8169. After system suspend the ethernet connection stops working. The card is still up and the modem can see it is connected, but the card doesn't get an ip address. Ifconfig down/up and restarting network- manager does not solve the issue. Similarly to the other bug, "sudo modprobe sky2 -r" an then "sudo modprobe sky2" solves the issue. Relevant: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752772/comments/107 Linux 4.15.0-36-generic #39-Ubuntu SMP Mon Sep 24 16:19:09 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux *-network description: Ethernet interface product: 88E8040 PCI-E Fast Ethernet Controller vendor: Marvell Technology Group Ltd. physical id: 0 bus info: pci@:09:00.0 logical name: enp9s0 version: 13 serial: 00:23:ae:ea:23:3e size: 100Mbit/s capacity: 100Mbit/s width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=sky2 driverversion=1.30 duplex=full latency=0 link=yes multicast=yes port=twisted pair speed=100Mbit/s resources: irq:24 memory:f68fc000-f68f ioport:de00(size=256) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798921/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1798921] Re: sky2 ethernet card don't work after returning from suspension
I just installed it it does not work there is still an error: "sky2 ethernet card do not work after returning from suspension" regards -- 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/1798921 Title: sky2 ethernet card don't work after returning from suspension Status in linux package in Ubuntu: Incomplete Bug description: Bug very similar to #1752772 (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752772) but affecting the sky2 driver instead of r8169. After system suspend the ethernet connection stops working. The card is still up and the modem can see it is connected, but the card doesn't get an ip address. Ifconfig down/up and restarting network- manager does not solve the issue. Similarly to the other bug, "sudo modprobe sky2 -r" an then "sudo modprobe sky2" solves the issue. Relevant: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752772/comments/107 Linux 4.15.0-36-generic #39-Ubuntu SMP Mon Sep 24 16:19:09 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux *-network description: Ethernet interface product: 88E8040 PCI-E Fast Ethernet Controller vendor: Marvell Technology Group Ltd. physical id: 0 bus info: pci@:09:00.0 logical name: enp9s0 version: 13 serial: 00:23:ae:ea:23:3e size: 100Mbit/s capacity: 100Mbit/s width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=sky2 driverversion=1.30 duplex=full latency=0 link=yes multicast=yes port=twisted pair speed=100Mbit/s resources: irq:24 memory:f68fc000-f68f ioport:de00(size=256) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798921/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1798921] Re: sky2 ethernet card don't work after returning from suspension
kris, Please try the kernel in https://people.canonical.com/~khfeng/lp1798921/ Best regards, -- Cristian Aravena Romero (caravena) -- 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/1798921 Title: sky2 ethernet card don't work after returning from suspension Status in linux package in Ubuntu: Incomplete Bug description: Bug very similar to #1752772 (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752772) but affecting the sky2 driver instead of r8169. After system suspend the ethernet connection stops working. The card is still up and the modem can see it is connected, but the card doesn't get an ip address. Ifconfig down/up and restarting network- manager does not solve the issue. Similarly to the other bug, "sudo modprobe sky2 -r" an then "sudo modprobe sky2" solves the issue. Relevant: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752772/comments/107 Linux 4.15.0-36-generic #39-Ubuntu SMP Mon Sep 24 16:19:09 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux *-network description: Ethernet interface product: 88E8040 PCI-E Fast Ethernet Controller vendor: Marvell Technology Group Ltd. physical id: 0 bus info: pci@:09:00.0 logical name: enp9s0 version: 13 serial: 00:23:ae:ea:23:3e size: 100Mbit/s capacity: 100Mbit/s width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=sky2 driverversion=1.30 duplex=full latency=0 link=yes multicast=yes port=twisted pair speed=100Mbit/s resources: irq:24 memory:f68fc000-f68f ioport:de00(size=256) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798921/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1798921] Re: sky2 ethernet card don't work after returning from suspension
4.19.0-041900-generic kernel-bug-exists-upstream :-( -- 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/1798921 Title: sky2 ethernet card don't work after returning from suspension Status in linux package in Ubuntu: Incomplete Bug description: Bug very similar to #1752772 (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752772) but affecting the sky2 driver instead of r8169. After system suspend the ethernet connection stops working. The card is still up and the modem can see it is connected, but the card doesn't get an ip address. Ifconfig down/up and restarting network- manager does not solve the issue. Similarly to the other bug, "sudo modprobe sky2 -r" an then "sudo modprobe sky2" solves the issue. Relevant: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752772/comments/107 Linux 4.15.0-36-generic #39-Ubuntu SMP Mon Sep 24 16:19:09 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux *-network description: Ethernet interface product: 88E8040 PCI-E Fast Ethernet Controller vendor: Marvell Technology Group Ltd. physical id: 0 bus info: pci@:09:00.0 logical name: enp9s0 version: 13 serial: 00:23:ae:ea:23:3e size: 100Mbit/s capacity: 100Mbit/s width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=sky2 driverversion=1.30 duplex=full latency=0 link=yes multicast=yes port=twisted pair speed=100Mbit/s resources: irq:24 memory:f68fc000-f68f ioport:de00(size=256) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798921/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1791427] Re: Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1 Carbon 6th
@rriemann As I said, I've no experience of filing kernel bugs. I have no filed one about this. -- 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/1791427 Title: Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1 Carbon 6th Status in linux package in Ubuntu: Triaged Bug description: Ubuntu 18.04.1 Terminology in case we use different terms: touchpad - just the rectangular touch-sensitive surface below the keyboard (xinput lists it as Synaptics TM3288-011) trackpoint - the red thingy built into the keyboard + 3 physical buttons below the keyboard (trackpoint and buttons are integrated together; listed in xinput as TPPS/2 Elan TrackPoint) On September 7th, 2018, Lenovo has issued a BIOS update (v1.30), which enables proper S3 deep sleep state - users no longer have to patch DSDT tables to get it. It can be enabled in the BIOS settings. In X1 carbon 6th generation models that have NFC, when laptop wakes from suspend by opening the lid, in most cases both touchpad and trackpoint stop working completely. They are also no longer listed when running xinput command. Sometimes just one of them stops working, usually the trackpoint. In some rare cases it is possible to bring them back by using these commands: echo -n none > /sys/devices/platform/i8042/serio1/drvctl echo -n reconnect > /sys/devices/platform/i8042/serio1/drvctl rmmod psmouse modprobe psmouse These worked properly when waking up from S2Idle sleep state (had these in a script that runs after waking the machine from suspend), but with S3 deep sleep these rarely work and the only way to bring back touchpad and/or trackpoint is turning off the machine and turning it on (restart does not help). I could not find any pattern that would show when the input devices stop working or start working again using the commands mentioned above. It's completely random from my perspective. This is happening on the standard issue 4.15.0-33-generic kernel that shipped with my Ubuntu 18.04 (with updates), as well as with newer mainline kernels, such as the newest point versions of 4.17, 4.18 and 4.19 RC2. This happens regardless of whether "blacklist i2c_i801" is commented out in /etc/modprobe.d/blacklist.conf or not. It happens regardless of whether "psmouse.synaptics_intertouch=1" is passed as grub parameter. Presence of TLP does not make it better, nor worse. It appears that non-NFC models are not affected. I know at least one Arch Linux user who has the exact same model, but without this issue. I'm using synaptics driver (no libinput installed), he uses libinput and doesn't have synaptics, if that information is of any use. Libinput does not seem to help. This forum thread also has more details from users who updated their BIOS to get S3 suspend: https://forums.lenovo.com/t5/Linux- Discussion/X1-Carbon-Gen-6-cannot-enter-deep-sleep-S3-state-aka- Suspend-to/td-p/3998182/page/27 Another related thread: https://bbs.archlinux.org/viewtopic.php?id=236367 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-33-generic 4.15.0-33.36 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: maciej 2651 F...m pulseaudio /dev/snd/controlC0: maciej 2651 F pulseaudio CurrentDesktop: i3 Date: Sat Sep 8 13:45:43 2018 HibernationDevice: RESUME=UUID=3116dcb0-d91e-4b2a-8166-43b7a9a9d36e InstallationDate: Installed on 2018-07-21 (49 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 13d3:56b2 IMC Networks Bus 001 Device 002: ID 04b4:0060 Cypress Semiconductor Corp. Wireless optical mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20KH006KPB ProcFB: 0 EFI VGA 1 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-33-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash psmouse.synaptics_intertouch=1 vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-33-generic N/A linux-backports-modules-4.15.0-33-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/31/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET55W (1.30 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KH006KPB dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Non
[Kernel-packages] [Bug 1800901] Re: Updating breaks wifi on Intel Compute Stick
After the bios update the issues that occurred after the apt-get upgrade have disappeared. Let's mark this as closed. -- 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/1800901 Title: Updating breaks wifi on Intel Compute Stick Status in linux package in Ubuntu: Incomplete Bug description: On an Intel Compute Stick model STCK1A8LFC the stock install works fine. The default kernel: uname -a Linux joe-STCK1A8LFC 3.16.0-34-generic #47~14.04.1-Ubuntu SMP Fri Apr 10 17:49:16 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux When an apt-get update/upgrade is run all network connectivity is lost. Run wpa_cli scan shows no networks at all. A return to the factory default returns connectivity. Any help would be greatly appreciated. Cheers,-Joe To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1800901/+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 1717796] Re: Bluetoothd fills 100% CPU when bluetooth keyboard goes in idle
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: bluez (Ubuntu) Status: New => Confirmed -- 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/1717796 Title: Bluetoothd fills 100% CPU when bluetooth keyboard goes in idle Status in bluez package in Ubuntu: Confirmed Bug description: When bluetooth keyboard goes in idle bluetoothd fills 100% CPU. At this point you have to press any key to reconnect the device and let bluetoothd to return to work normally. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: bluez 5.37-0ubuntu5.1 ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79 Uname: Linux 4.4.0-93-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 Date: Sun Sep 17 19:02:40 2017 ExecutablePath: /usr/lib/bluetooth/bluetoothd InstallationDate: Installed on 2016-08-06 (406 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: GIGABYTE GB-BXBT-2807 ProcEnviron: LANG=it_IT.UTF-8 PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-93-generic.efi.signed root=UUID=8931ead4-8d43-4aef-8946-c7845c63c7d3 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/22/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F8 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MZBAYAP-00 dmi.board.vendor: GIGABYTE dmi.board.version: 1.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF8:bd10/22/2015:svnGIGABYTE:pnGB-BXBT-2807:pvr1.x:rvnGIGABYTE:rnMZBAYAP-00:rvr1.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: GB-BXBT-2807 dmi.product.version: 1.x dmi.sys.vendor: GIGABYTE hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: DC:85:DE:FD:2F:BC ACL MTU: 820:8 SCO MTU: 255:16 UP RUNNING PSCAN ISCAN RX bytes:528225 acl:32183 sco:0 events:1134 errors:0 TX bytes:33849 acl:338 sco:0 commands:388 errors:1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1717796/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1774950] Re: Suspend fails in Ubuntu and Kubuntu 18.04 but works fine in Ubuntu and Kubuntu 17.10 (and on Kubuntu 18.04 using kernel 4.14.47)
Please file 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/1774950 Title: Suspend fails in Ubuntu and Kubuntu 18.04 but works fine in Ubuntu and Kubuntu 17.10 (and on Kubuntu 18.04 using kernel 4.14.47) Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Bug description: ===SRU Justification=== [Impact] Systems with acpi-lpss can't do S3/S4 on Bionic. [Test] Users confirmed these patches work for them. [Fix] Commit a192aa923b66a (ACPI / LPSS: Consolidate runtime PM and system sleep handling) applies quirks for both runtime and system suspend. This causes problems for some systems, so avoid using quirks on S3 and S4. [Regression Potential] Low. These patches are in upstream stable, and it brings back driver's old behavior. ===Original Bug Report=== I have installed Kubuntu 18.04 on 3 different machines (my friend's and my own) with no suspend problems but my HP Pavilion 11 x360 does not suspend. It suspends fine with Ubuntu 17.10, Kubuntu 17.10, Devuan Jesse, Devuan ASCII and Windows 10 but fails with Ubuntu 18.04 and Kubuntu 18.04. I have also tried suspend using a live USB of 18.04 on this machine and it fails in the same way, so does not appear to be caused by any additional programs that I had installed. By installing an older kernel (4.14) on Kubuntu 18.04 the suspend function works as expected. Running Kubuntu 18.04 with kernels 4.15, 4.16, 4.17 results in the suspend failure that freezes the machine and requires a hard reset. Correct behaviour is - Screen goes blank, fan goes off, power LED flashes to show machine is in suspend. Pressing power button triggers 'resume' function. What happens - Screen goes blank, fan stays on, power LED stays on. Machine stays in this state and does not respond to any keyboard interaction, mouse movement or power button presses. Ctrl + Alt + f1 (or f2, f3, f4 etc) does not get any response. The only way to use the machine is to shut down by holding down the power button. Checking the logs suggests that the machine believes it is in suspend mode sleep [deep] when it isn't. Having to hard reset to get any response means that the kernel logs say no more than sleep [deep] pm-suspend also results in the same problems with kernels 4.15 and 4.16, but works fine with 4.14. It is curious that a machine that suspends fine on an earlier 4.14 kernel no longer works with 4.15 and above, whilst 3 other machines (including one with pretty similar hardware) do not exhibit this problem. There are only a handful of questions about it on the forums but at least 3 other people have the same problem: https://askubuntu.com/questions/1029405/ubuntu-18-04-crashes-on- resuming-from-suspend https://askubuntu.com/questions/1041369/after-upgrading- from-17-10-ubuntu-18-04-wont-sleep-suspend I am attempting to round up anyone else with the same issue and point them to this bug report. My laptop is HP Pavilion x360 11-n013na Matalaks is Acer Aspire ES1-511 collisionTwo has XPS 9560 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774950/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799718] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1799718/+attachment/5209033/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1799718 Title: Ubuntu 18.10 fr FAN always ON 5 400 rpm Status in linux package in Ubuntu: Incomplete Bug description: On Ubuntu 18.10 fr since 20181022. By update from 18.04 My PC ASUS ROG GL 753V Notebook PC Fan always on At 5 400 rpm. Air cold ! GPU temp 31 °C PC 33 °C Ubuntu version : 4.18.0.11-generic On startup, says "Failed start load kernel Modules" On picture on attachment : Value of fan is incorrect I don't know where is fan sensor to put on my conky --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rg 4260 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 HibernationDevice: RESUME=UUID=a4c1f9fd-8ee7-4a18-8aa4-8eb2ecead862 InstallationDate: Installed on 2018-10-31 (3 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 0b05:1854 ASUSTek Computer, Inc. Bus 001 Device 004: ID 13d3:5666 IMC Networks Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. GL753VD NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic root=UUID=2172f67c-0362-49ad-9639-8077f44d34f8 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 RelatedPackageVersions: linux-restricted-modules-4.18.0-11-generic N/A linux-backports-modules-4.18.0-11-generic N/A linux-firmware 1.175 Tags: cosmic Uname: Linux 4.18.0-11-generic x86_64 UpgradeStatus: Upgraded to cosmic on 2018-11-03 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/16/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GL753VD.307 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GL753VD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGL753VD.307:bd04/16/2018:svnASUSTeKCOMPUTERINC.:pnGL753VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL753VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ROG dmi.product.name: GL753VD 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/1799718/+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 1799718] Re: Ubuntu 18.10 fr FAN always ON 5 400 rpm
Seems to be crashed ! Something blocks apport information -- 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/1799718 Title: Ubuntu 18.10 fr FAN always ON 5 400 rpm Status in linux package in Ubuntu: Incomplete Bug description: On Ubuntu 18.10 fr since 20181022. By update from 18.04 My PC ASUS ROG GL 753V Notebook PC Fan always on At 5 400 rpm. Air cold ! GPU temp 31 °C PC 33 °C Ubuntu version : 4.18.0.11-generic On startup, says "Failed start load kernel Modules" On picture on attachment : Value of fan is incorrect I don't know where is fan sensor to put on my conky --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rg 4260 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 HibernationDevice: RESUME=UUID=a4c1f9fd-8ee7-4a18-8aa4-8eb2ecead862 InstallationDate: Installed on 2018-10-31 (3 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 0b05:1854 ASUSTek Computer, Inc. Bus 001 Device 004: ID 13d3:5666 IMC Networks Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. GL753VD NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic root=UUID=2172f67c-0362-49ad-9639-8077f44d34f8 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 RelatedPackageVersions: linux-restricted-modules-4.18.0-11-generic N/A linux-backports-modules-4.18.0-11-generic N/A linux-firmware 1.175 Tags: cosmic Uname: Linux 4.18.0-11-generic x86_64 UpgradeStatus: Upgraded to cosmic on 2018-11-03 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/16/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GL753VD.307 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GL753VD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGL753VD.307:bd04/16/2018:svnASUSTeKCOMPUTERINC.:pnGL753VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL753VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ROG dmi.product.name: GL753VD 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/1799718/+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 1799718] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1799718/+attachment/5209027/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1799718 Title: Ubuntu 18.10 fr FAN always ON 5 400 rpm Status in linux package in Ubuntu: Incomplete Bug description: On Ubuntu 18.10 fr since 20181022. By update from 18.04 My PC ASUS ROG GL 753V Notebook PC Fan always on At 5 400 rpm. Air cold ! GPU temp 31 °C PC 33 °C Ubuntu version : 4.18.0.11-generic On startup, says "Failed start load kernel Modules" On picture on attachment : Value of fan is incorrect I don't know where is fan sensor to put on my conky --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rg 4260 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 HibernationDevice: RESUME=UUID=a4c1f9fd-8ee7-4a18-8aa4-8eb2ecead862 InstallationDate: Installed on 2018-10-31 (3 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 0b05:1854 ASUSTek Computer, Inc. Bus 001 Device 004: ID 13d3:5666 IMC Networks Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. GL753VD NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic root=UUID=2172f67c-0362-49ad-9639-8077f44d34f8 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 RelatedPackageVersions: linux-restricted-modules-4.18.0-11-generic N/A linux-backports-modules-4.18.0-11-generic N/A linux-firmware 1.175 Tags: cosmic Uname: Linux 4.18.0-11-generic x86_64 UpgradeStatus: Upgraded to cosmic on 2018-11-03 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/16/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GL753VD.307 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GL753VD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGL753VD.307:bd04/16/2018:svnASUSTeKCOMPUTERINC.:pnGL753VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL753VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ROG dmi.product.name: GL753VD 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/1799718/+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 1799718] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1799718/+attachment/5209031/+files/RfKill.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1799718 Title: Ubuntu 18.10 fr FAN always ON 5 400 rpm Status in linux package in Ubuntu: Incomplete Bug description: On Ubuntu 18.10 fr since 20181022. By update from 18.04 My PC ASUS ROG GL 753V Notebook PC Fan always on At 5 400 rpm. Air cold ! GPU temp 31 °C PC 33 °C Ubuntu version : 4.18.0.11-generic On startup, says "Failed start load kernel Modules" On picture on attachment : Value of fan is incorrect I don't know where is fan sensor to put on my conky --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rg 4260 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 HibernationDevice: RESUME=UUID=a4c1f9fd-8ee7-4a18-8aa4-8eb2ecead862 InstallationDate: Installed on 2018-10-31 (3 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 0b05:1854 ASUSTek Computer, Inc. Bus 001 Device 004: ID 13d3:5666 IMC Networks Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. GL753VD NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic root=UUID=2172f67c-0362-49ad-9639-8077f44d34f8 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 RelatedPackageVersions: linux-restricted-modules-4.18.0-11-generic N/A linux-backports-modules-4.18.0-11-generic N/A linux-firmware 1.175 Tags: cosmic Uname: Linux 4.18.0-11-generic x86_64 UpgradeStatus: Upgraded to cosmic on 2018-11-03 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/16/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GL753VD.307 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GL753VD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGL753VD.307:bd04/16/2018:svnASUSTeKCOMPUTERINC.:pnGL753VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL753VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ROG dmi.product.name: GL753VD 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/1799718/+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 1799718] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1799718/+attachment/5209022/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1799718 Title: Ubuntu 18.10 fr FAN always ON 5 400 rpm Status in linux package in Ubuntu: Incomplete Bug description: On Ubuntu 18.10 fr since 20181022. By update from 18.04 My PC ASUS ROG GL 753V Notebook PC Fan always on At 5 400 rpm. Air cold ! GPU temp 31 °C PC 33 °C Ubuntu version : 4.18.0.11-generic On startup, says "Failed start load kernel Modules" On picture on attachment : Value of fan is incorrect I don't know where is fan sensor to put on my conky --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rg 4260 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 HibernationDevice: RESUME=UUID=a4c1f9fd-8ee7-4a18-8aa4-8eb2ecead862 InstallationDate: Installed on 2018-10-31 (3 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 0b05:1854 ASUSTek Computer, Inc. Bus 001 Device 004: ID 13d3:5666 IMC Networks Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. GL753VD NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic root=UUID=2172f67c-0362-49ad-9639-8077f44d34f8 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 RelatedPackageVersions: linux-restricted-modules-4.18.0-11-generic N/A linux-backports-modules-4.18.0-11-generic N/A linux-firmware 1.175 Tags: cosmic Uname: Linux 4.18.0-11-generic x86_64 UpgradeStatus: Upgraded to cosmic on 2018-11-03 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/16/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GL753VD.307 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GL753VD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGL753VD.307:bd04/16/2018:svnASUSTeKCOMPUTERINC.:pnGL753VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL753VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ROG dmi.product.name: GL753VD 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/1799718/+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 1799718] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1799718/+attachment/5209030/+files/PulseList.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1799718 Title: Ubuntu 18.10 fr FAN always ON 5 400 rpm Status in linux package in Ubuntu: Incomplete Bug description: On Ubuntu 18.10 fr since 20181022. By update from 18.04 My PC ASUS ROG GL 753V Notebook PC Fan always on At 5 400 rpm. Air cold ! GPU temp 31 °C PC 33 °C Ubuntu version : 4.18.0.11-generic On startup, says "Failed start load kernel Modules" On picture on attachment : Value of fan is incorrect I don't know where is fan sensor to put on my conky --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rg 4260 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 HibernationDevice: RESUME=UUID=a4c1f9fd-8ee7-4a18-8aa4-8eb2ecead862 InstallationDate: Installed on 2018-10-31 (3 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 0b05:1854 ASUSTek Computer, Inc. Bus 001 Device 004: ID 13d3:5666 IMC Networks Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. GL753VD NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic root=UUID=2172f67c-0362-49ad-9639-8077f44d34f8 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 RelatedPackageVersions: linux-restricted-modules-4.18.0-11-generic N/A linux-backports-modules-4.18.0-11-generic N/A linux-firmware 1.175 Tags: cosmic Uname: Linux 4.18.0-11-generic x86_64 UpgradeStatus: Upgraded to cosmic on 2018-11-03 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/16/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GL753VD.307 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GL753VD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGL753VD.307:bd04/16/2018:svnASUSTeKCOMPUTERINC.:pnGL753VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL753VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ROG dmi.product.name: GL753VD 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/1799718/+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 1799718] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1799718/+attachment/5209028/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1799718 Title: Ubuntu 18.10 fr FAN always ON 5 400 rpm Status in linux package in Ubuntu: Incomplete Bug description: On Ubuntu 18.10 fr since 20181022. By update from 18.04 My PC ASUS ROG GL 753V Notebook PC Fan always on At 5 400 rpm. Air cold ! GPU temp 31 °C PC 33 °C Ubuntu version : 4.18.0.11-generic On startup, says "Failed start load kernel Modules" On picture on attachment : Value of fan is incorrect I don't know where is fan sensor to put on my conky --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rg 4260 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 HibernationDevice: RESUME=UUID=a4c1f9fd-8ee7-4a18-8aa4-8eb2ecead862 InstallationDate: Installed on 2018-10-31 (3 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 0b05:1854 ASUSTek Computer, Inc. Bus 001 Device 004: ID 13d3:5666 IMC Networks Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. GL753VD NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic root=UUID=2172f67c-0362-49ad-9639-8077f44d34f8 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 RelatedPackageVersions: linux-restricted-modules-4.18.0-11-generic N/A linux-backports-modules-4.18.0-11-generic N/A linux-firmware 1.175 Tags: cosmic Uname: Linux 4.18.0-11-generic x86_64 UpgradeStatus: Upgraded to cosmic on 2018-11-03 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/16/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GL753VD.307 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GL753VD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGL753VD.307:bd04/16/2018:svnASUSTeKCOMPUTERINC.:pnGL753VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL753VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ROG dmi.product.name: GL753VD 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/1799718/+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 1799718] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1799718/+attachment/5209029/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1799718 Title: Ubuntu 18.10 fr FAN always ON 5 400 rpm Status in linux package in Ubuntu: Incomplete Bug description: On Ubuntu 18.10 fr since 20181022. By update from 18.04 My PC ASUS ROG GL 753V Notebook PC Fan always on At 5 400 rpm. Air cold ! GPU temp 31 °C PC 33 °C Ubuntu version : 4.18.0.11-generic On startup, says "Failed start load kernel Modules" On picture on attachment : Value of fan is incorrect I don't know where is fan sensor to put on my conky --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rg 4260 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 HibernationDevice: RESUME=UUID=a4c1f9fd-8ee7-4a18-8aa4-8eb2ecead862 InstallationDate: Installed on 2018-10-31 (3 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 0b05:1854 ASUSTek Computer, Inc. Bus 001 Device 004: ID 13d3:5666 IMC Networks Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. GL753VD NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic root=UUID=2172f67c-0362-49ad-9639-8077f44d34f8 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 RelatedPackageVersions: linux-restricted-modules-4.18.0-11-generic N/A linux-backports-modules-4.18.0-11-generic N/A linux-firmware 1.175 Tags: cosmic Uname: Linux 4.18.0-11-generic x86_64 UpgradeStatus: Upgraded to cosmic on 2018-11-03 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/16/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GL753VD.307 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GL753VD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGL753VD.307:bd04/16/2018:svnASUSTeKCOMPUTERINC.:pnGL753VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL753VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ROG dmi.product.name: GL753VD 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/1799718/+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 1799718] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1799718/+attachment/5209023/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1799718 Title: Ubuntu 18.10 fr FAN always ON 5 400 rpm Status in linux package in Ubuntu: Incomplete Bug description: On Ubuntu 18.10 fr since 20181022. By update from 18.04 My PC ASUS ROG GL 753V Notebook PC Fan always on At 5 400 rpm. Air cold ! GPU temp 31 °C PC 33 °C Ubuntu version : 4.18.0.11-generic On startup, says "Failed start load kernel Modules" On picture on attachment : Value of fan is incorrect I don't know where is fan sensor to put on my conky --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rg 4260 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 HibernationDevice: RESUME=UUID=a4c1f9fd-8ee7-4a18-8aa4-8eb2ecead862 InstallationDate: Installed on 2018-10-31 (3 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 0b05:1854 ASUSTek Computer, Inc. Bus 001 Device 004: ID 13d3:5666 IMC Networks Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. GL753VD NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic root=UUID=2172f67c-0362-49ad-9639-8077f44d34f8 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 RelatedPackageVersions: linux-restricted-modules-4.18.0-11-generic N/A linux-backports-modules-4.18.0-11-generic N/A linux-firmware 1.175 Tags: cosmic Uname: Linux 4.18.0-11-generic x86_64 UpgradeStatus: Upgraded to cosmic on 2018-11-03 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/16/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GL753VD.307 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GL753VD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGL753VD.307:bd04/16/2018:svnASUSTeKCOMPUTERINC.:pnGL753VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL753VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ROG dmi.product.name: GL753VD 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/1799718/+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 1799718] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1799718/+attachment/5209024/+files/IwConfig.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1799718 Title: Ubuntu 18.10 fr FAN always ON 5 400 rpm Status in linux package in Ubuntu: Incomplete Bug description: On Ubuntu 18.10 fr since 20181022. By update from 18.04 My PC ASUS ROG GL 753V Notebook PC Fan always on At 5 400 rpm. Air cold ! GPU temp 31 °C PC 33 °C Ubuntu version : 4.18.0.11-generic On startup, says "Failed start load kernel Modules" On picture on attachment : Value of fan is incorrect I don't know where is fan sensor to put on my conky --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rg 4260 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 HibernationDevice: RESUME=UUID=a4c1f9fd-8ee7-4a18-8aa4-8eb2ecead862 InstallationDate: Installed on 2018-10-31 (3 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 0b05:1854 ASUSTek Computer, Inc. Bus 001 Device 004: ID 13d3:5666 IMC Networks Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. GL753VD NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic root=UUID=2172f67c-0362-49ad-9639-8077f44d34f8 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 RelatedPackageVersions: linux-restricted-modules-4.18.0-11-generic N/A linux-backports-modules-4.18.0-11-generic N/A linux-firmware 1.175 Tags: cosmic Uname: Linux 4.18.0-11-generic x86_64 UpgradeStatus: Upgraded to cosmic on 2018-11-03 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/16/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GL753VD.307 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GL753VD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGL753VD.307:bd04/16/2018:svnASUSTeKCOMPUTERINC.:pnGL753VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL753VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ROG dmi.product.name: GL753VD 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/1799718/+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 1799718] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1799718/+attachment/5209025/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1799718 Title: Ubuntu 18.10 fr FAN always ON 5 400 rpm Status in linux package in Ubuntu: Incomplete Bug description: On Ubuntu 18.10 fr since 20181022. By update from 18.04 My PC ASUS ROG GL 753V Notebook PC Fan always on At 5 400 rpm. Air cold ! GPU temp 31 °C PC 33 °C Ubuntu version : 4.18.0.11-generic On startup, says "Failed start load kernel Modules" On picture on attachment : Value of fan is incorrect I don't know where is fan sensor to put on my conky --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rg 4260 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 HibernationDevice: RESUME=UUID=a4c1f9fd-8ee7-4a18-8aa4-8eb2ecead862 InstallationDate: Installed on 2018-10-31 (3 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 0b05:1854 ASUSTek Computer, Inc. Bus 001 Device 004: ID 13d3:5666 IMC Networks Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. GL753VD NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic root=UUID=2172f67c-0362-49ad-9639-8077f44d34f8 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 RelatedPackageVersions: linux-restricted-modules-4.18.0-11-generic N/A linux-backports-modules-4.18.0-11-generic N/A linux-firmware 1.175 Tags: cosmic Uname: Linux 4.18.0-11-generic x86_64 UpgradeStatus: Upgraded to cosmic on 2018-11-03 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/16/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GL753VD.307 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GL753VD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGL753VD.307:bd04/16/2018:svnASUSTeKCOMPUTERINC.:pnGL753VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL753VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ROG dmi.product.name: GL753VD 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/1799718/+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 1799718] AlsaInfo.txt
apport information ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1799718/+attachment/5209021/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1799718 Title: Ubuntu 18.10 fr FAN always ON 5 400 rpm Status in linux package in Ubuntu: Incomplete Bug description: On Ubuntu 18.10 fr since 20181022. By update from 18.04 My PC ASUS ROG GL 753V Notebook PC Fan always on At 5 400 rpm. Air cold ! GPU temp 31 °C PC 33 °C Ubuntu version : 4.18.0.11-generic On startup, says "Failed start load kernel Modules" On picture on attachment : Value of fan is incorrect I don't know where is fan sensor to put on my conky --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rg 4260 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 HibernationDevice: RESUME=UUID=a4c1f9fd-8ee7-4a18-8aa4-8eb2ecead862 InstallationDate: Installed on 2018-10-31 (3 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 0b05:1854 ASUSTek Computer, Inc. Bus 001 Device 004: ID 13d3:5666 IMC Networks Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. GL753VD NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic root=UUID=2172f67c-0362-49ad-9639-8077f44d34f8 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 RelatedPackageVersions: linux-restricted-modules-4.18.0-11-generic N/A linux-backports-modules-4.18.0-11-generic N/A linux-firmware 1.175 Tags: cosmic Uname: Linux 4.18.0-11-generic x86_64 UpgradeStatus: Upgraded to cosmic on 2018-11-03 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/16/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GL753VD.307 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GL753VD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGL753VD.307:bd04/16/2018:svnASUSTeKCOMPUTERINC.:pnGL753VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL753VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ROG dmi.product.name: GL753VD 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/1799718/+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 1799718] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1799718/+attachment/5209032/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1799718 Title: Ubuntu 18.10 fr FAN always ON 5 400 rpm Status in linux package in Ubuntu: Incomplete Bug description: On Ubuntu 18.10 fr since 20181022. By update from 18.04 My PC ASUS ROG GL 753V Notebook PC Fan always on At 5 400 rpm. Air cold ! GPU temp 31 °C PC 33 °C Ubuntu version : 4.18.0.11-generic On startup, says "Failed start load kernel Modules" On picture on attachment : Value of fan is incorrect I don't know where is fan sensor to put on my conky --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rg 4260 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 HibernationDevice: RESUME=UUID=a4c1f9fd-8ee7-4a18-8aa4-8eb2ecead862 InstallationDate: Installed on 2018-10-31 (3 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 0b05:1854 ASUSTek Computer, Inc. Bus 001 Device 004: ID 13d3:5666 IMC Networks Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. GL753VD NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic root=UUID=2172f67c-0362-49ad-9639-8077f44d34f8 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 RelatedPackageVersions: linux-restricted-modules-4.18.0-11-generic N/A linux-backports-modules-4.18.0-11-generic N/A linux-firmware 1.175 Tags: cosmic Uname: Linux 4.18.0-11-generic x86_64 UpgradeStatus: Upgraded to cosmic on 2018-11-03 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/16/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GL753VD.307 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GL753VD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGL753VD.307:bd04/16/2018:svnASUSTeKCOMPUTERINC.:pnGL753VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL753VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ROG dmi.product.name: GL753VD 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/1799718/+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 1799718] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1799718/+attachment/5209026/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1799718 Title: Ubuntu 18.10 fr FAN always ON 5 400 rpm Status in linux package in Ubuntu: Incomplete Bug description: On Ubuntu 18.10 fr since 20181022. By update from 18.04 My PC ASUS ROG GL 753V Notebook PC Fan always on At 5 400 rpm. Air cold ! GPU temp 31 °C PC 33 °C Ubuntu version : 4.18.0.11-generic On startup, says "Failed start load kernel Modules" On picture on attachment : Value of fan is incorrect I don't know where is fan sensor to put on my conky --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rg 4260 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 HibernationDevice: RESUME=UUID=a4c1f9fd-8ee7-4a18-8aa4-8eb2ecead862 InstallationDate: Installed on 2018-10-31 (3 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 0b05:1854 ASUSTek Computer, Inc. Bus 001 Device 004: ID 13d3:5666 IMC Networks Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. GL753VD NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic root=UUID=2172f67c-0362-49ad-9639-8077f44d34f8 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 RelatedPackageVersions: linux-restricted-modules-4.18.0-11-generic N/A linux-backports-modules-4.18.0-11-generic N/A linux-firmware 1.175 Tags: cosmic Uname: Linux 4.18.0-11-generic x86_64 UpgradeStatus: Upgraded to cosmic on 2018-11-03 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/16/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GL753VD.307 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GL753VD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGL753VD.307:bd04/16/2018:svnASUSTeKCOMPUTERINC.:pnGL753VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL753VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ROG dmi.product.name: GL753VD 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/1799718/+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 1799718] Re: Ubuntu 18.10 fr FAN always ON 5 400 rpm
Hie, Too much bugs to restart pc. Finally after format hard disk, impossible to install Ubuntu 18.04... My PC : ASUS ROG GL753VD. Notebook . Bios change version (307)... No possibility to put a bootable usb on CSM mode... Only EFI permiss. To restart, I put Ubuntu 16.04 EFI, then upgrade with ubuntu 18.04.1 and then bug !!! Black screen and problem with ACPI temp sensors... See attachment words To restart, Recovery start/ Clean and remove all fills proposed, Then dkpg repair. Then resume and black screen obtained ! Restart and Ubuntu 18.04 gone in bad quality Then, upgrade on Ubuntu 18.10. Seems correct but many fonction don't work ! (colour of screen (fade and white cloud... no contrast, saturation can be used) Driver AMDNVidia correct (390), virtualbox (I am looking on forum to see more...)). This way ubuntu 18.10 is correctly installed. He asked me a new password to bios enter... I think that is a problem of EFI and secure boot management... And too bugs with sensors use. I don't find where is fan sensor... ** Attachment added: "EFI bugs" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1799718/+attachment/5209020/+files/Bug%20Ub%2018%2004%201.odt ** Tags added: apport-collected cosmic ** Description changed: On Ubuntu 18.10 fr since 20181022. By update from 18.04 My PC ASUS ROG GL 753V Notebook PC Fan always on At 5 400 rpm. Air cold ! GPU temp 31 °C PC 33 °C Ubuntu version : 4.18.0.11-generic On startup, says "Failed start load kernel Modules" - On picture on attachment : Value of fan is incorrect I don't know where - is fan sensor to put on my conky + On picture on attachment : Value of fan is incorrect I don't know where is fan sensor to put on my conky + --- + ProblemType: Bug + ApportVersion: 2.20.10-0ubuntu13.1 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: rg 4260 F pulseaudio + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 18.10 + HibernationDevice: RESUME=UUID=a4c1f9fd-8ee7-4a18-8aa4-8eb2ecead862 + InstallationDate: Installed on 2018-10-31 (3 days ago) + InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) + Lsusb: + Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 001 Device 003: ID 8087:0a2a Intel Corp. + Bus 001 Device 002: ID 0b05:1854 ASUSTek Computer, Inc. + Bus 001 Device 004: ID 13d3:5666 IMC Networks + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + MachineType: ASUSTeK COMPUTER INC. GL753VD + NonfreeKernelModules: nvidia_modeset nvidia + Package: linux (not installed) + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=fr_FR.UTF-8 + SHELL=/bin/bash + ProcFB: 0 inteldrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic root=UUID=2172f67c-0362-49ad-9639-8077f44d34f8 ro quiet splash vt.handoff=1 + ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 + RelatedPackageVersions: + linux-restricted-modules-4.18.0-11-generic N/A + linux-backports-modules-4.18.0-11-generic N/A + linux-firmware 1.175 + Tags: cosmic + Uname: Linux 4.18.0-11-generic x86_64 + UpgradeStatus: Upgraded to cosmic on 2018-11-03 (0 days ago) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 04/16/2018 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: GL753VD.307 + dmi.board.asset.tag: ATN12345678901234567 + dmi.board.name: GL753VD + dmi.board.vendor: ASUSTeK COMPUTER INC. + dmi.board.version: 1.0 + dmi.chassis.asset.tag: No Asset Tag + dmi.chassis.type: 10 + dmi.chassis.vendor: ASUSTeK COMPUTER INC. + dmi.chassis.version: 1.0 + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGL753VD.307:bd04/16/2018:svnASUSTeKCOMPUTERINC.:pnGL753VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL753VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: + dmi.product.family: ROG + dmi.product.name: GL753VD + dmi.product.version: 1.0 + dmi.sys.vendor: ASUSTeK COMPUTER INC. -- 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/1799718 Title: Ubuntu 18.10 fr FAN always ON 5 400 rpm Status in linux package in Ubuntu: Incomplete Bug description: On Ubuntu 18.10 fr since 20181022. By update from 18.04 My PC ASUS ROG GL 753V Notebook PC Fan always on At 5 400 rpm. Air cold ! GPU temp 31 °C PC 33 °C Ubuntu version : 4.18.0.11-generic On startup, says "Failed start load kernel Modules" On picture on attachment : Value of fan is incorrect I don't know where is fan sensor to put on my conky --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rg 4260 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 HibernationDevice: RESUME=UUID=a4
[Kernel-packages] [Bug 1801577] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1801577 Title: package linux-headers-4.4.0-96 4.4.0-96.119 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in linux package in Ubuntu: Confirmed Bug description: Linux Ubuntu mate. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-headers-4.4.0-96 4.4.0-96.119 ProcVersionSignature: Ubuntu 4.4.0-138.164-generic 4.4.155 Uname: Linux 4.4.0-138-generic i686 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: johnnyreb 1872 F...m pulseaudio /dev/snd/controlC0: johnnyreb 1872 F pulseaudio Date: Sun Nov 4 08:20:41 2018 DpkgHistoryLog: Start-Date: 2018-11-04 08:19:40 Commandline: aptdaemon role='role-commit-packages' sender=':1.66' Install: ubuntu-advantage-tools:i386 (10ubuntu0.16.04.1, automatic) Upgrade: update-manager-core:i386 (1:16.04.14, 1:16.04.15), friendly-recovery:i386 (0.2.31ubuntu1, 0.2.31ubuntu2), update-manager:i386 (1:16.04.14, 1:16.04.15), ubuntu-standard:i386 (1.361.1, 1.361.2), ubuntu-minimal:i386 (1.361.1, 1.361.2), dpkg:i386 (1.18.4ubuntu1.4, 1.18.4ubuntu1.5), python3-update-manager:i386 (1:16.04.14, 1:16.04.15), libdpkg-perl:i386 (1.18.4ubuntu1.4, 1.18.4ubuntu1.5), secureboot-db:i386 (1.1, 1.4~ubuntu0.16.04.1), dpkg-dev:i386 (1.18.4ubuntu1.4, 1.18.4ubuntu1.5) DuplicateSignature: package:linux-headers-4.4.0-96:4.4.0-96.119 Processing triggers for mime-support (3.59ubuntu1) ... dpkg: error processing package linux-headers-4.4.0-96 (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration HibernationDevice: RESUME=UUID=6783c982-9133-4a7b-b7fb-a98cc9f16216 InstallationDate: Installed on 2016-09-06 (788 days ago) InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1) MachineType: System manufacturer System Product Name PackageArchitecture: all ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-138-generic root=UUID=f010cd2c-4c9f-4785-b4ce-c0df263752d3 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.18 SourcePackage: linux Title: package linux-headers-4.4.0-96 4.4.0-96.119 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/01/2007 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1221 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5B-Deluxe 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.:bvr1221:bd11/01/2007:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5B-Deluxe: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/ubuntu/+source/linux/+bug/1801577/+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 1801577] Re: package linux-headers-4.4.0-96 4.4.0-96.119 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting confi
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1801577 Title: package linux-headers-4.4.0-96 4.4.0-96.119 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in linux package in Ubuntu: New Bug description: Linux Ubuntu mate. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-headers-4.4.0-96 4.4.0-96.119 ProcVersionSignature: Ubuntu 4.4.0-138.164-generic 4.4.155 Uname: Linux 4.4.0-138-generic i686 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: johnnyreb 1872 F...m pulseaudio /dev/snd/controlC0: johnnyreb 1872 F pulseaudio Date: Sun Nov 4 08:20:41 2018 DpkgHistoryLog: Start-Date: 2018-11-04 08:19:40 Commandline: aptdaemon role='role-commit-packages' sender=':1.66' Install: ubuntu-advantage-tools:i386 (10ubuntu0.16.04.1, automatic) Upgrade: update-manager-core:i386 (1:16.04.14, 1:16.04.15), friendly-recovery:i386 (0.2.31ubuntu1, 0.2.31ubuntu2), update-manager:i386 (1:16.04.14, 1:16.04.15), ubuntu-standard:i386 (1.361.1, 1.361.2), ubuntu-minimal:i386 (1.361.1, 1.361.2), dpkg:i386 (1.18.4ubuntu1.4, 1.18.4ubuntu1.5), python3-update-manager:i386 (1:16.04.14, 1:16.04.15), libdpkg-perl:i386 (1.18.4ubuntu1.4, 1.18.4ubuntu1.5), secureboot-db:i386 (1.1, 1.4~ubuntu0.16.04.1), dpkg-dev:i386 (1.18.4ubuntu1.4, 1.18.4ubuntu1.5) DuplicateSignature: package:linux-headers-4.4.0-96:4.4.0-96.119 Processing triggers for mime-support (3.59ubuntu1) ... dpkg: error processing package linux-headers-4.4.0-96 (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration HibernationDevice: RESUME=UUID=6783c982-9133-4a7b-b7fb-a98cc9f16216 InstallationDate: Installed on 2016-09-06 (788 days ago) InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1) MachineType: System manufacturer System Product Name PackageArchitecture: all ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-138-generic root=UUID=f010cd2c-4c9f-4785-b4ce-c0df263752d3 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.18 SourcePackage: linux Title: package linux-headers-4.4.0-96 4.4.0-96.119 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/01/2007 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1221 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5B-Deluxe 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.:bvr1221:bd11/01/2007:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5B-Deluxe: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/ubuntu/+source/linux/+bug/1801577/+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 1801577] [NEW] package linux-headers-4.4.0-96 4.4.0-96.119 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting con
Public bug reported: Linux Ubuntu mate. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-headers-4.4.0-96 4.4.0-96.119 ProcVersionSignature: Ubuntu 4.4.0-138.164-generic 4.4.155 Uname: Linux 4.4.0-138-generic i686 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: johnnyreb 1872 F...m pulseaudio /dev/snd/controlC0: johnnyreb 1872 F pulseaudio Date: Sun Nov 4 08:20:41 2018 DpkgHistoryLog: Start-Date: 2018-11-04 08:19:40 Commandline: aptdaemon role='role-commit-packages' sender=':1.66' Install: ubuntu-advantage-tools:i386 (10ubuntu0.16.04.1, automatic) Upgrade: update-manager-core:i386 (1:16.04.14, 1:16.04.15), friendly-recovery:i386 (0.2.31ubuntu1, 0.2.31ubuntu2), update-manager:i386 (1:16.04.14, 1:16.04.15), ubuntu-standard:i386 (1.361.1, 1.361.2), ubuntu-minimal:i386 (1.361.1, 1.361.2), dpkg:i386 (1.18.4ubuntu1.4, 1.18.4ubuntu1.5), python3-update-manager:i386 (1:16.04.14, 1:16.04.15), libdpkg-perl:i386 (1.18.4ubuntu1.4, 1.18.4ubuntu1.5), secureboot-db:i386 (1.1, 1.4~ubuntu0.16.04.1), dpkg-dev:i386 (1.18.4ubuntu1.4, 1.18.4ubuntu1.5) DuplicateSignature: package:linux-headers-4.4.0-96:4.4.0-96.119 Processing triggers for mime-support (3.59ubuntu1) ... dpkg: error processing package linux-headers-4.4.0-96 (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration HibernationDevice: RESUME=UUID=6783c982-9133-4a7b-b7fb-a98cc9f16216 InstallationDate: Installed on 2016-09-06 (788 days ago) InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1) MachineType: System manufacturer System Product Name PackageArchitecture: all ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-138-generic root=UUID=f010cd2c-4c9f-4785-b4ce-c0df263752d3 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.18 SourcePackage: linux Title: package linux-headers-4.4.0-96 4.4.0-96.119 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/01/2007 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1221 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5B-Deluxe 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.:bvr1221:bd11/01/2007:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5B-Deluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 xenial -- 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/1801577 Title: package linux-headers-4.4.0-96 4.4.0-96.119 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in linux package in Ubuntu: New Bug description: Linux Ubuntu mate. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-headers-4.4.0-96 4.4.0-96.119 ProcVersionSignature: Ubuntu 4.4.0-138.164-generic 4.4.155 Uname: Linux 4.4.0-138-generic i686 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: johnnyreb 1872 F...m pulseaudio /dev/snd/controlC0: johnnyreb 1872 F pulseaudio Date: Sun Nov 4 08:20:41 2018 DpkgHistoryLog: Start-Date: 2018-11-04 08:19:40 Commandline: aptdaemon role='role-commit-packages' sender=':1.66' Install: ubuntu-advantage-tools:i386 (10ubuntu0.16.04.1, automatic) Upgrade: update-manager-core:i386 (1:16.04.14, 1:16.04.15), friendly-recovery:i386 (0.2.31ubuntu1, 0.2.31ubuntu2), update-manager:i386 (1:16.04.14, 1:16.04.15), ubuntu-standard:i386 (1.361.1, 1.361.2), ubuntu-minimal:i386 (1.361.1, 1.361.2), dpkg:i386 (1.18.4ubuntu1.4, 1.18.4ubuntu1.5), python3-update-manager:i386 (1:16.04.14, 1:16.04.15), libdpkg-perl:i386 (1.18.4ubuntu1.4, 1.18.4ubuntu1.5), secureboot-db:i386 (1.1, 1.4~ubuntu0.16.04.1), dpkg-dev:i386 (1.18.4ubuntu1.4, 1.18.4ubuntu1.5) DuplicateSignature: package:linux-headers-4.4.0-96:4.4.0-96.119 Processing triggers for mime-support (3.59ubuntu1) ... dpkg: error processing package linux-headers-4.4.0
[Kernel-packages] [Bug 1722478] Re: Two-finger scrolling no longer works after resuming from suspend
I can also confirm that this problem still exists with a fresh install of Ubuntu 18.10 with kernel 4.18.0.. I will try the psmouse.synaptics_intertouch=0 workaround. -- 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/1722478 Title: Two-finger scrolling no longer works after resuming from suspend Status in Linux: Confirmed Status in linux package in Ubuntu: Incomplete Bug description: I own a Thinkpad T440p onto which I have had Debian 9 running without hardware issues. I have recently installed Ubuntu 17.10 final beta to test it out, but two-finger scrolling does not work at the moment. It used to work out-of-the-box from the final beta iso, but a subsequent update broke it. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-12-generic 4.13.0-12.13 [modified: boot/vmlinuz-4.13.0-12-generic] ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ghislain 10620 F pulseaudio /dev/snd/controlC0: ghislain 10620 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Oct 10 09:20:01 2017 HibernationDevice: RESUME=UUID=ae4cca1e-80ef-4a1e-87e3-0a860b49492e InstallationDate: Installed on 2017-10-05 (4 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) MachineType: LENOVO 20AN00C1UK ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-12-generic root=/dev/mapper/doc1485--lap--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-12-generic N/A linux-backports-modules-4.13.0-12-generic N/A linux-firmware 1.169 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/31/2016 dmi.bios.vendor: LENOVO dmi.bios.version: GLET83WW (2.37 ) dmi.board.asset.tag: Not Available dmi.board.name: 20AN00C1UK dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGLET83WW(2.37):bd03/31/2016:svnLENOVO:pn20AN00C1UK:pvrThinkPadT440p:rvnLENOVO:rn20AN00C1UK:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T440p dmi.product.name: 20AN00C1UK dmi.product.version: ThinkPad T440p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1722478/+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 1801573] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1801573 Title: pc randomly freeze Status in linux package in Ubuntu: Confirmed Bug description: pc with ubuntu 18.04 randomly freeze and i'm forced to turn it off. This often happens while playing VLC 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: plraska8379 F pulseaudio /dev/snd/controlC0: plraska8379 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Nov 4 08:23:54 2018 InstallationDate: Installed on 2018-10-03 (31 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: HP HP Laptop 15-db0xxx ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic root=UUID=c1c43279-03a7-4d7e-8b7e-9b999190af0a 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 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/26/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.03 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 84AE dmi.board.vendor: HP dmi.board.version: 86.19 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.03:bd04/26/2018:svnHP:pnHPLaptop15-db0xxx:pvrType1ProductConfigId:rvnHP:rn84AE:rvr86.19:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15-db0xxx dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801573/+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 1801574] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1801574 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: cosmic -- 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/1801574 Title: [cosmic] ipoib ping with large message size failed Status in linux package in Ubuntu: Incomplete Bug description: We see that ping over ipoib interface stuck with large packets, this is a new degradation, this test pass on Ubuntu 18.04. After investigating the issue, we see that commit [1] introduce the issue, and it is not an upstream commit, it is canonical commit. Could you please check with the canonical kernel team why they revert that commit? To reproduce the bug, please use ConnectX-3 devices with ipoib connection with 2044 MTU (default) and run command [2]. Is there open Launchpad on it? [1] commit 77a24c313d21e3765b04d90521e9228a9bb6e332 Author: Tyler Hicks Date: Fri Aug 3 21:53:15 2018 + Revert "net: increase fragment memory usage limits" This reverts commit c2a936600f78aea00d3312ea4b66a79a4619f9b4. It made denial of service attacks on the IP fragment handling easier to carry out. CVE-2018-5391 Signed-off-by: Tyler Hicks Signed-off-by: Stefan Bader [2] ping 13.194.22.1 -I 13.194.23.1 -s 65507 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801574/+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 1801574] [NEW] [cosmic] ipoib ping with large message size failed
Public bug reported: We see that ping over ipoib interface stuck with large packets, this is a new degradation, this test pass on Ubuntu 18.04. After investigating the issue, we see that commit [1] introduce the issue, and it is not an upstream commit, it is canonical commit. Could you please check with the canonical kernel team why they revert that commit? To reproduce the bug, please use ConnectX-3 devices with ipoib connection with 2044 MTU (default) and run command [2]. Is there open Launchpad on it? [1] commit 77a24c313d21e3765b04d90521e9228a9bb6e332 Author: Tyler Hicks Date: Fri Aug 3 21:53:15 2018 + Revert "net: increase fragment memory usage limits" This reverts commit c2a936600f78aea00d3312ea4b66a79a4619f9b4. It made denial of service attacks on the IP fragment handling easier to carry out. CVE-2018-5391 Signed-off-by: Tyler Hicks Signed-off-by: Stefan Bader [2] ping 13.194.22.1 -I 13.194.23.1 -s 65507 ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: cosmic ** Summary changed: - [bionic] ipoib ping with large message size failed + [cosmic] ipoib ping with large message size failed -- 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/1801574 Title: [cosmic] ipoib ping with large message size failed Status in linux package in Ubuntu: Incomplete Bug description: We see that ping over ipoib interface stuck with large packets, this is a new degradation, this test pass on Ubuntu 18.04. After investigating the issue, we see that commit [1] introduce the issue, and it is not an upstream commit, it is canonical commit. Could you please check with the canonical kernel team why they revert that commit? To reproduce the bug, please use ConnectX-3 devices with ipoib connection with 2044 MTU (default) and run command [2]. Is there open Launchpad on it? [1] commit 77a24c313d21e3765b04d90521e9228a9bb6e332 Author: Tyler Hicks Date: Fri Aug 3 21:53:15 2018 + Revert "net: increase fragment memory usage limits" This reverts commit c2a936600f78aea00d3312ea4b66a79a4619f9b4. It made denial of service attacks on the IP fragment handling easier to carry out. CVE-2018-5391 Signed-off-by: Tyler Hicks Signed-off-by: Stefan Bader [2] ping 13.194.22.1 -I 13.194.23.1 -s 65507 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801574/+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 1801573] [NEW] pc randomly freeze
Public bug reported: pc with ubuntu 18.04 randomly freeze and i'm forced to turn it off. This often happens while playing VLC 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: plraska8379 F pulseaudio /dev/snd/controlC0: plraska8379 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Nov 4 08:23:54 2018 InstallationDate: Installed on 2018-10-03 (31 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: HP HP Laptop 15-db0xxx ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic root=UUID=c1c43279-03a7-4d7e-8b7e-9b999190af0a 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 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/26/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.03 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 84AE dmi.board.vendor: HP dmi.board.version: 86.19 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.03:bd04/26/2018:svnHP:pnHPLaptop15-db0xxx:pvrType1ProductConfigId:rvnHP:rn84AE:rvr86.19:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15-db0xxx dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1801573 Title: pc randomly freeze Status in linux package in Ubuntu: New Bug description: pc with ubuntu 18.04 randomly freeze and i'm forced to turn it off. This often happens while playing VLC 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: plraska8379 F pulseaudio /dev/snd/controlC0: plraska8379 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Nov 4 08:23:54 2018 InstallationDate: Installed on 2018-10-03 (31 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: HP HP Laptop 15-db0xxx ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic root=UUID=c1c43279-03a7-4d7e-8b7e-9b999190af0a 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 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/26/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.03 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 84AE dmi.board.vendor: HP dmi.board.version: 86.19 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.03:bd04/26/2018:svnHP:pnHPLaptop15-db0xxx:pvrType1ProductConfigId:rvnHP:rn84AE:rvr86.19:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15-db0xxx dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801573/+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