[Kernel-packages] [Bug 1759997] Re: intel-microcode 3.20180312.0~ubuntu17.10.1 fails to boot on E3-1505M
This is probably a duplicate of #1746418. Confusing part here was that the problem started appearing after microcode update. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1759997 Title: intel-microcode 3.20180312.0~ubuntu17.10.1 fails to boot on E3-1505M Status in linux package in Ubuntu: Confirmed Bug description: I have Lenovo P50 with E3-1505M. After intel-microcode 3.20180312.0~ubuntu17.10.1 is installed it hangs during boot some time after graphic display interface - exact time of hang differs from boot to boot. Rolling intel-microcode back to 3.20170707.1 fixes the problem. This happens on Ubuntu 17.10 with 4.13.0-37-generic and 4.13.0-36-generic kernels. --- ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: kolya 2039 F pulseaudio /dev/snd/controlC1: kolya 2039 F pulseaudio /dev/snd/pcmC0D0p: kolya 2039 F...m pulseaudio /dev/snd/controlC0: kolya 2039 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 17.10 HibernationDevice: RESUME=UUID=a1a81ad4-e4bc-4115-b60f-07f02f93ecf6 InstallationDate: Installed on 2016-02-20 (768 days ago) InstallationMedia: Ubuntu-MATE 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: LENOVO 20EN001SUS NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-37-generic root=/dev/mapper/ubuntu-root ro rootflags=subvol=@ quiet splash ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13 RelatedPackageVersions: linux-restricted-modules-4.13.0-37-generic N/A linux-backports-modules-4.13.0-37-generic N/A linux-firmware 1.169.3 Tags: artful Uname: Linux 4.13.0-37-generic x86_64 UpgradeStatus: Upgraded to artful on 2017-10-29 (152 days ago) UserGroups: dialout kismet libvirt sudo wireshark _MarkForUpload: True dmi.bios.date: 09/28/2017 dmi.bios.vendor: LENOVO dmi.bios.version: N1EET73W (1.46 ) dmi.board.asset.tag: Not Available dmi.board.name: 20EN001SUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1EET73W(1.46):bd09/28/2017:svnLENOVO:pn20EN001SUS:pvrThinkPadP50:rvnLENOVO:rn20EN001SUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P50 dmi.product.name: 20EN001SUS dmi.product.version: ThinkPad P50 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1759997/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1759821] Re: Dell XPS 13 9360 bluetooth scan can not detect any device
mainline v4.4.116 could not reproduce the issue with the target systems listed in the description. Results: https://certification.canonical.com/hardware/201606-22355/submission/128848/ https://certification.canonical.com/hardware/201606-22338/submission/128847/ https://certification.canonical.com/hardware/201610-25144/submission/128849/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1759821 Title: Dell XPS 13 9360 bluetooth scan can not detect any device Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: Dell XPS 13 9360 (CID 201606-22355) Image: OEM pre-installed image Kernel: 4.4.0-117-generic #141-Ubuntu SMP Tue Mar 13 11:58:07 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux Click the bluetooth applet and try to add bt devices. The long scanning (> 5 mins) gets nothing. Reproducing rate: 100% [More Information] ubuntu@201606-22355:~$ lspci -nn 00:00.0 Host bridge [0600]: Intel Corporation Device [8086:5904] (rev 02) 00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:5916] (rev 02) 00:04.0 Signal processing controller [1180]: Intel Corporation Skylake Processor Thermal Subsystem [8086:1903] (rev 02) 00:14.0 USB controller [0c03]: Intel Corporation Sunrise Point-LP USB 3.0 xHCI Controller [8086:9d2f] (rev 21) 00:14.2 Signal processing controller [1180]: Intel Corporation Sunrise Point-LP Thermal subsystem [8086:9d31] (rev 21) 00:15.0 Signal processing controller [1180]: Intel Corporation Sunrise Point-LP Serial IO I2C Controller [8086:9d60] (rev 21) 00:15.1 Signal processing controller [1180]: Intel Corporation Sunrise Point-LP Serial IO I2C Controller [8086:9d61] (rev 21) 00:16.0 Communication controller [0780]: Intel Corporation Sunrise Point-LP CSME HECI [8086:9d3a] (rev 21) 00:1c.0 PCI bridge [0604]: Intel Corporation Device [8086:9d10] (rev f1) 00:1c.4 PCI bridge [0604]: Intel Corporation Sunrise Point-LP PCI Express Root Port [8086:9d14] (rev f1) 00:1c.5 PCI bridge [0604]: Intel Corporation Sunrise Point-LP PCI Express Root Port [8086:9d15] (rev f1) 00:1d.0 PCI bridge [0604]: Intel Corporation Device [8086:9d18] (rev f1) 00:1f.0 ISA bridge [0601]: Intel Corporation Device [8086:9d58] (rev 21) 00:1f.2 Memory controller [0580]: Intel Corporation Sunrise Point-LP PMC [8086:9d21] (rev 21) 00:1f.3 Audio device [0403]: Intel Corporation Device [8086:9d71] (rev 21) 00:1f.4 SMBus [0c05]: Intel Corporation Sunrise Point-LP SMBus [8086:9d23] (rev 21) 3a:00.0 Network controller [0280]: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter [168c:003e] (rev 32) 3b:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS525A PCI Express Card Reader [10ec:525a] (rev 01) 3c:00.0 Non-Volatile memory controller [0108]: Samsung Electronics Co Ltd NVMe SSD Controller [144d:a802] (rev 01) ubuntu@201606-22355:~$ rfkill list 0: hci0: Bluetooth Soft blocked: no Hard blocked: no 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no ubuntu@201606-22355:~$ So far this issue affects the following machines at least: - Dell XPS 13 9360 (CID 201606-22338) - Dell XPS 13 9360 (CID 201606-22355) - Dell Precision 5520 (201610-25144) - ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-117-generic 4.4.0-117.141 ProcVersionSignature: Ubuntu 4.4.0-117.141-generic 4.4.114 Uname: Linux 4.4.0-117-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1723 F pulseaudio Date: Thu Mar 29 18:39:27 2018 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 HibernationDevice: RESUME=UUID=e30b2dfe-7ba1-4cde-876a-928e9bbb077b InstallationDate: Installed on 2018-03-23 (6 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. XPS 13 9360 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-117-generic.efi.signed root=UUID=488684c8-a47f-46bc-b84d-ad4bff229ccd ro automatic-oem-config quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-117-generic N/A linux-backports-modules-4.4.0-117-generic N/A linux-firmware 1.157.17 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/21/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.4.2 dmi.board.vendor: Dell Inc. dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnD
[Kernel-packages] [Bug 1759920] Re: linux-image-4.13.0-37-generic locks up at login screen with intel-microcode 3.20180312.0
I have this issue as well, and I'm pretty sure this is a regression of the latest released intel-microcode package as I deliberately upgrade this single one just today. ** Attachment added: "Content of /proc/cpuinfo" https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1759920/+attachment/5095607/+files/_proc_cpuinfo.content -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1759920 Title: intel-microcode 3.20180312.0 causes locks up at login screen(w/ linux- image-4.13.0-37-generic) Status in intel-microcode package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in intel-microcode source package in Artful: Confirmed Status in linux source package in Artful: Confirmed Bug description: I don't know if this is a problem with the kernel or the microcode, but we have a significant number of computers in our organization (on both 16.04 and 17.10) that fail if they have both updated. Booting with either linux-image-4.13.0-36-generic or intel-microcode 3.20180108.0+really20170707ubuntu17.10.1 allows all these computers to boot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1759920/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1759920] Re: linux-image-4.13.0-37-generic locks up at login screen with intel-microcode 3.20180312.0
This is a Ivybridge based laptop, ASUS S550CB to be specific. ** Attachment added: "Output of `sudo iucode-tool --scan-system`" https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1759920/+attachment/5095608/+files/iucode-tool_--scan-system.output ** Summary changed: - linux-image-4.13.0-37-generic locks up at login screen with intel-microcode 3.20180312.0 + intel-microcode 3.20180312.0 causes locks up at login screen(w/ linux-image-4.13.0-37-generic) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1759920 Title: intel-microcode 3.20180312.0 causes locks up at login screen(w/ linux- image-4.13.0-37-generic) Status in intel-microcode package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in intel-microcode source package in Artful: Confirmed Status in linux source package in Artful: Confirmed Bug description: I don't know if this is a problem with the kernel or the microcode, but we have a significant number of computers in our organization (on both 16.04 and 17.10) that fail if they have both updated. Booting with either linux-image-4.13.0-36-generic or intel-microcode 3.20180108.0+really20170707ubuntu17.10.1 allows all these computers to boot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1759920/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1759920] JournalErrors.txt
apport information ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1759920/+attachment/5095603/+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/1759920 Title: intel-microcode 3.20180312.0 causes locks up at login screen(w/ linux- image-4.13.0-37-generic) Status in intel-microcode package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in intel-microcode source package in Artful: Confirmed Status in linux source package in Artful: Confirmed Bug description: I don't know if this is a problem with the kernel or the microcode, but we have a significant number of computers in our organization (on both 16.04 and 17.10) that fail if they have both updated. Booting with either linux-image-4.13.0-36-generic or intel-microcode 3.20180108.0+really20170707ubuntu17.10.1 allows all these computers to boot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1759920/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1759920] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1759920/+attachment/5095602/+files/Dependencies.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/1759920 Title: intel-microcode 3.20180312.0 causes locks up at login screen(w/ linux- image-4.13.0-37-generic) Status in intel-microcode package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in intel-microcode source package in Artful: Confirmed Status in linux source package in Artful: Confirmed Bug description: I don't know if this is a problem with the kernel or the microcode, but we have a significant number of computers in our organization (on both 16.04 and 17.10) that fail if they have both updated. Booting with either linux-image-4.13.0-36-generic or intel-microcode 3.20180108.0+really20170707ubuntu17.10.1 allows all these computers to boot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1759920/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1759920] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1759920/+attachment/5095605/+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/1759920 Title: intel-microcode 3.20180312.0 causes locks up at login screen(w/ linux- image-4.13.0-37-generic) Status in intel-microcode package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in intel-microcode source package in Artful: Confirmed Status in linux source package in Artful: Confirmed Bug description: I don't know if this is a problem with the kernel or the microcode, but we have a significant number of computers in our organization (on both 16.04 and 17.10) that fail if they have both updated. Booting with either linux-image-4.13.0-36-generic or intel-microcode 3.20180108.0+really20170707ubuntu17.10.1 allows all these computers to boot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1759920/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1759920] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1759920/+attachment/5095604/+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/1759920 Title: intel-microcode 3.20180312.0 causes locks up at login screen(w/ linux- image-4.13.0-37-generic) Status in intel-microcode package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in intel-microcode source package in Artful: Confirmed Status in linux source package in Artful: Confirmed Bug description: I don't know if this is a problem with the kernel or the microcode, but we have a significant number of computers in our organization (on both 16.04 and 17.10) that fail if they have both updated. Booting with either linux-image-4.13.0-36-generic or intel-microcode 3.20180108.0+really20170707ubuntu17.10.1 allows all these computers to boot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1759920/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1759920] Re: linux-image-4.13.0-37-generic locks up at login screen with intel-microcode 3.20180312.0
ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CurrentDesktop: KDE DistroRelease: KDE 16.04 InstallationDate: Installed on 2017-04-11 (352 days ago) InstallationMedia: neon user "Xenial" - Build amd64 LIVE Binary 20170323-10:36 Package: linux PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.13.0-37.42~16.04.1-generic 4.13.13 Tags: third-party-packages xenial Uname: Linux 4.13.0-37-generic x86_64 UnreportableReason: 這不是官方的 KDE 套件。請移除任何第三方套件並重試。 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bumblebee cdrom dip docker libvirtd lpadmin lxd plugdev sambashare scanner sudo ubridge vboxusers video _MarkForUpload: True ** Tags added: third-party-packages -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1759920 Title: intel-microcode 3.20180312.0 causes locks up at login screen(w/ linux- image-4.13.0-37-generic) Status in intel-microcode package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in intel-microcode source package in Artful: Confirmed Status in linux source package in Artful: Confirmed Bug description: I don't know if this is a problem with the kernel or the microcode, but we have a significant number of computers in our organization (on both 16.04 and 17.10) that fail if they have both updated. Booting with either linux-image-4.13.0-36-generic or intel-microcode 3.20180108.0+really20170707ubuntu17.10.1 allows all these computers to boot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1759920/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1729674] Re: TB16 dock ethernet corrupts data with hw checksum silently failing
I've already backported it: http://kernel.ubuntu.com/git/ubuntu/ubuntu-xenial.git/commit/?h=master- next&id=2cecb2e49bee95d4b9d89f732e999a6908db6abf -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1729674 Title: TB16 dock ethernet corrupts data with hw checksum silently failing Status in Dell Sputnik: Triaged Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Status in linux source package in Artful: Fix Committed Status in linux source package in Bionic: Fix Released Status in linux package in Fedora: Confirmed Bug description: It looks like TCP rx and tx checksum offloading is broken on the TB16 dock's ethernet adapter. For example downloading a large file such as the Ubuntu ISO, and then running an md5sum on it yields the incorrect md5sum. This is because rx-checksumming: on tx-checksumming: on and both set to on by default. Running sudo ethtool -K tx off rx off, allows the download to complete correctly. This is very bad since this can cause very bad untrustworthy behavior. This was conducted using an Dell Precision 5520 on Ubuntu 16.04+linux- generic-hwe-16.04-edge. Thank you To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1729674/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1759865] Re: general protection fault: 0000 [#1] SMP NOPTI
Doesn't look like switching out the video driver was enough; I'll continue with the kernel change after work tomorrow. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1759865 Title: general protection fault: [#1] SMP NOPTI Status in linux package in Ubuntu: Incomplete Bug description: I was using chrome and saw the update-notifier warn me of "" Went to the command line to try to figure out what the problem was. Most commands just core dumped (including apt and su) however I was able to get this from dmesg [ 693.573723] cron[5576]: segfault at 7fff196473d0 ip 7fff196473d0 sp 7fff19645a80 error 15 [ 695.126425] phpquery[5587]: segfault at 7ffd0388c258 ip 56454f0e4650 sp 7ffd0388a180 error 6 in dash[56454f0d2000+1c000] [ 695.234845] phpquery[5591]: segfault at 7ffd0388c258 ip 56454f0e4650 sp 7ffd0388a180 error 6 in dash[56454f0d2000+1c000] [ 695.343616] phpquery[5589]: segfault at 7ffd0388c258 ip 56454f0e4650 sp 7ffd0388a180 error 6 in dash[56454f0d2000+1c000] [ 695.452099] phpquery[5585]: segfault at 7ffd0388c258 ip 56454f0e4650 sp 7ffd0388a180 error 6 in dash[56454f0d2000+1c000] [ 695.583528] sessionclean[5598]: segfault at 7ffc09ce50e8 ip 55936e2f0650 sp 7ffc09ce3010 error 6 in dash[55936e2de000+1c000] [ 695.692891] sessionclean[5597]: segfault at 7ffc09ce50e8 ip 55936e2f0650 sp 7ffc09ce3010 error 6 in dash[55936e2de000+1c000] [ 695.801617] sessionclean[5581]: segfault at 7ffc09ce50e8 ip 55936e2f0650 sp 7ffc09ce3010 error 6 in dash[55936e2de000+1c000] [ 695.904212] sessionclean[5584]: segfault at 7ffc09ce50e8 ip 55936e2f0650 sp 7ffc09ce3010 error 6 in dash[55936e2de000+1c000] [ 696.013519] sessionclean[5580]: segfault at 7ffc09ce50e8 ip 55936e2f0650 sp 7ffc09ce3010 error 6 in dash[55936e2de000+1c000] [ 696.695912] systemd: 35 output lines suppressed due to ratelimiting [ 769.048253] systemd-journald[545]: Failed to send WATCHDOG=1 notification message: Connection refused [ 828.941426] systemd-journald[545]: Failed to send WATCHDOG=1 notification message: Transport endpoint is not connected [ 908.937238] systemd-journald[545]: Failed to send WATCHDOG=1 notification message: Transport endpoint is not connected [ 999.871627] systemd-journald[545]: Failed to send WATCHDOG=1 notification message: Transport endpoint is not connected [ 1005.962536] systemd-journald[545]: Failed to send WATCHDOG=1 notification message: Transport endpoint is not connected [ 1005.975570] show_signal_msg: 1 callbacks suppressed [ 1005.975573] which[6212]: segfault at 7ffeadceb8a8 ip 55d161a5e650 sp 7ffeadce97d0 error 6 in dash[55d161a4c000+1c000] [ 1006.089011] which[6218]: segfault at 7fff2ad5e448 ip 561b807f8650 sp 7fff2ad5c370 error 6 in dash[561b807e6000+1c000] [ 1006.219235] which[6223]: segfault at 7ffcee0a0118 ip 5621a961f650 sp 7ffcee09e040 error 6 in dash[5621a960d000+1c000] [ 1006.343970] which[6228]: segfault at 7ffc9fda2948 ip 55b0a1fb5650 sp 7ffc9fda0870 error 6 in dash[55b0a1fa3000+1c000] [ 1006.472231] which[6234]: segfault at 7ffc991e4528 ip 555b82672650 sp 7ffc991e2450 error 6 in dash[555b8266+1c000] [ 1006.597085] which[6240]: segfault at 7fff395ec008 ip 5652da3aa650 sp 7fff395e9f30 error 6 in dash[5652da398000+1c000] [ 1008.042333] idea_tmp_check.[6414]: segfault at 7ffd634cb518 ip 5633b025e650 sp 7ffd634c9440 error 6 in dash[5633b024c000+1c000] ProblemType: KernelOops DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-13-generic 4.15.0-13.14 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 Date: Thu Mar 29 06:49:08 2018 Failure: oops MachineType: System manufacturer System Product Name ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed root=UUID=9320ec1f-aa3c-477d-b5d8-b02d82864086 ro pcie_aspm=off PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: kerneloops-daemon N/A SourcePackage: linux Title: general protection fault: [#1] SMP NOPTI UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/21/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0902 dmi.board.asset.tag: Default string dmi.board.name: ROG ZENITH EXTREME dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.ver
[Kernel-packages] [Bug 1759947] Re: BUG: unable to handle kernel paging request at 0000200000000020
Sure - trying it now. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1759947 Title: BUG: unable to handle kernel paging request at 2020 Status in linux package in Ubuntu: Confirmed Bug description: Unclear what happened. It said chrome was dying, but then nothing including mouse and keyboard worked. ProblemType: KernelOops DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-13-generic 4.15.0-13.14 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 Date: Thu Mar 29 13:56:40 2018 DuplicateSignature: BUG: unable to handle kernel paging request at location RIP: find_get_entry+0x42/0x110 RSP: b73c51c3fbe8 Failure: oops MachineType: System manufacturer System Product Name ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed root=UUID=9320ec1f-aa3c-477d-b5d8-b02d82864086 ro pcie_aspm=off PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: kerneloops-daemon N/A SourcePackage: linux Title: BUG: unable to handle kernel paging request at 2020 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/21/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0902 dmi.board.asset.tag: Default string dmi.board.name: ROG ZENITH EXTREME dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0902:bd12/21/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGZENITHEXTREME:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1759947/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1759920] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1759920/+attachment/5095598/+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/1759920 Title: linux-image-4.13.0-37-generic locks up at login screen with intel- microcode 3.20180312.0 Status in intel-microcode package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in intel-microcode source package in Artful: Confirmed Status in linux source package in Artful: Confirmed Bug description: I don't know if this is a problem with the kernel or the microcode, but we have a significant number of computers in our organization (on both 16.04 and 17.10) that fail if they have both updated. Booting with either linux-image-4.13.0-36-generic or intel-microcode 3.20180108.0+really20170707ubuntu17.10.1 allows all these computers to boot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1759920/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1759920] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1759920/+attachment/5095597/+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/1759920 Title: linux-image-4.13.0-37-generic locks up at login screen with intel- microcode 3.20180312.0 Status in intel-microcode package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in intel-microcode source package in Artful: Confirmed Status in linux source package in Artful: Confirmed Bug description: I don't know if this is a problem with the kernel or the microcode, but we have a significant number of computers in our organization (on both 16.04 and 17.10) that fail if they have both updated. Booting with either linux-image-4.13.0-36-generic or intel-microcode 3.20180108.0+really20170707ubuntu17.10.1 allows all these computers to boot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1759920/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1759920] JournalErrors.txt
apport information ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1759920/+attachment/5095596/+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/1759920 Title: linux-image-4.13.0-37-generic locks up at login screen with intel- microcode 3.20180312.0 Status in intel-microcode package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in intel-microcode source package in Artful: Confirmed Status in linux source package in Artful: Confirmed Bug description: I don't know if this is a problem with the kernel or the microcode, but we have a significant number of computers in our organization (on both 16.04 and 17.10) that fail if they have both updated. Booting with either linux-image-4.13.0-36-generic or intel-microcode 3.20180108.0+really20170707ubuntu17.10.1 allows all these computers to boot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1759920/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1759920] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1759920/+attachment/5095595/+files/Dependencies.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/1759920 Title: linux-image-4.13.0-37-generic locks up at login screen with intel- microcode 3.20180312.0 Status in intel-microcode package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in intel-microcode source package in Artful: Confirmed Status in linux source package in Artful: Confirmed Bug description: I don't know if this is a problem with the kernel or the microcode, but we have a significant number of computers in our organization (on both 16.04 and 17.10) that fail if they have both updated. Booting with either linux-image-4.13.0-36-generic or intel-microcode 3.20180108.0+really20170707ubuntu17.10.1 allows all these computers to boot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1759920/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1759920] apport information
ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2018-02-17 (40 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) Package: linux PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13 Tags: artful Uname: Linux 4.13.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1759920 Title: linux-image-4.13.0-37-generic locks up at login screen with intel- microcode 3.20180312.0 Status in intel-microcode package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in intel-microcode source package in Artful: Confirmed Status in linux source package in Artful: Confirmed Bug description: I don't know if this is a problem with the kernel or the microcode, but we have a significant number of computers in our organization (on both 16.04 and 17.10) that fail if they have both updated. Booting with either linux-image-4.13.0-36-generic or intel-microcode 3.20180108.0+really20170707ubuntu17.10.1 allows all these computers to boot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1759920/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1758206] Comment bridged from LTC Bugzilla
--- Comment From pavra...@in.ibm.com 2018-03-30 01:14 EDT--- Tested again with given kernel, dump capture is successful with smt=2 and smt=off. Sorry fr the wrong update in previous comment, not sure what i had missed yesterday. root@ltc-wspoon4:~# uname -a Linux ltc-wspoon4 4.15.0-12-generic #13~lp1758206 SMP Tue Mar 27 15:20:59 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux root@ltc-wspoon4:~# ppc64_cpu --smt=off root@ltc-wspoon4:~# root@ltc-wspoon4:~# echo 1 > /proc/sys/kernel/sysrq root@ltc-wspoon4:~# echo "c" > /proc/sysrq-trigger [ 1424.806117] sysrq: SysRq : Trigger a crash [ 1424.806163] Unable to handle kernel paging request for data at address 0x [ 1424.806267] Faulting instruction address: 0xc07ec768 [ 1424.806352] Oops: Kernel access of bad area, sig: 11 [#1] [ 1424.806424] LE SMP NR_CPUS=2048 NUMA PowerNV [ 1424.806483] Modules linked in: idt_89hpesx(E) at24 ofpart uio_pdrv_genirq cmdlinepart powernv_flash uio mtd opal_prd ipmi_powernv ipmi_devintf ibmpowernv vmx_crypto ipmi_msghandler crct10dif_vpmsum sch_fq_codel ip_tables x_tables autofs4 ast i2c_algo_bit ttm drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops ahci crc32c_vpmsum drm tg3 libahci [ 1424.806828] CPU: 0 PID: 3110 Comm: bash Tainted: GE 4.15.0-12-generic #13~lp1758206 [ 1424.806963] NIP: c07ec768 LR: c07ed6a8 CTR: c07ec740 [ 1424.807075] REGS: c01fce3d39f0 TRAP: 0300 Tainted: GE (4.15.0-12-generic) [ 1424.807211] MSR: 90009033 CR: 2822 XER: 2004 [ 1424.807325] CFAR: c07ed6a4 DAR: DSISR: 4200 SOFTE: 1 [ 1424.807325] GPR00: c07ed6a8 c01fce3d3c70 c16eaf00 0063 [ 1424.807325] GPR04: c01ff6fbce18 c01ff6fd4368 90009033 000a [ 1424.807325] GPR08: 0007 0001 90001003 [ 1424.807325] GPR12: c07ec740 c7a2 06127f00ae48 [ 1424.807325] GPR16: 06124f78e9f0 06124f821998 06124f8219d0 06124f858204 [ 1424.807325] GPR20: 0001 7fffd6e57524 [ 1424.807325] GPR24: 7fffd6e57520 06124f85afc4 c15e9968 0002 [ 1424.807325] GPR28: 0063 0004 c1572a9c c15e9d08 [ 1424.808272] NIP [c07ec768] sysrq_handle_crash+0x28/0x30 [ 1424.808364] LR [c07ed6a8] __handle_sysrq+0xf8/0x2c0 [ 1424.808417] Call Trace: [ 1424.808468] [c01fce3d3c70] [c07ed688] __handle_sysrq+0xd8/0x2c0 (unreliable) [ 1424.808582] [c01fce3d3d10] [c07edeb4] write_sysrq_trigger+0x64/0x90 [ 1424.808690] [c01fce3d3d40] [c047dfe8] proc_reg_write+0x88/0xd0 [ 1424.808782] [c01fce3d3d70] [c03d131c] __vfs_write+0x3c/0x70 [ 1424.808875] [c01fce3d3d90] [c03d1578] vfs_write+0xd8/0x220 [ 1424.808957] [c01fce3d3de0] [c03d1898] SyS_write+0x68/0x110 [ 1424.809038] [c01fce3d3e30] [c000b184] system_call+0x58/0x6c [ 1424.809139] Instruction dump: [ 1424.809191] 4bfff9f1 4bfffe50 3c4c00f0 3842e7c0 7c0802a6 6000 3921 3d42001c [ 1424.809294] 394a6db0 912a 7c0004ac 3940 <992a> 4e800020 3c4c00f0 3842e790 [ 1424.809399] ---[ end trace a6b92894072107e0 ]--- [ 1425.814557] [ 1425.814659] Sending IPI to other CPUs [ 1427[ 1827.188061287,5] OPAL: Switch to big-endian OS .111853] IPI complete [ 1428[ 1830.496187306,5] OPAL: Switch to little-endian OS [ 1832.313865861,3] PHB#[0:0]: CRESET: Unexpected slot state 0102, resetting... [ 1840.498727171,3] PHB#0003[0:3]: CRESET: Unexpected slot state 0102, resetting... [ 1849.245109062,3] PHB#0030[8:0]: CRESET: Unexpected slot state 0102, resetting... [ 1851.209060452,3] PHB#0033[8:3]: CRESET: Unexpected slot state 0102, resetting... [ 1853.170614858,3] PHB#0034[8:4]: CRESET: Unexpected slot state 0102, resetting... .808156] kexec: Starting switchover sequence. [1.199857] integrity: Unable to open file: /etc/keys/x509_ima.der (-2) [1.199861] integrity: Unable to open file: /etc/keys/x509_evm.der (-2) [1.286500] vio vio: uevent: failed to send synthetic uevent /dev/sdb2: recovering journal /dev/sdb2: clean, 163655/61054976 files, 17123931/244188416 blocks [6.018312] vio vio: uevent: failed to send synthetic uevent [ OK ] Started Show Plymouth Boot Screen. plymouth-start.service [ OK ] Started Forward Password Requests to Plymouth Directory Watch. [ OK ] Reached target Local Encrypted Volumes. [ OK ] Started Network Service. systemd-networkd.service Starting Wait for Network to be Configured... [ OK ] Reached target Network. [7.934300] PKCS#7 signature not signed with a trusted key [7.934373] PKCS#7 signature not signed with a trusted key [7.935026] PKCS#7 signature not signed with a trusted key [7.935470] PKCS#7 signature not signed with a trusted key [7.93
[Kernel-packages] [Bug 1723904] Re: ubuntu-kvm-unit test failed with sprs test on ppc64le
The attachment "canonical_sprs_backport.patch" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1723904 Title: ubuntu-kvm-unit test failed with sprs test on ppc64le Status in linux package in Ubuntu: Confirmed Status in qemu package in Ubuntu: Incomplete Bug description: The sprs test has failed on ppc64le This issue can be spotted on Zesty and Xenial. There is no history for this test on Artful $ sudo /bin/bash -c "MIGRATION=yes TESTNAME=sprs TIMEOUT=90s ACCEL= ./powerpc/run powerpc/sprs.elf -smp 1 -append '-w'" run_migration timeout -k 1s --foreground 90s /usr/bin/qemu-system-ppc64 -nodefaults -machine pseries,accel=kvm -bios powerpc/boot_rom.bin -display none -serial stdio -kernel powerpc/sprs.elf -smp 1 -append -w # -initrd /tmp/tmp.RUTL6E2JSi Settings SPRs to 0xcafefacec0debabe... Now migrate the VM, then press a key or send NMI... Checking SPRs... PASS: SPR 3: 0x00debabe <==> 0x00debabe PASS: SPR 13: 0xcafefacec0debabe <==> 0xcafefacec0debabe PASS: SPR 17: 0x00debabe <==> 0x00debabe PASS: SPR 18: 0xc0debabe <==> 0xc0debabe PASS: SPR 19: 0xcafefacec0debabe <==> 0xcafefacec0debabe PASS: SPR 29: 0xcafefacec0debabe <==> 0xcafefacec0debabe FAIL: SPR 61: 0x4054504440541014 <==> 00 PASS: SPR 153:0x0a84 <==> 0x0a84 PASS: SPR 157:0xcfcfc0cf <==> 0xcfcfc0cf FAIL: SPR 159:0xc0debabe <==> 00 PASS: SPR 256:0xc0debabe <==> 0xc0debabe PASS: SPR 259:0xcafefacec0debabe <==> 0xcafefacec0debabe PASS: SPR 274:0xcafefacec0debabe <==> 0xcafefacec0debabe PASS: SPR 275:0xcafefacec0debabe <==> 0xcafefacec0debabe PASS: SPR 769:0xcafefacec0debabe <==> 0xcafefacec0debabe PASS: SPR 770:0xcafefacec006babe <==> 0xcafefacec006babe PASS: SPR 771:0xc0debabe <==> 0xc0debabe PASS: SPR 772:0xc0debabe <==> 0xc0debabe PASS: SPR 773:0xc0debabe <==> 0xc0debabe PASS: SPR 774:0xc0debabe <==> 0xc0debabe PASS: SPR 775:0xc0debabe <==> 0xc0debabe PASS: SPR 776:0xc0debabe <==> 0xc0debabe PASS: SPR 779:0xfa8b1afe <==> 0xfa8b1afe PASS: SPR 780:0xcafefacec0debabc <==> 0xcafefacec0debabc PASS: SPR 781:0xcafefacec0debabe <==> 0xcafefacec0debabe PASS: SPR 782:0xcafefacec0debabe <==> 0xcafefacec0debabe FAIL: SPR 784:0xcafefacec0debabe <==> 00 PASS: SPR 785:0xcafefacec0debabe <==> 0xcafefacec0debabe PASS: SPR 786:0xcafefacec006babe <==> 0xcafefacec006babe PASS: SPR 787:0xc0debabe <==> 0xc0debabe PASS: SPR 788:0xc0debabe <==> 0xc0debabe PASS: SPR 789:0xc0debabe <==> 0xc0debabe PASS: SPR 790:0xc0debabe <==> 0xc0debabe PASS: SPR 791:0xc0debabe <==> 0xc0debabe PASS: SPR 792:0xc0debabe <==> 0xc0debabe PASS: SPR 795:0xfa8b1afe <==> 0xfa8b1afe PASS: SPR 796:0xcafefacec0debabc <==> 0xcafefacec0debabc PASS: SPR 797:0xcafefacec0debabe <==> 0xcafefacec0debabe PASS: SPR 798:0xcafefacec0debabe <==> 0xcafefacec0debabe PASS: SPR 800:0x8000c000 <==> 0x8000c000 PASS: SPR 801:0x8000 <==> 0x8000 PASS: SPR 802:0x8000c000 <==> 0x8000c000 PASS: SPR 803:0x8000 <==> 0x8000 PASS: SPR 804:0xcafefacec0debabe <==> 0xcafefacec0debabe PASS: SPR 805:0xcafefacec0debabc <==> 0xcafefacec0debabc PASS: SPR 806:0x8000c000 <==> 0x8000c000 FAIL: SPR 815:0xcafefacec0debabe <==> 00 SUMMARY: 47 tests, 4 unexpected failures EXIT: STATUS=3 $ qemu-system-ppc --version QEMU emulator version 2.5.0 (Debian 1:2.5+dfsg-5ubuntu10.16), Copyright (c) 2003-2008 Fabrice Bellard ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.10.0-37-generic 4.10.0-37.41~16.04.1 ProcVersionSignature: User Name 4.10.0-37.41~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-37-generic ppc64le ApportVersion: 2.20.1-0ubuntu2.10 Architecture: ppc64el Date: Mon Oct 16 09:16:08 2017 ProcEnviron: TERM=xterm-256color PATH=(custom, no user)
[Kernel-packages] [Bug 1759920] Re: linux-image-4.13.0-37-generic locks up at login screen with intel-microcode 3.20180312.0
John, could you run 'apport-collect 1759920' or, alternatively, include your /proc/cpuinfo contents and the 'iucode-tool --scan-system' output? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1759920 Title: linux-image-4.13.0-37-generic locks up at login screen with intel- microcode 3.20180312.0 Status in intel-microcode package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in intel-microcode source package in Artful: Confirmed Status in linux source package in Artful: Confirmed Bug description: I don't know if this is a problem with the kernel or the microcode, but we have a significant number of computers in our organization (on both 16.04 and 17.10) that fail if they have both updated. Booting with either linux-image-4.13.0-36-generic or intel-microcode 3.20180108.0+really20170707ubuntu17.10.1 allows all these computers to boot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1759920/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1740855] Re: Ubuntu 17.10 freeze after a while after startup
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1740855 Title: Ubuntu 17.10 freeze after a while after startup Status in linux package in Ubuntu: Expired Bug description: Hello, after upgrading to ubuntu 17.10, my pc freezes every time after a while after startup. Mostly when browsing webpages (google-chrome); playing videos (youtube) oder while development with eclipse / java. Some Times the screens begin to "flittering", sometimes the desktop freezes completly. The only thing, that works ist : ALT+PRINT+REISUB to reset an restart the pc. Sometimes this Magic-Keys doensn't work. Before 17.10 I use 17.04 Ubuntu, and everything was fine! I've got a gigabyte Graficcard with 2 TFT-Displays connected. One with dvi, one with hdmi. This worked fine in 17.04 and also in 17.10, instead of the freezing in 17.10. lsb-release -rd Description: Ubuntu 17.10 Release: 17.10 ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-21-generic 4.13.0-21.24 ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13 Uname: Linux 4.13.0-21-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: thomas 1470 F pulseaudio /dev/snd/controlC0: thomas 1470 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Jan 2 12:23:31 2018 IwConfig: lono wireless extensions. enp3s0no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. GA-78LMT-USB3 6.0 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-21-generic root=UUID=3880cd93-060f-4216-aefa-20044b4df8ee ro quiet splash vt.handoff=7 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: SourcePackage: linux UpgradeStatus: Upgraded to artful on 2017-11-26 (36 days ago) dmi.bios.date: 11/25/2014 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F2 dmi.board.name: GA-78LMT-USB3 6.0 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF2:bd11/25/2014:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-USB36.0:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-USB36.0:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-78LMT-USB3 6.0 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1740855/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1759997] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1759997/+attachment/5095518/+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/1759997 Title: intel-microcode 3.20180312.0~ubuntu17.10.1 fails to boot on E3-1505M Status in linux package in Ubuntu: Confirmed Bug description: I have Lenovo P50 with E3-1505M. After intel-microcode 3.20180312.0~ubuntu17.10.1 is installed it hangs during boot some time after graphic display interface - exact time of hang differs from boot to boot. Rolling intel-microcode back to 3.20170707.1 fixes the problem. This happens on Ubuntu 17.10 with 4.13.0-37-generic and 4.13.0-36-generic kernels. --- ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: kolya 2039 F pulseaudio /dev/snd/controlC1: kolya 2039 F pulseaudio /dev/snd/pcmC0D0p: kolya 2039 F...m pulseaudio /dev/snd/controlC0: kolya 2039 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 17.10 HibernationDevice: RESUME=UUID=a1a81ad4-e4bc-4115-b60f-07f02f93ecf6 InstallationDate: Installed on 2016-02-20 (768 days ago) InstallationMedia: Ubuntu-MATE 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: LENOVO 20EN001SUS NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-37-generic root=/dev/mapper/ubuntu-root ro rootflags=subvol=@ quiet splash ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13 RelatedPackageVersions: linux-restricted-modules-4.13.0-37-generic N/A linux-backports-modules-4.13.0-37-generic N/A linux-firmware 1.169.3 Tags: artful Uname: Linux 4.13.0-37-generic x86_64 UpgradeStatus: Upgraded to artful on 2017-10-29 (152 days ago) UserGroups: dialout kismet libvirt sudo wireshark _MarkForUpload: True dmi.bios.date: 09/28/2017 dmi.bios.vendor: LENOVO dmi.bios.version: N1EET73W (1.46 ) dmi.board.asset.tag: Not Available dmi.board.name: 20EN001SUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1EET73W(1.46):bd09/28/2017:svnLENOVO:pn20EN001SUS:pvrThinkPadP50:rvnLENOVO:rn20EN001SUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P50 dmi.product.name: 20EN001SUS dmi.product.version: ThinkPad P50 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1759997/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1759997] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1759997/+attachment/5095517/+files/RfKill.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1759997 Title: intel-microcode 3.20180312.0~ubuntu17.10.1 fails to boot on E3-1505M Status in linux package in Ubuntu: Confirmed Bug description: I have Lenovo P50 with E3-1505M. After intel-microcode 3.20180312.0~ubuntu17.10.1 is installed it hangs during boot some time after graphic display interface - exact time of hang differs from boot to boot. Rolling intel-microcode back to 3.20170707.1 fixes the problem. This happens on Ubuntu 17.10 with 4.13.0-37-generic and 4.13.0-36-generic kernels. --- ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: kolya 2039 F pulseaudio /dev/snd/controlC1: kolya 2039 F pulseaudio /dev/snd/pcmC0D0p: kolya 2039 F...m pulseaudio /dev/snd/controlC0: kolya 2039 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 17.10 HibernationDevice: RESUME=UUID=a1a81ad4-e4bc-4115-b60f-07f02f93ecf6 InstallationDate: Installed on 2016-02-20 (768 days ago) InstallationMedia: Ubuntu-MATE 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: LENOVO 20EN001SUS NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-37-generic root=/dev/mapper/ubuntu-root ro rootflags=subvol=@ quiet splash ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13 RelatedPackageVersions: linux-restricted-modules-4.13.0-37-generic N/A linux-backports-modules-4.13.0-37-generic N/A linux-firmware 1.169.3 Tags: artful Uname: Linux 4.13.0-37-generic x86_64 UpgradeStatus: Upgraded to artful on 2017-10-29 (152 days ago) UserGroups: dialout kismet libvirt sudo wireshark _MarkForUpload: True dmi.bios.date: 09/28/2017 dmi.bios.vendor: LENOVO dmi.bios.version: N1EET73W (1.46 ) dmi.board.asset.tag: Not Available dmi.board.name: 20EN001SUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1EET73W(1.46):bd09/28/2017:svnLENOVO:pn20EN001SUS:pvrThinkPadP50:rvnLENOVO:rn20EN001SUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P50 dmi.product.name: 20EN001SUS dmi.product.version: ThinkPad P50 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1759997/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1759997] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1759997/+attachment/5095519/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1759997 Title: intel-microcode 3.20180312.0~ubuntu17.10.1 fails to boot on E3-1505M Status in linux package in Ubuntu: Confirmed Bug description: I have Lenovo P50 with E3-1505M. After intel-microcode 3.20180312.0~ubuntu17.10.1 is installed it hangs during boot some time after graphic display interface - exact time of hang differs from boot to boot. Rolling intel-microcode back to 3.20170707.1 fixes the problem. This happens on Ubuntu 17.10 with 4.13.0-37-generic and 4.13.0-36-generic kernels. --- ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: kolya 2039 F pulseaudio /dev/snd/controlC1: kolya 2039 F pulseaudio /dev/snd/pcmC0D0p: kolya 2039 F...m pulseaudio /dev/snd/controlC0: kolya 2039 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 17.10 HibernationDevice: RESUME=UUID=a1a81ad4-e4bc-4115-b60f-07f02f93ecf6 InstallationDate: Installed on 2016-02-20 (768 days ago) InstallationMedia: Ubuntu-MATE 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: LENOVO 20EN001SUS NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-37-generic root=/dev/mapper/ubuntu-root ro rootflags=subvol=@ quiet splash ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13 RelatedPackageVersions: linux-restricted-modules-4.13.0-37-generic N/A linux-backports-modules-4.13.0-37-generic N/A linux-firmware 1.169.3 Tags: artful Uname: Linux 4.13.0-37-generic x86_64 UpgradeStatus: Upgraded to artful on 2017-10-29 (152 days ago) UserGroups: dialout kismet libvirt sudo wireshark _MarkForUpload: True dmi.bios.date: 09/28/2017 dmi.bios.vendor: LENOVO dmi.bios.version: N1EET73W (1.46 ) dmi.board.asset.tag: Not Available dmi.board.name: 20EN001SUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1EET73W(1.46):bd09/28/2017:svnLENOVO:pn20EN001SUS:pvrThinkPadP50:rvnLENOVO:rn20EN001SUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P50 dmi.product.name: 20EN001SUS dmi.product.version: ThinkPad P50 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1759997/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1759997] JournalErrors.txt
apport information ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1759997/+attachment/5095508/+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/1759997 Title: intel-microcode 3.20180312.0~ubuntu17.10.1 fails to boot on E3-1505M Status in linux package in Ubuntu: Confirmed Bug description: I have Lenovo P50 with E3-1505M. After intel-microcode 3.20180312.0~ubuntu17.10.1 is installed it hangs during boot some time after graphic display interface - exact time of hang differs from boot to boot. Rolling intel-microcode back to 3.20170707.1 fixes the problem. This happens on Ubuntu 17.10 with 4.13.0-37-generic and 4.13.0-36-generic kernels. --- ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: kolya 2039 F pulseaudio /dev/snd/controlC1: kolya 2039 F pulseaudio /dev/snd/pcmC0D0p: kolya 2039 F...m pulseaudio /dev/snd/controlC0: kolya 2039 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 17.10 HibernationDevice: RESUME=UUID=a1a81ad4-e4bc-4115-b60f-07f02f93ecf6 InstallationDate: Installed on 2016-02-20 (768 days ago) InstallationMedia: Ubuntu-MATE 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: LENOVO 20EN001SUS NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-37-generic root=/dev/mapper/ubuntu-root ro rootflags=subvol=@ quiet splash ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13 RelatedPackageVersions: linux-restricted-modules-4.13.0-37-generic N/A linux-backports-modules-4.13.0-37-generic N/A linux-firmware 1.169.3 Tags: artful Uname: Linux 4.13.0-37-generic x86_64 UpgradeStatus: Upgraded to artful on 2017-10-29 (152 days ago) UserGroups: dialout kismet libvirt sudo wireshark _MarkForUpload: True dmi.bios.date: 09/28/2017 dmi.bios.vendor: LENOVO dmi.bios.version: N1EET73W (1.46 ) dmi.board.asset.tag: Not Available dmi.board.name: 20EN001SUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1EET73W(1.46):bd09/28/2017:svnLENOVO:pn20EN001SUS:pvrThinkPadP50:rvnLENOVO:rn20EN001SUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P50 dmi.product.name: 20EN001SUS dmi.product.version: ThinkPad P50 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1759997/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1759997] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1759997/+attachment/5095509/+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/1759997 Title: intel-microcode 3.20180312.0~ubuntu17.10.1 fails to boot on E3-1505M Status in linux package in Ubuntu: Confirmed Bug description: I have Lenovo P50 with E3-1505M. After intel-microcode 3.20180312.0~ubuntu17.10.1 is installed it hangs during boot some time after graphic display interface - exact time of hang differs from boot to boot. Rolling intel-microcode back to 3.20170707.1 fixes the problem. This happens on Ubuntu 17.10 with 4.13.0-37-generic and 4.13.0-36-generic kernels. --- ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: kolya 2039 F pulseaudio /dev/snd/controlC1: kolya 2039 F pulseaudio /dev/snd/pcmC0D0p: kolya 2039 F...m pulseaudio /dev/snd/controlC0: kolya 2039 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 17.10 HibernationDevice: RESUME=UUID=a1a81ad4-e4bc-4115-b60f-07f02f93ecf6 InstallationDate: Installed on 2016-02-20 (768 days ago) InstallationMedia: Ubuntu-MATE 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: LENOVO 20EN001SUS NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-37-generic root=/dev/mapper/ubuntu-root ro rootflags=subvol=@ quiet splash ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13 RelatedPackageVersions: linux-restricted-modules-4.13.0-37-generic N/A linux-backports-modules-4.13.0-37-generic N/A linux-firmware 1.169.3 Tags: artful Uname: Linux 4.13.0-37-generic x86_64 UpgradeStatus: Upgraded to artful on 2017-10-29 (152 days ago) UserGroups: dialout kismet libvirt sudo wireshark _MarkForUpload: True dmi.bios.date: 09/28/2017 dmi.bios.vendor: LENOVO dmi.bios.version: N1EET73W (1.46 ) dmi.board.asset.tag: Not Available dmi.board.name: 20EN001SUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1EET73W(1.46):bd09/28/2017:svnLENOVO:pn20EN001SUS:pvrThinkPadP50:rvnLENOVO:rn20EN001SUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P50 dmi.product.name: 20EN001SUS dmi.product.version: ThinkPad P50 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1759997/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1759997] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1759997/+attachment/5095516/+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/1759997 Title: intel-microcode 3.20180312.0~ubuntu17.10.1 fails to boot on E3-1505M Status in linux package in Ubuntu: Confirmed Bug description: I have Lenovo P50 with E3-1505M. After intel-microcode 3.20180312.0~ubuntu17.10.1 is installed it hangs during boot some time after graphic display interface - exact time of hang differs from boot to boot. Rolling intel-microcode back to 3.20170707.1 fixes the problem. This happens on Ubuntu 17.10 with 4.13.0-37-generic and 4.13.0-36-generic kernels. --- ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: kolya 2039 F pulseaudio /dev/snd/controlC1: kolya 2039 F pulseaudio /dev/snd/pcmC0D0p: kolya 2039 F...m pulseaudio /dev/snd/controlC0: kolya 2039 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 17.10 HibernationDevice: RESUME=UUID=a1a81ad4-e4bc-4115-b60f-07f02f93ecf6 InstallationDate: Installed on 2016-02-20 (768 days ago) InstallationMedia: Ubuntu-MATE 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: LENOVO 20EN001SUS NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-37-generic root=/dev/mapper/ubuntu-root ro rootflags=subvol=@ quiet splash ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13 RelatedPackageVersions: linux-restricted-modules-4.13.0-37-generic N/A linux-backports-modules-4.13.0-37-generic N/A linux-firmware 1.169.3 Tags: artful Uname: Linux 4.13.0-37-generic x86_64 UpgradeStatus: Upgraded to artful on 2017-10-29 (152 days ago) UserGroups: dialout kismet libvirt sudo wireshark _MarkForUpload: True dmi.bios.date: 09/28/2017 dmi.bios.vendor: LENOVO dmi.bios.version: N1EET73W (1.46 ) dmi.board.asset.tag: Not Available dmi.board.name: 20EN001SUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1EET73W(1.46):bd09/28/2017:svnLENOVO:pn20EN001SUS:pvrThinkPadP50:rvnLENOVO:rn20EN001SUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P50 dmi.product.name: 20EN001SUS dmi.product.version: ThinkPad P50 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1759997/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1759997] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1759997/+attachment/5095506/+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/1759997 Title: intel-microcode 3.20180312.0~ubuntu17.10.1 fails to boot on E3-1505M Status in linux package in Ubuntu: Confirmed Bug description: I have Lenovo P50 with E3-1505M. After intel-microcode 3.20180312.0~ubuntu17.10.1 is installed it hangs during boot some time after graphic display interface - exact time of hang differs from boot to boot. Rolling intel-microcode back to 3.20170707.1 fixes the problem. This happens on Ubuntu 17.10 with 4.13.0-37-generic and 4.13.0-36-generic kernels. --- ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: kolya 2039 F pulseaudio /dev/snd/controlC1: kolya 2039 F pulseaudio /dev/snd/pcmC0D0p: kolya 2039 F...m pulseaudio /dev/snd/controlC0: kolya 2039 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 17.10 HibernationDevice: RESUME=UUID=a1a81ad4-e4bc-4115-b60f-07f02f93ecf6 InstallationDate: Installed on 2016-02-20 (768 days ago) InstallationMedia: Ubuntu-MATE 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: LENOVO 20EN001SUS NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-37-generic root=/dev/mapper/ubuntu-root ro rootflags=subvol=@ quiet splash ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13 RelatedPackageVersions: linux-restricted-modules-4.13.0-37-generic N/A linux-backports-modules-4.13.0-37-generic N/A linux-firmware 1.169.3 Tags: artful Uname: Linux 4.13.0-37-generic x86_64 UpgradeStatus: Upgraded to artful on 2017-10-29 (152 days ago) UserGroups: dialout kismet libvirt sudo wireshark _MarkForUpload: True dmi.bios.date: 09/28/2017 dmi.bios.vendor: LENOVO dmi.bios.version: N1EET73W (1.46 ) dmi.board.asset.tag: Not Available dmi.board.name: 20EN001SUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1EET73W(1.46):bd09/28/2017:svnLENOVO:pn20EN001SUS:pvrThinkPadP50:rvnLENOVO:rn20EN001SUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P50 dmi.product.name: 20EN001SUS dmi.product.version: ThinkPad P50 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1759997/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1759997] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1759997/+attachment/5095510/+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/1759997 Title: intel-microcode 3.20180312.0~ubuntu17.10.1 fails to boot on E3-1505M Status in linux package in Ubuntu: Confirmed Bug description: I have Lenovo P50 with E3-1505M. After intel-microcode 3.20180312.0~ubuntu17.10.1 is installed it hangs during boot some time after graphic display interface - exact time of hang differs from boot to boot. Rolling intel-microcode back to 3.20170707.1 fixes the problem. This happens on Ubuntu 17.10 with 4.13.0-37-generic and 4.13.0-36-generic kernels. --- ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: kolya 2039 F pulseaudio /dev/snd/controlC1: kolya 2039 F pulseaudio /dev/snd/pcmC0D0p: kolya 2039 F...m pulseaudio /dev/snd/controlC0: kolya 2039 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 17.10 HibernationDevice: RESUME=UUID=a1a81ad4-e4bc-4115-b60f-07f02f93ecf6 InstallationDate: Installed on 2016-02-20 (768 days ago) InstallationMedia: Ubuntu-MATE 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: LENOVO 20EN001SUS NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-37-generic root=/dev/mapper/ubuntu-root ro rootflags=subvol=@ quiet splash ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13 RelatedPackageVersions: linux-restricted-modules-4.13.0-37-generic N/A linux-backports-modules-4.13.0-37-generic N/A linux-firmware 1.169.3 Tags: artful Uname: Linux 4.13.0-37-generic x86_64 UpgradeStatus: Upgraded to artful on 2017-10-29 (152 days ago) UserGroups: dialout kismet libvirt sudo wireshark _MarkForUpload: True dmi.bios.date: 09/28/2017 dmi.bios.vendor: LENOVO dmi.bios.version: N1EET73W (1.46 ) dmi.board.asset.tag: Not Available dmi.board.name: 20EN001SUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1EET73W(1.46):bd09/28/2017:svnLENOVO:pn20EN001SUS:pvrThinkPadP50:rvnLENOVO:rn20EN001SUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P50 dmi.product.name: 20EN001SUS dmi.product.version: ThinkPad P50 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1759997/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1759997] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1759997/+attachment/5095512/+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/1759997 Title: intel-microcode 3.20180312.0~ubuntu17.10.1 fails to boot on E3-1505M Status in linux package in Ubuntu: Confirmed Bug description: I have Lenovo P50 with E3-1505M. After intel-microcode 3.20180312.0~ubuntu17.10.1 is installed it hangs during boot some time after graphic display interface - exact time of hang differs from boot to boot. Rolling intel-microcode back to 3.20170707.1 fixes the problem. This happens on Ubuntu 17.10 with 4.13.0-37-generic and 4.13.0-36-generic kernels. --- ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: kolya 2039 F pulseaudio /dev/snd/controlC1: kolya 2039 F pulseaudio /dev/snd/pcmC0D0p: kolya 2039 F...m pulseaudio /dev/snd/controlC0: kolya 2039 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 17.10 HibernationDevice: RESUME=UUID=a1a81ad4-e4bc-4115-b60f-07f02f93ecf6 InstallationDate: Installed on 2016-02-20 (768 days ago) InstallationMedia: Ubuntu-MATE 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: LENOVO 20EN001SUS NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-37-generic root=/dev/mapper/ubuntu-root ro rootflags=subvol=@ quiet splash ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13 RelatedPackageVersions: linux-restricted-modules-4.13.0-37-generic N/A linux-backports-modules-4.13.0-37-generic N/A linux-firmware 1.169.3 Tags: artful Uname: Linux 4.13.0-37-generic x86_64 UpgradeStatus: Upgraded to artful on 2017-10-29 (152 days ago) UserGroups: dialout kismet libvirt sudo wireshark _MarkForUpload: True dmi.bios.date: 09/28/2017 dmi.bios.vendor: LENOVO dmi.bios.version: N1EET73W (1.46 ) dmi.board.asset.tag: Not Available dmi.board.name: 20EN001SUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1EET73W(1.46):bd09/28/2017:svnLENOVO:pn20EN001SUS:pvrThinkPadP50:rvnLENOVO:rn20EN001SUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P50 dmi.product.name: 20EN001SUS dmi.product.version: ThinkPad P50 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1759997/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1759997] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1759997/+attachment/5095507/+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/1759997 Title: intel-microcode 3.20180312.0~ubuntu17.10.1 fails to boot on E3-1505M Status in linux package in Ubuntu: Confirmed Bug description: I have Lenovo P50 with E3-1505M. After intel-microcode 3.20180312.0~ubuntu17.10.1 is installed it hangs during boot some time after graphic display interface - exact time of hang differs from boot to boot. Rolling intel-microcode back to 3.20170707.1 fixes the problem. This happens on Ubuntu 17.10 with 4.13.0-37-generic and 4.13.0-36-generic kernels. --- ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: kolya 2039 F pulseaudio /dev/snd/controlC1: kolya 2039 F pulseaudio /dev/snd/pcmC0D0p: kolya 2039 F...m pulseaudio /dev/snd/controlC0: kolya 2039 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 17.10 HibernationDevice: RESUME=UUID=a1a81ad4-e4bc-4115-b60f-07f02f93ecf6 InstallationDate: Installed on 2016-02-20 (768 days ago) InstallationMedia: Ubuntu-MATE 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: LENOVO 20EN001SUS NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-37-generic root=/dev/mapper/ubuntu-root ro rootflags=subvol=@ quiet splash ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13 RelatedPackageVersions: linux-restricted-modules-4.13.0-37-generic N/A linux-backports-modules-4.13.0-37-generic N/A linux-firmware 1.169.3 Tags: artful Uname: Linux 4.13.0-37-generic x86_64 UpgradeStatus: Upgraded to artful on 2017-10-29 (152 days ago) UserGroups: dialout kismet libvirt sudo wireshark _MarkForUpload: True dmi.bios.date: 09/28/2017 dmi.bios.vendor: LENOVO dmi.bios.version: N1EET73W (1.46 ) dmi.board.asset.tag: Not Available dmi.board.name: 20EN001SUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1EET73W(1.46):bd09/28/2017:svnLENOVO:pn20EN001SUS:pvrThinkPadP50:rvnLENOVO:rn20EN001SUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P50 dmi.product.name: 20EN001SUS dmi.product.version: ThinkPad P50 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1759997/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1759997] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1759997/+attachment/5095515/+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/1759997 Title: intel-microcode 3.20180312.0~ubuntu17.10.1 fails to boot on E3-1505M Status in linux package in Ubuntu: Confirmed Bug description: I have Lenovo P50 with E3-1505M. After intel-microcode 3.20180312.0~ubuntu17.10.1 is installed it hangs during boot some time after graphic display interface - exact time of hang differs from boot to boot. Rolling intel-microcode back to 3.20170707.1 fixes the problem. This happens on Ubuntu 17.10 with 4.13.0-37-generic and 4.13.0-36-generic kernels. --- ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: kolya 2039 F pulseaudio /dev/snd/controlC1: kolya 2039 F pulseaudio /dev/snd/pcmC0D0p: kolya 2039 F...m pulseaudio /dev/snd/controlC0: kolya 2039 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 17.10 HibernationDevice: RESUME=UUID=a1a81ad4-e4bc-4115-b60f-07f02f93ecf6 InstallationDate: Installed on 2016-02-20 (768 days ago) InstallationMedia: Ubuntu-MATE 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: LENOVO 20EN001SUS NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-37-generic root=/dev/mapper/ubuntu-root ro rootflags=subvol=@ quiet splash ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13 RelatedPackageVersions: linux-restricted-modules-4.13.0-37-generic N/A linux-backports-modules-4.13.0-37-generic N/A linux-firmware 1.169.3 Tags: artful Uname: Linux 4.13.0-37-generic x86_64 UpgradeStatus: Upgraded to artful on 2017-10-29 (152 days ago) UserGroups: dialout kismet libvirt sudo wireshark _MarkForUpload: True dmi.bios.date: 09/28/2017 dmi.bios.vendor: LENOVO dmi.bios.version: N1EET73W (1.46 ) dmi.board.asset.tag: Not Available dmi.board.name: 20EN001SUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1EET73W(1.46):bd09/28/2017:svnLENOVO:pn20EN001SUS:pvrThinkPadP50:rvnLENOVO:rn20EN001SUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P50 dmi.product.name: 20EN001SUS dmi.product.version: ThinkPad P50 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1759997/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1759997] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1759997/+attachment/5095514/+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/1759997 Title: intel-microcode 3.20180312.0~ubuntu17.10.1 fails to boot on E3-1505M Status in linux package in Ubuntu: Confirmed Bug description: I have Lenovo P50 with E3-1505M. After intel-microcode 3.20180312.0~ubuntu17.10.1 is installed it hangs during boot some time after graphic display interface - exact time of hang differs from boot to boot. Rolling intel-microcode back to 3.20170707.1 fixes the problem. This happens on Ubuntu 17.10 with 4.13.0-37-generic and 4.13.0-36-generic kernels. --- ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: kolya 2039 F pulseaudio /dev/snd/controlC1: kolya 2039 F pulseaudio /dev/snd/pcmC0D0p: kolya 2039 F...m pulseaudio /dev/snd/controlC0: kolya 2039 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 17.10 HibernationDevice: RESUME=UUID=a1a81ad4-e4bc-4115-b60f-07f02f93ecf6 InstallationDate: Installed on 2016-02-20 (768 days ago) InstallationMedia: Ubuntu-MATE 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: LENOVO 20EN001SUS NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-37-generic root=/dev/mapper/ubuntu-root ro rootflags=subvol=@ quiet splash ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13 RelatedPackageVersions: linux-restricted-modules-4.13.0-37-generic N/A linux-backports-modules-4.13.0-37-generic N/A linux-firmware 1.169.3 Tags: artful Uname: Linux 4.13.0-37-generic x86_64 UpgradeStatus: Upgraded to artful on 2017-10-29 (152 days ago) UserGroups: dialout kismet libvirt sudo wireshark _MarkForUpload: True dmi.bios.date: 09/28/2017 dmi.bios.vendor: LENOVO dmi.bios.version: N1EET73W (1.46 ) dmi.board.asset.tag: Not Available dmi.board.name: 20EN001SUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1EET73W(1.46):bd09/28/2017:svnLENOVO:pn20EN001SUS:pvrThinkPadP50:rvnLENOVO:rn20EN001SUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P50 dmi.product.name: 20EN001SUS dmi.product.version: ThinkPad P50 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1759997/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1759997] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1759997/+attachment/5095505/+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/1759997 Title: intel-microcode 3.20180312.0~ubuntu17.10.1 fails to boot on E3-1505M Status in linux package in Ubuntu: Confirmed Bug description: I have Lenovo P50 with E3-1505M. After intel-microcode 3.20180312.0~ubuntu17.10.1 is installed it hangs during boot some time after graphic display interface - exact time of hang differs from boot to boot. Rolling intel-microcode back to 3.20170707.1 fixes the problem. This happens on Ubuntu 17.10 with 4.13.0-37-generic and 4.13.0-36-generic kernels. --- ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: kolya 2039 F pulseaudio /dev/snd/controlC1: kolya 2039 F pulseaudio /dev/snd/pcmC0D0p: kolya 2039 F...m pulseaudio /dev/snd/controlC0: kolya 2039 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 17.10 HibernationDevice: RESUME=UUID=a1a81ad4-e4bc-4115-b60f-07f02f93ecf6 InstallationDate: Installed on 2016-02-20 (768 days ago) InstallationMedia: Ubuntu-MATE 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: LENOVO 20EN001SUS NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-37-generic root=/dev/mapper/ubuntu-root ro rootflags=subvol=@ quiet splash ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13 RelatedPackageVersions: linux-restricted-modules-4.13.0-37-generic N/A linux-backports-modules-4.13.0-37-generic N/A linux-firmware 1.169.3 Tags: artful Uname: Linux 4.13.0-37-generic x86_64 UpgradeStatus: Upgraded to artful on 2017-10-29 (152 days ago) UserGroups: dialout kismet libvirt sudo wireshark _MarkForUpload: True dmi.bios.date: 09/28/2017 dmi.bios.vendor: LENOVO dmi.bios.version: N1EET73W (1.46 ) dmi.board.asset.tag: Not Available dmi.board.name: 20EN001SUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1EET73W(1.46):bd09/28/2017:svnLENOVO:pn20EN001SUS:pvrThinkPadP50:rvnLENOVO:rn20EN001SUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P50 dmi.product.name: 20EN001SUS dmi.product.version: ThinkPad P50 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1759997/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1759997] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1759997/+attachment/5095513/+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/1759997 Title: intel-microcode 3.20180312.0~ubuntu17.10.1 fails to boot on E3-1505M Status in linux package in Ubuntu: Confirmed Bug description: I have Lenovo P50 with E3-1505M. After intel-microcode 3.20180312.0~ubuntu17.10.1 is installed it hangs during boot some time after graphic display interface - exact time of hang differs from boot to boot. Rolling intel-microcode back to 3.20170707.1 fixes the problem. This happens on Ubuntu 17.10 with 4.13.0-37-generic and 4.13.0-36-generic kernels. --- ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: kolya 2039 F pulseaudio /dev/snd/controlC1: kolya 2039 F pulseaudio /dev/snd/pcmC0D0p: kolya 2039 F...m pulseaudio /dev/snd/controlC0: kolya 2039 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 17.10 HibernationDevice: RESUME=UUID=a1a81ad4-e4bc-4115-b60f-07f02f93ecf6 InstallationDate: Installed on 2016-02-20 (768 days ago) InstallationMedia: Ubuntu-MATE 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: LENOVO 20EN001SUS NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-37-generic root=/dev/mapper/ubuntu-root ro rootflags=subvol=@ quiet splash ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13 RelatedPackageVersions: linux-restricted-modules-4.13.0-37-generic N/A linux-backports-modules-4.13.0-37-generic N/A linux-firmware 1.169.3 Tags: artful Uname: Linux 4.13.0-37-generic x86_64 UpgradeStatus: Upgraded to artful on 2017-10-29 (152 days ago) UserGroups: dialout kismet libvirt sudo wireshark _MarkForUpload: True dmi.bios.date: 09/28/2017 dmi.bios.vendor: LENOVO dmi.bios.version: N1EET73W (1.46 ) dmi.board.asset.tag: Not Available dmi.board.name: 20EN001SUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1EET73W(1.46):bd09/28/2017:svnLENOVO:pn20EN001SUS:pvrThinkPadP50:rvnLENOVO:rn20EN001SUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P50 dmi.product.name: 20EN001SUS dmi.product.version: ThinkPad P50 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1759997/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1759997] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1759997/+attachment/5095511/+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/1759997 Title: intel-microcode 3.20180312.0~ubuntu17.10.1 fails to boot on E3-1505M Status in linux package in Ubuntu: Confirmed Bug description: I have Lenovo P50 with E3-1505M. After intel-microcode 3.20180312.0~ubuntu17.10.1 is installed it hangs during boot some time after graphic display interface - exact time of hang differs from boot to boot. Rolling intel-microcode back to 3.20170707.1 fixes the problem. This happens on Ubuntu 17.10 with 4.13.0-37-generic and 4.13.0-36-generic kernels. --- ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: kolya 2039 F pulseaudio /dev/snd/controlC1: kolya 2039 F pulseaudio /dev/snd/pcmC0D0p: kolya 2039 F...m pulseaudio /dev/snd/controlC0: kolya 2039 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 17.10 HibernationDevice: RESUME=UUID=a1a81ad4-e4bc-4115-b60f-07f02f93ecf6 InstallationDate: Installed on 2016-02-20 (768 days ago) InstallationMedia: Ubuntu-MATE 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: LENOVO 20EN001SUS NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-37-generic root=/dev/mapper/ubuntu-root ro rootflags=subvol=@ quiet splash ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13 RelatedPackageVersions: linux-restricted-modules-4.13.0-37-generic N/A linux-backports-modules-4.13.0-37-generic N/A linux-firmware 1.169.3 Tags: artful Uname: Linux 4.13.0-37-generic x86_64 UpgradeStatus: Upgraded to artful on 2017-10-29 (152 days ago) UserGroups: dialout kismet libvirt sudo wireshark _MarkForUpload: True dmi.bios.date: 09/28/2017 dmi.bios.vendor: LENOVO dmi.bios.version: N1EET73W (1.46 ) dmi.board.asset.tag: Not Available dmi.board.name: 20EN001SUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1EET73W(1.46):bd09/28/2017:svnLENOVO:pn20EN001SUS:pvrThinkPadP50:rvnLENOVO:rn20EN001SUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P50 dmi.product.name: 20EN001SUS dmi.product.version: ThinkPad P50 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1759997/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1759997] Re: intel-microcode 3.20180312.0~ubuntu17.10.1 fails to boot on E3-1505M
apport information ** Tags added: apport-collected ** Description changed: I have Lenovo P50 with E3-1505M. After intel-microcode 3.20180312.0~ubuntu17.10.1 is installed it hangs during boot some time after graphic display interface - exact time of hang differs from boot to boot. Rolling intel-microcode back to 3.20170707.1 fixes the problem. - This happens on Ubuntu 17.10 with 4.13.0-37-generic and - 4.13.0-36-generic kernels. + This happens on Ubuntu 17.10 with 4.13.0-37-generic and 4.13.0-36-generic kernels. + --- + ApportVersion: 2.20.7-0ubuntu3.7 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC2: kolya 2039 F pulseaudio + /dev/snd/controlC1: kolya 2039 F pulseaudio + /dev/snd/pcmC0D0p: kolya 2039 F...m pulseaudio + /dev/snd/controlC0: kolya 2039 F pulseaudio + CurrentDesktop: MATE + DistroRelease: Ubuntu 17.10 + HibernationDevice: RESUME=UUID=a1a81ad4-e4bc-4115-b60f-07f02f93ecf6 + InstallationDate: Installed on 2016-02-20 (768 days ago) + InstallationMedia: Ubuntu-MATE 15.10 "Wily Werewolf" - Release amd64 (20151021) + MachineType: LENOVO 20EN001SUS + NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia + Package: linux (not installed) + ProcFB: 0 EFI VGA + ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-37-generic root=/dev/mapper/ubuntu-root ro rootflags=subvol=@ quiet splash + ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13 + RelatedPackageVersions: + linux-restricted-modules-4.13.0-37-generic N/A + linux-backports-modules-4.13.0-37-generic N/A + linux-firmware 1.169.3 + Tags: artful + Uname: Linux 4.13.0-37-generic x86_64 + UpgradeStatus: Upgraded to artful on 2017-10-29 (152 days ago) + UserGroups: dialout kismet libvirt sudo wireshark + _MarkForUpload: True + dmi.bios.date: 09/28/2017 + dmi.bios.vendor: LENOVO + dmi.bios.version: N1EET73W (1.46 ) + dmi.board.asset.tag: Not Available + dmi.board.name: 20EN001SUS + dmi.board.vendor: LENOVO + dmi.board.version: SDK0J40705 WIN + dmi.chassis.asset.tag: No Asset Information + dmi.chassis.type: 10 + dmi.chassis.vendor: LENOVO + dmi.chassis.version: None + dmi.modalias: dmi:bvnLENOVO:bvrN1EET73W(1.46):bd09/28/2017:svnLENOVO:pn20EN001SUS:pvrThinkPadP50:rvnLENOVO:rn20EN001SUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: + dmi.product.family: ThinkPad P50 + dmi.product.name: 20EN001SUS + dmi.product.version: ThinkPad P50 + dmi.sys.vendor: LENOVO ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1759997/+attachment/5095504/+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/1759997 Title: intel-microcode 3.20180312.0~ubuntu17.10.1 fails to boot on E3-1505M Status in linux package in Ubuntu: Confirmed Bug description: I have Lenovo P50 with E3-1505M. After intel-microcode 3.20180312.0~ubuntu17.10.1 is installed it hangs during boot some time after graphic display interface - exact time of hang differs from boot to boot. Rolling intel-microcode back to 3.20170707.1 fixes the problem. This happens on Ubuntu 17.10 with 4.13.0-37-generic and 4.13.0-36-generic kernels. --- ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: kolya 2039 F pulseaudio /dev/snd/controlC1: kolya 2039 F pulseaudio /dev/snd/pcmC0D0p: kolya 2039 F...m pulseaudio /dev/snd/controlC0: kolya 2039 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 17.10 HibernationDevice: RESUME=UUID=a1a81ad4-e4bc-4115-b60f-07f02f93ecf6 InstallationDate: Installed on 2016-02-20 (768 days ago) InstallationMedia: Ubuntu-MATE 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: LENOVO 20EN001SUS NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-37-generic root=/dev/mapper/ubuntu-root ro rootflags=subvol=@ quiet splash ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13 RelatedPackageVersions: linux-restricted-modules-4.13.0-37-generic N/A linux-backports-modules-4.13.0-37-generic N/A linux-firmware 1.169.3 Tags: artful Uname: Linux 4.13.0-37-generic x86_64 UpgradeStatus: Upgraded to artful on 2017-10-29 (152 days ago) UserGroups: dialout kismet libvirt sudo wireshark _MarkForUpload: True dmi.bios.date: 09/28/2017 dmi.bios.vendor: LENOVO dmi.bios.version: N1EET73W (1.46 ) dmi.board.asset.tag: Not Available dmi.board.name: 20EN001SUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvr
[Kernel-packages] [Bug 1759999] [NEW] missing net-snmp packages in redhat
Public bug reported: The net-snmp-python packages were upgraded from 5.7.2-24 to 5.7.2-31 However the dependent packages were missing. so adding upgraded dependent packages as well. ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Tags: analytics ** 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/175 Title: missing net-snmp packages in redhat Status in linux package in Ubuntu: Invalid Bug description: The net-snmp-python packages were upgraded from 5.7.2-24 to 5.7.2-31 However the dependent packages were missing. so adding upgraded dependent packages as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/175/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1759997] 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 1759997 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: artful -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1759997 Title: intel-microcode 3.20180312.0~ubuntu17.10.1 fails to boot on E3-1505M Status in linux package in Ubuntu: Incomplete Bug description: I have Lenovo P50 with E3-1505M. After intel-microcode 3.20180312.0~ubuntu17.10.1 is installed it hangs during boot some time after graphic display interface - exact time of hang differs from boot to boot. Rolling intel-microcode back to 3.20170707.1 fixes the problem. This happens on Ubuntu 17.10 with 4.13.0-37-generic and 4.13.0-36-generic kernels. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1759997/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1759997] [NEW] intel-microcode 3.20180312.0~ubuntu17.10.1 fails to boot on E3-1505M
Public bug reported: I have Lenovo P50 with E3-1505M. After intel-microcode 3.20180312.0~ubuntu17.10.1 is installed it hangs during boot some time after graphic display interface - exact time of hang differs from boot to boot. Rolling intel-microcode back to 3.20170707.1 fixes the problem. This happens on Ubuntu 17.10 with 4.13.0-37-generic and 4.13.0-36-generic kernels. ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: artful ** Description changed: I have Lenovo P50 with E3-1505M. After intel-microcode 3.20180312.0~ubuntu17.10.1 is installed it hangs during boot some time after graphic display interface - exact time of hang differs from boot to boot. Rolling intel-microcode back to 3.20170707.1 fixes the problem. + + This happens on Ubuntu 17.10 with 4.13.0-37-generic and + 4.13.0-36-generic kernels. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1759997 Title: intel-microcode 3.20180312.0~ubuntu17.10.1 fails to boot on E3-1505M Status in linux package in Ubuntu: Incomplete Bug description: I have Lenovo P50 with E3-1505M. After intel-microcode 3.20180312.0~ubuntu17.10.1 is installed it hangs during boot some time after graphic display interface - exact time of hang differs from boot to boot. Rolling intel-microcode back to 3.20170707.1 fixes the problem. This happens on Ubuntu 17.10 with 4.13.0-37-generic and 4.13.0-36-generic kernels. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1759997/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1759860] Re: Ubuntu MATE Bionic Beaver alpha - Hibernate/Resume Failure - ASUS P8H67-M PRO
Hibernate / Resume from Hibernate: Fresh Ubuntu MATE 18.04 - kernel 4.16.0-041600rc7-lowlatency-> the issue described in this bug report -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1759860 Title: Ubuntu MATE Bionic Beaver alpha - Hibernate/Resume Failure - ASUS P8H67-M PRO Status in linux package in Ubuntu: Confirmed Bug description: Resume from hibernate failed ProblemType: KernelOops DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-13-generic 4.15.0-13.14 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 Annotation: This occurred during a previous hibernation, and prevented the system from resuming properly. ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mihai 1761 F pulseaudio Date: Thu Mar 29 15:35:03 2018 DuplicateSignature: hibernate/resume:System manufacturer System Product Name:3904 ExecutablePath: /usr/share/apport/apportcheckresume Failure: hibernate/resume HibernationDevice: RESUME=UUID=21524dee-cba8-4f0e-8718-07509400c3f8 InstallationDate: Installed on 2018-03-29 (0 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180307.1) InterpreterPath: /usr/bin/python3.6 MachineType: System manufacturer System Product Name ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic root=UUID=47373a65-7f17-4d2d-a006-c7eebce02df4 ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.6, Python 3.6.5rc1, python3-minimal, 3.6.4-1 PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4 RelatedPackageVersions: linux-restricted-modules-4.15.0-13-generic N/A linux-backports-modules-4.15.0-13-generic N/A linux-firmware 1.173 SourcePackage: linux Title: [System manufacturer System Product Name] hibernate/resume failure UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 04/27/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3904 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8H67-M PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3904:bd04/27/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H67-MPRO:rvrRevX.0x: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/1759860/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1759860] Re: Ubuntu MATE Bionic Beaver alpha - Hibernate/Resume Failure - ASUS P8H67-M PRO
Hibernate / Resume from Hibernate: Ubuntu MATE 17.10 - kernel 4.13.0-21-generic -> OK Ubuntu MATE 17.10 - kernel 4.13.0-25-generic -> Resume does not work at all (see https://ubuntuforums.org/showthread.php?t=2382336) Ubuntu MATE 17.10 - kernel 4.15.2 (via ukuu) -> OK Ubuntu MATE 17.10 - kernel 4.15.12 (via ukuu) -> OK Ubuntu MATE 17.10 - kernel 4.15.13 (via ukuu) -> OK Ubuntu MATE 17.10 - kernel 4.15.14 (via ukuu) -> OK Upgrade to Ubuntu MATE 18.04 (from Ubuntu MATE 17.10) - kernel 4.15.0-13-generic -> the issue described in this bug report Upgrade to Ubuntu MATE 18.04 (from Ubuntu MATE 17.10) - kernel 4.15.13 (via ukuu) -> the issue described in this bug report Fresh Ubuntu MATE 18.04 - kernel 4.15.0-13-generic -> the issue described in this bug report Fresh Ubuntu MATE 18.04 - kernel 4.15.14 (via ukuu)-> the issue described in this bug report Fresh Ubuntu MATE 18.04 - kernel 4.15.14 (via ukuu)-> the issue described in this bug report Fresh Ubuntu MATE 18.04 - kernel 4.16-rc6 (via ukuu)-> the issue described in this bug report Fresh Ubuntu MATE 18.04 - kernel 4.16-rc7 (via ukuu)-> the issue described in this bug report Fresh Ubuntu MATE 18.04 - kernel 4.16.0-041600rc7-> the issue described in this bug report ** 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/1759860 Title: Ubuntu MATE Bionic Beaver alpha - Hibernate/Resume Failure - ASUS P8H67-M PRO Status in linux package in Ubuntu: Confirmed Bug description: Resume from hibernate failed ProblemType: KernelOops DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-13-generic 4.15.0-13.14 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 Annotation: This occurred during a previous hibernation, and prevented the system from resuming properly. ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mihai 1761 F pulseaudio Date: Thu Mar 29 15:35:03 2018 DuplicateSignature: hibernate/resume:System manufacturer System Product Name:3904 ExecutablePath: /usr/share/apport/apportcheckresume Failure: hibernate/resume HibernationDevice: RESUME=UUID=21524dee-cba8-4f0e-8718-07509400c3f8 InstallationDate: Installed on 2018-03-29 (0 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180307.1) InterpreterPath: /usr/bin/python3.6 MachineType: System manufacturer System Product Name ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic root=UUID=47373a65-7f17-4d2d-a006-c7eebce02df4 ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.6, Python 3.6.5rc1, python3-minimal, 3.6.4-1 PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4 RelatedPackageVersions: linux-restricted-modules-4.15.0-13-generic N/A linux-backports-modules-4.15.0-13-generic N/A linux-firmware 1.173 SourcePackage: linux Title: [System manufacturer System Product Name] hibernate/resume failure UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 04/27/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3904 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8H67-M PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3904:bd04/27/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H67-MPRO:rvrRevX.0x: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/1759860/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1759860] Re: Ubuntu MATE Bionic Beaver alpha - Hibernate/Resume Failure - ASUS P8H67-M PRO
** Tags added: kernel-bug-exists-upstream -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1759860 Title: Ubuntu MATE Bionic Beaver alpha - Hibernate/Resume Failure - ASUS P8H67-M PRO Status in linux package in Ubuntu: Incomplete Bug description: Resume from hibernate failed ProblemType: KernelOops DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-13-generic 4.15.0-13.14 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 Annotation: This occurred during a previous hibernation, and prevented the system from resuming properly. ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mihai 1761 F pulseaudio Date: Thu Mar 29 15:35:03 2018 DuplicateSignature: hibernate/resume:System manufacturer System Product Name:3904 ExecutablePath: /usr/share/apport/apportcheckresume Failure: hibernate/resume HibernationDevice: RESUME=UUID=21524dee-cba8-4f0e-8718-07509400c3f8 InstallationDate: Installed on 2018-03-29 (0 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180307.1) InterpreterPath: /usr/bin/python3.6 MachineType: System manufacturer System Product Name ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic root=UUID=47373a65-7f17-4d2d-a006-c7eebce02df4 ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.6, Python 3.6.5rc1, python3-minimal, 3.6.4-1 PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4 RelatedPackageVersions: linux-restricted-modules-4.15.0-13-generic N/A linux-backports-modules-4.15.0-13-generic N/A linux-firmware 1.173 SourcePackage: linux Title: [System manufacturer System Product Name] hibernate/resume failure UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 04/27/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3904 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8H67-M PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3904:bd04/27/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H67-MPRO:rvrRevX.0x: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/1759860/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1759828] Re: BUG: Bad page map in process SaveScripts pte:20000000 pmd:56c58a067
dmidecode output from BIOS F22 https://gist.github.com/mettacrawler/ed333ea4349f71c481892fe53eea6039 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1759828 Title: BUG: Bad page map in process SaveScripts pte:2000 pmd:56c58a067 Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Bug description: Note that this is from an AMD Ryzen 5 2600G Also the BIOS firmware is a beta, but the previous version, which is the last so-called stable version is in much worse shape. For instance it misidentifies the RAM as having CAS 19 when it's really CAS 16. The beta BIOS firmware does the job correctly and shows CAS 16. UPDATED: There is a newer BIOS, I'll be updating soon. https://www.gigabyte.com/us/Motherboard/GA-AX370-Gaming-5-rev-10#support-dl ProblemType: KernelOops DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-13-generic 4.15.0-13.14 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ksta 1882 F pulseaudio /dev/snd/controlC2: ksta 1882 F pulseaudio /dev/snd/controlC1: ksta 1882 F pulseaudio Date: Thu Mar 29 07:09:10 2018 Failure: oops InstallationDate: Installed on 2018-03-13 (15 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180311) MachineType: Gigabyte Technology Co., Ltd. AX370-Gaming 5 ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic root=UUID=5a435321-b09d-44ad-a2ca-cfda4521071d ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: kerneloops-daemon N/A RfKill: SourcePackage: linux Title: BUG: Bad page map in process SaveScripts pte:2000 pmd:56c58a067 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/13/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F22b dmi.board.asset.tag: Default string dmi.board.name: AX370-Gaming 5 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF22b:bd02/13/2018:svnGigabyteTechnologyCo.,Ltd.:pnAX370-Gaming5:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAX370-Gaming5:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: AX370-Gaming 5 dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1759828/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1759947] Re: BUG: unable to handle kernel paging request at 0000200000000020
@malachid can you please try booting with: iommu=pt and see if that works? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1759947 Title: BUG: unable to handle kernel paging request at 2020 Status in linux package in Ubuntu: Confirmed Bug description: Unclear what happened. It said chrome was dying, but then nothing including mouse and keyboard worked. ProblemType: KernelOops DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-13-generic 4.15.0-13.14 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 Date: Thu Mar 29 13:56:40 2018 DuplicateSignature: BUG: unable to handle kernel paging request at location RIP: find_get_entry+0x42/0x110 RSP: b73c51c3fbe8 Failure: oops MachineType: System manufacturer System Product Name ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed root=UUID=9320ec1f-aa3c-477d-b5d8-b02d82864086 ro pcie_aspm=off PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: kerneloops-daemon N/A SourcePackage: linux Title: BUG: unable to handle kernel paging request at 2020 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/21/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0902 dmi.board.asset.tag: Default string dmi.board.name: ROG ZENITH EXTREME dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0902:bd12/21/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGZENITHEXTREME:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1759947/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1759828] Re: BUG: Bad page map in process SaveScripts pte:20000000 pmd:56c58a067
I'm on the new BIOS. It requires iommu=pt Even with older kernels like 4.14.31 this computer requires iommu=pt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1759828 Title: BUG: Bad page map in process SaveScripts pte:2000 pmd:56c58a067 Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Bug description: Note that this is from an AMD Ryzen 5 2600G Also the BIOS firmware is a beta, but the previous version, which is the last so-called stable version is in much worse shape. For instance it misidentifies the RAM as having CAS 19 when it's really CAS 16. The beta BIOS firmware does the job correctly and shows CAS 16. UPDATED: There is a newer BIOS, I'll be updating soon. https://www.gigabyte.com/us/Motherboard/GA-AX370-Gaming-5-rev-10#support-dl ProblemType: KernelOops DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-13-generic 4.15.0-13.14 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ksta 1882 F pulseaudio /dev/snd/controlC2: ksta 1882 F pulseaudio /dev/snd/controlC1: ksta 1882 F pulseaudio Date: Thu Mar 29 07:09:10 2018 Failure: oops InstallationDate: Installed on 2018-03-13 (15 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180311) MachineType: Gigabyte Technology Co., Ltd. AX370-Gaming 5 ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic root=UUID=5a435321-b09d-44ad-a2ca-cfda4521071d ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: kerneloops-daemon N/A RfKill: SourcePackage: linux Title: BUG: Bad page map in process SaveScripts pte:2000 pmd:56c58a067 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/13/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F22b dmi.board.asset.tag: Default string dmi.board.name: AX370-Gaming 5 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF22b:bd02/13/2018:svnGigabyteTechnologyCo.,Ltd.:pnAX370-Gaming5:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAX370-Gaming5:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: AX370-Gaming 5 dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1759828/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1756105] Re: X1 Carbon 6th gen S0i3 sleep broken
fyi almost all of the time after suspending it will wake up at some point. but there is an small upside to that; closing/opening lid "works". battery drain is definitely lower during suspend compared to ec_no_wakeup=0 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1756105 Title: X1 Carbon 6th gen S0i3 sleep broken Status in linux package in Ubuntu: Confirmed Bug description: Recent kernel claims S0i3 patch, but this mode is not currently engage "out of the box" on latest patch levels of 18.04. Sleep consumes 2-3 watts instead of 0.1. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1756105/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1751268] Re: bionic desktop does not boot with external monitor attached - [drm:ironlake_crtc_enable [i915]] *ERROR* mode set failed: pipe A stuck / vblank wait timed out on crt
** Changed in: linux Status: Unknown => Confirmed ** Changed in: linux Importance: Unknown => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1751268 Title: bionic desktop does not boot with external monitor attached - [drm:ironlake_crtc_enable [i915]] *ERROR* mode set failed: pipe A stuck / vblank wait timed out on crtc 1 Status in Linux: Confirmed Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Bug description: Ubuntu Desktop Bionic up to date System doesn't boot with an external monitor attached. There is this message in the journal (full journal attached for this boot) fbcon: inteldrmfb (fb0) is primary device [drm:ironlake_crtc_enable [i915]] *ERROR* mode set failed: pipe A stuck vblank wait timed out on crtc 1 [ cut here ] WARNING: CPU: 3 PID: 201 at /build/linux-UKCsxy/linux-4.13.0/drivers/gpu/drm/drm_vblank.c:1090 drm_wait_one_vblank+0x19b/0x1b0 [drm] Modules linked in: hid_lenovo uas usb_storage rtsx_usb_sdmmc rtsx_usb hid_generic usbhid hid i915 mxm_wmi i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops psmouse ahci libahci drm wmi video CPU: 3 PID: 201 Comm: kworker/u8:6 Tainted: G U 4.13.0-32-generic #35-Ubuntu Hardware name: ASUSTeK COMPUTER INC. UX32VD/UX32VD, BIOS UX32VD.214 01/29/2013 Workqueue: events_unbound async_run_entry_fn task: 9760d81cae80 task.stack: b01dc1fb8000 RIP: 0010:drm_wait_one_vblank+0x19b/0x1b0 [drm] RSP: 0018:b01dc1fbb7c8 EFLAGS: 00010282 RAX: 001f RBX: 9760d708 RCX: RDX: RSI: 0002 RDI: 0246 RBP: b01dc1fbb828 R08: 001f R09: 0002af84 R10: b01dc1fbb7c8 R11: 041b R12: 0001 R13: 0170 R14: 0001 R15: FS: () GS:9760eef8() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: 7f156d6d68f0 CR3: 00024660a002 CR4: 001606e0 Call Trace: ? wait_woken+0x80/0x80 ironlake_crtc_enable+0x477/0xc00 [i915] ? gen6_write8+0x190/0x190 [i915] intel_update_crtc+0x4b/0xe0 [i915] intel_update_crtcs+0x5b/0x80 [i915] intel_atomic_commit_tail+0x254/0xf90 [i915] ? __schedule+0x293/0x880 intel_atomic_commit+0x3d5/0x490 [i915] ? drm_atomic_check_only+0x37b/0x540 [drm] drm_atomic_commit+0x4b/0x50 [drm] restore_fbdev_mode+0x15e/0x270 [drm_kms_helper] drm_fb_helper_restore_fbdev_mode_unlocked+0x2e/0x80 [drm_kms_helper] drm_fb_helper_set_par+0x2d/0x60 [drm_kms_helper] intel_fbdev_set_par+0x1a/0x70 [i915] fbcon_init+0x484/0x650 visual_init+0xd6/0x130 do_bind_con_driver+0x1fc/0x410 do_take_over_console+0x82/0x1a0 do_fbcon_takeover+0x5c/0xb0 fbcon_event_notify+0x587/0x780 notifier_call_chain+0x4a/0x70 blocking_notifier_call_chain+0x43/0x60 fb_notifier_call_chain+0x1b/0x20 register_framebuffer+0x24d/0x360 drm_fb_helper_initial_config+0x249/0x400 [drm_kms_helper] intel_fbdev_initial_config+0x18/0x30 [i915] async_run_entry_fn+0x36/0x150 process_one_work+0x1e7/0x410 worker_thread+0x4b/0x420 kthread+0x125/0x140 ? process_one_work+0x410/0x410 ? kthread_create_on_node+0x70/0x70 ret_from_fork+0x1f/0x30 Code: ff e8 da 3b 4c d6 48 8b 7d a0 48 8d 75 a8 e8 dd 93 50 d6 45 85 ff 0f 85 0c ff ff ff 44 89 e6 48 c7 c7 d8 eb 3d c0 e8 b6 46 52 d6 <0f> ff e9 f6 fe ff ff 0f 1f 40 00 66 2e 0f 1f 84 00 00 00 00 00 ---[ end trace a1db7ccd0b5e4dfc ]--- ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-10-generic 4.15.0-10.11 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: j-lallement 3671 F pulseaudio /dev/snd/controlC0: j-lallement 3671 F pulseaudio /dev/snd/controlC1: j-lallement 3671 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Feb 23 13:58:39 2018 InstallationDate: Installed on 2013-09-03 (1633 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902) MachineType: ASUSTeK COMPUTER INC. UX32VD ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic root=UUID=1004226d-a9db-46c7-bd28-eca0806c12f2 ro pcie_aspm=force drm.vblankoffdelay=1 i915.semaphores=1 init=/lib/systemd/systemd-bootchart RelatedPackageVersions: linux-restricted-modules-4.15.0-10-generic N/A linux-backports-modules-4.15.0-10-generic N/A linux-firmware
[Kernel-packages] [Bug 1749961] Re: xhci_hcd: TRB DMA errors reported with ASMedia ASM1142 USB 3.1 Controller
Wow Imperia, you're being really helpful here, thank you very much! To enable traces, these are the instructions I've provided to other people affected so far: 0) Reboot the machine in order to put it in a consistent state; 1) echo "module xhci_hcd +flpt" > /sys/kernel/debug/dynamic_debug/control 2) echo nop > /sys/kernel/debug/tracing/current_tracer 3) echo 81920 > /sys/kernel/debug/tracing/buffer_size_kb 4) echo 0 > /sys/kernel/debug/tracing/trace 5) echo 1 > /sys/kernel/debug/tracing/tracing_on 6) echo 1 > /sys/kernel/debug/tracing/events/xhci-hcd/enable After reproduce the issue, you should collect /sys/kernel/debug/tracing/trace. Problem is that the file might be huge, much larger than the kernel log you provided for instance. About the SSH access, I'm interested in getting it next week, if it doesn't annoy you too much. It'll be really helpful, but I might need to reboot the machine. Oh, I've downloaded the logs from your website, so you can delete it now. Cheers, Guilherme -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1749961 Title: xhci_hcd: TRB DMA errors reported with ASMedia ASM1142 USB 3.1 Controller Status in linux package in Ubuntu: In Progress Status in linux source package in Trusty: In Progress Status in linux source package in Xenial: In Progress Status in linux source package in Artful: In Progress Status in linux source package in Bionic: In Progress Status in linux package in Debian: New Bug description: It was observed that while trying to use a 4K USB webcam connected to USB port provided by ASMedia ASM1142 USB 3.1 Controller, the webcam does not work and kernel log shows the following messages: [431.928016] xhci_hcd :12:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13 [431.928021] xhci_hcd :12:00.0: Looking for event-dma 003f3330e020 trb-start 003f3330e000 trb-end 003f3330e000 seg-start 003f3330e000 seg-end 003f3330eff0 [431.928024] xhci_hcd :12:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13 [431.928026] xhci_hcd :12:00.0: Looking for event-dma 003f3330e030 trb-start 003f3330e000 trb-end 003f3330e000 seg-start 003f3330e000 seg-end 003f3330eff0 [431.928027] xhci_hcd :12:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13 [431.928029] xhci_hcd :12:00.0: Looking for event-dma 003f3330e050 trb-start 003f3330e000 trb-end 003f3330e000 seg-start 003f3330e000 seg-end 003f3330eff0 [431.928386] xhci_hcd :12:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13 A similar issue was already reported on Launchpad: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1667750 The fix to this issue seems to be the following patch: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=9da5a109 Tests in our scenario with this patch proved still broken. Our next approach is to modify the patch a bit and re-test. This LP will be used to document our progress in the investigation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1749961/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1759920] Re: linux-image-4.13.0-37-generic locks up at login screen with intel-microcode 3.20180312.0
I'm having the same problem. 4.13.0-36-generic works, 4.13.0-37-generic freezes up before I can log in. I have a 2nd generation core i7 and AMD graphics. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1759920 Title: linux-image-4.13.0-37-generic locks up at login screen with intel- microcode 3.20180312.0 Status in intel-microcode package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in intel-microcode source package in Artful: Confirmed Status in linux source package in Artful: Confirmed Bug description: I don't know if this is a problem with the kernel or the microcode, but we have a significant number of computers in our organization (on both 16.04 and 17.10) that fail if they have both updated. Booting with either linux-image-4.13.0-36-generic or intel-microcode 3.20180108.0+really20170707ubuntu17.10.1 allows all these computers to boot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1759920/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1759961] [NEW] Update to 5.49 in Bionic (mostly bug-fix release)
Public bug reported: >From upstream: http://www.bluez.org/release-of-bluez-5-49/ Release of BlueZ 5.49 This is mostly a bug fix release, with fixes to features such as AVCTP, OBEX, GATT and Mesh. There are however some notable new features also, such as improved heartbeat management support in meshctl as well as a new experimental ConnectDevice D-Bus method on the Adapter interface, which can be used for quick device object creation for testing purpose or when information about the device has been received over some Out-of- Band channel. Upstream changelog: https://git.kernel.org/pub/scm/bluetooth/bluez.git/tree/ChangeLog ver 5.49: Fix issue with configuring discoverable advertising flag. Fix issue with bearer selection and single mode controllers. Fix issue with Connect and ConnectProfile returning in progress. Fix issue with missing Paired property change when not bonded. Fix issue with storage for controllers without public address. Fix issue with handling AVCTP disconnecting the channel queue. Fix issue with not clearing connectable setting on power off. Fix issue with creating multiple mgmt socket instances. Fix issue with GATT server and BR/EDR only devices. Fix issue with InterfaceAdded event ordering. Add support for generic ConnectDevice method call. Add support for Mesh heartbeat client functionality. ** Affects: bluez (Ubuntu) Importance: Undecided Status: New -- 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/1759961 Title: Update to 5.49 in Bionic (mostly bug-fix release) Status in bluez package in Ubuntu: New Bug description: From upstream: http://www.bluez.org/release-of-bluez-5-49/ Release of BlueZ 5.49 This is mostly a bug fix release, with fixes to features such as AVCTP, OBEX, GATT and Mesh. There are however some notable new features also, such as improved heartbeat management support in meshctl as well as a new experimental ConnectDevice D-Bus method on the Adapter interface, which can be used for quick device object creation for testing purpose or when information about the device has been received over some Out-of-Band channel. Upstream changelog: https://git.kernel.org/pub/scm/bluetooth/bluez.git/tree/ChangeLog ver 5.49: Fix issue with configuring discoverable advertising flag. Fix issue with bearer selection and single mode controllers. Fix issue with Connect and ConnectProfile returning in progress. Fix issue with missing Paired property change when not bonded. Fix issue with storage for controllers without public address. Fix issue with handling AVCTP disconnecting the channel queue. Fix issue with not clearing connectable setting on power off. Fix issue with creating multiple mgmt socket instances. Fix issue with GATT server and BR/EDR only devices. Fix issue with InterfaceAdded event ordering. Add support for generic ConnectDevice method call. Add support for Mesh heartbeat client functionality. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1759961/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1758910] Comment bridged from LTC Bugzilla
--- Comment From cha...@us.ibm.com 2018-03-29 18:11 EDT--- *** Bug 165741 has been marked as a duplicate of this bug. *** -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1758910 Title: Important Kernel fixes to be backported for Power9 (kvm) Status in The Ubuntu-power-systems project: Triaged Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Bug description: == Comment: #0 - Satheesh Rajendran - 2018-03-26 02:18:44 == ---Problem Description--- Important Kernel fixes to be backported for Power9 (kvm) Contact Information = sathe...@in.ibm.com ---uname output--- 4.15.0-13-generic Machine Type = power9 boston 2.2 (pvr 004e 1202) ---Debugger--- A debugger is not configured ---Steps to Reproduce--- Following upstream patches are need to be backported for Power9 KVM to function well. * Emulation of VMX loads and stores for MMIO. 09f984961c13 KVM: PPC: Book3S: Add MMIO emulation for VMX instructions 6df3877fc962 KVM: PPC: Book3S: Fix compile error that occurs with some gcc versions (needed once 09f984961c13 is in) * Other important fixes. 05f2bb0313a2 KVM: PPC: Book3S HV: Fix handling of secondary HPTEG in HPT resizing code 790a9df5fbef KVM: PPC: Book3S HV: Make HPT resizing work on POWER9 a8b48a4dccea KVM: PPC: Book3S HV: Fix trap number return from __kvmppc_vcore_entry https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=fixes&id=ff6781fd1bb404d8a551c02c35c70cec1da17ff1 https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=fixes&id=e4b79900222b8cccd4da4a7a89581f0e1b764ed2 and https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=fixes&id=a5d4b5891c2f1f865a2def1eb0030f534e77ff86 Stack trace output: no Oops output: no System Dump Info: The system is not configured to capture a system dump. *Additional Instructions for sathe...@in.ibm.com: -Attach sysctl -a output output to the bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1758910/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1759865] Re: general protection fault: 0000 [#1] SMP NOPTI
The first step in trying the other kernel was to disable the nvidia driver. I have switched it to nouveau and am letting it run for a little to see if that makes any difference before I swap out the kernel. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1759865 Title: general protection fault: [#1] SMP NOPTI Status in linux package in Ubuntu: Incomplete Bug description: I was using chrome and saw the update-notifier warn me of "" Went to the command line to try to figure out what the problem was. Most commands just core dumped (including apt and su) however I was able to get this from dmesg [ 693.573723] cron[5576]: segfault at 7fff196473d0 ip 7fff196473d0 sp 7fff19645a80 error 15 [ 695.126425] phpquery[5587]: segfault at 7ffd0388c258 ip 56454f0e4650 sp 7ffd0388a180 error 6 in dash[56454f0d2000+1c000] [ 695.234845] phpquery[5591]: segfault at 7ffd0388c258 ip 56454f0e4650 sp 7ffd0388a180 error 6 in dash[56454f0d2000+1c000] [ 695.343616] phpquery[5589]: segfault at 7ffd0388c258 ip 56454f0e4650 sp 7ffd0388a180 error 6 in dash[56454f0d2000+1c000] [ 695.452099] phpquery[5585]: segfault at 7ffd0388c258 ip 56454f0e4650 sp 7ffd0388a180 error 6 in dash[56454f0d2000+1c000] [ 695.583528] sessionclean[5598]: segfault at 7ffc09ce50e8 ip 55936e2f0650 sp 7ffc09ce3010 error 6 in dash[55936e2de000+1c000] [ 695.692891] sessionclean[5597]: segfault at 7ffc09ce50e8 ip 55936e2f0650 sp 7ffc09ce3010 error 6 in dash[55936e2de000+1c000] [ 695.801617] sessionclean[5581]: segfault at 7ffc09ce50e8 ip 55936e2f0650 sp 7ffc09ce3010 error 6 in dash[55936e2de000+1c000] [ 695.904212] sessionclean[5584]: segfault at 7ffc09ce50e8 ip 55936e2f0650 sp 7ffc09ce3010 error 6 in dash[55936e2de000+1c000] [ 696.013519] sessionclean[5580]: segfault at 7ffc09ce50e8 ip 55936e2f0650 sp 7ffc09ce3010 error 6 in dash[55936e2de000+1c000] [ 696.695912] systemd: 35 output lines suppressed due to ratelimiting [ 769.048253] systemd-journald[545]: Failed to send WATCHDOG=1 notification message: Connection refused [ 828.941426] systemd-journald[545]: Failed to send WATCHDOG=1 notification message: Transport endpoint is not connected [ 908.937238] systemd-journald[545]: Failed to send WATCHDOG=1 notification message: Transport endpoint is not connected [ 999.871627] systemd-journald[545]: Failed to send WATCHDOG=1 notification message: Transport endpoint is not connected [ 1005.962536] systemd-journald[545]: Failed to send WATCHDOG=1 notification message: Transport endpoint is not connected [ 1005.975570] show_signal_msg: 1 callbacks suppressed [ 1005.975573] which[6212]: segfault at 7ffeadceb8a8 ip 55d161a5e650 sp 7ffeadce97d0 error 6 in dash[55d161a4c000+1c000] [ 1006.089011] which[6218]: segfault at 7fff2ad5e448 ip 561b807f8650 sp 7fff2ad5c370 error 6 in dash[561b807e6000+1c000] [ 1006.219235] which[6223]: segfault at 7ffcee0a0118 ip 5621a961f650 sp 7ffcee09e040 error 6 in dash[5621a960d000+1c000] [ 1006.343970] which[6228]: segfault at 7ffc9fda2948 ip 55b0a1fb5650 sp 7ffc9fda0870 error 6 in dash[55b0a1fa3000+1c000] [ 1006.472231] which[6234]: segfault at 7ffc991e4528 ip 555b82672650 sp 7ffc991e2450 error 6 in dash[555b8266+1c000] [ 1006.597085] which[6240]: segfault at 7fff395ec008 ip 5652da3aa650 sp 7fff395e9f30 error 6 in dash[5652da398000+1c000] [ 1008.042333] idea_tmp_check.[6414]: segfault at 7ffd634cb518 ip 5633b025e650 sp 7ffd634c9440 error 6 in dash[5633b024c000+1c000] ProblemType: KernelOops DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-13-generic 4.15.0-13.14 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 Date: Thu Mar 29 06:49:08 2018 Failure: oops MachineType: System manufacturer System Product Name ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed root=UUID=9320ec1f-aa3c-477d-b5d8-b02d82864086 ro pcie_aspm=off PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: kerneloops-daemon N/A SourcePackage: linux Title: general protection fault: [#1] SMP NOPTI UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/21/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0902 dmi.board.asset.tag: Default string dmi.board.name: ROG ZENITH EXTREME dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: De
[Kernel-packages] [Bug 1759920] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1759920/+attachment/5095364/+files/Dependencies.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/1759920 Title: linux-image-4.13.0-37-generic locks up at login screen with intel- microcode 3.20180312.0 Status in intel-microcode package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in intel-microcode source package in Artful: Confirmed Status in linux source package in Artful: Confirmed Bug description: I don't know if this is a problem with the kernel or the microcode, but we have a significant number of computers in our organization (on both 16.04 and 17.10) that fail if they have both updated. Booting with either linux-image-4.13.0-36-generic or intel-microcode 3.20180108.0+really20170707ubuntu17.10.1 allows all these computers to boot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1759920/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1759920] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1759920/+attachment/5095366/+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/1759920 Title: linux-image-4.13.0-37-generic locks up at login screen with intel- microcode 3.20180312.0 Status in intel-microcode package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in intel-microcode source package in Artful: Confirmed Status in linux source package in Artful: Confirmed Bug description: I don't know if this is a problem with the kernel or the microcode, but we have a significant number of computers in our organization (on both 16.04 and 17.10) that fail if they have both updated. Booting with either linux-image-4.13.0-36-generic or intel-microcode 3.20180108.0+really20170707ubuntu17.10.1 allows all these computers to boot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1759920/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1759920] Re: linux-image-4.13.0-37-generic locks up at login screen with intel-microcode 3.20180312.0
ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.13.0-37.42~16.04.1-generic 4.13.13 Tags: xenial Uname: Linux 4.13.0-37-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: Domain Users adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True ** 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/1759920 Title: linux-image-4.13.0-37-generic locks up at login screen with intel- microcode 3.20180312.0 Status in intel-microcode package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in intel-microcode source package in Artful: Confirmed Status in linux source package in Artful: Confirmed Bug description: I don't know if this is a problem with the kernel or the microcode, but we have a significant number of computers in our organization (on both 16.04 and 17.10) that fail if they have both updated. Booting with either linux-image-4.13.0-36-generic or intel-microcode 3.20180108.0+really20170707ubuntu17.10.1 allows all these computers to boot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1759920/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1759920] JournalErrors.txt
apport information ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1759920/+attachment/5095365/+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/1759920 Title: linux-image-4.13.0-37-generic locks up at login screen with intel- microcode 3.20180312.0 Status in intel-microcode package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in intel-microcode source package in Artful: Confirmed Status in linux source package in Artful: Confirmed Bug description: I don't know if this is a problem with the kernel or the microcode, but we have a significant number of computers in our organization (on both 16.04 and 17.10) that fail if they have both updated. Booting with either linux-image-4.13.0-36-generic or intel-microcode 3.20180108.0+really20170707ubuntu17.10.1 allows all these computers to boot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1759920/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1759920] Re: linux-image-4.13.0-37-generic locks up at login screen with intel-microcode 3.20180312.0
Booting with 4.13.0-36-generic prevented computer lockup during startup. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1759920 Title: linux-image-4.13.0-37-generic locks up at login screen with intel- microcode 3.20180312.0 Status in intel-microcode package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in intel-microcode source package in Artful: Confirmed Status in linux source package in Artful: Confirmed Bug description: I don't know if this is a problem with the kernel or the microcode, but we have a significant number of computers in our organization (on both 16.04 and 17.10) that fail if they have both updated. Booting with either linux-image-4.13.0-36-generic or intel-microcode 3.20180108.0+really20170707ubuntu17.10.1 allows all these computers to boot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1759920/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1759920] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1759920/+attachment/5095367/+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/1759920 Title: linux-image-4.13.0-37-generic locks up at login screen with intel- microcode 3.20180312.0 Status in intel-microcode package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in intel-microcode source package in Artful: Confirmed Status in linux source package in Artful: Confirmed Bug description: I don't know if this is a problem with the kernel or the microcode, but we have a significant number of computers in our organization (on both 16.04 and 17.10) that fail if they have both updated. Booting with either linux-image-4.13.0-36-generic or intel-microcode 3.20180108.0+really20170707ubuntu17.10.1 allows all these computers to boot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1759920/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1754584] Re: zfs system process hung on container stop/delete
One requires both the user space and the kernel packages to be installed, so please re-test when the kernel also appears in -proposed. Apologies for the confusion. -- 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/1754584 Title: zfs system process hung on container stop/delete Status in Native ZFS for Linux: New Status in linux package in Ubuntu: Fix Committed Status in zfs-linux package in Ubuntu: Fix Released Status in linux source package in Xenial: In Progress Status in zfs-linux source package in Xenial: Fix Committed Status in linux source package in Artful: In Progress Status in zfs-linux source package in Artful: Fix Committed Status in linux source package in Bionic: Fix Committed Status in zfs-linux source package in Bionic: Fix Released Bug description: == SRU Request [Xenial][Artful] == == Justification == It is possible to hang zfs asynchronous reads if a read to a page that is mmap'd onto the the file being read is the same offset in the mapping as in the file. This is caused by two lock operations on the page. == Fix == Upstream ZFS fix to ensure the page is not double-locked during async I/O of one or more pages. == Testing == Create a zfs pool + zfs file system, run the reproducer program in comment #28 on the zfs filesystem. Without the fix this can lock up, with the fix this runs to completion. == Regression Potential == Minimal, the locking fix addresses a fundamental bug in the locking and this should not affect ZFS read/write I/O with this fix. -- Summary: On a Bionic system running 4.15.0-10-generic, after attempting to build libaio in a Bionic daily container I cannot stop or delete the container. dmesg shows a variety of hung tasks Steps to Reproduce: Use the following script and watch for the the hang. At that point attempt to stop or delete the container: http://paste.ubuntu.com/p/SxfgbxM8v7/ Originally filed against LXD: https://github.com/lxc/lxd/issues/4314 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-10-generic 4.15.0-10.11 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: powersj2414 F pulseaudio /dev/snd/controlC0: powersj2414 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Mar 9 09:19:11 2018 HibernationDevice: RESUME=UUID=40a4eb28-4454-44f0-a377-ea611ce685bb InstallationDate: Installed on 2018-02-19 (17 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214) Lsusb: Bus 001 Device 002: ID 8087:8001 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 002: ID 04f2:b45d Chicony Electronics Co., Ltd Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20BSCTO1WW 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=/vmlinuz-4.15.0-10-generic root=/dev/mapper/ubuntu--vg-root ro RelatedPackageVersions: linux-restricted-modules-4.15.0-10-generic N/A linux-backports-modules-4.15.0-10-generic N/A linux-firmware 1.172 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/13/2017 dmi.bios.vendor: LENOVO dmi.bios.version: N14ET42W (1.20 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BSCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0E50512 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN14ET42W(1.20):bd09/13/2017:svnLENOVO:pn20BSCTO1WW:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BSCTO1WW:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 3rd dmi.product.name: 20BSCTO1WW dmi.product.version: ThinkPad X1 Carbon 3rd dmi.sys.vendor: LENOVO --- ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: powersj1878 F pulseaudio /dev/snd/controlC0: powersj1878 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=40a4eb28-4454-44f0-a377-ea611ce685bb InstallationDate: Installed on 2018-02-19 (17 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214)
[Kernel-packages] [Bug 1756877] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1756877/+attachment/5095322/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1756877 Title: High visual latency in 18.04 when using nouveau Status in linux package in Ubuntu: Confirmed Bug description: I am on an Dell xps 9530 laptop and I had recently cleaned installed 17.10. A few days back I decided to updated to 18.04 to check it out and report some bugs. The most annoying bug so far is the insane amount of input latency this update has brought with it to a degree that it makes it impossible to be productive. The issue is observable when using either the mouse or the keyboard. The mouse does not move immediately but it needs a second or two to register and start moving and even then at some point it freezes for half a second at some random point and then moves again. Also if I have two applications side by side and I try an move focus from one to the next at around the edges of each window the mouse freezes for a second and then moves. The keyboard freezes if it hasn't been used for a while and on the first keystroke will take a second to register and for a bonus you get the first keystorke repeated for around 15-30 times. So if you are trying to write "and" will become "aaand" or pressing "ctrl + T" in the browser will open not one but 20 tabs! I am reporting it here cause I am not sure what is causing all this latency (it could be libinput or something else entirely) but please try and fix this as soon as possible!! ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Mar 19 13:04:05 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-02-14 (32 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) SourcePackage: gnome-shell UpgradeStatus: Upgraded to bionic on 2018-03-15 (3 days ago) --- ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: giannissc 2031 F pulseaudio /dev/snd/pcmC1D0p: giannissc 2031 F...m pulseaudio /dev/snd/controlC1: giannissc 2031 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=999e9885-dbd2-4a45-a45f-998e322f32dc InstallationDate: Installed on 2018-03-26 (2 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180325) MachineType: Dell Inc. XPS 15 9530 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-13-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 RelatedPackageVersions: linux-restricted-modules-4.15.0-13-generic N/A linux-backports-modules-4.15.0-13-generic N/A linux-firmware 1.173 Tags: wayland-session bionic Uname: Linux 4.15.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/08/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: XPS 15 9530 dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA08:bd01/08/2015:svnDellInc.:pnXPS159530:pvrA08:rvnDellInc.:rnXPS159530:rvrA08:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: XPS 15 9530 dmi.product.version: A08 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1756877/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1756877] Re: High visual latency in 18.04 when using nouveau
I am not so sure but as I understand it running the nvidia driver does not allow to use the integrated intel graphics to run and always the higher power consumption nvidia gpu. And that is why the laptop runs the fans all the time and is warmer because it cannot switch between the two to minimize the consumption. But I must admit that I havent actually measured anything so it could just be my idea. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1756877 Title: High visual latency in 18.04 when using nouveau Status in linux package in Ubuntu: Confirmed Bug description: I am on an Dell xps 9530 laptop and I had recently cleaned installed 17.10. A few days back I decided to updated to 18.04 to check it out and report some bugs. The most annoying bug so far is the insane amount of input latency this update has brought with it to a degree that it makes it impossible to be productive. The issue is observable when using either the mouse or the keyboard. The mouse does not move immediately but it needs a second or two to register and start moving and even then at some point it freezes for half a second at some random point and then moves again. Also if I have two applications side by side and I try an move focus from one to the next at around the edges of each window the mouse freezes for a second and then moves. The keyboard freezes if it hasn't been used for a while and on the first keystroke will take a second to register and for a bonus you get the first keystorke repeated for around 15-30 times. So if you are trying to write "and" will become "aaand" or pressing "ctrl + T" in the browser will open not one but 20 tabs! I am reporting it here cause I am not sure what is causing all this latency (it could be libinput or something else entirely) but please try and fix this as soon as possible!! ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Mar 19 13:04:05 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-02-14 (32 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) SourcePackage: gnome-shell UpgradeStatus: Upgraded to bionic on 2018-03-15 (3 days ago) --- ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: giannissc 2031 F pulseaudio /dev/snd/pcmC1D0p: giannissc 2031 F...m pulseaudio /dev/snd/controlC1: giannissc 2031 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=999e9885-dbd2-4a45-a45f-998e322f32dc InstallationDate: Installed on 2018-03-26 (2 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180325) MachineType: Dell Inc. XPS 15 9530 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-13-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 RelatedPackageVersions: linux-restricted-modules-4.15.0-13-generic N/A linux-backports-modules-4.15.0-13-generic N/A linux-firmware 1.173 Tags: wayland-session bionic Uname: Linux 4.15.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/08/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: XPS 15 9530 dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA08:bd01/08/2015:svnDellInc.:pnXPS159530:pvrA08:rvnDellInc.:rnXPS159530:rvrA08:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: XPS 15 9530 dmi.product.version: A08 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1756877/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1756877] Re: High visual latency in 18.04 when using nouveau
If this is just an output latency issue why would trying to write or use a shortcut result in a key being registered as being pressed multiple times? Example is pressing 'Ctrl' + 'T' for a new tab and opening 20 more tabs or writing 'and' and resulting in 'aand' -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1756877 Title: High visual latency in 18.04 when using nouveau Status in linux package in Ubuntu: Confirmed Bug description: I am on an Dell xps 9530 laptop and I had recently cleaned installed 17.10. A few days back I decided to updated to 18.04 to check it out and report some bugs. The most annoying bug so far is the insane amount of input latency this update has brought with it to a degree that it makes it impossible to be productive. The issue is observable when using either the mouse or the keyboard. The mouse does not move immediately but it needs a second or two to register and start moving and even then at some point it freezes for half a second at some random point and then moves again. Also if I have two applications side by side and I try an move focus from one to the next at around the edges of each window the mouse freezes for a second and then moves. The keyboard freezes if it hasn't been used for a while and on the first keystroke will take a second to register and for a bonus you get the first keystorke repeated for around 15-30 times. So if you are trying to write "and" will become "aaand" or pressing "ctrl + T" in the browser will open not one but 20 tabs! I am reporting it here cause I am not sure what is causing all this latency (it could be libinput or something else entirely) but please try and fix this as soon as possible!! ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Mar 19 13:04:05 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-02-14 (32 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) SourcePackage: gnome-shell UpgradeStatus: Upgraded to bionic on 2018-03-15 (3 days ago) --- ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: giannissc 2031 F pulseaudio /dev/snd/pcmC1D0p: giannissc 2031 F...m pulseaudio /dev/snd/controlC1: giannissc 2031 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=999e9885-dbd2-4a45-a45f-998e322f32dc InstallationDate: Installed on 2018-03-26 (2 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180325) MachineType: Dell Inc. XPS 15 9530 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-13-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 RelatedPackageVersions: linux-restricted-modules-4.15.0-13-generic N/A linux-backports-modules-4.15.0-13-generic N/A linux-firmware 1.173 Tags: wayland-session bionic Uname: Linux 4.15.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/08/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: XPS 15 9530 dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA08:bd01/08/2015:svnDellInc.:pnXPS159530:pvrA08:rvnDellInc.:rnXPS159530:rvrA08:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: XPS 15 9530 dmi.product.version: A08 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1756877/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1759893] Re: [18.04][config] regression: nvme and nvme_core couldn't be built as modules starting 4.15-rc2
** Tags added: patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1759893 Title: [18.04][config] regression: nvme and nvme_core couldn't be built as modules starting 4.15-rc2 Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Bug description: Some regression was introduced into NVME-related kernel configuration by 32c662c58a9b9 into 4.15-rc2, which was pulled later into ubuntu- bionic.git In result, "nvme" and "nvme_core" drivers are built into the kernel, we can't build them as modules. It caused incompatibility of NMVe-OF target and initiator modules (nvmet, nvme-rdma) installed by Mellanox OFED with the inbox "nvme" driver. Root cause analysis. In the drivers/lightnvm/Kconfig file - kernel configuration for the OpenChannel SSDs (lightnvm) we have: menuconfig NVM bool "Open-Channel SSD target support" depends on BLOCK && HAS_DMA && PCI select BLK_DEV_NVME help Say Y here to get to enable Open-channel SSDs. ... It means that BLK_DEV_NVME is selected to "y" when NVM (CONFIG_NVM) is selected. NVM parameter is 2 state (on / off, i.e. "y" or "no"), it couldn't be built as a module. So that it triggers the change of BLK_DEV_NAME=y and NVME_CORE=y $ git blame drivers/lightnvm/Kconfig 32c662c58a9b9 (Rakesh Pandit 2017-10-13 14:45:55 +0200 7)depends on BLOCK && HAS_DMA && PCI 32c662c58a9b9 (Rakesh Pandit 2017-10-13 14:45:55 +0200 8)select BLK_DEV_NVME commit 32c662c58a9b9d0c99e713a14ca323a9a91c73a0 Author: Rakesh Pandit Date: Fri Oct 13 14:45:55 2017 +0200 lightnvm: include NVM Express driver if OCSSD is selected for build Because NVM needs BLK_DEV_NVME, select it automatically if we mark NVM in config file before building kernel. Also append PCI to depends as select doesn't automatically add dependencies. Signed-off-by: Rakesh Pandit Signed-off-by: Matias Bjørling Signed-off-by: Jens Axboe drivers/lightnvm/Kconfig | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) $ git diff 32c662c58a9b9^1..32c662c58a9b9 diff --git a/drivers/lightnvm/Kconfig b/drivers/lightnvm/Kconfig index ead61a93cb4e..2a953efec4e1 100644 --- a/drivers/lightnvm/Kconfig +++ b/drivers/lightnvm/Kconfig @@ -4,7 +4,8 @@ menuconfig NVM bool "Open-Channel SSD target support" - depends on BLOCK && HAS_DMA + depends on BLOCK && HAS_DMA && PCI + select BLK_DEV_NVME help Say Y here to get to enable Open-channel SSDs. Proposed fix is following: diff --git a/drivers/lightnvm/Kconfig b/drivers/lightnvm/Kconfig index 2a953efec4e1..9969236314d7 100644 --- a/drivers/lightnvm/Kconfig +++ b/drivers/lightnvm/Kconfig @@ -4,8 +4,7 @@ menuconfig NVM bool "Open-Channel SSD target support" - depends on BLOCK && HAS_DMA && PCI - select BLK_DEV_NVME + depends on BLOCK && HAS_DMA && PCI && BLK_DEV_NVME help Say Y here to get to enable Open-channel SSDs. Regards, Yurii Shestakov --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 29 17:05 seq crw-rw 1 root audio 116, 33 Mar 29 17:05 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu1 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: DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=/dev/mapper/vg2-swap_1 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: QEMU Standard PC (Q35 + ICH9, 2009) Package: linux (not installed) PciMultimedia: ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic root=/dev/mapper/vg2-root ro net.ifnames=0 biosdevname=0 quiet nofb nomodeset console=ttyS0,115200n8 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 RelatedPackageVersions: linux-restricted-modules-4.15.0-10-generic N/A linux-backports-modules-4.15.0-10-generic N/A linux-firmware 1.173 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux 4.15.0-10-generic x86_64 UnreportableReason: The report belongs to a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: False dmi.bios.date: 01/01/2011 dmi.bios.vendor: Seabios dmi.bios.version: 0.5.1 dmi.chassis.type: 1 dmi.chassis
[Kernel-packages] [Bug 1759947] 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/1759947 Title: BUG: unable to handle kernel paging request at 2020 Status in linux package in Ubuntu: Confirmed Bug description: Unclear what happened. It said chrome was dying, but then nothing including mouse and keyboard worked. ProblemType: KernelOops DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-13-generic 4.15.0-13.14 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 Date: Thu Mar 29 13:56:40 2018 DuplicateSignature: BUG: unable to handle kernel paging request at location RIP: find_get_entry+0x42/0x110 RSP: b73c51c3fbe8 Failure: oops MachineType: System manufacturer System Product Name ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed root=UUID=9320ec1f-aa3c-477d-b5d8-b02d82864086 ro pcie_aspm=off PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: kerneloops-daemon N/A SourcePackage: linux Title: BUG: unable to handle kernel paging request at 2020 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/21/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0902 dmi.board.asset.tag: Default string dmi.board.name: ROG ZENITH EXTREME dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0902:bd12/21/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGZENITHEXTREME:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1759947/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1758507] Re: sky2 gigabit ethernet driver sometimes stops working after lid-open resume from sleep (88E8055)
Well this is odd... I tried following the instructions on PM tracing from https://wiki.ubuntu.com/DebuggingKernelSuspend (using systemctl suspend instead of pm-suspend), but the system hangs on resume when tracing is enabled - and this happens also when pm_test is set to "devices" (doesn't happen with "freezer"). There is no hang when tracing full suspend on 4.8.0. ** Attachment added: "pm_trace of boot after hang with pm_test=devices" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1758507/+attachment/5095301/+files/dmesg-4.16-rc7-test-devices-fail.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/1758507 Title: sky2 gigabit ethernet driver sometimes stops working after lid-open resume from sleep (88E8055) Status in linux package in Ubuntu: Confirmed Bug description: After resuming from sleep using the lid-open event, OFTEN (60% replicable, usually after 2nd or later resume) the NIC is not functional, and reloading the sky2 module does not help. Relevant parts from dmesg: [ 582.852065] sky2 :04:00.0: Refused to change power state, currently in D3 ... [ 827.613729] sky2 :04:00.0: ignoring stuck error report bit [ 827.613748] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613750] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613752] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613754] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613756] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613759] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613761] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613763] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613765] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613767] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613769] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613772] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613774] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613776] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613778] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613780] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613782] sky2 :04:00.0: enp4s0: phy I/O error And after reloading the module: [ 1421.781480] sky2: driver version 1.30 [ 1421.781533] sky2 :04:00.0: enabling device ( -> 0003) [ 1421.781667] sky2 :04:00.0: unsupported chip type 0xff [ 1421.782292] sky2: probe of :04:00.0 failed with error -95 Possibly relevant: [ 1235.944086] ACPI: button: The lid device is not compliant to SW_LID. Replicability: When it happens once, further suspend-resume cycles (tried ~5) don't fix it. Reboot fixes the NIC, and it often survives first resume after that, but 1-2 suspend-resume cycles later the issue WILL occur again. Per-boot chance of encountering the issue - so far 2/5. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-12-generic 4.15.0-12.13 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-12-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Date: Sat Mar 24 09:54:10 2018 HibernationDevice: RESUME=UUID=02d18685-fc92-4ebe-a43e-34d1e52a26b1 InstallationDate: Installed on 2018-03-21 (3 days ago) InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180319) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: FUJITSU SIEMENS ESPRIMO Mobile U9200 ProcEnviron: LANGUAGE=en_US:en TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic root=UUID=bc171dce-b703-44f6-8244-22b6b3b1dc33 ro video=SVIDEO-1:d consoleblank=300 RelatedPackageVersions: linux-restricted-modules-4.15.0-12-generic N/A linux-backports-modules-4.15.0-12-generic N/A linux-firmware 1.173 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/22/2008 dmi.bios.vendor: Phoenix dmi.bios.version: 1.11 - 067 - 1566 dmi.board.name: S11D dmi.board.vendor: FUJITSU SIEMENS dmi.board.versio
[Kernel-packages] [Bug 1734147] Re: corrupted BIOS due to Intel SPI bug in kernel
>#589 I did not try it myself, but in case of everything eles failed, this site might give you some idea. https://www.dedoimedo.com/computers/lenovo-g50-read-only-nvram-solution.html and https://www.dedoimedo.com/computers/uefi-nvram-ro-installation-workaround.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1734147 Title: corrupted BIOS due to Intel SPI bug in kernel Status in Linux: Unknown Status in linux package in Ubuntu: Fix Released Status in linux-hwe-edge source package in Xenial: Fix Released Status in linux-oem source package in Xenial: Fix Released Status in linux source package in Artful: Fix Released Bug description: An update to linux kernel on Ubuntu 17.10 that enabled the Intel SPI drivers results in a serial flash that is read only in Intel Broadwell and Haswell machines with serial flashes with SPI_NOR_HAS_LOCK set. Symptoms: * BIOS settings cannot be saved * USB Boot impossible * EFI entries read-only. --- Fix: The issue was fixed in kernel version 4.13.0-21 by configuring the kernel so it is not compiled with Intel SPI support. But previous affected machines still suffered from a broken BIOS. Repair: If you still can boot into Ubuntu, you can recover your BIOS with the following steps: 1. Boot into Ubuntu 2. Download http://people.canonical.com/~ypwong/lp1734147/linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+20170103+1_amd64.deb 3. Install the downloaded package: $ sudo dpkg -i linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+20170103+1_amd64.deb 4. Make sure the kernel is installed without any error. Once installed, reboot. 5. At grub, choose the newly installed kernel. You can choose the "recovery" mode. 6. Reboot and go to BIOS settings to confirm your BIOS has been recovered. 7. In case your BIOS is not recovered, reboot to the new kernel, then reboot *once again* to the new kernel, do not enter BIOS settings before the reboot. After the second reboot, check BIOS. 8. If your BIOS issue remains, download another kernel from http://people.canonical.com/~ypwong/lp1734147/linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+clear+debug_amd64.deb, and use dpkg to install it, then repeat steps 4 to 6. After your BIOS is fixed, the kernel packages you just installed are no longer needed, you can remove it by running 'sudo dpkg -r linux- image-4.15.0-041500rc6-generic'. The patch used to build the linux v4.15 kernel in step 8 can be found at https://goo.gl/xUKJFR. --- Test Case: Fix has been verified by our HWE team on affected hardware. Regression Potential: Minimal, it's unlikely anyone is actually doing anything which requires this driver. --- Affected Machines: Lenovo B40-70 Lenovo B50-70 Lenovo B50-80 Lenovo Flex-3 Lenovo Flex-10 Lenovo G40-30 Lenovo G50-30 Lenovo G50-70 Lenovo G50-80 Lenovo S20-30 Lenovo U31-70 Lenovo Y50-70 Lenovo Y70-70 Lenovo Yoga Thinkpad (20C0) Lenovo Yoga 2 11" - 20332 Lenovo Yoga 3 11" Lenovo Z50-70 Lenovo Z51-70 Lenovo ideapad 100-15IBY Acer Aspire E5-771G Acer Aspire ES1-111M-C1LE (fixed following your new instruction (thank you)) Acer TravelMate B113 Acer Swift SF314-52 (Fixed by 4.14.9) Toshiba Satellite S55T-B5233 Toshiba Satellite L50-B-1R7 Toshiba Satellite S50-B-13G Toshiba Satellite L70-A-13M Dell Inspiron 15-3531 Mediacom Smartbook 14 Ultra M-SB14UC (fixed with official fix) Acer Aspire E3-111-C0UM HP 14-r012la --- Affected serial flash devices by manufacturer part number, JEDEC ID (SPI_NOR_HAS_LOCK set in drivers/mtd/spi-nor/spi-nor.c) /* ESMT */ f25l32pa, 0x8c2016 f25l32qa, 0x8c4116 f25l64qa, 0x8c4117 /* GigaDevice */ gd25q16, 0xc84015 gd25q32, 0xc84016 gd25lq32, 0xc86016 gd25q64, 0xc84017 gd25lq64c, 0xc86017 gd25q128, 0xc84018 gd25q256, 0xc84019 /* Winbond */ w25q16dw, 0xef6015 w25q32dw, 0xef6016 w25q64dw, 0xef6017 w25q128fw, 0xef6018 --- Original Description: Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users reported a corrupted BIOS. It's not possible to save new settings in BIOS anymore and after rebooting, the system starts with the old settings. Moreover (and most important) USB booting is not possible anymore since USB is not recognized. It's very serious, since our machines do not have a CDROM. Lenovo forums at the moment are full of topics regading this issue. Thank you!! To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1734147/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListH
[Kernel-packages] [Bug 1756877] Re: High visual latency in 18.04 when using nouveau
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.16 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.16-rc7 ** Changed in: linux (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1756877 Title: High visual latency in 18.04 when using nouveau Status in linux package in Ubuntu: Confirmed Bug description: I am on an Dell xps 9530 laptop and I had recently cleaned installed 17.10. A few days back I decided to updated to 18.04 to check it out and report some bugs. The most annoying bug so far is the insane amount of input latency this update has brought with it to a degree that it makes it impossible to be productive. The issue is observable when using either the mouse or the keyboard. The mouse does not move immediately but it needs a second or two to register and start moving and even then at some point it freezes for half a second at some random point and then moves again. Also if I have two applications side by side and I try an move focus from one to the next at around the edges of each window the mouse freezes for a second and then moves. The keyboard freezes if it hasn't been used for a while and on the first keystroke will take a second to register and for a bonus you get the first keystorke repeated for around 15-30 times. So if you are trying to write "and" will become "aaand" or pressing "ctrl + T" in the browser will open not one but 20 tabs! I am reporting it here cause I am not sure what is causing all this latency (it could be libinput or something else entirely) but please try and fix this as soon as possible!! ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Mar 19 13:04:05 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-02-14 (32 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) SourcePackage: gnome-shell UpgradeStatus: Upgraded to bionic on 2018-03-15 (3 days ago) --- ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: giannissc 2031 F pulseaudio /dev/snd/pcmC1D0p: giannissc 2031 F...m pulseaudio /dev/snd/controlC1: giannissc 2031 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=999e9885-dbd2-4a45-a45f-998e322f32dc InstallationDate: Installed on 2018-03-26 (2 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180325) MachineType: Dell Inc. XPS 15 9530 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-13-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 RelatedPackageVersions: linux-restricted-modules-4.15.0-13-generic N/A linux-backports-modules-4.15.0-13-generic N/A linux-firmware 1.173 Tags: wayland-session bionic Uname: Linux 4.15.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/08/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: XPS 15 9530 dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA08:bd01/08/2015:svnDellInc.:pnXPS159530:pvrA08:rvnDellInc.:rnXPS159530:rvrA08:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: XPS 15 9530 dmi.product.version: A08 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1756877/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1749961] Re: xhci_hcd: TRB DMA errors reported with ASMedia ASM1142 USB 3.1 Controller
** Also affects: linux (Debian) 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/1749961 Title: xhci_hcd: TRB DMA errors reported with ASMedia ASM1142 USB 3.1 Controller Status in linux package in Ubuntu: In Progress Status in linux source package in Trusty: In Progress Status in linux source package in Xenial: In Progress Status in linux source package in Artful: In Progress Status in linux source package in Bionic: In Progress Status in linux package in Debian: New Bug description: It was observed that while trying to use a 4K USB webcam connected to USB port provided by ASMedia ASM1142 USB 3.1 Controller, the webcam does not work and kernel log shows the following messages: [431.928016] xhci_hcd :12:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13 [431.928021] xhci_hcd :12:00.0: Looking for event-dma 003f3330e020 trb-start 003f3330e000 trb-end 003f3330e000 seg-start 003f3330e000 seg-end 003f3330eff0 [431.928024] xhci_hcd :12:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13 [431.928026] xhci_hcd :12:00.0: Looking for event-dma 003f3330e030 trb-start 003f3330e000 trb-end 003f3330e000 seg-start 003f3330e000 seg-end 003f3330eff0 [431.928027] xhci_hcd :12:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13 [431.928029] xhci_hcd :12:00.0: Looking for event-dma 003f3330e050 trb-start 003f3330e000 trb-end 003f3330e000 seg-start 003f3330e000 seg-end 003f3330eff0 [431.928386] xhci_hcd :12:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13 A similar issue was already reported on Launchpad: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1667750 The fix to this issue seems to be the following patch: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=9da5a109 Tests in our scenario with this patch proved still broken. Our next approach is to modify the patch a bit and re-test. This LP will be used to document our progress in the investigation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1749961/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1749961] Re: xhci_hcd: TRB DMA errors reported with ASMedia ASM1142 USB 3.1 Controller
echo xhci-hcd >> /sys/kernel/debug/tracing/set_event (tail -F -n0 /var/log/kern.log &) | grep -q "TRB DMA" cp /var/log/kern.log /home/imperia/log1.log Is this correct command to get traces? I will run it in advance. Somebody told me to run this before when I was looking for help. BTW did you download the full logs so I can remove it from web page? I will can provide ssh access to box affected if needed. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1749961 Title: xhci_hcd: TRB DMA errors reported with ASMedia ASM1142 USB 3.1 Controller Status in linux package in Ubuntu: In Progress Status in linux source package in Trusty: In Progress Status in linux source package in Xenial: In Progress Status in linux source package in Artful: In Progress Status in linux source package in Bionic: In Progress Bug description: It was observed that while trying to use a 4K USB webcam connected to USB port provided by ASMedia ASM1142 USB 3.1 Controller, the webcam does not work and kernel log shows the following messages: [431.928016] xhci_hcd :12:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13 [431.928021] xhci_hcd :12:00.0: Looking for event-dma 003f3330e020 trb-start 003f3330e000 trb-end 003f3330e000 seg-start 003f3330e000 seg-end 003f3330eff0 [431.928024] xhci_hcd :12:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13 [431.928026] xhci_hcd :12:00.0: Looking for event-dma 003f3330e030 trb-start 003f3330e000 trb-end 003f3330e000 seg-start 003f3330e000 seg-end 003f3330eff0 [431.928027] xhci_hcd :12:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13 [431.928029] xhci_hcd :12:00.0: Looking for event-dma 003f3330e050 trb-start 003f3330e000 trb-end 003f3330e000 seg-start 003f3330e000 seg-end 003f3330eff0 [431.928386] xhci_hcd :12:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13 A similar issue was already reported on Launchpad: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1667750 The fix to this issue seems to be the following patch: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=9da5a109 Tests in our scenario with this patch proved still broken. Our next approach is to modify the patch a bit and re-test. This LP will be used to document our progress in the investigation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1749961/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1756877] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1756877/+attachment/5095314/+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/1756877 Title: High visual latency in 18.04 when using nouveau Status in linux package in Ubuntu: Confirmed Bug description: I am on an Dell xps 9530 laptop and I had recently cleaned installed 17.10. A few days back I decided to updated to 18.04 to check it out and report some bugs. The most annoying bug so far is the insane amount of input latency this update has brought with it to a degree that it makes it impossible to be productive. The issue is observable when using either the mouse or the keyboard. The mouse does not move immediately but it needs a second or two to register and start moving and even then at some point it freezes for half a second at some random point and then moves again. Also if I have two applications side by side and I try an move focus from one to the next at around the edges of each window the mouse freezes for a second and then moves. The keyboard freezes if it hasn't been used for a while and on the first keystroke will take a second to register and for a bonus you get the first keystorke repeated for around 15-30 times. So if you are trying to write "and" will become "aaand" or pressing "ctrl + T" in the browser will open not one but 20 tabs! I am reporting it here cause I am not sure what is causing all this latency (it could be libinput or something else entirely) but please try and fix this as soon as possible!! ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Mar 19 13:04:05 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-02-14 (32 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) SourcePackage: gnome-shell UpgradeStatus: Upgraded to bionic on 2018-03-15 (3 days ago) --- ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: giannissc 2031 F pulseaudio /dev/snd/pcmC1D0p: giannissc 2031 F...m pulseaudio /dev/snd/controlC1: giannissc 2031 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=999e9885-dbd2-4a45-a45f-998e322f32dc InstallationDate: Installed on 2018-03-26 (2 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180325) MachineType: Dell Inc. XPS 15 9530 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-13-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 RelatedPackageVersions: linux-restricted-modules-4.15.0-13-generic N/A linux-backports-modules-4.15.0-13-generic N/A linux-firmware 1.173 Tags: wayland-session bionic Uname: Linux 4.15.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/08/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: XPS 15 9530 dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA08:bd01/08/2015:svnDellInc.:pnXPS159530:pvrA08:rvnDellInc.:rnXPS159530:rvrA08:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: XPS 15 9530 dmi.product.version: A08 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1756877/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1756877] Re: High visual latency in 18.04 when using nouveau
Run the apport-collect command btw. ** 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/1756877 Title: High visual latency in 18.04 when using nouveau Status in linux package in Ubuntu: Confirmed Bug description: I am on an Dell xps 9530 laptop and I had recently cleaned installed 17.10. A few days back I decided to updated to 18.04 to check it out and report some bugs. The most annoying bug so far is the insane amount of input latency this update has brought with it to a degree that it makes it impossible to be productive. The issue is observable when using either the mouse or the keyboard. The mouse does not move immediately but it needs a second or two to register and start moving and even then at some point it freezes for half a second at some random point and then moves again. Also if I have two applications side by side and I try an move focus from one to the next at around the edges of each window the mouse freezes for a second and then moves. The keyboard freezes if it hasn't been used for a while and on the first keystroke will take a second to register and for a bonus you get the first keystorke repeated for around 15-30 times. So if you are trying to write "and" will become "aaand" or pressing "ctrl + T" in the browser will open not one but 20 tabs! I am reporting it here cause I am not sure what is causing all this latency (it could be libinput or something else entirely) but please try and fix this as soon as possible!! ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Mar 19 13:04:05 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-02-14 (32 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) SourcePackage: gnome-shell UpgradeStatus: Upgraded to bionic on 2018-03-15 (3 days ago) --- ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: giannissc 2031 F pulseaudio /dev/snd/pcmC1D0p: giannissc 2031 F...m pulseaudio /dev/snd/controlC1: giannissc 2031 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=999e9885-dbd2-4a45-a45f-998e322f32dc InstallationDate: Installed on 2018-03-26 (2 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180325) MachineType: Dell Inc. XPS 15 9530 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-13-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 RelatedPackageVersions: linux-restricted-modules-4.15.0-13-generic N/A linux-backports-modules-4.15.0-13-generic N/A linux-firmware 1.173 Tags: wayland-session bionic Uname: Linux 4.15.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/08/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: XPS 15 9530 dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA08:bd01/08/2015:svnDellInc.:pnXPS159530:pvrA08:rvnDellInc.:rnXPS159530:rvrA08:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: XPS 15 9530 dmi.product.version: A08 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1756877/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1759947] Re: BUG: unable to handle kernel paging request at 0000200000000020
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1759947 Title: BUG: unable to handle kernel paging request at 2020 Status in linux package in Ubuntu: New Bug description: Unclear what happened. It said chrome was dying, but then nothing including mouse and keyboard worked. ProblemType: KernelOops DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-13-generic 4.15.0-13.14 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 Date: Thu Mar 29 13:56:40 2018 DuplicateSignature: BUG: unable to handle kernel paging request at location RIP: find_get_entry+0x42/0x110 RSP: b73c51c3fbe8 Failure: oops MachineType: System manufacturer System Product Name ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed root=UUID=9320ec1f-aa3c-477d-b5d8-b02d82864086 ro pcie_aspm=off PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: kerneloops-daemon N/A SourcePackage: linux Title: BUG: unable to handle kernel paging request at 2020 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/21/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0902 dmi.board.asset.tag: Default string dmi.board.name: ROG ZENITH EXTREME dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0902:bd12/21/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGZENITHEXTREME:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1759947/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1759947] Re: BUG: unable to handle kernel paging request at 0000200000000020
** Attachment added: "lspci-vnvn.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1759947/+attachment/5095360/+files/lspci-vnvn.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1759947 Title: BUG: unable to handle kernel paging request at 2020 Status in linux package in Ubuntu: New Bug description: Unclear what happened. It said chrome was dying, but then nothing including mouse and keyboard worked. ProblemType: KernelOops DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-13-generic 4.15.0-13.14 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 Date: Thu Mar 29 13:56:40 2018 DuplicateSignature: BUG: unable to handle kernel paging request at location RIP: find_get_entry+0x42/0x110 RSP: b73c51c3fbe8 Failure: oops MachineType: System manufacturer System Product Name ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed root=UUID=9320ec1f-aa3c-477d-b5d8-b02d82864086 ro pcie_aspm=off PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: kerneloops-daemon N/A SourcePackage: linux Title: BUG: unable to handle kernel paging request at 2020 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/21/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0902 dmi.board.asset.tag: Default string dmi.board.name: ROG ZENITH EXTREME dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0902:bd12/21/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGZENITHEXTREME:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1759947/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1759947] [NEW] BUG: unable to handle kernel paging request at 0000200000000020
Public bug reported: Unclear what happened. It said chrome was dying, but then nothing including mouse and keyboard worked. ProblemType: KernelOops DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-13-generic 4.15.0-13.14 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 Date: Thu Mar 29 13:56:40 2018 DuplicateSignature: BUG: unable to handle kernel paging request at location RIP: find_get_entry+0x42/0x110 RSP: b73c51c3fbe8 Failure: oops MachineType: System manufacturer System Product Name ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed root=UUID=9320ec1f-aa3c-477d-b5d8-b02d82864086 ro pcie_aspm=off PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: kerneloops-daemon N/A SourcePackage: linux Title: BUG: unable to handle kernel paging request at 2020 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/21/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0902 dmi.board.asset.tag: Default string dmi.board.name: ROG ZENITH EXTREME dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0902:bd12/21/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGZENITHEXTREME:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-kerneloops bionic kernel-oops ** Attachment added: "version.log" https://bugs.launchpad.net/bugs/1759947/+attachment/5095343/+files/version.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1759947 Title: BUG: unable to handle kernel paging request at 2020 Status in linux package in Ubuntu: New Bug description: Unclear what happened. It said chrome was dying, but then nothing including mouse and keyboard worked. ProblemType: KernelOops DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-13-generic 4.15.0-13.14 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 Date: Thu Mar 29 13:56:40 2018 DuplicateSignature: BUG: unable to handle kernel paging request at location RIP: find_get_entry+0x42/0x110 RSP: b73c51c3fbe8 Failure: oops MachineType: System manufacturer System Product Name ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed root=UUID=9320ec1f-aa3c-477d-b5d8-b02d82864086 ro pcie_aspm=off PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: kerneloops-daemon N/A SourcePackage: linux Title: BUG: unable to handle kernel paging request at 2020 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/21/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0902 dmi.board.asset.tag: Default string dmi.board.name: ROG ZENITH EXTREME dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0902:bd12/21/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGZENITHEXTREME:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1759947/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1729674] Re: TB16 dock ethernet corrupts data with hw checksum silently failing
Ran same tests against 4.13.0-38 on artful. Just curious, this only seems to be applied to hwe and hwe-edge kernels for xenial. Is that a change in policy? Even though I haven't attempted it, it appears as if this should be pretty straightforward apply on the 4.4 kernel stream. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1729674 Title: TB16 dock ethernet corrupts data with hw checksum silently failing Status in Dell Sputnik: Triaged Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Status in linux source package in Artful: Fix Committed Status in linux source package in Bionic: Fix Released Status in linux package in Fedora: Confirmed Bug description: It looks like TCP rx and tx checksum offloading is broken on the TB16 dock's ethernet adapter. For example downloading a large file such as the Ubuntu ISO, and then running an md5sum on it yields the incorrect md5sum. This is because rx-checksumming: on tx-checksumming: on and both set to on by default. Running sudo ethtool -K tx off rx off, allows the download to complete correctly. This is very bad since this can cause very bad untrustworthy behavior. This was conducted using an Dell Precision 5520 on Ubuntu 16.04+linux- generic-hwe-16.04-edge. Thank you To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1729674/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1756877] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1756877/+attachment/5095318/+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/1756877 Title: High visual latency in 18.04 when using nouveau Status in linux package in Ubuntu: Confirmed Bug description: I am on an Dell xps 9530 laptop and I had recently cleaned installed 17.10. A few days back I decided to updated to 18.04 to check it out and report some bugs. The most annoying bug so far is the insane amount of input latency this update has brought with it to a degree that it makes it impossible to be productive. The issue is observable when using either the mouse or the keyboard. The mouse does not move immediately but it needs a second or two to register and start moving and even then at some point it freezes for half a second at some random point and then moves again. Also if I have two applications side by side and I try an move focus from one to the next at around the edges of each window the mouse freezes for a second and then moves. The keyboard freezes if it hasn't been used for a while and on the first keystroke will take a second to register and for a bonus you get the first keystorke repeated for around 15-30 times. So if you are trying to write "and" will become "aaand" or pressing "ctrl + T" in the browser will open not one but 20 tabs! I am reporting it here cause I am not sure what is causing all this latency (it could be libinput or something else entirely) but please try and fix this as soon as possible!! ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Mar 19 13:04:05 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-02-14 (32 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) SourcePackage: gnome-shell UpgradeStatus: Upgraded to bionic on 2018-03-15 (3 days ago) --- ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: giannissc 2031 F pulseaudio /dev/snd/pcmC1D0p: giannissc 2031 F...m pulseaudio /dev/snd/controlC1: giannissc 2031 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=999e9885-dbd2-4a45-a45f-998e322f32dc InstallationDate: Installed on 2018-03-26 (2 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180325) MachineType: Dell Inc. XPS 15 9530 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-13-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 RelatedPackageVersions: linux-restricted-modules-4.15.0-13-generic N/A linux-backports-modules-4.15.0-13-generic N/A linux-firmware 1.173 Tags: wayland-session bionic Uname: Linux 4.15.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/08/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: XPS 15 9530 dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA08:bd01/08/2015:svnDellInc.:pnXPS159530:pvrA08:rvnDellInc.:rnXPS159530:rvrA08:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: XPS 15 9530 dmi.product.version: A08 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1756877/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1756877] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1756877/+attachment/5095312/+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/1756877 Title: High visual latency in 18.04 when using nouveau Status in linux package in Ubuntu: Confirmed Bug description: I am on an Dell xps 9530 laptop and I had recently cleaned installed 17.10. A few days back I decided to updated to 18.04 to check it out and report some bugs. The most annoying bug so far is the insane amount of input latency this update has brought with it to a degree that it makes it impossible to be productive. The issue is observable when using either the mouse or the keyboard. The mouse does not move immediately but it needs a second or two to register and start moving and even then at some point it freezes for half a second at some random point and then moves again. Also if I have two applications side by side and I try an move focus from one to the next at around the edges of each window the mouse freezes for a second and then moves. The keyboard freezes if it hasn't been used for a while and on the first keystroke will take a second to register and for a bonus you get the first keystorke repeated for around 15-30 times. So if you are trying to write "and" will become "aaand" or pressing "ctrl + T" in the browser will open not one but 20 tabs! I am reporting it here cause I am not sure what is causing all this latency (it could be libinput or something else entirely) but please try and fix this as soon as possible!! ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Mar 19 13:04:05 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-02-14 (32 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) SourcePackage: gnome-shell UpgradeStatus: Upgraded to bionic on 2018-03-15 (3 days ago) --- ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: giannissc 2031 F pulseaudio /dev/snd/pcmC1D0p: giannissc 2031 F...m pulseaudio /dev/snd/controlC1: giannissc 2031 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=999e9885-dbd2-4a45-a45f-998e322f32dc InstallationDate: Installed on 2018-03-26 (2 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180325) MachineType: Dell Inc. XPS 15 9530 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-13-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 RelatedPackageVersions: linux-restricted-modules-4.15.0-13-generic N/A linux-backports-modules-4.15.0-13-generic N/A linux-firmware 1.173 Tags: wayland-session bionic Uname: Linux 4.15.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/08/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: XPS 15 9530 dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA08:bd01/08/2015:svnDellInc.:pnXPS159530:pvrA08:rvnDellInc.:rnXPS159530:rvrA08:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: XPS 15 9530 dmi.product.version: A08 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1756877/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1756877] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1756877/+attachment/5095321/+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/1756877 Title: High visual latency in 18.04 when using nouveau Status in linux package in Ubuntu: Confirmed Bug description: I am on an Dell xps 9530 laptop and I had recently cleaned installed 17.10. A few days back I decided to updated to 18.04 to check it out and report some bugs. The most annoying bug so far is the insane amount of input latency this update has brought with it to a degree that it makes it impossible to be productive. The issue is observable when using either the mouse or the keyboard. The mouse does not move immediately but it needs a second or two to register and start moving and even then at some point it freezes for half a second at some random point and then moves again. Also if I have two applications side by side and I try an move focus from one to the next at around the edges of each window the mouse freezes for a second and then moves. The keyboard freezes if it hasn't been used for a while and on the first keystroke will take a second to register and for a bonus you get the first keystorke repeated for around 15-30 times. So if you are trying to write "and" will become "aaand" or pressing "ctrl + T" in the browser will open not one but 20 tabs! I am reporting it here cause I am not sure what is causing all this latency (it could be libinput or something else entirely) but please try and fix this as soon as possible!! ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Mar 19 13:04:05 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-02-14 (32 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) SourcePackage: gnome-shell UpgradeStatus: Upgraded to bionic on 2018-03-15 (3 days ago) --- ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: giannissc 2031 F pulseaudio /dev/snd/pcmC1D0p: giannissc 2031 F...m pulseaudio /dev/snd/controlC1: giannissc 2031 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=999e9885-dbd2-4a45-a45f-998e322f32dc InstallationDate: Installed on 2018-03-26 (2 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180325) MachineType: Dell Inc. XPS 15 9530 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-13-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 RelatedPackageVersions: linux-restricted-modules-4.15.0-13-generic N/A linux-backports-modules-4.15.0-13-generic N/A linux-firmware 1.173 Tags: wayland-session bionic Uname: Linux 4.15.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/08/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: XPS 15 9530 dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA08:bd01/08/2015:svnDellInc.:pnXPS159530:pvrA08:rvnDellInc.:rnXPS159530:rvrA08:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: XPS 15 9530 dmi.product.version: A08 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1756877/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1756877] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1756877/+attachment/5095313/+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/1756877 Title: High visual latency in 18.04 when using nouveau Status in linux package in Ubuntu: Confirmed Bug description: I am on an Dell xps 9530 laptop and I had recently cleaned installed 17.10. A few days back I decided to updated to 18.04 to check it out and report some bugs. The most annoying bug so far is the insane amount of input latency this update has brought with it to a degree that it makes it impossible to be productive. The issue is observable when using either the mouse or the keyboard. The mouse does not move immediately but it needs a second or two to register and start moving and even then at some point it freezes for half a second at some random point and then moves again. Also if I have two applications side by side and I try an move focus from one to the next at around the edges of each window the mouse freezes for a second and then moves. The keyboard freezes if it hasn't been used for a while and on the first keystroke will take a second to register and for a bonus you get the first keystorke repeated for around 15-30 times. So if you are trying to write "and" will become "aaand" or pressing "ctrl + T" in the browser will open not one but 20 tabs! I am reporting it here cause I am not sure what is causing all this latency (it could be libinput or something else entirely) but please try and fix this as soon as possible!! ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Mar 19 13:04:05 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-02-14 (32 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) SourcePackage: gnome-shell UpgradeStatus: Upgraded to bionic on 2018-03-15 (3 days ago) --- ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: giannissc 2031 F pulseaudio /dev/snd/pcmC1D0p: giannissc 2031 F...m pulseaudio /dev/snd/controlC1: giannissc 2031 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=999e9885-dbd2-4a45-a45f-998e322f32dc InstallationDate: Installed on 2018-03-26 (2 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180325) MachineType: Dell Inc. XPS 15 9530 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-13-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 RelatedPackageVersions: linux-restricted-modules-4.15.0-13-generic N/A linux-backports-modules-4.15.0-13-generic N/A linux-firmware 1.173 Tags: wayland-session bionic Uname: Linux 4.15.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/08/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: XPS 15 9530 dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA08:bd01/08/2015:svnDellInc.:pnXPS159530:pvrA08:rvnDellInc.:rnXPS159530:rvrA08:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: XPS 15 9530 dmi.product.version: A08 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1756877/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1756877] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1756877/+attachment/5095319/+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/1756877 Title: High visual latency in 18.04 when using nouveau Status in linux package in Ubuntu: Confirmed Bug description: I am on an Dell xps 9530 laptop and I had recently cleaned installed 17.10. A few days back I decided to updated to 18.04 to check it out and report some bugs. The most annoying bug so far is the insane amount of input latency this update has brought with it to a degree that it makes it impossible to be productive. The issue is observable when using either the mouse or the keyboard. The mouse does not move immediately but it needs a second or two to register and start moving and even then at some point it freezes for half a second at some random point and then moves again. Also if I have two applications side by side and I try an move focus from one to the next at around the edges of each window the mouse freezes for a second and then moves. The keyboard freezes if it hasn't been used for a while and on the first keystroke will take a second to register and for a bonus you get the first keystorke repeated for around 15-30 times. So if you are trying to write "and" will become "aaand" or pressing "ctrl + T" in the browser will open not one but 20 tabs! I am reporting it here cause I am not sure what is causing all this latency (it could be libinput or something else entirely) but please try and fix this as soon as possible!! ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Mar 19 13:04:05 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-02-14 (32 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) SourcePackage: gnome-shell UpgradeStatus: Upgraded to bionic on 2018-03-15 (3 days ago) --- ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: giannissc 2031 F pulseaudio /dev/snd/pcmC1D0p: giannissc 2031 F...m pulseaudio /dev/snd/controlC1: giannissc 2031 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=999e9885-dbd2-4a45-a45f-998e322f32dc InstallationDate: Installed on 2018-03-26 (2 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180325) MachineType: Dell Inc. XPS 15 9530 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-13-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 RelatedPackageVersions: linux-restricted-modules-4.15.0-13-generic N/A linux-backports-modules-4.15.0-13-generic N/A linux-firmware 1.173 Tags: wayland-session bionic Uname: Linux 4.15.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/08/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: XPS 15 9530 dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA08:bd01/08/2015:svnDellInc.:pnXPS159530:pvrA08:rvnDellInc.:rnXPS159530:rvrA08:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: XPS 15 9530 dmi.product.version: A08 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1756877/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1723904] Re: ubuntu-kvm-unit test failed with sprs test on ppc64le
Hi @paelzer, Here are the backport patches. Let me know if there are any problems. ** Patch added: "canonical_sprs_backport.patch" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1723904/+attachment/5095323/+files/canonical_sprs_backport.patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1723904 Title: ubuntu-kvm-unit test failed with sprs test on ppc64le Status in linux package in Ubuntu: Confirmed Status in qemu package in Ubuntu: Incomplete Bug description: The sprs test has failed on ppc64le This issue can be spotted on Zesty and Xenial. There is no history for this test on Artful $ sudo /bin/bash -c "MIGRATION=yes TESTNAME=sprs TIMEOUT=90s ACCEL= ./powerpc/run powerpc/sprs.elf -smp 1 -append '-w'" run_migration timeout -k 1s --foreground 90s /usr/bin/qemu-system-ppc64 -nodefaults -machine pseries,accel=kvm -bios powerpc/boot_rom.bin -display none -serial stdio -kernel powerpc/sprs.elf -smp 1 -append -w # -initrd /tmp/tmp.RUTL6E2JSi Settings SPRs to 0xcafefacec0debabe... Now migrate the VM, then press a key or send NMI... Checking SPRs... PASS: SPR 3: 0x00debabe <==> 0x00debabe PASS: SPR 13: 0xcafefacec0debabe <==> 0xcafefacec0debabe PASS: SPR 17: 0x00debabe <==> 0x00debabe PASS: SPR 18: 0xc0debabe <==> 0xc0debabe PASS: SPR 19: 0xcafefacec0debabe <==> 0xcafefacec0debabe PASS: SPR 29: 0xcafefacec0debabe <==> 0xcafefacec0debabe FAIL: SPR 61: 0x4054504440541014 <==> 00 PASS: SPR 153:0x0a84 <==> 0x0a84 PASS: SPR 157:0xcfcfc0cf <==> 0xcfcfc0cf FAIL: SPR 159:0xc0debabe <==> 00 PASS: SPR 256:0xc0debabe <==> 0xc0debabe PASS: SPR 259:0xcafefacec0debabe <==> 0xcafefacec0debabe PASS: SPR 274:0xcafefacec0debabe <==> 0xcafefacec0debabe PASS: SPR 275:0xcafefacec0debabe <==> 0xcafefacec0debabe PASS: SPR 769:0xcafefacec0debabe <==> 0xcafefacec0debabe PASS: SPR 770:0xcafefacec006babe <==> 0xcafefacec006babe PASS: SPR 771:0xc0debabe <==> 0xc0debabe PASS: SPR 772:0xc0debabe <==> 0xc0debabe PASS: SPR 773:0xc0debabe <==> 0xc0debabe PASS: SPR 774:0xc0debabe <==> 0xc0debabe PASS: SPR 775:0xc0debabe <==> 0xc0debabe PASS: SPR 776:0xc0debabe <==> 0xc0debabe PASS: SPR 779:0xfa8b1afe <==> 0xfa8b1afe PASS: SPR 780:0xcafefacec0debabc <==> 0xcafefacec0debabc PASS: SPR 781:0xcafefacec0debabe <==> 0xcafefacec0debabe PASS: SPR 782:0xcafefacec0debabe <==> 0xcafefacec0debabe FAIL: SPR 784:0xcafefacec0debabe <==> 00 PASS: SPR 785:0xcafefacec0debabe <==> 0xcafefacec0debabe PASS: SPR 786:0xcafefacec006babe <==> 0xcafefacec006babe PASS: SPR 787:0xc0debabe <==> 0xc0debabe PASS: SPR 788:0xc0debabe <==> 0xc0debabe PASS: SPR 789:0xc0debabe <==> 0xc0debabe PASS: SPR 790:0xc0debabe <==> 0xc0debabe PASS: SPR 791:0xc0debabe <==> 0xc0debabe PASS: SPR 792:0xc0debabe <==> 0xc0debabe PASS: SPR 795:0xfa8b1afe <==> 0xfa8b1afe PASS: SPR 796:0xcafefacec0debabc <==> 0xcafefacec0debabc PASS: SPR 797:0xcafefacec0debabe <==> 0xcafefacec0debabe PASS: SPR 798:0xcafefacec0debabe <==> 0xcafefacec0debabe PASS: SPR 800:0x8000c000 <==> 0x8000c000 PASS: SPR 801:0x8000 <==> 0x8000 PASS: SPR 802:0x8000c000 <==> 0x8000c000 PASS: SPR 803:0x8000 <==> 0x8000 PASS: SPR 804:0xcafefacec0debabe <==> 0xcafefacec0debabe PASS: SPR 805:0xcafefacec0debabc <==> 0xcafefacec0debabc PASS: SPR 806:0x8000c000 <==> 0x8000c000 FAIL: SPR 815:0xcafefacec0debabe <==> 00 SUMMARY: 47 tests, 4 unexpected failures EXIT: STATUS=3 $ qemu-system-ppc --version QEMU emulator version 2.5.0 (Debian 1:2.5+dfsg-5ubuntu10.16), Copyright (c) 2003-2008 Fabrice Bellard ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.10.0-37-generic 4.10.0-37.41~16.04.1 ProcVersionSignature: User Name 4.10.0-37.41~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-37-generic ppc64le ApportVersion: 2.20.1-0ubuntu2.10 Architecture: ppc64el Date: Mon Oct 16 09:16:08 2017 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcLoadAvg: 0.02 0.14 0.17 1/1464 15093 ProcLocks:
[Kernel-packages] [Bug 1756877] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1756877/+attachment/5095320/+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/1756877 Title: High visual latency in 18.04 when using nouveau Status in linux package in Ubuntu: Confirmed Bug description: I am on an Dell xps 9530 laptop and I had recently cleaned installed 17.10. A few days back I decided to updated to 18.04 to check it out and report some bugs. The most annoying bug so far is the insane amount of input latency this update has brought with it to a degree that it makes it impossible to be productive. The issue is observable when using either the mouse or the keyboard. The mouse does not move immediately but it needs a second or two to register and start moving and even then at some point it freezes for half a second at some random point and then moves again. Also if I have two applications side by side and I try an move focus from one to the next at around the edges of each window the mouse freezes for a second and then moves. The keyboard freezes if it hasn't been used for a while and on the first keystroke will take a second to register and for a bonus you get the first keystorke repeated for around 15-30 times. So if you are trying to write "and" will become "aaand" or pressing "ctrl + T" in the browser will open not one but 20 tabs! I am reporting it here cause I am not sure what is causing all this latency (it could be libinput or something else entirely) but please try and fix this as soon as possible!! ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Mar 19 13:04:05 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-02-14 (32 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) SourcePackage: gnome-shell UpgradeStatus: Upgraded to bionic on 2018-03-15 (3 days ago) --- ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: giannissc 2031 F pulseaudio /dev/snd/pcmC1D0p: giannissc 2031 F...m pulseaudio /dev/snd/controlC1: giannissc 2031 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=999e9885-dbd2-4a45-a45f-998e322f32dc InstallationDate: Installed on 2018-03-26 (2 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180325) MachineType: Dell Inc. XPS 15 9530 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-13-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 RelatedPackageVersions: linux-restricted-modules-4.15.0-13-generic N/A linux-backports-modules-4.15.0-13-generic N/A linux-firmware 1.173 Tags: wayland-session bionic Uname: Linux 4.15.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/08/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: XPS 15 9530 dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA08:bd01/08/2015:svnDellInc.:pnXPS159530:pvrA08:rvnDellInc.:rnXPS159530:rvrA08:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: XPS 15 9530 dmi.product.version: A08 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1756877/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1756877] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1756877/+attachment/5095316/+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/1756877 Title: High visual latency in 18.04 when using nouveau Status in linux package in Ubuntu: Confirmed Bug description: I am on an Dell xps 9530 laptop and I had recently cleaned installed 17.10. A few days back I decided to updated to 18.04 to check it out and report some bugs. The most annoying bug so far is the insane amount of input latency this update has brought with it to a degree that it makes it impossible to be productive. The issue is observable when using either the mouse or the keyboard. The mouse does not move immediately but it needs a second or two to register and start moving and even then at some point it freezes for half a second at some random point and then moves again. Also if I have two applications side by side and I try an move focus from one to the next at around the edges of each window the mouse freezes for a second and then moves. The keyboard freezes if it hasn't been used for a while and on the first keystroke will take a second to register and for a bonus you get the first keystorke repeated for around 15-30 times. So if you are trying to write "and" will become "aaand" or pressing "ctrl + T" in the browser will open not one but 20 tabs! I am reporting it here cause I am not sure what is causing all this latency (it could be libinput or something else entirely) but please try and fix this as soon as possible!! ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Mar 19 13:04:05 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-02-14 (32 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) SourcePackage: gnome-shell UpgradeStatus: Upgraded to bionic on 2018-03-15 (3 days ago) --- ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: giannissc 2031 F pulseaudio /dev/snd/pcmC1D0p: giannissc 2031 F...m pulseaudio /dev/snd/controlC1: giannissc 2031 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=999e9885-dbd2-4a45-a45f-998e322f32dc InstallationDate: Installed on 2018-03-26 (2 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180325) MachineType: Dell Inc. XPS 15 9530 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-13-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 RelatedPackageVersions: linux-restricted-modules-4.15.0-13-generic N/A linux-backports-modules-4.15.0-13-generic N/A linux-firmware 1.173 Tags: wayland-session bionic Uname: Linux 4.15.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/08/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: XPS 15 9530 dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA08:bd01/08/2015:svnDellInc.:pnXPS159530:pvrA08:rvnDellInc.:rnXPS159530:rvrA08:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: XPS 15 9530 dmi.product.version: A08 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1756877/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1756877] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1756877/+attachment/5095317/+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/1756877 Title: High visual latency in 18.04 when using nouveau Status in linux package in Ubuntu: Confirmed Bug description: I am on an Dell xps 9530 laptop and I had recently cleaned installed 17.10. A few days back I decided to updated to 18.04 to check it out and report some bugs. The most annoying bug so far is the insane amount of input latency this update has brought with it to a degree that it makes it impossible to be productive. The issue is observable when using either the mouse or the keyboard. The mouse does not move immediately but it needs a second or two to register and start moving and even then at some point it freezes for half a second at some random point and then moves again. Also if I have two applications side by side and I try an move focus from one to the next at around the edges of each window the mouse freezes for a second and then moves. The keyboard freezes if it hasn't been used for a while and on the first keystroke will take a second to register and for a bonus you get the first keystorke repeated for around 15-30 times. So if you are trying to write "and" will become "aaand" or pressing "ctrl + T" in the browser will open not one but 20 tabs! I am reporting it here cause I am not sure what is causing all this latency (it could be libinput or something else entirely) but please try and fix this as soon as possible!! ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Mar 19 13:04:05 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-02-14 (32 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) SourcePackage: gnome-shell UpgradeStatus: Upgraded to bionic on 2018-03-15 (3 days ago) --- ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: giannissc 2031 F pulseaudio /dev/snd/pcmC1D0p: giannissc 2031 F...m pulseaudio /dev/snd/controlC1: giannissc 2031 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=999e9885-dbd2-4a45-a45f-998e322f32dc InstallationDate: Installed on 2018-03-26 (2 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180325) MachineType: Dell Inc. XPS 15 9530 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-13-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 RelatedPackageVersions: linux-restricted-modules-4.15.0-13-generic N/A linux-backports-modules-4.15.0-13-generic N/A linux-firmware 1.173 Tags: wayland-session bionic Uname: Linux 4.15.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/08/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: XPS 15 9530 dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA08:bd01/08/2015:svnDellInc.:pnXPS159530:pvrA08:rvnDellInc.:rnXPS159530:rvrA08:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: XPS 15 9530 dmi.product.version: A08 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1756877/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1756877] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1756877/+attachment/5095315/+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/1756877 Title: High visual latency in 18.04 when using nouveau Status in linux package in Ubuntu: Confirmed Bug description: I am on an Dell xps 9530 laptop and I had recently cleaned installed 17.10. A few days back I decided to updated to 18.04 to check it out and report some bugs. The most annoying bug so far is the insane amount of input latency this update has brought with it to a degree that it makes it impossible to be productive. The issue is observable when using either the mouse or the keyboard. The mouse does not move immediately but it needs a second or two to register and start moving and even then at some point it freezes for half a second at some random point and then moves again. Also if I have two applications side by side and I try an move focus from one to the next at around the edges of each window the mouse freezes for a second and then moves. The keyboard freezes if it hasn't been used for a while and on the first keystroke will take a second to register and for a bonus you get the first keystorke repeated for around 15-30 times. So if you are trying to write "and" will become "aaand" or pressing "ctrl + T" in the browser will open not one but 20 tabs! I am reporting it here cause I am not sure what is causing all this latency (it could be libinput or something else entirely) but please try and fix this as soon as possible!! ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Mar 19 13:04:05 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-02-14 (32 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) SourcePackage: gnome-shell UpgradeStatus: Upgraded to bionic on 2018-03-15 (3 days ago) --- ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: giannissc 2031 F pulseaudio /dev/snd/pcmC1D0p: giannissc 2031 F...m pulseaudio /dev/snd/controlC1: giannissc 2031 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=999e9885-dbd2-4a45-a45f-998e322f32dc InstallationDate: Installed on 2018-03-26 (2 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180325) MachineType: Dell Inc. XPS 15 9530 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-13-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 RelatedPackageVersions: linux-restricted-modules-4.15.0-13-generic N/A linux-backports-modules-4.15.0-13-generic N/A linux-firmware 1.173 Tags: wayland-session bionic Uname: Linux 4.15.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/08/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: XPS 15 9530 dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA08:bd01/08/2015:svnDellInc.:pnXPS159530:pvrA08:rvnDellInc.:rnXPS159530:rvrA08:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: XPS 15 9530 dmi.product.version: A08 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1756877/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1756877] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1756877/+attachment/5095311/+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/1756877 Title: High visual latency in 18.04 when using nouveau Status in linux package in Ubuntu: Confirmed Bug description: I am on an Dell xps 9530 laptop and I had recently cleaned installed 17.10. A few days back I decided to updated to 18.04 to check it out and report some bugs. The most annoying bug so far is the insane amount of input latency this update has brought with it to a degree that it makes it impossible to be productive. The issue is observable when using either the mouse or the keyboard. The mouse does not move immediately but it needs a second or two to register and start moving and even then at some point it freezes for half a second at some random point and then moves again. Also if I have two applications side by side and I try an move focus from one to the next at around the edges of each window the mouse freezes for a second and then moves. The keyboard freezes if it hasn't been used for a while and on the first keystroke will take a second to register and for a bonus you get the first keystorke repeated for around 15-30 times. So if you are trying to write "and" will become "aaand" or pressing "ctrl + T" in the browser will open not one but 20 tabs! I am reporting it here cause I am not sure what is causing all this latency (it could be libinput or something else entirely) but please try and fix this as soon as possible!! ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Mar 19 13:04:05 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-02-14 (32 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) SourcePackage: gnome-shell UpgradeStatus: Upgraded to bionic on 2018-03-15 (3 days ago) --- ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: giannissc 2031 F pulseaudio /dev/snd/pcmC1D0p: giannissc 2031 F...m pulseaudio /dev/snd/controlC1: giannissc 2031 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=999e9885-dbd2-4a45-a45f-998e322f32dc InstallationDate: Installed on 2018-03-26 (2 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180325) MachineType: Dell Inc. XPS 15 9530 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-13-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 RelatedPackageVersions: linux-restricted-modules-4.15.0-13-generic N/A linux-backports-modules-4.15.0-13-generic N/A linux-firmware 1.173 Tags: wayland-session bionic Uname: Linux 4.15.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/08/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: XPS 15 9530 dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA08:bd01/08/2015:svnDellInc.:pnXPS159530:pvrA08:rvnDellInc.:rnXPS159530:rvrA08:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: XPS 15 9530 dmi.product.version: A08 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1756877/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1756877] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1756877/+attachment/5095309/+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/1756877 Title: High visual latency in 18.04 when using nouveau Status in linux package in Ubuntu: Confirmed Bug description: I am on an Dell xps 9530 laptop and I had recently cleaned installed 17.10. A few days back I decided to updated to 18.04 to check it out and report some bugs. The most annoying bug so far is the insane amount of input latency this update has brought with it to a degree that it makes it impossible to be productive. The issue is observable when using either the mouse or the keyboard. The mouse does not move immediately but it needs a second or two to register and start moving and even then at some point it freezes for half a second at some random point and then moves again. Also if I have two applications side by side and I try an move focus from one to the next at around the edges of each window the mouse freezes for a second and then moves. The keyboard freezes if it hasn't been used for a while and on the first keystroke will take a second to register and for a bonus you get the first keystorke repeated for around 15-30 times. So if you are trying to write "and" will become "aaand" or pressing "ctrl + T" in the browser will open not one but 20 tabs! I am reporting it here cause I am not sure what is causing all this latency (it could be libinput or something else entirely) but please try and fix this as soon as possible!! ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Mar 19 13:04:05 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-02-14 (32 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) SourcePackage: gnome-shell UpgradeStatus: Upgraded to bionic on 2018-03-15 (3 days ago) --- ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: giannissc 2031 F pulseaudio /dev/snd/pcmC1D0p: giannissc 2031 F...m pulseaudio /dev/snd/controlC1: giannissc 2031 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=999e9885-dbd2-4a45-a45f-998e322f32dc InstallationDate: Installed on 2018-03-26 (2 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180325) MachineType: Dell Inc. XPS 15 9530 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-13-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 RelatedPackageVersions: linux-restricted-modules-4.15.0-13-generic N/A linux-backports-modules-4.15.0-13-generic N/A linux-firmware 1.173 Tags: wayland-session bionic Uname: Linux 4.15.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/08/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: XPS 15 9530 dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA08:bd01/08/2015:svnDellInc.:pnXPS159530:pvrA08:rvnDellInc.:rnXPS159530:rvrA08:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: XPS 15 9530 dmi.product.version: A08 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1756877/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1756877] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1756877/+attachment/5095310/+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/1756877 Title: High visual latency in 18.04 when using nouveau Status in linux package in Ubuntu: Confirmed Bug description: I am on an Dell xps 9530 laptop and I had recently cleaned installed 17.10. A few days back I decided to updated to 18.04 to check it out and report some bugs. The most annoying bug so far is the insane amount of input latency this update has brought with it to a degree that it makes it impossible to be productive. The issue is observable when using either the mouse or the keyboard. The mouse does not move immediately but it needs a second or two to register and start moving and even then at some point it freezes for half a second at some random point and then moves again. Also if I have two applications side by side and I try an move focus from one to the next at around the edges of each window the mouse freezes for a second and then moves. The keyboard freezes if it hasn't been used for a while and on the first keystroke will take a second to register and for a bonus you get the first keystorke repeated for around 15-30 times. So if you are trying to write "and" will become "aaand" or pressing "ctrl + T" in the browser will open not one but 20 tabs! I am reporting it here cause I am not sure what is causing all this latency (it could be libinput or something else entirely) but please try and fix this as soon as possible!! ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Mar 19 13:04:05 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-02-14 (32 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) SourcePackage: gnome-shell UpgradeStatus: Upgraded to bionic on 2018-03-15 (3 days ago) --- ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: giannissc 2031 F pulseaudio /dev/snd/pcmC1D0p: giannissc 2031 F...m pulseaudio /dev/snd/controlC1: giannissc 2031 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=999e9885-dbd2-4a45-a45f-998e322f32dc InstallationDate: Installed on 2018-03-26 (2 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180325) MachineType: Dell Inc. XPS 15 9530 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-13-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 RelatedPackageVersions: linux-restricted-modules-4.15.0-13-generic N/A linux-backports-modules-4.15.0-13-generic N/A linux-firmware 1.173 Tags: wayland-session bionic Uname: Linux 4.15.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/08/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: XPS 15 9530 dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA08:bd01/08/2015:svnDellInc.:pnXPS159530:pvrA08:rvnDellInc.:rnXPS159530:rvrA08:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: XPS 15 9530 dmi.product.version: A08 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1756877/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1756877] Re: High visual latency in 18.04 when using nouveau
apport information ** Tags added: apport-collected ** Description changed: I am on an Dell xps 9530 laptop and I had recently cleaned installed 17.10. A few days back I decided to updated to 18.04 to check it out and report some bugs. The most annoying bug so far is the insane amount of input latency this update has brought with it to a degree that it makes it impossible to be productive. The issue is observable when using either the mouse or the keyboard. The mouse does not move immediately but it needs a second or two to register and start moving and even then at some point it freezes for half a second at some random point and then moves again. Also if I have two applications side by side and I try an move focus from one to the next at around the edges of each window the mouse freezes for a second and then moves. The keyboard freezes if it hasn't been used for a while and on the first keystroke will take a second to register and for a bonus you get the first keystorke repeated for around 15-30 times. So if you are trying to write "and" will become "aaand" or pressing "ctrl + T" in the browser will open not one but 20 tabs! I am reporting it here cause I am not sure what is causing all this latency (it could be libinput or something else entirely) but please try and fix this as soon as possible!! ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Mar 19 13:04:05 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-02-14 (32 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) SourcePackage: gnome-shell UpgradeStatus: Upgraded to bionic on 2018-03-15 (3 days ago) + --- + ApportVersion: 2.20.9-0ubuntu2 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: giannissc 2031 F pulseaudio + /dev/snd/pcmC1D0p: giannissc 2031 F...m pulseaudio + /dev/snd/controlC1: giannissc 2031 F pulseaudio + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 18.04 + HibernationDevice: RESUME=UUID=999e9885-dbd2-4a45-a45f-998e322f32dc + InstallationDate: Installed on 2018-03-26 (2 days ago) + InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180325) + MachineType: Dell Inc. XPS 15 9530 + Package: linux (not installed) + ProcFB: 0 inteldrmfb + ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-13-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 + ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 + RelatedPackageVersions: + linux-restricted-modules-4.15.0-13-generic N/A + linux-backports-modules-4.15.0-13-generic N/A + linux-firmware 1.173 + Tags: wayland-session bionic + Uname: Linux 4.15.0-13-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 01/08/2015 + dmi.bios.vendor: Dell Inc. + dmi.bios.version: A08 + dmi.board.name: XPS 15 9530 + dmi.board.vendor: Dell Inc. + dmi.board.version: A08 + dmi.chassis.type: 8 + dmi.chassis.vendor: Dell Inc. + dmi.chassis.version: Not Specified + dmi.modalias: dmi:bvnDellInc.:bvrA08:bd01/08/2015:svnDellInc.:pnXPS159530:pvrA08:rvnDellInc.:rnXPS159530:rvrA08:cvnDellInc.:ct8:cvrNotSpecified: + dmi.product.name: XPS 15 9530 + dmi.product.version: A08 + dmi.sys.vendor: Dell Inc. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1756877/+attachment/5095308/+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/1756877 Title: High visual latency in 18.04 when using nouveau Status in linux package in Ubuntu: Confirmed Bug description: I am on an Dell xps 9530 laptop and I had recently cleaned installed 17.10. A few days back I decided to updated to 18.04 to check it out and report some bugs. The most annoying bug so far is the insane amount of input latency this update has brought with it to a degree that it makes it impossible to be productive. The issue is observable when using either the mouse or the keyboard. The mouse does not move immediately but it needs a second or two to register and start moving and even then at some point it freezes for half a second at some random point and then moves again. Also if I have two applications side by side and I try an move focus from one to the next at around the edges of each window the mouse freezes for a second and then moves. The keyboard freezes if it hasn't been used for a while and on the first keystroke will take a second to register and for a bonus you g
[Kernel-packages] [Bug 1759787] Re: Very inaccurate TSC clocksource on HP ProLiant DL380 Gen10 with kernel 4.13
Can you see if this bug also exists in the latest Bionic kernel: https://launchpad.net/ubuntu/+source/linux/4.15.0-13.14/+build/14466170 ** Also affects: linux (Ubuntu Artful) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Artful) Status: New => Triaged ** Changed in: linux (Ubuntu) Status: Confirmed => Triaged ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Changed in: linux (Ubuntu Artful) Importance: Undecided => High ** Tags added: kernel-key -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1759787 Title: Very inaccurate TSC clocksource on HP ProLiant DL380 Gen10 with kernel 4.13 Status in linux package in Ubuntu: Triaged Status in linux source package in Artful: Triaged Bug description: On kernel 4.13.0-37-generic, HP ProLiant DL380 Gen10 systems have been observed with very large clock offsets, as measured by NTP. Over the past few days on one of our production systems, we've used 3 different kernels: https://pastebin.ubuntu.com/p/nDkkgRqdtv/ All of these kernels default to the TSC clocksource, which is supposed to be very reliable on Skylake-X CPUs. On 4.4 (linux-image-generic- lts-xenial) it works as expected; on 3.13 (trusty default kernel) it works a little worse, and on 4.13 (linux-image-generic-hwe-16.04) it is much worse. Today I switched 4.13 from the TSC clocksource to the HPET clocksource and it improved the situation dramatically. I've produced loopstats & peerstats graphs from NTP corresponding to the dates in the pastebin above and placed them at https://people.canonical.com/~paulgear/ntp/. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-4.13.0-37-generic 4.13.0-37.42 ProcVersionSignature: User Name 4.13.0-37.42~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 27 18:26 seq crw-rw 1 root audio 116, 33 Mar 27 18:26 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.14.1-0ubuntu3.27 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: [ 6280.259121] perf: interrupt took too long (2505 > 2500), lowering kernel.perf_event_max_sample_rate to 79750 [10463.378558] perf: interrupt took too long (3133 > 3131), lowering kernel.perf_event_max_sample_rate to 63750 [32314.949747] perf: interrupt took too long (4000 > 3916), lowering kernel.perf_event_max_sample_rate to 5 [129804.100274] clocksource: Switched to clocksource hpet [132747.312089] perf: interrupt took too long (5004 > 5000), lowering kernel.perf_event_max_sample_rate to 39750 Date: Thu Mar 29 07:45:22 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 002: ID 0bda:0329 Realtek Semiconductor Corp. Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 002: ID 0424:2660 Standard Microsystems Corp. Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HPE ProLiant DL380 Gen10 PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-37-generic root=UUID=b33fdcbd-a949-41a0-86d2-03d0c6808284 ro console=tty0 console=ttyS0,115200 RelatedPackageVersions: linux-restricted-modules-4.13.0-37-generic N/A linux-backports-modules-4.13.0-37-generic N/A linux-firmware 1.127.24 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: dmi.bios.date: 02/15/2018 dmi.bios.vendor: HPE dmi.bios.version: U30 dmi.board.name: ProLiant DL380 Gen10 dmi.board.vendor: HPE dmi.chassis.type: 23 dmi.chassis.vendor: HPE dmi.modalias: dmi:bvnHPE:bvrU30:bd02/15/2018:svnHPE:pnProLiantDL380Gen10:pvr:rvnHPE:rnProLiantDL380Gen10:rvr:cvnHPE:ct23:cvr: dmi.product.family: ProLiant dmi.product.name: ProLiant DL380 Gen10 dmi.sys.vendor: HPE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1759787/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1759775] Re: Unable to insert test_bpf module on X-HWE-edge ARM64
** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Incomplete => Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1759775 Title: Unable to insert test_bpf module on X-HWE-edge ARM64 Status in linux package in Ubuntu: Triaged Status in linux-hwe-edge package in Ubuntu: New Bug description: Similar to bug 1751234, but this issue was found on a X-HWE-edge ARM64 node. ubuntu@ms10-35-mcdivittB0-kernel:~$ sudo modprobe test_bpf modprobe: ERROR: could not insert 'test_bpf': Invalid argument ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.15.0-13-generic 4.15.0-13.14~16.04.1 ProcVersionSignature: User Name 4.15.0-13.14~16.04.1-generic 4.15.10 Uname: Linux 4.15.0-13-generic aarch64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: arm64 Date: Thu Mar 29 06:41:45 2018 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-hwe-edge UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1759775/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1759644] Re: [18.04] Regression: wired network does not work upon resume from suspend
Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem? Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.16 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.16-rc7 ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Also affects: linux (Ubuntu Bionic) Importance: High Status: Confirmed ** Changed in: linux (Ubuntu Bionic) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1759644 Title: [18.04] Regression: wired network does not work upon resume from suspend Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Bug description: After upgrade to 18.04 (bionic) I've encountered the following regression: wired network connection does not work, when system is resumed from suspend. Reloading the kernel driver module seems to help: sudo modprobe -r r8169 sudo modprobe r8169 Could this be fixed structurally? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.6-2ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 28 20:08:20 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-01-06 (811 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) IpRoute: default via 192.168.0.1 dev enp5s0 proto dhcp metric 100 169.254.0.0/16 dev enp5s0 scope link metric 1000 192.168.0.0/24 dev enp5s0 proto kernel scope link src 192.168.0.107 metric 100 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=false WWANEnabled=true RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no SourcePackage: network-manager UpgradeStatus: Upgraded to bionic on 2018-03-21 (6 days ago) nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REALAUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE Wired connection 1 7fa0c3a2-6ef0-37fd-9f9e-9029777aaf23 ethernet 1522260260 wo 28 mrt 2018 20:04:20 CEST yes 4294966297no /org/freedesktop/NetworkManager/Settings/3 yes enp5s0 activated /org/freedesktop/NetworkManager/ActiveConnection/1 -- dzente a899e56b-4048-43a8-bc38-9212d0af383b wifi 1493769143 wo 03 mei 2017 01:52:23 CEST yes 0 no /org/freedesktop/NetworkManager/Settings/1 no -- -- -- -- nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH enp5s0 ethernet connected/org/freedesktop/NetworkManager/Devices/4 Wired connection 1 7fa0c3a2-6ef0-37fd-9f9e-9029777aaf23 /org/freedesktop/NetworkManager/ActiveConnection/1 wlp4s0 wifi unavailable /org/freedesktop/NetworkManager/Devices/3 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.6 connected started full enabled enabled disabled enabled enabled --- ApportVersion: 2.20.9-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: alexei 1673 F pulseaudio /dev/snd/controlC0: alexei 1673 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=45af239b-c597-45a1-bb72-3ba25b5ee546 InstallationDate: Installed on 2016-01-06 (812 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: To
[Kernel-packages] [Bug 1759674] Re: Xenial fails to boot because of cryptsetup keyfiles.
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.16 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.16-rc7 ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1759674 Title: Xenial fails to boot because of cryptsetup keyfiles. Status in linux package in Ubuntu: Incomplete Bug description: I always install fresh configurations apart from my working system, on logical volumes of my "victor" logical group. I always use four logical volumes per distribution : boot (clear), root (crypted), home (crypted) and usr (clear), naming them differently from a distribution to another one. Xenial logical volumes are archos (boot), odos (root), oikia (home) and trophe (usr). Only odos and oikia are concerned. To avoid typing cryptsetup keys, I rely on keyfiles. It turns out that, for reasons outside of this report, I did install grub on removable USB keys, and did not alter Windows booting procedure on my hard disk. I also record my key-files on that same device. This means that my USB key is always connected to my PC when I boot Ubuntu. My working system is Ubuntu Trusty with the 3.13.0.106-generic kernel. It does not suffer the bug I'm reporting (I discarted 3.13.0.108-generic for a reason I forgot, but it also works, as regards to the present report). Xenial does not boot, apparently because it hangs waiting for the USB device. The present bug is then a regression bug. I attached the output of "journalctl -xb" in which one can read (I translated french sentences in brakets[]) ### -- L'unité (unit) boot.mount a commencé à démarrer. [unit boot.mount started] mars 25 12:22:37 remi-Vostro-3550 systemd-udevd[666]: Process '/sbin/crda' failed with exit code 249. mars 25 12:22:37 remi-Vostro-3550 kernel: EXT4-fs (dm-12): mounting ext2 file system using the ext4 subsystem mars 25 12:22:37 remi-Vostro-3550 kernel: EXT4-fs (dm-12): mounted filesystem without journal. Opts: (null) mars 25 12:22:37 remi-Vostro-3550 systemd[1]: Mounted /boot. -- Subject: L'unité (unit) boot.mount a terminé son démarrage [unit boot.mount has finished] -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- L'unité (unit) boot.mount a terminé son démarrage, avec le résultat done.[unit boot.mount has finished and reported done] mars 25 12:23:58 remi-Vostro-3550 systemd[1]: dev-disk-by\x2duuid-4146dfad\x2d26f0\x2d4aec\x2d99c3\x2d8ab00c3e4297:-.ckf-victor\x2dodos:1.device: Job dev-disk-by\x2duuid-4146dfad\x2d26f0\x2d4aec\x2d99c3\x2d8ab00c3e4297:-.ckf-victor\x2dodos:1.device/start timed out. mars 25 12:23:58 remi-Vostro-3550 systemd[1]: Timed out waiting for device dev-disk-by\x2duuid-4146dfad\x2d26f0\x2d4aec\x2d99c3\x2d8ab00c3e4297:-.ckf-victor\x2dodos:1.device. -- Subject: L'unité (unit) dev-disk-by\x2duuid-4146dfad\x2d26f0\x2d4aec\x2d99c3\x2d8ab00c3e4297:-.ckf-victor\x2dodos:1.device a échoué [unit dev-disk…-victor\x2dodos:1.device failed] -- Defined-By: systemd For testing purposes, I also installed a Xenial-B on a clear logical volume. I have being able, after boot of Xenial-B, to "cryptdisks_start" crypted logical volumes defined with the crypttab's "noauto" option. Removing the "noauto" option, without mounting the corresponding volumes with fstab, did not prevent Xenial-B to boot, but the same message as the one I mentionned ealier, appeared into the "journalctl -xb" output. I also discovered that cryptdisks_start fails if the USB key happens to be mounted. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-106-generic 3.13.0-106.153 ProcVersionSignature: Ubuntu 3.13.0-106.153-generic 3.13.11-ckt39 Uname: Linux 3.13.0-106-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: remi 3564 F pulseaudio CurrentDesktop: Unity Date: Wed Mar 28 22:15:20 2018 InstallationDate: Installed on 2014-05-30 (1397 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Dell Inc. Vostro 3550 ProcFB: 0 inteldrmfb 1 radeondrmfb ProcKernelCmdLine
[Kernel-packages] [Bug 1759920] Re: linux-image-4.13.0-37-generic locks up at login screen with intel-microcode 3.20180312.0
Could someone else with an affected system verify Erich's report that booting into the linux-image-4.13.0-36-generic kernel while using intel- microcode 3.20180312.0~ubuntu17.10.1 results in a system that does not experience lock ups? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1759920 Title: linux-image-4.13.0-37-generic locks up at login screen with intel- microcode 3.20180312.0 Status in intel-microcode package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in intel-microcode source package in Artful: Confirmed Status in linux source package in Artful: Confirmed Bug description: I don't know if this is a problem with the kernel or the microcode, but we have a significant number of computers in our organization (on both 16.04 and 17.10) that fail if they have both updated. Booting with either linux-image-4.13.0-36-generic or intel-microcode 3.20180108.0+really20170707ubuntu17.10.1 allows all these computers to boot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1759920/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1754584] Re: zfs system process hung on container stop/delete
I am marking this verification-failed as my steps to reproduce this and the ones in step #24 still fail in Bionic, Artful, and Xenial. Bionic: 0.7.5-1ubuntu12 https://paste.ubuntu.com/p/mWVnhdFpRp/ Artful: 0.6.5.11-1ubuntu3.3 https://paste.ubuntu.com/p/RQmxNS7Vxn/ Xenial: 0.6.5.6-0ubuntu20 https://paste.ubuntu.com/p/fZpfWKyYMk/ ** Tags added: verification-failed-artful verification-failed-xenial -- 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/1754584 Title: zfs system process hung on container stop/delete Status in Native ZFS for Linux: New Status in linux package in Ubuntu: Fix Committed Status in zfs-linux package in Ubuntu: Fix Released Status in linux source package in Xenial: In Progress Status in zfs-linux source package in Xenial: Fix Committed Status in linux source package in Artful: In Progress Status in zfs-linux source package in Artful: Fix Committed Status in linux source package in Bionic: Fix Committed Status in zfs-linux source package in Bionic: Fix Released Bug description: == SRU Request [Xenial][Artful] == == Justification == It is possible to hang zfs asynchronous reads if a read to a page that is mmap'd onto the the file being read is the same offset in the mapping as in the file. This is caused by two lock operations on the page. == Fix == Upstream ZFS fix to ensure the page is not double-locked during async I/O of one or more pages. == Testing == Create a zfs pool + zfs file system, run the reproducer program in comment #28 on the zfs filesystem. Without the fix this can lock up, with the fix this runs to completion. == Regression Potential == Minimal, the locking fix addresses a fundamental bug in the locking and this should not affect ZFS read/write I/O with this fix. -- Summary: On a Bionic system running 4.15.0-10-generic, after attempting to build libaio in a Bionic daily container I cannot stop or delete the container. dmesg shows a variety of hung tasks Steps to Reproduce: Use the following script and watch for the the hang. At that point attempt to stop or delete the container: http://paste.ubuntu.com/p/SxfgbxM8v7/ Originally filed against LXD: https://github.com/lxc/lxd/issues/4314 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-10-generic 4.15.0-10.11 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: powersj2414 F pulseaudio /dev/snd/controlC0: powersj2414 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Mar 9 09:19:11 2018 HibernationDevice: RESUME=UUID=40a4eb28-4454-44f0-a377-ea611ce685bb InstallationDate: Installed on 2018-02-19 (17 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214) Lsusb: Bus 001 Device 002: ID 8087:8001 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 002: ID 04f2:b45d Chicony Electronics Co., Ltd Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20BSCTO1WW 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=/vmlinuz-4.15.0-10-generic root=/dev/mapper/ubuntu--vg-root ro RelatedPackageVersions: linux-restricted-modules-4.15.0-10-generic N/A linux-backports-modules-4.15.0-10-generic N/A linux-firmware 1.172 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/13/2017 dmi.bios.vendor: LENOVO dmi.bios.version: N14ET42W (1.20 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BSCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0E50512 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN14ET42W(1.20):bd09/13/2017:svnLENOVO:pn20BSCTO1WW:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BSCTO1WW:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 3rd dmi.product.name: 20BSCTO1WW dmi.product.version: ThinkPad X1 Carbon 3rd dmi.sys.vendor: LENOVO --- ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: powersj1878 F pulseaudio /dev/snd/controlC0: powersj1878 F pulseaudio CurrentDesktop: ubuntu:GNOME
[Kernel-packages] [Bug 1723904] Comment bridged from LTC Bugzilla
--- Comment From yasm...@br.ibm.com 2018-03-29 16:23 EDT--- Some SPR registers were not yet defined in qemu 2.5 and therefore are failing this test. The problem is gone from qemu 2.6. Sending the backport patches to Canonical team. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1723904 Title: ubuntu-kvm-unit test failed with sprs test on ppc64le Status in linux package in Ubuntu: Confirmed Status in qemu package in Ubuntu: Incomplete Bug description: The sprs test has failed on ppc64le This issue can be spotted on Zesty and Xenial. There is no history for this test on Artful $ sudo /bin/bash -c "MIGRATION=yes TESTNAME=sprs TIMEOUT=90s ACCEL= ./powerpc/run powerpc/sprs.elf -smp 1 -append '-w'" run_migration timeout -k 1s --foreground 90s /usr/bin/qemu-system-ppc64 -nodefaults -machine pseries,accel=kvm -bios powerpc/boot_rom.bin -display none -serial stdio -kernel powerpc/sprs.elf -smp 1 -append -w # -initrd /tmp/tmp.RUTL6E2JSi Settings SPRs to 0xcafefacec0debabe... Now migrate the VM, then press a key or send NMI... Checking SPRs... PASS: SPR 3: 0x00debabe <==> 0x00debabe PASS: SPR 13: 0xcafefacec0debabe <==> 0xcafefacec0debabe PASS: SPR 17: 0x00debabe <==> 0x00debabe PASS: SPR 18: 0xc0debabe <==> 0xc0debabe PASS: SPR 19: 0xcafefacec0debabe <==> 0xcafefacec0debabe PASS: SPR 29: 0xcafefacec0debabe <==> 0xcafefacec0debabe FAIL: SPR 61: 0x4054504440541014 <==> 00 PASS: SPR 153:0x0a84 <==> 0x0a84 PASS: SPR 157:0xcfcfc0cf <==> 0xcfcfc0cf FAIL: SPR 159:0xc0debabe <==> 00 PASS: SPR 256:0xc0debabe <==> 0xc0debabe PASS: SPR 259:0xcafefacec0debabe <==> 0xcafefacec0debabe PASS: SPR 274:0xcafefacec0debabe <==> 0xcafefacec0debabe PASS: SPR 275:0xcafefacec0debabe <==> 0xcafefacec0debabe PASS: SPR 769:0xcafefacec0debabe <==> 0xcafefacec0debabe PASS: SPR 770:0xcafefacec006babe <==> 0xcafefacec006babe PASS: SPR 771:0xc0debabe <==> 0xc0debabe PASS: SPR 772:0xc0debabe <==> 0xc0debabe PASS: SPR 773:0xc0debabe <==> 0xc0debabe PASS: SPR 774:0xc0debabe <==> 0xc0debabe PASS: SPR 775:0xc0debabe <==> 0xc0debabe PASS: SPR 776:0xc0debabe <==> 0xc0debabe PASS: SPR 779:0xfa8b1afe <==> 0xfa8b1afe PASS: SPR 780:0xcafefacec0debabc <==> 0xcafefacec0debabc PASS: SPR 781:0xcafefacec0debabe <==> 0xcafefacec0debabe PASS: SPR 782:0xcafefacec0debabe <==> 0xcafefacec0debabe FAIL: SPR 784:0xcafefacec0debabe <==> 00 PASS: SPR 785:0xcafefacec0debabe <==> 0xcafefacec0debabe PASS: SPR 786:0xcafefacec006babe <==> 0xcafefacec006babe PASS: SPR 787:0xc0debabe <==> 0xc0debabe PASS: SPR 788:0xc0debabe <==> 0xc0debabe PASS: SPR 789:0xc0debabe <==> 0xc0debabe PASS: SPR 790:0xc0debabe <==> 0xc0debabe PASS: SPR 791:0xc0debabe <==> 0xc0debabe PASS: SPR 792:0xc0debabe <==> 0xc0debabe PASS: SPR 795:0xfa8b1afe <==> 0xfa8b1afe PASS: SPR 796:0xcafefacec0debabc <==> 0xcafefacec0debabc PASS: SPR 797:0xcafefacec0debabe <==> 0xcafefacec0debabe PASS: SPR 798:0xcafefacec0debabe <==> 0xcafefacec0debabe PASS: SPR 800:0x8000c000 <==> 0x8000c000 PASS: SPR 801:0x8000 <==> 0x8000 PASS: SPR 802:0x8000c000 <==> 0x8000c000 PASS: SPR 803:0x8000 <==> 0x8000 PASS: SPR 804:0xcafefacec0debabe <==> 0xcafefacec0debabe PASS: SPR 805:0xcafefacec0debabc <==> 0xcafefacec0debabc PASS: SPR 806:0x8000c000 <==> 0x8000c000 FAIL: SPR 815:0xcafefacec0debabe <==> 00 SUMMARY: 47 tests, 4 unexpected failures EXIT: STATUS=3 $ qemu-system-ppc --version QEMU emulator version 2.5.0 (Debian 1:2.5+dfsg-5ubuntu10.16), Copyright (c) 2003-2008 Fabrice Bellard ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.10.0-37-generic 4.10.0-37.41~16.04.1 ProcVersionSignature: User Name 4.10.0-37.41~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-37-generic ppc64le ApportVersion: 2.20.1-0ubuntu2.10 Architecture: ppc64el Date: Mon Oct 16 09:16:08 2017 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcLoadAvg: 0.02 0.14 0.17 1/1464 15093 ProcLocks: 1: POSIX AD
[Kernel-packages] [Bug 1754584] Re: zfs system process hung on container stop/delete
@colin - is there a requirement to have a newer kernel and not just a newer zfs-linux for this to be fixed? -- 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/1754584 Title: zfs system process hung on container stop/delete Status in Native ZFS for Linux: New Status in linux package in Ubuntu: Fix Committed Status in zfs-linux package in Ubuntu: Fix Released Status in linux source package in Xenial: In Progress Status in zfs-linux source package in Xenial: Fix Committed Status in linux source package in Artful: In Progress Status in zfs-linux source package in Artful: Fix Committed Status in linux source package in Bionic: Fix Committed Status in zfs-linux source package in Bionic: Fix Released Bug description: == SRU Request [Xenial][Artful] == == Justification == It is possible to hang zfs asynchronous reads if a read to a page that is mmap'd onto the the file being read is the same offset in the mapping as in the file. This is caused by two lock operations on the page. == Fix == Upstream ZFS fix to ensure the page is not double-locked during async I/O of one or more pages. == Testing == Create a zfs pool + zfs file system, run the reproducer program in comment #28 on the zfs filesystem. Without the fix this can lock up, with the fix this runs to completion. == Regression Potential == Minimal, the locking fix addresses a fundamental bug in the locking and this should not affect ZFS read/write I/O with this fix. -- Summary: On a Bionic system running 4.15.0-10-generic, after attempting to build libaio in a Bionic daily container I cannot stop or delete the container. dmesg shows a variety of hung tasks Steps to Reproduce: Use the following script and watch for the the hang. At that point attempt to stop or delete the container: http://paste.ubuntu.com/p/SxfgbxM8v7/ Originally filed against LXD: https://github.com/lxc/lxd/issues/4314 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-10-generic 4.15.0-10.11 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: powersj2414 F pulseaudio /dev/snd/controlC0: powersj2414 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Mar 9 09:19:11 2018 HibernationDevice: RESUME=UUID=40a4eb28-4454-44f0-a377-ea611ce685bb InstallationDate: Installed on 2018-02-19 (17 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214) Lsusb: Bus 001 Device 002: ID 8087:8001 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 002: ID 04f2:b45d Chicony Electronics Co., Ltd Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20BSCTO1WW 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=/vmlinuz-4.15.0-10-generic root=/dev/mapper/ubuntu--vg-root ro RelatedPackageVersions: linux-restricted-modules-4.15.0-10-generic N/A linux-backports-modules-4.15.0-10-generic N/A linux-firmware 1.172 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/13/2017 dmi.bios.vendor: LENOVO dmi.bios.version: N14ET42W (1.20 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BSCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0E50512 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN14ET42W(1.20):bd09/13/2017:svnLENOVO:pn20BSCTO1WW:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BSCTO1WW:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 3rd dmi.product.name: 20BSCTO1WW dmi.product.version: ThinkPad X1 Carbon 3rd dmi.sys.vendor: LENOVO --- ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: powersj1878 F pulseaudio /dev/snd/controlC0: powersj1878 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=40a4eb28-4454-44f0-a377-ea611ce685bb InstallationDate: Installed on 2018-02-19 (17 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214) Lsusb: Bus 001 Device 002: ID 8087:8001 Intel Corp.
[Kernel-packages] [Bug 1759920] Re: linux-image-4.13.0-37-generic locks up at login screen with intel-microcode 3.20180312.0
I have replicated this issue on several systems. I have had the lockup occur at several moments at the lock screen. It usually locks up once you reach the login screen, sometimes when you start typing your password, sometimes when you hit enter after typing in a correct password. I have replicated this issue on systems that have NVIDIA GPUs/Drivers, and those without. The systems I have had this issue on have had 6th or 7th generation i7 Intel processors and all are laptops. I have a desktop with 8th generation Intel, with Linux Kernel 4.13.0-37 and the updated Intel microcode and I am not having this issue. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1759920 Title: linux-image-4.13.0-37-generic locks up at login screen with intel- microcode 3.20180312.0 Status in intel-microcode package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in intel-microcode source package in Artful: Confirmed Status in linux source package in Artful: Confirmed Bug description: I don't know if this is a problem with the kernel or the microcode, but we have a significant number of computers in our organization (on both 16.04 and 17.10) that fail if they have both updated. Booting with either linux-image-4.13.0-36-generic or intel-microcode 3.20180108.0+really20170707ubuntu17.10.1 allows all these computers to boot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1759920/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1759920] Re: linux-image-4.13.0-37-generic locks up at login screen with intel-microcode 3.20180312.0
> Does the lockup happen as soon as you reach the login screen or does it happen once you put in your password and hit enter? It sometimes happens as soon as the login screen shows up, sometimes it happens after you hit enter, and roughly 1:8 tries it will make it all the way to the desktop. > Do you happen to use NVIDIA graphics drivers on the system that's locking up? I believe that all of our systems are running NVIDIA drivers, but we have replicated it on a system not running the NVIDIA driver. > Erich, could you include the output of 'iucode-tool --scan-system'? Most of them report: iucode-tool: system has processor(s) with signature 0x000906e9 We have one that reports: iucode-tool: system has processor(s) with signature 0x000906ea -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1759920 Title: linux-image-4.13.0-37-generic locks up at login screen with intel- microcode 3.20180312.0 Status in intel-microcode package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in intel-microcode source package in Artful: Confirmed Status in linux source package in Artful: Confirmed Bug description: I don't know if this is a problem with the kernel or the microcode, but we have a significant number of computers in our organization (on both 16.04 and 17.10) that fail if they have both updated. Booting with either linux-image-4.13.0-36-generic or intel-microcode 3.20180108.0+really20170707ubuntu17.10.1 allows all these computers to boot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1759920/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
