[Kernel-packages] [Bug 1726061] Re: Inspiron 5565 suspend issues after 17.10 upgrade
So it may be PNP0C0D:00 (lid switch), LNXPWRBN:00 (power button), or ACAD wakes your system up. Can you attach output of `cat /proc/acpi/wakeup` here? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1726061 Title: Inspiron 5565 suspend issues after 17.10 upgrade Status in linux package in Ubuntu: Confirmed Bug description: On my Inspiron 5565, 17.10 seems to work fairly well, unless I try to suspend. Suspend shuts off the display but doesn't seem to actually shut off the CPU -- fans still run. When I move the mouse the display comes back on but upon entering my password sometimes the session crashes and I am dumped back to the login screen; sometimes the session is still there but wifi is either disabled (all wifi-related menu items gone) or visible (with question mark) but non-functional. In any case once I have suspended I cannot shut down or reboot any way other than the hard way, by holding the power button for several seconds. Doesn't seem to matter whether I am using X or Wayland. Suspend works mostly fine if I choose the 4.10 kernel from GRUB... although I am prompted for login more times than necessary on resume. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-16-generic 4.13.0-16.19 ProcVersionSignature: Ubuntu 4.10.0-37.41-generic 4.10.17 Uname: Linux 4.10.0-37-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: aaron 2489 F pulseaudio /dev/snd/controlC1: aaron 2489 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Oct 22 12:22:13 2017 HibernationDevice: RESUME=UUID=3cc55560-1886-446c-8d60-15136ee14d32 InstallationDate: Installed on 2016-12-25 (301 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: Dell Inc. Inspiron 5565 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-37-generic.efi.signed root=UUID=c30eb880-24e4-41af-9203-feff0ab69c8c ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.10.0-37-generic N/A linux-backports-modules-4.10.0-37-generic N/A linux-firmware 1.169 SourcePackage: linux UpgradeStatus: Upgraded to artful on 2017-10-22 (0 days ago) dmi.bios.date: 07/20/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.2 dmi.board.name: 0RVKF9 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.0.2 dmi.modalias: dmi:bvnDellInc.:bvr1.0.2:bd07/20/2016:svnDellInc.:pnInspiron5565:pvr1.0.2:rvnDellInc.:rn0RVKF9:rvrA00:cvnDellInc.:ct10:cvr1.0.2: dmi.product.name: Inspiron 5565 dmi.product.version: 1.0.2 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1726061/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1732034] Re: Microphone headset isn't detected with Intel Skull Canyon NUC
Can you attach output of `cat /proc/asound/card0/codec\#0` *without* using dell-headset-multi? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1732034 Title: Microphone headset isn't detected with Intel Skull Canyon NUC Status in linux package in Ubuntu: Confirmed Bug description: I've also tested this machine with two separate USB Microphone adapters, and they do the same thing really. Super-low volume on the mic. I can only see a bit of a spike if I tap the mic hard. I can confirm the Headset/Microphone selection screen pops up when plugging the headset in. This workaround works after a reboot: https://communities.intel.com/thread/108361 > # Add to /etc/modprobe.d/alsa-base.conf > options snd-hda-intel model=dell-headset-multi I'm using this headset https://www.amazon.co.uk/HyperX-Stinger-Gaming- Headset- Mobile/dp/B01LRX2DSA/ref=sr_1_2?ie=UTF8&qid=1510612581&sr=8-2&ppw=fresh&keywords=hyperx+gaming+headphones ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-16-generic 4.13.0-16.19 [modified: boot/vmlinuz-4.13.0-16-generic] ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: andrewvos 1395 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Nov 13 22:30:33 2017 InstallationDate: Installed on 2017-11-10 (3 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed root=UUID=b7992a74-c44e-44cc-be68-f658972e448f ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-16-generic N/A linux-backports-modules-4.13.0-16-generic N/A linux-firmware 1.169 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/31/2017 dmi.bios.vendor: Intel Corp. dmi.bios.version: KYSKLi70.86A.0050.2017.0831.1924 dmi.board.name: NUC6i7KYB dmi.board.vendor: Intel Corporation dmi.board.version: H90766-406 dmi.chassis.type: 3 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnIntelCorp.:bvrKYSKLi70.86A.0050.2017.0831.1924:bd08/31/2017:svn:pn:pvr:rvnIntelCorporation:rnNUC6i7KYB:rvrH90766-406:cvnIntelCorporation:ct3:cvr1.0: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1732034/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1730746] Re: Processes hang on attempted access of WDC WD30-EZRX 3TB HDD
Please file an upstream bug at https://bugzilla.kernel.org/ Product: IO/Storage Component: SCSI -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1730746 Title: Processes hang on attempted access of WDC WD30-EZRX 3TB HDD Status in linux package in Ubuntu: Confirmed Status in linux source package in Artful: Confirmed Status in linux source package in Bionic: Confirmed Bug description: When booted under kernel 4.13.x, processes (such as parted, boot-info, gparted, etc) always hang when attempting to run due to a Western Digital Green WD30-EZRX 3TB HDD. Drive works as expected under kernel 4.10.x (even when all other things are the same about the system but only booted kernel is different). Full specs of the machine if useful: https://www.support.hp.com/id- en/document/c03277050 ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-16-generic 4.13.0-16.19 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 1781 F pulseaudio /dev/snd/controlC0: ubuntu 1781 F pulseaudio CasperVersion: 1.387 CurrentDesktop: ubuntu:GNOME Date: Tue Nov 7 20:00:57 2017 IwConfig: eno1 no wireless extensions. lono wireless extensions. LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: Hewlett-Packard HP Z420 Workstation ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/username.seed boot=casper quiet splash --- RelatedPackageVersions: linux-restricted-modules-4.13.0-16-generic N/A linux-backports-modules-4.13.0-16-generic N/A linux-firmware 1.169 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/17/2016 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: J61 v03.91 dmi.board.asset.tag: HP5012436 dmi.board.name: 1589 dmi.board.vendor: Hewlett-Packard dmi.board.version: 0.00 dmi.chassis.asset.tag: HP5012436 dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrJ61v03.91:bd10/17/2016:svnHewlett-Packard:pnHPZ420Workstation:pvr:rvnHewlett-Packard:rn1589:rvr0.00:cvnHewlett-Packard:ct6:cvr: dmi.product.family: 103C_53335X G=D dmi.product.name: HP Z420 Workstation dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1730746/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1730596] Comment bridged from LTC Bugzilla
--- Comment From heinz-werner_se...@de.ibm.com 2017-11-14 03:24 EDT---
Already verified for Zesty - see also comment #4
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1730596
Title:
s390/mm: fix write access check in gup_huge_pmd()
Status in Ubuntu on IBM z Systems:
Fix Committed
Status in linux package in Ubuntu:
Fix Committed
Status in linux source package in Xenial:
Fix Committed
Status in linux source package in Zesty:
Fix Committed
Status in linux source package in Artful:
Fix Committed
Status in linux source package in Bionic:
Fix Committed
Bug description:
== SRU Justification ==
The check for the _SEGMENT_ENTRY_PROTECT bit in gup_huge_pmd() is the
wrong way around. It must not be set for write==1, and not be checked for
write==0. Fix this similar to how it was fixed for ptes long time ago in
commit 25591b0 ("[S390] fix get_user_pages_fast").
One impact of this bug would be unnecessarily using the gup slow path for
write==0 on r/w mappings. A potentially more severe impact would be that
gup_huge_pmd() will succeed for write==1 on r/o mappings.
This bug is fixed by mainline commit ba385c0594, which is in mainline
as of v4.14-rc2. It was also cc'd to upstream stable. It has already
been accepted in upstream v4.13.y, so Artful and Bionic have the fix
via the 4.13.5 stable updates.
== Fix ==
commit ba385c0594e723d41790ecfb12c610e6f90c7785
Author: Gerald Schaefer
Date: Mon Sep 18 16:51:51 2017 +0200
s390/mm: fix write access check in gup_huge_pmd()
== Regression Potential ==
This patch is specific to s390. It has also been accepted by upstream
stable, so additional upstream review has been done.
Addl information
Problem: The check for the _SEGMENT_ENTRY_PROTECT bit in
gup_huge_pmd() is the wrong way around. It must not be set
for write==1, and not be checked for write==0. Allowing
write==1 with protection bit set, instead of breaking out
to the slow path, will result in a missing faultin_page()
to clear the protection bit (for valid writable mappings),
and the async I/O write operation will fail to write to
such a mapping.
Solution: Fix it by correctly checking the protection bit like it is
also done in gup_pte_range() and gup_huge_pud().
Reproduction: Async I/O workload on buffers that are mapped as transparent
hugepages.
Upstream-ID: ba385c0594e723d41790ecfb12c610e6f90c7785
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1730596/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1729010] Re: USB hub stops working after suspend(s?)
You were using the system from 15.10, did this issue occur in previous kernel versions? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1729010 Title: USB hub stops working after suspend(s?) Status in linux package in Ubuntu: Confirmed Bug description: On initial boot, my usb hub works fine, but after a (series of?) suspends, I stop being able to see devices that are plugged into it. journalctl output on plugging it in: Oct 31 07:08:36 spiny kernel: usb 1-1: new high-speed USB device number 21 using xhci_hcd Oct 31 07:08:36 spiny kernel: usb 1-1: New USB device found, idVendor=0409, idProduct=005a Oct 31 07:08:36 spiny kernel: usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0 Oct 31 07:08:36 spiny kernel: hub 1-1:1.0: USB hub found Oct 31 07:08:36 spiny kernel: hub 1-1:1.0: 4 ports detected Oct 31 07:08:36 spiny kernel: [UFW BLOCK] IN=wlp3s0 OUT= MAC= SRC=fe80::::a299:9bff:fe17:9047 DST=ff02:::::::0001 LEN=64 TC=0 HOPLIMIT=1 FLOWLBL=32325 PROTO=UDP SPT=8612 DPT=8612 LEN=24 Oct 31 07:08:36 spiny kernel: usb 1-1.1: new high-speed USB device number 22 using xhci_hcd Oct 31 07:08:36 spiny kernel: usb 1-1.1: New USB device found, idVendor=0b95, idProduct=772a Oct 31 07:08:36 spiny kernel: usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Oct 31 07:08:36 spiny kernel: usb 1-1.1: Product: AX88x72A Oct 31 07:08:36 spiny kernel: usb 1-1.1: Manufacturer: ASIX Elec. Corp. Oct 31 07:08:36 spiny kernel: usb 1-1.1: SerialNumber: 47EDE2 Oct 31 07:08:37 spiny kernel: asix 1-1.1:1.0 eth0: register 'asix' at usb-:00:14.0-1.1, ASIX AX88772 USB 2.0 Ethernet, 00:50:b6:47:ed:e2 Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.0438] manager: (eth0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/7) Oct 31 07:08:37 spiny mtp-probe[13207]: checking bus 1, device 22: "/sys/devices/pci:00/:00:14.0/usb1/1-1/1-1.1" Oct 31 07:08:37 spiny mtp-probe[13207]: bus: 1, device: 22 was not an MTP device Oct 31 07:08:37 spiny systemd-udevd[13206]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable. Oct 31 07:08:37 spiny kernel: asix 1-1.1:1.0 enx0050b647ede2: renamed from eth0 Oct 31 07:08:37 spiny pkexec[13215]: pam_unix(polkit-1:session): session opened for user root by (uid=1000) Oct 31 07:08:37 spiny pkexec[13215]: jbarnett: Executing command [USER=root] [TTY=unknown] [CWD=/home/jbarnett] [COMMAND=/usr/lib/gnome-settings-daemon/gsd-backlight-helper --set-brightness 31] Oct 31 07:08:37 spiny pkexec[13214]: gdm: Error executing command as another user: Not authorized [USER=root] [TTY=unknown] [CWD=/var/lib/gdm3] [COMMAND=/usr/lib/gnome-settings-daemon/gsd-backlight-helper --set-brightness 48] Oct 31 07:08:37 spiny org.gnome.SettingsDaemon.Power.desktop[2273]: Error executing command as another user: Not authorized Oct 31 07:08:37 spiny org.gnome.SettingsDaemon.Power.desktop[2273]: This incident has been reported. Oct 31 07:08:37 spiny systemd-networkd[1119]: eth0: Renamed to enx0050b647ede2 Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.1066] device (eth0): interface index 10 renamed iface from 'eth0' to 'enx0050b647ede2' Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.1214] devices added (path: /sys/devices/pci:00/:00:14.0/usb1/1-1/1-1.1/1-1.1:1.0/net/enx0050b647ede2, iface: enx0050b647ede2) Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.1214] device added (path: /sys/devices/pci:00/:00:14.0/usb1/1-1/1-1.1/1-1.1:1.0/net/enx0050b647ede2, iface: enx0050b647ede2): no ifupdown configuration found. Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.1217] device (enx0050b647ede2): state change: unmanaged -> unavailable (reason 'managed', internal state 'external') Oct 31 07:08:37 spiny kernel: IPv6: ADDRCONF(NETDEV_UP): enx0050b647ede2: link is not ready Oct 31 07:08:37 spiny kernel: IPv6: ADDRCONF(NETDEV_UP): enx0050b647ede2: link is not ready Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.1274] keyfile: add connection in-memory (9365f42f-9dd9-3bdc-bbad-e7062efcaf7c,"Wired connection 4") Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.1284] settings: (enx0050b647ede2): created default wired connection 'Wired connection 4' Oct 31 07:08:37 spiny systemd[1]: Starting systemd-resolved-update-resolvconf.service... Oct 31 07:08:37 spiny systemd[1]: Started systemd-resolved-update-resolvconf.service. Oct 31 07:08:37 spiny kernel: usb 1-1.2: new full-speed USB device number 23 using xhci_hcd Oct 31 07:08:37 spiny kernel: usb 1-1.2: New USB device found, idVendor=0d8c, idProduct=0105 Oct 31 07:08:37 spiny kernel: usb 1-1.2: New USB device strings: Mfr=3, Product=1, SerialNumber=0 Oct 31 07:08:37
[Kernel-packages] [Bug 1594023] Re: Poweroff or reboot hangs. Laptop won't shutdown. 16.04
I had the same issue after installing fresh Ubunut 17.04 on laptop Dell Inspiron, after installing kernel 4.9 ,the issue has been solved. http://ubuntuhandbook.org/index.php/2016/12/install-linux-kernel-4-9 -ubuntu-linux-mint/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1594023 Title: Poweroff or reboot hangs. Laptop won't shutdown. 16.04 Status in linux package in Ubuntu: Confirmed Bug description: This is about a fresh Ubuntu 16.04 install on a new laptop (asus x540sa). After pressing the shutdown button in the start menu; the shutdown procedure starts and in the final splash screen the system just hangs. Tried a second time by pressing Esc once the splash screen showed up and I saw that it reaches the line "Reached target shutdown" and just stops there, no matter how long I leave it there the machine won't turn off. I also tried a Kubuntu 16.04 fresh install on the same machine and it hanged too at the final splash screen where the pulsating logo stopped. Then I tried with Esc only to see the exact same line in the end. The issue seems to affect lately quite many users as shown by the google results of the past month / week or so. I have also tried shutting down from the console with shutdown -and all the parameters after that suggested online- and sudo poweroff but unfortunately they didn't do the trick. The exact same situation occurred. Unmounting the swap as suggested online doesn't work. Also rebooting the system is not working either due to the same issue. So right now the only way for me to poweroff the machine is to press the power button on the keyboard continuously. Reproducible: Always Steps to Reproduce: 1.Install OS 2.Do something, anything or nothing 3.Try to shutdown or reboot Actual Results: The computer is not shutting down: "Reached target shutdown" and hangs there. Expected Results: Powering off the machine. For what it's worth, closing the lid won't suspend the system, but using the menu buttons for suspension will do it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1594023/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1727331] Comment bridged from LTC Bugzilla
--- Comment From sthou...@in.ibm.com 2017-11-14 03:50 EDT--- please help submitting an SRU request for inclusion in 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/1727331 Title: NMI watchdog: BUG: soft lockup on Guest upon boot (KVM) Status in The Ubuntu-power-systems project: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Bug description: == SRU Justification == Xenial does not include the patch: "KVM: PPC: Book3S: Treat VTB as a per-subcore register, not per-thread", which is commit 88b02cf97bb7 in the upstream Linux kernel repository. The symptom of not having this patch is that guests running with threads > 1 (that is, in SMT2, SMT4 or SMT8 mode) can give spurious soft-lockup messages when they are not in fact locked up, if the guest kernel uses the VTB (virtual timebase) register in its softlockup detector code. IBM provided this backport of commit 88b02cf97bb7. == Fix == commit 88b02cf97bb7e742db3e31671d54177e3e19fd89 Author: Paul Mackerras Date: Thu Sep 15 13:42:52 2016 +1000 KVM: PPC: Book3S: Treat VTB as a per-subcore register, not per- thread == Regression Potential == This patch is specific to powerpc. It was provided by and tested by IBM. Environment: Host OS: Ubuntu 16.04 (4.4.0-97-generic) Guest OS: Ubuntu 16.04 Host is running NovaLink and GPFS. Guest gets filesystem from gpfs cluster. Issue: While booting the guest OS went into recovery. dmesg shows CPU soft lockup. This issue is easily recreatable when multiple VMs (about 10) are being started simultaneously. ... - Paul Mackerras - 2017-10-24 00:42:25 == Looking at kernel sources: The Ubuntu host kernel (4.4.0-97) does not include the patch "KVM: PPC: Book3S: Treat VTB as a per-subcore register, not per-thread", which is commit 88b02cf97bb7 in the upstream Linux kernel repository. The symptom of not having this patch is that guests running with threads > 1 (that is, in SMT2, SMT4 or SMT8 mode) can give spurious soft-lockup messages when they are not in fact locked up, if the guest kernel uses the VTB (virtual timebase) register in its softlockup detector code. This is a backport of commit 88b02cf97bb7 from the upstream Linux kernel repository to the Ubuntu 4.4 kernel. It is the fix for the problem of seeing spurious soft lockup messages in guests running in an SMT mode greater than 1. These tests were run on a system with 20 cores. Each VM had 1 core and 4 threads (SMT=4). It is working very well with this patch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1727331/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1651635] Re: XPS 13 9360 trackpad locks into scroll mode
@James - Likely it had nothing to do with the firmware update. Have a look at the linked Ubuntu thread... many of us have been through exactly what you're going through now. Make a change, seems to help, 2 days later it's back. Please try some of the suggested solutions we've listed here: firm pressure on various parts of the lower case seems to resolve it for days at a time, for some people. As far as we can tell, there is no software or firmware fix possible for this 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/1651635 Title: XPS 13 9360 trackpad locks into scroll mode Status in Dell Sputnik: Confirmed Status in Linux: Unknown Status in linux package in Ubuntu: New Bug description: Hello, I'm running Linux on a Dell XPS 13 (9360) laptop. I find that upwards of 10 times per day, my trackpad gets stuck in "scrolling" mode. Moving the trackpad won't move the X windows pointer, but will send scrolling events to the foreground window. When the trackpad is locked in this mode, the touchscreen will still let me move the mouse cursor, as will an external mouse. On Ubuntu 16.04 freshly restored from the Dell recovery image, I find that it's often difficult to get the trackpad to recover. I do find that the issue happens less frequently on Dell's build of Ubuntu 16.04 than on other linux distributions and versions, but it still happens enough to significantly impact my ability to do productive work. The issue does not occur when running Windows 10 on the same device. I suspect that the issue may be related to palm detection or misdetecting the user's palm as a gesture to enable scrolling mode, but have no proof for this. It seems that I'm often able to reproduce the issue by brushing the trackpad with my right palm. On Ubuntu 16.10, with the latest shipped 4.8 kernel (Linux szx 4.8.0-30-generic #32-Ubuntu SMP Fri Dec 2 03:43:27 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux), with the extra xinput configuration below, I am able to get the trackpad to recover, simply by clicking the trackpad: /usr/share/X11/xorg.conf.d/99-libinput.conf: Section "InputClass" Identifier "libinput touchpad catchall" Driver "libinput" MatchIsTouchpad "on" MatchDevicePath "/dev/input/event*" Option "Tapping" "True" Option "DisableWhileTyping" "True" Option "NaturalScrolling" "False" Option "AccelProfile" "adaptive" Option "AccelSpeed" "0.05" Option "MiddleEmulation" "True" Option "ScrollMethod" "twofinger" # Option "ClickMethod" "clickfinger" Option "ClickMethod" "buttonareas" EndSection In my experience, the problem manifests using both the Xorg synaptics driver and the Xorg libinput driver. root@szx:/etc/modprobe.d# xinput list ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ Logitech M570 id=10 [slave pointer (2)] ⎜ ↳ DLL075B:01 06CB:76AF Touchpad id=13 [slave pointer (2)] ⎜ ↳ ELAN Touchscreenid=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Buttonid=8[slave keyboard (3)] ↳ Sleep Buttonid=9[slave keyboard (3)] ↳ Integrated_Webcam_HDid=12 [slave keyboard (3)] ↳ Intel Virtual Button driver id=14 [slave keyboard (3)] ↳ Intel HID eventsid=15 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=16 [slave keyboard (3)] ↳ Dell WMI hotkeysid=17 [slave keyboard (3)] root@szx:/etc/modprobe.d# To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1651635/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1651635] Re: XPS 13 9360 trackpad locks into scroll mode
whoops, I meant the linked kernel.org thread. :) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1651635 Title: XPS 13 9360 trackpad locks into scroll mode Status in Dell Sputnik: Confirmed Status in Linux: Unknown Status in linux package in Ubuntu: New Bug description: Hello, I'm running Linux on a Dell XPS 13 (9360) laptop. I find that upwards of 10 times per day, my trackpad gets stuck in "scrolling" mode. Moving the trackpad won't move the X windows pointer, but will send scrolling events to the foreground window. When the trackpad is locked in this mode, the touchscreen will still let me move the mouse cursor, as will an external mouse. On Ubuntu 16.04 freshly restored from the Dell recovery image, I find that it's often difficult to get the trackpad to recover. I do find that the issue happens less frequently on Dell's build of Ubuntu 16.04 than on other linux distributions and versions, but it still happens enough to significantly impact my ability to do productive work. The issue does not occur when running Windows 10 on the same device. I suspect that the issue may be related to palm detection or misdetecting the user's palm as a gesture to enable scrolling mode, but have no proof for this. It seems that I'm often able to reproduce the issue by brushing the trackpad with my right palm. On Ubuntu 16.10, with the latest shipped 4.8 kernel (Linux szx 4.8.0-30-generic #32-Ubuntu SMP Fri Dec 2 03:43:27 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux), with the extra xinput configuration below, I am able to get the trackpad to recover, simply by clicking the trackpad: /usr/share/X11/xorg.conf.d/99-libinput.conf: Section "InputClass" Identifier "libinput touchpad catchall" Driver "libinput" MatchIsTouchpad "on" MatchDevicePath "/dev/input/event*" Option "Tapping" "True" Option "DisableWhileTyping" "True" Option "NaturalScrolling" "False" Option "AccelProfile" "adaptive" Option "AccelSpeed" "0.05" Option "MiddleEmulation" "True" Option "ScrollMethod" "twofinger" # Option "ClickMethod" "clickfinger" Option "ClickMethod" "buttonareas" EndSection In my experience, the problem manifests using both the Xorg synaptics driver and the Xorg libinput driver. root@szx:/etc/modprobe.d# xinput list ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ Logitech M570 id=10 [slave pointer (2)] ⎜ ↳ DLL075B:01 06CB:76AF Touchpad id=13 [slave pointer (2)] ⎜ ↳ ELAN Touchscreenid=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Buttonid=8[slave keyboard (3)] ↳ Sleep Buttonid=9[slave keyboard (3)] ↳ Integrated_Webcam_HDid=12 [slave keyboard (3)] ↳ Intel Virtual Button driver id=14 [slave keyboard (3)] ↳ Intel HID eventsid=15 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=16 [slave keyboard (3)] ↳ Dell WMI hotkeysid=17 [slave keyboard (3)] root@szx:/etc/modprobe.d# To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1651635/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1730596] Re: s390/mm: fix write access check in gup_huge_pmd()
** Tags removed: verification-needed-zesty
** Tags added: verification-done-zesty
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1730596
Title:
s390/mm: fix write access check in gup_huge_pmd()
Status in Ubuntu on IBM z Systems:
Fix Committed
Status in linux package in Ubuntu:
Fix Committed
Status in linux source package in Xenial:
Fix Committed
Status in linux source package in Zesty:
Fix Committed
Status in linux source package in Artful:
Fix Committed
Status in linux source package in Bionic:
Fix Committed
Bug description:
== SRU Justification ==
The check for the _SEGMENT_ENTRY_PROTECT bit in gup_huge_pmd() is the
wrong way around. It must not be set for write==1, and not be checked for
write==0. Fix this similar to how it was fixed for ptes long time ago in
commit 25591b0 ("[S390] fix get_user_pages_fast").
One impact of this bug would be unnecessarily using the gup slow path for
write==0 on r/w mappings. A potentially more severe impact would be that
gup_huge_pmd() will succeed for write==1 on r/o mappings.
This bug is fixed by mainline commit ba385c0594, which is in mainline
as of v4.14-rc2. It was also cc'd to upstream stable. It has already
been accepted in upstream v4.13.y, so Artful and Bionic have the fix
via the 4.13.5 stable updates.
== Fix ==
commit ba385c0594e723d41790ecfb12c610e6f90c7785
Author: Gerald Schaefer
Date: Mon Sep 18 16:51:51 2017 +0200
s390/mm: fix write access check in gup_huge_pmd()
== Regression Potential ==
This patch is specific to s390. It has also been accepted by upstream
stable, so additional upstream review has been done.
Addl information
Problem: The check for the _SEGMENT_ENTRY_PROTECT bit in
gup_huge_pmd() is the wrong way around. It must not be set
for write==1, and not be checked for write==0. Allowing
write==1 with protection bit set, instead of breaking out
to the slow path, will result in a missing faultin_page()
to clear the protection bit (for valid writable mappings),
and the async I/O write operation will fail to write to
such a mapping.
Solution: Fix it by correctly checking the protection bit like it is
also done in gup_pte_range() and gup_huge_pud().
Reproduction: Async I/O workload on buffers that are mapped as transparent
hugepages.
Upstream-ID: ba385c0594e723d41790ecfb12c610e6f90c7785
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1730596/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1731264] Re: linux: 4.4.0-101.124 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/certification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/security-signoff Status: New => Confirmed ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: 1731266 derivatives: - kernel-stable-phase-changed:Friday, 10. November 2017 11:30 UTC - kernel-stable-phase:Uploaded - -- swm properties -- boot-testing-requested: true phase: Uploaded + kernel-stable-phase:Promoted to proposed + kernel-stable-phase-changed:Tuesday, 14. November 2017 09:31 UTC ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: 1731266 derivatives: -- swm properties -- boot-testing-requested: true - phase: Uploaded - kernel-stable-phase:Promoted to proposed - kernel-stable-phase-changed:Tuesday, 14. November 2017 09:31 UTC + phase: Promoted to proposed + proposed-announcement-sent: true + proposed-testing-requested: true -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1731264 Title: linux: 4.4.0-101.124 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Confirmed Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow snap-certification-testing series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: 1731266 derivatives: -- swm properties -- boot-testing-requested: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1731264/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1730596] Re: s390/mm: fix write access check in gup_huge_pmd()
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag 'verification-needed-xenial' to 'verification-failed-
xenial'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: verification-needed-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/1730596
Title:
s390/mm: fix write access check in gup_huge_pmd()
Status in Ubuntu on IBM z Systems:
Fix Committed
Status in linux package in Ubuntu:
Fix Committed
Status in linux source package in Xenial:
Fix Committed
Status in linux source package in Zesty:
Fix Committed
Status in linux source package in Artful:
Fix Committed
Status in linux source package in Bionic:
Fix Committed
Bug description:
== SRU Justification ==
The check for the _SEGMENT_ENTRY_PROTECT bit in gup_huge_pmd() is the
wrong way around. It must not be set for write==1, and not be checked for
write==0. Fix this similar to how it was fixed for ptes long time ago in
commit 25591b0 ("[S390] fix get_user_pages_fast").
One impact of this bug would be unnecessarily using the gup slow path for
write==0 on r/w mappings. A potentially more severe impact would be that
gup_huge_pmd() will succeed for write==1 on r/o mappings.
This bug is fixed by mainline commit ba385c0594, which is in mainline
as of v4.14-rc2. It was also cc'd to upstream stable. It has already
been accepted in upstream v4.13.y, so Artful and Bionic have the fix
via the 4.13.5 stable updates.
== Fix ==
commit ba385c0594e723d41790ecfb12c610e6f90c7785
Author: Gerald Schaefer
Date: Mon Sep 18 16:51:51 2017 +0200
s390/mm: fix write access check in gup_huge_pmd()
== Regression Potential ==
This patch is specific to s390. It has also been accepted by upstream
stable, so additional upstream review has been done.
Addl information
Problem: The check for the _SEGMENT_ENTRY_PROTECT bit in
gup_huge_pmd() is the wrong way around. It must not be set
for write==1, and not be checked for write==0. Allowing
write==1 with protection bit set, instead of breaking out
to the slow path, will result in a missing faultin_page()
to clear the protection bit (for valid writable mappings),
and the async I/O write operation will fail to write to
such a mapping.
Solution: Fix it by correctly checking the protection bit like it is
also done in gup_pte_range() and gup_huge_pud().
Reproduction: Async I/O workload on buffers that are mapped as transparent
hugepages.
Upstream-ID: ba385c0594e723d41790ecfb12c610e6f90c7785
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1730596/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1730331] Re: ath10k_pci: firmware crashed!
Here is another confirmation of this bug: https://bugzilla.redhat.com/show_bug.cgi?id=1490172 and downgrading to a previous version of linux-firmware (as suggested above, and to xenial-updates in my case), made the problem disappear: $ dpkg -l | grep linux-firmware ii linux-firmware 1.157.13 all Firmware for Linux kernel drivers ** Bug watch added: Red Hat Bugzilla #1490172 https://bugzilla.redhat.com/show_bug.cgi?id=1490172 -- 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/1730331 Title: ath10k_pci: firmware crashed! Status in linux package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: New Bug description: ... Nov 4 18:35:50 akane kernel: [ 10.216896] ath10k_pci :04:00.0: qca988x hw2.0 target 0x4100016c chip_id 0x043222ff sub : Nov 4 18:35:50 akane kernel: [ 10.216908] ath10k_pci :04:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0 Nov 4 18:35:50 akane kernel: [ 10.217641] ath10k_pci :04:00.0: firmware ver 10.2.4.70.63-2 api 5 features no-p2p,raw-mode,mfp,allows-mesh-bcast crc32 4ff9e14d Nov 4 18:35:50 akane kernel: [ 10.228600] kvm: Nested Virtualization enabled Nov 4 18:35:50 akane kernel: [ 10.228611] kvm: Nested Paging enabled Nov 4 18:35:50 akane kernel: [ 10.258913] ath10k_pci :04:00.0: board_file api 1 bmi_id N/A crc32 bebc7c08 Nov 4 18:35:50 akane kernel: [ 10.263535] MCE: In-kernel MCE decoding enabled. Nov 4 18:35:50 akane kernel: [ 10.271401] EDAC amd64: Node 0: DRAM ECC enabled. Nov 4 18:35:50 akane kernel: [ 10.271416] EDAC amd64: F16h_M30h detected (node 0). Nov 4 18:35:50 akane kernel: [ 10.271491] EDAC MC: DCT0 chip selects: Nov 4 18:35:50 akane kernel: [ 10.271494] EDAC amd64: MC: 0: 4096MB 1: 0MB Nov 4 18:35:50 akane kernel: [ 10.271523] EDAC amd64: MC: 2: 0MB 3: 0MB Nov 4 18:35:50 akane kernel: [ 10.271526] EDAC amd64: MC: 4: 0MB 5: 0MB Nov 4 18:35:50 akane kernel: [ 10.271528] EDAC amd64: MC: 6: 0MB 7: 0MB Nov 4 18:35:50 akane kernel: [ 10.271530] EDAC MC: DCT1 chip selects: Nov 4 18:35:50 akane kernel: [ 10.271532] EDAC amd64: MC: 0: 0MB 1: 0MB Nov 4 18:35:50 akane kernel: [ 10.271534] EDAC amd64: MC: 2: 0MB 3: 0MB Nov 4 18:35:50 akane kernel: [ 10.271537] EDAC amd64: MC: 4: 0MB 5: 0MB Nov 4 18:35:50 akane kernel: [ 10.271539] EDAC amd64: MC: 6: 0MB 7: 0MB Nov 4 18:35:50 akane kernel: [ 10.271541] EDAC amd64: using x4 syndromes. Nov 4 18:35:50 akane kernel: [ 10.271542] EDAC amd64: MCT channel count: 1 Nov 4 18:35:50 akane kernel: [ 10.271829] EDAC MC0: Giving out device to module amd64_edac controller F16h_M30h: DEV :00:18.3 (INTERRUPT) Nov 4 18:35:50 akane kernel: [ 10.271892] EDAC PCI0: Giving out device to module amd64_edac controller EDAC PCI controller: DEV :00:18.2 (POLLED) Nov 4 18:35:50 akane kernel: [ 10.271894] AMD64 EDAC driver v3.5.0 Nov 4 18:35:50 akane kernel: [ 10.532131] EXT4-fs (sdc1): mounted filesystem with ordered data mode. Opts: errors=remount-ro Nov 4 18:35:50 akane kernel: [ 10.575859] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: errors=remount-ro Nov 4 18:35:50 akane kernel: [ 11.397803] ath10k_pci :04:00.0: firmware crashed! (uuid f75dd562-d1bb-40a7-8454-fdc5f86cb8aa) Nov 4 18:35:50 akane kernel: [ 11.407389] ath10k_pci :04:00.0: qca988x hw2.0 target 0x4100016c chip_id 0x043222ff sub : Nov 4 18:35:50 akane kernel: [ 11.407395] ath10k_pci :04:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0 Nov 4 18:35:50 akane kernel: [ 11.408085] ath10k_pci :04:00.0: firmware ver 10.2.4.70.63-2 api 5 features no-p2p,raw-mode,mfp,allows-mesh-bcast crc32 4ff9e14d Nov 4 18:35:50 akane kernel: [ 11.408148] ath10k_pci :04:00.0: board_file api 1 bmi_id N/A crc32 bebc7c08 Nov 4 18:35:50 akane kernel: [ 11.408156] ath10k_pci :04:00.0: htt-ver 0.0 wmi-op 5 htt-op 2 cal otp max-sta 128 raw 0 hwcrypto 1 Nov 4 18:35:50 akane kernel: [ 11.410197] ath10k_pci :04:00.0: firmware register dump: Nov 4 18:35:50 akane kernel: [ 11.416213] ath10k_pci :04:00.0: [00]: 0x4100016C 0x15B3 0x009BFF84 0x00955B31 Nov 4 18:35:50 akane kernel: [ 11.424559] ath10k_pci :04:00.0: [04]: 0x009BFF84 0x00060130 0x0013 0x Nov 4 18:35:50 akane kernel: [ 11.432767] ath10k_pci :04:00.0: [08]: 0x009C8EA4 0x7170 0x0001 0x00435300 Nov 4 18:35:50 akane kernel: [ 11.441059] ath10k_pci :04:00.0: [12]: 0x0009 0x 0x00958360 0x0095836B Nov 4 18:35:50 akane kernel: [ 11.449397] ath10k_pci :04:00.0: [16]: 0x00958080 0x0094078E 0x 0x Nov 4 18:35:50 a
[Kernel-packages] [Bug 1732034] Re: Microphone headset isn't detected with Intel Skull Canyon NUC
** Attachment added: "codec0.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1732034/+attachment/5008813/+files/codec0.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/1732034 Title: Microphone headset isn't detected with Intel Skull Canyon NUC Status in linux package in Ubuntu: Confirmed Bug description: I've also tested this machine with two separate USB Microphone adapters, and they do the same thing really. Super-low volume on the mic. I can only see a bit of a spike if I tap the mic hard. I can confirm the Headset/Microphone selection screen pops up when plugging the headset in. This workaround works after a reboot: https://communities.intel.com/thread/108361 > # Add to /etc/modprobe.d/alsa-base.conf > options snd-hda-intel model=dell-headset-multi I'm using this headset https://www.amazon.co.uk/HyperX-Stinger-Gaming- Headset- Mobile/dp/B01LRX2DSA/ref=sr_1_2?ie=UTF8&qid=1510612581&sr=8-2&ppw=fresh&keywords=hyperx+gaming+headphones ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-16-generic 4.13.0-16.19 [modified: boot/vmlinuz-4.13.0-16-generic] ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: andrewvos 1395 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Nov 13 22:30:33 2017 InstallationDate: Installed on 2017-11-10 (3 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed root=UUID=b7992a74-c44e-44cc-be68-f658972e448f ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-16-generic N/A linux-backports-modules-4.13.0-16-generic N/A linux-firmware 1.169 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/31/2017 dmi.bios.vendor: Intel Corp. dmi.bios.version: KYSKLi70.86A.0050.2017.0831.1924 dmi.board.name: NUC6i7KYB dmi.board.vendor: Intel Corporation dmi.board.version: H90766-406 dmi.chassis.type: 3 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnIntelCorp.:bvrKYSKLi70.86A.0050.2017.0831.1924:bd08/31/2017:svn:pn:pvr:rvnIntelCorporation:rnNUC6i7KYB:rvrH90766-406:cvnIntelCorporation:ct3:cvr1.0: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1732034/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1731269] Re: linux: 4.10.0-40.44 -proposed tracker
Verification done. ** Changed in: kernel-sru-workflow/verification-testing Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/verification-testing Assignee: Canonical Kernel Team (canonical-kernel-team) => Po-Hsu Lin (cypressyew) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1731269 Title: linux: 4.10.0-40.44 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Confirmed Status in Kernel SRU Workflow certification-testing series: In Progress Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Zesty: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: 1731270 derivatives: -- swm properties -- boot-testing-requested: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1731269/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1731163] Re: Trackpoint device not working by default on Thinkpad L570
No, multi touch does not work any more with this parameter. Touch pad and track point are reduced to the functions of a standard mouse, I beliebe, which can also be seen in the corresponding settings dialog. Scrolling with the help of the middle track point button works though, as it is customary on ThinkPad models. ** Attachment added: "Settings dialog - limited to standard mouse settings" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1731163/+attachment/5008812/+files/settings-touch-devices.png -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1731163 Title: Trackpoint device not working by default on Thinkpad L570 Status in linux package in Ubuntu: Confirmed Bug description: Installing Ubuntu 17.10 on a ThinkPad L570 (L470 should be the same in this regard) leaves the trackpoint as well as the trackpoint buttons in a non-working state. Most probably, it is not correctly detected on startup; dmesg shows kernel: [ 2.997182 ] input: AlpsPS/2 ALPS GlidePoint as /devices/platform/i8042/serio1/input/input6 As far as I understand it, "GlidePoint" only refers to a touch pad without track point. All events coming from the track point are consequently actively discarded, seen in dmesg as kernel: [ 2279.323441 ] psmouse serio1: alps: Rejected trackstick packet from non DualPoint device Searching for this problem I found this kernel developer discussion which seems related: https://patchwork.kernel.org/patch/9941661/ As suggested by one of the kernel developers there, I added "psmouse.proto=imps" as a kernel boot parameter. The touch pad and track point now show up in the system log as input: PS/2 Generic Mouse as /devices/platform/i8042/serio1/input/input6 And it works well now, just as it should. I also noted that the touch pad became a lot more usable at the same time. Previously (with the default installation) it was lagging and could produce pseudo clicks at random. I am submitting this report here in order to help improve the hardware detection in Ubuntu / linux kernel. Ubuntu version: 17.10 Kernel version: 4.13.0.16.17 Default GNOME desktop, Wayland, etc, just as it comes in the default install --- ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dirichs 896 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-11-07 (1 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 5986:111c Acer, Inc Bus 001 Device 004: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20J8CTO1WW Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed root=UUID=f2a92db0-5f37-4d70-b878-a4ba4c80e890 ro quiet splash psmouse.proto=imps vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 RelatedPackageVersions: linux-restricted-modules-4.13.0-16-generic N/A linux-backports-modules-4.13.0-16-generic N/A linux-firmware 1.169 Tags: wayland-session artful Uname: Linux 4.13.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/12/2017 dmi.bios.vendor: LENOVO dmi.bios.version: N1XET43W (1.21 ) dmi.board.asset.tag: Not Available dmi.board.name: 20J8CTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1XET43W(1.21):bd07/12/2017:svnLENOVO:pn20J8CTO1WW:pvrThinkPadL570:rvnLENOVO:rn20J8CTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad L570 dmi.product.name: 20J8CTO1WW dmi.product.version: ThinkPad L570 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1731163/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1728244] Re: Touchpad stops working after reboot on Apollo Lake
[7.350290] input: SYNA3602:00 0911:5288 Touchpad as /devices/pci:00/:00:16.1/i2c_designware.1/i2c-5/i2c-SYNA3602:00/0018:0911:5288.0002/input/input18 [7.350982] hid-multitouch 0018:0911:5288.0002: input,hidraw1: I2C HID v1.00 Mouse [SYNA3602:00 0911:5288] on i2c-SYNA3602:00 This is my touchpad, as far as I'm concerned. Honestly, even If I am a noob, I don't think this "Hantick thing" is a solution... rc7 recognizes mytouhpad, but button clicks. Anyway, tell me what you want me to do and I'll do it! :) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1728244 Title: Touchpad stops working after reboot on Apollo Lake Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Bug description: On the Jumper EZBook 3 Pro (V4) laptop, using an Apollo Lake N3450 processor, if you install Ubuntu 17.10 (or less) with isorespin and use rEFInd as bootloader (this is the only way to get linux booting on this laptop) everything works out of the box, but after a reboot or two the touchpad stops working. Both in Ubuntu and Windows 10. The only way to restore functionality is to boot from usb key ubuntu 17.10 respined, or disassemble laptop and detach-reattach battery cable. This is mesg | grep i2c_hid: [ 2056.460636] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (27/34) [ 3077.604699] i2c_hid i2c-SYNA3602:00: failed to reset device. [ 3077.605473] dpm_run_callback(): i2c_hid_resume+0x0/0xe0 [i2c_hid] returns -61 [ 3080.468156] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (27/34) uname -rvps Linux 4.10.0-32-generic #36~16.04.1-Ubuntu SMP Wed Aug 9 09:19:02 UTC 2017 x86_64 There has to be a bug in the kernel. Any way to avoid this? To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1728244/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1732162] [NEW] Zesty / Artful zKVM does not have /dev/kvm
Public bug reported: For now we have 3 zKVM instances running Xenial, Zesty and Artful kernel respectively. The /dev/kvm does not exist on Zesty and Artful kernel. kvm-ok output on Zesty $ sudo kvm-ok INFO: /dev/kvm does not exist HINT: sudo modprobe kvm modprobe: FATAL: Module msr not found in directory /lib/modules/4.10.0-40-generic kvm-ok output on Artful $ sudo kvm-ok INFO: /dev/kvm does not exist HINT: sudo modprobe kvm modprobe: FATAL: Module msr not found in directory /lib/modules/4.13.0-17-generic ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-17-generic 4.13.0-17.20 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 Uname: Linux 4.13.0-17-generic s390x NonfreeKernelModules: zfs zunicode zavl zcommon znvpair AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.7-0ubuntu3.2 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CurrentDmesg: Date: Tue Nov 14 11:18:49 2017 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C SHELL=/bin/bash ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb' ProcKernelCmdLine: root=UUID=d86dc8de-6ac8-4e4b-aba8-92872a209a8c crashkernel=196M RelatedPackageVersions: linux-restricted-modules-4.13.0-17-generic N/A linux-backports-modules-4.13.0-17-generic N/A linux-firmware 1.169 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: apport-bug artful package-from-proposed s390x -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1732162 Title: Zesty / Artful zKVM does not have /dev/kvm Status in linux package in Ubuntu: Incomplete Bug description: For now we have 3 zKVM instances running Xenial, Zesty and Artful kernel respectively. The /dev/kvm does not exist on Zesty and Artful kernel. kvm-ok output on Zesty $ sudo kvm-ok INFO: /dev/kvm does not exist HINT: sudo modprobe kvm modprobe: FATAL: Module msr not found in directory /lib/modules/4.10.0-40-generic kvm-ok output on Artful $ sudo kvm-ok INFO: /dev/kvm does not exist HINT: sudo modprobe kvm modprobe: FATAL: Module msr not found in directory /lib/modules/4.13.0-17-generic ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-17-generic 4.13.0-17.20 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 Uname: Linux 4.13.0-17-generic s390x NonfreeKernelModules: zfs zunicode zavl zcommon znvpair AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.7-0ubuntu3.2 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CurrentDmesg: Date: Tue Nov 14 11:18:49 2017 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C SHELL=/bin/bash ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb' ProcKernelCmdLine: root=UUID=d86dc8de-6ac8-4e4b-aba8-92872a209a8c crashkernel=196M RelatedPackageVersions: linux-restricted-modules-4.13.0-17-generic N/A linux-backports-modules-4.13.0-17-generic N/A linux-firmware 1.169 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1732162/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1732162] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1732162 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1732162 Title: Zesty / Artful zKVM does not have /dev/kvm Status in linux package in Ubuntu: Incomplete Bug description: For now we have 3 zKVM instances running Xenial, Zesty and Artful kernel respectively. The /dev/kvm does not exist on Zesty and Artful kernel. kvm-ok output on Zesty $ sudo kvm-ok INFO: /dev/kvm does not exist HINT: sudo modprobe kvm modprobe: FATAL: Module msr not found in directory /lib/modules/4.10.0-40-generic kvm-ok output on Artful $ sudo kvm-ok INFO: /dev/kvm does not exist HINT: sudo modprobe kvm modprobe: FATAL: Module msr not found in directory /lib/modules/4.13.0-17-generic ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-17-generic 4.13.0-17.20 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 Uname: Linux 4.13.0-17-generic s390x NonfreeKernelModules: zfs zunicode zavl zcommon znvpair AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.7-0ubuntu3.2 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CurrentDmesg: Date: Tue Nov 14 11:18:49 2017 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C SHELL=/bin/bash ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb' ProcKernelCmdLine: root=UUID=d86dc8de-6ac8-4e4b-aba8-92872a209a8c crashkernel=196M RelatedPackageVersions: linux-restricted-modules-4.13.0-17-generic N/A linux-backports-modules-4.13.0-17-generic N/A linux-firmware 1.169 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1732162/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1731913] Re: New kernel 4.13.0-16 is buggy on session lock
apport information ** Tags added: apport-collected artful ** Description changed: Hi, I updated my distro from 17.04 to 17.10 in the last week. My 'budgie-desktop' is 10.4. My graphic card is an Nvidia GTX 1070. Since the update, when I lock my session with new kernel, my screen don't wakeup correctly when I try to login again. The screen light is off, but I can hardly distinct login window. I can login, but screen light doesn't get back until I reboot my computer. I have to set GRUB_DEFAULT to old kernel '4.10.0-38' for no getting this problem. If you need more information feel free to ask ! + --- + ApportVersion: 2.20.7-0ubuntu3.1 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: john 2621 F pulseaudio + CurrentDesktop: Budgie:GNOME + DistroRelease: Ubuntu 17.10 + EcryptfsInUse: Yes + HibernationDevice: RESUME=UUID=997c0c1c-72b4-491d-9dfc-da86f655bcca + MachineType: ASUSTeK COMPUTER INC. GL502VSK + Package: linux (not installed) + ProcFB: 0 nouveaufb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-lowlatency root=UUID=5fe02e3e-86d4-4749-a879-902fc34feda5 ro quiet splash acpi_osi= vt.handoff=7 + ProcVersionSignature: Ubuntu 4.13.0-16.19-lowlatency 4.13.4 + RelatedPackageVersions: + linux-restricted-modules-4.13.0-16-lowlatency N/A + linux-backports-modules-4.13.0-16-lowlatency N/A + linux-firmware1.169 + Tags: artful + Uname: Linux 4.13.0-16-lowlatency x86_64 + UpgradeStatus: Upgraded to artful on 2017-11-10 (4 days ago) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 03/28/2017 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: GL502VSK.303 + dmi.board.asset.tag: ATN12345678901234567 + dmi.board.name: GL502VSK + 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.:bvrGL502VSK.303:bd03/28/2017:svnASUSTeKCOMPUTERINC.:pnGL502VSK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL502VSK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: + dmi.product.family: GL + dmi.product.name: GL502VSK + dmi.product.version: 1.0 + dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1731913/+attachment/5008845/+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/1731913 Title: New kernel 4.13.0-16 is buggy on session lock Status in linux package in Ubuntu: Confirmed Bug description: Hi, I updated my distro from 17.04 to 17.10 in the last week. My 'budgie-desktop' is 10.4. My graphic card is an Nvidia GTX 1070. Since the update, when I lock my session with new kernel, my screen don't wakeup correctly when I try to login again. The screen light is off, but I can hardly distinct login window. I can login, but screen light doesn't get back until I reboot my computer. I have to set GRUB_DEFAULT to old kernel '4.10.0-38' for no getting this problem. If you need more information feel free to ask ! --- ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: john 2621 F pulseaudio CurrentDesktop: Budgie:GNOME DistroRelease: Ubuntu 17.10 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=997c0c1c-72b4-491d-9dfc-da86f655bcca MachineType: ASUSTeK COMPUTER INC. GL502VSK Package: linux (not installed) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-lowlatency root=UUID=5fe02e3e-86d4-4749-a879-902fc34feda5 ro quiet splash acpi_osi= vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-16.19-lowlatency 4.13.4 RelatedPackageVersions: linux-restricted-modules-4.13.0-16-lowlatency N/A linux-backports-modules-4.13.0-16-lowlatency N/A linux-firmware1.169 Tags: artful Uname: Linux 4.13.0-16-lowlatency x86_64 UpgradeStatus: Upgraded to artful on 2017-11-10 (4 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/28/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GL502VSK.303 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GL502VSK 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.:bvrGL502VSK.303:bd03/28/2017:svnASUSTeKCOMPUTERINC.:pnGL502VSK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL502VSK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: GL dmi.product.name: GL502VSK dmi.product.v
[Kernel-packages] [Bug 1731913] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1731913/+attachment/5008847/+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/1731913 Title: New kernel 4.13.0-16 is buggy on session lock Status in linux package in Ubuntu: Confirmed Bug description: Hi, I updated my distro from 17.04 to 17.10 in the last week. My 'budgie-desktop' is 10.4. My graphic card is an Nvidia GTX 1070. Since the update, when I lock my session with new kernel, my screen don't wakeup correctly when I try to login again. The screen light is off, but I can hardly distinct login window. I can login, but screen light doesn't get back until I reboot my computer. I have to set GRUB_DEFAULT to old kernel '4.10.0-38' for no getting this problem. If you need more information feel free to ask ! --- ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: john 2621 F pulseaudio CurrentDesktop: Budgie:GNOME DistroRelease: Ubuntu 17.10 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=997c0c1c-72b4-491d-9dfc-da86f655bcca MachineType: ASUSTeK COMPUTER INC. GL502VSK Package: linux (not installed) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-lowlatency root=UUID=5fe02e3e-86d4-4749-a879-902fc34feda5 ro quiet splash acpi_osi= vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-16.19-lowlatency 4.13.4 RelatedPackageVersions: linux-restricted-modules-4.13.0-16-lowlatency N/A linux-backports-modules-4.13.0-16-lowlatency N/A linux-firmware1.169 Tags: artful Uname: Linux 4.13.0-16-lowlatency x86_64 UpgradeStatus: Upgraded to artful on 2017-11-10 (4 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/28/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GL502VSK.303 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GL502VSK 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.:bvrGL502VSK.303:bd03/28/2017:svnASUSTeKCOMPUTERINC.:pnGL502VSK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL502VSK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: GL dmi.product.name: GL502VSK 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/1731913/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1731913] JournalErrors.txt
apport information ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1731913/+attachment/5008849/+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/1731913 Title: New kernel 4.13.0-16 is buggy on session lock Status in linux package in Ubuntu: Confirmed Bug description: Hi, I updated my distro from 17.04 to 17.10 in the last week. My 'budgie-desktop' is 10.4. My graphic card is an Nvidia GTX 1070. Since the update, when I lock my session with new kernel, my screen don't wakeup correctly when I try to login again. The screen light is off, but I can hardly distinct login window. I can login, but screen light doesn't get back until I reboot my computer. I have to set GRUB_DEFAULT to old kernel '4.10.0-38' for no getting this problem. If you need more information feel free to ask ! --- ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: john 2621 F pulseaudio CurrentDesktop: Budgie:GNOME DistroRelease: Ubuntu 17.10 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=997c0c1c-72b4-491d-9dfc-da86f655bcca MachineType: ASUSTeK COMPUTER INC. GL502VSK Package: linux (not installed) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-lowlatency root=UUID=5fe02e3e-86d4-4749-a879-902fc34feda5 ro quiet splash acpi_osi= vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-16.19-lowlatency 4.13.4 RelatedPackageVersions: linux-restricted-modules-4.13.0-16-lowlatency N/A linux-backports-modules-4.13.0-16-lowlatency N/A linux-firmware1.169 Tags: artful Uname: Linux 4.13.0-16-lowlatency x86_64 UpgradeStatus: Upgraded to artful on 2017-11-10 (4 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/28/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GL502VSK.303 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GL502VSK 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.:bvrGL502VSK.303:bd03/28/2017:svnASUSTeKCOMPUTERINC.:pnGL502VSK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL502VSK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: GL dmi.product.name: GL502VSK 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/1731913/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1731913] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1731913/+attachment/5008854/+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/1731913 Title: New kernel 4.13.0-16 is buggy on session lock Status in linux package in Ubuntu: Confirmed Bug description: Hi, I updated my distro from 17.04 to 17.10 in the last week. My 'budgie-desktop' is 10.4. My graphic card is an Nvidia GTX 1070. Since the update, when I lock my session with new kernel, my screen don't wakeup correctly when I try to login again. The screen light is off, but I can hardly distinct login window. I can login, but screen light doesn't get back until I reboot my computer. I have to set GRUB_DEFAULT to old kernel '4.10.0-38' for no getting this problem. If you need more information feel free to ask ! --- ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: john 2621 F pulseaudio CurrentDesktop: Budgie:GNOME DistroRelease: Ubuntu 17.10 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=997c0c1c-72b4-491d-9dfc-da86f655bcca MachineType: ASUSTeK COMPUTER INC. GL502VSK Package: linux (not installed) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-lowlatency root=UUID=5fe02e3e-86d4-4749-a879-902fc34feda5 ro quiet splash acpi_osi= vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-16.19-lowlatency 4.13.4 RelatedPackageVersions: linux-restricted-modules-4.13.0-16-lowlatency N/A linux-backports-modules-4.13.0-16-lowlatency N/A linux-firmware1.169 Tags: artful Uname: Linux 4.13.0-16-lowlatency x86_64 UpgradeStatus: Upgraded to artful on 2017-11-10 (4 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/28/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GL502VSK.303 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GL502VSK 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.:bvrGL502VSK.303:bd03/28/2017:svnASUSTeKCOMPUTERINC.:pnGL502VSK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL502VSK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: GL dmi.product.name: GL502VSK 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/1731913/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1731913] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1731913/+attachment/5008855/+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/1731913 Title: New kernel 4.13.0-16 is buggy on session lock Status in linux package in Ubuntu: Confirmed Bug description: Hi, I updated my distro from 17.04 to 17.10 in the last week. My 'budgie-desktop' is 10.4. My graphic card is an Nvidia GTX 1070. Since the update, when I lock my session with new kernel, my screen don't wakeup correctly when I try to login again. The screen light is off, but I can hardly distinct login window. I can login, but screen light doesn't get back until I reboot my computer. I have to set GRUB_DEFAULT to old kernel '4.10.0-38' for no getting this problem. If you need more information feel free to ask ! --- ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: john 2621 F pulseaudio CurrentDesktop: Budgie:GNOME DistroRelease: Ubuntu 17.10 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=997c0c1c-72b4-491d-9dfc-da86f655bcca MachineType: ASUSTeK COMPUTER INC. GL502VSK Package: linux (not installed) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-lowlatency root=UUID=5fe02e3e-86d4-4749-a879-902fc34feda5 ro quiet splash acpi_osi= vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-16.19-lowlatency 4.13.4 RelatedPackageVersions: linux-restricted-modules-4.13.0-16-lowlatency N/A linux-backports-modules-4.13.0-16-lowlatency N/A linux-firmware1.169 Tags: artful Uname: Linux 4.13.0-16-lowlatency x86_64 UpgradeStatus: Upgraded to artful on 2017-11-10 (4 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/28/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GL502VSK.303 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GL502VSK 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.:bvrGL502VSK.303:bd03/28/2017:svnASUSTeKCOMPUTERINC.:pnGL502VSK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL502VSK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: GL dmi.product.name: GL502VSK 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/1731913/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1731913] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1731913/+attachment/5008852/+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/1731913 Title: New kernel 4.13.0-16 is buggy on session lock Status in linux package in Ubuntu: Confirmed Bug description: Hi, I updated my distro from 17.04 to 17.10 in the last week. My 'budgie-desktop' is 10.4. My graphic card is an Nvidia GTX 1070. Since the update, when I lock my session with new kernel, my screen don't wakeup correctly when I try to login again. The screen light is off, but I can hardly distinct login window. I can login, but screen light doesn't get back until I reboot my computer. I have to set GRUB_DEFAULT to old kernel '4.10.0-38' for no getting this problem. If you need more information feel free to ask ! --- ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: john 2621 F pulseaudio CurrentDesktop: Budgie:GNOME DistroRelease: Ubuntu 17.10 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=997c0c1c-72b4-491d-9dfc-da86f655bcca MachineType: ASUSTeK COMPUTER INC. GL502VSK Package: linux (not installed) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-lowlatency root=UUID=5fe02e3e-86d4-4749-a879-902fc34feda5 ro quiet splash acpi_osi= vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-16.19-lowlatency 4.13.4 RelatedPackageVersions: linux-restricted-modules-4.13.0-16-lowlatency N/A linux-backports-modules-4.13.0-16-lowlatency N/A linux-firmware1.169 Tags: artful Uname: Linux 4.13.0-16-lowlatency x86_64 UpgradeStatus: Upgraded to artful on 2017-11-10 (4 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/28/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GL502VSK.303 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GL502VSK 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.:bvrGL502VSK.303:bd03/28/2017:svnASUSTeKCOMPUTERINC.:pnGL502VSK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL502VSK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: GL dmi.product.name: GL502VSK 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/1731913/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1731913] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1731913/+attachment/5008850/+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/1731913 Title: New kernel 4.13.0-16 is buggy on session lock Status in linux package in Ubuntu: Confirmed Bug description: Hi, I updated my distro from 17.04 to 17.10 in the last week. My 'budgie-desktop' is 10.4. My graphic card is an Nvidia GTX 1070. Since the update, when I lock my session with new kernel, my screen don't wakeup correctly when I try to login again. The screen light is off, but I can hardly distinct login window. I can login, but screen light doesn't get back until I reboot my computer. I have to set GRUB_DEFAULT to old kernel '4.10.0-38' for no getting this problem. If you need more information feel free to ask ! --- ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: john 2621 F pulseaudio CurrentDesktop: Budgie:GNOME DistroRelease: Ubuntu 17.10 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=997c0c1c-72b4-491d-9dfc-da86f655bcca MachineType: ASUSTeK COMPUTER INC. GL502VSK Package: linux (not installed) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-lowlatency root=UUID=5fe02e3e-86d4-4749-a879-902fc34feda5 ro quiet splash acpi_osi= vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-16.19-lowlatency 4.13.4 RelatedPackageVersions: linux-restricted-modules-4.13.0-16-lowlatency N/A linux-backports-modules-4.13.0-16-lowlatency N/A linux-firmware1.169 Tags: artful Uname: Linux 4.13.0-16-lowlatency x86_64 UpgradeStatus: Upgraded to artful on 2017-11-10 (4 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/28/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GL502VSK.303 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GL502VSK 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.:bvrGL502VSK.303:bd03/28/2017:svnASUSTeKCOMPUTERINC.:pnGL502VSK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL502VSK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: GL dmi.product.name: GL502VSK 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/1731913/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1731913] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1731913/+attachment/5008846/+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/1731913 Title: New kernel 4.13.0-16 is buggy on session lock Status in linux package in Ubuntu: Confirmed Bug description: Hi, I updated my distro from 17.04 to 17.10 in the last week. My 'budgie-desktop' is 10.4. My graphic card is an Nvidia GTX 1070. Since the update, when I lock my session with new kernel, my screen don't wakeup correctly when I try to login again. The screen light is off, but I can hardly distinct login window. I can login, but screen light doesn't get back until I reboot my computer. I have to set GRUB_DEFAULT to old kernel '4.10.0-38' for no getting this problem. If you need more information feel free to ask ! --- ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: john 2621 F pulseaudio CurrentDesktop: Budgie:GNOME DistroRelease: Ubuntu 17.10 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=997c0c1c-72b4-491d-9dfc-da86f655bcca MachineType: ASUSTeK COMPUTER INC. GL502VSK Package: linux (not installed) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-lowlatency root=UUID=5fe02e3e-86d4-4749-a879-902fc34feda5 ro quiet splash acpi_osi= vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-16.19-lowlatency 4.13.4 RelatedPackageVersions: linux-restricted-modules-4.13.0-16-lowlatency N/A linux-backports-modules-4.13.0-16-lowlatency N/A linux-firmware1.169 Tags: artful Uname: Linux 4.13.0-16-lowlatency x86_64 UpgradeStatus: Upgraded to artful on 2017-11-10 (4 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/28/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GL502VSK.303 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GL502VSK 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.:bvrGL502VSK.303:bd03/28/2017:svnASUSTeKCOMPUTERINC.:pnGL502VSK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL502VSK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: GL dmi.product.name: GL502VSK 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/1731913/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1731913] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1731913/+attachment/5008851/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1731913 Title: New kernel 4.13.0-16 is buggy on session lock Status in linux package in Ubuntu: Confirmed Bug description: Hi, I updated my distro from 17.04 to 17.10 in the last week. My 'budgie-desktop' is 10.4. My graphic card is an Nvidia GTX 1070. Since the update, when I lock my session with new kernel, my screen don't wakeup correctly when I try to login again. The screen light is off, but I can hardly distinct login window. I can login, but screen light doesn't get back until I reboot my computer. I have to set GRUB_DEFAULT to old kernel '4.10.0-38' for no getting this problem. If you need more information feel free to ask ! --- ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: john 2621 F pulseaudio CurrentDesktop: Budgie:GNOME DistroRelease: Ubuntu 17.10 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=997c0c1c-72b4-491d-9dfc-da86f655bcca MachineType: ASUSTeK COMPUTER INC. GL502VSK Package: linux (not installed) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-lowlatency root=UUID=5fe02e3e-86d4-4749-a879-902fc34feda5 ro quiet splash acpi_osi= vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-16.19-lowlatency 4.13.4 RelatedPackageVersions: linux-restricted-modules-4.13.0-16-lowlatency N/A linux-backports-modules-4.13.0-16-lowlatency N/A linux-firmware1.169 Tags: artful Uname: Linux 4.13.0-16-lowlatency x86_64 UpgradeStatus: Upgraded to artful on 2017-11-10 (4 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/28/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GL502VSK.303 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GL502VSK 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.:bvrGL502VSK.303:bd03/28/2017:svnASUSTeKCOMPUTERINC.:pnGL502VSK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL502VSK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: GL dmi.product.name: GL502VSK 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/1731913/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1731913] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1731913/+attachment/5008848/+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/1731913 Title: New kernel 4.13.0-16 is buggy on session lock Status in linux package in Ubuntu: Confirmed Bug description: Hi, I updated my distro from 17.04 to 17.10 in the last week. My 'budgie-desktop' is 10.4. My graphic card is an Nvidia GTX 1070. Since the update, when I lock my session with new kernel, my screen don't wakeup correctly when I try to login again. The screen light is off, but I can hardly distinct login window. I can login, but screen light doesn't get back until I reboot my computer. I have to set GRUB_DEFAULT to old kernel '4.10.0-38' for no getting this problem. If you need more information feel free to ask ! --- ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: john 2621 F pulseaudio CurrentDesktop: Budgie:GNOME DistroRelease: Ubuntu 17.10 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=997c0c1c-72b4-491d-9dfc-da86f655bcca MachineType: ASUSTeK COMPUTER INC. GL502VSK Package: linux (not installed) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-lowlatency root=UUID=5fe02e3e-86d4-4749-a879-902fc34feda5 ro quiet splash acpi_osi= vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-16.19-lowlatency 4.13.4 RelatedPackageVersions: linux-restricted-modules-4.13.0-16-lowlatency N/A linux-backports-modules-4.13.0-16-lowlatency N/A linux-firmware1.169 Tags: artful Uname: Linux 4.13.0-16-lowlatency x86_64 UpgradeStatus: Upgraded to artful on 2017-11-10 (4 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/28/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GL502VSK.303 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GL502VSK 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.:bvrGL502VSK.303:bd03/28/2017:svnASUSTeKCOMPUTERINC.:pnGL502VSK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL502VSK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: GL dmi.product.name: GL502VSK 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/1731913/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1731913] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1731913/+attachment/5008853/+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/1731913 Title: New kernel 4.13.0-16 is buggy on session lock Status in linux package in Ubuntu: Confirmed Bug description: Hi, I updated my distro from 17.04 to 17.10 in the last week. My 'budgie-desktop' is 10.4. My graphic card is an Nvidia GTX 1070. Since the update, when I lock my session with new kernel, my screen don't wakeup correctly when I try to login again. The screen light is off, but I can hardly distinct login window. I can login, but screen light doesn't get back until I reboot my computer. I have to set GRUB_DEFAULT to old kernel '4.10.0-38' for no getting this problem. If you need more information feel free to ask ! --- ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: john 2621 F pulseaudio CurrentDesktop: Budgie:GNOME DistroRelease: Ubuntu 17.10 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=997c0c1c-72b4-491d-9dfc-da86f655bcca MachineType: ASUSTeK COMPUTER INC. GL502VSK Package: linux (not installed) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-lowlatency root=UUID=5fe02e3e-86d4-4749-a879-902fc34feda5 ro quiet splash acpi_osi= vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-16.19-lowlatency 4.13.4 RelatedPackageVersions: linux-restricted-modules-4.13.0-16-lowlatency N/A linux-backports-modules-4.13.0-16-lowlatency N/A linux-firmware1.169 Tags: artful Uname: Linux 4.13.0-16-lowlatency x86_64 UpgradeStatus: Upgraded to artful on 2017-11-10 (4 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/28/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GL502VSK.303 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GL502VSK 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.:bvrGL502VSK.303:bd03/28/2017:svnASUSTeKCOMPUTERINC.:pnGL502VSK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL502VSK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: GL dmi.product.name: GL502VSK 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/1731913/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1731913] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1731913/+attachment/5008856/+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/1731913 Title: New kernel 4.13.0-16 is buggy on session lock Status in linux package in Ubuntu: Confirmed Bug description: Hi, I updated my distro from 17.04 to 17.10 in the last week. My 'budgie-desktop' is 10.4. My graphic card is an Nvidia GTX 1070. Since the update, when I lock my session with new kernel, my screen don't wakeup correctly when I try to login again. The screen light is off, but I can hardly distinct login window. I can login, but screen light doesn't get back until I reboot my computer. I have to set GRUB_DEFAULT to old kernel '4.10.0-38' for no getting this problem. If you need more information feel free to ask ! --- ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: john 2621 F pulseaudio CurrentDesktop: Budgie:GNOME DistroRelease: Ubuntu 17.10 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=997c0c1c-72b4-491d-9dfc-da86f655bcca MachineType: ASUSTeK COMPUTER INC. GL502VSK Package: linux (not installed) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-lowlatency root=UUID=5fe02e3e-86d4-4749-a879-902fc34feda5 ro quiet splash acpi_osi= vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-16.19-lowlatency 4.13.4 RelatedPackageVersions: linux-restricted-modules-4.13.0-16-lowlatency N/A linux-backports-modules-4.13.0-16-lowlatency N/A linux-firmware1.169 Tags: artful Uname: Linux 4.13.0-16-lowlatency x86_64 UpgradeStatus: Upgraded to artful on 2017-11-10 (4 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/28/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GL502VSK.303 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GL502VSK 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.:bvrGL502VSK.303:bd03/28/2017:svnASUSTeKCOMPUTERINC.:pnGL502VSK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL502VSK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: GL dmi.product.name: GL502VSK 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/1731913/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1731913] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1731913/+attachment/5008859/+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/1731913 Title: New kernel 4.13.0-16 is buggy on session lock Status in linux package in Ubuntu: Confirmed Bug description: Hi, I updated my distro from 17.04 to 17.10 in the last week. My 'budgie-desktop' is 10.4. My graphic card is an Nvidia GTX 1070. Since the update, when I lock my session with new kernel, my screen don't wakeup correctly when I try to login again. The screen light is off, but I can hardly distinct login window. I can login, but screen light doesn't get back until I reboot my computer. I have to set GRUB_DEFAULT to old kernel '4.10.0-38' for no getting this problem. If you need more information feel free to ask ! --- ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: john 2621 F pulseaudio CurrentDesktop: Budgie:GNOME DistroRelease: Ubuntu 17.10 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=997c0c1c-72b4-491d-9dfc-da86f655bcca MachineType: ASUSTeK COMPUTER INC. GL502VSK Package: linux (not installed) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-lowlatency root=UUID=5fe02e3e-86d4-4749-a879-902fc34feda5 ro quiet splash acpi_osi= vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-16.19-lowlatency 4.13.4 RelatedPackageVersions: linux-restricted-modules-4.13.0-16-lowlatency N/A linux-backports-modules-4.13.0-16-lowlatency N/A linux-firmware1.169 Tags: artful Uname: Linux 4.13.0-16-lowlatency x86_64 UpgradeStatus: Upgraded to artful on 2017-11-10 (4 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/28/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GL502VSK.303 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GL502VSK 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.:bvrGL502VSK.303:bd03/28/2017:svnASUSTeKCOMPUTERINC.:pnGL502VSK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL502VSK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: GL dmi.product.name: GL502VSK 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/1731913/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1731913] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1731913/+attachment/5008860/+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/1731913 Title: New kernel 4.13.0-16 is buggy on session lock Status in linux package in Ubuntu: Confirmed Bug description: Hi, I updated my distro from 17.04 to 17.10 in the last week. My 'budgie-desktop' is 10.4. My graphic card is an Nvidia GTX 1070. Since the update, when I lock my session with new kernel, my screen don't wakeup correctly when I try to login again. The screen light is off, but I can hardly distinct login window. I can login, but screen light doesn't get back until I reboot my computer. I have to set GRUB_DEFAULT to old kernel '4.10.0-38' for no getting this problem. If you need more information feel free to ask ! --- ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: john 2621 F pulseaudio CurrentDesktop: Budgie:GNOME DistroRelease: Ubuntu 17.10 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=997c0c1c-72b4-491d-9dfc-da86f655bcca MachineType: ASUSTeK COMPUTER INC. GL502VSK Package: linux (not installed) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-lowlatency root=UUID=5fe02e3e-86d4-4749-a879-902fc34feda5 ro quiet splash acpi_osi= vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-16.19-lowlatency 4.13.4 RelatedPackageVersions: linux-restricted-modules-4.13.0-16-lowlatency N/A linux-backports-modules-4.13.0-16-lowlatency N/A linux-firmware1.169 Tags: artful Uname: Linux 4.13.0-16-lowlatency x86_64 UpgradeStatus: Upgraded to artful on 2017-11-10 (4 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/28/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GL502VSK.303 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GL502VSK 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.:bvrGL502VSK.303:bd03/28/2017:svnASUSTeKCOMPUTERINC.:pnGL502VSK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL502VSK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: GL dmi.product.name: GL502VSK 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/1731913/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1731913] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1731913/+attachment/5008858/+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/1731913 Title: New kernel 4.13.0-16 is buggy on session lock Status in linux package in Ubuntu: Confirmed Bug description: Hi, I updated my distro from 17.04 to 17.10 in the last week. My 'budgie-desktop' is 10.4. My graphic card is an Nvidia GTX 1070. Since the update, when I lock my session with new kernel, my screen don't wakeup correctly when I try to login again. The screen light is off, but I can hardly distinct login window. I can login, but screen light doesn't get back until I reboot my computer. I have to set GRUB_DEFAULT to old kernel '4.10.0-38' for no getting this problem. If you need more information feel free to ask ! --- ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: john 2621 F pulseaudio CurrentDesktop: Budgie:GNOME DistroRelease: Ubuntu 17.10 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=997c0c1c-72b4-491d-9dfc-da86f655bcca MachineType: ASUSTeK COMPUTER INC. GL502VSK Package: linux (not installed) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-lowlatency root=UUID=5fe02e3e-86d4-4749-a879-902fc34feda5 ro quiet splash acpi_osi= vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-16.19-lowlatency 4.13.4 RelatedPackageVersions: linux-restricted-modules-4.13.0-16-lowlatency N/A linux-backports-modules-4.13.0-16-lowlatency N/A linux-firmware1.169 Tags: artful Uname: Linux 4.13.0-16-lowlatency x86_64 UpgradeStatus: Upgraded to artful on 2017-11-10 (4 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/28/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GL502VSK.303 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GL502VSK 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.:bvrGL502VSK.303:bd03/28/2017:svnASUSTeKCOMPUTERINC.:pnGL502VSK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL502VSK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: GL dmi.product.name: GL502VSK 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/1731913/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1731913] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1731913/+attachment/5008857/+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/1731913 Title: New kernel 4.13.0-16 is buggy on session lock Status in linux package in Ubuntu: Confirmed Bug description: Hi, I updated my distro from 17.04 to 17.10 in the last week. My 'budgie-desktop' is 10.4. My graphic card is an Nvidia GTX 1070. Since the update, when I lock my session with new kernel, my screen don't wakeup correctly when I try to login again. The screen light is off, but I can hardly distinct login window. I can login, but screen light doesn't get back until I reboot my computer. I have to set GRUB_DEFAULT to old kernel '4.10.0-38' for no getting this problem. If you need more information feel free to ask ! --- ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: john 2621 F pulseaudio CurrentDesktop: Budgie:GNOME DistroRelease: Ubuntu 17.10 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=997c0c1c-72b4-491d-9dfc-da86f655bcca MachineType: ASUSTeK COMPUTER INC. GL502VSK Package: linux (not installed) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-lowlatency root=UUID=5fe02e3e-86d4-4749-a879-902fc34feda5 ro quiet splash acpi_osi= vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-16.19-lowlatency 4.13.4 RelatedPackageVersions: linux-restricted-modules-4.13.0-16-lowlatency N/A linux-backports-modules-4.13.0-16-lowlatency N/A linux-firmware1.169 Tags: artful Uname: Linux 4.13.0-16-lowlatency x86_64 UpgradeStatus: Upgraded to artful on 2017-11-10 (4 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/28/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GL502VSK.303 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GL502VSK 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.:bvrGL502VSK.303:bd03/28/2017:svnASUSTeKCOMPUTERINC.:pnGL502VSK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL502VSK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: GL dmi.product.name: GL502VSK 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/1731913/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1730596] Comment bridged from LTC Bugzilla
--- Comment From heinz-werner_se...@de.ibm.com 2017-11-14 07:18 EDT---
Already verified for Xenial - see also comment #4
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1730596
Title:
s390/mm: fix write access check in gup_huge_pmd()
Status in Ubuntu on IBM z Systems:
Fix Committed
Status in linux package in Ubuntu:
Fix Committed
Status in linux source package in Xenial:
Fix Committed
Status in linux source package in Zesty:
Fix Committed
Status in linux source package in Artful:
Fix Committed
Status in linux source package in Bionic:
Fix Committed
Bug description:
== SRU Justification ==
The check for the _SEGMENT_ENTRY_PROTECT bit in gup_huge_pmd() is the
wrong way around. It must not be set for write==1, and not be checked for
write==0. Fix this similar to how it was fixed for ptes long time ago in
commit 25591b0 ("[S390] fix get_user_pages_fast").
One impact of this bug would be unnecessarily using the gup slow path for
write==0 on r/w mappings. A potentially more severe impact would be that
gup_huge_pmd() will succeed for write==1 on r/o mappings.
This bug is fixed by mainline commit ba385c0594, which is in mainline
as of v4.14-rc2. It was also cc'd to upstream stable. It has already
been accepted in upstream v4.13.y, so Artful and Bionic have the fix
via the 4.13.5 stable updates.
== Fix ==
commit ba385c0594e723d41790ecfb12c610e6f90c7785
Author: Gerald Schaefer
Date: Mon Sep 18 16:51:51 2017 +0200
s390/mm: fix write access check in gup_huge_pmd()
== Regression Potential ==
This patch is specific to s390. It has also been accepted by upstream
stable, so additional upstream review has been done.
Addl information
Problem: The check for the _SEGMENT_ENTRY_PROTECT bit in
gup_huge_pmd() is the wrong way around. It must not be set
for write==1, and not be checked for write==0. Allowing
write==1 with protection bit set, instead of breaking out
to the slow path, will result in a missing faultin_page()
to clear the protection bit (for valid writable mappings),
and the async I/O write operation will fail to write to
such a mapping.
Solution: Fix it by correctly checking the protection bit like it is
also done in gup_pte_range() and gup_huge_pud().
Reproduction: Async I/O workload on buffers that are mapped as transparent
hugepages.
Upstream-ID: ba385c0594e723d41790ecfb12c610e6f90c7785
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1730596/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1730596] Re: s390/mm: fix write access check in gup_huge_pmd()
** Tags removed: verification-needed-xenial
** Tags added: verification-done-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/1730596
Title:
s390/mm: fix write access check in gup_huge_pmd()
Status in Ubuntu on IBM z Systems:
Fix Committed
Status in linux package in Ubuntu:
Fix Committed
Status in linux source package in Xenial:
Fix Committed
Status in linux source package in Zesty:
Fix Committed
Status in linux source package in Artful:
Fix Committed
Status in linux source package in Bionic:
Fix Committed
Bug description:
== SRU Justification ==
The check for the _SEGMENT_ENTRY_PROTECT bit in gup_huge_pmd() is the
wrong way around. It must not be set for write==1, and not be checked for
write==0. Fix this similar to how it was fixed for ptes long time ago in
commit 25591b0 ("[S390] fix get_user_pages_fast").
One impact of this bug would be unnecessarily using the gup slow path for
write==0 on r/w mappings. A potentially more severe impact would be that
gup_huge_pmd() will succeed for write==1 on r/o mappings.
This bug is fixed by mainline commit ba385c0594, which is in mainline
as of v4.14-rc2. It was also cc'd to upstream stable. It has already
been accepted in upstream v4.13.y, so Artful and Bionic have the fix
via the 4.13.5 stable updates.
== Fix ==
commit ba385c0594e723d41790ecfb12c610e6f90c7785
Author: Gerald Schaefer
Date: Mon Sep 18 16:51:51 2017 +0200
s390/mm: fix write access check in gup_huge_pmd()
== Regression Potential ==
This patch is specific to s390. It has also been accepted by upstream
stable, so additional upstream review has been done.
Addl information
Problem: The check for the _SEGMENT_ENTRY_PROTECT bit in
gup_huge_pmd() is the wrong way around. It must not be set
for write==1, and not be checked for write==0. Allowing
write==1 with protection bit set, instead of breaking out
to the slow path, will result in a missing faultin_page()
to clear the protection bit (for valid writable mappings),
and the async I/O write operation will fail to write to
such a mapping.
Solution: Fix it by correctly checking the protection bit like it is
also done in gup_pte_range() and gup_huge_pud().
Reproduction: Async I/O workload on buffers that are mapped as transparent
hugepages.
Upstream-ID: ba385c0594e723d41790ecfb12c610e6f90c7785
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1730596/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1731264] Re: linux: 4.4.0-101.124 -proposed tracker
** Changed in: kernel-sru-workflow/snap-release-to-beta Status: New => Confirmed ** Changed in: kernel-sru-workflow/snap-release-to-edge Status: New => Confirmed ** Changed in: kernel-sru-workflow/snap-release-to-beta Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/snap-release-to-edge Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/snap-certification-testing Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1731264 Title: linux: 4.4.0-101.124 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow snap-certification-testing series: Confirmed Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: 1731266 derivatives: -- swm properties -- boot-testing-requested: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1731264/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1728244] Re: Touchpad stops working after reboot on Apollo Lake
@mogio, this probably is not important but I wanted to record the difference between the BIOS version in your EZbook and mine. Yours has a slightly new version NHNAUHN05 [0.00] DMI: Jumper EZbook/P313R, BIOS JUMPER10x.P8.WP313R.NHNAUHN02 08/07/2017 [0.00] DMI: Jumper EZbook/P313R, BIOS JUMPER2x.P8.WP313R.NHNAUHN05 09/30/2017 Note: when the problem happens for me, nothing works. When the problem does not happen everything works including the touchpad buttons. I never have a problem of only the buttons not working. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1728244 Title: Touchpad stops working after reboot on Apollo Lake Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Bug description: On the Jumper EZBook 3 Pro (V4) laptop, using an Apollo Lake N3450 processor, if you install Ubuntu 17.10 (or less) with isorespin and use rEFInd as bootloader (this is the only way to get linux booting on this laptop) everything works out of the box, but after a reboot or two the touchpad stops working. Both in Ubuntu and Windows 10. The only way to restore functionality is to boot from usb key ubuntu 17.10 respined, or disassemble laptop and detach-reattach battery cable. This is mesg | grep i2c_hid: [ 2056.460636] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (27/34) [ 3077.604699] i2c_hid i2c-SYNA3602:00: failed to reset device. [ 3077.605473] dpm_run_callback(): i2c_hid_resume+0x0/0xe0 [i2c_hid] returns -61 [ 3080.468156] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (27/34) uname -rvps Linux 4.10.0-32-generic #36~16.04.1-Ubuntu SMP Wed Aug 9 09:19:02 UTC 2017 x86_64 There has to be a bug in the kernel. Any way to avoid this? To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1728244/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1731264] Re: linux: 4.4.0-101.124 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1731264 Title: linux: 4.4.0-101.124 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow snap-certification-testing series: Confirmed Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: 1731266 derivatives: -- swm properties -- boot-testing-requested: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1731264/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1690085] Re: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks
Almost 1 month of uptime, it looks solved. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1690085 Title: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Bug description: Hi, We aregetting various kernel crash on a pretty new config. We're using Ryzen 1800X CPU with X370 Gaming Pro Carbon MB (7A32V1) using latest BIOS available (1.52) We are running Ubuntu 17.04 (amd64), we've tried different kernel version, native one and releases from http://kernel.ubuntu.com/~kernel-ppa/mainline/ too. Tested kernel version: native 17.04 kernel 4.10.15 Issues are the same, we're getting random freeze on the machine. Here is kern.log entry when happening : May 10 22:41:56 dev2 kernel: [24366.186246] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:41:56 dev2 kernel: [24366.187618] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=913449 May 10 22:41:56 dev2 kernel: [24366.188977] (detected by 12, t=1860207 jiffies, g=10001, c=1, q=4656) May 10 22:41:56 dev2 kernel: [24366.190344] Task dump for CPU 0: May 10 22:41:56 dev2 kernel: [24366.190345] swapper/0 R running task 0 0 0 0x0008 May 10 22:41:56 dev2 kernel: [24366.190348] Call Trace: May 10 22:41:56 dev2 kernel: [24366.190354] ? native_safe_halt+0x6/0x10 May 10 22:41:56 dev2 kernel: [24366.190355] ? default_idle+0x20/0xd0 May 10 22:41:56 dev2 kernel: [24366.190358] ? arch_cpu_idle+0xf/0x20 May 10 22:41:56 dev2 kernel: [24366.190360] ? default_idle_call+0x23/0x30 May 10 22:41:56 dev2 kernel: [24366.190362] ? do_idle+0x16f/0x200 May 10 22:41:56 dev2 kernel: [24366.190364] ? cpu_startup_entry+0x71/0x80 May 10 22:41:56 dev2 kernel: [24366.190366] ? rest_init+0x77/0x80 May 10 22:41:56 dev2 kernel: [24366.190368] ? start_kernel+0x464/0x485 May 10 22:41:56 dev2 kernel: [24366.190369] ? early_idt_handler_array+0x120/0x120 May 10 22:41:56 dev2 kernel: [24366.190371] ? x86_64_start_reservations+0x24/0x26 May 10 22:41:56 dev2 kernel: [24366.190372] ? x86_64_start_kernel+0x14d/0x170 May 10 22:41:56 dev2 kernel: [24366.190373] ? start_cpu+0x14/0x14 May 10 22:44:56 dev2 kernel: [24546.188093] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:44:56 dev2 kernel: [24546.189461] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=935027 May 10 22:44:56 dev2 kernel: [24546.190823] (detected by 14, t=1905212 jiffies, g=10001, c=1, q=4740) May 10 22:44:56 dev2 kernel: [24546.192191] Task dump for CPU 0: May 10 22:44:56 dev2 kernel: [24546.192192] swapper/0 R running task 0 0 0 0x0008 May 10 22:44:56 dev2 kernel: [24546.192195] Call Trace: May 10 22:44:56 dev2 kernel: [24546.192199] ? native_safe_halt+0x6/0x10 May 10 22:44:56 dev2 kernel: [24546.192201] ? default_idle+0x20/0xd0 May 10 22:44:56 dev2 kernel: [24546.192203] ? arch_cpu_idle+0xf/0x20 May 10 22:44:56 dev2 kernel: [24546.192204] ? default_idle_call+0x23/0x30 May 10 22:44:56 dev2 kernel: [24546.192206] ? do_idle+0x16f/0x200 May 10 22:44:56 dev2 kernel: [24546.192208] ? cpu_startup_entry+0x71/0x80 May 10 22:44:56 dev2 kernel: [24546.192210] ? rest_init+0x77/0x80 May 10 22:44:56 dev2 kernel: [24546.192211] ? start_kernel+0x464/0x485 May 10 22:44:56 dev2 kernel: [24546.192213] ? early_idt_handler_array+0x120/0x120 May 10 22:44:56 dev2 kernel: [24546.192214] ? x86_64_start_reservations+0x24/0x26 May 10 22:44:56 dev2 kernel: [24546.192215] ? x86_64_start_kernel+0x14d/0x170 May 10 22:44:56 dev2 kernel: [24546.192217] ? start_cpu+0x14/0x14 Depending on the kernel version, we've got NMI watchdog errors related to CPU stuck (mentioning the CPU core id, which is random). Crash is happening randomly, but in general after some hours (3-4h). Now, we've installed kernel 4.11.0-041100-generic #201705041534 this morning and waiting for crash... For now, the machine is not "used", at least, it's not CPU stressed... Thanks --- ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-05-09 (1 days ago) InstallationMedia: Ubuntu-Server 17.04 "Zesty Zapus" - Release amd64 (20170412) Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash Tags: zesty Uname: Linux 4.11.0-041100-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1690085/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Po
[Kernel-packages] [Bug 1069350] Re: suspicious /.rpmdb root directory
This also happened on Ubuntu 16.04 in 2017.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dkms in Ubuntu.
https://bugs.launchpad.net/bugs/1069350
Title:
suspicious /.rpmdb root directory
Status in RPM:
Opinion
Status in dkms package in Ubuntu:
Confirmed
Status in rpm package in Ubuntu:
Fix Released
Status in dkms source package in Trusty:
Confirmed
Status in rpm source package in Trusty:
Confirmed
Status in dkms package in Debian:
New
Status in rpm package in Debian:
Fix Released
Bug description:
I have the following directory structure on my system which conflicts
to the LSB standard:
ls -ld /.rpmdb/{,*}
drwxr-xr-x 2 root root 4096 Okt 21 2011 /.rpmdb/
-rw-r--r-- 1 root root 8192 Okt 21 2011 /.rpmdb/Basenames
-rw-r--r-- 1 root root 8192 Okt 21 2011 /.rpmdb/Conflictname
-rw-r--r-- 1 root root24576 Apr 27 00:52 /.rpmdb/__db.001
-rw-r--r-- 1 root root 4096000 Apr 27 00:52 /.rpmdb/__db.002
-rw-r--r-- 1 root root 83894272 Apr 27 00:52 /.rpmdb/__db.003
-rw-r--r-- 1 root root 811008 Apr 27 00:52 /.rpmdb/__db.004
-rw-r--r-- 1 root root 8192 Okt 21 2011 /.rpmdb/Dirnames
-rw-r--r-- 1 root root 8192 Okt 21 2011 /.rpmdb/Group
-rw-r--r-- 1 root root 8192 Okt 21 2011 /.rpmdb/Installtid
-rw-r--r-- 1 root root 8192 Okt 21 2011 /.rpmdb/Name
-rw-r--r-- 1 root root 8192 Okt 21 2011 /.rpmdb/Obsoletename
-rw-r--r-- 1 root root12288 Okt 21 2011 /.rpmdb/Packages
-rw-r--r-- 1 root root 8192 Okt 21 2011 /.rpmdb/Providename
-rw-r--r-- 1 root root 8192 Okt 21 2011 /.rpmdb/Requirename
-rw-r--r-- 1 root root 8192 Okt 21 2011 /.rpmdb/Sha1header
-rw-r--r-- 1 root root 8192 Okt 21 2011 /.rpmdb/Sigmd5
-rw-r--r-- 1 root root 8192 Okt 21 2011 /.rpmdb/Triggername
Afaik, this directory belongs to rpm or alien. Maybe it appears
because of a lack of environment variables (e.g. $HOME not set) in
particular situations.
As you can see in the listing, the directory is not used frequently,
but I'm not sure if it's save to delete it. Maybe the problem is
already solved in the current version of ubuntu (at last the time the
files were touched I was running Ubuntu 11.10), but I think it's
important to have this bug registered so other users can find it.
There is an active thread about it at ubuntuforums:
http://ubuntuforums.org/showthread.php?t=1864423
To manage notifications about this bug go to:
https://bugs.launchpad.net/rpm/+bug/1069350/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1731269] Re: linux: 4.10.0-40.44 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1731269 Title: linux: 4.10.0-40.44 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: In Progress Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Zesty: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: 1731270 derivatives: -- swm properties -- boot-testing-requested: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1731269/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1731264] Re: linux: 4.4.0-101.124 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/security-signoff Assignee: Canonical Security Team (canonical-security) => Steve Beattie (sbeattie) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1731264 Title: linux: 4.4.0-101.124 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-certification-testing series: Confirmed Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: 1731266 derivatives: -- swm properties -- boot-testing-requested: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1731264/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1722478] Re: Two-finger scrolling no longer works after resuming from suspend
Hi, this one is working fine for me! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1722478 Title: Two-finger scrolling no longer works after resuming from suspend Status in linux package in Ubuntu: Incomplete Bug description: I own a Thinkpad T440p onto which I have had Debian 9 running without hardware issues. I have recently installed Ubuntu 17.10 final beta to test it out, but two-finger scrolling does not work at the moment. It used to work out-of-the-box from the final beta iso, but a subsequent update broke it. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-12-generic 4.13.0-12.13 [modified: boot/vmlinuz-4.13.0-12-generic] ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ghislain 10620 F pulseaudio /dev/snd/controlC0: ghislain 10620 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Oct 10 09:20:01 2017 HibernationDevice: RESUME=UUID=ae4cca1e-80ef-4a1e-87e3-0a860b49492e InstallationDate: Installed on 2017-10-05 (4 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) MachineType: LENOVO 20AN00C1UK ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-12-generic root=/dev/mapper/doc1485--lap--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-12-generic N/A linux-backports-modules-4.13.0-12-generic N/A linux-firmware 1.169 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/31/2016 dmi.bios.vendor: LENOVO dmi.bios.version: GLET83WW (2.37 ) dmi.board.asset.tag: Not Available dmi.board.name: 20AN00C1UK dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGLET83WW(2.37):bd03/31/2016:svnLENOVO:pn20AN00C1UK:pvrThinkPadT440p:rvnLENOVO:rn20AN00C1UK:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T440p dmi.product.name: 20AN00C1UK dmi.product.version: ThinkPad T440p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1722478/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1729280] Re: linux-aws: 4.4.0-1040.49 -proposed tracker
** Changed in: kernel-sru-workflow/snap-release-to-candidate Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1729280 Title: linux-aws: 4.4.0-1040.49 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-certification-testing series: Invalid Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Confirmed Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1731264 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1729280/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1728244] Re: Touchpad stops working after reboot on Apollo Lake
@brad try this Kernel: http://kernel.ubuntu.com/~kernel- ppa/mainline/v4.14-rc7/ Is your BIOS setting Default? (I just changed SSD instead of HDD into SATA port settings). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1728244 Title: Touchpad stops working after reboot on Apollo Lake Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Bug description: On the Jumper EZBook 3 Pro (V4) laptop, using an Apollo Lake N3450 processor, if you install Ubuntu 17.10 (or less) with isorespin and use rEFInd as bootloader (this is the only way to get linux booting on this laptop) everything works out of the box, but after a reboot or two the touchpad stops working. Both in Ubuntu and Windows 10. The only way to restore functionality is to boot from usb key ubuntu 17.10 respined, or disassemble laptop and detach-reattach battery cable. This is mesg | grep i2c_hid: [ 2056.460636] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (27/34) [ 3077.604699] i2c_hid i2c-SYNA3602:00: failed to reset device. [ 3077.605473] dpm_run_callback(): i2c_hid_resume+0x0/0xe0 [i2c_hid] returns -61 [ 3080.468156] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (27/34) uname -rvps Linux 4.10.0-32-generic #36~16.04.1-Ubuntu SMP Wed Aug 9 09:19:02 UTC 2017 x86_64 There has to be a bug in the kernel. Any way to avoid this? To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1728244/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1726061] Re: Inspiron 5565 suspend issues after 17.10 upgrade
Upon initially booting either 4.13.11 or 4.14.0 I see 1 in active_count for ACAD, and zeros elsewhere. When 4.14.0 has immediately resumed from suspend and shows additional events from the lid and the power button, I have not touched either of those in the course of attempting to suspend. Attached /proc/acpi/wakeup from 4.14.0 ; in 4.13.11 it seems identical. 4.13.11 has been suspending OK but today it is not -- instead it behaves exactly like 4.14.0 . ** Attachment added: "acpi_wakeup_4140" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1726061/+attachment/5008903/+files/acpi_wakeup_4140 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1726061 Title: Inspiron 5565 suspend issues after 17.10 upgrade Status in linux package in Ubuntu: Confirmed Bug description: On my Inspiron 5565, 17.10 seems to work fairly well, unless I try to suspend. Suspend shuts off the display but doesn't seem to actually shut off the CPU -- fans still run. When I move the mouse the display comes back on but upon entering my password sometimes the session crashes and I am dumped back to the login screen; sometimes the session is still there but wifi is either disabled (all wifi-related menu items gone) or visible (with question mark) but non-functional. In any case once I have suspended I cannot shut down or reboot any way other than the hard way, by holding the power button for several seconds. Doesn't seem to matter whether I am using X or Wayland. Suspend works mostly fine if I choose the 4.10 kernel from GRUB... although I am prompted for login more times than necessary on resume. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-16-generic 4.13.0-16.19 ProcVersionSignature: Ubuntu 4.10.0-37.41-generic 4.10.17 Uname: Linux 4.10.0-37-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: aaron 2489 F pulseaudio /dev/snd/controlC1: aaron 2489 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Oct 22 12:22:13 2017 HibernationDevice: RESUME=UUID=3cc55560-1886-446c-8d60-15136ee14d32 InstallationDate: Installed on 2016-12-25 (301 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: Dell Inc. Inspiron 5565 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-37-generic.efi.signed root=UUID=c30eb880-24e4-41af-9203-feff0ab69c8c ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.10.0-37-generic N/A linux-backports-modules-4.10.0-37-generic N/A linux-firmware 1.169 SourcePackage: linux UpgradeStatus: Upgraded to artful on 2017-10-22 (0 days ago) dmi.bios.date: 07/20/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.2 dmi.board.name: 0RVKF9 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.0.2 dmi.modalias: dmi:bvnDellInc.:bvr1.0.2:bd07/20/2016:svnDellInc.:pnInspiron5565:pvr1.0.2:rvnDellInc.:rn0RVKF9:rvrA00:cvnDellInc.:ct10:cvr1.0.2: dmi.product.name: Inspiron 5565 dmi.product.version: 1.0.2 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1726061/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1728244] Re: Touchpad stops working after reboot on Apollo Lake
Yes, I reloaded default BIOS settings and always use this. Btw, never use BIOS setting OS "linux", it can freeze the screen and keyboard and you will have to disconnect the battery to reset it. I will try that kernel. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1728244 Title: Touchpad stops working after reboot on Apollo Lake Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Bug description: On the Jumper EZBook 3 Pro (V4) laptop, using an Apollo Lake N3450 processor, if you install Ubuntu 17.10 (or less) with isorespin and use rEFInd as bootloader (this is the only way to get linux booting on this laptop) everything works out of the box, but after a reboot or two the touchpad stops working. Both in Ubuntu and Windows 10. The only way to restore functionality is to boot from usb key ubuntu 17.10 respined, or disassemble laptop and detach-reattach battery cable. This is mesg | grep i2c_hid: [ 2056.460636] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (27/34) [ 3077.604699] i2c_hid i2c-SYNA3602:00: failed to reset device. [ 3077.605473] dpm_run_callback(): i2c_hid_resume+0x0/0xe0 [i2c_hid] returns -61 [ 3080.468156] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (27/34) uname -rvps Linux 4.10.0-32-generic #36~16.04.1-Ubuntu SMP Wed Aug 9 09:19:02 UTC 2017 x86_64 There has to be a bug in the kernel. Any way to avoid this? To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1728244/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1728244] Re: Touchpad stops working after reboot on Apollo Lake
@mogio, It is possible your failure could be caused by something different than mine. In your logs there is one message I do not see in either my working/not-working logs... "i2c_hid i2c-SYNA3602:00: i2c-SYNA3602:00 supply vdd not found, using dummy regulator" I don't know what the significance of this message is. There is another Arch user with this same log message here... https://bbs.archlinux.org/viewtopic.php?pid=1747409#p1747409 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1728244 Title: Touchpad stops working after reboot on Apollo Lake Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Bug description: On the Jumper EZBook 3 Pro (V4) laptop, using an Apollo Lake N3450 processor, if you install Ubuntu 17.10 (or less) with isorespin and use rEFInd as bootloader (this is the only way to get linux booting on this laptop) everything works out of the box, but after a reboot or two the touchpad stops working. Both in Ubuntu and Windows 10. The only way to restore functionality is to boot from usb key ubuntu 17.10 respined, or disassemble laptop and detach-reattach battery cable. This is mesg | grep i2c_hid: [ 2056.460636] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (27/34) [ 3077.604699] i2c_hid i2c-SYNA3602:00: failed to reset device. [ 3077.605473] dpm_run_callback(): i2c_hid_resume+0x0/0xe0 [i2c_hid] returns -61 [ 3080.468156] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (27/34) uname -rvps Linux 4.10.0-32-generic #36~16.04.1-Ubuntu SMP Wed Aug 9 09:19:02 UTC 2017 x86_64 There has to be a bug in the kernel. Any way to avoid this? To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1728244/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1726061] Re: Inspiron 5565 suspend issues after 17.10 upgrade
Perhaps this is no longer a kernel issue or at least no longer a regression. I am getting the same behavior with 4.14 and 4.13.11 and even the kernel from 17.04 . Normally when I am suspending at the end of the day I first close the laptop lid, then choose suspend from the menu on the external monitor... and that seems to work. Not sure how long the suspend menu has not worked with the laptop lid left open but today I still get it if I boot 17.04 from a different partition. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1726061 Title: Inspiron 5565 suspend issues after 17.10 upgrade Status in linux package in Ubuntu: Confirmed Bug description: On my Inspiron 5565, 17.10 seems to work fairly well, unless I try to suspend. Suspend shuts off the display but doesn't seem to actually shut off the CPU -- fans still run. When I move the mouse the display comes back on but upon entering my password sometimes the session crashes and I am dumped back to the login screen; sometimes the session is still there but wifi is either disabled (all wifi-related menu items gone) or visible (with question mark) but non-functional. In any case once I have suspended I cannot shut down or reboot any way other than the hard way, by holding the power button for several seconds. Doesn't seem to matter whether I am using X or Wayland. Suspend works mostly fine if I choose the 4.10 kernel from GRUB... although I am prompted for login more times than necessary on resume. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-16-generic 4.13.0-16.19 ProcVersionSignature: Ubuntu 4.10.0-37.41-generic 4.10.17 Uname: Linux 4.10.0-37-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: aaron 2489 F pulseaudio /dev/snd/controlC1: aaron 2489 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Oct 22 12:22:13 2017 HibernationDevice: RESUME=UUID=3cc55560-1886-446c-8d60-15136ee14d32 InstallationDate: Installed on 2016-12-25 (301 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: Dell Inc. Inspiron 5565 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-37-generic.efi.signed root=UUID=c30eb880-24e4-41af-9203-feff0ab69c8c ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.10.0-37-generic N/A linux-backports-modules-4.10.0-37-generic N/A linux-firmware 1.169 SourcePackage: linux UpgradeStatus: Upgraded to artful on 2017-10-22 (0 days ago) dmi.bios.date: 07/20/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.2 dmi.board.name: 0RVKF9 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.0.2 dmi.modalias: dmi:bvnDellInc.:bvr1.0.2:bd07/20/2016:svnDellInc.:pnInspiron5565:pvr1.0.2:rvnDellInc.:rn0RVKF9:rvrA00:cvnDellInc.:ct10:cvr1.0.2: dmi.product.name: Inspiron 5565 dmi.product.version: 1.0.2 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1726061/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1721455] Re: Support Dell Wireless DW5819/5818 WWAN devices
** Changed in: linux (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1721455 Title: Support Dell Wireless DW5819/5818 WWAN devices Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Bug description: [Impact] Dell Wireless 5819/5818 devices are re-branded Sierra Wireless MC74 series which will by default boot with vid 0x413c and pid's 0x81cf, 0x81d0, 0x81d1,0x81d2. [Fix] This patch has already been submitted upstream, reviewed and applied by linux-usb serial maintainer. [PATCH] USB: serial: qcserial: add Dell DW5818, DW581 (See: https://marc.info/?l=linux-usb&m=150703788328773&w=2) However, to meet Dell Edge Gateway 300x delivery schedule, a sauce patch is being submitted to Xenial SRU. [Regression Potential] The patch adds USB VID's/PID's to the usb qcserial driver. Regression potential is minimal. [Testing] A test kernel (snap) with this patch was verified by the ODM, no issues were reported. This bug is used for tracking purposes, please do not triage. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1721455/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1729674] Re: TB16 dock ethernet corrupts data with hw checksum silently failing
@Dave: I was glancing at r8152 driver and notice that it has some special handling for ipv6. Is this issue reproducing only in ipv6 for you? https://github.com/torvalds/linux/commit/6128d1bb30748d0ff56a63898d14f312126e404c -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1729674 Title: TB16 dock ethernet corrupts data with hw checksum silently failing Status in Dell Sputnik: Triaged Status in linux package in Ubuntu: In Progress Bug description: It looks like TCP rx and tx checksum offloading is broken on the TB16 dock's ethernet adapter. For example downloading a large file such as the Ubuntu ISO, and then running an md5sum on it yields the incorrect md5sum. This is because rx-checksumming: on tx-checksumming: on and both set to on by default. Running sudo ethtool -K tx off rx off, allows the download to complete correctly. This is very bad since this can cause very bad untrustworthy behavior. This was conducted using an Dell Precision 5520 on Ubuntu 16.04+linux- generic-hwe-16.04-edge. Thank you To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1729674/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1727331] Re: NMI watchdog: BUG: soft lockup on Guest upon boot (KVM)
Mailing list thread for SRU request: https://lists.ubuntu.com/archives/kernel-team/2017-November/088038.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1727331 Title: NMI watchdog: BUG: soft lockup on Guest upon boot (KVM) Status in The Ubuntu-power-systems project: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Bug description: == SRU Justification == Xenial does not include the patch: "KVM: PPC: Book3S: Treat VTB as a per-subcore register, not per-thread", which is commit 88b02cf97bb7 in the upstream Linux kernel repository. The symptom of not having this patch is that guests running with threads > 1 (that is, in SMT2, SMT4 or SMT8 mode) can give spurious soft-lockup messages when they are not in fact locked up, if the guest kernel uses the VTB (virtual timebase) register in its softlockup detector code. IBM provided this backport of commit 88b02cf97bb7. == Fix == commit 88b02cf97bb7e742db3e31671d54177e3e19fd89 Author: Paul Mackerras Date: Thu Sep 15 13:42:52 2016 +1000 KVM: PPC: Book3S: Treat VTB as a per-subcore register, not per- thread == Regression Potential == This patch is specific to powerpc. It was provided by and tested by IBM. Environment: Host OS: Ubuntu 16.04 (4.4.0-97-generic) Guest OS: Ubuntu 16.04 Host is running NovaLink and GPFS. Guest gets filesystem from gpfs cluster. Issue: While booting the guest OS went into recovery. dmesg shows CPU soft lockup. This issue is easily recreatable when multiple VMs (about 10) are being started simultaneously. ... - Paul Mackerras - 2017-10-24 00:42:25 == Looking at kernel sources: The Ubuntu host kernel (4.4.0-97) does not include the patch "KVM: PPC: Book3S: Treat VTB as a per-subcore register, not per-thread", which is commit 88b02cf97bb7 in the upstream Linux kernel repository. The symptom of not having this patch is that guests running with threads > 1 (that is, in SMT2, SMT4 or SMT8 mode) can give spurious soft-lockup messages when they are not in fact locked up, if the guest kernel uses the VTB (virtual timebase) register in its softlockup detector code. This is a backport of commit 88b02cf97bb7 from the upstream Linux kernel repository to the Ubuntu 4.4 kernel. It is the fix for the problem of seeing spurious soft lockup messages in guests running in an SMT mode greater than 1. These tests were run on a system with 20 cores. Each VM had 1 core and 4 threads (SMT=4). It is working very well with this patch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1727331/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1731467] Re: Cannot pair BLE remote devices when using combo BT SoC
** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1731467 Title: Cannot pair BLE remote devices when using combo BT SoC Status in bluez package in Ubuntu: In Progress Status in linux package in Ubuntu: New Bug description: It has been observed that sometimes it is not possible to pair with BLE remote devices when the host system is using combo (WiFi + BT) chip. The root cause of the disconnection has been identified as coming from the internal to bluez timeout. If bluez does not hear any reply from for two seconds the link is automagically disconnected. The reason fro the silence is not however a failure of the remote device but quite often a delay in the WiFi/BT combo driver that causes the packages not to reach the bluez stack. [Impact] Not possible to pair BLE remote devices such as sensors and such with Ubuntu when the host system uses BT+WiFi combo SoC. The connection attempt is disturbed with a timeout. [Fix] It has been fixed by increasing the timeout value from 2 seconds to 4 seconds. It is enough for the events to reach the stack (measured that it takes between 3 and 3.5 seconds). [Testcase] Tested with the device that failed to connect to Ubuntu Core gateway. It fails w/o the patch, it connects just fine with the patch applied. [Regression Potential] Very small. The increased timeout is taken into consideration only for new and scan report triggered connections. It will not make any already working device to fail to pair. [Other Info] The bug has been discussed and fixed here: https://marc.info/?l=linux-bluetooth&m=150824844606937&w=2 [Patch] https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth- next.git/commit/?id=1f01d8be0e6a04bd682a55f6d50c14c1679e7571 The patch has been accepted by the upstream and will be a part of the next kernel release. Currently in the bluetooth-next tree. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1731467/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1710019] Re: support GICv3 ITS save/restore & migration
Uploaded qemu_2.8+dfsg-3ubuntu2.8 to unapproved. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1710019 Title: support GICv3 ITS save/restore & migration Status in linux package in Ubuntu: In Progress Status in qemu package in Ubuntu: Fix Released Status in linux source package in Xenial: Won't Fix Status in qemu source package in Xenial: Won't Fix Status in linux source package in Zesty: In Progress Status in qemu source package in Zesty: In Progress Status in linux source package in Artful: In Progress Status in qemu source package in Artful: Fix Released Bug description: [Impact] Virtual machines on GICv3-based ARM systems cannot be saved/restored or migrated. This feature was added in QEMU 2.10. [Test Case] ubuntu@grotrian:~$ sudo virsh save 7936-0 7936-0.sav Domain 7936-0 saved to 7936-0.sav ubuntu@grotrian:~$ sudo virsh restore 7396-0.sav error: Failed to restore domain from 7396-0.sav error: operation failed: job: unexpectedly failed ubuntu@grotrian:~$ sudo tail -3 /var/log/libvirt/qemu/7936-0.log 2017-08-10T21:26:38.217427Z qemu-system-aarch64: State blocked by non-migratable device 'arm_gicv3_its' 2017-08-10T21:26:38.217565Z qemu-system-aarch64: load of migration failed: Invalid argument 2017-08-10 21:26:38.217+: shutting down, reason=failed [Regression Risk] The kernel changes are restricted to ARM, minimizing the regression risk on other architectures. Other than one minor offset adjustment, all patches are clean cherry-picks from upstream. Tested on Cavium ThunderX and Qualcomm Centriq. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1710019/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1729010] Re: USB hub stops working after suspend(s?)
It did not occur on previous ubuntu releases, and didn't occur during the artful dev cycle either. It seems to be on a suspend-by-suspend basis: after reproducing, another suspend cycle seems to "fix" it at least some of the time. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1729010 Title: USB hub stops working after suspend(s?) Status in linux package in Ubuntu: Confirmed Bug description: On initial boot, my usb hub works fine, but after a (series of?) suspends, I stop being able to see devices that are plugged into it. journalctl output on plugging it in: Oct 31 07:08:36 spiny kernel: usb 1-1: new high-speed USB device number 21 using xhci_hcd Oct 31 07:08:36 spiny kernel: usb 1-1: New USB device found, idVendor=0409, idProduct=005a Oct 31 07:08:36 spiny kernel: usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0 Oct 31 07:08:36 spiny kernel: hub 1-1:1.0: USB hub found Oct 31 07:08:36 spiny kernel: hub 1-1:1.0: 4 ports detected Oct 31 07:08:36 spiny kernel: [UFW BLOCK] IN=wlp3s0 OUT= MAC= SRC=fe80::::a299:9bff:fe17:9047 DST=ff02:::::::0001 LEN=64 TC=0 HOPLIMIT=1 FLOWLBL=32325 PROTO=UDP SPT=8612 DPT=8612 LEN=24 Oct 31 07:08:36 spiny kernel: usb 1-1.1: new high-speed USB device number 22 using xhci_hcd Oct 31 07:08:36 spiny kernel: usb 1-1.1: New USB device found, idVendor=0b95, idProduct=772a Oct 31 07:08:36 spiny kernel: usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Oct 31 07:08:36 spiny kernel: usb 1-1.1: Product: AX88x72A Oct 31 07:08:36 spiny kernel: usb 1-1.1: Manufacturer: ASIX Elec. Corp. Oct 31 07:08:36 spiny kernel: usb 1-1.1: SerialNumber: 47EDE2 Oct 31 07:08:37 spiny kernel: asix 1-1.1:1.0 eth0: register 'asix' at usb-:00:14.0-1.1, ASIX AX88772 USB 2.0 Ethernet, 00:50:b6:47:ed:e2 Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.0438] manager: (eth0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/7) Oct 31 07:08:37 spiny mtp-probe[13207]: checking bus 1, device 22: "/sys/devices/pci:00/:00:14.0/usb1/1-1/1-1.1" Oct 31 07:08:37 spiny mtp-probe[13207]: bus: 1, device: 22 was not an MTP device Oct 31 07:08:37 spiny systemd-udevd[13206]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable. Oct 31 07:08:37 spiny kernel: asix 1-1.1:1.0 enx0050b647ede2: renamed from eth0 Oct 31 07:08:37 spiny pkexec[13215]: pam_unix(polkit-1:session): session opened for user root by (uid=1000) Oct 31 07:08:37 spiny pkexec[13215]: jbarnett: Executing command [USER=root] [TTY=unknown] [CWD=/home/jbarnett] [COMMAND=/usr/lib/gnome-settings-daemon/gsd-backlight-helper --set-brightness 31] Oct 31 07:08:37 spiny pkexec[13214]: gdm: Error executing command as another user: Not authorized [USER=root] [TTY=unknown] [CWD=/var/lib/gdm3] [COMMAND=/usr/lib/gnome-settings-daemon/gsd-backlight-helper --set-brightness 48] Oct 31 07:08:37 spiny org.gnome.SettingsDaemon.Power.desktop[2273]: Error executing command as another user: Not authorized Oct 31 07:08:37 spiny org.gnome.SettingsDaemon.Power.desktop[2273]: This incident has been reported. Oct 31 07:08:37 spiny systemd-networkd[1119]: eth0: Renamed to enx0050b647ede2 Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.1066] device (eth0): interface index 10 renamed iface from 'eth0' to 'enx0050b647ede2' Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.1214] devices added (path: /sys/devices/pci:00/:00:14.0/usb1/1-1/1-1.1/1-1.1:1.0/net/enx0050b647ede2, iface: enx0050b647ede2) Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.1214] device added (path: /sys/devices/pci:00/:00:14.0/usb1/1-1/1-1.1/1-1.1:1.0/net/enx0050b647ede2, iface: enx0050b647ede2): no ifupdown configuration found. Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.1217] device (enx0050b647ede2): state change: unmanaged -> unavailable (reason 'managed', internal state 'external') Oct 31 07:08:37 spiny kernel: IPv6: ADDRCONF(NETDEV_UP): enx0050b647ede2: link is not ready Oct 31 07:08:37 spiny kernel: IPv6: ADDRCONF(NETDEV_UP): enx0050b647ede2: link is not ready Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.1274] keyfile: add connection in-memory (9365f42f-9dd9-3bdc-bbad-e7062efcaf7c,"Wired connection 4") Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.1284] settings: (enx0050b647ede2): created default wired connection 'Wired connection 4' Oct 31 07:08:37 spiny systemd[1]: Starting systemd-resolved-update-resolvconf.service... Oct 31 07:08:37 spiny systemd[1]: Started systemd-resolved-update-resolvconf.service. Oct 31 07:08:37 spiny kernel: usb 1-1.2: new full-speed USB device number 23 using xhci_hcd Oct 31 07:08:37 spiny kernel: usb 1-1.2: New USB device found, idVen
[Kernel-packages] [Bug 1695093] Re: arm64: "unsupported RELA relocation: 275" loading certain modules
I've verified that this is resolved in both linux_4.4.0-101.124 and linux-hwe_4.10.0-40.44~16.04.1. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1695093 Title: arm64: "unsupported RELA relocation: 275" loading certain modules Status in Linux: In Progress Status in gcc-5 package in Ubuntu: Fix Released Status in gcc-6 package in Ubuntu: Fix Released Status in linux package in Ubuntu: Triaged Status in gcc-5 source package in Xenial: Fix Released Status in gcc-6 source package in Xenial: Invalid Status in linux source package in Xenial: Fix Committed Status in gcc-5 source package in Yakkety: Won't Fix Status in gcc-6 source package in Yakkety: Won't Fix Status in linux source package in Yakkety: Won't Fix Status in gcc-5 source package in Zesty: Triaged Status in gcc-6 source package in Zesty: Triaged Status in linux source package in Zesty: Fix Committed Bug description: [Impact] Certain kernel modules are unloadable (libceph & scsi_debug) due to the compiler generating unsupported relocations. This symptom is similar to LP: #1533009 but, in that case it impacted all modules, and the fix for that appears to remain in place. [Test Case] With the hwe-z kernel: ubuntu@grotian:~$ sudo modprobe libceph modprobe: ERROR: could not insert 'libceph': Exec format error ubuntu@grotian:~$ dmesg [66988.470307] module libceph: unsupported RELA relocation: 275 [Regression Risk] The scope of the fix is restricted to aarch64, so regressions should only impact the arm64 port of Ubuntu. Regressions could impact when literal loads are used - which may have performance impacts or possibly cause software to fail to build/run where it previously did. This is somewhat mitigated by the fact that this has been fixed in artful gcc-5/gcc-6 and used on our buildds for some time. Only "somewhat", because gcc-7 is now the default. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1695093/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1726519] Re: Unable to handle kernel NULL pointer dereference at isci_task_abort_task
Thanks for the testing, Brendan. Can you run one more test of the latest mainline kernel? Then I will ping the upstream patch Author. The 4.14 is available from: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.14/ Thanks! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1726519 Title: Unable to handle kernel NULL pointer dereference at isci_task_abort_task Status in linux package in Ubuntu: In Progress Status in linux source package in Artful: In Progress Status in linux source package in Bionic: In Progress Bug description: So I just upgrade from zesty zapus to artful aardvark. At boot, right after I enter my drive encryption password, it kernel panics with the above message. It doesn't even get far enough along in the boot process for syslog to log this panic, so the only info I have is a photo of the panic. In short, I can't boot using the latest artful aardvark kernel, and I have to boot with the latest zesty zapus kernel. :~$ lsb_release -rd Description: Ubuntu 17.10 Release: 17.10 linux-image-4.13.0-16-generic I expect this isn't normal and I should be able to boot with the new kernel, which I can't. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-16-generic 4.13.0-16.19 ProcVersionSignature: Ubuntu 4.10.0-37.41-generic 4.10.17 Uname: Linux 4.10.0-37-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: lost 2071 F pulseaudio /dev/snd/controlC2: lost 2071 F pulseaudio /dev/snd/controlC0: lost 2071 F pulseaudio CurrentDesktop: XFCE Date: Mon Oct 23 12:52:20 2017 HibernationDevice: RESUME=UUID=cf59c168-54d0-45b9-b633-240bd76bbaa6 InstallationDate: Installed on 2016-11-01 (355 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: LENOVO 11361Q0 ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-37-generic root=/dev/mapper/xubuntu--vg-root ro quiet RelatedPackageVersions: linux-restricted-modules-4.10.0-37-generic N/A linux-backports-modules-4.10.0-37-generic N/A linux-firmware 1.169 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to artful on 2017-10-23 (0 days ago) dmi.bios.date: 09/29/2016 dmi.bios.vendor: LENOVO dmi.bios.version: A3KT57AUS dmi.board.name: LENOVO dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: 573921 dmi.chassis.type: 7 dmi.chassis.vendor: LENOVO dmi.chassis.version: NONE dmi.modalias: dmi:bvnLENOVO:bvrA3KT57AUS:bd09/29/2016:svnLENOVO:pn11361Q0:pvrThinkStationC30:rvnLENOVO:rnLENOVO:rvrNODPK:cvnLENOVO:ct7:cvrNONE: dmi.product.name: 11361Q0 dmi.product.version: ThinkStation C30 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1726519/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1731467] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1731467 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1731467 Title: Cannot pair BLE remote devices when using combo BT SoC Status in bluez package in Ubuntu: In Progress Status in linux package in Ubuntu: Incomplete Bug description: It has been observed that sometimes it is not possible to pair with BLE remote devices when the host system is using combo (WiFi + BT) chip. The root cause of the disconnection has been identified as coming from the internal to bluez timeout. If bluez does not hear any reply from for two seconds the link is automagically disconnected. The reason fro the silence is not however a failure of the remote device but quite often a delay in the WiFi/BT combo driver that causes the packages not to reach the bluez stack. [Impact] Not possible to pair BLE remote devices such as sensors and such with Ubuntu when the host system uses BT+WiFi combo SoC. The connection attempt is disturbed with a timeout. [Fix] It has been fixed by increasing the timeout value from 2 seconds to 4 seconds. It is enough for the events to reach the stack (measured that it takes between 3 and 3.5 seconds). [Testcase] Tested with the device that failed to connect to Ubuntu Core gateway. It fails w/o the patch, it connects just fine with the patch applied. [Regression Potential] Very small. The increased timeout is taken into consideration only for new and scan report triggered connections. It will not make any already working device to fail to pair. [Other Info] The bug has been discussed and fixed here: https://marc.info/?l=linux-bluetooth&m=150824844606937&w=2 [Patch] https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth- next.git/commit/?id=1f01d8be0e6a04bd682a55f6d50c14c1679e7571 The patch has been accepted by the upstream and will be a part of the next kernel release. Currently in the bluetooth-next tree. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1731467/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1730321] Re: Ubuntu VM is not detecting the disks connected to Availa beach (LSI/Avago) in Pass Thru mode
** Changed in: xubuntu-meta (Ubuntu) Status: Invalid => 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/1730321 Title: Ubuntu VM is not detecting the disks connected to Availa beach (LSI/Avago) in Pass Thru mode Status in linux package in Ubuntu: Confirmed Status in xubuntu-meta package in Ubuntu: Confirmed Bug description: Below is my setup details: C240 M4 24HDD server with AVB card (FW 24.12.1-0048) and Boot SSDs. Installed ESXi 6.0U1b in the boot SSD in AHCI mode. Updated the latest ESXi Native driver on this. (VMWare-Native-6.610.17.00) Created a VM and Installed Ubuntu 14.04.04. AVB card has one RAID1 VD, one JBOD and all other UG drives. Assigned the AVB controller as a Pass thorugh to ESXi host. Added AVB controller as a Pass through device to the Ubuntu VM. Updated the /etc/vmware/passthru.map file with the device ID and vendor ID of AVB card. Updated the Ubuntu VM with the latest MR driver 06.810 I want to run some IOs to the disks connected to the AVB card from Ubuntu VM. But I am unable to see the disks from the VM. I am seeing so many call traces in the console related to megaraid_sas and see the attached screenshots of the same. Avago is able to reproduce the issue in their lab and see the attached email thread on this discussion. Note : The same scenario is working fine with Ubuntu 12.x series VM's.This issue is occurring both Ubuntu 14.x.x and 16.x.x series guest operating systems. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1730321/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1725350] Re: KVM on 17.10 crashes the machine
I built a 17.10(Artful) test kernel with a pick of the following commit:
67f8a8c1151c ("KVM: PPC: Book3S HV: Fix bug causing host SLB to be restored
incorrectly")
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1725350/
Can you test this kernel and see if it resolves this bug?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1725350
Title:
KVM on 17.10 crashes the machine
Status in The Ubuntu-power-systems project:
Incomplete
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Artful:
In Progress
Bug description:
When you start qemu on a 17.10 machine, the whole machine goes down
and crashes:
[ 90.689627] Unable to handle kernel paging request for data at address
0xf2d3bda0
[ 90.689705] Faulting instruction address: 0xc0361224
[ 90.689840] Oops: Kernel access of bad area, sig: 11 [#1]
[ 90.689911] SMP NR_CPUS=2048
[ 90.689912] NUMA
[ 90.690053] PowerNV
[ 90.690092] Modules linked in: xt_CHECKSUM iptable_mangle ipt_MASQUERADE
nf_nat_masquerade_ipv4 iptable_nat xt_conntrack ipt_REJECT nf_reject_ipv4
xt_tcpudp bridge stp llc kvm_hv kvm_pr kvm ebtable_filter ebtables
ip6table_filter ip6_tables iptable_filter openvswitch nf_conntrack_ipv6
nf_nat_ipv6 nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_defrag_ipv6 nf_nat
nf_conntrack_netlink nf_conntrack nfnetlink idt_89hpesx snd_hda_codec_hdmi xfs
joydev input_leds mac_hid snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep
snd_pcm snd_timer snd soundcore ofpart opal_prd cmdlinepart powernv_flash mtd
at24 ipmi_powernv ipmi_devintf ipmi_msghandler powernv_rng uio_pdrv_genirq
vmx_crypto ibmpowernv uio ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp
libiscsi_tcp libiscsi scsi_transport_iscsi sunrpc ip_tables x_tables
[ 90.690724] autofs4 btrfs raid10 raid456 async_raid6_recov async_memcpy
async_pq async_xor async_tx xor hid_generic usbhid hid raid6_pq libcrc32c raid1
raid0 multipath linear uas usb_storage ast crct10dif_vpmsum i2c_algo_bit
crc32c_vpmsum ttm drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops
drm tg3 ahci libahci
[ 90.690937] CPU: 48 PID: 3986 Comm: qemu-system-ppc Not tainted
4.13.0-12-generic #13-Ubuntu
[ 90.691001] task: c00b122d8700 task.stack: c00b431cc000
[ 90.691167] NIP: c0361224 LR: c0998960 CTR:
c09a19b0
[ 90.691223] REGS: c00bff61b800 TRAP: 0300 Not tainted
(4.13.0-12-generic)
[ 90.691277] MSR: 90009033
[ 90.691282] CR: 88002844 XER:
[ 90.691347] CFAR: c099895c DAR: f2d3bda0 DSISR: 4000
SOFTE: 0
[ 90.691347] GPR00: c0998960 c00bff61ba80 c15e3000
c00b4ef61f20
[ 90.691347] GPR04: c00b44c61680 001f
001f
[ 90.691347] GPR08: 001f 02d3bd80 c178e8e8
c00b5a0c26f0
[ 90.691347] GPR12: 28002842 cfadf800 c00b52d07880
c00b44c61680
[ 90.691347] GPR16: 001f 001f
c553a560
[ 90.691347] GPR20: 0001 0002 08000553a560
c00b5c62a228
[ 90.691347] GPR24: c5531110 c00b5c632238 0210
[ 90.691347] GPR28: c0998960 c00bff61bc20 c00b4ef61f20
f2d3bd80
[ 90.692089] NIP [c0361224] kfree+0x54/0x270
[ 90.692133] LR [c0998960] xhci_urb_free_priv+0x20/0x40
[ 90.692325] Call Trace:
[ 90.692345] [c00bff61ba80] [c00bff61bad0] 0xc00bff61bad0
(unreliable)
[ 90.692402] [c00bff61bac0] [c0998960]
xhci_urb_free_priv+0x20/0x40
[ 90.692459] [c00bff61bae0] [c099bfc8]
xhci_giveback_urb_in_irq.isra.22+0x78/0x190
[ 90.692645] [c00bff61bb40] [c099c350]
xhci_td_cleanup+0x130/0x200
[ 90.692702] [c00bff61bbc0] [c09a175c]
handle_tx_event+0x74c/0x1380
[ 90.692759] [c00bff61bcc0] [c09a2894] xhci_irq+0x504/0xf20
[ 90.692808] [c00bff61bde0] [c017b110]
__handle_irq_event_percpu+0x90/0x300
[ 90.692977] [c00bff61bea0] [c017b3b8]
handle_irq_event_percpu+0x38/0x90
[ 90.693038] [c00bff61bee0] [c017b474]
handle_irq_event+0x64/0xb0
[ 90.693094] [c00bff61bf10] [c0180da0]
handle_fasteoi_irq+0xc0/0x230
[ 90.693155] [c00bff61bf40] [c017972c]
generic_handle_irq+0x4c/0x70
[ 90.693332] [c00bff61bf60] [c001767c] __do_irq+0x7c/0x1c0
[ 90.693383] [c00bff61bf90] [c002ab70] call_do_irq+0x14/0x24
[ 90.693431] [c00b431cf9d0] [c001785c] do_IRQ+0x9c/0x130
[ 90.693478] [c00b431cfa20] [c0008ac4]
hardware_interrupt_common+0x114/0x120
[ 90.693663] --- interrupt: 501 at __copy
[Kernel-packages] [Bug 1651635] Re: XPS 13 9360 trackpad locks into scroll mode
I'm sending it back to dell then... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1651635 Title: XPS 13 9360 trackpad locks into scroll mode Status in Dell Sputnik: Confirmed Status in Linux: Unknown Status in linux package in Ubuntu: New Bug description: Hello, I'm running Linux on a Dell XPS 13 (9360) laptop. I find that upwards of 10 times per day, my trackpad gets stuck in "scrolling" mode. Moving the trackpad won't move the X windows pointer, but will send scrolling events to the foreground window. When the trackpad is locked in this mode, the touchscreen will still let me move the mouse cursor, as will an external mouse. On Ubuntu 16.04 freshly restored from the Dell recovery image, I find that it's often difficult to get the trackpad to recover. I do find that the issue happens less frequently on Dell's build of Ubuntu 16.04 than on other linux distributions and versions, but it still happens enough to significantly impact my ability to do productive work. The issue does not occur when running Windows 10 on the same device. I suspect that the issue may be related to palm detection or misdetecting the user's palm as a gesture to enable scrolling mode, but have no proof for this. It seems that I'm often able to reproduce the issue by brushing the trackpad with my right palm. On Ubuntu 16.10, with the latest shipped 4.8 kernel (Linux szx 4.8.0-30-generic #32-Ubuntu SMP Fri Dec 2 03:43:27 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux), with the extra xinput configuration below, I am able to get the trackpad to recover, simply by clicking the trackpad: /usr/share/X11/xorg.conf.d/99-libinput.conf: Section "InputClass" Identifier "libinput touchpad catchall" Driver "libinput" MatchIsTouchpad "on" MatchDevicePath "/dev/input/event*" Option "Tapping" "True" Option "DisableWhileTyping" "True" Option "NaturalScrolling" "False" Option "AccelProfile" "adaptive" Option "AccelSpeed" "0.05" Option "MiddleEmulation" "True" Option "ScrollMethod" "twofinger" # Option "ClickMethod" "clickfinger" Option "ClickMethod" "buttonareas" EndSection In my experience, the problem manifests using both the Xorg synaptics driver and the Xorg libinput driver. root@szx:/etc/modprobe.d# xinput list ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ Logitech M570 id=10 [slave pointer (2)] ⎜ ↳ DLL075B:01 06CB:76AF Touchpad id=13 [slave pointer (2)] ⎜ ↳ ELAN Touchscreenid=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Buttonid=8[slave keyboard (3)] ↳ Sleep Buttonid=9[slave keyboard (3)] ↳ Integrated_Webcam_HDid=12 [slave keyboard (3)] ↳ Intel Virtual Button driver id=14 [slave keyboard (3)] ↳ Intel HID eventsid=15 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=16 [slave keyboard (3)] ↳ Dell WMI hotkeysid=17 [slave keyboard (3)] root@szx:/etc/modprobe.d# To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1651635/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1731088] Re: ubuntu 17.10 freezes at anytime
Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem? Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.14 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.14 ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete ** Tags added: kernel-da-key -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1731088 Title: ubuntu 17.10 freezes at anytime Status in linux package in Ubuntu: Incomplete Bug description: opening internet browser -firefox or file browser, the system freezes. i have seen it last when i opened Krita application. the only option is hard reboot from power button. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-16-generic 4.13.0-16.19 [modified: boot/vmlinuz-4.13.0-16-generic] ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: prabin 1517 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Nov 8 19:40:37 2017 HibernationDevice: RESUME=UUID=3d8b4fbf-8efe-4b9a-af50-65a4a5f5e597 InstallationDate: Installed on 2017-11-02 (6 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: Hewlett-Packard HP ENVY m6 Notebook PC ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=UUID=cba91a21-02a0-4f8d-9f79-263001d33acf ro quiet splash RelatedPackageVersions: linux-restricted-modules-4.13.0-16-generic N/A linux-backports-modules-4.13.0-16-generic N/A linux-firmware 1.169 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/14/2014 dmi.bios.vendor: Insyde dmi.bios.version: F.26 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 18A5 dmi.board.vendor: Hewlett-Packard dmi.board.version: 73.50 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.26:bd05/14/2014:svnHewlett-Packard:pnHPENVYm6NotebookPC:pvr088B1130591620100:rvnHewlett-Packard:rn18A5:rvr73.50:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV dmi.product.name: HP ENVY m6 Notebook PC dmi.product.version: 088B1130591620100 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1731088/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1731080] Re: Very slow display on Legacy mode, but it's normal on UEFI mode
Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem? Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.14 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.14 ** Tags added: kernel-da-key -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1731080 Title: Very slow display on Legacy mode, but it's normal on UEFI mode Status in linux package in Ubuntu: Confirmed Bug description: When I start boot into OS in text mode with BIOS Legacy mode,it is very slow display for example do type cmd: cat /proc/cpuinfo ,but I had tried add a GRUB_CMDLINE_LINUX=”vga=normal” in /etc/default/grub. It can be normal display My config on the server : OS ver:Ubuntu 16.04.x VGA: onboard AST2x00 w/o install expansion vga card To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1731080/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1731031] Re: Kernel Oops with 17.10
Can you see which release candidate in 4.14 fixes this bug? If we know that, we can "Reverse" bisect to identify the specific commit that is the fix. All of the release candidates are here: http://kernel.ubuntu.com/~kernel-ppa/mainline/ You already tested 4.14-rc8, so maybe try 4.14-rc4 and 4.14-rc1. ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete ** Changed in: linux (Ubuntu) Status: Incomplete => Triaged ** Also affects: linux (Ubuntu Artful) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Artful) Status: New => Triaged ** Changed in: linux (Ubuntu Artful) Importance: Undecided => Medium ** Tags added: performing-bisect -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1731031 Title: Kernel Oops with 17.10 Status in linux package in Ubuntu: Triaged Status in linux source package in Artful: Triaged Bug description: have captured dmesg just before oops ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: KDE Date: Wed Nov 8 20:41:14 2017 DistUpgraded: 2017-11-07 01:49:14,657 DEBUG icon theme changed, re-reading DistroCodename: artful DistroVariant: kubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.10.0-38-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 4.13.0-16-generic, x86_64: installed GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a2e] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. Haswell-ULT Integrated Graphics Controller [106b:011a] LightdmGreeterLogOld: ** (lightdm-gtk-greeter:1762): WARNING **: Failed to load user image: Failed to open file '/home/hmeyer/.face': No such file or directory MachineType: Apple Inc. MacBookPro11,1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=UUID=fbc61d79-8b51-4801-8e2b-175ff6daa14f ro quiet splash apparmor=0 vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to artful on 2017-11-07 (1 days ago) dmi.bios.date: 02/22/2016 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP111.88Z.0138.B17.1602221718 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-189A3D4F975D5FFC dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro11,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-189A3D4F975D5FFC dmi.modalias: dmi:bvnAppleInc.:bvrMBP111.88Z.0138.B17.1602221718:bd02/22/2016:svnAppleInc.:pnMacBookPro11,1:pvr1.0:rvnAppleInc.:rnMac-189A3D4F975D5FFC:rvrMacBookPro11,1:cvnAppleInc.:ct10:cvrMac-189A3D4F975D5FFC: dmi.product.family: Mac dmi.product.name: MacBookPro11,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Wed Nov 8 20:39:06 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.5-0ubuntu2 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1731031/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1731060] Re: package linux-image-extra-4.13.0-17-generic 4.13.0-17.20 failed to install/upgrade: il sottoprocesso installato script di post-removal ha restituito lo stato di err
You may need to run the following from a terminal: sudo apt-get install -f sudo apt-get clean sudo apt-get update Then re-install the package or updates. If that does not resolve your issue, please mark the bug as "Confirmed" ** Changed in: linux (Ubuntu) Importance: Undecided => Low ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1731060 Title: package linux-image-extra-4.13.0-17-generic 4.13.0-17.20 failed to install/upgrade: il sottoprocesso installato script di post-removal ha restituito lo stato di errore 1 Status in linux package in Ubuntu: Incomplete Bug description: The uninstall process run forever with this last line as output: run-parts: executing /etc/kernel/postinst.d/dkms 4.13.0-17-generic /boot/vmlinuz-4.13.0-17-generic ProblemType: Package DistroRelease: Ubuntu 17.10 Package: linux-image-extra-4.13.0-17-generic 4.13.0-17.20 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gdm1521 F pulseaudio casa 2790 F pulseaudio /dev/snd/controlC0: gdm1521 F pulseaudio casa 2790 F pulseaudio Date: Wed Nov 8 23:03:53 2017 ErrorMessage: il sottoprocesso installato script di post-removal ha restituito lo stato di errore 1 HibernationDevice: RESUME=UUID=b1a7755c-92df-48fe-92d2-66de15fbb008 InstallationDate: Installed on 2015-10-23 (747 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: LENOVO 20ANCTO1WW ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=UUID=942dc08f-9465-4002-8ffb-c1fbe03f7a04 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: grub-pc 2.02~beta3-4ubuntu7 SourcePackage: linux Title: package linux-image-extra-4.13.0-17-generic 4.13.0-17.20 failed to install/upgrade: il sottoprocesso installato script di post-removal ha restituito lo stato di errore 1 UpgradeStatus: Upgraded to artful on 2017-10-21 (18 days ago) dmi.bios.date: 07/23/2015 dmi.bios.vendor: LENOVO dmi.bios.version: GLET80WW (2.34 ) dmi.board.asset.tag: Not Available dmi.board.name: 20ANCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGLET80WW(2.34):bd07/23/2015:svnLENOVO:pn20ANCTO1WW:pvrThinkPadT440p:rvnLENOVO:rn20ANCTO1WW:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T440p dmi.product.name: 20ANCTO1WW dmi.product.version: ThinkPad T440p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1731060/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1730904] Re: 17.10 freezes every hour ramdomly
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.14 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.14 ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1730904 Title: 17.10 freezes every hour ramdomly Status in linux package in Ubuntu: Incomplete Bug description: on 17.04 I had frequent errors reported, now hangs all the computer, please some workaround or way back to 17.04 ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-16-generic 4.13.0-16.19 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rogelio1645 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Nov 8 09:07:15 2017 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=e26838c6-6b72-461d-a811-a892d423fac1 InstallationDate: Installed on 2017-05-04 (187 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: ASUSTeK COMPUTER INC. K55A ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-16-generic N/A linux-backports-modules-4.13.0-16-generic N/A linux-firmware 1.169 SourcePackage: linux UpgradeStatus: Upgraded to artful on 2017-11-07 (0 days ago) dmi.bios.date: 03/13/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: K55A.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: K55A 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.:bvrK55A.204:bd03/13/2012:svnASUSTeKCOMPUTERINC.:pnK55A:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnK55A:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: K dmi.product.name: K55A 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/1730904/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1730958] Re: nuvoton-cir not working after boot
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.14 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.14 ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete ** Tags added: needs-bisect -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1730958 Title: nuvoton-cir not working after boot Status in linux package in Ubuntu: Incomplete Bug description: Current setup/failing setup: Linux frontend01 4.13.0-17-generic #20-Ubuntu SMP Mon Nov 6 10:04:08 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux Ubuntu 4.13.0-17.20-generic 4.13.8 Ubuntu 17.10, 4.13.0-17-generic Nuvoton w836x7hg Infrared Remote Transceiver Zotac ID42 Working setup: Ubuntu 17.10, 4.4.8-040408-generic I'm not able to get the remote working after a normal reboot (using 4.13 kernel) It does actually after a suspend and wake-up, and do a echo 'auto' to resources. Please find snapshot of dmesg below: [ 14.067757] nuvoton-cir 00:0a: found NCT6776F or compatible: chip id: 0xc3 0x33 [ 14.468143] rc rc0: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0 [ 14.468227] input: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0/input7 [ 14.468484] rc rc0: lirc_dev: driver ir-lirc-codec (nuvoton-cir) registered at minor = 0 [ 14.468526] nuvoton-cir 00:0a: driver has been successfully loaded modprobe -r nuvoton-cir echo "auto" > /sys/bus/acpi/devices/NTN0530\:00/physical_node/resources modprobe nuvoton-cir [ 66.231365] nuvoton-cir 00:0a: found NCT6776F or compatible: chip id: 0xc3 0x33 [ 66.231610] rc rc0: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0 [ 66.231758] input: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0/input13 [ 66.232140] rc rc0: lirc_dev: driver ir-lirc-codec (nuvoton-cir) registered at minor = 0 [ 66.232240] nuvoton-cir 00:0a: driver has been successfully loaded suspend/resume [ 105.890769] nuvoton-cir 00:0a: disabled [ 106.651982] nuvoton-cir 00:0a: activated modprobe -r nuvoton-cir echo "auto" > /sys/bus/acpi/devices/NTN0530\:00/physical_node/resources modprobe nuvoton-cir [ 138.549572] nuvoton-cir 00:0a: found NCT6776F or compatible: chip id: 0xc3 0x33 [ 138.549839] rc rc0: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0 [ 138.551225] input: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0/input17 [ 138.552171] rc rc0: lirc_dev: driver ir-lirc-codec (nuvoton-cir) registered at minor = 0 [ 138.552256] nuvoton-cir 00:0a: driver has been successfully loaded In order to get the device working I need the following in this order: * suspend/resume * echo "auto" > /sys/bus/acpi/devices/NTN0530\:00/physical_node/resources --- ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/controlC1', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 17.10 HibernationDevice: RESUME=UUID=d95eb1c2-ba63-486d-9da0-8b4c785342d6 InstallationDate: Installed on 2014-04-01 (1317 days ago) InstallationMedia: Mythbuntu 12.04.3 "Precise Pangolin" - Release amd64 (20130820) MachineType: ZOTAC ZBOX-ID42-BE NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic root=UUID=e870e449-a4ea-4551-b4a6-32e3966a1789 ro splash quiet vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 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.13.0-17-generic N/A linux-backports-modules-4.13.0-17-generic N/A linux-firmware 1.169 Tags: artful Uname: Linux 4.13.0-17-generic x86_64 UpgradeStatus: Upgraded to artful on 2017-11-05 (2 days ago) UserGroups: adm audio cdrom dip lpadmin mythtv nopasswdlogin plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 05/03/2013
[Kernel-packages] [Bug 1730970] Re: TouchPad Stopped Working
Does this bug go away if you boot back into the prior kernel version? ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete ** Tags added: needs-bisect -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1730970 Title: TouchPad Stopped Working Status in linux package in Ubuntu: Incomplete Bug description: Release: Description: Ubuntu 16.04.3 LTS Release: 16.04 version_signature: Ubuntu 4.4.0-98.121-generic 4.4.90 Issue: | I recently did and update (sudo apt-get update / sudo apt-get upgrade). A few days later I did a reboot and my touchpad stopped working. The touchpad does not appear to show in devices (cat /proc/bus/input/devices), but my external usb mouse does. Perhaps a recent update in the kernel has caused this issue. --- ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: james 2565 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=671f3f70-b698-48fc-bbff-e0854576a83a InstallationDate: Installed on 2017-01-04 (308 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Hewlett-Packard HP ENVY 15 Notebook PC Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-98-generic root=UUID=97ae60fc-8359-45ec-a361-5b46165aeaae ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90 RelatedPackageVersions: linux-restricted-modules-4.4.0-98-generic N/A linux-backports-modules-4.4.0-98-generic N/A linux-firmware1.157.13 Tags: xenial Uname: Linux 4.4.0-98-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin plugdev pulse sambashare sudo video _MarkForUpload: True dmi.bios.date: 10/31/2012 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.0B dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 1688 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 44.20 dmi.chassis.asset.tag: CNU2063908 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnHewlett-Packard:bvrF.0B:bd10/31/2012:svnHewlett-Packard:pnHPENVY15NotebookPC:pvr06911020481620100:rvnHewlett-Packard:rn1688:rvrKBCVersion44.20:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP ENVY 15 Notebook PC dmi.product.version: 06911020481620100 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1730970/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1730924] Re: Wifi does down "crash" in Surface Pro 4
Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem? Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.14 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.14 ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1730924 Title: Wifi does down "crash" in Surface Pro 4 Status in linux package in Ubuntu: Incomplete Bug description: I have a Surface Pro 4. The wifi works well in principle, but unfortunately it drops every x minutes. The only way to fix it I've found is to reboot the computer. lsb_release -rd Description:Ubuntu 17.10 Release:17.10 ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-16-generic 4.13.0-16.19 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: predatux 1537 F pulseaudio CurrentDesktop: KDE Date: Wed Nov 8 10:41:26 2017 HibernationDevice: RESUME=UUID=147af4ba-a4ce-41fe-a176-b36a1f6a590b Lsusb: Bus 002 Device 002: ID 045e:090c Microsoft Corp. Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 045e:07e8 Microsoft Corp. Bus 001 Device 003: ID 1286:204c Marvell Semiconductor, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Microsoft Corporation Surface Pro 4 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=UUID=125200b0-7377-4985-a217-15503781a525 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-16-generic N/A linux-backports-modules-4.13.0-16-generic N/A linux-firmware 1.169 SourcePackage: linux UpgradeStatus: Upgraded to artful on 2017-10-22 (16 days ago) dmi.bios.date: 02/24/2017 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: 106.1624.768 dmi.board.name: Surface Pro 4 dmi.board.vendor: Microsoft Corporation dmi.chassis.type: 9 dmi.chassis.vendor: Microsoft Corporation dmi.modalias: dmi:bvnMicrosoftCorporation:bvr106.1624.768:bd02/24/2017:svnMicrosoftCorporation:pnSurfacePro4:pvrD0B08F1C03P38:rvnMicrosoftCorporation:rnSurfacePro4:rvr:cvnMicrosoftCorporation:ct9:cvr: dmi.product.family: Surface dmi.product.name: Surface Pro 4 dmi.product.version: D:0B:08F:1C:03P:38 dmi.sys.vendor: Microsoft Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1730924/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1721070] Comment bridged from LTC Bugzilla
--- Comment From gwal...@br.ibm.com 2017-11-14 11:58 EDT---
Status Today:
Tested on Artful
- Aligntest : OK
- Stress-ng : OK, 30 minutes of stress of CPUs was fine.
Missing Zesty environment.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1721070
Title:
powerpc/64s: Add workaround for P9 vector CI load issue
Status in The Ubuntu-power-systems project:
Fix Committed
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Zesty:
Fix Committed
Status in linux source package in Artful:
Fix Committed
Bug description:
== SRU Justification ==
POWER9 DD2.1 and earlier has an issue where some cache inhibited
vector load will return bad data. The fix is two part, one
firmware/microcode part triggers HMI interrupts when hitting such
loads, the other part is commit 5080332c2c89 from linux-next which then
emulates the instructions in Linux.
The affected instructions are limited to lxvd2x, lxvw4x, lxvb16x and
lxvh8x.
Commit ccd3cd361341 is needed as a prereq for Artful.
Commits a3d96f70c147 and ccd3cd361341 are needed as prereqs for Zesty.
== Fixes ==
a3d96f70c147 ("powerpc/64s: Fix system reset vs general interrupt reentrancy")
ccd3cd361341 ("powerpc/mce: Move 64-bit machine check code into mce.c")
5080332c2c89 ("powerpc/64s: Add workaround for P9 vector CI load issue")
== Regression Potential ==
These commits are specific to powerpc. They required some back porting but
have been tested by IBM.
-- Problem Description --
When an instruction triggers the HMI, all threads in the core will be
sent to the HMI handler, not just the one running the vector load.
In general, these spurious HMIs are detected by the emulation code and
we just return back to the running process. Unfortunately, if a
spurious interrupt occurs on a vector load that's to normal memory we
have no way to detect that it's spurious (unless we walk the page
tables, which is very expensive). In this case we emulate the load but
we need do so using a vector load itself to ensure 128bit atomicity is
preserved.
Some additional debugfs emulated instruction counters are added also.
In order to solve this bug, we need to cherry pick the following patch
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=next&id=5080332c2c893118dbc18755f35c8b0131cf0fc4
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1721070/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1731257] Re: linux 4.14.0-6.8 ADT test failure with linux 4.14.0-6.8
LSM stacking patches have been applied in 4.14.0-7.9, so we'll see whether that resolves these failures. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1731257 Title: linux 4.14.0-6.8 ADT test failure with linux 4.14.0-6.8 Status in linux package in Ubuntu: Confirmed Bug description: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-bootstrap/bionic/amd64/l/linux/20171107_153858_c2c05@/log.gz i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-bootstrap/bionic/i386/l/linux/20171108_140414_c2c05@/log.gz ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-bootstrap/bionic/ppc64el/l/linux/20171107_154212_c2c05@/log.gz s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-bootstrap/bionic/s390x/l/linux/20171107_150354_c2c05@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1731257/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1722721] Re: Rebase drm-core & i915 to 4.9.x
** Changed in: linux (Ubuntu Xenial) Status: Triaged => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1722721 Title: Rebase drm-core & i915 to 4.9.x Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Invalid Bug description: PLACEHOLDER To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1722721/+subscriptions -- Mailing list: https://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 1729674] Re: TB16 dock ethernet corrupts data with hw checksum silently failing
I am not using ipv6. On Tue, Nov 14, 2017 at 9:10 AM, Mario Limonciello wrote: > @Dave: > > I was glancing at r8152 driver and notice that it has some special > handling for ipv6. Is this issue reproducing only in ipv6 for you? > https://github.com/torvalds/linux/commit/6128d1bb30748d0ff56a63898d14f3 > 12126e404c > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1729674 > > Title: > TB16 dock ethernet corrupts data with hw checksum silently failing > > Status in Dell Sputnik: > Triaged > Status in linux package in Ubuntu: > In Progress > > Bug description: > It looks like TCP rx and tx checksum offloading is broken on the TB16 > dock's ethernet adapter. For example downloading a large file such as the > Ubuntu ISO, and then running an md5sum on it yields the incorrect md5sum. > This is because > rx-checksumming: on > tx-checksumming: on > and both set to on by default. > > Running sudo ethtool -K tx off rx off, allows the > download to complete correctly. This is very bad since this can cause > very bad untrustworthy behavior. > > This was conducted using an Dell Precision 5520 on Ubuntu 16.04+linux- > generic-hwe-16.04-edge. > > Thank you > > To manage notifications about this bug go to: > https://bugs.launchpad.net/dell-sputnik/+bug/1729674/+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/1729674 Title: TB16 dock ethernet corrupts data with hw checksum silently failing Status in Dell Sputnik: Triaged Status in linux package in Ubuntu: In Progress Bug description: It looks like TCP rx and tx checksum offloading is broken on the TB16 dock's ethernet adapter. For example downloading a large file such as the Ubuntu ISO, and then running an md5sum on it yields the incorrect md5sum. This is because rx-checksumming: on tx-checksumming: on and both set to on by default. Running sudo ethtool -K tx off rx off, allows the download to complete correctly. This is very bad since this can cause very bad untrustworthy behavior. This was conducted using an Dell Precision 5520 on Ubuntu 16.04+linux- generic-hwe-16.04-edge. Thank you To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1729674/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1729674] Re: TB16 dock ethernet corrupts data with hw checksum silently failing
I also just went through the process of reproducing this while watching the kern.log. Absolutely 0 messages came out. If you find some verbose debugging you want me to turn on let me know. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1729674 Title: TB16 dock ethernet corrupts data with hw checksum silently failing Status in Dell Sputnik: Triaged Status in linux package in Ubuntu: In Progress Bug description: It looks like TCP rx and tx checksum offloading is broken on the TB16 dock's ethernet adapter. For example downloading a large file such as the Ubuntu ISO, and then running an md5sum on it yields the incorrect md5sum. This is because rx-checksumming: on tx-checksumming: on and both set to on by default. Running sudo ethtool -K tx off rx off, allows the download to complete correctly. This is very bad since this can cause very bad untrustworthy behavior. This was conducted using an Dell Precision 5520 on Ubuntu 16.04+linux- generic-hwe-16.04-edge. Thank you To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1729674/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1732238] [NEW] arm64: Unfair rwlock can stall the system
Public bug reported: [Impact] There is a long-standing upstream bug with the ARM64 specific implementation of RW locks. The implementation can starve writers under lock contention leading to RCU stalls and general system instability. [Test Case] $ stress-ng --kill 0 -t 300 -v You'll see the console fill with messages like: [ 2534.423119] INFO: rcu_sched detected stalls on CPUs/tasks: [ 2534.428606] 192-...: (1 ticks this GP) idle=b6e/140/0 softirq=578/578 fqs=6770 [ 2534.437029] (detected by 0, t=15005 jiffies, g=1479, c=1478, q=473) [ 2714.623691] INFO: rcu_sched detected stalls on CPUs/tasks: [ 2714.629181] 192-...: (1 ticks this GP) idle=b6e/140/0 softirq=578/578 fqs=12819 [ 2714.637692] (detected by 116, t=60058 jiffies, g=1479, c=1478, q=1736) [ 2747.216955] watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kworker/0:5:1464] [ 2775.399061] watchdog: BUG: soft lockup - CPU#13 stuck for 123s! [systemd-network:2936] [Regression Risk] TBD ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1732238 Title: arm64: Unfair rwlock can stall the system Status in linux package in Ubuntu: New Bug description: [Impact] There is a long-standing upstream bug with the ARM64 specific implementation of RW locks. The implementation can starve writers under lock contention leading to RCU stalls and general system instability. [Test Case] $ stress-ng --kill 0 -t 300 -v You'll see the console fill with messages like: [ 2534.423119] INFO: rcu_sched detected stalls on CPUs/tasks: [ 2534.428606]192-...: (1 ticks this GP) idle=b6e/140/0 softirq=578/578 fqs=6770 [ 2534.437029](detected by 0, t=15005 jiffies, g=1479, c=1478, q=473) [ 2714.623691] INFO: rcu_sched detected stalls on CPUs/tasks: [ 2714.629181]192-...: (1 ticks this GP) idle=b6e/140/0 softirq=578/578 fqs=12819 [ 2714.637692](detected by 116, t=60058 jiffies, g=1479, c=1478, q=1736) [ 2747.216955] watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kworker/0:5:1464] [ 2775.399061] watchdog: BUG: soft lockup - CPU#13 stuck for 123s! [systemd-network:2936] [Regression Risk] TBD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1732238/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1651635] Re: XPS 13 9360 trackpad locks into scroll mode
I'm not convinced it's hardware related, booted with 16.04.3 , going to use it until tonight. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1651635 Title: XPS 13 9360 trackpad locks into scroll mode Status in Dell Sputnik: Confirmed Status in Linux: Unknown Status in linux package in Ubuntu: New Bug description: Hello, I'm running Linux on a Dell XPS 13 (9360) laptop. I find that upwards of 10 times per day, my trackpad gets stuck in "scrolling" mode. Moving the trackpad won't move the X windows pointer, but will send scrolling events to the foreground window. When the trackpad is locked in this mode, the touchscreen will still let me move the mouse cursor, as will an external mouse. On Ubuntu 16.04 freshly restored from the Dell recovery image, I find that it's often difficult to get the trackpad to recover. I do find that the issue happens less frequently on Dell's build of Ubuntu 16.04 than on other linux distributions and versions, but it still happens enough to significantly impact my ability to do productive work. The issue does not occur when running Windows 10 on the same device. I suspect that the issue may be related to palm detection or misdetecting the user's palm as a gesture to enable scrolling mode, but have no proof for this. It seems that I'm often able to reproduce the issue by brushing the trackpad with my right palm. On Ubuntu 16.10, with the latest shipped 4.8 kernel (Linux szx 4.8.0-30-generic #32-Ubuntu SMP Fri Dec 2 03:43:27 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux), with the extra xinput configuration below, I am able to get the trackpad to recover, simply by clicking the trackpad: /usr/share/X11/xorg.conf.d/99-libinput.conf: Section "InputClass" Identifier "libinput touchpad catchall" Driver "libinput" MatchIsTouchpad "on" MatchDevicePath "/dev/input/event*" Option "Tapping" "True" Option "DisableWhileTyping" "True" Option "NaturalScrolling" "False" Option "AccelProfile" "adaptive" Option "AccelSpeed" "0.05" Option "MiddleEmulation" "True" Option "ScrollMethod" "twofinger" # Option "ClickMethod" "clickfinger" Option "ClickMethod" "buttonareas" EndSection In my experience, the problem manifests using both the Xorg synaptics driver and the Xorg libinput driver. root@szx:/etc/modprobe.d# xinput list ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ Logitech M570 id=10 [slave pointer (2)] ⎜ ↳ DLL075B:01 06CB:76AF Touchpad id=13 [slave pointer (2)] ⎜ ↳ ELAN Touchscreenid=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Buttonid=8[slave keyboard (3)] ↳ Sleep Buttonid=9[slave keyboard (3)] ↳ Integrated_Webcam_HDid=12 [slave keyboard (3)] ↳ Intel Virtual Button driver id=14 [slave keyboard (3)] ↳ Intel HID eventsid=15 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=16 [slave keyboard (3)] ↳ Dell WMI hotkeysid=17 [slave keyboard (3)] root@szx:/etc/modprobe.d# To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1651635/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1732238] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1732238 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1732238 Title: arm64: Unfair rwlock can stall the system Status in linux package in Ubuntu: Incomplete Bug description: [Impact] There is a long-standing upstream bug with the ARM64 specific implementation of RW locks. The implementation can starve writers under lock contention leading to RCU stalls and general system instability. [Test Case] $ stress-ng --kill 0 -t 300 -v You'll see the console fill with messages like: [ 2534.423119] INFO: rcu_sched detected stalls on CPUs/tasks: [ 2534.428606]192-...: (1 ticks this GP) idle=b6e/140/0 softirq=578/578 fqs=6770 [ 2534.437029](detected by 0, t=15005 jiffies, g=1479, c=1478, q=473) [ 2714.623691] INFO: rcu_sched detected stalls on CPUs/tasks: [ 2714.629181]192-...: (1 ticks this GP) idle=b6e/140/0 softirq=578/578 fqs=12819 [ 2714.637692](detected by 116, t=60058 jiffies, g=1479, c=1478, q=1736) [ 2747.216955] watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kworker/0:5:1464] [ 2775.399061] watchdog: BUG: soft lockup - CPU#13 stuck for 123s! [systemd-network:2936] [Regression Risk] TBD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1732238/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1712765] Re: reboot instead of shutdown
** Bug watch added: Linux Kernel Bug Tracker #197871 https://bugzilla.kernel.org/show_bug.cgi?id=197871 ** Also affects: linux via https://bugzilla.kernel.org/show_bug.cgi?id=197871 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1712765 Title: reboot instead of shutdown Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Bug description: I have a Acer Aspire v5 571g laptop which initially had Windows installed. After I installed Ubuntu (and overwrote Windows) the computer shuts down when a restart is requested. Windows did not exhibit this problem. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-32-generic 4.10.0-32.36 ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17 Uname: Linux 4.10.0-32-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: felix 1929 F...m pulseaudio /dev/snd/controlC0: felix 1929 F pulseaudio CurrentDesktop: Unity:Unity7 Date: Thu Aug 24 10:24:56 2017 HibernationDevice: RESUME=UUID=9aa9aa29-eb16-473f-b28d-5d6c340eac81 InstallationDate: Installed on 2017-06-14 (70 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: Acer Aspire V5-571G ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-32-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.10.0-32-generic N/A linux-backports-modules-4.10.0-32-generic N/A linux-firmware 1.164.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/12/2012 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: V1.12 dmi.board.asset.tag: No Asset Tag dmi.board.name: Aspire V5-571G dmi.board.vendor: Acer dmi.board.version: V1.12 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Acer dmi.chassis.version: V1.12 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrV1.12:bd06/12/2012:svnAcer:pnAspireV5-571G:pvrV1.12:rvnAcer:rnAspireV5-571G:rvrV1.12:cvnAcer:ct9:cvrV1.12: dmi.product.name: Aspire V5-571G dmi.product.version: V1.12 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1712765/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1725259] Re: general protection fault: 0000 [#1] SMP
I tested with Debian buster and Fedora 27 and the file is playing without any GPU hangs. So the problem might be Ubuntu only. I also tested Ubuntu 18.04 (daily 13/11) and the hangs still occurs. FOr me this isn't a kernel or DRM/Intel Bug -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1725259 Title: general protection fault: [#1] SMP Status in linux package in Ubuntu: Confirmed Bug description: Got a GPU hang when playing videos in totem. When Playing in VLC everything is OK Same crash under mpv [drm] GPU HANG: ecode 5:0:0xfdff, in Xorg [2005], reason: Hang on rcs0, action: reset [ 235.623605] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace. [ 235.623606] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel [ 235.623607] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue. [ 235.623607] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it. [ 235.623608] [drm] GPU crash dump saved to /sys/class/drm/card0/error [ 235.623687] drm/i915: Resetting chip after gpu hang ProblemType: KernelOops DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-16-generic 4.13.0-16.19 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm 984 F pulseaudio brand101338 F pulseaudio Date: Fri Oct 20 13:47:22 2017 Failure: oops InstallationDate: Installed on 2017-08-18 (63 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170816) Lsusb: Bus 002 Device 003: ID 0a5c:5800 Broadcom Corp. BCM5880 Secure Applications Processor Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude E6410 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed root=UUID=5810df9f-2bd6-4f2e-89a8-b16ac27ff5b2 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: kerneloops-daemon N/A SourcePackage: linux Title: general protection fault: [#1] SMP UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/05/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A16 dmi.board.name: 04373Y dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA16:bd12/05/2013:svnDellInc.:pnLatitudeE6410:pvr0001:rvnDellInc.:rn04373Y:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6410 dmi.product.version: 0001 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1725259/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1729878] Re: stress-ng triggering oomkiller running brk and stack stressors on all arches.
** Tags added: hwcert-server -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1729878 Title: stress-ng triggering oomkiller running brk and stack stressors on all arches. Status in Stress-ng: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Artful: Confirmed Bug description: During regression testing on a z/VM instance, I noticed call traces being dumped to dmesg that seem to be related to stress-ng. The stress-ng invocation we're using is: stress-ng --aggressive --verify --timeout $runtime \ --metrics-brief --tz --times \ --af-alg 0 --bsearch 0 --context 0 --cpu 0 \ --crypt 0 --hsearch 0 --longjmp 0 --lsearch 0 \ --matrix 0 --qsort 0 --str 0 --stream 0 \ --tsearch 0 --vecmath 0 --wcs 0 as executed by the cpu_stress script from the cpu/cpu_stress_ng test in the certification suite. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-16-generic 4.13.0-16.19 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic s390x AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.7-0ubuntu3.1 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Fri Nov 3 11:12:04 2017 HibernationDevice: RESUME=UUID=1ce0f037-449a-43a1-af49-e730f6f99ac4 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C SHELL=/bin/bash ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb' ProcKernelCmdLine: root=/dev/mapper/hwe0008_vg-lv crashkernel=196M BOOT_IMAGE=0 RelatedPackageVersions: linux-restricted-modules-4.13.0-16-generic N/A linux-backports-modules-4.13.0-16-generic N/A linux-firmware 1.169 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: Upgraded to artful on 2017-11-02 (0 days ago) --- AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.7-0ubuntu3.1 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. DistroRelease: Ubuntu 17.10 HibernationDevice: RESUME=UUID=1ce0f037-449a-43a1-af49-e730f6f99ac4 IwConfig: Error: [Errno 2] No such file or directory Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C SHELL=/bin/bash ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb' ProcKernelCmdLine: root=/dev/mapper/hwe0008_vg-lv crashkernel=196M BOOT_IMAGE=0 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 RelatedPackageVersions: linux-restricted-modules-4.13.0-16-generic N/A linux-backports-modules-4.13.0-16-generic N/A linux-firmware 1.169 RfKill: Error: [Errno 2] No such file or directory Tags: artful Uname: Linux 4.13.0-16-generic s390x UpgradeStatus: Upgraded to artful on 2017-11-02 (0 days ago) UserGroups: adm cdrom cpacfstats dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/stress-ng/+bug/1729878/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1721856] Re: Suspend ends after seconds and laptop resumes
I built the next test kernel, up to the following commit: 91d57bae08689199c8acc77a8b3b41150cafab1c The test kernel can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1721856 Can you test that kernel and report back if it has the bug or not? I will build the next test kernel based on your test results. We should only have 2 or so more kernels to test. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1721856 Title: Suspend ends after seconds and laptop resumes Status in linux package in Ubuntu: In Progress Status in linux source package in Zesty: In Progress Bug description: The suspend/standby ends after seconds and the laptop resumes like it'd wake up from suspend. I didn't use suspend for a long time (months or years) and can't even estimate when it worked for the last time. This issue is fixed in 4.14-rc3 mainline kernel - although some parts of the installation don't work, like ZFS and nvidia-340 which might cause the problem as well. I'm willing to do git bisect work if you confirm me that this makes sense. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-35-generic 4.10.0-35.39 ProcVersionSignature: Ubuntu 4.10.0-35.39-generic 4.10.17 Uname: Linux 4.10.0-35-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 AudioDevicesInUse: BEN.PID ZUGR. BEFEHL /dev/snd/controlC0: richter 18896 F pulseaudio CurrentDesktop: XFCE Date: Fri Oct 6 20:21:35 2017 HibernationDevice: RESUME=UUID=1bb0bb3e-8148-4957-9673-9701bd571c0a InstallationDate: Installed on 2015-12-12 (664 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: LENOVO 20221 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-35-generic root=UUID=791b47e7-915d-4d5a-bce0-d7e9b660a2ab ro rootflags=subvol=ubuntu-main-root RelatedPackageVersions: linux-restricted-modules-4.10.0-35-generic N/A linux-backports-modules-4.10.0-35-generic N/A linux-firmware 1.164.1 SourcePackage: linux UpgradeStatus: Upgraded to zesty on 2017-05-01 (158 days ago) dmi.bios.date: 07/12/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 71CN51WW(V1.21) dmi.board.asset.tag: No Asset Tag dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: 3193WIN8 STD MLT dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad Z500 Touch dmi.modalias: dmi:bvnLENOVO:bvr71CN51WW(V1.21):bd07/12/2013:svnLENOVO:pn20221:pvrLenovoIdeaPadZ500Touch:rvnLENOVO:rnINVALID:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoIdeaPadZ500Touch: dmi.product.name: 20221 dmi.product.version: Lenovo IdeaPad Z500 Touch dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1721856/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1730895] Re: aio-dio-invalidate-failure test failed with event res -22 on s390x
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Status: Incomplete => Triaged
** Tags added: kernel-da-key
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1730895
Title:
aio-dio-invalidate-failure test failed with event res -22 on s390x
Status in linux package in Ubuntu:
Triaged
Bug description:
This bug is for tracking purpose, this is not a regression for current
cycle as this issue exists for a long time.
It can be reproduced on zVM, zKVM and Ubuntu on LPAR
Steps:
1. git clone --depth=1 https://github.com/autotest/autotest-client-tests.git
2. make -C autotest-client-tests/aio_dio_bugs/src
3. sudo ./autotest-client-tests/aio_dio_bugs/src/aio-dio-invalidate-failure
poo
Result:
event res -22
From the code itself, it's expecting a -EIO return value:
if (event.res == -EIO) {
printf("invalidation returned -EIO, OK\n");
exit(0);
}
The actual return value is -22, which I think is -EINVAL
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-100-generic 4.4.0-100.123
ProcVersionSignature: Ubuntu 4.4.0-100.123-generic 4.4.95
Uname: Linux 4.4.0-100-generic s390x
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code
2: ls: cannot access '/dev/snd/': No such file or directory
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: s390x
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211
not found.
CurrentDmesg:
Date: Wed Nov 8 01:57:40 2017
HibernationDevice: RESUME=UUID=f578fa27-1d57-41c9-bb1d-7ff64c1c9345
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
Lsusb: Error: command ['lsusb'] failed with exit code 1:
PciMultimedia:
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb'
ProcKernelCmdLine: root=UUID=f26894a2-496d-4891-aa9a-f66344c9
crashkernel=196M BOOT_IMAGE=0
RelatedPackageVersions:
linux-restricted-modules-4.4.0-100-generic N/A
linux-backports-modules-4.4.0-100-generic N/A
linux-firmware 1.157.13
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1730895/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1730864] Re: Shutdown crashing when connected to AC adapter
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.14 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.14 ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1730864 Title: Shutdown crashing when connected to AC adapter Status in linux package in Ubuntu: Incomplete Bug description: Hello there, I'm using Ubuntu 17.10 (fully updated) and my system is crashing at shutdown when connected to an AC adapter. The error is: Nov 6 22:16:49 rene-Inspiron-5447 kernel: [ 248.294280] [drm:atom_op_jump [amdgpu]] *ERROR* atombios stuck in loop for more than 5secs aborting Nov 6 22:16:49 rene-Inspiron-5447 kernel: [ 248.294336] [drm:amdgpu_atom_execute_table_locked [amdgpu]] *ERROR* atombios stuck executing 75A8 (len 272, WS 0, PS 4) @ 0x75F1 Nov 6 22:16:49 rene-Inspiron-5447 kernel: [ 248.294384] [drm:amdgpu_atom_execute_table_locked [amdgpu]] *ERROR* atombios stuck executing 640C (len 68, WS 0, PS 8) @ 0x6430] This behavior is only happening when my laptop is charging. When running on battery I got a clean shutdown/reboot. Already tried to run the latest kernel package (from Mainline) and the problem is exactly the same. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-16-generic 4.13.0-16.19 [modified: boot/vmlinuz-4.13.0-16-generic] ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: rene 1249 F pulseaudio /dev/snd/controlC0: rene 1249 F pulseaudio CurrentDesktop: GNOME Date: Wed Nov 8 01:00:51 2017 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=0f3b9237-1086-430d-be15-043b9ca00fd2 InstallationDate: Installed on 2017-11-06 (1 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: Dell Inc. Inspiron 5447 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic.efi.signed root=UUID=1237aa76-9a2f-4a06-8552-526f124914ff ro quiet splash acpi_backlight=intel_backlight RelatedPackageVersions: linux-restricted-modules-4.13.0-16-generic N/A linux-backports-modules-4.13.0-16-generic N/A linux-firmware 1.169 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/25/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 0MHP6R dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A10 dmi.modalias: dmi:bvnDellInc.:bvrA10:bd08/25/2016:svnDellInc.:pnInspiron5447:pvrA10:rvnDellInc.:rn0MHP6R:rvrA00:cvnDellInc.:ct8:cvrA10: dmi.product.family: 00 dmi.product.name: Inspiron 5447 dmi.product.version: A10 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1730864/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1730862] Re: package linux-image-extra-4.13.0-17-generic (not installed) failed to install/upgrade: unable to open '/lib/modules/4.13.0-17-generic/kernel/drivers/net/wireless/in
You may need to run the following from a terminal: sudo apt-get install -f sudo apt-get clean sudo apt-get update Then re-install the package or updates. If that does not resolve your issue, please mark the bug as "Confirmed" ** Changed in: linux (Ubuntu) Importance: Undecided => Low ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1730862 Title: package linux-image-extra-4.13.0-17-generic (not installed) failed to install/upgrade: unable to open '/lib/modules/4.13.0-17-generic/kernel/drivers/net/wireless/intersil/hostap/hostap.ko .dpkg-new': Operation not permitted Status in linux package in Ubuntu: Incomplete Bug description: I ran software update and agreed to report several system probblems when prompted. ProblemType: Package DistroRelease: Ubuntu 17.10 Package: linux-image-extra-4.13.0-17-generic (not installed) ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: doc4488 F pulseaudio /dev/snd/controlC1: doc4488 F pulseaudio Date: Tue Nov 7 22:40:02 2017 DuplicateSignature: package:linux-image-extra-4.13.0-17-generic:(not installed) Unpacking linux-image-extra-4.13.0-17-generic (4.13.0-17.20) ... dpkg: error processing archive /tmp/apt-dpkg-install-2jmHF3/09-linux-image-extra-4.13.0-17-generic_4.13.0-17.20_amd64.deb (--unpack): unable to open '/lib/modules/4.13.0-17-generic/kernel/drivers/net/wireless/intersil/hostap/hostap.ko.dpkg-new': Operation not permitted ErrorMessage: unable to open '/lib/modules/4.13.0-17-generic/kernel/drivers/net/wireless/intersil/hostap/hostap.ko.dpkg-new': Operation not permitted HibernationDevice: RESUME=UUID=559dcc83-cf81-43b6-b17c-e024ec829072 InstallationDate: Installed on 2016-01-18 (659 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: EVGA 122-CK-NF68 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=UUID=74393e40-c217-40dd-a9ff-e8fb9b6e4983 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: grub-pc 2.02~beta3-4ubuntu7 RfKill: SourcePackage: linux Title: package linux-image-extra-4.13.0-17-generic (not installed) failed to install/upgrade: unable to open '/lib/modules/4.13.0-17-generic/kernel/drivers/net/wireless/intersil/hostap/hostap.ko.dpkg-new': Operation not permitted UpgradeStatus: Upgraded to artful on 2017-10-23 (16 days ago) dmi.bios.date: 01/22/2008 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 6.00 PG dmi.board.name: 122-CK-NF68 dmi.board.vendor: EVGA dmi.board.version: 2 dmi.chassis.type: 3 dmi.chassis.vendor: EVGA dmi.chassis.version: 122-CK-NF68 dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd01/22/2008:svnEVGA:pn122-CK-NF68:pvr2:rvnEVGA:rn122-CK-NF68:rvr2:cvnEVGA:ct3:cvr122-CK-NF68: dmi.product.name: 122-CK-NF68 dmi.product.version: 2 dmi.sys.vendor: EVGA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1730862/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1730762] Re: 17.10 - suspend/resume failure
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.14 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.14 ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1730762 Title: 17.10 - suspend/resume failure Status in linux package in Ubuntu: Incomplete Bug description: I'm experiencing a failure in the resume process after the suspend. When I try to resume the system start, but the screen stay black while the disk seem be really busy. The only way to exit from this status is unplug the system before restart it. Let me know how to collect additional info (if necessary). Alessandro- ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-16-generic 4.13.0-16.19 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: alessandro 1948 F pulseaudio /dev/snd/controlC0: alessandro 1948 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Nov 7 22:59:45 2017 HibernationDevice: RESUME=UUID=e43cf651-e870-4c57-826f-54017ec51f13 InstallationDate: Installed on 2016-07-09 (486 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IwConfig: lono wireless extensions. enp2s5no wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 002: ID 046d:c03d Logitech, Inc. M-BT96a Pilot Optical Mouse Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Packard Bell NEC IMEDIA 5204 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=UUID=50ada02b-678c-4b91-96b4-65bcdeaf645c ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-16-generic N/A linux-backports-modules-4.13.0-16-generic N/A linux-firmware 1.169 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/14/2006 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 6.00 PG dmi.board.name: GA-8TRC410M-NF dmi.board.vendor: NEC COMPUTERS INTERNATIONAL dmi.chassis.type: 3 dmi.chassis.vendor: NEC COMPUTERS INTERNATIONAL dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd02/14/2006:svnPackardBellNEC:pnIMEDIA5204:pvrPB34310106:rvnNECCOMPUTERSINTERNATIONAL:rnGA-8TRC410M-NF:rvr:cvnNECCOMPUTERSINTERNATIONAL:ct3:cvr: dmi.product.name: IMEDIA 5204 dmi.product.version: PB34310106 dmi.sys.vendor: Packard Bell NEC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1730762/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1729389] Re: Bluetooth mouse and keyboard connects, works for a few seconds, then doesn't react
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.14 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.14 ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Importance: Medium => High ** Tags added: kernel-da-key ** Tags added: needs-bisect -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1729389 Title: Bluetooth mouse and keyboard connects, works for a few seconds, then doesn't react Status in linux package in Ubuntu: Confirmed Bug description: After upgrading from Ubuntu Gnome 17.04 to Ubuntu 17.10, bluetooth mouse and keyboard connects, works for a few seconds, then doesn't react. Bluetooth package version: 5.46-0ubuntu3 500 Please tell me which log-files to upload. Thanks --- ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2016-06-11 (509 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 (20160421) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 006: ID 04b4:5210 Cypress Semiconductor Corp. Bus 001 Device 005: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 13d3:5664 IMC Networks Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80MK Package: bluez 5.46-0ubuntu3 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=da_DK.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=UUID=ed8fbe48-3db5-4a77-ab34-f35fd1a481cc ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Tags: artful wayland-session Uname: Linux 4.13.0-16-generic x86_64 UpgradeStatus: Upgraded to artful on 2017-10-23 (11 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/01/2016 dmi.bios.vendor: LENOVO dmi.bios.version: C6CN37WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: VIUU4 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo YOGA 900-13ISK dmi.modalias: dmi:bvnLENOVO:bvrC6CN37WW:bd03/01/2016:svnLENOVO:pn80MK:pvrLenovoYOGA900-13ISK:rvnLENOVO:rnVIUU4:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoYOGA900-13ISK: dmi.product.family: IDEAPAD dmi.product.name: 80MK dmi.product.version: Lenovo YOGA 900-13ISK dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: A4:34:D9:9A:CD:FF ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN INQUIRY RX bytes:71005 acl:1028 sco:0 events:2920 errors:0 TX bytes:601922 acl:36 sco:0 commands:2468 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1729389/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1729389] Re: Bluetooth mouse and keyboard connects, works for a few seconds, then doesn't react
If v4.14 fixes the bug, can you give the latest upstream 4.13 kernel a test, which is: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.13.12/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1729389 Title: Bluetooth mouse and keyboard connects, works for a few seconds, then doesn't react Status in linux package in Ubuntu: Confirmed Bug description: After upgrading from Ubuntu Gnome 17.04 to Ubuntu 17.10, bluetooth mouse and keyboard connects, works for a few seconds, then doesn't react. Bluetooth package version: 5.46-0ubuntu3 500 Please tell me which log-files to upload. Thanks --- ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2016-06-11 (509 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 (20160421) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 006: ID 04b4:5210 Cypress Semiconductor Corp. Bus 001 Device 005: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 13d3:5664 IMC Networks Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80MK Package: bluez 5.46-0ubuntu3 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=da_DK.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=UUID=ed8fbe48-3db5-4a77-ab34-f35fd1a481cc ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Tags: artful wayland-session Uname: Linux 4.13.0-16-generic x86_64 UpgradeStatus: Upgraded to artful on 2017-10-23 (11 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/01/2016 dmi.bios.vendor: LENOVO dmi.bios.version: C6CN37WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: VIUU4 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo YOGA 900-13ISK dmi.modalias: dmi:bvnLENOVO:bvrC6CN37WW:bd03/01/2016:svnLENOVO:pn80MK:pvrLenovoYOGA900-13ISK:rvnLENOVO:rnVIUU4:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoYOGA900-13ISK: dmi.product.family: IDEAPAD dmi.product.name: 80MK dmi.product.version: Lenovo YOGA 900-13ISK dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: A4:34:D9:9A:CD:FF ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN INQUIRY RX bytes:71005 acl:1028 sco:0 events:2920 errors:0 TX bytes:601922 acl:36 sco:0 commands:2468 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1729389/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1651635] Re: XPS 13 9360 trackpad locks into scroll mode
Solid hour so far , zero problems. Usually the problem would have already happened on 17.10. I believe there is a bug, that's not to say some people don't have a hardware issue, it doesn't seem to apply in my case. I'm rolling my install on this notebook back to 16.04 lts and I will report back if it happens again, if nobody hears from me in days or weeks, it means moving back to 16 resolved my problem. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1651635 Title: XPS 13 9360 trackpad locks into scroll mode Status in Dell Sputnik: Confirmed Status in Linux: Unknown Status in linux package in Ubuntu: New Bug description: Hello, I'm running Linux on a Dell XPS 13 (9360) laptop. I find that upwards of 10 times per day, my trackpad gets stuck in "scrolling" mode. Moving the trackpad won't move the X windows pointer, but will send scrolling events to the foreground window. When the trackpad is locked in this mode, the touchscreen will still let me move the mouse cursor, as will an external mouse. On Ubuntu 16.04 freshly restored from the Dell recovery image, I find that it's often difficult to get the trackpad to recover. I do find that the issue happens less frequently on Dell's build of Ubuntu 16.04 than on other linux distributions and versions, but it still happens enough to significantly impact my ability to do productive work. The issue does not occur when running Windows 10 on the same device. I suspect that the issue may be related to palm detection or misdetecting the user's palm as a gesture to enable scrolling mode, but have no proof for this. It seems that I'm often able to reproduce the issue by brushing the trackpad with my right palm. On Ubuntu 16.10, with the latest shipped 4.8 kernel (Linux szx 4.8.0-30-generic #32-Ubuntu SMP Fri Dec 2 03:43:27 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux), with the extra xinput configuration below, I am able to get the trackpad to recover, simply by clicking the trackpad: /usr/share/X11/xorg.conf.d/99-libinput.conf: Section "InputClass" Identifier "libinput touchpad catchall" Driver "libinput" MatchIsTouchpad "on" MatchDevicePath "/dev/input/event*" Option "Tapping" "True" Option "DisableWhileTyping" "True" Option "NaturalScrolling" "False" Option "AccelProfile" "adaptive" Option "AccelSpeed" "0.05" Option "MiddleEmulation" "True" Option "ScrollMethod" "twofinger" # Option "ClickMethod" "clickfinger" Option "ClickMethod" "buttonareas" EndSection In my experience, the problem manifests using both the Xorg synaptics driver and the Xorg libinput driver. root@szx:/etc/modprobe.d# xinput list ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ Logitech M570 id=10 [slave pointer (2)] ⎜ ↳ DLL075B:01 06CB:76AF Touchpad id=13 [slave pointer (2)] ⎜ ↳ ELAN Touchscreenid=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Buttonid=8[slave keyboard (3)] ↳ Sleep Buttonid=9[slave keyboard (3)] ↳ Integrated_Webcam_HDid=12 [slave keyboard (3)] ↳ Intel Virtual Button driver id=14 [slave keyboard (3)] ↳ Intel HID eventsid=15 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=16 [slave keyboard (3)] ↳ Dell WMI hotkeysid=17 [slave keyboard (3)] root@szx:/etc/modprobe.d# To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1651635/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1732238] Re: arm64: Unfair rwlock can stall the system
** Also affects: linux (Ubuntu Artful) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Changed in: linux (Ubuntu Artful) Status: New => Confirmed ** Changed in: linux (Ubuntu) Assignee: (unassigned) => dann frazier (dannf) ** Changed in: linux (Ubuntu Artful) Assignee: (unassigned) => dann frazier (dannf) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1732238 Title: arm64: Unfair rwlock can stall the system Status in linux package in Ubuntu: Confirmed Status in linux source package in Artful: Confirmed Bug description: [Impact] There is a long-standing upstream bug with the ARM64 specific implementation of RW locks. The implementation can starve writers under lock contention leading to RCU stalls and general system instability. [Test Case] $ stress-ng --kill 0 -t 300 -v You'll see the console fill with messages like: [ 2534.423119] INFO: rcu_sched detected stalls on CPUs/tasks: [ 2534.428606]192-...: (1 ticks this GP) idle=b6e/140/0 softirq=578/578 fqs=6770 [ 2534.437029](detected by 0, t=15005 jiffies, g=1479, c=1478, q=473) [ 2714.623691] INFO: rcu_sched detected stalls on CPUs/tasks: [ 2714.629181]192-...: (1 ticks this GP) idle=b6e/140/0 softirq=578/578 fqs=12819 [ 2714.637692](detected by 116, t=60058 jiffies, g=1479, c=1478, q=1736) [ 2747.216955] watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kworker/0:5:1464] [ 2775.399061] watchdog: BUG: soft lockup - CPU#13 stuck for 123s! [systemd-network:2936] [Regression Risk] TBD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1732238/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1728244] Re: Touchpad stops working after reboot on Apollo Lake
Hi, For your information I already own a recent Jumper ezbook pro 3 v4 with 09/30/2017 BIOS version. I have the same issue with Touchpad that is only solved when using kernel v4.14-rc7. If I can help with some tests let me know. BTW I also have an issue with resuming from suspend. In short resuming starts but screen stays black and no mater what I do I can't use my laptop and have to force a power off. I don't think it is related but who knows... Regards -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1728244 Title: Touchpad stops working after reboot on Apollo Lake Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Bug description: On the Jumper EZBook 3 Pro (V4) laptop, using an Apollo Lake N3450 processor, if you install Ubuntu 17.10 (or less) with isorespin and use rEFInd as bootloader (this is the only way to get linux booting on this laptop) everything works out of the box, but after a reboot or two the touchpad stops working. Both in Ubuntu and Windows 10. The only way to restore functionality is to boot from usb key ubuntu 17.10 respined, or disassemble laptop and detach-reattach battery cable. This is mesg | grep i2c_hid: [ 2056.460636] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (27/34) [ 3077.604699] i2c_hid i2c-SYNA3602:00: failed to reset device. [ 3077.605473] dpm_run_callback(): i2c_hid_resume+0x0/0xe0 [i2c_hid] returns -61 [ 3080.468156] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (27/34) uname -rvps Linux 4.10.0-32-generic #36~16.04.1-Ubuntu SMP Wed Aug 9 09:19:02 UTC 2017 x86_64 There has to be a bug in the kernel. Any way to avoid this? To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1728244/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1731163] Re: Trackpoint device not working by default on Thinkpad L570
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.14 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.14 ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Triaged ** Tags added: kernel-da-key -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1731163 Title: Trackpoint device not working by default on Thinkpad L570 Status in linux package in Ubuntu: Triaged Bug description: Installing Ubuntu 17.10 on a ThinkPad L570 (L470 should be the same in this regard) leaves the trackpoint as well as the trackpoint buttons in a non-working state. Most probably, it is not correctly detected on startup; dmesg shows kernel: [ 2.997182 ] input: AlpsPS/2 ALPS GlidePoint as /devices/platform/i8042/serio1/input/input6 As far as I understand it, "GlidePoint" only refers to a touch pad without track point. All events coming from the track point are consequently actively discarded, seen in dmesg as kernel: [ 2279.323441 ] psmouse serio1: alps: Rejected trackstick packet from non DualPoint device Searching for this problem I found this kernel developer discussion which seems related: https://patchwork.kernel.org/patch/9941661/ As suggested by one of the kernel developers there, I added "psmouse.proto=imps" as a kernel boot parameter. The touch pad and track point now show up in the system log as input: PS/2 Generic Mouse as /devices/platform/i8042/serio1/input/input6 And it works well now, just as it should. I also noted that the touch pad became a lot more usable at the same time. Previously (with the default installation) it was lagging and could produce pseudo clicks at random. I am submitting this report here in order to help improve the hardware detection in Ubuntu / linux kernel. Ubuntu version: 17.10 Kernel version: 4.13.0.16.17 Default GNOME desktop, Wayland, etc, just as it comes in the default install --- ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dirichs 896 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-11-07 (1 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 5986:111c Acer, Inc Bus 001 Device 004: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20J8CTO1WW Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed root=UUID=f2a92db0-5f37-4d70-b878-a4ba4c80e890 ro quiet splash psmouse.proto=imps vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 RelatedPackageVersions: linux-restricted-modules-4.13.0-16-generic N/A linux-backports-modules-4.13.0-16-generic N/A linux-firmware 1.169 Tags: wayland-session artful Uname: Linux 4.13.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/12/2017 dmi.bios.vendor: LENOVO dmi.bios.version: N1XET43W (1.21 ) dmi.board.asset.tag: Not Available dmi.board.name: 20J8CTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1XET43W(1.21):bd07/12/2017:svnLENOVO:pn20J8CTO1WW:pvrThinkPadL570:rvnLENOVO:rn20J8CTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad L570 dmi.product.name: 20J8CTO1WW dmi.product.version: ThinkPad L570 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1731163/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1729030] Re: [regression] Kernel crash in bluetooth with Bose QC35
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.14 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.14 ** Tags added: kernel-da-key -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1729030 Title: [regression] Kernel crash in bluetooth with Bose QC35 Status in linux package in Ubuntu: Incomplete Bug description: Bose QC35 with latest firmware Ubuntu 17.10 This is a regression from 17.04 Ubuntu Gnome. In 17.04, you had to temporarily disable `le` mode to pair but after pairing, everything worked flawlessly. In 17.10, pairing works out of the box, but the following issue appears: After a few hours of being connected, the connection between bose qc35 and Ubuntu seemingly breaks: the headphones don't play any sound anymore. re-pairing fails and restarting the headphones doesn't fix the issue. It seems bluetoothd crashed conmpletely since `bluetoothctl` doesn't work anymore.. Restarting Ubuntu fixes the issue. syslog contains a bunch of kernel stacktraces including a nullpointer dereference.. Oct 31 16:41:06 travers dbus-daemon[3888]: Activating via systemd: service name='org.bluez.obex' unit='dbus-org.bluez.obex.service' Oct 31 16:41:06 travers systemd[3874]: Starting Bluetooth OBEX service... Oct 31 16:41:06 travers bluetoothd[1128]: Failed to set mode: Busy (0x0a) Oct 31 16:41:06 travers obexd[29587]: OBEX daemon 5.46 Oct 31 16:41:06 travers dbus-daemon[3888]: Successfully activated service 'org.bluez.obex' Oct 31 16:41:06 travers systemd[3874]: Started Bluetooth OBEX service. Oct 31 16:41:06 travers bluetoothd[1128]: Failed to set mode: Busy (0x0a) Oct 31 16:41:06 travers bluetoothd[1128]: Failed to set mode: Busy (0x0a) Oct 31 16:41:12 travers kernel: Bluetooth: hci0 link tx timeout Oct 31 16:41:12 travers kernel: Bluetooth: hci0 killing stalled connection 04:52:c7:60:d6:2c Oct 31 16:41:12 travers acpid[1126]: input device has been disconnected, fd 24 Oct 31 16:41:12 travers kernel: Bluetooth: hci0 link tx timeout Oct 31 16:41:12 travers kernel: Bluetooth: hci0 killing stalled connection 04:52:c7:60:d6:2c Oct 31 16:41:14 travers bluetoothd[1128]: Disconnecting failed: already disconnected Oct 31 16:41:18 travers bluetoothd[1128]: Close: Connection timed out (110) Oct 31 16:41:18 travers kernel: Bluetooth: hci0 link tx timeout Oct 31 16:41:18 travers kernel: Bluetooth: hci0 killing stalled connection 04:52:c7:60:d6:2c Oct 31 16:41:20 travers bluetoothd[1128]: Abort: Connection timed out (110) Oct 31 16:41:20 travers kernel: Bluetooth: hci0 link tx timeout Oct 31 16:41:20 travers kernel: Bluetooth: hci0 killing stalled connection 04:52:c7:60:d6:2c Oct 31 16:41:20 travers kernel: Bluetooth: hci0 link tx timeout Oct 31 16:41:20 travers kernel: Bluetooth: hci0 killing stalled connection 04:52:c7:60:d6:2c Oct 31 16:41:20 travers dbus[1074]: [system] Rejected send message, 3 matched rules; type="method_return", sender=":1.86" (uid=1000 pid=3997 comm="/usr/bin/pulseaudio --start --log-target=syslog ") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.7" (uid=0 pid=1128 comm="/usr/lib/bluetooth/bluetoothd ") Oct 31 16:41:20 travers gsd-media-keys[4157]: Unable to get default sink Oct 31 16:41:32 travers kernel: sysfs: cannot create duplicate filename '/devices/pci:00/:00:14.0/usb1/1-6/1-6:1.0/bluetooth/hci0/hci0:256' Oct 31 16:41:32 travers kernel: [ cut here ] Oct 31 16:41:32 travers kernel: WARNING: CPU: 2 PID: 19117 at /build/linux-XO_uEE/linux-4.13.0/fs/sysfs/dir.c:31 sysfs_warn_dup+0x56/0x70 Oct 31 16:41:32 travers kernel: Modules linked in: rfcomm ip6t_MASQUERADE nf_nat_masquerade_ipv6 ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 xt_comment zfs(PO) zunicode(PO) zavl(PO) zcommon(PO) znvpair(PO) spl(O) pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) ccm cmac xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack libcrc32c ipt_REJECT nf_reject_ipv4 xt_tcpudp bridge stp llc ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter bnep nls_iso8859_1 arc4 hid_alps snd_hda_codec_hdmi intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm dell_rbtn dell_laptop iwlmvm irqbypass dell_smm_hwmon mac80211 crct10dif_pclmul crc32_pclmul snd_hda_codec_realtek
[Kernel-packages] [Bug 1724796] Re: Picture is heavily malformed
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.14 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.14 ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1724796 Title: Picture is heavily malformed Status in linux package in Ubuntu: Incomplete Bug description: On boot screen with disk decrypt password and gdm are heavily deformed (check attachment). After login wayland session is also deformed, then if I logout and login to Xorg, picture is fine. After that if I logout and login back to Wayland session picture is also fine. GDM -> https://imgur.com/a/MhHbd Disk decrypt -> https://imgur.com/a/UP0rL ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-lowlatency 4.13.4 Uname: Linux 4.13.0-16-lowlatency x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Oct 19 12:29:31 2017 DistUpgraded: 2017-10-19 11:49:45,543 DEBUG icon theme changed, re-reading DistroCodename: artful DistroVariant: ubuntu DkmsStatus: virtualbox, 5.1.30, 4.10.0-37-generic, x86_64: installed virtualbox, 5.1.30, 4.13.0-16-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480] [1002:67df] (rev e7) (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. Ellesmere [Radeon RX 470/480/570/580] [1682:c580] InstallationDate: Installed on 2017-08-25 (54 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: ASUS All Series ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-lowlatency root=UUID=23900d78-4c59-4f7b-a317-4dd19bd68a7e ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to artful on 2017-10-19 (0 days ago) dmi.bios.date: 11/11/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2801 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97-AR dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2801:bd11/11/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-AR:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1 version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 1:17.2.2-0~z~padoka0 version.libgl1-mesa-glx: libgl1-mesa-glx 1:17.2.2-0~z~padoka0 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1724796/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1724796] Re: Picture is heavily malformed
Also, did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem? ** Tags added: kernel-da-key -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1724796 Title: Picture is heavily malformed Status in linux package in Ubuntu: Incomplete Bug description: On boot screen with disk decrypt password and gdm are heavily deformed (check attachment). After login wayland session is also deformed, then if I logout and login to Xorg, picture is fine. After that if I logout and login back to Wayland session picture is also fine. GDM -> https://imgur.com/a/MhHbd Disk decrypt -> https://imgur.com/a/UP0rL ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-lowlatency 4.13.4 Uname: Linux 4.13.0-16-lowlatency x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Oct 19 12:29:31 2017 DistUpgraded: 2017-10-19 11:49:45,543 DEBUG icon theme changed, re-reading DistroCodename: artful DistroVariant: ubuntu DkmsStatus: virtualbox, 5.1.30, 4.10.0-37-generic, x86_64: installed virtualbox, 5.1.30, 4.13.0-16-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480] [1002:67df] (rev e7) (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. Ellesmere [Radeon RX 470/480/570/580] [1682:c580] InstallationDate: Installed on 2017-08-25 (54 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: ASUS All Series ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-lowlatency root=UUID=23900d78-4c59-4f7b-a317-4dd19bd68a7e ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to artful on 2017-10-19 (0 days ago) dmi.bios.date: 11/11/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2801 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97-AR dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2801:bd11/11/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-AR:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1 version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 1:17.2.2-0~z~padoka0 version.libgl1-mesa-glx: libgl1-mesa-glx 1:17.2.2-0~z~padoka0 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1724796/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1731455] Re: generic/166 test for btrfs from xfstests will hang
** Changed in: linux (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1731455 Title: generic/166 test for btrfs from xfstests will hang Status in linux package in Ubuntu: Triaged Bug description: From the log you will see it stuck after generic/165 for the btrfs filesystem: 08:40:48 DEBUG| [stdout] generic/163 16s 08:41:01 DEBUG| [stdout] generic/164 12s 08:41:15 DEBUG| [stdout] generic/165 14s And it will be killed by the time-out setting. This issue can be spotted across different kernel, and it looks like a test case issue. Possible fix could be found in upstream repo: https://git.kernel.org/pub/scm/fs/xfs/xfstests-dev.git/commit/tests/generic/166?id=132f37916d2c5f64b857ecaf2072ce7891c5f5ba ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.13.0-17-lowlatency 4.13.0-17.20~16.04.1 ProcVersionSignature: User Name 4.13.0-17.20~16.04.1-lowlatency 4.13.8 Uname: Linux 4.13.0-17-lowlatency x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 Date: Fri Nov 10 10:11:21 2017 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-hwe-edge UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1731455/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1731679] Re: package linux-image-4.4.0-98-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128
You may need to run the following from a terminal: sudo apt-get install -f sudo apt-get clean sudo apt-get update Then re-install the package or updates. If that does not resolve your issue, please mark the bug as "Confirmed" ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1731679 Title: package linux-image-4.4.0-98-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 Status in linux package in Ubuntu: Incomplete Bug description: There were upgrades waiting for me to restart this laptop. Laptop crashed, forcing the restart, then the bug reports started rolling in ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-98-generic (not installed) ProcVersionSignature: Ubuntu 4.4.0-97.120-generic 4.4.87 Uname: Linux 4.4.0-97-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: spnorris 1838 F pulseaudio Date: Mon Nov 6 14:20:28 2017 ErrorMessage: subprocess new pre-installation script returned error exit status 128 HibernationDevice: RESUME=UUID=ba95494f-3afb-4b2e-8de8-6361d815ae50 InstallationDate: Installed on 2014-06-22 (1238 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Dell Inc. Inspiron 1545 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-97-generic root=UUID=e5ef2fc4-7884-434f-9a5a-e70fd31fe4a7 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.14 SourcePackage: linux Title: package linux-image-4.4.0-98-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 UpgradeStatus: Upgraded to xenial on 2017-06-10 (154 days ago) dmi.bios.date: 10/23/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: A13 dmi.board.name: 0G848F dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA13:bd10/23/2009:svnDellInc.:pnInspiron1545:pvr:rvnDellInc.:rn0G848F:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Inspiron 1545 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1731679/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1731527] Re: Elantech touchpad never work
** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1731527 Title: Elantech touchpad never work Status in linux package in Ubuntu: Incomplete Bug description: Since I installed Ubuntu 17.10, the touchpad has never worked. I read a lot in forums, but no one found a solution. Please, solve my problem ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-16-generic 4.13.0-16.19 [modified: boot/vmlinuz-4.13.0-16-generic] ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: lorenzo1135 F pulseaudio /dev/snd/controlC0: lorenzo1135 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Nov 10 19:11:04 2017 InstallationDate: Installed on 2017-11-10 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: LENOVO 80XV ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed root=UUID=02baf904-cbdf-4796-a6f8-f8290963b313 ro i8042.kbdreset=1 RelatedPackageVersions: linux-restricted-modules-4.13.0-16-generic N/A linux-backports-modules-4.13.0-16-generic N/A linux-firmware 1.169 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/13/2017 dmi.bios.vendor: LENOVO dmi.bios.version: 5PCN17WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 320-15AST dmi.modalias: dmi:bvnLENOVO:bvr5PCN17WW:bd07/13/2017:svnLENOVO:pn80XV:pvrLenovoideapad320-15AST:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoideapad320-15AST: dmi.product.family: ideapad 320-15AST dmi.product.name: 80XV dmi.product.version: Lenovo ideapad 320-15AST dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1731527/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1731207] Re: Ubuntu 17.10 keeps freezing
Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem? Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.14 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.14 ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1731207 Title: Ubuntu 17.10 keeps freezing Status in linux package in Ubuntu: Incomplete Bug description: It keeps freezing. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-16-generic 4.13.0-16.19 [modified: boot/vmlinuz-4.13.0-16-generic] ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: shoezmann 1367 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Nov 9 12:36:25 2017 InstallationDate: Installed on 2017-11-08 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: Hewlett-Packard HP ProBook 4530s ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=UUID=5db6ea12-61a9-4992-a1ef-06047ec7ac61 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-16-generic N/A linux-backports-modules-4.13.0-16-generic N/A linux-firmware 1.169 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/18/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68SRR Ver. F.0A dmi.board.name: 167C dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 22.1F dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68SRRVer.F.0A:bd07/18/2011:svnHewlett-Packard:pnHPProBook4530s:pvrA0001C02:rvnHewlett-Packard:rn167C:rvrKBCVersion22.1F:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.name: HP ProBook 4530s dmi.product.version: A0001C02 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1731207/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
