[Kernel-packages] [Bug 1835185] Re: High write iops after kernel upgrade
Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1835185 Title: High write iops after kernel upgrade Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu server 18.04.2 There is a problem with the latest system updates (kernel version 4.15.0-54-generic # 58-Ubuntu SMP). After upgrading from version 4.15.0-36-generic # 39-Ubuntu SMP we observe at the same software configuration an increased load on the disk (write) - MySQL previously loaded the disk at 20-50 mB/s, after the update it started loading at 150-250 mB/s. On the server we have cronjobs with PHP writing stuff to the DB. MySQL configuration and package version was not changed, the load profile is the same and does not depend on external users (OLAP DB) If we boot into the old kernel version (4.15.0-36), the problem disappears. Also tested kernels: 4.15.0-52 - problem persists 4.18.0-25 (hwe) - problem persists, load became more 200-250 mB/s Attaching list of updated packages (apt/history.log) and other info. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1835185/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836521] Re: Mainline kernel build failure for i386 and amd64 - v5.2.1, v5.1.18
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.2.1/BUILD.LOG.amd64 ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1836521 Title: Mainline kernel build failure for i386 and amd64 - v5.2.1, v5.1.18 Status in linux package in Ubuntu: Confirmed Bug description: The mainline kernel builds on kernels.ubuntu.com are in failed state for the latest kernel versions. https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.2.1/ https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.2/ https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.1.17/ https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.1.18/ Build seems to have failed for i386 and amd64 but succeeded for other architectures. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836521/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836215] Re: [DELL][BIONICS] Redpine driver got crashed during shutdown/reboot
This patch fixes the issue. ** Patch removed: "0001-UBUNTU-SAUCE-Redpine-system-crashed-while-reboot-shutdown.patch" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836215/+attachment/5276646/+files/0001-UBUNTU-SAUCE-Redpine-system-crashed-while-reboot-shutdown.patch ** Patch added: "patch" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836215/+attachment/5277058/+files/0001-Xenial-PATCH-rsi-system-crashed-while-reboot-shutdow.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/1836215 Title: [DELL][BIONICS] Redpine driver got crashed during shutdown/reboot Status in linux package in Ubuntu: Incomplete Bug description: SRU Justification: -- Impact: --- Kernel crash upon shutdown or rebooting the device. Test case: -- 1) Power up the device, Redpine modules are loaded by default. 2) Reboot or shutdown the device. 3) Observe the behavior. Result: --- Redpine driver crashes the entire kernel and below is the crash log. ... skipping ... [ 47.002030] BUG: unable to handle kernel NULL pointer dereference at 0038 [ 47.010828] IP: rsi_shutdown+0x2c/0x100 [rsi_sdio] [ 47.016180] PGD 0 P4D 0 [ 47.019025] Oops: 1 SMP PTI [ 47.136275] CPU: 1 PID: 1 Comm: systemd-shutdow Not tainted 4.15.0-1035-oem #40-Ubuntu [ 47.145131] Hardware name: Dell Inc. Edge Gateway 3001/0YMHCG, BIOS 01.00.08 10/23/2018 [ 47.154096] RIP: 0010:rsi_shutdown+0x2c/0x100 [rsi_sdio] [ 47.160039] RSP: 0018:b08dbd78 EFLAGS: 00010246 [ 47.165887] RAX: RBX: a08b77f1d000 RCX: [ 47.173869] RDX: 0002 RSI: c07aa77f RDI: 0001 [ 47.181851] RBP: b08dbd90 R08: R09: b08dbc50 [ 47.189834] R10: R11: 023a R12: a08b6d94 [ 47.197816] R13: a08b3cbfb408 R14: 8f556137 R15: a08b3cbfb468 [ 47.205801] FS: 7f85cd093940() GS:a08b70b0() knlGS: [ 47.214854] CS: 0010 DS: ES: CR0: 80050033 [ 47.221281] CR2: 0038 CR3: 6a93 CR4: 001006e0 [ 47.229262] Call Trace: [ 47.232017] device_shutdown+0x14e/0x200 [ 47.236416] kernel_power_off+0x35/0x70 [ 47.240711] SYSC_reboot+0x132/0x210 [ 47.244721] ? SYSC_rt_sigtimedwait+0x88/0xe0 [ 47.249604] ? do_writev+0x61/0xf0 [ 47.253411] ? do_writev+0x61/0xf0 [ 47.257219] ? sigprocmask+0x6f/0xa0 [ 47.261225] SyS_reboot+0xe/0x10 [ 47.264841] do_syscall_64+0x73/0x130 [ 47.268945] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 Root cause analysis: Device operating mode 8(bluetooth alone), our driver supports multiple modes like 13(WiFi + Bluetooth), WiFi related structures are not been initialized in Bluetooth alone mode(8), dereferencing them in rsi_shutdown function causes crash. In Redpine driver, this NULL check is missed. Hence, Added the fix for the same. Fix: Added proper NULL check in rsi_shutdown function. Regression Potential: - This is a very direct issue, since the driver is getting crashed while reboot. We rebooted multiples times, checked the driver stability. Every thing ran smooth. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836215/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835054] Re: Enable Armada SOCs and MVPP2 NIC driver for disco/generic arm64
** Description changed: == SRU Justification == - The mvpp2 is a driver for network controllers(s) in Marvell SOCs, particularly Armada 8040. + The mvpp2 is a driver for network controllers(s) in Marvell SOCs, + particularly Armada 8040. However this driver was neither enabled as a module or a built-in for Disco arm64. == Fix == - Just like what we did for armhf, set CONFIG_MVPP2 to "m" for arm64 can solve this problem. + Just like what we did for armhf, set CONFIG_MVPP2 to "m" for arm64 can + solve this problem. - Corresponding configs like CONFIG_ARCH_MVEBU and CONFIG_ARCH_MULTI_V7 - need to be enabled as well to meet the dependency requirement. + We need to enable the Armada SOCs support (CONFIG_ARCH_MVEBU) as well + to meet the dependency requirement. - CONFIG_CRYPTO_DEV_SAFEXCEL and CONFIG_PCI_AARDVARK are disabled - explicitly to avoid interactive dialogues when building the kernel. + Other configs were added by the updateconfigs process. == Test == A test kernel for Disco ARM64 could be found here: - https://people.canonical.com/~phlin/kernel/lp-1835054-mvpp2/ + https://people.canonical.com/~phlin/kernel/lp-1835054-mvpp2/V2/ - User has confirmed that the patched kernel can fix this missing driver - issue. + User has confirmed that the V1 kernel can fix this missing driver + issue (V2 is just with CONFIG_ARCH_MULTI_V7 dropped and some configs + added explicitly, I have it tested on an ARM64 node, the mvpp2 module + can be loaded without any issue). == Regression Potential == - Low, this patch just make this driver to be built as a module, and we already have this enabled for armhf. + Low, this patch just enable the Armada SOCs and make this mvpp2 driver + to be built as a module on ARM64, and we already have those for armhf. == Original Bug Report == At least in Ubuntu 19.04, the arm64 kernel (linux-image-5.0.0) is not building CONFIG_MVPP2 (depends on CONFIG_ARCH_MVEBU) - a driver for network controllers(s) in Marvell SOCs, particularly Armada 8040 - neither as a module or a built-in: $ uname -m aarch64 $ grep MVPP2 /boot/config-5.0.0-20-generic $ It makes very hard (and impossible for non-advanced users) to install and use Ubuntu on the Macchiatobin board (http://macchiatobin.net/) - a reasonably priced and performant server/mini-desktop platform. Could it be added, please, and the installer image re-generated. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1835054 Title: Enable Armada SOCs and MVPP2 NIC driver for disco/generic arm64 Status in linux package in Ubuntu: In Progress Status in linux source package in Disco: In Progress Status in linux source package in Eoan: In Progress Bug description: == SRU Justification == The mvpp2 is a driver for network controllers(s) in Marvell SOCs, particularly Armada 8040. However this driver was neither enabled as a module or a built-in for Disco arm64. == Fix == Just like what we did for armhf, set CONFIG_MVPP2 to "m" for arm64 can solve this problem. We need to enable the Armada SOCs support (CONFIG_ARCH_MVEBU) as well to meet the dependency requirement. Other configs were added by the updateconfigs process. == Test == A test kernel for Disco ARM64 could be found here: https://people.canonical.com/~phlin/kernel/lp-1835054-mvpp2/V2/ User has confirmed that the V1 kernel can fix this missing driver issue (V2 is just with CONFIG_ARCH_MULTI_V7 dropped and some configs added explicitly, I have it tested on an ARM64 node, the mvpp2 module can be loaded without any issue). == Regression Potential == Low, this patch just enable the Armada SOCs and make this mvpp2 driver to be built as a module on ARM64, and we already have those for armhf. == Original Bug Report == At least in Ubuntu 19.04, the arm64 kernel (linux-image-5.0.0) is not building CONFIG_MVPP2 (depends on CONFIG_ARCH_MVEBU) - a driver for network controllers(s) in Marvell SOCs, particularly Armada 8040 - neither as a module or a built-in: $ uname -m aarch64 $ grep MVPP2 /boot/config-5.0.0-20-generic $ It makes very hard (and impossible for non-advanced users) to install and use Ubuntu on the Macchiatobin board (http://macchiatobin.net/) - a reasonably priced and performant server/mini-desktop platform. Could it be added, please, and the installer image re-generated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1835054/+subscriptions -- Mailing list: https://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 1829620] Re: intel-microcode on ASUS makes kernel stuck during loading initramfs on bionic-updates, bionic-security
Is there a BIOS update for your Dell? I updated my Asus' BIOS and it fixed the issue. Though, now the NVIDIA driver does not work for me. I haven't had a chance to dig in on yet. Perhaps a reinstall of the driver would fix it. On Mon, 15 Jul 2019 at 05:30, Bert M Snider <1829...@bugs.launchpad.net> wrote: > I am super new to linux. I have read through the thread, and I am pretty > sure that my ASUS ZenBook is having the same problem. I re-installed Ubuntu > and have just not upgraded, but I not happy with that workaround. So, will > this be something that will be fixed with a future update? Or, will I need > to do this from now on? I have no understanding of how to use the > "dis_ucode_ldr". > Thank you > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1829620 > > Title: > intel-microcode on ASUS makes kernel stuck during loading initramfs on > bionic-updates, bionic-security > > Status in intel-microcode package in Ubuntu: > Confirmed > Status in linux package in Ubuntu: > Confirmed > Status in linux-hwe package in Ubuntu: > Confirmed > Status in linux-hwe-edge package in Ubuntu: > Confirmed > > Bug description: > Description: > - my system gets stuck at "Booting, Loading initramfs" (the first 2 > lines of booting, after grub) > - does not even show the enter cryptsetup passphrase > - affected kernels: > # apt list --installed |grep linux-signed > WARNING: apt does not have a stable CLI interface. Use with caution in > scripts. > linux-signed-generic/bionic-security,bionic-updates,now 4.15.0.50.52 > amd64 [installed] > linux-signed-generic-hwe-18.04/bionic-security,bionic-updates,now > 4.18.0.20.70 amd64 [installed] > linux-signed-generic-hwe-18.04-edge/bionic-security,bionic-updates,now > 5.0.0.15.71 amd64 [installed] > > - the setup is not new, has been working perfectly before (about 7 > days since my last restart?) > > System: > - HW: ASUS Zenbook 14 UX433FN > - Ubuntu 18.04, runing latest HWE, fully updated > - grub(-pc), cryptsetup (crypttab entries for custom encrypted LUKS > setup), > > Suspected/possible cause?: > - recent intel-microcode package update > - recent kernel package updates > > Steps taken: > - tried to remove "splash quiet" from grub/kernel cmd line (also tried > adding nosplash, noplymouth) > - completely removed nvidia drivers (apt purge *nvidia*) > - completely purged and reinstalled grub (grup-pc) > - completely purged and reinstalled all kernels (headers, modules, > image, ..) > - toggle BIOS "fastboot" (now using OFF) > - toggle UEFI SecureBoot (now using ON) > - remove plymouth (apt remove *plymouth* , but the workaround is working > with plymouth installed) > > Workaround: > - so far, I'm only able to boot with non-Ubuntu kernel! > (linux-image-liquorix-amd64) > - which needs "splash" option ON > - reinstall cryptsetup & update-grub (as suggested in > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829620/comments/10 ) > > I am not sure how to get you more debug info, as this setup has been > working before, and it's a very eary boot-process bug, so I can't even > access dmesg etc. > > EDIT: > > Hypothesis: > Only affects ASUS with i7-8565U Whiskey Lake Intel CPU > > Upstream Bug Report: > > https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/issues/1 > > WORKAROUND 1: disable intel microcode updates during boot > From this bug: > https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1759920 > 1/ add the boot parameter: dis_ucode_ldr to /etc/default/grub > 2/ update-grub > > WORKAROUND 2: downgrade (and hold) intel-microcode to older version from > bionic/main > apt install --reinstall intel-microcode=3.20180312.0~ubuntu18.04.1 > > WORKAROUND 3: upgrade BIOS > Asus has released updated BIOSes, which probably include the newest > microcode. After upgrading workarounds 1,2 are not needed. > Please NOTE, unlike workarounds 1,2, BIOS upgrade is permanent and > cannot be (easily) reverted. > > --- > ProblemType: Bug > ApportVersion: 2.20.9-0ubuntu7.6 > Architecture: amd64 > CurrentDesktop: KDE > DistroRelease: KDE neon 18.04 > InstallationDate: Installed on 2012-12-23 (2337 days ago) > InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 > (20121017.1) > Package: linux-hwe-edge (not installed) > Tags: bionic wayland-session > Uname: Linux 5.0.0-17.1-liquorix-amd64 x86_64 > UnreportableReason: The running kernel is not an Ubuntu kernel > UpgradeStatus: No upgrade log present (probably fresh install) > UserGroups: adm libvirtd lpadmin netdev plugdev sudo vboxusers video > _MarkForUpload: True > --- > ProblemType: Bug > ApportVersion: 2.20.9-0ubuntu7.6 > Architecture: amd64 > CurrentDesktop: KDE > DistroRelease: KDE neon 18.04 > InstallationDate: Installed on 2012-12-23 (2339 days ago) > InstallationMedia: Kubuntu
[Kernel-packages] [Bug 1835449] Re: Bluetooth: hci0: request failed to create LE connection: status 0x0c (Intel 9260)
** Tags added: verification-done-bionic ** Tags added: verification-done-xenial -- 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/1835449 Title: Bluetooth: hci0: request failed to create LE connection: status 0x0c (Intel 9260) Status in linux-firmware package in Ubuntu: In Progress Status in linux-firmware source package in Xenial: Fix Committed Status in linux-firmware source package in Bionic: Fix Committed Bug description: [Impact] Intel Wireless-AC 9260 Bluetooth doesn't pair to Bluetooth 5.0 HID devices. [Fix] Bluetooth FW Build REL0329 or newer is known to have fixed this problem on Cosmic, and for Disco we have REL0420. On Bionic and Xenial it takes a firmware backport from upstream commit c2d8f1b7f820b31b6120d741c23db23340a72821. Original patch modified to fix conflicts in the WHENCE file. [Test Case] Verified on hardware platforms with Intel Wireless AC 9260 installed, e.g. Dell Precision 7530. Copied the two blobs to /lib/firmware/intel and power off the device completely to trigger firmware reload at the next boot. [Regression Risk] Low. Tried following kernels with REL0329 firmware blobs: * 4.4.0-154-generic: Xenial, WiFi/Bluetooth doesn't work * 4.8.0-58-generic: Xenial, even doesn't boot to console * 4.10.0-42-generic: Xenial, WiFi/Bluetooth doesn't work * 4.11.0-14-generic: Xenial, WiFi/Bluetooth doesn't work * 4.13.0-45-generic: Xenial * 4.15.0-54-generic: Xenial, Bionic * 4.15.0-1043-oem: Xenial, Bionic For those WiFi/Bluetooth doesn't work versions, WiFi/Bluetooth doesn't work even with current firmware blobs shipped in Xenial's linux-firmware REL0186. So overall, these updated blobs are only loaded by hardware requires them, and they doesn't bring harm to known working configurations. Original Bug Description Same problem exactly as encountered with Intel 9560 is also happening with Intel 9260. Update to linux-firmware 1.173.8 did not fix the problem. Everything is working fine when using 4.15 kernel, but not for 4.18+ 5.0+. Reference problem: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1829737 You-Sheng Yang advised to do this by email and it fixed my issue, so I think the 9260 driver would need to be updated in the bionic branch (it seems to be updated in newer branches). -- Basically you should try copy the latest firmware (ibt-*) under https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/intel , power off the device completely and power on, then have a check on bluetooth pairing. -- Linux ideapad 5.0.0-20-generic #21~18.04.1-Ubuntu SMP Thu Jun 27 04:04:37 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux OS: Linux Mint 19.1 Tessa x86_64 Host: 81JB Lenovo ideapad 730S-13IWL Wifi/Bluetooth card is Intel 9260 @:/etc$ dmesg | egrep -i 'blue|firm' [0.099619] Spectre V2 : Enabling Restricted Speculation for firmware calls [0.173124] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored [2.379392] [Firmware Bug]: Invalid critical threshold (0) [2.699758] [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_04.bin (v1.4) [6.259427] iwlwifi :73:00.0: loaded firmware version 43.95eb4e97.0 op_mode iwlmvm [6.337749] Bluetooth: Core ver 2.22 [6.337767] Bluetooth: HCI device and connection manager initialized [6.337770] Bluetooth: HCI socket layer initialized [6.337773] Bluetooth: L2CAP socket layer initialized [6.33] Bluetooth: SCO socket layer initialized [6.368073] Bluetooth: hci0: Firmware revision 0.1 build 201 week 49 2017 [7.309936] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [7.309938] Bluetooth: BNEP filters: protocol multicast [7.309943] Bluetooth: BNEP socket layer initialized [ 17.197268] Bluetooth: RFCOMM TTY layer initialized [ 17.197275] Bluetooth: RFCOMM socket layer initialized [ 17.197284] Bluetooth: RFCOMM ver 1.11 [ 104.453159] Bluetooth: hci0: request failed to create LE connection: status 0x0c [ 104.509148] Bluetooth: hci0: request failed to create LE connection: status 0x0c [ 104.551340] Bluetooth: hci0: request failed to create LE connection: status 0x0c [ 104.589338] Bluetooth: hci0: request failed to create LE connection: status 0x0c [ 104.623323] Bluetooth: hci0: request failed to create LE connection: status 0x0c To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1835449/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834464] Re: Missing bluetooth firmware for Intel Wireless-AC 9462/9560
** Tags added: verification-done-disco ** Tags added: verification-done-bionic -- 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/1834464 Title: Missing bluetooth firmware for Intel Wireless-AC 9462/9560 Status in HWE Next: New Status in linux-firmware package in Ubuntu: In Progress Status in linux-firmware source package in Bionic: Fix Committed Status in linux-firmware source package in Cosmic: Fix Committed Status in linux-firmware source package in Disco: Fix Committed Status in linux-firmware source package in Eoan: In Progress Bug description: [Impact] Bluetooth on Intel Wireless-AC 9462/9560 requires new firmware blobs to be enabled. [Fix] Backport newly released firmware blobs from linux-firmware. This will also requires minor change to the WHENCE file to resolve cherry-pick conflicts. B/C/D would requires this explicitly and Eoan should be rebased onto linux-firmware master branch HEAD as usual. [Test Case] Verified with hardware platforms with corresponding devices. Completely power off and power on to trigger firmware reload, check from dmesg to see if Bluetooth firmware has been correctly loaded. [Regression Risk] Low. This adds new binary firmware blobs that are only loaded by targeting hardware. == original bug description == On systems with Intel Wireless-AC 9462/9560 cards, following failed- to-load-firmware kernel messages found: bluetooth hci0: Direct firmware load for intel/ibt-19-32-1.sfi failed with error -2 See also Bug #1833065 for wireless firmware & driver fix. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1834464/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835879] Re: Intel Wireless-AC 9462/9560 not supported on ICL
For linux-firmware part, we'll only need ibt-19-32-0.{sfi,ddc} for 9462
on ICL, which has been committed as
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-
firmware.git/commit/?id=d52556e4592e64023157a83fb0f483661f23ac0e. This
should be backported to B/C/D, and let Eoan to be rebased on latest
upstream HEAD.
** Changed in: linux-firmware (Ubuntu)
Assignee: (unassigned) => You-Sheng Yang (vicamo)
** Changed in: linux-firmware (Ubuntu)
Status: New => In Progress
** Changed in: linux-firmware (Ubuntu Bionic)
Status: New => In Progress
** Changed in: linux-firmware (Ubuntu Cosmic)
Status: New => In Progress
** Changed in: linux-firmware (Ubuntu Disco)
Status: New => In Progress
--
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/1835879
Title:
Intel Wireless-AC 9462/9560 not supported on ICL
Status in HWE Next:
New
Status in linux-firmware package in Ubuntu:
In Progress
Status in linux-oem-osp1 package in Ubuntu:
Fix Committed
Status in linux-firmware source package in Bionic:
In Progress
Status in linux-oem-osp1 source package in Bionic:
Fix Committed
Status in linux-firmware source package in Cosmic:
In Progress
Status in linux-oem-osp1 source package in Cosmic:
Won't Fix
Status in linux-firmware source package in Disco:
In Progress
Status in linux-oem-osp1 source package in Disco:
Won't Fix
Bug description:
[Impact]
Intel Wireless-AC 9560/9462 is not correctly enabled on IceLake
platforms.
[Fix]
Two changes from Intel maintained backport-iwlwifi repository are
necessary to add device ID/configs to iwlwifi driver.
[Test]
Verified on hardware 9462/9560 on IceLake/CometLake platforms.
[Regression Potential]
Low. These changes are part of the series to enable 9462/9560 on
CometLake/IceLake platforms that don't have the support originally.
= Original Bug Description =
Intel Wireless-AC 9462/9560 on CML was previously enabled via bug
1833065, bug 1834415 and bug 1834464. However on ICL, it fails to
startup with following error messages with kernel v5.2-rc7:
iwlwifi :00:14.3: loaded firmware version 48.13675109.0 op_mode iwlmvm
iwlwifi :00:14.3: Detected Intel(R) Wireless-AC 9560, REV=0x338
iwlwifi :00:14.3: Loaded firmware version: 48.13675109.0
iwlwifi :00:14.3: SecBoot CPU1 Status: 0x5c97, CPU2 Status: 0x3
iwlwifi :00:14.3: Failed to start RT ucode: -5
iwlwifi :00:14.3: Collecting data: trigger 16 fired.
iwlwifi :00:14.3: Firmware not running - cannot dump error
iwlwifi :00:14.3: Failed to run INIT ucode: -5
Also tried backport-iwlwifi out-of-tree driver revision 7858 (HEAD at
the moment) with no luck.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1835879/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836188] Re: cpuset_exclusive in controllers from ubuntu_ltp failed on C P9
This is also affecting any script that's calling this cpuset_funcs.sh: * cpuset_base_ops * cpuset_exclusive * cpuset_hierarchy * cpuset_hotplug cpuset_inherit * cpuset_load_balance * cpuset_memory cpuset_memory_pressure * cpuset_memory_spread * cpuset_sched_domains * cpuset_syscall -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1836188 Title: cpuset_exclusive in controllers from ubuntu_ltp failed on C P9 Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Cosmic: Invalid Bug description: This issue was only spotted on node Baltar (P9) This is caused by the return value in: $ cat /sys/devices/system/node/has_normal_memory 0,8 The test was trying to use do arithmetic operation with it, but didn't expect to get a return value with a comma in it. <<>> tag=cpuset_exclusive stime=1562844139 cmdline=" cpuset_exclusive_test.sh" contacts="" analysis=exit <<>> incrementing stop /opt/ltp/testcases/bin/cpuset_exclusive_test.sh: 36: /opt/ltp/testcases/bin/cpuset_funcs.sh: arithmetic expression: expecting EOF: "0,8 + 1" <<>> initiation_status="ok" duration=0 termination_type=exited termination_id=2 corefile=no cutime=0 cstime=0 <<>> Not sure if this is a test case issue, or if we should see a comma in /sys/devices/system/node/has_normal_memory ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-25-generic 4.18.0-25.26 ProcVersionSignature: Ubuntu 4.18.0-25.26-generic 4.18.20 Uname: Linux 4.18.0-25-generic ppc64le AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 11 10:56 seq crw-rw 1 root audio 116, 33 Jul 11 10:56 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu13.4 Architecture: ppc64el ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Thu Jul 11 11:25:40 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0451:80ff Texas Instruments, Inc. Bus 001 Device 004: ID 0557:2419 ATEN International Co., Ltd Bus 001 Device 002: ID 0557:7000 ATEN International Co., Ltd Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub PciMultimedia: ProcFB: 0 astdrmfb ProcKernelCmdLine: root=UUID=acd1a0d7-f6fc-4130-928c-c8b11ad6e4be ro console=hvc0 ProcLoadAvg: 0.74 1.52 0.74 1/1338 6264 ProcLocks: 1: POSIX ADVISORY WRITE 1805 00:17:364 0 EOF 2: POSIX ADVISORY WRITE 3956 00:17:504 0 EOF 3: FLOCK ADVISORY WRITE 3915 00:17:566 0 EOF ProcSwaps: Filename TypeSizeUsedPriority /swap.img file 8388544 0 -2 ProcVersion: Linux version 4.18.0-25-generic (buildd@bos02-ppc64el-009) (gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1~18.10.1)) #26-Ubuntu SMP Mon Jun 24 09:32:46 UTC 2019 RelatedPackageVersions: linux-restricted-modules-4.18.0-25-generic N/A linux-backports-modules-4.18.0-25-generic N/A linux-firmware 1.175.6 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) VarLogDump_list: total 0 cpu_cores: Number of cores present = 40 cpu_coreson: Number of cores online = 39 cpu_dscr: DSCR is 16 cpu_freq: min: 2.862 GHz (cpu 79) max: 2.945 GHz (cpu 83) avg: 2.903 GHz cpu_runmode: Could not retrieve current diagnostics mode, No kernel interface to firmware cpu_smt: SMT=4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1836188/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834904] Re: linux: 4.18.0-26.27 -proposed tracker
4.18.0-26.27 - generic Regression test CMPL, RTB. 56 / 57 tests were run, missing: ubuntu_ltp Issue to note in amd64: ubuntu_kernel_selftests - run_netsocktests (bug 1830016) rtnetlink.sh in net (bug 1812978) psock_snd in net (bug 1812618) ubuntu_kvm_unit_tests - apic timeouted (bug 1748103) apic-split timeouted (bug 1821390) svm (bug 1821903) ubuntu_ltp_syscalls - fanotify09-2 (bug 1804594) sync_file_range02 (bug 1819116) Issue to note in arm64: hwclock - issue for HP m400 (bug 1716603) ubuntu_bpf - Failed sockmap unexpected timeout on ARM64 (bug 1805806) ubuntu_kernel_selftests - cpu-hotplug failed on moonshot (bug 1809701) run_netsocktests (bug 1830016) rtnetlink.sh in net (bug 1812978) psock_snd in net (bug 1812618) ubuntu_kvm_unit_tests - gicv2-mmio-up and gicv2-mmio-3p failed on Moonshot ARM64 (bug 1802492) ubuntu_ltp - binfmt_misc02 (bug 1822246) userns06 (bug 1836162) memcg_stat (bug 1829983) memcg_use_hierarchy (bug 1829989) leapsec_timer (bug 1829971) cpuhotplug03 (bug 1836167) cpuhotplug04 (bug 1836169) cpuhotplug06 (bug 1836170) zram01 (bug 1829991) zram02 (bug 1829992) ubuntu_ltp_syscalls - fanotify09-2 (bug 1804594) sync_file_range02 (bug 1819116) 51 / 52 tests were run, missing: xfstests Issue to note in i386: ubuntu_bpf - Some test in test_verifier failed on i386 Bionic (bug 1788578) ubuntu_btrfs_kernel_fixes - ff76b05 failed (bug 1812988) ubuntu_kernel_selftests - run_netsocktests (bug 1830016) rtnetlink.sh in net (bug 1812978) psock_snd in net (bug 1812618) ubuntu_kvm_smoke_test - timed out waiting for dnsmasq lease (bug 1802056) ubuntu_kvm_unit_tests - eventinj on i386 (bug 1822235) hypercall on i386 (bug 1822235) hyperv_connections on i386 (bug 1822235) hyperv_stimer on i386 (bug 1822235) kvmclock_test on i386 (bug 1822235) msr on i386 (bug 1822235) port80 on i386 (bug 1822235) realmode on i386 (bug 1822235) s3 on i386 (bug 1822235) sieve on i386 (bug 1822235) smap on i386 (bug 1822235) smptest on i386 (bug 1822235) smptest3 on i386 (bug 1822235) taskswitch on i386 (bug 1822235) taskswitch2 on i386 (bug 1822235) tsc on i386 (bug 1822235) tsc_adjust on i386 (bug 1822235) umip on i386 (bug 1822235) vmexit_cpuid on i386 (bug 1822235) vmexit_inl_pmtimer on i386 (bug 1822235) vmexit_ipi on i386 (bug 1822235) vmexit_ipi_halt on i386 (bug 1822235) vmexit_mov_from_cr8 on i386 (bug 1822235) vmexit_mov_to_cr8 on i386 (bug 1822235) vmexit_ple_round_robin on i386 (bug 1822235) vmexit_tscdeadline on i386 (bug 1822235) vmexit_tscdeadline_immed on i386 (bug 1822235) vmexit_vmcall on i386 (bug 1822235) ubuntu_ltp - binfmt_misc02 (bug 1822246) userns06 (bug 1836162) memcg_usage_in_bytes (bug 1829984) memcg_stat (bug 1829983) memcg_use_hierarchy (bug 1829989) leapsec_timer (bug 1829971) zram01 (bug 1829991) zram02 (bug 1829992) ubuntu_ltp_syscalls - fanotify09-2 (bug 1804594) 51 / 53 tests were run, missing: ubuntu_boot, ubuntu_ltp Issue to note in ppc64le (P8): ubuntu_bpf - test_map failed on PowerPC (bug 1802474) ubuntu_btrfs_kernel_fixes - ff76b05 failed (bug 1812988) ubuntu_kernel_selftests - reuseport_bpf_numa in net (bug 1812638) run_netsocktests (bug 1830016) psock_snd in net (bug 1812618) TRACE_syscall.ptrace_syscall_errno in seccomp (bug 1829359) TRACE_syscall.ptrace_syscall_faked in seccomp (bug 1829363) ubuntu_ltp_syscalls - fanotify09-2 (bug 1804594) sync_file_range02 (bug 1819116) xfstests - btrfs shared/007 timeout 52 / 53 tests were run, missing: xfstests Issue to note in ppc64le (P9): hwclock - hwclock test failed on PowerPC due to 0.x sec difference (bug 1802233) ubuntu_bpf - test_map failed on PowerPC (bug 1802474) ubuntu_btrfs_kernel_fixes - ff76b05 failed (bug 1812988) ubuntu_kernel_selftests - reuseport_bpf_numa in net (bug 1812638) run_netsocktests (bug 1830016) psock_snd in net (bug 1812618) TRACE_syscall.ptrace_syscall_errno in seccomp (bug 1829359) TRACE_syscall.ptrace_syscall_faked in seccomp (bug 1829363) ubuntu_ltp - binfmt_misc02 (bug 1822246) userns06 (bug 1836162) cpuset_base_ops cpuset_exclusive cpuset_hierarchy cpuset_hotplug cpuset_inherit cpuset_load_balance cpuset_memory cpuset_memory_pressure cpuset_memory_spread cpuset_sched_domains cpuset_syscall in controller (bug 1836188) leapsec_timer (bug 1829971) zram01 (bug 1829991) zram02 (bug 1829992) ubuntu_ltp_syscalls - fanotify09-2 (bug 1804594) sync_file_range02 (bug 1819116) ubuntu_lxc - network issue 50 / 52 tests were run, missing: ubuntu_btrfs_kernel_fixes, ubuntu_ltp Issue to note in s390x (KVM): ubuntu_bpf - test_verifier in ubuntu_bpf test failed with 'Failed to load prog' on Cosmic s390x (bug 1801033) ubuntu_kernel_selftests - reuseport_dualstack in net (bug 1812843) run_netsocktests (bug 1830016) rtnetlink.sh in net (bug 1812978) msg_zerocopy in net (bug 1812620) psock_snd in net (bug 1812618) TRACE_syscall in ftrace (bug 1812824) ubuntu_ltp_syscalls - fanotify09-2 (bug 1804594) msgstress03 (bug 179734
[Kernel-packages] [Bug 1835879] Re: Intel Wireless-AC 9462/9560 not supported on ICL
https://lists.ubuntu.com/archives/kernel-team/2019-July/102175.html -- 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/1835879 Title: Intel Wireless-AC 9462/9560 not supported on ICL Status in HWE Next: New Status in linux-firmware package in Ubuntu: In Progress Status in linux-oem-osp1 package in Ubuntu: Fix Committed Status in linux-firmware source package in Bionic: In Progress Status in linux-oem-osp1 source package in Bionic: Fix Committed Status in linux-firmware source package in Cosmic: In Progress Status in linux-oem-osp1 source package in Cosmic: Won't Fix Status in linux-firmware source package in Disco: In Progress Status in linux-oem-osp1 source package in Disco: Won't Fix Bug description: [Impact] Intel Wireless-AC 9560/9462 is not correctly enabled on IceLake platforms. [Fix] Two changes from Intel maintained backport-iwlwifi repository are necessary to add device ID/configs to iwlwifi driver. [Test] Verified on hardware 9462/9560 on IceLake/CometLake platforms. [Regression Potential] Low. These changes are part of the series to enable 9462/9560 on CometLake/IceLake platforms that don't have the support originally. = Original Bug Description = Intel Wireless-AC 9462/9560 on CML was previously enabled via bug 1833065, bug 1834415 and bug 1834464. However on ICL, it fails to startup with following error messages with kernel v5.2-rc7: iwlwifi :00:14.3: loaded firmware version 48.13675109.0 op_mode iwlmvm iwlwifi :00:14.3: Detected Intel(R) Wireless-AC 9560, REV=0x338 iwlwifi :00:14.3: Loaded firmware version: 48.13675109.0 iwlwifi :00:14.3: SecBoot CPU1 Status: 0x5c97, CPU2 Status: 0x3 iwlwifi :00:14.3: Failed to start RT ucode: -5 iwlwifi :00:14.3: Collecting data: trigger 16 fired. iwlwifi :00:14.3: Firmware not running - cannot dump error iwlwifi :00:14.3: Failed to run INIT ucode: -5 Also tried backport-iwlwifi out-of-tree driver revision 7858 (HEAD at the moment) with no luck. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1835879/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836153] Re: [18.04 FEAT] zKVM: Add hardware CPU Model - kernel part
** Information type changed from Private to Public -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1836153 Title: [18.04 FEAT] zKVM: Add hardware CPU Model - kernel part Status in Ubuntu on IBM z Systems: Triaged Status in linux package in Ubuntu: New Bug description: Feature request to be applied to Ubuntu 18.04 - kernel. The git commit information is already provided within https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1830239 Once this feature is accepted all information for integration will be provided by IBM kernel 5.2 down to 4.15. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1836153/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1812176] Re: psock_tpacket from the net test in ubuntu_kernel_selftests failed on KVM kernels
Fix applied upstream: ff95bf28c23490584b9d75913a520bb7bb1f2ecb
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1812176
Title:
psock_tpacket from the net test in ubuntu_kernel_selftests failed on
KVM kernels
Status in ubuntu-kernel-tests:
New
Status in linux-kvm package in Ubuntu:
New
Status in linux-kvm source package in Xenial:
New
Status in linux-kvm source package in Bionic:
New
Status in linux-kvm source package in Cosmic:
New
Bug description:
The psock_tpacket in the net test from ubuntu_kernel_selftests failed with
B-KVM
$ sudo ./psock_tpacket
test: TPACKET_V1 with PACKET_RX_RING open: No such file or directory
Look into the code, it seems that this file not found error is caused
by the attempt to access /proc/kallsyms in test_kernel_bit_width():
static int test_kernel_bit_width(void)
{
char in[512], *ptr;
int num = 0, fd;
ssize_t ret;
fd = open("/proc/kallsyms", O_RDONLY);
if (fd == -1) {
perror("open");
exit(1);
}
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-1028-kvm 4.15.0-1028.28
ProcVersionSignature: User Name 4.15.0-1028.28-kvm 4.15.18
Uname: Linux 4.15.0-1028-kvm x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
Date: Thu Jan 17 08:05:47 2019
SourcePackage: linux-kvm
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1812176/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835054] Re: Enable Armada SOCs and MVPP2 NIC driver for disco/generic arm64
V2 resubmitted. https://lists.ubuntu.com/archives/kernel- team/2019-July/102171.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/1835054 Title: Enable Armada SOCs and MVPP2 NIC driver for disco/generic arm64 Status in linux package in Ubuntu: In Progress Status in linux source package in Disco: In Progress Status in linux source package in Eoan: In Progress Bug description: == SRU Justification == The mvpp2 is a driver for network controllers(s) in Marvell SOCs, particularly Armada 8040. However this driver was neither enabled as a module or a built-in for Disco arm64. == Fix == Just like what we did for armhf, set CONFIG_MVPP2 to "m" for arm64 can solve this problem. We need to enable the Armada SOCs support (CONFIG_ARCH_MVEBU) as well to meet the dependency requirement. Other configs were added by the updateconfigs process. == Test == A test kernel for Disco ARM64 could be found here: https://people.canonical.com/~phlin/kernel/lp-1835054-mvpp2/V2/ User has confirmed that the V1 kernel can fix this missing driver issue (V2 is just with CONFIG_ARCH_MULTI_V7 dropped and some configs added explicitly, I have it tested on an ARM64 node, the mvpp2 module can be loaded without any issue). == Regression Potential == Low, this patch just enable the Armada SOCs and make this mvpp2 driver to be built as a module on ARM64, and we already have those for armhf. == Original Bug Report == At least in Ubuntu 19.04, the arm64 kernel (linux-image-5.0.0) is not building CONFIG_MVPP2 (depends on CONFIG_ARCH_MVEBU) - a driver for network controllers(s) in Marvell SOCs, particularly Armada 8040 - neither as a module or a built-in: $ uname -m aarch64 $ grep MVPP2 /boot/config-5.0.0-20-generic $ It makes very hard (and impossible for non-advanced users) to install and use Ubuntu on the Macchiatobin board (http://macchiatobin.net/) - a reasonably priced and performant server/mini-desktop platform. Could it be added, please, and the installer image re-generated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1835054/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834915] Re: linux-fips: 4.4.0-1014.19 -proposed tracker
** Summary changed: - linux-fips: 4.4.0-1014.18 -proposed tracker + linux-fips: 4.4.0-1014.19 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Fix Released => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Status: Fix Released => In Progress ** Changed in: kernel-sru-workflow/prepare-package-signed Status: Fix Released => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1834915 Title: linux-fips: 4.4.0-1014.19 -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: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-signing-to-proposed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: Invalid 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: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1834918 phase: Holding before Promote to Proposed phase-changed: Friday, 12. July 2019 16:09 UTC reason: promote-to-proposed: Pending -- builds not complete in ppa main:failed,meta:building,signed:building variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834915/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1787857] Re: USB mouse cursor lags after random time of correct behaviour
** Attachment added: "USB devices in the system" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787857/+attachment/5277100/+files/lsusb_mouse_lag_ubuntustudio_login_screen.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1787857 Title: USB mouse cursor lags after random time of correct behaviour Status in linux package in Ubuntu: Incomplete Status in rtirq package in Ubuntu: Invalid Bug description: I installed Ubuntu Studio 18.04.1 LTS. After the first apt-get update I noticed the following behaviour: after havig logged in, my USB mouse works normally for about ten seconds, then the cursor starts lagging a lot which makes the mouse pretty much unusable. The last dmesg always contain lines these: (more in attached file) [<9e659b0c>] irq_default_primary_handler threaded [] usb_hcd_irq [<9e659b0c>] irq_default_primary_handler threaded [ ] _rtl_pci_interrupt [rtl_pci] Disabling IRQ #18 Out of frustration & curiosity I disabled most autostart apps (Settings > Session ... > Autostart) and re-enabled them after rebooting. Since then I rarely encounter the lagging cursor. If I open Settings > Mouse & Touchpad and toggle any option on/off the cursor starts lagging. How can make the cursor work reliably? Some comment in dmesg mentions "irqpoll" boot option Ubuntu Studio 18.04.1 4.15.0-20-lowlatency #21-Ubuntu SMP PREEMPT To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787857/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1787857] Re: USB mouse cursor lags after random time of correct behaviour
** Attachment added: "/proc/interrupts output" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787857/+attachment/5277101/+files/proc_interrupts_mouse_lag_ubuntustudio_login_screen.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1787857 Title: USB mouse cursor lags after random time of correct behaviour Status in linux package in Ubuntu: Incomplete Status in rtirq package in Ubuntu: Invalid Bug description: I installed Ubuntu Studio 18.04.1 LTS. After the first apt-get update I noticed the following behaviour: after havig logged in, my USB mouse works normally for about ten seconds, then the cursor starts lagging a lot which makes the mouse pretty much unusable. The last dmesg always contain lines these: (more in attached file) [<9e659b0c>] irq_default_primary_handler threaded [] usb_hcd_irq [<9e659b0c>] irq_default_primary_handler threaded [ ] _rtl_pci_interrupt [rtl_pci] Disabling IRQ #18 Out of frustration & curiosity I disabled most autostart apps (Settings > Session ... > Autostart) and re-enabled them after rebooting. Since then I rarely encounter the lagging cursor. If I open Settings > Mouse & Touchpad and toggle any option on/off the cursor starts lagging. How can make the cursor work reliably? Some comment in dmesg mentions "irqpoll" boot option Ubuntu Studio 18.04.1 4.15.0-20-lowlatency #21-Ubuntu SMP PREEMPT To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787857/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1787857] Re: USB mouse cursor lags after random time of correct behaviour
I just saw this right at boot. The mouse was lagging already at the login screen. And the login screen took around 10 seconds to show up after the first two lines of kernel boot messages. (Usually takes around 2 seconds). ** Attachment added: "dmesg_mouse_lag_ubuntustudio_login_screen.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787857/+attachment/5277099/+files/dmesg_mouse_lag_ubuntustudio_login_screen.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1787857 Title: USB mouse cursor lags after random time of correct behaviour Status in linux package in Ubuntu: Incomplete Status in rtirq package in Ubuntu: Invalid Bug description: I installed Ubuntu Studio 18.04.1 LTS. After the first apt-get update I noticed the following behaviour: after havig logged in, my USB mouse works normally for about ten seconds, then the cursor starts lagging a lot which makes the mouse pretty much unusable. The last dmesg always contain lines these: (more in attached file) [<9e659b0c>] irq_default_primary_handler threaded [] usb_hcd_irq [<9e659b0c>] irq_default_primary_handler threaded [ ] _rtl_pci_interrupt [rtl_pci] Disabling IRQ #18 Out of frustration & curiosity I disabled most autostart apps (Settings > Session ... > Autostart) and re-enabled them after rebooting. Since then I rarely encounter the lagging cursor. If I open Settings > Mouse & Touchpad and toggle any option on/off the cursor starts lagging. How can make the cursor work reliably? Some comment in dmesg mentions "irqpoll" boot option Ubuntu Studio 18.04.1 4.15.0-20-lowlatency #21-Ubuntu SMP PREEMPT To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787857/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1785964] Re: Unable to unlock the desktop session: systemd-logind: got pause for 13:69
I added a systemd unit to stop autofs before going into suspend and start autofs again after resume. I haven't had any freezes with gdm3 anymore. But there is still a difference between Ethernet and Wifi. When connected to Wifi, it takes some seconds longer to unlock the user session. It seems gdm3 is waiting for an active network sonnection. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1785964 Title: Unable to unlock the desktop session: systemd-logind: got pause for 13:69 Status in linux package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Confirmed Bug description: When this issue happens, you won't be able to unlock your desktop session (VT works fine). This happened twice today for me, one is after a suspend, one is just a screen lock. Not sure what is the trigger yet. Syndrome: On the login screen after typing the correct password, you will see a small circle keep spinning and that's it. I need to restart my computer to get it back to normal. In the syslog this error message looks fishy: Aug 8 10:44:57 Leggiero gnome-shell[2118]: g_array_unref: assertion 'array' failed This is part of the syslog fetching from a VT after a GUI unlock attempt (session 24 is the desktop login attempt): Aug 8 10:44:42 Leggiero systemd[1]: Started Session 24 of user sam. Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) systemd-logind: got resume for 226:0 Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) AIGLX: Resuming AIGLX clients after VT switch Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) modeset(0): EDID vendor "AUO", prod id 4204 Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) modeset(0): Printing DDC gathered Modelines: Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) modeset(0): Modeline "1366x768"x0.0 76.20 1366 1404 1426 1590 768 771 777 798 +hsync -vsync (47.9 kHz eP) Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) modeset(0): Modeline "1366x768"x0.0 76.20 1366 1404 1426 1988 768 771 777 798 +hsync -vsync (38.3 kHz e) Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) systemd-logind: got resume for 13:78 Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event14 - Dell WMI hotkeys: is tagged by udev as: Keyboard Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event14 - Dell WMI hotkeys: device is a keyboard Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) systemd-logind: got resume for 13:66 Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event2 - Sleep Button: is tagged by udev as: Keyboard Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event2 - Sleep Button: device is a keyboard Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) systemd-logind: got resume for 13:79 Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event15 - Integrated_Webcam_HD: Integrate: is tagged by udev as: Keyboard Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event15 - Integrated_Webcam_HD: Integrate: device is a keyboard Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) systemd-logind: got resume for 13:68 Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event4 - AT Translated Set 2 keyboard: is tagged by udev as: Keyboard Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event4 - AT Translated Set 2 keyboard: device is a keyboard Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) systemd-logind: got resume for 13:67 Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event3 - Power Button: is tagged by udev as: Keyboard Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event3 - Power Button: device is a keyboard Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) systemd-logind: got resume for 13:71 Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event7 - AlpsPS/2 ALPS GlidePoint: is tagged by udev as: Touchpad Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event7 - AlpsPS/2 ALPS GlidePoint: device is a touchpad Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) systemd-logind: got resume for 13:72 Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event8 - DELL Wireless hotkeys: is tagged by udev as: Keyboard Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event8 - DELL Wireless hotkeys: device is a keyboard Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) libinput: PixArt Microsoft USB Optical Mouse: SetProperty on 286 called but device is disabled. Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: This driver
[Kernel-packages] [Bug 1829749] Re: [MIR] Please add support for SIPL
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1829749
Title:
[MIR] Please add support for SIPL
Status in Launchpad itself:
Fix Released
Status in linux package in Ubuntu:
New
Status in linux-signed package in Ubuntu:
New
Status in s390-tools package in Ubuntu:
Fix Released
Status in s390-tools-signed package in Ubuntu:
Fix Released
Bug description:
Please add support for zipl ("z/ecureBoot") signing.
It should be similar to opal signing, but using the new zipl signing
key.
I am expecting to sign s390-tools stage3.bin and kernel images using
this key.
s390-tools -> can be signed already
kernels -> should only sign v5.2+
To manage notifications about this bug go to:
https://bugs.launchpad.net/launchpad/+bug/1829749/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828596] Comment bridged from LTC Bugzilla
--- Comment From hbath...@in.ibm.com 2019-07-15 06:36 EDT--- Cascardo, I did not tinker with other options but disabling ratelimit helped: "StartLimitInterval=0" "systemctl reset-failed kdump-tools.service" seems like a good option but may not be needed if ratelimit is disabled.. Thanks Hari -- 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/1828596 Title: kdump fails when crash is triggered after DLPAR cpu add operation Status in The Ubuntu-power-systems project: Incomplete Status in kexec-tools package in Ubuntu: Invalid Status in makedumpfile package in Ubuntu: Fix Released Status in kexec-tools source package in Xenial: New Status in makedumpfile source package in Xenial: New Status in kexec-tools source package in Bionic: New Status in makedumpfile source package in Bionic: New Status in kexec-tools source package in Cosmic: New Status in makedumpfile source package in Cosmic: New Status in kexec-tools source package in Disco: New Status in makedumpfile source package in Disco: New Status in kexec-tools source package in Eoan: Invalid Status in makedumpfile source package in Eoan: Fix Released Bug description: [Impact] After a CPU add/hotplug operation on Power systems, kdump will fail after a crash. The kdump kernel needs to be reloaded after a CPU add/hotplug. [Test case] Do CPU add/hotplug, trigger a crash, and check for a successful kdump. [Regression potential] Multiple reloads caused by multiple sequential CPU adds may cause spurious log results, and systemd may fail to properly reload the kdump kernel. == Comment: #0 - Hari Krishna Bathini - 2019-05-10 05:55:40 == ---Problem Description--- kdump fails when crash is triggered after CPU add operation. Machine Type = na ---System Hang--- Crashed in early boot process of kdump kernel after crash Had to issue system reset from HMC to reclaim ---Steps to Reproduce--- 1. Configure kdump. 2. Add cpu from HMC. 3. Trigger crash. 4. Machine hangs after crash as below: --- [169250.213166] IPI complete [169250.234331] kexec: Starting switchover sequence. I'm in purgatory --- STRUCK HERE --- ---uname output--- na ---Debugger--- A debugger is not configured == Comment: #1 - Hari Krishna Bathini - 2019-05-10 05:56:46 == The problem is, kexec udev rule to restart kdump-tools service - when a core is added, is not being triggered. The old DT created by kexec (before the core is added) is being used by KDump Kernel. So, when system crashes on a thread from the added core(s), KDump kernel is failing to get the 'boot_cpuid' and eventually failing to boot.. == Comment: #2 - Hari Krishna Bathini - 2019-05-10 06:02:27 == The udev rule when CPU is added is not triggered because ppc64 does not eject add/remove event when a CPU is hot added/removed. It only ejects online/offline event to user space when CPU is hot added/removed. So, the below udev rules are never triggered when needed: SUBSYSTEM=="cpu", ACTION=="add", PROGRAM="/bin/systemctl try-restart kdump-tools.service" SUBSYSTEM=="cpu", ACTION=="remove", PROGRAM="/bin/systemctl try-restart kdump-tools.service" Also, with how CPU hot add & remove are handled in ppc64, a udev trigger to reload kdump after CPU is hot removed is NOT necessary. So, fix the CPU hot add case by updating the udev rule and drop the udev rule meant for CPU hot remove in the kdump udev rules file: SUBSYSTEM=="cpu", ACTION=="online", PROGRAM="/bin/systemctl try- restart kdump-tools.service" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1828596/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834915] Re: linux-fips: 4.4.0-1014.19 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1834918 - phase: Holding before Promote to Proposed - phase-changed: Friday, 12. July 2019 16:09 UTC + phase: Packaging + phase-changed: Monday, 15. July 2019 10:38 UTC reason: - promote-to-proposed: Pending -- builds not complete in ppa main:failed,meta:building,signed:building + prepare-package: Pending -- package not yet uploaded + prepare-package-signed: Pending -- package not yet uploaded variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1834915 Title: linux-fips: 4.4.0-1014.19 -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: In Progress Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-signing-to-proposed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: Invalid 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: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1834918 phase: Packaging phase-changed: Monday, 15. July 2019 10:38 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-signed: Pending -- package not yet uploaded variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834915/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829749] 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 1829749
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/1829749
Title:
[MIR] Please add support for SIPL
Status in Launchpad itself:
Fix Released
Status in linux package in Ubuntu:
Incomplete
Status in linux-signed package in Ubuntu:
New
Status in s390-tools package in Ubuntu:
Fix Released
Status in s390-tools-signed package in Ubuntu:
Fix Released
Bug description:
Please add support for zipl ("z/ecureBoot") signing.
It should be similar to opal signing, but using the new zipl signing
key.
I am expecting to sign s390-tools stage3.bin and kernel images using
this key.
s390-tools -> can be signed already
kernels -> should only sign v5.2+
To manage notifications about this bug go to:
https://bugs.launchpad.net/launchpad/+bug/1829749/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836497] Re: https://kernel.ubuntu.com/~kernel-ppa/mainline fails i386 and amd64 builds
*** This bug is a duplicate of bug 1830961 ***
https://bugs.launchpad.net/bugs/1830961
** This bug has been marked a duplicate of bug 1830961
Kernels & kernel drivers fail to build with gcc-9 [error:
‘-mindirect-branch’ and ‘-fcf-protection’ are not compatible]
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1836497
Title:
https://kernel.ubuntu.com/~kernel-ppa/mainline fails i386 and amd64
builds
Status in linux package in Ubuntu:
Incomplete
Bug description:
84 | {
| ^
/home/kernel/COD/linux/scripts/mod/devicetable-offsets.c: In function 'main':
/home/kernel/COD/linux/scripts/mod/devicetable-offsets.c:10:1: error:
'-mindirect-branch' and '-fcf-protection' are not compatible
10 | {
| ^
make[4]: *** [/home/kernel/COD/linux/scripts/Makefile.build:112:
scripts/mod/devicetable-offsets.s] Error 1
make[3]: *** [/home/kernel/COD/linux/Makefile:1117: prepare0] Error 2
make[2]: *** [/home/kernel/COD/linux/Makefile:325: __build_one_by_one] Error 2
make[2]: Leaving directory '/home/kernel/COD/linux/debian/build/build-generic'
make[1]: *** [Makefile:179: sub-make] Error 2
make[1]: Leaving directory '/home/kernel/COD/linux'
make: *** [debian/rules.d/2-binary-arch.mk:34:
/home/kernel/COD/linux/debian/stamps/stamp-prepare-tree-generic] Error 2
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836497/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834915] Re: linux-fips: 4.4.0-1014.19 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-signed Status: In Progress => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1834918 - phase: Packaging - phase-changed: Monday, 15. July 2019 10:38 UTC + phase: Holding before Promote to Proposed + phase-changed: Monday, 15. July 2019 11:08 UTC reason: - prepare-package: Pending -- package not yet uploaded - prepare-package-signed: Pending -- package not yet uploaded + promote-to-proposed: Ongoing -- builds not complete in ppa main:building,meta:building,signed:building variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1834915 Title: linux-fips: 4.4.0-1014.19 -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 prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: Invalid 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: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1834918 phase: Holding before Promote to Proposed phase-changed: Monday, 15. July 2019 11:08 UTC reason: promote-to-proposed: Ongoing -- builds not complete in ppa main:building,meta:building,signed:building variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834915/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1783267] Re: linux-modules-extra breaks virtualbox guest modules
This looks like a regression in the kernel builtin module, nothing I can fix in virtualbox side. There have been breaking changes in newer 5.2+ virtualbox kernel modules, I suggest to avoid having them in 16.04, and to move to 18.04 if you want a newer codebase ** Changed in: virtualbox-hwe (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1783267 Title: linux-modules-extra breaks virtualbox guest modules Status in linux package in Ubuntu: Confirmed Status in virtualbox-hwe package in Ubuntu: Invalid Bug description: linux-modules-extra-4.15.0-29-generic installs virtualbox guest modules that are newer than what virtualbox-guest-dkms-hwe provides (5.2.8 vs 5.1.34): $ modinfo /lib/modules/4.15.0-29-generic/kernel/drivers/staging/vboxvideo/vboxvideo.ko filename: /lib/modules/4.15.0-29-generic/kernel/drivers/staging/vboxvideo/vboxvideo.ko license:GPL and additional rights description:Oracle VM VirtualBox Graphics Card author: Oracle Corporation srcversion: 689EDF1E50DE15779B4F930 alias: pci:v80EEdBEEFsv*sd*bc*sc*i* depends:drm,drm_kms_helper,ttm staging:Y retpoline: Y intree: Y name: vboxvideo vermagic: 4.15.0-29-generic SMP mod_unload parm: modeset:Disable/Enable modesetting (int) $ modinfo /lib/modules/4.15.0-29-generic/kernel/ubuntu/vbox/vboxsf/vboxsf.ko filename: /lib/modules/4.15.0-29-generic/kernel/ubuntu/vbox/vboxsf/vboxsf.ko version:5.2.8_KernelUbuntu r120774 alias: fs-vboxsf license:GPL author: Oracle Corporation description:Oracle VM VirtualBox VFS Module for Host File System Access srcversion: AF89497125574B5225F9B6A depends:vboxguest retpoline: Y intree: Y name: vboxsf vermagic: 4.15.0-29-generic SMP mod_unload parm: follow_symlinks:Let host resolve symlinks rather than showing them (int) $ modinfo /lib/modules/4.15.0-29-generic/kernel/ubuntu/vbox/vboxguest/vboxguest.ko filename: /lib/modules/4.15.0-29-generic/kernel/ubuntu/vbox/vboxguest/vboxguest.ko version:5.2.8_KernelUbuntu r120774 license:GPL description:Oracle VM VirtualBox Guest Additions for Linux Module author: Oracle Corporation srcversion: F2E5886E3B0544500D404A1 alias: pci:v80EEdCAFEsvsdbc*sc*i* depends: retpoline: Y intree: Y name: vboxguest vermagic: 4.15.0-29-generic SMP mod_unload Thus installation with dkms fails (while attempting `apt-get install --reinstall virtualbox-guest-dkms-hwe`): Building initial module for 4.15.0-29-generic Done. vboxguest: Running module version sanity check. Error! Module version 5.1.34_Ubuntu for vboxguest.ko is not newer than what is already found in kernel 4.15.0-29-generic (5.2.8_KernelUbuntu). You may override by specifying --force. vboxsf.ko: Running module version sanity check. Error! Module version 5.1.34_Ubuntu for vboxsf.ko is not newer than what is already found in kernel 4.15.0-29-generic (5.2.8_KernelUbuntu). You may override by specifying --force. vboxvideo.ko: Running module version sanity check. - Original module - Installation - Installing to /lib/modules/4.15.0-29-generic/updates/dkms/ depmod DKMS: install completed. My system does not start correctly with kernel 4.15 and I had to fall back to 4.13 which has working virtualbox guest modules. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-modules-extra-4.15.0-29-generic 4.15.0-29.31~16.04.1 ProcVersionSignature: Ubuntu 4.13.0-45.50~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-45-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: MATE Date: Tue Jul 24 08:33:57 2018 InstallationDate: Installed on 2015-02-04 (1265 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) SourcePackage: linux-hwe UpgradeStatus: Upgraded to xenial on 2016-08-02 (720 days ago) --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dyslimet 3006 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=c045d946-13ab-48d3-afa0-2496f98eb0a4 InstallationDate: Installed on 2015-02-04 (1266 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) IwConfig: lono wireless extensions. eth0 no wireless extensions. docker0 no wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Devi
[Kernel-packages] [Bug 1836372] Re: Update firmware in nic-firmware udeb for 5.0 hwe kernel
Confirmed that the new files are now present in nic- firmware_1.173.9_all.udeb, marking verification done. ** Tags added: verification-done-bionic -- 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/1836372 Title: Update firmware in nic-firmware udeb for 5.0 hwe kernel Status in linux-firmware package in Ubuntu: Fix Committed Status in linux-firmware source package in Bionic: Fix Committed Bug description: SRU Justification Impact: Recent updates to linux-firmware means that there are new and updated firmware files relevant to the 5.0 hwe kernel from disco. Adding these files to give a better install experience for the 18.04.3 release. Fix: Add the new firmware files to the nic-firmware udeb. Test Case: Confirm that the new files are present in the nic-firmware udeb. Regression Potential: New firmware versions could contain regressions. These versions have already been released into bionic with no reported regressions though, and are known to fix actual problems, so the benefit seems to outweigh the potential risk. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1836372/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834944] Re: linux-fips: 4.15.0-1012.13 -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) => Andy Whitcroft (apw) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1834944 Title: linux-fips: 4.15.0-1012.13 -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 prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: New Status in Kernel SRU Workflow promote-to-proposed series: In Progress Status in Kernel SRU Workflow promote-to-security series: Invalid 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: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1834954 phase: Ready for Promote to Proposed phase-changed: Friday, 12. July 2019 16:12 UTC reason: promote-to-proposed: Pending -- ready for review variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834944/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1787857] Re: USB mouse cursor lags after random time of correct behaviour
I tried now with 'linux-generic' package (provides currently linux- image-5.0.0-20-generic). I did not experience any mouse lag issues, upon any successful* boot. So in that sense this is 0/10 reproducible with 'generic' kernel variant. With 'lowlatency' kernel the mouse lag issue is roughly 5/10. *) NOTE: with 'generic'-kernel I saw i2c-2 device NAK errors at startup boot messages, and sometimes the boot froze at that point. I checked with the 'i2cdetect' tool and the listing for device 2 showed "nvkm". Howwever, I saw the i2c-2 NAK errors during successful boots as well. With 'lowlatency' kernel I did not see the i2c NAK-errors at all, but the dmesg in mouse lag case shows "nvkm" in it... So, could this be related to KMS 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/1787857 Title: USB mouse cursor lags after random time of correct behaviour Status in linux package in Ubuntu: Incomplete Status in rtirq package in Ubuntu: Invalid Bug description: I installed Ubuntu Studio 18.04.1 LTS. After the first apt-get update I noticed the following behaviour: after havig logged in, my USB mouse works normally for about ten seconds, then the cursor starts lagging a lot which makes the mouse pretty much unusable. The last dmesg always contain lines these: (more in attached file) [<9e659b0c>] irq_default_primary_handler threaded [] usb_hcd_irq [<9e659b0c>] irq_default_primary_handler threaded [ ] _rtl_pci_interrupt [rtl_pci] Disabling IRQ #18 Out of frustration & curiosity I disabled most autostart apps (Settings > Session ... > Autostart) and re-enabled them after rebooting. Since then I rarely encounter the lagging cursor. If I open Settings > Mouse & Touchpad and toggle any option on/off the cursor starts lagging. How can make the cursor work reliably? Some comment in dmesg mentions "irqpoll" boot option Ubuntu Studio 18.04.1 4.15.0-20-lowlatency #21-Ubuntu SMP PREEMPT To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787857/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835345] Re: [Intel CyclonePeak] Can not turn on BT after turn off (via Hotkey)
@AceLan: Why did you change the status to fix released when the packages are still in proposed? Setting them back to fix committed. If you want the package to release you need to mark verification done, not change the status. ** Changed in: linux-firmware (Ubuntu Bionic) Status: Fix Released => Fix Committed ** Changed in: linux-firmware (Ubuntu Disco) Status: Fix Released => Fix Committed -- 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/1835345 Title: [Intel CyclonePeak] Can not turn on BT after turn off (via Hotkey) Status in HWE Next: New Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Bionic: Fix Committed Status in linux-firmware source package in Disco: Fix Committed Bug description: [Impact] BT fails to enable again after disabled it by hotkey with the following message Bus 001 Device 004: ID 8087:0029 Intel Corp. [248987.643125] usb 1-10: device descriptor read/64, error -110 [249003.247721] usb 1-10: device descriptor read/64, error -110 [249003.483611] usb 1-10: reset full-speed USB device number 4 using xhci_hcd [249018.855466] usb 1-10: device descriptor read/64, error -110 [249034.467589] usb 1-10: device descriptor read/64, error -110 [249034.703574] usb 1-10: reset full-speed USB device number 4 using xhci_hcd [249045.299399] usb 1-10: device not accepting address 4, error -62 [249045.427510] usb 1-10: reset full-speed USB device number 4 using xhci_hcd [249050.675715] usb 1-10: Device not responding to setup address. [249050.883541] usb 1-10: device not accepting address 4, error -71 [Fix] Found the updated firmware fixes the issue [Test] Verify on the machine couple days, and can't duplicate the issue anymore. [Regression Potential] Low, the system keeps running for 5 days, and pass s3 tests 30 times, everything works well. [Misc] The firmware for the wifi/bt card is intel/ibt-20-0-3.*, but intel/ibt-20-0-4.* have identical md5sum. To avoid the following new cards require the new fw_revision, so SRU both of them. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1835345/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834886] Re: linux-aws: 5.0.0-1011.12 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Incomplete => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1835782 (bionic/linux-aws-edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834902 - phase: Testing - phase-changed: Wednesday, 03. July 2019 12:01 UTC + phase: Ready for Testing + phase-changed: Monday, 15. July 2019 12:35 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Stalled -- testing FAILED regression-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1834886 Title: linux-aws: 5.0.0-1011.12 -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 promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Disco: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1835782 (bionic/linux-aws-edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834902 phase: Ready for Testing phase-changed: Monday, 15. July 2019 12:35 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834886/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835580] Re: Disco update: 5.0.16 upstream stable release
** Changed in: linux (Ubuntu Disco) Status: New => In Progress ** Changed in: linux (Ubuntu Disco) Assignee: (unassigned) => Stefan Bader (smb) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1835580 Title: Disco update: 5.0.16 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Disco: In Progress 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 following upstream stable patches should be included in the Ubuntu kernel: 5.0.16 upstream stable release from git://git.kernel.org/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1835580/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834944] Re: linux-fips: 4.15.0-1012.13 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1834954 - phase: Ready for Promote to Proposed - phase-changed: Friday, 12. July 2019 16:12 UTC + phase: Promote to Proposed + phase-changed: Monday, 15. July 2019 12:41 UTC reason: - promote-to-proposed: Pending -- ready for review + promote-to-proposed: Ongoing -- review in progress variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1834944 Title: linux-fips: 4.15.0-1012.13 -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 prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: New Status in Kernel SRU Workflow promote-to-proposed series: In Progress Status in Kernel SRU Workflow promote-to-security series: Invalid 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: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1834954 phase: Promote to Proposed phase-changed: Monday, 15. July 2019 12:41 UTC reason: promote-to-proposed: Ongoing -- review in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834944/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834944] Re: linux-fips: 4.15.0-1012.13 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: In Progress => Fix Committed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1834954 phase: Promote to Proposed phase-changed: Monday, 15. July 2019 12:41 UTC reason: - promote-to-proposed: Ongoing -- review in progress + promote-signing-to-proposed: Ongoing -- builds not complete in Signing signed:building + promote-to-proposed: Pending -- packages copied to Signing signed:building variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1834944 Title: linux-fips: 4.15.0-1012.13 -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 prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: New Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: Invalid 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: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1834954 phase: Promote to Proposed phase-changed: Monday, 15. July 2019 12:41 UTC reason: promote-signing-to-proposed: Ongoing -- builds not complete in Signing signed:building promote-to-proposed: Pending -- packages copied to Signing signed:building variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834944/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836577] [NEW] Disco update: 5.0.17 upstream stable release
Public bug reported: 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 following upstream stable patches should be included in the Ubuntu kernel: 5.0.17 upstream stable release from git://git.kernel.org/ ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Disco) Importance: Medium Assignee: Stefan Bader (smb) Status: In Progress ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Disco) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Disco) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Disco) Status: New => In Progress ** Changed in: linux (Ubuntu Disco) Assignee: (unassigned) => Stefan Bader (smb) ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1836577 Title: Disco update: 5.0.17 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Disco: In Progress 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 following upstream stable patches should be included in the Ubuntu kernel: 5.0.17 upstream stable release from git://git.kernel.org/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836577/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835580] Re: Disco update: 5.0.16 upstream stable release
Already applied for CVE-2018-12126, CVE-2018-12127, CVE-2018-12130: - "x86/msr-index: Cleanup bit defines" - "x86/speculation: Consolidate CPU whitelists" - "x86/speculation/mds: Add basic bug infrastructure for MDS" - "x86/speculation/mds: Add BUG_MSBDS_ONLY" - "x86/kvm: Expose X86_FEATURE_MD_CLEAR to guests" - "x86/speculation/mds: Add mds_clear_cpu_buffers()" - "x86/speculation/mds: Clear CPU buffers on exit to user" - "x86/kvm/vmx: Add MDS protection when L1D Flush is not active" - "x86/speculation/mds: Conditionally clear CPU buffers on idle entry" - "x86/speculation/mds: Add mitigation control for MDS" - "x86/speculation/mds: Add sysfs reporting for MDS" - "x86/speculation/mds: Add mitigation mode VMWERV" - "Documentation: Move L1TF to separate directory" - "Documentation: Add MDS vulnerability documentation" - "x86/speculation/mds: Add mds=full,nosmt cmdline option" - "x86/speculation: Move arch_smt_update() call to after mitigation decisions" - "x86/speculation/mds: Add SMT warning message" - "x86/speculation/mds: Fix comment" - "x86/speculation/mds: Print SMT vulnerable on MSBDS with mitigations off" - "cpu/speculation: Add 'mitigations=' cmdline option" - "x86/speculation: Support 'mitigations=' cmdline option" - "powerpc/speculation: Support 'mitigations=' cmdline option" - "s390/speculation: Support 'mitigations=' cmdline option" - "x86/speculation/mds: Add 'mitigations=' support for MDS" Already applied for CVE-2019-11091: - "x86/mds: Add MDSUM variant to the MDS documentation" Already applied for CVE-2018-12126, CVE-2018-12127, CVE-2018-12130, CVE-2019-11091: - "Documentation: Correct the possible MDS sysfs values" - "x86/speculation/mds: Fix documentation typo" This upstream stable already was completely applied for security. ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-12126 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-12127 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-12130 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-11091 ** Changed in: linux (Ubuntu Disco) 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/1835580 Title: Disco update: 5.0.16 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Disco: 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 following upstream stable patches should be included in the Ubuntu kernel: 5.0.16 upstream stable release from git://git.kernel.org/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1835580/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836202] Re: bionic/linux-gke-5.0: 5.0.0-1011.11~18.04.1 -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) => Andy Whitcroft (apw) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1836202 Title: bionic/linux-gke-5.0: 5.0.0-1011.11~18.04.1 -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 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 verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1836201 (gke-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834891 phase: Promote to Proposed phase-changed: Monday, 15. July 2019 13:10 UTC reason: promote-to-proposed: Ongoing -- review in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1836202/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836202] Re: bionic/linux-gke-5.0: 5.0.0-1011.11~18.04.1 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1836201 (gke-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834891 - phase: Ready for Promote to Proposed - phase-changed: Friday, 12. July 2019 14:13 UTC + phase: Promote to Proposed + phase-changed: Monday, 15. July 2019 13:10 UTC reason: - promote-to-proposed: Pending -- ready for review + promote-to-proposed: Ongoing -- review in progress variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1836202 Title: bionic/linux-gke-5.0: 5.0.0-1011.11~18.04.1 -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 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 verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1836201 (gke-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834891 phase: Promote to Proposed phase-changed: Monday, 15. July 2019 13:10 UTC reason: promote-to-proposed: Ongoing -- review in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1836202/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834944] Re: linux-fips: 4.15.0-1012.13 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1834954 phase: Promote to Proposed phase-changed: Monday, 15. July 2019 12:41 UTC reason: - promote-signing-to-proposed: Ongoing -- builds not complete in Signing signed:building - promote-to-proposed: Pending -- packages copied to Signing signed:building + promote-signing-to-proposed: Pending -- builds not complete in Signing signed:retry-needed + promote-to-proposed: Pending -- packages copied to Signing signed:retry-needed variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1834944 Title: linux-fips: 4.15.0-1012.13 -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 prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: New Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: Invalid 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: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1834954 phase: Promote to Proposed phase-changed: Monday, 15. July 2019 12:41 UTC reason: promote-signing-to-proposed: Pending -- builds not complete in Signing signed:retry-needed promote-to-proposed: Pending -- packages copied to Signing signed:retry-needed variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834944/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836577] Re: Disco update: 5.0.17 upstream stable release
Applied with fuzz 1 (verified): "x86/reboot, efi: Use EFI reboot for Acer TravelMate X514-51T". Already applied for bug #1825777: "selftests/net: correct the return value for run_netsocktests". Already applied for bug #1822871: "arm64/module: ftrace: deal with place relative nature of PLTs". Already applied for bug #1830815: "RDMA/hns: Bugfix for mapping user db". ** Description changed: + SRU Justification - 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 following upstream + stable patches should be included in the Ubuntu kernel: - 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 following upstream -stable patches should be included in the Ubuntu kernel: + 5.0.17 upstream stable release + from git://git.kernel.org/ -5.0.17 upstream stable release -from git://git.kernel.org/ + The following patches were applied: + * bfq: update internal depth state when queue depth changes + * platform/x86: sony-laptop: Fix unintentional fall-through + * platform/x86: thinkpad_acpi: Disable Bluetooth for some machines + * platform/x86: dell-laptop: fix rfkill functionality + * hwmon: (pwm-fan) Disable PWM if fetching cooling data fails + * hwmon: (occ) Fix extended status bits + * selftests/seccomp: Handle namespace failures gracefully + * kernfs: fix barrier usage in __kernfs_new_node() + * virt: vbox: Sanity-check parameter types for hgcm-calls coming from userspace + * USB: serial: fix unthrottle races + * iio: adc: xilinx: fix potential use-after-free on remove + * iio: adc: xilinx: fix potential use-after-free on probe + * iio: adc: xilinx: prevent touching unclocked h/w on remove + * acpi/nfit: Always dump _DSM output payload + * libnvdimm/namespace: Fix a potential NULL pointer dereference + * HID: input: add mapping for Expose/Overview key + * HID: input: add mapping for keyboard Brightness Up/Down/Toggle keys + * HID: input: add mapping for "Toggle Display" key + * libnvdimm/btt: Fix a kmemdup failure check + * s390/dasd: Fix capacity calculation for large volumes + * mac80211: fix unaligned access in mesh table hash function + * mac80211: Increase MAX_MSG_LEN + * cfg80211: Handle WMM rules in regulatory domain intersection + * mac80211: fix memory accounting with A-MSDU aggregation + * nl80211: Add NL80211_FLAG_CLEAR_SKB flag for other NL commands + * libnvdimm/security: provide fix for secure-erase to use zero-key + * libnvdimm/pmem: fix a possible OOB access when read and write pmem + * tools/testing/nvdimm: Retain security state after overwrite + * s390/3270: fix lockdep false positive on view->lock + * drm/ttm: fix dma_fence refcount imbalance on error path + * drm/amd/display: extending AUX SW Timeout + * clocksource/drivers/npcm: select TIMER_OF + * clocksource/drivers/oxnas: Fix OX820 compatible + * selftests: fib_tests: Fix 'Command line is not complete' errors + * drm/amdgpu: shadow in shadow_list without tbo.mem.start cause page fault + in sriov TDR + * mISDN: Check address length before reading address family + * vxge: fix return of a free'd memblock on a failed dma mapping + * qede: fix write to free'd pointer error and double free of ptp + * afs: Unlock pages for __pagevec_release() + * afs: Fix in-progess ops to ignore server-level callback invalidation + * qed: Delete redundant doorbell recovery types + * qed: Fix the doorbell address sanity check + * qed: Fix missing DORQ attentions + * qed: Fix the DORQ's attentions handling + * drm/amd/display: If one stream full updates, full update all planes + * s390/pkey: add one more argument space for debug feature entry + * x86/build/lto: Fix truncated .bss with -fdata-sections + * x86/mm: Prevent bogus warnings with "noexec=off" + * x86/reboot, efi: Use EFI reboot for Acer TravelMate X514-51T + * KVM: nVMX: always use early vmcs check when EPT is disabled + * KVM: fix spectrev1 gadgets + * KVM: x86: avoid misreporting level-triggered irqs as edge-triggered in tracing + * tools lib traceevent: Fix missing equality check for strcmp + * perf top: Always sample time to satisfy needs of use of ordered queuing + * ipmi: ipmi_si_hardcode.c: init si_type array to fix a crash + * ocelot: Don't sleep in atomic context (irqs_disabled()) + * perf tools: Fix map reference counting + * scsi: aic7xxx: fix EISA support + * slab: store tagged freelist for off-slab slabmgmt + * mm/ho
[Kernel-packages] [Bug 1828948] Re: OBSOLETE_BY in DKMS.CONF does not work
Hello Alex, or anyone else affected, Accepted dkms into disco-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/dkms/2.6.1-4ubuntu2.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-disco to verification-done-disco. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-disco. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: dkms (Ubuntu Disco) Status: New => Fix Committed ** Tags added: verification-needed-disco -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1828948 Title: OBSOLETE_BY in DKMS.CONF does not work Status in DKMS: Fix Released Status in OEM Priority Project: Fix Committed Status in dkms package in Ubuntu: Fix Released Status in dkms source package in Bionic: Fix Committed Status in dkms source package in Disco: Fix Committed Bug description: [Impact] OBSOLETE_BY in DKMS.CONF not work Which also be reported on upstream: https://github.com/dell/dkms/issues/81 [Test case] 1. add OBSOLETE_BY in DKMS.CONF e.g. OBSOLETE_BY="4.15.0-1033" 2. the kernel module should not be built with kernel greater than the version specified by OBSOLETE_BY e.g. - user install kernel 4.15.0-1030 and 4.15.0-10360 - user install kernel oem-wifi-qualcomm-ath10k-lp1803647-4.15-dkms [1] which has OBSOLETE_BY="4.15.0-1033" - the kernel module from dkms [1] should only built for 4.15.0-1030, but not for 4.15.0-10360 [Regression potential] None as it used to work, but somehow regression there. [1] https://code.launchpad.net/~alextu/+recipe/oem-wifi-qualcomm- ath10k-lp1803647-4.15-dkms-daily To manage notifications about this bug go to: https://bugs.launchpad.net/dkms/+bug/1828948/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1831775] Re: ss seems broken when using multiple filters in the same cmdline
Hello Rafael, or anyone else affected, Accepted iproute2 into disco-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/iproute2/4.18.0-1ubuntu2.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-disco to verification-done-disco. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-disco. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: iproute2 (Ubuntu Disco) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-disco -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to iproute2 in Ubuntu. Matching subscriptions: iproute2 https://bugs.launchpad.net/bugs/1831775 Title: ss seems broken when using multiple filters in the same cmdline Status in iproute2 package in Ubuntu: Fix Released Status in iproute2 source package in Cosmic: Won't Fix Status in iproute2 source package in Disco: Fix Committed Status in iproute2 source package in Eoan: Fix Released Bug description: [Impact] * ss won't be able to run commands with single filters inside parentheses, like: "( sport == :X )", for example. * A workaround is to remove "( )" from single filters, since it looks the issue does not affect 2 filters being put together in the same parentheses, like: " ( X and Y ) and Y " instead of ( X and Y ) and ( Y )". * CTDB is unable to use ss filter to obtain nodes public IP addresses in order to fail over services (LP: #722201). [Test Case] * Having an Ubuntu Cosmic, Disco or Eoan, try to execute the following command: $ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" Independent of the IPs or ports being used. Copying and pasting the command should be enough for you to know if you are affected. Bad Result: ss: bison bellows (while parsing filter): "syntax error!" Sorry. Usage: ss [ OPTIONS ] ss [ OPTIONS ] [ FILTER ] -h, --help this message ... Expected Result: Recv-QSend-Q Local Address:Port Peer Address:Port ... * test case was discovered during CTDB scripts execution [Regression Potential] * biggest risk would be to affect ss interpreter (worst case scenario). * the proposed patch is based in upstream fix and was tested against the same issue reported as the reproducer (above) and some other generic ss commands. * any problem here is unlikely to change iproute2 most important command interpreter, "ip", since the patch is applied against ss code. [Other Info] ORIGINAL DESCRIPTION: Investigating an issue for CTDB (LP: #722201), after suggesting a fix on ss syntax to CTDB upstream project, we discovered that "ss" seems to be broken in Ubuntu since Ubuntu Cosmic: # Debian Sid inaddy@workstation:~$ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" Recv-QSend-Q Local Address:Port Peer Address:Port # Ubuntu Ubuntu 16.04 LTS (Xenial Xerus) (c)inaddy@xenial:~$ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" Recv-Q Send-QLocal Address:Port Peer Address:Port # Ubuntu 18.04 LTS (Bionic Beaver) (c)inaddy@bionic:~$ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" Recv-Q Send-Q Local Address:Port Peer Address:Port # Ubuntu 18.10 (Cosmic Cuttlefish) (c)inaddy@cosmic:~$ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" ss: bison bellows (while parsing filter): "syntax error!" Sorry. Usage: ss [ OPTIONS ] ss [ OPTIONS ] [ FILTER ] -h, --help this message # Ubuntu 19.04 (Disco Dingo) (c)inaddy@disco:~$ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" ss: bison bellows (while parsing fil
[Kernel-packages] [Bug 1836585] [NEW] Xenial kernel 4.4.0-155.182 fails to build perf with libnuma
Public bug reported: [Impact] When libnuma-dev is installed on the build environment, tools/perf tries to build bench/numa.c, but in the current Xenial kernel in -proposed it fails: CC bench/numa.o bench/numa.c: In function 'lfsr_32': bench/numa.c:729:24: error: implicit declaration of function 'BIT' [-Werror=implicit-function-declaration] const uint32_t taps = BIT(1) | BIT(5) | BIT(6) | BIT(31); ^ bench/numa.c:729:2: error: nested extern declaration of 'BIT' [-Werror=nested-externs] const uint32_t taps = BIT(1) | BIT(5) | BIT(6) | BIT(31); ^ [Fix] Commit "UBUNTU: SAUCE: perf/bench: Drop definition of BIT in numa.c", applied for "Xenial update: 4.4.180 upstream stable release (LP: #1830176)" is causing build failures on tools/perf/bench after stable upstream commit "perf tools: No need to include bitops.h in util.h" removed the inclusion of the header file where the BIT() macro is defined. The fix is to revert the SAUCE patch and keep the definition of BIT() in loco in numa.c as done in 4.4 stable upstream. [Test Case] 1. Install libnuma-dev package on the build environment. 2. cd xenial/linux source directory. 3. fakeroot debian/rules clean 4. cd tools/perf 5. make [Regression Potential] Low. The fix is to revert a SAUCE patch that was applied to fix a build failure that has been fixed upstream and it's not needed anymore. ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Xenial) Importance: Undecided Status: In Progress ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Status: New => In Progress ** Changed in: linux (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1836585 Title: Xenial kernel 4.4.0-155.182 fails to build perf with libnuma Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: In Progress Bug description: [Impact] When libnuma-dev is installed on the build environment, tools/perf tries to build bench/numa.c, but in the current Xenial kernel in -proposed it fails: CC bench/numa.o bench/numa.c: In function 'lfsr_32': bench/numa.c:729:24: error: implicit declaration of function 'BIT' [-Werror=implicit-function-declaration] const uint32_t taps = BIT(1) | BIT(5) | BIT(6) | BIT(31); ^ bench/numa.c:729:2: error: nested extern declaration of 'BIT' [-Werror=nested-externs] const uint32_t taps = BIT(1) | BIT(5) | BIT(6) | BIT(31); ^ [Fix] Commit "UBUNTU: SAUCE: perf/bench: Drop definition of BIT in numa.c", applied for "Xenial update: 4.4.180 upstream stable release (LP: #1830176)" is causing build failures on tools/perf/bench after stable upstream commit "perf tools: No need to include bitops.h in util.h" removed the inclusion of the header file where the BIT() macro is defined. The fix is to revert the SAUCE patch and keep the definition of BIT() in loco in numa.c as done in 4.4 stable upstream. [Test Case] 1. Install libnuma-dev package on the build environment. 2. cd xenial/linux source directory. 3. fakeroot debian/rules clean 4. cd tools/perf 5. make [Regression Potential] Low. The fix is to revert a SAUCE patch that was applied to fix a build failure that has been fixed upstream and it's not needed anymore. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836585/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834915] Re: linux-fips: 4.4.0-1014.19 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1834918 phase: Holding before Promote to Proposed phase-changed: Monday, 15. July 2019 11:08 UTC reason: - promote-to-proposed: Ongoing -- builds not complete in ppa main:building,meta:building,signed:building + promote-to-proposed: Ongoing -- builds not complete in ppa meta:building,signed:building variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1834915 Title: linux-fips: 4.4.0-1014.19 -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 prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: Invalid 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: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1834918 phase: Holding before Promote to Proposed phase-changed: Monday, 15. July 2019 11:08 UTC reason: promote-to-proposed: Ongoing -- builds not complete in ppa meta:building,signed:building variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834915/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799791] Re: linux-kvm: please support kexec
** Changed in: linux-kvm (Ubuntu Bionic) Status: In Progress => Fix Committed ** Changed in: linux-kvm (Ubuntu Xenial) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1799791 Title: linux-kvm: please support kexec Status in linux-kvm package in Ubuntu: Fix Released Status in linux-kvm source package in Xenial: Fix Committed Status in linux-kvm source package in Bionic: Fix Committed Status in linux-kvm source package in Cosmic: Fix Released Status in linux-kvm source package in Disco: Fix Released Bug description: linux-kvm doesn't support kexec. Adding support for kexec would enable other interesting uses of linux- kvm, such as for a linuxboot embedded kernel in kvm. Please enable CONFIG_KEXEC=y, CONFIG_KEXEC_FILE=y in linux-kvm. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-kvm/+bug/1799791/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836291] Re: 5.2.0-8-generic regresses KMS edid file support, resulting in no video
Thanks @kaihengfeng! I can't believe I missed that. [headdesk] Indeed I just needed linux-modules-extra installed. That indeed fixes my issue, which was clearly PEBCAK. -- 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/1836291 Title: 5.2.0-8-generic regresses KMS edid file support, resulting in no video Status in linux package in Ubuntu: Invalid Status in linux-meta package in Ubuntu: Invalid Bug description: I have the kernel load an EDID file so that when connecting my amd64 machine to a tv and speaker bar through hdmi I get the full setup information even if the speaker bar and tv might be off. The relevant kernel cmdline is "drm.edid_firmware=HDMI-A-1:edid/edid.bin" In most recent kernel versions this hasn't been a problem. The mainline 5.2.0-rc7 generic kernel at https://kernel.ubuntu.com /~kernel-ppa/mainline/v5.2-rc7/ works properly. The 5.2.0.8.9 kernel in eoan/proposed at https://bugs.launchpad.net/ubuntu/+source/linux-meta/5.2.0.8.9 however does not work, insofar as I get no video output at all after grub loads the kernel. (I would test with the 5.2.0 mainline generic kernel, but the mainline kernel builds are currently broken due to issues with gcc-9.1 flags.) dmesg and Xorg log for boots for both kernels (working and not working) are attached. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.2.0-8-generic (not installed) ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0 Uname: Linux 5.2.0-8-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp ApportVersion: 2.20.11-0ubuntu5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Thu Jul 11 23:43:12 2019 HibernationDevice: RESUME=UUID=102ff483-9121-4be7-af0d-e2599a7c1cf8 InstallationDate: Installed on 2016-08-03 (1073 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: MSI MS-7998 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.2.0-8-generic root=UUID=89506e95-35b5-4f17-8095-aa2aeb09c5c5 ro intel_pstate=skylake_hwp i915.disable_power_well=0 i915.enable_dc=2 i915.enable_fbc=1 i915.enable_guc=3 i915.modeset=1 video=HDMI-A-1:e video=DP-1:d video=HDMI-A-2:d video=HDMI-A-3:d drm.edid_firmware=HDMI-A-1:edid/edid.bin video=efifb:off i915.fastboot=1 video=1920x1080@60 ipti=off spectre_v2=off l1tf=off mds=off nospec_store_bypass_disable no_stf_barrier noibrs noibpb nopti nospectre_v2 nospectre_v1 mpt3sas.msix_disable=1 mpt3sas.logging_level=1 pcie_aspm=off fsck.mode=force fsck.repair=yes cpuidle.governor=teo crashkernel=512M-:192M PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.2.0-8-generic N/A linux-backports-modules-5.2.0-8-generic N/A linux-firmware 1.180 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to eoan on 2018-03-02 (496 days ago) dmi.bios.date: 06/15/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.A0 dmi.board.asset.tag: Default string dmi.board.name: C236A WORKSTATION (MS-7998) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.A0:bd06/15/2018:svnMSI:pnMS-7998:pvr1.0:rvnMSI:rnC236AWORKSTATION(MS-7998):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7998 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836291/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834915] Re: linux-fips: 4.4.0-1014.19 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1834918 phase: Holding before Promote to Proposed phase-changed: Monday, 15. July 2019 11:08 UTC reason: - promote-to-proposed: Ongoing -- builds not complete in ppa meta:building,signed:building + promote-to-proposed: Pending -- builds not complete in ppa meta:queued,signed:queued variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1834915 Title: linux-fips: 4.4.0-1014.19 -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 prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: Invalid 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: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1834918 phase: Holding before Promote to Proposed phase-changed: Monday, 15. July 2019 11:08 UTC reason: promote-to-proposed: Pending -- builds not complete in ppa meta:queued,signed:queued variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834915/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1752002] Comment bridged from LTC Bugzilla
--- Comment From mranw...@us.ibm.com 2019-07-15 09:59 EDT--- I added: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=0c9108b083706330cd5484d121fbb0ad67e8f647 in addition to: https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=next&id=7ccc4fe5ff9e3a134e863beed0dba18a5e511659 It ran a lot longer - hour instead of minutes, but then ended up with this: [18734.191331] perf: interrupt took too long (1054 > 1051), lowering kernel.perf_event_max_sample_rate to 7500 [18736.617855] perf: Dynamic interrupt throttling disabled, can hang your system! [18751.191062] perf: interrupt took too long (2317 > 1333), lowering kernel.perf_event_max_sample_rate to 3250 [18753.006339] perf: interrupt took too long (2218 > 1), lowering kernel.perf_event_max_sample_rate to 3500 [18754.156398] perf: Dynamic interrupt throttling disabled, can hang your system! [18775.067223] perf: interrupt took too long (2227 > 1), lowering kernel.perf_event_max_sample_rate to 3500 [18779.532549] perf: Dynamic interrupt throttling disabled, can hang your system! [18834.315583] perf: Dynamic interrupt throttling disabled, can hang your system! [18851.090933] Watchdog CPU:102 Hard LOCKUP [18851.090936] Modules linked in: kvm_hv kvm vmx_crypto crct10dif_vpmsum ast drm_kms_helper ttm ofpart cmdlinepart drm fb_sys_fops ipmi_powernv at24 syscopyarea ipmi_devintf powernv_flash sysfillrect ipmi_msghandler opal_prd mtd ibmpowernv sysimgblt i2c_algo_bit uio_pdrv_genirq uio sch_fq_codel ip_tables x_tables autofs4 mlx5_core ahci mlxfw crc32c_vpmsum tg3 libahci devlink [18851.090995] CPU: 102 PID: 0 Comm: swapper/102 Tainted: G L 4.15.0-54-generic #58 [18851.090997] NIP: c0100740 LR: c010058c CTR: c00fe770 [18851.091000] REGS: c7ad3d80 TRAP: 0900 Tainted: G L (4.15.0-54-generic) [18851.091001] MSR: 90009033 CR: 28002882 XER: [18851.091014] CFAR: c000deb8 SOFTE: 0 GPR00: c0100584 c00020397b423850 c170b800 c03f80925000 GPR04: 7fff c00020397b4238b0 c000203994486958 c0002039944868b8 GPR08: 0004 0001 GPR12: c0002039944868f8 c7a56200 c00020397b423f90 GPR16: c004ad60 c004ad30 c11d5380 GPR20: 0800 c1742494 0066 0001 GPR24: 0198 8000 0006 GPR28: c18d1808 06004010 c0002039944868a0 [18851.091058] NIP [c0100740] power_pmu_enable+0x4f0/0x600 [18851.091060] LR [c010058c] power_pmu_enable+0x33c/0x600 [18851.091061] Call Trace: [18851.091065] [c00020397b423850] [c0100584] power_pmu_enable+0x334/0x600 (unreliable) [18851.091071] [c00020397b423930] [c02c9dbc] ctx_resched+0xec/0x150 [18851.091075] [c00020397b423970] [c02ca014] __perf_install_in_context+0x1f4/0x280 [18851.091079] [c00020397b4239c0] [c02bf7d0] remote_function+0x40/0x90 [18851.091083] [c00020397b4239f0] [c01db9dc] flush_smp_call_function_queue+0xac/0x1d0 [18851.091087] [c00020397b423a70] [c004bf7c] smp_ipi_demux_relaxed+0x9c/0x110 [18851.091092] [c00020397b423ab0] [c0047948] doorbell_exception+0xa8/0xe0 [18851.091096] [c00020397b423ae0] [c0009ad4] h_doorbell_common+0x114/0x120 [18851.091102] --- interrupt: e81 at replay_interrupt_return+0x0/0x4 LR = arch_local_irq_restore+0x74/0x90 [18851.091106] [c00020397b423dd0] [0040] 0x40 (unreliable) [18851.09] [c00020397b423df0] [c0acea80] cpuidle_enter_state+0xf0/0x450 [18851.091116] [c00020397b423e50] [c017852c] call_cpuidle+0x4c/0x90 [18851.091119] [c00020397b423e70] [c0178940] do_idle+0x2b0/0x330 [18851.091122] [c00020397b423ec0] [c0178bf8] cpu_startup_entry+0x38/0x40 [18851.091125] [c00020397b423ef0] [c004d280] start_secondary+0x4f0/0x510 [18851.091129] [c00020397b423f90] [c000ab6c] start_secondary_prolog+0x10/0x14 [18851.091131] Instruction dump: [18851.091135] 7fa9f000 419d001c 7d29c850 7d244b78 f93801b8 4bfffe44 6000 6000 [18851.091147] 3920 3880 f93801b8 4bfffe2c 4bfffb98 6000 6000 [18854.550395] Watchdog CPU:102 became unstuck [18873.055963] perf: interrupt took too long (329 > 1), lowering kernel.perf_event_max_sample_rate to 48500 [18873.965492] perf: interrupt took too long (420 > 411), lowering kernel.perf_event_max_sample_rate to 38000 [18898.926809] perf: Dynamic interrupt throttling disabled, can hang your system! [18933.376330] perf: interrupt took too long (1534 > 1481), lowering kernel.perf_event_max_sample_rate to 5000 [18942.748893] perf: interrupt took too long (1589 > 1), lowering kernel.perf_event_max_sample_rate to 5000 [18961.230616] perf: interrupt took too long (1190 > 1188), lowering kernel.perf_event_max_s
[Kernel-packages] [Bug 1836291] Re: 5.2.0-8-generic regresses KMS edid file support, resulting in no video
** Changed in: linux (Ubuntu) Status: Incomplete => Invalid ** Changed in: linux-meta (Ubuntu) Status: Incomplete => Invalid -- 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/1836291 Title: 5.2.0-8-generic regresses KMS edid file support, resulting in no video Status in linux package in Ubuntu: Invalid Status in linux-meta package in Ubuntu: Invalid Bug description: I have the kernel load an EDID file so that when connecting my amd64 machine to a tv and speaker bar through hdmi I get the full setup information even if the speaker bar and tv might be off. The relevant kernel cmdline is "drm.edid_firmware=HDMI-A-1:edid/edid.bin" In most recent kernel versions this hasn't been a problem. The mainline 5.2.0-rc7 generic kernel at https://kernel.ubuntu.com /~kernel-ppa/mainline/v5.2-rc7/ works properly. The 5.2.0.8.9 kernel in eoan/proposed at https://bugs.launchpad.net/ubuntu/+source/linux-meta/5.2.0.8.9 however does not work, insofar as I get no video output at all after grub loads the kernel. (I would test with the 5.2.0 mainline generic kernel, but the mainline kernel builds are currently broken due to issues with gcc-9.1 flags.) dmesg and Xorg log for boots for both kernels (working and not working) are attached. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.2.0-8-generic (not installed) ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0 Uname: Linux 5.2.0-8-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp ApportVersion: 2.20.11-0ubuntu5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Thu Jul 11 23:43:12 2019 HibernationDevice: RESUME=UUID=102ff483-9121-4be7-af0d-e2599a7c1cf8 InstallationDate: Installed on 2016-08-03 (1073 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: MSI MS-7998 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.2.0-8-generic root=UUID=89506e95-35b5-4f17-8095-aa2aeb09c5c5 ro intel_pstate=skylake_hwp i915.disable_power_well=0 i915.enable_dc=2 i915.enable_fbc=1 i915.enable_guc=3 i915.modeset=1 video=HDMI-A-1:e video=DP-1:d video=HDMI-A-2:d video=HDMI-A-3:d drm.edid_firmware=HDMI-A-1:edid/edid.bin video=efifb:off i915.fastboot=1 video=1920x1080@60 ipti=off spectre_v2=off l1tf=off mds=off nospec_store_bypass_disable no_stf_barrier noibrs noibpb nopti nospectre_v2 nospectre_v1 mpt3sas.msix_disable=1 mpt3sas.logging_level=1 pcie_aspm=off fsck.mode=force fsck.repair=yes cpuidle.governor=teo crashkernel=512M-:192M PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.2.0-8-generic N/A linux-backports-modules-5.2.0-8-generic N/A linux-firmware 1.180 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to eoan on 2018-03-02 (496 days ago) dmi.bios.date: 06/15/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.A0 dmi.board.asset.tag: Default string dmi.board.name: C236A WORKSTATION (MS-7998) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.A0:bd06/15/2018:svnMSI:pnMS-7998:pvr1.0:rvnMSI:rnC236AWORKSTATION(MS-7998):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7998 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836291/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834915] Re: linux-fips: 4.4.0-1014.19 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1834918 phase: Holding before Promote to Proposed phase-changed: Monday, 15. July 2019 11:08 UTC reason: - promote-to-proposed: Pending -- builds not complete in ppa meta:queued,signed:queued + promote-to-proposed: Ongoing -- builds not complete in ppa meta:building,signed:building variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1834915 Title: linux-fips: 4.4.0-1014.19 -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 prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: Invalid 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: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1834918 phase: Holding before Promote to Proposed phase-changed: Monday, 15. July 2019 11:08 UTC reason: promote-to-proposed: Ongoing -- builds not complete in ppa meta:building,signed:building variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834915/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828166] Re: perf top problem on z with Ubuntu 18.04
Hello IBM, I have built a kernel for tests with the patches mentioned in the previous comment: perf record: Fix s390 missing module symbol and warning for non-root users perf machine: Read also the end of the kernel perf machine: Update kernel map address and re-order properly perf machine: Set main kernel end address properly perf machine: Don't search for active kernel start in __machine__create_kernel_maps perf machine: Generalize machine__set_kernel_mmap() The packages for s390x can be found at: https://people.canonical.com/~ksouza/lp1828166/bionic/ Could you please test the kernel from the link above if it fixes the problem? Thank you. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1828166 Title: perf top problem on z with Ubuntu 18.04 Status in Ubuntu on IBM z Systems: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: Invalid Bug description: SRU Justification: == [Impact] * The perf top tool hangs and shows error messages, like 'Not enough memory for annotating' [Fix] * edeb0c90df3581b821a764052d185df985f8b8dc edeb0c9 "perf tools: Stop fallbacking to kallsyms for vdso symbols lookup" [Test Case] * start a benchmark (mem_alloc, but it doesn't really matter what) * execute perf top in a second terminal * the output of perf top is correct * now stop the benchmark * and perf top shows an error message, like "Not enough memory for annotating '__irf_end' symbol!)" * and perf top can't be exited anymore [Regression Potential] * The regression potential can be considered as low since this happens only while using the perf top tool * and it is known that the commit (above) fixes the problem * and the fix is upstream since 4.19 [Other Info] * current disco and eoan kernels don't show that problem * bisecting result points to above commit * applies cleanly on cosmic, but has a little conflict on bionic (both master-next) _ perf top hangs and shows error messages ---uname output--- Linux weather 4.15.0-46-generic #49-Ubuntu SMP Wed Feb 6 09:32:27 UTC 2019 s390x s390x s390x GNU/Linux ---Steps to Reproduce--- I start a benchmark (mem_alloc, but it really doesn't matter) and then issue perf top in a second terminal, the output from perf top is correct. Now I stop the benchmark: perf top shows a error message (Not enough memory for annotating '__irf_end' symbol!) and I can't quit from perf top anymore Following analyse took place: No problem with current kernel . Bi-Secting of perf tool took place and following commit was found: commit edeb0c90df3581b821a764052d185df985f8b8dc (HEAD, refs/bisect/bad) Author: Arnaldo Carvalho de Melo Date: Tue Oct 16 17:08:29 2018 -0300 perf tools: Stop fallbacking to kallsyms for vdso symbols lookup When you apply this patch the issue is gone, however it is contained in these versions: git tag --contains edeb0c90df3581b821 v4.19 v4.20 The level I was debugging was kernel 4.15 which does not contain this patch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1828166/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836202] Re: bionic/linux-gke-5.0: 5.0.0-1011.11~18.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: In Progress => Fix Committed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1836201 (gke-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834891 phase: Promote to Proposed phase-changed: Monday, 15. July 2019 13:10 UTC reason: - promote-to-proposed: Ongoing -- review in progress + promote-to-proposed: Pending -- packages copied to Proposed signed:retry-needed + promote-to-updates: Pending -- Nvidia objects not found -- current-driver-5.0.0-1011-gke-d1809-0-amd64 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1836202 Title: bionic/linux-gke-5.0: 5.0.0-1011.11~18.04.1 -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 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 verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1836201 (gke-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834891 phase: Promote to Proposed phase-changed: Monday, 15. July 2019 13:10 UTC reason: promote-to-proposed: Pending -- packages copied to Proposed signed:retry-needed promote-to-updates: Pending -- Nvidia objects not found -- current-driver-5.0.0-1011-gke-d1809-0-amd64 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1836202/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834915] Re: linux-fips: 4.4.0-1014.19 -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 will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1834918 - phase: Holding before Promote to Proposed - phase-changed: Monday, 15. July 2019 11:08 UTC + phase: Ready for Promote to Proposed + phase-changed: Monday, 15. July 2019 15:08 UTC reason: - promote-to-proposed: Ongoing -- builds not complete in ppa meta:building,signed:building + promote-to-proposed: Pending -- ready for review variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1834915 Title: linux-fips: 4.4.0-1014.19 -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 prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: New Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: Invalid 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: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1834918 phase: Ready for Promote to Proposed phase-changed: Monday, 15. July 2019 15:08 UTC reason: promote-to-proposed: Pending -- ready for review variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834915/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834944] Re: linux-fips: 4.15.0-1012.13 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1834954 phase: Promote to Proposed phase-changed: Monday, 15. July 2019 12:41 UTC reason: - promote-signing-to-proposed: Pending -- builds not complete in Signing signed:retry-needed - promote-to-proposed: Pending -- packages copied to Signing signed:retry-needed + promote-signing-to-proposed: Ongoing -- builds not complete in Signing signed:building + promote-to-proposed: Pending -- packages copied to Signing signed:building variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1834944 Title: linux-fips: 4.15.0-1012.13 -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 prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: New Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: Invalid 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: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1834954 phase: Promote to Proposed phase-changed: Monday, 15. July 2019 12:41 UTC reason: promote-signing-to-proposed: Ongoing -- builds not complete in Signing signed:building promote-to-proposed: Pending -- packages copied to Signing signed:building variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834944/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834944] Re: linux-fips: 4.15.0-1012.13 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1834954 - phase: Promote to Proposed - phase-changed: Monday, 15. July 2019 12:41 UTC + phase: Holding before Promote to Proposed + phase-changed: Monday, 15. July 2019 15:22 UTC reason: - promote-signing-to-proposed: Ongoing -- builds not complete in Signing signed:building - promote-to-proposed: Pending -- packages copied to Signing signed:building + promote-signing-to-proposed: Holding -- another kernel is currently pending in Proposed variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1834944 Title: linux-fips: 4.15.0-1012.13 -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 prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: New Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid 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: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1834954 phase: Holding before Promote to Proposed phase-changed: Monday, 15. July 2019 15:22 UTC reason: promote-signing-to-proposed: Holding -- another kernel is currently pending in Proposed variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834944/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1787857] Re: USB mouse cursor lags after random time of correct behaviour
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1787857 Title: USB mouse cursor lags after random time of correct behaviour Status in linux package in Ubuntu: Confirmed Status in rtirq package in Ubuntu: Invalid Bug description: I installed Ubuntu Studio 18.04.1 LTS. After the first apt-get update I noticed the following behaviour: after havig logged in, my USB mouse works normally for about ten seconds, then the cursor starts lagging a lot which makes the mouse pretty much unusable. The last dmesg always contain lines these: (more in attached file) [<9e659b0c>] irq_default_primary_handler threaded [] usb_hcd_irq [<9e659b0c>] irq_default_primary_handler threaded [ ] _rtl_pci_interrupt [rtl_pci] Disabling IRQ #18 Out of frustration & curiosity I disabled most autostart apps (Settings > Session ... > Autostart) and re-enabled them after rebooting. Since then I rarely encounter the lagging cursor. If I open Settings > Mouse & Touchpad and toggle any option on/off the cursor starts lagging. How can make the cursor work reliably? Some comment in dmesg mentions "irqpoll" boot option Ubuntu Studio 18.04.1 4.15.0-20-lowlatency #21-Ubuntu SMP PREEMPT To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787857/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1831775] Autopkgtest regression report (iproute2/4.18.0-1ubuntu2.1)
All autopkgtests for the newly accepted iproute2 (4.18.0-1ubuntu2.1) for disco have finished running. There have been regressions in tests triggered by the package. Please visit the sru report page and investigate the failures. https://people.canonical.com/~ubuntu-archive/pending-sru.html#disco -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to iproute2 in Ubuntu. Matching subscriptions: iproute2 https://bugs.launchpad.net/bugs/1831775 Title: ss seems broken when using multiple filters in the same cmdline Status in iproute2 package in Ubuntu: Fix Released Status in iproute2 source package in Cosmic: Won't Fix Status in iproute2 source package in Disco: Fix Committed Status in iproute2 source package in Eoan: Fix Released Bug description: [Impact] * ss won't be able to run commands with single filters inside parentheses, like: "( sport == :X )", for example. * A workaround is to remove "( )" from single filters, since it looks the issue does not affect 2 filters being put together in the same parentheses, like: " ( X and Y ) and Y " instead of ( X and Y ) and ( Y )". * CTDB is unable to use ss filter to obtain nodes public IP addresses in order to fail over services (LP: #722201). [Test Case] * Having an Ubuntu Cosmic, Disco or Eoan, try to execute the following command: $ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" Independent of the IPs or ports being used. Copying and pasting the command should be enough for you to know if you are affected. Bad Result: ss: bison bellows (while parsing filter): "syntax error!" Sorry. Usage: ss [ OPTIONS ] ss [ OPTIONS ] [ FILTER ] -h, --help this message ... Expected Result: Recv-QSend-Q Local Address:Port Peer Address:Port ... * test case was discovered during CTDB scripts execution [Regression Potential] * biggest risk would be to affect ss interpreter (worst case scenario). * the proposed patch is based in upstream fix and was tested against the same issue reported as the reproducer (above) and some other generic ss commands. * any problem here is unlikely to change iproute2 most important command interpreter, "ip", since the patch is applied against ss code. [Other Info] ORIGINAL DESCRIPTION: Investigating an issue for CTDB (LP: #722201), after suggesting a fix on ss syntax to CTDB upstream project, we discovered that "ss" seems to be broken in Ubuntu since Ubuntu Cosmic: # Debian Sid inaddy@workstation:~$ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" Recv-QSend-Q Local Address:Port Peer Address:Port # Ubuntu Ubuntu 16.04 LTS (Xenial Xerus) (c)inaddy@xenial:~$ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" Recv-Q Send-QLocal Address:Port Peer Address:Port # Ubuntu 18.04 LTS (Bionic Beaver) (c)inaddy@bionic:~$ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" Recv-Q Send-Q Local Address:Port Peer Address:Port # Ubuntu 18.10 (Cosmic Cuttlefish) (c)inaddy@cosmic:~$ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" ss: bison bellows (while parsing filter): "syntax error!" Sorry. Usage: ss [ OPTIONS ] ss [ OPTIONS ] [ FILTER ] -h, --help this message # Ubuntu 19.04 (Disco Dingo) (c)inaddy@disco:~$ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" ss: bison bellows (while parsing filter): "syntax error!" Sorry. Usage: ss [ OPTIONS ] ss [ OPTIONS ] [ FILTER ] # Ubuntu 19.10 (Eoan Ermine) (c)inaddy@eoan:~$ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" ss: bison bellows (while parsing filter): "syntax error!" Sorry. Usage: ss [ OPTIONS ] ss [ OPTIONS ] [ FILTER ] I have generated a pkg using upstream iproute2 source code and it does not suffer the issue. I have generated a package using Ubuntu cosmic source package, without debian/patches/*, and verified the issue still persists (not being introduced by any of our packages, and being present if vanilla upstream version used in Cosmic). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1831775/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1787857] Re: USB mouse cursor lags after random time of correct behaviour
Subscribing kernel team. Also, posting the difference between the kernel configurations for reference so that you can see exactly why I believe it's a hardware issue. This issue you're reporting has been reported very few times, which is why I believe there is hardware commonality and might be related to the video driver. For instance, I have issues with stuttering on my AMD video unless I add the following kernel options: radeon.cik_support=0 radeon.si_support=0 amdgpu.dc=1 amdgpu.cik_support=1 amdgpu.si_support=1 amdgpu.dpm=0 amdgpu.gpu_recovery=1 Here's the configuration file differences, which you'll find are VERY minimal: --- /home/erich/Desktop/config-5.0.0-20-generic +++ /home/erich/Desktop/config-5.0.0-20-lowlatency @@ -1,6 +1,6 @@ # # Automatically generated file; DO NOT EDIT. -# Linux/x86 5.0.0-20-generic Kernel Configuration +# Linux/x86 5.0.0-20-lowlatency Kernel Configuration # # @@ -35,7 +35,7 @@ # CONFIG_KERNEL_LZO is not set # CONFIG_KERNEL_LZ4 is not set CONFIG_DEFAULT_HOSTNAME="(none)" -CONFIG_VERSION_SIGNATURE="Ubuntu 5.0.0-20.21-generic 5.0.8" +CONFIG_VERSION_SIGNATURE="Ubuntu 5.0.0-20.21-lowlatency 5.0.8" CONFIG_SWAP=y CONFIG_SYSVIPC=y CONFIG_SYSVIPC_SYSCTL=y @@ -63,7 +63,7 @@ CONFIG_GENERIC_IRQ_MATRIX_ALLOCATOR=y CONFIG_GENERIC_IRQ_RESERVATION_MODE=y CONFIG_IRQ_FORCED_THREADING=y -# CONFIG_IRQ_FORCED_THREADING_DEFAULT is not set +CONFIG_IRQ_FORCED_THREADING_DEFAULT=y CONFIG_SPARSE_IRQ=y # CONFIG_GENERIC_IRQ_DEBUGFS is not set CONFIG_CLOCKSOURCE_WATCHDOG=y @@ -87,8 +87,9 @@ CONFIG_NO_HZ=y CONFIG_HIGH_RES_TIMERS=y # CONFIG_PREEMPT_NONE is not set -CONFIG_PREEMPT_VOLUNTARY=y -# CONFIG_PREEMPT is not set +# CONFIG_PREEMPT_VOLUNTARY is not set +CONFIG_PREEMPT=y +CONFIG_PREEMPT_COUNT=y # # CPU/Task time and stats accounting @@ -109,7 +110,7 @@ # # RCU Subsystem # -CONFIG_TREE_RCU=y +CONFIG_PREEMPT_RCU=y # CONFIG_RCU_EXPERT is not set CONFIG_SRCU=y CONFIG_TREE_SRCU=y @@ -421,10 +422,10 @@ CONFIG_EFI_MIXED=y CONFIG_SECCOMP=y # CONFIG_HZ_100 is not set -CONFIG_HZ_250=y +# CONFIG_HZ_250 is not set # CONFIG_HZ_300 is not set -# CONFIG_HZ_1000 is not set -CONFIG_HZ=250 +CONFIG_HZ_1000=y +CONFIG_HZ=1000 CONFIG_SCHED_HRTICK=y CONFIG_KEXEC=y CONFIG_KEXEC_FILE=y @@ -864,11 +865,7 @@ CONFIG_PREEMPT_NOTIFIERS=y CONFIG_PADATA=y CONFIG_ASN1=y -CONFIG_INLINE_SPIN_UNLOCK_IRQ=y -CONFIG_INLINE_READ_UNLOCK=y -CONFIG_INLINE_READ_UNLOCK_IRQ=y -CONFIG_INLINE_WRITE_UNLOCK=y -CONFIG_INLINE_WRITE_UNLOCK_IRQ=y +CONFIG_UNINLINE_SPIN_UNLOCK=y CONFIG_ARCH_SUPPORTS_ATOMIC_RMW=y CONFIG_MUTEX_SPIN_ON_OWNER=y CONFIG_RWSEM_SPIN_ON_OWNER=y @@ -5160,6 +5157,7 @@ CONFIG_REGULATOR_WM8994=m CONFIG_CEC_CORE=y CONFIG_CEC_NOTIFIER=y +CONFIG_CEC_PIN=y CONFIG_RC_CORE=m CONFIG_RC_MAP=m CONFIG_LIRC=y @@ -5205,6 +5203,7 @@ CONFIG_MEDIA_RADIO_SUPPORT=y CONFIG_MEDIA_SDR_SUPPORT=y CONFIG_MEDIA_CEC_SUPPORT=y +# CONFIG_CEC_PIN_ERROR_INJ is not set CONFIG_MEDIA_CONTROLLER=y # CONFIG_MEDIA_CONTROLLER_DVB is not set # CONFIG_MEDIA_CONTROLLER_REQUEST_API is not set @@ -5498,6 +5497,7 @@ CONFIG_DVB_PLATFORM_DRIVERS=y CONFIG_CEC_PLATFORM_DRIVERS=y CONFIG_VIDEO_CROS_EC_CEC=m +CONFIG_CEC_GPIO=m CONFIG_VIDEO_SECO_CEC=m CONFIG_VIDEO_SECO_RC=y CONFIG_SDR_PLATFORM_DRIVERS=y @@ -9709,6 +9709,7 @@ CONFIG_SCHEDSTATS=y CONFIG_SCHED_STACK_END_CHECK=y # CONFIG_DEBUG_TIMEKEEPING is not set +# CONFIG_DEBUG_PREEMPT is not set # # Lock Debugging (spinlocks, mutexes, etc...) @@ -9753,7 +9754,7 @@ # CONFIG_NETDEV_NOTIFIER_ERROR_INJECT is not set CONFIG_FUNCTION_ERROR_INJECTION=y # CONFIG_FAULT_INJECTION is not set -# CONFIG_LATENCYTOP is not set +CONFIG_LATENCYTOP=y CONFIG_USER_STACKTRACE_SUPPORT=y CONFIG_NOP_TRACER=y CONFIG_HAVE_FUNCTION_TRACER=y @@ -9778,6 +9779,7 @@ CONFIG_FUNCTION_GRAPH_TRACER=y # CONFIG_PREEMPTIRQ_EVENTS is not set # CONFIG_IRQSOFF_TRACER is not set +# CONFIG_PREEMPT_TRACER is not set CONFIG_SCHED_TRACER=y CONFIG_HWLAT_TRACER=y CONFIG_FTRACE_SYSCALLS=y -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1787857 Title: USB mouse cursor lags after random time of correct behaviour Status in linux package in Ubuntu: Confirmed Status in rtirq package in Ubuntu: Invalid Bug description: I installed Ubuntu Studio 18.04.1 LTS. After the first apt-get update I noticed the following behaviour: after havig logged in, my USB mouse works normally for about ten seconds, then the cursor starts lagging a lot which makes the mouse pretty much unusable. The last dmesg always contain lines these: (more in attached file) [<9e659b0c>] irq_default_primary_handler threaded [] usb_hcd_irq [<9e659b0c>] irq_default_primary_handler threaded [ ] _rtl_pci_interrupt [rtl_pci] Disabling IRQ #18 Out of frustration & curiosity I disabled most autostart apps (Settings > Session ... > Autostart) and re-enabl
[Kernel-packages] [Bug 1836614] [NEW] Disco update: 5.0.18 upstream stable release
Public bug reported: 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 following upstream stable patches should be included in the Ubuntu kernel: 5.0.18 upstream stable release from git://git.kernel.org/ ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Disco) Importance: Medium Assignee: Stefan Bader (smb) Status: In Progress ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Disco) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Disco) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Disco) Status: New => In Progress ** Changed in: linux (Ubuntu Disco) Assignee: (unassigned) => Stefan Bader (smb) ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1836614 Title: Disco update: 5.0.18 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Disco: In Progress 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 following upstream stable patches should be included in the Ubuntu kernel: 5.0.18 upstream stable release from git://git.kernel.org/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836614/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836614] Re: Disco update: 5.0.18 upstream stable release
Already applied for bug #1827967: - "ALSA: hda/hdmi - Read the pin sense from register when repolling" - "ALSA: hda/hdmi - Consider eld_valid when reporting jack event" Already applied for bug #1827555: - "ALSA: hda/realtek - Headset fixup for System76 Gazelle (gaze14)" - "ALSA: hda/realtek - Corrected fixup for System76 Gazelle (gaze14)" Already applied for CVE-2019-11833: - "ext4: zero out the unused memory region in the extent tree block" Already applied for bug #1828798: - "ALSA: hda/realtek - Fixup headphone noise via runtime suspend" ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-11833 ** Description changed: + SRU Justification - 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 following upstream + stable patches should be included in the Ubuntu kernel: - 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 following upstream -stable patches should be included in the Ubuntu kernel: + 5.0.18 upstream stable release + from git://git.kernel.org/ -5.0.18 upstream stable release -from git://git.kernel.org/ + The following patches were applied: + * locking/rwsem: Prevent decrement of reader count before increment + * x86/speculation/mds: Revert CPU buffer clear on double fault exit + * x86/speculation/mds: Improve CPU buffer clear documentation + * objtool: Fix function fallthrough detection + * arm64: dts: rockchip: fix IO domain voltage setting of APIO5 on rockpro64 + * arm64: dts: rockchip: Disable DCMDs on RK3399's eMMC controller. + * ARM: dts: qcom: ipq4019: enlarge PCIe BAR range + * ARM: dts: exynos: Fix interrupt for shared EINTs on Exynos5260 + * ARM: dts: exynos: Fix audio (microphone) routing on Odroid XU3 + * mmc: sdhci-of-arasan: Add DTS property to disable DCMDs. + * ARM: exynos: Fix a leaked reference by adding missing of_node_put + * power: supply: axp288_charger: Fix unchecked return value + * power: supply: axp288_fuel_gauge: Add ACEPC T8 and T11 mini PCs to the blacklist + * arm64: mmap: Ensure file offset is treated as unsigned + * arm64: arch_timer: Ensure counter register reads occur with seqlock held + * arm64: compat: Reduce address limit + * arm64: Clear OSDLR_EL1 on CPU boot + * arm64: Save and restore OSDLR_EL1 across suspend/resume + * sched/x86: Save [ER]FLAGS on context switch + * x86/MCE: Add an MCE-record filtering function + * x86/MCE/AMD: Turn off MC4_MISC thresholding on all family 0x15 models + * x86/MCE/AMD: Carve out the MC4_MISC thresholding quirk + * x86/MCE: Group AMD function prototypes in + * x86/MCE/AMD: Don't report L1 BTB MCA errors on some family 17h models + * crypto: crypto4xx - fix ctr-aes missing output IV + * crypto: crypto4xx - fix cfb and ofb "overran dst buffer" issues + * crypto: salsa20 - don't access already-freed walk.iv + * crypto: lrw - don't access already-freed walk.iv + * crypto: chacha-generic - fix use as arm64 no-NEON fallback + * crypto: chacha20poly1305 - set cra_name correctly + * crypto: ccp - Do not free psp_master when PLATFORM_INIT fails + * crypto: vmx - fix copy-paste error in CTR mode + * crypto: skcipher - don't WARN on unprocessed data after slow walk step + * crypto: crct10dif-generic - fix use via crypto_shash_digest() + * crypto: x86/crct10dif-pcl - fix use via crypto_shash_digest() + * crypto: arm64/gcm-aes-ce - fix no-NEON fallback code + * crypto: gcm - fix incompatibility between "gcm" and "gcm_base" + * crypto: rockchip - update IV buffer to contain the next IV + * crypto: caam/qi2 - fix zero-length buffer DMA mapping + * crypto: caam/qi2 - fix DMA mapping of stack memory + * crypto: caam/qi2 - generate hash keys in-place + * crypto: arm/aes-neonbs - don't access already-freed walk.iv + * crypto: arm64/aes-neonbs - don't access already-freed walk.iv + * mmc: tegra: fix ddr signaling for non-ddr modes + * mmc: core: Fix tag set memory leak + * mmc: sdhci-pci: Fix BYT OCP setting + * ALSA: line6: toneport: Fix broken usage of timer for delayed execution + * ALSA: usb-audio: Fix a memory leak bug + * ALSA: hda/realtek - EAPD turn on later + * ASoC: max98090: Fix restore of DAPM Muxes + * ASoC: RT5677-SPI: Disable 16Bit SPI Transfers + * ASoC: fsl_esai: Fix missing break in switch statement + * ASoC: codec: hdac_hdmi add device_link to card device + * bpf, arm64: remove prefetch insn in xadd mapping + * crypto: ccree - remo
[Kernel-packages] [Bug 1767992] Re: Linux md raid-10 freezes during resync
Kernel from https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1767992/comments/8 solved my issues. For reproduce on 4.15.0-50-generic Make new raid-10, add some io fio/dd, unpack anaconda archives(lol), after minute or two deadlocked [Mon Jul 15 19:31:11 2019] Workqueue: md md_submit_flush_data [Mon Jul 15 19:31:11 2019] Call Trace: [Mon Jul 15 19:31:11 2019] __schedule+0x291/0x8a0 [Mon Jul 15 19:31:11 2019] ? __switch_to_asm+0x34/0x70 [Mon Jul 15 19:31:11 2019] ? __switch_to_asm+0x40/0x70 [Mon Jul 15 19:31:11 2019] schedule+0x2c/0x80 [Mon Jul 15 19:31:11 2019] wait_barrier+0x146/0x1a0 [raid10] [Mon Jul 15 19:31:11 2019] ? wait_woken+0x80/0x80 [Mon Jul 15 19:31:11 2019] raid10_write_request+0x77/0x950 [raid10] [Mon Jul 15 19:31:11 2019] ? r10bio_pool_alloc+0x24/0x30 [raid10] [Mon Jul 15 19:31:11 2019] ? mempool_alloc+0x71/0x190 [Mon Jul 15 19:31:11 2019] ? md_write_start+0xf4/0x210 [Mon Jul 15 19:31:11 2019] ? default_wake_function+0x12/0x20 [Mon Jul 15 19:31:11 2019] ? autoremove_wake_function+0x12/0x40 [Mon Jul 15 19:31:11 2019] raid10_make_request+0xcc/0x140 [raid10] [Mon Jul 15 19:31:11 2019] md_handle_request+0x126/0x1a0 [Mon Jul 15 19:31:11 2019] md_submit_flush_data+0x54/0x70 [Mon Jul 15 19:31:11 2019] process_one_work+0x1de/0x410 [Mon Jul 15 19:31:11 2019] worker_thread+0x32/0x410 [Mon Jul 15 19:31:11 2019] kthread+0x121/0x140 [Mon Jul 15 19:31:11 2019] ? process_one_work+0x410/0x410 [Mon Jul 15 19:31:11 2019] ? kthread_create_worker_on_cpu+0x70/0x70 [Mon Jul 15 19:31:11 2019] ret_from_fork+0x35/0x40 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1767992 Title: Linux md raid-10 freezes during resync Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: In Progress Bug description: I'm trying to setup a few nodes with software raid-10. When array is created and resync is running i'm trying to install a few packages and frequently system stops responding, resync process stops, and I'm getting following errors in the kernel log. This looks like a deadlock for me. I had this problem in both 18.04 and 16.04. Reboot is the only way to fix the node. [ 2659.317256] INFO: task kworker/u24:13:343 blocked for more than 120 seconds. [ 2659.317313] Not tainted 4.15.0-20-generic #21-Ubuntu [ 2659.317350] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 2659.317401] kworker/u24:13 D0 343 2 0x8000 [ 2659.317414] Workqueue: writeback wb_workfn (flush-9:1) [ 2659.317417] Call Trace: [ 2659.317430] __schedule+0x297/0x8b0 [ 2659.317435] schedule+0x2c/0x80 [ 2659.317443] wait_barrier+0x146/0x1a0 [raid10] [ 2659.317449] ? wait_woken+0x80/0x80 [ 2659.317454] raid10_write_request+0x77/0x950 [raid10] [ 2659.317459] ? r10bio_pool_alloc+0x24/0x30 [raid10] [ 2659.317465] ? mempool_alloc+0x71/0x190 [ 2659.317469] ? ___slab_alloc+0x20a/0x4b0 [ 2659.317475] ? md_write_start+0xc8/0x200 [ 2659.317480] ? mempool_alloc_slab+0x15/0x20 [ 2659.317484] raid10_make_request+0xcc/0x140 [raid10] [ 2659.317489] md_handle_request+0x126/0x1a0 [ 2659.317494] md_make_request+0x6b/0x150 [ 2659.317501] generic_make_request+0x124/0x300 [ 2659.317506] submit_bio+0x73/0x150 [ 2659.317510] ? submit_bio+0x73/0x150 [ 2659.317579] xfs_submit_ioend+0x87/0x1c0 [xfs] [ 2659.317626] xfs_do_writepage+0x377/0x6a0 [xfs] [ 2659.317632] write_cache_pages+0x20c/0x4e0 [ 2659.317674] ? xfs_vm_writepages+0xf0/0xf0 [xfs] [ 2659.317682] ? intel_pstate_update_pstate+0x40/0x40 [ 2659.317687] ? update_load_avg+0x5c5/0x6e0 [ 2659.317727] xfs_vm_writepages+0xbe/0xf0 [xfs] [ 2659.317732] do_writepages+0x4b/0xe0 [ 2659.317738] ? check_preempt_curr+0x83/0x90 [ 2659.317742] ? ttwu_do_wakeup+0x1e/0x150 [ 2659.317746] __writeback_single_inode+0x45/0x340 [ 2659.317749] ? __writeback_single_inode+0x45/0x340 [ 2659.317752] writeback_sb_inodes+0x1e1/0x510 [ 2659.317756] __writeback_inodes_wb+0x67/0xb0 [ 2659.317759] wb_writeback+0x271/0x300 [ 2659.317764] wb_workfn+0x180/0x410 [ 2659.317766] ? wb_workfn+0x180/0x410 [ 2659.317773] process_one_work+0x1de/0x410 [ 2659.317776] worker_thread+0x32/0x410 [ 2659.317781] kthread+0x121/0x140 [ 2659.317784] ? process_one_work+0x410/0x410 [ 2659.317788] ? kthread_create_worker_on_cpu+0x70/0x70 [ 2659.317793] ? do_syscall_64+0x73/0x130 [ 2659.317797] ? SyS_exit_group+0x14/0x20 [ 2659.317801] ret_from_fork+0x35/0x40 [ 2659.317806] INFO: task md1_resync:429 blocked for more than 120 seconds. [ 2659.317853] Not tainted 4.15.0-20-generic #21-Ubuntu [ 2659.317889] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 2659.317940] md1_resync D0 429 2 0x8000 [ 2659.317943] Call Trace: [ 2659.317949] __schedule+0x297
[Kernel-packages] [Bug 1836153] Re: [18.04 FEAT] zKVM: Add hardware CPU Model - kernel part
** Description changed: + SRU Justification: + == + + [Impact] + + * New hardware is not supported by qemu and won't run run, due to + missing hardware CPU model + + [Fix] + + * 11ba5961a2156a4f210627ed8421387e2531b100 11ba596 "KVM: s390: add debug + logging for cpu model subfunctions" + + * 346fa2f891c71a9b98014f8f62c15f4c7dd95ec1 346fa2f "KVM: s390: implement + subfunction processor calls" + + * 7832e91cd33f21f3cf82b003478c292915a1ec14 7832e91 "KVM: s390: add + vector enhancements facility 2 to cpumodel" + + * d5cb6ab1e3d4d7e0648a167f6290e89f6e86964e d5cb6ab "KVM: s390: add + vector BCD enhancements facility to cpumodel" + + * 13209ad0395c4de7fa48108b1dac72e341d5c089 13209ad "KVM: s390: add MSA9 + to cpumodel" + + * d668139718a9e2260702777bd8d86d71c30b6539 d668139 "KVM: s390: provide + query function for instructions returning 32 byte" + + * 173aec2d5a9fa5f40e462661a8283fcafe04764f 173aec2 "KVM: s390: add + enhanced sort facilty to cpu model" + + * 4f45b90e1c03466202fca7f62eaf32243f220830 4f45b90 "KVM: s390: add + deflate conversion facilty to cpu model" + + * 8ec2fa52eac53bff7ef1cedbc4ad8af650ec937c 8ec2fa5 "KVM: s390: enable + MSA9 keywrapping functions depending on cpu model" + + [Test Case] + + * need to be tested by IBM on pre-rel. hardware or simulator + + [Regression Potential] + + * The regression potential can be considered as low since these changes + are limited to arch/s390 + + * changes are in support for new and upcoming hardware and shouldn't + affect existing s390x systems + + [Other Info] + + * the first 2 commits are the key ones, the other 7 are needed to make + them applly cleanly + + * these patches are already all included in upstream kernel 5.2, hence + they are in eoan's kernel 5.2 + + * qemu package SRU in LP 1836154 complements this SRU - for testing both + need to be in place + + * I could apply the commit IDs cleanly with 'cherry-picks --strategy=recursive -X theirs' and checked that no patches on top were pulled in + _ + Feature request to be applied to Ubuntu 18.04 - kernel. - The git commit information is already provided within + The git commit information is already provided within https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1830239 Once this feature is accepted all information for integration will be provided by IBM kernel 5.2 down to 4.15. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1836153 Title: [18.04 FEAT] zKVM: Add hardware CPU Model - kernel part Status in Ubuntu on IBM z Systems: Triaged Status in linux package in Ubuntu: New Bug description: SRU Justification: == [Impact] * New hardware is not supported by qemu and won't run run, due to missing hardware CPU model [Fix] * 11ba5961a2156a4f210627ed8421387e2531b100 11ba596 "KVM: s390: add debug logging for cpu model subfunctions" * 346fa2f891c71a9b98014f8f62c15f4c7dd95ec1 346fa2f "KVM: s390: implement subfunction processor calls" * 7832e91cd33f21f3cf82b003478c292915a1ec14 7832e91 "KVM: s390: add vector enhancements facility 2 to cpumodel" * d5cb6ab1e3d4d7e0648a167f6290e89f6e86964e d5cb6ab "KVM: s390: add vector BCD enhancements facility to cpumodel" * 13209ad0395c4de7fa48108b1dac72e341d5c089 13209ad "KVM: s390: add MSA9 to cpumodel" * d668139718a9e2260702777bd8d86d71c30b6539 d668139 "KVM: s390: provide query function for instructions returning 32 byte" * 173aec2d5a9fa5f40e462661a8283fcafe04764f 173aec2 "KVM: s390: add enhanced sort facilty to cpu model" * 4f45b90e1c03466202fca7f62eaf32243f220830 4f45b90 "KVM: s390: add deflate conversion facilty to cpu model" * 8ec2fa52eac53bff7ef1cedbc4ad8af650ec937c 8ec2fa5 "KVM: s390: enable MSA9 keywrapping functions depending on cpu model" [Test Case] * need to be tested by IBM on pre-rel. hardware or simulator [Regression Potential] * The regression potential can be considered as low since these changes are limited to arch/s390 * changes are in support for new and upcoming hardware and shouldn't affect existing s390x systems [Other Info] * the first 2 commits are the key ones, the other 7 are needed to make them applly cleanly * these patches are already all included in upstream kernel 5.2, hence they are in eoan's kernel 5.2 * qemu package SRU in LP 1836154 complements this SRU - for testing both need to be in place * I could apply the commit IDs cleanly with 'cherry-picks --strategy=recursive -X theirs' and checked that no patches on top were pulled in _ Feature request to be applied to Ubuntu 18.04 - kernel. The git commit information is already provided within https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1830239 Once this feature is accepted all information for integration will be provided by IBM ke
[Kernel-packages] [Bug 1836622] [NEW] Eoan update: v5.2.1 upstream stable release
Public bug reported: 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 following upstream stable patches should be included in the Ubuntu kernel: v5.2.1 upstream stable release from git://git.kernel.org/ ** Affects: linux (Ubuntu) Importance: Medium Assignee: Seth Forshee (sforshee) Status: In Progress ** Affects: linux (Ubuntu Eoan) Importance: Medium Assignee: Seth Forshee (sforshee) Status: In Progress ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Eoan) Importance: Undecided Status: Confirmed ** Changed in: linux (Ubuntu Eoan) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Eoan) Status: Confirmed => In Progress ** Changed in: linux (Ubuntu Eoan) Assignee: (unassigned) => Seth Forshee (sforshee) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1836622 Title: Eoan update: v5.2.1 upstream stable release Status in linux package in Ubuntu: In Progress Status in linux source package in Eoan: In Progress 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 following upstream stable patches should be included in the Ubuntu kernel: v5.2.1 upstream stable release from git://git.kernel.org/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836622/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836622] Re: Eoan update: v5.2.1 upstream stable release
** Changed in: linux (Ubuntu Eoan) 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/1836622 Title: Eoan update: v5.2.1 upstream stable release Status in linux package in Ubuntu: Fix Committed Status in linux source package in Eoan: 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 following upstream stable patches should be included in the Ubuntu kernel: v5.2.1 upstream stable release from git://git.kernel.org/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836622/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835891] Re: [wishlist] CONFIG_XFRM_MIGRATE=y
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1835891 Title: [wishlist] CONFIG_XFRM_MIGRATE=y Status in libreswan package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: This is a new feature request, Ubuntu linux, kernel, package. Description: Ubuntu 18.04.1 LTS Release: 18.04 Ubuntu 4.15.0-36.39-generic 4.15.18 I am adding version information from bionic, it would be nice to be fixed in the next possible version. Please enable CONFIG_XFRM_MIGRATE=y in kernel config to supoort IKE (IPsec mobike). Libreswan use this kernel feature to support MOBIKE RFC 4555. conn iphone-psk mobike=yes Error meesage: ipsec auto --add iphone-psk 036 MOBIKE kernel support missing for netkey interface: CONFIG_XFRM_MIGRATE && CONFIG_NET_KEY_MIGRATE FYI: CONFIG_XFRM_MIGRATE=y in Debian Buster and RHEL, Fedora. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreswan/+bug/1835891/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836211] Re: bcmwl fails to install with recent Eoan (Bad return status for module build on kernel: 5.0.0-20-generic)
I am facing this same issue. Wifi not found and the driver wont compile. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1836211 Title: bcmwl fails to install with recent Eoan (Bad return status for module build on kernel: 5.0.0-20-generic) Status in bcmwl package in Ubuntu: New Bug description: With recent Eoan builds, bcmwl fails to install completely, . It had worked when I installed Eoan a couple weeks ago, but not when I first tried to clean install on 9 July until today. (I've unfortunately erased the old, working installation so I don't have more details.) $ sudo apt install bcmwl-kernel-source Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: dkms Suggested packages: menu The following NEW packages will be installed: bcmwl-kernel-source dkms 0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded. Need to get 1,610 kB of archives. After this operation, 8,359 kB of additional disk space will be used. Do you want to continue? [Y/n] Get:1 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 dkms all 2.7.1-1ubuntu1 [66.5 kB] Get:2 http://us.archive.ubuntu.com/ubuntu eoan/restricted amd64 bcmwl-kernel-source amd64 6.30.223.271+bdcom-0ubuntu5 [1,544 kB] Fetched 1,610 kB in 0s (4,097 kB/s) Selecting previously unselected package dkms. (Reading database ... 122315 files and directories currently installed.) Preparing to unpack .../dkms_2.7.1-1ubuntu1_all.deb ... Unpacking dkms (2.7.1-1ubuntu1) ... Selecting previously unselected package bcmwl-kernel-source. Preparing to unpack .../bcmwl-kernel-source_6.30.223.271+bdcom-0ubuntu5_amd64.deb ... Unpacking bcmwl-kernel-source (6.30.223.271+bdcom-0ubuntu5) ... Setting up dkms (2.7.1-1ubuntu1) ... Setting up bcmwl-kernel-source (6.30.223.271+bdcom-0ubuntu5) ... Loading new bcmwl-6.30.223.271+bdcom DKMS files... Building for 5.0.0-20-generic Building for architecture x86_64 Building initial module for 5.0.0-20-generic Error! Bad return status for module build on kernel: 5.0.0-20-generic (x86_64) Consult /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/make.log for more information. dpkg: error processing package bcmwl-kernel-source (--configure): installed bcmwl-kernel-source package post-installation script subprocess returned error exit status 10 Processing triggers for man-db (2.8.5-2) ... Errors were encountered while processing: bcmwl-kernel-source E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.11-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Jul 11 09:02:53 2019 InstallationDate: Installed on 2019-07-11 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190711) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: bcmwl UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1836211/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836630] [NEW] System76 Oryx Pro (oryp5) with 5.0.0-21: Fail to resume from suspend
Public bug reported: After upgrading the Ubuntu kernel to version 5.0.0-21, the System76 Oryx Pro (oryp5) fails to resume from suspend when using discrete NVIDIA graphics The issue can be created on this hardware by following these steps: - Install Ubuntu 18.04.2 - Add the proposed updates: https://wiki.ubuntu.com/Testing/EnableProposed - Upgrade: sudo apt-get updatesudo apt-get dist-upgrade - Install 5.0 HWE kernel: sudo apt-get install linux-generic-hwe-18.04-edge - Install NVIDIA driver: sudo apt-get install nvidia-driver-430 - Reboot: sudo reboot - Attempt suspend/resume cycle This occurred after upgrading the kernel from version 5.0.0-20. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1836630 Title: System76 Oryx Pro (oryp5) with 5.0.0-21: Fail to resume from suspend Status in linux package in Ubuntu: New Bug description: After upgrading the Ubuntu kernel to version 5.0.0-21, the System76 Oryx Pro (oryp5) fails to resume from suspend when using discrete NVIDIA graphics The issue can be created on this hardware by following these steps: - Install Ubuntu 18.04.2 - Add the proposed updates: https://wiki.ubuntu.com/Testing/EnableProposed - Upgrade: sudo apt-get updatesudo apt-get dist-upgrade - Install 5.0 HWE kernel: sudo apt-get install linux-generic-hwe-18.04-edge - Install NVIDIA driver: sudo apt-get install nvidia-driver-430 - Reboot: sudo reboot - Attempt suspend/resume cycle This occurred after upgrading the kernel from version 5.0.0-20. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836630/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836630] 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 1836630 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/1836630 Title: System76 Oryx Pro (oryp5) with 5.0.0-21: Fail to resume from suspend Status in linux package in Ubuntu: Incomplete Bug description: After upgrading the Ubuntu kernel to version 5.0.0-21, the System76 Oryx Pro (oryp5) fails to resume from suspend when using discrete NVIDIA graphics The issue can be created on this hardware by following these steps: - Install Ubuntu 18.04.2 - Add the proposed updates: https://wiki.ubuntu.com/Testing/EnableProposed - Upgrade: sudo apt-get updatesudo apt-get dist-upgrade - Install 5.0 HWE kernel: sudo apt-get install linux-generic-hwe-18.04-edge - Install NVIDIA driver: sudo apt-get install nvidia-driver-430 - Reboot: sudo reboot - Attempt suspend/resume cycle This occurred after upgrading the kernel from version 5.0.0-20. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836630/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836635] [NEW] Bionic: support for Solarflare X2542 network adapter (sfc driver)
Public bug reported: [Impact] * Support for Solarflare X2542 network adapter (Medford2 / SFC9250) in the sfc driver. * This network adapter is present on recent hardware, at least HP 2019 and Dell PowerEdge R740xd systems. * On recent-hardware deployments that would rather use the Bionic LTS / GA supported kernel and cannot move to HWE kernels this adapter is non functional at all. [Test Case] * The X2542 adapter has been exercised with iperf3 and nc across 2 hosts on 25G link speed w/ MTUs 1400/1500/9000 on both directions, for 1 week. Its performance is on par with the Cosmic 4.18 kernel (which contains all these patches) and the out-of-tree driver from the vendor. * The 7000 series adapter (for regression testing an old model, supported previously) has been exercised with iperf and netperf (TCP_STREAM, UDP_STREAM, TCP_RR, UDP_RR, and TCP_CRR) in one host (client/server in different adapter ports isolated with network namespaces, so traffic goes through the network switch), on 10G link speed on MTUs 1500/9000, for 1 weekend. No regressions observed between the original and test kernels. [Regression Potential] * The patchset touches a lot of the sfc driver, so the potential for regression definitely exists. It has been tested on other adapter which uses the old code, and no regressions were found. ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Bionic) Importance: Undecided Assignee: Mauricio Faria de Oliveira (mfo) Status: In Progress ** Affects: linux (Ubuntu Cosmic) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Disco) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Eoan) Importance: Undecided Status: Invalid ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Eoan) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Disco) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Mauricio Faria de Oliveira (mfo) ** Changed in: linux (Ubuntu Cosmic) Status: New => Invalid ** Changed in: linux (Ubuntu Disco) Status: New => Invalid ** Changed in: linux (Ubuntu Eoan) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1836635 Title: Bionic: support for Solarflare X2542 network adapter (sfc driver) Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: Invalid Status in linux source package in Disco: Invalid Status in linux source package in Eoan: Invalid Bug description: [Impact] * Support for Solarflare X2542 network adapter (Medford2 / SFC9250) in the sfc driver. * This network adapter is present on recent hardware, at least HP 2019 and Dell PowerEdge R740xd systems. * On recent-hardware deployments that would rather use the Bionic LTS / GA supported kernel and cannot move to HWE kernels this adapter is non functional at all. [Test Case] * The X2542 adapter has been exercised with iperf3 and nc across 2 hosts on 25G link speed w/ MTUs 1400/1500/9000 on both directions, for 1 week. Its performance is on par with the Cosmic 4.18 kernel (which contains all these patches) and the out-of-tree driver from the vendor. * The 7000 series adapter (for regression testing an old model, supported previously) has been exercised with iperf and netperf (TCP_STREAM, UDP_STREAM, TCP_RR, UDP_RR, and TCP_CRR) in one host (client/server in different adapter ports isolated with network namespaces, so traffic goes through the network switch), on 10G link speed on MTUs 1500/9000, for 1 weekend. No regressions observed between the original and test kernels. [Regression Potential] * The patchset touches a lot of the sfc driver, so the potential for regression definitely exists. It has been tested on other adapter which uses the old code, and no regressions were found. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836635/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836630] Re: System76 Oryx Pro (oryp5) with 5.0.0-21: Fail to resume from suspend
apport information ** Also affects: linux-hwe-edge (Ubuntu) Importance: Undecided Status: New ** Tags added: apport-collected bionic ** Description changed: After upgrading the Ubuntu kernel to version 5.0.0-21, the System76 Oryx Pro (oryp5) fails to resume from suspend when using discrete NVIDIA graphics The issue can be created on this hardware by following these steps: - Install Ubuntu 18.04.2 - Add the proposed updates: https://wiki.ubuntu.com/Testing/EnableProposed - Upgrade: sudo apt-get updatesudo apt-get dist-upgrade - Install 5.0 HWE kernel: sudo apt-get install linux-generic-hwe-18.04-edge - Install NVIDIA driver: sudo apt-get install nvidia-driver-430 - Reboot: sudo reboot - Attempt suspend/resume cycle This occurred after upgrading the kernel from version 5.0.0-20. + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.7 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC1: system76 1721 F pulseaudio + /dev/snd/controlC0: system76 1721 F pulseaudio + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 18.04 + MachineType: System76 Oryx Pro + NonfreeKernelModules: nvidia_modeset nvidia + Package: linux-hwe-edge + ProcFB: 0 inteldrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-21-generic root=UUID=10b5d457-8884-4b50-bd82-9b38e7f36564 ro + ProcVersionSignature: Ubuntu 5.0.0-21.22~18.04.1-generic 5.0.15 + RelatedPackageVersions: + linux-restricted-modules-5.0.0-21-generic N/A + linux-backports-modules-5.0.0-21-generic N/A + linux-firmware1.173.9 + Tags: bionic + Uname: Linux 5.0.0-21-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm sudo + _MarkForUpload: True + dmi.bios.date: 05/07/2019 + dmi.bios.vendor: INSYDE Corp. + dmi.bios.version: 1.07.08 + dmi.board.asset.tag: Tag 12345 + dmi.board.name: Oryx Pro + dmi.board.vendor: System76 + dmi.board.version: oryp5 + dmi.chassis.asset.tag: No Asset Tag + dmi.chassis.type: 10 + dmi.chassis.vendor: System76 + dmi.chassis.version: oryp5 + dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.08:bd05/07/2019:svnSystem76:pnOryxPro:pvroryp5:rvnSystem76:rnOryxPro:rvroryp5:cvnSystem76:ct10:cvroryp5: + dmi.product.family: Not Applicable + dmi.product.name: Oryx Pro + dmi.product.sku: Not Applicable + dmi.product.version: oryp5 + dmi.sys.vendor: System76 ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1836630/+attachment/5277198/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1836630 Title: System76 Oryx Pro (oryp5) with 5.0.0-21: Fail to resume from suspend Status in linux package in Ubuntu: Confirmed Status in linux-hwe-edge package in Ubuntu: Confirmed Bug description: After upgrading the Ubuntu kernel to version 5.0.0-21, the System76 Oryx Pro (oryp5) fails to resume from suspend when using discrete NVIDIA graphics The issue can be created on this hardware by following these steps: - Install Ubuntu 18.04.2 - Add the proposed updates: https://wiki.ubuntu.com/Testing/EnableProposed - Upgrade: sudo apt-get updatesudo apt-get dist-upgrade - Install 5.0 HWE kernel: sudo apt-get install linux-generic-hwe-18.04-edge - Install NVIDIA driver: sudo apt-get install nvidia-driver-430 - Reboot: sudo reboot - Attempt suspend/resume cycle This occurred after upgrading the kernel from version 5.0.0-20. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: system76 1721 F pulseaudio /dev/snd/controlC0: system76 1721 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 MachineType: System76 Oryx Pro NonfreeKernelModules: nvidia_modeset nvidia Package: linux-hwe-edge ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-21-generic root=UUID=10b5d457-8884-4b50-bd82-9b38e7f36564 ro ProcVersionSignature: Ubuntu 5.0.0-21.22~18.04.1-generic 5.0.15 RelatedPackageVersions: linux-restricted-modules-5.0.0-21-generic N/A linux-backports-modules-5.0.0-21-generic N/A linux-firmware1.173.9 Tags: bionic Uname: Linux 5.0.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm sudo _MarkForUpload: True dmi.bios.date: 05/07/2019 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.08 dmi.board.asset.tag: Tag 12345 dmi.board.name: Oryx Pro dmi.board.vendor: System76 dmi.board.version: oryp5 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: System76 dmi.chassis.version: oryp5 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.08:bd05/07/2019:svnSystem76:pnOryxPro:pvroryp5:rvnSystem76:rnOry
[Kernel-packages] [Bug 1836630] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1836630/+attachment/5277205/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1836630 Title: System76 Oryx Pro (oryp5) with 5.0.0-21: Fail to resume from suspend Status in linux package in Ubuntu: Confirmed Status in linux-hwe-edge package in Ubuntu: Confirmed Bug description: After upgrading the Ubuntu kernel to version 5.0.0-21, the System76 Oryx Pro (oryp5) fails to resume from suspend when using discrete NVIDIA graphics The issue can be created on this hardware by following these steps: - Install Ubuntu 18.04.2 - Add the proposed updates: https://wiki.ubuntu.com/Testing/EnableProposed - Upgrade: sudo apt-get updatesudo apt-get dist-upgrade - Install 5.0 HWE kernel: sudo apt-get install linux-generic-hwe-18.04-edge - Install NVIDIA driver: sudo apt-get install nvidia-driver-430 - Reboot: sudo reboot - Attempt suspend/resume cycle This occurred after upgrading the kernel from version 5.0.0-20. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: system76 1721 F pulseaudio /dev/snd/controlC0: system76 1721 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 MachineType: System76 Oryx Pro NonfreeKernelModules: nvidia_modeset nvidia Package: linux-hwe-edge ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-21-generic root=UUID=10b5d457-8884-4b50-bd82-9b38e7f36564 ro ProcVersionSignature: Ubuntu 5.0.0-21.22~18.04.1-generic 5.0.15 RelatedPackageVersions: linux-restricted-modules-5.0.0-21-generic N/A linux-backports-modules-5.0.0-21-generic N/A linux-firmware1.173.9 Tags: bionic Uname: Linux 5.0.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm sudo _MarkForUpload: True dmi.bios.date: 05/07/2019 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.08 dmi.board.asset.tag: Tag 12345 dmi.board.name: Oryx Pro dmi.board.vendor: System76 dmi.board.version: oryp5 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: System76 dmi.chassis.version: oryp5 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.08:bd05/07/2019:svnSystem76:pnOryxPro:pvroryp5:rvnSystem76:rnOryxPro:rvroryp5:cvnSystem76:ct10:cvroryp5: dmi.product.family: Not Applicable dmi.product.name: Oryx Pro dmi.product.sku: Not Applicable dmi.product.version: oryp5 dmi.sys.vendor: System76 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836630/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836630] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1836630/+attachment/5277203/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1836630 Title: System76 Oryx Pro (oryp5) with 5.0.0-21: Fail to resume from suspend Status in linux package in Ubuntu: Confirmed Status in linux-hwe-edge package in Ubuntu: Confirmed Bug description: After upgrading the Ubuntu kernel to version 5.0.0-21, the System76 Oryx Pro (oryp5) fails to resume from suspend when using discrete NVIDIA graphics The issue can be created on this hardware by following these steps: - Install Ubuntu 18.04.2 - Add the proposed updates: https://wiki.ubuntu.com/Testing/EnableProposed - Upgrade: sudo apt-get updatesudo apt-get dist-upgrade - Install 5.0 HWE kernel: sudo apt-get install linux-generic-hwe-18.04-edge - Install NVIDIA driver: sudo apt-get install nvidia-driver-430 - Reboot: sudo reboot - Attempt suspend/resume cycle This occurred after upgrading the kernel from version 5.0.0-20. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: system76 1721 F pulseaudio /dev/snd/controlC0: system76 1721 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 MachineType: System76 Oryx Pro NonfreeKernelModules: nvidia_modeset nvidia Package: linux-hwe-edge ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-21-generic root=UUID=10b5d457-8884-4b50-bd82-9b38e7f36564 ro ProcVersionSignature: Ubuntu 5.0.0-21.22~18.04.1-generic 5.0.15 RelatedPackageVersions: linux-restricted-modules-5.0.0-21-generic N/A linux-backports-modules-5.0.0-21-generic N/A linux-firmware1.173.9 Tags: bionic Uname: Linux 5.0.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm sudo _MarkForUpload: True dmi.bios.date: 05/07/2019 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.08 dmi.board.asset.tag: Tag 12345 dmi.board.name: Oryx Pro dmi.board.vendor: System76 dmi.board.version: oryp5 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: System76 dmi.chassis.version: oryp5 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.08:bd05/07/2019:svnSystem76:pnOryxPro:pvroryp5:rvnSystem76:rnOryxPro:rvroryp5:cvnSystem76:ct10:cvroryp5: dmi.product.family: Not Applicable dmi.product.name: Oryx Pro dmi.product.sku: Not Applicable dmi.product.version: oryp5 dmi.sys.vendor: System76 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836630/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836630] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1836630/+attachment/5277200/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1836630 Title: System76 Oryx Pro (oryp5) with 5.0.0-21: Fail to resume from suspend Status in linux package in Ubuntu: Confirmed Status in linux-hwe-edge package in Ubuntu: Confirmed Bug description: After upgrading the Ubuntu kernel to version 5.0.0-21, the System76 Oryx Pro (oryp5) fails to resume from suspend when using discrete NVIDIA graphics The issue can be created on this hardware by following these steps: - Install Ubuntu 18.04.2 - Add the proposed updates: https://wiki.ubuntu.com/Testing/EnableProposed - Upgrade: sudo apt-get updatesudo apt-get dist-upgrade - Install 5.0 HWE kernel: sudo apt-get install linux-generic-hwe-18.04-edge - Install NVIDIA driver: sudo apt-get install nvidia-driver-430 - Reboot: sudo reboot - Attempt suspend/resume cycle This occurred after upgrading the kernel from version 5.0.0-20. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: system76 1721 F pulseaudio /dev/snd/controlC0: system76 1721 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 MachineType: System76 Oryx Pro NonfreeKernelModules: nvidia_modeset nvidia Package: linux-hwe-edge ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-21-generic root=UUID=10b5d457-8884-4b50-bd82-9b38e7f36564 ro ProcVersionSignature: Ubuntu 5.0.0-21.22~18.04.1-generic 5.0.15 RelatedPackageVersions: linux-restricted-modules-5.0.0-21-generic N/A linux-backports-modules-5.0.0-21-generic N/A linux-firmware1.173.9 Tags: bionic Uname: Linux 5.0.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm sudo _MarkForUpload: True dmi.bios.date: 05/07/2019 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.08 dmi.board.asset.tag: Tag 12345 dmi.board.name: Oryx Pro dmi.board.vendor: System76 dmi.board.version: oryp5 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: System76 dmi.chassis.version: oryp5 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.08:bd05/07/2019:svnSystem76:pnOryxPro:pvroryp5:rvnSystem76:rnOryxPro:rvroryp5:cvnSystem76:ct10:cvroryp5: dmi.product.family: Not Applicable dmi.product.name: Oryx Pro dmi.product.sku: Not Applicable dmi.product.version: oryp5 dmi.sys.vendor: System76 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836630/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836630] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1836630/+attachment/5277209/+files/PulseList.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1836630 Title: System76 Oryx Pro (oryp5) with 5.0.0-21: Fail to resume from suspend Status in linux package in Ubuntu: Confirmed Status in linux-hwe-edge package in Ubuntu: Confirmed Bug description: After upgrading the Ubuntu kernel to version 5.0.0-21, the System76 Oryx Pro (oryp5) fails to resume from suspend when using discrete NVIDIA graphics The issue can be created on this hardware by following these steps: - Install Ubuntu 18.04.2 - Add the proposed updates: https://wiki.ubuntu.com/Testing/EnableProposed - Upgrade: sudo apt-get updatesudo apt-get dist-upgrade - Install 5.0 HWE kernel: sudo apt-get install linux-generic-hwe-18.04-edge - Install NVIDIA driver: sudo apt-get install nvidia-driver-430 - Reboot: sudo reboot - Attempt suspend/resume cycle This occurred after upgrading the kernel from version 5.0.0-20. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: system76 1721 F pulseaudio /dev/snd/controlC0: system76 1721 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 MachineType: System76 Oryx Pro NonfreeKernelModules: nvidia_modeset nvidia Package: linux-hwe-edge ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-21-generic root=UUID=10b5d457-8884-4b50-bd82-9b38e7f36564 ro ProcVersionSignature: Ubuntu 5.0.0-21.22~18.04.1-generic 5.0.15 RelatedPackageVersions: linux-restricted-modules-5.0.0-21-generic N/A linux-backports-modules-5.0.0-21-generic N/A linux-firmware1.173.9 Tags: bionic Uname: Linux 5.0.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm sudo _MarkForUpload: True dmi.bios.date: 05/07/2019 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.08 dmi.board.asset.tag: Tag 12345 dmi.board.name: Oryx Pro dmi.board.vendor: System76 dmi.board.version: oryp5 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: System76 dmi.chassis.version: oryp5 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.08:bd05/07/2019:svnSystem76:pnOryxPro:pvroryp5:rvnSystem76:rnOryxPro:rvroryp5:cvnSystem76:ct10:cvroryp5: dmi.product.family: Not Applicable dmi.product.name: Oryx Pro dmi.product.sku: Not Applicable dmi.product.version: oryp5 dmi.sys.vendor: System76 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836630/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836630] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1836630/+attachment/5277202/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1836630 Title: System76 Oryx Pro (oryp5) with 5.0.0-21: Fail to resume from suspend Status in linux package in Ubuntu: Confirmed Status in linux-hwe-edge package in Ubuntu: Confirmed Bug description: After upgrading the Ubuntu kernel to version 5.0.0-21, the System76 Oryx Pro (oryp5) fails to resume from suspend when using discrete NVIDIA graphics The issue can be created on this hardware by following these steps: - Install Ubuntu 18.04.2 - Add the proposed updates: https://wiki.ubuntu.com/Testing/EnableProposed - Upgrade: sudo apt-get updatesudo apt-get dist-upgrade - Install 5.0 HWE kernel: sudo apt-get install linux-generic-hwe-18.04-edge - Install NVIDIA driver: sudo apt-get install nvidia-driver-430 - Reboot: sudo reboot - Attempt suspend/resume cycle This occurred after upgrading the kernel from version 5.0.0-20. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: system76 1721 F pulseaudio /dev/snd/controlC0: system76 1721 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 MachineType: System76 Oryx Pro NonfreeKernelModules: nvidia_modeset nvidia Package: linux-hwe-edge ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-21-generic root=UUID=10b5d457-8884-4b50-bd82-9b38e7f36564 ro ProcVersionSignature: Ubuntu 5.0.0-21.22~18.04.1-generic 5.0.15 RelatedPackageVersions: linux-restricted-modules-5.0.0-21-generic N/A linux-backports-modules-5.0.0-21-generic N/A linux-firmware1.173.9 Tags: bionic Uname: Linux 5.0.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm sudo _MarkForUpload: True dmi.bios.date: 05/07/2019 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.08 dmi.board.asset.tag: Tag 12345 dmi.board.name: Oryx Pro dmi.board.vendor: System76 dmi.board.version: oryp5 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: System76 dmi.chassis.version: oryp5 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.08:bd05/07/2019:svnSystem76:pnOryxPro:pvroryp5:rvnSystem76:rnOryxPro:rvroryp5:cvnSystem76:ct10:cvroryp5: dmi.product.family: Not Applicable dmi.product.name: Oryx Pro dmi.product.sku: Not Applicable dmi.product.version: oryp5 dmi.sys.vendor: System76 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836630/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836630] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1836630/+attachment/5277207/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1836630 Title: System76 Oryx Pro (oryp5) with 5.0.0-21: Fail to resume from suspend Status in linux package in Ubuntu: Confirmed Status in linux-hwe-edge package in Ubuntu: Confirmed Bug description: After upgrading the Ubuntu kernel to version 5.0.0-21, the System76 Oryx Pro (oryp5) fails to resume from suspend when using discrete NVIDIA graphics The issue can be created on this hardware by following these steps: - Install Ubuntu 18.04.2 - Add the proposed updates: https://wiki.ubuntu.com/Testing/EnableProposed - Upgrade: sudo apt-get updatesudo apt-get dist-upgrade - Install 5.0 HWE kernel: sudo apt-get install linux-generic-hwe-18.04-edge - Install NVIDIA driver: sudo apt-get install nvidia-driver-430 - Reboot: sudo reboot - Attempt suspend/resume cycle This occurred after upgrading the kernel from version 5.0.0-20. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: system76 1721 F pulseaudio /dev/snd/controlC0: system76 1721 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 MachineType: System76 Oryx Pro NonfreeKernelModules: nvidia_modeset nvidia Package: linux-hwe-edge ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-21-generic root=UUID=10b5d457-8884-4b50-bd82-9b38e7f36564 ro ProcVersionSignature: Ubuntu 5.0.0-21.22~18.04.1-generic 5.0.15 RelatedPackageVersions: linux-restricted-modules-5.0.0-21-generic N/A linux-backports-modules-5.0.0-21-generic N/A linux-firmware1.173.9 Tags: bionic Uname: Linux 5.0.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm sudo _MarkForUpload: True dmi.bios.date: 05/07/2019 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.08 dmi.board.asset.tag: Tag 12345 dmi.board.name: Oryx Pro dmi.board.vendor: System76 dmi.board.version: oryp5 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: System76 dmi.chassis.version: oryp5 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.08:bd05/07/2019:svnSystem76:pnOryxPro:pvroryp5:rvnSystem76:rnOryxPro:rvroryp5:cvnSystem76:ct10:cvroryp5: dmi.product.family: Not Applicable dmi.product.name: Oryx Pro dmi.product.sku: Not Applicable dmi.product.version: oryp5 dmi.sys.vendor: System76 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836630/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836630] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1836630/+attachment/5277204/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1836630 Title: System76 Oryx Pro (oryp5) with 5.0.0-21: Fail to resume from suspend Status in linux package in Ubuntu: Confirmed Status in linux-hwe-edge package in Ubuntu: Confirmed Bug description: After upgrading the Ubuntu kernel to version 5.0.0-21, the System76 Oryx Pro (oryp5) fails to resume from suspend when using discrete NVIDIA graphics The issue can be created on this hardware by following these steps: - Install Ubuntu 18.04.2 - Add the proposed updates: https://wiki.ubuntu.com/Testing/EnableProposed - Upgrade: sudo apt-get updatesudo apt-get dist-upgrade - Install 5.0 HWE kernel: sudo apt-get install linux-generic-hwe-18.04-edge - Install NVIDIA driver: sudo apt-get install nvidia-driver-430 - Reboot: sudo reboot - Attempt suspend/resume cycle This occurred after upgrading the kernel from version 5.0.0-20. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: system76 1721 F pulseaudio /dev/snd/controlC0: system76 1721 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 MachineType: System76 Oryx Pro NonfreeKernelModules: nvidia_modeset nvidia Package: linux-hwe-edge ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-21-generic root=UUID=10b5d457-8884-4b50-bd82-9b38e7f36564 ro ProcVersionSignature: Ubuntu 5.0.0-21.22~18.04.1-generic 5.0.15 RelatedPackageVersions: linux-restricted-modules-5.0.0-21-generic N/A linux-backports-modules-5.0.0-21-generic N/A linux-firmware1.173.9 Tags: bionic Uname: Linux 5.0.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm sudo _MarkForUpload: True dmi.bios.date: 05/07/2019 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.08 dmi.board.asset.tag: Tag 12345 dmi.board.name: Oryx Pro dmi.board.vendor: System76 dmi.board.version: oryp5 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: System76 dmi.chassis.version: oryp5 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.08:bd05/07/2019:svnSystem76:pnOryxPro:pvroryp5:rvnSystem76:rnOryxPro:rvroryp5:cvnSystem76:ct10:cvroryp5: dmi.product.family: Not Applicable dmi.product.name: Oryx Pro dmi.product.sku: Not Applicable dmi.product.version: oryp5 dmi.sys.vendor: System76 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836630/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836630] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1836630/+attachment/5277208/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1836630 Title: System76 Oryx Pro (oryp5) with 5.0.0-21: Fail to resume from suspend Status in linux package in Ubuntu: Confirmed Status in linux-hwe-edge package in Ubuntu: Confirmed Bug description: After upgrading the Ubuntu kernel to version 5.0.0-21, the System76 Oryx Pro (oryp5) fails to resume from suspend when using discrete NVIDIA graphics The issue can be created on this hardware by following these steps: - Install Ubuntu 18.04.2 - Add the proposed updates: https://wiki.ubuntu.com/Testing/EnableProposed - Upgrade: sudo apt-get updatesudo apt-get dist-upgrade - Install 5.0 HWE kernel: sudo apt-get install linux-generic-hwe-18.04-edge - Install NVIDIA driver: sudo apt-get install nvidia-driver-430 - Reboot: sudo reboot - Attempt suspend/resume cycle This occurred after upgrading the kernel from version 5.0.0-20. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: system76 1721 F pulseaudio /dev/snd/controlC0: system76 1721 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 MachineType: System76 Oryx Pro NonfreeKernelModules: nvidia_modeset nvidia Package: linux-hwe-edge ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-21-generic root=UUID=10b5d457-8884-4b50-bd82-9b38e7f36564 ro ProcVersionSignature: Ubuntu 5.0.0-21.22~18.04.1-generic 5.0.15 RelatedPackageVersions: linux-restricted-modules-5.0.0-21-generic N/A linux-backports-modules-5.0.0-21-generic N/A linux-firmware1.173.9 Tags: bionic Uname: Linux 5.0.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm sudo _MarkForUpload: True dmi.bios.date: 05/07/2019 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.08 dmi.board.asset.tag: Tag 12345 dmi.board.name: Oryx Pro dmi.board.vendor: System76 dmi.board.version: oryp5 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: System76 dmi.chassis.version: oryp5 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.08:bd05/07/2019:svnSystem76:pnOryxPro:pvroryp5:rvnSystem76:rnOryxPro:rvroryp5:cvnSystem76:ct10:cvroryp5: dmi.product.family: Not Applicable dmi.product.name: Oryx Pro dmi.product.sku: Not Applicable dmi.product.version: oryp5 dmi.sys.vendor: System76 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836630/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836630] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1836630/+attachment/5277210/+files/RfKill.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1836630 Title: System76 Oryx Pro (oryp5) with 5.0.0-21: Fail to resume from suspend Status in linux package in Ubuntu: Confirmed Status in linux-hwe-edge package in Ubuntu: Confirmed Bug description: After upgrading the Ubuntu kernel to version 5.0.0-21, the System76 Oryx Pro (oryp5) fails to resume from suspend when using discrete NVIDIA graphics The issue can be created on this hardware by following these steps: - Install Ubuntu 18.04.2 - Add the proposed updates: https://wiki.ubuntu.com/Testing/EnableProposed - Upgrade: sudo apt-get updatesudo apt-get dist-upgrade - Install 5.0 HWE kernel: sudo apt-get install linux-generic-hwe-18.04-edge - Install NVIDIA driver: sudo apt-get install nvidia-driver-430 - Reboot: sudo reboot - Attempt suspend/resume cycle This occurred after upgrading the kernel from version 5.0.0-20. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: system76 1721 F pulseaudio /dev/snd/controlC0: system76 1721 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 MachineType: System76 Oryx Pro NonfreeKernelModules: nvidia_modeset nvidia Package: linux-hwe-edge ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-21-generic root=UUID=10b5d457-8884-4b50-bd82-9b38e7f36564 ro ProcVersionSignature: Ubuntu 5.0.0-21.22~18.04.1-generic 5.0.15 RelatedPackageVersions: linux-restricted-modules-5.0.0-21-generic N/A linux-backports-modules-5.0.0-21-generic N/A linux-firmware1.173.9 Tags: bionic Uname: Linux 5.0.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm sudo _MarkForUpload: True dmi.bios.date: 05/07/2019 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.08 dmi.board.asset.tag: Tag 12345 dmi.board.name: Oryx Pro dmi.board.vendor: System76 dmi.board.version: oryp5 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: System76 dmi.chassis.version: oryp5 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.08:bd05/07/2019:svnSystem76:pnOryxPro:pvroryp5:rvnSystem76:rnOryxPro:rvroryp5:cvnSystem76:ct10:cvroryp5: dmi.product.family: Not Applicable dmi.product.name: Oryx Pro dmi.product.sku: Not Applicable dmi.product.version: oryp5 dmi.sys.vendor: System76 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836630/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836630] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1836630/+attachment/5277206/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1836630 Title: System76 Oryx Pro (oryp5) with 5.0.0-21: Fail to resume from suspend Status in linux package in Ubuntu: Confirmed Status in linux-hwe-edge package in Ubuntu: Confirmed Bug description: After upgrading the Ubuntu kernel to version 5.0.0-21, the System76 Oryx Pro (oryp5) fails to resume from suspend when using discrete NVIDIA graphics The issue can be created on this hardware by following these steps: - Install Ubuntu 18.04.2 - Add the proposed updates: https://wiki.ubuntu.com/Testing/EnableProposed - Upgrade: sudo apt-get updatesudo apt-get dist-upgrade - Install 5.0 HWE kernel: sudo apt-get install linux-generic-hwe-18.04-edge - Install NVIDIA driver: sudo apt-get install nvidia-driver-430 - Reboot: sudo reboot - Attempt suspend/resume cycle This occurred after upgrading the kernel from version 5.0.0-20. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: system76 1721 F pulseaudio /dev/snd/controlC0: system76 1721 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 MachineType: System76 Oryx Pro NonfreeKernelModules: nvidia_modeset nvidia Package: linux-hwe-edge ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-21-generic root=UUID=10b5d457-8884-4b50-bd82-9b38e7f36564 ro ProcVersionSignature: Ubuntu 5.0.0-21.22~18.04.1-generic 5.0.15 RelatedPackageVersions: linux-restricted-modules-5.0.0-21-generic N/A linux-backports-modules-5.0.0-21-generic N/A linux-firmware1.173.9 Tags: bionic Uname: Linux 5.0.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm sudo _MarkForUpload: True dmi.bios.date: 05/07/2019 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.08 dmi.board.asset.tag: Tag 12345 dmi.board.name: Oryx Pro dmi.board.vendor: System76 dmi.board.version: oryp5 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: System76 dmi.chassis.version: oryp5 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.08:bd05/07/2019:svnSystem76:pnOryxPro:pvroryp5:rvnSystem76:rnOryxPro:rvroryp5:cvnSystem76:ct10:cvroryp5: dmi.product.family: Not Applicable dmi.product.name: Oryx Pro dmi.product.sku: Not Applicable dmi.product.version: oryp5 dmi.sys.vendor: System76 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836630/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836630] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1836630/+attachment/5277211/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1836630 Title: System76 Oryx Pro (oryp5) with 5.0.0-21: Fail to resume from suspend Status in linux package in Ubuntu: Confirmed Status in linux-hwe-edge package in Ubuntu: Confirmed Bug description: After upgrading the Ubuntu kernel to version 5.0.0-21, the System76 Oryx Pro (oryp5) fails to resume from suspend when using discrete NVIDIA graphics The issue can be created on this hardware by following these steps: - Install Ubuntu 18.04.2 - Add the proposed updates: https://wiki.ubuntu.com/Testing/EnableProposed - Upgrade: sudo apt-get updatesudo apt-get dist-upgrade - Install 5.0 HWE kernel: sudo apt-get install linux-generic-hwe-18.04-edge - Install NVIDIA driver: sudo apt-get install nvidia-driver-430 - Reboot: sudo reboot - Attempt suspend/resume cycle This occurred after upgrading the kernel from version 5.0.0-20. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: system76 1721 F pulseaudio /dev/snd/controlC0: system76 1721 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 MachineType: System76 Oryx Pro NonfreeKernelModules: nvidia_modeset nvidia Package: linux-hwe-edge ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-21-generic root=UUID=10b5d457-8884-4b50-bd82-9b38e7f36564 ro ProcVersionSignature: Ubuntu 5.0.0-21.22~18.04.1-generic 5.0.15 RelatedPackageVersions: linux-restricted-modules-5.0.0-21-generic N/A linux-backports-modules-5.0.0-21-generic N/A linux-firmware1.173.9 Tags: bionic Uname: Linux 5.0.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm sudo _MarkForUpload: True dmi.bios.date: 05/07/2019 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.08 dmi.board.asset.tag: Tag 12345 dmi.board.name: Oryx Pro dmi.board.vendor: System76 dmi.board.version: oryp5 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: System76 dmi.chassis.version: oryp5 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.08:bd05/07/2019:svnSystem76:pnOryxPro:pvroryp5:rvnSystem76:rnOryxPro:rvroryp5:cvnSystem76:ct10:cvroryp5: dmi.product.family: Not Applicable dmi.product.name: Oryx Pro dmi.product.sku: Not Applicable dmi.product.version: oryp5 dmi.sys.vendor: System76 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836630/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836630] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1836630/+attachment/5277199/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1836630 Title: System76 Oryx Pro (oryp5) with 5.0.0-21: Fail to resume from suspend Status in linux package in Ubuntu: Confirmed Status in linux-hwe-edge package in Ubuntu: Confirmed Bug description: After upgrading the Ubuntu kernel to version 5.0.0-21, the System76 Oryx Pro (oryp5) fails to resume from suspend when using discrete NVIDIA graphics The issue can be created on this hardware by following these steps: - Install Ubuntu 18.04.2 - Add the proposed updates: https://wiki.ubuntu.com/Testing/EnableProposed - Upgrade: sudo apt-get updatesudo apt-get dist-upgrade - Install 5.0 HWE kernel: sudo apt-get install linux-generic-hwe-18.04-edge - Install NVIDIA driver: sudo apt-get install nvidia-driver-430 - Reboot: sudo reboot - Attempt suspend/resume cycle This occurred after upgrading the kernel from version 5.0.0-20. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: system76 1721 F pulseaudio /dev/snd/controlC0: system76 1721 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 MachineType: System76 Oryx Pro NonfreeKernelModules: nvidia_modeset nvidia Package: linux-hwe-edge ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-21-generic root=UUID=10b5d457-8884-4b50-bd82-9b38e7f36564 ro ProcVersionSignature: Ubuntu 5.0.0-21.22~18.04.1-generic 5.0.15 RelatedPackageVersions: linux-restricted-modules-5.0.0-21-generic N/A linux-backports-modules-5.0.0-21-generic N/A linux-firmware1.173.9 Tags: bionic Uname: Linux 5.0.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm sudo _MarkForUpload: True dmi.bios.date: 05/07/2019 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.08 dmi.board.asset.tag: Tag 12345 dmi.board.name: Oryx Pro dmi.board.vendor: System76 dmi.board.version: oryp5 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: System76 dmi.chassis.version: oryp5 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.08:bd05/07/2019:svnSystem76:pnOryxPro:pvroryp5:rvnSystem76:rnOryxPro:rvroryp5:cvnSystem76:ct10:cvroryp5: dmi.product.family: Not Applicable dmi.product.name: Oryx Pro dmi.product.sku: Not Applicable dmi.product.version: oryp5 dmi.sys.vendor: System76 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836630/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836630] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1836630/+attachment/5277212/+files/WifiSyslog.txt ** Changed in: linux-hwe-edge (Ubuntu) Status: New => Confirmed ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1836630 Title: System76 Oryx Pro (oryp5) with 5.0.0-21: Fail to resume from suspend Status in linux package in Ubuntu: Confirmed Status in linux-hwe-edge package in Ubuntu: Confirmed Bug description: After upgrading the Ubuntu kernel to version 5.0.0-21, the System76 Oryx Pro (oryp5) fails to resume from suspend when using discrete NVIDIA graphics The issue can be created on this hardware by following these steps: - Install Ubuntu 18.04.2 - Add the proposed updates: https://wiki.ubuntu.com/Testing/EnableProposed - Upgrade: sudo apt-get updatesudo apt-get dist-upgrade - Install 5.0 HWE kernel: sudo apt-get install linux-generic-hwe-18.04-edge - Install NVIDIA driver: sudo apt-get install nvidia-driver-430 - Reboot: sudo reboot - Attempt suspend/resume cycle This occurred after upgrading the kernel from version 5.0.0-20. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: system76 1721 F pulseaudio /dev/snd/controlC0: system76 1721 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 MachineType: System76 Oryx Pro NonfreeKernelModules: nvidia_modeset nvidia Package: linux-hwe-edge ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-21-generic root=UUID=10b5d457-8884-4b50-bd82-9b38e7f36564 ro ProcVersionSignature: Ubuntu 5.0.0-21.22~18.04.1-generic 5.0.15 RelatedPackageVersions: linux-restricted-modules-5.0.0-21-generic N/A linux-backports-modules-5.0.0-21-generic N/A linux-firmware1.173.9 Tags: bionic Uname: Linux 5.0.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm sudo _MarkForUpload: True dmi.bios.date: 05/07/2019 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.08 dmi.board.asset.tag: Tag 12345 dmi.board.name: Oryx Pro dmi.board.vendor: System76 dmi.board.version: oryp5 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: System76 dmi.chassis.version: oryp5 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.08:bd05/07/2019:svnSystem76:pnOryxPro:pvroryp5:rvnSystem76:rnOryxPro:rvroryp5:cvnSystem76:ct10:cvroryp5: dmi.product.family: Not Applicable dmi.product.name: Oryx Pro dmi.product.sku: Not Applicable dmi.product.version: oryp5 dmi.sys.vendor: System76 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836630/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836630] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1836630/+attachment/5277201/+files/IwConfig.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1836630 Title: System76 Oryx Pro (oryp5) with 5.0.0-21: Fail to resume from suspend Status in linux package in Ubuntu: Confirmed Status in linux-hwe-edge package in Ubuntu: Confirmed Bug description: After upgrading the Ubuntu kernel to version 5.0.0-21, the System76 Oryx Pro (oryp5) fails to resume from suspend when using discrete NVIDIA graphics The issue can be created on this hardware by following these steps: - Install Ubuntu 18.04.2 - Add the proposed updates: https://wiki.ubuntu.com/Testing/EnableProposed - Upgrade: sudo apt-get updatesudo apt-get dist-upgrade - Install 5.0 HWE kernel: sudo apt-get install linux-generic-hwe-18.04-edge - Install NVIDIA driver: sudo apt-get install nvidia-driver-430 - Reboot: sudo reboot - Attempt suspend/resume cycle This occurred after upgrading the kernel from version 5.0.0-20. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: system76 1721 F pulseaudio /dev/snd/controlC0: system76 1721 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 MachineType: System76 Oryx Pro NonfreeKernelModules: nvidia_modeset nvidia Package: linux-hwe-edge ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-21-generic root=UUID=10b5d457-8884-4b50-bd82-9b38e7f36564 ro ProcVersionSignature: Ubuntu 5.0.0-21.22~18.04.1-generic 5.0.15 RelatedPackageVersions: linux-restricted-modules-5.0.0-21-generic N/A linux-backports-modules-5.0.0-21-generic N/A linux-firmware1.173.9 Tags: bionic Uname: Linux 5.0.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm sudo _MarkForUpload: True dmi.bios.date: 05/07/2019 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.08 dmi.board.asset.tag: Tag 12345 dmi.board.name: Oryx Pro dmi.board.vendor: System76 dmi.board.version: oryp5 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: System76 dmi.chassis.version: oryp5 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.08:bd05/07/2019:svnSystem76:pnOryxPro:pvroryp5:rvnSystem76:rnOryxPro:rvroryp5:cvnSystem76:ct10:cvroryp5: dmi.product.family: Not Applicable dmi.product.name: Oryx Pro dmi.product.sku: Not Applicable dmi.product.version: oryp5 dmi.sys.vendor: System76 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836630/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1826691] Re: fwupd hangs after 19.04 upgrade from 18.10
** Changed in: linux (Ubuntu Disco) Status: Incomplete => Triaged ** Changed in: linux (Ubuntu Eoan) Status: Incomplete => Triaged ** Also affects: linux via https://bugs.freedesktop.org/show_bug.cgi?id=110604 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1826691 Title: fwupd hangs after 19.04 upgrade from 18.10 Status in Linux: Unknown Status in fwupd package in Ubuntu: Triaged Status in linux package in Ubuntu: Triaged Status in fwupd source package in Disco: Triaged Status in linux source package in Disco: Triaged Status in fwupd source package in Eoan: Triaged Status in linux source package in Eoan: Triaged Bug description: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu $ lsb_release -rd Description:Ubuntu 19.04 Release:19.04 Being a firmware updater, the machine is probably relevant - Dell 7730. 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center $ apt policy fwupd fwupd: Installed: (none) Candidate: 1.2.5-1ubuntu1 Version table: 1.2.5-1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages 100 /var/lib/dpkg/status 3) What you expected to happen I expected few/no issues after 19.04 upgrade. The fwupd process worked perfectly in 18.10. It's upgraded the firmware on my laptop twice since I installed 18.10. 4) What happened instead After upgrading from 18.10 to 19.04 I had an issues that when I tried to suspend my laptop using the same button press as previous, the laptop would be hot and screen flickering when I returned to reopen it. I thought there were power management issues in the upgrade, but I've traced it to fwupd not letting the PM suspend process complete (see dmesg below). I tried shutting down the fwupd daemon with systemctl but the command hangs forever. All of the fwupdmgr commands timeout. Thinking something might have broken in the upgrade, I tried uninstalling (purge) the fwupd package and reinstalling. Starting the process with systemctl hangs forever like stopping it. Trying to kill -9 the process does not work - in uninterruptible sleep (D). This crash is probably related. It happened a couple of ours before I tried to put it to sleep the last time before uninstalling fwupd. Apr 23 19:29:14 texas kernel: [ 133.673290] [drm] REG_WAIT timeout 10us * 160 tries - submit_channel_request line:246 Apr 23 19:29:14 texas kernel: [ 133.673348] WARNING: CPU: 6 PID: 2467 at drivers/gpu/drm/amd/amdgpu/../display/dc/dc_helper.c:249 generic_reg_wait.cold.3+0x25/0x2c [amdgpu] Apr 23 19:29:14 texas kernel: [ 133.673349] Modules linked in: thunderbolt rfcomm xt_owner ip6table_filter ip6_tables ipt_MASQUERADE iptable_nat nf_nat_ipv4 nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c bridge xt_CHECKSUM xt_tcpudp stp llc iptable_filter iptable_mangle bpfilter ccm snd_hda_codec_realtek snd_hda_codec_generic pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) cmac vboxdrv(OE) bnep binfmt_misc dell_rbtn nls_iso8859_1 joydev arc4 snd_soc_skl snd_soc_hdac_hda snd_hda_ext_core snd_soc_skl_ipc snd_soc_sst_ipc snd_soc_sst_dsp snd_soc_acpi_intel_match snd_soc_acpi snd_soc_core snd_compress ac97_bus intel_rapl snd_pcm_dmaengine x86_pkg_temp_thermal intel_powerclamp coretemp snd_hda_codec_hdmi kvm_intel snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep crct10dif_pclmul i915 snd_pcm crc32_pclmul iwlmvm uvcvideo amdgpu snd_seq_midi ghash_clmulni_intel snd_seq_midi_event mac80211 videobuf2_vmalloc kvmgt videobuf2_memops vfio_mdev videobuf2_v4l2 snd_rawmidi dell_laptop mdev videobuf2_common Apr 23 19:29:14 texas kernel: [ 133.673362] ledtrig_audio vfio_iommu_type1 videodev dell_smm_hwmon vfio snd_seq dell_wmi media kvm chash btusb snd_seq_device amd_iommu_v2 btrtl snd_timer btbcm dell_smbios gpu_sched irqbypass btintel dcdbas ttm aesni_intel iwlwifi bluetooth drm_kms_helper aes_x86_64 crypto_simd cryptd glue_helper rtsx_pci_ms input_leds snd drm ecdh_generic intel_cstate mei_me ucsi_acpi cfg80211 serio_raw dell_wmi_descriptor intel_wmi_thunderbolt wmi_bmof memstick i2c_algo_bit mei fb_sys_fops intel_rapl_perf idma64 syscopyarea hid_multitouch processor_thermal_device soundcore sysfillrect virt_dma typec_ucsi sysimgblt intel_soc_dts_iosf intel_pch_thermal typec int3403_thermal int340x_thermal_zone dell_smo8800 acpi_pad intel_hid int3400_thermal mac_hid acpi_thermal_rel sparse_keymap sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables autofs4 hid_generic rtsx_pci_sdmmc nvme e1000e i2c_i801 intel_lpss_pci rtsx_pci nvme_core intel_lpss i2c_hid wmi hid video pinctrl_cannonlake pinctrl_intel Apr 23 19:29:14 texas kernel: [ 133.673381]
[Kernel-packages] [Bug 1836635] Re: Bionic: support for Solarflare X2542 network adapter (sfc driver)
** Description changed:
[Impact]
- * Support for Solarflare X2542 network adapter
-(Medford2 / SFC9250) in the sfc driver.
+ * Support for Solarflare X2542 network adapter
+ (Medford2 / SFC9250) in the sfc driver.
- * This network adapter is present on recent hardware,
-at least HP 2019 and Dell PowerEdge R740xd systems.
+ * This network adapter is present on recent hardware,
+ at least HP 2019 and Dell PowerEdge R740xd systems.
- * On recent-hardware deployments that would rather use
-the Bionic LTS / GA supported kernel and cannot move
-to HWE kernels this adapter is non functional at all.
+ * On recent-hardware deployments that would rather use
+ the Bionic LTS / GA supported kernel and cannot move
+ to HWE kernels this adapter is non functional at all.
[Test Case]
- * The X2542 adapter has been exercised with iperf3 and nc
-across 2 hosts on 25G link speed w/ MTUs 1400/1500/9000
-on both directions, for 1 week.
+ * The X2542 adapter has been exercised with iperf3 and nc
+ across 2 hosts on 25G link speed w/ MTUs 1400/1500/9000
+ on both directions, for 1 week.
-Its performance is on par with the Cosmic 4.18 kernel
-(which contains all these patches) and the out-of-tree
-driver from the vendor.
+ Its performance is on par with the Cosmic 4.18 kernel
+ (which contains all these patches) and the out-of-tree
+ driver from the vendor.
- * The 7000 series adapter (for regression testing an old model,
-supported previously) has been exercised with iperf and netperf
-(TCP_STREAM, UDP_STREAM, TCP_RR, UDP_RR, and TCP_CRR) in one
-host (client/server in different adapter ports isolated with
-network namespaces, so traffic goes through the network switch),
-on 10G link speed on MTUs 1500/9000, for 1 weekend.
+ * The 7000 series adapter (for regression testing an old model,
+ supported previously) has been exercised with iperf and netperf
+ (TCP_STREAM, UDP_STREAM, TCP_RR, UDP_RR, and TCP_CRR) in one
+ host (client/server in different adapter ports isolated with
+ network namespaces, so traffic goes through the network switch),
+ on 10G link speed on MTUs 1500/9000, for 1 weekend.
-No regressions observed between the original and test kernels.
+ No regressions observed between the original and test kernels.
[Regression Potential]
* The patchset touches a lot of the sfc driver, so the potential
-for regression definitely exists. It has been tested on other
-adapter which uses the old code, and no regressions were found.
+for regression definitely exists. Thus, a lot of consideration
+and testing happened:
+
+ * It has been tested on other adapter which uses the old code,
+and no regressions were found so far (see 7000 series above).
+
+ * The patchset essentially moves the driver in Bionic up in the
+upstream 'git log':
+- since commit d4a7a8893d4c ("sfc: pass valid pointers from
efx_enqueue_unwind")
+- until commit 7f61e6c6279b ("sfc: support FEC configuration through
ethtool")
+- except for 2 commits (not needed / unrelated)
+ - commit 42356d9a137b ("sfc: support RSS spreading of ethtool ntuple
filters")
+ - commit 9baeb5eb1f83 ("sfc: falcon: remove duplicated bit-wise or of
LOOPBACK_SGMII")
+- plus 2 more recent commits (fixes)
+ - commit 458bd99e4974 ("sfc: remove ctpio_dmabuf_start from stats")
+ - commit 0c235113b3c4 ("sfc: stop the TX queue before pushing new
buffers")
+
+ * The patchset is exclusively cherry-picks, no single backport.
** Description changed:
[Impact]
* Support for Solarflare X2542 network adapter
(Medford2 / SFC9250) in the sfc driver.
* This network adapter is present on recent hardware,
at least HP 2019 and Dell PowerEdge R740xd systems.
* On recent-hardware deployments that would rather use
the Bionic LTS / GA supported kernel and cannot move
to HWE kernels this adapter is non functional at all.
[Test Case]
* The X2542 adapter has been exercised with iperf3 and nc
across 2 hosts on 25G link speed w/ MTUs 1400/1500/9000
on both directions, for 1 week.
Its performance is on par with the Cosmic 4.18 kernel
(which contains all these patches) and the out-of-tree
driver from the vendor.
* The 7000 series adapter (for regression testing an old model,
supported previously) has been exercised with iperf and netperf
(TCP_STREAM, UDP_STREAM, TCP_RR, UDP_RR, and TCP_CRR) in one
host (client/server in different adapter ports isolated with
network namespaces, so traffic goes through the network switch),
on 10G link speed on MTUs 1500/9000, for 1 weekend.
No regressions observed between the original and test kernels.
[Regression Potential]
- * The patchset touches a lot of the sfc driver, so the potential
-for regression definitely exists. Thus, a l
[Kernel-packages] [Bug 1836635] Re: Bionic: support for Solarflare X2542 network adapter (sfc driver)
[Bionic][PULL] sfc: patches for LP#1836635
https://lists.ubuntu.com/archives/kernel-team/2019-July/102196.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/1836635
Title:
Bionic: support for Solarflare X2542 network adapter (sfc driver)
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Bionic:
In Progress
Status in linux source package in Cosmic:
Invalid
Status in linux source package in Disco:
Invalid
Status in linux source package in Eoan:
Invalid
Bug description:
[Impact]
* Support for Solarflare X2542 network adapter
(Medford2 / SFC9250) in the Bionic sfc driver.
* This network adapter is present on recent hardware,
at least HP 2019 and Dell PowerEdge R740xd systems.
* On recent-hardware deployments that would rather use
the Bionic LTS / GA supported kernel and cannot move
to HWE kernels this adapter is non functional at all.
[Test Case]
* The X2542 adapter has been exercised with iperf3 and nc
across 2 hosts on 25G link speed w/ MTUs 1400/1500/9000
on both directions, for 1 week.
Its performance is on par with the Cosmic 4.18 kernel
(which contains all these patches) and the out-of-tree
driver from the vendor.
* The 7000 series adapter (for regression testing an old model,
supported previously) has been exercised with iperf and netperf
(TCP_STREAM, UDP_STREAM, TCP_RR, UDP_RR, and TCP_CRR) in one
host (client/server in different adapter ports isolated with
network namespaces, so traffic goes through the network switch),
on 10G link speed on MTUs 1500/9000, for 1 weekend.
No regressions observed between the original and test kernels.
[Regression Potential]
* The patchset touches a lot of the sfc driver, so the potential
for regression definitely exists. Thus, a lot of consideration
and testing happened:
* It has been tested on other adapter which uses the old code,
and no regressions were found so far (see 7000 series above).
* The patchset is exclusively cherry-picks, no single backport.
* The patchset essentially moves the Bionic driver up in the
upstream 'git log --oneline -- drivers/net/ethernet/sfc/':
- since commit d4a7a8893d4c ("sfc: pass valid pointers from
efx_enqueue_unwind")
- until commit 7f61e6c6279b ("sfc: support FEC configuration through
ethtool")
- except for 2 commits (not needed / unrelated)
- commit 42356d9a137b ("sfc: support RSS spreading of ethtool ntuple
filters")
- commit 9baeb5eb1f83 ("sfc: falcon: remove duplicated bit-wise or of
LOOPBACK_SGMII")
- plus 2 more recent commits (fixes)
- commit 458bd99e4974 ("sfc: remove ctpio_dmabuf_start from stats")
- commit 0c235113b3c4 ("sfc: stop the TX queue before pushing new
buffers")
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836635/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836614] Re: Disco update: 5.0.18 upstream stable release
Commit "s390/mm: convert to the generic get_user_pages_fast code" implements a gup_fast_permitted() function which expects 2 arguments. However at that point the general mm code is using 3 arguments. This gets changed in 5.0.19 by "mm/gup: Remove the 'write' parameter from gup_fast_permitted()". To avoid breaking the build on s390x this one patch from 5.0.19 got moved into 5.0.18. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1836614 Title: Disco update: 5.0.18 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Disco: In Progress 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 following upstream stable patches should be included in the Ubuntu kernel: 5.0.18 upstream stable release from git://git.kernel.org/ The following patches were applied: * locking/rwsem: Prevent decrement of reader count before increment * x86/speculation/mds: Revert CPU buffer clear on double fault exit * x86/speculation/mds: Improve CPU buffer clear documentation * objtool: Fix function fallthrough detection * arm64: dts: rockchip: fix IO domain voltage setting of APIO5 on rockpro64 * arm64: dts: rockchip: Disable DCMDs on RK3399's eMMC controller. * ARM: dts: qcom: ipq4019: enlarge PCIe BAR range * ARM: dts: exynos: Fix interrupt for shared EINTs on Exynos5260 * ARM: dts: exynos: Fix audio (microphone) routing on Odroid XU3 * mmc: sdhci-of-arasan: Add DTS property to disable DCMDs. * ARM: exynos: Fix a leaked reference by adding missing of_node_put * power: supply: axp288_charger: Fix unchecked return value * power: supply: axp288_fuel_gauge: Add ACEPC T8 and T11 mini PCs to the blacklist * arm64: mmap: Ensure file offset is treated as unsigned * arm64: arch_timer: Ensure counter register reads occur with seqlock held * arm64: compat: Reduce address limit * arm64: Clear OSDLR_EL1 on CPU boot * arm64: Save and restore OSDLR_EL1 across suspend/resume * sched/x86: Save [ER]FLAGS on context switch * x86/MCE: Add an MCE-record filtering function * x86/MCE/AMD: Turn off MC4_MISC thresholding on all family 0x15 models * x86/MCE/AMD: Carve out the MC4_MISC thresholding quirk * x86/MCE: Group AMD function prototypes in * x86/MCE/AMD: Don't report L1 BTB MCA errors on some family 17h models * crypto: crypto4xx - fix ctr-aes missing output IV * crypto: crypto4xx - fix cfb and ofb "overran dst buffer" issues * crypto: salsa20 - don't access already-freed walk.iv * crypto: lrw - don't access already-freed walk.iv * crypto: chacha-generic - fix use as arm64 no-NEON fallback * crypto: chacha20poly1305 - set cra_name correctly * crypto: ccp - Do not free psp_master when PLATFORM_INIT fails * crypto: vmx - fix copy-paste error in CTR mode * crypto: skcipher - don't WARN on unprocessed data after slow walk step * crypto: crct10dif-generic - fix use via crypto_shash_digest() * crypto: x86/crct10dif-pcl - fix use via crypto_shash_digest() * crypto: arm64/gcm-aes-ce - fix no-NEON fallback code * crypto: gcm - fix incompatibility between "gcm" and "gcm_base" * crypto: rockchip - update IV buffer to contain the next IV * crypto: caam/qi2 - fix zero-length buffer DMA mapping * crypto: caam/qi2 - fix DMA mapping of stack memory * crypto: caam/qi2 - generate hash keys in-place * crypto: arm/aes-neonbs - don't access already-freed walk.iv * crypto: arm64/aes-neonbs - don't access already-freed walk.iv * mmc: tegra: fix ddr signaling for non-ddr modes * mmc: core: Fix tag set memory leak * mmc: sdhci-pci: Fix BYT OCP setting * ALSA: line6: toneport: Fix broken usage of timer for delayed execution * ALSA: usb-audio: Fix a memory leak bug * ALSA: hda/realtek - EAPD turn on later * ASoC: max98090: Fix restore of DAPM Muxes * ASoC: RT5677-SPI: Disable 16Bit SPI Transfers * ASoC: fsl_esai: Fix missing break in switch statement * ASoC: codec: hdac_hdmi add device_link to card device * bpf, arm64: remove prefetch insn in xadd mapping * crypto: ccree - remove special handling of chained sg * crypto: ccree - fix mem leak on error path * crypto: ccree - don't map MAC key on stack * crypto: ccree - use correct internal state sizes for export * crypto: ccree - don't map AEAD key and IV on stack * crypto: ccree - pm resume first enable the source clk * crypto: ccree - HOST_POWER_DOWN_EN should be the last CC access during suspend * crypto: ccree - add function to handle cryptocell tee fips error * crypto: cc
[Kernel-packages] [Bug 1835279] Re: 4.15.0-54.58-generic 4.15.18: oops/BUG on LUKS open
We're now opening the LUKS device using the master key directly and the crash is happening again in both the original 4.15.0-54-generic (buildd@lgw01-amd64-014) kernel or the patched 4.15.0-54-generic (arighi@kathleen) kernel. The backtrace is very similar but unlike the previous scenario it happens even if delays as large as 5000 ms are placed between partition table re-reading and commands. The LUKS device is created and accessed using the following commands: # cryptsetup -q luksFormat --type luks2 --pbkdf-memory 1 --master- key-file # LD_PRELOAD=/lib/no-udev.so cryptsetup open --master-key-file -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1835279 Title: 4.15.0-54.58-generic 4.15.18: oops/BUG on LUKS open Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: In Progress Bug description: This is Linux version 4.15.0-54-generic (buildd@lgw01-amd64-014) (gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1)) #58-Ubuntu SMP Mon Jun 24 10:55:24 UTC 2019 (Ubuntu 4.15.0-54.58-generic 4.15.18), from pc- kernel_240.snap Version signature: 4.15.0-54.58-generic 4.15.18 Issue is non-deterministic, and happens in roughly 20% of the attempts. Running on: qemu-kvm, command line: kvm \ -bios /usr/share/ovmf/OVMF.fd \ -smp 2 -m 512 -netdev user,id=mynet0,hostfwd=tcp::8022-:22,hostfwd=tcp::8090-:80 \ -device virtio-net-pci,netdev=mynet0 \ -drive file=pc.img,format=raw Commands that caused the problem: cryptsetup -q --type luks2 --key-file luksFormat /dev/sda4 LD_PRELOAD=/lib/no-udev.so cryptsetup --type luks2 --key-file open /dev/sda4 crypt-data Notes: - See https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1589083 for more information on the no-udev workaround. - The commands are scripted. Also tried to add a 200ms and 1s interval before opening the device. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1835279/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835279] Re: 4.15.0-54.58-generic 4.15.18: oops/BUG on LUKS open
** Attachment added: "4.15.0-54-generic #58+lp1835279 kernel log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1835279/+attachment/5277230/+files/kernel-arighi.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1835279 Title: 4.15.0-54.58-generic 4.15.18: oops/BUG on LUKS open Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: In Progress Bug description: This is Linux version 4.15.0-54-generic (buildd@lgw01-amd64-014) (gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1)) #58-Ubuntu SMP Mon Jun 24 10:55:24 UTC 2019 (Ubuntu 4.15.0-54.58-generic 4.15.18), from pc- kernel_240.snap Version signature: 4.15.0-54.58-generic 4.15.18 Issue is non-deterministic, and happens in roughly 20% of the attempts. Running on: qemu-kvm, command line: kvm \ -bios /usr/share/ovmf/OVMF.fd \ -smp 2 -m 512 -netdev user,id=mynet0,hostfwd=tcp::8022-:22,hostfwd=tcp::8090-:80 \ -device virtio-net-pci,netdev=mynet0 \ -drive file=pc.img,format=raw Commands that caused the problem: cryptsetup -q --type luks2 --key-file luksFormat /dev/sda4 LD_PRELOAD=/lib/no-udev.so cryptsetup --type luks2 --key-file open /dev/sda4 crypt-data Notes: - See https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1589083 for more information on the no-udev workaround. - The commands are scripted. Also tried to add a 200ms and 1s interval before opening the device. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1835279/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1833147] Re: hns: attempt to restart autoneg when disabled should report error
verification = cosmic = ubuntu@d05-3:~$ cat /proc/version Linux version 4.18.0-26-generic (buildd@bos02-arm64-042) (gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1~18.10.1)) #27-Ubuntu SMP Tue Jul 2 15:36:34 UTC 2019 ubuntu@d05-3:~$ sudo ethtool -s enahisic2i1 autoneg off ubuntu@d05-3:~$ sudo ethtool -r enahisic2i1 Cannot restart autonegotiation: Invalid argument = bionic = ubuntu@d05-3:~$ cat /proc/version Linux version 4.15.0-55-generic (buildd@bos02-arm64-065) (gcc version 7.4.0 (Ubuntu/Linaro 7.4.0-1ubuntu1~18.04.1)) #60-Ubuntu SMP Tue Jul 2 18:23:38 UTC 2019 ubuntu@d05-3:~$ sudo ethtool -s enahisic2i1 autoneg off ubuntu@d05-3:~$ sudo ethtool -r enahisic2i1 Cannot restart autonegotiation: Invalid argument ** Tags removed: verification-needed-bionic verification-needed-cosmic ** Tags added: verification-done-bionic verification-done-cosmic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1833147 Title: hns: attempt to restart autoneg when disabled should report error Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Committed Bug description: [Impact] Asking the driver to restart autonegotiation silently fails when autonegotation has been disabled. It should report an error. [Test Case] sudo ethtool -s ethX autoneg off sudo ethtool -r ethX [Fix] ed29ca8b95925 net: hns: Restart autoneg need return failed when autoneg off [Regression Risk] Fix is restricted to the hns driver, which is the driver for the nics on the Hi1616 SoC. Regressions would therefore be limited to platforms using this SoC, such as the HiSilicon D05 board. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1833147/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836635] Re: Bionic: support for Solarflare X2542 network adapter (sfc driver)
Regression test results/log/script,
for documentation purposes.
** Attachment added: "lp1836635-test-regression.tar.xz"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836635/+attachment/5277232/+files/lp1836635-test-regression.tar.xz
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1836635
Title:
Bionic: support for Solarflare X2542 network adapter (sfc driver)
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Bionic:
In Progress
Status in linux source package in Cosmic:
Invalid
Status in linux source package in Disco:
Invalid
Status in linux source package in Eoan:
Invalid
Bug description:
[Impact]
* Support for Solarflare X2542 network adapter
(Medford2 / SFC9250) in the Bionic sfc driver.
* This network adapter is present on recent hardware,
at least HP 2019 and Dell PowerEdge R740xd systems.
* On recent-hardware deployments that would rather use
the Bionic LTS / GA supported kernel and cannot move
to HWE kernels this adapter is non functional at all.
[Test Case]
* The X2542 adapter has been exercised with iperf3 and nc
across 2 hosts on 25G link speed w/ MTUs 1400/1500/9000
on both directions, for 1 week.
Its performance is on par with the Cosmic 4.18 kernel
(which contains all these patches) and the out-of-tree
driver from the vendor.
* The 7000 series adapter (for regression testing an old model,
supported previously) has been exercised with iperf and netperf
(TCP_STREAM, UDP_STREAM, TCP_RR, UDP_RR, and TCP_CRR) in one
host (client/server in different adapter ports isolated with
network namespaces, so traffic goes through the network switch),
on 10G link speed on MTUs 1500/9000, for 1 weekend.
No regressions observed between the original and test kernels.
[Regression Potential]
* The patchset touches a lot of the sfc driver, so the potential
for regression definitely exists. Thus, a lot of consideration
and testing happened:
* It has been tested on other adapter which uses the old code,
and no regressions were found so far (see 7000 series above).
* The patchset is exclusively cherry-picks, no single backport.
* The patchset essentially moves the Bionic driver up in the
upstream 'git log --oneline -- drivers/net/ethernet/sfc/':
- since commit d4a7a8893d4c ("sfc: pass valid pointers from
efx_enqueue_unwind")
- until commit 7f61e6c6279b ("sfc: support FEC configuration through
ethtool")
- except for 2 commits (not needed / unrelated)
- commit 42356d9a137b ("sfc: support RSS spreading of ethtool ntuple
filters")
- commit 9baeb5eb1f83 ("sfc: falcon: remove duplicated bit-wise or of
LOOPBACK_SGMII")
- plus 2 more recent commits (fixes)
- commit 458bd99e4974 ("sfc: remove ctpio_dmabuf_start from stats")
- commit 0c235113b3c4 ("sfc: stop the TX queue before pushing new
buffers")
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836635/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828868] Re: crashdump fails on HiSilicon D06
** Tags removed: verification-needed-cosmic ** Tags added: verification-done-cosmic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1828868 Title: crashdump fails on HiSilicon D06 Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Committed Status in linux source package in Disco: Fix Committed Bug description: [Impact] The crashdump kernel fails to boot on HiSilicon D06, and likely other SMMUv3 ARM systems. [Test Case] sudo apt install linux-crashdump Adjust crashkernel= parameter in /etc/default/grub.d/kdump-tools.cfg as appropriate (for D06, crashkernel=512M) Add "arm_smmu_v3.disable_bypass=1" to the kernel command line sudo reboot (needed to add crashkernel= param) echo 1 | sudo tee /proc/sys/kernel/sysrq echo c | sudo tee /proc/sysrq-trigger (Note to self - the following is needed on our systems w/ Mellanox adapters: ubuntu@d06-3:~$ grep blacklist /etc/default/kdump-tools KDUMP_CMDLINE_APPEND="nr_cpus=1 systemd.unit=kdump-tools-dump.service module_blacklist=mlx5_core") [Fix] 3f54c447df34f iommu/arm-smmu-v3: Don't disable SMMU in kdump kernel [Regression Risk] Restricted to SMMUv3 arm64-based systems. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1828868/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835700] Re: linux: 5.2.0-8.9 -proposed tracker
** Tags added: regression-testing-passed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1835700 Title: linux: 5.2.0-8.9 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete 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-release series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in linux package in Ubuntu: New Status in linux source package in Eoan: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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 phase: Testing phase-changed: Tuesday, 09. July 2019 22:34 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1835700/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835700] Re: linux: 5.2.0-8.9 -proposed tracker
** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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 phase: Testing phase-changed: Tuesday, 09. July 2019 22:34 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED - regression-testing: Ongoing -- testing in progress variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1835700 Title: linux: 5.2.0-8.9 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete 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-release series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in linux package in Ubuntu: New Status in linux source package in Eoan: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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 phase: Testing phase-changed: Tuesday, 09. July 2019 22:34 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1835700/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1833140] Re: hns: fix ICMP6 neighbor solicitation messages discard problem
Smoke test successful on each release. ** Tags removed: verification-needed-bionic verification-needed-cosmic verification-needed-disco ** Tags added: verification-done-bionic verification-done-cosmic verification-done-disco -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1833140 Title: hns: fix ICMP6 neighbor solicitation messages discard problem Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Committed Status in linux source package in Disco: Fix Committed Status in linux source package in Eoan: In Progress Bug description: [Impact] ICMP6 neighbor solicitation messages are discarded. [Test Case] Regression tested only [Fix] ea401685a20b5 net: hns: fix unsigned comparison to less than zero f058e46855dcb net: hns: fix ICMP6 neighbor solicitation messages discard problem [Regression Risk] Fix is restricted to the hns driver, which is the driver for the nics on the Hi1616 SoC. Regressions would therefore be limited to platforms using this SoC, such as the HiSilicon D05 board. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1833140/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828868] Re: crashdump fails on HiSilicon D06
** Tags removed: verification-needed-bionic ** Tags added: verification-done-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/1828868 Title: crashdump fails on HiSilicon D06 Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Committed Status in linux source package in Disco: Fix Committed Bug description: [Impact] The crashdump kernel fails to boot on HiSilicon D06, and likely other SMMUv3 ARM systems. [Test Case] sudo apt install linux-crashdump Adjust crashkernel= parameter in /etc/default/grub.d/kdump-tools.cfg as appropriate (for D06, crashkernel=512M) Add "arm_smmu_v3.disable_bypass=1" to the kernel command line sudo reboot (needed to add crashkernel= param) echo 1 | sudo tee /proc/sys/kernel/sysrq echo c | sudo tee /proc/sysrq-trigger (Note to self - the following is needed on our systems w/ Mellanox adapters: ubuntu@d06-3:~$ grep blacklist /etc/default/kdump-tools KDUMP_CMDLINE_APPEND="nr_cpus=1 systemd.unit=kdump-tools-dump.service module_blacklist=mlx5_core") [Fix] 3f54c447df34f iommu/arm-smmu-v3: Don't disable SMMU in kdump kernel [Regression Risk] Restricted to SMMUv3 arm64-based systems. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1828868/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835700] Re: linux: 5.2.0-8.9 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Incomplete => Fix Released ** Changed in: kernel-sru-workflow/promote-to-release Status: New => Confirmed ** Tags removed: block-proposed-eoan ** Tags removed: block-proposed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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 - phase: Testing - phase-changed: Tuesday, 09. July 2019 22:34 UTC + phase: Ready for Release + phase-changed: Monday, 15. July 2019 22:07 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Stalled -- testing FAILED + promote-to-release: Pending -- ready to copy variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1835700 Title: linux: 5.2.0-8.9 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released 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-release series: Confirmed Status in Kernel SRU Workflow regression-testing series: Fix Released Status in linux package in Ubuntu: New Status in linux source package in Eoan: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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 phase: Ready for Release phase-changed: Monday, 15. July 2019 22:07 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-release: Pending -- ready to copy variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1835700/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834085] Re: Bluetooth touchpad (Apple Magic Trackpad) disconnects every few minutes
THIS IS NOT A BUG. This is in TLP's FAQ : https://linrunner.de/en/tlp/docs/tlp-faq.html#btusb Please read the documentation, do what it says, confirm that your problem is fixed, and close the bug as invalid. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1834085 Title: Bluetooth touchpad (Apple Magic Trackpad) disconnects every few minutes Status in linux package in Ubuntu: Incomplete Status in tlp package in Ubuntu: Incomplete Bug description: I recently got an Apple's Magic Trackpad. I paired it with Ubuntu 18.04.2 LTS and worked out of the box, no special drivers needed. However, I experience frequent disconnections that last a few seconds (5-15 seconds usually), which are quite annoying, as the cursor stops responding during that interval. The trackpad connects by itself after that period. That usually happens every 20-40 minutes. I use the onboard bluetooth device of my laptop. I also have, at the same time, two more bluetooth devices (keyboard and mouse) and they do not experience that issue, just the trackpad. On ocassion I use bluetooth headphones which work just fine. First of all: Using the command "bluetoothctl" I get the following every time I experience a disconnection: [CHG] Device F4:1B:A1:33:F9:8D Connected: no [CHG] Device F4:1B:A1:33:F9:8D Connected: yes Checking "dmesg" I can see more information: (if I am not mistaken, this shows 4 disconnections) [ 1609.070538] magicmouse 0005:05AC:030E.0007: unknown main item tag 0x0 [ 1609.070797] input: Apple Wireless Trackpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0007/input/input23 [ 1609.071460] magicmouse 0005:05AC:030E.0007: input,hidraw1: BLUETOOTH HID v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98 [ 1676.917377] NET: Registered protocol family 38 [ 1872.815348] magicmouse 0005:05AC:030E.0008: unknown main item tag 0x0 [ 1872.815559] input: Apple Wireless Trackpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0008/input/input24 [ 1872.816248] magicmouse 0005:05AC:030E.0008: input,hidraw1: BLUETOOTH HID v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98 [ 3101.682671] magicmouse 0005:05AC:030E.0009: unknown main item tag 0x0 [ 3101.683100] input: Apple Wireless Trackpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0009/input/input25 [ 3101.683673] magicmouse 0005:05AC:030E.0009: input,hidraw1: BLUETOOTH HID v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98 [ 3110.683360] magicmouse 0005:05AC:030E.000A: unknown main item tag 0x0 [ 3110.683929] input: Apple Wireless Trackpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:1024/0005:05AC:030E.000A/input/input26 [ 3110.684487] magicmouse 0005:05AC:030E.000A: input,hidraw1: BLUETOOTH HID v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98 And this is what journalctl -b shows at the moment of the disconnection/reconnection: de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) config/udev: removing device Apple Wireless Trackpad de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (**) Option "fd" "64" (1,63 m)˜ de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) event16 - Apple Wireless Trackpad: device removed de juny 13 21:37:49 TM1703 gnome-shell[5071]: g_array_unref: assertion 'array' failed de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) UnloadModule: "libinput" de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) systemd-logind: releasing fd for 13:80 de juny 13 21:37:49 TM1703 upowerd[1271]: unhandled action 'unbind' on /sys/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0008 de juny 13 21:37:50 TM1703 kernel: magicmouse 0005:05AC:030E.0009: unknown main item tag 0x0 de juny 13 21:37:50 TM1703 kernel: input: Apple Wireless Trackpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0009/input/input25 de juny 13 21:37:50 TM1703 kernel: magicmouse 0005:05AC:030E.0009: input,hidraw1: BLUETOOTH HID v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98 de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) config/udev: Adding input device Apple Wireless Trackpad (/dev/input/mouse1) de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) No input driver specified, ignoring this device. de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) This device may have been added with another device file. de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) config/udev: Adding input device Apple Wireless Trackpad (/dev/input/event16) de juny 13 21:37:5
[Kernel-packages] [Bug 1836654] [NEW] Bionic update: upstream stable patchset 2019-07-15
Public bug reported: 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 following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2019-07-15 Ported from the following upstream stable releases: v4.14.78, v4.18.16, v4.14.79, v4.18.17, v4.14.80, v4.18.18 from git://git.kernel.org/ media: af9035: prevent buffer overflow on write batman-adv: Avoid probe ELP information leak batman-adv: Fix segfault when writing to throughput_override batman-adv: Fix segfault when writing to sysfs elp_interval batman-adv: Prevent duplicated gateway_node entry batman-adv: Prevent duplicated nc_node entry batman-adv: Prevent duplicated softif_vlan entry batman-adv: Prevent duplicated global TT entry batman-adv: Prevent duplicated tvlv handler batman-adv: fix backbone_gw refcount on queue_work() failure batman-adv: fix hardif_neigh refcount on queue_work() failure clocksource/drivers/ti-32k: Add CLOCK_SOURCE_SUSPEND_NONSTOP flag for non-am43 SoCs scsi: ibmvscsis: Fix a stringop-overflow warning scsi: ibmvscsis: Ensure partition name is properly NUL terminated intel_th: pci: Add Ice Lake PCH support Input: atakbd - fix Atari keymap Input: atakbd - fix Atari CapsLock behaviour net: emac: fix fixed-link setup for the RTL8363SB switch ravb: do not write 1 to reserved bits PCI: dwc: Fix scheduling while atomic issues drm: mali-dp: Call drm_crtc_vblank_reset on device init scsi: ipr: System hung while dlpar adding primary ipr adapter back scsi: sd: don't crash the host on invalid commands net/mlx4: Use cpumask_available for eq->affinity_mask clocksource/drivers/fttmr010: Fix set_next_event handler powerpc/tm: Fix userspace r13 corruption powerpc/tm: Avoid possible userspace r1 corruption on reclaim iommu/amd: Return devid as alias for ACPI HID devices ARC: build: Get rid of toolchain check ARC: build: Don't set CROSS_COMPILE in arch's Makefile HID: quirks: fix support for Apple Magic Keyboards staging: ccree: check DMA pool buf !NULL before free net/smc: fix sizeof to int comparison qed: Fix populating the invalid stag value in multi function mode. RDMA/uverbs: Fix validity check for modify QP bpf: test_maps, only support ESTABLISHED socks RDMA/bnxt_re: Fix system crash during RDMA resource initialization RISC-V: include linux/ftrace.h in asm-prototypes.h powerpc/numa: Use associativity if VPHN hcall is successful x86/boot: Fix kexec booting failure in the SEV bit detection code xfrm: Validate address prefix lengths in the xfrm selector. xfrm6: call kfree_skb when skb is toobig xfrm: reset transport header back to network header after all input transforms ahave been applied xfrm: reset crypto_done when iterating over multiple input xfrms mac80211: Always report TX status cfg80211: reg: Init wiphy_idx in regulatory_hint_core() mac80211: fix pending queue hang due to TX_DROP cfg80211: Address some corner cases in scan result channel updating mac80211: TDLS: fix skb queue/priority assignment mac80211: fix TX status reporting for ieee80211s ARM: 8799/1: mm: fix pci_ioremap_io() offset check xfrm: validate template mode netfilter: bridge: Don't sabotage nf_hook calls from an l3mdev arm64: hugetlb: Fix handling of young ptes ARM: dts: BCM63xx: Fix incorrect interrupt specifiers net: macb: Clean 64b dma addresses if they are not detected soc: fsl: qbman: qman: avoid allocating from non existing gen_pool soc: fsl: qe: Fix copy/paste bug in ucc_get_tdm_sync_shift() mac80211_hwsim: do not omit multicast announce of first added radio Bluetooth: SMP: fix crash in unpairing pxa168fb: prepare the clock qed: Avoid implicit enum conversion in qed_set_tunn_cls_info qed: Fix mask parameter in qed_vf_prep_tunn_req_tlv qed: Avoid implicit enum conversion in qed_roce_mode_to_flavor qed: Avoid constant logical operation warning in qed_vf_pf_acquire qed: Avoid implicit enum conversion in qed_iwarp_parse_rx_pkt asix: Check for supported Wake-on-LAN modes ax88179_178a: Check for supported Wake-on-LAN modes lan78xx: Check for supported Wake-on-LAN modes sr9800: Check for supported Wake-on-LAN modes r8152: Check for supported Wake-on-LAN Modes smsc75xx: Check for Wake-on-LAN modes smsc95xx: Check for Wake-on-LAN modes cfg80211: fix use-after-free in reg_process_hint() perf/core: Fix perf_pmu_unregister() locking perf/ring_buffer: Prevent concurent ring buffer access perf/x86/intel/uncore: Fix PCI BDF address of M3UPI on SKX perf/x86/amd/uncore: Set ThreadMask and SliceMask for L3 Cache perf events net: fec: fix rare tx timeout declance: Fix continuation with the adapter identification message locking/ww_mutex: Fix runtime warning in the WW mutex
