[Kernel-packages] [Bug 1786890] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1786890 Title: AR3012 Bluetooth Status in linux package in Ubuntu: Confirmed Bug description: Qualcomm Atheros AR3012, sometimes can't work ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-30-generic 4.15.0-30.32 ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18 Uname: Linux 4.15.0-30-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rafael 1660 F pulseaudio CurrentDesktop: communitheme:ubuntu:GNOME Date: Mon Aug 13 22:26:37 2018 InstallationDate: Installed on 2018-05-09 (96 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: TOSHIBA Satellite L845 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic root=UUID=947b919c-6edd-4dc8-8592-b3a5cc7a25c4 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-30-generic N/A linux-backports-modules-4.15.0-30-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/27/2012 dmi.bios.vendor: Insyde Corp. dmi.bios.version: 6.50 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Type2 - Board Product Name1 dmi.board.vendor: Type2 - Board Vendor Name1 dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis Manufacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvr6.50:bd12/27/2012:svnTOSHIBA:pnSatelliteL845:pvrPSK8GM-025TM4:rvnType2-BoardVendorName1:rnType2-BoardProductName1:rvrType2-BoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion: dmi.product.family: Type1Family dmi.product.name: Satellite L845 dmi.product.version: PSK8GM-025TM4 dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786890/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786890] [NEW] AR3012 Bluetooth
Public bug reported: Qualcomm Atheros AR3012, sometimes can't work ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-30-generic 4.15.0-30.32 ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18 Uname: Linux 4.15.0-30-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rafael 1660 F pulseaudio CurrentDesktop: communitheme:ubuntu:GNOME Date: Mon Aug 13 22:26:37 2018 InstallationDate: Installed on 2018-05-09 (96 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: TOSHIBA Satellite L845 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic root=UUID=947b919c-6edd-4dc8-8592-b3a5cc7a25c4 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-30-generic N/A linux-backports-modules-4.15.0-30-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/27/2012 dmi.bios.vendor: Insyde Corp. dmi.bios.version: 6.50 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Type2 - Board Product Name1 dmi.board.vendor: Type2 - Board Vendor Name1 dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis Manufacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvr6.50:bd12/27/2012:svnTOSHIBA:pnSatelliteL845:pvrPSK8GM-025TM4:rvnType2-BoardVendorName1:rnType2-BoardProductName1:rvrType2-BoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion: dmi.product.family: Type1Family dmi.product.name: Satellite L845 dmi.product.version: PSK8GM-025TM4 dmi.sys.vendor: TOSHIBA ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1786890 Title: AR3012 Bluetooth Status in linux package in Ubuntu: Confirmed Bug description: Qualcomm Atheros AR3012, sometimes can't work ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-30-generic 4.15.0-30.32 ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18 Uname: Linux 4.15.0-30-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rafael 1660 F pulseaudio CurrentDesktop: communitheme:ubuntu:GNOME Date: Mon Aug 13 22:26:37 2018 InstallationDate: Installed on 2018-05-09 (96 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: TOSHIBA Satellite L845 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic root=UUID=947b919c-6edd-4dc8-8592-b3a5cc7a25c4 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-30-generic N/A linux-backports-modules-4.15.0-30-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/27/2012 dmi.bios.vendor: Insyde Corp. dmi.bios.version: 6.50 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Type2 - Board Product Name1 dmi.board.vendor: Type2 - Board Vendor Name1 dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis Manufacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvr6.50:bd12/27/2012:svnTOSHIBA:pnSatelliteL845:pvrPSK8GM-025TM4:rvnType2-BoardVendorName1:rnType2-BoardProductName1:rvrType2-BoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion: dmi.product.family: Type1Family dmi.product.name: Satellite L845 dmi.product.version: PSK8GM-025TM4 dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786890/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1785560] Re: package linux-headers-4.15.0-24-generic 4.15.0-24.26 failed to install/upgrade: installed linux-headers-4.15.0-24-generic package post-installation script subproces
I uninstall Virtualbox and run command sudo apt autoremove after that my problem was solved ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1785560 Title: package linux-headers-4.15.0-24-generic 4.15.0-24.26 failed to install/upgrade: installed linux-headers-4.15.0-24-generic package post-installation script subprocess returned error exit status 1 Status in linux package in Ubuntu: Invalid Bug description: Error while update ProblemType: Package DistroRelease: Ubuntu 18.04 Package: linux-headers-4.15.0-24-generic 4.15.0-24.26 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 NonfreeKernelModules: kpatch_livepatch_Ubuntu_4_15_0_23_25_generic_40 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: sphinx 1801 F...m pulseaudio /dev/snd/controlC0: sphinx 1801 F pulseaudio Date: Tue Jul 31 15:00:50 2018 ErrorMessage: installed linux-headers-4.15.0-24-generic package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2018-06-12 (54 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 09da:9033 A4Tech Co., Ltd. X-718BK Optical Mouse Bus 001 Device 003: ID 09da:fa10 A4Tech Co., Ltd. Bus 001 Device 002: ID 0529:0001 Aladdin Knowledge Systems HASP copy protection dongle Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: MSI MS-7A70 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic root=UUID=5350e0d0-7d27-4150-b938-2af8b6b95a1c ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.02-2ubuntu8.2 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux Title: package linux-headers-4.15.0-24-generic 4.15.0-24.26 failed to install/upgrade: installed linux-headers-4.15.0-24-generic package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/06/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.30 dmi.board.asset.tag: Default string dmi.board.name: B250M PRO-VDH (MS-7A70) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.30:bd04/06/2017:svnMSI:pnMS-7A70:pvr2.0:rvnMSI:rnB250MPRO-VDH(MS-7A70):rvr2.0:cvnMSI:ct3:cvr2.0: dmi.product.family: Default string dmi.product.name: MS-7A70 dmi.product.version: 2.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1785560/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1699772] Re: linux-image-4.13.0-12-generic, linux-image-4.10.0-24-generic, linux-image-4.8.0-56-generic, linux-image-4.4.0-81-generic, linux-image-3.13.0-121-generic | Regressio
Is there any chance to have this fixed in Ubuntu 18.04 earlier than 20.04 is released ? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1699772 Title: linux-image-4.13.0-12-generic, linux-image-4.10.0-24-generic, linux- image-4.8.0-56-generic, linux-image-4.4.0-81-generic, linux- image-3.13.0-121-generic | Regression: many user-space apps crashing Status in LibreOffice: Won't Fix Status in linux package in Ubuntu: Incomplete Status in linux source package in Xenial: Incomplete Status in linux source package in Artful: Won't Fix Status in linux source package in Bionic: Incomplete Status in linux package in Debian: Fix Released Bug description: Distribution: Ubuntu 16.04 x64 (Flavour: KDE Neon User Edition 5.10) linux-image-4.4.0-81-generic appears to contain a regression, probably related to the CVE-2017-1000364 fix backport / patch. Using this kernel, the Oracle Java browser plugin always crashes during stack-related actions on initialization. This means, the plugin completely stopped working. It works perfectly fine in linux-image-4.4.0-79-generic (vurlerable to CVE-2017-1000364) as well as linux-image-4.11.6-041106-generic, which also contains a fix for CVE-2017-1000364. uname -a: > Linux Zweiblum 4.4.0-81-generic #104-Ubuntu SMP Wed Jun 14 08:17:06 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux I tested Oracle Java 1.8 u131 as well as 1.6 u64 in Firefox 51.0.1 as well as Iceweasel / Firefox/3.5.16 in a chroot. Using linux-image-4.4.0-81-generic it crashes in all combinations while with both other kernels it works. I was not able to obtain any detailed crash information from Firefox 51.0.1, but Iceweasel 3.5.16 crashed completely, allowing me to obtain a stack trace which shows the relation to stack operations performed by the plugin, even without proper debug symbols: > (gdb) bt full > #0 0x7fa06d805307 in _expand_stack_to(unsigned char*) () from /opt/java-8-oracle/jre/lib/amd64/server/libjvm.so > No symbol table info available. > #1 0x7fa06d8053ae in os::Linux::manually_expand_stack(JavaThread*, unsigned char*) () >from /opt/java-8-oracle/jre/lib/amd64/server/libjvm.so > No symbol table info available. > #2 0x7fa06d80cf0b in JVM_handle_linux_signal () from /opt/java-8-oracle/jre/lib/amd64/server/libjvm.so > No symbol table info available. > #3 0x7fa06d802e13 in signalHandler(int, siginfo*, void*) () from /opt/java-8-oracle/jre/lib/amd64/server/libjvm.so > No symbol table info available. > #4 I first assumed a bug in the Java plugin, but it works fine in Linux 4.11.6. The crash will be triggered by any applet, for example the test applet at: * https://java.com/en/download/installed8.jsp I'm running the Ubuntu 16.04 based KDE Neon distribution which somehow apparently does not allow me to use apport to report this bug: > $ LANG= apport-cli linux-image-4.4.0-81-generic > > *** Collecting problem information > > The collected information can be sent to the developers to improve the > application. This might take a few minutes. > . > > *** Problem in linux-image-4.4.0-81-generic > > The problem cannot be reported: > > This is not an official KDE package. Please remove any third party package and try again. If someone can tell me how to get apport working for this package, I can use it to collect additional information, but (unfortunately?) the problem should be fairly easy to reproduce... To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1699772/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1777021] Re: Xorg freeze after wakeup from hibernate
[Expired for xorg-server (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg-server (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1777021 Title: Xorg freeze after wakeup from hibernate Status in linux package in Ubuntu: Expired Status in xorg-server package in Ubuntu: Expired Bug description: Happens mostly after wakeup from hibernate ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-43.48~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-43-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Jun 15 03:21:59 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.13.0-43-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a week GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Within the last week or two GraphicsCard: Intel Corporation Device [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:837f] Subsystem: Hewlett-Packard Company Device [103c:8380] InstallationDate: Installed on 2018-02-13 (121 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: HP HP ProBook 470 G5 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-43-generic.efi.signed root=UUID=0f2b268a-ea3c-40bf-a329-13b1447b ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/17/2017 dmi.bios.vendor: HP dmi.bios.version: Q85 Ver. 01.01.07 dmi.board.name: 837F dmi.board.vendor: HP dmi.board.version: KBC Version 02.21.00 dmi.chassis.asset.tag: 5CD7497QSD dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrQ85Ver.01.01.07:bd10/17/2017:svnHP:pnHPProBook470G5:pvr:rvnHP:rn837F:rvrKBCVersion02.21.00:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP ProBook dmi.product.name: HP ProBook 470 G5 dmi.sys.vendor: HP version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Fri Jun 15 03:21:12 2018 xserver.configfile: default xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) NOUVEAU(G0): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.5-0ubuntu2~16.04.1 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777021/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1777021] Re: Xorg freeze after wakeup from hibernate
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1777021 Title: Xorg freeze after wakeup from hibernate Status in linux package in Ubuntu: Expired Status in xorg-server package in Ubuntu: Expired Bug description: Happens mostly after wakeup from hibernate ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-43.48~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-43-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Jun 15 03:21:59 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.13.0-43-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a week GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Within the last week or two GraphicsCard: Intel Corporation Device [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:837f] Subsystem: Hewlett-Packard Company Device [103c:8380] InstallationDate: Installed on 2018-02-13 (121 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: HP HP ProBook 470 G5 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-43-generic.efi.signed root=UUID=0f2b268a-ea3c-40bf-a329-13b1447b ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/17/2017 dmi.bios.vendor: HP dmi.bios.version: Q85 Ver. 01.01.07 dmi.board.name: 837F dmi.board.vendor: HP dmi.board.version: KBC Version 02.21.00 dmi.chassis.asset.tag: 5CD7497QSD dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrQ85Ver.01.01.07:bd10/17/2017:svnHP:pnHPProBook470G5:pvr:rvnHP:rn837F:rvrKBCVersion02.21.00:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP ProBook dmi.product.name: HP ProBook 470 G5 dmi.sys.vendor: HP version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Fri Jun 15 03:21:12 2018 xserver.configfile: default xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) NOUVEAU(G0): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.5-0ubuntu2~16.04.1 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777021/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786878] Re: [Regression] kernel crashdump fails on arm64
** Changed in: linux (Ubuntu) Status: Incomplete => In Progress ** Changed in: linux (Ubuntu Bionic) Status: Incomplete => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1786878 Title: [Regression] kernel crashdump fails on arm64 Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: [Impact] With artful, crashdump worked on the Cavium CRBs, Cavium-based Gigabyte boards and the Qualcomm Amberwing board, but it no longer works with v4.15. While possibly not a regression, crashdump also does not currently work with the HiSilicon D05 board, but does with the proposed fixes. [Test Case] sudo apt install linux-crashdump sudo reboot (needed to add crashkernel= param) echo 1 | sudo tee /proc/sys/kernel/sysrq echo c | sudo tee /proc/sysrq-trigger [Fix] Fixes are currently staged in linux-next: 09ffcb0d718a0 arm64: acpi: fix alignment fault in accessing ACPI 20d12cf990618 efi/arm: map UEFI memory map even w/o runtime services enabled 3ea86495aef2f efi/arm: preserve early mapping of UEFI memory map longer for BGRT 5bcd44083a082 drivers: acpi: add dependency of EFI for arm64 50d7ba36b916d arm64: export memblock_reserve()d regions via /proc/iomem [Regression Risk] TBD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786878/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1785687] Re: btrfs send can bypass DAC check with certain capability set
Hello, This is probably not possible to fix -- it was a widely accepted criticism of the POSIX draft capabilities, and Linux implemented capabilities, that it is an impossible task to prevent individual capability grants from 'bleeding' over into privileges that correspond to other capabilities. If you get any traction reporting this issue to upstreams please do report back, but please don't take it too hard if they're not interested in trying to build stronger separation between root's various capabilities. Thanks ** Information type changed from Private Security to Public Security -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1785687 Title: btrfs send can bypass DAC check with certain capability set Status in linux-signed package in Ubuntu: New Bug description: Expected: For btrfs tool with certain capabilities set(cap_fowner, cap_sys_admin), DAC check should not be by-passed when operating on subvol snapshot What happened instead: btrfs tool with certain capability(cap_fowner,cap_sys_admin) set can be used to by-pass DAC check on a snapshot, and gain read access to all files in a snapshot steps to reproduce: as root # dd if=/dev/zero of=/tmp/test.disk bs=1M count=128 # mkfs.btrfs /tmp/test.disk # mkdir -p /mnt/test # mount /tmp/test.disk /mnt/test/ # cd /mnt/test # btrfs subvol create snapshot # echo "this is a secret" > snapshot/1.secret # chmod 600 snapshot/1.secret # btrfs subvol snapshot -r snapshot snapshot-ro # setcap cap_fowner,cap_sys_admin+eip /bin/btrfs as non-root $ cd /mnt/test $ cat snapshot-ro/1.secret cat: snapshot-ro/1.secret: Permission denied $ btrfs send snapshot-ro > /tmp/snap $ strings /tmp/snap this is a secret ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-23-generic 4.15.0-23.25 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Aug 6 11:18:18 2018 InstallationDate: Installed on 2018-05-17 (80 days ago) InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803) SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1785687/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1526155] Re: nvidia-* kernel module failed to build [cc: error: unrecognized command line option ‘-fstack-protector-strong’]
** Also affects: nvidia-graphics-drivers-390 (Ubuntu) Importance: Undecided Status: New ** Changed in: nvidia-graphics-drivers-390 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1526155 Title: nvidia-* kernel module failed to build [cc: error: unrecognized command line option ‘-fstack-protector-strong’] Status in nvidia-graphics-drivers-304-updates package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-340 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-352 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-361 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-375 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-384 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Bug description: I don't know ProblemType: Package DistroRelease: Ubuntu 14.04 Package: nvidia-340 340.96-0ubuntu0.14.04.1 Uname: Linux 4.0.4-040004-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 DKMSKernelVersion: 4.3.2-040302-generic Date: Tue Dec 15 01:29:18 2015 DuplicateSignature: dkms:nvidia-340:340.96-0ubuntu0.14.04.1:cc: error: unrecognized command line option ‘-fstack-protector-strong’ InstallationDate: Installed on 2014-10-15 (425 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageVersion: 340.96-0ubuntu0.14.04.1 RelatedPackageVersions: dpkg 1.17.5ubuntu5.5 apt 1.0.1ubuntu2.10 SourcePackage: nvidia-graphics-drivers-340 Title: nvidia-340 340.96-0ubuntu0.14.04.1: nvidia-340 kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.modprobe.d.nvidia.340.hybrid.conf: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304-updates/+bug/1526155/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786426] Re: nvidia-dkms-390 390.48-0ubuntu3: nvidia kernel module failed to build [cc: error: unrecognized command line option ‘-fstack-protector-strong’]
*** This bug is a duplicate of bug 1526155 *** https://bugs.launchpad.net/bugs/1526155 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1526155, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** Summary changed: - nvidia-dkms-390 390.48-0ubuntu3: nvidia kernel module failed to build + nvidia-dkms-390 390.48-0ubuntu3: nvidia kernel module failed to build [cc: error: unrecognized command line option ‘-fstack-protector-strong’] ** This bug has been marked a duplicate of bug 1526155 nvidia-* kernel module failed to build [cc: error: unrecognized command line option ‘-fstack-protector-strong’] -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1786426 Title: nvidia-dkms-390 390.48-0ubuntu3: nvidia kernel module failed to build [cc: error: unrecognized command line option ‘-fstack-protector- strong’] Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: cant open the gnome ProblemType: Package DistroRelease: Ubuntu 18.04 Package: nvidia-dkms-390 390.48-0ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18 Uname: Linux 4.15.0-30-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 DKMSKernelVersion: 4.15.0-30-generic Date: Fri Aug 10 10:38:34 2018 DuplicateSignature: dkms:nvidia-dkms-390:390.48-0ubuntu3:cc: error: unrecognized command line option ‘-fstack-protector-strong’ InstallationDate: Installed on 2018-07-11 (30 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageVersion: 390.48-0ubuntu3 Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/local/bin/python2.7, Python 2.7.15, unpackaged RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3 SourcePackage: nvidia-graphics-drivers-390 Title: nvidia-dkms-390 390.48-0ubuntu3: nvidia kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1786426/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786878] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1786878 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Changed in: linux (Ubuntu Bionic) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1786878 Title: [Regression] kernel crashdump fails on arm64 Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Bug description: [Impact] With artful, crashdump worked on the Cavium CRBs, Cavium-based Gigabyte boards and the Qualcomm Amberwing board, but it no longer works with v4.15. While possibly not a regression, crashdump also does not currently work with the HiSilicon D05 board, but does with the proposed fixes. [Test Case] sudo apt install linux-crashdump sudo reboot (needed to add crashkernel= param) echo 1 | sudo tee /proc/sys/kernel/sysrq echo c | sudo tee /proc/sysrq-trigger [Fix] Fixes are currently staged in linux-next: 09ffcb0d718a0 arm64: acpi: fix alignment fault in accessing ACPI 20d12cf990618 efi/arm: map UEFI memory map even w/o runtime services enabled 3ea86495aef2f efi/arm: preserve early mapping of UEFI memory map longer for BGRT 5bcd44083a082 drivers: acpi: add dependency of EFI for arm64 50d7ba36b916d arm64: export memblock_reserve()d regions via /proc/iomem [Regression Risk] TBD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786878/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786878] [NEW] [Regression] kernel crashdump fails on arm64
Public bug reported: [Impact] With artful, crashdump worked on the Cavium CRBs, Cavium-based Gigabyte boards and the Qualcomm Amberwing board, but it no longer works with v4.15. While possibly not a regression, crashdump also does not currently work with the HiSilicon D05 board, but does with the proposed fixes. [Test Case] sudo apt install linux-crashdump sudo reboot (needed to add crashkernel= param) echo 1 | sudo tee /proc/sys/kernel/sysrq echo c | sudo tee /proc/sysrq-trigger [Fix] Fixes are currently staged in linux-next: 09ffcb0d718a0 arm64: acpi: fix alignment fault in accessing ACPI 20d12cf990618 efi/arm: map UEFI memory map even w/o runtime services enabled 3ea86495aef2f efi/arm: preserve early mapping of UEFI memory map longer for BGRT 5bcd44083a082 drivers: acpi: add dependency of EFI for arm64 50d7ba36b916d arm64: export memblock_reserve()d regions via /proc/iomem [Regression Risk] TBD ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Affects: linux (Ubuntu Bionic) Importance: Undecided Status: Incomplete ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1786878 Title: [Regression] kernel crashdump fails on arm64 Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Bug description: [Impact] With artful, crashdump worked on the Cavium CRBs, Cavium-based Gigabyte boards and the Qualcomm Amberwing board, but it no longer works with v4.15. While possibly not a regression, crashdump also does not currently work with the HiSilicon D05 board, but does with the proposed fixes. [Test Case] sudo apt install linux-crashdump sudo reboot (needed to add crashkernel= param) echo 1 | sudo tee /proc/sys/kernel/sysrq echo c | sudo tee /proc/sysrq-trigger [Fix] Fixes are currently staged in linux-next: 09ffcb0d718a0 arm64: acpi: fix alignment fault in accessing ACPI 20d12cf990618 efi/arm: map UEFI memory map even w/o runtime services enabled 3ea86495aef2f efi/arm: preserve early mapping of UEFI memory map longer for BGRT 5bcd44083a082 drivers: acpi: add dependency of EFI for arm64 50d7ba36b916d arm64: export memblock_reserve()d regions via /proc/iomem [Regression Risk] TBD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786878/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1784542] Re: Realtek ethernet not functional on 4.15.0-29.31
I've been using https://people.canonical.com/~khfeng/bionic-r8169-backport2/ for a week now, no issue so far. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1784542 Title: Realtek ethernet not functional on 4.15.0-29.31 Status in linux package in Ubuntu: Confirmed Bug description: When using ethernet (Realtek RTL8111/8168/8411 using built-in r8169 driver v2.3LK-NAPI), dhclient stuck at DHCPDISCOVER. When using static IP, nm shows it's connected, but I can't ping anywhere. This issue only shows up in 4.15.0-29.31. I tried the following versions without issue: 1) 4.18.0-041800rc7 2) 4.16.0-041600 3) 4.15.0-23 4) 4.15.0-20 No issue on wifi (Intel 7260 iwlwifi), USB ethernet (Dell D3100 Dock) and USB ethernet (generic adapter using r8152 driver). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-29-generic 4.15.0-29.31 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: daniel 1771 F pulseaudio /dev/snd/controlC0: daniel 1771 F pulseaudio CurrentDesktop: MATE Date: Tue Jul 31 14:42:31 2018 HibernationDevice: RESUME=UUID=efa14060-79a3-4f5d-99a5-9bb5f7e840d6 InstallationDate: Installed on 2018-07-08 (22 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Dell Inc. Inspiron 7537 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-29-generic root=/dev/mapper/ubuntu--mate--vg-root ro ipv6.disable=1 quiet splash i915.enable_psr=0 vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-29-generic N/A linux-backports-modules-4.15.0-29-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/31/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 07PF9F dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA05:bd10/31/2013:svnDellInc.:pnInspiron7537:pvr:rvnDellInc.:rn07PF9F:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.family: Shark Bay ULT dmi.product.name: Inspiron 7537 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784542/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1767711] Re: Nvidia+XFCE: Totem window is see-through during playback, colours washed out
xfce4 (Ubuntu) → Invalid means that Theo believes this bug is not a bug in xfce4. But it is still a bug in another component(s). See that task and others at the top of the page. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1767711 Title: Nvidia+XFCE: Totem window is see-through during playback, colours washed out Status in nvidia-graphics-drivers-390 package in Ubuntu: New Status in totem package in Ubuntu: New Status in xfce4 package in Ubuntu: Invalid Bug description: Since the upgrade to Ubuntu 18.04, the Totem player will show everything behind it during playback, and the colours of the video are washed-out. https://i.imgur.com/0AwJMmf.jpg I did not find 'tranparency' nor 'opacity' setting in the program preferences, and the colour adjudgement settings are pinned to +/-0. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: totem 3.26.0-0ubuntu6 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Apr 28 14:56:29 2018 InstallationDate: Installed on 2016-06-05 (692 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: totem UpgradeStatus: Upgraded to bionic on 2018-04-27 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1767711/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1777338] Re: Linux 4.15.0-23 crashes during the boot process with a "Unable to handle kernel NULL pointer dereference" message
OK, I have tested the provided kernel and it works for me under Xen. Thank you for fixing the bug! I look forward to seeing this in the real releases. [anovak@octagon ~]$ uname -a Linux octagon 4.15.0-31-generic #34~lp1777338 SMP Tue Aug 7 14:57:12 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux On Mon, Aug 13, 2018 at 8:48 AM, Joseph Salisbury wrote: > The hashes are: > > 63d7e9ca7710792e1603953b0ec14337 linux-image- > unsigned-4.15.0-31-generic_4.15.0-31.34~lp1777338_amd64.deb > > 8cca692f07f9edbb56dec15375bc9979 linux- > modules-4.15.0-31-generic_4.15.0-31.34~lp1777338_amd64.deb > > df24a98ec4769f33a9831a5aaeb9f437 linux-modules- > extra-4.15.0-31-generic_4.15.0-31.34~lp1777338_amd64.deb > > -- > You received this bug notification because you are subscribed to the bug > report. > 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: > In Progress > Status in linux source package in Bionic: > In Progress > > Bug description: > 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 -- You 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: In Progress Status in linux source package in Bionic: In Progress Bug description: 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 1767711] Re: Nvidia+XFCE: Totem window is see-through during playback, colours washed out
What does "status: invalid" mean? In XFCE > Settings > Additional Drivers > Additional Drivers, it's currently set to "NVIDIA Corporation GF106M [GeForce GTX 460M] "[x] Using NVIDIA driver metapackage from nvidia-driver-390 (proprietary, tested)". Other options are "[ ] Using NVIDIA bindary driver - version 340.106 from nvidia-340 (proprietary)" and "[ ] Using X.Org server - Nouveau display driver from xserver-xorg-video-nouveau (open source)" Tried to install nvidia-340, but it cocked up and left the system in a bad state. I couldn't even revert to nvidia-driver-390 without doing a lot of "apt --fix-broken install ... dpkg-divert --remove" loops. Installed the nouveau driver, doesn't send output to the primary display, had to plug in a second display. (???) used "xfwm4-tweaks-settings" to make sure Compositing is turned on. Started "totem vapourwave.mp4" and... no transparency. does_not_reproduce NVIDIA website says the latest "long lived" (stable?) version is 390.77 (2018-07-16). https://www.nvidia.com/Download/driverResults.aspx/136120/en-us . It won't let me install it because of the kernel modules already installed, which I can't remove with modprobe nor rmmod because "resource is in use" despite no dependencies and I already stopped X.Org. I'll keep trying. Looking like it's a bad interaction between Totem and the NVIDIA proprietary driver (nvidia-driver-390). Weird that the other video players, even the gstreamer-based ones, don't suffer the same problem. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1767711 Title: Nvidia+XFCE: Totem window is see-through during playback, colours washed out Status in nvidia-graphics-drivers-390 package in Ubuntu: New Status in totem package in Ubuntu: New Status in xfce4 package in Ubuntu: Invalid Bug description: Since the upgrade to Ubuntu 18.04, the Totem player will show everything behind it during playback, and the colours of the video are washed-out. https://i.imgur.com/0AwJMmf.jpg I did not find 'tranparency' nor 'opacity' setting in the program preferences, and the colour adjudgement settings are pinned to +/-0. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: totem 3.26.0-0ubuntu6 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Apr 28 14:56:29 2018 InstallationDate: Installed on 2016-06-05 (692 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: totem UpgradeStatus: Upgraded to bionic on 2018-04-27 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1767711/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1767857] Re: Kernel 4.4.0-122 Breaks qemu-system-x86
I booted from the Xubuntu 18.04.1 Install ISO, installed qemu, copied and modified some files to adjust for user name and permissions, and ran my Windows 10 qemu-system-x86 script - same result (black screen displays and qemu-system-x86 runs at 100% cpu indefinitely). Totally black screen immediately - no bios flashes. Therefore, it appears to me that the problem is not my Xubuntu software setup. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1767857 Title: Kernel 4.4.0-122 Breaks qemu-system-x86 Status in linux package in Ubuntu: Confirmed Status in qemu package in Ubuntu: Incomplete Bug description: Fully updated xubuntu 16.04 running kernel 4.4.0-122 breaks qemu- system-x86: black screen displays and qemu-system-x86 runs at 100% cpu indefinitely. Boot the same system with kernel 4.4.0-119 and qemu- system-x86 works fine running a Windows 10 VM. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: qemu-system-x86 1:2.5+dfsg-5ubuntu10.25 ProcVersionSignature: Ubuntu 4.4.0-122.146-generic 4.4.117 Uname: Linux 4.4.0-122-generic i686 ApportVersion: 2.20.1-0ubuntu2.16 Architecture: i386 CurrentDesktop: XFCE Date: Sun Apr 29 15:58:25 2018 InstallationDate: Installed on 2014-04-29 (1460 days ago) InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140416.2) KvmCmdLine: COMMAND STAT EUID RUID PID PPID %CPU COMMAND kvm-irqfd-clean S< 0 0 394 2 0.0 [kvm-irqfd-clean] MachineType: Dell Inc. Inspiron 518 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-122-generic root=UUID=7cffb293-c044-4b2c-8343-dc50fd16db97 ro --verbose nosplash nmi_watchdog=0 SourcePackage: qemu UpgradeStatus: Upgraded to xenial on 2016-08-10 (627 days ago) dmi.bios.date: 03/30/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.8 dmi.board.name: 0K068D dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: OEM dmi.modalias: dmi:bvnDellInc.:bvr1.0.8:bd03/30/2009:svnDellInc.:pnInspiron518:pvr00:rvnDellInc.:rn0K068D:rvrA00:cvnDellInc.:ct3:cvrOEM: dmi.product.name: Inspiron 518 dmi.product.version: 00 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1767857/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1767711] Re: Nvidia+XFCE: Totem window is see-through during playback, colours washed out
Looks like the next step would be to test with an older NVIDIA driver version from the Ubuntu repository, and maybe with the slightly newer version 390.77 from the NVIDIA website also. ** Changed in: xfce4 (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1767711 Title: Nvidia+XFCE: Totem window is see-through during playback, colours washed out Status in nvidia-graphics-drivers-390 package in Ubuntu: New Status in totem package in Ubuntu: New Status in xfce4 package in Ubuntu: Invalid Bug description: Since the upgrade to Ubuntu 18.04, the Totem player will show everything behind it during playback, and the colours of the video are washed-out. https://i.imgur.com/0AwJMmf.jpg I did not find 'tranparency' nor 'opacity' setting in the program preferences, and the colour adjudgement settings are pinned to +/-0. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: totem 3.26.0-0ubuntu6 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Apr 28 14:56:29 2018 InstallationDate: Installed on 2016-06-05 (692 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: totem UpgradeStatus: Upgraded to bionic on 2018-04-27 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1767711/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786848] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1786848 Title: package linux-headers-4.4.0-119 4.4.0-119.143 failed to install/upgrade: package linux-headers-4.4.0-119 is not ready for configuration cannot configure (current status 'half-installed') Status in linux package in Ubuntu: Confirmed Bug description: Bug registered during partial update ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-headers-4.4.0-119 4.4.0-119.143 ProcVersionSignature: Ubuntu 4.4.0-131.157-generic 4.4.134 Uname: Linux 4.4.0-131-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: peter 2280 F pulseaudio Date: Mon Aug 13 21:19:54 2018 DuplicateSignature: package:linux-headers-4.4.0-119:4.4.0-119.143 Processing triggers for ureadahead (0.100.0-19) ... ureadahead will be reprofiled on next reboot dpkg: error processing package linux-headers-4.4.0-119 (--configure): package linux-headers-4.4.0-119 is not ready for configuration ErrorMessage: package linux-headers-4.4.0-119 is not ready for configuration cannot configure (current status 'half-installed') HibernationDevice: RESUME=UUID=3ecf3ed3-b50a-49c6-839f-f749cac4636d InstallationDate: Installed on 2014-09-12 (1431 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) Lsusb: Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 03f0:231d Hewlett-Packard Broadcom 2070 Bluetooth Combo Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Hewlett-Packard HP EliteBook 8440p PackageArchitecture: all PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-131-generic root=UUID=fdb4935c-8375-4ff5-8861-91f2c4b872d4 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.18 SourcePackage: linux Title: package linux-headers-4.4.0-119 4.4.0-119.143 failed to install/upgrade: package linux-headers-4.4.0-119 is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/02/2010 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68CCU Ver. F.0B dmi.board.name: 172A dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 30.2C dmi.chassis.asset.tag: CZC0317WTV dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68CCUVer.F.0B:bd06/02/2010:svnHewlett-Packard:pnHPEliteBook8440p:pvr:rvnHewlett-Packard:rn172A:rvrKBCVersion30.2C:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook 8440p dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786848/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786664] Re: wifi (mwifiex_pcie) stops working undeterministically in 18.04 on Surface Pro 3
I have installed the v4.18.rc8-generic kernel (uname: 4.18.0-041800rc8-generic) Unfortunately the problem remains. Although the driver reports itself as the exact same version as in the Ubuntu kernel (info: MWIFIEX VERSION: mwifiex 1.0 (15.68.7.p154) it produced a slightly different dmesg output which might be of help here. I do not know how to set tags here, I would ask you to set 'kernel-bug-exists-upstream'. ** Attachment added: "dmesg.4.18.generic.crop.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786664/+attachment/5174903/+files/dmesg.4.18.generic.crop.log ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1786664 Title: wifi (mwifiex_pcie) stops working undeterministically in 18.04 on Surface Pro 3 Status in linux package in Ubuntu: Confirmed Bug description: I am using the mainline kernel on Ubuntu 18.04 on a Surface Pro 3. After a varying amount of time the wifi connection is gone. The driver does not seem to respond anymore to any action invoked by the gnome ui. My only known workaround for this is to reboot. In this state the shutdown process may take several minutes. Version signature: Ubuntu 4.15.0-30.32-generic 4.15.18 lsb_release: Description: Ubuntu 18.04.1 LTS Release: 18.04 logs as attachments are following To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786664/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1767711] Re: Nvidia+XFCE: Totem window is see-through during playback, colours washed out
I didn't try 'marco' because I didn't know what that is. Installing it now. totem used with 'marco' and 'compton' are not washed out, but strangely transparent. See attached image for 'marco' -- compton is the same just no messages on stderr from compton. ** Attachment added: "totem.with.marco.png" https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1767711/+attachment/5174902/+files/totem.with.marco.png -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1767711 Title: Nvidia+XFCE: Totem window is see-through during playback, colours washed out Status in nvidia-graphics-drivers-390 package in Ubuntu: New Status in totem package in Ubuntu: New Status in xfce4 package in Ubuntu: Incomplete Bug description: Since the upgrade to Ubuntu 18.04, the Totem player will show everything behind it during playback, and the colours of the video are washed-out. https://i.imgur.com/0AwJMmf.jpg I did not find 'tranparency' nor 'opacity' setting in the program preferences, and the colour adjudgement settings are pinned to +/-0. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: totem 3.26.0-0ubuntu6 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Apr 28 14:56:29 2018 InstallationDate: Installed on 2016-06-05 (692 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: totem UpgradeStatus: Upgraded to bionic on 2018-04-27 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1767711/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786848] Re: package linux-headers-4.4.0-119 4.4.0-119.143 failed to install/upgrade: package linux-headers-4.4.0-119 is not ready for configuration cannot configure (current st
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1786848 Title: package linux-headers-4.4.0-119 4.4.0-119.143 failed to install/upgrade: package linux-headers-4.4.0-119 is not ready for configuration cannot configure (current status 'half-installed') Status in linux package in Ubuntu: New Bug description: Bug registered during partial update ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-headers-4.4.0-119 4.4.0-119.143 ProcVersionSignature: Ubuntu 4.4.0-131.157-generic 4.4.134 Uname: Linux 4.4.0-131-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: peter 2280 F pulseaudio Date: Mon Aug 13 21:19:54 2018 DuplicateSignature: package:linux-headers-4.4.0-119:4.4.0-119.143 Processing triggers for ureadahead (0.100.0-19) ... ureadahead will be reprofiled on next reboot dpkg: error processing package linux-headers-4.4.0-119 (--configure): package linux-headers-4.4.0-119 is not ready for configuration ErrorMessage: package linux-headers-4.4.0-119 is not ready for configuration cannot configure (current status 'half-installed') HibernationDevice: RESUME=UUID=3ecf3ed3-b50a-49c6-839f-f749cac4636d InstallationDate: Installed on 2014-09-12 (1431 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) Lsusb: Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 03f0:231d Hewlett-Packard Broadcom 2070 Bluetooth Combo Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Hewlett-Packard HP EliteBook 8440p PackageArchitecture: all PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-131-generic root=UUID=fdb4935c-8375-4ff5-8861-91f2c4b872d4 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.18 SourcePackage: linux Title: package linux-headers-4.4.0-119 4.4.0-119.143 failed to install/upgrade: package linux-headers-4.4.0-119 is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/02/2010 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68CCU Ver. F.0B dmi.board.name: 172A dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 30.2C dmi.chassis.asset.tag: CZC0317WTV dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68CCUVer.F.0B:bd06/02/2010:svnHewlett-Packard:pnHPEliteBook8440p:pvr:rvnHewlett-Packard:rn172A:rvrKBCVersion30.2C:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook 8440p dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786848/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1784291] Re: linux-kvm: 4.15.0-1018.18 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1784291 Title: linux-kvm: 4.15.0-1018.18 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1784281 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1784291/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1784285] Re: linux-aws: 4.15.0-1018.18 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => Fix Released -- 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/1784285 Title: linux-aws: 4.15.0-1018.18 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-release-to-beta series: Confirmed Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Confirmed Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1784281 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1784285/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786848] [NEW] package linux-headers-4.4.0-119 4.4.0-119.143 failed to install/upgrade: package linux-headers-4.4.0-119 is not ready for configuration cannot configure (current
Public bug reported: Bug registered during partial update ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-headers-4.4.0-119 4.4.0-119.143 ProcVersionSignature: Ubuntu 4.4.0-131.157-generic 4.4.134 Uname: Linux 4.4.0-131-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: peter 2280 F pulseaudio Date: Mon Aug 13 21:19:54 2018 DuplicateSignature: package:linux-headers-4.4.0-119:4.4.0-119.143 Processing triggers for ureadahead (0.100.0-19) ... ureadahead will be reprofiled on next reboot dpkg: error processing package linux-headers-4.4.0-119 (--configure): package linux-headers-4.4.0-119 is not ready for configuration ErrorMessage: package linux-headers-4.4.0-119 is not ready for configuration cannot configure (current status 'half-installed') HibernationDevice: RESUME=UUID=3ecf3ed3-b50a-49c6-839f-f749cac4636d InstallationDate: Installed on 2014-09-12 (1431 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) Lsusb: Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 03f0:231d Hewlett-Packard Broadcom 2070 Bluetooth Combo Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Hewlett-Packard HP EliteBook 8440p PackageArchitecture: all PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-131-generic root=UUID=fdb4935c-8375-4ff5-8861-91f2c4b872d4 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.18 SourcePackage: linux Title: package linux-headers-4.4.0-119 4.4.0-119.143 failed to install/upgrade: package linux-headers-4.4.0-119 is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/02/2010 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68CCU Ver. F.0B dmi.board.name: 172A dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 30.2C dmi.chassis.asset.tag: CZC0317WTV dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68CCUVer.F.0B:bd06/02/2010:svnHewlett-Packard:pnHPEliteBook8440p:pvr:rvnHewlett-Packard:rn172A:rvrKBCVersion30.2C:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook 8440p dmi.sys.vendor: Hewlett-Packard ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1786848 Title: package linux-headers-4.4.0-119 4.4.0-119.143 failed to install/upgrade: package linux-headers-4.4.0-119 is not ready for configuration cannot configure (current status 'half-installed') Status in linux package in Ubuntu: New Bug description: Bug registered during partial update ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-headers-4.4.0-119 4.4.0-119.143 ProcVersionSignature: Ubuntu 4.4.0-131.157-generic 4.4.134 Uname: Linux 4.4.0-131-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: peter 2280 F pulseaudio Date: Mon Aug 13 21:19:54 2018 DuplicateSignature: package:linux-headers-4.4.0-119:4.4.0-119.143 Processing triggers for ureadahead (0.100.0-19) ... ureadahead will be reprofiled on next reboot dpkg: error processing package linux-headers-4.4.0-119 (--configure): package linux-headers-4.4.0-119 is not ready for configuration ErrorMessage: package linux-headers-4.4.0-119 is not ready for configuration cannot configure (current status 'half-installed') HibernationDevice: RESUME=UUID=3ecf3ed3-b50a-49c6-839f-f749cac4636d InstallationDate: Installed on 2014-09-12 (1431 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) Lsusb: Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 03f0:231d Hewlett-Packard Broadcom 2070 Bluetooth Combo Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Hewlett-Packard HP EliteBook 8440p PackageArchitecture: all PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0
[Kernel-packages] [Bug 1784292] Re: linux-azure: 4.15.0-1020.20~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1784292 Title: linux-azure: 4.15.0-1020.20~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-release-to-beta series: Confirmed Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Confirmed Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1784281 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1784292/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1779817] Re: r8169 no internet after suspending
Can we cherry-pick https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git/commit/?id=7c53a722459c1d6ffb0f5b2058c06ca8980b8600 for bionic? On 10 August 2018 at 12:49, Heiner Kallweit <1779...@bugs.launchpad.net> wrote: > @Steve, there's some resistance amongst kernel maintainers against > additional module parameters. Each new parameter increases complexity and > makes maintenance harder. > Most likely it would result in a NAK when trying to fix an issue with one > broken exotic (sorry..) system in the kernel, especially if a userspace > workaround is available (disabling MSI via sysfs for the network device). > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1779817 > > Title: > r8169 no internet after suspending > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/ > 1779817/+subscriptions > -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1779817 Title: r8169 no internet after suspending Status in linux package in Ubuntu: Confirmed Bug description: When my computer wakes up from suspending, there's no internet. Unplugging and replugging cable doesn't work, restarting network service doesn't work also. Only after restarting the computer, internet comes back. It only started happening after I freshly installed Ubuntu Budgie (18.04) and did all the system updates. Before I was using Ubuntu with Unity (16.04) and there was no problems with my internet. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-24-generic 4.15.0-24.26 ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 Uname: Linux 4.15.0-24-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: minihydra 2085 F pulseaudio /dev/snd/controlC0: minihydra 2085 F pulseaudio /dev/snd/controlC1: minihydra 2085 F pulseaudio CurrentDesktop: Budgie:GNOME Date: Tue Jul 3 10:13:19 2018 HibernationDevice: RESUME=UUID=3747bab8-c258-4600-bc24-5d1f56a642dd InstallationDate: Installed on 2018-07-02 (1 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IwConfig: enp2s0no wireless extensions. lono wireless extensions. MachineType: System manufacturer System Product Name ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic root=UUID=a5ceb36e-76f7-4bd4-a37b-0b91b995c635 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-24-generic N/A linux-backports-modules-4.15.0-24-generic N/A linux-firmware 1.173.1 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/28/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2103 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4A77T 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.:bvr2103:bd06/28/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A77T:rvrRevX.0x: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/1779817/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786752] Re: Reference counter issue in 4.15 (nf_xfrm_me_harder / dst_release)
The issue still is visible with the latest mainline kernel; see attached. ** Attachment added: "dmesg from 4.18" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786752/+attachment/5174879/+files/dmesg_4.18.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Tags added: kernel-bug-exists-upstream -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1786752 Title: Reference counter issue in 4.15 (nf_xfrm_me_harder / dst_release) Status in linux package in Ubuntu: Confirmed Bug description: Since upgrading from 14.04 to 18.04, we see very frequent warnings about negative refcnts in dst_release: [ 3117.882227] WARNING: CPU: 6 PID: 0 at /build/linux-I4R9hO/linux-4.15.0/include/net/dst.h:256 nf_xfrm_me_harder+0x127/0x140 [nf_nat] [ 3117.882229] Modules linked in: xt_policy cls_u32 sch_sfq ip_vti ip_tunnel authenc echainiv xfrm6_mode_tunnel xfrm4_mode_tunnel xfrm4_tunnel tunnel4 ipcomp xfrm_ipcomp esp4 ah4 af_key nfnetlink_queue nfnetlink_log sch_htb xt_TPROXY xt_multiport veth nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo br_netfilter bridge overlay macvlan 8021q garp mrp stp llc bonding algif_skcipher af_alg xt_hl ip6t_rt nf_conntrack_ipv6 nf_defrag_ipv6 ip6t_REJECT nf_reject_ipv6 xt_nat ipt_MASQUERADE nf_nat_masquerade_ipv4 dm_crypt iptable_nat nf_nat_ipv4 xt_DSCP xt_dscp xt_mark iptable_mangle xt_limit xt_tcpudp xt_addrtype intel_rapl sb_edac x86_pkg_temp_thermal intel_powerclamp coretemp nf_conntrack_ipv4 nf_defrag_ipv4 kvm_intel xt_conntrack kvm joydev input_leds ipt_REJECT nf_reject_ipv4 ftdi_sio usbserial ipmi_si [ 3117.882265] irqbypass intel_cstate mei_me mei ioatdma acpi_pad intel_rapl_perf shpchp ipmi_devintf ipmi_msghandler acpi_power_meter lpc_ich mac_hid ip6table_filter ip6_tables nf_conntrack_netbios_ns nf_conntrack_broadcast nf_nat_ftp nf_nat nf_conntrack_ftp sch_fq_codel nf_conntrack iptable_filter 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 mgag200 ttm crct10dif_pclmul igb ixgbe crc32_pclmul drm_kms_helper hid_generic ghash_clmulni_intel syscopyarea i2c_algo_bit dca sysfillrect usbhid pcbc sysimgblt fb_sys_fops aesni_intel aes_x86_64 crypto_simd ahci glue_helper ptp hid mxm_wmi cryptd [ 3117.882309] drm libahci megaraid_sas pps_core mdio wmi [ 3117.882315] CPU: 6 PID: 0 Comm: swapper/6 Tainted: GW 4.15.0-30-generic #32-Ubuntu [ 3117.882316] Hardware name: Intel Corporation S2600WT2R/S2600WT2R, BIOS SE5C610.86B.01.01.0022.062820171903 06/28/2017 [ 3117.882319] RIP: 0010:nf_xfrm_me_harder+0x127/0x140 [nf_nat] [ 3117.882320] RSP: 0018:88d77f3839f0 EFLAGS: 00010246 [ 3117.882322] RAX: RBX: 90de4000 RCX: 1924 [ 3117.882323] RDX: RSI: 88d749ae6400 RDI: 88d655e96600 [ 3117.882324] RBP: 88d77f383a68 R08: 88d7493dc000 R09: 0018 [ 3117.882324] R10: 0001 R11: 88e770dedc00 R12: 88d655e96600 [ 3117.882325] R13: 88d77f383ae8 R14: 88d7799ff200 R15: 88d7493dc000 [ 3117.882327] FS: () GS:88d77f38() knlGS: [ 3117.882327] CS: 0010 DS: ES: CR0: 80050033 [ 3117.882328] CR2: ff600400 CR3: 00193de0a002 CR4: 003606e0 [ 3117.882329] DR0: DR1: DR2: [ 3117.882330] DR3: DR6: fffe0ff0 DR7: 0400 [ 3117.882331] Call Trace: [ 3117.882332] [ 3117.882337] ? nf_nat_ipv4_fn+0x15b/0x200 [nf_nat_ipv4] [ 3117.882339] nf_nat_ipv4_out+0xc5/0xe0 [nf_nat_ipv4] [ 3117.882342] iptable_nat_ipv4_out+0x15/0x20 [iptable_nat] [ 3117.882347] nf_hook_slow+0x48/0xc0 [ 3117.882353] ip_output+0xd2/0xe0 [ 3117.882355] ? ip_fragment.constprop.44+0x80/0x80 [ 3117.882357] ip_forward_finish+0x49/0x70 [ 3117.882359] ip_forward+0x366/0x440 [ 3117.882361] ? ip_frag_mem+0x20/0x20 [ 3117.882362] ip_rcv_finish+0x129/0x430 [ 3117.882364] ip_rcv+0x28f/0x3a0 [ 3117.882366] ? inet_del_offload+0x40/0x40 [ 3117.882372] __netif_receive_skb_core+0x432/0xb40 [ 3117.882379] ? handle_edge_irq+0x7c/0x190 [ 3117.882384] ? irq_exit+0x67/0xc0 [ 3117.882391] ? do_IRQ+0x82/0xd0 [ 3117.882393] __netif_receive_skb+0x18/0x60 [ 3117.882395] ? __netif_receive_skb+0x18/0x60 [ 3117.882397] netif_receive_skb_internal+0x37/0xd0 [ 3117.882398] napi_gro_receive+0xc5/0xf0 [ 3117.882407] ixgbe_clean_rx_irq+0x446/0xe30 [ixgbe] [ 3117.882411] ixgbe_poll+0x256/0x710 [ixgbe] [ 3117.882413] ? do_IRQ+0x82/0xd0 [ 3117.882415] net_rx_action+0x140/0x3a0 [ 3117.882418]
[Kernel-packages] [Bug 1783906] Re: Linux 4.15 and onwards fails to initialize some hard drives
I built a test kernel with debug output as requested by upstream. Can
you test this kernel and post your syslog or dmesg output?
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1783906
This kernel should exhibit the bug, but will write to syslog with output like:
***-> Value of spd_limit: N
***-> Value of sstatus: N
***-> Value of spd: N
***-> Value of mask: N
I did a dump_stack in the function, so you should see a new stack trace
as well.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1783906
Title:
Linux 4.15 and onwards fails to initialize some hard drives
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Bionic:
In Progress
Status in linux source package in Cosmic:
In Progress
Bug description:
I have two hard drives, the main hard drive is a TOSHIBA DT01ACA200
the second backup hard drive is a Western Digital WD5003AZEX. I
installed lubuntu 18.04.1 on the Toshiba HDD and it boots just fine,
the issue is with the second hard drive, when installing the WD HDD
wouldn't even come as an option to install, and after boot the WD HDD
still wouldn't come up, this is the dmesg with the stock kernel (4.15)
https://paste.ubuntu.com/p/kpxh94v2SK/
ata6 is the WD HDD that refuses to work. The messages:
[ 302.107650] ata6: SError: { CommWake 10B8B Dispar DevExch }
[ 302.107658] ata6: hard resetting link
[ 307.860291] ata6: link is slow to respond, please be patient (ready=0)
[ 312.120898] ata6: COMRESET failed (errno=-16)
[ 363.445120] INFO: task kworker/u8:5:201 blocked for more than 120 seconds.
[ 363.445131] Not tainted 4.15.0-29-generic #31-Ubuntu
[ 363.445135] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables
this message.
[ 363.445140] kworker/u8:5D0 201 2 0x8000
[ 363.445155] Workqueue: events_unbound async_run_entry_fn
[ 363.445157] Call Trace:
[ 363.445171] __schedule+0x291/0x8a0
[ 363.445177] schedule+0x2c/0x80
[ 363.445182] ata_port_wait_eh+0x7c/0xf0
[ 363.445186] ? wait_woken+0x80/0x80
[ 363.445189] ata_port_probe+0x28/0x40
[ 363.445192] async_port_probe+0x2e/0x52
[ 363.445196] async_run_entry_fn+0x3c/0x150
[ 363.445199] process_one_work+0x1de/0x410
[ 363.445203] worker_thread+0x32/0x410
[ 363.445207] kthread+0x121/0x140
[ 363.445210] ? process_one_work+0x410/0x410
[ 363.445214] ? kthread_create_worker_on_cpu+0x70/0x70
[ 363.445218] ret_from_fork+0x22/0x40
Repeat constantly. Also when I try to turn off the computer, the
computer seem to freeze, the lights of the keyboard and mouse turn off
and the computer just stay on.
I tried Tiny Core 9.0 which has linux 4.14.10, and i didn't had this
issue, i also installed linux 4.14 on this lubuntu 18.04 using Ukuu
Kernel Update Utility. And with this kernel version, or any previous
version the WD HDD does work again. Here's a dmesg of lubuntu 18.04
with linux 4.14 and the WD HDD finally coming up at the end:
https://paste.ubuntu.com/p/Gd3cGFbjTJ/
Also tried with with linux 4.17 but the WD HDD would also refuse to
work on this version. Here's another dmesg with this version:
https://paste.ubuntu.com/p/PmNn96vZZv/
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-29-generic 4.15.0-29.31
ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
Uname: Linux 4.15.0-29-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version
k4.15.0-29-generic.
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: testtest756 F pulseaudio
/dev/snd/controlC1: testtest756 F pulseaudio
Card0.Amixer.info:
Card hw:0 'NVidia_1'/'HDA NVidia at 0xfe02 irq 22'
Mixer name : 'Realtek ALC1200'
Components : 'HDA:10ec0888,10ec,00100101
HDA:10de0002,10de0101,0010'
Controls : 56
Simple ctrls : 21
Card1.Amixer.info:
Card hw:1 'NVidia'/'HDA NVidia at 0xfcffc000 irq 16'
Mixer name : 'Nvidia GPU 42 HDMI/DP'
Components : 'HDA:10de0042,38422651,00100100'
Controls : 21
Simple ctrls : 3
CurrentDesktop: LXDE
Date: Thu Jul 26 17:10:58 2018
HibernationDevice: RESUME=UUID=17e70869-516d-4b63-b900-e92e3c4b73b6
InstallationDate: Installed on 2018-07-26 (0 days ago)
InstallationMedia: Lubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64
(20180725)
MachineType: 113 1
ProcFB: 0 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic
root=UUID=71cf0a32-7827-49be-a2c0-cd50a72c26a1 ro quiet splash vt.handoff=1
RelatedPackageVersions:
linux-restricted-modules-4.15.0-29-generic N/A
linux-backports-modules-4.15.0-29-generic N/A
linux-firmware 1.173.1
RfKill:
0: phy0: Wireless
[Kernel-packages] [Bug 1752961] Re: With kernel 4.13 btrfs scans for devices before all devices have been discovered
The latest test kernel is for commit
362f6729cbb1d6bbab59e069f19441b0622ff7ec
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1752961
Title:
With kernel 4.13 btrfs scans for devices before all devices have been
discovered
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Artful:
Won't Fix
Status in linux source package in Bionic:
In Progress
Status in linux source package in Cosmic:
In Progress
Bug description:
See attached dmesg outputs for booting kernels 4.11.x (working) and
4.13.x (not working).
dmesg-4.11.0-14-good.txt shows the dmesg output when booting kernel 4.11.x.
btrfs scans for devices after all 4 (sda, sdb, sdc, sdd) of the devices have
been discovered by the kernel. The btrfs RAID1 filesystem mounts, and
everything is good.
dmesg-4.13.0-36-fail.txt shows the dmesg output when booting kernel 4.13.x.
btrfs scans for devices after only 2 (sda, sdb) of the devices have been
discovered by the kernel. The btrfs RAID1 filesystem fails to mount ("failed
to read the system array: -5"). The remaining 2 devices (sdc, sdd) are
discovered by the kernel immediately afterward. At the end of the log, I run
`btrfs device scan` and mount the filesystem manually.
Hardware:
HP ProLiant MicroServer Gen8
4x WDC WD20EFRX
---
AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code
2: ls: cannot access '/dev/snd/': No such file or directory
AplayDevices: aplay: device_list:270: no soundcards found...
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
ArecordDevices: arecord: device_list:270: no soundcards found...
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2015-10-15 (933 days ago)
InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
MachineType: HP ProLiant MicroServer Gen8
Package: linux (not installed)
ProcEnviron:
TERM=linux
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-20-generic
root=UUID=d976ab07-8377-46dd-ac6c-f5f7312a8305 ro rootflags=subvol=@
rootdelay=10
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
Tags: bionic apport-hook-error
Uname: Linux 4.15.0-20-generic x86_64
UnreportableReason: This report is about a package that is not installed.
UpgradeStatus: Upgraded to bionic on 2018-05-05 (0 days ago)
UserGroups:
_MarkForUpload: True
dmi.bios.date: 07/16/2015
dmi.bios.vendor: HP
dmi.bios.version: J06
dmi.chassis.type: 7
dmi.chassis.vendor: HP
dmi.modalias:
dmi:bvnHP:bvrJ06:bd07/16/2015:svnHP:pnProLiantMicroServerGen8:pvr:cvnHP:ct7:cvr:
dmi.product.family: ProLiant
dmi.product.name: ProLiant MicroServer Gen8
dmi.sys.vendor: HP
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752961/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786713] Re: MODULE_SOFTDEP for crc32c is not working
btw making initramfs is the problem, not the kernel itself. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1786713 Title: MODULE_SOFTDEP for crc32c is not working Status in linux package in Ubuntu: Incomplete Bug description: I have a kernel config with Ext4, for which softdep is not working. See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1778265 Ubuntu 18.04. Kernel 4.17.18 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786713/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1685794] Re: Boot delayed for about 90 seconds until 'random: crng init done'
haveged not solve for me. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1685794 Title: Boot delayed for about 90 seconds until 'random: crng init done' Status in linux package in Ubuntu: Confirmed Bug description: Shortened dmesg output, notice the unnaturally long delay before crng init finishes: [8.533630] Bluetooth: hci0: Intel Bluetooth firmware patch completed and activated [8.542239] input: HDA Intel PCH Mic as /devices/pci:00/:00:1b.0/sound/card1/input18 [8.542313] input: HDA Intel PCH Line as /devices/pci:00/:00:1b.0/sound/card1/input19 [8.542382] input: HDA Intel PCH Dock Line Out as /devices/pci:00/:00:1b.0/sound/card1/input20 [8.542449] input: HDA Intel PCH Headphone as /devices/pci:00/:00:1b.0/sound/card1/input21 [8.544240] cdc_ether 2-6:2.0 usb0: register 'cdc_ether' at usb-:00:14.0-6, CDC Ethernet Device, 02:1e:10:1f:00:00 [8.544271] usbcore: registered new interface driver cdc_ether [8.637660] ieee80211 phy0: Selected rate control algorithm 'iwl-mvm-rs' [8.654022] input: HP WMI hotkeys as /devices/virtual/input/input22 [8.688226] cdc_ether 2-6:2.0 enp0s20u6c2: renamed from usb0 [8.713288] iwlwifi :02:00.0 wlo1: renamed from wlan0 [9.804308] input: ST LIS3LV02DL Accelerometer as /devices/platform/lis3lv02d/input/input23 [ 98.327857] random: crng init done [ 98.330072] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 98.330073] Bluetooth: BNEP filters: protocol multicast [ 98.330077] Bluetooth: BNEP socket layer initialized [ 98.443281] kauditd_printk_skb: 90 callbacks suppressed [ 98.492927] IPv6: ADDRCONF(NETDEV_UP): enp0s25: link is not ready [ 98.681030] IPv6: ADDRCONF(NETDEV_UP): enp0s25: link is not ready [ 98.685672] IPv6: ADDRCONF(NETDEV_UP): enp0s20u6c2: link is not ready [ 98.685789] cdc_ether 2-6:2.0 enp0s20u6c2: kevent 12 may have been dropped [ 98.688384] IPv6: ADDRCONF(NETDEV_UP): wlo1: link is not ready [ 98.690915] iwlwifi :02:00.0: L1 Enabled - LTR Enabled ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-19-generic 4.10.0-19.21 [modified: boot/vmlinuz-4.10.0-19-generic] ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity:Unity7 Date: Mon Apr 24 14:58:33 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2017-04-18 (5 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: Hewlett-Packard HP EliteBook 840 G1 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic.efi.signed root=UUID=9fb9fc1d-15a4-4e98-a2ae-bf572e0900d5 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.10.0-19-generic N/A linux-backports-modules-4.10.0-19-generic N/A linux-firmware 1.164 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/23/2016 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: L71 Ver. 01.37 dmi.board.name: 198F dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 15.59 dmi.chassis.asset.tag: USH452L0B1 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrL71Ver.01.37:bd05/23/2016:svnHewlett-Packard:pnHPEliteBook840G1:pvrA3009DD10203:rvnHewlett-Packard:rn198F:rvrKBCVersion15.59:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook 840 G1 dmi.product.version: A3009DD10203 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1685794/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1784665] Re: mkfs.ext4 over /dev/bcache0 hangs
4.14 Final: OK 4.15-rc1:OK I started a further bisect: 4.15-rc9:FAIL 4.15-rc5:OK 4.15-rc7:FAIL 4.15-rc6:OK So, it appears something between rc6 (last known good) and rc7 (FAIL) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1784665 Title: mkfs.ext4 over /dev/bcache0 hangs Status in linux package in Ubuntu: Confirmed Status in linux source package in Cosmic: Confirmed Bug description: $ cat /proc/version_signature Ubuntu 4.15.0-29.31-generic 4.15.18 $ lsb_release -rd Description: Ubuntu Cosmic Cuttlefish (development branch) Release: 18.10 $ apt-cache policy linux-image-`uname -r` linux-image-4.15.0-29-generic: Installed: 4.15.0-29.31 Candidate: 4.15.0-29.31 Version table: *** 4.15.0-29.31 500 500 http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages 100 /var/lib/dpkg/status 3) mkfs.ext4 /dev/bcache0 returns successful creating an ext4 filesystem on top of a bcache device 4) mkfs.ext4 doesn't return and kernel prints hung process info [ 58.018099] cloud-init[920]: Running command ['mkfs.ext4', '-F', '-L', 'root-fs', '-U', 'f01aec97-9457-11e8-b8d6-525400123401', '/dev/bcache0'] with allowed return codes [0] (capture=True) [ 242.652018] INFO: task kworker/u4:0:5 blocked for more than 120 seconds. [ 242.653767] Tainted: P O 4.15.0-29-generic #31-Ubuntu [ 242.655391] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 242.657397] INFO: task kworker/0:2:410 blocked for more than 120 seconds. [ 242.659126] Tainted: P O 4.15.0-29-generic #31-Ubuntu [ 242.660980] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 242.663000] INFO: task bcache_allocato:2326 blocked for more than 120 seconds. [ 242.664807] Tainted: P O 4.15.0-29-generic #31-Ubuntu [ 242.666516] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 242.668503] INFO: task bcache_writebac:2345 blocked for more than 120 seconds. [ 242.670301] Tainted: P O 4.15.0-29-generic #31-Ubuntu [ 242.671936] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 242.673909] INFO: task mkfs.ext4:2803 blocked for more than 120 seconds. [ 242.675414] Tainted: P O 4.15.0-29-generic #31-Ubuntu [ 242.677038] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 363.483998] INFO: task kworker/u4:0:5 blocked for more than 120 seconds. [ 363.488441] Tainted: P O 4.15.0-29-generic #31-Ubuntu [ 363.489598] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 363.491043] INFO: task kworker/0:2:410 blocked for more than 120 seconds. [ 363.492252] Tainted: P O 4.15.0-29-generic #31-Ubuntu [ 363.494085] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 363.495659] INFO: task bcache_allocato:2326 blocked for more than 120 seconds. [ 363.496957] Tainted: P O 4.15.0-29-generic #31-Ubuntu [ 363.498454] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 363.499866] INFO: task bcache_writebac:2345 blocked for more than 120 seconds. [ 363.501156] Tainted: P O 4.15.0-29-generic #31-Ubuntu [ 363.502597] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 363.504048] INFO: task mkfs.ext4:2803 blocked for more than 120 seconds. [ 363.505505] Tainted: P O 4.15.0-29-generic #31-Ubuntu [ 363.506677] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. System has two virtio block devices. bcache was created like so: make-bcache -C /dev/vdb make-bcache -B /dev/vda2 resulting in /dev/bcache0 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.15.0-29-generic 4.15.0-29.31 ProcVersionSignature: User Name 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 31 15:52 seq crw-rw 1 root audio 116, 33 Jul 31 15:52 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu7 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 Date: Tue Jul 31 15:53:56 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcEnviron:
[Kernel-packages] [Bug 1728244] Re: Touchpad stops working after reboot on Apollo Lake
@Boris, it's probably better you followup on these bug threads more specific to your Notebook and touchpad device: https://bugzilla.redhat.com/show_bug.cgi?id=1591307#c6 Hans de Goede 2018-06-17 05:56:11 EDT (In reply to Viktar from comment #0) > I am trying to use Fedora 28 on Chuwi Lapbook Air, but touchpad does not > work. > Similar problem was in bug "1526312", but it seems like I have ALPS touchpad > and modified "i2c-hid.c" file does not work for me after recompiling the > kernel. I don't think you have the same issue, the problem in bug 1526312 is a touchpad with missing descriptors. I think what you are seeing is the same i2c-hid touchpad power- management issue as other people or seeing on various ezbook models. This is currently being discussed here: https://bugzilla.kernel.org/show_bug.cgi?id=199821 The touchpad should work after a suspend/resume. You may need to do: sudo rmmod i2c-hid sudo modprobe i2c-hid After suspend-resume. ** Bug watch added: Red Hat Bugzilla #1591307 https://bugzilla.redhat.com/show_bug.cgi?id=1591307 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1728244 Title: Touchpad stops working after reboot on Apollo Lake Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Bug description: On the Jumper EZBook 3 Pro (V4) laptop, using an Apollo Lake N3450 processor, if you install Ubuntu 17.10 (or less) with isorespin and use rEFInd as bootloader (this is the only way to get linux booting on this laptop) everything works out of the box, but after a reboot or two the touchpad stops working. Both in Ubuntu and Windows 10. The only way to restore functionality is to boot from usb key ubuntu 17.10 respined, or disassemble laptop and detach-reattach battery cable. This is mesg | grep i2c_hid: [ 2056.460636] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (27/34) [ 3077.604699] i2c_hid i2c-SYNA3602:00: failed to reset device. [ 3077.605473] dpm_run_callback(): i2c_hid_resume+0x0/0xe0 [i2c_hid] returns -61 [ 3080.468156] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (27/34) uname -rvps Linux 4.10.0-32-generic #36~16.04.1-Ubuntu SMP Wed Aug 9 09:19:02 UTC 2017 x86_64 There has to be a bug in the kernel. Any way to avoid this? To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1728244/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1781476] Re: [Bionic] bug fixes to improve stability of the ThunderX2 i2c driver
-- Kernel version --
ubuntu@apollo:~$ apt policy linux-image-4.15.0-31
linux-image-4.15.0-31-generic:
Installed: 4.15.0-31.33
Candidate: 4.15.0-31.33
Version table:
*** 4.15.0-31.33 500
500 http://ports.ubuntu.com/ubuntu-ports bionic-proposed/main arm64
Packages
100 /var/lib/dpkg/status
linux-image-4.15.0-31-snapdragon:
Installed: (none)
Candidate: 4.15.0-31.33
Version table:
4.15.0-31.33 500
500 http://ports.ubuntu.com/ubuntu-ports bionic-proposed/main arm64
Packages
ubuntu@apollo:~$
-- Testcase --
for i in {1..100}; do sudo ipmitool sensor list; done
for i in {1..100}; do sudo ipmitool mc info; done
-- Results --
No issues found, the commands printed information and there were no stack
corruptions.
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1781476
Title:
[Bionic] bug fixes to improve stability of the ThunderX2 i2c driver
Status in linux package in Ubuntu:
Fix Committed
Status in linux source package in Bionic:
Fix Committed
Bug description:
[Impact]
With ThunderX2 i2c driver, ipmi transfers may get stuck or stack corruption
might occur.
[Test]
Generate data with ipmitool:
for i in {1..100}; do sudo ipmitool sensor list; done
for i in {1..100}; do sudo ipmitool mc info; done
[Fix]
88b4116e7e98 i2c: xlp9xx: Make sure the transfer size is not more than
I2C_SMBUS_BLOCK_SIZE
8d504d804ab6 i2c: xlp9xx: Fix issue seen when updating receive length
[Regression Potential]
The driver is limited to ThunderX2 hardware, and bug fixes to this driver
does not have any impact on other platforms. There for risk for regression is
low.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781476/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1728244] Re: Touchpad stops working after reboot on Apollo Lake
@Boris, there is a mention in this Arch Linux discussion thread of Kernel 4.14.04 and 4.14-rc7 working for your touchpad: https://bbs.archlinux.org/viewtopic.php?pid=1768446#p1768446 I don't know why kernel 4.18 would not also have this fix. If it works, then just don't update the kernel. http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.14-rc7/ [PS!] See this. There there is at least one other bug already open on this specific to the ALPS0001 touchpad: https://bugzilla.redhat.com/show_bug.cgi?id=1569422 ** Bug watch added: Red Hat Bugzilla #1569422 https://bugzilla.redhat.com/show_bug.cgi?id=1569422 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1728244 Title: Touchpad stops working after reboot on Apollo Lake Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Bug description: On the Jumper EZBook 3 Pro (V4) laptop, using an Apollo Lake N3450 processor, if you install Ubuntu 17.10 (or less) with isorespin and use rEFInd as bootloader (this is the only way to get linux booting on this laptop) everything works out of the box, but after a reboot or two the touchpad stops working. Both in Ubuntu and Windows 10. The only way to restore functionality is to boot from usb key ubuntu 17.10 respined, or disassemble laptop and detach-reattach battery cable. This is mesg | grep i2c_hid: [ 2056.460636] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (27/34) [ 3077.604699] i2c_hid i2c-SYNA3602:00: failed to reset device. [ 3077.605473] dpm_run_callback(): i2c_hid_resume+0x0/0xe0 [i2c_hid] returns -61 [ 3080.468156] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (27/34) uname -rvps Linux 4.10.0-32-generic #36~16.04.1-Ubuntu SMP Wed Aug 9 09:19:02 UTC 2017 x86_64 There has to be a bug in the kernel. Any way to avoid this? To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1728244/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1752961] Re: With kernel 4.13 btrfs scans for devices before all devices have been discovered
Sorry for the delay. I missed the email regarding you're test results
of the last kernel.
I built the next test kernel, up to the following commit:
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1752961
Can you test that kernel and report back if it has the bug or not? I
will build the next test kernel based on your test results.
Thanks in advance
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1752961
Title:
With kernel 4.13 btrfs scans for devices before all devices have been
discovered
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Artful:
Won't Fix
Status in linux source package in Bionic:
In Progress
Status in linux source package in Cosmic:
In Progress
Bug description:
See attached dmesg outputs for booting kernels 4.11.x (working) and
4.13.x (not working).
dmesg-4.11.0-14-good.txt shows the dmesg output when booting kernel 4.11.x.
btrfs scans for devices after all 4 (sda, sdb, sdc, sdd) of the devices have
been discovered by the kernel. The btrfs RAID1 filesystem mounts, and
everything is good.
dmesg-4.13.0-36-fail.txt shows the dmesg output when booting kernel 4.13.x.
btrfs scans for devices after only 2 (sda, sdb) of the devices have been
discovered by the kernel. The btrfs RAID1 filesystem fails to mount ("failed
to read the system array: -5"). The remaining 2 devices (sdc, sdd) are
discovered by the kernel immediately afterward. At the end of the log, I run
`btrfs device scan` and mount the filesystem manually.
Hardware:
HP ProLiant MicroServer Gen8
4x WDC WD20EFRX
---
AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code
2: ls: cannot access '/dev/snd/': No such file or directory
AplayDevices: aplay: device_list:270: no soundcards found...
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
ArecordDevices: arecord: device_list:270: no soundcards found...
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2015-10-15 (933 days ago)
InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
MachineType: HP ProLiant MicroServer Gen8
Package: linux (not installed)
ProcEnviron:
TERM=linux
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-20-generic
root=UUID=d976ab07-8377-46dd-ac6c-f5f7312a8305 ro rootflags=subvol=@
rootdelay=10
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
Tags: bionic apport-hook-error
Uname: Linux 4.15.0-20-generic x86_64
UnreportableReason: This report is about a package that is not installed.
UpgradeStatus: Upgraded to bionic on 2018-05-05 (0 days ago)
UserGroups:
_MarkForUpload: True
dmi.bios.date: 07/16/2015
dmi.bios.vendor: HP
dmi.bios.version: J06
dmi.chassis.type: 7
dmi.chassis.vendor: HP
dmi.modalias:
dmi:bvnHP:bvrJ06:bd07/16/2015:svnHP:pnProLiantMicroServerGen8:pvr:cvnHP:ct7:cvr:
dmi.product.family: ProLiant
dmi.product.name: ProLiant MicroServer Gen8
dmi.sys.vendor: HP
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752961/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1767711] Re: Nvidia+XFCE: Totem window is see-through during playback, colours washed out
I suggested to test with MATE's compositing window manager "marco" also. Any results? Another test case would be to use xfwm4 with disabled compositor plus "compton" (standalone compositing manager). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1767711 Title: Nvidia+XFCE: Totem window is see-through during playback, colours washed out Status in nvidia-graphics-drivers-390 package in Ubuntu: New Status in totem package in Ubuntu: New Status in xfce4 package in Ubuntu: Incomplete Bug description: Since the upgrade to Ubuntu 18.04, the Totem player will show everything behind it during playback, and the colours of the video are washed-out. https://i.imgur.com/0AwJMmf.jpg I did not find 'tranparency' nor 'opacity' setting in the program preferences, and the colour adjudgement settings are pinned to +/-0. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: totem 3.26.0-0ubuntu6 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Apr 28 14:56:29 2018 InstallationDate: Installed on 2016-06-05 (692 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: totem UpgradeStatus: Upgraded to bionic on 2018-04-27 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1767711/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1784152] Re: i2c_hid_get_input floods system logs
I built a test kernel with commit ef6eaf27274c0351f7059163918f3795da13199c. The test kernel can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1784152 Can you test this kernel and see if it resolves this bug? Note about installing test kernels: • If the test kernel is prior to 4.15(Bionic) you need to install the linux-image and linux-image-extra .deb packages. • If the test kernel is 4.15(Bionic) or newer, you need to install the linux-modules, linux-modules-extra and linux-image-unsigned .deb packages. Thanks in advance! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1784152 Title: i2c_hid_get_input floods system logs Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 4.15.0-29.31-generic 4.15.18 After upgrading to kernel version 4.15.0-29 from 4.15.0-23, the system logs are flooded whenever I move the cursor with my touchpad. It looks like this: i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535) i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535) i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535) i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535) etc... This problem did not occur on the previous kernel version so there must have been a change to the "drivers/hid/i2c-hid/i2c-hid.c" file. This seems to be fixed in a recent commit here: https://github.com/torvalds/linux/commit/ef6eaf27274c0351f7059163918f3795da13199c I am currently running the older kernel version but would still like to be up to date without this flooding happening. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784152/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786382] Re: Repeated crashes in cifs kernel code
I'm sorry, I found a workaround for this issue -- changing my Synology NAS configuration to allow SMB 3 to be used made the problem go away, or at least it seemed to -- and I don't have any more time to spend troubleshooting it. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1786382 Title: Repeated crashes in cifs kernel code Status in linux package in Ubuntu: Incomplete Bug description: While trying to write a bunch of files in quick succession to a CIFS filesystem on my Synology NAS, I start getting kernel oopses and the terminal windows in which I'm doing the file operations -- whose current directories are inside the CIFS filesystem -- suddenly crashing. For some reason apport is not picking up on this so I'm reporting manually. Here's one of the oopses: [ 871.470183] general protection fault: [#4] SMP PTI [ 871.470188] Modules linked in: rfcomm xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 bridge stp llc devlink ebtable_filter ebtables pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) cachefiles md4 nfsv3 nfs_acl rpcsec_gss_krb5 auth_rpcgss nfsv4 nls_utf8 cifs nfs lockd ccm grace fscache xt_multiport cmac bnep binfmt_misc ip6t_REJECT nf_reject_ipv6 nls_iso8859_1 xt_hl ip6t_rt nf_conntrack_ipv6 nf_defrag_ipv6 ipt_REJECT nf_reject_ipv4 xt_comment xt_limit xt_tcpudp snd_hda_codec_hdmi xt_addrtype intel_rapl sparse_keymap wmi_bmof x86_pkg_temp_thermal intel_powerclamp nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack coretemp kvm_intel kvm snd_hda_codec_realtek arc4 snd_hda_codec_generic snd_hda_intel irqbypass uvcvideo snd_hda_codec btusb snd_usb_audio [ 871.470259] btrtl videobuf2_vmalloc snd_hda_core btbcm videobuf2_memops crct10dif_pclmul btintel snd_usbmidi_lib videobuf2_v4l2 snd_hwdep videobuf2_core bluetooth input_leds snd_seq_midi videodev snd_seq_midi_event snd_pcm crc32_pclmul snd_rawmidi media ghash_clmulni_intel ecdh_generic snd_seq cryptd intel_cstate snd_seq_device intel_rapl_perf iwlmvm mac80211 ip6table_filter ip6_tables snd_timer iwlwifi snd nf_conntrack_netbios_ns nvidia_uvm(POE) cfg80211 soundcore serio_raw nf_conntrack_broadcast shpchp wmi mei_me intel_pch_thermal acpi_pad mei mac_hid tpm_crb nf_nat_ftp nf_nat nf_conntrack_ftp nf_conntrack libcrc32c sch_fq_codel iptable_filter parport_pc ppdev sunrpc lp parport ip_tables x_tables autofs4 hid_logitech_hidpp hid_generic hid_logitech_dj uas usbhid usb_storage hid dm_mirror dm_region_hash [ 871.470329] dm_log nvidia_drm(POE) nvidia_modeset(POE) nvidia(POE) drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops psmouse drm r8169 ahci ipmi_devintf mii libahci ipmi_msghandler video [ 871.470351] CPU: 6 PID: 8614 Comm: nautilus Tainted: P DOE 4.15.0-30-generic #32-Ubuntu [ 871.470354] Hardware name: Acer Predator G6-710/Predator G6-710, BIOS R01-A4 05/18/2016 [ 871.470362] RIP: 0010:kmem_cache_alloc+0x81/0x1b0 [ 871.470365] RSP: 0018:bbed47c9f618 EFLAGS: 00010202 [ 871.470369] RAX: 65b1b269c87f4446 RBX: 65b1b269c87f4446 RCX: 0ee9 [ 871.470372] RDX: 0ee8 RSI: 01011200 RDI: 0002b5c0 [ 871.470375] RBP: bbed47c9f648 R08: 9e312edab5c0 R09: [ 871.470378] R10: bbed47c9f870 R11: c1ab4000 R12: 01011200 [ 871.470381] R13: 9e311bdbdb00 R14: 65b1b269c87f4446 R15: 9e311bdbdb00 [ 871.470385] FS: 7f2f11675700() GS:9e312ed8() knlGS: [ 871.470388] CS: 0010 DS: ES: CR0: 80050033 [ 871.470391] CR2: 55ba011c7100 CR3: 000451898004 CR4: 003606e0 [ 871.470395] DR0: DR1: DR2: [ 871.470398] DR3: DR6: fffe0ff0 DR7: 0400 [ 871.470400] Call Trace: [ 871.470408] ? mempool_alloc_slab+0x15/0x20 [ 871.470415] ? wait_woken+0x80/0x80 [ 871.470419] mempool_alloc_slab+0x15/0x20 [ 871.470424] mempool_alloc+0x71/0x190 [ 871.470453] cifs_small_buf_get+0x1a/0x30 [cifs] [ 871.470482] small_smb2_init+0x62/0xb0 [cifs] [ 871.470511] SMB2_open+0xc3/0xb50 [cifs] [ 871.470535] ? cifsConvertToUTF16+0x1e9/0x420 [cifs] [ 871.470558] ? cifs_strndup_to_utf16+0xbd/0x110 [cifs] [ 871.470585] smb2_open_op_close+0xad/0x220 [cifs] [ 871.470609] ? smb2_open_op_close+0xad/0x220 [cifs] [ 871.470616] ? alloc_pages_current+0x6a/0xe0 [ 871.470640] smb2_query_path_info+0x74/0xf0 [cifs] [ 871.470667] cifs_get_inode_info+0x4eb/0xab0 [cifs] [ 871.470692] ? build_path_from_dentry_optional_prefix+0x179/0x3e0 [cifs] [ 871.470715] cifs_revalidate_dentry_attr+0x1d8/0x250 [cifs] [ 871.470739] cifs_revalidate_dentry+0x13/0x30 [cifs] [ 871.470760] cifs_d_revalidate+0x27/0xb0 [cifs] [
[Kernel-packages] [Bug 1786713] Re: MODULE_SOFTDEP for crc32c is not working
I don't know, why this is not working. With kernel source 4.15.17 there was no problem. I didn't see errors while compiling 4.15.18. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1786713 Title: MODULE_SOFTDEP for crc32c is not working Status in linux package in Ubuntu: Incomplete Bug description: I have a kernel config with Ext4, for which softdep is not working. See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1778265 Ubuntu 18.04. Kernel 4.17.18 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786713/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786382] Re: Repeated crashes in cifs kernel code
Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem? Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.18 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.18 ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1786382 Title: Repeated crashes in cifs kernel code Status in linux package in Ubuntu: Incomplete Bug description: While trying to write a bunch of files in quick succession to a CIFS filesystem on my Synology NAS, I start getting kernel oopses and the terminal windows in which I'm doing the file operations -- whose current directories are inside the CIFS filesystem -- suddenly crashing. For some reason apport is not picking up on this so I'm reporting manually. Here's one of the oopses: [ 871.470183] general protection fault: [#4] SMP PTI [ 871.470188] Modules linked in: rfcomm xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 bridge stp llc devlink ebtable_filter ebtables pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) cachefiles md4 nfsv3 nfs_acl rpcsec_gss_krb5 auth_rpcgss nfsv4 nls_utf8 cifs nfs lockd ccm grace fscache xt_multiport cmac bnep binfmt_misc ip6t_REJECT nf_reject_ipv6 nls_iso8859_1 xt_hl ip6t_rt nf_conntrack_ipv6 nf_defrag_ipv6 ipt_REJECT nf_reject_ipv4 xt_comment xt_limit xt_tcpudp snd_hda_codec_hdmi xt_addrtype intel_rapl sparse_keymap wmi_bmof x86_pkg_temp_thermal intel_powerclamp nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack coretemp kvm_intel kvm snd_hda_codec_realtek arc4 snd_hda_codec_generic snd_hda_intel irqbypass uvcvideo snd_hda_codec btusb snd_usb_audio [ 871.470259] btrtl videobuf2_vmalloc snd_hda_core btbcm videobuf2_memops crct10dif_pclmul btintel snd_usbmidi_lib videobuf2_v4l2 snd_hwdep videobuf2_core bluetooth input_leds snd_seq_midi videodev snd_seq_midi_event snd_pcm crc32_pclmul snd_rawmidi media ghash_clmulni_intel ecdh_generic snd_seq cryptd intel_cstate snd_seq_device intel_rapl_perf iwlmvm mac80211 ip6table_filter ip6_tables snd_timer iwlwifi snd nf_conntrack_netbios_ns nvidia_uvm(POE) cfg80211 soundcore serio_raw nf_conntrack_broadcast shpchp wmi mei_me intel_pch_thermal acpi_pad mei mac_hid tpm_crb nf_nat_ftp nf_nat nf_conntrack_ftp nf_conntrack libcrc32c sch_fq_codel iptable_filter parport_pc ppdev sunrpc lp parport ip_tables x_tables autofs4 hid_logitech_hidpp hid_generic hid_logitech_dj uas usbhid usb_storage hid dm_mirror dm_region_hash [ 871.470329] dm_log nvidia_drm(POE) nvidia_modeset(POE) nvidia(POE) drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops psmouse drm r8169 ahci ipmi_devintf mii libahci ipmi_msghandler video [ 871.470351] CPU: 6 PID: 8614 Comm: nautilus Tainted: P DOE 4.15.0-30-generic #32-Ubuntu [ 871.470354] Hardware name: Acer Predator G6-710/Predator G6-710, BIOS R01-A4 05/18/2016 [ 871.470362] RIP: 0010:kmem_cache_alloc+0x81/0x1b0 [ 871.470365] RSP: 0018:bbed47c9f618 EFLAGS: 00010202 [ 871.470369] RAX: 65b1b269c87f4446 RBX: 65b1b269c87f4446 RCX: 0ee9 [ 871.470372] RDX: 0ee8 RSI: 01011200 RDI: 0002b5c0 [ 871.470375] RBP: bbed47c9f648 R08: 9e312edab5c0 R09: [ 871.470378] R10: bbed47c9f870 R11: c1ab4000 R12: 01011200 [ 871.470381] R13: 9e311bdbdb00 R14: 65b1b269c87f4446 R15: 9e311bdbdb00 [ 871.470385] FS: 7f2f11675700() GS:9e312ed8() knlGS: [ 871.470388] CS: 0010 DS: ES: CR0: 80050033 [ 871.470391] CR2: 55ba011c7100 CR3: 000451898004 CR4: 003606e0 [ 871.470395] DR0: DR1: DR2: [ 871.470398] DR3: DR6: fffe0ff0 DR7: 0400 [ 871.470400] Call Trace: [ 871.470408] ? mempool_alloc_slab+0x15/0x20 [ 871.470415] ? wait_woken+0x80/0x80 [ 871.470419] mempool_alloc_slab+0x15/0x20 [ 871.470424] mempool_alloc+0x71/0x190 [ 871.470453] cifs_small_buf_get+0x1a/0x30 [cifs] [ 871.470482] small_smb2_init+0x62/0xb0 [cifs] [ 871.470511] SMB2_open+0xc3/0xb50 [cifs] [ 871.470535] ? cifsConvertToUTF16+0x1e9/0x420 [cifs] [ 871.470558] ?
[Kernel-packages] [Bug 1786341] Re: Touchpad doesn't work
Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem? Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.18 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.18 ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1786341 Title: Touchpad doesn't work Status in linux package in Ubuntu: Incomplete Bug description: Hello! I have Asus of TUF GAMING FX504 series. When I connect external mouse it works. However touchpad doesn't response at all. Output of "cat /proc/bus/input/devices" command doesn't show any kind of touchpad device. I have Ubuntu 18.04.1 LTS installed. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: firefly1445 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-07-06 (34 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 13d3:5666 IMC Networks Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 005: ID 2717:5001 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. TUF GAMING FX504GD_FX80GD Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic root=UUID=fa887fbb-ea9a-48ca-996f-8246577c2af3 ro quiet splash nouveau.modeset=0 acpi_backlight=vendor vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-30-generic N/A linux-backports-modules-4.15.0-30-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-30-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/11/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FX504GD.310 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: FX504GD 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.:bvrFX504GD.310:bd05/11/2018:svnASUSTeKCOMPUTERINC.:pnTUFGAMINGFX504GD_FX80GD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFX504GD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: TUF GAMING dmi.product.name: TUF GAMING FX504GD_FX80GD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: firefly1445 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-07-06 (34 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 13d3:5666 IMC Networks Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 005: ID 2717:5001 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. TUF GAMING FX504GD_FX80GD Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic root=UUID=fa887fbb-ea9a-48ca-996f-8246577c2af3 ro quiet splash nouveau.modeset=0 acpi_backlight=vendor vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-30-generic N/A linux-backports-modules-4.15.0-30-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-30-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/11/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version:
[Kernel-packages] [Bug 1786752] Re: Reference counter issue in 4.15 (nf_xfrm_me_harder / dst_release)
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.18 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.18 ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1786752 Title: Reference counter issue in 4.15 (nf_xfrm_me_harder / dst_release) Status in linux package in Ubuntu: Incomplete Bug description: Since upgrading from 14.04 to 18.04, we see very frequent warnings about negative refcnts in dst_release: [ 3117.882227] WARNING: CPU: 6 PID: 0 at /build/linux-I4R9hO/linux-4.15.0/include/net/dst.h:256 nf_xfrm_me_harder+0x127/0x140 [nf_nat] [ 3117.882229] Modules linked in: xt_policy cls_u32 sch_sfq ip_vti ip_tunnel authenc echainiv xfrm6_mode_tunnel xfrm4_mode_tunnel xfrm4_tunnel tunnel4 ipcomp xfrm_ipcomp esp4 ah4 af_key nfnetlink_queue nfnetlink_log sch_htb xt_TPROXY xt_multiport veth nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo br_netfilter bridge overlay macvlan 8021q garp mrp stp llc bonding algif_skcipher af_alg xt_hl ip6t_rt nf_conntrack_ipv6 nf_defrag_ipv6 ip6t_REJECT nf_reject_ipv6 xt_nat ipt_MASQUERADE nf_nat_masquerade_ipv4 dm_crypt iptable_nat nf_nat_ipv4 xt_DSCP xt_dscp xt_mark iptable_mangle xt_limit xt_tcpudp xt_addrtype intel_rapl sb_edac x86_pkg_temp_thermal intel_powerclamp coretemp nf_conntrack_ipv4 nf_defrag_ipv4 kvm_intel xt_conntrack kvm joydev input_leds ipt_REJECT nf_reject_ipv4 ftdi_sio usbserial ipmi_si [ 3117.882265] irqbypass intel_cstate mei_me mei ioatdma acpi_pad intel_rapl_perf shpchp ipmi_devintf ipmi_msghandler acpi_power_meter lpc_ich mac_hid ip6table_filter ip6_tables nf_conntrack_netbios_ns nf_conntrack_broadcast nf_nat_ftp nf_nat nf_conntrack_ftp sch_fq_codel nf_conntrack iptable_filter 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 mgag200 ttm crct10dif_pclmul igb ixgbe crc32_pclmul drm_kms_helper hid_generic ghash_clmulni_intel syscopyarea i2c_algo_bit dca sysfillrect usbhid pcbc sysimgblt fb_sys_fops aesni_intel aes_x86_64 crypto_simd ahci glue_helper ptp hid mxm_wmi cryptd [ 3117.882309] drm libahci megaraid_sas pps_core mdio wmi [ 3117.882315] CPU: 6 PID: 0 Comm: swapper/6 Tainted: GW 4.15.0-30-generic #32-Ubuntu [ 3117.882316] Hardware name: Intel Corporation S2600WT2R/S2600WT2R, BIOS SE5C610.86B.01.01.0022.062820171903 06/28/2017 [ 3117.882319] RIP: 0010:nf_xfrm_me_harder+0x127/0x140 [nf_nat] [ 3117.882320] RSP: 0018:88d77f3839f0 EFLAGS: 00010246 [ 3117.882322] RAX: RBX: 90de4000 RCX: 1924 [ 3117.882323] RDX: RSI: 88d749ae6400 RDI: 88d655e96600 [ 3117.882324] RBP: 88d77f383a68 R08: 88d7493dc000 R09: 0018 [ 3117.882324] R10: 0001 R11: 88e770dedc00 R12: 88d655e96600 [ 3117.882325] R13: 88d77f383ae8 R14: 88d7799ff200 R15: 88d7493dc000 [ 3117.882327] FS: () GS:88d77f38() knlGS: [ 3117.882327] CS: 0010 DS: ES: CR0: 80050033 [ 3117.882328] CR2: ff600400 CR3: 00193de0a002 CR4: 003606e0 [ 3117.882329] DR0: DR1: DR2: [ 3117.882330] DR3: DR6: fffe0ff0 DR7: 0400 [ 3117.882331] Call Trace: [ 3117.882332] [ 3117.882337] ? nf_nat_ipv4_fn+0x15b/0x200 [nf_nat_ipv4] [ 3117.882339] nf_nat_ipv4_out+0xc5/0xe0 [nf_nat_ipv4] [ 3117.882342] iptable_nat_ipv4_out+0x15/0x20 [iptable_nat] [ 3117.882347] nf_hook_slow+0x48/0xc0 [ 3117.882353] ip_output+0xd2/0xe0 [ 3117.882355] ? ip_fragment.constprop.44+0x80/0x80 [ 3117.882357] ip_forward_finish+0x49/0x70 [ 3117.882359] ip_forward+0x366/0x440 [ 3117.882361] ? ip_frag_mem+0x20/0x20 [ 3117.882362] ip_rcv_finish+0x129/0x430 [ 3117.882364] ip_rcv+0x28f/0x3a0 [ 3117.882366] ? inet_del_offload+0x40/0x40 [ 3117.882372] __netif_receive_skb_core+0x432/0xb40 [ 3117.882379] ? handle_edge_irq+0x7c/0x190 [ 3117.882384] ? irq_exit+0x67/0xc0 [ 3117.882391] ? do_IRQ+0x82/0xd0 [ 3117.882393] __netif_receive_skb+0x18/0x60 [ 3117.882395] ?
[Kernel-packages] [Bug 1543418] Re: Closing lid causes system hang
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.18 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.18-rc8 ** Changed in: linux (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1543418 Title: Closing lid causes system hang Status in linux package in Ubuntu: Incomplete Bug description: I have been having this problem for a past few weeks. I have been using this system for almost 1 year. I use with the power setting to suspend my system when I close the lid. In the past few weeks sometimes when I close the lid, the system doesn't gets suspended. Instead, it gets stuck. When i reopen the lid screen will be back and nothing can bring the system back. I have to restart the system by pressing the power key. No key is working during this state. I tried pressing num lock and no response. It happened rarely before. But for past few days, my system has been getting stuck like this more. Before this, I used to have system crash suddenly and lose all data without any reasons. I am fairly new to ubuntu I don't know how to diagnose these things. Please help me. Thank you To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1543418/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1784665] Re: mkfs.ext4 over /dev/bcache0 hangs
To narrow it down further, can you test the following two kernels: 4.14 Final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.14/ 4.15-rc1: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15-rc1/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1784665 Title: mkfs.ext4 over /dev/bcache0 hangs Status in linux package in Ubuntu: Confirmed Status in linux source package in Cosmic: Confirmed Bug description: $ cat /proc/version_signature Ubuntu 4.15.0-29.31-generic 4.15.18 $ lsb_release -rd Description: Ubuntu Cosmic Cuttlefish (development branch) Release: 18.10 $ apt-cache policy linux-image-`uname -r` linux-image-4.15.0-29-generic: Installed: 4.15.0-29.31 Candidate: 4.15.0-29.31 Version table: *** 4.15.0-29.31 500 500 http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages 100 /var/lib/dpkg/status 3) mkfs.ext4 /dev/bcache0 returns successful creating an ext4 filesystem on top of a bcache device 4) mkfs.ext4 doesn't return and kernel prints hung process info [ 58.018099] cloud-init[920]: Running command ['mkfs.ext4', '-F', '-L', 'root-fs', '-U', 'f01aec97-9457-11e8-b8d6-525400123401', '/dev/bcache0'] with allowed return codes [0] (capture=True) [ 242.652018] INFO: task kworker/u4:0:5 blocked for more than 120 seconds. [ 242.653767] Tainted: P O 4.15.0-29-generic #31-Ubuntu [ 242.655391] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 242.657397] INFO: task kworker/0:2:410 blocked for more than 120 seconds. [ 242.659126] Tainted: P O 4.15.0-29-generic #31-Ubuntu [ 242.660980] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 242.663000] INFO: task bcache_allocato:2326 blocked for more than 120 seconds. [ 242.664807] Tainted: P O 4.15.0-29-generic #31-Ubuntu [ 242.666516] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 242.668503] INFO: task bcache_writebac:2345 blocked for more than 120 seconds. [ 242.670301] Tainted: P O 4.15.0-29-generic #31-Ubuntu [ 242.671936] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 242.673909] INFO: task mkfs.ext4:2803 blocked for more than 120 seconds. [ 242.675414] Tainted: P O 4.15.0-29-generic #31-Ubuntu [ 242.677038] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 363.483998] INFO: task kworker/u4:0:5 blocked for more than 120 seconds. [ 363.488441] Tainted: P O 4.15.0-29-generic #31-Ubuntu [ 363.489598] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 363.491043] INFO: task kworker/0:2:410 blocked for more than 120 seconds. [ 363.492252] Tainted: P O 4.15.0-29-generic #31-Ubuntu [ 363.494085] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 363.495659] INFO: task bcache_allocato:2326 blocked for more than 120 seconds. [ 363.496957] Tainted: P O 4.15.0-29-generic #31-Ubuntu [ 363.498454] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 363.499866] INFO: task bcache_writebac:2345 blocked for more than 120 seconds. [ 363.501156] Tainted: P O 4.15.0-29-generic #31-Ubuntu [ 363.502597] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 363.504048] INFO: task mkfs.ext4:2803 blocked for more than 120 seconds. [ 363.505505] Tainted: P O 4.15.0-29-generic #31-Ubuntu [ 363.506677] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. System has two virtio block devices. bcache was created like so: make-bcache -C /dev/vdb make-bcache -B /dev/vda2 resulting in /dev/bcache0 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.15.0-29-generic 4.15.0-29.31 ProcVersionSignature: User Name 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 31 15:52 seq crw-rw 1 root audio 116, 33 Jul 31 15:52 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu7 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 Date: Tue Jul 31 15:53:56 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcEnviron:
Re: [Kernel-packages] [Bug 1543418] Re: Closing lid causes system hang
Sure. Will check it and update. Will probably takes some time to update since issue is not reproduced everytime. I will use it for 1 month max and if no issue report same fine? On Mon, Aug 13, 2018, 10:35 PM Joseph Salisbury < joseph.salisb...@canonical.com> wrote: > Would it be possible for you to test the latest upstream kernel? Refer > to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest > v4.18 kernel[0]. > > If this bug is fixed in the mainline kernel, please add the following > tag 'kernel-fixed-upstream'. > > If the mainline kernel does not fix this bug, please add the tag: > 'kernel-bug-exists-upstream'. > > Once testing of the upstream kernel is complete, please mark this bug as > "Confirmed". > > > Thanks in advance. > > [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.18-rc8 > > > ** Changed in: linux (Ubuntu) >Importance: Undecided => Medium > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1543418 > > Title: > Closing lid causes system hang > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1543418/+subscriptions > -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1543418 Title: Closing lid causes system hang Status in linux package in Ubuntu: Incomplete Bug description: I have been having this problem for a past few weeks. I have been using this system for almost 1 year. I use with the power setting to suspend my system when I close the lid. In the past few weeks sometimes when I close the lid, the system doesn't gets suspended. Instead, it gets stuck. When i reopen the lid screen will be back and nothing can bring the system back. I have to restart the system by pressing the power key. No key is working during this state. I tried pressing num lock and no response. It happened rarely before. But for past few days, my system has been getting stuck like this more. Before this, I used to have system crash suddenly and lose all data without any reasons. I am fairly new to ubuntu I don't know how to diagnose these things. Please help me. Thank you To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1543418/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786713] Re: MODULE_SOFTDEP for crc32c is not working
Can you expand upon why it is not working? Was it once working and now it is not? Are you seeing specific errors? ** Tags added: kernel-da-key ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1786713 Title: MODULE_SOFTDEP for crc32c is not working Status in linux package in Ubuntu: Incomplete Bug description: I have a kernel config with Ext4, for which softdep is not working. See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1778265 Ubuntu 18.04. Kernel 4.17.18 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786713/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786419] Re: Acer Aspire E5-574G Touchpad does not work
Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem? Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.18 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.18 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1786419 Title: Acer Aspire E5-574G Touchpad does not work Status in linux package in Ubuntu: Confirmed Bug description: On Ubuntu 18.04 LTS with Kernel 4.15.0-31-generic #33-Ubuntu the built in touch pad does not work. But both mouse buttons works (hard press on touchpad). lsb_release -rd Description:Ubuntu 18.04.1 LTS Release:18.04 dmidecode hardware info: System Information Manufacturer: Acer Product Name: Aspire E5-574G Version: V1.18 xinput: ⎡ Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointerid=4[slave pointer (2)] ⎜ ↳ Microsoft Compact Optical Mouse 500 id=11 [slave pointer (2)] ⎜ ↳ ELAN0501:00 04F3:300B Touchpadid=13 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Button id=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] ↳ Power Button id=9[slave keyboard (3)] ↳ Sleep Button id=10 [slave keyboard (3)] ↳ HD WebCam: HD WebCam id=12 [slave keyboard (3)] ↳ AT Translated Set 2 keyboard id=14 [slave keyboard (3)] ↳ Acer WMI hotkeys id=15 [slave keyboard (3)] Also a try to compose a udev rule with: sudo touchpad-edge-detector 106x78 /dev/input/event10 Touchpad ELAN0501:00 04F3:300B Touchpad on /dev/input/event10 Move one finger around the touchpad to detect the actual edges Kernel says:x [0..3239], y [0..2347] Touchpad sends: x [0..3239], y [0..2347] --- \ Touchpad sends: x [0..3239], y [0..2347] /^C Touchpad size as listed by the kernel: 104x73mm User-specified touchpad size: 106x78mm Calculated ranges: 3239/2347 Suggested udev rule: # Acer Aspire E5-574 evdev:name:ELAN0501:00 04F3:300B Touchpad:dmi:bvnInsydeCorp.:bvrV1.18:bd05/25/2017:svnAcer:pnAspireE5-574G:pvrVvrChassisVersion:* EVDEV_ABS_00=0:3239:31 EVDEV_ABS_01=0:2347:30 EVDEV_ABS_35=0:3239:31 EVDEV_ABS_36=0:2347:30 edited to a file: /etc/udev/hwdb.d$ cat acer.hwdb # Acer Aspire E5-574 evdev:name:ELAN0501:00 04F3:300B Touchpad:dmi:bvnInsydeCorp.:bvrV1.18:bd05/25/2017:svnAcer:pnAspireE5-574G:pvrVvrChassisVersion:* EVDEV_ABS_00=0:3239:31 EVDEV_ABS_01=0:2347:30 EVDEV_ABS_35=0:3239:31 EVDEV_ABS_36=0:2347:30 and updating the hwdb with the command: systemd-hwdb update After this change not even the mouse buttons works. May you have any suggestions what I can do to fix this problem? Best regards Alexander --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mathias1501 F pulseaudio DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=01471360-bc72-4ec9-b9da-8132988e9bb7 InstallationDate: Installed on 2018-07-21 (19 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180721) MachineType: Acer Aspire E5-574G Package: linux (not installed) ProcEnviron: LANGUAGE= TERM=xterm-256color PATH=(custom, no user) LANG=de_AT.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-31-generic root=/dev/mapper/ACER-btrfs ro rootflags=subvol=@ priority=low quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-31.33-generic 4.15.18 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-31-generic N/A linux-backports-modules-4.15.0-31-generic N/A linux-firmware
[Kernel-packages] [Bug 1786436] Re: test_190_config_have_stack_protector failed on ARM64 Trusty
** Also affects: linux (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Trusty) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1786436 Title: test_190_config_have_stack_protector failed on ARM64 Trusty Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Trusty: Confirmed Bug description: FAIL: test_190_config_have_stack_protector (__main__.KernelSecurityConfigTest) CONFIG_HAVE_CC_STACKPROTECTOR set -- Traceback (most recent call last): File "./test-kernel-security.py", line 2367, in test_190_config_have_stack_protector self.assertKernelConfig(config_option, expected) File "./test-kernel-security.py", line 207, in assertKernelConfig self.assertKernelConfigSet(name) File "./test-kernel-security.py", line 194, in assertKernelConfigSet '%s option was expected to be set in the kernel config' % name) AssertionError: HAVE_CC_STACKPROTECTOR option was expected to be set in the kernel config ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-154-generic 3.13.0-154.204 ProcVersionSignature: User Name 3.13.0-154.204-generic 3.13.11-ckt39 Uname: Linux 3.13.0-154-generic aarch64 AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access /dev/snd/: No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.14.1-0ubuntu3.29 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: Error: [Errno 2] No such file or directory: 'iw' CurrentDmesg: Date: Fri Aug 10 08:28:50 2018 IwConfig: lono wireless extensions. enp1s0no wireless extensions. enp1s0d1 no wireless extensions. Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 PciMultimedia: ProcFB: ProcKernelCmdLine: console=ttyS0,9600n8r ro RelatedPackageVersions: linux-restricted-modules-3.13.0-154-generic N/A linux-backports-modules-3.13.0-154-generic N/A linux-firmware 1.127.24 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1786436/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786619] Re: Cannot able to upgrade from 16.04 to 18.04
You may need to run the following from a terminal: sudo apt-get install -f sudo apt-get clean sudo apt-get update Then re-install the package or updates. If that does not resolve your issue, please mark the bug as "Confirmed" ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1786619 Title: Cannot able to upgrade from 16.04 to 18.04 Status in linux package in Ubuntu: Incomplete Bug description: package linux-headers-4.4.0-131 4.4.0-131.157 failed to install/upgrade: package linux-headers-4.4.0-131 is not ready for configuration cannot configure (current status 'half-installed') Processing triggers for libc-bin (2.23-0ubuntu10) ... dpkg: error processing package linux-headers-4.4.0-131 (--configure): package linux-headers-4.4.0-131 is not ready for configuration cannot configure (current status 'half-installed') Errors were encountered while processing: linux-headers-4.4.0-131 E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-headers-4.4.0-131 4.4.0-131.157 ProcVersionSignature: Ubuntu 4.4.0-131.157-generic 4.4.134 Uname: Linux 4.4.0-131-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.18 AptOrdering: linux-headers-4.4.0-131: Configure NULL: ConfigurePending Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: argha 2096 F pulseaudio /dev/snd/controlC0: argha 2096 F pulseaudio Date: Sat Aug 11 19:54:47 2018 DpkgTerminalLog: dpkg: error processing package linux-headers-4.4.0-131 (--configure): package linux-headers-4.4.0-131 is not ready for configuration cannot configure (current status 'half-installed') ErrorMessage: package linux-headers-4.4.0-131 is not ready for configuration cannot configure (current status 'half-installed') HibernationDevice: RESUME=UUID=cc8a-0f65-4d75-bf10-dd906f85e00b InstallationDate: Installed on 2017-08-12 (363 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 001 Device 003: ID 04f2:b40e Chicony Electronics Co., Ltd HP Truevision HD camera Bus 001 Device 002: ID 8087:8000 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Hewlett-Packard HP 15 Notebook PC PackageArchitecture: all ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-131-generic.efi.signed root=UUID=e95dbb4f-5fb3-4ee3-8ad1-155b711b1a4c ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc N/A SourcePackage: linux Title: package linux-headers-4.4.0-131 4.4.0-131.157 failed to install/upgrade: package linux-headers-4.4.0-131 is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/21/2014 dmi.bios.vendor: Insyde dmi.bios.version: F.18 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 2212 dmi.board.vendor: Hewlett-Packard dmi.board.version: 86.28 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.18:bd05/21/2014:svnHewlett-Packard:pnHP15NotebookPC:pvr0991100600087:rvnHewlett-Packard:rn2212:rvr86.28:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP 15 Notebook PC dmi.product.version: 0991100600087 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786619/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1687274] Re: Boot fails waiting for /dev/disk/by-uuid
** Changed in: linux (Ubuntu) Importance: Undecided => High ** Tags added: kernel-da-key -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1687274 Title: Boot fails waiting for /dev/disk/by-uuid Status in linux package in Ubuntu: Incomplete Bug description: The system is stuck waiting 90 seconds for the /dev/disk/by-uuid/* devices to show up. When dropping me to a shell, they do exist. Forcing the system to fsck (by removing power) makes no difference. After rebooting 1-5 times it suddenly completes booting. So it seems it might be a race condition. = Workaround = If I boot once in recovery mode, then the next boot will mostly complete just fine. OK as a workaround, but a horrible solution. I can even just run `systemctl reboot` from recovery mode - no need to boot fully. Running `reboot`, however, does not work. Attached: working$ cat ls-dev-disk-by-uuid working$ cat journalctl-xb failing$ cat ls-dev-disk-by-uuid failing$ cat journalctl-xb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1687274/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786664] Re: wifi (mwifiex_pcie) stops working undeterministically in 18.04 on Surface Pro 3
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.18 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.18-rc8 ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1786664 Title: wifi (mwifiex_pcie) stops working undeterministically in 18.04 on Surface Pro 3 Status in linux package in Ubuntu: Incomplete Bug description: I am using the mainline kernel on Ubuntu 18.04 on a Surface Pro 3. After a varying amount of time the wifi connection is gone. The driver does not seem to respond anymore to any action invoked by the gnome ui. My only known workaround for this is to reboot. In this state the shutdown process may take several minutes. Version signature: Ubuntu 4.15.0-30.32-generic 4.15.18 lsb_release: Description: Ubuntu 18.04.1 LTS Release: 18.04 logs as attachments are following To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786664/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786415] Re: Repeated Kernel Traces
** Changed in: linux (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1786415 Title: Repeated Kernel Traces Status in linux package in Ubuntu: Invalid Bug description: [27775.520196] [ cut here ] [27775.520198] Unknown pixelformat 0x [27775.520222] WARNING: CPU: 2 PID: 12038 at /build/linux-I4R9hO/linux-4.15.0/drivers/media/v4l2-core/v4l2-ioctl.c:1291 v4l_fill_fmtdesc+0xf41/0x1250 [videodev] [27775.520223] Modules linked in: nf_conntrack_ipv6 nf_defrag_ipv6 xt_tcpudp nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack rfcomm hid_generic uhid algif_hash algif_skcipher af_alg msr ip6table_filter ip6_tables iptable_filter ccm pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) cmac bnep uvcvideo videobuf2_vmalloc videobuf2_memops btusb videobuf2_v4l2 btrtl btbcm videobuf2_core btintel videodev bluetooth media cdc_acm ecdh_generic xfs libcrc32c nls_iso8859_1 arc4 snd_hda_codec_hdmi hid_multitouch intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp dell_smbios_smm dcdbas kvm_intel kvm snd_soc_skl irqbypass snd_soc_skl_ipc crct10dif_pclmul dell_laptop crc32_pclmul snd_hda_ext_core snd_soc_sst_dsp ghash_clmulni_intel snd_soc_sst_ipc pcbc snd_hda_codec_realtek snd_soc_acpi [27775.520261] iwlmvm snd_soc_core snd_hda_codec_generic aesni_intel aes_x86_64 mac80211 crypto_simd glue_helper snd_compress cryptd ac97_bus intel_cstate snd_pcm_dmaengine intel_rapl_perf iwlwifi joydev cfg80211 rtsx_pci_ms memstick input_leds serio_raw dell_smbios_wmi dell_wmi dell_smbios dell_wmi_descriptor wmi_bmof intel_wmi_thunderbolt snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device snd_timer snd idma64 virt_dma soundcore mei_me processor_thermal_device intel_lpss_pci shpchp mei intel_lpss intel_pch_thermal intel_soc_dts_iosf int3400_thermal int3403_thermal intel_hid int340x_thermal_zone acpi_thermal_rel mac_hid tpm_crb sparse_keymap acpi_pad sch_fq_codel parport_pc ppdev sunrpc lp parport ip_tables x_tables autofs4 [27775.520297] rtsx_pci_sdmmc i915 i2c_algo_bit drm_kms_helper syscopyarea sysfillrect psmouse sysimgblt fb_sys_fops nvme drm nvme_core rtsx_pci wmi i2c_hid hid video pinctrl_sunrisepoint [27775.520308] CPU: 2 PID: 12038 Comm: chrome Tainted: GW OE 4.15.0-30-generic #32-Ubuntu [27775.520309] Hardware name: Dell Inc. XPS 13 9370/09DKKT, BIOS 1.4.0 05/25/2018 [27775.520314] RIP: 0010:v4l_fill_fmtdesc+0xf41/0x1250 [videodev] [27775.520315] RSP: 0018:bf6f04e27c30 EFLAGS: 00010282 [27775.520316] RAX: RBX: bf6f04e27d68 RCX: 0006 [27775.520317] RDX: 0007 RSI: 0086 RDI: 9b9cee496490 [27775.520318] RBP: bf6f04e27c40 R08: 0001 R09: 046d [27775.520318] R10: 9b9cd97b1000 R11: R12: 9b9c44a3d700 [27775.520319] R13: c0e44900 R14: 9b9cd97b10c0 R15: 9b9c44a3d700 [27775.520321] FS: 7f4aa2b5eac0() GS:9b9cee48() knlGS: [27775.520321] CS: 0010 DS: ES: CR0: 80050033 [27775.520322] CR2: 56225ac51460 CR3: 0003ebff6004 CR4: 003606e0 [27775.520323] DR0: DR1: DR2: [27775.520324] DR3: DR6: fffe0ff0 DR7: 0400 [27775.520325] Call Trace: [27775.520330] v4l_enum_fmt+0x74/0x110 [videodev] [27775.520334] __video_do_ioctl+0x370/0x380 [videodev] [27775.520337] ? alloc_set_pte+0x25e/0x560 [27775.520339] ? filemap_map_pages+0x36c/0x390 [27775.520343] video_usercopy+0x24d/0x640 [videodev] [27775.520346] ? video_ioctl2+0x20/0x20 [videodev] [27775.520348] ? __handle_mm_fault+0x47b/0x5c0 [27775.520352] video_ioctl2+0x15/0x20 [videodev] [27775.520355] v4l2_ioctl+0xc8/0xf0 [videodev] [27775.520357] do_vfs_ioctl+0xa8/0x630 [27775.520359] ? handle_mm_fault+0xb1/0x1f0 [27775.520361] ? __do_page_fault+0x270/0x4d0 [27775.520363] ? do_sys_open+0x13e/0x2c0 [27775.520365] SyS_ioctl+0x79/0x90 [27775.520368] do_syscall_64+0x73/0x130 [27775.520370] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 [27775.520372] RIP: 0033:0x7f4a9c8205d7 [27775.520372] RSP: 002b:7ffd6a4cbfc8 EFLAGS: 0246 ORIG_RAX: 0010 [27775.520374] RAX: ffda RBX: 7ffd6a4cc180 RCX: 7f4a9c8205d7 [27775.520375] RDX: 7ffd6a4cc200 RSI: c0405602 RDI: 0019 [27775.520375] RBP: 7ffd6a4cc290 R08: R09: 7ffd6a4cbe20 [27775.520376] R10: R11: 0246 R12: 18335e331c00 [27775.520377] R13: 7ffd6a4cc149 R14: R15: 0019 [27775.520378] Code: 30 0f 84 b4 01 00
[Kernel-packages] [Bug 1786713] Re: MODULE_SOFTDEP for crc32c is not working
** Changed in: linux (Ubuntu) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1786713 Title: MODULE_SOFTDEP for crc32c is not working Status in linux package in Ubuntu: Incomplete Bug description: I have a kernel config with Ext4, for which softdep is not working. See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1778265 Ubuntu 18.04. Kernel 4.17.18 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786713/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1784665] Re: mkfs.ext4 over /dev/bcache0 hangs
4.10: Status: OK Comment: Survived 30 minute loop over recreating with no issues. 4.13: Status: OK Comment: Survived 30 minute loop over recreating with no issues. 4.15: Status: FAIL Comment: triggered within less than a minute of the loop. Kernel Trace: [ 122.500943] Oops: [#24] SMP PTI [ 122.501612] Modules linked in: bcache nls_utf8 isofs nls_iso8859_1 ppdev kvm_intel kvm irqbypass parport_pc input_leds parport joydev mac_hid serio_raw sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi virtio_rng 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 psmouse virtio_net virtio_blk virtio_scsi i2c_piix4 pata_acpi floppy [ 122.508306] CPU: 3 PID: 2212 Comm: kworker/3:249 Tainted: G D 4.15.0-041500-generic #201802011154 [ 122.510459] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Ubuntu-1.8.2-1ubuntu1 04/01/2014 [ 122.512541] Workqueue: bcache bch_data_insert_keys [bcache] [ 122.513779] RIP: 0010:__bch_bset_search+0x80/0x470 [bcache] [ 122.515015] RSP: 0018:b49141a83c10 EFLAGS: 00010286 [ 122.516127] RAX: fff6cacc RBX: fff6cacc RCX: [ 122.516947] RDX: b49141a83e18 RSI: 0069 RDI: 8f6a7ad64cc8 [ 122.517768] RBP: b49141a83c70 R08: 0001 R09: 8f6a7ad64ce0 [ 122.518586] R10: 8f6a6735ab80 R11: 00027ec0 R12: b49141a83e18 [ 122.519858] R13: 000400656369 R14: 66643165 R15: 8f6a7ad64ce0 [ 122.521302] FS: () GS:8f6a7fd8() knlGS: [ 122.522272] CS: 0010 DS: ES: CR0: 80050033 [ 122.522969] CR2: 000400656389 CR3: 38fc2000 CR4: 06e0 [ 122.524521] Call Trace: [ 122.525153] ? ttwu_do_activate+0x7a/0x90 [ 122.526147] __bch_btree_iter_init+0x5d/0xc0 [bcache] [ 122.527411] bch_btree_iter_init+0x12/0x20 [bcache] [ 122.528578] bch_btree_map_nodes_recurse+0x93/0x190 [bcache] [ 122.529904] ? __slab_free+0x14d/0x2c0 [ 122.530814] ? bch_btree_insert_check_key+0x1f0/0x1f0 [bcache] [ 122.532331] __bch_btree_map_nodes+0x142/0x1a0 [bcache] [ 122.533685] ? bch_btree_insert_check_key+0x1f0/0x1f0 [bcache] [ 122.534994] bch_btree_insert+0xf9/0x170 [bcache] [ 122.536059] ? wait_woken+0x80/0x80 [ 122.536876] bch_data_insert_keys+0x36/0x130 [bcache] [ 122.538004] process_one_work+0x1ef/0x410 [ 122.538928] worker_thread+0x32/0x410 [ 122.539779] kthread+0x121/0x140 [ 122.540538] ? process_one_work+0x410/0x410 [ 122.541487] ? kthread_create_worker_on_cpu+0x70/0x70 [ 122.542619] ret_from_fork+0x35/0x40 [ 122.543547] Code: 41 08 81 e3 ff ff 0f 00 25 ff ff 0f 00 48 39 d8 48 89 5d d0 0f 85 b6 03 00 00 48 8b 42 08 49 2b 41 10 48 85 c0 0f 89 7c 03 00 00 <49> 8b 45 20 25 ff ff 0f 00 48 39 45 d0 0f 85 c0 03 00 00 48 8b [ 122.546019] RIP: __bch_bset_search+0x80/0x470 [bcache] RSP: b49141a83c10 [ 122.546836] CR2: 000400656389 [ 122.547567] ---[ end trace c539406c76c0edd2 ]--- -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1784665 Title: mkfs.ext4 over /dev/bcache0 hangs Status in linux package in Ubuntu: Confirmed Status in linux source package in Cosmic: Confirmed Bug description: $ cat /proc/version_signature Ubuntu 4.15.0-29.31-generic 4.15.18 $ lsb_release -rd Description: Ubuntu Cosmic Cuttlefish (development branch) Release: 18.10 $ apt-cache policy linux-image-`uname -r` linux-image-4.15.0-29-generic: Installed: 4.15.0-29.31 Candidate: 4.15.0-29.31 Version table: *** 4.15.0-29.31 500 500 http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages 100 /var/lib/dpkg/status 3) mkfs.ext4 /dev/bcache0 returns successful creating an ext4 filesystem on top of a bcache device 4) mkfs.ext4 doesn't return and kernel prints hung process info [ 58.018099] cloud-init[920]: Running command ['mkfs.ext4', '-F', '-L', 'root-fs', '-U', 'f01aec97-9457-11e8-b8d6-525400123401', '/dev/bcache0'] with allowed return codes [0] (capture=True) [ 242.652018] INFO: task kworker/u4:0:5 blocked for more than 120 seconds. [ 242.653767] Tainted: P O 4.15.0-29-generic #31-Ubuntu [ 242.655391] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 242.657397] INFO: task kworker/0:2:410 blocked for more than 120 seconds. [ 242.659126] Tainted: P O 4.15.0-29-generic #31-Ubuntu [ 242.660980] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 242.663000] INFO: task bcache_allocato:2326 blocked for more than 120 seconds. [ 242.664807] Tainted: P O 4.15.0-29-generic #31-Ubuntu [
[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
The hashes are: 63d7e9ca7710792e1603953b0ec14337 linux-image- unsigned-4.15.0-31-generic_4.15.0-31.34~lp1777338_amd64.deb 8cca692f07f9edbb56dec15375bc9979 linux- modules-4.15.0-31-generic_4.15.0-31.34~lp1777338_amd64.deb df24a98ec4769f33a9831a5aaeb9f437 linux-modules- extra-4.15.0-31-generic_4.15.0-31.34~lp1777338_amd64.deb -- You 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: In Progress Status in linux source package in Bionic: In Progress Bug description: 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 1728244] Re: Touchpad stops working after reboot on Apollo Lake
@bbaker6212 Hi, Brad Thank you for quick answer. Touchpad model is HID\ALPS0001. Laptop is Chuwi Lapbook Air 14.1. I tried linux kernel 4.18rc8 with Ubuntu 18.04 today and touchpad didn't work at all there. Could you please guide me on how to make it work? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1728244 Title: Touchpad stops working after reboot on Apollo Lake Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Bug description: On the Jumper EZBook 3 Pro (V4) laptop, using an Apollo Lake N3450 processor, if you install Ubuntu 17.10 (or less) with isorespin and use rEFInd as bootloader (this is the only way to get linux booting on this laptop) everything works out of the box, but after a reboot or two the touchpad stops working. Both in Ubuntu and Windows 10. The only way to restore functionality is to boot from usb key ubuntu 17.10 respined, or disassemble laptop and detach-reattach battery cable. This is mesg | grep i2c_hid: [ 2056.460636] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (27/34) [ 3077.604699] i2c_hid i2c-SYNA3602:00: failed to reset device. [ 3077.605473] dpm_run_callback(): i2c_hid_resume+0x0/0xe0 [i2c_hid] returns -61 [ 3080.468156] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (27/34) uname -rvps Linux 4.10.0-32-generic #36~16.04.1-Ubuntu SMP Wed Aug 9 09:19:02 UTC 2017 x86_64 There has to be a bug in the kernel. Any way to avoid this? To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1728244/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1754949] Re: gnome-shell crashed with SIGSEGV in meta_gpu_kms_apply_crtc_mode() from meta_renderer_native_finish_frame()
Hello Ferdinand, or anyone else affected, Accepted mutter into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mutter/3.28.3-2~ubuntu18.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: mutter (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1754949 Title: gnome-shell crashed with SIGSEGV in meta_gpu_kms_apply_crtc_mode() from meta_renderer_native_finish_frame() Status in gnome-shell package in Ubuntu: Fix Released Status in linux package in Ubuntu: Triaged Status in mutter package in Ubuntu: Fix Released Status in linux source package in Bionic: New Status in mutter source package in Bionic: Fix Committed Bug description: [ Description ] GNome shell crashes after Xorg loggin [ Test case ] From GDM login in a GNOME Ubuntu session (so Xorg). It should start with no issues [ Regression potential ] We were deferencing a NULL pointer while outputting an error. This is pretty safe. Although the session might still not run properly as per a driver issue to be addressed in linux package. --- https://gitlab.gnome.org/GNOME/mutter/issues/70 https://errors.ubuntu.com/problem/16426125ad8d92ae4dc9ce9e89450153b0a8b665 https://salsa.debian.org/gnome-team/mutter/merge_requests/6 --- The crash was reported after booting and logging in to an X.Org session. $ lsb_release -rd Description: Ubuntu Bionic Beaver (development branch) Release: 18.04 $ apt-cache policy gnome-shell gnome-shell: Instalovaná verze: 3.27.92-0ubuntu1 Kandidát: 3.27.92-0ubuntu1 Tabulka verzí: *** 3.27.92-0ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: CrashDistroRelease: Ubuntu 18.04 Package: gnome-shell 3.27.92-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: GNOME-Greeter:GNOME Date: Sun Mar 11 11:08:00 2018 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2017-12-19 (81 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANGUAGE=cs_CZ PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=cs_CZ.UTF-8 SHELL=/bin/false SegvAnalysis: Segfault happened at: 0x7f3fee5d2f17 : mov0x20(%rax),%rcx PC (0x7f3fee5d2f17) ok source "0x20(%rax)" (0x0020) not located in a known VMA region (needed readable region)! destination "%rcx" ok SegvReason: reading NULL VMASignal: 11SourcePackage: gnome-shell StacktraceTop: meta_gpu_kms_apply_crtc_mode () at /usr/lib/x86_64-linux-gnu/libmutter-2.so.0 meta_renderer_native_finish_frame () at /usr/lib/x86_64-linux-gnu/libmutter-2.so.0 () at /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-2.so () at /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-2.so () at /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-2.so Title: gnome-shell crashed with SIGSEGV in meta_gpu_kms_apply_crtc_mode() UpgradeStatus: Upgraded to bionic on 2018-03-05 (5 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1754949/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1774225] Re: netns: unable to follow an interface that moves to another netns
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1774225
Title:
netns: unable to follow an interface that moves to another netns
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Xenial:
In Progress
Status in linux source package in Bionic:
Fix Committed
Bug description:
== SRU Justification ==
6Wind is requesting these three patches. The patches fix a bug that prevents
a user
from following an interface that moves to another netns.
These commits are also needed in Xenial. However, they will be sent in
a separate SRU request due to additional prereq commits being needed for
Xenial.
== Fixes ==
b2d3bcfa26a7 ("net: core: Expose number of link up/down transitions")
c36ac8e23073 ("dev: always advertise the new nsid when the netns iface
changes")
38e01b30563a ("dev: advertise the new ifindex when the netns iface changes")
== Regression Potential ==
Medium due to three patches needed and the changes to core networking.
== 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.
The following upstream patches are missing (v4.16):
6621dd29eb9b ("dev: advertise the new nsid when the netns iface changes")
c36ac8e23073 ("dev: always advertise the new nsid when the netns iface
changes")
38e01b30563a ("dev: advertise the new ifindex when the netns iface changes")
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6621dd29eb9b
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=c36ac8e23073
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=38e01b30563a
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774225/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1770095] Re: Need fix to aacraid driver to prevent panic
** Tags removed: targetmilestone-inin---
** Tags added: targetmilestone-inin1804
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1770095
Title:
Need fix to aacraid driver to prevent panic
Status in The Ubuntu-power-systems project:
Fix Committed
Status in linux package in Ubuntu:
Fix Committed
Status in linux source package in Bionic:
Fix Committed
Status in linux source package in Cosmic:
Fix Committed
Bug description:
== SRU Justification ==
A commit introduced in mainline v4.14-rc1 to aacraid
(b60710ec7d7ab1ca277b458338563ac21b393906) introduced a regression whereby a
panic may happen under certain recovery situations.
This regression is fixed by linux-next commit 7d3af7d96af7.
== Fix ==
7d3af7d96af7 ("scsi: aacraid: Correct hba_send to include iu_type")
== Regression Potential ==
Low. This patch fixes a current regression. It was cc'd to upstream
stable, so it has had additonal 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.
== Comment: #0 - Douglas Miller - 2018-05-08 15:45:13 ==
+++ This bug was initially created as a clone of Bug #167565 +++
A recent commit to aacraid (b60710ec7d7ab1ca277b458338563ac21b393906)
introduced a bug whereby a panic may happen under certain recovery
situations. The following commit fixes that:
https://git.kernel.org/pub/scm/linux/kernel/git/jejb/scsi.git/commit/?h=fixes=7d3af7d96af7b9f51e1ef67b6f4725f545737da2
We need this commit backported to Ubuntu 18.04
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1770095/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1723612] Re: new laptop: Lenovo Y520-15IKBM no wireless networks found
Any outlook when this will be fixed for Ubuntu? I see it is still not there in linux 4.18. Suse LEAP 15 fixed this within 6 weeks after I reported it to Suse. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1723612 Title: new laptop: Lenovo Y520-15IKBM no wireless networks found Status in linux package in Ubuntu: In Progress Bug description: platform/x86: ideapad-laptop: Add Y720-15IKBM to no_hw_rfkill Lenovo Legion Y720-15IKBM is yet another Lenovo model that does not have an hw rfkill switch, resulting in wifi always reported as hard blocked. Please add the model to the list of models without rfkill switch, in module ideapad-laptop ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-37-generic 4.10.0-37.41 ProcVersionSignature: Ubuntu 4.10.0-37.41-generic 4.10.17 Uname: Linux 4.10.0-37-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: loek 2044 F pulseaudio CurrentDesktop: Unity:Unity7 Date: Sat Oct 14 16:14:40 2017 HibernationDevice: RESUME=UUID=4864f7b1-0f01-42de-8c0b-fe93495c315f InstallationDate: Installed on 2017-10-09 (4 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 174f:2414 Syntek Bus 001 Device 002: ID 046d:c52f Logitech, Inc. Unifying Receiver Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80YY ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.10.0-37-generic.efi.signed root=UUID=349aa14b-4edc-478e-9b00-da8d368233f8 ro rootflags=subvol=@ quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.10.0-37-generic N/A linux-backports-modules-4.10.0-37-generic N/A linux-firmware 1.164.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/07/2017 dmi.bios.vendor: LENOVO dmi.bios.version: 5XCN13WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Y520-15IKBM dmi.modalias: dmi:bvnLENOVO:bvr5XCN13WW:bd09/07/2017:svnLENOVO:pn80YY:pvrLenovoY520-15IKBM:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoY520-15IKBM: dmi.product.name: 80YY dmi.product.version: Lenovo Y520-15IKBM dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1723612/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1784659] Re: P9 PMU Events Update #5
** Changed in: linux (Ubuntu) Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) => Canonical Kernel Team (canonical-kernel-team) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1784659 Title: P9 PMU Events Update #5 Status in The Ubuntu-power-systems project: Triaged Status in linux package in Ubuntu: Triaged Bug description: == Comment: #0 - Sukadev Bhattiprolu - 2018-03-13 18:08:25 == ---Problem Description--- There has been some updates to the P9 PMU events list (some events dropped, some events changed linux category). We need to make corresponding updates to the PMU event JSON files in the Linux perf. Submitted a pull request https://lkml.org/lkml/2018/3/13/1428 with Subject line [GIT PULL] Please pull JSON files for POWR9 PMU events Userspace tool common name: perf Userspace rpm: linux-tools The userspace tool has the following bit modes: 64-bit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1784659/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1784659] Re: P9 PMU Events Update #5
** Tags added: p9 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1784659 Title: P9 PMU Events Update #5 Status in The Ubuntu-power-systems project: Triaged Status in linux package in Ubuntu: Triaged Bug description: == Comment: #0 - Sukadev Bhattiprolu - 2018-03-13 18:08:25 == ---Problem Description--- There has been some updates to the P9 PMU events list (some events dropped, some events changed linux category). We need to make corresponding updates to the PMU event JSON files in the Linux perf. Submitted a pull request https://lkml.org/lkml/2018/3/13/1428 with Subject line [GIT PULL] Please pull JSON files for POWR9 PMU events Userspace tool common name: perf Userspace rpm: linux-tools The userspace tool has the following bit modes: 64-bit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1784659/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1785675] Re: Security fix: check if IOMMU page is contained in the pinned physical page
** Changed in: linux (Ubuntu) Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1785675 Title: Security fix: check if IOMMU page is contained in the pinned physical page Status in The Ubuntu-power-systems project: In Progress Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Bug description: == Comment: #0 - Leonardo Augusto Guimaraes Garcia - 2018-08-06 12:27:59 == Please, add the following security fix to the distro kernel: 76fa4975f3ed KVM: PPC: Check if IOMMU page is contained in the pinned physical page Also already available in the 4.14 stable tree: 58113603a4ea KVM: PPC: Check if IOMMU page is contained in the pinned physical page And in the 4.17 stable tree: 970e28cb2c7a KVM: PPC: Check if IOMMU page is contained in the pinned physical page To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1785675/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1785675] Re: Security fix: check if IOMMU page is contained in the pinned physical page
** Changed in: ubuntu-power-systems Status: Triaged => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1785675 Title: Security fix: check if IOMMU page is contained in the pinned physical page Status in The Ubuntu-power-systems project: In Progress Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Bug description: == Comment: #0 - Leonardo Augusto Guimaraes Garcia - 2018-08-06 12:27:59 == Please, add the following security fix to the distro kernel: 76fa4975f3ed KVM: PPC: Check if IOMMU page is contained in the pinned physical page Also already available in the 4.14 stable tree: 58113603a4ea KVM: PPC: Check if IOMMU page is contained in the pinned physical page And in the 4.17 stable tree: 970e28cb2c7a KVM: PPC: Check if IOMMU page is contained in the pinned physical page To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1785675/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1778011] Re: SRU: PRIME Power Saving mode draws too much power
** Merge proposal linked: https://code.launchpad.net/~dgadomski/ubuntu/+source/gdm3/+git/lp1782152/+merge/352976 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1778011 Title: SRU: PRIME Power Saving mode draws too much power Status in gdm3 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in nvidia-prime package in Ubuntu: Fix Released Status in nvidia-settings package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in gdm3 source package in Bionic: In Progress Status in nvidia-graphics-drivers-390 source package in Bionic: In Progress Status in nvidia-prime source package in Bionic: In Progress Status in nvidia-settings source package in Bionic: In Progress Status in ubuntu-drivers-common source package in Bionic: In Progress Bug description: SRU Request: [Impact] Relying on the nouveau driver and on the vga switcheroo (to get around a change in systemd LP: #1777099) caused increased power consumption, and slowed down the switching process. Furthermore, if the main X/Xwayland session was started by Gdm when the nvidia driver was loaded, the session will keep the nvidia module loaded, and prevent the system from switching off the dGPU. Also, the nouveau driver will be loaded, if nvidia is not, and this can cause problems to unsupported NVIDIA GPUs. The solution involves the following changes: 1) Solving the problem in systemd (LP: #1777099) 2) Adding code in gpu-manager and in nvidia-prime to unload the nvidia modules, and to allow the PCI device to sleep. 3) Making a slight change to the current patch in Gdm, used to call the PRIME scripts before and after a Gdm session (so that gpu-manager gets actually called on log out) 4) Adding code in gpu-manager to kill the main X/Xwayland session on log out, if the session is preventing us from unloading the nvidia driver. A new X/Xwayland session will be created after unload the module. 5) Removing the systemd service that loads nouveau from the nvidia packages. [Test Case] 1) Enable the -proposed repository, and install the new "ubuntu-drivers-common", nvidia drivers, nvidia-prime, and gdm3 2) Make sure the nvidia packages are installed, and enable performance mode (if it is already enabled, call "sudo prime-select intel" first): sudo prime-select nvidia 3) Restart your computer and attach your /var/log/gpu-manager.log. see if the system boots correctly. If unsure, please attach your /var/log /gpu-manager.log and /var/log/Xorg.0.log 4) Select power saving mode: sudo prime-select intel 5) Log out and log back in 6) Check if the nvidia driver is still loaded: lsmod | grep nvidia [Regression Potential] Low, as hybrid graphics support does not work correctly, and the changes only affect this use case. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1778011/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1778011] Re: SRU: PRIME Power Saving mode draws too much power
** Merge proposal linked: https://code.launchpad.net/~dgadomski/ubuntu/+source/gdm3/+git/lp1782152/+merge/352973 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1778011 Title: SRU: PRIME Power Saving mode draws too much power Status in gdm3 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in nvidia-prime package in Ubuntu: Fix Released Status in nvidia-settings package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in gdm3 source package in Bionic: In Progress Status in nvidia-graphics-drivers-390 source package in Bionic: In Progress Status in nvidia-prime source package in Bionic: In Progress Status in nvidia-settings source package in Bionic: In Progress Status in ubuntu-drivers-common source package in Bionic: In Progress Bug description: SRU Request: [Impact] Relying on the nouveau driver and on the vga switcheroo (to get around a change in systemd LP: #1777099) caused increased power consumption, and slowed down the switching process. Furthermore, if the main X/Xwayland session was started by Gdm when the nvidia driver was loaded, the session will keep the nvidia module loaded, and prevent the system from switching off the dGPU. Also, the nouveau driver will be loaded, if nvidia is not, and this can cause problems to unsupported NVIDIA GPUs. The solution involves the following changes: 1) Solving the problem in systemd (LP: #1777099) 2) Adding code in gpu-manager and in nvidia-prime to unload the nvidia modules, and to allow the PCI device to sleep. 3) Making a slight change to the current patch in Gdm, used to call the PRIME scripts before and after a Gdm session (so that gpu-manager gets actually called on log out) 4) Adding code in gpu-manager to kill the main X/Xwayland session on log out, if the session is preventing us from unloading the nvidia driver. A new X/Xwayland session will be created after unload the module. 5) Removing the systemd service that loads nouveau from the nvidia packages. [Test Case] 1) Enable the -proposed repository, and install the new "ubuntu-drivers-common", nvidia drivers, nvidia-prime, and gdm3 2) Make sure the nvidia packages are installed, and enable performance mode (if it is already enabled, call "sudo prime-select intel" first): sudo prime-select nvidia 3) Restart your computer and attach your /var/log/gpu-manager.log. see if the system boots correctly. If unsure, please attach your /var/log /gpu-manager.log and /var/log/Xorg.0.log 4) Select power saving mode: sudo prime-select intel 5) Log out and log back in 6) Check if the nvidia driver is still loaded: lsmod | grep nvidia [Regression Potential] Low, as hybrid graphics support does not work correctly, and the changes only affect this use case. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1778011/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1784306] Re: linux-aws: 4.4.0-1064.74 -proposed tracker
Task marked as incomplete for bug 1786729 (execveat03 failed) 4.4.0-1064.74 - aws Regression test CMPL, RTB. Issue to note in x86_64 (aws): libhugetlbfs - 1 failed (brk_near_huge), Killed by signal 1, bad config 3, only spotted on t2.small, passed on the rest ubuntu_kvm_unit_tests - test skipped due to no KVM support ubuntu_ltp_syscalls - execveat03 failed (bug 1786729) msgstress04 failed (1786737) inotify07 failed (bug 1774387), inotify08 (bug 1775784) fanotify07/fanotify08 test timeouted (bug 1775165) fanotify09 timeouted (bug 1775153) Skipped / blacklisted: * ubuntu_ltp * ubuntu_nbd_smoke_test * ubuntu_quota_smoke_test * ubuntu_seccomp * ubuntu_sysdig_smoke_test * ubuntu_zram_smoke_test Note: ubuntu_ltp_syscalls test must be reviewed on the Jenkins server, the hang issue (bug 179) will prevent it from copy the test report ** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => Incomplete ** Changed in: kernel-sru-workflow/regression-testing Assignee: Canonical Kernel Team (canonical-kernel-team) => Po-Hsu Lin (cypressyew) -- 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/1784306 Title: linux-aws: 4.4.0-1064.74 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Incomplete Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Confirmed Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1784306/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1776563] Re: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash
For me the latest 4.18 is the best. AMDGPU PRO is not necessary. Please copy-paste for me the "sensors" output on 4.18 kernel. -- 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/1776563 Title: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash Status in amd: New Status in Linux: Incomplete Status in linux package in Ubuntu: Triaged Status in linux-firmware package in Ubuntu: Confirmed Bug description: CPU: Ryzen 5 2500U VGA: Radeon 535 Notebook: Acer Aspire A315 This is a brand new notebook on the market with Ryzen 5/Radeon. The default kernel of Ubuntu(18.04) hangs at loading with message: tsc: Refined TSC clocksource calibration: 1996.250 MHz clocksource: tsc: mask: 0x max_cycles: (...), max_idle_ns: (...) Soft lockup Using pci=noacpi kernel parameter kernel loads without any problem but my notebook produces more heat than on Win10. If I know right Acer notebooks need ACPI to the correct power management. The same thing happens on mainline 4.17,4.18rc1-2. BIOS upgrade to the latest version: 1.08 hasn't helped This problem has been reported upstream: https://bugzilla.kernel.org/show_bug.cgi?id=200087 The latest correctly working kernel was 4.13.* but the heat problem was present with this too. To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1776563/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786752] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1786752 Title: Reference counter issue in 4.15 (nf_xfrm_me_harder / dst_release) Status in linux package in Ubuntu: Confirmed Bug description: Since upgrading from 14.04 to 18.04, we see very frequent warnings about negative refcnts in dst_release: [ 3117.882227] WARNING: CPU: 6 PID: 0 at /build/linux-I4R9hO/linux-4.15.0/include/net/dst.h:256 nf_xfrm_me_harder+0x127/0x140 [nf_nat] [ 3117.882229] Modules linked in: xt_policy cls_u32 sch_sfq ip_vti ip_tunnel authenc echainiv xfrm6_mode_tunnel xfrm4_mode_tunnel xfrm4_tunnel tunnel4 ipcomp xfrm_ipcomp esp4 ah4 af_key nfnetlink_queue nfnetlink_log sch_htb xt_TPROXY xt_multiport veth nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo br_netfilter bridge overlay macvlan 8021q garp mrp stp llc bonding algif_skcipher af_alg xt_hl ip6t_rt nf_conntrack_ipv6 nf_defrag_ipv6 ip6t_REJECT nf_reject_ipv6 xt_nat ipt_MASQUERADE nf_nat_masquerade_ipv4 dm_crypt iptable_nat nf_nat_ipv4 xt_DSCP xt_dscp xt_mark iptable_mangle xt_limit xt_tcpudp xt_addrtype intel_rapl sb_edac x86_pkg_temp_thermal intel_powerclamp coretemp nf_conntrack_ipv4 nf_defrag_ipv4 kvm_intel xt_conntrack kvm joydev input_leds ipt_REJECT nf_reject_ipv4 ftdi_sio usbserial ipmi_si [ 3117.882265] irqbypass intel_cstate mei_me mei ioatdma acpi_pad intel_rapl_perf shpchp ipmi_devintf ipmi_msghandler acpi_power_meter lpc_ich mac_hid ip6table_filter ip6_tables nf_conntrack_netbios_ns nf_conntrack_broadcast nf_nat_ftp nf_nat nf_conntrack_ftp sch_fq_codel nf_conntrack iptable_filter 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 mgag200 ttm crct10dif_pclmul igb ixgbe crc32_pclmul drm_kms_helper hid_generic ghash_clmulni_intel syscopyarea i2c_algo_bit dca sysfillrect usbhid pcbc sysimgblt fb_sys_fops aesni_intel aes_x86_64 crypto_simd ahci glue_helper ptp hid mxm_wmi cryptd [ 3117.882309] drm libahci megaraid_sas pps_core mdio wmi [ 3117.882315] CPU: 6 PID: 0 Comm: swapper/6 Tainted: GW 4.15.0-30-generic #32-Ubuntu [ 3117.882316] Hardware name: Intel Corporation S2600WT2R/S2600WT2R, BIOS SE5C610.86B.01.01.0022.062820171903 06/28/2017 [ 3117.882319] RIP: 0010:nf_xfrm_me_harder+0x127/0x140 [nf_nat] [ 3117.882320] RSP: 0018:88d77f3839f0 EFLAGS: 00010246 [ 3117.882322] RAX: RBX: 90de4000 RCX: 1924 [ 3117.882323] RDX: RSI: 88d749ae6400 RDI: 88d655e96600 [ 3117.882324] RBP: 88d77f383a68 R08: 88d7493dc000 R09: 0018 [ 3117.882324] R10: 0001 R11: 88e770dedc00 R12: 88d655e96600 [ 3117.882325] R13: 88d77f383ae8 R14: 88d7799ff200 R15: 88d7493dc000 [ 3117.882327] FS: () GS:88d77f38() knlGS: [ 3117.882327] CS: 0010 DS: ES: CR0: 80050033 [ 3117.882328] CR2: ff600400 CR3: 00193de0a002 CR4: 003606e0 [ 3117.882329] DR0: DR1: DR2: [ 3117.882330] DR3: DR6: fffe0ff0 DR7: 0400 [ 3117.882331] Call Trace: [ 3117.882332] [ 3117.882337] ? nf_nat_ipv4_fn+0x15b/0x200 [nf_nat_ipv4] [ 3117.882339] nf_nat_ipv4_out+0xc5/0xe0 [nf_nat_ipv4] [ 3117.882342] iptable_nat_ipv4_out+0x15/0x20 [iptable_nat] [ 3117.882347] nf_hook_slow+0x48/0xc0 [ 3117.882353] ip_output+0xd2/0xe0 [ 3117.882355] ? ip_fragment.constprop.44+0x80/0x80 [ 3117.882357] ip_forward_finish+0x49/0x70 [ 3117.882359] ip_forward+0x366/0x440 [ 3117.882361] ? ip_frag_mem+0x20/0x20 [ 3117.882362] ip_rcv_finish+0x129/0x430 [ 3117.882364] ip_rcv+0x28f/0x3a0 [ 3117.882366] ? inet_del_offload+0x40/0x40 [ 3117.882372] __netif_receive_skb_core+0x432/0xb40 [ 3117.882379] ? handle_edge_irq+0x7c/0x190 [ 3117.882384] ? irq_exit+0x67/0xc0 [ 3117.882391] ? do_IRQ+0x82/0xd0 [ 3117.882393] __netif_receive_skb+0x18/0x60 [ 3117.882395] ? __netif_receive_skb+0x18/0x60 [ 3117.882397] netif_receive_skb_internal+0x37/0xd0 [ 3117.882398] napi_gro_receive+0xc5/0xf0 [ 3117.882407] ixgbe_clean_rx_irq+0x446/0xe30 [ixgbe] [ 3117.882411] ixgbe_poll+0x256/0x710 [ixgbe] [ 3117.882413] ? do_IRQ+0x82/0xd0 [ 3117.882415] net_rx_action+0x140/0x3a0 [ 3117.882418] __do_softirq+0xdf/0x2b2 [ 3117.882419] irq_exit+0xb6/0xc0 [ 3117.882421] do_IRQ+0x82/0xd0 [ 3117.882423] common_interrupt+0x84/0x84 [ 3117.882424] [ 3117.882427] RIP: 0010:cpuidle_enter_state+0xa7/0x2f0 [
[Kernel-packages] [Bug 1786752] Re: Reference counter issue in 4.15 (nf_xfrm_me_harder / dst_release)
** Attachment added: "dmesg" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786752/+attachment/5174664/+files/dmesg.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1786752 Title: Reference counter issue in 4.15 (nf_xfrm_me_harder / dst_release) Status in linux package in Ubuntu: Confirmed Bug description: Since upgrading from 14.04 to 18.04, we see very frequent warnings about negative refcnts in dst_release: [ 3117.882227] WARNING: CPU: 6 PID: 0 at /build/linux-I4R9hO/linux-4.15.0/include/net/dst.h:256 nf_xfrm_me_harder+0x127/0x140 [nf_nat] [ 3117.882229] Modules linked in: xt_policy cls_u32 sch_sfq ip_vti ip_tunnel authenc echainiv xfrm6_mode_tunnel xfrm4_mode_tunnel xfrm4_tunnel tunnel4 ipcomp xfrm_ipcomp esp4 ah4 af_key nfnetlink_queue nfnetlink_log sch_htb xt_TPROXY xt_multiport veth nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo br_netfilter bridge overlay macvlan 8021q garp mrp stp llc bonding algif_skcipher af_alg xt_hl ip6t_rt nf_conntrack_ipv6 nf_defrag_ipv6 ip6t_REJECT nf_reject_ipv6 xt_nat ipt_MASQUERADE nf_nat_masquerade_ipv4 dm_crypt iptable_nat nf_nat_ipv4 xt_DSCP xt_dscp xt_mark iptable_mangle xt_limit xt_tcpudp xt_addrtype intel_rapl sb_edac x86_pkg_temp_thermal intel_powerclamp coretemp nf_conntrack_ipv4 nf_defrag_ipv4 kvm_intel xt_conntrack kvm joydev input_leds ipt_REJECT nf_reject_ipv4 ftdi_sio usbserial ipmi_si [ 3117.882265] irqbypass intel_cstate mei_me mei ioatdma acpi_pad intel_rapl_perf shpchp ipmi_devintf ipmi_msghandler acpi_power_meter lpc_ich mac_hid ip6table_filter ip6_tables nf_conntrack_netbios_ns nf_conntrack_broadcast nf_nat_ftp nf_nat nf_conntrack_ftp sch_fq_codel nf_conntrack iptable_filter 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 mgag200 ttm crct10dif_pclmul igb ixgbe crc32_pclmul drm_kms_helper hid_generic ghash_clmulni_intel syscopyarea i2c_algo_bit dca sysfillrect usbhid pcbc sysimgblt fb_sys_fops aesni_intel aes_x86_64 crypto_simd ahci glue_helper ptp hid mxm_wmi cryptd [ 3117.882309] drm libahci megaraid_sas pps_core mdio wmi [ 3117.882315] CPU: 6 PID: 0 Comm: swapper/6 Tainted: GW 4.15.0-30-generic #32-Ubuntu [ 3117.882316] Hardware name: Intel Corporation S2600WT2R/S2600WT2R, BIOS SE5C610.86B.01.01.0022.062820171903 06/28/2017 [ 3117.882319] RIP: 0010:nf_xfrm_me_harder+0x127/0x140 [nf_nat] [ 3117.882320] RSP: 0018:88d77f3839f0 EFLAGS: 00010246 [ 3117.882322] RAX: RBX: 90de4000 RCX: 1924 [ 3117.882323] RDX: RSI: 88d749ae6400 RDI: 88d655e96600 [ 3117.882324] RBP: 88d77f383a68 R08: 88d7493dc000 R09: 0018 [ 3117.882324] R10: 0001 R11: 88e770dedc00 R12: 88d655e96600 [ 3117.882325] R13: 88d77f383ae8 R14: 88d7799ff200 R15: 88d7493dc000 [ 3117.882327] FS: () GS:88d77f38() knlGS: [ 3117.882327] CS: 0010 DS: ES: CR0: 80050033 [ 3117.882328] CR2: ff600400 CR3: 00193de0a002 CR4: 003606e0 [ 3117.882329] DR0: DR1: DR2: [ 3117.882330] DR3: DR6: fffe0ff0 DR7: 0400 [ 3117.882331] Call Trace: [ 3117.882332] [ 3117.882337] ? nf_nat_ipv4_fn+0x15b/0x200 [nf_nat_ipv4] [ 3117.882339] nf_nat_ipv4_out+0xc5/0xe0 [nf_nat_ipv4] [ 3117.882342] iptable_nat_ipv4_out+0x15/0x20 [iptable_nat] [ 3117.882347] nf_hook_slow+0x48/0xc0 [ 3117.882353] ip_output+0xd2/0xe0 [ 3117.882355] ? ip_fragment.constprop.44+0x80/0x80 [ 3117.882357] ip_forward_finish+0x49/0x70 [ 3117.882359] ip_forward+0x366/0x440 [ 3117.882361] ? ip_frag_mem+0x20/0x20 [ 3117.882362] ip_rcv_finish+0x129/0x430 [ 3117.882364] ip_rcv+0x28f/0x3a0 [ 3117.882366] ? inet_del_offload+0x40/0x40 [ 3117.882372] __netif_receive_skb_core+0x432/0xb40 [ 3117.882379] ? handle_edge_irq+0x7c/0x190 [ 3117.882384] ? irq_exit+0x67/0xc0 [ 3117.882391] ? do_IRQ+0x82/0xd0 [ 3117.882393] __netif_receive_skb+0x18/0x60 [ 3117.882395] ? __netif_receive_skb+0x18/0x60 [ 3117.882397] netif_receive_skb_internal+0x37/0xd0 [ 3117.882398] napi_gro_receive+0xc5/0xf0 [ 3117.882407] ixgbe_clean_rx_irq+0x446/0xe30 [ixgbe] [ 3117.882411] ixgbe_poll+0x256/0x710 [ixgbe] [ 3117.882413] ? do_IRQ+0x82/0xd0 [ 3117.882415] net_rx_action+0x140/0x3a0 [ 3117.882418] __do_softirq+0xdf/0x2b2 [ 3117.882419] irq_exit+0xb6/0xc0 [ 3117.882421] do_IRQ+0x82/0xd0 [ 3117.882423] common_interrupt+0x84/0x84 [ 3117.882424] [ 3117.882427] RIP:
[Kernel-packages] [Bug 1786752] Re: Reference counter issue in 4.15 (nf_xfrm_me_harder / dst_release)
** Attachment added: "version.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786752/+attachment/5174665/+files/version.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1786752 Title: Reference counter issue in 4.15 (nf_xfrm_me_harder / dst_release) Status in linux package in Ubuntu: Confirmed Bug description: Since upgrading from 14.04 to 18.04, we see very frequent warnings about negative refcnts in dst_release: [ 3117.882227] WARNING: CPU: 6 PID: 0 at /build/linux-I4R9hO/linux-4.15.0/include/net/dst.h:256 nf_xfrm_me_harder+0x127/0x140 [nf_nat] [ 3117.882229] Modules linked in: xt_policy cls_u32 sch_sfq ip_vti ip_tunnel authenc echainiv xfrm6_mode_tunnel xfrm4_mode_tunnel xfrm4_tunnel tunnel4 ipcomp xfrm_ipcomp esp4 ah4 af_key nfnetlink_queue nfnetlink_log sch_htb xt_TPROXY xt_multiport veth nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo br_netfilter bridge overlay macvlan 8021q garp mrp stp llc bonding algif_skcipher af_alg xt_hl ip6t_rt nf_conntrack_ipv6 nf_defrag_ipv6 ip6t_REJECT nf_reject_ipv6 xt_nat ipt_MASQUERADE nf_nat_masquerade_ipv4 dm_crypt iptable_nat nf_nat_ipv4 xt_DSCP xt_dscp xt_mark iptable_mangle xt_limit xt_tcpudp xt_addrtype intel_rapl sb_edac x86_pkg_temp_thermal intel_powerclamp coretemp nf_conntrack_ipv4 nf_defrag_ipv4 kvm_intel xt_conntrack kvm joydev input_leds ipt_REJECT nf_reject_ipv4 ftdi_sio usbserial ipmi_si [ 3117.882265] irqbypass intel_cstate mei_me mei ioatdma acpi_pad intel_rapl_perf shpchp ipmi_devintf ipmi_msghandler acpi_power_meter lpc_ich mac_hid ip6table_filter ip6_tables nf_conntrack_netbios_ns nf_conntrack_broadcast nf_nat_ftp nf_nat nf_conntrack_ftp sch_fq_codel nf_conntrack iptable_filter 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 mgag200 ttm crct10dif_pclmul igb ixgbe crc32_pclmul drm_kms_helper hid_generic ghash_clmulni_intel syscopyarea i2c_algo_bit dca sysfillrect usbhid pcbc sysimgblt fb_sys_fops aesni_intel aes_x86_64 crypto_simd ahci glue_helper ptp hid mxm_wmi cryptd [ 3117.882309] drm libahci megaraid_sas pps_core mdio wmi [ 3117.882315] CPU: 6 PID: 0 Comm: swapper/6 Tainted: GW 4.15.0-30-generic #32-Ubuntu [ 3117.882316] Hardware name: Intel Corporation S2600WT2R/S2600WT2R, BIOS SE5C610.86B.01.01.0022.062820171903 06/28/2017 [ 3117.882319] RIP: 0010:nf_xfrm_me_harder+0x127/0x140 [nf_nat] [ 3117.882320] RSP: 0018:88d77f3839f0 EFLAGS: 00010246 [ 3117.882322] RAX: RBX: 90de4000 RCX: 1924 [ 3117.882323] RDX: RSI: 88d749ae6400 RDI: 88d655e96600 [ 3117.882324] RBP: 88d77f383a68 R08: 88d7493dc000 R09: 0018 [ 3117.882324] R10: 0001 R11: 88e770dedc00 R12: 88d655e96600 [ 3117.882325] R13: 88d77f383ae8 R14: 88d7799ff200 R15: 88d7493dc000 [ 3117.882327] FS: () GS:88d77f38() knlGS: [ 3117.882327] CS: 0010 DS: ES: CR0: 80050033 [ 3117.882328] CR2: ff600400 CR3: 00193de0a002 CR4: 003606e0 [ 3117.882329] DR0: DR1: DR2: [ 3117.882330] DR3: DR6: fffe0ff0 DR7: 0400 [ 3117.882331] Call Trace: [ 3117.882332] [ 3117.882337] ? nf_nat_ipv4_fn+0x15b/0x200 [nf_nat_ipv4] [ 3117.882339] nf_nat_ipv4_out+0xc5/0xe0 [nf_nat_ipv4] [ 3117.882342] iptable_nat_ipv4_out+0x15/0x20 [iptable_nat] [ 3117.882347] nf_hook_slow+0x48/0xc0 [ 3117.882353] ip_output+0xd2/0xe0 [ 3117.882355] ? ip_fragment.constprop.44+0x80/0x80 [ 3117.882357] ip_forward_finish+0x49/0x70 [ 3117.882359] ip_forward+0x366/0x440 [ 3117.882361] ? ip_frag_mem+0x20/0x20 [ 3117.882362] ip_rcv_finish+0x129/0x430 [ 3117.882364] ip_rcv+0x28f/0x3a0 [ 3117.882366] ? inet_del_offload+0x40/0x40 [ 3117.882372] __netif_receive_skb_core+0x432/0xb40 [ 3117.882379] ? handle_edge_irq+0x7c/0x190 [ 3117.882384] ? irq_exit+0x67/0xc0 [ 3117.882391] ? do_IRQ+0x82/0xd0 [ 3117.882393] __netif_receive_skb+0x18/0x60 [ 3117.882395] ? __netif_receive_skb+0x18/0x60 [ 3117.882397] netif_receive_skb_internal+0x37/0xd0 [ 3117.882398] napi_gro_receive+0xc5/0xf0 [ 3117.882407] ixgbe_clean_rx_irq+0x446/0xe30 [ixgbe] [ 3117.882411] ixgbe_poll+0x256/0x710 [ixgbe] [ 3117.882413] ? do_IRQ+0x82/0xd0 [ 3117.882415] net_rx_action+0x140/0x3a0 [ 3117.882418] __do_softirq+0xdf/0x2b2 [ 3117.882419] irq_exit+0xb6/0xc0 [ 3117.882421] do_IRQ+0x82/0xd0 [ 3117.882423] common_interrupt+0x84/0x84 [ 3117.882424] [ 3117.882427] RIP:
[Kernel-packages] [Bug 1786752] Re: Reference counter issue in 4.15 (nf_xfrm_me_harder / dst_release)
** Attachment added: "lspci" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786752/+attachment/5174666/+files/lspci-vnvn.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1786752 Title: Reference counter issue in 4.15 (nf_xfrm_me_harder / dst_release) Status in linux package in Ubuntu: Confirmed Bug description: Since upgrading from 14.04 to 18.04, we see very frequent warnings about negative refcnts in dst_release: [ 3117.882227] WARNING: CPU: 6 PID: 0 at /build/linux-I4R9hO/linux-4.15.0/include/net/dst.h:256 nf_xfrm_me_harder+0x127/0x140 [nf_nat] [ 3117.882229] Modules linked in: xt_policy cls_u32 sch_sfq ip_vti ip_tunnel authenc echainiv xfrm6_mode_tunnel xfrm4_mode_tunnel xfrm4_tunnel tunnel4 ipcomp xfrm_ipcomp esp4 ah4 af_key nfnetlink_queue nfnetlink_log sch_htb xt_TPROXY xt_multiport veth nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo br_netfilter bridge overlay macvlan 8021q garp mrp stp llc bonding algif_skcipher af_alg xt_hl ip6t_rt nf_conntrack_ipv6 nf_defrag_ipv6 ip6t_REJECT nf_reject_ipv6 xt_nat ipt_MASQUERADE nf_nat_masquerade_ipv4 dm_crypt iptable_nat nf_nat_ipv4 xt_DSCP xt_dscp xt_mark iptable_mangle xt_limit xt_tcpudp xt_addrtype intel_rapl sb_edac x86_pkg_temp_thermal intel_powerclamp coretemp nf_conntrack_ipv4 nf_defrag_ipv4 kvm_intel xt_conntrack kvm joydev input_leds ipt_REJECT nf_reject_ipv4 ftdi_sio usbserial ipmi_si [ 3117.882265] irqbypass intel_cstate mei_me mei ioatdma acpi_pad intel_rapl_perf shpchp ipmi_devintf ipmi_msghandler acpi_power_meter lpc_ich mac_hid ip6table_filter ip6_tables nf_conntrack_netbios_ns nf_conntrack_broadcast nf_nat_ftp nf_nat nf_conntrack_ftp sch_fq_codel nf_conntrack iptable_filter 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 mgag200 ttm crct10dif_pclmul igb ixgbe crc32_pclmul drm_kms_helper hid_generic ghash_clmulni_intel syscopyarea i2c_algo_bit dca sysfillrect usbhid pcbc sysimgblt fb_sys_fops aesni_intel aes_x86_64 crypto_simd ahci glue_helper ptp hid mxm_wmi cryptd [ 3117.882309] drm libahci megaraid_sas pps_core mdio wmi [ 3117.882315] CPU: 6 PID: 0 Comm: swapper/6 Tainted: GW 4.15.0-30-generic #32-Ubuntu [ 3117.882316] Hardware name: Intel Corporation S2600WT2R/S2600WT2R, BIOS SE5C610.86B.01.01.0022.062820171903 06/28/2017 [ 3117.882319] RIP: 0010:nf_xfrm_me_harder+0x127/0x140 [nf_nat] [ 3117.882320] RSP: 0018:88d77f3839f0 EFLAGS: 00010246 [ 3117.882322] RAX: RBX: 90de4000 RCX: 1924 [ 3117.882323] RDX: RSI: 88d749ae6400 RDI: 88d655e96600 [ 3117.882324] RBP: 88d77f383a68 R08: 88d7493dc000 R09: 0018 [ 3117.882324] R10: 0001 R11: 88e770dedc00 R12: 88d655e96600 [ 3117.882325] R13: 88d77f383ae8 R14: 88d7799ff200 R15: 88d7493dc000 [ 3117.882327] FS: () GS:88d77f38() knlGS: [ 3117.882327] CS: 0010 DS: ES: CR0: 80050033 [ 3117.882328] CR2: ff600400 CR3: 00193de0a002 CR4: 003606e0 [ 3117.882329] DR0: DR1: DR2: [ 3117.882330] DR3: DR6: fffe0ff0 DR7: 0400 [ 3117.882331] Call Trace: [ 3117.882332] [ 3117.882337] ? nf_nat_ipv4_fn+0x15b/0x200 [nf_nat_ipv4] [ 3117.882339] nf_nat_ipv4_out+0xc5/0xe0 [nf_nat_ipv4] [ 3117.882342] iptable_nat_ipv4_out+0x15/0x20 [iptable_nat] [ 3117.882347] nf_hook_slow+0x48/0xc0 [ 3117.882353] ip_output+0xd2/0xe0 [ 3117.882355] ? ip_fragment.constprop.44+0x80/0x80 [ 3117.882357] ip_forward_finish+0x49/0x70 [ 3117.882359] ip_forward+0x366/0x440 [ 3117.882361] ? ip_frag_mem+0x20/0x20 [ 3117.882362] ip_rcv_finish+0x129/0x430 [ 3117.882364] ip_rcv+0x28f/0x3a0 [ 3117.882366] ? inet_del_offload+0x40/0x40 [ 3117.882372] __netif_receive_skb_core+0x432/0xb40 [ 3117.882379] ? handle_edge_irq+0x7c/0x190 [ 3117.882384] ? irq_exit+0x67/0xc0 [ 3117.882391] ? do_IRQ+0x82/0xd0 [ 3117.882393] __netif_receive_skb+0x18/0x60 [ 3117.882395] ? __netif_receive_skb+0x18/0x60 [ 3117.882397] netif_receive_skb_internal+0x37/0xd0 [ 3117.882398] napi_gro_receive+0xc5/0xf0 [ 3117.882407] ixgbe_clean_rx_irq+0x446/0xe30 [ixgbe] [ 3117.882411] ixgbe_poll+0x256/0x710 [ixgbe] [ 3117.882413] ? do_IRQ+0x82/0xd0 [ 3117.882415] net_rx_action+0x140/0x3a0 [ 3117.882418] __do_softirq+0xdf/0x2b2 [ 3117.882419] irq_exit+0xb6/0xc0 [ 3117.882421] do_IRQ+0x82/0xd0 [ 3117.882423] common_interrupt+0x84/0x84 [ 3117.882424] [ 3117.882427] RIP:
[Kernel-packages] [Bug 1786752] [NEW] Reference counter issue in 4.15 (nf_xfrm_me_harder / dst_release)
Public bug reported: Since upgrading from 14.04 to 18.04, we see very frequent warnings about negative refcnts in dst_release: [ 3117.882227] WARNING: CPU: 6 PID: 0 at /build/linux-I4R9hO/linux-4.15.0/include/net/dst.h:256 nf_xfrm_me_harder+0x127/0x140 [nf_nat] [ 3117.882229] Modules linked in: xt_policy cls_u32 sch_sfq ip_vti ip_tunnel authenc echainiv xfrm6_mode_tunnel xfrm4_mode_tunnel xfrm4_tunnel tunnel4 ipcomp xfrm_ipcomp esp4 ah4 af_key nfnetlink_queue nfnetlink_log sch_htb xt_TPROXY xt_multiport veth nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo br_netfilter bridge overlay macvlan 8021q garp mrp stp llc bonding algif_skcipher af_alg xt_hl ip6t_rt nf_conntrack_ipv6 nf_defrag_ipv6 ip6t_REJECT nf_reject_ipv6 xt_nat ipt_MASQUERADE nf_nat_masquerade_ipv4 dm_crypt iptable_nat nf_nat_ipv4 xt_DSCP xt_dscp xt_mark iptable_mangle xt_limit xt_tcpudp xt_addrtype intel_rapl sb_edac x86_pkg_temp_thermal intel_powerclamp coretemp nf_conntrack_ipv4 nf_defrag_ipv4 kvm_intel xt_conntrack kvm joydev input_leds ipt_REJECT nf_reject_ipv4 ftdi_sio usbserial ipmi_si [ 3117.882265] irqbypass intel_cstate mei_me mei ioatdma acpi_pad intel_rapl_perf shpchp ipmi_devintf ipmi_msghandler acpi_power_meter lpc_ich mac_hid ip6table_filter ip6_tables nf_conntrack_netbios_ns nf_conntrack_broadcast nf_nat_ftp nf_nat nf_conntrack_ftp sch_fq_codel nf_conntrack iptable_filter 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 mgag200 ttm crct10dif_pclmul igb ixgbe crc32_pclmul drm_kms_helper hid_generic ghash_clmulni_intel syscopyarea i2c_algo_bit dca sysfillrect usbhid pcbc sysimgblt fb_sys_fops aesni_intel aes_x86_64 crypto_simd ahci glue_helper ptp hid mxm_wmi cryptd [ 3117.882309] drm libahci megaraid_sas pps_core mdio wmi [ 3117.882315] CPU: 6 PID: 0 Comm: swapper/6 Tainted: GW 4.15.0-30-generic #32-Ubuntu [ 3117.882316] Hardware name: Intel Corporation S2600WT2R/S2600WT2R, BIOS SE5C610.86B.01.01.0022.062820171903 06/28/2017 [ 3117.882319] RIP: 0010:nf_xfrm_me_harder+0x127/0x140 [nf_nat] [ 3117.882320] RSP: 0018:88d77f3839f0 EFLAGS: 00010246 [ 3117.882322] RAX: RBX: 90de4000 RCX: 1924 [ 3117.882323] RDX: RSI: 88d749ae6400 RDI: 88d655e96600 [ 3117.882324] RBP: 88d77f383a68 R08: 88d7493dc000 R09: 0018 [ 3117.882324] R10: 0001 R11: 88e770dedc00 R12: 88d655e96600 [ 3117.882325] R13: 88d77f383ae8 R14: 88d7799ff200 R15: 88d7493dc000 [ 3117.882327] FS: () GS:88d77f38() knlGS: [ 3117.882327] CS: 0010 DS: ES: CR0: 80050033 [ 3117.882328] CR2: ff600400 CR3: 00193de0a002 CR4: 003606e0 [ 3117.882329] DR0: DR1: DR2: [ 3117.882330] DR3: DR6: fffe0ff0 DR7: 0400 [ 3117.882331] Call Trace: [ 3117.882332] [ 3117.882337] ? nf_nat_ipv4_fn+0x15b/0x200 [nf_nat_ipv4] [ 3117.882339] nf_nat_ipv4_out+0xc5/0xe0 [nf_nat_ipv4] [ 3117.882342] iptable_nat_ipv4_out+0x15/0x20 [iptable_nat] [ 3117.882347] nf_hook_slow+0x48/0xc0 [ 3117.882353] ip_output+0xd2/0xe0 [ 3117.882355] ? ip_fragment.constprop.44+0x80/0x80 [ 3117.882357] ip_forward_finish+0x49/0x70 [ 3117.882359] ip_forward+0x366/0x440 [ 3117.882361] ? ip_frag_mem+0x20/0x20 [ 3117.882362] ip_rcv_finish+0x129/0x430 [ 3117.882364] ip_rcv+0x28f/0x3a0 [ 3117.882366] ? inet_del_offload+0x40/0x40 [ 3117.882372] __netif_receive_skb_core+0x432/0xb40 [ 3117.882379] ? handle_edge_irq+0x7c/0x190 [ 3117.882384] ? irq_exit+0x67/0xc0 [ 3117.882391] ? do_IRQ+0x82/0xd0 [ 3117.882393] __netif_receive_skb+0x18/0x60 [ 3117.882395] ? __netif_receive_skb+0x18/0x60 [ 3117.882397] netif_receive_skb_internal+0x37/0xd0 [ 3117.882398] napi_gro_receive+0xc5/0xf0 [ 3117.882407] ixgbe_clean_rx_irq+0x446/0xe30 [ixgbe] [ 3117.882411] ixgbe_poll+0x256/0x710 [ixgbe] [ 3117.882413] ? do_IRQ+0x82/0xd0 [ 3117.882415] net_rx_action+0x140/0x3a0 [ 3117.882418] __do_softirq+0xdf/0x2b2 [ 3117.882419] irq_exit+0xb6/0xc0 [ 3117.882421] do_IRQ+0x82/0xd0 [ 3117.882423] common_interrupt+0x84/0x84 [ 3117.882424] [ 3117.882427] RIP: 0010:cpuidle_enter_state+0xa7/0x2f0 [ 3117.882428] RSP: 0018:9e1a46413e68 EFLAGS: 0246 ORIG_RAX: ffda [ 3117.882430] RAX: 88d77f3a2880 RBX: 02d5f0422d24 RCX: 001f [ 3117.882430] RDX: 02d5f0422d24 RSI: fffa51c90e2bb456 RDI: [ 3117.882431] RBP: 9e1a46413ea8 R08: 003c R09: 0007 [ 3117.882432] R10: 9e1a46413e38 R11: 0036 R12: be0a3fb82240 [ 3117.882432] R13: 0001 R14: 90d71c98 R15: [ 3117.882435] ?
[Kernel-packages] [Bug 1762940] Re: Ubuntu 18.04 d-i install screen becomes blurry on Huawei server in EFI boot mode
I have tested with 18.04.1 on Huawei FusionServer 2288 again. The screen blure is same. The kernel of this iso have been update to 4.15.0-29-generic. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1762940 Title: Ubuntu 18.04 d-i install screen becomes blurry on Huawei server in EFI boot mode Status in linux package in Ubuntu: Triaged Status in install-package source package in Bionic: New Status in linux source package in Bionic: Triaged Bug description: For all(as I know) Huawei servers, the vga adapter are embed in the iBMC chips. Those server can install from ISO manually for 16.04.4 and screen display normally. But for 18.04 ( tested both for daily and final beta)version, the install screen is blur. One of tested server is Huawei 2855 v5, the certification link for 16.04 are https://certification.ubuntu.com/hardware/201707-25596/. Below are key difference of dmesg. It seems might related with DRM. 18.04 install screen is blur dmesg ... [2.039009] fb0: EFI VGA frame buffer device ... [4.178058] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [4.191435] [drm] No driver support for vblank timestamp query. [4.209338] checking generic (9000 30) vs hw (0 0) [4.209384] fbcon: hibmcdrmfb (fb1) is primary device [4.209385] fbcon: Remapping primary device, fb1, to tty 1-63 ... [5.357024] hibmc-drm :07:00.0: fb1: hibmcdrmfb frame buffer device [5.380085] [drm] Initialized hibmc 1.0.0 20160828 for :07:00.0 on minor 0 ... [5.636624] vga16fb: initializing [5.636627] vga16fb: mapped to 0x48a7a1d2 [5.636630] checking generic (9000 30) vs hw (a 1) [5.636676] fb2: VGA16 VGA frame buffer device ... 16.04.4 install screen is fine (no screen blur) dmesg ... [2.000419] fb0: EFI VGA frame buffer device [8.795065] vga16fb: initializing [8.795068] vga16fb: mapped to 0x880a [8.795071] checking generic (9800 30) vs hw (a 1) [8.795121] fb1: VGA16 VGA frame buffer device ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762940/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1784281] Re: linux: 4.15.0-31.33 -proposed tracker
Hardware Certification have completed testing this -proposed kernel. No regressions were observed, results are available here: http://people.canonical.com/~hwcert/sru-testing/bionic/4.15.0-31.33 /bionic-proposed-published.html ** Tags added: certification-testing-passed ** Changed in: kernel-sru-workflow/certification-testing Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1784281 Title: linux: 4.15.0-31.33 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Confirmed Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-certification-testing series: Confirmed Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1784292 (linux-azure), bug 1784293 (linux-azure-edge), bug 1784294 (linux-gcp), bug 1784296 (linux-hwe), bug 1784297 (linux-hwe-edge) derivatives: bug 1784283 (linux-raspi2), bug 1784284 (linux-oem), bug 1784285 (linux-aws), bug 1784288 (linux-azure), bug 1784290 (linux-gcp), bug 1784291 (linux-kvm) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1784281/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786740] Re: kvm_pr can't load on power9
*** This bug is a duplicate of bug 1778854 *** https://bugs.launchpad.net/bugs/1778854 This reminds me of a bug I filed actually - rereading history on the old one ... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1786740 Title: kvm_pr can't load on power9 Status in linux package in Ubuntu: New Bug description: Hi, I have run into this and I'm not entirely sure if it is an error or just not supported. I'll file the bug and would ask for a check and answer by the kernel Team and IBM about it. On power you can never load the usual kvm_hv module in a guest. $ sudo modprobe kvm_hv modprobe: ERROR: could not insert 'kvm_hv': No such device That is normal and expected. But on a Power9 system I can neither load kvm_pr which was usually the way to go for nested KVM. $ sudo modprobe kvm_pr modprobe: ERROR: could not insert 'kvm_pr': Input/output error There is no error whatsoever in dmesg when triggering this. From libvirt the guest is defined with all defaults - see http://paste.ubuntu.com/p/2r34SG6pq6/ That gives the guest CPU this guest view: cat /proc/cpuinfo processor : 0 cpu : POWER9 (architected), altivec supported clock : 2134.00MHz revision: 2.2 (pvr 004e 1202) timebase: 51200 platform: pSeries model : IBM pSeries (emulated by qemu) machine : CHRP IBM pSeries (emulated by qemu) MMU : Radix Nothing obvious here, also the module exists and seems normal to me: $ modinfo kvm_pr filename: /lib/modules/4.17.0-6-generic/kernel/arch/powerpc/kvm/kvm-pr.ko alias: devname:kvm alias: char-major-10-232 license:GPL srcversion: 2472883ADEEBC51508B6BF4 depends:kvm intree: Y name: kvm_pr vermagic: 4.17.0-6-generic SMP mod_unload mprofile-kernel relocatable sig_id: PKCS#7 signer: sig_key: sig_hashalgo: md4 signature: 30:82... Current kernel is From Cosmic (as that is what I test for atm): 4.17.0-6-generic If I start the guest with the "least virtual" cpu via I get no difference in /proc/cpuinfo from the guest nor does the problem change. So is there a special constraint to Power9, is it the cosmic kernel, something else - would be great if there would be some advice on this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786740/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786740] [NEW] kvm_pr can't load on power9
*** This bug is a duplicate of bug 1778854 *** https://bugs.launchpad.net/bugs/1778854 Public bug reported: Hi, I have run into this and I'm not entirely sure if it is an error or just not supported. I'll file the bug and would ask for a check and answer by the kernel Team and IBM about it. On power you can never load the usual kvm_hv module in a guest. $ sudo modprobe kvm_hv modprobe: ERROR: could not insert 'kvm_hv': No such device That is normal and expected. But on a Power9 system I can neither load kvm_pr which was usually the way to go for nested KVM. $ sudo modprobe kvm_pr modprobe: ERROR: could not insert 'kvm_pr': Input/output error There is no error whatsoever in dmesg when triggering this. >From libvirt the guest is defined with all defaults - see >http://paste.ubuntu.com/p/2r34SG6pq6/ That gives the guest CPU this guest view: cat /proc/cpuinfo processor : 0 cpu : POWER9 (architected), altivec supported clock : 2134.00MHz revision: 2.2 (pvr 004e 1202) timebase: 51200 platform: pSeries model : IBM pSeries (emulated by qemu) machine : CHRP IBM pSeries (emulated by qemu) MMU : Radix Nothing obvious here, also the module exists and seems normal to me: $ modinfo kvm_pr filename: /lib/modules/4.17.0-6-generic/kernel/arch/powerpc/kvm/kvm-pr.ko alias: devname:kvm alias: char-major-10-232 license:GPL srcversion: 2472883ADEEBC51508B6BF4 depends:kvm intree: Y name: kvm_pr vermagic: 4.17.0-6-generic SMP mod_unload mprofile-kernel relocatable sig_id: PKCS#7 signer: sig_key: sig_hashalgo: md4 signature: 30:82... Current kernel is From Cosmic (as that is what I test for atm): 4.17.0-6-generic If I start the guest with the "least virtual" cpu via I get no difference in /proc/cpuinfo from the guest nor does the problem change. So is there a special constraint to Power9, is it the cosmic kernel, something else - would be great if there would be some advice on this. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1786740 Title: kvm_pr can't load on power9 Status in linux package in Ubuntu: New Bug description: Hi, I have run into this and I'm not entirely sure if it is an error or just not supported. I'll file the bug and would ask for a check and answer by the kernel Team and IBM about it. On power you can never load the usual kvm_hv module in a guest. $ sudo modprobe kvm_hv modprobe: ERROR: could not insert 'kvm_hv': No such device That is normal and expected. But on a Power9 system I can neither load kvm_pr which was usually the way to go for nested KVM. $ sudo modprobe kvm_pr modprobe: ERROR: could not insert 'kvm_pr': Input/output error There is no error whatsoever in dmesg when triggering this. From libvirt the guest is defined with all defaults - see http://paste.ubuntu.com/p/2r34SG6pq6/ That gives the guest CPU this guest view: cat /proc/cpuinfo processor : 0 cpu : POWER9 (architected), altivec supported clock : 2134.00MHz revision: 2.2 (pvr 004e 1202) timebase: 51200 platform: pSeries model : IBM pSeries (emulated by qemu) machine : CHRP IBM pSeries (emulated by qemu) MMU : Radix Nothing obvious here, also the module exists and seems normal to me: $ modinfo kvm_pr filename: /lib/modules/4.17.0-6-generic/kernel/arch/powerpc/kvm/kvm-pr.ko alias: devname:kvm alias: char-major-10-232 license:GPL srcversion: 2472883ADEEBC51508B6BF4 depends:kvm intree: Y name: kvm_pr vermagic: 4.17.0-6-generic SMP mod_unload mprofile-kernel relocatable sig_id: PKCS#7 signer: sig_key: sig_hashalgo: md4 signature: 30:82... Current kernel is From Cosmic (as that is what I test for atm): 4.17.0-6-generic If I start the guest with the "least virtual" cpu via I get no difference in /proc/cpuinfo from the guest nor does the problem change. So is there a special constraint to Power9, is it the cosmic kernel, something else - would be great if there would be some advice on this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786740/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786740] Re: kvm_pr can't load on power9
*** This bug is a duplicate of bug 1778854 *** https://bugs.launchpad.net/bugs/1778854 Yeah, dup'ing ** This bug has been marked a duplicate of bug 1778854 kvm_pr on power9 not loadable -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1786740 Title: kvm_pr can't load on power9 Status in linux package in Ubuntu: New Bug description: Hi, I have run into this and I'm not entirely sure if it is an error or just not supported. I'll file the bug and would ask for a check and answer by the kernel Team and IBM about it. On power you can never load the usual kvm_hv module in a guest. $ sudo modprobe kvm_hv modprobe: ERROR: could not insert 'kvm_hv': No such device That is normal and expected. But on a Power9 system I can neither load kvm_pr which was usually the way to go for nested KVM. $ sudo modprobe kvm_pr modprobe: ERROR: could not insert 'kvm_pr': Input/output error There is no error whatsoever in dmesg when triggering this. From libvirt the guest is defined with all defaults - see http://paste.ubuntu.com/p/2r34SG6pq6/ That gives the guest CPU this guest view: cat /proc/cpuinfo processor : 0 cpu : POWER9 (architected), altivec supported clock : 2134.00MHz revision: 2.2 (pvr 004e 1202) timebase: 51200 platform: pSeries model : IBM pSeries (emulated by qemu) machine : CHRP IBM pSeries (emulated by qemu) MMU : Radix Nothing obvious here, also the module exists and seems normal to me: $ modinfo kvm_pr filename: /lib/modules/4.17.0-6-generic/kernel/arch/powerpc/kvm/kvm-pr.ko alias: devname:kvm alias: char-major-10-232 license:GPL srcversion: 2472883ADEEBC51508B6BF4 depends:kvm intree: Y name: kvm_pr vermagic: 4.17.0-6-generic SMP mod_unload mprofile-kernel relocatable sig_id: PKCS#7 signer: sig_key: sig_hashalgo: md4 signature: 30:82... Current kernel is From Cosmic (as that is what I test for atm): 4.17.0-6-generic If I start the guest with the "least virtual" cpu via I get no difference in /proc/cpuinfo from the guest nor does the problem change. So is there a special constraint to Power9, is it the cosmic kernel, something else - would be great if there would be some advice on this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786740/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786737] [NEW] msgstress04 test in ubuntu_ltp_syscalls failed with X-AWS
Public bug reported: The msgstress test will failed to kill child processes, and leave many processes running after this test has finished. 10:28:07 DEBUG| [stdout] <<>> 10:28:07 DEBUG| [stdout] tag=msgstress04 stime=1533896887 10:28:07 DEBUG| [stdout] cmdline="msgstress04" 10:28:07 DEBUG| [stdout] contacts="" 10:28:07 DEBUG| [stdout] analysis=exit 10:28:07 DEBUG| [stdout] <<>> 10:28:08 DEBUG| [stdout] msgstress040 TINFO : Found 32000 available message queues 10:28:08 DEBUG| [stdout] msgstress040 TINFO : Using upto 16285 pids 10:28:09 DEBUG| [stdout] Fork failure in the second child of child group 188 10:28:09 DEBUG| [stdout] Fork failure in the first child of child group 189 10:28:09 DEBUG| [stdout] Fork failure in the first child of child group 190 10:28:09 DEBUG| [stdout] Fork failure in the first child of child group 191 10:28:09 DEBUG| [stdout] Fork failure in the second child of child group 192 10:28:09 DEBUG| [stdout] Fork failure in the first child of child group 193 10:28:09 DEBUG| [stdout] Fork failure in the first child of child group 194 10:28:09 DEBUG| [stdout] Fork failure in the first child of child group 195 10:28:09 DEBUG| [stdout] Fork failure in the first child of child group 205 10:28:09 DEBUG| [stdout] Fork failure in the first child of child group 237 10:28:09 DEBUG| [stdout] Fork failure in the second child of child group 274 10:28:09 DEBUG| [stdout] Fork failure in the first child of child group 275 10:28:09 DEBUG| [stdout] Fork failure in the first child of child group 276 10:28:09 DEBUG| [stdout] Fork failure in the first child of child group 285 10:28:09 DEBUG| [stdout] Fork failure in the first child of child group 286 10:28:09 DEBUG| [stdout] Fork failure in the first child of child group 287 10:28:09 DEBUG| [stdout] Fork failure in the first child of child group 288 10:28:09 DEBUG| [stdout] Fork failure in the first child of child group 289 10:28:09 DEBUG| [stdout] Fork failure in the first child of child group 290 10:28:09 DEBUG| [stdout] Fork failure in the first child of child group 298 10:28:09 DEBUG| [stdout] Fork failure in the first child of child group 299 10:28:09 DEBUG| [stdout] Fork failure in the first child of child group 301 10:28:09 DEBUG| [stdout] Fork failure in the second child of child group 294 10:28:09 DEBUG| [stdout] Fork failure in the first child of child group 226 10:28:10 DEBUG| [stdout] Fork failure in the first child of child group 335 10:28:11 DEBUG| [stdout] msgstress041 TFAIL : msgstress04.c:220: Child exit status = 1 10:28:11 DEBUG| [stdout] <<>> 10:28:11 DEBUG| [stdout] initiation_status="ok" 10:28:11 DEBUG| [stdout] duration=4 termination_type=exited termination_id=1 corefile=no 10:28:11 DEBUG| [stdout] cutime=23 cstime=14 10:28:11 DEBUG| [stdout] <<>> 10:28:12 DEBUG| [stdout] msgstress041 TBROK : msgstress04.c:365: Kill failed to kill child 0 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-1064-aws 4.4.0-1064.74 ProcVersionSignature: User Name 4.4.0-1064.74-aws 4.4.140 Uname: Linux 4.4.0-1064-aws x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Mon Aug 13 06:32:47 2018 Ec2AMI: ami-529fb82a Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-west-2b Ec2InstanceType: x1e.xlarge Ec2Kernel: unavailable Ec2Ramdisk: unavailable SourcePackage: linux-aws UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubuntu-kernel-tests Importance: Undecided Status: New ** Affects: linux-aws (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug ec2-images package-from-proposed xenial ** Also affects: ubuntu-kernel-tests Importance: Undecided Status: New ** No longer affects: ubuntu-kernel-tests ** Also affects: ubuntu-kernel-tests Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1786737 Title: msgstress04 test in ubuntu_ltp_syscalls failed with X-AWS Status in ubuntu-kernel-tests: New Status in linux-aws package in Ubuntu: New Bug description: The msgstress test will failed to kill child processes, and leave many processes running after this test has finished. 10:28:07 DEBUG| [stdout] <<>> 10:28:07 DEBUG| [stdout] tag=msgstress04 stime=1533896887 10:28:07 DEBUG| [stdout] cmdline="msgstress04" 10:28:07 DEBUG| [stdout] contacts="" 10:28:07 DEBUG| [stdout] analysis=exit 10:28:07 DEBUG| [stdout] <<>> 10:28:08 DEBUG| [stdout] msgstress040 TINFO : Found 32000 available message queues 10:28:08 DEBUG| [stdout] msgstress040 TINFO : Using upto 16285 pids 10:28:09 DEBUG| [stdout] Fork failure in the second child of child group 188 10:28:09 DEBUG| [stdout] Fork failure in the first child of child group 189 10:28:09 DEBUG| [stdout] Fork failure in the first child of child group 190 10:28:09 DEBUG| [stdout]
[Kernel-packages] [Bug 1786729] Re: execveat03 in ubuntu_ltp_syscalls failed on Xenial AWS
** Also affects: ubuntu-kernel-tests
Importance: Undecided
Status: New
** No longer affects: ubuntu-kernel-tests
** Also affects: ubuntu-kernel-tests
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1786729
Title:
execveat03 in ubuntu_ltp_syscalls failed on Xenial AWS
Status in ubuntu-kernel-tests:
New
Status in linux-aws package in Ubuntu:
New
Bug description:
This is a POTENTIAL REGRESSION.
PASSED with 4.4.0-1063-aws
FAILED with 4.4.0-1064-aws in proposed
This is a new test case added 4 days ago.
From the commit message it looks like this is a test case for commit
8db6c34f1dbc:
The regression is introduced from 8db6c34f1dbc ("Introduce v3 namespaced
file capabilities"). Overlayfs and possibly other networking filesystems
unhash the dentry on unlink, fail on this test with above change.
However this commit has been applied in the Xenial AWS kernel
(14985d791) with bug 1778286
This might have something to do with the way how we backport it (the
EINVAL return value is the clue)
<<>>
tag=execveat03 stime=1534135632
cmdline="execveat03"
contacts=""
analysis=exit
<<>>
incrementing stop
tst_test.c:1017: INFO: Timeout per run is 0h 05m 00s
execveat03.c:70: FAIL: execveat() returned unexpected errno: EINVAL
Summary:
passed 0
failed 1
skipped 0
warnings 0
<<>>
initiation_status="ok"
duration=0 termination_type=exited termination_id=1 corefile=no
cutime=0 cstime=0
<<>>
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-1064-aws 4.4.0-1064.74
ProcVersionSignature: User Name 4.4.0-1064.74-aws 4.4.140
Uname: Linux 4.4.0-1064-aws x86_64
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
Date: Mon Aug 13 04:51:09 2018
Ec2AMI: ami-529fb82a
Ec2AMIManifest: (unknown)
Ec2AvailabilityZone: us-west-2b
Ec2InstanceType: x1e.xlarge
Ec2Kernel: unavailable
Ec2Ramdisk: unavailable
SourcePackage: linux-aws
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1786729/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1655280] Re: ISST-LTE:pVM:roselp4:ubuntu 16.04: cp: error reading '/proc/vmcore': Bad address when trying to dump vmcore
** Changed in: ubuntu-power-systems Status: Incomplete => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1655280 Title: ISST-LTE:pVM:roselp4:ubuntu 16.04: cp: error reading '/proc/vmcore': Bad address when trying to dump vmcore Status in The Ubuntu-power-systems project: In Progress Status in linux package in Ubuntu: In Progress Bug description: == Comment: #0 - Ping Tian Han - 2017-01-09 02:51:00 == ---Problem Description--- Vmcore cannot be saved when triggering bug 150353 on roselp4: Copying data : [ 2.0 %] \/usr/sbin/kdump-config: line 591: 5502 Bus error makedumpfile $MAKEDUMP_ARGS $vmcore_file $KDUMP_CORETEMP [ 512.833872] kdump-tools[5450]: * kdump-tools: makedumpfile failed, falling back to 'cp' [ 573.595449] kdump-tools[5450]: cp: error reading '/proc/vmcore': Bad address [ 573.605717] kdump-tools[5450]: * kdump-tools: failed to save vmcore in /var/crash/201701090223 [ 573.765417] kdump-tools[5450]: * running makedumpfile --dump-dmesg /proc/vmcore /var/crash/201701090223/dmesg.201701090223 [ 574.285506] kdump-tools[5450]: The kernel version is not supported. [ 574.285672] kdump-tools[5450]: The makedumpfile operation may be incomplete. [ 574.285767] kdump-tools[5450]: The dmesg log is saved to /var/crash/201701090223/dmesg.201701090223. [ 574.305422] kdump-tools[5450]: makedumpfile Completed. [ 574.315363] kdump-tools[5450]: * kdump-tools: saved dmesg content in /var/crash/201701090223 [ 574.615688] kdump-tools[5450]: Mon, 09 Jan 2017 02:24:26 -0600 [ 574.705384] kdump-tools[5450]: Rebooting. Stopping ifup for ib0... [ OK ] Stopped ifup for ib0. [ 1008.579897] reboot: Restarting system Contact Information = Ping Tian Han/pt...@cn.ibm.com Carrie Mitsuyoshi/carri...@us.ibm.com ---uname output--- Linux roselp4 4.8.0-34-generic #36~16.04.1-Ubuntu SMP Wed Dec 21 18:53:20 UTC 2016 ppc64le ppc64le ppc64le GNU/Linux Machine Type = lpar ---Debugger--- A debugger is not configured ---Steps to Reproduce--- 1. config kdump on roselp4 2. try to trigger bug 150353 *Additional Instructions for Ping Tian Han/pt...@cn.ibm.com Carrie Mitsuyoshi/carri...@us.ibm.com: -Post a private note with access information to the machine that the bug is occuring on. == Comment: #3 - Brahadambal Srinivasan - 2017-01-10 02:42:25 == root@roselp4:~# cat /proc/cmdline BOOT_IMAGE=/boot/vmlinux-4.8.0-34-generic root=UUID=0bcf3431-df8b-499c-9a13-33070f242e0c ro splash quiet crashkernel=384M-:512M root@roselp4:~# dmesg | grep Reser [0.00] Reserving 512MB of memory at 128MB for crashkernel (System RAM: 21760MB) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1655280/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
