[Kernel-packages] [Bug 1740309] Re: user space process hangs when reading partition table of disk
*** This bug is a duplicate of bug 1726519 *** https://bugs.launchpad.net/bugs/1726519 ** This bug has been marked a duplicate of bug 1726519 Unable to handle kernel NULL pointer dereference at isci_task_abort_task -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1740309 Title: user space process hangs when reading partition table of disk Status in linux package in Ubuntu: Confirmed Bug description: user space process as in parted or fdisk or update-grub2 that read partition tables freeze on my system: /dev/sda/ GPT disk with efi, swap and ubuntu artful partition /dev/sdb old style partition table with one ext4 partition /dev/sdc GPT disk with efi partition, windows 10 I.e. if I run as root : # fdisk -l Disk /dev/sda: 232,9 GiB, 250059350016 bytes, 488397168 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: gpt Disk identifier: 56FF6AB0-076F-483C-890F-EC4B4FAF6313 DeviceStart End Sectors Size Type /dev/sda1 2048 2000895 1998848 976M EFI System /dev/sda2 2000896 1383 7999488 3,8G Linux swap /dev/sda3 1384 488396799 478396416 228,1G Linux filesystem Disk /dev/sdb: 489,1 GiB, 525112713216 bytes, 1025610768 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x2f11f9c4 Device Boot StartEndSectors Size Id Type /dev/sdb12048 1025609727 1025607680 489G 83 Linux <...process hangs here forever...> With gdb I stepped through fdisk -l and saw that the call to open ('dev/sdc'..) never returns. -- ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D3p: andreas1807 F...m pulseaudio /dev/snd/controlC0: andreas1807 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 HibernationDevice: RESUME=UUID=8a7a6077-0a3e-4641-8f15-bd6f09826510 InstallationDate: Installed on 2017-12-26 (1 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) IwConfig: lono wireless extensions. enp8s0no wireless extensions. enp12s0 no wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: linux-image-4.13.0-21-generic 4.13.0-21.24 PackageArchitecture: amd64 ProcFB: 0 radeondrmfb 1 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-21-generic.efi.signed root=UUID=4f18ad67-a4f0-4e03-b061-66615751538e ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13 RelatedPackageVersions: linux-restricted-modules-4.13.0-21-generic N/A linux-backports-modules-4.13.0-21-generic N/A linux-firmware 1.169.1 RfKill: Tags: artful Uname: Linux 4.13.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/09/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.80 dmi.board.name: EP2C602 dmi.board.vendor: ASRock 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.:bvrP1.80:bd12/09/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnEP2C602:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1740309/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1736393] Re: [Artful][Wyse 3040] System hang when trying to enable an offlined CPU core
** Changed in: linux (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1736393 Title: [Artful][Wyse 3040] System hang when trying to enable an offlined CPU core Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem package in Ubuntu: Invalid Status in linux source package in Xenial: Invalid Status in linux-oem source package in Xenial: Fix Released Bug description: 1. disable cpu[1-3] $ echo 0 > /sys/devices/system/cpu/cpu[1-3]/online 2. enable cpu[1-3] $ echo 1 > /sys/devices/system/cpu/cpu[1-3]/online System will hang on step 2. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1736393/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1733281] Re: ubuntu/xr-usb-serial didn't get built in zesty and artful
** Changed in: linux (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1733281 Title: ubuntu/xr-usb-serial didn't get built in zesty and artful Status in linux package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Committed Status in linux-azure-edge source package in Xenial: Fix Released Bug description: The ubuntu/xr-usb-serial is expected to be built for i386 and x86_64, and in ubuntu/Makefile it says: ifneq ($(filter $(ARCH), i386 x86_64),) obj-y += xr-usb-serial/ endif Since ARCH is x86 for both i386 and x86_64, this condition will never be true thus the module will never get a chance to be built. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1733281/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1255428] Re: 8086:0116 [Lenovo IdeaPad Z570] LCD brightness control keys and widget do not work on Intel Graphics
On 14.04, this link fixed it for me: https://itsfoss.com/fix-brightness- ubuntu-1310/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1255428 Title: 8086:0116 [Lenovo IdeaPad Z570] LCD brightness control keys and widget do not work on Intel Graphics Status in linux package in Ubuntu: Expired Bug description: After upgrading to Saucy, on my Lenovo IdeaPad Z570 with Intel HD Graphics 3000, it is no longer possible to control the LCD brightness using the hardware brightness control keys. Likewise for the KDE power management settings or the battery icon on my Kubuntu Plasma tray. (I don't use GNOME/Unity.) Until Raring I did not have this problem. WORKAROUND: At a terminal: echo 150 | sudo tee /sys/class/backlight/intel_backlight/brightness where 150 is on the scale of 0 to whatever is given within /sys/class/backlight/intel_backlight/max_brightness. Based on this I wrote a GUI which however needs to be run using sudo/kdesudo/gksudo. I have attached it. --- ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 DistroRelease: Ubuntu 13.10 InstallationDate: Installed on 2013-10-19 (38 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MarkForUpload: True Package: xserver-xorg-video-intel 2:2.99.904-0ubuntu2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Tags: saucy Uname: Linux 3.11.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo --- ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: samjnaa1717 F pulseaudio DistroRelease: Ubuntu 13.10 HibernationDevice: RESUME=UUID=ba00d992-e43e-4bce-8689-9647370add15 InstallationDate: Installed on 2013-10-19 (117 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: LENOVO HuronRiver Platform MarkForUpload: True Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=(hd0,msdos9)/vmlinuz root=/dev/sda9 ro quiet splash ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10 RelatedPackageVersions: linux-restricted-modules-3.11.0-15-generic N/A linux-backports-modules-3.11.0-15-generic N/A linux-firmware 1.116 StagingDrivers: rts5139 Tags: saucy staging Uname: Linux 3.11.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 02/22/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 45CN28WW dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Emerald Lake dmi.board.vendor: LENOVO dmi.board.version: FAB1 dmi.chassis.asset.tag: Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnLENOVO:bvr45CN28WW:bd02/22/2011:svnLENOVO:pnHuronRiverPlatform:pvrIdeapadZ570:rvnLENOVO:rnEmeraldLake:rvrFAB1:cvnLENOVO:ct10:cvr0.1: dmi.product.name: HuronRiver Platform dmi.product.version: Ideapad Z570 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1255428/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1255428] Re: 8086:0116 [Lenovo IdeaPad Z570] LCD brightness control keys and widget do not work on Intel Graphics
On 16.04 (and 14.04), the following link fixed it for me: https://itsfoss.com/fix-brightness-ubuntu-1310/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1255428 Title: 8086:0116 [Lenovo IdeaPad Z570] LCD brightness control keys and widget do not work on Intel Graphics Status in linux package in Ubuntu: Expired Bug description: After upgrading to Saucy, on my Lenovo IdeaPad Z570 with Intel HD Graphics 3000, it is no longer possible to control the LCD brightness using the hardware brightness control keys. Likewise for the KDE power management settings or the battery icon on my Kubuntu Plasma tray. (I don't use GNOME/Unity.) Until Raring I did not have this problem. WORKAROUND: At a terminal: echo 150 | sudo tee /sys/class/backlight/intel_backlight/brightness where 150 is on the scale of 0 to whatever is given within /sys/class/backlight/intel_backlight/max_brightness. Based on this I wrote a GUI which however needs to be run using sudo/kdesudo/gksudo. I have attached it. --- ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 DistroRelease: Ubuntu 13.10 InstallationDate: Installed on 2013-10-19 (38 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MarkForUpload: True Package: xserver-xorg-video-intel 2:2.99.904-0ubuntu2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Tags: saucy Uname: Linux 3.11.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo --- ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: samjnaa1717 F pulseaudio DistroRelease: Ubuntu 13.10 HibernationDevice: RESUME=UUID=ba00d992-e43e-4bce-8689-9647370add15 InstallationDate: Installed on 2013-10-19 (117 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: LENOVO HuronRiver Platform MarkForUpload: True Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=(hd0,msdos9)/vmlinuz root=/dev/sda9 ro quiet splash ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10 RelatedPackageVersions: linux-restricted-modules-3.11.0-15-generic N/A linux-backports-modules-3.11.0-15-generic N/A linux-firmware 1.116 StagingDrivers: rts5139 Tags: saucy staging Uname: Linux 3.11.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 02/22/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 45CN28WW dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Emerald Lake dmi.board.vendor: LENOVO dmi.board.version: FAB1 dmi.chassis.asset.tag: Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnLENOVO:bvr45CN28WW:bd02/22/2011:svnLENOVO:pnHuronRiverPlatform:pvrIdeapadZ570:rvnLENOVO:rnEmeraldLake:rvrFAB1:cvnLENOVO:ct10:cvr0.1: dmi.product.name: HuronRiver Platform dmi.product.version: Ideapad Z570 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1255428/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1744884] [NEW] OverlayFS not writeable
Public bug reported: A customer of ours has a collection of servers in a test environment which mounts production data via NFS. The NFS is then mounted as the lower directory of an overlayfs, $directory_workdir is mounted as the workdir, and $directory_cow is mounted as the upper directory. However, as of recent, the customer can not edit any data unless the necessary files are 'touch'ed first (or if you use vim, force-written). "uname -a" returns "Linux 4.4.0-104-generic #127-Ubuntu SMP Mon Dec 11 12:16:42 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux". ** 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/1744884 Title: OverlayFS not writeable Status in linux package in Ubuntu: New Bug description: A customer of ours has a collection of servers in a test environment which mounts production data via NFS. The NFS is then mounted as the lower directory of an overlayfs, $directory_workdir is mounted as the workdir, and $directory_cow is mounted as the upper directory. However, as of recent, the customer can not edit any data unless the necessary files are 'touch'ed first (or if you use vim, force-written). "uname -a" returns "Linux 4.4.0-104-generic #127-Ubuntu SMP Mon Dec 11 12:16:42 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1744884/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1686107] Re: Latest kernel update gets stuck
I had a similar issue while installing updates on my Ubuntu 17.10 x64 on Lenovo Thinkpad P50 (Nvidia Quadro M1000). The failing to install kernel was 4.13.0-31. I've managed to fix it by the steps from #11. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1686107 Title: Latest kernel update gets stuck Status in linux package in Ubuntu: Confirmed Status in linux source package in Zesty: Confirmed Bug description: I just installed the latest kernel update (4.10.0-20), but it gets stuck on the following line: Examining /etc/kernel/header_postinst.d. run-parts: executing /etc/kernel/header_postinst.d/dkms 4.10.0-20-generic /boot/vmlinuz-4.10.0-20-generic I can't finish the update process now. I am also unable to install any software because dpkg informs it's corrupted. But running sudo dpkg --configure -a causes it to get stuck again on the line above. More info is provided here on this AskUbuntu question: https://askubuntu.com/questions/908676/linux-kernel-update-stuck I hope I reported this on the right location. I am running Ubuntu GNOME 17.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1686107/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1744121] Re: Artful update to 4.13.14 stable release
** Changed in: linux (Ubuntu) Status: New => 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/1744121 Title: Artful update to 4.13.14 stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Artful: New Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The 4.13.14 upstream stable patch set is now available. It should be included in the Ubuntu kernel as well. git://git.kernel.org/ TEST CASE: TBD The following patches from the 4.13.14 stable release shall be applied: * ppp: fix race in ppp device destruction * gso: fix payload length when gso_size is zero * ipv4: Fix traffic triggered IPsec connections. * ipv6: Fix traffic triggered IPsec connections. * netlink: do not set cb_running if dump's start() errs * net: call cgroup_sk_alloc() earlier in sk_clone_lock() * macsec: fix memory leaks when skb_to_sgvec fails * l2tp: check ps->sock before running pppol2tp_session_ioctl() * tun: call dev_get_valid_name() before register_netdevice() * netlink: fix netlink_ack() extack race * sctp: add the missing sock_owned_by_user check in sctp_icmp_redirect * tcp/dccp: fix ireq->opt races * packet: avoid panic in packet_getsockopt() * geneve: Fix function matching VNI and tunnel ID on big-endian * net: bridge: fix returning of vlan range op errors * soreuseport: fix initialization race * ipv6: flowlabel: do not leave opt->tot_len with garbage * sctp: full support for ipv6 ip_nonlocal_bind & IP_FREEBIND * tcp/dccp: fix lockdep splat in inet_csk_route_req() * tcp/dccp: fix other lockdep splats accessing ireq_opt * net: dsa: check master device before put * net/unix: don't show information about sockets from other namespaces * tap: double-free in error path in tap_open() * net/mlx5: Fix health work queue spin lock to IRQ safe * net/mlx5e: Properly deal with encap flows add/del under neigh update * ipip: only increase err_count for some certain type icmp in ipip_err * ip6_gre: only increase err_count for some certain type icmpv6 in ip6gre_err * ip6_gre: update dst pmtu if dev mtu has been updated by toobig in __gre6_xmit * tcp: refresh tp timestamp before tcp_mtu_probe() * tap: reference to KVA of an unloaded module causes kernel panic * tun: allow positive return values on dev_get_valid_name() call * sctp: reset owner sk for data chunks on out queues when migrating a sock * net_sched: avoid matching qdisc with zero handle * l2tp: hold tunnel in pppol2tp_connect() * tun/tap: sanitize TUNSETSNDBUF input * ipv6: addrconf: increment ifp refcount before ipv6_del_addr() * tcp: fix tcp_mtu_probe() vs highest_sack * mac80211: accept key reinstall without changing anything * mac80211: use constant time comparison with keys * mac80211: don't compare TKIP TX MIC key in reinstall prevention * usb: usbtest: fix NULL pointer dereference * Input: ims-psu - check if CDC union descriptor is sane * EDAC, sb_edac: Don't create a second memory controller if HA1 is not present * dmaengine: dmatest: warn user when dma test times out * Linux 4.13.14 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1744121/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1566302] Re: Ubuntu 16.04: Suspend freezes the system after upgrade to linux image 4.4.0-16
Same problem. However, I noticed that the issue disappears when you modify the Dell firmware settings, e.g. updating the firmware, changing settings, ... I reproduced this solution a couple of times. Then, the problem re-appears periodically (perhaps after a kernel upgrade?). Moreover, I suspect that this can be related to the "fastboot" feature in the firmware. In my case it is activated. Maybe, after changing the firmware, the system performs a full boot procedure, correcting any system issue related to suspension. In the normal boot, however, these checks are not performed, so the issue appears again and again. Can you confirm if this option is activated also for you? Maybe you can try to disable it and see if the suspension issue disappears. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1566302 Title: Ubuntu 16.04: Suspend freezes the system after upgrade to linux image 4.4.0-16 Status in linux package in Ubuntu: Won't Fix Bug description: I'm using ubuntu 16.04 on a XPS 15 9550. Suspend/resume worked flawlessly with linux image 4.4.0-15, and after standard upgrade yesterday (5/04/2016) which installed image 4.4.0-16, the system freezes when attempting a suspend. I get no response from the system (nor keyboard, nor screen, nor touchpad), but it gets very hot, so that it must be running something. Booting with 4.4.0-15 makes the suspend to work perfectly. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-extra-4.4.0-16-generic 4.4.0-16.32 ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6 Uname: Linux 4.4.0-15-generic x86_64 ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: macias 1770 F pulseaudio CurrentDesktop: X-Cinnamon Date: Tue Apr 5 14:56:17 2016 HibernationDevice: RESUME=UUID=4180adfa-3852-4a96-86b4-f3696448c743 InstallationDate: Installed on 2016-03-07 (28 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160304) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f3:21d5 Elan Microelectronics Corp. Bus 001 Device 002: ID 0a5c:6410 Broadcom Corp. Bus 001 Device 004: ID 1bcf:2b95 Sunplus Innovation Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 15 9550 ProcEnviron: LANGUAGE=es_ES PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-15-generic.efi.signed root=UUID=673f4658-75f8-4c01-bcd8-0af860269699 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-15-generic N/A linux-backports-modules-4.4.0-15-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/25/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.01.19 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.01.19:bd01/25/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 15 9550 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1566302/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1744884] 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 1744884 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: 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/1744884 Title: OverlayFS not writeable Status in linux package in Ubuntu: Incomplete Bug description: A customer of ours has a collection of servers in a test environment which mounts production data via NFS. The NFS is then mounted as the lower directory of an overlayfs, $directory_workdir is mounted as the workdir, and $directory_cow is mounted as the upper directory. However, as of recent, the customer can not edit any data unless the necessary files are 'touch'ed first (or if you use vim, force-written). "uname -a" returns "Linux 4.4.0-104-generic #127-Ubuntu SMP Mon Dec 11 12:16:42 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1744884/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1744252] Re: linux-aws: -proposed tracker
** Tags removed: kernel-release-tracking-bug-live -- 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/1744252 Title: linux-aws: -proposed tracker Status in Kernel SRU Workflow: Invalid Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Invalid Status in Kernel SRU Workflow prepare-package-meta series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: Invalid Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow snap-release-to-beta series: Invalid Status in Kernel SRU Workflow snap-release-to-candidate series: Invalid Status in Kernel SRU Workflow snap-release-to-edge series: Invalid Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Xenial: Invalid Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1744244 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1744252/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1744078] Re: linux < 4.8: x-netns vti is broken
It resolves the problem ! Thanks ! > uname -a Linux ubuntu1604 4.4.0-109-generic #132~lp1744078 SMP Mon Jan 22 16:08:56 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux ... config ... (ping): no error raised (tcpdump) 10:24:52.885081 de:ad:de:01:02:03 > 52:55:0a:00:02:02, ethertype IPv4 (0x0800), length 166: 1.1.1.1 > 2.2.2.2: ESP(spi=0x0001,seq=0x1), length 132 (tcpdump) 10:24:53.892653 de:ad:de:01:02:03 > 52:55:0a:00:02:02, ethertype IPv4 (0x0800), length 166: 1.1.1.1 > 2.2.2.2: ESP(spi=0x0001,seq=0x2), length 132 => OK -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1744078 Title: linux < 4.8: x-netns vti is broken Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Bug description: The following upstream patch is missing: 11d7a0bb95ea xfrm: Only add l3mdev oif to dst lookups https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=11d7a0bb95ea There are several ways to reproduce this problem. Here an example: # Prepare netns ip netns add test ip netns exec test sysctl -q -w net.ipv4.conf.all.forwarding=1 ip netns exec test ip link set lo up ip netns exec test ip addr add 172.16.1.1/24 dev lo # Create VTI iface and move it in netns test ip addr add 1.1.1.1/32 dev lo ip link add name vti_test type vti local 1.1.1.1 remote 2.2.2.2 key 0x1 ip link set dev vti_test netns test # Configure IPsec ip xfrm state add src 1.1.1.1 dst 2.2.2.2 proto esp spi 1 mode tunnel enc 'cbc(aes)' '0x' auth-trunc 'hmac(sha1)' '0x' 96 flag align4 mark 0x1 ip xfrm state add src 2.2.2.2 dst 1.1.1.1 proto esp spi 2 mode tunnel enc 'cbc(aes)' '0x' auth-trunc 'hmac(sha1)' '0x' 96 flag align4 mark 0x1 ip xfrm policy add dir out tmpl src 1.1.1.1 dst 2.2.2.2 proto esp mode tunnel mark 0x1 ip xfrm policy add dir in tmpl src 2.2.2.2 dst 1.1.1.1 proto esp mode tunnel mark 0x1 # Configure SVTI ip netns exec test ip link set dev vti_test up # Add route ip netns exec test ip route add 172.16.2.0/24 dev vti_test # Run a tcpdump on the output interface (given by "ip route get 2.2.2.2") tcpdump -nei eth0 & # Ping from the netns ip netns exec test ping 172.16.2.1 -I 172.16.1.1 -c 4 -- On 4.4.0-109-generic: (ping) From 172.16.1.1 icmp_seq=1 Destination Host Unreachable (tcpdump) no IPsec packet => Problem On 4.8.0-58-generic: (ping): no error raised (tcpdump) 15:09:45.109776 de:ad:de:01:02:03 > 52:55:0a:00:02:02, ethertype IPv4 (0x0800), length 166: 1.1.1.1 > 2.2.2.2: ESP(spi=0x0001,seq=0x2), length 132 (tcpdump) 15:10:05.422243 de:ad:de:01:02:03 > 52:55:0a:00:02:02, ethertype IPv4 (0x0800), length 166: 1.1.1.1 > 2.2.2.2: ESP(spi=0x0001,seq=0x3), length 132 => No problem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1744078/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1743111] Re: crash after update linux-image-4.13.0-26-generic
Installed the version 4.10.0-42-generic; installation went perfect. I got an update message and updated to 4.13.0-26-generic. I can see the system running but the screen shows only some lines and a small peace of a window in the right part of the window. The system does not react on the keyboard. I am running Lubuntu 17.10 on a Samsung Nc10 notebook. If is not possible to generate an error report as requested. Thanks for your help to solve this 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/1743111 Title: crash after update linux-image-4.13.0-26-generic Status in linux package in Ubuntu: Incomplete Bug description: The lubuntu does not startup correctly screen is a mess but no crash. More complaints seen in the ubuntu forem blog To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1743111/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1722261] Re: deadlock in mount umount and sync
Another lock. Several smbd processes hold lock-up files. Impossible to kill them because they are in state D. Failed to restart samba and make file system umount. smbd process stack: [] cv_wait_common+0x10b/0x140 [spl] [] __cv_wait+0x15/0x20 [spl] [] zfs_dirent_lock+0x175/0x590 [zfs] [] zfs_get_xattrdir+0x12b/0x1b0 [zfs] [] zfs_lookup+0x1c4/0x310 [zfs] [] zpl_xattr_get_dir+0x64/0x110 [zfs] [] zpl_xattr_get+0xbb/0x1a0 [zfs] [] zpl_xattr_user_get+0x5f/0x80 [zfs] [] generic_getxattr+0x4b/0x70 [] vfs_getxattr+0x88/0xb0 [] getxattr+0xa8/0x200 [] path_getxattr+0x65/0xb0 [] SyS_getxattr+0x14/0x20 [] entry_SYSCALL_64_fastpath+0x16/0x71 [] 0x smbd status: Name: smbd State: D (disk sleep) Tgid: 451 Ngid: 451 Pid:451 PPid: 1 TracerPid: 0 Uid:65534 65534 0 65534 Gid:0 36080 3608 FDSize: 64 Groups: 65534 NStgid: 451 NSpid: 451 NSpgid: 74623 NSsid: 74623 VmPeak: 482860 kB VmSize: 482860 kB VmLck: 0 kB VmPin: 0 kB VmHWM: 22528 kB VmRSS: 19760 kB VmData: 100048 kB VmStk: 132 kB VmExe:64 kB VmLib: 33124 kB VmPTE: 720 kB VmPMD:16 kB VmSwap:0 kB HugetlbPages: 0 kB Threads:1 SigQ: 412/514626 SigPnd: 0100 ShdPnd: 4100 SigBlk: 1880 SigIgn: 2000 SigCgt: 000580014461 CapInh: CapPrm: 003f CapEff: CapBnd: 003f CapAmb: Seccomp:0 Cpus_allowed: ,,,,, Cpus_allowed_list: 0-191 Mems_allowed: ,0003 Mems_allowed_list: 0-1 voluntary_ctxt_switches:121 nonvoluntary_ctxt_switches: 299 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1722261 Title: deadlock in mount umount and sync Status in zfs-linux package in Ubuntu: New Bug description: I use zfs vesion 0.6.5.6 on Ubuntu 16.04.2 LTS . I have many zombie process on auto-mount of snapshot and on sync ! 903 process are in deadlock. i can't mount a new file system or snapshot . Partial output of ps alx |grep 'call_r D' below . what is the cause? what can I do ? 0 0 2371 1 20 0 6016 752 call_r D? 0:00 /bin/sync 0 0 15290 1 20 0 6016 676 call_r D? 0:00 /bin/sync 0 0 18919 1 20 0 6016 708 call_r D? 0:00 /bin/sync 0 0 27076 1 20 0 6016 808 call_r D? 0:00 /bin/sync 4 0 31976 1 20 0 22084 1344 call_r D? 0:00 umount -t zfs -n /samba/shares/Aat/.zfs/snapshot/2017-10-04_09.00.05--5d error in kern.log: 9 13:20:28 zfs-cis kernel: [5368563.592834] WARNING: Unable to automount /samba/shares/Trapianti/.zfs/snapshot/2017-10-03_08.00.03--5d/pool_z2_samba/shares/Trapianti@2017-10-03_08.00.03--5d: 256 Oct 9 13:20:28 zfs-cis kernel: [5368563.597868] WARNING: Unable to automount /samba/shares/Trapianti/.zfs/snapshot/2017-10-03_08.00.03--5d/pool_z2_samba/shares/Trapianti@2017-10-03_08.00.03--5d: 256 Oct 9 13:20:28 zfs-cis kernel: [5368563.601730] WARNING: Unable to automount /samba/shares/Trapianti/.zfs/snapshot/2017-10-03_08.00.03--5d/pool_z2_samba/shares/Trapianti@2017-10-03_08.00.03--5d: 256 Oct 9 13:22:57 zfs-cis kernel: [5368713.187001] WARNING: Unable to automount /samba/shares/Trapianti/.zfs/snapshot/2017-10-03_10.00.03--5d/pool_z2_samba/shares/Trapianti@2017-10-03_10.00.03--5d: 256 Oct 9 13:22:57 zfs-cis kernel: [5368713.13] WARNING: Unable to automount /samba/shares/Cardiologia2/.zfs/snapshot/2017-10-03_12.00.03--5d/pool_z2_samba/shares/Cardiologia2@2017-10-03_12.00.03--5d: 256 Oct 9 13:22:57 zfs-cis kernel: [5368713.15] WARNING: Unable to automount /samba/shares/Trapianti/.zfs/snapshot/2017-10-03_14.00.04--5d/pool_z2_samba/shares/Trapianti@2017-10-03_14.00.04--5d: 256 Oct 9 13:22:57 zfs-cis kernel: [5368713.189005] WARNING: Unable to automount /samba/shares/Aat/.zfs/snapshot/2017-10-03_20.00.04--5d/pool_z2_samba/shares/Aat@2017-10-03_20.00.04--5d: 256 Oct 9 13:22:57 zfs-cis kernel: [5368713.190105] WARNING: Unable to automount /samba/shares/Trapianti/.zfs/snapshot/2017-10-03_10.00.03--5d/pool_z2_samba/shares/Trapianti@2017-10-03_10.00.03--5d: 256 Oct 9 13:22:57 zfs-cis kernel: [5368713.192847] WARNING: Unable to automount /samba/shares/Trapianti/.zfs/snapshot/2017-10-03_10.00.03--5d/pool_z2_samba/shares/Trapianti@2017-10-03_10.00.03--5d: 256 Oct 9 13:22:57 zfs-cis kernel: [5368713.193617] WARNING: Unable to automount /samba/shares/Trapianti/.zfs/snapshot/2017-10-03_14.00.04--5d/pool_z2_samba/shares/Trapianti@2017-10-03_14.00.04--5d: 256 Oct 9 13:22:57 zfs-cis kernel: [5368713.198096] WARNING: Unable to automount /samba/shares/Trapianti/.zfs/snapshot/2017-10-03_14.00.04--
[Kernel-packages] [Bug 1744121] Re: Artful update to 4.13.14 stable release
Applied to artful/master-next-backlog for now. ** Changed in: linux (Ubuntu Artful) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Artful) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1744121 Title: Artful update to 4.13.14 stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Artful: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The 4.13.14 upstream stable patch set is now available. It should be included in the Ubuntu kernel as well. git://git.kernel.org/ TEST CASE: TBD The following patches from the 4.13.14 stable release shall be applied: * ppp: fix race in ppp device destruction * gso: fix payload length when gso_size is zero * ipv4: Fix traffic triggered IPsec connections. * ipv6: Fix traffic triggered IPsec connections. * netlink: do not set cb_running if dump's start() errs * net: call cgroup_sk_alloc() earlier in sk_clone_lock() * macsec: fix memory leaks when skb_to_sgvec fails * l2tp: check ps->sock before running pppol2tp_session_ioctl() * tun: call dev_get_valid_name() before register_netdevice() * netlink: fix netlink_ack() extack race * sctp: add the missing sock_owned_by_user check in sctp_icmp_redirect * tcp/dccp: fix ireq->opt races * packet: avoid panic in packet_getsockopt() * geneve: Fix function matching VNI and tunnel ID on big-endian * net: bridge: fix returning of vlan range op errors * soreuseport: fix initialization race * ipv6: flowlabel: do not leave opt->tot_len with garbage * sctp: full support for ipv6 ip_nonlocal_bind & IP_FREEBIND * tcp/dccp: fix lockdep splat in inet_csk_route_req() * tcp/dccp: fix other lockdep splats accessing ireq_opt * net: dsa: check master device before put * net/unix: don't show information about sockets from other namespaces * tap: double-free in error path in tap_open() * net/mlx5: Fix health work queue spin lock to IRQ safe * net/mlx5e: Properly deal with encap flows add/del under neigh update * ipip: only increase err_count for some certain type icmp in ipip_err * ip6_gre: only increase err_count for some certain type icmpv6 in ip6gre_err * ip6_gre: update dst pmtu if dev mtu has been updated by toobig in __gre6_xmit * tcp: refresh tp timestamp before tcp_mtu_probe() * tap: reference to KVA of an unloaded module causes kernel panic * tun: allow positive return values on dev_get_valid_name() call * sctp: reset owner sk for data chunks on out queues when migrating a sock * net_sched: avoid matching qdisc with zero handle * l2tp: hold tunnel in pppol2tp_connect() * tun/tap: sanitize TUNSETSNDBUF input * ipv6: addrconf: increment ifp refcount before ipv6_del_addr() * tcp: fix tcp_mtu_probe() vs highest_sack * mac80211: accept key reinstall without changing anything * mac80211: use constant time comparison with keys * mac80211: don't compare TKIP TX MIC key in reinstall prevention * usb: usbtest: fix NULL pointer dereference * Input: ims-psu - check if CDC union descriptor is sane * EDAC, sb_edac: Don't create a second memory controller if HA1 is not present * dmaengine: dmatest: warn user when dma test times out * Linux 4.13.14 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1744121/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1703742] Re: Transparent hugepages should default to enabled=madvise
** Changed in: linux (Ubuntu Zesty) Status: In Progress => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1703742 Title: Transparent hugepages should default to enabled=madvise Status in linux package in Ubuntu: Fix Released Status in linux-gke package in Ubuntu: Fix Committed Status in linux source package in Xenial: In Progress Status in linux-gke source package in Xenial: Fix Released Status in linux source package in Yakkety: Won't Fix Status in linux source package in Zesty: Won't Fix Status in linux source package in Artful: Fix Released Bug description: SRU Justification, Zesty, Xenial [Impact] Ubuntu kernels should default transparent_hugepages to enabled=madvise, not enabled=always (this corresponds to TRANSPARENT_HUGEPAGE_MADVISE=y in .config). I've blogged about this at some length here: https://blog.nelhage.com/post/transparent-hugepages/ but here is a summary: Transparent Hugepages are a feature that allows the kernel to attempt to automatically back any anonymous maps with "huge" 2MiB page tables, instead of the normal 4k entries. It can produce small net performance gains in certain benchmarks, but also has numerous downsides, in the form of apparent memory leaks and 30% slowdowns or worse for some applications. Many popular pieces of software now refuse to run with hugepages enabled because of known performance issues. Examples of problem reports: MongoDB: https://docs.mongodb.com/manual/tutorial/transparent-huge-pages/ Oracle: https://blogs.oracle.com/linux/entry/performance_issues_with_transparent_huge Splunk: https://docs.splunk.com/Documentation/Splunk/6.5.2/ReleaseNotes/SplunkandTHP Go runtime: https://github.com/golang/go/issues/8832 jemalloc: https://blog.digitalocean.com/transparent-huge-pages-and-alternative-memory-allocators/ node.js: https://github.com/nodejs/node/issues/11077 Setting `enabled=madvise` enables applications that know they benefit from transparent huge pages to opt-in to this feature, while eliminating all the problematic behavior for other applications. Note also that transparent hugepage settings don't affect the use of explicit hugepages via hugetlbfs or mmap(…, MAP_HUGETLB, …) [Fix] Enable CONFIG_TRANSPARENT_HUGEPAGE_MADVISE=y [Regression Potential] May marginally impact performance, but the benefits of madvise'd huge transparent hugepage over-weigh this considerably. This has been enabled in Artful since July (and in Bionic) and we've not seen any regression reports, so we are confident this has minimal impact. [Testcase] Kernel ADT tests and stress-ng memory tests should not show any regressions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1703742/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1742626] Re: Unstable LTS kernel 4.13.0-26
4.13.0-30.33 available with dist-upgrade We installed it on 12 machines. It seems to be stable. https://insights.ubuntu.com/2018/01/17/spectre-mitigation-updates- available-for-testing-in-ubuntu-proposed/ ** Changed in: linux-signed (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1742626 Title: Unstable LTS kernel 4.13.0-26 Status in linux-signed package in Ubuntu: Fix Released Bug description: At job, after upgrading many Lubuntu 16.04 LTS 64 bit systems from 4.10 to 4.13 they are (most of them) unstable. Acer TravelMate B117-M (SSD disk) freeze at boot or show errors at startup such: unexpected irq trap at vector similar to https://forum.manjaro.org/t/manjaro-kernel-4-13-unexpected- irq-trap-at-vector-e3-error/30942 At home (no signed kernel, old machine) my VirtualBox freezes also the machine, as explained at https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1736116/comments/14 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1742626/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1736954] Re: ppc64el: Do not call ibm, os-term on panic
** Also affects: linux (Ubuntu Artful) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) Importance: High Assignee: Thadeu Lima de Souza Cascardo (cascardo) Status: In Progress ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Trusty) 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/1736954 Title: ppc64el: Do not call ibm,os-term on panic Status in linux package in Ubuntu: In Progress Status in linux source package in Trusty: New Status in linux source package in Xenial: New Status in linux source package in Artful: New Status in linux source package in Bionic: In Progress Bug description: [Impact] When panic_timeout is set, the user would expect the system to reboot. However, it is shutdown, possibly requiring user intervention to power on the system again. This may impact availability. This happens under certain versions of qemu (2.10+) emulating pseries. [Test Case] Built kernels (trusty, xenial, zesty, artful) have been tested and they reboot after the fix, when running under an affected qemu. [Regression Potential] fadump might require that RTAS ibm,os-term be called. The fix should still allow it to be called when fadump is registered. --- When panic_timeout is set, the user would expect that the system would reboot after some timeout after a panic. However, on powerpc architecture, a panic notifier may not ever return and even shutdown the system. The main example that impacts platforms we support is pseries calling RTAS ibm,os-term. That panic notifier and calling RTAS ibm,os-term is useful for fadump, so this should not be impacted. The Linux code has changed back and forth on considering the panic_timeout setting and checking whether ibm,extended-os-term was available. Unfortunately, recent changes on qemu led to the guest being shut down when calling ibm,os-term even when ibm,extended-os- term was available. Luckily, upstream Linux already has the change that does not call ibm ,os-term on panic, but only during fadump. So, we can use that commit for fixing this. Changing qemu itself is harder as: 1) qemu community already decided some qemu settings should override PAPR; 2) updating deployed hypervisor is harder than updating our guest kernels. Cascardo. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1736954/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1730717] Re: Some VMs fail to reboot with "watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [systemd:1]"
** Changed in: linux (Ubuntu Zesty) Status: Incomplete => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1730717 Title: Some VMs fail to reboot with "watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [systemd:1]" Status in linux package in Ubuntu: Fix Committed Status in qemu-kvm package in Ubuntu: Confirmed Status in linux source package in Zesty: Won't Fix Status in qemu-kvm source package in Zesty: New Status in linux source package in Artful: In Progress Status in qemu-kvm source package in Artful: Confirmed Status in linux source package in Bionic: Fix Committed Status in qemu-kvm source package in Bionic: Confirmed Bug description: == SRU Justification == The fix to bug 1672819 can cause an lockup because it can spin indefinitely waiting for a child to exit. [FIX] Add a sauce patch to the original fix to insert a reasonable small delay and an upper bounds to the number of retries that are made before bailing out with an error. This avoids the lockup and also is less aggressive in the retry loop. [TEST] Without the fix the machine hangs. With the fix, the lockup no longer occurs. [REGRESSION POTENTIAL] There may be an issue with the interruptible sleep having some unforeseen impact with userspace racy code that expects the system call to return quickly when the race condition occurs and instead it gets delayed by a few milliseconds while the retry loop spins. However, code that relies on timing on fork/exec inside pthreads where this particular code path could bite is generally non-POSIX conforming racy code anyhow. --- This is impacting us for ubuntu autopkgtests. Eventually the whole region ends up dying because each worker is hit by this bug in turn and backs off until the next reset (6 hourly). 17.10 (and bionic) guests are sometimes failing to reboot. When this happens, you see the following in the console [[0;32m OK [0m] Reached target Shutdown. [ 191.698969] watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [systemd:1] [ 219.698438] watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [systemd:1] [ 226.702150] INFO: rcu_sched detected stalls on CPUs/tasks: [ 226.704958] »(detected by 0, t=15002 jiffies, g=5347, c=5346, q=187) [ 226.706093] All QSes seen, last rcu_sched kthread activity 15002 (4294949060-4294934058), jiffies_till_next_fqs=1, root ->qsmask 0x0 [ 226.708202] rcu_sched kthread starved for 15002 jiffies! g5347 c5346 f0x2 RCU_GP_WAIT_FQS(3) ->state=0x0 One host that exhibits this behaviour was: Linux klock 4.4.0-98-generic #121-Ubuntu SMP Tue Oct 10 14:24:03 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux guest running: Linux version 4.13.0-16-generic (buildd@lcy01-02) (gcc version 7.2.0 (Ubuntu 7.2.0-8ubuntu2)) #19-Ubuntu SMP Wed Oct 11 18:35:14 UTC 2017 (Ubuntu 4.13.0-16.19-generic 4.13.4) The affected cloud region is running the xenial/Ocata cloud archive, so the version of qemu-kvm in there may also be relevant. Here's how I reproduced it in lcy01: $ for n in {1..30}; do nova boot --flavor m1.small --image ubuntu/ubuntu-artful-17.10-amd64-server-20171026.1-disk1.img --key-name testbed-`hostname` --nic net-name=net_ues_proposed_migration laney-test${n}; done $ sudo reboot # wait a minute or so for the instances to all reboot $ for n in {1..30}; do echo "=== ${n} ==="; nova console-log laney-test${n} | tail; done On bad instances you'll see the "soft lockup" message - on good it'll reboot as normal. We've seen good and bad instances on multiple compute hosts - it doesn't feel to me like a host problem but rather a race condition somewhere that's somehow either triggered or triggered much more often by what lcy01 is running. I always saw this on the first reboot - never on first boot, and never on n>1th boot. (But if it's a race then that might not mean much.) I'll attach a bad and a good console-log for reference. If you're at Canonical then see internal rt #107135 for some other details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1730717/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1694485] Re: Ubuntu17.04: CAPI: call trace seen while error injection to the CAPI card.
** Changed in: linux (Ubuntu Zesty) Status: In Progress => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1694485 Title: Ubuntu17.04: CAPI: call trace seen while error injection to the CAPI card. Status in The Ubuntu-power-systems project: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Zesty: Won't Fix Bug description: == Comment: #0 - SUDEESH JOHN - 2017-03-18 13:55:03 == ---Problem Description--- call trace while injecting error to the CAPI card. " WARNING: CPU: 31 PID: 491 at /build/linux-VtwHOM/linux-4.10.0/drivers/misc/cxl/main.c:325 cxl_adapter_context_unlock+0x68/0x90 [cxl] " ---uname output--- Linux freak 4.10.0-13-generic #15-Ubuntu SMP Thu Mar 9 20:27:28 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux Machine Type = PowerNV 8247-21L ---Steps to Reproduce--- 1. echo 1 > /sys/kernel/debug/powerpc/eeh_max_freezes 2. echo 1 > /sys/class/cxl/card0/perst_reloads_same_image 3. echo 0x8000 > /sys/kernel/debug/powerpc/PCI/err_injct_outbound ---The complete call trace --- Mar 18 14:39:09 freak kernel: [ 289.675421] [ cut here ] Mar 18 14:39:09 freak kernel: [ 289.675431] WARNING: CPU: 5 PID: 491 at /build/linux-VtwHOM/linux-4.10.0/drivers/misc/cxl/main.c:325 cxl_adapter_context_unlock+0x68/0x90 [cxl] Mar 18 14:39:09 freak kernel: [ 289.675432] Modules linked in: 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 ipt_REJECT nf_reject_ipv4 xt_tcpudp bridge stp llc kvm_hv kvm_pr kvm ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter uio_pdrv_genirq uio ipmi_powernv ipmi_devintf ipmi_msghandler powernv_op_panel powernv_rng vmx_crypto ibmpowernv leds_powernv ib_iser rdma_cm iw_cm ib_cm ib_core configfs iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq raid1 raid0 multipath linear ses enclosure scsi_transport_sas bnx2x mlx5_core tg3 cxl mdio ipr libcrc32c devlink crc32c_vpmsum pnv_php Mar 18 14:39:09 freak kernel: [ 289.675490] CPU: 5 PID: 491 Comm: eehd Not tainted 4.10.0-13-generic #15-Ubuntu Mar 18 14:39:09 freak kernel: [ 289.675492] task: c003bfbfde00 task.stack: c003bfc5c000 Mar 18 14:39:09 freak kernel: [ 289.675493] NIP: d5cc0ca0 LR: d5cc0c9c CTR: c0605aa0 Mar 18 14:39:09 freak kernel: [ 289.675495] REGS: c003bfc5f6a0 TRAP: 0700 Not tainted (4.10.0-13-generic) Mar 18 14:39:09 freak kernel: [ 289.675496] MSR: 9282b033 Mar 18 14:39:09 freak kernel: [ 289.675504] CR: 28008282 XER: 2000 Mar 18 14:39:09 freak kernel: [ 289.675504] CFAR: c0b568dc SOFTE: 1 Mar 18 14:39:09 freak kernel: [ 289.675504] GPR00: d5cc0c9c c003bfc5f920 d5cf2d88 002f Mar 18 14:39:09 freak kernel: [ 289.675504] GPR04: 0001 03fd 63206576 Mar 18 14:39:09 freak kernel: [ 289.675504] GPR08: c15dc700 0001 Mar 18 14:39:09 freak kernel: [ 289.675504] GPR12: 8800 cfb82d00 c0108c88 c003c51f9f00 Mar 18 14:39:09 freak kernel: [ 289.675504] GPR16: Mar 18 14:39:09 freak kernel: [ 289.675504] GPR20: c0d53990 Mar 18 14:39:09 freak kernel: [ 289.675504] GPR24: c0d53968 c14a4330 c003ab8fa800 c003bd2c20c0 Mar 18 14:39:09 freak kernel: [ 289.675504] GPR28: c003c5051098 c003ab8fa800 Mar 18 14:39:09 freak kernel: [ 289.675535] NIP [d5cc0ca0] cxl_adapter_context_unlock+0x68/0x90 [cxl] Mar 18 14:39:09 freak kernel: [ 289.675540] LR [d5cc0c9c] cxl_adapter_context_unlock+0x64/0x90 [cxl] Mar 18 14:39:09 freak kernel: [ 289.675541] Call Trace: Mar 18 14:39:09 freak kernel: [ 289.675547] [c003bfc5f920] [d5cc0c9c] cxl_adapter_context_unlock+0x64/0x90 [cxl] (unreliable) Mar 18 14:39:09 freak kernel: [ 289.675556] [c003bfc5f980] [d5cd022c] cxl_configure_adapter+0x954/0x990 [cxl] Mar 18 14:39:09 freak kernel: [ 289.675563] [c003bfc5fa30] [d5cd02c0] cxl_pci_slot_reset+0x58/0x240 [cxl] Mar 18 14:39:09 freak kernel: [ 289.675568] [c003bfc5fae0] [c003b0d4] eeh_report_reset+0x154/0x190 Mar 18 14:39:09 freak kernel: [ 289.675571] [c003bfc5fb20] [c0039428] eeh_pe_dev_traverse+0x98/0x170 Mar 18 14:39:09 freak kernel: [ 289.675574] [c003bfc5fbb0] [c003b8
[Kernel-packages] [Bug 1742626] Re: Unstable LTS kernel 4.13.0-26
I'm sorry! dist-upgrade on our 16.04 LTS HWE systems installs 4.13.0-31 It seems to be estable, as I said. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1742626 Title: Unstable LTS kernel 4.13.0-26 Status in linux-signed package in Ubuntu: Fix Released Bug description: At job, after upgrading many Lubuntu 16.04 LTS 64 bit systems from 4.10 to 4.13 they are (most of them) unstable. Acer TravelMate B117-M (SSD disk) freeze at boot or show errors at startup such: unexpected irq trap at vector similar to https://forum.manjaro.org/t/manjaro-kernel-4-13-unexpected- irq-trap-at-vector-e3-error/30942 At home (no signed kernel, old machine) my VirtualBox freezes also the machine, as explained at https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1736116/comments/14 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1742626/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1729145] Re: /dev/bcache/by-uuid links not created after reboot
** Changed in: linux (Ubuntu Zesty) Status: In Progress => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1729145 Title: /dev/bcache/by-uuid links not created after reboot Status in linux package in Ubuntu: In Progress Status in systemd package in Ubuntu: Incomplete Status in linux source package in Xenial: In Progress Status in systemd source package in Xenial: Won't Fix Status in linux source package in Zesty: Won't Fix Status in systemd source package in Zesty: Won't Fix Status in linux source package in Artful: In Progress Status in systemd source package in Artful: Won't Fix Status in linux source package in Bionic: In Progress Status in systemd source package in Bionic: Won't Fix Bug description: 1. $ lsb_release -rd Description: Ubuntu 17.10 Release: 17.10 2. $ apt-cache policy linux-image-`uname -r` linux-image-4.13.0-16-generic: Installed: 4.13.0-16.19 Candidate: 4.13.0-16.19 Version table: *** 4.13.0-16.19 500 500 http://nova.clouds.archive.ubuntu.com/ubuntu artful/main amd64 Packages 100 /var/lib/dpkg/status 3. After creating some bcache devices and rebooting /dev/bcache/by-uuid/ -> ../../bcacheN symlinks point to the current bcache device which is caching the dev.uuid found after creating a backing device. 4. /dev/bcache/by-uuid does not exist and there are not symlinks underneath It appears that since the initramfs loads the bcache module which probes and finds all of the cache devices and backing devices then once the rootfs is mounted and udev gets to run, the bcache kernel module does not emit the CACHED_UUID value into the environment if the underlying devices are already registered. In dmesg, one can see that prior to mounting the rootfs, we see bcache register events: [5.333973] bcache: register_bdev() registered backing device vdb2 [5.354138] bcache: register_bdev() registered backing device vdb4 [5.365665] bcache: register_bdev() registered backing device vdb3 [5.397720] bcache: bch_journal_replay() journal replay done, 0 keys in 1 entries, seq 1 [5.428683] bcache: register_cache() registered cache device vdb1 then rootfs ismounted and systemd starts systemd-udev [9.350889] systemd[1]: Listening on udev Kernel Socket. And then the coldplug replay of kernel events triggers /lib/udev/rules.d/69-bcache.rules which invokes /lib/udev/bcache-register which writes the device name (/dev/vdb1 or /dev/bcache0) into /sys/fs/bcache/register and results is the bcache kernel driver attempting to register the block device. However, there is already a bcache device associated already and registration fails [ 11.173141] bcache: register_bcache() error opening /dev/vdb2: device already registered [ 11.184617] bcache: register_bcache() error opening /dev/vdb3: device already registered [ 11.199130] bcache: register_bcache() error opening /dev/vdb1: device already registered [ 11.271694] bcache: register_bcache() error opening /dev/vdb4: device already registered The problem then is that only a kernel call to bch_cached_dev_run() which happens like this: bcache_register() register_bdev() bch_cached_dev_run() kobject_uevent_env(&disk_to_dev(d->disk)->kobj, KOBJ_CHANGE, env); where env includes: "DRIVER=bcache", kasprintf(GFP_KERNEL, "CACHED_UUID=%pU", dc->sb.uuid), NULL, NULL, }; Since that event is not emitted for any previously registered device, then the symlink will not be created. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-16-generic 4.13.0-16.19 ProcVersionSignature: User Name 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Oct 31 22:09 seq crw-rw 1 root audio 116, 33 Oct 31 22:09 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A Date: Wed Nov 1 01:39:01 2017 Ec2AMI: ami-030b Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: m1.small Ec2Kernel: unavailable Ec2Ramdisk: unavailable IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: OpenStack Foundation OpenStack Nova PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/
[Kernel-packages] [Bug 1744884] Re: OverlayFS not writeable
** Attachment added: "apport.linux.RsIdPS.apport" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1744884/+attachment/5041632/+files/apport.linux.RsIdPS.apport ** 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/1744884 Title: OverlayFS not writeable Status in linux package in Ubuntu: Confirmed Bug description: A customer of ours has a collection of servers in a test environment which mounts production data via NFS. The NFS is then mounted as the lower directory of an overlayfs, $directory_workdir is mounted as the workdir, and $directory_cow is mounted as the upper directory. However, as of recent, the customer can not edit any data unless the necessary files are 'touch'ed first (or if you use vim, force-written). "uname -a" returns "Linux 4.4.0-104-generic #127-Ubuntu SMP Mon Dec 11 12:16:42 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1744884/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1741166] Re: [0cf3:e010] QCA6174A XR failed to pair with bt 4.0 device
** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux-oem (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Status: New => Invalid ** Changed in: linux-oem (Ubuntu) Status: New => 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/1741166 Title: [0cf3:e010] QCA6174A XR failed to pair with bt 4.0 device Status in OEM Priority Project: Triaged Status in linux package in Ubuntu: Fix Committed Status in linux-oem package in Ubuntu: Invalid Status in linux source package in Xenial: Invalid Status in linux-oem source package in Xenial: New Bug description: [Impact] QCA6174A XR can scan but can't pair with bt 4.0 device. [Fix] [0cf3:e010] is one of the QCA ROME family and should be listed in btusb driver. [Test Case] Applied the patch and can pair with bt 4.0 keyboard without any issue. [Regression Potential] Adding the device to the list won't have any regression potential. impacted tickets: LP: #1736330 LP: #1742849 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1741166/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1718654] Re: Touchpad input doesn't work after longer suspend.
Confirmed, I haven't seen this issue in a while. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1718654 Title: Touchpad input doesn't work after longer suspend. Status in gnome-shell package in Ubuntu: Incomplete Status in linux package in Ubuntu: Confirmed Bug description: When I resume my laptop from a longer (not sure what the threshold is yet) suspend, I don't get input from the touchpad, a short suspend cycle fixes it. Touchscreen works all the time. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10 Uname: Linux 4.12.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Sep 21 14:20:56 2017 DisplayManager: gdm3 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1718654/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1727228] Re: ath9k can't connect to wifi AP
** Package changed: linux (Ubuntu) => linux-oem (Ubuntu) ** Also affects: linux-oem (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux-oem (Ubuntu) Status: In Progress => 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/1727228 Title: ath9k can't connect to wifi AP Status in HWE Next: New Status in linux-oem package in Ubuntu: Invalid Status in linux-oem source package in Xenial: New Bug description: [Impact] iwlist scan can search the available wifi APs, but can't get connected. On new Intel platforms like ApolloLake, legacy interrupt mechanism (INTx) is not supported, so WLAN modules are not working because interrupts are missing. The affected and listed platforms are Dell Inspiron 24-3460 Dell Inspiron 14-3473 Dell Inspiron 3472 Dell Inspiron 3576 Dell Vostro 3262 Dell Vostro 15-3572 Dell Vostro 3578 [Fix] Qualcomm provided a MSI patch for ath9k, and it fixes the issue. [Test Case] Tested on the machines mentioned above, and they all work well. [Regression Potential] There shouldn't be any regression potential. These are newly enabled machines and quirks are applied based on DMI_PRODUCT_NAME to only use MSI on such machines. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1727228/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1742675] Re: after upgrade to linux-image-extra-4.13.0-26-generic the system does not start at all
ad #22 and 23: same with me: 4.13.0-31 not working BUT 4.4.0-112 working (without boot options) (32bit installation) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1742675 Title: after upgrade to linux-image-extra-4.13.0-26-generic the system does not start at all Status in linux package in Ubuntu: Confirmed Bug description: After upgrade to linux-image-extra-4.13.0-26-generic the system does not start at all. Only restart through Advanced Options with linux-image-extra-4.10.0-42-generic helps. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ubuntu-release-upgrader-core 1:16.04.23 ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-42-generic i686 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: i386 CrashDB: ubuntu CurrentDesktop: Unity Date: Thu Jan 11 15:20:26 2018 InstallationDate: Installed on 2017-06-23 (201 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release i386 (20170215.2) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.update-manager.release-upgrades: 2017-06-24T18:05:02.372991 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1742675/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1742626] Re: Unstable LTS kernel 4.13.0-26
Some of our Acer TravelMate B117-M (SSD disk) still having problems with 4.13.0-31 They freeze at boot or show errors at startup such: unexpected irq trap at vector 73 like https://community.endlessos.com/uploads/default/optimized/2X/4/470e2bb3ad0b6286e86710f2add2571f41fc03e9_1_281x500.jpg from https://community.endlessos.com/t/problem-while-booting-unexpected-irq- trap/4553 ** Changed in: linux-signed (Ubuntu) Status: Fix Released => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1742626 Title: Unstable LTS kernel 4.13.0-26 Status in linux-signed package in Ubuntu: Confirmed Bug description: At job, after upgrading many Lubuntu 16.04 LTS 64 bit systems from 4.10 to 4.13 they are (most of them) unstable. Acer TravelMate B117-M (SSD disk) freeze at boot or show errors at startup such: unexpected irq trap at vector similar to https://forum.manjaro.org/t/manjaro-kernel-4-13-unexpected- irq-trap-at-vector-e3-error/30942 At home (no signed kernel, old machine) my VirtualBox freezes also the machine, as explained at https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1736116/comments/14 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1742626/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1744806] Re: Bluetooth is turned off at boot with latest update (bluez 5.37-0ubuntu5.2)
*** This bug is a duplicate of bug 1510570 *** https://bugs.launchpad.net/bugs/1510570 Okay, thanks. I have AutoEnable=true and it won't come on, I'll subscribe to LP #1510570 ** This bug has been marked a duplicate of bug 1510570 Bluetooth LE pairing fail -- 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/1744806 Title: Bluetooth is turned off at boot with latest update (bluez 5.37-0ubuntu5.2) Status in bluez package in Ubuntu: Triaged Bug description: With latest update, BLUEZ is now off right after boot, as opposed to previous behaviour that was on/off depending on last setting. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: bluez 5.37-0ubuntu5.2 ProcVersionSignature: Ubuntu 4.13.0-31.34~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CurrentDesktop: Unity Date: Mon Jan 22 16:08:20 2018 InstallationDate: Installed on 2017-09-29 (115 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 003: ID 04f2:b59d Chicony Electronics Co., Ltd Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System76 Lemur ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-31-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash resume=/dev/mapper/ubuntu--vg-swap_1 vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/17/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.12 dmi.board.asset.tag: Tag 12345 dmi.board.name: Lemur dmi.board.vendor: System76 dmi.board.version: lemu7 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: System76 dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.12:bd02/17/2017:svnSystem76:pnLemur:pvrlemu7:rvnSystem76:rnLemur:rvrlemu7:cvnSystem76:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: Lemur dmi.product.version: lemu7 dmi.sys.vendor: System76 hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: AC:ED:5C:F6:32:44 ACL MTU: 1021:4 SCO MTU: 96:6 DOWN RX bytes:667 acl:0 sco:0 events:38 errors:0 TX bytes:405 acl:0 sco:0 commands:38 errors:0 mtime.conffile..etc.bluetooth.input.conf: 2017-12-06T11:16:58.937870 mtime.conffile..etc.bluetooth.main.conf: 2018-01-18T18:34:20.102879 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1744806/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1510570] Re: Bluetooth LE pairing fail
Verification failed on Xenial -- 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/1510570 Title: Bluetooth LE pairing fail Status in OEM Priority Project: Confirmed Status in bluez package in Ubuntu: Fix Released Status in bluez source package in Xenial: Fix Committed Bug description: [Impact] When the Bluetooth adapter is not powered on it is not possible to use it in normal way. We used to have a hack to force powering on by using an udev rule but this doe snot work anymore. Luckily the BlueZ has introduced "AutoEnable" option that makes the stack power on adapters by itself. Backporting this to xenial will improve life of the desktop users and will not require them to hack the solution on their own. The fix itself uses the well known solution to this problem that is floating around there for a while. The upload fixes the bug by enabling the 'AutoEnable' option in the bluetoothd config file. [Original Report] . 15.10 we now have bluez 5 so we can pair BLE devices like the Microsoft Arc Touch Bluetooth Mouse. But this pairing doesn't work very well. Mouse is seen but pairing fail. More information: https://bugzilla.kernel.org/show_bug.cgi?id=104011#c5 This is due to udev rule that use "hcitool" to power on device. Hopefully, bluez 5.35 has a new parameter "AutoEnable" who can be used instead of udev rules. here is a commit with this parameter: http://bazaar.launchpad.net/~guilhem-fr/bluez/autoenable/revision/138 [Test Case] On xenial install from ppa: https://launchpad.net/~bluetooth/+archive/ubuntu/bluez Now reboot the machine. The BT adapter shall be powered on. [Regression Potential] If things go wrong the adapter will not be powered on after the system boots up. Therefore while testing please focus on the adapter state, i.e. powered on or off. [Other Info] This fix is included in the development release, see: http://bazaar.launchpad.net/~bluetooth/bluez/ubuntu-zesty/revision/22 [What to upload] For xenial as in: ) https://launchpad.net/~bluetooth/+archive/ubuntu/bluez ) https://launchpadlibrarian.net/347480725/bluez_5.37-0ubuntu5_5.37-0ubuntu5.2~build1.diff.gz To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1510570/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1744935] [NEW] [i915] Display Corruption
Public bug reported: Sometime during a regular package update of Ubuntu of 17.10 I started having screen corruption issues within GL apps (e.g. WebGL on google maps) on both the external screens as well as the laptops (Thinkpad T460p), but then spread further to the regular desktop. I updated to Ubuntu 18.04 to try to resolve the issue and then even updated the kernel to the Linux-4.15-rc8 (4.15.0-994-generic) but the issues remain on both Wayland and Xorg. It seems related to the 3D acceleration since the corruption only starts with gdm, not on the framebuffer before. The issue happens on every boot. The i915 module is loaded with its default parameters, the nvidia card is deactivated with switcheroo and the proprietary driver has never been installed. The corruption is best described as flashing distortions associated with timers and/or input events. Sometimes a whole triangular section of up to a quarter of the double-screen setup is streched and/or discolored or blacked out. Sometimes black squares (a few pixels) splatter the whole screen for a few frames until a damaged region is updated. It looks like some kind of shader issue. Sometimes the screen gets stuck for a few seconds (presumably the hang from the crashdump attached), so it's possible that there are multiple issues but I can't discern them. dmesg reports: ` [31026.161705] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [31731.589497] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [32477.060892] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [35533.800723] [drm] GPU HANG: ecode 9:0:0x85db, in gnome-shell [14269], reason: Hang on rcs0, action: reset [35533.800725] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace. [35533.800725] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel [35533.800725] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue. [35533.800726] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it. [35533.800726] [drm] GPU crash dump saved to /sys/class/drm/card1/error [35533.800768] i915 :00:02.0: Resetting rcs0 after gpu hang [36101.847545] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [41209.093879] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [43073.711135] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [43339.548927] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [43886.208705] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [44617.864814] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [45925.860575] i915 :00:02.0: Resetting rcs0 after gpu hang ` The memory size in UEFI is already set to the maximum of 512Mb. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: drm i915 ** Attachment added: "i915 Hang Kernel Error Dump" https://bugs.launchpad.net/bugs/1744935/+attachment/5041734/+files/drm-card1-error.dump -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1744935 Title: [i915] Display Corruption Status in linux package in Ubuntu: New Bug description: Sometime during a regular package update of Ubuntu of 17.10 I started having screen corruption issues within GL apps (e.g. WebGL on google maps) on both the external screens as well as the laptops (Thinkpad T460p), but then spread further to the regular desktop. I updated to Ubuntu 18.04 to try to resolve the issue and then even updated the kernel to the Linux-4.15-rc8 (4.15.0-994-generic) but the issues remain on both Wayland and Xorg. It seems related to the 3D acceleration since the corruption only starts with gdm, not on the framebuffer before. The issue happens on every boot. The i915 module is loaded with its default parameters, the nvidia card is deactivated with
[Kernel-packages] [Bug 1740971] Re: Can't detect external headset via line-out jack on some Dell machines
** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux-oem (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Status: New => Invalid ** Changed in: linux-oem (Ubuntu) Status: Confirmed => 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/1740971 Title: Can't detect external headset via line-out jack on some Dell machines Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem package in Ubuntu: Invalid Status in linux source package in Xenial: Invalid Status in linux-oem source package in Xenial: New Bug description: insert a headset to line-out jack Expected results: system should detect line-out port and sound output through line-out jack Actual results: Can't detect external headset via line-out jack To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1740971/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1744935] 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 1744935 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1744935 Title: [i915] Display Corruption Status in linux package in Ubuntu: Incomplete Bug description: Sometime during a regular package update of Ubuntu of 17.10 I started having screen corruption issues within GL apps (e.g. WebGL on google maps) on both the external screens as well as the laptops (Thinkpad T460p), but then spread further to the regular desktop. I updated to Ubuntu 18.04 to try to resolve the issue and then even updated the kernel to the Linux-4.15-rc8 (4.15.0-994-generic) but the issues remain on both Wayland and Xorg. It seems related to the 3D acceleration since the corruption only starts with gdm, not on the framebuffer before. The issue happens on every boot. The i915 module is loaded with its default parameters, the nvidia card is deactivated with switcheroo and the proprietary driver has never been installed. The corruption is best described as flashing distortions associated with timers and/or input events. Sometimes a whole triangular section of up to a quarter of the double-screen setup is streched and/or discolored or blacked out. Sometimes black squares (a few pixels) splatter the whole screen for a few frames until a damaged region is updated. It looks like some kind of shader issue. Sometimes the screen gets stuck for a few seconds (presumably the hang from the crashdump attached), so it's possible that there are multiple issues but I can't discern them. dmesg reports: ` [31026.161705] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [31731.589497] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [32477.060892] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [35533.800723] [drm] GPU HANG: ecode 9:0:0x85db, in gnome-shell [14269], reason: Hang on rcs0, action: reset [35533.800725] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace. [35533.800725] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel [35533.800725] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue. [35533.800726] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it. [35533.800726] [drm] GPU crash dump saved to /sys/class/drm/card1/error [35533.800768] i915 :00:02.0: Resetting rcs0 after gpu hang [36101.847545] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [41209.093879] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [43073.711135] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [43339.548927] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [43886.208705] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [44617.864814] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [45925.860575] i915 :00:02.0: Resetting rcs0 after gpu hang ` The memory size in UEFI is already set to the maximum of 512Mb. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1744935/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe :
[Kernel-packages] [Bug 1740972] Re: No external microphone be detected via headset jack on a dell machine
** Package changed: linux (Ubuntu) => linux-oem (Ubuntu) ** Also affects: linux-oem (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Status: New => Invalid ** Changed in: linux-oem (Ubuntu) Status: Incomplete => 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/1740972 Title: No external microphone be detected via headset jack on a dell machine Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-oem package in Ubuntu: Invalid Status in linux source package in Xenial: Invalid Status in linux-oem source package in Xenial: New Bug description: Plug a headset into the headset jack check external microphone Expected results: external microphone should wrok well Actual results: No external microphone be detected To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1740972/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1740973] Re: Two front mics can't work on a lenovo machine
** Also affects: linux-oem (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux-oem (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux-oem (Ubuntu) Status: New => Invalid ** Changed in: linux (Ubuntu Xenial) Status: New => 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/1740973 Title: Two front mics can't work on a lenovo machine Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-oem package in Ubuntu: Invalid Status in linux source package in Xenial: Invalid Status in linux-oem source package in Xenial: New Bug description: There are two front mics on this lenovo machine. The test case 'audio/microphone-plug-detection' is always failed To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1740973/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1740974] Re: [800 G3 SFF] [800 G3 DM]External microphone of headset(3-ring) is working, 2-ring mic not working, both not shown in sound settings
** Also affects: linux-oem (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux-oem (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Status: New => Invalid ** Changed in: linux-oem (Ubuntu) Status: New => 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/1740974 Title: [800 G3 SFF] [800 G3 DM]External microphone of headset(3-ring) is working, 2-ring mic not working, both not shown in sound settings Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-oem package in Ubuntu: Invalid Status in linux source package in Xenial: Invalid Status in linux-oem source package in Xenial: New Bug description: External microphone of headset(3-ring) is working, 2-ring mic not working, both not shown in sound settings. Steps: 1. Plug headset(3-ring) or microphone (2-ring) 2. Observe input device in sound setting Expected results: Microphone should be detected and working Actual results: Microphone is not detected, only 3-ring mic (from headset) is working To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1740974/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1741206] Re: QCA Rome bluetooth failed to work after applying reset-resume quirk
** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux-oem (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux-oem (Ubuntu) Status: New => Invalid ** Changed in: linux (Ubuntu Xenial) Status: New => 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/1741206 Title: QCA Rome bluetooth failed to work after applying reset-resume quirk Status in linux package in Ubuntu: Triaged Status in linux-oem package in Ubuntu: Invalid Status in linux source package in Xenial: Invalid Status in linux-oem source package in Xenial: New Bug description: == SRU Justification == [Impact] Some QCA ROME bluetooth devices does not work after runtime suspend/resume after SRU LP: #1734020. [Fix] The commit let btusb reset at second time it resume, i.e. btusb_open(). The btusb stops working because the reset happens *after* btusb_open(). The reset should be done at hub port initialization, before btusb_probe(). Revert the bad commit and use the reset-resume quirk in USB core stack. [Test] Cherry-picked the commit into Artful/OEM kernel and the issue is fixed. [Regression Potential] Low. This is limited to QCA Rome, also verified by the original quirk author. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1741206/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1740972] 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 1740972 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/1740972 Title: No external microphone be detected via headset jack on a dell machine Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-oem package in Ubuntu: Invalid Status in linux source package in Xenial: Invalid Status in linux-oem source package in Xenial: New Bug description: Plug a headset into the headset jack check external microphone Expected results: external microphone should wrok well Actual results: No external microphone be detected To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1740972/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1730550] Re: e1000e in 4.4.0-97-generic breaks 82574L under heavy load.
** Changed in: linux (Ubuntu Zesty) Status: In Progress => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1730550 Title: e1000e in 4.4.0-97-generic breaks 82574L under heavy load. Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Status in linux source package in Zesty: Won't Fix Status in linux source package in Artful: In Progress Bug description: == SRU Justification == This issue was first reported on the netdev email list by Lennart Sorensen: https://www.mail-archive.com/netdev@vger.kernel.org/msg178170.html Commit 16ecba59bc333d6282ee057fb02339f77a880beb causes link drops on the 82574L under heavy load. "Unfortunately this commit changed the driver to assume that the Other Causes interrupt can only mean link state change and hence sets the flag that (unfortunately) means both link is down and link state should be checked. Since this now happens 3000 times per second, the chances of it happening while the watchdog_task is checking the link state becomes pretty high, and it if does happen to coincice, then the watchdog_task will reset the adapter, which causes a real loss of link." The original reported experienced this issue on a Supermicro X7SPA-HF-D525 server board. However, the bug is now seen on many servers running X9DBL-1F server boards. This bug is fixed by commits 19110cfbb34 and 4aea7a5c5e9, which were both added to mainline in v4.15-rc1. The commit that introduced this bug,16ecba5, was added to mainlien in v4.5-rc1. However, Xenial recived this commit as well as commit 531ff577a. Bionic master-next does not need these commits, since it got them via bug 1735843 and the 4.14.3 updates. == Fixes == 19110cfbb34 ("e1000e: Separate signaling for link check/link up") 4aea7a5c5e9 ("e1000e: Avoid receiver overrun interrupt bursts") == Regression Potential == These commits are specific to e1000. == Test Case == A test kernel was built with these patches and tested by the original bug reporter. The bug reporter states the test kernel resolved the bug. == Original Bug Descriptio == This issue was first reported on the netdev email list by Lennart Sorensen: https://www.mail-archive.com/netdev@vger.kernel.org/msg178170.html Commit 16ecba59bc333d6282ee057fb02339f77a880beb causes link drops on the 82574L under heavy load. "Unfortunately this commit changed the driver to assume that the Other Causes interrupt can only mean link state change and hence sets the flag that (unfortunately) means both link is down and link state should be checked. Since this now happens 3000 times per second, the chances of it happening while the watchdog_task is checking the link state becomes pretty high, and it if does happen to coincice, then the watchdog_task will reset the adapter, which causes a real loss of link." A fix for this issue was accepted into the net-next branch, along with other e1000e/igb patches: https://git.kernel.org/pub/scm/linux/kernel/git/davem/net- next.git/commit/?id=f44dea3421b47d355a835e9cfcc59ca7318575a9 The original reported experienced this issue on a Supermicro X7SPA- HF-D525 server board. We see this issue on many servers running X9DBL- 1F server boards. Both boards use the Intel 82574L for the network interfaces. We see messages like this under heavy load: [Nov 6 15:42] e1000e: eth0 NIC Link is Down [ +0.001670] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx [Nov 6 16:10] e1000e: eth0 NIC Link is Down [ +0.008505] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx [Nov 7 00:49] e1000e: eth0 NIC Link is Down [ +2.235111] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx We have confirmed that the connected switch sees the link drops also, to these are not false alarms from the e1000e driver. # lsb_release -rd Description: Ubuntu 16.04.2 LTS Release: 16.04 I could not cleanly apply the net-next patch to 4.4.0 so I tested with just the following cherry picked changes on the latest 4.4.0 kernel source package. https://patchwork.ozlabs.org/patch/823942/ https://patchwork.ozlabs.org/patch/823945/ https://patchwork.ozlabs.org/patch/823940/ https://patchwork.ozlabs.org/patch/823941/ https://patchwork.ozlabs.org/patch/823939/ Although it's my understanding the first two are the critical ones for the race condition. I have been running with the patches e1000e kernel driver, under network load for 7 days and I no longer see the network interface drops. Could we pull these changes into the Ubuntu 4.4.0 kernel ? Thanks --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 19 07:34 seq crw-rw 1 root audio 116, 33 Jul 19 07:34 timer AplayDevices: Er
[Kernel-packages] [Bug 1743094] Re: hibernation broken (freezes with resume) in kernel linux-image-4.13.0-26-generic
I can also confirm that with 4.13.0-30, hibernate did not work, but installing 4.14.13-041413-generic works perfectly. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1743094 Title: hibernation broken (freezes with resume) in kernel linux- image-4.13.0-26-generic Status in linux package in Ubuntu: Incomplete Bug description: After hibernating the system and than resuming it the system reboots notifying that it is resuming and than stops/freezes. The system does not respond to anything (no tty's other notifying textg are available). After booting kernel 4.10-042 the hibernation and hibride hibernation/sleep functions as proposed. --- ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jb 1717 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux 18.3 HibernationDevice: RESUME=UUID=00059f88-0cf2-44a0-a23d-f0a995cb1478 InstallationDate: Installed on 2017-12-10 (34 days ago) InstallationMedia: Linux Mint 18.3 "Sylvia" - Release amd64 20171124 MachineType: Acer Aspire S3-391 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-26-generic root=UUID=5397ffb7-8114-45c4-824f-b1da7cce468c ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13 RelatedPackageVersions: linux-restricted-modules-4.13.0-26-generic N/A linux-backports-modules-4.13.0-26-generic N/A linux-firmware 1.157.14 Tags: sylvia Uname: Linux 4.13.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/31/2012 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.10 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Hummingbird2 dmi.board.vendor: Acer dmi.board.version: V2.10 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.10 dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.10:bd10/31/2012:svnAcer:pnAspireS3-391:pvrV2.10:rvnAcer:rnHummingbird2:rvrV2.10:cvnAcer:ct10:cvrV2.10: dmi.product.family: ChiefRiver System dmi.product.name: Aspire S3-391 dmi.product.version: V2.10 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1743094/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1738972] Re: [A] KVM Windows BSOD on 4.13.x
** Also affects: linux (Ubuntu Artful) 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/1738972 Title: [A] KVM Windows BSOD on 4.13.x Status in linux package in Ubuntu: Triaged Status in linux source package in Artful: New Bug description: == SRU Justification == Impact: Windows 2016 and 10 VMs running in Qemu VMs using KVM trigger BSODs under certain memory conditions Fix: Single follow-up upstream cherry pick which fixes the problem. Regression Potential: Merged in 4.15 and 4.14.6, tested by multiple affected users. --- see https://marc.info/?l=linux-kernel&m=151203441531472&w=2 for the long writeup 58582f04bc87b9d8d848d9163ce3355dd6f00602 is the cherry-pick in 4.14-6 (only context changes outside of the actual diff) b1394e745b9453dcb5b0671c205b770e87dedb87 is the fix as applied in 4.15-rc3 I'll send the SRU patch as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1738972/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1743672] Re: the wifi driver is always hard blocked on a lenovo laptop
** Also affects: linux-oem (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux-oem (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux-oem (Ubuntu) Status: New => Invalid ** Changed in: linux (Ubuntu Xenial) Status: New => 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/1743672 Title: the wifi driver is always hard blocked on a lenovo laptop Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-oem package in Ubuntu: Invalid Status in linux source package in Xenial: Invalid Status in linux-oem source package in Xenial: New Bug description: On this machine, there is no wifi enable/disable hw switch, but the wifi driver is always reported the wifi radio is hard blocked by switch. The kernel is Artful and OEM kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1743672/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1706247] Re: Add support for 16g huge pages on Ubuntu 16.04.2 PowerNV
** Changed in: linux (Ubuntu Zesty) Status: In Progress => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1706247 Title: Add support for 16g huge pages on Ubuntu 16.04.2 PowerNV Status in The Ubuntu-power-systems project: Incomplete Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Status in linux source package in Zesty: Won't Fix Status in linux source package in Artful: In Progress Bug description: 16G Huge Pages are not supported on PowerNV (bare metal) installations. Ubuntu 16.04.2 still allows 16G huge pages to be turned on. Contact Information = Mike Hollinger (mchol...@us.ibm.com) ---uname output--- Linux aprilmin4 4.4.0-83-generic #106-Ubuntu SMP Mon Jun 26 17:53:54 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux Machine Type = 8335-GTB ---Debugger--- A debugger is not configured ---Steps to Reproduce--- 1. Add the following to the kernel boot args (either via editing the petitboot boot option manually, or updating /boot/grub/grub.cfg: default_hugepagesz=16G hugepagesz=16G hugepages=4 2. Boot Linux 3. Observe that the kernel believes 16G huge pages are available: ubuntu@aprilmin7:~$ cat /proc/meminfo | grep -i huge AnonHugePages:475136 kB HugePages_Total: 0 HugePages_Free:0 HugePages_Rsvd:0 HugePages_Surp:0 Hugepagesize: 16777216 kB ubuntu@aprilmin7:~$ ls /sys/devices/system/node/node0/hugepages hugepages-1024kB hugepages-16384kB hugepages-16777216kB Stack trace output: no Oops output: no System Dump Info: The system is not configured to capture a system dump. *Additional Instructions for Mike Hollinger (mchol...@us.ibm.com): -Post a private note with access information to the machine that the bug is occuring on. -Attach sysctl -a output output to the bug. This may be recreated on any bare metal POWER8 server with Ubuntu 16.04.2; I haven't checked other versions of Ubuntu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1706247/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1744935] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1744935/+attachment/5041747/+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/1744935 Title: [i915] Display Corruption Status in linux package in Ubuntu: Confirmed Bug description: Sometime during a regular package update of Ubuntu of 17.10 I started having screen corruption issues within GL apps (e.g. WebGL on google maps) on both the external screens as well as the laptops (Thinkpad T460p), but then spread further to the regular desktop. I updated to Ubuntu 18.04 to try to resolve the issue and then even updated the kernel to the Linux-4.15-rc8 (4.15.0-994-generic) but the issues remain on both Wayland and Xorg. It seems related to the 3D acceleration since the corruption only starts with gdm, not on the framebuffer before. The issue happens on every boot. The i915 module is loaded with its default parameters, the nvidia card is deactivated with switcheroo and the proprietary driver has never been installed. The corruption is best described as flashing distortions associated with timers and/or input events. Sometimes a whole triangular section of up to a quarter of the double-screen setup is streched and/or discolored or blacked out. Sometimes black squares (a few pixels) splatter the whole screen for a few frames until a damaged region is updated. It looks like some kind of shader issue. Sometimes the screen gets stuck for a few seconds (presumably the hang from the crashdump attached), so it's possible that there are multiple issues but I can't discern them. dmesg reports: ` [31026.161705] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [31731.589497] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [32477.060892] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [35533.800723] [drm] GPU HANG: ecode 9:0:0x85db, in gnome-shell [14269], reason: Hang on rcs0, action: reset [35533.800725] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace. [35533.800725] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel [35533.800725] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue. [35533.800726] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it. [35533.800726] [drm] GPU crash dump saved to /sys/class/drm/card1/error [35533.800768] i915 :00:02.0: Resetting rcs0 after gpu hang [36101.847545] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [41209.093879] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [43073.711135] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [43339.548927] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [43886.208705] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [44617.864814] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [45925.860575] i915 :00:02.0: Resetting rcs0 after gpu hang ` The memory size in UEFI is already set to the maximum of 512Mb. --- ApportVersion: 2.20.8-0ubuntu6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1396 F pulseaudio abr1860 F pulseaudio DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=c566c6bc-3708-4170-8812-823802420564 InstallationDate: Installed on 2017-05-30 (238 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) MachineType: LENOVO 20FW003PMZ Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-25-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4
[Kernel-packages] [Bug 1744935] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1744935/+attachment/5041746/+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/1744935 Title: [i915] Display Corruption Status in linux package in Ubuntu: Confirmed Bug description: Sometime during a regular package update of Ubuntu of 17.10 I started having screen corruption issues within GL apps (e.g. WebGL on google maps) on both the external screens as well as the laptops (Thinkpad T460p), but then spread further to the regular desktop. I updated to Ubuntu 18.04 to try to resolve the issue and then even updated the kernel to the Linux-4.15-rc8 (4.15.0-994-generic) but the issues remain on both Wayland and Xorg. It seems related to the 3D acceleration since the corruption only starts with gdm, not on the framebuffer before. The issue happens on every boot. The i915 module is loaded with its default parameters, the nvidia card is deactivated with switcheroo and the proprietary driver has never been installed. The corruption is best described as flashing distortions associated with timers and/or input events. Sometimes a whole triangular section of up to a quarter of the double-screen setup is streched and/or discolored or blacked out. Sometimes black squares (a few pixels) splatter the whole screen for a few frames until a damaged region is updated. It looks like some kind of shader issue. Sometimes the screen gets stuck for a few seconds (presumably the hang from the crashdump attached), so it's possible that there are multiple issues but I can't discern them. dmesg reports: ` [31026.161705] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [31731.589497] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [32477.060892] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [35533.800723] [drm] GPU HANG: ecode 9:0:0x85db, in gnome-shell [14269], reason: Hang on rcs0, action: reset [35533.800725] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace. [35533.800725] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel [35533.800725] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue. [35533.800726] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it. [35533.800726] [drm] GPU crash dump saved to /sys/class/drm/card1/error [35533.800768] i915 :00:02.0: Resetting rcs0 after gpu hang [36101.847545] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [41209.093879] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [43073.711135] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [43339.548927] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [43886.208705] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [44617.864814] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [45925.860575] i915 :00:02.0: Resetting rcs0 after gpu hang ` The memory size in UEFI is already set to the maximum of 512Mb. --- ApportVersion: 2.20.8-0ubuntu6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1396 F pulseaudio abr1860 F pulseaudio DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=c566c6bc-3708-4170-8812-823802420564 InstallationDate: Installed on 2017-05-30 (238 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) MachineType: LENOVO 20FW003PMZ Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-25-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13 PulseLis
[Kernel-packages] [Bug 1744935] Re: [i915] Display Corruption
apport information ** Tags added: apport-collected ** Description changed: Sometime during a regular package update of Ubuntu of 17.10 I started having screen corruption issues within GL apps (e.g. WebGL on google maps) on both the external screens as well as the laptops (Thinkpad T460p), but then spread further to the regular desktop. I updated to Ubuntu 18.04 to try to resolve the issue and then even updated the kernel to the Linux-4.15-rc8 (4.15.0-994-generic) but the issues remain on both Wayland and Xorg. It seems related to the 3D acceleration since the corruption only starts with gdm, not on the framebuffer before. The issue happens on every boot. The i915 module is loaded with its default parameters, the nvidia card is deactivated with switcheroo and the proprietary driver has never been installed. The corruption is best described as flashing distortions associated with timers and/or input events. Sometimes a whole triangular section of up to a quarter of the double-screen setup is streched and/or discolored or blacked out. Sometimes black squares (a few pixels) splatter the whole screen for a few frames until a damaged region is updated. It looks like some kind of shader issue. Sometimes the screen gets stuck for a few seconds (presumably the hang from the crashdump attached), so it's possible that there are multiple issues but I can't discern them. dmesg reports: ` [31026.161705] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [31731.589497] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [32477.060892] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [35533.800723] [drm] GPU HANG: ecode 9:0:0x85db, in gnome-shell [14269], reason: Hang on rcs0, action: reset [35533.800725] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace. [35533.800725] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel [35533.800725] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue. [35533.800726] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it. [35533.800726] [drm] GPU crash dump saved to /sys/class/drm/card1/error [35533.800768] i915 :00:02.0: Resetting rcs0 after gpu hang [36101.847545] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [41209.093879] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [43073.711135] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [43339.548927] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [43886.208705] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [44617.864814] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [45925.860575] i915 :00:02.0: Resetting rcs0 after gpu hang ` The memory size in UEFI is already set to the maximum of 512Mb. + --- + ApportVersion: 2.20.8-0ubuntu6 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: gdm1396 F pulseaudio + abr1860 F pulseaudio + DistroRelease: Ubuntu 18.04 + HibernationDevice: RESUME=UUID=c566c6bc-3708-4170-8812-823802420564 + InstallationDate: Installed on 2017-05-30 (238 days ago) + InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) + MachineType: LENOVO 20FW003PMZ + Package: linux (not installed) + ProcFB: 0 inteldrmfb + ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-25-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash + ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13 + PulseList: + Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied + No PulseAudio daemon running, or not running as session daemon. + RelatedPackageVersions: + linux-restricted-modules-4.13.0-25-generic N/A + linux-backports-modules-4.13.0-25-generic N/A + li
[Kernel-packages] [Bug 1744935] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1744935/+attachment/5041750/+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/1744935 Title: [i915] Display Corruption Status in linux package in Ubuntu: Confirmed Bug description: Sometime during a regular package update of Ubuntu of 17.10 I started having screen corruption issues within GL apps (e.g. WebGL on google maps) on both the external screens as well as the laptops (Thinkpad T460p), but then spread further to the regular desktop. I updated to Ubuntu 18.04 to try to resolve the issue and then even updated the kernel to the Linux-4.15-rc8 (4.15.0-994-generic) but the issues remain on both Wayland and Xorg. It seems related to the 3D acceleration since the corruption only starts with gdm, not on the framebuffer before. The issue happens on every boot. The i915 module is loaded with its default parameters, the nvidia card is deactivated with switcheroo and the proprietary driver has never been installed. The corruption is best described as flashing distortions associated with timers and/or input events. Sometimes a whole triangular section of up to a quarter of the double-screen setup is streched and/or discolored or blacked out. Sometimes black squares (a few pixels) splatter the whole screen for a few frames until a damaged region is updated. It looks like some kind of shader issue. Sometimes the screen gets stuck for a few seconds (presumably the hang from the crashdump attached), so it's possible that there are multiple issues but I can't discern them. dmesg reports: ` [31026.161705] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [31731.589497] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [32477.060892] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [35533.800723] [drm] GPU HANG: ecode 9:0:0x85db, in gnome-shell [14269], reason: Hang on rcs0, action: reset [35533.800725] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace. [35533.800725] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel [35533.800725] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue. [35533.800726] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it. [35533.800726] [drm] GPU crash dump saved to /sys/class/drm/card1/error [35533.800768] i915 :00:02.0: Resetting rcs0 after gpu hang [36101.847545] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [41209.093879] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [43073.711135] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [43339.548927] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [43886.208705] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [44617.864814] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [45925.860575] i915 :00:02.0: Resetting rcs0 after gpu hang ` The memory size in UEFI is already set to the maximum of 512Mb. --- ApportVersion: 2.20.8-0ubuntu6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1396 F pulseaudio abr1860 F pulseaudio DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=c566c6bc-3708-4170-8812-823802420564 InstallationDate: Installed on 2017-05-30 (238 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) MachineType: LENOVO 20FW003PMZ Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-25-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13 PulseL
[Kernel-packages] [Bug 1744935] JournalErrors.txt
apport information ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1744935/+attachment/5041749/+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/1744935 Title: [i915] Display Corruption Status in linux package in Ubuntu: Confirmed Bug description: Sometime during a regular package update of Ubuntu of 17.10 I started having screen corruption issues within GL apps (e.g. WebGL on google maps) on both the external screens as well as the laptops (Thinkpad T460p), but then spread further to the regular desktop. I updated to Ubuntu 18.04 to try to resolve the issue and then even updated the kernel to the Linux-4.15-rc8 (4.15.0-994-generic) but the issues remain on both Wayland and Xorg. It seems related to the 3D acceleration since the corruption only starts with gdm, not on the framebuffer before. The issue happens on every boot. The i915 module is loaded with its default parameters, the nvidia card is deactivated with switcheroo and the proprietary driver has never been installed. The corruption is best described as flashing distortions associated with timers and/or input events. Sometimes a whole triangular section of up to a quarter of the double-screen setup is streched and/or discolored or blacked out. Sometimes black squares (a few pixels) splatter the whole screen for a few frames until a damaged region is updated. It looks like some kind of shader issue. Sometimes the screen gets stuck for a few seconds (presumably the hang from the crashdump attached), so it's possible that there are multiple issues but I can't discern them. dmesg reports: ` [31026.161705] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [31731.589497] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [32477.060892] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [35533.800723] [drm] GPU HANG: ecode 9:0:0x85db, in gnome-shell [14269], reason: Hang on rcs0, action: reset [35533.800725] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace. [35533.800725] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel [35533.800725] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue. [35533.800726] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it. [35533.800726] [drm] GPU crash dump saved to /sys/class/drm/card1/error [35533.800768] i915 :00:02.0: Resetting rcs0 after gpu hang [36101.847545] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [41209.093879] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [43073.711135] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [43339.548927] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [43886.208705] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [44617.864814] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [45925.860575] i915 :00:02.0: Resetting rcs0 after gpu hang ` The memory size in UEFI is already set to the maximum of 512Mb. --- ApportVersion: 2.20.8-0ubuntu6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1396 F pulseaudio abr1860 F pulseaudio DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=c566c6bc-3708-4170-8812-823802420564 InstallationDate: Installed on 2017-05-30 (238 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) MachineType: LENOVO 20FW003PMZ Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-25-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash ProcVersionSignature: Ubuntu 4.13.0-25.29-generic
[Kernel-packages] [Bug 1744935] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1744935/+attachment/5041753/+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/1744935 Title: [i915] Display Corruption Status in linux package in Ubuntu: Confirmed Bug description: Sometime during a regular package update of Ubuntu of 17.10 I started having screen corruption issues within GL apps (e.g. WebGL on google maps) on both the external screens as well as the laptops (Thinkpad T460p), but then spread further to the regular desktop. I updated to Ubuntu 18.04 to try to resolve the issue and then even updated the kernel to the Linux-4.15-rc8 (4.15.0-994-generic) but the issues remain on both Wayland and Xorg. It seems related to the 3D acceleration since the corruption only starts with gdm, not on the framebuffer before. The issue happens on every boot. The i915 module is loaded with its default parameters, the nvidia card is deactivated with switcheroo and the proprietary driver has never been installed. The corruption is best described as flashing distortions associated with timers and/or input events. Sometimes a whole triangular section of up to a quarter of the double-screen setup is streched and/or discolored or blacked out. Sometimes black squares (a few pixels) splatter the whole screen for a few frames until a damaged region is updated. It looks like some kind of shader issue. Sometimes the screen gets stuck for a few seconds (presumably the hang from the crashdump attached), so it's possible that there are multiple issues but I can't discern them. dmesg reports: ` [31026.161705] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [31731.589497] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [32477.060892] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [35533.800723] [drm] GPU HANG: ecode 9:0:0x85db, in gnome-shell [14269], reason: Hang on rcs0, action: reset [35533.800725] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace. [35533.800725] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel [35533.800725] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue. [35533.800726] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it. [35533.800726] [drm] GPU crash dump saved to /sys/class/drm/card1/error [35533.800768] i915 :00:02.0: Resetting rcs0 after gpu hang [36101.847545] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [41209.093879] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [43073.711135] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [43339.548927] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [43886.208705] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [44617.864814] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [45925.860575] i915 :00:02.0: Resetting rcs0 after gpu hang ` The memory size in UEFI is already set to the maximum of 512Mb. --- ApportVersion: 2.20.8-0ubuntu6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1396 F pulseaudio abr1860 F pulseaudio DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=c566c6bc-3708-4170-8812-823802420564 InstallationDate: Installed on 2017-05-30 (238 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) MachineType: LENOVO 20FW003PMZ Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-25-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash ProcVersionSignature: Ubuntu 4.13.0-25.
[Kernel-packages] [Bug 1744935] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1744935/+attachment/5041754/+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/1744935 Title: [i915] Display Corruption Status in linux package in Ubuntu: Confirmed Bug description: Sometime during a regular package update of Ubuntu of 17.10 I started having screen corruption issues within GL apps (e.g. WebGL on google maps) on both the external screens as well as the laptops (Thinkpad T460p), but then spread further to the regular desktop. I updated to Ubuntu 18.04 to try to resolve the issue and then even updated the kernel to the Linux-4.15-rc8 (4.15.0-994-generic) but the issues remain on both Wayland and Xorg. It seems related to the 3D acceleration since the corruption only starts with gdm, not on the framebuffer before. The issue happens on every boot. The i915 module is loaded with its default parameters, the nvidia card is deactivated with switcheroo and the proprietary driver has never been installed. The corruption is best described as flashing distortions associated with timers and/or input events. Sometimes a whole triangular section of up to a quarter of the double-screen setup is streched and/or discolored or blacked out. Sometimes black squares (a few pixels) splatter the whole screen for a few frames until a damaged region is updated. It looks like some kind of shader issue. Sometimes the screen gets stuck for a few seconds (presumably the hang from the crashdump attached), so it's possible that there are multiple issues but I can't discern them. dmesg reports: ` [31026.161705] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [31731.589497] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [32477.060892] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [35533.800723] [drm] GPU HANG: ecode 9:0:0x85db, in gnome-shell [14269], reason: Hang on rcs0, action: reset [35533.800725] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace. [35533.800725] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel [35533.800725] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue. [35533.800726] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it. [35533.800726] [drm] GPU crash dump saved to /sys/class/drm/card1/error [35533.800768] i915 :00:02.0: Resetting rcs0 after gpu hang [36101.847545] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [41209.093879] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [43073.711135] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [43339.548927] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [43886.208705] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [44617.864814] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [45925.860575] i915 :00:02.0: Resetting rcs0 after gpu hang ` The memory size in UEFI is already set to the maximum of 512Mb. --- ApportVersion: 2.20.8-0ubuntu6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1396 F pulseaudio abr1860 F pulseaudio DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=c566c6bc-3708-4170-8812-823802420564 InstallationDate: Installed on 2017-05-30 (238 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) MachineType: LENOVO 20FW003PMZ Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-25-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.1
[Kernel-packages] [Bug 1744935] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1744935/+attachment/5041748/+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/1744935 Title: [i915] Display Corruption Status in linux package in Ubuntu: Confirmed Bug description: Sometime during a regular package update of Ubuntu of 17.10 I started having screen corruption issues within GL apps (e.g. WebGL on google maps) on both the external screens as well as the laptops (Thinkpad T460p), but then spread further to the regular desktop. I updated to Ubuntu 18.04 to try to resolve the issue and then even updated the kernel to the Linux-4.15-rc8 (4.15.0-994-generic) but the issues remain on both Wayland and Xorg. It seems related to the 3D acceleration since the corruption only starts with gdm, not on the framebuffer before. The issue happens on every boot. The i915 module is loaded with its default parameters, the nvidia card is deactivated with switcheroo and the proprietary driver has never been installed. The corruption is best described as flashing distortions associated with timers and/or input events. Sometimes a whole triangular section of up to a quarter of the double-screen setup is streched and/or discolored or blacked out. Sometimes black squares (a few pixels) splatter the whole screen for a few frames until a damaged region is updated. It looks like some kind of shader issue. Sometimes the screen gets stuck for a few seconds (presumably the hang from the crashdump attached), so it's possible that there are multiple issues but I can't discern them. dmesg reports: ` [31026.161705] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [31731.589497] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [32477.060892] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [35533.800723] [drm] GPU HANG: ecode 9:0:0x85db, in gnome-shell [14269], reason: Hang on rcs0, action: reset [35533.800725] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace. [35533.800725] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel [35533.800725] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue. [35533.800726] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it. [35533.800726] [drm] GPU crash dump saved to /sys/class/drm/card1/error [35533.800768] i915 :00:02.0: Resetting rcs0 after gpu hang [36101.847545] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [41209.093879] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [43073.711135] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [43339.548927] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [43886.208705] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [44617.864814] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [45925.860575] i915 :00:02.0: Resetting rcs0 after gpu hang ` The memory size in UEFI is already set to the maximum of 512Mb. --- ApportVersion: 2.20.8-0ubuntu6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1396 F pulseaudio abr1860 F pulseaudio DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=c566c6bc-3708-4170-8812-823802420564 InstallationDate: Installed on 2017-05-30 (238 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) MachineType: LENOVO 20FW003PMZ Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-25-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
[Kernel-packages] [Bug 1744935] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1744935/+attachment/5041751/+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/1744935 Title: [i915] Display Corruption Status in linux package in Ubuntu: Confirmed Bug description: Sometime during a regular package update of Ubuntu of 17.10 I started having screen corruption issues within GL apps (e.g. WebGL on google maps) on both the external screens as well as the laptops (Thinkpad T460p), but then spread further to the regular desktop. I updated to Ubuntu 18.04 to try to resolve the issue and then even updated the kernel to the Linux-4.15-rc8 (4.15.0-994-generic) but the issues remain on both Wayland and Xorg. It seems related to the 3D acceleration since the corruption only starts with gdm, not on the framebuffer before. The issue happens on every boot. The i915 module is loaded with its default parameters, the nvidia card is deactivated with switcheroo and the proprietary driver has never been installed. The corruption is best described as flashing distortions associated with timers and/or input events. Sometimes a whole triangular section of up to a quarter of the double-screen setup is streched and/or discolored or blacked out. Sometimes black squares (a few pixels) splatter the whole screen for a few frames until a damaged region is updated. It looks like some kind of shader issue. Sometimes the screen gets stuck for a few seconds (presumably the hang from the crashdump attached), so it's possible that there are multiple issues but I can't discern them. dmesg reports: ` [31026.161705] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [31731.589497] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [32477.060892] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [35533.800723] [drm] GPU HANG: ecode 9:0:0x85db, in gnome-shell [14269], reason: Hang on rcs0, action: reset [35533.800725] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace. [35533.800725] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel [35533.800725] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue. [35533.800726] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it. [35533.800726] [drm] GPU crash dump saved to /sys/class/drm/card1/error [35533.800768] i915 :00:02.0: Resetting rcs0 after gpu hang [36101.847545] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [41209.093879] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [43073.711135] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [43339.548927] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [43886.208705] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [44617.864814] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [45925.860575] i915 :00:02.0: Resetting rcs0 after gpu hang ` The memory size in UEFI is already set to the maximum of 512Mb. --- ApportVersion: 2.20.8-0ubuntu6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1396 F pulseaudio abr1860 F pulseaudio DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=c566c6bc-3708-4170-8812-823802420564 InstallationDate: Installed on 2017-05-30 (238 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) MachineType: LENOVO 20FW003PMZ Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-25-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13 PulseL
[Kernel-packages] [Bug 1744935] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1744935/+attachment/5041752/+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/1744935 Title: [i915] Display Corruption Status in linux package in Ubuntu: Confirmed Bug description: Sometime during a regular package update of Ubuntu of 17.10 I started having screen corruption issues within GL apps (e.g. WebGL on google maps) on both the external screens as well as the laptops (Thinkpad T460p), but then spread further to the regular desktop. I updated to Ubuntu 18.04 to try to resolve the issue and then even updated the kernel to the Linux-4.15-rc8 (4.15.0-994-generic) but the issues remain on both Wayland and Xorg. It seems related to the 3D acceleration since the corruption only starts with gdm, not on the framebuffer before. The issue happens on every boot. The i915 module is loaded with its default parameters, the nvidia card is deactivated with switcheroo and the proprietary driver has never been installed. The corruption is best described as flashing distortions associated with timers and/or input events. Sometimes a whole triangular section of up to a quarter of the double-screen setup is streched and/or discolored or blacked out. Sometimes black squares (a few pixels) splatter the whole screen for a few frames until a damaged region is updated. It looks like some kind of shader issue. Sometimes the screen gets stuck for a few seconds (presumably the hang from the crashdump attached), so it's possible that there are multiple issues but I can't discern them. dmesg reports: ` [31026.161705] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [31731.589497] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [32477.060892] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [35533.800723] [drm] GPU HANG: ecode 9:0:0x85db, in gnome-shell [14269], reason: Hang on rcs0, action: reset [35533.800725] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace. [35533.800725] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel [35533.800725] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue. [35533.800726] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it. [35533.800726] [drm] GPU crash dump saved to /sys/class/drm/card1/error [35533.800768] i915 :00:02.0: Resetting rcs0 after gpu hang [36101.847545] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [41209.093879] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [43073.711135] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [43339.548927] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [43886.208705] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [44617.864814] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [45925.860575] i915 :00:02.0: Resetting rcs0 after gpu hang ` The memory size in UEFI is already set to the maximum of 512Mb. --- ApportVersion: 2.20.8-0ubuntu6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1396 F pulseaudio abr1860 F pulseaudio DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=c566c6bc-3708-4170-8812-823802420564 InstallationDate: Installed on 2017-05-30 (238 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) MachineType: LENOVO 20FW003PMZ Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-25-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.1
[Kernel-packages] [Bug 1744935] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1744935/+attachment/5041757/+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/1744935 Title: [i915] Display Corruption Status in linux package in Ubuntu: Confirmed Bug description: Sometime during a regular package update of Ubuntu of 17.10 I started having screen corruption issues within GL apps (e.g. WebGL on google maps) on both the external screens as well as the laptops (Thinkpad T460p), but then spread further to the regular desktop. I updated to Ubuntu 18.04 to try to resolve the issue and then even updated the kernel to the Linux-4.15-rc8 (4.15.0-994-generic) but the issues remain on both Wayland and Xorg. It seems related to the 3D acceleration since the corruption only starts with gdm, not on the framebuffer before. The issue happens on every boot. The i915 module is loaded with its default parameters, the nvidia card is deactivated with switcheroo and the proprietary driver has never been installed. The corruption is best described as flashing distortions associated with timers and/or input events. Sometimes a whole triangular section of up to a quarter of the double-screen setup is streched and/or discolored or blacked out. Sometimes black squares (a few pixels) splatter the whole screen for a few frames until a damaged region is updated. It looks like some kind of shader issue. Sometimes the screen gets stuck for a few seconds (presumably the hang from the crashdump attached), so it's possible that there are multiple issues but I can't discern them. dmesg reports: ` [31026.161705] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [31731.589497] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [32477.060892] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [35533.800723] [drm] GPU HANG: ecode 9:0:0x85db, in gnome-shell [14269], reason: Hang on rcs0, action: reset [35533.800725] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace. [35533.800725] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel [35533.800725] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue. [35533.800726] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it. [35533.800726] [drm] GPU crash dump saved to /sys/class/drm/card1/error [35533.800768] i915 :00:02.0: Resetting rcs0 after gpu hang [36101.847545] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [41209.093879] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [43073.711135] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [43339.548927] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [43886.208705] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [44617.864814] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [45925.860575] i915 :00:02.0: Resetting rcs0 after gpu hang ` The memory size in UEFI is already set to the maximum of 512Mb. --- ApportVersion: 2.20.8-0ubuntu6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1396 F pulseaudio abr1860 F pulseaudio DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=c566c6bc-3708-4170-8812-823802420564 InstallationDate: Installed on 2017-05-30 (238 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) MachineType: LENOVO 20FW003PMZ Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-25-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13 Puls
[Kernel-packages] [Bug 1744935] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1744935/+attachment/5041759/+files/WifiSyslog.txt ** Changed in: linux (Ubuntu) Status: Incomplete => 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/1744935 Title: [i915] Display Corruption Status in linux package in Ubuntu: Confirmed Bug description: Sometime during a regular package update of Ubuntu of 17.10 I started having screen corruption issues within GL apps (e.g. WebGL on google maps) on both the external screens as well as the laptops (Thinkpad T460p), but then spread further to the regular desktop. I updated to Ubuntu 18.04 to try to resolve the issue and then even updated the kernel to the Linux-4.15-rc8 (4.15.0-994-generic) but the issues remain on both Wayland and Xorg. It seems related to the 3D acceleration since the corruption only starts with gdm, not on the framebuffer before. The issue happens on every boot. The i915 module is loaded with its default parameters, the nvidia card is deactivated with switcheroo and the proprietary driver has never been installed. The corruption is best described as flashing distortions associated with timers and/or input events. Sometimes a whole triangular section of up to a quarter of the double-screen setup is streched and/or discolored or blacked out. Sometimes black squares (a few pixels) splatter the whole screen for a few frames until a damaged region is updated. It looks like some kind of shader issue. Sometimes the screen gets stuck for a few seconds (presumably the hang from the crashdump attached), so it's possible that there are multiple issues but I can't discern them. dmesg reports: ` [31026.161705] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [31731.589497] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [32477.060892] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [35533.800723] [drm] GPU HANG: ecode 9:0:0x85db, in gnome-shell [14269], reason: Hang on rcs0, action: reset [35533.800725] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace. [35533.800725] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel [35533.800725] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue. [35533.800726] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it. [35533.800726] [drm] GPU crash dump saved to /sys/class/drm/card1/error [35533.800768] i915 :00:02.0: Resetting rcs0 after gpu hang [36101.847545] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [41209.093879] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [43073.711135] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [43339.548927] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [43886.208705] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [44617.864814] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [45925.860575] i915 :00:02.0: Resetting rcs0 after gpu hang ` The memory size in UEFI is already set to the maximum of 512Mb. --- ApportVersion: 2.20.8-0ubuntu6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1396 F pulseaudio abr1860 F pulseaudio DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=c566c6bc-3708-4170-8812-823802420564 InstallationDate: Installed on 2017-05-30 (238 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) MachineType: LENOVO 20FW003PMZ Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-25-generic root=/dev/mapper/ubuntu--vg-root ro quiet
[Kernel-packages] [Bug 1744945] [NEW] [Comm] IBM JDK >=8.0.5.7 integration into Ubuntu
You have been subscribed to a public bug: We will use this to track the 8.0.5.7 release packages ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Skipper Bug Screeners (skipper-screen-team) Status: New ** Tags: architecture-s39064 bugnameltc-163840 severity-high targetmilestone-inin--- -- [Comm] IBM JDK >=8.0.5.7 integration into Ubuntu https://bugs.launchpad.net/bugs/1744945 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1744945] [NEW] [Comm] IBM JDK >=8.0.5.7 integration into Ubuntu
Public bug reported: We will use this to track the 8.0.5.7 release packages ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Skipper Bug Screeners (skipper-screen-team) Status: New ** Tags: architecture-s39064 bugnameltc-163840 severity-high targetmilestone-inin--- ** Tags added: architecture-s39064 bugnameltc-163840 severity-high targetmilestone-inin--- ** Changed in: ubuntu Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team) ** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1744945 Title: [Comm] IBM JDK >=8.0.5.7 integration into Ubuntu Status in linux package in Ubuntu: New Bug description: We will use this to track the 8.0.5.7 release packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1744945/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1743027] [NEW] error loading realtime clock since upgrading to 17.10
You have been subscribed to a public bug: (originally asked over at askubuntu.com, but is still unresolved: https://askubuntu.com/questions/971349/problem-with-real-time-clock- since-upgrading-to-ubuntu-17-10) I recently upgraded from Ubuntu 17.04 to Ubuntu 17.10 using the software update process. The update completed without any errors, and Ubuntu 17.10 is now running without any major issues. However, I was running a script previously that uses rtcwake which has since stopped working. The script automatically hibernates my laptop after a set period of time in sleep mode, and was working perfectly in Ubuntu 17.04. In the process of troubleshooting, I discovered that the problem was with rtcwake which is complaining about /dev/rtc0 missing. Here is output from a sample rtcwake command: peter@haven:~$ rtcwake -m no -s 1300 rtcwake: assuming RTC uses UTC ... rtcwake: /dev/rtc0: unable to find device: No such file or directory I verified that in fact, that directory is missing. Since this was working prior to the upgrade, I have to assume that it was there previously, but I don't know for sure. In researching the error, I found some suggestions to get further information with timedatectl and hwclock, so here are the results from those commands as well. Output of timedatectl: peter@haven:~$ timedatectl Local time: Fri 2017-10-27 19:06:26 EDT Universal time: Fri 2017-10-27 23:06:26 UTC RTC time: n/a Time zone: America/New_York (EDT, -0400) Network time on: yes NTP synchronized: yes RTC in local TZ: no Output of hwclock --debug: peter@haven:~$ sudo hwclock --debug [sudo] password for peter: hwclock from util-linux 2.30.1 Trying to open: /dev/rtc0 Trying to open: /dev/rtc Trying to open: /dev/misc/rtc No usable clock interface found. hwclock: Cannot access the Hardware Clock via any known method. UPDATE When I boot with my old kernel, 4.10.0-37-generic the real-time clock works fine. I get the following RTC messages in dmesg when I boot the 4.13.0-16-generic kernel: peter@haven:~$ dmesg | grep -i rtc [0.089393] RTC time: 17:03:55, date: 11/01/17 [1.238784] rtc_cmos 00:01: RTC can wake from S4 [1.238794] rtc_cmos: probe of 00:01 failed with error -16 [1.295459] hctosys: unable to open rtc device (rtc0) UPDATE #2 Well, I was starting to believe that I had a hardware issue, since discovering I was unable to save changes to my BIOS and could not boot from USB. As it turns out, my laptop was bitten by this bug: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1734147 causing my BIOS to be locked in a read-only state. Once I resolved the BIOS issue, and fixed the USB boot problem, I did a live boot of Ubuntu 17.10. The issue with my real time clock still exists under this clean boot scenario, yet when I boot other distros, like Linux Mint 18.3 and the real time clock works fine. I feel this definitely has something to do with the Ubuntu install, perhaps even a kernel bug. UPDATE #3 More evidence to suggest this is a kernel bug: I live-booted a copy of Antergos Linux, which was using the Arch kernel 4.14.12-1-ARCH and it exhibited the same problem with the real time clock as Ubuntu 17.10. In addition, I confirmed that the Linux Mint version I booted earlier (see Update #2) was on the Ubuntu kernel 4.10.0-38-generic. So, I suspect that sometime between kernels 4.10 and 4.13 this bug was introduced. --- ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: peter 1832 F pulseaudio /dev/snd/controlC1: peter 1832 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 HibernationDevice: RESUME=UUID=a602efe1-467d-4ac4-806f-1b931c91cdad InstallationDate: Installed on 2017-04-05 (292 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: LENOVO 20354 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-25-generic.efi.signed root=UUID=fa5454aa-9072-475d-b515-acd51a6166cc ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13 RelatedPackageVersions: linux-restricted-modules-4.13.0-25-generic N/A linux-backports-modules-4.13.0-25-generic N/A linux-firmware 1.169.1 Tags: wayland-session artful Uname: Linux 4.13.0-25-generic x86_64 UpgradeStatus: Upgraded to artful on 2017-10-24 (90 days ago) UserGroups: adm cdrom dip kismet lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/21/2015 dmi.bios.vendor: LENOVO dmi.bios.version: 9BCN91WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lancer 5A5 dmi.board.vendor: LENOVO dmi.board.version: 31900058WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Z50-70 dmi.modalia
[Kernel-packages] [Bug 1744510] Re: RF mouse (with USB dongle) doesn't work after reboot until I unplug it and plug it back in
I am using the nvidia driver for my graphics card. It sounds like I can't do that with an upstream kernel build? Is that correct? Well my X server automatically use the open-source Nouveau drivers if the nvidia driver isn't in the kernel, or do I need to reconfigure something manually? And it looks like the virtualbox driver won't build with the upstream kernel header files. Can you advise me on the best way to temporarily disable the virtualbox driver so that it can be reenabled easily and reliably when I'm done doing this testing? 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/1744510 Title: RF mouse (with USB dongle) doesn't work after reboot until I unplug it and plug it back in Status in linux package in Ubuntu: Incomplete Bug description: My wireless mouse doesn't work after I reboot until I unplug its USB dongle and plug it back in. I don't see anything in Xorg.0.log which obviously explains this problem. It looks like the mouse is added to the X server configuration on startup without any problems, at least unless I'm misreading the log, and then the second time it's added, when I unplug it and plug it back in, it looks like the same thing happens in the log, but then the mouse works. This was a problem in 17.04 as well, i.e., it isn't new in 17.10. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xserver-xorg-core 2:1.19.5-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13 Uname: Linux 4.13.0-25-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 384.111 Tue Dec 19 23:51:45 PST 2017 GCC version: gcc version 7.2.0 (Ubuntu 7.2.0-8ubuntu3) .tmp.unity_support_test.0: ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Jan 20 18:31:15 2018 DistUpgraded: 2018-01-20 12:11:24,767 ERROR Cache can not be locked (E:Could not get lock /var/lib/dpkg/lock - open (11: Resource temporarily unavailable), E:Unable to lock the administration directory (/var/lib/dpkg/), is another process using it?) DistroCodename: artful DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GM204 [GeForce GTX 970] [10de:13c2] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Device [196e:1131] InstallationDate: Installed on 2016-01-16 (735 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: Acer Predator G6-710 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-25-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg-server UpgradeStatus: Upgraded to artful on 2018-01-20 (0 days ago) dmi.bios.date: 05/18/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R01-A4 dmi.board.name: Predator G6-710 dmi.board.vendor: Acer dmi.chassis.type: 3 dmi.chassis.vendor: Acer dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR01-A4:bd05/18/2016:svnAcer:pnPredatorG6-710:pvr:rvnAcer:rnPredatorG6-710:rvr:cvnAcer:ct3:cvr: dmi.product.family: Acer Desktop dmi.product.name: Predator G6-710 dmi.sys.vendor: Acer 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 17.2.4-0ubuntu1~17.10.2 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~17.10.2 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A 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: Sat Jan 20 17:16:47 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.5-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1744510/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1737640] Re: [SRU] /usr/sbin/fanctl: arithmetic expression: expecting primary | unconfigured interfaces cause ifup failures
This bug was fixed in the package ubuntu-fan - 0.12.9 --- ubuntu-fan (0.12.9) bionic; urgency=medium [ Andy Whitcroft ] * fanctl: fix config_filename when the interface does not have a width (LP: #1737640) -- Andreas Hasenack Thu, 04 Jan 2018 15:41:32 -0200 ** Changed in: ubuntu-fan (Ubuntu Bionic) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to ubuntu-fan in Ubuntu. https://bugs.launchpad.net/bugs/1737640 Title: [SRU] /usr/sbin/fanctl: arithmetic expression: expecting primary | unconfigured interfaces cause ifup failures Status in juju: Invalid Status in OPNFV: Fix Committed Status in ubuntu-fan package in Ubuntu: Fix Released Status in ubuntu-fan source package in Xenial: Fix Released Status in ubuntu-fan source package in Zesty: Won't Fix Status in ubuntu-fan source package in Artful: In Progress Status in ubuntu-fan source package in Bionic: Fix Released Bug description: [Impact] * This bug effects anyone deploying LXD with juju on a machine with interfaces configured as IP/mask. Since this is a very common use case, SRU is needed. [Test Case] * Detailed process can be seen at https://paste.ubuntu.com/26169937/ [Regression Potential] * Potential for regression is low because of the nature of the error. It's just missing a case stanza for interfaces that are defined with IP/mask [Other Info] * Original report: I'm seeing this error as the status of multiple containers in my deploy: http://paste.ubuntu.com/26166720/ I can't connect to the parent machines anymore either - it seems networking is totally hosed on the machines. This is with juju 2.3.1. To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1737640/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1743027] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1743027/+attachment/5041787/+files/WifiSyslog.txt ** Package changed: compiz-plugins-main (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1743027 Title: error loading realtime clock since upgrading to 17.10 Status in linux package in Ubuntu: Confirmed Bug description: (originally asked over at askubuntu.com, but is still unresolved: https://askubuntu.com/questions/971349/problem-with-real-time-clock- since-upgrading-to-ubuntu-17-10) I recently upgraded from Ubuntu 17.04 to Ubuntu 17.10 using the software update process. The update completed without any errors, and Ubuntu 17.10 is now running without any major issues. However, I was running a script previously that uses rtcwake which has since stopped working. The script automatically hibernates my laptop after a set period of time in sleep mode, and was working perfectly in Ubuntu 17.04. In the process of troubleshooting, I discovered that the problem was with rtcwake which is complaining about /dev/rtc0 missing. Here is output from a sample rtcwake command: peter@haven:~$ rtcwake -m no -s 1300 rtcwake: assuming RTC uses UTC ... rtcwake: /dev/rtc0: unable to find device: No such file or directory I verified that in fact, that directory is missing. Since this was working prior to the upgrade, I have to assume that it was there previously, but I don't know for sure. In researching the error, I found some suggestions to get further information with timedatectl and hwclock, so here are the results from those commands as well. Output of timedatectl: peter@haven:~$ timedatectl Local time: Fri 2017-10-27 19:06:26 EDT Universal time: Fri 2017-10-27 23:06:26 UTC RTC time: n/a Time zone: America/New_York (EDT, -0400) Network time on: yes NTP synchronized: yes RTC in local TZ: no Output of hwclock --debug: peter@haven:~$ sudo hwclock --debug [sudo] password for peter: hwclock from util-linux 2.30.1 Trying to open: /dev/rtc0 Trying to open: /dev/rtc Trying to open: /dev/misc/rtc No usable clock interface found. hwclock: Cannot access the Hardware Clock via any known method. UPDATE When I boot with my old kernel, 4.10.0-37-generic the real-time clock works fine. I get the following RTC messages in dmesg when I boot the 4.13.0-16-generic kernel: peter@haven:~$ dmesg | grep -i rtc [0.089393] RTC time: 17:03:55, date: 11/01/17 [1.238784] rtc_cmos 00:01: RTC can wake from S4 [1.238794] rtc_cmos: probe of 00:01 failed with error -16 [1.295459] hctosys: unable to open rtc device (rtc0) UPDATE #2 Well, I was starting to believe that I had a hardware issue, since discovering I was unable to save changes to my BIOS and could not boot from USB. As it turns out, my laptop was bitten by this bug: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1734147 causing my BIOS to be locked in a read-only state. Once I resolved the BIOS issue, and fixed the USB boot problem, I did a live boot of Ubuntu 17.10. The issue with my real time clock still exists under this clean boot scenario, yet when I boot other distros, like Linux Mint 18.3 and the real time clock works fine. I feel this definitely has something to do with the Ubuntu install, perhaps even a kernel bug. UPDATE #3 More evidence to suggest this is a kernel bug: I live-booted a copy of Antergos Linux, which was using the Arch kernel 4.14.12-1-ARCH and it exhibited the same problem with the real time clock as Ubuntu 17.10. In addition, I confirmed that the Linux Mint version I booted earlier (see Update #2) was on the Ubuntu kernel 4.10.0-38-generic. So, I suspect that sometime between kernels 4.10 and 4.13 this bug was introduced. --- ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: peter 1832 F pulseaudio /dev/snd/controlC1: peter 1832 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 HibernationDevice: RESUME=UUID=a602efe1-467d-4ac4-806f-1b931c91cdad InstallationDate: Installed on 2017-04-05 (292 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: LENOVO 20354 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-25-generic.efi.signed root=UUID=fa5454aa-9072-475d-b515-acd51a6166cc ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13 RelatedPackageVersions: linux-restricted-modules-4.13.0-25-
[Kernel-packages] [Bug 1738219] Re: the kernel is blackholing IPv6 packets to linkdown nexthops
** Changed in: linux (Ubuntu Zesty) Status: In Progress => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1738219 Title: the kernel is blackholing IPv6 packets to linkdown nexthops Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Status in linux source package in Zesty: Won't Fix Status in linux source package in Artful: In Progress Status in linux source package in Bionic: In Progress Bug description: == SRU Justification == When the 'ignore_routes_with_linkdown' sysctl is set, we should not consider linkdown nexthops during route lookup. While the code correctly verifies that the initially selected route ('match') has a carrier, it does not perform the same check in the subsequent multipath selection, resulting in a potential packet loss. In case the chosen route does not have a carrier and the sysctl is set, choose the initially selected route. This is a regression introduced by commit 35103d11173b in 4.3-rc1. Commit bbfcd7763 resolves this regression and is mainline as of 4.15-rc1. == Fix == commit bbfcd77631573ac4a9f57eb6169e04256a111bc1 Author: Ido Schimmel Date: Tue Nov 21 09:50:12 2017 +0200 ipv6: Do not consider linkdown nexthops during multipath == Regression Potential == This fix is specific to ipv6 and fixes a current regression. == Test Case == A test kernel was built with this patch and tested by the original bug reporter. The bug reporter states the test kernel resolved the bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1738219/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1744935] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1744935/+attachment/5041758/+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/1744935 Title: [i915] Display Corruption Status in linux package in Ubuntu: Confirmed Bug description: Sometime during a regular package update of Ubuntu of 17.10 I started having screen corruption issues within GL apps (e.g. WebGL on google maps) on both the external screens as well as the laptops (Thinkpad T460p), but then spread further to the regular desktop. I updated to Ubuntu 18.04 to try to resolve the issue and then even updated the kernel to the Linux-4.15-rc8 (4.15.0-994-generic) but the issues remain on both Wayland and Xorg. It seems related to the 3D acceleration since the corruption only starts with gdm, not on the framebuffer before. The issue happens on every boot. The i915 module is loaded with its default parameters, the nvidia card is deactivated with switcheroo and the proprietary driver has never been installed. The corruption is best described as flashing distortions associated with timers and/or input events. Sometimes a whole triangular section of up to a quarter of the double-screen setup is streched and/or discolored or blacked out. Sometimes black squares (a few pixels) splatter the whole screen for a few frames until a damaged region is updated. It looks like some kind of shader issue. Sometimes the screen gets stuck for a few seconds (presumably the hang from the crashdump attached), so it's possible that there are multiple issues but I can't discern them. dmesg reports: ` [31026.161705] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [31731.589497] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [32477.060892] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [35533.800723] [drm] GPU HANG: ecode 9:0:0x85db, in gnome-shell [14269], reason: Hang on rcs0, action: reset [35533.800725] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace. [35533.800725] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel [35533.800725] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue. [35533.800726] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it. [35533.800726] [drm] GPU crash dump saved to /sys/class/drm/card1/error [35533.800768] i915 :00:02.0: Resetting rcs0 after gpu hang [36101.847545] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [41209.093879] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [43073.711135] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [43339.548927] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [43886.208705] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [44617.864814] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [45925.860575] i915 :00:02.0: Resetting rcs0 after gpu hang ` The memory size in UEFI is already set to the maximum of 512Mb. --- ApportVersion: 2.20.8-0ubuntu6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1396 F pulseaudio abr1860 F pulseaudio DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=c566c6bc-3708-4170-8812-823802420564 InstallationDate: Installed on 2017-05-30 (238 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) MachineType: LENOVO 20FW003PMZ Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-25-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13 Puls
[Kernel-packages] [Bug 1744935] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1744935/+attachment/5041755/+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/1744935 Title: [i915] Display Corruption Status in linux package in Ubuntu: Confirmed Bug description: Sometime during a regular package update of Ubuntu of 17.10 I started having screen corruption issues within GL apps (e.g. WebGL on google maps) on both the external screens as well as the laptops (Thinkpad T460p), but then spread further to the regular desktop. I updated to Ubuntu 18.04 to try to resolve the issue and then even updated the kernel to the Linux-4.15-rc8 (4.15.0-994-generic) but the issues remain on both Wayland and Xorg. It seems related to the 3D acceleration since the corruption only starts with gdm, not on the framebuffer before. The issue happens on every boot. The i915 module is loaded with its default parameters, the nvidia card is deactivated with switcheroo and the proprietary driver has never been installed. The corruption is best described as flashing distortions associated with timers and/or input events. Sometimes a whole triangular section of up to a quarter of the double-screen setup is streched and/or discolored or blacked out. Sometimes black squares (a few pixels) splatter the whole screen for a few frames until a damaged region is updated. It looks like some kind of shader issue. Sometimes the screen gets stuck for a few seconds (presumably the hang from the crashdump attached), so it's possible that there are multiple issues but I can't discern them. dmesg reports: ` [31026.161705] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [31731.589497] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [32477.060892] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [35533.800723] [drm] GPU HANG: ecode 9:0:0x85db, in gnome-shell [14269], reason: Hang on rcs0, action: reset [35533.800725] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace. [35533.800725] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel [35533.800725] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue. [35533.800726] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it. [35533.800726] [drm] GPU crash dump saved to /sys/class/drm/card1/error [35533.800768] i915 :00:02.0: Resetting rcs0 after gpu hang [36101.847545] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [41209.093879] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [43073.711135] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [43339.548927] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [43886.208705] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [44617.864814] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [45925.860575] i915 :00:02.0: Resetting rcs0 after gpu hang ` The memory size in UEFI is already set to the maximum of 512Mb. --- ApportVersion: 2.20.8-0ubuntu6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1396 F pulseaudio abr1860 F pulseaudio DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=c566c6bc-3708-4170-8812-823802420564 InstallationDate: Installed on 2017-05-30 (238 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) MachineType: LENOVO 20FW003PMZ Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-25-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash ProcVersionSignature: Ubuntu 4.13.0-25.29-gener
[Kernel-packages] [Bug 1744935] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1744935/+attachment/5041756/+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/1744935 Title: [i915] Display Corruption Status in linux package in Ubuntu: Confirmed Bug description: Sometime during a regular package update of Ubuntu of 17.10 I started having screen corruption issues within GL apps (e.g. WebGL on google maps) on both the external screens as well as the laptops (Thinkpad T460p), but then spread further to the regular desktop. I updated to Ubuntu 18.04 to try to resolve the issue and then even updated the kernel to the Linux-4.15-rc8 (4.15.0-994-generic) but the issues remain on both Wayland and Xorg. It seems related to the 3D acceleration since the corruption only starts with gdm, not on the framebuffer before. The issue happens on every boot. The i915 module is loaded with its default parameters, the nvidia card is deactivated with switcheroo and the proprietary driver has never been installed. The corruption is best described as flashing distortions associated with timers and/or input events. Sometimes a whole triangular section of up to a quarter of the double-screen setup is streched and/or discolored or blacked out. Sometimes black squares (a few pixels) splatter the whole screen for a few frames until a damaged region is updated. It looks like some kind of shader issue. Sometimes the screen gets stuck for a few seconds (presumably the hang from the crashdump attached), so it's possible that there are multiple issues but I can't discern them. dmesg reports: ` [31026.161705] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [31731.589497] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [32477.060892] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [35533.800723] [drm] GPU HANG: ecode 9:0:0x85db, in gnome-shell [14269], reason: Hang on rcs0, action: reset [35533.800725] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace. [35533.800725] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel [35533.800725] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue. [35533.800726] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it. [35533.800726] [drm] GPU crash dump saved to /sys/class/drm/card1/error [35533.800768] i915 :00:02.0: Resetting rcs0 after gpu hang [36101.847545] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [41209.093879] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [43073.711135] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [43339.548927] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [43886.208705] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [44617.864814] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [45925.860575] i915 :00:02.0: Resetting rcs0 after gpu hang ` The memory size in UEFI is already set to the maximum of 512Mb. --- ApportVersion: 2.20.8-0ubuntu6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1396 F pulseaudio abr1860 F pulseaudio DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=c566c6bc-3708-4170-8812-823802420564 InstallationDate: Installed on 2017-05-30 (238 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) MachineType: LENOVO 20FW003PMZ Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-25-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.1
[Kernel-packages] [Bug 1733281] Re: ubuntu/xr-usb-serial didn't get built in zesty and artful
** Also affects: linux (Ubuntu Artful) Importance: Undecided Status: New ** Also affects: linux-azure-edge (Ubuntu Artful) Importance: Undecided Status: New ** Changed in: linux-azure-edge (Ubuntu Artful) Status: New => 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/1733281 Title: ubuntu/xr-usb-serial didn't get built in zesty and artful Status in linux package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Committed Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Artful: New Status in linux-azure-edge source package in Artful: Invalid Bug description: The ubuntu/xr-usb-serial is expected to be built for i386 and x86_64, and in ubuntu/Makefile it says: ifneq ($(filter $(ARCH), i386 x86_64),) obj-y += xr-usb-serial/ endif Since ARCH is x86 for both i386 and x86_64, this condition will never be true thus the module will never get a chance to be built. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1733281/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1744935] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1744935 Title: [i915] Display Corruption Status in linux package in Ubuntu: Confirmed Bug description: Sometime during a regular package update of Ubuntu of 17.10 I started having screen corruption issues within GL apps (e.g. WebGL on google maps) on both the external screens as well as the laptops (Thinkpad T460p), but then spread further to the regular desktop. I updated to Ubuntu 18.04 to try to resolve the issue and then even updated the kernel to the Linux-4.15-rc8 (4.15.0-994-generic) but the issues remain on both Wayland and Xorg. It seems related to the 3D acceleration since the corruption only starts with gdm, not on the framebuffer before. The issue happens on every boot. The i915 module is loaded with its default parameters, the nvidia card is deactivated with switcheroo and the proprietary driver has never been installed. The corruption is best described as flashing distortions associated with timers and/or input events. Sometimes a whole triangular section of up to a quarter of the double-screen setup is streched and/or discolored or blacked out. Sometimes black squares (a few pixels) splatter the whole screen for a few frames until a damaged region is updated. It looks like some kind of shader issue. Sometimes the screen gets stuck for a few seconds (presumably the hang from the crashdump attached), so it's possible that there are multiple issues but I can't discern them. dmesg reports: ` [31026.161705] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [31731.589497] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [32477.060892] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [35533.800723] [drm] GPU HANG: ecode 9:0:0x85db, in gnome-shell [14269], reason: Hang on rcs0, action: reset [35533.800725] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace. [35533.800725] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel [35533.800725] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue. [35533.800726] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it. [35533.800726] [drm] GPU crash dump saved to /sys/class/drm/card1/error [35533.800768] i915 :00:02.0: Resetting rcs0 after gpu hang [36101.847545] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [41209.093879] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [43073.711135] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [43339.548927] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [43886.208705] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [44617.864814] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [45925.860575] i915 :00:02.0: Resetting rcs0 after gpu hang ` The memory size in UEFI is already set to the maximum of 512Mb. --- ApportVersion: 2.20.8-0ubuntu6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1396 F pulseaudio abr1860 F pulseaudio DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=c566c6bc-3708-4170-8812-823802420564 InstallationDate: Installed on 2017-05-30 (238 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) MachineType: LENOVO 20FW003PMZ Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-25-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13 PulseList: Error: command ['pacmd', 'list'
[Kernel-packages] [Bug 1581594] Re: constantly shows wrong temperature (99°C )
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: libatasmart (Ubuntu Xenial) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to libatasmart in Ubuntu. https://bugs.launchpad.net/bugs/1581594 Title: constantly shows wrong temperature (99°C ) Status in libatasmart: Unknown Status in libatasmart package in Ubuntu: In Progress Status in libatasmart source package in Trusty: Confirmed Status in libatasmart source package in Xenial: Confirmed Status in libatasmart source package in Yakkety: Confirmed Bug description: Hello, here's my system info ~$ lsb_release -rd Description: Ubuntu 16.04 LTS Release: 16.04 ~$ apt-cache policy udisks2 udisks2: Installed: 2.1.7-1ubuntu1 Candidate: 2.1.7-1ubuntu1 Version table: *** 2.1.7-1ubuntu1 500 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status Here's the problem: udisks2 constantly shows that my ssd temperature is 99°C (210°F), but in reality it's 30°C ~$ sudo smartctl -A /dev/sda smartctl 6.5 2016-01-24 r4214 [x86_64-linux-4.4.0-22-generic] (local build) Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org === START OF READ SMART DATA SECTION === SMART Attributes Data Structure revision number: 16 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000b 100 100 050Pre-fail Always - 0 9 Power_On_Hours 0x0012 100 100 000Old_age Always - 24 12 Power_Cycle_Count 0x0012 100 100 000Old_age Always - 51 168 Unknown_Attribute 0x0012 100 100 000Old_age Always - 0 170 Unknown_Attribute 0x0003 100 100 010Pre-fail Always - 231 173 Unknown_Attribute 0x0012 100 100 000Old_age Always - 65539 192 Power-Off_Retract_Count 0x0012 100 100 000Old_age Always - 23 194 Temperature_Celsius 0x0023 070 070 030Pre-fail Always - 30 (Min/Max 30/30) 218 Unknown_Attribute 0x000b 100 100 050Pre-fail Always - 0 231 Temperature_Celsius 0x0013 100 100 000Pre-fail Always - 99 241 Total_LBAs_Written 0x0012 100 100 000Old_age Always - 337 in the GUI app ("Disks") it shows the wrong temperature too. hddtemp works well though: ~$ sudo hddtemp /dev/sda /dev/sda: PNY EU SSD CS1311 240GB: 30°C To manage notifications about this bug go to: https://bugs.launchpad.net/libatasmart/+bug/1581594/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1581594] Re: constantly shows wrong temperature (99°C )
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: libatasmart (Ubuntu Yakkety) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to libatasmart in Ubuntu. https://bugs.launchpad.net/bugs/1581594 Title: constantly shows wrong temperature (99°C ) Status in libatasmart: Unknown Status in libatasmart package in Ubuntu: In Progress Status in libatasmart source package in Trusty: Confirmed Status in libatasmart source package in Xenial: Confirmed Status in libatasmart source package in Yakkety: Confirmed Bug description: Hello, here's my system info ~$ lsb_release -rd Description: Ubuntu 16.04 LTS Release: 16.04 ~$ apt-cache policy udisks2 udisks2: Installed: 2.1.7-1ubuntu1 Candidate: 2.1.7-1ubuntu1 Version table: *** 2.1.7-1ubuntu1 500 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status Here's the problem: udisks2 constantly shows that my ssd temperature is 99°C (210°F), but in reality it's 30°C ~$ sudo smartctl -A /dev/sda smartctl 6.5 2016-01-24 r4214 [x86_64-linux-4.4.0-22-generic] (local build) Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org === START OF READ SMART DATA SECTION === SMART Attributes Data Structure revision number: 16 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000b 100 100 050Pre-fail Always - 0 9 Power_On_Hours 0x0012 100 100 000Old_age Always - 24 12 Power_Cycle_Count 0x0012 100 100 000Old_age Always - 51 168 Unknown_Attribute 0x0012 100 100 000Old_age Always - 0 170 Unknown_Attribute 0x0003 100 100 010Pre-fail Always - 231 173 Unknown_Attribute 0x0012 100 100 000Old_age Always - 65539 192 Power-Off_Retract_Count 0x0012 100 100 000Old_age Always - 23 194 Temperature_Celsius 0x0023 070 070 030Pre-fail Always - 30 (Min/Max 30/30) 218 Unknown_Attribute 0x000b 100 100 050Pre-fail Always - 0 231 Temperature_Celsius 0x0013 100 100 000Pre-fail Always - 99 241 Total_LBAs_Written 0x0012 100 100 000Old_age Always - 337 in the GUI app ("Disks") it shows the wrong temperature too. hddtemp works well though: ~$ sudo hddtemp /dev/sda /dev/sda: PNY EU SSD CS1311 240GB: 30°C To manage notifications about this bug go to: https://bugs.launchpad.net/libatasmart/+bug/1581594/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1581594] Re: constantly shows wrong temperature (99°C )
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: libatasmart (Ubuntu Trusty) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to libatasmart in Ubuntu. https://bugs.launchpad.net/bugs/1581594 Title: constantly shows wrong temperature (99°C ) Status in libatasmart: Unknown Status in libatasmart package in Ubuntu: In Progress Status in libatasmart source package in Trusty: Confirmed Status in libatasmart source package in Xenial: Confirmed Status in libatasmart source package in Yakkety: Confirmed Bug description: Hello, here's my system info ~$ lsb_release -rd Description: Ubuntu 16.04 LTS Release: 16.04 ~$ apt-cache policy udisks2 udisks2: Installed: 2.1.7-1ubuntu1 Candidate: 2.1.7-1ubuntu1 Version table: *** 2.1.7-1ubuntu1 500 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status Here's the problem: udisks2 constantly shows that my ssd temperature is 99°C (210°F), but in reality it's 30°C ~$ sudo smartctl -A /dev/sda smartctl 6.5 2016-01-24 r4214 [x86_64-linux-4.4.0-22-generic] (local build) Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org === START OF READ SMART DATA SECTION === SMART Attributes Data Structure revision number: 16 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000b 100 100 050Pre-fail Always - 0 9 Power_On_Hours 0x0012 100 100 000Old_age Always - 24 12 Power_Cycle_Count 0x0012 100 100 000Old_age Always - 51 168 Unknown_Attribute 0x0012 100 100 000Old_age Always - 0 170 Unknown_Attribute 0x0003 100 100 010Pre-fail Always - 231 173 Unknown_Attribute 0x0012 100 100 000Old_age Always - 65539 192 Power-Off_Retract_Count 0x0012 100 100 000Old_age Always - 23 194 Temperature_Celsius 0x0023 070 070 030Pre-fail Always - 30 (Min/Max 30/30) 218 Unknown_Attribute 0x000b 100 100 050Pre-fail Always - 0 231 Temperature_Celsius 0x0013 100 100 000Pre-fail Always - 99 241 Total_LBAs_Written 0x0012 100 100 000Old_age Always - 337 in the GUI app ("Disks") it shows the wrong temperature too. hddtemp works well though: ~$ sudo hddtemp /dev/sda /dev/sda: PNY EU SSD CS1311 240GB: 30°C To manage notifications about this bug go to: https://bugs.launchpad.net/libatasmart/+bug/1581594/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1724120] Comment bridged from LTC Bugzilla
--- Comment From dieg...@br.ibm.com 2018-01-23 09:23 EDT--- Hi Joseph, I was able to reproduce the problem on HWE Kernal (XENIAL): -- System root@tuletapio2-lp3:~# uname -a Linux tuletapio2-lp3 4.13.13 #1 SMP Tue Jan 23 07:41:39 CST 2018 ppc64le ppc64le ppc64le GNU/Linux root@tuletapio2-lp3:~# cat /proc/meminfo HugePages_Total: 2 HugePages_Free:2 HugePages_Rsvd:0 HugePages_Surp:0 Hugepagesize: 16777216 kB root@tuletapio2-lp3:~# cat /proc/cmdline BOOT_IMAGE=/boot/vmlinux-4.13.13 root=UUID=728bebfe-83ba-410d-917b-b552edbbb0a3 ro quiet splash default_hugepagesz=16G hugepagesz=16G hugepages=2 -- DUMP Unable to handle kernel paging request for data at address 0x5deadbeef108 Faulting instruction address: 0xc02cf374 Oops: Kernel access of bad area, sig: 11 [#1] SMP NR_CPUS=2048 NUMA pSeries Modules linked in: CPU: 7 PID: 3769 Comm: mem-on-off-test Not tainted 4.13.13 #1 task: c007d940 task.stack: c007d948 NIP: c02cf374 LR: c02cf298 CTR: c0134ef0 REGS: c007d94837d0 TRAP: 0380 Not tainted (4.13.13) MSR: 8280b033 CR: 44422484 XER: CFAR: c02cf308 SOFTE: 1 GPR00: c02cf28c c007d9483a50 c0e6ff00 c0fbc580 GPR04: f400 5deadbeef100 5deadbeef200 0002 GPR08: 5deadbeef000 0001 c0fbc580 c007fb000628 GPR12: 2200 cfd02a00 1000 f400 GPR16: 0002 c0ea3b00 1000 GPR20: db4f 0001 c00fffd44600 c007d9483b60 GPR24: 0010 c0f0dad8 c0eb2dd0 0001 GPR28: c0fc4580 c0fd4580 f400 NIP [c02cf374] dissolve_free_huge_page+0x124/0x230 LR [c02cf298] dissolve_free_huge_page+0x48/0x230 Call Trace: [c007d9483a50] [c02cf28c] dissolve_free_huge_page+0x3c/0x230 (unreliable) [c007d9483a90] [c02cf548] dissolve_free_huge_pages+0xc8/0x150 [c007d9483ae0] [c02ee1c8] __offline_pages.constprop.5+0x398/0xa90 [c007d9483c30] [c0645870] memory_subsys_offline+0x60/0xf0 [c007d9483c60] [c0623434] device_offline+0xf4/0x130 [c007d9483ca0] [c0645718] store_mem_state+0x178/0x190 [c007d9483ce0] [c061ea34] dev_attr_store+0x34/0x60 [c007d9483d00] [c03bdd10] sysfs_kf_write+0x60/0xa0 [c007d9483d20] [c03bcaac] kernfs_fop_write+0x16c/0x240 [c007d9483d70] [c0314cf4] __vfs_write+0x34/0x70 [c007d9483d90] [c031673c] vfs_write+0xcc/0x230 [c007d9483de0] [c0318410] SyS_write+0x60/0x110 [c007d9483e30] [c000b860] system_call+0x58/0x6c Instruction dump: e90a0030 88ff0007 7fa94000 419e0120 3d005dea e8df0028 e8bf0020 7fe4fb78 6108dbee 7d435378 790807c6 6508f000 f8a6 7d094378 61080100 ---[ end trace 23e3dda3fe0a58bd ]-- -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1724120 Title: Ubuntu 16.04.3 - call traces occurs when memory-hotplug test is run with 16Gb hugepages configured Status in The Ubuntu-power-systems project: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Artful: In Progress Bug description: Issue: Call traces occurs when memory-hotplug script is run with 16Gb hugepages configured. Environment: ppc64le PowerVM Lpar root@ltctuleta-lp1:~# uname -r 4.4.0-34-generic root@ltctuleta-lp1:~# cat /proc/meminfo | grep -i huge AnonHugePages: 0 kB HugePages_Total: 2 HugePages_Free:2 HugePages_Rsvd:0 HugePages_Surp:0 Hugepagesize: 16777216 kB root@ltctuleta-lp1:~# free -h totalusedfree shared buff/cache available Mem:85G 32G 52G 16M193M 52G Swap: 43G 0B 43G Steps to reproduce: 1 - Download kernel source and enter to the directory- tools/testing/selftests/memory-hotplug/ 2 - Run mem-on-off-test.sh script in it. System gives call traces like: offline_memory_expect_success 639: unexpected fail online-offline 668 [ 57.552964] Unable to handle kernel paging request for data at address 0x0028 [ 57.552977] Faulting instruction address: 0xc029bc04 [ 57.552987] Oops: Kernel access of bad area, sig: 11 [#1] [ 57.552992] SMP NR_CPUS=2048 NUMA pSeries [ 57.553002] Modules linked in: btrfs xor raid6_pq pseries_rng sunrpc autofs4 ses enclosure nouveau bnx2x i2c_algo_bit ttm drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops drm vxlan ip6_udp_tunnel ipr udp_tunnel rtc_generic mdio libcrc32c [ 57.553050] CPU: 44 PID: 6518 Comm: mem-on-off-test Not tainted 4.4.0-34-generic #53-Ubuntu
[Kernel-packages] [Bug 1743027] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: 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/1743027 Title: error loading realtime clock since upgrading to 17.10 Status in linux package in Ubuntu: Confirmed Bug description: (originally asked over at askubuntu.com, but is still unresolved: https://askubuntu.com/questions/971349/problem-with-real-time-clock- since-upgrading-to-ubuntu-17-10) I recently upgraded from Ubuntu 17.04 to Ubuntu 17.10 using the software update process. The update completed without any errors, and Ubuntu 17.10 is now running without any major issues. However, I was running a script previously that uses rtcwake which has since stopped working. The script automatically hibernates my laptop after a set period of time in sleep mode, and was working perfectly in Ubuntu 17.04. In the process of troubleshooting, I discovered that the problem was with rtcwake which is complaining about /dev/rtc0 missing. Here is output from a sample rtcwake command: peter@haven:~$ rtcwake -m no -s 1300 rtcwake: assuming RTC uses UTC ... rtcwake: /dev/rtc0: unable to find device: No such file or directory I verified that in fact, that directory is missing. Since this was working prior to the upgrade, I have to assume that it was there previously, but I don't know for sure. In researching the error, I found some suggestions to get further information with timedatectl and hwclock, so here are the results from those commands as well. Output of timedatectl: peter@haven:~$ timedatectl Local time: Fri 2017-10-27 19:06:26 EDT Universal time: Fri 2017-10-27 23:06:26 UTC RTC time: n/a Time zone: America/New_York (EDT, -0400) Network time on: yes NTP synchronized: yes RTC in local TZ: no Output of hwclock --debug: peter@haven:~$ sudo hwclock --debug [sudo] password for peter: hwclock from util-linux 2.30.1 Trying to open: /dev/rtc0 Trying to open: /dev/rtc Trying to open: /dev/misc/rtc No usable clock interface found. hwclock: Cannot access the Hardware Clock via any known method. UPDATE When I boot with my old kernel, 4.10.0-37-generic the real-time clock works fine. I get the following RTC messages in dmesg when I boot the 4.13.0-16-generic kernel: peter@haven:~$ dmesg | grep -i rtc [0.089393] RTC time: 17:03:55, date: 11/01/17 [1.238784] rtc_cmos 00:01: RTC can wake from S4 [1.238794] rtc_cmos: probe of 00:01 failed with error -16 [1.295459] hctosys: unable to open rtc device (rtc0) UPDATE #2 Well, I was starting to believe that I had a hardware issue, since discovering I was unable to save changes to my BIOS and could not boot from USB. As it turns out, my laptop was bitten by this bug: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1734147 causing my BIOS to be locked in a read-only state. Once I resolved the BIOS issue, and fixed the USB boot problem, I did a live boot of Ubuntu 17.10. The issue with my real time clock still exists under this clean boot scenario, yet when I boot other distros, like Linux Mint 18.3 and the real time clock works fine. I feel this definitely has something to do with the Ubuntu install, perhaps even a kernel bug. UPDATE #3 More evidence to suggest this is a kernel bug: I live-booted a copy of Antergos Linux, which was using the Arch kernel 4.14.12-1-ARCH and it exhibited the same problem with the real time clock as Ubuntu 17.10. In addition, I confirmed that the Linux Mint version I booted earlier (see Update #2) was on the Ubuntu kernel 4.10.0-38-generic. So, I suspect that sometime between kernels 4.10 and 4.13 this bug was introduced. --- ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: peter 1832 F pulseaudio /dev/snd/controlC1: peter 1832 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 HibernationDevice: RESUME=UUID=a602efe1-467d-4ac4-806f-1b931c91cdad InstallationDate: Installed on 2017-04-05 (292 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: LENOVO 20354 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-25-generic.efi.signed root=UUID=fa5454aa-9072-475d-b515-acd51a6166cc ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13 RelatedPackageVersions: linux-restricted-modules-4.13.0-25-generic N/A linux-backports-modules-4.13.0-25-generic N/A linux-firmware
[Kernel-packages] [Bug 123920] Re: Bluetooth Logitech Dinovo Keyboard/Mouse don't work
Confirm. I have updated 17.04 -> 17.10 and this bug is still exist. Have to edit hid2hci.rules file as Daniel Beauyat suggest to get it work. Have this bug since I start using ubuntu 10.04. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/123920 Title: Bluetooth Logitech Dinovo Keyboard/Mouse don't work Status in Bluez Utilities: New Status in Bluez-utils: New Status in Linux Mint: Invalid Status in Unity: Invalid Status in bluez package in Ubuntu: Fix Released Status in linux package in Ubuntu: Invalid Status in linux-source-2.6.22 package in Ubuntu: Won't Fix Status in udev package in Ubuntu: Invalid Bug description: Testing Gutsy Gibbon Tribe 2 LiveCD and bluetooth keyboard and mouse will work until Nautilus starts. After Nautilus starts the keyboard and mouse are unresponsive and do not work. I tried reconnecting the keyboard and mouse by using the discovery buttons on both the Bluetooth Dongle and Input device. The problem still persists. Using Intel P4 2.8 Ghz Processor, 3 GB ddr400 ram, Intel D875PBZ motherboard. Logitech Dinovo media keyboard and mx1000 laser bluetooth mouse, with logitech mini bluetooth receiver. To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/123920/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1730152] Re: Internal microsd card reader does not work in Ubuntu 17.10
Please someone write the driver for this card reader. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1730152 Title: Internal microsd card reader does not work in Ubuntu 17.10 Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 17.10 x86_64 of Wayland-Session is running on a HP Envy 13-ad1xx notbook with a internal microsd card reader. The system gives no response when inserting different micro sd cards, which work fine on Windows 10. I report this bug in hope that the upstream may notice and make some change on the suited driver or kernel module. I would provide more information under further direction. According to `lspci` output, the model name is 'Alcor Micro Device 6625'. `udevadm monitor --env` gives no related events when inserting or pulling out the microsd card, in which only thermal_zone changes are recorded. No related events are recoded in /var/log/kern.log either. With sd card being inserted, `sudo fdisk -l` and `sudo blkid` gives no related information. The outputs are all about partitions on the local disk. No sdhc or mmc device is found in /dev/ either. The only implication now is the system notice the existence of the card reader, in terms of `lspci` outputs, the '01:00.0 Unassigned class [ff00]: Alcor Micro Device 6625', even when a sd card is inserted: 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/pcmC0D0p: limorg 1514 F...m pulseaudio /dev/snd/controlC0: limorg 1514 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Nov 5 10:29:26 2017 HibernationDevice: RESUME=UUID=8f370e7c-280d-4864-b687-a2c81ce87247 InstallationDate: Installed on 2017-10-22 (13 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bus 001 Device 003: ID 0bda:5620 Realtek Semiconductor Corp. Bus 001 Device 002: ID 046d:c52f Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP ENVY Laptop 13-ad1xx ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=UUID=67e321d1-4810-4157-8c29-09c51ea7 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-29 (6 days ago) dmi.bios.date: 07/26/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.12 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 83A8 dmi.board.vendor: HP dmi.board.version: KBC Version 39.32 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.12:bd07/26/2017:svnHP:pnHPENVYLaptop13-ad1xx:pvrType1ProductConfigId:rvnHP:rn83A8:rvrKBCVersion39.32:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Envy dmi.product.name: HP ENVY Laptop 13-ad1xx dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1730152/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1742302] Re: Kernel 4.13.0-25 broke nvidia driver
I spoke too soon! The recent 4.13.0-31 kernel appears to have fixed the problem for me, at least. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1742302 Title: Kernel 4.13.0-25 broke nvidia driver Status in linux package in Ubuntu: Confirmed Bug description: After updating to linux-image-4.13.0-25-generic the binary nvidia driver 387.22 cannot be built. As a result the system does not boot into the desktop environment (in my case, KDE). I've attached the driver build log. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-25-generic 4.13.0-25.29 ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13 Uname: Linux 4.13.0-21-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lastique 3049 F pulseaudio /dev/snd/controlC2: lastique 3049 F pulseaudio /dev/snd/controlC3: lastique 3049 F pulseaudio /dev/snd/controlC1: lastique 3049 F pulseaudio CurrentDesktop: KDE Date: Wed Jan 10 02:00:46 2018 InstallationDate: Installed on 2015-05-01 (984 days ago) InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: System manufacturer System Product Name ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-21-generic root=UUID=a03f1835-52f9-4409-9da7-fe45770637ae ro quiet splash nomdmonddf nomdmonisw RelatedPackageVersions: linux-restricted-modules-4.13.0-21-generic N/A linux-backports-modules-4.13.0-21-generic N/A linux-firmware 1.169.1 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to artful on 2017-11-03 (67 days ago) dmi.bios.date: 11/09/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3603 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8Z68-V PRO dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3603:bd11/09/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8Z68-VPRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1742302/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1569925] Re: Shutdown hang on 16.04 with iscsi targets
** Changed in: linux (Ubuntu Bionic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1569925 Title: Shutdown hang on 16.04 with iscsi targets Status in linux package in Ubuntu: Fix Committed Status in open-iscsi package in Ubuntu: Opinion Status in linux source package in Trusty: In Progress Status in open-iscsi source package in Trusty: Opinion Status in linux source package in Xenial: In Progress Status in open-iscsi source package in Xenial: Opinion Status in linux source package in Artful: In Progress Status in open-iscsi source package in Artful: Opinion Status in linux source package in Bionic: Fix Committed Status in open-iscsi source package in Bionic: Opinion Bug description: [Impact] * open-iscsi users might face hangs during OS shutdown. * hangs can be caused by manual iscsi configuration/setup. * hangs can also be caused by bad systemd unit ordering. * if transport layer interface vanishes before lun is disconnected, then the hang will happen. * check comment #89 for the fix decision. [Test Case] * a simple way of reproducing the kernel hang is to disable the open-iscsi logouts. this simulates a situation when a service has shutdown the network interface, used by the transport layer, before proper iscsi logout was done. $ log into all iscsi luns $ systemctl edit --full open-iscsi.service ... #ExecStop=/lib/open-iscsi/logout-all.sh ... $ sudo reboot # this will make server to hang forever # on shutdown [Regression Potential] * the regression is low because the change acts on the iscsi transport layer code ONLY when the server is in shutdown state. * any error in logic would only appear during shutdown and would not cause any harm to data. [Other Info] * ORIGINAL BUG DESCRIPTION I have 4 servers running the latest 16.04 updates from the development branch (as of right now). Each server is connected to NetApp storage using iscsi software initiator. There are a total of 56 volumes spread across two NetApp arrays. Each volume has 4 paths available to it which are being managed by device mapper. While logged into the iscsi sessions all I have to do is reboot the server and I get a hang. I see a message that says: "Reached target Shutdown" followed by "systemd-shutdown[1]: Failed to finalize DM devices, ignoring" and then I see 8 lines that say: "connection1:0: ping timeout of 5 secs expired, recv timeout 5, last rx 4311815***, last ping 43118164**, now 4311817***" "connection2:0: ping timeout of 5 secs expired, recv timeout 5, last rx 4311815***, last ping 43118164**, now 4311817***" "connection3:0: ping timeout of 5 secs expired, recv timeout 5, last rx 4311815***, last ping 43118164**, now 4311817***" "connection4:0: ping timeout of 5 secs expired, recv timeout 5, last rx 4311815***, last ping 43118164**, now 4311817***" "connection5:0: ping timeout of 5 secs expired, recv timeout 5, last rx 4311815***, last ping 43118164**, now 4311817***" "connection6:0: ping timeout of 5 secs expired, recv timeout 5, last rx 4311815***, last ping 43118164**, now 4311817***" "connection7:0: ping timeout of 5 secs expired, recv timeout 5, last rx 4311815***, last ping 43118164**, now 4311817***" "connection8:0: ping timeout of 5 secs expired, recv timeout 5, last rx 4311815***, last ping 43118164**, now 4311817***" NOTE: the actual values of the *'s differ for each line above. This seems like a bug somewhere but I am unaware of any additional logging that I could turn on to pinpoint the problem. Note I also have similar setups that are not doing iscsi and they don't have this problem. Here is a screenshot of what I see on the shell when I try to reboot: (https://launchpadlibrarian.net/291303059/Screenshot.jpg) This is being tracked in NetApp bug tracker CQ number 860251. If I log out of all iscsi sessions before rebooting then I do not experience the hang: iscsiadm -m node -U all We are wondering if this could be some kind of shutdown ordering problem. Like the network devices have already disappeared and then iscsi tries to perform some operation (hence the ping timeouts). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1569925/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1744979] [NEW] grub_efi_secure_boot signal at the beginning of the boot process
Public bug reported: The previous kernel (4.4.0-109) was running without any problems, without triggering an error. After today's kernel update, the machine can not be started unless you select "run" the selected kernel from the advanced settings menu item. The first message always: grub_efi_secure_boot Ubuntu 4.4.0-112.135-generic 4.4.98 LSB Version: core-9.20160110ubuntu0.2-ia32:core-9.20160110ubuntu0.2-noarch:security-9.20160110ubuntu0.2-ia32:security-9.20160110ubuntu0.2-noarch Distributor ID: Ubuntu Description:Ubuntu 16.04.3 LTS Release:16.04 Codename: xenial Intel® Core™ i5-3330 CPU @ 3.00GHz × 4 GeForce GT 630/PCIe/SSE2 system 32 bit Please help... I chose 16.04 LTS because I wanted to have a long, calm and safe use ... ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Attachment added: "20180123_143559.jpg" https://bugs.launchpad.net/bugs/1744979/+attachment/5041851/+files/20180123_143559.jpg -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1744979 Title: grub_efi_secure_boot signal at the beginning of the boot process Status in linux package in Ubuntu: New Bug description: The previous kernel (4.4.0-109) was running without any problems, without triggering an error. After today's kernel update, the machine can not be started unless you select "run" the selected kernel from the advanced settings menu item. The first message always: grub_efi_secure_boot Ubuntu 4.4.0-112.135-generic 4.4.98 LSB Version: core-9.20160110ubuntu0.2-ia32:core-9.20160110ubuntu0.2-noarch:security-9.20160110ubuntu0.2-ia32:security-9.20160110ubuntu0.2-noarch Distributor ID: Ubuntu Description: Ubuntu 16.04.3 LTS Release: 16.04 Codename: xenial Intel® Core™ i5-3330 CPU @ 3.00GHz × 4 GeForce GT 630/PCIe/SSE2 system 32 bit Please help... I chose 16.04 LTS because I wanted to have a long, calm and safe use ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1744979/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1744981] [NEW] linux: 4.14.0-17.20 -proposed tracker
Public bug reported: This bug is for tracking the 4.14.0-17.20 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 kernel-phase:Packaging kernel-phase-changed:Tuesday, 23. January 2018 17:30 UTC -- swm properties -- phase: Packaging ** Affects: kernel-development-workflow Importance: Medium Status: In Progress ** Affects: kernel-development-workflow/automated-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-development-workflow/prepare-package Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: Confirmed ** Affects: kernel-development-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-development-workflow/prepare-package-signed Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-development-workflow/promote-to-proposed Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-development-workflow/promote-to-release Importance: Medium Assignee: Ubuntu Package Archive Administrators (ubuntu-archive) Status: New ** Affects: kernel-development-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux (Ubuntu) Importance: Medium Status: Confirmed ** Affects: linux (Ubuntu Bionic) Importance: Medium Status: Confirmed ** Tags: bionic kernel-release-tracking-bug kernel-release-tracking-bug-live ** Tags added: kernel-release-tracking-bug ** Tags added: kernel-release-tracking-bug-live ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Tags added: bionic ** Changed in: linux (Ubuntu Bionic) Status: New => Confirmed ** Also affects: kernel-development-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-development-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-development-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-development-workflow/prepare-package-signed Importance: Undecided Status: New ** Also affects: kernel-development-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-development-workflow/promote-to-release Importance: Undecided Status: New ** Also affects: kernel-development-workflow/regression-testing Importance: Undecided Status: New ** Changed in: kernel-development-workflow Status: New => In Progress ** Changed in: kernel-development-workflow Importance: Undecided => Medium ** Changed in: kernel-development-workflow/automated-testing Importance: Undecided => Medium ** Changed in: kernel-development-workflow/automated-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-development-workflow/prepare-package Importance: Undecided => Medium ** Changed in: kernel-development-workflow/prepare-package Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-development-workflow/prepare-package-meta Importance: Undecided => Medium ** Changed in: kernel-development-workflow/prepare-package-meta Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-development-workflow/prepare-package-signed Importance: Undecided => Medium ** Changed in: kernel-development-workflow/prepare-package-signed Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-development-workflow/promote-to-proposed Importance: Undecided => Medium ** Changed in: kernel-development-workflow/promote-to-proposed Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-development-workflow/promote-to-release Importance: Undecided => Medium ** Changed in: kernel-development-workflow/promote-to-release Assignee: (unassigned) => Ubuntu Package Archive Administrators (ubuntu-archive) ** Changed in: kernel-development-workflow/regression-testing Importance: Undecided => Medium ** Changed in: kernel-development-workflow/regression-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** 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.ne
[Kernel-packages] [Bug 1742302] Re: Kernel 4.13.0-25 broke nvidia driver
I know it might sound stupid, but how do I get a terminal session as I am not able to log in under X11 at all when this issue occurs. It boots straight away into bios. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1742302 Title: Kernel 4.13.0-25 broke nvidia driver Status in linux package in Ubuntu: Confirmed Bug description: After updating to linux-image-4.13.0-25-generic the binary nvidia driver 387.22 cannot be built. As a result the system does not boot into the desktop environment (in my case, KDE). I've attached the driver build log. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-25-generic 4.13.0-25.29 ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13 Uname: Linux 4.13.0-21-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lastique 3049 F pulseaudio /dev/snd/controlC2: lastique 3049 F pulseaudio /dev/snd/controlC3: lastique 3049 F pulseaudio /dev/snd/controlC1: lastique 3049 F pulseaudio CurrentDesktop: KDE Date: Wed Jan 10 02:00:46 2018 InstallationDate: Installed on 2015-05-01 (984 days ago) InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: System manufacturer System Product Name ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-21-generic root=UUID=a03f1835-52f9-4409-9da7-fe45770637ae ro quiet splash nomdmonddf nomdmonisw RelatedPackageVersions: linux-restricted-modules-4.13.0-21-generic N/A linux-backports-modules-4.13.0-21-generic N/A linux-firmware 1.169.1 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to artful on 2017-11-03 (67 days ago) dmi.bios.date: 11/09/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3603 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8Z68-V PRO dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3603:bd11/09/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8Z68-VPRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1742302/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1741501] Re: linux: 4.14.0-15.18 -proposed tracker
*** This bug is a duplicate of bug 1744981 *** https://bugs.launchpad.net/bugs/1744981 ** This bug is no longer a duplicate of bug 1741920 linux: 4.14.0-16.19 -proposed tracker ** This bug has been marked a duplicate of bug 1744981 linux: 4.14.0-17.20 -proposed tracker -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1741501 Title: linux: 4.14.0-15.18 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow automated-testing series: New Status in Kernel Development Workflow prepare-package series: Fix Released Status in Kernel Development Workflow prepare-package-meta series: Fix Released Status in Kernel Development Workflow prepare-package-signed series: Confirmed Status in Kernel Development Workflow promote-to-proposed series: Fix Committed Status in Kernel Development Workflow promote-to-release series: New Status in Kernel Development Workflow regression-testing series: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Bug description: This bug is for tracking the 4.14.0-15.18 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 -- phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1741501/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1743279] Re: QCA6174 stops working on newer kernels after second group rekeying
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-firmware (Ubuntu Artful) Status: New => Confirmed -- 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/1743279 Title: QCA6174 stops working on newer kernels after second group rekeying Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Xenial: Fix Committed Status in linux-firmware source package in Artful: Confirmed Bug description: After upgrading to the 4.13 kernel on Ubuntu 16.04.3, I've noticed my WiFi would stop working after every 20 minutes or so. The problem initially seems related to some DNS services crashing because of what happend in browsers and other software that usually rely on DNS but I've noticed I couldn't ping my router and other local devices for which I knew the IP addresses. The connection is still presented as being connected, but it just doesn't work. After googling a lot, I came across this question on askubuntu.com https://askubuntu.com/questions/967355/wifi-unstable- after-17-10-update Which led me to this bug report on Debian's bug tracker: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=879184 Which led me to this bug in upstream: http://lists.infradead.org/pipermail/ath10k/2017-September/010088.html I've tested the proposed fixes myself and I can confirm they work. What causes the WiFi to stop working is a bug related to the group rekeying routines. It seems it only happens in >4.12 kernels, hence why I've only had problems after 4.13 was pushed as the current rolling HWE kernel for 16.04.3. kvalo made the fix available in version WLAN.RM.4.4.1-00051-QCARMSWP-1 of the firmware-6.bin file, which is the current one present in upstream. Updating the firmware-6.bin (and board-2.bin, optionally) to any version equal or later than that fixes the issue completely. - SRU Justification: [Impact] Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter, available in numerous laptops, including ones that ship with Ubuntu 16.04 pre-installed, silently stops working after the second group rekeying, which is usually few minutes after the user has connected to a WiFi network. The connection status remains unchanged but there's no connectivity at all. This effectively disconnects the user without notifying it of what's occurred. Additionally, this happens for the only HWE kernel that's been patched against the recent Meltdown vulnerability, leaving the user without the option of using a recent kernel and a secure kernel at the same time. [Test Case] After applying the required firmwares, check if the connectivity is unaffected after the second group rekeying, which can be checked with $ cat /var/log/syslog | grep wpa_.*rekeying [How to fix it] Update the firmware-6.bin file to version WLAN.RM.4.4.1-00051-QCARMSWP-1 or later. [Regression Potential] The new firmware overwrites the old one, but since it's been in upstream since October 2017, it should be good. - Description: Ubuntu 16.04.3 LTS Release: 16.04 linux-firmware: Instalado: 1.157.14 Candidato: 1.157.14 Tabela de versão: *** 1.157.14 500 500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu xenial-updates/main i386 Packages 500 http://archive.ubuntu.com/ubuntu xenial-security/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu xenial-security/main i386 Packages 100 /var/lib/dpkg/status 1.157 500 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu xenial/main i386 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1743279/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1741920] Re: linux: 4.14.0-16.19 -proposed tracker
*** This bug is a duplicate of bug 1744981 *** https://bugs.launchpad.net/bugs/1744981 ** This bug has been marked a duplicate of bug 1744981 linux: 4.14.0-17.20 -proposed tracker -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1741920 Title: linux: 4.14.0-16.19 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow automated-testing series: Incomplete Status in Kernel Development Workflow prepare-package series: Fix Released Status in Kernel Development Workflow prepare-package-meta series: Fix Released Status in Kernel Development Workflow prepare-package-signed series: Fix Released Status in Kernel Development Workflow promote-to-proposed series: Fix Committed Status in Kernel Development Workflow promote-to-release series: New Status in Kernel Development Workflow regression-testing series: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Bug description: This bug is for tracking the 4.14.0-16.19 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 -- phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1741920/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1738554] Re: linux: 4.14.0-12.14 -proposed tracker
*** This bug is a duplicate of bug 1744981 *** https://bugs.launchpad.net/bugs/1744981 ** This bug is no longer a duplicate of bug 1741920 linux: 4.14.0-16.19 -proposed tracker ** This bug has been marked a duplicate of bug 1744981 linux: 4.14.0-17.20 -proposed tracker -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1738554 Title: linux: 4.14.0-12.14 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow automated-testing series: New Status in Kernel Development Workflow prepare-package series: Confirmed Status in Kernel Development Workflow prepare-package-meta series: New Status in Kernel Development Workflow prepare-package-signed series: New Status in Kernel Development Workflow promote-to-proposed series: New Status in Kernel Development Workflow promote-to-release series: New Status in Kernel Development Workflow regression-testing series: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Bug description: This bug is for tracking the 4.14.0-12.14 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 kernel-phase-changed:Saturday, 16. December 2017 16:32 UTC kernel-phase:Packaging -- swm properties -- phase: Packaging To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1738554/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1741139] Re: linux: 4.14.0-14.17 -proposed tracker
*** This bug is a duplicate of bug 1744981 *** https://bugs.launchpad.net/bugs/1744981 ** This bug is no longer a duplicate of bug 1741920 linux: 4.14.0-16.19 -proposed tracker ** This bug has been marked a duplicate of bug 1744981 linux: 4.14.0-17.20 -proposed tracker -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1741139 Title: linux: 4.14.0-14.17 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow automated-testing series: New Status in Kernel Development Workflow prepare-package series: Fix Released Status in Kernel Development Workflow prepare-package-meta series: Fix Released Status in Kernel Development Workflow prepare-package-signed series: Confirmed Status in Kernel Development Workflow promote-to-proposed series: Fix Committed Status in Kernel Development Workflow promote-to-release series: New Status in Kernel Development Workflow regression-testing series: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Bug description: This bug is for tracking the 4.14.0-14.17 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 -- phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1741139/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1734728] Re: linux: 4.14.0-9.11 -proposed tracker
*** This bug is a duplicate of bug 1744981 *** https://bugs.launchpad.net/bugs/1744981 ** This bug is no longer a duplicate of bug 1741920 linux: 4.14.0-16.19 -proposed tracker ** This bug has been marked a duplicate of bug 1744981 linux: 4.14.0-17.20 -proposed tracker -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1734728 Title: linux: 4.14.0-9.11 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow automated-testing series: New Status in Kernel Development Workflow prepare-package series: Confirmed Status in Kernel Development Workflow prepare-package-meta series: New Status in Kernel Development Workflow prepare-package-signed series: New Status in Kernel Development Workflow promote-to-proposed series: New Status in Kernel Development Workflow promote-to-release series: New Status in Kernel Development Workflow regression-testing series: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Bug description: This bug is for tracking the 4.14.0-9.11 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 kernel-phase:Packaging kernel-phase-changed:Monday, 27. November 2017 18:00 UTC -- swm properties -- phase: Packaging To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1734728/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1736168] Re: linux: 4.14.0-11.13 -proposed tracker
*** This bug is a duplicate of bug 1744981 *** https://bugs.launchpad.net/bugs/1744981 ** This bug is no longer a duplicate of bug 1741920 linux: 4.14.0-16.19 -proposed tracker ** This bug has been marked a duplicate of bug 1744981 linux: 4.14.0-17.20 -proposed tracker -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1736168 Title: linux: 4.14.0-11.13 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow automated-testing series: Fix Released Status in Kernel Development Workflow prepare-package series: Fix Released Status in Kernel Development Workflow prepare-package-meta series: Fix Released Status in Kernel Development Workflow prepare-package-signed series: Fix Released Status in Kernel Development Workflow promote-to-proposed series: Fix Released Status in Kernel Development Workflow promote-to-release series: New Status in Kernel Development Workflow regression-testing series: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Bug description: This bug is for tracking the 4.14.0-11.13 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 -- 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-development-workflow/+bug/1736168/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1738848] Re: linux: 4.14.0-13.15 -proposed tracker
*** This bug is a duplicate of bug 1744981 *** https://bugs.launchpad.net/bugs/1744981 ** This bug is no longer a duplicate of bug 1741920 linux: 4.14.0-16.19 -proposed tracker ** This bug has been marked a duplicate of bug 1744981 linux: 4.14.0-17.20 -proposed tracker -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1738848 Title: linux: 4.14.0-13.15 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow automated-testing series: Incomplete Status in Kernel Development Workflow prepare-package series: Fix Released Status in Kernel Development Workflow prepare-package-meta series: Fix Released Status in Kernel Development Workflow prepare-package-signed series: Fix Released Status in Kernel Development Workflow promote-to-proposed series: Fix Released Status in Kernel Development Workflow promote-to-release series: New Status in Kernel Development Workflow regression-testing series: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Bug description: This bug is for tracking the 4.14.0-13.15 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 -- 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-development-workflow/+bug/1738848/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1734695] Re: linux: 4.14.0-8.10 -proposed tracker
*** This bug is a duplicate of bug 1744981 *** https://bugs.launchpad.net/bugs/1744981 ** This bug is no longer a duplicate of bug 1741920 linux: 4.14.0-16.19 -proposed tracker ** This bug has been marked a duplicate of bug 1744981 linux: 4.14.0-17.20 -proposed tracker -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1734695 Title: linux: 4.14.0-8.10 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow automated-testing series: New Status in Kernel Development Workflow prepare-package series: Confirmed Status in Kernel Development Workflow prepare-package-meta series: New Status in Kernel Development Workflow prepare-package-signed series: New Status in Kernel Development Workflow promote-to-proposed series: New Status in Kernel Development Workflow promote-to-release series: New Status in Kernel Development Workflow regression-testing series: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Bug description: This bug is for tracking the 4.14.0-8.10 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 kernel-phase:Packaging kernel-phase-changed:Monday, 27. November 2017 14:00 UTC -- swm properties -- phase: Packaging To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1734695/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1734901] Re: linux: 4.14.0-10.12 -proposed tracker
*** This bug is a duplicate of bug 1744981 *** https://bugs.launchpad.net/bugs/1744981 ** This bug is no longer a duplicate of bug 1741920 linux: 4.14.0-16.19 -proposed tracker ** This bug has been marked a duplicate of bug 1744981 linux: 4.14.0-17.20 -proposed tracker -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1734901 Title: linux: 4.14.0-10.12 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow automated-testing series: New Status in Kernel Development Workflow prepare-package series: Confirmed Status in Kernel Development Workflow prepare-package-meta series: New Status in Kernel Development Workflow prepare-package-signed series: New Status in Kernel Development Workflow promote-to-proposed series: New Status in Kernel Development Workflow promote-to-release series: New Status in Kernel Development Workflow regression-testing series: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Bug description: This bug is for tracking the 4.14.0-10.12 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 kernel-phase-changed:Tuesday, 28. November 2017 15:01 UTC kernel-phase:Packaging -- swm properties -- phase: Packaging To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1734901/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1743799] Re: "fwts uefirtmisc" causes reboot in recent kernels
A further update: This problem does NOT occur under Artful on the Dell PowerEdge T610 with the following kernel: $ uname -a Linux hogplum 4.13.0-30-generic #33-Ubuntu SMP Mon Jan 15 19:45:48 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux I have not yet tested with Xenial or with other kernel series on the PowerEdge T710. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1743799 Title: "fwts uefirtmisc" causes reboot in recent kernels Status in Provider for Plainbox - Checkbox: Invalid Status in linux package in Ubuntu: Triaged Bug description: In doing Meltdown regression testing, we found that one server, lucuma, a Dell PowerEdge T710, would spontaneously reboot when running the miscellanea/fwts_test under Ubuntu 14.04.5 with a 3.13.0-139-generic #188-Ubuntu kernel. This test has been dropped from our test list for 16.04, so it was not initially tested under more recent kernels. This server has been out of our testing queue for years, so it hasn't been tested since Ubuntu 10.04. Thus, we don't yet know if the problem is a regression or if it's existed for a long time. We need to do more testing to better isolate the issue; stay tuned for more information The system's entry on C3 is: https://certification.canonical.com/hardware/200910-4539/ The submission showing the error is: https://certification.canonical.com/hardware/200910-4539/submission/126589/ To manage notifications about this bug go to: https://bugs.launchpad.net/plainbox-provider-checkbox/+bug/1743799/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1744979] 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 1744979 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: 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/1744979 Title: grub_efi_secure_boot signal at the beginning of the boot process Status in linux package in Ubuntu: Incomplete Bug description: The previous kernel (4.4.0-109) was running without any problems, without triggering an error. After today's kernel update, the machine can not be started unless you select "run" the selected kernel from the advanced settings menu item. The first message always: grub_efi_secure_boot Ubuntu 4.4.0-112.135-generic 4.4.98 LSB Version: core-9.20160110ubuntu0.2-ia32:core-9.20160110ubuntu0.2-noarch:security-9.20160110ubuntu0.2-ia32:security-9.20160110ubuntu0.2-noarch Distributor ID: Ubuntu Description: Ubuntu 16.04.3 LTS Release: 16.04 Codename: xenial Intel® Core™ i5-3330 CPU @ 3.00GHz × 4 GeForce GT 630/PCIe/SSE2 system 32 bit Please help... I chose 16.04 LTS because I wanted to have a long, calm and safe use ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1744979/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1744981] Re: linux: 4.14.0-17.20 -proposed tracker
** Changed in: kernel-development-workflow/prepare-package Status: New => Confirmed ** Description changed: This bug is for tracking the 4.14.0-17.20 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 + + kernel-phase:Packaging + kernel-phase-changed:Tuesday, 23. January 2018 17:30 UTC ** Description changed: This bug is for tracking the 4.14.0-17.20 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 kernel-phase:Packaging kernel-phase-changed:Tuesday, 23. January 2018 17:30 UTC + + -- swm properties -- + phase: Packaging -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1744981 Title: linux: 4.14.0-17.20 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow automated-testing series: New Status in Kernel Development Workflow prepare-package series: Confirmed Status in Kernel Development Workflow prepare-package-meta series: New Status in Kernel Development Workflow prepare-package-signed series: New Status in Kernel Development Workflow promote-to-proposed series: New Status in Kernel Development Workflow promote-to-release series: New Status in Kernel Development Workflow regression-testing series: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Bug description: This bug is for tracking the 4.14.0-17.20 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 kernel-phase:Packaging kernel-phase-changed:Tuesday, 23. January 2018 17:30 UTC -- swm properties -- phase: Packaging To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1744981/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1734147] Re: corrupted BIOS due to Intel SPI bug in kernel
My laptop: Mediacom Smartbook 14 Ultra M-SB14UC is fixed with official fix provided in description of this bug report. Thank you <3 ** Description changed: An update to linux kernel on Ubuntu 17.10 that enabled the Intel SPI drivers results in a serial flash that is read only in Intel Broadwell and Haswell machines with serial flashes with SPI_NOR_HAS_LOCK set. Symptoms: * BIOS settings cannot be saved * USB Boot impossible * EFI entries read-only. --- Fix: The issue was fixed in kernel version 4.13.0-21 by configuring the kernel so it is not compiled with Intel SPI support. But previous affected machines still suffered from a broken BIOS. Repair: If you still can boot into Ubuntu, you can recover your BIOS with the following steps: 1. Boot into Ubuntu 2. Download http://people.canonical.com/~ypwong/lp1734147/linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+20170103+1_amd64.deb 3. Install the downloaded package: $ sudo dpkg -i linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+20170103+1_amd64.deb 4. Make sure the kernel is installed without any error. Once installed, reboot. 5. At grub, choose the newly installed kernel. You can choose the "recovery" mode. 6. Reboot and go to BIOS settings to confirm your BIOS has been recovered. 7. In case your BIOS is not recovered, reboot to the new kernel, then reboot *once again* to the new kernel, do not enter BIOS settings before the reboot. After the second reboot, check BIOS. 8. If your BIOS issue remains, download another kernel from http://people.canonical.com/~ypwong/lp1734147/linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+clear+debug_amd64.deb, and use dpkg to install it, then repeat steps 4 to 6. After your BIOS is fixed, the kernel packages you just installed are no longer needed, you can remove it by running 'sudo dpkg -r linux- image-4.15.0-041500rc6-generic'. The patch used to build the linux v4.15 kernel in step 8 can be found at https://goo.gl/xUKJFR. --- Test Case: Fix has been verified by our HWE team on affected hardware. Regression Potential: Minimal, it's unlikely anyone is actually doing anything which requires this driver. --- Affected Machines: Lenovo B40-70 Lenovo B50-70 Lenovo B50-80 Lenovo Flex-3 Lenovo Flex-10 Lenovo G40-30 Lenovo G50-30 Lenovo G50-70 Lenovo G50-80 Lenovo S20-30 Lenovo U31-70 Lenovo Y50-70 Lenovo Y70-70 Lenovo Yoga Thinkpad (20C0) Lenovo Yoga 2 11" - 20332 Lenovo Yoga 3 11" Lenovo Z50-70 Lenovo Z51-70 Lenovo ideapad 100-15IBY Acer Aspire E5-771G Acer Aspire ES1-111M-C1LE (fixed following your new instruction (thank you)) Acer TravelMate B113 Acer Swift SF314-52 (Fixed by 4.14.9) Toshiba Satellite S55T-B5233 Toshiba Satellite L50-B-1R7 Toshiba Satellite S50-B-13G Dell Inspiron 15-3531 - Mediacom Smartbook 14 Ultra M-SB14UC + Mediacom Smartbook 14 Ultra M-SB14UC (fixed with official fix) Acer Aspire E3-111-C0UM HP 14-r012la --- Affected serial flash devices by manufacturer part number, JEDEC ID (SPI_NOR_HAS_LOCK set in drivers/mtd/spi-nor/spi-nor.c) /* ESMT */ f25l32pa, 0x8c2016 f25l32qa, 0x8c4116 f25l64qa, 0x8c4117 /* GigaDevice */ gd25q16, 0xc84015 gd25q32, 0xc84016 gd25lq32, 0xc86016 gd25q64, 0xc84017 gd25lq64c, 0xc86017 gd25q128, 0xc84018 gd25q256, 0xc84019 /* Winbond */ w25q16dw, 0xef6015 w25q32dw, 0xef6016 w25q64dw, 0xef6017 w25q128fw, 0xef6018 --- Original Description: Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users reported a corrupted BIOS. It's not possible to save new settings in BIOS anymore and after rebooting, the system starts with the old settings. Moreover (and most important) USB booting is not possible anymore since USB is not recognized. It's very serious, since our machines do not have a CDROM. Lenovo forums at the moment are full of topics regading this issue. Thank you!! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1734147 Title: corrupted BIOS due to Intel SPI bug in kernel Status in Linux: Unknown Status in linux package in Ubuntu: Fix Released Status in linux-hwe-edge source package in Xenial: Fix Released Status in linux-oem source package in Xenial: Fix Released Status in linux source package in Artful: Fix Released Bug description: An update to linux kernel on Ubuntu 17.10 that enabled the Intel SPI drivers results in a serial flash that is read only in Intel Broadwell and Haswell machines with serial flashes with SPI_NOR_HAS_LOCK set. Symptoms: * BIOS settings cannot be saved * USB Boot impossible * EFI entries read-only. --- Fix: The issue was fixed in kernel version 4
[Kernel-packages] [Bug 1741081] Re: zfs-import-cache.service fails on startup
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: zfs-linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1741081 Title: zfs-import-cache.service fails on startup Status in zfs-linux package in Ubuntu: Confirmed Bug description: I just noticed on my test VM of artful that zfs-import-cache.service does not have a ConditionPathExists=/etc/zfs/zpool.cache. Because of that, it fails on startup, since the cache file does not exist. This line is being deleted by debian/patches/ubuntu-load-zfs-unconditionally.patch. This patch seems to exist per: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1672749 This patch still exists in bionic, so I assume it will be similarly broken. If the goal of the patch is to load the module (and only that), I think it should create a third unit instead: zfs-load-module.service ^^ runs modprobe zfs zfs-import-cache.service & zfs-import-scan.service ^^ per upstream minus modprobe plus Requires=zfs-load-module.service I have tested this manually and it works. I can submit a package patch if this is the desired solution. Interestingly, before this change, zfs-import-scan.service wasn't starting. If started manually, it worked. I had to give it a `systemctl enable zfs-import-scan.service` to create the Wants symlinks. Looking at the zfsutils-linux.postinst, I see the correct boilerplate from dh_systemd, so I'm not sure why this wasn't already done. Can anyone confirm or deny whether zfs-import-scan.service is enabled out-of-the-box on their system? Is the zfs-import-scan.service not starting actually the cause of the original bug? The design is that *either* zfs-import-cache.service or zfs-import-scan.service starts. They both call modprobe zfs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1741081/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1726743] Re: Kernel hangs after mounting usb HD
Kernel 4.13.0.31.33 still has this issue. Machine simply panics and freezes. syslog: ... Jan 23 16:40:49 mbpr13b kernel: [12217.671240] usb 2-2: new SuperSpeed USB device number 5 using xhci_hcd Jan 23 16:40:49 mbpr13b kernel: [12217.692311] usb 2-2: New USB device found, idVendor=0bc2, idProduct=231a Jan 23 16:40:49 mbpr13b kernel: [12217.692315] usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Jan 23 16:40:49 mbpr13b kernel: [12217.692317] usb 2-2: Product: Expansion Jan 23 16:40:49 mbpr13b kernel: [12217.692319] usb 2-2: Manufacturer: Seagate Jan 23 16:40:49 mbpr13b kernel: [12217.692321] usb 2-2: SerialNumber: NA8658H8 Jan 23 16:40:49 mbpr13b kernel: [12217.694135] scsi host1: uas Jan 23 16:40:49 mbpr13b kernel: [12217.694460] scsi 1:0:0:0: tag#0 data cmplt err -75 uas-tag 1 inflight: CMD Jan 23 16:40:49 mbpr13b kernel: [12217.694463] scsi 1:0:0:0: tag#0 CDB: Inquiry 12 00 00 00 24 00 Jan 23 16:40:49 mbpr13b kernel: [12217.694470] usb 2-2: stat urb: no pending cmd for uas-tag 0 Jan 23 16:40:50 mbpr13b kernel: [12217.695541] BUG: unable to handle kernel paging request at 0103 Jan 23 16:40:50 mbpr13b kernel: [12217.695604] IP: __kmalloc+0x9b/0x200 Jan 23 16:40:50 mbpr13b kernel: [12217.695629] PGD 0 Jan 23 16:40:50 mbpr13b kernel: [12217.695630] P4D 0 Jan 23 16:40:50 mbpr13b kernel: [12217.695646] Jan 23 16:40:50 mbpr13b kernel: [12217.695674] Oops: [#1] SMP PTI Jan 23 16:40:50 mbpr13b kernel: [12217.695698] Modules linked in: pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) rfcomm hid_magicmouse hidp cmac bnep nls_iso8859_1 joydev bcm5974 btusb btrtl btbcm btintel input_leds bluetooth ecdh_generic applesmc snd_hda_codec_cirrus snd_hda_codec_hdmi snd_hda_codec_generic input_polldev snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel snd_pcm snd_seq_midi snd_seq_midi_event kvm snd_rawmidi snd_seq snd_seq_device irqbypass snd_timer intel_cstate intel_rapl_perf snd brcmfmac intel_pch_thermal lpc_ich brcmutil soundcore thunderbolt cfg80211 bdc_pci mei_me dw_dmac_pci mei dw_dmac_core shpchp spi_pxa2xx_pci sbs acpi_als sbshc kfifo_buf industrialio spi_pxa2xx_platform mac_hid apple_bl parport_pc ppdev lp parport ip_tables Jan 23 16:40:50 mbpr13b kernel: [12217.696152] x_tables autofs4 algif_skcipher af_alg dm_crypt hid_apple hid_generic usbhid hid uas usb_storage crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc i915 aesni_intel i2c_algo_bit aes_x86_64 crypto_simd drm_kms_helper glue_helper cryptd syscopyarea sysfillrect sysimgblt fb_sys_fops ahci drm libahci video Jan 23 16:40:50 mbpr13b kernel: [12217.696339] CPU: 0 PID: 403 Comm: systemd-journal Tainted: G OE 4.13.0-31-generic #34-Ubuntu Jan 23 16:40:50 mbpr13b kernel: [12217.696396] Hardware name: Apple Inc. MacBookPro12,1/Mac-E43C1C25D4880AD6, BIOS MBP121.88Z.0171.B00.1708080033 08/08/2017 Jan 23 16:40:50 mbpr13b kernel: [12217.696461] task: 8f3d10d7c5c0 task.stack: a44f81f24000 Jan 23 16:40:50 mbpr13b kernel: [12217.696501] RIP: 0010:__kmalloc+0x9b/0x200 Jan 23 16:40:50 mbpr13b kernel: [12217.696529] RSP: 0018:a44f81f27c18 EFLAGS: 00010206 Jan 23 16:40:50 mbpr13b kernel: [12217.696563] RAX: RBX: 014080c0 RCX: 001007a8 Jan 23 16:40:50 mbpr13b kernel: [12217.696607] RDX: 001007a7 RSI: RDI: 00025ce0 Jan 23 16:40:50 mbpr13b kernel: [12217.696651] RBP: a44f81f27c48 R08: 8f3d2ec25ce0 R09: 8f3d1e003980 Jan 23 16:40:50 mbpr13b kernel: [12217.696695] R10: a44f81f27ec0 R11: R12: 0103 Jan 23 16:40:50 mbpr13b kernel: [12217.696739] R13: 014080c0 R14: 0018 R15: 8f3d1e003980 Jan 23 16:40:50 mbpr13b kernel: [12217.696784] FS: 7f41614fddc0() GS:8f3d2ec0() knlGS: Jan 23 16:40:50 mbpr13b kernel: [12217.696833] CS: 0010 DS: ES: CR0: 80050033 Jan 23 16:40:50 mbpr13b kernel: [12217.696869] CR2: 0103 CR3: 0004516a2002 CR4: 003606f0 Jan 23 16:40:50 mbpr13b kernel: [12217.696914] DR0: DR1: DR2: Jan 23 16:40:50 mbpr13b kernel: [12217.696957] DR3: 0080 DR6: 0ff0 DR7: 2400 Jan 23 16:40:50 mbpr13b kernel: [12217.697001] Call Trace: Jan 23 16:40:50 mbpr13b kernel: [12217.697023] ? security_file_alloc+0x58/0x70 Jan 23 16:40:50 mbpr13b kernel: [12217.697053] security_file_alloc+0x58/0x70 Jan 23 16:40:50 mbpr13b kernel: [12217.697083] get_empty_filp+0x93/0x1b0 Jan 23 16:40:50 mbpr13b kernel: [12217.697111] path_openat+0x3d/0x1630 Jan 23 16:40:50 mbpr13b kernel: [12217.697139] ? __bpf_prog_run32+0x39/0x50 Jan 23 16:40:50 mbpr13b kernel: [12217.697167] ? putname+0x4b/0x50 Jan 23 16:40:50 mbpr13b kernel: [12217.697192] do_filp_open+0x9b/0x110 Jan 23 16:40:50 mbpr13b kernel: [12217.697219] ? __seccomp
[Kernel-packages] [Bug 1741081] Re: zfs-import-cache.service fails on startup
Confirmed to also affect bionic: $ sudo journalctl -u zfs-import-cache.service -- Logs begin at Tue 2018-01-23 17:46:55 UTC, end at Tue 2018-01-23 17:49:18 UTC. -- Jan 23 17:46:58 ubuntu systemd[1]: Starting Import ZFS pools by cache file... Jan 23 17:46:59 ubuntu zpool[640]: failed to open cache file: No such file or directory Jan 23 17:46:59 ubuntu systemd[1]: zfs-import-cache.service: Main process exited, code=exited, status=1/FAILURE Jan 23 17:46:59 ubuntu systemd[1]: zfs-import-cache.service: Failed with result 'exit-code'. Jan 23 17:46:59 ubuntu systemd[1]: Failed to start Import ZFS pools by cache file. This is on a host with no ZFS filesystems, so expected behavior is a no- op. ** Tags added: artful bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1741081 Title: zfs-import-cache.service fails on startup Status in zfs-linux package in Ubuntu: Confirmed Bug description: I just noticed on my test VM of artful that zfs-import-cache.service does not have a ConditionPathExists=/etc/zfs/zpool.cache. Because of that, it fails on startup, since the cache file does not exist. This line is being deleted by debian/patches/ubuntu-load-zfs-unconditionally.patch. This patch seems to exist per: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1672749 This patch still exists in bionic, so I assume it will be similarly broken. If the goal of the patch is to load the module (and only that), I think it should create a third unit instead: zfs-load-module.service ^^ runs modprobe zfs zfs-import-cache.service & zfs-import-scan.service ^^ per upstream minus modprobe plus Requires=zfs-load-module.service I have tested this manually and it works. I can submit a package patch if this is the desired solution. Interestingly, before this change, zfs-import-scan.service wasn't starting. If started manually, it worked. I had to give it a `systemctl enable zfs-import-scan.service` to create the Wants symlinks. Looking at the zfsutils-linux.postinst, I see the correct boilerplate from dh_systemd, so I'm not sure why this wasn't already done. Can anyone confirm or deny whether zfs-import-scan.service is enabled out-of-the-box on their system? Is the zfs-import-scan.service not starting actually the cause of the original bug? The design is that *either* zfs-import-cache.service or zfs-import-scan.service starts. They both call modprobe zfs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1741081/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1744117] Re: [SRU][HWE] ALSA backport missing NVIDIA GPU codec IDs to patch table to Ubuntu 16.04 LTS Kernel
I have provided a test kernel "4.4.0-111-generic #134+hf166707v20180117b5" for pre-SRU verification and it has been brought to my attention the following statement: - Our QA was able to test with the kernel you provided, and things look good! I've upgraded the kernel and issue did not repro. Config : GPU Driver 384.111 Kernel 4.4.0-111-generic # uname -a Linux 4.4.0-111-generic #134+hf166707v20180117b5-Ubuntu SMP Wed Jan 17 19:04:03 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux I've verified output through all channels (7.1) using Test Sound option in Sound Setting + by running different 4,6 channel clips using aplay. Connections were made using DP-HDMI dongle (accell) + DENON-AVR - - Eric -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1744117 Title: [SRU][HWE] ALSA backport missing NVIDIA GPU codec IDs to patch table to Ubuntu 16.04 LTS Kernel Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: In Progress Bug description: Add support for 4/6/8 channel sound in 16.04 LTS kernel for future GPUs. This commit[1] first introduced in "Thu Jul 13 19:27:39 2017"[2] has what is needed base on discussion we had with nvidia: [1] - Commit https://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git/commit/?id=74ec118152ea494a25ebb677cbc83a75c982ac5f ALSA: hda - Add missing NVIDIA GPU codec IDs to patch table Add codec IDs for several recently released, pending, and historical NVIDIA GPU audio controllers to the patch table, to allow the correct patch functions to be selected for them. [2] - git describe --contains 74ec118152ea494a25ebb677cbc83a75c982ac5f v4.13-rc3~21^2~5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1744117/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1744979] Re: grub_efi_secure_boot signal at the beginning of the boot process
apport information ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Tags added: apport-collected ** Description changed: The previous kernel (4.4.0-109) was running without any problems, without triggering an error. After today's kernel update, the machine can not be started unless you select "run" the selected kernel from the advanced settings menu item. The first message always: grub_efi_secure_boot Ubuntu 4.4.0-112.135-generic 4.4.98 LSB Version: core-9.20160110ubuntu0.2-ia32:core-9.20160110ubuntu0.2-noarch:security-9.20160110ubuntu0.2-ia32:security-9.20160110ubuntu0.2-noarch Distributor ID: Ubuntu Description: Ubuntu 16.04.3 LTS Release: 16.04 Codename: xenial Intel® Core™ i5-3330 CPU @ 3.00GHz × 4 GeForce GT 630/PCIe/SSE2 system 32 bit Please help... I chose 16.04 LTS because I wanted to have a long, calm and safe use ... + --- + ApportVersion: 2.20.1-0ubuntu2.15 + Architecture: i386 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC1: csola481454 F pulseaudio + /dev/snd/controlC2: csola481454 F pulseaudio + /dev/snd/controlC0: csola481454 F pulseaudio + CurrentDesktop: Unity + DistroRelease: Ubuntu 16.04 + HibernationDevice: RESUME=UUID=6c8c77a4-d4d3-4e31-a038-13930e1abfd0 + InstallationDate: Installed on 2016-11-08 (441 days ago) + InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1) + IwConfig: + lono wireless extensions. + + enp4s0no wireless extensions. + MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. + NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia + Package: linux (not installed) + ProcFB: 0 VESA VGA + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic root=UUID=4cbb9ed4-c9ab-4ee3-8eb5-2473af0d2ae7 ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98 + RelatedPackageVersions: + linux-restricted-modules-4.4.0-112-generic N/A + linux-backports-modules-4.4.0-112-generic N/A + linux-firmware 1.157.14 + RfKill: + + Tags: xenial + Uname: Linux 4.4.0-112-generic i686 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 08/21/2012 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: F7 + dmi.board.asset.tag: To be filled by O.E.M. + dmi.board.name: H77-DS3H + dmi.board.vendor: Gigabyte Technology Co., Ltd. + dmi.board.version: x.x + dmi.chassis.asset.tag: To Be Filled By O.E.M. + dmi.chassis.type: 3 + dmi.chassis.vendor: Gigabyte Technology Co., Ltd. + dmi.chassis.version: To Be Filled By O.E.M. + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF7:bd08/21/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH77-DS3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: + dmi.product.name: To be filled by O.E.M. + dmi.product.version: To be filled by O.E.M. + dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1744979/+attachment/5041902/+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/1744979 Title: grub_efi_secure_boot signal at the beginning of the boot process Status in linux package in Ubuntu: Confirmed Bug description: The previous kernel (4.4.0-109) was running without any problems, without triggering an error. After today's kernel update, the machine can not be started unless you select "run" the selected kernel from the advanced settings menu item. The first message always: grub_efi_secure_boot Ubuntu 4.4.0-112.135-generic 4.4.98 LSB Version: core-9.20160110ubuntu0.2-ia32:core-9.20160110ubuntu0.2-noarch:security-9.20160110ubuntu0.2-ia32:security-9.20160110ubuntu0.2-noarch Distributor ID: Ubuntu Description: Ubuntu 16.04.3 LTS Release: 16.04 Codename: xenial Intel® Core™ i5-3330 CPU @ 3.00GHz × 4 GeForce GT 630/PCIe/SSE2 system 32 bit Please help... I chose 16.04 LTS because I wanted to have a long, calm and safe use ... --- ApportVersion: 2.20.1-0ubuntu2.15 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: csola481454 F pulseaudio /dev/snd/controlC2: csola481454 F pulseaudio /dev/snd/controlC0: csola481454 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=6c8c77a4-d4d3-4e31-a038-13930e1abfd0 InstallationDate: Installed on 2016-11-08 (441 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1) IwConfig: lono wireless extensions. enp4s0no wireless extensions. MachineType:
[Kernel-packages] [Bug 1744979] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1744979/+attachment/5041911/+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/1744979 Title: grub_efi_secure_boot signal at the beginning of the boot process Status in linux package in Ubuntu: Confirmed Bug description: The previous kernel (4.4.0-109) was running without any problems, without triggering an error. After today's kernel update, the machine can not be started unless you select "run" the selected kernel from the advanced settings menu item. The first message always: grub_efi_secure_boot Ubuntu 4.4.0-112.135-generic 4.4.98 LSB Version: core-9.20160110ubuntu0.2-ia32:core-9.20160110ubuntu0.2-noarch:security-9.20160110ubuntu0.2-ia32:security-9.20160110ubuntu0.2-noarch Distributor ID: Ubuntu Description: Ubuntu 16.04.3 LTS Release: 16.04 Codename: xenial Intel® Core™ i5-3330 CPU @ 3.00GHz × 4 GeForce GT 630/PCIe/SSE2 system 32 bit Please help... I chose 16.04 LTS because I wanted to have a long, calm and safe use ... --- ApportVersion: 2.20.1-0ubuntu2.15 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: csola481454 F pulseaudio /dev/snd/controlC2: csola481454 F pulseaudio /dev/snd/controlC0: csola481454 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=6c8c77a4-d4d3-4e31-a038-13930e1abfd0 InstallationDate: Installed on 2016-11-08 (441 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1) IwConfig: lono wireless extensions. enp4s0no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic root=UUID=4cbb9ed4-c9ab-4ee3-8eb5-2473af0d2ae7 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98 RelatedPackageVersions: linux-restricted-modules-4.4.0-112-generic N/A linux-backports-modules-4.4.0-112-generic N/A linux-firmware 1.157.14 RfKill: Tags: xenial Uname: Linux 4.4.0-112-generic i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/21/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F7 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H77-DS3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF7:bd08/21/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH77-DS3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1744979/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1744979] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1744979/+attachment/5041913/+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/1744979 Title: grub_efi_secure_boot signal at the beginning of the boot process Status in linux package in Ubuntu: Confirmed Bug description: The previous kernel (4.4.0-109) was running without any problems, without triggering an error. After today's kernel update, the machine can not be started unless you select "run" the selected kernel from the advanced settings menu item. The first message always: grub_efi_secure_boot Ubuntu 4.4.0-112.135-generic 4.4.98 LSB Version: core-9.20160110ubuntu0.2-ia32:core-9.20160110ubuntu0.2-noarch:security-9.20160110ubuntu0.2-ia32:security-9.20160110ubuntu0.2-noarch Distributor ID: Ubuntu Description: Ubuntu 16.04.3 LTS Release: 16.04 Codename: xenial Intel® Core™ i5-3330 CPU @ 3.00GHz × 4 GeForce GT 630/PCIe/SSE2 system 32 bit Please help... I chose 16.04 LTS because I wanted to have a long, calm and safe use ... --- ApportVersion: 2.20.1-0ubuntu2.15 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: csola481454 F pulseaudio /dev/snd/controlC2: csola481454 F pulseaudio /dev/snd/controlC0: csola481454 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=6c8c77a4-d4d3-4e31-a038-13930e1abfd0 InstallationDate: Installed on 2016-11-08 (441 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1) IwConfig: lono wireless extensions. enp4s0no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic root=UUID=4cbb9ed4-c9ab-4ee3-8eb5-2473af0d2ae7 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98 RelatedPackageVersions: linux-restricted-modules-4.4.0-112-generic N/A linux-backports-modules-4.4.0-112-generic N/A linux-firmware 1.157.14 RfKill: Tags: xenial Uname: Linux 4.4.0-112-generic i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/21/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F7 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H77-DS3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF7:bd08/21/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH77-DS3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1744979/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp