[Kernel-packages] [Bug 1850876] Re: CONFIG_DRＭ_V3D is disabled for linux-raspi2 of eoan
You are right, compiling the 4.19.y kernel works and seems to be stable. -- 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/1850876 Title: CONFIG_DRＭ_V3D is disabled for linux-raspi2 of eoan Status in linux-raspi2 package in Ubuntu: Fix Released Status in linux-raspi2 source package in Eoan: Triaged Bug description: We enabled DRM_VC4 in the linux-raspi2 of eoan, but disabled the DRM_V3D. In fact the DRM_V3D is crucial for graphical applications (such as ubuntu-desktop :) as it removes the graphical overhead from the cpu to the gpu, making the applications work much faster. Please refer to https://bugs.launchpad.net/ubuntu/+source/linux- raspi2/+bug/1848703/comments/32 [Impact] Users reported that we should enable the DRM_V3D, then the GPU will be fully used when running "ubuntu-desktop" [Fix] Enable the DRM_V3D, the v3d.ko will be built [Test Case] Users already tested it, it worked well. https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1848703/comments/36 [Regression Risk] Low, I already did building test for arm64 and armhf, all passed. And uers already tested the kernel module, it worked as expected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1850876/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1853378] Re: [amdgpu] ryzen 2500u random Xorg freeze
Another log file for Asus X505ZA. ** Attachment added: "log messages.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853378/+attachment/5310642/+files/log%20messages.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1853378 Title: [amdgpu] ryzen 2500u random Xorg freeze Status in linux package in Ubuntu: Confirmed Bug description: Currently using a Dell Inspiron 3835 with a ryzen 2500u with 8gb of ram on a pcie nvme ssd. PC randomly freezes at times. This actually occurs on asus x505za also running 2500u. I checked the log files and there was this error. [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process gnome-shell pid 10648 thread gnome-shel:cs0 pid 10654 [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process gnome-shell pid 10648 thread gnome-shel:cs0 pid 10654 I think it may be a problem with gnome since I was running lubuntu before and there's no hang whatsoever when using that. Ubuntu 18.04.3 LTS Release 18.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 Uname: Linux 5.3.12-050312-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Nov 21 07:04:57 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GpuHangFrequency: Several times a week GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Since a couple weeks or more GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15dd] (rev c4) (prog-if 00 [VGA controller]) Subsystem: Dell Vega [Radeon Vega 8 Mobile] [1028:08d7] InstallationDate: Installed on 2019-11-19 (1 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: Dell Inc. Inspiron 3585 ProcEnviron: LANGUAGE=en_PH:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_PH.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.12-050312-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash idle=nomwait iommu=soft pci=nomsi vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/29/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.0 dmi.board.asset.tag: not specified dmi.board.name: 0TY9XW dmi.board.vendor: Dell Inc. dmi.board.version: X01 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.4.0 dmi.modalias: dmi:bvnDellInc.:bvr1.4.0:bd05/29/2019:svnDellInc.:pnInspiron3585:pvr1.4.0:rvnDellInc.:rn0TY9XW:rvrX01:cvnDellInc.:ct10:cvr1.4.0: dmi.product.family: Inspiron dmi.product.name: Inspiron 3585 dmi.product.sku: 08D7 dmi.product.version: 1.4.0 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100+git1911150630.a39c34~oibaf~b version.libgl1-mesa-dri: libgl1-mesa-dri 20.0~git1911201930.bcfc9c~oibaf~b version.libgl1-mesa-glx: libgl1-mesa-glx 20.0~git1911201930.bcfc9c~oibaf~b version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853378/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1847628] Re: When using swap in ZFS, system stops when you start using swap
Yes this is confirmed, there is currently no way to use swap on zvol without a deadlock. The only solution at the moment is to create a swap partition. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1847628 Title: When using swap in ZFS, system stops when you start using swap Status in Release Notes for Ubuntu: Fix Released Status in Native ZFS for Linux: Unknown Status in ubiquity package in Ubuntu: Fix Released Status in zfs-linux package in Ubuntu: Triaged Bug description: # Problem When using swap in ZFS, system stops when you start using swap. > stress --vm 100 if you doing swapoff will only occur OOM and the system will not stop. # Environment jehos@MacBuntu:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu Eoan Ermine (development branch) Release:19.10 Codename: eoan jehos@MacBuntu:~$ dpkg -l | grep zfs ii libzfs2linux 0.8.1-1ubuntu13 amd64OpenZFS filesystem library for Linux ii zfs-initramfs 0.8.1-1ubuntu13 amd64OpenZFS root filesystem capabilities for Linux - initramfs ii zfs-zed0.8.1-1ubuntu13 amd64OpenZFS Event Daemon ii zfsutils-linux 0.8.1-1ubuntu13 amd64command-line tools to manage OpenZFS filesystems jehos@MacBuntu:~$ uname -a Linux MacBuntu 5.3.0-13-generic #14-Ubuntu SMP Tue Sep 24 02:46:08 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux jehos@MacBuntu:~$ zpool list NAMESIZE ALLOC FREE CKPOINT EXPANDSZ FRAGCAP DEDUPHEALTH ALTROOT bpool 1.88G 66.1M 1.81G- - - 3% 1.00xONLINE - rpool 230G 124G 106G- - 9%53% 1.00xONLINE - jehos@MacBuntu:~$ zfs get all rpool/swap NAMEPROPERTY VALUESOURCE rpool/swap type volume - rpool/swap creation 목 10월 10 15:56 2019 - rpool/swap used 2.13G- rpool/swap available 98.9G- rpool/swap referenced72K - rpool/swap compressratio 1.11x- rpool/swap reservation none default rpool/swap volsize 2G local rpool/swap volblocksize 4K - rpool/swap checksum on default rpool/swap compression zle local rpool/swap readonly off default rpool/swap createtxg 34 - rpool/swap copies1default rpool/swap refreservation2.13Glocal rpool/swap guid 18209330213704683244 - rpool/swap primarycache metadata local rpool/swap secondarycachenone local rpool/swap usedbysnapshots 0B - rpool/swap usedbydataset 72K - rpool/swap usedbychildren0B - rpool/swap usedbyrefreservation 2.13G- rpool/swap logbias throughput local rpool/swap objsetid 393 - rpool/swap dedup off default rpool/swap mlslabel none default rpool/swap sync always local rpool/swap refcompressratio 1.11x- rpool/swap written 72K - rpool/swap logicalused 40K - rpool/swap logicalreferenced 40K - rpool/swap volmode default default rpool/swap snapshot_limitnone default rpool/swap snapshot_countnone default rpool/swap snapdev hidden default rpool/swap context none default rpool/swap fscontext none default rpool/swap defcontextnone default rpool/swap rootcontext none default rpool/swap redundant_metadataall default rpool/swap encryptionoff default rpool/swap keylocation none default rpool/swap keyformat none default rpool/swap
[Kernel-packages] [Bug 1834578] Re: Mouse stop working
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1834578 Title: Mouse stop working Status in linux package in Ubuntu: Expired Bug description: USB mouse stop working randomly ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-53.57-generic 4.15.18 Uname: Linux 4.15.0-53-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.116 Sun Jan 27 07:21:36 PST 2019 GCC version: gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1) ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jun 28 10:24:54 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 390.116, 4.15.0-52-generic, x86_64: installed nvidia, 390.116, 4.15.0-53-generic, x86_64: installed virtualbox, 5.2.18, 4.15.0-52-generic, x86_64: installed virtualbox, 5.2.18, 4.15.0-53-generic, x86_64: installed GraphicsCard: NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] [10de:1c82] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP107 [GeForce GTX 1050 Ti] [1043:85d3] InstallationDate: Installed on 2018-09-21 (280 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 009: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse Bus 001 Device 002: ID 0518:5111 EzKEY Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-53-generic root=UUID=8e5738ba-3515-4603-abfb-a837482ef7ba 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: American Megatrends Inc. dmi.bios.version: 0809 dmi.board.asset.tag: Default string dmi.board.name: PRIME B250M-K dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0809:bd07/07/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB250M-K:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1834578/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838678] Re: radeon kernel driver fails to resume from suspend
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1838678 Title: radeon kernel driver fails to resume from suspend Status in linux package in Ubuntu: Expired Bug description: Hello everybody, I'm using a laptop which is a Dell Latitude E6540 with hybrid graphics: 00:02.0 VGA compatible controller: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller (rev 06) 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Mars XTX [Radeon HD 8790M] (rev ff) The distribution is Ubuntu 18.04.2 LTS with HWE kernel 4.18.0-25-generic and HWE XServer packages. However, the problem described below showed up with the standard kernel as well. Kernel modules amdgpu, radeon, i915 are loaded. From time to time, I suspend the laptop and switch from using the laptop's primary display only to using one or more connected external displays/projectors and back. On resume, the window manager isn't started immediately. Instead, a lot of error messages are displayed on the console: radeon :01:00.0: failed VCE resume (-110). [drm:r600_ring_test [radeon]] *ERROR* radeon: ring 0 test failed (scratch(0x850C)=0x) [drm:atom_op_jump [radeon]] *ERROR* atombios stuck in loop for more than 5secs aborting [drm:atom_execute_table_locked [radeon]] *ERROR* atombios stuck executing CF1C (len 62, WS 0, PS 0) @ 0xCF38 [drm:atom_execute_table_locked [radeon]] *ERROR* atombios stuck executing B67E (len 236, WS 4, PS 0) @ 0xB74B [drm:atom_execute_table_locked [radeon]] *ERROR* atombios stuck executing B5DC (len 74, WS 0, PS 8) @ 0xB5E4 [drm:si_dpm_enable [radeon]] *ERROR* si_init_smc_table failed [drm:radeon_pm_resume [radeon]] *ERROR* radeon: dpm resume failed The error messages are also shown on connected projectors which is slightly annoying. Mostly, after a minute or two the system resumes successfully with the window manager starting and all applications still running. However, after more and more suspend/resume cycles the resume process takes longer and sometimes X11 will crash so that a new session has to be started. Best regards, Thomas --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=255880d2-46ce-4ad0-ae40-cbe8d6448bcb InstallationDate: Installed on 2018-08-09 (357 days ago) InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. Latitude E6540 Package: linux (not installed) ProcFB: 0 inteldrmfb 1 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-25-generic root=UUID=6c1fe528-1808-4de4-8d6e-be8d7e796823 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-25.26~18.04.1-generic 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-25-generic N/A linux-backports-modules-4.18.0-25-generic N/A linux-firmware 1.173.9 Tags: bionic Uname: Linux 4.18.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/18/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0725FP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA08:bd02/18/2014:svnDellInc.:pnLatitudeE6540:pvr01:rvnDellInc.:rn0725FP:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6540 dmi.product.sku: Latitude E6540 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838678/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1855177] Re: QEMU emulated nvdimm regions alignment need (128MB) or ndctl create-namespace namespace1.0 might fail
You have to make sure to set the label size as the same size as the minimum alignment required. For QEMU emulation I found it to be 2M, and, in this case, you can correctly work with 2 or more nvdimms. With proper alignment, you can also re-create namespaces - of other mode like devdax or fsdax - if you already have a namespace working. Example: $_nvpath1 1048576 0 2048 $_nvpath2 1048576 1 2048 So I'm closing this as NOT A BUG as the alignment can be configured accordingly. For other examples you can check autopkgtests being proposed as a merge request at: https://bugs.launchpad.net/ubuntu/+source/ndctl/+bug/1853506 ** Changed in: ndctl (Ubuntu Focal) Status: Confirmed => Invalid ** Changed in: qemu (Ubuntu Focal) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1855177 Title: QEMU emulated nvdimm regions alignment need (128MB) or ndctl create- namespace namespace1.0 might fail Status in linux package in Ubuntu: Fix Released Status in ndctl package in Ubuntu: Invalid Status in qemu package in Ubuntu: Invalid Status in linux source package in Focal: Fix Released Status in ndctl source package in Focal: Invalid Status in qemu source package in Focal: Invalid Bug description: I got a probe error for pfn1.0 (from both pfn0.0 and pfn1.0) when dealing with ndctl: [11257.765457] memory add fail, invalid altmap [11257.765489] WARNING: CPU: 6 PID: 5680 at arch/x86/mm/init_64.c:852 add_pages+0x5d/0x70 [11257.765489] Modules linked in: nls_iso8859_1 edac_mce_amd crct10dif_pclmul crc32_pclmul dax_pmem_compat device_dax dax_pmem_core nd_pmem nd_btt ghash_clmulni_intel aesni_intel aes_x86_64 crypto_simd cryptd glue_helper input_leds joydev mac_hid nfit serio_raw qemu_fw_cfg sch_fq_codel ip_tables x_tables autofs4 virtio_net net_failover psmouse failover pata_acpi virtio_blk i2c_piix4 floppy [11257.765505] CPU: 6 PID: 5680 Comm: ndctl Not tainted 5.3.0-24-generic #26-Ubuntu [11257.765505] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.12.0-1 04/01/2014 [11257.765507] RIP: 0010:add_pages+0x5d/0x70 [11257.765509] Code: 33 c2 01 76 20 48 89 15 99 33 c2 01 48 89 15 a2 33 c2 01 48 c1 e2 0c 48 03 15 97 96 39 01 48 89 15 48 0e c2 01 5b 41 5c 5d c3 <0f> 0b eb ba 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 0f 1f 44 [11257.765509] RSP: 0018:a360c09dfbf0 EFLAGS: 00010282 [11257.765510] RAX: ffea RBX: 0017ffe0 RCX: [11257.765511] RDX: RSI: 8acb7db17448 RDI: 8acb7db17448 [11257.765512] RBP: a360c09dfc00 R08: 8acb7db17448 R09: 0004 [11257.765512] R10: R11: 0001 R12: 0003fe20 [11257.765513] R13: 0001 R14: a360c09dfc48 R15: 8acb7a7226f8 [11257.765515] FS: 7febc9fd6bc0() GS:8acb7db0() knlGS: [11257.765516] CS: 0010 DS: ES: CR0: 80050033 [11257.765517] CR2: 55eec8aab398 CR3: 00013a8fa000 CR4: 000406e0 [11257.765519] Call Trace: [11257.765523] arch_add_memory+0x41/0x50 [11257.765525] devm_memremap_pages+0x47c/0x640 [11257.765529] pmem_attach_disk+0x173/0x610 [nd_pmem] [11257.765531] ? devm_memremap+0x67/0xa0 [11257.765532] nd_pmem_probe+0x7f/0xa0 [nd_pmem] [11257.765542] nvdimm_bus_probe+0x6b/0x170 [11257.765547] really_probe+0xfb/0x3a0 [11257.765549] driver_probe_device+0x5f/0xe0 [11257.765550] device_driver_attach+0x5d/0x70 [11257.765551] bind_store+0xd3/0x110 [11257.765553] drv_attr_store+0x24/0x30 [11257.765554] sysfs_kf_write+0x3e/0x50 [11257.76] kernfs_fop_write+0x11e/0x1a0 [11257.765557] __vfs_write+0x1b/0x40 [11257.765558] vfs_write+0xb9/0x1a0 [11257.765559] ksys_write+0x67/0xe0 [11257.765561] __x64_sys_write+0x1a/0x20 [11257.765567] do_syscall_64+0x5a/0x130 [11257.765693] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [11257.765696] RIP: 0033:0x7febc9e81327 [11257.765698] Code: 64 89 02 48 c7 c0 ff ff ff ff eb bb 0f 1f 80 00 00 00 00 f3 0f 1e fa 64 8b 04 25 18 00 00 00 85 c0 75 10 b8 01 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 51 c3 48 83 ec 28 48 89 54 24 18 48 89 74 24 [11257.765698] RSP: 002b:7ffd599433f8 EFLAGS: 0246 ORIG_RAX: 0001 [11257.765699] RAX: ffda RBX: 7febc9fd6ae8 RCX: 7febc9e81327 [11257.765700] RDX: 0007 RSI: 55eec8a9bfa0 RDI: 0004 [11257.765701] RBP: 0004 R08: 0006 R09: 7375622f7379732f [11257.765701] R10: R11: 0246 R12: 55eec8a9bfa0 [11257.765702] R13:
[Kernel-packages] [Bug 1847628] Re: When using swap in ZFS, system stops when you start using swap
@jibel unfortunately that doesn't help, still stalling when writing to swap, even without compression. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1847628 Title: When using swap in ZFS, system stops when you start using swap Status in Release Notes for Ubuntu: Fix Released Status in Native ZFS for Linux: Unknown Status in ubiquity package in Ubuntu: Fix Released Status in zfs-linux package in Ubuntu: Triaged Bug description: # Problem When using swap in ZFS, system stops when you start using swap. > stress --vm 100 if you doing swapoff will only occur OOM and the system will not stop. # Environment jehos@MacBuntu:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu Eoan Ermine (development branch) Release:19.10 Codename: eoan jehos@MacBuntu:~$ dpkg -l | grep zfs ii libzfs2linux 0.8.1-1ubuntu13 amd64OpenZFS filesystem library for Linux ii zfs-initramfs 0.8.1-1ubuntu13 amd64OpenZFS root filesystem capabilities for Linux - initramfs ii zfs-zed0.8.1-1ubuntu13 amd64OpenZFS Event Daemon ii zfsutils-linux 0.8.1-1ubuntu13 amd64command-line tools to manage OpenZFS filesystems jehos@MacBuntu:~$ uname -a Linux MacBuntu 5.3.0-13-generic #14-Ubuntu SMP Tue Sep 24 02:46:08 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux jehos@MacBuntu:~$ zpool list NAMESIZE ALLOC FREE CKPOINT EXPANDSZ FRAGCAP DEDUPHEALTH ALTROOT bpool 1.88G 66.1M 1.81G- - - 3% 1.00xONLINE - rpool 230G 124G 106G- - 9%53% 1.00xONLINE - jehos@MacBuntu:~$ zfs get all rpool/swap NAMEPROPERTY VALUESOURCE rpool/swap type volume - rpool/swap creation 목 10월 10 15:56 2019 - rpool/swap used 2.13G- rpool/swap available 98.9G- rpool/swap referenced72K - rpool/swap compressratio 1.11x- rpool/swap reservation none default rpool/swap volsize 2G local rpool/swap volblocksize 4K - rpool/swap checksum on default rpool/swap compression zle local rpool/swap readonly off default rpool/swap createtxg 34 - rpool/swap copies1default rpool/swap refreservation2.13Glocal rpool/swap guid 18209330213704683244 - rpool/swap primarycache metadata local rpool/swap secondarycachenone local rpool/swap usedbysnapshots 0B - rpool/swap usedbydataset 72K - rpool/swap usedbychildren0B - rpool/swap usedbyrefreservation 2.13G- rpool/swap logbias throughput local rpool/swap objsetid 393 - rpool/swap dedup off default rpool/swap mlslabel none default rpool/swap sync always local rpool/swap refcompressratio 1.11x- rpool/swap written 72K - rpool/swap logicalused 40K - rpool/swap logicalreferenced 40K - rpool/swap volmode default default rpool/swap snapshot_limitnone default rpool/swap snapshot_countnone default rpool/swap snapdev hidden default rpool/swap context none default rpool/swap fscontext none default rpool/swap defcontextnone default rpool/swap rootcontext none default rpool/swap redundant_metadataall default rpool/swap encryptionoff default rpool/swap keylocation none default rpool/swap keyformat none default rpool/swap pbkdf2iters 0default
[Kernel-packages] [Bug 1848703] Re: Raspberry Pi 4 - USB Bus not detecting any devices
*** This bug is a duplicate of bug 1848790 *** https://bugs.launchpad.net/bugs/1848790 @Pete, Looks like someone else met the same issue, and already opened a bug in the upstream, let's track the upstream bug, after it is fixed by upstream, we will integrate the fix in the ubuntu kernel. https://github.com/raspberrypi/linux/issues/3334 thx. ** Bug watch added: github.com/raspberrypi/linux/issues #3334 https://github.com/raspberrypi/linux/issues/3334 -- 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/1848703 Title: Raspberry Pi 4 - USB Bus not detecting any devices Status in linux-raspi2 package in Ubuntu: Confirmed Bug description: Pi 4 new install. System boots up but USB bus is not working. Tried 3 keyboards no key presses detected, 2 usb memory drives don't show up in lsblk. output of $lspci 00:00.0 PCI bridge: Broadcom Inc. and subsidiaries Device 2711 (rev 10) 01:00.0 USB controller: VIA Technologies, Inc. VL805 USB 3.0 Host Controller (rev 01) output of $dmesg on pastebin here http://pastebin.com/h7A3n9xa or attached to this bug report. Not the only one experiencing bug. Another user created a post on the ubuntu forums: https://ubuntuforums.org/showthread.php?t=2429396=01a0c4b0cb4c05e605cbf9d41f660e08=13898142#post13898142 64bit raspberry pi 4&4 image pulled from https://ubuntu.com/download/iot/raspberry-pi page. Specifically http://cdimage.ubuntu.com/releases/19.10/release/ubuntu-19.10 -preinstalled-server-arm64+raspi3.img.xz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1848703/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1855564] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1855564 Title: system load gradually increase, until a forced shutdown kernel 5.3.0-23 and above Status in linux package in Ubuntu: Confirmed Bug description: There is no issues with kernel 5.3.0-19. the issue is from kernel 5.3.0-23 and above. 20-22 were not tested. The freeze is related to nvme drive access. it can be tested with the following command. sudo /usr/sbin/grub-probe --device /dev/nvme1n1p2 --target=fs_uuid This command freezes on kernel with the bug. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-19-generic 5.3.0-19.20 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Dec 7 17:01:27 2019 HibernationDevice: RESUME=UUID=24dfd8ad-f9e6-4f3a-87bd-32549cf5ba9b InstallationDate: Installed on 2014-04-18 (2059 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Micro-Star International Co., Ltd. MS-7A95 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic root=UUID=79eaf8ba-9463-4191-9bfb-30f8b81ed108 ro intel_iommu=on RelatedPackageVersions: linux-restricted-modules-5.3.0-19-generic N/A linux-backports-modules-5.3.0-19-generic N/A linux-firmware1.183.2 SourcePackage: linux UpgradeStatus: Upgraded to eoan on 2019-10-27 (41 days ago) dmi.bios.date: 07/31/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.90 dmi.board.asset.tag: Default string dmi.board.name: X299 GAMING PRO CARBON AC (MS-7A95) dmi.board.vendor: Micro-Star International Co., Ltd dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.90:bd07/31/2018:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A95:pvr1.0:rvnMicro-StarInternationalCo.,Ltd:rnX299GAMINGPROCARBONAC(MS-7A95):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7A95 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2014-09-06T20:58:41 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855564/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1850876] Re: CONFIG_DRＭ_V3D is disabled for linux-raspi2 of eoan
The 5.3.y branch doesn't have this fix yet, and looking for fix patches from branch 4.19.y is not easy. If possible, it is helpful if users could file V3D issues against 5.3.y (https://github.com/raspberrypi/linux/issues) Thx. -- 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/1850876 Title: CONFIG_DRＭ_V3D is disabled for linux-raspi2 of eoan Status in linux-raspi2 package in Ubuntu: Fix Released Status in linux-raspi2 source package in Eoan: Triaged Bug description: We enabled DRM_VC4 in the linux-raspi2 of eoan, but disabled the DRM_V3D. In fact the DRM_V3D is crucial for graphical applications (such as ubuntu-desktop :) as it removes the graphical overhead from the cpu to the gpu, making the applications work much faster. Please refer to https://bugs.launchpad.net/ubuntu/+source/linux- raspi2/+bug/1848703/comments/32 [Impact] Users reported that we should enable the DRM_V3D, then the GPU will be fully used when running "ubuntu-desktop" [Fix] Enable the DRM_V3D, the v3d.ko will be built [Test Case] Users already tested it, it worked well. https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1848703/comments/36 [Regression Risk] Low, I already did building test for arm64 and armhf, all passed. And uers already tested the kernel module, it worked as expected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1850876/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1850876] Re: CONFIG_DRＭ_V3D is disabled for linux-raspi2 of eoan
** Changed in: linux-raspi2 (Ubuntu Eoan) Status: Fix Released => Triaged -- 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/1850876 Title: CONFIG_DRＭ_V3D is disabled for linux-raspi2 of eoan Status in linux-raspi2 package in Ubuntu: Fix Released Status in linux-raspi2 source package in Eoan: Triaged Bug description: We enabled DRM_VC4 in the linux-raspi2 of eoan, but disabled the DRM_V3D. In fact the DRM_V3D is crucial for graphical applications (such as ubuntu-desktop :) as it removes the graphical overhead from the cpu to the gpu, making the applications work much faster. Please refer to https://bugs.launchpad.net/ubuntu/+source/linux- raspi2/+bug/1848703/comments/32 [Impact] Users reported that we should enable the DRM_V3D, then the GPU will be fully used when running "ubuntu-desktop" [Fix] Enable the DRM_V3D, the v3d.ko will be built [Test Case] Users already tested it, it worked well. https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1848703/comments/36 [Regression Risk] Low, I already did building test for arm64 and armhf, all passed. And uers already tested the kernel module, it worked as expected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1850876/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1855564] [NEW] system load gradually increase, until a forced shutdown kernel 5.3.0-23 and above
Public bug reported: There is no issues with kernel 5.3.0-19. the issue is from kernel 5.3.0-23 and above. 20-22 were not tested. The freeze is related to nvme drive access. it can be tested with the following command. sudo /usr/sbin/grub-probe --device /dev/nvme1n1p2 --target=fs_uuid This command freezes on kernel with the bug. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-19-generic 5.3.0-19.20 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Dec 7 17:01:27 2019 HibernationDevice: RESUME=UUID=24dfd8ad-f9e6-4f3a-87bd-32549cf5ba9b InstallationDate: Installed on 2014-04-18 (2059 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Micro-Star International Co., Ltd. MS-7A95 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic root=UUID=79eaf8ba-9463-4191-9bfb-30f8b81ed108 ro intel_iommu=on RelatedPackageVersions: linux-restricted-modules-5.3.0-19-generic N/A linux-backports-modules-5.3.0-19-generic N/A linux-firmware1.183.2 SourcePackage: linux UpgradeStatus: Upgraded to eoan on 2019-10-27 (41 days ago) dmi.bios.date: 07/31/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.90 dmi.board.asset.tag: Default string dmi.board.name: X299 GAMING PRO CARBON AC (MS-7A95) dmi.board.vendor: Micro-Star International Co., Ltd dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.90:bd07/31/2018:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A95:pvr1.0:rvnMicro-StarInternationalCo.,Ltd:rnX299GAMINGPROCARBONAC(MS-7A95):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7A95 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2014-09-06T20:58:41 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1855564 Title: system load gradually increase, until a forced shutdown kernel 5.3.0-23 and above Status in linux package in Ubuntu: New Bug description: There is no issues with kernel 5.3.0-19. the issue is from kernel 5.3.0-23 and above. 20-22 were not tested. The freeze is related to nvme drive access. it can be tested with the following command. sudo /usr/sbin/grub-probe --device /dev/nvme1n1p2 --target=fs_uuid This command freezes on kernel with the bug. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-19-generic 5.3.0-19.20 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Dec 7 17:01:27 2019 HibernationDevice: RESUME=UUID=24dfd8ad-f9e6-4f3a-87bd-32549cf5ba9b InstallationDate: Installed on 2014-04-18 (2059 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Micro-Star International Co., Ltd. MS-7A95 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic root=UUID=79eaf8ba-9463-4191-9bfb-30f8b81ed108 ro intel_iommu=on RelatedPackageVersions: linux-restricted-modules-5.3.0-19-generic N/A linux-backports-modules-5.3.0-19-generic N/A linux-firmware1.183.2 SourcePackage: linux UpgradeStatus: Upgraded to eoan on 2019-10-27 (41 days ago) dmi.bios.date: 07/31/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.90 dmi.board.asset.tag: Default string dmi.board.name: X299 GAMING PRO CARBON AC (MS-7A95) dmi.board.vendor: Micro-Star International Co., Ltd dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias:
[Kernel-packages] [Bug 1850876] Re: CONFIG_DRＭ_V3D is disabled for linux-raspi2 of eoan
Fix is not released since it was reverted above. Any updates on this? -- 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/1850876 Title: CONFIG_DRＭ_V3D is disabled for linux-raspi2 of eoan Status in linux-raspi2 package in Ubuntu: Fix Released Status in linux-raspi2 source package in Eoan: Fix Released Bug description: We enabled DRM_VC4 in the linux-raspi2 of eoan, but disabled the DRM_V3D. In fact the DRM_V3D is crucial for graphical applications (such as ubuntu-desktop :) as it removes the graphical overhead from the cpu to the gpu, making the applications work much faster. Please refer to https://bugs.launchpad.net/ubuntu/+source/linux- raspi2/+bug/1848703/comments/32 [Impact] Users reported that we should enable the DRM_V3D, then the GPU will be fully used when running "ubuntu-desktop" [Fix] Enable the DRM_V3D, the v3d.ko will be built [Test Case] Users already tested it, it worked well. https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1848703/comments/36 [Regression Risk] Low, I already did building test for arm64 and armhf, all passed. And uers already tested the kernel module, it worked as expected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1850876/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834771] Re: No HDMI-audio after kernel 4.15.-0.50
I've also installed the testing kernels but without success. No audio at all :( @hui.wang: I saw some dmesg outputs being uploaded. Do you need more samples to fix this bug? Can you please give us a status update on this? I'm dealing with this situation for months now and half of the PCs in our office are affected. Using such an old unpatched kernel for work is not an option. So me and my colleagues have to use headphones or external speakers along our speaker equipped monitors. If quick help is not in sight, I vote for simply undoing the patch that triggered this terrible bug: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1827967 Please make our audio work again, @hui.wang! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1834771 Title: No HDMI-audio after kernel 4.15.-0.50 Status in linux package in Ubuntu: Confirmed Bug description: I've got no HDMI-audio. Latest kernel with working HDMI-audio is 4.15.-0.50. In pavucontrol HDMI-audio shows unplugged. And also internal audio shows unplugged, but it still works. I'm on linux mint 18.3. --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jouni 1859 F pulseaudio /dev/snd/controlC1: jouni 1859 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux 18.3 HibernationDevice: RESUME=UUID=9e8d7bf3-dc5f-4c72-b875-6dbe81a36c36 InstallationDate: Installed on 2017-01-28 (883 days ago) InstallationMedia: Linux Mint 18.1 "Serena" - Release amd64 20161213 IwConfig: lono wireless extensions. enp3s0no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-54-generic root=UUID=f167a2b0-3b30-4a5a-907f-6b97c95b7a91 ro quiet iommu=soft splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.15.0-54.58~16.04.1-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-54-generic N/A linux-backports-modules-4.15.0-54-generic N/A linux-firmware 1.157.21 RfKill: Tags: sylvia Uname: Linux 4.15.0-54-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 02/26/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FC dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 970A-UD3P dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrFC:bd02/26/2016:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rn970A-UD3P:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1834771/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 869017] Re: Ubuntu server enables screenblanking, concealing crashdumps (DPMS is not used)
Some additional information and observations. What I am currently seeing with this issue on 3 systems running Ubuntu 18.04 that did not occur on the same systems that previously ran 16.04 is that the actual screen blanking in 18.04, aside from default settings or overrides, fails to turn off the monitor using DPMS as it did in 16.04, but only with nvidia binary drivers installed and only in 18.04, and only with the console blanking code in its current state. In 18.04 without the nvidia binary driver, console blanking seems to work, as expected, with the consoleblank=n. This includes a correct power down. In 18.04 with the nvidia binary driver 340.107, console blanking only blanks the screen, but fails to power down the monitor- yet a call to vbetool dpms off does work, as do any similar calls in X for those systems that have X installed. So if vbetool dpms works with the nvidia binary driver and the console blanking code no longer does, I am half way to an assumption that the dpms code in the console blanking has changed, with some reservation that possibly the latest nvidia binary driver doesn't like the way the call is coming from the newly changed console blanking code. This problem did not exist in 16.04, on any of our systems to my knowledge, with or without a graphical desktop installed and with or without a binary driver installed. >From my perspective, this isn't an issue of default blanking behaviour, but rather an issue with a broken dpms call in 18.04 to a system with the nvidia binary driver. Other calls, such as vbetool dpms off work as do those within graphical desktop systems such as those like the one that xscreensaver uses. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/869017 Title: Ubuntu server enables screenblanking, concealing crashdumps (DPMS is not used) Status in kbd package in Ubuntu: Invalid Status in linux package in Ubuntu: Fix Released Status in kbd source package in Zesty: Invalid Status in linux source package in Zesty: Fix Released Status in kbd package in Debian: Fix Released Bug description: James Rice of Jump Networks noticed that there is a screen-blanker enabled on Ubuntu Server. James notes that this blanking is not enabling DPMS power saving (thereby negating any power-saving benefit), and is simply turning the screen content blank. This means that the crash output is invisible which is unhelpful on a server (virtual or otherwise). Ideally the screen should (at a minimum) be turned on and unblanked at the point of an OOPs/crash being printed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kbd/+bug/869017/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1854895] Re: touchpad stopped working after the update
*** This bug is a duplicate of bug 1854798 *** https://bugs.launchpad.net/bugs/1854798 I have exactly the same issue. Touchapd Synaptics TM2869-008 working perfectly fine with kernel 4.15.0-70 under Ubuntu 18.04 LTS. As soon as I updated kernel to 4.15.0-72, touchpad stopped working. Booting back to previous kernel, touchpad is working perfectly fine. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1854895 Title: touchpad stopped working after the update Status in Linux: New Status in linux package in Ubuntu: Confirmed Bug description: After the automatic software update the touchpad stopped working in my laptop. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-72-generic 4.15.0-72.81 ProcVersionSignature: Ubuntu 4.15.0-72.81-generic 4.15.18 Uname: Linux 4.15.0-72-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: anil 1722 F pulseaudio /dev/snd/controlC0: anil 1722 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Dec 3 10:44:48 2019 InstallationDate: Installed on 2018-12-21 (346 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. Inspiron 3542 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-72-generic root=UUID=a85be26b-aca7-48bd-b03b-6a99e1587772 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-72-generic N/A linux-backports-modules-4.15.0-72-generic N/A linux-firmware 1.173.12 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/23/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A14 dmi.board.name: 09V1VC dmi.board.vendor: Dell Inc. dmi.board.version: A14 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA14:bd05/23/2018:svnDellInc.:pnInspiron3542:pvrNotSpecified:rvnDellInc.:rn09V1VC:rvrA14:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 3542 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1854895/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1712508] Re: Disappearing screen and flickering after upgrade to 16.04
I confirm this bug is present on Ubuntu 18.04, my hardware is an Intel HD Graphics 5500. It was working fine on the previous LTS, 16.04; if I use kernel 4.4.0-161-generic from Ubuntu 16 Xenial I can boot Ubuntu 18 Bionic fine, thus I conclude it's something in the kernel. I have tried these options (individually) without any effect: i915.enable_ips=0 swiotlb=force i915.enable_ips=0 intel_idle.max_cstate=1 i915.enable_rc6=0 i915.enable_psr=0 On the good kernel I see this error in dmesg: [drm:intel_dp_link_training_channel_equalization [i915]] *ERROR* failed to train DP, aborting While on the bad one there are no such failures as it detects everything: [ 10.429894] input: HDA Intel HDMI HDMI/DP,pcm=3 as /devices/pci:00/:00:03.0/sound/card0/input22 [ 10.429989] input: HDA Intel HDMI HDMI/DP,pcm=7 as /devices/pci:00/:00:03.0/sound/card0/input23 [ 10.430070] input: HDA Intel HDMI HDMI/DP,pcm=8 as /devices/pci:00/:00:03.0/sound/card0/input24 [ 10.430166] input: HDA Intel HDMI HDMI/DP,pcm=9 as /devices/pci:00/:00:03.0/sound/card0/input25 [ 10.430250] input: HDA Intel HDMI HDMI/DP,pcm=10 as /devices/pci:00/:00:03.0/sound/card0/input26 The most interesting clue to find a solution is however to be found in gparted-live-1.0.0-5-amd64.iso: when booting this live distro via USB I get exactly the same flickering (it uses kernel 5.2.0) but when starting Xorg the problem disappears. Switching back to any VT shows the flickering problem. I was wondering if it could be possible to dissect the GParted live ISO to find out what makes it work when starting Xorg. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1712508 Title: Disappearing screen and flickering after upgrade to 16.04 Status in linux package in Ubuntu: Confirmed Bug description: I have two Lenovo T410s that I upgraded from 14.04 to 16.04. Since then, one is working fine while the other shows mainly an ever disappearing screen and flickering. I have asked here: https://askubuntu.com/questions/947233/i-upgraded-from-kubuntu-14-04-lts-to-16-04-lts-and-now-my-screen-shows-up-and-di?noredirect=1#comment1506995_947233 I also found I am not the only one: https://askubuntu.com/questions/927407/flickering-screen-with-intel-graphics-on-ubuntu-17-04?noredirect=1#comment1507937_927407 The latter has tried pretty much that could be tried already, to no avail. I think that I can help with this problem, since my two T410s are identical in hard- and software, including BIOS, except that one is a type 2924 (with NVIDIA-card, though disabled in the BIOS), and the other one is a 2904 (without NVIDIA card). I have checked for differences at boot time and found DMAR as major difference: T410s, 2924: [ 0.335616] DMAR: Disabling batched IOTLB flush on Ironlake T410s, 2904: [ 0.355681] DMAR: BIOS has allocated no shadow GTT; disabling IOMMU for graphics Should this be initially at the root of the problem, I'd consider the kernel package as responsible, therefore I marked it as above. The outputs of lspci -k | grep -EA3 'VGA|3D|Display' are identical to the point. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1712508/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1824407] Re: remount of multilower moved pivoted-root overlayfs root, results in I/O errors on some modified files
The comment in #34 is about 5.3.0-25.27 which is in eoan-proposed. Also ubuntu-kernel-bot must post these message when the kernel is copied into -proposed pocket, and it should state the release series and version, just like all other SRU comments do. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1824407 Title: remount of multilower moved pivoted-root overlayfs root, results in I/O errors on some modified files Status in linux package in Ubuntu: In Progress Status in linux-hwe package in Ubuntu: Invalid Status in linux-hwe source package in Bionic: In Progress Status in linux source package in Disco: Fix Committed Status in linux source package in Eoan: Fix Committed Status in linux source package in Focal: In Progress Bug description: == SRU Justification Disco, Eoan, Focal == Multiple squashfs filesystems with overlayfs cause file corruption issues when modifying zero sized files == Fix == The current fix is pending in https://github.com/amir73il/linux/commit/b2d4f0ea5af42e16e154254de99da064f3ac551a == Test case == With an Ubuntu ISO on the cdrom drive, use: #!/bin/bash -x mkdir -p /cdrom mount -t iso9660 -o ro,noatime /dev/sr0 /cdrom sleep 1 mkdir -p /cow mount -t tmpfs -o 'rw,noatime,mode=755' tmpfs /cow sleep 1 mkdir -p /cow/upper mkdir -p /cow/work modprobe -q -b overlay sleep 1 modprobe -q -b loop sleep 1 dev=$(losetup -f) mkdir -p /filesystem.squashfs losetup $dev /cdrom/casper/filesystem.squashfs mount -t squashfs -o ro,noatime $dev /filesystem.squashfs sleep 1 dev=$(losetup -f) mkdir -p /installer.squashfs losetup $dev /cdrom/casper/installer.squashfs mount -t squashfs -o ro,noatime $dev /installer.squashfs sleep 1 mkdir -p /root-tmp mount -t overlay -o 'upperdir=/cow/upper,lowerdir=/installer.squashfs:/filesystem.squashfs,workdir=/cow/work' /cow /root-tmp FILE=/root-tmp/etc/.pwd.lock echo foo > $FILE cat $FILE sync # # dropping caches or remounting causes the bug # echo 3 > /proc/sys/vm/drop_caches cat $FILE Without the fix the cat of the file will produce an error. With the the cat will work correctly. == Regression Potential == There is an unhandled corner case: - two filesystems, A and B, both have null uuid - upper layer is on A - lower layer 1 is also on A - lower layer 2 is on B However, since this is an issue without the fix and will be addressed later with subsequent fixes once they are OK with upstream I think the risk is minimal considering nobody is complaining about these corner cases with the current broken overlayfs squashfs layering. --- 1) Download focal subiquity pending image, or eoan release image 2) boot, and press ESC and edit boot command line (F6 in bios, e in UEFI) 3) After --- insert the following options break=top debug init=/bin/bash 4) Continue boot (Enter in BIOS, ctrl+x in UEFI) 5) in the initramfs execute: rm /scripts/casper-bottom/25adduser exit 6) you will be dropped into pivoted root filesystem, before systemd is execed as pid one 7) /run/initramfs/ will contain a debug log, showing how everything was mounted. Ie. cdrom mounted, squashfs losetup from there, then multilower overlay setup from them, moved to /root, and then pivot-root to /root done to finally end up as /. Underlying layers are moved into /cow for your convenience. 8) At this point modifying zero-byte length files, that exist in the lowest layer, but not the middle one, in certain ways, will results in them to be corrupted, after / is remounted. 9) Corruption examples (On both focal & eoan) cat /etc/.pwd.lock systemd-sysusers cat /etc/.pwd.lock mount -o remount / cat /etc/.pwd.lock overlayfs: invalid origin (etc/.pwd.lock, ftype=8000, origin ftype=4000) cat: /etc/.pwd.lock: Input/output error (Only on eoan) cat /etc/machine-id systemd-machine-id-setup cat /etc/machine-id mount -o remount / cat /etc/machine-id overlayfs: invalid origin (etc/machine-id, ftype=8000, origin ftype=4000) cat: /etc/machine-id: Input/output error Lots of things break once machine-id and .pwd.lock are corrupted. I.e. unable to dhcp, connect to dbus, add/remove/change users or groups, etc. We were unable to recreate the issue outside of booting things with casper. Ie. statically on a regular host machine without pivot-root. But hopefully booting to a quite state with nothing running is sufficient to reproduce this. Instead of booting with `bebroken init=/bin/bash` you can boot with `bebroken systemd.mask=systemd-remount-fs.service` this will complete the boot, with /etc/machine-id & .pwd.lock modified, meaning that remount of / will cause IO errors on those files. Currently, we are shipping two hacks in casper's 25adduser
[Kernel-packages] [Bug 1854329] Re: Synaptics Touchpad "loosing sync" on HP laptop
No, it does not help. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1854329 Title: Synaptics Touchpad "loosing sync" on HP laptop Status in linux package in Ubuntu: Confirmed Bug description: I have a problem with the touchpad on HP 15-db1041nm (AMD Ryzen 5 3500U). The touchpad freezes for a few seconds then resumes working. There are also freezes when typing where letters repeat, so instead of the letter r i get r. This may be a different and unrelated bug which I will open, but I'm mentioning as the built-in keyboard could be attached to the same bus? This is similar to bug #1803171, but on HP. I was instructed to report a new bug. Attached is dmesg | grep psmouse showing the sync problems that appear. Description: Ubuntu 19.10 Release: 19.10 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-10-28 (30 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Package: linux (not installed) Tags: eoan Uname: Linux 5.4.0-050400-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin lxd plugdev sambashare sudo video _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: milan 951 F pulseaudio /dev/snd/controlC0: milan 951 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-10-28 (30 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) IwConfig: lono wireless extensions. eno1 no wireless extensions. MachineType: HP HP Laptop 15-db1xxx Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic root=UUID=c6d5dded-989d-4d10-a52c-4e53aaaba9d2 ro mitigations=off quiet splash mitigations=off vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 RelatedPackageVersions: linux-restricted-modules-5.3.0-23-generic N/A linux-backports-modules-5.3.0-23-generic N/A linux-firmware1.183.2 RfKill: Tags: eoan Uname: Linux 5.3.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin lxd plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 06/27/2019 dmi.bios.vendor: Insyde dmi.bios.version: F.12 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 85EA dmi.board.vendor: HP dmi.board.version: 51.16 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.12:bd06/27/2019:svnHP:pnHPLaptop15-db1xxx:pvrType1ProductConfigId:rvnHP:rn85EA:rvr51.16:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15-db1xxx dmi.product.sku: 6VK24EA#BED dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1854329/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1846140] Re: Realtek RTL8723BU doesn't work well in ubuntu
Do you know if the fix is in mainline now? Thanks. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1846140 Title: Realtek RTL8723BU doesn't work well in ubuntu Status in linux package in Ubuntu: Confirmed Bug description: I have one laptop with Realtek RTL8723BU wifi card. It runs, but signal is weak (it only works if the router is less than a meter away), and even if it gets signal it's slow and it gets interrupted frequently. In windows it works normally, and with a much stronger signal. I tested it on Ubuntu 18.04.3 and 19.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1846140/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1855546] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1855546 Title: Desktop freezes a while than logs out Status in linux package in Ubuntu: Confirmed Bug description: In the last few months I often experience the following symptom. The Ubuntu desktop freezes for 2-3 minutes, then automatically logs out without any user interaction. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-72-generic 4.15.0-72.81 ProcVersionSignature: Ubuntu 4.15.0-72.81-generic 4.15.18 Uname: Linux 4.15.0-72-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: laca 2067 F pulseaudio /dev/snd/controlC2: laca 2067 F pulseaudio /dev/snd/controlC1: laca 2067 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Dec 7 16:01:15 2019 HibernationDevice: RESUME=UUID=9b9553b2-3060-4b74-9890-16e50d306f43 InstallationDate: Installed on 2018-08-25 (469 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. Inspiron 5548 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-72-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-72-generic N/A linux-backports-modules-4.15.0-72-generic N/A linux-firmware 1.173.12 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/04/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A02 dmi.board.name: 079JDM dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A02 dmi.modalias: dmi:bvnDellInc.:bvrA02:bd12/04/2014:svnDellInc.:pnInspiron5548:pvrA02:rvnDellInc.:rn079JDM:rvrA00:cvnDellInc.:ct8:cvrA02: dmi.product.name: Inspiron 5548 dmi.product.version: A02 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855546/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1855546] [NEW] Desktop freezes a while than logs out
Public bug reported: In the last few months I often experience the following symptom. The Ubuntu desktop freezes for 2-3 minutes, then automatically logs out without any user interaction. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-72-generic 4.15.0-72.81 ProcVersionSignature: Ubuntu 4.15.0-72.81-generic 4.15.18 Uname: Linux 4.15.0-72-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: laca 2067 F pulseaudio /dev/snd/controlC2: laca 2067 F pulseaudio /dev/snd/controlC1: laca 2067 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Dec 7 16:01:15 2019 HibernationDevice: RESUME=UUID=9b9553b2-3060-4b74-9890-16e50d306f43 InstallationDate: Installed on 2018-08-25 (469 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. Inspiron 5548 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-72-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-72-generic N/A linux-backports-modules-4.15.0-72-generic N/A linux-firmware 1.173.12 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/04/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A02 dmi.board.name: 079JDM dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A02 dmi.modalias: dmi:bvnDellInc.:bvrA02:bd12/04/2014:svnDellInc.:pnInspiron5548:pvrA02:rvnDellInc.:rn079JDM:rvrA00:cvnDellInc.:ct8:cvrA02: dmi.product.name: Inspiron 5548 dmi.product.version: A02 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug 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/1855546 Title: Desktop freezes a while than logs out Status in linux package in Ubuntu: New Bug description: In the last few months I often experience the following symptom. The Ubuntu desktop freezes for 2-3 minutes, then automatically logs out without any user interaction. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-72-generic 4.15.0-72.81 ProcVersionSignature: Ubuntu 4.15.0-72.81-generic 4.15.18 Uname: Linux 4.15.0-72-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: laca 2067 F pulseaudio /dev/snd/controlC2: laca 2067 F pulseaudio /dev/snd/controlC1: laca 2067 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Dec 7 16:01:15 2019 HibernationDevice: RESUME=UUID=9b9553b2-3060-4b74-9890-16e50d306f43 InstallationDate: Installed on 2018-08-25 (469 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. Inspiron 5548 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-72-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-72-generic N/A linux-backports-modules-4.15.0-72-generic N/A linux-firmware 1.173.12 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/04/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A02 dmi.board.name: 079JDM dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A02 dmi.modalias: dmi:bvnDellInc.:bvrA02:bd12/04/2014:svnDellInc.:pnInspiron5548:pvrA02:rvnDellInc.:rn079JDM:rvrA00:cvnDellInc.:ct8:cvrA02: dmi.product.name: Inspiron 5548 dmi.product.version: A02 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855546/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1855542] Re: Touchpad not working
EVTEST log ** Attachment added: "EVTEST log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855542/+attachment/5310515/+files/evtest -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1855542 Title: Touchpad not working Status in linux package in Ubuntu: Confirmed Bug description: After installation "zsh-autosuggestions", following instructions on: https://github.com/zsh-users/zsh- autosuggestions/blob/master/INSTALL.md , my note touchpad stopped work. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-72-generic 4.15.0-72.81 ProcVersionSignature: Ubuntu 4.15.0-72.81-generic 4.15.18 Uname: Linux 4.15.0-72-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: leandro2537 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Dec 7 11:07:08 2019 InstallationDate: Installed on 2018-12-06 (366 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 80YH ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-72-generic root=UUID=d1ee713a-114d-4799-9071-37939c97549c ro i8042.reset quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-72-generic N/A linux-backports-modules-4.15.0-72-generic N/A linux-firmware 1.173.12 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/30/2017 dmi.bios.vendor: LENOVO dmi.bios.version: 4WCN29WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Cairo 5A dmi.board.vendor: LENOVO dmi.board.version: SDK0J40688 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 320-15IKB dmi.modalias: dmi:bvnLENOVO:bvr4WCN29WW:bd09/30/2017:svnLENOVO:pn80YH:pvrLenovoideapad320-15IKB:rvnLENOVO:rnCairo5A:rvrSDK0J40688WIN:cvnLENOVO:ct10:cvrLenovoideapad320-15IKB: dmi.product.family: IDEAPAD dmi.product.name: 80YH dmi.product.version: Lenovo ideapad 320-15IKB dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855542/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1855541] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1855541 Title: Newer Kernel Versions Cause Kernel Panic Status in linux package in Ubuntu: Confirmed Bug description: Since installing and updating the kernel a couple times (new install was 2 days ago), I logged out after installing, had a windows session and wanted to start Ubuntu again, but ran into a "Kernel Panic Not Syncing: fatal exception in interrupt" with every version other version newer to this one (xx-19, 23, 24). ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-18-generic 5.3.0-18.19+1 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tuto 1246 F pulseaudio /dev/snd/controlC0: tuto 1246 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Dec 7 15:08:18 2019 InstallationDate: Installed on 2019-12-04 (2 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Notebook P17SM ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-18-generic root=UUID=c53e7d61-4e51-44c5-ac1b-183f309b6854 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-18-generic N/A linux-backports-modules-5.3.0-18-generic N/A linux-firmware1.183.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/26/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: P17SM dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd12/26/2013:svnNotebook:pnP17SM:pvrNotApplicable:rvnNotebook:rnP17SM:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: P17SM 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/1855541/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1855542] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1855542 Title: Touchpad not working Status in linux package in Ubuntu: Confirmed Bug description: After installation "zsh-autosuggestions", following instructions on: https://github.com/zsh-users/zsh- autosuggestions/blob/master/INSTALL.md , my note touchpad stopped work. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-72-generic 4.15.0-72.81 ProcVersionSignature: Ubuntu 4.15.0-72.81-generic 4.15.18 Uname: Linux 4.15.0-72-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: leandro2537 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Dec 7 11:07:08 2019 InstallationDate: Installed on 2018-12-06 (366 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 80YH ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-72-generic root=UUID=d1ee713a-114d-4799-9071-37939c97549c ro i8042.reset quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-72-generic N/A linux-backports-modules-4.15.0-72-generic N/A linux-firmware 1.173.12 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/30/2017 dmi.bios.vendor: LENOVO dmi.bios.version: 4WCN29WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Cairo 5A dmi.board.vendor: LENOVO dmi.board.version: SDK0J40688 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 320-15IKB dmi.modalias: dmi:bvnLENOVO:bvr4WCN29WW:bd09/30/2017:svnLENOVO:pn80YH:pvrLenovoideapad320-15IKB:rvnLENOVO:rnCairo5A:rvrSDK0J40688WIN:cvnLENOVO:ct10:cvrLenovoideapad320-15IKB: dmi.product.family: IDEAPAD dmi.product.name: 80YH dmi.product.version: Lenovo ideapad 320-15IKB dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855542/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1855542] [NEW] Touchpad not working
Public bug reported: After installation "zsh-autosuggestions", following instructions on: https://github.com/zsh-users/zsh-autosuggestions/blob/master/INSTALL.md , my note touchpad stopped work. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-72-generic 4.15.0-72.81 ProcVersionSignature: Ubuntu 4.15.0-72.81-generic 4.15.18 Uname: Linux 4.15.0-72-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: leandro2537 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Dec 7 11:07:08 2019 InstallationDate: Installed on 2018-12-06 (366 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 80YH ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-72-generic root=UUID=d1ee713a-114d-4799-9071-37939c97549c ro i8042.reset quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-72-generic N/A linux-backports-modules-4.15.0-72-generic N/A linux-firmware 1.173.12 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/30/2017 dmi.bios.vendor: LENOVO dmi.bios.version: 4WCN29WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Cairo 5A dmi.board.vendor: LENOVO dmi.board.version: SDK0J40688 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 320-15IKB dmi.modalias: dmi:bvnLENOVO:bvr4WCN29WW:bd09/30/2017:svnLENOVO:pn80YH:pvrLenovoideapad320-15IKB:rvnLENOVO:rnCairo5A:rvrSDK0J40688WIN:cvnLENOVO:ct10:cvrLenovoideapad320-15IKB: dmi.product.family: IDEAPAD dmi.product.name: 80YH dmi.product.version: Lenovo ideapad 320-15IKB dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug bionic ** Attachment added: "devices" https://bugs.launchpad.net/bugs/1855542/+attachment/5310498/+files/devices -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1855542 Title: Touchpad not working Status in linux package in Ubuntu: Confirmed Bug description: After installation "zsh-autosuggestions", following instructions on: https://github.com/zsh-users/zsh- autosuggestions/blob/master/INSTALL.md , my note touchpad stopped work. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-72-generic 4.15.0-72.81 ProcVersionSignature: Ubuntu 4.15.0-72.81-generic 4.15.18 Uname: Linux 4.15.0-72-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: leandro2537 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Dec 7 11:07:08 2019 InstallationDate: Installed on 2018-12-06 (366 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 80YH ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-72-generic root=UUID=d1ee713a-114d-4799-9071-37939c97549c ro i8042.reset quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-72-generic N/A linux-backports-modules-4.15.0-72-generic N/A linux-firmware 1.173.12 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/30/2017 dmi.bios.vendor: LENOVO dmi.bios.version: 4WCN29WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Cairo 5A dmi.board.vendor: LENOVO dmi.board.version: SDK0J40688 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 320-15IKB dmi.modalias: dmi:bvnLENOVO:bvr4WCN29WW:bd09/30/2017:svnLENOVO:pn80YH:pvrLenovoideapad320-15IKB:rvnLENOVO:rnCairo5A:rvrSDK0J40688WIN:cvnLENOVO:ct10:cvrLenovoideapad320-15IKB: dmi.product.family: IDEAPAD dmi.product.name: 80YH dmi.product.version: Lenovo ideapad 320-15IKB dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855542/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1855541] [NEW] Newer Kernel Versions Cause Kernel Panic
Public bug reported: Since installing and updating the kernel a couple times (new install was 2 days ago), I logged out after installing, had a windows session and wanted to start Ubuntu again, but ran into a "Kernel Panic Not Syncing: fatal exception in interrupt" with every version other version newer to this one (xx-19, 23, 24). ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-18-generic 5.3.0-18.19+1 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tuto 1246 F pulseaudio /dev/snd/controlC0: tuto 1246 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Dec 7 15:08:18 2019 InstallationDate: Installed on 2019-12-04 (2 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Notebook P17SM ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-18-generic root=UUID=c53e7d61-4e51-44c5-ac1b-183f309b6854 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-18-generic N/A linux-backports-modules-5.3.0-18-generic N/A linux-firmware1.183.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/26/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: P17SM dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd12/26/2013:svnNotebook:pnP17SM:pvrNotApplicable:rvnNotebook:rnP17SM:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: P17SM dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1855541 Title: Newer Kernel Versions Cause Kernel Panic Status in linux package in Ubuntu: New Bug description: Since installing and updating the kernel a couple times (new install was 2 days ago), I logged out after installing, had a windows session and wanted to start Ubuntu again, but ran into a "Kernel Panic Not Syncing: fatal exception in interrupt" with every version other version newer to this one (xx-19, 23, 24). ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-18-generic 5.3.0-18.19+1 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tuto 1246 F pulseaudio /dev/snd/controlC0: tuto 1246 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Dec 7 15:08:18 2019 InstallationDate: Installed on 2019-12-04 (2 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Notebook P17SM ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-18-generic root=UUID=c53e7d61-4e51-44c5-ac1b-183f309b6854 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-18-generic N/A linux-backports-modules-5.3.0-18-generic N/A linux-firmware1.183.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/26/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: P17SM dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd12/26/2013:svnNotebook:pnP17SM:pvrNotApplicable:rvnNotebook:rnP17SM:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: P17SM 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/1855541/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1855518] Re: Dell XPS13, Ubuntu 18.04: Trackpad stopped working
*** This bug is a duplicate of bug 1854798 *** https://bugs.launchpad.net/bugs/1854798 Confirmed as duplicate: I can revert to the 4.15.0-70 kernel and the trackpad starts working again. A strange thing happened when I tried to retrieve the log. apport-collect 1855518 ERROR: The python3-launchpadlib package is not installed. This functionality is not available. But then: sudo apt install python3-launchpadlib python3-launchpadlib is already the newest version (1.10.6-1). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1855518 Title: Dell XPS13, Ubuntu 18.04: Trackpad stopped working Status in linux package in Ubuntu: Incomplete Bug description: When I opened my laptop this morning (Dell XPS13, purchased in fall 2014), the trackpad no longer worked. No touchpad appears when typing "xinput list". Submitting bug report per advice at https://wiki.ubuntu.com/DebuggingTouchpadDetection Contents of "/proc/bus/input/devices" attached. Thank you! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855518/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1854842] Re: mlx5_core reports hardware checksum error for padded packets on Mellanox NICs
Hi Matthew, Thank you for your effort :). please let me know if you need any help with the backporting. Thanks, Mohammad -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1854842 Title: mlx5_core reports hardware checksum error for padded packets on Mellanox NICs Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: In Progress Bug description: Hi, we have the following issue which affects a lot of our customers this issue fixes upstream and need to add the fixes to ubuntu 18.04. Mlx5 driver: Tail padding HW Checksum crash in Ubuntu 18.04 kernel Ubuntu-4.15.0-72 Crach log: [ 785.337368] Call Trace: [ 785.337372] [ 785.337388] dump_stack+0x63/0x8e [ 785.337397] netdev_rx_csum_fault+0x38/0x40 [ 785.337403] __skb_checksum_complete+0xbc/0xd0 [ 785.337408] nf_ip_checksum+0xc3/0xf0 [ 785.337417] icmp_error+0x27d/0x310 [nf_conntrack_ipv4] [ 785.337431] nf_conntrack_in+0x15a/0x510 [nf_conntrack] [ 785.337437] ? __skb_checksum+0x68/0x330 [ 785.337441] ipv4_conntrack_in+0x1c/0x20 [nf_conntrack_ipv4] [ 785.337449] nf_hook_slow+0x48/0xc0 [ 785.337452] ? skb_send_sock+0x50/0x50 [ 785.337460] ip_rcv+0x301/0x360 [ 785.337463] ? inet_del_offload+0x40/0x40 [ 785.337468] __netif_receive_skb_core+0x432/0xb80 [ 785.337473] __netif_receive_skb+0x18/0x60 [ 785.337477] ? __netif_receive_skb+0x18/0x60 [ 785.337481] netif_receive_skb_internal+0x45/0xe0 [ 785.337483] napi_gro_receive+0xc5/0xf0 [ 785.337517] mlx5e_handle_rx_cqe+0x48d/0x5e0 [mlx5_core] [ 785.337524] ? enqueue_task_rt+0x1b4/0x2e0 [ 785.337546] mlx5e_poll_rx_cq+0xd1/0x8c0 [mlx5_core] [ 785.337566] mlx5e_napi_poll+0x9d/0x290 [mlx5_core] [ 785.337569] net_rx_action+0x140/0x3a0 [ 785.337574] __do_softirq+0xe4/0x2d4 [ 785.337580] irq_exit+0xc5/0xd0 [ 785.337583] do_IRQ+0x86/0xe0 [ 785.337588] common_interrupt+0x8c/0x8c [ 785.337590] [ 785.337598] RIP: 0010:cpuidle_enter_state+0xa4/0x2f0 [ 785.337600] RSP: 0018:ad8d8329fe68 EFLAGS: 0246 ORIG_RAX: ffd9 [ 785.337604] RAX: 8a6c7f7e1840 RBX: 00b6d9bf6a06 RCX: 001f [ 785.337605] RDX: 00b6d9bf6a06 RSI: ffd4a4b4c86359ce RDI: [ 785.337607] RBP: ad8d8329fea8 R08: 0004 R09: 00021080 [ 785.337609] R10: ad8d8329fe38 R11: 0056b80166a42400 R12: 8a6c7f7ece18 [ 785.337610] R13: 0005 R14: aff73438 R15: [HOW TO REPRODUCE]: with scapy on the sender side please run the following commands: 1) a=Ether(dst='ff:ff:ff:ff:ff:ff')/IP(dst='127.0.0.1')/ICMP()/Padding(load='\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe') 2) sendp(a, iface='enp6s0f0') 3) check the dmesg i the receiver side [ADDITIONAL INFO]: This issue fixes upstream by the following set of patches: net/mlx5e: Rx, Fix checksum calculation for new hardware --> db849faa9bef993a1379dc510623f750a72fa7ce net/mlx5e: Rx, Check ip headers sanity - > 0318a7b7fcad9765931146efa7ca3a034194737c net/mlx5e: Rx, Fixup skb checksum for packets with tail padding --> 0aa1d18615c163f92935b806dcaff9157645233a net/mlx5e: XDP, Avoid checksum complete when XDP prog is loaded --> 5d0bb3bac4b9f6c22280b04545626fdfd99edc6b mlx5: fix get_ip_proto() --> ef6fcd455278c2be3032a346cc66d9dd9866b787 net/mlx5e: Allow reporting of checksum unnecessary --> b856df28f9230a47669efbdd57896084caadb2b3 net/mlx5e: don't set CHECKSUM_COMPLETE on SCTP packets --> fe1dc069990c1f290ef6b99adb46332c03258f38 net/mlx5e: Set ECN for received packets using CQE indication --> f007c13d4ad62f494c83897eda96437005df4a91 net/mlx5e: Add likely to the common RX checksum flow --> 63a612f984a1fae040ab6f1c6a0f1fdcdf1954b8 net/mlx5e: CHECKSUM_COMPLETE offload for VLAN/QinQ packets --> f938daeee95eb36ef6b431bf054a5cc6cdada112 attached the /var/log/kern.log file. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1854842/+subscriptions -- Mailing list:
[Kernel-packages] [Bug 1854842] Re: mlx5_core reports hardware checksum error for padded packets on Mellanox NICs
Hi Mohammad, I have backported: Subject: net/mlx5e: Rx, Fixup skb checksum for packets with tail padding Commit: 0aa1d18615c163f92935b806dcaff9157645233a to the bionic 4.15 kernel: https://paste.ubuntu.com/p/Svfp8DQGRP/ The test kernel is currently building in: https://launchpad.net/~mruffell/+archive/ubuntu/lp1854842-test Once the kernel is built and I have tested it to ensure it built correctly, I will provide instructions for you to test the kernel, since I cannot reproduce due to my lab not having any Mellanox NICs. I have started looking into Subject: net/mlx5e: Rx, Fix checksum calculation for new hardware Commit: db849faa9bef993a1379dc510623f750a72fa7ce and will likely start backporting this and doing a test kernel when I get in on Monday. I will let you know when the test kernel is ready. Thanks, Matthew -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1854842 Title: mlx5_core reports hardware checksum error for padded packets on Mellanox NICs Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: In Progress Bug description: Hi, we have the following issue which affects a lot of our customers this issue fixes upstream and need to add the fixes to ubuntu 18.04. Mlx5 driver: Tail padding HW Checksum crash in Ubuntu 18.04 kernel Ubuntu-4.15.0-72 Crach log: [ 785.337368] Call Trace: [ 785.337372] [ 785.337388] dump_stack+0x63/0x8e [ 785.337397] netdev_rx_csum_fault+0x38/0x40 [ 785.337403] __skb_checksum_complete+0xbc/0xd0 [ 785.337408] nf_ip_checksum+0xc3/0xf0 [ 785.337417] icmp_error+0x27d/0x310 [nf_conntrack_ipv4] [ 785.337431] nf_conntrack_in+0x15a/0x510 [nf_conntrack] [ 785.337437] ? __skb_checksum+0x68/0x330 [ 785.337441] ipv4_conntrack_in+0x1c/0x20 [nf_conntrack_ipv4] [ 785.337449] nf_hook_slow+0x48/0xc0 [ 785.337452] ? skb_send_sock+0x50/0x50 [ 785.337460] ip_rcv+0x301/0x360 [ 785.337463] ? inet_del_offload+0x40/0x40 [ 785.337468] __netif_receive_skb_core+0x432/0xb80 [ 785.337473] __netif_receive_skb+0x18/0x60 [ 785.337477] ? __netif_receive_skb+0x18/0x60 [ 785.337481] netif_receive_skb_internal+0x45/0xe0 [ 785.337483] napi_gro_receive+0xc5/0xf0 [ 785.337517] mlx5e_handle_rx_cqe+0x48d/0x5e0 [mlx5_core] [ 785.337524] ? enqueue_task_rt+0x1b4/0x2e0 [ 785.337546] mlx5e_poll_rx_cq+0xd1/0x8c0 [mlx5_core] [ 785.337566] mlx5e_napi_poll+0x9d/0x290 [mlx5_core] [ 785.337569] net_rx_action+0x140/0x3a0 [ 785.337574] __do_softirq+0xe4/0x2d4 [ 785.337580] irq_exit+0xc5/0xd0 [ 785.337583] do_IRQ+0x86/0xe0 [ 785.337588] common_interrupt+0x8c/0x8c [ 785.337590] [ 785.337598] RIP: 0010:cpuidle_enter_state+0xa4/0x2f0 [ 785.337600] RSP: 0018:ad8d8329fe68 EFLAGS: 0246 ORIG_RAX: ffd9 [ 785.337604] RAX: 8a6c7f7e1840 RBX: 00b6d9bf6a06 RCX: 001f [ 785.337605] RDX: 00b6d9bf6a06 RSI: ffd4a4b4c86359ce RDI: [ 785.337607] RBP: ad8d8329fea8 R08: 0004 R09: 00021080 [ 785.337609] R10: ad8d8329fe38 R11: 0056b80166a42400 R12: 8a6c7f7ece18 [ 785.337610] R13: 0005 R14: aff73438 R15: [HOW TO REPRODUCE]: with scapy on the sender side please run the following commands: 1) a=Ether(dst='ff:ff:ff:ff:ff:ff')/IP(dst='127.0.0.1')/ICMP()/Padding(load='\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe') 2) sendp(a, iface='enp6s0f0') 3) check the dmesg i the receiver side [ADDITIONAL INFO]: This issue fixes upstream by the following set of patches: net/mlx5e: Rx, Fix checksum calculation for new hardware --> db849faa9bef993a1379dc510623f750a72fa7ce net/mlx5e: Rx, Check ip headers sanity - > 0318a7b7fcad9765931146efa7ca3a034194737c net/mlx5e: Rx, Fixup skb checksum for packets with tail padding --> 0aa1d18615c163f92935b806dcaff9157645233a net/mlx5e: XDP, Avoid checksum complete when XDP prog is loaded --> 5d0bb3bac4b9f6c22280b04545626fdfd99edc6b mlx5: fix get_ip_proto() --> ef6fcd455278c2be3032a346cc66d9dd9866b787 net/mlx5e: Allow reporting of
[Kernel-packages] [Bug 1854749] Re: eoan/linux-azure: 5.3.0-1009.10 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/security-signoff Assignee: Canonical Security Team (canonical-security) => Steve Beattie (sbeattie) -- 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/1854749 Title: eoan/linux-azure: 5.3.0-1009.10 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress 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-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: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Eoan: Confirmed 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: 1854762 packages: lrm: linux-restricted-modules-azure main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Friday, 06. December 2019 22:26 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff stakeholder-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-azure-5.3: bug 1854747 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1854749/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1854797] Re: bionic/linux-oem: 4.15.0-1066.76 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/security-signoff Assignee: Canonical Security Team (canonical-security) => Steve Beattie (sbeattie) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1854797 Title: bionic/linux-oem: 4.15.0-1066.76 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress Status in Kernel SRU Workflow certification-testing series: Confirmed 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: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-oem package in Ubuntu: Invalid Status in linux-oem source package in Bionic: Confirmed 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: 1854819 packages: lrm: linux-restricted-modules-oem main: linux-oem meta: linux-meta-oem signed: linux-signed-oem phase: Testing phase-changed: Friday, 06. December 2019 22:27 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1854797/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1810183] Re: numpad on touchpad doesn't work in ASUS Zenbook 14
Hi everyone, same here with ubuntu 19.10 and with asus vivobook S14 X420F. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1810183 Title: numpad on touchpad doesn't work in ASUS Zenbook 14 Status in Linux: New Status in linux package in Ubuntu: Confirmed Bug description: I have Asus Zenbook 14 UX433FA which I have installed Ubuntu 18.10 alongside windows 10. The numeric keypads are within the touchpad and are supposed to be turned on by a button on the touchpad. This works well in Windows but doesn't work in Ubuntu. I have tried to search for any related problems/solutions online but I haven't been able to. I will appreciate any suggestion or help. Thanks, --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-12-30 (4 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Package: linux (not installed) Tags: cosmic Uname: Linux 4.19.11-041911-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-12-30 (4 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Package: linux (not installed) Tags: cosmic Uname: Linux 4.18.10-041810-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1810183/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
