[Kernel-packages] [Bug 1753127] Re: No nvidia driver support in a wayland session
Hello, I have reinstall a fresh Ubuntu 18.04 but I can’t always open any user session Best regards Battant -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1753127 Title: No nvidia driver support in a wayland session Status in nvidia-graphics-drivers-390 package in Ubuntu: Triaged Bug description: Why not? If I log into X11 then the nvidia drivers are used, if I log into wayland then it reverts to Intel. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nvidia-driver-390 390.25-0ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Mar 3 11:29:53 2018 InstallationDate: Installed on 2018-03-03 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180301) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nvidia-graphics-drivers-390 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1753127/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1776578] Re: Ubuntu installation stuck at "Installing the 'grub2' package..." every time. Kernel crash every time.
See also: https://bugs.launchpad.net/ubuntu/+bugs?field.tag=apollo-lake -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1776578 Title: Ubuntu installation stuck at "Installing the 'grub2' package..." every time. Kernel crash every time. Status in grub2 package in Ubuntu: New Status in linux package in Ubuntu: New Bug description: Ubuntu 18.04 and 18.10 installation never completes on one particular machine (Apollo Lake N4200). It always ends up stuck at "Installing the 'grub2' package..." The kernel log shows a crash each time. The same installation media works perfectly on other machines. The same machine installs Windows 10 perfectly too. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1776578/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1776578] Re: Ubuntu installation stuck at "Installing the 'grub2' package..." every time. Kernel reports "invalid opcode: 0000 [#1] SMP NOPTI" every time.
** Attachment added: "cosmic Screenshot from 2018-06-10 14-54-35.png" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776578/+attachment/5151912/+files/cosmic%20Screenshot%20from%202018-06-10%2014-54-35.png -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1776578 Title: Ubuntu installation stuck at "Installing the 'grub2' package..." every time. Kernel crash every time. Status in grub2 package in Ubuntu: New Status in linux package in Ubuntu: New Bug description: Ubuntu 18.04 and 18.10 installation never completes on one particular machine (Apollo Lake N4200). It always ends up stuck at "Installing the 'grub2' package..." The kernel log shows a crash each time. The same installation media works perfectly on other machines. The same machine installs Windows 10 perfectly too. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1776578/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1776578] Re: Ubuntu installation stuck at "Installing the 'grub2' package..." every time. Kernel reports "invalid opcode: 0000 [#1] SMP NOPTI" every time.
** Attachment added: "cosmic dmesg.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776578/+attachment/5151913/+files/cosmic%20dmesg.txt ** Summary changed: - Ubuntu installation stuck at "Installing the 'grub2' package..." every time. Kernel reports "invalid opcode: [#1] SMP NOPTI" every time. + Ubuntu installation stuck at "Installing the 'grub2' package..." every time. Kernel crash every time. ** Description changed: - Ubuntu 18.04 and 18.10 installation never completes on one particular machine (Apollo Lake N4200). + Ubuntu 18.04 and 18.10 installation never completes on one particular + machine (Apollo Lake N4200). + It always ends up stuck at "Installing the 'grub2' package..." - Kernel reports "invalid opcode: [#1] SMP NOPTI". + The kernel log shows a crash each time. The same installation media works perfectly on other machines. + The same machine installs Windows 10 perfectly too. ** Tags added: bionic cosmic ** Also affects: grub2 (Ubuntu) Importance: Undecided Status: New ** Tags added: apollo-lake -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1776578 Title: Ubuntu installation stuck at "Installing the 'grub2' package..." every time. Kernel crash every time. Status in grub2 package in Ubuntu: New Status in linux package in Ubuntu: New Bug description: Ubuntu 18.04 and 18.10 installation never completes on one particular machine (Apollo Lake N4200). It always ends up stuck at "Installing the 'grub2' package..." The kernel log shows a crash each time. The same installation media works perfectly on other machines. The same machine installs Windows 10 perfectly too. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1776578/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1760643] Re: test_072_config_debug_rodata in kernel security test failed with 4.4 X-kvm
** Changed in: ubuntu-kernel-tests Status: In Progress => Fix Released ** Changed in: linux-kvm (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1760643 Title: test_072_config_debug_rodata in kernel security test failed with 4.4 X-kvm Status in QA Regression Testing: Fix Released Status in ubuntu-kernel-tests: Fix Released Status in linux package in Ubuntu: Invalid Status in linux-kvm package in Ubuntu: Fix Released Status in linux source package in Xenial: Invalid Status in linux-kvm source package in Xenial: Fix Released Bug description: == Justification == In Xenial KVM kernel, the CONFIG_DEBUG_KERNEL is enabled, security team would like to see CONFIG_DEBUG_RODATA to be enabled as well. == Test == Before enabling the config the test_072_config_debug_rodata test from qa-regression-testing will fail. After that, the test will pass. A test kernel with CONFIG_DEBUG_RODATA enabled in Xenial KVM could be found here: http://people.canonical.com/~phlin/kernel/lp-1760643/ == Fix == Enable the CONFIG_DEBUG_RODATA. Some other configs were enabled just for skipping the interaction during the compilation. == Regression Potential == Minimal. No code changes, just one config enabled without disabling any other configs. The test failed with: FAIL: test_072_config_debug_rodata (__main__.KernelSecurityTest) CONFIG_DEBUG_RODATA/CONFIG_STRICT_KERNEL_RWX enabled -- Traceback (most recent call last): File "./test-kernel-security.py", line 642, in test_072_config_debug_rodata self.assertEqual(self._test_config(option), expected) AssertionError: False != True Steps to reproduce: Deploy the node with Xenial 4.4 kernel, install linux-kvm sudo apt-get install python-minimal git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest-client-tests -b master-next git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest rm -fr autotest/client/tests ln -sf ~/autotest-client-tests autotest/client/tests AUTOTEST_PATH=/home/ubuntu/autotest sudo -E autotest/client/autotest-local --verbose autotest/client/tests/ubuntu_qrt_kernel_security/control ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-1019-kvm 4.4.0-1019.24 ProcVersionSignature: User Name 4.4.0-1019.24-kvm 4.4.98 Uname: Linux 4.4.0-1019-kvm x86_64 NonfreeKernelModules: signpost ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Mon Apr 2 16:54:36 2018 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.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/qa-regression-testing/+bug/1760643/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1775764] Re: Unable to switch VTs - screen frozen
This bug has existed for as long as I remember. I do not know of any kernel version that didn't have it, but at the same time I have only been trying for a year or less. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1775764 Title: Unable to switch VTs - screen frozen Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Bug description: Prior to doing any Gnome Shell development I always disable the existing instance by dropping back to a non-graphical runlevel: sudo systemctl start multi-user.target At least half the time this works. But the other half the time the screen freezes and I am not able to interact with it or switch VTs. Even a remote login can't force a VT switch: sudo chvt 4 # just hangs The kernel log shows no errors at all. ProblemType: Bug DistroRelease: Ubuntu 18.10 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.10-0ubuntu3 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Fri Jun 8 13:21:38 2018 InstallationDate: Installed on 2018-05-26 (12 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180525) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 17ef:6009 Lenovo ThinkPad Keyboard with TrackPoint Bus 001 Device 003: ID 045e:0047 Microsoft Corp. IntelliMouse Explorer 3.0 Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 10M7CTO1WW ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=d7ecc709-02c2-4413-b7e7-dfce1d2b3703 ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.15.0-22-generic N/A linux-backports-modules-4.15.0-22-generic N/A linux-firmware 1.174 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/06/2018 dmi.bios.vendor: LENOVO dmi.bios.version: M16KT47A dmi.board.name: 3102 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN 3259627060530 dmi.chassis.type: 3 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrM16KT47A:bd02/06/2018:svnLENOVO:pn10M7CTO1WW:pvrThinkCentreM710s:rvnLENOVO:rn3102:rvrSDK0J40709WIN3259627060530:cvnLENOVO:ct3:cvrNone: dmi.product.family: ThinkCentre M710s dmi.product.name: 10M7CTO1WW dmi.product.version: ThinkCentre M710s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775764/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 532137]
I quickly looked at the Xorg.log files from launchpad below. Right after hotplug of tablet, usbParse() goes in infinite loop and prints message about invalid serial #. Not positive its infinite loop but at least the log stops with no messages beyond repeating error message. If you wait long enough, perhaps the tablet corrects itself? Intuos1 and Intuos2 are unique in that they get serial # from hardware itself and used by xf86-input.wacom. Serial # is a unique value that allows tracking multiple tools at once. You've found a case were tablet streams out packets in a way that serial # is sent as zero. Either tablet is saying a zero value or else an if() statement is getting confused and not allowing to init values correctly. This is all on kernel side, BTW. Since I do not own own of these tablets, I do not have much more to offer. I can only say it appears mostly a kernel side bug from information so far. BTW: the best place to discuss wacom bugs is at project page bug tracker or mailing list: http://linuxwacom.sourceforge.net -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/532137 Title: Wacom Intuos2 tablet hotplug only works once after booting Status in X.Org X server: Invalid Status in linux package in Ubuntu: Incomplete Status in xf86-input-wacom package in Ubuntu: Incomplete Bug description: Binary package hint: xserver-xorg-input-wacom The following two tablets do not work out plug-and-play of the box in Lucid: 056a:0041 Wacom Co., Ltd Intuos2 4x5 056a:0044 Wacom Co., Ltd Intuos2 12x12 messages/syslog: Mar 4 14:17:37 cool kernel: [94581.248021] usb 3-2: new full speed USB device using uhci_hcd and address 6 Mar 4 14:17:37 cool kernel: [94581.416147] usb 3-2: configuration #1 chosen from 1 choice Mar 4 14:17:37 cool kernel: [94581.419397] input: Wacom Intuos2 4x5 as /devices/pci:00/:00:1a.0/usb3/3-2/3-2:1.0/input/input18 ProblemType: Bug Architecture: i386 Date: Thu Mar 4 14:36:17 2010 DistroRelease: Ubuntu 10.04 Package: xserver-xorg-input-wacom 1:0.10.3+20100109-1ubuntu1 ProcCmdLine: BOOT_IMAGE=/vmlinuz-2.6.32-15-generic root=/dev/mapper/hostname-root ro quiet splash ProcEnviron: PATH=(custom, user) LANG=en_US.utf8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.32-15.22-generic SourcePackage: nvidia-graphics-drivers Uname: Linux 2.6.32-15-generic i686 dmi.bios.date: 06/05/2006 dmi.bios.vendor: Intel Corp. dmi.bios.version: MQ96510J.86A.0372.2006.0605.1717 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: DG965MQ dmi.board.vendor: Intel Corporation dmi.board.version: AAD37419-102 dmi.chassis.type: 2 dmi.modalias: dmi:bvnIntelCorp.:bvrMQ96510J.86A.0372.2006.0605.1717:bd06/05/2006:svn:pn:pvr:rvnIntelCorporation:rnDG965MQ:rvrAAD37419-102:cvn:ct2:cvr: glxinfo: Error: [Errno 2] No such file or directory system: distro: Ubuntu codename: lucidarchitecture: i686kernel: 2.6.32-15-generic To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/532137/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1776578] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1776578 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1776578 Title: Ubuntu installation stuck at "Installing the 'grub2' package..." every time. Kernel crash every time. Status in grub2 package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu 18.04 and 18.10 installation never completes on one particular machine (Apollo Lake N4200). It always ends up stuck at "Installing the 'grub2' package..." The kernel log shows a crash each time. The same installation media works perfectly on other machines. The same machine installs Windows 10 perfectly too. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1776578/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1473200] Re: adaptec starfire fails to initialize with pae kernels
** Tags added: kernel-bug-exists-upstream-4.14-rc1 needs-upstream- testing xenial ** Description changed: Adaptec ethernet adapter using starfire driver fails to initialize when a pae-enabled kernel is used. Adapted initializes correctly with a non- pae kernel: From dmesg: [3.154813] FDC 0 is a National Semiconductor PC87306 [3.165051] [ cut here ] [3.169716] WARNING: CPU: 0 PID: 118 at /build/buildd/linux-lts-utopic-3.16.0/arch/x86/mm/ioremap.c:98 __ioremap_caller+0x358/0x380() [3.178686] tsc: Refined TSC clocksource calibration: 2790.998 MHz [3.187928] Modules linked in: starfire(+) mii floppy [3.193114] CPU: 0 PID: 118 Comm: systemd-udevd Not tainted 3.16.0-30-generic #40~14.04.1-Ubuntu [3.201911] Hardware name: Intel/SE7501BR2 , BIOS SBR20.86B.0041.P01.02102211/11/2002 [3.212522] f68a1c14 c168b423 [3.217089] usb 2-1: New USB device found, idVendor=413c, idProduct=2005 [3.217093] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [3.217098] usb 2-1: Product: DELL USB Keyboard [3.217102] usb 2-1: Manufacturer: DELL [3.240047] f68a1c44 c105c2ae c187a884 [3.244147] 0076 c1878950 0062 c104f0b8 c104f0b8 0fff fe4f [3.252032] f68a1c54 c105c372 0009 f68a1cb8 c104f0b8 c1878924 [3.259910] Call Trace: [3.262384] [] dump_stack+0x41/0x52 [3.266838] [] warn_slowpath_common+0x7e/0xa0 [3.272157] [] ? __ioremap_caller+0x358/0x380 [3.277476] [] ? __ioremap_caller+0x358/0x380 [3.282798] [] warn_slowpath_null+0x22/0x30 [3.287944] [] __ioremap_caller+0x358/0x380 [3.293096] [] ? __pci_request_selected_regions+0x3f/0x80 [3.299457] [] ? starfire_init_one+0xc6/0x5b0 [starfire] [3.305734] [] ioremap_nocache+0x1f/0x30 [3.310623] [] ? starfire_init_one+0xc6/0x5b0 [starfire] [3.316899] [] starfire_init_one+0xc6/0x5b0 [starfire] [3.323002] [] ? __pm_runtime_resume+0x51/0x70 [3.328417] [] pci_device_probe+0x6f/0xc0 [3.98] [] ? sysfs_create_link+0x25/0x40 [3.338632] [] driver_probe_device+0x93/0x3a0 [3.343958] [] ? pci_match_device+0xca/0x100 [3.349192] [] __driver_attach+0x71/0x80 [3.354081] [] ? __device_attach+0x40/0x40 [3.359139] [] bus_for_each_dev+0x47/0x80 [3.364114] [] driver_attach+0x1e/0x20 [3.368828] [] ? __device_attach+0x40/0x40 [3.373893] [] bus_add_driver+0x157/0x230 [3.378869] [] ? 0xf8370fff [3.382630] [] ? 0xf8370fff [3.386393] [] driver_register+0x59/0xe0 [3.391278] [] ? printk+0x50/0x52 [3.395557] [] __pci_register_driver+0x32/0x40 [3.400968] [] starfire_init+0x30/0x1000 [starfire] [3.406807] [] do_one_initcall+0xc2/0x1f0 [3.411779] [] ? 0xf8370fff [3.415544] [] ? free_vmap_area_noflush+0x24/0x60 [3.421208] [] ? __vunmap+0x8f/0xe0 [3.425660] [] ? __vunmap+0x8f/0xe0 [3.430117] [] load_module+0x1237/0x1930 [3.435005] [] SyS_finit_module+0x75/0xc0 [3.439978] [] ? vm_mmap_pgoff+0x7b/0xa0 [3.444867] [] sysenter_do_call+0x12/0x12 [3.449839] ---[ end trace 3eef602429cd6b81 ]--- [3.454468] starfire :08:04.0: cannot remap 0x8 @ 0xfe48, aborting [3.461915] ioremap: invalid physical address fe38 [3.467770] starfire :08:05.0: cannot remap 0x8 @ 0xfe38, aborting [3.475139] ioremap: invalid physical address fe30 [3.480984] starfire :08:06.0: cannot remap 0x8 @ 0xfe30, aborting [3.488341] ioremap: invalid physical address fe20 [3.494190] starfire :08:07.0: cannot remap 0x8 @ 0xfe20, aborting [3.501552] ioremap: invalid physical address fea8 [3.507394] starfire :09:04.0: cannot remap 0x8 @ 0xfea8, aborting [3.514741] ioremap: invalid physical address fe98 [3.520585] starfire :09:05.0: cannot remap 0x8 @ 0xfe98, aborting [3.527943] ioremap: invalid physical address fe90 [3.533789] starfire :09:06.0: cannot remap 0x8 @ 0xfe90, aborting [3.541144] ioremap: invalid physical address fe80 [3.546986] starfire :09:07.0: cannot remap 0x8 @ 0xfe80, aborting [3.554329] ioremap: invalid physical address fd68 [3.560175] starfire :05:04.0: cannot remap 0x8 @ 0xfd68, aborting [3.567492] ioremap: invalid physical address fd58 [3.573338] starfire :05:05.0: cannot remap 0x8 @ 0xfd58, aborting [3.580664] ioremap: invalid physical address fd50 [3.586511] starfire :05:06.0: cannot remap 0x8 @ 0xfd50, aborting [3.593836] ioremap: invalid
[Kernel-packages] [Bug 1473200] Re: adaptec starfire fails to initialize with pae kernels
Steve Holton: 1) To clarify, for the modification of drivers/net/ethernet/adaptec/starfire.c at line 653 did you test this in both 32-bit and 64-bit environments and had no issues using it? 2) To keep this relevant to upstream, it is best to continue to test the latest mainline kernel (now 4.17.1) as it is released, and note if the patch is still necessary, and if so, does it still work with no problems in both environments. Could you please advise? ** Changed in: linux (Ubuntu) Importance: Low => Medium ** Changed in: linux (Ubuntu) Status: Expired => 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/1473200 Title: adaptec starfire fails to initialize with pae kernels Status in linux package in Ubuntu: Incomplete Bug description: Adaptec ethernet adapter using starfire driver fails to initialize when a pae-enabled kernel is used. Adapted initializes correctly with a non-pae kernel: From dmesg: [3.154813] FDC 0 is a National Semiconductor PC87306 [3.165051] [ cut here ] [3.169716] WARNING: CPU: 0 PID: 118 at /build/buildd/linux-lts-utopic-3.16.0/arch/x86/mm/ioremap.c:98 __ioremap_caller+0x358/0x380() [3.178686] tsc: Refined TSC clocksource calibration: 2790.998 MHz [3.187928] Modules linked in: starfire(+) mii floppy [3.193114] CPU: 0 PID: 118 Comm: systemd-udevd Not tainted 3.16.0-30-generic #40~14.04.1-Ubuntu [3.201911] Hardware name: Intel/SE7501BR2 , BIOS SBR20.86B.0041.P01.02102211/11/2002 [3.212522] f68a1c14 c168b423 [3.217089] usb 2-1: New USB device found, idVendor=413c, idProduct=2005 [3.217093] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [3.217098] usb 2-1: Product: DELL USB Keyboard [3.217102] usb 2-1: Manufacturer: DELL [3.240047] f68a1c44 c105c2ae c187a884 [3.244147] 0076 c1878950 0062 c104f0b8 c104f0b8 0fff fe4f [3.252032] f68a1c54 c105c372 0009 f68a1cb8 c104f0b8 c1878924 [3.259910] Call Trace: [3.262384] [] dump_stack+0x41/0x52 [3.266838] [] warn_slowpath_common+0x7e/0xa0 [3.272157] [] ? __ioremap_caller+0x358/0x380 [3.277476] [] ? __ioremap_caller+0x358/0x380 [3.282798] [] warn_slowpath_null+0x22/0x30 [3.287944] [] __ioremap_caller+0x358/0x380 [3.293096] [] ? __pci_request_selected_regions+0x3f/0x80 [3.299457] [] ? starfire_init_one+0xc6/0x5b0 [starfire] [3.305734] [] ioremap_nocache+0x1f/0x30 [3.310623] [] ? starfire_init_one+0xc6/0x5b0 [starfire] [3.316899] [] starfire_init_one+0xc6/0x5b0 [starfire] [3.323002] [] ? __pm_runtime_resume+0x51/0x70 [3.328417] [] pci_device_probe+0x6f/0xc0 [3.98] [] ? sysfs_create_link+0x25/0x40 [3.338632] [] driver_probe_device+0x93/0x3a0 [3.343958] [] ? pci_match_device+0xca/0x100 [3.349192] [] __driver_attach+0x71/0x80 [3.354081] [] ? __device_attach+0x40/0x40 [3.359139] [] bus_for_each_dev+0x47/0x80 [3.364114] [] driver_attach+0x1e/0x20 [3.368828] [] ? __device_attach+0x40/0x40 [3.373893] [] bus_add_driver+0x157/0x230 [3.378869] [] ? 0xf8370fff [3.382630] [] ? 0xf8370fff [3.386393] [] driver_register+0x59/0xe0 [3.391278] [] ? printk+0x50/0x52 [3.395557] [] __pci_register_driver+0x32/0x40 [3.400968] [] starfire_init+0x30/0x1000 [starfire] [3.406807] [] do_one_initcall+0xc2/0x1f0 [3.411779] [] ? 0xf8370fff [3.415544] [] ? free_vmap_area_noflush+0x24/0x60 [3.421208] [] ? __vunmap+0x8f/0xe0 [3.425660] [] ? __vunmap+0x8f/0xe0 [3.430117] [] load_module+0x1237/0x1930 [3.435005] [] SyS_finit_module+0x75/0xc0 [3.439978] [] ? vm_mmap_pgoff+0x7b/0xa0 [3.444867] [] sysenter_do_call+0x12/0x12 [3.449839] ---[ end trace 3eef602429cd6b81 ]--- [3.454468] starfire :08:04.0: cannot remap 0x8 @ 0xfe48, aborting [3.461915] ioremap: invalid physical address fe38 [3.467770] starfire :08:05.0: cannot remap 0x8 @ 0xfe38, aborting [3.475139] ioremap: invalid physical address fe30 [3.480984] starfire :08:06.0: cannot remap 0x8 @ 0xfe30, aborting [3.488341] ioremap: invalid physical address fe20 [3.494190] starfire :08:07.0: cannot remap 0x8 @ 0xfe20, aborting [3.501552] ioremap: invalid physical address fea8 [3.507394] starfire :09:04.0: cannot remap 0x8 @ 0xfea8, aborting [3.514741] ioremap: invalid physical address fe98 [3.520585] starfire :09:05.0: cannot remap 0x8 @ 0xfe98, aborting [3.527943] ioremap:
[Kernel-packages] [Bug 1757218] Re: QCA9377 isn't being recognized sometimes
Bionic kernel with the delay quirk: https://people.canonical.com/~khfeng/lp1757218-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/1757218 Title: QCA9377 isn't being recognized sometimes Status in linux package in Ubuntu: Confirmed Bug description: Sometimes, the Wireless Network Card QCA9377 is not recognized on boot. This caused, on prior versions, a kernel panic at boot. With Bionic, the system boots but is unable to use wireless network. On dmesg there are messages like: [2.680590] usb 1-7: new full-speed USB device number 7 using xhci_hcd [2.808640] usb 1-7: device descriptor read/64, error -71 [3.044337] usb 1-7: device descriptor read/64, error -71 [3.280064] usb 1-7: new full-speed USB device number 8 using xhci_hcd [3.408245] usb 1-7: device descriptor read/64, error -71 [3.644244] usb 1-7: device descriptor read/64, error -71 [3.752193] usb usb1-port7: attempt power cycle [4.404591] usb 1-7: new full-speed USB device number 9 using xhci_hcd [4.404904] usb 1-7: Device not responding to setup address. [4.612478] usb 1-7: Device not responding to setup address. [4.820588] usb 1-7: device not accepting address 9, error -71 [4.948591] usb 1-7: new full-speed USB device number 10 using xhci_hcd [4.949109] usb 1-7: Device not responding to setup address. [5.156893] usb 1-7: Device not responding to setup address. [5.364589] usb 1-7: device not accepting address 10, error -71 [5.364655] usb usb1-port7: unable to enumerate USB device And lspci and lsusb don't show the wireless network card. The alternative is to turn the system off. Reboot don't work and reboot to Windows 10 also don't. The system must be powered off to restore functionality. Then, on the next boot, it works properly. However, after the system is turned off, it may cause the issue again. This is not 100% consistent, but mostly it cycles between powering off and powering on the notebook as: Work -> Don't work -> Work -> Don't work On Windows 10 this doesn't happen but when happens on Ubuntu, it's possible to reboot and see the status on Windows 10 too: on Device Manager it's shown a unidentified USB device at 1-7. Sometimes, on Windows 10's Network Devices it's shown, instead of the QCA9377, from four to six different devices with generic names and Bluetooth and/or Wireless don't work. When turning Ubuntu off, there are messages that appears a few instants before the system is turned off: Mar 18 18:27:26 usuario-Lenovo-ideapad-310-14ISK kernel: [14146.403388] ath10k_pci :02:00.0: failed to install key for vdev 0 peer xx:xx:xx:xx:xx:xx: -110 Mar 18 18:27:26 usuario-Lenovo-ideapad-310-14ISK kernel: [14146.403399] wlp2s0: failed to remove key (0, xx:xx:xx:xx:xx:xx) from hardware (-110) Generally, only the second message appears (but both are recorded on kern.log). The MAC adress is the one from the router, not from the wireless card. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-12-generic 4.15.0-12.13 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: usuario1364 F pulseaudio /dev/snd/seq:usuario1258 F timidity CurrentDesktop: XFCE Date: Tue Mar 20 14:43:42 2018 HibernationDevice: RESUME=UUID=9f36068f-c6d6-4fd6-87d5-46f1f5247563 InstallationDate: Installed on 2017-06-13 (279 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: LENOVO 80UG ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic.efi.signed root=UUID=6b4ae5c0-c78c-49a6-a1ba-029192618a7a ro quiet RelatedPackageVersions: linux-restricted-modules-4.15.0-12-generic N/A linux-backports-modules-4.15.0-12-generic N/A linux-firmware 1.173 SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2017-10-20 (151 days ago) dmi.bios.date: 07/10/2017 dmi.bios.vendor: LENOVO dmi.bios.version: 0XCN43WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Toronto 4A2 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40679 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 310-14ISK dmi.modalias: dmi:bvnLENOVO:bvr0XCN43WW:bd07/10/2017:svnLENOVO:pn80UG:pvrLenovoideapad310-14ISK:rvnLENOVO:rnToronto4A2:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad310-14ISK: dmi.product.family: IDEAPAD dmi.product.name: 80UG dmi.product.version: Lenovo ideapad 310-14ISK dmi.sys.vendor: LENOVO To manage notifications about this bug go to:
[Kernel-packages] [Bug 1752961] Re: With kernel 4.13 btrfs scans for devices before all devices have been discovered
Sorry for the delay.
I built the next test kernel, up to the following commit:
cbcd4f08aa637b74f575268770da86a00fabde6d
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1752961
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/1752961
Title:
With kernel 4.13 btrfs scans for devices before all devices have been
discovered
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:
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 1776333] Re: linux: 4.13.0-46.51 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed 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/1776333 Title: linux: 4.13.0-46.51 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Artful: New Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1776335 (linux-gcp), bug 1776336 (linux-hwe), bug 1776337 (linux-oem) derivatives: bug 1776334 (linux-raspi2) kernel-stable-phase-changed:Tuesday, 12. June 2018 13:00 UTC kernel-stable-phase:Uploaded -- swm properties -- boot-testing-requested: true phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1776333/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1774950] Re: Suspend fails in Ubuntu and Kubuntu 18.04 but works fine in Ubuntu and Kubuntu 17.10 (and on Kubuntu 18.04 using kernel 4.14.47)
@kaihengfeng the patched kernel works for me on an Acer Travelmate B115 with Intel Pentium N3540 CPU. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1774950 Title: Suspend fails in Ubuntu and Kubuntu 18.04 but works fine in Ubuntu and Kubuntu 17.10 (and on Kubuntu 18.04 using kernel 4.14.47) Status in linux package in Ubuntu: Confirmed Bug description: I have installed Kubuntu 18.04 on 3 different machines (my friend's and my own) with no suspend problems but my HP Pavilion 11 x360 does not suspend. It suspends fine with Ubuntu 17.10, Kubuntu 17.10, Devuan Jesse, Devuan ASCII and Windows 10 but fails with Ubuntu 18.04 and Kubuntu 18.04. I have also tried suspend using a live USB of 18.04 on this machine and it fails in the same way, so does not appear to be caused by any additional programs that I had installed. By installing an older kernel (4.14) on Kubuntu 18.04 the suspend function works as expected. Running Kubuntu 18.04 with kernels 4.15, 4.16, 4.17 results in the suspend failure that freezes the machine and requires a hard reset. Correct behaviour is - Screen goes blank, fan goes off, power LED flashes to show machine is in suspend. Pressing power button triggers 'resume' function. What happens - Screen goes blank, fan stays on, power LED stays on. Machine stays in this state and does not respond to any keyboard interaction, mouse movement or power button presses. Ctrl + Alt + f1 (or f2, f3, f4 etc) does not get any response. The only way to use the machine is to shut down by holding down the power button. Checking the logs suggests that the machine believes it is in suspend mode sleep [deep] when it isn't. Having to hard reset to get any response means that the kernel logs say no more than sleep [deep] pm-suspend also results in the same problems with kernels 4.15 and 4.16, but works fine with 4.14. It is curious that a machine that suspends fine on an earlier 4.14 kernel no longer works with 4.15 and above, whilst 3 other machines (including one with pretty similar hardware) do not exhibit this problem. There are only a handful of questions about it on the forums but at least 3 other people have the same problem: https://askubuntu.com/questions/1029405/ubuntu-18-04-crashes-on- resuming-from-suspend https://askubuntu.com/questions/1041369/after-upgrading- from-17-10-ubuntu-18-04-wont-sleep-suspend I am attempting to round up anyone else with the same issue and point them to this bug report. My laptop is HP Pavilion x360 11-n013na Matalaks is Acer Aspire ES1-511 collisionTwo has XPS 9560 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774950/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1774950] Re: Suspend fails in Ubuntu and Kubuntu 18.04 but works fine in Ubuntu and Kubuntu 17.10 (and on Kubuntu 18.04 using kernel 4.14.47)
@kaihengfeng - thanks for the patched kernel link. I have installed it and tested it on my machine and suspend now works as it should! I will continue running it over the next couple of days and check for any odd behaviour but it certainly seems to have fixed the 'suspend' problem. Many thanks! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1774950 Title: Suspend fails in Ubuntu and Kubuntu 18.04 but works fine in Ubuntu and Kubuntu 17.10 (and on Kubuntu 18.04 using kernel 4.14.47) Status in linux package in Ubuntu: Confirmed Bug description: I have installed Kubuntu 18.04 on 3 different machines (my friend's and my own) with no suspend problems but my HP Pavilion 11 x360 does not suspend. It suspends fine with Ubuntu 17.10, Kubuntu 17.10, Devuan Jesse, Devuan ASCII and Windows 10 but fails with Ubuntu 18.04 and Kubuntu 18.04. I have also tried suspend using a live USB of 18.04 on this machine and it fails in the same way, so does not appear to be caused by any additional programs that I had installed. By installing an older kernel (4.14) on Kubuntu 18.04 the suspend function works as expected. Running Kubuntu 18.04 with kernels 4.15, 4.16, 4.17 results in the suspend failure that freezes the machine and requires a hard reset. Correct behaviour is - Screen goes blank, fan goes off, power LED flashes to show machine is in suspend. Pressing power button triggers 'resume' function. What happens - Screen goes blank, fan stays on, power LED stays on. Machine stays in this state and does not respond to any keyboard interaction, mouse movement or power button presses. Ctrl + Alt + f1 (or f2, f3, f4 etc) does not get any response. The only way to use the machine is to shut down by holding down the power button. Checking the logs suggests that the machine believes it is in suspend mode sleep [deep] when it isn't. Having to hard reset to get any response means that the kernel logs say no more than sleep [deep] pm-suspend also results in the same problems with kernels 4.15 and 4.16, but works fine with 4.14. It is curious that a machine that suspends fine on an earlier 4.14 kernel no longer works with 4.15 and above, whilst 3 other machines (including one with pretty similar hardware) do not exhibit this problem. There are only a handful of questions about it on the forums but at least 3 other people have the same problem: https://askubuntu.com/questions/1029405/ubuntu-18-04-crashes-on- resuming-from-suspend https://askubuntu.com/questions/1041369/after-upgrading- from-17-10-ubuntu-18-04-wont-sleep-suspend I am attempting to round up anyone else with the same issue and point them to this bug report. My laptop is HP Pavilion x360 11-n013na Matalaks is Acer Aspire ES1-511 collisionTwo has XPS 9560 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774950/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1775786] Re: Update to ocxl driver for 18.04.1
** Changed in: linux (Ubuntu) Status: New => Triaged ** 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 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1775786 Title: Update to ocxl driver for 18.04.1 Status in The Ubuntu-power-systems project: Triaged Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Bug description: ---Problem Description--- Update to ocxl driver ---uname output--- 4.15.0-22-generic ---Additional Hardware Info--- opencapi adapter needed Machine Type = any POWER9 system ---Debugger--- A debugger is not configured == Comment: #1 - Frederic Barrat - 2018-06-05 03:46:00 == ocxl (opencapi) is a relatively new driver which was added to Ubuntu 18.04; It's specific to POWER9 systems. We'd like to add the following 9 commits for Ubuntu 18.04.1: The following 2 patches are already in the main linux tree: 474cca5fd894de99afc69274e8b25524ae62d7ee misc: ocxl: use put_device() instead of device_unregister() e7666d046ac0eda535282a5fd3b188f31d0f4afd ocxl: Document the OCXL_IOCTL_GET_METADATA IOCTL The remaining commits are in the powerpc-next tree and will be merged in the next merge window (i.e. in a week or so). See https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/log/?h=next 819844285ef2b5d15466f5b5062514135ffba06c powerpc: Add TIDR CPU feature for POWER9 3449f191ca9be1a6ac9757b8ab55f239092362e5 powerpc: Use TIDR CPU feature to control TIDR allocation 71cc64a85d8d99936f6851709a07f18c87a0adab powerpc: use task_pid_nr() for TID allocation 19df39581ce99eb1fcfb119945810c9c5bc3f8d4 ocxl: Rename pnv_ocxl_spa_remove_pe to clarify it's action e948e06fc63a1c1e36ec4c8e5c510b881ff19c26 ocxl: Expose the thread_id needed for wait on POWER9 02a8e5bc1c06045f36423bd9632ad9f40da18d3f ocxl: Add an IOCTL so userspace knows what OCXL features are available 721c551d31fb441ff3be701ad3be14cf6e0aca3f ocxl: Document new OCXL IOCTLs Another commit ID to add to the list (fixes a commit from previous list), from the 'next' tree: 2e5c93d6bb2f7bc17eb82748943a1b9f6b068520 ocxl: Fix missing unlock on error in afu_ioctl_enable_p9_wait() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1775786/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1776211] Re: kdump fails to take dump with smt set to 2, hmc dumpstart
** Changed in: makedumpfile (Ubuntu) Status: New => Incomplete ** Changed in: makedumpfile (Ubuntu Artful) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1776211 Title: kdump fails to take dump with smt set to 2, hmc dumpstart Status in The Ubuntu-power-systems project: In Progress Status in linux package in Ubuntu: Invalid Status in makedumpfile package in Ubuntu: Incomplete Status in linux source package in Artful: In Progress Status in makedumpfile source package in Artful: Incomplete Bug description: --Problem Description--- kdump fails to take dump with smt set to 2, hmc dumpstart ---Issue observed--- [0.004111] Oops: Exception in kernel mode, sig: 4 [#1] [0.004118] SMP NR_CPUS=2048 [0.004120] NUMA [0.004125] pSeries [0.004132] Modules linked in: [0.004142] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 4.13.0-12-generic #13-Ubuntu [0.004153] task: c00046715900 task.stack: c00046134000 [0.004162] NIP: c0006468 LR: c801764c CTR: 006cdc70 [0.004173] REGS: c00047fe3ce0 TRAP: 0700 Not tainted (4.13.0-12-generic) [0.004181] MSR: 80081031 [0.004193] CR: 8804 XER: 2003 [0.004204] CFAR: c0006454 SOFTE: 0 [0.004204] GPR00: c801764c c00047fe3f60 c95e3000 [0.004204] GPR04: 0001 0002 ffdf [0.004204] GPR08: 2804 0002 0002 [0.004204] GPR12: cfff c00046137f90 0b5452d8 [0.004204] GPR16: fffd 089ffd10 0136 0b55d378 [0.004204] GPR20: 0060 1eca 0a6c 0007 [0.004204] GPR24: c9621ed0 [0.004204] GPR28: c00046134000 c00046137c80 c9105df8 [0.004328] NIP [c0006468] 0xc0006468 [0.004338] LR [c801764c] __do_irq+0x4c/0x1c0 [0.004345] Call Trace: [0.004354] [c00047fe3f60] [c801764c] __do_irq+0x4c/0x1c0 (unreliable) [0.004368] [c00047fe3f90] [c802ab70] call_do_irq+0x14/0x24 [0.004380] [c00046137bc0] [c801785c] do_IRQ+0x9c/0x130 [0.004393] [c00046137c10] [c8008ac4] hardware_interrupt_common+0x114/0x120 [0.004409] --- interrupt: 501 at arch_local_irq_restore+0x5c/0x90 [0.004409] LR = arch_local_irq_restore+0x40/0x90 [0.004423] [c00046137f00] [0005] 0x5 (unreliable) [0.004436] [c00046137f20] [c8049824] start_secondary+0x324/0x350 [0.004450] [c00046137f90] [c800aa6c] start_secondary_prolog+0x10/0x14 [0.004460] Instruction dump: [0.004467] [0.004484] [0.004506] ---[ end trace 3e5a2a9047ef3cd0 ]--- [0.004512] [0.004518] Oops: Exception in kernel mode, sig: 4 [#2] [0.004525] SMP NR_CPUS=2048 [0.004526] NUMA [0.004532] pSeries [0.004540] Modules linked in: [0.004550] CPU: 1 PID: 0 Comm: swapper/1 Tainted: G D 4.13.0-12-generic #13-Ubuntu [0.004561] task: c9579f00 task.stack: c95dc000 [0.004569] NIP: c0006460 LR: c80b6e80 CTR: [0.004580] REGS: c95dfb20 TRAP: 0700 Tainted: G D (4.13.0-12-generic) [0.004589] MSR: 80081031 [0.004599] CR: 22002228 XER: 2004 [0.004611] CFAR: c000493c SOFTE: 0 [0.004611] GPR00: c95dfda0 c95e3000 [0.004611] GPR04: [0.004611] GPR08: 22002228 7fff 0008 [0.004611] GPR12: cfff0a80 c00c7e137f90 09980600 [0.004611] GPR16: 1ec7 0001 [0.004611] GPR20: 0007 [0.004611] GPR24: 0008 c800 0800 [0.004611] GPR28: 0008 c9621ed0 c9622354 [0.004729] NIP [c0006460] 0xc0006460 [0.004739] LR [c80b6e80] pseries_lpar_idle+0x30/0x50 [0.004746] Call Trace: [0.004756] [c95dfda0] [c95dfe90]
[Kernel-packages] [Bug 1775945] Re: Lenovi X1 Carbon regularly has frozen lock- or dark screen after closing lid
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 ** Changed in: linux-signed (Ubuntu) Importance: Undecided => Medium ** 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/1775945 Title: Lenovi X1 Carbon regularly has frozen lock- or dark screen after closing lid Status in linux package in Ubuntu: New Bug description: I was running ubuntu 17.10 for months with no issues. After upgrading to 18.04, closing the lid regularly (but not always) results in either: 1. The display staying on with a frozen lock-screen, or 2. The display powered off, but the notebook still powered on. In both cases the notebook does not respond. A five-second press of the power button to hard-reboot the computer is the only means of recovery. After powering the notebook back on, there are no files in /var/crash. 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.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Jun 9 00:00:48 2018 InstallationDate: Installed on 2018-06-02 (6 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/1775945/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1776113] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1776113 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1776113 Title: Laptop does not suspend when lid is closed Status in linux package in Ubuntu: Incomplete Bug description: $ lsb_release -rd Description: Ubuntu 18.04 LTS Release: 18.04 In Tweaks > Power, "Suspend when laptop lid is closed" is ON, but my laptop does not suspend when the lid is closed. The laptop is a Thinkpad P50. When closing the laptop lid, no events show up in dmesg. This is my /etc/systemd/login.conf: [Login] #NAutoVTs=6 #ReserveVT=6 #KillUserProcesses=no #KillOnlyUsers= #KillExcludeUsers=root #InhibitDelayMaxSec=5 #HandlePowerKey=poweroff #HandleSuspendKey=suspend #HandleHibernateKey=hibernate HandleLidSwitch=suspend HandleLidSwitchDocked=suspend #PowerKeyIgnoreInhibited=no #SuspendKeyIgnoreInhibited=no #HibernateKeyIgnoreInhibited=no #LidSwitchIgnoreInhibited=yes #HoldoffTimeoutSec=30s #IdleAction=ignore #IdleActionSec=30min #RuntimeDirectorySize=10% #RemoveIPC=yes #InhibitorsMax=8192 #SessionsMax=8192 #UserTasksMax=33% 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 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Jun 10 14:16:10 2018 InstallationDate: Installed on 2018-03-26 (76 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed UpgradeStatus: Upgraded to bionic on 2018-05-17 (24 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776113/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1776108] Re: Resume after hibernate/suspend fails
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 ** 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/1776108 Title: Resume after hibernate/suspend fails Status in linux package in Ubuntu: Incomplete Bug description: Fresh/clean install of 18.04 resulted in hibernation working (after it being broken on an upgrade install). Now after rebooting after recent package upgrades (last 4-5 days) resuming from suspend/hibernate fails. Have to force hard reboot Last message in syslog is: PM: suspend entry (deep) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-22-generic 4.15.0-22.24 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.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: petter 1475 F pulseaudio /dev/snd/controlC0: petter 1475 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Jun 10 22:34:32 2018 HibernationDevice: RESUME=UUID=8f436028-c350-445e-85dc-115d58d47796 InstallationDate: Installed on 2018-05-18 (23 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IwConfig: lono wireless extensions. enp5s0no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=sv_SE.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=bc80c3a6-55ef-4636-ac7a-d7bd837b6320 ro 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.1 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/14/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F22 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z77-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF22:bd11/14/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ77-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.: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: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776108/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1776266] Re: Touchpad and keyboard of MacBook unresponsive
** 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/1776266 Title: Touchpad and keyboard of MacBook unresponsive Status in linux package in Ubuntu: Confirmed Bug description: The touchpad and keyboard of my Macbook are unresponsive in Ubuntu 18.04. External USB devices are fine. At first it happened sporadically at boot or kicking in during operation, now it's a somewhat permanent state. In grub I can still use the keyboard, on the login screen not anymore. dmesg snippet of the relevant lines: [0.00] Linux version 4.15.0-22-generic (buildd@lgw01-amd64-013) (gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #24-Ubuntu SMP Wed May 16 12:15:17 UTC 2018 (Ubuntu 4.15.0-22.24-generic 4.15.17) [ ... ] [1.644120] usb 1-5: new full-speed USB device number 3 using xhci_hcd [1.772223] usb 1-5: device descriptor read/64, error -71 [2.008240] usb 1-5: device descriptor read/64, error -71 [2.244154] usb 1-5: new full-speed USB device number 4 using xhci_hcd [2.372240] usb 1-5: device descriptor read/64, error -71 [2.608239] usb 1-5: device descriptor read/64, error -71 [2.716180] usb usb1-port5: attempt power cycle [3.368155] usb 1-5: new full-speed USB device number 5 using xhci_hcd [3.368385] usb 1-5: Device not responding to setup address. [3.576372] usb 1-5: Device not responding to setup address. [3.784150] usb 1-5: device not accepting address 5, error -71 [3.912155] usb 1-5: new full-speed USB device number 6 using xhci_hcd [3.912397] usb 1-5: Device not responding to setup address. [4.120389] usb 1-5: Device not responding to setup address. [4.328154] usb 1-5: device not accepting address 6, error -71 [4.328190] usb usb1-port5: unable to enumerate USB device Apparently touchpad and keyboard are connected internally via USB? This happens with the current Ubuntu generic kernel (4.15.0-22) as well as vanilla upstream kernel 4.17. In fact, it happened already with Ubuntu 16.04 and whatever the recent kernel there was. 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.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ole2200 F pulseaudio /dev/snd/controlC0: ole2200 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Jun 11 19:25:07 2018 InstallationDate: Installed on 2018-06-01 (10 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 05ac:8290 Apple, Inc. Bus 001 Device 031: ID 04d9:1603 Holtek Semiconductor, Inc. Keyboard Bus 001 Device 030: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Apple Inc. MacBookPro12,1 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=28bf4396-f8c7-4936-9d45-d970c49ef1f3 ro resume=/dev/disk/by-uuid/28bf4396-f8c7-4936-9d45-d970c49ef1f3 resume_offset=34816 quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-22-generic N/A linux-backports-modules-4.15.0-22-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/09/2018 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP121.88Z.0176.B00.1804091715 dmi.board.name: Mac-E43C1C25D4880AD6 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro12,1 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-E43C1C25D4880AD6 dmi.modalias: dmi:bvnAppleInc.:bvrMBP121.88Z.0176.B00.1804091715:bd04/09/2018:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro12,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776266/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1775875] Re: Ubuntu 18.04 Lenovo X1 Carbon 5th fails to suspend after detaching dock station (NULL pointer dereference)
*** This bug is a duplicate of bug 1768852 *** https://bugs.launchpad.net/bugs/1768852 ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete ** This bug has been marked a duplicate of bug 1768852 Kernel bug when unplugging Thunderbolt 3 cable, leaves xHCI host controller dead -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1775875 Title: Ubuntu 18.04 Lenovo X1 Carbon 5th fails to suspend after detaching dock station (NULL pointer dereference) Status in linux package in Ubuntu: Incomplete Bug description: lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04 LTS Release: 18.04 Codename: bionic uname -r 4.15.0-22-generic How to reproduce: 1) connect dock station 2) disconnect dock station 3) type: systemctl suspend Result: system doesn't respond. Only Alt + Print Screen + SUB works. There is a workaround for this issue - disable USB for thunderbolt 3 in BIOS. But this is slightly an overkill. Error from kern.log: Jun 4 12:09:33 ya-x1 kernel: [ 375.060038] pcieport :0a:03.0: Refused to change power state, currently in D3 Jun 4 12:09:33 ya-x1 kernel: [ 375.061527] xhci_hcd :0d:00.0: remove, state 1 Jun 4 12:09:33 ya-x1 kernel: [ 375.061532] usb usb6: USB disconnect, device number 1 Jun 4 12:09:33 ya-x1 kernel: [ 375.061533] usb 6-1: USB disconnect, device number 2 Jun 4 12:09:33 ya-x1 kernel: [ 375.061572] xhci_hcd :0d:00.0: xHCI host controller not responding, assume dead Jun 4 12:09:33 ya-x1 kernel: [ 375.061578] r8152 6-1:1.0 enx0050b68eac7d: Stop submitting intr, status -108 Jun 4 12:09:33 ya-x1 kernel: [ 375.116210] xhci_hcd :0d:00.0: USB bus 6 deregistered Jun 4 12:09:33 ya-x1 kernel: [ 375.116217] xhci_hcd :0d:00.0: remove, state 1 Jun 4 12:09:33 ya-x1 kernel: [ 375.116220] usb usb5: USB disconnect, device number 1 Jun 4 12:09:33 ya-x1 kernel: [ 375.116222] usb 5-3: USB disconnect, device number 3 Jun 4 12:09:33 ya-x1 kernel: [ 375.117197] xhci_hcd :0d:00.0: Host halt failed, -19 Jun 4 12:09:33 ya-x1 kernel: [ 375.117199] xhci_hcd :0d:00.0: Host not accessible, reset failed. Jun 4 12:09:33 ya-x1 kernel: [ 375.117307] xhci_hcd :0d:00.0: USB bus 5 deregistered Jun 4 12:09:33 ya-x1 kernel: [ 375.147887] pcieport :0a:02.0: Refused to change power state, currently in D3 Jun 4 12:09:33 ya-x1 kernel: [ 375.149415] pcieport :0a:01.0: Refused to change power state, currently in D3 Jun 4 12:09:33 ya-x1 kernel: [ 375.150959] xhci_hcd :0b:00.0: remove, state 4 Jun 4 12:09:33 ya-x1 kernel: [ 375.150965] usb usb4: USB disconnect, device number 1 Jun 4 12:09:33 ya-x1 kernel: [ 375.151217] xhci_hcd :0b:00.0: USB bus 4 deregistered Jun 4 12:09:33 ya-x1 kernel: [ 375.151223] xhci_hcd :0b:00.0: xHCI host controller not responding, assume dead Jun 4 12:09:33 ya-x1 kernel: [ 375.151230] xhci_hcd :0b:00.0: remove, state 1 Jun 4 12:09:33 ya-x1 kernel: [ 375.151233] usb usb3: USB disconnect, device number 1 Jun 4 12:09:33 ya-x1 kernel: [ 375.151234] usb 3-1: USB disconnect, device number 2 Jun 4 12:09:33 ya-x1 kernel: [ 375.192843] usb 3-4: USB disconnect, device number 3 Jun 4 12:09:33 ya-x1 kernel: [ 375.194286] BUG: unable to handle kernel NULL pointer dereference at 0034 Jun 4 12:09:33 ya-x1 kernel: [ 375.194294] IP: tty_unregister_driver+0xd/0x70 Jun 4 12:09:33 ya-x1 kernel: [ 375.194295] PGD 0 P4D 0 Jun 4 12:09:33 ya-x1 kernel: [ 375.194298] Oops: [#1] SMP PTI Jun 4 12:09:33 ya-x1 kernel: [ 375.194300] Modules linked in: cdc_ether usbnet r8152 mii hid_generic snd_usb_audio usbhid snd_usbmidi_lib ccm thunderbolt bnep snd_hda_codec_hdmi snd_hda_codec_conexant snd_hda_codec_generic nls_iso8859_1 intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp arc4 kvm_intel snd_soc_skl kvm snd_soc_skl_ipc snd_hda_ext_core snd_soc_sst_dsp irqbypass snd_soc_sst_ipc crct10dif_pclmul snd_soc_acpi crc32_pclmul snd_soc_core ghash_clmulni_intel snd_compress ac97_bus pcbc snd_pcm_dmaengine snd_seq_midi snd_hda_intel snd_hda_codec snd_seq_midi_event snd_hda_core snd_hwdep aesni_intel uvcvideo snd_rawmidi aes_x86_64 input_leds crypto_simd glue_helper snd_pcm videobuf2_vmalloc cryptd intel_cstate intel_rapl_perf videobuf2_memops iwlmvm videobuf2_v4l2 joydev mac80211 serio_raw btusb videobuf2_core snd_seq Jun 4 12:09:33 ya-x1 kernel: [ 375.194335] thinkpad_acpi btrtl btbcm intel_wmi_thunderbolt wmi_bmof btintel nvram iwlwifi rtsx_pci_ms videodev bluetooth snd_seq_device snd_timer media cfg80211 memstick snd ecdh_generic mei_me mei intel_pch_thermal ucsi_acpi shpchp typec_ucsi typec soundcore mac_hid acpi_pad tpm_crb
[Kernel-packages] [Bug 1776155] Re: Hantick HTT5288 touchpad wrongly detected as SYNA3602, does not work at all.
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 ** 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/1776155 Title: Hantick HTT5288 touchpad wrongly detected as SYNA3602, does not work at all. Status in linux package in Ubuntu: New Bug description: On my cheaper-end laptop/netbook the touchpad, which I believe is the Hantick HT 5288, is wrongly detected by Linux to be the SYNA 3602. Accordingly it does not work at all, neither touchpad nor buttons. Freshly installed Ubuntu 18.04 system. I belive the issue is, as reported previously other places by vendors of such computers, that the touchpad is not being reset properly on boot. martin@alanah:~$ cat /proc/bus/input/devices I: Bus=0019 Vendor= Product=0005 Version= N: Name="Lid Switch" P: Phys=PNP0C0D/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:13/PNP0C09:00/PNP0C0D:00/input/input0 U: Uniq= H: Handlers=event0 B: PROP=0 B: EV=21 B: SW=1 I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=PNP0C0C/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input1 U: Uniq= H: Handlers=kbd event1 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0011 Vendor=0001 Product=0001 Version=ab83 N: Name="AT Translated Set 2 keyboard" P: Phys=isa0060/serio0/input0 S: Sysfs=/devices/platform/i8042/serio0/input/input2 U: Uniq= H: Handlers=sysrq kbd event2 leds B: PROP=0 B: EV=120013 B: KEY=40200 3803078f800d001 fedfffef fffe B: MSC=10 B: LED=7 I: Bus=0019 Vendor= Product=0006 Version= N: Name="Video Bus" P: Phys=LNXVIDEO/video/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input3 U: Uniq= H: Handlers=kbd event3 B: PROP=0 B: EV=3 B: KEY=3e000b 0 0 0 I: Bus=0019 Vendor= Product= Version= N: Name="Intel HID events" P: Phys= S: Sysfs=/devices/platform/INT33D5:00/input/input4 U: Uniq= H: Handlers=rfkill kbd event4 B: PROP=0 B: EV=13 B: KEY=810003 504000 1e29400020 0 B: MSC=10 I: Bus=0019 Vendor= Product= Version= N: Name="Intel HID 5 button array" P: Phys= S: Sysfs=/devices/platform/INT33D5:00/input/input5 U: Uniq= H: Handlers=kbd event5 B: PROP=0 B: EV=33 B: KEY=1 0 201c 0 B: MSC=10 B: SW=1000 I: Bus=0003 Vendor=058f Product=5608 Version=0009 N: Name="VGA Webcam: VGA Webcam" P: Phys=usb-:00:15.0-8/button S: Sysfs=/devices/pci:00/:00:15.0/usb1/1-8/1-8:1.0/input/input6 U: Uniq= H: Handlers=kbd event6 B: PROP=0 B: EV=3 B: KEY=10 0 0 0 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH Mic" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:0e.0/sound/card0/input7 U: Uniq= H: Handlers=event7 B: PROP=0 B: EV=21 B: SW=10 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH Headphone" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:0e.0/sound/card0/input8 U: Uniq= H: Handlers=event8 B: PROP=0 B: EV=21 B: SW=4 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=3" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:0e.0/sound/card0/input9 U: Uniq= H: Handlers=event9 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=7" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:0e.0/sound/card0/input10 U: Uniq= H: Handlers=event10 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=8" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:0e.0/sound/card0/input11 U: Uniq= H: Handlers=event11 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=9" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:0e.0/sound/card0/input12 U: Uniq= H: Handlers=event12 B: PROP=0 B: EV=21 B: SW=140 I: Bus=
[Kernel-packages] [Bug 1775945] Re: Lenovi X1 Carbon regularly has frozen lock- or dark screen after closing lid
Please ignore the first question. You already indicated this is a regression. ** 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/1775945 Title: Lenovi X1 Carbon regularly has frozen lock- or dark screen after closing lid Status in linux package in Ubuntu: New Bug description: I was running ubuntu 17.10 for months with no issues. After upgrading to 18.04, closing the lid regularly (but not always) results in either: 1. The display staying on with a frozen lock-screen, or 2. The display powered off, but the notebook still powered on. In both cases the notebook does not respond. A five-second press of the power button to hard-reboot the computer is the only means of recovery. After powering the notebook back on, there are no files in /var/crash. 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.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Jun 9 00:00:48 2018 InstallationDate: Installed on 2018-06-02 (6 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/1775945/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1748689] Re: Mounting SMB shares with vers=3.0 in fstab gives "ioctl error in smb2_get_dfs_refer rc=-2"
Any update on this issue? Having it happen pretty consistently on my 16.04 machines. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1748689 Title: Mounting SMB shares with vers=3.0 in fstab gives "ioctl error in smb2_get_dfs_refer rc=-2" Status in linux package in Ubuntu: Confirmed Bug description: Xubuntu 17.10 artful Kernel: x86_64 Linux 4.13.0-32.35-generic cifs-utils 2:6.7-1 smbclient 2:4.6.7+dfsg-1ubuntu3.1 Mounting an SMB share with sec=ntlmssp,vers=3.0,credentials=/home/.smbcredentials,dir_mode=0777,file_mode=0777 in /etc/fstab gives the error: "CIFS VFS: ioctl error in smb2_get_dfs_refer rc=-2" in dmesg. Shares mounted this way are readable, but writing data to them (or using programs such as EasyTAG to write to them) ultimately fails. This bug did not occur in kernel 4.10. Mounting the share(s) with vers=1.0 does not give the error, but this is a haphazard fix as SMB v3.0 carries many security features with it not avaliable in SMB 1.0. --- ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: XFCE DistroRelease: Ubuntu 17.10 HibernationDevice: RESUME=/dev/mapper/DeusVitam--vg-swap_1 JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. MachineType: ASUS All Series Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic root=/dev/mapper/hostname--vg-root ro splash quiet amdgpu.cik_support=1 vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 RelatedPackageVersions: linux-restricted-modules-4.13.0-32-generic N/A linux-backports-modules-4.13.0-32-generic N/A linux-firmware 1.169.3 RfKill: Tags: artful Uname: Linux 4.13.0-32-generic x86_64 UpgradeStatus: Upgraded to artful on 2018-02-05 (7 days ago) UserGroups: libvirt libvirtd sudo wireshark WifiSyslog: _MarkForUpload: True dmi.bios.date: 03/16/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0701 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97-E/USB 3.1 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x 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.:bvr0701:bd03/16/2016:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-E/USB3.1:rvrRevX.0x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1748689/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1774950] Re: Suspend fails in Ubuntu and Kubuntu 18.04 but works fine in Ubuntu and Kubuntu 17.10 (and on Kubuntu 18.04 using kernel 4.14.47)
@pHeLiOn: Thanks for putting in the effort! Seeing that this is not resolved yet, I figured that though I'm not a kernel-hacker/sysadmin-guru by a long shot, I'll throw my tidbits in, in the faint hope that someone gets onto the right track. (For rememberance: Acer Aspire E13, Intel Celeron N2940, 4GB RAM, changed standard HD for a 250G SSD) 1.) The 'other' bug I mentioned above was (I believe) resolved by adding the statement intel_idle.max_cstate=1 in the grub configuration file. However, my first inquiries into the problem (System freezes, not resolvable by anything (didnt try remote access, though)) pointed me to a potential problem with the SSD HD. Now, I cannot, for the life of me, remember what it was, exactly, but it was something along the lines of Point No. 6 on this site: http://bernaerts.dyndns.org/linux/74-ubuntu/250-ubuntu-tweaks-ssd I remembered this because you narrowed it down to some CPU types PLUS SSD, so, maybe there's a hint somewhere. 2.) In my above Post, I mentioned that my problem was 'fixed' in 18.04 by downgrading the kernel, as mentioned. Well, it IS fixed in a way, but there remain some oddities - for example: After Boot, the cooling fan is on (running at a moderate pace at first) no matter what, even after a cold boot. It takes putting the system into suspend and out again (which, as mentioned, works now!) so that the fan is turned off completely - and, somewhat worringly, stays off. I've not tested running the system at full power to see if the cooling fan comes on again, when required - so as of now, I take it a bit on 'good faith' that it will :) These are my further observations - hope it helps somehow! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1774950 Title: Suspend fails in Ubuntu and Kubuntu 18.04 but works fine in Ubuntu and Kubuntu 17.10 (and on Kubuntu 18.04 using kernel 4.14.47) Status in linux package in Ubuntu: Confirmed Bug description: I have installed Kubuntu 18.04 on 3 different machines (my friend's and my own) with no suspend problems but my HP Pavilion 11 x360 does not suspend. It suspends fine with Ubuntu 17.10, Kubuntu 17.10, Devuan Jesse, Devuan ASCII and Windows 10 but fails with Ubuntu 18.04 and Kubuntu 18.04. I have also tried suspend using a live USB of 18.04 on this machine and it fails in the same way, so does not appear to be caused by any additional programs that I had installed. By installing an older kernel (4.14) on Kubuntu 18.04 the suspend function works as expected. Running Kubuntu 18.04 with kernels 4.15, 4.16, 4.17 results in the suspend failure that freezes the machine and requires a hard reset. Correct behaviour is - Screen goes blank, fan goes off, power LED flashes to show machine is in suspend. Pressing power button triggers 'resume' function. What happens - Screen goes blank, fan stays on, power LED stays on. Machine stays in this state and does not respond to any keyboard interaction, mouse movement or power button presses. Ctrl + Alt + f1 (or f2, f3, f4 etc) does not get any response. The only way to use the machine is to shut down by holding down the power button. Checking the logs suggests that the machine believes it is in suspend mode sleep [deep] when it isn't. Having to hard reset to get any response means that the kernel logs say no more than sleep [deep] pm-suspend also results in the same problems with kernels 4.15 and 4.16, but works fine with 4.14. It is curious that a machine that suspends fine on an earlier 4.14 kernel no longer works with 4.15 and above, whilst 3 other machines (including one with pretty similar hardware) do not exhibit this problem. There are only a handful of questions about it on the forums but at least 3 other people have the same problem: https://askubuntu.com/questions/1029405/ubuntu-18-04-crashes-on- resuming-from-suspend https://askubuntu.com/questions/1041369/after-upgrading- from-17-10-ubuntu-18-04-wont-sleep-suspend I am attempting to round up anyone else with the same issue and point them to this bug report. My laptop is HP Pavilion x360 11-n013na Matalaks is Acer Aspire ES1-511 collisionTwo has XPS 9560 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774950/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1776335] Re: linux-gcp: 4.13.0-1020.24 -proposed tracker
** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- + boot-testing-requested: true kernel-stable-master-bug: 1776333 phase: Uploaded -- 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/1776335 Title: linux-gcp: 4.13.0-1020.24 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1776333 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1776335/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1776333] Re: linux: 4.13.0-46.51 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed ** Tags added: block-proposed-artful ** Tags added: block-proposed ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1776335 (linux-gcp), bug 1776336 (linux-hwe), bug 1776337 (linux-oem) derivatives: bug 1776334 (linux-raspi2) kernel-stable-phase-changed:Tuesday, 12. June 2018 13:00 UTC kernel-stable-phase:Uploaded -- swm properties -- + boot-testing-requested: true phase: Uploaded -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1776333 Title: linux: 4.13.0-46.51 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Artful: New Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1776335 (linux-gcp), bug 1776336 (linux-hwe), bug 1776337 (linux-oem) derivatives: bug 1776334 (linux-raspi2) kernel-stable-phase-changed:Tuesday, 12. June 2018 13:00 UTC kernel-stable-phase:Uploaded -- swm properties -- boot-testing-requested: true phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1776333/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1757218] Re: QCA9377 isn't being recognized sometimes
This kernel did not work. On boot, the same messages that appeared with the other problematic kernels appear and the boot freezes. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1757218 Title: QCA9377 isn't being recognized sometimes Status in linux package in Ubuntu: Confirmed Bug description: Sometimes, the Wireless Network Card QCA9377 is not recognized on boot. This caused, on prior versions, a kernel panic at boot. With Bionic, the system boots but is unable to use wireless network. On dmesg there are messages like: [2.680590] usb 1-7: new full-speed USB device number 7 using xhci_hcd [2.808640] usb 1-7: device descriptor read/64, error -71 [3.044337] usb 1-7: device descriptor read/64, error -71 [3.280064] usb 1-7: new full-speed USB device number 8 using xhci_hcd [3.408245] usb 1-7: device descriptor read/64, error -71 [3.644244] usb 1-7: device descriptor read/64, error -71 [3.752193] usb usb1-port7: attempt power cycle [4.404591] usb 1-7: new full-speed USB device number 9 using xhci_hcd [4.404904] usb 1-7: Device not responding to setup address. [4.612478] usb 1-7: Device not responding to setup address. [4.820588] usb 1-7: device not accepting address 9, error -71 [4.948591] usb 1-7: new full-speed USB device number 10 using xhci_hcd [4.949109] usb 1-7: Device not responding to setup address. [5.156893] usb 1-7: Device not responding to setup address. [5.364589] usb 1-7: device not accepting address 10, error -71 [5.364655] usb usb1-port7: unable to enumerate USB device And lspci and lsusb don't show the wireless network card. The alternative is to turn the system off. Reboot don't work and reboot to Windows 10 also don't. The system must be powered off to restore functionality. Then, on the next boot, it works properly. However, after the system is turned off, it may cause the issue again. This is not 100% consistent, but mostly it cycles between powering off and powering on the notebook as: Work -> Don't work -> Work -> Don't work On Windows 10 this doesn't happen but when happens on Ubuntu, it's possible to reboot and see the status on Windows 10 too: on Device Manager it's shown a unidentified USB device at 1-7. Sometimes, on Windows 10's Network Devices it's shown, instead of the QCA9377, from four to six different devices with generic names and Bluetooth and/or Wireless don't work. When turning Ubuntu off, there are messages that appears a few instants before the system is turned off: Mar 18 18:27:26 usuario-Lenovo-ideapad-310-14ISK kernel: [14146.403388] ath10k_pci :02:00.0: failed to install key for vdev 0 peer xx:xx:xx:xx:xx:xx: -110 Mar 18 18:27:26 usuario-Lenovo-ideapad-310-14ISK kernel: [14146.403399] wlp2s0: failed to remove key (0, xx:xx:xx:xx:xx:xx) from hardware (-110) Generally, only the second message appears (but both are recorded on kern.log). The MAC adress is the one from the router, not from the wireless card. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-12-generic 4.15.0-12.13 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: usuario1364 F pulseaudio /dev/snd/seq:usuario1258 F timidity CurrentDesktop: XFCE Date: Tue Mar 20 14:43:42 2018 HibernationDevice: RESUME=UUID=9f36068f-c6d6-4fd6-87d5-46f1f5247563 InstallationDate: Installed on 2017-06-13 (279 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: LENOVO 80UG ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic.efi.signed root=UUID=6b4ae5c0-c78c-49a6-a1ba-029192618a7a ro quiet RelatedPackageVersions: linux-restricted-modules-4.15.0-12-generic N/A linux-backports-modules-4.15.0-12-generic N/A linux-firmware 1.173 SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2017-10-20 (151 days ago) dmi.bios.date: 07/10/2017 dmi.bios.vendor: LENOVO dmi.bios.version: 0XCN43WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Toronto 4A2 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40679 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 310-14ISK dmi.modalias: dmi:bvnLENOVO:bvr0XCN43WW:bd07/10/2017:svnLENOVO:pn80UG:pvrLenovoideapad310-14ISK:rvnLENOVO:rnToronto4A2:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad310-14ISK: dmi.product.family: IDEAPAD dmi.product.name: 80UG dmi.product.version: Lenovo ideapad 310-14ISK dmi.sys.vendor: LENOVO To manage notifications about
[Kernel-packages] [Bug 1776254] Re: CacheFiles: Error: Overlong wait for old active object to go away.
** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Incomplete => Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1776254 Title: CacheFiles: Error: Overlong wait for old active object to go away. Status in linux package in Ubuntu: Triaged Bug description: == SRU Justification == [Impact] Oops during heavy NFS + FSCache + Cachefiles use: CacheFiles: Error: Overlong wait for old active object to go away. BUG: unable to handle kernel NULL pointer dereference at 0002 CacheFiles: Error: Object already active kernel BUG at fs/cachefiles/namei.c:163! [Cause] In a heavily loaded system with big files being read and truncated, an fscache object for a cookie is being dropped and a new object being looked. The new object being looked for has to wait for the old object to go away before the new object is moved to active state. [Fix] Clear the flag 'CACHEFILES_OBJECT_ACTIVE' for the new object when retrying the object lookup. Remove the BUG() for the case where the old object is still being dropped and convert to WARN() [Testcase] A user has run ~100 hours of NFS stress tests and not seen this bug recur. [Regression Potential] - Limited to fscache/cachefiles. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776254/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1776325] Re: Error messages during boot - Ubuntu 18.04 & Mint19
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 ** 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/1776325 Title: Error messages during boot - Ubuntu 18.04 & Mint19 Status in linux package in Ubuntu: Incomplete Bug description: This came about as I had problems with efi while installing a dual boot of ubuntu and linux mint. As I understand it, during the boot process, the kernel sees a cpu count for the processor chip , AMD Ryzen 2400G, as 8 but 4 of them are graphics compute units. A little later in the process, the graphics processors cause errors. Subsequent to discovering this , I have added a line to grub GRUB_CMDLINE_LINUX_ which appears to have improved the boot process. It is 'ruc_nocbs=0-3'. The alteration in grub seems to help limit the cpu count and gets the boot process over the bump. I searched the interweb for clues and this seems to be a successful experiment. I am reporting this because I could not find any pertinent reference to this sort of problem with this particular chip. This search was not exhaustive so I hope I am not wasting your time :) I am attaching a file of concatenated system info for kernel reports as the options on this page only appear to allow one file to be selected (https://bugs.launchpad.net/ubuntu/+source/linux/+filebug/4aca6a90-6dc0-11e8 -b34a-002481e7f48a. Most of this was my lack of understanding the efi requirements, but the lack of useful information in the Gigabyte motherboard manual about how the UEFI operation was managed by its operating system prolonged my agony.:) I hope this helps, thank you and keep up the fantastic work Bob. 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.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tpf1528 F pulseaudio /dev/snd/controlC0: tpf1528 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Jun 12 09:38:39 2018 HibernationDevice: RESUME=UUID=150c1cd8-2246-4c18-b40e-dc07d8425777 InstallationDate: Installed on 2018-06-10 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Gigabyte Technology Co., Ltd. AB350N-Gaming WIFI ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_NZ.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=36d43481-0720-4808-a234-82941b71f750 ro quiet splash RelatedPackageVersions: linux-restricted-modules-4.15.0-22-generic N/A linux-backports-modules-4.15.0-22-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/17/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F23d dmi.board.asset.tag: Default string dmi.board.name: AB350N-Gaming WIFI-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF23d:bd04/17/2018:svnGigabyteTechnologyCo.,Ltd.:pnAB350N-GamingWIFI:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAB350N-GamingWIFI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: AB350N-Gaming WIFI dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776325/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1776159] Re: mdadm raid soft lock-ups ubuntu kernel 4.13.0-36 Inbox x
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 ** Tags added: artful kernel-da-key ** 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/1776159 Title: mdadm raid soft lock-ups ubuntu kernel 4.13.0-36 Inbox x Status in linux package in Ubuntu: Incomplete Bug description: we're running Ubuntu 16.04.4, mdadm - v3.3 and Kernel 4.13.0-36(ubuntu package linux-image-generic-hwe-16.04). We have created raid10 using 22 960GB SSDs [1] . The problem we're experiencing is that /usr/share/mdadm/checkarray (executed by cron, included in a mdadm pkg) results in (soft?) deadlock - load on the node spikes up to 500-700 and all I/O operations are blocked for a period of time. We can see traces liek these [2] in our kernel log. e.g. it ends up in static state like test@os-node1:~$ cat /proc/mdstat Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4] [raid10] md1 : active raid10 dm-23[9] dm-22[8] dm-21[7] dm-20[6] dm-18[4] dm-19[5] dm-17[3] dm-16[21] dm-15[20] dm-14[2] dm-13[19] dm-12[18] dm-11[17] dm-10[16] dm-9[15] dm-8[14] dm-7[13] dm-6[12] dm-5[11] dm-4[10] dm-3[1] dm-2[0] 10313171968 blocks super 1.2 512K chunks 2 near-copies [22/22] [UU] [===>.] check = 19.0% (1965748032/10313171968) finish=1034728.8min speed=134K/sec bitmap: 0/39 pages [0KB], 131072KB chunk unused devices: and the only solution is to hard reboot the node. What we found out is that it doesn't happen on idle raid, we have to generate some significant load (10 VMs running fio[3] with 500GB HDDs.) to be able to reproduce the issue. Anyone ever experienced similar issues? Do you have any suggestions how to better trouble shoot this issue and maybe identify if disks or software layer is responsible for this behavior [1] http://www.samsung.com/us/dell/pdfs/PM1633a_Flyer_2016_v4.pdf [2] https://gist.github.com/haad/09213bab1bc30a00c7d255c0bc60897b [3] https://github.com/axboe/fio To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776159/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1776277] Re: fscache cookie refcount updated incorrectly during fscache object allocation
** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Incomplete => Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1776277 Title: fscache cookie refcount updated incorrectly during fscache object allocation Status in linux package in Ubuntu: Triaged Bug description: == SRU Justification == [Impact] Oops during heavy NFS + FSCache + Cachefiles use: kernel BUG at /build/linux-Y09MKI/linux-4.4.0/fs/fscache/internal.h:321! kernel BUG at /build/linux-Y09MKI/linux-4.4.0/fs/fscache/cookie.c:639! [Cause] 1)Two threads are trying to do operate on a cookie and two objects. 2a)One thread tries to unmount the filesystem and in process goes over a huge list of objects marking them dead and deleting the objects. cookie->usage is also decremented in following path nfs_fscache_release_super_cookie -> __fscache_relinquish_cookie ->__fscache_cookie_put ->BUG_ON(atomic_read(>usage) <= 0); 2b)second thread tries to lookup an object for reading data in following path fscache_alloc_object 1) cachefiles_alloc_object -> fscache_object_init -> assign cookie, but usage not bumped. 2) fscache_attach_object -> fails in cant_attach_object because the cookie's backing object or cookie's->parent object are going away 3)fscache_put_object -> cachefiles_put_object ->fscache_object_destroy ->fscache_cookie_put ->BUG_ON(atomic_read(>usage) <= 0); [Fix] Bump up the cookie usage in fscache_object_init, when it is first being assigned a cookie atomically such that the cookie is added and bumped up if its refcount is not zero. remove the assignment in the attach_object. [Testcase] A user has run ~100 hours of NFS stress tests and not seen this bug recur. [Regression Potential] - Limited to fscache/cachefiles. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776277/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1776376] Re: Intel 9462 bluetooth and wifi doesn't work
** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1776376 Title: Intel 9462 bluetooth and wifi doesn't work Status in linux package in Ubuntu: Incomplete Bug description: Besides the issue mentioned above,the keyboard is not completely suitable. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-21-generic 4.4.0-21.37 [modified: boot/vmlinuz-4.4.0-21-generic] ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gjd1940 F pulseaudio CurrentDesktop: Unity Date: Tue Jun 12 10:33:31 2018 HibernationDevice: RESUME=UUID=a93c190f-117c-44c6-8595-37cc0499c28b InstallationDate: Installed on 2018-06-11 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IwConfig: enp3s0no wireless extensions. lono wireless extensions. MachineType: Dell Inc. G3 3579 ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed root=UUID=7b8b7532-3642-4369-bfeb-04208cf72efc ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-21-generic N/A linux-backports-modules-4.4.0-21-generic N/A linux-firmware1.157.19 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/25/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.0 dmi.board.name: 0JYXHN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.0:bd05/25/2018:svnDellInc.:pnG33579:pvr:rvnDellInc.:rn0JYXHN:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.name: G3 3579 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776376/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1776029] Re: Installer should not display "Install Now" when it's not the last step
** Package changed: linux (Ubuntu) => ubiquity (Ubuntu) ** Changed in: ubiquity (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/1776029 Title: Installer should not display "Install Now" when it's not the last step Status in ubiquity package in Ubuntu: New Bug description: See attachments. On step 2/3, when disk encryption is enabled, you enter the security key, and says "Install now". However, clicking on that button takes you to drive selection to install the distro, which shows also "Install now" and this is actually the good one. Please fix. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1776029/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1776113] Re: Laptop does not suspend when lid is closed
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 ** 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/1776113 Title: Laptop does not suspend when lid is closed Status in linux package in Ubuntu: New Bug description: $ lsb_release -rd Description: Ubuntu 18.04 LTS Release: 18.04 In Tweaks > Power, "Suspend when laptop lid is closed" is ON, but my laptop does not suspend when the lid is closed. The laptop is a Thinkpad P50. When closing the laptop lid, no events show up in dmesg. This is my /etc/systemd/login.conf: [Login] #NAutoVTs=6 #ReserveVT=6 #KillUserProcesses=no #KillOnlyUsers= #KillExcludeUsers=root #InhibitDelayMaxSec=5 #HandlePowerKey=poweroff #HandleSuspendKey=suspend #HandleHibernateKey=hibernate HandleLidSwitch=suspend HandleLidSwitchDocked=suspend #PowerKeyIgnoreInhibited=no #SuspendKeyIgnoreInhibited=no #HibernateKeyIgnoreInhibited=no #LidSwitchIgnoreInhibited=yes #HoldoffTimeoutSec=30s #IdleAction=ignore #IdleActionSec=30min #RuntimeDirectorySize=10% #RemoveIPC=yes #InhibitorsMax=8192 #SessionsMax=8192 #UserTasksMax=33% 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 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Jun 10 14:16:10 2018 InstallationDate: Installed on 2018-03-26 (76 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed UpgradeStatus: Upgraded to bionic on 2018-05-17 (24 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776113/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1775967] Re: Wrong temperature after suspend
Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem? Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.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 ** 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/1775967 Title: Wrong temperature after suspend Status in linux package in Ubuntu: Incomplete Bug description: My laptop's temperature is stuck at 40°C after resume from suspend, but only for the acpitz-virtual-0 sensor: soc_dts0-virtual-0 Adapter: Virtual device temp1:+71.0°C acpitz-virtual-0 Adapter: Virtual device temp1:+40.0°C (crit = +105.0°C) soc_dts1-virtual-0 Adapter: Virtual device temp1:+70.0°C coretemp-isa- Adapter: ISA adapter Core 0: +68.0°C (high = +105.0°C, crit = +105.0°C) Core 1: +68.0°C (high = +105.0°C, crit = +105.0°C) Core 2: +68.0°C (high = +105.0°C, crit = +105.0°C) Core 3: +68.0°C (high = +105.0°C, crit = +105.0°C) Before suspend, acpitz-virtual-0 displays the correct value, but after suspend it stays at 40°C forever, resulting in the fan to stay off all the time, and, thus, to the laptop overheating. 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 NonfreeKernelModules: nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: juloliv1700 F pulseaudio CurrentDesktop: GNOME Date: Sat Jun 9 07:50:16 2018 InstallationDate: Installed on 2018-05-14 (25 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Acer Aspire ES1-711G ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=fe1aba35-e7ba-460a-9b8d-96af3582d60d ro quiet splash scsi_mod.scan=sync RelatedPackageVersions: linux-restricted-modules-4.15.0-22-generic N/A linux-backports-modules-4.15.0-22-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/29/2015 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: EA70_BM dmi.board.vendor: Acer dmi.board.version: Type2 - A01 Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.07:bd07/29/2015:svnAcer:pnAspireES1-711G:pvrV1.07:rvnAcer:rnEA70_BM:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: BTM dmi.product.name: Aspire ES1-711G dmi.product.version: V1.07 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775967/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1776153] Re: package linux-headers-4.13.0-43 (not installed) failed to install/upgrade: unable to open '/usr/src/linux-headers-4.13.0-43/drivers/misc/genwqe/Makefile.dpkg-new':
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/1776153 Title: package linux-headers-4.13.0-43 (not installed) failed to install/upgrade: unable to open '/usr/src/linux- headers-4.13.0-43/drivers/misc/genwqe/Makefile.dpkg-new': Operation not permitted Status in linux package in Ubuntu: Incomplete Bug description: I am keep on getting pop up error message ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-headers-4.13.0-43 (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.15 Architecture: amd64 Date: Mon Jun 11 11:00:55 2018 DpkgHistoryLog: DuplicateSignature: package:linux-headers-4.13.0-43:(not installed) Unpacking linux-headers-4.13.0-43 (4.13.0-43.48~16.04.1) ... dpkg: error processing archive /var/cache/apt/archives/linux-headers-4.13.0-43_4.13.0-43.48~16.04.1_all.deb (--unpack): unable to open '/usr/src/linux-headers-4.13.0-43/drivers/misc/genwqe/Makefile.dpkg-new': Operation not permitted ErrorMessage: unable to open '/usr/src/linux-headers-4.13.0-43/drivers/misc/genwqe/Makefile.dpkg-new': Operation not permitted InstallationDate: Installed on 2017-10-26 (227 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.24 SourcePackage: linux-hwe Title: package linux-headers-4.13.0-43 (not installed) failed to install/upgrade: unable to open '/usr/src/linux-headers-4.13.0-43/drivers/misc/genwqe/Makefile.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/1776153/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1776443] Re: iwlwifi-29 kernel timeout queue active on fifo 2 and stuck
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 ** Changed in: linux-firmware (Ubuntu) Importance: Undecided => Medium ** Package changed: linux-firmware (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1776443 Title: iwlwifi-29 kernel timeout queue active on fifo 2 and stuck Status in linux package in Ubuntu: New Bug description: dell inspiron 15 3565 and intel 3165. Difficult to report when wifi is down! Happens sometimes after a few minutes, never more than 30 minutes. Easy to capture journalctl when the network connection hangs. Intel fails on 2.4 GHz or 5 GHz, using several different AP's. The same system runs stable and perfect with a USB dongle Realtek RTL8188CUS, but I have to blacklist iwlwifi in /etc/modprobe.d/modprobe.conf to prevent iwlwifi hanging all network activity while simply scanning and not connected to an AP. I've had similar problems with this system under 17.10, but it has become more reproducible under 18.04. I've back-levelled the driver as far as possible, but they all hang the network. Because version 29 firmware is the latest in the bionic repository, and also on the intel support web site, I won't confuse matters by reporting earlier ubuntu kernels or iwlwifi versions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776443/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1776443] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1776443 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1776443 Title: iwlwifi-29 kernel timeout queue active on fifo 2 and stuck Status in linux package in Ubuntu: Incomplete Bug description: dell inspiron 15 3565 and intel 3165. Difficult to report when wifi is down! Happens sometimes after a few minutes, never more than 30 minutes. Easy to capture journalctl when the network connection hangs. Intel fails on 2.4 GHz or 5 GHz, using several different AP's. The same system runs stable and perfect with a USB dongle Realtek RTL8188CUS, but I have to blacklist iwlwifi in /etc/modprobe.d/modprobe.conf to prevent iwlwifi hanging all network activity while simply scanning and not connected to an AP. I've had similar problems with this system under 17.10, but it has become more reproducible under 18.04. I've back-levelled the driver as far as possible, but they all hang the network. Because version 29 firmware is the latest in the bionic repository, and also on the intel support web site, I won't confuse matters by reporting earlier ubuntu kernels or iwlwifi versions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776443/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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'm wondering why not just adding the modules to the udebs, but I'm happy with this solution, too. ** Changed in: linux (Ubuntu Bionic) Status: Incomplete => New ** Changed in: linux (Ubuntu Cosmic) Status: Incomplete => New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/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: Incomplete Status in linux source package in Bionic: New Status in linux source package in Cosmic: Incomplete 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
Re: [Kernel-packages] [Bug 1773704] Re: Typo at line 184 in xhci-pci.c makes trouble for Renesas USB chipset in Bionic 18.04
Hey! This bug may be fixed.As best I recall I did a fresh install from nightly build about 3 days ago, but had not installed zoneminder so no op to tickle the bug. Today I did an upgrade and a dist-upgrade, then loaded zoneminder, started pulling data over renesas port, so far no dmesg errors, I think it's fixed. Did you fix it? Well blessings on whoever did. I'll let you know if it pops up again. Thank you so much On Tuesday, May 29, 2018, 1:11:03 PM PDT, Joseph Salisbury wrote: I built a patched test kernel. The test kernel can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1773704 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 subscribed to the bug report. https://bugs.launchpad.net/bugs/1773704 Title: Typo at line 184 in xhci-pci.c makes trouble for Renesas USB chipset in Bionic 18.04 Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: A typo at line 184 in /drivers/usb/host/xhci-pci.c trashes a good fix. 183 if (pdev->vendor == PCI_VENDOR_ID_RENESAS && 184 pdev->device == 0x0014) 185 xhci->quirks |= XHCI_TRUST_TX_LENGTH; 186 if (pdev->vendor == PCI_VENDOR_ID_RENESAS && 187 pdev->device == 0x0015) 188 xhci->quirks |= XHCI_RESET_ON_RESUME; Line 184 should be identical to line 187, ie: should read pdev->device == 0x0015) I've compiled the kernel both with and without the typo. As written, hundreds of messages fill dmesg suggesting XHCI_TRUST_TX_LENGTH may be needed when zoneminder tries to access my USB webcams. With the fix applied as I've suggested the messages disappear. The typo is still present in 4.15.0-22.24 For more background, you may refer to bug ID #1710548 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1773704/+subscriptions -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1773704 Title: Typo at line 184 in xhci-pci.c makes trouble for Renesas USB chipset in Bionic 18.04 Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: A typo at line 184 in /drivers/usb/host/xhci-pci.c trashes a good fix. 183 if (pdev->vendor == PCI_VENDOR_ID_RENESAS && 184 pdev->device == 0x0014) 185 xhci->quirks |= XHCI_TRUST_TX_LENGTH; 186 if (pdev->vendor == PCI_VENDOR_ID_RENESAS && 187 pdev->device == 0x0015) 188 xhci->quirks |= XHCI_RESET_ON_RESUME; Line 184 should be identical to line 187, ie: should read pdev->device == 0x0015) I've compiled the kernel both with and without the typo. As written, hundreds of messages fill dmesg suggesting XHCI_TRUST_TX_LENGTH may be needed when zoneminder tries to access my USB webcams. With the fix applied as I've suggested the messages disappear. The typo is still present in 4.15.0-22.24 For more background, you may refer to bug ID #1710548 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1773704/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1774950] Re: Suspend fails in Ubuntu and Kubuntu 18.04 but works fine in Ubuntu and Kubuntu 17.10 (and on Kubuntu 18.04 using kernel 4.14.47)
Anyone else experiencing this bug might also want to test out the kernel that @kaihengfeng has kindly put together with the patch from Rafael. It's in his post (#35) but here's the link: https://people.canonical.com/~khfeng/lp1774950/ It'll be interesting to check that it fixes suspend issues for other folks too. The only thing I've noticed so far is that it makes a weird click sound through the speakers as it goes into suspend (probably when it switches them off) but that is a small price to pay for a working suspend function! - I downloaded all the files, put them in a folder called KernelFix and then opened up a terminal. I changed directory ( cd /Downloads/KernelFix ) and then used sudo dpkg -i to install them. - I'm fairly incompetent so tried sudo dpkg -i linux-image- unsigned-4.15.0-24-generic_4.15.0-24.26~lp1774950_amd64.deb first which told me I needed to install the modules. - I installed both module .debs using sudo dpkg -i and then installed the kernel again just to be sure. Anyway, that seems to have worked for me and I'm now running Kubuntu 18.04 with a 4.15 kernel and suspend works fine! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1774950 Title: Suspend fails in Ubuntu and Kubuntu 18.04 but works fine in Ubuntu and Kubuntu 17.10 (and on Kubuntu 18.04 using kernel 4.14.47) Status in linux package in Ubuntu: Confirmed Bug description: I have installed Kubuntu 18.04 on 3 different machines (my friend's and my own) with no suspend problems but my HP Pavilion 11 x360 does not suspend. It suspends fine with Ubuntu 17.10, Kubuntu 17.10, Devuan Jesse, Devuan ASCII and Windows 10 but fails with Ubuntu 18.04 and Kubuntu 18.04. I have also tried suspend using a live USB of 18.04 on this machine and it fails in the same way, so does not appear to be caused by any additional programs that I had installed. By installing an older kernel (4.14) on Kubuntu 18.04 the suspend function works as expected. Running Kubuntu 18.04 with kernels 4.15, 4.16, 4.17 results in the suspend failure that freezes the machine and requires a hard reset. Correct behaviour is - Screen goes blank, fan goes off, power LED flashes to show machine is in suspend. Pressing power button triggers 'resume' function. What happens - Screen goes blank, fan stays on, power LED stays on. Machine stays in this state and does not respond to any keyboard interaction, mouse movement or power button presses. Ctrl + Alt + f1 (or f2, f3, f4 etc) does not get any response. The only way to use the machine is to shut down by holding down the power button. Checking the logs suggests that the machine believes it is in suspend mode sleep [deep] when it isn't. Having to hard reset to get any response means that the kernel logs say no more than sleep [deep] pm-suspend also results in the same problems with kernels 4.15 and 4.16, but works fine with 4.14. It is curious that a machine that suspends fine on an earlier 4.14 kernel no longer works with 4.15 and above, whilst 3 other machines (including one with pretty similar hardware) do not exhibit this problem. There are only a handful of questions about it on the forums but at least 3 other people have the same problem: https://askubuntu.com/questions/1029405/ubuntu-18-04-crashes-on- resuming-from-suspend https://askubuntu.com/questions/1041369/after-upgrading- from-17-10-ubuntu-18-04-wont-sleep-suspend I am attempting to round up anyone else with the same issue and point them to this bug report. My laptop is HP Pavilion x360 11-n013na Matalaks is Acer Aspire ES1-511 collisionTwo has XPS 9560 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774950/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1775477] Re: Xenial update to 4.4.133 stable release
4.4.131 includes "sctp: do not check port in sctp_inet6_cmp_addr" that
breaks combined AF_INET and AF_INET6 support in SCTP, it should be fixed
in 4.4.133 with "sctp: handle two v4 addrs comparison in
sctp_inet6_cmp_addr".
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1775477
Title:
Xenial update to 4.4.133 stable release
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Xenial:
Fix Committed
Bug description:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from a mainline/stable Linux tree or
a minimally backported form of that patch. The 4.4.133 upstream stable
patch set is now available. It should be included in the Ubuntu
kernel as well.
git://git.kernel.org/
TEST CASE: TBD
The following patches from the 4.4.133 stable release shall be applied:
* 8139too: Use disable_irq_nosync() in rtl8139_poll_controller()
* bridge: check iface upper dev when setting master via ioctl
* dccp: fix tasklet usage
* ipv4: fix memory leaks in udp_sendmsg, ping_v4_sendmsg
* llc: better deal with too small mtu
* net: ethernet: sun: niu set correct packet size in skb
* net/mlx4_en: Verify coalescing parameters are in range
* net_sched: fq: take care of throttled flows before reuse
* net: support compat 64-bit time in {s,g}etsockopt
* openvswitch: Don't swap table in nlattr_set() after OVS_ATTR_NESTED is found
* qmi_wwan: do not steal interfaces from class drivers
* r8169: fix powering up RTL8168h
* sctp: handle two v4 addrs comparison in sctp_inet6_cmp_addr
* sctp: use the old asoc when making the cookie-ack chunk in dupcook_d
* tg3: Fix vunmap() BUG_ON() triggered from tg3_free_consistent().
* bonding: do not allow rlb updates to invalid mac
* tcp: ignore Fast Open on repair mode
* sctp: fix the issue that the cookie-ack with auth can't get processed
* sctp: delay the authentication for the duplicated cookie-echo chunk
* ALSA: timer: Call notifier in the same spinlock
* audit: move calcs after alloc and check when logging set loginuid
* arm64: introduce mov_q macro to move a constant into a 64-bit register
* arm64: Add work around for Arm Cortex-A55 Erratum 1024718
* futex: Remove unnecessary warning from get_futex_key
* futex: Remove duplicated code and fix undefined behaviour
* xfrm: fix xfrm_do_migrate() with AEAD e.g(AES-GCM)
* lockd: lost rollback of set_grace_period() in lockd_down_net()
* Revert "ARM: dts: imx6qdl-wandboard: Fix audio channel swap"
* l2tp: revert "l2tp: fix missing print session offset info"
* pipe: cap initial pipe capacity according to pipe-max-size limit
* futex: futex_wake_op, fix sign_extend32 sign bits
* kernel/exit.c: avoid undefined behaviour when calling wait4()
* usbip: usbip_host: refine probe and disconnect debug msgs to be useful
* usbip: usbip_host: delete device from busid_table after rebind
* usbip: usbip_host: run rebind from exit when module is removed
* usbip: usbip_host: fix NULL-ptr deref and use-after-free errors
* usbip: usbip_host: fix bad unlock balance during stub_probe()
* ALSA: usb: mixer: volume quirk for CM102-A+/102S+
* ALSA: hda: Add Lenovo C50 All in one to the power_save blacklist
* ALSA: control: fix a redundant-copy issue
* spi: pxa2xx: Allow 64-bit DMA
* powerpc/powernv: panic() on OPAL < V3
* powerpc/powernv: Remove OPALv2 firmware define and references
* powerpc/powernv: remove FW_FEATURE_OPALv3 and just use FW_FEATURE_OPAL
* cpuidle: coupled: remove unused define cpuidle_coupled_lock
* powerpc: Don't preempt_disable() in show_cpuinfo()
* vmscan: do not force-scan file lru if its absolute size is small
* mm: filemap: remove redundant code in do_read_cache_page
* mm: filemap: avoid unnecessary calls to lock_page when waiting for IO to
complete
during a read
* signals: avoid unnecessary taking of sighand->siglock
* tracing/x86/xen: Remove zero data size trace events
trace_xen_mmu_flush_tlb{_all}
* proc read mm's {arg,env}_{start,end} with mmap semaphore taken.
* powerpc/powernv: Fix NVRAM sleep in invalid context when crashing
* mm: don't allow deferred pages with NEED_PER_CPU_KM
* s390/qdio: fix access to uninitialized qdio_q fields
* s390/qdio: don't release memory in qdio_setup_irq()
* s390: remove indirect branch from do_softirq_own_stack
* efi: Avoid potential crashes, fix the 'struct efi_pci_io_protocol_32'
definition
for mixed mode
* ARM: 8771/1: kprobes: Prohibit kprobes on do_undefinstr
* tick/broadcast: Use for_each_cpu() specially on UP kernels
* ARM: 8769/1: kprobes: Fix to use get_kprobe_ctlblk
[Kernel-packages] [Bug 1776005] Re: kernel instability with BTRFS filesystem as rootfs
I built a test kernel with a revert of commit 2f500a9d7ff6. The test kernel can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1776005 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/1776005 Title: kernel instability with BTRFS filesystem as rootfs Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Bug description: Hello, As explained yesterday on #ubuntu-kernel, several laptop won't boot (kernel panic) with the latest kernel 4.4.0-127-generic (x86_64) and upper (proposed 4.4.0-128-generic), on Xenial 16.04 LTS I have made many tests to verify that the bootloader (GRUB) is correctly configured (I have also reinstall it, but same result). I have also verified the BTRFS system is clean and not corrupted (with a livecd). The behavior is unpredictable, because often the kernel fall in "panic" during boot, but not all the time, if i do several consecutive reboot to test stability of the boot "process". I have no search behavior with previous kernels (like 4.4.0-124-generic). I suspect (even if I'm quiet disturbed by this behavior, maybe I wrong) that something I changed on last kernel: - on BTRFS subsystem, I have "aggregate" BTRFS partitions as rootfs (for a long time) - something related with the last mitigation about the recent security processor breach But my skills stop here, and I'm not able to find the origin of this behavior despite my efforts. I can continue my investigation if I have some additional pointers. Thanks for your time, Sylvain To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776005/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
hi, I just updated to 18.04 today and have started to see this message on
reboot.
I am also on an HP DL380 Gen9.
It looks like everything has already been found :).
Pardon me for asking, but how long does a fix like this (ballpark
estimate) usually take to get into an OS update?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/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
[Kernel-packages] [Bug 1776153] [NEW] package linux-headers-4.13.0-43 (not installed) failed to install/upgrade: unable to open '/usr/src/linux-headers-4.13.0-43/drivers/misc/genwqe/Makefile.dpkg-new'
You have been subscribed to a public bug: I am keep on getting pop up error message ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-headers-4.13.0-43 (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.15 Architecture: amd64 Date: Mon Jun 11 11:00:55 2018 DpkgHistoryLog: DuplicateSignature: package:linux-headers-4.13.0-43:(not installed) Unpacking linux-headers-4.13.0-43 (4.13.0-43.48~16.04.1) ... dpkg: error processing archive /var/cache/apt/archives/linux-headers-4.13.0-43_4.13.0-43.48~16.04.1_all.deb (--unpack): unable to open '/usr/src/linux-headers-4.13.0-43/drivers/misc/genwqe/Makefile.dpkg-new': Operation not permitted ErrorMessage: unable to open '/usr/src/linux-headers-4.13.0-43/drivers/misc/genwqe/Makefile.dpkg-new': Operation not permitted InstallationDate: Installed on 2017-10-26 (227 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.24 SourcePackage: linux-hwe Title: package linux-headers-4.13.0-43 (not installed) failed to install/upgrade: unable to open '/usr/src/linux-headers-4.13.0-43/drivers/misc/genwqe/Makefile.dpkg-new': Operation not permitted UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux (Ubuntu) Importance: Medium Status: Incomplete ** Tags: amd64 apport-package xenial -- package linux-headers-4.13.0-43 (not installed) failed to install/upgrade: unable to open '/usr/src/linux-headers-4.13.0-43/drivers/misc/genwqe/Makefile.dpkg-new': Operation not permitted https://bugs.launchpad.net/bugs/1776153 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1776389] Re: [Ubuntu 1804][boston][ixgbe] EEH causes kernel BUG at /build/linux-jWa1Fv/linux-4.15.0/drivers/pci/msi.c:352 (i2S)
** Changed in: linux (Ubuntu) Status: New => Triaged ** 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/1776389 Title: [Ubuntu 1804][boston][ixgbe] EEH causes kernel BUG at /build/linux- jWa1Fv/linux-4.15.0/drivers/pci/msi.c:352 (i2S) Status in The Ubuntu-power-systems project: Triaged Status in linux package in Ubuntu: Triaged Bug description: == Comment: #0 - ABDUL HALEEM <> - 2018-02-16 08:26:15 == Problem: Injecting error multiple times causes kernel crash. echo 0x0:1:4:0x60800:0xfff8 > /sys/kernel/debug/powerpc/PCI/err_injct EEH: PHB#0 failure detected, location: N/A EEH: PHB#0-PE#0 has failed 6 times in the last hour and has been permanently disabled. EEH: Unable to recover from failure from PHB#0-PE#0. Please try reseating or replacing it ixgbe :01:00.1: Adapter removed kernel BUG at /build/linux-jWa1Fv/linux-4.15.0/drivers/pci/msi.c:352! Oops: Exception in kernel mode, sig: 5 [#1] LE SMP NR_CPUS=2048 NUMA PowerNV Modules linked in: rpcsec_gss_krb5 nfsv4 nfs fscache joydev input_leds mac_hid idt_89hpesx ofpart ipmi_powernv cmdlinepart ipmi_devintf ipmi_msghandler at24 powernv_flash mtd opal_prd ibmpowernv uio_pdrv_genirq vmx_crypto uio sch_fq_codel nfsd auth_rpcgss nfs_acl lockd grace sunrpc 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 async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear ses enclosure scsi_transport_sas qla2xxx ast hid_generic ttm drm_kms_helper ixgbe syscopyarea usbhid igb sysfillrect sysimgblt nvme_fc fb_sys_fops hid nvme_fabrics crct10dif_vpmsum crc32c_vpmsum drm i40e scsi_transport_fc aacraid i2c_algo_bit mdio CPU: 28 PID: 972 Comm: eehd Not tainted 4.15.0-10-generic #11-Ubuntu NIP: c077f080 LR: c077f070 CTR: c00aac30 REGS: c00ff1deb5a0 TRAP: 0700 Not tainted (4.15.0-10-generic) MSR: 90029033 CR: 24002822 XER: 2004 CFAR: c018bddc SOFTE: 1 GPR00: c077f070 c00ff1deb820 c16ea600 c00fbb5fac00 GPR04: 02c5 GPR08: c00fbb5fac00 0001 c00fec617a00 c00fdfd86488 GPR12: 0040 c7a33400 c0138be8 c00ff90ec1c0 GPR16: GPR20: c0f48d10 GPR24: c0f48ce8 c000200e4fcf4000 c00fc6900b18 c000200e4fcf4000 GPR28: c000200e4fcf4288 c00810624480 c00fbb633ea0 NIP [c077f080] free_msi_irqs+0xa0/0x260 LR [c077f070] free_msi_irqs+0x90/0x260 Call Trace: [c00ff1deb820] [c077f070] free_msi_irqs+0x90/0x260 (unreliable) [c00ff1deb880] [c077fa68] pci_disable_msix+0x128/0x170 [c00ff1deb8c0] [c0081060b5c8] ixgbe_reset_interrupt_capability+0x90/0xd0 [ixgbe] [c00ff1deb8f0] [c008105d52f4] ixgbe_remove+0xec/0x240 [ixgbe] [c00ff1deb990] [c07670ec] pci_device_remove+0x6c/0x110 [c00ff1deb9d0] [c085d194] device_release_driver_internal+0x224/0x310 [c00ff1deba20] [c075b398] pci_stop_bus_device+0x98/0xe0 [c00ff1deba60] [c075b588] pci_stop_and_remove_bus_device+0x28/0x40 [c00ff1deba90] [c005e1d0] pci_hp_remove_devices+0x90/0x130 [c00ff1debb20] [c005e184] pci_hp_remove_devices+0x44/0x130 [c00ff1debbb0] [c003ec04] eeh_handle_normal_event+0x134/0x580 [c00ff1debc60] [c003f160] eeh_handle_event+0x30/0x338 [c00ff1debd10] [c003f830] eeh_event_handler+0x140/0x200 [c00ff1debdc0] [c0138d88] kthread+0x1a8/0x1b0 [c00ff1debe30] [c000b528] ret_from_kernel_thread+0x5c/0xb4 Instruction dump: 419effe0 3bc0 480c 6042 807f0010 7c7e1a14 78630020 4ba0cd3d 6000 e9430158 312a 7d295110 <0b09> 813f0014 395e0001 7d5e07b4 ---[ end trace 23c446a470e60864 ]--- ixgbe :01:00.0: Adapter removed Sending IPI to other CPUs OPAL: Switch to big-endian OS OPAL: Switch to little-endian OS PHB#[0:0]: eeh_freeze_clear on fenced PHB ---uname output--- Linux ltciofvtr-bostonlc1 4.15.0-10-generic #11-Ubuntu SMP Tue Feb 13 18:21:52 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux Machine Type = Boston-LC :00:00.0 PCI bridge [0604]: IBM Device [1014:04c1] :01:00.0 Ethernet controller [0200]: Intel Corporation 82599ES 10-Gigabit SFI/SFP+ Network Connection [8086:10fb] (rev 01) :01:00.1 Ethernet controller [0200]: Intel Corporation 82599ES 10-Gigabit SFI/SFP+ Network
[Kernel-packages] [Bug 1775945] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1775945 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1775945 Title: Lenovi X1 Carbon regularly has frozen lock- or dark screen after closing lid Status in linux package in Ubuntu: Incomplete Bug description: I was running ubuntu 17.10 for months with no issues. After upgrading to 18.04, closing the lid regularly (but not always) results in either: 1. The display staying on with a frozen lock-screen, or 2. The display powered off, but the notebook still powered on. In both cases the notebook does not respond. A five-second press of the power button to hard-reboot the computer is the only means of recovery. After powering the notebook back on, there are no files in /var/crash. 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.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Jun 9 00:00:48 2018 InstallationDate: Installed on 2018-06-02 (6 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/1775945/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1775717] Re: CPU/GPU Fans suddenly go 100% RPM on Asus ROG G752VT
Well, the fans just went 100% on kernel 4.4.14-040414-generic after about a day
of normal operation.
Any advice on what other information to collect?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1775717
Title:
CPU/GPU Fans suddenly go 100% RPM on Asus ROG G752VT
Status in linux package in Ubuntu:
Incomplete
Bug description:
After upgrading from Ubuntu 16.04 to 18.04, I've noticed that CPU and
GPU fans suddenly go full throttle. It doesn't seem to depend on
temperature, could happen when 32 °C reported, sometimes the laptop
can work for day or two without this issue, but eventually it happens.
The only way to stop fans is to power off the laptop, power on (fans
go 100% at this point again), power off during BIOS splash screen and
power on again. Seems to happen more often after waking up from a
sleep.
Things tried:
Upgrading BIOS to latest available on ASUS site to the date of
writing. No change.
asus-fan kernel module (https://github.com/daringer/asus-fan). Detects
both fans and shows correct speed in /sys/class/hwmon/*/fan{1,2}*, but
does not seem to control it and does not prevent going full throttle.
4.17.0 kernel from Ubuntu mainline builds. Doesn't seem to affect the
issue.
Userspace fan control software (https://github.com/hirschmann/nbfc).
Can control speed of both fans to the point where they go full
throttle, after that has no effect on them.
System info:
$ lsb_release -rd
Description: Ubuntu 18.04 LTS
Release: 18.04
$ cat /proc/version
Linux version 4.17.0-041700-generic (kernel@kathleen) (gcc version 7.3.0
(Ubuntu 7.3.0-20ubuntu1)) #201806041953 SMP Mon Jun 4 19:55:25 UTC 2018
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775717/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1776352] Re: linux: 4.4.0-129.155 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed ** Tags added: block-proposed-xenial ** Tags added: block-proposed ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1776353 (linux-aws), bug 1776355 (linux-lts-xenial) derivatives: bug 1776356 (linux-aws), bug 1776357 (linux-euclid), bug 1776358 (linux-kvm), bug 1776359 (linux-raspi2), bug 1776361 (linux-snapdragon) kernel-stable-phase:Uploaded kernel-stable-phase-changed:Tuesday, 12. June 2018 10:34 UTC -- swm properties -- + boot-testing-requested: true phase: Uploaded -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1776352 Title: linux: 4.4.0-129.155 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-certification-testing series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1776353 (linux-aws), bug 1776355 (linux-lts-xenial) derivatives: bug 1776356 (linux-aws), bug 1776357 (linux-euclid), bug 1776358 (linux-kvm), bug 1776359 (linux-raspi2), bug 1776361 (linux-snapdragon) kernel-stable-phase:Uploaded kernel-stable-phase-changed:Tuesday, 12. June 2018 10:34 UTC -- swm properties -- boot-testing-requested: true phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1776352/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1776333] Re: linux: 4.13.0-46.51 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz Zemczak (sil2100) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1776333 Title: linux: 4.13.0-46.51 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: In Progress Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Artful: New Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1776335 (linux-gcp), bug 1776336 (linux-hwe), bug 1776337 (linux-oem) derivatives: bug 1776334 (linux-raspi2) kernel-stable-phase-changed:Tuesday, 12. June 2018 13:00 UTC kernel-stable-phase:Uploaded -- swm properties -- boot-testing-requested: true phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1776333/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1770095] Comment bridged from LTC Bugzilla
--- Comment From dougm...@us.ibm.com 2018-06-12 16:13 EDT--- We don't see the panic anymore, with the test 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/1770095 Title: Need fix to aacraid driver to prevent panic 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 - Douglas Miller - 2018-05-08 15:45:13 == +++ This bug was initially created as a clone of Bug #167565 +++ A recent commit to aacraid (b60710ec7d7ab1ca277b458338563ac21b393906) introduced a bug whereby a panic may happen under certain recovery situations. The following commit fixes that: https://git.kernel.org/pub/scm/linux/kernel/git/jejb/scsi.git/commit/?h=fixes=7d3af7d96af7b9f51e1ef67b6f4725f545737da2 We need this commit backported to Ubuntu 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1770095/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1776407] Re: intel_do_flush_locked failed:Bad address
The 4.10 kernel is no longer supported in an Ubuntu release. Can you see if this bug still happens with 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/1776407 Title: intel_do_flush_locked failed:Bad address Status in linux package in Ubuntu: Incomplete Bug description: when my app run on about 3 days, it exits and throws error info: "intel_do_flush_locked failed:bad address". this information is throwed by OpenGL(mesa). relations: app -> SDL -> OpenGL(mesa) -> libdrm -> kernel frequency: often kernel version:Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17GNU/Linux meas version: 17.2.8 libdrm : 2.4.83 I think it is a kernel bug because the bad address is meaning error code "-EFALUT". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776407/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1776005] Re: kernel instability with BTRFS filesystem as rootfs
** Changed in: linux (Ubuntu) Importance: Undecided => High ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Status: New => In Progress ** Changed in: linux (Ubuntu) Status: Incomplete => In Progress ** Changed in: linux (Ubuntu Xenial) Importance: Undecided => High ** Changed in: linux (Ubuntu Xenial) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) ** Changed in: linux (Ubuntu) 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/1776005 Title: kernel instability with BTRFS filesystem as rootfs Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Bug description: Hello, As explained yesterday on #ubuntu-kernel, several laptop won't boot (kernel panic) with the latest kernel 4.4.0-127-generic (x86_64) and upper (proposed 4.4.0-128-generic), on Xenial 16.04 LTS I have made many tests to verify that the bootloader (GRUB) is correctly configured (I have also reinstall it, but same result). I have also verified the BTRFS system is clean and not corrupted (with a livecd). The behavior is unpredictable, because often the kernel fall in "panic" during boot, but not all the time, if i do several consecutive reboot to test stability of the boot "process". I have no search behavior with previous kernels (like 4.4.0-124-generic). I suspect (even if I'm quiet disturbed by this behavior, maybe I wrong) that something I changed on last kernel: - on BTRFS subsystem, I have "aggregate" BTRFS partitions as rootfs (for a long time) - something related with the last mitigation about the recent security processor breach But my skills stop here, and I'm not able to find the origin of this behavior despite my efforts. I can continue my investigation if I have some additional pointers. Thanks for your time, Sylvain To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776005/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1776155] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1776155 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1776155 Title: Hantick HTT5288 touchpad wrongly detected as SYNA3602, does not work at all. Status in linux package in Ubuntu: Incomplete Bug description: On my cheaper-end laptop/netbook the touchpad, which I believe is the Hantick HT 5288, is wrongly detected by Linux to be the SYNA 3602. Accordingly it does not work at all, neither touchpad nor buttons. Freshly installed Ubuntu 18.04 system. I belive the issue is, as reported previously other places by vendors of such computers, that the touchpad is not being reset properly on boot. martin@alanah:~$ cat /proc/bus/input/devices I: Bus=0019 Vendor= Product=0005 Version= N: Name="Lid Switch" P: Phys=PNP0C0D/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:13/PNP0C09:00/PNP0C0D:00/input/input0 U: Uniq= H: Handlers=event0 B: PROP=0 B: EV=21 B: SW=1 I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=PNP0C0C/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input1 U: Uniq= H: Handlers=kbd event1 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0011 Vendor=0001 Product=0001 Version=ab83 N: Name="AT Translated Set 2 keyboard" P: Phys=isa0060/serio0/input0 S: Sysfs=/devices/platform/i8042/serio0/input/input2 U: Uniq= H: Handlers=sysrq kbd event2 leds B: PROP=0 B: EV=120013 B: KEY=40200 3803078f800d001 fedfffef fffe B: MSC=10 B: LED=7 I: Bus=0019 Vendor= Product=0006 Version= N: Name="Video Bus" P: Phys=LNXVIDEO/video/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input3 U: Uniq= H: Handlers=kbd event3 B: PROP=0 B: EV=3 B: KEY=3e000b 0 0 0 I: Bus=0019 Vendor= Product= Version= N: Name="Intel HID events" P: Phys= S: Sysfs=/devices/platform/INT33D5:00/input/input4 U: Uniq= H: Handlers=rfkill kbd event4 B: PROP=0 B: EV=13 B: KEY=810003 504000 1e29400020 0 B: MSC=10 I: Bus=0019 Vendor= Product= Version= N: Name="Intel HID 5 button array" P: Phys= S: Sysfs=/devices/platform/INT33D5:00/input/input5 U: Uniq= H: Handlers=kbd event5 B: PROP=0 B: EV=33 B: KEY=1 0 201c 0 B: MSC=10 B: SW=1000 I: Bus=0003 Vendor=058f Product=5608 Version=0009 N: Name="VGA Webcam: VGA Webcam" P: Phys=usb-:00:15.0-8/button S: Sysfs=/devices/pci:00/:00:15.0/usb1/1-8/1-8:1.0/input/input6 U: Uniq= H: Handlers=kbd event6 B: PROP=0 B: EV=3 B: KEY=10 0 0 0 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH Mic" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:0e.0/sound/card0/input7 U: Uniq= H: Handlers=event7 B: PROP=0 B: EV=21 B: SW=10 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH Headphone" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:0e.0/sound/card0/input8 U: Uniq= H: Handlers=event8 B: PROP=0 B: EV=21 B: SW=4 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=3" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:0e.0/sound/card0/input9 U: Uniq= H: Handlers=event9 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=7" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:0e.0/sound/card0/input10 U: Uniq= H: Handlers=event10 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=8" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:0e.0/sound/card0/input11 U: Uniq= H: Handlers=event11 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=9" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:0e.0/sound/card0/input12 U: Uniq= H: Handlers=event12 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=10" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:0e.0/sound/card0/input13 U: Uniq= H:
[Kernel-packages] [Bug 1771823] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1771823 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/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: Incomplete Status in linux source package in Bionic: New Status in linux source package in Cosmic: Incomplete 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 1707875] Comment bridged from LTC Bugzilla
--- Comment From pac...@us.ibm.com 2018-06-12 08:29 EDT--- What are the expectations for resolving this issue? Is there a plan? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1707875 Title: [18.04] include support for Python bindings in "perf" Status in The Ubuntu-power-systems project: Fix Committed Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Bug description: == Comment: #0 - Paul A. Clarke - 2017-07-26 09:59:57 == ---Problem Description--- Request to build python bindings support with perf. ---Steps to Reproduce--- Ubuntu-17.04# perf script -g python Python scripting not supported. Install libpython and rebuild perf to enable it. For example: # apt-get install python-dev (ubuntu) # yum install python-devel (Fedora) etc. Userspace tool common name: perf Userspace rpm: linux-tools-common Userspace tool obtained from project website: na == Comment: #2 - MAMATHA INAMDAR - 2017-08-01 05:02:34 == After installing libpython, downloaded ubuntu 17.04 linux source code and compiled perf tool then it works fine. # ./perf script -g python generated Python script: perf-script.py but when I run perf tool without rebuilding after installing libpython it shows an error # perf script -g python Python scripting not supported. Install libpython and rebuild perf to enable it. For example: # apt-get install python-dev (ubuntu) # yum install python-devel (Fedora) etc. root@p8wookie:/home/Mamatha/ubuntu/ubuntu-zesty/tools/perf# perf --version perf version 4.10.17 == Comment: #3 - MAMATHA INAMDAR - 2017-08-01 05:03:44 == Request to build python bindings support with perf. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1707875/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1776337] Re: linux-oem: -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: New => Confirmed ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1776333 + kernel-stable-phase-changed:Tuesday, 12. June 2018 13:01 UTC + kernel-stable-phase:Packaging ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1776333 - kernel-stable-phase-changed:Tuesday, 12. June 2018 13:01 UTC - kernel-stable-phase:Packaging + phase: Packaging -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1776337 Title: linux-oem: -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Confirmed Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow prepare-package-signed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-oem package in Ubuntu: Invalid Status in linux-oem source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1776333 phase: Packaging To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1776337/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1776389] Comment bridged from LTC Bugzilla
--- Comment From maur...@br.ibm.com 2018-06-12 08:59 EDT--- I've just sent the fix for the kernel mail list review: https://lists.ubuntu.com/archives/kernel-team/2018-June/093281.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/1776389 Title: [Ubuntu 1804][boston][ixgbe] EEH causes kernel BUG at /build/linux- jWa1Fv/linux-4.15.0/drivers/pci/msi.c:352 (i2S) Status in The Ubuntu-power-systems project: Triaged Status in linux package in Ubuntu: New Bug description: == Comment: #0 - ABDUL HALEEM <> - 2018-02-16 08:26:15 == Problem: Injecting error multiple times causes kernel crash. echo 0x0:1:4:0x60800:0xfff8 > /sys/kernel/debug/powerpc/PCI/err_injct EEH: PHB#0 failure detected, location: N/A EEH: PHB#0-PE#0 has failed 6 times in the last hour and has been permanently disabled. EEH: Unable to recover from failure from PHB#0-PE#0. Please try reseating or replacing it ixgbe :01:00.1: Adapter removed kernel BUG at /build/linux-jWa1Fv/linux-4.15.0/drivers/pci/msi.c:352! Oops: Exception in kernel mode, sig: 5 [#1] LE SMP NR_CPUS=2048 NUMA PowerNV Modules linked in: rpcsec_gss_krb5 nfsv4 nfs fscache joydev input_leds mac_hid idt_89hpesx ofpart ipmi_powernv cmdlinepart ipmi_devintf ipmi_msghandler at24 powernv_flash mtd opal_prd ibmpowernv uio_pdrv_genirq vmx_crypto uio sch_fq_codel nfsd auth_rpcgss nfs_acl lockd grace sunrpc 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 async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear ses enclosure scsi_transport_sas qla2xxx ast hid_generic ttm drm_kms_helper ixgbe syscopyarea usbhid igb sysfillrect sysimgblt nvme_fc fb_sys_fops hid nvme_fabrics crct10dif_vpmsum crc32c_vpmsum drm i40e scsi_transport_fc aacraid i2c_algo_bit mdio CPU: 28 PID: 972 Comm: eehd Not tainted 4.15.0-10-generic #11-Ubuntu NIP: c077f080 LR: c077f070 CTR: c00aac30 REGS: c00ff1deb5a0 TRAP: 0700 Not tainted (4.15.0-10-generic) MSR: 90029033 CR: 24002822 XER: 2004 CFAR: c018bddc SOFTE: 1 GPR00: c077f070 c00ff1deb820 c16ea600 c00fbb5fac00 GPR04: 02c5 GPR08: c00fbb5fac00 0001 c00fec617a00 c00fdfd86488 GPR12: 0040 c7a33400 c0138be8 c00ff90ec1c0 GPR16: GPR20: c0f48d10 GPR24: c0f48ce8 c000200e4fcf4000 c00fc6900b18 c000200e4fcf4000 GPR28: c000200e4fcf4288 c00810624480 c00fbb633ea0 NIP [c077f080] free_msi_irqs+0xa0/0x260 LR [c077f070] free_msi_irqs+0x90/0x260 Call Trace: [c00ff1deb820] [c077f070] free_msi_irqs+0x90/0x260 (unreliable) [c00ff1deb880] [c077fa68] pci_disable_msix+0x128/0x170 [c00ff1deb8c0] [c0081060b5c8] ixgbe_reset_interrupt_capability+0x90/0xd0 [ixgbe] [c00ff1deb8f0] [c008105d52f4] ixgbe_remove+0xec/0x240 [ixgbe] [c00ff1deb990] [c07670ec] pci_device_remove+0x6c/0x110 [c00ff1deb9d0] [c085d194] device_release_driver_internal+0x224/0x310 [c00ff1deba20] [c075b398] pci_stop_bus_device+0x98/0xe0 [c00ff1deba60] [c075b588] pci_stop_and_remove_bus_device+0x28/0x40 [c00ff1deba90] [c005e1d0] pci_hp_remove_devices+0x90/0x130 [c00ff1debb20] [c005e184] pci_hp_remove_devices+0x44/0x130 [c00ff1debbb0] [c003ec04] eeh_handle_normal_event+0x134/0x580 [c00ff1debc60] [c003f160] eeh_handle_event+0x30/0x338 [c00ff1debd10] [c003f830] eeh_event_handler+0x140/0x200 [c00ff1debdc0] [c0138d88] kthread+0x1a8/0x1b0 [c00ff1debe30] [c000b528] ret_from_kernel_thread+0x5c/0xb4 Instruction dump: 419effe0 3bc0 480c 6042 807f0010 7c7e1a14 78630020 4ba0cd3d 6000 e9430158 312a 7d295110 <0b09> 813f0014 395e0001 7d5e07b4 ---[ end trace 23c446a470e60864 ]--- ixgbe :01:00.0: Adapter removed Sending IPI to other CPUs OPAL: Switch to big-endian OS OPAL: Switch to little-endian OS PHB#[0:0]: eeh_freeze_clear on fenced PHB ---uname output--- Linux ltciofvtr-bostonlc1 4.15.0-10-generic #11-Ubuntu SMP Tue Feb 13 18:21:52 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux Machine Type = Boston-LC :00:00.0 PCI bridge [0604]: IBM Device [1014:04c1] :01:00.0 Ethernet controller [0200]: Intel Corporation 82599ES 10-Gigabit SFI/SFP+ Network Connection [8086:10fb] (rev 01) :01:00.1 Ethernet controller [0200]:
[Kernel-packages] [Bug 1776335] Re: linux-gcp: 4.13.0-1020.24 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Released ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1776333 + kernel-stable-phase:Uploaded + kernel-stable-phase-changed:Tuesday, 12. June 2018 14:01 UTC ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1776333 - kernel-stable-phase:Uploaded - kernel-stable-phase-changed:Tuesday, 12. June 2018 14:01 UTC + phase: Uploaded -- 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/1776335 Title: linux-gcp: 4.13.0-1020.24 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1776333 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1776335/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1776491] Re: linux-snapdragon: wcn36xx: mac address generation on boot
** Patch added: "0001-SAUCE-wcn36xx-read-MAC-from-file-or-randomly-generat.patch" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776491/+attachment/5151767/+files/0001-SAUCE-wcn36xx-read-MAC-from-file-or-randomly-generat.patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1776491 Title: linux-snapdragon: wcn36xx: mac address generation on boot Status in linux package in Ubuntu: Incomplete Bug description: Impact: The wcn36xx driver in Xenial/linux-snapdragon had an ability to autogenerate its MAC address upon boot, or read it from a file (/lib/firmware/wlan/macaddr0). The linux-snapdragon kernel in Bionic doesn't have this feature. While by itself not a bug (Xenial used a QCOM provided custom driver, while Bionic uses the upstream wcn36xx driver), it can be easily work- arounded by specifying the hw address in /etc/network/interfaces, or set using ifconfig on the command line, but it turned out to be a real problem on ubuntu core: 1) upon boot, with no MAC address assigned, the wcn36xx assigns itself the dummy address "00:00:00:00:00" and that prevents the network interface from working at all, until a valid address is set 2) the ubuntu core installer doesn't have any knowledge about this behaviour, it simply tries to bring up the interface and on failure, it marks it as 'not working' On top of that, ubuntu core ships a small script in initramfs, that generates the /lib/firmware/wlan/macaddr0 file starting from the android boot serial, effectively generating a unique MAC address per board: clearly, without driver support, this ubuntu core feature doesn't work. Fix: Import back the MAC generation mechanism from Xenial: the pseudo random generation and the parsing of /lib/firmware/wlan/macaddr0 - see the attached patch. How to test: Unpon boot, if no /lib/firmware/wlan/macaddr0 is present, the kernel will print: [ 10.612701] wcn36xx a204000.wcnss:smd-edge:wcnss:wifi: Direct firmware load for wlan/macaddr0 failed with error -2 [ 10.612713] wcn36xx a204000.wcnss:smd-edge:wcnss:wifi: Failed (-2) to read macaddressfile wlan/macaddr0, using a random address instead ubuntu@dragon410c:~$ ifconfig wlan0 wlan0: flags=4098 mtu 1500 ether 00:0a:f5:d5:54:d7 txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 else, if /lib/firmware/wlan/macaddr0 is present, its content will be used to generate wlan0 MAC address: ubuntu@dragon410c:~$ cat /lib/firmware/wlan/macaddr0 fe:1a:19:77:d9:88 ubuntu@dragon410c:~$ ifconfig wlan0 wlan0: flags=4098 mtu 1500 ether fe:1a:19:77:d9:88 txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 Regression potential: Low - the patch is small and the code is wrapped in a Kconfig option (WCN36XX_SNAPDRAGON_HACKS) that only affects the linux-snapdragon flavour, leaving the generic kernel untouched. --- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776491/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1776491] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1776491 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1776491 Title: linux-snapdragon: wcn36xx: mac address generation on boot Status in linux package in Ubuntu: Incomplete Bug description: Impact: The wcn36xx driver in Xenial/linux-snapdragon had an ability to autogenerate its MAC address upon boot, or read it from a file (/lib/firmware/wlan/macaddr0). The linux-snapdragon kernel in Bionic doesn't have this feature. While by itself not a bug (Xenial used a QCOM provided custom driver, while Bionic uses the upstream wcn36xx driver), it can be easily work- arounded by specifying the hw address in /etc/network/interfaces, or set using ifconfig on the command line, but it turned out to be a real problem on ubuntu core: 1) upon boot, with no MAC address assigned, the wcn36xx assigns itself the dummy address "00:00:00:00:00" and that prevents the network interface from working at all, until a valid address is set 2) the ubuntu core installer doesn't have any knowledge about this behaviour, it simply tries to bring up the interface and on failure, it marks it as 'not working' On top of that, ubuntu core ships a small script in initramfs, that generates the /lib/firmware/wlan/macaddr0 file starting from the android boot serial, effectively generating a unique MAC address per board: clearly, without driver support, this ubuntu core feature doesn't work. Fix: Import back the MAC generation mechanism from Xenial: the pseudo random generation and the parsing of /lib/firmware/wlan/macaddr0 - see the attached patch. How to test: Unpon boot, if no /lib/firmware/wlan/macaddr0 is present, the kernel will print: [ 10.612701] wcn36xx a204000.wcnss:smd-edge:wcnss:wifi: Direct firmware load for wlan/macaddr0 failed with error -2 [ 10.612713] wcn36xx a204000.wcnss:smd-edge:wcnss:wifi: Failed (-2) to read macaddressfile wlan/macaddr0, using a random address instead ubuntu@dragon410c:~$ ifconfig wlan0 wlan0: flags=4098 mtu 1500 ether 00:0a:f5:d5:54:d7 txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 else, if /lib/firmware/wlan/macaddr0 is present, its content will be used to generate wlan0 MAC address: ubuntu@dragon410c:~$ cat /lib/firmware/wlan/macaddr0 fe:1a:19:77:d9:88 ubuntu@dragon410c:~$ ifconfig wlan0 wlan0: flags=4098 mtu 1500 ether fe:1a:19:77:d9:88 txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 Regression potential: Low - the patch is small and the code is wrapped in a Kconfig option (WCN36XX_SNAPDRAGON_HACKS) that only affects the linux-snapdragon flavour, leaving the generic kernel untouched. --- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776491/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1776335] Re: linux-gcp: 4.13.0-1020.24 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Released -- 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/1776335 Title: linux-gcp: 4.13.0-1020.24 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1776333 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1776335/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1774950] Re: Suspend fails in Ubuntu and Kubuntu 18.04 but works fine in Ubuntu and Kubuntu 17.10 (and on Kubuntu 18.04 using kernel 4.14.47)
pHeLiOn, please try the kernel here. It includes the patch from Rafael. https://people.canonical.com/~khfeng/lp1774950/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1774950 Title: Suspend fails in Ubuntu and Kubuntu 18.04 but works fine in Ubuntu and Kubuntu 17.10 (and on Kubuntu 18.04 using kernel 4.14.47) Status in linux package in Ubuntu: Confirmed Bug description: I have installed Kubuntu 18.04 on 3 different machines (my friend's and my own) with no suspend problems but my HP Pavilion 11 x360 does not suspend. It suspends fine with Ubuntu 17.10, Kubuntu 17.10, Devuan Jesse, Devuan ASCII and Windows 10 but fails with Ubuntu 18.04 and Kubuntu 18.04. I have also tried suspend using a live USB of 18.04 on this machine and it fails in the same way, so does not appear to be caused by any additional programs that I had installed. By installing an older kernel (4.14) on Kubuntu 18.04 the suspend function works as expected. Running Kubuntu 18.04 with kernels 4.15, 4.16, 4.17 results in the suspend failure that freezes the machine and requires a hard reset. Correct behaviour is - Screen goes blank, fan goes off, power LED flashes to show machine is in suspend. Pressing power button triggers 'resume' function. What happens - Screen goes blank, fan stays on, power LED stays on. Machine stays in this state and does not respond to any keyboard interaction, mouse movement or power button presses. Ctrl + Alt + f1 (or f2, f3, f4 etc) does not get any response. The only way to use the machine is to shut down by holding down the power button. Checking the logs suggests that the machine believes it is in suspend mode sleep [deep] when it isn't. Having to hard reset to get any response means that the kernel logs say no more than sleep [deep] pm-suspend also results in the same problems with kernels 4.15 and 4.16, but works fine with 4.14. It is curious that a machine that suspends fine on an earlier 4.14 kernel no longer works with 4.15 and above, whilst 3 other machines (including one with pretty similar hardware) do not exhibit this problem. There are only a handful of questions about it on the forums but at least 3 other people have the same problem: https://askubuntu.com/questions/1029405/ubuntu-18-04-crashes-on- resuming-from-suspend https://askubuntu.com/questions/1041369/after-upgrading- from-17-10-ubuntu-18-04-wont-sleep-suspend I am attempting to round up anyone else with the same issue and point them to this bug report. My laptop is HP Pavilion x360 11-n013na Matalaks is Acer Aspire ES1-511 collisionTwo has XPS 9560 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774950/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1776491] [NEW] linux-snapdragon: wcn36xx: mac address generation on boot
Public bug reported: Impact: The wcn36xx driver in Xenial/linux-snapdragon had an ability to autogenerate its MAC address upon boot, or read it from a file (/lib/firmware/wlan/macaddr0). The linux-snapdragon kernel in Bionic doesn't have this feature. While by itself not a bug (Xenial used a QCOM provided custom driver, while Bionic uses the upstream wcn36xx driver), it can be easily work- arounded by specifying the hw address in /etc/network/interfaces, or set using ifconfig on the command line, but it turned out to be a real problem on ubuntu core: 1) upon boot, with no MAC address assigned, the wcn36xx assigns itself the dummy address "00:00:00:00:00" and that prevents the network interface from working at all, until a valid address is set 2) the ubuntu core installer doesn't have any knowledge about this behaviour, it simply tries to bring up the interface and on failure, it marks it as 'not working' On top of that, ubuntu core ships a small script in initramfs, that generates the /lib/firmware/wlan/macaddr0 file starting from the android boot serial, effectively generating a unique MAC address per board: clearly, without driver support, this ubuntu core feature doesn't work. Fix: Import back the MAC generation mechanism from Xenial: the pseudo random generation and the parsing of /lib/firmware/wlan/macaddr0 - see the attached patch. How to test: Unpon boot, if no /lib/firmware/wlan/macaddr0 is present, the kernel will print: [ 10.612701] wcn36xx a204000.wcnss:smd-edge:wcnss:wifi: Direct firmware load for wlan/macaddr0 failed with error -2 [ 10.612713] wcn36xx a204000.wcnss:smd-edge:wcnss:wifi: Failed (-2) to read macaddressfile wlan/macaddr0, using a random address instead ubuntu@dragon410c:~$ ifconfig wlan0 wlan0: flags=4098 mtu 1500 ether 00:0a:f5:d5:54:d7 txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 else, if /lib/firmware/wlan/macaddr0 is present, its content will be used to generate wlan0 MAC address: ubuntu@dragon410c:~$ cat /lib/firmware/wlan/macaddr0 fe:1a:19:77:d9:88 ubuntu@dragon410c:~$ ifconfig wlan0 wlan0: flags=4098 mtu 1500 ether fe:1a:19:77:d9:88 txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 Regression potential: Low - the patch is small and the code is wrapped in a Kconfig option (WCN36XX_SNAPDRAGON_HACKS) that only affects the linux-snapdragon flavour, leaving the generic kernel untouched. --- ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1776491 Title: linux-snapdragon: wcn36xx: mac address generation on boot Status in linux package in Ubuntu: Incomplete Bug description: Impact: The wcn36xx driver in Xenial/linux-snapdragon had an ability to autogenerate its MAC address upon boot, or read it from a file (/lib/firmware/wlan/macaddr0). The linux-snapdragon kernel in Bionic doesn't have this feature. While by itself not a bug (Xenial used a QCOM provided custom driver, while Bionic uses the upstream wcn36xx driver), it can be easily work- arounded by specifying the hw address in /etc/network/interfaces, or set using ifconfig on the command line, but it turned out to be a real problem on ubuntu core: 1) upon boot, with no MAC address assigned, the wcn36xx assigns itself the dummy address "00:00:00:00:00" and that prevents the network interface from working at all, until a valid address is set 2) the ubuntu core installer doesn't have any knowledge about this behaviour, it simply tries to bring up the interface and on failure, it marks it as 'not working' On top of that, ubuntu core ships a small script in initramfs, that generates the /lib/firmware/wlan/macaddr0 file starting from the android boot serial, effectively generating a unique MAC address per board: clearly, without driver support, this ubuntu core feature doesn't work. Fix: Import back the MAC generation mechanism from Xenial: the pseudo random generation and the parsing of /lib/firmware/wlan/macaddr0 - see the attached patch. How to test: Unpon boot, if no /lib/firmware/wlan/macaddr0 is present, the kernel will print: [ 10.612701] wcn36xx a204000.wcnss:smd-edge:wcnss:wifi: Direct firmware load for wlan/macaddr0 failed with error -2 [ 10.612713] wcn36xx a204000.wcnss:smd-edge:wcnss:wifi: Failed (-2) to read macaddressfile wlan/macaddr0, using a random address instead ubuntu@dragon410c:~$ ifconfig wlan0 wlan0: flags=4098 mtu 1500 ether 00:0a:f5:d5:54:d7 txqueuelen 1000 (Ethernet)
[Kernel-packages] [Bug 1776491] Re: linux-snapdragon: wcn36xx: mac address generation on boot
** Description changed: Impact: The wcn36xx driver in Xenial/linux-snapdragon had an ability to - autogerenate its MAC address upon boot, or read it from a file + autogenerate its MAC address upon boot, or read it from a file (/lib/firmware/wlan/macaddr0). The linux-snapdragon kernel in Bionic - doesn't have this ability. + doesn't have this feature. - While by itself it's not a bug (Xenial used a QCOM provided custom - driver, while Bionic uses the upstream wcn36xx driver) and can be - easility workarounded by specifying the hw address in - /etc/network/interfaces, or set via ifconfig on the commandline, it - turned out to be a real problem on ubuntu core: + While by itself not a bug (Xenial used a QCOM provided custom driver, + while Bionic uses the upstream wcn36xx driver), it can be easily work- + arounded by specifying the hw address in /etc/network/interfaces, or set + using ifconfig on the command line, but it turned out to be a real + problem on ubuntu core: - 1) upon boot, with now MAC address assigned, the wcn36xx assigns itself - the empty value "00:00:00:00:00" and that prevents the network interface - to work at all, until a valid address is set + 1) upon boot, with no MAC address assigned, the wcn36xx assigns itself the + dummy address "00:00:00:00:00" and that prevents the network interface from working at all, until a valid address is set - 2) the ubuntu core installed doesn't have any knowledge about this, it - tris to 'up' the interface and upon failure, it simply marks it as 'not - working' + 2) the ubuntu core installer doesn't have any knowledge about this + behaviour, it simply tries to bring up the interface and on failure, it + marks it as 'not working' - On top of that, ubuntu core ships a small script in initramfs that + On top of that, ubuntu core ships a small script in initramfs, that generates the /lib/firmware/wlan/macaddr0 file starting from the android boot serial, effectively generating a unique MAC address per board: - clearly, without driver support for this feature, the ubuntu core - efforts fall flat. + clearly, without driver support, this ubuntu core feature doesn't work. Fix: - Import back from Xenial the MAC generation mechanism: the pseudo random - generation and parsing of /lib/firmware/wlan/macaddr0 - see the attached - patch. + Import back the MAC generation mechanism from Xenial: the pseudo random + generation and the parsing of /lib/firmware/wlan/macaddr0 - see the attached patch. How to test: Unpon boot, if no /lib/firmware/wlan/macaddr0 is present, the kernel will print: - [ 10.612701] wcn36xx a204000.wcnss:smd-edge:wcnss:wifi: Direct firmware load for wlan/macaddr0 failed with error -2 - [ 10.612713] wcn36xx a204000.wcnss:smd-edge:wcnss:wifi: Failed (-2) to read macaddressfile wlan/macaddr0, using a random address instead + [ 10.612701] wcn36xx a204000.wcnss:smd-edge:wcnss:wifi: Direct firmware load for wlan/macaddr0 failed with error -2 + [ 10.612713] wcn36xx a204000.wcnss:smd-edge:wcnss:wifi: Failed (-2) to read macaddressfile wlan/macaddr0, using a random address instead ubuntu@dragon410c:~$ ifconfig wlan0 - wlan0: flags=4098 mtu 1500 - ether 00:0a:f5:d5:54:d7 txqueuelen 1000 (Ethernet) - RX packets 0 bytes 0 (0.0 B) - RX errors 0 dropped 0 overruns 0 frame 0 - TX packets 0 bytes 0 (0.0 B) - TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 + wlan0: flags=4098 mtu 1500 + ether 00:0a:f5:d5:54:d7 txqueuelen 1000 (Ethernet) + RX packets 0 bytes 0 (0.0 B) + RX errors 0 dropped 0 overruns 0 frame 0 + TX packets 0 bytes 0 (0.0 B) + TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 + else, if /lib/firmware/wlan/macaddr0 is present, its content will be + used to generate wlan0 MAC address: - else, if /lib/firmware/wlan/macaddr0 is present, its content will be used to generate wlan0 MAC address: - - ubuntu@dragon410c:~$ cat /lib/firmware/wlan/macaddr0 + ubuntu@dragon410c:~$ cat /lib/firmware/wlan/macaddr0 fe:1a:19:77:d9:88 ubuntu@dragon410c:~$ ifconfig wlan0 - wlan0: flags=4098 mtu 1500 - ether fe:1a:19:77:d9:88 txqueuelen 1000 (Ethernet) - RX packets 0 bytes 0 (0.0 B) - RX errors 0 dropped 0 overruns 0 frame 0 - TX packets 0 bytes 0 (0.0 B) - TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 - + wlan0: flags=4098 mtu 1500 + ether fe:1a:19:77:d9:88 txqueuelen 1000 (Ethernet) + RX packets 0 bytes 0 (0.0 B) + RX errors 0 dropped 0 overruns 0 frame 0 + TX packets 0 bytes 0 (0.0 B) + TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 Regression potential: Low - the patch is small and the code is wrapped in a Kconfig option - (WCN36XX_SNAPDRAGON_HACKS) that only affects the linux-snapdragon - flavour, leaving the generic kernel untouched. + (WCN36XX_SNAPDRAGON_HACKS) that
[Kernel-packages] [Bug 1776333] Re: linux: 4.13.0-46.51 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-signed Status: In Progress => Fix Released ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1776335 (linux-gcp), bug 1776336 (linux-hwe), bug 1776337 (linux-oem) derivatives: bug 1776334 (linux-raspi2) + kernel-stable-phase-changed:Tuesday, 12. June 2018 13:00 UTC + kernel-stable-phase:Uploaded ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1776335 (linux-gcp), bug 1776336 (linux-hwe), bug 1776337 (linux-oem) derivatives: bug 1776334 (linux-raspi2) kernel-stable-phase-changed:Tuesday, 12. June 2018 13:00 UTC kernel-stable-phase:Uploaded + + -- swm properties -- + phase: Uploaded -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1776333 Title: linux: 4.13.0-46.51 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Artful: New Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1776335 (linux-gcp), bug 1776336 (linux-hwe), bug 1776337 (linux-oem) derivatives: bug 1776334 (linux-raspi2) kernel-stable-phase-changed:Tuesday, 12. June 2018 13:00 UTC kernel-stable-phase:Uploaded -- swm properties -- phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1776333/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1753127] Re: No nvidia driver support in a wayland session
Hello , I can’t login to my use your profile same result with command line “incorrect login” whith the correct username and password I can’t use my computer except with a live DVD Could you help me please to fix this issus Best regards Battant -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1753127 Title: No nvidia driver support in a wayland session Status in nvidia-graphics-drivers-390 package in Ubuntu: Triaged Bug description: Why not? If I log into X11 then the nvidia drivers are used, if I log into wayland then it reverts to Intel. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nvidia-driver-390 390.25-0ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Mar 3 11:29:53 2018 InstallationDate: Installed on 2018-03-03 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180301) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nvidia-graphics-drivers-390 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1753127/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1774472] Re: hisi_sas: improve performance by optimizing DQ locking
** 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/1774472 Title: hisi_sas: improve performance by optimizing DQ locking Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: Fix Committed Bug description: [Impact] The way the driver deals with locking the DQ causes performance to suffer. [Test Case] Run iozone3 and validate performance is >= previous. [Fix] Once a DQ slot is allocated, it must be used. So, currently the driver locks the DQ while it builds and sends each task to the hardware, just in case there is a failure, so that it can reuse that slot. However - there is a point at which we the build/send is guaranteed to succeed, so we can release the lock at that point allowing new slots to be allocated. [Regression Risk] All fixes are localized to the hisi_sas drivers, which are drivers for the controllers in the hip06/hip07 SoCs, where we have directly tested these updates. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774472/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1774467] Re: hisi_sas: Support newer v3 hardware
** 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/1774467 Title: hisi_sas: Support newer v3 hardware Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: Fix Committed Bug description: [Impact] Changes in the hisi_sas v3 hardware design require corresponding changes in the driver. [Test Case] I don't have a way to inject these errors, so testing here will be limited to regression testing on the two Ubuntu-supported platforms that have hisi_sas controllers (D05/D06). [Fix] Include various cherry-picks from upstream that add the necessary support. [Regression Risk] All fixes are localized to the hisi_sas drivers, which are drivers for the controllers in the hip06/hip07 SoCs, where we have directly tested these updates. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774467/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1774466] Re: hisi_sas robustness fixes
** 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/1774466 Title: hisi_sas robustness fixes Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: Fix Committed Bug description: [Impact] Several issues have been uncovered during testing. [Test Case] Not all of these changes have a reliable reproducer - some are corner cases hit during error recovery, etc. However, we can regression test w/ e.g. iozone3 on the two Ubuntu-supported platforms that use this device, as well as remove/reload the module, which is a trigger for some of these issues. [Fix] All fixes here are upstream cherry-picks - see the individual commits for details. [Regression Risk] All fixes are localized to the hisi_sas drivers, which are drivers for the controllers in the hip06/hip07 SoCs, where we have directly tested these updates. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774466/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1773295] Re: False positive ACPI _PRS error messages
** Changed in: linux (Ubuntu Bionic) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1773295 Title: False positive ACPI _PRS error messages Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Fix Committed Bug description: New platforms have hardware registers for routing table implemented as "write once". Once set by UEFI firmware during POST, OS will not be able to modify the routing table, and ACPI _PRS method are removed according to ACPI spec. As a result, generating the error messages "ACPI Exception: AE_NOT_FOUND, Evaluating _PRS" in kernel by default does not make sense, and they should be muted by default. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1773295/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1773243] Re: PCIe link speeds of 16 GT/s are shown as "Unknown speed"
** 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/1773243 Title: PCIe link speeds of 16 GT/s are shown as "Unknown speed" Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: Fix Committed Bug description: [Impact] sysfs shows the linkspeed of 16 GT/s devices as "Unknown", so the user can't actually see what speed it is capable of, or currently running at. [Test Case] For a PCIe device that supports 16 GT/s: $ cat /sys/devices/pci:80/:80:08.0/max_link_speed 16 GT/s [Fix] Cherry-pick an upstream commit that supports in-kernel decoding of 16 GT/s link speed [Regression Risk] Trivial fix that just adds an extra case in a switch statement w/ supporting #defines. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1773243/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1776293] Re: [Hyper-V] Disable CONFIG_HOTPLUG_CPU in linux-azure
Yes, please disable CONFIG_ARCH_HIBERATION_POSSIBLE and CONFIG_ARCH_SUSPEND_POSSIBLE and the obligatory dependencies. We don't rely on these guest cooperation to pause or suspend a VM. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1776293 Title: [Hyper-V] Disable CONFIG_HOTPLUG_CPU in linux-azure Status in linux-azure package in Ubuntu: New Status in linux-azure source package in Bionic: In Progress Bug description: While Hyper-V may present all potential CPUs via ACPI MADT, CPU add/remove is not supported. This results in kernel data structures created for the largest potential size based on the number of CPUs when those CPUs will never be added during the time the guest is up (it can certainly be resized when it's down and deallocated). Please disable CONFIG_HOTPLUG_CPU in linux-azure. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1776293/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1776491] Re: linux-snapdragon: wcn36xx: mac address generation on boot
** Tags added: patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1776491 Title: linux-snapdragon: wcn36xx: mac address generation on boot Status in linux package in Ubuntu: Incomplete Bug description: Impact: The wcn36xx driver in Xenial/linux-snapdragon had an ability to autogenerate its MAC address upon boot, or read it from a file (/lib/firmware/wlan/macaddr0). The linux-snapdragon kernel in Bionic doesn't have this feature. While by itself not a bug (Xenial used a QCOM provided custom driver, while Bionic uses the upstream wcn36xx driver), it can be easily work- arounded by specifying the hw address in /etc/network/interfaces, or set using ifconfig on the command line, but it turned out to be a real problem on ubuntu core: 1) upon boot, with no MAC address assigned, the wcn36xx assigns itself the dummy address "00:00:00:00:00" and that prevents the network interface from working at all, until a valid address is set 2) the ubuntu core installer doesn't have any knowledge about this behaviour, it simply tries to bring up the interface and on failure, it marks it as 'not working' On top of that, ubuntu core ships a small script in initramfs, that generates the /lib/firmware/wlan/macaddr0 file starting from the android boot serial, effectively generating a unique MAC address per board: clearly, without driver support, this ubuntu core feature doesn't work. Fix: Import back the MAC generation mechanism from Xenial: the pseudo random generation and the parsing of /lib/firmware/wlan/macaddr0 - see the attached patch. How to test: Unpon boot, if no /lib/firmware/wlan/macaddr0 is present, the kernel will print: [ 10.612701] wcn36xx a204000.wcnss:smd-edge:wcnss:wifi: Direct firmware load for wlan/macaddr0 failed with error -2 [ 10.612713] wcn36xx a204000.wcnss:smd-edge:wcnss:wifi: Failed (-2) to read macaddressfile wlan/macaddr0, using a random address instead ubuntu@dragon410c:~$ ifconfig wlan0 wlan0: flags=4098 mtu 1500 ether 00:0a:f5:d5:54:d7 txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 else, if /lib/firmware/wlan/macaddr0 is present, its content will be used to generate wlan0 MAC address: ubuntu@dragon410c:~$ cat /lib/firmware/wlan/macaddr0 fe:1a:19:77:d9:88 ubuntu@dragon410c:~$ ifconfig wlan0 wlan0: flags=4098 mtu 1500 ether fe:1a:19:77:d9:88 txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 Regression potential: Low - the patch is small and the code is wrapped in a Kconfig option (WCN36XX_SNAPDRAGON_HACKS) that only affects the linux-snapdragon flavour, leaving the generic kernel untouched. --- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776491/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1772930] Re: linux-azure: 4.15.0-1013.13 -proposed tracker
Tested, looks good. ** Changed in: kernel-sru-workflow/stakeholder-signoff Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1772930 Title: linux-azure: 4.15.0-1013.13 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Confirmed Status in Kernel SRU Workflow promote-to-updates series: Confirmed Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow stakeholder-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1772927 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1772930/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1772930] Re: linux-azure: 4.15.0-1013.13 -proposed tracker
The package has been published and the bug is being set to Fix Released ** Changed in: kernel-sru-workflow/promote-to-security Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/promote-to-updates Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow Status: In Progress => Fix Released ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1772927 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true + kernel-stable-phase:Released + kernel-stable-phase-changed:Tuesday, 12. June 2018 17:00 UTC ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1772927 - phase: Promoted to proposed + phase: Released proposed-announcement-sent: true proposed-testing-requested: true - kernel-stable-phase:Released - kernel-stable-phase-changed:Tuesday, 12. June 2018 17:00 UTC ** Tags removed: kernel-release-tracking-bug-live -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1772930 Title: linux-azure: 4.15.0-1013.13 -proposed tracker Status in Kernel SRU Workflow: Fix Released Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Fix Released Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow stakeholder-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure source package in Bionic: Fix Released Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1772927 phase: Released proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1772930/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1752772] Re: r8169 ethernet card don't work after returning from suspension
** Changed in: linux (Ubuntu Bionic) Status: Confirmed => 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/1752772 Title: r8169 ethernet card don't work after returning from suspension Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Bug description: ===SRU Justification=== [Impact] Ethernet r8169 stops working after system resumed from suspend. [Test] User confirmed these patches fix the issue. r8169 continues to work after resume from suspend. [Regression Potential] Medium. The fix is limited to one device, all patches are in mainline. The WOL default change might cause regression for users that depend on BIOS settings. We can advice them to use userspace tool (systemd, ethtool, etc.) instead. ===Original Bug Report=== I have noticed that the network stopped working on my desktop after I've suspended the system and woke it up. On dmesg there are messages like: [ 150.877998] IPv6: ADDRCONF(NETDEV_UP): enp1s0: link is not ready [ 150.944101] do_IRQ: 3.37 No irq handler for vector [ 150.944105] r8169 :01:00.0 enp1s0: link down [ 150.944180] IPv6: ADDRCONF(NETDEV_UP): enp1s0: link is not ready When using Xenial (from a different install), this problem is not happening. This is happening on Bionic. There are only two ways to restore connectivity: 1) Reboot the system; 2) Remove the r8169 module and reinsert it with modprobe. The motherboard is a AsRock H55M-LE and the Ethernet controller is: 01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 03) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-firmware 1.172 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: LXDE Date: Fri Mar 2 00:21:57 2018 Dependencies: InstallationDate: Installed on 2018-02-26 (3 days ago) InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180226) PackageArchitecture: all SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-10-generic. ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: MID [HDA Intel MID], device 0: VT1818S Analog [VT1818S Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: usuario1153 F pulseaudio /dev/snd/controlC1: usuario1153 F pulseaudio Card0.Amixer.info: Card hw:0 'MID'/'HDA Intel MID at 0xfbdf8000 irq 26' Mixer name : 'VIA VT1818S' Components : 'HDA:11060440,18492818,0010' Controls : 40 Simple ctrls : 17 Card1.Amixer.info: Card hw:1 'HDMI'/'HDA ATI HDMI at 0xfbffc000 irq 27' Mixer name : 'ATI R6xx HDMI' Components : 'HDA:1002aa01,00aa0100,00100200' Controls : 7 Simple ctrls : 1 Card1.Amixer.values: Simple mixer control 'IEC958',0 Capabilities: pswitch pswitch-joined Playback channels: Mono Mono: Playback [on] CurrentDesktop: LXDE Dependencies: DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=edd83175-c707-4b31-90d2-ce2f5cebc73f InstallationDate: Installed on 2018-02-26 (3 days ago) InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180226) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: linux-firmware 1.172 PackageArchitecture: all ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz root=UUID=0c4fc517-b7a0-49b0-bfcb-0485dfe6413b ro quiet ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 RelatedPackageVersions: linux-restricted-modules-4.15.0-10-generic N/A linux-backports-modules-4.15.0-10-generic N/A linux-firmware 1.172 RfKill: Tags: bionic Uname: Linux 4.15.0-10-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/20/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.80 dmi.board.name: H55M-LE dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.80:bd10/20/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH55M-LE:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M.
[Kernel-packages] [Bug 1770974] Re: Fix several bugs in RDMA/hns driver
** 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/1770974 Title: Fix several bugs in RDMA/hns driver Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: Fix Committed Bug description: [Impact] Several issues and features in the RDMA/hns driver for HiSilicon network adapters have recently landed upstream. This includes fixes for crashes and endianness issues, among others. [Test Case] Server side: ubuntu@d06-1:~$ ib_write_bw -n 5 -d hns_2 * Waiting for client to connect... * hr_qp->port_num= 0x1 --- RDMA_Write BW Test Dual-port : OFFDevice : hns_2 Number of qps : 1 Transport type : IB Connection type : RC Using SRQ : OFF CQ Moderation : 5 Mtu : 1024[B] Link type : Ethernet GID index : 2 Max inline data : 0[B] rdma_cm QPs : OFF Data ex. method : Ethernet --- local address: LID QPN 0x000c PSN 0x368fa8 RKey 0x000200 VAddr 0x00be39 GID: 00:00:00:00:00:00:00:00:00:00:255:255:10:228:68:237 remote address: LID QPN 0x000c PSN 0x19f3aa RKey 0x000200 VAddr 0x008338 GID: 00:00:00:00:00:00:00:00:00:00:255:255:10:228:68:192 --- #bytes #iterationsBW peak[MB/sec]BW average[MB/sec] MsgRate[Mpps] 65536 5108.08 108.08 0.001729 --- Client side: ubuntu@d06-2:~$ ib_write_bw -n 5 -d hns_2 10.228.68.237 hr_qp->port_num= 0x1 --- RDMA_Write BW Test Dual-port : OFFDevice : hns_2 Number of qps : 1 Transport type : IB Connection type : RC Using SRQ : OFF TX depth: 5 CQ Moderation : 5 Mtu : 1024[B] Link type : Ethernet GID index : 2 Max inline data : 0[B] rdma_cm QPs : OFF Data ex. method : Ethernet --- local address: LID QPN 0x000c PSN 0x19f3aa RKey 0x000200 VAddr 0x008338 GID: 00:00:00:00:00:00:00:00:00:00:255:255:10:228:68:192 remote address: LID QPN 0x000c PSN 0x368fa8 RKey 0x000200 VAddr 0x00be39 GID: 00:00:00:00:00:00:00:00:00:00:255:255:10:228:68:237 --- #bytes #iterationsBW peak[MB/sec]BW average[MB/sec] MsgRate[Mpps] 65536 5108.08 108.08 0.001729 --- [Regression Risk] TLDR; this driver isn't usable today, so changes to it carry negligible regression risk. These patches are localized to the hns/RDMA driver. This driver is for hardware in the hip07/hip08 SoCs, which Ubuntu supports in the D05 and D06 servers respectively. D05 firmware has intentionally disabled this feature by not exposing the ACPI ID for it. The driver therefore doesn't find the device on that platform, so there is no regression risk. D06 *does* enable this device in firmware. However, the current bionic kernel crashes when loading the base ethernet driver (hns3 - LP: #1768670) on this platform, so this feature is also currently unusable there. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1770974/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1772930] Re: linux-azure: 4.15.0-1013.13 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-security Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-updates Status: New => Confirmed ** Tags removed: block-proposed-bionic ** Tags removed: block-proposed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1772930 Title: linux-azure: 4.15.0-1013.13 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Confirmed Status in Kernel SRU Workflow promote-to-updates series: Confirmed Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow stakeholder-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1772927 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1772930/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1770770] Re: Switch Build-Depends: transfig to fig2dev
This bug was fixed in the package linux-azure - 4.15.0-1013.13
---
linux-azure (4.15.0-1013.13) bionic; urgency=medium
* linux-azure: 4.15.0-1013.13 -proposed tracker (LP: #1772930)
* Switch Build-Depends: transfig to fig2dev (LP: #1770770)
- [Config] update Build-Depends: transfig to fig2dev
[ Ubuntu: 4.15.0-23.25 ]
* linux: 4.15.0-23.25 -proposed tracker (LP: #1772927)
* arm64 SDEI support needs trampoline code for KPTI (LP: #1768630)
- arm64: mmu: add the entry trampolines start/end section markers into
sections.h
- arm64: sdei: Add trampoline code for remapping the kernel
* Some PCIe errors not surfaced through rasdaemon (LP: #1769730)
- ACPI: APEI: handle PCIe AER errors in separate function
- ACPI: APEI: call into AER handling regardless of severity
* 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
* Several hisi_sas bug fixes (LP: #1768974)
- scsi: hisi_sas: dt-bindings: add an property of signal attenuation
- scsi: hisi_sas: support the property of signal attenuation for v2 hw
- scsi: hisi_sas: fix the issue of link rate inconsistency
- scsi: hisi_sas: fix the issue of setting linkrate register
- scsi: hisi_sas: increase timer expire of internal abort task
- scsi: hisi_sas: remove unused variable hisi_sas_devices.running_req
- scsi: hisi_sas: fix return value of hisi_sas_task_prep()
- scsi: hisi_sas: Code cleanup and minor bug fixes
* [bionic] machine stuck and bonding not working well when nvmet_rdma module
is loaded (LP: #1764982)
- nvmet-rdma: Don't flush system_wq by default during remove_one
- nvme-rdma: Don't flush delete_wq by default during remove_one
* Warnings/hang during error handling of SATA disks on SAS controller
(LP: #1768971)
- scsi: libsas: defer ata device eh commands to libata
* Hotplugging a SATA disk into a SAS controller may cause crash (LP: #1768948)
- ata: do not schedule hot plug if it is a sas host
* ISST-LTE:pKVM:Ubuntu1804: rcu_sched self-detected stall on CPU follow by CPU
ATTEMPT TO RE-ENTER FIRMWARE! (LP: #1767927)
- powerpc/powernv: Handle unknown OPAL errors in opal_nvram_write()
- powerpc/64s: return more carefully from sreset NMI
- powerpc/64s: sreset panic if there is no debugger or crash dump handlers
* fsnotify: Fix fsnotify_mark_connector race (LP: #1765564)
- fsnotify: Fix fsnotify_mark_connector race
* Hang on network interface removal in Xen virtual machine (LP: #1771620)
- xen-netfront: Fix hang on device removal
* HiSilicon HNS NIC names are truncated in /proc/interrupts (LP: #1765977)
- net: hns: Avoid action name truncation
* Ubuntu 18.04 kernel crashed while in degraded mode (LP: #1770849)
- SAUCE: powerpc/perf: Fix memory allocation for core-imc based on
num_possible_cpus()
* Switch Build-Depends: transfig to fig2dev (LP: #1770770)
- [Config] update Build-Depends: transfig to fig2dev
* smp_call_function_single/many core hangs with stop4 alone (LP: #1768898)
- cpufreq: powernv: Fix hardlockup due to synchronous smp_call in timer
interrupt
* Add d-i support for Huawei NICs (LP: #1767490)
- d-i: add hinic to nic-modules udeb
* unregister_netdevice: waiting for eth0 to become free. Usage count = 5
(LP: #1746474)
- xfrm: reuse uncached_list to track xdsts
* Include nfp driver in linux-modules (LP: #1768526)
- [Config] Add nfp.ko to generic inclusion list
* Kernel panic on boot (m1.small in cn-north-1) (LP: #1771679)
- x86/xen: Reset VCPU0 info pointer after shared_info remap
* CVE-2018-3639 (x86)
- x86/bugs: Fix the parameters alignment and missing void
- KVM: SVM: Move spec control call after restore of GS
- x86/speculation: Use synthetic bits for IBRS/IBPB/STIBP
- x86/cpufeatures: Disentangle MSR_SPEC_CTRL enumeration from IBRS
- x86/cpufeatures: Disentangle SSBD enumeration
- x86/cpufeatures: Add FEATURE_ZEN
- x86/speculation: Handle HT correctly on AMD
- x86/bugs, KVM: Extend speculation control for VIRT_SPEC_CTRL
- x86/speculation: Add virtualized speculative store bypass disable support
- x86/speculation: Rework speculative_store_bypass_update()
- x86/bugs: Unify x86_spec_ctrl_{set_guest,restore_host}
- x86/bugs: Expose x86_spec_ctrl_base directly
- x86/bugs: Remove
[Kernel-packages] [Bug 1772930] Re: linux-azure: 4.15.0-1013.13 -proposed tracker
This bug was fixed in the package linux-azure - 4.15.0-1013.13
---
linux-azure (4.15.0-1013.13) bionic; urgency=medium
* linux-azure: 4.15.0-1013.13 -proposed tracker (LP: #1772930)
* Switch Build-Depends: transfig to fig2dev (LP: #1770770)
- [Config] update Build-Depends: transfig to fig2dev
[ Ubuntu: 4.15.0-23.25 ]
* linux: 4.15.0-23.25 -proposed tracker (LP: #1772927)
* arm64 SDEI support needs trampoline code for KPTI (LP: #1768630)
- arm64: mmu: add the entry trampolines start/end section markers into
sections.h
- arm64: sdei: Add trampoline code for remapping the kernel
* Some PCIe errors not surfaced through rasdaemon (LP: #1769730)
- ACPI: APEI: handle PCIe AER errors in separate function
- ACPI: APEI: call into AER handling regardless of severity
* 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
* Several hisi_sas bug fixes (LP: #1768974)
- scsi: hisi_sas: dt-bindings: add an property of signal attenuation
- scsi: hisi_sas: support the property of signal attenuation for v2 hw
- scsi: hisi_sas: fix the issue of link rate inconsistency
- scsi: hisi_sas: fix the issue of setting linkrate register
- scsi: hisi_sas: increase timer expire of internal abort task
- scsi: hisi_sas: remove unused variable hisi_sas_devices.running_req
- scsi: hisi_sas: fix return value of hisi_sas_task_prep()
- scsi: hisi_sas: Code cleanup and minor bug fixes
* [bionic] machine stuck and bonding not working well when nvmet_rdma module
is loaded (LP: #1764982)
- nvmet-rdma: Don't flush system_wq by default during remove_one
- nvme-rdma: Don't flush delete_wq by default during remove_one
* Warnings/hang during error handling of SATA disks on SAS controller
(LP: #1768971)
- scsi: libsas: defer ata device eh commands to libata
* Hotplugging a SATA disk into a SAS controller may cause crash (LP: #1768948)
- ata: do not schedule hot plug if it is a sas host
* ISST-LTE:pKVM:Ubuntu1804: rcu_sched self-detected stall on CPU follow by CPU
ATTEMPT TO RE-ENTER FIRMWARE! (LP: #1767927)
- powerpc/powernv: Handle unknown OPAL errors in opal_nvram_write()
- powerpc/64s: return more carefully from sreset NMI
- powerpc/64s: sreset panic if there is no debugger or crash dump handlers
* fsnotify: Fix fsnotify_mark_connector race (LP: #1765564)
- fsnotify: Fix fsnotify_mark_connector race
* Hang on network interface removal in Xen virtual machine (LP: #1771620)
- xen-netfront: Fix hang on device removal
* HiSilicon HNS NIC names are truncated in /proc/interrupts (LP: #1765977)
- net: hns: Avoid action name truncation
* Ubuntu 18.04 kernel crashed while in degraded mode (LP: #1770849)
- SAUCE: powerpc/perf: Fix memory allocation for core-imc based on
num_possible_cpus()
* Switch Build-Depends: transfig to fig2dev (LP: #1770770)
- [Config] update Build-Depends: transfig to fig2dev
* smp_call_function_single/many core hangs with stop4 alone (LP: #1768898)
- cpufreq: powernv: Fix hardlockup due to synchronous smp_call in timer
interrupt
* Add d-i support for Huawei NICs (LP: #1767490)
- d-i: add hinic to nic-modules udeb
* unregister_netdevice: waiting for eth0 to become free. Usage count = 5
(LP: #1746474)
- xfrm: reuse uncached_list to track xdsts
* Include nfp driver in linux-modules (LP: #1768526)
- [Config] Add nfp.ko to generic inclusion list
* Kernel panic on boot (m1.small in cn-north-1) (LP: #1771679)
- x86/xen: Reset VCPU0 info pointer after shared_info remap
* CVE-2018-3639 (x86)
- x86/bugs: Fix the parameters alignment and missing void
- KVM: SVM: Move spec control call after restore of GS
- x86/speculation: Use synthetic bits for IBRS/IBPB/STIBP
- x86/cpufeatures: Disentangle MSR_SPEC_CTRL enumeration from IBRS
- x86/cpufeatures: Disentangle SSBD enumeration
- x86/cpufeatures: Add FEATURE_ZEN
- x86/speculation: Handle HT correctly on AMD
- x86/bugs, KVM: Extend speculation control for VIRT_SPEC_CTRL
- x86/speculation: Add virtualized speculative store bypass disable support
- x86/speculation: Rework speculative_store_bypass_update()
- x86/bugs: Unify x86_spec_ctrl_{set_guest,restore_host}
- x86/bugs: Expose x86_spec_ctrl_base directly
- x86/bugs: Remove
[Kernel-packages] [Bug 1753127] Re: No nvidia driver support in a wayland session
This bug also affect kernel 4.16 and kernel 4.17 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1753127 Title: No nvidia driver support in a wayland session Status in nvidia-graphics-drivers-390 package in Ubuntu: Triaged Bug description: Why not? If I log into X11 then the nvidia drivers are used, if I log into wayland then it reverts to Intel. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nvidia-driver-390 390.25-0ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Mar 3 11:29:53 2018 InstallationDate: Installed on 2018-03-03 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180301) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nvidia-graphics-drivers-390 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1753127/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1770770] Re: Switch Build-Depends: transfig to fig2dev
This bug was fixed in the package linux-azure - 4.15.0-1013.13
---
linux-azure (4.15.0-1013.13) bionic; urgency=medium
* linux-azure: 4.15.0-1013.13 -proposed tracker (LP: #1772930)
* Switch Build-Depends: transfig to fig2dev (LP: #1770770)
- [Config] update Build-Depends: transfig to fig2dev
[ Ubuntu: 4.15.0-23.25 ]
* linux: 4.15.0-23.25 -proposed tracker (LP: #1772927)
* arm64 SDEI support needs trampoline code for KPTI (LP: #1768630)
- arm64: mmu: add the entry trampolines start/end section markers into
sections.h
- arm64: sdei: Add trampoline code for remapping the kernel
* Some PCIe errors not surfaced through rasdaemon (LP: #1769730)
- ACPI: APEI: handle PCIe AER errors in separate function
- ACPI: APEI: call into AER handling regardless of severity
* 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
* Several hisi_sas bug fixes (LP: #1768974)
- scsi: hisi_sas: dt-bindings: add an property of signal attenuation
- scsi: hisi_sas: support the property of signal attenuation for v2 hw
- scsi: hisi_sas: fix the issue of link rate inconsistency
- scsi: hisi_sas: fix the issue of setting linkrate register
- scsi: hisi_sas: increase timer expire of internal abort task
- scsi: hisi_sas: remove unused variable hisi_sas_devices.running_req
- scsi: hisi_sas: fix return value of hisi_sas_task_prep()
- scsi: hisi_sas: Code cleanup and minor bug fixes
* [bionic] machine stuck and bonding not working well when nvmet_rdma module
is loaded (LP: #1764982)
- nvmet-rdma: Don't flush system_wq by default during remove_one
- nvme-rdma: Don't flush delete_wq by default during remove_one
* Warnings/hang during error handling of SATA disks on SAS controller
(LP: #1768971)
- scsi: libsas: defer ata device eh commands to libata
* Hotplugging a SATA disk into a SAS controller may cause crash (LP: #1768948)
- ata: do not schedule hot plug if it is a sas host
* ISST-LTE:pKVM:Ubuntu1804: rcu_sched self-detected stall on CPU follow by CPU
ATTEMPT TO RE-ENTER FIRMWARE! (LP: #1767927)
- powerpc/powernv: Handle unknown OPAL errors in opal_nvram_write()
- powerpc/64s: return more carefully from sreset NMI
- powerpc/64s: sreset panic if there is no debugger or crash dump handlers
* fsnotify: Fix fsnotify_mark_connector race (LP: #1765564)
- fsnotify: Fix fsnotify_mark_connector race
* Hang on network interface removal in Xen virtual machine (LP: #1771620)
- xen-netfront: Fix hang on device removal
* HiSilicon HNS NIC names are truncated in /proc/interrupts (LP: #1765977)
- net: hns: Avoid action name truncation
* Ubuntu 18.04 kernel crashed while in degraded mode (LP: #1770849)
- SAUCE: powerpc/perf: Fix memory allocation for core-imc based on
num_possible_cpus()
* Switch Build-Depends: transfig to fig2dev (LP: #1770770)
- [Config] update Build-Depends: transfig to fig2dev
* smp_call_function_single/many core hangs with stop4 alone (LP: #1768898)
- cpufreq: powernv: Fix hardlockup due to synchronous smp_call in timer
interrupt
* Add d-i support for Huawei NICs (LP: #1767490)
- d-i: add hinic to nic-modules udeb
* unregister_netdevice: waiting for eth0 to become free. Usage count = 5
(LP: #1746474)
- xfrm: reuse uncached_list to track xdsts
* Include nfp driver in linux-modules (LP: #1768526)
- [Config] Add nfp.ko to generic inclusion list
* Kernel panic on boot (m1.small in cn-north-1) (LP: #1771679)
- x86/xen: Reset VCPU0 info pointer after shared_info remap
* CVE-2018-3639 (x86)
- x86/bugs: Fix the parameters alignment and missing void
- KVM: SVM: Move spec control call after restore of GS
- x86/speculation: Use synthetic bits for IBRS/IBPB/STIBP
- x86/cpufeatures: Disentangle MSR_SPEC_CTRL enumeration from IBRS
- x86/cpufeatures: Disentangle SSBD enumeration
- x86/cpufeatures: Add FEATURE_ZEN
- x86/speculation: Handle HT correctly on AMD
- x86/bugs, KVM: Extend speculation control for VIRT_SPEC_CTRL
- x86/speculation: Add virtualized speculative store bypass disable support
- x86/speculation: Rework speculative_store_bypass_update()
- x86/bugs: Unify x86_spec_ctrl_{set_guest,restore_host}
- x86/bugs: Expose x86_spec_ctrl_base directly
- x86/bugs: Remove
[Kernel-packages] [Bug 1772930] Re: linux-azure: 4.15.0-1013.13 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-updates Status: Confirmed => Fix Committed ** Changed in: kernel-sru-workflow/promote-to-updates Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz Zemczak (sil2100) ** Changed in: kernel-sru-workflow/promote-to-security Status: Confirmed => Fix Committed ** Changed in: kernel-sru-workflow/promote-to-security Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz Zemczak (sil2100) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1772930 Title: linux-azure: 4.15.0-1013.13 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Fix Committed Status in Kernel SRU Workflow promote-to-updates series: Fix Committed Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow stakeholder-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure source package in Bionic: Fix Released Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1772927 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1772930/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1738259] Re: need to ensure microcode updates are available to all bare-metal installs of Ubuntu
@sdeziel, I agree 100%.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1738259
Title:
need to ensure microcode updates are available to all bare-metal
installs of Ubuntu
Status in linux-meta package in Ubuntu:
Triaged
Status in linux-meta-hwe package in Ubuntu:
New
Status in linux-meta-hwe-edge package in Ubuntu:
New
Status in linux-meta-lts-xenial package in Ubuntu:
Fix Released
Status in linux-meta-oem package in Ubuntu:
Fix Released
Status in linux-meta source package in Precise:
New
Status in linux-meta source package in Trusty:
Fix Released
Status in linux-meta source package in Xenial:
Fix Released
Status in linux-meta-hwe source package in Xenial:
Fix Released
Status in linux-meta-hwe-edge source package in Xenial:
Fix Released
Status in linux-meta-lts-xenial source package in Xenial:
Fix Committed
Status in linux-meta-oem source package in Xenial:
Fix Released
Status in linux-meta source package in Zesty:
Invalid
Status in linux-meta source package in Artful:
Fix Released
Status in linux-meta source package in Bionic:
Fix Released
Bug description:
From time to time, CPU vendors release updates to microcode that can
be loaded into the CPU from the OS. For x86, we have these updates
available in the archive as amd64-microcode and intel-microcode.
Sometimes, these microcode updates have addressed security issues with
the CPU. They almost certainly will again in the future.
We should ensure that all users of Ubuntu on baremetal x86 receive
these security updates, and have them applied to the CPU in early boot
where at all feasible.
Because these are hardware-dependent packages which we don't want to
install except on baremetal (so: not in VMs or containers), the
logical place to pull them into the system is via the kernel, so that
only the kernel baremetal flavors pull them in. This is analogous to
linux-firmware, which is already a dependency of the linux-
image-{lowlatency,generic} metapackages, and whose contents are
applied to the hardware by the kernel similar to microcode.
So, please update the linux-image-{lowlatency,generic} metapackages to
add a dependency on amd64-microcode [amd64], intel-microcode [amd64],
and the corresponding hwe metapackages also.
Please time this change to coincide with the next updates of the
microcode packages in the archive.
I believe we will also need to promote the *-microcode packages to
main from restricted as part of this (again, by analogy with linux-
firmware).
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1738259/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
