[Kernel-packages] [Bug 1885671] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1885671 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1885671 Title: Touchpad is not detected - HP Probok 430 G2 Status in linux package in Ubuntu: Incomplete Bug description: Hi Touchpad is not detected in my newly installed Ububtu 5.4.0-39. I have checked "/proc/bus/input/devices" but havent seen any TouchPad info Device: HP ProBookk 430 G2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1885671/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1885671] Re: Touchpad is not detected - HP Probok 430 G2
Logfile has been attached ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1885671 Title: Touchpad is not detected - HP Probok 430 G2 Status in linux package in Ubuntu: Confirmed Bug description: Hi Touchpad is not detected in my newly installed Ububtu 5.4.0-39. I have checked "/proc/bus/input/devices" but havent seen any TouchPad info Device: HP ProBookk 430 G2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1885671/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1825636] Re: Battery drain during sleep. System suspended before kernel suspends all tasks
I'm no kernel triager but I have a few observations that can help focusing the bug report: 1. Are people manually installing tlp and that causing problems, or do people experience this too with vanilla installation of Ubuntu? (tlp is not part of the default install, and not in the 'main' supported packages, but definitely power management is optimized as is, ie many of the settings tlp would set are the default anyway in Ubuntu) 2. It may be useful to rule out it's not case of bug 1808957, some people here might be here because of it, ie check cat /sys/power/mem_sleep and if it says s2idle, then you've an unfortunate configuration problem, you can add mem_sleep_default=deep to grub config. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1825636 Title: Battery drain during sleep. System suspended before kernel suspends all tasks Status in linux package in Ubuntu: Confirmed Status in linux-signed-hwe package in Ubuntu: Confirmed Bug description: Description: Ubuntu 18.04.2 LTS Release: 18.04 Expected behaviour: No battery drain during suspend. Ubuntu 18.04 running on a Thinkpad L390 has battery drain during suspend (~10% in 5 hours) in. I excluded wake ups during sleep and checking the logs I have realized that the kernel suspends too fast, before the full system is put to sleep. Here are the syslogs after initiating the suspend mode: Apr 19 11:59:53 ThinkPad-L390 systemd[1]: Starting TLP suspend/resume... Apr 19 11:59:53 ThinkPad-L390 systemd[1]: Started TLP suspend/resume. Apr 19 11:59:53 ThinkPad-L390 systemd[1]: Reached target Sleep. Apr 19 11:59:53 ThinkPad-L390 systemd[1]: Starting Suspend... Apr 19 11:59:53 ThinkPad-L390 kernel: [15459.897941] PM: suspend entry (deep) Apr 19 11:59:53 ThinkPad-L390 systemd-sleep[28261]: Suspending system... Apr 19 11:59:53 ThinkPad-L390 kernel: [15459.897944] PM: Syncing filesystems ... done. And here the syslogs directly after waking up: Apr 19 12:37:50 ThinkPad-L390 kernel: [15459.906928] Freezing user space processes ... (elapsed 0.004 seconds) done. Apr 19 12:37:50 ThinkPad-L390 kernel: [15459.910995] OOM killer disabled. Apr 19 12:37:50 ThinkPad-L390 kernel: [15459.910996] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. Apr 19 12:37:50 ThinkPad-L390 kernel: [15459.912868] Suspending console(s) (use no_console_suspend to debug) Apr 19 12:37:50 ThinkPad-L390 kernel: [15460.032873] e1000e: EEE TX LPI TIMER: 0011 Apr 19 12:37:50 ThinkPad-L390 kernel: [15460.204567] ACPI: EC: interrupt blocked Apr 19 12:37:50 ThinkPad-L390 kernel: [15460.243401] ACPI: Preparing to enter system sleep state S3 Apr 19 12:37:50 ThinkPad-L390 kernel: [15460.249397] ACPI: EC: event blocked Apr 19 12:37:50 ThinkPad-L390 kernel: [15460.249398] ACPI: EC: EC stopped Apr 19 12:37:50 ThinkPad-L390 kernel: [15460.249399] PM: Saving platform NVS memory Apr 19 12:37:50 ThinkPad-L390 kernel: [15460.249432] Disabling non-boot CPUs ... Apr 19 12:37:50 ThinkPad-L390 kernel: [15460.263401] irq_migrate_all_off_this_cpu: 5 callbacks suppressed Apr 19 12:37:50 ThinkPad-L390 kernel: [15460.263403] IRQ 141: no longer affine to CPU1 Apr 19 12:37:50 ThinkPad-L390 kernel: [15460.264445] smpboot: CPU 1 is now offline Apr 19 12:37:50 ThinkPad-L390 kernel: [15460.296469] smpboot: CPU 2 is now offline Apr 19 12:37:50 ThinkPad-L390 kernel: [15460.320478] smpboot: CPU 3 is now offline Apr 19 12:37:50 ThinkPad-L390 kernel: [15460.343319] IRQ 149: no longer affine to CPU4 Apr 19 12:37:50 ThinkPad-L390 kernel: [15460.345025] smpboot: CPU 4 is now offline Apr 19 12:37:50 ThinkPad-L390 kernel: [15460.375279] IRQ 17: no longer affine to CPU5 Apr 19 12:37:50 ThinkPad-L390 kernel: [15460.375285] IRQ 18: no longer affine to CPU5 Apr 19 12:37:50 ThinkPad-L390 kernel: [15460.375298] IRQ 148: no longer affine to CPU5 Apr 19 12:37:50 ThinkPad-L390 kernel: [15460.376311] smpboot: CPU 5 is now offline Apr 19 12:37:50 ThinkPad-L390 kernel: [15460.399234] IRQ 124: no longer affine to CPU6 Apr 19 12:37:50 ThinkPad-L390 kernel: [15460.400265] smpboot: CPU 6 is now offline Apr 19 12:37:50 ThinkPad-L390 kernel: [15460.423211] IRQ 123: no longer affine to CPU7 Apr 19 12:37:50 ThinkPad-L390 kernel: [15460.423222] IRQ 139: no longer affine to CPU7 Apr 19 12:37:50 ThinkPad-L390 kernel: [15460.423228] IRQ 140: no longer affine to CPU7 Apr 19 12:37:50 ThinkPad-L390 kernel: [15460.423235] IRQ 142: no longer affine to CPU7 Apr 19 12:37:50 ThinkPad-L390 kernel: [15460.424278] smpboot: CPU 7 is now offline Apr 19 12:37:50 ThinkPad-L390 kernel: [15460.428456] ACPI: Low-level resume complete Apr 19 12:37:50 ThinkPad-L390 kernel: [15460.428541] ACPI: EC: EC started Apr 19 12:37:50 ThinkPad-L390 kernel: [15460.428541] PM: Restoring platform NVS memory Apr 19 12:37:
[Kernel-packages] [Bug 1885087] Re: Can't keep brightness value after reboot/poweroff in some nvidia gfx
** Also affects: nvidia-graphics-drivers-440 (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: nvidia-graphics-drivers-440 (Ubuntu Focal) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Changed in: nvidia-graphics-drivers-440 (Ubuntu) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Changed in: nvidia-graphics-drivers-440 (Ubuntu) Status: New => Triaged ** Changed in: nvidia-graphics-drivers-440 (Ubuntu Focal) Status: New => Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-440 in Ubuntu. https://bugs.launchpad.net/bugs/1885087 Title: Can't keep brightness value after reboot/poweroff in some nvidia gfx Status in OEM Priority Project: Confirmed Status in OEM Priority Project focal series: New Status in nvidia-graphics-drivers-440 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-440 source package in Focal: Triaged Bug description: systemd-backlight saves the brightness value right before shutdown.target, however it doesn't work because the nvidia_0 backlight sysfs disappears after GFX device is closed by Xorg, long before shutdown.target. [Impact] System can not keep the brightness value, after reboot/poweroff the brightness will still be highest. [Fix] Suggested by Nvidia, we need to run nvidia-persistenced.service before systemd-backlight@backlight:nvidia_0.service [Test Case] Adjust the brightness value, reboot, the value must keep persistence during boots. [Regression Risk] Low, this fix is just adjust the systemd order more earier. https://github.com/hugh712/nvidia-graphics-drivers To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1885087/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1885690] [NEW] Groovy update: v5.7.6 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.7.6 upstream stable release from git://git.kernel.org/ Linux 5.7.6 iommu/vt-d: Remove real DMA lookup in find_domain net: core: device_rename: Use rwsem instead of a seqcount net: octeon: mgmt: Repair filling of RX ring e1000e: Do not wake up the system via WOL if device wakeup is disabled powerpc/64s: Fix KVM interrupt using wrong save area kretprobe: Prevent triggering kretprobe from within kprobe_flush_task kprobes: Fix to protect kick_kprobe_optimizer() by kprobe_mutex netfilter: nft_set_pipapo: Disable preemption before getting per-CPU pointer netfilter: nft_set_rbtree: Don't account for expired elements on insertion sample-trace-array: Fix sleeping function called from invalid context sample-trace-array: Remove trace_array 'sample-instance' tools/bootconfig: Fix to return 0 if succeeded to show the bootconfig tools/bootconfig: Fix to use correct quotes for value proc/bootconfig: Fix to use correct quotes for value tracing/probe: Fix memleak in fetch_op_data operations tracing: Make ftrace packed events have align of 1 crypto: algboss - don't wait during notifier callback crypto: algif_skcipher - Cap recv SG list at ctx->used drm/i915/tgl: Make Wa_14010229206 permanent Revert "drm/amd/display: disable dcn20 abm feature for bring up" drm/i915/gt: Move gen4 GT workarounds from init_clock_gating to workarounds drm/i915/gt: Move vlv GT workarounds from init_clock_gating to workarounds drm/i915/gt: Move ilk GT workarounds from init_clock_gating to workarounds drm/i915/gt: Move snb GT workarounds from init_clock_gating to workarounds drm/i915/gt: Move ivb GT workarounds from init_clock_gating to workarounds drm/i915/gt: Move hsw GT workarounds from init_clock_gating to workarounds drm/i915/gt: Incrementally check for rewinding drm/i915/tc: fix the reset of ln0 drm/i915/icl+: Fix hotplug interrupt disabling after storm detection drm/amd/display: Use kvfree() to free coeff in build_regamma() drm/amdkfd: Use correct major in devcgroup check drm/connector: notify userspace on hotplug after register complete drm/i915: Whitelist context-local timestamp in the gen9 cmdparser drm/i915/gem: Avoid iterating an empty list drm/msm: Check for powered down HW in the devfreq callbacks drm/i915: Fix AUX power domain toggling across TypeC mode resets s390: fix syscall_get_error for compat processes f2fs: avoid utf8_strncasecmp() with unstable name f2fs: split f2fs_d_compare() from f2fs_match_name() net/mlx5: DR, Fix freeing in dr_create_rc_qp() drm/dp_mst: Increase ACT retry timeout to 3s ext4: avoid race conditions when remounting with options that change dax io_uring: fix possible race condition against REQ_F_NEED_CLEANUP io_uring: reap poll completions while waiting for refs to drop on exit io_uring: acquire 'mm' for task_work for SQPOLL io_uring: add memory barrier to synchronize io_kiocb's result and iopoll_completed io_uring: don't fail links for EAGAIN error in IOPOLL mode io_uring: fix io_kiocb.flags modification race in IOPOLL mode drm/ast: Don't check new mode if CRTC is being disabled selinux: fix undefined return of cond_evaluate_expr selinux: fix a double free in cond_read_node()/cond_read_list() selinux: fix double free drm/amdgpu: Replace invalid device ID with a valid device ID drm/amdgpu/display: use blanked rather than plane state for sync groups drm/qxl: Use correct notify port address when creating cursor ring drm/dp_mst: Reformat drm_dp_check_act_status() a bit drm/nouveau/kms: Fix regression by audio component transition sh: Convert iounmap() macros to inline functions arm64: dts: realtek: rtd129x: Carve out boot ROM from memory arm64: dts: realtek: rtd129x: Use reserved-memory for RPC regions ext4, jbd2: ensure panic by fix a race between jbd2 abort and ext4 error handlers ext4: avoid utf8_strncasecmp() with unstable name ext4: fix partial cluster initialization when splitting extent pinctrl: qcom: ipq6018 Add missing pins in qpic pin group drm: encoder_slave: fix refcouting error for modules libata: Use per port sync for detach arm64: hw_breakpoint: Don't invoke overflow handler on uaccess watchpoints arm64: mm: reserve hugetlb CMA after numa_init mlxsw: spectrum: Adjust headroom buffers for 8x ports bareudp: Fixed configuration to avoid having garbage values mvpp2: remove module bugfix block: Fix use-after-free in blkdev_get() s390/numa: let NODES_SHIFT depend on NEED_MULTIPLE_NODES scsi: ufs-bsg: Fix runtime PM imbalance on error net: dsa: sja1105: fix PTP timestamping with large tc-taprio cycles bnxt
[Kernel-packages] [Bug 1653498] Re: Server reboots every 4.1 weeks
Hi, Does this issue exist on Ubuntu18.04? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1653498 Title: Server reboots every 4.1 weeks Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Confirmed Bug description: Every 4.1 uptime weeks (more or less), our 34 servers reboots with the logs below. Description:Ubuntu 16.04.1 LTS Release:16.04 The servers hosts the stack flanneld (0.5.5) docker (1.11.2, build b9f10c9) kubernetes (v1.3.6) plus etcd (2.3.7) Jan 02 06:40:32 prd-node021 kernel: [ cut here ] Jan 02 06:40:32 prd-node021 kernel: kernel BUG at /build/linux-xHzv4a/linux-4.4.0/include/linux/fs.h:2569! Jan 02 06:40:32 prd-node021 kernel: invalid opcode: [#1] SMP Jan 02 06:40:32 prd-node021 kernel: Modules linked in: nf_conntrack_netlink nfnetlink veth xt_statistic xt_nat xt_recent ipt_REJECT nf_reject_ipv4 xt_tcpudp tcp_diag inet_diag Jan 02 06:40:32 prd-node021 kernel: raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear crct10dif_pclmul crc Jan 02 06:40:32 prd-node021 kernel: CPU: 46 PID: 22749 Comm: iptables-restor Not tainted 4.4.0-47-generic #68-Ubuntu Jan 02 06:40:32 prd-node021 kernel: Hardware name: HP ProLiant DL360 Gen9/ProLiant DL360 Gen9, BIOS P89 09/13/2016 Jan 02 06:40:32 prd-node021 kernel: task: 882f7ccb44c0 ti: 882fcb81 task.ti: 882fcb81 Jan 02 06:40:32 prd-node021 kernel: RIP: 0010:[] [] __fput+0x21d/0x220 Jan 02 06:40:32 prd-node021 kernel: RSP: 0018:882fcb813e68 EFLAGS: 00010246 Jan 02 06:40:32 prd-node021 kernel: RAX: RBX: 8829dbd92700 RCX: 308c6396 Jan 02 06:40:32 prd-node021 kernel: RDX: 0001 RSI: 88301f299f60 RDI: Jan 02 06:40:32 prd-node021 kernel: RBP: 882fcb813ea0 R08: 00019f60 R09: 811b3a1d Jan 02 06:40:32 prd-node021 kernel: R10: ea0064756680 R11: 8829dbd92710 R12: 0010 Jan 02 06:40:32 prd-node021 kernel: R13: 8817d3520518 R14: 881021a34da0 R15: 8817d3542540 Jan 02 06:40:32 prd-node021 kernel: FS: 7fcdaa753700() GS:88301f28() knlGS: Jan 02 06:40:32 prd-node021 kernel: CS: 0010 DS: ES: CR0: 80050033 Jan 02 06:40:32 prd-node021 kernel: CR2: 7fcdaa758000 CR3: 001917993000 CR4: 003406e0 Jan 02 06:40:32 prd-node021 kernel: DR0: DR1: DR2: Jan 02 06:40:32 prd-node021 kernel: DR3: DR6: fffe0ff0 DR7: 0400 Jan 02 06:40:32 prd-node021 kernel: Stack: Jan 02 06:40:32 prd-node021 kernel: 8817d3520518 8829dbd92710 882f7ccb44c0 82103a30 Jan 02 06:40:32 prd-node021 kernel: 8829dbd92700 882f7ccb4b38 882fcb813eb0 Jan 02 06:40:32 prd-node021 kernel: 8120fa2e 882fcb813ef0 8109ee01 882f7ccb4b6c Jan 02 06:40:32 prd-node021 kernel: Call Trace: Jan 02 06:40:32 prd-node021 kernel: [] fput+0xe/0x10 Jan 02 06:40:32 prd-node021 kernel: [] task_work_run+0x81/0xa0 Jan 02 06:40:32 prd-node021 kernel: [] exit_to_usermode_loop+0xc2/0xd0 Jan 02 06:40:32 prd-node021 kernel: [] syscall_return_slowpath+0x4e/0x60 Jan 02 06:40:32 prd-node021 kernel: [] int_ret_from_sys_call+0x25/0x8f Jan 02 06:40:32 prd-node021 kernel: Code: 0f 84 cf fe ff ff 48 8b 43 28 48 8b 80 80 00 00 00 48 85 c0 0f 84 bb fe ff ff 31 d2 48 89 de bf ff ff ff ff ff d0 e9 aa fe ff ff <0f> Jan 02 06:40:32 prd-node021 kernel: RIP [] __fput+0x21d/0x220 -- Reboot -- Jan 02 06:42:56 prd-node021 systemd-journald[819]: Runtime journal (/run/log/journal/) is 8.0M, max 1.8G, 1.8G free. Jan 02 06:42:56 prd-node021 kernel: Initializing cgroup subsys cpuset ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-47-generic 4.4.0-47.68 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 2 06:42 seq crw-rw 1 root audio 116, 33 Jan 2 06:42 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Mon Jan 2 10:49:15 2017 HibernationDevice: RESUME=/dev/mapper/vg00-swap InstallationDate: Installed on 2016-09-13 (110 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Beta amd64 (20160803) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: HP ProLiant DL360 G
[Kernel-packages] [Bug 1653498] Re: Server reboots every 4.1 weeks
Hi, Does this issue exist on Ubuntu18.04? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1653498 Title: Server reboots every 4.1 weeks Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Confirmed Bug description: Every 4.1 uptime weeks (more or less), our 34 servers reboots with the logs below. Description:Ubuntu 16.04.1 LTS Release:16.04 The servers hosts the stack flanneld (0.5.5) docker (1.11.2, build b9f10c9) kubernetes (v1.3.6) plus etcd (2.3.7) Jan 02 06:40:32 prd-node021 kernel: [ cut here ] Jan 02 06:40:32 prd-node021 kernel: kernel BUG at /build/linux-xHzv4a/linux-4.4.0/include/linux/fs.h:2569! Jan 02 06:40:32 prd-node021 kernel: invalid opcode: [#1] SMP Jan 02 06:40:32 prd-node021 kernel: Modules linked in: nf_conntrack_netlink nfnetlink veth xt_statistic xt_nat xt_recent ipt_REJECT nf_reject_ipv4 xt_tcpudp tcp_diag inet_diag Jan 02 06:40:32 prd-node021 kernel: raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear crct10dif_pclmul crc Jan 02 06:40:32 prd-node021 kernel: CPU: 46 PID: 22749 Comm: iptables-restor Not tainted 4.4.0-47-generic #68-Ubuntu Jan 02 06:40:32 prd-node021 kernel: Hardware name: HP ProLiant DL360 Gen9/ProLiant DL360 Gen9, BIOS P89 09/13/2016 Jan 02 06:40:32 prd-node021 kernel: task: 882f7ccb44c0 ti: 882fcb81 task.ti: 882fcb81 Jan 02 06:40:32 prd-node021 kernel: RIP: 0010:[] [] __fput+0x21d/0x220 Jan 02 06:40:32 prd-node021 kernel: RSP: 0018:882fcb813e68 EFLAGS: 00010246 Jan 02 06:40:32 prd-node021 kernel: RAX: RBX: 8829dbd92700 RCX: 308c6396 Jan 02 06:40:32 prd-node021 kernel: RDX: 0001 RSI: 88301f299f60 RDI: Jan 02 06:40:32 prd-node021 kernel: RBP: 882fcb813ea0 R08: 00019f60 R09: 811b3a1d Jan 02 06:40:32 prd-node021 kernel: R10: ea0064756680 R11: 8829dbd92710 R12: 0010 Jan 02 06:40:32 prd-node021 kernel: R13: 8817d3520518 R14: 881021a34da0 R15: 8817d3542540 Jan 02 06:40:32 prd-node021 kernel: FS: 7fcdaa753700() GS:88301f28() knlGS: Jan 02 06:40:32 prd-node021 kernel: CS: 0010 DS: ES: CR0: 80050033 Jan 02 06:40:32 prd-node021 kernel: CR2: 7fcdaa758000 CR3: 001917993000 CR4: 003406e0 Jan 02 06:40:32 prd-node021 kernel: DR0: DR1: DR2: Jan 02 06:40:32 prd-node021 kernel: DR3: DR6: fffe0ff0 DR7: 0400 Jan 02 06:40:32 prd-node021 kernel: Stack: Jan 02 06:40:32 prd-node021 kernel: 8817d3520518 8829dbd92710 882f7ccb44c0 82103a30 Jan 02 06:40:32 prd-node021 kernel: 8829dbd92700 882f7ccb4b38 882fcb813eb0 Jan 02 06:40:32 prd-node021 kernel: 8120fa2e 882fcb813ef0 8109ee01 882f7ccb4b6c Jan 02 06:40:32 prd-node021 kernel: Call Trace: Jan 02 06:40:32 prd-node021 kernel: [] fput+0xe/0x10 Jan 02 06:40:32 prd-node021 kernel: [] task_work_run+0x81/0xa0 Jan 02 06:40:32 prd-node021 kernel: [] exit_to_usermode_loop+0xc2/0xd0 Jan 02 06:40:32 prd-node021 kernel: [] syscall_return_slowpath+0x4e/0x60 Jan 02 06:40:32 prd-node021 kernel: [] int_ret_from_sys_call+0x25/0x8f Jan 02 06:40:32 prd-node021 kernel: Code: 0f 84 cf fe ff ff 48 8b 43 28 48 8b 80 80 00 00 00 48 85 c0 0f 84 bb fe ff ff 31 d2 48 89 de bf ff ff ff ff ff d0 e9 aa fe ff ff <0f> Jan 02 06:40:32 prd-node021 kernel: RIP [] __fput+0x21d/0x220 -- Reboot -- Jan 02 06:42:56 prd-node021 systemd-journald[819]: Runtime journal (/run/log/journal/) is 8.0M, max 1.8G, 1.8G free. Jan 02 06:42:56 prd-node021 kernel: Initializing cgroup subsys cpuset ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-47-generic 4.4.0-47.68 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 2 06:42 seq crw-rw 1 root audio 116, 33 Jan 2 06:42 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Mon Jan 2 10:49:15 2017 HibernationDevice: RESUME=/dev/mapper/vg00-swap InstallationDate: Installed on 2016-09-13 (110 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Beta amd64 (20160803) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: HP ProLiant DL360 G
[Kernel-packages] [Bug 1885289] Re: zfs-linux 0.7.5-1ubuntu16.9 ADT test failure with 5.4 kernels in Bionic
** Changed in: zfs-linux (Ubuntu) Status: New => Invalid -- 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/1885289 Title: zfs-linux 0.7.5-1ubuntu16.9 ADT test failure with 5.4 kernels in Bionic Status in zfs-linux package in Ubuntu: Invalid Status in zfs-linux source package in Bionic: Confirmed Bug description: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/amd64/z/zfs-linux/20200625_160936_8fbbb@/log.gz arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/arm64/z/zfs-linux/20200625_161319_b9d4a@/log.gz ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/ppc64el/z/zfs-linux/20200625_134053_b1336@/log.gz s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/s390x/z/zfs-linux/20200625_133912_0757e@/log.gz The dkms tests are failing for two reasons: 1. spl-linux can't be installed (see bug 1885285). 2. test kernel-smoke-test fails with the following error: autopkgtest [16:08:43]: test kernel-smoke-test: [--- kernel smoke test, create and destroy pool, 2x2 mirror: PASSED kernel smoke test, create and destroy pool, 4x1 mirror: PASSED kernel smoke test, create and destroy pool, nested raidz3: PASSED kernel smoke test, create and destroy pool, raidz1: PASSED kernel smoke test, create and destroy pool, raidz2: PASSED kernel smoke test, create and destroy pool, raidz3: PASSED kernel smoke test, create and destroy pool, striped: PASSED kernel smoke test, create and destroy ZFS Intent Log: PASSED kernel smoke test, create and destroy ZFS filesystems: PASSED kernel smoke test, ZFS snapshot: PASSED kernel smoke test, ZFS clone: PASSED kernel smoke test, ZFS send and receive: PASSED kernel smoke test, corrupt data and clean with a scrub: cannot scrub pool-smoke-6551: currently resilvering FAILED: zpool scrub failed, exit code=1 autopkgtest [16:09:24]: test kernel-smoke-test: ---] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1885289/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1885289] Re: zfs-linux 0.7.5-1ubuntu16.9 ADT test failure with 5.4 kernels in Bionic
** Changed in: zfs-linux (Ubuntu) Assignee: (unassigned) => Colin Ian King (colin-king) -- 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/1885289 Title: zfs-linux 0.7.5-1ubuntu16.9 ADT test failure with 5.4 kernels in Bionic Status in zfs-linux package in Ubuntu: Invalid Status in zfs-linux source package in Bionic: Confirmed Bug description: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/amd64/z/zfs-linux/20200625_160936_8fbbb@/log.gz arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/arm64/z/zfs-linux/20200625_161319_b9d4a@/log.gz ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/ppc64el/z/zfs-linux/20200625_134053_b1336@/log.gz s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/s390x/z/zfs-linux/20200625_133912_0757e@/log.gz The dkms tests are failing for two reasons: 1. spl-linux can't be installed (see bug 1885285). 2. test kernel-smoke-test fails with the following error: autopkgtest [16:08:43]: test kernel-smoke-test: [--- kernel smoke test, create and destroy pool, 2x2 mirror: PASSED kernel smoke test, create and destroy pool, 4x1 mirror: PASSED kernel smoke test, create and destroy pool, nested raidz3: PASSED kernel smoke test, create and destroy pool, raidz1: PASSED kernel smoke test, create and destroy pool, raidz2: PASSED kernel smoke test, create and destroy pool, raidz3: PASSED kernel smoke test, create and destroy pool, striped: PASSED kernel smoke test, create and destroy ZFS Intent Log: PASSED kernel smoke test, create and destroy ZFS filesystems: PASSED kernel smoke test, ZFS snapshot: PASSED kernel smoke test, ZFS clone: PASSED kernel smoke test, ZFS send and receive: PASSED kernel smoke test, corrupt data and clean with a scrub: cannot scrub pool-smoke-6551: currently resilvering FAILED: zpool scrub failed, exit code=1 autopkgtest [16:09:24]: test kernel-smoke-test: ---] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1885289/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1885491] Re: firefor crashes ubuntu command terminal crashes
I was facing BSOD in windows OS so i shift to Linux OS but here also I am facing some issues like firefox crash. On Mon, 29 Jun 2020 at 20:20, Guilherme G. Piccoli < 1885...@bugs.launchpad.net> wrote: > Hi Sangam, I think this is bug is reported against the wrong component. > Crash is a tool used to analyze crash dumps from kernel (kdump stuff), > and it seems you are seeing crashed on..firefox? If not, what is > firefor? > > If possible, give a more detailed explanation on what you are > experiencing, and we will find the right component for your report. > Cheers, > > > Guilherme > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1885491 > > Title: > firefor crashes ubuntu command terminal crashes > > Status in crash package in Ubuntu: > New > > Bug description: > this is the ubuntu 20.04 > i am using ubuntu as i faced blue screen in windows.After installing > ubuntu i am not facing blue screen but some kind of crashes happen here too > ...whatever the task i am performing it crashes automatically but now it is > ok but can't say when it will crash again. > > ProblemType: Bug > DistroRelease: Ubuntu 20.04 > Package: crash (not installed) > ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41 > Uname: Linux 5.4.0-39-generic x86_64 > ApportVersion: 2.20.11-0ubuntu27.3 > Architecture: amd64 > CasperMD5CheckResult: skip > CurrentDesktop: ubuntu:GNOME > Date: Mon Jun 29 10:03:56 2020 > InstallationDate: Installed on 2020-06-28 (0 days ago) > InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 > (20200423) > SourcePackage: crash > UpgradeStatus: No upgrade log present (probably fresh install) > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1885491/+subscriptions > -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to crash in Ubuntu. https://bugs.launchpad.net/bugs/1885491 Title: firefor crashes ubuntu command terminal crashes Status in crash package in Ubuntu: New Bug description: this is the ubuntu 20.04 i am using ubuntu as i faced blue screen in windows.After installing ubuntu i am not facing blue screen but some kind of crashes happen here too ...whatever the task i am performing it crashes automatically but now it is ok but can't say when it will crash again. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: crash (not installed) ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41 Uname: Linux 5.4.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Jun 29 10:03:56 2020 InstallationDate: Installed on 2020-06-28 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: crash UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1885491/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1861941] Re: bcache by-uuid links disappear after mounting bcache0
** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: bcache-tools (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux-signed (Ubuntu Bionic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1861941 Title: bcache by-uuid links disappear after mounting bcache0 Status in bcache-tools package in Ubuntu: Triaged Status in linux package in Ubuntu: Incomplete Status in linux-signed package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Fix Released Status in bcache-tools source package in Bionic: New Status in linux source package in Bionic: New Status in linux-signed source package in Bionic: New Status in systemd source package in Bionic: New Status in bcache-tools source package in Focal: Confirmed Status in linux source package in Focal: Invalid Status in linux-signed source package in Focal: Confirmed Status in systemd source package in Focal: Confirmed Status in bcache-tools source package in Groovy: Triaged Status in linux source package in Groovy: Incomplete Status in linux-signed source package in Groovy: Confirmed Status in systemd source package in Groovy: Fix Released Bug description: 1. root@ubuntu:~# lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 2. root@ubuntu:~# lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 root@ubuntu:~# apt-cache policy linux-image-virtual linux-image-virtual: Installed: 5.4.0.12.15 Candidate: 5.4.0.12.15 Version table: *** 5.4.0.12.15 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status root@ubuntu:~# apt-cache policy linux-image-5.4.0-12-generic linux-image-5.4.0-12-generic: Installed: 5.4.0-12.15 Candidate: 5.4.0-12.15 Version table: *** 5.4.0-12.15 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status 3. mount /dev/bcache0 && ls -al /dev/bcache/by-uuid/ + ls -al /dev/bcache/by-uuid/ total 0 drwxr-xr-x 2 root root 60 Feb 4 23:31 . drwxr-xr-x 3 root root 60 Feb 4 23:31 .. lrwxrwxrwx 1 root root 13 Feb 4 23:31 abdfd1f6-44ce-4266-91db-24667b9ae51a -> ../../bcache0 4. root@ubuntu:~# ls -al /dev/bcache/by-uuid ls: cannot access '/dev/bcache/by-uuid': No such file or directory ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-12-generic 5.4.0-12.15 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 Date: Tue Feb 4 23:31:52 2020 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-5.4 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcache-tools/+bug/1861941/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1861941] Re: bcache by-uuid links disappear after mounting bcache0
@raharper I've forwarded the systemd fix for you with minimal tidying of the commit message https://github.com/systemd/systemd/pull/16317 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1861941 Title: bcache by-uuid links disappear after mounting bcache0 Status in bcache-tools package in Ubuntu: Triaged Status in linux package in Ubuntu: Incomplete Status in linux-signed package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Fix Released Status in bcache-tools source package in Bionic: New Status in linux source package in Bionic: New Status in linux-signed source package in Bionic: New Status in systemd source package in Bionic: New Status in bcache-tools source package in Focal: Confirmed Status in linux source package in Focal: Invalid Status in linux-signed source package in Focal: Confirmed Status in systemd source package in Focal: Confirmed Status in bcache-tools source package in Groovy: Triaged Status in linux source package in Groovy: Incomplete Status in linux-signed source package in Groovy: Confirmed Status in systemd source package in Groovy: Fix Released Bug description: 1. root@ubuntu:~# lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 2. root@ubuntu:~# lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 root@ubuntu:~# apt-cache policy linux-image-virtual linux-image-virtual: Installed: 5.4.0.12.15 Candidate: 5.4.0.12.15 Version table: *** 5.4.0.12.15 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status root@ubuntu:~# apt-cache policy linux-image-5.4.0-12-generic linux-image-5.4.0-12-generic: Installed: 5.4.0-12.15 Candidate: 5.4.0-12.15 Version table: *** 5.4.0-12.15 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status 3. mount /dev/bcache0 && ls -al /dev/bcache/by-uuid/ + ls -al /dev/bcache/by-uuid/ total 0 drwxr-xr-x 2 root root 60 Feb 4 23:31 . drwxr-xr-x 3 root root 60 Feb 4 23:31 .. lrwxrwxrwx 1 root root 13 Feb 4 23:31 abdfd1f6-44ce-4266-91db-24667b9ae51a -> ../../bcache0 4. root@ubuntu:~# ls -al /dev/bcache/by-uuid ls: cannot access '/dev/bcache/by-uuid': No such file or directory ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-12-generic 5.4.0-12.15 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 Date: Tue Feb 4 23:31:52 2020 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-5.4 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcache-tools/+bug/1861941/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1653498] Re: Server reboots every 4.1 weeks
Hello, We have the same issue on our k8s cluster. Description: ubuntu16.04.1 LTSx86_64 Release: 16.04.1 Kernel: 4.4.0-104-generic [19156101.592212] [ cut here ] [19156101.593103] kernel BUG at /build/linux-SwhOyu/linux-4.4.0/include/linux/fs.h:2582! [19156101.594385] invalid opcode: [#1] SMP [19156101.595083] Modules linked in: binfmt_misc af_packet_diag netlink_diag dccp_diag dccp tcp_diag udp_diag inet_diag unix_diag veth br_netfilter ipt_MASQUERADE nf_nat_masquerade_ipv4 xt_set xt_mark ip_set_hash_ipportnet ip_set_hash_ipportip ip_set_bitmap_port ip_set_hash_ipport ip_set dummy xt_comment xt_addrtype iptable_nat nf_nat_ipv4 nf_conntrack_ipv4 nf_defrag_ipv4 ip_vs_sh ip_vs_wrr ip_vs_rr ip_vs xt_tcpudp bridge stp llc nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo iptable_filter ip_tables xt_conntrack x_tables nf_nat nf_conntrack aufs isofs ppdev crct10dif_pclmul parport_pc crc32_pclmul input_leds joydev ghash_clmulni_intel parport serio_raw ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr sunrpc iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi autofs4 btrfs raid10 raid456 async_raid6_recov [19156101.606434] async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear aesni_intel aes_x86_64 glue_helper lrw gf128mul ablk_helper cryptd psmouse floppy [19156101.609129] CPU: 29 PID: 11388 Comm: heartbeat Not tainted 4.4.0-104-generic #127-Ubuntu [19156101.610384] Hardware name: Smdbmds KVM, BIOS seabios-1.9.1-qemu-project.org 04/01/2014 [19156101.611637] task: 880eb1f79e00 ti: 8809131a4000 task.ti: 8809131a4000 [19156101.612905] RIP: 0010:[] [] __fput+0x21d/0x220 [19156101.614188] RSP: 0018:8809131a7e68 EFLAGS: 00010246 [19156101.614989] RAX: RBX: 880ef6915700 RCX: 000365fb1705 [19156101.616143] RDX: 0001 RSI: 880fff55a020 RDI: [19156101.617285] RBP: 8809131a7ea0 R08: 0001a020 R09: 811b591d [19156101.618422] R10: ea002b69b300 R11: 880ef6915710 R12: 0010 [19156101.619574] R13: 880ed152aef8 R14: 8800bba18aa0 R15: 880ed1513a40 [19156101.620785] FS: 00c42085bc90() GS:880fff54() knlGS: [19156101.622074] CS: 0010 DS: ES: CR0: 80050033 [19156101.622921] CR2: 7f508b166b04 CR3: 000e0981b000 CR4: 003406e0 [19156101.624062] DR0: DR1: DR2: [19156101.625210] DR3: DR6: fffe0ff0 DR7: 0400 [19156101.626349] Stack: [19156101.626765] 880ed152aef8 880ef6915710 880eb1f79e00 8210ad50 [19156101.628018] 880ef6915700 880eb1f7a4a0 8809131a7eb0 [19156101.629305] 812126ee 8809131a7ef0 8109f101 880eb1f7a4d4 [19156101.630568] Call Trace: [19156101.631036] [] fput+0xe/0x10 [19156101.631804] [] task_work_run+0x81/0xa0 [19156101.632612] [] exit_to_usermode_loop+0xc2/0xd0 [19156101.633497] [] syscall_return_slowpath+0x4e/0x60 [19156101.634402] [] int_ret_from_sys_call+0x25/0x8f [19156101.635285] Code: 0f 84 cf fe ff ff 48 8b 43 28 48 8b 80 80 00 00 00 48 85 c0 0f 84 bb fe ff ff 31 d2 48 89 de bf ff ff ff ff ff d0 e9 aa fe ff ff <0f> 0b 90 0f 1f 44 00 00 31 ff 48 87 3d 8a 6e fc 00 48 85 ff 74 [19156101.639244] RIP [] __fput+0x21d/0x220 [19156101.640049] RSP crash> Does this issue exist on Ubuntu18.04 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1653498 Title: Server reboots every 4.1 weeks Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Confirmed Bug description: Every 4.1 uptime weeks (more or less), our 34 servers reboots with the logs below. Description:Ubuntu 16.04.1 LTS Release:16.04 The servers hosts the stack flanneld (0.5.5) docker (1.11.2, build b9f10c9) kubernetes (v1.3.6) plus etcd (2.3.7) Jan 02 06:40:32 prd-node021 kernel: [ cut here ] Jan 02 06:40:32 prd-node021 kernel: kernel BUG at /build/linux-xHzv4a/linux-4.4.0/include/linux/fs.h:2569! Jan 02 06:40:32 prd-node021 kernel: invalid opcode: [#1] SMP Jan 02 06:40:32 prd-node021 kernel: Modules linked in: nf_conntrack_netlink nfnetlink veth xt_statistic xt_nat xt_recent ipt_REJECT nf_reject_ipv4 xt_tcpudp tcp_diag inet_diag Jan 02 06:40:32 prd-node021 kernel: raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear crct10dif_pclmul crc Jan 02 06:40:32 prd-node021 kernel: CPU: 46 PID: 22749 Comm: iptables-restor Not tainted 4.4.0-47-generic #68-Ubuntu Jan 02 06:40:32 prd-node021 kernel: Hardware name: HP ProLiant DL360 Gen9/ProLiant DL360 Gen9, BIOS P89 09/13/2016 Jan 02 06:40:32 prd-node021 kernel: task
[Kernel-packages] [Bug 1885711] [NEW] Wifi + Bluetooth coexistence
Public bug reported: Hi, Internet is full of this for several years and for several years for whatever reason it's not fixed in Ubuntu without any explanation. It's a problem with wifi drivers? Or it's a problem with linux bluetooth stack. Or with kernel or it's only specific to Ubuntu configuration/packaging? No answers and solution anywhere. Meanwhile i have a new desktop computer with different hardware (previously Broadcomm, now Realtek) and guess what? It's still not working in Ubuntu 20.04.. Wifi itself is working properly. Also bluetooth itself semms to work properly. But try to use both and wifi speed will drop down significantly, almost stops to something like 20-50 kb/s. Turnning off Bluetooth and it recovers to full speed. In my desktop board ASUS ROG-Strix B-450-I Gaming i have build in Wifi and Bluetooth module from Realtek. It is using kernel module rtw88 - so much i have finded out. But how to enable and get working coexistence like in Windows, good luck with that.. almost zero information on the internet, very end-user unfriedly. It's about time you start solving similar issues and closing bugreports or nobody will take your most popular distro seriously.. ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1885711 Title: Wifi + Bluetooth coexistence Status in linux package in Ubuntu: Incomplete Bug description: Hi, Internet is full of this for several years and for several years for whatever reason it's not fixed in Ubuntu without any explanation. It's a problem with wifi drivers? Or it's a problem with linux bluetooth stack. Or with kernel or it's only specific to Ubuntu configuration/packaging? No answers and solution anywhere. Meanwhile i have a new desktop computer with different hardware (previously Broadcomm, now Realtek) and guess what? It's still not working in Ubuntu 20.04.. Wifi itself is working properly. Also bluetooth itself semms to work properly. But try to use both and wifi speed will drop down significantly, almost stops to something like 20-50 kb/s. Turnning off Bluetooth and it recovers to full speed. In my desktop board ASUS ROG-Strix B-450-I Gaming i have build in Wifi and Bluetooth module from Realtek. It is using kernel module rtw88 - so much i have finded out. But how to enable and get working coexistence like in Windows, good luck with that.. almost zero information on the internet, very end-user unfriedly. It's about time you start solving similar issues and closing bugreports or nobody will take your most popular distro seriously.. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1885711/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1885711] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1885711 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1885711 Title: Wifi + Bluetooth coexistence Status in linux package in Ubuntu: Incomplete Bug description: Hi, Internet is full of this for several years and for several years for whatever reason it's not fixed in Ubuntu without any explanation. It's a problem with wifi drivers? Or it's a problem with linux bluetooth stack. Or with kernel or it's only specific to Ubuntu configuration/packaging? No answers and solution anywhere. Meanwhile i have a new desktop computer with different hardware (previously Broadcomm, now Realtek) and guess what? It's still not working in Ubuntu 20.04.. Wifi itself is working properly. Also bluetooth itself semms to work properly. But try to use both and wifi speed will drop down significantly, almost stops to something like 20-50 kb/s. Turnning off Bluetooth and it recovers to full speed. In my desktop board ASUS ROG-Strix B-450-I Gaming i have build in Wifi and Bluetooth module from Realtek. It is using kernel module rtw88 - so much i have finded out. But how to enable and get working coexistence like in Windows, good luck with that.. almost zero information on the internet, very end-user unfriedly. It's about time you start solving similar issues and closing bugreports or nobody will take your most popular distro seriously.. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1885711/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1884288] Re: LapBook Pro touchpad (HTIX5288:00) sometimes does not work when machine is restarted
I tell you several things: 1. Have you tried putting this line in the GRUB file?: GRUB_CMDLINE_LINUX = 'i8042.nopnp pci = noaer' 2. Next, you must update the GRUB. 3. I have verified that almost every time I update the GRUB the TOUCHPAD works, but previously I must modify the GRUB file first. It seems as if rewriting in the GRUB activates the TOUCHPAD. I don't know if it will have something to do with the boot sector. 4. As I suppose that the resolution of this problem will take a long time, I advise you to use Windows if you find it essential to use TOUCHPAD. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1884288 Title: LapBook Pro touchpad (HTIX5288:00) sometimes does not work when machine is restarted Status in linux package in Ubuntu: Confirmed Bug description: Touchpad completely ceases to work sometimes upon startup / restart. When this happens, I have to plug in an external mouse to navigate as touchpad is not even recognised as a device when I use xinput command in terminal. I removed and reinstalled xserver-xorg-input-synaptics which may have got it working again, although I am not too sure. When the trackpad is working, it's device name is listed as HTIX5288:00 0911:5288 Touchpad. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jun 19 18:03:47 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics 605 [8086:3185] (rev 03) (prog-if 00 [VGA controller]) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0c45:6366 Microdia USB 2.0 Camera Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=c549aad1-cbca-42d0-abc5-e73556f0921b ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/29/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E.G140J.D8.E1.016.bin dmi.board.asset.tag: Default string dmi.board.name: Default string dmi.board.vendor: Default string dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE.G140J.D8.E1.016.bin:bd11/29/2019:svn:pnLapBookPro:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: LapBook Pro dmi.product.sku: Default string dmi.product.version: Default string version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ian1619 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0c45:6366 Microdia USB 2.0 Camera Bus 001 Device 008: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=c549aad1-cbca-42d0-abc5-e73556f0921b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.4.0-37-generic N/A linux-backports-modules-5.4.0-37-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-37-generic x86_64 UpgradeStatus: No upg
[Kernel-packages] [Bug 1850439] Re: No sound on ASUS UX534FT
Hello, Please refer to the report below. Report: - Device: Asus Zenbook Flip UX563FD-A1041T - Popos 20.04 (Linux pop-os 5.4.0-7634-generic #38~1592497129~20.04~9a1ea2e-Ubuntu) Results: 1) Before the commands: - Speakers - don't work - Internal mic - works 2) After the commands: - Speakers - work - Internal mic - works - Headphones: only left works - Headset - doesn't work (it isn't shown in settings, so it can't be selected) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1850439 Title: No sound on ASUS UX534FT Status in linux package in Ubuntu: Confirmed Bug description: Hi, after instal Ubuntu in dual boot alongside Windows 10, I've realised there is no sound coming out of mine new ASUS Zenbook 15 UX534FT- AA024R in Ubuntu. In Windows there is no problem. Found this topic https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810214 which had the same problem with driver for Realtek ALC294 which is also mine sound card. But even with this fix it is not working on UX534FT. Can you please add fix also for this newer model? Description: Ubuntu 18.04.3 LTS Release: 18.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.0.0-32-generic 5.0.0-32.34~18.04.2 ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 29 15:11:25 2019 InstallationDate: Installed on 2019-10-29 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) SourcePackage: linux-signed-hwe UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850439/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1863911] Re: Wireless-AC 3168NGW no longer initializes
With Linux 5.4.0-39-generic, it works fine. Please close this bug. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-5.4 in Ubuntu. https://bugs.launchpad.net/bugs/1863911 Title: Wireless-AC 3168NGW no longer initializes Status in linux-signed-5.4 package in Ubuntu: New Bug description: Booting into that kernel results in failure to load the wifi card firmware. it is known issue see: https://bugzilla.kernel.org/show_bug.cgi?id=206329 https://lkml.org/lkml/2020/2/8/5 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-14-generic 5.4.0-14.17 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 CurrentDesktop: KDE Date: Wed Feb 19 19:05:55 2020 InstallationDate: Installed on 2020-02-10 (9 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-5.4 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-5.4/+bug/1863911/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1882088] Re: [UBUNTU 20.04] smc: SMC connections hang with later-level implementations
Changing to Incomplete for now until discussions concluded ... ** Changed in: ubuntu-z-systems Status: New => Incomplete ** Also affects: linux (Ubuntu Groovy) Importance: Undecided Assignee: Skipper Bug Screeners (skipper-screen-team) Status: New ** Changed in: ubuntu-z-systems Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team) ** Changed in: linux (Ubuntu Groovy) Assignee: Skipper Bug Screeners (skipper-screen-team) => (unassigned) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1882088 Title: [UBUNTU 20.04] smc: SMC connections hang with later-level implementations Status in Ubuntu on IBM z Systems: Incomplete Status in linux package in Ubuntu: New Status in linux source package in Focal: New Status in linux source package in Groovy: New Bug description: Description: smc: SMC connections hang with later-level implementations Symptom: Connections from later-level SMC versions to an SMC-enabled server on Linux hang. Problem: Later-level versions of SMC present, although backwards- compatible, a higher version number, and use larger messages during the CLC handshake. Solution: Adjust for tolerating later version numbers, and support CLC messages of arbitrary length. Reproduction: Enable a server on Linux for SMC, and connect using a later- level version of SMC Applicable for: Ubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1882088/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1885693] [NEW] Unwanted reboot after screen is locked
You have been subscribed to a public bug: After locking the screen to leave the computer for a few minutes, I come back to a computer that is freshly rebooted. It usually happens 1 out of 4 or 5 times when locking the screen. This only happens when my laptop (Lenovo T470s, also seen with T490) is connected to my USB-C dock. The problem has been observed with 18.04, 19.10 and 20.04. /var/log/syslog contains: Jun 30 10:47:05 jbn3 kernel: [33470.649606] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. Jun 30 10:47:23 jbn3 kernel: [33488.187142] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. Jun 30 10:47:23 jbn3 kernel: [33488.419723] [drm:pipe_config_mismatch [i915]] *ERROR* mismatch in pixel_rate (expected 241500, found 482999) Jun 30 10:47:23 jbn3 kernel: [33488.419818] [drm:pipe_config_mismatch [i915]] *ERROR* mismatch in shared_dpll (expected a870403d, found 5108ff4b) Jun 30 10:47:23 jbn3 kernel: [33488.419902] [drm:pipe_config_mismatch [i915]] *ERROR* mismatch in dpll_hw_state.ctrl1 (expected 0x0003, found 0x0001) Jun 30 10:47:23 jbn3 kernel: [33488.419986] [drm:pipe_config_mismatch [i915]] *ERROR* mismatch in base.adjusted_mode.crtc_clock (expected 241500, found 482999) Jun 30 10:47:23 jbn3 kernel: [33488.420067] [drm:pipe_config_mismatch [i915]] *ERROR* mismatch in port_clock (expected 27, found 54) Jun 30 10:47:23 jbn3 kernel: [33488.420071] [ cut here ] Jun 30 10:47:23 jbn3 kernel: [33488.420072] pipe state doesn't match! Jun 30 10:47:23 jbn3 kernel: [33488.420249] WARNING: CPU: 0 PID: 2300 at drivers/gpu/drm/i915/display/intel_display.c:13158 verify_crtc_state+0x2ad/0x300 [i915] Jun 30 10:47:23 jbn3 kernel: [33488.420251] Modules linked in: xt_nat xt_tcpudp veth xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo xt_addrtype iptable_filter iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 bpfilter br_netfilter bridge stp llc hid_generic snd_usb_audio usbhid snd_usbmidi_lib hid cdc_ether r8152 vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) ccm aufs overlay bnep nls_iso8859_1 joydev intel_rapl_msr mei_hdcp cdc_mbim qcserial usb_wwan cdc_wdm usbserial cdc_ncm usbnet mii uvcvideo btusb btrtl snd_hda_codec_hdmi btbcm btintel intel_rapl_common x86_pkg_temp_thermal intel_powerclamp coretemp bluetooth kvm_intel snd_hda_codec_realtek snd_hda_codec_generic kvm snd_hda_intel snd_intel_dspcfg snd_hda_codec intel_cstate rmi_smbus ecdh_generic rmi_core intel_rapl_perf ecc videobuf2_vmalloc snd_hda_core videobuf2_memops videobuf2_v4l2 snd_hwdep iwlmvm snd_seq_midi videobuf2_common snd_seq_midi_event mac80211 videodev intel_wmi_thunderbolt libarc4 snd_pcm input_leds iwlwifi Jun 30 10:47:23 jbn3 kernel: [33488.420310] snd_rawmidi mc serio_raw snd_seq wmi_bmof thinkpad_acpi nvram cfg80211 ledtrig_audio mei_me intel_xhci_usb_role_switch mei snd_seq_device intel_pch_thermal snd_timer ucsi_acpi typec_ucsi roles typec snd soundcore acpi_pad mac_hid sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables autofs4 btrfs xor zstd_compress raid6_pq libcrc32c dm_crypt uas usb_storage i915 crct10dif_pclmul crc32_pclmul nvme ghash_clmulni_intel i2c_algo_bit aesni_intel crypto_simd cryptd glue_helper psmouse e1000e i2c_i801 nvme_core drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops thunderbolt drm wmi video Jun 30 10:47:23 jbn3 kernel: [33488.420358] CPU: 0 PID: 2300 Comm: Xorg Tainted: G OE 5.4.0-39-generic #43-Ubuntu Jun 30 10:47:23 jbn3 kernel: [33488.420360] Hardware name: LENOVO 20HF004MMX/20HF004MMX, BIOS N1WET59W (1.38 ) 04/22/2020 Jun 30 10:47:23 jbn3 kernel: [33488.420437] RIP: 0010:verify_crtc_state+0x2ad/0x300 [i915] Jun 30 10:47:23 jbn3 kernel: [33488.420441] Code: b6 45 bf e9 8d fe ff ff 80 3d 45 77 10 00 00 0f b6 f0 48 c7 c7 40 aa 85 c0 75 32 e8 1d 48 d5 ff e9 1e fe ff ff e8 6e 9e b1 ef <0f> 0b e9 1b ff ff ff e8 62 9e b1 ef 0f 0b e9 85 fe ff ff e8 56 9e Jun 30 10:47:23 jbn3 kernel: [33488.420444] RSP: 0018:b1b74290fa80 EFLAGS: 00010282 Jun 30 10:47:23 jbn3 kernel: [33488.420448] RAX: RBX: 97a35f0002b0 RCX: 0006 Jun 30 10:47:23 jbn3 kernel: [33488.420450] RDX: 0007 RSI: 0092 RDI: 97a3724178c0 Jun 30 10:47:23 jbn3 kernel: [33488.420452] RBP: b1b74290fac8 R08: 0ae9 R09: 0004 Jun 30 10:47:23 jbn3 kernel: [33488.420454] R10: R11: 0001 R12: 97a35f207000 Jun 30 10:47:23 jbn3 kernel: [33488.420456] R13: 97a35f0002b8 R14: 97a35f00 R15: 97a139c69000 Jun 30 10:47:23 jbn3 kernel: [33488.420460] FS: 7f4db55a5a80() GS:97a37240() knlGS: Jun 30 10:47:23 jb
[Kernel-packages] [Bug 1885696] [NEW] Kernel panic linux-image-5.4.0-39-generic with cachefiles
You have been subscribed to a public bug: Ubuntu 20.04 server with latest kernel 5.4.0-39-generic panics under load when cachefilesd is used. This bug is known and fixed in upstream kernel 5.4.44 https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.4.44 cachefiles: Fix race between read_waiter and read_copier involving op->to_do [ Upstream commit 7bb0c5338436dae953622470d52689265867f032 ] https://github.com/torvalds/linux/commit/7bb0c5338436dae953622470d52689265867f032 #diff-14a48d14f7cd98c97d57211cfd758797 package: linux-image-5.4.0-39-generic, linux-image-generic Dmesg output: [450023.072377] FS-Cache: [450023.075150] FS-Cache: Assertion failed [450023.079496] FS-Cache: 4 == 5 is false [450023.083749] kernel BUG at fs/fscache/operation.c:69! [450023.089468] invalid opcode: [#1] SMP PTI [450023.094500] CPU: 13 PID: 0 Comm: swapper/13 Not tainted 5.4.0-37-generic #41-Ubuntu [450023.104057] Hardware name: Dell Inc. PowerEdge R430/0CN7X8, BIOS 2.11.0 12/23/2019 [450023.112660] RIP: 0010:fscache_enqueue_operation.cold+0xb7/0xb9 [fscache] [450023.120279] Code: a8 96 c0 e8 3f dc 1a e1 48 c7 c7 14 a8 96 c0 e8 33 dc 1a e1 41 8b 74 24 40 ba 05 00 00 00 48 c7 c7 28 98 96 c0 e8 1d dc 1a e1 <0f> 0b 48 c7 c7 06 a8 96 c0 e8 0f dc 1a e1 48 c7 c7 14 a8 96 c0 e8 [450023.141515] RSP: 0018:baca8cb88b98 EFLAGS: 00010046 [450023.147490] RAX: 0019 RBX: 98535b7f6540 RCX: 0006 [450023.156712] RDX: RSI: 0092 RDI: 9872bf3978c0 [450023.165774] RBP: baca8cb88bb0 R08: 337d R09: baca8f984020 [450023.175116] R10: 9852b7ebc2a0 R11: 0001 R12: 9872b870f740 [450023.184384] R13: 9838bd287580 R14: R15: baca8cb88c48 [450023.193659] FS: () GS:9872bf38() knlGS: [450023.204016] CS: 0010 DS: ES: CR0: 80050033 [450023.211346] CR2: 55eb5afaf2d8 CR3: 00359180a004 CR4: 003626e0 [450023.220602] DR0: DR1: DR2: [450023.229668] DR3: DR6: fffe0ff0 DR7: 0400 [450023.238621] Call Trace: [450023.242266] [450023.245426] cachefiles_read_waiter+0xe5/0x100 [cachefiles] [450023.252592] __wake_up_common+0x7e/0x140 [450023.257909] __wake_up_locked_key_bookmark+0x1b/0x20 [450023.264404] wake_up_page_bit+0xa7/0x100 [450023.269733] unlock_page+0x25/0x30 [450023.274491] __read_end_io+0xb6/0x110 [450023.279530] mpage_end_io+0x2f/0x40 [450023.284389] bio_endio+0xfb/0x160 [450023.289052] dec_pending+0x11c/0x210 [450023.294006] clone_endio+0x77/0x170 [450023.298874] bio_endio+0xfb/0x160 [450023.303540] blk_update_request+0x18a/0x2e0 [450023.309201] scsi_end_request+0x30/0x160 [450023.314571] scsi_io_completion+0x7c/0x540 [450023.320129] ? __update_load_avg_cfs_rq+0x212/0x2f0 [450023.326580] scsi_finish_command+0xe7/0x120 [450023.332259] scsi_softirq_done+0x14a/0x170 [450023.337840] blk_done_softirq+0x92/0xc0 [450023.343141] __do_softirq+0xe1/0x2d6 [450023.348145] irq_exit+0xae/0xb0 [450023.352670] smp_call_function_single_interrupt+0x48/0xd0 [450023.359735] call_function_single_interrupt+0xf/0x20 [450023.366323] [450023.369712] RIP: 0010:cpuidle_enter_state+0xc5/0x450 [450023.376326] Code: ff e8 5f 0c 81 ff 80 7d c7 00 74 17 9c 58 0f 1f 44 00 00 f6 c4 02 0f 85 65 03 00 00 31 ff e8 72 6e 87 ff fb 66 0f 1f 44 00 00 <45> 85 ed 0f 88 8f 02 00 00 49 63 cd 4c 8b 7d d0 4c 2b 7d c8 48 8d [450023.399419] RSP: 0018:baca8017be38 EFLAGS: 0246 ORIG_RAX: ff04 [450023.409020] RAX: 9872bf3aad00 RBX: a3159c00 RCX: 001f [450023.418148] RDX: RSI: 3a3fe5c1 RDI: [450023.427270] RBP: baca8017be78 R08: 0001994b295dad0d R09: 0001 [450023.436383] R10: 9872bf3a9a00 R11: 9872bf3a99e0 R12: daca7f583400 [450023.445496] R13: 0003 R14: 0003 R15: daca7f583400 [450023.454584] ? cpuidle_enter_state+0xa1/0x450 [450023.460544] cpuidle_enter+0x2e/0x40 [450023.465593] call_cpuidle+0x23/0x40 [450023.470525] do_idle+0x1dd/0x270 [450023.475147] cpu_startup_entry+0x20/0x30 [450023.480547] start_secondary+0x167/0x1c0 [450023.485934] secondary_startup_64+0xa4/0xb0 [450023.491620] Modules linked in: vhost_net vhost tap cpuid xt_state br_netfilter xt_physdev ip_set xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat iptable_mangle iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nf_tables nfnetlink ip6table_filter ip6_tables iptable_filter bpfilter bridge cachefiles rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace fscache 8021q garp mrp stp llc bonding nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua ipmi_ssif intel_rapl_msr intel_rapl_common sb_edac x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel dcdbas kvm i
[Kernel-packages] [Bug 1885696] Re: Kernel panic linux-image-5.4.0-39-generic with cachefiles
** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1885696 Title: Kernel panic linux-image-5.4.0-39-generic with cachefiles Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu 20.04 server with latest kernel 5.4.0-39-generic panics under load when cachefilesd is used. This bug is known and fixed in upstream kernel 5.4.44 https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.4.44 cachefiles: Fix race between read_waiter and read_copier involving op->to_do [ Upstream commit 7bb0c5338436dae953622470d52689265867f032 ] https://github.com/torvalds/linux/commit/7bb0c5338436dae953622470d52689265867f032 #diff-14a48d14f7cd98c97d57211cfd758797 package: linux-image-5.4.0-39-generic, linux-image-generic Dmesg output: [450023.072377] FS-Cache: [450023.075150] FS-Cache: Assertion failed [450023.079496] FS-Cache: 4 == 5 is false [450023.083749] kernel BUG at fs/fscache/operation.c:69! [450023.089468] invalid opcode: [#1] SMP PTI [450023.094500] CPU: 13 PID: 0 Comm: swapper/13 Not tainted 5.4.0-37-generic #41-Ubuntu [450023.104057] Hardware name: Dell Inc. PowerEdge R430/0CN7X8, BIOS 2.11.0 12/23/2019 [450023.112660] RIP: 0010:fscache_enqueue_operation.cold+0xb7/0xb9 [fscache] [450023.120279] Code: a8 96 c0 e8 3f dc 1a e1 48 c7 c7 14 a8 96 c0 e8 33 dc 1a e1 41 8b 74 24 40 ba 05 00 00 00 48 c7 c7 28 98 96 c0 e8 1d dc 1a e1 <0f> 0b 48 c7 c7 06 a8 96 c0 e8 0f dc 1a e1 48 c7 c7 14 a8 96 c0 e8 [450023.141515] RSP: 0018:baca8cb88b98 EFLAGS: 00010046 [450023.147490] RAX: 0019 RBX: 98535b7f6540 RCX: 0006 [450023.156712] RDX: RSI: 0092 RDI: 9872bf3978c0 [450023.165774] RBP: baca8cb88bb0 R08: 337d R09: baca8f984020 [450023.175116] R10: 9852b7ebc2a0 R11: 0001 R12: 9872b870f740 [450023.184384] R13: 9838bd287580 R14: R15: baca8cb88c48 [450023.193659] FS: () GS:9872bf38() knlGS: [450023.204016] CS: 0010 DS: ES: CR0: 80050033 [450023.211346] CR2: 55eb5afaf2d8 CR3: 00359180a004 CR4: 003626e0 [450023.220602] DR0: DR1: DR2: [450023.229668] DR3: DR6: fffe0ff0 DR7: 0400 [450023.238621] Call Trace: [450023.242266] [450023.245426] cachefiles_read_waiter+0xe5/0x100 [cachefiles] [450023.252592] __wake_up_common+0x7e/0x140 [450023.257909] __wake_up_locked_key_bookmark+0x1b/0x20 [450023.264404] wake_up_page_bit+0xa7/0x100 [450023.269733] unlock_page+0x25/0x30 [450023.274491] __read_end_io+0xb6/0x110 [450023.279530] mpage_end_io+0x2f/0x40 [450023.284389] bio_endio+0xfb/0x160 [450023.289052] dec_pending+0x11c/0x210 [450023.294006] clone_endio+0x77/0x170 [450023.298874] bio_endio+0xfb/0x160 [450023.303540] blk_update_request+0x18a/0x2e0 [450023.309201] scsi_end_request+0x30/0x160 [450023.314571] scsi_io_completion+0x7c/0x540 [450023.320129] ? __update_load_avg_cfs_rq+0x212/0x2f0 [450023.326580] scsi_finish_command+0xe7/0x120 [450023.332259] scsi_softirq_done+0x14a/0x170 [450023.337840] blk_done_softirq+0x92/0xc0 [450023.343141] __do_softirq+0xe1/0x2d6 [450023.348145] irq_exit+0xae/0xb0 [450023.352670] smp_call_function_single_interrupt+0x48/0xd0 [450023.359735] call_function_single_interrupt+0xf/0x20 [450023.366323] [450023.369712] RIP: 0010:cpuidle_enter_state+0xc5/0x450 [450023.376326] Code: ff e8 5f 0c 81 ff 80 7d c7 00 74 17 9c 58 0f 1f 44 00 00 f6 c4 02 0f 85 65 03 00 00 31 ff e8 72 6e 87 ff fb 66 0f 1f 44 00 00 <45> 85 ed 0f 88 8f 02 00 00 49 63 cd 4c 8b 7d d0 4c 2b 7d c8 48 8d [450023.399419] RSP: 0018:baca8017be38 EFLAGS: 0246 ORIG_RAX: ff04 [450023.409020] RAX: 9872bf3aad00 RBX: a3159c00 RCX: 001f [450023.418148] RDX: RSI: 3a3fe5c1 RDI: [450023.427270] RBP: baca8017be78 R08: 0001994b295dad0d R09: 0001 [450023.436383] R10: 9872bf3a9a00 R11: 9872bf3a99e0 R12: daca7f583400 [450023.445496] R13: 0003 R14: 0003 R15: daca7f583400 [450023.454584] ? cpuidle_enter_state+0xa1/0x450 [450023.460544] cpuidle_enter+0x2e/0x40 [450023.465593] call_cpuidle+0x23/0x40 [450023.470525] do_idle+0x1dd/0x270 [450023.475147] cpu_startup_entry+0x20/0x30 [450023.480547] start_secondary+0x167/0x1c0 [450023.485934] secondary_startup_64+0xa4/0xb0 [450023.491620] Modules linked in: vhost_net vhost tap cpuid xt_state br_netfilter xt_physdev ip_set xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_n
[Kernel-packages] [Bug 1885696] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1885696 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1885696 Title: Kernel panic linux-image-5.4.0-39-generic with cachefiles Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu 20.04 server with latest kernel 5.4.0-39-generic panics under load when cachefilesd is used. This bug is known and fixed in upstream kernel 5.4.44 https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.4.44 cachefiles: Fix race between read_waiter and read_copier involving op->to_do [ Upstream commit 7bb0c5338436dae953622470d52689265867f032 ] https://github.com/torvalds/linux/commit/7bb0c5338436dae953622470d52689265867f032 #diff-14a48d14f7cd98c97d57211cfd758797 package: linux-image-5.4.0-39-generic, linux-image-generic Dmesg output: [450023.072377] FS-Cache: [450023.075150] FS-Cache: Assertion failed [450023.079496] FS-Cache: 4 == 5 is false [450023.083749] kernel BUG at fs/fscache/operation.c:69! [450023.089468] invalid opcode: [#1] SMP PTI [450023.094500] CPU: 13 PID: 0 Comm: swapper/13 Not tainted 5.4.0-37-generic #41-Ubuntu [450023.104057] Hardware name: Dell Inc. PowerEdge R430/0CN7X8, BIOS 2.11.0 12/23/2019 [450023.112660] RIP: 0010:fscache_enqueue_operation.cold+0xb7/0xb9 [fscache] [450023.120279] Code: a8 96 c0 e8 3f dc 1a e1 48 c7 c7 14 a8 96 c0 e8 33 dc 1a e1 41 8b 74 24 40 ba 05 00 00 00 48 c7 c7 28 98 96 c0 e8 1d dc 1a e1 <0f> 0b 48 c7 c7 06 a8 96 c0 e8 0f dc 1a e1 48 c7 c7 14 a8 96 c0 e8 [450023.141515] RSP: 0018:baca8cb88b98 EFLAGS: 00010046 [450023.147490] RAX: 0019 RBX: 98535b7f6540 RCX: 0006 [450023.156712] RDX: RSI: 0092 RDI: 9872bf3978c0 [450023.165774] RBP: baca8cb88bb0 R08: 337d R09: baca8f984020 [450023.175116] R10: 9852b7ebc2a0 R11: 0001 R12: 9872b870f740 [450023.184384] R13: 9838bd287580 R14: R15: baca8cb88c48 [450023.193659] FS: () GS:9872bf38() knlGS: [450023.204016] CS: 0010 DS: ES: CR0: 80050033 [450023.211346] CR2: 55eb5afaf2d8 CR3: 00359180a004 CR4: 003626e0 [450023.220602] DR0: DR1: DR2: [450023.229668] DR3: DR6: fffe0ff0 DR7: 0400 [450023.238621] Call Trace: [450023.242266] [450023.245426] cachefiles_read_waiter+0xe5/0x100 [cachefiles] [450023.252592] __wake_up_common+0x7e/0x140 [450023.257909] __wake_up_locked_key_bookmark+0x1b/0x20 [450023.264404] wake_up_page_bit+0xa7/0x100 [450023.269733] unlock_page+0x25/0x30 [450023.274491] __read_end_io+0xb6/0x110 [450023.279530] mpage_end_io+0x2f/0x40 [450023.284389] bio_endio+0xfb/0x160 [450023.289052] dec_pending+0x11c/0x210 [450023.294006] clone_endio+0x77/0x170 [450023.298874] bio_endio+0xfb/0x160 [450023.303540] blk_update_request+0x18a/0x2e0 [450023.309201] scsi_end_request+0x30/0x160 [450023.314571] scsi_io_completion+0x7c/0x540 [450023.320129] ? __update_load_avg_cfs_rq+0x212/0x2f0 [450023.326580] scsi_finish_command+0xe7/0x120 [450023.332259] scsi_softirq_done+0x14a/0x170 [450023.337840] blk_done_softirq+0x92/0xc0 [450023.343141] __do_softirq+0xe1/0x2d6 [450023.348145] irq_exit+0xae/0xb0 [450023.352670] smp_call_function_single_interrupt+0x48/0xd0 [450023.359735] call_function_single_interrupt+0xf/0x20 [450023.366323] [450023.369712] RIP: 0010:cpuidle_enter_state+0xc5/0x450 [450023.376326] Code: ff e8 5f 0c 81 ff 80 7d c7 00 74 17 9c 58 0f 1f 44 00 00 f6 c4 02 0f 85 65 03 00 00 31 ff e8 72 6e 87 ff fb 66 0f 1f 44 00 00 <45> 85 ed 0f 88 8f 02 00 00 49 63 cd 4c 8b 7d d0 4c 2b 7d c8 48 8d [450023.399419] RSP: 0018:baca8017be38 EFLAGS: 0246 ORIG_RAX: ff04 [450023.409020] RAX: 9872bf3aad00 RBX: a3159c00 RCX: 001f [450023.418148] RDX: RSI: 3a3fe5c1 RDI: [450023.427270] RBP: baca8017be78 R08: 0001994b295dad0d R09: 0001 [450023.436383] R10: 9872bf3a9a00 R11: 9872bf3a99e0 R12: daca7f583400 [450023.445496] R13: 00
[Kernel-packages] [Bug 1885693] Re: Unwanted reboot after screen is locked
** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1885693 Title: Unwanted reboot after screen is locked Status in linux package in Ubuntu: Confirmed Bug description: After locking the screen to leave the computer for a few minutes, I come back to a computer that is freshly rebooted. It usually happens 1 out of 4 or 5 times when locking the screen. This only happens when my laptop (Lenovo T470s, also seen with T490) is connected to my USB-C dock. The problem has been observed with 18.04, 19.10 and 20.04. /var/log/syslog contains: Jun 30 10:47:05 jbn3 kernel: [33470.649606] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. Jun 30 10:47:23 jbn3 kernel: [33488.187142] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. Jun 30 10:47:23 jbn3 kernel: [33488.419723] [drm:pipe_config_mismatch [i915]] *ERROR* mismatch in pixel_rate (expected 241500, found 482999) Jun 30 10:47:23 jbn3 kernel: [33488.419818] [drm:pipe_config_mismatch [i915]] *ERROR* mismatch in shared_dpll (expected a870403d, found 5108ff4b) Jun 30 10:47:23 jbn3 kernel: [33488.419902] [drm:pipe_config_mismatch [i915]] *ERROR* mismatch in dpll_hw_state.ctrl1 (expected 0x0003, found 0x0001) Jun 30 10:47:23 jbn3 kernel: [33488.419986] [drm:pipe_config_mismatch [i915]] *ERROR* mismatch in base.adjusted_mode.crtc_clock (expected 241500, found 482999) Jun 30 10:47:23 jbn3 kernel: [33488.420067] [drm:pipe_config_mismatch [i915]] *ERROR* mismatch in port_clock (expected 27, found 54) Jun 30 10:47:23 jbn3 kernel: [33488.420071] [ cut here ] Jun 30 10:47:23 jbn3 kernel: [33488.420072] pipe state doesn't match! Jun 30 10:47:23 jbn3 kernel: [33488.420249] WARNING: CPU: 0 PID: 2300 at drivers/gpu/drm/i915/display/intel_display.c:13158 verify_crtc_state+0x2ad/0x300 [i915] Jun 30 10:47:23 jbn3 kernel: [33488.420251] Modules linked in: xt_nat xt_tcpudp veth xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo xt_addrtype iptable_filter iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 bpfilter br_netfilter bridge stp llc hid_generic snd_usb_audio usbhid snd_usbmidi_lib hid cdc_ether r8152 vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) ccm aufs overlay bnep nls_iso8859_1 joydev intel_rapl_msr mei_hdcp cdc_mbim qcserial usb_wwan cdc_wdm usbserial cdc_ncm usbnet mii uvcvideo btusb btrtl snd_hda_codec_hdmi btbcm btintel intel_rapl_common x86_pkg_temp_thermal intel_powerclamp coretemp bluetooth kvm_intel snd_hda_codec_realtek snd_hda_codec_generic kvm snd_hda_intel snd_intel_dspcfg snd_hda_codec intel_cstate rmi_smbus ecdh_generic rmi_core intel_rapl_perf ecc videobuf2_vmalloc snd_hda_core videobuf2_memops videobuf2_v4l2 snd_hwdep iwlmvm snd_seq_midi videobuf2_common snd_seq_midi_event mac80211 videodev intel_wmi_thunderbolt libarc4 snd_pcm input_leds iwlwifi Jun 30 10:47:23 jbn3 kernel: [33488.420310] snd_rawmidi mc serio_raw snd_seq wmi_bmof thinkpad_acpi nvram cfg80211 ledtrig_audio mei_me intel_xhci_usb_role_switch mei snd_seq_device intel_pch_thermal snd_timer ucsi_acpi typec_ucsi roles typec snd soundcore acpi_pad mac_hid sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables autofs4 btrfs xor zstd_compress raid6_pq libcrc32c dm_crypt uas usb_storage i915 crct10dif_pclmul crc32_pclmul nvme ghash_clmulni_intel i2c_algo_bit aesni_intel crypto_simd cryptd glue_helper psmouse e1000e i2c_i801 nvme_core drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops thunderbolt drm wmi video Jun 30 10:47:23 jbn3 kernel: [33488.420358] CPU: 0 PID: 2300 Comm: Xorg Tainted: G OE 5.4.0-39-generic #43-Ubuntu Jun 30 10:47:23 jbn3 kernel: [33488.420360] Hardware name: LENOVO 20HF004MMX/20HF004MMX, BIOS N1WET59W (1.38 ) 04/22/2020 Jun 30 10:47:23 jbn3 kernel: [33488.420437] RIP: 0010:verify_crtc_state+0x2ad/0x300 [i915] Jun 30 10:47:23 jbn3 kernel: [33488.420441] Code: b6 45 bf e9 8d fe ff ff 80 3d 45 77 10 00 00 0f b6 f0 48 c7 c7 40 aa 85 c0 75 32 e8 1d 48 d5 ff e9 1e fe ff ff e8 6e 9e b1 ef <0f> 0b e9 1b ff ff ff e8 62 9e b1 ef 0f 0b e9 85 fe ff ff e8 56 9e Jun 30 10:47:23 jbn3 kernel: [33488.420444] RSP: 0018:b1b74290fa80 EFLAGS: 00010282 Jun 30 10:47:23 jbn3 kernel: [33488.420448] RAX: RBX: 97a35f0002b0 RCX: 0006 Jun 30 10:47:23 jbn3 kernel: [33488.420450] RDX: 0007 RSI: 0092 RDI: 97a3724178c0 Jun 30 10:47:23 jbn3 kernel: [33488.420452] RBP: b1b74290fac8 R08: 0ae9 R09: 0004 Jun 30 10:47:23 jbn3 ke
[Kernel-packages] [Bug 1885730] [NEW] Bring back ondemand.service or switch kernel default governor for pstate - pstate now defaults to performance governor
Public bug reported: In a recent merge from Debian we lost ondemand.service, meaning all CPUs now run in Turbo all the time when idle, which is clearly suboptimal. The discussion in bug 1806012 seems misleading, focusing on p-state vs other drivers, when in fact, the script actually set the default governor for the pstate driver on platforms that use pstate. Everything below only looks at systems that use pstate. pstate has two governors: performance and powerstate. performance runs CPU at maximum frequency constantly, and powersave can be configured using various energy profiles energy profiles: - performance - balanced performance - balanced power - power It defaults to balanced performance, I think, but I'm not sure. Whether performance governor is faster than powersave governor is not even clear. https://www.phoronix.com/scan.php?page=article&item=linux50 -pstate-cpufreq&num=5 benchmarked them, but did not benchmark the individual energy profiles. For a desktop/laptop, the expected behavior is the powersave governor with balanced_performance on AC and balanced_power on battery. I don't know about servers or VMs, but the benchmark series seems to indicate it does not really matter much performance wise. I think most other distributions configure their kernels to use the powersave governor by default, whereas we configure it to use the performance governor and then switch it later in the boot to get the maximum performance during bootup. It's not clear to me that's actually useful. ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: rls-gg-incoming ** Summary changed: - Bring back ondemand.service - pstate now defaults to performance governor + Bring back ondemand.service or switch kernel default governor for pstate - pstate now defaults to performance governor ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1885730 Title: Bring back ondemand.service or switch kernel default governor for pstate - pstate now defaults to performance governor Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: New Bug description: In a recent merge from Debian we lost ondemand.service, meaning all CPUs now run in Turbo all the time when idle, which is clearly suboptimal. The discussion in bug 1806012 seems misleading, focusing on p-state vs other drivers, when in fact, the script actually set the default governor for the pstate driver on platforms that use pstate. Everything below only looks at systems that use pstate. pstate has two governors: performance and powerstate. performance runs CPU at maximum frequency constantly, and powersave can be configured using various energy profiles energy profiles: - performance - balanced performance - balanced power - power It defaults to balanced performance, I think, but I'm not sure. Whether performance governor is faster than powersave governor is not even clear. https://www.phoronix.com/scan.php?page=article&item=linux50-pstate- cpufreq&num=5 benchmarked them, but did not benchmark the individual energy profiles. For a desktop/laptop, the expected behavior is the powersave governor with balanced_performance on AC and balanced_power on battery. I don't know about servers or VMs, but the benchmark series seems to indicate it does not really matter much performance wise. I think most other distributions configure their kernels to use the powersave governor by default, whereas we configure it to use the performance governor and then switch it later in the boot to get the maximum performance during bootup. It's not clear to me that's actually useful. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1885730/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1885696] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1885696/+attachment/5388461/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1885696 Title: Kernel panic linux-image-5.4.0-39-generic with cachefiles Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 20.04 server with latest kernel 5.4.0-39-generic panics under load when cachefilesd is used. This bug is known and fixed in upstream kernel 5.4.44 https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.4.44 cachefiles: Fix race between read_waiter and read_copier involving op->to_do [ Upstream commit 7bb0c5338436dae953622470d52689265867f032 ] https://github.com/torvalds/linux/commit/7bb0c5338436dae953622470d52689265867f032 #diff-14a48d14f7cd98c97d57211cfd758797 package: linux-image-5.4.0-39-generic, linux-image-generic Dmesg output: [450023.072377] FS-Cache: [450023.075150] FS-Cache: Assertion failed [450023.079496] FS-Cache: 4 == 5 is false [450023.083749] kernel BUG at fs/fscache/operation.c:69! [450023.089468] invalid opcode: [#1] SMP PTI [450023.094500] CPU: 13 PID: 0 Comm: swapper/13 Not tainted 5.4.0-37-generic #41-Ubuntu [450023.104057] Hardware name: Dell Inc. PowerEdge R430/0CN7X8, BIOS 2.11.0 12/23/2019 [450023.112660] RIP: 0010:fscache_enqueue_operation.cold+0xb7/0xb9 [fscache] [450023.120279] Code: a8 96 c0 e8 3f dc 1a e1 48 c7 c7 14 a8 96 c0 e8 33 dc 1a e1 41 8b 74 24 40 ba 05 00 00 00 48 c7 c7 28 98 96 c0 e8 1d dc 1a e1 <0f> 0b 48 c7 c7 06 a8 96 c0 e8 0f dc 1a e1 48 c7 c7 14 a8 96 c0 e8 [450023.141515] RSP: 0018:baca8cb88b98 EFLAGS: 00010046 [450023.147490] RAX: 0019 RBX: 98535b7f6540 RCX: 0006 [450023.156712] RDX: RSI: 0092 RDI: 9872bf3978c0 [450023.165774] RBP: baca8cb88bb0 R08: 337d R09: baca8f984020 [450023.175116] R10: 9852b7ebc2a0 R11: 0001 R12: 9872b870f740 [450023.184384] R13: 9838bd287580 R14: R15: baca8cb88c48 [450023.193659] FS: () GS:9872bf38() knlGS: [450023.204016] CS: 0010 DS: ES: CR0: 80050033 [450023.211346] CR2: 55eb5afaf2d8 CR3: 00359180a004 CR4: 003626e0 [450023.220602] DR0: DR1: DR2: [450023.229668] DR3: DR6: fffe0ff0 DR7: 0400 [450023.238621] Call Trace: [450023.242266] [450023.245426] cachefiles_read_waiter+0xe5/0x100 [cachefiles] [450023.252592] __wake_up_common+0x7e/0x140 [450023.257909] __wake_up_locked_key_bookmark+0x1b/0x20 [450023.264404] wake_up_page_bit+0xa7/0x100 [450023.269733] unlock_page+0x25/0x30 [450023.274491] __read_end_io+0xb6/0x110 [450023.279530] mpage_end_io+0x2f/0x40 [450023.284389] bio_endio+0xfb/0x160 [450023.289052] dec_pending+0x11c/0x210 [450023.294006] clone_endio+0x77/0x170 [450023.298874] bio_endio+0xfb/0x160 [450023.303540] blk_update_request+0x18a/0x2e0 [450023.309201] scsi_end_request+0x30/0x160 [450023.314571] scsi_io_completion+0x7c/0x540 [450023.320129] ? __update_load_avg_cfs_rq+0x212/0x2f0 [450023.326580] scsi_finish_command+0xe7/0x120 [450023.332259] scsi_softirq_done+0x14a/0x170 [450023.337840] blk_done_softirq+0x92/0xc0 [450023.343141] __do_softirq+0xe1/0x2d6 [450023.348145] irq_exit+0xae/0xb0 [450023.352670] smp_call_function_single_interrupt+0x48/0xd0 [450023.359735] call_function_single_interrupt+0xf/0x20 [450023.366323] [450023.369712] RIP: 0010:cpuidle_enter_state+0xc5/0x450 [450023.376326] Code: ff e8 5f 0c 81 ff 80 7d c7 00 74 17 9c 58 0f 1f 44 00 00 f6 c4 02 0f 85 65 03 00 00 31 ff e8 72 6e 87 ff fb 66 0f 1f 44 00 00 <45> 85 ed 0f 88 8f 02 00 00 49 63 cd 4c 8b 7d d0 4c 2b 7d c8 48 8d [450023.399419] RSP: 0018:baca8017be38 EFLAGS: 0246 ORIG_RAX: ff04 [450023.409020] RAX: 9872bf3aad00 RBX: a3159c00 RCX: 001f [450023.418148] RDX: RSI: 3a3fe5c1 RDI: [450023.427270] RBP: baca8017be78 R08: 0001994b295dad0d R09: 0001 [450023.436383] R10: 9872bf3a9a00 R11: 9872bf3a99e0 R12: daca7f583400 [450023.445496] R13: 0003 R14: 0003 R15: daca7f583400 [450023.454584] ? cpuidle_enter_state+0xa1/0x450 [450023.460544] cpuidle_enter+0x2e/0x40 [450023.465593] call_cpuidle+0x23/0x40 [450023.470525] do_idle+0x1dd/0x270 [450023.475147] cpu_startup_entry+0x20/0x30 [450023.480547] start_secondary+0x167/0x1c0 [450023.485934] secondary_startup_64+0xa4/0xb0 [450023.491620] Modules linked in: vhost_net vhost tap cpuid xt_state br_netfilter xt_physdev ip_set xt_CHECKSUM xt_
[Kernel-packages] [Bug 1885696] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1885696/+attachment/5388463/+files/Lsusb-v.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/1885696 Title: Kernel panic linux-image-5.4.0-39-generic with cachefiles Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 20.04 server with latest kernel 5.4.0-39-generic panics under load when cachefilesd is used. This bug is known and fixed in upstream kernel 5.4.44 https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.4.44 cachefiles: Fix race between read_waiter and read_copier involving op->to_do [ Upstream commit 7bb0c5338436dae953622470d52689265867f032 ] https://github.com/torvalds/linux/commit/7bb0c5338436dae953622470d52689265867f032 #diff-14a48d14f7cd98c97d57211cfd758797 package: linux-image-5.4.0-39-generic, linux-image-generic Dmesg output: [450023.072377] FS-Cache: [450023.075150] FS-Cache: Assertion failed [450023.079496] FS-Cache: 4 == 5 is false [450023.083749] kernel BUG at fs/fscache/operation.c:69! [450023.089468] invalid opcode: [#1] SMP PTI [450023.094500] CPU: 13 PID: 0 Comm: swapper/13 Not tainted 5.4.0-37-generic #41-Ubuntu [450023.104057] Hardware name: Dell Inc. PowerEdge R430/0CN7X8, BIOS 2.11.0 12/23/2019 [450023.112660] RIP: 0010:fscache_enqueue_operation.cold+0xb7/0xb9 [fscache] [450023.120279] Code: a8 96 c0 e8 3f dc 1a e1 48 c7 c7 14 a8 96 c0 e8 33 dc 1a e1 41 8b 74 24 40 ba 05 00 00 00 48 c7 c7 28 98 96 c0 e8 1d dc 1a e1 <0f> 0b 48 c7 c7 06 a8 96 c0 e8 0f dc 1a e1 48 c7 c7 14 a8 96 c0 e8 [450023.141515] RSP: 0018:baca8cb88b98 EFLAGS: 00010046 [450023.147490] RAX: 0019 RBX: 98535b7f6540 RCX: 0006 [450023.156712] RDX: RSI: 0092 RDI: 9872bf3978c0 [450023.165774] RBP: baca8cb88bb0 R08: 337d R09: baca8f984020 [450023.175116] R10: 9852b7ebc2a0 R11: 0001 R12: 9872b870f740 [450023.184384] R13: 9838bd287580 R14: R15: baca8cb88c48 [450023.193659] FS: () GS:9872bf38() knlGS: [450023.204016] CS: 0010 DS: ES: CR0: 80050033 [450023.211346] CR2: 55eb5afaf2d8 CR3: 00359180a004 CR4: 003626e0 [450023.220602] DR0: DR1: DR2: [450023.229668] DR3: DR6: fffe0ff0 DR7: 0400 [450023.238621] Call Trace: [450023.242266] [450023.245426] cachefiles_read_waiter+0xe5/0x100 [cachefiles] [450023.252592] __wake_up_common+0x7e/0x140 [450023.257909] __wake_up_locked_key_bookmark+0x1b/0x20 [450023.264404] wake_up_page_bit+0xa7/0x100 [450023.269733] unlock_page+0x25/0x30 [450023.274491] __read_end_io+0xb6/0x110 [450023.279530] mpage_end_io+0x2f/0x40 [450023.284389] bio_endio+0xfb/0x160 [450023.289052] dec_pending+0x11c/0x210 [450023.294006] clone_endio+0x77/0x170 [450023.298874] bio_endio+0xfb/0x160 [450023.303540] blk_update_request+0x18a/0x2e0 [450023.309201] scsi_end_request+0x30/0x160 [450023.314571] scsi_io_completion+0x7c/0x540 [450023.320129] ? __update_load_avg_cfs_rq+0x212/0x2f0 [450023.326580] scsi_finish_command+0xe7/0x120 [450023.332259] scsi_softirq_done+0x14a/0x170 [450023.337840] blk_done_softirq+0x92/0xc0 [450023.343141] __do_softirq+0xe1/0x2d6 [450023.348145] irq_exit+0xae/0xb0 [450023.352670] smp_call_function_single_interrupt+0x48/0xd0 [450023.359735] call_function_single_interrupt+0xf/0x20 [450023.366323] [450023.369712] RIP: 0010:cpuidle_enter_state+0xc5/0x450 [450023.376326] Code: ff e8 5f 0c 81 ff 80 7d c7 00 74 17 9c 58 0f 1f 44 00 00 f6 c4 02 0f 85 65 03 00 00 31 ff e8 72 6e 87 ff fb 66 0f 1f 44 00 00 <45> 85 ed 0f 88 8f 02 00 00 49 63 cd 4c 8b 7d d0 4c 2b 7d c8 48 8d [450023.399419] RSP: 0018:baca8017be38 EFLAGS: 0246 ORIG_RAX: ff04 [450023.409020] RAX: 9872bf3aad00 RBX: a3159c00 RCX: 001f [450023.418148] RDX: RSI: 3a3fe5c1 RDI: [450023.427270] RBP: baca8017be78 R08: 0001994b295dad0d R09: 0001 [450023.436383] R10: 9872bf3a9a00 R11: 9872bf3a99e0 R12: daca7f583400 [450023.445496] R13: 0003 R14: 0003 R15: daca7f583400 [450023.454584] ? cpuidle_enter_state+0xa1/0x450 [450023.460544] cpuidle_enter+0x2e/0x40 [450023.465593] call_cpuidle+0x23/0x40 [450023.470525] do_idle+0x1dd/0x270 [450023.475147] cpu_startup_entry+0x20/0x30 [450023.480547] start_secondary+0x167/0x1c0 [450023.485934] secondary_startup_64+0xa4/0xb0 [450023.491620] Modules linked in: vhost_net vhost tap cpuid xt_state br_netfilter xt_physdev ip_set xt_CHECKSU
[Kernel-packages] [Bug 1885696] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1885696/+attachment/5388465/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1885696 Title: Kernel panic linux-image-5.4.0-39-generic with cachefiles Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 20.04 server with latest kernel 5.4.0-39-generic panics under load when cachefilesd is used. This bug is known and fixed in upstream kernel 5.4.44 https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.4.44 cachefiles: Fix race between read_waiter and read_copier involving op->to_do [ Upstream commit 7bb0c5338436dae953622470d52689265867f032 ] https://github.com/torvalds/linux/commit/7bb0c5338436dae953622470d52689265867f032 #diff-14a48d14f7cd98c97d57211cfd758797 package: linux-image-5.4.0-39-generic, linux-image-generic Dmesg output: [450023.072377] FS-Cache: [450023.075150] FS-Cache: Assertion failed [450023.079496] FS-Cache: 4 == 5 is false [450023.083749] kernel BUG at fs/fscache/operation.c:69! [450023.089468] invalid opcode: [#1] SMP PTI [450023.094500] CPU: 13 PID: 0 Comm: swapper/13 Not tainted 5.4.0-37-generic #41-Ubuntu [450023.104057] Hardware name: Dell Inc. PowerEdge R430/0CN7X8, BIOS 2.11.0 12/23/2019 [450023.112660] RIP: 0010:fscache_enqueue_operation.cold+0xb7/0xb9 [fscache] [450023.120279] Code: a8 96 c0 e8 3f dc 1a e1 48 c7 c7 14 a8 96 c0 e8 33 dc 1a e1 41 8b 74 24 40 ba 05 00 00 00 48 c7 c7 28 98 96 c0 e8 1d dc 1a e1 <0f> 0b 48 c7 c7 06 a8 96 c0 e8 0f dc 1a e1 48 c7 c7 14 a8 96 c0 e8 [450023.141515] RSP: 0018:baca8cb88b98 EFLAGS: 00010046 [450023.147490] RAX: 0019 RBX: 98535b7f6540 RCX: 0006 [450023.156712] RDX: RSI: 0092 RDI: 9872bf3978c0 [450023.165774] RBP: baca8cb88bb0 R08: 337d R09: baca8f984020 [450023.175116] R10: 9852b7ebc2a0 R11: 0001 R12: 9872b870f740 [450023.184384] R13: 9838bd287580 R14: R15: baca8cb88c48 [450023.193659] FS: () GS:9872bf38() knlGS: [450023.204016] CS: 0010 DS: ES: CR0: 80050033 [450023.211346] CR2: 55eb5afaf2d8 CR3: 00359180a004 CR4: 003626e0 [450023.220602] DR0: DR1: DR2: [450023.229668] DR3: DR6: fffe0ff0 DR7: 0400 [450023.238621] Call Trace: [450023.242266] [450023.245426] cachefiles_read_waiter+0xe5/0x100 [cachefiles] [450023.252592] __wake_up_common+0x7e/0x140 [450023.257909] __wake_up_locked_key_bookmark+0x1b/0x20 [450023.264404] wake_up_page_bit+0xa7/0x100 [450023.269733] unlock_page+0x25/0x30 [450023.274491] __read_end_io+0xb6/0x110 [450023.279530] mpage_end_io+0x2f/0x40 [450023.284389] bio_endio+0xfb/0x160 [450023.289052] dec_pending+0x11c/0x210 [450023.294006] clone_endio+0x77/0x170 [450023.298874] bio_endio+0xfb/0x160 [450023.303540] blk_update_request+0x18a/0x2e0 [450023.309201] scsi_end_request+0x30/0x160 [450023.314571] scsi_io_completion+0x7c/0x540 [450023.320129] ? __update_load_avg_cfs_rq+0x212/0x2f0 [450023.326580] scsi_finish_command+0xe7/0x120 [450023.332259] scsi_softirq_done+0x14a/0x170 [450023.337840] blk_done_softirq+0x92/0xc0 [450023.343141] __do_softirq+0xe1/0x2d6 [450023.348145] irq_exit+0xae/0xb0 [450023.352670] smp_call_function_single_interrupt+0x48/0xd0 [450023.359735] call_function_single_interrupt+0xf/0x20 [450023.366323] [450023.369712] RIP: 0010:cpuidle_enter_state+0xc5/0x450 [450023.376326] Code: ff e8 5f 0c 81 ff 80 7d c7 00 74 17 9c 58 0f 1f 44 00 00 f6 c4 02 0f 85 65 03 00 00 31 ff e8 72 6e 87 ff fb 66 0f 1f 44 00 00 <45> 85 ed 0f 88 8f 02 00 00 49 63 cd 4c 8b 7d d0 4c 2b 7d c8 48 8d [450023.399419] RSP: 0018:baca8017be38 EFLAGS: 0246 ORIG_RAX: ff04 [450023.409020] RAX: 9872bf3aad00 RBX: a3159c00 RCX: 001f [450023.418148] RDX: RSI: 3a3fe5c1 RDI: [450023.427270] RBP: baca8017be78 R08: 0001994b295dad0d R09: 0001 [450023.436383] R10: 9872bf3a9a00 R11: 9872bf3a99e0 R12: daca7f583400 [450023.445496] R13: 0003 R14: 0003 R15: daca7f583400 [450023.454584] ? cpuidle_enter_state+0xa1/0x450 [450023.460544] cpuidle_enter+0x2e/0x40 [450023.465593] call_cpuidle+0x23/0x40 [450023.470525] do_idle+0x1dd/0x270 [450023.475147] cpu_startup_entry+0x20/0x30 [450023.480547] start_secondary+0x167/0x1c0 [450023.485934] secondary_startup_64+0xa4/0xb0 [450023.491620] Modules linked in: vhost_net vhost tap cpuid xt_state br_netfilter xt_physdev ip_
[Kernel-packages] [Bug 1885696] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1885696/+attachment/5388462/+files/Lspci-vt.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/1885696 Title: Kernel panic linux-image-5.4.0-39-generic with cachefiles Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 20.04 server with latest kernel 5.4.0-39-generic panics under load when cachefilesd is used. This bug is known and fixed in upstream kernel 5.4.44 https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.4.44 cachefiles: Fix race between read_waiter and read_copier involving op->to_do [ Upstream commit 7bb0c5338436dae953622470d52689265867f032 ] https://github.com/torvalds/linux/commit/7bb0c5338436dae953622470d52689265867f032 #diff-14a48d14f7cd98c97d57211cfd758797 package: linux-image-5.4.0-39-generic, linux-image-generic Dmesg output: [450023.072377] FS-Cache: [450023.075150] FS-Cache: Assertion failed [450023.079496] FS-Cache: 4 == 5 is false [450023.083749] kernel BUG at fs/fscache/operation.c:69! [450023.089468] invalid opcode: [#1] SMP PTI [450023.094500] CPU: 13 PID: 0 Comm: swapper/13 Not tainted 5.4.0-37-generic #41-Ubuntu [450023.104057] Hardware name: Dell Inc. PowerEdge R430/0CN7X8, BIOS 2.11.0 12/23/2019 [450023.112660] RIP: 0010:fscache_enqueue_operation.cold+0xb7/0xb9 [fscache] [450023.120279] Code: a8 96 c0 e8 3f dc 1a e1 48 c7 c7 14 a8 96 c0 e8 33 dc 1a e1 41 8b 74 24 40 ba 05 00 00 00 48 c7 c7 28 98 96 c0 e8 1d dc 1a e1 <0f> 0b 48 c7 c7 06 a8 96 c0 e8 0f dc 1a e1 48 c7 c7 14 a8 96 c0 e8 [450023.141515] RSP: 0018:baca8cb88b98 EFLAGS: 00010046 [450023.147490] RAX: 0019 RBX: 98535b7f6540 RCX: 0006 [450023.156712] RDX: RSI: 0092 RDI: 9872bf3978c0 [450023.165774] RBP: baca8cb88bb0 R08: 337d R09: baca8f984020 [450023.175116] R10: 9852b7ebc2a0 R11: 0001 R12: 9872b870f740 [450023.184384] R13: 9838bd287580 R14: R15: baca8cb88c48 [450023.193659] FS: () GS:9872bf38() knlGS: [450023.204016] CS: 0010 DS: ES: CR0: 80050033 [450023.211346] CR2: 55eb5afaf2d8 CR3: 00359180a004 CR4: 003626e0 [450023.220602] DR0: DR1: DR2: [450023.229668] DR3: DR6: fffe0ff0 DR7: 0400 [450023.238621] Call Trace: [450023.242266] [450023.245426] cachefiles_read_waiter+0xe5/0x100 [cachefiles] [450023.252592] __wake_up_common+0x7e/0x140 [450023.257909] __wake_up_locked_key_bookmark+0x1b/0x20 [450023.264404] wake_up_page_bit+0xa7/0x100 [450023.269733] unlock_page+0x25/0x30 [450023.274491] __read_end_io+0xb6/0x110 [450023.279530] mpage_end_io+0x2f/0x40 [450023.284389] bio_endio+0xfb/0x160 [450023.289052] dec_pending+0x11c/0x210 [450023.294006] clone_endio+0x77/0x170 [450023.298874] bio_endio+0xfb/0x160 [450023.303540] blk_update_request+0x18a/0x2e0 [450023.309201] scsi_end_request+0x30/0x160 [450023.314571] scsi_io_completion+0x7c/0x540 [450023.320129] ? __update_load_avg_cfs_rq+0x212/0x2f0 [450023.326580] scsi_finish_command+0xe7/0x120 [450023.332259] scsi_softirq_done+0x14a/0x170 [450023.337840] blk_done_softirq+0x92/0xc0 [450023.343141] __do_softirq+0xe1/0x2d6 [450023.348145] irq_exit+0xae/0xb0 [450023.352670] smp_call_function_single_interrupt+0x48/0xd0 [450023.359735] call_function_single_interrupt+0xf/0x20 [450023.366323] [450023.369712] RIP: 0010:cpuidle_enter_state+0xc5/0x450 [450023.376326] Code: ff e8 5f 0c 81 ff 80 7d c7 00 74 17 9c 58 0f 1f 44 00 00 f6 c4 02 0f 85 65 03 00 00 31 ff e8 72 6e 87 ff fb 66 0f 1f 44 00 00 <45> 85 ed 0f 88 8f 02 00 00 49 63 cd 4c 8b 7d d0 4c 2b 7d c8 48 8d [450023.399419] RSP: 0018:baca8017be38 EFLAGS: 0246 ORIG_RAX: ff04 [450023.409020] RAX: 9872bf3aad00 RBX: a3159c00 RCX: 001f [450023.418148] RDX: RSI: 3a3fe5c1 RDI: [450023.427270] RBP: baca8017be78 R08: 0001994b295dad0d R09: 0001 [450023.436383] R10: 9872bf3a9a00 R11: 9872bf3a99e0 R12: daca7f583400 [450023.445496] R13: 0003 R14: 0003 R15: daca7f583400 [450023.454584] ? cpuidle_enter_state+0xa1/0x450 [450023.460544] cpuidle_enter+0x2e/0x40 [450023.465593] call_cpuidle+0x23/0x40 [450023.470525] do_idle+0x1dd/0x270 [450023.475147] cpu_startup_entry+0x20/0x30 [450023.480547] start_secondary+0x167/0x1c0 [450023.485934] secondary_startup_64+0xa4/0xb0 [450023.491620] Modules linked in: vhost_net vhost tap cpuid xt_state br_netfilter xt_physdev ip_set xt_CHECK
[Kernel-packages] [Bug 1885696] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1885696/+attachment/5388467/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1885696 Title: Kernel panic linux-image-5.4.0-39-generic with cachefiles Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 20.04 server with latest kernel 5.4.0-39-generic panics under load when cachefilesd is used. This bug is known and fixed in upstream kernel 5.4.44 https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.4.44 cachefiles: Fix race between read_waiter and read_copier involving op->to_do [ Upstream commit 7bb0c5338436dae953622470d52689265867f032 ] https://github.com/torvalds/linux/commit/7bb0c5338436dae953622470d52689265867f032 #diff-14a48d14f7cd98c97d57211cfd758797 package: linux-image-5.4.0-39-generic, linux-image-generic Dmesg output: [450023.072377] FS-Cache: [450023.075150] FS-Cache: Assertion failed [450023.079496] FS-Cache: 4 == 5 is false [450023.083749] kernel BUG at fs/fscache/operation.c:69! [450023.089468] invalid opcode: [#1] SMP PTI [450023.094500] CPU: 13 PID: 0 Comm: swapper/13 Not tainted 5.4.0-37-generic #41-Ubuntu [450023.104057] Hardware name: Dell Inc. PowerEdge R430/0CN7X8, BIOS 2.11.0 12/23/2019 [450023.112660] RIP: 0010:fscache_enqueue_operation.cold+0xb7/0xb9 [fscache] [450023.120279] Code: a8 96 c0 e8 3f dc 1a e1 48 c7 c7 14 a8 96 c0 e8 33 dc 1a e1 41 8b 74 24 40 ba 05 00 00 00 48 c7 c7 28 98 96 c0 e8 1d dc 1a e1 <0f> 0b 48 c7 c7 06 a8 96 c0 e8 0f dc 1a e1 48 c7 c7 14 a8 96 c0 e8 [450023.141515] RSP: 0018:baca8cb88b98 EFLAGS: 00010046 [450023.147490] RAX: 0019 RBX: 98535b7f6540 RCX: 0006 [450023.156712] RDX: RSI: 0092 RDI: 9872bf3978c0 [450023.165774] RBP: baca8cb88bb0 R08: 337d R09: baca8f984020 [450023.175116] R10: 9852b7ebc2a0 R11: 0001 R12: 9872b870f740 [450023.184384] R13: 9838bd287580 R14: R15: baca8cb88c48 [450023.193659] FS: () GS:9872bf38() knlGS: [450023.204016] CS: 0010 DS: ES: CR0: 80050033 [450023.211346] CR2: 55eb5afaf2d8 CR3: 00359180a004 CR4: 003626e0 [450023.220602] DR0: DR1: DR2: [450023.229668] DR3: DR6: fffe0ff0 DR7: 0400 [450023.238621] Call Trace: [450023.242266] [450023.245426] cachefiles_read_waiter+0xe5/0x100 [cachefiles] [450023.252592] __wake_up_common+0x7e/0x140 [450023.257909] __wake_up_locked_key_bookmark+0x1b/0x20 [450023.264404] wake_up_page_bit+0xa7/0x100 [450023.269733] unlock_page+0x25/0x30 [450023.274491] __read_end_io+0xb6/0x110 [450023.279530] mpage_end_io+0x2f/0x40 [450023.284389] bio_endio+0xfb/0x160 [450023.289052] dec_pending+0x11c/0x210 [450023.294006] clone_endio+0x77/0x170 [450023.298874] bio_endio+0xfb/0x160 [450023.303540] blk_update_request+0x18a/0x2e0 [450023.309201] scsi_end_request+0x30/0x160 [450023.314571] scsi_io_completion+0x7c/0x540 [450023.320129] ? __update_load_avg_cfs_rq+0x212/0x2f0 [450023.326580] scsi_finish_command+0xe7/0x120 [450023.332259] scsi_softirq_done+0x14a/0x170 [450023.337840] blk_done_softirq+0x92/0xc0 [450023.343141] __do_softirq+0xe1/0x2d6 [450023.348145] irq_exit+0xae/0xb0 [450023.352670] smp_call_function_single_interrupt+0x48/0xd0 [450023.359735] call_function_single_interrupt+0xf/0x20 [450023.366323] [450023.369712] RIP: 0010:cpuidle_enter_state+0xc5/0x450 [450023.376326] Code: ff e8 5f 0c 81 ff 80 7d c7 00 74 17 9c 58 0f 1f 44 00 00 f6 c4 02 0f 85 65 03 00 00 31 ff e8 72 6e 87 ff fb 66 0f 1f 44 00 00 <45> 85 ed 0f 88 8f 02 00 00 49 63 cd 4c 8b 7d d0 4c 2b 7d c8 48 8d [450023.399419] RSP: 0018:baca8017be38 EFLAGS: 0246 ORIG_RAX: ff04 [450023.409020] RAX: 9872bf3aad00 RBX: a3159c00 RCX: 001f [450023.418148] RDX: RSI: 3a3fe5c1 RDI: [450023.427270] RBP: baca8017be78 R08: 0001994b295dad0d R09: 0001 [450023.436383] R10: 9872bf3a9a00 R11: 9872bf3a99e0 R12: daca7f583400 [450023.445496] R13: 0003 R14: 0003 R15: daca7f583400 [450023.454584] ? cpuidle_enter_state+0xa1/0x450 [450023.460544] cpuidle_enter+0x2e/0x40 [450023.465593] call_cpuidle+0x23/0x40 [450023.470525] do_idle+0x1dd/0x270 [450023.475147] cpu_startup_entry+0x20/0x30 [450023.480547] start_secondary+0x167/0x1c0 [450023.485934] secondary_startup_64+0xa4/0xb0 [450023.491620] Modules linked in: vhost_net vhost tap cpuid xt_state br_netfilter xt_physdev ip_set xt_CHECKSUM x
[Kernel-packages] [Bug 1885696] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1885696/+attachment/5388468/+files/WifiSyslog.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1885696 Title: Kernel panic linux-image-5.4.0-39-generic with cachefiles Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 20.04 server with latest kernel 5.4.0-39-generic panics under load when cachefilesd is used. This bug is known and fixed in upstream kernel 5.4.44 https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.4.44 cachefiles: Fix race between read_waiter and read_copier involving op->to_do [ Upstream commit 7bb0c5338436dae953622470d52689265867f032 ] https://github.com/torvalds/linux/commit/7bb0c5338436dae953622470d52689265867f032 #diff-14a48d14f7cd98c97d57211cfd758797 package: linux-image-5.4.0-39-generic, linux-image-generic Dmesg output: [450023.072377] FS-Cache: [450023.075150] FS-Cache: Assertion failed [450023.079496] FS-Cache: 4 == 5 is false [450023.083749] kernel BUG at fs/fscache/operation.c:69! [450023.089468] invalid opcode: [#1] SMP PTI [450023.094500] CPU: 13 PID: 0 Comm: swapper/13 Not tainted 5.4.0-37-generic #41-Ubuntu [450023.104057] Hardware name: Dell Inc. PowerEdge R430/0CN7X8, BIOS 2.11.0 12/23/2019 [450023.112660] RIP: 0010:fscache_enqueue_operation.cold+0xb7/0xb9 [fscache] [450023.120279] Code: a8 96 c0 e8 3f dc 1a e1 48 c7 c7 14 a8 96 c0 e8 33 dc 1a e1 41 8b 74 24 40 ba 05 00 00 00 48 c7 c7 28 98 96 c0 e8 1d dc 1a e1 <0f> 0b 48 c7 c7 06 a8 96 c0 e8 0f dc 1a e1 48 c7 c7 14 a8 96 c0 e8 [450023.141515] RSP: 0018:baca8cb88b98 EFLAGS: 00010046 [450023.147490] RAX: 0019 RBX: 98535b7f6540 RCX: 0006 [450023.156712] RDX: RSI: 0092 RDI: 9872bf3978c0 [450023.165774] RBP: baca8cb88bb0 R08: 337d R09: baca8f984020 [450023.175116] R10: 9852b7ebc2a0 R11: 0001 R12: 9872b870f740 [450023.184384] R13: 9838bd287580 R14: R15: baca8cb88c48 [450023.193659] FS: () GS:9872bf38() knlGS: [450023.204016] CS: 0010 DS: ES: CR0: 80050033 [450023.211346] CR2: 55eb5afaf2d8 CR3: 00359180a004 CR4: 003626e0 [450023.220602] DR0: DR1: DR2: [450023.229668] DR3: DR6: fffe0ff0 DR7: 0400 [450023.238621] Call Trace: [450023.242266] [450023.245426] cachefiles_read_waiter+0xe5/0x100 [cachefiles] [450023.252592] __wake_up_common+0x7e/0x140 [450023.257909] __wake_up_locked_key_bookmark+0x1b/0x20 [450023.264404] wake_up_page_bit+0xa7/0x100 [450023.269733] unlock_page+0x25/0x30 [450023.274491] __read_end_io+0xb6/0x110 [450023.279530] mpage_end_io+0x2f/0x40 [450023.284389] bio_endio+0xfb/0x160 [450023.289052] dec_pending+0x11c/0x210 [450023.294006] clone_endio+0x77/0x170 [450023.298874] bio_endio+0xfb/0x160 [450023.303540] blk_update_request+0x18a/0x2e0 [450023.309201] scsi_end_request+0x30/0x160 [450023.314571] scsi_io_completion+0x7c/0x540 [450023.320129] ? __update_load_avg_cfs_rq+0x212/0x2f0 [450023.326580] scsi_finish_command+0xe7/0x120 [450023.332259] scsi_softirq_done+0x14a/0x170 [450023.337840] blk_done_softirq+0x92/0xc0 [450023.343141] __do_softirq+0xe1/0x2d6 [450023.348145] irq_exit+0xae/0xb0 [450023.352670] smp_call_function_single_interrupt+0x48/0xd0 [450023.359735] call_function_single_interrupt+0xf/0x20 [450023.366323] [450023.369712] RIP: 0010:cpuidle_enter_state+0xc5/0x450 [450023.376326] Code: ff e8 5f 0c 81 ff 80 7d c7 00 74 17 9c 58 0f 1f 44 00 00 f6 c4 02 0f 85 65 03 00 00 31 ff e8 72 6e 87 ff fb 66 0f 1f 44 00 00 <45> 85 ed 0f 88 8f 02 00 00 49 63 cd 4c 8b 7d d0 4c 2b 7d c8 48 8d [450023.399419] RSP: 0018:baca8017be38 EFLAGS: 0246 ORIG_RAX: ff04 [450023.409020] RAX: 9872bf3aad00 RBX: a3159c00 RCX: 001f [450023.418148] RDX: RSI: 3a3fe5c1 RDI: [450023.427270] RBP: baca8017be78 R08: 0001994b295dad0d R09: 0001 [450023.436383] R10: 9872bf3a9a00 R11: 9872bf3a99e0 R12: daca7f583400 [450023.445496] R13: 0003 R14: 0003 R15: daca7f583400 [450023.454584] ? cpuidle_enter_state+0xa1/0x450 [450023.460544] cpuidle_enter+0x2e/0x40 [450023.465593] call_cpuidle+0x23/0x40 [450023.470525] do_idle+0x1dd/0x270 [450023.475147] cpu_startup_entry+0x20/0x30 [450023.480547] start_secondary+0x167/0x1c0 [450023.485934] secondary_startup_64+0xa4/0xb0 [450023.491620] Modules linked in: v
[Kernel-packages] [Bug 1885696] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1885696/+attachment/5388464/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1885696 Title: Kernel panic linux-image-5.4.0-39-generic with cachefiles Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 20.04 server with latest kernel 5.4.0-39-generic panics under load when cachefilesd is used. This bug is known and fixed in upstream kernel 5.4.44 https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.4.44 cachefiles: Fix race between read_waiter and read_copier involving op->to_do [ Upstream commit 7bb0c5338436dae953622470d52689265867f032 ] https://github.com/torvalds/linux/commit/7bb0c5338436dae953622470d52689265867f032 #diff-14a48d14f7cd98c97d57211cfd758797 package: linux-image-5.4.0-39-generic, linux-image-generic Dmesg output: [450023.072377] FS-Cache: [450023.075150] FS-Cache: Assertion failed [450023.079496] FS-Cache: 4 == 5 is false [450023.083749] kernel BUG at fs/fscache/operation.c:69! [450023.089468] invalid opcode: [#1] SMP PTI [450023.094500] CPU: 13 PID: 0 Comm: swapper/13 Not tainted 5.4.0-37-generic #41-Ubuntu [450023.104057] Hardware name: Dell Inc. PowerEdge R430/0CN7X8, BIOS 2.11.0 12/23/2019 [450023.112660] RIP: 0010:fscache_enqueue_operation.cold+0xb7/0xb9 [fscache] [450023.120279] Code: a8 96 c0 e8 3f dc 1a e1 48 c7 c7 14 a8 96 c0 e8 33 dc 1a e1 41 8b 74 24 40 ba 05 00 00 00 48 c7 c7 28 98 96 c0 e8 1d dc 1a e1 <0f> 0b 48 c7 c7 06 a8 96 c0 e8 0f dc 1a e1 48 c7 c7 14 a8 96 c0 e8 [450023.141515] RSP: 0018:baca8cb88b98 EFLAGS: 00010046 [450023.147490] RAX: 0019 RBX: 98535b7f6540 RCX: 0006 [450023.156712] RDX: RSI: 0092 RDI: 9872bf3978c0 [450023.165774] RBP: baca8cb88bb0 R08: 337d R09: baca8f984020 [450023.175116] R10: 9852b7ebc2a0 R11: 0001 R12: 9872b870f740 [450023.184384] R13: 9838bd287580 R14: R15: baca8cb88c48 [450023.193659] FS: () GS:9872bf38() knlGS: [450023.204016] CS: 0010 DS: ES: CR0: 80050033 [450023.211346] CR2: 55eb5afaf2d8 CR3: 00359180a004 CR4: 003626e0 [450023.220602] DR0: DR1: DR2: [450023.229668] DR3: DR6: fffe0ff0 DR7: 0400 [450023.238621] Call Trace: [450023.242266] [450023.245426] cachefiles_read_waiter+0xe5/0x100 [cachefiles] [450023.252592] __wake_up_common+0x7e/0x140 [450023.257909] __wake_up_locked_key_bookmark+0x1b/0x20 [450023.264404] wake_up_page_bit+0xa7/0x100 [450023.269733] unlock_page+0x25/0x30 [450023.274491] __read_end_io+0xb6/0x110 [450023.279530] mpage_end_io+0x2f/0x40 [450023.284389] bio_endio+0xfb/0x160 [450023.289052] dec_pending+0x11c/0x210 [450023.294006] clone_endio+0x77/0x170 [450023.298874] bio_endio+0xfb/0x160 [450023.303540] blk_update_request+0x18a/0x2e0 [450023.309201] scsi_end_request+0x30/0x160 [450023.314571] scsi_io_completion+0x7c/0x540 [450023.320129] ? __update_load_avg_cfs_rq+0x212/0x2f0 [450023.326580] scsi_finish_command+0xe7/0x120 [450023.332259] scsi_softirq_done+0x14a/0x170 [450023.337840] blk_done_softirq+0x92/0xc0 [450023.343141] __do_softirq+0xe1/0x2d6 [450023.348145] irq_exit+0xae/0xb0 [450023.352670] smp_call_function_single_interrupt+0x48/0xd0 [450023.359735] call_function_single_interrupt+0xf/0x20 [450023.366323] [450023.369712] RIP: 0010:cpuidle_enter_state+0xc5/0x450 [450023.376326] Code: ff e8 5f 0c 81 ff 80 7d c7 00 74 17 9c 58 0f 1f 44 00 00 f6 c4 02 0f 85 65 03 00 00 31 ff e8 72 6e 87 ff fb 66 0f 1f 44 00 00 <45> 85 ed 0f 88 8f 02 00 00 49 63 cd 4c 8b 7d d0 4c 2b 7d c8 48 8d [450023.399419] RSP: 0018:baca8017be38 EFLAGS: 0246 ORIG_RAX: ff04 [450023.409020] RAX: 9872bf3aad00 RBX: a3159c00 RCX: 001f [450023.418148] RDX: RSI: 3a3fe5c1 RDI: [450023.427270] RBP: baca8017be78 R08: 0001994b295dad0d R09: 0001 [450023.436383] R10: 9872bf3a9a00 R11: 9872bf3a99e0 R12: daca7f583400 [450023.445496] R13: 0003 R14: 0003 R15: daca7f583400 [450023.454584] ? cpuidle_enter_state+0xa1/0x450 [450023.460544] cpuidle_enter+0x2e/0x40 [450023.465593] call_cpuidle+0x23/0x40 [450023.470525] do_idle+0x1dd/0x270 [450023.475147] cpu_startup_entry+0x20/0x30 [450023.480547] start_secondary+0x167/0x1c0 [450023.485934] secondary_startup_64+0xa4/0xb0 [450023.491620] Modules linked in: vhost_net vhost tap cpuid xt_state br_netfilter xt_phy
[Kernel-packages] [Bug 1885730] Re: Bring back ondemand.service or switch kernel default governor for pstate - pstate now defaults to performance governor
Someone probably needs to look at non-pstate systems as I have no idea about them. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1885730 Title: Bring back ondemand.service or switch kernel default governor for pstate - pstate now defaults to performance governor Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: New Bug description: In a recent merge from Debian we lost ondemand.service, meaning all CPUs now run in Turbo all the time when idle, which is clearly suboptimal. The discussion in bug 1806012 seems misleading, focusing on p-state vs other drivers, when in fact, the script actually set the default governor for the pstate driver on platforms that use pstate. Everything below only looks at systems that use pstate. pstate has two governors: performance and powerstate. performance runs CPU at maximum frequency constantly, and powersave can be configured using various energy profiles energy profiles: - performance - balanced performance - balanced power - power It defaults to balanced performance, I think, but I'm not sure. Whether performance governor is faster than powersave governor is not even clear. https://www.phoronix.com/scan.php?page=article&item=linux50-pstate- cpufreq&num=5 benchmarked them, but did not benchmark the individual energy profiles. For a desktop/laptop, the expected behavior is the powersave governor with balanced_performance on AC and balanced_power on battery. I don't know about servers or VMs, but the benchmark series seems to indicate it does not really matter much performance wise. I think most other distributions configure their kernels to use the powersave governor by default, whereas we configure it to use the performance governor and then switch it later in the boot to get the maximum performance during bootup. It's not clear to me that's actually useful. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1885730/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1885730] Re: Bring back ondemand.service or switch kernel default governor for pstate - pstate now defaults to performance governor
Tagging rls-gg-incoming so it's reviewed, that has a performance impact on desktop and ideally should have been discussed before landing rather than afterfact ** Tags added: rls-gg-incoming -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1885730 Title: Bring back ondemand.service or switch kernel default governor for pstate - pstate now defaults to performance governor Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: New Bug description: In a recent merge from Debian we lost ondemand.service, meaning all CPUs now run in Turbo all the time when idle, which is clearly suboptimal. The discussion in bug 1806012 seems misleading, focusing on p-state vs other drivers, when in fact, the script actually set the default governor for the pstate driver on platforms that use pstate. Everything below only looks at systems that use pstate. pstate has two governors: performance and powerstate. performance runs CPU at maximum frequency constantly, and powersave can be configured using various energy profiles energy profiles: - performance - balanced performance - balanced power - power It defaults to balanced performance, I think, but I'm not sure. Whether performance governor is faster than powersave governor is not even clear. https://www.phoronix.com/scan.php?page=article&item=linux50-pstate- cpufreq&num=5 benchmarked them, but did not benchmark the individual energy profiles. For a desktop/laptop, the expected behavior is the powersave governor with balanced_performance on AC and balanced_power on battery. I don't know about servers or VMs, but the benchmark series seems to indicate it does not really matter much performance wise. I think most other distributions configure their kernels to use the powersave governor by default, whereas we configure it to use the performance governor and then switch it later in the boot to get the maximum performance during bootup. It's not clear to me that's actually useful. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1885730/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1885696] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1885696/+attachment/5388460/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1885696 Title: Kernel panic linux-image-5.4.0-39-generic with cachefiles Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 20.04 server with latest kernel 5.4.0-39-generic panics under load when cachefilesd is used. This bug is known and fixed in upstream kernel 5.4.44 https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.4.44 cachefiles: Fix race between read_waiter and read_copier involving op->to_do [ Upstream commit 7bb0c5338436dae953622470d52689265867f032 ] https://github.com/torvalds/linux/commit/7bb0c5338436dae953622470d52689265867f032 #diff-14a48d14f7cd98c97d57211cfd758797 package: linux-image-5.4.0-39-generic, linux-image-generic Dmesg output: [450023.072377] FS-Cache: [450023.075150] FS-Cache: Assertion failed [450023.079496] FS-Cache: 4 == 5 is false [450023.083749] kernel BUG at fs/fscache/operation.c:69! [450023.089468] invalid opcode: [#1] SMP PTI [450023.094500] CPU: 13 PID: 0 Comm: swapper/13 Not tainted 5.4.0-37-generic #41-Ubuntu [450023.104057] Hardware name: Dell Inc. PowerEdge R430/0CN7X8, BIOS 2.11.0 12/23/2019 [450023.112660] RIP: 0010:fscache_enqueue_operation.cold+0xb7/0xb9 [fscache] [450023.120279] Code: a8 96 c0 e8 3f dc 1a e1 48 c7 c7 14 a8 96 c0 e8 33 dc 1a e1 41 8b 74 24 40 ba 05 00 00 00 48 c7 c7 28 98 96 c0 e8 1d dc 1a e1 <0f> 0b 48 c7 c7 06 a8 96 c0 e8 0f dc 1a e1 48 c7 c7 14 a8 96 c0 e8 [450023.141515] RSP: 0018:baca8cb88b98 EFLAGS: 00010046 [450023.147490] RAX: 0019 RBX: 98535b7f6540 RCX: 0006 [450023.156712] RDX: RSI: 0092 RDI: 9872bf3978c0 [450023.165774] RBP: baca8cb88bb0 R08: 337d R09: baca8f984020 [450023.175116] R10: 9852b7ebc2a0 R11: 0001 R12: 9872b870f740 [450023.184384] R13: 9838bd287580 R14: R15: baca8cb88c48 [450023.193659] FS: () GS:9872bf38() knlGS: [450023.204016] CS: 0010 DS: ES: CR0: 80050033 [450023.211346] CR2: 55eb5afaf2d8 CR3: 00359180a004 CR4: 003626e0 [450023.220602] DR0: DR1: DR2: [450023.229668] DR3: DR6: fffe0ff0 DR7: 0400 [450023.238621] Call Trace: [450023.242266] [450023.245426] cachefiles_read_waiter+0xe5/0x100 [cachefiles] [450023.252592] __wake_up_common+0x7e/0x140 [450023.257909] __wake_up_locked_key_bookmark+0x1b/0x20 [450023.264404] wake_up_page_bit+0xa7/0x100 [450023.269733] unlock_page+0x25/0x30 [450023.274491] __read_end_io+0xb6/0x110 [450023.279530] mpage_end_io+0x2f/0x40 [450023.284389] bio_endio+0xfb/0x160 [450023.289052] dec_pending+0x11c/0x210 [450023.294006] clone_endio+0x77/0x170 [450023.298874] bio_endio+0xfb/0x160 [450023.303540] blk_update_request+0x18a/0x2e0 [450023.309201] scsi_end_request+0x30/0x160 [450023.314571] scsi_io_completion+0x7c/0x540 [450023.320129] ? __update_load_avg_cfs_rq+0x212/0x2f0 [450023.326580] scsi_finish_command+0xe7/0x120 [450023.332259] scsi_softirq_done+0x14a/0x170 [450023.337840] blk_done_softirq+0x92/0xc0 [450023.343141] __do_softirq+0xe1/0x2d6 [450023.348145] irq_exit+0xae/0xb0 [450023.352670] smp_call_function_single_interrupt+0x48/0xd0 [450023.359735] call_function_single_interrupt+0xf/0x20 [450023.366323] [450023.369712] RIP: 0010:cpuidle_enter_state+0xc5/0x450 [450023.376326] Code: ff e8 5f 0c 81 ff 80 7d c7 00 74 17 9c 58 0f 1f 44 00 00 f6 c4 02 0f 85 65 03 00 00 31 ff e8 72 6e 87 ff fb 66 0f 1f 44 00 00 <45> 85 ed 0f 88 8f 02 00 00 49 63 cd 4c 8b 7d d0 4c 2b 7d c8 48 8d [450023.399419] RSP: 0018:baca8017be38 EFLAGS: 0246 ORIG_RAX: ff04 [450023.409020] RAX: 9872bf3aad00 RBX: a3159c00 RCX: 001f [450023.418148] RDX: RSI: 3a3fe5c1 RDI: [450023.427270] RBP: baca8017be78 R08: 0001994b295dad0d R09: 0001 [450023.436383] R10: 9872bf3a9a00 R11: 9872bf3a99e0 R12: daca7f583400 [450023.445496] R13: 0003 R14: 0003 R15: daca7f583400 [450023.454584] ? cpuidle_enter_state+0xa1/0x450 [450023.460544] cpuidle_enter+0x2e/0x40 [450023.465593] call_cpuidle+0x23/0x40 [450023.470525] do_idle+0x1dd/0x270 [450023.475147] cpu_startup_entry+0x20/0x30 [450023.480547] start_secondary+0x167/0x1c0 [450023.485934] secondary_startup_64+0xa4/0xb0 [450023.491620] Modules linked in: vhost_net vhost tap cpuid xt_state br_netfilter xt_physdev ip_set
[Kernel-packages] [Bug 1885696] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1885696/+attachment/5388466/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1885696 Title: Kernel panic linux-image-5.4.0-39-generic with cachefiles Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 20.04 server with latest kernel 5.4.0-39-generic panics under load when cachefilesd is used. This bug is known and fixed in upstream kernel 5.4.44 https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.4.44 cachefiles: Fix race between read_waiter and read_copier involving op->to_do [ Upstream commit 7bb0c5338436dae953622470d52689265867f032 ] https://github.com/torvalds/linux/commit/7bb0c5338436dae953622470d52689265867f032 #diff-14a48d14f7cd98c97d57211cfd758797 package: linux-image-5.4.0-39-generic, linux-image-generic Dmesg output: [450023.072377] FS-Cache: [450023.075150] FS-Cache: Assertion failed [450023.079496] FS-Cache: 4 == 5 is false [450023.083749] kernel BUG at fs/fscache/operation.c:69! [450023.089468] invalid opcode: [#1] SMP PTI [450023.094500] CPU: 13 PID: 0 Comm: swapper/13 Not tainted 5.4.0-37-generic #41-Ubuntu [450023.104057] Hardware name: Dell Inc. PowerEdge R430/0CN7X8, BIOS 2.11.0 12/23/2019 [450023.112660] RIP: 0010:fscache_enqueue_operation.cold+0xb7/0xb9 [fscache] [450023.120279] Code: a8 96 c0 e8 3f dc 1a e1 48 c7 c7 14 a8 96 c0 e8 33 dc 1a e1 41 8b 74 24 40 ba 05 00 00 00 48 c7 c7 28 98 96 c0 e8 1d dc 1a e1 <0f> 0b 48 c7 c7 06 a8 96 c0 e8 0f dc 1a e1 48 c7 c7 14 a8 96 c0 e8 [450023.141515] RSP: 0018:baca8cb88b98 EFLAGS: 00010046 [450023.147490] RAX: 0019 RBX: 98535b7f6540 RCX: 0006 [450023.156712] RDX: RSI: 0092 RDI: 9872bf3978c0 [450023.165774] RBP: baca8cb88bb0 R08: 337d R09: baca8f984020 [450023.175116] R10: 9852b7ebc2a0 R11: 0001 R12: 9872b870f740 [450023.184384] R13: 9838bd287580 R14: R15: baca8cb88c48 [450023.193659] FS: () GS:9872bf38() knlGS: [450023.204016] CS: 0010 DS: ES: CR0: 80050033 [450023.211346] CR2: 55eb5afaf2d8 CR3: 00359180a004 CR4: 003626e0 [450023.220602] DR0: DR1: DR2: [450023.229668] DR3: DR6: fffe0ff0 DR7: 0400 [450023.238621] Call Trace: [450023.242266] [450023.245426] cachefiles_read_waiter+0xe5/0x100 [cachefiles] [450023.252592] __wake_up_common+0x7e/0x140 [450023.257909] __wake_up_locked_key_bookmark+0x1b/0x20 [450023.264404] wake_up_page_bit+0xa7/0x100 [450023.269733] unlock_page+0x25/0x30 [450023.274491] __read_end_io+0xb6/0x110 [450023.279530] mpage_end_io+0x2f/0x40 [450023.284389] bio_endio+0xfb/0x160 [450023.289052] dec_pending+0x11c/0x210 [450023.294006] clone_endio+0x77/0x170 [450023.298874] bio_endio+0xfb/0x160 [450023.303540] blk_update_request+0x18a/0x2e0 [450023.309201] scsi_end_request+0x30/0x160 [450023.314571] scsi_io_completion+0x7c/0x540 [450023.320129] ? __update_load_avg_cfs_rq+0x212/0x2f0 [450023.326580] scsi_finish_command+0xe7/0x120 [450023.332259] scsi_softirq_done+0x14a/0x170 [450023.337840] blk_done_softirq+0x92/0xc0 [450023.343141] __do_softirq+0xe1/0x2d6 [450023.348145] irq_exit+0xae/0xb0 [450023.352670] smp_call_function_single_interrupt+0x48/0xd0 [450023.359735] call_function_single_interrupt+0xf/0x20 [450023.366323] [450023.369712] RIP: 0010:cpuidle_enter_state+0xc5/0x450 [450023.376326] Code: ff e8 5f 0c 81 ff 80 7d c7 00 74 17 9c 58 0f 1f 44 00 00 f6 c4 02 0f 85 65 03 00 00 31 ff e8 72 6e 87 ff fb 66 0f 1f 44 00 00 <45> 85 ed 0f 88 8f 02 00 00 49 63 cd 4c 8b 7d d0 4c 2b 7d c8 48 8d [450023.399419] RSP: 0018:baca8017be38 EFLAGS: 0246 ORIG_RAX: ff04 [450023.409020] RAX: 9872bf3aad00 RBX: a3159c00 RCX: 001f [450023.418148] RDX: RSI: 3a3fe5c1 RDI: [450023.427270] RBP: baca8017be78 R08: 0001994b295dad0d R09: 0001 [450023.436383] R10: 9872bf3a9a00 R11: 9872bf3a99e0 R12: daca7f583400 [450023.445496] R13: 0003 R14: 0003 R15: daca7f583400 [450023.454584] ? cpuidle_enter_state+0xa1/0x450 [450023.460544] cpuidle_enter+0x2e/0x40 [450023.465593] call_cpuidle+0x23/0x40 [450023.470525] do_idle+0x1dd/0x270 [450023.475147] cpu_startup_entry+0x20/0x30 [450023.480547] start_secondary+0x167/0x1c0 [450023.485934] secondary_startup_64+0xa4/0xb0 [450023.491620] Modules linked in: vhost_net vhost tap cpuid xt_state br_netfilter xt_physdev ip_set xt
[Kernel-packages] [Bug 1885696] Re: Kernel panic linux-image-5.4.0-39-generic with cachefiles
apport information ** Tags added: apport-collected uec-images ** Description changed: Ubuntu 20.04 server with latest kernel 5.4.0-39-generic panics under load when cachefilesd is used. This bug is known and fixed in upstream kernel 5.4.44 https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.4.44 cachefiles: Fix race between read_waiter and read_copier involving op->to_do [ Upstream commit 7bb0c5338436dae953622470d52689265867f032 ] https://github.com/torvalds/linux/commit/7bb0c5338436dae953622470d52689265867f032 #diff-14a48d14f7cd98c97d57211cfd758797 package: linux-image-5.4.0-39-generic, linux-image-generic Dmesg output: [450023.072377] FS-Cache: [450023.075150] FS-Cache: Assertion failed [450023.079496] FS-Cache: 4 == 5 is false [450023.083749] kernel BUG at fs/fscache/operation.c:69! [450023.089468] invalid opcode: [#1] SMP PTI [450023.094500] CPU: 13 PID: 0 Comm: swapper/13 Not tainted 5.4.0-37-generic #41-Ubuntu [450023.104057] Hardware name: Dell Inc. PowerEdge R430/0CN7X8, BIOS 2.11.0 12/23/2019 [450023.112660] RIP: 0010:fscache_enqueue_operation.cold+0xb7/0xb9 [fscache] [450023.120279] Code: a8 96 c0 e8 3f dc 1a e1 48 c7 c7 14 a8 96 c0 e8 33 dc 1a e1 41 8b 74 24 40 ba 05 00 00 00 48 c7 c7 28 98 96 c0 e8 1d dc 1a e1 <0f> 0b 48 c7 c7 06 a8 96 c0 e8 0f dc 1a e1 48 c7 c7 14 a8 96 c0 e8 [450023.141515] RSP: 0018:baca8cb88b98 EFLAGS: 00010046 [450023.147490] RAX: 0019 RBX: 98535b7f6540 RCX: 0006 [450023.156712] RDX: RSI: 0092 RDI: 9872bf3978c0 [450023.165774] RBP: baca8cb88bb0 R08: 337d R09: baca8f984020 [450023.175116] R10: 9852b7ebc2a0 R11: 0001 R12: 9872b870f740 [450023.184384] R13: 9838bd287580 R14: R15: baca8cb88c48 [450023.193659] FS: () GS:9872bf38() knlGS: [450023.204016] CS: 0010 DS: ES: CR0: 80050033 [450023.211346] CR2: 55eb5afaf2d8 CR3: 00359180a004 CR4: 003626e0 [450023.220602] DR0: DR1: DR2: [450023.229668] DR3: DR6: fffe0ff0 DR7: 0400 [450023.238621] Call Trace: [450023.242266] [450023.245426] cachefiles_read_waiter+0xe5/0x100 [cachefiles] [450023.252592] __wake_up_common+0x7e/0x140 [450023.257909] __wake_up_locked_key_bookmark+0x1b/0x20 [450023.264404] wake_up_page_bit+0xa7/0x100 [450023.269733] unlock_page+0x25/0x30 [450023.274491] __read_end_io+0xb6/0x110 [450023.279530] mpage_end_io+0x2f/0x40 [450023.284389] bio_endio+0xfb/0x160 [450023.289052] dec_pending+0x11c/0x210 [450023.294006] clone_endio+0x77/0x170 [450023.298874] bio_endio+0xfb/0x160 [450023.303540] blk_update_request+0x18a/0x2e0 [450023.309201] scsi_end_request+0x30/0x160 [450023.314571] scsi_io_completion+0x7c/0x540 [450023.320129] ? __update_load_avg_cfs_rq+0x212/0x2f0 [450023.326580] scsi_finish_command+0xe7/0x120 [450023.332259] scsi_softirq_done+0x14a/0x170 [450023.337840] blk_done_softirq+0x92/0xc0 [450023.343141] __do_softirq+0xe1/0x2d6 [450023.348145] irq_exit+0xae/0xb0 [450023.352670] smp_call_function_single_interrupt+0x48/0xd0 [450023.359735] call_function_single_interrupt+0xf/0x20 [450023.366323] [450023.369712] RIP: 0010:cpuidle_enter_state+0xc5/0x450 [450023.376326] Code: ff e8 5f 0c 81 ff 80 7d c7 00 74 17 9c 58 0f 1f 44 00 00 f6 c4 02 0f 85 65 03 00 00 31 ff e8 72 6e 87 ff fb 66 0f 1f 44 00 00 <45> 85 ed 0f 88 8f 02 00 00 49 63 cd 4c 8b 7d d0 4c 2b 7d c8 48 8d [450023.399419] RSP: 0018:baca8017be38 EFLAGS: 0246 ORIG_RAX: ff04 [450023.409020] RAX: 9872bf3aad00 RBX: a3159c00 RCX: 001f [450023.418148] RDX: RSI: 3a3fe5c1 RDI: [450023.427270] RBP: baca8017be78 R08: 0001994b295dad0d R09: 0001 [450023.436383] R10: 9872bf3a9a00 R11: 9872bf3a99e0 R12: daca7f583400 [450023.445496] R13: 0003 R14: 0003 R15: daca7f583400 [450023.454584] ? cpuidle_enter_state+0xa1/0x450 [450023.460544] cpuidle_enter+0x2e/0x40 [450023.465593] call_cpuidle+0x23/0x40 [450023.470525] do_idle+0x1dd/0x270 [450023.475147] cpu_startup_entry+0x20/0x30 [450023.480547] start_secondary+0x167/0x1c0 [450023.485934] secondary_startup_64+0xa4/0xb0 [450023.491620] Modules linked in: vhost_net vhost tap cpuid xt_state br_netfilter xt_physdev ip_set xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat iptable_mangle iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nf_tables nfnetlink ip6table_filter ip6_tables iptable_filter bpfilter bridge cachefiles rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace fscache 8021q garp m
[Kernel-packages] [Bug 1885730] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1885730 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1885730 Title: Bring back ondemand.service or switch kernel default governor for pstate - pstate now defaults to performance governor Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: New Bug description: In a recent merge from Debian we lost ondemand.service, meaning all CPUs now run in Turbo all the time when idle, which is clearly suboptimal. The discussion in bug 1806012 seems misleading, focusing on p-state vs other drivers, when in fact, the script actually set the default governor for the pstate driver on platforms that use pstate. Everything below only looks at systems that use pstate. pstate has two governors: performance and powerstate. performance runs CPU at maximum frequency constantly, and powersave can be configured using various energy profiles energy profiles: - performance - balanced performance - balanced power - power It defaults to balanced performance, I think, but I'm not sure. Whether performance governor is faster than powersave governor is not even clear. https://www.phoronix.com/scan.php?page=article&item=linux50-pstate- cpufreq&num=5 benchmarked them, but did not benchmark the individual energy profiles. For a desktop/laptop, the expected behavior is the powersave governor with balanced_performance on AC and balanced_power on battery. I don't know about servers or VMs, but the benchmark series seems to indicate it does not really matter much performance wise. I think most other distributions configure their kernels to use the powersave governor by default, whereas we configure it to use the performance governor and then switch it later in the boot to get the maximum performance during bootup. It's not clear to me that's actually useful. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1885730/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1885730] Re: Bring back ondemand.service or switch kernel default governor for pstate - pstate now defaults to performance governor
The commit message removing ondemand.service has several bug references, too: https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=65f46a7d14b335e5743350dbbc5b5ef1e72826f7 remove Ubuntu-specific ondemand.service New processors handle scaling/throttling in internal firmware (e.g. intel_pstate), and do not require OS config. Additionally, nobody else does this, not even Debian. And finally, this has caused problems for years, e.g.: https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/1497375 https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1503773 https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/1480320 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1579278 https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1806012 https://bugs.launchpad.net/charm-sysconfig/+bug/1873028 IMO the kernel is a better place for setting the default governor properly and can even set different governors in cloud-specific kernels. If the decision is to control the governor in user space in Ubuntu I'd prefer a solution shipped in an other package because systemd does too many things already. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1885730 Title: Bring back ondemand.service or switch kernel default governor for pstate - pstate now defaults to performance governor Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: New Bug description: In a recent merge from Debian we lost ondemand.service, meaning all CPUs now run in Turbo all the time when idle, which is clearly suboptimal. The discussion in bug 1806012 seems misleading, focusing on p-state vs other drivers, when in fact, the script actually set the default governor for the pstate driver on platforms that use pstate. Everything below only looks at systems that use pstate. pstate has two governors: performance and powerstate. performance runs CPU at maximum frequency constantly, and powersave can be configured using various energy profiles energy profiles: - performance - balanced performance - balanced power - power It defaults to balanced performance, I think, but I'm not sure. Whether performance governor is faster than powersave governor is not even clear. https://www.phoronix.com/scan.php?page=article&item=linux50-pstate- cpufreq&num=5 benchmarked them, but did not benchmark the individual energy profiles. For a desktop/laptop, the expected behavior is the powersave governor with balanced_performance on AC and balanced_power on battery. I don't know about servers or VMs, but the benchmark series seems to indicate it does not really matter much performance wise. I think most other distributions configure their kernels to use the powersave governor by default, whereas we configure it to use the performance governor and then switch it later in the boot to get the maximum performance during bootup. It's not clear to me that's actually useful. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1885730/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874567] Re: [nvidia] Rotating secondary monitor to portrait fails, results in landscape
** Also affects: gnome-control-center (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: mutter (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-340 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-435 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-440 (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: mutter (Ubuntu Focal) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Changed in: nvidia-graphics-drivers-435 (Ubuntu Focal) Status: New => Won't Fix ** Changed in: nvidia-graphics-drivers-440 (Ubuntu Focal) Status: New => Won't Fix ** Tags removed: rls-ff-incoming -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-435 in Ubuntu. https://bugs.launchpad.net/bugs/1874567 Title: [nvidia] Rotating secondary monitor to portrait fails, results in landscape Status in gnome-control-center package in Ubuntu: Won't Fix Status in mutter package in Ubuntu: In Progress Status in nvidia-graphics-drivers-340 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-435 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-440 package in Ubuntu: Won't Fix Status in gnome-control-center source package in Focal: New Status in mutter source package in Focal: New Status in nvidia-graphics-drivers-340 source package in Focal: New Status in nvidia-graphics-drivers-435 source package in Focal: Won't Fix Status in nvidia-graphics-drivers-440 source package in Focal: Won't Fix Bug description: I have two monitors, with the secondary one rotated in a portrait orientation. Using the nvidia 440 drivers, the orientation is not applied when configuring in gnome settings (the displays go blank for a second, and then reappear in landscape orientation). Using nvidia settings, I can set the monitor rotation and offset correctly, however these settings do not persist on next boot (even when selecting to save to xorg.conf). When using the nouveau drivers, the orientation is applied correctly in gnome settings, and is persisted. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-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.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: GNOME Date: Fri Apr 24 08:30:41 2020 DistUpgraded: 2020-04-20 18:27:13,972 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.64, 5.4.0-26-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GK106 [GeForce GTX 660] [10de:11c0] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] GK106 [GeForce GTX 660] [1462:2871] InstallationDate: Installed on 2018-05-01 (723 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Shuttle Inc. SZ77 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=UUID=d2c17cee-7c37-429f-9cbb-9484a159f182 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-04-20 (3 days ago) dmi.bios.date: 10/13/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.13 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: FZ77 dmi.board.vendor: Shuttle Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.13:bd10/13/2014:svnShuttleInc.:pnSZ77:pvr1.0:rvnShuttleInc.:rnFZ77:rvr1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: SZ77 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Shuttle Inc. version.compiz: compiz N/A version.libdrm2: l
[Kernel-packages] [Bug 1885730] Re: Bring back ondemand.service or switch kernel default governor for pstate - pstate now defaults to performance governor
@balint Kernel has no facility to startup in one mode, and later transition to another. I think maybe we should measure the difference between "performance, then on demand" vs "balanced performance". If the difference is not significant, maybe we can simply change the kernel default to "balanced performance" -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1885730 Title: Bring back ondemand.service or switch kernel default governor for pstate - pstate now defaults to performance governor Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: New Bug description: In a recent merge from Debian we lost ondemand.service, meaning all CPUs now run in Turbo all the time when idle, which is clearly suboptimal. The discussion in bug 1806012 seems misleading, focusing on p-state vs other drivers, when in fact, the script actually set the default governor for the pstate driver on platforms that use pstate. Everything below only looks at systems that use pstate. pstate has two governors: performance and powerstate. performance runs CPU at maximum frequency constantly, and powersave can be configured using various energy profiles energy profiles: - performance - balanced performance - balanced power - power It defaults to balanced performance, I think, but I'm not sure. Whether performance governor is faster than powersave governor is not even clear. https://www.phoronix.com/scan.php?page=article&item=linux50-pstate- cpufreq&num=5 benchmarked them, but did not benchmark the individual energy profiles. For a desktop/laptop, the expected behavior is the powersave governor with balanced_performance on AC and balanced_power on battery. I don't know about servers or VMs, but the benchmark series seems to indicate it does not really matter much performance wise. I think most other distributions configure their kernels to use the powersave governor by default, whereas we configure it to use the performance governor and then switch it later in the boot to get the maximum performance during bootup. It's not clear to me that's actually useful. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1885730/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1883229] Re: Ubuntu server installation on S3260M4 server gets failed
** Tags added: rls-ff-incoming -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1883229 Title: Ubuntu server installation on S3260M4 server gets failed Status in grub2 package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Details/Description: - Ubuntu 20.04 fails on S3260 M4 with Gonga Beach in UEFI mode. Os get installed. However, upon rebooting OS never came up. Grub loads only to get hanged in a black screen. No options work later. Unable to collect Installer logs. How to reproduce: -- 1.Update S3260M4 M4 to bios build ucs-s3260-huu-4.1.2S36 2.Deploy Ubuntu 20.04 on S3260 M4. 3.Observe the installation proceeding and after installation OS reboots and loads the kernel and gets hanged on the black screen 4. The same OS works in Legacy mode in C3000 RAID controller card of LSI. Expected behavior: - Ubuntu 20.04 should get deployed in GB/DD-Raid in UEFI mode Screenshots -- Screenshot attached. Please let us know how to collect logs on this scenario Note :With MASS deployment we are able to deploy OS successfully with USFI method. Attached the logs of MASS server in this bug. --- ProblemType: Bug AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Jun 17 09:07 seq crw-rw+ 1 root audio 116, 33 Jun 17 09:07 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-06-16 (0 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 003: ID 0624:0402 Avocent Corp. Cisco Virtual Keyboard and Mouse Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Cisco Systems Inc UCSC-C3K-M4SRB Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=UUID=1db32ed4-cafc-4d2c-b57c-d0b6a3943066 ro ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 RelatedPackageVersions: linux-restricted-modules-5.4.0-26-generic N/A linux-backports-modules-5.4.0-26-generic N/A linux-firmware1.187 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.4.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: WifiSyslog: _MarkForUpload: True dmi.bios.date: 03/06/2020 dmi.bios.vendor: Cisco Systems, Inc. dmi.bios.version: C3X60M4.4.1.1.13.0306200116 dmi.board.name: UCSC-C3K-M4SRB dmi.board.vendor: Cisco Systems Inc dmi.board.version: 73-17622-03 dmi.chassis.type: 23 dmi.chassis.vendor: Cisco Systems Inc dmi.chassis.version: 68-5829-03 dmi.modalias: dmi:bvnCiscoSystems,Inc.:bvrC3X60M4.4.1.1.13.0306200116:bd03/06/2020:svnCiscoSystemsInc:pnUCSC-C3K-M4SRB:pvrA0:rvnCiscoSystemsInc:rnUCSC-C3K-M4SRB:rvr73-17622-03:cvnCiscoSystemsInc:ct23:cvr68-5829-03: dmi.product.name: UCSC-C3K-M4SRB dmi.product.version: A0 dmi.sys.vendor: Cisco Systems Inc --- ProblemType: Bug AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Jun 17 09:07 seq crw-rw+ 1 root audio 116, 33 Jun 17 09:07 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-06-16 (0 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 003: ID 0624:0402 Avocent Corp. Cisco Virtual Keyboard and Mouse Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub M
Re: [Kernel-packages] [Bug 1861941] Re: bcache by-uuid links disappear after mounting bcache0
On Tue, Jun 30, 2020 at 6:35 AM Balint Reczey <1861...@bugs.launchpad.net> wrote: > @raharper I've forwarded the systemd fix for you with minimal tidying of > the commit message https://github.com/systemd/systemd/pull/16317 Thanks! > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1861941 > > Title: > bcache by-uuid links disappear after mounting bcache0 > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/bcache-tools/+bug/1861941/+subscriptions > -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1861941 Title: bcache by-uuid links disappear after mounting bcache0 Status in bcache-tools package in Ubuntu: Triaged Status in linux package in Ubuntu: Incomplete Status in linux-signed package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Fix Released Status in bcache-tools source package in Bionic: New Status in linux source package in Bionic: New Status in linux-signed source package in Bionic: New Status in systemd source package in Bionic: New Status in bcache-tools source package in Focal: Confirmed Status in linux source package in Focal: Invalid Status in linux-signed source package in Focal: Confirmed Status in systemd source package in Focal: Confirmed Status in bcache-tools source package in Groovy: Triaged Status in linux source package in Groovy: Incomplete Status in linux-signed source package in Groovy: Confirmed Status in systemd source package in Groovy: Fix Released Bug description: 1. root@ubuntu:~# lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 2. root@ubuntu:~# lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 root@ubuntu:~# apt-cache policy linux-image-virtual linux-image-virtual: Installed: 5.4.0.12.15 Candidate: 5.4.0.12.15 Version table: *** 5.4.0.12.15 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status root@ubuntu:~# apt-cache policy linux-image-5.4.0-12-generic linux-image-5.4.0-12-generic: Installed: 5.4.0-12.15 Candidate: 5.4.0-12.15 Version table: *** 5.4.0-12.15 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status 3. mount /dev/bcache0 && ls -al /dev/bcache/by-uuid/ + ls -al /dev/bcache/by-uuid/ total 0 drwxr-xr-x 2 root root 60 Feb 4 23:31 . drwxr-xr-x 3 root root 60 Feb 4 23:31 .. lrwxrwxrwx 1 root root 13 Feb 4 23:31 abdfd1f6-44ce-4266-91db-24667b9ae51a -> ../../bcache0 4. root@ubuntu:~# ls -al /dev/bcache/by-uuid ls: cannot access '/dev/bcache/by-uuid': No such file or directory ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-12-generic 5.4.0-12.15 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 Date: Tue Feb 4 23:31:52 2020 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-5.4 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcache-tools/+bug/1861941/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1885730] Re: Bring back ondemand.service or switch kernel default governor for pstate - pstate now defaults to performance governor
@rbalint As said before the kernel messages and bugs are irrelevant and wrong. They pretend like intel_pstate is different, when in fact it's this script that is configuring it here. And yes, it needs OS config. Nor do other distros not do this, but we do it differently. We set the CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE=y option, and then transition to that at the end of the boot. Other distributions do not set CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE and hence the kernel has powersave as the default. By removing this script, we are diverging from other distros, not becoming closer to them - for pstates, anyway. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1885730 Title: Bring back ondemand.service or switch kernel default governor for pstate - pstate now defaults to performance governor Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: New Bug description: In a recent merge from Debian we lost ondemand.service, meaning all CPUs now run in Turbo all the time when idle, which is clearly suboptimal. The discussion in bug 1806012 seems misleading, focusing on p-state vs other drivers, when in fact, the script actually set the default governor for the pstate driver on platforms that use pstate. Everything below only looks at systems that use pstate. pstate has two governors: performance and powerstate. performance runs CPU at maximum frequency constantly, and powersave can be configured using various energy profiles energy profiles: - performance - balanced performance - balanced power - power It defaults to balanced performance, I think, but I'm not sure. Whether performance governor is faster than powersave governor is not even clear. https://www.phoronix.com/scan.php?page=article&item=linux50-pstate- cpufreq&num=5 benchmarked them, but did not benchmark the individual energy profiles. For a desktop/laptop, the expected behavior is the powersave governor with balanced_performance on AC and balanced_power on battery. I don't know about servers or VMs, but the benchmark series seems to indicate it does not really matter much performance wise. I think most other distributions configure their kernels to use the powersave governor by default, whereas we configure it to use the performance governor and then switch it later in the boot to get the maximum performance during bootup. It's not clear to me that's actually useful. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1885730/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1884288] Re: LapBook Pro touchpad (HTIX5288:00) sometimes does not work when machine is restarted
Hi Califa, thank you for your suggestion. Unfortunately this has not solved my problem. I tried a reboot after updating GRUB file and touchpad gone again. This is what the GRUB looks like now: GRUB_DEFAULT=0 GRUB_TIMEOUT_STYLE=hidden GRUB_TIMEOUT=0 GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian` GRUB_CMDLINE_LINUX_DEFAULT="quiet splash hid.debug=1 i2c-hid.debug=1 log_buf_le> GRUB_CMDLINE_LINUX="i8042.nopnp pci = noaer" Is this correct? Using the touchpad is not absolutely essential as I do have a usb mouse, however, it is not something that I would like to write off as a quirk and live with it as there are situations where using an external mouse is awkward, for example sitting on the couch, a busy train, etc. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1884288 Title: LapBook Pro touchpad (HTIX5288:00) sometimes does not work when machine is restarted Status in linux package in Ubuntu: Confirmed Bug description: Touchpad completely ceases to work sometimes upon startup / restart. When this happens, I have to plug in an external mouse to navigate as touchpad is not even recognised as a device when I use xinput command in terminal. I removed and reinstalled xserver-xorg-input-synaptics which may have got it working again, although I am not too sure. When the trackpad is working, it's device name is listed as HTIX5288:00 0911:5288 Touchpad. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jun 19 18:03:47 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics 605 [8086:3185] (rev 03) (prog-if 00 [VGA controller]) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0c45:6366 Microdia USB 2.0 Camera Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=c549aad1-cbca-42d0-abc5-e73556f0921b ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/29/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E.G140J.D8.E1.016.bin dmi.board.asset.tag: Default string dmi.board.name: Default string dmi.board.vendor: Default string dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE.G140J.D8.E1.016.bin:bd11/29/2019:svn:pnLapBookPro:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: LapBook Pro dmi.product.sku: Default string dmi.product.version: Default string version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ian1619 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0c45:6366 Microdia USB 2.0 Camera Bus 001 Device 008: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=c549aad1-cbca-42d0-abc5-e73556f0921b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.4.0-37-generic N/A linux
[Kernel-packages] [Bug 1864073] Re: seccomp_bpf fails Eoan 5.3 in ubuntu_kernel_selftests
*** This bug is a duplicate of bug 1872047 ***
https://bugs.launchpad.net/bugs/1872047
** This bug has been marked a duplicate of bug 1872047
kselftest: seccomp kill_after_ptrace() timeout
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1864073
Title:
seccomp_bpf fails Eoan 5.3 in ubuntu_kernel_selftests
Status in ubuntu-kernel-tests:
Triaged
Status in linux-aws package in Ubuntu:
Confirmed
Status in linux-aws source package in Eoan:
Confirmed
Bug description:
Cloud: AWS
Kernel: 5.3.0-1012.13
Test: ubuntu_kernel_selftests
The following is observed from the autotest failure.
02/19 21:33:08 DEBUG| utils:0153| [stdout] Estimated seccomp overhead per
syscall: 42 ns
02/19 21:33:08 DEBUG| utils:0153| [stdout] ok 1..2 selftests: seccomp:
seccomp_benchmark [PASS]
02/19 21:33:08 DEBUG| utils:0153| [stdout] make[1]: Leaving directory
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/seccomp'
02/19 21:33:08 DEBUG| utils:0153| [stdout] make: Leaving directory
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests'
02/19 21:33:08 INFO |ubuntu_ker:0179| == Summary ===
02/19 21:33:08 INFO |ubuntu_ker:0056| Sub test case: seccomp_bpf failed.
02/19 21:33:08 ERROR| test:0414| Exception escaping from test:
Traceback (most recent call last):
File "/home/ubuntu/autotest/client/shared/test.py", line 411, in _exec
_call_test_function(self.execute, *p_args, **p_dargs)
File "/home/ubuntu/autotest/client/shared/test.py", line 823, in
_call_test_function
return func(*args, **dargs)
File "/home/ubuntu/autotest/client/shared/test.py", line 291, in execute
postprocess_profiled_run, args, dargs)
File "/home/ubuntu/autotest/client/shared/test.py", line 212, in
_call_run_once
self.run_once(*args, **dargs)
File
"/home/ubuntu/autotest/client/tests/ubuntu_kernel_selftests/ubuntu_kernel_selftests.py",
line 188, in run_once
raise error.TestError('Test failed for ' + test_name)
TestError: Test failed for seccomp
When the test is run standalone we can get a little more information.
[==] Running 75 tests from 1 test cases.
[ RUN ] global.mode_strict_support
[ OK ] global.mode_strict_support
[ RUN ] global.mode_strict_cannot_call_prctl
[ OK ] global.mode_strict_cannot_call_prctl
[ RUN ] global.no_new_privs_support
[ OK ] global.no_new_privs_support
[ RUN ] global.mode_filter_support
[ OK ] global.mode_filter_support
[ RUN ] global.mode_filter_without_nnp
[ OK ] global.mode_filter_without_nnp
[ RUN ] global.filter_size_limits
[ OK ] global.filter_size_limits
[ RUN ] global.filter_chain_limits
[ OK ] global.filter_chain_limits
[ RUN ] global.mode_filter_cannot_move_to_strict
[ OK ] global.mode_filter_cannot_move_to_strict
[ RUN ] global.mode_filter_get_seccomp
[ OK ] global.mode_filter_get_seccomp
[ RUN ] global.ALLOW_all
[ OK ] global.ALLOW_all
[ RUN ] global.empty_prog
[ OK ] global.empty_prog
[ RUN ] global.log_all
[ OK ] global.log_all
[ RUN ] global.unknown_ret_is_kill_inside
[ OK ] global.unknown_ret_is_kill_inside
[ RUN ] global.unknown_ret_is_kill_above_allow
[ OK ] global.unknown_ret_is_kill_above_allow
[ RUN ] global.KILL_all
[ OK ] global.KILL_all
[ RUN ] global.KILL_one
[ OK ] global.KILL_one
[ RUN ] global.KILL_one_arg_one
[ OK ] global.KILL_one_arg_one
[ RUN ] global.KILL_one_arg_six
[ OK ] global.KILL_one_arg_six
[ RUN ] global.KILL_thread
[ OK ] global.KILL_thread
[ RUN ] global.KILL_process
[ OK ] global.KILL_process
[ RUN ] global.arg_out_of_range
[ OK ] global.arg_out_of_range
[ RUN ] global.ERRNO_valid
[ OK ] global.ERRNO_valid
[ RUN ] global.ERRNO_zero
[ OK ] global.ERRNO_zero
[ RUN ] global.ERRNO_capped
[ OK ] global.ERRNO_capped
[ RUN ] global.ERRNO_order
[ OK ] global.ERRNO_order
[ RUN ] TRAP.dfl
[ OK ] TRAP.dfl
[ RUN ] TRAP.ign
[ OK ] TRAP.ign
[ RUN ] TRAP.handler
[ OK ] TRAP.handler
[ RUN ] precedence.allow_ok
[ OK ] precedence.allow_ok
[ RUN ] precedence.kill_is_highest
[ OK ] precedence.kill_is_highest
[ RUN ] precedence.kill_is_highest_in_any_order
[ OK ] precedence.kill_is_highest_in_any_order
[ RUN ] precedence.trap_is_second
[ OK ] precedence.trap_is_second
[ RUN ] precedence.trap_is_second_in_any_order
[ OK ] precedence.trap_is_second_in_any_order
[ RUN ] precedence.errno_is_th
[Kernel-packages] [Bug 1849844] Re: seccomp test in ubuntu_kernel_selftests failed to build on D amd64
*** This bug is a duplicate of bug 1872047 ***
https://bugs.launchpad.net/bugs/1872047
** This bug is no longer a duplicate of bug 1864073
seccomp_bpf fails Eoan 5.3 in ubuntu_kernel_selftests
** This bug has been marked a duplicate of bug 1872047
kselftest: seccomp kill_after_ptrace() timeout
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1849844
Title:
seccomp test in ubuntu_kernel_selftests failed to build on D amd64
Status in ubuntu-kernel-tests:
Invalid
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Disco:
Invalid
Bug description:
Test failed to build with the proposed Disco kernel with:
undefined reference to `BIT'
ubuntu@moe:~/ubuntu-disco/tools/testing/selftests$ sudo make run_tests
make[1]: Entering directory
'/home/ubuntu/ubuntu-disco/tools/testing/selftests/seccomp'
gcc -Wl,-no-as-needed -Wall seccomp_bpf.c -lpthread -o seccomp_bpf
seccomp_bpf.c: In function ‘user_notification_continue’:
seccomp_bpf.c:3074:26: warning: overflow in conversion from ‘long int’ to
‘__s32’ {aka ‘int’} changes value from ‘116983961184613’ to ‘1936943461’
[-Woverflow]
#define USER_NOTIF_MAGIC 116983961184613L
^~~~
seccomp_bpf.c:3535:15: note: in expansion of macro ‘USER_NOTIF_MAGIC’
resp.error = USER_NOTIF_MAGIC;
^~~~
/usr/bin/ld: /tmp/cc5Df3dg.o: in function `user_notification_continue':
seccomp_bpf.c:(.text+0x2e226): undefined reference to `BIT'
collect2: error: ld returned 1 exit status
make[1]: *** [Makefile:12: seccomp_bpf] Error 1
make[1]: Leaving directory
'/home/ubuntu/ubuntu-disco/tools/testing/selftests/seccomp'
make: *** [Makefile:91: all] Error 2
Note that bug 1849281 looks like a different issue.
ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: linux-image-5.0.0-33-generic 5.0.0-33.35
ProcVersionSignature: User Name 5.0.0-33.35-generic 5.0.21
Uname: Linux 5.0.0-33-generic x86_64
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Oct 25 13:38 seq
crw-rw 1 root audio 116, 33 Oct 25 13:38 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.10-0ubuntu27.1
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord':
'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
CurrentDmesg: [ 484.024237] systemd-journald[391]: /dev/kmsg buffer overrun,
some messages lost.
Date: Fri Oct 25 13:50:36 2019
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
PciMultimedia:
ProcFB: 0 cirrusdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-33-generic
root=UUID=36e162f3-41b5-4487-a6dc-09ba4e37d3bf ro console=tty1 console=ttyS0
RelatedPackageVersions:
linux-restricted-modules-5.0.0-33-generic N/A
linux-backports-modules-5.0.0-33-generic N/A
linux-firmware1.178.5
RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/01/2014
dmi.bios.vendor: SeaBIOS
dmi.bios.version: 1.10.2-1ubuntu1
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.version: pc-i440fx-bionic
dmi.modalias:
dmi:bvnSeaBIOS:bvr1.10.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-bionic:cvnQEMU:ct1:cvrpc-i440fx-bionic:
dmi.product.name: Standard PC (i440FX + PIIX, 1996)
dmi.product.version: pc-i440fx-bionic
dmi.sys.vendor: QEMU
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1849844/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1885757] [NEW] seccomp_bpf fails on powerpc
Public bug reported: [Impact] seccomp_bpf test fails on powerpc and ends up being disabled on some series, or causing engineers to waste their time verifying the same failures are the only ones we see every kernel release. [Test case] Run the test and notice there are no more failures. [Regression potential] We may break the test on different architectures. That doesn't break users, though, as the changes are only on tests. It has been tested at least on ppc64el and amd64. ** Affects: linux (Ubuntu) Importance: Medium Assignee: Thadeu Lima de Souza Cascardo (cascardo) Status: In Progress ** Affects: linux (Ubuntu Bionic) Importance: Medium Assignee: Thadeu Lima de Souza Cascardo (cascardo) Status: In Progress ** Affects: linux (Ubuntu Eoan) Importance: Medium Assignee: Thadeu Lima de Souza Cascardo (cascardo) Status: In Progress ** Affects: linux (Ubuntu Focal) Importance: Medium Assignee: Thadeu Lima de Souza Cascardo (cascardo) Status: In Progress ** Affects: linux (Ubuntu Groovy) Importance: Medium Assignee: Thadeu Lima de Souza Cascardo (cascardo) Status: In Progress ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Eoan) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux (Ubuntu Groovy) Status: New => In Progress ** Changed in: linux (Ubuntu Focal) Status: New => In Progress ** Changed in: linux (Ubuntu Eoan) Status: New => In Progress ** Changed in: linux (Ubuntu Groovy) Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo) ** Changed in: linux (Ubuntu Focal) Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo) ** Changed in: linux (Ubuntu Eoan) Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo) ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo) ** Changed in: linux (Ubuntu Groovy) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Eoan) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1885757 Title: seccomp_bpf fails on powerpc Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Status in linux source package in Eoan: In Progress Status in linux source package in Focal: In Progress Status in linux source package in Groovy: In Progress Bug description: [Impact] seccomp_bpf test fails on powerpc and ends up being disabled on some series, or causing engineers to waste their time verifying the same failures are the only ones we see every kernel release. [Test case] Run the test and notice there are no more failures. [Regression potential] We may break the test on different architectures. That doesn't break users, though, as the changes are only on tests. It has been tested at least on ppc64el and amd64. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1885757/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1885757] Re: seccomp_bpf fails on powerpc
https://lore.kernel.org/linux- kselftest/20200630164739.1268222-1-casca...@canonical.com/T/#u -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1885757 Title: seccomp_bpf fails on powerpc Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Status in linux source package in Eoan: In Progress Status in linux source package in Focal: In Progress Status in linux source package in Groovy: In Progress Bug description: [Impact] seccomp_bpf test fails on powerpc and ends up being disabled on some series, or causing engineers to waste their time verifying the same failures are the only ones we see every kernel release. [Test case] Run the test and notice there are no more failures. [Regression potential] We may break the test on different architectures. That doesn't break users, though, as the changes are only on tests. It has been tested at least on ppc64el and amd64. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1885757/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1870971] Re: [amdgpu] (X)ubuntu 20.04 boots to black screen on Lenovo Ideapad L340-17API when in battery mode
@franzheinz: I didn't notice any negative side effects with the workaround in #20. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1870971 Title: [amdgpu] (X)ubuntu 20.04 boots to black screen on Lenovo Ideapad L340-17API when in battery mode Status in linux package in Ubuntu: Confirmed Status in vlc package in Ubuntu: Invalid Bug description: Freshly installed Xubuntu 20.04 shows black screen instead of login screen upon boot on Lenovo Ideapad L340-17API. It is not possible to chvt to text terminal when boot is stuck on black screen. Booting with 'nomodeset' kernel option works properly but is not an option (e.g. screen brightness is not adjustable in this case). Another workaround is to ssh to laptop and run systemctl restart display-manager.service. After 5-10 seconds upon executing this command perfectly working login screen appears. Check dmesg. There is apparently related messages from amdgpu driver: ... апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_crtc_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_crtc_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_crtc_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_crtc_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_crtc_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_crtc_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_crtc_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_crtc_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_pflip_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_pflip_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_pflip_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_pflip_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_pflip_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_pflip_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_pflip_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_pflip_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_vupdate_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_vupdate_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_vupdate_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_vupdate_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_vupdate_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_vupdate_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_vupdate_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_vupdate_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm] recover vram bo from shadow start апр 05 20:46:45 kernel: [drm] recover vram bo from shadow done апр 05 20:46:45 kernel: [drm] Skip scheduling IBs! апр 05 20:46:45 kernel: [ cut here ] апр 05 20:46:45 kernel: WARNING: CPU: 3 PID: 793 at include/linux/dma-fence.h:533 drm_sched_resubmit_jobs+0x152/0x160 [gpu_sched] апр 05 20:46:45 kernel: Modules linked in: cmac algif_hash algif_skcipher af_alg bnep zram nls_iso8859_1 snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio snd_hda_codec_hdmi snd_hda_intel snd_intel_nhlt snd_hda_codec > апр 05 20:46:45 kernel: CPU: 3 PID: 793 Comm: kworker/3:4 Tainted: G OE 5.4.0-21-generic #25-Ubuntu апр 05 20:46:45 kernel: Hardware name: LENOVO 81LY/LNVNB161216, BIOS ARCN32WW 07/11/2019 апр 05 20:46:45 kernel: Workqueue: events drm_sched_job_timedout [gpu_sched] апр 05 20:46:45 kernel: RIP: 0010:drm_sched_resubmit_jobs+0x152/0x160 [gpu_sched] апр 05 20:46:45 kernel: Code: 41 5c 41 5d 41 5e 41 5f 5d c3 49 8b 46 10 31 c9 48 c7 80 80 00 00 00 00 00 00 00 49 8b 7f 70 31 c0 83 e7 01 74 04 0f 0b eb bf <0f> 0b eb c7 0f 0b eb 8b 66 0f 1f 44 00 00 0f 1f 44 00 00 83 7f 4c апр 05 20:46:45 kernel: RSP: 0018:a4dc806d7d28 EFLAGS: 00010246 апр 05 20:46:45 kernel: RAX: RBX: 0001 RCX: апр 05 20:46:45 kernel: RDX: 8cc9a6fc9180 RSI: 8cc9ac4609f8 RDI: апр 05 20:46:45 kernel: RBP: a4dc806d7d60 R08: 047a R09: 0004 апр 05 20:46:45 kernel: R10: R11: 0001 R12: 8cc9ac463c00 апр 05 20:46:45 kernel: R13: 8cc9a63c7980 R14: 8cc9ac460800 R15: 8cc9a6fc9140 апр 05 20:46:45 kernel: FS: () GS:8cc9b88c() knlGS: апр 05 20:46:45 kernel: CS: 0010 DS: ES: CR0: 80050033 апр 05 20:46:45 kernel: CR2: 7f275ff6c000 CR3: 0001af148000 CR4: 003406e0 апр 05 20:46:45 kernel: Call Trace: апр 05 20:46:45 kernel: amdgpu_device_gpu_recover+0x6cd/0x95a [amdgpu] апр 05 20:46:45 kernel: amdgpu_job_timedout+0x103/0x130 [amdgpu] апр 05 20:46:45 kernel: drm_sched_job_timedout+0x44/0x90 [gpu_sched] апр 05 20:46:45 kernel: process_one_work+0x1eb/0x3b0
[Kernel-packages] [Bug 1885757] Re: seccomp_bpf fails on powerpc
** Also affects: ubuntu-kernel-tests Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1885757 Title: seccomp_bpf fails on powerpc Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Status in linux source package in Eoan: In Progress Status in linux source package in Focal: In Progress Status in linux source package in Groovy: In Progress Bug description: [Impact] seccomp_bpf test fails on powerpc and ends up being disabled on some series, or causing engineers to waste their time verifying the same failures are the only ones we see every kernel release. [Test case] Run the test and notice there are no more failures. [Regression potential] We may break the test on different architectures. That doesn't break users, though, as the changes are only on tests. It has been tested at least on ppc64el and amd64. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1885757/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1855747] Re: systemd-udevd appears to be attempting to load Nvidia kernel modules in a tight loop
>Kai-Heng Feng (kaihengfeng) wrote on 2019-12-11: #4 > Can you please run `sudo update-initramfs -u -k all` and see if the issue still happens? yes this persists even after that. I have a nvidia card but I want to blacklist it. even blacklisted, the systemd-udevd /lib/udev/rules.d/71-nvidia.rules attempt to run the rules forever. moving /lib/udev/rules.d/71-nvidia.rules away from udev rules search path fixes that, but that's not the correct solution. why does systemd- udev insist repeating instead of failing after first try? 18.04 lts here. drivers nvidia-driver-390 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-440 in Ubuntu. https://bugs.launchpad.net/bugs/1855747 Title: systemd-udevd appears to be attempting to load Nvidia kernel modules in a tight loop Status in nvidia-graphics-drivers-440 package in Ubuntu: Expired Status in systemd package in Ubuntu: Expired Bug description: I'm seeing these lines repeated: ``` Dec 09 12:01:45 surprise systemd-udevd[731]: nvidia: Process '/usr/bin/nvidia-smi' failed with exit code 9. Dec 09 12:01:46 surprise systemd-udevd[731]: nvidia: Process '/sbin/modprobe nvidia-modeset' failed with exit code 1. Dec 09 12:01:46 surprise systemd-udevd[731]: nvidia: Process '/sbin/modprobe nvidia-drm' failed with exit code 1. Dec 09 12:01:47 surprise systemd-udevd[731]: nvidia: Process '/sbin/modprobe nvidia-uvm' failed with exit code 1. Dec 09 12:01:48 surprise systemd-udevd[731]: nvidia: Process '/usr/bin/nvidia-smi' failed with exit code 9. Dec 09 12:01:49 surprise systemd-udevd[731]: nvidia: Process '/sbin/modprobe nvidia-modeset' failed with exit code 1. Dec 09 12:01:49 surprise systemd-udevd[731]: nvidia: Process '/sbin/modprobe nvidia-drm' failed with exit code 1. Dec 09 12:01:50 surprise systemd-udevd[731]: nvidia: Process '/sbin/modprobe nvidia-uvm' failed with exit code 1. ``` My system has been up ~an hour: $ uptime 12:02:28 up 1:00, 1 user, load average: 4.52, 4.80, 5.50 and I've seen a lot of these: $ journalctl -u systemd-udevd.service -b0 | grep -c "exit code 9" 1333 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: udev 243-3ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-25.27-generic 5.3.13 Uname: Linux 5.3.0-25-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.11-0ubuntu13 Architecture: amd64 CurrentDesktop: i3 CustomUdevRuleFiles: 70-snap.core.rules 70-snap.spotify.rules Date: Mon Dec 9 11:59:10 2019 InstallationDate: Installed on 2019-05-07 (215 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Gigabyte Technology Co., Ltd. B450M DS3H ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-25-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash resume=UUID=73909634-a75d-42c9-8f66-a69138690756 vt.handoff=7 SourcePackage: systemd UpgradeStatus: Upgraded to focal on 2019-11-15 (23 days ago) dmi.bios.date: 01/25/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F4 dmi.board.asset.tag: Default string dmi.board.name: B450M DS3H-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF4:bd01/25/2019:svnGigabyteTechnologyCo.,Ltd.:pnB450MDS3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450MDS3H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: B450M DS3H dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. modified.conffile..etc.apport.crashdb.conf: [modified] modified.conffile..etc.udev.udev.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2019-11-25T16:40:26.261317 mtime.conffile..etc.udev.udev.conf: 2019-11-28T09:22:42.096686 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-440/+bug/1855747/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1855747] Re: systemd-udevd appears to be attempting to load Nvidia kernel modules in a tight loop
also other people complained https://www.reddit.com/r/VFIO/comments/90tg4h/after_loading_vfiopci_instead_of_nvidia_my_dmesg/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-440 in Ubuntu. https://bugs.launchpad.net/bugs/1855747 Title: systemd-udevd appears to be attempting to load Nvidia kernel modules in a tight loop Status in nvidia-graphics-drivers-440 package in Ubuntu: Expired Status in systemd package in Ubuntu: Expired Bug description: I'm seeing these lines repeated: ``` Dec 09 12:01:45 surprise systemd-udevd[731]: nvidia: Process '/usr/bin/nvidia-smi' failed with exit code 9. Dec 09 12:01:46 surprise systemd-udevd[731]: nvidia: Process '/sbin/modprobe nvidia-modeset' failed with exit code 1. Dec 09 12:01:46 surprise systemd-udevd[731]: nvidia: Process '/sbin/modprobe nvidia-drm' failed with exit code 1. Dec 09 12:01:47 surprise systemd-udevd[731]: nvidia: Process '/sbin/modprobe nvidia-uvm' failed with exit code 1. Dec 09 12:01:48 surprise systemd-udevd[731]: nvidia: Process '/usr/bin/nvidia-smi' failed with exit code 9. Dec 09 12:01:49 surprise systemd-udevd[731]: nvidia: Process '/sbin/modprobe nvidia-modeset' failed with exit code 1. Dec 09 12:01:49 surprise systemd-udevd[731]: nvidia: Process '/sbin/modprobe nvidia-drm' failed with exit code 1. Dec 09 12:01:50 surprise systemd-udevd[731]: nvidia: Process '/sbin/modprobe nvidia-uvm' failed with exit code 1. ``` My system has been up ~an hour: $ uptime 12:02:28 up 1:00, 1 user, load average: 4.52, 4.80, 5.50 and I've seen a lot of these: $ journalctl -u systemd-udevd.service -b0 | grep -c "exit code 9" 1333 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: udev 243-3ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-25.27-generic 5.3.13 Uname: Linux 5.3.0-25-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.11-0ubuntu13 Architecture: amd64 CurrentDesktop: i3 CustomUdevRuleFiles: 70-snap.core.rules 70-snap.spotify.rules Date: Mon Dec 9 11:59:10 2019 InstallationDate: Installed on 2019-05-07 (215 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Gigabyte Technology Co., Ltd. B450M DS3H ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-25-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash resume=UUID=73909634-a75d-42c9-8f66-a69138690756 vt.handoff=7 SourcePackage: systemd UpgradeStatus: Upgraded to focal on 2019-11-15 (23 days ago) dmi.bios.date: 01/25/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F4 dmi.board.asset.tag: Default string dmi.board.name: B450M DS3H-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF4:bd01/25/2019:svnGigabyteTechnologyCo.,Ltd.:pnB450MDS3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450MDS3H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: B450M DS3H dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. modified.conffile..etc.apport.crashdb.conf: [modified] modified.conffile..etc.udev.udev.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2019-11-25T16:40:26.261317 mtime.conffile..etc.udev.udev.conf: 2019-11-28T09:22:42.096686 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-440/+bug/1855747/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1885775] [NEW] Eoan update: upstream stable patchset 2020-06-30
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2020-06-30 from git://git.kernel.org/ ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: linux (Ubuntu Eoan) Importance: Undecided Assignee: Kamal Mostafa (kamalmostafa) Status: In Progress ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Eoan) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Eoan) Status: New => In Progress ** Changed in: linux (Ubuntu Eoan) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1885775 Title: Eoan update: upstream stable patchset 2020-06-30 Status in linux package in Ubuntu: Confirmed Status in linux source package in Eoan: In Progress Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2020-06-30 from git://git.kernel.org/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1885775/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1885775] Re: Eoan update: upstream stable patchset 2020-06-30
** Description changed:
-
- SRU Justification
-
- Impact:
-The upstream process for stable tree updates is quite similar
-in scope to the Ubuntu SRU process, e.g., each patch has to
-demonstrably fix a bug, and each patch is vetted by upstream
-by originating either directly from a mainline/stable Linux tree or
-a minimally backported form of that patch. The following upstream
-stable patches should be included in the Ubuntu kernel:
-
-upstream stable patchset 2020-06-30
-from git://git.kernel.org/
+ SRU Justification
+
+ Impact:
+ The upstream process for stable tree updates is quite similar
+ in scope to the Ubuntu SRU process, e.g., each patch has to
+ demonstrably fix a bug, and each patch is vetted by upstream
+ by originating either directly from a mainline/stable Linux tree or
+ a minimally backported form of that patch. The following upstream
+ stable patches should be included in the Ubuntu kernel:
+
+ upstream stable patchset 2020-06-30
+
+ Ported from the following upstream stable releases:
+ v4.19.129, v5.4.47
+
+ from git://git.kernel.org/
+
+ ipv6: fix IPV6_ADDRFORM operation logic
+ net_failover: fixed rollback in net_failover_open()
+ bridge: Avoid infinite loop when suppressing NS messages with invalid options
+ vxlan: Avoid infinite loop when suppressing NS messages with invalid options
+ tun: correct header offsets in napi frags mode
+ Input: mms114 - fix handling of mms345l
+ ARM: 8977/1: ptrace: Fix mask for thumb breakpoint hook
+ sched/fair: Don't NUMA balance for kthreads
+ Input: synaptics - add a second working PNP_ID for Lenovo T470s
+ drivers/net/ibmvnic: Update VNIC protocol version reporting
+ powerpc/xive: Clear the page tables for the ESB IO mapping
+ ath9k_htc: Silence undersized packet warnings
+ RDMA/uverbs: Make the event_queue fds return POLLERR when disassociated
+ x86/cpu/amd: Make erratum #1054 a legacy erratum
+ perf probe: Accept the instance number of kretprobe event
+ mm: add kvfree_sensitive() for freeing sensitive data objects
+ aio: fix async fsync creds
+ x86_64: Fix jiffies ODR violation
+ x86/PCI: Mark Intel C620 MROMs as having non-compliant BARs
+ x86/speculation: Prevent rogue cross-process SSBD shutdown
+ x86/reboot/quirks: Add MacBook6,1 reboot quirk
+ efi/efivars: Add missing kobject_put() in sysfs entry creation error path
+ ALSA: es1688: Add the missed snd_card_free()
+ ALSA: hda/realtek - add a pintbl quirk for several Lenovo machines
+ ALSA: usb-audio: Fix inconsistent card PM state after resume
+ ALSA: usb-audio: Add vendor, product and profile name for HP Thunderbolt Dock
+ ACPI: sysfs: Fix reference count leak in acpi_sysfs_add_hotplug_profile()
+ ACPI: CPPC: Fix reference count leak in acpi_cppc_processor_probe()
+ ACPI: GED: add support for _Exx / _Lxx handler methods
+ ACPI: PM: Avoid using power resources if there are none for D0
+ nilfs2: fix null pointer dereference at nilfs_segctor_do_construct()
+ spi: dw: Fix controller unregister order
+ spi: bcm2835aux: Fix controller unregister order
+ spi: bcm-qspi: when tx/rx buffer is NULL set to 0
+ PM: runtime: clk: Fix clk_pm_runtime_get() error path
+ crypto: cavium/nitrox - Fix 'nitrox_get_first_device()' when ndevlist is
fully iterated
+ ALSA: pcm: disallow linking stream to itself
+ x86/{mce,mm}: Unmap the entire page if the whole page is affected and poisoned
+ KVM: x86: Fix APIC page invalidation race
+ KVM: x86/mmu: Consolidate "is MMIO SPTE" code
+ KVM: x86: only do L1TF workaround on affected processors
+ x86/speculation: Avoid force-disabling IBPB based on STIBP and enhanced IBRS.
+ x86/speculation: PR_SPEC_FORCE_DISABLE enforcement for indirect branches.
+ spi: Fix controller unregister order
+ spi: pxa2xx: Fix controller unregister order
+ spi: bcm2835: Fix controller unregister order
+ spi: pxa2xx: Fix runtime PM ref imbalance on probe error
+ crypto: virtio: Fix use-after-free in virtio_crypto_skcipher_finalize_req()
+ crypto: virtio: Fix src/dst scatterlist calculation in
__virtio_crypto_skcipher_do_req()
+ crypto: virtio: Fix dest length calculation in
__virtio_crypto_skcipher_do_req()
+ selftests/net: in rxtimestamp getopt_long needs terminating null entry
+ ovl: initialize error in ovl_copy_xattr
+ proc: Use new_inode not new_inode_pseudo
+ video: fbdev: w100fb: Fix a potential double free.
+ KVM: nSVM: fix condition for filtering async PF
+ KVM: nSVM: leave ASID aside in copy_vmcb_control_area
+ KVM: nVMX: Consult only the "basic" exit reason when routing nested exit
+ KVM: MIPS: Define KVM_ENTRYHI_ASID to cpu_asid_mask(&boot_cpu_data)
+ KVM: MIPS: Fix VPN2_MASK definition for variable cpu_vmbits
+ KVM: arm64: Make vcpu_cp1x() work on Big Endian hosts
+ scsi: megaraid_sas: TM command refire leads to controller firmware crash
+ ath9k: Fix use-after-free Read in ath9k_wmi_ctrl_rx
+ ath9k: Fix use
[Kernel-packages] [Bug 1882419] Re: Intel 3945ABG [8086:4227] Subsystem [8086:1010]: syslog flooded with "wlan0: Failed check-sdata-in-driver check, flags: 0x4"
Similar error. Syslog grew to 11GB and I see the repitition of this error message seemingly from the mac80211 driver. The error message (in syslog) below repeats forever and fills up syslog. I don't know exactly what triggers it. Jun 30 22:49:23 sapporo kernel: [34661.655411] Modules linked in: hidp nls_utf8 exfat(C) uas usb_storage rfcomm thunderbolt xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo xt_addrtype iptable_filter iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 bpfilter br_netfilter bridge stp llc ccm aufs overlay cmac algif_hash algif_skcipher af_alg bnep snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio snd_hda_intel snd_intel_dspcfg snd_hda_codec snd_hda_core snd_hwdep snd_pcm mei_hdcp intel_rapl_msr snd_seq_midi snd_seq_midi_event snd_rawmidi x86_pkg_temp_thermal intel_powerclamp coretemp iwlmvm kvm_intel mac80211 nls_iso8859_1 libarc4 kvm snd_seq intel_cstate intel_rapl_perf input_leds iwlwifi snd_seq_device joydev uvcvideo snd_timer videobuf2_vmalloc videobuf2_memops serio_raw hp_wmi wmi_bmof videobuf2_v4l2 videobuf2_common btusb intel_wmi_thunderbolt snd cfg80211 btrtl mxm_wmi btbcm soundcore mei_me btintel videodev hid_sensor_accel_3d rtsx_pci_ms Jun 30 22:49:23 sapporo kernel: [34661.655424] hid_sensor_rotation hid_sensor_magn_3d mei hid_sensor_incl_3d hid_sensor_gyro_3d hid_sensor_trigger hid_multitouch mc bluetooth industrialio_triggered_buffer memstick kfifo_buf hid_sensor_iio_common industrialio processor_thermal_device ecdh_generic intel_xhci_usb_role_switch intel_rapl_common cros_ec_ishtp ecc roles cros_ec intel_pch_thermal intel_soc_dts_iosf int3403_thermal int340x_thermal_zone hp_wireless intel_vbtn mac_hid sparse_keymap acpi_pad int3400_thermal acpi_thermal_rel sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables autofs4 dm_crypt raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear system76_io(OE) system76_acpi(OE) hid_sensor_custom hid_sensor_hub intel_ishtp_loader intel_ishtp_hid hid_generic i915 crct10dif_pclmul crc32_pclmul i2c_algo_bit ghash_clmulni_intel rtsx_pci_sdmmc drm_kms_helper aesni_intel intel_ish_ipc crypto_simd syscopyarea nvme sysfillrect sysimgblt fb_sys_fops Jun 30 22:49:23 sapporo kernel: [34661.655437] cryptd glue_helper psmouse i2c_i801 nvme_core rtsx_pci intel_ishtp drm intel_lpss_pci intel_lpss idma64 virt_dma i2c_hid hid wmi pinctrl_sunrisepoint pinctrl_intel video Jun 30 22:49:23 sapporo kernel: [34661.655440] CPU: 2 PID: 44245 Comm: kworker/u8:1 Tainted: GWC OE 5.4.0-7634-generic #38~1592497129~20.04~9a1ea2e-Ubuntu Jun 30 22:49:23 sapporo kernel: [34661.655441] Hardware name: HP HP Spectre x360 Convertible 15-bl0XX/82C1, BIOS F.40 04/25/2019 Jun 30 22:49:23 sapporo kernel: [34661.655449] Workqueue: phy0 ieee80211_csa_connection_drop_work [mac80211] Jun 30 22:49:23 sapporo kernel: [34661.655456] RIP: 0010:drv_sta_state+0x254/0x3f0 [mac80211] Jun 30 22:49:23 sapporo kernel: [34661.655457] Code: 00 45 31 ed e9 66 fe ff ff 48 8b 83 78 04 00 00 48 8d b3 98 04 00 00 48 c7 c7 c8 68 f2 c0 48 85 c0 48 0f 45 f0 e8 47 c1 5f cd <0f> 0b 41 bd fb ff ff ff e9 3d fe ff ff 65 8b 05 e8 ac 16 3f 89 c0 Jun 30 22:49:23 sapporo kernel: [34661.655457] RSP: 0018:bb57c348bc98 EFLAGS: 00010282 Jun 30 22:49:23 sapporo kernel: [34661.655458] RAX: RBX: 98a571e6a8c0 RCX: 0006 Jun 30 22:49:23 sapporo kernel: [34661.655458] RDX: 0007 RSI: 0082 RDI: 98a57eb178c0 Jun 30 22:49:23 sapporo kernel: [34661.655459] RBP: bb57c348bcd0 R08: 01c0ae38 R09: 0004 Jun 30 22:49:23 sapporo kernel: [34661.655459] R10: R11: 0001 R12: 98a57a7107a0 Jun 30 22:49:23 sapporo kernel: [34661.655460] R13: 98a57a7107a0 R14: 0004 R15: 98a57a710d68 Jun 30 22:49:23 sapporo kernel: [34661.655460] FS: () GS:98a57eb0() knlGS: Jun 30 22:49:23 sapporo kernel: [34661.655461] CS: 0010 DS: ES: CR0: 80050033 Jun 30 22:49:23 sapporo kernel: [34661.655461] CR2: 7f71bfaff9d0 CR3: 000476cf8002 CR4: 003606e0 Jun 30 22:49:23 sapporo kernel: [34661.655462] Call Trace: Jun 30 22:49:23 sapporo kernel: [34661.655469] sta_info_move_state+0x276/0x370 [mac80211] Jun 30 22:49:23 sapporo kernel: [34661.655476] __sta_info_destroy_part2+0x2f/0x180 [mac80211] Jun 30 22:49:23 sapporo kernel: [34661.655484] __sta_info_flush+0x128/0x180 [mac80211] Jun 30 22:49:23 sapporo kernel: [34661.655492] ieee80211_set_disassoc+0xc0/0x5f0 [mac80211] Jun 30 22:49:23 sapporo kernel: [34661.655494] ? _raw_spin_unlock_bh+0x1e/0x20 Jun 30 22:49:23 sapporo kernel: [34661.655502] __ieee80211_disconnect+0x86/0x120 [mac80211] Jun 30 22:49:23 sapporo kernel: [34661.655510] ieee80211_csa_connection_drop_work+0x15/0x20 [mac8
[Kernel-packages] [Bug 1884766] Re: use-after-free in af_alg_accept() due to bh_lock_sock()
** Description changed:
- This bug is for tracking and submitting this commit [1] once it lands in
- v5.8-rcN.
+ [Impact]
- [1]
-
https://git.kernel.org/pub/scm/linux/kernel/git/herbert/crypto-2.6.git/commit/?id=34c86f4c4a7be3b3e35aa48bd18299d4c756064d
+ * Users of the Linux kernel's crypto userspace API
+reported BUG() / kernel NULL pointer dereference
+errors after kernel upgrades.
+
+ * The stack trace signature is an accept() syscall
+going through af_alg_accept() and hitting errors
+usually in one of:
+- apparmor_sk_clone_security()
+- apparmor_sock_graft()
+- release_sock()
+
+ [Fix]
+
+ * This is a regression introduced by upstream commit
+37f96694cf73 ("crypto: af_alg - Use bh_lock_sock
+in sk_destruct") which made its way through stable.
+
+ * The offending patch allows the critical regions
+of af_alg_accept() and af_alg_release_parent() to
+run concurrently; now with the "right" events on 2
+CPUs it might drop the non-atomic reference counter
+of the alg_sock then the sock, thus release a sock
+that is still in use.
+
+ * The fix is upstream commit 34c86f4c4a7b ("crypto:
+af_alg - fix use-after-free in af_alg_accept() due
+to bh_lock_sock()") [1]. It changes alg_sock's ref
+counter to atomic, which addresses the root cause.
+
+ [Test Case]
+
+ * There is a synthetic test case available, which
+uses a kprobes kernel module to synchronize the
+concurrent CPUs on the instructions responsible
+for the problem; and a userspace part to run it.
+
+ * The organic reproducer is the Varnish Cache Plus
+software with the Crypto vmod (which uses kernel
+crypto userspace API) under long, very high load.
+
+ * The patch has been verified on both reproducers
+with the 4.15 and 5.7 kernels.
+
+ * More tests performed with 'stress-ng --af-alg'
+with 11 CPUs/hogs on Bionic/Disco/Eoan/Focal
+(all on same version of stress-ng, V0.11.14)
+No regressions observed from original kernel.
+(the af-alg stressor can exercise almost all
+kernel crypto modules shipped with the kernel;
+so it checks more paths/crypto alg interfaces.)
+
+ [Regression Potential]
+
+ * The fix patch does a fundamental change in how
+alg_sock reference counters work, plus another
+change to the 'nokey' counting. This of course
+*has* a risk of regression.
+
+ * Regressions theoretically could manifest as use
+after free errors (in case of undercounting) in
+the af_alg functions or silent memory leaks (in
+case of overcounting), but also other behaviors
+since reference counting is key to many things.
+
+ * FWIW, this patch has been written by the crypto
+subsystem maintainer, who certainly knows a lot
+of the normal and corner cases, thus giving the
+patch more credit.
+
+ * Testing with the organic reproducer ran as long
+as 5 days, without issues, so it does look good.
+
+ [Other Info]
+
+ * [1] Patch:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=34c86f4c4a7be3b3e35aa48bd18299d4c756064d
+
+ [Stack Trace Examples]
+
+ Examples:
+
+ BUG: unable to handle kernel NULL pointer dereference at
+ ...
+ RIP: 0010:apparmor_sk_clone_security+0x26/0x70
+ ...
+ Call Trace:
+ security_sk_clone+0x33/0x50
+ af_alg_accept+0x81/0x1c0 [af_alg]
+ alg_accept+0x15/0x20 [af_alg]
+ SYSC_accept4+0xff/0x210
+ SyS_accept+0x10/0x20
+ do_syscall_64+0x73/0x130
+ entry_SYSCALL_64_after_hwframe+0x3d/0xa2
+
+ general protection fault: [#1] SMP PTI
+ ...
+ RIP: 0010:__release_sock+0x54/0xe0
+ ...
+ Call Trace:
+ release_sock+0x30/0xa0
+ af_alg_accept+0x122/0x1c0 [af_alg]
+ alg_accept+0x15/0x20 [af_alg]
+ SYSC_accept4+0xff/0x210
+ SyS_accept+0x10/0x20
+ do_syscall_64+0x73/0x130
+ entry_SYSCALL_64_after_hwframe+0x3d/0xa2
** Also affects: linux (Ubuntu Groovy)
Importance: Medium
Assignee: Mauricio Faria de Oliveira (mfo)
Status: Confirmed
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Eoan)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1884766
Title:
use-after-free in af_alg_accept() due to bh_lock_sock()
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Xenial:
New
Status in linux source package in Bionic:
New
Status in linux source package in Eoan:
New
Status in linux source package in Focal:
New
Status in linux source package in Groovy:
Confirmed
B
[Kernel-packages] [Bug 1882419] Re: Intel 3945ABG [8086:4227] Subsystem [8086:1010]: syslog flooded with "wlan0: Failed check-sdata-in-driver check, flags: 0x4"
These are the part before the start of the error dump looping. One of the lines is giving a 'Microcode SW error'. Is this the cause Jun 30 22:46:07 sapporo kernel: [34465.678263] iwlwifi :3b:00.0: Microcode SW error detected. Restarting 0x200. Syslog dump: Jun 30 22:46:06 sapporo kernel: [34464.164632] wlp59s0: cannot understand ECSA IE operating class, 0, ignoring Jun 30 22:46:06 sapporo wpa_supplicant[787]: wlp59s0: CTRL-EVENT-STARTED-CHANNEL-SWITCH freq=5540 ht_enabled=1 ch_offset=1 ch_width=80 MHz cf1=5530 cf2=0 Jun 30 22:46:06 sapporo kernel: [34464.267457] wlp59s0: cannot understand ECSA IE operating class, 0, ignoring Jun 30 22:46:06 sapporo kernel: [34464.369259] wlp59s0: cannot understand ECSA IE operating class, 0, ignoring Jun 30 22:46:06 sapporo kernel: [34464.471749] wlp59s0: cannot understand ECSA IE operating class, 0, ignoring Jun 30 22:46:06 sapporo kernel: [34464.574148] wlp59s0: cannot understand ECSA IE operating class, 0, ignoring Jun 30 22:46:06 sapporo kernel: [34464.676582] wlp59s0: cannot understand ECSA IE operating class, 0, ignoring Jun 30 22:46:06 sapporo kernel: [34464.778822] wlp59s0: cannot understand ECSA IE operating class, 0, ignoring Jun 30 22:46:06 sapporo kernel: [34464.881254] wlp59s0: cannot understand ECSA IE operating class, 0, ignoring Jun 30 22:46:06 sapporo kernel: [34464.983611] wlp59s0: cannot understand ECSA IE operating class, 0, ignoring Jun 30 22:46:07 sapporo kernel: [34465.086076] wlp59s0: cannot understand ECSA IE operating class, 0, ignoring Jun 30 22:46:07 sapporo kernel: [34465.188515] wlp59s0: cannot understand ECSA IE operating class, 0, ignoring Jun 30 22:46:07 sapporo kernel: [34465.290813] wlp59s0: cannot understand ECSA IE operating class, 0, ignoring Jun 30 22:46:07 sapporo kernel: [34465.393663] wlp59s0: cannot understand ECSA IE operating class, 0, ignoring Jun 30 22:46:07 sapporo kernel: [34465.495660] wlp59s0: cannot understand ECSA IE operating class, 0, ignoring Jun 30 22:46:07 sapporo kernel: [34465.598069] wlp59s0: cannot understand ECSA IE operating class, 0, ignoring Jun 30 22:46:07 sapporo kernel: [34465.678263] iwlwifi :3b:00.0: Microcode SW error detected. Restarting 0x200. Jun 30 22:46:07 sapporo kernel: [34465.678486] iwlwifi :3b:00.0: Start IWL Error Log Dump: Jun 30 22:46:07 sapporo kernel: [34465.678489] iwlwifi :3b:00.0: Status: 0x0040, count: 6 Jun 30 22:46:07 sapporo kernel: [34465.678491] iwlwifi :3b:00.0: Loaded firmware version: 36.77d01142.0 Jun 30 22:46:07 sapporo kernel: [34465.678493] iwlwifi :3b:00.0: 0x0039 | BAD_COMMAND Jun 30 22:46:07 sapporo kernel: [34465.678495] iwlwifi :3b:00.0: 0x0230 | trm_hw_status0 Jun 30 22:46:07 sapporo kernel: [34465.678496] iwlwifi :3b:00.0: 0x | trm_hw_status1 Jun 30 22:46:07 sapporo kernel: [34465.678498] iwlwifi :3b:00.0: 0x000248EC | branchlink2 Jun 30 22:46:07 sapporo kernel: [34465.678500] iwlwifi :3b:00.0: 0x0003A862 | interruptlink1 Jun 30 22:46:07 sapporo kernel: [34465.678501] iwlwifi :3b:00.0: 0x | interruptlink2 Jun 30 22:46:07 sapporo kernel: [34465.678503] iwlwifi :3b:00.0: 0x0002 | data1 Jun 30 22:46:07 sapporo kernel: [34465.678504] iwlwifi :3b:00.0: 0xDEADBEEF | data2 Jun 30 22:46:07 sapporo kernel: [34465.678506] iwlwifi :3b:00.0: 0xDEADBEEF | data3 Jun 30 22:46:07 sapporo kernel: [34465.678507] iwlwifi :3b:00.0: 0x56C052FF | beacon time Jun 30 22:46:07 sapporo kernel: [34465.678509] iwlwifi :3b:00.0: 0x5581DD08 | tsf low Jun 30 22:46:07 sapporo kernel: [34465.678511] iwlwifi :3b:00.0: 0x0007 | tsf hi Jun 30 22:46:07 sapporo kernel: [34465.678512] iwlwifi :3b:00.0: 0x | time gp1 Jun 30 22:46:07 sapporo kernel: [34465.678514] iwlwifi :3b:00.0: 0x69A0D064 | time gp2 Jun 30 22:46:07 sapporo kernel: [34465.678515] iwlwifi :3b:00.0: 0x0001 | uCode revision type Jun 30 22:46:07 sapporo kernel: [34465.678517] iwlwifi :3b:00.0: 0x0024 | uCode version major Jun 30 22:46:07 sapporo kernel: [34465.678518] iwlwifi :3b:00.0: 0x77D01142 | uCode version minor Jun 30 22:46:07 sapporo kernel: [34465.678520] iwlwifi :3b:00.0: 0x0230 | hw version Jun 30 22:46:07 sapporo kernel: [34465.678522] iwlwifi :3b:00.0: 0x00C89000 | board version Jun 30 22:46:07 sapporo kernel: [34465.678523] iwlwifi :3b:00.0: 0x00280304 | hcmd Jun 30 22:46:07 sapporo kernel: [34465.678525] iwlwifi :3b:00.0: 0x24022080 | isr0 Jun 30 22:46:07 sapporo kernel: [34465.678526] iwlwifi :3b:00.0: 0x0100 | isr1 Jun 30 22:46:07 sapporo kernel: [34465.678528] iwlwifi :3b:00.0: 0x08201802 | isr2 Jun 30 22:46:07 sapporo kernel: [34465.678529] iwlwifi :3b:00.0: 0x004144C0 | isr3 Jun 30 22:46:07 sapporo kernel: [34465.678531] iwlwifi :3b:00.0: 0x | isr4 Jun 30 22:46:07 sapporo kernel: [34465.678532] iwlwifi :3b:00.0: 0x9284009D | last cmd Id Jun 30 22:46:07
[Kernel-packages] [Bug 1215411] Re: libcpupower.so is not installed from linux-tools
** Tags added: rls-gg-incoming -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1215411 Title: libcpupower.so is not installed from linux-tools Status in linux package in Ubuntu: In Progress Status in linux source package in Zesty: Invalid Status in linux source package in Eoan: In Progress Bug description: The patch for bug 1158668 installs cpupower_$(abi_version) command- line tool as well as libcpupower.so.$(abi_version). This isn't particularly suitable for projects that previously used libcpufreq and intend to migrate to libcpupower, because the libcpupower.so symlink is no longer installed. The command-line tools can also have symlinks (e.g. cpupower -> cpupower_$(abi_version)). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1215411/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1884766] Re: use-after-free in af_alg_accept() due to bh_lock_sock()
** Description changed:
[Impact]
- * Users of the Linux kernel's crypto userspace API
-reported BUG() / kernel NULL pointer dereference
-errors after kernel upgrades.
+ * Users of the Linux kernel's crypto userspace API
+ reported BUG() / kernel NULL pointer dereference
+ errors after kernel upgrades.
- * The stack trace signature is an accept() syscall
-going through af_alg_accept() and hitting errors
-usually in one of:
-- apparmor_sk_clone_security()
-- apparmor_sock_graft()
-- release_sock()
+ * The stack trace signature is an accept() syscall
+ going through af_alg_accept() and hitting errors
+ usually in one of:
+ - apparmor_sk_clone_security()
+ - apparmor_sock_graft()
+ - release_sock()
[Fix]
-
- * This is a regression introduced by upstream commit
-37f96694cf73 ("crypto: af_alg - Use bh_lock_sock
-in sk_destruct") which made its way through stable.
-
- * The offending patch allows the critical regions
-of af_alg_accept() and af_alg_release_parent() to
-run concurrently; now with the "right" events on 2
-CPUs it might drop the non-atomic reference counter
-of the alg_sock then the sock, thus release a sock
-that is still in use.
- * The fix is upstream commit 34c86f4c4a7b ("crypto:
-af_alg - fix use-after-free in af_alg_accept() due
-to bh_lock_sock()") [1]. It changes alg_sock's ref
-counter to atomic, which addresses the root cause.
-
+ * This is a regression introduced by upstream commit
+ 37f96694cf73 ("crypto: af_alg - Use bh_lock_sock
+ in sk_destruct") which made its way through stable.
+
+ * The offending patch allows the critical regions
+ of af_alg_accept() and af_alg_release_parent() to
+ run concurrently; now with the "right" events on 2
+ CPUs it might drop the non-atomic reference counter
+ of the alg_sock then the sock, thus release a sock
+ that is still in use.
+
+ * The fix is upstream commit 34c86f4c4a7b ("crypto:
+ af_alg - fix use-after-free in af_alg_accept() due
+ to bh_lock_sock()") [1]. It changes alg_sock's ref
+ counter to atomic, which addresses the root cause.
+
[Test Case]
- * There is a synthetic test case available, which
-uses a kprobes kernel module to synchronize the
-concurrent CPUs on the instructions responsible
-for the problem; and a userspace part to run it.
+ * There is a synthetic test case available, which
+ uses a kprobes kernel module to synchronize the
+ concurrent CPUs on the instructions responsible
+ for the problem; and a userspace part to run it.
- * The organic reproducer is the Varnish Cache Plus
-software with the Crypto vmod (which uses kernel
-crypto userspace API) under long, very high load.
-
- * The patch has been verified on both reproducers
-with the 4.15 and 5.7 kernels.
-
+ * The organic reproducer is the Varnish Cache Plus
+ software with the Crypto vmod (which uses kernel
+ crypto userspace API) under long, very high load.
+
+ * The patch has been verified on both reproducers
+ with the 4.15 and 5.7 kernels.
+
* More tests performed with 'stress-ng --af-alg'
-with 11 CPUs/hogs on Bionic/Disco/Eoan/Focal
+with 11 CPUs on Xenial/Bionic/Disco/Eoan/Focal
(all on same version of stress-ng, V0.11.14)
+
No regressions observed from original kernel.
(the af-alg stressor can exercise almost all
kernel crypto modules shipped with the kernel;
so it checks more paths/crypto alg interfaces.)
-
+
[Regression Potential]
- * The fix patch does a fundamental change in how
-alg_sock reference counters work, plus another
-change to the 'nokey' counting. This of course
-*has* a risk of regression.
+ * The fix patch does a fundamental change in how
+ alg_sock reference counters work, plus another
+ change to the 'nokey' counting. This of course
+ *has* a risk of regression.
- * Regressions theoretically could manifest as use
-after free errors (in case of undercounting) in
-the af_alg functions or silent memory leaks (in
-case of overcounting), but also other behaviors
-since reference counting is key to many things.
-
- * FWIW, this patch has been written by the crypto
-subsystem maintainer, who certainly knows a lot
-of the normal and corner cases, thus giving the
-patch more credit.
-
- * Testing with the organic reproducer ran as long
-as 5 days, without issues, so it does look good.
+ * Regressions theoretically could manifest as use
+ after free errors (in case of undercounting) in
+ the af_alg functions or silent memory leaks (in
+ case of overcounting), but also other behaviors
+ since reference counting is key to many things.
+
+ * FWIW, this patch has been written by the crypto
+ subsystem maintainer, who certainly knows a lot
+ of the normal and corner cases, thus giving the
+ pat
[Kernel-packages] [Bug 1884766] Re: use-after-free in af_alg_accept() due to bh_lock_sock()
** Changed in: linux (Ubuntu Xenial)
Status: New => In Progress
** Changed in: linux (Ubuntu Xenial)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Xenial)
Assignee: (unassigned) => Mauricio Faria de Oliveira (mfo)
** Changed in: linux (Ubuntu Bionic)
Status: New => In Progress
** Changed in: linux (Ubuntu Bionic)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Bionic)
Assignee: (unassigned) => Mauricio Faria de Oliveira (mfo)
** Changed in: linux (Ubuntu Eoan)
Status: New => In Progress
** Changed in: linux (Ubuntu Eoan)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Eoan)
Assignee: (unassigned) => Mauricio Faria de Oliveira (mfo)
** Changed in: linux (Ubuntu Focal)
Status: New => In Progress
** Changed in: linux (Ubuntu Focal)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Focal)
Assignee: (unassigned) => Mauricio Faria de Oliveira (mfo)
** Changed in: linux (Ubuntu Groovy)
Status: Confirmed => Won't Fix
** Changed in: linux (Ubuntu Groovy)
Importance: Medium => Undecided
** Changed in: linux (Ubuntu Groovy)
Assignee: Mauricio Faria de Oliveira (mfo) => (unassigned)
** Changed in: linux (Ubuntu)
Status: Confirmed => In Progress
** Description changed:
[Impact]
* Users of the Linux kernel's crypto userspace API
reported BUG() / kernel NULL pointer dereference
errors after kernel upgrades.
* The stack trace signature is an accept() syscall
going through af_alg_accept() and hitting errors
usually in one of:
- apparmor_sk_clone_security()
- apparmor_sock_graft()
- release_sock()
[Fix]
* This is a regression introduced by upstream commit
37f96694cf73 ("crypto: af_alg - Use bh_lock_sock
in sk_destruct") which made its way through stable.
* The offending patch allows the critical regions
of af_alg_accept() and af_alg_release_parent() to
run concurrently; now with the "right" events on 2
CPUs it might drop the non-atomic reference counter
of the alg_sock then the sock, thus release a sock
that is still in use.
* The fix is upstream commit 34c86f4c4a7b ("crypto:
af_alg - fix use-after-free in af_alg_accept() due
to bh_lock_sock()") [1]. It changes alg_sock's ref
counter to atomic, which addresses the root cause.
[Test Case]
* There is a synthetic test case available, which
uses a kprobes kernel module to synchronize the
concurrent CPUs on the instructions responsible
for the problem; and a userspace part to run it.
* The organic reproducer is the Varnish Cache Plus
software with the Crypto vmod (which uses kernel
crypto userspace API) under long, very high load.
* The patch has been verified on both reproducers
with the 4.15 and 5.7 kernels.
- * More tests performed with 'stress-ng --af-alg'
-with 11 CPUs on Xenial/Bionic/Disco/Eoan/Focal
-(all on same version of stress-ng, V0.11.14)
+ * More tests performed with 'stress-ng --af-alg'
+ with 11 CPUs on Xenial/Bionic/Disco/Eoan/Focal
+ (all on same version of stress-ng, V0.11.14)
-No regressions observed from original kernel.
-(the af-alg stressor can exercise almost all
-kernel crypto modules shipped with the kernel;
-so it checks more paths/crypto alg interfaces.)
+ No regressions observed from original kernel.
+ (the af-alg stressor can exercise almost all
+ kernel crypto modules shipped with the kernel;
+ so it checks more paths/crypto alg interfaces.)
[Regression Potential]
* The fix patch does a fundamental change in how
alg_sock reference counters work, plus another
change to the 'nokey' counting. This of course
*has* a risk of regression.
* Regressions theoretically could manifest as use
after free errors (in case of undercounting) in
the af_alg functions or silent memory leaks (in
case of overcounting), but also other behaviors
since reference counting is key to many things.
* FWIW, this patch has been written by the crypto
subsystem maintainer, who certainly knows a lot
of the normal and corner cases, thus giving the
patch more credit.
* Testing with the organic reproducer ran as long
as 5 days, without issues, so it does look good.
[Other Info]
+
+ * Not sending for Groovy (should get via Unstable).
* [1] Patch:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=34c86f4c4a7be3b3e35aa48bd18299d4c756064d
[Stack Trace Examples]
Examples:
BUG: unable to handle kernel NULL pointer dereference at
...
RIP: 0010:apparmor_sk_clone_security+0x26/0x70
...
Call Trace:
security_sk_clone+0x33/0x50
af_alg_accept+0x81/0x1c0 [af_alg]
alg_accept+0x15/0x20 [af_alg]
SYSC_accept4+0xff/0x210
[Kernel-packages] [Bug 1884232] Re: touchpad doesn't work at all on ACER Spin 5
Sorry for delay, I'll look into it on Thursday I hope - just letting you know I'm still on it, just overwhelmed by work these days... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1884232 Title: touchpad doesn't work at all on ACER Spin 5 Status in linux package in Ubuntu: Confirmed Bug description: Touchpad is not working at all on ACER Spin 5 SP513-54N. According to https://wiki.ubuntu.com/DebuggingTouchpadDetection#In_case_your_Touchpad_doesn.27t_work_at_all_.28No_response_from_the_Touchpad.29 I am creating this kernel bug issue. There are more issues, too, like touchscreen not working and Ubuntu not installable - see here if interrested https://askubuntu.com/questions/1251719/ I would like to run Ubuntu on this machine and I am willing to help with any debug or kernel tweaking... Please let me know. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-26-generic 5.4.0-26.30 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 4195 F pulseaudio CasperMD5CheckResult: skip CasperVersion: 1.445 CurrentDesktop: ubuntu:GNOME Date: Fri Jun 19 10:44:58 2020 LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Acer Spin SP513-54N ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- RelatedPackageVersions: linux-restricted-modules-5.4.0-26-generic N/A linux-backports-modules-5.4.0-26-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/21/2020 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.00 dmi.board.name: Caboom_IL dmi.board.vendor: IL dmi.board.version: V1.00 dmi.chassis.type: 31 dmi.chassis.vendor: Acer dmi.chassis.version: V1.00 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.00:bd02/21/2020:svnAcer:pnSpinSP513-54N:pvrV1.00:rvnIL:rnCaboom_IL:rvrV1.00:cvnAcer:ct31:cvrV1.00: dmi.product.family: Spin 5 dmi.product.name: Spin SP513-54N dmi.product.sku: dmi.product.version: V1.00 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884232/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1215411] Re: libcpupower.so is not installed from linux-tools
During my +1 maintenance I looked at both gkrellm2-cpufreq and cpufreqd (ppc64el arch only) both of which are depwait in groovy because Ubuntu does not have a libcpupower-dev package. If Ubuntu isn't going to provide the libcpupower-dev package we should blacklist packages which depend on it so people doing +1 maintenance don't keep spending time on it. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1215411 Title: libcpupower.so is not installed from linux-tools Status in linux package in Ubuntu: In Progress Status in linux source package in Zesty: Invalid Status in linux source package in Eoan: In Progress Bug description: The patch for bug 1158668 installs cpupower_$(abi_version) command- line tool as well as libcpupower.so.$(abi_version). This isn't particularly suitable for projects that previously used libcpufreq and intend to migrate to libcpupower, because the libcpupower.so symlink is no longer installed. The command-line tools can also have symlinks (e.g. cpupower -> cpupower_$(abi_version)). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1215411/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1884288] Re: LapBook Pro touchpad (HTIX5288:00) sometimes does not work when machine is restarted
Yes, I understand you. Okay. As for the GRUB, as I was saying, I modify anything in this file, a simple line with # in front, or anything else simple, I update and TOUCHPAD works for me almost always ... Paranormal phenomena? :-). Let's hope someone enlightens us. In the meantime, and if I want to use TOUCHPAD, I have to do what I have said or work in a session with Windows. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1884288 Title: LapBook Pro touchpad (HTIX5288:00) sometimes does not work when machine is restarted Status in linux package in Ubuntu: Confirmed Bug description: Touchpad completely ceases to work sometimes upon startup / restart. When this happens, I have to plug in an external mouse to navigate as touchpad is not even recognised as a device when I use xinput command in terminal. I removed and reinstalled xserver-xorg-input-synaptics which may have got it working again, although I am not too sure. When the trackpad is working, it's device name is listed as HTIX5288:00 0911:5288 Touchpad. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jun 19 18:03:47 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics 605 [8086:3185] (rev 03) (prog-if 00 [VGA controller]) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0c45:6366 Microdia USB 2.0 Camera Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=c549aad1-cbca-42d0-abc5-e73556f0921b ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/29/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E.G140J.D8.E1.016.bin dmi.board.asset.tag: Default string dmi.board.name: Default string dmi.board.vendor: Default string dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE.G140J.D8.E1.016.bin:bd11/29/2019:svn:pnLapBookPro:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: LapBook Pro dmi.product.sku: Default string dmi.product.version: Default string version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ian1619 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0c45:6366 Microdia USB 2.0 Camera Bus 001 Device 008: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=c549aad1-cbca-42d0-abc5-e73556f0921b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.4.0-37-generic N/A linux-backports-modules-5.4.0-37-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-37-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 11/29/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E.G140J.D8.E1.0
[Kernel-packages] [Bug 1881120] Autopkgtest regression report (linux-oracle-5.4/5.4.0-1019.19~18.04.1)
All autopkgtests for the newly accepted linux-oracle-5.4 (5.4.0-1019.19~18.04.1) for bionic have finished running. The following regressions have been reported in tests triggered by the package: zfs-linux/unknown (armhf) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-oracle-5.4 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1881120 Title: linux-oem-5.6-tools-common and -tools-host should be dropped Status in linux package in Ubuntu: Invalid Status in linux-oem-5.6 package in Ubuntu: Confirmed Status in linux source package in Focal: Fix Committed Status in linux-oem-5.6 source package in Focal: Fix Committed Bug description: [Impact] linux-oem-5.6 built -tools-common and -tools-host, which conflict with the master kernel versions. These shouldn't be built at all. [Test case] Check that upgrade removes the oem versions. [Regression potential] shouldn't be any -- Updating 20.04, unaware of details package linux-oem-5.6-tools-common 5.6.0-1008.8 [modified: usr/share /bash-completion/completions/bpftool usr/share/man/man1/cpupower.1.gz usr/share/man/man1/perf-annotate.1.gz usr/share/man/man1/perf- archive.1.gz usr/share/man/man1/perf-bench.1.gz usr/share/man/man1 /perf-buildid-cache.1.gz usr/share/man/man1/perf-buildid-list.1.gz usr/share/man/man1/perf-c2c.1.gz usr/share/man/man1/perf-config.1.gz usr/share/man/man1/perf-data.1.gz usr/share/man/man1/perf-diff.1.gz usr/share/man/man1/perf-evlist.1.gz usr/share/man/man1/perf- ftrace.1.gz usr/share/man/man1/perf-help.1.gz usr/share/man/man1/perf- inject.1.gz usr/share/man/man1/perf-kallsyms.1.gz usr/share/man/man1 /perf-kmem.1.gz usr/share/man/man1/perf-kvm.1.gz usr/share/man/man1 /perf-list.1.gz usr/share/man/man1/perf-lock.1.gz usr/share/man/man1 /perf-mem.1.gz usr/share/man/man1/perf-probe.1.gz usr/share/man/man1 /perf-record.1.gz usr/share/man/man1/perf-report.1.gz usr/share/man/man1/perf-sched.1.gz usr/share/man/man1/perf-script- perl.1.gz usr/share/man/man1/perf-script-python.1.gz usr/share/man/man1/perf-script.1.gz usr/share/man/man1/perf-stat.1.gz usr/share/man/man1/perf-test.1.gz usr/share/man/man1/perf- timechart.1.gz usr/share/man/man1/perf-top.1.gz usr/share/man/man1 /perf-trace.1.gz usr/share/man/man1/perf-version.1.gz usr/share/man/man1/perf.1.gz usr/share/man/man8/bpftool-map.8.gz usr/share/man/man8/bpftool-prog.8.gz usr/share/man/man8/bpftool.8.gz] failed to install/upgrade: trying to overwrite '/usr/bin/acpidbg', which is also in package linux-tools-common 5.4.0-31.35 ProblemType: Package DistroRelease: Ubuntu 20.04 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu May 28 07:43:09 2020 ErrorMessage: trying to overwrite '/usr/bin/acpidbg', which is also in package linux-tools-common 5.4.0-31.35 InstallationDate: Installed on 2020-04-28 (29 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: linux-oem-5.6 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881120/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1883874] Autopkgtest regression report (linux-oracle-5.4/5.4.0-1019.19~18.04.1)
All autopkgtests for the newly accepted linux-oracle-5.4 (5.4.0-1019.19~18.04.1) for bionic have finished running. The following regressions have been reported in tests triggered by the package: zfs-linux/unknown (armhf) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-oracle-5.4 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1883874 Title: dkms-build: downloads fail in private PPAs Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: Fix Released Status in linux source package in Eoan: Fix Released Status in linux source package in Focal: Fix Released Bug description: We currently using apt-cache policy to obtain the local URLs this eliminates username and password data. We need the URLs intact in order to build in private PPAs. Switch URL source. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1883874/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1881576] Autopkgtest regression report (linux-oracle-5.4/5.4.0-1019.19~18.04.1)
All autopkgtests for the newly accepted linux-oracle-5.4 (5.4.0-1019.19~18.04.1) for bionic have finished running. The following regressions have been reported in tests triggered by the package: zfs-linux/unknown (armhf) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-oracle-5.4 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1881576 Title: seccomp_benchmark times out on eoan Status in ubuntu-kernel-tests: Invalid Status in linux package in Ubuntu: In Progress Status in linux source package in Eoan: Fix Committed Status in linux source package in Focal: Fix Committed Bug description: [Impact] seccomp selftests will timeout, causing the test to be detected as failure. [Fix] Set timeout to 90s. [Test case] Run sudo make run_tests under tools/testing/selftests/seccomp/. [Regression potential] Minimal, the test could still timeout, but by reading the code, it should take around 42s to 50s to execute in the worst cases, so 90s seem safe enough. == As it tries to calibrate how many samples will take more than 5 seconds to execute, it may end up picking up a number of samples that take 10 (but up to 12) seconds. As the calibration will take double that time, it takes around 20 seconds. Then, it executes the whole thing again, and then once more, with some added overhead. So, the thing might take more than 40 seconds, which is too close to the 45s timeout. So, it times out once in a while depending on the system. Using a timeout of 90 seconds should be safe enough for this test. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1881576/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1879321] Autopkgtest regression report (linux-oracle-5.4/5.4.0-1019.19~18.04.1)
All autopkgtests for the newly accepted linux-oracle-5.4 (5.4.0-1019.19~18.04.1) for bionic have finished running. The following regressions have been reported in tests triggered by the package: zfs-linux/unknown (armhf) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-oracle-5.4 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1879321 Title: Fix Pericom USB controller OHCI/EHCI PME# defect Status in HWE Next: New Status in linux package in Ubuntu: Invalid Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux-oem-osp1 package in Ubuntu: Fix Released Status in linux source package in Bionic: Won't Fix Status in linux-oem-5.6 source package in Bionic: Won't Fix Status in linux-oem-osp1 source package in Bionic: Fix Released Status in linux source package in Focal: Fix Committed Status in linux-oem-5.6 source package in Focal: Fix Released Status in linux-oem-osp1 source package in Focal: Won't Fix Bug description: [Impact] Pericom EHCI/OHCI USB Controller can't detect hotplug event when it's runtime-suspended, due to its unreliable PME#. [Fix] Disable PME for all its power state since all of them don't work reliably. [Test] Hotplugging event can be reliably detected by the device, after the fix gets applied. [Regression Potentia] Low. This targets specific device, without touching any logic. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1879321/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1881927] Autopkgtest regression report (linux-oracle-5.4/5.4.0-1019.19~18.04.1)
All autopkgtests for the newly accepted linux-oracle-5.4 (5.4.0-1019.19~18.04.1) for bionic have finished running. The following regressions have been reported in tests triggered by the package: zfs-linux/unknown (armhf) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-oracle-5.4 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1881927 Title: Focal update: v5.4.44 upstream stable release Status in linux package in Ubuntu: Confirmed Status in linux source package in Focal: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.4.44 upstream stable release from git://git.kernel.org/ ax25: fix setsockopt(SO_BINDTODEVICE) dpaa_eth: fix usage as DSA master, try 3 net: don't return invalid table id error when we fall back to PF_UNSPEC net: dsa: mt7530: fix roaming from DSA user ports net: ethernet: ti: cpsw: fix ASSERT_RTNL() warning during suspend __netif_receive_skb_core: pass skb by reference net: inet_csk: Fix so_reuseport bind-address cache in tb->fast* net: ipip: fix wrong address family in init error path net/mlx5: Add command entry handling completion net: mvpp2: fix RX hashing for non-10G ports net: nlmsg_cancel() if put fails for nhmsg net: qrtr: Fix passing invalid reference to qrtr_local_enqueue() net: revert "net: get rid of an signed integer overflow in ip_idents_reserve()" net sched: fix reporting the first-time use timestamp net/tls: fix race condition causing kernel panic nexthop: Fix attribute checking for groups r8152: support additional Microsoft Surface Ethernet Adapter variant sctp: Don't add the shutdown timer if its already been added sctp: Start shutdown on association restart if in SHUTDOWN-SENT state and socket is closed tipc: block BH before using dst_cache net/mlx5e: kTLS, Destroy key object after destroying the TIS net/mlx5e: Fix inner tirs handling net/mlx5: Fix memory leak in mlx5_events_init net/mlx5e: Update netdev txq on completions during closure net/mlx5: Fix error flow in case of function_setup failure net/mlx5: Annotate mutex destroy for root ns net/tls: fix encryption error checking net/tls: free record only on encryption error net: sun: fix missing release regions in cas_init_one(). net/mlx4_core: fix a memory leak bug. mlxsw: spectrum: Fix use-after-free of split/unsplit/type_set in case reload fails ARM: dts: rockchip: fix phy nodename for rk3228-evb ARM: dts: rockchip: fix phy nodename for rk3229-xms6 arm64: dts: rockchip: fix status for &gmac2phy in rk3328-evb.dts arm64: dts: rockchip: swap interrupts interrupt-names rk3399 gpu node ARM: dts: rockchip: swap clock-names of gpu nodes ARM: dts: rockchip: fix pinctrl sub nodename for spi in rk322x.dtsi gpio: tegra: mask GPIO IRQs during IRQ shutdown ALSA: usb-audio: add mapping for ASRock TRX40 Creator net: microchip: encx24j600: add missed kthread_stop gfs2: move privileged user check to gfs2_quota_lock_check gfs2: Grab glock reference sooner in gfs2_add_revoke drm/amdgpu: drop unnecessary cancel_delayed_work_sync on PG ungate drm/amd/powerplay: perform PG ungate prior to CG ungate drm/amdgpu: Use GEM obj reference for KFD BOs cachefiles: Fix race between read_waiter and read_copier involving op->to_do usb: dwc3: pci: Enable extcon driver for Intel Merrifield usb: phy: twl6030-usb: Fix a resource leak in an error handling path in 'twl6030_usb_probe()' usb: gadget: legacy: fix redundant initialization warnings net: freescale: select CONFIG_FIXED_PHY where needed IB/i40iw: Remove bogus call to netdev_master_upper_dev_get() riscv: stacktrace: Fix undefined reference to `walk_stackframe' clk: ti: am33xx: fix RTC clock parent csky: Fixup msa highest 3 bits mask csky: Fixup perf callchain unwind csky: Fixup remove duplicate irq_disable hwmon: (nct7904) Fix incorrect range of temperature limit registers cifs: Fix null pointer check in cifs_read csky: Fixup raw_copy_from_user() samples: bpf: Fix build error drivers: net: hamradio: Fix suspicious RCU usage warning in bpqether.c Input: usbtouchscreen - add support for BonXeon TP
[Kernel-packages] [Bug 1878897] Autopkgtest regression report (linux-oracle-5.4/5.4.0-1019.19~18.04.1)
All autopkgtests for the newly accepted linux-oracle-5.4 (5.4.0-1019.19~18.04.1) for bionic have finished running. The following regressions have been reported in tests triggered by the package: zfs-linux/unknown (armhf) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-oracle-5.4 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1878897 Title: debian/scripts/file-downloader does not handle positive failures correctly Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: Fix Released Status in linux source package in Eoan: Fix Released Status in linux source package in Focal: Fix Released Status in linux source package in Groovy: In Progress Bug description: Somehow we are not really correctly handling positive failures, 404 for example. Sigh. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1878897/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1879704] Autopkgtest regression report (linux-oracle-5.4/5.4.0-1019.19~18.04.1)
All autopkgtests for the newly accepted linux-oracle-5.4
(5.4.0-1019.19~18.04.1) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:
zfs-linux/unknown (armhf)
Please visit the excuses page listed below and investigate the failures,
proceeding afterwards as per the StableReleaseUpdates policy regarding
autopkgtest regressions [1].
https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#linux-oracle-5.4
[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions
Thank you!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1879704
Title:
[UBUNTU 20.04] s390x/pci: fix linking between PF and VF for
multifunction devices
Status in Ubuntu on IBM z Systems:
Fix Committed
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Focal:
Fix Committed
Status in linux source package in Groovy:
In Progress
Bug description:
SRU Justification:
==
[Impact]
* It's currently not possible on s390x to verify the relationships
between PFs and VFs of network interfaces (neither natively nor in
libvirt).
* So s390x currently behaves differently here compared to other
architectures, but shouldn't, since this is needed for proper
management.
* The creation of not only the sysfs, but also the in-kernel link
(struct pci_dev->physfn), solves this and on top allows the use of a
common code path for disabling/shutdown of PFs.
* This code path is right now fenced off by the struct
pci_dev->no_vf_scan flag of which s390x is currently the only user.
* This allows to gracefully and orderly shutdown VFs associated with a
PF as triggered by '/sys/bus/pci/devices//sriov_numvfs'
* Previously this could leave the card in an unresponsive error state.
[Fix]
* a1ceea67f2e5b73cebd456e7fb463b3052bc6344 a1ceea67f2e5 "PCI/IOV:
Introduce pci_iov_sysfs_link() function"
* e5794cf1a270d813a5b9373a6876487d4d154195 e5794cf1a270 "s390/pci:
create links between PFs and VFs"
[Test Case]
* Setup an s390x LPAR with at least one SR-IOV card and assign PF and
VFs to that system.
* Determine if a device is a virtual function: for other architectures
this is currently available in the file 'physfn' which is a link to
the parent PF's device.
* Determine virtual functions of a physical function: for other
architectures this is currently available as 'virtfn{index}' links
under the PF device's directory.
* Determine the physical function of a virtual function: on x86 this
is currently available in the file 'physfn' which is a link to the
parent PF.
* This verification needs to be done by IBM on a system with SR-IOV
(PCI-based) hardware.
[Regression Potential]
* There is a certain regression risk with having code changes in the PCI/IOV
space,
even is they are limited, especially is the patches touche common code.
* The changes in pci.h are very minimal, and the iov.c changes are
traceable, too. All other modifications are s390x specific.
* Nevertheless, it could be that PCI hardware get harmed, here
especially (SR-)IOV hardware.
* The patches got cross-company verified (IBM and Google).
* They were brought upstream and are currently tagged with 20200521,
and are planned to be included in 5.8.
* A patched kernel was created based on a LP PPA and successfully
tested by IBM.
[Other]
* Since the fix/patch is planned to be included in kernel v5.8, it
will later automatically land in groovy.
* But because groovy is not there yet (5.8 is not yet out), this SRU
got requested for focal and groovy.
* This SRU depends on the SRU from LP 1874056, and this has already two ACKs.
So LP 1874056 needs to be applied before this one!
__
As with other architectures, we must be able on s390x to verify the
following relationships between PFs and VFs for proper management
(including by libvirt) of network interfaces:
1. Determine if a device is a virtual function: for other architectures this
is currently available in the file `physfn` which is a link to the parent PF's
device.
2. Determine virtual functions of a physical function: for other
architectures this is currently available as `virtfn{index}` links under the PF
device's directory.
3. Determine the physical function of a virtual function: on x86 this is
currently available in the file `physfn` which is a link to the parent PF
More details for the already existing parameters mentioned above can
be found here: https://www.kernel.org/doc/Documentation/ABI/testing
/sysfs-bus-pci
Moreover creating not just the sysfs but also the in-kernel link
(struct pci_dev->physfn) also allows us to use the common code path
for disabling/shutdown of PFs.
This code path is currently fenced off b
[Kernel-packages] [Bug 1881710] Autopkgtest regression report (linux-oracle-5.4/5.4.0-1019.19~18.04.1)
All autopkgtests for the newly accepted linux-oracle-5.4
(5.4.0-1019.19~18.04.1) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:
zfs-linux/unknown (armhf)
Please visit the excuses page listed below and investigate the failures,
proceeding afterwards as per the StableReleaseUpdates policy regarding
autopkgtest regressions [1].
https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#linux-oracle-5.4
[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions
Thank you!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1881710
Title:
tpm: fix TIS locality timeout problems
Status in linux package in Ubuntu:
Invalid
Status in linux-oem-5.6 package in Ubuntu:
Invalid
Status in linux-oem-osp1 package in Ubuntu:
Invalid
Status in linux-oem-osp1 source package in Bionic:
Fix Committed
Status in linux source package in Focal:
Fix Committed
Status in linux-oem-5.6 source package in Focal:
Fix Committed
Bug description:
[Impact]
It has been reported that some TIS based TPMs are giving unexpected errors
when using the O_NONBLOCK path of the TPM device. The problem is that some TPMs
don't like it when you get and then relinquish a locality (as the
tpm_try_get_ops()/tpm_put_ops() pair does) without sending a command. This
currently happens all the time in the O_NONBLOCK write path. This affects
Nuvoton TPMs and was a regression caused by the patch d23d12484307 ("tpm: fix
invalid locking in NONBLOCKING mode").
PatchLink: https://patchwork.kernel.org/patch/11576453/
[Fix]
Fix this by moving the tpm_try_get_ops()
further down the code to after the O_NONBLOCK determination is made.
This is safe because the priv->buffer_mutex still protects the priv
state being modified.
[Regression Risk]
Low. This patch only for fix the patch d23d12484307 ("tpm: fix invalid
locking in NONBLOCKING mode").
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881710/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1879690] Autopkgtest regression report (linux-oracle-5.4/5.4.0-1019.19~18.04.1)
All autopkgtests for the newly accepted linux-oracle-5.4 (5.4.0-1019.19~18.04.1) for bionic have finished running. The following regressions have been reported in tests triggered by the package: zfs-linux/unknown (armhf) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-oracle-5.4 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1879690 Title: Docker registry doesn't stay up and keeps restarting Status in linux package in Ubuntu: Incomplete Status in linux source package in Eoan: Fix Released Status in linux source package in Focal: Fix Released Bug description: [Impact] The change applied for bug 1857257 and its followup fix bug 1876645, which were released on focal and eoan -updates, introduced a regression on overlayfs, breaking docker snap. [Test case] See original bug report. [Fix] While we don't have a final fix the solution for now is to revert the following commits: UBUNTU: SAUCE: overlayfs: fix shitfs special-casing UBUNTU: SAUCE: overlayfs: use shiftfs hacks only with shiftfs as underlay [Regression potential] Low. Reverting these two commits will introduce back the issue reported on bug 1857257, but will fix the other use cases which was broken by the latest release. Original bug report. --- Tested kernels: Focal 5.4.0-31.35 Eoan 5.3.0-53.47 To reproduce: 1) Spin up a cloud image 2) snap install docker 3) auth_folder=/var/snap/docker/common/auth 4) mkdir -p $auth_folder 5) docker run --entrypoint htpasswd registry:2 -Bbn user passwd > $auth_folder/htpasswd 6) docker run -d -p 5000:5000 --restart=always --name registry \ -v $auth_folder:/auth \ -e "REGISTRY_AUTH=htpasswd" \ -e "REGISTRY_AUTH_HTPASSWD_REALM=Registry Realm" \ -e REGISTRY_AUTH_HTPASSWD_PATH=/auth/htpasswd \ registry:2 On a good kernel 'docker ps' shows something like: # docker ps CONTAINER IDIMAGE COMMAND CREATED STATUS PORTSNAMES a346b65b4509registry:2 "/entrypoint.sh /etc…" 14 seconds ago Up 12 seconds 0.0.0.0:5000->5000/tcp registry On a bad kernel: docker ps CONTAINER IDIMAGE COMMAND CREATED STATUSPORTS NAMES 0322374f1b1dregistry:2 "/entrypoint.sh /etc…" 5 seconds ago Restarting (2) 1 second ago registry Note status 'Restarting' on the bad kernel. This seems to be introduce by any of the following commits: b3bdda24f1bc UBUNTU: SAUCE: overlayfs: fix shitfs special-casing 6f18a8434050 UBUNTU: SAUCE: overlayfs: use shiftfs hacks only with shiftfs as underlay 629edd70891c UBUNTU: SAUCE: shiftfs: record correct creator credentials cfaa482afb97 UBUNTU: SAUCE: shiftfs: fix dentry revalidation Kernels that don't have these commits seem fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879690/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1879327] Autopkgtest regression report (linux-oracle-5.4/5.4.0-1019.19~18.04.1)
All autopkgtests for the newly accepted linux-oracle-5.4 (5.4.0-1019.19~18.04.1) for bionic have finished running. The following regressions have been reported in tests triggered by the package: zfs-linux/unknown (armhf) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-oracle-5.4 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1879327 Title: Enforce all config annotations Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: Confirmed Status in linux source package in Bionic: Confirmed Status in linux source package in Eoan: Confirmed Status in linux source package in Focal: Fix Committed Status in linux source package in Groovy: In Progress Bug description: [Impact] Not all config annotations are enforced, which means config could regress without notice. [Test case] Check the logs mention much more options being enforced. From the hundreds to more than 1. [Regression potential] Builds will start failing when config doesn't match annotations. However, this is an opt-in for now, which means only those branches prepared to accept it will risk such regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879327/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1881046] Autopkgtest regression report (linux-oracle-5.4/5.4.0-1019.19~18.04.1)
All autopkgtests for the newly accepted linux-oracle-5.4 (5.4.0-1019.19~18.04.1) for bionic have finished running. The following regressions have been reported in tests triggered by the package: zfs-linux/unknown (armhf) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-oracle-5.4 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1881046 Title: ASoC/amd: add audio driver for amd renoir Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.6 package in Ubuntu: New Status in linux source package in Focal: Fix Committed Status in linux-oem-5.6 source package in Focal: Fix Committed Status in linux source package in Groovy: Incomplete Bug description: This patchset is for mainline kernel-5.8, after backporting to 5.6, there is no need to change anything, but after backporting to 5.4 kernel, because of API differences, need to do some change to adapt to 5.4 kernel's API. So there is one more patch for focal than for oem-5.6. [Impact] We have a couple of LENOVO machines which has amd renoir audio on them, our kernel doesn't have the driver for it yet. [Fix] amd just upstreamed the driver, it is for kernel-5.8, we backport them to ubunt kernel. [Test Case] boot the kernel with those patches, we could see a sound card named "acp" and the dmic on it could record sound via arecord. [Regression Risk] Low, just adding a new driver, no change to existing drivers. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1881046/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1881178] Autopkgtest regression report (linux-oracle-5.4/5.4.0-1019.19~18.04.1)
All autopkgtests for the newly accepted linux-oracle-5.4 (5.4.0-1019.19~18.04.1) for bionic have finished running. The following regressions have been reported in tests triggered by the package: zfs-linux/unknown (armhf) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-oracle-5.4 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1881178 Title: Focal update: v5.4.43 upstream stable release Status in linux package in Ubuntu: Confirmed Status in linux source package in Focal: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.4.43 upstream stable release from git://git.kernel.org/ i2c: dev: Fix the race between the release of i2c_dev and cdev KVM: SVM: Fix potential memory leak in svm_cpu_init() ima: Set file->f_mode instead of file->f_flags in ima_calc_file_hash() evm: Check also if *tfm is an error pointer in init_desc() ima: Fix return value of ima_write_policy() ubifs: fix wrong use of crypto_shash_descsize() ACPI: EC: PM: Avoid flushing EC work when EC GPE is inactive mtd: spinand: Propagate ECC information to the MTD structure fix multiplication overflow in copy_fdtable() ubifs: remove broken lazytime support i2c: fix missing pm_runtime_put_sync in i2c_device_probe iommu/amd: Fix over-read of ACPI UID from IVRS table evm: Fix a small race in init_desc() i2c: mux: demux-pinctrl: Fix an error handling path in 'i2c_demux_pinctrl_probe()' ubi: Fix seq_file usage in detailed_erase_block_info debugfs file afs: Don't unlock fetched data pages until the op completes successfully mtd: Fix mtd not registered due to nvmem name collision kbuild: avoid concurrency issue in parallel building dtbs and dtbs_check net: drop_monitor: use IS_REACHABLE() to guard net_dm_hw_report() gcc-common.h: Update for GCC 10 HID: multitouch: add eGalaxTouch P80H84 support HID: alps: Add AUI1657 device ID HID: alps: ALPS_1657 is too specific; use U1_UNICORN_LEGACY instead scsi: qla2xxx: Fix hang when issuing nvme disconnect-all in NPIV scsi: qla2xxx: Delete all sessions before unregister local nvme port configfs: fix config_item refcnt leak in configfs_rmdir() vhost/vsock: fix packet delivery order to monitoring devices aquantia: Fix the media type of AQC100 ethernet controller in the driver component: Silence bind error on -EPROBE_DEFER net/ena: Fix build warning in ena_xdp_set() scsi: ibmvscsi: Fix WARN_ON during event pool release HID: i2c-hid: reset Synaptics SYNA2393 on resume x86/mm/cpa: Flush direct map alias during cpa ibmvnic: Skip fatal error reset after passive init x86/apic: Move TSC deadline timer debug printk gtp: set NLM_F_MULTI flag in gtp_genl_dump_pdp() HID: quirks: Add HID_QUIRK_NO_INIT_REPORTS quirk for Dell K12A keyboard-dock ceph: fix double unlock in handle_cap_export() stmmac: fix pointer check after utilization in stmmac_interrupt USB: core: Fix misleading driver bug report platform/x86: asus-nb-wmi: Do not load on Asus T100TA and T200TA iommu/amd: Call domain_flush_complete() in update_domain() drm/amd/display: Prevent dpcd reads with passive dongles KVM: selftests: Fix build for evmcs.h ARM: futex: Address build warning scripts/gdb: repair rb_first() and rb_last() ALSA: hda - constify and cleanup static NodeID tables ALSA: hda: patch_realtek: fix empty macro usage in if block ALSA: hda: Manage concurrent reg access more properly ALSA: hda/realtek - Add supported new mute Led for HP ALSA: hda/realtek - Add HP new mute led supported for ALC236 ALSA: hda/realtek: Add quirk for Samsung Notebook ALSA: hda/realtek - Enable headset mic of ASUS GL503VM with ALC295 ALSA: hda/realtek - Enable headset mic of ASUS UX550GE with ALC295 ALSA: hda/realtek: Enable headset mic of ASUS UX581LV with ALC295 KVM: x86: Fix pkru save/restore when guest CR4.PKE=0, move it to x86.c ALSA: iec1712: Initialize STDSP24 properly when using the model=staudio option ALSA: pcm: fix incorrect hw_base increase ALSA: hda/realtek - Fix silent output on Gigabyte X570 Aorus Xtreme ALSA: hda/realtek - Add more fixup entries for Clevo machines scsi: q
[Kernel-packages] [Bug 1880656] Autopkgtest regression report (linux-oracle-5.4/5.4.0-1019.19~18.04.1)
All autopkgtests for the newly accepted linux-oracle-5.4 (5.4.0-1019.19~18.04.1) for bionic have finished running. The following regressions have been reported in tests triggered by the package: zfs-linux/unknown (armhf) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-oracle-5.4 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1880656 Title: Fix incorrect speed/duplex when I210 device is runtime suspended Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.6 package in Ubuntu: New Status in linux-oem-osp1 package in Ubuntu: New Status in linux source package in Bionic: Invalid Status in linux-oem-5.6 source package in Bionic: Won't Fix Status in linux-oem-osp1 source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux-oem-5.6 source package in Focal: Fix Committed Status in linux-oem-osp1 source package in Focal: Won't Fix Bug description: [Impact] When I210 device is runtime suspended, trying to read speed or duplex from sysfs causes an error: [ 385.991957] igb :03:00.0 enp3s0: PCIe link lost [Fix] Only try to read the device register when it's not runtime suspended. [Test] Without the fix: $ cat /sys/class/net/enp3s0/speed 1000 With the fix: $ cat /sys/class/net/enp3s0/speed -1 -1 means "unknown speed", which is the correct status when device is runtime suspend. [Regression Potential] Low. It's a trivial fix which limits to one driver. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1880656/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1880660] Autopkgtest regression report (linux-oracle-5.4/5.4.0-1019.19~18.04.1)
All autopkgtests for the newly accepted linux-oracle-5.4
(5.4.0-1019.19~18.04.1) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:
zfs-linux/unknown (armhf)
Please visit the excuses page listed below and investigate the failures,
proceeding afterwards as per the StableReleaseUpdates policy regarding
autopkgtest regressions [1].
https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#linux-oracle-5.4
[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions
Thank you!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1880660
Title:
security: lockdown: remove trailing semicolon before function body
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Focal:
Fix Committed
Status in linux source package in Groovy:
Confirmed
Bug description:
[Impact]
In focal commit 40fc208c8aae ("UBUNTU: SAUCE: (lockdown) security:
lockdown: expose a hook to lock the kernel down") adds an inline
function with a trailing semicolon before the function body, that can
potentially cause build errors.
[Test case]
Build anything that includes linux/security.h and check for
warnings/errors.
[Fix]
Fix by removing the trailing semicolon.
[Regression potential]
The problem is an obvious syntax error, fix is trivial, so regression
potential is minimal.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1880660/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1879759] Autopkgtest regression report (linux-oracle-5.4/5.4.0-1019.19~18.04.1)
All autopkgtests for the newly accepted linux-oracle-5.4
(5.4.0-1019.19~18.04.1) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:
zfs-linux/unknown (armhf)
Please visit the excuses page listed below and investigate the failures,
proceeding afterwards as per the StableReleaseUpdates policy regarding
autopkgtest regressions [1].
https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#linux-oracle-5.4
[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions
Thank you!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1879759
Title:
Focal update: v5.4.42 upstream stable release
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Focal:
Fix Committed
Bug description:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from a mainline/stable Linux tree or
a minimally backported form of that patch. The following upstream
stable patches should be included in the Ubuntu kernel:
v5.4.42 upstream stable release
from git://git.kernel.org/
net: dsa: Do not make user port errors fatal
shmem: fix possible deadlocks on shmlock_user_lock
net: phy: microchip_t1: add lan87xx_phy_init to initialize the lan87xx phy.
KVM: arm: vgic: Synchronize the whole guest on GIC{D,R}_I{S,C}ACTIVER read
gpio: pca953x: Fix pca953x_gpio_set_config
SUNRPC: Add "@len" parameter to gss_unwrap()
SUNRPC: Fix GSS privacy computation of auth->au_ralign
net/sonic: Fix a resource leak in an error handling path in
'jazz_sonic_probe()'
net: moxa: Fix a potential double 'free_irq()'
ftrace/selftests: workaround cgroup RT scheduling issues
drop_monitor: work around gcc-10 stringop-overflow warning
virtio-blk: handle block_device_operations callbacks after hot unplug
sun6i: dsi: fix gcc-4.8
net_sched: fix tcm_parent in tc filter dump
scsi: sg: add sg_remove_request in sg_write
mmc: sdhci-acpi: Add SDHCI_QUIRK2_BROKEN_64_BIT_DMA for AMDI0040
dpaa2-eth: properly handle buffer size restrictions
net: fix a potential recursive NETDEV_FEAT_CHANGE
netlabel: cope with NULL catmap
net: phy: fix aneg restart in phy_ethtool_set_eee
net: stmmac: fix num_por initialization
pppoe: only process PADT targeted at local interfaces
Revert "ipv6: add mtu lock check in __ip6_rt_update_pmtu"
tcp: fix error recovery in tcp_zerocopy_receive()
tcp: fix SO_RCVLOWAT hangs with fat skbs
virtio_net: fix lockdep warning on 32 bit
dpaa2-eth: prevent array underflow in update_cls_rule()
hinic: fix a bug of ndo_stop
net: dsa: loop: Add module soft dependency
net: ipv4: really enforce backoff for redirects
netprio_cgroup: Fix unlimited memory leak of v2 cgroups
net: tcp: fix rx timestamp behavior for tcp_recvmsg
nfp: abm: fix error return code in nfp_abm_vnic_alloc()
r8169: re-establish support for RTL8401 chip version
umh: fix memory leak on execve failure
riscv: fix vdso build with lld
dmaengine: pch_dma.c: Avoid data race between probe and irq handler
dmaengine: mmp_tdma: Do not ignore slave config validation errors
dmaengine: mmp_tdma: Reset channel error on release
selftests/ftrace: Check the first record for kprobe_args_type.tc
cpufreq: intel_pstate: Only mention the BIOS disabling turbo mode once
ALSA: hda/hdmi: fix race in monitor detection during probe
drm/amd/powerplay: avoid using pm_en before it is initialized revised
drm/amd/display: check if REFCLK_CNTL register is present
drm/amd/display: Update downspread percent to match spreadsheet for DCN2.1
drm/qxl: lost qxl_bo_kunmap_atomic_page in qxl_image_init_helper()
drm/amdgpu: simplify padding calculations (v2)
drm/amdgpu: invalidate L2 before SDMA IBs (v2)
ipc/util.c: sysvipc_find_ipc() incorrectly updates position index
ALSA: hda/realtek - Fix S3 pop noise on Dell Wyse
gfs2: Another gfs2_walk_metadata fix
mmc: sdhci-pci-gli: Fix no irq handler from suspend
IB/hfi1: Fix another case where pq is left on waitlist
ACPI: EC: PM: Avoid premature returns from acpi_s2idle_wake()
pinctrl: sunrisepoint: Fix PAD lock register offset for SPT-H
pinctrl: baytrail: Enable pin configuration setting for GPIO chip
pinctrl: qcom: fix wrong write in update_dual_edge
pinctrl: cherryview: Add missing spinlock usage in chv_gpio_irq_handler
bpf: Fix error return code in map_lookup_and_delete_elem()
ALSA: firewire-lib: fix 'function sizeof not defined' error of tracepoints
format
i40iw: Fix error handling in i40iw_manage_arp_cache()
drm/i915: Don't enable WaIncreaseLatencyIPCEnabled when IPC is dis
[Kernel-packages] [Bug 1879688] Autopkgtest regression report (linux-oracle-5.4/5.4.0-1019.19~18.04.1)
All autopkgtests for the newly accepted linux-oracle-5.4 (5.4.0-1019.19~18.04.1) for bionic have finished running. The following regressions have been reported in tests triggered by the package: zfs-linux/unknown (armhf) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-oracle-5.4 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1879688 Title: shiftfs: fix btrfs snapshot deletion Status in linux package in Ubuntu: Confirmed Status in linux source package in Eoan: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Groovy: Confirmed Bug description: SRU Justification Impact: Stéphane discovered a problem during NorthSec which makes heavy use of shiftfs. In containers with a btrfs root filesystem that make use of shiftfs userns root is not able to delete subvolumes that have been created by another users which it would be able to do otherwise. This makes it impossible for LXD to delete nested containers. To reproduce this as root in the container: btrfs subvolume create my-subvol chown 1000:1000 my-subvol btrfs subvolume delete my-subvol The deletion will fail when it should have succeeded. Fix: For improved security we drop all capabilities before we forward btrfs ioctls in shiftfs. To fix the above problem we can retain the CAP_DAC_OVERRIDE capability only if we are userns root. Regression Potential: Limited to shiftfs. Even though we drop all capabilities in all capability sets we really mostly care about dropping CAP_SYS_ADMIN and we mostly do this for ioctl that e.g. allow you to traverse the btrfs filesystem and with CAP_SYS_ADMIN retained in the underlay would allow you to list subvolumes you shouldn't be able to list. This fix only retains CAP_DAC_OVERRIDE and only for the deletion of subvolumes and only by userns root. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879688/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1877955] Autopkgtest regression report (linux-oracle-5.4/5.4.0-1019.19~18.04.1)
All autopkgtests for the newly accepted linux-oracle-5.4
(5.4.0-1019.19~18.04.1) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:
zfs-linux/unknown (armhf)
Please visit the excuses page listed below and investigate the failures,
proceeding afterwards as per the StableReleaseUpdates policy regarding
autopkgtest regressions [1].
https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#linux-oracle-5.4
[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions
Thank you!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1877955
Title:
Fix for secure boot rules in IMA arch policy on powerpc
Status in The Ubuntu-power-systems project:
Fix Committed
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Focal:
Fix Committed
Status in linux source package in Groovy:
In Progress
Bug description:
SRU Justification:
==
[Impact]
* Currently the kernel module appended signature is verified twice
(finit_module) - once by the module_sig_check() and again by IMA.
* To prevent this the powerpc secure boot rules define an IMA
architecture specific policy rule only if CONFIG_MODULE_SIG_FORCE is
not enabled.
* But this doesn't take the ability into account of enabling
"sig_enforce" at the boot command line (module.sig_enforce=1).
* Including the IMA module appraise rule results in failing the
finit_module syscall, unless the module signing public key is loaded
onto the IMA keyring.
* This patch fixes secure boot policy rules to be based on
CONFIG_MODULE_SIG instead.
[Fix]
* fa4f3f56ccd28ac031ab275e673ed4098855fed4 fa4f3f56ccd2 "powerpc/ima:
Fix secure boot rules in ima arch policy"
[Test Case]
* Perform a secure boot on a powerpc system with
'module.sig_enforce=1' set at the boot command.
* If the IMA module appraise rule is included, the finit_module
syscall will fail (unless the module signing public key got loaded
onto the IMA keyring) without having the patch in place.
* The verification needs to be done by the IBM Power team.
[Regression Potential]
* There is (always) a certain regression risk with having code
changes, especially in the secure boot area.
* But this patch is limited to the powerpc platform and will not
affect any other architecture.
* It got discussed at
https://lore.kernel.org/r/1588342612-14532-1-git-send-email-na...@linux.ibm.com
before it became finally upstream accepted with kernel 5.7-rc7.
* The secure boot code itself wasn't really touched, rather than it's basis
for execution.
The IMA policy rule for module appraisal is now added only if
'CONFIG_MODULE_SIG' is not enabled (instead of CONFIG_MODULE_SIG_FORCE).
Hence the change is very limited and straightforward.
[Other]
* Since the patch got upstream with 5.7-rc7, it is already in groovy, hence
this SRU is for focal only.
__
== Comment: #0 - Michael Ranweiler - 2020-04-22
14:44:31 ==
+++ This bug was initially created as a clone of Bug #184073 +++
This bug is a follow on to LP 1866909 to address a missing piece -
only half the following patch was included in 5.4.0-24.28.
The upstream patch has an additional fix but it?s not critical for GA.
It can get included as part of bug fixes. It also affects only power.
The patch("powerpc/ima: fix secure boot rules in ima arch policy") is
posted to linux-integrity and linuxppc-dev mailing list
(https://lore.kernel.org/linux-integrity/1586549618-6106-1-git-send-
email-na...@linux.ibm.com/T/#u)
If there are any issues identified during further testing, they will
get opened as separate issue to be addressed later.
Thanks & Regards,
- Nayna
== Comment: #4 - Michael Ranweiler - 2020-05-11
02:23:35 ==
Updated posting:
https://lore.kernel.org/linux-integrity/1588342612-14532-1-git-send-
email-na...@linux.ibm.com/T/#u
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1877955/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1878147] Autopkgtest regression report (linux-oracle-5.4/5.4.0-1019.19~18.04.1)
All autopkgtests for the newly accepted linux-oracle-5.4 (5.4.0-1019.19~18.04.1) for bionic have finished running. The following regressions have been reported in tests triggered by the package: zfs-linux/unknown (armhf) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-oracle-5.4 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1878147 Title: Realtek 8723DE [10ec:d723] subsystem [10ec:d738] disconnects unsolicitedly when Bluetooth is paired: Reason: 23=IEEE8021X_FAILED Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux-oem-osp1 package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Status in linux-oem-5.6 source package in Bionic: Invalid Status in linux-oem-osp1 source package in Bionic: Fix Committed Status in linux source package in Eoan: Invalid Status in linux-oem-5.6 source package in Eoan: Invalid Status in linux-oem-osp1 source package in Eoan: Invalid Status in linux source package in Focal: Fix Committed Status in linux-oem-5.6 source package in Focal: Fix Committed Status in linux-oem-osp1 source package in Focal: Invalid Status in linux source package in Groovy: In Progress Status in linux-oem-5.6 source package in Groovy: Invalid Status in linux-oem-osp1 source package in Groovy: Invalid Bug description: [SRU Justification] [Impact] Existing Wi-Fi connection may be deauthenticated unsolicitedly with reason 23=IEEE8021X_FAILED when the system is also paired with a Bluetooth device. A WLAN passphrase dialog propmpts, and system disconnects from network: wlp5s0: deauthenticated from a4:56:30:cc:0f:30 (Reason: 23=IEEE8021X_FAILED). [Fix] Realtek proposed a fix[1] to linux-wireless consisting of three patches. rtw88: coex: 8723d: set antanna control owner rtw88: coex: 8723d: handle BT inquiry cases rtw88: fix EAPOL 4-way failure by finish IQK earlier The third one actually duplicates the fix we have for bug 1871300 also from Realtek and was claimed critical to this issue, therefore those for bug 1871300 are reverted in favor of the new one. Also revert that Ubuntu sauced "rtw88: 8723d: Add coex support" commit and replace it with the upstream one due to dependency to bt coex functionality. [1]: https://lore.kernel.org/linux- wireless/20200518081444.7664-1-yhchu...@realtek.com/ [Test Case] 1. Associate to a WLAN, 2. Pair with some Bluetooth device, e.g. headset, 3. Run a stress test script to disconnect and reconnect Wi-Fi for 200 runs, 4. Make sure Wi-Fi passphrase dialog doesn't prompt at the end of the test. [Regression Potential] Low. These changes are mostly about rtl8723de or 11n, which is also for 8723de. == Original Bug Description == Existing Wi-Fi connection may be deauthenticated unsolicitedly with reason 23=IEEE8021X_FAILED when the system is also paired with a Bluetooth device. A WLAN passphrase dialog propmpts, and system disconnects from network leaving an error message in syslog: [ 207.523312] wlp5s0: deauthenticated from a4:56:30:cc:0f:30 (Reason: 23=IEEE8021X_FAILED). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-oem-osp1 5.0.0.1050.53 ProcVersionSignature: Ubuntu 5.0.0-1050.55-oem-osp1 5.0.21 Uname: Linux 5.0.0-1050-oem-osp1 x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gdm1667 F pulseaudio u 3061 F pulseaudio /dev/snd/controlC0: gdm1667 F pulseaudio u 3061 F pulseaudio Date: Tue May 12 14:59:32 2020 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-grenn+X39 InstallationDate: Installed on 2020-04-10 (31 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04d9:0024 Holtek Semiconductor, Inc. Bus 001 Device 003: ID 0bda:d739 Realtek Semiconductor Corp. Bus 001 Device 005: ID 062a:4c01 Creative Labs Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell In
[Kernel-packages] [Bug 1877394] Autopkgtest regression report (linux-oracle-5.4/5.4.0-1019.19~18.04.1)
All autopkgtests for the newly accepted linux-oracle-5.4 (5.4.0-1019.19~18.04.1) for bionic have finished running. The following regressions have been reported in tests triggered by the package: zfs-linux/unknown (armhf) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-oracle-5.4 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1877394 Title: Kernel panic due to NULL ringbuffer vaddr dereference in i915 Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Fix Released Bug description: SRU Justification: [Impact] A sauce fix for a kernel panic in i915 that I frequently experienced was fixed by upstream. [Fix] The sauce patch I made should be dropped in exchange for the proper upstream fix. [Test] I tested the upstream fix and can confirm it fixes the crashes I experienced. [Regression Potential] Low. The upstream fix for this bug is tiny and we get to remove a nasty sauce patch. --- This is what the crash looks like: BUG: unable to handle page fault for address: 3448 RIP: 0010:gen8_emit_flush_render+0x163/0x190 Call Trace: execlists_request_alloc+0x25/0x40 __i915_request_create+0x1f4/0x2c0 i915_request_create+0x71/0xc0 i915_gem_do_execbuffer+0xb98/0x1a80 ? preempt_count_add+0x68/0xa0 ? _raw_spin_lock+0x13/0x30 ? _raw_spin_unlock+0x16/0x30 i915_gem_execbuffer2_ioctl+0x1de/0x3c0 ? i915_gem_busy_ioctl+0x7f/0x1d0 ? i915_gem_execbuffer_ioctl+0x2d0/0x2d0 drm_ioctl_kernel+0xb2/0x100 drm_ioctl+0x209/0x360 ? i915_gem_execbuffer_ioctl+0x2d0/0x2d0 ksys_ioctl+0x87/0xc0 __x64_sys_ioctl+0x16/0x20 do_syscall_64+0x4e/0x150 entry_SYSCALL_64_after_hwframe+0x44/0xa9 This bug was fixed by "UBUNTU: SAUCE: drm/i915: Synchronize active and retire callbacks" but there is an upstream fix for it, "drm/i915/gt: Make intel_ring_unpin() safe for concurrent pint". Let's replace the sauce patch with the upstream fix. More info here: https://gitlab.freedesktop.org/drm/intel/issues/1599 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1877394/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1878296] Autopkgtest regression report (linux-oracle-5.4/5.4.0-1019.19~18.04.1)
All autopkgtests for the newly accepted linux-oracle-5.4
(5.4.0-1019.19~18.04.1) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:
zfs-linux/unknown (armhf)
Please visit the excuses page listed below and investigate the failures,
proceeding afterwards as per the StableReleaseUpdates policy regarding
autopkgtest regressions [1].
https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#linux-oracle-5.4
[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions
Thank you!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1878296
Title:
rtl8723bu wifi issue after being turned off
Status in linux package in Ubuntu:
Confirmed
Status in linux-oem-osp1 package in Ubuntu:
Invalid
Status in linux source package in Bionic:
Fix Committed
Status in linux-oem-osp1 source package in Bionic:
Fix Released
Status in linux source package in Eoan:
Fix Committed
Status in linux-oem-osp1 source package in Eoan:
Fix Released
Status in linux source package in Focal:
Fix Committed
Status in linux-oem-osp1 source package in Focal:
Invalid
Status in linux source package in Groovy:
Confirmed
Status in linux-oem-osp1 source package in Groovy:
Invalid
Bug description:
[SRU Justification]
[Impact]
With the rtl8723bu Wi-Fi/Bluetooth combo adapter, if the wifi is turned
off and then turned on again under the circumstance that a Bluetooth
device was paired previously, the system can't connect to a wireless
network until the system is rebooted.
[Fix]
Commit e542e66b7c2e("rtl8xxxu: add bluetooth co-existence support for
single antenna"), which landed v5.5 and as its subject suggests, support
bluetooth co-existence for RTL8723BU and fixes WiFi disconnection
problem when Bluetooth is in action.
Commit a9bb0b515778("rtl8xxxu: Improve TX performance of RTL8723BU on
rtl8xxxu driver") was added as a prerequisite to aforementioned fix.
Commit 4fcef8609132("rtl8xxxu: remove set but not used variable
'rate_mask'") and commit eac08515d7bd("rtl8xxxu: Remove set but not used
variable 'vif','dev','len'") are included as minor fixes to previous
commits.
[Test Case]
1. Turn on Wi-Fi and get associated with some AP.
2. Pair some bluetooth device.
3. Turn off Wi-Fi and turn again.
4. Expect Wi-Fi reconnects to the previous associated AP.
[Regression Potential]
Low. Both commits only affect RTL8723BU.
== Original Bug Description ==
With the rtl8723bu wireless adapter, if the wifi is turned off and then
turned on again, the system can't connect to a wireless network until the
system is rebooted.
The issue is not upstream. With mainline kernel and in other distros,
everything works fine.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-29-generic 5.4.0-29.33
ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
Uname: Linux 5.4.0-29-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: user 1384 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Tue May 12 19:02:49 2020
InstallationDate: Installed on 2020-05-12 (0 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 090c:037c Silicon Motion, Inc. - Taiwan (formerly
Feiya Technology Corp.) 300k Pixel Camera
Bus 001 Device 003: ID 0bda:b720 Realtek Semiconductor Corp. 802.11n WLAN
Adapter
Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card
Reader Controller
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Positivo Tecnologia SA N1240
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic
root=UUID=984e1018-1354-474e-83a9-b8ab7a761be7 ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-5.4.0-29-generic N/A
linux-backports-modules-5.4.0-29-generic N/A
linux-firmware1.187
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/15/2019
dmi.bios.vendor: Desenvolvido por Positivo Tecnologia SA
dmi.bios.version: V1.09.X
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: N14DP6
dmi.board.vendor: Positivo Tecnologia SA
dmi.board.version: 11139547
dmi.chassis.asset.tag: To be filled by O.E.M.
dmi.chassis.type: 10
dmi.chassis.vendor: Positivo Tecnologia SA
dmi.chassis.version: To be filled by O.E.M.
dmi.modalias:
dmi:bvnDesenvolvidoporPositivoTecnologiaSA:bvrV1.09.X:bd07/15/2019:svnPositivoTecnologiaSA:pnN1240:pvrTobefilledbyO.E.M.:rvnPositivoTecnologi
[Kernel-packages] [Bug 1877013] Autopkgtest regression report (linux-oracle-5.4/5.4.0-1019.19~18.04.1)
All autopkgtests for the newly accepted linux-oracle-5.4 (5.4.0-1019.19~18.04.1) for bionic have finished running. The following regressions have been reported in tests triggered by the package: zfs-linux/unknown (armhf) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-oracle-5.4 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1877013 Title: Dell XPS 13 9300 mirror mode doesn't work sometimes with WD19TB Status in HWE Next: New Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Fix Released Bug description: [Impact] Connect HDMI monitor on WD19TB dock and connect WD19TB to Dell XPS 13 9300, toggling the display mode to mirror sometimes got a blank screen on external monitor. [Fix] After bisect kernel and found below commit(from v5.7-rc2) improves the stability bcad588dea53 drm/i915/perf: Do not clear pollin for small user read buffers [Test] Verified on Dell XPS 13 9300 with WD19TB docking station, the fail rate becomes from 1/2 to 1/30 [Regression Potential] Low, this commit has been CC'd to stable, so we will have this soon. [Misc] OEM-5.6 has this commit from v5.6.6 stable update To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1877013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1878040] Autopkgtest regression report (linux-oracle-5.4/5.4.0-1019.19~18.04.1)
All autopkgtests for the newly accepted linux-oracle-5.4 (5.4.0-1019.19~18.04.1) for bionic have finished running. The following regressions have been reported in tests triggered by the package: zfs-linux/unknown (armhf) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-oracle-5.4 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1878040 Title: Focal update: v5.4.40 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Fix Released Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.4.40 upstream stable release from git://git.kernel.org/ vhost: vsock: kick send_pkt worker once device is started drm/bridge: analogix_dp: Split bind() into probe() and real bind() ASoC: topology: Check return value of soc_tplg_create_tlv ASoC: topology: Check return value of soc_tplg_*_create ASoC: topology: Check soc_tplg_add_route return value ASoC: topology: Check return value of pcm_new_ver ASoC: topology: Check return value of soc_tplg_dai_config selftests/ipc: Fix test failure seen after initial test run ASoC: sgtl5000: Fix VAG power-on handling ASoC: topology: Fix endianness issue usb: dwc3: gadget: Properly set maxpacket limit ASoC: rsnd: Fix parent SSI start/stop in multi-SSI mode ASoC: rsnd: Fix HDMI channel mapping for multi-SSI mode ASoC: codecs: hdac_hdmi: Fix incorrect use of list_for_each_entry remoteproc: qcom_q6v5_mss: fix a bug in q6v5_probe() drm/amdgpu: Correctly initialize thermal controller for GPUs with Powerplay table v0 (e.g Hawaii) wimax/i2400m: Fix potential urb refcnt leak net: stmmac: fix enabling socfpga's ptp_ref_clock net: stmmac: Fix sub-second increment ASoC: rsnd: Don't treat master SSI in multi SSI setup as parent ASoC: rsnd: Fix "status check failed" spam for multi-SSI cifs: protect updating server->dstaddr with a spinlock scripts/config: allow colons in option strings for sed cifs: do not share tcons with DFS tracing: Fix memory leaks in trace_events_hist.c lib/mpi: Fix building for powerpc with clang mac80211: sta_info: Add lockdep condition for RCU list usage net: bcmgenet: suppress warnings on failed Rx SKB allocations net: systemport: suppress warnings on failed Rx SKB allocations drm/i915: Extend WaDisableDARBFClkGating to icl,ehl,tgl sctp: Fix SHUTDOWN CTSN Ack in the peer restart case Revert "software node: Simplify software_node_release() function" hexagon: clean up ioremap hexagon: define ioremap_uc ALSA: hda: Match both PCI ID and SSID for driver blacklist x86/kvm: fix a missing-prototypes "vmread_error" platform/x86: GPD pocket fan: Fix error message when temp-limits are out of range ACPI: PM: s2idle: Fix comment in acpi_s2idle_prepare_late() mac80211: add ieee80211_is_any_nullfunc() cgroup, netclassid: remove double cond_resched libbpf: Fix readelf output parsing for Fedora mm/mremap: Add comment explaining the untagging behaviour of mremap() Revert "drm/amd/display: setting the DIG_MODE to the correct value." tools headers UAPI: Sync copy of arm64's asm/unistd.h with the kernel sources udp: document udp_rcv_segment special case for looped packets PM / devfreq: Add missing locking while setting suspend_freq Linux 5.4.40 UBUNTU: upstream stable to v5.4.40 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1878040/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1877958] Autopkgtest regression report (linux-oracle-5.4/5.4.0-1019.19~18.04.1)
All autopkgtests for the newly accepted linux-oracle-5.4
(5.4.0-1019.19~18.04.1) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:
zfs-linux/unknown (armhf)
Please visit the excuses page listed below and investigate the failures,
proceeding afterwards as per the StableReleaseUpdates policy regarding
autopkgtest regressions [1].
https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#linux-oracle-5.4
[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions
Thank you!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1877958
Title:
Do not treat unresolved test case in ftrace from
ubuntu_kernel_selftests as failure
Status in ubuntu-kernel-tests:
In Progress
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Xenial:
Fix Released
Status in linux source package in Bionic:
Fix Released
Status in linux source package in Eoan:
Fix Released
Status in linux source package in Focal:
Fix Released
Bug description:
== SRU Justification ==
There are some test cases in ftrace from ubuntu_kernel_selftests that
would need some kernel configs to be enabled or have some special HW
requirements:
* https://pad.lv/1869347 - missing CONFIG_SAMPLE_TRACE_PRINTK=m
* https://pad.lv/1869349 - missing CONFIG_SAMPLE_TRACE_PRINTK=m
* https://pad.lv/1874198 - nproc > 1
If the requirement was not met, these test will fail with "unresolved"
and return 1. So even these is no failed test case, the ftrace test
will still be marked as "failed" with the presence of unresolved test:
# # of passed: 28
# # of failed: 0
# # of unresolved: 1
# # of untested: 0
# # of unsupported: 58
# # of xfailed: 0
# # of undefined(test bug): 0
not ok 1 selftests: ftrace: ftracetest # exit=1
== Fix ==
* b730d668138c ("ftrace/selftest: make unresolved cases cause failure if
--fail-unresolved set")
This patch will only make unresolved test case return 1 if we ask it
to fail with unresolved test case.
It can be cherry-picked to kernels starting from Disco.
For Bionic and Xenial it needs to be backported with some context
adjustment as they're missing some other patches to the testing tool.
== Test ==
With the patch applied, the ftrace test will not be marked as failed
with the presence of unresolved test case:
# # of passed: 28
# # of failed: 0
# # of unresolved: 1
# # of untested: 0
# # of unsupported: 58
# # of xfailed: 0
# # of undefined(test bug): 0
ok 1 selftests: ftrace: ftracetest
== Regression Potential ==
Low, changes limited to testing tools, no actual impacts to our kernels.
The worst case is to cause false negative in test reports, but in that
case it's probably a test case issue since a failed case should be
treated as a failed one, instead of unresolved.
== Original Bug Report ==
There are some test cases in ftrace from ubuntu_kernel_selftests that would
need some kernel configs to be enabled.
bug 1869347
bug 1869349
We should not treat unresolved test case as a failure, as it's
expected to fail with no correlated configs enabeled.
https://github.com/torvalds/linux/commit/b730d668138cb3dd9ce78f8003986d1adae5523a
#diff-33d74da785cbc5da20f71eb1af106d68
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1877958/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1876885] Autopkgtest regression report (linux-oracle-5.4/5.4.0-1019.19~18.04.1)
All autopkgtests for the newly accepted linux-oracle-5.4 (5.4.0-1019.19~18.04.1) for bionic have finished running. The following regressions have been reported in tests triggered by the package: zfs-linux/unknown (armhf) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-oracle-5.4 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1876885 Title: linux: riscv: set max_pfn to the PFN of the last page Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Released Bug description: == SRU Justification Focal/Groovy == The current max_pfn equals to zero. In this case, I found it caused users cannot get some page information through /proc such as kpagecount in v5.6 kernel because of new sanity checks. The following message is displayed by stress-ng test suite with the command "stress-ng --verbose --physpage 1 -t 1" on HiFive unleashed board. # stress-ng --verbose --physpage 1 -t 1 stress-ng: debug: [109] 4 processors online, 4 processors configured stress-ng: info: [109] dispatching hogs: 1 physpage stress-ng: debug: [109] cache allocate: reducing cache level from L3 (too high) to L0 stress-ng: debug: [109] get_cpu_cache: invalid cache_level: 0 stress-ng: info: [109] cache allocate: using built-in defaults as no suitable cache found stress-ng: debug: [109] cache allocate: default cache size: 2048K stress-ng: debug: [109] starting stressors stress-ng: debug: [109] 1 stressor spawned stress-ng: debug: [110] stress-ng-physpage: started [110] (instance 0) stress-ng: error: [110] stress-ng-physpage: cannot read page count for address 0x3fd34de000 in /proc/kpagecount, errno=0 (Success) stress-ng: error: [110] stress-ng-physpage: cannot read page count for address 0x3fd32db078 in /proc/kpagecount, errno=0 (Success) ... stress-ng: error: [110] stress-ng-physpage: cannot read page count for address 0x3fd32db078 in /proc/kpagecount, errno=0 (Success) stress-ng: debug: [110] stress-ng-physpage: exited [110] (instance 0) stress-ng: debug: [109] process [110] terminated stress-ng: info: [109] successful run completed in 1.00s # == Fix == Upstream commit in linux-next: commit c749bb2d554825e007cbc43b791f54e124dadfce Author: Vincent Chen Date: Mon Apr 27 14:59:24 2020 +0800 riscv: set max_pfn to the PFN of the last page == Test Case == Without the patch, running stress-ng --verbose --physpage 1 -t 1 on HiFive unleashed board will trip the bug. With the patch, the test passes as follows: # stress-ng --verbose --physpage 1 -t 1 stress-ng: debug: [104] 4 processors online, 4 processors configured stress-ng: info: [104] dispatching hogs: 1 physpage stress-ng: info: [104] cache allocate: using defaults, can't determine cache details from sysfs stress-ng: debug: [104] cache allocate: default cache size: 2048K stress-ng: debug: [104] starting stressors stress-ng: debug: [104] 1 stressor spawned stress-ng: debug: [105] stress-ng-physpage: started [105] (instance 0) stress-ng: debug: [105] stress-ng-physpage: exited [105] (instance 0) stress-ng: debug: [104] process [105] terminated stress-ng: info: [104] successful run completed in 1.01s == Regression Potential == Small, this correctly fixes the max_pfn and max_low_pfn to the correct end of DRAM location. The fix now can be shown to set these appropriately because stress-ng no longer triggers this corner case. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1876885/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1877592] Autopkgtest regression report (linux-oracle-5.4/5.4.0-1019.19~18.04.1)
All autopkgtests for the newly accepted linux-oracle-5.4 (5.4.0-1019.19~18.04.1) for bionic have finished running. The following regressions have been reported in tests triggered by the package: zfs-linux/unknown (armhf) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-oracle-5.4 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1877592 Title: Focal update: v5.4.39 upstream stable release Status in linux package in Ubuntu: Confirmed Status in linux source package in Focal: Fix Released Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.4.39 upstream stable release from git://git.kernel.org/ dma-buf: Fix SET_NAME ioctl uapi drm/edid: Fix off-by-one in DispID DTD pixel clock drm/amd/display: Fix green screen issue after suspend drm/qxl: qxl_release leak in qxl_draw_dirty_fb() drm/qxl: qxl_release leak in qxl_hw_surface_alloc() drm/qxl: qxl_release use after free NFSv4.1: fix handling of backchannel binding in BIND_CONN_TO_SESSION btrfs: fix transaction leak in btrfs_recover_relocation btrfs: fix block group leak when removing fails btrfs: fix partial loss of prealloc extent past i_size after fsync btrfs: transaction: Avoid deadlock due to bad initialization timing of fs_info::journal_info mmc: cqhci: Avoid false "cqhci: CQE stuck on" by not open-coding timeout loop mmc: sdhci-xenon: fix annoying 1.8V regulator warning mmc: sdhci-pci: Fix eMMC driver strength for BYT-based controllers mmc: sdhci-msm: Enable host capabilities pertains to R1b response mmc: meson-mx-sdio: Set MMC_CAP_WAIT_WHILE_BUSY mmc: meson-mx-sdio: remove the broken ->card_busy() op crypto: caam - fix the address of the last entry of S/G ALSA: hda/realtek - Two front mics on a Lenovo ThinkCenter ALSA: usb-audio: Correct a typo of NuPrime DAC-10 USB ID ALSA: hda/hdmi: fix without unlocked before return ALSA: line6: Fix POD HD500 audio playback ALSA: pcm: oss: Place the plugin buffer overflow checks correctly i2c: amd-mp2-pci: Fix Oops in amd_mp2_pci_init() error handling Drivers: hv: vmbus: Fix Suspend-to-Idle for Generation-2 VM dlmfs_file_write(): fix the bogosity in handling non-zero *ppos IB/rdmavt: Always return ERR_PTR from rvt_create_mmap_info() PM: ACPI: Output correct message on target power state PM: hibernate: Freeze kernel threads in software_resume() dm verity fec: fix hash block number in verity_fec_decode dm writecache: fix data corruption when reloading the target dm multipath: use updated MPATHF_QUEUE_IO on mapping for bio-based mpath ARM: dts: imx6qdl-sr-som-ti: indicate powering off wifi is safe scsi: qla2xxx: set UNLOADING before waiting for session deletion scsi: qla2xxx: check UNLOADING before posting async work RDMA/mlx5: Set GRH fields in query QP on RoCE RDMA/mlx4: Initialize ib_spec on the stack RDMA/siw: Fix potential siw_mem refcnt leak in siw_fastreg_mr() RDMA/core: Prevent mixed use of FDs between shared ufiles RDMA/core: Fix race between destroy and release FD object RDMA/cm: Fix ordering of xa_alloc_cyclic() in ib_create_cm_id() RDMA/cm: Fix an error check in cm_alloc_id_priv() i2c: iproc: generate stop event for slave writes vfio: avoid possible overflow in vfio_iommu_type1_pin_pages vfio/type1: Fix VA->PA translation for PFNMAP VMAs in vaddr_get_pfn() iommu/qcom: Fix local_base status check scsi: target/iblock: fix WRITE SAME zeroing iommu/amd: Fix legacy interrupt remapping for x2APIC-enabled system i2c: aspeed: Avoid i2c interrupt status clear race condition. ALSA: opti9xx: shut up gcc-10 range warning Fix use after free in get_tree_bdev() nvme: prevent double free in nvme_alloc_ns() error handling nfs: Fix potential posix_acl refcnt leak in nfs3_set_acl dmaengine: dmatest: Fix iteration non-stop logic dmaengine: dmatest: Fix process hang when reading 'wait' parameter arm64: vdso: Add -fasynchronous-unwind-tables to cflags selinux: properly handle multiple messages in selinux_netlink_send() Linux 5.4.39 UBUNTU: upstream stable to v5.4.39 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/
[Kernel-packages] [Bug 1878649] Autopkgtest regression report (linux-oracle-5.4/5.4.0-1019.19~18.04.1)
All autopkgtests for the newly accepted linux-oracle-5.4 (5.4.0-1019.19~18.04.1) for bionic have finished running. The following regressions have been reported in tests triggered by the package: zfs-linux/unknown (armhf) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-oracle-5.4 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1878649 Title: Focal update: v5.4.41 upstream stable release Status in linux package in Ubuntu: Confirmed Status in linux source package in Focal: Fix Released Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.4.41 upstream stable release from git://git.kernel.org/ USB: serial: qcserial: Add DW5816e support nvme: refactor nvme_identify_ns_descs error handling nvme: fix possible hang when ns scanning fails during error recovery tracing/kprobes: Fix a double initialization typo net: macb: Fix runtime PM refcounting drm/amdgpu: move kfd suspend after ip_suspend_phase1 drm/amdgpu: drop redundant cg/pg ungate on runpm enter vt: fix unicode console freeing with a common interface tty: xilinx_uartps: Fix missing id assignment to the console devlink: fix return value after hitting end in region read dp83640: reverse arguments to list_add_tail fq_codel: fix TCA_FQ_CODEL_DROP_BATCH_SIZE sanity checks ipv6: Use global sernum for dst validation with nexthop objects mlxsw: spectrum_acl_tcam: Position vchunk in a vregion list properly neigh: send protocol value in neighbor create notification net: dsa: Do not leave DSA master with NULL netdev_ops net: macb: fix an issue about leak related system resources net: macsec: preserve ingress frame ordering net/mlx4_core: Fix use of ENOSPC around mlx4_counter_alloc() net_sched: sch_skbprio: add message validation to skbprio_change() net: stricter validation of untrusted gso packets net: tc35815: Fix phydev supported/advertising mask net/tls: Fix sk_psock refcnt leak in bpf_exec_tx_verdict() net/tls: Fix sk_psock refcnt leak when in tls_data_ready() net: usb: qmi_wwan: add support for DW5816e nfp: abm: fix a memory leak bug sch_choke: avoid potential panic in choke_reset() sch_sfq: validate silly quantum values tipc: fix partial topology connection closure tunnel: Propagate ECT(1) when decapsulating as recommended by RFC6040 bnxt_en: Fix VF anti-spoof filter setup. bnxt_en: Reduce BNXT_MSIX_VEC_MAX value to supported CQs per PF. bnxt_en: Improve AER slot reset. bnxt_en: Return error when allocating zero size context memory. bnxt_en: Fix VLAN acceleration handling in bnxt_fix_features(). net/mlx5: DR, On creation set CQ's arm_db member to right value net/mlx5: Fix forced completion access non initialized command entry net/mlx5: Fix command entry leak in Internal Error State net: mvpp2: prevent buffer overflow in mvpp22_rss_ctx() net: mvpp2: cls: Prevent buffer overflow in mvpp2_ethtool_cls_rule_del() HID: wacom: Read HID_DG_CONTACTMAX directly for non-generic devices sctp: Fix bundling of SHUTDOWN with COOKIE-ACK Revert "HID: wacom: generic: read the number of expected touches on a per collection basis" HID: usbhid: Fix race between usbhid_close() and usbhid_stop() HID: wacom: Report 2nd-gen Intuos Pro S center button status over BT USB: uas: add quirk for LaCie 2Big Quadra usb: chipidea: msm: Ensure proper controller reset using role switch API USB: serial: garmin_gps: add sanity checking for data length tracing: Add a vmalloc_sync_mappings() for safe measure crypto: arch/nhpoly1305 - process in explicit 4k chunks KVM: s390: Remove false WARN_ON_ONCE for the PQAP instruction KVM: VMX: Explicitly clear RFLAGS.CF and RFLAGS.ZF in VM-Exit RSB path KVM: arm: vgic: Fix limit condition when writing to GICD_I[CS]ACTIVER KVM: arm64: Fix 32bit PC wrap-around arm64: hugetlb: avoid potential NULL dereference drm: ingenic-drm: add MODULE_DEVICE_TABLE ipc/mqueue.c: change __do_notify() to bypass check_kill_permission() epoll: atomically remove wait entry on wake up eventpoll: fix missing wakeup for ovflist in ep_poll_callback mm/page_alloc: fix watchdog soft lockups during set_zone_
[Kernel-packages] [Bug 1876859] Autopkgtest regression report (linux-oracle-5.4/5.4.0-1019.19~18.04.1)
All autopkgtests for the newly accepted linux-oracle-5.4 (5.4.0-1019.19~18.04.1) for bionic have finished running. The following regressions have been reported in tests triggered by the package: zfs-linux/unknown (armhf) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-oracle-5.4 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1876859 Title: Support DMIC micmute LED on HP platforms Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux source package in Focal: Fix Released Status in linux-oem-5.6 source package in Focal: Fix Released Status in linux source package in Groovy: Incomplete Status in linux-oem-5.6 source package in Groovy: Invalid Bug description: [Impact] DMIC micmute LED on HP platforms doesn't work. [Fix] Add LED class support from HDA codec, so DMIC can use LEDS_TRIGGER_AUDIO to control micmute. [Test] After applying the fix, micmute LED can correctly indicate the status of micmute. [Regression Potential] Low. For now it only affects one platform, and it doesn't touch any core part of the subsystem. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1876859/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1866357] Autopkgtest regression report (linux-oracle-5.4/5.4.0-1019.19~18.04.1)
All autopkgtests for the newly accepted linux-oracle-5.4 (5.4.0-1019.19~18.04.1) for bionic have finished running. The following regressions have been reported in tests triggered by the package: zfs-linux/unknown (armhf) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-oracle-5.4 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1866357 Title: Pop sound from build-in speaker during cold boot and resume from S3 Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Released Bug description: [Description] On a Dell Wyse 5070 ThinClient device with 18.04 installed, during cold boot and resume from S3, internal speaker will have a noticeable short pop noise. [More detail] There are similar bugs reported indicating it's related to codec powersaving [1]. On some devices, disable powersaving can workaround it, but the same workaround does not work on this device. [1] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821663 [Experiment] With Ubuntu 16.04 (4.13 kernel) installed --> NO pop noise With Ubuntu 16.04.x (4.15 kernel) installed --> pop noise With Ubuntu 18.04.x (4.15, 5.0 kernel) installed --> pop noise So I started testing kernels between 4.13 and 4.15, found the issue does not present before 4.15.0-58 kernel (including 4.15.0-58), and kernel after that started to have the pop noise. [HW info] Codec: Realtek ALC3253 00:0e.0 Audio device [0403]: Intel Corporation Device [8086:3198] (rev 03) Device is not with me at this moment, I will provide more info if required. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1901 F pulseaudio CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-osp1-sanbernardino+X100 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-03-09 (0 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 MachineType: Dell Inc. Wyse 5070 Thin Client Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic root=UUID=22fa172b-895b-4061-834e-d616380befc5 ro mem_sleep_default=deep quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-40-generic N/A linux-backports-modules-5.3.0-40-generic N/A linux-firmware1.173.9 Tags: bionic Uname: Linux 5.3.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/08/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.0 dmi.board.vendor: Dell Inc. dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.0:bd01/08/2020:svnDellInc.:pnWyse5070ThinClient:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct3:cvr: dmi.product.family: Wyse Thin Client 5000 Series dmi.product.name: Wyse 5070 Thin Client dmi.product.sku: 080C dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1866357/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1884766] Re: use-after-free in af_alg_accept() due to bh_lock_sock()
Focal: testing
=
$ ./stress-ng --version
stress-ng, version 0.11.14 (gcc 9.3, x86_64 Linux 5.4.0-38-generic) 💻🔥
$ sudo modprobe -a \
$(modinfo \
/lib/modules/$(uname -r)/kernel/crypto/*.ko \
/lib/modules/$(uname -r)/kernel/arch/*/crypto/*.ko \
| grep -ow 'crypto-.*')
No error/strange kernel messages logged in /var/log/kern.log.
original:
$ uname -rv
5.4.0-38-generic #42-Ubuntu SMP Mon Jun 8 14:14:24 UTC 2020
$ ./stress-ng --af-alg 0 --timeout 1h 2>&1 | tee
../stress-ng.log.focal.orig
stress-ng: info: [27052] dispatching hogs: 11 af-alg
stress-ng: info: [27054] stress-ng-af-alg: 62 cryptographic algorithms
found in /proc/crypto
stress-ng: info: [27054] stress-ng-af-alg: 101 cryptographic
algorithms max (with defconfigs)
stress-ng: info: [27052] successful run completed in 3600.38s (1 hour,
0.38 secs)
modified:
$ uname -rv
5.4.0-38-generic #42+test20200623b1 SMP Tue Jun 23 09:37:56 -03 2020
$ ./stress-ng --af-alg 0 --timeout 1h 2>&1 | tee
../stress-ng.log.focal.mod.2
stress-ng: info: [2577] dispatching hogs: 11 af-alg
stress-ng: info: [2579] stress-ng-af-alg: 62 cryptographic algorithms
found in /proc/crypto
stress-ng: info: [2579] stress-ng-af-alg: 101 cryptographic algorithms
max (with defconfigs)
stress-ng: info: [2577] successful run completed in 3600.52s (1 hour,
0.52 secs)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1884766
Title:
use-after-free in af_alg_accept() due to bh_lock_sock()
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Xenial:
In Progress
Status in linux source package in Bionic:
In Progress
Status in linux source package in Eoan:
In Progress
Status in linux source package in Focal:
In Progress
Status in linux source package in Groovy:
Won't Fix
Bug description:
[Impact]
* Users of the Linux kernel's crypto userspace API
reported BUG() / kernel NULL pointer dereference
errors after kernel upgrades.
* The stack trace signature is an accept() syscall
going through af_alg_accept() and hitting errors
usually in one of:
- apparmor_sk_clone_security()
- apparmor_sock_graft()
- release_sock()
[Fix]
* This is a regression introduced by upstream commit
37f96694cf73 ("crypto: af_alg - Use bh_lock_sock
in sk_destruct") which made its way through stable.
* The offending patch allows the critical regions
of af_alg_accept() and af_alg_release_parent() to
run concurrently; now with the "right" events on 2
CPUs it might drop the non-atomic reference counter
of the alg_sock then the sock, thus release a sock
that is still in use.
* The fix is upstream commit 34c86f4c4a7b ("crypto:
af_alg - fix use-after-free in af_alg_accept() due
to bh_lock_sock()") [1]. It changes alg_sock's ref
counter to atomic, which addresses the root cause.
[Test Case]
* There is a synthetic test case available, which
uses a kprobes kernel module to synchronize the
concurrent CPUs on the instructions responsible
for the problem; and a userspace part to run it.
* The organic reproducer is the Varnish Cache Plus
software with the Crypto vmod (which uses kernel
crypto userspace API) under long, very high load.
* The patch has been verified on both reproducers
with the 4.15 and 5.7 kernels.
* More tests performed with 'stress-ng --af-alg'
with 11 CPUs on Xenial/Bionic/Disco/Eoan/Focal
(all on same version of stress-ng, V0.11.14)
No regressions observed from original kernel.
(the af-alg stressor can exercise almost all
kernel crypto modules shipped with the kernel;
so it checks more paths/crypto alg interfaces.)
[Regression Potential]
* The fix patch does a fundamental change in how
alg_sock reference counters work, plus another
change to the 'nokey' counting. This of course
*has* a risk of regression.
* Regressions theoretically could manifest as use
after free errors (in case of undercounting) in
the af_alg functions or silent memory leaks (in
case of overcounting), but also other behaviors
since reference counting is key to many things.
* FWIW, this patch has been written by the crypto
subsystem maintainer, who certainly knows a lot
of the normal and corner cases, thus giving the
patch more credit.
* Testing with the organic reproducer ran as long
as 5 days, without issues, so it does look good.
[Other Info]
* Not sending for Groovy (should get via Unstable).
* [1] Patch:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=34c86f4c4a7be3b3e35aa48b
[Kernel-packages] [Bug 1875916] Autopkgtest regression report (linux-oracle-5.4/5.4.0-1019.19~18.04.1)
All autopkgtests for the newly accepted linux-oracle-5.4 (5.4.0-1019.19~18.04.1) for bionic have finished running. The following regressions have been reported in tests triggered by the package: zfs-linux/unknown (armhf) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-oracle-5.4 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1875916 Title: upgrading to 4.15.0-99-generic breaks the sound and the trackpad Status in linux package in Ubuntu: Confirmed Bug description: I am using kubuntu LTS 18.04. This morning I was promped to update the kernel to the 4.15.0-99-generic. After the upgrade I did not manage to get any sound. I checked everything, pavucontrol, alsamix, everything was in order, the streams showed as if they were playing, however I couldn't get any sound from the speakers headphones and I could not get any sound recorded either. I then rebooted with the previous version of the Kernel, and have my sound back without doing anything at all. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=4a7a721a-7a2e-4644-a881-34adcb28e1ba InstallationDate: Installed on 2019-01-29 (455 days ago) InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IwConfig: lono wireless extensions. wlp108s0 no wireless extensions. MachineType: Dell Inc. Latitude 7390 2-in-1 Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-99-generic root=/dev/mapper/kubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-99.100-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-99-generic N/A linux-backports-modules-4.15.0-99-generic N/A linux-firmware 1.173.17 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 4.15.0-99-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/27/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.0 dmi.board.name: 0YNG30 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.0:bd08/27/2018:svnDellInc.:pnLatitude73902-in-1:pvr:rvnDellInc.:rn0YNG30:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 7390 2-in-1 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875916/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874359] Autopkgtest regression report (linux-oracle-5.4/5.4.0-1019.19~18.04.1)
All autopkgtests for the newly accepted linux-oracle-5.4 (5.4.0-1019.19~18.04.1) for bionic have finished running. The following regressions have been reported in tests triggered by the package: zfs-linux/unknown (armhf) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-oracle-5.4 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1874359 Title: alsa/sof: kernel oops on the machine without Intel hdmi audio codec (a regression in the asoc machine driver) Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.6 package in Ubuntu: Fix Released Status in linux-oem-osp1 package in Ubuntu: Fix Released Status in linux-oem-osp1 source package in Bionic: Fix Released Status in linux source package in Eoan: Fix Released Status in linux source package in Focal: Fix Released Status in linux-oem-5.6 source package in Focal: Fix Released Bug description: Please apply the fix for #1872569 first, then apply this patch. [Impact] The fix for #1872569 introduces a regression, the driver access a NULL pointer on the machiens without Intel hdmi audio codec. [Fix] pick a fixing patch from alsa/asoc repo, the patch doesn't assume the first rtd is for hda codec, it will look for that rtd through strstr() [Test Case] Boot the kenrel on those 2 Dell and 2 Lenovo machines which uses this driver, the audio could work. disable the intel hdmi audio codec through bios, the analogue audio still works [Regression Risk] Low, I have tested this patch Lenovo / Dell machines, they all worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874359/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1884766] Re: use-after-free in af_alg_accept() due to bh_lock_sock()
[E/F/Unstable][PATCH 0/1] crypto: fix regression/use-after-free in
af_alg_accept()
https://lists.ubuntu.com/archives/kernel-team/2020-June/111620.html
[E/F/Unstable][PATCH 1/1] crypto: af_alg - fix use-after-free in
af_alg_accept() due to bh_lock_sock()
https://lists.ubuntu.com/archives/kernel-team/2020-June/111621.html
[D][PATCH] crypto: af_alg - fix use-after-free in af_alg_accept() due to
bh_lock_sock()
https://lists.ubuntu.com/archives/kernel-team/2020-June/111622.html
[B][PATCH] crypto: af_alg - fix use-after-free in af_alg_accept() due to
bh_lock_sock()
https://lists.ubuntu.com/archives/kernel-team/2020-June/111623.html
[X][PATCH] crypto: af_alg - fix use-after-free in af_alg_accept() due to
bh_lock_sock()
https://lists.ubuntu.com/archives/kernel-team/2020-June/111624.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1884766
Title:
use-after-free in af_alg_accept() due to bh_lock_sock()
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Xenial:
In Progress
Status in linux source package in Bionic:
In Progress
Status in linux source package in Eoan:
In Progress
Status in linux source package in Focal:
In Progress
Status in linux source package in Groovy:
Won't Fix
Bug description:
[Impact]
* Users of the Linux kernel's crypto userspace API
reported BUG() / kernel NULL pointer dereference
errors after kernel upgrades.
* The stack trace signature is an accept() syscall
going through af_alg_accept() and hitting errors
usually in one of:
- apparmor_sk_clone_security()
- apparmor_sock_graft()
- release_sock()
[Fix]
* This is a regression introduced by upstream commit
37f96694cf73 ("crypto: af_alg - Use bh_lock_sock
in sk_destruct") which made its way through stable.
* The offending patch allows the critical regions
of af_alg_accept() and af_alg_release_parent() to
run concurrently; now with the "right" events on 2
CPUs it might drop the non-atomic reference counter
of the alg_sock then the sock, thus release a sock
that is still in use.
* The fix is upstream commit 34c86f4c4a7b ("crypto:
af_alg - fix use-after-free in af_alg_accept() due
to bh_lock_sock()") [1]. It changes alg_sock's ref
counter to atomic, which addresses the root cause.
[Test Case]
* There is a synthetic test case available, which
uses a kprobes kernel module to synchronize the
concurrent CPUs on the instructions responsible
for the problem; and a userspace part to run it.
* The organic reproducer is the Varnish Cache Plus
software with the Crypto vmod (which uses kernel
crypto userspace API) under long, very high load.
* The patch has been verified on both reproducers
with the 4.15 and 5.7 kernels.
* More tests performed with 'stress-ng --af-alg'
with 11 CPUs on Xenial/Bionic/Disco/Eoan/Focal
(all on same version of stress-ng, V0.11.14)
No regressions observed from original kernel.
(the af-alg stressor can exercise almost all
kernel crypto modules shipped with the kernel;
so it checks more paths/crypto alg interfaces.)
[Regression Potential]
* The fix patch does a fundamental change in how
alg_sock reference counters work, plus another
change to the 'nokey' counting. This of course
*has* a risk of regression.
* Regressions theoretically could manifest as use
after free errors (in case of undercounting) in
the af_alg functions or silent memory leaks (in
case of overcounting), but also other behaviors
since reference counting is key to many things.
* FWIW, this patch has been written by the crypto
subsystem maintainer, who certainly knows a lot
of the normal and corner cases, thus giving the
patch more credit.
* Testing with the organic reproducer ran as long
as 5 days, without issues, so it does look good.
[Other Info]
* Not sending for Groovy (should get via Unstable).
* [1] Patch:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=34c86f4c4a7be3b3e35aa48bd18299d4c756064d
[Stack Trace Examples]
Examples:
BUG: unable to handle kernel NULL pointer dereference at
...
RIP: 0010:apparmor_sk_clone_security+0x26/0x70
...
Call Trace:
security_sk_clone+0x33/0x50
af_alg_accept+0x81/0x1c0 [af_alg]
alg_accept+0x15/0x20 [af_alg]
SYSC_accept4+0xff/0x210
SyS_accept+0x10/0x20
do_syscall_64+0x73/0x130
entry_SYSCALL_64_after_hwframe+0x3d/0xa2
general protection fault: [#1] SMP PTI
...
RIP: 0010:__release_sock+0x54/0xe0
...
Call Trace:
release_sock+0x30/0xa0
af_alg_accept+0x122/0x1c0 [af_alg]
alg_accept+0x15/0x20 [af_alg]
SYSC_
[Kernel-packages] [Bug 1875863] Autopkgtest regression report (linux-oracle-5.4/5.4.0-1019.19~18.04.1)
All autopkgtests for the newly accepted linux-oracle-5.4 (5.4.0-1019.19~18.04.1) for bionic have finished running. The following regressions have been reported in tests triggered by the package: zfs-linux/unknown (armhf) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-oracle-5.4 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1875863 Title: ceph -- Unable to mount ceph volume on s390x Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: Fix Released Status in linux source package in Groovy: In Progress Bug description: SRU Justification: == [Impact] * Unable to mount ceph volumes on big endian systems, like s390x. * The mount operation always fails with an IO error. * This is caused by an endiness issue in function handle_session where variable features is always little endian. * But test_bit assumes the host order of bytes, hence causes a problem on big endian systems. [Fix] * 0fa8263367db9287aa0632f96c1a5f93cc478150 0fa8263367db "ceph: fix endianness bug when handling MDS session feature bits" [Test Case] * Setup ceph on s390x. * Try to mount a ceph volume. * If it mounts correctly the patch is applied and working. * Without the patch a mount always fails on big endian / s390x. [Regression Potential] * There is regression potential with having code changes in ceph's session handler, which is common code. * However, the patch was accepted (slightly changed) by the ceph maintainers and with that got upstream accepted, too. * The patch is fairly limited (5 lines removed, 3 added), hence the changes are quite traceable. __ When mounting a ceph volume, mount operation fails with an IO error. The problem is always reproducible. Identified potential root cause as kernel endian bug: In the function handle_session() variable @features always contains little endian order of bytes. Just because The feature mask sent by the MDS is little-endian (bits are packed bytewise from left to right in encode_supported_features()). However, test_bit(), called to check features availability, assumes the host order of bytes in that variable. This leads to problems on big endian architectures. Specifically it is impossible to mount ceph volume on s390. A fixup was proposed to convert little-endian order of bytes to the host one. That fixup was modified by ceph maintainers to use existing unpacking means for the conversion. The resulted patch attached. Related discussion in the ceph-development mailing list: https://marc.info/?l=ceph-devel&m=158815357301332&w=2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1875863/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-oracle-5.4/5.4.0-1019.19~18.04.1)
All autopkgtests for the newly accepted linux-oracle-5.4 (5.4.0-1019.19~18.04.1) for bionic have finished running. The following regressions have been reported in tests triggered by the package: zfs-linux/unknown (armhf) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-oracle-5.4 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: New Status in linux source package in Precise: Fix Committed Status in linux-azure source package in Precise: Invalid Status in linux-azure-edge source package in Precise: Invalid Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Invalid Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: New Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: New Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874698] Autopkgtest regression report (linux-oracle-5.4/5.4.0-1019.19~18.04.1)
All autopkgtests for the newly accepted linux-oracle-5.4 (5.4.0-1019.19~18.04.1) for bionic have finished running. The following regressions have been reported in tests triggered by the package: zfs-linux/unknown (armhf) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-oracle-5.4 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/1874698 Title: [OMEN by HP Laptop 15-dh0xxx, Realtek ALC285, Black Mic, Left] Recording problem Status in HWE Next: New Status in OEM Priority Project: Fix Released Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in linux package in Ubuntu: Confirmed Status in alsa-ucm-conf source package in Focal: Fix Released Status in linux source package in Focal: Fix Committed Status in alsa-ucm-conf source package in Groovy: Fix Released Bug description: This is for alsa-ucm-conf: The patches are already in the mainline alsa-ucm-conf, so only sent the SRU for focal [Impact] On the machines without Intel HDMI, the sof driver will fail to initialize. [Fix] After fixing the kernel, we also need to change the ucm2 to make it support the machine without Intel hdmi audio. [Test Case] Boot the kernel on the machines without Intel HDMI audio, everything works well including the audio. [Regression Risk] Low, these 2 patches are already in the mainline alsa-ucm-conf. And we already tested them on 4 HP machines. This is for linux kernel: The patch is already in the oem-5.6 kernel and unstable kernel, so only sent the SRU for focal [Impact] On the machines without Intel HDMI, the sof driver will fail to initialize. [Fix] Intel upstream 2 patches in the kernel to fix it. [Test Case] Boot the kernel on the machines without Intel HDMI audio, everything works well including the audio. [Regression Risk] Low, these 2 patches are already in the mainline kernel. On Ubuntu 20.04, by default, sof-audio-pci is used. I only have "Dummy output" in pavucontrol. To fix this, I modified /etc/modprobe.d/alsa- base.conf and added "options snd-intel-dspcfg dsp_driver=1" so that now "snd-hda-intel" is loaded instead of sof-audio-pci. While the speakers are working fine, I do not have the internal microphone working (suspect a digital array). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: wittawat 2063 F pulseaudio /dev/snd/controlC0: wittawat 2063 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Apr 24 12:42:32 2020 InstallationDate: Installed on 2020-04-23 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Mic, Left Symptom_Type: None of the above Title: [OMEN by HP Laptop 15-dh0xxx, Realtek ALC285, Black Mic, Left] Recording problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/09/2019 dmi.bios.vendor: AMI dmi.bios.version: F.22 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8600 dmi.board.vendor: HP dmi.board.version: 44.41 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.22:bd12/09/2019:svnHP:pnOMENbyHPLaptop15-dh0xxx:pvr:rvnHP:rn8600:rvr44.41:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP OMEN dmi.product.name: OMEN by HP Laptop 15-dh0xxx dmi.product.sku: 7JX54EA#ABD dmi.sys.vendor: HP mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-04-24T12:32:21.613996 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1874698/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874056] Autopkgtest regression report (linux-oracle-5.4/5.4.0-1019.19~18.04.1)
All autopkgtests for the newly accepted linux-oracle-5.4 (5.4.0-1019.19~18.04.1) for bionic have finished running. The following regressions have been reported in tests triggered by the package: zfs-linux/unknown (armhf) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-oracle-5.4 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1874056 Title: [UBUNTU 20.04] s390x/pci: enumerate pci functions per physical adapter Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: Fix Committed Bug description: SRU Justification: == [Impact] * Mellanox CX5 port multi-pathing is broken on s390x due to non- standard topology of PCI IDs (phys. and virtual) * The Mellanox Connect-X 5 PCI driver (mlx5) implements multi-path that can be used to combine multiple networking ports to improve performance and reliability. * For that purpose, the mlx5 driver combines PCI functions based on topology information (the function number) as determined by their PCI ID. * Currently the Linux on Z PCI bus does not reflect PCI topology information in the PCI ID. As a result, the mlx5 multi-path function is broken and cannot be activated. [Fix] * Backport 1: https://launchpadlibrarian.net/479699471/0001-s390-pci- Improve-handling-of-unset-UID.patch * Backport 2: https://launchpadlibrarian.net/479699482/0002-s390-pci- embedding-hotplug_slot-in-zdev.patch * Backport 3: https://launchpadlibrarian.net/479699492/0003-s390-pci- Expose-new-port-attribute-for-PCIe-function.patch * Backport 4: https://launchpadlibrarian.net/479699497/0004-s390-pci- adaptation-of-iommu-to-multifunction.patch * Backport 5: https://launchpadlibrarian.net/479700706/0005-s390-pci- define-kernel-parameters-for-PCI-multifunct.patch * Backport 6: https://launchpadlibrarian.net/479700712/0006-s390-pci- define-RID-and-RID-available.patch * Backport 7: https://launchpadlibrarian.net/479700739/0007-s390-pci- create-zPCI-bus.patch * Backport 8: https://launchpadlibrarian.net/479700769/0008-s390-pci- adapt-events-for-zbus.patch * Backport 9: https://launchpadlibrarian.net/479700786/0009-s390-pci- Handling-multifunctions.patch * Backport 10: https://launchpadlibrarian.net/479700794/0010-s390-pci- Do-not-disable-PF-when-VFs-exist.patch * Backport 11: https://launchpadlibrarian.net/479700798/0011-s390-pci- Documentation-for-zPCI.patch * Backport 12: https://launchpadlibrarian.net/479700799/0012-s390-pci- removes-wrong-PCI-multifunction-assignment.patch [Test Case] * Prepare an IBM z13 or LinuxONE III (or newer) system with two or more RoCE Express PCI 2(.1) adapters. * Assign the adapters (and it's virtual functions) to an LPAR. * Verify whether the physical and virtual functions are grouped in arbitrary order or in consecutive order - physical first (for example with lspci -t ...) [Regression Potential] * The regression potential can be considered as moderate, since: * It is purely s390x specific code (arch/s390/* drivers/iommu/s390-iommu.c and drivers/pci/hotplug/s390_pci_hpc.c - and some doc adjustments, too). * It largely affects zPCI, the s390x specific PCI code layer. * PCI cards available for s390x are optional cards (RoCE and zEDC) and not very wide-spread. * The situation described above affects the RoCE adapters only (Mellanox based). * The patches are also upstream accepted and available via linux-next, but to apply them to focal kernel 5.4 the above backports are needed. * However, the code is modified by several patches (12), hence there is a chance to break zPCI with them. * For upfront testing a PPA got created with a focal (master-next) kernel that incl. all the above patches. __ Today, the enumeration of PCI functions on s390x does not reflect which functions belongs to which physical adapter. Layout of a PCI function address on Linux: :00:00.0 ::. On s390x, each function is presented as individual root complex today, e.g.: PCHID 0100 VF1 :00:00.0 PCHID 0100 VF23 0001:00:00.0 PCHID 0200 VF1 0002:00:00.0 OCHID 0100 VF17 0003:00:00.0 On other platforms, the addresses correctly reflect the actual HW configuration. Some device drivers (mlx5 for Mellanox adapters) group functions of one physical adapter by checking which PCI functions have identical values for ::. We need to use the same enumeration scheme to achieve this functionality on s390x.
