[Kernel-packages] [Bug 1771252] Re: [ICL] Enable intel_rapl driver for Icelake
** Description changed: Desription: This feature is intended to track intel_rapl driver enabling for IceLake. Commit:Powercap/intel_rapl driver enabling for Icelake Target Release: 19.10 Target Kernel: 5.1 + + SRU Justification + [Impact] + New CPU is required to be listed in Intel RAPL (Running Average Power Limit) driver. + + [Fix] + From Intel's suggestion, below 2 commits are required +ba6f3ec198d5 powercap/intel_rapl: add Ice Lake mobile +df7f8e00a50f powercap: intel_rapl: add support for Jacobsville + + [Test] + Boot up Intel ICL-Y SDP with the patched kernel, nothing abnormal, but I'm unable to distinguish the difference. + + [Regression Potential] + Low, the 2 commits add new ID to the table, should affect new CPU only. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1771252 Title: [ICL] Enable intel_rapl driver for Icelake Status in intel: Fix Committed Status in linux package in Ubuntu: Incomplete Status in linux-oem-osp1 package in Ubuntu: In Progress Status in linux-oem-osp1 source package in Bionic: New Bug description: Desription: This feature is intended to track intel_rapl driver enabling for IceLake. Commit:Powercap/intel_rapl driver enabling for Icelake Target Release: 19.10 Target Kernel: 5.1 SRU Justification [Impact] New CPU is required to be listed in Intel RAPL (Running Average Power Limit) driver. [Fix] From Intel's suggestion, below 2 commits are required ba6f3ec198d5 powercap/intel_rapl: add Ice Lake mobile df7f8e00a50f powercap: intel_rapl: add support for Jacobsville [Test] Boot up Intel ICL-Y SDP with the patched kernel, nothing abnormal, but I'm unable to distinguish the difference. [Regression Potential] Low, the 2 commits add new ID to the table, should affect new CPU only. To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1771252/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1771252] 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 1771252 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/1771252 Title: [ICL] Enable intel_rapl driver for Icelake Status in intel: Fix Committed Status in linux package in Ubuntu: Incomplete Status in linux-oem-osp1 package in Ubuntu: In Progress Status in linux-oem-osp1 source package in Bionic: New Bug description: Desription: This feature is intended to track intel_rapl driver enabling for IceLake. Commit:Powercap/intel_rapl driver enabling for Icelake Target Release: 19.10 Target Kernel: 5.1 SRU Justification [Impact] New CPU is required to be listed in Intel RAPL (Running Average Power Limit) driver. [Fix] From Intel's suggestion, below 2 commits are required ba6f3ec198d5 powercap/intel_rapl: add Ice Lake mobile df7f8e00a50f powercap: intel_rapl: add support for Jacobsville [Test] Boot up Intel ICL-Y SDP with the patched kernel, nothing abnormal, but I'm unable to distinguish the difference. [Regression Potential] Low, the 2 commits add new ID to the table, should affect new CPU only. To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1771252/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1771252] Re: [ICL] Enable intel_rapl driver for Icelake
** Changed in: linux-oem-osp1 (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux-oem-osp1 (Ubuntu) Status: In Progress => New ** Changed in: linux-oem-osp1 (Ubuntu Bionic) Assignee: (unassigned) => AceLan Kao (acelankao) ** Changed in: linux-oem-osp1 (Ubuntu) Assignee: AceLan Kao (acelankao) => (unassigned) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1771252 Title: [ICL] Enable intel_rapl driver for Icelake Status in intel: Fix Committed Status in linux package in Ubuntu: Incomplete Status in linux-oem-osp1 package in Ubuntu: New Status in linux-oem-osp1 source package in Bionic: In Progress Bug description: Desription: This feature is intended to track intel_rapl driver enabling for IceLake. Commit:Powercap/intel_rapl driver enabling for Icelake Target Release: 19.10 Target Kernel: 5.1 SRU Justification [Impact] New CPU is required to be listed in Intel RAPL (Running Average Power Limit) driver. [Fix] From Intel's suggestion, below 2 commits are required ba6f3ec198d5 powercap/intel_rapl: add Ice Lake mobile df7f8e00a50f powercap: intel_rapl: add support for Jacobsville [Test] Boot up Intel ICL-Y SDP with the patched kernel, nothing abnormal, but I'm unable to distinguish the difference. [Regression Potential] Low, the 2 commits add new ID to the table, should affect new CPU only. To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1771252/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1809224] Re: To support Intel Wireless-AX 22000 series
** Also affects: linux-oem-osp1 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-oem-osp1 (Ubuntu Bionic) Status: New => Fix Committed ** Changed in: linux-oem-osp1 (Ubuntu Bionic) Assignee: (unassigned) => AceLan Kao (acelankao) ** No longer affects: linux (Ubuntu Bionic) ** Changed in: linux (Ubuntu) Assignee: AceLan Kao (acelankao) => (unassigned) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1809224 Title: To support Intel Wireless-AX 22000 series Status in linux package in Ubuntu: In Progress Status in linux-oem-osp1 package in Ubuntu: New Status in linux-oem-osp1 source package in Bionic: Fix Committed Bug description: [Impact] New Intel Cyclone Peak Wifi doesn't work without newly added driver. [Fix] Cherry pick iwlwifi commits from v5.0 to v5.1, and confirmed with proper firmware the wifi works. [Test] Verified on AX200NGW & 22560NGW chips & Killer 1653 card, wifi works well. [Regression Potential] Medium, it affects the whole iwlwifi driver, but I've verified it with fwst S3 test, and the wifi is still working after S3 test 30 times. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1809224/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1813118] Re: alignment test in powerpc from ubuntu_kernel_selftests failed on B/C Power9
** Changed in: linux (Ubuntu Bionic) Status: New => In Progress ** Changed in: ubuntu-kernel-tests Status: New => In Progress ** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1813118 Title: alignment test in powerpc from ubuntu_kernel_selftests failed on B/C Power9 Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: In Progress Bug description: This issue was only spotted on Power9 system "balter", for Power8 system, it has passed with this test: TAP version 13 selftests: copy_unaligned test: test_copy_unaligned tags: git_version:unknown !! child died by signal 4 failure: test_copy_unaligned not ok 1..1 selftests: copy_unaligned [FAIL] selftests: copy_first_unaligned test: test_copy_first_unaligned tags: git_version:unknown success: test_copy_first_unaligned ok 1..2 selftests: copy_first_unaligned [PASS] selftests: paste_unaligned test: test_paste_unaligned tags: git_version:unknown !! child died by signal 4 failure: test_paste_unaligned not ok 1..3 selftests: paste_unaligned [FAIL] selftests: paste_last_unaligned test: test_paste_last_unaligned tags: git_version:unknown !! child died by signal 4 failure: test_paste_last_unaligned not ok 1..4 selftests: paste_last_unaligned [FAIL] ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-43-generic 4.15.0-43.46 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic ppc64le AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 24 06:50 seq crw-rw 1 root audio 116, 33 Jan 24 06:50 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.5 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 Jan 24 07:05:20 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: 1.24 0.89 0.66 3/1412 8319 ProcLocks: 1: POSIX ADVISORY WRITE 3876 00:17:569 0 EOF 2: FLOCK ADVISORY WRITE 3556 00:17:497 0 EOF 3: FLOCK ADVISORY WRITE 4090 00:17:596 0 EOF 4: POSIX ADVISORY WRITE 3955 00:17:571 0 EOF 5: POSIX ADVISORY WRITE 1823 00:17:348 0 EOF ProcSwaps: Filename TypeSizeUsedPriority /swap.img file 8388544 0 -2 ProcVersion: Linux version 4.15.0-43-generic (buildd@bos02-ppc64el-020) (gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #46-Ubuntu SMP Thu Dec 6 14:43:28 UTC 2018 RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.173.3 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 = 40 cpu_dscr: DSCR is 3 cpu_freq: min: 2.862 GHz (cpu 159) max: 2.863 GHz (cpu 1) avg: 2.862 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/1813118/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828632] Re: bionic i386 kernel crashes in memory pressure situations
Thanks Steve, but I'm still not able to reproduce the kernel crash. If I start netbeans, the current session is killed and I'm thrown back to the login screen. If I do this multiple times the VM eventually simply dies. But no kernel crash. kernel: 4.15.0-49-generic netbeans: 10.0-3~18.04.1ubuntu1 openjdk-11-jre: 11.0.3+7-1ubuntu2~18.04.1 qemu-system-x86_64: /build/qemu-VBsewI/qemu-3.1+dfsg/hw/display/qxl.c:1230: qxl_check_state: Assertion `!spice_display_running || SPICE_RING_IS_EMPTY(&ram->cmd_ring)' failed. 2019-05-14 07:32:36.996+: shutting down, reason=crashed I'm on a Disco host, are you running on 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/1828632 Title: bionic i386 kernel crashes in memory pressure situations Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: New Bug description: The linux-image-4.15.0-49-generic (currently in bionic-proposed) can be made to crash in a kvm guest with memory pressure. The reproducer used is to attempt to run netbeans with openjdk-8-jre installed as the only jvm. It will fail to run, and when it fails, it also causes gnome-shell to crash. After 3 to 5 repeats of this, the kernel will crash with the following oops in dmesg: [ 545.926175] rfkill: input handler enabled [ 546.117550] [ cut here ] [ 546.117552] kernel BUG at /build/linux-S9wgEU/linux-4.15.0/arch/x86/mm/fault.c:268! [ 546.117564] invalid opcode: [#1] SMP PTI [ 546.117565] Modules linked in: snd_hda_codec_generic snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep snd_pcm kvm_intel kvm snd_seq_midi snd_seq_midi_e vent snd_rawmidi irqbypass snd_seq snd_seq_device input_leds joydev snd_timer serio_raw snd soundcore qemu_fw_cfg mac_hid binfmt_misc sch_fq_codel ib_iser r dma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi parport_pc ppdev lp parport ip_tables x_tables autofs4 btrfs zstd_compress r aid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear hid_generic usbhid hid crc32_pc lmul pcbc qxl ttm drm_kms_helper syscopyarea aesni_intel aes_i586 sysfillrect sysimgblt crypto_simd cryptd fb_sys_fops psmouse virtio_blk virtio_net floppy drm pata_acpi i2c_piix4 [ 546.117600] CPU: 0 PID: 1335 Comm: Xorg Not tainted 4.15.0-49-generic #53-Ubuntu [ 546.117600] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.10.2-1ubuntu1 04/01/2014 [ 546.117618] EIP: vmalloc_fault+0x229/0x240 [ 546.117618] EFLAGS: 00010086 CPU: 0 [ 546.117619] EAX: 026c EBX: c3e20c50 ECX: f8eb EDX: [ 546.117620] ESI: f140 EDI: f800 EBP: eddc1934 ESP: eddc1918 [ 546.117621] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 [ 546.117621] CR0: 80050033 CR2: f140 CR3: 25f16000 CR4: 001406f0 [ 546.117624] Call Trace: [ 546.117637] ? kvm_async_pf_task_wait+0x1b0/0x1b0 [ 546.117638] __do_page_fault+0x39d/0x510 [ 546.117640] ? kvm_async_pf_task_wait+0x1b0/0x1b0 [ 546.117641] do_page_fault+0x27/0xf0 [ 546.117644] ? kvm_async_pf_task_wait+0x1b0/0x1b0 [ 546.117645] do_async_page_fault+0x55/0x90 [ 546.117655] common_exception+0x130/0x136 [ 546.117659] EIP: qxl_image_init+0x338/0x390 [qxl] [ 546.117659] EFLAGS: 00010286 CPU: 0 [ 546.117660] EAX: fffbb000 EBX: 0fec ECX: fffbb014 EDX: 0030 [ 546.117661] ESI: f140 EDI: fffbb018 EBP: eddc1a18 ESP: eddc19e4 [ 546.117661] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 [ 546.117663] ? ioremap_nocache+0x12/0x20 [ 546.117665] qxl_draw_dirty_fb+0x1cd/0x3d0 [qxl] [ 546.117668] qxl_primary_atomic_update+0x159/0x2c0 [qxl] [ 546.117680] drm_atomic_helper_commit_planes+0xe8/0x240 [drm_kms_helper] [ 546.117684] drm_atomic_helper_commit_tail+0x23/0x50 [drm_kms_helper] [ 546.117688] commit_tail+0x5d/0x60 [drm_kms_helper] [ 546.117691] drm_atomic_helper_commit+0xf7/0x100 [drm_kms_helper] [ 546.117695] ? drm_atomic_helper_setup_commit+0x3f0/0x3f0 [drm_kms_helper] [ 546.117715] drm_atomic_commit+0x3f/0x50 [drm] [ 546.117719] restore_fbdev_mode_atomic+0x16b/0x1c0 [drm_kms_helper] [ 546.117723] restore_fbdev_mode+0x2c/0x150 [drm_kms_helper] [ 546.117725] ? _cond_resched+0x17/0x40 [ 546.117729] drm_fb_helper_restore_fbdev_mode_unlocked.part.32+0x21/0x70 [drm_kms_helper] [ 546.117732] drm_fb_helper_set_par+0x45/0x80 [drm_kms_helper] [ 546.117743] fb_set_var+0x1a9/0x440 [ 546.117750] ? wakeup_preempt_entity+0x73/0x80 [ 546.117752] ? check_preempt_wakeup+0x108/0x230 [ 546.117753] ? check_cfs_rq_runtime+0x70/0x70 [ 546.117755] ? check_preempt_curr+0x27/0x80 [ 546.117757] ? ttwu_do_wakeup+0x17/0x190 [ 546.117760] fbcon_blank+0x29e/0x370 [ 546.117772] ? __switch_to_asm+0x27/0x4c [ 546.117774]
[Kernel-packages] [Bug 1819413] Re: [ICL] S0ix Enabling
** Changed in: linux (Ubuntu) Assignee: AceLan Kao (acelankao) => (unassigned) ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux-oem-osp1 (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux-oem-osp1 (Ubuntu Bionic) Assignee: (unassigned) => AceLan Kao (acelankao) ** Changed in: linux-oem-osp1 (Ubuntu Bionic) Status: New => In Progress ** No longer affects: linux (Ubuntu Bionic) ** Changed in: linux-oem-osp1 (Ubuntu) Status: In Progress => New ** Changed in: linux-oem-osp1 (Ubuntu) Assignee: AceLan Kao (acelankao) => (unassigned) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1819413 Title: [ICL] S0ix Enabling Status in intel: Fix Committed Status in linux package in Ubuntu: Triaged Status in linux-oem-osp1 package in Ubuntu: New Status in linux-oem-osp1 source package in Bionic: In Progress Bug description: Description: S0ix-states represent the residency in the Intel® SoC idle standby power states. The S0ix states shut off part of the SoC when they are not in use. The S0ix states are triggered when specific conditions within the SoC have been achieved, for example: certain components are in low power states. The SoC consumes the least amount of power in the deepest (for example, S0i3) state. S0ix is triggered by two paths: (1) by system PM, e.g "suspend-to-idle" triggered by pressing the power button on Android device or command manually triggered on any Linux based distros; (2) by runtime PM, i.e no system activities with display off. S0ix should simply work in theory with trigger path (1) if we have the device drivers ready. On GLK, we require the below PCI device drivers with system PM support. ACPI device requirements are WIP. I2C designware PCI driver USB XHCI PCI ID Intel trace Hub[NPK) PCI ID SPI BXT PCI ID SCSI UFS BXT PCI host ID Graphics Audio PWM HSUART Security engine S0ix with trigger path (2) require work as defined below. All the above device drivers need to support runtime PM (already defined in the same LCK above) PCI root port to support runtime PM Both paths will require intel_idle driver support for S0ix support. 238f9c11351f8af8534ae0318b4d9acc77b09ee8 8aba056a4ea6da18186025a335a96b2f071e69d3 6769fdbe27d782dfee5e459e25b44baacc7c8459 cfb55af9add9c19806300fdb31f4cd25e67c6d1a 4a5861f714293767980e4948c9a7c9e5e09c9b94 2a13096ac7da07a1bfc9d91fc4a982020e7ded2b cd89e92b7399a69512b8d855a2dd145c47399bf8 d6827015e671cd17871c9b7a0fabe06c044f7470 0e68eeea9894feeba2edf7ec63e4551b87f39621 e50af8332785355de3cb40d9f5e8c45dbfc86f53 Target Kernel: 5.1 Target Release: 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1819413/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1771252] Re: [ICL] Enable intel_rapl driver for Icelake
** Changed in: linux (Ubuntu) Status: Incomplete => New ** Changed in: linux-oem-osp1 (Ubuntu Bionic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1771252 Title: [ICL] Enable intel_rapl driver for Icelake Status in intel: Fix Committed Status in linux package in Ubuntu: Incomplete Status in linux-oem-osp1 package in Ubuntu: New Status in linux-oem-osp1 source package in Bionic: Fix Committed Bug description: Desription: This feature is intended to track intel_rapl driver enabling for IceLake. Commit:Powercap/intel_rapl driver enabling for Icelake Target Release: 19.10 Target Kernel: 5.1 SRU Justification [Impact] New CPU is required to be listed in Intel RAPL (Running Average Power Limit) driver. [Fix] From Intel's suggestion, below 2 commits are required ba6f3ec198d5 powercap/intel_rapl: add Ice Lake mobile df7f8e00a50f powercap: intel_rapl: add support for Jacobsville [Test] Boot up Intel ICL-Y SDP with the patched kernel, nothing abnormal, but I'm unable to distinguish the difference. [Regression Potential] Low, the 2 commits add new ID to the table, should affect new CPU only. To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1771252/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828394] Comment bridged from LTC Bugzilla
--- Comment From heinz-werner_se...@de.ibm.com 2019-05-14 03:26 EDT--- Canonical: Can someone provide the info where to download the test-kernel for our testing.. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1828394 Title: [UBUNTU] qdio: clear intparm during shutdown Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Bug description: SRU Justification: [Impact] * Crash in qeth_irq() with "Unable to handle kernel pointer dereference in virtual kernel address space" [Fix] * 89286320a236d245834075fa13adb0bdd827ecaa 8928632 "s390/qdio: clear intparm during shutdown" [Test Case] * Offline an OSA CHPID with multiple active qeth interfaces. [Regression Potential] * The regression potential can be considered as very low since it only affects the s390x platform * and there it only affects the (ccW) qeth (OSA) network devices * and again this happens if the CHPID is offlined, which usually doesn't happen during regular operation. [Other Info] * The patch was upstream accepted with kernel 4.17, hence it's already part of cosmic, disco and eoan and proven there to work. * It needs to be applied to kernel 4.15 to land in 18.04 GA and 16.04.5 HWE. _ Description: qdio: clear intparm during shutdown Symptom: Crash in qeth_irq() with "Unable to handle kernel pointer dereference in virtual kernel address space". Problem: During shutdown, qdio returns its ccw device back to control by qeth - but doesn't reset the interrupt parameter on the device. If qdio_shutdown() failed to terminate its long-running IO on the ccw_device, qeth will subsequently do so. In this case the IRQ for the IO completion is presented to qeth_irq() with the _old_ interrupt parameter, which gets mis-interpreted as a valid qeth_cmd_buffer pointer. Dereferencing this bogus pointer in qeth_release_buffer() triggers the crash. Solution: When returning the ccw device in qdio_shutdown(), also reset its interrupt parameter. Reproduction: Offline an OSA CHPID with multiple active qeth interfaces. Component: Kernel Upstream-ID: 89286320a236d245834075fa13adb0bdd827ecaa Reported: Ubuntu 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1828394/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1771252] 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 1771252 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/1771252 Title: [ICL] Enable intel_rapl driver for Icelake Status in intel: Fix Committed Status in linux package in Ubuntu: Incomplete Status in linux-oem-osp1 package in Ubuntu: New Status in linux-oem-osp1 source package in Bionic: Fix Committed Bug description: Desription: This feature is intended to track intel_rapl driver enabling for IceLake. Commit:Powercap/intel_rapl driver enabling for Icelake Target Release: 19.10 Target Kernel: 5.1 SRU Justification [Impact] New CPU is required to be listed in Intel RAPL (Running Average Power Limit) driver. [Fix] From Intel's suggestion, below 2 commits are required ba6f3ec198d5 powercap/intel_rapl: add Ice Lake mobile df7f8e00a50f powercap: intel_rapl: add support for Jacobsville [Test] Boot up Intel ICL-Y SDP with the patched kernel, nothing abnormal, but I'm unable to distinguish the difference. [Regression Potential] Low, the 2 commits add new ID to the table, should affect new CPU only. To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1771252/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828298] Re: Kernel Oops - unable to handle kernel paging request at ffffc90000d6e808; IP [] iwl_trans_pcie_read32+0x12/0x20 [iwlwifi]
Fix is here: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=1c6bca6d75bca2cc47b5eafb9f7f16e368ffbeca -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1828298 Title: Kernel Oops - unable to handle kernel paging request at c9d6e808; IP [] iwl_trans_pcie_read32+0x12/0x20 [iwlwifi] Status in linux-signed package in Ubuntu: New Bug description: After using my computer (Dell Inspiron 3576, running Ununtu 16.04.6 LTS) for a while the wi-fi suddenly stops working. The rest of my apps and programs continue to run smoothly. However, when I open "System Settings" and then try to open "Network", the computer hangs and in order to get it working again I have to reboot it. The reboot takes forever; meanwhle, I get a black screen with this message: [75873.475364] BUG: unable to handle kernel paging request at c9d6e808 [] IP [] iwl_trans_pcie_read32+0x12/0x20 [iwlwifi] PGD 2569aa067 PUD 2569ab067 PMD 255a96067 PTE 0 Oops: [#1] SMP Full error readout in the attached photos. Btw, there seems to be a very similar issue for this model Dell laptops: https://www.dell.com/community/Linux-General/Wi-Fi-WiFi-not- found-after-suspend-sleep/td-p/7186711 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-146-generic 4.4.0-146.172 ProcVersionSignature: Ubuntu 4.4.0-146.172-generic 4.4.177 Uname: Linux 4.4.0-146-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: Unity Date: Wed May 8 21:56:07 2019 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 EcryptfsInUse: Yes InstallationDate: Installed on 2018-12-13 (146 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1828298/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1783906] Re: Linux 4.15 and onwards fails to initialize some hard drives
I forgot to say that even on Linux 4.14 I have to execute manually
script while booting:
echo "- - -" > /sys/class/scsi_host/host1/scan
So, only after this reset sata my laptop can see external HDD. Since
Linux 4.15 resetting has no effect.
I am analyzing how libata setup is working, so I will try to fix this
issue later.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1783906
Title:
Linux 4.15 and onwards fails to initialize some hard drives
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Bionic:
Confirmed
Status in linux source package in Cosmic:
Confirmed
Bug description:
I have two hard drives, the main hard drive is a TOSHIBA DT01ACA200
the second backup hard drive is a Western Digital WD5003AZEX. I
installed lubuntu 18.04.1 on the Toshiba HDD and it boots just fine,
the issue is with the second hard drive, when installing the WD HDD
wouldn't even come as an option to install, and after boot the WD HDD
still wouldn't come up, this is the dmesg with the stock kernel (4.15)
https://paste.ubuntu.com/p/kpxh94v2SK/
ata6 is the WD HDD that refuses to work. The messages:
[ 302.107650] ata6: SError: { CommWake 10B8B Dispar DevExch }
[ 302.107658] ata6: hard resetting link
[ 307.860291] ata6: link is slow to respond, please be patient (ready=0)
[ 312.120898] ata6: COMRESET failed (errno=-16)
[ 363.445120] INFO: task kworker/u8:5:201 blocked for more than 120 seconds.
[ 363.445131] Not tainted 4.15.0-29-generic #31-Ubuntu
[ 363.445135] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables
this message.
[ 363.445140] kworker/u8:5D0 201 2 0x8000
[ 363.445155] Workqueue: events_unbound async_run_entry_fn
[ 363.445157] Call Trace:
[ 363.445171] __schedule+0x291/0x8a0
[ 363.445177] schedule+0x2c/0x80
[ 363.445182] ata_port_wait_eh+0x7c/0xf0
[ 363.445186] ? wait_woken+0x80/0x80
[ 363.445189] ata_port_probe+0x28/0x40
[ 363.445192] async_port_probe+0x2e/0x52
[ 363.445196] async_run_entry_fn+0x3c/0x150
[ 363.445199] process_one_work+0x1de/0x410
[ 363.445203] worker_thread+0x32/0x410
[ 363.445207] kthread+0x121/0x140
[ 363.445210] ? process_one_work+0x410/0x410
[ 363.445214] ? kthread_create_worker_on_cpu+0x70/0x70
[ 363.445218] ret_from_fork+0x22/0x40
Repeat constantly. Also when I try to turn off the computer, the
computer seem to freeze, the lights of the keyboard and mouse turn off
and the computer just stay on.
I tried Tiny Core 9.0 which has linux 4.14.10, and i didn't had this
issue, i also installed linux 4.14 on this lubuntu 18.04 using Ukuu
Kernel Update Utility. And with this kernel version, or any previous
version the WD HDD does work again. Here's a dmesg of lubuntu 18.04
with linux 4.14 and the WD HDD finally coming up at the end:
https://paste.ubuntu.com/p/Gd3cGFbjTJ/
Also tried with with linux 4.17 but the WD HDD would also refuse to
work on this version. Here's another dmesg with this version:
https://paste.ubuntu.com/p/PmNn96vZZv/
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-29-generic 4.15.0-29.31
ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
Uname: Linux 4.15.0-29-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version
k4.15.0-29-generic.
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: testtest756 F pulseaudio
/dev/snd/controlC1: testtest756 F pulseaudio
Card0.Amixer.info:
Card hw:0 'NVidia_1'/'HDA NVidia at 0xfe02 irq 22'
Mixer name : 'Realtek ALC1200'
Components : 'HDA:10ec0888,10ec,00100101
HDA:10de0002,10de0101,0010'
Controls : 56
Simple ctrls : 21
Card1.Amixer.info:
Card hw:1 'NVidia'/'HDA NVidia at 0xfcffc000 irq 16'
Mixer name : 'Nvidia GPU 42 HDMI/DP'
Components : 'HDA:10de0042,38422651,00100100'
Controls : 21
Simple ctrls : 3
CurrentDesktop: LXDE
Date: Thu Jul 26 17:10:58 2018
HibernationDevice: RESUME=UUID=17e70869-516d-4b63-b900-e92e3c4b73b6
InstallationDate: Installed on 2018-07-26 (0 days ago)
InstallationMedia: Lubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64
(20180725)
MachineType: 113 1
ProcFB: 0 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic
root=UUID=71cf0a32-7827-49be-a2c0-cd50a72c26a1 ro quiet splash vt.handoff=1
RelatedPackageVersions:
linux-restricted-modules-4.15.0-29-generic N/A
linux-backports-modules-4.15.0-29-generic N/A
linux-firmware 1.173.1
RfKill:
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 0
[Kernel-packages] [Bug 1826410] Re: Please package libbpf (which is done out of the kernel src) in Debian [for 19.10]
** Also affects: linux (Ubuntu Disco) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Disco) Status: New => 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/1826410 Title: Please package libbpf (which is done out of the kernel src) in Debian [for 19.10] Status in linux package in Ubuntu: Triaged Status in linux source package in Disco: In Progress Bug description: Hi, Debian packages libbpf and so far does so out of the kernel source [1]. There is some movement to separate that from the kernel source [2] but this isn't ready yet. So far it is just a sync of the subtree out of the kernel sources. Since we do not share our kernel packaging we will not get this for-free without doing anything. If there will be an ITP about it in Debian I'll let you know and we can abort this, but unless that really happens I wanted to ask if you could as well build the libbpf* packages for 19.10 and onward? Note: this is not the same bpf lib as [3] despite the similarity in names. Reasoning: BPF becomes more and more important in general and is used in the kernel for many things. In the case that brought it to my attention it will be a PMD of DPDK that will need it to control XDP [4]. And XDP in general is an interesting and rising feature for network acceleration - I'd think it would be helpful to have this package around in Ubuntu. [1]: https://packages.debian.org/sid/libbpf-dev [2]: https://github.com/libbpf/libbpf [3]: https://github.com/iovisor/bcc [4]: https://www.iovisor.org/technology/xdp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1826410/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1762940] Re: Ubuntu 18.04 d-i install screen becomes blurry on Huawei server in EFI boot mode
@Aaron Ma I want to test your patch. But seems it would patch with error. I guess, the new 18.04 source code have been change to: list_add_tail(&vgadev->list, &vga_list); instead of: - list_add(&vgadev->list, &vga_list); + list_add_tail(&vgadev->list, &vga_list); Does it mean this patch have been already merged in our new source. In last month, I testing with 18.04.2 iso (d-i) and this screen blur is still existing. Does it mean this patch did not solve our cases. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1762940 Title: Ubuntu 18.04 d-i install screen becomes blurry on Huawei server in EFI boot mode Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Bug description: For all(as I know) Huawei servers, the vga adapter are embed in the iBMC chips. Those server can install from ISO manually for 16.04.4 and screen display normally. But for 18.04 ( tested both for daily and final beta)version, the install screen is blur. One of tested server is Huawei 2855 v5, the certification link for 16.04 are https://certification.ubuntu.com/hardware/201707-25596/. Below are key difference of dmesg. It seems might related with DRM. 18.04 install screen is blur dmesg ... [2.039009] fb0: EFI VGA frame buffer device ... [4.178058] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [4.191435] [drm] No driver support for vblank timestamp query. [4.209338] checking generic (9000 30) vs hw (0 0) [4.209384] fbcon: hibmcdrmfb (fb1) is primary device [4.209385] fbcon: Remapping primary device, fb1, to tty 1-63 ... [5.357024] hibmc-drm :07:00.0: fb1: hibmcdrmfb frame buffer device [5.380085] [drm] Initialized hibmc 1.0.0 20160828 for :07:00.0 on minor 0 ... [5.636624] vga16fb: initializing [5.636627] vga16fb: mapped to 0x48a7a1d2 [5.636630] checking generic (9000 30) vs hw (a 1) [5.636676] fb2: VGA16 VGA frame buffer device ... 16.04.4 install screen is fine (no screen blur) dmesg ... [2.000419] fb0: EFI VGA frame buffer device [8.795065] vga16fb: initializing [8.795068] vga16fb: mapped to 0x880a [8.795071] checking generic (9800 30) vs hw (a 1) [8.795121] fb1: VGA16 VGA frame buffer device ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762940/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1824690] Re: proc_thermal flooding dmesg
** Changed in: thermald (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1824690 Title: proc_thermal flooding dmesg Status in linux package in Ubuntu: Incomplete Status in thermald package in Ubuntu: Incomplete Bug description: [ 11.520358] proc_thermal :00:00.1: Unsupported event [0x91] [ 16.532358] proc_thermal :00:00.1: Unsupported event [0x91] [ 21.572719] proc_thermal :00:00.1: Unsupported event [0x91] [ 26.580855] proc_thermal :00:00.1: Unsupported event [0x91] [ 31.588851] proc_thermal :00:00.1: Unsupported event [0x91] [ 36.592827] proc_thermal :00:00.1: Unsupported event [0x91] [ 41.572682] random: crng init done [ 41.572690] random: 7 urandom warning(s) missed due to ratelimiting Kernel 4.18.0-18-generic No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.2 LTS Release: 18.04 Codename: bionic --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: juno 1175 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-04-15 (0 days ago) InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0025 Intel Corp. Bus 001 Device 003: ID 04f2:b59e Chicony Electronics Co., Ltd Bus 001 Device 002: ID 1ea7:0064 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Notebook N24_25GU Package: thermald 1.7.0-5ubuntu2 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-18-generic root=UUID=a23ca3ac-6284-45ce-9aa8-6670879910e7 ro quiet splash acpi_osi= acpi_os_name=Linux vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-18.19~18.04.1-generic 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-18-generic N/A linux-backports-modules-4.18.0-18-generic N/A linux-firmware 1.173.5 Tags: bionic Uname: Linux 4.18.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/18/2018 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.06 dmi.board.asset.tag: Tag 12345 dmi.board.name: N24_25GU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.06:bd05/18/2018:svnNotebook:pnN24_25GU:pvrNotApplicable:rvnNotebook:rnN24_25GU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: N24_25GU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824690/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1813118] Re: alignment test in powerpc from ubuntu_kernel_selftests failed on B/C Power9
** Description changed: - This issue was only spotted on Power9 system "balter", for Power8 - system, it has passed with this test: + == Justification == + The copy_unaligned / paste_unaligned / paste_last_unaligned test in powerpc/alignment will fail on a Power9 node as which implements ISA 3.0B, but the test was designed base on ISA 3.0. - TAP version 13 - selftests: copy_unaligned - - test: test_copy_unaligned - tags: git_version:unknown - !! child died by signal 4 - failure: test_copy_unaligned - not ok 1..1 selftests: copy_unaligned [FAIL] - selftests: copy_first_unaligned - - test: test_copy_first_unaligned - tags: git_version:unknown - success: test_copy_first_unaligned - ok 1..2 selftests: copy_first_unaligned [PASS] - selftests: paste_unaligned - - test: test_paste_unaligned - tags: git_version:unknown - !! child died by signal 4 - failure: test_paste_unaligned - not ok 1..3 selftests: paste_unaligned [FAIL] - selftests: paste_last_unaligned - - test: test_paste_last_unaligned - tags: git_version:unknown - !! child died by signal 4 - failure: test_paste_last_unaligned - not ok 1..4 selftests: paste_last_unaligned [FAIL] + From commit message: + This is a test of the ISA 3.0 "copy" instruction. That instruction has + an L field, which if set to 1 specifies that "the instruction + identifies the beginning of a move group" (pp 858). That's also + referred to as "copy first" vs "copy". + + In ISA 3.0B the copy instruction does not have an L field, and the + corresponding bit in the instruction must be set to 1. + + This test is generating a "copy" instruction, not a "copy first", and + so on Power9 (which implements 3.0B), this results in an illegal + instruction. + + So just drop the test entirely. We still have copy_first_unaligned to + test the "copy first" behaviour. + + == Fix == + * 83039f22 (selftests/powerpc: Remove Power9 copy_unaligned test) + + Patch can be cherry-picked into C, for Bionic it needs patches for bug + 1828935 to land first to make it a clean cherry-pick. + + It's already landed in D and onward. + + == Test == + Tested on a Power9 server with Cosmic, the broken tests will be removed correctly. + + == Regression Potential == + Low. + Code change limited to testing tools and just removing broken tests. We still have copy_first_unaligned to test the "copy first" behaviour. + + + == Original Bug Report == + This issue was only spotted on Power9 system "balter", for Power8 system, it has passed (skipped, and marked as passed) with this test: + + TAP version 13 + selftests: copy_unaligned + + test: test_copy_unaligned + tags: git_version:unknown + !! child died by signal 4 + failure: test_copy_unaligned + not ok 1..1 selftests: copy_unaligned [FAIL] + selftests: copy_first_unaligned + + test: test_copy_first_unaligned + tags: git_version:unknown + success: test_copy_first_unaligned + ok 1..2 selftests: copy_first_unaligned [PASS] + selftests: paste_unaligned + + test: test_paste_unaligned + tags: git_version:unknown + !! child died by signal 4 + failure: test_paste_unaligned + not ok 1..3 selftests: paste_unaligned [FAIL] + selftests: paste_last_unaligned + + test: test_paste_last_unaligned + tags: git_version:unknown + !! child died by signal 4 + failure: test_paste_last_unaligned + not ok 1..4 selftests: paste_last_unaligned [FAIL] ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-43-generic 4.15.0-43.46 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic ppc64le AlsaDevices: - total 0 - crw-rw 1 root audio 116, 1 Jan 24 06:50 seq - crw-rw 1 root audio 116, 33 Jan 24 06:50 timer + total 0 + crw-rw 1 root audio 116, 1 Jan 24 06:50 seq + crw-rw 1 root audio 116, 33 Jan 24 06:50 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.5 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 Jan 24 07:05:20 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 + Bus 002 Device 001: ID 1d6b:0003 Linux
[Kernel-packages] [Bug 1827555] Re: [ALSA] [PATCH] Headset fixup for System76 Gazelle (gaze14)
** Changed in: linux (Ubuntu Bionic) Status: Fix Committed => Confirmed ** Changed in: linux (Ubuntu Cosmic) Status: Fix Committed => Confirmed ** Changed in: linux (Ubuntu Disco) Status: Fix Committed => 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/1827555 Title: [ALSA] [PATCH] Headset fixup for System76 Gazelle (gaze14) Status in linux package in Ubuntu: Confirmed Status in linux-hwe package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Status in linux-hwe source package in Bionic: New Status in linux source package in Cosmic: Confirmed Status in linux-hwe source package in Cosmic: Invalid Status in linux source package in Disco: Confirmed Status in linux-hwe source package in Disco: Invalid Bug description: [Impact] * On the System76 Gazelle (gaze14), there is a headset microphone input attached to 0x1a that does not have a jack detect. In order to get it working, the pin configuration needs to be set correctly, and the ALC269_FIXUP_HEADSET_MODE_NO_HP_MIC fixup needs to be applied. This is identical to the patch already applied for the System76 Darter Pro (darp5). [Test Case] * With the affected hardware, attempt to use a headset with a microphone input. There will be no microphone input from the headset until applying this patch. [Regression Potential] * Extremely low, it specifically identifies the affected hardware. [Other Info] * I have attached the patch as it will be applied to upstream Linux. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1827555/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828763] Re: Cannot build kernel 4.15.0-48.51 due to an in-source-tree ZFS module.
Hi Hyeonho, good catch. It looks like b49151d684f44 renamed tx_waited to
tx_dirty_delayed, but only in the tracepoint definition in trace_dmu.h
and not in the rest of the code. I think we should simply restore the
original name.
Can you check if this patch solves the problem? Thanks.
** Patch added: "zfs-fix-build-error-with-tracepoints-enabled.patch"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1828763/+attachment/5263595/+files/zfs-fix-build-error-with-tracepoints-enabled.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/1828763
Title:
Cannot build kernel 4.15.0-48.51 due to an in-source-tree ZFS module.
Status in linux package in Ubuntu:
Confirmed
Bug description:
I tried to build a kernel 4.15.0-48.51 that cloned from the Ubuntu
kernel git (x86_64-generic flavour).
commit c50532b9d7b623ff98aeaf0b848e58adae54ca75 (HEAD -> master, tag:
Ubuntu-4.15.0-48.51, origin/master, origin/HEAD)
Author: Andrea Righi
Date: Tue Apr 2 18:31:55 2019 +0200
UBUNTU: Ubuntu-4.15.0-48.51
Signed-off-by: Andrea Righi
1. Build a kernel image with 'zfs_enable' flag set as false.
2. Build SPL/ZFS modules independently by 'make' command (debug purpose;
DECLARE_EVENT_CLASS() enabled).
But 'make' was always failed at the same point,
'zfs/module/zfs/trace.c' (as seem as below).
In file included from /home/np/linux-4.15/include/trace/define_trace.h:96:0,
from /home/np/linux-4.15/zfs/include/sys/trace_dmu.h:127,
from /home/np/linux-4.15/zfs/module/zfs/trace.c:45:
/home/np/linux-4.15/zfs/include/sys/trace_dmu.h: In function
‘trace_event_raw_event_zfs_delay_mintime_class’:
/home/np/linux-4.15/zfs/include/sys/trace_dmu.h:65:37: error: ‘dmu_tx_t {aka
struct dmu_tx}’ has no member named ‘tx_dirty_delayed’
__entry->tx_dirty_delayed = tx->tx_dirty_delayed;
^
/home/np/linux-4.15/include/trace/trace_events.h:719:4: note: in definition
of macro ‘DECLARE_EVENT_CLASS’
{ assign; } \
^~
/home/np/linux-4.15/zfs/include/sys/trace_dmu.h:60:2: note: in expansion of
macro ‘TP_fast_assign’
TP_fast_assign(
^~
In file included from /home/np/linux-4.15/include/trace/define_trace.h:97:0,
from /home/np/linux-4.15/zfs/include/sys/trace_dmu.h:127,
from /home/np/linux-4.15/zfs/module/zfs/trace.c:45:
/home/np/linux-4.15/zfs/include/sys/trace_dmu.h: In function
‘perf_trace_zfs_delay_mintime_class’:
/home/np/linux-4.15/zfs/include/sys/trace_dmu.h:65:37: error: ‘dmu_tx_t {aka
struct dmu_tx}’ has no member named ‘tx_dirty_delayed’
__entry->tx_dirty_delayed = tx->tx_dirty_delayed;
^
/home/np/linux-4.15/include/trace/perf.h:66:4: note: in definition of macro
‘DECLARE_EVENT_CLASS’
{ assign; } \
^~
/home/np/linux-4.15/zfs/include/sys/trace_dmu.h:60:2: note: in expansion of
macro ‘TP_fast_assign’
TP_fast_assign(
^~
I tried to debug this issue with myself and found something intriguing.
In 'zfs/include/sys/trace_dmu.h', the failed code accessing
'tx_dirty_delayed' from 'dmu_tx_t' (which same as 'struct dmu_tx').
DECLARE_EVENT_CLASS(zfs_delay_mintime_class,
TP_PROTO(dmu_tx_t *tx, uint64_t dirty, uint64_t min_tx_time),
TP_ARGS(tx, dirty, min_tx_time),
TP_STRUCT__entry(
__field(uint64_t, tx_txg)
__field(uint64_t, tx_lastsnap_txg)
__field(uint64_t, tx_lasttried_txg)
__field(boolean_t, tx_anyobj)
__field(boolean_t, tx_dirty_delayed)
__field(hrtime_t, tx_start)
__field(boolean_t, tx_wait_dirty)
__field(int,tx_err)
__field(uint64_t, min_tx_time)
__field(uint64_t, dirty)
),
TP_fast_assign(
__entry->tx_txg = tx->tx_txg;
__entry->tx_lastsnap_txg= tx->tx_lastsnap_txg;
__entry->tx_lasttried_txg = tx->tx_lasttried_txg;
__entry->tx_anyobj = tx->tx_anyobj;
__entry->tx_dirty_delayed = tx->tx_dirty_delayed;
__entry->tx_start = tx->tx_start;
__entry->tx_wait_dirty = tx->tx_wait_dirty;
__entry->tx_err = tx->tx_err;
__entry->dirty = dirty;
__entry->min_tx_time= min_tx_time;
),
TP_printk("tx { txg %llu lastsnap_txg %llu tx_lasttried_txg %llu "
"any
[Kernel-packages] [Bug 1828763] Re: Cannot build kernel 4.15.0-48.51 due to an in-source-tree ZFS module.
** Tags added: patch
** Changed in: linux (Ubuntu)
Importance: Undecided => Low
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Andrea Righi (arighi)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1828763
Title:
Cannot build kernel 4.15.0-48.51 due to an in-source-tree ZFS module.
Status in linux package in Ubuntu:
Confirmed
Bug description:
I tried to build a kernel 4.15.0-48.51 that cloned from the Ubuntu
kernel git (x86_64-generic flavour).
commit c50532b9d7b623ff98aeaf0b848e58adae54ca75 (HEAD -> master, tag:
Ubuntu-4.15.0-48.51, origin/master, origin/HEAD)
Author: Andrea Righi
Date: Tue Apr 2 18:31:55 2019 +0200
UBUNTU: Ubuntu-4.15.0-48.51
Signed-off-by: Andrea Righi
1. Build a kernel image with 'zfs_enable' flag set as false.
2. Build SPL/ZFS modules independently by 'make' command (debug purpose;
DECLARE_EVENT_CLASS() enabled).
But 'make' was always failed at the same point,
'zfs/module/zfs/trace.c' (as seem as below).
In file included from /home/np/linux-4.15/include/trace/define_trace.h:96:0,
from /home/np/linux-4.15/zfs/include/sys/trace_dmu.h:127,
from /home/np/linux-4.15/zfs/module/zfs/trace.c:45:
/home/np/linux-4.15/zfs/include/sys/trace_dmu.h: In function
‘trace_event_raw_event_zfs_delay_mintime_class’:
/home/np/linux-4.15/zfs/include/sys/trace_dmu.h:65:37: error: ‘dmu_tx_t {aka
struct dmu_tx}’ has no member named ‘tx_dirty_delayed’
__entry->tx_dirty_delayed = tx->tx_dirty_delayed;
^
/home/np/linux-4.15/include/trace/trace_events.h:719:4: note: in definition
of macro ‘DECLARE_EVENT_CLASS’
{ assign; } \
^~
/home/np/linux-4.15/zfs/include/sys/trace_dmu.h:60:2: note: in expansion of
macro ‘TP_fast_assign’
TP_fast_assign(
^~
In file included from /home/np/linux-4.15/include/trace/define_trace.h:97:0,
from /home/np/linux-4.15/zfs/include/sys/trace_dmu.h:127,
from /home/np/linux-4.15/zfs/module/zfs/trace.c:45:
/home/np/linux-4.15/zfs/include/sys/trace_dmu.h: In function
‘perf_trace_zfs_delay_mintime_class’:
/home/np/linux-4.15/zfs/include/sys/trace_dmu.h:65:37: error: ‘dmu_tx_t {aka
struct dmu_tx}’ has no member named ‘tx_dirty_delayed’
__entry->tx_dirty_delayed = tx->tx_dirty_delayed;
^
/home/np/linux-4.15/include/trace/perf.h:66:4: note: in definition of macro
‘DECLARE_EVENT_CLASS’
{ assign; } \
^~
/home/np/linux-4.15/zfs/include/sys/trace_dmu.h:60:2: note: in expansion of
macro ‘TP_fast_assign’
TP_fast_assign(
^~
I tried to debug this issue with myself and found something intriguing.
In 'zfs/include/sys/trace_dmu.h', the failed code accessing
'tx_dirty_delayed' from 'dmu_tx_t' (which same as 'struct dmu_tx').
DECLARE_EVENT_CLASS(zfs_delay_mintime_class,
TP_PROTO(dmu_tx_t *tx, uint64_t dirty, uint64_t min_tx_time),
TP_ARGS(tx, dirty, min_tx_time),
TP_STRUCT__entry(
__field(uint64_t, tx_txg)
__field(uint64_t, tx_lastsnap_txg)
__field(uint64_t, tx_lasttried_txg)
__field(boolean_t, tx_anyobj)
__field(boolean_t, tx_dirty_delayed)
__field(hrtime_t, tx_start)
__field(boolean_t, tx_wait_dirty)
__field(int,tx_err)
__field(uint64_t, min_tx_time)
__field(uint64_t, dirty)
),
TP_fast_assign(
__entry->tx_txg = tx->tx_txg;
__entry->tx_lastsnap_txg= tx->tx_lastsnap_txg;
__entry->tx_lasttried_txg = tx->tx_lasttried_txg;
__entry->tx_anyobj = tx->tx_anyobj;
__entry->tx_dirty_delayed = tx->tx_dirty_delayed;
__entry->tx_start = tx->tx_start;
__entry->tx_wait_dirty = tx->tx_wait_dirty;
__entry->tx_err = tx->tx_err;
__entry->dirty = dirty;
__entry->min_tx_time= min_tx_time;
),
TP_printk("tx { txg %llu lastsnap_txg %llu tx_lasttried_txg %llu "
"anyobj %d dirty_delayed %d start %llu wait_dirty %d err %i "
"} dirty %llu min_tx_time %llu",
__entry->tx_txg, __entry->tx_lastsnap_txg,
__entry->tx_lasttried_txg, __entry->tx_anyobj,
__entry->tx_dirty_delayed, __entry->tx_start,
__entry->tx_wait_dirty, __entry->t
[Kernel-packages] [Bug 1813118] Re: alignment test in powerpc from ubuntu_kernel_selftests failed on B/C Power9
** Description changed: == Justification == The copy_unaligned / paste_unaligned / paste_last_unaligned test in powerpc/alignment will fail on a Power9 node as which implements ISA 3.0B, but the test was designed base on ISA 3.0. - From commit message: + From the commit message: This is a test of the ISA 3.0 "copy" instruction. That instruction has an L field, which if set to 1 specifies that "the instruction identifies the beginning of a move group" (pp 858). That's also referred to as "copy first" vs "copy". In ISA 3.0B the copy instruction does not have an L field, and the corresponding bit in the instruction must be set to 1. This test is generating a "copy" instruction, not a "copy first", and so on Power9 (which implements 3.0B), this results in an illegal instruction. So just drop the test entirely. We still have copy_first_unaligned to test the "copy first" behaviour. == Fix == * 83039f22 (selftests/powerpc: Remove Power9 copy_unaligned test) Patch can be cherry-picked into C, for Bionic it needs patches for bug 1828935 to land first to make it a clean cherry-pick. It's already landed in D and onward. == Test == - Tested on a Power9 server with Cosmic, the broken tests will be removed correctly. + Tested on a Power9 server with Cosmic, the broken tests will be removed correctly. == Regression Potential == Low. Code change limited to testing tools and just removing broken tests. We still have copy_first_unaligned to test the "copy first" behaviour. - == Original Bug Report == This issue was only spotted on Power9 system "balter", for Power8 system, it has passed (skipped, and marked as passed) with this test: TAP version 13 selftests: copy_unaligned test: test_copy_unaligned tags: git_version:unknown !! child died by signal 4 failure: test_copy_unaligned not ok 1..1 selftests: copy_unaligned [FAIL] selftests: copy_first_unaligned test: test_copy_first_unaligned tags: git_version:unknown success: test_copy_first_unaligned ok 1..2 selftests: copy_first_unaligned [PASS] selftests: paste_unaligned test: test_paste_unaligned tags: git_version:unknown !! child died by signal 4 failure: test_paste_unaligned not ok 1..3 selftests: paste_unaligned [FAIL] selftests: paste_last_unaligned test: test_paste_last_unaligned tags: git_version:unknown !! child died by signal 4 failure: test_paste_last_unaligned not ok 1..4 selftests: paste_last_unaligned [FAIL] ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-43-generic 4.15.0-43.46 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic ppc64le AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 24 06:50 seq crw-rw 1 root audio 116, 33 Jan 24 06:50 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.5 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 Jan 24 07:05:20 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: 1.24 0.89 0.66 3/1412 8319 ProcLocks: 1: POSIX ADVISORY WRITE 3876 00:17:569 0 EOF 2: FLOCK ADVISORY WRITE 3556 00:17:497 0 EOF 3: FLOCK ADVISORY WRITE 4090 00:17:596 0 EOF 4: POSIX ADVISORY WRITE 3955 00:17:571 0 EOF 5: POSIX ADVISORY WRITE 1823 00:17:348 0 EOF ProcSwaps: Filename TypeSizeUsedPriority /swap.img file 8388544 0 -2 ProcVersion: Linux version 4.15.0-43-generic (buildd@bos02-ppc64el-020) (gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #46-Ubuntu SMP Thu Dec 6 14:43:28 UTC 2018 RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.173.3 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
[Kernel-packages] [Bug 1825626] Re: nvLock: client timed out, taking the lock
Same here with ubuntu 19.04, mentiond driver version and a Quadro M620 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-418 in Ubuntu. https://bugs.launchpad.net/bugs/1825626 Title: nvLock: client timed out, taking the lock Status in nvidia-graphics-drivers-418 package in Ubuntu: Confirmed Bug description: While launching an app or performing an operation, the screen has a certain chance to freeze for a few seconds and then recover. [ System Info ] Version : Ubuntu 19.04 Kernel : x86_64 Linux 5.0.0-13-generic GPU : NVIDIA GeForce GTX 1050 Xorg version : 1:7.7+19ubuntu12 Product Name : Aspire VX5-591G (Acer) [ Log File ] Uploaded as an attachment *Sorry for my not-good English. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] 是一个目录: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 418.56 Fri Mar 15 12:59:26 CDT 2019 GCC version: gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1) ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] 权限不够: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 20 17:19:29 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu DkmsStatus: nvidia, 418.56, 5.0.0-13-generic, x86_64: installed virtualbox, 6.0.6, 4.18.0-17-generic, x86_64: installed virtualbox, 6.0.6, 5.0.0-13-generic, x86_64: installed ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] HD Graphics 630 [1025:1127] Subsystem: Acer Incorporated [ALI] GP107M [GeForce GTX 1050 Mobile] [1025:1128] MachineType: Acer Aspire VX5-591G ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=a0525f6e-8c28-4e08-9c6e-9745ee51c18a ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/07/2017 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.06 dmi.board.asset.tag: Type2 - Board Serial Number dmi.board.name: Wish_KLS dmi.board.vendor: KBL dmi.board.version: V1.06 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.06 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.06:bd07/07/2017:svnAcer:pnAspireVX5-591G:pvrV1.06:rvnKBL:rnWish_KLS:rvrV1.06:cvnAcer:ct10:cvrV1.06: dmi.product.family: Aspire VX 15 dmi.product.name: Aspire VX5-591G dmi.product.sku: dmi.product.version: V1.06 dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-418/+bug/1825626/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828410] Re: Disco update: 5.0.7 upstream stable release
** Changed in: linux (Ubuntu Disco) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Changed in: linux (Ubuntu Disco) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1828410 Title: Disco update: 5.0.7 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.7 upstream stable release from git://git.kernel.org/ The following patches were applied: * ext4: cleanup bh release code in ext4_ind_remove_space() * CIFS: fix POSIX lock leak and invalid ptr deref * nvme-fc: fix numa_node when dev is null * nvme-loop: init nvmet_ctrl fatal_err_work when allocate * h8300: use cc-cross-prefix instead of hardcoding h8300-unknown-linux- * f2fs: fix to adapt small inline xattr space in __find_inline_xattr() * f2fs: fix to avoid deadlock in f2fs_read_inline_dir() * tracing: kdb: Fix ftdump to not sleep * net/mlx5e: Fix access to non-existing receive queue * net/mlx5: Avoid panic when setting vport rate * net/mlx5: Avoid panic when setting vport mac, getting vport config * xsk: fix to reject invalid flags in xsk_bind * clk: ti: clkctrl: Fix clkdm_name regression for TI_CLK_CLKCTRL_COMPAT * gpio: gpio-omap: fix level interrupt idling * include/linux/relay.h: fix percpu annotation in struct rchan * sysctl: handle overflow for file-max * net: stmmac: Avoid sometimes uninitialized Clang warnings * enic: fix build warning without CONFIG_CPUMASK_OFFSTACK * libbpf: force fixdep compilation at the start of the build * iio: adc: fix warning in Qualcomm PM8xxx HK/XOADC driver * x86/hyperv: Fix kernel panic when kexec on HyperV * perf c2c: Fix c2c report for empty numa node * mm/sparse: fix a bad comparison * mm/cma.c: cma_declare_contiguous: correct err handling * mm/page_ext.c: fix an imbalance with kmemleak * mm, swap: bounds check swap_info array accesses to avoid NULL derefs * docs/core-api/mm: fix user memory accessors formatting * mm,oom: don't kill global init via memory.oom.group * memcg: killed threads should not invoke memcg OOM killer * mm, mempolicy: fix uninit memory access * mm/vmalloc.c: fix kernel BUG at mm/vmalloc.c:512! * mm/slab.c: kmemleak no scan alien caches * ocfs2: fix a panic problem caused by o2cb_ctl * f2fs: do not use mutex lock in atomic context * f2fs: fix to data block override node segment by mistake * fs/file.c: initialize init_files.resize_wait * page_poison: play nicely with KASAN * kasan: fix kasan_check_read/write definitions * cifs: use correct format characters * dm thin: add sanity checks to thin-pool and external snapshot creation * f2fs: fix to check inline_xattr_size boundary correctly * cifs: Accept validate negotiate if server return NT_STATUS_NOT_SUPPORTED * cifs: Fix NULL pointer dereference of devname * perf beauty msg_flags: Add missing %s lost when adding prefix suppression logic * netfilter: nf_tables: check the result of dereferencing base_chain->stats * PCI: mediatek: Fix memory mapped IO range size computation * netfilter: conntrack: tcp: only close if RST matches exact sequence * iommu/vt-d: Disable ATS support on untrusted devices * jbd2: fix invalid descriptor block checksum * ext4: fix bigalloc cluster freeing when hole punching under load * fs: fix guard_bio_eod to check for real EOD errors * tools lib traceevent: Fix buffer overflow in arg_eval * mm/resource: Return real error codes from walk failures * PCI/PME: Fix hotplug/sysfs remove deadlock in pcie_pme_remove() * wil6210: check null pointer in _wil_cfg80211_merge_extra_ies * mt76: fix a leaked reference by adding a missing of_node_put * ath10k: Fix the wrong updation of BW in tx_stats debugfs entry * lockdep/lib/tests: Fix run_tests.sh * crypto: crypto4xx - add missing of_node_put after of_device_is_available * crypto: cavium/zip - fix collision with generic cra_driver_name * tools/bpf: selftests: add map lookup to test_map_in_map bpf prog * usb: chipidea: Grab the (legacy) USB PHY by phandle first * powerpc/powernv/ioda: Fix locked_vm counting for memory used by IOMMU tables * scsi: core: replace GFP_ATOMIC with GFP_KERNEL in scsi_scan.c * kbuild: invoke syncconfig if include/config/auto.conf.cmd is missing * kbuild:
[Kernel-packages] [Bug 1828935] Re: Add powerpc/alignment_handler test for selftests
https://lists.ubuntu.com/archives/kernel-team/2019-May/100684.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/1828935 Title: Add powerpc/alignment_handler test for selftests Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: In Progress Bug description: == Justification == There is a powerpc/alignment_handler available in the upstream for PowerPC self-testing tool. Bring this in to cover more bits in the ubuntu_kernel_selftest test suite. == Fix == * 8d191587 (selftests/powerpc: Add alignment handler selftest) * ecdf06e1 (selftests/powerpc: Fix to use ucontext_t instead of struct ucontext) Both of them can be cherry-picked into Bionic kernel. The second patch is essential to fix a build error. It's already available in Cosmic and onward. == Test == Test was successfully built and passed on a Power9 node with Bionic kernel: selftests: alignment_handler test: test_alignment_handler_vsx_206 tags: git_version:Ubuntu-4.15.0-48.51-2-g705784d93589-dirty VSX: 2.06B Doing lxvd2x: PASSED Doing lxvw4x: PASSED Doing lxsdx:PASSED Doing lxvdsx: PASSED Doing stxvd2x: PASSED Doing stxvw4x: PASSED Doing stxsdx: PASSED success: test_alignment_handler_vsx_206 test: test_alignment_handler_vsx_207 tags: git_version:Ubuntu-4.15.0-48.51-2-g705784d93589-dirty VSX: 2.07B Doing lxsspx: PASSED Doing lxsiwax: PASSED Doing lxsiwzx: PASSED Doing stxsspx: PASSED Doing stxsiwx: PASSED success: test_alignment_handler_vsx_207 test: test_alignment_handler_vsx_300 tags: git_version:Ubuntu-4.15.0-48.51-2-g705784d93589-dirty VSX: 3.00B Doing lxsd: PASSED Doing lxsibzx: PASSED Doing lxsihzx: PASSED Doing lxssp:PASSED Doing lxv: PASSED Doing lxvb16x: PASSED Doing lxvh8x: PASSED Doing lxvx: PASSED Doing lxvwsx: PASSED Doing lxvl: PASSED Doing lxvll:PASSED Doing stxsd:PASSED Doing stxsibx: PASSED Doing stxsihx: PASSED Doing stxssp: PASSED Doing stxv: PASSED Doing stxvb16x: PASSED Doing stxvh8x: PASSED Doing stxvx:PASSED Doing stxvl:PASSED Doing stxvll: PASSED success: test_alignment_handler_vsx_300 test: test_alignment_handler_integer tags: git_version:Ubuntu-4.15.0-48.51-2-g705784d93589-dirty Integer Doing lbz: PASSED Doing lbzu: PASSED Doing lbzx: PASSED Doing lbzux:PASSED Doing lhz: PASSED Doing lhzu: PASSED Doing lhzx: PASSED Doing lhzux:PASSED Doing lha: PASSED Doing lhau: PASSED Doing lhax: PASSED Doing lhaux:PASSED Doing lhbrx:PASSED Doing lwz: PASSED Doing lwzu: PASSED Doing lwzx: PASSED Doing lwzux:PASSED Doing lwa: PASSED Doing lwax: PASSED Doing lwaux:PASSED Doing lwbrx:PASSED Doing ld: PASSED Doing ldu: PASSED Doing ldx: PASSED Doing ldux: PASSED Doing ldbrx:PASSED Doing lmw: PASSED Doing stb: PASSED Doing stbx: PASSED Doing stbu: PASSED Doing stbux:PASSED Doing sth: PASSED Doing sthx: PASSED Doing sthu: PASSED Doing sthux:PASSED Doing sthbrx: PASSED Doing stw: PASSED Doing stwx: PASSED Doing stwu: PASSED Doing stwux:PASSED Doing stwbrx: PASSED Doing std: PASSED Doing stdx: PASSED Doing stdu: PASSED Doing stdux:PASSED Doing stdbrx: PASSED Doing stmw: PASSED success: test_alignment_handler_integer test: test_alignment_handler_vmx tags: git_version:Ubuntu-4.15.0-48.51-2-g705784d93589-dirty VMX Doing lvx: PASSED Doing stvx: PASSED Doing stvebx: PASSED Doing stvehx: PASSED Doing stvewx: PASSED Doing stvxl:PASSED success: test_alignment_handler_vmx test: test_alignment_handler_fp tags: git_version:Ubuntu-4.15.0-48.51-2-g705784d93589-dirty Floating point Doing lfd: PASSED Doing lfdx: PASSED Doing lfdp: PASSED Doing lfdpx:PASSED Doing lfdu: PASSED Doing lfdux:PASSED Doing lfs: PASSED Doing lfsx: PASSED Doing lfsu: PASSED Doing lfsux:PASSED Doing lfiwzx: PASSED Doing lfiw
[Kernel-packages] [Bug 1813118] Re: alignment test in powerpc from ubuntu_kernel_selftests failed on B/C Power9
https://lists.ubuntu.com/archives/kernel-team/2019-May/100696.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/1813118 Title: alignment test in powerpc from ubuntu_kernel_selftests failed on B/C Power9 Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: In Progress Bug description: == Justification == The copy_unaligned / paste_unaligned / paste_last_unaligned test in powerpc/alignment will fail on a Power9 node as which implements ISA 3.0B, but the test was designed base on ISA 3.0. From the commit message: This is a test of the ISA 3.0 "copy" instruction. That instruction has an L field, which if set to 1 specifies that "the instruction identifies the beginning of a move group" (pp 858). That's also referred to as "copy first" vs "copy". In ISA 3.0B the copy instruction does not have an L field, and the corresponding bit in the instruction must be set to 1. This test is generating a "copy" instruction, not a "copy first", and so on Power9 (which implements 3.0B), this results in an illegal instruction. So just drop the test entirely. We still have copy_first_unaligned to test the "copy first" behaviour. == Fix == * 83039f22 (selftests/powerpc: Remove Power9 copy_unaligned test) Patch can be cherry-picked into C, for Bionic it needs patches for bug 1828935 to land first (8d191587) to make it a clean cherry-pick. It's already landed in D and onward. == Test == Tested on a Power9 server with Cosmic, the broken tests will be removed correctly. == Regression Potential == Low. Code change limited to testing tools and just removing broken tests. We still have copy_first_unaligned to test the "copy first" behaviour. == Original Bug Report == This issue was only spotted on Power9 system "balter", for Power8 system, it has passed (skipped, and marked as passed) with this test: TAP version 13 selftests: copy_unaligned test: test_copy_unaligned tags: git_version:unknown !! child died by signal 4 failure: test_copy_unaligned not ok 1..1 selftests: copy_unaligned [FAIL] selftests: copy_first_unaligned test: test_copy_first_unaligned tags: git_version:unknown success: test_copy_first_unaligned ok 1..2 selftests: copy_first_unaligned [PASS] selftests: paste_unaligned test: test_paste_unaligned tags: git_version:unknown !! child died by signal 4 failure: test_paste_unaligned not ok 1..3 selftests: paste_unaligned [FAIL] selftests: paste_last_unaligned test: test_paste_last_unaligned tags: git_version:unknown !! child died by signal 4 failure: test_paste_last_unaligned not ok 1..4 selftests: paste_last_unaligned [FAIL] ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-43-generic 4.15.0-43.46 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic ppc64le AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 24 06:50 seq crw-rw 1 root audio 116, 33 Jan 24 06:50 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.5 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 Jan 24 07:05:20 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: 1.24 0.89 0.66 3/1412 8319 ProcLocks: 1: POSIX ADVISORY WRITE 3876 00:17:569 0 EOF 2: FLOCK ADVISORY WRITE 3556 00:17:497 0 EOF 3: FLOCK ADVISORY WRITE 4090 00:17:596 0 EOF 4: POSIX ADVISORY WRITE 3955 00:17:571 0 EOF 5: POSIX ADVISORY WRITE 1823 00:17:348 0 EOF ProcSwaps: Filename TypeSizeUsedPriority /swap.img file 8388544 0 -2 ProcVersion: Linux version 4.15.0-43-generic (buildd@bos02-ppc64el-020) (gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #46-Ubuntu SMP Thu Dec 6 14:43:28 UTC
[Kernel-packages] [Bug 1828394] Re: [UBUNTU] qdio: clear intparm during shutdown
There is no test kernel available, yet, but a kernel will be made available for verification purposes via the proposed archive pocket as part of the kernel SRU process. The patch/commit was already accepted: https://lists.ubuntu.com/archives/kernel-team/2019-May/100674.html and applied to the bionic-next tree. One of the next steps is now to create that new kernel version and make it available via proposed. Once available an (automated) comment will be added to this ticket and you will be asked for verification. This may take some days - see 'Kernel prep' here: https://kernel.ubuntu.com/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1828394 Title: [UBUNTU] qdio: clear intparm during shutdown Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Bug description: SRU Justification: [Impact] * Crash in qeth_irq() with "Unable to handle kernel pointer dereference in virtual kernel address space" [Fix] * 89286320a236d245834075fa13adb0bdd827ecaa 8928632 "s390/qdio: clear intparm during shutdown" [Test Case] * Offline an OSA CHPID with multiple active qeth interfaces. [Regression Potential] * The regression potential can be considered as very low since it only affects the s390x platform * and there it only affects the (ccW) qeth (OSA) network devices * and again this happens if the CHPID is offlined, which usually doesn't happen during regular operation. [Other Info] * The patch was upstream accepted with kernel 4.17, hence it's already part of cosmic, disco and eoan and proven there to work. * It needs to be applied to kernel 4.15 to land in 18.04 GA and 16.04.5 HWE. _ Description: qdio: clear intparm during shutdown Symptom: Crash in qeth_irq() with "Unable to handle kernel pointer dereference in virtual kernel address space". Problem: During shutdown, qdio returns its ccw device back to control by qeth - but doesn't reset the interrupt parameter on the device. If qdio_shutdown() failed to terminate its long-running IO on the ccw_device, qeth will subsequently do so. In this case the IRQ for the IO completion is presented to qeth_irq() with the _old_ interrupt parameter, which gets mis-interpreted as a valid qeth_cmd_buffer pointer. Dereferencing this bogus pointer in qeth_release_buffer() triggers the crash. Solution: When returning the ccw device in qdio_shutdown(), also reset its interrupt parameter. Reproduction: Offline an OSA CHPID with multiple active qeth interfaces. Component: Kernel Upstream-ID: 89286320a236d245834075fa13adb0bdd827ecaa Reported: Ubuntu 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1828394/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1768976] Re: Ubuntu 18.04 is overheating after upgrade from 16.04
I'm not sure if this is related but just in case. I upgraded from 16.04.1 LTS to 18.04.2 - straight after I started getting alarms from my SNMP monitoring, low voltage VBat etc. Upon checking the sensors output I can see it's all messed up: Linux host.no.domain 4.15.0-48-generic #51-Ubuntu SMP Wed Apr 3 08:28:49 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux root@host:/# sensors it8728-isa-0a20 Adapter: ISA adapter in0: +2.24 V (min = +2.32 V, max = +0.77 V) ALARM in1: +2.24 V (min = +2.83 V, max = +0.67 V) ALARM in2: +3.06 V (min = +1.68 V, max = +1.54 V) ALARM +3.3V:+3.41 V (min = +0.77 V, max = +0.31 V) ALARM in4: +2.24 V (min = +0.84 V, max = +0.65 V) ALARM in5: +2.24 V (min = +1.58 V, max = +1.64 V) ALARM in6: +2.24 V (min = +0.05 V, max = +2.36 V) 3VSB: +3.41 V (min = +1.66 V, max = +4.73 V) Vbat: +0.14 V fan1: 0 RPM (min = 13 RPM) ALARM fan2:2027 RPM (min = 11 RPM) fan3: 0 RPM (min = 25 RPM) ALARM temp1:+54.0°C (low = +101.0°C, high = +14.0°C) ALARM sensor = thermal diode temp2:+55.0°C (low = +40.0°C, high = +7.0°C) ALARM sensor = Intel PECI temp3: -128.0°C (low = +17.0°C, high = +26.0°C) sensor = disabled intrusion0: ALARM acpitz-virtual-0 Adapter: Virtual device temp1:+27.8°C (crit = +106.0°C) temp2:+29.8°C (crit = +106.0°C) coretemp-isa- Adapter: ISA adapter Package id 0: +57.0°C (high = +87.0°C, crit = +105.0°C) Core 0:+55.0°C (high = +87.0°C, crit = +105.0°C) Core 1:+56.0°C (high = +87.0°C, crit = +105.0°C) CPU temperatures and fan speed are probably OK but voltages are certainly not. May be a red-herring - just thought I should bring it up. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1768976 Title: Ubuntu 18.04 is overheating after upgrade from 16.04 Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-video-nouveau package in Ubuntu: Confirmed Bug description: Ubuntu is overheating at my laptop. Opening youtube on firefox is enough for critical temperature shutdown. Using lm-sensors for monitoring on 18.04 the temp varies between 70 and 85°C with only firefox or chrome open and doing nothing. On my old 16.04 with same using, the temp varies between 55 and 70°C. First thought was the driver nouveau is the problem, and finally I was able to install by add "nouveau.modeset=0" at livecd boot options, without temp shutdown. After install I disable the nouveau at modprobe blacklist, but the system continues overheating and shutdown with basic usage. I have no idea what's happening with the bionic at my laptop. My laptop is a Samsung RF411 i5 2nd Generation and Geforce 540M. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.17 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Thu May 3 16:22:40 2018 InstallationDate: Installed on 2018-04-27 (6 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) VarLogDistupgradeAptHistorylog: Start-Date: 2018-04-27 15:46:02 End-Date: 2018-04-27 15:46:02 VarLogDistupgradeAptlog: Log time: 2018-04-27 15:45:39.753331 Starting pkgProblemResolver with broken count: 0 Starting 2 pkgProblemResolver with broken count: 0 Done Log time: 2018-04-27 15:46:04.859979 VarLogDistupgradeApttermlog: Log started: 2018-04-27 15:46:02 Log ended: 2018-04-27 15:46:02 --- .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: edir 2354 F pulseaudio CompositorRunning: None DistUpgraded: Fresh install DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.15.0-20-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 4.15.0-22-generic, x86_64: installed GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd 2nd Generation Core Processor Family Integrated Graphics Controller [144d:c0a5] Subsystem: Samsung Electronics Co Ltd GF108M [GeForce GT 540M] [144d:c0a5] HibernationDevice: RESUME=UUID=e7a61aee-64c2-4c88-b4e1-4de481d0f88d InstallationDate: Installed on 2018-04-27 (36 days ago) Install
[Kernel-packages] [Bug 1828166] Re: perf top problem on z with Ubuntu 18.04
Hi, Can you please provide the output of 'uname -a'? Also, on the original bug report it states that the issue is fixed with the mentioned patch applied. On top of which kernel was this patch applied and tested? 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: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: In Progress 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 1828420] Re: Xenial update: 4.4.179 upstream stable release
** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Changed in: linux (Ubuntu Xenial) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Xenial) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1828420 Title: Xenial update: 4.4.179 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: 4.4.179 upstream stable release from git://git.kernel.org/ The following patches were applied: * arm64: debug: Don't propagate UNKNOWN FAR into si_code for debug signals * arm64: debug: Ensure debug handlers check triggering exception level * ext4: cleanup bh release code in ext4_ind_remove_space() * lib/int_sqrt: optimize initial value compute * tty/serial: atmel: Add is_half_duplex helper * mm: mempolicy: make mbind() return -EIO when MPOL_MF_STRICT is specified * i2c: core-smbus: prevent stack corruption on read I2C_BLOCK_DATA * Bluetooth: Fix decrementing reference count twice in releasing socket * tty/serial: atmel: RS485 HD w/DMA: enable RX after TX is stopped * CIFS: fix POSIX lock leak and invalid ptr deref * h8300: use cc-cross-prefix instead of hardcoding h8300-unknown-linux- * tracing: kdb: Fix ftdump to not sleep * gpio: gpio-omap: fix level interrupt idling * sysctl: handle overflow for file-max * enic: fix build warning without CONFIG_CPUMASK_OFFSTACK * mm/cma.c: cma_declare_contiguous: correct err handling * mm/page_ext.c: fix an imbalance with kmemleak * mm/vmalloc.c: fix kernel BUG at mm/vmalloc.c:512! * mm/slab.c: kmemleak no scan alien caches * ocfs2: fix a panic problem caused by o2cb_ctl * f2fs: do not use mutex lock in atomic context * fs/file.c: initialize init_files.resize_wait * cifs: use correct format characters * dm thin: add sanity checks to thin-pool and external snapshot creation * cifs: Fix NULL pointer dereference of devname * fs: fix guard_bio_eod to check for real EOD errors * tools lib traceevent: Fix buffer overflow in arg_eval * usb: chipidea: Grab the (legacy) USB PHY by phandle first * scsi: core: replace GFP_ATOMIC with GFP_KERNEL in scsi_scan.c * coresight: etm4x: Add support to enable ETMv4.2 * ARM: 8840/1: use a raw_spinlock_t in unwind * mmc: omap: fix the maximum timeout setting * e1000e: Fix -Wformat-truncation warnings * IB/mlx4: Increase the timeout for CM cache * scsi: megaraid_sas: return error when create DMA pool failed * perf test: Fix failure of 'evsel-tp-sched' test on s390 * SoC: imx-sgtl5000: add missing put_device() * media: sh_veu: Correct return type for mem2mem buffer helpers * media: s5p-jpeg: Correct return type for mem2mem buffer helpers * media: s5p-g2d: Correct return type for mem2mem buffer helpers * media: mx2_emmaprp: Correct return type for mem2mem buffer helpers * leds: lp55xx: fix null deref on firmware load failure * kprobes: Prohibit probing on bsearch() * ARM: 8833/1: Ensure that NEON code always compiles with Clang * ALSA: PCM: check if ops are defined before suspending PCM * bcache: fix input overflow to cache set sysfs file io_error_halflife * bcache: fix input overflow to sequential_cutoff * bcache: improve sysfs_strtoul_clamp() * fbdev: fbmem: fix memory access if logo is bigger than the screen * cdrom: Fix race condition in cdrom_sysctl_register * ASoC: fsl-asoc-card: fix object reference leaks in fsl_asoc_card_probe * soc: qcom: gsbi: Fix error handling in gsbi_probe() * mt7601u: bump supported EEPROM version * ARM: avoid Cortex-A9 livelock on tight dmb loops * tty: increase the default flip buffer limit to 2*640K * media: mt9m111: set initial frame size other than 0x0 * hwrng: virtio - Avoid repeated init of completion * soc/tegra: fuse: Fix illegal free of IO base address * hpet: Fix missing '=' character in the __setup() code of hpet_mmap_enable * dmaengine: imx-dma: fix warning comparison of distinct pointer types * netfilter: physdev: relax br_netfilter dependency * media: s5p-jpeg: Check for fmt_ver_flag when doing fmt enumeration * regulator: act8865: Fix act8600_sudcdc_voltage_ranges setting * wlcore: Fix memory leak in case wl12xx_fetch_firmware failure * x86/build: Mark per-CPU symbols as absolute explicitly for LLD * dmaengine: tegra: avoid overflow of byt
[Kernel-packages] [Bug 1796292] Re: Tight timeout for bcache removal causes spurious failures
** Tags added: cdo-qa foundations-engine
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1796292
Title:
Tight timeout for bcache removal causes spurious failures
Status in curtin:
New
Status in linux package in Ubuntu:
Confirmed
Bug description:
I've had a number of deployment faults where curtin would report
Timeout exceeded for removal of /sys/fs/bcache/xxx when doing a mass-
deployment of 30+ nodes. Upon retrying the node would usually deploy
fine. Experimentally I've set the timeout ridiculously high, and it
seems I'm getting no faults with this. I'm wondering if the timeout
for removal is set too tight, or might need to be made configurable.
--- curtin/util.py~ 2018-05-18 18:40:48.0 +
+++ curtin/util.py 2018-10-05 09:40:06.807390367 +
@@ -263,7 +263,7 @@
return _subp(*args, **kwargs)
-def wait_for_removal(path, retries=[1, 3, 5, 7]):
+def wait_for_removal(path, retries=[1, 3, 5, 7, 1200, 1200]):
if not path:
raise ValueError('wait_for_removal: missing path parameter')
To manage notifications about this bug go to:
https://bugs.launchpad.net/curtin/+bug/1796292/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828989] [NEW] ftrace in ubuntu_kernel_selftests complains "Illegal number" because of the absence of tput
Public bug reported: == Justification == Issue found in Disco, the ftrace test will complain about: ./ftracetest: 163: [: Illegal number: This is because the tput command fails and returns nothing for the shell script comparison. == Fix == * 0e27ded1 (selftests/ftrace: Handle the absence of tput) Prerequisite: * 4ce55a9c (selftests/ftrace: Replace \e with \033 Patch 4ce55a9c is needed to make this a clean cherry-pick. As it's fixing the color escape code, it is safe to pull this in. These patches can be cherry-picked into Disco and Eoan. == Test == Problem can be solved with this patch. == Regression Potential == No regression is expected. It's just fixing the testing tool. ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Po-Hsu Lin (cypressyew) Status: In Progress ** Affects: linux (Ubuntu Disco) Importance: Undecided Assignee: Po-Hsu Lin (cypressyew) Status: In Progress ** Affects: linux (Ubuntu Eoan) Importance: Undecided Assignee: Po-Hsu Lin (cypressyew) Status: In Progress ** Also affects: linux (Ubuntu Eoan) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Disco) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Eoan) Status: New => In Progress ** Changed in: linux (Ubuntu Disco) Status: New => In Progress ** Changed in: linux (Ubuntu Disco) Assignee: (unassigned) => Po-Hsu Lin (cypressyew) ** Changed in: linux (Ubuntu Eoan) Assignee: (unassigned) => Po-Hsu Lin (cypressyew) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1828989 Title: ftrace in ubuntu_kernel_selftests complains "Illegal number" because of the absence of tput 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: == Justification == Issue found in Disco, the ftrace test will complain about: ./ftracetest: 163: [: Illegal number: This is because the tput command fails and returns nothing for the shell script comparison. == Fix == * 0e27ded1 (selftests/ftrace: Handle the absence of tput) Prerequisite: * 4ce55a9c (selftests/ftrace: Replace \e with \033 Patch 4ce55a9c is needed to make this a clean cherry-pick. As it's fixing the color escape code, it is safe to pull this in. These patches can be cherry-picked into Disco and Eoan. == Test == Problem can be solved with this patch. == Regression Potential == No regression is expected. It's just fixing the testing tool. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1828989/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1779289] Re: [regression] bluetooth mouse not reconnected on reboot
Hello, The package in bionic-proposed has fixed the issue for me on Ubuntu 18.04.2 with a Logitech M535 mouse. After installing the update I had to re-pair the mouse (I was expecting to have to do this anyway). The mouse now connects automatically after: - waking up the laptop from sleep - turning the bluetooth mouse off and on In both instances without the fix I would have had to pair the mouse with the laptop again. With the proposed fix installed, I discovered no regressions, my other bluetooth peripherals work as expected (previously paired keyboard and headphones connected automatically when turned on). -Alex ** 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 bluez in Ubuntu. https://bugs.launchpad.net/bugs/1779289 Title: [regression] bluetooth mouse not reconnected on reboot Status in bluez package in Ubuntu: Invalid Status in gnome-bluetooth package in Ubuntu: Fix Released Status in gnome-bluetooth source package in Bionic: Fix Committed Bug description: * Impact Bluetooth pointer devices are not always correctly paired, which leads to have them failing to connect or not auto-reconnecting * Test case Pair a bluetooth mouse, it should re-connect automatically after suspend/resume or reboot cycles * Regression potential The change makes all devices go through pairing with the standard code that should work fine but we should keep an eye if it confuses some devices and lead to prompt for a PIN when that shouldn't be needd -- This affects at least 2 different bluetooth mice(both logitech) The behavior is that initial config when using the gui works but that the resulting "/var/lib/bluetooth///info" file does not contain a [LinkKey] section as the mouse does not require a pin. This mouse was connection on reboot under 16.04 so it's a new bug for 18.04 When setting up the mouse using bluetoothctl the info file is correctly written with a [LinkKey] section and everything works, ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-bluetooth 3.28.0-2 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jun 29 11:27:27 2018 InstallationDate: Installed on 2018-06-27 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-bluetooth UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1779289/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1779289] Re: [regression] bluetooth mouse not reconnected on reboot
Sorry, I forgot to add the package version to my previous comment (is there no way to edit a comment?): I've tested with gnome-bluetooth 3.28.0-2ubuntu0.2 from bionic-proposed. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1779289 Title: [regression] bluetooth mouse not reconnected on reboot Status in bluez package in Ubuntu: Invalid Status in gnome-bluetooth package in Ubuntu: Fix Released Status in gnome-bluetooth source package in Bionic: Fix Committed Bug description: * Impact Bluetooth pointer devices are not always correctly paired, which leads to have them failing to connect or not auto-reconnecting * Test case Pair a bluetooth mouse, it should re-connect automatically after suspend/resume or reboot cycles * Regression potential The change makes all devices go through pairing with the standard code that should work fine but we should keep an eye if it confuses some devices and lead to prompt for a PIN when that shouldn't be needd -- This affects at least 2 different bluetooth mice(both logitech) The behavior is that initial config when using the gui works but that the resulting "/var/lib/bluetooth///info" file does not contain a [LinkKey] section as the mouse does not require a pin. This mouse was connection on reboot under 16.04 so it's a new bug for 18.04 When setting up the mouse using bluetoothctl the info file is correctly written with a [LinkKey] section and everything works, ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-bluetooth 3.28.0-2 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jun 29 11:27:27 2018 InstallationDate: Installed on 2018-06-27 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-bluetooth UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1779289/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1826410] Re: Please package libbpf (which is done out of the kernel src) in Debian [for 19.10]
** Changed in: linux (Ubuntu) Status: Triaged => Confirmed ** 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/1826410 Title: Please package libbpf (which is done out of the kernel src) in Debian [for 19.10] Status in linux package in Ubuntu: Confirmed Status in linux source package in Disco: Fix Committed Bug description: Hi, Debian packages libbpf and so far does so out of the kernel source [1]. There is some movement to separate that from the kernel source [2] but this isn't ready yet. So far it is just a sync of the subtree out of the kernel sources. Since we do not share our kernel packaging we will not get this for-free without doing anything. If there will be an ITP about it in Debian I'll let you know and we can abort this, but unless that really happens I wanted to ask if you could as well build the libbpf* packages for 19.10 and onward? Note: this is not the same bpf lib as [3] despite the similarity in names. Reasoning: BPF becomes more and more important in general and is used in the kernel for many things. In the case that brought it to my attention it will be a PMD of DPDK that will need it to control XDP [4]. And XDP in general is an interesting and rising feature for network acceleration - I'd think it would be helpful to have this package around in Ubuntu. [1]: https://packages.debian.org/sid/libbpf-dev [2]: https://github.com/libbpf/libbpf [3]: https://github.com/iovisor/bcc [4]: https://www.iovisor.org/technology/xdp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1826410/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
We are applying these changes on linux-kvm only for Cosmic and Disco for now. If they don't cause any problems (e.g. boot speed increase) we will apply later also for the older series. ** Changed in: linux-kvm (Ubuntu Cosmic) Status: In Progress => Fix Committed ** Changed in: linux-kvm (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-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1799791 Title: linux-kvm: please support kexec Status in linux-kvm package in Ubuntu: Confirmed Status in linux-kvm source package in Xenial: In Progress Status in linux-kvm source package in Bionic: In Progress Status in linux-kvm source package in Cosmic: Fix Committed Status in linux-kvm source package in Disco: Fix Committed 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 1828995] [NEW] POSIX fix for ftrace in ubuntu_kernel_selftests
Public bug reported: == Justification == There are some non-POSIX implementations in the test script, which will generate some noise in the test reports like: -e -n [1] Basic trace file check -e [PASS] == Fix == * 4ce55a9c (selftests/ftrace: Replace \e with \033) * 37fb665b (selftests/ftrace: Replace echo -e with printf) These two patches can be cherry-picked into D/E == Test == Tested on a P8 box with Disco, the patched test will print the report in a proper format: [1] Basic trace file check [PASS] [2] Basic test for tracers [PASS] == Regression Potential == No regression is expected. This patchset just make sure this test comply with POSIX standard. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Disco) Importance: Undecided Status: New ** Affects: linux (Ubuntu Eoan) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Eoan) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Disco) 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/1828995 Title: POSIX fix for ftrace in ubuntu_kernel_selftests Status in linux package in Ubuntu: New Status in linux source package in Disco: New Status in linux source package in Eoan: New Bug description: == Justification == There are some non-POSIX implementations in the test script, which will generate some noise in the test reports like: -e -n [1] Basic trace file check -e [PASS] == Fix == * 4ce55a9c (selftests/ftrace: Replace \e with \033) * 37fb665b (selftests/ftrace: Replace echo -e with printf) These two patches can be cherry-picked into D/E == Test == Tested on a P8 box with Disco, the patched test will print the report in a proper format: [1] Basic trace file check[PASS] [2] Basic test for tracers[PASS] == Regression Potential == No regression is expected. This patchset just make sure this test comply with POSIX standard. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1828995/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828994] [NEW] POSIX fix for ftrace in ubuntu_kernel_selftests
Public bug reported: == Justification == There are some non-POSIX implementations in the test script, which will generate some noise in the test reports like: -e -n [1] Basic trace file check -e [PASS] == Fix == * 4ce55a9c (selftests/ftrace: Replace \e with \033) * 37fb665b (selftests/ftrace: Replace echo -e with printf) These two patches can be cherry-picked into D/E == Test == Tested on a P8 box with Disco, the patched test will print the report in a proper format: [1] Basic trace file check [PASS] [2] Basic test for tracers [PASS] == Regression Potential == No regression is expected. This patchset just make sure this test comply with POSIX standard. ** 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/1828994 Title: POSIX fix for ftrace in ubuntu_kernel_selftests Status in linux package in Ubuntu: New Bug description: == Justification == There are some non-POSIX implementations in the test script, which will generate some noise in the test reports like: -e -n [1] Basic trace file check -e [PASS] == Fix == * 4ce55a9c (selftests/ftrace: Replace \e with \033) * 37fb665b (selftests/ftrace: Replace echo -e with printf) These two patches can be cherry-picked into D/E == Test == Tested on a P8 box with Disco, the patched test will print the report in a proper format: [1] Basic trace file check[PASS] [2] Basic test for tracers[PASS] == Regression Potential == No regression is expected. This patchset just make sure this test comply with POSIX standard. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1828994/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828995] 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 1828995 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 ** Changed in: linux (Ubuntu Disco) 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/1828995 Title: POSIX fix for ftrace test in ubuntu_kernel_selftests 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: == Justification == There are some non-POSIX implementations in the test script, which will generate some noise in the test reports like: -e -n [1] Basic trace file check -e [PASS] -e -n [2] Basic test for tracers -e [PASS] == Fix == * 4ce55a9c (selftests/ftrace: Replace \e with \033) * 37fb665b (selftests/ftrace: Replace echo -e with printf) These two patches can be cherry-picked into D/E == Test == Tested on a P8 box with Disco, the patched test will print the report in a proper format: [1] Basic trace file check [PASS] [2] Basic test for tracers [PASS] == Regression Potential == No regression is expected. This patchset just make sure this test comply with POSIX standard. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1828995/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828994] 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 1828994 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/1828994 Title: POSIX fix for ftrace in ubuntu_kernel_selftests Status in linux package in Ubuntu: Incomplete Bug description: == Justification == There are some non-POSIX implementations in the test script, which will generate some noise in the test reports like: -e -n [1] Basic trace file check -e [PASS] == Fix == * 4ce55a9c (selftests/ftrace: Replace \e with \033) * 37fb665b (selftests/ftrace: Replace echo -e with printf) These two patches can be cherry-picked into D/E == Test == Tested on a P8 box with Disco, the patched test will print the report in a proper format: [1] Basic trace file check[PASS] [2] Basic test for tracers[PASS] == Regression Potential == No regression is expected. This patchset just make sure this test comply with POSIX standard. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1828994/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1804149] Re: Kernel panic, Oops: 0004 ilc:3 [#1] SMP, iscsi_q_20 iscsi_xmitworker [libiscsi]
IBM, have you had any luck with the test kernel? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1804149 Title: Kernel panic,Oops: 0004 ilc:3 [#1] SMP, iscsi_q_20 iscsi_xmitworker [libiscsi] Status in Ubuntu on IBM z Systems: Incomplete Status in linux package in Ubuntu: Triaged Bug description: == Comment: #0 - Michael Finnegan - 2018-11-19 14:14:40 == ---Problem Description--- Kernel panic,Oops: 0004 ilc:3 [#1] SMP, iscsi_q_20 iscsi_xmitworker [libiscsi] ---uname output--- Linux ilabg3 4.15.0-36-generic #39-Ubuntu SMP Mon Sep 24 16:13:24 UTC 2018 s390x s390x s390x GNU/Linux Machine Type = IBM 3906 M05 7G4 (z/VM 7.1.0) ---Debugger--- A debugger is not configured Contact Information = Michael Finnegan/finne...@us.ibm.com Stack trace output: dmesg.201811161956 [1363037.322472] Unable to handle kernel pointer dereference in virtual kernel address space [1363037.322481] Failing address: TEID: 0483 [1363037.322483] Fault in home space mode while using kernel ASCE. [1363037.322486] AS:00ea0007 R3:f37d0007 S:f37ff000 P:013d [1363037.322524] Oops: 0004 ilc:3 [#1] SMP [1363037.322529] Modules linked in: iptable_filter binfmt_misc rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace fscache qeth_l3 qeth_l2 s390_trng ghash_s390 prng aes_s390 des_s390 des_generic sha512_s390 sha256_s390 sha1_s390 sha_common qeth vmur ccwgroup vfio_ccw vfio_mdev mdev vfio_iommu_type1 vfio sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core sunrpc iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables dm_round_robin dm_service_time crc32_vx_s390 dasd_eckd_mod zfcp qdio scsi_transport_fc dasd_fba_mod dasd_mod scsi_dh_emc scsi_dh_rdac scsi_dh_alua dm_multipath [1363037.322567] CPU: 3 PID: 37970 Comm: kworker/u128:19 Not tainted 4.15.0-36-generic #39-Ubuntu [1363037.322573] Hardware name: IBM 3906 M05 7G4 (z/VM 7.1.0) [1363037.322581] Workqueue: iscsi_q_20 iscsi_xmitworker [libiscsi] [1363037.322583] Krnl PSW : c8051cf6 e49a28f4 (__iscsi_get_task+0x6/0x18 [libiscsi]) [1363037.322587]R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:2 PM:0 RI:0 EA:3 [1363037.322589] Krnl GPRS: 02923ce0 0400 [1363037.322591]03ff80277640 0008 788efc00 03ff802777cc [1363037.322592]03ff8027769c 78ce8310 [1363037.322594]f3689800 78ce83a2 03ff80272e8e 02923c90 [1363037.322601] Krnl Code: 03ff80272624: c0f4fcf6 brcl 15,3ff80272010 03ff8027262a: c0f4377b brcl 15,3ff80279520 #03ff80272630: c004 brcl 0,3ff80272630 >03ff80272636: eb012078006a asi 120(%r2),1 03ff8027263c: c0f43772 brcl 15,3ff80279520 03ff80272642: 0707 bcr 0,%r7 03ff80272644: 0707 bcr 0,%r7 03ff80272646: 0707 bcr 0,%r7 [1363037.322618] Call Trace: [1363037.322621] ([<03ff80272ec6>] iscsi_xmit_task+0x86/0x138 [libiscsi]) [1363037.322625] [<03ff8027769c>] iscsi_data_xmit+0x44c/0x548 [libiscsi] [1363037.322636] [<03ff802777cc>] iscsi_xmitworker+0x34/0x58 [libiscsi] [1363037.322642] [<001918f2>] process_one_work+0x262/0x4d8 [1363037.322644] [<00191bc0>] worker_thread+0x58/0x4e8 [1363037.322648] [<00198d24>] kthread+0x14c/0x168 [1363037.322652] [<008e3eb2>] kernel_thread_starter+0xa/0x10 [1363037.322654] [<008e3ea8>] kernel_thread_starter+0x0/0x10 [1363037.322655] Last Breaking-Event-Address: [1363037.322657] [<03ff80272e88>] iscsi_xmit_task+0x48/0x138 [libiscsi] [1363037.322658] [1363037.322660] Kernel panic - not syncing: Fatal exception in interrupt Oops output: Oops: 0004 ilc:3 [#1] SMP *Additional Instructions for Michael Finnegan/finne...@us.ibm.com: -Post a private note with access information to the machine that the bug is occuring on. -Attach sysctl -a output output to the bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1804149/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1823056] Re: autopkgtests run too often, too much and don't skip enough
** Changed in: linux (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 in Ubuntu. https://bugs.launchpad.net/bugs/1823056 Title: autopkgtests run too often, too much and don't skip enough Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Committed Bug description: [Impact] * linux autopkgtest should only execute either rebuild tests, when triggered by toolchain. or execute regression suite when triggered by meta but never both. As otherwise, it results in false negative results for the kernel [Test Case] * Trigger adt test of linux with a matching linux-meta. Check that rebuild test is skipped, and that the regression suite test runs. * trigger adt test of linux with triggered by gcc-6/7/8 (as appropriate) and observe that rebuild test runs, and regression suite test is skipped. * (when this is applied to flavours) trigger adt test of linux-* with a matching flavour meta, and check that regression test-suite is skipped on kernels that cannot boot in scaling stack (e.g. gcp, azure, aws, etc) [Fix] * debian/tests/* are modified to pay more attention as to what they are triggered by, and raise appropriate skipped error codes [Regression Potential] * incorrect tests may run at incorrect time is the regression potential here, hence the two test cases verify that the right tests are executed when expected. * care was taken to take into account all linux kernel flavours, hence the third test case need to be reverified on flavoured kernels. [Other Info] * affects all stable series xenial and up, across all kernel flavours To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823056/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819493] Re: network loss and traffic loss problems with i40e 2.1.14-k in Xenial HWE Kernel 4.15
The following commits are required for 4.15:
- 14a627313893 ("i40e: Check and correct speed values for link on open")
- 6f0c1b41ae95 ("i40e: Set fec_config when forcing link state")
- c3880bd159d4 ("i40e: link_down_on_close private flag support")
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1819493
Title:
network loss and traffic loss problems with i40e 2.1.14-k in Xenial
HWE Kernel 4.15
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Xenial:
Confirmed
Status in linux source package in Bionic:
Confirmed
Bug description:
[SRU Justification]
= Impact =
Network loss and traffic loss problems experienced by customer with i40e
2.1.14-k in Xenial HWE Kernel 4.15
The traffic issues were reported from our customer deployments and we had
Intel helping us with the troubleshooting of the problem.
= Fix =
Intel recommends and customer requests application of the following
commit e78d9a39fd06109022d11c8ca444cfcec2abb290 (upstream Linus tree)
= Testcase =
The issue could only be seen in customer environment. Regression
testing only would be possible.
= Regression Potential =
Change is limited to a specific driver, testing should show if there
is any negative impact.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1819493/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828995] Re: POSIX fix for ftrace test in ubuntu_kernel_selftests
** Summary changed: - POSIX fix for ftrace in ubuntu_kernel_selftests + POSIX fix for ftrace test in ubuntu_kernel_selftests ** Description changed: == Justification == There are some non-POSIX implementations in the test script, which will generate some noise in the test reports like: - -e -n [1] Basic trace file check + -e -n [1] Basic trace file check + -e [PASS] + -e -n [2] Basic test for tracers -e [PASS] == Fix == * 4ce55a9c (selftests/ftrace: Replace \e with \033) * 37fb665b (selftests/ftrace: Replace echo -e with printf) These two patches can be cherry-picked into D/E == Test == Tested on a P8 box with Disco, the patched test will print the report in a proper format: - [1] Basic trace file check[PASS] - [2] Basic test for tracers[PASS] + [1] Basic trace file check [PASS] + [2] Basic test for tracers [PASS] == Regression Potential == No regression is expected. This patchset just make sure this test comply with POSIX standard. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1828995 Title: POSIX fix for ftrace test in ubuntu_kernel_selftests 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: == Justification == There are some non-POSIX implementations in the test script, which will generate some noise in the test reports like: -e -n [1] Basic trace file check -e [PASS] -e -n [2] Basic test for tracers -e [PASS] == Fix == * 4ce55a9c (selftests/ftrace: Replace \e with \033) * 37fb665b (selftests/ftrace: Replace echo -e with printf) These two patches can be cherry-picked into D/E == Test == Tested on a P8 box with Disco, the patched test will print the report in a proper format: [1] Basic trace file check [PASS] [2] Basic test for tracers [PASS] == Regression Potential == No regression is expected. This patchset just make sure this test comply with POSIX standard. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1828995/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828995] Re: POSIX fix for ftrace test in ubuntu_kernel_selftests
https://lists.ubuntu.com/archives/kernel-team/2019-May/100707.html ** Tags added: disco eoan ** Changed in: linux (Ubuntu Disco) Status: Incomplete => In Progress ** Changed in: linux (Ubuntu Eoan) Status: Incomplete => In Progress ** Changed in: linux (Ubuntu Disco) Assignee: (unassigned) => Po-Hsu Lin (cypressyew) ** Changed in: linux (Ubuntu Eoan) Assignee: (unassigned) => Po-Hsu Lin (cypressyew) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1828995 Title: POSIX fix for ftrace test in ubuntu_kernel_selftests 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: == Justification == There are some non-POSIX implementations in the test script, which will generate some noise in the test reports like: -e -n [1] Basic trace file check -e [PASS] -e -n [2] Basic test for tracers -e [PASS] == Fix == * 4ce55a9c (selftests/ftrace: Replace \e with \033) * 37fb665b (selftests/ftrace: Replace echo -e with printf) These two patches can be cherry-picked into D/E == Test == Tested on a P8 box with Disco, the patched test will print the report in a proper format: [1] Basic trace file check [PASS] [2] Basic test for tracers [PASS] == Regression Potential == No regression is expected. This patchset just make sure this test comply with POSIX standard. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1828995/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1775137] Re: Prevent speculation on user controlled pointer
** Changed in: linux (Ubuntu Precise)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1775137
Title:
Prevent speculation on user controlled pointer
Status in linux package in Ubuntu:
Incomplete
Status in linux source package in Precise:
Fix Released
Status in linux source package in Trusty:
Fix Released
Status in linux source package in Xenial:
Fix Released
Bug description:
== SRU Justification ==
Upstream's Spectre v1 mitigation prevents speculation on a user controlled
pointer. This part of the Spectre v1 patchset was never backported to 4.4 (for
unknown reasons) so Xenial/Trusty/Precise are lacking it as well. All the other
stable upstream kernels include it, so add it to our older kernels.
== Fix ==
Backport the following patches:
x86/uaccess: Use __uaccess_begin_nospec() and uaccess_try_nospec
x86/usercopy: Replace open coded stac/clac with __uaccess_{begin, end}
x86: Introduce __uaccess_begin_nospec() and uaccess_try_nospec
== Regression Potential ==
Low. Patches have been in upstream (and other distro kernels) for quite a
while now and the changes only introduce a barrier on copy_from_user operations.
== Test Case ==
TBD.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775137/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1774181] Re: Update to upstream's implementation of Spectre v1 mitigation
** Changed in: linux (Ubuntu Precise) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1774181 Title: Update to upstream's implementation of Spectre v1 mitigation Status in linux package in Ubuntu: Incomplete Status in linux source package in Precise: Fix Released Status in linux source package in Trusty: Fix Released Status in linux source package in Xenial: Fix Released Bug description: Xenial/Trusty/Precise are currently lacking full support of upstream's Spectre v1 mitigation. Add the missing patches and merge them with Ubuntu's current implementation. == SRU Justification == Ubuntu's Spectre v1 mitigation is based on the original embargoed patchset which introduced a barrier macro to prevent speculation beyond array boundaries for user controlled indices. What eventually landed in upstream is slightly different and uses a barrier macro in combination with a masking solution (plus syscall table and user pointer sanitation). During the updates to newer stable upstream versions, all those patches were skipped. After reviewing them, we want to bring them back and merge them with the current implementation which brings us back in sync with upstream stable. == Fix == Add all the missing Spectre v1 patches from upstream stable 4.4.118 to 4.4.131. Where appropriate, replace Ubuntu's additional barriers with the masking macro. == Regression Potential == Low. The patches have been in upstream for quite a while now and we keep the speculation barriers that are currently in Ubuntu but not in upstream. == Test Case == TBD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774181/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1824690] Re: proc_thermal flooding dmesg
Hi Giovanni, do you mind testing the kernels as mentioned in comment #24, 1. download the .deb packages https://kernel.ubuntu.com/~cking/lp-1824690 2. from the relevant Download directory, install them using: sudo dpkg -i *.deb 3. reboot and test. Thank you. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1824690 Title: proc_thermal flooding dmesg Status in linux package in Ubuntu: Incomplete Status in thermald package in Ubuntu: Incomplete Bug description: [ 11.520358] proc_thermal :00:00.1: Unsupported event [0x91] [ 16.532358] proc_thermal :00:00.1: Unsupported event [0x91] [ 21.572719] proc_thermal :00:00.1: Unsupported event [0x91] [ 26.580855] proc_thermal :00:00.1: Unsupported event [0x91] [ 31.588851] proc_thermal :00:00.1: Unsupported event [0x91] [ 36.592827] proc_thermal :00:00.1: Unsupported event [0x91] [ 41.572682] random: crng init done [ 41.572690] random: 7 urandom warning(s) missed due to ratelimiting Kernel 4.18.0-18-generic No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.2 LTS Release: 18.04 Codename: bionic --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: juno 1175 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-04-15 (0 days ago) InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0025 Intel Corp. Bus 001 Device 003: ID 04f2:b59e Chicony Electronics Co., Ltd Bus 001 Device 002: ID 1ea7:0064 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Notebook N24_25GU Package: thermald 1.7.0-5ubuntu2 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-18-generic root=UUID=a23ca3ac-6284-45ce-9aa8-6670879910e7 ro quiet splash acpi_osi= acpi_os_name=Linux vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-18.19~18.04.1-generic 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-18-generic N/A linux-backports-modules-4.18.0-18-generic N/A linux-firmware 1.173.5 Tags: bionic Uname: Linux 4.18.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/18/2018 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.06 dmi.board.asset.tag: Tag 12345 dmi.board.name: N24_25GU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.06:bd05/18/2018:svnNotebook:pnN24_25GU:pvrNotApplicable:rvnNotebook:rnN24_25GU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: N24_25GU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824690/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828763] Re: Cannot build kernel 4.15.0-48.51 due to an in-source-tree ZFS module.
Hi, Andrea, thanks for your prompt response.
I tried to build kernel sources applied your patch, and it failed with an error.
/home/np/linux-4.15/zfs/include/sys/trace_dmu.h:65:33: error: ‘dmu_tx_t {aka
struct dmu_tx}’ has no member named ‘waited’; did you mean ‘tx_waited’?
__entry->tx_waited = tx->waited;
According to the error message, the following diff caused the problem.
@@ -62,7 +62,7 @@ DECLARE_EVENT_CLASS(zfs_delay_mintime_class,
__entry->tx_lastsnap_txg= tx->tx_lastsnap_txg;
__entry->tx_lasttried_txg = tx->tx_lasttried_txg;
__entry->tx_anyobj = tx->tx_anyobj;
- __entry->tx_dirty_delayed = tx->tx_dirty_delayed;
+ __entry->tx_waited = tx->waited;
I think we should assign '__entry->tx_waited' as 'tx->tx_waited', not
'tx->waited'.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1828763
Title:
Cannot build kernel 4.15.0-48.51 due to an in-source-tree ZFS module.
Status in linux package in Ubuntu:
Confirmed
Bug description:
I tried to build a kernel 4.15.0-48.51 that cloned from the Ubuntu
kernel git (x86_64-generic flavour).
commit c50532b9d7b623ff98aeaf0b848e58adae54ca75 (HEAD -> master, tag:
Ubuntu-4.15.0-48.51, origin/master, origin/HEAD)
Author: Andrea Righi
Date: Tue Apr 2 18:31:55 2019 +0200
UBUNTU: Ubuntu-4.15.0-48.51
Signed-off-by: Andrea Righi
1. Build a kernel image with 'zfs_enable' flag set as false.
2. Build SPL/ZFS modules independently by 'make' command (debug purpose;
DECLARE_EVENT_CLASS() enabled).
But 'make' was always failed at the same point,
'zfs/module/zfs/trace.c' (as seem as below).
In file included from /home/np/linux-4.15/include/trace/define_trace.h:96:0,
from /home/np/linux-4.15/zfs/include/sys/trace_dmu.h:127,
from /home/np/linux-4.15/zfs/module/zfs/trace.c:45:
/home/np/linux-4.15/zfs/include/sys/trace_dmu.h: In function
‘trace_event_raw_event_zfs_delay_mintime_class’:
/home/np/linux-4.15/zfs/include/sys/trace_dmu.h:65:37: error: ‘dmu_tx_t {aka
struct dmu_tx}’ has no member named ‘tx_dirty_delayed’
__entry->tx_dirty_delayed = tx->tx_dirty_delayed;
^
/home/np/linux-4.15/include/trace/trace_events.h:719:4: note: in definition
of macro ‘DECLARE_EVENT_CLASS’
{ assign; } \
^~
/home/np/linux-4.15/zfs/include/sys/trace_dmu.h:60:2: note: in expansion of
macro ‘TP_fast_assign’
TP_fast_assign(
^~
In file included from /home/np/linux-4.15/include/trace/define_trace.h:97:0,
from /home/np/linux-4.15/zfs/include/sys/trace_dmu.h:127,
from /home/np/linux-4.15/zfs/module/zfs/trace.c:45:
/home/np/linux-4.15/zfs/include/sys/trace_dmu.h: In function
‘perf_trace_zfs_delay_mintime_class’:
/home/np/linux-4.15/zfs/include/sys/trace_dmu.h:65:37: error: ‘dmu_tx_t {aka
struct dmu_tx}’ has no member named ‘tx_dirty_delayed’
__entry->tx_dirty_delayed = tx->tx_dirty_delayed;
^
/home/np/linux-4.15/include/trace/perf.h:66:4: note: in definition of macro
‘DECLARE_EVENT_CLASS’
{ assign; } \
^~
/home/np/linux-4.15/zfs/include/sys/trace_dmu.h:60:2: note: in expansion of
macro ‘TP_fast_assign’
TP_fast_assign(
^~
I tried to debug this issue with myself and found something intriguing.
In 'zfs/include/sys/trace_dmu.h', the failed code accessing
'tx_dirty_delayed' from 'dmu_tx_t' (which same as 'struct dmu_tx').
DECLARE_EVENT_CLASS(zfs_delay_mintime_class,
TP_PROTO(dmu_tx_t *tx, uint64_t dirty, uint64_t min_tx_time),
TP_ARGS(tx, dirty, min_tx_time),
TP_STRUCT__entry(
__field(uint64_t, tx_txg)
__field(uint64_t, tx_lastsnap_txg)
__field(uint64_t, tx_lasttried_txg)
__field(boolean_t, tx_anyobj)
__field(boolean_t, tx_dirty_delayed)
__field(hrtime_t, tx_start)
__field(boolean_t, tx_wait_dirty)
__field(int,tx_err)
__field(uint64_t, min_tx_time)
__field(uint64_t, dirty)
),
TP_fast_assign(
__entry->tx_txg = tx->tx_txg;
__entry->tx_lastsnap_txg= tx->tx_lastsnap_txg;
__entry->tx_lasttried_txg = tx->tx_lasttried_txg;
__entry->tx_anyobj = tx->tx_anyobj;
__entry->tx_dirty_delayed = tx->tx_dirty_delayed;
__entry->tx_start =
[Kernel-packages] [Bug 1827112] Re: nvidia-graphics-drivers-418 418.56-0ubuntu1 ADT test failure with linux 5.1.0-1.1
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-418 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-418 in Ubuntu. https://bugs.launchpad.net/bugs/1827112 Title: nvidia-graphics-drivers-418 418.56-0ubuntu1 ADT test failure with linux 5.1.0-1.1 Status in nvidia-graphics-drivers-418 package in Ubuntu: Confirmed Bug description: Testing failed on: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-418/+bug/1827112/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828948] Re: OBSOLETE_BY in DKMS.CONF not work
** Also affects: dkms (Ubuntu) Importance: Undecided Status: New ** Also affects: dkms (Ubuntu Bionic) Importance: Undecided Status: New -- 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 not work Status in DKMS: Confirmed Status in OEM Priority Project: New Status in dkms package in Ubuntu: New Status in dkms source package in Bionic: New Bug description: the issue has been fixed by upstream [1]: https://github.com/dell/dkms/issues/81 we need to land that fix to DKMS on Ubuntu as well. [1] https://github.com/dell/dkms 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 1827944] Re: Kernel 5.1 is unsupported (and nvidia-418.56 error) [error: initialization of `vm_fault_t (*)(struct vm_fault *)' {aka `unsigned int (*)(struct vm_fault *)'} from i
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: nvidia-graphics-drivers-418 (Ubuntu)
Status: New => Confirmed
--
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/1827944
Title:
Kernel 5.1 is unsupported (and nvidia-418.56 error) [error:
initialization of `vm_fault_t (*)(struct vm_fault *)' {aka `unsigned
int (*)(struct vm_fault *)'} from incompatible pointer type `int
(*)(struct vm_fault *)']
Status in dkms package in Ubuntu:
Opinion
Status in nvidia-graphics-drivers-418 package in Ubuntu:
Confirmed
Bug description:
Installing mainline v5.1 from https://kernel.ubuntu.com/~kernel-
ppa/mainline/v5.1/ , I get this error:
ERROR (dkms apport): kernel package linux-
headers-5.1.0-050100-generic is not supported
Also, building nvidia modules fail; I'm not sure it's
related/critical.
See attached file for both logs.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1827944/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1824016] Re: Built-Using incorrect
In Xenial, hwe-edge is a meta-only source pointing at the hwe binaries. So there is no separate linux-signed. ** Changed in: linux-signed-hwe-edge (Ubuntu Xenial) Status: In Progress => Invalid ** Changed in: linux-signed-hwe (Ubuntu Bionic) Status: In Progress => Fix Committed ** Changed in: linux-signed-hwe-edge (Ubuntu Bionic) Status: In Progress => Fix Committed ** Changed in: linux-signed (Ubuntu Bionic) Status: In Progress => Fix Committed ** Changed in: linux-signed (Ubuntu Cosmic) Importance: Undecided => Medium ** Changed in: linux-signed (Ubuntu Cosmic) Status: In Progress => Fix Committed ** Changed in: linux-signed (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: linux-signed (Ubuntu Xenial) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1824016 Title: Built-Using incorrect Status in linux-signed package in Ubuntu: In Progress Status in linux-signed-hwe package in Ubuntu: Invalid Status in linux-signed-hwe-edge package in Ubuntu: Invalid Status in linux-signed source package in Xenial: In Progress Status in linux-signed-hwe source package in Xenial: Fix Committed Status in linux-signed-hwe-edge source package in Xenial: Invalid Status in linux-signed source package in Bionic: Fix Committed Status in linux-signed-hwe source package in Bionic: Fix Committed Status in linux-signed-hwe-edge source package in Bionic: Fix Committed Status in linux-signed source package in Cosmic: Fix Committed Status in linux-signed-hwe source package in Cosmic: Invalid Status in linux-signed-hwe-edge source package in Cosmic: Invalid Status in linux-signed source package in Disco: Fix Committed Status in linux-signed-hwe source package in Disco: Invalid Status in linux-signed-hwe-edge source package in Disco: Invalid Bug description: [Impact] The Build-Using control file field is incorrect for linux-signed-hwe & linux-signed-hwe-edge. They claim they were built against the "linux" package, but should be linux-hwe/linux-hwe-edge respectively. [Test Case] Look at the Packages file. [Fix] Detect and insert the correct package name at build time. [Regression Risk] Hm.. maybe if something gets added using the PACKAGE keyword in control.stub that isn't intended to be replaced gets accidentally replaced, screwing up some other control field? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1824016/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828657] [NEW] Slow resume after lid close/open
You have been subscribed to a public bug: Summary 1.) Release Info: Description: Ubuntu 19.04 Release:19.04 2.) Package version: linux-image-5.0.0-13-generic 3.) Expected behavior: Computer resumes shortly after opening lid. 4.) Actual behavior: Computer takes ~2 minutes to resume after opening lid. I have installed Ubuntu 19.04 (Disco Dingo) on my Lenovo Flex 6-11IGM. I found that when it resumes from sleep after opening the lid, it takes a long time to resume (~2 minutes). While experimenting with the upstream kernel releases, I found that the problem was introduced with version 5.0.5 version of the Linux kernel; the problem does not occur when I run version 5.0.4. I've narrowed the culprit down to the following commit in the upstream kernel: a57af6d07... ALSA: hda - Enforces runtime_resume after S3 and S4 for each codec This change was applied to the ubuntu kernel with commit 9c51afaceb61459d2becac8fb32c860bb084e643. The following messages appear in the system log upon resume with the released ubuntu kernel: May 05 20:22:11 brian-Lenovo-FLEX-6-11IGM kernel: snd_hda_intel :00:0e.0: azx_get_response timeout, switching to polling mode: last cmd=0x20bf8100 May 05 20:22:11 brian-Lenovo-FLEX-6-11IGM kernel: hid-sensor-hub 001F:8086:22D8.0003: timeout waiting for response from ISHTP device May 05 20:22:11 brian-Lenovo-FLEX-6-11IGM kernel: snd_hda_intel :00:0e.0: No response from codec, disabling MSI: last cmd=0x20bf8100 May 05 20:22:11 brian-Lenovo-FLEX-6-11IGM kernel: snd_hda_codec_hdmi hdaudioC0D2: Unable to sync register 0x2f0d00. -11 These messages do not appear in the system log upon resume when running with upstream kernel version 5.0.4. I have upgraded the system BIOS to the latest from Lenovo (6qcn47ww), but the problem persists. For now, I will run with the 5.0.4 version of the upstream kernel, as I am not experiencing any issues with it. Thank you. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- Slow resume after lid close/open https://bugs.launchpad.net/bugs/1828657 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1804481] Re: SecureBoot support for arm64
** Changed in: linux-signed-hwe-edge (Ubuntu Bionic) Status: In Progress => Fix Committed ** Also affects: linux-signed-hwe (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-signed-hwe (Ubuntu Cosmic) Status: New => Invalid ** Changed in: linux-signed-hwe (Ubuntu Disco) Status: New => Invalid ** Changed in: linux-signed-hwe (Ubuntu) Status: New => Invalid ** Changed in: linux-signed-hwe (Ubuntu Bionic) Importance: Undecided => Critical ** Changed in: linux-signed-hwe (Ubuntu Bionic) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1804481 Title: SecureBoot support for arm64 Status in linux package in Ubuntu: Fix Released Status in linux-meta package in Ubuntu: In Progress Status in linux-signed package in Ubuntu: Fix Released Status in linux-signed-hwe package in Ubuntu: Invalid Status in linux-signed-hwe-edge package in Ubuntu: New Status in shim package in Ubuntu: Fix Released Status in shim-signed package in Ubuntu: Fix Released Status in linux source package in Bionic: Triaged Status in linux-meta source package in Bionic: Triaged Status in linux-signed source package in Bionic: Triaged Status in linux-signed-hwe source package in Bionic: Fix Committed Status in linux-signed-hwe-edge source package in Bionic: Fix Committed Status in shim source package in Bionic: Fix Released Status in shim-signed source package in Bionic: Triaged Status in linux source package in Cosmic: Triaged Status in linux-meta source package in Cosmic: Triaged Status in linux-signed source package in Cosmic: Triaged Status in linux-signed-hwe source package in Cosmic: Invalid Status in linux-signed-hwe-edge source package in Cosmic: Invalid Status in shim source package in Cosmic: Fix Released Status in shim-signed source package in Cosmic: Triaged Status in linux source package in Disco: Fix Released Status in linux-meta source package in Disco: In Progress Status in linux-signed source package in Disco: Fix Released Status in linux-signed-hwe source package in Disco: Invalid Status in linux-signed-hwe-edge source package in Disco: Invalid Status in shim source package in Disco: Fix Released Status in shim-signed source package in Disco: Fix Released Bug description: [Impact] Ubuntu does not currently support SecureBoot for UEFI systems on arm64 platforms. [Test Case] See: https://wiki.ubuntu.com/UEFI/SecureBoot/Testing [Fix] - Introduce shim-signed for arm64 - Introduce grub-signed for arm64 - Produce signed linux kernels [Regression Risk] We're enabling new signed packages - regressions would most likely fall into packaging issues. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1804481/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1796292] Re: Tight timeout for bcache removal causes spurious failures
I was looking into kernel commits and I came across this:
https://github.com/torvalds/linux/commit/fadd94e05c02afec7b70b0b14915624f1782f578
So, as far as I understood, it actually deals with the issue of manual
device detach during a writeback clean-up and causing deadlock. The
timeline makes sense when we look for Bionic GA kernel, as well. Bionic
GA should not include this fix, but HWE should.
Could we run the tests again, but focusing on Bionic hwe? Afair hwe runs
4.18, which should include this commit.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1796292
Title:
Tight timeout for bcache removal causes spurious failures
Status in curtin:
New
Status in linux package in Ubuntu:
Confirmed
Bug description:
I've had a number of deployment faults where curtin would report
Timeout exceeded for removal of /sys/fs/bcache/xxx when doing a mass-
deployment of 30+ nodes. Upon retrying the node would usually deploy
fine. Experimentally I've set the timeout ridiculously high, and it
seems I'm getting no faults with this. I'm wondering if the timeout
for removal is set too tight, or might need to be made configurable.
--- curtin/util.py~ 2018-05-18 18:40:48.0 +
+++ curtin/util.py 2018-10-05 09:40:06.807390367 +
@@ -263,7 +263,7 @@
return _subp(*args, **kwargs)
-def wait_for_removal(path, retries=[1, 3, 5, 7]):
+def wait_for_removal(path, retries=[1, 3, 5, 7, 1200, 1200]):
if not path:
raise ValueError('wait_for_removal: missing path parameter')
To manage notifications about this bug go to:
https://bugs.launchpad.net/curtin/+bug/1796292/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828657] Re: Slow resume after lid close/open
** Package changed: apport (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1828657 Title: Slow resume after lid close/open Status in linux package in Ubuntu: Incomplete Bug description: Summary 1.) Release Info: Description: Ubuntu 19.04 Release: 19.04 2.) Package version: linux-image-5.0.0-13-generic 3.) Expected behavior: Computer resumes shortly after opening lid. 4.) Actual behavior: Computer takes ~2 minutes to resume after opening lid. I have installed Ubuntu 19.04 (Disco Dingo) on my Lenovo Flex 6-11IGM. I found that when it resumes from sleep after opening the lid, it takes a long time to resume (~2 minutes). While experimenting with the upstream kernel releases, I found that the problem was introduced with version 5.0.5 version of the Linux kernel; the problem does not occur when I run version 5.0.4. I've narrowed the culprit down to the following commit in the upstream kernel: a57af6d07... ALSA: hda - Enforces runtime_resume after S3 and S4 for each codec This change was applied to the ubuntu kernel with commit 9c51afaceb61459d2becac8fb32c860bb084e643. The following messages appear in the system log upon resume with the released ubuntu kernel: May 05 20:22:11 brian-Lenovo-FLEX-6-11IGM kernel: snd_hda_intel :00:0e.0: azx_get_response timeout, switching to polling mode: last cmd=0x20bf8100 May 05 20:22:11 brian-Lenovo-FLEX-6-11IGM kernel: hid-sensor-hub 001F:8086:22D8.0003: timeout waiting for response from ISHTP device May 05 20:22:11 brian-Lenovo-FLEX-6-11IGM kernel: snd_hda_intel :00:0e.0: No response from codec, disabling MSI: last cmd=0x20bf8100 May 05 20:22:11 brian-Lenovo-FLEX-6-11IGM kernel: snd_hda_codec_hdmi hdaudioC0D2: Unable to sync register 0x2f0d00. -11 These messages do not appear in the system log upon resume when running with upstream kernel version 5.0.4. I have upgraded the system BIOS to the latest from Lenovo (6qcn47ww), but the problem persists. For now, I will run with the 5.0.4 version of the upstream kernel, as I am not experiencing any issues with it. Thank you. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1828657/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1824016] Re: Built-Using incorrect
** Changed in: linux-signed-hwe (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: linux-signed-hwe (Ubuntu Xenial) Status: In Progress => Fix Committed ** Changed in: linux-signed-hwe (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: linux-signed-hwe-edge (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: linux-signed (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-signed in Ubuntu. https://bugs.launchpad.net/bugs/1824016 Title: Built-Using incorrect Status in linux-signed package in Ubuntu: In Progress Status in linux-signed-hwe package in Ubuntu: Invalid Status in linux-signed-hwe-edge package in Ubuntu: Invalid Status in linux-signed source package in Xenial: Fix Committed Status in linux-signed-hwe source package in Xenial: Fix Committed Status in linux-signed-hwe-edge source package in Xenial: Invalid Status in linux-signed source package in Bionic: Fix Committed Status in linux-signed-hwe source package in Bionic: Fix Committed Status in linux-signed-hwe-edge source package in Bionic: Fix Committed Status in linux-signed source package in Cosmic: Fix Committed Status in linux-signed-hwe source package in Cosmic: Invalid Status in linux-signed-hwe-edge source package in Cosmic: Invalid Status in linux-signed source package in Disco: Fix Committed Status in linux-signed-hwe source package in Disco: Invalid Status in linux-signed-hwe-edge source package in Disco: Invalid Bug description: [Impact] The Build-Using control file field is incorrect for linux-signed-hwe & linux-signed-hwe-edge. They claim they were built against the "linux" package, but should be linux-hwe/linux-hwe-edge respectively. [Test Case] Look at the Packages file. [Fix] Detect and insert the correct package name at build time. [Regression Risk] Hm.. maybe if something gets added using the PACKAGE keyword in control.stub that isn't intended to be replaced gets accidentally replaced, screwing up some other control field? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1824016/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1827122] Re: shiftfs: lock security sensitive superblock flags
** Changed in: linux (Ubuntu) Status: In Progress => Fix Committed ** Also affects: linux (Ubuntu Disco) 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/1827122 Title: shiftfs: lock security sensitive superblock flags Status in linux package in Ubuntu: Fix Committed Status in linux source package in Disco: New Bug description: Felix Abecassis from Nvidia recently reported the following bug: "I recently upgraded to Ubuntu 19.04, and decided to experiment with shiftfs and unprivileged overlay. My goal was to have root (in my case, the docker daemon) download overlay layers and then have multiple users leveraging shiftfs + unprivileged overlay to assemble the rootfs without copying and chowning. For obvious security reasons, I want root to expose these layers as read-only, any change will be to the user-owned "upper" filesystem. Here's what I'm currently doing: # Exposing the root-owned docker layers, the "ro" option seems to have no impact on later userns mounts. sudo mount -t shiftfs -o mark,ro /var/lib/docker/overlay2 /mnt # Creating a userns as uid 1000, then mounting the shiftfs. unshare -U -m -r cd $(mktemp -d) mkdir shiftfs upper work merged # I can pass "ro" to the mount to get the behavior I want. mount -t shiftfs -o ro /mnt shiftfs mount -t overlay overlay -o 'lowerdir=shiftfs/c34c048514dcab5fc1bddf6d99681645786021e4a5b239972ec688386852a666/diff:[...],upperdir=upper,workdir=work' merged This works fine (excluding the xattrs issue with unprivileged overlay), but I can't rely on users to pass the "ro" option to their mounts. Without it, any user would be able to write to /var/lib/docker/overlay2 through the shiftfs mountpoint. I couldn't find a way to enforce do that, is there one? Is it possible to have one? I quickly attempted to have root do the shiftfs mounts for the users, but it seems the shift is always for the root of the current userns, and can't be done for another user." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1827122/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828657] 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 1828657 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: 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/1828657 Title: Slow resume after lid close/open Status in linux package in Ubuntu: Incomplete Bug description: Summary 1.) Release Info: Description: Ubuntu 19.04 Release: 19.04 2.) Package version: linux-image-5.0.0-13-generic 3.) Expected behavior: Computer resumes shortly after opening lid. 4.) Actual behavior: Computer takes ~2 minutes to resume after opening lid. I have installed Ubuntu 19.04 (Disco Dingo) on my Lenovo Flex 6-11IGM. I found that when it resumes from sleep after opening the lid, it takes a long time to resume (~2 minutes). While experimenting with the upstream kernel releases, I found that the problem was introduced with version 5.0.5 version of the Linux kernel; the problem does not occur when I run version 5.0.4. I've narrowed the culprit down to the following commit in the upstream kernel: a57af6d07... ALSA: hda - Enforces runtime_resume after S3 and S4 for each codec This change was applied to the ubuntu kernel with commit 9c51afaceb61459d2becac8fb32c860bb084e643. The following messages appear in the system log upon resume with the released ubuntu kernel: May 05 20:22:11 brian-Lenovo-FLEX-6-11IGM kernel: snd_hda_intel :00:0e.0: azx_get_response timeout, switching to polling mode: last cmd=0x20bf8100 May 05 20:22:11 brian-Lenovo-FLEX-6-11IGM kernel: hid-sensor-hub 001F:8086:22D8.0003: timeout waiting for response from ISHTP device May 05 20:22:11 brian-Lenovo-FLEX-6-11IGM kernel: snd_hda_intel :00:0e.0: No response from codec, disabling MSI: last cmd=0x20bf8100 May 05 20:22:11 brian-Lenovo-FLEX-6-11IGM kernel: snd_hda_codec_hdmi hdaudioC0D2: Unable to sync register 0x2f0d00. -11 These messages do not appear in the system log upon resume when running with upstream kernel version 5.0.4. I have upgraded the system BIOS to the latest from Lenovo (6qcn47ww), but the problem persists. For now, I will run with the 5.0.4 version of the upstream kernel, as I am not experiencing any issues with it. Thank you. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1828657/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828763] Re: Cannot build kernel 4.15.0-48.51 due to an in-source-tree ZFS module.
Hyeonho, you're absolutely right, there's a typo in my previous patch.
Can you double check if this one is correct? Thanks again!
** Patch added: "zfs-fix-build-error-with-tracepoints-enabled-v2.patch"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1828763/+attachment/5263626/+files/zfs-fix-build-error-with-tracepoints-enabled-v2.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/1828763
Title:
Cannot build kernel 4.15.0-48.51 due to an in-source-tree ZFS module.
Status in linux package in Ubuntu:
Confirmed
Bug description:
I tried to build a kernel 4.15.0-48.51 that cloned from the Ubuntu
kernel git (x86_64-generic flavour).
commit c50532b9d7b623ff98aeaf0b848e58adae54ca75 (HEAD -> master, tag:
Ubuntu-4.15.0-48.51, origin/master, origin/HEAD)
Author: Andrea Righi
Date: Tue Apr 2 18:31:55 2019 +0200
UBUNTU: Ubuntu-4.15.0-48.51
Signed-off-by: Andrea Righi
1. Build a kernel image with 'zfs_enable' flag set as false.
2. Build SPL/ZFS modules independently by 'make' command (debug purpose;
DECLARE_EVENT_CLASS() enabled).
But 'make' was always failed at the same point,
'zfs/module/zfs/trace.c' (as seem as below).
In file included from /home/np/linux-4.15/include/trace/define_trace.h:96:0,
from /home/np/linux-4.15/zfs/include/sys/trace_dmu.h:127,
from /home/np/linux-4.15/zfs/module/zfs/trace.c:45:
/home/np/linux-4.15/zfs/include/sys/trace_dmu.h: In function
‘trace_event_raw_event_zfs_delay_mintime_class’:
/home/np/linux-4.15/zfs/include/sys/trace_dmu.h:65:37: error: ‘dmu_tx_t {aka
struct dmu_tx}’ has no member named ‘tx_dirty_delayed’
__entry->tx_dirty_delayed = tx->tx_dirty_delayed;
^
/home/np/linux-4.15/include/trace/trace_events.h:719:4: note: in definition
of macro ‘DECLARE_EVENT_CLASS’
{ assign; } \
^~
/home/np/linux-4.15/zfs/include/sys/trace_dmu.h:60:2: note: in expansion of
macro ‘TP_fast_assign’
TP_fast_assign(
^~
In file included from /home/np/linux-4.15/include/trace/define_trace.h:97:0,
from /home/np/linux-4.15/zfs/include/sys/trace_dmu.h:127,
from /home/np/linux-4.15/zfs/module/zfs/trace.c:45:
/home/np/linux-4.15/zfs/include/sys/trace_dmu.h: In function
‘perf_trace_zfs_delay_mintime_class’:
/home/np/linux-4.15/zfs/include/sys/trace_dmu.h:65:37: error: ‘dmu_tx_t {aka
struct dmu_tx}’ has no member named ‘tx_dirty_delayed’
__entry->tx_dirty_delayed = tx->tx_dirty_delayed;
^
/home/np/linux-4.15/include/trace/perf.h:66:4: note: in definition of macro
‘DECLARE_EVENT_CLASS’
{ assign; } \
^~
/home/np/linux-4.15/zfs/include/sys/trace_dmu.h:60:2: note: in expansion of
macro ‘TP_fast_assign’
TP_fast_assign(
^~
I tried to debug this issue with myself and found something intriguing.
In 'zfs/include/sys/trace_dmu.h', the failed code accessing
'tx_dirty_delayed' from 'dmu_tx_t' (which same as 'struct dmu_tx').
DECLARE_EVENT_CLASS(zfs_delay_mintime_class,
TP_PROTO(dmu_tx_t *tx, uint64_t dirty, uint64_t min_tx_time),
TP_ARGS(tx, dirty, min_tx_time),
TP_STRUCT__entry(
__field(uint64_t, tx_txg)
__field(uint64_t, tx_lastsnap_txg)
__field(uint64_t, tx_lasttried_txg)
__field(boolean_t, tx_anyobj)
__field(boolean_t, tx_dirty_delayed)
__field(hrtime_t, tx_start)
__field(boolean_t, tx_wait_dirty)
__field(int,tx_err)
__field(uint64_t, min_tx_time)
__field(uint64_t, dirty)
),
TP_fast_assign(
__entry->tx_txg = tx->tx_txg;
__entry->tx_lastsnap_txg= tx->tx_lastsnap_txg;
__entry->tx_lasttried_txg = tx->tx_lasttried_txg;
__entry->tx_anyobj = tx->tx_anyobj;
__entry->tx_dirty_delayed = tx->tx_dirty_delayed;
__entry->tx_start = tx->tx_start;
__entry->tx_wait_dirty = tx->tx_wait_dirty;
__entry->tx_err = tx->tx_err;
__entry->dirty = dirty;
__entry->min_tx_time= min_tx_time;
),
TP_printk("tx { txg %llu lastsnap_txg %llu tx_lasttried_txg %llu "
"anyobj %d dirty_delayed %d start %llu wait_dirty %d err %i "
"} dirty %llu min_tx_time %llu",
__entry->tx_txg, __entry->tx_la
[Kernel-packages] [Bug 1826410] Re: Please package libbpf (which is done out of the kernel src) in Debian [for 19.10]
** Changed in: linux (Ubuntu) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1826410 Title: Please package libbpf (which is done out of the kernel src) in Debian [for 19.10] Status in linux package in Ubuntu: Fix Committed Status in linux source package in Disco: Fix Committed Bug description: Hi, Debian packages libbpf and so far does so out of the kernel source [1]. There is some movement to separate that from the kernel source [2] but this isn't ready yet. So far it is just a sync of the subtree out of the kernel sources. Since we do not share our kernel packaging we will not get this for-free without doing anything. If there will be an ITP about it in Debian I'll let you know and we can abort this, but unless that really happens I wanted to ask if you could as well build the libbpf* packages for 19.10 and onward? Note: this is not the same bpf lib as [3] despite the similarity in names. Reasoning: BPF becomes more and more important in general and is used in the kernel for many things. In the case that brought it to my attention it will be a PMD of DPDK that will need it to control XDP [4]. And XDP in general is an interesting and rising feature for network acceleration - I'd think it would be helpful to have this package around in Ubuntu. [1]: https://packages.debian.org/sid/libbpf-dev [2]: https://github.com/libbpf/libbpf [3]: https://github.com/iovisor/bcc [4]: https://www.iovisor.org/technology/xdp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1826410/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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] Comment bridged from LTC Bugzilla
--- Comment From tmri...@de.ibm.com 2019-05-14 08:35 EDT--- I have debugged this issue Klaus reported. I have installed the following system: root@s8360046:~/linux/tools/perf# uname -a Linux s8360046 4.18.0-17-generic #18-Ubuntu SMP Wed Mar 13 14:29:38 UTC 2019 s390x s390x s390x GNU/Linux root@s8360046:~/linux/tools/perf# and ran into the issue Klaus reported by running command root@s8360046:~/ # perf top in one window and in another window running this command while perf top was running: root@s8360046:~/ # for i in $(seq 15); do find / >/dev/null 2>&1; echo $i; done The issue shows up pretty quickly. I then cloned the linux kernel tree and build the perf tool from the downloaded linux kernel in directory linux/tools/perf. I did the same test with the locally compiled perf tools and the issue did not show up. To me it looked like the latest version did not have this problem. Next bisected the linux kernel tree (which also includes the perf tool) and the bisecting process stopped at the mentioned commit. Thats how I arrived at the commit id stated im comment 4. Obviously it did not fix the issue otherwise the patch would work. Sorry for that. It looks like we are back to start again. PS: I'm not sure but I have the feeling the issue only shows up when the debuginfo packages for the kernel are not installed. -- You 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: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: In Progress 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 1828948] Re: OBSOLETE_BY in DKMS.CONF not work
** Changed in: oem-priority Assignee: (unassigned) => Alex Tu (alextu) ** Changed in: dkms Assignee: Alex Tu (alextu) => (unassigned) ** Changed in: dkms Importance: High => Undecided ** Changed in: oem-priority Importance: Undecided => High -- 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 not work Status in DKMS: Confirmed Status in OEM Priority Project: New Status in dkms package in Ubuntu: New Status in dkms source package in Bionic: New Bug description: the issue has been fixed by upstream [1]: https://github.com/dell/dkms/issues/81 we need to land that fix to DKMS on Ubuntu as well. [1] https://github.com/dell/dkms 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 1817321] Re: installer does not support iSCSI iBFT
** Description changed: [Impact] - * It's not possible to access iBFT (iSCSI Boot Firmware Table) information -(settings for network interface, initiator, and target) in the installer -because the 'iscsi_ibft' module is not present in udeb packages. + * It's not possible to access iBFT (iSCSI Boot Firmware Table) information + (settings for network interface, initiator, and target) in the installer + because the 'iscsi_ibft' module is not present in udeb packages. - * Even if it was, the installer does not handle iBFT information at all, -thus any settings are ignored, and iSCSI-related configuration has to -be done manually or with workarounds. + * Even if it was, the installer does not handle iBFT information at all, + thus any settings are ignored, and iSCSI-related configuration has to + be done manually or with workarounds. - * This impacts user-experience and automatic installation on systems and -deployments which actually do provide the iBFT feature and information, -but cannot use it practically. + * This impacts user-experience and automatic installation on systems and + deployments which actually do provide the iBFT feature and information, + but cannot use it practically. - * With proper iBFT support in the installer (kernel module in udeb package -and automatic iSCSI-related configuration) users will be able to rely on -iBFT to install/deploy Ubuntu on their servers and datacenters. + * With proper iBFT support in the installer (kernel module in udeb package + and automatic iSCSI-related configuration) users will be able to rely on + iBFT to install/deploy Ubuntu on their servers and datacenters. - * These fixes add the 'iscsi_ibft' kernel module in the scsi-modules udeb, -and configure network/iSCSI according to iBFT information in disk-detect. + * These fixes add the 'iscsi_ibft' kernel module in the scsi-modules udeb, + and configure network/iSCSI according to iBFT information in disk-detect. -This is done in disk-detect so that the iSCSI LUNs are detected as disks -(useful in case of no other disks in the system so the installer doesn't -complain nor wait too long) and that any partman-related preseed options -are not required and may be still available for the user. + This is done in disk-detect so that the iSCSI LUNs are detected as disks + (useful in case of no other disks in the system so the installer doesn't + complain nor wait too long) and that any partman-related preseed options + are not required and may be still available for the user. [Test Case] - * linux package / kernel module in udeb: + * linux package / kernel module in udeb: -$ dpkg-deb -c scsi-modules_*.udeb | grep iscsi_ibft.ko + $ dpkg-deb -c scsi-modules_*.udeb | grep iscsi_ibft.ko -Check the module loads in the installer environment. -See comment with example for disco. + Check the module loads in the installer environment. + See comment with example for disco. - * d-i/hw-detect package: -(to be done) + * d-i/hw-detect/partman-iscsi package: + (to be done) [Regression Potential] - * linux package: low, the kernel module is not loaded by default, -and only checks whether iBFT information is present in firmware, -then exposes that in sysfs in read-only mode. + * linux package: low, the kernel module is not loaded by default, + and only checks whether iBFT information is present in firmware, + then exposes that in sysfs in read-only mode. - * d-i/hw-detect: -(to be done) + * d-i/hw-detect/partman-iscsi: + (to be done) [Other Info] - - * This has been verified both by the developer with a simple iSCSI -iBFT environment (2 VMs: iSCSI target & initiator with UEFI+iPXE) -and by an user with system/firmware that supports iBFT for iSCSI. + + * This has been verified both by the developer with a simple iSCSI + iBFT environment (2 VMs: iSCSI target & initiator with UEFI+iPXE) + and by an user with system/firmware that supports iBFT for iSCSI. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1817321 Title: installer does not support iSCSI iBFT Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux source package in Disco: Fix Released Bug description: [Impact] * It's not possible to access iBFT (iSCSI Boot Firmware Table) information (settings for network interface, initiator, and target) in the installer because the 'iscsi_ibft' module is not present in udeb packages. * Even if it was, the installer does not handle iBFT information at all, thus any settings are ignored, and iSCSI-related configuration has to be done manually or with wor
[Kernel-packages] [Bug 1828657] Re: Slow resume after lid close/open
** 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/1828657 Title: Slow resume after lid close/open Status in linux package in Ubuntu: Confirmed Bug description: Summary 1.) Release Info: Description: Ubuntu 19.04 Release: 19.04 2.) Package version: linux-image-5.0.0-13-generic 3.) Expected behavior: Computer resumes shortly after opening lid. 4.) Actual behavior: Computer takes ~2 minutes to resume after opening lid. I have installed Ubuntu 19.04 (Disco Dingo) on my Lenovo Flex 6-11IGM. I found that when it resumes from sleep after opening the lid, it takes a long time to resume (~2 minutes). While experimenting with the upstream kernel releases, I found that the problem was introduced with version 5.0.5 version of the Linux kernel; the problem does not occur when I run version 5.0.4. I've narrowed the culprit down to the following commit in the upstream kernel: a57af6d07... ALSA: hda - Enforces runtime_resume after S3 and S4 for each codec This change was applied to the ubuntu kernel with commit 9c51afaceb61459d2becac8fb32c860bb084e643. The following messages appear in the system log upon resume with the released ubuntu kernel: May 05 20:22:11 brian-Lenovo-FLEX-6-11IGM kernel: snd_hda_intel :00:0e.0: azx_get_response timeout, switching to polling mode: last cmd=0x20bf8100 May 05 20:22:11 brian-Lenovo-FLEX-6-11IGM kernel: hid-sensor-hub 001F:8086:22D8.0003: timeout waiting for response from ISHTP device May 05 20:22:11 brian-Lenovo-FLEX-6-11IGM kernel: snd_hda_intel :00:0e.0: No response from codec, disabling MSI: last cmd=0x20bf8100 May 05 20:22:11 brian-Lenovo-FLEX-6-11IGM kernel: snd_hda_codec_hdmi hdaudioC0D2: Unable to sync register 0x2f0d00. -11 These messages do not appear in the system log upon resume when running with upstream kernel version 5.0.4. I have upgraded the system BIOS to the latest from Lenovo (6qcn47ww), but the problem persists. For now, I will run with the 5.0.4 version of the upstream kernel, as I am not experiencing any issues with it. Thank you. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1828657/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1827122] Re: shiftfs: lock security sensitive superblock flags
** Changed in: linux (Ubuntu Disco) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1827122 Title: shiftfs: lock security sensitive superblock flags Status in linux package in Ubuntu: Fix Committed Status in linux source package in Disco: Fix Committed Bug description: Felix Abecassis from Nvidia recently reported the following bug: "I recently upgraded to Ubuntu 19.04, and decided to experiment with shiftfs and unprivileged overlay. My goal was to have root (in my case, the docker daemon) download overlay layers and then have multiple users leveraging shiftfs + unprivileged overlay to assemble the rootfs without copying and chowning. For obvious security reasons, I want root to expose these layers as read-only, any change will be to the user-owned "upper" filesystem. Here's what I'm currently doing: # Exposing the root-owned docker layers, the "ro" option seems to have no impact on later userns mounts. sudo mount -t shiftfs -o mark,ro /var/lib/docker/overlay2 /mnt # Creating a userns as uid 1000, then mounting the shiftfs. unshare -U -m -r cd $(mktemp -d) mkdir shiftfs upper work merged # I can pass "ro" to the mount to get the behavior I want. mount -t shiftfs -o ro /mnt shiftfs mount -t overlay overlay -o 'lowerdir=shiftfs/c34c048514dcab5fc1bddf6d99681645786021e4a5b239972ec688386852a666/diff:[...],upperdir=upper,workdir=work' merged This works fine (excluding the xattrs issue with unprivileged overlay), but I can't rely on users to pass the "ro" option to their mounts. Without it, any user would be able to write to /var/lib/docker/overlay2 through the shiftfs mountpoint. I couldn't find a way to enforce do that, is there one? Is it possible to have one? I quickly attempted to have root do the shiftfs mounts for the users, but it seems the shift is always for the root of the current userns, and can't be done for another user." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1827122/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1814373] Re: storage / luks / dmsetup regressed (or got better) on ppc64le
** Changed in: udisks2 (Ubuntu Bionic) Status: New => Invalid ** Changed in: udisks2 (Ubuntu Disco) Status: New => Invalid ** Changed in: udisks2 (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/1814373 Title: storage / luks / dmsetup regressed (or got better) on ppc64le Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Status in udisks2 package in Ubuntu: Invalid Status in linux source package in Bionic: New Status in systemd source package in Bionic: New Status in udisks2 source package in Bionic: Invalid Status in linux source package in Disco: New Status in systemd source package in Disco: New Status in udisks2 source package in Disco: Invalid Status in linux source package in Eoan: Confirmed Status in systemd source package in Eoan: New Status in udisks2 source package in Eoan: Invalid Bug description: in disco proposed with new systemd and v4.19 kernel it appears that dmsetup / cryptsetup storage either got better or worse. Devices take very long to activate, and sometimes remain in use during test clean up. This leads to udisks autopkgtest failing on ppc64le and systemd's "storage" autopkgtest is also failing. I've tried to make ppc64le test more resilient, but it's still odd that it became unstable in disco, and used to be rock solid on ppc64le. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814373/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1796292] Re: Tight timeout for bcache removal causes spurious failures
This script *should* trigger the issue on Bionic GA:
https://pastebin.ubuntu.com/p/WdKGbMWnM6/
Try it with both GA and HWE bionic, the commit on HWE should trigger up.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1796292
Title:
Tight timeout for bcache removal causes spurious failures
Status in curtin:
New
Status in linux package in Ubuntu:
Confirmed
Bug description:
I've had a number of deployment faults where curtin would report
Timeout exceeded for removal of /sys/fs/bcache/xxx when doing a mass-
deployment of 30+ nodes. Upon retrying the node would usually deploy
fine. Experimentally I've set the timeout ridiculously high, and it
seems I'm getting no faults with this. I'm wondering if the timeout
for removal is set too tight, or might need to be made configurable.
--- curtin/util.py~ 2018-05-18 18:40:48.0 +
+++ curtin/util.py 2018-10-05 09:40:06.807390367 +
@@ -263,7 +263,7 @@
return _subp(*args, **kwargs)
-def wait_for_removal(path, retries=[1, 3, 5, 7]):
+def wait_for_removal(path, retries=[1, 3, 5, 7, 1200, 1200]):
if not path:
raise ValueError('wait_for_removal: missing path parameter')
To manage notifications about this bug go to:
https://bugs.launchpad.net/curtin/+bug/1796292/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1823753] Re: arm64: cma_alloc errors at boot
The hisi_sas maintainer is experimenting with a patch that will change the driver's 33 page allocations to single page allocations. If there is no significant performance impact, that could be a way forward to deal with the fragmentation issue costing us up to 31M of CMA. In addition, there is DMA/CMA optimization making its way upstream, that uses non-CMA memory for single page requests: https://lkml.org/lkml/2019/5/6/1219 This avoids the impact of the CMA memory usage increase in the RDMA/hns driver (see comment #11) and - with the aforementioned hisi_sas patch - those allocations as well. After those optimizations, I am able to fulfill all cma allocation requests from our D06 CS board[*] with cma=64M. However, Ubuntu ships with only 16M of CMA. Note that upstream's defconfig allocates 32M of CMA, which is apparently required for the RPi VC4: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ebf089248dab2ef569e5e26a607f0977a71182b7 So there maybe other reasons we want to bump to at least 32M - I'm not sure that we'd want to go all the way to 64M for general purpose kernel though. [*] Keeping in mind that this is just tuning for a specific system/config. Throw in a bunch of mlx5 cards, and I suspect we'll still see cma_alloc log spew on this platform. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1823753 Title: arm64: cma_alloc errors at boot Status in linux package in Ubuntu: Confirmed Bug description: On some arm64 systems[*] we are seeing a spew of messages on the console: [ 19.534097] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12 [ 19.534109] cma: cma_alloc: alloc failed, req-size: 16 pages, ret: -12 [ 19.534113] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12 [ 19.534126] cma: cma_alloc: alloc failed, req-size: 16 pages, ret: -12 [ 19.534130] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12 [ 19.534142] cma: cma_alloc: alloc failed, req-size: 16 pages, ret: -12 [ 19.534146] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12 [ 19.534157] cma: cma_alloc: alloc failed, req-size: 16 pages, ret: -12 [ 19.534161] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12 [ 19.534173] cma: cma_alloc: alloc failed, req-size: 16 pages, ret: -12 [ 19.534177] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12 This appears to be non-fatal - impacted systems all eventually boot. But, at least in the case of the HP m400, it slows down boot enough that MAAS' default timeout will expire before completing deployment. [*] Observed on a HiSilicon D06 w/ SMMU disabled in the BIOS, as well as an HP m400 (APM X-Gene) cartridge - although, not on another one that - in theory - should be identical. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823753/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828248] Re: [linux-azure] Storage performance drop on RAID
@marcelo, we do want the changes requested in comment #5 in bug 1819689. We can wait for the results of Long Li's investigation before proceeding there. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1828248 Title: [linux-azure] Storage performance drop on RAID Status in linux-azure package in Ubuntu: New Status in linux-azure source package in Xenial: Fix Committed Bug description: In Azure, FIO 4k tests are showing performance drops on latest proposed 4.15.0 linux-azure kernels - from 52K IOPS to ~38K IOPS (max value reached on both sequential and random read tests). The setup used is 12 disks in RAID0. The affected kernels are: Ubuntu 14.04 + 4.15.0-1043 Ubuntu 16.04 + 4.15.0-1044 Previous kernel versions had reached max IOPS, ~52K IOPS on both read tests (e.g. 16.04 + 4.15.0-1043 kernel). Right now, it seems like the issue is in the diff from 1043 kernel on trusty vs 1044 kernel on xenial. The 52K IOPS is expected at qdepth=256. The repro cmd (as ran by the automation) is this: fio --size=1023G --direct=1 --ioengine=libaio --filename=/dev/md0 --overwrite=1 --readwrite=randread --bs=4K --runtime=300 --iodepth=32 --numjob=8 --output-format=json --output=/root/FIOLog/jsonLog/fio-result-randread-4K-256td.json --name='repro' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1828248/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828248] Re: [linux-azure] Storage performance drop on RAID
Thanks for the feedback, @jsalisbury. So we are proceeding with the revert for now. Later when Long Li's investigation is ready, can you open a new bug listing the remaining commits that need to be included? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1828248 Title: [linux-azure] Storage performance drop on RAID Status in linux-azure package in Ubuntu: New Status in linux-azure source package in Xenial: Fix Committed Bug description: In Azure, FIO 4k tests are showing performance drops on latest proposed 4.15.0 linux-azure kernels - from 52K IOPS to ~38K IOPS (max value reached on both sequential and random read tests). The setup used is 12 disks in RAID0. The affected kernels are: Ubuntu 14.04 + 4.15.0-1043 Ubuntu 16.04 + 4.15.0-1044 Previous kernel versions had reached max IOPS, ~52K IOPS on both read tests (e.g. 16.04 + 4.15.0-1043 kernel). Right now, it seems like the issue is in the diff from 1043 kernel on trusty vs 1044 kernel on xenial. The 52K IOPS is expected at qdepth=256. The repro cmd (as ran by the automation) is this: fio --size=1023G --direct=1 --ioengine=libaio --filename=/dev/md0 --overwrite=1 --readwrite=randread --bs=4K --runtime=300 --iodepth=32 --numjob=8 --output-format=json --output=/root/FIOLog/jsonLog/fio-result-randread-4K-256td.json --name='repro' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1828248/+subscriptions -- Mailing list: https://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 1828248] Re: [linux-azure] Storage performance drop on RAID
Morning Joe, On 5/14/19 8:40 AM, Joseph Salisbury wrote: > @marcelo, we do want the changes requested in comment #5 in bug 1819689. > We can wait for the results of Long Li's investigation before proceeding > there. > that is the revert in comment #6, right? Terry -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1828248 Title: [linux-azure] Storage performance drop on RAID Status in linux-azure package in Ubuntu: New Status in linux-azure source package in Xenial: Fix Committed Bug description: In Azure, FIO 4k tests are showing performance drops on latest proposed 4.15.0 linux-azure kernels - from 52K IOPS to ~38K IOPS (max value reached on both sequential and random read tests). The setup used is 12 disks in RAID0. The affected kernels are: Ubuntu 14.04 + 4.15.0-1043 Ubuntu 16.04 + 4.15.0-1044 Previous kernel versions had reached max IOPS, ~52K IOPS on both read tests (e.g. 16.04 + 4.15.0-1043 kernel). Right now, it seems like the issue is in the diff from 1043 kernel on trusty vs 1044 kernel on xenial. The 52K IOPS is expected at qdepth=256. The repro cmd (as ran by the automation) is this: fio --size=1023G --direct=1 --ioengine=libaio --filename=/dev/md0 --overwrite=1 --readwrite=randread --bs=4K --runtime=300 --iodepth=32 --numjob=8 --output-format=json --output=/root/FIOLog/jsonLog/fio-result-randread-4K-256td.json --name='repro' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1828248/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1816669] Re: AMD Rome : Minimal support patches
Per comment #17 Kim, can you please indicate exactly which kernel you want these commits in? Terry -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1816669 Title: AMD Rome : Minimal support patches Status in amd: New Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: New Status in linux source package in Cosmic: Fix Committed Bug description: The following 3 patches need to be back ported to ubuntu 18.04.2(Linux 4.18) to complete the minimal support for Rome : 818b7587b4d3 x86: irq_remapping: Move irq remapping mode enum e881dbd5d4a6 iommu/amd: Add support for higher 64-bit IOMMU Control Register 90fcffd9cf5e iommu/amd: Add support for IOMMU XT mode --thanks --kim --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-02-28 (5 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IwConfig: enp33s0f0 no wireless extensions. lono wireless extensions. enp33s0f1 no wireless extensions. MachineType: AMD Corporation DAYTONA_X Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-15-generic root=UUID=6500165b-63c3-4a3e-bbee-ca9f43bb1784 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-15-generic N/A linux-backports-modules-4.18.0-15-generic N/A linux-firmware 1.173.3 RfKill: Tags: bionic Uname: Linux 4.18.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/18/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: RDY0071B dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DAYTONA_X dmi.board.vendor: AMD Corporation dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 2 dmi.chassis.vendor: To be filled by O.E.M. dmi.chassis.version: To be filled by O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrRDY0071B:bd01/18/2019:svnAMDCorporation:pnDAYTONA_X:pvrTobefilledbyO.E.M.:rvnAMDCorporation:rnDAYTONA_X:rvrTobefilledbyO.E.M.:cvnTobefilledbyO.E.M.:ct2:cvrTobefilledbyO.E.M.: dmi.product.family: Default string dmi.product.name: DAYTONA_X dmi.product.sku: Default string dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: AMD Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1816669/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828248] Re: [linux-azure] Storage performance drop on RAID
Yes, that is correct. Comment #6. Sorry for the typo. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1828248 Title: [linux-azure] Storage performance drop on RAID Status in linux-azure package in Ubuntu: New Status in linux-azure source package in Xenial: Fix Committed Bug description: In Azure, FIO 4k tests are showing performance drops on latest proposed 4.15.0 linux-azure kernels - from 52K IOPS to ~38K IOPS (max value reached on both sequential and random read tests). The setup used is 12 disks in RAID0. The affected kernels are: Ubuntu 14.04 + 4.15.0-1043 Ubuntu 16.04 + 4.15.0-1044 Previous kernel versions had reached max IOPS, ~52K IOPS on both read tests (e.g. 16.04 + 4.15.0-1043 kernel). Right now, it seems like the issue is in the diff from 1043 kernel on trusty vs 1044 kernel on xenial. The 52K IOPS is expected at qdepth=256. The repro cmd (as ran by the automation) is this: fio --size=1023G --direct=1 --ioengine=libaio --filename=/dev/md0 --overwrite=1 --readwrite=randread --bs=4K --runtime=300 --iodepth=32 --numjob=8 --output-format=json --output=/root/FIOLog/jsonLog/fio-result-randread-4K-256td.json --name='repro' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1828248/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1825942] Re: kernel crash : net_sched race condition in tcindex_destroy()
** Changed in: linux (Ubuntu) Assignee: (unassigned) => Andrea Righi (arighi) ** Changed in: linux (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1825942 Title: kernel crash : net_sched race condition in tcindex_destroy() Status in linux package in Ubuntu: Confirmed Bug description: I am running into a kernel crash issue using latest Ubuntu 4.15 kernel. It does not appear to have been fixed in Ubuntu-4.15.0-48.51. This crash has also been reported for debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921542 The kernel crash issue was fixed in February in the Linux kernel: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=056a17982adbd52b2a6c5ec6266cee4521cd931b I did test one of the recent kernel-ppa/mainline kernels, more specifically: linux-image-unsigned-4.19.34-041934-generic_4.19.34-041934.201904051741_amd64.deb It seems to fix the problem, that is, no crashes experienced so far. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825942/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1816669] Re: AMD Rome : Minimal support patches
Terry, We need the patches to be in the 4.15 kernel. --kim -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1816669 Title: AMD Rome : Minimal support patches Status in amd: New Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: New Status in linux source package in Cosmic: Fix Committed Bug description: The following 3 patches need to be back ported to ubuntu 18.04.2(Linux 4.18) to complete the minimal support for Rome : 818b7587b4d3 x86: irq_remapping: Move irq remapping mode enum e881dbd5d4a6 iommu/amd: Add support for higher 64-bit IOMMU Control Register 90fcffd9cf5e iommu/amd: Add support for IOMMU XT mode --thanks --kim --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-02-28 (5 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IwConfig: enp33s0f0 no wireless extensions. lono wireless extensions. enp33s0f1 no wireless extensions. MachineType: AMD Corporation DAYTONA_X Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-15-generic root=UUID=6500165b-63c3-4a3e-bbee-ca9f43bb1784 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-15-generic N/A linux-backports-modules-4.18.0-15-generic N/A linux-firmware 1.173.3 RfKill: Tags: bionic Uname: Linux 4.18.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/18/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: RDY0071B dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DAYTONA_X dmi.board.vendor: AMD Corporation dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 2 dmi.chassis.vendor: To be filled by O.E.M. dmi.chassis.version: To be filled by O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrRDY0071B:bd01/18/2019:svnAMDCorporation:pnDAYTONA_X:pvrTobefilledbyO.E.M.:rvnAMDCorporation:rnDAYTONA_X:rvrTobefilledbyO.E.M.:cvnTobefilledbyO.E.M.:ct2:cvrTobefilledbyO.E.M.: dmi.product.family: Default string dmi.product.name: DAYTONA_X dmi.product.sku: Default string dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: AMD Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1816669/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1825942] Re: kernel crash : net_sched race condition in tcindex_destroy()
** Tags added: bionic 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/1825942 Title: kernel crash : net_sched race condition in tcindex_destroy() Status in linux package in Ubuntu: Confirmed Bug description: I am running into a kernel crash issue using latest Ubuntu 4.15 kernel. It does not appear to have been fixed in Ubuntu-4.15.0-48.51. This crash has also been reported for debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921542 The kernel crash issue was fixed in February in the Linux kernel: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=056a17982adbd52b2a6c5ec6266cee4521cd931b I did test one of the recent kernel-ppa/mainline kernels, more specifically: linux-image-unsigned-4.19.34-041934-generic_4.19.34-041934.201904051741_amd64.deb It seems to fix the problem, that is, no crashes experienced so far. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825942/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829046] [NEW] Eoan update: v5.1.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.1.1 upstream stable release from git://git.kernel.org/ Drivers: hv: vmbus: Remove the undesired put_cpu_ptr() in hv_synic_cleanup() ubsan: Fix nasty -Wbuiltin-declaration-mismatch GCC-9 warnings staging: greybus: power_supply: fix prop-descriptor request size staging: wilc1000: Avoid GFP_KERNEL allocation from atomic context. staging: most: cdev: fix chrdev_region leak in mod_exit staging: most: sound: pass correct device when creating a sound card usb: dwc3: Allow building USB_DWC3_QCOM without EXTCON usb: dwc3: Fix default lpm_nyet_threshold value USB: serial: f81232: fix interrupt worker not stop USB: cdc-acm: fix unthrottle races usb-storage: Set virt_boundary_mask to avoid SG overflows genirq: Prevent use-after-free and work list corruption intel_th: pci: Add Comet Lake support iio: adc: qcom-spmi-adc5: Fix of-based module autoloading cpufreq: armada-37xx: fix frequency calculation for opp ACPI / LPSS: Use acpi_lpss_* instead of acpi_subsys_* functions for hibernate soc: sunxi: Fix missing dependency on REGMAP_MMIO scsi: lpfc: change snprintf to scnprintf for possible overflow scsi: qla2xxx: Fix incorrect region-size setting in optrom SYSFS routines scsi: qla2xxx: Set remote port devloss timeout to 0 scsi: qla2xxx: Fix device staying in blocked state Bluetooth: hidp: fix buffer overflow Bluetooth: Align minimum encryption key size for LE and BR/EDR connections Bluetooth: Fix not initializing L2CAP tx_credits Bluetooth: hci_bcm: Fix empty regulator supplies for Intel Macs UAS: fix alignment of scatter/gather segments ASoC: Intel: avoid Oops if DMA setup fails i3c: Fix a shift wrap bug in i3c_bus_set_addr_slot_status() locking/futex: Allow low-level atomic operations to return -EAGAIN arm64: futex: Bound number of LDXR/STXR loops in FUTEX_WAKE_OP Linux 5.1.1 ** 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) ** 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: + v5.1.1 upstream stable release + from git://git.kernel.org/ -v5.1.1 upstream stable release -from git://git.kernel.org/ + Drivers: hv: vmbus: Remove the undesired put_cpu_ptr() in hv_synic_cleanup() + ubsan: Fix nasty -Wbuiltin-declaration-mismatch GCC-9 warnings + staging: greybus: power_supply: fix prop-descriptor request size + staging: wilc1000: Avoid GFP_KERNEL allocation from atomic context. + staging: most: cdev: fix chrdev_region leak in mod_exit + staging: most: sound: pass correct device when creating a sound card + usb: dwc3: Allow building USB_DWC3_QCOM without EXTCON + usb: dwc3: Fix default lpm_nyet_threshold value + USB: serial: f81232: fix interrupt worker not stop + USB: cdc-acm: fix unthrottle races + usb-storage: Set virt_boundary_mask to avoid SG overflows + genirq: Prevent use-after-free and work list corruption + intel_th: pci: Add Comet Lake support + iio: adc: qcom-spmi-adc5: Fix of-based module autoloading + cpufreq: armada-37xx: fix frequency calculation for opp + ACPI /
[Kernel-packages] [Bug 1829046] Re: Eoan update: v5.1.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/1829046 Title: Eoan update: v5.1.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.1.1 upstream stable release from git://git.kernel.org/ Drivers: hv: vmbus: Remove the undesired put_cpu_ptr() in hv_synic_cleanup() ubsan: Fix nasty -Wbuiltin-declaration-mismatch GCC-9 warnings staging: greybus: power_supply: fix prop-descriptor request size staging: wilc1000: Avoid GFP_KERNEL allocation from atomic context. staging: most: cdev: fix chrdev_region leak in mod_exit staging: most: sound: pass correct device when creating a sound card usb: dwc3: Allow building USB_DWC3_QCOM without EXTCON usb: dwc3: Fix default lpm_nyet_threshold value USB: serial: f81232: fix interrupt worker not stop USB: cdc-acm: fix unthrottle races usb-storage: Set virt_boundary_mask to avoid SG overflows genirq: Prevent use-after-free and work list corruption intel_th: pci: Add Comet Lake support iio: adc: qcom-spmi-adc5: Fix of-based module autoloading cpufreq: armada-37xx: fix frequency calculation for opp ACPI / LPSS: Use acpi_lpss_* instead of acpi_subsys_* functions for hibernate soc: sunxi: Fix missing dependency on REGMAP_MMIO scsi: lpfc: change snprintf to scnprintf for possible overflow scsi: qla2xxx: Fix incorrect region-size setting in optrom SYSFS routines scsi: qla2xxx: Set remote port devloss timeout to 0 scsi: qla2xxx: Fix device staying in blocked state Bluetooth: hidp: fix buffer overflow Bluetooth: Align minimum encryption key size for LE and BR/EDR connections Bluetooth: Fix not initializing L2CAP tx_credits Bluetooth: hci_bcm: Fix empty regulator supplies for Intel Macs UAS: fix alignment of scatter/gather segments ASoC: Intel: avoid Oops if DMA setup fails i3c: Fix a shift wrap bug in i3c_bus_set_addr_slot_status() locking/futex: Allow low-level atomic operations to return -EAGAIN arm64: futex: Bound number of LDXR/STXR loops in FUTEX_WAKE_OP Linux 5.1.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829046/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829050] [NEW] Eoan update: v5.1.2 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.1.2 upstream stable release from git://git.kernel.org/ Linux 5.1.2 x86/speculation/mds: Fix documentation typo Documentation: Correct the possible MDS sysfs values x86/mds: Add MDSUM variant to the MDS documentation x86/speculation/mds: Add 'mitigations=' support for MDS s390/speculation: Support 'mitigations=' cmdline option powerpc/speculation: Support 'mitigations=' cmdline option x86/speculation: Support 'mitigations=' cmdline option cpu/speculation: Add 'mitigations=' cmdline option x86/speculation/mds: Print SMT vulnerable on MSBDS with mitigations off x86/speculation/mds: Fix comment x86/speculation/mds: Add SMT warning message x86/speculation: Move arch_smt_update() call to after mitigation decisions x86/speculation/mds: Add mds=full,nosmt cmdline option Documentation: Add MDS vulnerability documentation Documentation: Move L1TF to separate directory x86/speculation/mds: Add mitigation mode VMWERV x86/speculation/mds: Add sysfs reporting for MDS x86/speculation/mds: Add mitigation control for MDS x86/speculation/mds: Conditionally clear CPU buffers on idle entry x86/kvm/vmx: Add MDS protection when L1D Flush is not active x86/speculation/mds: Clear CPU buffers on exit to user x86/speculation/mds: Add mds_clear_cpu_buffers() x86/kvm: Expose X86_FEATURE_MD_CLEAR to guests x86/speculation/mds: Add BUG_MSBDS_ONLY x86/speculation/mds: Add basic bug infrastructure for MDS x86/speculation: Consolidate CPU whitelists x86/msr-index: Cleanup bit defines ** Affects: linux (Ubuntu) Importance: Undecided Status: Fix Committed ** Affects: linux (Ubuntu Eoan) Importance: Undecided Status: Fix Committed ** 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) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1829050 Title: Eoan update: v5.1.2 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.1.2 upstream stable release from git://git.kernel.org/ Linux 5.1.2 x86/speculation/mds: Fix documentation typo Documentation: Correct the possible MDS sysfs values x86/mds: Add MDSUM variant to the MDS documentation x86/speculation/mds: Add 'mitigations=' support for MDS s390/speculation: Support 'mitigations=' cmdline option powerpc/speculation: Support 'mitigations=' cmdline option x86/speculation: Support 'mitigations=' cmdline option cpu/speculation: Add 'mitigations=' cmdline option x86/speculation/mds: Print SMT vulnerable on MSBDS with mitigations off x86/speculation/mds: Fix comment x86/speculation/mds: Add SMT warning message x86/speculation: Move arch_smt_update() call to after mitigation decisions x86/speculation/mds: Add mds=full,nosmt cmdline option Documentation: Add MDS vulnerability documentation Documentation: Move L1TF to separate directory x86/speculation/mds: Add mitigation mode VMWERV x86/speculation/mds: Add sysfs reporting for MDS x86/speculation/mds: Add mitigation control for MDS x86/speculation/mds: Conditionally clear CPU buffers on idle entry x86/kvm/vmx: Add MDS protection when L1D Flush is not active x86/speculation/mds: Clear CPU buffers on exit to user x86/speculation/mds: Add mds_clear_cpu_buffers() x86/kvm: Expose X86_FEATURE_MD_CLEAR to guests x86/speculation/mds: Add BUG_MSBDS_ONLY x86/speculation/mds: Add basic bug infrastructure for MDS x86/speculation: Consolidate CPU whitelists x86/msr-index: Cleanup bit defines To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829050/+subscriptions -- Mailing list: https
[Kernel-packages] [Bug 1816669] Re: AMD Rome : Minimal support patches
Kim, this works is staged for the next SRU cycle. Terry -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1816669 Title: AMD Rome : Minimal support patches Status in amd: New Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: New Status in linux source package in Cosmic: Fix Committed Bug description: The following 3 patches need to be back ported to ubuntu 18.04.2(Linux 4.18) to complete the minimal support for Rome : 818b7587b4d3 x86: irq_remapping: Move irq remapping mode enum e881dbd5d4a6 iommu/amd: Add support for higher 64-bit IOMMU Control Register 90fcffd9cf5e iommu/amd: Add support for IOMMU XT mode --thanks --kim --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-02-28 (5 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IwConfig: enp33s0f0 no wireless extensions. lono wireless extensions. enp33s0f1 no wireless extensions. MachineType: AMD Corporation DAYTONA_X Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-15-generic root=UUID=6500165b-63c3-4a3e-bbee-ca9f43bb1784 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-15-generic N/A linux-backports-modules-4.18.0-15-generic N/A linux-firmware 1.173.3 RfKill: Tags: bionic Uname: Linux 4.18.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/18/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: RDY0071B dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DAYTONA_X dmi.board.vendor: AMD Corporation dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 2 dmi.chassis.vendor: To be filled by O.E.M. dmi.chassis.version: To be filled by O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrRDY0071B:bd01/18/2019:svnAMDCorporation:pnDAYTONA_X:pvrTobefilledbyO.E.M.:rvnAMDCorporation:rnDAYTONA_X:rvrTobefilledbyO.E.M.:cvnTobefilledbyO.E.M.:ct2:cvrTobefilledbyO.E.M.: dmi.product.family: Default string dmi.product.name: DAYTONA_X dmi.product.sku: Default string dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: AMD Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1816669/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1826358] Re: linux: 4.15.0-49.53 -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 backports: bug 1826354 (xenial/linux-azure), bug 1826357 (xenial/linux-hwe) derivatives: bug 1826334 (linux-raspi2), bug 1826335 (linux-snapdragon), bug 1826336 (linux-oem), bug 1826338 (linux-aws), bug 1826340 (linux-gcp), bug 1826342 (linux-gke-4.15), bug 1826343 (linux-kvm), bug 1826345 (linux-ibm-gt), bug 1826348 (linux-oracle), bug 1826350 (linux-fips), bug 1827353 (linux) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Holding before Release phase-changed: Monday, 13. May 2019 10:02 UTC proposed-announcement-sent: true proposed-testing-requested: true - reason: - promote-to-updates: Holding -- kernel-block/kernel-block-proposed tag present -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1826358 Title: linux: 4.15.0-49.53 -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: 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-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow snap-certification-testing series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Fix Released Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow verification-testing series: Fix Released 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 backports: bug 1826354 (xenial/linux-azure), bug 1826357 (xenial/linux-hwe) derivatives: bug 1826334 (linux-raspi2), bug 1826335 (linux-snapdragon), bug 1826336 (linux-oem), bug 1826338 (linux-aws), bug 1826340 (linux-gcp), bug 1826342 (linux-gke-4.15), bug 1826343 (linux-kvm), bug 1826345 (linux-ibm-gt), bug 1826348 (linux-oracle), bug 1826350 (linux-fips), bug 1827353 (linux) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Holding before Release phase-changed: Monday, 13. May 2019 10:02 UTC proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1826358/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1826171] Re: linux: 4.18.0-19.20 -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 backports: bug 1826170 (bionic/linux-hwe) derivatives: bug 1826160 (linux-raspi2), bug 1826163 (linux-aws), bug 1826166 (linux-azure), bug 1826168 (linux-gcp), bug 1826169 (linux-kvm) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Holding before Release phase-changed: Monday, 13. May 2019 10:01 UTC proposed-announcement-sent: true proposed-testing-requested: true - reason: - promote-to-updates: Holding -- kernel-block/kernel-block-proposed tag present -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1826171 Title: linux: 4.18.0-19.20 -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: 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-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Cosmic: 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 1826170 (bionic/linux-hwe) derivatives: bug 1826160 (linux-raspi2), bug 1826163 (linux-aws), bug 1826166 (linux-azure), bug 1826168 (linux-gcp), bug 1826169 (linux-kvm) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Holding before Release phase-changed: Monday, 13. May 2019 10:01 UTC proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1826171/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1826028] Re: linux-kvm: 4.4.0-1045.51 -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: 1826036 phase: Holding before Release phase-changed: Monday, 13. May 2019 05:03 UTC proposed-announcement-sent: true proposed-testing-requested: true - reason: - promote-to-updates: Holding -- master bug not ready for release -- 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/1826028 Title: linux-kvm: 4.4.0-1045.51 -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: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm 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: 1826036 phase: Holding before Release phase-changed: Monday, 13. May 2019 05:03 UTC proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1826028/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1826024] Re: linux-aws: 4.4.0-1082.92 -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: 1826036 phase: Holding before Release phase-changed: Monday, 13. May 2019 05:03 UTC proposed-announcement-sent: true proposed-testing-requested: true - reason: - promote-to-updates: Holding -- master bug not ready for release -- 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/1826024 Title: linux-aws: 4.4.0-1082.92 -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: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Fix Released Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-aws package in Ubuntu: Invalid Status in linux-aws 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: 1826036 phase: Holding before Release phase-changed: Monday, 13. May 2019 05:03 UTC proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1826024/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1826150] Re: linux: 5.0.0-14.15 -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 backports: bug 1826147 (bionic/linux-hwe-edge), bug 1827847 (bionic/linux-oem-osp1) derivatives: bug 1826139 (linux-raspi2), bug 1826141 (linux-aws), bug 1826143 (linux-azure), bug 1826144 (linux-gcp), bug 1826145 (linux-kvm), bug 1826146 (linux-snapdragon) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Holding before Release phase-changed: Monday, 13. May 2019 05:01 UTC proposed-announcement-sent: true proposed-testing-requested: true - reason: - promote-to-updates: Holding -- kernel-block/kernel-block-proposed tag present -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1826150 Title: linux: 5.0.0-14.15 -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: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux 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 1826147 (bionic/linux-hwe-edge), bug 1827847 (bionic/linux-oem-osp1) derivatives: bug 1826139 (linux-raspi2), bug 1826141 (linux-aws), bug 1826143 (linux-azure), bug 1826144 (linux-gcp), bug 1826145 (linux-kvm), bug 1826146 (linux-snapdragon) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Holding before Release phase-changed: Monday, 13. May 2019 05:01 UTC proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1826150/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1826036] Re: linux: 4.4.0-147.173 -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 backports: bug 1826034 (trusty/linux-aws), bug 1826035 (trusty/linux-lts-xenial) derivatives: bug 1826024 (linux-aws), bug 1826028 (linux-kvm), bug 1826029 (linux-raspi2), bug 1826030 (linux-snapdragon), bug 1826032 (linux-fips) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Holding before Release phase-changed: Monday, 13. May 2019 05:00 UTC proposed-announcement-sent: true proposed-testing-requested: true - reason: - promote-to-updates: Holding -- kernel-block/kernel-block-proposed tag present -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1826036 Title: linux: 4.4.0-147.173 -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: 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-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow snap-certification-testing series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Fix Released Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow verification-testing series: Fix Released 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 backports: bug 1826034 (trusty/linux-aws), bug 1826035 (trusty/linux-lts-xenial) derivatives: bug 1826024 (linux-aws), bug 1826028 (linux-kvm), bug 1826029 (linux-raspi2), bug 1826030 (linux-snapdragon), bug 1826032 (linux-fips) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Holding before Release phase-changed: Monday, 13. May 2019 05:00 UTC proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1826036/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1826030] Re: linux-snapdragon: 4.4.0-1112.117 -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: 1826036 phase: Holding before Release phase-changed: Monday, 13. May 2019 05:04 UTC proposed-announcement-sent: true proposed-testing-requested: true - reason: - promote-to-updates: Holding -- master bug not ready for release -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-snapdragon in Ubuntu. https://bugs.launchpad.net/bugs/1826030 Title: linux-snapdragon: 4.4.0-1112.117 -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: 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 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: Invalid Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow snap-certification-testing series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Fix Released Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-snapdragon package in Ubuntu: Invalid Status in linux-snapdragon 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: 1826036 phase: Holding before Release phase-changed: Monday, 13. May 2019 05:04 UTC proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1826030/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1826029] Re: linux-raspi2: 4.4.0-1108.116 -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: 1826036 phase: Holding before Release phase-changed: Monday, 13. May 2019 10:03 UTC proposed-announcement-sent: true proposed-testing-requested: true - reason: - promote-to-updates: Holding -- master bug not ready for release -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1826029 Title: linux-raspi2: 4.4.0-1108.116 -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: 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 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: Invalid Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow snap-certification-testing series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Fix Released Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 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: 1826036 phase: Holding before Release phase-changed: Monday, 13. May 2019 10:03 UTC proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1826029/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1722478] Re: Two-finger scrolling no longer works after resuming from suspend
Quick follower to my own #102, it turns out that my machine simply needed to be started twice with the bootloader option psmouse.proto=imps set. The first time shook something looks in Gnome which resulted in a notification appearing about a minute after boot, "software update made that require restart." After the restart, when I open my Mouse & Touchpad control panel, the two-finger/edge-scrolling/tap-to-click controls have appeared (they were hidden on the first boot!) and function correctly. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1722478 Title: Two-finger scrolling no longer works after resuming from suspend Status in Linux: Confirmed Status in linux package in Ubuntu: Incomplete Bug description: I own a Thinkpad T440p onto which I have had Debian 9 running without hardware issues. I have recently installed Ubuntu 17.10 final beta to test it out, but two-finger scrolling does not work at the moment. It used to work out-of-the-box from the final beta iso, but a subsequent update broke it. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-12-generic 4.13.0-12.13 [modified: boot/vmlinuz-4.13.0-12-generic] ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ghislain 10620 F pulseaudio /dev/snd/controlC0: ghislain 10620 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Oct 10 09:20:01 2017 HibernationDevice: RESUME=UUID=ae4cca1e-80ef-4a1e-87e3-0a860b49492e InstallationDate: Installed on 2017-10-05 (4 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) MachineType: LENOVO 20AN00C1UK ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-12-generic root=/dev/mapper/doc1485--lap--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-12-generic N/A linux-backports-modules-4.13.0-12-generic N/A linux-firmware 1.169 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/31/2016 dmi.bios.vendor: LENOVO dmi.bios.version: GLET83WW (2.37 ) dmi.board.asset.tag: Not Available dmi.board.name: 20AN00C1UK dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGLET83WW(2.37):bd03/31/2016:svnLENOVO:pn20AN00C1UK:pvrThinkPadT440p:rvnLENOVO:rn20AN00C1UK:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T440p dmi.product.name: 20AN00C1UK dmi.product.version: ThinkPad T440p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1722478/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1722478] Re: Two-finger scrolling no longer works after resuming from suspend
I was not having any issue with two-finger scrolling on my T560 and kernel 4.18.0-18-generic. I was trying to resolve a separate problem, that the pointing stick pointing in the center of the keyboard wasn't functioning, and would in fact cause the touchpad to stop functioning if I attempted to use it. The pointing stick's function was restored by adding psmouse.proto=imps to my bootloader options. However, now my touchpad 1) refuses to send scroll events, and 2) refuses to stop emulating mouse clicks (even after it's been disabled in tweaks). I've attempted every fix on this thread, with no success. Some of them cause the pointing stick to stop working again. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1722478 Title: Two-finger scrolling no longer works after resuming from suspend Status in Linux: Confirmed Status in linux package in Ubuntu: Incomplete Bug description: I own a Thinkpad T440p onto which I have had Debian 9 running without hardware issues. I have recently installed Ubuntu 17.10 final beta to test it out, but two-finger scrolling does not work at the moment. It used to work out-of-the-box from the final beta iso, but a subsequent update broke it. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-12-generic 4.13.0-12.13 [modified: boot/vmlinuz-4.13.0-12-generic] ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ghislain 10620 F pulseaudio /dev/snd/controlC0: ghislain 10620 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Oct 10 09:20:01 2017 HibernationDevice: RESUME=UUID=ae4cca1e-80ef-4a1e-87e3-0a860b49492e InstallationDate: Installed on 2017-10-05 (4 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) MachineType: LENOVO 20AN00C1UK ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-12-generic root=/dev/mapper/doc1485--lap--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-12-generic N/A linux-backports-modules-4.13.0-12-generic N/A linux-firmware 1.169 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/31/2016 dmi.bios.vendor: LENOVO dmi.bios.version: GLET83WW (2.37 ) dmi.board.asset.tag: Not Available dmi.board.name: 20AN00C1UK dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGLET83WW(2.37):bd03/31/2016:svnLENOVO:pn20AN00C1UK:pvrThinkPadT440p:rvnLENOVO:rn20AN00C1UK:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T440p dmi.product.name: 20AN00C1UK dmi.product.version: ThinkPad T440p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1722478/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1814373] Re: storage / luks / dmsetup regressed (or got better) on ppc64le
https://github.com/systemd/systemd/pull/12566 thnx @cascardo! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1814373 Title: storage / luks / dmsetup regressed (or got better) on ppc64le Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Status in udisks2 package in Ubuntu: Invalid Status in linux source package in Bionic: New Status in systemd source package in Bionic: New Status in udisks2 source package in Bionic: Invalid Status in linux source package in Disco: New Status in systemd source package in Disco: New Status in udisks2 source package in Disco: Invalid Status in linux source package in Eoan: Confirmed Status in systemd source package in Eoan: New Status in udisks2 source package in Eoan: Invalid Bug description: in disco proposed with new systemd and v4.19 kernel it appears that dmsetup / cryptsetup storage either got better or worse. Devices take very long to activate, and sometimes remain in use during test clean up. This leads to udisks autopkgtest failing on ppc64le and systemd's "storage" autopkgtest is also failing. I've tried to make ppc64le test more resilient, but it's still odd that it became unstable in disco, and used to be rock solid on ppc64le. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814373/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1826160] Re: linux-raspi2: 4.18.0-1013.15 -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: 1826171 phase: Holding before Release phase-changed: Monday, 13. May 2019 10:08 UTC proposed-announcement-sent: true proposed-testing-requested: true - reason: - promote-to-updates: Holding -- master bug not ready for release -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1826160 Title: linux-raspi2: 4.18.0-1013.15 -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: Invalid Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 source package in Cosmic: 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: 1826171 phase: Holding before Release phase-changed: Monday, 13. May 2019 10:08 UTC proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1826160/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1826143] Re: linux-azure: 5.0.0-1005.5 -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: 1826150 phase: Ready for Signoff phase-changed: Monday, 13. May 2019 05:07 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - promote-to-updates: Holding -- stakeholder signoff not verified stakeholder-signoff: Pending -- waiting for signoff -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1826143 Title: linux-azure: 5.0.0-1005.5 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-azure package in Ubuntu: Invalid Status in linux-azure 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 -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1826150 phase: Ready for Signoff phase-changed: Monday, 13. May 2019 05:07 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: stakeholder-signoff: Pending -- waiting for signoff To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1826143/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1826141] Re: linux-aws: 5.0.0-1005.5 -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: 1826150 phase: Holding before Release phase-changed: Monday, 13. May 2019 05:07 UTC proposed-announcement-sent: true proposed-testing-requested: true - reason: - promote-to-updates: Holding -- master bug not ready for release -- 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/1826141 Title: linux-aws: 5.0.0-1005.5 -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: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released 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 -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1826150 phase: Holding before Release phase-changed: Monday, 13. May 2019 05:07 UTC proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1826141/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1826144] Re: linux-gcp: 5.0.0-1005.5 -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: 1826150 phase: Holding before Release phase-changed: Monday, 13. May 2019 05:07 UTC proposed-announcement-sent: true proposed-testing-requested: true - reason: - promote-to-updates: Holding -- master bug not ready for release -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1826144 Title: linux-gcp: 5.0.0-1005.5 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp 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 -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1826150 phase: Holding before Release phase-changed: Monday, 13. May 2019 05:07 UTC proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1826144/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1826145] Re: linux-kvm: 5.0.0-1005.5 -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: 1826150 phase: Holding before Release phase-changed: Monday, 13. May 2019 15:14 UTC proposed-announcement-sent: true proposed-testing-requested: true - reason: - promote-to-updates: Holding -- master bug not ready for release -- 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/1826145 Title: linux-kvm: 5.0.0-1005.5 -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: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm 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 -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1826150 phase: Holding before Release phase-changed: Monday, 13. May 2019 15:14 UTC proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1826145/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1826146] Re: linux-snapdragon: 5.0.0-1011.11 -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: 1826150 phase: Holding before Release phase-changed: Monday, 13. May 2019 05:08 UTC proposed-announcement-sent: true proposed-testing-requested: true - reason: - promote-to-updates: Holding -- master bug not ready for release -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-snapdragon in Ubuntu. https://bugs.launchpad.net/bugs/1826146 Title: linux-snapdragon: 5.0.0-1011.11 -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: Invalid Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-snapdragon package in Ubuntu: Invalid Status in linux-snapdragon 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 -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1826150 phase: Holding before Release phase-changed: Monday, 13. May 2019 05:08 UTC proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1826146/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1826139] Re: linux-raspi2: 5.0.0-1007.7 -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: 1826150 phase: Holding before Release phase-changed: Monday, 13. May 2019 05:06 UTC proposed-announcement-sent: true proposed-testing-requested: true - reason: - promote-to-updates: Holding -- master bug not ready for release -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1826139 Title: linux-raspi2: 5.0.0-1007.7 -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: Invalid Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 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 -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1826150 phase: Holding before Release phase-changed: Monday, 13. May 2019 05:06 UTC proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1826139/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1761379] Re: [18.04/18.10] File libperf-jvmti.so is missing in linux-tools-common deb on Ubuntu
Probably will be ready for the cycle the ends on the last week of June. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1761379 Title: [18.04/18.10] File libperf-jvmti.so is missing in linux-tools-common deb on Ubuntu Status in The Ubuntu-power-systems project: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Artful: Won't Fix Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: In Progress Status in linux source package in Disco: In Progress Bug description: [Impact] File libperf-jvmti.so is missing in linux-tools-common deb making it impossible to use perf for the JVM JITed methods. [Test case] $ sudo perf record -k 1 -e instructions:u ./java -agentpath:/usr/lib/linux-tools-5.0.0-8/libperf-jvmti.so crc32 $ sudo perf inject -i ./perf.data -j -o ./perf.data.jitted $ sudo perf report -f -i ./perf.data.jitted [Fix] Include java build dependencies and install the library into linux-tools package. [Regression potential] Small regression potential, an extra file is distributed and is not automatically linked to anything. It could impact the build, which was tested. ---Problem Description--- File libperf-jvmti.so is missing in linux-tools-common deb making it impossible to use perf for the JVM JITed methods ---uname output--- linux-image-4.13.0-36-generic Machine Type = not relevant ---Debugger--- A debugger is not configured ---Steps to Reproduce--- File libperf-jvmti.so is missing in linux-tools-common deb provided for Ubuntu 17.10 making it impossible to use perf for the JVM JITed methods. I also checked if the file is available on launchpad (https://launchpad.net/ubuntu/+source/linux) for Bionic Beaver proposed (main) at it's also absent there: gromero@ltc-wspoon3:~/download$ dpkg -c linux-tools-common_4.15.0-13.14_all.deb | fgrep jvm gromero@ltc-wspoon3:~/download$ dpkg -c linux-tools-4.15.0-13-generic_4.15.0-13.14_ppc64el.deb | fgrep jvm I do see the file in tools/perf/jvmti dir in the source .tar.gz, but apparently it's no being packaged in any .deb file? Thanks. Userspace tool common name: perf The userspace tool has the following bit modes: 64-bit Userspace tool obtained from project website: na To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1761379/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1816669] Re: AMD Rome : Minimal support patches
Terry, The next SRU cycle will be which kernel? --kim -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1816669 Title: AMD Rome : Minimal support patches Status in amd: New Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: New Status in linux source package in Cosmic: Fix Released Bug description: The following 3 patches need to be back ported to ubuntu 18.04.2(Linux 4.18) to complete the minimal support for Rome : 818b7587b4d3 x86: irq_remapping: Move irq remapping mode enum e881dbd5d4a6 iommu/amd: Add support for higher 64-bit IOMMU Control Register 90fcffd9cf5e iommu/amd: Add support for IOMMU XT mode --thanks --kim --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-02-28 (5 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IwConfig: enp33s0f0 no wireless extensions. lono wireless extensions. enp33s0f1 no wireless extensions. MachineType: AMD Corporation DAYTONA_X Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-15-generic root=UUID=6500165b-63c3-4a3e-bbee-ca9f43bb1784 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-15-generic N/A linux-backports-modules-4.18.0-15-generic N/A linux-firmware 1.173.3 RfKill: Tags: bionic Uname: Linux 4.18.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/18/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: RDY0071B dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DAYTONA_X dmi.board.vendor: AMD Corporation dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 2 dmi.chassis.vendor: To be filled by O.E.M. dmi.chassis.version: To be filled by O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrRDY0071B:bd01/18/2019:svnAMDCorporation:pnDAYTONA_X:pvrTobefilledbyO.E.M.:rvnAMDCorporation:rnDAYTONA_X:rvrTobefilledbyO.E.M.:cvnTobefilledbyO.E.M.:ct2:cvrTobefilledbyO.E.M.: dmi.product.family: Default string dmi.product.name: DAYTONA_X dmi.product.sku: Default string dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: AMD Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1816669/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
