[Kernel-packages] [Bug 1790511] Re: General protection fault while trying to discover a nvmeof target
** Description changed: nvme discover command times out and results in general protection fault in kernel. # nvme discover -t rdma -a 10.1.1.6 -s 4420 Failed to write to /dev/nvme-fabrics: Input/output error^M - # + # # [16900.248129] nvme nvme0: Connect command failed, error wo/DNR bit: 7 [16900.248182] nvme nvme0: failed to connect queue: 0 ret=7 [16900.253138] nvme nvme0: Reconnecting in 10 seconds... [16910.300029] general protection fault: [#1] SMP PTI [16910.300069] Modules linked in: mlx4_en mlx4_ib mlx4_core nvme_rdma nvme_fabrics nvme_core rdma_ucm ib_umad ib_ucm ib_uverbs xt_conntrack ipt_MASQUERADE nf_nat_masquerade_ipv4 nfnetlink xfrm_user xfrm_algo iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack xt_addrtype overlay aufs joydev input_leds ipmi_ssif intel_rapl skx_edac x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm irqbypass intel_cstate intel_rapl_perf mei_me mei ioatdma lpc_ich shpchp sch_fq_codel ipmi_si ipmi_devintf ipmi_msghandler acpi_pad mac_hid acpi_power_meter iptable_filter ip6table_filter ip6_tables br_netfilter bridge stp llc arp_tables ib_iser rdma_cm iw_cm ib_cm iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov [16910.300534] async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear mlx5_ib ib_core hid_generic usbhid hid crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc aesni_intel aes_x86_64 crypto_simd glue_helper cryptd mlx5_core ast mlxfw i2c_algo_bit devlink ttm drm_kms_helper ixgbe syscopyarea sysfillrect sysimgblt fb_sys_fops dca ptp drm pps_core mdio ahci libahci wmi [last unloaded: nvme_core] [16910.300794] CPU: 33 PID: 3173 Comm: kworker/u146:1 Not tainted 4.15.0-33-generic #36-Ubuntu [16910.300845] Hardware name: Supermicro SYS-6019U-TN4RT/X11DPU, BIOS 2.0b 02/24/2018 [16910.300898] Workqueue: nvme-wq nvme_rdma_reconnect_ctrl_work [nvme_rdma] [16910.300945] RIP: 0010:nvme_rdma_alloc_queue+0x3c/0x190 [nvme_rdma] [16910.300984] RSP: 0018:9ba8a037be08 EFLAGS: 00010206 [16910.301019] RAX: RBX: 52404d65f5994178 RCX: 8a0f78002820 [16910.301063] RDX: c0b58600 RSI: c0b573ab RDI: 8a0f70aec000 [16910.301108] RBP: 9ba8a037be28 R08: 0334 R09: [16910.301152] R10: R11: 0337 R12: 8a0f70aec000 [16910.301195] R13: R14: 0020 R15: [16910.301240] FS: () GS:8a0f7efc() knlGS: [16910.301289] CS: 0010 DS: ES: CR0: 80050033 [16910.301326] CR2: 7ffc4e5cadb8 CR3: 00123ba0a003 CR4: 007606e0 [16910.301370] DR0: DR1: DR2: [16910.301414] DR3: DR6: fffe0ff0 DR7: 0400 [16910.301458] PKRU: 5554 [16910.301477] Call Trace: [16910.301504] nvme_rdma_configure_admin_queue+0x22/0x2d0 [nvme_rdma] [16910.301548] nvme_rdma_reconnect_ctrl_work+0x27/0xd0 [nvme_rdma] [16910.301591] process_one_work+0x1de/0x410 [16910.301620] worker_thread+0x32/0x410 [16910.301651] kthread+0x121/0x140 [16910.301676] ? process_one_work+0x410/0x410 [16910.301707] ? kthread_create_worker_on_cpu+0x70/0x70 [16910.301744] ? do_syscall_64+0x73/0x130 [16910.301774] ? SyS_exit_group+0x14/0x20 [16910.301805] ret_from_fork+0x35/0x40 [16910.301831] Code: 89 e5 41 56 41 55 41 54 53 48 8d 1c c5 00 00 00 00 49 89 fc 49 89 c5 49 89 d6 48 29 c3 48 c7 c2 00 86 b5 c0 48 c1 e3 04 48 03 1f <48> 89 7b 18 48 8d 7b 58 c7 43 50 00 00 00 00 e8 20 d4 57 ef 45 [16910.305367] RIP: nvme_rdma_alloc_queue+0x3c/0x190 [nvme_rdma] RSP: 9ba8a037be08 [16910.307146] ---[ end trace 3ae215b72b2ac870 ]--- # # lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 18.04.1 LTS Release:18.04 Codename: bionic # # uname -a Linux esdev005 4.15.0-33-generic #36-Ubuntu SMP Wed Aug 15 16:00:05 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux # -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1790511 Title: General protection fault while trying to discover a nvmeof target Status in linux package in Ubuntu: Incomplete Bug description: nvme discover command times out and results in general protection fault in kernel. # nvme discover -t rdma -a 10.1.1.6 -s 4420 Failed to write to /dev/nvme-fabrics: Input/output error^M # # [16900.248129] nvme nvme0: Connect command failed, error wo/DNR bit: 7 [16900.248182] nvme nvme0: failed to connect queue: 0 ret=7 [16900.253138] nvme nvme0: Reconnecting in 10 seconds... [16910.300029] general protection fault: [#1] SMP PTI
[Kernel-packages] [Bug 1791754] Re: linux: 3.13.0-159.209 -proposed tracker
** Summary changed: - linux: -proposed tracker + linux: 3.13.0-159.209 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El Mously (kmously) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El Mously (kmously) ** Changed in: kernel-sru-workflow/prepare-package-signed Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El Mously (kmously) -- 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/1791754 Title: linux: 3.13.0-159.209 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1791756 (linux-lts-trusty) derivatives: To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1791754/+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 1792002] Re: Wireless signal extremely weak or not detected
Unable to run the command in the terminal window: apport-collect 1792002 Error: apport-collect: command not found. I'm a newbie to LM (v19, Tara). Pl give the detailed steps if you need the logs. However the kindly node that I've never had this issue till kernel v4.15.0.32 and whenever I've upgraded the kernel. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1792002 Title: Wireless signal extremely weak or not detected Status in linux package in Ubuntu: Confirmed Bug description: Hi Support, I'm Linux Mint newbie started using from LM v18. I'm using HP245 series laptop with AMD A6-7310 APU & Wifi driver Realtek RTL8723BE. Currently I've migrated from Linux 18 (Sylvia) to Linux 19 (Tara) abt a month ago. I'm facing a WiFi signal problem whenever I've tried to upgrade to Kernel v4.15.0.33 or v4.15.0.34. The Wifi signal strength is either very weak & disconnects frequently or cannot be detected from very small distances (3-5 mtr). I've never had this issue till kernel v4.15.0.32 and everything was working fine and currently I had to downgrade or revert back to 4.15.0.32 again in order to receive signal to write this mail. Kindly resolve this error ASAP as I want to upgrade to the latest version. Regards, Joseph To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1792002/+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 1791746] Re: linux-aws: 4.4.0-1030.33 -proposed tracker
** Summary changed: - linux-aws: -proposed tracker + linux-aws: 4.4.0-1030.33 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El Mously (kmously) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El Mously (kmously) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1791746 Title: linux-aws: 4.4.0-1030.33 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Trusty: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1791745 phase: Packaging To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1791746/+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 1791749] Re: linux-aws: 4.4.0-1068.78 -proposed tracker
** Summary changed: - linux-aws: 4.4.0-1067.77 -proposed tracker + linux-aws: 4.4.0-1068.78 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Fix Released => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Status: Fix Released => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1791749 Title: linux-aws: 4.4.0-1068.78 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1791745 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1791749/+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 1791745] Re: linux: 4.4.0-136.162 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed ** Tags added: block-proposed-xenial ** Tags added: block-proposed ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1791746 (linux-aws), bug 1791747 (linux-lts-xenial) derivatives: bug 1791749 (linux-aws), bug 1791750 (linux-euclid), bug 1791751 (linux-kvm), bug 1791752 (linux-raspi2), bug 1791753 (linux-snapdragon) kernel-stable-phase:Uploaded kernel-stable-phase-changed:Tuesday, 11. September 2018 15:30 UTC -- swm properties -- + boot-testing-requested: true phase: Uploaded -- 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/1791745 Title: linux: 4.4.0-136.162 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-certification-testing series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1791746 (linux-aws), bug 1791747 (linux-lts-xenial) derivatives: bug 1791749 (linux-aws), bug 1791750 (linux-euclid), bug 1791751 (linux-kvm), bug 1791752 (linux-raspi2), bug 1791753 (linux-snapdragon) kernel-stable-phase:Uploaded kernel-stable-phase-changed:Tuesday, 11. September 2018 15:30 UTC -- swm properties -- boot-testing-requested: true phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1791745/+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 1791749] Re: linux-aws: 4.4.0-1067.77 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed ** Tags added: block-proposed-xenial ** Tags added: block-proposed ** Changed in: kernel-sru-workflow/snap-release-to-stable Status: New => Invalid ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1791745 phase: Packaging + kernel-stable-phase-changed:Wednesday, 12. September 2018 04:31 UTC + kernel-stable-phase:Uploaded ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- + boot-testing-requested: true kernel-stable-master-bug: 1791745 - phase: Packaging - kernel-stable-phase-changed:Wednesday, 12. September 2018 04:31 UTC - kernel-stable-phase:Uploaded + phase: Uploaded -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1791749 Title: linux-aws: 4.4.0-1068.78 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1791745 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1791749/+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 1791749] Re: linux-aws: 4.4.0-1067.77 -proposed tracker
** Summary changed: - linux-aws: -proposed tracker + linux-aws: 4.4.0-1067.77 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El Mously (kmously) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El Mously (kmously) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1791749 Title: linux-aws: 4.4.0-1068.78 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1791745 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1791749/+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
Thanks for the detail test. I have another X1 Carbon 6th, but it cann't reproduce your issue. Could you isolate which change solve this issue? 1, suspend/resume; 2, kernel update; 3, libinput update. My X1 Carbon's PnP ID is the same as yours, so I think we have the same touchpad. But the product ID is not the same. -- 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: Confirmed 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:
[Kernel-packages] [Bug 1748565] Re: Kernel regularly logs: Bluetooth: hci0: last event is not cmd complete (0x0f)
Everyone, if you would like this bug fixed then the most effective place to discuss it is directly with the Bluetooth/kernel developers here: https://bugzilla.kernel.org/show_bug.cgi?id=198699 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1748565 Title: Kernel regularly logs: Bluetooth: hci0: last event is not cmd complete (0x0f) Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Hello, dmesg: [ 3363.056494] Bluetooth: hci0: last event is not cmd complete (0x0f) Regards, -- Cristian ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-9-generic 4.15.0-9.10 ProcVersionSignature: Ubuntu 4.15.0-9.10-generic 4.15.2 Uname: Linux 4.15.0-9-generic x86_64 ApportVersion: 2.20.8-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: caravena 1811 F pulseaudio CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME Date: Fri Feb 9 20:35:29 2018 InstallationDate: Installed on 2017-10-13 (119 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-9-generic root=UUID=707d0f89-4b1d-4432-9d50-6058dc4c1ee9 ro rootflags=subvol=@ quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-9-generic N/A linux-backports-modules-4.15.0-9-generic N/A linux-firmware1.170 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P14AAJ dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: SAMSUNG_NP1234567890 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.family: ChiefRiver System dmi.product.name: 530U3C/530U4C dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1748565/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1791663] Re: linux: 4.18.0-8.9 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: derivatives: bug 1791664 (linux-azure) - kernel-phase:Uploaded - kernel-phase-changed:Tuesday, 11. September 2018 16:02 UTC - -- swm properties -- backports: null derivatives: null phase: Uploaded + kernel-phase:Promoted to proposed + kernel-phase-changed:Wednesday, 12. September 2018 01:02 UTC ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: derivatives: bug 1791664 (linux-azure) -- swm properties -- backports: null derivatives: null - phase: Uploaded - kernel-phase:Promoted to proposed - kernel-phase-changed:Wednesday, 12. September 2018 01:02 UTC + phase: Promoted to proposed + proposed-announcement-sent: true + proposed-testing-requested: true -- 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/1791663 Title: linux: 4.18.0-8.9 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux source package in Cosmic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: derivatives: bug 1791664 (linux-azure) -- swm properties -- backports: null derivatives: null phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1791663/+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 1780817] Re: kernel panic in nested VM with latest 4.15 kernel (4.15.0-24-generic)
I can confirm this, the issue showed up in 4.14. I have tried a number kernels from http://kernel.ubuntu.com/~kernel-ppa/mainline/, and found that somewhere between 4.13.16 and 4.14.0 this bug introduced itself. I am running a fresh install of Bionic, not an upgrade. -- 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/1780817 Title: kernel panic in nested VM with latest 4.15 kernel (4.15.0-24-generic) Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Bug description: When starting a nested VM in a Bionic VM, the "host" VM kernel panics following a simple drop to QEMU monitor by hitting A-c. For some reason kdump is unable to capture the kernel panic so I only have a screen capture of the panic. It also happens on the latest mainline kernel(4.18-rc4). It is fairly trivial to reproduce. In a Bionic VM, install qemu & ovmf and run the following : qemu-system-x86_64 -enable-kvm \ -name balloontest \ -display none \ -monitor none \ -nographic \ -nodefaults \ -m 2048M \ -serial mon:stdio \ -smp 2 \ -cpu host \ -drive if=pflash,format=raw,readonly,file=/usr/share/OVMF/OVMF_CODE.fd \ -drive if=pflash,format=raw,file=/home/caribou/balloon/efi.vars Use A-c to drop to QEMU monitor and . ^[]0;/opt/ocs/gotty-serial/nolp-cli^G^[]2;Loading...^G^[]2;avogadro^G[ 267.784299] general protection fault: [#1] SMP PTI [ 267.785834] Modules linked in: nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo xt_addrtype ip6t_MASQUERADE nf_nat_masquerade_ipv6 ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 ip6table_filter i> [ 267.804312] xor raid6_pq libcrc32c raid1 raid0 multipath linear floppy aesni_intel pata_acpi aes_x86_64 crypto_simd cryptd glue_helper psmouse i2c_piix4 virtio_net virtio_blk [ 267.807946] CPU: 6 PID: 0 Comm: swapper/6 Not tainted 4.15.0-24-generic #26-Ubuntu [ 267.809710] Hardware name: Scaleway Standard PC (i440FX + PIIX, 1996), BIOS 0.0.0 02/06/2015 [ 267.811666] RIP: 0010:native_write_cr4+0x4/0x10 [ 267.812727] RSP: 0018:8c01ffd83f48 EFLAGS: 00010006 [ 267.813960] RAX: 003626e0 RBX: 0046 RCX: 8c01ffd8 [ 267.815582] RDX: 8c01ffd94020 RSI: 8c01ffda5040 RDI: 003606e0 [ 267.817095] RBP: 8c01ffd83f48 R08: 00478079a547 R09: [ 267.818625] R10: R11: R12: 00025040 [ 267.820130] R13: 0001 R14: R15: [ 267.821638] FS: () GS:8c01ffd8() knlGS: [ 267.823352] CS: 0010 DS: ES: CR0: 80050033 [ 267.824592] CR2: CR3: 00058c00a006 CR4: 003626e0 [ 267.826108] DR0: DR1: DR2: [ 267.827567] DR3: DR6: fffe0ff0 DR7: 0400 [ 267.828973] Call Trace: [ 267.829470] [ 267.829893] hardware_disable+0xaa/0xc0 [kvm_intel] [ 267.830897] kvm_arch_hardware_disable+0x19/0x40 [kvm] [ 267.831928] hardware_disable_nolock+0x2b/0x30 [kvm] [ 267.832912] flush_smp_call_function_queue+0x4c/0xf0 [ 267.833911] generic_smp_call_function_single_interrupt+0x13/0x30 [ 267.835121] smp_call_function_interrupt+0x36/0xd0 [ 267.836069] call_function_interrupt+0x84/0x90 [ 267.836950] [ 267.837396] RIP: 0010:native_safe_halt+0x6/0x10 [ 267.838272] RSP: 0018:a2e1431afe80 EFLAGS: 0246 ORIG_RAX: ff03 [ 267.839698] RAX: acd97150 RBX: 0006 RCX: [ 267.840978] RDX: RSI: RDI: [ 267.842258] RBP: a2e1431afe80 R08: 0002 R09: [ 267.843554] R10: 00b3 R11: 00a6 R12: 0006 [ 267.844826] R13: R14: R15: [ 267.846107] ? __cpuidle_text_start+0x8/0x8 [ 267.846875] default_idle+0x20/0x100 [ 267.847533] arch_cpu_idle+0x15/0x20 [ 267.848186] default_idle_call+0x23/0x30 [ 267.848917] do_idle+0x172/0x1f0 [ 267.849516] cpu_startup_entry+0x73/0x80 [ 267.850255] start_secondary+0x1ab/0x200 [ 267.850971] secondary_startup_64+0xa5/0xb0 [ 267.851700] Code: 0f 1f 80 00 00 00 00 55 48 89 e5 0f 20 d8 5d c3 0f 1f 80 00 00 00 00 55 48 89 e5 0f 22 df 5d c3 0f 1f 80 00 00 00 00 55 48 89 e5 <0f> 22 e7 5d c3 0f 1f 80 00 00 00 00 55 48 89 e5 44 0f 20 c0> [ 267.854894] RIP: native_write_cr4+0x4/0x10 RSP: 8c01ffd83f48 [ 268.848104] invalid
[Kernel-packages] [Bug 1792045] Re: Ubuntu 18.04 external USB hard drive performance 1/10th of 16.04
** Description changed: - From both a live and an installed environment, I cannot get my external - 8TB sata hard drive (attached via USB 3) to write faster than about 10 - megabytes per second under Ubuntu 18.04. I have another that writes at - the expected full speed or close enough (100+ MBps). + From both a live and an installed 18.04 environment, I cannot get my + external 8TB sata hard drive (attached via USB 3) to write faster than + about 10 megabytes per second under Ubuntu 18.04. I have another that + writes at the expected full speed or close enough (100+ MBps). I have tried: * Changing the enclosure from the stock to a new one * Using usb-storage "quirks" options in modprobe conf files to work around any UAS incompatibilities with the bridge (many reports of the drive working at full performance when disabling UAS, no such luck for me) * Checking the disk for errors * Updating the kernel to the most recent mainline (4.18.6 at the time) * Checking UEFI settings (I'm already on the most recent revision of the firmware) * Applying all available updates * Changing USB ports * Checking dmesg for any obvious errors (dead end, I googled everything) - - Again, a different external 3TB USB 3 drive does not have any write speed issues at all, so it's not the computer (Intel NUC7PJYH). + Again, a different external 3TB USB 3 drive does not have any write + speed issues at all, so it's not the computer (Intel NUC7PJYH). However, the very same drive in both of the enclosures I have used works *perfectly* in Ubuntu 16.04 on kernel 4.15.0-34 in both a live session and installed. I am not sure what the difference is between the two LTS versions that is causing this, but unfortunately I think I've reached the end of my know-how on this. Thank you for your time, and please let me know what other information I can provide. 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: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: XFCE Date: Tue Sep 11 18:33:46 2018 InstallationDate: Installed on 2018-09-06 (4 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: - Bus 002 Device 002: ID 174c:55aa ASMedia Technology Inc. ASM1051E SATA 6Gb/s bridge, ASM1053E SATA 6Gb/s bridge, ASM1153 SATA 3Gb/s bridge - Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub - Bus 001 Device 003: ID 8087:0aaa Intel Corp. - Bus 001 Device 002: ID 1997:2433 - Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Bus 002 Device 002: ID 174c:55aa ASMedia Technology Inc. ASM1051E SATA 6Gb/s bridge, ASM1053E SATA 6Gb/s bridge, ASM1153 SATA 3Gb/s bridge + Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 001 Device 003: ID 8087:0aaa Intel Corp. + Bus 001 Device 002: ID 1997:2433 + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Intel Corporation NUC7PJYH ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + LANG=en_US.UTF-8 + SHELL=/bin/bash ProcFB: - + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic root=UUID=b40fd1a1-0de5-40bb-b598-7f4cd53daee1 ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: - 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 + 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) WifiSyslog: - + dmi.bios.date: 08/21/2018 dmi.bios.vendor: Intel Corp. dmi.bios.version: JYGLKCPX.86A.0044.2018.0821.1915 dmi.board.name: NUC7JYB dmi.board.vendor: Intel Corporation dmi.board.version: J67969-401 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrJYGLKCPX.86A.0044.2018.0821.1915:bd08/21/2018:svnIntelCorporation:pnNUC7PJYH:pvrJ67992-401:rvnIntelCorporation:rnNUC7JYB:rvrJ67969-401:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: Intel NUC dmi.product.name: NUC7PJYH dmi.product.version: J67992-401 dmi.sys.vendor: Intel Corporation -- You received this bug notification because you are a
[Kernel-packages] [Bug 1792045] Re: Ubuntu 18.04 external USB hard drive performance 1/10th of 16.04
** Summary changed: - Ubuntu 18.04 external USB performance 1/10th of 16.04 + Ubuntu 18.04 external USB hard drive performance 1/10th of 16.04 -- 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/1792045 Title: Ubuntu 18.04 external USB hard drive performance 1/10th of 16.04 Status in linux package in Ubuntu: Confirmed Bug description: From both a live and an installed 18.04 environment, I cannot get my external 8TB sata hard drive (attached via USB 3) to write faster than about 10 megabytes per second under Ubuntu 18.04. I have another that writes at the expected full speed or close enough (100+ MBps). I have tried: * Changing the enclosure from the stock to a new one * Using usb-storage "quirks" options in modprobe conf files to work around any UAS incompatibilities with the bridge (many reports of the drive working at full performance when disabling UAS, no such luck for me) * Checking the disk for errors * Updating the kernel to the most recent mainline (4.18.6 at the time) * Checking UEFI settings (I'm already on the most recent revision of the firmware) * Applying all available updates * Changing USB ports * Checking dmesg for any obvious errors (dead end, I googled everything) Again, a different external 3TB USB 3 drive does not have any write speed issues at all, so it's not the computer (Intel NUC7PJYH). However, the very same drive in both of the enclosures I have used works *perfectly* in Ubuntu 16.04 on kernel 4.15.0-34 in both a live session and installed. I am not sure what the difference is between the two LTS versions that is causing this, but unfortunately I think I've reached the end of my know-how on this. Thank you for your time, and please let me know what other information I can provide. 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: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: XFCE Date: Tue Sep 11 18:33:46 2018 InstallationDate: Installed on 2018-09-06 (4 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 002: ID 174c:55aa ASMedia Technology Inc. ASM1051E SATA 6Gb/s bridge, ASM1053E SATA 6Gb/s bridge, ASM1153 SATA 3Gb/s bridge Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0aaa Intel Corp. Bus 001 Device 002: ID 1997:2433 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Intel Corporation NUC7PJYH ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic root=UUID=b40fd1a1-0de5-40bb-b598-7f4cd53daee1 ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: 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) WifiSyslog: dmi.bios.date: 08/21/2018 dmi.bios.vendor: Intel Corp. dmi.bios.version: JYGLKCPX.86A.0044.2018.0821.1915 dmi.board.name: NUC7JYB dmi.board.vendor: Intel Corporation dmi.board.version: J67969-401 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrJYGLKCPX.86A.0044.2018.0821.1915:bd08/21/2018:svnIntelCorporation:pnNUC7PJYH:pvrJ67992-401:rvnIntelCorporation:rnNUC7JYB:rvrJ67969-401:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: Intel NUC dmi.product.name: NUC7PJYH dmi.product.version: J67992-401 dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1792045/+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 1792045] 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/1792045 Title: Ubuntu 18.04 external USB hard drive performance 1/10th of 16.04 Status in linux package in Ubuntu: Confirmed Bug description: From both a live and an installed environment, I cannot get my external 8TB sata hard drive (attached via USB 3) to write faster than about 10 megabytes per second under Ubuntu 18.04. I have another that writes at the expected full speed or close enough (100+ MBps). I have tried: * Changing the enclosure from the stock to a new one * Using usb-storage "quirks" options in modprobe conf files to work around any UAS incompatibilities with the bridge (many reports of the drive working at full performance when disabling UAS, no such luck for me) * Checking the disk for errors * Updating the kernel to the most recent mainline (4.18.6 at the time) * Checking UEFI settings (I'm already on the most recent revision of the firmware) * Applying all available updates * Changing USB ports * Checking dmesg for any obvious errors (dead end, I googled everything) Again, a different external 3TB USB 3 drive does not have any write speed issues at all, so it's not the computer (Intel NUC7PJYH). However, the very same drive in both of the enclosures I have used works *perfectly* in Ubuntu 16.04 on kernel 4.15.0-34 in both a live session and installed. I am not sure what the difference is between the two LTS versions that is causing this, but unfortunately I think I've reached the end of my know-how on this. Thank you for your time, and please let me know what other information I can provide. 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: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: XFCE Date: Tue Sep 11 18:33:46 2018 InstallationDate: Installed on 2018-09-06 (4 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 002: ID 174c:55aa ASMedia Technology Inc. ASM1051E SATA 6Gb/s bridge, ASM1053E SATA 6Gb/s bridge, ASM1153 SATA 3Gb/s bridge Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0aaa Intel Corp. Bus 001 Device 002: ID 1997:2433 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Intel Corporation NUC7PJYH ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic root=UUID=b40fd1a1-0de5-40bb-b598-7f4cd53daee1 ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: 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) WifiSyslog: dmi.bios.date: 08/21/2018 dmi.bios.vendor: Intel Corp. dmi.bios.version: JYGLKCPX.86A.0044.2018.0821.1915 dmi.board.name: NUC7JYB dmi.board.vendor: Intel Corporation dmi.board.version: J67969-401 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrJYGLKCPX.86A.0044.2018.0821.1915:bd08/21/2018:svnIntelCorporation:pnNUC7PJYH:pvrJ67992-401:rvnIntelCorporation:rnNUC7JYB:rvrJ67969-401:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: Intel NUC dmi.product.name: NUC7PJYH dmi.product.version: J67992-401 dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1792045/+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 1792045] [NEW] Ubuntu 18.04 external USB hard drive performance 1/10th of 16.04
Public bug reported: >From both a live and an installed environment, I cannot get my external 8TB sata hard drive (attached via USB 3) to write faster than about 10 megabytes per second under Ubuntu 18.04. I have another that writes at the expected full speed or close enough (100+ MBps). I have tried: * Changing the enclosure from the stock to a new one * Using usb-storage "quirks" options in modprobe conf files to work around any UAS incompatibilities with the bridge (many reports of the drive working at full performance when disabling UAS, no such luck for me) * Checking the disk for errors * Updating the kernel to the most recent mainline (4.18.6 at the time) * Checking UEFI settings (I'm already on the most recent revision of the firmware) * Applying all available updates * Changing USB ports * Checking dmesg for any obvious errors (dead end, I googled everything) Again, a different external 3TB USB 3 drive does not have any write speed issues at all, so it's not the computer (Intel NUC7PJYH). However, the very same drive in both of the enclosures I have used works *perfectly* in Ubuntu 16.04 on kernel 4.15.0-34 in both a live session and installed. I am not sure what the difference is between the two LTS versions that is causing this, but unfortunately I think I've reached the end of my know-how on this. Thank you for your time, and please let me know what other information I can provide. 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: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: XFCE Date: Tue Sep 11 18:33:46 2018 InstallationDate: Installed on 2018-09-06 (4 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 002: ID 174c:55aa ASMedia Technology Inc. ASM1051E SATA 6Gb/s bridge, ASM1053E SATA 6Gb/s bridge, ASM1153 SATA 3Gb/s bridge Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0aaa Intel Corp. Bus 001 Device 002: ID 1997:2433 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Intel Corporation NUC7PJYH ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic root=UUID=b40fd1a1-0de5-40bb-b598-7f4cd53daee1 ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: 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) WifiSyslog: dmi.bios.date: 08/21/2018 dmi.bios.vendor: Intel Corp. dmi.bios.version: JYGLKCPX.86A.0044.2018.0821.1915 dmi.board.name: NUC7JYB dmi.board.vendor: Intel Corporation dmi.board.version: J67969-401 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrJYGLKCPX.86A.0044.2018.0821.1915:bd08/21/2018:svnIntelCorporation:pnNUC7PJYH:pvrJ67992-401:rvnIntelCorporation:rnNUC7JYB:rvrJ67969-401:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: Intel NUC dmi.product.name: NUC7PJYH dmi.product.version: J67992-401 dmi.sys.vendor: Intel Corporation ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug bionic ** Attachment added: "lspci-vnvn.log" https://bugs.launchpad.net/bugs/1792045/+attachment/5187735/+files/lspci-vnvn.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1792045 Title: Ubuntu 18.04 external USB hard drive performance 1/10th of 16.04 Status in linux package in Ubuntu: Confirmed Bug description: From both a live and an installed environment, I cannot get my external 8TB sata hard drive (attached via USB 3) to write faster than about 10 megabytes per second under Ubuntu 18.04. I have another that writes at the expected full speed or close enough (100+ MBps). I have tried: * Changing the enclosure from the stock to a new one * Using usb-storage "quirks" options in modprobe conf files to work around any UAS incompatibilities with the bridge (many reports of the drive working at full performance when disabling UAS, no such luck for me) * Checking the disk for errors * Updating the kernel to the most recent mainline (4.18.6 at the time) * Checking UEFI settings
[Kernel-packages] [Bug 1792044] [NEW] update ENA driver to latest mainline version
Public bug reported: Update ENA driver to latest mainline version as of this commit: https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=0e1f4c76be241377d282e34ebea6d16ff7829747 ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Kamal Mostafa (kamalmostafa) Status: In Progress ** Affects: linux (Ubuntu Xenial) Importance: Undecided Assignee: Kamal Mostafa (kamalmostafa) Status: In Progress ** Affects: linux (Ubuntu Bionic) Importance: Undecided Assignee: Kamal Mostafa (kamalmostafa) Status: In Progress ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) ** Changed in: linux (Ubuntu Xenial) Status: New => In Progress ** Changed in: linux (Ubuntu Bionic) Status: New => 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/1792044 Title: update ENA driver to latest mainline version Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Status in linux source package in Bionic: In Progress Bug description: Update ENA driver to latest mainline version as of this commit: https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=0e1f4c76be241377d282e34ebea6d16ff7829747 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1792044/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1748565] Re: Kernel regularly logs: Bluetooth: hci0: last event is not cmd complete (0x0f)
WRT comment #46: Installing brcm/BCM20702A1-0b05-180a.hcd from winterheart had no effect on this or any other Bluetooth anomalies I've observed except eliminating the "Direct firmware load" error. WRT comment #51: in my environment this co-occurs with Bluetooth functioning "correctly", i.e. the only issue I see is this error message. (However, I am only using LE, not audio/BR/EDR.) I suspect it may be related to mixing HCI-based and D-Bus-based bluetooth control within or across applications, or to an application not properly stopping discovery before it shuts down. Or both. Issuing a "power off" "power on" sequence from bluetoothctl stops the error message. Getting from "unhealthy Bluetooth" to "working Bluetooth" may involve a power cycle, fixing multiple problems. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1748565 Title: Kernel regularly logs: Bluetooth: hci0: last event is not cmd complete (0x0f) Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Hello, dmesg: [ 3363.056494] Bluetooth: hci0: last event is not cmd complete (0x0f) Regards, -- Cristian ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-9-generic 4.15.0-9.10 ProcVersionSignature: Ubuntu 4.15.0-9.10-generic 4.15.2 Uname: Linux 4.15.0-9-generic x86_64 ApportVersion: 2.20.8-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: caravena 1811 F pulseaudio CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME Date: Fri Feb 9 20:35:29 2018 InstallationDate: Installed on 2017-10-13 (119 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-9-generic root=UUID=707d0f89-4b1d-4432-9d50-6058dc4c1ee9 ro rootflags=subvol=@ quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-9-generic N/A linux-backports-modules-4.15.0-9-generic N/A linux-firmware1.170 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P14AAJ dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: SAMSUNG_NP1234567890 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.family: ChiefRiver System dmi.product.name: 530U3C/530U4C dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1748565/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1790602] Comment bridged from LTC Bugzilla
--- Comment From mranw...@us.ibm.com 2018-09-11 17:31 EDT---
That package didn't have what I needed so I just symlink'd the -34 version to
-35 - doesn't sound like there's much change.
With that and your kernel it looks good:
user@deb3qwsp1:~$ cat /proc/version
Linux version 4.15.0-35-generic (kamal@kathleen) (gcc version 7.3.0 (Ubuntu
7.3.0-16ubuntu3)) #38 SMP Wed Sep 5 15:07:24 UTC 2018
user@deb3qwsp1:~$ cpupower monitor sleep 30
sleep took 30.02114 seconds and exited with status 0
|Idle_Stats
PKG |CORE|CPU | snoo | stop | stop | stop | stop | stop | stop | stop | stop
0| 0| 0| 0.09| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.12| 99.66
0| 0| 1| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 96.70
0| 0| 2| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 95.84
0| 0| 3| 2.54| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 96.71
0| 4| 4| 0.43| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.41| 94.66
0| 4| 5| 0.47| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 26.69| 68.68
0| 4| 6| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 95.84
0| 4| 7| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 95.84
Thanks!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1790602
Title:
Ubuntu18.04.1: cpuidle: powernv: Fix promotion from snooze if next
state disabled (performance)
Status in The Ubuntu-power-systems project:
New
Status in linux package in Ubuntu:
New
Status in linux source package in Bionic:
Fix Committed
Bug description:
== Comment: #0 - Michael Ranweiler - 2018-09-04
00:50:14 ==
The CPUs remain in snooze state on an idle system when only the
shallow states disabled resulting in increased power consumption.
The commit 78eaa10f027c ("cpuidle: powernv/pseries: Auto-promotion of snooze
to deeper idle state") introduced a timeout for the snooze idle state so that
it could be eventually be promoted to a deeper idlestate. The snooze
timeout value is static and set to the target residency of the next idle
state, which would train the cpuidle governor to pick the next idle state
eventually.
The unfortunate side-effect of this is that if the next idle state(s) is
disabled, the CPU will forever remain in snooze, despite the fact that the
system is completely idle, and other deeper idle states are available.
This patch fixes the issue by dynamically setting the snooze timeout to the
target residency of the next enabled state on the device.
Before Patch:
POWER8 : Only nap disabled.
$ cpupower monitor sleep 30
sleep took 30.01297 seconds and exited with status 0
|Idle_Stats
PKG |CORE|CPU | snoo | Nap | Fast
0| 8| 0| 96.41| 0.00| 0.00
0| 8| 1| 96.43| 0.00| 0.00
0| 8| 2| 96.47| 0.00| 0.00
0| 8| 3| 96.35| 0.00| 0.00
0| 8| 4| 96.37| 0.00| 0.00
0| 8| 5| 96.37| 0.00| 0.00
0| 8| 6| 96.47| 0.00| 0.00
0| 8| 7| 96.47| 0.00| 0.00
POWER9: Shallow states (stop0lite, stop1lite, stop2lite, stop0, stop1, stop2)
disabled:
$ cpupower monitor sleep 30
sleep took 30.05033 seconds and exited with status 0
|Idle_Stats
PKG |CORE|CPU | snoo | stop | stop | stop | stop | stop | stop | stop |
stop
0| 16| 0| 89.79| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00|
0.00
0| 16| 1| 90.12| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00|
0.00
0| 16| 2| 90.21| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00|
0.00
0| 16| 3| 90.29| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00|
0.00
After Patch:
POWER8 : Only nap disabled.
$ cpupower monitor sleep 30
sleep took 30.01200 seconds and exited with status 0
|Idle_Stats
PKG |CORE|CPU | snoo | Nap | Fast
0| 8| 0| 16.58| 0.00| 77.21
0| 8| 1| 18.42| 0.00| 75.38
0| 8| 2| 4.70| 0.00| 94.09
0| 8| 3| 17.06| 0.00| 81.73
0| 8| 4| 3.06| 0.00| 95.73
0| 8| 5| 7.00| 0.00| 96.80
0| 8| 6| 1.00| 0.00| 98.79
0| 8| 7| 5.62| 0.00| 94.17
POWER9: Shallow states (stop0lite, stop1lite, stop2lite, stop0, stop1,
stop2) disabled:
$ cpupower monitor sleep 30
sleep took 30.02110 seconds and exited with status 0
|Idle_Stats
PKG |CORE|CPU | snoo | stop | stop | stop | stop | stop | stop | stop |
stop
0| 0| 0| 0.69| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 9.39|
89.70
0| 0| 1| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.05|
93.21
0| 0| 2| 0.00| 0.00| 0.00|
[Kernel-packages] [Bug 1791959] Re: remove /boot/initrd.img-*.old-dkms files left behind
** Changed in: dkms (Ubuntu Xenial) Status: New => Invalid ** Changed in: dkms (Ubuntu Bionic) Status: New => Invalid ** Description changed: [Impact] If a dkms package is installed which has REMAKE_INITRD or the same setting has been manually configured by a user then when a kernel is removed its possible for an ".old-dkms" file to be left in /boot with no associated kernel. bug 1515513 dealt with removing initrd.img-.old-dkms files using the kernel's prerm hook, but that is only executed for the kernel version being removed: any other old-dkms file generated prior to that would not be removed by the hook, taking space in the /boot directory. Note: Filling up the /boot partition causes updates to fail. [Test Case] - As the fix for bug 1515513 is available on Xenial it is no longer possible to reproduce this by simply installing and updating kernels (dkms 2.2.0.3-2ubuntu11.3 would be required for that). In order to replicate it an old dkms file will be created by hand. + As the fix for bug 1515513 is available on Xenial and Bionic it is no longer possible to reproduce this by simply installing and updating kernels - dkms 2.2.0.3-2ubuntu11.3/xenial or 2.3-3ubuntu1/bionic would be required for that. In order to replicate it an old dkms file will be created by hand. - This assumes a new Xenial schroot. + This assumes a new Xenial/Bionic schroot. 1) create a file to work as a placeholder for the initrd.img old dkms file sudo touch /boot/initrd.img-4.0.0-0-generic.old-dkms 2) install 3 old kernels, r8168-dkms, and the current initramfs-tools + * xenial: sudo apt-get install -y linux-image-4.4.0-21-generic linux-image-4.4.0-22-generic linux-image-4.4.0-24-generic r8168-dkms initramfs-tools=0.122ubuntu8.12 + * bionic: + TBD 3) install the headers for the old kernels (forces dkms to run) + * xenial: sudo apt-get install -y linux-headers-4.4.0-21-generic linux-headers-4.4.0-22-generic linux-headers-4.4.0-24-generic + * bionic: + TBD 4) verify that there are 4 old-dkms, the manually created and one for each installed kernel ls /boot/*.old-dkms 5) install the initramfs-tools that contains this fix sudo apt-get install -y initramfs-tools 6) verify that the manually created old-dkms file was removed and that there are only 3 files now, one for each installed kernel ls /boot/*.old-dkms 7) autoremove the older kernel sudo apt-get autoremove -y 8) verify that there are now only 2 old-dkms, one for each installed kernel ls /boot/*.old-dkms [Regression Potential] Somebody out there might expect the .old-dkms file to be kept, but that seems like an odd expectation. One notices *.old-dkms files being left behind still sitting on the disk after purging the related kernel. This can cause /boot to become full, and when it gets really bad, even sudo apt-get autoremove won't fix the problem - only deleting the old-dkms files manually solves the problem. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1791959 Title: remove /boot/initrd.img-*.old-dkms files left behind Status in dkms package in Ubuntu: Invalid Status in initramfs-tools package in Ubuntu: Confirmed Status in dkms source package in Xenial: Invalid Status in initramfs-tools source package in Xenial: New Status in dkms source package in Bionic: Invalid Status in initramfs-tools source package in Bionic: New Bug description: [Impact] If a dkms package is installed which has REMAKE_INITRD or the same setting has been manually configured by a user then when a kernel is removed its possible for an ".old-dkms" file to be left in /boot with no associated kernel. bug 1515513 dealt with removing initrd.img-.old-dkms files using the kernel's prerm hook, but that is only executed for the kernel version being removed: any other old-dkms file generated prior to that would not be removed by the hook, taking space in the /boot directory. Note: Filling up the /boot partition causes updates to fail. [Test Case] As the fix for bug 1515513 is available on Xenial and Bionic it is no longer possible to reproduce this by simply installing and updating kernels - dkms 2.2.0.3-2ubuntu11.3/xenial or 2.3-3ubuntu1/bionic would be required for that. In order to replicate it an old dkms file will be created by hand. This assumes a new Xenial/Bionic schroot. 1) create a file to work as a placeholder for the initrd.img old dkms file sudo touch /boot/initrd.img-4.0.0-0-generic.old-dkms 2) install 3 old kernels, r8168-dkms, and the current initramfs-tools * xenial: sudo apt-get install -y linux-image-4.4.0-21-generic linux-image-4.4.0-22-generic linux-image-4.4.0-24-generic r8168-dkms initramfs-tools=0.122ubuntu8.12 * bionic: TBD 3) install the headers for the old kernels (forces dkms to run) *
[Kernel-packages] [Bug 1789118] Re: Fails to boot under Xen PV: BUG: unable to handle kernel paging request at edc21fd9
This patch was submitted here: https://lkml.org/lkml/2018/9/11/885 -- 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/1789118 Title: Fails to boot under Xen PV: BUG: unable to handle kernel paging request at edc21fd9 Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Bug description: After the most recent 18.04 32-bit upgrade of linux-image-generic, it now refuses to boot under Xen PV mode: . . . [0.114370] clocksource: jiffies: mask: 0x max_cycles: 0x, max_idle_ns: 764504178510 ns [0.114382] futex hash table entries: 256 (order: 2, 16384 bytes) [0.114423] pinctrl core: initialized pinctrl subsystem [0.134326] RTC time: 165:165:165, date: 165/165/65 [0.134442] NET: Registered protocol family 16 [0.134457] xen:grant_table: Grant tables using version 1 layout [0.134502] Grant table initialized [0.134544] audit: initializing netlink subsys (disabled) [0.134611] audit: type=2000 audit(1535307799.132:1): state=initialized audit_enabled=0 res=1 [0.134678] EISA bus registered [0.136019] PCI: setting up Xen PCI frontend stub [0.136073] BUG: unable to handle kernel paging request at edc21fd9 [0.136084] IP: eisa_bus_probe+0x19/0x36 [0.136089] *pdpt = 01ee6027 *pde = 29cc6067 *pte = [0.136100] Oops: [#1] SMP [0.136105] Modules linked in: [0.136111] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.15.0-33-generic #36-Ubuntu [0.136120] EIP: eisa_bus_probe+0x19/0x36 [0.136125] EFLAGS: 00010246 CPU: 0 [0.136130] EAX: edc21fd9 EBX: ECX: 01e0d000 EDX: 0200 [0.136138] ESI: c1d0d452 EDI: c1dd34a4 EBP: e9c89f24 ESP: e9c89f24 [0.136145] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: e021 [0.136154] CR0: 80050033 CR2: edc21fd9 CR3: 01e1 CR4: 00042660 [0.136166] Call Trace: [0.136173] do_one_initcall+0x49/0x174 [0.136179] ? parse_args+0x143/0x390 [0.136187] ? set_debug_rodata+0x14/0x14 [0.136193] kernel_init_freeable+0x149/0x1c5 [0.136201] ? rest_init+0xa0/0xa0 [0.136207] kernel_init+0xd/0xf0 [0.136213] ret_from_fork+0x2e/0x38 [0.14] Code: ff b8 df 43 ae c1 e8 35 1b 88 ff e8 20 12 88 ff c9 c3 3e 8d 74 26 00 55 b9 04 00 00 00 31 d2 b8 d9 ff 0f 00 89 e5 e8 35 8d 35 ff <8b> 10 81 fa 45 49 53 41 75 0a c7 05 a0 76 ed c1 01 00 00 00 e8 [0.14] EIP: eisa_bus_probe+0x19/0x36 SS:ESP: e021:e9c89f24 [0.14] CR2: edc21fd9 [0.14] ---[ end trace 8c00b3cb7d4f06ba ]--- [0.140013] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0009 This is: [0.00] Linux version 4.15.0-33-generic (buildd@lgw01-amd64-038) (gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #36-Ubuntu SMP Wed Aug 15 13:44:35 UTC 2018 (Ubuntu 4.15.0-33.36-generic 4.15.18) Switching to a 64-bit kernel allows boot to proceed. I cannot include output of the commands you request (uname, version_signature, dmesg, lspci) because the guest doesn't boot. The above kernel output is from a just-installed clean guest however. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1789118/+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 1714178] Re: Triple 4K monitor display failed (modesetting driver limited to 8192x8192)
I should have mentioned, my Hades has 32GB of RAM. With 8GB or less of RAM, the problem might persist (if I understand the mailing list posts). -- 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/1714178 Title: Triple 4K monitor display failed (modesetting driver limited to 8192x8192) Status in X.Org X server: Confirmed Status in linux package in Ubuntu: Triaged Status in mesa package in Ubuntu: Triaged Status in xorg-server package in Ubuntu: Triaged Status in linux source package in Bionic: Confirmed Status in mesa source package in Bionic: Confirmed Status in xorg-server source package in Bionic: Confirmed Bug description: Title: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) Summary: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) Steps: 1. a laptop with Built-in 4K LCD 2. Cold boot system with Dell Dock connected 3. Connect a 4K monitor to Dock 4. Connect 2nd 4K monitor to Dock 5. Go to [All Settings]=>[Displays] to have the following configuration. Resolution: 4kx2k@60Hz (one Built-in LCD + two external monitors) Mirror displays: disable Expected results: Triple monitor display should works without issues Actual results: Triple monitor display failed with Dell Dock Additional information: 1. Linux distribution: Ubuntu 16.04+modesetting, 16.04.3, and 17.04 2. Laptop: Dell Precision 5520 3. Dell Business Thunderbolt Dock - TB16 https://goo.gl/vFDjpi WORKAROUND (UBUNTU 18.04+): Log in to "Ubuntu on Wayland" instead of "Ubuntu". --- .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity DistUpgraded: Fresh install DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:591d] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:07bf] Subsystem: Dell Device [1028:07bf] InstallationDate: Installed on 2017-08-29 (2 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. Precision 5520 Package: xorg-server (not installed) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-14-generic.efi.signed root=UUID=b79ae801-0652-4785-beaf-e8387d798948 ro acpi_rev_override quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.11.0-14.20~16.04.1-generic 4.11.12 Tags: xenial ubuntu compiz-0.9 Uname: Linux 4.11.0-14-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/08/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.3 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.3:bd05/08/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.name: Precision 5520 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1714178/+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 1714178] Re: Triple 4K monitor display failed (modesetting driver limited to 8192x8192)
This just changed for me... but the hardware may matter, as I'm on Hades Canyon, using the amd gpu, not HD graphics. A few days ago I updated to the then-latest 4.19-rc2 (and wrote https://ubuntuforums.org/showthread.php?t=2400400 documenting exactly what I did). Using plain old X (no desktop) on my Hades Canyon, I now see a 16384 x 16384 limit: $ xrandr Screen 0: minimum 320 x 200, current 11520 x 2160, maximum 16384 x 16384 Three screens horizontally work. https://www.mail-archive.com/amd-gfx@lists.freedesktop.org/msg24954.html looks related. I have not yet tested on HD graphics with the new kernel. -- 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/1714178 Title: Triple 4K monitor display failed (modesetting driver limited to 8192x8192) Status in X.Org X server: Confirmed Status in linux package in Ubuntu: Triaged Status in mesa package in Ubuntu: Triaged Status in xorg-server package in Ubuntu: Triaged Status in linux source package in Bionic: Confirmed Status in mesa source package in Bionic: Confirmed Status in xorg-server source package in Bionic: Confirmed Bug description: Title: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) Summary: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) Steps: 1. a laptop with Built-in 4K LCD 2. Cold boot system with Dell Dock connected 3. Connect a 4K monitor to Dock 4. Connect 2nd 4K monitor to Dock 5. Go to [All Settings]=>[Displays] to have the following configuration. Resolution: 4kx2k@60Hz (one Built-in LCD + two external monitors) Mirror displays: disable Expected results: Triple monitor display should works without issues Actual results: Triple monitor display failed with Dell Dock Additional information: 1. Linux distribution: Ubuntu 16.04+modesetting, 16.04.3, and 17.04 2. Laptop: Dell Precision 5520 3. Dell Business Thunderbolt Dock - TB16 https://goo.gl/vFDjpi WORKAROUND (UBUNTU 18.04+): Log in to "Ubuntu on Wayland" instead of "Ubuntu". --- .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity DistUpgraded: Fresh install DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:591d] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:07bf] Subsystem: Dell Device [1028:07bf] InstallationDate: Installed on 2017-08-29 (2 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. Precision 5520 Package: xorg-server (not installed) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-14-generic.efi.signed root=UUID=b79ae801-0652-4785-beaf-e8387d798948 ro acpi_rev_override quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.11.0-14.20~16.04.1-generic 4.11.12 Tags: xenial ubuntu compiz-0.9 Uname: Linux 4.11.0-14-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/08/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.3 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.3:bd05/08/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.name: Precision 5520 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1714178/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to :
[Kernel-packages] [Bug 1788222] Re: Bugfix for handling of shadow doorbell buffer
I added all debian to a tarball to simplify the download: http://kernel.ubuntu.com/~mhcerri/gcp/lp1788222.tar.gz In order to install the test kernel, download the packages and run the following command: apt install \ ./linux-headers-4.4.0-135-generic_4.4.0-135.161+lp1788222.0_amd64.deb \ ./linux-headers-4.4.0-135_4.4.0-135.161+lp1788222.0_all.deb \ ./linux-image-4.4.0-135-generic_4.4.0-135.161+lp1788222.0_amd64.deb \ ./linux-image-extra-4.4.0-135-generic_4.4.0-135.161+lp1788222.0_amd64.deb -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1788222 Title: Bugfix for handling of shadow doorbell buffer Status in linux package in Ubuntu: Fix Committed Status in linux-gcp package in Ubuntu: Fix Released Status in linux source package in Xenial: In Progress Status in linux source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Committed Bug description: This request is to pull in the following patch for NVMe bug from https://lore.kernel.org/patchwork/patch/974880/ in the linux-gcp kernel: === This patch adds full memory barrier into nvme_dbbuf_update_and_check_event function to ensure that the shadow doorbell is written before reading EventIdx from memory. This is a critical bugfix for initial patch that added support for shadow doorbell into NVMe driver[...]. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788222/+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 1788222] Re: Bugfix for handling of shadow doorbell buffer
The fix for xenial was submitted for review: https://lists.ubuntu.com/archives/kernel-team/2018-September/095382.html And the debian packages for a test kernel are available at: http://kernel.ubuntu.com/~mhcerri/gcp/lp1788222/ -- 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/1788222 Title: Bugfix for handling of shadow doorbell buffer Status in linux package in Ubuntu: Fix Committed Status in linux-gcp package in Ubuntu: Fix Released Status in linux source package in Xenial: In Progress Status in linux source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Committed Bug description: This request is to pull in the following patch for NVMe bug from https://lore.kernel.org/patchwork/patch/974880/ in the linux-gcp kernel: === This patch adds full memory barrier into nvme_dbbuf_update_and_check_event function to ensure that the shadow doorbell is written before reading EventIdx from memory. This is a critical bugfix for initial patch that added support for shadow doorbell into NVMe driver[...]. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788222/+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 1678665] Re: mei_me 0000:00:16.0: hbm: properties response: wrong status = 1 CLIENT_NOT_FOUND
After a few weeks running the 4.15.0-33 kernel, I have seen the hbm... message twice, much less frequently than before turning off the security chip, but it's not totally gone. -- 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/1678665 Title: mei_me :00:16.0: hbm: properties response: wrong status = 1 CLIENT_NOT_FOUND Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Bug description: dmesg: [ 2089.236192] mei_me :00:16.0: hbm: properties response: wrong status = 1 CLIENT_NOT_FOUND [ 2089.236196] mei_me :00:16.0: mei_irq_read_handler ret = -71. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-14-generic 4.10.0-14.16 ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3 Uname: Linux 4.10.0-14-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: caravena 2083 F...m pulseaudio /dev/snd/controlC0: caravena 2083 F pulseaudio CurrentDesktop: GNOME Date: Sun Apr 2 16:59:22 2017 HibernationDevice: RESUME=UUID=360bd2d2-4f44-4311-86d6-4781ac81ee87 InstallationDate: Installed on 2015-07-26 (616 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150723) MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-14-generic root=UUID=4f4435ca-b877-47a5-9065-3dd624c0514e ro rootflags=subvol=@ quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.10.0-14-generic N/A linux-backports-modules-4.10.0-14-generic N/A linux-firmware 1.164 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P14AAJ dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: SAMSUNG_NP1234567890 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.name: 530U3C/530U4C dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1678665/+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 1767322] Re: "Activation of network connection failed" popup shows incessantly
My wireless connections works fine in Windows, but in Ubuntu it does't even connect and the message of error is as above: "activation of network connection failed". I am using the version 18.04.01. ** Changed in: network-manager (Ubuntu) Assignee: (unassigned) => ANDRE LUIZ DE PINHO CAVALCANTE (andreluizpinho) -- 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/1767322 Title: "Activation of network connection failed" popup shows incessantly Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: Confirmed Bug description: All network connections work normally, however the popup "Activation of network connection failed" keeps showing. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.6-2ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-lowlatency 4.15.17 Uname: Linux 4.15.0-20-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Apr 27 20:04:56 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-04-03 (24 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180402) IpRoute: default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 169.254.0.0/16 dev virbr1 scope link metric 1000 linkdown 192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.128 metric 600 192.168.100.0/24 dev virbr1 proto kernel scope link src 192.168.100.1 linkdown 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.6 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1767322/+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 1792002] 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 1792002 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1792002 Title: Wireless signal extremely weak or not detected Status in linux package in Ubuntu: Incomplete Bug description: Hi Support, I'm Linux Mint newbie started using from LM v18. I'm using HP245 series laptop with AMD A6-7310 APU & Wifi driver Realtek RTL8723BE. Currently I've migrated from Linux 18 (Sylvia) to Linux 19 (Tara) abt a month ago. I'm facing a WiFi signal problem whenever I've tried to upgrade to Kernel v4.15.0.33 or v4.15.0.34. The Wifi signal strength is either very weak & disconnects frequently or cannot be detected from very small distances (3-5 mtr). I've never had this issue till kernel v4.15.0.32 and everything was working fine and currently I had to downgrade or revert back to 4.15.0.32 again in order to receive signal to write this mail. Kindly resolve this error ASAP as I want to upgrade to the latest version. Regards, Joseph To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1792002/+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 1791663] Re: linux: 4.18.0-8.9 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => Fix Released ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: derivatives: bug 1791664 (linux-azure) kernel-phase:Uploaded kernel-phase-changed:Tuesday, 11. September 2018 16:02 UTC -- swm properties -- + backports: null + derivatives: null phase: Uploaded - backports: - derivatives: - backports: - derivatives: -- 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/1791663 Title: linux: 4.18.0-8.9 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Cosmic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: derivatives: bug 1791664 (linux-azure) kernel-phase:Uploaded kernel-phase-changed:Tuesday, 11. September 2018 16:02 UTC -- swm properties -- backports: null derivatives: null phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1791663/+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 1791663] Re: linux: 4.18.0-8.9 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: Fix Released => Confirmed ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: derivatives: bug 1791664 (linux-azure) kernel-phase:Uploaded kernel-phase-changed:Tuesday, 11. September 2018 16:02 UTC -- swm properties -- phase: Uploaded + backports: + derivatives: ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: derivatives: bug 1791664 (linux-azure) kernel-phase:Uploaded kernel-phase-changed:Tuesday, 11. September 2018 16:02 UTC -- swm properties -- phase: Uploaded backports: derivatives: + backports: + derivatives: -- 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/1791663 Title: linux: 4.18.0-8.9 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Cosmic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: derivatives: bug 1791664 (linux-azure) kernel-phase:Uploaded kernel-phase-changed:Tuesday, 11. September 2018 16:02 UTC -- swm properties -- backports: null derivatives: null phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1791663/+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 1791806] Re: alsa does not detech headphone output on Clevo P651RS laptop
** Description changed: Even though there is a duplex S/Pdif + Headphones out output the following line is observed: [ 13.617774] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC898: line_outs=1 (0x17/0x0/0x0/0x0/0x0) type:line [ 13.617776] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=1 (0x14/0x0/0x0/0x0/0x0) [ 13.617778] snd_hda_codec_realtek hdaudioC0D0:hp_outs=0 (0x0/0x0/0x0/0x0/0x0) [ 13.617779] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0 [ 13.617780] snd_hda_codec_realtek hdaudioC0D0:dig-out=0x1e/0x0 [ 13.617781] snd_hda_codec_realtek hdaudioC0D0:inputs: [ 13.617782] snd_hda_codec_realtek hdaudioC0D0: Mic=0x18 [ 13.617783] snd_hda_codec_realtek hdaudioC0D0: Internal Mic=0x12 [ 13.632784] input: HDA Intel PCH Mic as /devices/pci:00/:00:1f.3/sound/card0/input19 [ 13.632851] input: HDA Intel PCH Line Out as /devices/pci:00/:00:1f.3/sound/card0/input20 [ 13.632905] input: HDA Intel PCH HDMI/DP,pcm=3 as /devices/pci:00/:00:1f.3/sound/card0/input21 [ 13.632953] input: HDA Intel PCH HDMI/DP,pcm=7 as /devices/pci:00/:00:1f.3/sound/card0/input22 [ 13.632989] input: HDA Intel PCH HDMI/DP,pcm=8 as /devices/pci:00/:00:1f.3/sound/card0/input23 [ 13.633108] input: HDA Intel PCH HDMI/DP,pcm=9 as /devices/pci:00/:00:1f.3/sound/card0/input24 [ 13.633291] input: HDA Intel PCH HDMI/DP,pcm=10 as /devices/pci:00/:00:1f.3/sound/card0/input25 - --- + --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: lehel 1673 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: lehel 1673 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=14306ed9-327a-44fd-8c4d-2eba92aa55c0 InstallationDate: Installed on 2017-04-30 (499 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: Notebook P65_67RSRP Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-34-lowlatency root=/dev/mapper/xubuntu--vg-root ro noquiet nosplash i915.modeset=1 acpi_osi=! "acpi_osi=Windows 2009" ProcVersionSignature: Ubuntu 4.15.0-34.37-lowlatency 4.15.18 RelatedPackageVersions: - linux-restricted-modules-4.15.0-34-lowlatency N/A - linux-backports-modules-4.15.0-34-lowlatency N/A - linux-firmware1.173.1 + linux-restricted-modules-4.15.0-34-lowlatency N/A + linux-backports-modules-4.15.0-34-lowlatency N/A + linux-firmware1.173.1 Tags: bionic Uname: Linux 4.15.0-34-lowlatency x86_64 UpgradeStatus: Upgraded to bionic on 2018-08-23 (18 days ago) UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/14/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.04 dmi.board.asset.tag: Tag 12345 dmi.board.name: P65_67RSRP dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.04:bd09/14/2016:svnNotebook:pnP65_67RSRP:pvrNotApplicable:rvnNotebook:rnP65_67RSRP:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: P65_67RSRP dmi.product.version: Not Applicable dmi.sys.vendor: Notebook ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1791806 Title: alsa does not detech headphone output on Clevo P651RS laptop Status in linux package in Ubuntu: Confirmed Bug description: Even though there is a duplex S/Pdif + Headphones out output the following line is observed: [ 13.617774] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC898: line_outs=1 (0x17/0x0/0x0/0x0/0x0) type:line [ 13.617776] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=1 (0x14/0x0/0x0/0x0/0x0) [ 13.617778] snd_hda_codec_realtek hdaudioC0D0:hp_outs=0 (0x0/0x0/0x0/0x0/0x0) [ 13.617779] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0 [ 13.617780] snd_hda_codec_realtek hdaudioC0D0:dig-out=0x1e/0x0 [ 13.617781] snd_hda_codec_realtek hdaudioC0D0:inputs: [ 13.617782] snd_hda_codec_realtek hdaudioC0D0: Mic=0x18 [ 13.617783] snd_hda_codec_realtek hdaudioC0D0: Internal Mic=0x12 [ 13.632784] input: HDA Intel PCH Mic as /devices/pci:00/:00:1f.3/sound/card0/input19 [ 13.632851] input: HDA Intel PCH Line Out as /devices/pci:00/:00:1f.3/sound/card0/input20 [ 13.632905] input: HDA Intel PCH
[Kernel-packages] [Bug 1792002] [NEW] Wireless signal extremely weak or not detected
Public bug reported: Hi Support, I'm Linux Mint newbie started using from LM v18. I'm using HP245 series laptop with AMD A6-7310 APU & Wifi driver Realtek RTL8723BE. Currently I've migrated from Linux 18 (Sylvia) to Linux 19 (Tara) abt a month ago. I'm facing a WiFi signal problem whenever I've tried to upgrade to Kernel v4.15.0.33 or v4.15.0.34. The Wifi signal strength is either very weak & disconnects frequently or cannot be detected from very small distances (3-5 mtr). I've never had this issue till kernel v4.15.0.32 and everything was working fine and currently I had to downgrade or revert back to 4.15.0.32 again in order to receive signal to write this mail. Kindly resolve this error ASAP as I want to upgrade to the latest version. Regards, Joseph ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1792002 Title: Wireless signal extremely weak or not detected Status in linux package in Ubuntu: New Bug description: Hi Support, I'm Linux Mint newbie started using from LM v18. I'm using HP245 series laptop with AMD A6-7310 APU & Wifi driver Realtek RTL8723BE. Currently I've migrated from Linux 18 (Sylvia) to Linux 19 (Tara) abt a month ago. I'm facing a WiFi signal problem whenever I've tried to upgrade to Kernel v4.15.0.33 or v4.15.0.34. The Wifi signal strength is either very weak & disconnects frequently or cannot be detected from very small distances (3-5 mtr). I've never had this issue till kernel v4.15.0.32 and everything was working fine and currently I had to downgrade or revert back to 4.15.0.32 again in order to receive signal to write this mail. Kindly resolve this error ASAP as I want to upgrade to the latest version. Regards, Joseph To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1792002/+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 1791321] Re: No video on laptop display after suspend/resume
Yes, the test kernel you uploaded works fine. Thanks. I wish I understood more of what was behind that bad commit and the previous ones it referenced, since there appears to have been a series of fixes/reversions already, with each one apparently causing new problems on some other system: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=c3a696b6e8f8 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=662591461c4b https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=3cd091a77393 -- 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/1791321 Title: No video on laptop display after suspend/resume Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Bug description: Between linux 4.15.0-23 and 4.15.0-24, suspend/resume stopped working correctly. After resume, the laptop panel remains blank with -24 (external monitors resume correctly). Suspend/resume worked correctly with -23. Ubuntu 18.04 LTS Lenovo P50 laptop, using nouveau driver --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: john 1100 F pulseaudio /dev/snd/controlC0: john 1100 F pulseaudio DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=1114cee9-db59-4a6e-a257-06ed1131a72b InstallationDate: Installed on 2017-02-01 (586 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: LENOVO 20EN001AUS Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic root=UUID=cd371ad3-bcc5-4389-b0b7-910bd49727c5 ro quiet ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-23-generic N/A linux-backports-modules-4.15.0-23-generic N/A linux-firmware 1.173.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux 4.15.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark _MarkForUpload: True dmi.bios.date: 03/28/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N1EET77W (1.50 ) dmi.board.asset.tag: Not Available dmi.board.name: 20EN001AUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1EET77W(1.50):bd03/28/2018:svnLENOVO:pn20EN001AUS:pvrThinkPadP50:rvnLENOVO:rn20EN001AUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P50 dmi.product.name: 20EN001AUS dmi.product.version: ThinkPad P50 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791321/+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 1791806] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1791806/+attachment/5187672/+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/1791806 Title: alsa does not detech headphone output on Clevo P651RS laptop Status in linux package in Ubuntu: Incomplete Bug description: Even though there is a duplex S/Pdif + Headphones out output the following line is observed: [ 13.617774] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC898: line_outs=1 (0x17/0x0/0x0/0x0/0x0) type:line [ 13.617776] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=1 (0x14/0x0/0x0/0x0/0x0) [ 13.617778] snd_hda_codec_realtek hdaudioC0D0:hp_outs=0 (0x0/0x0/0x0/0x0/0x0) [ 13.617779] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0 [ 13.617780] snd_hda_codec_realtek hdaudioC0D0:dig-out=0x1e/0x0 [ 13.617781] snd_hda_codec_realtek hdaudioC0D0:inputs: [ 13.617782] snd_hda_codec_realtek hdaudioC0D0: Mic=0x18 [ 13.617783] snd_hda_codec_realtek hdaudioC0D0: Internal Mic=0x12 [ 13.632784] input: HDA Intel PCH Mic as /devices/pci:00/:00:1f.3/sound/card0/input19 [ 13.632851] input: HDA Intel PCH Line Out as /devices/pci:00/:00:1f.3/sound/card0/input20 [ 13.632905] input: HDA Intel PCH HDMI/DP,pcm=3 as /devices/pci:00/:00:1f.3/sound/card0/input21 [ 13.632953] input: HDA Intel PCH HDMI/DP,pcm=7 as /devices/pci:00/:00:1f.3/sound/card0/input22 [ 13.632989] input: HDA Intel PCH HDMI/DP,pcm=8 as /devices/pci:00/:00:1f.3/sound/card0/input23 [ 13.633108] input: HDA Intel PCH HDMI/DP,pcm=9 as /devices/pci:00/:00:1f.3/sound/card0/input24 [ 13.633291] input: HDA Intel PCH HDMI/DP,pcm=10 as /devices/pci:00/:00:1f.3/sound/card0/input25 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lehel 1673 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=14306ed9-327a-44fd-8c4d-2eba92aa55c0 InstallationDate: Installed on 2017-04-30 (499 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: Notebook P65_67RSRP Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-34-lowlatency root=/dev/mapper/xubuntu--vg-root ro noquiet nosplash i915.modeset=1 acpi_osi=! "acpi_osi=Windows 2009" ProcVersionSignature: Ubuntu 4.15.0-34.37-lowlatency 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-34-lowlatency N/A linux-backports-modules-4.15.0-34-lowlatency N/A linux-firmware1.173.1 Tags: bionic Uname: Linux 4.15.0-34-lowlatency x86_64 UpgradeStatus: Upgraded to bionic on 2018-08-23 (18 days ago) UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/14/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.04 dmi.board.asset.tag: Tag 12345 dmi.board.name: P65_67RSRP dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.04:bd09/14/2016:svnNotebook:pnP65_67RSRP:pvrNotApplicable:rvnNotebook:rnP65_67RSRP:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: P65_67RSRP dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791806/+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 1790125] Comment bridged from LTC Bugzilla
--- Comment From frederic.bar...@fr.ibm.com 2018-09-11 12:57 EDT--- I've tested the ocxl driver found in proposed ( 4.18.0-7-generic ) and things look good. Thanks! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1790125 Title: Ubuntu18.10 - Bring ocxl driver in 18.10 to same level as 18.04.1 Status in The Ubuntu-power-systems project: Fix Committed Status in linux package in Ubuntu: Fix Committed Status in linux source package in Cosmic: Fix Committed Bug description: == Comment: #0 - Frederic Barrat - 2018-08-31 02:41:58 == ---Problem Description--- bring ocxl driver in 18.10 to same level as in 18.04.1 ---uname output--- Linux zaiuslp14 4.15.0-24-generic #26-Ubuntu SMP Wed Jun 13 08:43:33 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux ---Additional Hardware Info--- opencapi adapter needed to use ocxl driver Machine Type = power9 ---Debugger--- A debugger is not configured ---Steps to Reproduce--- Contact Information = frederic.bar...@fr.ibm.com Stack trace output: no Oops output: no System Dump Info: The system is not configured to capture a system dump. *Additional Instructions for frederic.bar...@fr.ibm.com: -Attach sysctl -a output output to the bug. == Comment: #1 - Frederic Barrat - 2018-08-31 02:48:24 == An important fix for the ocxl driver (opencapi driver for POWER9) is missing in kernel 4.18. It was merged during the 4.19 merge window. The fix is already in 18.04.1, so it needs to be added to the 18.10 kernel to avoid regression. The commit ID is: d497ebf5fb3a026c0817f8c96cde578787f24093 ocxl: Fix page fault handler in case of fault on dying process Could you add it to the kernel for 18.10? Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1790125/+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 1791806] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1791806/+attachment/5187673/+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/1791806 Title: alsa does not detech headphone output on Clevo P651RS laptop Status in linux package in Ubuntu: Incomplete Bug description: Even though there is a duplex S/Pdif + Headphones out output the following line is observed: [ 13.617774] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC898: line_outs=1 (0x17/0x0/0x0/0x0/0x0) type:line [ 13.617776] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=1 (0x14/0x0/0x0/0x0/0x0) [ 13.617778] snd_hda_codec_realtek hdaudioC0D0:hp_outs=0 (0x0/0x0/0x0/0x0/0x0) [ 13.617779] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0 [ 13.617780] snd_hda_codec_realtek hdaudioC0D0:dig-out=0x1e/0x0 [ 13.617781] snd_hda_codec_realtek hdaudioC0D0:inputs: [ 13.617782] snd_hda_codec_realtek hdaudioC0D0: Mic=0x18 [ 13.617783] snd_hda_codec_realtek hdaudioC0D0: Internal Mic=0x12 [ 13.632784] input: HDA Intel PCH Mic as /devices/pci:00/:00:1f.3/sound/card0/input19 [ 13.632851] input: HDA Intel PCH Line Out as /devices/pci:00/:00:1f.3/sound/card0/input20 [ 13.632905] input: HDA Intel PCH HDMI/DP,pcm=3 as /devices/pci:00/:00:1f.3/sound/card0/input21 [ 13.632953] input: HDA Intel PCH HDMI/DP,pcm=7 as /devices/pci:00/:00:1f.3/sound/card0/input22 [ 13.632989] input: HDA Intel PCH HDMI/DP,pcm=8 as /devices/pci:00/:00:1f.3/sound/card0/input23 [ 13.633108] input: HDA Intel PCH HDMI/DP,pcm=9 as /devices/pci:00/:00:1f.3/sound/card0/input24 [ 13.633291] input: HDA Intel PCH HDMI/DP,pcm=10 as /devices/pci:00/:00:1f.3/sound/card0/input25 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lehel 1673 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=14306ed9-327a-44fd-8c4d-2eba92aa55c0 InstallationDate: Installed on 2017-04-30 (499 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: Notebook P65_67RSRP Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-34-lowlatency root=/dev/mapper/xubuntu--vg-root ro noquiet nosplash i915.modeset=1 acpi_osi=! "acpi_osi=Windows 2009" ProcVersionSignature: Ubuntu 4.15.0-34.37-lowlatency 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-34-lowlatency N/A linux-backports-modules-4.15.0-34-lowlatency N/A linux-firmware1.173.1 Tags: bionic Uname: Linux 4.15.0-34-lowlatency x86_64 UpgradeStatus: Upgraded to bionic on 2018-08-23 (18 days ago) UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/14/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.04 dmi.board.asset.tag: Tag 12345 dmi.board.name: P65_67RSRP dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.04:bd09/14/2016:svnNotebook:pnP65_67RSRP:pvrNotApplicable:rvnNotebook:rnP65_67RSRP:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: P65_67RSRP dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791806/+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 1791806] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1791806/+attachment/5187667/+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/1791806 Title: alsa does not detech headphone output on Clevo P651RS laptop Status in linux package in Ubuntu: Incomplete Bug description: Even though there is a duplex S/Pdif + Headphones out output the following line is observed: [ 13.617774] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC898: line_outs=1 (0x17/0x0/0x0/0x0/0x0) type:line [ 13.617776] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=1 (0x14/0x0/0x0/0x0/0x0) [ 13.617778] snd_hda_codec_realtek hdaudioC0D0:hp_outs=0 (0x0/0x0/0x0/0x0/0x0) [ 13.617779] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0 [ 13.617780] snd_hda_codec_realtek hdaudioC0D0:dig-out=0x1e/0x0 [ 13.617781] snd_hda_codec_realtek hdaudioC0D0:inputs: [ 13.617782] snd_hda_codec_realtek hdaudioC0D0: Mic=0x18 [ 13.617783] snd_hda_codec_realtek hdaudioC0D0: Internal Mic=0x12 [ 13.632784] input: HDA Intel PCH Mic as /devices/pci:00/:00:1f.3/sound/card0/input19 [ 13.632851] input: HDA Intel PCH Line Out as /devices/pci:00/:00:1f.3/sound/card0/input20 [ 13.632905] input: HDA Intel PCH HDMI/DP,pcm=3 as /devices/pci:00/:00:1f.3/sound/card0/input21 [ 13.632953] input: HDA Intel PCH HDMI/DP,pcm=7 as /devices/pci:00/:00:1f.3/sound/card0/input22 [ 13.632989] input: HDA Intel PCH HDMI/DP,pcm=8 as /devices/pci:00/:00:1f.3/sound/card0/input23 [ 13.633108] input: HDA Intel PCH HDMI/DP,pcm=9 as /devices/pci:00/:00:1f.3/sound/card0/input24 [ 13.633291] input: HDA Intel PCH HDMI/DP,pcm=10 as /devices/pci:00/:00:1f.3/sound/card0/input25 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lehel 1673 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=14306ed9-327a-44fd-8c4d-2eba92aa55c0 InstallationDate: Installed on 2017-04-30 (499 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: Notebook P65_67RSRP Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-34-lowlatency root=/dev/mapper/xubuntu--vg-root ro noquiet nosplash i915.modeset=1 acpi_osi=! "acpi_osi=Windows 2009" ProcVersionSignature: Ubuntu 4.15.0-34.37-lowlatency 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-34-lowlatency N/A linux-backports-modules-4.15.0-34-lowlatency N/A linux-firmware1.173.1 Tags: bionic Uname: Linux 4.15.0-34-lowlatency x86_64 UpgradeStatus: Upgraded to bionic on 2018-08-23 (18 days ago) UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/14/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.04 dmi.board.asset.tag: Tag 12345 dmi.board.name: P65_67RSRP dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.04:bd09/14/2016:svnNotebook:pnP65_67RSRP:pvrNotApplicable:rvnNotebook:rnP65_67RSRP:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: P65_67RSRP dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791806/+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 1791806] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1791806/+attachment/5187662/+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/1791806 Title: alsa does not detech headphone output on Clevo P651RS laptop Status in linux package in Ubuntu: Incomplete Bug description: Even though there is a duplex S/Pdif + Headphones out output the following line is observed: [ 13.617774] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC898: line_outs=1 (0x17/0x0/0x0/0x0/0x0) type:line [ 13.617776] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=1 (0x14/0x0/0x0/0x0/0x0) [ 13.617778] snd_hda_codec_realtek hdaudioC0D0:hp_outs=0 (0x0/0x0/0x0/0x0/0x0) [ 13.617779] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0 [ 13.617780] snd_hda_codec_realtek hdaudioC0D0:dig-out=0x1e/0x0 [ 13.617781] snd_hda_codec_realtek hdaudioC0D0:inputs: [ 13.617782] snd_hda_codec_realtek hdaudioC0D0: Mic=0x18 [ 13.617783] snd_hda_codec_realtek hdaudioC0D0: Internal Mic=0x12 [ 13.632784] input: HDA Intel PCH Mic as /devices/pci:00/:00:1f.3/sound/card0/input19 [ 13.632851] input: HDA Intel PCH Line Out as /devices/pci:00/:00:1f.3/sound/card0/input20 [ 13.632905] input: HDA Intel PCH HDMI/DP,pcm=3 as /devices/pci:00/:00:1f.3/sound/card0/input21 [ 13.632953] input: HDA Intel PCH HDMI/DP,pcm=7 as /devices/pci:00/:00:1f.3/sound/card0/input22 [ 13.632989] input: HDA Intel PCH HDMI/DP,pcm=8 as /devices/pci:00/:00:1f.3/sound/card0/input23 [ 13.633108] input: HDA Intel PCH HDMI/DP,pcm=9 as /devices/pci:00/:00:1f.3/sound/card0/input24 [ 13.633291] input: HDA Intel PCH HDMI/DP,pcm=10 as /devices/pci:00/:00:1f.3/sound/card0/input25 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lehel 1673 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=14306ed9-327a-44fd-8c4d-2eba92aa55c0 InstallationDate: Installed on 2017-04-30 (499 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: Notebook P65_67RSRP Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-34-lowlatency root=/dev/mapper/xubuntu--vg-root ro noquiet nosplash i915.modeset=1 acpi_osi=! "acpi_osi=Windows 2009" ProcVersionSignature: Ubuntu 4.15.0-34.37-lowlatency 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-34-lowlatency N/A linux-backports-modules-4.15.0-34-lowlatency N/A linux-firmware1.173.1 Tags: bionic Uname: Linux 4.15.0-34-lowlatency x86_64 UpgradeStatus: Upgraded to bionic on 2018-08-23 (18 days ago) UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/14/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.04 dmi.board.asset.tag: Tag 12345 dmi.board.name: P65_67RSRP dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.04:bd09/14/2016:svnNotebook:pnP65_67RSRP:pvrNotApplicable:rvnNotebook:rnP65_67RSRP:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: P65_67RSRP dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791806/+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 1791806] Re: alsa does not detech headphone output on Clevo P651RS laptop
apport information ** Tags added: apport-collected bionic ** Description changed: Even though there is a duplex S/Pdif + Headphones out output the following line is observed: [ 13.617774] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC898: line_outs=1 (0x17/0x0/0x0/0x0/0x0) type:line [ 13.617776] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=1 (0x14/0x0/0x0/0x0/0x0) [ 13.617778] snd_hda_codec_realtek hdaudioC0D0:hp_outs=0 (0x0/0x0/0x0/0x0/0x0) [ 13.617779] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0 [ 13.617780] snd_hda_codec_realtek hdaudioC0D0:dig-out=0x1e/0x0 [ 13.617781] snd_hda_codec_realtek hdaudioC0D0:inputs: [ 13.617782] snd_hda_codec_realtek hdaudioC0D0: Mic=0x18 [ 13.617783] snd_hda_codec_realtek hdaudioC0D0: Internal Mic=0x12 [ 13.632784] input: HDA Intel PCH Mic as /devices/pci:00/:00:1f.3/sound/card0/input19 [ 13.632851] input: HDA Intel PCH Line Out as /devices/pci:00/:00:1f.3/sound/card0/input20 [ 13.632905] input: HDA Intel PCH HDMI/DP,pcm=3 as /devices/pci:00/:00:1f.3/sound/card0/input21 [ 13.632953] input: HDA Intel PCH HDMI/DP,pcm=7 as /devices/pci:00/:00:1f.3/sound/card0/input22 [ 13.632989] input: HDA Intel PCH HDMI/DP,pcm=8 as /devices/pci:00/:00:1f.3/sound/card0/input23 [ 13.633108] input: HDA Intel PCH HDMI/DP,pcm=9 as /devices/pci:00/:00:1f.3/sound/card0/input24 [ 13.633291] input: HDA Intel PCH HDMI/DP,pcm=10 as /devices/pci:00/:00:1f.3/sound/card0/input25 + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.3 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: lehel 1673 F pulseaudio + CurrentDesktop: XFCE + DistroRelease: Ubuntu 18.04 + HibernationDevice: RESUME=UUID=14306ed9-327a-44fd-8c4d-2eba92aa55c0 + InstallationDate: Installed on 2017-04-30 (499 days ago) + InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) + MachineType: Notebook P65_67RSRP + Package: linux (not installed) + ProcFB: 0 inteldrmfb + ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-34-lowlatency root=/dev/mapper/xubuntu--vg-root ro noquiet nosplash i915.modeset=1 acpi_osi=! "acpi_osi=Windows 2009" + ProcVersionSignature: Ubuntu 4.15.0-34.37-lowlatency 4.15.18 + RelatedPackageVersions: + linux-restricted-modules-4.15.0-34-lowlatency N/A + linux-backports-modules-4.15.0-34-lowlatency N/A + linux-firmware1.173.1 + Tags: bionic + Uname: Linux 4.15.0-34-lowlatency x86_64 + UpgradeStatus: Upgraded to bionic on 2018-08-23 (18 days ago) + UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 09/14/2016 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: 1.05.04 + dmi.board.asset.tag: Tag 12345 + dmi.board.name: P65_67RSRP + dmi.board.vendor: Notebook + dmi.board.version: Not Applicable + dmi.chassis.asset.tag: No Asset Tag + dmi.chassis.type: 10 + dmi.chassis.vendor: Notebook + dmi.chassis.version: N/A + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.04:bd09/14/2016:svnNotebook:pnP65_67RSRP:pvrNotApplicable:rvnNotebook:rnP65_67RSRP:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: + dmi.product.family: Not Applicable + dmi.product.name: P65_67RSRP + dmi.product.version: Not Applicable + dmi.sys.vendor: Notebook ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1791806/+attachment/5187661/+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/1791806 Title: alsa does not detech headphone output on Clevo P651RS laptop Status in linux package in Ubuntu: Incomplete Bug description: Even though there is a duplex S/Pdif + Headphones out output the following line is observed: [ 13.617774] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC898: line_outs=1 (0x17/0x0/0x0/0x0/0x0) type:line [ 13.617776] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=1 (0x14/0x0/0x0/0x0/0x0) [ 13.617778] snd_hda_codec_realtek hdaudioC0D0:hp_outs=0 (0x0/0x0/0x0/0x0/0x0) [ 13.617779] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0 [ 13.617780] snd_hda_codec_realtek hdaudioC0D0:dig-out=0x1e/0x0 [ 13.617781] snd_hda_codec_realtek hdaudioC0D0:inputs: [ 13.617782] snd_hda_codec_realtek hdaudioC0D0: Mic=0x18 [ 13.617783] snd_hda_codec_realtek hdaudioC0D0: Internal Mic=0x12 [ 13.632784] input: HDA Intel PCH Mic as /devices/pci:00/:00:1f.3/sound/card0/input19 [ 13.632851] input: HDA Intel PCH Line Out as /devices/pci:00/:00:1f.3/sound/card0/input20 [ 13.632905] input: HDA Intel PCH HDMI/DP,pcm=3 as /devices/pci:00/:00:1f.3/sound/card0/input21 [ 13.632953] input: HDA Intel PCH HDMI/DP,pcm=7 as
[Kernel-packages] [Bug 1788222] Re: Bugfix for handling of shadow doorbell buffer
Xenial has an earlier version of the patches that have introduced the issue and it will require a custom fix. -- 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/1788222 Title: Bugfix for handling of shadow doorbell buffer Status in linux package in Ubuntu: Fix Committed Status in linux-gcp package in Ubuntu: Fix Released Status in linux source package in Xenial: In Progress Status in linux source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Committed Bug description: This request is to pull in the following patch for NVMe bug from https://lore.kernel.org/patchwork/patch/974880/ in the linux-gcp kernel: === This patch adds full memory barrier into nvme_dbbuf_update_and_check_event function to ensure that the shadow doorbell is written before reading EventIdx from memory. This is a critical bugfix for initial patch that added support for shadow doorbell into NVMe driver[...]. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788222/+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 1752961] Re: With kernel 4.13 btrfs scans for devices before all devices have been discovered
I built the next test kernel, up to the following commit:
d60dafdca4b463405e5586df923f05b10e9ac2f9
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1752961
Can you test that kernel and report back if it has the bug or not? I
will build the next test kernel based on your test results.
Thanks in advance
--
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/1752961
Title:
With kernel 4.13 btrfs scans for devices before all devices have been
discovered
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Artful:
Won't Fix
Status in linux source package in Bionic:
In Progress
Status in linux source package in Cosmic:
In Progress
Bug description:
See attached dmesg outputs for booting kernels 4.11.x (working) and
4.13.x (not working).
dmesg-4.11.0-14-good.txt shows the dmesg output when booting kernel 4.11.x.
btrfs scans for devices after all 4 (sda, sdb, sdc, sdd) of the devices have
been discovered by the kernel. The btrfs RAID1 filesystem mounts, and
everything is good.
dmesg-4.13.0-36-fail.txt shows the dmesg output when booting kernel 4.13.x.
btrfs scans for devices after only 2 (sda, sdb) of the devices have been
discovered by the kernel. The btrfs RAID1 filesystem fails to mount ("failed
to read the system array: -5"). The remaining 2 devices (sdc, sdd) are
discovered by the kernel immediately afterward. At the end of the log, I run
`btrfs device scan` and mount the filesystem manually.
Hardware:
HP ProLiant MicroServer Gen8
4x WDC WD20EFRX
---
AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code
2: ls: cannot access '/dev/snd/': No such file or directory
AplayDevices: aplay: device_list:270: no soundcards found...
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
ArecordDevices: arecord: device_list:270: no soundcards found...
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2015-10-15 (933 days ago)
InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
MachineType: HP ProLiant MicroServer Gen8
Package: linux (not installed)
ProcEnviron:
TERM=linux
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-20-generic
root=UUID=d976ab07-8377-46dd-ac6c-f5f7312a8305 ro rootflags=subvol=@
rootdelay=10
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
Tags: bionic apport-hook-error
Uname: Linux 4.15.0-20-generic x86_64
UnreportableReason: This report is about a package that is not installed.
UpgradeStatus: Upgraded to bionic on 2018-05-05 (0 days ago)
UserGroups:
_MarkForUpload: True
dmi.bios.date: 07/16/2015
dmi.bios.vendor: HP
dmi.bios.version: J06
dmi.chassis.type: 7
dmi.chassis.vendor: HP
dmi.modalias:
dmi:bvnHP:bvrJ06:bd07/16/2015:svnHP:pnProLiantMicroServerGen8:pvr:cvnHP:ct7:cvr:
dmi.product.family: ProLiant
dmi.product.name: ProLiant MicroServer Gen8
dmi.sys.vendor: HP
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752961/+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 1791321] Re: No video on laptop display after suspend/resume
I built a test kernel with a revert of commit 3cd091a773936c54344a519f7ee1379ccb620bee. The test kernel can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1791321 Can you test this kernel and see if it resolves this bug? Note about installing test kernels: • If the test kernel is prior to 4.15(Bionic) you need to install the linux-image and linux-image-extra .deb packages. • If the test kernel is 4.15(Bionic) or newer, you need to install the linux-modules, linux-modules-extra and linux-image-unsigned .deb packages. Thanks in advance! -- 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/1791321 Title: No video on laptop display after suspend/resume Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Bug description: Between linux 4.15.0-23 and 4.15.0-24, suspend/resume stopped working correctly. After resume, the laptop panel remains blank with -24 (external monitors resume correctly). Suspend/resume worked correctly with -23. Ubuntu 18.04 LTS Lenovo P50 laptop, using nouveau driver --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: john 1100 F pulseaudio /dev/snd/controlC0: john 1100 F pulseaudio DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=1114cee9-db59-4a6e-a257-06ed1131a72b InstallationDate: Installed on 2017-02-01 (586 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: LENOVO 20EN001AUS Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic root=UUID=cd371ad3-bcc5-4389-b0b7-910bd49727c5 ro quiet ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-23-generic N/A linux-backports-modules-4.15.0-23-generic N/A linux-firmware 1.173.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux 4.15.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark _MarkForUpload: True dmi.bios.date: 03/28/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N1EET77W (1.50 ) dmi.board.asset.tag: Not Available dmi.board.name: 20EN001AUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1EET77W(1.50):bd03/28/2018:svnLENOVO:pn20EN001AUS:pvrThinkPadP50:rvnLENOVO:rn20EN001AUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P50 dmi.product.name: 20EN001AUS dmi.product.version: ThinkPad P50 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791321/+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 1788222] Re: Bugfix for handling of shadow doorbell buffer
** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux-gcp (Ubuntu Xenial) Importance: Undecided Status: New ** No longer affects: linux-gcp (Ubuntu Xenial) ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Marcelo Cerri (mhcerri) ** Changed in: linux (Ubuntu Cosmic) Assignee: (unassigned) => Marcelo Cerri (mhcerri) ** Changed in: linux (Ubuntu Xenial) Assignee: (unassigned) => Marcelo Cerri (mhcerri) ** Changed in: linux (Ubuntu Xenial) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1788222 Title: Bugfix for handling of shadow doorbell buffer Status in linux package in Ubuntu: Fix Committed Status in linux-gcp package in Ubuntu: Fix Released Status in linux source package in Xenial: In Progress Status in linux source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Committed Bug description: This request is to pull in the following patch for NVMe bug from https://lore.kernel.org/patchwork/patch/974880/ in the linux-gcp kernel: === This patch adds full memory barrier into nvme_dbbuf_update_and_check_event function to ensure that the shadow doorbell is written before reading EventIdx from memory. This is a critical bugfix for initial patch that added support for shadow doorbell into NVMe driver[...]. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788222/+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 1791806] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1791806/+attachment/5187664/+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/1791806 Title: alsa does not detech headphone output on Clevo P651RS laptop Status in linux package in Ubuntu: Incomplete Bug description: Even though there is a duplex S/Pdif + Headphones out output the following line is observed: [ 13.617774] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC898: line_outs=1 (0x17/0x0/0x0/0x0/0x0) type:line [ 13.617776] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=1 (0x14/0x0/0x0/0x0/0x0) [ 13.617778] snd_hda_codec_realtek hdaudioC0D0:hp_outs=0 (0x0/0x0/0x0/0x0/0x0) [ 13.617779] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0 [ 13.617780] snd_hda_codec_realtek hdaudioC0D0:dig-out=0x1e/0x0 [ 13.617781] snd_hda_codec_realtek hdaudioC0D0:inputs: [ 13.617782] snd_hda_codec_realtek hdaudioC0D0: Mic=0x18 [ 13.617783] snd_hda_codec_realtek hdaudioC0D0: Internal Mic=0x12 [ 13.632784] input: HDA Intel PCH Mic as /devices/pci:00/:00:1f.3/sound/card0/input19 [ 13.632851] input: HDA Intel PCH Line Out as /devices/pci:00/:00:1f.3/sound/card0/input20 [ 13.632905] input: HDA Intel PCH HDMI/DP,pcm=3 as /devices/pci:00/:00:1f.3/sound/card0/input21 [ 13.632953] input: HDA Intel PCH HDMI/DP,pcm=7 as /devices/pci:00/:00:1f.3/sound/card0/input22 [ 13.632989] input: HDA Intel PCH HDMI/DP,pcm=8 as /devices/pci:00/:00:1f.3/sound/card0/input23 [ 13.633108] input: HDA Intel PCH HDMI/DP,pcm=9 as /devices/pci:00/:00:1f.3/sound/card0/input24 [ 13.633291] input: HDA Intel PCH HDMI/DP,pcm=10 as /devices/pci:00/:00:1f.3/sound/card0/input25 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lehel 1673 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=14306ed9-327a-44fd-8c4d-2eba92aa55c0 InstallationDate: Installed on 2017-04-30 (499 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: Notebook P65_67RSRP Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-34-lowlatency root=/dev/mapper/xubuntu--vg-root ro noquiet nosplash i915.modeset=1 acpi_osi=! "acpi_osi=Windows 2009" ProcVersionSignature: Ubuntu 4.15.0-34.37-lowlatency 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-34-lowlatency N/A linux-backports-modules-4.15.0-34-lowlatency N/A linux-firmware1.173.1 Tags: bionic Uname: Linux 4.15.0-34-lowlatency x86_64 UpgradeStatus: Upgraded to bionic on 2018-08-23 (18 days ago) UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/14/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.04 dmi.board.asset.tag: Tag 12345 dmi.board.name: P65_67RSRP dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.04:bd09/14/2016:svnNotebook:pnP65_67RSRP:pvrNotApplicable:rvnNotebook:rnP65_67RSRP:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: P65_67RSRP dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791806/+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 1791806] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1791806/+attachment/5187665/+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/1791806 Title: alsa does not detech headphone output on Clevo P651RS laptop Status in linux package in Ubuntu: Incomplete Bug description: Even though there is a duplex S/Pdif + Headphones out output the following line is observed: [ 13.617774] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC898: line_outs=1 (0x17/0x0/0x0/0x0/0x0) type:line [ 13.617776] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=1 (0x14/0x0/0x0/0x0/0x0) [ 13.617778] snd_hda_codec_realtek hdaudioC0D0:hp_outs=0 (0x0/0x0/0x0/0x0/0x0) [ 13.617779] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0 [ 13.617780] snd_hda_codec_realtek hdaudioC0D0:dig-out=0x1e/0x0 [ 13.617781] snd_hda_codec_realtek hdaudioC0D0:inputs: [ 13.617782] snd_hda_codec_realtek hdaudioC0D0: Mic=0x18 [ 13.617783] snd_hda_codec_realtek hdaudioC0D0: Internal Mic=0x12 [ 13.632784] input: HDA Intel PCH Mic as /devices/pci:00/:00:1f.3/sound/card0/input19 [ 13.632851] input: HDA Intel PCH Line Out as /devices/pci:00/:00:1f.3/sound/card0/input20 [ 13.632905] input: HDA Intel PCH HDMI/DP,pcm=3 as /devices/pci:00/:00:1f.3/sound/card0/input21 [ 13.632953] input: HDA Intel PCH HDMI/DP,pcm=7 as /devices/pci:00/:00:1f.3/sound/card0/input22 [ 13.632989] input: HDA Intel PCH HDMI/DP,pcm=8 as /devices/pci:00/:00:1f.3/sound/card0/input23 [ 13.633108] input: HDA Intel PCH HDMI/DP,pcm=9 as /devices/pci:00/:00:1f.3/sound/card0/input24 [ 13.633291] input: HDA Intel PCH HDMI/DP,pcm=10 as /devices/pci:00/:00:1f.3/sound/card0/input25 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lehel 1673 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=14306ed9-327a-44fd-8c4d-2eba92aa55c0 InstallationDate: Installed on 2017-04-30 (499 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: Notebook P65_67RSRP Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-34-lowlatency root=/dev/mapper/xubuntu--vg-root ro noquiet nosplash i915.modeset=1 acpi_osi=! "acpi_osi=Windows 2009" ProcVersionSignature: Ubuntu 4.15.0-34.37-lowlatency 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-34-lowlatency N/A linux-backports-modules-4.15.0-34-lowlatency N/A linux-firmware1.173.1 Tags: bionic Uname: Linux 4.15.0-34-lowlatency x86_64 UpgradeStatus: Upgraded to bionic on 2018-08-23 (18 days ago) UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/14/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.04 dmi.board.asset.tag: Tag 12345 dmi.board.name: P65_67RSRP dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.04:bd09/14/2016:svnNotebook:pnP65_67RSRP:pvrNotApplicable:rvnNotebook:rnP65_67RSRP:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: P65_67RSRP dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791806/+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 1791806] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1791806/+attachment/5187668/+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/1791806 Title: alsa does not detech headphone output on Clevo P651RS laptop Status in linux package in Ubuntu: Incomplete Bug description: Even though there is a duplex S/Pdif + Headphones out output the following line is observed: [ 13.617774] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC898: line_outs=1 (0x17/0x0/0x0/0x0/0x0) type:line [ 13.617776] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=1 (0x14/0x0/0x0/0x0/0x0) [ 13.617778] snd_hda_codec_realtek hdaudioC0D0:hp_outs=0 (0x0/0x0/0x0/0x0/0x0) [ 13.617779] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0 [ 13.617780] snd_hda_codec_realtek hdaudioC0D0:dig-out=0x1e/0x0 [ 13.617781] snd_hda_codec_realtek hdaudioC0D0:inputs: [ 13.617782] snd_hda_codec_realtek hdaudioC0D0: Mic=0x18 [ 13.617783] snd_hda_codec_realtek hdaudioC0D0: Internal Mic=0x12 [ 13.632784] input: HDA Intel PCH Mic as /devices/pci:00/:00:1f.3/sound/card0/input19 [ 13.632851] input: HDA Intel PCH Line Out as /devices/pci:00/:00:1f.3/sound/card0/input20 [ 13.632905] input: HDA Intel PCH HDMI/DP,pcm=3 as /devices/pci:00/:00:1f.3/sound/card0/input21 [ 13.632953] input: HDA Intel PCH HDMI/DP,pcm=7 as /devices/pci:00/:00:1f.3/sound/card0/input22 [ 13.632989] input: HDA Intel PCH HDMI/DP,pcm=8 as /devices/pci:00/:00:1f.3/sound/card0/input23 [ 13.633108] input: HDA Intel PCH HDMI/DP,pcm=9 as /devices/pci:00/:00:1f.3/sound/card0/input24 [ 13.633291] input: HDA Intel PCH HDMI/DP,pcm=10 as /devices/pci:00/:00:1f.3/sound/card0/input25 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lehel 1673 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=14306ed9-327a-44fd-8c4d-2eba92aa55c0 InstallationDate: Installed on 2017-04-30 (499 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: Notebook P65_67RSRP Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-34-lowlatency root=/dev/mapper/xubuntu--vg-root ro noquiet nosplash i915.modeset=1 acpi_osi=! "acpi_osi=Windows 2009" ProcVersionSignature: Ubuntu 4.15.0-34.37-lowlatency 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-34-lowlatency N/A linux-backports-modules-4.15.0-34-lowlatency N/A linux-firmware1.173.1 Tags: bionic Uname: Linux 4.15.0-34-lowlatency x86_64 UpgradeStatus: Upgraded to bionic on 2018-08-23 (18 days ago) UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/14/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.04 dmi.board.asset.tag: Tag 12345 dmi.board.name: P65_67RSRP dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.04:bd09/14/2016:svnNotebook:pnP65_67RSRP:pvrNotApplicable:rvnNotebook:rnP65_67RSRP:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: P65_67RSRP dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791806/+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 1791806] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1791806/+attachment/5187663/+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/1791806 Title: alsa does not detech headphone output on Clevo P651RS laptop Status in linux package in Ubuntu: Incomplete Bug description: Even though there is a duplex S/Pdif + Headphones out output the following line is observed: [ 13.617774] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC898: line_outs=1 (0x17/0x0/0x0/0x0/0x0) type:line [ 13.617776] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=1 (0x14/0x0/0x0/0x0/0x0) [ 13.617778] snd_hda_codec_realtek hdaudioC0D0:hp_outs=0 (0x0/0x0/0x0/0x0/0x0) [ 13.617779] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0 [ 13.617780] snd_hda_codec_realtek hdaudioC0D0:dig-out=0x1e/0x0 [ 13.617781] snd_hda_codec_realtek hdaudioC0D0:inputs: [ 13.617782] snd_hda_codec_realtek hdaudioC0D0: Mic=0x18 [ 13.617783] snd_hda_codec_realtek hdaudioC0D0: Internal Mic=0x12 [ 13.632784] input: HDA Intel PCH Mic as /devices/pci:00/:00:1f.3/sound/card0/input19 [ 13.632851] input: HDA Intel PCH Line Out as /devices/pci:00/:00:1f.3/sound/card0/input20 [ 13.632905] input: HDA Intel PCH HDMI/DP,pcm=3 as /devices/pci:00/:00:1f.3/sound/card0/input21 [ 13.632953] input: HDA Intel PCH HDMI/DP,pcm=7 as /devices/pci:00/:00:1f.3/sound/card0/input22 [ 13.632989] input: HDA Intel PCH HDMI/DP,pcm=8 as /devices/pci:00/:00:1f.3/sound/card0/input23 [ 13.633108] input: HDA Intel PCH HDMI/DP,pcm=9 as /devices/pci:00/:00:1f.3/sound/card0/input24 [ 13.633291] input: HDA Intel PCH HDMI/DP,pcm=10 as /devices/pci:00/:00:1f.3/sound/card0/input25 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lehel 1673 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=14306ed9-327a-44fd-8c4d-2eba92aa55c0 InstallationDate: Installed on 2017-04-30 (499 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: Notebook P65_67RSRP Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-34-lowlatency root=/dev/mapper/xubuntu--vg-root ro noquiet nosplash i915.modeset=1 acpi_osi=! "acpi_osi=Windows 2009" ProcVersionSignature: Ubuntu 4.15.0-34.37-lowlatency 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-34-lowlatency N/A linux-backports-modules-4.15.0-34-lowlatency N/A linux-firmware1.173.1 Tags: bionic Uname: Linux 4.15.0-34-lowlatency x86_64 UpgradeStatus: Upgraded to bionic on 2018-08-23 (18 days ago) UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/14/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.04 dmi.board.asset.tag: Tag 12345 dmi.board.name: P65_67RSRP dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.04:bd09/14/2016:svnNotebook:pnP65_67RSRP:pvrNotApplicable:rvnNotebook:rnP65_67RSRP:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: P65_67RSRP dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791806/+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 1791806] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1791806/+attachment/5187671/+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/1791806 Title: alsa does not detech headphone output on Clevo P651RS laptop Status in linux package in Ubuntu: Incomplete Bug description: Even though there is a duplex S/Pdif + Headphones out output the following line is observed: [ 13.617774] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC898: line_outs=1 (0x17/0x0/0x0/0x0/0x0) type:line [ 13.617776] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=1 (0x14/0x0/0x0/0x0/0x0) [ 13.617778] snd_hda_codec_realtek hdaudioC0D0:hp_outs=0 (0x0/0x0/0x0/0x0/0x0) [ 13.617779] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0 [ 13.617780] snd_hda_codec_realtek hdaudioC0D0:dig-out=0x1e/0x0 [ 13.617781] snd_hda_codec_realtek hdaudioC0D0:inputs: [ 13.617782] snd_hda_codec_realtek hdaudioC0D0: Mic=0x18 [ 13.617783] snd_hda_codec_realtek hdaudioC0D0: Internal Mic=0x12 [ 13.632784] input: HDA Intel PCH Mic as /devices/pci:00/:00:1f.3/sound/card0/input19 [ 13.632851] input: HDA Intel PCH Line Out as /devices/pci:00/:00:1f.3/sound/card0/input20 [ 13.632905] input: HDA Intel PCH HDMI/DP,pcm=3 as /devices/pci:00/:00:1f.3/sound/card0/input21 [ 13.632953] input: HDA Intel PCH HDMI/DP,pcm=7 as /devices/pci:00/:00:1f.3/sound/card0/input22 [ 13.632989] input: HDA Intel PCH HDMI/DP,pcm=8 as /devices/pci:00/:00:1f.3/sound/card0/input23 [ 13.633108] input: HDA Intel PCH HDMI/DP,pcm=9 as /devices/pci:00/:00:1f.3/sound/card0/input24 [ 13.633291] input: HDA Intel PCH HDMI/DP,pcm=10 as /devices/pci:00/:00:1f.3/sound/card0/input25 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lehel 1673 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=14306ed9-327a-44fd-8c4d-2eba92aa55c0 InstallationDate: Installed on 2017-04-30 (499 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: Notebook P65_67RSRP Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-34-lowlatency root=/dev/mapper/xubuntu--vg-root ro noquiet nosplash i915.modeset=1 acpi_osi=! "acpi_osi=Windows 2009" ProcVersionSignature: Ubuntu 4.15.0-34.37-lowlatency 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-34-lowlatency N/A linux-backports-modules-4.15.0-34-lowlatency N/A linux-firmware1.173.1 Tags: bionic Uname: Linux 4.15.0-34-lowlatency x86_64 UpgradeStatus: Upgraded to bionic on 2018-08-23 (18 days ago) UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/14/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.04 dmi.board.asset.tag: Tag 12345 dmi.board.name: P65_67RSRP dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.04:bd09/14/2016:svnNotebook:pnP65_67RSRP:pvrNotApplicable:rvnNotebook:rnP65_67RSRP:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: P65_67RSRP dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791806/+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 1791806] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1791806/+attachment/5187675/+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/1791806 Title: alsa does not detech headphone output on Clevo P651RS laptop Status in linux package in Ubuntu: Incomplete Bug description: Even though there is a duplex S/Pdif + Headphones out output the following line is observed: [ 13.617774] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC898: line_outs=1 (0x17/0x0/0x0/0x0/0x0) type:line [ 13.617776] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=1 (0x14/0x0/0x0/0x0/0x0) [ 13.617778] snd_hda_codec_realtek hdaudioC0D0:hp_outs=0 (0x0/0x0/0x0/0x0/0x0) [ 13.617779] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0 [ 13.617780] snd_hda_codec_realtek hdaudioC0D0:dig-out=0x1e/0x0 [ 13.617781] snd_hda_codec_realtek hdaudioC0D0:inputs: [ 13.617782] snd_hda_codec_realtek hdaudioC0D0: Mic=0x18 [ 13.617783] snd_hda_codec_realtek hdaudioC0D0: Internal Mic=0x12 [ 13.632784] input: HDA Intel PCH Mic as /devices/pci:00/:00:1f.3/sound/card0/input19 [ 13.632851] input: HDA Intel PCH Line Out as /devices/pci:00/:00:1f.3/sound/card0/input20 [ 13.632905] input: HDA Intel PCH HDMI/DP,pcm=3 as /devices/pci:00/:00:1f.3/sound/card0/input21 [ 13.632953] input: HDA Intel PCH HDMI/DP,pcm=7 as /devices/pci:00/:00:1f.3/sound/card0/input22 [ 13.632989] input: HDA Intel PCH HDMI/DP,pcm=8 as /devices/pci:00/:00:1f.3/sound/card0/input23 [ 13.633108] input: HDA Intel PCH HDMI/DP,pcm=9 as /devices/pci:00/:00:1f.3/sound/card0/input24 [ 13.633291] input: HDA Intel PCH HDMI/DP,pcm=10 as /devices/pci:00/:00:1f.3/sound/card0/input25 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lehel 1673 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=14306ed9-327a-44fd-8c4d-2eba92aa55c0 InstallationDate: Installed on 2017-04-30 (499 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: Notebook P65_67RSRP Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-34-lowlatency root=/dev/mapper/xubuntu--vg-root ro noquiet nosplash i915.modeset=1 acpi_osi=! "acpi_osi=Windows 2009" ProcVersionSignature: Ubuntu 4.15.0-34.37-lowlatency 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-34-lowlatency N/A linux-backports-modules-4.15.0-34-lowlatency N/A linux-firmware1.173.1 Tags: bionic Uname: Linux 4.15.0-34-lowlatency x86_64 UpgradeStatus: Upgraded to bionic on 2018-08-23 (18 days ago) UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/14/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.04 dmi.board.asset.tag: Tag 12345 dmi.board.name: P65_67RSRP dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.04:bd09/14/2016:svnNotebook:pnP65_67RSRP:pvrNotApplicable:rvnNotebook:rnP65_67RSRP:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: P65_67RSRP dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791806/+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 1791806] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1791806/+attachment/5187666/+files/Lsusb.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/1791806 Title: alsa does not detech headphone output on Clevo P651RS laptop Status in linux package in Ubuntu: Incomplete Bug description: Even though there is a duplex S/Pdif + Headphones out output the following line is observed: [ 13.617774] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC898: line_outs=1 (0x17/0x0/0x0/0x0/0x0) type:line [ 13.617776] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=1 (0x14/0x0/0x0/0x0/0x0) [ 13.617778] snd_hda_codec_realtek hdaudioC0D0:hp_outs=0 (0x0/0x0/0x0/0x0/0x0) [ 13.617779] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0 [ 13.617780] snd_hda_codec_realtek hdaudioC0D0:dig-out=0x1e/0x0 [ 13.617781] snd_hda_codec_realtek hdaudioC0D0:inputs: [ 13.617782] snd_hda_codec_realtek hdaudioC0D0: Mic=0x18 [ 13.617783] snd_hda_codec_realtek hdaudioC0D0: Internal Mic=0x12 [ 13.632784] input: HDA Intel PCH Mic as /devices/pci:00/:00:1f.3/sound/card0/input19 [ 13.632851] input: HDA Intel PCH Line Out as /devices/pci:00/:00:1f.3/sound/card0/input20 [ 13.632905] input: HDA Intel PCH HDMI/DP,pcm=3 as /devices/pci:00/:00:1f.3/sound/card0/input21 [ 13.632953] input: HDA Intel PCH HDMI/DP,pcm=7 as /devices/pci:00/:00:1f.3/sound/card0/input22 [ 13.632989] input: HDA Intel PCH HDMI/DP,pcm=8 as /devices/pci:00/:00:1f.3/sound/card0/input23 [ 13.633108] input: HDA Intel PCH HDMI/DP,pcm=9 as /devices/pci:00/:00:1f.3/sound/card0/input24 [ 13.633291] input: HDA Intel PCH HDMI/DP,pcm=10 as /devices/pci:00/:00:1f.3/sound/card0/input25 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lehel 1673 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=14306ed9-327a-44fd-8c4d-2eba92aa55c0 InstallationDate: Installed on 2017-04-30 (499 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: Notebook P65_67RSRP Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-34-lowlatency root=/dev/mapper/xubuntu--vg-root ro noquiet nosplash i915.modeset=1 acpi_osi=! "acpi_osi=Windows 2009" ProcVersionSignature: Ubuntu 4.15.0-34.37-lowlatency 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-34-lowlatency N/A linux-backports-modules-4.15.0-34-lowlatency N/A linux-firmware1.173.1 Tags: bionic Uname: Linux 4.15.0-34-lowlatency x86_64 UpgradeStatus: Upgraded to bionic on 2018-08-23 (18 days ago) UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/14/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.04 dmi.board.asset.tag: Tag 12345 dmi.board.name: P65_67RSRP dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.04:bd09/14/2016:svnNotebook:pnP65_67RSRP:pvrNotApplicable:rvnNotebook:rnP65_67RSRP:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: P65_67RSRP dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791806/+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 1791806] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1791806/+attachment/5187670/+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/1791806 Title: alsa does not detech headphone output on Clevo P651RS laptop Status in linux package in Ubuntu: Incomplete Bug description: Even though there is a duplex S/Pdif + Headphones out output the following line is observed: [ 13.617774] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC898: line_outs=1 (0x17/0x0/0x0/0x0/0x0) type:line [ 13.617776] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=1 (0x14/0x0/0x0/0x0/0x0) [ 13.617778] snd_hda_codec_realtek hdaudioC0D0:hp_outs=0 (0x0/0x0/0x0/0x0/0x0) [ 13.617779] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0 [ 13.617780] snd_hda_codec_realtek hdaudioC0D0:dig-out=0x1e/0x0 [ 13.617781] snd_hda_codec_realtek hdaudioC0D0:inputs: [ 13.617782] snd_hda_codec_realtek hdaudioC0D0: Mic=0x18 [ 13.617783] snd_hda_codec_realtek hdaudioC0D0: Internal Mic=0x12 [ 13.632784] input: HDA Intel PCH Mic as /devices/pci:00/:00:1f.3/sound/card0/input19 [ 13.632851] input: HDA Intel PCH Line Out as /devices/pci:00/:00:1f.3/sound/card0/input20 [ 13.632905] input: HDA Intel PCH HDMI/DP,pcm=3 as /devices/pci:00/:00:1f.3/sound/card0/input21 [ 13.632953] input: HDA Intel PCH HDMI/DP,pcm=7 as /devices/pci:00/:00:1f.3/sound/card0/input22 [ 13.632989] input: HDA Intel PCH HDMI/DP,pcm=8 as /devices/pci:00/:00:1f.3/sound/card0/input23 [ 13.633108] input: HDA Intel PCH HDMI/DP,pcm=9 as /devices/pci:00/:00:1f.3/sound/card0/input24 [ 13.633291] input: HDA Intel PCH HDMI/DP,pcm=10 as /devices/pci:00/:00:1f.3/sound/card0/input25 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lehel 1673 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=14306ed9-327a-44fd-8c4d-2eba92aa55c0 InstallationDate: Installed on 2017-04-30 (499 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: Notebook P65_67RSRP Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-34-lowlatency root=/dev/mapper/xubuntu--vg-root ro noquiet nosplash i915.modeset=1 acpi_osi=! "acpi_osi=Windows 2009" ProcVersionSignature: Ubuntu 4.15.0-34.37-lowlatency 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-34-lowlatency N/A linux-backports-modules-4.15.0-34-lowlatency N/A linux-firmware1.173.1 Tags: bionic Uname: Linux 4.15.0-34-lowlatency x86_64 UpgradeStatus: Upgraded to bionic on 2018-08-23 (18 days ago) UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/14/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.04 dmi.board.asset.tag: Tag 12345 dmi.board.name: P65_67RSRP dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.04:bd09/14/2016:svnNotebook:pnP65_67RSRP:pvrNotApplicable:rvnNotebook:rnP65_67RSRP:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: P65_67RSRP dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791806/+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 1791806] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1791806/+attachment/5187674/+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/1791806 Title: alsa does not detech headphone output on Clevo P651RS laptop Status in linux package in Ubuntu: Incomplete Bug description: Even though there is a duplex S/Pdif + Headphones out output the following line is observed: [ 13.617774] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC898: line_outs=1 (0x17/0x0/0x0/0x0/0x0) type:line [ 13.617776] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=1 (0x14/0x0/0x0/0x0/0x0) [ 13.617778] snd_hda_codec_realtek hdaudioC0D0:hp_outs=0 (0x0/0x0/0x0/0x0/0x0) [ 13.617779] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0 [ 13.617780] snd_hda_codec_realtek hdaudioC0D0:dig-out=0x1e/0x0 [ 13.617781] snd_hda_codec_realtek hdaudioC0D0:inputs: [ 13.617782] snd_hda_codec_realtek hdaudioC0D0: Mic=0x18 [ 13.617783] snd_hda_codec_realtek hdaudioC0D0: Internal Mic=0x12 [ 13.632784] input: HDA Intel PCH Mic as /devices/pci:00/:00:1f.3/sound/card0/input19 [ 13.632851] input: HDA Intel PCH Line Out as /devices/pci:00/:00:1f.3/sound/card0/input20 [ 13.632905] input: HDA Intel PCH HDMI/DP,pcm=3 as /devices/pci:00/:00:1f.3/sound/card0/input21 [ 13.632953] input: HDA Intel PCH HDMI/DP,pcm=7 as /devices/pci:00/:00:1f.3/sound/card0/input22 [ 13.632989] input: HDA Intel PCH HDMI/DP,pcm=8 as /devices/pci:00/:00:1f.3/sound/card0/input23 [ 13.633108] input: HDA Intel PCH HDMI/DP,pcm=9 as /devices/pci:00/:00:1f.3/sound/card0/input24 [ 13.633291] input: HDA Intel PCH HDMI/DP,pcm=10 as /devices/pci:00/:00:1f.3/sound/card0/input25 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lehel 1673 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=14306ed9-327a-44fd-8c4d-2eba92aa55c0 InstallationDate: Installed on 2017-04-30 (499 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: Notebook P65_67RSRP Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-34-lowlatency root=/dev/mapper/xubuntu--vg-root ro noquiet nosplash i915.modeset=1 acpi_osi=! "acpi_osi=Windows 2009" ProcVersionSignature: Ubuntu 4.15.0-34.37-lowlatency 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-34-lowlatency N/A linux-backports-modules-4.15.0-34-lowlatency N/A linux-firmware1.173.1 Tags: bionic Uname: Linux 4.15.0-34-lowlatency x86_64 UpgradeStatus: Upgraded to bionic on 2018-08-23 (18 days ago) UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/14/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.04 dmi.board.asset.tag: Tag 12345 dmi.board.name: P65_67RSRP dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.04:bd09/14/2016:svnNotebook:pnP65_67RSRP:pvrNotApplicable:rvnNotebook:rnP65_67RSRP:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: P65_67RSRP dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791806/+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 1791806] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1791806/+attachment/5187669/+files/ProcEnviron.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/1791806 Title: alsa does not detech headphone output on Clevo P651RS laptop Status in linux package in Ubuntu: Incomplete Bug description: Even though there is a duplex S/Pdif + Headphones out output the following line is observed: [ 13.617774] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC898: line_outs=1 (0x17/0x0/0x0/0x0/0x0) type:line [ 13.617776] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=1 (0x14/0x0/0x0/0x0/0x0) [ 13.617778] snd_hda_codec_realtek hdaudioC0D0:hp_outs=0 (0x0/0x0/0x0/0x0/0x0) [ 13.617779] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0 [ 13.617780] snd_hda_codec_realtek hdaudioC0D0:dig-out=0x1e/0x0 [ 13.617781] snd_hda_codec_realtek hdaudioC0D0:inputs: [ 13.617782] snd_hda_codec_realtek hdaudioC0D0: Mic=0x18 [ 13.617783] snd_hda_codec_realtek hdaudioC0D0: Internal Mic=0x12 [ 13.632784] input: HDA Intel PCH Mic as /devices/pci:00/:00:1f.3/sound/card0/input19 [ 13.632851] input: HDA Intel PCH Line Out as /devices/pci:00/:00:1f.3/sound/card0/input20 [ 13.632905] input: HDA Intel PCH HDMI/DP,pcm=3 as /devices/pci:00/:00:1f.3/sound/card0/input21 [ 13.632953] input: HDA Intel PCH HDMI/DP,pcm=7 as /devices/pci:00/:00:1f.3/sound/card0/input22 [ 13.632989] input: HDA Intel PCH HDMI/DP,pcm=8 as /devices/pci:00/:00:1f.3/sound/card0/input23 [ 13.633108] input: HDA Intel PCH HDMI/DP,pcm=9 as /devices/pci:00/:00:1f.3/sound/card0/input24 [ 13.633291] input: HDA Intel PCH HDMI/DP,pcm=10 as /devices/pci:00/:00:1f.3/sound/card0/input25 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lehel 1673 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=14306ed9-327a-44fd-8c4d-2eba92aa55c0 InstallationDate: Installed on 2017-04-30 (499 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: Notebook P65_67RSRP Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-34-lowlatency root=/dev/mapper/xubuntu--vg-root ro noquiet nosplash i915.modeset=1 acpi_osi=! "acpi_osi=Windows 2009" ProcVersionSignature: Ubuntu 4.15.0-34.37-lowlatency 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-34-lowlatency N/A linux-backports-modules-4.15.0-34-lowlatency N/A linux-firmware1.173.1 Tags: bionic Uname: Linux 4.15.0-34-lowlatency x86_64 UpgradeStatus: Upgraded to bionic on 2018-08-23 (18 days ago) UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/14/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.04 dmi.board.asset.tag: Tag 12345 dmi.board.name: P65_67RSRP dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.04:bd09/14/2016:svnNotebook:pnP65_67RSRP:pvrNotApplicable:rvnNotebook:rnP65_67RSRP:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: P65_67RSRP dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791806/+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 1791951] Re: nvidia-settings does not work when i install proprietary driver and reboot
** Description changed:
- -What I expected to happen:
+ - What I expected to happen:
Open nvidia-settings and switch between Intel and Nvidia graphic cards.
- -What happened instead:
+ - What happened instead:
Steps (case 1):
1. Install propetary driver.
2. Reboot and select Wayland session.
3. Open nvidia-settings --> "ERROR: Unable to find display on any available
system"
Steps (case 2)
1. sudo prime-select intel.
2. Reboot and select Wayland session.
3. Open nvidia-settings --> "ERROR: Unable to find display on any available
system"
Steps (case 3)
1. sudo prime-select nvidia.
- 1. Reboot and select X11 session.
- 2. Open nvidia-settings. --> Not ERROR.
+ 2. Reboot and select X11 session.
+ 3. Open nvidia-settings. --> Not ERROR.
- In my second test, this step generate an error:
+ In my second test, this step generate an error:
"ERROR: NVIDIA driver is not loaded
ERROR: Unable to load info from any available system"
Steps (Case 4)
1. sudo prime-select intel.
2. Reboot and select X11 session.
3. Open nvidia-settings --> "ERROR: NVIDIA driver is not loaded
ERROR: Unable to load info from any available system"
- The command: sudo prime-select nvidia[intel] work
+ Notes:
+ - The command: sudo prime-select nvidia[intel] always work
+ - Secure boot is disabled
SYSTEM INFORMATION:
Description: Ubuntu 18.04.1 LTS
Release: 18.04
nvidia-settings:
Installed: 396.54-0ubuntu0~gpu18.04.1
Candidate: 396.54-0ubuntu0~gpu18.04.1
Version table:
*** 396.54-0ubuntu0~gpu18.04.1 500
500 http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu bionic/main
amd64 Packages
100 /var/lib/dpkg/status
390.42-0ubuntu1 500
500 http://co.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
lspci -v -s 02:00
02:00.0 3D controller: NVIDIA Corporation GP108M [GeForce MX150] (rev a1)
Subsystem: Lenovo GP108M [GeForce MX150]
Flags: bus master, fast devsel, latency 0, IRQ 16
Memory at e800 (32-bit, non-prefetchable) [size=16M]
Memory at 7000 (64-bit, prefetchable) [size=256M]
Memory at 8000 (64-bit, prefetchable) [size=32M]
I/O ports at d000 [size=128]
Capabilities:
Kernel driver in use: nvidia
Kernel modules: nvidiafb, nouveau, nvidia_drm, nvidia
{
"Version": "18.04",
"OEM": {
"Vendor": "LENOVO",
},
"BIOS": {
"Vendor": "LENOVO",
},
"CPU": {
"OpMode": "32-bit, 64-bit",
"CPUs": "8",
"Threads": "2",
"Cores": "4",
"Sockets": "1",
"Vendor": "GenuineIntel",
"Family": "6",
"Model": "142",
"Stepping": "10",
"Name": "Intel(R) Core(TM) i5-8250U CPU @ 1.60GHz",
"Virtualization": "VT-x"
},
"Arch": "amd64",
"GPU": [
{
"Vendor": "8086",
"Model": "5917"
}
],
"RAM": 7.9,
"Disks": [
0
],
"Partitions": [
28.4,
0.3,
210.4
],
"Screens": [
{
"Size": "340mmx190mm",
"Resolution": "1368x768",
"Frequency": "59.71"
}
],
"Autologin": false,
"LivePatch": false,
"Session": {
"DE": "ubuntu:GNOME",
"Name": "ubuntu-wayland",
"Type": "wayland"
},
"Language": "en_US",
"Timezone": "America/Bogota",
"Install": {
"Media": "Ubuntu 18.04.1 LTS \"Bionic Beaver\" - Release amd64
(20180725)",
"Type": "GTK",
"OEM": false,
"PartitionMethod": "manual",
"DownloadUpdates": true,
"Language": "en",
"Minimal": true,
"RestrictedAddons": true,
"Stages": {
"0": "language",
"4": "console_setup",
"18": "console_setup",
"21": "wireless",
"86": "prepare",
"205": "partman",
"250": "partman",
"251": "partman",
"252": "partman",
"267": "partman",
"281": "partman",
"297": "partman",
"300": "start_install",
"314": "timezone",
"333": "usersetup",
"343": "user_done",
"800": "done"
}
}
}
Driver version: 396.54
--
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/1791951
Title:
nvidia-settings does not work when i install proprietary driver and
reboot
Status in nvidia-settings package in Ubuntu:
New
Bug description:
- What I expected to happen:
Open nvidia-settings and switch between Intel and Nvidia graphic cards.
- What happened instead:
Steps (case 1):
1. Install propetary driver.
2. Reboot and select Wayland session.
3. Open nvidia-settings --> "ERROR: Unable to find display on any available
system"
Steps (case 2)
1. sudo prime-select intel.
2. Reboot and select Wayland session.
3. Open nvidia-settings --> "ERROR: Unable to find display on any available
system"
Steps (case 3)
1. sudo
[Kernel-packages] [Bug 1791951] Re: nvidia-settings does not work when i install proprietary driver and reboot
** Description changed:
-What I expected to happen:
Open nvidia-settings and switch between Intel and Nvidia graphic cards.
-What happened instead:
Steps (case 1):
1. Install propetary driver.
2. Reboot and select Wayland session.
3. Open nvidia-settings --> "ERROR: Unable to find display on any available
system"
Steps (case 2)
1. sudo prime-select intel.
2. Reboot and select Wayland session.
3. Open nvidia-settings --> "ERROR: Unable to find display on any available
system"
Steps (case 3)
1. sudo prime-select nvidia.
1. Reboot and select X11 session.
- 2. Open nvidia-settings. --> Not ERROR.
+ 2. Open nvidia-settings. --> Not ERROR.
+
+ In my second test, this step generate an error:
+ "ERROR: NVIDIA driver is not loaded
+ ERROR: Unable to load info from any available system"
Steps (Case 4)
1. sudo prime-select intel.
2. Reboot and select X11 session.
3. Open nvidia-settings --> "ERROR: NVIDIA driver is not loaded
ERROR: Unable to load info from any available system"
The command: sudo prime-select nvidia[intel] work
SYSTEM INFORMATION:
Description: Ubuntu 18.04.1 LTS
Release: 18.04
nvidia-settings:
Installed: 396.54-0ubuntu0~gpu18.04.1
Candidate: 396.54-0ubuntu0~gpu18.04.1
Version table:
*** 396.54-0ubuntu0~gpu18.04.1 500
500 http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu bionic/main
amd64 Packages
100 /var/lib/dpkg/status
390.42-0ubuntu1 500
500 http://co.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
lspci -v -s 02:00
02:00.0 3D controller: NVIDIA Corporation GP108M [GeForce MX150] (rev a1)
Subsystem: Lenovo GP108M [GeForce MX150]
Flags: bus master, fast devsel, latency 0, IRQ 16
Memory at e800 (32-bit, non-prefetchable) [size=16M]
Memory at 7000 (64-bit, prefetchable) [size=256M]
Memory at 8000 (64-bit, prefetchable) [size=32M]
I/O ports at d000 [size=128]
Capabilities:
Kernel driver in use: nvidia
Kernel modules: nvidiafb, nouveau, nvidia_drm, nvidia
{
"Version": "18.04",
"OEM": {
"Vendor": "LENOVO",
},
"BIOS": {
"Vendor": "LENOVO",
},
"CPU": {
"OpMode": "32-bit, 64-bit",
"CPUs": "8",
"Threads": "2",
"Cores": "4",
"Sockets": "1",
"Vendor": "GenuineIntel",
"Family": "6",
"Model": "142",
"Stepping": "10",
"Name": "Intel(R) Core(TM) i5-8250U CPU @ 1.60GHz",
"Virtualization": "VT-x"
},
"Arch": "amd64",
"GPU": [
{
"Vendor": "8086",
"Model": "5917"
}
],
"RAM": 7.9,
"Disks": [
0
],
"Partitions": [
28.4,
0.3,
210.4
],
"Screens": [
{
"Size": "340mmx190mm",
"Resolution": "1368x768",
"Frequency": "59.71"
}
],
"Autologin": false,
"LivePatch": false,
"Session": {
"DE": "ubuntu:GNOME",
"Name": "ubuntu-wayland",
"Type": "wayland"
},
"Language": "en_US",
"Timezone": "America/Bogota",
"Install": {
"Media": "Ubuntu 18.04.1 LTS \"Bionic Beaver\" - Release amd64
(20180725)",
"Type": "GTK",
"OEM": false,
"PartitionMethod": "manual",
"DownloadUpdates": true,
"Language": "en",
"Minimal": true,
"RestrictedAddons": true,
"Stages": {
"0": "language",
"4": "console_setup",
"18": "console_setup",
"21": "wireless",
"86": "prepare",
"205": "partman",
"250": "partman",
"251": "partman",
"252": "partman",
"267": "partman",
"281": "partman",
"297": "partman",
"300": "start_install",
"314": "timezone",
"333": "usersetup",
"343": "user_done",
"800": "done"
}
}
}
Driver version: 396.54
--
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/1791951
Title:
nvidia-settings does not work when i install proprietary driver and
reboot
Status in nvidia-settings package in Ubuntu:
New
Bug description:
- What I expected to happen:
Open nvidia-settings and switch between Intel and Nvidia graphic cards.
- What happened instead:
Steps (case 1):
1. Install propetary driver.
2. Reboot and select Wayland session.
3. Open nvidia-settings --> "ERROR: Unable to find display on any available
system"
Steps (case 2)
1. sudo prime-select intel.
2. Reboot and select Wayland session.
3. Open nvidia-settings --> "ERROR: Unable to find display on any available
system"
Steps (case 3)
1. sudo prime-select nvidia.
2. Reboot and select X11 session.
3. Open nvidia-settings. --> Not ERROR.
In my second test, this step generate an error:
"ERROR: NVIDIA driver is not loaded
ERROR: Unable to load info from any available system"
[Kernel-packages] [Bug 1791664] Re: linux-azure: -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: New => Confirmed ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-master-bug: 1791663 + kernel-phase-changed:Tuesday, 11. September 2018 16:31 UTC + kernel-phase:Packaging ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-master-bug: 1791663 - kernel-phase-changed:Tuesday, 11. September 2018 16:31 UTC - kernel-phase:Packaging + phase: Packaging -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1791664 Title: linux-azure: -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow prepare-package series: Confirmed Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow prepare-package-signed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow stakeholder-signoff series: New Status in linux-azure package in Ubuntu: Confirmed Status in linux-azure source package in Cosmic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-master-bug: 1791663 phase: Packaging To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1791664/+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 1791979] 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 1791979 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1791979 Title: USB enumeration problem / Wandboard Quad rev. b1 Status in linux package in Ubuntu: Incomplete Bug description: The USB devices are detected/enumerated correctly with system start, but when disconnected later and connected once again are not recognized / enumerated anymore. Also removal of ci_hdrc_imx module causes the system hard lock without any information printed in the console. Tried with 4.15.0-29 4.15.0-33 4.15.0-34 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-34-generic 4.15.0-34.37 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic armv7l .etc.asound.conf: defaults.pcm.card 1 defaults.ctl.card 1 AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-34-generic. ApportVersion: 2.20.9-0ubuntu7.3 Architecture: armhf ArecordDevices: List of CAPTURE Hardware Devices AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/by-path', '/dev/snd/seq', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A Card0.Amixer.info: Card hw:0 'DWHDMI'/'DW-HDMI rev 0x0a, irq 19' Mixer name : '' Components : '' Controls : 0 Simple ctrls : 0 Card0.Amixer.values: Card1.Amixer.info: Card hw:1 'imxspdif'/'imx-spdif' Mixer name : '' Components : '' Controls : 7 Simple ctrls : 0 Card1.Amixer.values: Date: Tue Sep 11 18:11:46 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lspci: Lsusb: Bus 001 Device 002: ID 03f0:4117 Hewlett-Packard LaserJet 1018 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub PciMultimedia: ProcFB: ProcKernelCmdLine: console=ttymxc0,115200 root=/dev/sda2 RelatedPackageVersions: linux-restricted-modules-4.15.0-34-generic N/A linux-backports-modules-4.15.0-34-generic N/A linux-firmware 1.173.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux StagingDrivers: imx_media imx_media_csi imx_media_ic imx_media_vdic imx_media_capture imx_media_common UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791979/+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 1791951] Re: nvidia-settings does not work when i install proprietary driver and reboot
** Description changed:
Steps (case 1):
1. Install propetary driver.
2. Reboot and select Wayland session.
3. Open nvidia-settings --> "ERROR: Unable to find display on any available
system"
Steps (case 2)
1. sudo prime-select intel.
2. Reboot and select Wayland session.
3. Open nvidia-settings --> "ERROR: Unable to find display on any available
system"
- Steps (case 2)
+ Steps (case 3)
1. sudo prime-select nvidia.
1. Reboot and select X11 session.
2. Open nvidia-settings. --> Not ERROR.
- Steps (Case 3)
+ Steps (Case 4)
1. sudo prime-select intel.
2. Reboot and select X11 session.
3. Open nvidia-settings --> "ERROR: NVIDIA driver is not loaded
ERROR: Unable to load info from any available system"
The command: sudo prime-select nvidia[intel] work
SYSTEM INFORMATION:
Description: Ubuntu 18.04.1 LTS
Release: 18.04
nvidia-settings:
Installed: 396.54-0ubuntu0~gpu18.04.1
Candidate: 396.54-0ubuntu0~gpu18.04.1
Version table:
*** 396.54-0ubuntu0~gpu18.04.1 500
500 http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu bionic/main
amd64 Packages
100 /var/lib/dpkg/status
390.42-0ubuntu1 500
500 http://co.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
lspci -v -s 02:00
02:00.0 3D controller: NVIDIA Corporation GP108M [GeForce MX150] (rev a1)
Subsystem: Lenovo GP108M [GeForce MX150]
Flags: bus master, fast devsel, latency 0, IRQ 16
Memory at e800 (32-bit, non-prefetchable) [size=16M]
Memory at 7000 (64-bit, prefetchable) [size=256M]
Memory at 8000 (64-bit, prefetchable) [size=32M]
I/O ports at d000 [size=128]
Capabilities:
Kernel driver in use: nvidia
Kernel modules: nvidiafb, nouveau, nvidia_drm, nvidia
{
"Version": "18.04",
"OEM": {
"Vendor": "LENOVO",
},
"BIOS": {
"Vendor": "LENOVO",
},
"CPU": {
"OpMode": "32-bit, 64-bit",
"CPUs": "8",
"Threads": "2",
"Cores": "4",
"Sockets": "1",
"Vendor": "GenuineIntel",
"Family": "6",
"Model": "142",
"Stepping": "10",
"Name": "Intel(R) Core(TM) i5-8250U CPU @ 1.60GHz",
"Virtualization": "VT-x"
},
"Arch": "amd64",
"GPU": [
{
"Vendor": "8086",
"Model": "5917"
}
],
"RAM": 7.9,
"Disks": [
0
],
"Partitions": [
28.4,
0.3,
210.4
],
"Screens": [
{
"Size": "340mmx190mm",
"Resolution": "1368x768",
"Frequency": "59.71"
}
],
"Autologin": false,
"LivePatch": false,
"Session": {
"DE": "ubuntu:GNOME",
"Name": "ubuntu-wayland",
"Type": "wayland"
},
"Language": "en_US",
"Timezone": "America/Bogota",
"Install": {
"Media": "Ubuntu 18.04.1 LTS \"Bionic Beaver\" - Release amd64
(20180725)",
"Type": "GTK",
"OEM": false,
"PartitionMethod": "manual",
"DownloadUpdates": true,
"Language": "en",
"Minimal": true,
"RestrictedAddons": true,
"Stages": {
"0": "language",
"4": "console_setup",
"18": "console_setup",
"21": "wireless",
"86": "prepare",
"205": "partman",
"250": "partman",
"251": "partman",
"252": "partman",
"267": "partman",
"281": "partman",
"297": "partman",
"300": "start_install",
"314": "timezone",
"333": "usersetup",
"343": "user_done",
"800": "done"
}
}
}
Driver version: 396.54
** Description changed:
+ -What I expected to happen:
+ Open nvidia-settings and switch between Intel and Nvidia graphic cards.
+
+ -What happened instead:
+
Steps (case 1):
1. Install propetary driver.
2. Reboot and select Wayland session.
3. Open nvidia-settings --> "ERROR: Unable to find display on any available
system"
Steps (case 2)
1. sudo prime-select intel.
2. Reboot and select Wayland session.
3. Open nvidia-settings --> "ERROR: Unable to find display on any available
system"
Steps (case 3)
1. sudo prime-select nvidia.
1. Reboot and select X11 session.
2. Open nvidia-settings. --> Not ERROR.
Steps (Case 4)
1. sudo prime-select intel.
2. Reboot and select X11 session.
3. Open nvidia-settings --> "ERROR: NVIDIA driver is not loaded
ERROR: Unable to load info from any available system"
The command: sudo prime-select nvidia[intel] work
SYSTEM INFORMATION:
Description: Ubuntu 18.04.1 LTS
Release: 18.04
nvidia-settings:
Installed: 396.54-0ubuntu0~gpu18.04.1
Candidate: 396.54-0ubuntu0~gpu18.04.1
Version table:
*** 396.54-0ubuntu0~gpu18.04.1 500
500 http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu bionic/main
amd64 Packages
100 /var/lib/dpkg/status
390.42-0ubuntu1 500
500 http://co.archive.ubuntu.com/ubuntu bionic/main amd64
[Kernel-packages] [Bug 1791751] Re: linux-kvm: 4.4.0-1034.40 -proposed tracker
** Summary changed: - linux-kvm: -proposed tracker + linux-kvm: 4.4.0-1034.40 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Kleber Sacilotto de Souza (kleber-souza) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Kleber Sacilotto de Souza (kleber-souza) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1791751 Title: linux-kvm: 4.4.0-1034.40 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1791745 phase: Packaging To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1791751/+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 1791979] [NEW] USB enumeration problem / Wandboard Quad rev. b1
Public bug reported: The USB devices are detected/enumerated correctly with system start, but when disconnected later and connected once again are not recognized / enumerated anymore. Also removal of ci_hdrc_imx module causes the system hard lock without any information printed in the console. Tried with 4.15.0-29 4.15.0-33 4.15.0-34 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-34-generic 4.15.0-34.37 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic armv7l .etc.asound.conf: defaults.pcm.card 1 defaults.ctl.card 1 AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-34-generic. ApportVersion: 2.20.9-0ubuntu7.3 Architecture: armhf ArecordDevices: List of CAPTURE Hardware Devices AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/by-path', '/dev/snd/seq', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A Card0.Amixer.info: Card hw:0 'DWHDMI'/'DW-HDMI rev 0x0a, irq 19' Mixer name : '' Components : '' Controls : 0 Simple ctrls : 0 Card0.Amixer.values: Card1.Amixer.info: Card hw:1 'imxspdif'/'imx-spdif' Mixer name : '' Components : '' Controls : 7 Simple ctrls : 0 Card1.Amixer.values: Date: Tue Sep 11 18:11:46 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lspci: Lsusb: Bus 001 Device 002: ID 03f0:4117 Hewlett-Packard LaserJet 1018 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub PciMultimedia: ProcFB: ProcKernelCmdLine: console=ttymxc0,115200 root=/dev/sda2 RelatedPackageVersions: linux-restricted-modules-4.15.0-34-generic N/A linux-backports-modules-4.15.0-34-generic N/A linux-firmware 1.173.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux StagingDrivers: imx_media imx_media_csi imx_media_ic imx_media_vdic imx_media_capture imx_media_common UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug armhf bionic staging third-party-packages -- 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/1791979 Title: USB enumeration problem / Wandboard Quad rev. b1 Status in linux package in Ubuntu: New Bug description: The USB devices are detected/enumerated correctly with system start, but when disconnected later and connected once again are not recognized / enumerated anymore. Also removal of ci_hdrc_imx module causes the system hard lock without any information printed in the console. Tried with 4.15.0-29 4.15.0-33 4.15.0-34 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-34-generic 4.15.0-34.37 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic armv7l .etc.asound.conf: defaults.pcm.card 1 defaults.ctl.card 1 AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-34-generic. ApportVersion: 2.20.9-0ubuntu7.3 Architecture: armhf ArecordDevices: List of CAPTURE Hardware Devices AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/by-path', '/dev/snd/seq', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A Card0.Amixer.info: Card hw:0 'DWHDMI'/'DW-HDMI rev 0x0a, irq 19' Mixer name : '' Components : '' Controls : 0 Simple ctrls : 0 Card0.Amixer.values: Card1.Amixer.info: Card hw:1 'imxspdif'/'imx-spdif' Mixer name : '' Components : '' Controls : 7 Simple ctrls : 0 Card1.Amixer.values: Date: Tue Sep 11 18:11:46 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lspci: Lsusb: Bus 001 Device 002: ID 03f0:4117 Hewlett-Packard LaserJet 1018 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub PciMultimedia: ProcFB: ProcKernelCmdLine: console=ttymxc0,115200 root=/dev/sda2 RelatedPackageVersions: linux-restricted-modules-4.15.0-34-generic N/A linux-backports-modules-4.15.0-34-generic N/A linux-firmware 1.173.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux StagingDrivers: imx_media imx_media_csi imx_media_ic imx_media_vdic imx_media_capture imx_media_common UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791979/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe :
[Kernel-packages] [Bug 1791663] Re: linux: 4.18.0-8.9 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-signed Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Fix Committed ** Tags added: block-proposed-cosmic ** Tags added: block-proposed ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: derivatives: bug 1791664 (linux-azure) + kernel-phase:Uploaded + kernel-phase-changed:Tuesday, 11. September 2018 16:02 UTC ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: derivatives: bug 1791664 (linux-azure) kernel-phase:Uploaded kernel-phase-changed:Tuesday, 11. September 2018 16:02 UTC + + -- swm properties -- + phase: Uploaded -- 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/1791663 Title: linux: 4.18.0-8.9 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Cosmic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: derivatives: bug 1791664 (linux-azure) kernel-phase:Uploaded kernel-phase-changed:Tuesday, 11. September 2018 16:02 UTC -- swm properties -- phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1791663/+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 1791953] Re: Xenial update to 4.4.146 stable release
** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Xenial) Status: New => In Progress ** Changed in: linux (Ubuntu Xenial) Assignee: (unassigned) => Stefan Bader (smb) ** Changed in: linux (Ubuntu) Status: New => Invalid ** Description changed: + SRU Justification - SRU Justification + Impact: + The upstream process for stable tree updates is quite similar + in scope to the Ubuntu SRU process, e.g., each patch has to + demonstrably fix a bug, and each patch is vetted by upstream + by originating either directly from a mainline/stable Linux tree or + a minimally backported form of that patch. The 4.4.146 upstream stable + patch set is now available. It should be included in the Ubuntu + kernel as well. - Impact: -The upstream process for stable tree updates is quite similar -in scope to the Ubuntu SRU process, e.g., each patch has to -demonstrably fix a bug, and each patch is vetted by upstream -by originating either directly from a mainline/stable Linux tree or -a minimally backported form of that patch. The 4.4.146 upstream stable -patch set is now available. It should be included in the Ubuntu -kernel as well. + git://git.kernel.org/ -git://git.kernel.org/ + TEST CASE: TBD - TEST CASE: TBD - -The following patches from the 4.4.146 stable release shall be - applied: + The following patches from the 4.4.146 stable release shall be applied: + * MIPS: Fix off-by-one in pci_resource_to_user() + * Input: elan_i2c - add ACPI ID for lenovo ideapad 330 + * Input: i8042 - add Lenovo LaVie Z to the i8042 reset list + * Input: elan_i2c - add another ACPI ID for Lenovo Ideapad 330-15AST + * tracing: Fix double free of event_trigger_data + * tracing: Fix possible double free in event_enable_trigger_func() + * tracing/kprobes: Fix trace_probe flags on enable_trace_kprobe() failure + * tracing: Quiet gcc warning about maybe unused link variable + * xen/netfront: raise max number of slots in xennet_get_responses() + * ALSA: emu10k1: add error handling for snd_ctl_add + * ALSA: fm801: add error handling for snd_ctl_add + * nfsd: fix potential use-after-free in nfsd4_decode_getdeviceinfo + * mm: vmalloc: avoid racy handling of debugobjects in vunmap + * mm/slub.c: add __printf verification to slab_err() + * rtc: ensure rtc_set_alarm fails when alarms are not supported + * netfilter: ipset: List timing out entries with "timeout 1" instead of zero + * infiniband: fix a possible use-after-free bug + * hvc_opal: don't set tb_ticks_per_usec in udbg_init_opal_common() + * powerpc/64s: Fix compiler store ordering to SLB shadow area + * RDMA/mad: Convert BUG_ONs to error flows + * disable loading f2fs module on PAGE_SIZE > 4KB + * f2fs: fix to don't trigger writeback during recovery + * usbip: usbip_detach: Fix memory, udev context and udev leak + * perf/x86/intel/uncore: Correct fixed counter index check in generic code + * perf/x86/intel/uncore: Correct fixed counter index check for NHM + * iwlwifi: pcie: fix race in Rx buffer allocator + * Bluetooth: hci_qca: Fix "Sleep inside atomic section" warning + * Bluetooth: btusb: Add a new Realtek 8723DE ID 2ff8:b011 + * ASoC: dpcm: fix BE dai not hw_free and shutdown + * mfd: cros_ec: Fail early if we cannot identify the EC + * mwifiex: handle race during mwifiex_usb_disconnect + * wlcore: sdio: check for valid platform device data before suspend + * media: videobuf2-core: don't call memop 'finish' when queueing + * btrfs: add barriers to btrfs_sync_log before log_commit_wait wakeups + * btrfs: qgroup: Finish rescan when hit the last leaf of extent tree + * PCI: Prevent sysfs disable of device while driver is attached + * ath: Add regulatory mapping for FCC3_ETSIC + * ath: Add regulatory mapping for ETSI8_WORLD + * ath: Add regulatory mapping for APL13_WORLD + * ath: Add regulatory mapping for APL2_FCCA + * ath: Add regulatory mapping for Uganda + * ath: Add regulatory mapping for Tanzania + * ath: Add regulatory mapping for Serbia + * ath: Add regulatory mapping for Bermuda + * ath: Add regulatory mapping for Bahamas + * powerpc/32: Add a missing include header + * powerpc/chrp/time: Make some functions static, add missing header include + * powerpc/powermac: Add missing prototype for note_bootable_part() + * powerpc/powermac: Mark variable x as unused + * powerpc/8xx: fix invalid register expression in head_8xx.S + * pinctrl: at91-pio4: add missing of_node_put + * PCI: pciehp: Request control of native hotplug only if supported + * mwifiex: correct histogram data with appropriate index + * scsi: ufs: fix exception event handling + * ALSA: emu10k1: Rate-limit error messages about page errors + * regulator: pfuze100: add .is_enable() for pfuze100_swb_regulator_ops + *
[Kernel-packages] [Bug 1791147] Re: package linux-modules-extra-4.15.0-33-generic (not installed) failed to install/upgrade: no package named 'linux-modules-extra-4.15.0-33-generic' is installed, cann
You may need to run the following from a terminal: sudo apt-get install -f sudo apt-get clean sudo apt-get update Then re-install the package or updates. If that does not resolve your issue, please mark the bug as "Confirmed" ** Package changed: linux-hwe (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1791147 Title: package linux-modules-extra-4.15.0-33-generic (not installed) failed to install/upgrade: no package named 'linux-modules- extra-4.15.0-33-generic' is installed, cannot configure Status in linux package in Ubuntu: Incomplete Bug description: not able to fix this . update is available but not able to update the ubantu ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-modules-extra-4.15.0-33-generic (not installed) ProcVersionSignature: Ubuntu 4.15.0-32.35~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Fri Sep 7 00:05:35 2018 ErrorMessage: no package named 'linux-modules-extra-4.15.0-33-generic' is installed, cannot configure InstallationDate: Installed on 2018-08-13 (24 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.27 SourcePackage: linux-hwe Title: package linux-modules-extra-4.15.0-33-generic (not installed) failed to install/upgrade: no package named 'linux-modules-extra-4.15.0-33-generic' is installed, cannot configure UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791147/+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 1791312] Re: ubuntu 18.04 flickering screen with Radeon X1600
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.19 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19-rc3 ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1791312 Title: ubuntu 18.04 flickering screen with Radeon X1600 Status in linux package in Ubuntu: Incomplete Bug description: my laptop: HP Compaq nx9420 my grafic card: 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RV530/M56-P [Mobility Radeon X1600] (prog-if 00 [VGA controller]) attachment: the bug-apport-file Description: I start ubuntu 18.04 LTS (Kernel 4.15.0.33) in textmode; -> as soon as the kernel-module radeon.ko is loaded the screen starts flickering when starting the grafic-mode the flickering continues; so the screen is unusable. when setting the option "radeon.modeset=0" (thus: not use radeon drivers) the screen does not flicker but the resolution is limited to 1400x1050 (instead of natural 1680x1050) so I can not use this as work-around when using the old ubuntu 14.04.05 LTS (Kernel 3.13.0-157) the screen is o.k. NO flickering in textmode, nice grafic, NO flickering xrandr tells: 1680x1050 60.1 so I must stay on old ubuntu 14.04.05 ??? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791312/+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 1791749] Re: linux-aws: -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: New => Confirmed ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1791745 + kernel-stable-phase:Packaging + kernel-stable-phase-changed:Tuesday, 11. September 2018 15:31 UTC ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1791745 - kernel-stable-phase:Packaging - kernel-stable-phase-changed:Tuesday, 11. September 2018 15:31 UTC + phase: Packaging -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1791749 Title: linux-aws: -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Confirmed Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1791745 phase: Packaging To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1791749/+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 1791746] Re: linux-aws: -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: New => Confirmed ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1791745 + kernel-stable-phase:Packaging + kernel-stable-phase-changed:Tuesday, 11. September 2018 15:30 UTC ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1791745 - kernel-stable-phase:Packaging - kernel-stable-phase-changed:Tuesday, 11. September 2018 15:30 UTC + phase: Packaging -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1791746 Title: linux-aws: -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Confirmed Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Trusty: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1791745 phase: Packaging To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1791746/+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 1791745] Re: linux: 4.4.0-136.162 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-signed Status: In Progress => Fix Released ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1791746 (linux-aws), bug 1791747 (linux-lts-xenial) derivatives: bug 1791749 (linux-aws), bug 1791750 (linux-euclid), bug 1791751 (linux-kvm), bug 1791752 (linux-raspi2), bug 1791753 (linux-snapdragon) + kernel-stable-phase:Uploaded + kernel-stable-phase-changed:Tuesday, 11. September 2018 15:30 UTC ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1791746 (linux-aws), bug 1791747 (linux-lts-xenial) derivatives: bug 1791749 (linux-aws), bug 1791750 (linux-euclid), bug 1791751 (linux-kvm), bug 1791752 (linux-raspi2), bug 1791753 (linux-snapdragon) kernel-stable-phase:Uploaded kernel-stable-phase-changed:Tuesday, 11. September 2018 15:30 UTC + + -- swm properties -- + phase: Uploaded -- 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/1791745 Title: linux: 4.4.0-136.162 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-certification-testing series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1791746 (linux-aws), bug 1791747 (linux-lts-xenial) derivatives: bug 1791749 (linux-aws), bug 1791750 (linux-euclid), bug 1791751 (linux-kvm), bug 1791752 (linux-raspi2), bug 1791753 (linux-snapdragon) kernel-stable-phase:Uploaded kernel-stable-phase-changed:Tuesday, 11. September 2018 15:30 UTC -- swm properties -- phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1791745/+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 1791321] Re: No video on laptop display after suspend/resume
Forwarded to https://bugzilla.kernel.org/show_bug.cgi?id=201091. ** Bug watch added: Linux Kernel Bug Tracker #201091 https://bugzilla.kernel.org/show_bug.cgi?id=201091 -- 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/1791321 Title: No video on laptop display after suspend/resume Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Bug description: Between linux 4.15.0-23 and 4.15.0-24, suspend/resume stopped working correctly. After resume, the laptop panel remains blank with -24 (external monitors resume correctly). Suspend/resume worked correctly with -23. Ubuntu 18.04 LTS Lenovo P50 laptop, using nouveau driver --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: john 1100 F pulseaudio /dev/snd/controlC0: john 1100 F pulseaudio DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=1114cee9-db59-4a6e-a257-06ed1131a72b InstallationDate: Installed on 2017-02-01 (586 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: LENOVO 20EN001AUS Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic root=UUID=cd371ad3-bcc5-4389-b0b7-910bd49727c5 ro quiet ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-23-generic N/A linux-backports-modules-4.15.0-23-generic N/A linux-firmware 1.173.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux 4.15.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark _MarkForUpload: True dmi.bios.date: 03/28/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N1EET77W (1.50 ) dmi.board.asset.tag: Not Available dmi.board.name: 20EN001AUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1EET77W(1.50):bd03/28/2018:svnLENOVO:pn20EN001AUS:pvrThinkPadP50:rvnLENOVO:rn20EN001AUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P50 dmi.product.name: 20EN001AUS dmi.product.version: ThinkPad P50 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791321/+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 1791751] Re: linux-kvm: -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: New => Confirmed ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1791745 + kernel-stable-phase:Packaging + kernel-stable-phase-changed:Tuesday, 11. September 2018 15:31 UTC ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1791745 - kernel-stable-phase:Packaging - kernel-stable-phase-changed:Tuesday, 11. September 2018 15:31 UTC + phase: Packaging -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1791751 Title: linux-kvm: -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Confirmed Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1791745 phase: Packaging To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1791751/+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 1785912] Re: Screen flicker Intel UHD graphics 620 (rev 07) Lenovo Ideapad 720s 13IKB 81BV
** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1785912 Title: Screen flicker Intel UHD graphics 620 (rev 07) Lenovo Ideapad 720s 13IKB 81BV Status in linux package in Ubuntu: Incomplete Bug description: Horrible screen flicker from login screen and after login. 18.04.1 LTS. I have two similar laptops, both Lenovo Ideapad 720s 13IKB, model 81A8 - Core i5 7200U - Intel HD Graphics 620 Rev 02 - works fine. model 81BV - Core i5 8250U - Intel UHD Graphics 620 Rev 07 - awful screen flashing. Neither have the problem in Windows (ie hardware fine) I installed the standard Ubuntu 18.04 on each of them (same USB Key, few weeks apart) but only the 81BV / 8th gen / UHD 620 Rev 07 has the problem. Flickering visible on video here: https://photos.app.goo.gl/HCN73q1nQfgstgVBA I've used ubuntu-bug so I believe you have all the details of the machine. The install came straight from your standard 18.04 download. Any changes are due to me trying to fix this (not much prev exp of kernel params etc) Things tried but which didn't work were: - enable huc/guc (got it to load - it's now visible in the attached dmesg - but didn't help.) - enable_rc6=0 (just stopped sleep / resume working) - edp_vswing=2 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xserver-xorg-video-intel 2:2.99.917+git20171229-1 ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18 Uname: Linux 4.15.0-30-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CompositorRunning: None Date: Tue Aug 7 23:09:14 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 [17aa:39af] InstallationDate: Installed on 2018-08-06 (1 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 004: ID 0cf3:e500 Atheros Communications, Inc. Bus 001 Device 003: ID 5986:210d Acer, Inc Bus 001 Device 002: ID 06cb:0081 Synaptics, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81BV ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic root=UUID=10eb4e00-26e4-4f42-b983-9a603a658f89 ro i915.enable_guc=3 i915.enable_guc_loading=1 SourcePackage: xserver-xorg-video-intel UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/02/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 6MCN27WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 720S-13IKB dmi.modalias: dmi:bvnLENOVO:bvr6MCN27WW:bd05/02/2018:svnLENOVO:pn81BV:pvrLenovoideapad720S-13IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad720S-13IKB: dmi.product.family: ideapad 720S-13IKB dmi.product.name: 81BV dmi.product.version: Lenovo ideapad 720S-13IKB dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1785912/+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 1788686] Re: Acer laptop does not boot Ubuntu 16.04.5
Would it be possible for you to test the proposed kernel and post back if it resolves this bug? See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Tags added: kernel-da-key ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1788686 Title: Acer laptop does not boot Ubuntu 16.04.5 Status in linux package in Ubuntu: Incomplete Bug description: *** *** Please change package to the appropriate one *** Trying to boot Acer laptop () from USB2 key on USB3 port with Ubuntu 16.04.5 LTS fails as per attached screenshots. This is reproducible. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gedit 3.18.3-0ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-133.159-generic 4.4.134 Uname: Linux 4.4.0-133-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Aug 23 15:11:08 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2017-07-22 (397 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gedit UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788686/+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 1779483] Re: DRM bug
Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem? Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.19 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19-rc3 ** Changed in: linux (Ubuntu) Importance: Undecided => Medium -- 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/1779483 Title: DRM bug Status in linux package in Ubuntu: Incomplete Bug description: [ 215.876104] [ cut here ] [ 215.876108] vblank wait timed out on crtc 1 [ 215.876235] WARNING: CPU: 0 PID: 811 at /build/linux-9slaCn/linux-4.15.0/drivers/gpu/drm/drm_vblank.c:1073 drm_wait_one_vblank+0x1a1/0x1b0 [drm] [ 215.876237] Modules linked in: ccm bnep coretemp kvm_intel kvm irqbypass pcmcia arc4 btusb btrtl yenta_socket pcmcia_rsrc joydev btbcm btintel pcmcia_core input_leds bluetooth ecdh_generic serio_raw snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel snd_hda_codec iwl4965 lpc_ich iwlegacy snd_hda_core mac80211 snd_hwdep cfg80211 snd_pcm snd_timer fujitsu_laptop snd sparse_keymap soundcore smsc_ircc2(CE) irda(CE) mac_hid shpchp sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables autofs4 ahci psmouse i915 libahci i2c_algo_bit sdhci_pci e1000e drm_kms_helper sdhci pata_acpi firewire_ohci ptp firewire_core syscopyarea crc_itu_t pps_core sysfillrect sysimgblt fb_sys_fops drm video [ 215.876363] CPU: 0 PID: 811 Comm: Xorg Tainted: GWC E 4.15.0-23-generic #25-Ubuntu [ 215.876371] Hardware name: FUJITSU SIEMENS LIFEBOOK E8410/FJNB1CF, BIOS Version 1.10 12/27/2007 [ 215.876412] EIP: drm_wait_one_vblank+0x1a1/0x1b0 [drm] [ 215.876416] EFLAGS: 00010292 CPU: 0 [ 215.876420] EAX: 001f EBX: f4954000 ECX: f1ad5630 EDX: 0007 [ 215.876424] ESI: 0001 EDI: EBP: ef8abb74 ESP: ef8abb3c [ 215.876428] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 [ 215.876433] CR0: 80050033 CR2: bf807f7c CR3: 32a0a8a0 CR4: 06f0 [ 215.876436] Call Trace: [ 215.876455] ? wait_woken+0x70/0x70 [ 215.876552] intel_get_load_detect_pipe+0x5eb/0x650 [i915] [ 215.876567] ? chksum_finup+0x20/0x20 [ 215.876653] intel_tv_detect+0x113/0x4b0 [i915] [ 215.876743] ? intel_tv_get_modes+0x1f0/0x1f0 [i915] [ 215.876767] drm_helper_probe_detect+0x45/0x80 [drm_kms_helper] [ 215.876790] drm_helper_probe_single_connector_modes+0xbc/0x640 [drm_kms_helper] [ 215.876814] ? drm_helper_probe_detect+0x80/0x80 [drm_kms_helper] [ 215.876856] drm_mode_getconnector+0x11e/0x2c0 [drm] [ 215.876900] ? drm_mode_connector_property_set_ioctl+0x60/0x60 [drm] [ 215.876936] drm_ioctl_kernel+0x56/0xb0 [drm] [ 215.876972] drm_ioctl+0x2c4/0x370 [drm] [ 215.877014] ? drm_mode_connector_property_set_ioctl+0x60/0x60 [drm] [ 215.877029] ? dput.part.22+0xcf/0x1e0 [ 215.877064] ? drm_version+0x80/0x80 [drm] [ 215.877073] do_vfs_ioctl+0x93/0x6b0 [ 215.877083] ? vfs_write+0x150/0x1a0 [ 215.877089] ? vfs_write+0x125/0x1a0 [ 215.877098] SyS_ioctl+0x58/0x70 [ 215.877108] do_fast_syscall_32+0x7f/0x1e0 [ 215.877118] entry_SYSENTER_32+0x4e/0x7c [ 215.877125] EIP: 0xb7ef7d09 [ 215.877128] EFLAGS: 3292 CPU: 0 [ 215.877132] EAX: ffda EBX: 000e ECX: c05064a7 EDX: bfb35478 [ 215.877135] ESI: 0001 EDI: c05064a7 EBP: 000e ESP: bfb353f8 [ 215.877140] DS: 007b ES: 007b FS: GS: 0033 SS: 007b [ 215.877144] Code: 00 00 00 e9 e4 fe ff ff e8 5d 48 94 cb 8b 45 d0 8d 55 dc e8 62 66 98 cb 85 ff 0f 85 ee fe ff ff 56 68 48 a2 74 f8 e8 cf 45 94 cb <0f> 0b 58 5a e9 da fe ff ff 8d b6 00 00 00 00 66 66 66 66 90 55 [ 215.877254] ---[ end trace 50ae73cd2f1975a1 ]--- ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xserver-xorg-video-intel 2:2.99.917+git20171229-1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic i686 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: i386 Date: Sat Jun 30 19:21:28 2018 InstallationDate: Installed on 2017-11-01 (240 days ago) InstallationMedia: Lubuntu 17.10 "Artful Aardvark" - Release i386 (20171017.1) SourcePackage: xserver-xorg-video-intel UpgradeStatus: Upgraded to bionic on 2018-06-30 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779483/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to
[Kernel-packages] [Bug 1783906] Re: Linux 4.15 and onwards fails to initialize some hard drives
I built a test kernel with the patch from David posted in comment #21. The
test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1783906
Can you test this kernel and see if it resolves this bug?
Note about installing test kernels:
• If the test kernel is prior to 4.15(Bionic) you need to install the
linux-image and linux-image-extra .deb packages.
• If the test kernel is 4.15(Bionic) or newer, you need to install the
linux-modules, linux-modules-extra and linux-image-unsigned .deb packages.
Thanks in advance!
--
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/1783906
Title:
Linux 4.15 and onwards fails to initialize some hard drives
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Bionic:
In Progress
Status in linux source package in Cosmic:
In Progress
Bug description:
I have two hard drives, the main hard drive is a TOSHIBA DT01ACA200
the second backup hard drive is a Western Digital WD5003AZEX. I
installed lubuntu 18.04.1 on the Toshiba HDD and it boots just fine,
the issue is with the second hard drive, when installing the WD HDD
wouldn't even come as an option to install, and after boot the WD HDD
still wouldn't come up, this is the dmesg with the stock kernel (4.15)
https://paste.ubuntu.com/p/kpxh94v2SK/
ata6 is the WD HDD that refuses to work. The messages:
[ 302.107650] ata6: SError: { CommWake 10B8B Dispar DevExch }
[ 302.107658] ata6: hard resetting link
[ 307.860291] ata6: link is slow to respond, please be patient (ready=0)
[ 312.120898] ata6: COMRESET failed (errno=-16)
[ 363.445120] INFO: task kworker/u8:5:201 blocked for more than 120 seconds.
[ 363.445131] Not tainted 4.15.0-29-generic #31-Ubuntu
[ 363.445135] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables
this message.
[ 363.445140] kworker/u8:5D0 201 2 0x8000
[ 363.445155] Workqueue: events_unbound async_run_entry_fn
[ 363.445157] Call Trace:
[ 363.445171] __schedule+0x291/0x8a0
[ 363.445177] schedule+0x2c/0x80
[ 363.445182] ata_port_wait_eh+0x7c/0xf0
[ 363.445186] ? wait_woken+0x80/0x80
[ 363.445189] ata_port_probe+0x28/0x40
[ 363.445192] async_port_probe+0x2e/0x52
[ 363.445196] async_run_entry_fn+0x3c/0x150
[ 363.445199] process_one_work+0x1de/0x410
[ 363.445203] worker_thread+0x32/0x410
[ 363.445207] kthread+0x121/0x140
[ 363.445210] ? process_one_work+0x410/0x410
[ 363.445214] ? kthread_create_worker_on_cpu+0x70/0x70
[ 363.445218] ret_from_fork+0x22/0x40
Repeat constantly. Also when I try to turn off the computer, the
computer seem to freeze, the lights of the keyboard and mouse turn off
and the computer just stay on.
I tried Tiny Core 9.0 which has linux 4.14.10, and i didn't had this
issue, i also installed linux 4.14 on this lubuntu 18.04 using Ukuu
Kernel Update Utility. And with this kernel version, or any previous
version the WD HDD does work again. Here's a dmesg of lubuntu 18.04
with linux 4.14 and the WD HDD finally coming up at the end:
https://paste.ubuntu.com/p/Gd3cGFbjTJ/
Also tried with with linux 4.17 but the WD HDD would also refuse to
work on this version. Here's another dmesg with this version:
https://paste.ubuntu.com/p/PmNn96vZZv/
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
AlsaVersion: Advanced Linux Sound Architecture Driver Version
k4.15.0-29-generic.
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: testtest756 F pulseaudio
/dev/snd/controlC1: testtest756 F pulseaudio
Card0.Amixer.info:
Card hw:0 'NVidia_1'/'HDA NVidia at 0xfe02 irq 22'
Mixer name : 'Realtek ALC1200'
Components : 'HDA:10ec0888,10ec,00100101
HDA:10de0002,10de0101,0010'
Controls : 56
Simple ctrls : 21
Card1.Amixer.info:
Card hw:1 'NVidia'/'HDA NVidia at 0xfcffc000 irq 16'
Mixer name : 'Nvidia GPU 42 HDMI/DP'
Components : 'HDA:10de0042,38422651,00100100'
Controls : 21
Simple ctrls : 3
CurrentDesktop: LXDE
Date: Thu Jul 26 17:10:58 2018
HibernationDevice: RESUME=UUID=17e70869-516d-4b63-b900-e92e3c4b73b6
InstallationDate: Installed on 2018-07-26 (0 days ago)
InstallationMedia: Lubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64
(20180725)
MachineType: 113 1
ProcFB: 0 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic
root=UUID=71cf0a32-7827-49be-a2c0-cd50a72c26a1 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
[Kernel-packages] [Bug 1559308] Re: Plugging HDMI screen in causes system hang
Still hitting this using MATE and the NVIDIA Drivers: calvinh@calvinh-ws:/var/log$ uname -a Linux calvinh-ws 4.15.0-34-generic #37~16.04.1-Ubuntu SMP Tue Aug 28 10:44:06 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux calvinh@calvinh-ws:/var/log$ sudo apt-get install nvidia-384 Reading package lists... Done Building dependency tree Reading state information... Done nvidia-384 is already the newest version (384.130-0ubuntu0.16.04.1). Cannot plug in my second monitor, it locks the system up until I unplug it. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1559308 Title: Plugging HDMI screen in causes system hang Status in linux package in Ubuntu: Fix Released Bug description: I have a 4K UHD laptop screen and am running Ubuntu Gnome 16.04 Beta1 using 4.4.0-13-generic and the Nouveau drivers. If I plug in an external HDMI monitor (FHD) either into either HDMI port (there's one on the machine and there's one available via a usb 3.1 extra adaptor) then the whole system hangs, completely unresponsive and needing a hard reboot. Before hanging the 2nd display gets an image as expected, but the laptop's screen flashes randomly, sometimes you see weird artifacts. Then the hang comes. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xserver-xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-13.29-generic 4.4.5 Uname: Linux 4.4.0-13-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME Date: Fri Mar 18 20:43:42 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Skylake Integrated Graphics [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Dell Skylake Integrated Graphics [1028:06e4] Subsystem: Dell GM107M [GeForce GTX 960M] [1028:06e4] InstallationDate: Installed on 2016-03-15 (3 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160225.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f3:21d5 Elan Microelectronics Corp. Bus 001 Device 002: ID 0a5c:6410 Broadcom Corp. Bus 001 Device 004: ID 0c45:6713 Microdia Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 15 9550 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-13-generic.efi.signed root=UUID=b026feed-8801-44f4-9f3f-c245f4a1f25e ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/25/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.01.19 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.01.19:bd01/25/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 15 9550 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.1.2-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.1.2-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.1-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.6.1-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160218-1ubuntu3 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Fri Mar 18 17:28:07 2016 xserver.configfile: default xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) Unknown chipset: NV117 SynPS/2 Synaptics TouchPad: Read error 19 xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id5182 vendor SHP xserver.version: 2:1.18.1-1ubuntu4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1559308/+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 1788686] Re: Acer laptop does not boot Ubuntu 16.04.5
Joseph Salisbury (jsalisbury), If you can direct me to an ISO download distribution containing your proposed kernel, then yes, I can test. Else, out of luck, sorry. The PC does not boot at all. ** Changed in: linux (Ubuntu) Status: Incomplete => 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/1788686 Title: Acer laptop does not boot Ubuntu 16.04.5 Status in linux package in Ubuntu: In Progress Bug description: *** *** Please change package to the appropriate one *** Trying to boot Acer laptop () from USB2 key on USB3 port with Ubuntu 16.04.5 LTS fails as per attached screenshots. This is reproducible. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gedit 3.18.3-0ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-133.159-generic 4.4.134 Uname: Linux 4.4.0-133-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Aug 23 15:11:08 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2017-07-22 (397 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gedit UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788686/+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 1791195] Re: Lenovo ideapad FLEX 6-14ARR no trackpad no touch/pen no wifi
Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem? Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.19 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19-rc3 ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1791195 Title: Lenovo ideapad FLEX 6-14ARR no trackpad no touch/pen no wifi Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu 18.04.1 LTS Device wifi/bluetooth is hardlocked, proper drivers don't achieve anything. The blacklist 'ideapad_laptop' workaround enables wifi but disables other features important for use as a 2-in-1. Device uses Synaptics touchpad but isn't functional. Touch/Stylus Screen is Wacom AES but haven't been able to get Linux to identify it. Version: 8MCN25WW Version: Lenovo ideapad FLEX 6-14ARR Version: SDK0J40709 WIN Version: Lenovo ideapad FLEX 6-14ARR Version: AMD Ryzen 5 2500U with Radeon Vega Mobile Gfx String: Compiler Version: VC 9.0 Linux pepper 4.18.6-041806-generic #201809050847 SMP Wed Sep 5 08:49:36 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux 0:ideapad_wlan: Wireless LAN Soft Blocked: no Hard Blocked: yes 1: ideapad_bluetooth: Bluetooth Soft Blocked: yes Hard Blocked: yes 3: phy0:Wireless LAN Soft Blocked: no Hard blocked: no 4. hci0 Bluetooth Soft blocked: yes Hard blocked: no SecureBoot disabled Vendor: LENOVO Vendor Syndrome: Unknown Vendor Syndrome: Unknown Vendor Syndrome: Unknown --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: arielle1667 F pulseaudio /dev/snd/controlC0: arielle1667 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-09-06 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 81HA Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic root=UUID=d1b7dad0-c413-4c06-af98-585f57943bdb ro i8042.notimeout i8042.nomux i8042.nopnp quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 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 StagingDrivers: r8822be Tags: bionic staging Uname: Linux 4.15.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/02/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 8MCN25WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad FLEX 6-14ARR dmi.modalias: dmi:bvnLENOVO:bvr8MCN25WW:bd08/02/2018:svnLENOVO:pn81HA:pvrLenovoideapadFLEX6-14ARR:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoideapadFLEX6-14ARR: dmi.product.family: ideapad FLEX 6-14ARR dmi.product.name: 81HA dmi.product.version: Lenovo ideapad FLEX 6-14ARR dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791195/+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 1791959] Re: remove /boot/initrd.img-*.old-dkms files left behind
** Also affects: initramfs-tools (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: dkms (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: initramfs-tools (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: dkms (Ubuntu Bionic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1791959 Title: remove /boot/initrd.img-*.old-dkms files left behind Status in dkms package in Ubuntu: Invalid Status in initramfs-tools package in Ubuntu: Confirmed Status in dkms source package in Xenial: New Status in initramfs-tools source package in Xenial: New Status in dkms source package in Bionic: New Status in initramfs-tools source package in Bionic: New Bug description: [Impact] If a dkms package is installed which has REMAKE_INITRD or the same setting has been manually configured by a user then when a kernel is removed its possible for an ".old-dkms" file to be left in /boot with no associated kernel. bug 1515513 dealt with removing initrd.img-.old-dkms files using the kernel's prerm hook, but that is only executed for the kernel version being removed: any other old-dkms file generated prior to that would not be removed by the hook, taking space in the /boot directory. Note: Filling up the /boot partition causes updates to fail. [Test Case] As the fix for bug 1515513 is available on Xenial it is no longer possible to reproduce this by simply installing and updating kernels (dkms 2.2.0.3-2ubuntu11.3 would be required for that). In order to replicate it an old dkms file will be created by hand. This assumes a new Xenial schroot. 1) create a file to work as a placeholder for the initrd.img old dkms file sudo touch /boot/initrd.img-4.0.0-0-generic.old-dkms 2) install 3 old kernels, r8168-dkms, and the current initramfs-tools sudo apt-get install -y linux-image-4.4.0-21-generic linux-image-4.4.0-22-generic linux-image-4.4.0-24-generic r8168-dkms initramfs-tools=0.122ubuntu8.12 3) install the headers for the old kernels (forces dkms to run) sudo apt-get install -y linux-headers-4.4.0-21-generic linux-headers-4.4.0-22-generic linux-headers-4.4.0-24-generic 4) verify that there are 4 old-dkms, the manually created and one for each installed kernel ls /boot/*.old-dkms 5) install the initramfs-tools that contains this fix sudo apt-get install -y initramfs-tools 6) verify that the manually created old-dkms file was removed and that there are only 3 files now, one for each installed kernel ls /boot/*.old-dkms 7) autoremove the older kernel sudo apt-get autoremove -y 8) verify that there are now only 2 old-dkms, one for each installed kernel ls /boot/*.old-dkms [Regression Potential] Somebody out there might expect the .old-dkms file to be kept, but that seems like an odd expectation. One notices *.old-dkms files being left behind still sitting on the disk after purging the related kernel. This can cause /boot to become full, and when it gets really bad, even sudo apt-get autoremove won't fix the problem - only deleting the old-dkms files manually solves the problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1791959/+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 1791193] Re: errores dmesg
Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem? Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.19 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19-rc3 ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1791193 Title: errores dmesg Status in linux package in Ubuntu: Incomplete Bug description: HP-Pavilion-dv6-Notebook-PC:~$ dmesg | grep 'ERROR' [0.314854] acpi PNP0A08:00: _OSC failed (AE_ERROR); disabling ASPM HP-Pavilion-dv6-Notebook-PC:~$ dmesg | grep 'error' [2.210335] rtc_cmos: probe of 00:01 failed with error -16 [8.740655] EXT4-fs (sda3): re-mounted. Opts: errors=remount-ro [ 14.065747] hp_wmi: query 0xd returned error 0x5 HP-Pavilion-dv6-Notebook-PC:~$ dmesg | grep 'Error' [2.228970] RAS: Correctable Errors collector initialized. 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/controlC0: jdaniel1 2175 F pulseaudio /dev/snd/controlC1: jdaniel1 2175 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Sep 7 02:04:05 2018 HibernationDevice: RESUME=UUID=8e4040b1-92e2-4966-85b4-cd96d821b8b7 InstallationDate: Installed on 2018-06-12 (86 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Hewlett-Packard HP Pavilion dv6 Notebook PC ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic root=UUID=6386aebd-7d3c-4128-9e45-2a0adc183b79 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 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/07/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.29 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 1448 dmi.board.vendor: Hewlett-Packard dmi.board.version: 65.38 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: N/A dmi.modalias: dmi:bvnHewlett-Packard:bvrF.29:bd11/07/2011:svnHewlett-Packard:pnHPPaviliondv6NotebookPC:pvr048E10242B102:rvnHewlett-Packard:rn1448:rvr65.38:cvnHewlett-Packard:ct10:cvrN/A: dmi.product.family: 103C_5335KV dmi.product.name: HP Pavilion dv6 Notebook PC dmi.product.version: 048E10242B102 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791193/+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 1791951] Re: nvidia-settings does not work when i install propetary driver and reboot
** Description changed:
Steps (case 1):
-
1. Install propetary driver.
- 2. reboot and select wayland session.
+ 2. reboot and select Wayland session.
3. Open nvidia-settings --> "ERROR: Unable to find display on any available
system"
Steps (case 2)
+ 1. sudo prime-select intel.
+ 2. reboot and select Wayland session.
+ 3. Open nvidia-settings --> "ERROR: Unable to find display on any available
system"
+
+ Steps (case 2)
+ 1. sudo prime-select nvidia.
1. Reboot and select X11 session.
2. Open nvidia-settings. --> Not ERROR.
Steps (Case 3)
- 1. sudo prime-select intel
- 2. reboot and select X11 session
+ 1. sudo prime-select intel.
+ 2. reboot and select X11 session.
3. Open nvidia-settings --> "ERROR: NVIDIA driver is not loaded
ERROR: Unable to load info from any available system"
- This command: sudo prime-select nvidia[intel] work
+ The command: sudo prime-select nvidia[intel] work
SYSTEM INFORMATION:
Description: Ubuntu 18.04.1 LTS
Release: 18.04
nvidia-settings:
Installed: 396.54-0ubuntu0~gpu18.04.1
Candidate: 396.54-0ubuntu0~gpu18.04.1
Version table:
*** 396.54-0ubuntu0~gpu18.04.1 500
500 http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu bionic/main
amd64 Packages
100 /var/lib/dpkg/status
390.42-0ubuntu1 500
500 http://co.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
lspci -v -s 02:00
02:00.0 3D controller: NVIDIA Corporation GP108M [GeForce MX150] (rev a1)
Subsystem: Lenovo GP108M [GeForce MX150]
Flags: bus master, fast devsel, latency 0, IRQ 16
Memory at e800 (32-bit, non-prefetchable) [size=16M]
Memory at 7000 (64-bit, prefetchable) [size=256M]
Memory at 8000 (64-bit, prefetchable) [size=32M]
I/O ports at d000 [size=128]
Capabilities:
Kernel driver in use: nvidia
Kernel modules: nvidiafb, nouveau, nvidia_drm, nvidia
{
"Version": "18.04",
"OEM": {
"Vendor": "LENOVO",
},
"BIOS": {
"Vendor": "LENOVO",
},
"CPU": {
"OpMode": "32-bit, 64-bit",
"CPUs": "8",
"Threads": "2",
"Cores": "4",
"Sockets": "1",
"Vendor": "GenuineIntel",
"Family": "6",
"Model": "142",
"Stepping": "10",
"Name": "Intel(R) Core(TM) i5-8250U CPU @ 1.60GHz",
"Virtualization": "VT-x"
},
"Arch": "amd64",
"GPU": [
{
"Vendor": "8086",
"Model": "5917"
}
],
"RAM": 7.9,
"Disks": [
0
],
"Partitions": [
28.4,
0.3,
210.4
],
"Screens": [
{
"Size": "340mmx190mm",
"Resolution": "1368x768",
"Frequency": "59.71"
}
],
"Autologin": false,
"LivePatch": false,
"Session": {
"DE": "ubuntu:GNOME",
"Name": "ubuntu-wayland",
"Type": "wayland"
},
"Language": "en_US",
"Timezone": "America/Bogota",
"Install": {
"Media": "Ubuntu 18.04.1 LTS \"Bionic Beaver\" - Release amd64
(20180725)",
"Type": "GTK",
"OEM": false,
"PartitionMethod": "manual",
"DownloadUpdates": true,
"Language": "en",
"Minimal": true,
"RestrictedAddons": true,
"Stages": {
"0": "language",
"4": "console_setup",
"18": "console_setup",
"21": "wireless",
"86": "prepare",
"205": "partman",
"250": "partman",
"251": "partman",
"252": "partman",
"267": "partman",
"281": "partman",
"297": "partman",
"300": "start_install",
"314": "timezone",
"333": "usersetup",
"343": "user_done",
"800": "done"
}
}
}
Driver version: 396.54
** Description changed:
Steps (case 1):
1. Install propetary driver.
- 2. reboot and select Wayland session.
+ 2. Reboot and select Wayland session.
3. Open nvidia-settings --> "ERROR: Unable to find display on any available
system"
Steps (case 2)
1. sudo prime-select intel.
- 2. reboot and select Wayland session.
+ 2. Reboot and select Wayland session.
3. Open nvidia-settings --> "ERROR: Unable to find display on any available
system"
Steps (case 2)
1. sudo prime-select nvidia.
1. Reboot and select X11 session.
2. Open nvidia-settings. --> Not ERROR.
Steps (Case 3)
1. sudo prime-select intel.
- 2. reboot and select X11 session.
+ 2. Reboot and select X11 session.
3. Open nvidia-settings --> "ERROR: NVIDIA driver is not loaded
ERROR: Unable to load info from any available system"
The command: sudo prime-select nvidia[intel] work
SYSTEM INFORMATION:
Description: Ubuntu 18.04.1 LTS
Release: 18.04
nvidia-settings:
Installed: 396.54-0ubuntu0~gpu18.04.1
Candidate: 396.54-0ubuntu0~gpu18.04.1
Version table:
*** 396.54-0ubuntu0~gpu18.04.1 500
500 http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu bionic/main
amd64 Packages
100
[Kernel-packages] [Bug 1791959] Re: remove /boot/initrd.img-*.old-dkms files left behind
** Changed in: dkms (Ubuntu) Importance: Undecided => Medium ** Changed in: dkms (Ubuntu) Status: New => Confirmed ** Also affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Changed in: initramfs-tools (Ubuntu) Status: New => Confirmed ** Changed in: initramfs-tools (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1791959 Title: remove /boot/initrd.img-*.old-dkms files left behind Status in dkms package in Ubuntu: Invalid Status in initramfs-tools package in Ubuntu: Confirmed Bug description: [Impact] If a dkms package is installed which has REMAKE_INITRD or the same setting has been manually configured by a user then when a kernel is removed its possible for an ".old-dkms" file to be left in /boot with no associated kernel. bug 1515513 dealt with removing initrd.img-.old-dkms files using the kernel's prerm hook, but that is only executed for the kernel version being removed: any other old-dkms file generated prior to that would not be removed by the hook, taking space in the /boot directory. Note: Filling up the /boot partition causes updates to fail. [Test Case] As the fix for bug 1515513 is available on Xenial it is no longer possible to reproduce this by simply installing and updating kernels (dkms 2.2.0.3-2ubuntu11.3 would be required for that). In order to replicate it an old dkms file will be created by hand. This assumes a new Xenial schroot. 1) create a file to work as a placeholder for the initrd.img old dkms file sudo touch /boot/initrd.img-4.0.0-0-generic.old-dkms 2) install 3 old kernels, r8168-dkms, and the current initramfs-tools sudo apt-get install -y linux-image-4.4.0-21-generic linux-image-4.4.0-22-generic linux-image-4.4.0-24-generic r8168-dkms initramfs-tools=0.122ubuntu8.12 3) install the headers for the old kernels (forces dkms to run) sudo apt-get install -y linux-headers-4.4.0-21-generic linux-headers-4.4.0-22-generic linux-headers-4.4.0-24-generic 4) verify that there are 4 old-dkms, the manually created and one for each installed kernel ls /boot/*.old-dkms 5) install the initramfs-tools that contains this fix sudo apt-get install -y initramfs-tools 6) verify that the manually created old-dkms file was removed and that there are only 3 files now, one for each installed kernel ls /boot/*.old-dkms 7) autoremove the older kernel sudo apt-get autoremove -y 8) verify that there are now only 2 old-dkms, one for each installed kernel ls /boot/*.old-dkms [Regression Potential] Somebody out there might expect the .old-dkms file to be kept, but that seems like an odd expectation. One notices *.old-dkms files being left behind still sitting on the disk after purging the related kernel. This can cause /boot to become full, and when it gets really bad, even sudo apt-get autoremove won't fix the problem - only deleting the old-dkms files manually solves the problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1791959/+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 1791281] Re: Latest update (4.15.0-33) not booting, 4.15.0-23 OK
Would it be possible for you to test the proposed kernel and post back if it resolves this bug? See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Status: New => Incomplete ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => High ** Tags added: kernel-key -- 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/1791281 Title: Latest update (4.15.0-33) not booting, 4.15.0-23 OK Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Bug description: Hi, Auto update to 4.15.0-33 doesn't boot. Any ideas or do you need more info? Thanks, Tim ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.25 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Fri Sep 7 11:17:25 2018 InstallationDate: Installed on 2018-06-02 (96 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: Upgraded to bionic on 2018-06-02 (96 days ago) VarLogDistupgradeTermlog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791281/+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 1791959] Re: remove /boot/initrd.img-*.old-dkms files left behind
** Changed in: dkms (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1791959 Title: remove /boot/initrd.img-*.old-dkms files left behind Status in dkms package in Ubuntu: Invalid Status in initramfs-tools package in Ubuntu: Confirmed Bug description: [Impact] If a dkms package is installed which has REMAKE_INITRD or the same setting has been manually configured by a user then when a kernel is removed its possible for an ".old-dkms" file to be left in /boot with no associated kernel. bug 1515513 dealt with removing initrd.img-.old-dkms files using the kernel's prerm hook, but that is only executed for the kernel version being removed: any other old-dkms file generated prior to that would not be removed by the hook, taking space in the /boot directory. Note: Filling up the /boot partition causes updates to fail. [Test Case] As the fix for bug 1515513 is available on Xenial it is no longer possible to reproduce this by simply installing and updating kernels (dkms 2.2.0.3-2ubuntu11.3 would be required for that). In order to replicate it an old dkms file will be created by hand. This assumes a new Xenial schroot. 1) create a file to work as a placeholder for the initrd.img old dkms file sudo touch /boot/initrd.img-4.0.0-0-generic.old-dkms 2) install 3 old kernels, r8168-dkms, and the current initramfs-tools sudo apt-get install -y linux-image-4.4.0-21-generic linux-image-4.4.0-22-generic linux-image-4.4.0-24-generic r8168-dkms initramfs-tools=0.122ubuntu8.12 3) install the headers for the old kernels (forces dkms to run) sudo apt-get install -y linux-headers-4.4.0-21-generic linux-headers-4.4.0-22-generic linux-headers-4.4.0-24-generic 4) verify that there are 4 old-dkms, the manually created and one for each installed kernel ls /boot/*.old-dkms 5) install the initramfs-tools that contains this fix sudo apt-get install -y initramfs-tools 6) verify that the manually created old-dkms file was removed and that there are only 3 files now, one for each installed kernel ls /boot/*.old-dkms 7) autoremove the older kernel sudo apt-get autoremove -y 8) verify that there are now only 2 old-dkms, one for each installed kernel ls /boot/*.old-dkms [Regression Potential] Somebody out there might expect the .old-dkms file to be kept, but that seems like an odd expectation. One notices *.old-dkms files being left behind still sitting on the disk after purging the related kernel. This can cause /boot to become full, and when it gets really bad, even sudo apt-get autoremove won't fix the problem - only deleting the old-dkms files manually solves the problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1791959/+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 1791321] Re: No video on laptop display after suspend/resume
** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete ** Changed in: linux (Ubuntu) Status: Incomplete => Triaged ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Status: New => Triaged ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => Medium -- 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/1791321 Title: No video on laptop display after suspend/resume Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Bug description: Between linux 4.15.0-23 and 4.15.0-24, suspend/resume stopped working correctly. After resume, the laptop panel remains blank with -24 (external monitors resume correctly). Suspend/resume worked correctly with -23. Ubuntu 18.04 LTS Lenovo P50 laptop, using nouveau driver --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: john 1100 F pulseaudio /dev/snd/controlC0: john 1100 F pulseaudio DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=1114cee9-db59-4a6e-a257-06ed1131a72b InstallationDate: Installed on 2017-02-01 (586 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: LENOVO 20EN001AUS Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic root=UUID=cd371ad3-bcc5-4389-b0b7-910bd49727c5 ro quiet ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-23-generic N/A linux-backports-modules-4.15.0-23-generic N/A linux-firmware 1.173.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux 4.15.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark _MarkForUpload: True dmi.bios.date: 03/28/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N1EET77W (1.50 ) dmi.board.asset.tag: Not Available dmi.board.name: 20EN001AUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1EET77W(1.50):bd03/28/2018:svnLENOVO:pn20EN001AUS:pvrThinkPadP50:rvnLENOVO:rn20EN001AUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P50 dmi.product.name: 20EN001AUS dmi.product.version: ThinkPad P50 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791321/+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 1791147] [NEW] package linux-modules-extra-4.15.0-33-generic (not installed) failed to install/upgrade: no package named 'linux-modules-extra-4.15.0-33-generic' is installed, ca
You have been subscribed to a public bug: not able to fix this . update is available but not able to update the ubantu ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-modules-extra-4.15.0-33-generic (not installed) ProcVersionSignature: Ubuntu 4.15.0-32.35~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Fri Sep 7 00:05:35 2018 ErrorMessage: no package named 'linux-modules-extra-4.15.0-33-generic' is installed, cannot configure InstallationDate: Installed on 2018-08-13 (24 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.27 SourcePackage: linux-hwe Title: package linux-modules-extra-4.15.0-33-generic (not installed) failed to install/upgrade: no package named 'linux-modules-extra-4.15.0-33-generic' is installed, cannot configure UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- package linux-modules-extra-4.15.0-33-generic (not installed) failed to install/upgrade: no package named 'linux-modules-extra-4.15.0-33-generic' is installed, cannot configure https://bugs.launchpad.net/bugs/1791147 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1791959] Re: remove /boot/initrd.img-*.old-dkms files left behind
** Description changed: [Impact] - If a dkms package is installed which has REMAKE_INITRD or the same setting has be manually configured by a user then when a kernel is removed its possible for an ".old-dkms" file to be left in /boot with no associated kernel. + If a dkms package is installed which has REMAKE_INITRD or the same setting has been manually configured by a user then when a kernel is removed its possible for an ".old-dkms" file to be left in /boot with no associated kernel. bug 1515513 dealt with removing initrd.img-.old-dkms files using the kernel's prerm hook, but that is only executed for the kernel version being removed: any other old-dkms file generated prior to that would not be removed by the hook, taking space in the /boot directory. Note: Filling up the /boot partition causes updates to fail. [Test Case] As the fix for bug 1515513 is available on Xenial it is no longer possible to reproduce this by simply installing and updating kernels (dkms 2.2.0.3-2ubuntu11.3 would be required for that). In order to replicate it an old dkms file will be created by hand. This assumes a new Xenial schroot. 1) create a file to work as a placeholder for the initrd.img old dkms file sudo touch /boot/initrd.img-4.0.0-0-generic.old-dkms 2) install 3 old kernels, r8168-dkms, and the current initramfs-tools sudo apt-get install -y linux-image-4.4.0-21-generic linux-image-4.4.0-22-generic linux-image-4.4.0-24-generic r8168-dkms initramfs-tools=0.122ubuntu8.12 3) install the headers for the old kernels (forces dkms to run) sudo apt-get install -y linux-headers-4.4.0-21-generic linux-headers-4.4.0-22-generic linux-headers-4.4.0-24-generic 4) verify that there are 4 old-dkms, the manually created and one for each installed kernel ls /boot/*.old-dkms 5) install the initramfs-tools that contains this fix sudo apt-get install -y initramfs-tools 6) verify that the manually created old-dkms file was removed and that there are only 3 files now, one for each installed kernel ls /boot/*.old-dkms 7) autoremove the older kernel sudo apt-get autoremove -y 8) verify that there are now only 2 old-dkms, one for each installed kernel ls /boot/*.old-dkms [Regression Potential] Somebody out there might expect the .old-dkms file to be kept, but that seems like an odd expectation. One notices *.old-dkms files being left behind still sitting on the disk after purging the related kernel. This can cause /boot to become full, and when it gets really bad, even sudo apt-get autoremove won't fix the problem - only deleting the old-dkms files manually solves the problem. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1791959 Title: remove /boot/initrd.img-*.old-dkms files left behind Status in dkms package in Ubuntu: Invalid Status in initramfs-tools package in Ubuntu: Confirmed Bug description: [Impact] If a dkms package is installed which has REMAKE_INITRD or the same setting has been manually configured by a user then when a kernel is removed its possible for an ".old-dkms" file to be left in /boot with no associated kernel. bug 1515513 dealt with removing initrd.img-.old-dkms files using the kernel's prerm hook, but that is only executed for the kernel version being removed: any other old-dkms file generated prior to that would not be removed by the hook, taking space in the /boot directory. Note: Filling up the /boot partition causes updates to fail. [Test Case] As the fix for bug 1515513 is available on Xenial it is no longer possible to reproduce this by simply installing and updating kernels (dkms 2.2.0.3-2ubuntu11.3 would be required for that). In order to replicate it an old dkms file will be created by hand. This assumes a new Xenial schroot. 1) create a file to work as a placeholder for the initrd.img old dkms file sudo touch /boot/initrd.img-4.0.0-0-generic.old-dkms 2) install 3 old kernels, r8168-dkms, and the current initramfs-tools sudo apt-get install -y linux-image-4.4.0-21-generic linux-image-4.4.0-22-generic linux-image-4.4.0-24-generic r8168-dkms initramfs-tools=0.122ubuntu8.12 3) install the headers for the old kernels (forces dkms to run) sudo apt-get install -y linux-headers-4.4.0-21-generic linux-headers-4.4.0-22-generic linux-headers-4.4.0-24-generic 4) verify that there are 4 old-dkms, the manually created and one for each installed kernel ls /boot/*.old-dkms 5) install the initramfs-tools that contains this fix sudo apt-get install -y initramfs-tools 6) verify that the manually created old-dkms file was removed and that there are only 3 files now, one for each installed kernel ls /boot/*.old-dkms 7) autoremove the older kernel sudo apt-get autoremove -y 8) verify that there are now only 2 old-dkms, one for
[Kernel-packages] [Bug 1791959] Re: remove /boot/initrd.img-*.old-dkms files left behind
** Description changed: [Impact] If a dkms package is installed which has REMAKE_INITRD or the same setting has be manually configured by a user then when a kernel is removed its possible for an ".old-dkms" file to be left in /boot with no associated kernel. bug 1515513 dealt with removing initrd.img-.old-dkms files using the kernel's prerm hook, but that is only executed for the kernel version being removed: any other old-dkms file generated prior to that would not be removed by the hook, taking space in the /boot directory. Note: Filling up the /boot partition causes updates to fail. - [Test Case] As the fix for bug 1515513 is available on Xenial it is no longer possible to reproduce this by simply installing and updating kernels (dkms 2.2.0.3-2ubuntu11.3 would be required for that). In order to replicate it an old dkms file will be created by hand. This assumes a new Xenial schroot. 1) create a file to work as a placeholder for the initrd.img old dkms file sudo touch /boot/initrd.img-4.0.0-0-generic.old-dkms 2) install 3 old kernels, r8168-dkms, and the current initramfs-tools sudo apt-get install -y linux-image-4.4.0-21-generic linux-image-4.4.0-22-generic linux-image-4.4.0-24-generic r8168-dkms initramfs-tools=0.122ubuntu8.12 3) install the headers for the old kernels (forces dkms to run) sudo apt-get install -y linux-headers-4.4.0-21-generic linux-headers-4.4.0-22-generic linux-headers-4.4.0-24-generic - 4) verify that there are 4 old-dkms + 4) verify that there are 4 old-dkms, the manually created and one for each installed kernel ls /boot/*.old-dkms - 5) install the proposed initramfs-tools with this fix + 5) install the initramfs-tools that contains this fix sudo apt-get install -y initramfs-tools - 6) verify that the manually created old-dkms file was removed (only 3 files now) + 6) verify that the manually created old-dkms file was removed and that there are only 3 files now, one for each installed kernel ls /boot/*.old-dkms 7) autoremove the older kernel sudo apt-get autoremove -y - 8) verify that there are now only 2 old-dkms + 8) verify that there are now only 2 old-dkms, one for each installed kernel ls /boot/*.old-dkms - [Regression Potential] Somebody out there might expect the .old-dkms file to be kept, but that seems like an odd expectation. One notices *.old-dkms files being left behind still sitting on the disk after purging the related kernel. This can cause /boot to become full, and when it gets really bad, even sudo apt-get autoremove won't fix the problem - only deleting the old-dkms files manually solves the problem. ** Tags added: xenial ** Tags added: patch ** Patch added: "initramfs-tools_0.122ubuntu8.12_debdiff_0.122ubuntu8.13.patch" https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1791959/+attachment/5187601/+files/initramfs-tools_0.122ubuntu8.12_debdiff_0.122ubuntu8.13.patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1791959 Title: remove /boot/initrd.img-*.old-dkms files left behind Status in dkms package in Ubuntu: Confirmed Bug description: [Impact] If a dkms package is installed which has REMAKE_INITRD or the same setting has be manually configured by a user then when a kernel is removed its possible for an ".old-dkms" file to be left in /boot with no associated kernel. bug 1515513 dealt with removing initrd.img-.old-dkms files using the kernel's prerm hook, but that is only executed for the kernel version being removed: any other old-dkms file generated prior to that would not be removed by the hook, taking space in the /boot directory. Note: Filling up the /boot partition causes updates to fail. [Test Case] As the fix for bug 1515513 is available on Xenial it is no longer possible to reproduce this by simply installing and updating kernels (dkms 2.2.0.3-2ubuntu11.3 would be required for that). In order to replicate it an old dkms file will be created by hand. This assumes a new Xenial schroot. 1) create a file to work as a placeholder for the initrd.img old dkms file sudo touch /boot/initrd.img-4.0.0-0-generic.old-dkms 2) install 3 old kernels, r8168-dkms, and the current initramfs-tools sudo apt-get install -y linux-image-4.4.0-21-generic linux-image-4.4.0-22-generic linux-image-4.4.0-24-generic r8168-dkms initramfs-tools=0.122ubuntu8.12 3) install the headers for the old kernels (forces dkms to run) sudo apt-get install -y linux-headers-4.4.0-21-generic linux-headers-4.4.0-22-generic linux-headers-4.4.0-24-generic 4) verify that there are 4 old-dkms, the manually created and one for each installed kernel ls /boot/*.old-dkms 5) install the initramfs-tools that contains this fix sudo apt-get install -y initramfs-tools 6) verify that the manually created old-dkms file
[Kernel-packages] [Bug 1772624] Re: Broadcom BCM4356 wifi chipset firmware is not working
@orestis-8 Did you try the previous ubuntu package or the newest files from the official linux-firmware git repo ? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1772624 Title: Broadcom BCM4356 wifi chipset firmware is not working Status in linux-firmware package in Ubuntu: Confirmed Bug description: Hello, After upgrading to Ubuntu 18.04 I got an issue with the wifi chipset (Broadcom BCM4356) not initializing properly. Here is the error I got when loading the driver brcmfmac: ``` [ 8189.092819] brcmfmac: brcmf_fw_map_chip_to_name: using brcm/brcmfmac4356-pcie.bin for chip 0x004356(17238) rev 0x02 [ 8189.093100] brcmfmac :04:00.0: Direct firmware load for brcm/brcmfmac4356-pcie.txt failed with error -2 [ 8191.568544] brcmfmac: brcmf_msgbuf_query_dcmd: Timeout on response for query command [ 8191.568562] brcmfmac: brcmf_c_preinit_dcmds: Retreiving cur_etheraddr failed, -5 [ 8191.568570] brcmfmac: brcmf_bus_started: failed: -5 [ 8191.568588] brcmfmac: brcmf_pcie_attach_bus: dongle is not responding ``` As seen here https://answers.launchpad.net/ubuntu/+question/668329, I reverted to the previous linux-firmware version and then the wifi chipset is working: Previous firmware package: https://packages.ubuntu.com/artful-updates /linux-firmware ``` [10087.698214] brcmfmac: brcmf_fw_map_chip_to_name: using brcm/brcmfmac4356-pcie.bin for chip 0x004356(17238) rev 0x02 [10087.698634] brcmfmac :04:00.0: Direct firmware load for brcm/brcmfmac4356-pcie.txt failed with error -2 [10088.104176] brcmfmac :04:00.0: Direct firmware load for brcm/brcmfmac4356-pcie.clm_blob failed with error -2 [10088.104186] brcmfmac: brcmf_c_process_clm_blob: no clm_blob available(err=-2), device may have limited channels available [10088.105170] brcmfmac: brcmf_c_preinit_dcmds: Firmware version = wl0: Oct 22 2015 06:16:41 version 7.35.180.119 (r594535) FWID 01-1a5c4016 [10088.179872] brcmfmac :04:00.0 wlp4s0: renamed from wlan0 ``` The problem seems to have been reported to the linux-wireless mailing list but no fix has been committed apparently : https://www.spinics.net/lists/linux-wireless/msg168687.html System information: Description: Ubuntu 18.04 LTS Release: 18.04 linux-image-4.15.0-20-generic: Installé : 4.15.0-20.21 Candidat : 4.15.0-20.21 Table de version : *** 4.15.0-20.21 500 500 http://fr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status linux-firmware: Installé : 1.173 Candidat : 1.173 Table de version : *** 1.173 500 500 http://fr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 500 http://fr.archive.ubuntu.com/ubuntu bionic/main i386 Packages 100 /var/lib/dpkg/status Regards, Jean Pierre. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1772624/+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 1791959] [NEW] remove /boot/initrd.img-*.old-dkms files left behind
Public bug reported: [Impact] If a dkms package is installed which has REMAKE_INITRD or the same setting has be manually configured by a user then when a kernel is removed its possible for an ".old-dkms" file to be left in /boot with no associated kernel. bug 1515513 dealt with removing initrd.img-.old-dkms files using the kernel's prerm hook, but that is only executed for the kernel version being removed: any other old-dkms file generated prior to that would not be removed by the hook, taking space in the /boot directory. Note: Filling up the /boot partition causes updates to fail. [Test Case] As the fix for bug 1515513 is available on Xenial it is no longer possible to reproduce this by simply installing and updating kernels (dkms 2.2.0.3-2ubuntu11.3 would be required for that). In order to replicate it an old dkms file will be created by hand. This assumes a new Xenial schroot. 1) create a file to work as a placeholder for the initrd.img old dkms file sudo touch /boot/initrd.img-4.0.0-0-generic.old-dkms 2) install 3 old kernels, r8168-dkms, and the current initramfs-tools sudo apt-get install -y linux-image-4.4.0-21-generic linux-image-4.4.0-22-generic linux-image-4.4.0-24-generic r8168-dkms initramfs-tools=0.122ubuntu8.12 3) install the headers for the old kernels (forces dkms to run) sudo apt-get install -y linux-headers-4.4.0-21-generic linux-headers-4.4.0-22-generic linux-headers-4.4.0-24-generic 4) verify that there are 4 old-dkms, the manually created and one for each installed kernel ls /boot/*.old-dkms 5) install the initramfs-tools that contains this fix sudo apt-get install -y initramfs-tools 6) verify that the manually created old-dkms file was removed and that there are only 3 files now, one for each installed kernel ls /boot/*.old-dkms 7) autoremove the older kernel sudo apt-get autoremove -y 8) verify that there are now only 2 old-dkms, one for each installed kernel ls /boot/*.old-dkms [Regression Potential] Somebody out there might expect the .old-dkms file to be kept, but that seems like an odd expectation. One notices *.old-dkms files being left behind still sitting on the disk after purging the related kernel. This can cause /boot to become full, and when it gets really bad, even sudo apt-get autoremove won't fix the problem - only deleting the old-dkms files manually solves the problem. ** Affects: dkms (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1791959 Title: remove /boot/initrd.img-*.old-dkms files left behind Status in dkms package in Ubuntu: New Bug description: [Impact] If a dkms package is installed which has REMAKE_INITRD or the same setting has be manually configured by a user then when a kernel is removed its possible for an ".old-dkms" file to be left in /boot with no associated kernel. bug 1515513 dealt with removing initrd.img-.old-dkms files using the kernel's prerm hook, but that is only executed for the kernel version being removed: any other old-dkms file generated prior to that would not be removed by the hook, taking space in the /boot directory. Note: Filling up the /boot partition causes updates to fail. [Test Case] As the fix for bug 1515513 is available on Xenial it is no longer possible to reproduce this by simply installing and updating kernels (dkms 2.2.0.3-2ubuntu11.3 would be required for that). In order to replicate it an old dkms file will be created by hand. This assumes a new Xenial schroot. 1) create a file to work as a placeholder for the initrd.img old dkms file sudo touch /boot/initrd.img-4.0.0-0-generic.old-dkms 2) install 3 old kernels, r8168-dkms, and the current initramfs-tools sudo apt-get install -y linux-image-4.4.0-21-generic linux-image-4.4.0-22-generic linux-image-4.4.0-24-generic r8168-dkms initramfs-tools=0.122ubuntu8.12 3) install the headers for the old kernels (forces dkms to run) sudo apt-get install -y linux-headers-4.4.0-21-generic linux-headers-4.4.0-22-generic linux-headers-4.4.0-24-generic 4) verify that there are 4 old-dkms, the manually created and one for each installed kernel ls /boot/*.old-dkms 5) install the initramfs-tools that contains this fix sudo apt-get install -y initramfs-tools 6) verify that the manually created old-dkms file was removed and that there are only 3 files now, one for each installed kernel ls /boot/*.old-dkms 7) autoremove the older kernel sudo apt-get autoremove -y 8) verify that there are now only 2 old-dkms, one for each installed kernel ls /boot/*.old-dkms [Regression Potential] Somebody out there might expect the .old-dkms file to be kept, but that seems like an odd expectation. One notices *.old-dkms files being left behind still sitting on the disk after purging the related kernel. This can cause /boot to
[Kernel-packages] [Bug 1790096] Re: PTP no longuer working on igb since 4.15.0-33
Looking a the code, igb driver is untouched between -32 and -34. looking network, timekeeping and x86 timer code is needed. -- 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/1790096 Title: PTP no longuer working on igb since 4.15.0-33 Status in linux package in Ubuntu: Incomplete Bug description: ptp4l is no longer able to sync the PHC of a i350 (igb driver) since 4.15.0-33-generic. 4.15.0-32-generic work. It no longer reach the slave state and is stuck to UNCALIBRATED: Aug 31 10:03:29 ptp4l[1259]: [79.208] [0:enp7s0f1] port 1: link up Aug 31 10:03:29 ptp4l[1259]: [79.260] [0:enp7s0f1] port 1: FAULTY to LISTENING on INIT_COMPLETE Aug 31 10:03:30 ptp4l[1259]: [80.814] [0:enp7s0f1] port 1: new foreign master ec4670.fffe.009fc5-1 Aug 31 10:03:34 ptp4l[1259]: [84.815] [0:enp7s0f1] selected best master clock ec4670.fffe.009fc5 Aug 31 10:03:34 ptp4l[1259]: [84.815] [0:enp7s0f1] port 1: LISTENING to UNCALIBRATED on RS_SLAVE OR Aug 31 10:53:44 ptp4l[1259]: [3094.219] [0:enp7s0f1] timed out while polling for tx timestamp Aug 31 10:53:44 ptp4l[1259]: [3094.219] [0:enp7s0f1] increasing tx_timestamp_timeout may correct this issue, but it is likely caused by a driver bug Aug 31 10:53:44 ptp4l[1259]: [3094.219] [0:enp7s0f1] port 1: send delay request failed Aug 31 10:53:44 ptp4l[1259]: [3094.219] [0:enp7s0f1] port 1: UNCALIBRATED to FAULTY on FAULT_DETECTED (FT_UNSPECIFIED) Aug 31 10:54:00 ptp4l[1259]: [3110.292] [0:enp7s0f1] port 1: FAULTY to LISTENING on INIT_COMPLETE Aug 31 10:54:02 ptp4l[1259]: [3112.052] [0:enp7s0f1] port 1: new foreign master ec4670.fffe.009fc5-1 Aug 31 10:54:06 ptp4l[1259]: [3116.053] [0:enp7s0f1] selected best master clock ec4670.fffe.009fc5 Aug 31 10:54:06 ptp4l[1259]: [3116.053] [0:enp7s0f1] port 1: LISTENING to UNCALIBRATED on RS_SLAVE On 4.15.0-32-generic: Aug 31 09:52:27 ptp4l[2392]: [654.860] [0:enp7s0f1] port 1: new foreign master ec4670.fffe.009fc5-1 Aug 31 09:52:31 ptp4l[2392]: [658.861] [0:enp7s0f1] selected best master clock ec4670.fffe.009fc5 Aug 31 09:52:31 ptp4l[2392]: [658.861] [0:enp7s0f1] port 1: LISTENING to UNCALIBRATED on RS_SLAVE Aug 31 09:52:33 ptp4l[2392]: [660.737] [0:enp7s0f1] port 1: minimum delay request interval 2^1 Aug 31 09:52:34 ptp4l[2392]: [662.037] [0:enp7s0f1] port 1: UNCALIBRATED to SLAVE on MASTER_CLOCK_SELECTED I don't know if it is a driver change or a network/timekeeping change or other that is the root cause of this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1790096/+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 1791953] Re: Xenial update to 4.4.146 stable release
Modified: * "perf/x86/intel/uncore: Correct fixed counter index check in generic code" -> needed path adjusted -> arch/x86/events/intel * "perf/x86/intel/uncore: Correct fixed counter index check for NHM" -> same path adjustment -- 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/1791953 Title: Xenial update to 4.4.146 stable release Status in linux package in Ubuntu: New Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The 4.4.146 upstream stable patch set is now available. It should be included in the Ubuntu kernel as well. git://git.kernel.org/ TEST CASE: TBD The following patches from the 4.4.146 stable release shall be applied: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791953/+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 1791953] [NEW] Xenial update to 4.4.146 stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The 4.4.146 upstream stable patch set is now available. It should be included in the Ubuntu kernel as well. git://git.kernel.org/ TEST CASE: TBD The following patches from the 4.4.146 stable release shall be applied: ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: kernel-stable-tracking-bug ** Tags added: kernel-stable-tracking-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/1791953 Title: Xenial update to 4.4.146 stable release Status in linux package in Ubuntu: New Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The 4.4.146 upstream stable patch set is now available. It should be included in the Ubuntu kernel as well. git://git.kernel.org/ TEST CASE: TBD The following patches from the 4.4.146 stable release shall be applied: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791953/+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 1783140] Re: KVM live migration fails
PPA prepared at: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3412 MP: https://code.launchpad.net/~paelzer/ubuntu/+source/qemu/+git/qemu/+merge/354695 Test of the case on the PPA is successful. But I'll need a regression check on that before going on. ** Changed in: qemu (Ubuntu) Status: Incomplete => Triaged -- 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/1783140 Title: KVM live migration fails Status in The Ubuntu-power-systems project: In Progress Status in linux package in Ubuntu: Triaged Status in qemu package in Ubuntu: Triaged Bug description: Environment: 2 POWER8 with Ubuntu 16.04.4 LTS as KVM hypervisor. 1 KVM guest with Ubuntu 18.04 LTS. Virtual disk for the guest is a qcow2 file on an NFS share, accessible from both hypervisors, so live migration is possible and works for all other guests (SLES, RHEL, Ubunutu 16.04), Live migratino of Ubuntu 18.04 guest fails on ppc, while the same test on an x86_64 environment suceeds. root@pkvm2:~# virsh migrate --persistent --live p8lnxtst4 qemu+ssh://pkvm1/system error: internal error: early end of file from monitor, possible problem: 2018-07-23T11:12:25.586385Z qemu-system-ppc64: VQ 0 size 0x100 Guest index 0x38aa inconsistent with Host index 0xa980: delta 0x8f2a 2018-07-23T11:12:25.586434Z qemu-system-ppc64: error while loading state for instance 0x0 of device 'pci@8002000:01.0/virtio-net' 2018-07-23T11:12:25.587246Z qemu-system-ppc64: load of migration failed: Operation not permitted root@pkvm2:~# uname -a Linux pkvm2 4.4.0-130-generic #156-Ubuntu SMP Thu Jun 14 08:51:21 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1783140/+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 1791951] Re: nvidia-settings does not work when i install propetary driver and reboot
** Description changed:
When reboot my system and try open nvidia-settings, this message arise
"ERROR: Unable to find display on any available system"
+
+ Over Wayland and X11.
SYSTEM INFORMATION:
Description: Ubuntu 18.04.1 LTS
Release: 18.04
nvidia-settings:
Installed: 396.54-0ubuntu0~gpu18.04.1
Candidate: 396.54-0ubuntu0~gpu18.04.1
Version table:
*** 396.54-0ubuntu0~gpu18.04.1 500
500 http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu bionic/main
amd64 Packages
100 /var/lib/dpkg/status
390.42-0ubuntu1 500
500 http://co.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
lspci -v -s 02:00
02:00.0 3D controller: NVIDIA Corporation GP108M [GeForce MX150] (rev a1)
Subsystem: Lenovo GP108M [GeForce MX150]
Flags: bus master, fast devsel, latency 0, IRQ 16
Memory at e800 (32-bit, non-prefetchable) [size=16M]
Memory at 7000 (64-bit, prefetchable) [size=256M]
Memory at 8000 (64-bit, prefetchable) [size=32M]
I/O ports at d000 [size=128]
Capabilities:
Kernel driver in use: nvidia
Kernel modules: nvidiafb, nouveau, nvidia_drm, nvidia
{
"Version": "18.04",
"OEM": {
"Vendor": "LENOVO",
},
"BIOS": {
"Vendor": "LENOVO",
},
"CPU": {
"OpMode": "32-bit, 64-bit",
"CPUs": "8",
"Threads": "2",
"Cores": "4",
"Sockets": "1",
"Vendor": "GenuineIntel",
"Family": "6",
"Model": "142",
"Stepping": "10",
"Name": "Intel(R) Core(TM) i5-8250U CPU @ 1.60GHz",
"Virtualization": "VT-x"
},
"Arch": "amd64",
"GPU": [
{
"Vendor": "8086",
"Model": "5917"
}
],
"RAM": 7.9,
"Disks": [
0
],
"Partitions": [
28.4,
0.3,
210.4
],
"Screens": [
{
"Size": "340mmx190mm",
"Resolution": "1368x768",
"Frequency": "59.71"
}
],
"Autologin": false,
"LivePatch": false,
"Session": {
"DE": "ubuntu:GNOME",
"Name": "ubuntu-wayland",
"Type": "wayland"
},
"Language": "en_US",
"Timezone": "America/Bogota",
"Install": {
"Media": "Ubuntu 18.04.1 LTS \"Bionic Beaver\" - Release amd64
(20180725)",
"Type": "GTK",
"OEM": false,
"PartitionMethod": "manual",
"DownloadUpdates": true,
"Language": "en",
"Minimal": true,
"RestrictedAddons": true,
"Stages": {
"0": "language",
"4": "console_setup",
"18": "console_setup",
"21": "wireless",
"86": "prepare",
"205": "partman",
"250": "partman",
"251": "partman",
"252": "partman",
"267": "partman",
"281": "partman",
"297": "partman",
"300": "start_install",
"314": "timezone",
"333": "usersetup",
"343": "user_done",
"800": "done"
}
}
}
Driver version: 396.54
** Description changed:
When reboot my system and try open nvidia-settings, this message arise
- "ERROR: Unable to find display on any available system"
+ "ERROR: Unable to find display on any available system" (wayland session
+ with nvidia selected)
- Over Wayland and X11.
+ "ERROR: NVIDIA driver is not loaded
+ ERROR: Unable to load info from any available system" (X11 session with intel
selected)
+
+ This command: sudo prime-select nvidia[intel] work
SYSTEM INFORMATION:
Description: Ubuntu 18.04.1 LTS
Release: 18.04
nvidia-settings:
Installed: 396.54-0ubuntu0~gpu18.04.1
Candidate: 396.54-0ubuntu0~gpu18.04.1
Version table:
*** 396.54-0ubuntu0~gpu18.04.1 500
500 http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu bionic/main
amd64 Packages
100 /var/lib/dpkg/status
390.42-0ubuntu1 500
500 http://co.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
lspci -v -s 02:00
02:00.0 3D controller: NVIDIA Corporation GP108M [GeForce MX150] (rev a1)
Subsystem: Lenovo GP108M [GeForce MX150]
Flags: bus master, fast devsel, latency 0, IRQ 16
Memory at e800 (32-bit, non-prefetchable) [size=16M]
Memory at 7000 (64-bit, prefetchable) [size=256M]
Memory at 8000 (64-bit, prefetchable) [size=32M]
I/O ports at d000 [size=128]
Capabilities:
Kernel driver in use: nvidia
Kernel modules: nvidiafb, nouveau, nvidia_drm, nvidia
{
"Version": "18.04",
"OEM": {
"Vendor": "LENOVO",
},
"BIOS": {
"Vendor": "LENOVO",
},
"CPU": {
"OpMode": "32-bit, 64-bit",
"CPUs": "8",
"Threads": "2",
"Cores": "4",
"Sockets": "1",
"Vendor": "GenuineIntel",
"Family": "6",
"Model": "142",
"Stepping": "10",
"Name": "Intel(R) Core(TM) i5-8250U CPU @ 1.60GHz",
"Virtualization": "VT-x"
},
"Arch": "amd64",
"GPU": [
{
"Vendor": "8086",
"Model": "5917"
[Kernel-packages] [Bug 1783110] Re: >= linux-4.4.0-130: 14 bytes memory leaked when sending AF_PACKET / SOCK_RAW frames
** Changed in: linux (Ubuntu Bionic) Status: Fix Committed => Fix Released ** Changed in: linux (Ubuntu Xenial) Status: Fix Committed => Fix Released ** Changed in: linux (Ubuntu) Status: Fix Committed => 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/1783110 Title: >= linux-4.4.0-130: 14 bytes memory leaked when sending AF_PACKET / SOCK_RAW frames Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Bug description: Vulnerable: linux-image-4.4.0-130-generic, linux-image-4.4.0-131-generic Not vulnerable: linux-image-4.4.0-128-generic Bug (likely) introduced by commit: https://github.com/torvalds/linux/commit/b84bbaf7a6c8cca24f8acf25a2c8e46913a947ba Likely fixed upstream with (NOT VERIFIED): https://github.com/torvalds/linux/commit/9aad13b087ab0a588cd68259de618f100053360e Discussion about these commits on maillist, including someone referring to this bug: https://www.mail-archive.com/search?l=net...@vger.kernel.org=subject:%22Re%5C%3A+%5C%5BPATCH+net%5C%5D+packet%5C%3A+in+packet_snd+start+writing+at+link+layer+allocation%22=newest=1 When sending packets with AF_PACKET / SOCK_RAW, the actual transmitted packet contains 14 additional bytes at the end of the payload. Observations do show non-zero bytes getting leaked. See attached source for a simple proof of concept that sends a raw packet on the loopback interface. The payload should be 40 bytes of 0xAA, but tcpdump clearly shows 14 additional bytes are added. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1783110/+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 1777242] Re: 4.15.0-23-generic fails to boot in qemu on amd64 host (kernel panic)
** Changed in: linux (Ubuntu) Status: Fix Committed => Fix Released ** Changed in: linux (Ubuntu Bionic) Status: Fix Committed => 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/1777242 Title: 4.15.0-23-generic fails to boot in qemu on amd64 host (kernel panic) Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Bug description: Trying to boot bionic with 4.15.0-23-generic fails with a kernel panic in qemu on an Debian amd64 host. The version of qemu is the current in Debian Testing: 2.12+dfsg-3. Booting with 4.15.0-22-generic works fine. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: zouzou 1274 F pulseaudio CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2017-07-12 (338 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170710) IwConfig: lono wireless extensions. ens3 no wireless extensions. MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux-signed (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 qxldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=26da642a-bbc4-440b-bed3-a911bbbfe582 ro quiet splash ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-22-generic N/A linux-backports-modules-4.15.0-22-generic N/A linux-firmware 1.173.1 RfKill: Tags: bionic Uname: Linux 4.15.0-22-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-02-07 (128 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.11.1-1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-2.8 dmi.modalias: dmi:bvnSeaBIOS:bvr1.11.1-1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.8:cvnQEMU:ct1:cvrpc-i440fx-2.8: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-2.8 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777242/+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 1776005] Re: kernel instability with BTRFS filesystem as rootfs
** Changed in: linux (Ubuntu Xenial) Status: In Progress => Incomplete ** Changed in: linux (Ubuntu) Status: In Progress => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1776005 Title: kernel instability with BTRFS filesystem as rootfs Status in linux package in Ubuntu: Incomplete Status in linux source package in Xenial: Incomplete Bug description: Hello, As explained yesterday on #ubuntu-kernel, several laptop won't boot (kernel panic) with the latest kernel 4.4.0-127-generic (x86_64) and upper (proposed 4.4.0-128-generic), on Xenial 16.04 LTS I have made many tests to verify that the bootloader (GRUB) is correctly configured (I have also reinstall it, but same result). I have also verified the BTRFS system is clean and not corrupted (with a livecd). The behavior is unpredictable, because often the kernel fall in "panic" during boot, but not all the time, if i do several consecutive reboot to test stability of the boot "process". I have no search behavior with previous kernels (like 4.4.0-124-generic). I suspect (even if I'm quiet disturbed by this behavior, maybe I wrong) that something I changed on last kernel: - on BTRFS subsystem, I have "aggregate" BTRFS partitions as rootfs (for a long time) - something related with the last mitigation about the recent security processor breach But my skills stop here, and I'm not able to find the origin of this behavior despite my efforts. I can continue my investigation if I have some additional pointers. Thanks for your time, Sylvain To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776005/+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 1778475] Re: i40e: restore workaround for removing default MAC filter
** Changed in: linux (Ubuntu Bionic) Status: Triaged => Incomplete ** Changed in: linux (Ubuntu) Status: Triaged => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1778475 Title: i40e: restore workaround for removing default MAC filter Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Bug description: Ubuntu Bionic kernel (4.15.0-23) lacks upstream patch for i40e which results in forced promiscous mode when adding a vlan. [ 10.847381] i40e :3d:00.0: Error I40E_AQ_RC_EINVAL adding RX filters on PF, promiscuous mode forced on Steps to reproduce and patch here: https://patchwork.ozlabs.org/patch/692499/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1778475/+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 1770423] Re: Please cherry-pick upstream patch for HDMI on Dell XPS 9360
** Changed in: linux (Ubuntu Xenial) Status: In Progress => Incomplete ** Changed in: linux (Ubuntu) Status: In Progress => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1770423 Title: Please cherry-pick upstream patch for HDMI on Dell XPS 9360 Status in linux package in Ubuntu: Incomplete Status in linux source package in Xenial: Incomplete Bug description: Connecting the Dell USB-C HDMI/LAN/VGA/USB adapter to my XPS 9360 doesn’t quite work: I could not get my monitor to display a picture at all, regardless of which resolution I tried. A quick search on the internet revealed this patch: https://lists.freedesktop.org/archives/intel- gfx/2017-March/124077.html. Applying it to the 4.4.0-122 kernel does indeed make the HDMI work Could you please cherry-pick this patch into the Ubuntu kernel? Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1770423/+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 1791951] [NEW] nvidia-settings does not work when i install propetary driver and reboot
Public bug reported:
When reboot my system and try open nvidia-settings, this message arise
"ERROR: Unable to find display on any available system"
SYSTEM INFORMATION:
Description:Ubuntu 18.04.1 LTS
Release:18.04
nvidia-settings:
Installed: 396.54-0ubuntu0~gpu18.04.1
Candidate: 396.54-0ubuntu0~gpu18.04.1
Version table:
*** 396.54-0ubuntu0~gpu18.04.1 500
500 http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu bionic/main
amd64 Packages
100 /var/lib/dpkg/status
390.42-0ubuntu1 500
500 http://co.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
lspci -v -s 02:00
02:00.0 3D controller: NVIDIA Corporation GP108M [GeForce MX150] (rev a1)
Subsystem: Lenovo GP108M [GeForce MX150]
Flags: bus master, fast devsel, latency 0, IRQ 16
Memory at e800 (32-bit, non-prefetchable) [size=16M]
Memory at 7000 (64-bit, prefetchable) [size=256M]
Memory at 8000 (64-bit, prefetchable) [size=32M]
I/O ports at d000 [size=128]
Capabilities:
Kernel driver in use: nvidia
Kernel modules: nvidiafb, nouveau, nvidia_drm, nvidia
{
"Version": "18.04",
"OEM": {
"Vendor": "LENOVO",
},
"BIOS": {
"Vendor": "LENOVO",
},
"CPU": {
"OpMode": "32-bit, 64-bit",
"CPUs": "8",
"Threads": "2",
"Cores": "4",
"Sockets": "1",
"Vendor": "GenuineIntel",
"Family": "6",
"Model": "142",
"Stepping": "10",
"Name": "Intel(R) Core(TM) i5-8250U CPU @ 1.60GHz",
"Virtualization": "VT-x"
},
"Arch": "amd64",
"GPU": [
{
"Vendor": "8086",
"Model": "5917"
}
],
"RAM": 7.9,
"Disks": [
0
],
"Partitions": [
28.4,
0.3,
210.4
],
"Screens": [
{
"Size": "340mmx190mm",
"Resolution": "1368x768",
"Frequency": "59.71"
}
],
"Autologin": false,
"LivePatch": false,
"Session": {
"DE": "ubuntu:GNOME",
"Name": "ubuntu-wayland",
"Type": "wayland"
},
"Language": "en_US",
"Timezone": "America/Bogota",
"Install": {
"Media": "Ubuntu 18.04.1 LTS \"Bionic Beaver\" - Release amd64 (20180725)",
"Type": "GTK",
"OEM": false,
"PartitionMethod": "manual",
"DownloadUpdates": true,
"Language": "en",
"Minimal": true,
"RestrictedAddons": true,
"Stages": {
"0": "language",
"4": "console_setup",
"18": "console_setup",
"21": "wireless",
"86": "prepare",
"205": "partman",
"250": "partman",
"251": "partman",
"252": "partman",
"267": "partman",
"281": "partman",
"297": "partman",
"300": "start_install",
"314": "timezone",
"333": "usersetup",
"343": "user_done",
"800": "done"
}
}
}
Driver version: 396.54
** Affects: nvidia-settings (Ubuntu)
Importance: Undecided
Status: New
** Package changed: nvidia-graphics-drivers-340 (Ubuntu) => nvidia-
settings (Ubuntu)
** Description changed:
When reboot my system and try open nvidia-settings, this message arise
"ERROR: Unable to find display on any available system"
- System information:
+ SYSTEM INFORMATION:
+
Description: Ubuntu 18.04.1 LTS
Release: 18.04
nvidia-settings:
- Installed: 396.54-0ubuntu0~gpu18.04.1
- Candidate: 396.54-0ubuntu0~gpu18.04.1
- Version table:
- *** 396.54-0ubuntu0~gpu18.04.1 500
- 500 http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu bionic/main
amd64 Packages
- 100 /var/lib/dpkg/status
- 390.42-0ubuntu1 500
- 500 http://co.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
-
+ Installed: 396.54-0ubuntu0~gpu18.04.1
+ Candidate: 396.54-0ubuntu0~gpu18.04.1
+ Version table:
+ *** 396.54-0ubuntu0~gpu18.04.1 500
+ 500 http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu bionic/main
amd64 Packages
+ 100 /var/lib/dpkg/status
+ 390.42-0ubuntu1 500
+ 500 http://co.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
lspci -v -s 02:00
02:00.0 3D controller: NVIDIA Corporation GP108M [GeForce MX150] (rev a1)
- Subsystem: Lenovo GP108M [GeForce MX150]
- Flags: bus master, fast devsel, latency 0, IRQ 16
- Memory at e800 (32-bit, non-prefetchable) [size=16M]
- Memory at 7000 (64-bit, prefetchable) [size=256M]
- Memory at 8000 (64-bit, prefetchable) [size=32M]
- I/O ports at d000 [size=128]
- Capabilities:
- Kernel driver in use: nvidia
- Kernel modules: nvidiafb, nouveau, nvidia_drm, nvidia
+ Subsystem: Lenovo GP108M [GeForce MX150]
+ Flags: bus master, fast devsel, latency 0, IRQ 16
+ Memory at e800 (32-bit, non-prefetchable) [size=16M]
+ Memory at 7000 (64-bit, prefetchable) [size=256M]
+ Memory at 8000 (64-bit, prefetchable) [size=32M]
+ I/O ports at d000 [size=128]
+ Capabilities:
+ Kernel driver in use: nvidia
+ Kernel modules: nvidiafb, nouveau, nvidia_drm, nvidia
{
- "Version": "18.04",
- "OEM": {
- "Vendor": "LENOVO",
- },
- "BIOS":
[Kernel-packages] [Bug 1791745] Re: linux: 4.4.0-136.162 -proposed tracker
** Summary changed: - linux: -proposed tracker + linux: 4.4.0-136.162 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Kleber Sacilotto de Souza (kleber-souza) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Kleber Sacilotto de Souza (kleber-souza) ** Changed in: kernel-sru-workflow/prepare-package-signed Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Canonical Kernel Team (canonical-kernel-team) => Kleber Sacilotto de Souza (kleber-souza) -- 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/1791745 Title: linux: 4.4.0-136.162 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-certification-testing series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1791746 (linux-aws), bug 1791747 (linux-lts-xenial) derivatives: bug 1791749 (linux-aws), bug 1791750 (linux-euclid), bug 1791751 (linux-kvm), bug 1791752 (linux-raspi2), bug 1791753 (linux-snapdragon) To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1791745/+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
