[Kernel-packages] [Bug 1771222] Re: Using sysctl to permanently disable IPv6 doesn't have any effect
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.17 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.17-rc5 ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1771222 Title: Using sysctl to permanently disable IPv6 doesn't have any effect Status in linux package in Ubuntu: Incomplete Bug description: Shows up in version 18.04 of Ubuntu. I added the following 2 lines in /etc/sysctl.d/99-sysctl.conf and /etc/sysctl.d/01-disable-ipv6.conf: ``` net.ipv6.conf.all.disable_ipv6=1 net.ipv6.conf.default.disable_ipv6=1 ``` Rebooting my machine sets those parameters for "all" and "default" but not for the sysctl options of my network interface: ``` net.ipv6.conf.all.disable_ipv6 = 1 net.ipv6.conf.default.disable_ipv6 = 1 net.ipv6.conf.ens160.disable_ipv6 = 0 ``` I use disable_ipv6 above as an example. I've also verified this with the promote_secondaries option of ipv4. I can always restart systemd-sysctl.service at every boot and this will set net.ipv6.conf.ens160.disable_ipv6 to 1. Unfortunately though this won't work for devices that are hot-plugged. Other info: - version signature: Ubuntu 4.15.0-20.21-generic 4.15.17 - lspci is attached To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1771222/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1771344] Re: Fix enabling bridge MMIO windows
I built a test kernel with commit 13a83eac373c49c0a081cbcd137e79210fe78acd. The test kernel can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1771344 Can you test this kernel and see if it resolves this bug? Note about installing test kernels: • If the test kernel is prior to 4.15(Bionic) you need to install the linux-image and linux-image-extra .deb packages. • If the test kernel is 4.15(Bionic) or newer, you need to install the linux-image-unsigned, linux-modules and linux-modules-extra .deb packages. Thanks in advance! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1771344 Title: Fix enabling bridge MMIO windows Status in The Ubuntu-power-systems project: Triaged Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: == Comment: #0 - Breno Leitao On boot we save the configuration space of PCIe bridges. We do this so when we get an EEH event and everything gets reset that we can restore them. Unfortunately we save this state before we've enabled the MMIO space on the bridges. Hence if we have to reset the bridge when we come back MMIO is not enabled and we end up taking an PE freeze when the driver starts accessing again. This patch forces the memory/MMIO and bus mastering on when restoring bridges on EEH. Ideally we'd do this correctly by saving the configuration space writes later, but that will have to come later in a larger EEH rewrite. For now we have this simple fix. The original bug can be triggered on a boston machine by doing: echo 0x8000 > /sys/kernel/debug/powerpc/PCI0001/err_injct_outbound On boston, this PHB has a PCIe switch on it. Without this patch, you'll see two EEH events, 1 expected and 1 the failure we are fixing here. The second EEH event causes the anything under the PHB to disappear (i.e. the i40e eth). With this patch, only 1 EEH event occurs and devices properly recover. This is commit id 13a83eac373c49c0a081cbcd137e79210fe78acd and should be part of Ubuntu 18.04 kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1771344/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1771276] Re: linux 4.15 currupts ipsec packets over non ethernet devices
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.17 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.17-rc5 ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Status: New => Triaged ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Triaged ** Tags added: kernel-da-key ** Tags added: bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1771276 Title: linux 4.15 currupts ipsec packets over non ethernet devices Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Bug description: Linux 4.15 has a bug that currupts ipsec packets if they are received over a non ethernet interface. This is a serve showstopper bug for me since it breaks my VPN setup and locks me out of my server. see https://wiki.strongswan.org/issues/2571 and https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=87cdf3148b11 since 4.15 is already EOL, the only possibility is backporting the linked patch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1771276/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1771555] Re: dmesg Error seen on system booting from Ubuntu18.04
** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: New => Triaged ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Bionic) Status: New => 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/1771555 Title: dmesg Error seen on system booting from Ubuntu18.04 Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Bug description: Problem Description === dmesg Error seen on system booting from Ubuntu18.04 Is this an issue? [2.601750] integrity: Unable to open file: /etc/keys/x509_ima.der (-2) [2.601754] integrity: Unable to open file: /etc/keys/x509_evm.der (-2) user1@yob45wos:~$ sudo dmesg --level=alert user1@yob45wos:~$ sudo dmesg --level=crit user1@yob45wos:~$ sudo dmesg --level=err [3.382733] integrity: Unable to open file: /etc/keys/x509_ima.der (-2) [3.382738] integrity: Unable to open file: /etc/keys/x509_evm.der (-2) [3.531263] vio vio: uevent: failed to send synthetic uevent [4.521383] nouveau 0004:04:00.0: unknown chipset (14a1) [4.521889] nouveau 0035:03:00.0: unknown chipset (14a1) [4.634336] lpfc 0030:01:00.0: 0:6101 Disabling NVME support: Not supported by firmware: 0 0 [4.634416] lpfc 0030:01:00.0: 0:2574 IO channels: irqs 4 fcp 4 nvme 0 MRQ: 16 [5.646354] lpfc 0030:01:00.1: 1:6101 Disabling NVME support: Not supported by firmware: 0 0 [5.646420] lpfc 0030:01:00.1: 1:2574 IO channels: irqs 4 fcp 4 nvme 0 MRQ: 16 [6.944481] lpfc 0030:01:00.1: 1:1303 Link Up Event x1 received Data: x1 x0 x80 x0 x0 x0 0 [6.944634] lpfc 0030:01:00.0: 0:1303 Link Up Event x1 received Data: x1 x0 x80 x0 x0 x0 0 [ 22.109545] vio vio: uevent: failed to send synthetic uevent user1@yob45wos:~$ > > Problem Description > === > dmesg Error seen on system booting from Ubuntu18.04 > Is this an issue? These messages are seen on every IPL. Is there an issue? > [2.601750] integrity: Unable to open file: /etc/keys/x509_ima.der (-2) > [2.601754] integrity: Unable to open file: /etc/keys/x509_evm.der (-2) These messages should be marked as Warnings instead of Errors as they it supposedly a warning and not an error. This was fixed in LP #1656908 / Bug 150596, but seeing it with 'dmesg --level=err' again in 18.04. * In Ubuntu 17.04 : after reboot getting message in console like Unable to open file: /etc/keys/x509_ima.der (-2) (LP: #1656908) - SAUCE: ima: Downgrade error to warning Mirroring this bug to distro to fix this in the latest kernel. Thank you. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1771555/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1771542] Re: Suspend to idle: Open lid didn't resume
** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Also affects: linux (Ubuntu Artful) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: Confirmed => Triaged ** Changed in: linux (Ubuntu Artful) Status: New => Triaged ** Changed in: linux (Ubuntu Bionic) Status: New => Triaged ** Changed in: linux (Ubuntu Artful) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1771542 Title: Suspend to idle: Open lid didn't resume Status in linux package in Ubuntu: Triaged Status in linux source package in Artful: Triaged Status in linux source package in Bionic: Triaged Bug description: [Impact] Some platforms are set suspend-to-idle (s2idle) as default suspend mode, and then they can't resume the system from opening the lid. [Fix] According a patch sent to 4.17-rc1, which was not be included before 4.15 EOL, so we cherry pick the patch to Ubuntu 4.13 / 4.15 kernel. https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=147a7d9d25ca2551aab15071cb1f048ecd9b7953 [Regression Potential] no regression could be happened To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1771542/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1771546] Re: WARNING: setup_local_APIC+0x27f/0x340
Vivid is now EOL. Can you see if this bug still exists on a supported release, such as Artful or Bionic? ** 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/1771546 Title: WARNING: setup_local_APIC+0x27f/0x340 Status in linux package in Ubuntu: Incomplete Bug description: when load kernel with kexec: /sbin/kexec -p --command-line="root=UUID=5f248d51-af51-4178-bd4d-763d4a6648b3 ro console=ttyS0 console=tty0 irqpoll maxcpus=1 nousb" --initrd=/boot/initrd.img-3.19.0-80-generic /boot/vmlinuz-3.19.0-80-generic and then, triggers a panic: echo c > /proc/sysrq-trigger and now we got reboot into secondary kernel, but at this process, we will got this call trace with 100% reproducible: [14257.863168] Initializing cgroup subsys net_prio [14257.864506] Initializing cgroup subsys hugetlb [14257.865898] CPU: Physical Processor ID: 0 [14257.867035] CPU: Processor Core ID: 0 [14257.869296] mce: CPU supports 0 MCE banks [14257.870495] Last level iTLB entries: 4KB 64, 2MB 8, 4MB 8 [14257.870495] Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0, 1GB 4 [14257.901734] ftrace: allocating 30063 entries in 118 pages [14258.976524] [ cut here ] [14258.983143] WARNING: CPU: 0 PID: 1 at /build/linux-lts-vivid-PmeBs4/linux-lts-vivid-3.19.0/arch/x86/kernel/apic/apic.c:1400 setup_local_APIC+0x27f/0x340() [14259.005863] Modules linked in: [14259.009221] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 3.19.0-80-generic #88~14.04.1-Ubuntu [14259.015315] Hardware name: innotek GmbH VirtualBox/VirtualBox, BIOS VirtualBox 12/01/2006 [14259.021134] 88003191fe18 817b63c3 [14259.036605] 81a8b9d0 88003191fe58 81075d6a 88003191fdfc [14259.055284] 0001 00f0 [14259.061414] Call Trace: [14259.063414] [] dump_stack+0x63/0x81 [14259.067742] [] warn_slowpath_common+0x8a/0xc0 [14259.076934] [] warn_slowpath_null+0x1a/0x20 [14259.085878] [] setup_local_APIC+0x27f/0x340 [14259.101292] [] native_smp_prepare_cpus+0x2f2/0x3af [14259.111873] [] kernel_init_freeable+0xaf/0x1f9 [14259.114495] [] ? rest_init+0x80/0x80 [14259.116783] [] kernel_init+0xe/0xf0 [14259.118990] [] ret_from_fork+0x58/0x90 [14259.121292] [] ? rest_init+0x80/0x80 [14259.123341] ---[ end trace 7384fc8d5897e3f0 ]--- [14259.130738] Spurious LAPIC timer interrupt on cpu 0 [14259.153429] do_IRQ: 0.145 No irq handler for vector (irq -1) [14259.157634] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1 [14259.161002] smpboot: CPU0: Intel(R) Core(TM) i5-6360U CPU @ 2.00GHz (fam: 06, model: 4e, stepping: 03) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1771546/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1771499] Re: package linux-image-extra-4.4.0-122-generic 4.4.0-122.146 failed to install/upgrade: subprocess installed post-removal script was killed by signal (Terminated)
You may need to run the following from a terminal: sudo apt-get install -f sudo apt-get clean sudo apt-get update Then re-install the package or updates. If that does not resolve your issue, please mark the bug as "Confirmed" ** Changed in: linux (Ubuntu) Importance: Undecided => Low ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1771499 Title: package linux-image-extra-4.4.0-122-generic 4.4.0-122.146 failed to install/upgrade: subprocess installed post-removal script was killed by signal (Terminated) Status in linux package in Ubuntu: Incomplete Bug description: I was running bleachbit, it hung and crashed while I was using it to clear out apt. I couldn't finish in the terminal so i did "sudo reboot now". After rebooting I got this error popup requesting I send a bug report. I still couldn't run apt-get autoremove or autoclean so I was prompted with: E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem. I did that an everything went back to normal (that I'm aware of). ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-extra-4.4.0-122-generic 4.4.0-122.146 ProcVersionSignature: Ubuntu 4.13.0-41.46~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-41-generic x86_64 NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.17 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: catherine 2155 F pulseaudio /dev/snd/controlC0: catherine 2155 F pulseaudio Date: Tue May 15 22:17:02 2018 DuplicateSignature: package:linux-image-extra-4.4.0-122-generic:4.4.0-122.146 Removing linux-image-extra-4.4.0-122-generic (4.4.0-122.146) ... run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.4.0-122-generic /boot/vmlinuz-4.4.0-122-generic dpkg: error processing package linux-image-extra-4.4.0-122-generic (--remove): subprocess installed post-removal script was killed by signal (Terminated) ErrorMessage: subprocess installed post-removal script was killed by signal (Terminated) HibernationDevice: RESUME=UUID=d0e88aed-0bea-4ee7-987b-57da2ead80b9 InstallationDate: Installed on 2017-04-12 (398 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-41-generic.efi.signed root=UUID=c199f55c-69ae-45a1-b45a-16652728bf57 ro text PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc N/A SourcePackage: linux Title: package linux-image-extra-4.4.0-122-generic 4.4.0-122.146 failed to install/upgrade: subprocess installed post-removal script was killed by signal (Terminated) UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/30/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P7.10 dmi.board.name: Z170 Gaming-ITX/ac dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP7.10:bd09/30/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ170Gaming-ITX/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1771499/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1771620] Re: Hang on network interface removal in Xen virtual machine
** Package changed: linux-signed (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: New => Triaged ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Bionic) Status: New => 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/1771620 Title: Hang on network interface removal in Xen virtual machine Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Bug description: On a hosting platform running Xen hypervisor, in a virtual machine with Ubuntu 18.04 system and the default kernel from Ubuntu, I try to detach a virtual network interface. On the Xen side, the virtual interface is removed from the VM but the kernel still has the interface. Then a couple of minutes afterwards, the kernel log show this kernel trace: INFO: task xenwatch:108 blocked for more than 120 seconds. Tainted: GW4.15.0-20-generic #21-Ubuntu "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. xenwatchD0 108 2 0x8000 Call Trace: __schedule+0x297/0x8b0 schedule+0x2c/0x80 xennet_remove+0xda/0x1c0 ? wait_woken+0x80/0x80 xenbus_dev_remove+0x54/0xa0 device_release_driver_internal+0x15b/0x220 device_release_driver+0x12/0x20 bus_remove_device+0xec/0x160 ? xenbus_otherend_changed+0x110/0x110 device_del+0x13d/0x360 ? xenbus_otherend_changed+0x110/0x110 ? xenbus_otherend_changed+0x110/0x110 device_unregister+0x1a/0x60 xenbus_dev_changed+0xa3/0x1e0 ? xenwatch_thread+0xcc/0x160 frontend_changed+0x21/0x50 xenwatch_thread+0xc4/0x160 ? wait_woken+0x80/0x80 kthread+0x121/0x140 ? find_watch+0x40/0x40 ? kthread_create_worker_on_cpu+0x70/0x70 ret_from_fork+0x35/0x40 In the git repository of Linux, the commit c2d2e6738a209f0f9dffa2dc8e7292fc45360d61 (xen-netfront: Fix hang on device removal) https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=c2d2e6738a209f0f9dffa2dc8e7292fc45360d61 seems to be related to this situation. I rebuilded the Ubuntu kernel from the package source and applied this patch. Once the VM has booted with the new kernel, I was able to remove network interface without hangs from the kernel. I also booted the VM with the Ubuntu kernel 4.13.0-42-generic and was able to remove the network interface with success. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-20-generic 4.15.0-20.21 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Wed May 16 16:36:06 2018 ProcEnviron: TERM=rxvt-unicode PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1771620/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1771535] Re: synaptics trackpad not detected by libinput
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.17 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.17-rc5 ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1771535 Title: synaptics trackpad not detected by libinput Status in linux package in Ubuntu: Incomplete Bug description: Laptop msi gp62 7rd leopard http://www.linlap.com/msi_gp62_leopard_pro After installing ubuntu 18.04, trackpad does not work at all. External usb mouse does work, though. $ xinput list ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ PixArt HP USB Optical Mouse id=6[slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=7[slave keyboard (3)] $ cat /proc/version_signature Ubuntu 4.15.0-20.21-generic 4.15.17 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-generic 4.15.0.20.23 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: roberto1513 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed May 16 10:17:30 2018 InstallationDate: Installed on 2018-05-15 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Micro-Star International Co., Ltd. GP62 7RD ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=UUID=fb3ba161-3d9b-4fc3-844d-e45adb61a7f1 ro acpi=off quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/07/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E16J9IMS.307 dmi.board.asset.tag: Default string dmi.board.name: MS-16J9 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE16J9IMS.307:bd11/07/2016:svnMicro-StarInternationalCo.,Ltd.:pnGP627RD:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16J9:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A: dmi.product.family: GP dmi.product.name: GP62 7RD dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1771535/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1771620] Re: Hang on network interface removal in Xen virtual machine
** Changed in: linux (Ubuntu) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) ** Changed in: linux (Ubuntu Bionic) Status: Triaged => In Progress ** Changed in: linux (Ubuntu) Status: Triaged => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1771620 Title: Hang on network interface removal in Xen virtual machine Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: On a hosting platform running Xen hypervisor, in a virtual machine with Ubuntu 18.04 system and the default kernel from Ubuntu, I try to detach a virtual network interface. On the Xen side, the virtual interface is removed from the VM but the kernel still has the interface. Then a couple of minutes afterwards, the kernel log show this kernel trace: INFO: task xenwatch:108 blocked for more than 120 seconds. Tainted: GW4.15.0-20-generic #21-Ubuntu "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. xenwatchD0 108 2 0x8000 Call Trace: __schedule+0x297/0x8b0 schedule+0x2c/0x80 xennet_remove+0xda/0x1c0 ? wait_woken+0x80/0x80 xenbus_dev_remove+0x54/0xa0 device_release_driver_internal+0x15b/0x220 device_release_driver+0x12/0x20 bus_remove_device+0xec/0x160 ? xenbus_otherend_changed+0x110/0x110 device_del+0x13d/0x360 ? xenbus_otherend_changed+0x110/0x110 ? xenbus_otherend_changed+0x110/0x110 device_unregister+0x1a/0x60 xenbus_dev_changed+0xa3/0x1e0 ? xenwatch_thread+0xcc/0x160 frontend_changed+0x21/0x50 xenwatch_thread+0xc4/0x160 ? wait_woken+0x80/0x80 kthread+0x121/0x140 ? find_watch+0x40/0x40 ? kthread_create_worker_on_cpu+0x70/0x70 ret_from_fork+0x35/0x40 In the git repository of Linux, the commit c2d2e6738a209f0f9dffa2dc8e7292fc45360d61 (xen-netfront: Fix hang on device removal) https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=c2d2e6738a209f0f9dffa2dc8e7292fc45360d61 seems to be related to this situation. I rebuilded the Ubuntu kernel from the package source and applied this patch. Once the VM has booted with the new kernel, I was able to remove network interface without hangs from the kernel. I also booted the VM with the Ubuntu kernel 4.13.0-42-generic and was able to remove the network interface with success. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-20-generic 4.15.0-20.21 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Wed May 16 16:36:06 2018 ProcEnviron: TERM=rxvt-unicode PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1771620/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1771555] Re: dmesg Error seen on system booting from Ubuntu18.04
** Changed in: linux (Ubuntu) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1771555 Title: dmesg Error seen on system booting from Ubuntu18.04 Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Bug description: Problem Description === dmesg Error seen on system booting from Ubuntu18.04 Is this an issue? [2.601750] integrity: Unable to open file: /etc/keys/x509_ima.der (-2) [2.601754] integrity: Unable to open file: /etc/keys/x509_evm.der (-2) user1@yob45wos:~$ sudo dmesg --level=alert user1@yob45wos:~$ sudo dmesg --level=crit user1@yob45wos:~$ sudo dmesg --level=err [3.382733] integrity: Unable to open file: /etc/keys/x509_ima.der (-2) [3.382738] integrity: Unable to open file: /etc/keys/x509_evm.der (-2) [3.531263] vio vio: uevent: failed to send synthetic uevent [4.521383] nouveau 0004:04:00.0: unknown chipset (14a1) [4.521889] nouveau 0035:03:00.0: unknown chipset (14a1) [4.634336] lpfc 0030:01:00.0: 0:6101 Disabling NVME support: Not supported by firmware: 0 0 [4.634416] lpfc 0030:01:00.0: 0:2574 IO channels: irqs 4 fcp 4 nvme 0 MRQ: 16 [5.646354] lpfc 0030:01:00.1: 1:6101 Disabling NVME support: Not supported by firmware: 0 0 [5.646420] lpfc 0030:01:00.1: 1:2574 IO channels: irqs 4 fcp 4 nvme 0 MRQ: 16 [6.944481] lpfc 0030:01:00.1: 1:1303 Link Up Event x1 received Data: x1 x0 x80 x0 x0 x0 0 [6.944634] lpfc 0030:01:00.0: 0:1303 Link Up Event x1 received Data: x1 x0 x80 x0 x0 x0 0 [ 22.109545] vio vio: uevent: failed to send synthetic uevent user1@yob45wos:~$ > > Problem Description > === > dmesg Error seen on system booting from Ubuntu18.04 > Is this an issue? These messages are seen on every IPL. Is there an issue? > [2.601750] integrity: Unable to open file: /etc/keys/x509_ima.der (-2) > [2.601754] integrity: Unable to open file: /etc/keys/x509_evm.der (-2) These messages should be marked as Warnings instead of Errors as they it supposedly a warning and not an error. This was fixed in LP #1656908 / Bug 150596, but seeing it with 'dmesg --level=err' again in 18.04. * In Ubuntu 17.04 : after reboot getting message in console like Unable to open file: /etc/keys/x509_ima.der (-2) (LP: #1656908) - SAUCE: ima: Downgrade error to warning Mirroring this bug to distro to fix this in the latest kernel. Thank you. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1771555/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1771439] Re: [LTC Test] Ubuntu 18.04: tm_sigreturn failed on P8 compat mode 16.04.04 guest
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Status: New => 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/1771439
Title:
[LTC Test] Ubuntu 18.04: tm_sigreturn failed on P8 compat mode
16.04.04 guest
Status in The Ubuntu-power-systems project:
Triaged
Status in linux package in Ubuntu:
Triaged
Bug description:
This test fails in the same way on a P8 host, so it is nothing to do
with P9.
There have been many TM bugs fixed upstream since 4.4. I would suggest
starting with commit 044215d145a7 ("powerpc/tm: Fix illegal TM state
in signal handler", 2017-08-22) and see if that helps.
The bad thing exception is being raised when executing the following
line:
c004fcfc: b0 04 03 e8 ld r0,1200(r3)
-> c004fd00: a6 23 02 7c mtspr 130,r0
Which is basically restoring TEXASR in the thread.
ISA says "These registers can be written only when in Non-transactional
state" and the MSR is set to be transactional (suspended):
MSR: 800300201033 [ME][RI][IR][DR][LE][SF][HTM][TSU]
That explains why we are getting the "bad thing exception". A mtspr is
being called with a transaction suspended.
I think we need the following commit to have this fixed:
commit 78a3e8889b4b6b99775ed954696ff3e017f5d19b
Author: Cyril Bur
Date: Tue Aug 23 10:46:17 2016 +1000
powerpc: signals: Discard transaction state from signal frames
Userspace can begin and suspend a transaction within the signal
handler which means they might enter sys_rt_sigreturn() with the
processor in suspended state.
sys_rt_sigreturn() wants to restore process context (which may have
been in a transaction before signal delivery). To do this it must
restore TM SPRS. To achieve this, any transaction initiated within the
signal frame must be discarded in order to be able to restore TM SPRs
as TM SPRs can only be manipulated non-transactionally..
>From the PowerPC ISA:
TM Bad Thing Exception [Category: Transactional Memory]
An attempt is made to execute a mtspr targeting a TM register in
other than Non-transactional state.
Not doing so results in a TM Bad Thing:
[12045.221359] Kernel BUG at c0050a40 [verbose debug info
unavailable]
[12045.221470] Unexpected TM Bad Thing exception at c0050a40 (msr
0x201033)
[12045.221540] Oops: Unrecoverable exception, sig: 6 [#1]
[12045.221586] SMP NR_CPUS=2048 NUMA PowerNV
[12045.221634] Modules linked in: xt_CHECKSUM iptable_mangle
ipt_MASQUERADE
nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4
nf_defrag_ipv4
xt_conntrack nf_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp bridge stp
llc ebtable_filter
ebtables ip6table_filter ip6_tables iptable_filter ip_tables x_tables
kvm_hv kvm
uio_pdrv_genirq ipmi_powernv uio powernv_rng ipmi_msghandler autofs4 ses
enclosure
scsi_transport_sas bnx2x ipr mdio libcrc32c
[12045.222167] CPU: 68 PID: 6178 Comm: sigreturnpanic Not tainted 4.7.0
#34
[12045.24] task: c000fce38600 ti: c000fceb4000 task.ti:
c000fceb4000
[12045.93] NIP: c0050a40 LR: c00163bc CTR:
[12045.222361] REGS: c000fceb7ac0 TRAP: 0700 Not tainted (4.7.0)
[12045.222418] MSR: 900300201033 CR:
28444280 XER: 2000
[12045.222625] CFAR: c00163b8 SOFTE: 0 PACATMSCRATCH:
90014280f033
GPR00: 0110b801 c000fceb7d40 c139c100 c000fce390d0
GPR04: 90034280f033
GPR08: b0001033 0001
GPR12: c2926400
GPR16:
GPR20:
GPR24: 398cadd0 398cb470
GPR28: 90034280f033 c000fceb7ea0 0001 c000fce390d0
[12045.223535] NIP [c0050a40] tm_restore_sprs+0xc/0x1c
[12045.223584] LR [c00163bc] tm_recheckpoint+0x5c/0xa0
[12045.223630] Call Trace:
[12045.223655] [c000fceb7d80] [c0026e74]
sys_rt_sigreturn+0x494/0x6c0
[12045.223738] [c000fceb7e30] [c00092e0]
system_call+0x38/0x108
[12045.223806] Instruction dump:
[12045.223841] 7c800164 4e800020 7c0022a6 f80304a8 7c0222a6 f80304b0
7c0122a6 f80304b8
[12045.223955] 4e800020 e80304a8 7c0023a6 e80304b0 <7c0223a6> e80304b8
7c0123a6 4e800020
[12045.224074] ---[ end trace cb8002ee240
[Kernel-packages] [Bug 1771555] Re: dmesg Error seen on system booting from Ubuntu18.04
I built a Bionic test kernel. The test kernel can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1771555 Can you test this kernel and see if it resolves this bug? Note about installing test kernels: • If the test kernel is prior to 4.15(Bionic) you need to install the linux-image and linux-image-extra .deb packages. • If the test kernel is 4.15(Bionic) or newer, you need to install the linux-image-unsigned, linux-modules and linux-modules-extra .deb packages. Thanks in advance! ** Changed in: linux (Ubuntu Bionic) Status: Triaged => In Progress ** Changed in: linux (Ubuntu) Status: Triaged => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1771555 Title: dmesg Error seen on system booting from Ubuntu18.04 Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: Problem Description === dmesg Error seen on system booting from Ubuntu18.04 Is this an issue? [2.601750] integrity: Unable to open file: /etc/keys/x509_ima.der (-2) [2.601754] integrity: Unable to open file: /etc/keys/x509_evm.der (-2) user1@yob45wos:~$ sudo dmesg --level=alert user1@yob45wos:~$ sudo dmesg --level=crit user1@yob45wos:~$ sudo dmesg --level=err [3.382733] integrity: Unable to open file: /etc/keys/x509_ima.der (-2) [3.382738] integrity: Unable to open file: /etc/keys/x509_evm.der (-2) [3.531263] vio vio: uevent: failed to send synthetic uevent [4.521383] nouveau 0004:04:00.0: unknown chipset (14a1) [4.521889] nouveau 0035:03:00.0: unknown chipset (14a1) [4.634336] lpfc 0030:01:00.0: 0:6101 Disabling NVME support: Not supported by firmware: 0 0 [4.634416] lpfc 0030:01:00.0: 0:2574 IO channels: irqs 4 fcp 4 nvme 0 MRQ: 16 [5.646354] lpfc 0030:01:00.1: 1:6101 Disabling NVME support: Not supported by firmware: 0 0 [5.646420] lpfc 0030:01:00.1: 1:2574 IO channels: irqs 4 fcp 4 nvme 0 MRQ: 16 [6.944481] lpfc 0030:01:00.1: 1:1303 Link Up Event x1 received Data: x1 x0 x80 x0 x0 x0 0 [6.944634] lpfc 0030:01:00.0: 0:1303 Link Up Event x1 received Data: x1 x0 x80 x0 x0 x0 0 [ 22.109545] vio vio: uevent: failed to send synthetic uevent user1@yob45wos:~$ > > Problem Description > === > dmesg Error seen on system booting from Ubuntu18.04 > Is this an issue? These messages are seen on every IPL. Is there an issue? > [2.601750] integrity: Unable to open file: /etc/keys/x509_ima.der (-2) > [2.601754] integrity: Unable to open file: /etc/keys/x509_evm.der (-2) These messages should be marked as Warnings instead of Errors as they it supposedly a warning and not an error. This was fixed in LP #1656908 / Bug 150596, but seeing it with 'dmesg --level=err' again in 18.04. * In Ubuntu 17.04 : after reboot getting message in console like Unable to open file: /etc/keys/x509_ima.der (-2) (LP: #1656908) - SAUCE: ima: Downgrade error to warning Mirroring this bug to distro to fix this in the latest kernel. Thank you. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1771555/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1771439] Re: [LTC Test] Ubuntu 18.04: tm_sigreturn failed on P8 compat mode 16.04.04 guest
I built a test kernel with commit 78a3e8889b4b6b99775ed954696ff3e017f5d19b.
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1771439
Can you test this kernel and see if it resolves this bug?
Note about installing test kernels:
• If the test kernel is prior to 4.15(Bionic) you need to install the
linux-image and linux-image-extra .deb packages.
• If the test kernel is 4.15(Bionic) or newer, you need to install the
linux-image-unsigned, linux-modules and linux-modules-extra .deb packages.
Thanks in advance!
** Changed in: linux (Ubuntu)
Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) =>
Joseph Salisbury (jsalisbury)
** Changed in: linux (Ubuntu)
Status: Triaged => In Progress
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Xenial)
Status: New => In Progress
** Changed in: linux (Ubuntu Xenial)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Xenial)
Assignee: (unassigned) => Joseph Salisbury (jsalisbury)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1771439
Title:
[LTC Test] Ubuntu 18.04: tm_sigreturn failed on P8 compat mode
16.04.04 guest
Status in The Ubuntu-power-systems project:
Triaged
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Xenial:
In Progress
Bug description:
This test fails in the same way on a P8 host, so it is nothing to do
with P9.
There have been many TM bugs fixed upstream since 4.4. I would suggest
starting with commit 044215d145a7 ("powerpc/tm: Fix illegal TM state
in signal handler", 2017-08-22) and see if that helps.
The bad thing exception is being raised when executing the following
line:
c004fcfc: b0 04 03 e8 ld r0,1200(r3)
-> c004fd00: a6 23 02 7c mtspr 130,r0
Which is basically restoring TEXASR in the thread.
ISA says "These registers can be written only when in Non-transactional
state" and the MSR is set to be transactional (suspended):
MSR: 800300201033 [ME][RI][IR][DR][LE][SF][HTM][TSU]
That explains why we are getting the "bad thing exception". A mtspr is
being called with a transaction suspended.
I think we need the following commit to have this fixed:
commit 78a3e8889b4b6b99775ed954696ff3e017f5d19b
Author: Cyril Bur
Date: Tue Aug 23 10:46:17 2016 +1000
powerpc: signals: Discard transaction state from signal frames
Userspace can begin and suspend a transaction within the signal
handler which means they might enter sys_rt_sigreturn() with the
processor in suspended state.
sys_rt_sigreturn() wants to restore process context (which may have
been in a transaction before signal delivery). To do this it must
restore TM SPRS. To achieve this, any transaction initiated within the
signal frame must be discarded in order to be able to restore TM SPRs
as TM SPRs can only be manipulated non-transactionally..
>From the PowerPC ISA:
TM Bad Thing Exception [Category: Transactional Memory]
An attempt is made to execute a mtspr targeting a TM register in
other than Non-transactional state.
Not doing so results in a TM Bad Thing:
[12045.221359] Kernel BUG at c0050a40 [verbose debug info
unavailable]
[12045.221470] Unexpected TM Bad Thing exception at c0050a40 (msr
0x201033)
[12045.221540] Oops: Unrecoverable exception, sig: 6 [#1]
[12045.221586] SMP NR_CPUS=2048 NUMA PowerNV
[12045.221634] Modules linked in: xt_CHECKSUM iptable_mangle
ipt_MASQUERADE
nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4
nf_defrag_ipv4
xt_conntrack nf_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp bridge stp
llc ebtable_filter
ebtables ip6table_filter ip6_tables iptable_filter ip_tables x_tables
kvm_hv kvm
uio_pdrv_genirq ipmi_powernv uio powernv_rng ipmi_msghandler autofs4 ses
enclosure
scsi_transport_sas bnx2x ipr mdio libcrc32c
[12045.222167] CPU: 68 PID: 6178 Comm: sigreturnpanic Not tainted 4.7.0
#34
[12045.24] task: c000fce38600 ti: c000fceb4000 task.ti:
c000fceb4000
[12045.93] NIP: c0050a40 LR: c00163bc CTR:
[12045.222361] REGS: c000fceb7ac0 TRAP: 0700 Not tainted (4.7.0)
[12045.222418] MSR: 900300201033 CR:
28444280 XER: 2000
[12045.222625] CFAR: c00163b8 SOFTE: 0 PACATMSCRATCH:
90014280f033
GPR00: 0110b801 c000fceb7d40 c139c100 c000fce390d0
GPR04: 90034280f033
GPR08:
[Kernel-packages] [Bug 1771620] Re: Hang on network interface removal in Xen virtual machine
I built a test kernel with commit c2d2e6738a209f0f9dffa2dc8e7292fc45360d61. The test kernel can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1771620 Can you test this kernel and see if it resolves this bug? Note about installing test kernels: • If the test kernel is prior to 4.15(Bionic) you need to install the linux-image and linux-image-extra .deb packages. • If the test kernel is 4.15(Bionic) or newer, you need to install the linux-image-unsigned, linux-modules and linux-modules-extra .deb packages. Thanks in advance! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1771620 Title: Hang on network interface removal in Xen virtual machine Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: On a hosting platform running Xen hypervisor, in a virtual machine with Ubuntu 18.04 system and the default kernel from Ubuntu, I try to detach a virtual network interface. On the Xen side, the virtual interface is removed from the VM but the kernel still has the interface. Then a couple of minutes afterwards, the kernel log show this kernel trace: INFO: task xenwatch:108 blocked for more than 120 seconds. Tainted: GW4.15.0-20-generic #21-Ubuntu "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. xenwatchD0 108 2 0x8000 Call Trace: __schedule+0x297/0x8b0 schedule+0x2c/0x80 xennet_remove+0xda/0x1c0 ? wait_woken+0x80/0x80 xenbus_dev_remove+0x54/0xa0 device_release_driver_internal+0x15b/0x220 device_release_driver+0x12/0x20 bus_remove_device+0xec/0x160 ? xenbus_otherend_changed+0x110/0x110 device_del+0x13d/0x360 ? xenbus_otherend_changed+0x110/0x110 ? xenbus_otherend_changed+0x110/0x110 device_unregister+0x1a/0x60 xenbus_dev_changed+0xa3/0x1e0 ? xenwatch_thread+0xcc/0x160 frontend_changed+0x21/0x50 xenwatch_thread+0xc4/0x160 ? wait_woken+0x80/0x80 kthread+0x121/0x140 ? find_watch+0x40/0x40 ? kthread_create_worker_on_cpu+0x70/0x70 ret_from_fork+0x35/0x40 In the git repository of Linux, the commit c2d2e6738a209f0f9dffa2dc8e7292fc45360d61 (xen-netfront: Fix hang on device removal) https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=c2d2e6738a209f0f9dffa2dc8e7292fc45360d61 seems to be related to this situation. I rebuilded the Ubuntu kernel from the package source and applied this patch. Once the VM has booted with the new kernel, I was able to remove network interface without hangs from the kernel. I also booted the VM with the Ubuntu kernel 4.13.0-42-generic and was able to remove the network interface with success. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-20-generic 4.15.0-20.21 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Wed May 16 16:36:06 2018 ProcEnviron: TERM=rxvt-unicode PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1771620/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1771222] Re: Using sysctl to permanently disable IPv6 doesn't have any effect
This issue appears to be an upstream bug, since you tested the latest upstream kernel. Would it be possible for you to open an upstream bug report[0]? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug. Please follow the instructions on the wiki page[0]. The first step is to email the appropriate mailing list. If no response is received, then a bug may be opened on bugzilla.kernel.org. Once this bug is reported upstream, please add the tag: 'kernel-bug- reported-upstream'. [0] https://wiki.ubuntu.com/Bugs/Upstream/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/1771222 Title: Using sysctl to permanently disable IPv6 doesn't have any effect Status in linux package in Ubuntu: Confirmed Bug description: Shows up in version 18.04 of Ubuntu. I added the following 2 lines in /etc/sysctl.d/99-sysctl.conf and /etc/sysctl.d/01-disable-ipv6.conf: ``` net.ipv6.conf.all.disable_ipv6=1 net.ipv6.conf.default.disable_ipv6=1 ``` Rebooting my machine sets those parameters for "all" and "default" but not for the sysctl options of my network interface: ``` net.ipv6.conf.all.disable_ipv6 = 1 net.ipv6.conf.default.disable_ipv6 = 1 net.ipv6.conf.ens160.disable_ipv6 = 0 ``` I use disable_ipv6 above as an example. I've also verified this with the promote_secondaries option of ipv4. I can always restart systemd-sysctl.service at every boot and this will set net.ipv6.conf.ens160.disable_ipv6 to 1. Unfortunately though this won't work for devices that are hot-plugged. Other info: - version signature: Ubuntu 4.15.0-20.21-generic 4.15.17 - lspci is attached To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1771222/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1762928] Re: [LTC Test] Ubuntu 18.04: tm_trap_test failed on P8 compat mode guest
** No longer affects: linux (Ubuntu Artful)
** No longer affects: linux (Ubuntu 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/1762928
Title:
[LTC Test] Ubuntu 18.04: tm_trap_test failed on P8 compat mode guest
Status in The Ubuntu-power-systems project:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Bionic:
Fix Released
Bug description:
---Problem Description---
tm_trap_test failed on P8 compat mode [16.04.04 daily build as well bionic ]
guests on a P9 host running bionic final beta version.
Contact Information = srikanth/bssrika...@in.ibm.com
---uname output---
16.04.04 Guest running in P8compat mode:
Linux guest 4.15.0-15-generic #16~16.04.1-Ubuntu SMP Thu Apr 5 12:18:22 UTC
2018 ppc64le ppc64le ppc64le GNU/Linux
18.04 guest running in P8compat mode:
Linux ubuntu 4.15.0-15-generic #16-Ubuntu SMP Wed Apr 4 13:57:51 UTC 2018
ppc64le ppc64le ppc64le GNU/Linux
Machine Type = boston-LC
---Debugger---
A debugger is not configured
---Steps to Reproduce---
1. Log into P9 Ubuntu 18.04 host, take console of guest
`srikanth_ubuntu160404`
2. Run TM selftests
git clone --depth 1 https://github.com/torvalds/linux.git;cd
linux/tools/testing/selftests/powerpc/;git log --oneline -1;make;make -C tm
run_tests
We will observe one of the tm tests failing, mentioned below:
selftests: tm-trap
test: tm_trap_test
tags: git_version:c18bb39
Little-Endian machine detected. Checking if endianness flips inadvertently on
trap in TM... yes!
failure: tm_trap_test
not ok 1..11 selftests: tm-trap [FAIL]
Expected result: All tm selftests should have been pass on the P8 compat
guest.. giventhat we had TM workaround patches in latest Ubuntu BIONIC host
kernel
Stack trace output:
no
Oops output:
no
System Dump Info:
The system is not configured to capture a system dump.
*Additional Instructions for srikanth/bssrika...@in.ibm.com:
-Attach sysctl -a output output to the bug.
== Comment: #2 - SRIKANTH AITHAL - 2018-04-10
01:32:00 ==
== Comment: #3 - SRIKANTH AITHAL - 2018-04-10
01:33:41 ==
== Comment: #4 - SRIKANTH AITHAL - 2018-04-10
01:34:02 ==
Please pick
`1c200e63d055 ("powerpc/tm: Fix endianness flip on trap")`
ie. the commit that the test was written for
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1762928/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1762940] Re: Ubuntu 18.04 install screen becomes blur on Huawei server
** Tags removed: kernel-key ** Tags added: kernel-da-key -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1762940 Title: Ubuntu 18.04 install screen becomes blur on Huawei server Status in linux package in Ubuntu: Triaged Status in install-package source package in Bionic: New Status in linux source package in Bionic: Triaged Bug description: For all(as I know) Huawei servers, the vga adapter are embed in the iBMC chips. Those server can install from ISO manually for 16.04.4 and screen display normally. But for 18.04 ( tested both for daily and final beta)version, the install screen is blur. One of tested server is Huawei 2855 v5, the certification link for 16.04 are https://certification.ubuntu.com/hardware/201707-25596/. Below are key difference of dmesg. It seems might related with DRM. 18.04 install screen is blur dmesg ... [2.039009] fb0: EFI VGA frame buffer device ... [4.178058] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [4.191435] [drm] No driver support for vblank timestamp query. [4.209338] checking generic (9000 30) vs hw (0 0) [4.209384] fbcon: hibmcdrmfb (fb1) is primary device [4.209385] fbcon: Remapping primary device, fb1, to tty 1-63 ... [5.357024] hibmc-drm :07:00.0: fb1: hibmcdrmfb frame buffer device [5.380085] [drm] Initialized hibmc 1.0.0 20160828 for :07:00.0 on minor 0 ... [5.636624] vga16fb: initializing [5.636627] vga16fb: mapped to 0x48a7a1d2 [5.636630] checking generic (9000 30) vs hw (a 1) [5.636676] fb2: VGA16 VGA frame buffer device ... 16.04.4 install screen is fine (no screen blur) dmesg ... [2.000419] fb0: EFI VGA frame buffer device [8.795065] vga16fb: initializing [8.795068] vga16fb: mapped to 0x880a [8.795071] checking generic (9800 30) vs hw (a 1) [8.795121] fb1: VGA16 VGA frame buffer device ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762940/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1762468] Re: Cryptoswap not working in Bionic
** Tags removed: kernel-key ** Tags added: kernel-da-key -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1762468 Title: Cryptoswap not working in Bionic Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Bug description: I have cryptoswap set up both with the 2 GB default swap file and an 8 GB swap partition with 8 GB of ram. However, the system does not use this swap when it should. For example, if I run a little test code which attempts to allocate 10 GB of memory in 1 GB chuncks, the system hangs with no obvious use of swap. E.g. running top shows no swap use before the hang. However, if I replace cryptoswap by standard swap, it works as expected: allocates the requested memory and exits, using swap. Of course, my disk is slow, so this takes some time but it does work. I originally noticed this problem when compiling a very large application. The system would hang on ld. I've checked hardware using memtest and stress. No problems. This took me days to track down but I'm 99% certain now that the problem is with cryptoswap. If I compile with cryptoswap: hang. If I compile with standard swap: no problem. ProblemType: Bug 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 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: weinberg 2425 F pulseaudio /dev/snd/controlC0: weinberg 2425 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Apr 9 11:57:23 2018 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=8d33a538-4ec4-418d-b277-be1a9a1c1113 InstallationDate: Installed on 2018-03-12 (28 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180114) MachineType: LENOVO 20ARA0S100 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic root=UUID=b6683bc1-7dd5-4afd-8e70-f69253403b71 ro quiet splash vt.handoff=1 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 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/19/2014 dmi.bios.vendor: LENOVO dmi.bios.version: GJET74WW (2.24 ) dmi.board.asset.tag: Not Available dmi.board.name: 20ARA0S100 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGJET74WW(2.24):bd03/19/2014:svnLENOVO:pn20ARA0S100:pvrThinkPadT440s:rvnLENOVO:rn20ARA0S100:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T440s dmi.product.name: 20ARA0S100 dmi.product.version: ThinkPad T440s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762468/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1752002] Re: [P9, POwer NV][WSP][DD2.1][Ubuntu 1804][Perf fuzzer] : Call trace is seen while running perf fuzzer (perf:)
** Changed in: linux (Ubuntu) Status: Triaged => Fix Released ** Changed in: linux (Ubuntu Bionic) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1752002 Title: [P9,POwer NV][WSP][DD2.1][Ubuntu 1804][Perf fuzzer] : Call trace is seen while running perf fuzzer (perf:) Status in The Ubuntu-power-systems project: Incomplete Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Bug description: == Comment: #0 - Shriya R. Kulkarni - 2018-02-02 01:21:36 == Problem Description : = Warn on message is seen while running perf fuzzer tests. Machine details : == Hardware : Witherspoon (wsp12) + DD2.1 OS : Ubuntu 1804 uname -a : 4.13.0-32-generic #35~lp1746225 ( Kernel from the bug : https://bugzilla.linux.ibm.com/show_bug.cgi?id=164107#c7 ) Steps to reproduce : Build Kernel : To avoid the kernel crash due to Perf fuzzer , use the kernel mentioned in the link : https://bugzilla.linux.ibm.com/show_bug.cgi?id=164107#c7 #! /bin/bash set -x git clone https://github.com/deater/perf_event_tests.git cd perf_event_tests/include mkdir asm cd asm wget http://9.114.13.132/repo/shriya/perf_regs.h cd ../../lib make sleep 10 cd ../fuzzer make sleep 10 echo 0 > /proc/sys/kernel/nmi_watchdog echo 2 > /proc/sys/kernel/perf_event_paranoid echo 10 > /proc/sys/kernel/perf_event_max_sample_rate ./perf_fuzzer -r 1492143527 Call trace : === [ 329.228031] [ cut here ] [ 329.228039] WARNING: CPU: 43 PID: 9088 at /home/jsalisbury/bugs/lp1746225/ubuntu-artful/kernel/events/core.c:3038 perf_pmu_sched_task+0x170/0x180 [ 329.228040] Modules linked in: ofpart at24 uio_pdrv_genirq uio cmdlinepart powernv_flash mtd ipmi_powernv vmx_crypto ipmi_devintf ipmi_msghandler ibmpowernv opal_prd crct10dif_vpmsum sch_fq_codel ip_tables x_tables autofs4 crc32c_vpmsum lpfc ast i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt mlx5_core fb_sys_fops ttm tg3 nvmet_fc drm ahci nvmet nvme_fc libahci nvme_fabrics mlxfw nvme_core devlink scsi_transport_fc [ 329.228068] CPU: 43 PID: 9088 Comm: perf_fuzzer Not tainted 4.13.0-32-generic #35~lp1746225 [ 329.228070] task: c03f776ac900 task.stack: c03f77728000 [ 329.228071] NIP: c0299b70 LR: c02a4534 CTR: c029bb80 [ 329.228073] REGS: c03f7772b760 TRAP: 0700 Not tainted (4.13.0-32-generic) [ 329.228073] MSR: 9282b033 [ 329.228079] CR: 24008822 XER: [ 329.228080] CFAR: c0299a70 SOFTE: 0 GPR00: c02a4534 c03f7772b9e0 c1606200 c03fef858908 GPR04: c03f776ac900 0001 003fee73 GPR08: c11220d8 0002 GPR12: c029bb80 c7a3d900 GPR16: GPR20: c03f776ad090 c0c71354 GPR24: c03fef716780 003fee73 c03fe69d4200 c03f776ad330 GPR28: c11220d8 0001 c14c6108 c03fef858900 [ 329.228098] NIP [c0299b70] perf_pmu_sched_task+0x170/0x180 [ 329.228100] LR [c02a4534] __perf_event_task_sched_in+0xc4/0x230 [ 329.228101] Call Trace: [ 329.228102] [c03f7772b9e0] [c02a0678] perf_iterate_sb+0x158/0x2a0 (unreliable) [ 329.228105] [c03f7772ba30] [c02a4534] __perf_event_task_sched_in+0xc4/0x230 [ 329.228107] [c03f7772bab0] [c01396dc] finish_task_switch+0x21c/0x310 [ 329.228109] [c03f7772bb60] [c0c71354] __schedule+0x304/0xb80 [ 329.228111] [c03f7772bc40] [c0c71c10] schedule+0x40/0xc0 [ 329.228113] [c03f7772bc60] [c01033f4] do_wait+0x254/0x2e0 [ 329.228115] [c03f7772bcd0] [c0104ac0] kernel_wait4+0xa0/0x1a0 [ 329.228117] [c03f7772bd70] [c0104c24] SyS_wait4+0x64/0xc0 [ 329.228121] [c03f7772be30] [c000b184] system_call+0x58/0x6c [ 329.228121] Instruction dump: [ 329.228123] 3beafea0 7faa4800 409eff18 e8010060 eb610028 ebc10040 7c0803a6 38210050 [ 329.228127] eb81ffe0 eba1ffe8 ebe1fff8 4e800020 <0fe0> 4bbc 6000 6042 [ 329.228131] ---[ end trace 8c46856d314c1811 ]--- [ 375.755943] hrtimer: interrupt took 31601 ns == Comment: #4 - SEETEENA THOUFEEK - 2018-02-05 06:34:09 == == Comment: #5 - SEETEENA THOUFEEK - 2018-02-05 06:36:12 == We have similar issue reported on different distro where Anj
[Kernel-packages] [Bug 1742502] Re: 108 and 109 kernel hangs
** Tags removed: kernel-key ** Tags added: kernel-da-key -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1742502 Title: 108 and 109 kernel hangs Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: Overnight I had 2 of 12 16.04 servers brick with the 108 kernel. They also do not work with 109. They work fine with 104. The other 10 worked fine on both 108 and 109. All are hosted on VMWARE. The two broken ones stop at the same place. I was able to go back to the 104 kernel to get them working and pin the kernel version. Just for fun, I set zswap.enabled=0 and they both crashed with kthread starved for jiffies. They are both multi-processor with lots of ram and disk. I have a task from the Ubuntu Kernel team to try this with 'nopti'. I'll report back. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1742502/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1761796] Re: Rebooting bionic fails with hardware error on ProLiant DL360 Gen9
I started a kernel bisect between v4.15-rc6 and v4.15-rc7. The kernel
bisect will require testing of about 6 test kernels.
I built the first test kernel, up to the following commit:
d8887f1c7289848e74c92bd4322789a9cd7de699
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1761796
Can you test that kernel and report back if it has the bug or not? I
will build the next test kernel based on your test results.
Thanks in advance
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1761796
Title:
Rebooting bionic fails with hardware error on ProLiant DL360 Gen9
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Bionic:
Confirmed
Bug description:
From an ephemeral environment in an HPGen9, the machine fails to
reboot when the ephemeral environment is Bionic (it does not fail in
Xenial).
Full log from the moment the 'sudo reboot' was executed:
https://pastebin.ubuntu.com/p/hyD6VY7CbW/
The actual failure is:
[ OK ] Stopped Remount Root and Kernel File Systems.
[ OK ] Reached target Shutdown.
[ OK ] Reached target Final Step.
Starting Reboot...
[ OK ] Stopped Monitoring of LVM2 mirrors,…sing dmeventd or progress
polling.
Stopping LVM2 metadata daemon...
[ OK ] Stopped LVM2 metadata daemon.
[ 257.160527] {1}[Hardware Error]: Hardware error from APEI Generic Hardware
Error Source: 1
[ 257.160530] {1}[Hardware Error]: event severity: fatal
[ 257.160533] {1}[Hardware Error]: Error 0, type: fatal
[ 257.160534] {1}[Hardware Error]: section_type: PCIe error
[ 257.160536] {1}[Hardware Error]: port_type: 4, root port
[ 257.160541] {1}[Hardware Error]: version: 1.16
[ 257.160544] {1}[Hardware Error]: command: 0x6010, status: 0x0143
[ 257.160546] {1}[Hardware Error]: device_id: :00:01.0
[ 257.160547] {1}[Hardware Error]: slot: 0
[ 257.160548] {1}[Hardware Error]: secondary_bus: 0x03
[ 257.160550] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x6f02
[ 257.160552] {1}[Hardware Error]: class_code: 040600
[ 257.160554] {1}[Hardware Error]: bridge: secondary_status: 0x2000,
control: 0x0003
[ 257.160556] {1}[Hardware Error]: Error 1, type: fatal
[ 257.160557] {1}[Hardware Error]: section_type: PCIe error
[ 257.160559] {1}[Hardware Error]: port_type: 4, root port
[ 257.160560] {1}[Hardware Error]: version: 1.16
[ 257.160562] {1}[Hardware Error]: command: 0x6010, status: 0x0143
[ 257.160564] {1}[Hardware Error]: device_id: :00:01.0
[ 257.160565] {1}[Hardware Error]: slot: 0
[ 257.160566] {1}[Hardware Error]: secondary_bus: 0x03
[ 257.160567] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x6f02
[ 257.160568] {1}[Hardware Error]: class_code: 040600
[ 257.160569] {1}[Hardware Error]: bridge: secondary_status: 0x2000,
control: 0x0003
[ 257.160570] Kernel panic - not syncing: Fatal hardware error!
[ 257.200091] Kernel Offset: 0x2540 from 0x8100 (relocation
range: 0x8000-0xbfff)
[ 257.815850] ERST: [Firmware Warn]: Firmware does not respond in time.
---
AlsaDevices:
total 0
crw-rw 1 root audio 116, 33 Apr 6 17:40 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.9-0ubuntu2
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord':
'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/timer'] failed
with exit code 1:
CRDA: N/A
DistroRelease: Ubuntu 18.04
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
MachineType: HP ProLiant DL360 Gen9
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Package: linux (not installed)
PciMultimedia:
ProcEnviron:
TERM=screen-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=C.UTF-8
SHELL=/bin/bash
ProcFB: 0 EFI VGA
ProcKernelCmdLine:
BOOT_IMAGE=username/amd64/ga-18.04/bionic/daily/boot-kernel nomodeset ro
root=squash:http://10.245.136.6:5248/images/username/amd64/ga-18.04/bionic/daily/squashfs
ip=hostname:BOOTIF ip6=off overlayroot=tmpfs overlayroot_cfgdisk=disabled
cc:{datasource_list: [MAAS]}end_cc
cloud-config-url=http://10.245.136.6:5240/MAAS/metadata/latest/by-id/hqsxdc/?op=get_preseed
apparmor=0 log_host=10.245.136.6 log_port=514 --- console=ttyS1,115200n8
BOOTIF=01-94:18:82:7a:82:c8
ProcVersionSignature: User Name 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 N/A
RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
Tags: bionic uec-images
Uname: Linux 4.15.0-13-generic x86_64
UpgradeStatus: No upgrade
[Kernel-packages] [Bug 1758205] Re: Ubuntu 18.04 NVMe disks are not displayed on lsblk and /dev/disk/by-path (NVMe / Bolt ) (systemd?)
Actually commit 8a30ecc6e0ecbb9ae95daf499b2680b885ed0349 is in bionic as
of 4.15.0-13:
1a3abe0db677 Revert "nvme: create 'slaves' and 'holders' entries for
hidden controllers"
git describe --contains 1a3abe0db677
Ubuntu-4.15.0-13.14~323
Can you see if this bug still exists with the latest Bionic kernel, that should
be neweter than -13?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1758205
Title:
Ubuntu 18.04 NVMe disks are not displayed on lsblk and /dev/disk/by-
path (NVMe / Bolt ) (systemd?)
Status in The Ubuntu-power-systems project:
In Progress
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Bionic:
In Progress
Bug description:
---Problem Description---
Bolt based NVMe disks (namespaces) are not displayed on lsblk and
/dev/disk/by-path
# nvme list
Node SN Model
Namespace Usage Format FW Rev
- --
/dev/nvme0n1 S3RVNA0J600206 PCIe3 1.6TB NVMe Flash Adapter II x8
1 28.67 GB / 28.67 GB 4 KiB + 0 B MN12MN12
/dev/nvme0n10S3RVNA0J600206 PCIe3 1.6TB NVMe Flash Adapter II x8
10 28.67 GB / 28.67 GB 4 KiB + 0 B MN12MN12
/dev/nvme0n11S3RVNA0J600206 PCIe3 1.6TB NVMe Flash Adapter II x8
11 28.67 GB / 28.67 GB 4 KiB + 0 B MN12MN12
/dev/nvme0n12S3RVNA0J600206 PCIe3 1.6TB NVMe Flash Adapter II x8
12 28.67 GB / 28.67 GB 4 KiB + 0 B MN12MN12
/dev/nvme0n13S3RVNA0J600206 PCIe3 1.6TB NVMe Flash Adapter II x8
13 28.67 GB / 28.67 GB 4 KiB + 0 B MN12MN12
/dev/nvme0n14S3RVNA0J600206 PCIe3 1.6TB NVMe Flash Adapter II x8
14 28.67 GB / 28.67 GB 4 KiB + 0 B MN12MN12
/dev/nvme0n15S3RVNA0J600206 PCIe3 1.6TB NVMe Flash Adapter II x8
15 28.67 GB / 28.67 GB 4 KiB + 0 B MN12MN12
/dev/nvme0n16S3RVNA0J600206 PCIe3 1.6TB NVMe Flash Adapter II x8
16 28.67 GB / 28.67 GB 4 KiB + 0 B MN12MN12
/dev/nvme0n17S3RVNA0J600206 PCIe3 1.6TB NVMe Flash Adapter II x8
17 28.67 GB / 28.67 GB 4 KiB + 0 B MN12MN12
/dev/nvme0n18S3RVNA0J600206 PCIe3 1.6TB NVMe Flash Adapter II x8
18 28.67 GB / 28.67 GB 4 KiB + 0 B MN12MN12
/dev/nvme0n19S3RVNA0J600206 PCIe3 1.6TB NVMe Flash Adapter II x8
19 28.67 GB / 28.67 GB 4 KiB + 0 B MN12MN12
/dev/nvme0n2 S3RVNA0J600206 PCIe3 1.6TB NVMe Flash Adapter II x8
2 28.67 GB / 28.67 GB 4 KiB + 0 B MN12MN12
/dev/nvme0n20S3RVNA0J600206 PCIe3 1.6TB NVMe Flash Adapter II x8
20 28.67 GB / 28.67 GB 4 KiB + 0 B MN12MN12
/dev/nvme0n21S3RVNA0J600206 PCIe3 1.6TB NVMe Flash Adapter II x8
21 28.67 GB / 28.67 GB 4 KiB + 0 B MN12MN12
/dev/nvme0n22S3RVNA0J600206 PCIe3 1.6TB NVMe Flash Adapter II x8
22 28.67 GB / 28.67 GB 4 KiB + 0 B MN12MN12
/dev/nvme0n23S3RVNA0J600206 PCIe3 1.6TB NVMe Flash Adapter II x8
23 28.67 GB / 28.67 GB 4 KiB + 0 B MN12MN12
/dev/nvme0n24S3RVNA0J600206 PCIe3 1.6TB NVMe Flash Adapter II x8
24 28.67 GB / 28.67 GB 4 KiB + 0 B MN12MN12
/dev/nvme0n25S3RVNA0J600206 PCIe3 1.6TB NVMe Flash Adapter II x8
25 28.67 GB / 28.67 GB 4 KiB + 0 B MN12MN12
/dev/nvme0n26S3RVNA0J600206 PCIe3 1.6TB NVMe Flash Adapter II x8
26 28.67 GB / 28.67 GB 4 KiB + 0 B MN12MN12
/dev/nvme0n27S3RVNA0J600206 PCIe3 1.6TB NVMe Flash Adapter II x8
27 28.67 GB / 28.67 GB 4 KiB + 0 B MN12MN12
/dev/nvme0n28S3RVNA0J600206 PCIe3 1.6TB NVMe Flash Adapter II x8
28 28.67 GB / 28.67 GB 4 KiB + 0 B MN12MN12
/dev/nvme0n29S3RVNA0J600206 PCIe3 1.6TB NVMe Flash Adapter II x8
29 28.67 GB / 28.67 GB 4 KiB + 0 B MN12MN12
/dev/nvme0n3 S3RVNA0J600206 PCIe3 1.6TB NVMe Flash Adapter II x8
3 28.67 GB / 28.67 GB 4 KiB + 0 B MN12MN12
/dev/nvme0n30S3RVNA0J600206 PCIe3 1.6TB NVMe Flash Adapter II x8
30 28.67 GB / 28.67 GB 4 KiB + 0 B MN12MN12
/dev/nvme0n31S3RVNA0J600206 PCIe3 1.6TB NVMe Flash Adapter II x8
31 28.67 GB / 28.67 GB 4 KiB + 0 B MN12MN12
/dev/nvme0n32S3RVNA0J600206 PCIe3 1.6TB NVMe Flash Adapter II x8
32 28.67 GB / 28.67 GB 4 KiB + 0 B MN12MN12
/de
[Kernel-packages] [Bug 1768431] Re: Request to revert SAUCE patches in the 18.04 SRU and update with upstream version
I built a Bionic test kernel with your diff patch and the three new patches on top. The test kernel can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1768431 Can you test this kernel and see if it resolves this bug? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1768431 Title: Request to revert SAUCE patches in the 18.04 SRU and update with upstream version Status in The Ubuntu-power-systems project: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: == Comment: #0 - UMA KRISHNAN - 2018-04-30 14:41:30 == ---Problem Description--- Request to revert SAUCE patches from 18.04 and apply the patches from next/master. Below set of cxlflash patches were submitted to Canonical after they were sent to the community. Based on review comments, there has been minor changes from that version. This BZ is to request reverting those SAUCE patches with the ones that are queued in next/master tree for 4.18. - SAUCE: cxlflash: Preserve number of interrupts for master contexts - SAUCE: cxlflash: Avoid clobbering context control register value - SAUCE: cxlflash: Add argument identifier names - SAUCE: cxlflash: Introduce OCXL backend - SAUCE: cxlflash: Hardware AFU for OCXL - SAUCE: cxlflash: Read host function configuration - SAUCE: cxlflash: Setup function acTag range - SAUCE: cxlflash: Read host AFU configuration - SAUCE: cxlflash: Setup AFU acTag range - SAUCE: cxlflash: Setup AFU PASID - SAUCE: cxlflash: Adapter context support for OCXL - SAUCE: cxlflash: Use IDR to manage adapter contexts - SAUCE: cxlflash: Support adapter file descriptors for OCXL - SAUCE: cxlflash: Support adapter context discovery - SAUCE: cxlflash: Support image reload policy modification - SAUCE: cxlflash: MMIO map the AFU - SAUCE: cxlflash: Support starting an adapter context - SAUCE: cxlflash: Support process specific mappings - SAUCE: cxlflash: Support AFU state toggling - SAUCE: cxlflash: Support reading adapter VPD data - SAUCE: cxlflash: Setup function OCXL link - SAUCE: cxlflash: Setup OCXL transaction layer - SAUCE: cxlflash: Support process element lifecycle - SAUCE: cxlflash: Support AFU interrupt management - SAUCE: cxlflash: Support AFU interrupt mapping and registration - SAUCE: cxlflash: Support starting user contexts - SAUCE: cxlflash: Support adapter context polling - SAUCE: cxlflash: Support adapter context reading - SAUCE: cxlflash: Support adapter context mmap and release - SAUCE: cxlflash: Support file descriptor mapping - SAUCE: cxlflash: Introduce object handle fop - SAUCE: cxlflash: Setup LISNs for user contexts - SAUCE: cxlflash: Setup LISNs for master contexts - SAUCE: cxlflash: Update synchronous interrupt status bits - SAUCE: cxlflash: Introduce OCXL context state machine - SAUCE: cxlflash: Register for translation errors - SAUCE: cxlflash: Support AFU reset - SAUCE: cxlflash: Enable OCXL operations Also, there are 3 additional patches added to end of this series that we would like to request being pulled into the SRU stream. These 3 patches address bug fixes. The commit ids for the patches queued in next/master tree are, 768999d6b1eadc6a13b1fba1886f1708f433d82b scsi: cxlflash: Preserve number of interrupts for master contexts 6c2b116dd38e3fbda10c3e3d5ac80ea7442e4f4d scsi: cxlflash: Avoid clobbering context control register value fcace1d5e11f518c6f91dd245fa1ac37393b47d3 scsi: cxlflash: Add argument identifier names 863dbdc0552f8bc100df48bb231089c382b89004 scsi: cxlflash: Introduce OCXL backend f2180daa83950ff8183f70b1b78d67cb13fd90b2 scsi: cxlflash: Hardware AFU for OCXL 1042535633554592d7d95a9cf83d2940803689e0 scsi: cxlflash: Read host function configuration ba84823a8b448207659753ae4f9c8b956923bada scsi: cxlflash: Setup function acTag range f55ced2dcd00ab257a2bb25eee619b75cda24817 scsi: cxlflash: Read host AFU configuration c5a8fec11278e245136c7f696c914269c58a6000 scsi: cxlflash: Setup AFU acTag range b42d68d728a63337bcb7860b59e6458946d94a84 scsi: cxlflash: Setup AFU PASID de25ec59a75802584aac97aed05fd94094dbbb58 scsi: cxlflash: Adapter context support for OCXL a76fc993e399f54b37f46107a31e817c779f2b82 scsi: cxlflash: Use IDR to manage adapter contexts 09f35da5fe218baf73f7b4efd281e2c19490512c scsi: cxlflash: Support adapter file descriptors for OCXL 17f9335bc59c1cf8f93617eee137e745abd71a3f scsi: cxlflash: Support adapter context discovery a5cfe355f23d4410d69af0e5b196b095463a0b4b scsi: cxlflash: Support image reload policy modification 0c62e7c091a4e0a01a7c6027fe719625ab2f521e scsi: cxlflash: MMIO map the AFU f39bab766ea4f0b3d5888fdd7d66babd7bef3966 scsi: cxlflash: Support starting an adapter context bef2014e8bd6391988b588acb969b48133072f17 scsi: cxlflash: Support
[Kernel-packages] [Bug 1771439] Re: [LTC Test] Ubuntu 18.04: tm_sigreturn failed on P8 compat mode 16.04.04 guest
SRU request submitted:
https://lists.ubuntu.com/archives/kernel-team/2018-May/092537.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/1771439
Title:
[LTC Test] Ubuntu 18.04: tm_sigreturn failed on P8 compat mode
16.04.04 guest
Status in The Ubuntu-power-systems project:
In Progress
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Xenial:
In Progress
Bug description:
This test fails in the same way on a P8 host, so it is nothing to do
with P9.
There have been many TM bugs fixed upstream since 4.4. I would suggest
starting with commit 044215d145a7 ("powerpc/tm: Fix illegal TM state
in signal handler", 2017-08-22) and see if that helps.
The bad thing exception is being raised when executing the following
line:
c004fcfc: b0 04 03 e8 ld r0,1200(r3)
-> c004fd00: a6 23 02 7c mtspr 130,r0
Which is basically restoring TEXASR in the thread.
ISA says "These registers can be written only when in Non-transactional
state" and the MSR is set to be transactional (suspended):
MSR: 800300201033 [ME][RI][IR][DR][LE][SF][HTM][TSU]
That explains why we are getting the "bad thing exception". A mtspr is
being called with a transaction suspended.
I think we need the following commit to have this fixed:
commit 78a3e8889b4b6b99775ed954696ff3e017f5d19b
Author: Cyril Bur
Date: Tue Aug 23 10:46:17 2016 +1000
powerpc: signals: Discard transaction state from signal frames
Userspace can begin and suspend a transaction within the signal
handler which means they might enter sys_rt_sigreturn() with the
processor in suspended state.
sys_rt_sigreturn() wants to restore process context (which may have
been in a transaction before signal delivery). To do this it must
restore TM SPRS. To achieve this, any transaction initiated within the
signal frame must be discarded in order to be able to restore TM SPRs
as TM SPRs can only be manipulated non-transactionally..
>From the PowerPC ISA:
TM Bad Thing Exception [Category: Transactional Memory]
An attempt is made to execute a mtspr targeting a TM register in
other than Non-transactional state.
Not doing so results in a TM Bad Thing:
[12045.221359] Kernel BUG at c0050a40 [verbose debug info
unavailable]
[12045.221470] Unexpected TM Bad Thing exception at c0050a40 (msr
0x201033)
[12045.221540] Oops: Unrecoverable exception, sig: 6 [#1]
[12045.221586] SMP NR_CPUS=2048 NUMA PowerNV
[12045.221634] Modules linked in: xt_CHECKSUM iptable_mangle
ipt_MASQUERADE
nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4
nf_defrag_ipv4
xt_conntrack nf_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp bridge stp
llc ebtable_filter
ebtables ip6table_filter ip6_tables iptable_filter ip_tables x_tables
kvm_hv kvm
uio_pdrv_genirq ipmi_powernv uio powernv_rng ipmi_msghandler autofs4 ses
enclosure
scsi_transport_sas bnx2x ipr mdio libcrc32c
[12045.222167] CPU: 68 PID: 6178 Comm: sigreturnpanic Not tainted 4.7.0
#34
[12045.24] task: c000fce38600 ti: c000fceb4000 task.ti:
c000fceb4000
[12045.93] NIP: c0050a40 LR: c00163bc CTR:
[12045.222361] REGS: c000fceb7ac0 TRAP: 0700 Not tainted (4.7.0)
[12045.222418] MSR: 900300201033 CR:
28444280 XER: 2000
[12045.222625] CFAR: c00163b8 SOFTE: 0 PACATMSCRATCH:
90014280f033
GPR00: 0110b801 c000fceb7d40 c139c100 c000fce390d0
GPR04: 90034280f033
GPR08: b0001033 0001
GPR12: c2926400
GPR16:
GPR20:
GPR24: 398cadd0 398cb470
GPR28: 90034280f033 c000fceb7ea0 0001 c000fce390d0
[12045.223535] NIP [c0050a40] tm_restore_sprs+0xc/0x1c
[12045.223584] LR [c00163bc] tm_recheckpoint+0x5c/0xa0
[12045.223630] Call Trace:
[12045.223655] [c000fceb7d80] [c0026e74]
sys_rt_sigreturn+0x494/0x6c0
[12045.223738] [c000fceb7e30] [c00092e0]
system_call+0x38/0x108
[12045.223806] Instruction dump:
[12045.223841] 7c800164 4e800020 7c0022a6 f80304a8 7c0222a6 f80304b0
7c0122a6 f80304b8
[12045.223955] 4e800020 e80304a8 7c0023a6 e80304b0 <7c0223a6> e80304b8
7c0123a6 4e800020
[12045.224074
[Kernel-packages] [Bug 1761796] Re: Rebooting bionic fails with hardware error on ProLiant DL360 Gen9
** Changed in: linux (Ubuntu)
Status: Confirmed => In Progress
** Changed in: linux (Ubuntu Bionic)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1761796
Title:
Rebooting bionic fails with hardware error on ProLiant DL360 Gen9
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Bionic:
In Progress
Bug description:
From an ephemeral environment in an HPGen9, the machine fails to
reboot when the ephemeral environment is Bionic (it does not fail in
Xenial).
Full log from the moment the 'sudo reboot' was executed:
https://pastebin.ubuntu.com/p/hyD6VY7CbW/
The actual failure is:
[ OK ] Stopped Remount Root and Kernel File Systems.
[ OK ] Reached target Shutdown.
[ OK ] Reached target Final Step.
Starting Reboot...
[ OK ] Stopped Monitoring of LVM2 mirrors,…sing dmeventd or progress
polling.
Stopping LVM2 metadata daemon...
[ OK ] Stopped LVM2 metadata daemon.
[ 257.160527] {1}[Hardware Error]: Hardware error from APEI Generic Hardware
Error Source: 1
[ 257.160530] {1}[Hardware Error]: event severity: fatal
[ 257.160533] {1}[Hardware Error]: Error 0, type: fatal
[ 257.160534] {1}[Hardware Error]: section_type: PCIe error
[ 257.160536] {1}[Hardware Error]: port_type: 4, root port
[ 257.160541] {1}[Hardware Error]: version: 1.16
[ 257.160544] {1}[Hardware Error]: command: 0x6010, status: 0x0143
[ 257.160546] {1}[Hardware Error]: device_id: :00:01.0
[ 257.160547] {1}[Hardware Error]: slot: 0
[ 257.160548] {1}[Hardware Error]: secondary_bus: 0x03
[ 257.160550] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x6f02
[ 257.160552] {1}[Hardware Error]: class_code: 040600
[ 257.160554] {1}[Hardware Error]: bridge: secondary_status: 0x2000,
control: 0x0003
[ 257.160556] {1}[Hardware Error]: Error 1, type: fatal
[ 257.160557] {1}[Hardware Error]: section_type: PCIe error
[ 257.160559] {1}[Hardware Error]: port_type: 4, root port
[ 257.160560] {1}[Hardware Error]: version: 1.16
[ 257.160562] {1}[Hardware Error]: command: 0x6010, status: 0x0143
[ 257.160564] {1}[Hardware Error]: device_id: :00:01.0
[ 257.160565] {1}[Hardware Error]: slot: 0
[ 257.160566] {1}[Hardware Error]: secondary_bus: 0x03
[ 257.160567] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x6f02
[ 257.160568] {1}[Hardware Error]: class_code: 040600
[ 257.160569] {1}[Hardware Error]: bridge: secondary_status: 0x2000,
control: 0x0003
[ 257.160570] Kernel panic - not syncing: Fatal hardware error!
[ 257.200091] Kernel Offset: 0x2540 from 0x8100 (relocation
range: 0x8000-0xbfff)
[ 257.815850] ERST: [Firmware Warn]: Firmware does not respond in time.
---
AlsaDevices:
total 0
crw-rw 1 root audio 116, 33 Apr 6 17:40 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.9-0ubuntu2
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord':
'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/timer'] failed
with exit code 1:
CRDA: N/A
DistroRelease: Ubuntu 18.04
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
MachineType: HP ProLiant DL360 Gen9
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Package: linux (not installed)
PciMultimedia:
ProcEnviron:
TERM=screen-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=C.UTF-8
SHELL=/bin/bash
ProcFB: 0 EFI VGA
ProcKernelCmdLine:
BOOT_IMAGE=username/amd64/ga-18.04/bionic/daily/boot-kernel nomodeset ro
root=squash:http://10.245.136.6:5248/images/username/amd64/ga-18.04/bionic/daily/squashfs
ip=hostname:BOOTIF ip6=off overlayroot=tmpfs overlayroot_cfgdisk=disabled
cc:{datasource_list: [MAAS]}end_cc
cloud-config-url=http://10.245.136.6:5240/MAAS/metadata/latest/by-id/hqsxdc/?op=get_preseed
apparmor=0 log_host=10.245.136.6 log_port=514 --- console=ttyS1,115200n8
BOOTIF=01-94:18:82:7a:82:c8
ProcVersionSignature: User Name 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 N/A
RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
Tags: bionic uec-images
Uname: Linux 4.15.0-13-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video
_MarkForUpload: True
dmi.bios.date: 09/13/2016
dmi.bios.vendor: HP
dmi.bios.version: P89
dmi.board.name: ProLiant DL360 Gen9
dmi.board.vendor: HP
dmi.chassis.type: 23
dmi.chassis
[Kernel-packages] [Bug 1768898] Re: smp_call_function_single/many core hangs with stop4 alone
SRU request submitted:
https://lists.ubuntu.com/archives/kernel-team/2018-May/092540.html
** Description changed:
+ == SRU Justification ==
+ IBM reports that this bug occurs with stop4 which results in soft lockups/rcu
stalls.
+ This is a kernel synchronization issue leading to a dead lock.
+
+ This bug was introduced by commit 7bc54b652f13 in v4.8-rc1. This
+ regression is fixed by mainline commit c0f7f5b6c6910.
+
+ == Fix ==
+ c0f7f5b6c6910 ("cpufreq: powernv: Fix hardlockup due to synchronous smp_call
in timer interrupt")
+
+ == Regression Potential ==
+ Low. Fixes current regression. Cc'd to upstream stable, so it has had
+ additon upstream review.
+
+ == Test Case ==
+ A test kernel was built with this patch and tested by the original bug
reporter.
+ The bug reporter states the test kernel resolved the bug.
+
+
Recently we discovered this bug occurs just alone with stop4 which
results in soft lockups/rcu stalls.
```
root@ltc-boston125:~# [15523.619395] systemd[1]: systemd-journald.service:
Processes still around after final SIGKILL. Entering failed mode.
[15523.619508] systemd[1]: systemd-journald.service: Failed with result
'timeout'.
[15523.619769] systemd[1]: Failed to start Journal Service.
[15523.620618] systemd[1]: systemd-journald.service: Service has no hold-off
time, scheduling restart.
[15523.620774] systemd[1]: systemd-journald.service: Scheduled restart job,
restart counter is at 21.
[15523.621462] systemd[1]: Stopped Journal Service.
[15523.621635] systemd[1]: systemd-journald.service: Found left-over process
1561 (systemd-journal) in control group while starting unit. Ignoring.
[15523.621756] systemd[1]: This usually indicates unclean termination of a
previous run, or service implementation deficiencies.
[15523.621888] systemd[1]: systemd-journald.service: Found left-over process
69060 (systemd-journal) in control group while starting unit. Ignoring.
[15523.622029] systemd[1]: This usually indica[15541.629904] INFO: rcu_sched
self-detected stall on CPU
- [15541.629958]60-: (2 GPs behind) idle=146/142/0
softirq=300022/300022 fqs=999069
+ [15541.629958]60-: (2 GPs behind) idle=146/142/0
softirq=300022/300022 fqs=999069
[15541.630046] (t=2415546 jiffies g=184827 c=184826 q=57111)
[15541.630101] NMI backtrace for cpu 60
[15541.630135] CPU: 60 PID: 4810 Comm: tlbie_test Tainted: G L
4.15.0-15-generic #16-Ubuntu
[15541.630207] Call Trace:
[15541.630232] [c000201a1da96b00] [c0ceb35c] dump_stack+0xb0/0xf4
(unreliable)
[15541.630298] [c000201a1da96b40] [c0cf4d48]
nmi_cpu_backtrace+0x1f8/0x200
[15541.630363] [c000201a1da96bd0] [c0cf4ee8]
nmi_trigger_cpumask_backtrace+0x198/0x1f0
[15541.630429] [c000201a1da96c60] [c002f2d8]
arch_trigger_cpumask_backtrace+0x28/0x40
[15541.630495] [c000201a1da96c80] [c01a913c]
rcu_dump_cpu_stacks+0xf4/0x158
[15541.630560] [c000201a1da96cd0] [c01a81e8]
rcu_check_callbacks+0x8e8/0xb40
[15541.630625] [c000201a1da96e00] [c01b64a8]
update_process_times+0x48/0x90
[15541.630689] [c000201a1da96e30] [c01ce1f4]
tick_sched_handle.isra.5+0x34/0xd0
[15541.630753] [c000201a1da96e60] [c01ce2f0]
tick_sched_timer+0x60/0xe0
[15541.630818] [c000201a1da96ea0] [c01b7054]
__hrtimer_run_queues+0x144/0x370
[15541.630883] [c000201a1da96f20] [c01b7fac]
hrtimer_interrupt+0xfc/0x350
[15541.630948] [c000201a1da96ff0] [c00248f0]
__timer_interrupt+0x90/0x260
[15541.631013] [c000201a1da97040] [c0024d08] timer_interrupt+0x98/0xe0
[15541.631069] [c000201a1da97070] [c0009014]
decrementer_common+0x114/0x120
[15541.631135] --- interrupt: 901 at smp_call_function_single+0x134/0x180
[15541.631135] LR = smp_call_function_single+0x110/0x180
[15541.631230] [c000201a1da973d0] [c01d55e0]
smp_call_function_any+0x180/0x250
[15541.631294] [c000201a1da97430] [c0acd3e8]
gpstate_timer_handler+0x1e8/0x580
[15541.631359] [c000201a1da974e0] [c01b46b0] call_timer_fn+0x50/0x1c0
[15541.631433] [c000201a1da97560] [c01b4958] expire_timers+0x138/0x1f0
[15541.631488] [c000201a1da975d0] [c01b4bf8]
run_timer_softirq+0x1e8/0x270
[15541.631553] [c000201a1da97670] [c0d0d6c8] __do_softirq+0x158/0x3e4
[15541.631608] [c000201a1da97750] [c0114be8] irq_exit+0xe8/0x120
[15541.631663] [c000201a1da97770] [c0024d0c] timer_interrupt+0x9c/0xe0
[15541.631718] [c000201a1da977a0] [c0009014]
decrementer_common+0x114/0x120
[15541.631784] --- interrupt: 901 at smp_call_function_many+0x330/0x450
[15541.631784] LR = smp_call_function_many+0x324/0x450
[15541.631879] [c000201a1da97b00] [c0075f18] pmdp_invalidate+0x98/0xe0
[15541.631935] [c000201a1da97b30] [c03a1120]
change_huge_pmd+0xe0/0x270
[15541.632000] [c000201a1da97ba0] [c0349
[Kernel-packages] [Bug 1771439] Re: [LTC Test] Ubuntu 18.04: tm_sigreturn failed on P8 compat mode 16.04.04 guest
** Description changed:
- This test fails in the same way on a P8 host, so it is nothing to do
- with P9.
+
+ == SRU Justification ==
+ IBM is seeing tm_sigreturn test failures on P8 and P9 hosts. The bad thing
+ exception is being raised when executing the following line:
+
+ c004fcfc: b0 04 03 e8 ld r0,1200(r3)
+ -> c004fd00: a6 23 02 7c mtspr 130,r0
+
+ Which is basically restoring TEXASR in the thread.
+
+ ISA says "These registers can be written only when in Non-transactional
+ state" and the MSR is set to be transactional (suspended):
+
+ MSR: 800300201033 [ME][RI][IR][DR][LE][SF][HTM][TSU]
+
+ That explains why they are getting the "bad thing exception". A mtspr is
+ being called with a transaction suspended.
+
+ This test failure is fixed by upstream commit 78a3e8889b4b.
+ Upstream commit 78a3e8889b4b is in mainline as of 4.8-rc5.
+
+ == Fix ==
+ 78a3e8889b4b ("powerpc: signals: Discard transaction state from signal
frames")
+
+ == Regression Potential ==
+ Low. Specific to powerpc.
+
+ == Test Case ==
+ A test kernel was built with this patch and tested by the original bug
reporter.
+ The bug reporter states the test kernel resolved the bug.
+
+
+
+ This test fails in the same way on a P8 host, so it is nothing to do with P9.
There have been many TM bugs fixed upstream since 4.4. I would suggest
starting with commit 044215d145a7 ("powerpc/tm: Fix illegal TM state in
signal handler", 2017-08-22) and see if that helps.
The bad thing exception is being raised when executing the following
line:
- c004fcfc: b0 04 03 e8 ld r0,1200(r3)
- -> c004fd00: a6 23 02 7c mtspr 130,r0
+ c004fcfc: b0 04 03 e8 ld r0,1200(r3)
+ -> c004fd00: a6 23 02 7c mtspr 130,r0
Which is basically restoring TEXASR in the thread.
-
- ISA says "These registers can be written only when in Non-transactional
state" and the MSR is set to be transactional (suspended):
+ ISA says "These registers can be written only when in Non-transactional
+ state" and the MSR is set to be transactional (suspended):
MSR: 800300201033 [ME][RI][IR][DR][LE][SF][HTM][TSU]
That explains why we are getting the "bad thing exception". A mtspr is
being called with a transaction suspended.
I think we need the following commit to have this fixed:
commit 78a3e8889b4b6b99775ed954696ff3e017f5d19b
Author: Cyril Bur
Date: Tue Aug 23 10:46:17 2016 +1000
- powerpc: signals: Discard transaction state from signal frames
-
- Userspace can begin and suspend a transaction within the signal
- handler which means they might enter sys_rt_sigreturn() with the
- processor in suspended state.
-
- sys_rt_sigreturn() wants to restore process context (which may have
- been in a transaction before signal delivery). To do this it must
- restore TM SPRS. To achieve this, any transaction initiated within the
- signal frame must be discarded in order to be able to restore TM SPRs
- as TM SPRs can only be manipulated non-transactionally..
- >From the PowerPC ISA:
- TM Bad Thing Exception [Category: Transactional Memory]
-An attempt is made to execute a mtspr targeting a TM register in
-other than Non-transactional state.
-
- Not doing so results in a TM Bad Thing:
- [12045.221359] Kernel BUG at c0050a40 [verbose debug info
unavailable]
- [12045.221470] Unexpected TM Bad Thing exception at c0050a40 (msr
0x201033)
- [12045.221540] Oops: Unrecoverable exception, sig: 6 [#1]
- [12045.221586] SMP NR_CPUS=2048 NUMA PowerNV
- [12045.221634] Modules linked in: xt_CHECKSUM iptable_mangle
ipt_MASQUERADE
- nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4
nf_defrag_ipv4
- xt_conntrack nf_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp bridge stp
llc ebtable_filter
- ebtables ip6table_filter ip6_tables iptable_filter ip_tables x_tables
kvm_hv kvm
- uio_pdrv_genirq ipmi_powernv uio powernv_rng ipmi_msghandler autofs4 ses
enclosure
- scsi_transport_sas bnx2x ipr mdio libcrc32c
- [12045.222167] CPU: 68 PID: 6178 Comm: sigreturnpanic Not tainted 4.7.0
#34
- [12045.24] task: c000fce38600 ti: c000fceb4000 task.ti:
c000fceb4000
- [12045.93] NIP: c0050a40 LR: c00163bc CTR:
- [12045.222361] REGS: c000fceb7ac0 TRAP: 0700 Not tainted (4.7.0)
- [12045.222418] MSR: 900300201033 CR:
28444280 XER: 2000
- [12045.222625] CFAR: c00163b8 SOFTE: 0 PACATMSCRATCH:
90014280f033
- GPR00: 0110b801 c000fceb7d40 c139c100 c000fce390d0
- GPR04: 90034280f033
- GPR08: b0001033 0001
- GPR12: 00
[Kernel-packages] [Bug 1770849] Re: Ubuntu 18.04 kernel crashed while in degraded mode
SRU request submitted: https://lists.ubuntu.com/archives/kernel-team/2018-May/092543.html ** Description changed: + == SRU Justification == + IBM reports a kernel crash with Bionic while in degraded mode(Degraded + cores). + + IBM created a patch to resolve this bug and has submitted it upstream: + https://lists.ozlabs.org/pipermail/linuxppc-dev/2018-May/172835.html + + The patch has not laned in mainline as of yet, so it is being submitted + as a SAUCE patch. + + + == Fix == + UBUNTU: SAUCE: powerpc/perf: Fix memory allocation for core-imc based on num_possible_cpus() + + == Regression Potential == + Low. Limited to powerpc. + + == Test Case == + A test kernel was built with this patch and tested by the original bug reporter. + The bug reporter states the test kernel resolved the bug. + + + kernel crash The system is going down NOW! Sent SIGTERM to all processes Sent SIGKILL to all processes [ 64.713154] kexec_core: Starting new kernel [ 156.281504630,5] OPAL: Switch to big-endian OS [ 158.440263459,5] OPAL: Switch to little-endian OS [1.889211] Unable to handle kernel paging request for data at address 0x678e549df9e2878c [1.889289] Faulting instruction address: 0xc038aa30 [1.889344] Oops: Kernel access of bad area, sig: 11 [#1] [1.889386] LE SMP NR_CPUS=2048 NUMA PowerNV [1.889432] Modules linked in: [1.889468] CPU: 3 PID: 1 Comm: swapper/0 Not tainted 4.15.0-20-generic #21-Ubuntu [1.889545] NIP: c038aa30 LR: c038aa1c CTR: [1.889608] REGS: c03fed193840 TRAP: 0380 Not tainted (4.15.0-20-generic) [1.889670] MSR: 90009033 CR: 28000884 XER: 2004 - [1.889742] CFAR: c0016e1c SOFTE: 1 - [1.889742] GPR00: c038a914 c03fed193ac0 c16eae00 0001 - [1.889742] GPR04: c03fd754c7f8 002c 0001 002b - [1.889742] GPR08: 678e549df9e28874 fffe - [1.889742] GPR12: 28000888 cfa82100 c000d3b8 - [1.889742] GPR16: - [1.889742] GPR20: a78e54a22eb64f8c - [1.889742] GPR24: c03fd754c800 678e549df9e2878c 0300 c02bd05c - [1.889742] GPR28: c03fed01ea00 014080c0 c03fd754c800 c03fed01ea00 + [1.889742] CFAR: c0016e1c SOFTE: 1 + [1.889742] GPR00: c038a914 c03fed193ac0 c16eae00 0001 + [1.889742] GPR04: c03fd754c7f8 002c 0001 002b + [1.889742] GPR08: 678e549df9e28874 fffe + [1.889742] GPR12: 28000888 cfa82100 c000d3b8 + [1.889742] GPR16: + [1.889742] GPR20: a78e54a22eb64f8c + [1.889742] GPR24: c03fd754c800 678e549df9e2878c 0300 c02bd05c + [1.889742] GPR28: c03fed01ea00 014080c0 c03fd754c800 c03fed01ea00 [1.890286] NIP [c038aa30] kmem_cache_alloc_trace+0x2d0/0x330 [1.890340] LR [c038aa1c] kmem_cache_alloc_trace+0x2bc/0x330 [1.890391] Call Trace: [1.890416] [c03fed193ac0] [c038a914] kmem_cache_alloc_trace+0x1b4/0x330 (unreliable) [1.890491] [c03fed193b30] [c02bd05c] pmu_dev_alloc+0x3c/0x170 [1.890547] [c03fed193bb0] [c10e3210] perf_event_sysfs_init+0x8c/0xf0 [1.890611] [c03fed193c40] [c000d144] do_one_initcall+0x64/0x1d0 [1.890676] [c03fed193d00] [c10b4400] kernel_init_freeable+0x280/0x374 [1.890740] [c03fed193dc0] [c000d3d4] kernel_init+0x24/0x160 [1.890795] [c03fed193e30] [c000b528] ret_from_kernel_thread+0x5c/0xb4 [1.890857] Instruction dump: - [1.890909] 7c97ba78 fb210038 38a50001 7f19ba78 fb29 f8aa 4bc8c3f1 6000 - [1.890978] 7fb8b840 419e0028 e93f0022 e91f0140 <7d59482a> 7d394a14 7d4a4278 7fa95040 + [1.890909] 7c97ba78 fb210038 38a50001 7f19ba78 fb29 f8aa 4bc8c3f1 6000 + [1.890978] 7fb8b840 419e0028 e93f0022 e91f0140 <7d59482a> 7d394a14 7d4a4278 7fa95040 [1.891050] ---[ end trace 41b3fe7a827f3888 ]--- - [2.900027] + [2.900027] [3.900175] Kernel panic - not syncing: Attempted to kill init! exitcode=0x000b - [3.900175] + [3.900175] [4.71868[ 175.340944355,5] OPAL: Reboot request... 2] Rebooting in 10 seconds.. This fix is needed to resolve the crash https://lists.ozlabs.org/pipermail/linuxppc-dev/2018-May/172835.html -- You received this bug notification because you are a membe
[Kernel-packages] [Bug 1771620] Re: Hang on network interface removal in Xen virtual machine
SRU request submitted:
https://lists.ubuntu.com/archives/kernel-team/2018-May/092545.html
** Description changed:
+
+ == SRU Justification ==
+ Upstream commit 5b5971df3bc2 introduced a regression in v4.15-rc2. This
+ regression causes a hang on network interface removal in Xen virtual machine.
+
+ This regression is fixed by commit c2d2e6738a209 in v4.16-rc4.
+
+ == Fix ==
+ c2d2e6738a20 ("xen-netfront: Fix hang on device removal")
+
+ == Regression Potential ==
+ Low. Fixes a current regression and specific to Xen.
+
+ == Test Case ==
+ A test kernel was built with this patch and tested by the original bug
reporter.
+ The bug reporter states the test kernel resolved the bug.
+
+
On a hosting platform running Xen hypervisor, in a virtual machine with
Ubuntu 18.04 system and the default kernel from Ubuntu, I try to detach
a virtual network interface. On the Xen side, the virtual interface is
removed from the VM but the kernel still has the interface. Then a
couple of minutes afterwards, the kernel log show this kernel trace:
INFO: task xenwatch:108 blocked for more than 120 seconds.
- Tainted: GW4.15.0-20-generic #21-Ubuntu
+ Tainted: GW4.15.0-20-generic #21-Ubuntu
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
xenwatchD0 108 2 0x8000
Call Trace:
- __schedule+0x297/0x8b0
- schedule+0x2c/0x80
- xennet_remove+0xda/0x1c0
- ? wait_woken+0x80/0x80
- xenbus_dev_remove+0x54/0xa0
- device_release_driver_internal+0x15b/0x220
- device_release_driver+0x12/0x20
- bus_remove_device+0xec/0x160
- ? xenbus_otherend_changed+0x110/0x110
- device_del+0x13d/0x360
- ? xenbus_otherend_changed+0x110/0x110
- ? xenbus_otherend_changed+0x110/0x110
- device_unregister+0x1a/0x60
- xenbus_dev_changed+0xa3/0x1e0
- ? xenwatch_thread+0xcc/0x160
- frontend_changed+0x21/0x50
- xenwatch_thread+0xc4/0x160
- ? wait_woken+0x80/0x80
- kthread+0x121/0x140
- ? find_watch+0x40/0x40
- ? kthread_create_worker_on_cpu+0x70/0x70
- ret_from_fork+0x35/0x40
+ __schedule+0x297/0x8b0
+ schedule+0x2c/0x80
+ xennet_remove+0xda/0x1c0
+ ? wait_woken+0x80/0x80
+ xenbus_dev_remove+0x54/0xa0
+ device_release_driver_internal+0x15b/0x220
+ device_release_driver+0x12/0x20
+ bus_remove_device+0xec/0x160
+ ? xenbus_otherend_changed+0x110/0x110
+ device_del+0x13d/0x360
+ ? xenbus_otherend_changed+0x110/0x110
+ ? xenbus_otherend_changed+0x110/0x110
+ device_unregister+0x1a/0x60
+ xenbus_dev_changed+0xa3/0x1e0
+ ? xenwatch_thread+0xcc/0x160
+ frontend_changed+0x21/0x50
+ xenwatch_thread+0xc4/0x160
+ ? wait_woken+0x80/0x80
+ kthread+0x121/0x140
+ ? find_watch+0x40/0x40
+ ? kthread_create_worker_on_cpu+0x70/0x70
+ ret_from_fork+0x35/0x40
In the git repository of Linux, the commit
c2d2e6738a209f0f9dffa2dc8e7292fc45360d61 (xen-netfront: Fix hang on
device removal)
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=c2d2e6738a209f0f9dffa2dc8e7292fc45360d61
seems to be related to this situation.
I rebuilded the Ubuntu kernel from the package source and applied this
patch. Once the VM has booted with the new kernel, I was able to remove
network interface without hangs from the kernel.
I also booted the VM with the Ubuntu kernel 4.13.0-42-generic and was
able to remove the network interface with success.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-20-generic 4.15.0-20.21
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
Date: Wed May 16 16:36:06 2018
ProcEnviron:
- TERM=rxvt-unicode
- PATH=(custom, no user)
- LANG=en_US.UTF-8
- SHELL=/bin/bash
+ TERM=rxvt-unicode
+ PATH=(custom, no user)
+ LANG=en_US.UTF-8
+ SHELL=/bin/bash
SourcePackage: linux-signed
UpgradeStatus: No upgrade log present (probably fresh install)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1771620
Title:
Hang on network interface removal in Xen virtual machine
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Bionic:
In Progress
Bug description:
== SRU Justification ==
Upstream commit 5b5971df3bc2 introduced a regression in v4.15-rc2. This
regression causes a hang on network interface removal in Xen virtual machine.
This regression is fixed by commit c2d2e6738a209 in v4.16-rc4.
== Fix ==
c2d2e6738a20 ("xen-netfront: Fix hang on device removal")
== Regression Potential ==
Low. Fixes a current regression and specific to Xen.
== Test Case ==
A test kernel was built with this patch and tested by the original bug
reporter.
The bug reporter states the test kernel resolved the bug.
On a hosting platform running Xen hypervisor, in a virtual machine
with U
[Kernel-packages] [Bug 1771075] Re: General Protection fault in inotify (fixed upstream)
I will submit an SRU request to have that commit included in the affected Ubuntu kernels. Then the fix will be available in the next set of kernel updates. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1771075 Title: General Protection fault in inotify (fixed upstream) Status in linux package in Ubuntu: In Progress Status in linux source package in Artful: In Progress Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: In Progress Bug description: We've run into some issues where upgrading the kernel from a 4.10 series to a 4.13 series on Ubuntu 16.04 hosts that make heavy use of inotify causes panics and lockups in the kernel in inotify-related code. Our particular use case seemed to hit these at a rate of one every 30 minutes or so when serving up production traffic. Unfortunately, I have been unable to replicate the issue so far with a simulated load-testing environment. When the issue occurs, we get dmesg entries like "BUG: soft lockup - CPU#0 stuck for 22s!" or "General protection fault: [#1] SMP PTI". In the soft lockup case, the host is still up but all I/O operations stall indefinitely (e.g. typing "sync" into the console will hang forever). In the protection fault case, the system reboots. I've attached dmesg output from the two cases to this bugreport. We have noticed the issue with the following kernels: - linux-image-4.13.0-1013-gcp - linux-image-4.13.0-1015-gcp - linux-image-4.13.0-36-generic We did _not_ have the issue with - linux-image-4.10.0-32-generic I've submitted this bug report from a system which should be configured identically to our production hosts that were having issue (the affected hosts were immediately rolled back to 4.10). This bug appears to have been fixed upstream as of 4.17-rc3 in this commit: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=d90a10e2444ba5a351fa695917258ff4c5709fa5 I would guess that perhaps this patch should be backported into both the 4.13 HWE and GCP Ubuntu kernel series? Thanks, KJ ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.13.0-1013-gcp 4.13.0-1013.17 ProcVersionSignature: Ubuntu 4.13.0-1013.17-gcp 4.13.16 Uname: Linux 4.13.0-1013-gcp x86_64 ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 Date: Mon May 14 07:58:29 2018 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-gcp UpgradeStatus: No upgrade log present (probably fresh install) --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 10 07:57 seq crw-rw 1 root audio 116, 33 May 10 07:57 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A DistroRelease: Ubuntu 16.04 IwConfig: Error: [Errno 2] No such file or directory Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Google Google Compute Engine Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-32-generic root=UUID=73ea38ed-7fcd-4871-8afa-17d36f4e4bfc ro scsi_mod.use_blk_mq=Y console=ttyS0 ProcVersionSignature: Ubuntu 4.10.0-32.36~16.04.1-generic 4.10.17 RelatedPackageVersions: linux-restricted-modules-4.10.0-32-generic N/A linux-backports-modules-4.10.0-32-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory Tags: xenial uec-images xenial uec-images Uname: Linux 4.10.0-32-generic x86_64 UnreportableReason: The report belongs to a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: WifiSyslog: _MarkForUpload: False dmi.bios.date: 01/01/2011 dmi.bios.vendor: Google dmi.bios.version: Google dmi.board.asset.tag: 98BEC19B-1DEB-1A9F-1146-C6E4D8577ADB dmi.board.name: Google Compute Engine dmi.board.vendor: Google dmi.chassis.type: 1 dmi.chassis.vendor: Google dmi.modalias: dmi:bvnGoogle:bvrGoogle:bd01/01/2011:svnGoogle:pnGoogleComputeEngine:pvr:rvnGoogle:rnGoogleComputeEngine:rvr:cvnGoogle:ct1:cvr: dmi.product.name: Google Compute Engine dmi.sys.vendor: Google To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1771075/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.
[Kernel-packages] [Bug 1723799] Re: touchpad not working after resume on kernel 4.13
Can those affected by this bug in Bionic open a new 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/1723799 Title: touchpad not working after resume on kernel 4.13 Status in linux package in Ubuntu: Fix Released Status in linux source package in Artful: Fix Released Bug description: I'm running Ubuntu 17.10 [Ubuntu Artful Aardvark (development branch) installed from beta 2 ISO with latest apt update && apt dist-upgrade] with kernel: $ uname -rv 4.13.0-16-generic #19-Ubuntu SMP Wed Oct 11 18:35:14 UTC 2017 and after putting system to sleep via closing laptop lid and then resuming it by opening laptop lid makes touchpad not working. Kernel message buffer contains following error message after resume: PM: Device i2c-SYNA3105:00 failed to resume async: error -11 and I can find other people reporting similar issue on other distros: https://bugzilla.redhat.com/show_bug.cgi?id=1431375 https://bugzilla.kernel.org/show_bug.cgi?id=195949 https://bugzilla.redhat.com/show_bug.cgi?id=1442699 like in those other bug reports I can workaround the problem by: rmmod i2c-hid modprobe i2c-hid in systemd-suspend.service(8) post scripts. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-extra-4.13.0-16-generic 4.13.0-16.19 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mkucharski 1367 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Oct 15 22:49:38 2017 HibernationDevice: RESUME=UUID=aa9acb18-b692-4020-9811-d58e5c8b8857 InstallationDate: Installed on 2017-10-06 (9 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 05c8:03a1 Cheng Uei Precision Industry Co., Ltd (Foxlink) Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Timi TM1607 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-16-generic N/A linux-backports-modules-4.13.0-16-generic N/A linux-firmware 1.169 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/07/2017 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: XMAKB200P0100 dmi.board.asset.tag: Any dmi.board.name: TM1607 dmi.board.vendor: Timi dmi.board.version: MP dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Timi dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvrXMAKB200P0100:bd05/07/2017:svnTimi:pnTM1607:pvr:rvnTimi:rnTM1607:rvrMP:cvnTimi:ct10:cvrChassisVersion: dmi.product.family: Timibook dmi.product.name: TM1607 dmi.sys.vendor: Timi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1723799/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1771844] Re: powerpc/livepatch: Implement reliable stack tracing for the consistency model
** Changed in: linux (Ubuntu) Importance: Undecided => High ** Changed in: linux (Ubuntu) Status: New => Triaged ** Also affects: linux (Ubuntu Cosmic) Importance: High Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) Status: Triaged ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux (Ubuntu Cosmic) Status: Triaged => In Progress ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) ** Changed in: linux (Ubuntu Cosmic) Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) => Joseph Salisbury (jsalisbury) ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1771844 Title: powerpc/livepatch: Implement reliable stack tracing for the consistency model Status in The Ubuntu-power-systems project: Triaged Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: In Progress Bug description: == Comment: #0 - Kamalesh Babulal - 2018-05-15 09:37:52 == Livepatch has a consistency model which is a hybrid of kGraft and kpatch: it uses kGraft's per-task consistency and syscall barrier switching combined with kpatch's stack trace switching. The current approach is stack checking of sleeping tasks. If no affected functions are on the stack of a given task, the task is patched. In most cases this will patch most or all of the tasks on the first try. Otherwise, it'll keep trying periodically. This patch implements the reliable stack tracing for consistency model a.k.a HAVE_RELIABLE_STACKTRACE. This will help in switching livepatching implementation to basic per- task consistency model. It is the foundation, which will help us enable security patches changing function or data semantics. This is the biggest remaining piece needed on ppc64le to make livepatch more generally useful. https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?id=df78d3f6148092d33a9a24c7a9cfac To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1771844/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1771826] Re: Creation of IMA file hashes fails when appraisal is enabled
** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: Confirmed => Triaged ** Changed in: linux (Ubuntu Xenial) Status: New => Triaged ** Changed in: linux (Ubuntu Xenial) 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/1771826 Title: Creation of IMA file hashes fails when appraisal is enabled Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: In Progress Bug description: On a system that has IMA appraisal enabled it is impossible to create security.ima extended attribute files that contain IMA hash. For instance, consider the following use case: 1) extract application files to a staging area as non root user 2) verify that installation is correct 3) create IMA extended attributes for the installed files 4) move the files to their destination 5) change the files ownership to root With kernel 4.4.x step 3 will fail. The issues is fixed in upstream kernels by the following commit [1]: commit f5acb3dcba1ffb7f0b8cbb9dba61500eea5d610b Author: Mimi Zohar Date: Wed Nov 2 09:14:16 2016 -0400 Revert "ima: limit file hash setting by user to fix and log modes" [1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?i d=f5acb3dcba1ffb7f0b8cbb9dba61500eea5d610b ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-124-generic 4.4.0-124.148 ProcVersionSignature: User Name 4.4.0-124.148-generic 4.4.117 Uname: Linux 4.4.0-124-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 17 14:07 seq crw-rw 1 root audio 116, 33 May 17 14:07 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.15 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: CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Thu May 17 14:08:59 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-124-generic root=UUID=aef88a4e-dbea-4cc7-be8b-03cf8501cc8f ro biosdevname=0 net.ifnames=0 console=tty1 console=ttyS0 crashkernel=384M-:128M RelatedPackageVersions: linux-restricted-modules-4.4.0-124-generic N/A linux-backports-modules-4.4.0-124-generic N/A linux-firmware 1.157.17 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: rel-1.11.0-0-g63451fca13-prebuilt.qemu-project.org dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-2.12 dmi.modalias: dmi:bvnSeaBIOS:bvrrel-1.11.0-0-g63451fca13-prebuilt.qemu-project.org:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.12:cvnQEMU:ct1:cvrpc-i440fx-2.12: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-2.12 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1771826/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1771799] Re: package linux-signed-image-4.13.0-41-generic 4.13.0-41.46 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
You may need to run the following from a terminal: sudo apt-get install -f sudo apt-get clean sudo apt-get update Then re-install the package or updates. If that does not resolve your issue, please mark the bug as "Confirmed" ** Package changed: linux-signed (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1771799 Title: package linux-signed-image-4.13.0-41-generic 4.13.0-41.46 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in linux package in Ubuntu: Incomplete Bug description: Installed when prompted by Ubuntu. This seems to have been a failure owing to /boot being jam-packed with other kernels. ProblemType: Package DistroRelease: Ubuntu 17.10 Package: linux-signed-image-4.13.0-41-generic 4.13.0-41.46 ProcVersionSignature: Ubuntu 4.13.0-38.43-generic 4.13.16 Uname: Linux 4.13.0-38-generic x86_64 NonfreeKernelModules: talpa_vfshook talpa_pedconnector talpa_pedevice talpa_vcdevice talpa_core talpa_linux talpa_syscallhook ApportVersion: 2.20.7-0ubuntu3.8 Architecture: amd64 Date: Thu May 17 11:48:04 2018 DuplicateSignature: package:linux-signed-image-4.13.0-41-generic:4.13.0-41.46 Setting up linux-signed-image-4.13.0-39-generic (4.13.0-39.44) ... cp: error writing '/boot/vmlinuz-4.13.0-39-generic.efi.signed': No space left on device dpkg: error processing package linux-signed-image-4.13.0-39-generic (--configure): subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2017-06-19 (332 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.5.1 SourcePackage: linux-signed Title: package linux-signed-image-4.13.0-41-generic 4.13.0-41.46 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to artful on 2018-02-19 (86 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1771799/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1771826] Re: Creation of IMA file hashes fails when appraisal is enabled
** Changed in: linux (Ubuntu) Status: Triaged => Invalid ** Changed in: linux (Ubuntu Xenial) Status: Triaged => In Progress ** Changed in: linux (Ubuntu Xenial) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1771826 Title: Creation of IMA file hashes fails when appraisal is enabled Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: In Progress Bug description: On a system that has IMA appraisal enabled it is impossible to create security.ima extended attribute files that contain IMA hash. For instance, consider the following use case: 1) extract application files to a staging area as non root user 2) verify that installation is correct 3) create IMA extended attributes for the installed files 4) move the files to their destination 5) change the files ownership to root With kernel 4.4.x step 3 will fail. The issues is fixed in upstream kernels by the following commit [1]: commit f5acb3dcba1ffb7f0b8cbb9dba61500eea5d610b Author: Mimi Zohar Date: Wed Nov 2 09:14:16 2016 -0400 Revert "ima: limit file hash setting by user to fix and log modes" [1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?i d=f5acb3dcba1ffb7f0b8cbb9dba61500eea5d610b ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-124-generic 4.4.0-124.148 ProcVersionSignature: User Name 4.4.0-124.148-generic 4.4.117 Uname: Linux 4.4.0-124-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 17 14:07 seq crw-rw 1 root audio 116, 33 May 17 14:07 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.15 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: CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Thu May 17 14:08:59 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-124-generic root=UUID=aef88a4e-dbea-4cc7-be8b-03cf8501cc8f ro biosdevname=0 net.ifnames=0 console=tty1 console=ttyS0 crashkernel=384M-:128M RelatedPackageVersions: linux-restricted-modules-4.4.0-124-generic N/A linux-backports-modules-4.4.0-124-generic N/A linux-firmware 1.157.17 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: rel-1.11.0-0-g63451fca13-prebuilt.qemu-project.org dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-2.12 dmi.modalias: dmi:bvnSeaBIOS:bvrrel-1.11.0-0-g63451fca13-prebuilt.qemu-project.org:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.12:cvnQEMU:ct1:cvrpc-i440fx-2.12: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-2.12 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1771826/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1771844] Re: powerpc/livepatch: Implement reliable stack tracing for the consistency model
I built a test kernel with commit df78d3f6148092d33a9a24c7a9cfac3d0220b484. The test kernel can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1771844 Can you test this kernel and see if it resolves this bug? Note about installing test kernels: • If the test kernel is prior to 4.15(Bionic) you need to install the linux-image and linux-image-extra .deb packages. • If the test kernel is 4.15(Bionic) or newer, you need to install the linux-image-unsigned, linux-modules and linux-modules-extra .deb packages. Thanks in advance! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1771844 Title: powerpc/livepatch: Implement reliable stack tracing for the consistency model Status in The Ubuntu-power-systems project: Triaged Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: In Progress Bug description: == Comment: #0 - Kamalesh Babulal - 2018-05-15 09:37:52 == Livepatch has a consistency model which is a hybrid of kGraft and kpatch: it uses kGraft's per-task consistency and syscall barrier switching combined with kpatch's stack trace switching. The current approach is stack checking of sleeping tasks. If no affected functions are on the stack of a given task, the task is patched. In most cases this will patch most or all of the tasks on the first try. Otherwise, it'll keep trying periodically. This patch implements the reliable stack tracing for consistency model a.k.a HAVE_RELIABLE_STACKTRACE. This will help in switching livepatching implementation to basic per- task consistency model. It is the foundation, which will help us enable security patches changing function or data semantics. This is the biggest remaining piece needed on ppc64le to make livepatch more generally useful. https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?id=df78d3f6148092d33a9a24c7a9cfac To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1771844/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1771823] Re: Please include ax88179_178a and r8152 modules in d-i udeb
** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Also affects: debian-installer (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: Confirmed => Triaged ** Tags added: bionic kernel-da-key -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1771823 Title: Please include ax88179_178a and r8152 modules in d-i udeb Status in debian-installer package in Ubuntu: New Status in linux package in Ubuntu: Triaged Bug description: r8152 is used in a thunderbolt-connected docking station and ax88179_178a by an external USB dongle. Despite having two nics connected i can't install Bionic. :-) This is probably a subset of the modules to be included when fixing LP: #1503218. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1771823/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1761796] Re: Rebooting bionic fails with hardware error on ProLiant DL360 Gen9
I built the next test kernel, up to the following commit:
abb62c46d4949d44979fa647740feff3f7538799
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1761796
Can you test that kernel and report back if it has the bug or not? I
will build the next test kernel based on your test results.
Thanks in advance
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1761796
Title:
Rebooting bionic fails with hardware error on ProLiant DL360 Gen9
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Bionic:
In Progress
Bug description:
From an ephemeral environment in an HPGen9, the machine fails to
reboot when the ephemeral environment is Bionic (it does not fail in
Xenial).
Full log from the moment the 'sudo reboot' was executed:
https://pastebin.ubuntu.com/p/hyD6VY7CbW/
The actual failure is:
[ OK ] Stopped Remount Root and Kernel File Systems.
[ OK ] Reached target Shutdown.
[ OK ] Reached target Final Step.
Starting Reboot...
[ OK ] Stopped Monitoring of LVM2 mirrors,…sing dmeventd or progress
polling.
Stopping LVM2 metadata daemon...
[ OK ] Stopped LVM2 metadata daemon.
[ 257.160527] {1}[Hardware Error]: Hardware error from APEI Generic Hardware
Error Source: 1
[ 257.160530] {1}[Hardware Error]: event severity: fatal
[ 257.160533] {1}[Hardware Error]: Error 0, type: fatal
[ 257.160534] {1}[Hardware Error]: section_type: PCIe error
[ 257.160536] {1}[Hardware Error]: port_type: 4, root port
[ 257.160541] {1}[Hardware Error]: version: 1.16
[ 257.160544] {1}[Hardware Error]: command: 0x6010, status: 0x0143
[ 257.160546] {1}[Hardware Error]: device_id: :00:01.0
[ 257.160547] {1}[Hardware Error]: slot: 0
[ 257.160548] {1}[Hardware Error]: secondary_bus: 0x03
[ 257.160550] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x6f02
[ 257.160552] {1}[Hardware Error]: class_code: 040600
[ 257.160554] {1}[Hardware Error]: bridge: secondary_status: 0x2000,
control: 0x0003
[ 257.160556] {1}[Hardware Error]: Error 1, type: fatal
[ 257.160557] {1}[Hardware Error]: section_type: PCIe error
[ 257.160559] {1}[Hardware Error]: port_type: 4, root port
[ 257.160560] {1}[Hardware Error]: version: 1.16
[ 257.160562] {1}[Hardware Error]: command: 0x6010, status: 0x0143
[ 257.160564] {1}[Hardware Error]: device_id: :00:01.0
[ 257.160565] {1}[Hardware Error]: slot: 0
[ 257.160566] {1}[Hardware Error]: secondary_bus: 0x03
[ 257.160567] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x6f02
[ 257.160568] {1}[Hardware Error]: class_code: 040600
[ 257.160569] {1}[Hardware Error]: bridge: secondary_status: 0x2000,
control: 0x0003
[ 257.160570] Kernel panic - not syncing: Fatal hardware error!
[ 257.200091] Kernel Offset: 0x2540 from 0x8100 (relocation
range: 0x8000-0xbfff)
[ 257.815850] ERST: [Firmware Warn]: Firmware does not respond in time.
---
AlsaDevices:
total 0
crw-rw 1 root audio 116, 33 Apr 6 17:40 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.9-0ubuntu2
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord':
'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/timer'] failed
with exit code 1:
CRDA: N/A
DistroRelease: Ubuntu 18.04
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
MachineType: HP ProLiant DL360 Gen9
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Package: linux (not installed)
PciMultimedia:
ProcEnviron:
TERM=screen-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=C.UTF-8
SHELL=/bin/bash
ProcFB: 0 EFI VGA
ProcKernelCmdLine:
BOOT_IMAGE=username/amd64/ga-18.04/bionic/daily/boot-kernel nomodeset ro
root=squash:http://10.245.136.6:5248/images/username/amd64/ga-18.04/bionic/daily/squashfs
ip=hostname:BOOTIF ip6=off overlayroot=tmpfs overlayroot_cfgdisk=disabled
cc:{datasource_list: [MAAS]}end_cc
cloud-config-url=http://10.245.136.6:5240/MAAS/metadata/latest/by-id/hqsxdc/?op=get_preseed
apparmor=0 log_host=10.245.136.6 log_port=514 --- console=ttyS1,115200n8
BOOTIF=01-94:18:82:7a:82:c8
ProcVersionSignature: User Name 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 N/A
RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
Tags: bionic uec-images
Uname: Linux 4.15.0-13-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video
_Mar
[Kernel-packages] [Bug 1771780] Re: [LTCTest][OPAL][OP920] cpupower idle-info is not listing stop4 and stop5 idle states when all CORES are guarded
** Changed in: linux (Ubuntu) Status: New => Triaged ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Status: New => Triaged ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => Critical ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) ** Changed in: linux (Ubuntu) Assignee: Canonical Kernel Team (canonical-kernel-team) => Joseph Salisbury (jsalisbury) ** Changed in: linux (Ubuntu Bionic) Status: Triaged => In Progress ** Changed in: linux (Ubuntu) Status: Triaged => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1771780 Title: [LTCTest][OPAL][OP920] cpupower idle-info is not listing stop4 and stop5 idle states when all CORES are guarded Status in The Ubuntu-power-systems project: Triaged Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: == Comment: #0 - PAVAMAN SUBRAMANIYAM - 2018-05-16 04:07:59 == ---Problem Description--- cpupower idle-info is not listing stop4 and stop5 idle states when all CORES are guarded ---uname output--- Linux ltc-wspoon11 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:14:44 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux Machine Type = P9 ---Debugger--- A debugger is not configured ---Steps to Reproduce--- Install a P9 Open Power Hardware with Ubuntu 18.04 OS. root@ltc-wspoon11:~# uname -a Linux ltc-wspoon11 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:14:44 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux root@ltc-wspoon11:~# cat /etc/os-release NAME="Ubuntu" VERSION="18.04 LTS (Bionic Beaver)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 18.04 LTS" VERSION_ID="18.04" HOME_URL="https://www.ubuntu.com/"; SUPPORT_URL="https://help.ubuntu.com/"; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"; VERSION_CODENAME=bionic UBUNTU_CODENAME=bionic Then guard an entire processor and also guard all the CORES in the processor 0 except for 1 single core. root@ltc-wspoon11:~# opal-gard list ID | Error| Type | Path --- 0001 | | Manual | /Sys0/Node0/Proc0/EQ1/EX0/Core0 0002 | | Manual | /Sys0/Node0/Proc0/EQ1/EX0/Core1 0003 | | Manual | /Sys0/Node0/Proc1 0004 | | Manual | /Sys0/Node0/Proc0/EQ2/EX0/Core1 0005 | | Manual | /Sys0/Node0/Proc0/EQ2/EX0/Core0 0006 | | Manual | /Sys0/Node0/Proc0/EQ2/EX1/Core0 0007 | | Manual | /Sys0/Node0/Proc0/EQ2/EX1/Core1 0008 | | Manual | /Sys0/Node0/Proc0/EQ3/EX0/Core0 0009 | | Manual | /Sys0/Node0/Proc0/EQ3/EX0/Core1 000a | | Manual | /Sys0/Node0/Proc0/EQ3/EX1/Core0 000b | | Manual | /Sys0/Node0/Proc0/EQ3/EX1/Core1 000c | | Manual | /Sys0/Node0/Proc0/EQ4/EX0/Core0 000d | | Manual | /Sys0/Node0/Proc0/EQ4/EX0/Core1 000e | | Manual | /Sys0/Node0/Proc0/EQ4/EX1/Core0 000f | | Manual | /Sys0/Node0/Proc0/EQ4/EX1/Core1 0010 | | Manual | /Sys0/Node0/Proc0/EQ5/EX0/Core0 0011 | | Manual | /Sys0/Node0/Proc0/EQ5/EX0/Core1 0012 | | Manual | /Sys0/Node0/Proc0/EQ5/EX1/Core0 0013 | | Manual | /Sys0/Node0/Proc0/EQ5/EX1/Core1 0014 | | Manual | /Sys0/Node0/Proc0/EQ1/EX1/Core0 0015 | | Manual | /Sys0/Node0/Proc0/EQ1/EX1/Core1 0016 | | Manual | /Sys0/Node0/Proc0/EQ0/EX1/Core1 0017 | | Manual | /Sys0/Node0/Proc0/EQ0/EX1/Core0 === Then execute the cpupower idle-info command to check the idle states being shown in the OS. root@ltc-wspoon11:~# cpupower idle-info CPUidle driver: powernv_idle CPUidle governor: menu analyzing CPU 0: Number of idle states: 7 Available idle states: snooze stop0_lite stop0 stop1_lite stop1 stop2_lite stop2 snooze: Flags/Description: snooze Latency: 0 Usage: 774653 Duration: 7698954 stop0_lite: Flags/Description: stop0_lite Latency: 1 Usage: 2751 Duration: 11363825 stop0: Flags/Description: stop0 Latency: 2 Usage: 2343 Duration: 915084 stop1_lite: Flags/Description: stop1_lite Latency: 5 Usage: 20 Duration: 1533 stop1: Flags/Description: stop1 Latency: 5 U
[Kernel-packages] [Bug 1771708] Re: Ubuntu 18.04 and 16.04 hang on shutdown.
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.17 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.17-rc6 ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Importance: Undecided => High ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => High ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete ** Changed in: linux (Ubuntu Xenial) Status: New => Incomplete ** Changed in: linux (Ubuntu Bionic) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1771708 Title: Ubuntu 18.04 and 16.04 hang on shutdown. Status in linux package in Ubuntu: Incomplete Status in linux source package in Xenial: Incomplete Status in linux source package in Bionic: Incomplete Bug description: That happens with all Ubuntu flavors: Xubuntu, Kubuntu... Reboot and suspend are works. (This laptop had Ubuntu 14.04 or 12.04 (don't remember) preinstalled, which was fine) Hardware details: pc description: Portable Computer product: Inspiron 3542 (0651) vendor: Dell Inc. version: Not Specified width: 64 bits capabilities: smbios-2.8 dmi-2.8 smp vsyscall32 configuration: boot=normal chassis=portable sku=0651 uuid=44454C4C-4700-1042-8034-B7C04F343132 *-core description: Motherboard product: 0FKWR5 vendor: Dell Inc. physical id: 0 version: A12 slot: To Be Filled By O.E.M. *-firmware description: BIOS vendor: Dell Inc. physical id: 0 version: A12 date: 05/13/2016 size: 64KiB capacity: 1984KiB capabilities: mca pci upgrade shadowing escd cdboot bootselect socketedrom edd int13floppy1200 int13floppy720 int13floppy2880 int5printscreen int9keyboard int14serial int17printer int10video acpi usb zipboot biosbootspecification uefi *-memory:0 UNCLAIMED physical id: 1 *-bank UNCLAIMED description: SODIMM DDR3 Synchronous 1600 MHz (0,6 ns) product: 99U5428-018.A00LF vendor: Kingston physical id: 0 slot: DIMM_A size: 8GiB width: 64 bits clock: 1600MHz (0.6ns) *-memory:1 description: System Memory physical id: 7 slot: System board or motherboard *-cache:0 description: L3 cache physical id: 6 slot: CPU Internal L3 size: 2MiB capacity: 2MiB capabilities: internal write-back unified configuration: level=3 *-cache:1 description: L2 cache physical id: 5 slot: CPU Internal L2 size: 512KiB capacity: 512KiB capabilities: internal write-back unified configuration: level=2 *-cache:2 description: L1 cache physical id: 4 slot: CPU Internal L1 size: 128KiB capacity: 128KiB capabilities: internal write-back configuration: level=1 *-cpu description: CPU product: Intel(R) Celeron(R) 2957U @ 1.40GHz vendor: Intel Corp. physical id: 24 bus info: cpu@0 version: Intel(R) Celeron(R) 2957U @ 1.40GHz slot: SOCKET 0 size: 1179MHz capacity: 3800MHz width: 64 bits clock: 100MHz capabilities: x86-64 fpu fpu_exception wp vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 sdbg cx16 xtpr pdcm pcid sse4_1 sse4_2 movbe popcnt xsave rdrand lahf_lm abm cpuid_fault epb invpcid_single pti tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust erms invpcid xsaveopt dtherm arat pln pts cpufreq configuration: cores=2 enabledcores=2 threads=2 *-memory:2 UNCLAIMED physical id: 2 *-memory:3
[Kernel-packages] [Bug 1772287] Re: package linux-image-4.4.0-124-generic 4.4.0-124.148 failed to install/upgrade: subprocess new pre-installation script returned error exit status 128
You may need to run the following from a terminal: sudo apt-get install -f sudo apt-get clean sudo apt-get update Then re-install the package or updates. If that does not resolve your issue, please mark the bug as "Confirmed" ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete ** Changed in: linux (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1772287 Title: package linux-image-4.4.0-124-generic 4.4.0-124.148 failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 Status in linux package in Ubuntu: Incomplete Bug description: Under Vbox ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-124-generic 4.4.0-124.148 ProcVersionSignature: Ubuntu 4.4.0-124.148-generic 4.4.117 Uname: Linux 4.4.0-124-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.17 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bill 1870 F pulseaudio Date: Fri May 11 22:56:50 2018 ErrorMessage: subprocess new pre-installation script returned error exit status 128 HibernationDevice: RESUME=UUID=44bf76c6-29c5-4361-baa1-ccfd72a45695 InstallationDate: Installed on 2016-07-05 (683 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IwConfig: enp0s3no wireless extensions. lono wireless extensions. docker0 no wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox ProcFB: 0 vboxdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-124-generic root=UUID=e84f9ca3-7cca-43d5-a7f1-1412f9276f77 ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.17 RfKill: SourcePackage: linux Title: package linux-image-4.4.0-124-generic 4.4.0-124.148 failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1772287/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1772154] Re: Unstable WiFi adapter Gigabyte GC-WB867D-I
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.17 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.17-rc6 ** Package changed: linux-signed (Ubuntu) => linux (Ubuntu) ** 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/1772154 Title: Unstable WiFi adapter Gigabyte GC-WB867D-I Status in linux package in Ubuntu: New Bug description: The WiFi adapter Gigabyte GC-WB867D-I is quite unstable on Ubuntu 18.04. I do not have data relative to previous versions of Ubuntu since this PCIe card is part of a new build that has had 18.04 as the first installed version. The reason why I can point the finger at the Linux kernel is that the card seems to work reliably well on Windows 10 (no packet loss when pinging the local router). On Ubuntu 18.04, the card's behaviour seems very correlated to the signal strength and exhibits a threshold phenomenon. With the antenna placed in an obstacle-free area, some ping packets are occasionally lost. But when some objects are placed near the antenna (e.g. a phone), the packet loss can get up to 90%. Under the very same conditions, the packet loss on Windows is exactly 0 (and the RTT never gets above 500ms). I have disabled the WiFi power saving (changed from 2 to 3) but that didn't fix the problem. It seems that restarting the NetworkManager service helps for a bit, but after a while the problem resurfaces. The card in question has onboard USB Bluetooth and is pretty much an M.2 to PCIe x1 adapter for an Intel Wifi adapter. The relevant output of lspci is 03:00.0 Network controller: Intel Corporation Wireless 8265 / 8275 (rev 78) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-20-generic 4.15.0-20.21 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat May 19 10:32:00 2018 InstallationDate: Installed on 2018-04-29 (19 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1772154/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1771780] Re: [LTCTest][OPAL][OP920] cpupower idle-info is not listing stop4 and stop5 idle states when all CORES are guarded
I built a Bionic test kernel with the patch posted in the description. The test kernel can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1771780 Can you test this kernel and see if it resolves this bug? Note about installing test kernels: • If the test kernel is prior to 4.15(Bionic) you need to install the linux-image and linux-image-extra .deb packages. • If the test kernel is 4.15(Bionic) or newer, you need to install the linux-image-unsigned, linux-modules and linux-modules-extra .deb packages. Thanks in advance! ** Also affects: linux (Ubuntu Cosmic) Importance: Critical Assignee: Joseph Salisbury (jsalisbury) Status: In Progress ** Also affects: linux (Ubuntu Artful) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Artful) Importance: Undecided => Critical ** Changed in: linux (Ubuntu Xenial) Importance: Undecided => Critical ** No longer affects: linux (Ubuntu Artful) ** No longer affects: linux (Ubuntu 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/1771780 Title: [LTCTest][OPAL][OP920] cpupower idle-info is not listing stop4 and stop5 idle states when all CORES are guarded Status in The Ubuntu-power-systems project: Triaged Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: In Progress Bug description: == Comment: #0 - PAVAMAN SUBRAMANIYAM - 2018-05-16 04:07:59 == ---Problem Description--- cpupower idle-info is not listing stop4 and stop5 idle states when all CORES are guarded ---uname output--- Linux ltc-wspoon11 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:14:44 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux Machine Type = P9 ---Debugger--- A debugger is not configured ---Steps to Reproduce--- Install a P9 Open Power Hardware with Ubuntu 18.04 OS. root@ltc-wspoon11:~# uname -a Linux ltc-wspoon11 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:14:44 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux root@ltc-wspoon11:~# cat /etc/os-release NAME="Ubuntu" VERSION="18.04 LTS (Bionic Beaver)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 18.04 LTS" VERSION_ID="18.04" HOME_URL="https://www.ubuntu.com/"; SUPPORT_URL="https://help.ubuntu.com/"; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"; VERSION_CODENAME=bionic UBUNTU_CODENAME=bionic Then guard an entire processor and also guard all the CORES in the processor 0 except for 1 single core. root@ltc-wspoon11:~# opal-gard list ID | Error| Type | Path --- 0001 | | Manual | /Sys0/Node0/Proc0/EQ1/EX0/Core0 0002 | | Manual | /Sys0/Node0/Proc0/EQ1/EX0/Core1 0003 | | Manual | /Sys0/Node0/Proc1 0004 | | Manual | /Sys0/Node0/Proc0/EQ2/EX0/Core1 0005 | | Manual | /Sys0/Node0/Proc0/EQ2/EX0/Core0 0006 | | Manual | /Sys0/Node0/Proc0/EQ2/EX1/Core0 0007 | | Manual | /Sys0/Node0/Proc0/EQ2/EX1/Core1 0008 | | Manual | /Sys0/Node0/Proc0/EQ3/EX0/Core0 0009 | | Manual | /Sys0/Node0/Proc0/EQ3/EX0/Core1 000a | | Manual | /Sys0/Node0/Proc0/EQ3/EX1/Core0 000b | | Manual | /Sys0/Node0/Proc0/EQ3/EX1/Core1 000c | | Manual | /Sys0/Node0/Proc0/EQ4/EX0/Core0 000d | | Manual | /Sys0/Node0/Proc0/EQ4/EX0/Core1 000e | | Manual | /Sys0/Node0/Proc0/EQ4/EX1/Core0 000f | | Manual | /Sys0/Node0/Proc0/EQ4/EX1/Core1 0010 | | Manual | /Sys0/Node0/Proc0/EQ5/EX0/Core0 0011 | | Manual | /Sys0/Node0/Proc0/EQ5/EX0/Core1 0012 | | Manual | /Sys0/Node0/Proc0/EQ5/EX1/Core0 0013 | | Manual | /Sys0/Node0/Proc0/EQ5/EX1/Core1 0014 | | Manual | /Sys0/Node0/Proc0/EQ1/EX1/Core0 0015 | | Manual | /Sys0/Node0/Proc0/EQ1/EX1/Core1 0016 | | Manual | /Sys0/Node0/Proc0/EQ0/EX1/Core1 0017 | | Manual | /Sys0/Node0/Proc0/EQ0/EX1/Core0 === Then execute the cpupower idle-info command to check the idle states being shown in the OS. root@ltc-wspoon11:~# cpupower idle-info CPUidle driver: powernv_idle CPUidle governor: menu analyzing CPU 0: Number of idle states: 7 Available idl
[Kernel-packages] [Bug 1771826] Re: Creation of IMA file hashes fails when appraisal is enabled
I built a test kernel with commit f5acb3dcba1ffb7f0b8cbb9dba61500eea5d610b. The test kernel can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1771826 Can you test this kernel and see if it resolves this bug? Note about installing test kernels: • If the test kernel is prior to 4.15(Bionic) you need to install the linux-image and linux-image-extra .deb packages. • If the test kernel is 4.15(Bionic) or newer, you need to install the linux-image-unsigned, linux-modules and linux-modules-extra .deb packages. Thanks in advance! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1771826 Title: Creation of IMA file hashes fails when appraisal is enabled Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: In Progress Bug description: On a system that has IMA appraisal enabled it is impossible to create security.ima extended attribute files that contain IMA hash. For instance, consider the following use case: 1) extract application files to a staging area as non root user 2) verify that installation is correct 3) create IMA extended attributes for the installed files 4) move the files to their destination 5) change the files ownership to root With kernel 4.4.x step 3 will fail. The issues is fixed in upstream kernels by the following commit [1]: commit f5acb3dcba1ffb7f0b8cbb9dba61500eea5d610b Author: Mimi Zohar Date: Wed Nov 2 09:14:16 2016 -0400 Revert "ima: limit file hash setting by user to fix and log modes" [1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?i d=f5acb3dcba1ffb7f0b8cbb9dba61500eea5d610b ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-124-generic 4.4.0-124.148 ProcVersionSignature: User Name 4.4.0-124.148-generic 4.4.117 Uname: Linux 4.4.0-124-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 17 14:07 seq crw-rw 1 root audio 116, 33 May 17 14:07 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.15 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: CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Thu May 17 14:08:59 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-124-generic root=UUID=aef88a4e-dbea-4cc7-be8b-03cf8501cc8f ro biosdevname=0 net.ifnames=0 console=tty1 console=ttyS0 crashkernel=384M-:128M RelatedPackageVersions: linux-restricted-modules-4.4.0-124-generic N/A linux-backports-modules-4.4.0-124-generic N/A linux-firmware 1.157.17 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: rel-1.11.0-0-g63451fca13-prebuilt.qemu-project.org dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-2.12 dmi.modalias: dmi:bvnSeaBIOS:bvrrel-1.11.0-0-g63451fca13-prebuilt.qemu-project.org:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.12:cvnQEMU:ct1:cvrpc-i440fx-2.12: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-2.12 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1771826/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1772081] Re: HP x360 - Ryzen 2500U Locks up
** Changed in: linux (Ubuntu) Importance: Undecided => High ** Tags added: kernel-da-key -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1772081 Title: HP x360 - Ryzen 2500U Locks up Status in linux package in Ubuntu: Incomplete Bug description: Hi, I have an HP x360 Ryzen 2500u. It locks up a couple of times a day. Before I disabled C6, using this python script https://github.com/r4m0n/ZenStates-Linux it would lock up minutes after boot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1772081/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1772031] Re: kernel backtrace when receiving large UDP packages
** Also affects: linux (Ubuntu Artful)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Artful)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Artful)
Status: New => In Progress
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
** Changed in: linux (Ubuntu Artful)
Assignee: (unassigned) => Joseph Salisbury (jsalisbury)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1772031
Title:
kernel backtrace when receiving large UDP packages
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Artful:
In Progress
Bug description:
kernel 4.13.0-41-generic is missing commit a90bcb86ae70:
Author: Petar Penkov
Date: Tue Aug 29 11:20:32 2017 -0700
iov_iter: fix page_copy_sane for compound pages
Issue is that if the data crosses a page boundary inside a compound
page, this check will incorrectly trigger a WARN_ON.
To fix this, compute the order using the head of the compound page and
adjust the offset to be relative to that head.
Fixes: 72e809ed81ed ("iov_iter: sanity checks for copy to/from page
primitives")
Signed-off-by: Petar Penkov
CC: Al Viro
CC: Eric Dumazet
Signed-off-by: Al Viro
Commit 72e809ed81ed is in kernel 4.13.0-41-generic.
As a result, when receiving large UDP packages with a small MTU we get
backtraces like:
[ 361.260969] [ cut here ]
[ 361.260974] WARNING: CPU: 4 PID: 2541 at
/build/linux-hwe-v6kHHF/linux-hwe-4.13.0/lib/iov_iter.c:693
copy_page_to_iter+0x194/0x2d0
[ 361.260975] Modules linked in: cmdlinepart sfc(OE) hwmon_vid crc32_generic
mii rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace fscache 8021q garp mrp
stp llc intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm
i]
[ 361.261002] CPU: 4 PID: 2541 Comm: udp_recv Tainted: G OE
4.13.0-39-generic #44~16.04.1-Ubuntu
[ 361.261003] Hardware name: Dell Inc. PowerEdge R220/05Y15N, BIOS 1.4.0
10/23/2014
[ 361.261004] task: 91630b2bae80 task.stack: bb19c2bfc000
[ 361.261005] RIP: 0010:copy_page_to_iter+0x194/0x2d0
[ 361.261006] RSP: 0018:bb19c2bffc60 EFLAGS: 00010202
[ 361.261007] RAX: 1000 RBX: 00df RCX:
0017c000
[ 361.261008] RDX: 00df RSI: 0f8e RDI:
f666895279c0
[ 361.261009] RBP: bb19c2bffca0 R08: 106d R09:
1024
[ 361.261009] R10: R11: 91630ccc9b00 R12:
91630d27a300
[ 361.261010] R13: bb19c2bffde0 R14: 00df R15:
0175
[ 361.261011] FS: 7fb8e7649700() GS:91631fd0()
knlGS:
[ 361.261012] CS: 0010 DS: ES: CR0: 80050033
[ 361.261013] CR2: 14588da85624 CR3: 00024bad2002 CR4:
001606e0
[ 361.261013] Call Trace:
[ 361.261017] ? proto_init_net+0x40/0x40
[ 361.261019] skb_copy_datagram_iter+0x171/0x270
[ 361.261022] udp_recvmsg+0x108/0x490
[ 361.261024] inet_recvmsg+0x51/0xc0
[ 361.261026] sock_recvmsg+0x43/0x50
[ 361.261028] sock_read_iter+0x90/0xe0
[ 361.261030] new_sync_read+0xe2/0x130
[ 361.261032] __vfs_read+0x29/0x40
[ 361.261033] vfs_read+0x93/0x130
[ 361.261034] SyS_read+0x55/0xc0
[ 361.261037] entry_SYSCALL_64_fastpath+0x24/0xab
[ 361.261038] RIP: 0033:0x7fb8e7160260
[ 361.261039] RSP: 002b:7ffed9dd9e38 EFLAGS: 0246 ORIG_RAX:
[ 361.261040] RAX: ffda RBX: RCX:
7fb8e7160260
[ 361.261041] RDX: ffe3 RSI: 5622ad02f0a0 RDI:
0003
[ 361.261041] RBP: 7ffed9dd9e70 R08: R09:
0011
[ 361.261042] R10: R11: 0246 R12:
5622ace2e800
[ 361.261043] R13: 7ffed9dd9f50 R14: R15:
[ 361.261044] Code: de 4c 89 e7 e8 be fa ff ff 41 83 af a0 12 00 00 01 48 83
c4 18 5b 41 5c 41 5d 41 5e 41 5f 5d c3 8b 4f 6c 48 d3 e0 e9 9d fe ff ff <0f> ff
48 83 c4 18 31 c0 5b 41 5c 41 5d 41 5e 41 5f 5d c3 49 83
[ 361.261064] ---[ end trace c0b23bf37be9874d ]---
This is a request to pull in commit a90bcb86ae70.
# lsb_release -rd
Description: Ubuntu 17.10
Release: 17.10
# uname -a
Linux c6320f 4.13.0-41-generic #46-Ubuntu SMP Wed May 2 13:38:30 UTC 2018
x86_64 x86_64 x86_64 GNU/Linux
# cat /proc/version_signature
Ubuntu 4.13.0-41.46-generic 4.13.16
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1772031/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kern
[Kernel-packages] [Bug 1771927] Re: System randomly freeze
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.17 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.17-rc6 ** Package changed: linux-signed (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1771927 Title: System randomly freeze Status in linux package in Ubuntu: Incomplete Bug description: Mostly when i play games. but freeze when using chrome also ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-20-generic 4.15.0-20.21 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri May 18 05:51:51 2018 InstallationDate: Installed on 2018-05-03 (14 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1771927/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1772038] Re: ubuntu/xubuntu 18.04 kernel crash during install.
Also, it would be good to know if this bug also happens with the current daily iso: Desktop: http://cdimage.ubuntu.com/daily-live/current/ Server: http://cdimage.ubuntu.com/ubuntu-server/daily/current/ ** Tags added: kernel-key ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => High ** Changed in: linux (Ubuntu Bionic) Status: New => Incomplete ** 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/1772038 Title: ubuntu/xubuntu 18.04 kernel crash during install. Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Bug description: I've been trying to install ubuntu 18.04, but the system crashes with a kernel panic and thus won't run. So how do I report this bug? The system passes all memory tests and runs 17.10 with no problems, but will not run 18.04 There is very little data gathering that I can do, as the system will not boot, not even into text mode. PS. This back door way of creating a bug report is very poor when dealing with systems that don't run. The steps required to reproduce this bug are: 1) download Ubuntu and/or Xubuntu 2) burn the installation image to a dvd 3) insert dvd into target computer 4) power on target computer 5) wait a couple of seconds 6) Stare at frozen screen saying Kernel panic 7) Go back to step 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1772038/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1772038] Re: ubuntu/xubuntu 18.04 kernel crash during install.
Can you install and see if installing a 18.04(Bionic) kernel will boot on 17.10? The kernel can be downloaded from: https://launchpad.net/~canonical-kernel- team/+archive/ubuntu/ppa/+build/14810997 You need to install the linux-modules, linux-modules-extra and linux-image-unsigned .deb packages. ** Changed in: linux (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1772038 Title: ubuntu/xubuntu 18.04 kernel crash during install. Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Bug description: I've been trying to install ubuntu 18.04, but the system crashes with a kernel panic and thus won't run. So how do I report this bug? The system passes all memory tests and runs 17.10 with no problems, but will not run 18.04 There is very little data gathering that I can do, as the system will not boot, not even into text mode. PS. This back door way of creating a bug report is very poor when dealing with systems that don't run. The steps required to reproduce this bug are: 1) download Ubuntu and/or Xubuntu 2) burn the installation image to a dvd 3) insert dvd into target computer 4) power on target computer 5) wait a couple of seconds 6) Stare at frozen screen saying Kernel panic 7) Go back to step 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1772038/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1772031] Re: kernel backtrace when receiving large UDP packages
I built a test kernel with commit a90bcb86ae70. The test kernel can be
downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1772031
Can you test this kernel and see if it resolves this bug?
Note about installing test kernels:
• If the test kernel is prior to 4.15(Bionic) you need to install the
linux-image and linux-image-extra .deb packages.
• If the test kernel is 4.15(Bionic) or newer, you need to install the
linux-modules, linux-modules-extra and linux-image-unsigned .deb packages.
Thanks in advance!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1772031
Title:
kernel backtrace when receiving large UDP packages
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Artful:
In Progress
Bug description:
kernel 4.13.0-41-generic is missing commit a90bcb86ae70:
Author: Petar Penkov
Date: Tue Aug 29 11:20:32 2017 -0700
iov_iter: fix page_copy_sane for compound pages
Issue is that if the data crosses a page boundary inside a compound
page, this check will incorrectly trigger a WARN_ON.
To fix this, compute the order using the head of the compound page and
adjust the offset to be relative to that head.
Fixes: 72e809ed81ed ("iov_iter: sanity checks for copy to/from page
primitives")
Signed-off-by: Petar Penkov
CC: Al Viro
CC: Eric Dumazet
Signed-off-by: Al Viro
Commit 72e809ed81ed is in kernel 4.13.0-41-generic.
As a result, when receiving large UDP packages with a small MTU we get
backtraces like:
[ 361.260969] [ cut here ]
[ 361.260974] WARNING: CPU: 4 PID: 2541 at
/build/linux-hwe-v6kHHF/linux-hwe-4.13.0/lib/iov_iter.c:693
copy_page_to_iter+0x194/0x2d0
[ 361.260975] Modules linked in: cmdlinepart sfc(OE) hwmon_vid crc32_generic
mii rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace fscache 8021q garp mrp
stp llc intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm
i]
[ 361.261002] CPU: 4 PID: 2541 Comm: udp_recv Tainted: G OE
4.13.0-39-generic #44~16.04.1-Ubuntu
[ 361.261003] Hardware name: Dell Inc. PowerEdge R220/05Y15N, BIOS 1.4.0
10/23/2014
[ 361.261004] task: 91630b2bae80 task.stack: bb19c2bfc000
[ 361.261005] RIP: 0010:copy_page_to_iter+0x194/0x2d0
[ 361.261006] RSP: 0018:bb19c2bffc60 EFLAGS: 00010202
[ 361.261007] RAX: 1000 RBX: 00df RCX:
0017c000
[ 361.261008] RDX: 00df RSI: 0f8e RDI:
f666895279c0
[ 361.261009] RBP: bb19c2bffca0 R08: 106d R09:
1024
[ 361.261009] R10: R11: 91630ccc9b00 R12:
91630d27a300
[ 361.261010] R13: bb19c2bffde0 R14: 00df R15:
0175
[ 361.261011] FS: 7fb8e7649700() GS:91631fd0()
knlGS:
[ 361.261012] CS: 0010 DS: ES: CR0: 80050033
[ 361.261013] CR2: 14588da85624 CR3: 00024bad2002 CR4:
001606e0
[ 361.261013] Call Trace:
[ 361.261017] ? proto_init_net+0x40/0x40
[ 361.261019] skb_copy_datagram_iter+0x171/0x270
[ 361.261022] udp_recvmsg+0x108/0x490
[ 361.261024] inet_recvmsg+0x51/0xc0
[ 361.261026] sock_recvmsg+0x43/0x50
[ 361.261028] sock_read_iter+0x90/0xe0
[ 361.261030] new_sync_read+0xe2/0x130
[ 361.261032] __vfs_read+0x29/0x40
[ 361.261033] vfs_read+0x93/0x130
[ 361.261034] SyS_read+0x55/0xc0
[ 361.261037] entry_SYSCALL_64_fastpath+0x24/0xab
[ 361.261038] RIP: 0033:0x7fb8e7160260
[ 361.261039] RSP: 002b:7ffed9dd9e38 EFLAGS: 0246 ORIG_RAX:
[ 361.261040] RAX: ffda RBX: RCX:
7fb8e7160260
[ 361.261041] RDX: ffe3 RSI: 5622ad02f0a0 RDI:
0003
[ 361.261041] RBP: 7ffed9dd9e70 R08: R09:
0011
[ 361.261042] R10: R11: 0246 R12:
5622ace2e800
[ 361.261043] R13: 7ffed9dd9f50 R14: R15:
[ 361.261044] Code: de 4c 89 e7 e8 be fa ff ff 41 83 af a0 12 00 00 01 48 83
c4 18 5b 41 5c 41 5d 41 5e 41 5f 5d c3 8b 4f 6c 48 d3 e0 e9 9d fe ff ff <0f> ff
48 83 c4 18 31 c0 5b 41 5c 41 5d 41 5e 41 5f 5d c3 49 83
[ 361.261064] ---[ end trace c0b23bf37be9874d ]---
This is a request to pull in commit a90bcb86ae70.
# lsb_release -rd
Description: Ubuntu 17.10
Release: 17.10
# uname -a
Linux c6320f 4.13.0-41-generic #46-Ubuntu SMP Wed May 2 13:38:30 UTC 2018
x86_64 x86_64 x86_64 GNU/Linux
# cat /proc/version_signature
Ubuntu 4.13.0-41.46-generic 4.13.16
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1772031/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packag
[Kernel-packages] [Bug 1772467] Re: Driver iwlwifi for Intel Wireless-AC 9560 is slow and unreliable in kernel 4.15.0-20-generic
Can you see if this bug exists in the latest upstream 4.15 kernel? It can be downloaded from: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15.18/ ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Triaged ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Bionic) Status: New => Triaged ** Tags added: kernel-da-key -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1772467 Title: Driver iwlwifi for Intel Wireless-AC 9560 is slow and unreliable in kernel 4.15.0-20-generic Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Bug description: This is a hardware specific issue with Ubuntu 18.04 and kernel 4.15.0-20-generic. The driver for the Intel AC 9560 wireless chip causes the problem. Driver location: https://www.intel.com/content/www/us/en/support/articles/05511 /network-and-i-o/wireless-networking.html The wifi connection is very slow (1MB instead of 100MB possible download speed, upload speed is normal) and is also very unreliable. When installing the 4.16 kernel from mainline kernel http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.16/ the described problem is solved. Sytem data: Description: Ubuntu 18.04 LTS Release: 18.04 Package: 4.15.0-20-generic driver=iwlwifi driverversion=4.15.0-20-generic firmware=34.0.0 --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: david 1729 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-05-19 (2 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Acer Swift SF114-32 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_AT.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=39ea17c1-4c91-45ac-81a7-401583763b21 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/02/2018 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.03 dmi.board.name: Sapporo_GL dmi.board.vendor: GLK dmi.board.version: V1.03 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.03 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.03:bd05/02/2018:svnAcer:pnSwiftSF114-32:pvrV1.03:rvnGLK:rnSapporo_GL:rvrV1.03:cvnAcer:ct10:cvrV1.03: dmi.product.family: Swift 1 dmi.product.name: Swift SF114-32 dmi.product.version: V1.03 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1772467/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1771823] Re: Please include ax88179_178a and r8152 modules in d-i udeb
** Also affects: debian-installer (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Cosmic) Importance: Medium Status: Triaged ** Also affects: debian-installer (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** No longer affects: debian-installer (Ubuntu Bionic) ** No longer affects: debian-installer (Ubuntu Cosmic) ** Changed in: linux (Ubuntu Bionic) Status: New => Triaged ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) ** Changed in: linux (Ubuntu Cosmic) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1771823 Title: Please include ax88179_178a and r8152 modules in d-i udeb Status in debian-installer package in Ubuntu: New Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Status in linux source package in Cosmic: Triaged Bug description: r8152 is used in a thunderbolt-connected docking station and ax88179_178a by an external USB dongle. Despite having two nics connected i can't install Bionic. :-) This is probably a subset of the modules to be included when fixing LP: #1503218. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1771823/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1771823] Re: Please include ax88179_178a and r8152 modules in d-i udeb
I built a test kernel with those two modules built into the kernel. The test kernel can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1771823 Can you test this kernel and see if it resolves this bug? Note about installing test kernels: • If the test kernel is prior to 4.15(Bionic) you need to install the linux-image and linux-image-extra .deb packages. • If the test kernel is 4.15(Bionic) or newer, you need to install the linux-modules, linux-modules-extra and linux-image-unsigned .deb packages. Thanks in advance! ** Changed in: linux (Ubuntu Bionic) Status: Triaged => In Progress ** Changed in: linux (Ubuntu Cosmic) Status: Triaged => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1771823 Title: Please include ax88179_178a and r8152 modules in d-i udeb Status in debian-installer package in Ubuntu: New Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: In Progress Bug description: r8152 is used in a thunderbolt-connected docking station and ax88179_178a by an external USB dongle. Despite having two nics connected i can't install Bionic. :-) This is probably a subset of the modules to be included when fixing LP: #1503218. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1771823/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1771075] Re: General Protection fault in inotify (fixed upstream)
Any fix that goes into Artful is also applied to the 4.13 HWE kernel in Xenial. The fix will get into the HWE kernel that way. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1771075 Title: General Protection fault in inotify (fixed upstream) Status in linux package in Ubuntu: In Progress Status in linux source package in Artful: In Progress Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: In Progress Bug description: We've run into some issues where upgrading the kernel from a 4.10 series to a 4.13 series on Ubuntu 16.04 hosts that make heavy use of inotify causes panics and lockups in the kernel in inotify-related code. Our particular use case seemed to hit these at a rate of one every 30 minutes or so when serving up production traffic. Unfortunately, I have been unable to replicate the issue so far with a simulated load-testing environment. When the issue occurs, we get dmesg entries like "BUG: soft lockup - CPU#0 stuck for 22s!" or "General protection fault: [#1] SMP PTI". In the soft lockup case, the host is still up but all I/O operations stall indefinitely (e.g. typing "sync" into the console will hang forever). In the protection fault case, the system reboots. I've attached dmesg output from the two cases to this bugreport. We have noticed the issue with the following kernels: - linux-image-4.13.0-1013-gcp - linux-image-4.13.0-1015-gcp - linux-image-4.13.0-36-generic We did _not_ have the issue with - linux-image-4.10.0-32-generic I've submitted this bug report from a system which should be configured identically to our production hosts that were having issue (the affected hosts were immediately rolled back to 4.10). This bug appears to have been fixed upstream as of 4.17-rc3 in this commit: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=d90a10e2444ba5a351fa695917258ff4c5709fa5 I would guess that perhaps this patch should be backported into both the 4.13 HWE and GCP Ubuntu kernel series? Thanks, KJ ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.13.0-1013-gcp 4.13.0-1013.17 ProcVersionSignature: Ubuntu 4.13.0-1013.17-gcp 4.13.16 Uname: Linux 4.13.0-1013-gcp x86_64 ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 Date: Mon May 14 07:58:29 2018 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-gcp UpgradeStatus: No upgrade log present (probably fresh install) --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 10 07:57 seq crw-rw 1 root audio 116, 33 May 10 07:57 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A DistroRelease: Ubuntu 16.04 IwConfig: Error: [Errno 2] No such file or directory Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Google Google Compute Engine Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-32-generic root=UUID=73ea38ed-7fcd-4871-8afa-17d36f4e4bfc ro scsi_mod.use_blk_mq=Y console=ttyS0 ProcVersionSignature: Ubuntu 4.10.0-32.36~16.04.1-generic 4.10.17 RelatedPackageVersions: linux-restricted-modules-4.10.0-32-generic N/A linux-backports-modules-4.10.0-32-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory Tags: xenial uec-images xenial uec-images Uname: Linux 4.10.0-32-generic x86_64 UnreportableReason: The report belongs to a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: WifiSyslog: _MarkForUpload: False dmi.bios.date: 01/01/2011 dmi.bios.vendor: Google dmi.bios.version: Google dmi.board.asset.tag: 98BEC19B-1DEB-1A9F-1146-C6E4D8577ADB dmi.board.name: Google Compute Engine dmi.board.vendor: Google dmi.chassis.type: 1 dmi.chassis.vendor: Google dmi.modalias: dmi:bvnGoogle:bvrGoogle:bd01/01/2011:svnGoogle:pnGoogleComputeEngine:pvr:rvnGoogle:rnGoogleComputeEngine:rvr:cvnGoogle:ct1:cvr: dmi.product.name: Google Compute Engine dmi.sys.vendor: Google To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1771075/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More hel
[Kernel-packages] [Bug 1772671] Re: Kernel produces empty lines in /proc/PID/status
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.17 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.17-rc6 ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Status: New => Incomplete ** Changed in: linux (Ubuntu Xenial) 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/1772671 Title: Kernel produces empty lines in /proc/PID/status Status in linux package in Ubuntu: Incomplete Status in linux source package in Xenial: Incomplete Bug description: Hello, after running updates today to linux- image-4.4.0-127-generic_4.4.0-127.153 and rebooting i noticed that iotop is not working any more. Reason are empty lines in /proc/PID/status, which confuse iotop (and me) In new view there is an empy line between Seccomp and Speculation_Store_Bypass: Seccomp:0 Speculation_Store_Bypass: vulnerable Speculation_Store_Bypass seems to be new in /proc/PID/status, may be a relation to spectre/meltdown patches. iotop is first application which is failing here, but iam afraid of more. Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1772671/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1772641] Re: package linux-image-4.15.0-22-generic 4.15.0-22.24 failed to install/upgrade: installed linux-image-4.15.0-22-generic package post-installation script subprocess re
You may need to run the following from a terminal: sudo apt-get install -f sudo apt-get clean sudo apt-get update Then re-install the package or updates. If that does not resolve your issue, please mark the bug as "Confirmed" ** Changed in: linux-signed (Ubuntu) Importance: Undecided => Medium ** Changed in: linux-signed (Ubuntu) Status: New => Incomplete ** Package changed: linux-signed (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1772641 Title: package linux-image-4.15.0-22-generic 4.15.0-22.24 failed to install/upgrade: installed linux-image-4.15.0-22-generic package post- installation script subprocess returned error exit status 1 Status in linux package in Ubuntu: Incomplete Bug description: Installed PyCharm from jetbrains > get this error when starting the application. Thx for your help! Pom ProblemType: Package DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-22-generic 4.15.0-22.24 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Tue May 22 08:29:45 2018 ErrorMessage: installed linux-image-4.15.0-22-generic package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2018-05-08 (14 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: linux-signed Title: package linux-image-4.15.0-22-generic 4.15.0-22.24 failed to install/upgrade: installed linux-image-4.15.0-22-generic package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1772641/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1772593] Re: cpum_sf: ensure sample freq is non-zero
** Changed in: linux (Ubuntu) Status: New => Triaged ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Artful) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Cosmic) Importance: High Assignee: Skipper Bug Screeners (skipper-screen-team) Status: Triaged ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Status: New => Triaged ** Changed in: linux (Ubuntu Artful) Status: New => Triaged ** Changed in: linux (Ubuntu Xenial) Status: New => Triaged ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => High ** Changed in: linux (Ubuntu Artful) Importance: Undecided => High ** Changed in: linux (Ubuntu Xenial) Importance: Undecided => High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1772593 Title: cpum_sf: ensure sample freq is non-zero Status in Ubuntu on IBM z Systems: New Status in linux package in Ubuntu: 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 source package in Cosmic: In Progress Bug description: Description: cpum_sf: ensure sample freq is non-zero Symptom: A kernel crash might occur. Problem: An FP divide exception during the sample rate initialization for the hardware sampling facility. Solution: Ensure that the sample frequency of the perf event attribute is non-zero. Reproduction: Run trinity against the perf_event_open() syscall. Upstream-ID: 4bbaf2584b86b0772413edeac22ff448f36351b1 Component: kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1772593/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1772593] Re: cpum_sf: ensure sample freq is non-zero
** Changed in: linux (Ubuntu Cosmic) Assignee: Skipper Bug Screeners (skipper-screen-team) => Joseph Salisbury (jsalisbury) ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) ** Changed in: linux (Ubuntu Artful) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) ** Changed in: linux (Ubuntu Xenial) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) ** Changed in: linux (Ubuntu Cosmic) Status: Triaged => In Progress ** Changed in: linux (Ubuntu Bionic) Status: Triaged => In Progress ** Changed in: linux (Ubuntu Artful) Status: Triaged => In Progress ** Changed in: linux (Ubuntu Xenial) Status: Triaged => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1772593 Title: cpum_sf: ensure sample freq is non-zero Status in Ubuntu on IBM z Systems: New Status in linux package in Ubuntu: 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 source package in Cosmic: In Progress Bug description: Description: cpum_sf: ensure sample freq is non-zero Symptom: A kernel crash might occur. Problem: An FP divide exception during the sample rate initialization for the hardware sampling facility. Solution: Ensure that the sample frequency of the perf event attribute is non-zero. Reproduction: Run trinity against the perf_event_open() syscall. Upstream-ID: 4bbaf2584b86b0772413edeac22ff448f36351b1 Component: kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1772593/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1765279] Re: Unable to build libhugetlbfs test on 4.15 Bionic
** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux-kvm (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: Incomplete => Triaged ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Bionic) Status: New => Triaged ** Changed in: linux-kvm (Ubuntu) Status: Confirmed => 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/1765279 Title: Unable to build libhugetlbfs test on 4.15 Bionic Status in linux package in Ubuntu: Triaged Status in linux-kvm package in Ubuntu: New Status in linux source package in Bionic: Triaged Status in linux-kvm source package in Bionic: New Bug description: When trying to build the libhugetlbfs test Bionic, it will fail with: CC32 obj32/linkhuge_nofd.o LD32 (hugelink test) obj32/linkhuge_nofd CC32 obj32/linkshare.o LD32 (hugelink test) obj32/linkshare LD32 (xB test) obj32/xB.linkhuge /usr/bin/x86_64-linux-gnu-ld: unrecognized option '--hugetlbfs-link=B' /usr/bin/x86_64-linux-gnu-ld: use the --help option for usage information collect2: error: ld returned 1 exit status Makefile:227: recipe for target 'obj32/xB.linkhuge' failed make[1]: *** [obj32/xB.linkhuge] Error 1 Makefile:242: recipe for target 'tests/all' failed make: *** [tests/all] Error 2 Steps: 1. git clone --depth=1 -b next https://github.com/libhugetlbfs/libhugetlbfs.git 2. cd libhugetlbfs 3. make ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-1003-kvm 4.15.0-1003.3 ProcVersionSignature: User Name 4.15.0-1003.3-kvm 4.15.10 Uname: Linux 4.15.0-1003-kvm x86_64 ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 Date: Thu Apr 19 04:44:08 2018 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1765279/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1772564] Re: package linux-image-extra-4.13.0-43-generic (not installed) failed to install/upgrade: unable to open '/lib/modules/4.13.0-43-generic/kernel/drivers/hwmon/vt1211.ko
You may need to run the following from a terminal: sudo apt-get install -f sudo apt-get clean sudo apt-get update Then re-install the package or updates. If that does not resolve your issue, please mark the bug as "Confirmed" ** Changed in: linux-hwe (Ubuntu) Importance: Undecided => Medium ** Changed in: linux-hwe (Ubuntu) Status: New => Incomplete ** Package changed: linux-hwe (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1772564 Title: package linux-image-extra-4.13.0-43-generic (not installed) failed to install/upgrade: unable to open '/lib/modules/4.13.0-43-generic/kernel/drivers/hwmon/vt1211.ko.dpkg- new': Operation not permitted Status in linux package in Ubuntu: Incomplete Bug description: I installed f-secure antivirus and this started to appear ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-extra-4.13.0-43-generic (not installed) ProcVersionSignature: Ubuntu 4.13.0-41.46~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-41-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.17 Architecture: amd64 Date: Tue May 22 09:54:07 2018 DuplicateSignature: package:linux-image-extra-4.13.0-43-generic:(not installed) Unpacking linux-image-extra-4.13.0-43-generic (4.13.0-43.48~16.04.1) ... dpkg: error processing archive /var/cache/apt/archives/linux-image-extra-4.13.0-43-generic_4.13.0-43.48~16.04.1_amd64.deb (--unpack): unable to open '/lib/modules/4.13.0-43-generic/kernel/drivers/hwmon/vt1211.ko.dpkg-new': Operation not permitted ErrorMessage: unable to open '/lib/modules/4.13.0-43-generic/kernel/drivers/hwmon/vt1211.ko.dpkg-new': Operation not permitted InstallationDate: Installed on 2018-02-11 (99 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: linux-hwe Title: package linux-image-extra-4.13.0-43-generic (not installed) failed to install/upgrade: unable to open '/lib/modules/4.13.0-43-generic/kernel/drivers/hwmon/vt1211.ko.dpkg-new': Operation not permitted UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1772564/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1772593] Re: cpum_sf: ensure sample freq is non-zero
I built Xenial, Artful and Bionic test kernels with commit 4bbaf2584b86b0772413edeac22ff448f36351b1. The test kernel can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1772593 Can you test this kernel and see if it resolves this bug? Note about installing test kernels: • If the test kernel is prior to 4.15(Bionic) you need to install the linux-image and linux-image-extra .deb packages. • If the test kernel is 4.15(Bionic) or newer, you need to install the linux-modules, linux-modules-extra and linux-image-unsigned .deb packages. Thanks in advance! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1772593 Title: cpum_sf: ensure sample freq is non-zero Status in Ubuntu on IBM z Systems: New Status in linux package in Ubuntu: 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 source package in Cosmic: In Progress Bug description: Description: cpum_sf: ensure sample freq is non-zero Symptom: A kernel crash might occur. Problem: An FP divide exception during the sample rate initialization for the hardware sampling facility. Solution: Ensure that the sample frequency of the perf event attribute is non-zero. Reproduction: Run trinity against the perf_event_open() syscall. Upstream-ID: 4bbaf2584b86b0772413edeac22ff448f36351b1 Component: kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1772593/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1772682] Re: No sound
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.17 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.17-rc6 ** 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/1772682 Title: No sound Status in linux package in Ubuntu: Confirmed Bug description: I have Dell Inspiron 5758 with UBUNTU 14.04 LTS.have I tried to update system but the computer did not finish updating, and informed me that there is no internet connection, while the connection was OK. As a result, I still have not been any sound in the computer. Sincerely yours, Andrew. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-147-generic 3.13.0-147.196 ProcVersionSignature: Ubuntu 3.13.0-147.196-generic 3.13.11-ckt39 Uname: Linux 3.13.0-147-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.23 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: country RU: (2402 - 2482 @ 40), (N/A, 20) (5735 - 5835 @ 20), (N/A, 30) Date: Tue May 22 19:03:51 2018 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 HibernationDevice: RESUME=UUID=e4298f48-6ba8-489f-b77c-bdb717a22436 InstallationDate: Installed on 2016-01-25 (848 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 MachineType: Dell Inc. Inspiron 5758 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-147-generic root=UUID=63a6a91d-fec3-47ee-982b-7dd7b57320f1 ro quiet splash radeon.modeset=0 nouveau.modeset=0 vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-147-generic N/A linux-backports-modules-3.13.0-147-generic N/A linux-firmware 1.127.24 SourcePackage: linux StagingDrivers: rts5139 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/06/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.name: 09CGRW dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA07:bd11/06/2015:svnDellInc.:pnInspiron5758:pvr01:rvnDellInc.:rn09CGRW:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 5758 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1772682/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1771844] Re: powerpc/livepatch: Implement reliable stack tracing for the consistency model
I built a new test kernel and included the source package. The test kernel can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1771844 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1771844 Title: powerpc/livepatch: Implement reliable stack tracing for the consistency model Status in The Ubuntu-power-systems project: Triaged Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: In Progress Bug description: == Comment: #0 - Kamalesh Babulal - 2018-05-15 09:37:52 == Livepatch has a consistency model which is a hybrid of kGraft and kpatch: it uses kGraft's per-task consistency and syscall barrier switching combined with kpatch's stack trace switching. The current approach is stack checking of sleeping tasks. If no affected functions are on the stack of a given task, the task is patched. In most cases this will patch most or all of the tasks on the first try. Otherwise, it'll keep trying periodically. This patch implements the reliable stack tracing for consistency model a.k.a HAVE_RELIABLE_STACKTRACE. This will help in switching livepatching implementation to basic per- task consistency model. It is the foundation, which will help us enable security patches changing function or data semantics. This is the biggest remaining piece needed on ppc64le to make livepatch more generally useful. https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?id=df78d3f6148092d33a9a24c7a9cfac To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1771844/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1772575] Re: Kernel 4.4 NBD size overflow with image size exceeding 1TB
** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Triaged ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Status: New => In Progress ** Changed in: linux (Ubuntu) Status: Triaged => Invalid ** Changed in: linux (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Xenial) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1772575 Title: Kernel 4.4 NBD size overflow with image size exceeding 1TB Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: In Progress Bug description: Release 16.04, kernel 4.4.0-124-generic There's an issue in kernel's NBD module which prevents some larger images to be correctly "connected" , largely described here: https://github.com/NetworkBlockDevice/nbd/issues/44 There is a small patch here that was accepted into mainline 4.10: https://www.spinics.net/lists/linux-block/msg07060.html This is a regression from the previous LTS 3.13 kernel. Here is a small example of the faulty behaviour: # qemu-img create -f qcow2 test.img 1100G Formatting 'test.img', fmt=qcow2 size=1181116006400 cluster_size=65536 lazy_refcounts=off refcount_bits=16 # qemu-nbd -c /dev/nbd0 test.img # blockdev --getsize64 /dev/nbd0 18446743055802302464 The correct response would be 1181116006400; this breaks most tools and makes the image unusable, e.g. # fdisk -l /dev/nbd0 fdisk: cannot open /dev/nbd0: Invalid argument --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 21 12:51 seq crw-rw 1 root audio 116, 33 May 21 12:51 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.17 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=/dev/mapper/VolGroup00-swap_1 IwConfig: Error: [Errno 2] No such file or directory MachineType: Supermicro SYS-1028R-WTR Package: linux (not installed) PciMultimedia: ProcEnviron: LANGUAGE=en_AU: TERM=xterm PATH=(custom, no user) LANG=en_AU SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-124-generic root=/dev/mapper/VolGroup00-root ro nomodeset elevator=noop consoleblank=0 net.ifnames=0 biosdevname=0 modprobe.blacklist=igb nosplash quiet ProcVersionSignature: Ubuntu 4.4.0-124.148-generic 4.4.117 RelatedPackageVersions: linux-restricted-modules-4.4.0-124-generic N/A linux-backports-modules-4.4.0-124-generic N/A linux-firmware 1.157.18 RfKill: Error: [Errno 2] No such file or directory Tags: xenial xenial Uname: Linux 4.4.0-124-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: 02/08/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3.0a dmi.board.asset.tag: Default string dmi.board.name: X10DRW-i dmi.board.vendor: Supermicro dmi.board.version: 1.10 dmi.chassis.asset.tag: Default string dmi.chassis.type: 1 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3.0a:bd02/08/2018:svnSupermicro:pnSYS-1028R-WTR:pvr0123456789:rvnSupermicro:rnX10DRW-i:rvr1.10:cvnSupermicro:ct1:cvr0123456789: dmi.product.name: SYS-1028R-WTR dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1772575/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1772573] Re: package linux-image-4.15.0-20-generic 4.15.0-20.21 failed to install/upgrade: installed linux-image-4.15.0-20-generic package pre-removal script subprocess returned
You may need to run the following from a terminal: sudo apt-get install -f sudo apt-get clean sudo apt-get update Then re-install the package or updates. If that does not resolve your issue, please mark the bug as "Confirmed" ** Changed in: linux-signed (Ubuntu) Importance: Undecided => Medium ** Changed in: linux-signed (Ubuntu) Status: New => Incomplete ** Package changed: linux-signed (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1772573 Title: package linux-image-4.15.0-20-generic 4.15.0-20.21 failed to install/upgrade: installed linux-image-4.15.0-20-generic package pre- removal script subprocess returned error exit status 1 Status in linux package in Ubuntu: Incomplete Bug description: Upgrade to newer kernel failed via command line, I used Synaptic and there were 2 broken packages according to it. I removed/unmarked all but the current kernel "linux-image" files and that seems to have resolved the broken packages. I'm submitting this BEFORE I reboot just in case ProblemType: Package DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-20-generic 4.15.0-20.21 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: qnx4 hfsplus hfs minix ntfs jfs rfcomm pci_stub bnep uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_core videodev media rtsx_usb_ms memstick btusb btrtl btbcm btintel bluetooth rtl8723be btcoexist rtl8723_common rtl_pci rtlwifi mac80211 intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp cfg80211 snd_hda_codec_hdmi snd_hda_codec_conexant snd_hda_codec_generic snd_hda_intel snd_hda_codec intel_cstate intel_rapl_perf snd_hda_core mei_me mei lpc_ich ideapad_laptop sparse_keymap shpchp mac_hid rtsx_usb_sdmmc rtsx_usb nouveau i915 mxm_wmi r8169 wmi ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Tue May 22 06:18:12 2018 DpkgTerminalLog: Removing linux-modules-extra-4.15.0-20-generic (4.15.0-20.21) ... Removing linux-image-4.15.0-20-generic (4.15.0-20.21) ... E: Aborting removal of the running kernel dpkg: error processing package linux-image-4.15.0-20-generic (--remove): installed linux-image-4.15.0-20-generic package pre-removal script subprocess returned error exit status 1 DuplicateSignature: package:linux-image-4.15.0-20-generic:4.15.0-20.21 Removing linux-image-4.15.0-20-generic (4.15.0-20.21) ... E: Aborting removal of the running kernel dpkg: error processing package linux-image-4.15.0-20-generic (--remove): installed linux-image-4.15.0-20-generic package pre-removal script subprocess returned error exit status 1 ErrorMessage: installed linux-image-4.15.0-20-generic package pre-removal script subprocess returned error exit status 1 InstallationDate: Installed on 2015-03-07 (1171 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: linux-signed Title: package linux-image-4.15.0-20-generic 4.15.0-20.21 failed to install/upgrade: installed linux-image-4.15.0-20-generic package pre-removal script subprocess returned error exit status 1 UpgradeStatus: Upgraded to bionic on 2018-05-08 (13 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1772573/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1772575] Re: Kernel 4.4 NBD size overflow with image size exceeding 1TB
I built a test kernel with commit ef77b515243b3499d62cf446eda6ca7e0a0b079c. The test kernel can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1772575 Can you test this kernel and see if it resolves this bug? Thanks in advance! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1772575 Title: Kernel 4.4 NBD size overflow with image size exceeding 1TB Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: In Progress Bug description: Release 16.04, kernel 4.4.0-124-generic There's an issue in kernel's NBD module which prevents some larger images to be correctly "connected" , largely described here: https://github.com/NetworkBlockDevice/nbd/issues/44 There is a small patch here that was accepted into mainline 4.10: https://www.spinics.net/lists/linux-block/msg07060.html This is a regression from the previous LTS 3.13 kernel. Here is a small example of the faulty behaviour: # qemu-img create -f qcow2 test.img 1100G Formatting 'test.img', fmt=qcow2 size=1181116006400 cluster_size=65536 lazy_refcounts=off refcount_bits=16 # qemu-nbd -c /dev/nbd0 test.img # blockdev --getsize64 /dev/nbd0 18446743055802302464 The correct response would be 1181116006400; this breaks most tools and makes the image unusable, e.g. # fdisk -l /dev/nbd0 fdisk: cannot open /dev/nbd0: Invalid argument --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 21 12:51 seq crw-rw 1 root audio 116, 33 May 21 12:51 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.17 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=/dev/mapper/VolGroup00-swap_1 IwConfig: Error: [Errno 2] No such file or directory MachineType: Supermicro SYS-1028R-WTR Package: linux (not installed) PciMultimedia: ProcEnviron: LANGUAGE=en_AU: TERM=xterm PATH=(custom, no user) LANG=en_AU SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-124-generic root=/dev/mapper/VolGroup00-root ro nomodeset elevator=noop consoleblank=0 net.ifnames=0 biosdevname=0 modprobe.blacklist=igb nosplash quiet ProcVersionSignature: Ubuntu 4.4.0-124.148-generic 4.4.117 RelatedPackageVersions: linux-restricted-modules-4.4.0-124-generic N/A linux-backports-modules-4.4.0-124-generic N/A linux-firmware 1.157.18 RfKill: Error: [Errno 2] No such file or directory Tags: xenial xenial Uname: Linux 4.4.0-124-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: 02/08/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3.0a dmi.board.asset.tag: Default string dmi.board.name: X10DRW-i dmi.board.vendor: Supermicro dmi.board.version: 1.10 dmi.chassis.asset.tag: Default string dmi.chassis.type: 1 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3.0a:bd02/08/2018:svnSupermicro:pnSYS-1028R-WTR:pvr0123456789:rvnSupermicro:rnX10DRW-i:rvr1.10:cvnSupermicro:ct1:cvr0123456789: dmi.product.name: SYS-1028R-WTR dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1772575/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1752961] Re: With kernel 4.13 btrfs scans for devices before all devices have been discovered
I'd like to perform a bisect to figure out what commit caused this
regression. We need to identify the earliest kernel where the issue
started happening as well as the last kernel that did not have this
issue.
Can you test the following kernels and report back? We are looking for
the first kernel version that exhibits this bug:
v4.12 Final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.12/
v4.13-rc1: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.13-rc1/
v4.13-rc4: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.13-rc4/
v4.13 Final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.13/
You don't have to test every kernel, just up until the kernel that first
has this bug.
Thanks in advance!
** Tags added: performing-bisect
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1752961
Title:
With kernel 4.13 btrfs scans for devices before all devices have been
discovered
Status in linux package in Ubuntu:
Confirmed
Bug description:
See attached dmesg outputs for booting kernels 4.11.x (working) and
4.13.x (not working).
dmesg-4.11.0-14-good.txt shows the dmesg output when booting kernel 4.11.x.
btrfs scans for devices after all 4 (sda, sdb, sdc, sdd) of the devices have
been discovered by the kernel. The btrfs RAID1 filesystem mounts, and
everything is good.
dmesg-4.13.0-36-fail.txt shows the dmesg output when booting kernel 4.13.x.
btrfs scans for devices after only 2 (sda, sdb) of the devices have been
discovered by the kernel. The btrfs RAID1 filesystem fails to mount ("failed
to read the system array: -5"). The remaining 2 devices (sdc, sdd) are
discovered by the kernel immediately afterward. At the end of the log, I run
`btrfs device scan` and mount the filesystem manually.
Hardware:
HP ProLiant MicroServer Gen8
4x WDC WD20EFRX
---
AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code
2: ls: cannot access '/dev/snd/': No such file or directory
AplayDevices: aplay: device_list:270: no soundcards found...
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
ArecordDevices: arecord: device_list:270: no soundcards found...
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2015-10-15 (933 days ago)
InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
MachineType: HP ProLiant MicroServer Gen8
Package: linux (not installed)
ProcEnviron:
TERM=linux
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-20-generic
root=UUID=d976ab07-8377-46dd-ac6c-f5f7312a8305 ro rootflags=subvol=@
rootdelay=10
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
Tags: bionic apport-hook-error
Uname: Linux 4.15.0-20-generic x86_64
UnreportableReason: This report is about a package that is not installed.
UpgradeStatus: Upgraded to bionic on 2018-05-05 (0 days ago)
UserGroups:
_MarkForUpload: True
dmi.bios.date: 07/16/2015
dmi.bios.vendor: HP
dmi.bios.version: J06
dmi.chassis.type: 7
dmi.chassis.vendor: HP
dmi.modalias:
dmi:bvnHP:bvrJ06:bd07/16/2015:svnHP:pnProLiantMicroServerGen8:pvr:cvnHP:ct7:cvr:
dmi.product.family: ProLiant
dmi.product.name: ProLiant MicroServer Gen8
dmi.sys.vendor: HP
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752961/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1771467] Re: Reboot/shutdown kernel panic on HP DL360/DL380 Gen9 w/ bionic 4.15.0
** Changed in: linux (Ubuntu Bionic)
Status: Confirmed => Triaged
** Changed in: linux (Ubuntu)
Status: Confirmed => Triaged
** Also affects: linux via
https://bugzilla.kernel.org/show_bug.cgi?id=199779
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1771467
Title:
Reboot/shutdown kernel panic on HP DL360/DL380 Gen9 w/ bionic 4.15.0
Status in Linux:
Unknown
Status in linux package in Ubuntu:
Triaged
Status in linux source package in Bionic:
Triaged
Bug description:
Verified on multiple DL360 Gen9 servers with up to date firmware.
Just before reboot or shutdown, there is the following panic:
[ 289.093083] {1}[Hardware Error]: Hardware error from APEI Generic Hardware
Error Source: 1
[ 289.093085] {1}[Hardware Error]: event severity: fatal
[ 289.093087] {1}[Hardware Error]: Error 0, type: fatal
[ 289.093088] {1}[Hardware Error]: section_type: PCIe error
[ 289.093090] {1}[Hardware Error]: port_type: 4, root port
[ 289.093091] {1}[Hardware Error]: version: 1.16
[ 289.093093] {1}[Hardware Error]: command: 0x6010, status: 0x0143
[ 289.093094] {1}[Hardware Error]: device_id: :00:01.0
[ 289.093095] {1}[Hardware Error]: slot: 0
[ 289.093096] {1}[Hardware Error]: secondary_bus: 0x03
[ 289.093097] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x2f02
[ 289.093098] {1}[Hardware Error]: class_code: 040600
[ 289.093378] {1}[Hardware Error]: bridge: secondary_status: 0x2000,
control: 0x0003
[ 289.093380] {1}[Hardware Error]: Error 1, type: fatal
[ 289.093381] {1}[Hardware Error]: section_type: PCIe error
[ 289.093382] {1}[Hardware Error]: port_type: 4, root port
[ 289.093383] {1}[Hardware Error]: version: 1.16
[ 289.093384] {1}[Hardware Error]: command: 0x6010, status: 0x0143
[ 289.093386] {1}[Hardware Error]: device_id: :00:01.0
[ 289.093386] {1}[Hardware Error]: slot: 0
[ 289.093387] {1}[Hardware Error]: secondary_bus: 0x03
[ 289.093388] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x2f02
[ 289.093674] {1}[Hardware Error]: class_code: 040600
[ 289.093676] {1}[Hardware Error]: bridge: secondary_status: 0x2000,
control: 0x0003
[ 289.093678] Kernel panic - not syncing: Fatal hardware error!
[ 289.093745] Kernel Offset: 0x1cc0 from 0x8100 (relocation
range: 0x8000-0xbfff)
[ 289.105835] ERST: [Firmware Warn]: Firmware does not respond in time.
It does eventually restart after this. Then during the subsequent
POST, the following warning appears:
Embedded RAID 1 : Smart Array P440ar Controller - (2048 MB, V6.30) 7 Logical
Drive(s) - Operation Failed
- 1719-Slot 0 Drive Array - A controller failure event occurred prior
to this power-up. (Previous lock up code = 0x13) Action: Install the
latest controller firmware. If the problem persists, replace the
controller.
The latter's symptoms are described in
https://support.hpe.com/hpsc/doc/public/display?docId=emr_na-c04805565
but the running storage controller firmware is much newer than the
doc's resolution.
Neither of these problems occur during shutdown/reboot on the xenial
kernel.
FWIW, when running on old P89 (1.50 (07/20/2015) vs 2.56
(01/22/2018)), the shutdown failure mode was a loop like so:
[529151.035267] NMI: IOCK error (debug interrupt?) for reason 75 on CPU 0.
[529153.222883] Uhhuh. NMI received for unknown reason 25 on CPU 0.
[529153.222884] Do you have a strange power saving mode enabled?
[529153.222884] Dazed and confused, but trying to continue
[529153.554447] Uhhuh. NMI received for unknown reason 25 on CPU 0.
[529153.554448] Do you have a strange power saving mode enabled?
[529153.554449] Dazed and confused, but trying to continue
[529153.554450] Uhhuh. NMI received for unknown reason 25 on CPU 0.
[529153.554451] Do you have a strange power saving mode enabled?
[529153.554452] Dazed and confused, but trying to continue
[529153.554452] Uhhuh. NMI received for unknown reason 25 on CPU 0.
[529153.554453] Do you have a strange power saving mode enabled?
[529153.554454] Dazed and confused, but trying to continue
[529153.554454] Uhhuh. NMI received for unknown reason 35 on CPU 0.
[529153.554455] Do you have a strange power saving mode enabled?
[529153.554456] Dazed and confused, but trying to continue
[529153.554457] Uhhuh. NMI received for unknown reason 25 on CPU 0.
[529153.554458] Do you have a strange power saving mode enabled?
[529153.554458] Dazed and confused, but trying to continue
[529153.554459] Uhhuh. NMI received for unknown reason 25 on CPU 0.
[529153.554460] Do you have a strange power saving mode enabled?
[529153.554460] Dazed and confused, but trying to continue
[529154.953916] Uhhuh. NMI re
[Kernel-packages] [Bug 1771181] Re: Ubuntu 18.04: LSI SAS93xx HBA detects incorrect bios version
This issue appears to be an upstream bug, since you tested the latest upstream kernel. Would it be possible for you to open an upstream bug report[0]? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug. Please follow the instructions on the wiki page[0]. The first step is to email the appropriate mailing list. If no response is received, then a bug may be opened on bugzilla.kernel.org. Once this bug is reported upstream, please add the tag: 'kernel-bug- reported-upstream'. [0] https://wiki.ubuntu.com/Bugs/Upstream/kernel ** Changed in: linux (Ubuntu) Status: Confirmed => 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/1771181 Title: Ubuntu 18.04: LSI SAS93xx HBA detects incorrect bios version Status in linux package in Ubuntu: Triaged Bug description: Under /sys/class/scsi_host/host*/ "version_bios" is reported as 16.00.00.00 instead of the correct bios version 08.35.04.00. The number that is reported under the version_bios is actually the version of the package used to flash the card. Installer(SAS3FLSH) DOS:\sas3flash_dos_rel\sas3flash.exe 16.00.00.00 ProblemType: Bug lsb_release -rd: Description:Ubuntu 18.04 LTS Release:18.04 Uname: Linux Uname -r: 4.15.0-20-generic Date: Mon May 14 13:18 2018 Architecture: x86_64 Kernel driver in use: mpt3sas Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1771181/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1758205] Re: Ubuntu 18.04 NVMe disks are not displayed on lsblk and /dev/disk/by-path (NVMe / Bolt ) (systemd?)
** Changed in: linux (Ubuntu)
Status: In Progress => Fix Released
** Changed in: linux (Ubuntu Bionic)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1758205
Title:
Ubuntu 18.04 NVMe disks are not displayed on lsblk and /dev/disk/by-
path (NVMe / Bolt ) (systemd?)
Status in The Ubuntu-power-systems project:
Incomplete
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Bionic:
Fix Released
Bug description:
---Problem Description---
Bolt based NVMe disks (namespaces) are not displayed on lsblk and
/dev/disk/by-path
# nvme list
Node SN Model
Namespace Usage Format FW Rev
- --
/dev/nvme0n1 S3RVNA0J600206 PCIe3 1.6TB NVMe Flash Adapter II x8
1 28.67 GB / 28.67 GB 4 KiB + 0 B MN12MN12
/dev/nvme0n10S3RVNA0J600206 PCIe3 1.6TB NVMe Flash Adapter II x8
10 28.67 GB / 28.67 GB 4 KiB + 0 B MN12MN12
/dev/nvme0n11S3RVNA0J600206 PCIe3 1.6TB NVMe Flash Adapter II x8
11 28.67 GB / 28.67 GB 4 KiB + 0 B MN12MN12
/dev/nvme0n12S3RVNA0J600206 PCIe3 1.6TB NVMe Flash Adapter II x8
12 28.67 GB / 28.67 GB 4 KiB + 0 B MN12MN12
/dev/nvme0n13S3RVNA0J600206 PCIe3 1.6TB NVMe Flash Adapter II x8
13 28.67 GB / 28.67 GB 4 KiB + 0 B MN12MN12
/dev/nvme0n14S3RVNA0J600206 PCIe3 1.6TB NVMe Flash Adapter II x8
14 28.67 GB / 28.67 GB 4 KiB + 0 B MN12MN12
/dev/nvme0n15S3RVNA0J600206 PCIe3 1.6TB NVMe Flash Adapter II x8
15 28.67 GB / 28.67 GB 4 KiB + 0 B MN12MN12
/dev/nvme0n16S3RVNA0J600206 PCIe3 1.6TB NVMe Flash Adapter II x8
16 28.67 GB / 28.67 GB 4 KiB + 0 B MN12MN12
/dev/nvme0n17S3RVNA0J600206 PCIe3 1.6TB NVMe Flash Adapter II x8
17 28.67 GB / 28.67 GB 4 KiB + 0 B MN12MN12
/dev/nvme0n18S3RVNA0J600206 PCIe3 1.6TB NVMe Flash Adapter II x8
18 28.67 GB / 28.67 GB 4 KiB + 0 B MN12MN12
/dev/nvme0n19S3RVNA0J600206 PCIe3 1.6TB NVMe Flash Adapter II x8
19 28.67 GB / 28.67 GB 4 KiB + 0 B MN12MN12
/dev/nvme0n2 S3RVNA0J600206 PCIe3 1.6TB NVMe Flash Adapter II x8
2 28.67 GB / 28.67 GB 4 KiB + 0 B MN12MN12
/dev/nvme0n20S3RVNA0J600206 PCIe3 1.6TB NVMe Flash Adapter II x8
20 28.67 GB / 28.67 GB 4 KiB + 0 B MN12MN12
/dev/nvme0n21S3RVNA0J600206 PCIe3 1.6TB NVMe Flash Adapter II x8
21 28.67 GB / 28.67 GB 4 KiB + 0 B MN12MN12
/dev/nvme0n22S3RVNA0J600206 PCIe3 1.6TB NVMe Flash Adapter II x8
22 28.67 GB / 28.67 GB 4 KiB + 0 B MN12MN12
/dev/nvme0n23S3RVNA0J600206 PCIe3 1.6TB NVMe Flash Adapter II x8
23 28.67 GB / 28.67 GB 4 KiB + 0 B MN12MN12
/dev/nvme0n24S3RVNA0J600206 PCIe3 1.6TB NVMe Flash Adapter II x8
24 28.67 GB / 28.67 GB 4 KiB + 0 B MN12MN12
/dev/nvme0n25S3RVNA0J600206 PCIe3 1.6TB NVMe Flash Adapter II x8
25 28.67 GB / 28.67 GB 4 KiB + 0 B MN12MN12
/dev/nvme0n26S3RVNA0J600206 PCIe3 1.6TB NVMe Flash Adapter II x8
26 28.67 GB / 28.67 GB 4 KiB + 0 B MN12MN12
/dev/nvme0n27S3RVNA0J600206 PCIe3 1.6TB NVMe Flash Adapter II x8
27 28.67 GB / 28.67 GB 4 KiB + 0 B MN12MN12
/dev/nvme0n28S3RVNA0J600206 PCIe3 1.6TB NVMe Flash Adapter II x8
28 28.67 GB / 28.67 GB 4 KiB + 0 B MN12MN12
/dev/nvme0n29S3RVNA0J600206 PCIe3 1.6TB NVMe Flash Adapter II x8
29 28.67 GB / 28.67 GB 4 KiB + 0 B MN12MN12
/dev/nvme0n3 S3RVNA0J600206 PCIe3 1.6TB NVMe Flash Adapter II x8
3 28.67 GB / 28.67 GB 4 KiB + 0 B MN12MN12
/dev/nvme0n30S3RVNA0J600206 PCIe3 1.6TB NVMe Flash Adapter II x8
30 28.67 GB / 28.67 GB 4 KiB + 0 B MN12MN12
/dev/nvme0n31S3RVNA0J600206 PCIe3 1.6TB NVMe Flash Adapter II x8
31 28.67 GB / 28.67 GB 4 KiB + 0 B MN12MN12
/dev/nvme0n32S3RVNA0J600206 PCIe3 1.6TB NVMe Flash Adapter II x8
32 28.67 GB / 28.67 GB 4 KiB + 0 B MN12MN12
/dev/nvme0n4 S3RVNA0J600206 PCIe3 1.6TB NVMe Flash Adapter II x8
4 28.67 GB / 28.67 GB 4 KiB + 0 B MN12MN12
/dev/nvme0n5 S3RVNA0J600206 PCIe3 1.6
[Kernel-packages] [Bug 1772760] Re: Touchpad slows down and then stops working
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.17 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.17-rc6 ** Changed in: linux-signed (Ubuntu) Importance: Undecided => Medium ** Changed in: linux-signed (Ubuntu) Status: New => Incomplete ** Package changed: linux-signed (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1772760 Title: Touchpad slows down and then stops working Status in linux package in Ubuntu: New Bug description: Cannot find a reason, but sometimes once a day, sometimes twice a day, my touchpad starts to work slowly, like jumping, and after a few seconds, it completely stops working. At some point, I did something with Terminal and it started working, but cannot reproduce it. The only thing that seems to be really working is to Suspend laptop and come back in Ubuntu (or restart, but that means to close everything + it takes more time). While I wrote this text, it seems to have recovered by itself, it is working right now, but this is unreliable and cannot be used in production (what about stopping it during a presentation, cannot suspend in a meeting). Hopefully, it is some kernel problem, as I reported kernel package. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-22-generic 4.15.0-22.24 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Wed May 23 01:15:44 2018 InstallationDate: Installed on 2018-04-27 (25 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1772760/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1772775] Re: 4.4.0-127.153 generates many "sit: non-ECT" messages
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.17 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.17-rc6 ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Tags added: kernel-da-key ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1772775 Title: 4.4.0-127.153 generates many "sit: non-ECT" messages Status in linux package in Ubuntu: Incomplete Bug description: Since deploying linux-image-4.4.0-127-generic (4.4.0-127.153) on a Xenial VM with a sit tunnel, I get such messages: May 22 10:49:38 gw kernel: [ 68.121601] sit: non-ECT from 0.0.0.0 with TOS=0x5 Those are logged quite often: # grep -cF 'sit: non-ECT' /var/log/syslog 9108 Reverting to linux-image-4.4.0-124-generic (4.4.0-124.148) fixes the issue. # lsb_release -rd Description: Ubuntu 16.04.4 LTS Release: 16.04 # apt-cache policy linux-image-4.4.0-127-generic linux-image-4.4.0-127-generic: Installed: 4.4.0-127.153 Candidate: 4.4.0-127.153 Version table: *** 4.4.0-127.153 500 500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-127-generic 4.4.0-127.153 ProcVersionSignature: Ubuntu 4.4.0-127.153-generic 4.4.128 Uname: Linux 4.4.0-127-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 22 20:08 seq crw-rw 1 root audio 116, 33 May 22 20:08 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.17 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser' CRDA: N/A Date: Tue May 22 21:18:45 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Error: [Errno 2] No such file or directory: 'lspci' Lsusb: Error: [Errno 2] No such file or directory: 'lsusb' MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-127-generic root=UUID=67f7ee15-64f4-4c85-805c-08386d5fed8b ro console=ttyS0 net.ifnames=0 kaslr vsyscall=none nmi_watchdog=0 possible_cpus=1 pti=on nr_cpus=1 RelatedPackageVersions: linux-restricted-modules-4.4.0-127-generic N/A linux-backports-modules-4.4.0-127-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-2.5 dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.5:cvnQEMU:ct1:cvrpc-i440fx-2.5: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-2.5 dmi.sys.vendor: QEMU --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 22 21:33 seq crw-rw 1 root audio 116, 33 May 22 21:33 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.17 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: [Errno 2] No such file or directory CRDA: N/A DistroRelease: Ubuntu 16.04 IwConfig: Error: [Errno 2] No such file or directory Lspci: Error: [Errno 2] No such file or directory Lsusb: Error: [Errno 2] No such file or directory MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-124-generic root=UUID=67f7ee15-64f4-4c85-805c-08386d5fed8b ro kaslr net.ifnames=0 nmi_watchdog=0 nr_cpus=1 pti=on console=ttyS0 vsyscall=none ProcVersionSignature: Ubuntu 4.4.0-124.148-generic 4.4.117 RelatedPackageVersions: linux-restricted-modules-4.4.0-124-generic N/A linux-b
[Kernel-packages] [Bug 1768103] Re: Lancer A0 Asic HBA's won't boot with 18.04
Thank you for the update, Laurie. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1768103 Title: Lancer A0 Asic HBA's won't boot with 18.04 Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: We have discovered that an early asic model (A0) of our 16/32GB HBA's doesn't boot with the lpfc driver in Ubuntu 18.04. After further review and discussion, this has been deemed a low risk issue since early A0 HBA's were only ever shipped to OEMs for test purposes. These cards were never shipped to end customers. We have been working to replace those cards whenever we discover them. We'll leave it up to Canonical to decide whether they want to pull this in this single patch to an 18.04 subsequent update. Symptom: Ubuntu 18.04 with lpfc driver 12.0.0.0 they can't see LPe16002-M6 but can see LPe16002B-M6 Resolution: new lpfc driver patch update. scsi: lpfc: Fix WQ/CQ creation for older asic's. https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?h=4.18/scsi-queue&id=83fae8ca4ae09403bfb99542f1aaa292c06cb111 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768103/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1771344] Re: Fix enabling bridge MMIO windows
SRU request submitted:
https://lists.ubuntu.com/archives/kernel-team/2018-May/092677.html
** Description changed:
- == Comment: #0 - Breno Leitao
+ == SRU Justification ==
+ IBM is requesting this patch in Bionic and Artful to fix a regression. The
+ regression was introduced in v3.11-rc1. The patch fixes enabling bridge
+ MMIO windows. Commit 13a83eac373c was also cc'd to upstream stable, and
+ has already landed in Xenial via upstream stable updates.
+
+ == Fix ==
+ 13a83eac373c ("powerpc/eeh: Fix enabling bridge MMIO windows")
+
+ == Regression Potential ==
+ Low. Limited to powerpc and fixes a current regression.
+
+ == Test Case ==
+ A test kernel was built with this patch and tested by the original bug
reporter.
+ The bug reporter states the test kernel resolved the bug.
+
+
+ == Comment: #0 - Breno Leitao
On boot we save the configuration space of PCIe bridges. We do this so
when we get an EEH event and everything gets reset that we can restore
them.
-
+
Unfortunately we save this state before we've enabled the MMIO space
on the bridges. Hence if we have to reset the bridge when we come back
MMIO is not enabled and we end up taking an PE freeze when the driver
starts accessing again.
-
+
This patch forces the memory/MMIO and bus mastering on when restoring
bridges on EEH. Ideally we'd do this correctly by saving the
configuration space writes later, but that will have to come later in
a larger EEH rewrite. For now we have this simple fix.
-
+
The original bug can be triggered on a boston machine by doing:
- echo 0x8000 >
/sys/kernel/debug/powerpc/PCI0001/err_injct_outbound
+ echo 0x8000 >
/sys/kernel/debug/powerpc/PCI0001/err_injct_outbound
On boston, this PHB has a PCIe switch on it. Without this patch,
you'll see two EEH events, 1 expected and 1 the failure we are fixing
here. The second EEH event causes the anything under the PHB to
disappear (i.e. the i40e eth).
-
+
With this patch, only 1 EEH event occurs and devices properly recover.
This is commit id 13a83eac373c49c0a081cbcd137e79210fe78acd and should be
part of Ubuntu 18.04 kernel.
** Also affects: linux (Ubuntu Artful)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Artful)
Status: New => In Progress
** Changed in: linux (Ubuntu Artful)
Importance: Undecided => High
** Changed in: linux (Ubuntu Artful)
Assignee: (unassigned) => Joseph Salisbury (jsalisbury)
** Also affects: linux (Ubuntu Cosmic)
Importance: High
Assignee: Joseph Salisbury (jsalisbury)
Status: In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1771344
Title:
Fix enabling bridge MMIO windows
Status in The Ubuntu-power-systems project:
In Progress
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Artful:
In Progress
Status in linux source package in Bionic:
In Progress
Status in linux source package in Cosmic:
In Progress
Bug description:
== SRU Justification ==
IBM is requesting this patch in Bionic and Artful to fix a regression. The
regression was introduced in v3.11-rc1. The patch fixes enabling bridge
MMIO windows. Commit 13a83eac373c was also cc'd to upstream stable, and
has already landed in Xenial via upstream stable updates.
== Fix ==
13a83eac373c ("powerpc/eeh: Fix enabling bridge MMIO windows")
== Regression Potential ==
Low. Limited to powerpc and fixes a current regression.
== Test Case ==
A test kernel was built with this patch and tested by the original bug
reporter.
The bug reporter states the test kernel resolved the bug.
== Comment: #0 - Breno Leitao
On boot we save the configuration space of PCIe bridges. We do this so
when we get an EEH event and everything gets reset that we can restore
them.
Unfortunately we save this state before we've enabled the MMIO space
on the bridges. Hence if we have to reset the bridge when we come back
MMIO is not enabled and we end up taking an PE freeze when the driver
starts accessing again.
This patch forces the memory/MMIO and bus mastering on when restoring
bridges on EEH. Ideally we'd do this correctly by saving the
configuration space writes later, but that will have to come later in
a larger EEH rewrite. For now we have this simple fix.
The original bug can be triggered on a boston machine by doing:
echo 0x8000 >
/sys/kernel/debug/powerpc/PCI0001/err_injct_outbound
On boston, this PHB has a PCIe switch on it. Without this patch,
you'll see two EEH events, 1 expected and 1 the failure we are fixing
here. The second EEH event causes the anything under the PHB to
disappear (i.e. the i40e eth).
With this pat
[Kernel-packages] [Bug 1771844] Re: powerpc/livepatch: Implement reliable stack tracing for the consistency model
SRU request submitted:
https://lists.ubuntu.com/archives/kernel-team/2018-May/092679.html
** Description changed:
- == Comment: #0 - Kamalesh Babulal - 2018-05-15 09:37:52 ==
- Livepatch has a consistency model which is a hybrid of kGraft and kpatch: it
uses kGraft's per-task consistency and syscall barrier switching combined with
kpatch's stack trace switching. The current approach is stack checking of
sleeping tasks. If no affected functions are on the stack of a given task, the
task is patched. In most cases this will patch most or all of the tasks on the
first try. Otherwise, it'll keep trying periodically. This patch implements
the reliable stack tracing for consistency model a.k.a
HAVE_RELIABLE_STACKTRACE.
+ == SRU Justification ==
+ Livepatch has a consistency model which is a hybrid of kGraft and kpatch:
+ it uses kGraft's per-task consistency and syscall barrier switching
+ combined with kpatch's stack trace switching. The current approach is
+ stack checking of sleeping tasks. If no affected functions are on the
+ stack of a given task, the task is patched. In most cases this will patch
+ most or all of the tasks on the first try. Otherwise, it'll keep trying
+ periodically. This patch implements the reliable stack tracing for
+ consistency model a.k.a HAVE_RELIABLE_STACKTRACE.
- This will help in switching livepatching implementation to basic per-
- task consistency model. It is the foundation, which will help us enable
- security patches changing function or data semantics. This is the
- biggest remaining piece needed on ppc64le to make livepatch more
- generally useful.
+ This will help in switching livepatching implementation to basic per-task
+ consistency model. It is the foundation, which will help us enable
+ security patches changing function or data semantics. This is the biggest
+ remaining piece needed on ppc64le to make livepatch more generally useful.
+
+ == Fix ==
+ df78d3f61480 ("powerpc/livepatch: Implement reliable stack tracing for the
consistency model")
+
+ == Regression Potential ==
+ Low. Limited to powerpc.
+
+ == Test Case ==
+ A test kernel was built with this patch and tested by the original bug
reporter.
+ The bug reporter states the test kernel resolved the bug.
+
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?id=df78d3f6148092d33a9a24c7a9cfac
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1771844
Title:
powerpc/livepatch: Implement reliable stack tracing for the
consistency model
Status in The Ubuntu-power-systems project:
In Progress
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Bionic:
In Progress
Status in linux source package in Cosmic:
In Progress
Bug description:
== SRU Justification ==
Livepatch has a consistency model which is a hybrid of kGraft and kpatch:
it uses kGraft's per-task consistency and syscall barrier switching
combined with kpatch's stack trace switching. The current approach is
stack checking of sleeping tasks. If no affected functions are on the
stack of a given task, the task is patched. In most cases this will patch
most or all of the tasks on the first try. Otherwise, it'll keep trying
periodically. This patch implements the reliable stack tracing for
consistency model a.k.a HAVE_RELIABLE_STACKTRACE.
This will help in switching livepatching implementation to basic per-task
consistency model. It is the foundation, which will help us enable
security patches changing function or data semantics. This is the biggest
remaining piece needed on ppc64le to make livepatch more generally useful.
== Fix ==
df78d3f61480 ("powerpc/livepatch: Implement reliable stack tracing for the
consistency model")
== Regression Potential ==
Low. Limited to powerpc.
== Test Case ==
A test kernel was built with this patch and tested by the original bug
reporter.
The bug reporter states the test kernel resolved the bug.
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?id=df78d3f6148092d33a9a24c7a9cfac
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1771844/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1771780] Re: [LTCTest][OPAL][OP920] cpupower idle-info is not listing stop4 and stop5 idle states when all CORES are guarded
SRU request submitted: https://lists.ubuntu.com/archives/kernel-team/2018-May/092681.html ** Description changed: + == SRU Justification == + During testing, IBM found that cpupower idle-info is not listing stop4 and + stop5 idle states when all CORES are guarded. A patch has been + submitted upstream by IBM. However, the patch has not landed in + linux-next or mainline as of yet. For that reason, this SRU request is + being sent as a SAUCE patch request. + + + == Fix == + UBUNTU: SAUCE: cpuidle/powernv : init all present cpus for deep states + + == Regression Potential == + Low. Limited to powerpc. + + == Test Case == + A test kernel was built with this patch and tested by the original bug reporter. + The bug reporter states the test kernel resolved the bug. + + + == Comment: #0 - PAVAMAN SUBRAMANIYAM - 2018-05-16 04:07:59 == ---Problem Description--- cpupower idle-info is not listing stop4 and stop5 idle states when all CORES are guarded - + ---uname output--- Linux ltc-wspoon11 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:14:44 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux - - Machine Type = P9 - + + Machine Type = P9 + ---Debugger--- A debugger is not configured - + ---Steps to Reproduce--- Install a P9 Open Power Hardware with Ubuntu 18.04 OS. root@ltc-wspoon11:~# uname -a Linux ltc-wspoon11 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:14:44 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux root@ltc-wspoon11:~# cat /etc/os-release NAME="Ubuntu" VERSION="18.04 LTS (Bionic Beaver)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 18.04 LTS" VERSION_ID="18.04" HOME_URL="https://www.ubuntu.com/"; SUPPORT_URL="https://help.ubuntu.com/"; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"; VERSION_CODENAME=bionic UBUNTU_CODENAME=bionic Then guard an entire processor and also guard all the CORES in the processor 0 except for 1 single core. root@ltc-wspoon11:~# opal-gard list - ID | Error| Type | Path + ID | Error| Type | Path --- - 0001 | | Manual | /Sys0/Node0/Proc0/EQ1/EX0/Core0 - 0002 | | Manual | /Sys0/Node0/Proc0/EQ1/EX0/Core1 - 0003 | | Manual | /Sys0/Node0/Proc1 - 0004 | | Manual | /Sys0/Node0/Proc0/EQ2/EX0/Core1 - 0005 | | Manual | /Sys0/Node0/Proc0/EQ2/EX0/Core0 - 0006 | | Manual | /Sys0/Node0/Proc0/EQ2/EX1/Core0 - 0007 | | Manual | /Sys0/Node0/Proc0/EQ2/EX1/Core1 - 0008 | | Manual | /Sys0/Node0/Proc0/EQ3/EX0/Core0 - 0009 | | Manual | /Sys0/Node0/Proc0/EQ3/EX0/Core1 - 000a | | Manual | /Sys0/Node0/Proc0/EQ3/EX1/Core0 - 000b | | Manual | /Sys0/Node0/Proc0/EQ3/EX1/Core1 - 000c | | Manual | /Sys0/Node0/Proc0/EQ4/EX0/Core0 - 000d | | Manual | /Sys0/Node0/Proc0/EQ4/EX0/Core1 - 000e | | Manual | /Sys0/Node0/Proc0/EQ4/EX1/Core0 - 000f | | Manual | /Sys0/Node0/Proc0/EQ4/EX1/Core1 - 0010 | | Manual | /Sys0/Node0/Proc0/EQ5/EX0/Core0 - 0011 | | Manual | /Sys0/Node0/Proc0/EQ5/EX0/Core1 - 0012 | | Manual | /Sys0/Node0/Proc0/EQ5/EX1/Core0 - 0013 | | Manual | /Sys0/Node0/Proc0/EQ5/EX1/Core1 - 0014 | | Manual | /Sys0/Node0/Proc0/EQ1/EX1/Core0 - 0015 | | Manual | /Sys0/Node0/Proc0/EQ1/EX1/Core1 - 0016 | | Manual | /Sys0/Node0/Proc0/EQ0/EX1/Core1 - 0017 | | Manual | /Sys0/Node0/Proc0/EQ0/EX1/Core0 + 0001 | | Manual | /Sys0/Node0/Proc0/EQ1/EX0/Core0 + 0002 | | Manual | /Sys0/Node0/Proc0/EQ1/EX0/Core1 + 0003 | | Manual | /Sys0/Node0/Proc1 + 0004 | | Manual | /Sys0/Node0/Proc0/EQ2/EX0/Core1 + 0005 | | Manual | /Sys0/Node0/Proc0/EQ2/EX0/Core0 + 0006 | | Manual | /Sys0/Node0/Proc0/EQ2/EX1/Core0 + 0007 | | Manual | /Sys0/Node0/Proc0/EQ2/EX1/Core1 + 0008 | | Manual | /Sys0/Node0/Proc0/EQ3/EX0/Core0 + 0009 | | Manual | /Sys0/Node0/Proc0/EQ3/EX0/Core1 + 000a | | Manual | /Sys0/Node0/Proc0/EQ3/EX1/Core0 + 000b | | Manual | /Sys0/Node0/Proc0/EQ3/EX1/Core1 + 000c | | Manual | /Sys0/Node0/Proc0/EQ4/EX0/Core0 + 000d | | Manual | /Sys0/Node0/Proc0/EQ4/EX0/Core1 + 000e | | Manual | /Sys0/Node0/Proc0/EQ4/EX1/Core0 + 000f | | Manual | /Sys0/Node0/Proc0/EQ4/EX1/Core1 + 0010 | | Manual | /Sys0/Node0/Proc0/EQ5/EX0/Core0 + 0011 | | Manual | /Sys0/Node0/Proc0/EQ
[Kernel-packages] [Bug 1772575] Re: Kernel 4.4 NBD size overflow with image size exceeding 1TB
SRU request submitted:
https://lists.ubuntu.com/archives/kernel-team/2018-May/092684.html
** Description changed:
+ == SRU Justification ==
+ With the Xenial kernel, the bug reporter states there is an NBD size
+ overflow with image size exceeding 1TB.
+
+ There's an issue in kernel's NBD module which prevents some larger images to
be
+ correctly "connected" , largely described here:
+ https://github.com/NetworkBlockDevice/nbd/issues/44
+
+ This is a regression from Trusty and was fixed in mainline as of
+ v4.10-rc1.
+
+ == Fix ==
+ ef77b515243b ("nbd: use loff_t for blocksize and nbd_set_size args")
+
+ == Regression Potential ==
+ Medium. A backport was needed. However, it was due to some context
+ diffs and the way debugfs_create_u32 was used in Xenial and how
+ debugfs_create_u64 was used in the patch.
+
+ == Test Case ==
+ A test kernel was built with this patch and tested by the original bug
reporter.
+ The bug reporter states the test kernel resolved the bug.
+
+
+ == Original Bug Report ==
Release 16.04, kernel 4.4.0-124-generic
There's an issue in kernel's NBD module which prevents some larger images to
be
correctly "connected" , largely described here:
https://github.com/NetworkBlockDevice/nbd/issues/44
There is a small patch here that was accepted into mainline 4.10:
https://www.spinics.net/lists/linux-block/msg07060.html
This is a regression from the previous LTS 3.13 kernel.
Here is a small example of the faulty behaviour:
# qemu-img create -f qcow2 test.img 1100G
Formatting 'test.img', fmt=qcow2 size=1181116006400 cluster_size=65536
lazy_refcounts=off refcount_bits=16
# qemu-nbd -c /dev/nbd0 test.img
# blockdev --getsize64 /dev/nbd0
18446743055802302464
The correct response would be 1181116006400; this breaks most tools and
makes the image unusable, e.g.
# fdisk -l /dev/nbd0
fdisk: cannot open /dev/nbd0: Invalid argument
- ---
+ ---
AlsaDevices:
- total 0
- crw-rw 1 root audio 116, 1 May 21 12:51 seq
- crw-rw 1 root audio 116, 33 May 21 12:51 timer
+ total 0
+ crw-rw 1 root audio 116, 1 May 21 12:51 seq
+ crw-rw 1 root audio 116, 33 May 21 12:51 timer
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.20.1-0ubuntu2.17
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
DistroRelease: Ubuntu 16.04
HibernationDevice: RESUME=/dev/mapper/VolGroup00-swap_1
IwConfig: Error: [Errno 2] No such file or directory
MachineType: Supermicro SYS-1028R-WTR
Package: linux (not installed)
PciMultimedia:
-
+
ProcEnviron:
- LANGUAGE=en_AU:
- TERM=xterm
- PATH=(custom, no user)
- LANG=en_AU
- SHELL=/bin/bash
+ LANGUAGE=en_AU:
+ TERM=xterm
+ PATH=(custom, no user)
+ LANG=en_AU
+ SHELL=/bin/bash
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-124-generic
root=/dev/mapper/VolGroup00-root ro nomodeset elevator=noop consoleblank=0
net.ifnames=0 biosdevname=0 modprobe.blacklist=igb nosplash quiet
ProcVersionSignature: Ubuntu 4.4.0-124.148-generic 4.4.117
RelatedPackageVersions:
- linux-restricted-modules-4.4.0-124-generic N/A
- linux-backports-modules-4.4.0-124-generic N/A
- linux-firmware 1.157.18
+ linux-restricted-modules-4.4.0-124-generic N/A
+ linux-backports-modules-4.4.0-124-generic N/A
+ linux-firmware 1.157.18
RfKill: Error: [Errno 2] No such file or directory
Tags: xenial xenial
Uname: Linux 4.4.0-124-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: 02/08/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 3.0a
dmi.board.asset.tag: Default string
dmi.board.name: X10DRW-i
dmi.board.vendor: Supermicro
dmi.board.version: 1.10
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 1
dmi.chassis.vendor: Supermicro
dmi.chassis.version: 0123456789
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr3.0a:bd02/08/2018:svnSupermicro:pnSYS-1028R-WTR:pvr0123456789:rvnSupermicro:rnX10DRW-i:rvr1.10:cvnSupermicro:ct1:cvr0123456789:
dmi.product.name: SYS-1028R-WTR
dmi.product.version: 0123456789
dmi.sys.vendor: Supermicro
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1772575
Title:
Kernel 4.4 NBD size overflow with image size exceeding 1TB
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Xenial:
In Progress
Bug description:
== SRU Justification ==
With the Xenial kernel, the bug reporter states there is an NBD size
overflow with image size exceeding 1TB.
There's an issue in
[Kernel-packages] [Bug 1771826] Re: Creation of IMA file hashes fails when appraisal is enabled
SRU request submitted:
https://lists.ubuntu.com/archives/kernel-team/2018-May/092686.html
** Description changed:
+ == SRU Justification ==
+ On a system that has IMA appraisal enabled it is impossible to create
+ security.ima extended attribute files that contain IMA hash. This is
+ due to mainline commit c68ed80c97d, which prevents writing file hashes as
+ security.ima xattrs.
+
+ This bug is fixed by reverting commit c68ed80c97d, which is done by
+ mainline commit f5acb3dcba1f as of v4.10-rc1.
+
+ == Fix ==
+ f5acb3dcba1f ("Revert "ima: limit file hash setting by user to fix and log
modes"")
+
+ == Regression Potential ==
+ Low. This revert happend in v4.10-rc1. It has been in Artful and
+ Bionic for a while without any reported issues.
+
+ == Test Case ==
+ A test kernel was built with this patch and tested by the original bug
reporter.
+ The bug reporter states the test kernel resolved the bug.
+
+
+ == Original Bug Description ==
On a system that has IMA appraisal enabled it is impossible to create
security.ima extended attribute files that contain IMA hash.
For instance, consider the following use case:
1) extract application files to a staging area as non root user
2) verify that installation is correct
3) create IMA extended attributes for the installed files
4) move the files to their destination
5) change the files ownership to root
With kernel 4.4.x step 3 will fail.
The issues is fixed in upstream kernels by the following commit [1]:
commit f5acb3dcba1ffb7f0b8cbb9dba61500eea5d610b
Author: Mimi Zohar
Date: Wed Nov 2 09:14:16 2016 -0400
Revert "ima: limit file hash setting by user to fix and log modes"
[1]
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?i
d=f5acb3dcba1ffb7f0b8cbb9dba61500eea5d610b
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-124-generic 4.4.0-124.148
ProcVersionSignature: User Name 4.4.0-124.148-generic 4.4.117
Uname: Linux 4.4.0-124-generic x86_64
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 May 17 14:07 seq
crw-rw 1 root audio 116, 33 May 17 14:07 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.1-0ubuntu2.15
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:
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211
not found.
Date: Thu May 17 14:08:59 2018
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
Lsusb: Error: command ['lsusb'] failed with exit code 1:
MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
PciMultimedia:
ProcFB:
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-124-generic
root=UUID=aef88a4e-dbea-4cc7-be8b-03cf8501cc8f ro biosdevname=0 net.ifnames=0
console=tty1 console=ttyS0 crashkernel=384M-:128M
RelatedPackageVersions:
linux-restricted-modules-4.4.0-124-generic N/A
linux-backports-modules-4.4.0-124-generic N/A
linux-firmware 1.157.17
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/01/2014
dmi.bios.vendor: SeaBIOS
dmi.bios.version: rel-1.11.0-0-g63451fca13-prebuilt.qemu-project.org
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.version: pc-i440fx-2.12
dmi.modalias:
dmi:bvnSeaBIOS:bvrrel-1.11.0-0-g63451fca13-prebuilt.qemu-project.org:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.12:cvnQEMU:ct1:cvrpc-i440fx-2.12:
dmi.product.name: Standard PC (i440FX + PIIX, 1996)
dmi.product.version: pc-i440fx-2.12
dmi.sys.vendor: QEMU
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1771826
Title:
Creation of IMA file hashes fails when appraisal is enabled
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Xenial:
In Progress
Bug description:
== SRU Justification ==
On a system that has IMA appraisal enabled it is impossible to create
security.ima extended attribute files that contain IMA hash. This is
due to mainline commit c68ed80c97d, which prevents writing file hashes as
security.ima xattrs.
This bug is fixed by reverting commit c68ed80c97d, which is done by
mainline commit f5acb3dcba1f as of v4.10-rc1.
== Fix ==
f5acb3dcba1f ("Revert "ima: limit file hash setting by user to fix and log
modes"")
== Regression Potential ==
Low. This revert happend in v4.10-rc1. It has been in Artful and
Bionic for a while without any reported issues.
== Test Case ==
A test kernel was built with this patch and tested by the original bug
reporter.
The bug reporter states the test k
[Kernel-packages] [Bug 1771075] Re: General Protection fault in inotify (fixed upstream)
** Changed in: linux (Ubuntu Cosmic) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Bionic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1771075 Title: General Protection fault in inotify (fixed upstream) Status in linux package in Ubuntu: In Progress Status in linux source package in Cosmic: In Progress Bug description: We've run into some issues where upgrading the kernel from a 4.10 series to a 4.13 series on Ubuntu 16.04 hosts that make heavy use of inotify causes panics and lockups in the kernel in inotify-related code. Our particular use case seemed to hit these at a rate of one every 30 minutes or so when serving up production traffic. Unfortunately, I have been unable to replicate the issue so far with a simulated load-testing environment. When the issue occurs, we get dmesg entries like "BUG: soft lockup - CPU#0 stuck for 22s!" or "General protection fault: [#1] SMP PTI". In the soft lockup case, the host is still up but all I/O operations stall indefinitely (e.g. typing "sync" into the console will hang forever). In the protection fault case, the system reboots. I've attached dmesg output from the two cases to this bugreport. We have noticed the issue with the following kernels: - linux-image-4.13.0-1013-gcp - linux-image-4.13.0-1015-gcp - linux-image-4.13.0-36-generic We did _not_ have the issue with - linux-image-4.10.0-32-generic I've submitted this bug report from a system which should be configured identically to our production hosts that were having issue (the affected hosts were immediately rolled back to 4.10). This bug appears to have been fixed upstream as of 4.17-rc3 in this commit: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=d90a10e2444ba5a351fa695917258ff4c5709fa5 I would guess that perhaps this patch should be backported into both the 4.13 HWE and GCP Ubuntu kernel series? Thanks, KJ ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.13.0-1013-gcp 4.13.0-1013.17 ProcVersionSignature: Ubuntu 4.13.0-1013.17-gcp 4.13.16 Uname: Linux 4.13.0-1013-gcp x86_64 ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 Date: Mon May 14 07:58:29 2018 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-gcp UpgradeStatus: No upgrade log present (probably fresh install) --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 10 07:57 seq crw-rw 1 root audio 116, 33 May 10 07:57 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A DistroRelease: Ubuntu 16.04 IwConfig: Error: [Errno 2] No such file or directory Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Google Google Compute Engine Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-32-generic root=UUID=73ea38ed-7fcd-4871-8afa-17d36f4e4bfc ro scsi_mod.use_blk_mq=Y console=ttyS0 ProcVersionSignature: Ubuntu 4.10.0-32.36~16.04.1-generic 4.10.17 RelatedPackageVersions: linux-restricted-modules-4.10.0-32-generic N/A linux-backports-modules-4.10.0-32-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory Tags: xenial uec-images xenial uec-images Uname: Linux 4.10.0-32-generic x86_64 UnreportableReason: The report belongs to a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: WifiSyslog: _MarkForUpload: False dmi.bios.date: 01/01/2011 dmi.bios.vendor: Google dmi.bios.version: Google dmi.board.asset.tag: 98BEC19B-1DEB-1A9F-1146-C6E4D8577ADB dmi.board.name: Google Compute Engine dmi.board.vendor: Google dmi.chassis.type: 1 dmi.chassis.vendor: Google dmi.modalias: dmi:bvnGoogle:bvrGoogle:bd01/01/2011:svnGoogle:pnGoogleComputeEngine:pvr:rvnGoogle:rnGoogleComputeEngine:rvr:cvnGoogle:ct1:cvr: dmi.product.name: Google Compute Engine dmi.sys.vendor: Google To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1771075/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1771075] Re: General Protection fault in inotify (fixed upstream)
The commit to fix this bug was added to Artful and Bionic via bug 1765564, so I'll remove those bug tasks. I did, however, submit a request to have this commit added to Cosmic. ** Changed in: linux (Ubuntu Artful) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Cosmic) Status: Fix Committed => In Progress ** No longer affects: linux (Ubuntu Artful) ** No longer affects: linux (Ubuntu Bionic) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1771075 Title: General Protection fault in inotify (fixed upstream) Status in linux package in Ubuntu: In Progress Status in linux source package in Cosmic: In Progress Bug description: We've run into some issues where upgrading the kernel from a 4.10 series to a 4.13 series on Ubuntu 16.04 hosts that make heavy use of inotify causes panics and lockups in the kernel in inotify-related code. Our particular use case seemed to hit these at a rate of one every 30 minutes or so when serving up production traffic. Unfortunately, I have been unable to replicate the issue so far with a simulated load-testing environment. When the issue occurs, we get dmesg entries like "BUG: soft lockup - CPU#0 stuck for 22s!" or "General protection fault: [#1] SMP PTI". In the soft lockup case, the host is still up but all I/O operations stall indefinitely (e.g. typing "sync" into the console will hang forever). In the protection fault case, the system reboots. I've attached dmesg output from the two cases to this bugreport. We have noticed the issue with the following kernels: - linux-image-4.13.0-1013-gcp - linux-image-4.13.0-1015-gcp - linux-image-4.13.0-36-generic We did _not_ have the issue with - linux-image-4.10.0-32-generic I've submitted this bug report from a system which should be configured identically to our production hosts that were having issue (the affected hosts were immediately rolled back to 4.10). This bug appears to have been fixed upstream as of 4.17-rc3 in this commit: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=d90a10e2444ba5a351fa695917258ff4c5709fa5 I would guess that perhaps this patch should be backported into both the 4.13 HWE and GCP Ubuntu kernel series? Thanks, KJ ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.13.0-1013-gcp 4.13.0-1013.17 ProcVersionSignature: Ubuntu 4.13.0-1013.17-gcp 4.13.16 Uname: Linux 4.13.0-1013-gcp x86_64 ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 Date: Mon May 14 07:58:29 2018 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-gcp UpgradeStatus: No upgrade log present (probably fresh install) --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 10 07:57 seq crw-rw 1 root audio 116, 33 May 10 07:57 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A DistroRelease: Ubuntu 16.04 IwConfig: Error: [Errno 2] No such file or directory Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Google Google Compute Engine Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-32-generic root=UUID=73ea38ed-7fcd-4871-8afa-17d36f4e4bfc ro scsi_mod.use_blk_mq=Y console=ttyS0 ProcVersionSignature: Ubuntu 4.10.0-32.36~16.04.1-generic 4.10.17 RelatedPackageVersions: linux-restricted-modules-4.10.0-32-generic N/A linux-backports-modules-4.10.0-32-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory Tags: xenial uec-images xenial uec-images Uname: Linux 4.10.0-32-generic x86_64 UnreportableReason: The report belongs to a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: WifiSyslog: _MarkForUpload: False dmi.bios.date: 01/01/2011 dmi.bios.vendor: Google dmi.bios.version: Google dmi.board.asset.tag: 98BEC19B-1DEB-1A9F-1146-C6E4D8577ADB dmi.board.name: Google Compute Engine dmi.board.vendor: Google dmi.chassis.type: 1 dmi.chassis.vendor: Google dmi.modalias: dmi:bvnGoogle:bvrGoogle:bd01/01/2011:svnGoogle:pnGoogleComputeEngine:pvr:rvnGoogle:rnGoogleComputeEngine:rvr:cvnGoogle:ct1:cvr: dmi.product.name: Google Compute Engine dmi.sys.vendor: Google To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug
[Kernel-packages] [Bug 1772991] Re: [Ubuntu 18.04.1] POWER9 - Nvidia Volta - Kernel changes to enable Nvidia driver on bare metal
I built a Bionic test kernel with the 9 commits posted in the bug description. The test kernel can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1772991 Can you test this kernel and see if it resolves this bug? Note about installing test kernels: • If the test kernel is prior to 4.15(Bionic) you need to install the linux-image and linux-image-extra .deb packages. • If the test kernel is 4.15(Bionic) or newer, you need to install the linux-modules, linux-modules-extra and linux-image-unsigned .deb packages. Thanks in advance! ** Changed in: linux (Ubuntu) Status: New => In Progress ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Changed in: linux (Ubuntu) Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) => Joseph Salisbury (jsalisbury) ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => High ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1772991 Title: [Ubuntu 18.04.1] POWER9 - Nvidia Volta - Kernel changes to enable Nvidia driver on bare metal Status in The Ubuntu-power-systems project: New Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: == Comment: #0 - Barry B. Arndt - 2018-05-23 13:40:33 == 12 kernel patches have been identified as needed to support Nvidia Volta on bare metal. All are accepted upstream in 4.17. Three of those are already in bionic, leaving a total of 9 remaining commits needed in bionic. Those 9 commits are: 720c84046c26 powerpc/npu-dma.c: Fix crash after __mmu_notifier_register failure 2b74e2a9b39d powerpc/powernv/npu: Fix deadlock in mmio_invalidate() 5ee573e8ef03 powerpc/powernv/mce: Don't silently restart the machine fb5924fddf9e powerpc/mm: Flush cache on memory hot(un)plug 7fd6641de28f powerpc/powernv/memtrace: Let the arch hotunplug code flush cache 28a5933e8d36 powerpc/powernv/npu: Add lock to prevent race in concurrent context init/destroy a1409adac748 powerpc/powernv/npu: Prevent overwriting of pnv_npu2_init_contex() callback parameters d0cf9b561ca9 powerpc/powernv/npu: Do a PID GPU TLB flush when invalidating a large address range 75ecfb49516c powerpc/mce: Fix a bug where mce loops on memory UE. We cherry-picked the commits, and all applied cleanly. The resultant kernel built successfully and loaded. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1772991/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1772775] Re: 4.4.0-127.153 generates many "sit: non-ECT" messages
** Changed in: linux (Ubuntu) Importance: Medium => High ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Status: New => Confirmed ** Changed in: linux (Ubuntu Xenial) Importance: Undecided => High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1772775 Title: 4.4.0-127.153 generates many "sit: non-ECT" messages Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Confirmed Bug description: Since deploying linux-image-4.4.0-127-generic (4.4.0-127.153) on a Xenial VM with a sit tunnel, I get such messages: May 22 10:49:38 gw kernel: [ 68.121601] sit: non-ECT from 0.0.0.0 with TOS=0x5 Those are logged quite often: # grep -cF 'sit: non-ECT' /var/log/syslog 9108 Reverting to linux-image-4.4.0-124-generic (4.4.0-124.148) fixes the issue. # lsb_release -rd Description: Ubuntu 16.04.4 LTS Release: 16.04 # apt-cache policy linux-image-4.4.0-127-generic linux-image-4.4.0-127-generic: Installed: 4.4.0-127.153 Candidate: 4.4.0-127.153 Version table: *** 4.4.0-127.153 500 500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-127-generic 4.4.0-127.153 ProcVersionSignature: Ubuntu 4.4.0-127.153-generic 4.4.128 Uname: Linux 4.4.0-127-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 22 20:08 seq crw-rw 1 root audio 116, 33 May 22 20:08 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.17 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser' CRDA: N/A Date: Tue May 22 21:18:45 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Error: [Errno 2] No such file or directory: 'lspci' Lsusb: Error: [Errno 2] No such file or directory: 'lsusb' MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-127-generic root=UUID=67f7ee15-64f4-4c85-805c-08386d5fed8b ro console=ttyS0 net.ifnames=0 kaslr vsyscall=none nmi_watchdog=0 possible_cpus=1 pti=on nr_cpus=1 RelatedPackageVersions: linux-restricted-modules-4.4.0-127-generic N/A linux-backports-modules-4.4.0-127-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-2.5 dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.5:cvnQEMU:ct1:cvrpc-i440fx-2.5: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-2.5 dmi.sys.vendor: QEMU --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 22 21:33 seq crw-rw 1 root audio 116, 33 May 22 21:33 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.17 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: [Errno 2] No such file or directory CRDA: N/A DistroRelease: Ubuntu 16.04 IwConfig: Error: [Errno 2] No such file or directory Lspci: Error: [Errno 2] No such file or directory Lsusb: Error: [Errno 2] No such file or directory MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-124-generic root=UUID=67f7ee15-64f4-4c85-805c-08386d5fed8b ro kaslr net.ifnames=0 nmi_watchdog=0 nr_cpus=1 pti=on console=ttyS0 vsyscall=none ProcVersionSignature: Ubuntu 4.4.0-124.148-generic 4.4.117 RelatedPackageVersions: linux-restricted-modules-4.4.0-124-generic N/A linux-backports-modules-4.4.0-124-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory Tags: xenial Uname: Linux 4.4.0-124-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.vendor: Sea
[Kernel-packages] [Bug 1772775] Re: 4.4.0-127.153 generates many "sit: non-ECT" messages
** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Changed in: linux (Ubuntu Xenial) Status: Confirmed => In Progress ** Changed in: linux (Ubuntu Xenial) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1772775 Title: 4.4.0-127.153 generates many "sit: non-ECT" messages Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: In Progress Bug description: Since deploying linux-image-4.4.0-127-generic (4.4.0-127.153) on a Xenial VM with a sit tunnel, I get such messages: May 22 10:49:38 gw kernel: [ 68.121601] sit: non-ECT from 0.0.0.0 with TOS=0x5 Those are logged quite often: # grep -cF 'sit: non-ECT' /var/log/syslog 9108 Reverting to linux-image-4.4.0-124-generic (4.4.0-124.148) fixes the issue. # lsb_release -rd Description: Ubuntu 16.04.4 LTS Release: 16.04 # apt-cache policy linux-image-4.4.0-127-generic linux-image-4.4.0-127-generic: Installed: 4.4.0-127.153 Candidate: 4.4.0-127.153 Version table: *** 4.4.0-127.153 500 500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-127-generic 4.4.0-127.153 ProcVersionSignature: Ubuntu 4.4.0-127.153-generic 4.4.128 Uname: Linux 4.4.0-127-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 22 20:08 seq crw-rw 1 root audio 116, 33 May 22 20:08 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.17 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser' CRDA: N/A Date: Tue May 22 21:18:45 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Error: [Errno 2] No such file or directory: 'lspci' Lsusb: Error: [Errno 2] No such file or directory: 'lsusb' MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-127-generic root=UUID=67f7ee15-64f4-4c85-805c-08386d5fed8b ro console=ttyS0 net.ifnames=0 kaslr vsyscall=none nmi_watchdog=0 possible_cpus=1 pti=on nr_cpus=1 RelatedPackageVersions: linux-restricted-modules-4.4.0-127-generic N/A linux-backports-modules-4.4.0-127-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-2.5 dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.5:cvnQEMU:ct1:cvrpc-i440fx-2.5: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-2.5 dmi.sys.vendor: QEMU --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 22 21:33 seq crw-rw 1 root audio 116, 33 May 22 21:33 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.17 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: [Errno 2] No such file or directory CRDA: N/A DistroRelease: Ubuntu 16.04 IwConfig: Error: [Errno 2] No such file or directory Lspci: Error: [Errno 2] No such file or directory Lsusb: Error: [Errno 2] No such file or directory MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-124-generic root=UUID=67f7ee15-64f4-4c85-805c-08386d5fed8b ro kaslr net.ifnames=0 nmi_watchdog=0 nr_cpus=1 pti=on console=ttyS0 vsyscall=none ProcVersionSignature: Ubuntu 4.4.0-124.148-generic 4.4.117 RelatedPackageVersions: linux-restricted-modules-4.4.0-124-generic N/A linux-backports-modules-4.4.0-124-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory Tags: xenial Uname: Linux 4.4.0-124-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForU
[Kernel-packages] [Bug 1768431] Re: Request to revert SAUCE patches in the 18.04 SRU and update with upstream version
What type or errors are you seeing? Can you post them? You need to install the packages in this order: linux-modules-4.15.0-20-generic_4.15.0-20.22~lp1768431DiffPatched_ppc64el.deb linux-modules-extra-4.15.0-20-generic_4.15.0-20.22~lp1768431DiffPatched_ppc64el.deb linux-image-unsigned-4.15.0-20-generic_4.15.0-20.22~lp1768431DiffPatched_ppc64el.deb -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1768431 Title: Request to revert SAUCE patches in the 18.04 SRU and update with upstream version Status in The Ubuntu-power-systems project: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: == Comment: #0 - UMA KRISHNAN - 2018-04-30 14:41:30 == ---Problem Description--- Request to revert SAUCE patches from 18.04 and apply the patches from next/master. Below set of cxlflash patches were submitted to Canonical after they were sent to the community. Based on review comments, there has been minor changes from that version. This BZ is to request reverting those SAUCE patches with the ones that are queued in next/master tree for 4.18. - SAUCE: cxlflash: Preserve number of interrupts for master contexts - SAUCE: cxlflash: Avoid clobbering context control register value - SAUCE: cxlflash: Add argument identifier names - SAUCE: cxlflash: Introduce OCXL backend - SAUCE: cxlflash: Hardware AFU for OCXL - SAUCE: cxlflash: Read host function configuration - SAUCE: cxlflash: Setup function acTag range - SAUCE: cxlflash: Read host AFU configuration - SAUCE: cxlflash: Setup AFU acTag range - SAUCE: cxlflash: Setup AFU PASID - SAUCE: cxlflash: Adapter context support for OCXL - SAUCE: cxlflash: Use IDR to manage adapter contexts - SAUCE: cxlflash: Support adapter file descriptors for OCXL - SAUCE: cxlflash: Support adapter context discovery - SAUCE: cxlflash: Support image reload policy modification - SAUCE: cxlflash: MMIO map the AFU - SAUCE: cxlflash: Support starting an adapter context - SAUCE: cxlflash: Support process specific mappings - SAUCE: cxlflash: Support AFU state toggling - SAUCE: cxlflash: Support reading adapter VPD data - SAUCE: cxlflash: Setup function OCXL link - SAUCE: cxlflash: Setup OCXL transaction layer - SAUCE: cxlflash: Support process element lifecycle - SAUCE: cxlflash: Support AFU interrupt management - SAUCE: cxlflash: Support AFU interrupt mapping and registration - SAUCE: cxlflash: Support starting user contexts - SAUCE: cxlflash: Support adapter context polling - SAUCE: cxlflash: Support adapter context reading - SAUCE: cxlflash: Support adapter context mmap and release - SAUCE: cxlflash: Support file descriptor mapping - SAUCE: cxlflash: Introduce object handle fop - SAUCE: cxlflash: Setup LISNs for user contexts - SAUCE: cxlflash: Setup LISNs for master contexts - SAUCE: cxlflash: Update synchronous interrupt status bits - SAUCE: cxlflash: Introduce OCXL context state machine - SAUCE: cxlflash: Register for translation errors - SAUCE: cxlflash: Support AFU reset - SAUCE: cxlflash: Enable OCXL operations Also, there are 3 additional patches added to end of this series that we would like to request being pulled into the SRU stream. These 3 patches address bug fixes. The commit ids for the patches queued in next/master tree are, 768999d6b1eadc6a13b1fba1886f1708f433d82b scsi: cxlflash: Preserve number of interrupts for master contexts 6c2b116dd38e3fbda10c3e3d5ac80ea7442e4f4d scsi: cxlflash: Avoid clobbering context control register value fcace1d5e11f518c6f91dd245fa1ac37393b47d3 scsi: cxlflash: Add argument identifier names 863dbdc0552f8bc100df48bb231089c382b89004 scsi: cxlflash: Introduce OCXL backend f2180daa83950ff8183f70b1b78d67cb13fd90b2 scsi: cxlflash: Hardware AFU for OCXL 1042535633554592d7d95a9cf83d2940803689e0 scsi: cxlflash: Read host function configuration ba84823a8b448207659753ae4f9c8b956923bada scsi: cxlflash: Setup function acTag range f55ced2dcd00ab257a2bb25eee619b75cda24817 scsi: cxlflash: Read host AFU configuration c5a8fec11278e245136c7f696c914269c58a6000 scsi: cxlflash: Setup AFU acTag range b42d68d728a63337bcb7860b59e6458946d94a84 scsi: cxlflash: Setup AFU PASID de25ec59a75802584aac97aed05fd94094dbbb58 scsi: cxlflash: Adapter context support for OCXL a76fc993e399f54b37f46107a31e817c779f2b82 scsi: cxlflash: Use IDR to manage adapter contexts 09f35da5fe218baf73f7b4efd281e2c19490512c scsi: cxlflash: Support adapter file descriptors for OCXL 17f9335bc59c1cf8f93617eee137e745abd71a3f scsi: cxlflash: Support adapter context discovery a5cfe355f23d4410d69af0e5b196b095463a0b4b scsi: cxlflash: Support image reload policy modification 0c62e7c091a4e0a01a7c6027fe719625ab2f521e scsi: cxlflash: MMIO map the AFU f39bab766ea4f0b3d5888fdd7d66babd7bef39
[Kernel-packages] [Bug 1772775] Re: 4.4.0-127.153 generates many "sit: non-ECT" messages
Its possible the following commit is the fix:
f4eb17e1efe5 ("Revert "sit: reload iphdr in ipip6_rcv"")
This commit was added to mainline in v4.12-rc5, which could be why this
bug was not seen in Artful or newer.
I built a test kernel with commit f4eb17e1efe5. The test kernel can be
downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1772775
Can you test this kernel and see if it resolves this bug?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1772775
Title:
4.4.0-127.153 generates many "sit: non-ECT" messages
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Xenial:
In Progress
Bug description:
Since deploying linux-image-4.4.0-127-generic (4.4.0-127.153) on a
Xenial VM with a sit tunnel, I get such messages:
May 22 10:49:38 gw kernel: [ 68.121601] sit: non-ECT from 0.0.0.0
with TOS=0x5
Those are logged quite often:
# grep -cF 'sit: non-ECT' /var/log/syslog
9108
Reverting to linux-image-4.4.0-124-generic (4.4.0-124.148) fixes the
issue.
# lsb_release -rd
Description: Ubuntu 16.04.4 LTS
Release: 16.04
# apt-cache policy linux-image-4.4.0-127-generic
linux-image-4.4.0-127-generic:
Installed: 4.4.0-127.153
Candidate: 4.4.0-127.153
Version table:
*** 4.4.0-127.153 500
500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64
Packages
500 http://security.ubuntu.com/ubuntu xenial-security/main amd64
Packages
100 /var/lib/dpkg/status
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-127-generic 4.4.0-127.153
ProcVersionSignature: Ubuntu 4.4.0-127.153-generic 4.4.128
Uname: Linux 4.4.0-127-generic x86_64
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 May 22 20:08 seq
crw-rw 1 root audio 116, 33 May 22 20:08 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.1-0ubuntu2.17
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser'
CRDA: N/A
Date: Tue May 22 21:18:45 2018
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
Lspci: Error: [Errno 2] No such file or directory: 'lspci'
Lsusb: Error: [Errno 2] No such file or directory: 'lsusb'
MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
PciMultimedia:
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-127-generic
root=UUID=67f7ee15-64f4-4c85-805c-08386d5fed8b ro console=ttyS0 net.ifnames=0
kaslr vsyscall=none nmi_watchdog=0 possible_cpus=1 pti=on nr_cpus=1
RelatedPackageVersions:
linux-restricted-modules-4.4.0-127-generic N/A
linux-backports-modules-4.4.0-127-generic N/A
linux-firmware N/A
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/01/2014
dmi.bios.vendor: SeaBIOS
dmi.bios.version: Ubuntu-1.8.2-1ubuntu1
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.version: pc-i440fx-2.5
dmi.modalias:
dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.5:cvnQEMU:ct1:cvrpc-i440fx-2.5:
dmi.product.name: Standard PC (i440FX + PIIX, 1996)
dmi.product.version: pc-i440fx-2.5
dmi.sys.vendor: QEMU
---
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 May 22 21:33 seq
crw-rw 1 root audio 116, 33 May 22 21:33 timer
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.20.1-0ubuntu2.17
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
AudioDevicesInUse: Error: [Errno 2] No such file or directory
CRDA: N/A
DistroRelease: Ubuntu 16.04
IwConfig: Error: [Errno 2] No such file or directory
Lspci: Error: [Errno 2] No such file or directory
Lsusb: Error: [Errno 2] No such file or directory
MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
Package: linux (not installed)
PciMultimedia:
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-124-generic
root=UUID=67f7ee15-64f4-4c85-805c-08386d5fed8b ro kaslr net.ifnames=0
nmi_watchdog=0 nr_cpus=1 pti=on console=ttyS0 vsyscall=none
ProcVersionSignature: Ubuntu 4.4.0-124.148-generic 4.4.117
RelatedPackageVersions:
linux-restricted-modules-4.4.0-124-generic N/A
linux-backports-modules-4.4.0-124-generic N/A
linux-firmware N/A
RfKill: Error: [Errno 2] No such file or directory
Tags: xenial
Uname: Linux 4.4.0-124-generic x86_64
UpgradeStatus: No upgrade log
[Kernel-packages] [Bug 1772775] Re: 4.4.0-127.153 generates many "sit: non-ECT" messages
Thanks for testing. I'll submit an SRU request for this commit. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1772775 Title: 4.4.0-127.153 generates many "sit: non-ECT" messages Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: In Progress Bug description: Since deploying linux-image-4.4.0-127-generic (4.4.0-127.153) on a Xenial VM with a sit tunnel, I get such messages: May 22 10:49:38 gw kernel: [ 68.121601] sit: non-ECT from 0.0.0.0 with TOS=0x5 Those are logged quite often: # grep -cF 'sit: non-ECT' /var/log/syslog 9108 Reverting to linux-image-4.4.0-124-generic (4.4.0-124.148) fixes the issue. # lsb_release -rd Description: Ubuntu 16.04.4 LTS Release: 16.04 # apt-cache policy linux-image-4.4.0-127-generic linux-image-4.4.0-127-generic: Installed: 4.4.0-127.153 Candidate: 4.4.0-127.153 Version table: *** 4.4.0-127.153 500 500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-127-generic 4.4.0-127.153 ProcVersionSignature: Ubuntu 4.4.0-127.153-generic 4.4.128 Uname: Linux 4.4.0-127-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 22 20:08 seq crw-rw 1 root audio 116, 33 May 22 20:08 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.17 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser' CRDA: N/A Date: Tue May 22 21:18:45 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Error: [Errno 2] No such file or directory: 'lspci' Lsusb: Error: [Errno 2] No such file or directory: 'lsusb' MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-127-generic root=UUID=67f7ee15-64f4-4c85-805c-08386d5fed8b ro console=ttyS0 net.ifnames=0 kaslr vsyscall=none nmi_watchdog=0 possible_cpus=1 pti=on nr_cpus=1 RelatedPackageVersions: linux-restricted-modules-4.4.0-127-generic N/A linux-backports-modules-4.4.0-127-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-2.5 dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.5:cvnQEMU:ct1:cvrpc-i440fx-2.5: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-2.5 dmi.sys.vendor: QEMU --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 22 21:33 seq crw-rw 1 root audio 116, 33 May 22 21:33 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.17 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: [Errno 2] No such file or directory CRDA: N/A DistroRelease: Ubuntu 16.04 IwConfig: Error: [Errno 2] No such file or directory Lspci: Error: [Errno 2] No such file or directory Lsusb: Error: [Errno 2] No such file or directory MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-124-generic root=UUID=67f7ee15-64f4-4c85-805c-08386d5fed8b ro kaslr net.ifnames=0 nmi_watchdog=0 nr_cpus=1 pti=on console=ttyS0 vsyscall=none ProcVersionSignature: Ubuntu 4.4.0-124.148-generic 4.4.117 RelatedPackageVersions: linux-restricted-modules-4.4.0-124-generic N/A linux-backports-modules-4.4.0-124-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory Tags: xenial Uname: Linux 4.4.0-124-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-2.5 dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandar
[Kernel-packages] [Bug 1771075] Re: General Protection fault in inotify (fixed upstream)
Thanks for the heads up, Joshua! No need to open a separate bug for linux-gcp. I added that package to this bug. bug 1765564 does not have cosmic or linux-gcp, so we can use this bug for those two. ** Also affects: linux-gcp (Ubuntu) Importance: Undecided Status: New ** No longer affects: linux-gcp (Ubuntu Cosmic) ** Changed in: linux-gcp (Ubuntu) Importance: Undecided => Medium ** Changed in: linux-gcp (Ubuntu) Status: New => In Progress ** Changed in: linux-gcp (Ubuntu) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1771075 Title: General Protection fault in inotify (fixed upstream) Status in linux package in Ubuntu: In Progress Status in linux-gcp package in Ubuntu: In Progress Status in linux source package in Cosmic: In Progress Bug description: We've run into some issues where upgrading the kernel from a 4.10 series to a 4.13 series on Ubuntu 16.04 hosts that make heavy use of inotify causes panics and lockups in the kernel in inotify-related code. Our particular use case seemed to hit these at a rate of one every 30 minutes or so when serving up production traffic. Unfortunately, I have been unable to replicate the issue so far with a simulated load-testing environment. When the issue occurs, we get dmesg entries like "BUG: soft lockup - CPU#0 stuck for 22s!" or "General protection fault: [#1] SMP PTI". In the soft lockup case, the host is still up but all I/O operations stall indefinitely (e.g. typing "sync" into the console will hang forever). In the protection fault case, the system reboots. I've attached dmesg output from the two cases to this bugreport. We have noticed the issue with the following kernels: - linux-image-4.13.0-1013-gcp - linux-image-4.13.0-1015-gcp - linux-image-4.13.0-36-generic We did _not_ have the issue with - linux-image-4.10.0-32-generic I've submitted this bug report from a system which should be configured identically to our production hosts that were having issue (the affected hosts were immediately rolled back to 4.10). This bug appears to have been fixed upstream as of 4.17-rc3 in this commit: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=d90a10e2444ba5a351fa695917258ff4c5709fa5 I would guess that perhaps this patch should be backported into both the 4.13 HWE and GCP Ubuntu kernel series? Thanks, KJ ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.13.0-1013-gcp 4.13.0-1013.17 ProcVersionSignature: Ubuntu 4.13.0-1013.17-gcp 4.13.16 Uname: Linux 4.13.0-1013-gcp x86_64 ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 Date: Mon May 14 07:58:29 2018 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-gcp UpgradeStatus: No upgrade log present (probably fresh install) --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 10 07:57 seq crw-rw 1 root audio 116, 33 May 10 07:57 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A DistroRelease: Ubuntu 16.04 IwConfig: Error: [Errno 2] No such file or directory Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Google Google Compute Engine Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-32-generic root=UUID=73ea38ed-7fcd-4871-8afa-17d36f4e4bfc ro scsi_mod.use_blk_mq=Y console=ttyS0 ProcVersionSignature: Ubuntu 4.10.0-32.36~16.04.1-generic 4.10.17 RelatedPackageVersions: linux-restricted-modules-4.10.0-32-generic N/A linux-backports-modules-4.10.0-32-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory Tags: xenial uec-images xenial uec-images Uname: Linux 4.10.0-32-generic x86_64 UnreportableReason: The report belongs to a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: WifiSyslog: _MarkForUpload: False dmi.bios.date: 01/01/2011 dmi.bios.vendor: Google dmi.bios.version: Google dmi.board.asset.tag: 98BEC19B-1DEB-1A9F-1146-C6E4D8577ADB dmi.board.name: Google Compute Engine dmi.board.vendor: Google
[Kernel-packages] [Bug 1773162] Re: 4.15.0-22-generic fails to boot on IBM S822LC (POWER8 (raw), altivec supported)
** Changed in: linux (Ubuntu) Importance: Undecided => Critical ** Changed in: linux (Ubuntu) Status: Incomplete => In Progress ** Changed in: linux (Ubuntu) Assignee: Canonical Kernel Team (canonical-kernel-team) => Joseph Salisbury (jsalisbury) ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => Critical ** Changed in: linux (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1773162 Title: 4.15.0-22-generic fails to boot on IBM S822LC (POWER8 (raw), altivec supported) Status in The Ubuntu-power-systems project: New Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: Upgrading from 16.04 to 18.04 on a IBM S822LC the system does not boot with 4.15.0-22-generic and is in a reboot cycle. ``` Exiting petitboot. Type 'exit' to return. The system is going down NOW! Sent SIGTERM to all processes Sent SIGKILL to all processes [31775213631,3] OPAL: Trying a CPU re-init with flags: 0x1 [32097001879,3] OPAL: Trying a CPU re-init with flags: 0x2 [2.660186] Bad kernel stack pointer 7fffcd511100 at c000b9ec [2.660382] Oops: Bad kernel stack pointer, sig: 6 [#1] [2.660422] LE SMP NR_CPUS=2048 NUMA PowerNV [2.660462] Modules linked in: [2.660494] CPU: 63 PID: 1201 Comm: modprobe Not tainted 4.15.0-22-generic #24-Ubuntu [2.660549] NIP: c000b9ec LR: CTR: [2.660603] REGS: c0003fd0bd40 TRAP: 0300 Not tainted (4.15.0-22-generic) [2.660657] MSR: 90001031 CR: XER: [2.660713] CFAR: c000b934 DAR: 000200f0 DSISR: 4000 SOFTE: -4611686018408771536 [2.660713] GPR00: 7fffcd511100 [2.660713] GPR04: [2.660713] GPR08: [2.660713] GPR12: 75501b231700 000200f0 [2.660713] GPR16: [2.660713] GPR20: [2.660713] GPR24: [2.660713] GPR28: [2.661203] NIP [c000b9ec] fast_exception_return+0x9c/0x184 [2.661249] LR [] (null) [2.661285] Call Trace: [2.661303] Instruction dump: [2.661331] e84101a0 7c4ff120 e8410170 7c5a03a6 e8010070 e8410080 e8610088 e8810090 [2.661387] e8210078 7db243a6 7db142a6 7c0004ac 63ff 7db242a6 4810 [2.661445] ---[ end trace b607b09fe6490607 ]--- […] ``` Please find the full log attached. Selecting Linux 4.4.0-124-generic works. ``` $ uname -a Linux flughafenberlinbrandenburgwillybrandt 4.4.0-124-generic #148-Ubuntu SMP Wed May 2 13:02:22 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux $ dpkg -l linux-image-4.15.0-22-generic Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==-==-==-= ii linux-image-4.15.0-22-generic 4.15.0-22.24 ppc64elSigned kernel image generic $ more /etc/os-release NAME="Ubuntu" VERSION="18.04 LTS (Bionic Beaver)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 18.04 LTS" VERSION_ID="18.04" HOME_URL="https://www.ubuntu.com/"; SUPPORT_URL="https://help.ubuntu.com/"; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"; VERSION_CODENAME=bionic UBUNTU_CODENAME=bionic ``` --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 23 16:40 seq crw-rw 1 root audio 116, 33 May 23 16:40 timer AplayDevices: Error: [Errno 2] No such file or directory:
[Kernel-packages] [Bug 1773162] Re: 4.15.0-22-generic fails to boot on IBM S822LC (POWER8 (raw), altivec supported)
** 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/1773162 Title: 4.15.0-22-generic fails to boot on IBM S822LC (POWER8 (raw), altivec supported) Status in The Ubuntu-power-systems project: New Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: Upgrading from 16.04 to 18.04 on a IBM S822LC the system does not boot with 4.15.0-22-generic and is in a reboot cycle. ``` Exiting petitboot. Type 'exit' to return. The system is going down NOW! Sent SIGTERM to all processes Sent SIGKILL to all processes [31775213631,3] OPAL: Trying a CPU re-init with flags: 0x1 [32097001879,3] OPAL: Trying a CPU re-init with flags: 0x2 [2.660186] Bad kernel stack pointer 7fffcd511100 at c000b9ec [2.660382] Oops: Bad kernel stack pointer, sig: 6 [#1] [2.660422] LE SMP NR_CPUS=2048 NUMA PowerNV [2.660462] Modules linked in: [2.660494] CPU: 63 PID: 1201 Comm: modprobe Not tainted 4.15.0-22-generic #24-Ubuntu [2.660549] NIP: c000b9ec LR: CTR: [2.660603] REGS: c0003fd0bd40 TRAP: 0300 Not tainted (4.15.0-22-generic) [2.660657] MSR: 90001031 CR: XER: [2.660713] CFAR: c000b934 DAR: 000200f0 DSISR: 4000 SOFTE: -4611686018408771536 [2.660713] GPR00: 7fffcd511100 [2.660713] GPR04: [2.660713] GPR08: [2.660713] GPR12: 75501b231700 000200f0 [2.660713] GPR16: [2.660713] GPR20: [2.660713] GPR24: [2.660713] GPR28: [2.661203] NIP [c000b9ec] fast_exception_return+0x9c/0x184 [2.661249] LR [] (null) [2.661285] Call Trace: [2.661303] Instruction dump: [2.661331] e84101a0 7c4ff120 e8410170 7c5a03a6 e8010070 e8410080 e8610088 e8810090 [2.661387] e8210078 7db243a6 7db142a6 7c0004ac 63ff 7db242a6 4810 [2.661445] ---[ end trace b607b09fe6490607 ]--- […] ``` Please find the full log attached. Selecting Linux 4.4.0-124-generic works. ``` $ uname -a Linux flughafenberlinbrandenburgwillybrandt 4.4.0-124-generic #148-Ubuntu SMP Wed May 2 13:02:22 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux $ dpkg -l linux-image-4.15.0-22-generic Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==-==-==-= ii linux-image-4.15.0-22-generic 4.15.0-22.24 ppc64elSigned kernel image generic $ more /etc/os-release NAME="Ubuntu" VERSION="18.04 LTS (Bionic Beaver)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 18.04 LTS" VERSION_ID="18.04" HOME_URL="https://www.ubuntu.com/"; SUPPORT_URL="https://help.ubuntu.com/"; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"; VERSION_CODENAME=bionic UBUNTU_CODENAME=bionic ``` --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 23 16:40 seq crw-rw 1 root audio 116, 33 May 23 16:40 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7 Architecture: ppc64el 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 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Package: linux (not installed) PciMultimedia: ProcFB: 0 astdrmfb ProcKernelCmdLine: root=UUID=2c3dd738-785a-469b-843e-9f0ba8b47b0d ro rootflags=subvol=@ quiet splash ProcLoadAvg: 0.01 0.08 0.04 2/1373 28071 ProcSwaps: Filename TypeSizeUsed
[Kernel-packages] [Bug 1773162] Re: 4.15.0-22-generic fails to boot on IBM S822LC (POWER8 (raw), altivec supported)
I built a test kernel with a revert of 06f7e3d39 and a new backport of a048a07d7f4. The test kernel can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1773162 Can you test this kernel and see if it resolves this bug? Note about installing test kernels: • If the test kernel is prior to 4.15(Bionic) you need to install the linux-image and linux-image-extra .deb packages. • If the test kernel is 4.15(Bionic) or newer, you need to install the linux-modules, linux-modules-extra and linux-image-unsigned .deb packages. Thanks in advance! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1773162 Title: 4.15.0-22-generic fails to boot on IBM S822LC (POWER8 (raw), altivec supported) Status in The Ubuntu-power-systems project: New Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: Upgrading from 16.04 to 18.04 on a IBM S822LC the system does not boot with 4.15.0-22-generic and is in a reboot cycle. ``` Exiting petitboot. Type 'exit' to return. The system is going down NOW! Sent SIGTERM to all processes Sent SIGKILL to all processes [31775213631,3] OPAL: Trying a CPU re-init with flags: 0x1 [32097001879,3] OPAL: Trying a CPU re-init with flags: 0x2 [2.660186] Bad kernel stack pointer 7fffcd511100 at c000b9ec [2.660382] Oops: Bad kernel stack pointer, sig: 6 [#1] [2.660422] LE SMP NR_CPUS=2048 NUMA PowerNV [2.660462] Modules linked in: [2.660494] CPU: 63 PID: 1201 Comm: modprobe Not tainted 4.15.0-22-generic #24-Ubuntu [2.660549] NIP: c000b9ec LR: CTR: [2.660603] REGS: c0003fd0bd40 TRAP: 0300 Not tainted (4.15.0-22-generic) [2.660657] MSR: 90001031 CR: XER: [2.660713] CFAR: c000b934 DAR: 000200f0 DSISR: 4000 SOFTE: -4611686018408771536 [2.660713] GPR00: 7fffcd511100 [2.660713] GPR04: [2.660713] GPR08: [2.660713] GPR12: 75501b231700 000200f0 [2.660713] GPR16: [2.660713] GPR20: [2.660713] GPR24: [2.660713] GPR28: [2.661203] NIP [c000b9ec] fast_exception_return+0x9c/0x184 [2.661249] LR [] (null) [2.661285] Call Trace: [2.661303] Instruction dump: [2.661331] e84101a0 7c4ff120 e8410170 7c5a03a6 e8010070 e8410080 e8610088 e8810090 [2.661387] e8210078 7db243a6 7db142a6 7c0004ac 63ff 7db242a6 4810 [2.661445] ---[ end trace b607b09fe6490607 ]--- […] ``` Please find the full log attached. Selecting Linux 4.4.0-124-generic works. ``` $ uname -a Linux flughafenberlinbrandenburgwillybrandt 4.4.0-124-generic #148-Ubuntu SMP Wed May 2 13:02:22 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux $ dpkg -l linux-image-4.15.0-22-generic Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==-==-==-= ii linux-image-4.15.0-22-generic 4.15.0-22.24 ppc64elSigned kernel image generic $ more /etc/os-release NAME="Ubuntu" VERSION="18.04 LTS (Bionic Beaver)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 18.04 LTS" VERSION_ID="18.04" HOME_URL="https://www.ubuntu.com/"; SUPPORT_URL="https://help.ubuntu.com/"; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"; VERSION_CODENAME=bionic UBUNTU_CODENAME=bionic ``` --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 23 16:40 seq crw-rw 1 root audio 116, 33 May 23 16:40 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7 Architecture: ppc64el ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'a
[Kernel-packages] [Bug 1772991] Re: [Ubuntu 18.04.1] POWER9 - Nvidia Volta - Kernel changes to enable Nvidia driver on bare metal
Thanks for testing. SRU request submitted: https://lists.ubuntu.com/archives/kernel-team/2018-May/092729.html ** Description changed: + == SRU Justification == + 12 kernel patches have been identified as needed to support Nvidia Volta + on bare metal. All are accepted upstream in 4.17. Three of those are + already in bionic, leaving a total of 9 remaining commits needed in bionic. + This pull request is for those other 9 commits. + + == Regression Potential == + All of the commits are specific to powerpc. + + == Test Case == + A test kernel was built with these patches and tested by IBM. + + == Comment: #0 - Barry B. Arndt - 2018-05-23 13:40:33 == 12 kernel patches have been identified as needed to support Nvidia Volta on bare metal. All are accepted upstream in 4.17. Three of those are already in bionic, leaving a total of 9 remaining commits needed in bionic. Those 9 commits are: 720c84046c26 powerpc/npu-dma.c: Fix crash after __mmu_notifier_register failure 2b74e2a9b39d powerpc/powernv/npu: Fix deadlock in mmio_invalidate() 5ee573e8ef03 powerpc/powernv/mce: Don't silently restart the machine fb5924fddf9e powerpc/mm: Flush cache on memory hot(un)plug 7fd6641de28f powerpc/powernv/memtrace: Let the arch hotunplug code flush cache 28a5933e8d36 powerpc/powernv/npu: Add lock to prevent race in concurrent context init/destroy a1409adac748 powerpc/powernv/npu: Prevent overwriting of pnv_npu2_init_contex() callback parameters d0cf9b561ca9 powerpc/powernv/npu: Do a PID GPU TLB flush when invalidating a large address range 75ecfb49516c powerpc/mce: Fix a bug where mce loops on memory UE. We cherry-picked the commits, and all applied cleanly. The resultant kernel built successfully and loaded. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1772991 Title: [Ubuntu 18.04.1] POWER9 - Nvidia Volta - Kernel changes to enable Nvidia driver on bare metal Status in The Ubuntu-power-systems project: New Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: == SRU Justification == 12 kernel patches have been identified as needed to support Nvidia Volta on bare metal. All are accepted upstream in 4.17. Three of those are already in bionic, leaving a total of 9 remaining commits needed in bionic. This pull request is for those other 9 commits. == Regression Potential == All of the commits are specific to powerpc. == Test Case == A test kernel was built with these patches and tested by IBM. == Comment: #0 - Barry B. Arndt - 2018-05-23 13:40:33 == 12 kernel patches have been identified as needed to support Nvidia Volta on bare metal. All are accepted upstream in 4.17. Three of those are already in bionic, leaving a total of 9 remaining commits needed in bionic. Those 9 commits are: 720c84046c26 powerpc/npu-dma.c: Fix crash after __mmu_notifier_register failure 2b74e2a9b39d powerpc/powernv/npu: Fix deadlock in mmio_invalidate() 5ee573e8ef03 powerpc/powernv/mce: Don't silently restart the machine fb5924fddf9e powerpc/mm: Flush cache on memory hot(un)plug 7fd6641de28f powerpc/powernv/memtrace: Let the arch hotunplug code flush cache 28a5933e8d36 powerpc/powernv/npu: Add lock to prevent race in concurrent context init/destroy a1409adac748 powerpc/powernv/npu: Prevent overwriting of pnv_npu2_init_contex() callback parameters d0cf9b561ca9 powerpc/powernv/npu: Do a PID GPU TLB flush when invalidating a large address range 75ecfb49516c powerpc/mce: Fix a bug where mce loops on memory UE. We cherry-picked the commits, and all applied cleanly. The resultant kernel built successfully and loaded. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1772991/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1770003] Re: qla2xxx: Fix page fault at kmem_cache_alloc_node()
That is the correct version, 4.15.0-23.25. Here are the fixes in the
changelog:
* qla2xxx: Fix page fault at kmem_cache_alloc_node() (LP: #1770003)
- scsi: qla2xxx: Fix session cleanup for N2N
- scsi: qla2xxx: Remove unused argument from
qlt_schedule_sess_for_deletion()
- scsi: qla2xxx: Serialize session deletion by using work_lock
- scsi: qla2xxx: Serialize session free in qlt_free_session_done
- scsi: qla2xxx: Don't call dma_free_coherent with IRQ disabled.
- scsi: qla2xxx: Fix warning in qla2x00_async_iocb_timeout()
- scsi: qla2xxx: Prevent relogin trigger from sending too many commands
- scsi: qla2xxx: Fix double free bug after firmware timeout
- scsi: qla2xxx: Fixup locking for session deletion
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1770003
Title:
qla2xxx: Fix page fault at kmem_cache_alloc_node()
Status in The Ubuntu-power-systems project:
In Progress
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Bionic:
Fix Committed
Bug description:
== SRU Justification ==
IBM is requesting these nine patches to be SRU'd to Bionic. IBM found
that the current Bionic kernel contains a problem related to qla2xxx
driver which causes the following:
[ 66.295233] Unable to handle kernel paging request for data at address
0x8882f6ed90e9151a
[ 66.295297] Faulting instruction address: 0xc038a110
cpu 0x50: Vector: 380 (Data Access Out of Range) at [c692f650]
pc: c038a110: kmem_cache_alloc_node+0x2f0/0x350
lr: c038a0fc: kmem_cache_alloc_node+0x2dc/0x350
sp: c692f8d0
msr: 90009033
dar: 8882f6ed90e9151a
current = 0xc698fd00
paca= 0xcfab7000 softe: 0irq_happened: 0x01
pid = 1762, comm = systemd-journal
Linux version 4.15.0-20-generic (buildd@bos02-ppc64el-002) (gcc version 7.3.0
(Ubuntu 7.3.0-14ubuntu1)) #16-Ubuntu SMP Wed Apr 4 13:57:51 UTC 2018 (Ubuntu
4.15.0-20.21-generic 4.15.20)
enter ? for help
[c692f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350
(unreliable)
[c692f940] c0b2ec6c __alloc_skb+0x6c/0x220
[c692f9a0] c0b30b6c alloc_skb_with_frags+0x7c/0x2e0
[c692fa30] c0b247cc sock_alloc_send_pskb+0x29c/0x2c0
[c692fae0] c0c5705c unix_dgram_sendmsg+0x15c/0x8f0
[c692fbc0] c0b1ec64 sock_sendmsg+0x64/0x90
[c692fbf0] c0b20abc ___sys_sendmsg+0x31c/0x390
[c692fd90] c0b221ec __sys_sendmsg+0x5c/0xc0
[c692fe30] c000b184 system_call+0x58/0x6c
--- Exception: c00 (System Call) at 74826f6fa9c4
SP (75dc5510) is in userspace
We were able to get rid of this problem cherry picking some of the
upstream patches. Do you think they might fit in the SRU criteria?
The commit ids are below and they were easily cherry picked.
eaf75d1815dad230dac2f1e8f1dc0349b2d50071: scsi: qla2xxx: Fix double free bug
after firmware timeout
6d67492764b39ad6efb6822816ad73dc141752f4: scsi: qla2xxx: Prevent relogin
trigger from sending too many commands
7ac0c332f96bb9688560726f5e80c097ed8de59a: scsi: qla2xxx: Fix warning in
qla2x00_async_iocb_timeout()
045d6ea200af794ba15515984cff63787a7fc3c0: scsi: qla2xxx: Don't call
dma_free_coherent with IRQ disabled.
1ae634eb28533b82f9777a47c1ade44cb8c0182b: scsi: qla2xxx: Serialize session
free in qlt_free_session_done
d8630bb95f46ea118dede63bd75533faa64f9612: scsi: qla2xxx: Serialize session
deletion by using work_lock
Requries: 1c6cacf4ea6c04a58a0e3057f5ed60c24a4ffeff ('scsi: qla2xxx:
Fixup locking for session deletion')
94cff6e114df56d0df74cdabe3481df38d9b0c1e: scsi: qla2xxx: Remove unused
argument from qlt_schedule_sess_for_dele?
9cd883f07a54e5301d51e259acd250bb035996be: scsi: qla2xxx: Fix session cleanup
for N2N
== Regression Potential ==
Medium. There are nine patches in this pull request. They are not specific
to a
paticular arch, but they are specific to qla2xxx.
== Test Case ==
A test kernel was built with these patches and tested by IBM.
IBM states the test kernel resolved the bug.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1770003/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1773232] Re: Not booting at all times
Did this issue start happening after an update/upgrade? Was there a kernel version where you were not having this particular problem? This will help determine if the problem you are seeing is the result of a regression, and when this regression was introduced. If this is a regression, we can perform a kernel bisect to identify the commit that introduced the problem. ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Status: New => Incomplete ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => High ** Tags added: kernel-da-key -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1773232 Title: Not booting at all times Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Bug description: I'm running Linux kernel 4.17rc5. (this problem is also with the 4.16 kernel and 4.15). My computer randomly freezes up after a hour of less and sometimes it works for more then a day. But when I check the kern.log or syslog it does not show any messages at the time of crashing. So is there a way that I can find you why it crashes? Also, after a crash it sometimes refuses to boot at all. It will give me a black screen. After restarting for 20 or more times it boots up. Sometimes my password doesn't work while booting even though I use the same (correct) password after the restart. I have made a video on this issue here: https://www.youtube.com/watch?v=gqH8ySXOUmk&feature=youtu.be (the video is a bit out of focus, forgot the manual focus. I have speeded up someparts to make it more pleasant to watch) I'd like to include some logs but Can't find any relevant logs since it does not log during the period of the error. I Have attached a picture of my screen that it will sometimes show. The moment it did boot up I was using kernel 4.15 (but with that version not all of my screens work) After the reboot I used the kernel 4.17r5 again and it did work. This happens to me a lot and it can take a lot of restarting in order to boot. In the video it didnt show the problem that my password would not be recognised. However this sometimes happens too. One more bug I'm having is that my thrird screen is not being recognised to it sets a lower screen resolution. I have solved this with forcing the screen resolution to 1080x1920 but then the menu bar is not shown correctly. and I have to drag the screen to the right place in the settings in order to have the menu's correctly. (video: https://youtu.be/Tq-TEeAAIGA) this is what I have to do at startup Is there anything more I can do to make this bug report more specific? --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-05-06 (17 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Package: linux (not installed) Tags: bionic Uname: Linux 4.17.0-041700rc5-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-05-06 (17 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Package: linux (not installed) Tags: bionic Uname: Linux 4.17.0-041700rc5-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1773232/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1773232] Re: Not booting at all times
Also, would it be possible for you to test some prior kernels to see if there was a previous good version? If there is a prior good kernel, we can perform a kernel bisect to identify the commit that introduced this bug. Prior upstream kernels can be found at: http://kernel.ubuntu.com/~kernel-ppa/mainline/ I would suggesting starting with 4.14, then maybe 4.13, 4.12, etc. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1773232 Title: Not booting at all times Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Bug description: I'm running Linux kernel 4.17rc5. (this problem is also with the 4.16 kernel and 4.15). My computer randomly freezes up after a hour of less and sometimes it works for more then a day. But when I check the kern.log or syslog it does not show any messages at the time of crashing. So is there a way that I can find you why it crashes? Also, after a crash it sometimes refuses to boot at all. It will give me a black screen. After restarting for 20 or more times it boots up. Sometimes my password doesn't work while booting even though I use the same (correct) password after the restart. I have made a video on this issue here: https://www.youtube.com/watch?v=gqH8ySXOUmk&feature=youtu.be (the video is a bit out of focus, forgot the manual focus. I have speeded up someparts to make it more pleasant to watch) I'd like to include some logs but Can't find any relevant logs since it does not log during the period of the error. I Have attached a picture of my screen that it will sometimes show. The moment it did boot up I was using kernel 4.15 (but with that version not all of my screens work) After the reboot I used the kernel 4.17r5 again and it did work. This happens to me a lot and it can take a lot of restarting in order to boot. In the video it didnt show the problem that my password would not be recognised. However this sometimes happens too. One more bug I'm having is that my thrird screen is not being recognised to it sets a lower screen resolution. I have solved this with forcing the screen resolution to 1080x1920 but then the menu bar is not shown correctly. and I have to drag the screen to the right place in the settings in order to have the menu's correctly. (video: https://youtu.be/Tq-TEeAAIGA) this is what I have to do at startup Is there anything more I can do to make this bug report more specific? --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-05-06 (17 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Package: linux (not installed) Tags: bionic Uname: Linux 4.17.0-041700rc5-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-05-06 (17 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Package: linux (not installed) Tags: bionic Uname: Linux 4.17.0-041700rc5-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1773232/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1773184] Re: Starting a KVM guest in a guest (nested VM) crash the kernel
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.17 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.17-rc6 ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Tags added: kernel-da-key -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1773184 Title: Starting a KVM guest in a guest (nested VM) crash the kernel Status in linux package in Ubuntu: Incomplete Bug description: linux-image-4.15.0.22 (20, and probably earlier, too) panics when starting a guest VM in a nested manner. compute1 login: [ 4847.733004] general protection fault: [#1] SMP PTI [ 4847.736595] Modules linked in: vxlan ip6_udp_tunnel udp_tunnel ebt_arp ebt_among ip6table_raw nf_conntrack_ipv6 nf_defrag_ipv6 xt_CT xt_mac xt_comment xt_physdev xt_set ip_set_hash_net ip_set nfnetlink vhost_net vhost tap xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp kvm_intel ip6table_filter ip6_tables iptable_filter ebtable_filter ebtable_nat ebtables iptable_raw br_netfilter bridge stp llc nls_iso8859_1 kvm irqbypass joydev input_leds serio_raw sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor [ 4847.756237] async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear hid_generic usbhid hid crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc aesni_intel aes_x86_64 crypto_simd glue_helper cryptd psmouse virtio_blk virtio_net floppy [last unloaded: kvm_intel] [ 4847.762893] CPU: 1 PID: 13789 Comm: CPU 0/KVM Not tainted 4.15.0-22-generic #24-Ubuntu [ 4847.765154] Hardware name: OpenStack Foundation OpenStack Nova, BIOS 1.10.2-1ubuntu1~cloud0 04/01/2014 [ 4847.767764] RIP: 0010:native_write_cr4+0x4/0x10 [ 4847.769085] RSP: 0018:9daf4119bb70 EFLAGS: 00010006 [ 4847.770629] RAX: 000626e0 RBX: 0046 RCX: 8edcbfc8 [ 4847.772771] RDX: 8edcbfc94020 RSI: 8edcbfca5040 RDI: 000606e0 [ 4847.774965] RBP: 9daf4119bb70 R08: fff8 R09: 000d [ 4847.777175] R10: c078c76e2000 R11: 0cd0 R12: 00025040 [ 4847.779213] R13: R14: 8edc438409a0 R15: 8edc43855278 [ 4847.781230] FS: 7f9a09a02700() GS:8edcbfc8() knlGS: [ 4847.783548] CS: 0010 DS: ES: CR0: 80050033 [ 4847.785233] CR2: 7f99fb80cd50 CR3: 000152e0a002 CR4: 000626e0 [ 4847.787225] Call Trace: [ 4847.788062] hardware_disable+0xaa/0xc0 [kvm_intel] [ 4847.789460] ? vcpu_stat_get_per_vm_open+0x20/0x20 [kvm] [ 4847.791025] kvm_arch_hardware_disable+0x19/0x40 [kvm] [ 4847.792664] hardware_disable_nolock+0x2b/0x30 [kvm] [ 4847.794260] on_each_cpu+0x46/0x60 [ 4847.795302] hardware_disable_all_nolock+0x35/0x40 [kvm] [ 4847.796896] hardware_disable_all+0x1a/0x30 [kvm] [ 4847.798267] kvm_put_kvm+0x1f8/0x260 [kvm] [ 4847.799470] kvm_vm_release+0x21/0x30 [kvm] [ 4847.800758] __fput+0xea/0x220 [ 4847.801681] fput+0xe/0x10 [ 4847.802602] task_work_run+0x9d/0xc0 [ 4847.803692] do_exit+0x2ec/0xb40 [ 4847.804676] do_group_exit+0x43/0xb0 [ 4847.805719] get_signal+0x27b/0x590 [ 4847.806742] do_signal+0x37/0x730 [ 4847.807774] ? do_futex+0x325/0x500 [ 4847.808803] ? SyS_futex+0x13b/0x180 [ 4847.809852] ? restore_altstack+0x51/0x70 [ 4847.811017] exit_to_usermode_loop+0x73/0xd0 [ 4847.812299] do_syscall_64+0x115/0x130 [ 4847.813401] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 [ 4847.814808] RIP: 0033:0x7f9a142bc10d [ 4847.815914] RSP: 002b:7f9a09a01798 EFLAGS: 0246 ORIG_RAX: 00ca [ 4847.818100] RAX: fe00 RBX: 5583a8961060 RCX: 7f9a142bc10d [ 4847.820065] RDX: 0002 RSI: 0080 RDI: 5583a6925e00 [ 4847.822029] RBP: 5583a8961084 R08: 5583a6925e00 R09: [ 4847.824002] R10: R11: 0246 R12: 5583a896108c [ 4847.825949] R13: R14: 5583a6925e00 R15: 000f [ 4847.827922] Code: 0f 1f 80 00 00 00 00 55 48 89 e5 0f 20 d8 5d c3 0f 1f 80 00 00 00 00 55 48 89 e5 0f 22 df 5d c3 0f 1f 80 00 00 00 00 55 48 89 e5 <0f> 22 e7 5d c3 0
[Kernel-packages] [Bug 1773137] Re: USB2 keep resetting. kernel: usb 2-1: USB disconnect
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.17 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.17-rc6 ** 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/1773137 Title: USB2 keep resetting. kernel: usb 2-1: USB disconnect Status in linux package in Ubuntu: Incomplete Status in linux-signed package in Ubuntu: New Bug description: Hello, I have found a bug. This bug is related to USB2, I have DVD RW external that using USB2 port. I using the kernel 4.15.0-22. I also attached the error log from dmesg. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-22-generic 4.15.0-22.24 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: KDE Date: Thu May 24 17:26:01 2018 InstallationDate: Installed on 2018-04-14 (40 days ago) InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: linux-signed UpgradeStatus: Upgraded to bionic on 2018-04-27 (26 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1773137/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1773100] Re: Bionic Server ISO soft lockup on Dell C6420 in swapper - Xenial appears OK
Can you see if this issue also happens with the latest daily image? It can be downloaded from: Desktop: http://cdimage.ubuntu.com/daily-live/current/ Server: http://cdimage.ubuntu.com/ubuntu-server/daily/current/ ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => High ** Changed in: linux (Ubuntu Bionic) Status: New => Confirmed ** Tags added: kernel-da-key -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1773100 Title: Bionic Server ISO soft lockup on Dell C6420 in swapper - Xenial appears OK Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Bug description: Hello! We are experiencing a soft lockup when booting the Bionic Server installer amd64 ISO (kernel 4.15.0-20). The installer seems to hang on boot: After GRUB, nothing ever appears on the display, and we only managed to get kernel logs through Serial-Over-LAN. The 16.04.4 Server installer ISO (kernel 4.4.0-16) does not seem to have this problem. Our hardware is a Dell C6420. The C6420 is one node in a four-node, 2 U chassis (the C6400 chassis). The node's hardware is two Intel Xeon Gold 6134 CPUs (8 cores @ 3.2 GHz/core). RAM is 96 GB, as twelve 8 GB DIMMs. We have tested with Hyperthreading on and off, and with UFEI and BIOS boot modes, and we get the same results in both cases. Right now, we have Hyperthreading on, and we are booting in UEFI mode. If you need us to change that for testing, let us know! Here are the first 25 lines of the soft lockup: [ 40.544002] watchdog: BUG: soft lockup - CPU#24 stuck for 22s! [swapper/0:1] [ 40.628002] Modules linked in: [ 40.664000] CPU: 24 PID: 1 Comm: swapper/0 Not tainted 4.15.0-20-generic #21-Ubuntu [ 40.756002] Hardware name: Dell Inc. PowerEdge C6420/0K2TT6, BIOS 1.3.7 02/09/2018 [ 40.844002] RIP: 0010:smp_call_function_many+0x229/0x250 [ 40.908002] RSP: :aa61000eb868 EFLAGS: 0202 ORIG_RAX: ff11 [ 41.00] RAX: 0004 RBX: 8eba9f5238c0 RCX: 0001 [ 41.084002] RDX: 8eba9f2a8f60 RSI: RDI: 8eba96754de0 [ 41.168002] RBP: aa61000eb8a0 R08: fff0 R09: feff [ 41.252003] R10: ecb61f56b380 R11: 0004 R12: 0100 [ 41.340002] R13: 00023880 R14: b4035030 R15: [ 41.424002] FS: () GS:8eba9f50() knlGS: [ 41.520002] CS: 0010 DS: ES: CR0: 80050033 [ 41.588002] CR2: CR3: 00018c00a001 CR4: 007606e0 [ 41.676002] DR0: DR1: DR2: [ 41.760004] DR3: DR6: fffe0ff0 DR7: 0400 [ 41.844002] PKRU: [ 41.876002] Call Trace: [ 41.908002] ? nsio_rw_bytes+0xd9/0x250 [ 41.952002] ? cpumask_weight+0x20/0x20 [ 42.02] ? nsio_rw_bytes+0xda/0x250 [ 42.044003] ? quirk_intel_brickland_xeon_ras_cap+0x60/0x60 [ 42.112002] on_each_cpu+0x2d/0x60 [ 42.152000] ? nsio_rw_bytes+0xd9/0x250 [ 42.196003] text_poke_bp+0x6a/0xf0 The full output is attached as "kernel 4.15.0-20 boot.txt". We used the following kernel command line: BOOT_IMAGE=/install/vmlinuz file=/cdrom/preseed/ubuntu-server.seed console=tty0 console=ttyS0 console=ttyS1 debug --- As I mentioned up top, we have started installing the Ubuntu Server 16.04.4 Server ISO, and this far the kernel is booting, and we have gotten through to the text-based installer. I'm sorry that I couldn't use the normal kernel bug-reporting process, but since we're hitting this problem in the installer, I'm not sure what else we can do. I also apologize that I don't have any more info, since it's after Midnight local time, but I wanted to make sure I got this information through to you ASAP. At this point, we're probably going to move forward with the 16.04.4 Server installer for now, but we do have an identical C6420 node (in a different chassis), and we will probably be able to use that for testing for at least a little while! For example, we were thinking of trying the 16.04 HWE kernel, as an additional data point. So, please let us know what additional information you would like, and what else we can try. Thanks very much! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1773100/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https
[Kernel-packages] [Bug 1773024] Re: Errors at boot
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.17 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.17-rc6 ** Package changed: linux-signed (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1773024 Title: Errors at boot Status in linux package in Ubuntu: Incomplete Bug description: LOGS DMESG: [0.048089] ACPI: Added _OSI(Module Device) [0.048090] ACPI: Added _OSI(Processor Device) [0.048091] ACPI: Added _OSI(3.0 _SCP Extensions) [0.048091] ACPI: Added _OSI(Processor Aggregator Device) [0.049587] ACPI Exception: Could not find/resolve named package element: LNKC (20170831/dspkginit-381) [0.049598] ACPI Exception: Could not find/resolve named package element: LNKD (20170831/dspkginit-381) [0.049607] ACPI Exception: Could not find/resolve named package element: LNKA (20170831/dspkginit-381) [0.049615] ACPI Exception: Could not find/resolve named package element: LNKB (20170831/dspkginit-381) [0.049676] ACPI Exception: Could not find/resolve named package element: LNKD (20170831/dspkginit-381) [0.049684] ACPI Exception: Could not find/resolve named package element: LNKA (20170831/dspkginit-381) [0.049692] ACPI Exception: Could not find/resolve named package element: LNKB (20170831/dspkginit-381) [0.049700] ACPI Exception: Could not find/resolve named package element: LNKC (20170831/dspkginit-381) [0.049760] ACPI Exception: Could not find/resolve named package element: LNKA (20170831/dspkginit-381) [0.049768] ACPI Exception: Could not find/resolve named package element: LNKB (20170831/dspkginit-381) [0.049776] ACPI Exception: Could not find/resolve named package element: LNKC (20170831/dspkginit-381) [0.049783] ACPI Exception: Could not find/resolve named package element: LNKD (20170831/dspkginit-381) [0.049843] ACPI Exception: Could not find/resolve named package element: LNKB (20170831/dspkginit-381) [0.049851] ACPI Exception: Could not find/resolve named package element: LNKC (20170831/dspkginit-381) [0.049859] ACPI Exception: Could not find/resolve named package element: LNKD (20170831/dspkginit-381) [0.049867] ACPI Exception: Could not find/resolve named package element: LNKA (20170831/dspkginit-381) [0.049925] ACPI Exception: Could not find/resolve named package element: LNKC (20170831/dspkginit-381) [0.049933] ACPI Exception: Could not find/resolve named package element: LNKD (20170831/dspkginit-381) [0.049941] ACPI Exception: Could not find/resolve named package element: LNKA (20170831/dspkginit-381) [0.049948] ACPI Exception: Could not find/resolve named package element: LNKB (20170831/dspkginit-381) [0.050008] ACPI Exception: Could not find/resolve named package element: LNKD (20170831/dspkginit-381) [0.050016] ACPI Exception: Could not find/resolve named package element: LNKA (20170831/dspkginit-381) [0.050024] ACPI Exception: Could not find/resolve named package element: LNKB (20170831/dspkginit-381) [0.050032] ACPI Exception: Could not find/resolve named package element: LNKC (20170831/dspkginit-381) [0.050091] ACPI Exception: Could not find/resolve named package element: LNKB (20170831/dspkginit-381) [0.050099] ACPI Exception: Could not find/resolve named package element: LNKC (20170831/dspkginit-381) [0.050107] ACPI Exception: Could not find/resolve named package element: LNKD (20170831/dspkginit-381) [0.050115] ACPI Exception: Could not find/resolve named package element: LNKA (20170831/dspkginit-381) [0.050173] ACPI Exception: Could not find/resolve named package element: LNKC (20170831/dspkginit-381) [0.050181] ACPI Exception: Could not find/resolve named package element: LNKD (20170831/dspkginit-381) [0.050190] ACPI Exception: Could not find/resolve named package element: LNKA (20170831/dspkginit-381) [0.050198] ACPI Exception: Could not find/resolve named package element: LNKB (20170831/dspkginit-381) [0.050258] ACPI Exception: Could not find/resolve named package element: LNKD (20170831/dspkginit-381) [0.050267]
[Kernel-packages] [Bug 1773184] Re: Starting a KVM guest in a guest (nested VM) crash the kernel
Did this issue start happening after an update/upgrade? Was there a kernel version where you were not having this particular problem? This will help determine if the problem you are seeing is the result of a regression, and when this regression was introduced. If this is a regression, we can perform a kernel bisect to identify the commit that introduced the problem. ** Changed in: linux (Ubuntu) Status: Confirmed => Triaged ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Status: New => Triaged ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1773184 Title: Starting a KVM guest in a guest (nested VM) crash the kernel Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Bug description: linux-image-4.15.0.22 (20, and probably earlier, too) panics when starting a guest VM in a nested manner. compute1 login: [ 4847.733004] general protection fault: [#1] SMP PTI [ 4847.736595] Modules linked in: vxlan ip6_udp_tunnel udp_tunnel ebt_arp ebt_among ip6table_raw nf_conntrack_ipv6 nf_defrag_ipv6 xt_CT xt_mac xt_comment xt_physdev xt_set ip_set_hash_net ip_set nfnetlink vhost_net vhost tap xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp kvm_intel ip6table_filter ip6_tables iptable_filter ebtable_filter ebtable_nat ebtables iptable_raw br_netfilter bridge stp llc nls_iso8859_1 kvm irqbypass joydev input_leds serio_raw sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor [ 4847.756237] async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear hid_generic usbhid hid crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc aesni_intel aes_x86_64 crypto_simd glue_helper cryptd psmouse virtio_blk virtio_net floppy [last unloaded: kvm_intel] [ 4847.762893] CPU: 1 PID: 13789 Comm: CPU 0/KVM Not tainted 4.15.0-22-generic #24-Ubuntu [ 4847.765154] Hardware name: OpenStack Foundation OpenStack Nova, BIOS 1.10.2-1ubuntu1~cloud0 04/01/2014 [ 4847.767764] RIP: 0010:native_write_cr4+0x4/0x10 [ 4847.769085] RSP: 0018:9daf4119bb70 EFLAGS: 00010006 [ 4847.770629] RAX: 000626e0 RBX: 0046 RCX: 8edcbfc8 [ 4847.772771] RDX: 8edcbfc94020 RSI: 8edcbfca5040 RDI: 000606e0 [ 4847.774965] RBP: 9daf4119bb70 R08: fff8 R09: 000d [ 4847.777175] R10: c078c76e2000 R11: 0cd0 R12: 00025040 [ 4847.779213] R13: R14: 8edc438409a0 R15: 8edc43855278 [ 4847.781230] FS: 7f9a09a02700() GS:8edcbfc8() knlGS: [ 4847.783548] CS: 0010 DS: ES: CR0: 80050033 [ 4847.785233] CR2: 7f99fb80cd50 CR3: 000152e0a002 CR4: 000626e0 [ 4847.787225] Call Trace: [ 4847.788062] hardware_disable+0xaa/0xc0 [kvm_intel] [ 4847.789460] ? vcpu_stat_get_per_vm_open+0x20/0x20 [kvm] [ 4847.791025] kvm_arch_hardware_disable+0x19/0x40 [kvm] [ 4847.792664] hardware_disable_nolock+0x2b/0x30 [kvm] [ 4847.794260] on_each_cpu+0x46/0x60 [ 4847.795302] hardware_disable_all_nolock+0x35/0x40 [kvm] [ 4847.796896] hardware_disable_all+0x1a/0x30 [kvm] [ 4847.798267] kvm_put_kvm+0x1f8/0x260 [kvm] [ 4847.799470] kvm_vm_release+0x21/0x30 [kvm] [ 4847.800758] __fput+0xea/0x220 [ 4847.801681] fput+0xe/0x10 [ 4847.802602] task_work_run+0x9d/0xc0 [ 4847.803692] do_exit+0x2ec/0xb40 [ 4847.804676] do_group_exit+0x43/0xb0 [ 4847.805719] get_signal+0x27b/0x590 [ 4847.806742] do_signal+0x37/0x730 [ 4847.807774] ? do_futex+0x325/0x500 [ 4847.808803] ? SyS_futex+0x13b/0x180 [ 4847.809852] ? restore_altstack+0x51/0x70 [ 4847.811017] exit_to_usermode_loop+0x73/0xd0 [ 4847.812299] do_syscall_64+0x115/0x130 [ 4847.813401] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 [ 4847.814808] RIP: 0033:0x7f9a142bc10d [ 4847.815914] RSP: 002b:7f9a09a01798 EFLAGS: 0246 ORIG_RAX: 00ca [ 4847.818100] RAX: fe00 RBX: 5583a8961060 RCX: 7f9a142bc10d [ 4847.820065] RDX: 0002 RSI: 0080 RDI: 5583a6925e00 [ 4847.822029] RBP: 5583a8961084 R08: 5583a6925e00 R09: [ 4847.824002] R10: R11: 0246 R12: 5583a896108c [ 4847.825949] R13: R14: 5583a6925e00 R15: 000f [ 4847.827922] Code: 0f 1f 80 00 00 00 00 55 48 89 e5 0f 20 d8 5d c3 0f 1f 80 00
