[Kernel-packages] [Bug 1762448] Re: Enable Tunneled Operations on POWER9
** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1762448 Title: Enable Tunneled Operations on POWER9 Status in The Ubuntu-power-systems project: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Bug description: == Comment: #0 - Philippe Bergheaud - 2018-04-09 09:15:22 == ---Problem Description--- PCI and CAPI Tunneled operations for POWER9 do not operate ---uname output--- Linux zzfp088p01 4.16.0-rc7-00062-g0b41260-dirty #5 SMP Wed Apr 4 14:48:53 CEST 2018 ppc64le ppc64le ppc64le GNU/Linux ---Additional Hardware Info--- POWER9 + CAPI card with MemCpy 2.0 Directed Mode AFU for PSL9 Machine Type = power9 ppc64le ---Debugger--- A debugger is not configured ---Steps to Reproduce--- AFU sends as_notify message ; host thread does not wake up Stack trace output: no Oops output: no System Dump Info: The system is not configured to capture a system dump. == Comment: #1 - Philippe Bergheaud - 2018-04-09 09:20:35 == The following mainline linux patches solve the issue: https://github.com/torvalds/linux/commit/d6a90bb83b50 powerpc/powernv: Enable tunneled operations https://github.com/torvalds/linux/commit/9dbcbfa1fe0c cxl: read PHB indications from the device tree To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1762448/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1762462] Re: PSL traces reset after PERST for debug AFU image
** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1762462 Title: PSL traces reset after PERST for debug AFU image Status in The Ubuntu-power-systems project: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Bug description: == Comment: #0 - Vaibhav Jain - 2018-04-09 05:20:18 == ---Problem Description--- Presently the Trace Data on the PSL is lost when it encounters a PERST signal. This is usually a major inconvenience during EEH debugging as PSL traces are needed to investigate the EEH cause. To fix this we enable the NORST bit by default for debug afu images to prevent reset of AFU trace-data on a PCI link drop. For production AFU images this bit is always ignored and PSL gets reconfigured anyways thereby resetting the trace data. So setting this bit for non-debug images doesn't have any impact. Fix for this issue was merged to mainline kernel via commit: 03ebb419b896 cxl: Enable NORST bit in PSL_DEBUG register for PSL9 ---Additional Hardware Info--- Flash GT+ adapter with 180323P1 Image Machine Type = Boston-LC ---Steps to Reproduce--- 1. Enable traces on the card with psl_trace_dump tool. 2. Inject an EEH. 3. Try to dump the traces from PSL via psl_trace_dump. ---uname output--- 4.15.0-12-generic ---Debugger--- A debugger is not configured System Dump Info: The system is not configured to capture a system dump. Stack trace output: no Oops output: no To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1762462/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1774964] Re: [LTCTest][OPAL][OP910.20] WARNING: CPU: 97 PID: 11965 at /build/linux-0zaMZw/linux-4.15.0/kernel/sched/core.c:1189 set_task_cpu+0x240/0x250
** Tags added: cscc
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1774964
Title:
[LTCTest][OPAL][OP910.20] WARNING: CPU: 97 PID: 11965 at /build/linux-
0zaMZw/linux-4.15.0/kernel/sched/core.c:1189 set_task_cpu+0x240/0x250
Status in The Ubuntu-power-systems project:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Bionic:
Fix Released
Bug description:
== SRU Justification ==
IBM reports seeing the following during their testing:
WARNING: CPU: 97 PID: 11965 at
/build/linux-0zaMZw/linux-4.15.0/kernel/sched/core.c:1189
set_task_cpu+0x240/0x250
This is a regression and was introduced by the following two commits in
v4.15-rc1:
01eaac2b0591 ("powerpc/mce: Hookup ierror (instruction) UE errors")
ba41e1e1ccb9 ("powerpc/mce: Hookup derror (load/store) UE errors")
This regression is fixed by commit 75ecfb49516c in v4.17-rc3. The
commit was also cc'd to upstream stable, but it is being SRU'd to get
the fix into Ubuntu without waiting for it to come down via stable
updates.
== Fix ==
75ecfb49516c ("powerpc/mce: Fix a bug where mce loops on memory UE.")
== Regression Potential ==
Low. Limited to powerpc. The commit was also cc'd to upstream stable
so it will recieve additional upstream stable review.
== Test Case ==
A test kernel was built with this patch and tested by the original bug
reporter.
The bug reporter states the test kernel resolved the bug.
== Original Bug Descriptions ==
== Comment: #0 - PAVAMAN SUBRAMANIYAM <> - 2018-04-25 01:59:10 ==
---Problem Description---
WARNING: CPU: 97 PID: 11965 at
/build/linux-0zaMZw/linux-4.15.0/kernel/sched/core.c:1189
set_task_cpu+0x240/0x250
---uname output---
Linux ltc-wspoon8 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:14:44 UTC
2018 ppc64le ppc64le ppc64le GNU/Linux
Machine Type = P9
---Debugger---
A debugger is not configured
---Steps to Reproduce---
Install a P9 Open Power Hardware with the latest OP910.20 Firmware images.
root@witherspoon:~# cat /etc/os-release
ID="openbmc-phosphor"
NAME="Phosphor OpenBMC (Phosphor OpenBMC Project Reference Distro)"
VERSION="ibm-v2.0"
VERSION_ID="ibm-v2.0-0-r46-0-gbed584c"
PRETTY_NAME="Phosphor OpenBMC (Phosphor OpenBMC Project Reference Distro)
ibm-v2.0"
BUILD_ID="ibm-v2.0-0-r46"
root@witherspoon:~# cat /var/lib/phosphor-software-manager/pnor/ro/VERSION
open-power-witherspoon-v1.21.2-251-ge2e9363-dirty
buildroot-2017.11-5-g65679be
skiboot-v5.10.3-op910-1-p240231e
hostboot-0aa5bed
linux-4.14.24-openpower1-p3e84190
petitboot-v1.6.6-pd7224b4
machine-xml-4af
occ-8c5b727
hostboot-binaries-9bd4056
capp-ucode-p9-dd2-v3
sbe-7e02c23
Then we have installed the Ubuntu 18.04 OS on the machine.
root@ltc-wspoon8:~# uname -a
Linux ltc-wspoon8 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:14:44 UTC
2018 ppc64le ppc64le ppc64le GNU/Linux
root@ltc-wspoon8:~# cat /etc/os-release
NAME="Ubuntu"
VERSION="18.04 LTS (Bionic Beaver)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 18.04 LTS"
VERSION_ID="18.04"
HOME_URL="https://www.ubuntu.com/;
SUPPORT_URL="https://help.ubuntu.com/;
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/;
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy;
VERSION_CODENAME=bionic
UBUNTU_CODENAME=bionic
root@ltc-wspoon8:~# cat /proc/cpuinfo | tail
cpu : POWER9, altivec supported
clock : 2300.00MHz
revision: 2.1 (pvr 004e 1201)
timebase: 51200
platform: PowerNV
model : 8335-GTC
machine : PowerNV 8335-GTC
firmware: OPAL
MMU : Radix
root@ltc-wspoon8:~# kdump-config show
DUMP_MODE:kdump
USE_KDUMP:1
KDUMP_SYSCTL: kernel.panic_on_oops=1
KDUMP_COREDIR:/var/crash
crashkernel addr:
/var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.15.0-20-generic
kdump initrd:
/var/lib/kdump/initrd.img: symbolic link to
/var/lib/kdump/initrd.img-4.15.0-20-generic
current state:ready to kdump
kexec command:
/sbin/kexec -p
--command-line="root=UUID=a2cd572c-9047-4f0a-843b-6996fae3e999 ro quiet splash
nr_cpus=1 systemd.unit=kdump-tools.service irqpoll noirqdistrib nousb"
--initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz
root@ltc-wspoon8:~# ps -ef | grep opal
root880 2 0 01:25 ?00:00:00 [kopald]
root 3604 1 2 01:25 ?00:00:03 /usr/sbin/opal-prd
root 4858 4278 0 01:28 pts/000:00:00 grep --color=auto opal
root@ltc-wspoon8:~# service opal-prd status
? opal-prd.service - OPAL PRD daemon
Loaded: loaded (/lib/systemd/system/opal-prd.service; enabled;
[Kernel-packages] [Bug 1775391] Re: kernel: Fix arch random implementation
** Tags added: cscc
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1775391
Title:
kernel: Fix arch random implementation
Status in Ubuntu on IBM z Systems:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Bionic:
Fix Released
Bug description:
== SRU Justification ==
IBM reports that arch_get_random_seed_long() invocations may slow down the
interrupt handling on heavy interrupt producing loads.
The existing random device driver calls arch_get_random_seed_long() in
interrupt context. The current implementation of this function uses the
PRNO(TRNG) instruction to provide good entropy. This instruction is
relatively slow and expensive and may slow down the capacity of interrupts
which can be handled per cpu.
This fix reworks the arch_get_random_seed implementation. It introduces a
buffer concept to decouple the delivery of random data via
arch_get_random_seed*() from the generation of new random bytes and so
does not limit the interrupt handling per cpu any more.
== Fix ==
966f53e750ae ("s390/archrandom: Rework arch random implementation.")
== Regression Potential ==
Low. This fix is limited to s390.
== Test Case ==
Verified upfront by IBM during upstream integration
Description: kernel: Fix arch random implementation
Symptom: arch_get_random_seed_long() invocations may slow down the
interrupt handling on heavy interrupt producing loads.
Problem: The existing random device driver calls
arch_get_random_seed_long() in interrupt context. The
current implementation of this function uses the
PRNO(TRNG) instruction to provide good entropy. This
instruction is relatively slow and expensive and may
slow down the capacity of interrupts which can be handled
per cpu.
Solution: This fix reworks the arch_get_random_seed implementation.
It introduces a buffer concept to decouple the delivery
of random data via arch_get_random_seed*() from the
generation of new random bytes and so does not limit
the interrupt handling per cpu any more.
Reproduction: Systems with heavy irq load show performance decrease.
Component:kernel
Upstream commit(s): kernel 4.18
966f53e750aedc5f59f9ccae6bbfb8f671c7c842
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1775391/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1775390] Re: kernel: Fix memory leak on CCA and EP11 CPRB processing.
** Tags added: cscc
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1775390
Title:
kernel: Fix memory leak on CCA and EP11 CPRB processing.
Status in Ubuntu on IBM z Systems:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Bionic:
Fix Released
Bug description:
== SRU Justification ==
Description: kernel: Fix memory leak on CCA and EP11 CPRB processing.
Symptom: Kernel memory not freed when CCA or EP11 CPRB processing fails.
Problem: kfree() in code error path missing.
Solution: Slight rework of the malloc and free places.
Reproduction: Run application which sends CCA or EP11 crypto requests
to the crypto card(s). Now switch the cards offline with
the help of chzcrypt. Monitor top or free output.
Upstream commit(s): kernel 4.18
89a0c0ec0d2e3ce0ee9caa00f60c0c26ccf11c21
== Fix ==
89a0c0ec0d2e ("s390/zcrypt: Fix CCA and EP11 CPRB processing failure memory
leak.")
== Regression Potential ==
Low. Limited to s390.
== Test Case ==
Verified upfront by IBM during upstream integration.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1775390/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1800238] Re: TechnoTrend TT-TVStick CT2-4400 (v2) stopped working with kernel 4.18
** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1800238 Title: TechnoTrend TT-TVStick CT2-4400 (v2) stopped working with kernel 4.18 Status in linux package in Ubuntu: Fix Released Bug description: Dear developer(s), I used a vdr-installation on Debian testing, before. Switched over to Ubuntu since the release of cosmic because of problems with GPU/steam under Debian. Now, I have problems to configure vdr because my TV stick doesn't seem to work with kernel 4.18. This is what I did: Installed Ubuntu, upgraded via aptitude to the latest packages, got the firmware "dvb-demod-si2168-b40-01.fw" and "dvb-tuner-si2158-a20-01.fw" (as it was recommended by *I guess it was* openelec.org and the modinfo output of si2168 and si2157), tried w_scan and failed (w_scan *can* find some signals but failes in getting the channels). That looks like this, f.e.: […} Scanning DVB-T2... 474000: (time: 01:38.796) 482000: (time: 01:43.155) 49: (time: 01:45.163) signal ok: QAM_AUTO f = 49 kHz I999B8C999D999T999G999Y999P0 (0:0:0) Info: no data from PAT after 2 seconds deleting (QAM_AUTO f = 49 kHz I999B8C999D999T999G999Y999P0 (0:0:0)) […] Now, I tried an older kernel - 4.15, because it's still in the cosmics' repository and tried w_scan again: Success, although the TV- Stick doesn't find all the channels I found with Debian Testing. So, maybe there's a regression in the latest kernel regarding the TV- Stick-driver or there is another firmware which will work better with 4.18…? Would be glad if someone could help to work that out… Greets! ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-10-generic 4.18.0-10.11 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jarosch1516 F pulseaudio /dev/snd/controlC0: jarosch1516 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Oct 26 23:32:50 2018 InstallationDate: Installed on 2018-10-24 (2 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) IwConfig: lono wireless extensions. enp3s0no wireless extensions. MachineType: BIOSTAR Group Hi-Fi A88S3+ ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.18.0-10-generic root=UUID=e5ad9e21-ba9d-4f5e-9100-374ea87d4eba ro rootflags=subvol=@ pti=off spectre_v2=off l1tf=off nospec_store_bypass_disable no_stf_barrier quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/18/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: None dmi.board.name: Hi-Fi A88S3+ dmi.board.vendor: BIOSTAR Group dmi.chassis.asset.tag: None dmi.chassis.type: 3 dmi.chassis.vendor: BIOSTAR Group dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd03/18/2015:svnBIOSTARGroup:pnHi-FiA88S3+:pvr:rvnBIOSTARGroup:rnHi-FiA88S3+:rvr:cvnBIOSTARGroup:ct3:cvr: dmi.product.family: None dmi.product.name: Hi-Fi A88S3+ dmi.product.sku: None dmi.sys.vendor: BIOSTAR Group To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1800238/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1796720] Re: High GPU temperature after kernel 4.18.0.9.10 on AMD RX460
** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1796720 Title: High GPU temperature after kernel 4.18.0.9.10 on AMD RX460 Status in Linux: Fix Released Status in linux package in Ubuntu: Confirmed Bug description: Hello, Today I have received an update for Linux kernel which upgraded the kernel on my Ubuntu 18.10 installation to 4.18.0.9.10! Immediately after restart I noticed that the GPU temperature is abnormally High... Before Update: - GPU fan set to off on idle - GPU idle temperature: 29-32 C After Update: - GPU fan set to off on idle - GPU idle temperature: 47-50 C (which I have to put the fans on 50% to keep it on 33 C) I have also tried to boot from the older kernel (4.18.0.8) and everything is normal there! System spec: - MB: ASUS Prime x299-deluxe - CPU: Intel Corei7 7820x skylake-x - GPU: AMD RX460 glxinfo | grep OpenGL: OpenGL vendor string: X.Org OpenGL renderer string: AMD Radeon (TM) RX 460 Graphics (POLARIS11, DRM 3.26.0, 4.18.0-9-generic, LLVM 7.0.0) OpenGL core profile version string: 4.5 (Core Profile) Mesa 18.2.1 OpenGL core profile shading language version string: 4.50 OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile OpenGL core profile extensions: OpenGL version string: 4.4 (Compatibility Profile) Mesa 18.2.1 OpenGL shading language version string: 4.40 OpenGL context flags: (none) OpenGL profile mask: compatibility profile OpenGL extensions: OpenGL ES profile version string: OpenGL ES 3.2 Mesa 18.2.1 OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20 OpenGL ES profile extensions: sudo cat /sys/kernel/debug/dri/0/amdgpu_pm_info: Clock Gating Flags Mask: 0x37bcf Graphics Medium Grain Clock Gating: On Graphics Medium Grain memory Light Sleep: On Graphics Coarse Grain Clock Gating: On Graphics Coarse Grain memory Light Sleep: On Graphics Coarse Grain Tree Shader Clock Gating: Off Graphics Coarse Grain Tree Shader Light Sleep: Off Graphics Command Processor Light Sleep: On Graphics Run List Controller Light Sleep: On Graphics 3D Coarse Grain Clock Gating: Off Graphics 3D Coarse Grain memory Light Sleep: Off Memory Controller Light Sleep: On Memory Controller Medium Grain Clock Gating: On System Direct Memory Access Light Sleep: Off System Direct Memory Access Medium Grain Clock Gating: On Bus Interface Medium Grain Clock Gating: Off Bus Interface Light Sleep: On Unified Video Decoder Medium Grain Clock Gating: On Video Compression Engine Medium Grain Clock Gating: On Host Data Path Light Sleep: Off Host Data Path Medium Grain Clock Gating: On Digital Right Management Medium Grain Clock Gating: Off Digital Right Management Light Sleep: Off Rom Medium Grain Clock Gating: On Data Fabric Medium Grain Clock Gating: Off GFX Clocks and Power: 1750 MHz (MCLK) 1212 MHz (SCLK) 214 MHz (PSTATE_SCLK) 300 MHz (PSTATE_MCLK) 1081 mV (VDDGFX) 18.65 W (average GPU) GPU Temperature: 39 C GPU Load: 0 % UVD: Disabled VCE: Disabled ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-9-generic 4.18.0-9.10 ProcVersionSignature: Ubuntu 4.18.0-9.10-generic 4.18.12 Uname: Linux 4.18.0-9-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: shadowfax 3078 F pulseaudio /dev/snd/controlC0: shadowfax 3078 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Oct 8 20:27:13 2018 InstallationDate: Installed on 2018-09-26 (11 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180925.1) MachineType: System manufacturer System Product Name ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-9-generic root=UUID=a58662c7-39e2-4f05-9da6-d63173c94d53 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-9-generic N/A linux-backports-modules-4.18.0-9-generic N/A linux-firmware1.175 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/03/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1503 dmi.board.asset.tag: Default string dmi.board.name: PRIME X299-DELUXE dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1503:bd08/03/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX299-DELUXE:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family:
[Kernel-packages] [Bug 1775526] Re: package linux-image-4.15.0-22-generic 4.15.0-22.24 failed to install/upgrade: installed linux-image-4.15.0-22-generic package pre-removal script subprocess returned
*** This bug is a duplicate of bug 1781001 *** https://bugs.launchpad.net/bugs/1781001 ** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1775526 Title: package linux-image-4.15.0-22-generic 4.15.0-22.24 failed to install/upgrade: installed linux-image-4.15.0-22-generic package pre- removal script subprocess returned error exit status 1 Status in linux package in Ubuntu: Confirmed Bug description: Failed to build package when installing nvidia drivers. Every time `Building initial module for 4.15.0-22-generic` is stuck. There is no antivirus on my machine. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-22-generic 4.15.0-22.24 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 NonfreeKernelModules: rfcomm bnep nouveau asus_nb_wmi asus_wmi sparse_keymap mxm_wmi intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp snd_hda_codec_realtek snd_hda_codec_hdmi snd_hda_codec_generic snd_hda_intel snd_hda_codec snd_hda_core ath3k btusb btrtl ath9k ath9k_common btbcm ath9k_hw uvcvideo btintel bluetooth videobuf2_vmalloc videobuf2_memops ath videobuf2_v4l2 videobuf2_core mac80211 videodev media mei_me mei rtsx_pci_ms memstick intel_cstate intel_rapl_perf cfg80211 shpchp lpc_ich ie31200_edac wmi mac_hid asus_wireless i915 rtsx_pci_sdmmc r8169 rtsx_pci ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Thu Jun 7 12:36:23 2018 ErrorMessage: installed linux-image-4.15.0-22-generic package pre-removal script subprocess returned error exit status 1 InstallationDate: Installed on 2018-06-05 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: linux-signed Title: package linux-image-4.15.0-22-generic 4.15.0-22.24 failed to install/upgrade: installed linux-image-4.15.0-22-generic package pre-removal script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775526/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1797296] Re: nouveau lockup
** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1797296 Title: nouveau lockup Status in linux package in Ubuntu: Triaged Status in linux source package in Cosmic: Triaged Bug description: Oct 10 11:38:30 sun kernel: [17891.545097] nouveau :03:00.0: fifo: SCHED_ERROR 0a [CTXSW_TIMEOUT] Oct 10 11:38:30 sun kernel: [17891.545109] nouveau :03:00.0: fifo: runlist 0: scheduled for recovery Oct 10 11:38:30 sun kernel: [17891.545118] nouveau :03:00.0: fifo: channel 12: killed Oct 10 11:38:30 sun kernel: [17891.545125] nouveau :03:00.0: fifo: engine 0: scheduled for recovery Oct 10 11:38:30 sun kernel: [17891.545563] nouveau :03:00.0: systemd-logind[944]: channel 12 killed! Oct 10 11:42:24 sun kernel: [18125.788110] INFO: task kworker/u32:0:14726 blocked for more than 120 seconds. Oct 10 11:42:24 sun kernel: [18125.788114] Tainted: GW 4.18.0-8-generic #9-Ubuntu Oct 10 11:42:24 sun kernel: [18125.788115] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Oct 10 11:42:24 sun kernel: [18125.788117] kworker/u32:0 D0 14726 2 0x8000 Oct 10 11:42:24 sun kernel: [18125.788154] Workqueue: events_unbound nv50_disp_atomic_commit_work [nouveau] Oct 10 11:42:24 sun kernel: [18125.788155] Call Trace: Oct 10 11:42:24 sun kernel: [18125.788161] __schedule+0x29e/0x840 Oct 10 11:42:24 sun kernel: [18125.788178] ? nvkm_ioctl_ntfy_get+0x5c/0x80 [nouveau] Oct 10 11:42:24 sun kernel: [18125.788180] schedule+0x2c/0x80 Oct 10 11:42:24 sun kernel: [18125.788181] schedule_timeout+0x258/0x360 Oct 10 11:42:24 sun kernel: [18125.788197] ? nvif_object_ioctl+0x47/0x50 [nouveau] Oct 10 11:42:24 sun kernel: [18125.788220] ? nouveau_bo_rd32+0x2a/0x30 [nouveau] Oct 10 11:42:24 sun kernel: [18125.788242] ? nv84_fence_read+0x2c/0x30 [nouveau] Oct 10 11:42:24 sun kernel: [18125.788263] ? nouveau_fence_no_signaling+0x2a/0x90 [nouveau] Oct 10 11:42:24 sun kernel: [18125.788266] dma_fence_default_wait+0x1fc/0x260 Oct 10 11:42:24 sun kernel: [18125.788267] ? dma_fence_release+0xa0/0xa0 Oct 10 11:42:24 sun kernel: [18125.788269] dma_fence_wait_timeout+0x3e/0xf0 Oct 10 11:42:24 sun kernel: [18125.788275] drm_atomic_helper_wait_for_fences+0x3f/0xc0 [drm_kms_helper] Oct 10 11:42:24 sun kernel: [18125.788309] nv50_disp_atomic_commit_tail+0x78/0x860 [nouveau] Oct 10 11:42:24 sun kernel: [18125.788311] ? __switch_to_asm+0x40/0x70 Oct 10 11:42:24 sun kernel: [18125.788312] ? __switch_to_asm+0x34/0x70 Oct 10 11:42:24 sun kernel: [18125.788333] nv50_disp_atomic_commit_work+0x12/0x20 [nouveau] Oct 10 11:42:24 sun kernel: [18125.788335] process_one_work+0x20f/0x3c0 Oct 10 11:42:24 sun kernel: [18125.788337] worker_thread+0x34/0x400 Oct 10 11:42:24 sun kernel: [18125.788339] kthread+0x120/0x140 Oct 10 11:42:24 sun kernel: [18125.788340] ? pwq_unbound_release_workfn+0xd0/0xd0 Oct 10 11:42:24 sun kernel: [18125.788341] ? kthread_bind+0x40/0x40 Oct 10 11:42:24 sun kernel: [18125.788343] ret_from_fork+0x35/0x40 Oct 10 11:44:25 sun kernel: [18246.620114] INFO: task kworker/u32:0:14726 blocked for more than 120 seconds. Oct 10 11:44:25 sun kernel: [18246.620117] Tainted: GW 4.18.0-8-generic #9-Ubuntu Oct 10 11:44:25 sun kernel: [18246.620118] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Oct 10 11:44:25 sun kernel: [18246.620120] kworker/u32:0 D0 14726 2 0x8000 Oct 10 11:44:25 sun kernel: [18246.620156] Workqueue: events_unbound nv50_disp_atomic_commit_work [nouveau] Oct 10 11:44:25 sun kernel: [18246.620157] Call Trace: Oct 10 11:44:25 sun kernel: [18246.620163] __schedule+0x29e/0x840 Oct 10 11:44:25 sun kernel: [18246.620180] ? nvkm_ioctl_ntfy_get+0x5c/0x80 [nouveau] Oct 10 11:44:25 sun kernel: [18246.620181] schedule+0x2c/0x80 Oct 10 11:44:25 sun kernel: [18246.620183] schedule_timeout+0x258/0x360 Oct 10 11:44:25 sun kernel: [18246.620197] ? nvif_object_ioctl+0x47/0x50 [nouveau] Oct 10 11:44:25 sun kernel: [18246.620221] ? nouveau_bo_rd32+0x2a/0x30 [nouveau] Oct 10 11:44:25 sun kernel: [18246.620242] ? nv84_fence_read+0x2c/0x30 [nouveau] Oct 10 11:44:25 sun kernel: [18246.620263] ? nouveau_fence_no_signaling+0x2a/0x90 [nouveau] Oct 10 11:44:25 sun kernel: [18246.620265] dma_fence_default_wait+0x1fc/0x260 Oct 10 11:44:25 sun kernel: [18246.620267] ? dma_fence_release+0xa0/0xa0 Oct 10 11:44:25 sun kernel: [18246.620268] dma_fence_wait_timeout+0x3e/0xf0 Oct 10 11:44:25 sun kernel: [18246.620274] drm_atomic_helper_wait_for_fences+0x3f/0xc0 [drm_kms_helper] Oct 10 11:44:25 sun kernel: [18246.620296] nv50_disp_atomic_commit_tail+0x78/0x860 [nouveau] Oct 10 11:44:25 sun kernel: [18246.620297] ? __switch_to_asm+0x40/0x70 Oct 10
[Kernel-packages] [Bug 1796895] Re: Kernel 4.15.0-36 network performance regression
** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1796895 Title: Kernel 4.15.0-36 network performance regression Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Bug description: Hardware: HP DL380 Gen 7 server with Gigabit interface. Ubuntu release: 18.04.1 Since upgrading from 4.15.0-33 to 4.15.0-36, I have noticed a dramatic slowdown in TCP over IPv6. Set up: two servers, Server A in US on Ubuntu 18.04.1, Server B in Europe. Test: Sending 400MB over TCP from Server B to Server A. With 4.15.0-33 on Server A, the transfer is completed in 24 seconds, with average speed of 139 mbps. With 4.15.0-36 on Server A, the same amount of data is transferred in 369 seconds, average speed less than 9 mbps. Looking at the result from tcpdump, I see that the there is a big difference in the TCP Window size. With 4.15-0.33 the TCP window size is around 3. But with 4.15-0.36, the window size is only 734. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796895/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1775486] Re: Bionic boot kernel oopses on Power
*** This bug is a duplicate of bug 1773162 *** https://bugs.launchpad.net/bugs/1773162 ** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1775486 Title: Bionic boot kernel oopses on Power Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: I'm trying to deploy Bionic to a Power S822LC (8335-GTB). The install fails because the boot kernel throws some oopses and reboots the server in an endless loop. The system powers on. Petitboot loads and populates the boot options. The system PXE boots the ephemeral boot kernel and then OOPSes and reboots, starting the cycle over. The following is the most I could get from a SOL session but it does show where the panics begin and the reboot happens at the end. The dump is from an attempt via MAAS to deploy Xenial with the 4.15 edge kernel. I also tried Bionic using the default kernel and got the same issue. Next I tried Xenial with the 4.13 kernel (hwe-16.04) and that kernel successfully boots. So the issue seems localized to the 4.15 kernel. [2.561982] vgaarb: loaded [2.562036] usbcore: registered new interface driver usbfs [2.562256] usbcore: registered new interface driver hub [2.562652] usbcore: registered new device driver usb [2.562834] pps_core: LinuxPPS API ver. 1 registered [2.563307] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti [2.589031] PTP clock support registered [2.589996] EDAC MC: Ver: 3.0.0 [2.590513] NetLabel: Initializing [2.590581] NetLabel: domain hash size = 128 [2.590613] NetLabel: protocols = UNLABELED CIPSOv4 CALIPSO [2.591086] NetLabel: unlabeled traffic allowed by default [2.592541] clocksource: Switched to clocksource timebase [2.609779] VFS: Disk quotas dquot_6.6.0 [2.610031] VFS: Dquot-cache hash table entries: 8192 (order 0, 65536 bytes) [2.613235] NET: Registered protocol family 2 [2.613651] TCP established hash table entries: 524288 (order: 6, 4194304 bytes) [2.614772] TCP bind hash table entries: 65536 (order: 4, 1048576 bytes) [2.619840] TCP: Hash tables configured (established 524288 bind 65536) [2.620414] UDP hash table entries: 65536 (order: 5, 2097152 bytes) [2.621044] UDP-Lite hash table entries: 65536 (order: 5, 2097152 bytes) [2.622142] NET: Registered protocol family 1 [2.622284] pci 0009:00:00.0: enabling device (0101 -> 0103) [2.622425] pci 0009:01:00.0: enabling device (0141 -> 0143) [2.622915] pci 0009:02:01.0: enabling device (0141 -> 0143) [2.623432] pci 0009:03:00.0: enabling device (0140 -> 0142) [2.624048] Unpacking initramfs... [3.541638] Freeing initrd memory: 53248K [3.546247] Initialise system trusted keyrings [3.546398] Key type blacklist registered [3.546548] workingset: timestamp_bits=38 max_order=23 bucket_order=0 [3.548288] zbud: loaded [3.551021] squashfs: version 4.0 (2009/01/31) Phillip Lougher [3.551827] fuse init (API version 7.26) [3.554352] Key type asymmetric registered [3.554487] Asymmetric key parser 'x509' registered [3.554785] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 244) [3.555088] io scheduler noop registered [3.555115] io scheduler deadline registered [3.10] io scheduler cfq registered (default) [3.557442] pci 0009:02:03.0: enabling device (0141 -> 0143) [3.557634] pci 0009:05:00.0: enabling device (0141 -> 0143) [3.557703] pci 0009:06:00.0: enabling device (0141 -> 0143) [3.557753] Using unsupported 1024x768 vga at 3fe28101, depth=32, pitch=4096 [3.691555] Console: switching to colour frame buffer device 128x48 [3.825001] fb0: Open Firmware frame buffer device on /pciex@3fffe4050/pci@0/pci@0/pci@3/pci@0/vga@0 [3.825359] hvc0: raw protocol on /ibm,opal/consoles/serial@0 (boot console) [3.825544] hvc0: No interrupts property, using OPAL event [3.825856] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled [3.828204] Linux agpgart interface v0.103 [3.838817] loop: module loaded [3.839111] libphy: Fixed MDIO Bus: probed [3.839213] tun: Universal TUN/TAP device driver, 1.6 [3.839350] PPP generic driver version 2.4.2 [3.839446] VFIO - User Level meta-driver version: 0.3 [3.839587] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver [3.839728] ehci-pci: EHCI PCI platform driver [3.839780] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver [3.839825] ohci-pci: OHCI PCI platform driver [3.839898] uhci_hcd: USB Universal Host Controller Interface driver [3.840232] xhci_hcd 0009:03:00.0: xHCI Host Controller [3.840298]
[Kernel-packages] [Bug 1796574] Re: Black screen on boot with AMD Radeon HD 7970/8970 OEM / R9 280X
** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1796574 Title: Black screen on boot with AMD Radeon HD 7970/8970 OEM / R9 280X Status in linux package in Ubuntu: Invalid Bug description: [1] Using the default "radeon" driver result in black screen on boot. Waiting until what looks like X finish initializing, putting the computer to sleep and awake it again almost always works as a workaround. dmesg: [5.165441] [drm:radeon_dp_link_train [radeon]] *ERROR* channel eq failed: 5 tries [5.165453] [drm:radeon_dp_link_train [radeon]] *ERROR* channel eq failed And it looks like the DisplayPort is not initialized correctly. "Black screen" in this context means nothing works (no TTY:s). [2] Disabling si_support (GCN 1.0) in grub results in system always boot correct from a shutdown state but awake from sleep doesn't work. [3] Switching to the experimental (for GCN 1.0 cards) amdgpu driver result in the same behavior as in [2]. [xrandr] DisplayPort-1 connected primary 2560x1440+0+0 (normal left inverted right x axis y axis) 597mm x 336mm 2560x1440 59.95*+ 1280x720 59.86 [lshw -c display] *-display description: VGA compatible controller product: Tahiti XT [Radeon HD 7970/8970 OEM / R9 280X] vendor: Advanced Micro Devices, Inc. [AMD/ATI] physical id: 0 bus info: pci@:02:00.0 version: 00 width: 64 bits clock: 33MHz capabilities: pm pciexpress msi vga_controller bus_master cap_list rom configuration: driver=radeon latency=0 resources: irq:57 memory:c000-cfff memory:fbe0-fbe3 ioport:e000(size=256) memory:c-d --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: andreas2086 F pulseaudio /dev/snd/controlC0: andreas2086 F pulseaudio /dev/snd/controlC1: andreas2086 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=fa1b42ae-604b-448d-a294-6578ef07f7fe InstallationDate: Installed on 2018-10-06 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: System manufacturer System Product Name Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=/dev/mapper/ubuntu--vg-root ro splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-36-generic N/A linux-backports-modules-4.15.0-36-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 12/25/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3305 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P9X79 DELUXE dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3305:bd12/25/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP9X79DELUXE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796574/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1777242] Re: 4.15.0-23-generic fails to boot in qemu on amd64 host (kernel panic)
** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1777242 Title: 4.15.0-23-generic fails to boot in qemu on amd64 host (kernel panic) Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Bug description: Trying to boot bionic with 4.15.0-23-generic fails with a kernel panic in qemu on an Debian amd64 host. The version of qemu is the current in Debian Testing: 2.12+dfsg-3. Booting with 4.15.0-22-generic works fine. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: zouzou 1274 F pulseaudio CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2017-07-12 (338 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170710) IwConfig: lono wireless extensions. ens3 no wireless extensions. MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux-signed (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 qxldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=26da642a-bbc4-440b-bed3-a911bbbfe582 ro quiet splash ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-22-generic N/A linux-backports-modules-4.15.0-22-generic N/A linux-firmware 1.173.1 RfKill: Tags: bionic Uname: Linux 4.15.0-22-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-02-07 (128 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.11.1-1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-2.8 dmi.modalias: dmi:bvnSeaBIOS:bvr1.11.1-1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.8:cvnQEMU:ct1:cvrpc-i440fx-2.8: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-2.8 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777242/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1777029] Re: fscache: Fix hanging wait on page discarded by writeback
** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1777029 Title: fscache: Fix hanging wait on page discarded by writeback Status in linux package in Ubuntu: Confirmed Status in linux source package in Trusty: Fix Released Status in linux source package in Xenial: Fix Released Status in linux source package in Artful: Won't Fix Status in linux source package in Bionic: Fix Released Bug description: == SRU Justification == [Impact] Under heavy NFS + FSCache load, a user sometimes observes a hang in __fscache_wait_on_page_write+0x5f/0xa0. Example traces: [] __fscache_wait_on_page_write+0x5f/0xa0 [fscache] [] __fscache_uncache_all_inode_pages+0xba/0x120 [fscache] [] nfs_fscache_open_file+0x4e/0xc0 [nfs] [] __fscache_wait_on_page_write+0x5f/0xa0 [fscache] [] __nfs_fscache_invalidate_page+0x2c/0x80 [nfs] [] nfs_invalidate_page+0x63/0x90 [nfs] [] truncate_inode_page+0x80/0x90 [Fix] Cherry-pick 2c98425720233ae3e135add0c7e869b32913502f from upstream, which is a patch from the FSCache maintainer. [Testcase] The user has run a NFS stress-test with a similar home-grown patch, and will run a stress test on the proposed kernel. [Regression Potential] Patch is limited to FSCache, so regression potential is limited. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777029/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1776211] Re: kdump fails to take dump with smt set to 2, hmc dumpstart
** Tags added: cscc
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://bugs.launchpad.net/bugs/1776211
Title:
kdump fails to take dump with smt set to 2, hmc dumpstart
Status in The Ubuntu-power-systems project:
Invalid
Status in linux package in Ubuntu:
Invalid
Status in makedumpfile package in Ubuntu:
Invalid
Status in linux source package in Artful:
Invalid
Status in makedumpfile source package in Artful:
Invalid
Bug description:
== SRU Justification ==
IBM has requested these three commits in Artful. In Artful, kdump fails to
capture dump when smt=2 or off.
Including these three commits allows kdump to work properly.
== Fixes ==
4388c9b3a6ee ("powerpc: Do not send system reset request through the oops
path")
04b9c96eae72 ("powerpc/crash: Remove the test for cpu_online in the IPI
callback")
4552d128c26e ("powerpc: System reset avoid interleaving oops using die
synchronisation")
== Regression Potential ==
Low. Fixes are limited to powerpc.
== Test Case ==
A test kernel was built with these patches and tested by the original bug
reporter.
The bug reporter states the test kernel resolved the bug.
--Problem Description---
kdump fails to take dump with smt set to 2, hmc dumpstart
---Issue observed---
[0.004111] Oops: Exception in kernel mode, sig: 4 [#1]
[0.004118] SMP NR_CPUS=2048
[0.004120] NUMA
[0.004125] pSeries
[0.004132] Modules linked in:
[0.004142] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 4.13.0-12-generic
#13-Ubuntu
[0.004153] task: c00046715900 task.stack: c00046134000
[0.004162] NIP: c0006468 LR: c801764c CTR:
006cdc70
[0.004173] REGS: c00047fe3ce0 TRAP: 0700 Not tainted
(4.13.0-12-generic)
[0.004181] MSR: 80081031
[0.004193] CR: 8804 XER: 2003
[0.004204] CFAR: c0006454 SOFTE: 0
[0.004204] GPR00: c801764c c00047fe3f60 c95e3000
[0.004204] GPR04: 0001 0002
ffdf
[0.004204] GPR08: 2804 0002
0002
[0.004204] GPR12: cfff c00046137f90
0b5452d8
[0.004204] GPR16: fffd 089ffd10 0136
0b55d378
[0.004204] GPR20: 0060 1eca 0a6c
0007
[0.004204] GPR24: c9621ed0
[0.004204] GPR28: c00046134000 c00046137c80
c9105df8
[0.004328] NIP [c0006468] 0xc0006468
[0.004338] LR [c801764c] __do_irq+0x4c/0x1c0
[0.004345] Call Trace:
[0.004354] [c00047fe3f60] [c801764c] __do_irq+0x4c/0x1c0
(unreliable)
[0.004368] [c00047fe3f90] [c802ab70] call_do_irq+0x14/0x24
[0.004380] [c00046137bc0] [c801785c] do_IRQ+0x9c/0x130
[0.004393] [c00046137c10] [c8008ac4]
hardware_interrupt_common+0x114/0x120
[0.004409] --- interrupt: 501 at arch_local_irq_restore+0x5c/0x90
[0.004409] LR = arch_local_irq_restore+0x40/0x90
[0.004423] [c00046137f00] [0005] 0x5 (unreliable)
[0.004436] [c00046137f20] [c8049824]
start_secondary+0x324/0x350
[0.004450] [c00046137f90] [c800aa6c]
start_secondary_prolog+0x10/0x14
[0.004460] Instruction dump:
[0.004467]
[0.004484]
[0.004506] ---[ end trace 3e5a2a9047ef3cd0 ]---
[0.004512]
[0.004518] Oops: Exception in kernel mode, sig: 4 [#2]
[0.004525] SMP NR_CPUS=2048
[0.004526] NUMA
[0.004532] pSeries
[0.004540] Modules linked in:
[0.004550] CPU: 1 PID: 0 Comm: swapper/1 Tainted: G D
4.13.0-12-generic #13-Ubuntu
[0.004561] task: c9579f00 task.stack: c95dc000
[0.004569] NIP: c0006460 LR: c80b6e80 CTR:
[0.004580] REGS: c95dfb20 TRAP: 0700 Tainted: G D
(4.13.0-12-generic)
[0.004589] MSR: 80081031
[0.004599] CR: 22002228 XER: 2004
[0.004611] CFAR: c000493c SOFTE: 0
[0.004611] GPR00: c95dfda0 c95e3000
[0.004611] GPR04:
[0.004611] GPR08: 22002228 7fff
0008
[0.004611] GPR12: cfff0a80 c00c7e137f90
09980600
[0.004611] GPR16: 1ec7 0001
[Kernel-packages] [Bug 1797092] Re: xenial guest on arm64 drops to busybox under openstack bionic-rocky
** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-snapdragon in Ubuntu. https://bugs.launchpad.net/bugs/1797092 Title: xenial guest on arm64 drops to busybox under openstack bionic-rocky Status in linux package in Ubuntu: Fix Released Status in linux-raspi2 package in Ubuntu: Fix Released Status in linux-snapdragon package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Status in linux-raspi2 source package in Xenial: Fix Released Status in linux-snapdragon source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-raspi2 source package in Bionic: Fix Released Status in linux-snapdragon source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-raspi2 source package in Cosmic: Fix Released Status in linux-snapdragon source package in Cosmic: Fix Released Bug description: [Impact] on openstack rocky-bionic (with patch, see 1771662), xenial guests will fail to launch as they drop to the busybox prompt after booting. The reason is that the EFI firmware image switched to ACPI mode by default in bionic. We knew that was happening, and backported some minimal ACPI support to keep xenial guests booting (bug 1744754). But, now we're seeing guests panic when trying to initialize PCI. [Test Case] Deploy rocky-bionic OpenStack and try to launch a xenial guest. [Fix] Backport ACPI/PCIe support for arm64 from upstream. [ Regression Risk ] TLDR: Definitely warrants some regression testing on armhf/arm64, but regression risk seems low for other architectures. Here's a patch-by-patch risk analysis: > 0001-UBUNTU-Config-CONFIG_PCI_ECAM-y.patch Enables code that will be added in the next patch. > 0002-PCI-Provide-common-functions-for-ECAM-mapping.patch Only adds new code w/ no callers yet > 0003-PCI-generic-thunder-Use-generic-ECAM-API.patch As noted in the commit message: "The patch does not introduce any functional changes other than a very minor one: with the new code, on 64-bit platforms, we do just a single ioremap for the whole config space." > 0004-PCI-of-Move-PCI-I-O-space-management-to-PCI-core-cod.patch As noted, no functional change. > 0005-PCI-Move-ecam.h-to-linux-include-pci-ecam.h.patch As noted, no functional change. > 0006-PCI-Add-parent-device-field-to-ECAM-struct-pci_confi.patch This makes changes to the ecam code, but that was added in this series, so no regression risk there. The pci-thunder-pem changes will be regression tested on the hardware that uses that driver (Cavium ThunderX). > 0007-PCI-Add-pci_unmap_iospace-to-unmap-I-O-resources.patch Only adds new code, w/ no callers yet > 0008-PCI-ACPI-Support-I-O-resources-when-parsing-host-bri.patch Adds and calls a new function that is a no-op on !ARM (PCI_IOBASE is only defined on ARM). Also adds a call to pci_unmap_iospace(), which was added in a previous patch and is also a no-op on !ARM. > 0009-UBUNTU-Config-CONFIG_ACPI_MCFG-y.patch Enables code that will be added in the next patch. > 0010-PCI-ACPI-Add-generic-MCFG-table-handling.patch Adds parsing of a new ACPI table. A possible regression risk to platforms an MCFG table that were working fine w/ 4.4 and there's a latent bug in this parsing code. > 0011-PCI-Refactor-pci_bus_assign_domain_nr-for-CONFIG_PCI.patch As noted, no functional change intended. > 0012-PCI-Factor-DT-specific-pci_bus_find_domain_nr-code-o.patch Again, no functional change. > 0013-ARM64-PCI-Add-acpi_pci_bus_find_domain_nr.patch Only impacts ARM due to CONFIG_PCI_DOMAINS_GENERIC guard > 0014-ARM64-PCI-ACPI-support-for-legacy-IRQs-parsing-and-c.patch arm64-specific PCI initialization code - mitigate risk by regression testing on supported platforms (X-Gene, ThunderX). > 0015-ARM64-PCI-Support-ACPI-based-PCI-host-controller.patch Adds new code for arm64-ACPI support. We didn't previously support these devices, so regression risk is negligible. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797092/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1775527] Re: Ubuntu16.04:KVM - xfs_log_force: error -5 returned after stress test running after a day #345
** Tags added: cscc
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1775527
Title:
Ubuntu16.04:KVM - xfs_log_force: error -5 returned after stress test
running after a day #345
Status in The Ubuntu-power-systems project:
Invalid
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Xenial:
Invalid
Bug description:
== Comment: #0 - Chanh H. Nguyen - 2016-09-08 15:01:30
==
We have installed 16.04.1 on our guest and running IO stress test against via
virtual qlogic disk. After running around 8 hrs, this error popping up
"xfs_imap_to_bp: xfs_trans_read_buf() returned error -5" then with all of these
errors "xfs_log_force: error -5 returned" fill up all the log.
Jul 19 19:03:41 tinyg2 kernel: [65047.974604] XFS (vdb9): metadata I/O error:
block 0x2f140 ("xfs_trans_read_buf_map") error 5 numblks 32
Jul 19 19:03:41 tinyg2 kernel: [65047.975885] XFS (vdb9): xfs_imap_to_bp:
xfs_trans_read_buf() returned error -5.
Jul 19 19:03:41 tinyg2 kernel: [65047.976069] XFS (vdb9):
xfs_do_force_shutdown(0x8) called from line 3433 of file
/build/linux-JQcyrX/linux-4.4.0/fs/xfs/xfs_inode.c. Return address =
0xd37951f4
Jul 19 19:03:41 tinyg2 kernel: [65047.976457] XFS (vdb9): metadata I/O error:
block 0x703d54 ("xlog_iodone") error 5 numblks 64
Jul 19 19:03:41 tinyg2 kernel: [65047.976662] XFS (vdb9):
xfs_do_force_shutdown(0x2) called from line 1197 of file
/build/linux-JQcyrX/linux-4.4.0/fs/xfs/xfs_log.c. Return address =
0xd37a4c00
Jul 19 19:03:41 tinyg2 kernel: [65047.976995] XFS (vdb9): Log I/O Error
Detected. Shutting down filesystem
Jul 19 19:03:41 tinyg2 kernel: [65047.977114] XFS (vdb9): Please umount the
filesystem and rectify the problem(s)
follow with all of these error that quickly fill up dmesg log
Jul 19 19:04:37 tinyg2 kernel: [65103.515386] XFS (vdb9): xfs_log_force:
error -5 returned.
Jul 19 19:05:07 tinyg2 kernel: [65133.595369] XFS (vdb9): xfs_log_force:
error -5 returned.
Jul 19 19:05:37 tinyg2 kernel: [65163.679358] XFS (vdb9): xfs_log_force:
error -5 returned.
Jul 19 19:06:07 tinyg2 kernel: [65193.755383] XFS (vdb9): xfs_log_force:
error -5 returned.
Jul 19 19:06:37 tinyg2 kernel: [65223.835396] XFS (vdb9): xfs_log_force:
error -5 returned.
Jul 19 19:06:51 tinyg2 kernel: [65237.091455] EXT4-fs (loop1): mounting ext2
file system using the ext4 subsystem
Jul 19 19:06:51 tinyg2 kernel: [65237.093219] EXT4-fs (loop1): mounted
filesystem without journal. Opts: (null)
Jul 19 19:06:51 tinyg2 kernel: [65237.623893] Process accounting resumed
Jul 19 19:07:07 tinyg2 kernel: [65253.919361] XFS (vdb9): xfs_log_force:
error -5 returned.
Jul 19 19:07:37 tinyg2 kernel: [65283.995393] XFS (vdb9): xfs_log_force:
error -5 returned.
Jul 19 19:08:08 tinyg2 kernel: [65314.075378] XFS (vdb9): xfs_log_force:
error -5 returned.
Jul 19 19:08:38 tinyg2 kernel: [65344.155397] XFS (vdb9): xfs_log_force:
error -5 returned.
Jul 19 19:09:08 tinyg2 kernel: [65374.235367] XFS (vdb9): xfs_log_force:
error -5 returned.
Jul 19 19:09:38 tinyg2 kernel: [65404.319354] XFS (vdb9): xfs_log_force:
error -5 returned.
Jul 19 19:10:08 tinyg2 kernel: [65434.395368] XFS (vdb9): xfs_log_force:
error -5 returned.
== Comment: #1 - Chanh H. Nguyen - 2016-09-08 15:02:27
==
We recently re-created this bug on our new system "cressg2" which is using a
different SAN on kernel -36.
My Ubuntu 16.04.1 guest, cressg2, are running the IO and other stress test,
and it is hitting "xfs_log_force: error -5 returned" problem after it runs the
tests for 15 hours. It is using our lab storage (SVC SAN storage configuation
with access to DS8000 Volume) and switch, compare to tinyg3, so it is using
different storage and fabric switch.
root@cressg2:~# uname -a
Linux cressg2 4.4.0-36-generic #55-Ubuntu SMP Thu Aug 11 18:00:57 UTC 2016
ppc64le ppc64le ppc64le GNU/Linux
[Wed Sep 7 10:26:48 2016] XFS (vdb8): xfs_log_force: error -5 returned.
[Wed Sep 7 10:27:18 2016] XFS (vdb8): xfs_log_force: error -5 returned.
[Wed Sep 7 10:27:32 2016] XFS (vdb8): xfs_log_force: error -5 returned.
[Wed Sep 7 10:27:33 2016] XFS (vdb8): xfs_log_force: error -5 returned.
[Wed Sep 7 10:27:33 2016] XFS (vdb8): xfs_log_force: error -5 returned.
[Wed Sep 7 10:27:48 2016] XFS (vdb8): xfs_log_force: error -5 returned.
[Wed Sep 7 10:27:48 2016] XFS (vdb8): xfs_log_force: error -5 returned.
[Wed Sep 7 10:27:49 2016] XFS (vdb8): xfs_log_force: error -5 returned.
[Wed Sep 7 10:27:56 2016] XFS (vdb8): xfs_log_force: error -5 returned.
[Wed Sep 7 10:28:18 2016] XFS (vdb8): xfs_log_force: error -5 returned.
[Wed Sep 7 10:28:48 2016] XFS (vdb8): xfs_log_force: error -5 returned.
[Wed Sep 7 10:29:18 2016] XFS (vdb8): xfs_log_force: error -5 returned.
To manage notifications about this bug go to:
[Kernel-packages] [Bug 1777338] Re: Linux 4.15.0-23 crashes during the boot process with a "Unable to handle kernel NULL pointer dereference" message
** Tags added: cscc
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1777338
Title:
Linux 4.15.0-23 crashes during the boot process with a "Unable to
handle kernel NULL pointer dereference" message
Status in linux package in Ubuntu:
Fix Committed
Status in linux source package in Bionic:
Fix Released
Bug description:
== SRU Justification ==
Mainline commit 1f50ddb4f418 introduced a regression. That commit added
speculative_store_bypass_ht_init() to the per-CPU initialization sequence.
However, speculative_store_bypass_ht_init() needs to be called on each CPU for
PV guests, as well.
The regresssion prevents systems from booting.
The patch to fix this regression has also been cc'd to upstream stable,
but it has not landed in Bionic as of yet.
== Fix ==
74899d92e666 ("x86/xen: Add call of speculative_store_bypass_ht_init() to PV
paths")
== Regression Potential ==
Low. This patch fixes a current regressionThis patch has also been
submitted to upstream stable, so it has had additional upstream review.
== Test Case ==
A test kernel was built with this patch and tested by the original bug
reporter.
The bug reporter states the test kernel resolved the bug.
I went to boot my computer today and it wouldn't boot.
I get an "Unable to handle kernel NULL pointer dereference" message
during the boot process, and, a bit after that, a message from the
kernel watchdog about CPU #0 being stuck. Then the boot process stops
completely.
I was able to boot the system by telling Grub to load 4.15.0-22, which
works perfectly fine, so there has been a regression.
I am running Ubuntu as a Xen dom0, if that matters. I haven't tried
booting the offending kernel version without Xen.
I'm not sure where, if anywhere, these messages go on disk, for
posting.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-23-generic 4.15.0-23.25
ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
Uname: Linux 4.15.0-22-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.9-0ubuntu7.1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun Jun 17 10:12:58 2018
InstallationDate: Installed on 2017-08-06 (314 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: linux-signed
UpgradeStatus: Upgraded to bionic on 2018-05-29 (19 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777338/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1797990] Re: kdump fail due to an IRQ storm
** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1797990 Title: kdump fail due to an IRQ storm Status in linux package in Ubuntu: Fix Released Status in linux source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux source package in Disco: Fix Released Bug description: [Impact] * A kexec/crash kernel might get stuck and fail to boot (for crash kernel, kdump fails to collect a crashdump) if a PCI device is buggy/stuck/looping and triggers a continuous flood of MSI(X) interrupts (that the kernel does not yet know about). * This fix allowed to obtain crashdumps when debugging a heavy-load scenario, in which a (heavy-loaded) network adapter wouldn't stop triggering MSI-X interrupts ever after panic()->kdump kicked in. * This fix disables MSI(X) in all PCI devices on early boot (this is OK as it's (re-)enabled normally later) with a kernel cmdline parameter (disabled by default). [Test Case] * A synthetic test-case is not yet available, however, this particular system/workload triggered the problem consistently, and it was used for development/testing. * We'll update this bug once a synthetic test-case is available; we're working on patching QEMU for this. * $ cat /proc/cmdline <...> pci=clearmsi $ dmesg | grep 'Clearing MSI' [0.00] Clearing MSI/MSI-X enable bits early in boot (quirk) * The comparison of 'dmesg -t | sort' has been reviewed between option disabled/enabled on boot & kexec modes, and only expected differences found (MHz, PIDs, MIPS). [Regression Potential] * The potential area for regressions is early boot, particularly effects of applying quirks during PCI bus scan, which is changed/broader w/ these patches. * However, all quirks are applied based on PCI ID matching, so would only apply if actually targeting a new device. * Moreover, the new quirk is only applied based on a kernel cmdline parameter that is disabled by default, which constraints even more when this is actually in effect. [Other Info] * The patch series is still under review/discussion upstream, but it's relatively important for Ubuntu users at this point, and after internal discussions we decided to submit it for SRU. * These are links to the linux-pci archive with the patches [1, 2, 3] [1] [PATCH 1/3] x86/quirks: Scan all busses for early PCI quirks https://lore.kernel.org/linux-pci/20181018183721.27467-1-gpicc...@canonical.com/ [2] [PATCH 2/3] x86/PCI: Export find_cap() to be used in early PCI code https://lore.kernel.org/linux-pci/20181018183721.27467-2-gpicc...@canonical.com/ [3] [PATCH 3/3] x86/quirks: Add parameter to clear MSIs early on boot https://lore.kernel.org/linux-pci/20181018183721.27467-3-gpicc...@canonical.com/ [Original Description] We have reports of a kdump failure in Ubuntu (in x86 machine) that was narrowed down to a MSI irq storm coming from a PCI network device. The bug manifests as a lack of progress in the boot process of the kdump kernel, and a storm of kernel messages like: [...] [ 342.265294] do_IRQ: 0.155 No irq handler for vector [ 342.266916] do_IRQ: 0.155 No irq handler for vector [ 347.258422] do_IRQ: 14053260 callbacks suppressed [...] The root cause of the issue is that the kdump kernel kexec process does not ensure PCI devices are reset and/or MSI capabilities are disabled, so a PCI device could produce a huge amount of PCI irqs which would take all the processing time for the CPU (specially since we restrict the kdump kernel to use one single CPU only). This was tested using upstream kernel version 4.18, and the problem reproduces. In the specific test scenario, the PCI NIC was an "Intel 82599ES 10-Gigabit [8086:10fb]" that was used in SR-IOV PCI passthrough mode (vfio_pci), under high load on the guest. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797990/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799237] Re: mprotect fails on ext4 with dax
** Tags added: cscc
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1799237
Title:
mprotect fails on ext4 with dax
Status in Ubuntu:
Invalid
Status in linux package in Ubuntu:
Invalid
Status in pmdk package in Ubuntu:
Invalid
Status in linux source package in Bionic:
Fix Released
Bug description:
I have a file located on ext4 mounted with "dax". When I call mmap on that
file with protection flag different than PROT_NONE and pass the returned
address to mprotect(..., PROT_NONE) it fails with:
mprotect: Permission denied
This bug affects PMDK (https://github.com/pmem/pmdk) and seems to be Ubuntu
kernel-specific.
Problem was observer on kernel 4.15.0-36-generic and 4.15.0-34-generic
Below is a code which can be used to reproduce the issue.
#include
#include
#include
#include
#include
#include
int main(int argc, char *argv[])
{
if (argc < 3) {
fprintf(stderr, "usage %s file size\n",
argv[0]);
return 1;
}
int size = atoi(argv[2]);
int fd = open(argv[1], O_RDWR);
if (fd < 0) {
perror("open");
return 1;
}
void *addr = mmap(NULL, size, PROT_READ | PROT_WRITE,
MAP_SHARED, fd, 0);
if (addr == MAP_FAILED) {
perror("mmap");
return 1;
}
if(mprotect(addr, size, PROT_NONE)) {
perror("mprotect");
return 1;
}
return 0;
}
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211
not found.
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2018-10-23 (0 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64
(20180725)
IwConfig:
lono wireless extensions.
enp0s3no wireless extensions.
Lsusb:
Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: innotek GmbH VirtualBox
Package: linux (not installed)
ProcFB:
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic
root=UUID=48e87c4c-3028-4252-b7bb-e1e6091ff7f6 ro quiet splash
ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
RelatedPackageVersions:
linux-restricted-modules-4.15.0-36-generic N/A
linux-backports-modules-4.15.0-36-generic N/A
linux-firmware 1.173.1
RfKill:
Tags: bionic
Uname: Linux 4.15.0-36-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 12/01/2006
dmi.bios.vendor: innotek GmbH
dmi.bios.version: VirtualBox
dmi.board.name: VirtualBox
dmi.board.vendor: Oracle Corporation
dmi.board.version: 1.2
dmi.chassis.type: 1
dmi.chassis.vendor: Oracle Corporation
dmi.modalias:
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
dmi.product.family: Virtual Machine
dmi.product.name: VirtualBox
dmi.product.version: 1.2
dmi.sys.vendor: innotek GmbH
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1799237/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1798182] Re: Update ENA driver to version 2.0.1K
** Tags added: cscc -- 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/1798182 Title: Update ENA driver to version 2.0.1K Status in linux package in Ubuntu: Fix Released Status in linux-aws package in Ubuntu: Fix Released Status in linux source package in Trusty: Invalid Status in linux-aws source package in Trusty: Fix Released Status in linux source package in Xenial: Fix Released Status in linux-aws source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-aws source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-aws source package in Cosmic: Fix Released Bug description: The following commits from mainline, linux-next, and net-next: Arthur Kiyanovski (18): net: ena: fix warning in rmmod caused by double iounmap net: ena: fix rare bug when failed restart/resume is followed by driver removal net: ena: fix NULL dereference due to untimely napi initialization net: ena: fix auto casting to boolean net: ena: minor performance improvement net: ena: complete host info to match latest ENA spec net: ena: introduce Low Latency Queues data structures according to ENA spec net: ena: add functions for handling Low Latency Queues in ena_com net: ena: add functions for handling Low Latency Queues in ena_netdev net: ena: use CSUM_CHECKED device indication to report skb's checksum status net: ena: explicit casting and initialization, and clearer error handling net: ena: limit refill Rx threshold to 256 to avoid latency issues net: ena: change rx copybreak default to reduce kernel memory pressure net: ena: remove redundant parameter in ena_com_admin_init() net: ena: update driver version to 2.0.1 net: ena: fix indentations in ena_defs for better readability net: ena: enable Low Latency Queues net: ena: fix compilation error in xtensa architecture Eric Dumazet (1): net: ena: remove ndo_poll_controller Netanel Belgazal (1): net: ena: Fix Kconfig dependency on X86 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798182/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1776887] Re: Critical upstream bugfix missing in Ubuntu 18.04 - frequent Xorg crash after suspend
** Tags added: cscc
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1776887
Title:
Critical upstream bugfix missing in Ubuntu 18.04 - frequent Xorg crash
after suspend
Status in linux package in Ubuntu:
Triaged
Status in linux source package in Bionic:
Fix Committed
Bug description:
== SRU Justification ==
This upstream bug has been confirmed to affect Ubuntu users[1]. As
per the fix commit (below), the most frequent symptom is a crash of
Xorg/Xwayland, i.e. killing the entire GUI, when a laptop is woken
from system sleep. Frequency of the bug is described as once every
few days[2].
[1] E.g. this user confirms the bug & very specific workaround:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1760450/comments/11
[2] E.g. this log of crashes:
https://bugzilla.redhat.com/show_bug.cgi?id=1553979#c23
This is a bug in blk-core.c. It is not specific to any one hardware
driver. Technically the suspend bug is triggered by the SCSI core -
which is used by *all SATA devices*.
The commit also includes a test which quickly and reliably proves the
existence of a horrifying bug.
I guess you might avoid this bug only if you have root on NVMe. The
other way to not hit the Xorg crash is if you don't use all your RAM,
so there's no pressure that leads to cold pages of Xorg being swapped.
Also, you won't reproduce the Xorg crash if you suspend+resume
immediately. (This frustrated my tests at one point, it only
triggered after left the system suspended over lunch :).
Fix: "block: do not use interruptible wait anywhere"
in kernel 4.17:
https://github.com/torvalds/linux/commit/1dc3039bc87ae7d19a990c3ee71cfd8a9068f428
in kernel 4.16.8:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-
stable.git/commit/?h=linux-4.16.y=7859056bc73dea2c3714b00c83b253d4c22bf7b6
lack of fix in 4.15.0-24.26 (ubuntu 18.04): https://git.launchpad.net
/~ubuntu-kernel/ubuntu/+source/linux/+git/bionic/tree/block/blk-
core.c?id=Ubuntu-4.15.0-24.26#n856
I.e., this bug is still present in Ubuntu source package
linux-4.15.0-24.26 (and 4.15.0-23.25). I attach hardware details
(lspci-vnvn.log) of a system where this bug is known to happen.
Regards
Alan
WORKAROUND: Use kernel parameter:
scsi_mod.scan=sync
== Fix ==
1dc3039bc87a ("block: do not use interruptible wait anywhere")
== Regression Potential ==
Low. This patch has been sent to stable, so it has had additional
upstream review.
== Test Case ==
A test kernel was built with this patch and tested by the original bug
reporter.
The bug reporter states the test kernel resolved the bug.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776887/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1801574] Re: [cosmic] ipoib ping with large message size failed
** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1801574 Title: [cosmic] ipoib ping with large message size failed Status in linux package in Ubuntu: Confirmed Bug description: We see that ping over ipoib interface stuck with large packets, this is a new degradation, this test pass on Ubuntu 18.04. After investigating the issue, we see that commit [1] introduce the issue, and it is not an upstream commit, it is canonical commit. Could you please check with the canonical kernel team why they revert that commit? To reproduce the bug, please use ConnectX-3 devices with ipoib connection with 2044 MTU (default) and run command [2]. Is there open Launchpad on it? [1] commit 77a24c313d21e3765b04d90521e9228a9bb6e332 Author: Tyler Hicks Date: Fri Aug 3 21:53:15 2018 + Revert "net: increase fragment memory usage limits" This reverts commit c2a936600f78aea00d3312ea4b66a79a4619f9b4. It made denial of service attacks on the IP fragment handling easier to carry out. CVE-2018-5391 Signed-off-by: Tyler Hicks Signed-off-by: Stefan Bader [2] ping 13.194.22.1 -I 13.194.23.1 -s 65507 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801574/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1796904] Re: [Bionic] Update ThunderX2 implementation defined pmu core events
** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1796904 Title: [Bionic] Update ThunderX2 implementation defined pmu core events Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Fix Released Bug description: [IMPACT] === The ARM architecture defines several events as part of the Performance Monitor Unit (PMU) Extension. In addition, Cavium has added "implementation defined" pmu core events, which Cavium deems most useful for analyzing performance. Currently perf does not list these "implementation defined" events. [FIX] b9b77222d4ff perf vendor events arm64: Update ThunderX2 implementation defined pmu core events [TEST] With the patch applied perf lists the additional PMU events. ubuntu@starbuck:~$ perf list List of pre-defined events (to be used in -e): armv8_pmuv3_0/br_immed_retired/[Kernel PMU event] armv8_pmuv3_0/br_mis_pred/ [Kernel PMU event] armv8_pmuv3_0/br_mis_pred_retired/ [Kernel PMU event] armv8_pmuv3_0/br_pred/ [Kernel PMU event] armv8_pmuv3_0/br_retired/ [Kernel PMU event] armv8_pmuv3_0/br_return_retired/ [Kernel PMU event] armv8_pmuv3_0/bus_access/ [Kernel PMU event] armv8_pmuv3_0/bus_cycles/ [Kernel PMU event] armv8_pmuv3_0/cid_write_retired/ [Kernel PMU event] armv8_pmuv3_0/cpu_cycles/ [Kernel PMU event] armv8_pmuv3_0/exc_return/ [Kernel PMU event] armv8_pmuv3_0/exc_taken/ [Kernel PMU event] armv8_pmuv3_0/inst_retired/[Kernel PMU event] armv8_pmuv3_0/inst_spec/ [Kernel PMU event] armv8_pmuv3_0/l1d_cache/ [Kernel PMU event] armv8_pmuv3_0/l1d_cache_allocate/ [Kernel PMU event] armv8_pmuv3_0/l1d_cache_refill/[Kernel PMU event] armv8_pmuv3_0/l1d_cache_wb/[Kernel PMU event] armv8_pmuv3_0/l1d_tlb/ [Kernel PMU event] armv8_pmuv3_0/l1d_tlb_refill/ [Kernel PMU event] armv8_pmuv3_0/l1i_cache/ [Kernel PMU event] armv8_pmuv3_0/l1i_cache_refill/[Kernel PMU event] armv8_pmuv3_0/l1i_tlb/ [Kernel PMU event] armv8_pmuv3_0/l1i_tlb_refill/ [Kernel PMU event] armv8_pmuv3_0/l2d_cache/ [Kernel PMU event] armv8_pmuv3_0/l2d_cache_allocate/ [Kernel PMU event] armv8_pmuv3_0/l2d_cache_refill/[Kernel PMU event] armv8_pmuv3_0/l2d_cache_wb/[Kernel PMU event] armv8_pmuv3_0/l2d_tlb/ [Kernel PMU event] armv8_pmuv3_0/l2d_tlb_refill/ [Kernel PMU event] armv8_pmuv3_0/ld_retired/ [Kernel PMU event] armv8_pmuv3_0/mem_access/ [Kernel PMU event] armv8_pmuv3_0/st_retired/ [Kernel PMU event] armv8_pmuv3_0/stall_backend/ [Kernel PMU event] armv8_pmuv3_0/stall_frontend/ [Kernel PMU event] armv8_pmuv3_0/sw_incr/ [Kernel PMU event] armv8_pmuv3_0/ttbr_write_retired/ [Kernel PMU event] armv8_pmuv3_0/unaligned_ldst_retired/ [Kernel PMU event] core imp def: bus_access_rd [Bus access read] bus_access_wr [Bus access write] exc_dabort [Exception taken, Data Abort and SError] exc_fiq [Exception taken, FIQ] exc_hvc [Exception taken, Hypervisor Call] exc_irq [Exception taken, IRQ] exc_pabort [Exception taken, Instruction Abort] exc_smc [Exception taken, Secure Monitor Call] exc_svc [Exception taken, Supervisor Call] exc_trap_dabort [Exception taken, Data Abort or SError not taken locally] exc_trap_fiq [Exception taken, FIQ not taken locally] exc_trap_irq [Exception taken, IRQ not taken locally] exc_trap_other [Exception taken, Other traps not taken locally] exc_trap_pabort [Exception taken, Instruction Abort not taken locally] exc_undef [Exception taken, Other synchronous] l1d_cache_inval [L1D cache invalidate] l1d_cache_rd [L1D cache access, read] l1d_cache_refill_inner [L1D cache refill, inner] l1d_cache_refill_outer [L1D cache refill, outer] l1d_cache_refill_rd [L1D
[Kernel-packages] [Bug 1799497] Re: 4.15 kernel hard lockup about once a week
** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1799497 Title: 4.15 kernel hard lockup about once a week Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Bug description: My main server has been running into hard lockups about once a week ever since I switched to the 4.15 Ubuntu 18.04 kernel. When this happens, nothing is printed to the console, it's effectively stuck showing a login prompt. The system is running with panic=1 on the cmdline but isn't rebooting so the kernel isn't even processing this as a kernel panic. As this felt like a potential hardware issue, I had my hosting provider give me a completely different system, different motherboard, different CPU, different RAM and different storage, I installed that system on 18.04 and moved my data over, a week later, I hit the issue again. We've since also had a LXD user reporting similar symptoms here also on varying hardware: https://github.com/lxc/lxd/issues/5197 My system doesn't have a lot of memory pressure with about 50% of free memory: root@vorash:~# free -m totalusedfree shared buff/cache available Mem: 31819 17574 402 513 13842 13292 Swap: 159092687 13222 I will now try to increase console logging as much as possible on the system in the hopes that next time it hangs we can get a better idea of what happened but I'm not too hopeful given the complete silence on the console when this occurs. System is currently on: Linux vorash 4.15.0-36-generic #39-Ubuntu SMP Mon Sep 24 16:19:09 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux But I've seen this since the GA kernel on 4.15 so it's not a recent regression. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Oct 23 16:12 seq crw-rw 1 root audio 116, 33 Oct 23 16:12 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.4 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: Cannot stat file /proc/22822/fd/10: Permission denied Cannot stat file /proc/22831/fd/10: Permission denied DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=none CRYPTSETUP=n IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 046b:ff10 American Megatrends, Inc. Virtual Keyboard and Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Intel Corporation S1200SP NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair 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 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic root=UUID=575c878a-0be6-4806-9c83-28f67aedea65 ro biosdevname=0 net.ifnames=0 panic=1 verbose console=tty0 console=ttyS0,115200n8 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-38-generic N/A linux-backports-modules-4.15.0-38-generic N/A linux-firmware 1.173.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux 4.15.0-38-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: False dmi.bios.date: 01/25/2018 dmi.bios.vendor: Intel Corporation dmi.bios.version: S1200SP.86B.03.01.1029.012520180838 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: S1200SP dmi.board.vendor: Intel Corporation dmi.board.version: H57532-271 dmi.chassis.asset.tag: dmi.chassis.type: 23 dmi.chassis.vendor: ... dmi.chassis.version: .. dmi.modalias: dmi:bvnIntelCorporation:bvrS1200SP.86B.03.01.1029.012520180838:bd01/25/2018:svnIntelCorporation:pnS1200SP:pvr:rvnIntelCorporation:rnS1200SP:rvrH57532-271:cvn...:ct23:cvr..: dmi.product.family: Family dmi.product.name: S1200SP dmi.product.version: dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1799497/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to :
[Kernel-packages] [Bug 1777194] Re: Hard LOCKUP observed on stressing Ubuntu 18 04
** Tags added: cscc
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1777194
Title:
Hard LOCKUP observed on stressing Ubuntu 18 04
Status in The Ubuntu-power-systems project:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Bionic:
Fix Released
Bug description:
== SRU Justification ==
IBM has seen hard lockups when running stress tests against Bionic.
These test sometimes lead to rcu_stalls. IBM found that this bug is
resolved with commits 6bed3237624e and ac61c1156623.
== Fixes ==
6bed3237624e ("powerpc: use NMI IPI for smp_send_stop")
ac61c1156623 ("powerpc: Fix smp_send_stop NMI IPI handling")
== Regression Potential ==
Low. Limited to powerpc.
== Test Case ==
A test kernel was built with these patches and tested by the original bug
reporter.
The bug reporter states the test kernel resolved the bug.
--Problem Description--
Hard LOCKUP on stressing Ubuntu 18 04
---Issue observed---
Hard LOCKUP on stressing Ubuntu 18 04 using Ubuntu 18 04, sometimes leads to
rcu_stalls.
Apr 17 00:00:23 lep8d kernel: [ 4309.786755] Watchdog CPU:3 Hard LOCKUP
Apr 17 00:00:23 lep8d kernel: [ 4309.786759] Modules linked in: algif_rng
salsa20_generic userio camellia_generic cast6_generic cast_common snd_seq
snd_seq_device snd_timer snd soundcore vhost_net serpent_generic tap
twofish_generic twofish_common vhost_vsock vmw_vsock_virtio_transport_common
vhost vsock lrw unix_diag algif_skcipher cuse sctp tgr192 wp512 rmd320 rmd256
rmd160 hci_vhci rmd128 bluetooth ecdh_generic dccp_ipv4 md4 uhid hid algif_hash
dccp af_alg xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4
iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack
nf_conntrack libcrc32c ipt_REJECT nf_reject_ipv4 xt_tcpudp bridge stp llc
ebtable_filter ebtables devlink ip6table_filter ip6_tables iptable_filter
kvm_hv kvm binfmt_misc uio_pdrv_genirq uio vmx_crypto ibmpowernv
powernv_op_panel ipmi_powernv
Apr 17 00:00:23 lep8d kernel: [ 4309.786899] ipmi_devintf ipmi_msghandler
powernv_rng leds_powernv crct10dif_vpmsum sch_fq_codel ip_tables x_tables
autofs4 ses enclosure scsi_transport_sas btrfs xor zstd_compress raid6_pq uas
usb_storage crc32c_vpmsum tg3 ipr
Apr 17 00:00:23 lep8d kernel: [ 4309.786944] CPU: 3 PID: 28361 Comm:
stress-ng-hrtim Not tainted 4.15.0-15-generic #16-Ubuntu
Apr 17 00:00:23 lep8d kernel: [ 4309.786950] NIP: c0d0c8b8 LR:
c0120dbc CTR: c0024480
Apr 17 00:00:23 lep8d kernel: [ 4309.786956] REGS: c7f7fd80 TRAP:
0900 Not tainted (4.15.0-15-generic)
Apr 17 00:00:23 lep8d kernel: [ 4309.786957] MSR: 90009033
CR: 28000442 XER: 2000
Apr 17 00:00:23 lep8d kernel: [ 4309.786972] CFAR: c0120db8 SOFTE: 0
Apr 17 00:00:23 lep8d kernel: [ 4309.786972] GPR00: c0120dbc
c02d51377ba0 c16eb400 c02d512b0f88
Apr 17 00:00:23 lep8d kernel: [ 4309.786972] GPR04:
0001 01f40668 0001
Apr 17 00:00:23 lep8d kernel: [ 4309.786972] GPR08: 0001
8003
Apr 17 00:00:23 lep8d kernel: [ 4309.786972] GPR12: c0024480
c7a22100 000186a0
Apr 17 00:00:23 lep8d kernel: [ 4309.786972] GPR16: 7fffed3687e0
0abda98e5db8 8005 00040100
Apr 17 00:00:23 lep8d kernel: [ 4309.786972] GPR20:
418004fc 003c 0843
Apr 17 00:00:23 lep8d kernel: [ 4309.786972] GPR24: c02d512b0f88
c02d51377d30 c02d52d47c00
Apr 17 00:00:23 lep8d kernel: [ 4309.786972] GPR28: c02d51377d50
c02d51377d50 c02d52f04500 c02d512b0f88
Apr 17 00:00:23 lep8d kernel: [ 4309.787035] NIP [c0d0c8b8]
_raw_spin_lock+0x38/0xe0
Apr 17 00:00:23 lep8d kernel: [ 4309.787045] LR [c0120dbc]
dequeue_signal+0xcc/0x260
Apr 17 00:00:23 lep8d kernel: [ 4309.787046] Call Trace:
Apr 17 00:00:23 lep8d kernel: [ 4309.787052] [c02d51377bd0]
[c0120dac] dequeue_signal+0xbc/0x260
Apr 17 00:00:23 lep8d kernel: [ 4309.787059] [c02d51377c20]
[c012459c] get_signal+0x13c/0x7a0
Apr 17 00:00:23 lep8d kernel: [ 4309.787066] [c02d51377d10]
[c001dacc] do_signal+0x7c/0x2c0
Apr 17 00:00:23 lep8d kernel: [ 4309.787072] [c02d51377e00]
[c001deb0] do_notify_resume+0xd0/0x100
Apr 17 00:00:23 lep8d kernel: [ 4309.787083] [c02d51377e30]
[c000b7c4] ret_from_except_lite+0x70/0x74
Apr 17 00:00:23 lep8d kernel: [ 4309.787085] Instruction dump:
Apr 17 00:00:23 lep8d kernel: [ 4309.787090] 7c0802a6 6000 fbe1fff8
f821ffd1 7c7f1b78 3940 994d028c 814d0008
Apr 17 00:00:23 lep8d kernel: [ 4309.787102] 7d201829 2c09 40c20010
[Kernel-packages] [Bug 1815033] Re: qlcnic: Firmware aborts/hangs in QLogic NIC
** Tags added: cscc
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1815033
Title:
qlcnic: Firmware aborts/hangs in QLogic NIC
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Bionic:
Fix Released
Bug description:
[Impact]
* In multi-queue configurations for qlcnic driver, there is a corner case
in which TX queue zero is used at same time for regular data transmission
by one CPU while another uses the same queue descriptor for MAC
configuration.
* When such "race" indeed happens, it could lead to TX queue zero corruption,
triggering as net result firmware aborts/hangs out of nowhere. The following
kernel log messages were collected during the corruption event:
qlcnic :01:00.0: Pause control frames disabled on all ports
qlcnic :01:00.0: firmware hang detected
qlcnic :01:00.0: Dumping hw/fw registers
PEG_HALT_STATUS1: 0x40001502, PEG_HALT_STATUS2: 0x3de7a0,
PEG_NET_0_PC: 0x6d268, PEG_NET_1_PC: 0x6d2ac,
PEG_NET_2_PC: 0x149, PEG_NET_3_PC: 0x6e105,
PEG_NET_4_PC: 0x1e00b
[...]
qlcnic :01:00.0: Detected state change from DEV_NEED_RESET, skipping
ack check
* The following device is known to suffer from the issue (lspci output),
although a whole class of devices (named 82XX series from the vendor) are
susceptible to this:
01:00.0 Ethernet controller [0200]: QLogic Corp. cLOM8214 1/10GbE
Controller [1077:8020]
* The fix is the following patch, present in mainline kernel as well as
in supported stable branches:
c333fa0c4f22 ("qlcnic: fix Tx descriptor corruption on 82xx devices").
Link for the patch in Linus tree: http://git.kernel.org/linus/c333fa0c4f22
[Test Case]
* Unfortunately this is not easy to reproduce; we have a user report of
the issue with a pretty reliable reproducer - user is running a NFS
workload on top of the above PCI adapter. His problem goes away with
the patch proposed here to SRU. His problem happens in both kernels 4.4
and 4.15, and the patch fixes it for both of them.
(Notice this is a Bionic-only SRU, since Ubuntu 4.4 kernel got the patch
from Greg's supported stable branch).
[Regression Potential]
* The patch scope is restricted to a single driver, and the code itself
is self-contained - basically a restriction to specific tx_ring when
setting filters. There is potential for regressions in this path for
the driver which could cause different firmware issues for example,
but the user testing exhibited great reliability - without the patch
issue happens after ~6h of machine boot. With the patch the machine ran
for more than 8 days without issues.
* Also the patch is present in mainline kernel as well as supported
stable branches, and is already present in Ubuntu 4.4 kernel.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1815033/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1775732] Re: arm64 soft lock crashes on nova-compute charm running
** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1775732 Title: arm64 soft lock crashes on nova-compute charm running Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Bug description: Discovered on bionic, arm64 (Moonshot, verified on multiple swirlix cartridges), 4.15.0-22-generic. After deploying the nova-compute Juju charm, on subsequent reboots, within a few seconds after complete boot, everything will freeze and eventually display on the serial console (just these, no traces): [ 188.010510] watchdog: BUG: soft lockup - CPU#1 stuck for 23s! [juju-log:2272] [ 216.010292] watchdog: BUG: soft lockup - CPU#1 stuck for 23s! [juju-log:2272] (From here on, "lock up" refers to that sequence: boot a kernel, it completes boot to login prompt, then everything freezes a few seconds later, then BUGs.) It's usually but not always juju-log, sometimes a relation-ids or similar. I was able to briefly notice that it was in its startup config-changed hook. I've separated out and tested nearly everything it does during its startup config-changed (sets up bridging, writes some config files, restarts libvirtd/nova-compute/etc) without being able to trigger the bug, but I suspect proximity to boot is a factor. If I disable jujud- unit-nova-compute startup, boot, log in, re-enable and start (by which time over a minute or so has elapsed from boot finish), it will not lock up. Similarly, if I wrap the jujud startup in a `strace -Ff -o /var/log/strace.log` (which slows it down massively), it will not lock up. Watched pot syndrome. I've tried kernels from http://kernel.ubuntu.com/~kernel-ppa/mainline/ . I noticed most of the recent arm64 mainline kernels had failed builds, notified the kernel team channel and apw fixed the issue and started some rebuilds. What I've discovered (after many dead ends and a futile bisection) is that mainline builds before the rebuilds lock up, but fixed mainline builds initiated by apw DO NOT lock up. e.g. 4.16.3-041603.201804190730 locks up, but 4.16.6-041606.201806042022 does not lock up. (4.16.4 and 4.16.5 appear to have never been rebuilt and don't have arm64 debs, and that period is what I tried to bisect after figuring a fix must be in there.) But when I try to compile any of these recent kernels myself, they lock up when booted. Same kernel configs, tried on both bionic and in a cosmic chroot, tried both native arm64 compile and cross-compile from amd64. e.g. 4.16.6-041606.201806042022 from k.u.c does not lock up, but when I build it myself, it does. TBC, I've verified lock ups on the following kernels (all assume kernel configs from their respective Ubuntu or k.u.c mainline builds): - 4.15.0-22-generic from bionic (both Ubuntu-provided and my own recompile) - v4.16 (and all point releases) - v4.17 As I write this, my compiled v4.10 DOES NOT appear to lock up. I will attempt to bisect at a macro level from 4.10..4.15 and dig deeper. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-22-generic 4.15.0-22.24 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic aarch64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 2 04:22 seq crw-rw 1 root audio 116, 33 Jun 2 04:22 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.2 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Fri Jun 8 00:13:05 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: console=ttyS0,9600n8r ro RelatedPackageVersions: linux-restricted-modules-4.15.0-22-generic N/A linux-backports-modules-4.15.0-22-generic N/A linux-firmware 1.173.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775732/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1797963] Re: not able to unwind the stack from within __kernel_clock_gettime in the Linux vDSO
** Tags added: cscc
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1797963
Title:
not able to unwind the stack from within __kernel_clock_gettime in the
Linux vDSO
Status in The Ubuntu-power-systems project:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Bionic:
Fix Released
Status in linux source package in Cosmic:
Fix Released
Bug description:
== SRU Justification ==
IBM is requesting this commit in Bionic and Cosmic. They report that they
are not able to unwind the stack from within __kernel_clock_gettime in the
Linux vDSO on Summit. This affects both DDT and MAP (via GDB and libunwind).
The issue is more serious than may first appear as the function appears to
be called somewhat often by the CUDA runtime, and can defer to a syscall
making it relatively time consuming (making it more likely to be encountered).
This commit is currently still in linux-next.
== Fix ==
56d20861c027 ("powerpc/vdso: Correct call frame information") linux-next
== Regression Potential ==
Low. Limited to powerpc.
Original Bug Description
We're not able to unwind the stack from within __kernel_clock_gettime
in the Linux vDSO on Summit. This affects both DDT and MAP (via GDB
and libunwind). The issue is more serious than may first appear as the
function appears to be called somewhat often by the CUDA runtime, and
can defer to a syscall making it relatively time consuming (making it
more likely to be encountered).
To reproduce:
Compile $CUDA_DIR/samples/0_Simple/matrixMul (attached is a small
patch to modify the Makefile to compile outside of the samples
directory)
Run the following GDB commands:
user@deb3qwsp1:/usr/local/cuda-10.0/samples/0_Simple/matrixMul$ gdb
./matrixMul
GNU gdb (Ubuntu 8.1-0ubuntu3) 8.1.0.20180409-git
Copyright (C) 2018 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "powerpc64le-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
[Kernel-packages] [Bug 1800639] Re: [Ubuntu] net/af_iucv: fix skb leaks for HiperTransport
** Tags added: cscc
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1800639
Title:
[Ubuntu] net/af_iucv: fix skb leaks for HiperTransport
Status in Ubuntu on IBM z Systems:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Xenial:
Fix Released
Status in linux source package in Bionic:
Fix Released
Status in linux source package in Cosmic:
Fix Released
Bug description:
== SRU Justification ==
Fix socket buffer (skb) leaks for HiperTransport
Description: net/af_iucv: fix skb leaks for HiperTransport
Symptom: Memory leaks and/or double-freed network packets.
Problem: Inbound packets may have any combination of flag bits set in
their iucv header. Current code only handles certain
combinations, and ignores (ie. leaks) all packets with other flags.
On Transmit, current code is inconsistent about whether the error
paths need to free the skb. Depending on which error path is
taken, it may either get freed twice, or leak.
Solution: On receive, drop any skb with an unexpected combination of iucv
Header flags.
On transmit, be consistent in all error paths about free'ing the skb.
== Fix ==
222440996d6daf635bed6cb35041be22ede3e8a0 ("net/af_iucv: drop inbound packets
with invalid flags")
b2f543949acd1ba64313fdad9e672ef47550d773 ("net/af_iucv: fix skb handling on
HiperTransport xmit error")
== Patch ==
commit 222440996d6daf635bed6cb35041be22ede3e8a0
Author: Julian Wiedmann
Date: Wed Sep 5 16:55:10 2018 +0200
net/af_iucv: drop inbound packets with invalid flags
Inbound packets may have any combination of flag bits set in their iucv
header. If we don't know how to handle a specific combination, drop the
skb instead of leaking it.
To clarify what error is returned in this case, replace the hard-coded
0 with the corresponding macro.
Signed-off-by: Julian Wiedmann
Signed-off-by: David S. Miller
==
commit b2f543949acd1ba64313fdad9e672ef47550d773
Author: Julian Wiedmann
Date: Wed Sep 5 16:55:11 2018 +0200
net/af_iucv: fix skb handling on HiperTransport xmit error
When sending an skb, afiucv_hs_send() bails out on various error
conditions. But currently the caller has no way of telling whether the
skb was freed or not - resulting in potentially either
a) leaked skbs from iucv_send_ctrl(), or
b) double-free's from iucv_sock_sendmsg().
As dev_queue_xmit() will always consume the skb (even on error), be
consistent and also free the skb from all other error paths. This way
callers no longer need to care about managing the skb.
Signed-off-by: Julian Wiedmann
Reviewed-by: Ursula Braun
Signed-off-by: David S. Miller
== Regression Potential ==
Low, because:
- IUCV functionality is very special to s390x and is only supported in z/VM
environments
(z/VM hypervisor to guest or guest to guest communications)
- So everything is s390x specific.
- Patch is limited to this single file: /net/iucv/af_iucv.c
- Patch was tested by IBM, and fixes an identified problem situation.
== Test Case ==
Set IUCV communication on an Ubuntu s390x system that runs as z/VM guest:
https://www.ibm.com/support/knowledgecenter/en/linuxonibm/com.ibm.linux.z.ludd/ludd_r_afiucv_setup.html
Provoke an error situation.
This is btw. hard to do, because the 'Inter-User Communication Vehicle"
(IUCV) is a virtual z/VM internal
network that does not use any real media.
To check for regressions one can use a shell over an ssh connection using an
IUCV interface
or use an application that utilises AF_IUCV sockets (like ICC).
__
Description: net/af_iucv: fix skb leaks for HiperTransport
Symptom: Memory leaks and/or double-freed network packets.
Problem: Inbound packets may have any combination of flag bits set in
their iucv header. Current code only handles certain
combinations, and ignores (ie. leaks) all packets with other
flags.
On Transmit, current code is inconsistent about whether the error
paths need to free the skb. Depending on which error path is
taken, it may either get freed twice, or leak.
Solution: On receive, drop any skb with an unexpected combination of iucv
Header flags.
On transmit, be consistent in all error paths about free'ing the
skb.
kerne 4.19
Upstream-ID: 222440996d6daf635bed6cb35041be22ede3e8a0
b2f543949acd1ba64313fdad9e672ef47550d773
Should also be applied, to all other Ubuntu Releases in the field !
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1800639/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe :
[Kernel-packages] [Bug 1828168] Re: [Surface Pro 3] Marvell 88W8897 wifi (module mwifiex) does not work
** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1828168 Title: [Surface Pro 3] Marvell 88W8897 wifi (module mwifiex) does not work Status in linux package in Ubuntu: Triaged Bug description: ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-13-generic 5.0.0-13.14 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: paul 2763 F pulseaudio /dev/snd/controlC1: paul 2763 F pulseaudio Date: Wed May 8 16:35:11 2019 InstallationDate: Installed on 2018-01-13 (480 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: Microsoft Corporation Surface Pro 3 ProcEnviron: LANGUAGE=en_AU:en TERM=xterm-256color PATH=(custom, no user) LANG=en_AU.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=2aaa6b5c-4cbb-4d78-92b5-b8f96f30eb4f ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.0.0-13-generic N/A linux-backports-modules-5.0.0-13-generic N/A linux-firmware1.178 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to disco on 2019-04-23 (14 days ago) dmi.bios.date: 06/12/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3.11.2550 dmi.board.asset.tag: 0 dmi.board.name: Surface Pro 3 dmi.board.vendor: Microsoft Corporation dmi.board.version: 1 dmi.chassis.asset.tag: 0 dmi.chassis.type: 9 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: 1 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3.11.2550:bd06/12/2018:svnMicrosoftCorporation:pnSurfacePro3:pvr1:rvnMicrosoftCorporation:rnSurfacePro3:rvr1:cvnMicrosoftCorporation:ct9:cvr1: dmi.product.family: Surface dmi.product.name: Surface Pro 3 dmi.product.sku: Surface_Pro_3 dmi.product.version: 1 dmi.sys.vendor: Microsoft Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1828168/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1777586] Re: Ubuntu Server 18.04 LTS aacraid error
** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1777586 Title: Ubuntu Server 18.04 LTS aacraid error Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Bug description: I upgraded from a previous version of Ubuntu 14.04LTS to 18.04LTS and am now running into these raid adapter driver errors. The server ran fine in older version. My apologies as I lost the exact version, but it never had any errors like this version. Now when ever I try to copy files to the RAID 5 drive, or untar a file, I get these errors now after a few MB's of written data. Linux batboat 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 18:02:16 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux batboat:/var/log$ lsb_release -rd Description: Ubuntu 18.04 LTS Release: 18.04 I have tried the IRQ debugging tips to no avail. I loaded in Debian9.4.0 and it only briefly showed this error once. But appears to be much more resilient and appears to work fine. Jun 19 00:02:21 batboat kernel: [ 498.770839] aacraid: Host adapter reset request. SCSI hang ? Jun 19 00:02:37 batboat kernel: [ 514.139167] aacraid: Host adapter reset request. SCSI hang ? Jun 19 00:02:37 batboat kernel: [ 514.795083] aacraid :03:09.0: Adapter health - 199 Jun 19 00:02:37 batboat kernel: [ 514.800376] aacraid :03:09.0: outstanding cmd: midlevel-0 Jun 19 00:02:37 batboat kernel: [ 514.800378] aacraid :03:09.0: outstanding cmd: lowlevel-0 Jun 19 00:02:37 batboat kernel: [ 514.800381] aacraid :03:09.0: outstanding cmd: error handler-0 Jun 19 00:02:37 batboat kernel: [ 514.800383] aacraid :03:09.0: outstanding cmd: firmware-5 Jun 19 00:02:37 batboat kernel: [ 514.800385] aacraid :03:09.0: outstanding cmd: kernel-0 Jun 19 00:02:37 batboat kernel: [ 514.800391] sd 4:0:0:0: Device offlined - not ready after error recovery Jun 19 00:02:37 batboat kernel: [ 514.800394] sd 4:0:0:0: Device offlined - not ready after error recovery Jun 19 00:02:37 batboat kernel: [ 514.800396] sd 4:0:0:0: Device offlined - not ready after error recovery Jun 19 00:02:37 batboat kernel: [ 514.800399] sd 4:0:0:0: Device offlined - not ready after error recovery Jun 19 00:02:37 batboat kernel: [ 514.800401] sd 4:0:0:0: Device offlined - not ready after error recovery To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777586/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1777600] Re: chzdev can't find modprobe
** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1777600 Title: chzdev can't find modprobe Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Invalid Status in s390-tools package in Ubuntu: Fix Released Status in s390-tools source package in Xenial: Fix Released Status in s390-tools source package in Bionic: Fix Released Status in s390-tools source package in Cosmic: Fix Released Bug description: [Impact] * chzdev fails to load additional kernel modules at runtime, resulting in failure to activate devices. [Test Case] $ chzdev zfcp --type datarouter=0 dbflevel=5 Should succeed, instead of erroring out / not able to find modprobe. [Regression Potential] * This corrects compiled-in path to /sbin/modprobe, thus making available previously a broken codepath of chzdev. [Other Info] * Original bug report Description: only when trying to change some attributes chzdev fails because it cant find modprobe under Ubuntu 18.04 root@m83lp09:~# chzdev zfcp --type datarouter=0 dbflevel=5 sh: 1: /usr/sbin/modprobe: not found zfcp device type configure failed Error: Command failed (exit code 127): /usr/sbin/modprobe -r zfcp root@m83lp09:~# whereis modprobe modprobe: /sbin/modprobe /etc/modprobe.d /lib/modprobe.d /usr/share/man/man8/modprobe.8.gz Potential solution ? : adding a symlink is a workaround, is this path hardcoded? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1777600/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1800278] Re: kernel linux 4.18 crashes on xiaomi notebook pro
** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1800278 Title: kernel linux 4.18 crashes on xiaomi notebook pro Status in linux package in Ubuntu: Confirmed Bug description: hello here´s my hardware profile ; 00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers (rev 08) 00:02.0 VGA compatible controller: Intel Corporation UHD Graphics 620 (rev 07) 00:08.0 System peripheral: Intel Corporation Skylake Gaussian Mixture Model 00:14.0 USB controller: Intel Corporation Sunrise Point-LP USB 3.0 xHCI Controller (rev 21) 00:14.2 Signal processing controller: Intel Corporation Sunrise Point-LP Thermal subsystem (rev 21) 00:15.0 Signal processing controller: Intel Corporation Sunrise Point-LP Serial IO I2C Controller #0 (rev 21) 00:15.1 Signal processing controller: Intel Corporation Sunrise Point-LP Serial IO I2C Controller #1 (rev 21) 00:16.0 Communication controller: Intel Corporation Sunrise Point-LP CSME HECI #1 (rev 21) 00:1c.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port (rev f1) 00:1c.7 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #8 (rev f1) 00:1d.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #9 (rev f1) 00:1f.0 ISA bridge: Intel Corporation Device 9d4e (rev 21) 00:1f.2 Memory controller: Intel Corporation Sunrise Point-LP PMC (rev 21) 00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21) 00:1f.4 SMBus: Intel Corporation Sunrise Point-LP SMBus (rev 21) 01:00.0 3D controller: NVIDIA Corporation Device 1d12 (rev a1) 02:00.0 Network controller: Intel Corporation Wireless 8265 / 8275 (rev 78) 03:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd Device a808 as xiaomi notebook pro late 2018 when i tried to use ubuntu 18.10(cosmic cuttlefish) with kernel 4.18 the system freeze and cause high processor activity (100%), high temperature, loud processor activity and the system crashes in one word all the system is static and i have to sutdown the system manually because there is no process respond to anything i can do... i tried every variant of this os and the bug repeat instantly after installation. i have to downgrade to ubuntu 18.04 to solve the probleme. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1800278/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1689365] Re: ibmvscsis: Do not send aborted task response
** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1689365 Title: ibmvscsis: Do not send aborted task response Status in The Ubuntu-power-systems project: Fix Released Status in linux package in Ubuntu: Incomplete Status in linux source package in Zesty: Fix Released Bug description: [Impact] ibmvscsis: Do not send aborted task response The driver is sending a response to the actual scsi op that was aborted by an abort task TM, while LIO is sending a response to the abort task TM. ibmvscsis_tgt does not send the response to the client until release_cmd time. The reason for this was because if we did it at queue_status time, then the client would be free to reuse the tag for that command, but we're still using the tag until the command is released at release_cmd time, so we chose to delay sending the response until then. That then caused this issue, because release_cmd is always called, even if queue_status is not. SCSI spec says that the initiator that sends the abort task TM NEVER gets a response to the aborted op and with the current code it will send a response. Thus this fix will remove that response if the CMD_T_ABORTED && !CMD_T_TAS. Another case with a small timing window is the case where if LIO sends a TMR_DOES_NOT_EXIST, and the release_cmd callback is called for the TMR Abort cmd before the release_cmd for the (attemped) aborted cmd, then we need to ensure that we send the response for the (attempted) abort cmd to the client before we send the response for the TMR Abort cmd. [Test Case] As per comment #11, this requires sending manual abort signals to trigger the bug. [Fix] ibmvscsis: Fix the incorrect req_lim_delta ibmvscsis: Clear left-over abort_cmd pointers ibmvscsis: Do not send aborted task response target: Fix unknown fabric callback queue-full errors [Regression Potential] Patches are confined to ibmvscsi driver and target driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1689365/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1776389] Re: [Ubuntu 1804][boston][ixgbe] EEH causes kernel BUG at /build/linux-jWa1Fv/linux-4.15.0/drivers/pci/msi.c:352 (i2S)
** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1776389 Title: [Ubuntu 1804][boston][ixgbe] EEH causes kernel BUG at /build/linux- jWa1Fv/linux-4.15.0/drivers/pci/msi.c:352 (i2S) Status in The Ubuntu-power-systems project: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Bug description: == Comment: #0 - ABDUL HALEEM <> - 2018-02-16 08:26:15 == Problem: Injecting error multiple times causes kernel crash. echo 0x0:1:4:0x60800:0xfff8 > /sys/kernel/debug/powerpc/PCI/err_injct EEH: PHB#0 failure detected, location: N/A EEH: PHB#0-PE#0 has failed 6 times in the last hour and has been permanently disabled. EEH: Unable to recover from failure from PHB#0-PE#0. Please try reseating or replacing it ixgbe :01:00.1: Adapter removed kernel BUG at /build/linux-jWa1Fv/linux-4.15.0/drivers/pci/msi.c:352! Oops: Exception in kernel mode, sig: 5 [#1] LE SMP NR_CPUS=2048 NUMA PowerNV Modules linked in: rpcsec_gss_krb5 nfsv4 nfs fscache joydev input_leds mac_hid idt_89hpesx ofpart ipmi_powernv cmdlinepart ipmi_devintf ipmi_msghandler at24 powernv_flash mtd opal_prd ibmpowernv uio_pdrv_genirq vmx_crypto uio sch_fq_codel nfsd auth_rpcgss nfs_acl lockd grace sunrpc ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear ses enclosure scsi_transport_sas qla2xxx ast hid_generic ttm drm_kms_helper ixgbe syscopyarea usbhid igb sysfillrect sysimgblt nvme_fc fb_sys_fops hid nvme_fabrics crct10dif_vpmsum crc32c_vpmsum drm i40e scsi_transport_fc aacraid i2c_algo_bit mdio CPU: 28 PID: 972 Comm: eehd Not tainted 4.15.0-10-generic #11-Ubuntu NIP: c077f080 LR: c077f070 CTR: c00aac30 REGS: c00ff1deb5a0 TRAP: 0700 Not tainted (4.15.0-10-generic) MSR: 90029033 CR: 24002822 XER: 2004 CFAR: c018bddc SOFTE: 1 GPR00: c077f070 c00ff1deb820 c16ea600 c00fbb5fac00 GPR04: 02c5 GPR08: c00fbb5fac00 0001 c00fec617a00 c00fdfd86488 GPR12: 0040 c7a33400 c0138be8 c00ff90ec1c0 GPR16: GPR20: c0f48d10 GPR24: c0f48ce8 c000200e4fcf4000 c00fc6900b18 c000200e4fcf4000 GPR28: c000200e4fcf4288 c00810624480 c00fbb633ea0 NIP [c077f080] free_msi_irqs+0xa0/0x260 LR [c077f070] free_msi_irqs+0x90/0x260 Call Trace: [c00ff1deb820] [c077f070] free_msi_irqs+0x90/0x260 (unreliable) [c00ff1deb880] [c077fa68] pci_disable_msix+0x128/0x170 [c00ff1deb8c0] [c0081060b5c8] ixgbe_reset_interrupt_capability+0x90/0xd0 [ixgbe] [c00ff1deb8f0] [c008105d52f4] ixgbe_remove+0xec/0x240 [ixgbe] [c00ff1deb990] [c07670ec] pci_device_remove+0x6c/0x110 [c00ff1deb9d0] [c085d194] device_release_driver_internal+0x224/0x310 [c00ff1deba20] [c075b398] pci_stop_bus_device+0x98/0xe0 [c00ff1deba60] [c075b588] pci_stop_and_remove_bus_device+0x28/0x40 [c00ff1deba90] [c005e1d0] pci_hp_remove_devices+0x90/0x130 [c00ff1debb20] [c005e184] pci_hp_remove_devices+0x44/0x130 [c00ff1debbb0] [c003ec04] eeh_handle_normal_event+0x134/0x580 [c00ff1debc60] [c003f160] eeh_handle_event+0x30/0x338 [c00ff1debd10] [c003f830] eeh_event_handler+0x140/0x200 [c00ff1debdc0] [c0138d88] kthread+0x1a8/0x1b0 [c00ff1debe30] [c000b528] ret_from_kernel_thread+0x5c/0xb4 Instruction dump: 419effe0 3bc0 480c 6042 807f0010 7c7e1a14 78630020 4ba0cd3d 6000 e9430158 312a 7d295110 <0b09> 813f0014 395e0001 7d5e07b4 ---[ end trace 23c446a470e60864 ]--- ixgbe :01:00.0: Adapter removed Sending IPI to other CPUs OPAL: Switch to big-endian OS OPAL: Switch to little-endian OS PHB#[0:0]: eeh_freeze_clear on fenced PHB ---uname output--- Linux ltciofvtr-bostonlc1 4.15.0-10-generic #11-Ubuntu SMP Tue Feb 13 18:21:52 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux Machine Type = Boston-LC :00:00.0 PCI bridge [0604]: IBM Device [1014:04c1] :01:00.0 Ethernet controller [0200]: Intel Corporation 82599ES 10-Gigabit SFI/SFP+ Network Connection [8086:10fb] (rev 01) :01:00.1 Ethernet controller [0200]: Intel Corporation 82599ES 10-Gigabit SFI/SFP+ Network Connection [8086:10fb] (rev 01) # ethtool
[Kernel-packages] [Bug 1776005] Re: kernel instability with BTRFS filesystem as rootfs
** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1776005 Title: kernel instability with BTRFS filesystem as rootfs Status in linux package in Ubuntu: Incomplete Status in linux source package in Xenial: Incomplete Bug description: Hello, As explained yesterday on #ubuntu-kernel, several laptop won't boot (kernel panic) with the latest kernel 4.4.0-127-generic (x86_64) and upper (proposed 4.4.0-128-generic), on Xenial 16.04 LTS I have made many tests to verify that the bootloader (GRUB) is correctly configured (I have also reinstall it, but same result). I have also verified the BTRFS system is clean and not corrupted (with a livecd). The behavior is unpredictable, because often the kernel fall in "panic" during boot, but not all the time, if i do several consecutive reboot to test stability of the boot "process". I have no search behavior with previous kernels (like 4.4.0-124-generic). I suspect (even if I'm quiet disturbed by this behavior, maybe I wrong) that something I changed on last kernel: - on BTRFS subsystem, I have "aggregate" BTRFS partitions as rootfs (for a long time) - something related with the last mitigation about the recent security processor breach But my skills stop here, and I'm not able to find the origin of this behavior despite my efforts. I can continue my investigation if I have some additional pointers. Thanks for your time, Sylvain To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776005/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799049] Re: [bionic]mlx5: reading SW stats through ifstat cause kernel crash
** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1799049 Title: [bionic]mlx5: reading SW stats through ifstat cause kernel crash Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Bug description: Description of problem: Attempting to read SW stats (ifstat -x cpu_hit) on a system with probed VFs will crash the system. How reproducible: Always Steps to Reproduce: 1. Create a VF echo 1 > /sys/bus/pci/devices/\:82\:00.0/sriov_numvfs 2. read SW stats: ifstat -x cpu_hit Actual results: System will crash Expected results: No system crash Additional info: The reason for the crash is insufficient check on the helper that determines if a netdev is vf rep. will crash: $ ifstat -x cpu_hit will not crash: $ ifstat -x cpu_hit $VF_REP $ ifstat -x cpu_hit $UPLINK_REP We already have a fix for this issue, and it is accepted upstream. https://patchwork.ozlabs.org/patch/935193/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1799049/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1823862] Re: disco: unable to use iptables/enable ufw under -virtual kernel
** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1823862 Title: disco: unable to use iptables/enable ufw under -virtual kernel Status in linux package in Ubuntu: Fix Released Status in ufw package in Ubuntu: Invalid Bug description: SRU Justification Impact: iptables does not work in disco with linux-virtual. Fix: Add bpfilter to the generic inclusion list. Regression Potential: There are no code changes and thus minimal potential for regressions. Test Case: Verify that bpffilter.ko is shipped in linux-modues instead of linux-module-extra and that iptables commands work in disco with the linux-virtual kernel installed. --- Fresh install of disco: $ sudo ufw enable Command may disrupt existing ssh connections. Proceed with operation (y|n)? y ERROR: problem running ufw-init iptables-restore v1.6.1: Can't set policy `DROP' on `INPUT' line 3: Bad built-in chain name iptables-restore: line 22 failed iptables-restore: line 2 failed iptables-restore v1.6.1: Couldn't load target `ufw-logging-deny':No such file or directory Error occurred at line: 30 Try `iptables-restore -h' or 'iptables-restore --help' for more information. iptables-restore v1.6.1: Couldn't load target `ufw-skip-to-policy-input':No such file or directory Error occurred at line: 19 Try `iptables-restore -h' or 'iptables-restore --help' for more information. iptables-restore v1.6.1: Couldn't load target `ufw-user-input':No such file or directory Error occurred at line: 2 Try `iptables-restore -h' or 'iptables-restore --help' for more information. Problem running '/etc/ufw/before.rules' Problem running '/etc/ufw/after.rules' ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: ufw 0.36-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu26 Architecture: amd64 Date: Tue Apr 9 08:49:59 2019 Ec2AMI: ami-04cf Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: m1.blue Ec2Kernel: unavailable Ec2Ramdisk: unavailable PackageArchitecture: all ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: ufw UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.default.ufw: 2019-04-09T08:48:31.371301 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823862/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1775717] Re: CPU/GPU Fans suddenly go 100% RPM on Asus ROG G752VT
** Tags added: cscc
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to thermald in Ubuntu.
https://bugs.launchpad.net/bugs/1775717
Title:
CPU/GPU Fans suddenly go 100% RPM on Asus ROG G752VT
Status in linux package in Ubuntu:
Incomplete
Status in thermald package in Ubuntu:
Confirmed
Bug description:
After upgrading from Ubuntu 16.04 to 18.04, I've noticed that CPU and
GPU fans suddenly go full throttle. It doesn't seem to depend on
temperature, could happen when 32 °C reported, sometimes the laptop
can work for day or two without this issue, but eventually it happens.
The only way to stop fans is to power off the laptop, power on (fans
go 100% at this point again), power off during BIOS splash screen and
power on again. Seems to happen more often after waking up from a
sleep.
Things tried:
Upgrading BIOS to latest available on ASUS site to the date of
writing. No change.
asus-fan kernel module (https://github.com/daringer/asus-fan). Detects
both fans and shows correct speed in /sys/class/hwmon/*/fan{1,2}*, but
does not seem to control it and does not prevent going full throttle.
4.17.0 kernel from Ubuntu mainline builds. Doesn't seem to affect the
issue.
Userspace fan control software (https://github.com/hirschmann/nbfc).
Can control speed of both fans to the point where they go full
throttle, after that has no effect on them.
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: whale 3068 F pulseaudio
/dev/snd/controlC0: whale 3068 F pulseaudio
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 18.04
HibernationDevice: RESUME=UUID=ada9b595-bbf2-40a3-8575-5908492bb969
InstallationDate: Installed on 2014-10-20 (1333 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64+mac
(20140722.2)
MachineType: ASUSTeK COMPUTER INC. G752VT
NonfreeKernelModules: nvidia_modeset nvidia wl
Package: linux (not installed)
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic
root=UUID=f6509d56-6183-464c-90bb-9c3be2c8abdf ro quiet splash
acpi_backlight=vendor vt.handoff=1
ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
RelatedPackageVersions:
linux-restricted-modules-4.15.0-23-generic N/A
linux-backports-modules-4.15.0-23-generic N/A
linux-firmware 1.173.1
Tags: bionic
Uname: Linux 4.15.0-23-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm audio cdrom dip docker lpadmin plugdev sambashare sudo tty
video
_MarkForUpload: True
dmi.bios.date: 06/29/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: G752VT.304
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: G752VT
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: ATN12345678901234567
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrG752VT.304:bd06/29/2017:svnASUSTeKCOMPUTERINC.:pnG752VT:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG752VT:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: G
dmi.product.name: G752VT
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775717/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1776578] Re: Ubuntu installation stuck at "Installing the 'grub2' package..." every time. Kernel crash every time.
** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1776578 Title: Ubuntu installation stuck at "Installing the 'grub2' package..." every time. Kernel crash every time. Status in grub2 package in Ubuntu: Invalid Status in linux package in Ubuntu: Invalid Bug description: Ubuntu 18.04 and 18.10 installation never completes on one particular machine (Apollo Lake N4200). It always ends up stuck at "Installing the 'grub2' package..." The kernel log shows a crash each time. The same installation media works perfectly on other machines. The same machine installs Windows 10 perfectly too. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1776578/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1826691] Re: fwupd hangs after 19.04 upgrade from 18.10
** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1826691 Title: fwupd hangs after 19.04 upgrade from 18.10 Status in Linux: Unknown Status in fwupd package in Ubuntu: Triaged Status in linux package in Ubuntu: Triaged Status in fwupd source package in Disco: Triaged Status in linux source package in Disco: Triaged Status in fwupd source package in Eoan: Triaged Status in linux source package in Eoan: Triaged Bug description: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu $ lsb_release -rd Description:Ubuntu 19.04 Release:19.04 Being a firmware updater, the machine is probably relevant - Dell 7730. 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center $ apt policy fwupd fwupd: Installed: (none) Candidate: 1.2.5-1ubuntu1 Version table: 1.2.5-1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages 100 /var/lib/dpkg/status 3) What you expected to happen I expected few/no issues after 19.04 upgrade. The fwupd process worked perfectly in 18.10. It's upgraded the firmware on my laptop twice since I installed 18.10. 4) What happened instead After upgrading from 18.10 to 19.04 I had an issues that when I tried to suspend my laptop using the same button press as previous, the laptop would be hot and screen flickering when I returned to reopen it. I thought there were power management issues in the upgrade, but I've traced it to fwupd not letting the PM suspend process complete (see dmesg below). I tried shutting down the fwupd daemon with systemctl but the command hangs forever. All of the fwupdmgr commands timeout. Thinking something might have broken in the upgrade, I tried uninstalling (purge) the fwupd package and reinstalling. Starting the process with systemctl hangs forever like stopping it. Trying to kill -9 the process does not work - in uninterruptible sleep (D). This crash is probably related. It happened a couple of ours before I tried to put it to sleep the last time before uninstalling fwupd. Apr 23 19:29:14 texas kernel: [ 133.673290] [drm] REG_WAIT timeout 10us * 160 tries - submit_channel_request line:246 Apr 23 19:29:14 texas kernel: [ 133.673348] WARNING: CPU: 6 PID: 2467 at drivers/gpu/drm/amd/amdgpu/../display/dc/dc_helper.c:249 generic_reg_wait.cold.3+0x25/0x2c [amdgpu] Apr 23 19:29:14 texas kernel: [ 133.673349] Modules linked in: thunderbolt rfcomm xt_owner ip6table_filter ip6_tables ipt_MASQUERADE iptable_nat nf_nat_ipv4 nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c bridge xt_CHECKSUM xt_tcpudp stp llc iptable_filter iptable_mangle bpfilter ccm snd_hda_codec_realtek snd_hda_codec_generic pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) cmac vboxdrv(OE) bnep binfmt_misc dell_rbtn nls_iso8859_1 joydev arc4 snd_soc_skl snd_soc_hdac_hda snd_hda_ext_core snd_soc_skl_ipc snd_soc_sst_ipc snd_soc_sst_dsp snd_soc_acpi_intel_match snd_soc_acpi snd_soc_core snd_compress ac97_bus intel_rapl snd_pcm_dmaengine x86_pkg_temp_thermal intel_powerclamp coretemp snd_hda_codec_hdmi kvm_intel snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep crct10dif_pclmul i915 snd_pcm crc32_pclmul iwlmvm uvcvideo amdgpu snd_seq_midi ghash_clmulni_intel snd_seq_midi_event mac80211 videobuf2_vmalloc kvmgt videobuf2_memops vfio_mdev videobuf2_v4l2 snd_rawmidi dell_laptop mdev videobuf2_common Apr 23 19:29:14 texas kernel: [ 133.673362] ledtrig_audio vfio_iommu_type1 videodev dell_smm_hwmon vfio snd_seq dell_wmi media kvm chash btusb snd_seq_device amd_iommu_v2 btrtl snd_timer btbcm dell_smbios gpu_sched irqbypass btintel dcdbas ttm aesni_intel iwlwifi bluetooth drm_kms_helper aes_x86_64 crypto_simd cryptd glue_helper rtsx_pci_ms input_leds snd drm ecdh_generic intel_cstate mei_me ucsi_acpi cfg80211 serio_raw dell_wmi_descriptor intel_wmi_thunderbolt wmi_bmof memstick i2c_algo_bit mei fb_sys_fops intel_rapl_perf idma64 syscopyarea hid_multitouch processor_thermal_device soundcore sysfillrect virt_dma typec_ucsi sysimgblt intel_soc_dts_iosf intel_pch_thermal typec int3403_thermal int340x_thermal_zone dell_smo8800 acpi_pad intel_hid int3400_thermal mac_hid acpi_thermal_rel sparse_keymap sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables autofs4 hid_generic rtsx_pci_sdmmc nvme e1000e i2c_i801 intel_lpss_pci rtsx_pci nvme_core intel_lpss i2c_hid wmi hid video pinctrl_cannonlake pinctrl_intel Apr 23 19:29:14 texas kernel: [ 133.673381] CPU: 6 PID: 2467 Comm: fwupd Tainted: G OE 5.0.0-13-generic #14-Ubuntu Apr 23 19:29:14 texas kernel: [ 133.673382] Hardware name: Dell Inc. Precision 7730/05W5TJ, BIOS 1.7.0 02/19/2019 Apr 23 19:29:14 texas kernel: [ 133.673417]
[Kernel-packages] [Bug 1821663] Re: [regression][snd_hda_codec_realtek] repeating crackling noise after 19.04 upgrade
** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1821663 Title: [regression][snd_hda_codec_realtek] repeating crackling noise after 19.04 upgrade Status in linux package in Ubuntu: Fix Released Status in linux-oem package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-oem source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux source package in Disco: Fix Released Bug description: [Impact] After CONFIG_SND_HDA_POWER_SAVE_DEFAULT is changed to 1, the codec runtime PM is enabled, on some codecs or for some hw design, there is noise with the codec runtime PM enabled. [Fix] put the machine in the power_save_black_list, this will set the power_save=0 [Test Case] just boot up and do some audio operations, there is no noise anymore [Regression Risk] Low. this patch ony applies to the specific machines. I'm experiencing a repeating crackling noise after 19.04 upgrade that start just after the boot and before the login. I tried a bunch of fixes for pulseaudio I found googling, including this one https://wiki.archlinux.org/index.php/PulseAudio/Troubleshooting#Glitches.2C_skips_or_crackling and this one https://askubuntu.com/questions/864608/audio-crackle-through-headphones. Neither of which helped. The command "killall pulseaudio" usually stop the noise for 10 seconds, then the noise restart. The system was running smoothly on 18.10 Alessandro- ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: alessandro 3310 F pulseaudio /dev/snd/controlC0: alessandro 3310 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Mar 26 03:29:00 2019 InstallationDate: Installed on 2016-07-09 (989 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-03-25 (0 days ago) dmi.bios.date: 02/14/2006 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 6.00 PG dmi.board.name: GA-8TRC410M-NF dmi.board.vendor: NEC COMPUTERS INTERNATIONAL dmi.chassis.type: 3 dmi.chassis.vendor: NEC COMPUTERS INTERNATIONAL dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd02/14/2006:svnPackardBellNEC:pnIMEDIA5204:pvrPB34310106:rvnNECCOMPUTERSINTERNATIONAL:rnGA-8TRC410M-NF:rvr:cvnNECCOMPUTERSINTERNATIONAL:ct3:cvr: dmi.product.name: IMEDIA 5204 dmi.product.version: PB34310106 dmi.sys.vendor: Packard Bell NEC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821663/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822394] Re: [Dell BIOSes dated 27 Mar 2019] laptop keyboard & touchpad not working at gdm screen after boot
** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1822394 Title: [Dell BIOSes dated 27 Mar 2019] laptop keyboard & touchpad not working at gdm screen after boot Status in libinput package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: On a dell XPS 15 2-in-1 with the latest 1.4.0 bios, my touchpad and keyboard are unresponsive at the gdm login screen. Keyboard works to unlock encrypted harddrive before that though. If I plug in a USB keyboard or activate my bluetooth mouse, I can use those to log in, and then after logging in the laptop touchpad and keyboard work again. Logging out of the desktop results in the laptop touchpad and keyboard working on the gdm screen. Did not see this behavior before upgrading from 1.2.0 bios to 1.4.0 bios, but also had not rebooted in a while, so not sure if bios or package upgrades triggered this behavior. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gdm3 3.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Mar 29 17:51:00 2019 InstallationDate: Installed on 2018-09-26 (184 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gdm3 UpgradeStatus: Upgraded to disco on 2019-03-11 (18 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1822394/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811803] Re: Crash on "ip link add foo type ipip"
** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1811803 Title: Crash on "ip link add foo type ipip" Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux source package in Disco: Fix Released Bug description: On 4.18.0-13-generic #14-Ubuntu SMP Wed Dec 5 09:04:24 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux When I executed "sudo ip link add foo type ipip" kernel crashed, leaving the system working but mostly unusable (networking was flaky). dmesg showed: [156541.500970] ipip: IPv4 and MPLS over IPv4 tunneling driver [156541.502201] BUG: unable to handle kernel NULL pointer dereference at 0108 [156541.502207] PGD 0 P4D 0 [156541.502210] Oops: [#1] SMP PTI [156541.502213] CPU: 9 PID: 29001 Comm: ip Tainted: G OE 4.18.0-13-generic #14-Ubuntu [156541.502215] Hardware name: Dell Inc. XPS 15 9570/0HWTMH, BIOS 1.6.0 11/02/2018 [156541.502223] RIP: 0010:ipip_netlink_fan.isra.11+0x5/0x250 [ipip] [156541.502224] Code: d9 fe ff ff 48 8d 93 78 09 00 00 eb 93 48 89 de 4c 89 e7 e8 cd 78 fe ff eb c3 e8 c6 79 5d e8 66 0f 1f 44 00 00 0f 1f 44 00 00 <48> 8b 87 08 01 00 00 48 85 c0 0f 84 1a 02 00 00 8b 12 85 d2 0f 85 [156541.502245] RSP: 0018:bac005a2b588 EFLAGS: 00010246 [156541.502246] RAX: RBX: RCX: [156541.502248] RDX: bac005a2b5d0 RSI: 9c1122439900 RDI: [156541.502249] RBP: bac005a2b600 R08: R09: bac005a2b594 [156541.502250] R10: c0cb9120 R11: R12: 9c1122439000 [156541.502251] R13: 9c1122439900 R14: bac005a2b930 R15: aa805780 [156541.502253] FS: 7fe219348680() GS:9c136be4() knlGS: [156541.502254] CS: 0010 DS: ES: CR0: 80050033 [156541.502255] CR2: 0108 CR3: 00010f724001 CR4: 003606e0 [156541.502257] DR0: DR1: DR2: [156541.502258] DR3: DR6: fffe0ff0 DR7: 0400 [156541.502259] Call Trace: [156541.502265] ? ipip_newlink+0x8c/0xc6 [ipip] [156541.502273] rtnl_newlink+0x67b/0x8c0 [156541.502279] ? nla_parse+0x35/0xe0 [156541.502280] ? rtnl_newlink+0x12e/0x8c0 [156541.502288] ? get_page_from_freelist+0xf7e/0x1320 [156541.502298] ? mem_cgroup_commit_charge+0x82/0x530 [156541.502302] ? lru_cache_add_active_or_unevictable+0x39/0xb0 [156541.502309] ? handle_pte_fault+0x52c/0xbe0 [156541.502313] rtnetlink_rcv_msg+0x213/0x300 [156541.502318] ? copy_user_generic_unrolled+0x89/0xc0 [156541.502320] ? rtnl_calcit.isra.33+0x100/0x100 [156541.502327] netlink_rcv_skb+0x52/0x130 [156541.502329] rtnetlink_rcv+0x15/0x20 [156541.502331] netlink_unicast+0x1a4/0x260 [156541.502333] netlink_sendmsg+0x20b/0x3d0 [156541.502340] sock_sendmsg+0x3e/0x50 [156541.502342] ___sys_sendmsg+0x295/0x2f0 [156541.502344] ? handle_pte_fault+0x539/0xbe0 [156541.502347] ? __handle_mm_fault+0x42c/0x5b0 [156541.502350] __sys_sendmsg+0x5c/0xa0 [156541.502353] __x64_sys_sendmsg+0x1f/0x30 [156541.502358] do_syscall_64+0x5a/0x110 [156541.502361] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [156541.502364] RIP: 0033:0x7fe219682234 [156541.502365] Code: 00 f7 d8 64 89 02 48 c7 c0 ff ff ff ff eb b5 0f 1f 80 00 00 00 00 48 8d 05 c9 d4 0c 00 8b 00 85 c0 75 13 b8 2e 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 54 c3 0f 1f 00 41 54 41 89 d4 55 48 89 f5 53 [156541.502390] RSP: 002b:7ffe5887fbe8 EFLAGS: 0246 ORIG_RAX: 002e [156541.502392] RAX: ffda RBX: 5c3dbcf0 RCX: 7fe219682234 [156541.502393] RDX: RSI: 7ffe5887fc50 RDI: 0003 [156541.502394] RBP: R08: 0001 R09: [156541.502396] R10: 0008 R11: 0246 R12: 0001 [156541.502397] R13: 5597e7c6c020 R14: 7ffe5887fd4c R15: [156541.502399] Modules linked in: ipip tunnel4 ip_tunnel veth sctp libcrc32c ses enclosure scsi_transport_sas uas usb_storage ath10k_pci thunderbolt rfcomm pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) ccm arc4 cmac bnep binfmt_misc nls_iso8859_1 snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic dell_wmi wmi_bmof mxm_wmi intel_wmi_thunderbolt snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep snd_pcm intel_rapl x86_pkg_temp_thermal dell_laptop intel_powerclamp ath10k_core dell_smbios coretemp dell_wmi_descriptor kvm_intel snd_seq_midi dcdbas snd_seq_midi_event ath snd_rawmidi mac80211 kvm snd_seq
[Kernel-packages] [Bug 1802283] Re: system freezes
** Tags added: ubuntu-certified ** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1802283 Title: system freezes Status in linux package in Ubuntu: Confirmed Bug description: My system freezes once every second day or so. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-10-generic 4.18.0-10.11 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jnns 2519 F pulseaudio /dev/snd/controlC0: jnns 2519 F pulseaudio CurrentDesktop: GNOME Date: Thu Nov 8 12:07:32 2018 HibernationDevice: RESUME=UUID=18edd09d-0a58-4464-accb-11ff57fc4327 InstallationDate: Installed on 2018-08-05 (95 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 20KGS5DU00 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/usr/bin/fish ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash mem_sleep_default=deep vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 SourcePackage: linux UpgradeStatus: Upgraded to cosmic on 2018-10-10 (29 days ago) dmi.bios.date: 09/17/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET56W (1.31 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KGS5DU00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN23ET56W(1.31):bd09/17/2018:svnLENOVO:pn20KGS5DU00:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KGS5DU00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 6th dmi.product.name: 20KGS5DU00 dmi.product.sku: LENOVO_MT_20KG_BU_Think_FM_ThinkPad X1 Carbon 6th dmi.product.version: ThinkPad X1 Carbon 6th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802283/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1824687] Re: 4.4.0-145-generic Kernel Panic ip6_expire_frag_queue
** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1824687 Title: 4.4.0-145-generic Kernel Panic ip6_expire_frag_queue Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Fix Released Status in linux source package in Cosmic: Incomplete Status in linux source package in Disco: Triaged Bug description: [SRU Justification] == Impact == Since 05c0b86b96 "ipv6: frags: rewrite ip6_expire_frag_queue()" the 16.04/4.4 kernel crashes whenever that functions gets called (on busy systems this can be every 3-4 hours). While this potentially affects Cosmic and later, too, the fix differs on later kernels (Bionic is not yet affected as it does not yet carry updates to the frags handling). == Fix == For Xenial and Cosmic, the proposed fix would be additional changes to ip6_expipre_frag_queue(), taken from follow-up changes to ip_expire(). For Disco, I would hold back because we have a backlog of stable patches there and depending on what got backported to 5.0.y there would be a simpler fix. For current development kernels, one just needs to ensure that the following upstream change is included: 47d3d7fdb10a "ip6: fix skb leak in ip6frag_expire_frag_queue()". == Testcase == Unfortunately this could not be re-created locally. But a test kernel which had the proposed fix applied was showing good testing (see comment #37 and #38). == Risk of Regression == The modified function is only called in rare cases and the positive testing in production would cover this. So I would consider it low. --- Description: Ubuntu 16.04.6 LTS Release: 16.04 After upgrading our server to this Kernel we experience frequent Kernel panics (Attachment). Every 3 hours. Our machine has a throuput of about 600 Mbits/s The Panics are around the area of ip6_expire_frag_queue. __pskb_pull_tail ip6_dst_lookup_tail _decode_session6 __xfrm_decode_session icmpv6_route_lookup icmp6_send It seems similar to Bug Report in Debian. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922488 According to the bug finder of above bug it also occurred after using a Kernel with the change of rewrite ip6_expire_frag_queue() Intermediate solution. We disabled IPv6 on this machine to avoid further Panics. Please let me know what information is missing. The ubuntu-bug linux was send. And I hope it is attached to this report. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-145-generic 4.4.0-145.171 ProcVersionSignature: Ubuntu 4.4.0-145.171-generic 4.4.176 Uname: Linux 4.4.0-145-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Sun Apr 14 11:40:11 2019 InstallationDate: Installed on 2018-03-18 (391 days ago) InstallationMedia: Ubuntu-Server 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) ProcEnviron: LANGUAGE=en_GB:en TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed UpgradeStatus: Upgraded to xenial on 2018-10-21 (174 days ago) --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Apr 12 21:04 seq crw-rw 1 root audio 116, 33 Apr 12 21:04 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=/dev/mapper/tor3--vg-swap_1 InstallationDate: Installed on 2018-03-18 (393 days ago) InstallationMedia: Ubuntu-Server 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) IwConfig: Error: [Errno 2] No such file or directory Lsusb: Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 0557:2221 ATEN International Co., Ltd Winbond Hermon Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Supermicro X9SRE/X9SRE-3F/X9SRi/X9SRi-3F Package: linux (not installed) PciMultimedia: ProcEnviron: LANGUAGE=en_GB:en TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-145-generic root=/dev/mapper/hostname--vg-root ro ProcVersionSignature: Ubuntu 4.4.0-145.171-generic 4.4.176 RelatedPackageVersions: linux-restricted-modules-4.4.0-145-generic N/A linux-backports-modules-4.4.0-145-generic N/A linux-firmware 1.157.21 RfKill: Error: [Errno 2] No such file or directory Tags:
[Kernel-packages] [Bug 1801924] Re: CVE-2018-18955: nested user namespaces with more than five extents incorrectly grant privileges over inode
** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1801924 Title: CVE-2018-18955: nested user namespaces with more than five extents incorrectly grant privileges over inode Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux source package in Disco: Fix Released Bug description: Jann Horn reported that nested user namespaces with more than five mappings allow gaining privilege over an inode. Here is my write up of how this happens: Currently, the forward map and reverse map are copied and sorted at the same time before necessary updates to the forward map have been performed. This has the consequence that the forward map receives the necessary updates while the reverse map does not leaving it with invalid data. Specifically, this means that the lower ids of the forward mapping will be correctly mapped to appropriate kernel ids, while the lower ids of the reverse mapping will not. This breaks inode_owner_or_capable() and privileged_wrt_inode_uidgid() which call helpers that need to access the reverse mapping. Thus, a process can incorrectly appear to be capable relative to an inode. Note that the sorting logic is only triggered when more than five extents are specified and when user namespaces are nested. Hence, only containers with complex mappings in nested user namespaces are affected. To fix this issue we need to ensures that the translation happens for both the forward and reverse mappings. First, the forward mappings are sorted and its lower ids translated into kernel ids. After this the forward mapping is copied and into the reverse mapping and the reverse mappings sorted. A proposed patch is appended here. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801924/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1818149] Re: backport relevant patches for support of the base_frequency attribute of intel_pstate
** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1818149 Title: backport relevant patches for support of the base_frequency attribute of intel_pstate Status in linux package in Ubuntu: Incomplete Bug description: Need to back port the following HWE commits from 4.20/5.0 kernel to 4.18, then 4.15 kernels for Cosmic and Bionic HWE 29523f095397637edca60c627bc3e5c25a02c40f 86d333a8cc7f66c2314ab1e147834a1cd95ec2de To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818149/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1817832] Re: qemu crashes with `kvm_init_vcpu failed: Invalid argument` during guest boot cores >256
** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1817832 Title: qemu crashes with `kvm_init_vcpu failed: Invalid argument` during guest boot cores >256 Status in The Ubuntu-power-systems project: Invalid Status in linux package in Ubuntu: Fix Released Status in qemu package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Status in linux source package in Cosmic: Invalid Bug description: == Comment: #0 - Satheesh Rajendran - 2019-02-14 23:48:15 == ---Problem Description--- qemu crashes with `kvm_init_vcpu failed: Invalid argument` during guest boot cores >256 but the error message is not clearly explains it. Contact Information = sathe...@in.ibm.com ---uname output--- 4.15.0-1016-ibm-gt Machine Type = power9 ppc64le ---Debugger--- A debugger is not configured ---Steps to Reproduce--- # /usr/bin/qemu-system-ppc64 -smp 257 -enable-kvm -monitor stdio qemu-system-ppc64: warning: Number of SMP cpus requested (257) exceeds the recommended cpus supported by KVM (128) qemu-system-ppc64: warning: Number of hotpluggable cpus requested (257) exceeds the recommended cpus supported by KVM (128) QEMU 2.11.1 monitor - type 'help' for more information (qemu) kvm_init_vcpu failed: Invalid argument Expected Result: 1. Guest should boot fine or 2. Proper error message stating cores >256 need to have thread>1 because smp=512 with threads=2 works fine like below # /usr/bin/qemu-system-ppc64 -smp 512,cores=256,threads=2 -enable-kvm -monitor stdio qemu-system-ppc64: warning: Number of SMP cpus requested (512) exceeds the recommended cpus supported by KVM (128) qemu-system-ppc64: warning: Number of hotpluggable cpus requested (512) exceeds the recommended cpus supported by KVM (128) QEMU 2.11.1 monitor - type 'help' for more information (qemu) VNC server running on ::1:5900 (qemu) info status VM status: running Userspace tool common name: ii qemu-system-ppc 1:2.11+dfsg-1ubuntu7.8-1ibm3 ppc64el QEMU full system emulation binaries (ppc) The userspace tool has the following bit modes: both Userspace rpm: ii qemu-system-ppc 1:2.11+dfsg-1ubuntu7.8-1ibm3 ppc64el QEMU full system emulation binaries (ppc) Userspace tool obtained from project website: na *Additional Instructions for sathe...@in.ibm.com: -Post a private note with access information to the machine that the bug is occuring on. -Attach ltrace and strace of userspace application. commit 1e175d2e07c71d9574f5b1c74523abca54e2654f Author: Sam Bobroff Date: Wed Jul 25 16:12:02 2018 +1000 commit b5c6f7607b908b1445f2556c8d2f3b1ec5fc5aa8 Author: Paul Mackerras Date: Thu Jul 26 15:38:41 2018 +1000 commit 1ebe6b81ebdba8faf377d1d7d84ad9368e7a0bae Author: Paul Mackerras Date: Thu Jul 26 14:53:54 2018 +1000 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1817832/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1825272] Re: headset-mic doesn't work on two Dell laptops.
** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1825272 Title: headset-mic doesn't work on two Dell laptops. Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-oem source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-oem source package in Cosmic: Fix Released Status in linux source package in Disco: Fix Released Status in linux-oem source package in Disco: Fix Released Bug description: [Impact] the headset-mic can't be detected after we plug the headset into the audio jack [Fix] Apply the fixup of ALC255_FIXUP_DELL1_MIC_NO_PRESENCE. [Test Case] Boot up the system plug the headset into the audio jack The audio device selecting dialogue will show up selecting headset-mic icon, then rerord sound from headset-mic, it works well. [Regression Risk] Low. this patch only applies to specific dell machines which have the same pin config as defined in the patch. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1825272/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1826410] Re: Please package libbpf (which is done out of the kernel src) in Debian [for 19.10]
*** This bug is a duplicate of bug 1836708 *** https://bugs.launchpad.net/bugs/1836708 ** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1826410 Title: Please package libbpf (which is done out of the kernel src) in Debian [for 19.10] Status in linux package in Ubuntu: Triaged Bug description: Hi, Debian packages libbpf and so far does so out of the kernel source [1]. There is some movement to separate that from the kernel source [2] but this isn't ready yet. So far it is just a sync of the subtree out of the kernel sources. Since we do not share our kernel packaging we will not get this for-free without doing anything. If there will be an ITP about it in Debian I'll let you know and we can abort this, but unless that really happens I wanted to ask if you could as well build the libbpf* packages for 19.10 and onward? Note: this is not the same bpf lib as [3] despite the similarity in names. Reasoning: BPF becomes more and more important in general and is used in the kernel for many things. In the case that brought it to my attention it will be a PMD of DPDK that will need it to control XDP [4]. And XDP in general is an interesting and rising feature for network acceleration - I'd think it would be helpful to have this package around in Ubuntu. [1]: https://packages.debian.org/sid/libbpf-dev [2]: https://github.com/libbpf/libbpf [3]: https://github.com/iovisor/bcc [4]: https://www.iovisor.org/technology/xdp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1826410/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819869] Re: linux-cloud-tools-common 3.13.0-166.216 in Trusty is missing contents of /usr/sbin
** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1819869 Title: linux-cloud-tools-common 3.13.0-166.216 in Trusty is missing contents of /usr/sbin Status in linux package in Ubuntu: In Progress Status in linux source package in Trusty: Fix Released Bug description: Version 3.13.0-165.215 of linux-cloud-tools-common has the following contents /. /usr /usr/sbin /usr/sbin/hv_vss_daemon /usr/sbin/hv_kvp_daemon /usr/sbin/hv_fcopy_daemon /usr/sbin/hv_get_dhcp_info /usr/sbin/hv_set_ifconfig /usr/sbin/hv_get_dns_info /usr/share /usr/share/man /usr/share/man/man8 /usr/share/man/man8/hv_kvp_daemon.8.gz /usr/share/doc /usr/share/doc/linux-cloud-tools-common /usr/share/doc/linux-cloud-tools-common/changelog.Debian.gz /usr/share/doc/linux-cloud-tools-common/copyright /etc /etc/init /etc/init/hv-vss-daemon.conf /etc/init/hv-fcopy-daemon.conf /etc/init/hv-kvp-daemon.conf whereas version 3.13.0-166.216 only contains /. /usr /usr/share /usr/share/doc /usr/share/doc/linux-cloud-tools-common /usr/share/doc/linux-cloud-tools-common/copyright /usr/share/doc/linux-cloud-tools-common/changelog.Debian.gz /etc /etc/init /etc/init/hv-vss-daemon.conf /etc/init/hv-kvp-daemon.conf /etc/init/hv-fcopy-daemon.conf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1819869/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1813934] Re: Vsock connect fails with ENODEV for large CID
** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1813934 Title: Vsock connect fails with ENODEV for large CID Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Bug description: - Problem Descripion: Kernel 4.19 introduced a bug in the Vsock protocol when using a large Context ID. E.g. CID 0xfff000 works correctly but CID 0xfff001 fails with ENODEV when trying to connect to the listener. The issue now also shows up in Ubuntu 18.04 with -> kernel 4.15.0-44-generic #47-Ubuntu on x86_64 and s390x. It is already fixed upstream kernel by: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=7fbe078c37aba3088359c9256c1a1d0c3e39ee81 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1813934/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822441] Re: [Intel® HD Graphics 3000] Blank screen after startup. Xorg reports "(EE) modeset(0): failed to set mode: Invalid argument" when using kernel 4.19.26 and later (but
** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1822441 Title: [Intel® HD Graphics 3000] Blank screen after startup. Xorg reports "(EE) modeset(0): failed to set mode: Invalid argument" when using kernel 4.19.26 and later (but 4.19.25 and earlier works) Status in Linux: Invalid Status in linux package in Ubuntu: Fix Released Bug description: Updated from kubuntu 18.10 to 19.04 beta without problems. After first reboot, first the kubuntu logo, then just a blank screen, no login screen. Switching to console and log in there possible. All seems fine, including wlan etc. systemd status sddm says sddm is running, any attempt to start KDE (including startkde) however fails with "could not connect to any x display". This happens with Kernel 5.0.0. Starting with 4.18.0-16-generic, the login screen comes up and all is fine. Anything I can contribute? Description:Ubuntu Disco Dingo (development branch) Release:19.04 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Sat Mar 30 21:51:04 2019 DistUpgraded: 2019-03-30 14:41:04,209 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: disco DistroVariant: ubuntu DkmsStatus: acpi-call, 1.1.0, 4.18.0-16-generic, x86_64: installed acpi-call, 1.1.0, 5.0.0-8-generic, x86_64: installed tp_smapi, 0.43, 5.0.0-8-generic, x86_64: installed virtualbox, 6.0.4, 5.0.0-8-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics Controller [17aa:21dd] InstallationDate: Installed on 2017-07-07 (631 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: LENOVO 78545HG ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-8-generic root=UUID=ce827244-1d04-4bdd-99bf-d70675baefef ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to disco on 2019-03-30 (0 days ago) dmi.bios.date: 04/12/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 8GET44WW (1.21 ) dmi.board.name: 78545HG dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8GET44WW(1.21):bd04/12/2013:svnLENOVO:pn78545HG:pvrThinkPadL420:rvnLENOVO:rn78545HG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad L420 dmi.product.name: 78545HG dmi.product.version: ThinkPad L420 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.1-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1822441/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822026] Re: [Nvidia Quadro P1000] Live USB freezes or cannot complete install when nouveau driver is loaded (crashing in gp100/gf100 code)
** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1822026 Title: [Nvidia Quadro P1000] Live USB freezes or cannot complete install when nouveau driver is loaded (crashing in gp100/gf100 code) Status in linux package in Ubuntu: Triaged Status in linux source package in Disco: Triaged Status in linux source package in Eoan: Triaged Bug description: When I boot the Disco 19.04 beta live USB, I can see a lot of errors related to nouveau in dmesg. Because of this, `lspci` freezes, so reporting an issue is impossible either with ubuntu-bug or sosreport (in both cases, the log gathering stops when trying to get the output from lspci). In addition, when nouveau is enabled: - the touchpad becomes unresponsive or behaves in a very weird way (slowing down, jumping), forcing me to use an external mouse or the little pointer in the middle of the keyboard. - the device cannot be powered off or restarted. It freezes and nothing can be done (I tried SysRq+REISUB to no avail) To avoid this issue, I need to launch the live USB with the following command line: $ cat /proc/cmdline BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed boot=casper quiet splash modprobe.blacklist=nouveau --- (that is, add `modprobe.blacklist=nouveau` to the command line in Grub) In the BIOS, I activated both GPUs (Intel and nvidia), which is the default settings. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: ubiquity 19.04.7 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CasperVersion: 1.402 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 28 03:23:52 2019 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed boot=casper quiet splash modprobe.blacklist=nouveau --- LiveMediaBuild: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822026/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1796647] Re: Shared folders cannot be mounted in ubuntu/cosmic64 due to missing vbox modules
** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1796647 Title: Shared folders cannot be mounted in ubuntu/cosmic64 due to missing vbox modules Status in cloud-images: Fix Released Status in linux package in Ubuntu: Fix Committed Status in linux source package in Cosmic: Fix Committed Bug description: SRU Justification Impact: Vagrant environments are no longer able to use virtualbox feartures like shared folders. This is due to Ubuntu Cosmic kernels currently shipping the upstream vboxguest module and not importing modules from the virtualbox-guest-dkms package. Fix: One solution would be to use the dkms modules for Vagrant, but this is not ideal. At this late stage the simplest solution is to go back to importing the out-of-tree modules. Regression Potential: Minimal. Will have no impact outside of virtualbox environments, and the drivers being imported come from the virtualbox-guest-dkms package in cosmic and are thus expected to work well. --- In bionic, the vboxsf module was included in linux- modules-...-generic: $ dpkg -c linux-modules-4.15.0-36-generic_4.15.0-36.39_amd64.deb | grep vboxsf.ko -rw-r--r-- root/root 63238 2018-09-24 10:08 ./lib/modules/4.15.0-36-generic/kernel/ubuntu/vbox/vboxsf/vboxsf.ko In cosmic, it isn't: $ dpkg -c ~/Downloads/linux- modules-4.18.0-9-generic_4.18.0-9.10_amd64.deb | grep vboxsf.ko This results in shared folders no longer being mountable in Ubuntu Vagrant boxes (and, as the other vbox modules are also missing, probably has other effects that haven't yet been reported). [Original Report] Just tried to test out the new cosmic64 vagrant box and get the following error; ``` Vagrant was unable to mount VirtualBox shared folders. This is usually because the filesystem "vboxsf" is not available. This filesystem is made available via the VirtualBox Guest Additions and kernel module. Please verify that these guest additions are properly installed in the guest. This is not a bug in Vagrant and is usually caused by a faulty Vagrant box. For context, the command attempted was: mount -t vboxsf -o uid=1000,gid=1000 vagrant /vagrant The error output from the command was: /sbin/mount.vboxsf: mounting failed with the error: No such device ``` I tried with ubuntu/bionic64 and it worked fine. I've got; $ vagrant version Installed Version: 2.1.5 Latest Version: 2.1.5 You're running an up-to-date version of Vagrant! $ VBoxManage --version 5.2.18r124319 $ To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1796647/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1824981] Re: cifs set_oplock buffer overflow in strcat
** Tags added: cscc
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1824981
Title:
cifs set_oplock buffer overflow in strcat
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Bionic:
Fix Committed
Status in linux source package in Cosmic:
Won't Fix
Status in linux source package in Disco:
Fix Committed
Status in linux source package in Eoan:
Fix Released
Bug description:
[Impact]
* We got reports of a kernel crash in cifs module with the following
signature:
detected buffer overflow in strcat
kernel BUG at <...>/lib/string.c:1052!
invalid opcode: [#1] SMP PTI
RIP: 0010:fortify_panic+0x13/0x1f
Call Trace:
smb21_set_oplock_level+0xde/0x190 [cifs]
smb3_set_oplock_level+0x22/0x90 [cifs]
smb2_set_fid+0x76/0xb0 [cifs]
cifs_new_fileinfo+0x268/0x3c0 [cifs]
? smb2_get_lease_key+0x40/0x40 [cifs]
? cifs_new_fileinfo+0x268/0x3c0 [cifs]
cifs_open+0x57c/0x8d0 [cifs]
do_dentry_open+0x1fe/0x320
[...]
* By analyzing the code of smb21_set_oplock_level(), we've noticed the
only way fortify function strcat() would get overflow was if the value
of cinode->oplock got corrupted in a another thread leading to a
buffer write bigger then buffer size. In this function, the 'message'
buffer writes are governed by cinode->oplock, so only a different
thread cleaning the oplock value would lead to 'message' overflow.
* By the same time we worked this analysis, a fix was proposed
upstream for this issue in the form of commit 6a54b2e002c9 ("cifs:
fix strcat buffer overflow and reduce raciness in
smb21_set_oplock_level()"), by the same reporter of this LP. The fix
is simple and directly addresses this problem, so we hereby request
its SRU into Bionic kernel - it's already present in linux stable
branches.
[Test case]
* Unfortunately we cannot reproduce the issue. The patch proposed here was
validated by us with xfstests (instructions followed from
https://wiki.samba.org/index.php/Xfstesting-cifs) and fio.
* Using xfstest with the exclusions proposed in the link above we
managed to get the same results as a non-patched kernel, i.e., the
same tests failed in both kernels, we didn't get worse results with
the patch. Fio also didn't show noticeable performance regression with
the patch.
[Regression potential]
* The patch was validated by the cifs filesystem maintainers and by
the aforementioned tests; also, the scope is restricted to cifs only
so the likelihood of regressions is considered low. The commit
introduces no functional changes and the only affected path was just
refactored in a way to prevent overflow and reduce race potential.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824981/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1809168] Re: FIPS and Ubuntu standard kernels prior to 4.11.0 won't boot; root device not found
** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1809168 Title: FIPS and Ubuntu standard kernels prior to 4.11.0 won't boot; root device not found Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: [IMPACT] Booting of the Xenial-based FIPS kernel packages failed with disk not found errors on amd64. This was also observed on standard Ubuntu kernels prior to 4.11.0. FIPS -- 1. linux-image-4.4.0-1002-fips <-- FAIL 2. linux-image-4.4.0-1006-fips <-- FAIL UBUNTU 1. Bionic kernels all WORK 2. Artful kernels: Ubuntu-4.11.0-1.6 <-- WORKS Ubuntu-4.10.0-26.30 <-- FAILS 3. Xenial kernels: Ubuntu-hwe-4.11.0-12.17_16.04.1 <--- WORKS Ubuntu-hwe-4.10.0-43.47_16.04.1 <--- FAILS Ubuntu-lts-* <--- ALL FAIL Ubuntu-4.4.0-* <--- ALL FAIL We have narrowed down the window to be: 4.11.0-1.6 (custom build) <--- WORKS 4.10.0-43.47~16.04.1 <-- FAILS Also works: https://kernel.ubuntu.com/~kernel-ppa/mainline/v4.11/linux-image-4.11.0-041100-generic_4.11.0-041100.201705041534_amd64.deb Symptoms - System cannot find the root disk and drops into an initramfs shell: mdadm script local-block "CREATE group disk not found" "Gave up waiting for root device. Common problems: - Boot args (cat /proc/cmdline) - Check rootdelay=... - Check root= ... - Missing modules (cat /proc/modules; ls/dev) ALERT! UUID=... does not exist. Dropping to a shell! ... (initramfs)_ There does not appear to be any workaround so far. The disks are encrypted SSDs. Attaching commit list between the last known failing Artful kernel and earliest known working kernel (adjacent tags) and other info. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1809168/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1814095] Re: bnxt_en_po: TX timed out triggering Netdev Watchdog Timer
** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1814095 Title: bnxt_en_po: TX timed out triggering Netdev Watchdog Timer Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Fix Released Bug description: [Impact] The bnxt_en_bpo driver experienced tx timeouts causing the system to experience network stalls and fail to send data and heartbeat packets. The following 25Gb Broadcom NIC error was seen on Xenial running the 4.4.0-141-generic kernel on an amd64 host seeing moderate-heavy network traffic (just once): * The bnxt_en_po driver froze on a "TX timed out" error and triggered the Netdev Watchdog timer under load. * From kernel log: "NETDEV WATCHDOG: eno2d1 (bnxt_en_bpo): transmit queue 0 timed out" See attached kern.log excerpt file for full excerpt of error log. * Release = Xenial Kernel = 4.4.0-141-generic #167 eno2d1 = Product Name: Broadcom Adv. Dual 25Gb Ethernet * This caused the driver to reset in order to recover: "bnxt_en_bpo :19:00.1 eno2d1: TX timeout detected, starting reset task!" driver: bnxt_en_bpo version: 1.8.1 source: ubuntu/bnxt/bnxt.c: bnxt_tx_timeout() * The loss of connectivity and softirq stall caused other failures on the system. * The bnxt_en_po driver is the imported Broadcom driver pulled in to support newer Broadcom HW (specific boards) while the bnx_en module continues to support the older HW. The current Linux upstream driver does not compile easily with the 4.4 kernel (too many changes). * This upstream and bnxt_en driver fix is a likely solution: "bnxt_en: Fix TX timeout during netpoll" commit: 73f21c653f930f438d53eed29b5e4c65c8a0f906 This fix has not been applied to the bnxt_en_po driver version, but review of the code indicates that it is susceptible to the bug, and the fix would be reasonable. [Test Case] * Unfortunately, this is not easy to reproduce. Also, it is only seen on 4.4 kernels with newer Broadcom NICs supported by the bnxt_en_bpo driver. [Regression Potential] * The patch is restricted to the bpo driver, with very constrained scope - just the newest Broadcom NICs being used by the Xenial 4.4 kernel (as opposed to the hwe 4.15 etc. kernels, which would have the in-tree fixed driver). * The patch is very small and backport is fairly minimal and simple. * The fix has been running on the in-tree driver in upstream mainline as well as the Ubuntu Linux in-tree driver, although the Broadcom driver has a lot of lower level code that is different, this piece is still the same. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814095/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1801573] Re: pc randomly freeze
** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1801573 Title: pc randomly freeze Status in linux package in Ubuntu: Confirmed Bug description: pc with ubuntu 18.04 randomly freeze and i'm forced to turn it off. This often happens while playing VLC ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-38-generic 4.15.0-38.41 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: plraska8379 F pulseaudio /dev/snd/controlC0: plraska8379 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Nov 4 08:23:54 2018 InstallationDate: Installed on 2018-10-03 (31 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: HP HP Laptop 15-db0xxx ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic root=UUID=c1c43279-03a7-4d7e-8b7e-9b999190af0a ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-38-generic N/A linux-backports-modules-4.15.0-38-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/26/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.03 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 84AE dmi.board.vendor: HP dmi.board.version: 86.19 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.03:bd04/26/2018:svnHP:pnHPLaptop15-db0xxx:pvrType1ProductConfigId:rvnHP:rn84AE:rvr86.19:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15-db0xxx dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801573/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1808609] Re: None of my external drives appear after Linux crash.
** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1808609 Title: None of my external drives appear after Linux crash. Status in linux package in Ubuntu: Invalid Bug description: First my system became incredibly slow (consistent with the memory leak in Caja). I xKill Caja and then tried to restart it. I then closed every app and tried to do a shutdown. I got a warning that Caja still had processes running preventing shutdown. I chose shut down anyway. I eventually got the progress screen showing that Linux was trying to shut down. After 1 1/2 hours of the progress screen, I manually turned off power. I was able to reboot but all of my external drives are missing. I tried turning off and then back on one drive with no result. When I plug a drive back in I do not feel the vibration caused by the drive spinning up. Nor do I feel the drive do the initial seek. This indicated that Linux is not even attempting to access the drives. Do I have to reinstall Ubuntu MATE 18.10 (again) in order to use external USB drives? The attached screen shots shows only partitions on my two internal hard drives. Gparted does not show the disks. Disks from the Control Center shows only internal devices. Without access to my external drives I am stalled. I can't even do backups. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-13-generic 4.18.0-13.14 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: robert 2606 F pulseaudio /dev/snd/controlC0: robert 2606 F pulseaudio CurrentDesktop: MATE Date: Fri Dec 14 22:38:44 2018 InstallationDate: Installed on 2018-11-30 (14 days ago) InstallationMedia: Ubuntu-MATE 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) MachineType: System manufacturer System Product Name ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic root=UUID=9bdf74d9-8608-440e-8020-66b698586d9d ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-13-generic N/A linux-backports-modules-4.18.0-13-generic N/A linux-firmware 1.175.1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1301 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: A88XM-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1301:bd04/01/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA88XM-A:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808609/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1798127] Re: CPU Soft Lockups when stress-ng stack stressor runs with M.2 NVMe as root FS
** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1798127 Title: CPU Soft Lockups when stress-ng stack stressor runs with M.2 NVMe as root FS Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Invalid Status in linux source package in Bionic: Triaged Status in linux source package in Cosmic: Triaged Bug description: This was reported by a hardware partner. The system set up is a server with 512GB RAM and an M.2 NVMe drive as the root filesystem/boot device. Per the customer, when running the certification Memory Stress test (utilizing several stress-ng stressors run in sequence) the system freezes with CPU Soft Lockup errors appearing on console whe the "stack" stressor is run. Tester has tried with 2.5” SATA (1TB), 2.5” NVMe (800GB), and M.2 NVMe (1.9TB). So far, this only seems to affect the 4.15 kernel. The tester has tried using the 2.5" SATA SSD as the RootFS/Boot device and the tests pass on all attempts. It is ONLY when using the M.2 NVMe as the root / boot device that the tests cause a lockup. The tester is re-trying now with the 2.5" NVMe device to see if this only occurs with the M.2 NVMe. The tester has tried this on the following while using the M.2 NVMe as the rootFS/Boot device: Test run #1 – 16.04.5 at kernel 4.15; Result: Failed stress-ng memory on stack stressor Test run #2 – 18.04.1 at kernel 4.15; Result: Failed stress-ng memory on stack stressor Test run #3 – 16.04.5 at kernel 4.4; Result: Passed stress-ng memory test The stress-ng command invoked at the time the soft lockups occur is this: 'stress-ng -k --aggressive --verify --timeout 300 --stack 0' This can be reproduced by running the memory_stress_ng test script from the cert suite: sudo /usr/lib/plainbox-provider-certification- server/bin/memory_stress_ng It may be more easily reproducible running the stack stressor alone, or the whole memory stress script without dealing with Checkbox. UPDATE: The tester also confirms that the 2.5" NVMe drives also fail with the 4.15 kernel and pass with the 4.4 kernel. The SSD works on all kernels. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798127/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819907] Re: 19.04 installer hangs on installation complete dialog
** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1819907 Title: 19.04 installer hangs on installation complete dialog Status in linux package in Ubuntu: Incomplete Bug description: Installed version 19.04 on a Lenovo P1 laptop and when the installation Complete dialog came up I hit the restart button and the system froze. I then have to hard power down. At this point it boots to a login prompt. I login but there is no desktop after ten minutes or more finally reinstalled. On reinstall again same freeze at install complete but this time after several minutes the desktop did finally show up. Only difference on the installs was first time I selected the update wifi and other drivers click box and second time I did not. BIOS N2EET38W CPU i7-8850H To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1819907/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1805802] Re: [UBUNTU] qeth: fix length check in SNMP processing
** Tags added: cscc
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1805802
Title:
[UBUNTU] qeth: fix length check in SNMP processing
Status in Ubuntu on IBM z Systems:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Bionic:
Fix Released
Status in linux source package in Cosmic:
Fix Released
Status in linux source package in Disco:
Fix Released
Bug description:
== SRU Justification ==
The response for a SNMP request can consist of multiple parts,
which the cmd callback stages into a kernel buffer until all
parts have been received. If the callback detects that the
staging buffer provides insufficient space, it bails out with
error.
This processing is buggy for the first part of the response -
while it initially checks for a length of 'data_len', it later
copies an additional amount of
'offsetof(struct qeth_snmp_cmd, data)' bytes.
== Fix ==
9a764c1e5968 ("s390/qeth: fix length check in SNMP processing")
== Regression Potential ==
Low. Changes limited to s390.
== Test Case ==
A test kernel was built with this patch and tested by the original bug
reporter.
The bug reporter states the test kernel resolved the bug.
== Original bug description ==
Description: qeth: fix length check in SNMP processing
Symptom: Undefined behaviour.
Problem: The response for a SNMP request can consist of multiple parts,
which the cmd callback stages into a kernel buffer until all
parts have been received. If the callback detects that the
staging buffer provides insufficient space, it bails out with
error.
This processing is buggy for the first part of the response -
while it initially checks for a length of 'data_len', it later
copies an additional amount of
'offsetof(struct qeth_snmp_cmd, data)' bytes.
Solution: Fix the calculation of 'data_len' for the first part of the
response.
Upstream-ID: 9a764c1e59684c0358e16ccaafd870629f2cfe67
Should be applied to all Ubuntu Releases in Service
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1805802/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822044] Re: Laptop freezes after installation is finished when pressing "Restart Now"
*** This bug is a duplicate of bug 1822026 *** https://bugs.launchpad.net/bugs/1822026 ** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1822044 Title: Laptop freezes after installation is finished when pressing "Restart Now" Status in linux package in Ubuntu: Incomplete Status in ubiquity package in Ubuntu: Incomplete Bug description: As stated in lp:1822026, the Dell Precision 7530 I'm using is using nouveau graphics drivers by default when starting a live session, and this driver is prone to errors. One of the most annoying for a new user is the following: 1. Boot into 19.04 live session 2. Launch "Install Ubuntu 19.04" and go through the installation steps 3. Once the install is done, the "Installation Complete" dialog is shown with two options: [Continue Testing][Restart Now] 4. Press [Restart Now] Expected behaviour: 4. The device restarts and boots into freshly installed Ubuntu 19.04. Actual behaviour: 4. The device freezes and even the keyboard combination SysRq+REISUB doesn't do anything. User has to force shutdown the device by pressing Power button for a few seconds, remember to remove the USB drive, then manually start the device. All the hardware-related information is available in the sosreport attachment in lp:1822026: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1822026/+attachment/5249977/+files /sosreport-ubuntu-20190328033617.tar.xz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822044/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1810392] Re: [Ubuntu 1810] Migrating Power9 guest back to source causes kernel Oops inside guest
** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1810392 Title: [Ubuntu 1810] Migrating Power9 guest back to source causes kernel Oops inside guest Status in The Ubuntu-power-systems project: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: ---Problem Description--- Migrating back Power9 to source cause Kernel Oops inside guest Contact Information = Balamuruhan S / balamuruh...@in.ibm.com ---uname output--- source and target host Kernel: 4.18.0-8-generic Guest Kernel: 4.18.0-8-generic Machine Type = Boston ---Debugger--- A debugger is not configured ---Steps to Reproduce--- Due to Bug 172310, Turn off the firewalld in source and target host machines. 1. Define a healthy guest and placed image in NFS share. 2. Mounted the image location in destination and start the guest to perform migration. 3. Perform migration from source to target, 08:07:54 INFO | Migrating VM avocado-vt-vm1-migration from qemu:///system to qemu+ssh://9.40.194.13/system 08:07:54 DEBUG| Running virsh command: migrate --live --domain avocado-vt-vm1-migration --desturi qemu+ssh://9.40.194.13/system --timeout 60 08:07:54 INFO | Running '/usr/bin/virsh -c 'qemu:///system' migrate --live --domain avocado-vt-vm1-migration --desturi qemu+ssh://9.40.194.13/system --timeout 60' 08:08:21 DEBUG| [stdout] 08:08:21 INFO | Command '/usr/bin/virsh -c 'qemu:///system' migrate --live --domain avocado-vt-vm1-migration --desturi qemu+ssh://9.40.194.13/system --timeout 60' finished with 0 after 26.9465551376s 08:08:21 DEBUG| status: 0 08:08:21 DEBUG| stdout: 08:08:21 DEBUG| stderr: 08:08:21 INFO | Migration exit status: 0 4. check VM uptime after successful migration, 08:07:44 INFO | Check VM uptime before migration: 57.66 5. Migration is successful from source to destination, now perform migration back to source 08:08:49 INFO | Migrating VM avocado-vt-vm1-migration from qemu+ssh://9.40.194.13/system to qemu:///system 08:08:49 DEBUG| Running virsh command: migrate --live --domain avocado-vt-vm1-migration --desturi qemu:///system --timeout 60 08:08:49 INFO | Running '/usr/bin/virsh -c 'qemu+ssh://9.40.194.13/system' migrate --live --domain avocado-vt-vm1-migration --desturi qemu:///system --timeout 60' 08:09:22 DEBUG| [stdout] 08:09:22 INFO | Command '/usr/bin/virsh -c 'qemu+ssh://9.40.194.13/system' migrate --live --domain avocado-vt-vm1-migration --desturi qemu:///system --timeout 60' finished with 0 after 32.8640539646s 08:09:22 DEBUG| status: 0 08:09:22 DEBUG| stdout: 08:09:22 DEBUG| stderr: 08:09:22 INFO | Migration exit status: 0 6. check uptime of VM after migration and it is observed that VM have gone for reboot 08:10:22 INFO | Check VM uptime after migrating back to source: 31.09 5. By checking the VM console Call Trace is observed as mentioned below The time stamp during the call trace observed inside guest matches with the timestamp during which migration is triggered. Stack trace output: no Attachment: 1. VM sosreport 2. source and target sosreport 3. VM console log with call trace 4. Guest xml 5. Test job log Oops output: 2018-10-26 08:08:26: root@ubuntu1810:~# 2018-10-26 08:09:11: [ 144.512549] Unable to handle kernel paging request for data at address 0x71ff9672fa0e0989 2018-10-26 08:09:11: [ 144.512655] Faulting instruction address: 0xc03af7cc 2018-10-26 08:09:11: [ 144.512741] Oops: Kernel access of bad area, sig: 11 [#1] 2018-10-26 08:09:11: [ 144.512789] LE SMP NR_CPUS=2048 NUMA pSeries 2018-10-26 08:09:11: [ 144.512859] Modules linked in: iscsi_target_mod target_core_mod xt_CHECKSUM iptable_mangle ipt_MASQUERADE iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp bridge stp llc ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter bpfilter kvm dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua vmx_crypto crct10dif_vpmsum sch_fq_codel nfsd ib_iser auth_rpcgss rdma_cm nfs_acl iw_cm lockd ib_cm grace ib_core sunrpc iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear virtio_net net_failover crc32c_vpmsum virtio_blk virtio_scsi failover 2018-10-26 08:09:11: [ 144.513801] CPU: 5 PID: 1072 Comm: systemd-network Not tainted 4.18.0-8-generic #9-Ubuntu 2018-10-26 08:09:11: [ 144.513872] NIP: c03af7cc LR: c03af7b8 CTR: c0c9ea80 2018-10-26 08:09:11: [ 144.513943] REGS: c000f19ab910 TRAP: 0380 Not tainted (4.18.0-8-generic) 2018-10-26 08:09:11: [ 144.514025] MSR: 80009033
[Kernel-packages] [Bug 1810328] Re: iommu - need to effectively disable iommu if "intel_iommu=off" is passed as a kernel parameter
** Tags added: cscc
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1810328
Title:
iommu - need to effectively disable iommu if "intel_iommu=off" is
passed as a kernel parameter
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Xenial:
Fix Released
Bug description:
[Impact]
* If the parameter "intel_iommu=off" is passed for the kernel in a
boot instance coming from a previously iommu-enabled kernel (like a
kexec/kdump scenario), currently Xenial kernel (4.4 version) is
missing a patch to effectively disable the iommu. As a result, the
previous DMA mappings remain and the new kernel will try to use them,
which is wrong since we don't have iommu initialized to translate the
addresses.
* The upstream patch proposed to SRU here, 161b28aae165 ("iommu/vt-d:
Make sure IOMMUs are off when intel_iommu=off") fixes the issue by
effectively disabling the iommu in case it was requested.
* One important use case is in a scenario of iommu bug that is leading to a
kernel crash; kdump naturally will have the iommu tables copied from previous
kernel in kdump boot time, so if iommu
tables are bogus, we could inherit the bug in the kdump kernel preventing a
successful dump.
Have the ability to disable iommu (given that the functionality is there) is
essential.
[Test Case]
* Boot a kernel with "intel_iommu=on", and then kexec a new kernel with
"intel_iommu=off"
parameter. A kdump test is also possible, by changing the kdump command-line
to disable
iommu (after booting a kernel with iommu enabled) - then, induce a crash and
the issue
will show.
* Attached to this Launchpad are 2 files with the kdump test case:
"iommu-missing" shows
the issue in a Trusty HWE kernel - without the fix patch, we can see messages
like
[36.489918] DMAR: DRHD: handling fault status reg 202
[36.734830] DMAR: DMAR:[DMA Read] Request device [03:00.0] fault addr 3179a000
[36.734830] DMAR:[fault reason 06] PTE Read access is not set
In our case, the rootfs couldn't be initialized since the SCSI adapter
wasn't initialized due to the DMAR failures (hpsa driver). Also,
Solarflare NIC (sfc driver) couldn't get initialized too.
The patch fixed those error messages and the rootfs was mounted (see file
"iommu-patched").
Notice the succeeding case couldn't kdump for other reasons, not strictly
related to the proposed patch here.
[Regression Potential]
* iommu operations are complex and subject to HW issues eventually. Having
iommu enabled
and then boot a kernel with this component disabled is inherently a "danger"
operation from
drivers (or any users of such mappings) point-of-view. That said, I don't see
a potential regression for this patch, in a way currently an user can't disable
iommu properly if it was
once enabled, and this simple patch fixes it
* Care should be taken of course to not confuse regressions with problems
induced by disabling the
iommu after it was enabled before (which would show that the patch works fine
indeed, by allowing iommu to get disabled) - some drivers/devices may require
iommu to be enabled in order to work, in such case disabling it would prevent
the device to work.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810328/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799794] Re: [Bionic][Cosmic] Fix to ipmi to support vendor specific messages greater than 255 bytes
** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1799794 Title: [Bionic][Cosmic] Fix to ipmi to support vendor specific messages greater than 255 bytes Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Bug description: [Impact] Unable to send ipmi raw command greater than 255bytes, eg hostnames. Multipart transmit messages with ipmi currently fails. [Fix] commit 10042504ed92c06077b8a20a4edd67ba784847d4 Author: Corey Minyard Date: Fri Jul 27 07:36:20 2018 -0500 ipmi:ssif: Add support for multi-part transmit messages > 2 parts [Test] -- Testcase -- ipmitool -v raw 0x32 0x6c 1 0 0x0 0xd 0x42 0x4d 0x43 0x41 0x52 0x36 \ 0x34 0x5a 0x41 0x4c 0x4f 0x4e 0x35 0x0 0x0 0x0 0x0 0x0 \ 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 \ 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 \ 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 \ 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 \ 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 \ 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 \ 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 \ 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0 0 -- before applying patch -- Running Get PICMG Properties my_addr 0x20, transit 0, target 0 Error response 0xc1 from Get PICMG Properities Running Get VSO Capabilities my_addr 0x20, transit 0, target 0 Invalid completion code received: Invalid command Discovered IPMB address 0x0 RAW REQ (channel=0x0 netfn=0x32 lun=0x0 cmd=0x6c data_len=132) RAW REQUEST (132 bytes) 01 00 00 0d 42 4d 43 41 52 36 34 5a 41 4c 4f 4e 35 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 Unable to send RAW command (channel=0x0 netfn=0x32 lun=0x0 cmd=0x6c rsp=0xff): Unspecified error -- After applying the patch -- Running Get PICMG Properties my_addr 0x20, transit 0, target 0 Error response 0xc1 from Get PICMG Properities Running Get VSO Capabilities my_addr 0x20, transit 0, target 0 Invalid completion code received: Invalid command Discovered IPMB address 0x0 RAW REQ (channel=0x0 netfn=0x32 lun=0x0 cmd=0x6c data_len=132) RAW REQUEST (132 bytes) 01 00 00 0d 42 4d 43 41 52 36 34 5a 41 4c 4f 4e 35 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 RAW RSP (0 bytes) [Regression Potential] The patch to ipmi_ssif module cleanly cherry-picks from linux-next, the patch touches no platform code. The kernel was tested on a Cavium Thunder X2 system and no regressions were found. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1799794/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1798897] Re: Linux: insufficient shootdown for paging-structure caches
** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1798897 Title: Linux: insufficient shootdown for paging-structure caches Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux source package in Disco: Fix Released Bug description: https://bugs.chromium.org/p/project-zero/issues/detail?id=1633 [Impact] Paging structure caches are not always flushed as part of a TLB shootdown operation on x86. [Test Case] Ideally, we'd be able to use the test case described in the Project Zero bug report. However, it depends on certain processor features as well as custom kernel changes to make the proof-of-concept more likely to be successful. Instead, I think we're limited to simple boot testing and then will need to rely on our regular SRU testing. [Regression Potential] Considerable since the changes are in mm/ but these three patches have been released in the upstream linux-stable trees for a while now. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798897/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1807393] Re: nvme - Polling on timeout
** Tags added: cscc
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1807393
Title:
nvme - Polling on timeout
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Xenial:
Fix Released
Bug description:
[Impact]
* NVMe controllers potentially could miss to send an interrupt, specially
due to bugs in virtual devices(which are common those days - qemu has its
own NVMe virtual device, so does AWS). This would be a difficult to
debug situation, because NVMe driver only reports the request timeout,
not the reason.
* The upstream patch proposed to SRU here here, 7776db1ccc12
("NVMe/pci: Poll CQ on timeout") was designed to provide more information
in these cases, by pro-actively polling the CQEs on request timeouts, to
check if the specific request was completed and some issue (probably a
missed interrupt) prevented the driver to notice, or if the request really
wasn't completed, which indicates more severe issues.
* Although quite useful for debugging, this patch could help to mitigate
issues in cloud environments like AWS, in case we may have jitter in
request completion and the i/o timeout was set to low values, or even
in case of atypical bugs in the virtual NVMe controller. With this patch,
if polling succeeds the NVMe driver will continue working instead of
trying a reset controller procedure, which may lead to fails in the
rootfs - refer to https://launchpad.net/bugs/1788035.
[Test Case]
* It's a bit tricky to artificially create a situation of missed interrupt;
one idea was to implement a small hack in the NVMe qemu virtual device
that given a trigger in guest kernel, will induce the virtual device to
skip an interrupt. The hack patch is present in comment #1 below.
* To trigger such hack from guest kernel, all is needed is to issue a
raw admin command from nvme-cli: "nvme admin-passthru -o 0xff /dev/nvme0"
After that, just perform some I/Os to see one of them aborting - one could
use dd for this goal, like "dd if=/dev/zero of=/dev/nvme0n1 count=5".
[Regression Potential]
* There are no clear risks in adding such polling mechanism to the NVMe
driver; one bad thing that was neverreported but could happen with this patch
is the device could be in a bad state IRQ-wise that a reset would fix, but
the patch could cause all requests to be completed via polling, which
prevents the adapter reset. This is however a very hypothetical situation,
which would also happen in the mainline kernel (since it has the patch).
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1807393/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799184] Re: [18.04 FEAT] zcrypt DD: introduce APQN tags to support deterministic driver binding
** Tags added: cscc
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1799184
Title:
[18.04 FEAT] zcrypt DD: introduce APQN tags to support deterministic
driver binding
Status in Ubuntu on IBM z Systems:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Bionic:
Fix Released
Bug description:
== SRU Justification ==
APQN tags in the zcrypt device driver are required to support
deterministic driver binding
With the introduction of KVM hw crypto virtualization (on s390x) the driver
bound to an AP queue device is no longer unique determined.
Therefore a deterministic hot plugging semantics of AP queues that may be
bound to multiple drivers is needed.
With the three listed commits here it will be possible to configure an AP
queue (APQN) as being bound to a particular driver even if the associate hw
gets intermittently lost and reconnected.
== Fixes ==
ac2b96f351d7d222 ("s390/zcrypt: code beautify")
7e0bdbe5c21cb831 ("s390/zcrypt: AP bus support for alternate driver(s)")
3d8f60d38e249f98 ("s390/zcrypt: hex string mask improvements for apmask and
aqmask")
== Patches ==
Git-commit: ac2b96f351d7d222
https://github.com/torvalds/linux/commit/ac2b96f351d7d222c46e524feca03005f3fa8d75
Author: Harald Freudenberger
Date: Fri Aug 17 12:36:01 2018 +0200
s390/zcrypt: code beautify
Code beautify by following most of the checkpatch suggestions:
- SPDX license identifier line complains by checkpatch
- missing space or newline complains by checkpatch
- octal numbers for permssions complains by checkpatch
- renaming of static sysfs functions complains by checkpatch
- fix of block comment complains by checkpatch
- fix printf like calls where function name instead of %s __func__
was used
- __packed instead of __attribute__((packed))
- init to zero for static variables removed
- use of DEVICE_ATTR_RO and DEVICE_ATTR_RW macros
No functional code changes or API changes!
Signed-off-by: Harald Freudenberger
Signed-off-by: Martin Schwidefsky
===
Git-commit 7e0bdbe5c21cb831
https://github.com/torvalds/linux/commit/7e0bdbe5c21cb8316a694e46ad5aad339f6894a6
Author: Harald Freudenberger
Date: Fri Jul 20 08:36:53 2018 +0200
s390/zcrypt: AP bus support for alternate driver(s)
The current AP bus, AP devices and AP device drivers implementation
uses a clearly defined mapping for binding AP devices to AP device
drivers. So for example a CEX6C queue will always be bound to the
cex4queue device driver.
The Linux Device Driver model has no sensitivity for more than one
device driver eligible for one device type. If there exist more than
one drivers matching to the device type, simple all drivers are tried
consecutively. There is no way to determine and influence the probing
order of the drivers.
With KVM there is a need to provide additional device drivers matching
to the very same type of AP devices. With a simple implementation the
KVM drivers run in competition to the regular drivers. Whichever
'wins' a device depends on build order and implementation details
within the common Linux Device Driver Model and is not
deterministic. However, a userspace process could figure out which
device should be bound to which driver and sort out the correct
binding by manipulating attributes in the sysfs.
If for security reasons a AP device must not get bound to the 'wrong'
device driver the sorting out has to be done within the Linux kernel
by the AP bus code. This patch modifies the behavior of the AP bus
for probing drivers for devices in a way that two sets of drivers are
usable. Two new bitmasks 'apmask' and 'aqmask' are used to mark a
subset of the APQN range for 'usable by the ap bus and the default
drivers' or 'not usable by the default drivers and thus available for
alternate drivers like vfio-xxx'. So an APQN which is addressed by
this masking only the default drivers will be probed. In contrary an
APQN which is not addressed by the masks will never be probed and
bound to default drivers but onny to alternate drivers.
Eventually the two masks give a way to divide the range of APQNs into
two pools: one pool of APQNs used by the AP bus and the default
drivers and thus via zcrypt drivers available to the userspace of the
system. And another pool where no zcrypt drivers are bound to and
which can be used by alternate drivers (like vfio-xxx) for their
needs. This division is hot-plug save and makes sure a APQN assigned
to an alternate driver is at no time somehow exploitable by the wrong
party.
The two masks are located in sysfs at /sys/bus/ap/apmask and
/sys/bus/ap/aqmask. The mask syntax is exactly the same as the
already existing mask attributes in the /sys/bus/ap directory (for
example
[Kernel-packages] [Bug 1825210] Re: [SRU] Please sync vbox modules from virtualbox 6.0.6 on next kernel update
** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1825210 Title: [SRU] Please sync vbox modules from virtualbox 6.0.6 on next kernel update Status in linux package in Ubuntu: Fix Released Status in linux source package in Disco: Fix Released Bug description: [SRU Justification] Impact: The virtualbox package was updated in disco just prior to release, with numerous bug fixes. It is standard practice during development to sync our in-kernel source with the latest version of the virtualbox-guest-dkms package, however this upload was done so late in the release that there was not time to update the source in our kernel tree. Fix: Re-sync the vbox guest dkms drivers from virtualbox 6.0.6-dfsg-1. Regression Potential: This is a sync from the dkms package in the disco-release pocket, thus the code has presumably been tested against the Ubuntu Disco kernel. However, this is a very large pile of changes, and contains more than just bug fixes, so regressions are possible. Test Case: Boot a kernel with the updated driver in virtualbox and confirm that the guest drier functionality works as expected. --- * the changes are already in disco (vbox-guest-dkms), and they are fixes for the kernel 5.0. They might seem a lot of changes, but they are needed, and probably some of them are even CVE fixes... As said, vbox 6.0.6 includes lots of fixes for host/guest kernel modules, and they should be syncd when possible. thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825210/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1798427] Re: kvm doesn't work on 36 physical bits systems
** Tags added: cscc
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1798427
Title:
kvm doesn't work on 36 physical bits systems
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Cosmic:
Fix Released
Bug description:
[Impact]
A guest will hang while booting under 4.18.0-10.11 because of "kvm: x86: Set
highest physical address bits in non-present/reserved SPTEs", which came in via
4.18.y.
[Test Case]
A guest was booted after applying the patch.
[Regression Potential]
It might break KVM on systems with different physical memory limits, which is
just what upstream might have been testing the most.
A fix is already upstream, and already present in 4.18.14.
This would be upstream commit
daa07cbc9ae3da2d61b7ce900c0b9107d134f2c1 ("KVM: x86: fix L1TF's MMIO GFN
calculation").
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798427/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1800641] Re: [Ubuntu] qeth: Fix potential array overrun in cmd/rc lookup
** Tags added: cscc
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1800641
Title:
[Ubuntu] qeth: Fix potential array overrun in cmd/rc lookup
Status in Ubuntu on IBM z Systems:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Xenial:
Fix Released
Status in linux source package in Bionic:
Fix Released
Status in linux source package in Cosmic:
Fix Released
Bug description:
== SRU Justification ==
IBM is requesting these commits in s390 for X, B and C. The bug
description the commits fix is as follows:
Description: qeth: Fix potential array overrun in cmd/rc lookup Symptom:
Infinite loop when processing a received cmd.
Problem: qeth_get_ipa_cmd_name() and qeth_get_ipa_msg() are used to build
human-readable messages for received cmd data.
== Fixes ==
065a2cdcbdf8 ("s390: qeth_core_mpc: Use ARRAY_SIZE instead of reimplementing
its function")
048a7f8b4ec0 ("s390: qeth: Fix potential array overrun in cmd/rc lookup")
== Regression Potential ==
Low. Limited to s390.
== Test Case ==
A test kernel was built with these two patches and tested by IBM.
The bug reporter states the test kernel resolved the bug.
Description: qeth: Fix potential array overrun in cmd/rc lookup
Symptom: Infinite loop when processing a received cmd.
Problem: qeth_get_ipa_cmd_name() and qeth_get_ipa_msg() are used
to build human-readable messages for received cmd data.
They store the to-be translated value in the last entry of a
global array, and then iterate over each entry until they found
the queried value (and the corresponding message string).
If there is no prior match, the lookup is intended to stop at
the final entry (which was previously prepared).
If two qeth devices are concurrently processing a received cmd,
one lookup can over-write the last entry of the global array
while a second lookup is in process. This second lookup will
then
never hit its stop-condition, and loop.
Solution: Remove the modification of the global array, and limit the
number
of iterations to the size of the array.
Upstream-ID: kernel 4.19
- 065a2cdcbdf8eb9aefb66e1a24b2d684b8b8852b
- 048a7f8b4ec085d5c56ad4a3bf450389a4aed5f9
Should also be applied, to all other Ubuntu Releases in the field !
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1800641/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1824350] Re: shiftfs: chown sets untranslated ids in lower fs
** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1824350 Title: shiftfs: chown sets untranslated ids in lower fs Status in linux package in Ubuntu: Fix Released Bug description: SRU Justification Impact: shiftfs_setattr() creates an iattr struct with shifted ids for the lower fs, but then mistakenly passes the original iattr struct when changing the lower filesystem attributes. As a result, chown on a shiftfs filesystem sets ownership using the untranslated user and group ids. Fix: Pass the struct containing shifted uids to notify_change(). Regression Potential: This is a simple and obvious fix, and it has been tested to confirm it fixes the issue. Therefore the risk of regressions is low. Test Case: Within a lxd container using shiftfs, run: # mkdir dir # touch file # ls -lh dir file drwxr-xr-x 2 root root 4.0K Apr 11 13:05 dir -rw-r--r-- 1 root root0 Apr 11 13:05 file # chown 500:500 dir file # ls -lh dir file Expected result: drwxr-xr-x 2 500 500 4.0K Apr 11 13:05 dir -rw-r--r-- 1 500 5000 Apr 11 13:05 file Result in 5.0.0-10.11: drwxr-xr-x 2 1000500 1000500 4.0K Apr 11 12:42 dir -rw-r--r-- 1 1000500 10005000 Apr 11 12:42 file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824350/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1818645] Re: Ubuntu18.04.01: [Power9] power8 Compat guest(RHEL7.6) crashes during guest boot with > 256G of memory (kernel/kvm)
** Tags added: cscc
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1818645
Title:
Ubuntu18.04.01: [Power9] power8 Compat guest(RHEL7.6) crashes during
guest boot with > 256G of memory (kernel/kvm)
Status in The Ubuntu-power-systems project:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Bionic:
Fix Released
Bug description:
== SRU Justification ==
Rebooting a PowerPC VM with > 256G of memory results in a guest crash.
== Fix ==
Backport commit 46dec40fb741 ("KVM: PPC: Book3S HV: Don't truncate
HPTE index in xlate function").
== Regression Potential ==
Low. Fix is trivial.
== Test Case ==
Create a PowerPC VM with > 256G of memory and reboot it repeatedly.
== Original description ==
== Comment: #0 - Satheesh Rajendran - 2019-02-28
04:38:22 ==
---Problem Description---
Power8 Compat guest(RHEL 7.6) crashes during guest boot with > 256G of memory
(kernel/kvm)
Contact Information = sathe...@in.ibm.com
---uname output---
Host Kernel: 4.15.0-1016-ibm-gt
ii qemu-system-ppc1:2.11+dfsg-
1ubuntu7.8-1ibm3 ppc64el QEMU
full system emulation binaries (ppc)
ii libvirt-bin4.0.0-1ubuntu8.6
ppc64el programs for the libvirt library
Guest kernel: 3.10.0-957.5.1.el7.ppc64le (rhel7.6 zstream)
Machine Type = power9 ppc64le
---Steps to Reproduce---
1. Boot a power8 compat guest with memory >256G
virsh define avocado-vt-vm1;virsh start --console avocado-vt-vm1 (guest xml
sosreport attached)
Guest crashes while booting
2019-02-28 10:36:44.752+: starting up libvirt version: 4.0.0, package:
1ubuntu8.6 (Christian Ehrhardt Fri, 09 Nov
2018 07:42:01 +0100), qemu version: 2.11.1(Debian
1:2.11+dfsg-1ubuntu7.8-1ibm3), hostname: cs-host-f37-ac922-3.pok.ibm.com
LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
QEMU_AUDIO_DRV=none /usr/bin/qemu-system-ppc64 -name
guest=avocado-vt-vm1,debug-threads=on -S -object
secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-15-avocado-vt-vm1/master-key.aes
-machine pseries-2.11,accel=kvm,usb=off,dump-guest-core=off -m 264192
-realtime mlock=off -smp 256,sockets=256,cores=1,threads=1 -uuid
f4e14f88-bf1b-4cc3-b6d6-958d514d6c18 -display none -no-user-config -nodefaults
-chardev
socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-15-avocado-vt-vm1/monitor.sock,server,nowait
-mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-shutdown
-boot strict=on -device qemu-xhci,id=usb,bus=pci.0,addr=0x3 -device
virtio-scsi-pci,id=scsi0,bus=pci.0,addr=0x2 -device
virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x4 -drive
file=/home/sath/avocado-fvt-wrapper/data/avocado-vt/images/rhel76-ppc64le.qcow2,format=qcow2,if=none,id=drive-scsi0-0-0-0
-device
scsi-hd,bus=scsi0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0-0-0-0,id=scsi0-0-0-0,bootindex=1
-netdev tap,fd=28,id=hostnet0,vhost=on,vhostfd=30 -device
virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:fc:fd:fe,bus=pci.0,addr=0x1
-chardev pty,id=charserial0 -device
spapr-vty,chardev=charserial0,id=serial0,reg=0x3000 -chardev
socket,id=charchannel0,path=/var/lib/libvirt/qemu/channel/target/domain-15-avocado-vt-vm1/org.qemu.guest_agent.0,server,nowait
-device
virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0
-device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5 -msg timestamp=on
2019-02-28 10:36:44.759+: 19598: info : libvirt version: 4.0.0, package:
1ubuntu8.6 (Christian Ehrhardt Fri, 09 Nov
2018 07:42:01 +0100)
2019-02-28 10:36:44.759+: 19598: info : hostname: cs-host-f37-ac922-3
2019-02-28 10:36:44.759+: 19598: info : virObjectUnref:350 :
OBJECT_UNREF: obj=0x76d594111710
2019-02-28T10:36:44.781703Z qemu-system-ppc64: -chardev pty,id=charserial0:
char device redirected to /dev/pts/3 (label charserial0)
2019-02-28T10:36:44.781945Z qemu-system-ppc64: warning: Number of SMP cpus
requested (256) exceeds the recommended cpus supported by KVM (128)
2019-02-28T10:36:44.781953Z qemu-system-ppc64: warning: Number of
hotpluggable cpus requested (256) exceeds the recommended cpus supported by KVM
(128)
2019-02-28 10:37:18.060+: shutting down, reason=crashed
2019-02-28T10:37:18.071969Z qemu-system-ppc64: terminating on signal 15 from
pid 14056 (/usr/sbin/libvirtd)
*Additional Instructions for sathe...@in.ibm.com:
-Post a private note with access information to the machine that the bug is
occuring on.
== Comment: #3 - Satheesh Rajendran - 2019-02-28
04:51:45 ==
Possible Upstream fix:
https://git.kernel.org/pub/scm/linux/kernel/git/paulus/powerpc.git/commit/?h=kvm-ppc-next=46dec40fb741f00f1864580130779aeeaf24fb3d
To
[Kernel-packages] [Bug 1799490] Re: Kernel 4.15 boot error on XenServer
** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1799490 Title: Kernel 4.15 boot error on XenServer Status in linux package in Ubuntu: Confirmed Bug description: I recently upgraded an ubuntu VM from 16.04.1 to 18.04.1 running on XenServer 7.1. The upgrade itself was fine, but several kernel updates after the upgrade have caused the VM to fail to boot. All kernels that fail to boot seem to be from 4.15. Current, the latest kernel I've tried is 4.15.0-38, though, day-to-day I'm running a 4.4 kernel since the VM is necessary to my environment. The error message on boot is: unchecked MSR access error: RDMSR from 0xc90 at rIP: 0x9806c04a (native_read_msr+0xa/0x30) The trace is attached as a screenshot. I haven't been able to get a log containing the output. user@host:~$ cat /proc/version_signature Ubuntu 4.4.0-112.135-generic 4.4.98 user@host:~$ sudo lspci -vnvn 00:00.0 Host bridge [0600]: Intel Corporation 440FX - 82441FX PMC [Natoma] [8086:1237] (rev 02) Subsystem: Red Hat, Inc Qemu virtual machine [1af4:1100] Physical Slot: 0 Control: I/O- Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- [disabled] 00:03.0 SCSI storage controller [0100]: XenSource, Inc. Xen Platform Device [5853:0001] (rev 02) Subsystem: XenSource, Inc. Xen Platform Device [5853:0001] Physical Slot: 3 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1799490/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1805414] Re: [Ubuntu] kernel: zcrypt: reinit ap queue state machine
** Tags added: cscc
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1805414
Title:
[Ubuntu] kernel: zcrypt: reinit ap queue state machine
Status in Ubuntu on IBM z Systems:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Bionic:
Fix Released
Status in linux source package in Cosmic:
Fix Released
Status in linux source package in Disco:
Fix Released
Bug description:
== SRU Justification ==
The vfio device driver when receiving an ap queue device does
additional resets thereby removing the registration for
interrupts for the ap device done by the ap bus core
code. So when later the vfio driver releases the device and
one of the default zcrypt drivers takes care of the device
the interrupt registration needs to get renewed. The current
code does no renew and result is that requests send into such
a queue will never see a reply processed - the application
hangs.
This commit has also been cc'd to upstream stable.
== Fix ==
104f708fd ("s390/zcrypt: reinit ap queue state machine during device probe")
== Regression Potential ==
Low. Limited to s390.
== Original Bug Description ==
Description: kernel: zcrypt: reinit ap queue state machine
Symptom: Zcrypt ap queue device not operational at host level after a
kvm guest used it.
Problem: The vfio device driver when receiving an ap queue device does
additional resets thereby removing the registration for
interrupts for the ap device done by the ap bus core
code. So when later the vfio driver releases the device and
one of the default zcrypt drivers takes care of the device
the interrupt registration needs to get renewed. The current
code does no renew and result is that requests send into such
a queue will never see a reply processed - the application
hangs.
Solution: This patch adds a function which resets the aq queue state
machine for the ap queue device and triggers the walk through
the initial states (which are reset and registration for
interrupts). This function is now called before the driver's
probe function is invoked.
When the association between driver and device is released,
the driver's remove function is called. The current
implementation calls a ap queue function
ap_queue_remove(). This invokation has been moved to the ap
bus function to make the probe / remove pair for ap bus and
drivers more symmetric.
Reproduction: Set up an kvm guest to use one or more ap queues in
pass-through mode. Start the guest. Stop the guest. Reassign
the ap resources back to the host system. Run an application
which uses exactly this ap resources. Without the fix, the
application hangs; with the fix the application should run
fine.
Upstream commit(s):
104f708fd1241b22f808bdf066ab67dc5a051de5
Available on kernel.org
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1805414/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836760] Re: ixgbe{vf} - Physical Function gets IRQ when VF checks link state
** Tags added: cscc
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1836760
Title:
ixgbe{vf} - Physical Function gets IRQ when VF checks link state
Status in linux package in Ubuntu:
Fix Committed
Status in linux source package in Xenial:
Fix Committed
Status in linux source package in Bionic:
Fix Committed
Status in linux source package in Cosmic:
Won't Fix
Status in linux source package in Disco:
Fix Committed
Status in linux source package in Eoan:
Fix Committed
Status in linux source package in FF-Series:
Fix Committed
Bug description:
[Impact]
* Intel NICs that are SR-IOV capable and are managed by ixgbe driver presents
a potentially harmful behavior when the ixgbevf-managed VFs (Virtual Functions)
perform an ethtool link check. The ixgbevf driver issues a mailbox command in
the ethtool link state handler, which induces one IRQ in the PF (Physical
Function) per link check.
* This was reported as a sort of "denial-of-service" from a guest; due to
some link check loop running inside a guest with PCI-PT of a ixgbevf-managed
VF, the host received a huge amount of IRQs causing soft-lockups.
* The patch proposed in this SRU request fix this behavior by relying in the
saved link state (obtained in the ixgbevf's watchdog routine) instead of
issuing a mailbox command to the PF in every link state check request. The
commit is available on Linus tree: 1e1b0c658d9b ("ixgbevf: Use cached link
state instead of re-reading the value for ethtool")
http://git.kernel.org/linus/1e1b0c658d9b
[Test case]
Reproducing the behavior is pretty simple; having a machine with an
Intel NIC managed by ixgbe, proceed with the following steps:
a) Create one or more VFs
(echo 1 > /sys/class/net//device/sriov_numvfs)
b) In a different terminal, monitor the non-TxRx PF IRQs:
(watch -n1 "cat /proc/interrupts | grep | grep -v Tx")
c) Run "ethtool " in a loop
Without the hereby proposed patch, the PF IRQs will increase.
[Regression potential]
The patch scope is restricted to ixgbevf ethtool link-check procedure,
and was developed by the vendor itself. Being a self-contained patch
affecting only this driver's ethtool handler, the worst potential
regression would be a wrong link state report.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836760/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1803827] Re: Cant install from usb or normal upgrade(says not supported) (Eee PC 904HD)
** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1803827 Title: Cant install from usb or normal upgrade(says not supported) (Eee PC 904HD) Status in linux package in Ubuntu: Confirmed Bug description: Cant install lubuntu 32 bit 18.10 or 19.04 (Disco Dingo Daily Builds) from usb or normal upgrade from 18.04 to 18.10(says not supported) it displays cdrom/casper/filesystem.squashfs error for the Asus Eee PC 904HD --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-39-generic. AplayDevices: List of PLAYBACK Hardware Devices card 0: Intel [HDA Intel], device 0: ALC269 Analog [ALC269 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: i386 ArecordDevices: List of CAPTURE Hardware Devices card 0: Intel [HDA Intel], device 0: ALC269 Analog [ALC269 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: asus725 F pulseaudio Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xf7eb8000 irq 24' Mixer name : 'Realtek ALC269' Components : 'HDA:10ec0269,1043834a,0014' Controls : 22 Simple ctrls : 10 CurrentDesktop: LXDE DistroRelease: Ubuntu 18.04 MachineType: ASUSTeK Computer INC. 904HD Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-39-generic root=UUID=d88102d1-73dc-40ae-9e3b-8d09460b1ae5 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-39-generic N/A linux-backports-modules-4.15.0-39-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-39-generic i686 UpgradeStatus: Upgraded to bionic on 2018-11-16 (1 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/22/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1002 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: 904HD dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: x.xx dmi.chassis.asset.tag: 0x dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTek Computer INC. dmi.chassis.version: x.x dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1002:bd09/22/2008:svnASUSTeKComputerINC.:pn904HD:pvrx.x:rvnASUSTeKComputerINC.:rn904HD:rvrx.xx:cvnASUSTekComputerINC.:ct10:cvrx.x: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: 904HD dmi.product.version: x.x dmi.sys.vendor: ASUSTeK Computer INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1803827/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1800849] Re: [Ubuntu] kvm: fix deadlock when killed by oom
** Tags added: cscc
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1800849
Title:
[Ubuntu] kvm: fix deadlock when killed by oom
Status in Ubuntu on IBM z Systems:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Xenial:
Fix Released
Status in linux source package in Bionic:
Fix Released
Status in linux source package in Cosmic:
Fix Released
Bug description:
== SRU Justification ==
Description: kvm: fix deadlock when killed by oom
Symptom: oom killer leaves processes in a deadlock state.
Problem: The problem arises in the rare cases in which
handle_mm_fault does not release the mm_sem.
Solution: Correct the issue by manually release the mm_sem when needed.
== Fix ==
306d6c49ac9ded4cb53b0925da52f2c2ada1 ("s390/kvm: fix deadlock when
killed by oom")
== Patch ==
commit 306d6c49ac9ded4cb53b0925da52f2c2ada1
Author: Claudio Imbrenda
Date: Mon Jul 16 10:38:57 2018 +0200
s390/kvm: fix deadlock when killed by oom
When the oom killer kills a userspace process in the page fault handler
while in guest context, the fault handler fails to release the mm_sem
if the FAULT_FLAG_RETRY_NOWAIT option is set. This leads to a deadlock
when tearing down the mm when the process terminates. This bug can only
happen when pfault is enabled, so only KVM clients are affected.
The problem arises in the rare cases in which handle_mm_fault does not
release the mm_sem. This patch fixes the issue by manually releasing
the mm_sem when needed.
Fixes: 24eb3a824c4f3 ("KVM: s390: Add FAULT_FLAG_RETRY_NOWAIT for guest
fault")
Cc: # 3.15+
Signed-off-by: Claudio Imbrenda
Signed-off-by: Martin Schwidefsky
== Regression Potential ==
Low and minimal, because:
- code change is s390x only
- limited to one single file: /arch/s390/mm/fault.c
- just two additional lines added (if stmt)
- Xenial and Cosmic already have this commit via upstream stable updates.
- Hence patch is just missing in Bionic.
- Test kernel was build for testting.
== Test Case ==
Create numerous KVM guests so that the host starts swapping
and memory becomes overcomitted and the oom killer is triggered.
__
Description: kvm: fix deadlock when killed by oom
Symptom: oom killer leaves processes in a deadlock state.
Problem: The problem arises in the rare cases in which
handle_mm_fault does not release the mm_sem.
Solution: Correct the issue by manually relaese the mm_sem
when needed.
Reproduction: Create numerous KVM guests so that the host starts
swapping and memory becomes overcomitted and the oom
killer is triggered.
kernel 4.19
Upstream-ID: 306d6c49ac9ded4cb53b0925da52f2c2ada1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1800849/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1810210] Re: Kernel 4.15.0-43 crashes laptop on boot
** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1810210 Title: Kernel 4.15.0-43 crashes laptop on boot Status in linux package in Ubuntu: Confirmed Bug description: Since upgrading kernel from 4.15.0-33 to 4.15.0-43 my laptop no longer boots, it crashes when reaching the stage where it says Reached Target Encrypted Volumes. Have reverted to 4.15.0-33 in the meantime. Is this something that can be rectified? Using an ASUS XM553MA laptop. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: aaron 1222 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.1 InstallationDate: Installed on 2018-12-06 (27 days ago) InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180717 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0bda:57b5 Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X553MA Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic root=UUID=7fdad478-0ec8-4191-9c7e-22f837dc7af3 ro ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-33-generic N/A linux-backports-modules-4.15.0-33-generic N/A linux-firmware 1.173.2 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: tessa Uname: Linux 4.15.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/10/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X553MA.211 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X553MA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX553MA.211:bd04/10/2015:svnASUSTeKCOMPUTERINC.:pnX553MA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX553MA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X553MA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810210/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1805693] Re: User reports a hang on 18.04 LTS(4.15.18) under a heavy I/O load
** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1805693 Title: User reports a hang on 18.04 LTS(4.15.18) under a heavy I/O load Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Bug description: User reports a hang under heavy I/O: The IO hang problem on our cloud is caused by IO hang in block-wbt wbt_wait. The fix commit id is 2887e41b910bb14fd847cf01ab7a5993db989d88. It is a block write buffer throttle queue lock contention and thundering herd issue in wbt_wait() We can recreate the problem easily by running concurrent IO from multiple VMs with sequential write. We can provide fio workload as needed for recreate. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1805693/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1821053] Re: [disco] [5.0.0-7.8] can't mount guest cifs share
** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1821053 Title: [disco] [5.0.0-7.8] can't mount guest cifs share Status in linux package in Ubuntu: Fix Released Bug description: Hi, with a simple smb.conf setup like this: [pub] path = /pub guest ok = yes The following mount command fails when the running kernel is 5.0.0-7: root@ubuntu:~# dmesg -C root@ubuntu:~# mount //localhost/pub /mnt -o guest mount error(13): Permission denied Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) root@ubuntu:~# dmesg [ 178.469307] CIFS: Attempting to mount //localhost/pub [ 178.469343] No dialect specified on mount. Default has changed to a more secure dialect, SMB2.1 or later (e.g. SMB3), from CIFS (SMB1). To use the less secure SMB1 dialect to access old servers which do not support SMB3 (or SMB2.1) specify vers=1.0 on mount. [ 178.481741] CIFS VFS: failed to connect to IPC (rc=-13) [ 178.485272] CIFS VFS: cifs_mount failed w/return code = -13 samba server logs, in debug 5, show: [2019/03/20 17:25:19.365445, 0] ../../libcli/smb/smb2_signing.c:169(smb2_signing_check_pdu) Bad SMB2 signature for message [2019/03/20 17:25:19.365524, 0] ../../lib/util/util.c:508(dump_data) [] A6 62 5F 50 9C D7 31 42 14 34 52 9F AA 49 C8 31 .b_P..1B .4R..I.1 [2019/03/20 17:25:19.365562, 0] ../../lib/util/util.c:508(dump_data) [] 31 37 12 A2 D5 D4 59 99 0B 63 C5 21 EB 86 70 74 17Y. .c.!..pt [2019/03/20 17:25:19.369055, 0] ../../libcli/smb/smb2_signing.c:169(smb2_signing_check_pdu) Bad SMB2 signature for message [2019/03/20 17:25:19.369092, 0] ../../lib/util/util.c:508(dump_data) [] 23 2C 4F 10 0E 4E 46 2E 8A 5B E3 70 0F B3 D3 FB #,O..NF. .[.p [2019/03/20 17:25:19.369120, 0] ../../lib/util/util.c:508(dump_data) [] 50 F7 C6 8A 6E BC B2 B7 1C 2F 43 30 90 6A 25 CA P...n... ./C0.j%. With kernel 4.19.0-12-generic, the exact same system, the command works: root@ubuntu:~# dmesg -C root@ubuntu:~# mount //localhost/pub /mnt -o guest root@ubuntu:~# dmesg [ 277.745885] FS-Cache: Loaded [ 277.768408] FS-Cache: Netfs 'cifs' registered for caching [ 277.768495] Key type cifs.spnego registered [ 277.768498] Key type cifs.idmap registered [ 277.768707] No dialect specified on mount. Default has changed to a more secure dialect, SMB2.1 or later (e.g. SMB3), from CIFS (SMB1). To use the less secure SMB1 dialect to access old servers which do not support SMB3 (or SMB2.1) specify vers=1.0 on mount. root@ubuntu:~# mount -t cifs //localhost/pub on /mnt type cifs (rw,relatime,vers=default,sec=none,cache=strict,uid=0,noforceuid,gid=0,noforcegid,addr=127.0.0.1,file_mode=0755,dir_mode=0755,soft,nounix,serverino,mapposix,rsize=1048576,wsize=1048576,echo_interval=60,actimeo=1) root@ubuntu:~# uname -r 4.19.0-12-generic Just looking at the list of patches queued up for the next upstream kernel release, at https://git.kernel.org/pub/scm/linux/kernel/git/stable/stable-queue.git/tree/queue-5.0, this one looks promising: https://git.kernel.org/pub/scm/linux/kernel/git/stable/stable-queue.git/tree/queue-5.0/cifs-do-not-skip-smb2-message-ids-on-send-failures.patch I can easily test a new kernel for you. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 20 18:04 seq crw-rw 1 root audio 116, 33 Mar 20 18:04 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu23 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: CRDA: N/A DistroRelease: Ubuntu 19.04 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) Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic root=PARTUUID=e2b8e290-77c5-437c-a78d-b59424881b58 ro console=tty1 console=ttyS0 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 RelatedPackageVersions: linux-restricted-modules-5.0.0-7-generic N/A linux-backports-modules-5.0.0-7-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: disco uec-images Uname: Linux 5.0.0-7-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install)
[Kernel-packages] [Bug 1825942] Re: kernel crash : net_sched race condition in tcindex_destroy()
** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1825942 Title: kernel crash : net_sched race condition in tcindex_destroy() Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Fix Released Bug description: [Impact] It is possible to trigger a NULL pointer dereference in tcindex_delete() with a simple reproducer script, this is because in tcindex_set_parms() when old_r doesn't exist we set the new exts to cr.exts that can be uninitialized, triggering the NULL pointer dereference. In addition to that we may also hit a race condition in tcindex_destroy() (as pointed out in the original bug report and also here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921542#10), that is also fixed upstream, but it requires 4b79817f7add "net_sched: switch to rcu_work". However adding these changes introduces three memory leak problems in cls_tcindex (that can be easily verified using the same test case). These leaks are also fixed upstream by 711ff09f3330 "net_sched: fix a memory leak in cls_tcindex" and 000d2aeda70c "net_sched: fix two more memory leaks in cls_tcindex", so we need to backport also these two additional fixes. After all these fixes are applied the test case doesn't seem to trigger any bug. [Test Case] #!/bin/sh -ex modprobe ifb while true; do tc qdisc add dev ifb0 root handle 2:0 prio bands 5 tc qdisc add dev ifb0 parent 2:5 sfq tc filter add dev ifb0 parent 2:0 protocol ip prio 5 handle 0 tcindex mask 0 classid 2:5 pass_on tc qdisc del dev ifb0 root || true done [Fix] * Fixes required to solve this problem: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=2df8bee5654bb2b7312662ca6810d4dc16b0b67f https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=8015d93ebd27484418d4952284fd02172fa4b0b2 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=033b228e7f26b29ae37f8bfa1bc6b209a5365e9f https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=1db817e75f5b9387b8db11e37d5f0624eb9223e0 [Regression Potential] * All upstream fixes, tested on the affected platform, backport changes are minimal. [Original bug report] I am running into a kernel crash issue using latest Ubuntu 4.15 kernel. It does not appear to have been fixed in Ubuntu-4.15.0-48.51. This crash has also been reported for debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921542 The kernel crash issue was fixed in February in the Linux kernel: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=056a17982adbd52b2a6c5ec6266cee4521cd931b I did test one of the recent kernel-ppa/mainline kernels, more specifically: linux-image-unsigned-4.19.34-041934-generic_4.19.34-041934.201904051741_amd64.deb It seems to fix the problem, that is, no crashes experienced so far. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825942/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1810214] Re: [ZenBook UX433FA_UX433FA, Realtek ALC294, Speaker, Internal] No sound at all
** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1810214 Title: [ZenBook UX433FA_UX433FA, Realtek ALC294, Speaker, Internal] No sound at all Status in linux package in Ubuntu: Fix Committed Bug description: There is no sound whatsoever while the controls all seems to indicate the playback is working. The patop's internal speaker, headphones, even bluetooth is not outputting any sound. Trying to upgrade the kernel to two different versions had no effect. There simply is no sound output nor is there any indication the microphone is working either, but without sound output that's hard to confirm. There are not issues with sounds when I boot into Windows ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 4.19.13-041913-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mac1193 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Jan 1 14:18:09 2019 InstallationDate: Installed on 2018-12-30 (2 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mac1193 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [ZenBook UX433FA_UX433FA, Realtek ALC294, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/19/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX433FA.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX433FA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX433FA.204:bd09/19/2018:svnASUSTeKCOMPUTERINC.:pnZenBookUX433FA_UX433FA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX433FA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX433FA_UX433FA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810214/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1824717] Re: kernel BUG at fs/attr.c:287 when using shiftfs
** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1824717 Title: kernel BUG at fs/attr.c:287 when using shiftfs Status in linux package in Ubuntu: Fix Released Bug description: SRU Justification Impact: It is possible to hit a BUG statement in notify_change() with shiftfs (below). This occurs when one of ATTR_KILL_SUID or ATTR_KILL_SGID is set in the attrs and notify_change() sets ATTR_MODE before calling shiftfs_setattr(). shiftfs_setattr() passes the attrs to notify_change(), and the BUG statement is hit due to ATTR_MODE being set with one of ATTR_KILL_SUID or ATTR_KILL_SGID set. Fix: Copy the logic used by ecryptfs and overlayfs to clear ATTR_MODE if one of these bits is set, allowning the lower fs to interpret the kill bits in its own way. Also fix a bug where changes to the attrs from setattr_prepare() are not propagated to the attrs used for the lower fs. Regression Potential: Limited to shiftfs, matches the behavior of other stacked filesystems, and has been tested (see below). Test Case: Tested in the lxd CI environment where the bug was originally discovered. No regressions were seen, and the BUG statement was not hit. --- [18558.819079] [ cut here ] [18558.819082] kernel BUG at fs/attr.c:287! [18558.823490] invalid opcode: [#1] SMP PTI [18558.828038] CPU: 2 PID: 26728 Comm: dpkg Tainted: P O 5.0.0-10-generic #11+shiftfsv201904110736 [18558.838152] Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 [18558.872092] RIP: 0010:notify_change+0x412/0x460 [18558.876843] Code: 55 00 e9 35 fe ff ff 48 3b 50 30 0f 85 88 fd ff ff e9 bf fe ff ff 41 83 ce 04 e9 21 ff ff ff 41 ba ff ff ff ff e9 ac fd ff ff <0f> 0b 4c 89 fe 4c 89 e7 e8 b1 af 00 00 41 89 c2 e9 b5 fe ff ff f6 [18558.896179] RSP: 0018:b706dbaf7d00 EFLAGS: 00010202 [18558.901984] RAX: 5cb1105d RBX: 1847 RCX: [18558.909241] RDX: 165a9c4b RSI: 165a9c4b RDI: 5cb1105d [18558.916491] RBP: b706dbaf7d38 R08: R09: [18558.923741] R10: R11: R12: 89fa79f756c0 [18558.931350] R13: 89fa43d89230 R14: 85ed R15: b706dbaf7d50 [18558.938616] FS: 7fe41f039040() GS:89fc61a8() knlGS: [18558.946928] CS: 0010 DS: ES: CR0: 80050033 [18558.952826] CR2: 5614215be0a8 CR3: 0007594fc002 CR4: 001606e0 [18558.960078] DR0: DR1: DR2: [18558.967395] DR3: DR6: fffe0ff0 DR7: 0400 [18558.975018] Call Trace: [18558.977810] ? setattr_prepare+0x178/0x200 [18558.982160] shiftfs_setattr+0xec/0x140 [18558.986149] notify_change+0x2d9/0x460 [18558.990014] chown_common+0x1c8/0x1e0 [18558.993917] do_fchownat+0x93/0xf0 [18558.997551] __x64_sys_chown+0x22/0x30 [18559.001522] do_syscall_64+0x5a/0x110 [18559.005481] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [18559.010652] RIP: 0033:0x7fe41e9193e7 [18559.014343] Code: 39 84 24 98 00 00 00 75 a1 48 89 df e8 d2 c5 f8 ff eb a0 e8 ab 38 02 00 66 2e 0f 1f 84 00 00 00 00 00 90 b8 5c 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 71 9a 2d 00 f7 d8 64 89 01 48 [18559.033294] RSP: 002b:7fff73c89d48 EFLAGS: 0297 ORIG_RAX: 005c [18559.041365] RAX: ffda RBX: 5614237e0190 RCX: 7fe41e9193e7 [18559.048820] RDX: 0008 RSI: RDI: 5614237e0190 [18559.056290] RBP: 5614237df110 R08: 001b R09: 002e [18559.063681] R10: f32f R11: 0297 R12: 7fff73c8a210 [18559.071386] R13: 561424166360 R14: 5614237e0190 R15: [18559.078773] Modules linked in: binfmt_misc veth ebtable_filter ebtables ip6t_MASQUERADE ip6table_nat nf_nat_ipv6 ipt_MASQUERADE xt_CHECKSUM xt_comment xt_tcpudp iptable_nat nf_nat_ipv4 nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 iptable_mangle bridge stp llc unix_diag ip6table_filter ip6_tables iptable_filter bpfilter zfs(PO) zunicode(PO) zavl(PO) icp(PO) zcommon(PO) nls_iso8859_1 znvpair(PO) spl(O) input_leds serio_raw sb_edac pvpanic mac_hid intel_rapl_perf sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel virtio_net aes_x86_64 nvme crypto_simd cryptd glue_helper net_failover psmouse nvme_core failover virtio_scsi i2c_piix4 [18559.161878]
[Kernel-packages] [Bug 1813663] Re: External monitors does not work anymore 4.15.0-44
** Tags added: ubuntu-certified ** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1813663 Title: External monitors does not work anymore 4.15.0-44 Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Bug description: I am using a docking station for my laptop. After install the 4.15.0-44 update my external monitors goes undetected after logging in or having the laptop closed. I am on 18.04.1 LTS with Intel® HD Graphics 620 (Kaby Lake GT2) Graphics. Going back to the 4.15.0-43 version makes it all work fine again. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jonas 2407 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=80397b76-2ded-4f7d-adbf-dfdface8e2d4 InstallationDate: Installed on 2018-10-17 (103 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 20HF004MMX Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-44-generic root=UUID=64cf1582-d574-4e2f-a40a-7942c40caf5d ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-44.47-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-44-generic N/A linux-backports-modules-4.15.0-44-generic N/A linux-firmware 1.173.3 Tags: bionic Uname: Linux 4.15.0-44-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker kvm lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/14/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N1WET51W (1.30 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HF004MMX dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1WET51W(1.30):bd09/14/2018:svnLENOVO:pn20HF004MMX:pvrThinkPadT470s:rvnLENOVO:rn20HF004MMX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T470s dmi.product.name: 20HF004MMX dmi.product.version: ThinkPad T470s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813663/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1823753] Re: arm64: cma_alloc errors at boot
** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1823753 Title: arm64: cma_alloc errors at boot Status in linux package in Ubuntu: Fix Released Status in linux source package in Disco: Fix Released Status in linux source package in Eoan: Fix Released Bug description: [Impact] We enabled CONFIG_DMA_CMA to fix bug 1803206, but that led to a regression on other arm64 systems that began spewing these messages on boot - sometimes > 10K of them: [ 19.534097] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12 [ 19.534109] cma: cma_alloc: alloc failed, req-size: 16 pages, ret: -12 [ 19.534113] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12 [ 19.534126] cma: cma_alloc: alloc failed, req-size: 16 pages, ret: -12 [ 19.534130] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12 [ 19.534142] cma: cma_alloc: alloc failed, req-size: 16 pages, ret: -12 [ 19.534146] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12 [ 19.534157] cma: cma_alloc: alloc failed, req-size: 16 pages, ret: -12 [ 19.534161] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12 [ 19.534173] cma: cma_alloc: alloc failed, req-size: 16 pages, ret: -12 [ 19.534177] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12 In a previous SRU (bug 1828092), we worked around this by just rate- limiting these messages. These are "err" priority messages though, so even a lower number of them is still disconcerting. [Fix] 1) Bump up the amount of available CMA on arm64 to 32M (same as upstream defconfig) 2) A patch-set from linux-next that redirects dma-direct contiguous allocations to alloc_pages() for single page allocations (single pages are by definition contiguous), avoiding CMA usage/fragmentation. [Test Case] dmesg | grep "cma_alloc: alloc failed" Some system configs will still have some of these errors even after this fix - but this should reduce them significantly. Per-driver optimizations can be used to make further improvements, but we should track those in other bugs. [Regression Risk] Tested on a HiSilicon D06 and HP m400 (Hi1620 & X-Gene arm64). Regression tested on: - Raspberry Pi 3B (see Comment #22) - Power9 system (ppc64el) - z/VM instance (s390x) - Intel Centerton system (amd64) Test builds are staged at http://ppa.launchpad.net/~dannf/ubuntu/cma To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823753/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1825420] Re: package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to install/upgrade: triggers looping, abandoned
** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1825420 Title: package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to install/upgrade: triggers looping, abandoned Status in Ubuntu MATE: Invalid Status in bamf package in Ubuntu: Confirmed Status in dpkg package in Ubuntu: Confirmed Status in initramfs-tools package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: Confirmed Status in mime-support package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Have Ubuntu 18.10 installed 2. Install all updates to it 3. Switch to Main server 4. Launch update-manager 5. Confirm upgrading to 19.04 6. Wait for upgrade process to finish Expected results: * upgrade process ended without errors Actual results: * upgrade process ended with warning message: Could not install 'linux-image-5.0.0-13-generic' The upgrade will continue but the 'linux-image-5.0.0-13-generic' package may not be in a working state. Please consider submitting a bug report about it. triggers looping, abandoned Workaround: Run recommended `dpkg --configure -a` before actual reboot. System info: running VirtualBox guest with virtualbox-guest-x11 (6.0.6-dfsg-1) inside VirtualBox 5.1.38 host. ProblemType: Package DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-13-generic 5.0.0-13.14 ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20 Uname: Linux 4.18.0-17-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mate 1542 F pulseaudio Date: Thu Apr 18 22:56:56 2019 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2019-02-17 (60 days ago) InstallationMedia: Ubuntu-MATE 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) IwConfig: lono wireless extensions. enp0s3no wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox ProcFB: 0 vboxdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-17-generic root=UUID=01417e27-d554-4ce8-91bc-1dda8392c976 ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.7, Python 3.7.3, python3-minimal, 3.7.3-1 PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.16-1 RelatedPackageVersions: grub-pc 2.02+dfsg1-12ubuntu2 RfKill: SourcePackage: linux StagingDrivers: vboxvideo Title: package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to disco on 2019-04-18 (0 days ago) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1825420/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1820948] Re: i40e xps management broken when > 64 queues/cpus
** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1820948 Title: i40e xps management broken when > 64 queues/cpus Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Bug description: [Impact] Transmit packet steering (xps) settings don't work when the number of queues (cpus) is higher than 64. This is currently still an issue on the 4.15 kernel (Xenial -hwe and Bionic kernels). It was fixed in Intel's i40e driver version 2.7.11 and in 4.16-rc1 mainline Linux (i.e. Cosmic, Disco have fix). Fix - The following commit fixes this issue (as identified by Lihong Yang in discussion with Intel i40e team): "i40e: Fix the number of queues available to be mapped for use" Commit: bc6d33c8d93f520e97a8c6330b8910053d4f It requires the following commit as well: i40e: Do not allow use more TC queue pairs than MSI-X vectors exist Commit: 1563f2d2e01242f05dd523ffd56fe104bc1afd58 [Test Case] 1. Kernel version: Bionic/Xenial -hwe: any 4.15 kernel i40e driver version: 2.1.14-k Any system with > 64 CPUs 2. For any queue 0 - 63, you can read/set tx xps: echo > /sys/class/net/eth2/queues/tx-63/xps_cpus echo $? 0 cat /sys/class/net/eth2/queues/tx-63/xps_cpus 00,, But for any queue number > 63, we see this error: echo > /sys/class/net/eth2/queues/tx-64/xps_cpus echo: write error: Invalid argument cat /sys/class/net/eth2/queues/tx-64/xps_cpus cat: /sys/class/net/eth2/queues/tx-64/xps_cpus: Invalid argument To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820948/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1810267] Re: hard lockup on multiple CPUs in spl_cache_flush
** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1810267 Title: hard lockup on multiple CPUs in spl_cache_flush Status in linux package in Ubuntu: Confirmed Bug description: Photo of failed machine, and video of a second lockup at https://photos.app.goo.gl/9qUxysZ4LN1NRdrA7 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-43-generic 4.15.0-43.46 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/hwC2D0', '/dev/snd/pcmC2D7p', '/dev/snd/controlC1', '/dev/snd/pcmC2D3p', '/dev/snd/controlC2', '/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Wed Jan 2 20:14:38 2019 InstallationDate: Installed on 2013-12-09 (1850 days ago) InstallationMedia: Ubuntu-Server 13.10 "Saucy Salamander" - Release amd64 (20131016) MachineType: System manufacturer System Product Name ProcEnviron: LANGUAGE=en_NZ:en TERM=xterm PATH=(custom, no user) LANG=en_NZ.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/ROOT/ubuntu@/boot/vmlinuz-4.15.0-43-generic root=ZFS=tr2srv/ROOT/ubuntu ro nomdmonddf nomdmonisw PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.173.2 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-06-26 (189 days ago) dmi.bios.date: 10/12/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0808 dmi.board.asset.tag: Default string dmi.board.name: PRIME X399-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0808:bd10/12/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX399-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810267/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811259] Re: 4.20 kernel on s390x VM crashes
** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1811259 Title: 4.20 kernel on s390x VM crashes Status in Linux: Fix Released Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Disco: Fix Released Bug description: Booting with 4.20.0-2-generic on a s390x 2 CPU VM we hit a panic: [0.394835] Linux version 4.20.0-2-generic (buildd@bos02-s390x-015) (gcc version 8.2.0 (Ubuntu 8.2.0-13ubuntu1)) #3-Ubuntu SMP Thu Jan 3 18:43:01 UTC 2019 (Ubuntu 4.20.0-2.3-generic 4.20.0) [0.394838] setup.289988: Linux is running under KVM in 64-bit mode [0.394846] setup.b050d0: The maximum memory size is 2048MB [0.394866] numa.196305: NUMA mode: plain [0.394893] cpu.33a262: 2 configured CPUs, 0 standby CPUs [0.394999] Write protected kernel read-only data: 10464k [0.395034] Zone ranges: [0.395035] DMA [mem 0x-0x7fff] [0.395037] Normal empty [0.395038] Movable zone start for each node [0.395039] Early memory node ranges [0.395041] node 0: [mem 0x-0x7fff] [0.395042] Initmem setup node 0 [mem 0x-0x7fff] [0.413802] percpu: Embedded 25 pages/cpu @(ptrval) s62208 r8192 d32000 u102400 [0.413824] Built 1 zonelists, mobility grouping on. Total pages: 516096 [0.413825] Policy zone: DMA [0.413827] Kernel command line: root=LABEL=cloudimg-rootfs [0.450276] Memory: 2034164K/2097152K available (8116K kernel code, 1079K rwdata, 2344K rodata, 992K init, 772K bss, 62988K reserved, 0K cma-reserved) [0.450283] random: get_random_u64 called from kmem_cache_open+0x4c/0x4f0 with crng_init=0 [0.450432] SLUB: HWalign=256, Order=0-3, MinObjects=0, CPUs=3, Nodes=1 [0.450434] ftrace: allocating 27385 entries in 107 pages [0.473325] rcu: Hierarchical RCU implementation. [0.473327] rcu: RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=3. [0.473328]Tasks RCU enabled. [0.473329] rcu: RCU calculated value of scheduler-enlistment delay is 10 jiffies. [0.473330] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=3 [0.475371] NR_IRQS: 3, nr_irqs: 3, preallocated irqs: 3 [0.475402] clocksource: tod: mask: 0x max_cycles: 0x3b0a9be803b0a9, max_idle_ns: 1805497147909793 ns [0.475558] printk: console [ttyS1] enabled [0.475623] pid_max: default: 32768 minimum: 301 [0.475658] LSM: Security Framework initializing [0.475660] Yama: becoming mindful. [0.475677] AppArmor: AppArmor initialized [0.476134] Dentry cache hash table entries: 262144 (order: 9, 2097152 bytes) [0.476352] Inode-cache hash table entries: 131072 (order: 8, 1048576 bytes) [0.476370] Mount-cache hash table entries: 4096 (order: 3, 32768 bytes) [0.476377] Mountpoint-cache hash table entries: 4096 (order: 3, 32768 bytes) [0.476726] rcu: Hierarchical SRCU implementation. [0.476927] smp: Bringing up secondary CPUs ... [0.477181] smp: Brought up 1 node, 2 CPUs [0.477549] devtmpfs: initialized [0.477882] clocksource: jiffies: mask: 0x max_cycles: 0x, max_idle_ns: 1911260446275 ns [0.477902] futex hash table entries: 1024 (order: 6, 262144 bytes) [0.478105] NET: Registered protocol family 16 [0.478134] audit: initializing netlink subsys (disabled) [0.478183] audit: type=2000 audit(1547122707.960:1): state=initialized audit_enabled=0 res=1 [0.478222] Spectre V2 mitigation: execute trampolines [0.479205] HugeTLB registered 1.00 MiB page size, pre-allocated 0 pages [0.479623] SCSI subsystem initialized [0.479856] NetLabel: Initializing [0.479858] NetLabel: domain hash size = 128 [0.479859] NetLabel: protocols = UNLABELED CIPSOv4 CALIPSO [0.479871] NetLabel: unlabeled traffic allowed by default [0.507362] VFS: Disk quotas dquot_6.6.0 [0.507378] VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes) [0.507486] AppArmor: AppArmor Filesystem Enabled [0.507847] NET: Registered protocol family 2 [0.507976] tcp_listen_portaddr_hash hash table entries: 1024 (order: 2, 16384 bytes) [0.507994] TCP established hash table entries: 16384 (order: 5, 131072 bytes) [0.508126] TCP bind hash table entries: 16384 (order: 6, 262144 bytes) [0.508235] TCP: Hash tables configured (established 16384 bind 16384) [0.508269] UDP hash table entries: 1024 (order: 3, 32768 bytes) [0.508287] UDP-Lite hash table entries: 1024 (order: 3, 32768 bytes) [0.508336] NET: Registered protocol family 1 [0.508343] NET: Registered protocol family 44 [0.508374]
[Kernel-packages] [Bug 1809993] Re: Lenovo X1C6 trackpad functions broken
** Tags added: ubuntu-certified ** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1809993 Title: Lenovo X1C6 trackpad functions broken Status in linux package in Ubuntu: Fix Released Bug description: Summary: After kernel update the trackpad advanced functions, like two finger scrolling and mouse acceleration have stopped working. Expected Result: Two finer scroll works and the mouse has acceleration features work Actual Result: Two finer scroll works and the mouse has acceleration features do not work Steps to reproduce: 1. Lenovo X1C6 (LENOVO 20KHCTO1WW/20KHCTO1WW, BIOS N23ET59W (1.34 ) 11/08/2018) 2. Install 18.04 LTS 3. config-4.15.0-42-generic acceleration works, while config-4.15.0-43-generic does not This appears to be some sort of regression or change in behavior between kernel versions. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: powersj1597 F pulseaudio CurrentDesktop: communitheme:ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=1eb43198-8ef5-4035-8b81-74c3e2936ad7 InstallationDate: Installed on 2018-12-06 (22 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 5986:2115 Acer, Inc Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20KHCTO1WW Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-42-generic root=/dev/mapper/ubuntu--vg-root ro ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-42-generic N/A linux-backports-modules-4.15.0-42-generic N/A linux-firmware 1.173.2 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 4.15.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/08/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET59W (1.34 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KHCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN23ET59W(1.34):bd11/08/2018:svnLENOVO:pn20KHCTO1WW:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 6th dmi.product.name: 20KHCTO1WW dmi.product.version: ThinkPad X1 Carbon 6th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1809993/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1803960] Re: 4.18.0 kernels hang system randomly
** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1803960 Title: 4.18.0 kernels hang system randomly Status in linux package in Ubuntu: Triaged Status in linux source package in Cosmic: Triaged Bug description: I've been using 18.04 on an Asus T300CHI without issue until I decided to switch to the v4.18 kernels from 18.10 via linux-image-lowlatency- hwe-18.04-edge. Since then the system randomly but regularly completely hangs. Only a hard power-off resolves it. Frustratingly there are never any clues in the kernel logs so it is very difficult to point to anything that might cause it; there is never any obvious pattern in the workload, the user interaction, or state of the PC when the hang occurs. A week ago I switched to the Ubuntu mainline v4.19 builds and that resolved the issue. I was reminded of it again today when it hung a few minutes ago. After the reboot I checked the previous boot log and realised the PC had accidentally been booted with the default v4.18 kernel rather than v4.19. I don't think this report can be debugged but it is worth having a tracking bug in case other people experience the same issue with v4.18. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1803960/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1813873] Re: Userspace break as a result of missing patch backport
** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1813873 Title: Userspace break as a result of missing patch backport Status in linux package in Ubuntu: Fix Committed Status in linux source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Bug description: Hi, The most recent set of Ubuntu kernels applied a variety of tty patches including: https://github.com/torvalds/linux/commit/c96cf923a98d1b094df9f0cf97a83e118817e31b But have not applied the more recent https://github.com/torvalds/linux/commit/d3736d82e8169768218ee0ef68718875918091a0 patch. This second patch is required to prevent a rather serious regression where userspace applications reading from stdin can receive EAGAIN when they should not. I will try to link correspondence from the mailing list archives once they are available, but for now if you have access to the linux- console mailing list you can find discussion under the thread "Userspace break? read from STDIN returns EAGAIN if tty is "touched"". I would appreciate it if this could be examined soon as it is a regression on userspace. Thanks Michael Good: 4.15.0-43-generic #46-Ubuntu SMP Thu Dec 6 14:45:28 UTC 2018 Bad: 4.15.0-44-generic #47-Ubuntu SMP Mon Jan 14 11:26:59 UTC 2019 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813873/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822870] Re: Backport support for software count cache flush Spectre v2 mitigation. (CVE) (required for POWER9 DD2.3)
** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1822870 Title: Backport support for software count cache flush Spectre v2 mitigation. (CVE) (required for POWER9 DD2.3) Status in The Ubuntu-power-systems project: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Bug description: [IMPACT] Need to further address the Spectre v2 and Meltdown vulnerability in Power with software count cache flush Spectre v2 mitigation support for Power9 DD2.3, and additional Spectre/Meltdown related patches for Power9. [Fix] List of upstream patches identified by IBM in comment #4, #5, and #8. [Test] Pre-req: requires Power9 DD2.3 hardware. A test kernel is available in PPA ppa:ubuntu-power-triage/lp1822870 and the kernel was tested by IBM. Please see comment #11 and #14 for details. [REGRESSION POTENTIAL] The patches are isolated to the ppc64el architecture and does not impact generic code. ppc64el test kernel was tested by IBM and no regressions were reported. [OTHER INFO] For the different kernels: The HWE a563fd9c62f0 UBUNTU: Ubuntu-hwe-4.18.0-17.18~18.04.1 appears to have all patches. Disco appears to be missing only this patch: 92edf8df0ff2ae86cc632eeca0e651fd8431d40d powerpc/security: Fix spectre_v2 reporting Cosmic (which is supported until July) is missing a number of patches: cf175dc315f90185128fb061dc05b6fbb211aa2f powerpc/64: Disable the speculation barrier from the command line 6453b532f2c8856a80381e6b9a1f5ea2f12294df powerpc/64: Make stf barrier PPC_BOOK3S_64 specific. 179ab1cbf883575c3a585bcfc0f2160f1d22a149 powerpc/64: Add CONFIG_PPC_BARRIER_NOSPEC af375eefbfb27cbb5b831984e66d724a40d26b5c powerpc/64: Call setup_barrier_nospec() from setup_arch() 406d2b6ae3420f5bb2b3db6986dc6f0b6dbb637b powerpc/64: Make meltdown reporting Book3S 64 specific 06d0bbc6d0f56dacac3a79900e9a9a0d5972d818 powerpc/asm: Add a patch_site macro & helpers for patching instructions dc8c6cce9a26a51fc19961accb978217a3ba8c75 powerpc/64s: Add new security feature flags for count cache flush ee13cb249fabdff8b90aaff61add347749280087 powerpc/64s: Add support for software count cache flush ba72dc171954b782a79d25e0f4b3ed91090c3b1e powerpc/pseries: Query hypervisor for count cache flush settings 99d54754d3d5f896a8f616b0b6520662bc99d66b powerpc/powernv: Query firmware for count cache flush settings 7d8bad99ba5a22892f0cad6881289fdc3875a930 powerpc/fsl: Fix spectre_v2 mitigations reporting 92edf8df0ff2ae86cc632eeca0e651fd8431d40d powerpc/security: Fix spectre_v2 reporting This appears to already be in -next. For the bionic 18.04.1 (4.15) kernel only this patch is already part of master-next: a6b3964ad71a61bb7c61d80a60bea7d42187b2eb powerpc/64s: Add barrier_nospec The others are ported, there were only 3 that were not clean. Those are: 2eea7f067f495e33b8b116b35b5988ab2b8aec55 powerpc/64s: Add support for ori barrier_nospec patching This failed because commit a048a07d7f4535baa4cbad6bc024f175317ab938 is missing, but it does not look like that is required here. cb3d6759a93c6d0aea1c10deb6d00e111c29c19c powerpc/64s: Enable barrier_nospec based on firmware settings This failed because debugfs was already included, I can see that previously added, I didn't see where it was previously removed. 06d0bbc6d0f56dacac3a79900e9a9a0d5972d818 powerpc/asm: Add a patch_site macro & helpers for patching instructions This failed because 8183d99f4a22c is not included - but doesn't seem necessary. All other patches applied with, at most, some fuzz. Has had a little testing - boots, check debugfs, etc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1822870/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799276] Re: [Bionic] ipmi: Remove ACPI SPMI probing from the SSIF (I2C) driver
** Tags added: cscc
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1799276
Title:
[Bionic] ipmi: Remove ACPI SPMI probing from the SSIF (I2C) driver
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Bionic:
Fix Released
Bug description:
[Impact]
The IPMI spec states:
The purpose of the SPMI Table is to provide a mechanism that can be
used by the OSPM (an ACPI term for “OS Operating System-directed
configuration and Power Management” essentially meaning an ACPI-aware
OS or OS loader) very early in the boot process, e.g., before the
ability to execute ACPI control methods in the OS is available.
When we are probing IPMI in Linux, ACPI control methods are available,
so we shouldn't be probing using SPMI. It could cause some confusion
during the probing process.
[Fix]
Fixed upstream in 4.17:
commit 4866b1dce0389013a268f0ab63f7229b30c6e5fe
Author: Corey Minyard
Date: Thu Mar 8 15:00:28 2018 -0600
ipmi: Remove ACPI SPMI probing from the SSIF (I2C) driver
[Test]
-- Test case --
for i in {1..500}; do sudo modprobe -r ipmi_ssif; sleep 2s ; sudo modprobe
ipmi_ssif || exit; done
--
-- Before Applying the patch --
Jun 19 18:53:04 starbuck kernel: [ 126.351580] ipmi_ssif 0-000e: Found new
BMC (man_id: 0x00, prod_id: 0x0202, dev_id: 0x20)
Jun 19 18:53:06 starbuck kernel: [ 128.725391] ipmi_ssif: probe of
dmi-ipmi-ssif.1 failed with error -17
-- With patch applied --
Oct 19 19:59:49 starbuck kernel: [ 1501.699109] IPMI SSIF Interface driver
Oct 19 19:59:49 starbuck kernel: [ 1501.730439] ipmi_ssif: Trying
SMBIOS-specified SSIF interface at i2c address 0xe, adapter xlp9xx-i2c, slave
address 0x20
Oct 19 19:59:49 starbuck kernel: [ 1501.862509] ipmi_ssif 0-000e: Found new
BMC (man_id: 0x00, prod_id: 0x0202, dev_id: 0x20)
[Regression Potential]
This patch applies to ipmi_ssif driver and was tested on ARM64 Cavium
ThunderX2 platform and no regressions were found.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1799276/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1729337] Re: CIFS errors on 4.4.0-98, but not on 4.4.0-97 with same config
** Tags added: cscc
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1729337
Title:
CIFS errors on 4.4.0-98, but not on 4.4.0-97 with same config
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Trusty:
Fix Released
Status in linux source package in Xenial:
Fix Released
Status in linux source package in Zesty:
Fix Released
Status in linux source package in Artful:
Won't Fix
Bug description:
== SRU Justification ==
The bug reporter stated they have a cluster of servers that applied Xenial
updates
and then were unable to mount CIFS shares after upgrading to 4.4.0-98. The
same machines on 4.4.0-97 do not hit the regression. It was found that the
regression is fixed by mainline commit:
4587eee04e2a ("SMB3: Validate negotiate request must always be signed").
This fix is required in all Ubuntu supported releases. Commit 4587eee04e2a
landed in mailine as of 4.14-rc7. It was also cc'd to upstream stable,
but it has not landed in any stable releases yet, which is the reason for
this SRU.
== Fix ==
commit 4587eee04e2ac7ac3ac9fa2bc164fb6e548f99cd
Author: Steve French
Date: Wed Oct 25 15:58:31 2017 -0500
SMB3: Validate negotiate request must always be signed
== Regression Potential ==
This patch is to fix a regression. It was also cc'd to upstream stable, so
it received addition review upstream.
We have a cluster of servers that applied a security update overnight
and were unable to mount CIFS shares after upgrading to 4.4.0-98. The
same machines on 4.4.0-97 were fine the night before, and are fine
after downgrading. The only error message CIFS would report, even on
verbose, was:
[ 257.089876] CIFS VFS: validate protocol negotiate failed: -11
[ 257.089964] CIFS VFS: cifs_mount failed w/return code = -5
Rebooting did not help. Nor did attempting to mount the share
manually using mount -t cifs.
Here's the offending line from our /etc/fstab (with hostnames
sanitized):
//server/share /mnt/share cifs
rw,user,credentials=/etc/samba/credentials.share,uid=33,gid=33,file_mode=0770,dir_mode=0770
,exec,soft,noserverino,vers=3.0 0 0
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-98-generic 4.4.0-98.121
ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90
Uname: Linux 4.4.0-98-generic x86_64
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Nov 1 07:56 seq
crw-rw 1 root audio 116, 33 Nov 1 07:56 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.1-0ubuntu2.10
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: Wed Nov 1 08:49:47 2017
HibernationDevice: RESUME=/dev/mapper/ubuntu--template--vg-swap_1
InstallationDate: Installed on 2016-12-16 (319 days ago)
InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64
(20160719)
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
Lsusb: Error: command ['lsusb'] failed with exit code 1:
MachineType: VMware, Inc. VMware Virtual Platform
PciMultimedia:
ProcFB: 0 svgadrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-98-generic
root=/dev/mapper/ubuntu--template--vg-root ro
RelatedPackageVersions:
linux-restricted-modules-4.4.0-98-generic N/A
linux-backports-modules-4.4.0-98-generic N/A
linux-firmware1.157.13
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/21/2015
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: 6.00
dmi.board.name: 440BX Desktop Reference Platform
dmi.board.vendor: Intel Corporation
dmi.board.version: None
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias:
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd09/21/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
dmi.product.name: VMware Virtual Platform
dmi.product.version: None
dmi.sys.vendor: VMware, Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1729337/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
