[Kernel-packages] [Bug 1811869] Re: Alienware m15 takes very long to boot Ubuntu
** Changed in: linux (Ubuntu) Status: Confirmed => 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/1811869 Title: Alienware m15 takes very long to boot Ubuntu Status in linux package in Ubuntu: Fix Released Bug description: Alienware m15 takes a long time to boot. Attached are the dmesg and lspci prints. --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ryan 2452 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=5dc51b23-d69d-4ced-8925-6821465b020d InstallationDate: Installed on 2018-12-25 (21 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) IwConfig: wlp112s0 no wireless extensions. enp111s0 no wireless extensions. lono wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:5765 Realtek Semiconductor Corp. Bus 001 Device 003: ID 8087:0025 Intel Corp. Bus 001 Device 002: ID 187c:0550 Alienware Corporation Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Alienware Alienware m15 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=b62227a1-0ff3-4fdb-9ef6-200fcc8a3a00 ro "acpi_osi=Windows 2015" acpi=noirq pci=biosirq debug ignore_level ProcVersionSignature: Ubuntu 4.15.0-43.46~16.04.1-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.157.21 Tags: xenial Uname: Linux 4.15.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/20/2018 dmi.bios.vendor: Alienware dmi.bios.version: 1.3.3 dmi.board.name: 0CNR45 dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.3.3:bd12/20/2018:svnAlienware:pnAlienwarem15:pvr1.3.3:rvnAlienware:rn0CNR45:rvrA00:cvnAlienware:ct10:cvrNotSpecified: dmi.product.family: Alienware dmi.product.name: Alienware m15 dmi.product.version: 1.3.3 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811869/+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 1627905] Re: Ubuntu can't be installed to certain Lenovo Yoga laptops because the fakeraid storage mode is not supported.
This bug is old and Lenovo fixed the issue upstream with a corrected BIOS that users can optionally install, which enables AHCI mode. Also, from my understanding, Linux installs even in the default configuration now, including on the more recent Yoga 910 and 920 models thanks to some patches from Intel that went into the upstream Linux kernel. Unless anyone objects, I think this should be closed as fixed upstream. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1627905 Title: Ubuntu can't be installed to certain Lenovo Yoga laptops because the fakeraid storage mode is not supported. Status in linux package in Ubuntu: Triaged Bug description: Several Lenovo Yoga laptops do not allow the user to install any current Linux distributions due to being BIOS-locked to a RAID mode and Linux does not support this. You can boot a Linux live environment, but when you go to install, it will not see the Solid State Drive and it does not appear as a PCI device. The affected models are the Yoga 900 ISK2, 900S, 710S, and 900 ISK for Business, and probably the new Yoga Book and Yoga 910 as well. Lenovo has stated that removing the AHCI option from the BIOS is a feature and that they don't plan to fix this. There have been some blog postings and news articles about this issue lately. Here is the Lenovo Forums topic: https://forums.lenovo.com/t5/Linux-Discussion/Yoga-900-13ISK2-BIOS- update-for-setting-RAID-mode-for-missing/td-p/3339206/highlight/false (Note that this says it is solved, but it is not. Lenovo replied that they won't fix it and that Linux is not supported on these laptops.) Matthew Garrett's blog post is here: https://mjg59.dreamwidth.org/44694.html I approached him with the idea that perhaps the Linux kernel could be modified to reset the hardware and put it into AHCI mode after GRUB loads the kernel (according to him, GRUB doesn't need to be modified because it uses the uEFI firmware's disk access), and then Linux could proceed to boot. Here's what he said: "If you wanted to try that, the best place to do it would be the UEFI setup code in the kernel under arch/x86/boot/compressed/eboot.c - that way you can do it independent of bootloader. Grub's able to read files anyway since it's using the firmware calls to do that. The power management thing isn't about the SSD itself, it's about ensuring that the controller is programmed correctly so that the entire CPU package can enter deep sleep states. Modern systems should idle at around 4W at most, so small amounts make abig difference here." [...] "If the firmware hasn't locked the control bit and if the hardware is ok with suddenly being reconfigured, sure, that ought to work. Doing it in eboot.c means you're doing it before any PCI enumeration has occurred, which makes it more likely that things will work out well." [...] "I'll take a quick look at the 10-series chipset docs to see if it's documented, and if so I'll throw a quick patch together - but I'm probably not going to try pushing it upstream, I'm afraid. If it does work, I'm fine with anybody else doing so." I heaven't heard anything back lately, so I am putting this in a bug report so that the Ubuntu maintainers are aware of the issue. It seems like a few lines of kernel code are all that is really required to fix this and restore the ability of Linux distributions to be installed on half a dozen laptops (probably more to come, since Lenovo says that the industry is moving to this!). --- ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ryan 1604 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 17.04 EcryptfsInUse: Yes InstallationDate: Installed on 2017-05-30 (2 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 5986:068c Acer, Inc Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80UE Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-22-generic.efi.signed root=UUID=3ee79c46-724b-41b5-8c42-44458297de6a ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 RelatedPackageVersions: linux-restricted-modules-4.10.0-22-generic N/A linux-backports-modules-4.10.0-22-generic N/A
[Kernel-packages] [Bug 1690085]
Eco mode supposedly only controls the PSU fan. I'm guessing that will not change anything on the CPU soft lock side. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1690085 Title: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Hi, We aregetting various kernel crash on a pretty new config. We're using Ryzen 1800X CPU with X370 Gaming Pro Carbon MB (7A32V1) using latest BIOS available (1.52) We are running Ubuntu 17.04 (amd64), we've tried different kernel version, native one and releases from http://kernel.ubuntu.com/~kernel-ppa/mainline/ too. Tested kernel version: native 17.04 kernel 4.10.15 Issues are the same, we're getting random freeze on the machine. Here is kern.log entry when happening : May 10 22:41:56 dev2 kernel: [24366.186246] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:41:56 dev2 kernel: [24366.187618] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=913449 May 10 22:41:56 dev2 kernel: [24366.188977] (detected by 12, t=1860207 jiffies, g=10001, c=1, q=4656) May 10 22:41:56 dev2 kernel: [24366.190344] Task dump for CPU 0: May 10 22:41:56 dev2 kernel: [24366.190345] swapper/0 R running task 0 0 0 0x0008 May 10 22:41:56 dev2 kernel: [24366.190348] Call Trace: May 10 22:41:56 dev2 kernel: [24366.190354] ? native_safe_halt+0x6/0x10 May 10 22:41:56 dev2 kernel: [24366.190355] ? default_idle+0x20/0xd0 May 10 22:41:56 dev2 kernel: [24366.190358] ? arch_cpu_idle+0xf/0x20 May 10 22:41:56 dev2 kernel: [24366.190360] ? default_idle_call+0x23/0x30 May 10 22:41:56 dev2 kernel: [24366.190362] ? do_idle+0x16f/0x200 May 10 22:41:56 dev2 kernel: [24366.190364] ? cpu_startup_entry+0x71/0x80 May 10 22:41:56 dev2 kernel: [24366.190366] ? rest_init+0x77/0x80 May 10 22:41:56 dev2 kernel: [24366.190368] ? start_kernel+0x464/0x485 May 10 22:41:56 dev2 kernel: [24366.190369] ? early_idt_handler_array+0x120/0x120 May 10 22:41:56 dev2 kernel: [24366.190371] ? x86_64_start_reservations+0x24/0x26 May 10 22:41:56 dev2 kernel: [24366.190372] ? x86_64_start_kernel+0x14d/0x170 May 10 22:41:56 dev2 kernel: [24366.190373] ? start_cpu+0x14/0x14 May 10 22:44:56 dev2 kernel: [24546.188093] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:44:56 dev2 kernel: [24546.189461] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=935027 May 10 22:44:56 dev2 kernel: [24546.190823] (detected by 14, t=1905212 jiffies, g=10001, c=1, q=4740) May 10 22:44:56 dev2 kernel: [24546.192191] Task dump for CPU 0: May 10 22:44:56 dev2 kernel: [24546.192192] swapper/0 R running task 0 0 0 0x0008 May 10 22:44:56 dev2 kernel: [24546.192195] Call Trace: May 10 22:44:56 dev2 kernel: [24546.192199] ? native_safe_halt+0x6/0x10 May 10 22:44:56 dev2 kernel: [24546.192201] ? default_idle+0x20/0xd0 May 10 22:44:56 dev2 kernel: [24546.192203] ? arch_cpu_idle+0xf/0x20 May 10 22:44:56 dev2 kernel: [24546.192204] ? default_idle_call+0x23/0x30 May 10 22:44:56 dev2 kernel: [24546.192206] ? do_idle+0x16f/0x200 May 10 22:44:56 dev2 kernel: [24546.192208] ? cpu_startup_entry+0x71/0x80 May 10 22:44:56 dev2 kernel: [24546.192210] ? rest_init+0x77/0x80 May 10 22:44:56 dev2 kernel: [24546.192211] ? start_kernel+0x464/0x485 May 10 22:44:56 dev2 kernel: [24546.192213] ? early_idt_handler_array+0x120/0x120 May 10 22:44:56 dev2 kernel: [24546.192214] ? x86_64_start_reservations+0x24/0x26 May 10 22:44:56 dev2 kernel: [24546.192215] ? x86_64_start_kernel+0x14d/0x170 May 10 22:44:56 dev2 kernel: [24546.192217] ? start_cpu+0x14/0x14 Depending on the kernel version, we've got NMI watchdog errors related to CPU stuck (mentioning the CPU core id, which is random). Crash is happening randomly, but in general after some hours (3-4h). Now, we've installed kernel 4.11.0-041100-generic #201705041534 this morning and waiting for crash... For now, the machine is not "used", at least, it's not CPU stressed... Thanks --- ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-05-09 (1 days ago) InstallationMedia: Ubuntu-Server 17.04 "Zesty Zapus" - Release amd64 (20170412) Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash Tags: zesty Uname: Linux 4.11.0-041100-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1690085
[Kernel-packages] [Bug 1690085]
@Paulo: Are you running the latest bios? There is a newer bios from ~April or so, but I do not have the motherboard to try it out. To add some more information to this thread, I have the following machine: * AMD Ryzen 2700X * SuperNOVA 650 G3 650W (Eco switch set to On) * Asus ROG Crosshair VII Hero Wifi (BIOS 0601 04/19/2018, Typical Current set in the BIOS) This setup is currently working better with the Typical Current setting, though I have experienced a soft lockup with these settings after about ~6 hours of uptime. I am going to run the same setup with the eco switch to off on the PSU to see if anything changes. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1690085 Title: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Hi, We aregetting various kernel crash on a pretty new config. We're using Ryzen 1800X CPU with X370 Gaming Pro Carbon MB (7A32V1) using latest BIOS available (1.52) We are running Ubuntu 17.04 (amd64), we've tried different kernel version, native one and releases from http://kernel.ubuntu.com/~kernel-ppa/mainline/ too. Tested kernel version: native 17.04 kernel 4.10.15 Issues are the same, we're getting random freeze on the machine. Here is kern.log entry when happening : May 10 22:41:56 dev2 kernel: [24366.186246] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:41:56 dev2 kernel: [24366.187618] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=913449 May 10 22:41:56 dev2 kernel: [24366.188977] (detected by 12, t=1860207 jiffies, g=10001, c=1, q=4656) May 10 22:41:56 dev2 kernel: [24366.190344] Task dump for CPU 0: May 10 22:41:56 dev2 kernel: [24366.190345] swapper/0 R running task 0 0 0 0x0008 May 10 22:41:56 dev2 kernel: [24366.190348] Call Trace: May 10 22:41:56 dev2 kernel: [24366.190354] ? native_safe_halt+0x6/0x10 May 10 22:41:56 dev2 kernel: [24366.190355] ? default_idle+0x20/0xd0 May 10 22:41:56 dev2 kernel: [24366.190358] ? arch_cpu_idle+0xf/0x20 May 10 22:41:56 dev2 kernel: [24366.190360] ? default_idle_call+0x23/0x30 May 10 22:41:56 dev2 kernel: [24366.190362] ? do_idle+0x16f/0x200 May 10 22:41:56 dev2 kernel: [24366.190364] ? cpu_startup_entry+0x71/0x80 May 10 22:41:56 dev2 kernel: [24366.190366] ? rest_init+0x77/0x80 May 10 22:41:56 dev2 kernel: [24366.190368] ? start_kernel+0x464/0x485 May 10 22:41:56 dev2 kernel: [24366.190369] ? early_idt_handler_array+0x120/0x120 May 10 22:41:56 dev2 kernel: [24366.190371] ? x86_64_start_reservations+0x24/0x26 May 10 22:41:56 dev2 kernel: [24366.190372] ? x86_64_start_kernel+0x14d/0x170 May 10 22:41:56 dev2 kernel: [24366.190373] ? start_cpu+0x14/0x14 May 10 22:44:56 dev2 kernel: [24546.188093] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:44:56 dev2 kernel: [24546.189461] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=935027 May 10 22:44:56 dev2 kernel: [24546.190823] (detected by 14, t=1905212 jiffies, g=10001, c=1, q=4740) May 10 22:44:56 dev2 kernel: [24546.192191] Task dump for CPU 0: May 10 22:44:56 dev2 kernel: [24546.192192] swapper/0 R running task 0 0 0 0x0008 May 10 22:44:56 dev2 kernel: [24546.192195] Call Trace: May 10 22:44:56 dev2 kernel: [24546.192199] ? native_safe_halt+0x6/0x10 May 10 22:44:56 dev2 kernel: [24546.192201] ? default_idle+0x20/0xd0 May 10 22:44:56 dev2 kernel: [24546.192203] ? arch_cpu_idle+0xf/0x20 May 10 22:44:56 dev2 kernel: [24546.192204] ? default_idle_call+0x23/0x30 May 10 22:44:56 dev2 kernel: [24546.192206] ? do_idle+0x16f/0x200 May 10 22:44:56 dev2 kernel: [24546.192208] ? cpu_startup_entry+0x71/0x80 May 10 22:44:56 dev2 kernel: [24546.192210] ? rest_init+0x77/0x80 May 10 22:44:56 dev2 kernel: [24546.192211] ? start_kernel+0x464/0x485 May 10 22:44:56 dev2 kernel: [24546.192213] ? early_idt_handler_array+0x120/0x120 May 10 22:44:56 dev2 kernel: [24546.192214] ? x86_64_start_reservations+0x24/0x26 May 10 22:44:56 dev2 kernel: [24546.192215] ? x86_64_start_kernel+0x14d/0x170 May 10 22:44:56 dev2 kernel: [24546.192217] ? start_cpu+0x14/0x14 Depending on the kernel version, we've got NMI watchdog errors related to CPU stuck (mentioning the CPU core id, which is random). Crash is happening randomly, but in general after some hours (3-4h). Now, we've installed kernel 4.11.0-041100-generic #201705041534 this morning and waiting for crash... For now, the machine is not "used", at least, it's not CPU stressed... Thanks --- ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-05-09 (1 days ago) InstallationMedia: Ubuntu-Server 17.04 "Zes
[Kernel-packages] [Bug 1690085]
I was able to capture a soft-lock with sysrq-l [1]. Networking and mouse were still functional, but focusing windows and window activity in Plasma were locked. https://gist.github.com/rphillips/fae9540a8e7a3a83731c9a9809a98df4 Notes: * AMD Ryzen 2700X * SuperNOVA 650 G3 650W (Eco switch set to Off) * Asus ROG Crosshair VII Hero Wifi (BIOS 0601 04/19/2018, Typical Current set in the BIOS) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1690085 Title: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Hi, We aregetting various kernel crash on a pretty new config. We're using Ryzen 1800X CPU with X370 Gaming Pro Carbon MB (7A32V1) using latest BIOS available (1.52) We are running Ubuntu 17.04 (amd64), we've tried different kernel version, native one and releases from http://kernel.ubuntu.com/~kernel-ppa/mainline/ too. Tested kernel version: native 17.04 kernel 4.10.15 Issues are the same, we're getting random freeze on the machine. Here is kern.log entry when happening : May 10 22:41:56 dev2 kernel: [24366.186246] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:41:56 dev2 kernel: [24366.187618] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=913449 May 10 22:41:56 dev2 kernel: [24366.188977] (detected by 12, t=1860207 jiffies, g=10001, c=1, q=4656) May 10 22:41:56 dev2 kernel: [24366.190344] Task dump for CPU 0: May 10 22:41:56 dev2 kernel: [24366.190345] swapper/0 R running task 0 0 0 0x0008 May 10 22:41:56 dev2 kernel: [24366.190348] Call Trace: May 10 22:41:56 dev2 kernel: [24366.190354] ? native_safe_halt+0x6/0x10 May 10 22:41:56 dev2 kernel: [24366.190355] ? default_idle+0x20/0xd0 May 10 22:41:56 dev2 kernel: [24366.190358] ? arch_cpu_idle+0xf/0x20 May 10 22:41:56 dev2 kernel: [24366.190360] ? default_idle_call+0x23/0x30 May 10 22:41:56 dev2 kernel: [24366.190362] ? do_idle+0x16f/0x200 May 10 22:41:56 dev2 kernel: [24366.190364] ? cpu_startup_entry+0x71/0x80 May 10 22:41:56 dev2 kernel: [24366.190366] ? rest_init+0x77/0x80 May 10 22:41:56 dev2 kernel: [24366.190368] ? start_kernel+0x464/0x485 May 10 22:41:56 dev2 kernel: [24366.190369] ? early_idt_handler_array+0x120/0x120 May 10 22:41:56 dev2 kernel: [24366.190371] ? x86_64_start_reservations+0x24/0x26 May 10 22:41:56 dev2 kernel: [24366.190372] ? x86_64_start_kernel+0x14d/0x170 May 10 22:41:56 dev2 kernel: [24366.190373] ? start_cpu+0x14/0x14 May 10 22:44:56 dev2 kernel: [24546.188093] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:44:56 dev2 kernel: [24546.189461] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=935027 May 10 22:44:56 dev2 kernel: [24546.190823] (detected by 14, t=1905212 jiffies, g=10001, c=1, q=4740) May 10 22:44:56 dev2 kernel: [24546.192191] Task dump for CPU 0: May 10 22:44:56 dev2 kernel: [24546.192192] swapper/0 R running task 0 0 0 0x0008 May 10 22:44:56 dev2 kernel: [24546.192195] Call Trace: May 10 22:44:56 dev2 kernel: [24546.192199] ? native_safe_halt+0x6/0x10 May 10 22:44:56 dev2 kernel: [24546.192201] ? default_idle+0x20/0xd0 May 10 22:44:56 dev2 kernel: [24546.192203] ? arch_cpu_idle+0xf/0x20 May 10 22:44:56 dev2 kernel: [24546.192204] ? default_idle_call+0x23/0x30 May 10 22:44:56 dev2 kernel: [24546.192206] ? do_idle+0x16f/0x200 May 10 22:44:56 dev2 kernel: [24546.192208] ? cpu_startup_entry+0x71/0x80 May 10 22:44:56 dev2 kernel: [24546.192210] ? rest_init+0x77/0x80 May 10 22:44:56 dev2 kernel: [24546.192211] ? start_kernel+0x464/0x485 May 10 22:44:56 dev2 kernel: [24546.192213] ? early_idt_handler_array+0x120/0x120 May 10 22:44:56 dev2 kernel: [24546.192214] ? x86_64_start_reservations+0x24/0x26 May 10 22:44:56 dev2 kernel: [24546.192215] ? x86_64_start_kernel+0x14d/0x170 May 10 22:44:56 dev2 kernel: [24546.192217] ? start_cpu+0x14/0x14 Depending on the kernel version, we've got NMI watchdog errors related to CPU stuck (mentioning the CPU core id, which is random). Crash is happening randomly, but in general after some hours (3-4h). Now, we've installed kernel 4.11.0-041100-generic #201705041534 this morning and waiting for crash... For now, the machine is not "used", at least, it's not CPU stressed... Thanks --- ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-05-09 (1 days ago) InstallationMedia: Ubuntu-Server 17.04 "Zesty Zapus" - Release amd64 (20170412) Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash Tags: zesty Uname: Linux 4.11.0-04110
[Kernel-packages] [Bug 1690085]
I have finally gotten to stable (no soft lockup). Asus released the 0702 bios which includes Agesa update 1.0.0.2c. Typical Current is set to enabled within the bios. No other special kernel command-line options are enabled. Machine: * Kernel 4.7.13 * AMD Ryzen 2700X * SuperNOVA 650 G3 650W (Eco switch set to Off) * Asus ROG Crosshair VII Hero Wifi (BIOS 0702 06/22/2018, Typical Current set in the BIOS) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1690085 Title: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Hi, We aregetting various kernel crash on a pretty new config. We're using Ryzen 1800X CPU with X370 Gaming Pro Carbon MB (7A32V1) using latest BIOS available (1.52) We are running Ubuntu 17.04 (amd64), we've tried different kernel version, native one and releases from http://kernel.ubuntu.com/~kernel-ppa/mainline/ too. Tested kernel version: native 17.04 kernel 4.10.15 Issues are the same, we're getting random freeze on the machine. Here is kern.log entry when happening : May 10 22:41:56 dev2 kernel: [24366.186246] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:41:56 dev2 kernel: [24366.187618] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=913449 May 10 22:41:56 dev2 kernel: [24366.188977] (detected by 12, t=1860207 jiffies, g=10001, c=1, q=4656) May 10 22:41:56 dev2 kernel: [24366.190344] Task dump for CPU 0: May 10 22:41:56 dev2 kernel: [24366.190345] swapper/0 R running task 0 0 0 0x0008 May 10 22:41:56 dev2 kernel: [24366.190348] Call Trace: May 10 22:41:56 dev2 kernel: [24366.190354] ? native_safe_halt+0x6/0x10 May 10 22:41:56 dev2 kernel: [24366.190355] ? default_idle+0x20/0xd0 May 10 22:41:56 dev2 kernel: [24366.190358] ? arch_cpu_idle+0xf/0x20 May 10 22:41:56 dev2 kernel: [24366.190360] ? default_idle_call+0x23/0x30 May 10 22:41:56 dev2 kernel: [24366.190362] ? do_idle+0x16f/0x200 May 10 22:41:56 dev2 kernel: [24366.190364] ? cpu_startup_entry+0x71/0x80 May 10 22:41:56 dev2 kernel: [24366.190366] ? rest_init+0x77/0x80 May 10 22:41:56 dev2 kernel: [24366.190368] ? start_kernel+0x464/0x485 May 10 22:41:56 dev2 kernel: [24366.190369] ? early_idt_handler_array+0x120/0x120 May 10 22:41:56 dev2 kernel: [24366.190371] ? x86_64_start_reservations+0x24/0x26 May 10 22:41:56 dev2 kernel: [24366.190372] ? x86_64_start_kernel+0x14d/0x170 May 10 22:41:56 dev2 kernel: [24366.190373] ? start_cpu+0x14/0x14 May 10 22:44:56 dev2 kernel: [24546.188093] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:44:56 dev2 kernel: [24546.189461] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=935027 May 10 22:44:56 dev2 kernel: [24546.190823] (detected by 14, t=1905212 jiffies, g=10001, c=1, q=4740) May 10 22:44:56 dev2 kernel: [24546.192191] Task dump for CPU 0: May 10 22:44:56 dev2 kernel: [24546.192192] swapper/0 R running task 0 0 0 0x0008 May 10 22:44:56 dev2 kernel: [24546.192195] Call Trace: May 10 22:44:56 dev2 kernel: [24546.192199] ? native_safe_halt+0x6/0x10 May 10 22:44:56 dev2 kernel: [24546.192201] ? default_idle+0x20/0xd0 May 10 22:44:56 dev2 kernel: [24546.192203] ? arch_cpu_idle+0xf/0x20 May 10 22:44:56 dev2 kernel: [24546.192204] ? default_idle_call+0x23/0x30 May 10 22:44:56 dev2 kernel: [24546.192206] ? do_idle+0x16f/0x200 May 10 22:44:56 dev2 kernel: [24546.192208] ? cpu_startup_entry+0x71/0x80 May 10 22:44:56 dev2 kernel: [24546.192210] ? rest_init+0x77/0x80 May 10 22:44:56 dev2 kernel: [24546.192211] ? start_kernel+0x464/0x485 May 10 22:44:56 dev2 kernel: [24546.192213] ? early_idt_handler_array+0x120/0x120 May 10 22:44:56 dev2 kernel: [24546.192214] ? x86_64_start_reservations+0x24/0x26 May 10 22:44:56 dev2 kernel: [24546.192215] ? x86_64_start_kernel+0x14d/0x170 May 10 22:44:56 dev2 kernel: [24546.192217] ? start_cpu+0x14/0x14 Depending on the kernel version, we've got NMI watchdog errors related to CPU stuck (mentioning the CPU core id, which is random). Crash is happening randomly, but in general after some hours (3-4h). Now, we've installed kernel 4.11.0-041100-generic #201705041534 this morning and waiting for crash... For now, the machine is not "used", at least, it's not CPU stressed... Thanks --- ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-05-09 (1 days ago) InstallationMedia: Ubuntu-Server 17.04 "Zesty Zapus" - Release amd64 (20170412) Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash Tags: zesty Uname:
[Kernel-packages] [Bug 1799964] Re: Ubuntu 18.10 After Blank Screen System Won't Come Back
Adding my output with the same issue in case it helps in investigation. Attached the output as requested by Daniel van Vugt. ** Attachment added: "Output of journalctl -b-1 > prev_boot.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1799964/+attachment/5206089/+files/prev_boot.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/1799964 Title: Ubuntu 18.10 After Blank Screen System Won't Come Back Status in linux package in Ubuntu: Confirmed Bug description: In Ubuntu 18.10 if the blank screen feature initiates (5 minutes default) the system will remain blank and there is no way to get the display back on without a hard reset. The video card I am using is a Vega 64. Other users who have Vega AMD GPU's are experiencing the same issue. This is only happening in Ubuntu 18.10. Does not occur in my Arch or Fedora installs. To reproduce: - Let 'Blank Screen' feature execute (5 min default) - Screen will not come back ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Oct 25 10:18:59 2018 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Vega 10 XT [Radeon RX Vega 64] [1002:687f] (rev c1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Vega 10 XT [Radeon RX Vega 64] [1043:04c4] InstallationDate: Installed on 2018-10-19 (6 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Micro-Star International Co., Ltd. MS-7B78 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=21c08187-f134-41b4-b8e5-93bead748c4f ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/24/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.20 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X470 GAMING PRO CARBON (MS-7B78) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.20:bd04/24/2018:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B78:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnX470GAMINGPROCARBON(MS-7B78):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7B78 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1799964/+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 1811869] [NEW] Alienware m15 takes very long to boot Ubuntu
Public bug reported: Alienware m15 takes a long time to boot. Attached are the dmesg and lspci prints. ** Affects: linux (Ubuntu) Importance: Undecided Assignee: TJ (tj) Status: New ** Attachment added: "errorlogs.txt" https://bugs.launchpad.net/bugs/1811869/+attachment/5229375/+files/errorlogs.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/1811869 Title: Alienware m15 takes very long to boot Ubuntu Status in linux package in Ubuntu: New Bug description: Alienware m15 takes a long time to boot. Attached are the dmesg and lspci prints. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811869/+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 1811869] Re: Alienware m15 takes very long to boot Ubuntu
apport information ** Tags added: apport-collected xenial ** Description changed: - Alienware m15 takes a long time to boot. Attached are the dmesg and - lspci prints. + Alienware m15 takes a long time to boot. Attached are the dmesg and lspci prints. + --- + ApportVersion: 2.20.1-0ubuntu2.18 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: ryan 2452 F pulseaudio + CurrentDesktop: Unity + DistroRelease: Ubuntu 16.04 + HibernationDevice: RESUME=UUID=5dc51b23-d69d-4ced-8925-6821465b020d + InstallationDate: Installed on 2018-12-25 (21 days ago) + InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) + IwConfig: + wlp112s0 no wireless extensions. + + enp111s0 no wireless extensions. + + lono wireless extensions. + Lsusb: + Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 001 Device 004: ID 0bda:5765 Realtek Semiconductor Corp. + Bus 001 Device 003: ID 8087:0025 Intel Corp. + Bus 001 Device 002: ID 187c:0550 Alienware Corporation + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + MachineType: Alienware Alienware m15 + Package: linux (not installed) + ProcFB: 0 inteldrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=b62227a1-0ff3-4fdb-9ef6-200fcc8a3a00 ro "acpi_osi=Windows 2015" acpi=noirq pci=biosirq debug ignore_level + ProcVersionSignature: Ubuntu 4.15.0-43.46~16.04.1-generic 4.15.18 + RelatedPackageVersions: + linux-restricted-modules-4.15.0-43-generic N/A + linux-backports-modules-4.15.0-43-generic N/A + linux-firmware 1.157.21 + Tags: xenial + Uname: Linux 4.15.0-43-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 12/20/2018 + dmi.bios.vendor: Alienware + dmi.bios.version: 1.3.3 + dmi.board.name: 0CNR45 + dmi.board.vendor: Alienware + dmi.board.version: A00 + dmi.chassis.type: 10 + dmi.chassis.vendor: Alienware + dmi.chassis.version: Not Specified + dmi.modalias: dmi:bvnAlienware:bvr1.3.3:bd12/20/2018:svnAlienware:pnAlienwarem15:pvr1.3.3:rvnAlienware:rn0CNR45:rvrA00:cvnAlienware:ct10:cvrNotSpecified: + dmi.product.family: Alienware + dmi.product.name: Alienware m15 + dmi.product.version: 1.3.3 + dmi.sys.vendor: Alienware ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1811869/+attachment/5229463/+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/1811869 Title: Alienware m15 takes very long to boot Ubuntu Status in linux package in Ubuntu: Confirmed Bug description: Alienware m15 takes a long time to boot. Attached are the dmesg and lspci prints. --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ryan 2452 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=5dc51b23-d69d-4ced-8925-6821465b020d InstallationDate: Installed on 2018-12-25 (21 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) IwConfig: wlp112s0 no wireless extensions. enp111s0 no wireless extensions. lono wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:5765 Realtek Semiconductor Corp. Bus 001 Device 003: ID 8087:0025 Intel Corp. Bus 001 Device 002: ID 187c:0550 Alienware Corporation Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Alienware Alienware m15 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=b62227a1-0ff3-4fdb-9ef6-200fcc8a3a00 ro "acpi_osi=Windows 2015" acpi=noirq pci=biosirq debug ignore_level ProcVersionSignature: Ubuntu 4.15.0-43.46~16.04.1-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.157.21 Tags: xenial Uname: Linux 4.15.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/20/2018 dmi.bios.vendor: Alienware dmi.bios.version: 1.3.3 dmi.board.name: 0CNR45 dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.3.3:bd12/20/2018:svnAlienware:pnAlienwarem15:pvr1.3.3:rvnAlienware:rn0CNR45:rvrA00:cvnAlienware:ct10:cvrNotSpecified: dmi.product.f
[Kernel-packages] [Bug 1811869] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1811869/+attachment/5229465/+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/1811869 Title: Alienware m15 takes very long to boot Ubuntu Status in linux package in Ubuntu: Confirmed Bug description: Alienware m15 takes a long time to boot. Attached are the dmesg and lspci prints. --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ryan 2452 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=5dc51b23-d69d-4ced-8925-6821465b020d InstallationDate: Installed on 2018-12-25 (21 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) IwConfig: wlp112s0 no wireless extensions. enp111s0 no wireless extensions. lono wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:5765 Realtek Semiconductor Corp. Bus 001 Device 003: ID 8087:0025 Intel Corp. Bus 001 Device 002: ID 187c:0550 Alienware Corporation Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Alienware Alienware m15 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=b62227a1-0ff3-4fdb-9ef6-200fcc8a3a00 ro "acpi_osi=Windows 2015" acpi=noirq pci=biosirq debug ignore_level ProcVersionSignature: Ubuntu 4.15.0-43.46~16.04.1-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.157.21 Tags: xenial Uname: Linux 4.15.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/20/2018 dmi.bios.vendor: Alienware dmi.bios.version: 1.3.3 dmi.board.name: 0CNR45 dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.3.3:bd12/20/2018:svnAlienware:pnAlienwarem15:pvr1.3.3:rvnAlienware:rn0CNR45:rvrA00:cvnAlienware:ct10:cvrNotSpecified: dmi.product.family: Alienware dmi.product.name: Alienware m15 dmi.product.version: 1.3.3 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811869/+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 1811869] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1811869/+attachment/5229464/+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/1811869 Title: Alienware m15 takes very long to boot Ubuntu Status in linux package in Ubuntu: Confirmed Bug description: Alienware m15 takes a long time to boot. Attached are the dmesg and lspci prints. --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ryan 2452 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=5dc51b23-d69d-4ced-8925-6821465b020d InstallationDate: Installed on 2018-12-25 (21 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) IwConfig: wlp112s0 no wireless extensions. enp111s0 no wireless extensions. lono wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:5765 Realtek Semiconductor Corp. Bus 001 Device 003: ID 8087:0025 Intel Corp. Bus 001 Device 002: ID 187c:0550 Alienware Corporation Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Alienware Alienware m15 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=b62227a1-0ff3-4fdb-9ef6-200fcc8a3a00 ro "acpi_osi=Windows 2015" acpi=noirq pci=biosirq debug ignore_level ProcVersionSignature: Ubuntu 4.15.0-43.46~16.04.1-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.157.21 Tags: xenial Uname: Linux 4.15.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/20/2018 dmi.bios.vendor: Alienware dmi.bios.version: 1.3.3 dmi.board.name: 0CNR45 dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.3.3:bd12/20/2018:svnAlienware:pnAlienwarem15:pvr1.3.3:rvnAlienware:rn0CNR45:rvrA00:cvnAlienware:ct10:cvrNotSpecified: dmi.product.family: Alienware dmi.product.name: Alienware m15 dmi.product.version: 1.3.3 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811869/+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 1811869] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1811869/+attachment/5229467/+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/1811869 Title: Alienware m15 takes very long to boot Ubuntu Status in linux package in Ubuntu: Confirmed Bug description: Alienware m15 takes a long time to boot. Attached are the dmesg and lspci prints. --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ryan 2452 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=5dc51b23-d69d-4ced-8925-6821465b020d InstallationDate: Installed on 2018-12-25 (21 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) IwConfig: wlp112s0 no wireless extensions. enp111s0 no wireless extensions. lono wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:5765 Realtek Semiconductor Corp. Bus 001 Device 003: ID 8087:0025 Intel Corp. Bus 001 Device 002: ID 187c:0550 Alienware Corporation Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Alienware Alienware m15 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=b62227a1-0ff3-4fdb-9ef6-200fcc8a3a00 ro "acpi_osi=Windows 2015" acpi=noirq pci=biosirq debug ignore_level ProcVersionSignature: Ubuntu 4.15.0-43.46~16.04.1-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.157.21 Tags: xenial Uname: Linux 4.15.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/20/2018 dmi.bios.vendor: Alienware dmi.bios.version: 1.3.3 dmi.board.name: 0CNR45 dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.3.3:bd12/20/2018:svnAlienware:pnAlienwarem15:pvr1.3.3:rvnAlienware:rn0CNR45:rvrA00:cvnAlienware:ct10:cvrNotSpecified: dmi.product.family: Alienware dmi.product.name: Alienware m15 dmi.product.version: 1.3.3 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811869/+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 1811869] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1811869/+attachment/5229468/+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/1811869 Title: Alienware m15 takes very long to boot Ubuntu Status in linux package in Ubuntu: Confirmed Bug description: Alienware m15 takes a long time to boot. Attached are the dmesg and lspci prints. --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ryan 2452 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=5dc51b23-d69d-4ced-8925-6821465b020d InstallationDate: Installed on 2018-12-25 (21 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) IwConfig: wlp112s0 no wireless extensions. enp111s0 no wireless extensions. lono wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:5765 Realtek Semiconductor Corp. Bus 001 Device 003: ID 8087:0025 Intel Corp. Bus 001 Device 002: ID 187c:0550 Alienware Corporation Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Alienware Alienware m15 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=b62227a1-0ff3-4fdb-9ef6-200fcc8a3a00 ro "acpi_osi=Windows 2015" acpi=noirq pci=biosirq debug ignore_level ProcVersionSignature: Ubuntu 4.15.0-43.46~16.04.1-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.157.21 Tags: xenial Uname: Linux 4.15.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/20/2018 dmi.bios.vendor: Alienware dmi.bios.version: 1.3.3 dmi.board.name: 0CNR45 dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.3.3:bd12/20/2018:svnAlienware:pnAlienwarem15:pvr1.3.3:rvnAlienware:rn0CNR45:rvrA00:cvnAlienware:ct10:cvrNotSpecified: dmi.product.family: Alienware dmi.product.name: Alienware m15 dmi.product.version: 1.3.3 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811869/+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 1811869] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1811869/+attachment/5229471/+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/1811869 Title: Alienware m15 takes very long to boot Ubuntu Status in linux package in Ubuntu: Confirmed Bug description: Alienware m15 takes a long time to boot. Attached are the dmesg and lspci prints. --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ryan 2452 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=5dc51b23-d69d-4ced-8925-6821465b020d InstallationDate: Installed on 2018-12-25 (21 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) IwConfig: wlp112s0 no wireless extensions. enp111s0 no wireless extensions. lono wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:5765 Realtek Semiconductor Corp. Bus 001 Device 003: ID 8087:0025 Intel Corp. Bus 001 Device 002: ID 187c:0550 Alienware Corporation Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Alienware Alienware m15 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=b62227a1-0ff3-4fdb-9ef6-200fcc8a3a00 ro "acpi_osi=Windows 2015" acpi=noirq pci=biosirq debug ignore_level ProcVersionSignature: Ubuntu 4.15.0-43.46~16.04.1-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.157.21 Tags: xenial Uname: Linux 4.15.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/20/2018 dmi.bios.vendor: Alienware dmi.bios.version: 1.3.3 dmi.board.name: 0CNR45 dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.3.3:bd12/20/2018:svnAlienware:pnAlienwarem15:pvr1.3.3:rvnAlienware:rn0CNR45:rvrA00:cvnAlienware:ct10:cvrNotSpecified: dmi.product.family: Alienware dmi.product.name: Alienware m15 dmi.product.version: 1.3.3 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811869/+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 1811869] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1811869/+attachment/5229470/+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/1811869 Title: Alienware m15 takes very long to boot Ubuntu Status in linux package in Ubuntu: Confirmed Bug description: Alienware m15 takes a long time to boot. Attached are the dmesg and lspci prints. --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ryan 2452 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=5dc51b23-d69d-4ced-8925-6821465b020d InstallationDate: Installed on 2018-12-25 (21 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) IwConfig: wlp112s0 no wireless extensions. enp111s0 no wireless extensions. lono wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:5765 Realtek Semiconductor Corp. Bus 001 Device 003: ID 8087:0025 Intel Corp. Bus 001 Device 002: ID 187c:0550 Alienware Corporation Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Alienware Alienware m15 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=b62227a1-0ff3-4fdb-9ef6-200fcc8a3a00 ro "acpi_osi=Windows 2015" acpi=noirq pci=biosirq debug ignore_level ProcVersionSignature: Ubuntu 4.15.0-43.46~16.04.1-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.157.21 Tags: xenial Uname: Linux 4.15.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/20/2018 dmi.bios.vendor: Alienware dmi.bios.version: 1.3.3 dmi.board.name: 0CNR45 dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.3.3:bd12/20/2018:svnAlienware:pnAlienwarem15:pvr1.3.3:rvnAlienware:rn0CNR45:rvrA00:cvnAlienware:ct10:cvrNotSpecified: dmi.product.family: Alienware dmi.product.name: Alienware m15 dmi.product.version: 1.3.3 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811869/+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 1811869] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1811869/+attachment/5229469/+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/1811869 Title: Alienware m15 takes very long to boot Ubuntu Status in linux package in Ubuntu: Confirmed Bug description: Alienware m15 takes a long time to boot. Attached are the dmesg and lspci prints. --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ryan 2452 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=5dc51b23-d69d-4ced-8925-6821465b020d InstallationDate: Installed on 2018-12-25 (21 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) IwConfig: wlp112s0 no wireless extensions. enp111s0 no wireless extensions. lono wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:5765 Realtek Semiconductor Corp. Bus 001 Device 003: ID 8087:0025 Intel Corp. Bus 001 Device 002: ID 187c:0550 Alienware Corporation Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Alienware Alienware m15 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=b62227a1-0ff3-4fdb-9ef6-200fcc8a3a00 ro "acpi_osi=Windows 2015" acpi=noirq pci=biosirq debug ignore_level ProcVersionSignature: Ubuntu 4.15.0-43.46~16.04.1-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.157.21 Tags: xenial Uname: Linux 4.15.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/20/2018 dmi.bios.vendor: Alienware dmi.bios.version: 1.3.3 dmi.board.name: 0CNR45 dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.3.3:bd12/20/2018:svnAlienware:pnAlienwarem15:pvr1.3.3:rvnAlienware:rn0CNR45:rvrA00:cvnAlienware:ct10:cvrNotSpecified: dmi.product.family: Alienware dmi.product.name: Alienware m15 dmi.product.version: 1.3.3 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811869/+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 1811869] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1811869/+attachment/5229473/+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/1811869 Title: Alienware m15 takes very long to boot Ubuntu Status in linux package in Ubuntu: Confirmed Bug description: Alienware m15 takes a long time to boot. Attached are the dmesg and lspci prints. --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ryan 2452 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=5dc51b23-d69d-4ced-8925-6821465b020d InstallationDate: Installed on 2018-12-25 (21 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) IwConfig: wlp112s0 no wireless extensions. enp111s0 no wireless extensions. lono wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:5765 Realtek Semiconductor Corp. Bus 001 Device 003: ID 8087:0025 Intel Corp. Bus 001 Device 002: ID 187c:0550 Alienware Corporation Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Alienware Alienware m15 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=b62227a1-0ff3-4fdb-9ef6-200fcc8a3a00 ro "acpi_osi=Windows 2015" acpi=noirq pci=biosirq debug ignore_level ProcVersionSignature: Ubuntu 4.15.0-43.46~16.04.1-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.157.21 Tags: xenial Uname: Linux 4.15.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/20/2018 dmi.bios.vendor: Alienware dmi.bios.version: 1.3.3 dmi.board.name: 0CNR45 dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.3.3:bd12/20/2018:svnAlienware:pnAlienwarem15:pvr1.3.3:rvnAlienware:rn0CNR45:rvrA00:cvnAlienware:ct10:cvrNotSpecified: dmi.product.family: Alienware dmi.product.name: Alienware m15 dmi.product.version: 1.3.3 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811869/+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 1811869] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1811869/+attachment/5229466/+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/1811869 Title: Alienware m15 takes very long to boot Ubuntu Status in linux package in Ubuntu: Confirmed Bug description: Alienware m15 takes a long time to boot. Attached are the dmesg and lspci prints. --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ryan 2452 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=5dc51b23-d69d-4ced-8925-6821465b020d InstallationDate: Installed on 2018-12-25 (21 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) IwConfig: wlp112s0 no wireless extensions. enp111s0 no wireless extensions. lono wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:5765 Realtek Semiconductor Corp. Bus 001 Device 003: ID 8087:0025 Intel Corp. Bus 001 Device 002: ID 187c:0550 Alienware Corporation Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Alienware Alienware m15 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=b62227a1-0ff3-4fdb-9ef6-200fcc8a3a00 ro "acpi_osi=Windows 2015" acpi=noirq pci=biosirq debug ignore_level ProcVersionSignature: Ubuntu 4.15.0-43.46~16.04.1-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.157.21 Tags: xenial Uname: Linux 4.15.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/20/2018 dmi.bios.vendor: Alienware dmi.bios.version: 1.3.3 dmi.board.name: 0CNR45 dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.3.3:bd12/20/2018:svnAlienware:pnAlienwarem15:pvr1.3.3:rvnAlienware:rn0CNR45:rvrA00:cvnAlienware:ct10:cvrNotSpecified: dmi.product.family: Alienware dmi.product.name: Alienware m15 dmi.product.version: 1.3.3 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811869/+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 1811869] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1811869/+attachment/5229472/+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/1811869 Title: Alienware m15 takes very long to boot Ubuntu Status in linux package in Ubuntu: Confirmed Bug description: Alienware m15 takes a long time to boot. Attached are the dmesg and lspci prints. --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ryan 2452 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=5dc51b23-d69d-4ced-8925-6821465b020d InstallationDate: Installed on 2018-12-25 (21 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) IwConfig: wlp112s0 no wireless extensions. enp111s0 no wireless extensions. lono wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:5765 Realtek Semiconductor Corp. Bus 001 Device 003: ID 8087:0025 Intel Corp. Bus 001 Device 002: ID 187c:0550 Alienware Corporation Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Alienware Alienware m15 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=b62227a1-0ff3-4fdb-9ef6-200fcc8a3a00 ro "acpi_osi=Windows 2015" acpi=noirq pci=biosirq debug ignore_level ProcVersionSignature: Ubuntu 4.15.0-43.46~16.04.1-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.157.21 Tags: xenial Uname: Linux 4.15.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/20/2018 dmi.bios.vendor: Alienware dmi.bios.version: 1.3.3 dmi.board.name: 0CNR45 dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.3.3:bd12/20/2018:svnAlienware:pnAlienwarem15:pvr1.3.3:rvnAlienware:rn0CNR45:rvrA00:cvnAlienware:ct10:cvrNotSpecified: dmi.product.family: Alienware dmi.product.name: Alienware m15 dmi.product.version: 1.3.3 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811869/+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 1811869] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1811869/+attachment/5229474/+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/1811869 Title: Alienware m15 takes very long to boot Ubuntu Status in linux package in Ubuntu: Confirmed Bug description: Alienware m15 takes a long time to boot. Attached are the dmesg and lspci prints. --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ryan 2452 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=5dc51b23-d69d-4ced-8925-6821465b020d InstallationDate: Installed on 2018-12-25 (21 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) IwConfig: wlp112s0 no wireless extensions. enp111s0 no wireless extensions. lono wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:5765 Realtek Semiconductor Corp. Bus 001 Device 003: ID 8087:0025 Intel Corp. Bus 001 Device 002: ID 187c:0550 Alienware Corporation Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Alienware Alienware m15 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=b62227a1-0ff3-4fdb-9ef6-200fcc8a3a00 ro "acpi_osi=Windows 2015" acpi=noirq pci=biosirq debug ignore_level ProcVersionSignature: Ubuntu 4.15.0-43.46~16.04.1-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.157.21 Tags: xenial Uname: Linux 4.15.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/20/2018 dmi.bios.vendor: Alienware dmi.bios.version: 1.3.3 dmi.board.name: 0CNR45 dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.3.3:bd12/20/2018:svnAlienware:pnAlienwarem15:pvr1.3.3:rvnAlienware:rn0CNR45:rvrA00:cvnAlienware:ct10:cvrNotSpecified: dmi.product.family: Alienware dmi.product.name: Alienware m15 dmi.product.version: 1.3.3 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811869/+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 1811869] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1811869/+attachment/5229475/+files/WifiSyslog.txt ** Changed in: linux (Ubuntu) Status: In Progress => 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/1811869 Title: Alienware m15 takes very long to boot Ubuntu Status in linux package in Ubuntu: Confirmed Bug description: Alienware m15 takes a long time to boot. Attached are the dmesg and lspci prints. --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ryan 2452 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=5dc51b23-d69d-4ced-8925-6821465b020d InstallationDate: Installed on 2018-12-25 (21 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) IwConfig: wlp112s0 no wireless extensions. enp111s0 no wireless extensions. lono wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:5765 Realtek Semiconductor Corp. Bus 001 Device 003: ID 8087:0025 Intel Corp. Bus 001 Device 002: ID 187c:0550 Alienware Corporation Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Alienware Alienware m15 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=b62227a1-0ff3-4fdb-9ef6-200fcc8a3a00 ro "acpi_osi=Windows 2015" acpi=noirq pci=biosirq debug ignore_level ProcVersionSignature: Ubuntu 4.15.0-43.46~16.04.1-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.157.21 Tags: xenial Uname: Linux 4.15.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/20/2018 dmi.bios.vendor: Alienware dmi.bios.version: 1.3.3 dmi.board.name: 0CNR45 dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.3.3:bd12/20/2018:svnAlienware:pnAlienwarem15:pvr1.3.3:rvnAlienware:rn0CNR45:rvrA00:cvnAlienware:ct10:cvrNotSpecified: dmi.product.family: Alienware dmi.product.name: Alienware m15 dmi.product.version: 1.3.3 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811869/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1891684] Re: [amdgpu] Screen flickers after resuming from suspend
were you able to figure it out? should i post another log? On Mon, Aug 17, 2020 at 12:46 AM Ryan D wrote: > > Thank you. I dont know how i did not see that before > > On Mon, Aug 17, 2020 at 12:25 AM Daniel van Vugt < > 1891...@bugs.launchpad.net> wrote: > >> Also, please don't use Alt+F2. This command needs to be run in the >> Terminal app: >> >> journalctl -b-1 > prevboot.txt >> >> But only using the steps from comment #2. And then use the Files app to >> retrieve the file. >> >> -- >> You received this bug notification because you are subscribed to the bug >> report. >> https://bugs.launchpad.net/bugs/1891684 >> >> Title: >> [amdgpu] Screen flickers after resuming from suspend >> >> Status in linux package in Ubuntu: >> Incomplete >> Status in xserver-xorg-video-amdgpu package in Ubuntu: >> Incomplete >> >> Bug description: >> when computer is coming out of suspension mode, i get terrible screen >> flickers. Only way i have worked around this is a reboot. >> >> This video card is from sapphire >> Nitro + SE 5700xt >> >> ProblemType: Bug >> DistroRelease: Ubuntu 20.04 >> Package: xorg 1:7.7+19ubuntu14 >> ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 >> Uname: Linux 5.4.0-42-generic x86_64 >> ApportVersion: 2.20.11-0ubuntu27.6 >> Architecture: amd64 >> BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' >> CasperMD5CheckResult: skip >> CompositorRunning: None >> CurrentDesktop: ubuntu:GNOME >> Date: Fri Aug 14 12:16:42 2020 >> DistUpgraded: Fresh install >> DistroCodename: focal >> DistroVariant: ubuntu >> GraphicsCard: >>Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 >> OEM/5600 XT / 5700/5700 XT] [1002:731f] (rev c1) (prog-if 00 [VGA >> controller]) >> Subsystem: Sapphire Technology Limited Navi 10 [Radeon RX 5600 >> OEM/5600 XT / 5700/5700 XT] [1da2:e410] >> InstallationDate: Installed on 2020-06-08 (66 days ago) >> InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 >> (20200423) >> MachineType: System manufacturer System Product Name >> ProcEnviron: >>PATH=(custom, no user) >>XDG_RUNTIME_DIR= >>LANG=en_US.UTF-8 >>SHELL=/bin/bash >> ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic >> root=UUID=de7b87e0-cf04-4f9f-978e-3646f7e7266d ro quiet splash vt.handoff=7 >> SourcePackage: xorg >> Symptom: display >> UpgradeStatus: No upgrade log present (probably fresh install) >> dmi.bios.date: 06/17/2020 >> dmi.bios.vendor: American Megatrends Inc. >> dmi.bios.version: 2203 >> dmi.board.asset.tag: Default string >> dmi.board.name: TUF GAMING X570-PLUS >> dmi.board.vendor: ASUSTeK COMPUTER INC. >> dmi.board.version: Rev X.0x >> dmi.chassis.asset.tag: Default string >> dmi.chassis.type: 3 >> dmi.chassis.vendor: Default string >> dmi.chassis.version: Default string >> dmi.modalias: >> dmi:bvnAmericanMegatrendsInc.:bvr2203:bd06/17/2020:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFGAMINGX570-PLUS:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: >> dmi.product.family: To be filled by O.E.M. >> dmi.product.name: System Product Name >> dmi.product.sku: SKU >> dmi.product.version: System Version >> dmi.sys.vendor: System manufacturer >> version.compiz: compiz N/A >> version.libdrm2: libdrm2 2.4.101-2 >> version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 >> version.libgl1-mesa-glx: libgl1-mesa-glx N/A >> version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 >> version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A >> version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 >> version.xserver-xorg-video-intel: xserver-xorg-video-intel >> 2:2.99.917+git20200226-1 >> version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau >> 1:1.0.16-1 >> >> To manage notifications about this bug go to: >> >> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1891684/+subscriptions >> > -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1891684 Title: [amdgpu] Screen flickers after resuming from suspend Status in linux package in Ubuntu: Incomplete Status in xserver-xorg-video-amdgpu package in Ubuntu: I
Re: [Kernel-packages] [Bug 1891684] Re: [amdgpu] Screen flickers after resuming from suspend
wow ok. i actually have a a acer aspire 5 with a 4500u i couldnt get ubuntu to boot on it so i abandoned it and re installed windows. is there a 20.10 iso available for download? On Mon, Sep 28, 2020 at 4:01 PM Richard Elkins <1891...@bugs.launchpad.net> wrote: > This could very well be an issue with the amdgpu kernel module or the > kernel itself. 20.04 uses kernel 5.4 I fixed my situation (similar) by > upgrading to 20.10 (beta) which uses 5.8 packages. Now, my power > management and suspend/resume actually work. > > My laptop (different than the nitro): Acer Aspire 5 4700U octacore APU > with built-in graphics. > > Good luck. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1891684 > > Title: > [amdgpu] Screen flickers after resuming from suspend > > Status in linux package in Ubuntu: > Incomplete > Status in xserver-xorg-video-amdgpu package in Ubuntu: > Incomplete > > Bug description: > when computer is coming out of suspension mode, i get terrible screen > flickers. Only way i have worked around this is a reboot. > > This video card is from sapphire > Nitro + SE 5700xt > > ProblemType: Bug > DistroRelease: Ubuntu 20.04 > Package: xorg 1:7.7+19ubuntu14 > ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 > Uname: Linux 5.4.0-42-generic x86_64 > ApportVersion: 2.20.11-0ubuntu27.6 > Architecture: amd64 > BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' > CasperMD5CheckResult: skip > CompositorRunning: None > CurrentDesktop: ubuntu:GNOME > Date: Fri Aug 14 12:16:42 2020 > DistUpgraded: Fresh install > DistroCodename: focal > DistroVariant: ubuntu > GraphicsCard: >Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 > XT / 5700/5700 XT] [1002:731f] (rev c1) (prog-if 00 [VGA controller]) > Subsystem: Sapphire Technology Limited Navi 10 [Radeon RX 5600 > OEM/5600 XT / 5700/5700 XT] [1da2:e410] > InstallationDate: Installed on 2020-06-08 (66 days ago) > InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 > (20200423) > MachineType: System manufacturer System Product Name > ProcEnviron: >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=en_US.UTF-8 >SHELL=/bin/bash > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic > root=UUID=de7b87e0-cf04-4f9f-978e-3646f7e7266d ro quiet splash vt.handoff=7 > SourcePackage: xorg > Symptom: display > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 06/17/2020 > dmi.bios.vendor: American Megatrends Inc. > dmi.bios.version: 2203 > dmi.board.asset.tag: Default string > dmi.board.name: TUF GAMING X570-PLUS > dmi.board.vendor: ASUSTeK COMPUTER INC. > dmi.board.version: Rev X.0x > dmi.chassis.asset.tag: Default string > dmi.chassis.type: 3 > dmi.chassis.vendor: Default string > dmi.chassis.version: Default string > dmi.modalias: > dmi:bvnAmericanMegatrendsInc.:bvr2203:bd06/17/2020:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFGAMINGX570-PLUS:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: > dmi.product.family: To be filled by O.E.M. > dmi.product.name: System Product Name > dmi.product.sku: SKU > dmi.product.version: System Version > dmi.sys.vendor: System manufacturer > version.compiz: compiz N/A > version.libdrm2: libdrm2 2.4.101-2 > version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 > version.libgl1-mesa-glx: libgl1-mesa-glx N/A > version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 > version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A > version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 > version.xserver-xorg-video-intel: xserver-xorg-video-intel > 2:2.99.917+git20200226-1 > version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1891684/+subscriptions > -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1891684 Title: [amdgpu] Screen flickers after resuming from suspend Status in linux package in Ubuntu: Incomplete Status in xserver-xorg-video-amdgpu package in Ubuntu: Incomplete Bug description: when computer is coming out of suspension mode, i get terrible screen flickers. Only way i have worked around this is a reboot. This video card is from sapphire Nitro + SE 5700xt ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None C
Re: [Kernel-packages] [Bug 1891684] Re: screen flickers
i am not recieving a text file when i run the command what am i doing wrong? alt+f2 to bring up command i have rebooted, suspended, reproduced flicker, rebooted then entered verbatim. No text file appears? On Sun, Aug 16, 2020 at 10:40 PM Daniel van Vugt <1891...@bugs.launchpad.net> wrote: > Please: > > 1. Reboot again. > > 2. Suspend, resume, and reproduce the flicker. > > 3. Reboot yet again. > > 4. Run this command: > >journalctl -b-1 > prevboot.txt > >and attach the resulting text file here. > > ** Tags added: amdgpu > > ** Summary changed: > > - screen flickers > + [amdgpu] screen flickers > > ** Tags added: suspend-resume > > ** Package changed: xorg (Ubuntu) => xserver-xorg-video-amdgpu (Ubuntu) > > ** Summary changed: > > - [amdgpu] screen flickers > + [amdgpu] Screen flickers after resuming from suspend > > ** Also affects: linux (Ubuntu) >Importance: Undecided >Status: New > > ** Changed in: linux (Ubuntu) >Status: New => Incomplete > > ** Changed in: xserver-xorg-video-amdgpu (Ubuntu) >Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1891684 > > Title: > [amdgpu] Screen flickers after resuming from suspend > > Status in linux package in Ubuntu: > Incomplete > Status in xserver-xorg-video-amdgpu package in Ubuntu: > Incomplete > > Bug description: > when computer is coming out of suspension mode, i get terrible screen > flickers. Only way i have worked around this is a reboot. > > This video card is from sapphire > Nitro + SE 5700xt > > ProblemType: Bug > DistroRelease: Ubuntu 20.04 > Package: xorg 1:7.7+19ubuntu14 > ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 > Uname: Linux 5.4.0-42-generic x86_64 > ApportVersion: 2.20.11-0ubuntu27.6 > Architecture: amd64 > BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' > CasperMD5CheckResult: skip > CompositorRunning: None > CurrentDesktop: ubuntu:GNOME > Date: Fri Aug 14 12:16:42 2020 > DistUpgraded: Fresh install > DistroCodename: focal > DistroVariant: ubuntu > GraphicsCard: >Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 > XT / 5700/5700 XT] [1002:731f] (rev c1) (prog-if 00 [VGA controller]) > Subsystem: Sapphire Technology Limited Navi 10 [Radeon RX 5600 > OEM/5600 XT / 5700/5700 XT] [1da2:e410] > InstallationDate: Installed on 2020-06-08 (66 days ago) > InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 > (20200423) > MachineType: System manufacturer System Product Name > ProcEnviron: >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=en_US.UTF-8 >SHELL=/bin/bash > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic > root=UUID=de7b87e0-cf04-4f9f-978e-3646f7e7266d ro quiet splash vt.handoff=7 > SourcePackage: xorg > Symptom: display > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 06/17/2020 > dmi.bios.vendor: American Megatrends Inc. > dmi.bios.version: 2203 > dmi.board.asset.tag: Default string > dmi.board.name: TUF GAMING X570-PLUS > dmi.board.vendor: ASUSTeK COMPUTER INC. > dmi.board.version: Rev X.0x > dmi.chassis.asset.tag: Default string > dmi.chassis.type: 3 > dmi.chassis.vendor: Default string > dmi.chassis.version: Default string > dmi.modalias: > dmi:bvnAmericanMegatrendsInc.:bvr2203:bd06/17/2020:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFGAMINGX570-PLUS:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: > dmi.product.family: To be filled by O.E.M. > dmi.product.name: System Product Name > dmi.product.sku: SKU > dmi.product.version: System Version > dmi.sys.vendor: System manufacturer > version.compiz: compiz N/A > version.libdrm2: libdrm2 2.4.101-2 > version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 > version.libgl1-mesa-glx: libgl1-mesa-glx N/A > version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 > version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A > version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 > version.xserver-xorg-video-intel: xserver-xorg-video-intel > 2:2.99.917+git20200226-1 > version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1891684/+subscriptions > -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1891684 Title: [amdgpu] Screen flickers after resuming from suspend Status in linux package in Ubuntu: Incomplete Status in xserver-xorg-video-amdgpu package in Ubuntu: Incomplete Bug description: when computer is coming out of suspension mode, i get terrible screen flickers. Only way i have worked around this
Re: [Kernel-packages] [Bug 1891684] Re: [amdgpu] Screen flickers after resuming from suspend
need a little more help than than. Im new to Ubuntu. I dont know how to navigate On Sun, Aug 16, 2020 at 11:55 PM Daniel van Vugt <1891...@bugs.launchpad.net> wrote: > The file should be created in the directory you ran the command so look > there: > > journalctl -b-1 > prevboot.txt > ls *.txt > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1891684 > > Title: > [amdgpu] Screen flickers after resuming from suspend > > Status in linux package in Ubuntu: > Incomplete > Status in xserver-xorg-video-amdgpu package in Ubuntu: > Incomplete > > Bug description: > when computer is coming out of suspension mode, i get terrible screen > flickers. Only way i have worked around this is a reboot. > > This video card is from sapphire > Nitro + SE 5700xt > > ProblemType: Bug > DistroRelease: Ubuntu 20.04 > Package: xorg 1:7.7+19ubuntu14 > ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 > Uname: Linux 5.4.0-42-generic x86_64 > ApportVersion: 2.20.11-0ubuntu27.6 > Architecture: amd64 > BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' > CasperMD5CheckResult: skip > CompositorRunning: None > CurrentDesktop: ubuntu:GNOME > Date: Fri Aug 14 12:16:42 2020 > DistUpgraded: Fresh install > DistroCodename: focal > DistroVariant: ubuntu > GraphicsCard: >Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 > XT / 5700/5700 XT] [1002:731f] (rev c1) (prog-if 00 [VGA controller]) > Subsystem: Sapphire Technology Limited Navi 10 [Radeon RX 5600 > OEM/5600 XT / 5700/5700 XT] [1da2:e410] > InstallationDate: Installed on 2020-06-08 (66 days ago) > InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 > (20200423) > MachineType: System manufacturer System Product Name > ProcEnviron: >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=en_US.UTF-8 >SHELL=/bin/bash > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic > root=UUID=de7b87e0-cf04-4f9f-978e-3646f7e7266d ro quiet splash vt.handoff=7 > SourcePackage: xorg > Symptom: display > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 06/17/2020 > dmi.bios.vendor: American Megatrends Inc. > dmi.bios.version: 2203 > dmi.board.asset.tag: Default string > dmi.board.name: TUF GAMING X570-PLUS > dmi.board.vendor: ASUSTeK COMPUTER INC. > dmi.board.version: Rev X.0x > dmi.chassis.asset.tag: Default string > dmi.chassis.type: 3 > dmi.chassis.vendor: Default string > dmi.chassis.version: Default string > dmi.modalias: > dmi:bvnAmericanMegatrendsInc.:bvr2203:bd06/17/2020:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFGAMINGX570-PLUS:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: > dmi.product.family: To be filled by O.E.M. > dmi.product.name: System Product Name > dmi.product.sku: SKU > dmi.product.version: System Version > dmi.sys.vendor: System manufacturer > version.compiz: compiz N/A > version.libdrm2: libdrm2 2.4.101-2 > version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 > version.libgl1-mesa-glx: libgl1-mesa-glx N/A > version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 > version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A > version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 > version.xserver-xorg-video-intel: xserver-xorg-video-intel > 2:2.99.917+git20200226-1 > version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1891684/+subscriptions > -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1891684 Title: [amdgpu] Screen flickers after resuming from suspend Status in linux package in Ubuntu: Incomplete Status in xserver-xorg-video-amdgpu package in Ubuntu: Incomplete Bug description: when computer is coming out of suspension mode, i get terrible screen flickers. Only way i have worked around this is a reboot. This video card is from sapphire Nitro + SE 5700xt ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Aug 14 12:16:42 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] [1002:731f] (rev c1) (prog-if 00 [VGA controller]) Subsystem: Sapphire Technology Limi
Re: [Kernel-packages] [Bug 1891684] Re: [amdgpu] Screen flickers after resuming from suspend
Thank you. I dont know how i did not see that before On Mon, Aug 17, 2020 at 12:25 AM Daniel van Vugt <1891...@bugs.launchpad.net> wrote: > Also, please don't use Alt+F2. This command needs to be run in the > Terminal app: > > journalctl -b-1 > prevboot.txt > > But only using the steps from comment #2. And then use the Files app to > retrieve the file. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1891684 > > Title: > [amdgpu] Screen flickers after resuming from suspend > > Status in linux package in Ubuntu: > Incomplete > Status in xserver-xorg-video-amdgpu package in Ubuntu: > Incomplete > > Bug description: > when computer is coming out of suspension mode, i get terrible screen > flickers. Only way i have worked around this is a reboot. > > This video card is from sapphire > Nitro + SE 5700xt > > ProblemType: Bug > DistroRelease: Ubuntu 20.04 > Package: xorg 1:7.7+19ubuntu14 > ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 > Uname: Linux 5.4.0-42-generic x86_64 > ApportVersion: 2.20.11-0ubuntu27.6 > Architecture: amd64 > BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' > CasperMD5CheckResult: skip > CompositorRunning: None > CurrentDesktop: ubuntu:GNOME > Date: Fri Aug 14 12:16:42 2020 > DistUpgraded: Fresh install > DistroCodename: focal > DistroVariant: ubuntu > GraphicsCard: >Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 > XT / 5700/5700 XT] [1002:731f] (rev c1) (prog-if 00 [VGA controller]) > Subsystem: Sapphire Technology Limited Navi 10 [Radeon RX 5600 > OEM/5600 XT / 5700/5700 XT] [1da2:e410] > InstallationDate: Installed on 2020-06-08 (66 days ago) > InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 > (20200423) > MachineType: System manufacturer System Product Name > ProcEnviron: >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=en_US.UTF-8 >SHELL=/bin/bash > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic > root=UUID=de7b87e0-cf04-4f9f-978e-3646f7e7266d ro quiet splash vt.handoff=7 > SourcePackage: xorg > Symptom: display > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 06/17/2020 > dmi.bios.vendor: American Megatrends Inc. > dmi.bios.version: 2203 > dmi.board.asset.tag: Default string > dmi.board.name: TUF GAMING X570-PLUS > dmi.board.vendor: ASUSTeK COMPUTER INC. > dmi.board.version: Rev X.0x > dmi.chassis.asset.tag: Default string > dmi.chassis.type: 3 > dmi.chassis.vendor: Default string > dmi.chassis.version: Default string > dmi.modalias: > dmi:bvnAmericanMegatrendsInc.:bvr2203:bd06/17/2020:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFGAMINGX570-PLUS:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: > dmi.product.family: To be filled by O.E.M. > dmi.product.name: System Product Name > dmi.product.sku: SKU > dmi.product.version: System Version > dmi.sys.vendor: System manufacturer > version.compiz: compiz N/A > version.libdrm2: libdrm2 2.4.101-2 > version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 > version.libgl1-mesa-glx: libgl1-mesa-glx N/A > version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 > version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A > version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 > version.xserver-xorg-video-intel: xserver-xorg-video-intel > 2:2.99.917+git20200226-1 > version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1891684/+subscriptions > ** Attachment added: "prevboot.txt" https://bugs.launchpad.net/bugs/1891684/+attachment/5402050/+files/prevboot.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/1891684 Title: [amdgpu] Screen flickers after resuming from suspend Status in linux package in Ubuntu: Incomplete Status in xserver-xorg-video-amdgpu package in Ubuntu: Incomplete Bug description: when computer is coming out of suspension mode, i get terrible screen flickers. Only way i have worked around this is a reboot. This video card is from sapphire Nitro + SE 5700xt ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Aug 14 12:16:42 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: Adv
[Kernel-packages] [Bug 1176857] Re: Touchpad resolution too coarse on thinkpad X230
Reply to #12 It's an instant showstopper for Windows 10 users as well, suggesting to me that it's a hardware/driver problem. It has so much less resolution compared to my old Samsung R580's touchpad! It's impossible to target handles in Adobe Illustrator or to accurately target enemies in games, not to mention everyday mis-clicks that happen in the OS. It's driving me mad and I'm about to rip the touchpad out and just hack in an R580 pad that I can trust. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1176857 Title: Touchpad resolution too coarse on thinkpad X230 Status in One Hundred Papercuts: Confirmed Status in linux package in Ubuntu: Invalid Status in xserver-xorg-input-synaptics package in Ubuntu: Confirmed Bug description: The thinkpad X230 tablet has three HID for controlling the pointer: mouse, touch screen and touch pad. With mouse and touch screen as inpt devices, I have pixel-exact control of the pointer. In contrast, when using the touch pad as the input device, resolution is very coarse: the pointer jumps in small steps of approx. 5 pixels. This resolution is too coarse, e.g. for controlling graphical user interfaces with small buttons. Very often, when I tap on the touch pad for emulating a left click, the pointer jumps 5 pixels from where it was, causing me to actually click on a different button. (This can be quite annoying. Example: I regularly hit "suspend" instead of "log out" in the system menu). Can the pointer resolution be changed for the touch pad? If so, it should default to pixel-exact resolution. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Mon May 6 13:13:29 2013 DistUpgraded: 2013-04-25 18:13:00,044 WARNING no activity on terminal for 300 seconds (Konfiguration von upstart wird vorbereitet) DistroCodename: raring DistroVariant: ubuntu DkmsStatus: virtualbox, 4.2.10, 3.8.0-19-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:2203] InstallationDate: Installed on 2013-04-12 (23 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MachineType: LENOVO 34382AG MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-19-generic root=/dev/mapper/vg-lv--root ro quiet splash "acpi_osi=!Windows 2012" vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to raring on 2013-04-25 (10 days ago) dmi.bios.date: 02/25/2013 dmi.bios.vendor: LENOVO dmi.bios.version: GCET92WW (2.52 ) dmi.board.asset.tag: Not Available dmi.board.name: 34382AG dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGCET92WW(2.52):bd02/25/2013:svnLENOVO:pn34382AG:pvrThinkPadX230Tablet:rvnLENOVO:rn34382AG:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 34382AG dmi.product.version: ThinkPad X230 Tablet dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.9~daily13.04.18.1~13.04-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.43-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.1.1-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.1.1-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.13.3-0ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2b2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.6-0ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.7-0ubuntu1 xserver.bootTime: Sun May 5 19:49:27 2013 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.13.3-0ubuntu6 xserver.video_driver: intel To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1176857/+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 1627905] Re: Ubuntu can't be installed to certain Lenovo Yoga laptops because the fakeraid storage mode is not supported.
This bug has been solved by Lenovo releasing a new BIOS update for affected Lenovo Yoga laptops that allows the user to put the storage controller into AHCI mode, thus making it visible to Linux and any other OS that the user wants to install. There was also a patch from Intel that adds support for the RAID controller, but there was a long discussion on the Linux Kernel Mailing List where the maintainers of the storage subsystem did not want to merge it because the way Intel implemented this was deemed to be pretty horrible and Intel themselves admitted that it would be better to just install in AHCI mode. Is Ubuntu interested in that patch? It's smallish, but it's likely to never be upstreamed. Users of the affected systems should go to Lenovo's support website, enter their serial number or model number, and download the "Linux Only" BIOS firmware. Then they can go into their BIOS and enable BIOS backflashing to make the BIOS accept the update, otherwise it thinks you're trying to install an older firmware and won't allow it. Once that's done, go back into Windows and double click the firmware exe and let it do its thing (making sure that the laptop is plugged into the wall and on AC power the entire time!!!). Once it's flashed in, you can then enter BIOS setup and switch the SATA controller mode to AHCI instead of RAID. Then you can boot from the Linux Live environment and install to the SSD. At all times, remember that it's easiest to get into boot options and BIOS set-up on a Lenovo laptop by finding the small button next to the power button and pressing it with something like the tip of a pen. This will turn on the computer and immediately take you to startup options. You may also want to disable "quick boot" while you're in the BIOS setup. I did and it doesn't seem to add any appreciable time to the boot procedure, but it gives you more startup options than quick boot does if you require them in the future. Now, with all of this said, I'm going to try/recommend closing this bug since Lenovo begrudgingly fixed it in response to a complaint that I filed with the Illinois Attorney General consumer affairs department, after telling the news all of the preceding weeks that it was all the fault of Linux for "not having drivers". The only real reason to have it in RAID mode was to force Windows to load the Intel RST driver for power policy, and that's irrelevant on Linux (although I do recommend creating a system service that calls powertop and has it auto tune the settings as you can get power usage down roughly 30% over the Linux defaults that way, and having it apply the optimization at every boot is convenient. I found out how to make powertop do this in Ubuntu. I believe they copied the service file from Fedora. https://blog.sleeplessbeastie.eu/2015/08/10/how-to-set-all-tunable- powertop-options-at-system-boot/ Anyway, I threw that in because the obscene power usage that Matthew Garrett talks about goes away if you do this. With the power policy optimization, the run time on my laptop in Ubuntu is comparable to Windows 10. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1627905 Title: Ubuntu can't be installed to certain Lenovo Yoga laptops because the fakeraid storage mode is not supported. Status in linux package in Ubuntu: Triaged Bug description: Several Lenovo Yoga laptops do not allow the user to install any current Linux distributions due to being BIOS-locked to a RAID mode and Linux does not support this. You can boot a Linux live environment, but when you go to install, it will not see the Solid State Drive and it does not appear as a PCI device. The affected models are the Yoga 900 ISK2, 900S, 710S, and 900 ISK for Business, and probably the new Yoga Book and Yoga 910 as well. Lenovo has stated that removing the AHCI option from the BIOS is a feature and that they don't plan to fix this. There have been some blog postings and news articles about this issue lately. Here is the Lenovo Forums topic: https://forums.lenovo.com/t5/Linux-Discussion/Yoga-900-13ISK2-BIOS- update-for-setting-RAID-mode-for-missing/td-p/3339206/highlight/false (Note that this says it is solved, but it is not. Lenovo replied that they won't fix it and that Linux is not supported on these laptops.) Matthew Garrett's blog post is here: https://mjg59.dreamwidth.org/44694.html I approached him with the idea that perhaps the Linux kernel could be modified to reset the hardware and put it into AHCI mode after GRUB loads the kernel (according to him, GRUB doesn't need to be modified because it uses the uEFI firmware's disk access), and then Linux could proceed to boot. Here's what he said: "If you wanted to try that, the best place to do it would be the UEFI setup code in the kernel under arch/x86/boot/compressed/eboot.c - that way you can d
[Kernel-packages] [Bug 1627905] Re: Ubuntu can't be installed to certain Lenovo Yoga laptops because the fakeraid storage mode is not supported.
http://marc.info/?l=linux-ide&m=147709610621480&w=2 There's a link to the patches that Intel submitted. If you go to next in list, you can see the patches and if you go to next in thread, you can follow the ensuing conversation where upstream kernel developers declare it "too ugly to live" and Intel admits that putting the storage in AHCI mode is better. Of course with Lenovo's default BIOS you can't, so no Linux for you! Regardless, does Ubuntu want to merge and maintain this in case there are other laptops out there with ridiculous BIOS settings? It's a distinct possibility that other companies have hardware out there that does this. I doubt that Lenovo will try it again, but you never know.:P I'm probably done buying hardware from OEMs that pull stuff like this and then fighting them later as others apologize for them. If it's not crooked, then it's at least braindead stupid. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1627905 Title: Ubuntu can't be installed to certain Lenovo Yoga laptops because the fakeraid storage mode is not supported. Status in linux package in Ubuntu: Triaged Bug description: Several Lenovo Yoga laptops do not allow the user to install any current Linux distributions due to being BIOS-locked to a RAID mode and Linux does not support this. You can boot a Linux live environment, but when you go to install, it will not see the Solid State Drive and it does not appear as a PCI device. The affected models are the Yoga 900 ISK2, 900S, 710S, and 900 ISK for Business, and probably the new Yoga Book and Yoga 910 as well. Lenovo has stated that removing the AHCI option from the BIOS is a feature and that they don't plan to fix this. There have been some blog postings and news articles about this issue lately. Here is the Lenovo Forums topic: https://forums.lenovo.com/t5/Linux-Discussion/Yoga-900-13ISK2-BIOS- update-for-setting-RAID-mode-for-missing/td-p/3339206/highlight/false (Note that this says it is solved, but it is not. Lenovo replied that they won't fix it and that Linux is not supported on these laptops.) Matthew Garrett's blog post is here: https://mjg59.dreamwidth.org/44694.html I approached him with the idea that perhaps the Linux kernel could be modified to reset the hardware and put it into AHCI mode after GRUB loads the kernel (according to him, GRUB doesn't need to be modified because it uses the uEFI firmware's disk access), and then Linux could proceed to boot. Here's what he said: "If you wanted to try that, the best place to do it would be the UEFI setup code in the kernel under arch/x86/boot/compressed/eboot.c - that way you can do it independent of bootloader. Grub's able to read files anyway since it's using the firmware calls to do that. The power management thing isn't about the SSD itself, it's about ensuring that the controller is programmed correctly so that the entire CPU package can enter deep sleep states. Modern systems should idle at around 4W at most, so small amounts make abig difference here." [...] "If the firmware hasn't locked the control bit and if the hardware is ok with suddenly being reconfigured, sure, that ought to work. Doing it in eboot.c means you're doing it before any PCI enumeration has occurred, which makes it more likely that things will work out well." [...] "I'll take a quick look at the 10-series chipset docs to see if it's documented, and if so I'll throw a quick patch together - but I'm probably not going to try pushing it upstream, I'm afraid. If it does work, I'm fine with anybody else doing so." I heaven't heard anything back lately, so I am putting this in a bug report so that the Ubuntu maintainers are aware of the issue. It seems like a few lines of kernel code are all that is really required to fix this and restore the ability of Linux distributions to be installed on half a dozen laptops (probably more to come, since Lenovo says that the industry is moving to this!). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1627905/+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 1627905] Re: Ubuntu can't be installed to certain Lenovo Yoga laptops because the fakeraid storage mode is not supported.
apport information ** Tags added: apport-collected zesty ** Description changed: Several Lenovo Yoga laptops do not allow the user to install any current Linux distributions due to being BIOS-locked to a RAID mode and Linux does not support this. You can boot a Linux live environment, but when you go to install, it will not see the Solid State Drive and it does not appear as a PCI device. The affected models are the Yoga 900 ISK2, 900S, 710S, and 900 ISK for Business, and probably the new Yoga Book and Yoga 910 as well. Lenovo has stated that removing the AHCI option from the BIOS is a feature and that they don't plan to fix this. There have been some blog postings and news articles about this issue lately. Here is the Lenovo Forums topic: https://forums.lenovo.com/t5/Linux-Discussion/Yoga-900-13ISK2-BIOS- update-for-setting-RAID-mode-for-missing/td-p/3339206/highlight/false (Note that this says it is solved, but it is not. Lenovo replied that they won't fix it and that Linux is not supported on these laptops.) Matthew Garrett's blog post is here: https://mjg59.dreamwidth.org/44694.html I approached him with the idea that perhaps the Linux kernel could be modified to reset the hardware and put it into AHCI mode after GRUB loads the kernel (according to him, GRUB doesn't need to be modified because it uses the uEFI firmware's disk access), and then Linux could proceed to boot. Here's what he said: "If you wanted to try that, the best place to do it would be the UEFI setup code in the kernel under arch/x86/boot/compressed/eboot.c - that way you can do it independent of bootloader. Grub's able to read files anyway since it's using the firmware calls to do that. The power management thing isn't about the SSD itself, it's about ensuring that the controller is programmed correctly so that the entire CPU package can enter deep sleep states. Modern systems should idle at around 4W at most, so small amounts make abig difference here." [...] "If the firmware hasn't locked the control bit and if the hardware is ok with suddenly being reconfigured, sure, that ought to work. Doing it in eboot.c means you're doing it before any PCI enumeration has occurred, which makes it more likely that things will work out well." [...] "I'll take a quick look at the 10-series chipset docs to see if it's documented, and if so I'll throw a quick patch together - but I'm probably not going to try pushing it upstream, I'm afraid. If it does work, I'm fine with anybody else doing so." I heaven't heard anything back lately, so I am putting this in a bug report so that the Ubuntu maintainers are aware of the issue. - It seems like a few lines of kernel code are all that is really required - to fix this and restore the ability of Linux distributions to be - installed on half a dozen laptops (probably more to come, since Lenovo - says that the industry is moving to this!). + It seems like a few lines of kernel code are all that is really required to fix this and restore the ability of Linux distributions to be installed on half a dozen laptops (probably more to come, since Lenovo says that the industry is moving to this!). + --- + ApportVersion: 2.20.4-0ubuntu4.1 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: ryan 1604 F pulseaudio + CurrentDesktop: GNOME + DistroRelease: Ubuntu 17.04 + EcryptfsInUse: Yes + InstallationDate: Installed on 2017-05-30 (2 days ago) + InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) + Lsusb: + Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 001 Device 003: ID 8087:0a2b Intel Corp. + Bus 001 Device 002: ID 5986:068c Acer, Inc + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + MachineType: LENOVO 80UE + Package: linux (not installed) + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcFB: 0 inteldrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-22-generic.efi.signed root=UUID=3ee79c46-724b-41b5-8c42-44458297de6a ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 + RelatedPackageVersions: + linux-restricted-modules-4.10.0-22-generic N/A + linux-backports-modules-4.10.0-22-generic N/A + linux-firmware 1.164.1 + Tags: zesty + Uname: Linux 4.10.0-22-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 10/14/2016 + dmi.bios.vendor: LENOVO + dmi.bios.version: 2UCN10T + dmi.board.asset.tag: NO Asset Tag + dmi.board.
[Kernel-packages] [Bug 1627905] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1627905/+attachment/4887128/+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/1627905 Title: Ubuntu can't be installed to certain Lenovo Yoga laptops because the fakeraid storage mode is not supported. Status in linux package in Ubuntu: Triaged Bug description: Several Lenovo Yoga laptops do not allow the user to install any current Linux distributions due to being BIOS-locked to a RAID mode and Linux does not support this. You can boot a Linux live environment, but when you go to install, it will not see the Solid State Drive and it does not appear as a PCI device. The affected models are the Yoga 900 ISK2, 900S, 710S, and 900 ISK for Business, and probably the new Yoga Book and Yoga 910 as well. Lenovo has stated that removing the AHCI option from the BIOS is a feature and that they don't plan to fix this. There have been some blog postings and news articles about this issue lately. Here is the Lenovo Forums topic: https://forums.lenovo.com/t5/Linux-Discussion/Yoga-900-13ISK2-BIOS- update-for-setting-RAID-mode-for-missing/td-p/3339206/highlight/false (Note that this says it is solved, but it is not. Lenovo replied that they won't fix it and that Linux is not supported on these laptops.) Matthew Garrett's blog post is here: https://mjg59.dreamwidth.org/44694.html I approached him with the idea that perhaps the Linux kernel could be modified to reset the hardware and put it into AHCI mode after GRUB loads the kernel (according to him, GRUB doesn't need to be modified because it uses the uEFI firmware's disk access), and then Linux could proceed to boot. Here's what he said: "If you wanted to try that, the best place to do it would be the UEFI setup code in the kernel under arch/x86/boot/compressed/eboot.c - that way you can do it independent of bootloader. Grub's able to read files anyway since it's using the firmware calls to do that. The power management thing isn't about the SSD itself, it's about ensuring that the controller is programmed correctly so that the entire CPU package can enter deep sleep states. Modern systems should idle at around 4W at most, so small amounts make abig difference here." [...] "If the firmware hasn't locked the control bit and if the hardware is ok with suddenly being reconfigured, sure, that ought to work. Doing it in eboot.c means you're doing it before any PCI enumeration has occurred, which makes it more likely that things will work out well." [...] "I'll take a quick look at the 10-series chipset docs to see if it's documented, and if so I'll throw a quick patch together - but I'm probably not going to try pushing it upstream, I'm afraid. If it does work, I'm fine with anybody else doing so." I heaven't heard anything back lately, so I am putting this in a bug report so that the Ubuntu maintainers are aware of the issue. It seems like a few lines of kernel code are all that is really required to fix this and restore the ability of Linux distributions to be installed on half a dozen laptops (probably more to come, since Lenovo says that the industry is moving to this!). --- ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ryan 1604 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 17.04 EcryptfsInUse: Yes InstallationDate: Installed on 2017-05-30 (2 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 5986:068c Acer, Inc Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80UE Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-22-generic.efi.signed root=UUID=3ee79c46-724b-41b5-8c42-44458297de6a ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 RelatedPackageVersions: linux-restricted-modules-4.10.0-22-generic N/A linux-backports-modules-4.10.0-22-generic N/A linux-firmware 1.164.1 Tags: zesty Uname: Linux 4.10.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios
[Kernel-packages] [Bug 1627905] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1627905/+attachment/4887126/+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/1627905 Title: Ubuntu can't be installed to certain Lenovo Yoga laptops because the fakeraid storage mode is not supported. Status in linux package in Ubuntu: Triaged Bug description: Several Lenovo Yoga laptops do not allow the user to install any current Linux distributions due to being BIOS-locked to a RAID mode and Linux does not support this. You can boot a Linux live environment, but when you go to install, it will not see the Solid State Drive and it does not appear as a PCI device. The affected models are the Yoga 900 ISK2, 900S, 710S, and 900 ISK for Business, and probably the new Yoga Book and Yoga 910 as well. Lenovo has stated that removing the AHCI option from the BIOS is a feature and that they don't plan to fix this. There have been some blog postings and news articles about this issue lately. Here is the Lenovo Forums topic: https://forums.lenovo.com/t5/Linux-Discussion/Yoga-900-13ISK2-BIOS- update-for-setting-RAID-mode-for-missing/td-p/3339206/highlight/false (Note that this says it is solved, but it is not. Lenovo replied that they won't fix it and that Linux is not supported on these laptops.) Matthew Garrett's blog post is here: https://mjg59.dreamwidth.org/44694.html I approached him with the idea that perhaps the Linux kernel could be modified to reset the hardware and put it into AHCI mode after GRUB loads the kernel (according to him, GRUB doesn't need to be modified because it uses the uEFI firmware's disk access), and then Linux could proceed to boot. Here's what he said: "If you wanted to try that, the best place to do it would be the UEFI setup code in the kernel under arch/x86/boot/compressed/eboot.c - that way you can do it independent of bootloader. Grub's able to read files anyway since it's using the firmware calls to do that. The power management thing isn't about the SSD itself, it's about ensuring that the controller is programmed correctly so that the entire CPU package can enter deep sleep states. Modern systems should idle at around 4W at most, so small amounts make abig difference here." [...] "If the firmware hasn't locked the control bit and if the hardware is ok with suddenly being reconfigured, sure, that ought to work. Doing it in eboot.c means you're doing it before any PCI enumeration has occurred, which makes it more likely that things will work out well." [...] "I'll take a quick look at the 10-series chipset docs to see if it's documented, and if so I'll throw a quick patch together - but I'm probably not going to try pushing it upstream, I'm afraid. If it does work, I'm fine with anybody else doing so." I heaven't heard anything back lately, so I am putting this in a bug report so that the Ubuntu maintainers are aware of the issue. It seems like a few lines of kernel code are all that is really required to fix this and restore the ability of Linux distributions to be installed on half a dozen laptops (probably more to come, since Lenovo says that the industry is moving to this!). --- ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ryan 1604 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 17.04 EcryptfsInUse: Yes InstallationDate: Installed on 2017-05-30 (2 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 5986:068c Acer, Inc Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80UE Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-22-generic.efi.signed root=UUID=3ee79c46-724b-41b5-8c42-44458297de6a ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 RelatedPackageVersions: linux-restricted-modules-4.10.0-22-generic N/A linux-backports-modules-4.10.0-22-generic N/A linux-firmware 1.164.1 Tags: zesty Uname: Linux 4.10.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 1
[Kernel-packages] [Bug 1627905] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1627905/+attachment/4887118/+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/1627905 Title: Ubuntu can't be installed to certain Lenovo Yoga laptops because the fakeraid storage mode is not supported. Status in linux package in Ubuntu: Triaged Bug description: Several Lenovo Yoga laptops do not allow the user to install any current Linux distributions due to being BIOS-locked to a RAID mode and Linux does not support this. You can boot a Linux live environment, but when you go to install, it will not see the Solid State Drive and it does not appear as a PCI device. The affected models are the Yoga 900 ISK2, 900S, 710S, and 900 ISK for Business, and probably the new Yoga Book and Yoga 910 as well. Lenovo has stated that removing the AHCI option from the BIOS is a feature and that they don't plan to fix this. There have been some blog postings and news articles about this issue lately. Here is the Lenovo Forums topic: https://forums.lenovo.com/t5/Linux-Discussion/Yoga-900-13ISK2-BIOS- update-for-setting-RAID-mode-for-missing/td-p/3339206/highlight/false (Note that this says it is solved, but it is not. Lenovo replied that they won't fix it and that Linux is not supported on these laptops.) Matthew Garrett's blog post is here: https://mjg59.dreamwidth.org/44694.html I approached him with the idea that perhaps the Linux kernel could be modified to reset the hardware and put it into AHCI mode after GRUB loads the kernel (according to him, GRUB doesn't need to be modified because it uses the uEFI firmware's disk access), and then Linux could proceed to boot. Here's what he said: "If you wanted to try that, the best place to do it would be the UEFI setup code in the kernel under arch/x86/boot/compressed/eboot.c - that way you can do it independent of bootloader. Grub's able to read files anyway since it's using the firmware calls to do that. The power management thing isn't about the SSD itself, it's about ensuring that the controller is programmed correctly so that the entire CPU package can enter deep sleep states. Modern systems should idle at around 4W at most, so small amounts make abig difference here." [...] "If the firmware hasn't locked the control bit and if the hardware is ok with suddenly being reconfigured, sure, that ought to work. Doing it in eboot.c means you're doing it before any PCI enumeration has occurred, which makes it more likely that things will work out well." [...] "I'll take a quick look at the 10-series chipset docs to see if it's documented, and if so I'll throw a quick patch together - but I'm probably not going to try pushing it upstream, I'm afraid. If it does work, I'm fine with anybody else doing so." I heaven't heard anything back lately, so I am putting this in a bug report so that the Ubuntu maintainers are aware of the issue. It seems like a few lines of kernel code are all that is really required to fix this and restore the ability of Linux distributions to be installed on half a dozen laptops (probably more to come, since Lenovo says that the industry is moving to this!). --- ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ryan 1604 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 17.04 EcryptfsInUse: Yes InstallationDate: Installed on 2017-05-30 (2 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 5986:068c Acer, Inc Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80UE Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-22-generic.efi.signed root=UUID=3ee79c46-724b-41b5-8c42-44458297de6a ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 RelatedPackageVersions: linux-restricted-modules-4.10.0-22-generic N/A linux-backports-modules-4.10.0-22-generic N/A linux-firmware 1.164.1 Tags: zesty Uname: Linux 4.10.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios
[Kernel-packages] [Bug 1627905] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1627905/+attachment/4887124/+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/1627905 Title: Ubuntu can't be installed to certain Lenovo Yoga laptops because the fakeraid storage mode is not supported. Status in linux package in Ubuntu: Triaged Bug description: Several Lenovo Yoga laptops do not allow the user to install any current Linux distributions due to being BIOS-locked to a RAID mode and Linux does not support this. You can boot a Linux live environment, but when you go to install, it will not see the Solid State Drive and it does not appear as a PCI device. The affected models are the Yoga 900 ISK2, 900S, 710S, and 900 ISK for Business, and probably the new Yoga Book and Yoga 910 as well. Lenovo has stated that removing the AHCI option from the BIOS is a feature and that they don't plan to fix this. There have been some blog postings and news articles about this issue lately. Here is the Lenovo Forums topic: https://forums.lenovo.com/t5/Linux-Discussion/Yoga-900-13ISK2-BIOS- update-for-setting-RAID-mode-for-missing/td-p/3339206/highlight/false (Note that this says it is solved, but it is not. Lenovo replied that they won't fix it and that Linux is not supported on these laptops.) Matthew Garrett's blog post is here: https://mjg59.dreamwidth.org/44694.html I approached him with the idea that perhaps the Linux kernel could be modified to reset the hardware and put it into AHCI mode after GRUB loads the kernel (according to him, GRUB doesn't need to be modified because it uses the uEFI firmware's disk access), and then Linux could proceed to boot. Here's what he said: "If you wanted to try that, the best place to do it would be the UEFI setup code in the kernel under arch/x86/boot/compressed/eboot.c - that way you can do it independent of bootloader. Grub's able to read files anyway since it's using the firmware calls to do that. The power management thing isn't about the SSD itself, it's about ensuring that the controller is programmed correctly so that the entire CPU package can enter deep sleep states. Modern systems should idle at around 4W at most, so small amounts make abig difference here." [...] "If the firmware hasn't locked the control bit and if the hardware is ok with suddenly being reconfigured, sure, that ought to work. Doing it in eboot.c means you're doing it before any PCI enumeration has occurred, which makes it more likely that things will work out well." [...] "I'll take a quick look at the 10-series chipset docs to see if it's documented, and if so I'll throw a quick patch together - but I'm probably not going to try pushing it upstream, I'm afraid. If it does work, I'm fine with anybody else doing so." I heaven't heard anything back lately, so I am putting this in a bug report so that the Ubuntu maintainers are aware of the issue. It seems like a few lines of kernel code are all that is really required to fix this and restore the ability of Linux distributions to be installed on half a dozen laptops (probably more to come, since Lenovo says that the industry is moving to this!). --- ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ryan 1604 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 17.04 EcryptfsInUse: Yes InstallationDate: Installed on 2017-05-30 (2 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 5986:068c Acer, Inc Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80UE Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-22-generic.efi.signed root=UUID=3ee79c46-724b-41b5-8c42-44458297de6a ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 RelatedPackageVersions: linux-restricted-modules-4.10.0-22-generic N/A linux-backports-modules-4.10.0-22-generic N/A linux-firmware 1.164.1 Tags: zesty Uname: Linux 4.10.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios
[Kernel-packages] [Bug 1627905] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1627905/+attachment/4887117/+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/1627905 Title: Ubuntu can't be installed to certain Lenovo Yoga laptops because the fakeraid storage mode is not supported. Status in linux package in Ubuntu: Triaged Bug description: Several Lenovo Yoga laptops do not allow the user to install any current Linux distributions due to being BIOS-locked to a RAID mode and Linux does not support this. You can boot a Linux live environment, but when you go to install, it will not see the Solid State Drive and it does not appear as a PCI device. The affected models are the Yoga 900 ISK2, 900S, 710S, and 900 ISK for Business, and probably the new Yoga Book and Yoga 910 as well. Lenovo has stated that removing the AHCI option from the BIOS is a feature and that they don't plan to fix this. There have been some blog postings and news articles about this issue lately. Here is the Lenovo Forums topic: https://forums.lenovo.com/t5/Linux-Discussion/Yoga-900-13ISK2-BIOS- update-for-setting-RAID-mode-for-missing/td-p/3339206/highlight/false (Note that this says it is solved, but it is not. Lenovo replied that they won't fix it and that Linux is not supported on these laptops.) Matthew Garrett's blog post is here: https://mjg59.dreamwidth.org/44694.html I approached him with the idea that perhaps the Linux kernel could be modified to reset the hardware and put it into AHCI mode after GRUB loads the kernel (according to him, GRUB doesn't need to be modified because it uses the uEFI firmware's disk access), and then Linux could proceed to boot. Here's what he said: "If you wanted to try that, the best place to do it would be the UEFI setup code in the kernel under arch/x86/boot/compressed/eboot.c - that way you can do it independent of bootloader. Grub's able to read files anyway since it's using the firmware calls to do that. The power management thing isn't about the SSD itself, it's about ensuring that the controller is programmed correctly so that the entire CPU package can enter deep sleep states. Modern systems should idle at around 4W at most, so small amounts make abig difference here." [...] "If the firmware hasn't locked the control bit and if the hardware is ok with suddenly being reconfigured, sure, that ought to work. Doing it in eboot.c means you're doing it before any PCI enumeration has occurred, which makes it more likely that things will work out well." [...] "I'll take a quick look at the 10-series chipset docs to see if it's documented, and if so I'll throw a quick patch together - but I'm probably not going to try pushing it upstream, I'm afraid. If it does work, I'm fine with anybody else doing so." I heaven't heard anything back lately, so I am putting this in a bug report so that the Ubuntu maintainers are aware of the issue. It seems like a few lines of kernel code are all that is really required to fix this and restore the ability of Linux distributions to be installed on half a dozen laptops (probably more to come, since Lenovo says that the industry is moving to this!). --- ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ryan 1604 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 17.04 EcryptfsInUse: Yes InstallationDate: Installed on 2017-05-30 (2 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 5986:068c Acer, Inc Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80UE Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-22-generic.efi.signed root=UUID=3ee79c46-724b-41b5-8c42-44458297de6a ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 RelatedPackageVersions: linux-restricted-modules-4.10.0-22-generic N/A linux-backports-modules-4.10.0-22-generic N/A linux-firmware 1.164.1 Tags: zesty Uname: Linux 4.10.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUplo
[Kernel-packages] [Bug 1627905] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1627905/+attachment/4887120/+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/1627905 Title: Ubuntu can't be installed to certain Lenovo Yoga laptops because the fakeraid storage mode is not supported. Status in linux package in Ubuntu: Triaged Bug description: Several Lenovo Yoga laptops do not allow the user to install any current Linux distributions due to being BIOS-locked to a RAID mode and Linux does not support this. You can boot a Linux live environment, but when you go to install, it will not see the Solid State Drive and it does not appear as a PCI device. The affected models are the Yoga 900 ISK2, 900S, 710S, and 900 ISK for Business, and probably the new Yoga Book and Yoga 910 as well. Lenovo has stated that removing the AHCI option from the BIOS is a feature and that they don't plan to fix this. There have been some blog postings and news articles about this issue lately. Here is the Lenovo Forums topic: https://forums.lenovo.com/t5/Linux-Discussion/Yoga-900-13ISK2-BIOS- update-for-setting-RAID-mode-for-missing/td-p/3339206/highlight/false (Note that this says it is solved, but it is not. Lenovo replied that they won't fix it and that Linux is not supported on these laptops.) Matthew Garrett's blog post is here: https://mjg59.dreamwidth.org/44694.html I approached him with the idea that perhaps the Linux kernel could be modified to reset the hardware and put it into AHCI mode after GRUB loads the kernel (according to him, GRUB doesn't need to be modified because it uses the uEFI firmware's disk access), and then Linux could proceed to boot. Here's what he said: "If you wanted to try that, the best place to do it would be the UEFI setup code in the kernel under arch/x86/boot/compressed/eboot.c - that way you can do it independent of bootloader. Grub's able to read files anyway since it's using the firmware calls to do that. The power management thing isn't about the SSD itself, it's about ensuring that the controller is programmed correctly so that the entire CPU package can enter deep sleep states. Modern systems should idle at around 4W at most, so small amounts make abig difference here." [...] "If the firmware hasn't locked the control bit and if the hardware is ok with suddenly being reconfigured, sure, that ought to work. Doing it in eboot.c means you're doing it before any PCI enumeration has occurred, which makes it more likely that things will work out well." [...] "I'll take a quick look at the 10-series chipset docs to see if it's documented, and if so I'll throw a quick patch together - but I'm probably not going to try pushing it upstream, I'm afraid. If it does work, I'm fine with anybody else doing so." I heaven't heard anything back lately, so I am putting this in a bug report so that the Ubuntu maintainers are aware of the issue. It seems like a few lines of kernel code are all that is really required to fix this and restore the ability of Linux distributions to be installed on half a dozen laptops (probably more to come, since Lenovo says that the industry is moving to this!). --- ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ryan 1604 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 17.04 EcryptfsInUse: Yes InstallationDate: Installed on 2017-05-30 (2 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 5986:068c Acer, Inc Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80UE Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-22-generic.efi.signed root=UUID=3ee79c46-724b-41b5-8c42-44458297de6a ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 RelatedPackageVersions: linux-restricted-modules-4.10.0-22-generic N/A linux-backports-modules-4.10.0-22-generic N/A linux-firmware 1.164.1 Tags: zesty Uname: Linux 4.10.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 1
[Kernel-packages] [Bug 1627905] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1627905/+attachment/4887123/+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/1627905 Title: Ubuntu can't be installed to certain Lenovo Yoga laptops because the fakeraid storage mode is not supported. Status in linux package in Ubuntu: Triaged Bug description: Several Lenovo Yoga laptops do not allow the user to install any current Linux distributions due to being BIOS-locked to a RAID mode and Linux does not support this. You can boot a Linux live environment, but when you go to install, it will not see the Solid State Drive and it does not appear as a PCI device. The affected models are the Yoga 900 ISK2, 900S, 710S, and 900 ISK for Business, and probably the new Yoga Book and Yoga 910 as well. Lenovo has stated that removing the AHCI option from the BIOS is a feature and that they don't plan to fix this. There have been some blog postings and news articles about this issue lately. Here is the Lenovo Forums topic: https://forums.lenovo.com/t5/Linux-Discussion/Yoga-900-13ISK2-BIOS- update-for-setting-RAID-mode-for-missing/td-p/3339206/highlight/false (Note that this says it is solved, but it is not. Lenovo replied that they won't fix it and that Linux is not supported on these laptops.) Matthew Garrett's blog post is here: https://mjg59.dreamwidth.org/44694.html I approached him with the idea that perhaps the Linux kernel could be modified to reset the hardware and put it into AHCI mode after GRUB loads the kernel (according to him, GRUB doesn't need to be modified because it uses the uEFI firmware's disk access), and then Linux could proceed to boot. Here's what he said: "If you wanted to try that, the best place to do it would be the UEFI setup code in the kernel under arch/x86/boot/compressed/eboot.c - that way you can do it independent of bootloader. Grub's able to read files anyway since it's using the firmware calls to do that. The power management thing isn't about the SSD itself, it's about ensuring that the controller is programmed correctly so that the entire CPU package can enter deep sleep states. Modern systems should idle at around 4W at most, so small amounts make abig difference here." [...] "If the firmware hasn't locked the control bit and if the hardware is ok with suddenly being reconfigured, sure, that ought to work. Doing it in eboot.c means you're doing it before any PCI enumeration has occurred, which makes it more likely that things will work out well." [...] "I'll take a quick look at the 10-series chipset docs to see if it's documented, and if so I'll throw a quick patch together - but I'm probably not going to try pushing it upstream, I'm afraid. If it does work, I'm fine with anybody else doing so." I heaven't heard anything back lately, so I am putting this in a bug report so that the Ubuntu maintainers are aware of the issue. It seems like a few lines of kernel code are all that is really required to fix this and restore the ability of Linux distributions to be installed on half a dozen laptops (probably more to come, since Lenovo says that the industry is moving to this!). --- ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ryan 1604 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 17.04 EcryptfsInUse: Yes InstallationDate: Installed on 2017-05-30 (2 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 5986:068c Acer, Inc Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80UE Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-22-generic.efi.signed root=UUID=3ee79c46-724b-41b5-8c42-44458297de6a ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 RelatedPackageVersions: linux-restricted-modules-4.10.0-22-generic N/A linux-backports-modules-4.10.0-22-generic N/A linux-firmware 1.164.1 Tags: zesty Uname: Linux 4.10.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUplo
[Kernel-packages] [Bug 1627905] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1627905/+attachment/4887116/+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/1627905 Title: Ubuntu can't be installed to certain Lenovo Yoga laptops because the fakeraid storage mode is not supported. Status in linux package in Ubuntu: Triaged Bug description: Several Lenovo Yoga laptops do not allow the user to install any current Linux distributions due to being BIOS-locked to a RAID mode and Linux does not support this. You can boot a Linux live environment, but when you go to install, it will not see the Solid State Drive and it does not appear as a PCI device. The affected models are the Yoga 900 ISK2, 900S, 710S, and 900 ISK for Business, and probably the new Yoga Book and Yoga 910 as well. Lenovo has stated that removing the AHCI option from the BIOS is a feature and that they don't plan to fix this. There have been some blog postings and news articles about this issue lately. Here is the Lenovo Forums topic: https://forums.lenovo.com/t5/Linux-Discussion/Yoga-900-13ISK2-BIOS- update-for-setting-RAID-mode-for-missing/td-p/3339206/highlight/false (Note that this says it is solved, but it is not. Lenovo replied that they won't fix it and that Linux is not supported on these laptops.) Matthew Garrett's blog post is here: https://mjg59.dreamwidth.org/44694.html I approached him with the idea that perhaps the Linux kernel could be modified to reset the hardware and put it into AHCI mode after GRUB loads the kernel (according to him, GRUB doesn't need to be modified because it uses the uEFI firmware's disk access), and then Linux could proceed to boot. Here's what he said: "If you wanted to try that, the best place to do it would be the UEFI setup code in the kernel under arch/x86/boot/compressed/eboot.c - that way you can do it independent of bootloader. Grub's able to read files anyway since it's using the firmware calls to do that. The power management thing isn't about the SSD itself, it's about ensuring that the controller is programmed correctly so that the entire CPU package can enter deep sleep states. Modern systems should idle at around 4W at most, so small amounts make abig difference here." [...] "If the firmware hasn't locked the control bit and if the hardware is ok with suddenly being reconfigured, sure, that ought to work. Doing it in eboot.c means you're doing it before any PCI enumeration has occurred, which makes it more likely that things will work out well." [...] "I'll take a quick look at the 10-series chipset docs to see if it's documented, and if so I'll throw a quick patch together - but I'm probably not going to try pushing it upstream, I'm afraid. If it does work, I'm fine with anybody else doing so." I heaven't heard anything back lately, so I am putting this in a bug report so that the Ubuntu maintainers are aware of the issue. It seems like a few lines of kernel code are all that is really required to fix this and restore the ability of Linux distributions to be installed on half a dozen laptops (probably more to come, since Lenovo says that the industry is moving to this!). --- ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ryan 1604 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 17.04 EcryptfsInUse: Yes InstallationDate: Installed on 2017-05-30 (2 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 5986:068c Acer, Inc Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80UE Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-22-generic.efi.signed root=UUID=3ee79c46-724b-41b5-8c42-44458297de6a ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 RelatedPackageVersions: linux-restricted-modules-4.10.0-22-generic N/A linux-backports-modules-4.10.0-22-generic N/A linux-firmware 1.164.1 Tags: zesty Uname: Linux 4.10.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 1
[Kernel-packages] [Bug 1627905] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1627905/+attachment/4887127/+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/1627905 Title: Ubuntu can't be installed to certain Lenovo Yoga laptops because the fakeraid storage mode is not supported. Status in linux package in Ubuntu: Triaged Bug description: Several Lenovo Yoga laptops do not allow the user to install any current Linux distributions due to being BIOS-locked to a RAID mode and Linux does not support this. You can boot a Linux live environment, but when you go to install, it will not see the Solid State Drive and it does not appear as a PCI device. The affected models are the Yoga 900 ISK2, 900S, 710S, and 900 ISK for Business, and probably the new Yoga Book and Yoga 910 as well. Lenovo has stated that removing the AHCI option from the BIOS is a feature and that they don't plan to fix this. There have been some blog postings and news articles about this issue lately. Here is the Lenovo Forums topic: https://forums.lenovo.com/t5/Linux-Discussion/Yoga-900-13ISK2-BIOS- update-for-setting-RAID-mode-for-missing/td-p/3339206/highlight/false (Note that this says it is solved, but it is not. Lenovo replied that they won't fix it and that Linux is not supported on these laptops.) Matthew Garrett's blog post is here: https://mjg59.dreamwidth.org/44694.html I approached him with the idea that perhaps the Linux kernel could be modified to reset the hardware and put it into AHCI mode after GRUB loads the kernel (according to him, GRUB doesn't need to be modified because it uses the uEFI firmware's disk access), and then Linux could proceed to boot. Here's what he said: "If you wanted to try that, the best place to do it would be the UEFI setup code in the kernel under arch/x86/boot/compressed/eboot.c - that way you can do it independent of bootloader. Grub's able to read files anyway since it's using the firmware calls to do that. The power management thing isn't about the SSD itself, it's about ensuring that the controller is programmed correctly so that the entire CPU package can enter deep sleep states. Modern systems should idle at around 4W at most, so small amounts make abig difference here." [...] "If the firmware hasn't locked the control bit and if the hardware is ok with suddenly being reconfigured, sure, that ought to work. Doing it in eboot.c means you're doing it before any PCI enumeration has occurred, which makes it more likely that things will work out well." [...] "I'll take a quick look at the 10-series chipset docs to see if it's documented, and if so I'll throw a quick patch together - but I'm probably not going to try pushing it upstream, I'm afraid. If it does work, I'm fine with anybody else doing so." I heaven't heard anything back lately, so I am putting this in a bug report so that the Ubuntu maintainers are aware of the issue. It seems like a few lines of kernel code are all that is really required to fix this and restore the ability of Linux distributions to be installed on half a dozen laptops (probably more to come, since Lenovo says that the industry is moving to this!). --- ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ryan 1604 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 17.04 EcryptfsInUse: Yes InstallationDate: Installed on 2017-05-30 (2 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 5986:068c Acer, Inc Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80UE Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-22-generic.efi.signed root=UUID=3ee79c46-724b-41b5-8c42-44458297de6a ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 RelatedPackageVersions: linux-restricted-modules-4.10.0-22-generic N/A linux-backports-modules-4.10.0-22-generic N/A linux-firmware 1.164.1 Tags: zesty Uname: Linux 4.10.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 1
[Kernel-packages] [Bug 1627905] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1627905/+attachment/4887125/+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/1627905 Title: Ubuntu can't be installed to certain Lenovo Yoga laptops because the fakeraid storage mode is not supported. Status in linux package in Ubuntu: Triaged Bug description: Several Lenovo Yoga laptops do not allow the user to install any current Linux distributions due to being BIOS-locked to a RAID mode and Linux does not support this. You can boot a Linux live environment, but when you go to install, it will not see the Solid State Drive and it does not appear as a PCI device. The affected models are the Yoga 900 ISK2, 900S, 710S, and 900 ISK for Business, and probably the new Yoga Book and Yoga 910 as well. Lenovo has stated that removing the AHCI option from the BIOS is a feature and that they don't plan to fix this. There have been some blog postings and news articles about this issue lately. Here is the Lenovo Forums topic: https://forums.lenovo.com/t5/Linux-Discussion/Yoga-900-13ISK2-BIOS- update-for-setting-RAID-mode-for-missing/td-p/3339206/highlight/false (Note that this says it is solved, but it is not. Lenovo replied that they won't fix it and that Linux is not supported on these laptops.) Matthew Garrett's blog post is here: https://mjg59.dreamwidth.org/44694.html I approached him with the idea that perhaps the Linux kernel could be modified to reset the hardware and put it into AHCI mode after GRUB loads the kernel (according to him, GRUB doesn't need to be modified because it uses the uEFI firmware's disk access), and then Linux could proceed to boot. Here's what he said: "If you wanted to try that, the best place to do it would be the UEFI setup code in the kernel under arch/x86/boot/compressed/eboot.c - that way you can do it independent of bootloader. Grub's able to read files anyway since it's using the firmware calls to do that. The power management thing isn't about the SSD itself, it's about ensuring that the controller is programmed correctly so that the entire CPU package can enter deep sleep states. Modern systems should idle at around 4W at most, so small amounts make abig difference here." [...] "If the firmware hasn't locked the control bit and if the hardware is ok with suddenly being reconfigured, sure, that ought to work. Doing it in eboot.c means you're doing it before any PCI enumeration has occurred, which makes it more likely that things will work out well." [...] "I'll take a quick look at the 10-series chipset docs to see if it's documented, and if so I'll throw a quick patch together - but I'm probably not going to try pushing it upstream, I'm afraid. If it does work, I'm fine with anybody else doing so." I heaven't heard anything back lately, so I am putting this in a bug report so that the Ubuntu maintainers are aware of the issue. It seems like a few lines of kernel code are all that is really required to fix this and restore the ability of Linux distributions to be installed on half a dozen laptops (probably more to come, since Lenovo says that the industry is moving to this!). --- ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ryan 1604 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 17.04 EcryptfsInUse: Yes InstallationDate: Installed on 2017-05-30 (2 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 5986:068c Acer, Inc Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80UE Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-22-generic.efi.signed root=UUID=3ee79c46-724b-41b5-8c42-44458297de6a ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 RelatedPackageVersions: linux-restricted-modules-4.10.0-22-generic N/A linux-backports-modules-4.10.0-22-generic N/A linux-firmware 1.164.1 Tags: zesty Uname: Linux 4.10.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios
[Kernel-packages] [Bug 1627905] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1627905/+attachment/4887121/+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/1627905 Title: Ubuntu can't be installed to certain Lenovo Yoga laptops because the fakeraid storage mode is not supported. Status in linux package in Ubuntu: Triaged Bug description: Several Lenovo Yoga laptops do not allow the user to install any current Linux distributions due to being BIOS-locked to a RAID mode and Linux does not support this. You can boot a Linux live environment, but when you go to install, it will not see the Solid State Drive and it does not appear as a PCI device. The affected models are the Yoga 900 ISK2, 900S, 710S, and 900 ISK for Business, and probably the new Yoga Book and Yoga 910 as well. Lenovo has stated that removing the AHCI option from the BIOS is a feature and that they don't plan to fix this. There have been some blog postings and news articles about this issue lately. Here is the Lenovo Forums topic: https://forums.lenovo.com/t5/Linux-Discussion/Yoga-900-13ISK2-BIOS- update-for-setting-RAID-mode-for-missing/td-p/3339206/highlight/false (Note that this says it is solved, but it is not. Lenovo replied that they won't fix it and that Linux is not supported on these laptops.) Matthew Garrett's blog post is here: https://mjg59.dreamwidth.org/44694.html I approached him with the idea that perhaps the Linux kernel could be modified to reset the hardware and put it into AHCI mode after GRUB loads the kernel (according to him, GRUB doesn't need to be modified because it uses the uEFI firmware's disk access), and then Linux could proceed to boot. Here's what he said: "If you wanted to try that, the best place to do it would be the UEFI setup code in the kernel under arch/x86/boot/compressed/eboot.c - that way you can do it independent of bootloader. Grub's able to read files anyway since it's using the firmware calls to do that. The power management thing isn't about the SSD itself, it's about ensuring that the controller is programmed correctly so that the entire CPU package can enter deep sleep states. Modern systems should idle at around 4W at most, so small amounts make abig difference here." [...] "If the firmware hasn't locked the control bit and if the hardware is ok with suddenly being reconfigured, sure, that ought to work. Doing it in eboot.c means you're doing it before any PCI enumeration has occurred, which makes it more likely that things will work out well." [...] "I'll take a quick look at the 10-series chipset docs to see if it's documented, and if so I'll throw a quick patch together - but I'm probably not going to try pushing it upstream, I'm afraid. If it does work, I'm fine with anybody else doing so." I heaven't heard anything back lately, so I am putting this in a bug report so that the Ubuntu maintainers are aware of the issue. It seems like a few lines of kernel code are all that is really required to fix this and restore the ability of Linux distributions to be installed on half a dozen laptops (probably more to come, since Lenovo says that the industry is moving to this!). --- ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ryan 1604 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 17.04 EcryptfsInUse: Yes InstallationDate: Installed on 2017-05-30 (2 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 5986:068c Acer, Inc Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80UE Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-22-generic.efi.signed root=UUID=3ee79c46-724b-41b5-8c42-44458297de6a ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 RelatedPackageVersions: linux-restricted-modules-4.10.0-22-generic N/A linux-backports-modules-4.10.0-22-generic N/A linux-firmware 1.164.1 Tags: zesty Uname: Linux 4.10.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios
[Kernel-packages] [Bug 1627905] JournalErrors.txt
apport information ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1627905/+attachment/4887119/+files/JournalErrors.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/1627905 Title: Ubuntu can't be installed to certain Lenovo Yoga laptops because the fakeraid storage mode is not supported. Status in linux package in Ubuntu: Triaged Bug description: Several Lenovo Yoga laptops do not allow the user to install any current Linux distributions due to being BIOS-locked to a RAID mode and Linux does not support this. You can boot a Linux live environment, but when you go to install, it will not see the Solid State Drive and it does not appear as a PCI device. The affected models are the Yoga 900 ISK2, 900S, 710S, and 900 ISK for Business, and probably the new Yoga Book and Yoga 910 as well. Lenovo has stated that removing the AHCI option from the BIOS is a feature and that they don't plan to fix this. There have been some blog postings and news articles about this issue lately. Here is the Lenovo Forums topic: https://forums.lenovo.com/t5/Linux-Discussion/Yoga-900-13ISK2-BIOS- update-for-setting-RAID-mode-for-missing/td-p/3339206/highlight/false (Note that this says it is solved, but it is not. Lenovo replied that they won't fix it and that Linux is not supported on these laptops.) Matthew Garrett's blog post is here: https://mjg59.dreamwidth.org/44694.html I approached him with the idea that perhaps the Linux kernel could be modified to reset the hardware and put it into AHCI mode after GRUB loads the kernel (according to him, GRUB doesn't need to be modified because it uses the uEFI firmware's disk access), and then Linux could proceed to boot. Here's what he said: "If you wanted to try that, the best place to do it would be the UEFI setup code in the kernel under arch/x86/boot/compressed/eboot.c - that way you can do it independent of bootloader. Grub's able to read files anyway since it's using the firmware calls to do that. The power management thing isn't about the SSD itself, it's about ensuring that the controller is programmed correctly so that the entire CPU package can enter deep sleep states. Modern systems should idle at around 4W at most, so small amounts make abig difference here." [...] "If the firmware hasn't locked the control bit and if the hardware is ok with suddenly being reconfigured, sure, that ought to work. Doing it in eboot.c means you're doing it before any PCI enumeration has occurred, which makes it more likely that things will work out well." [...] "I'll take a quick look at the 10-series chipset docs to see if it's documented, and if so I'll throw a quick patch together - but I'm probably not going to try pushing it upstream, I'm afraid. If it does work, I'm fine with anybody else doing so." I heaven't heard anything back lately, so I am putting this in a bug report so that the Ubuntu maintainers are aware of the issue. It seems like a few lines of kernel code are all that is really required to fix this and restore the ability of Linux distributions to be installed on half a dozen laptops (probably more to come, since Lenovo says that the industry is moving to this!). --- ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ryan 1604 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 17.04 EcryptfsInUse: Yes InstallationDate: Installed on 2017-05-30 (2 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 5986:068c Acer, Inc Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80UE Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-22-generic.efi.signed root=UUID=3ee79c46-724b-41b5-8c42-44458297de6a ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 RelatedPackageVersions: linux-restricted-modules-4.10.0-22-generic N/A linux-backports-modules-4.10.0-22-generic N/A linux-firmware 1.164.1 Tags: zesty Uname: Linux 4.10.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUplo
[Kernel-packages] [Bug 1627905] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1627905/+attachment/4887122/+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/1627905 Title: Ubuntu can't be installed to certain Lenovo Yoga laptops because the fakeraid storage mode is not supported. Status in linux package in Ubuntu: Triaged Bug description: Several Lenovo Yoga laptops do not allow the user to install any current Linux distributions due to being BIOS-locked to a RAID mode and Linux does not support this. You can boot a Linux live environment, but when you go to install, it will not see the Solid State Drive and it does not appear as a PCI device. The affected models are the Yoga 900 ISK2, 900S, 710S, and 900 ISK for Business, and probably the new Yoga Book and Yoga 910 as well. Lenovo has stated that removing the AHCI option from the BIOS is a feature and that they don't plan to fix this. There have been some blog postings and news articles about this issue lately. Here is the Lenovo Forums topic: https://forums.lenovo.com/t5/Linux-Discussion/Yoga-900-13ISK2-BIOS- update-for-setting-RAID-mode-for-missing/td-p/3339206/highlight/false (Note that this says it is solved, but it is not. Lenovo replied that they won't fix it and that Linux is not supported on these laptops.) Matthew Garrett's blog post is here: https://mjg59.dreamwidth.org/44694.html I approached him with the idea that perhaps the Linux kernel could be modified to reset the hardware and put it into AHCI mode after GRUB loads the kernel (according to him, GRUB doesn't need to be modified because it uses the uEFI firmware's disk access), and then Linux could proceed to boot. Here's what he said: "If you wanted to try that, the best place to do it would be the UEFI setup code in the kernel under arch/x86/boot/compressed/eboot.c - that way you can do it independent of bootloader. Grub's able to read files anyway since it's using the firmware calls to do that. The power management thing isn't about the SSD itself, it's about ensuring that the controller is programmed correctly so that the entire CPU package can enter deep sleep states. Modern systems should idle at around 4W at most, so small amounts make abig difference here." [...] "If the firmware hasn't locked the control bit and if the hardware is ok with suddenly being reconfigured, sure, that ought to work. Doing it in eboot.c means you're doing it before any PCI enumeration has occurred, which makes it more likely that things will work out well." [...] "I'll take a quick look at the 10-series chipset docs to see if it's documented, and if so I'll throw a quick patch together - but I'm probably not going to try pushing it upstream, I'm afraid. If it does work, I'm fine with anybody else doing so." I heaven't heard anything back lately, so I am putting this in a bug report so that the Ubuntu maintainers are aware of the issue. It seems like a few lines of kernel code are all that is really required to fix this and restore the ability of Linux distributions to be installed on half a dozen laptops (probably more to come, since Lenovo says that the industry is moving to this!). --- ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ryan 1604 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 17.04 EcryptfsInUse: Yes InstallationDate: Installed on 2017-05-30 (2 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 5986:068c Acer, Inc Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80UE Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-22-generic.efi.signed root=UUID=3ee79c46-724b-41b5-8c42-44458297de6a ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 RelatedPackageVersions: linux-restricted-modules-4.10.0-22-generic N/A linux-backports-modules-4.10.0-22-generic N/A linux-firmware 1.164.1 Tags: zesty Uname: Linux 4.10.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUplo
[Kernel-packages] [Bug 1627905] Re: Ubuntu can't be installed to certain Lenovo Yoga laptops because the fakeraid storage mode is not supported.
NOTE: The apport information posted above is with the nvme ssd in this laptop visible and operating in AHCI mode (not RAID) under the fixed BIOS that Lenovo provided. As noted by Intel, there's no way (without their patch) for computers without the new BIOS to install Linux. Linux can't see the device or interact with it at all in the "RAID" mode. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1627905 Title: Ubuntu can't be installed to certain Lenovo Yoga laptops because the fakeraid storage mode is not supported. Status in linux package in Ubuntu: Triaged Bug description: Several Lenovo Yoga laptops do not allow the user to install any current Linux distributions due to being BIOS-locked to a RAID mode and Linux does not support this. You can boot a Linux live environment, but when you go to install, it will not see the Solid State Drive and it does not appear as a PCI device. The affected models are the Yoga 900 ISK2, 900S, 710S, and 900 ISK for Business, and probably the new Yoga Book and Yoga 910 as well. Lenovo has stated that removing the AHCI option from the BIOS is a feature and that they don't plan to fix this. There have been some blog postings and news articles about this issue lately. Here is the Lenovo Forums topic: https://forums.lenovo.com/t5/Linux-Discussion/Yoga-900-13ISK2-BIOS- update-for-setting-RAID-mode-for-missing/td-p/3339206/highlight/false (Note that this says it is solved, but it is not. Lenovo replied that they won't fix it and that Linux is not supported on these laptops.) Matthew Garrett's blog post is here: https://mjg59.dreamwidth.org/44694.html I approached him with the idea that perhaps the Linux kernel could be modified to reset the hardware and put it into AHCI mode after GRUB loads the kernel (according to him, GRUB doesn't need to be modified because it uses the uEFI firmware's disk access), and then Linux could proceed to boot. Here's what he said: "If you wanted to try that, the best place to do it would be the UEFI setup code in the kernel under arch/x86/boot/compressed/eboot.c - that way you can do it independent of bootloader. Grub's able to read files anyway since it's using the firmware calls to do that. The power management thing isn't about the SSD itself, it's about ensuring that the controller is programmed correctly so that the entire CPU package can enter deep sleep states. Modern systems should idle at around 4W at most, so small amounts make abig difference here." [...] "If the firmware hasn't locked the control bit and if the hardware is ok with suddenly being reconfigured, sure, that ought to work. Doing it in eboot.c means you're doing it before any PCI enumeration has occurred, which makes it more likely that things will work out well." [...] "I'll take a quick look at the 10-series chipset docs to see if it's documented, and if so I'll throw a quick patch together - but I'm probably not going to try pushing it upstream, I'm afraid. If it does work, I'm fine with anybody else doing so." I heaven't heard anything back lately, so I am putting this in a bug report so that the Ubuntu maintainers are aware of the issue. It seems like a few lines of kernel code are all that is really required to fix this and restore the ability of Linux distributions to be installed on half a dozen laptops (probably more to come, since Lenovo says that the industry is moving to this!). --- ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ryan 1604 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 17.04 EcryptfsInUse: Yes InstallationDate: Installed on 2017-05-30 (2 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 5986:068c Acer, Inc Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80UE Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-22-generic.efi.signed root=UUID=3ee79c46-724b-41b5-8c42-44458297de6a ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 RelatedPackageVersions: linux-restricted-modules-4.10.0-22-generic N/A linux-backports-modules-4.10.0-22-generic N/A linux-firmware 1.1
[Kernel-packages] [Bug 1553811] [NEW] Thinkpad T460: Trackpoint mouse buttons instantly generate "release" event on press
Public bug reported: When using the trackpoint mouse buttons on the laptop, when any of the buttons are pressed a release event immediately follows, even if the mouse button is being held down. This prevents moving of windows, typical drag & drop operations, selection etc with the mouse. Example output from xev for button 1: ButtonPress event, serial 40, synthetic NO, window 0x7e1, root 0xb6, subw 0x0, time 1097221, (116,59), root:(116,142), state 0x0, button 1, same_screen YES ButtonRelease event, serial 40, synthetic NO, window 0x7e1, root 0xb6, subw 0x0, time 1097229, (116,59), root:(116,142), state 0x100, button 1, same_screen YES Button 2: ButtonPress event, serial 40, synthetic NO, window 0x7e1, root 0xb6, subw 0x0, time 1100941, (116,59), root:(116,142), state 0x0, button 2, same_screen YES ButtonRelease event, serial 40, synthetic NO, window 0x7e1, root 0xb6, subw 0x0, time 1100941, (116,59), root:(116,142), state 0x200, button 2, same_screen YES Button 3: ButtonPress event, serial 40, synthetic NO, window 0x7e1, root 0xb6, subw 0x0, time 1098467, (116,59), root:(116,142), state 0x0, button 3, same_screen YES ButtonRelease event, serial 40, synthetic NO, window 0x7e1, root 0xb6, subw 0x0, time 1098477, (116,59), root:(116,142), state 0x400, button 3, same_screen YES Possibly relevant output from journal: kernel: thinkpad_acpi: ThinkPad ACPI Extras v0.25 kernel: thinkpad_acpi: http://ibm-acpi.sf.net/ kernel: thinkpad_acpi: ThinkPad BIOS R06ET33W (1.07 ), EC unknown kernel: thinkpad_acpi: Lenovo ThinkPad T460, model 20FNCTO1WW kernel: thinkpad_acpi: detected a 8-level brightness capable ThinkPad kernel: thinkpad_acpi: unknown version of the HKEY interface: 0x200 kernel: thinkpad_acpi: please report this to ibm-acpi-de...@lists.sourceforge.net kernel: thinkpad_acpi: radio switch found; radios are enabled kernel: thinkpad_acpi: This ThinkPad has standard ACPI backlight brightness control, supported by the ACPI video driver kernel: thinkpad_acpi: Disabling thinkpad-acpi brightness events by default... kernel: thinkpad_acpi: rfkill switch tpacpi_bluetooth_sw: radio is unblocked kernel: thinkpad_acpi: Standard ACPI backlight interface available, not loading native one kernel: input: ThinkPad Extra Buttons as /devices/platform/thinkpad_acpi/input/input7 sensors[1000]: thinkpad-isa- kernel: thinkpad_acpi: EC reports that Thermal Table has changed kernel: thinkpad_acpi: acpi_evalf(GTRW, dd, ...) failed: AE_NOT_FOUND kernel: thinkpad_acpi: Cannot read adaptive keyboard mode. kernel: thinkpad_acpi: acpi_evalf(STRW, vd, ...) failed: AE_NOT_FOUND kernel: thinkpad_acpi: Cannot set adaptive keyboard mode. kernel: thinkpad_acpi: EC reports that Thermal Table has changed ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-10-generic 4.4.0-10.25 ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3 Uname: Linux 4.4.0-10-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: KDE Date: Sun Mar 6 12:38:59 2016 HibernationDevice: RESUME=UUID=04e04e17-3976-4daa-a1dd-2dd369aee83d InstallationDate: Installed on 2015-09-21 (166 days ago) InstallationMedia: It Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20FNCTO1WW ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-10-generic root=/dev/mapper/it--vg-root ro quiet intel_pstate=no_hwp RelatedPackageVersions: linux-restricted-modules-4.4.0-10-generic N/A linux-backports-modules-4.4.0-10-generic N/A linux-firmware1.156 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-02-24 (10 days ago) dmi.bios.date: 01/05/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R06ET33W (1.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FNCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR06ET33W(1.07):bd01/05/2016:svnLENOVO:pn20FNCTO1WW:pvrThinkPadT460:rvnLENOVO:rn20FNCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20FNCTO1WW dmi.product.version: ThinkPad T460 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1553811 Title: Thinkpad T460: Trackpoint mouse buttons instantly generate "release" event on press Status in linux package in Ubuntu: Confirmed Bug description: When using the trackpoint mouse buttons on the laptop, when any of the buttons are pressed a release event immediately follows, even if the mouse button is being held down. This prevents m
[Kernel-packages] [Bug 1553811] Re: Thinkpad T460: Trackpoint mouse buttons instantly generate "release" event on press
I attempted the work-around in #3, but it doesn't change the behavior on my system. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1553811 Title: Thinkpad T460: Trackpoint mouse buttons instantly generate "release" event on press Status in linux package in Ubuntu: Confirmed Bug description: When using the trackpoint mouse buttons on the laptop, when any of the buttons are pressed a release event immediately follows, even if the mouse button is being held down. This prevents moving of windows, typical drag & drop operations, selection etc with the mouse. Example output from xev for button 1: ButtonPress event, serial 40, synthetic NO, window 0x7e1, root 0xb6, subw 0x0, time 1097221, (116,59), root:(116,142), state 0x0, button 1, same_screen YES ButtonRelease event, serial 40, synthetic NO, window 0x7e1, root 0xb6, subw 0x0, time 1097229, (116,59), root:(116,142), state 0x100, button 1, same_screen YES Button 2: ButtonPress event, serial 40, synthetic NO, window 0x7e1, root 0xb6, subw 0x0, time 1100941, (116,59), root:(116,142), state 0x0, button 2, same_screen YES ButtonRelease event, serial 40, synthetic NO, window 0x7e1, root 0xb6, subw 0x0, time 1100941, (116,59), root:(116,142), state 0x200, button 2, same_screen YES Button 3: ButtonPress event, serial 40, synthetic NO, window 0x7e1, root 0xb6, subw 0x0, time 1098467, (116,59), root:(116,142), state 0x0, button 3, same_screen YES ButtonRelease event, serial 40, synthetic NO, window 0x7e1, root 0xb6, subw 0x0, time 1098477, (116,59), root:(116,142), state 0x400, button 3, same_screen YES Possibly relevant output from journal: kernel: thinkpad_acpi: ThinkPad ACPI Extras v0.25 kernel: thinkpad_acpi: http://ibm-acpi.sf.net/ kernel: thinkpad_acpi: ThinkPad BIOS R06ET33W (1.07 ), EC unknown kernel: thinkpad_acpi: Lenovo ThinkPad T460, model 20FNCTO1WW kernel: thinkpad_acpi: detected a 8-level brightness capable ThinkPad kernel: thinkpad_acpi: unknown version of the HKEY interface: 0x200 kernel: thinkpad_acpi: please report this to ibm-acpi-de...@lists.sourceforge.net kernel: thinkpad_acpi: radio switch found; radios are enabled kernel: thinkpad_acpi: This ThinkPad has standard ACPI backlight brightness control, supported by the ACPI video driver kernel: thinkpad_acpi: Disabling thinkpad-acpi brightness events by default... kernel: thinkpad_acpi: rfkill switch tpacpi_bluetooth_sw: radio is unblocked kernel: thinkpad_acpi: Standard ACPI backlight interface available, not loading native one kernel: input: ThinkPad Extra Buttons as /devices/platform/thinkpad_acpi/input/input7 sensors[1000]: thinkpad-isa- kernel: thinkpad_acpi: EC reports that Thermal Table has changed kernel: thinkpad_acpi: acpi_evalf(GTRW, dd, ...) failed: AE_NOT_FOUND kernel: thinkpad_acpi: Cannot read adaptive keyboard mode. kernel: thinkpad_acpi: acpi_evalf(STRW, vd, ...) failed: AE_NOT_FOUND kernel: thinkpad_acpi: Cannot set adaptive keyboard mode. kernel: thinkpad_acpi: EC reports that Thermal Table has changed ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-10-generic 4.4.0-10.25 ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3 Uname: Linux 4.4.0-10-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: KDE Date: Sun Mar 6 12:38:59 2016 HibernationDevice: RESUME=UUID=04e04e17-3976-4daa-a1dd-2dd369aee83d InstallationDate: Installed on 2015-09-21 (166 days ago) InstallationMedia: It Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20FNCTO1WW ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-10-generic root=/dev/mapper/it--vg-root ro quiet intel_pstate=no_hwp RelatedPackageVersions: linux-restricted-modules-4.4.0-10-generic N/A linux-backports-modules-4.4.0-10-generic N/A linux-firmware1.156 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-02-24 (10 days ago) dmi.bios.date: 01/05/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R06ET33W (1.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FNCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR06ET33W(1.07):bd01/05/2016:svnLENOVO:pn20FNCTO1WW:pvrThinkPadT460:rvnLENOVO:rn20FNCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20FNCTO1WW dmi.product.version: ThinkPad T460 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubu
[Kernel-packages] [Bug 1553811] Re: Thinkpad T460: Trackpoint mouse buttons instantly generate "release" event on press
I attempted to test with 4.5-rc7, but the trackpoint wasn't even listed in xinput. I will try a few other in the 4.5 series. Bug issue still exists in 4.4.4-040404.201603031931 ** Tags added: kernel-bug-exists-upstream-4.4.4 ** Tags removed: kernel-bug-exists-upstream-4.4.4 ** Tags added: kernel-bug-exists-upstream-4.5.0 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1553811 Title: Thinkpad T460: Trackpoint mouse buttons instantly generate "release" event on press Status in linux package in Ubuntu: Incomplete Bug description: When using the trackpoint mouse buttons on the laptop, when any of the buttons are pressed a release event immediately follows, even if the mouse button is being held down. This prevents moving of windows, typical drag & drop operations, selection etc with the mouse. Example output from xev for button 1: ButtonPress event, serial 40, synthetic NO, window 0x7e1, root 0xb6, subw 0x0, time 1097221, (116,59), root:(116,142), state 0x0, button 1, same_screen YES ButtonRelease event, serial 40, synthetic NO, window 0x7e1, root 0xb6, subw 0x0, time 1097229, (116,59), root:(116,142), state 0x100, button 1, same_screen YES Button 2: ButtonPress event, serial 40, synthetic NO, window 0x7e1, root 0xb6, subw 0x0, time 1100941, (116,59), root:(116,142), state 0x0, button 2, same_screen YES ButtonRelease event, serial 40, synthetic NO, window 0x7e1, root 0xb6, subw 0x0, time 1100941, (116,59), root:(116,142), state 0x200, button 2, same_screen YES Button 3: ButtonPress event, serial 40, synthetic NO, window 0x7e1, root 0xb6, subw 0x0, time 1098467, (116,59), root:(116,142), state 0x0, button 3, same_screen YES ButtonRelease event, serial 40, synthetic NO, window 0x7e1, root 0xb6, subw 0x0, time 1098477, (116,59), root:(116,142), state 0x400, button 3, same_screen YES Possibly relevant output from journal: kernel: thinkpad_acpi: ThinkPad ACPI Extras v0.25 kernel: thinkpad_acpi: http://ibm-acpi.sf.net/ kernel: thinkpad_acpi: ThinkPad BIOS R06ET33W (1.07 ), EC unknown kernel: thinkpad_acpi: Lenovo ThinkPad T460, model 20FNCTO1WW kernel: thinkpad_acpi: detected a 8-level brightness capable ThinkPad kernel: thinkpad_acpi: unknown version of the HKEY interface: 0x200 kernel: thinkpad_acpi: please report this to ibm-acpi-de...@lists.sourceforge.net kernel: thinkpad_acpi: radio switch found; radios are enabled kernel: thinkpad_acpi: This ThinkPad has standard ACPI backlight brightness control, supported by the ACPI video driver kernel: thinkpad_acpi: Disabling thinkpad-acpi brightness events by default... kernel: thinkpad_acpi: rfkill switch tpacpi_bluetooth_sw: radio is unblocked kernel: thinkpad_acpi: Standard ACPI backlight interface available, not loading native one kernel: input: ThinkPad Extra Buttons as /devices/platform/thinkpad_acpi/input/input7 sensors[1000]: thinkpad-isa- kernel: thinkpad_acpi: EC reports that Thermal Table has changed kernel: thinkpad_acpi: acpi_evalf(GTRW, dd, ...) failed: AE_NOT_FOUND kernel: thinkpad_acpi: Cannot read adaptive keyboard mode. kernel: thinkpad_acpi: acpi_evalf(STRW, vd, ...) failed: AE_NOT_FOUND kernel: thinkpad_acpi: Cannot set adaptive keyboard mode. kernel: thinkpad_acpi: EC reports that Thermal Table has changed ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-10-generic 4.4.0-10.25 ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3 Uname: Linux 4.4.0-10-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: KDE Date: Sun Mar 6 12:38:59 2016 HibernationDevice: RESUME=UUID=04e04e17-3976-4daa-a1dd-2dd369aee83d InstallationDate: Installed on 2015-09-21 (166 days ago) InstallationMedia: It Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20FNCTO1WW ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-10-generic root=/dev/mapper/it--vg-root ro quiet intel_pstate=no_hwp RelatedPackageVersions: linux-restricted-modules-4.4.0-10-generic N/A linux-backports-modules-4.4.0-10-generic N/A linux-firmware1.156 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-02-24 (10 days ago) dmi.bios.date: 01/05/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R06ET33W (1.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FNCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR06ET33W(1.07):bd01/05/2016:svnLENOVO:pn20FNCTO1WW:pvrThin
[Kernel-packages] [Bug 1553811] Re: Thinkpad T460: Trackpoint mouse buttons instantly generate "release" event on press
Confirmed still present in 4.5-rc5. ** Tags removed: kernel-bug-exists-upstream-4.5.0 ** Tags added: kernel-bug-exists-upstream-4.5-rc5 ** 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/1553811 Title: Thinkpad T460: Trackpoint mouse buttons instantly generate "release" event on press Status in linux package in Ubuntu: Confirmed Bug description: When using the trackpoint mouse buttons on the laptop, when any of the buttons are pressed a release event immediately follows, even if the mouse button is being held down. This prevents moving of windows, typical drag & drop operations, selection etc with the mouse. Example output from xev for button 1: ButtonPress event, serial 40, synthetic NO, window 0x7e1, root 0xb6, subw 0x0, time 1097221, (116,59), root:(116,142), state 0x0, button 1, same_screen YES ButtonRelease event, serial 40, synthetic NO, window 0x7e1, root 0xb6, subw 0x0, time 1097229, (116,59), root:(116,142), state 0x100, button 1, same_screen YES Button 2: ButtonPress event, serial 40, synthetic NO, window 0x7e1, root 0xb6, subw 0x0, time 1100941, (116,59), root:(116,142), state 0x0, button 2, same_screen YES ButtonRelease event, serial 40, synthetic NO, window 0x7e1, root 0xb6, subw 0x0, time 1100941, (116,59), root:(116,142), state 0x200, button 2, same_screen YES Button 3: ButtonPress event, serial 40, synthetic NO, window 0x7e1, root 0xb6, subw 0x0, time 1098467, (116,59), root:(116,142), state 0x0, button 3, same_screen YES ButtonRelease event, serial 40, synthetic NO, window 0x7e1, root 0xb6, subw 0x0, time 1098477, (116,59), root:(116,142), state 0x400, button 3, same_screen YES Possibly relevant output from journal: kernel: thinkpad_acpi: ThinkPad ACPI Extras v0.25 kernel: thinkpad_acpi: http://ibm-acpi.sf.net/ kernel: thinkpad_acpi: ThinkPad BIOS R06ET33W (1.07 ), EC unknown kernel: thinkpad_acpi: Lenovo ThinkPad T460, model 20FNCTO1WW kernel: thinkpad_acpi: detected a 8-level brightness capable ThinkPad kernel: thinkpad_acpi: unknown version of the HKEY interface: 0x200 kernel: thinkpad_acpi: please report this to ibm-acpi-de...@lists.sourceforge.net kernel: thinkpad_acpi: radio switch found; radios are enabled kernel: thinkpad_acpi: This ThinkPad has standard ACPI backlight brightness control, supported by the ACPI video driver kernel: thinkpad_acpi: Disabling thinkpad-acpi brightness events by default... kernel: thinkpad_acpi: rfkill switch tpacpi_bluetooth_sw: radio is unblocked kernel: thinkpad_acpi: Standard ACPI backlight interface available, not loading native one kernel: input: ThinkPad Extra Buttons as /devices/platform/thinkpad_acpi/input/input7 sensors[1000]: thinkpad-isa- kernel: thinkpad_acpi: EC reports that Thermal Table has changed kernel: thinkpad_acpi: acpi_evalf(GTRW, dd, ...) failed: AE_NOT_FOUND kernel: thinkpad_acpi: Cannot read adaptive keyboard mode. kernel: thinkpad_acpi: acpi_evalf(STRW, vd, ...) failed: AE_NOT_FOUND kernel: thinkpad_acpi: Cannot set adaptive keyboard mode. kernel: thinkpad_acpi: EC reports that Thermal Table has changed ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-10-generic 4.4.0-10.25 ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3 Uname: Linux 4.4.0-10-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: KDE Date: Sun Mar 6 12:38:59 2016 HibernationDevice: RESUME=UUID=04e04e17-3976-4daa-a1dd-2dd369aee83d InstallationDate: Installed on 2015-09-21 (166 days ago) InstallationMedia: It Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20FNCTO1WW ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-10-generic root=/dev/mapper/it--vg-root ro quiet intel_pstate=no_hwp RelatedPackageVersions: linux-restricted-modules-4.4.0-10-generic N/A linux-backports-modules-4.4.0-10-generic N/A linux-firmware1.156 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-02-24 (10 days ago) dmi.bios.date: 01/05/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R06ET33W (1.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FNCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR06ET33W(1.07):bd01/05/2016:svnLENOVO:pn20FNCTO1WW:pvrThinkPadT460:rvnLENOVO:rn20FNCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20FNCTO1WW dmi.product.ve
[Kernel-packages] [Bug 1553811] Re: Thinkpad T460: Trackpoint mouse buttons instantly generate "release" event on press
I tested in 15.10, issue persists. output of usb-devices: : Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=480 MxCh=12 D: Ver= 2.00 Cls=09(hub ) Sub=00 Prot=01 MxPS=64 #Cfgs= 1 P: Vendor=1d6b ProdID=0002 Rev=04.04 S: Manufacturer=Linux 4.4.0-11-generic xhci-hcd S: Product=xHCI Host Controller S: SerialNumber=:00:14.0 C: #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=0mA I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub T: Bus=02 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=5000 MxCh= 6 D: Ver= 3.00 Cls=09(hub ) Sub=00 Prot=03 MxPS= 9 #Cfgs= 1 P: Vendor=1d6b ProdID=0003 Rev=04.04 S: Manufacturer=Linux 4.4.0-11-generic xhci-hcd S: Product=xHCI Host Controller S: SerialNumber=:00:14.0 C: #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=0mA I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1553811 Title: Thinkpad T460: Trackpoint mouse buttons instantly generate "release" event on press Status in linux package in Ubuntu: Incomplete Bug description: When using the trackpoint mouse buttons on the laptop, when any of the buttons are pressed a release event immediately follows, even if the mouse button is being held down. This prevents moving of windows, typical drag & drop operations, selection etc with the mouse. Example output from xev for button 1: ButtonPress event, serial 40, synthetic NO, window 0x7e1, root 0xb6, subw 0x0, time 1097221, (116,59), root:(116,142), state 0x0, button 1, same_screen YES ButtonRelease event, serial 40, synthetic NO, window 0x7e1, root 0xb6, subw 0x0, time 1097229, (116,59), root:(116,142), state 0x100, button 1, same_screen YES Button 2: ButtonPress event, serial 40, synthetic NO, window 0x7e1, root 0xb6, subw 0x0, time 1100941, (116,59), root:(116,142), state 0x0, button 2, same_screen YES ButtonRelease event, serial 40, synthetic NO, window 0x7e1, root 0xb6, subw 0x0, time 1100941, (116,59), root:(116,142), state 0x200, button 2, same_screen YES Button 3: ButtonPress event, serial 40, synthetic NO, window 0x7e1, root 0xb6, subw 0x0, time 1098467, (116,59), root:(116,142), state 0x0, button 3, same_screen YES ButtonRelease event, serial 40, synthetic NO, window 0x7e1, root 0xb6, subw 0x0, time 1098477, (116,59), root:(116,142), state 0x400, button 3, same_screen YES Possibly relevant output from journal: kernel: thinkpad_acpi: ThinkPad ACPI Extras v0.25 kernel: thinkpad_acpi: http://ibm-acpi.sf.net/ kernel: thinkpad_acpi: ThinkPad BIOS R06ET33W (1.07 ), EC unknown kernel: thinkpad_acpi: Lenovo ThinkPad T460, model 20FNCTO1WW kernel: thinkpad_acpi: detected a 8-level brightness capable ThinkPad kernel: thinkpad_acpi: unknown version of the HKEY interface: 0x200 kernel: thinkpad_acpi: please report this to ibm-acpi-de...@lists.sourceforge.net kernel: thinkpad_acpi: radio switch found; radios are enabled kernel: thinkpad_acpi: This ThinkPad has standard ACPI backlight brightness control, supported by the ACPI video driver kernel: thinkpad_acpi: Disabling thinkpad-acpi brightness events by default... kernel: thinkpad_acpi: rfkill switch tpacpi_bluetooth_sw: radio is unblocked kernel: thinkpad_acpi: Standard ACPI backlight interface available, not loading native one kernel: input: ThinkPad Extra Buttons as /devices/platform/thinkpad_acpi/input/input7 sensors[1000]: thinkpad-isa- kernel: thinkpad_acpi: EC reports that Thermal Table has changed kernel: thinkpad_acpi: acpi_evalf(GTRW, dd, ...) failed: AE_NOT_FOUND kernel: thinkpad_acpi: Cannot read adaptive keyboard mode. kernel: thinkpad_acpi: acpi_evalf(STRW, vd, ...) failed: AE_NOT_FOUND kernel: thinkpad_acpi: Cannot set adaptive keyboard mode. kernel: thinkpad_acpi: EC reports that Thermal Table has changed ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-10-generic 4.4.0-10.25 ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3 Uname: Linux 4.4.0-10-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: KDE Date: Sun Mar 6 12:38:59 2016 HibernationDevice: RESUME=UUID=04e04e17-3976-4daa-a1dd-2dd369aee83d InstallationDate: Installed on 2015-09-21 (166 days ago) InstallationMedia: It Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20FNCTO1WW ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-10-generic root=/dev/mapper/it--vg-root ro quiet intel_pstate=no_hwp RelatedPackageVersions: linux-restricted-modules-4.4.0-10-generic N/A linux-backports-modules-4.4.0-10-generic N/A linux-firmware1.156 SourcePackage: linux Upgra
[Kernel-packages] [Bug 1553811] Re: Thinkpad T460: Trackpoint mouse buttons instantly generate "release" event on press
Yes that was all of the output -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1553811 Title: Thinkpad T460: Trackpoint mouse buttons instantly generate "release" event on press Status in linux package in Ubuntu: Triaged Bug description: When using the trackpoint mouse buttons on the laptop, when any of the buttons are pressed a release event immediately follows, even if the mouse button is being held down. This prevents moving of windows, typical drag & drop operations, selection etc with the mouse. Example output from xev for button 1: ButtonPress event, serial 40, synthetic NO, window 0x7e1, root 0xb6, subw 0x0, time 1097221, (116,59), root:(116,142), state 0x0, button 1, same_screen YES ButtonRelease event, serial 40, synthetic NO, window 0x7e1, root 0xb6, subw 0x0, time 1097229, (116,59), root:(116,142), state 0x100, button 1, same_screen YES Button 2: ButtonPress event, serial 40, synthetic NO, window 0x7e1, root 0xb6, subw 0x0, time 1100941, (116,59), root:(116,142), state 0x0, button 2, same_screen YES ButtonRelease event, serial 40, synthetic NO, window 0x7e1, root 0xb6, subw 0x0, time 1100941, (116,59), root:(116,142), state 0x200, button 2, same_screen YES Button 3: ButtonPress event, serial 40, synthetic NO, window 0x7e1, root 0xb6, subw 0x0, time 1098467, (116,59), root:(116,142), state 0x0, button 3, same_screen YES ButtonRelease event, serial 40, synthetic NO, window 0x7e1, root 0xb6, subw 0x0, time 1098477, (116,59), root:(116,142), state 0x400, button 3, same_screen YES Possibly relevant output from journal: kernel: thinkpad_acpi: ThinkPad ACPI Extras v0.25 kernel: thinkpad_acpi: http://ibm-acpi.sf.net/ kernel: thinkpad_acpi: ThinkPad BIOS R06ET33W (1.07 ), EC unknown kernel: thinkpad_acpi: Lenovo ThinkPad T460, model 20FNCTO1WW kernel: thinkpad_acpi: detected a 8-level brightness capable ThinkPad kernel: thinkpad_acpi: unknown version of the HKEY interface: 0x200 kernel: thinkpad_acpi: please report this to ibm-acpi-de...@lists.sourceforge.net kernel: thinkpad_acpi: radio switch found; radios are enabled kernel: thinkpad_acpi: This ThinkPad has standard ACPI backlight brightness control, supported by the ACPI video driver kernel: thinkpad_acpi: Disabling thinkpad-acpi brightness events by default... kernel: thinkpad_acpi: rfkill switch tpacpi_bluetooth_sw: radio is unblocked kernel: thinkpad_acpi: Standard ACPI backlight interface available, not loading native one kernel: input: ThinkPad Extra Buttons as /devices/platform/thinkpad_acpi/input/input7 sensors[1000]: thinkpad-isa- kernel: thinkpad_acpi: EC reports that Thermal Table has changed kernel: thinkpad_acpi: acpi_evalf(GTRW, dd, ...) failed: AE_NOT_FOUND kernel: thinkpad_acpi: Cannot read adaptive keyboard mode. kernel: thinkpad_acpi: acpi_evalf(STRW, vd, ...) failed: AE_NOT_FOUND kernel: thinkpad_acpi: Cannot set adaptive keyboard mode. kernel: thinkpad_acpi: EC reports that Thermal Table has changed ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-10-generic 4.4.0-10.25 ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3 Uname: Linux 4.4.0-10-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: KDE Date: Sun Mar 6 12:38:59 2016 HibernationDevice: RESUME=UUID=04e04e17-3976-4daa-a1dd-2dd369aee83d InstallationDate: Installed on 2015-09-21 (166 days ago) InstallationMedia: It Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20FNCTO1WW ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-10-generic root=/dev/mapper/it--vg-root ro quiet intel_pstate=no_hwp RelatedPackageVersions: linux-restricted-modules-4.4.0-10-generic N/A linux-backports-modules-4.4.0-10-generic N/A linux-firmware1.156 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-02-24 (10 days ago) dmi.bios.date: 01/05/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R06ET33W (1.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FNCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR06ET33W(1.07):bd01/05/2016:svnLENOVO:pn20FNCTO1WW:pvrThinkPadT460:rvnLENOVO:rn20FNCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20FNCTO1WW dmi.product.version: ThinkPad T460 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1553811/+subscriptions -- Mail
[Kernel-packages] [Bug 1558252] [NEW] Intel 8260 / iwlwifi Occasionally unusuable after restart
Public bug reported: Hello, Some times my wifi card is inaccessible immediately after boot. Typically, restarting the machine or reloading the iwlwifi kernel module resolves the issue. dmesg on inaccessible card: [ 13.146917] iwlwifi :04:00.0: Unsupported splx structure [ 13.147620] iwlwifi :04:00.0: Direct firmware load for iwlwifi-8000C-19.ucode failed with error -2 [ 13.147754] iwlwifi :04:00.0: Direct firmware load for iwlwifi-8000C-18.ucode failed with error -2 [ 13.147765] iwlwifi :04:00.0: Direct firmware load for iwlwifi-8000C-17.ucode failed with error -2 [ 13.154952] iwlwifi :04:00.0: loaded firmware version 16.242414.0 op_mode iwlmvm [ 13.191912] iwlwifi :04:00.0: Detected Intel(R) Dual Band Wireless AC 8260, REV=0x208 [ 13.198415] iwlwifi :04:00.0: L1 Enabled - LTR Enabled [ 13.199446] iwlwifi :04:00.0: L1 Enabled - LTR Enabled [ 13.200661] iwlwifi :04:00.0: can't access the RSA semaphore it is write protected [ 14.218185] iwlwifi :04:00.0: SecBoot CPU1 Status: 0x3090003, CPU2 Status: 0x0 [ 14.218190] iwlwifi :04:00.0: Failed to start INIT ucode: -110 [ 14.219090] iwlwifi :04:00.0: Failed to run INIT ucode: -110 [ 14.219157] iwlwifi :04:00.0: L1 Enabled - LTR Enabled ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-13-generic 4.4.0-13.29 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 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ryan 1999 F pulseaudio Date: Wed Mar 16 12:00:48 2016 HibernationDevice: RESUME=UUID=04e04e17-3976-4daa-a1dd-2dd369aee83d InstallationDate: Installed on 2015-09-21 (176 days ago) InstallationMedia: It IwConfig: enp0s31f6 no wireless extensions. lono wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20FNCTO1WW ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-13-generic root=/dev/mapper/it--vg-root ro quiet intel_pstate=no_hwp PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.4.0-13-generic N/A linux-backports-modules-4.4.0-13-generic N/A linux-firmware1.156 RfKill: 0: tpacpi_bluetooth_sw: Bluetooth Soft blocked: yes Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-02-24 (20 days ago) dmi.bios.date: 01/05/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R06ET33W (1.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FNCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR06ET33W(1.07):bd01/05/2016:svnLENOVO:pn20FNCTO1WW:pvrThinkPadT460:rvnLENOVO:rn20FNCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20FNCTO1WW dmi.product.version: ThinkPad T460 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1558252 Title: Intel 8260 / iwlwifi Occasionally unusuable after restart Status in linux package in Ubuntu: New Bug description: Hello, Some times my wifi card is inaccessible immediately after boot. Typically, restarting the machine or reloading the iwlwifi kernel module resolves the issue. dmesg on inaccessible card: [ 13.146917] iwlwifi :04:00.0: Unsupported splx structure [ 13.147620] iwlwifi :04:00.0: Direct firmware load for iwlwifi-8000C-19.ucode failed with error -2 [ 13.147754] iwlwifi :04:00.0: Direct firmware load for iwlwifi-8000C-18.ucode failed with error -2 [ 13.147765] iwlwifi :04:00.0: Direct firmware load for iwlwifi-8000C-17.ucode failed with error -2 [ 13.154952] iwlwifi :04:00.0: loaded firmware version 16.242414.0 op_mode iwlmvm [ 13.191912] iwlwifi :04:00.0: Detected Intel(R) Dual Band Wireless AC 8260, REV=0x208 [ 13.198415] iwlwifi :04:00.0: L1 Enabled - LTR Enabled [ 13.199446] iwlwifi :04:00.0: L1 Enabled - LTR Enabled [ 13.200661] iwlwifi :04:00.0: can't access the RSA semaphore it is write protected [ 14.218185] iwlwifi :04:00.0: SecBoot CPU1 Status: 0x3090003, CPU2 Status: 0x0 [ 14.218190] iwlwifi :04:00.0: Failed to start INIT ucode: -110 [ 14.219090] iwlwifi :04:00.0: Failed to run INIT ucode: -110
[Kernel-packages] [Bug 1553811] Re: Thinkpad T460: Trackpoint mouse buttons instantly generate "release" event on press
I tested the kernel in #15, seems to resolve the issue for me. Mouse press/release events act as expected. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1553811 Title: Thinkpad T460: Trackpoint mouse buttons instantly generate "release" event on press Status in linux package in Ubuntu: In Progress Bug description: When using the trackpoint mouse buttons on the laptop, when any of the buttons are pressed a release event immediately follows, even if the mouse button is being held down. This prevents moving of windows, typical drag & drop operations, selection etc with the mouse. Example output from xev for button 1: ButtonPress event, serial 40, synthetic NO, window 0x7e1, root 0xb6, subw 0x0, time 1097221, (116,59), root:(116,142), state 0x0, button 1, same_screen YES ButtonRelease event, serial 40, synthetic NO, window 0x7e1, root 0xb6, subw 0x0, time 1097229, (116,59), root:(116,142), state 0x100, button 1, same_screen YES Button 2: ButtonPress event, serial 40, synthetic NO, window 0x7e1, root 0xb6, subw 0x0, time 1100941, (116,59), root:(116,142), state 0x0, button 2, same_screen YES ButtonRelease event, serial 40, synthetic NO, window 0x7e1, root 0xb6, subw 0x0, time 1100941, (116,59), root:(116,142), state 0x200, button 2, same_screen YES Button 3: ButtonPress event, serial 40, synthetic NO, window 0x7e1, root 0xb6, subw 0x0, time 1098467, (116,59), root:(116,142), state 0x0, button 3, same_screen YES ButtonRelease event, serial 40, synthetic NO, window 0x7e1, root 0xb6, subw 0x0, time 1098477, (116,59), root:(116,142), state 0x400, button 3, same_screen YES Possibly relevant output from journal: kernel: thinkpad_acpi: ThinkPad ACPI Extras v0.25 kernel: thinkpad_acpi: http://ibm-acpi.sf.net/ kernel: thinkpad_acpi: ThinkPad BIOS R06ET33W (1.07 ), EC unknown kernel: thinkpad_acpi: Lenovo ThinkPad T460, model 20FNCTO1WW kernel: thinkpad_acpi: detected a 8-level brightness capable ThinkPad kernel: thinkpad_acpi: unknown version of the HKEY interface: 0x200 kernel: thinkpad_acpi: please report this to ibm-acpi-de...@lists.sourceforge.net kernel: thinkpad_acpi: radio switch found; radios are enabled kernel: thinkpad_acpi: This ThinkPad has standard ACPI backlight brightness control, supported by the ACPI video driver kernel: thinkpad_acpi: Disabling thinkpad-acpi brightness events by default... kernel: thinkpad_acpi: rfkill switch tpacpi_bluetooth_sw: radio is unblocked kernel: thinkpad_acpi: Standard ACPI backlight interface available, not loading native one kernel: input: ThinkPad Extra Buttons as /devices/platform/thinkpad_acpi/input/input7 sensors[1000]: thinkpad-isa- kernel: thinkpad_acpi: EC reports that Thermal Table has changed kernel: thinkpad_acpi: acpi_evalf(GTRW, dd, ...) failed: AE_NOT_FOUND kernel: thinkpad_acpi: Cannot read adaptive keyboard mode. kernel: thinkpad_acpi: acpi_evalf(STRW, vd, ...) failed: AE_NOT_FOUND kernel: thinkpad_acpi: Cannot set adaptive keyboard mode. kernel: thinkpad_acpi: EC reports that Thermal Table has changed ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-10-generic 4.4.0-10.25 ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3 Uname: Linux 4.4.0-10-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: KDE Date: Sun Mar 6 12:38:59 2016 HibernationDevice: RESUME=UUID=04e04e17-3976-4daa-a1dd-2dd369aee83d InstallationDate: Installed on 2015-09-21 (166 days ago) InstallationMedia: It Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20FNCTO1WW ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-10-generic root=/dev/mapper/it--vg-root ro quiet intel_pstate=no_hwp RelatedPackageVersions: linux-restricted-modules-4.4.0-10-generic N/A linux-backports-modules-4.4.0-10-generic N/A linux-firmware1.156 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-02-24 (10 days ago) dmi.bios.date: 01/05/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R06ET33W (1.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FNCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR06ET33W(1.07):bd01/05/2016:svnLENOVO:pn20FNCTO1WW:pvrThinkPadT460:rvnLENOVO:rn20FNCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20FNCTO1WW dmi.product.version: ThinkPad T460 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https
[Kernel-packages] [Bug 1558252] Re: Intel 8260 / iwlwifi Occasionally unusuable after restart
I tested 4.5.0-040500-generic, did 20 reboots/shutdown cycles, both powered and on battery. I haven't been able to trigger the issue again. ** Tags added: kernel-fixed-upstream ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1558252 Title: Intel 8260 / iwlwifi Occasionally unusuable after restart Status in linux package in Ubuntu: Confirmed Bug description: Hello, Some times my wifi card is inaccessible immediately after boot. Typically, restarting the machine or reloading the iwlwifi kernel module resolves the issue. dmesg on inaccessible card: [ 13.146917] iwlwifi :04:00.0: Unsupported splx structure [ 13.147620] iwlwifi :04:00.0: Direct firmware load for iwlwifi-8000C-19.ucode failed with error -2 [ 13.147754] iwlwifi :04:00.0: Direct firmware load for iwlwifi-8000C-18.ucode failed with error -2 [ 13.147765] iwlwifi :04:00.0: Direct firmware load for iwlwifi-8000C-17.ucode failed with error -2 [ 13.154952] iwlwifi :04:00.0: loaded firmware version 16.242414.0 op_mode iwlmvm [ 13.191912] iwlwifi :04:00.0: Detected Intel(R) Dual Band Wireless AC 8260, REV=0x208 [ 13.198415] iwlwifi :04:00.0: L1 Enabled - LTR Enabled [ 13.199446] iwlwifi :04:00.0: L1 Enabled - LTR Enabled [ 13.200661] iwlwifi :04:00.0: can't access the RSA semaphore it is write protected [ 14.218185] iwlwifi :04:00.0: SecBoot CPU1 Status: 0x3090003, CPU2 Status: 0x0 [ 14.218190] iwlwifi :04:00.0: Failed to start INIT ucode: -110 [ 14.219090] iwlwifi :04:00.0: Failed to run INIT ucode: -110 [ 14.219157] iwlwifi :04:00.0: L1 Enabled - LTR Enabled ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-13-generic 4.4.0-13.29 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 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ryan 1999 F pulseaudio Date: Wed Mar 16 12:00:48 2016 HibernationDevice: RESUME=UUID=04e04e17-3976-4daa-a1dd-2dd369aee83d InstallationDate: Installed on 2015-09-21 (176 days ago) InstallationMedia: It IwConfig: enp0s31f6 no wireless extensions. lono wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20FNCTO1WW ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-13-generic root=/dev/mapper/it--vg-root ro quiet intel_pstate=no_hwp PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.4.0-13-generic N/A linux-backports-modules-4.4.0-13-generic N/A linux-firmware1.156 RfKill: 0: tpacpi_bluetooth_sw: Bluetooth Soft blocked: yes Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-02-24 (20 days ago) dmi.bios.date: 01/05/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R06ET33W (1.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FNCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR06ET33W(1.07):bd01/05/2016:svnLENOVO:pn20FNCTO1WW:pvrThinkPadT460:rvnLENOVO:rn20FNCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20FNCTO1WW dmi.product.version: ThinkPad T460 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1558252/+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 1558252] Re: Intel 8260 / iwlwifi Occasionally unusuable after restart
I was able to trigger this again today on 4.4.0-16: [ 13.665350] iwlwifi :04:00.0: Unsupported splx structure [ 13.678584] iwlwifi :04:00.0: Direct firmware load for iwlwifi-8000C-19.ucode failed with error -2 [ 13.679439] iwlwifi :04:00.0: Direct firmware load for iwlwifi-8000C-18.ucode failed with error -2 [ 13.681595] iwlwifi :04:00.0: Direct firmware load for iwlwifi-8000C-17.ucode failed with error -2 [ 13.696430] iwlwifi :04:00.0: loaded firmware version 16.242414.0 op_mode iwlmvm [ 13.738654] iwlwifi :04:00.0: Detected Intel(R) Dual Band Wireless AC 8260, REV=0x208 [ 13.739014] iwlwifi :04:00.0: L1 Enabled - LTR Enabled [ 13.739585] iwlwifi :04:00.0: L1 Enabled - LTR Enabled [ 13.741861] iwlwifi :04:00.0: can't access the RSA semaphore it is write protected [ 14.761845] iwlwifi :04:00.0: SecBoot CPU1 Status: 0x3090001, CPU2 Status: 0x0 [ 14.761849] iwlwifi :04:00.0: Failed to start INIT ucode: -110 [ 14.762365] iwlwifi :04:00.0: Failed to run INIT ucode: -110 [ 14.762575] iwlwifi :04:00.0: L1 Enabled - LTR Enabled [ 48.788008] iwlwifi :04:00.0: Direct firmware load for iwlwifi-8000C-19.ucode failed with error -2 [ 48.788016] iwlwifi :04:00.0: Direct firmware load for iwlwifi-8000C-18.ucode failed with error -2 [ 48.788023] iwlwifi :04:00.0: Direct firmware load for iwlwifi-8000C-17.ucode failed with error -2 [ 48.788854] iwlwifi :04:00.0: loaded firmware version 16.242414.0 op_mode iwlmvm [ 48.788916] iwlwifi :04:00.0: Unsupported splx structure [ 48.793638] iwlwifi :04:00.0: Detected Intel(R) Dual Band Wireless AC 8260, REV=0x208 [ 48.793949] iwlwifi :04:00.0: L1 Enabled - LTR Enabled [ 48.794322] iwlwifi :04:00.0: L1 Enabled - LTR Enabled [ 48.795508] iwlwifi :04:00.0: can't access the RSA semaphore it is write protected [ 48.953491] ieee80211 phy1: Selected rate control algorithm 'iwl-mvm-rs' [ 48.955333] iwlwifi :04:00.0 wlp4s0: renamed from wlan0 [ 48.976863] iwlwifi :04:00.0: L1 Enabled - LTR Enabled [ 48.977285] iwlwifi :04:00.0: L1 Enabled - LTR Enabled [ 48.978049] iwlwifi :04:00.0: can't access the RSA semaphore it is write protected [ 49.124083] iwlwifi :04:00.0: L1 Enabled - LTR Enabled [ 49.124547] iwlwifi :04:00.0: L1 Enabled - LTR Enabled [ 49.125305] iwlwifi :04:00.0: can't access the RSA semaphore it is write protected -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1558252 Title: Intel 8260 / iwlwifi Occasionally unusuable after restart Status in linux package in Ubuntu: Confirmed Bug description: Hello, Some times my wifi card is inaccessible immediately after boot. Typically, restarting the machine or reloading the iwlwifi kernel module resolves the issue. dmesg on inaccessible card: [ 13.146917] iwlwifi :04:00.0: Unsupported splx structure [ 13.147620] iwlwifi :04:00.0: Direct firmware load for iwlwifi-8000C-19.ucode failed with error -2 [ 13.147754] iwlwifi :04:00.0: Direct firmware load for iwlwifi-8000C-18.ucode failed with error -2 [ 13.147765] iwlwifi :04:00.0: Direct firmware load for iwlwifi-8000C-17.ucode failed with error -2 [ 13.154952] iwlwifi :04:00.0: loaded firmware version 16.242414.0 op_mode iwlmvm [ 13.191912] iwlwifi :04:00.0: Detected Intel(R) Dual Band Wireless AC 8260, REV=0x208 [ 13.198415] iwlwifi :04:00.0: L1 Enabled - LTR Enabled [ 13.199446] iwlwifi :04:00.0: L1 Enabled - LTR Enabled [ 13.200661] iwlwifi :04:00.0: can't access the RSA semaphore it is write protected [ 14.218185] iwlwifi :04:00.0: SecBoot CPU1 Status: 0x3090003, CPU2 Status: 0x0 [ 14.218190] iwlwifi :04:00.0: Failed to start INIT ucode: -110 [ 14.219090] iwlwifi :04:00.0: Failed to run INIT ucode: -110 [ 14.219157] iwlwifi :04:00.0: L1 Enabled - LTR Enabled ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-13-generic 4.4.0-13.29 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 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ryan 1999 F pulseaudio Date: Wed Mar 16 12:00:48 2016 HibernationDevice: RESUME=UUID=04e04e17-3976-4daa-a1dd-2dd369aee83d InstallationDate: Installed on 2015-09-21 (176 days ago) InstallationMedia: It IwConfig: enp0s31f6 no wireless extensions. lono wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20FNCTO1WW ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.U
[Kernel-packages] [Bug 1568573] [NEW] i915 Skylake - Ultra Dock external displays not detected after suspend/resume cycle
Public bug reported: Hello, System is Thinkpad T460, Skylake graphics, Thinkpad Ultra dock. DVI and HDMI displays connected via dock. 4.4.0-18. After a suspend-resume cycle, when the laptop is docked the dock connected external displays are not initialized/connected. If I disconnect the displays from the dock and connect them directly to the laptop, they are initialized successfully and can be configured via xrandr etc. If the laptop is power cycled, the displays can be used normally until the next suspend-resume cycle. Example from relevant dmesg: [drm:intel_dp_link_training_clock_recovery [i915_bpo]] *ERROR* too many voltage retries, give up [drm:intel_dp_link_training_clock_recovery [i915_bpo]] *ERROR* too many voltage retries, give up [drm:intel_dp_link_training_clock_recovery [i915_bpo]] *ERROR* too many voltage retries, give up [drm:intel_dp_start_link_train [i915_bpo]] *ERROR* failed to train DP, aborting [drm:intel_dp_set_idle_link_train [i915_bpo]] *ERROR* Timed out waiting for DP idle patterns [drm:intel_dp_link_training_clock_recovery [i915_bpo]] *ERROR* too many voltage retries, give up [drm:intel_dp_link_training_clock_recovery [i915_bpo]] *ERROR* too many voltage retries, give up [drm:intel_dp_link_training_clock_recovery [i915_bpo]] *ERROR* too many voltage retries, give up ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-18-generic 4.4.0-18.34 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ryan 1838 F pulseaudio Date: Sun Apr 10 09:39:32 2016 HibernationDevice: RESUME=UUID=04e04e17-3976-4daa-a1dd-2dd369aee83d InstallationDate: Installed on 2015-09-21 (201 days ago) InstallationMedia: It Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20FNCTO1WW ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-18-generic root=/dev/mapper/it--vg-root ro quiet PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.4.0-18-generic N/A linux-backports-modules-4.4.0-18-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-02-24 (45 days ago) dmi.bios.date: 03/09/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R06ET35W (1.09 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FNCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR06ET35W(1.09):bd03/09/2016:svnLENOVO:pn20FNCTO1WW:pvrThinkPadT460:rvnLENOVO:rn20FNCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20FNCTO1WW dmi.product.version: ThinkPad T460 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1568573 Title: i915 Skylake - Ultra Dock external displays not detected after suspend/resume cycle Status in linux package in Ubuntu: New Bug description: Hello, System is Thinkpad T460, Skylake graphics, Thinkpad Ultra dock. DVI and HDMI displays connected via dock. 4.4.0-18. After a suspend-resume cycle, when the laptop is docked the dock connected external displays are not initialized/connected. If I disconnect the displays from the dock and connect them directly to the laptop, they are initialized successfully and can be configured via xrandr etc. If the laptop is power cycled, the displays can be used normally until the next suspend-resume cycle. Example from relevant dmesg: [drm:intel_dp_link_training_clock_recovery [i915_bpo]] *ERROR* too many voltage retries, give up [drm:intel_dp_link_training_clock_recovery [i915_bpo]] *ERROR* too many voltage retries, give up [drm:intel_dp_link_training_clock_recovery [i915_bpo]] *ERROR* too many voltage retries, give up [drm:intel_dp_start_link_train [i915_bpo]] *ERROR* failed to train DP, aborting [drm:intel_dp_set_idle_link_train [i915_bpo]] *ERROR* Timed out waiting for DP idle patterns [drm:intel_dp_link_training_clock_recovery [i915_bpo]] *ERROR* too many voltage retries, give up [drm:intel_dp_link_training_clock_recovery [i915_bpo]] *ERROR* too many voltage retries, give up [drm:intel_dp_link_training_clock_recovery [i915_bpo]] *ERROR* too many voltage retries, give up ProblemType: Bug DistroRelease: Ub
[Kernel-packages] [Bug 1566828] Re: Suspension does not work, freezes the pc
Same problem, also on a Dell 7520. Suspend worked every ubuntu release up through 15.10, now the fan spins and never fully sleeps and can't be woken up. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1566828 Title: Suspension does not work, freezes the pc Status in linux package in Ubuntu: Confirmed Bug description: I have this notebook HP 15 ac 191 nl Intel® Core™ i5-5200U with integrated Intel HD 5500 RAM 8 gb DEdicated GPU AMD Radeon R5 M330 I am running kubuntu 16.04 beta2. When i suspend the pc, gettin down the screen or givin the command in the menù, the screen goes black but the fan keeps running. So you can hear the fan working..and the pc got hot. It is also impossible to wake up the pc, it stays freezed in this condition, i have to force the shutdown with the power button pressing it for 3 sec. The problem is present every time i try to suspend the pc. --- ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ale1315 F pulseaudio /dev/snd/pcmC1D0c: ale1315 F...m pulseaudio /dev/snd/pcmC1D0p: ale1315 F...m pulseaudio /dev/snd/controlC1: ale1315 F pulseaudio DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=0c420aef-5eec-47f9-90cc-94eae92e8388 InstallationDate: Installed on 2016-03-31 (5 days ago) InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160331) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0bda:57d6 Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Notebook Package: linux (not installed) ProcEnviron: LANGUAGE= TERM=xterm PATH=(custom, no user) LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-16-generic.efi.signed root=UUID=623bb030-402f-4ae0-b47b-16c0d54bd861 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.4.0-16-generic N/A linux-backports-modules-4.4.0-16-generic N/A linux-firmware1.157 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: xenial Uname: Linux 4.4.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 01/18/2016 dmi.bios.vendor: Insyde dmi.bios.version: F.1F dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80C2 dmi.board.vendor: HP dmi.board.version: 96.45 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.1F:bd01/18/2016:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn80C2:rvr96.45:cvnHP:ct10:cvrChassisVersion: dmi.product.name: HP Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP --- ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ale1315 F pulseaudio /dev/snd/pcmC1D0c: ale1315 F...m pulseaudio /dev/snd/pcmC1D0p: ale1315 F...m pulseaudio /dev/snd/controlC1: ale1315 F pulseaudio DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=0c420aef-5eec-47f9-90cc-94eae92e8388 InstallationDate: Installed on 2016-03-31 (5 days ago) InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160331) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0bda:57d6 Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Notebook Package: linux (not installed) ProcEnviron: LANGUAGE= TERM=xterm PATH=(custom, no user) LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-16-generic.efi.signed root=UUID=623bb030-402f-4ae0-b47b-16c0d54bd861 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.4.0-16-generic N/A linux-backports-modules-4.4.0-16-generic N/A linux-firmware1.157 RfKill: 0: phy0: Wireless LAN Soft blocked
[Kernel-packages] [Bug 1568573] Re: i915 Skylake - Ultra Dock external displays not detected after suspend/resume cycle
I attempted to test both 4.6-rc4 and 4.6.0.996 from drm-next. 4.6-rc4 was un-bootable, and 4.6 from drm-next also had issues with freezing when enabling dock connected displays. ** Tags added: kernel-bug-exists-upstream ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1568573 Title: i915 Skylake - Ultra Dock external displays not detected after suspend/resume cycle Status in linux package in Ubuntu: Confirmed Bug description: Hello, System is Thinkpad T460, Skylake graphics, Thinkpad Ultra dock. DVI and HDMI displays connected via dock. 4.4.0-18. After a suspend-resume cycle, when the laptop is docked the dock connected external displays are not initialized/connected. If I disconnect the displays from the dock and connect them directly to the laptop, they are initialized successfully and can be configured via xrandr etc. If the laptop is power cycled, the displays can be used normally until the next suspend-resume cycle. Example from relevant dmesg: [drm:intel_dp_link_training_clock_recovery [i915_bpo]] *ERROR* too many voltage retries, give up [drm:intel_dp_link_training_clock_recovery [i915_bpo]] *ERROR* too many voltage retries, give up [drm:intel_dp_link_training_clock_recovery [i915_bpo]] *ERROR* too many voltage retries, give up [drm:intel_dp_start_link_train [i915_bpo]] *ERROR* failed to train DP, aborting [drm:intel_dp_set_idle_link_train [i915_bpo]] *ERROR* Timed out waiting for DP idle patterns [drm:intel_dp_link_training_clock_recovery [i915_bpo]] *ERROR* too many voltage retries, give up [drm:intel_dp_link_training_clock_recovery [i915_bpo]] *ERROR* too many voltage retries, give up [drm:intel_dp_link_training_clock_recovery [i915_bpo]] *ERROR* too many voltage retries, give up ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-18-generic 4.4.0-18.34 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ryan 1838 F pulseaudio Date: Sun Apr 10 09:39:32 2016 HibernationDevice: RESUME=UUID=04e04e17-3976-4daa-a1dd-2dd369aee83d InstallationDate: Installed on 2015-09-21 (201 days ago) InstallationMedia: It Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20FNCTO1WW ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-18-generic root=/dev/mapper/it--vg-root ro quiet PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.4.0-18-generic N/A linux-backports-modules-4.4.0-18-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-02-24 (45 days ago) dmi.bios.date: 03/09/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R06ET35W (1.09 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FNCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR06ET35W(1.09):bd03/09/2016:svnLENOVO:pn20FNCTO1WW:pvrThinkPadT460:rvnLENOVO:rn20FNCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20FNCTO1WW dmi.product.version: ThinkPad T460 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1568573/+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 1566828] Re: Suspension does not work, freezes the pc
Noticing everyone in this bug report has Intel + Radeon graphics, I tried disabling the Radeon. Simply running 'sudo rmmod radeon' after the laptop boots up with the stock 4.4 kernel allows it to properly sleep. Removing the kernel module causes kernel oops, but otherwise everything seems fine after unloading it. I've attached a dmesg showing the kernel module removal with the oops, and the successful sleep/wake that follows it. I've tried it several times and sleep/wake is working every time after removing radeon, and fails every time while radeon is loaded. ** Attachment added: "dmesg after removing radeon module" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1566828/+attachment/4640297/+files/dmesg.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/1566828 Title: Suspension does not work, freezes the pc Status in linux package in Ubuntu: Confirmed Bug description: I have this notebook HP 15 ac 191 nl Intel® Core™ i5-5200U with integrated Intel HD 5500 RAM 8 gb DEdicated GPU AMD Radeon R5 M330 I am running kubuntu 16.04 beta2. When i suspend the pc, gettin down the screen or givin the command in the menù, the screen goes black but the fan keeps running. So you can hear the fan working..and the pc got hot. It is also impossible to wake up the pc, it stays freezed in this condition, i have to force the shutdown with the power button pressing it for 3 sec. The problem is present every time i try to suspend the pc. --- ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ale1315 F pulseaudio /dev/snd/pcmC1D0c: ale1315 F...m pulseaudio /dev/snd/pcmC1D0p: ale1315 F...m pulseaudio /dev/snd/controlC1: ale1315 F pulseaudio DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=0c420aef-5eec-47f9-90cc-94eae92e8388 InstallationDate: Installed on 2016-03-31 (5 days ago) InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160331) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0bda:57d6 Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Notebook Package: linux (not installed) ProcEnviron: LANGUAGE= TERM=xterm PATH=(custom, no user) LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-16-generic.efi.signed root=UUID=623bb030-402f-4ae0-b47b-16c0d54bd861 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.4.0-16-generic N/A linux-backports-modules-4.4.0-16-generic N/A linux-firmware1.157 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: xenial Uname: Linux 4.4.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 01/18/2016 dmi.bios.vendor: Insyde dmi.bios.version: F.1F dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80C2 dmi.board.vendor: HP dmi.board.version: 96.45 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.1F:bd01/18/2016:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn80C2:rvr96.45:cvnHP:ct10:cvrChassisVersion: dmi.product.name: HP Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP --- ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ale1315 F pulseaudio /dev/snd/pcmC1D0c: ale1315 F...m pulseaudio /dev/snd/pcmC1D0p: ale1315 F...m pulseaudio /dev/snd/controlC1: ale1315 F pulseaudio DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=0c420aef-5eec-47f9-90cc-94eae92e8388 InstallationDate: Installed on 2016-03-31 (5 days ago) InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160331) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0bda:57d6 Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Notebook Package: linux (not installed) ProcEnviron: LANGUAGE= TERM=xterm PATH=(custom, no user) LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-
[Kernel-packages] [Bug 1566828] Re: Suspension does not work, freezes the pc
hesediel84, module radeon is in use means that's the graphics card you're using in X. See if you can disable it in your BIOS (I can't on my Dell laptop). If not, blacklist the radeon module so it doesn't load on boot. Add "blacklist radeon" to the bottom of /etc/modprobe.d/blacklist.conf -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1566828 Title: Suspension does not work, freezes the pc Status in linux package in Ubuntu: Confirmed Bug description: I have this notebook HP 15 ac 191 nl Intel® Core™ i5-5200U with integrated Intel HD 5500 RAM 8 gb DEdicated GPU AMD Radeon R5 M330 I am running kubuntu 16.04 beta2. When i suspend the pc, gettin down the screen or givin the command in the menù, the screen goes black but the fan keeps running. So you can hear the fan working..and the pc got hot. It is also impossible to wake up the pc, it stays freezed in this condition, i have to force the shutdown with the power button pressing it for 3 sec. The problem is present every time i try to suspend the pc. --- ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ale1315 F pulseaudio /dev/snd/pcmC1D0c: ale1315 F...m pulseaudio /dev/snd/pcmC1D0p: ale1315 F...m pulseaudio /dev/snd/controlC1: ale1315 F pulseaudio DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=0c420aef-5eec-47f9-90cc-94eae92e8388 InstallationDate: Installed on 2016-03-31 (5 days ago) InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160331) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0bda:57d6 Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Notebook Package: linux (not installed) ProcEnviron: LANGUAGE= TERM=xterm PATH=(custom, no user) LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-16-generic.efi.signed root=UUID=623bb030-402f-4ae0-b47b-16c0d54bd861 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.4.0-16-generic N/A linux-backports-modules-4.4.0-16-generic N/A linux-firmware1.157 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: xenial Uname: Linux 4.4.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 01/18/2016 dmi.bios.vendor: Insyde dmi.bios.version: F.1F dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80C2 dmi.board.vendor: HP dmi.board.version: 96.45 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.1F:bd01/18/2016:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn80C2:rvr96.45:cvnHP:ct10:cvrChassisVersion: dmi.product.name: HP Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP --- ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ale1315 F pulseaudio /dev/snd/pcmC1D0c: ale1315 F...m pulseaudio /dev/snd/pcmC1D0p: ale1315 F...m pulseaudio /dev/snd/controlC1: ale1315 F pulseaudio DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=0c420aef-5eec-47f9-90cc-94eae92e8388 InstallationDate: Installed on 2016-03-31 (5 days ago) InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160331) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0bda:57d6 Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Notebook Package: linux (not installed) ProcEnviron: LANGUAGE= TERM=xterm PATH=(custom, no user) LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-16-generic.efi.signed root=UUID=623bb030-402f-4ae0-b47b-16c0d54bd861 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.4.0-16-generic N/A linux-backport
[Kernel-packages] [Bug 1520978] Re: [MacBook1, 1] Suspend fails with error code 38
*** This bug is a duplicate of bug 1068839 *** https://bugs.launchpad.net/bugs/1068839 ** This bug has been marked a duplicate of bug 1068839 Module tpm_infineon prevents kernel suspend -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1520978 Title: [MacBook1,1] Suspend fails with error code 38 Status in linux package in Ubuntu: Expired Bug description: nov 29 20:11:27 stinky kernel: sd 2:0:1:0: [sda] Stopping disk nov 29 20:11:27 stinky kernel: tpm_inf_pnp 00:01: Error (38) sending savestate before suspend nov 29 20:11:27 stinky kernel: __pnp_bus_suspend(): tpm_pm_suspend+0x0/0x1e0 returns 38 nov 29 20:11:27 stinky kernel: dpm_run_callback(): pnp_bus_suspend+0x0/0x20 returns 38 nov 29 20:11:27 stinky kernel: PM: Device 00:01 failed to suspend: error 38 nov 29 20:11:27 stinky kernel: PM: Some devices failed to suspend, or early wake event detected nov 29 20:11:27 stinky kernel: rtc_cmos 00:04: System wakeup disabled by ACPI nov 29 20:11:27 stinky kernel: sd 2:0:1:0: [sda] Starting disk nov 29 20:11:27 stinky kernel: PM: resume of devices complete after 89.724 msecs Attaching the dmesg log surrounding the 'sudo pm-suspend' action as suspend.log, full dmesg in a separate file. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-18-generic 4.2.0-18.22 ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3 Uname: Linux 4.2.0-18-generic i686 ApportVersion: 2.19.1-0ubuntu5 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fredrik1569 F pulseaudio CurrentDesktop: GNOME Date: Sun Nov 29 20:14:31 2015 HibernationDevice: RESUME=UUID=92e841bc-e3de-4914-93cc-908fa8d2a504 MachineType: Apple Computer, Inc. MacBook1,1 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-18-generic root=UUID=850c48ad-e474-4613-8bb4-1f2fec700555 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.2.0-18-generic N/A linux-backports-modules-4.2.0-18-generic N/A linux-firmware1.149.2 SourcePackage: linux UdevLog: Error: [Errno 2] Filen eller katalogen finns inte: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/12/06 dmi.bios.vendor: Apple Computer, Inc. dmi.bios.version: MB11.88Z.0061.B03.0610121324 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Mac-F4208CC8 dmi.board.vendor: Apple Computer, Inc. dmi.board.version: PVT dmi.chassis.asset.tag: Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Apple Computer, Inc. dmi.chassis.version: Mac-F4208CC8 dmi.modalias: dmi:bvnAppleComputer,Inc.:bvrMB11.88Z.0061.B03.0610121324:bd10/12/06:svnAppleComputer,Inc.:pnMacBook1,1:pvr1.0:rvnAppleComputer,Inc.:rnMac-F4208CC8:rvrPVT:cvnAppleComputer,Inc.:ct10:cvrMac-F4208CC8: dmi.product.name: MacBook1,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Computer, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1520978/+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 1068839] Re: Module tpm_infineon prevents kernel suspend
Hey anville, I think you are onto something. Using modprobe to remove tpm_infineon worked for me as well... sort of. At least in the sense that I was finally able to put my laptop to sleep (I too am on a 32bit intel mac... a MacbookPro 1,1). Problem is I can't wake it up once its asleep and have to hard reset. Need to do some more learning to figure out how to find and read whats breaking now. Any tips? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1068839 Title: Module tpm_infineon prevents kernel suspend Status in linux package in Ubuntu: Confirmed Bug description: version_signature: Ubuntu 3.5.0-17.28-generic 3.5.5 WORKAROUND: Immediately prior to suspending: modprobe -r tpm_infineon part of kernel log when it's not working: Oct 19 15:46:37 loki kernel: [ 2145.963934] PM: Syncing filesystems ... done. Oct 19 15:46:37 loki kernel: [ 2146.491439] PM: Preparing system for mem sleep Oct 19 15:46:42 loki kernel: [ 2146.500216] Freezing user space processes ... (elapsed 0.01 seconds) done. Oct 19 15:46:42 loki kernel: [ 2146.516247] Freezing remaining freezable tasks ... (elapsed 0.01 seconds) done. Oct 19 15:46:42 loki kernel: [ 2146.532168] PM: Entering mem sleep Oct 19 15:46:42 loki kernel: [ 2146.532438] Suspending console(s) (use no_console_suspend to debug) Oct 19 15:46:42 loki kernel: [ 2146.576414] sd 2:0:1:0: >[sda] Synchronizing SCSI cache Oct 19 15:46:42 loki kernel: [ 2146.577467] tpm_inf_pnp 00:03: >saving TPM state Oct 19 15:46:42 loki kernel: [ 2146.595089] tpm_inf_pnp 00:03: >Timeout while clearing FIFO Oct 19 15:46:42 loki kernel: [ 2146.595092] tpm_inf_pnp 00:03: >error while saving TPM state Oct 19 15:46:42 loki kernel: [ 2146.595103] legacy_suspend(): pnp_bus_suspend+0x0/0x70 returns -5 Oct 19 15:46:42 loki kernel: [ 2146.595123] PM: Device 00:03 failed to suspend: error -5 Oct 19 15:46:42 loki kernel: [ 2146.813354] sd 2:0:1:0: >[sda] Stopping disk Oct 19 15:46:42 loki kernel: [ 2146.948595] PM: suspend of drv:sd dev:2:0:1:0 complete after 372.190 msecs Oct 19 15:46:42 loki kernel: [ 2146.948642] PM: Some devices failed to suspend Oct 19 15:46:42 loki kernel: [ 2146.951168] sd 2:0:1:0: >[sda] Starting disk log information when tpm_infineon is loaded: Oct 19 16:01:35 loki kernel: [ 3044.447305] tpm_inf_pnp 00:03: >Found TPM with ID IFX0101 Oct 19 16:01:35 loki kernel: [ 3044.447375] tpm_inf_pnp 00:03: >TPM found: config base 0x4e, data base 0x4700, chip version 0x000b, vendor id 0x15d1 (Infineon), product id 0x000b (SLB 9635 TT 1.2) part of successful suspend behavior after "modprobe -r tpm_infineon": Oct 19 16:10:58 loki kernel: [ 3603.184426] PM: Syncing filesystems ... done. Oct 19 16:10:58 loki kernel: [ 3603.194924] PM: Preparing system for mem sleep Oct 19 16:12:32 loki kernel: [ 3603.211750] Freezing user space processes ... (elapsed 0.01 seconds) done. Oct 19 16:12:32 loki kernel: [ 3603.228207] Freezing remaining freezable tasks ... (elapsed 0.01 seconds) done. Oct 19 16:12:32 loki kernel: [ 3603.244163] PM: Entering mem sleep Oct 19 16:12:32 loki kernel: [ 3603.244428] Suspending console(s) (use no_console_suspend to debug) Oct 19 16:12:32 loki kernel: [ 3603.248241] sd 2:0:1:0: >[sda] Synchronizing SCSI cache Oct 19 16:12:32 loki kernel: [ 3603.249462] ata_piix :00:1f.1: >power state changed by ACPI to D3 Oct 19 16:12:32 loki kernel: [ 3603.249691] pciehp :00:1c.0:pcie04: >pciehp_suspend ENTRY Oct 19 16:12:32 loki kernel: [ 3603.264125] pciehp :00:1c.1:pcie04: >pciehp_suspend ENTRY Oct 19 16:12:32 loki kernel: [ 3603.368026] PM: suspend of drv:snd_hda_intel dev::00:1b.0 complete after 118.325 msecs Oct 19 16:12:32 loki kernel: [ 3603.368177] sd 2:0:1:0: >[sda] Stopping disk Oct 19 16:12:32 loki kernel: [ 3603.506384] PM: suspend of drv:sd dev:2:0:1:0 complete after 258.143 msecs Oct 19 16:12:32 loki kernel: [ 3603.506405] PM: suspend of drv:scsi dev:target2:0:1 complete after 258.068 msecs Oct 19 16:12:32 loki kernel: [ 3603.506413] PM: suspend of drv:scsi dev:host2 complete after 257.796 msecs Oct 19 16:12:32 loki kernel: [ 3603.506450] PM: suspend of drv: dev:ata3 complete after 257.767 msecs Oct 19 16:12:32 loki kernel: [ 3603.520041] PM: suspend of drv:ata_piix dev::00:1f.2 complete after 270.699 msecs Oct 19 16:12:32 loki kernel: [ 3603.600043] PM: suspend of drv:radeon dev::01:00.0 complete after 350.769 msecs Oct 19 16:12:32 loki kernel: [ 3603.600065] PM: suspend of drv:pcieport dev::00:01.0 complete after 350.332 msecs Oct 19 16:12:32 loki kernel: [ 3603.600088] PM: suspend of drv: dev:pci:00 complete after 350.294 msecs Oct 19 16:12:32 loki kernel: [ 3603.600104] PM: suspend of devices complete after 355.380 msecs Oct 19 16:12:32 loki kernel: [ 3603.600106] PM: suspend devices took 0.356 second
[Kernel-packages] [Bug 1453292] [NEW] Can't Type in LUKS Password
Public bug reported: When trying to enter in my LUKS password to decrypt my drive, I try typing and nothing appears in the text box. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-16-generic 3.19.0-16.16 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ryan 2197 F pulseaudio /dev/snd/pcmC0D0c: ryan 2197 F...m pulseaudio /dev/snd/pcmC0D0p: ryan 2197 F...m pulseaudio /dev/snd/controlC0: ryan 2197 F pulseaudio CurrentDesktop: GNOME Date: Fri May 8 17:52:30 2015 EcryptfsInUse: Yes MachineType: ASUSTeK COMPUTER INC. G75VW ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-16-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro recovery nomodeset RelatedPackageVersions: linux-restricted-modules-3.19.0-16-generic N/A linux-backports-modules-3.19.0-16-generic N/A linux-firmware 1.143 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/06/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: G75VW.207 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G75VW dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrG75VW.207:bd04/06/2012:svnASUSTeKCOMPUTERINC.:pnG75VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG75VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: G75VW dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug vivid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1453292 Title: Can't Type in LUKS Password Status in linux package in Ubuntu: New Bug description: When trying to enter in my LUKS password to decrypt my drive, I try typing and nothing appears in the text box. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-16-generic 3.19.0-16.16 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ryan 2197 F pulseaudio /dev/snd/pcmC0D0c: ryan 2197 F...m pulseaudio /dev/snd/pcmC0D0p: ryan 2197 F...m pulseaudio /dev/snd/controlC0: ryan 2197 F pulseaudio CurrentDesktop: GNOME Date: Fri May 8 17:52:30 2015 EcryptfsInUse: Yes MachineType: ASUSTeK COMPUTER INC. G75VW ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-16-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro recovery nomodeset RelatedPackageVersions: linux-restricted-modules-3.19.0-16-generic N/A linux-backports-modules-3.19.0-16-generic N/A linux-firmware 1.143 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/06/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: G75VW.207 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G75VW dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrG75VW.207:bd04/06/2012:svnASUSTeKCOMPUTERINC.:pnG75VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG75VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: G75VW dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1453292/+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 1453292] Re: Can't Type in LUKS Password
I updated the BIOS to the latest version per your request. Upon rebooting, the aforementioned bug is still occurring. Specifically when I get to the LUKS decryption part of booting up (http://i.stack.imgur.com/0yaNi.png - not mine specifically, but I'm talking about that prompt), when I try typing in my password to decrypt the volume, nothing shows up in the text box. No input seems to be handled at all. Here is the output you requested (after the BIOS update): ryan@r6578-G75VW:~$ sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date [sudo] password for ryan: G75VW.223 01/07/2013 ryan@r6578-G75VW:~$ ** 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/1453292 Title: Can't Type in LUKS Password Status in linux package in Ubuntu: Confirmed Bug description: When trying to enter in my LUKS password to decrypt my drive, I try typing and nothing appears in the text box. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-16-generic 3.19.0-16.16 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ryan 2197 F pulseaudio /dev/snd/pcmC0D0c: ryan 2197 F...m pulseaudio /dev/snd/pcmC0D0p: ryan 2197 F...m pulseaudio /dev/snd/controlC0: ryan 2197 F pulseaudio CurrentDesktop: GNOME Date: Fri May 8 17:52:30 2015 EcryptfsInUse: Yes MachineType: ASUSTeK COMPUTER INC. G75VW ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-16-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro recovery nomodeset RelatedPackageVersions: linux-restricted-modules-3.19.0-16-generic N/A linux-backports-modules-3.19.0-16-generic N/A linux-firmware 1.143 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/06/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: G75VW.207 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G75VW dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrG75VW.207:bd04/06/2012:svnASUSTeKCOMPUTERINC.:pnG75VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG75VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: G75VW dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1453292/+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 1453292] Re: Can't Type in LUKS Password
Okay, so I installed the latest upstream kernal as you requested (v4.1-rc2-vivid), and now it's recognizing input, but the new problem is that it isn't decrypting the disk. When I type anything in, it just shows up at the top of the screen. Pressing the return key just yields a new line. You can see this here: http://i1065.photobucket.com/albums/u400/Ryan6578/IMAG0161_zpsclcxhuew.jpg So, it seems that this bug persists in upstream versions as well. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Tags added: kernel-bug-exists-upstream kernel-bug-exists- upstream-4.1-rc2 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1453292 Title: Can't Type in LUKS Password Status in linux package in Ubuntu: Confirmed Bug description: When trying to enter in my LUKS password to decrypt my drive, I try typing and nothing appears in the text box. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-16-generic 3.19.0-16.16 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ryan 2197 F pulseaudio /dev/snd/pcmC0D0c: ryan 2197 F...m pulseaudio /dev/snd/pcmC0D0p: ryan 2197 F...m pulseaudio /dev/snd/controlC0: ryan 2197 F pulseaudio CurrentDesktop: GNOME Date: Fri May 8 17:52:30 2015 EcryptfsInUse: Yes MachineType: ASUSTeK COMPUTER INC. G75VW ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-16-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro recovery nomodeset RelatedPackageVersions: linux-restricted-modules-3.19.0-16-generic N/A linux-backports-modules-3.19.0-16-generic N/A linux-firmware 1.143 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/06/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: G75VW.207 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G75VW dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrG75VW.207:bd04/06/2012:svnASUSTeKCOMPUTERINC.:pnG75VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG75VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: G75VW dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1453292/+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 1453292] Re: Can't Type in LUKS Password
Nope. I upgraded from 14.04 -> 14.10 -> 15.04 incrementally. And I only started having this issue in 15.04 from what I can remember. I'm not sure if I experienced it in 14.10. I have to boot in recovery mode and enter in my LUKS password there. I also heard that a few other people were experiencing the same issue as me. https://askubuntu.com/questions/613139/ubuntu-15-04-usb-devices-powered- off-at-encrypted-root-password-prompt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1453292 Title: Can't Type in LUKS Password Status in linux package in Ubuntu: Incomplete Bug description: When trying to enter in my LUKS password to decrypt my drive, I try typing and nothing appears in the text box. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-16-generic 3.19.0-16.16 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ryan 2197 F pulseaudio /dev/snd/pcmC0D0c: ryan 2197 F...m pulseaudio /dev/snd/pcmC0D0p: ryan 2197 F...m pulseaudio /dev/snd/controlC0: ryan 2197 F pulseaudio CurrentDesktop: GNOME Date: Fri May 8 17:52:30 2015 EcryptfsInUse: Yes MachineType: ASUSTeK COMPUTER INC. G75VW ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-16-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro recovery nomodeset RelatedPackageVersions: linux-restricted-modules-3.19.0-16-generic N/A linux-backports-modules-3.19.0-16-generic N/A linux-firmware 1.143 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/06/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: G75VW.207 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G75VW dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrG75VW.207:bd04/06/2012:svnASUSTeKCOMPUTERINC.:pnG75VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG75VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: G75VW dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1453292/+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 686385] Re: kexec linux hangs
I've seen this on EFI based systems with older kernel versions. It worked with the base kernel in utopic. If anyone has any more information that could potentially point me to a solution that doesn't require a kernel change that would be preferred. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to kexec-tools in Ubuntu. https://bugs.launchpad.net/bugs/686385 Title: kexec linux hangs Status in kexec-tools package in Ubuntu: Confirmed Bug description: Binary package hint: kexec-tools sudo service gdm stop wget http://archive.ubuntu.com/ubuntu/dists/natty/main/installer-i386/current/images/netboot/ubuntu-installer/i386/linux sudo kexec --load linux sudo kexec -e On the console I see [300.123] Starting new kernel then the box hangs, caps lock light flashing. I tried using netconsole, nothing got logged. NETCONSLOGR=192.168.1.20 echo "start" | netcat -q 1 -u $NETCONSLOGR sudo modprobe netconsole netconsole="@/,@$NETCONSLOGR/" (veyepar)juser@dhcp42:~$ lsb_release -rd Description: Ubuntu natty (development branch) Release: 11.04 (veyepar)juser@dhcp42:~$ uname -a Linux dhcp42 2.6.37-8-generic #21-Ubuntu SMP Sun Dec 5 17:57:05 UTC 2010 i686 GNU/Linux (veyepar)juser@dhcp42:~$ apt-cache policy kexec-tools kexec-tools: Installed: 1:2.0.1-2ubuntu3 Candidate: 1:2.0.1-2ubuntu3 Version table: *** 1:2.0.1-2ubuntu3 0 500 http://us.archive.ubuntu.com/ubuntu/ natty/main i386 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kexec-tools/+bug/686385/+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 1568573] Re: [Lenovo Thinkpad T460] Ultra Dock external displays not detected after suspend/resume cycle
As per my previous comment, 4.6.0-040600-generic #201606030904 is not effected by this bug. I've been using it for a month without issue. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1568573 Title: [Lenovo Thinkpad T460] Ultra Dock external displays not detected after suspend/resume cycle Status in linux package in Ubuntu: Incomplete Bug description: Hello, System is Thinkpad T460, Skylake graphics, Thinkpad Ultra dock. DVI and HDMI displays connected via dock. 4.4.0-18. After a suspend-resume cycle, when the laptop is docked the dock connected external displays are not initialized/connected. If I disconnect the displays from the dock and connect them directly to the laptop, they are initialized successfully and can be configured via xrandr etc. If the laptop is power cycled, the displays can be used normally until the next suspend-resume cycle. Example from relevant dmesg: [drm:intel_dp_link_training_clock_recovery [i915_bpo]] *ERROR* too many voltage retries, give up [drm:intel_dp_link_training_clock_recovery [i915_bpo]] *ERROR* too many voltage retries, give up [drm:intel_dp_link_training_clock_recovery [i915_bpo]] *ERROR* too many voltage retries, give up [drm:intel_dp_start_link_train [i915_bpo]] *ERROR* failed to train DP, aborting [drm:intel_dp_set_idle_link_train [i915_bpo]] *ERROR* Timed out waiting for DP idle patterns [drm:intel_dp_link_training_clock_recovery [i915_bpo]] *ERROR* too many voltage retries, give up [drm:intel_dp_link_training_clock_recovery [i915_bpo]] *ERROR* too many voltage retries, give up [drm:intel_dp_link_training_clock_recovery [i915_bpo]] *ERROR* too many voltage retries, give up ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-18-generic 4.4.0-18.34 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ryan 1838 F pulseaudio Date: Sun Apr 10 09:39:32 2016 HibernationDevice: RESUME=UUID=04e04e17-3976-4daa-a1dd-2dd369aee83d InstallationDate: Installed on 2015-09-21 (201 days ago) InstallationMedia: It Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20FNCTO1WW ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-18-generic root=/dev/mapper/it--vg-root ro quiet PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.4.0-18-generic N/A linux-backports-modules-4.4.0-18-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-02-24 (45 days ago) dmi.bios.date: 03/09/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R06ET35W (1.09 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FNCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR06ET35W(1.09):bd03/09/2016:svnLENOVO:pn20FNCTO1WW:pvrThinkPadT460:rvnLENOVO:rn20FNCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20FNCTO1WW dmi.product.version: ThinkPad T460 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1568573/+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 1568573] Re: [Lenovo Thinkpad T460] Ultra Dock external displays not detected after suspend/resume cycle
I wasn't able to boot 4.6.1, but I was able to boot 4.6.0-040600-generic #201606030904. It does not seem to have the screen detection or freezing issues experienced in 4.4.0 when docking/un-docking (yet). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1568573 Title: [Lenovo Thinkpad T460] Ultra Dock external displays not detected after suspend/resume cycle Status in linux package in Ubuntu: Incomplete Bug description: Hello, System is Thinkpad T460, Skylake graphics, Thinkpad Ultra dock. DVI and HDMI displays connected via dock. 4.4.0-18. After a suspend-resume cycle, when the laptop is docked the dock connected external displays are not initialized/connected. If I disconnect the displays from the dock and connect them directly to the laptop, they are initialized successfully and can be configured via xrandr etc. If the laptop is power cycled, the displays can be used normally until the next suspend-resume cycle. Example from relevant dmesg: [drm:intel_dp_link_training_clock_recovery [i915_bpo]] *ERROR* too many voltage retries, give up [drm:intel_dp_link_training_clock_recovery [i915_bpo]] *ERROR* too many voltage retries, give up [drm:intel_dp_link_training_clock_recovery [i915_bpo]] *ERROR* too many voltage retries, give up [drm:intel_dp_start_link_train [i915_bpo]] *ERROR* failed to train DP, aborting [drm:intel_dp_set_idle_link_train [i915_bpo]] *ERROR* Timed out waiting for DP idle patterns [drm:intel_dp_link_training_clock_recovery [i915_bpo]] *ERROR* too many voltage retries, give up [drm:intel_dp_link_training_clock_recovery [i915_bpo]] *ERROR* too many voltage retries, give up [drm:intel_dp_link_training_clock_recovery [i915_bpo]] *ERROR* too many voltage retries, give up ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-18-generic 4.4.0-18.34 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ryan 1838 F pulseaudio Date: Sun Apr 10 09:39:32 2016 HibernationDevice: RESUME=UUID=04e04e17-3976-4daa-a1dd-2dd369aee83d InstallationDate: Installed on 2015-09-21 (201 days ago) InstallationMedia: It Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20FNCTO1WW ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-18-generic root=/dev/mapper/it--vg-root ro quiet PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.4.0-18-generic N/A linux-backports-modules-4.4.0-18-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-02-24 (45 days ago) dmi.bios.date: 03/09/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R06ET35W (1.09 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FNCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR06ET35W(1.09):bd03/09/2016:svnLENOVO:pn20FNCTO1WW:pvrThinkPadT460:rvnLENOVO:rn20FNCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20FNCTO1WW dmi.product.version: ThinkPad T460 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1568573/+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 1568573] Re: [Lenovo Thinkpad T460] Ultra Dock external displays not detected after suspend/resume cycle
I have been running the BIOS 1.10 since the day it was released. Behavior between 1.09 and 1.10 related to this bug did not change. R06ET36W (1.10 ) 03/23/2016 ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Tags removed: bios-outdated-1.10 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1568573 Title: [Lenovo Thinkpad T460] Ultra Dock external displays not detected after suspend/resume cycle Status in linux package in Ubuntu: Confirmed Bug description: Hello, System is Thinkpad T460, Skylake graphics, Thinkpad Ultra dock. DVI and HDMI displays connected via dock. 4.4.0-18. After a suspend-resume cycle, when the laptop is docked the dock connected external displays are not initialized/connected. If I disconnect the displays from the dock and connect them directly to the laptop, they are initialized successfully and can be configured via xrandr etc. If the laptop is power cycled, the displays can be used normally until the next suspend-resume cycle. Example from relevant dmesg: [drm:intel_dp_link_training_clock_recovery [i915_bpo]] *ERROR* too many voltage retries, give up [drm:intel_dp_link_training_clock_recovery [i915_bpo]] *ERROR* too many voltage retries, give up [drm:intel_dp_link_training_clock_recovery [i915_bpo]] *ERROR* too many voltage retries, give up [drm:intel_dp_start_link_train [i915_bpo]] *ERROR* failed to train DP, aborting [drm:intel_dp_set_idle_link_train [i915_bpo]] *ERROR* Timed out waiting for DP idle patterns [drm:intel_dp_link_training_clock_recovery [i915_bpo]] *ERROR* too many voltage retries, give up [drm:intel_dp_link_training_clock_recovery [i915_bpo]] *ERROR* too many voltage retries, give up [drm:intel_dp_link_training_clock_recovery [i915_bpo]] *ERROR* too many voltage retries, give up ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-18-generic 4.4.0-18.34 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ryan 1838 F pulseaudio Date: Sun Apr 10 09:39:32 2016 HibernationDevice: RESUME=UUID=04e04e17-3976-4daa-a1dd-2dd369aee83d InstallationDate: Installed on 2015-09-21 (201 days ago) InstallationMedia: It Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20FNCTO1WW ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-18-generic root=/dev/mapper/it--vg-root ro quiet PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.4.0-18-generic N/A linux-backports-modules-4.4.0-18-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-02-24 (45 days ago) dmi.bios.date: 03/09/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R06ET35W (1.09 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FNCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR06ET35W(1.09):bd03/09/2016:svnLENOVO:pn20FNCTO1WW:pvrThinkPadT460:rvnLENOVO:rn20FNCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20FNCTO1WW dmi.product.version: ThinkPad T460 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1568573/+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 1568573] Re: [Lenovo Thinkpad T460] Ultra Dock external displays not detected after suspend/resume cycle
I have noticed fewer freezing issues on docking, and a complete resolve of this bug after installing the Intel SKL GuC firmware blob; along with running a drm-next or drm-next-intel kernel. The GuC blob seems to be missing from linux-firmware, I no longer receive error messages about missing i915 firmware when doing kernel upgrades or generating initrd. I managed to keep an uptime of almost 2 weeks without graphics crashes with a drm-next kernel, docking the laptop ~30 times over that period. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1568573 Title: [Lenovo Thinkpad T460] Ultra Dock external displays not detected after suspend/resume cycle Status in linux package in Ubuntu: Confirmed Bug description: Hello, System is Thinkpad T460, Skylake graphics, Thinkpad Ultra dock. DVI and HDMI displays connected via dock. 4.4.0-18. After a suspend-resume cycle, when the laptop is docked the dock connected external displays are not initialized/connected. If I disconnect the displays from the dock and connect them directly to the laptop, they are initialized successfully and can be configured via xrandr etc. If the laptop is power cycled, the displays can be used normally until the next suspend-resume cycle. Example from relevant dmesg: [drm:intel_dp_link_training_clock_recovery [i915_bpo]] *ERROR* too many voltage retries, give up [drm:intel_dp_link_training_clock_recovery [i915_bpo]] *ERROR* too many voltage retries, give up [drm:intel_dp_link_training_clock_recovery [i915_bpo]] *ERROR* too many voltage retries, give up [drm:intel_dp_start_link_train [i915_bpo]] *ERROR* failed to train DP, aborting [drm:intel_dp_set_idle_link_train [i915_bpo]] *ERROR* Timed out waiting for DP idle patterns [drm:intel_dp_link_training_clock_recovery [i915_bpo]] *ERROR* too many voltage retries, give up [drm:intel_dp_link_training_clock_recovery [i915_bpo]] *ERROR* too many voltage retries, give up [drm:intel_dp_link_training_clock_recovery [i915_bpo]] *ERROR* too many voltage retries, give up ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-18-generic 4.4.0-18.34 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ryan 1838 F pulseaudio Date: Sun Apr 10 09:39:32 2016 HibernationDevice: RESUME=UUID=04e04e17-3976-4daa-a1dd-2dd369aee83d InstallationDate: Installed on 2015-09-21 (201 days ago) InstallationMedia: It Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20FNCTO1WW ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-18-generic root=/dev/mapper/it--vg-root ro quiet PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.4.0-18-generic N/A linux-backports-modules-4.4.0-18-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-02-24 (45 days ago) dmi.bios.date: 03/09/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R06ET35W (1.09 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FNCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR06ET35W(1.09):bd03/09/2016:svnLENOVO:pn20FNCTO1WW:pvrThinkPadT460:rvnLENOVO:rn20FNCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20FNCTO1WW dmi.product.version: ThinkPad T460 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1568573/+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 1568573] Re: [Lenovo Thinkpad T460] Ultra Dock external displays not detected after suspend/resume cycle
The 4.7-rc1 kernel was not bootable on my system. However, I have been testing with 4.6.0-996-generic #201605082201 from drm-next and the behavior is better. With the drm-next kernel, I am able to dock/undock the laptop multiple times without a freeze and the displays are recognized and can be setup. The configured display layout is applied successfully on docking, unlike with the 4.4.0-22 kernel. I do have one persistent issue with the drm-next kernel, I have to change to a VT and back to get display output after docking - but I don't think its related to this issue. This intel stuff sure seems like a mess. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1568573 Title: [Lenovo Thinkpad T460] Ultra Dock external displays not detected after suspend/resume cycle Status in linux package in Ubuntu: Incomplete Bug description: Hello, System is Thinkpad T460, Skylake graphics, Thinkpad Ultra dock. DVI and HDMI displays connected via dock. 4.4.0-18. After a suspend-resume cycle, when the laptop is docked the dock connected external displays are not initialized/connected. If I disconnect the displays from the dock and connect them directly to the laptop, they are initialized successfully and can be configured via xrandr etc. If the laptop is power cycled, the displays can be used normally until the next suspend-resume cycle. Example from relevant dmesg: [drm:intel_dp_link_training_clock_recovery [i915_bpo]] *ERROR* too many voltage retries, give up [drm:intel_dp_link_training_clock_recovery [i915_bpo]] *ERROR* too many voltage retries, give up [drm:intel_dp_link_training_clock_recovery [i915_bpo]] *ERROR* too many voltage retries, give up [drm:intel_dp_start_link_train [i915_bpo]] *ERROR* failed to train DP, aborting [drm:intel_dp_set_idle_link_train [i915_bpo]] *ERROR* Timed out waiting for DP idle patterns [drm:intel_dp_link_training_clock_recovery [i915_bpo]] *ERROR* too many voltage retries, give up [drm:intel_dp_link_training_clock_recovery [i915_bpo]] *ERROR* too many voltage retries, give up [drm:intel_dp_link_training_clock_recovery [i915_bpo]] *ERROR* too many voltage retries, give up ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-18-generic 4.4.0-18.34 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ryan 1838 F pulseaudio Date: Sun Apr 10 09:39:32 2016 HibernationDevice: RESUME=UUID=04e04e17-3976-4daa-a1dd-2dd369aee83d InstallationDate: Installed on 2015-09-21 (201 days ago) InstallationMedia: It Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20FNCTO1WW ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-18-generic root=/dev/mapper/it--vg-root ro quiet PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.4.0-18-generic N/A linux-backports-modules-4.4.0-18-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-02-24 (45 days ago) dmi.bios.date: 03/09/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R06ET35W (1.09 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FNCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR06ET35W(1.09):bd03/09/2016:svnLENOVO:pn20FNCTO1WW:pvrThinkPadT460:rvnLENOVO:rn20FNCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20FNCTO1WW dmi.product.version: ThinkPad T460 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1568573/+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 1627905] [NEW] Ubuntu can't be installed to certain Lenovo Yoga laptops because the fakeraid storage mode is not supported.
Public bug reported: Several Lenovo Yoga laptops do not allow the user to install any current Linux distributions due to being BIOS-locked to a RAID mode and Linux does not support this. You can boot a Linux live environment, but when you go to install, it will not see the Solid State Drive and it does not appear as a PCI device. The affected models are the Yoga 900 ISK2, 900S, 710S, and 900 ISK for Business, and probably the new Yoga Book and Yoga 910 as well. Lenovo has stated that removing the AHCI option from the BIOS is a feature and that they don't plan to fix this. There have been some blog postings and news articles about this issue lately. Here is the Lenovo Forums topic: https://forums.lenovo.com/t5/Linux-Discussion/Yoga-900-13ISK2-BIOS- update-for-setting-RAID-mode-for-missing/td-p/3339206/highlight/false (Note that this says it is solved, but it is not. Lenovo replied that they won't fix it and that Linux is not supported on these laptops.) Matthew Garrett's blog post is here: https://mjg59.dreamwidth.org/44694.html I approached him with the idea that perhaps the Linux kernel could be modified to reset the hardware and put it into AHCI mode after GRUB loads the kernel (according to him, GRUB doesn't need to be modified because it uses the uEFI firmware's disk access), and then Linux could proceed to boot. Here's what he said: "If you wanted to try that, the best place to do it would be the UEFI setup code in the kernel under arch/x86/boot/compressed/eboot.c - that way you can do it independent of bootloader. Grub's able to read files anyway since it's using the firmware calls to do that. The power management thing isn't about the SSD itself, it's about ensuring that the controller is programmed correctly so that the entire CPU package can enter deep sleep states. Modern systems should idle at around 4W at most, so small amounts make abig difference here." [...] "If the firmware hasn't locked the control bit and if the hardware is ok with suddenly being reconfigured, sure, that ought to work. Doing it in eboot.c means you're doing it before any PCI enumeration has occurred, which makes it more likely that things will work out well." [...] "I'll take a quick look at the 10-series chipset docs to see if it's documented, and if so I'll throw a quick patch together - but I'm probably not going to try pushing it upstream, I'm afraid. If it does work, I'm fine with anybody else doing so." I heaven't heard anything back lately, so I am putting this in a bug report so that the Ubuntu maintainers are aware of the issue. It seems like a few lines of kernel code are all that is really required to fix this and restore the ability of Linux distributions to be installed on half a dozen laptops (probably more to come, since Lenovo says that the industry is moving to this!). ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1627905 Title: Ubuntu can't be installed to certain Lenovo Yoga laptops because the fakeraid storage mode is not supported. Status in linux package in Ubuntu: Incomplete Bug description: Several Lenovo Yoga laptops do not allow the user to install any current Linux distributions due to being BIOS-locked to a RAID mode and Linux does not support this. You can boot a Linux live environment, but when you go to install, it will not see the Solid State Drive and it does not appear as a PCI device. The affected models are the Yoga 900 ISK2, 900S, 710S, and 900 ISK for Business, and probably the new Yoga Book and Yoga 910 as well. Lenovo has stated that removing the AHCI option from the BIOS is a feature and that they don't plan to fix this. There have been some blog postings and news articles about this issue lately. Here is the Lenovo Forums topic: https://forums.lenovo.com/t5/Linux-Discussion/Yoga-900-13ISK2-BIOS- update-for-setting-RAID-mode-for-missing/td-p/3339206/highlight/false (Note that this says it is solved, but it is not. Lenovo replied that they won't fix it and that Linux is not supported on these laptops.) Matthew Garrett's blog post is here: https://mjg59.dreamwidth.org/44694.html I approached him with the idea that perhaps the Linux kernel could be modified to reset the hardware and put it into AHCI mode after GRUB loads the kernel (according to him, GRUB doesn't need to be modified because it uses the uEFI firmware's disk access), and then Linux could proceed to boot. Here's what he said: "If you wanted to try that, the best place to do it would be the UEFI setup code in the kernel under arch/x86/boot/compressed/eboot.c - that way you can do it independent of bootloader. Grub's able to read files anyway since it's using the firmware calls to do that. The power management thing isn't about the SSD
[Kernel-packages] [Bug 1372609] Re: Touchpad detected as mouse on Asus ux303ln laptop
Thanks to Pilot6! #317/#330 works fine on my machine (Zenbook UX303LA with Ubuntu 15.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/1372609 Title: Touchpad detected as mouse on Asus ux303ln laptop Status in linux package in Ubuntu: Fix Released Status in linux package in Arch Linux: New Bug description: Hi! I'm following the bug reporting documentation here: https://wiki.ubuntu.com/DebuggingTouchpadDetection#In_case_Touchpad_features_like_scrolling.2C_tapping.2C_etc._do_not_work_at_all. The touchpad on my new Asus ux303ln laptop is detected as a mouse, so I can't access touchpad features such as two-finger scrolling. The laptop was very recently released and I couldn't find any outstanding firmware updates for it through Asus's Windows-based tools. % lsb_release -rd Description: Ubuntu 14.04.1 LTS Release: 14.04 Per the instructions on the wiki, I'm attaching output from /proc/bus/input/devices,` xinput --list`, and /var/log/Xorg.0.log. This machine also has a touchscreen, which I'm fairly certain is the "maXtouch digitizer" visible in the logs. I haven't yet restarted in Windows to see if it says anything useful about the touchpad, but I can do so if that's helpful. This is a fresh install of 14.04 and I haven't done much customization of it apart from installing some applications and changing the default resolution. The only relevant bit I noticed in /var/log/dmesg is this: [3.967547] input: PS/2 Logitech Wheel Mouse as /devices/platform/i8042/serio4/input/input11 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-35-generic 3.13.0-35.62 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tim2234 F pulseaudio /dev/snd/controlC1: tim2234 F pulseaudio CurrentDesktop: Unity Date: Mon Sep 22 14:30:33 2014 HibernationDevice: RESUME=UUID=e6052f15-271a-4424-aac2-9b0ee1e490ed InstallationDate: Installed on 2014-09-22 (0 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 03eb:8a32 Atmel Corp. Bus 001 Device 002: ID 064e:9700 Suyin Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX303LN ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-35-generic.efi.signed root=UUID=4f908b1b-e06f-4dc9-9642-e952d2598e42 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-35-generic N/A linux-backports-modules-3.13.0-35-generic N/A linux-firmware 1.127.6 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/23/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX303LN.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX303LN dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX303LN.203:bd06/23/2014:svnASUSTeKCOMPUTERINC.:pnUX303LN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX303LN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: UX303LN dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1372609/+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 1432869] Re: No wireless access for BCM 43162
I've confirmed this is the case. Tried everything I could find on various forums, but the drivers in wl (and other related packages) do not provide connectivity with this chipset. ** Package changed: linux (Ubuntu) => wl (Ubuntu) ** Changed in: wl (Ubuntu) Status: Expired => 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/1432869 Title: No wireless access for BCM 43162 Status in wl package in Ubuntu: Confirmed Bug description: No connectivity on 14.04.2 for Lenovo Edge E555 using a BCM43162 wireless adapter. Here is what I got with lspci -nnk | grep -iA2 net Network Controller [0280]: Broadcom Corporation Device [14e4:43ae] (rev 02) Subsystem: Lenovo Device [17aa:0622] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wl/+bug/1432869/+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 1436940] Re: Atheros wifi 168c:0041(QCA6164) is not supported
Following Diego's steps above, "lshw -C network" no longer says my network card is unclaimed and the driver assigned to it is ath10k_pci. However, I see no difference in the functionality of the card (still can not use it). Lenovo Flex 3 14" QCA6164 168c:0041 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1436940 Title: Atheros wifi 168c:0041(QCA6164) is not supported Status in linux package in Ubuntu: Confirmed Status in linux source package in Vivid: Confirmed Status in linux source package in Wily: Confirmed Bug description: The atheros wireless device (168c:0041) isn't supported by the ath10k_pci kernel driver. Found in several laptop models: Lenovo Z70 Lenovo G50-45 Lenovo G50-80 Lenovo Edge 15 Lenovo Yoga 3 11 Lenovo Flex 3-1470 Samsung ATIV Book 9 NP930X2K ProblemType: BugDistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-9-generic 3.19.0-9.9 ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic x86_64 ApportVersion: 2.16.2-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicholas 1695 F pulseaudio /dev/snd/controlC1: nicholas 1695 F pulseaudio CurrentDesktop: Unity Date: Thu Mar 26 09:47:16 2015 HibernationDevice: RESUME=UUID=5b068cd8-e60a-49b9-a88e-1581bb6b3dc1 InstallationDate: Installed on 2015-03-25 (1 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) IwConfig: eth0 no wireless extensions. lono wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0cf3:e300 Atheros Communications, Inc. Bus 001 Device 003: ID 5986:0652 Acer, Inc Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80E5 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-9-generic root=UUID=e52867c5-0b50-42fb-8288-f30765f926c5 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-9-generic N/A linux-backports-modules-3.19.0-9-generic N/A linux-firmware1.143SourcePackage: linux UpgradeStatus: Upgraded to vivid on 2015-03-26 (0 days ago) dmi.bios.date: 06/20/2014 dmi.bios.vendor: LENOVO dmi.bios.version: B0CN69WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lenovo G50-80 dmi.board.vendor: LENOVO dmi.board.version: 31900058 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G50-80 dmi.modalias: dmi:bvnLENOVO:bvrB0CN69WW:bd06/20/2014:svnLENOVO:pn80E5:pvrLenovoG50-80:rvnLENOVO:rnLenovoG50-80:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoG50-80: dmi.product.name: 80E5 dmi.product.version: Lenovo G50-80 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1436940/+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 1436940] Re: Atheros wifi 168c:0041(QCA6164) is not supported
Hi Diego, I followed every step you outlined including patching the firmware and creating the conf file and adding the skip_otp line. Thank you for your help! "sudo lshw -C network" *-network description: Network controller product: Qualcomm Atheros vendor: Qualcomm Atheros physical id: 0 bus info: pci@:02:00.0 version: 20 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list configuration: driver=ath10k_pci latency=0 resources: irq:49 memory:e400-e41f *-network description: Ethernet interface product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:03:00.0 logical name: eth0 version: 10 serial: 54:ee:75:4e:86:b7 size: 1Gbit/s capacity: 1Gbit/s width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=r8169 driverversion=2.3LK-NAPI duplex=full firmware=rtl8168g-3_0.0.1 04/23/13 ip=192.168.1.4 latency=0 link=yes multicast=yes port=MII speed=1Gbit/s resources: irq:44 ioport:4000(size=256) memory:e4204000-e4204fff memory:e420-e4203fff "sudo ip link show" 1: lo: mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: eth0: mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000 link/ether 54:ee:75:4e:86:b7 brd ff:ff:ff:ff:ff:ff "sudo rfkill list" 0: ideapad_wlan: Wireless LAN Soft blocked: no Hard blocked: no 1: ideapad_bluetooth: Bluetooth Soft blocked: no Hard blocked: no 6: hci0: Bluetooth Soft blocked: no Hard blocked: no "dmesg | grep -i ath" [2.035031] [] warn_slowpath_common+0x8a/0xc0 [2.035032] [] warn_slowpath_fmt+0x46/0x50 [2.218428] ath10k_pci :02:00.0: pci irq msi-x interrupts 8 irq_mode 0 reset_mode 0 [2.405198] ath10k_pci :02:00.0: Direct firmware load for ath10k/cal-pci-:02:00.0.bin failed with error -2 [2.405407] ath10k_pci :02:00.0: Direct firmware load for ath10k/QCA6174/hw2.1/board-pci-168c:0041:17aa:3545.bin failed with error -2 [2.405409] ath10k_pci :02:00.0: failed to load spec board file, falling back to generic: -2 [3.583538] ath10k_pci :02:00.0: received unsolicited fw crash interrupt [3.583555] ath10k_pci :02:00.0: received unsolicited fw crash interrupt [3.584948] ath10k_pci :02:00.0: firmware crashed! (uuid e628e267-4dee-4da1-8a51-ed236bd4fc19) [3.584969] ath10k_pci :02:00.0: qca6174 hw2.1 (0x0501, 0x003405ff, 168c:0041:17aa:3545 fallback) fw WLAN.RM.1.1-00141 api 5 htt-ver 0.0 wmi-op 4 htt-op 3 cal otp max-sta 32 features ignore-otp,no-4addr-pad [3.584973] ath10k_pci :02:00.0: debug 1 debugfs 1 tracing 0 dfs 0 testmode 0 [3.587298] ath10k_pci :02:00.0: firmware register dump: [3.587303] ath10k_pci :02:00.0: [00]: 0x0501 0x15B3 0x000A012D 0x00955B31 [3.587316] ath10k_pci :02:00.0: [04]: 0x000A012D 0x00060330 0x0016 0x8A685006 [3.587317] ath10k_pci :02:00.0: [08]: 0x 0x0040 0x00400600 0x0001 [3.587319] ath10k_pci :02:00.0: [12]: 0x0009 0x 0x00931C61 0x00931C7D [3.587321] ath10k_pci :02:00.0: [16]: 0x0096BDBC 0x009287BD 0x 0x [3.587323] ath10k_pci :02:00.0: [20]: 0x400A012D 0x0040E2B0 0x00955A00 0x00404590 [3.587326] ath10k_pci :02:00.0: [24]: 0x809287D9 0x0040E310 0x7A508AF8 0xC00A012D [3.587333] ath10k_pci :02:00.0: [28]: 0x809288D7 0x0040E340 0x 0xFFF08040 [3.587337] ath10k_pci :02:00.0: [32]: 0x809290FE 0x0040E360 0x0040 0x00400600 [3.587340] ath10k_pci :02:00.0: [36]: 0x80929205 0x0040E380 0x 0x00400600 [3.587341] ath10k_pci :02:00.0: [40]: 0x40928024 0x0040E3B0 0x0040D3D0 0x0040D3D0 [3.587343] ath10k_pci :02:00.0: [44]: 0x 0x0040E3D0 0x009BB001 0x00040020 [3.587345] ath10k_pci :02:00.0: [48]: 0x00401BF0 0x0001 0x00404B9C 0x0040 [3.587346] ath10k_pci :02:00.0: [52]: 0x40928024 0x0040E3B0 0x0040D3D0 0x0040D3D0 [3.587348] ath10k_pci :02:00.0: [56]: 0xAB862A00 0x9531BA92 0xE7F0581D 0xC0424502 [4.580823] ath10k_pci :02:00.0: failed to receive control response completion, polling.. [5.581684] ath10k_pci :02:00.0: ctl_resp never came in (-110) [5.581688] ath10k_pci :02:00.0: failed to connect to HTC: -110 [5.659418] ath10k_pci :02:00.0: could not init core (-110) [5.659438] ath10k_pci :02:00.0: could not probe fw (-110) [5.669735] ath10k_pci :02:00.0: cannot restart
[Kernel-packages] [Bug 1436940] Re: Atheros wifi 168c:0041(QCA6164) is not supported
Hi Diego, Still no luck (copied the QCA6164 firmware.bin and board.bin to QCA6174/hw2.1/) but I am getting different outputs on dmesg. "dmesg | grep -i ath" [2.014702] [] warn_slowpath_common+0x8a/0xc0 [2.014704] [] warn_slowpath_fmt+0x46/0x50 [2.076696] ath10k_pci :02:00.0: pci irq msi-x interrupts 8 irq_mode 0 reset_mode 0 [2.264949] ath10k_pci :02:00.0: Direct firmware load for ath10k/cal-pci-:02:00.0.bin failed with error -2 [2.265161] ath10k_pci :02:00.0: Direct firmware load for ath10k/QCA6174/hw2.1/board-pci-168c:0041:17aa:3545.bin failed with error -2 [2.265162] ath10k_pci :02:00.0: failed to load spec board file, falling back to generic: -2 [3.437786] ath10k_pci :02:00.0: received unsolicited fw crash interrupt [3.437794] ath10k_pci :02:00.0: received unsolicited fw crash interrupt [4.436590] ath10k_pci :02:00.0: failed to receive control response completion, polling.. [4.436912] ath10k_pci :02:00.0: received unsolicited fw crash interrupt [4.437024] ath10k_pci :02:00.0: received unsolicited fw crash interrupt [5.437385] ath10k_pci :02:00.0: Service connect timeout [5.437393] ath10k_pci :02:00.0: failed to connect htt (-110) [5.514369] ath10k_pci :02:00.0: could not init core (-110) [5.514390] ath10k_pci :02:00.0: could not probe fw (-110) "dmesg | tail" [4.437024] ath10k_pci :02:00.0: received unsolicited fw crash interrupt [4.620546] [drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt lied (SDE)! [5.437385] ath10k_pci :02:00.0: Service connect timeout [5.437393] ath10k_pci :02:00.0: failed to connect htt (-110) [5.514369] ath10k_pci :02:00.0: could not init core (-110) [5.514390] ath10k_pci :02:00.0: could not probe fw (-110) [6.606130] r8169 :03:00.0 eth0: link up [9.611721] [drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt lied (SDE)! [9.800304] [drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt lied (SDE)! [9.989036] [drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt lied (SDE)! "lspci -nnk" 02:00.0 Network controller [0280]: Qualcomm Atheros Device [168c:0041] (rev 20) Subsystem: Lenovo Device [17aa:3545] Kernel driver in use: ath10k_pci -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1436940 Title: Atheros wifi 168c:0041(QCA6164) is not supported Status in linux package in Ubuntu: Confirmed Status in linux source package in Vivid: Confirmed Status in linux source package in Wily: Confirmed Bug description: The atheros wireless device (168c:0041) isn't supported by the ath10k_pci kernel driver. Found in several laptop models: Lenovo Z70 Lenovo G50-45 Lenovo G50-80 Lenovo Edge 15 Lenovo Yoga 3 11 Lenovo Flex 3-1470 Samsung ATIV Book 9 NP930X2K ProblemType: BugDistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-9-generic 3.19.0-9.9 ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic x86_64 ApportVersion: 2.16.2-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicholas 1695 F pulseaudio /dev/snd/controlC1: nicholas 1695 F pulseaudio CurrentDesktop: Unity Date: Thu Mar 26 09:47:16 2015 HibernationDevice: RESUME=UUID=5b068cd8-e60a-49b9-a88e-1581bb6b3dc1 InstallationDate: Installed on 2015-03-25 (1 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) IwConfig: eth0 no wireless extensions. lono wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0cf3:e300 Atheros Communications, Inc. Bus 001 Device 003: ID 5986:0652 Acer, Inc Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80E5 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-9-generic root=UUID=e52867c5-0b50-42fb-8288-f30765f926c5 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-9-generic N/A linux-backports-modules-3.19.0-9-generic N/A linux-firmware1.143SourcePackage: linux UpgradeStatus: Upgraded to vivid on 2015-03-26 (0 days ago) dmi.bios.date: 06/20/2014 dmi.bios.vendor: LENOVO dmi.bios.version: B0CN69WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lenovo G50-80 dmi.board.vendor: LENOVO dmi.board.version: 31900058 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G50-80 dmi.modalias: dmi:bvnLENOVO:bvrB0CN69WW:bd06/20/2014:svnLENOVO:pn80
[Kernel-packages] [Bug 1436940] Re: Atheros wifi 168c:0041(QCA6164) is not supported
Hi Diego, It's finally working! Thank you so much for your help. What seemed to be the final problem is I was running kernel 4.2 but after downgrading to your kernel (4.1.0), everything worked. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1436940 Title: Atheros wifi 168c:0041(QCA6164) is not supported Status in linux package in Ubuntu: Confirmed Status in linux source package in Vivid: Confirmed Status in linux source package in Wily: Confirmed Bug description: The atheros wireless device (168c:0041) isn't supported by the ath10k_pci kernel driver. Found in several laptop models: Lenovo Z70 Lenovo G50-45 Lenovo G50-80 Lenovo Edge 15 Lenovo Yoga 3 11 Lenovo Flex 3-1470 Samsung ATIV Book 9 NP930X2K ProblemType: BugDistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-9-generic 3.19.0-9.9 ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic x86_64 ApportVersion: 2.16.2-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicholas 1695 F pulseaudio /dev/snd/controlC1: nicholas 1695 F pulseaudio CurrentDesktop: Unity Date: Thu Mar 26 09:47:16 2015 HibernationDevice: RESUME=UUID=5b068cd8-e60a-49b9-a88e-1581bb6b3dc1 InstallationDate: Installed on 2015-03-25 (1 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) IwConfig: eth0 no wireless extensions. lono wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0cf3:e300 Atheros Communications, Inc. Bus 001 Device 003: ID 5986:0652 Acer, Inc Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80E5 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-9-generic root=UUID=e52867c5-0b50-42fb-8288-f30765f926c5 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-9-generic N/A linux-backports-modules-3.19.0-9-generic N/A linux-firmware1.143SourcePackage: linux UpgradeStatus: Upgraded to vivid on 2015-03-26 (0 days ago) dmi.bios.date: 06/20/2014 dmi.bios.vendor: LENOVO dmi.bios.version: B0CN69WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lenovo G50-80 dmi.board.vendor: LENOVO dmi.board.version: 31900058 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G50-80 dmi.modalias: dmi:bvnLENOVO:bvrB0CN69WW:bd06/20/2014:svnLENOVO:pn80E5:pvrLenovoG50-80:rvnLENOVO:rnLenovoG50-80:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoG50-80: dmi.product.name: 80E5 dmi.product.version: Lenovo G50-80 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1436940/+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 2042716] Re: [Intel AX201] Direct firmware load for iwlwifi-so-a0-hr-b0-83.ucode failed with error -2
This is also a problem for me using beelink s12 pro ubuntu 23.10 with
ax201 intel however adding the file in manually didn't fix the problem,
still detects the ax101 and can't connect to wifi or use bluetooth. The
error message does go away though
--
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/2042716
Title:
[Intel AX201] Direct firmware load for iwlwifi-so-a0-hr-b0-83.ucode
failed with error -2
Status in linux-firmware package in Ubuntu:
New
Status in linux-firmware source package in Jammy:
New
Status in linux-firmware source package in Mantic:
Fix Committed
Bug description:
[Impact]
Wifi is not functional.
[Fix]
Cherry-pick relevant FW files.
[Where Problems Could Occur]
Only machines with relevant Wifi HW is affected. Potential crashes and
hangs dues to bad FW.
[Summary]
I just upgraded my pc from 23.04 to 23.10,
and found that my wifi was dead, turn out it's because the firmware load
failed.
[Reproduce Steps]
1. Upgrade 23.04 to 23.10
[Results]
Expected: firmware can be loaded
Actual: firmware load failed
[Additional Information]
1. The firmware can be loaded successfully in 23.04
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-firmware 20230919.git3672ccab-0ubuntu2.1
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Uname: Linux 6.5.0-10-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sat Nov 4 16:58:00 2023
Dependencies: firmware-sof-signed 2.2.6-1ubuntu1
InstallationDate: Installed on 2023-02-09 (268 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64
(20220419)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-10-generic
root=UUID=d2e4673c-e5fe-4a04-8647-bc56a5fa2a08 ro quiet splash
nvidia.NVreg_PreserveVideoMemoryAllocations=1 vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-6.5.0-10-generic N/A
linux-backports-modules-6.5.0-10-generic N/A
linux-firmware20230919.git3672ccab-0ubuntu2.1
RfKill:
0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
SourcePackage: linux-firmware
UpgradeStatus: Upgraded to mantic on 2023-11-04 (0 days ago)
dmi.bios.date: 01/06/2023
dmi.bios.release: 8.9
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0809
dmi.board.asset.tag: Default string
dmi.board.name: PRIME Z790-P WIFI
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr0809:bd01/06/2023:br8.9:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ790-PWIFI:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: ASUS
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2042716/+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 1796292] Re: Tight timeout for bcache removal causes spurious failures
Andrea, thanks for the updated kernels.
On the first one, I got 23 installs before I ran into an issue; I'll
test the newer kernel next.
https://paste.ubuntu.com/p/2B4Kk3wbvQ/
[ 5436.870482] BUG: unable to handle kernel NULL pointer dereference at
09b8
[ 5436.873374] IP: cache_set_flush+0xf6/0x190 [bcache]
[ 5436.875208] PGD 0 P4D 0
[ 5436.876488] Oops: [#1] SMP PTI
[ 5436.877842] Modules linked in: zfs(PO) zunicode(PO) zavl(PO) icp(PO)
zcommon(PO) znvpair(PO) spl(O) nls_utf8 isofs ppdev nls_iso8859_1 kvm_intel kvm
irqbypass joydev input_leds serio_raw parport_pc parport qemu_fw_cfg mac_hid
sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp
libiscsi scsi_transport_iscsi virtio_rng ip_tables x_tables autofs4 btrfs
zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor
async_tx xor raid6_pq libcrc32c raid0 multipath linear raid1 bcache psmouse
nvme nvme_core virtio_blk virtio_net virtio_scsi floppy i2c_piix4 pata_acpi
[ 5436.896104] CPU: 0 PID: 11216 Comm: kworker/0:1 Tainted: P O
4.15.0-54-generic #58+lp1796292+1
[ 5436.899985] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS
0.0.0 02/06/2015
[ 5436.902645] Workqueue: events cache_set_flush [bcache]
[ 5436.904374] RIP: 0010:cache_set_flush+0xf6/0x190 [bcache]
[ 5436.906183] RSP: 0018:ab52826bbe58 EFLAGS: 00010202
[ 5436.909050] RAX: RBX: 94d104aa0cc0 RCX:
[ 5436.911939] RDX: RSI: 2001 RDI:
[ 5436.914448] RBP: ab52826bbe78 R08: 94d13f61ac30 R09: 94d13f342b98
[ 5436.917113] R10: ab52803b3d10 R11: 02c6 R12: 0001
[ 5436.919210] R13: 94d13f622140 R14: 94d104aa0db8 R15:
[ 5436.921401] FS: () GS:94d13f60()
knlGS:
[ 5436.923743] CS: 0010 DS: ES: CR0: 80050033
[ 5436.926299] CR2: 09b8 CR3: 38252000 CR4: 06f0
[ 5436.929093] Call Trace:
[ 5436.930818] process_one_work+0x1de/0x410
[ 5436.932818] worker_thread+0x32/0x410
[ 5436.935332] kthread+0x121/0x140
[ 5436.937309] ? process_one_work+0x410/0x410
[ 5436.939393] ? kthread_create_worker_on_cpu+0x70/0x70
[ 5436.941263] ret_from_fork+0x35/0x40
[ 5436.943060] Code: b8 00 00 00 a8 02 74 c8 31 f6 4c 89 e7 e8 43 0e ff ff eb
bc 66 83 bb 4c f7 ff ff 00 48 8b 83 58 ff ff ff 74 31 41 bc 01 00 00 00 <48> 8b
b8 b8 09 00 00 48 85 ff 74 05 e8 f9 9d 0d d3 0f b7 8b 4c
[ 5436.950188] RIP: cache_set_flush+0xf6/0x190 [bcache] RSP: ab52826bbe58
[ 5436.952796] CR2: 09b8
[ 5436.954567] ---[ end trace b771415397e98c3d ]---
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1796292
Title:
Tight timeout for bcache removal causes spurious failures
Status in curtin:
Fix Released
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Bionic:
Confirmed
Status in linux source package in Cosmic:
Confirmed
Status in linux source package in Disco:
Confirmed
Status in linux source package in Eoan:
Confirmed
Bug description:
I've had a number of deployment faults where curtin would report
Timeout exceeded for removal of /sys/fs/bcache/xxx when doing a mass-
deployment of 30+ nodes. Upon retrying the node would usually deploy
fine. Experimentally I've set the timeout ridiculously high, and it
seems I'm getting no faults with this. I'm wondering if the timeout
for removal is set too tight, or might need to be made configurable.
--- curtin/util.py~ 2018-05-18 18:40:48.0 +
+++ curtin/util.py 2018-10-05 09:40:06.807390367 +
@@ -263,7 +263,7 @@
return _subp(*args, **kwargs)
-def wait_for_removal(path, retries=[1, 3, 5, 7]):
+def wait_for_removal(path, retries=[1, 3, 5, 7, 1200, 1200]):
if not path:
raise ValueError('wait_for_removal: missing path parameter')
To manage notifications about this bug go to:
https://bugs.launchpad.net/curtin/+bug/1796292/+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 1796292] Re: Tight timeout for bcache removal causes spurious failures
The newer kernel went about 16 runs and then popped this:
[ 2137.810559] md: md0: resync done.
[ 2296.795633] INFO: task python3:11639 blocked for more than 120 seconds.
[ 2296.800320] Tainted: P O 4.15.0-55-generic
#60+lp1796292+1
[ 2296.805097] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this
message.
[ 2296.810071] python3 D0 11639 8301 0x
[ 2296.810075] Call Trace:
[ 2296.810100] __schedule+0x291/0x8a0
[ 2296.810102] ? __switch_to_asm+0x34/0x70
[ 2296.810103] ? __switch_to_asm+0x40/0x70
[ 2296.810105] schedule+0x2c/0x80
[ 2296.810118] bch_bucket_alloc+0xe5/0x370 [bcache]
[ 2296.810128] ? wait_woken+0x80/0x80
[ 2296.810132] __bch_bucket_alloc_set+0x10d/0x160 [bcache]
[ 2296.810137] bch_bucket_alloc_set+0x4e/0x70 [bcache]
[ 2296.810143] __uuid_write+0x59/0x170 [bcache]
[ 2296.810148] ? __write_super+0x137/0x170 [bcache]
[ 2296.810153] bch_uuid_write+0x16/0x40 [bcache]
[ 2296.810159] __cached_dev_store+0x1e5/0x8b0 [bcache]
[ 2296.810160] ? __switch_to_asm+0x34/0x70
[ 2296.810161] ? __switch_to_asm+0x40/0x70
[ 2296.810163] ? __switch_to_asm+0x34/0x70
[ 2296.810167] bch_cached_dev_store+0x46/0x110 [bcache]
[ 2296.810181] sysfs_kf_write+0x3c/0x50
[ 2296.810182] kernfs_fop_write+0x125/0x1a0
[ 2296.810185] __vfs_write+0x1b/0x40
[ 2296.810187] vfs_write+0xb1/0x1a0
[ 2296.810189] SyS_write+0x55/0xc0
[ 2296.810193] do_syscall_64+0x73/0x130
[ 2296.810194] entry_SYSCALL_64_after_hwframe+0x3d/0xa2
[ 2296.810196] RIP: 0033:0x7f8e80077154
[ 2296.810197] RSP: 002b:7fffc23855e8 EFLAGS: 0246 ORIG_RAX:
0001
[ 2296.810199] RAX: ffda RBX: 0008 RCX: 7f8e80077154
[ 2296.810200] RDX: 0008 RSI: 00d734b0 RDI: 0003
[ 2296.810201] RBP: 7f8e805726c0 R08: R09:
[ 2296.810202] R10: 0100 R11: 0246 R12: 0003
[ 2296.810203] R13: R14: 00d734b0 R15: 00aa4db0
[ 2417.627259] INFO: task python3:11639 blocked for more than 120 seconds.
[ 2417.632687] Tainted: P O 4.15.0-55-generic
#60+lp1796292+1
[ 2417.638276] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this
message.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1796292
Title:
Tight timeout for bcache removal causes spurious failures
Status in curtin:
Fix Released
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Bionic:
Confirmed
Status in linux source package in Cosmic:
Confirmed
Status in linux source package in Disco:
Confirmed
Status in linux source package in Eoan:
Confirmed
Bug description:
I've had a number of deployment faults where curtin would report
Timeout exceeded for removal of /sys/fs/bcache/xxx when doing a mass-
deployment of 30+ nodes. Upon retrying the node would usually deploy
fine. Experimentally I've set the timeout ridiculously high, and it
seems I'm getting no faults with this. I'm wondering if the timeout
for removal is set too tight, or might need to be made configurable.
--- curtin/util.py~ 2018-05-18 18:40:48.0 +
+++ curtin/util.py 2018-10-05 09:40:06.807390367 +
@@ -263,7 +263,7 @@
return _subp(*args, **kwargs)
-def wait_for_removal(path, retries=[1, 3, 5, 7]):
+def wait_for_removal(path, retries=[1, 3, 5, 7, 1200, 1200]):
if not path:
raise ValueError('wait_for_removal: missing path parameter')
To manage notifications about this bug go to:
https://bugs.launchpad.net/curtin/+bug/1796292/+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 1822108] Re: package linux-image-4.4.0-143-generic 4.4.0-143.169 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127
I just spent some time tracking this down for a datacenter tech trying to do a fresh install: linux-image-4.4.0-143-generic depends on linux-base (no min version) and needs linux-update-symlinks from linux-base linux-image-4.4.0-145-generic depends on linux-base >= 4.5ubuntu1~16.04.1 xenial main has linux-base 4.0ubuntu1 which doesn't have linux-update-symlinks xenial-updates xenial-security have 4.5ubuntu1~16.04.1 which does have linux-update-symlinks -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1822108 Title: package linux-image-4.4.0-143-generic 4.4.0-143.169 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127 Status in linux-signed package in Ubuntu: Confirmed Bug description: Error occurred when switching drivers for NVIDIA Corporation: G92[GeForce 9800 GT] to NVIDIA binary driver - version 340.107 from nvidia-340(proprietary, tested) ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-143-generic 4.4.0-143.169 ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11 Uname: Linux 4.8.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Thu Mar 28 09:47:57 2019 DuplicateSignature: package:linux-image-4.4.0-143-generic:4.4.0-143.169 Setting up linux-image-4.4.0-143-generic (4.4.0-143.169) ... /var/lib/dpkg/info/linux-image-4.4.0-143-generic.postinst: 50: /var/lib/dpkg/info/linux-image-4.4.0-143-generic.postinst: linux-update-symlinks: not found dpkg: error processing package linux-image-4.4.0-143-generic (--configure): subprocess installed post-installation script returned error exit status 127 ErrorMessage: subprocess installed post-installation script returned error exit status 127 InstallationDate: Installed on 2017-05-06 (691 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.19 SourcePackage: linux-signed Title: package linux-image-4.4.0-143-generic 4.4.0-143.169 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1822108/+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 1824050] [NEW] access.W_OK yields -1 EACCES (permission denied) on NFS mountpoints
Public bug reported:
When upgrading from xenial kernel (4.4.0-145) to linux-image-generic-
hwe-16.04 (4.15.0-47) I am no longer able to run an application that
checks it's data directory for write access/path traversal when that
directory is an NFS share. This works on 4.4 and 3.13 kernels that I
tested with but fails on 4.15. I'm using NFSv3 and have seen the
behavior with both a synology NAS as the nfs-server as well as my xenial
desktop as the nfs-server.
To reproduce:
0.) Boot test machine with kernel 4.15.0-47
1.) set up a NFS export on another machine (nfs-server)
/etc/exports:
/srv/nfstest 192.168.100.100(rw,sync,no_subtree_check)
2.) mount the NFS share on the test machine and give a non-root user
ownership of the mount, in my case I have a user: aptly, with
home=/var/lib/aptly, and I mounted the NFS at /var/lib/aptly/test.
aptly:aptly owns /var/lib/aptly/test.
/etc/fstab:
192.168.100.101:/srv/nfstest/var/lib/aptly/test nfs rw,mountvers=3
3.) attempt to call access.W_OK on the mount as the non-root user `strace
./testaccess.py`
stderr:
...
access("/var/lib/aptly/test", W_OK) = -1 EACCES (Permission denied)
...
stdout:
('Writeable:', False)
('user r,e,s', (5062, 5062, 5062))
('group r,e,s', (5062, 5062, 5062))
posix.stat_result(st_mode=16895, st_ino=101188113, st_dev=48, st_nlink=3,
st_uid=5062, st_gid=5062, st_size=4096, st_atime=1554858490,
st_mtime=1554858633, st_ctime=1554858633)
testaccess.py:
#!/usr/bin/python
import os
import sys
from pprint import pprint
directory = '/var/lib/aptly/test'
if __name__ == "__main__":
writeable = os.access(directory, os.W_OK)
print("Writeable:", writeable)
print("user r,e,s", os.getresuid())
print("group r,e,s", os.getresgid())
pprint(os.stat(directory))
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Incomplete
** Attachment added: "apport.linux-image-4.15.0-47-generic.j9ut204h.apport"
https://bugs.launchpad.net/bugs/1824050/+attachment/5254575/+files/apport.linux-image-4.15.0-47-generic.j9ut204h.apport
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1824050
Title:
access.W_OK yields -1 EACCES (permission denied) on NFS mountpoints
Status in linux package in Ubuntu:
Incomplete
Bug description:
When upgrading from xenial kernel (4.4.0-145) to linux-image-generic-
hwe-16.04 (4.15.0-47) I am no longer able to run an application that
checks it's data directory for write access/path traversal when that
directory is an NFS share. This works on 4.4 and 3.13 kernels that I
tested with but fails on 4.15. I'm using NFSv3 and have seen the
behavior with both a synology NAS as the nfs-server as well as my
xenial desktop as the nfs-server.
To reproduce:
0.) Boot test machine with kernel 4.15.0-47
1.) set up a NFS export on another machine (nfs-server)
/etc/exports:
/srv/nfstest 192.168.100.100(rw,sync,no_subtree_check)
2.) mount the NFS share on the test machine and give a non-root user
ownership of the mount, in my case I have a user: aptly, with
home=/var/lib/aptly, and I mounted the NFS at /var/lib/aptly/test.
aptly:aptly owns /var/lib/aptly/test.
/etc/fstab:
192.168.100.101:/srv/nfstest/var/lib/aptly/test nfs rw,mountvers=3
3.) attempt to call access.W_OK on the mount as the non-root user `strace
./testaccess.py`
stderr:
...
access("/var/lib/aptly/test", W_OK) = -1 EACCES (Permission denied)
...
stdout:
('Writeable:', False)
('user r,e,s', (5062, 5062, 5062))
('group r,e,s', (5062, 5062, 5062))
posix.stat_result(st_mode=16895, st_ino=101188113, st_dev=48, st_nlink=3,
st_uid=5062, st_gid=5062, st_size=4096, st_atime=1554858490,
st_mtime=1554858633, st_ctime=1554858633)
testaccess.py:
#!/usr/bin/python
import os
import sys
from pprint import pprint
directory = '/var/lib/aptly/test'
if __name__ == "__main__":
writeable = os.access(directory, os.W_OK)
print("Writeable:", writeable)
print("user r,e,s", os.getresuid())
print("group r,e,s", os.getresgid())
pprint(os.stat(directory))
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824050/+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 1824050] UdevDb.txt
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1824050/+attachment/5254594/+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/1824050
Title:
access.W_OK yields -1 EACCES (permission denied) on NFS mountpoints
Status in linux package in Ubuntu:
Confirmed
Bug description:
When upgrading from xenial kernel (4.4.0-145) to linux-image-generic-
hwe-16.04 (4.15.0-47) I am no longer able to run an application that
checks it's data directory for write access/path traversal when that
directory is an NFS share. This works on 4.4 and 3.13 kernels that I
tested with but fails on 4.15. I'm using NFSv3 and have seen the
behavior with both a synology NAS as the nfs-server as well as my
xenial desktop as the nfs-server.
To reproduce:
0.) Boot test machine with kernel 4.15.0-47
1.) set up a NFS export on another machine (nfs-server)
/etc/exports:
/srv/nfstest 192.168.100.100(rw,sync,no_subtree_check)
2.) mount the NFS share on the test machine and give a non-root user
ownership of the mount, in my case I have a user: aptly, with
home=/var/lib/aptly, and I mounted the NFS at /var/lib/aptly/test.
aptly:aptly owns /var/lib/aptly/test.
/etc/fstab:
192.168.100.101:/srv/nfstest/var/lib/aptly/test nfs rw,mountvers=3
3.) attempt to call access.W_OK on the mount as the non-root user `strace
./testaccess.py`
stderr:
...
access("/var/lib/aptly/test", W_OK) = -1 EACCES (Permission denied)
...
stdout:
('Writeable:', False)
('user r,e,s', (5062, 5062, 5062))
('group r,e,s', (5062, 5062, 5062))
posix.stat_result(st_mode=16895, st_ino=101188113, st_dev=48, st_nlink=3,
st_uid=5062, st_gid=5062, st_size=4096, st_atime=1554858490,
st_mtime=1554858633, st_ctime=1554858633)
testaccess.py:
#!/usr/bin/python
import os
import sys
from pprint import pprint
directory = '/var/lib/aptly/test'
if __name__ == "__main__":
writeable = os.access(directory, os.W_OK)
print("Writeable:", writeable)
print("user r,e,s", os.getresuid())
print("group r,e,s", os.getresgid())
pprint(os.stat(directory))
---
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Apr 9 18:53 seq
crw-rw 1 root audio 116, 33 Apr 9 18:53 timer
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
DistroRelease: Ubuntu 16.04
HibernationDevice: RESUME=/dev/mapper/pao03--aptly01--vg-swap_1
InstallationDate: Installed on 2019-04-09 (1 days ago)
InstallationMedia: Ubuntu-Server 16.04.5 LTS "Xenial Xerus" - Release amd64
(20180731)
IwConfig: Error: [Errno 2] No such file or directory
Lsusb: Error: command ['lsusb'] failed with exit code 1:
MachineType: VMware, Inc. VMware Virtual Platform
Package: linux (not installed)
PciMultimedia:
ProcFB: 0 svgadrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-47-generic
root=/dev/mapper/pao03--aptly01--vg-root ro
ProcVersionSignature: Ubuntu 4.15.0-47.50~16.04.1-generic 4.15.18
RelatedPackageVersions:
linux-restricted-modules-4.15.0-47-generic N/A
linux-backports-modules-4.15.0-47-generic N/A
linux-firmware 1.157.21
RfKill: Error: [Errno 2] No such file or directory
Tags: xenial xenial
Uname: Linux 4.15.0-47-generic x86_64
UnreportableReason: The report belongs to a package that is not installed.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
_MarkForUpload: False
dmi.bios.date: 07/28/2017
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: 6.00
dmi.board.name: 440BX Desktop Reference Platform
dmi.board.vendor: Intel Corporation
dmi.board.version: None
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias:
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/28/2017:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
dmi.product.name: VMware Virtual Platform
dmi.product.version: None
dmi.sys.vendor: VMware, Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824050/+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 1824050] Re: access.W_OK yields -1 EACCES (permission denied) on NFS mountpoints
apport information
** Tags added: apport-collected xenial
** Description changed:
When upgrading from xenial kernel (4.4.0-145) to linux-image-generic-
hwe-16.04 (4.15.0-47) I am no longer able to run an application that
checks it's data directory for write access/path traversal when that
directory is an NFS share. This works on 4.4 and 3.13 kernels that I
tested with but fails on 4.15. I'm using NFSv3 and have seen the
behavior with both a synology NAS as the nfs-server as well as my xenial
desktop as the nfs-server.
To reproduce:
0.) Boot test machine with kernel 4.15.0-47
1.) set up a NFS export on another machine (nfs-server)
/etc/exports:
/srv/nfstest 192.168.100.100(rw,sync,no_subtree_check)
2.) mount the NFS share on the test machine and give a non-root user
ownership of the mount, in my case I have a user: aptly, with
home=/var/lib/aptly, and I mounted the NFS at /var/lib/aptly/test.
aptly:aptly owns /var/lib/aptly/test.
/etc/fstab:
192.168.100.101:/srv/nfstest/var/lib/aptly/test nfs rw,mountvers=3
3.) attempt to call access.W_OK on the mount as the non-root user `strace
./testaccess.py`
stderr:
...
access("/var/lib/aptly/test", W_OK) = -1 EACCES (Permission denied)
...
stdout:
('Writeable:', False)
('user r,e,s', (5062, 5062, 5062))
('group r,e,s', (5062, 5062, 5062))
posix.stat_result(st_mode=16895, st_ino=101188113, st_dev=48, st_nlink=3,
st_uid=5062, st_gid=5062, st_size=4096, st_atime=1554858490,
st_mtime=1554858633, st_ctime=1554858633)
testaccess.py:
#!/usr/bin/python
import os
import sys
from pprint import pprint
directory = '/var/lib/aptly/test'
if __name__ == "__main__":
writeable = os.access(directory, os.W_OK)
print("Writeable:", writeable)
print("user r,e,s", os.getresuid())
print("group r,e,s", os.getresgid())
pprint(os.stat(directory))
+ ---
+ AlsaDevices:
+ total 0
+ crw-rw 1 root audio 116, 1 Apr 9 18:53 seq
+ crw-rw 1 root audio 116, 33 Apr 9 18:53 timer
+ AplayDevices: Error: [Errno 2] No such file or directory
+ ApportVersion: 2.20.1-0ubuntu2.18
+ Architecture: amd64
+ ArecordDevices: Error: [Errno 2] No such file or directory
+ AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
+ DistroRelease: Ubuntu 16.04
+ HibernationDevice: RESUME=/dev/mapper/pao03--aptly01--vg-swap_1
+ InstallationDate: Installed on 2019-04-09 (1 days ago)
+ InstallationMedia: Ubuntu-Server 16.04.5 LTS "Xenial Xerus" - Release amd64
(20180731)
+ IwConfig: Error: [Errno 2] No such file or directory
+ Lsusb: Error: command ['lsusb'] failed with exit code 1:
+ MachineType: VMware, Inc. VMware Virtual Platform
+ Package: linux (not installed)
+ PciMultimedia:
+
+ ProcFB: 0 svgadrmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-47-generic
root=/dev/mapper/pao03--aptly01--vg-root ro
+ ProcVersionSignature: Ubuntu 4.15.0-47.50~16.04.1-generic 4.15.18
+ RelatedPackageVersions:
+ linux-restricted-modules-4.15.0-47-generic N/A
+ linux-backports-modules-4.15.0-47-generic N/A
+ linux-firmware 1.157.21
+ RfKill: Error: [Errno 2] No such file or directory
+ Tags: xenial xenial
+ Uname: Linux 4.15.0-47-generic x86_64
+ UnreportableReason: The report belongs to a package that is not installed.
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups:
+
+ _MarkForUpload: False
+ dmi.bios.date: 07/28/2017
+ dmi.bios.vendor: Phoenix Technologies LTD
+ dmi.bios.version: 6.00
+ dmi.board.name: 440BX Desktop Reference Platform
+ dmi.board.vendor: Intel Corporation
+ dmi.board.version: None
+ dmi.chassis.asset.tag: No Asset Tag
+ dmi.chassis.type: 1
+ dmi.chassis.vendor: No Enclosure
+ dmi.chassis.version: N/A
+ dmi.modalias:
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/28/2017:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
+ dmi.product.name: VMware Virtual Platform
+ dmi.product.version: None
+ dmi.sys.vendor: VMware, Inc.
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1824050/+attachment/5254586/+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/1824050
Title:
access.W_OK yields -1 EACCES (permission denied) on NFS mountpoints
Status in linux package in Ubuntu:
Confirmed
Bug description:
When upgrading from xenial kernel (4.4.0-145) to linux-image-generic-
hwe-16.04 (4.15.0-47) I am no longer able to run an application that
checks it's data directory for write access/path traversal when that
directory is an NFS share. This works on 4.4 and 3.13 kernels that I
tested with but fails on 4.15. I'm using NFSv3 and have seen the
behavior with both a synology NAS as the nfs-server as well as my
xenial desktop as the nfs-
[Kernel-packages] [Bug 1824050] HookError_generic.txt
apport information
** Attachment added: "HookError_generic.txt"
https://bugs.launchpad.net/bugs/1824050/+attachment/5254588/+files/HookError_generic.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/1824050
Title:
access.W_OK yields -1 EACCES (permission denied) on NFS mountpoints
Status in linux package in Ubuntu:
Confirmed
Bug description:
When upgrading from xenial kernel (4.4.0-145) to linux-image-generic-
hwe-16.04 (4.15.0-47) I am no longer able to run an application that
checks it's data directory for write access/path traversal when that
directory is an NFS share. This works on 4.4 and 3.13 kernels that I
tested with but fails on 4.15. I'm using NFSv3 and have seen the
behavior with both a synology NAS as the nfs-server as well as my
xenial desktop as the nfs-server.
To reproduce:
0.) Boot test machine with kernel 4.15.0-47
1.) set up a NFS export on another machine (nfs-server)
/etc/exports:
/srv/nfstest 192.168.100.100(rw,sync,no_subtree_check)
2.) mount the NFS share on the test machine and give a non-root user
ownership of the mount, in my case I have a user: aptly, with
home=/var/lib/aptly, and I mounted the NFS at /var/lib/aptly/test.
aptly:aptly owns /var/lib/aptly/test.
/etc/fstab:
192.168.100.101:/srv/nfstest/var/lib/aptly/test nfs rw,mountvers=3
3.) attempt to call access.W_OK on the mount as the non-root user `strace
./testaccess.py`
stderr:
...
access("/var/lib/aptly/test", W_OK) = -1 EACCES (Permission denied)
...
stdout:
('Writeable:', False)
('user r,e,s', (5062, 5062, 5062))
('group r,e,s', (5062, 5062, 5062))
posix.stat_result(st_mode=16895, st_ino=101188113, st_dev=48, st_nlink=3,
st_uid=5062, st_gid=5062, st_size=4096, st_atime=1554858490,
st_mtime=1554858633, st_ctime=1554858633)
testaccess.py:
#!/usr/bin/python
import os
import sys
from pprint import pprint
directory = '/var/lib/aptly/test'
if __name__ == "__main__":
writeable = os.access(directory, os.W_OK)
print("Writeable:", writeable)
print("user r,e,s", os.getresuid())
print("group r,e,s", os.getresgid())
pprint(os.stat(directory))
---
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Apr 9 18:53 seq
crw-rw 1 root audio 116, 33 Apr 9 18:53 timer
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
DistroRelease: Ubuntu 16.04
HibernationDevice: RESUME=/dev/mapper/pao03--aptly01--vg-swap_1
InstallationDate: Installed on 2019-04-09 (1 days ago)
InstallationMedia: Ubuntu-Server 16.04.5 LTS "Xenial Xerus" - Release amd64
(20180731)
IwConfig: Error: [Errno 2] No such file or directory
Lsusb: Error: command ['lsusb'] failed with exit code 1:
MachineType: VMware, Inc. VMware Virtual Platform
Package: linux (not installed)
PciMultimedia:
ProcFB: 0 svgadrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-47-generic
root=/dev/mapper/pao03--aptly01--vg-root ro
ProcVersionSignature: Ubuntu 4.15.0-47.50~16.04.1-generic 4.15.18
RelatedPackageVersions:
linux-restricted-modules-4.15.0-47-generic N/A
linux-backports-modules-4.15.0-47-generic N/A
linux-firmware 1.157.21
RfKill: Error: [Errno 2] No such file or directory
Tags: xenial xenial
Uname: Linux 4.15.0-47-generic x86_64
UnreportableReason: The report belongs to a package that is not installed.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
_MarkForUpload: False
dmi.bios.date: 07/28/2017
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: 6.00
dmi.board.name: 440BX Desktop Reference Platform
dmi.board.vendor: Intel Corporation
dmi.board.version: None
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias:
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/28/2017:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
dmi.product.name: VMware Virtual Platform
dmi.product.version: None
dmi.sys.vendor: VMware, Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824050/+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 1824050] Lspci.txt
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1824050/+attachment/5254589/+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/1824050
Title:
access.W_OK yields -1 EACCES (permission denied) on NFS mountpoints
Status in linux package in Ubuntu:
Confirmed
Bug description:
When upgrading from xenial kernel (4.4.0-145) to linux-image-generic-
hwe-16.04 (4.15.0-47) I am no longer able to run an application that
checks it's data directory for write access/path traversal when that
directory is an NFS share. This works on 4.4 and 3.13 kernels that I
tested with but fails on 4.15. I'm using NFSv3 and have seen the
behavior with both a synology NAS as the nfs-server as well as my
xenial desktop as the nfs-server.
To reproduce:
0.) Boot test machine with kernel 4.15.0-47
1.) set up a NFS export on another machine (nfs-server)
/etc/exports:
/srv/nfstest 192.168.100.100(rw,sync,no_subtree_check)
2.) mount the NFS share on the test machine and give a non-root user
ownership of the mount, in my case I have a user: aptly, with
home=/var/lib/aptly, and I mounted the NFS at /var/lib/aptly/test.
aptly:aptly owns /var/lib/aptly/test.
/etc/fstab:
192.168.100.101:/srv/nfstest/var/lib/aptly/test nfs rw,mountvers=3
3.) attempt to call access.W_OK on the mount as the non-root user `strace
./testaccess.py`
stderr:
...
access("/var/lib/aptly/test", W_OK) = -1 EACCES (Permission denied)
...
stdout:
('Writeable:', False)
('user r,e,s', (5062, 5062, 5062))
('group r,e,s', (5062, 5062, 5062))
posix.stat_result(st_mode=16895, st_ino=101188113, st_dev=48, st_nlink=3,
st_uid=5062, st_gid=5062, st_size=4096, st_atime=1554858490,
st_mtime=1554858633, st_ctime=1554858633)
testaccess.py:
#!/usr/bin/python
import os
import sys
from pprint import pprint
directory = '/var/lib/aptly/test'
if __name__ == "__main__":
writeable = os.access(directory, os.W_OK)
print("Writeable:", writeable)
print("user r,e,s", os.getresuid())
print("group r,e,s", os.getresgid())
pprint(os.stat(directory))
---
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Apr 9 18:53 seq
crw-rw 1 root audio 116, 33 Apr 9 18:53 timer
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
DistroRelease: Ubuntu 16.04
HibernationDevice: RESUME=/dev/mapper/pao03--aptly01--vg-swap_1
InstallationDate: Installed on 2019-04-09 (1 days ago)
InstallationMedia: Ubuntu-Server 16.04.5 LTS "Xenial Xerus" - Release amd64
(20180731)
IwConfig: Error: [Errno 2] No such file or directory
Lsusb: Error: command ['lsusb'] failed with exit code 1:
MachineType: VMware, Inc. VMware Virtual Platform
Package: linux (not installed)
PciMultimedia:
ProcFB: 0 svgadrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-47-generic
root=/dev/mapper/pao03--aptly01--vg-root ro
ProcVersionSignature: Ubuntu 4.15.0-47.50~16.04.1-generic 4.15.18
RelatedPackageVersions:
linux-restricted-modules-4.15.0-47-generic N/A
linux-backports-modules-4.15.0-47-generic N/A
linux-firmware 1.157.21
RfKill: Error: [Errno 2] No such file or directory
Tags: xenial xenial
Uname: Linux 4.15.0-47-generic x86_64
UnreportableReason: The report belongs to a package that is not installed.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
_MarkForUpload: False
dmi.bios.date: 07/28/2017
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: 6.00
dmi.board.name: 440BX Desktop Reference Platform
dmi.board.vendor: Intel Corporation
dmi.board.version: None
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias:
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/28/2017:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
dmi.product.name: VMware Virtual Platform
dmi.product.version: None
dmi.sys.vendor: VMware, Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824050/+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 1824050] ProcEnviron.txt
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1824050/+attachment/5254591/+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/1824050
Title:
access.W_OK yields -1 EACCES (permission denied) on NFS mountpoints
Status in linux package in Ubuntu:
Confirmed
Bug description:
When upgrading from xenial kernel (4.4.0-145) to linux-image-generic-
hwe-16.04 (4.15.0-47) I am no longer able to run an application that
checks it's data directory for write access/path traversal when that
directory is an NFS share. This works on 4.4 and 3.13 kernels that I
tested with but fails on 4.15. I'm using NFSv3 and have seen the
behavior with both a synology NAS as the nfs-server as well as my
xenial desktop as the nfs-server.
To reproduce:
0.) Boot test machine with kernel 4.15.0-47
1.) set up a NFS export on another machine (nfs-server)
/etc/exports:
/srv/nfstest 192.168.100.100(rw,sync,no_subtree_check)
2.) mount the NFS share on the test machine and give a non-root user
ownership of the mount, in my case I have a user: aptly, with
home=/var/lib/aptly, and I mounted the NFS at /var/lib/aptly/test.
aptly:aptly owns /var/lib/aptly/test.
/etc/fstab:
192.168.100.101:/srv/nfstest/var/lib/aptly/test nfs rw,mountvers=3
3.) attempt to call access.W_OK on the mount as the non-root user `strace
./testaccess.py`
stderr:
...
access("/var/lib/aptly/test", W_OK) = -1 EACCES (Permission denied)
...
stdout:
('Writeable:', False)
('user r,e,s', (5062, 5062, 5062))
('group r,e,s', (5062, 5062, 5062))
posix.stat_result(st_mode=16895, st_ino=101188113, st_dev=48, st_nlink=3,
st_uid=5062, st_gid=5062, st_size=4096, st_atime=1554858490,
st_mtime=1554858633, st_ctime=1554858633)
testaccess.py:
#!/usr/bin/python
import os
import sys
from pprint import pprint
directory = '/var/lib/aptly/test'
if __name__ == "__main__":
writeable = os.access(directory, os.W_OK)
print("Writeable:", writeable)
print("user r,e,s", os.getresuid())
print("group r,e,s", os.getresgid())
pprint(os.stat(directory))
---
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Apr 9 18:53 seq
crw-rw 1 root audio 116, 33 Apr 9 18:53 timer
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
DistroRelease: Ubuntu 16.04
HibernationDevice: RESUME=/dev/mapper/pao03--aptly01--vg-swap_1
InstallationDate: Installed on 2019-04-09 (1 days ago)
InstallationMedia: Ubuntu-Server 16.04.5 LTS "Xenial Xerus" - Release amd64
(20180731)
IwConfig: Error: [Errno 2] No such file or directory
Lsusb: Error: command ['lsusb'] failed with exit code 1:
MachineType: VMware, Inc. VMware Virtual Platform
Package: linux (not installed)
PciMultimedia:
ProcFB: 0 svgadrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-47-generic
root=/dev/mapper/pao03--aptly01--vg-root ro
ProcVersionSignature: Ubuntu 4.15.0-47.50~16.04.1-generic 4.15.18
RelatedPackageVersions:
linux-restricted-modules-4.15.0-47-generic N/A
linux-backports-modules-4.15.0-47-generic N/A
linux-firmware 1.157.21
RfKill: Error: [Errno 2] No such file or directory
Tags: xenial xenial
Uname: Linux 4.15.0-47-generic x86_64
UnreportableReason: The report belongs to a package that is not installed.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
_MarkForUpload: False
dmi.bios.date: 07/28/2017
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: 6.00
dmi.board.name: 440BX Desktop Reference Platform
dmi.board.vendor: Intel Corporation
dmi.board.version: None
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias:
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/28/2017:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
dmi.product.name: VMware Virtual Platform
dmi.product.version: None
dmi.sys.vendor: VMware, Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824050/+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 1824050] WifiSyslog.txt
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1824050/+attachment/5254595/+files/WifiSyslog.txt
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1824050
Title:
access.W_OK yields -1 EACCES (permission denied) on NFS mountpoints
Status in linux package in Ubuntu:
Confirmed
Bug description:
When upgrading from xenial kernel (4.4.0-145) to linux-image-generic-
hwe-16.04 (4.15.0-47) I am no longer able to run an application that
checks it's data directory for write access/path traversal when that
directory is an NFS share. This works on 4.4 and 3.13 kernels that I
tested with but fails on 4.15. I'm using NFSv3 and have seen the
behavior with both a synology NAS as the nfs-server as well as my
xenial desktop as the nfs-server.
To reproduce:
0.) Boot test machine with kernel 4.15.0-47
1.) set up a NFS export on another machine (nfs-server)
/etc/exports:
/srv/nfstest 192.168.100.100(rw,sync,no_subtree_check)
2.) mount the NFS share on the test machine and give a non-root user
ownership of the mount, in my case I have a user: aptly, with
home=/var/lib/aptly, and I mounted the NFS at /var/lib/aptly/test.
aptly:aptly owns /var/lib/aptly/test.
/etc/fstab:
192.168.100.101:/srv/nfstest/var/lib/aptly/test nfs rw,mountvers=3
3.) attempt to call access.W_OK on the mount as the non-root user `strace
./testaccess.py`
stderr:
...
access("/var/lib/aptly/test", W_OK) = -1 EACCES (Permission denied)
...
stdout:
('Writeable:', False)
('user r,e,s', (5062, 5062, 5062))
('group r,e,s', (5062, 5062, 5062))
posix.stat_result(st_mode=16895, st_ino=101188113, st_dev=48, st_nlink=3,
st_uid=5062, st_gid=5062, st_size=4096, st_atime=1554858490,
st_mtime=1554858633, st_ctime=1554858633)
testaccess.py:
#!/usr/bin/python
import os
import sys
from pprint import pprint
directory = '/var/lib/aptly/test'
if __name__ == "__main__":
writeable = os.access(directory, os.W_OK)
print("Writeable:", writeable)
print("user r,e,s", os.getresuid())
print("group r,e,s", os.getresgid())
pprint(os.stat(directory))
---
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Apr 9 18:53 seq
crw-rw 1 root audio 116, 33 Apr 9 18:53 timer
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
DistroRelease: Ubuntu 16.04
HibernationDevice: RESUME=/dev/mapper/pao03--aptly01--vg-swap_1
InstallationDate: Installed on 2019-04-09 (1 days ago)
InstallationMedia: Ubuntu-Server 16.04.5 LTS "Xenial Xerus" - Release amd64
(20180731)
IwConfig: Error: [Errno 2] No such file or directory
Lsusb: Error: command ['lsusb'] failed with exit code 1:
MachineType: VMware, Inc. VMware Virtual Platform
Package: linux (not installed)
PciMultimedia:
ProcFB: 0 svgadrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-47-generic
root=/dev/mapper/pao03--aptly01--vg-root ro
ProcVersionSignature: Ubuntu 4.15.0-47.50~16.04.1-generic 4.15.18
RelatedPackageVersions:
linux-restricted-modules-4.15.0-47-generic N/A
linux-backports-modules-4.15.0-47-generic N/A
linux-firmware 1.157.21
RfKill: Error: [Errno 2] No such file or directory
Tags: xenial xenial
Uname: Linux 4.15.0-47-generic x86_64
UnreportableReason: The report belongs to a package that is not installed.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
_MarkForUpload: False
dmi.bios.date: 07/28/2017
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: 6.00
dmi.board.name: 440BX Desktop Reference Platform
dmi.board.vendor: Intel Corporation
dmi.board.version: None
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias:
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/28/2017:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
dmi.product.name: VMware Virtual Platform
dmi.product.version: None
dmi.sys.vendor: VMware, Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824050/+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 1824050] ProcInterrupts.txt
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1824050/+attachment/5254592/+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/1824050
Title:
access.W_OK yields -1 EACCES (permission denied) on NFS mountpoints
Status in linux package in Ubuntu:
Confirmed
Bug description:
When upgrading from xenial kernel (4.4.0-145) to linux-image-generic-
hwe-16.04 (4.15.0-47) I am no longer able to run an application that
checks it's data directory for write access/path traversal when that
directory is an NFS share. This works on 4.4 and 3.13 kernels that I
tested with but fails on 4.15. I'm using NFSv3 and have seen the
behavior with both a synology NAS as the nfs-server as well as my
xenial desktop as the nfs-server.
To reproduce:
0.) Boot test machine with kernel 4.15.0-47
1.) set up a NFS export on another machine (nfs-server)
/etc/exports:
/srv/nfstest 192.168.100.100(rw,sync,no_subtree_check)
2.) mount the NFS share on the test machine and give a non-root user
ownership of the mount, in my case I have a user: aptly, with
home=/var/lib/aptly, and I mounted the NFS at /var/lib/aptly/test.
aptly:aptly owns /var/lib/aptly/test.
/etc/fstab:
192.168.100.101:/srv/nfstest/var/lib/aptly/test nfs rw,mountvers=3
3.) attempt to call access.W_OK on the mount as the non-root user `strace
./testaccess.py`
stderr:
...
access("/var/lib/aptly/test", W_OK) = -1 EACCES (Permission denied)
...
stdout:
('Writeable:', False)
('user r,e,s', (5062, 5062, 5062))
('group r,e,s', (5062, 5062, 5062))
posix.stat_result(st_mode=16895, st_ino=101188113, st_dev=48, st_nlink=3,
st_uid=5062, st_gid=5062, st_size=4096, st_atime=1554858490,
st_mtime=1554858633, st_ctime=1554858633)
testaccess.py:
#!/usr/bin/python
import os
import sys
from pprint import pprint
directory = '/var/lib/aptly/test'
if __name__ == "__main__":
writeable = os.access(directory, os.W_OK)
print("Writeable:", writeable)
print("user r,e,s", os.getresuid())
print("group r,e,s", os.getresgid())
pprint(os.stat(directory))
---
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Apr 9 18:53 seq
crw-rw 1 root audio 116, 33 Apr 9 18:53 timer
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
DistroRelease: Ubuntu 16.04
HibernationDevice: RESUME=/dev/mapper/pao03--aptly01--vg-swap_1
InstallationDate: Installed on 2019-04-09 (1 days ago)
InstallationMedia: Ubuntu-Server 16.04.5 LTS "Xenial Xerus" - Release amd64
(20180731)
IwConfig: Error: [Errno 2] No such file or directory
Lsusb: Error: command ['lsusb'] failed with exit code 1:
MachineType: VMware, Inc. VMware Virtual Platform
Package: linux (not installed)
PciMultimedia:
ProcFB: 0 svgadrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-47-generic
root=/dev/mapper/pao03--aptly01--vg-root ro
ProcVersionSignature: Ubuntu 4.15.0-47.50~16.04.1-generic 4.15.18
RelatedPackageVersions:
linux-restricted-modules-4.15.0-47-generic N/A
linux-backports-modules-4.15.0-47-generic N/A
linux-firmware 1.157.21
RfKill: Error: [Errno 2] No such file or directory
Tags: xenial xenial
Uname: Linux 4.15.0-47-generic x86_64
UnreportableReason: The report belongs to a package that is not installed.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
_MarkForUpload: False
dmi.bios.date: 07/28/2017
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: 6.00
dmi.board.name: 440BX Desktop Reference Platform
dmi.board.vendor: Intel Corporation
dmi.board.version: None
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias:
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/28/2017:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
dmi.product.name: VMware Virtual Platform
dmi.product.version: None
dmi.sys.vendor: VMware, Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824050/+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 1824050] ProcModules.txt
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1824050/+attachment/5254593/+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/1824050
Title:
access.W_OK yields -1 EACCES (permission denied) on NFS mountpoints
Status in linux package in Ubuntu:
Confirmed
Bug description:
When upgrading from xenial kernel (4.4.0-145) to linux-image-generic-
hwe-16.04 (4.15.0-47) I am no longer able to run an application that
checks it's data directory for write access/path traversal when that
directory is an NFS share. This works on 4.4 and 3.13 kernels that I
tested with but fails on 4.15. I'm using NFSv3 and have seen the
behavior with both a synology NAS as the nfs-server as well as my
xenial desktop as the nfs-server.
To reproduce:
0.) Boot test machine with kernel 4.15.0-47
1.) set up a NFS export on another machine (nfs-server)
/etc/exports:
/srv/nfstest 192.168.100.100(rw,sync,no_subtree_check)
2.) mount the NFS share on the test machine and give a non-root user
ownership of the mount, in my case I have a user: aptly, with
home=/var/lib/aptly, and I mounted the NFS at /var/lib/aptly/test.
aptly:aptly owns /var/lib/aptly/test.
/etc/fstab:
192.168.100.101:/srv/nfstest/var/lib/aptly/test nfs rw,mountvers=3
3.) attempt to call access.W_OK on the mount as the non-root user `strace
./testaccess.py`
stderr:
...
access("/var/lib/aptly/test", W_OK) = -1 EACCES (Permission denied)
...
stdout:
('Writeable:', False)
('user r,e,s', (5062, 5062, 5062))
('group r,e,s', (5062, 5062, 5062))
posix.stat_result(st_mode=16895, st_ino=101188113, st_dev=48, st_nlink=3,
st_uid=5062, st_gid=5062, st_size=4096, st_atime=1554858490,
st_mtime=1554858633, st_ctime=1554858633)
testaccess.py:
#!/usr/bin/python
import os
import sys
from pprint import pprint
directory = '/var/lib/aptly/test'
if __name__ == "__main__":
writeable = os.access(directory, os.W_OK)
print("Writeable:", writeable)
print("user r,e,s", os.getresuid())
print("group r,e,s", os.getresgid())
pprint(os.stat(directory))
---
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Apr 9 18:53 seq
crw-rw 1 root audio 116, 33 Apr 9 18:53 timer
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
DistroRelease: Ubuntu 16.04
HibernationDevice: RESUME=/dev/mapper/pao03--aptly01--vg-swap_1
InstallationDate: Installed on 2019-04-09 (1 days ago)
InstallationMedia: Ubuntu-Server 16.04.5 LTS "Xenial Xerus" - Release amd64
(20180731)
IwConfig: Error: [Errno 2] No such file or directory
Lsusb: Error: command ['lsusb'] failed with exit code 1:
MachineType: VMware, Inc. VMware Virtual Platform
Package: linux (not installed)
PciMultimedia:
ProcFB: 0 svgadrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-47-generic
root=/dev/mapper/pao03--aptly01--vg-root ro
ProcVersionSignature: Ubuntu 4.15.0-47.50~16.04.1-generic 4.15.18
RelatedPackageVersions:
linux-restricted-modules-4.15.0-47-generic N/A
linux-backports-modules-4.15.0-47-generic N/A
linux-firmware 1.157.21
RfKill: Error: [Errno 2] No such file or directory
Tags: xenial xenial
Uname: Linux 4.15.0-47-generic x86_64
UnreportableReason: The report belongs to a package that is not installed.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
_MarkForUpload: False
dmi.bios.date: 07/28/2017
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: 6.00
dmi.board.name: 440BX Desktop Reference Platform
dmi.board.vendor: Intel Corporation
dmi.board.version: None
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias:
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/28/2017:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
dmi.product.name: VMware Virtual Platform
dmi.product.version: None
dmi.sys.vendor: VMware, Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824050/+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 1824050] ProcCpuinfoMinimal.txt
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1824050/+attachment/5254590/+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/1824050
Title:
access.W_OK yields -1 EACCES (permission denied) on NFS mountpoints
Status in linux package in Ubuntu:
Confirmed
Bug description:
When upgrading from xenial kernel (4.4.0-145) to linux-image-generic-
hwe-16.04 (4.15.0-47) I am no longer able to run an application that
checks it's data directory for write access/path traversal when that
directory is an NFS share. This works on 4.4 and 3.13 kernels that I
tested with but fails on 4.15. I'm using NFSv3 and have seen the
behavior with both a synology NAS as the nfs-server as well as my
xenial desktop as the nfs-server.
To reproduce:
0.) Boot test machine with kernel 4.15.0-47
1.) set up a NFS export on another machine (nfs-server)
/etc/exports:
/srv/nfstest 192.168.100.100(rw,sync,no_subtree_check)
2.) mount the NFS share on the test machine and give a non-root user
ownership of the mount, in my case I have a user: aptly, with
home=/var/lib/aptly, and I mounted the NFS at /var/lib/aptly/test.
aptly:aptly owns /var/lib/aptly/test.
/etc/fstab:
192.168.100.101:/srv/nfstest/var/lib/aptly/test nfs rw,mountvers=3
3.) attempt to call access.W_OK on the mount as the non-root user `strace
./testaccess.py`
stderr:
...
access("/var/lib/aptly/test", W_OK) = -1 EACCES (Permission denied)
...
stdout:
('Writeable:', False)
('user r,e,s', (5062, 5062, 5062))
('group r,e,s', (5062, 5062, 5062))
posix.stat_result(st_mode=16895, st_ino=101188113, st_dev=48, st_nlink=3,
st_uid=5062, st_gid=5062, st_size=4096, st_atime=1554858490,
st_mtime=1554858633, st_ctime=1554858633)
testaccess.py:
#!/usr/bin/python
import os
import sys
from pprint import pprint
directory = '/var/lib/aptly/test'
if __name__ == "__main__":
writeable = os.access(directory, os.W_OK)
print("Writeable:", writeable)
print("user r,e,s", os.getresuid())
print("group r,e,s", os.getresgid())
pprint(os.stat(directory))
---
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Apr 9 18:53 seq
crw-rw 1 root audio 116, 33 Apr 9 18:53 timer
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
DistroRelease: Ubuntu 16.04
HibernationDevice: RESUME=/dev/mapper/pao03--aptly01--vg-swap_1
InstallationDate: Installed on 2019-04-09 (1 days ago)
InstallationMedia: Ubuntu-Server 16.04.5 LTS "Xenial Xerus" - Release amd64
(20180731)
IwConfig: Error: [Errno 2] No such file or directory
Lsusb: Error: command ['lsusb'] failed with exit code 1:
MachineType: VMware, Inc. VMware Virtual Platform
Package: linux (not installed)
PciMultimedia:
ProcFB: 0 svgadrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-47-generic
root=/dev/mapper/pao03--aptly01--vg-root ro
ProcVersionSignature: Ubuntu 4.15.0-47.50~16.04.1-generic 4.15.18
RelatedPackageVersions:
linux-restricted-modules-4.15.0-47-generic N/A
linux-backports-modules-4.15.0-47-generic N/A
linux-firmware 1.157.21
RfKill: Error: [Errno 2] No such file or directory
Tags: xenial xenial
Uname: Linux 4.15.0-47-generic x86_64
UnreportableReason: The report belongs to a package that is not installed.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
_MarkForUpload: False
dmi.bios.date: 07/28/2017
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: 6.00
dmi.board.name: 440BX Desktop Reference Platform
dmi.board.vendor: Intel Corporation
dmi.board.version: None
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias:
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/28/2017:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
dmi.product.name: VMware Virtual Platform
dmi.product.version: None
dmi.sys.vendor: VMware, Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824050/+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 1824050] CurrentDmesg.txt
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1824050/+attachment/5254587/+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/1824050
Title:
access.W_OK yields -1 EACCES (permission denied) on NFS mountpoints
Status in linux package in Ubuntu:
Confirmed
Bug description:
When upgrading from xenial kernel (4.4.0-145) to linux-image-generic-
hwe-16.04 (4.15.0-47) I am no longer able to run an application that
checks it's data directory for write access/path traversal when that
directory is an NFS share. This works on 4.4 and 3.13 kernels that I
tested with but fails on 4.15. I'm using NFSv3 and have seen the
behavior with both a synology NAS as the nfs-server as well as my
xenial desktop as the nfs-server.
To reproduce:
0.) Boot test machine with kernel 4.15.0-47
1.) set up a NFS export on another machine (nfs-server)
/etc/exports:
/srv/nfstest 192.168.100.100(rw,sync,no_subtree_check)
2.) mount the NFS share on the test machine and give a non-root user
ownership of the mount, in my case I have a user: aptly, with
home=/var/lib/aptly, and I mounted the NFS at /var/lib/aptly/test.
aptly:aptly owns /var/lib/aptly/test.
/etc/fstab:
192.168.100.101:/srv/nfstest/var/lib/aptly/test nfs rw,mountvers=3
3.) attempt to call access.W_OK on the mount as the non-root user `strace
./testaccess.py`
stderr:
...
access("/var/lib/aptly/test", W_OK) = -1 EACCES (Permission denied)
...
stdout:
('Writeable:', False)
('user r,e,s', (5062, 5062, 5062))
('group r,e,s', (5062, 5062, 5062))
posix.stat_result(st_mode=16895, st_ino=101188113, st_dev=48, st_nlink=3,
st_uid=5062, st_gid=5062, st_size=4096, st_atime=1554858490,
st_mtime=1554858633, st_ctime=1554858633)
testaccess.py:
#!/usr/bin/python
import os
import sys
from pprint import pprint
directory = '/var/lib/aptly/test'
if __name__ == "__main__":
writeable = os.access(directory, os.W_OK)
print("Writeable:", writeable)
print("user r,e,s", os.getresuid())
print("group r,e,s", os.getresgid())
pprint(os.stat(directory))
---
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Apr 9 18:53 seq
crw-rw 1 root audio 116, 33 Apr 9 18:53 timer
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
DistroRelease: Ubuntu 16.04
HibernationDevice: RESUME=/dev/mapper/pao03--aptly01--vg-swap_1
InstallationDate: Installed on 2019-04-09 (1 days ago)
InstallationMedia: Ubuntu-Server 16.04.5 LTS "Xenial Xerus" - Release amd64
(20180731)
IwConfig: Error: [Errno 2] No such file or directory
Lsusb: Error: command ['lsusb'] failed with exit code 1:
MachineType: VMware, Inc. VMware Virtual Platform
Package: linux (not installed)
PciMultimedia:
ProcFB: 0 svgadrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-47-generic
root=/dev/mapper/pao03--aptly01--vg-root ro
ProcVersionSignature: Ubuntu 4.15.0-47.50~16.04.1-generic 4.15.18
RelatedPackageVersions:
linux-restricted-modules-4.15.0-47-generic N/A
linux-backports-modules-4.15.0-47-generic N/A
linux-firmware 1.157.21
RfKill: Error: [Errno 2] No such file or directory
Tags: xenial xenial
Uname: Linux 4.15.0-47-generic x86_64
UnreportableReason: The report belongs to a package that is not installed.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
_MarkForUpload: False
dmi.bios.date: 07/28/2017
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: 6.00
dmi.board.name: 440BX Desktop Reference Platform
dmi.board.vendor: Intel Corporation
dmi.board.version: None
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias:
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/28/2017:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
dmi.product.name: VMware Virtual Platform
dmi.product.version: None
dmi.sys.vendor: VMware, Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824050/+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 1824050] Re: access.W_OK yields -1 EACCES (permission denied) on NFS mountpoints
This linux-nfs list member found the origin of the problem:
https://marc.info/?l=linux-nfs&m=155480197614448&w=2
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1824050
Title:
access.W_OK yields -1 EACCES (permission denied) on NFS mountpoints
Status in linux package in Ubuntu:
Confirmed
Bug description:
When upgrading from xenial kernel (4.4.0-145) to linux-image-generic-
hwe-16.04 (4.15.0-47) I am no longer able to run an application that
checks it's data directory for write access/path traversal when that
directory is an NFS share. This works on 4.4 and 3.13 kernels that I
tested with but fails on 4.15. I'm using NFSv3 and have seen the
behavior with both a synology NAS as the nfs-server as well as my
xenial desktop as the nfs-server.
To reproduce:
0.) Boot test machine with kernel 4.15.0-47
1.) set up a NFS export on another machine (nfs-server)
/etc/exports:
/srv/nfstest 192.168.100.100(rw,sync,no_subtree_check)
2.) mount the NFS share on the test machine and give a non-root user
ownership of the mount, in my case I have a user: aptly, with
home=/var/lib/aptly, and I mounted the NFS at /var/lib/aptly/test.
aptly:aptly owns /var/lib/aptly/test.
/etc/fstab:
192.168.100.101:/srv/nfstest/var/lib/aptly/test nfs rw,mountvers=3
3.) attempt to call access.W_OK on the mount as the non-root user `strace
./testaccess.py`
stderr:
...
access("/var/lib/aptly/test", W_OK) = -1 EACCES (Permission denied)
...
stdout:
('Writeable:', False)
('user r,e,s', (5062, 5062, 5062))
('group r,e,s', (5062, 5062, 5062))
posix.stat_result(st_mode=16895, st_ino=101188113, st_dev=48, st_nlink=3,
st_uid=5062, st_gid=5062, st_size=4096, st_atime=1554858490,
st_mtime=1554858633, st_ctime=1554858633)
testaccess.py:
#!/usr/bin/python
import os
import sys
from pprint import pprint
directory = '/var/lib/aptly/test'
if __name__ == "__main__":
writeable = os.access(directory, os.W_OK)
print("Writeable:", writeable)
print("user r,e,s", os.getresuid())
print("group r,e,s", os.getresgid())
pprint(os.stat(directory))
---
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Apr 9 18:53 seq
crw-rw 1 root audio 116, 33 Apr 9 18:53 timer
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
DistroRelease: Ubuntu 16.04
HibernationDevice: RESUME=/dev/mapper/pao03--aptly01--vg-swap_1
InstallationDate: Installed on 2019-04-09 (1 days ago)
InstallationMedia: Ubuntu-Server 16.04.5 LTS "Xenial Xerus" - Release amd64
(20180731)
IwConfig: Error: [Errno 2] No such file or directory
Lsusb: Error: command ['lsusb'] failed with exit code 1:
MachineType: VMware, Inc. VMware Virtual Platform
Package: linux (not installed)
PciMultimedia:
ProcFB: 0 svgadrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-47-generic
root=/dev/mapper/pao03--aptly01--vg-root ro
ProcVersionSignature: Ubuntu 4.15.0-47.50~16.04.1-generic 4.15.18
RelatedPackageVersions:
linux-restricted-modules-4.15.0-47-generic N/A
linux-backports-modules-4.15.0-47-generic N/A
linux-firmware 1.157.21
RfKill: Error: [Errno 2] No such file or directory
Tags: xenial xenial
Uname: Linux 4.15.0-47-generic x86_64
UnreportableReason: The report belongs to a package that is not installed.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
_MarkForUpload: False
dmi.bios.date: 07/28/2017
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: 6.00
dmi.board.name: 440BX Desktop Reference Platform
dmi.board.vendor: Intel Corporation
dmi.board.version: None
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias:
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/28/2017:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
dmi.product.name: VMware Virtual Platform
dmi.product.version: None
dmi.sys.vendor: VMware, Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824050/+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 1809407] Re: [nvidia] Corrupted wallpaper after resuming from suspend
Just chiming in from Arch Linux, we got it too. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1809407 Title: [nvidia] Corrupted wallpaper after resuming from suspend Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-418 package in Ubuntu: Confirmed Bug description: Every other wake from sleep presents a corrupted screen with no unlock app. There's a dock and system menu on a black background with pixel garbage. Some personal information in the dock's large window thumbnails. Bitmap garbage flashes on the screen when interacting with anything. Only workaround is doing another sleep-wake cycle. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17 Uname: Linux 4.18.0-12-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..4b.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:4b:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.87 Tue Aug 21 12:33:05 PDT 2018 GCC version: gcc version 8.2.0 (Ubuntu 8.2.0-7ubuntu1) ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Dec 20 22:19:29 2018 DistUpgraded: 2018-12-01 23:07:50,385 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: cosmic DistroVariant: ubuntu DkmsStatus: nvidia, 390.87, 4.18.0-11-generic, x86_64: installed nvidia, 390.87, 4.18.0-12-generic, x86_64: installed virtualbox, 5.2.18, 4.18.0-11-generic, x86_64: installed virtualbox, 5.2.18, 4.18.0-12-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GP106 [GeForce GTX 1060 3GB] [10de:1c02] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GP106 [GeForce GTX 1060 3GB] [3842:6162] InstallationDate: Installed on 2018-10-28 (54 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Gigabyte Technology Co., Ltd. Default string ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-12-generic root=UUID=a8c839e7-c579-4699-999a-748f804ff9e0 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to cosmic on 2018-12-02 (18 days ago) dmi.bios.date: 06/08/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F24 dmi.board.asset.tag: Default string dmi.board.name: X99P-SLI-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF24:bd06/08/2017:svnGigabyteTechnologyCo.,Ltd.:pnDefaultstring:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX99P-SLI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: Default string dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1809407/+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 1784665] Re: bcache: bch_allocator_thread(): hung task timeout
I've verified that bionic-proposed linux-virtual kernel succeeds our test-case (curtin-nvme). I've 50 installs with no issue. ubuntu@ubuntu:~$ apt-cache policy linux-virtual linux-virtual: Installed: (none) Candidate: 4.15.0.59.61 Version table: 4.15.0.59.61 500 500 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 Packages 4.15.0.58.60 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 4.15.0.20.23 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages ubuntu@ubuntu:~$ lsb_release -rd Description:Ubuntu 18.04.2 LTS Release:18.04 ubuntu@ubuntu:~$ uname -r 4.15.0-59-generic ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1784665 Title: bcache: bch_allocator_thread(): hung task timeout Status in linux package in Ubuntu: Fix Committed Status in linux source package in Xenial: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Disco: Fix Committed Status in linux source package in Eoan: Fix Committed Bug description: [Impact] bcache_allocator() can call the following: bch_allocator_thread() -> bch_prio_write() -> bch_bucket_alloc() -> wait on &ca->set->bucket_wait But the wake up event on bucket_wait is supposed to come from bch_allocator_thread() itself causing a deadlock. [Test Case] This is a simple script that can easily trigger the deadlock condition: https://launchpadlibrarian.net/381282009/bcache-basic-repro.sh A better test case has been also provided in bug 1796292 (duplicate of this bug): https://bugs.launchpad.net/curtin/+bug/1796292/+attachment/5280353/+files/curtin-nvme.sh [Fix] Fix by making the call to bch_prio_write() non-blocking, so that bch_allocator_thread() never waits on itself. Moreover, make sure to wake up the garbage collector thread when bch_prio_write() is failing to allocate buckets to increase the chance of freeing up more buckets. In addition to that it would be safe to also import other upstream bcache fixes (all clean cherry picks): 7e865eba00a3df2dc8c4746173a8ca1c1c7f042e bcache: fix potential deadlock in cached_def_free() 80265d8dfd77792e133793cef44a21323aac2908 bcache: acquire bch_register_lock later in cached_dev_free() ce4c3e19e5201424357a0c82176633b32a98d2ec bcache: Replace bch_read_string_list() by __sysfs_match_string() ecb37ce9baac653cc09e2b631393dde3df82979f bcache: Move couple of functions to sysfs.c 04cbc21137bfa4d7b8771a5b14f3d6c9b2aee671 bcache: Move couple of string arrays to sysfs.c 5f2b18ec8e1643410a2369f06888951cdedea0bf bcache: Fix a compiler warning in bcache_device_init() 20d3a518713e394efa5a899c84574b4b79ec5098 bcache: Reduce the number of sparse complaints about lock imbalances 42361469ae84c851e40cb1f94c8c9a14cdd94039 bcache: Suppress more warnings about set-but-not-used variables f0d3814090ac77de94c42b7124c37ece23629197 bcache: Remove an unused variable 47344e330eabc1515cbe6061eb337100a3ab6d37 bcache: Fix kernel-doc warnings 9dfbdec7b7fea1ff1b7b5d5d12980dbc7dca46c7 bcache: Annotate switch fall-through 4a4e443835a43a79113cc237c472c0d268eb1e1c bcache: Add __printf annotation to __bch_check_keys() fd01991d5c20098c5c1ffc4dca6c821cc60a2f74 bcache: Fix indentation ca71df31661a0518ed58a1a59cf1993962153ebb bcache: fix using of loop variable in memory shrink f3641c3abd1da978ee969b0203b71b86ec1bfa93 bcache: fix error return value in memory shrink 688892b3bc05e25da94866e32210e5f503f16f69 bcache: fix incorrect sysfs output value of strip size 09a44ca2114737e0932257619c16a2b50c7807f1 bcache: use pr_info() to inform duplicated CACHE_SET_IO_DISABLE set c4dc2497d50d9c6fb16aa0d07b6a14f3b2adb1e0 bcache: fix high CPU occupancy during journal a728eacbbdd229d1d903e46261c57d5206f87a4a bcache: add journal statistic 616486ab52ab7f9739b066d958bdd20e65aefd74 bcache: fix writeback target calc on large devices 1f0ffa67349c56ea54c03ccfd1e073c990e7411e bcache: only set BCACHE_DEV_WB_RUNNING when cached device attached eb8cbb6df38f6e5124a3d5f1f8a3dbf519537c60 bcache: improve bcache_reboot() 9951379b0ca88c95876ad9778b9099e19a95d566 bcache: never writeback a discard operation [Regression Potential] The upstream fixes are all clean cherry picks from stable (most of them are small cleanups), so regression potential is minimal. The only special patch is "UBUNTU: SAUCE: bcache: fix deadlock in bcache_allocator()" that is addressing the main deadlock bug (that seems to be a mainline bug - not fixed yet). We should spend more time trying to reproduce this deadlock with a mainline kernel and p
[Kernel-packages] [Bug 1784665] Re: bcache: bch_allocator_thread(): hung task timeout
I've verified that disco-proposed linux-virtual kernel succeeds our test-case (curtin-nvme). I've 50 installs with no issue. root@ubuntu:~# apt-cache policy linux-virtual linux-virtual: Installed: 5.0.0.26.27 Candidate: 5.0.0.26.27 Version table: *** 5.0.0.26.27 500 500 http://archive.ubuntu.com/ubuntu disco-proposed/main amd64 Packages 100 /var/lib/dpkg/status 5.0.0.25.26 500 500 http://archive.ubuntu.com/ubuntu disco-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu disco-security/main amd64 Packages 5.0.0.13.14 500 500 http://archive.ubuntu.com/ubuntu disco/main amd64 Packages root@ubuntu:~# uname -r 5.0.0-26-generic root@ubuntu:~# lsb_release -rd Description:Ubuntu 19.04 Release:19.04 ** Tags removed: verification-needed-disco ** Tags added: verification-done-disco -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1784665 Title: bcache: bch_allocator_thread(): hung task timeout Status in linux package in Ubuntu: Fix Committed Status in linux source package in Xenial: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Disco: Fix Committed Status in linux source package in Eoan: Fix Committed Bug description: [Impact] bcache_allocator() can call the following: bch_allocator_thread() -> bch_prio_write() -> bch_bucket_alloc() -> wait on &ca->set->bucket_wait But the wake up event on bucket_wait is supposed to come from bch_allocator_thread() itself causing a deadlock. [Test Case] This is a simple script that can easily trigger the deadlock condition: https://launchpadlibrarian.net/381282009/bcache-basic-repro.sh A better test case has been also provided in bug 1796292 (duplicate of this bug): https://bugs.launchpad.net/curtin/+bug/1796292/+attachment/5280353/+files/curtin-nvme.sh [Fix] Fix by making the call to bch_prio_write() non-blocking, so that bch_allocator_thread() never waits on itself. Moreover, make sure to wake up the garbage collector thread when bch_prio_write() is failing to allocate buckets to increase the chance of freeing up more buckets. In addition to that it would be safe to also import other upstream bcache fixes (all clean cherry picks): 7e865eba00a3df2dc8c4746173a8ca1c1c7f042e bcache: fix potential deadlock in cached_def_free() 80265d8dfd77792e133793cef44a21323aac2908 bcache: acquire bch_register_lock later in cached_dev_free() ce4c3e19e5201424357a0c82176633b32a98d2ec bcache: Replace bch_read_string_list() by __sysfs_match_string() ecb37ce9baac653cc09e2b631393dde3df82979f bcache: Move couple of functions to sysfs.c 04cbc21137bfa4d7b8771a5b14f3d6c9b2aee671 bcache: Move couple of string arrays to sysfs.c 5f2b18ec8e1643410a2369f06888951cdedea0bf bcache: Fix a compiler warning in bcache_device_init() 20d3a518713e394efa5a899c84574b4b79ec5098 bcache: Reduce the number of sparse complaints about lock imbalances 42361469ae84c851e40cb1f94c8c9a14cdd94039 bcache: Suppress more warnings about set-but-not-used variables f0d3814090ac77de94c42b7124c37ece23629197 bcache: Remove an unused variable 47344e330eabc1515cbe6061eb337100a3ab6d37 bcache: Fix kernel-doc warnings 9dfbdec7b7fea1ff1b7b5d5d12980dbc7dca46c7 bcache: Annotate switch fall-through 4a4e443835a43a79113cc237c472c0d268eb1e1c bcache: Add __printf annotation to __bch_check_keys() fd01991d5c20098c5c1ffc4dca6c821cc60a2f74 bcache: Fix indentation ca71df31661a0518ed58a1a59cf1993962153ebb bcache: fix using of loop variable in memory shrink f3641c3abd1da978ee969b0203b71b86ec1bfa93 bcache: fix error return value in memory shrink 688892b3bc05e25da94866e32210e5f503f16f69 bcache: fix incorrect sysfs output value of strip size 09a44ca2114737e0932257619c16a2b50c7807f1 bcache: use pr_info() to inform duplicated CACHE_SET_IO_DISABLE set c4dc2497d50d9c6fb16aa0d07b6a14f3b2adb1e0 bcache: fix high CPU occupancy during journal a728eacbbdd229d1d903e46261c57d5206f87a4a bcache: add journal statistic 616486ab52ab7f9739b066d958bdd20e65aefd74 bcache: fix writeback target calc on large devices 1f0ffa67349c56ea54c03ccfd1e073c990e7411e bcache: only set BCACHE_DEV_WB_RUNNING when cached device attached eb8cbb6df38f6e5124a3d5f1f8a3dbf519537c60 bcache: improve bcache_reboot() 9951379b0ca88c95876ad9778b9099e19a95d566 bcache: never writeback a discard operation [Regression Potential] The upstream fixes are all clean cherry picks from stable (most of them are small cleanups), so regression potential is minimal. The only special patch is "UBUNTU: SAUCE: bcache: fix deadlock in bcache_allocator()" that is addressing the main deadlock bug (that seems to be a mainline bug - not fixed yet). We should spend more time trying to reproduce this deadlock with a mainli
[Kernel-packages] [Bug 1784665] Re: bcache: bch_allocator_thread(): hung task timeout
I've adjusted my bionic testing with the simpler configuration. I cannot reproduce the failure so far. I'll leave this running over night. I suspect there's something else going on baremetal that we can't reproduce in a VM. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1784665 Title: bcache: bch_allocator_thread(): hung task timeout Status in linux package in Ubuntu: Fix Committed Status in linux source package in Xenial: Fix Committed Status in linux source package in Bionic: New Status in linux source package in Disco: Fix Committed Status in linux source package in Eoan: Fix Committed Bug description: [Impact] bcache_allocator() can call the following: bch_allocator_thread() -> bch_prio_write() -> bch_bucket_alloc() -> wait on &ca->set->bucket_wait But the wake up event on bucket_wait is supposed to come from bch_allocator_thread() itself causing a deadlock. [Test Case] This is a simple script that can easily trigger the deadlock condition: https://launchpadlibrarian.net/381282009/bcache-basic-repro.sh A better test case has been also provided in bug 1796292 (duplicate of this bug): https://bugs.launchpad.net/curtin/+bug/1796292/+attachment/5280353/+files/curtin-nvme.sh [Fix] Fix by making the call to bch_prio_write() non-blocking, so that bch_allocator_thread() never waits on itself. Moreover, make sure to wake up the garbage collector thread when bch_prio_write() is failing to allocate buckets to increase the chance of freeing up more buckets. In addition to that it would be safe to also import other upstream bcache fixes (all clean cherry picks): 7e865eba00a3df2dc8c4746173a8ca1c1c7f042e bcache: fix potential deadlock in cached_def_free() 80265d8dfd77792e133793cef44a21323aac2908 bcache: acquire bch_register_lock later in cached_dev_free() ce4c3e19e5201424357a0c82176633b32a98d2ec bcache: Replace bch_read_string_list() by __sysfs_match_string() ecb37ce9baac653cc09e2b631393dde3df82979f bcache: Move couple of functions to sysfs.c 04cbc21137bfa4d7b8771a5b14f3d6c9b2aee671 bcache: Move couple of string arrays to sysfs.c 5f2b18ec8e1643410a2369f06888951cdedea0bf bcache: Fix a compiler warning in bcache_device_init() 20d3a518713e394efa5a899c84574b4b79ec5098 bcache: Reduce the number of sparse complaints about lock imbalances 42361469ae84c851e40cb1f94c8c9a14cdd94039 bcache: Suppress more warnings about set-but-not-used variables f0d3814090ac77de94c42b7124c37ece23629197 bcache: Remove an unused variable 47344e330eabc1515cbe6061eb337100a3ab6d37 bcache: Fix kernel-doc warnings 9dfbdec7b7fea1ff1b7b5d5d12980dbc7dca46c7 bcache: Annotate switch fall-through 4a4e443835a43a79113cc237c472c0d268eb1e1c bcache: Add __printf annotation to __bch_check_keys() fd01991d5c20098c5c1ffc4dca6c821cc60a2f74 bcache: Fix indentation ca71df31661a0518ed58a1a59cf1993962153ebb bcache: fix using of loop variable in memory shrink f3641c3abd1da978ee969b0203b71b86ec1bfa93 bcache: fix error return value in memory shrink 688892b3bc05e25da94866e32210e5f503f16f69 bcache: fix incorrect sysfs output value of strip size 09a44ca2114737e0932257619c16a2b50c7807f1 bcache: use pr_info() to inform duplicated CACHE_SET_IO_DISABLE set c4dc2497d50d9c6fb16aa0d07b6a14f3b2adb1e0 bcache: fix high CPU occupancy during journal a728eacbbdd229d1d903e46261c57d5206f87a4a bcache: add journal statistic 616486ab52ab7f9739b066d958bdd20e65aefd74 bcache: fix writeback target calc on large devices 1f0ffa67349c56ea54c03ccfd1e073c990e7411e bcache: only set BCACHE_DEV_WB_RUNNING when cached device attached eb8cbb6df38f6e5124a3d5f1f8a3dbf519537c60 bcache: improve bcache_reboot() 9951379b0ca88c95876ad9778b9099e19a95d566 bcache: never writeback a discard operation [Regression Potential] The upstream fixes are all clean cherry picks from stable (most of them are small cleanups), so regression potential is minimal. The only special patch is "UBUNTU: SAUCE: bcache: fix deadlock in bcache_allocator()" that is addressing the main deadlock bug (that seems to be a mainline bug - not fixed yet). We should spend more time trying to reproduce this deadlock with a mainline kernel and post the patch to the LKML for review / feedback. However, considering that this patch seems to fix/prevent the specific deadlock problem reported in this bug (tested on the affected platform) it can be considered safe to apply it. [Original Bug Report] $ cat /proc/version_signature Ubuntu 4.15.0-29.31-generic 4.15.18 $ lsb_release -rd Description: Ubuntu Cosmic Cuttlefish (development branch) Release: 18.10 $ apt-cache policy linux-image-`uname -r` linux-image-4.15.0-29-generic: Installed: 4.15.0-29.31 Candidate: 4.15.0-29.31 Version table: *** 4.15.0-29.31 500 500 http://
[Kernel-packages] [Bug 1784665] Re: bcache: bch_allocator_thread(): hung task timeout
Also, I had some confusion earlier about what kernel I was testing. apt-cache policy shows the package version 4.15.0.59.61, however that's the meta package, the actual kernel is the .66 one. # dpkg --list | grep linux-image ii linux-image-4.15.0-59-generic 4.15.0-59.66 amd64Signed kernel image generic ii linux-image-virtual 4.15.0.59.61 amd64Virtual Linux kernel image # cat /proc/version Linux version 4.15.0-59-generic (buildd@lgw01-amd64-035) (gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1)) #66-Ubuntu SMP Wed Aug 14 10:56:44 UTC 2019 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1784665 Title: bcache: bch_allocator_thread(): hung task timeout Status in linux package in Ubuntu: Fix Committed Status in linux source package in Xenial: Fix Committed Status in linux source package in Bionic: New Status in linux source package in Disco: Fix Committed Status in linux source package in Eoan: Fix Committed Bug description: [Impact] bcache_allocator() can call the following: bch_allocator_thread() -> bch_prio_write() -> bch_bucket_alloc() -> wait on &ca->set->bucket_wait But the wake up event on bucket_wait is supposed to come from bch_allocator_thread() itself causing a deadlock. [Test Case] This is a simple script that can easily trigger the deadlock condition: https://launchpadlibrarian.net/381282009/bcache-basic-repro.sh A better test case has been also provided in bug 1796292 (duplicate of this bug): https://bugs.launchpad.net/curtin/+bug/1796292/+attachment/5280353/+files/curtin-nvme.sh [Fix] Fix by making the call to bch_prio_write() non-blocking, so that bch_allocator_thread() never waits on itself. Moreover, make sure to wake up the garbage collector thread when bch_prio_write() is failing to allocate buckets to increase the chance of freeing up more buckets. In addition to that it would be safe to also import other upstream bcache fixes (all clean cherry picks): 7e865eba00a3df2dc8c4746173a8ca1c1c7f042e bcache: fix potential deadlock in cached_def_free() 80265d8dfd77792e133793cef44a21323aac2908 bcache: acquire bch_register_lock later in cached_dev_free() ce4c3e19e5201424357a0c82176633b32a98d2ec bcache: Replace bch_read_string_list() by __sysfs_match_string() ecb37ce9baac653cc09e2b631393dde3df82979f bcache: Move couple of functions to sysfs.c 04cbc21137bfa4d7b8771a5b14f3d6c9b2aee671 bcache: Move couple of string arrays to sysfs.c 5f2b18ec8e1643410a2369f06888951cdedea0bf bcache: Fix a compiler warning in bcache_device_init() 20d3a518713e394efa5a899c84574b4b79ec5098 bcache: Reduce the number of sparse complaints about lock imbalances 42361469ae84c851e40cb1f94c8c9a14cdd94039 bcache: Suppress more warnings about set-but-not-used variables f0d3814090ac77de94c42b7124c37ece23629197 bcache: Remove an unused variable 47344e330eabc1515cbe6061eb337100a3ab6d37 bcache: Fix kernel-doc warnings 9dfbdec7b7fea1ff1b7b5d5d12980dbc7dca46c7 bcache: Annotate switch fall-through 4a4e443835a43a79113cc237c472c0d268eb1e1c bcache: Add __printf annotation to __bch_check_keys() fd01991d5c20098c5c1ffc4dca6c821cc60a2f74 bcache: Fix indentation ca71df31661a0518ed58a1a59cf1993962153ebb bcache: fix using of loop variable in memory shrink f3641c3abd1da978ee969b0203b71b86ec1bfa93 bcache: fix error return value in memory shrink 688892b3bc05e25da94866e32210e5f503f16f69 bcache: fix incorrect sysfs output value of strip size 09a44ca2114737e0932257619c16a2b50c7807f1 bcache: use pr_info() to inform duplicated CACHE_SET_IO_DISABLE set c4dc2497d50d9c6fb16aa0d07b6a14f3b2adb1e0 bcache: fix high CPU occupancy during journal a728eacbbdd229d1d903e46261c57d5206f87a4a bcache: add journal statistic 616486ab52ab7f9739b066d958bdd20e65aefd74 bcache: fix writeback target calc on large devices 1f0ffa67349c56ea54c03ccfd1e073c990e7411e bcache: only set BCACHE_DEV_WB_RUNNING when cached device attached eb8cbb6df38f6e5124a3d5f1f8a3dbf519537c60 bcache: improve bcache_reboot() 9951379b0ca88c95876ad9778b9099e19a95d566 bcache: never writeback a discard operation [Regression Potential] The upstream fixes are all clean cherry picks from stable (most of them are small cleanups), so regression potential is minimal. The only special patch is "UBUNTU: SAUCE: bcache: fix deadlock in bcache_allocator()" that is addressing the main deadlock bug (that seems to be a mainline bug - not fixed yet). We should spend more time trying to reproduce this deadlock with a mainline kernel and post the patch to the LKML for review / feedback. However, considering that this patch seems to fix/prevent the specific deadlock problem reported in this bug (tested on the affected platform) it can be considered
[Kernel-packages] [Bug 1784665] Re: bcache: bch_allocator_thread(): hung task timeout
Finally, I did verify xenial proposed with our original test. I had over 100 installs with no issue. @Jason Have you had any runs on Xenial or Disco? (or do you not test those)? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1784665 Title: bcache: bch_allocator_thread(): hung task timeout Status in linux package in Ubuntu: Fix Committed Status in linux source package in Xenial: Fix Committed Status in linux source package in Bionic: New Status in linux source package in Disco: Fix Committed Status in linux source package in Eoan: Fix Committed Bug description: [Impact] bcache_allocator() can call the following: bch_allocator_thread() -> bch_prio_write() -> bch_bucket_alloc() -> wait on &ca->set->bucket_wait But the wake up event on bucket_wait is supposed to come from bch_allocator_thread() itself causing a deadlock. [Test Case] This is a simple script that can easily trigger the deadlock condition: https://launchpadlibrarian.net/381282009/bcache-basic-repro.sh A better test case has been also provided in bug 1796292 (duplicate of this bug): https://bugs.launchpad.net/curtin/+bug/1796292/+attachment/5280353/+files/curtin-nvme.sh [Fix] Fix by making the call to bch_prio_write() non-blocking, so that bch_allocator_thread() never waits on itself. Moreover, make sure to wake up the garbage collector thread when bch_prio_write() is failing to allocate buckets to increase the chance of freeing up more buckets. In addition to that it would be safe to also import other upstream bcache fixes (all clean cherry picks): 7e865eba00a3df2dc8c4746173a8ca1c1c7f042e bcache: fix potential deadlock in cached_def_free() 80265d8dfd77792e133793cef44a21323aac2908 bcache: acquire bch_register_lock later in cached_dev_free() ce4c3e19e5201424357a0c82176633b32a98d2ec bcache: Replace bch_read_string_list() by __sysfs_match_string() ecb37ce9baac653cc09e2b631393dde3df82979f bcache: Move couple of functions to sysfs.c 04cbc21137bfa4d7b8771a5b14f3d6c9b2aee671 bcache: Move couple of string arrays to sysfs.c 5f2b18ec8e1643410a2369f06888951cdedea0bf bcache: Fix a compiler warning in bcache_device_init() 20d3a518713e394efa5a899c84574b4b79ec5098 bcache: Reduce the number of sparse complaints about lock imbalances 42361469ae84c851e40cb1f94c8c9a14cdd94039 bcache: Suppress more warnings about set-but-not-used variables f0d3814090ac77de94c42b7124c37ece23629197 bcache: Remove an unused variable 47344e330eabc1515cbe6061eb337100a3ab6d37 bcache: Fix kernel-doc warnings 9dfbdec7b7fea1ff1b7b5d5d12980dbc7dca46c7 bcache: Annotate switch fall-through 4a4e443835a43a79113cc237c472c0d268eb1e1c bcache: Add __printf annotation to __bch_check_keys() fd01991d5c20098c5c1ffc4dca6c821cc60a2f74 bcache: Fix indentation ca71df31661a0518ed58a1a59cf1993962153ebb bcache: fix using of loop variable in memory shrink f3641c3abd1da978ee969b0203b71b86ec1bfa93 bcache: fix error return value in memory shrink 688892b3bc05e25da94866e32210e5f503f16f69 bcache: fix incorrect sysfs output value of strip size 09a44ca2114737e0932257619c16a2b50c7807f1 bcache: use pr_info() to inform duplicated CACHE_SET_IO_DISABLE set c4dc2497d50d9c6fb16aa0d07b6a14f3b2adb1e0 bcache: fix high CPU occupancy during journal a728eacbbdd229d1d903e46261c57d5206f87a4a bcache: add journal statistic 616486ab52ab7f9739b066d958bdd20e65aefd74 bcache: fix writeback target calc on large devices 1f0ffa67349c56ea54c03ccfd1e073c990e7411e bcache: only set BCACHE_DEV_WB_RUNNING when cached device attached eb8cbb6df38f6e5124a3d5f1f8a3dbf519537c60 bcache: improve bcache_reboot() 9951379b0ca88c95876ad9778b9099e19a95d566 bcache: never writeback a discard operation [Regression Potential] The upstream fixes are all clean cherry picks from stable (most of them are small cleanups), so regression potential is minimal. The only special patch is "UBUNTU: SAUCE: bcache: fix deadlock in bcache_allocator()" that is addressing the main deadlock bug (that seems to be a mainline bug - not fixed yet). We should spend more time trying to reproduce this deadlock with a mainline kernel and post the patch to the LKML for review / feedback. However, considering that this patch seems to fix/prevent the specific deadlock problem reported in this bug (tested on the affected platform) it can be considered safe to apply it. [Original Bug Report] $ cat /proc/version_signature Ubuntu 4.15.0-29.31-generic 4.15.18 $ lsb_release -rd Description: Ubuntu Cosmic Cuttlefish (development branch) Release: 18.10 $ apt-cache policy linux-image-`uname -r` linux-image-4.15.0-29-generic: Installed: 4.15.0-29.31 Candidate: 4.15.0-29.31 Version table: *** 4.15.0-29.31 500 500 http://archive.ubuntu.com/ubuntu cosmic/main amd64 P
