[Kernel-packages] [Bug 1752376] Re: Dell Vostro 5568 - Sound device disappears after connecting headphones
ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1654 F pulseaudio CasperVersion: 1.387 DistroRelease: Ubuntu 17.10 LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) MachineType: Dell Inc. Vostro 5568 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13 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.13.0-21-generic N/A linux-backports-modules-4.13.0-21-generic N/A linux-firmware 1.169.1 Tags: artful Uname: Linux 4.13.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 01/31/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.4 dmi.board.name: 0927W0 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.4:bd01/31/2018:svnDellInc.:pnVostro5568:pvr:rvnDellInc.:rn0927W0:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 5568 dmi.sys.vendor: Dell Inc. ** Tags added: apport-collected artful -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1752376 Title: Dell Vostro 5568 - Sound device disappears after connecting headphones Status in linux package in Ubuntu: Incomplete Bug description: With all kernel versions so far tested including mainline v4.15.4 the audio device permanently disappears even after a cold reboot once the headphones have been plugged/unplugged. Looks to be a firmware issue; latest firmware has been installed but issue remains. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752376/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1752376] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1752376/+attachment/5065889/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1752376 Title: Dell Vostro 5568 - Sound device disappears after connecting headphones Status in linux package in Ubuntu: Incomplete Bug description: With all kernel versions so far tested including mainline v4.15.4 the audio device permanently disappears even after a cold reboot once the headphones have been plugged/unplugged. Looks to be a firmware issue; latest firmware has been installed but issue remains. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752376/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1752376] AlsaInfo.txt
apport information ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1752376/+attachment/5065882/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1752376 Title: Dell Vostro 5568 - Sound device disappears after connecting headphones Status in linux package in Ubuntu: Incomplete Bug description: With all kernel versions so far tested including mainline v4.15.4 the audio device permanently disappears even after a cold reboot once the headphones have been plugged/unplugged. Looks to be a firmware issue; latest firmware has been installed but issue remains. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752376/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1752376] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1752376/+attachment/5065893/+files/RfKill.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1752376 Title: Dell Vostro 5568 - Sound device disappears after connecting headphones Status in linux package in Ubuntu: Incomplete Bug description: With all kernel versions so far tested including mainline v4.15.4 the audio device permanently disappears even after a cold reboot once the headphones have been plugged/unplugged. Looks to be a firmware issue; latest firmware has been installed but issue remains. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752376/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1752376] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1752376/+attachment/5065891/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1752376 Title: Dell Vostro 5568 - Sound device disappears after connecting headphones Status in linux package in Ubuntu: Incomplete Bug description: With all kernel versions so far tested including mainline v4.15.4 the audio device permanently disappears even after a cold reboot once the headphones have been plugged/unplugged. Looks to be a firmware issue; latest firmware has been installed but issue remains. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752376/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1752376] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1752376/+attachment/5065887/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1752376 Title: Dell Vostro 5568 - Sound device disappears after connecting headphones Status in linux package in Ubuntu: Incomplete Bug description: With all kernel versions so far tested including mainline v4.15.4 the audio device permanently disappears even after a cold reboot once the headphones have been plugged/unplugged. Looks to be a firmware issue; latest firmware has been installed but issue remains. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752376/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1752376] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1752376/+attachment/5065884/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1752376 Title: Dell Vostro 5568 - Sound device disappears after connecting headphones Status in linux package in Ubuntu: Incomplete Bug description: With all kernel versions so far tested including mainline v4.15.4 the audio device permanently disappears even after a cold reboot once the headphones have been plugged/unplugged. Looks to be a firmware issue; latest firmware has been installed but issue remains. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752376/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1752376] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1752376/+attachment/5065883/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1752376 Title: Dell Vostro 5568 - Sound device disappears after connecting headphones Status in linux package in Ubuntu: Incomplete Bug description: With all kernel versions so far tested including mainline v4.15.4 the audio device permanently disappears even after a cold reboot once the headphones have been plugged/unplugged. Looks to be a firmware issue; latest firmware has been installed but issue remains. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752376/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1752376] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1752376/+attachment/5065895/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1752376 Title: Dell Vostro 5568 - Sound device disappears after connecting headphones Status in linux package in Ubuntu: Incomplete Bug description: With all kernel versions so far tested including mainline v4.15.4 the audio device permanently disappears even after a cold reboot once the headphones have been plugged/unplugged. Looks to be a firmware issue; latest firmware has been installed but issue remains. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752376/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1752376] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1752376/+attachment/5065885/+files/IwConfig.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1752376 Title: Dell Vostro 5568 - Sound device disappears after connecting headphones Status in linux package in Ubuntu: Incomplete Bug description: With all kernel versions so far tested including mainline v4.15.4 the audio device permanently disappears even after a cold reboot once the headphones have been plugged/unplugged. Looks to be a firmware issue; latest firmware has been installed but issue remains. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752376/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1752376] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1752376/+attachment/5065890/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1752376 Title: Dell Vostro 5568 - Sound device disappears after connecting headphones Status in linux package in Ubuntu: Incomplete Bug description: With all kernel versions so far tested including mainline v4.15.4 the audio device permanently disappears even after a cold reboot once the headphones have been plugged/unplugged. Looks to be a firmware issue; latest firmware has been installed but issue remains. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752376/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1752376] JournalErrors.txt
apport information ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1752376/+attachment/5065886/+files/JournalErrors.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1752376 Title: Dell Vostro 5568 - Sound device disappears after connecting headphones Status in linux package in Ubuntu: Incomplete Bug description: With all kernel versions so far tested including mainline v4.15.4 the audio device permanently disappears even after a cold reboot once the headphones have been plugged/unplugged. Looks to be a firmware issue; latest firmware has been installed but issue remains. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752376/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1752376] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1752376/+attachment/5065888/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1752376 Title: Dell Vostro 5568 - Sound device disappears after connecting headphones Status in linux package in Ubuntu: Incomplete Bug description: With all kernel versions so far tested including mainline v4.15.4 the audio device permanently disappears even after a cold reboot once the headphones have been plugged/unplugged. Looks to be a firmware issue; latest firmware has been installed but issue remains. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752376/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1752376] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1752376/+attachment/5065892/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1752376 Title: Dell Vostro 5568 - Sound device disappears after connecting headphones Status in linux package in Ubuntu: Incomplete Bug description: With all kernel versions so far tested including mainline v4.15.4 the audio device permanently disappears even after a cold reboot once the headphones have been plugged/unplugged. Looks to be a firmware issue; latest firmware has been installed but issue remains. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752376/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1752376] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1752376/+attachment/5065894/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1752376 Title: Dell Vostro 5568 - Sound device disappears after connecting headphones Status in linux package in Ubuntu: Incomplete Bug description: With all kernel versions so far tested including mainline v4.15.4 the audio device permanently disappears even after a cold reboot once the headphones have been plugged/unplugged. Looks to be a firmware issue; latest firmware has been installed but issue remains. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752376/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1752376] Re: Dell Vostro 5568 - Sound device disappears after connecting headphones
** 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/1752376 Title: Dell Vostro 5568 - Sound device disappears after connecting headphones Status in linux package in Ubuntu: Confirmed Bug description: With all kernel versions so far tested including mainline v4.15.4 the audio device permanently disappears even after a cold reboot once the headphones have been plugged/unplugged. Looks to be a firmware issue; latest firmware has been installed but issue remains. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752376/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1746988] Comment bridged from LTC Bugzilla
--- Comment From frederic.bar...@fr.ibm.com 2018-03-01 03:55 EDT--- Today is the deadline for new feature submission and I don't see this driver code in the bionic tree. What's needed to make it happen? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1746988 Title: [Ubuntu 18.04 FEAT] OpenCAPI enabling Status in The Ubuntu-power-systems project: Triaged Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: Fix Committed Bug description: [FEATURE] OpenCAPI enabling OpenCAPI is an Open Interface Architecture that allows any microprocessor to attach to * Coherent user-level accelerators and I/O devices * Advanced memories accessible via read/write or user-level DMA semantics * Agnostic to processor architecture This is a feature to enable OpenCapi on Ubuntu 18.04. This is planned to be included in 4.16 and it will need to be backported to 4.15: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1746988/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1741081] Re: zfs-import-cache.service fails on startup
@Richard, thanks for reporting this issue. Re: "I have tested this manually and it works. I can submit a package patch if this is the desired solution." ..please attach a patch and I'll add it to the package. Just to clarify, which releases does this affect? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1741081 Title: zfs-import-cache.service fails on startup Status in zfs-linux package in Ubuntu: In Progress Bug description: I just noticed on my test VM of artful that zfs-import-cache.service does not have a ConditionPathExists=/etc/zfs/zpool.cache. Because of that, it fails on startup, since the cache file does not exist. This line is being deleted by debian/patches/ubuntu-load-zfs-unconditionally.patch. This patch seems to exist per: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1672749 This patch still exists in bionic, so I assume it will be similarly broken. If the goal of the patch is to load the module (and only that), I think it should create a third unit instead: zfs-load-module.service ^^ runs modprobe zfs zfs-import-cache.service & zfs-import-scan.service ^^ per upstream minus modprobe plus Requires=zfs-load-module.service I have tested this manually and it works. I can submit a package patch if this is the desired solution. Interestingly, before this change, zfs-import-scan.service wasn't starting. If started manually, it worked. I had to give it a `systemctl enable zfs-import-scan.service` to create the Wants symlinks. Looking at the zfsutils-linux.postinst, I see the correct boilerplate from dh_systemd, so I'm not sure why this wasn't already done. Can anyone confirm or deny whether zfs-import-scan.service is enabled out-of-the-box on their system? Is the zfs-import-scan.service not starting actually the cause of the original bug? The design is that *either* zfs-import-cache.service or zfs-import-scan.service starts. They both call modprobe zfs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1741081/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1746988] Re: [Ubuntu 18.04 FEAT] OpenCAPI enabling
Hi, Frederic. It's fix committed, which means it's no the master-next branch of the bionic tree. The next release of 4.15 will have these patches. Can you confirm all of them are on the master-next branch? Thank you. Cascardo. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1746988 Title: [Ubuntu 18.04 FEAT] OpenCAPI enabling Status in The Ubuntu-power-systems project: Triaged Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: Fix Committed Bug description: [FEATURE] OpenCAPI enabling OpenCAPI is an Open Interface Architecture that allows any microprocessor to attach to * Coherent user-level accelerators and I/O devices * Advanced memories accessible via read/write or user-level DMA semantics * Agnostic to processor architecture This is a feature to enable OpenCapi on Ubuntu 18.04. This is planned to be included in 4.16 and it will need to be backported to 4.15: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1746988/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1752536] [NEW] i915/kbl_dmc_ver1.bin failed with error -2
Public bug reported: :~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 16.04.4 LTS Release:16.04 Codename: xenial :~$ uname -r 4.4.0-116-generic The problem :~$ dmesg | grep i915 [0.991220] [drm:i915_dump_device_info] i915 device info: gen=9, pciid=0x5902 rev=0x04 flags=need_gfx_hws,is_kabylake,has_fbc,has_hotplug,has_llc,has_ddi,has_fpga_dbg, [0.991711] [drm:i915_gem_init_stolen] Memory reserved for graphics device: 65536K, usable: 64512K [0.992136] [drm:i915_ggtt_init_hw] GMADR size = 256M [0.992137] [drm:i915_ggtt_init_hw] GTT stolen size = 64M [0.992138] [drm:i915_ggtt_init_hw] ppgtt mode: 3 [1.001094] [drm:intel_csr_ucode_init] Loading i915/kbl_dmc_ver1.bin [1.001114] i915_bpo :00:02.0: Direct firmware load for i915/kbl_dmc_ver1.bin failed with error -2 [1.001119] i915_bpo :00:02.0: Failed to load DMC firmware [https://01.org/linuxgraphics/intel-linux-graphics-firmwares], disabling runtime power management. [1.005895] [drm:i915_gem_object_create_stolen_for_preallocated] creating preallocated stolen object: stolen_offset=0, gtt_offset=0, size=408000 [1.005897] [drm:i915_pages_create_for_stolen] offset=0x0, size=4227072 [1.006228] [drm:i915_gem_setup_global_gtt] reserving preallocated space: 0 + 408000 [1.006230] [drm:i915_gem_setup_global_gtt] clearing unused GTT space: [408000, f000] [1.007450] [drm:i915_gem_context_init] LR context support initialized [1.010861] [drm] Initialized i915_bpo 1.6.0 20160425 for :00:02.0 on minor 0 [1.857985] i915_bpo :00:02.0: fb0: inteldrmfb frame buffer device [ 11.248704] snd_hda_intel :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915_bpo]) [ 18.739304] [drm:i915_gem_open] [ 18.739408] [drm:i915_gem_open] [ 18.739484] [drm:i915_gem_open] [ 18.739524] [drm:i915_gem_open] [ 33.631792] [drm:i915_gem_open] [ 35.515257] [drm:i915_gem_open] [ 35.582793] [drm:i915_gem_open] [ 42.823681] [drm:i915_gem_open] [ 47.557725] [drm:i915_audio_component_sync_audio_rate] Not valid for port C [ 47.565183] [drm:i915_audio_component_sync_audio_rate] Not valid for port C [ 47.566992] [drm:i915_audio_component_sync_audio_rate] Not valid for port C [ 47.573099] [drm:i915_audio_component_sync_audio_rate] Not valid for port C [ 47.574721] [drm:i915_audio_component_sync_audio_rate] Not valid for port C [ 47.581074] [drm:i915_audio_component_sync_audio_rate] Not valid for port C [ 960.035670] [drm:i915_audio_component_sync_audio_rate] Not valid for port C [ 960.044499] [drm:i915_audio_component_sync_audio_rate] Not valid for port C [ 960.046373] [drm:i915_audio_component_sync_audio_rate] Not valid for port C [ 960.052451] [drm:i915_audio_component_sync_audio_rate] Not valid for port C [ 960.054246] [drm:i915_audio_component_sync_audio_rate] Not valid for port C [ 960.060454] [drm:i915_audio_component_sync_audio_rate] Not valid for port C [ 969.549771] [drm:i915_gem_open] [ 969.704665] [drm:i915_gem_context_create_ioctl] HW context 1 created [ 969.794654] [drm:i915_gem_context_destroy_ioctl] HW context 1 destroyed [ 1125.305318] [drm:i915_gem_open] [ 1125.328165] [drm:i915_gem_context_create_ioctl] HW context 1 created [ 1125.333583] [drm:i915_gem_context_destroy_ioctl] HW context 1 destroyed [ 1227.799188] [drm:i915_gem_open] [ 1227.806911] [drm:i915_gem_context_create_ioctl] HW context 1 created [ 1227.807865] [drm:i915_gem_context_destroy_ioctl] HW context 1 destroyed [ 1436.623061] [drm:i915_gem_open] [ 1436.629327] [drm:i915_gem_context_create_ioctl] HW context 1 created [ 1436.630138] [drm:i915_gem_context_destroy_ioctl] HW context 1 destroyed [ 1459.597494] [drm:i915_gem_open] [ 1459.603754] [drm:i915_gem_context_create_ioctl] HW context 1 created [ 1459.604550] [drm:i915_gem_context_destroy_ioctl] HW context 1 destroyed ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-firmware 1.157.17 ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98 Uname: Linux 4.4.0-116-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CurrentDesktop: LXDE Date: Thu Mar 1 10:30:27 2018 Dependencies: InstallationDate: Installed on 2016-11-19 (466 days ago) InstallationMedia: PackageArchitecture: all SourcePackage: linux-firmware UpgradeStatus: Upgraded to xenial on 2016-11-20 (465 days ago) ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug linux-firmware xenial -- 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/1752536 Title: i915/kbl_dmc_ver1.bin failed with error -2 Status in linux-firmware package in Ubuntu: New Bug description: :~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 16.04.4 LTS Release: 16
[Kernel-packages] [Bug 1729674] Re: TB16 dock ethernet corrupts data with hw checksum silently failing
** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1729674 Title: TB16 dock ethernet corrupts data with hw checksum silently failing Status in Dell Sputnik: Triaged Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Status in linux source package in Artful: In Progress Status in linux source package in Bionic: Fix Released Status in linux package in Fedora: Confirmed Bug description: It looks like TCP rx and tx checksum offloading is broken on the TB16 dock's ethernet adapter. For example downloading a large file such as the Ubuntu ISO, and then running an md5sum on it yields the incorrect md5sum. This is because rx-checksumming: on tx-checksumming: on and both set to on by default. Running sudo ethtool -K tx off rx off, allows the download to complete correctly. This is very bad since this can cause very bad untrustworthy behavior. This was conducted using an Dell Precision 5520 on Ubuntu 16.04+linux- generic-hwe-16.04-edge. Thank you To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1729674/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1752536] Re: i915/kbl_dmc_ver1.bin failed with error -2 kernel 4.4.0-116-generic
** Summary changed: - i915/kbl_dmc_ver1.bin failed with error -2 + i915/kbl_dmc_ver1.bin failed with error -2 kernel 4.4.0-116-generic ** Summary changed: - i915/kbl_dmc_ver1.bin failed with error -2 kernel 4.4.0-116-generic + i915/kbl_dmc_ver1.bin failed with error -2 package 1.157.17 kernel 4.4.0-116-generic -- 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/1752536 Title: i915/kbl_dmc_ver1.bin failed with error -2 package 1.157.17 kernel 4.4.0-116-generic Status in linux-firmware package in Ubuntu: New Bug description: :~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 16.04.4 LTS Release: 16.04 Codename: xenial :~$ uname -r 4.4.0-116-generic The problem :~$ dmesg | grep i915 [0.991220] [drm:i915_dump_device_info] i915 device info: gen=9, pciid=0x5902 rev=0x04 flags=need_gfx_hws,is_kabylake,has_fbc,has_hotplug,has_llc,has_ddi,has_fpga_dbg, [0.991711] [drm:i915_gem_init_stolen] Memory reserved for graphics device: 65536K, usable: 64512K [0.992136] [drm:i915_ggtt_init_hw] GMADR size = 256M [0.992137] [drm:i915_ggtt_init_hw] GTT stolen size = 64M [0.992138] [drm:i915_ggtt_init_hw] ppgtt mode: 3 [1.001094] [drm:intel_csr_ucode_init] Loading i915/kbl_dmc_ver1.bin [1.001114] i915_bpo :00:02.0: Direct firmware load for i915/kbl_dmc_ver1.bin failed with error -2 [1.001119] i915_bpo :00:02.0: Failed to load DMC firmware [https://01.org/linuxgraphics/intel-linux-graphics-firmwares], disabling runtime power management. [1.005895] [drm:i915_gem_object_create_stolen_for_preallocated] creating preallocated stolen object: stolen_offset=0, gtt_offset=0, size=408000 [1.005897] [drm:i915_pages_create_for_stolen] offset=0x0, size=4227072 [1.006228] [drm:i915_gem_setup_global_gtt] reserving preallocated space: 0 + 408000 [1.006230] [drm:i915_gem_setup_global_gtt] clearing unused GTT space: [408000, f000] [1.007450] [drm:i915_gem_context_init] LR context support initialized [1.010861] [drm] Initialized i915_bpo 1.6.0 20160425 for :00:02.0 on minor 0 [1.857985] i915_bpo :00:02.0: fb0: inteldrmfb frame buffer device [ 11.248704] snd_hda_intel :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915_bpo]) [ 18.739304] [drm:i915_gem_open] [ 18.739408] [drm:i915_gem_open] [ 18.739484] [drm:i915_gem_open] [ 18.739524] [drm:i915_gem_open] [ 33.631792] [drm:i915_gem_open] [ 35.515257] [drm:i915_gem_open] [ 35.582793] [drm:i915_gem_open] [ 42.823681] [drm:i915_gem_open] [ 47.557725] [drm:i915_audio_component_sync_audio_rate] Not valid for port C [ 47.565183] [drm:i915_audio_component_sync_audio_rate] Not valid for port C [ 47.566992] [drm:i915_audio_component_sync_audio_rate] Not valid for port C [ 47.573099] [drm:i915_audio_component_sync_audio_rate] Not valid for port C [ 47.574721] [drm:i915_audio_component_sync_audio_rate] Not valid for port C [ 47.581074] [drm:i915_audio_component_sync_audio_rate] Not valid for port C [ 960.035670] [drm:i915_audio_component_sync_audio_rate] Not valid for port C [ 960.044499] [drm:i915_audio_component_sync_audio_rate] Not valid for port C [ 960.046373] [drm:i915_audio_component_sync_audio_rate] Not valid for port C [ 960.052451] [drm:i915_audio_component_sync_audio_rate] Not valid for port C [ 960.054246] [drm:i915_audio_component_sync_audio_rate] Not valid for port C [ 960.060454] [drm:i915_audio_component_sync_audio_rate] Not valid for port C [ 969.549771] [drm:i915_gem_open] [ 969.704665] [drm:i915_gem_context_create_ioctl] HW context 1 created [ 969.794654] [drm:i915_gem_context_destroy_ioctl] HW context 1 destroyed [ 1125.305318] [drm:i915_gem_open] [ 1125.328165] [drm:i915_gem_context_create_ioctl] HW context 1 created [ 1125.333583] [drm:i915_gem_context_destroy_ioctl] HW context 1 destroyed [ 1227.799188] [drm:i915_gem_open] [ 1227.806911] [drm:i915_gem_context_create_ioctl] HW context 1 created [ 1227.807865] [drm:i915_gem_context_destroy_ioctl] HW context 1 destroyed [ 1436.623061] [drm:i915_gem_open] [ 1436.629327] [drm:i915_gem_context_create_ioctl] HW context 1 created [ 1436.630138] [drm:i915_gem_context_destroy_ioctl] HW context 1 destroyed [ 1459.597494] [drm:i915_gem_open] [ 1459.603754] [drm:i915_gem_context_create_ioctl] HW context 1 created [ 1459.604550] [drm:i915_gem_context_destroy_ioctl] HW context 1 destroyed ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-firmware 1.157.17 ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98 Uname: Linux 4.4.0-116-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CurrentDesktop: LXDE Date: Thu Mar 1 10:30:27 2018 De
[Kernel-packages] [Bug 1750245] Re: i915 kbl_guc_ver9_14.bin does not load
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-firmware (Ubuntu) Status: New => Confirmed -- 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/1750245 Title: i915 kbl_guc_ver9_14.bin does not load Status in linux-firmware package in Ubuntu: Confirmed Bug description: The provided i915/kbl_guc_ver9_14.bin does not load when configured to do so . If the file is replaced by manually installing with the included script from 01.org, it loads properly: https://01.org/linuxgraphics/downloads/kabylake-guc-9.14 Before: GuC firmware status: path: i915/kbl_guc_ver9_14.bin fetch: FAIL load: NONE version wanted: 9.14 version found: 0.0 header: offset is 0; size = 0 uCode: offset is 0; size = 0 RSA: offset is 0; size = 0 After: GuC firmware status: path: i915/kbl_guc_ver9_14.bin fetch: SUCCESS load: SUCCESS version wanted: 9.14 version found: 9.14 header: offset is 0; size = 128 uCode: offset is 128; size = 142272 RSA: offset is 142400; size = 256 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1750245/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1750937] Re: 4.4.0-116 Kernel update on 2/21 breaks Nvidia drivers (on 14.04 and 16.04)
Same here error with edvi's DisplayLinkManager process to get a displaylink screen from a USB 3.0 hub/docking station like https://www.anker.com/store/USB-3.0-Docking-Station/68ANDOCKS-BA went back to 4.4.0-112 to work. Will wait future 4.4.0-(>116) kernel to retry. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1750937 Title: 4.4.0-116 Kernel update on 2/21 breaks Nvidia drivers (on 14.04 and 16.04) Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-384 package in Ubuntu: Confirmed Status in xorg package in Ubuntu: Confirmed Bug description: Running fine with nvidia-384 until this kernel update came along. When booted into the new kernel, got super low resolution and nvidia- settings was missing most of its functionality - could not change resolution. Rebooted into 4.4.0-112 kernel and all was well. The root cause of the problem has been found to be installing the -116 kernel without a sufficiently updated version of gcc. In my case, my system received the gcc update AFTER the kernel update. Uninstalling the -116 kernel and reinstalling it with the updated version of gcc solved the problem for me. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 4.4.0-112.135~14.04.1-generic 4.4.98 Uname: Linux 4.4.0-112-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 384.111 Tue Dec 19 23:51:45 PST 2017 GCC version: gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3) ApportVersion: 2.14.1-0ubuntu3.27 Architecture: amd64 CurrentDesktop: LXDE Date: Wed Feb 21 19:23:39 2018 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 4.4.0-112-generic, x86_64: installed bbswitch, 0.7, 4.4.0-116-generic, x86_64: installed nvidia-384, 384.111, 4.4.0-112-generic, x86_64: installed nvidia-384, 384.111, 4.4.0-116-generic, x86_64: installed GraphicsCard: NVIDIA Corporation Device [10de:1c82] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. Device [3842:6253] InstallationDate: Installed on 2015-03-03 (1086 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) MachineType: ASUSTeK COMPUTER INC. M11AD ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic root=UUID=5a88d2a1-0a24-415b-adc2-28435b13248a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/15/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0302 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M11AD 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.:bvr0302:bd08/15/2013:svnASUSTeKCOMPUTERINC.:pnM11AD:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnM11AD:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: M11AD dmi.product.version: System Version dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 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: Wed Feb 21 18:48:14 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.3-1ubuntu2.3~trusty4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1750937/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1747855] Re: test_140_kernel_modules_not_tainted in ubuntu_qrt_kernel_security failed on Trusty ARM64
** Summary changed:
- test_140_kernel_modules_not_tainted in ubuntu_qrt_kernel_security failed on
Trusty ARM64 Edit
+ test_140_kernel_modules_not_tainted in ubuntu_qrt_kernel_security failed on
Trusty ARM64
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1747855
Title:
test_140_kernel_modules_not_tainted in ubuntu_qrt_kernel_security
failed on Trusty ARM64
Status in QA Regression Testing:
New
Status in linux package in Ubuntu:
Confirmed
Bug description:
This was reported in bug 163
I think it's better it tear it down into pieces.
FAIL: test_140_kernel_modules_not_tainted (__main__.KernelSecurityTest)
kernel modules are not marked with a taint flag (especially 'E' for
TAINT_UNSIGNED_MODULE)
--
Traceback (most recent call last):
File "./test-kernel-security.py", line 1727, in
test_140_kernel_modules_not_tainted
self.fail('Module \'%s\' is tainted: %s' % (fields[0], last_field))
AssertionError: Module 'signpost' is tainted: (OX)
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-141-generic 3.13.0-141.190
ProcVersionSignature: User Name 3.13.0-141.190-generic 3.13.11-ckt39
Uname: Linux 3.13.0-141-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.27
Architecture: arm64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
CRDA: Error: [Errno 2] No such file or directory: 'iw'
Date: Wed Feb 7 07:21:29 2018
Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize
libusb: -99
PciMultimedia:
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB:
ProcKernelCmdLine: console=ttyS0,9600n8r ro
RelatedPackageVersions:
linux-restricted-modules-3.13.0-141-generic N/A
linux-backports-modules-3.13.0-141-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/qa-regression-testing/+bug/1747855/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1747853] Re: test_082_stack_guard_kernel in ubuntu_qrt_kernel_security failed on Trusty ARM64
** Summary changed: - test_082_stack_guard_kernel in ubuntu_qrt_kernel_security failed on Trusty ARM64 Edit + test_082_stack_guard_kernel in ubuntu_qrt_kernel_security failed on Trusty ARM64 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1747853 Title: test_082_stack_guard_kernel in ubuntu_qrt_kernel_security failed on Trusty ARM64 Status in QA Regression Testing: New Status in linux package in Ubuntu: Confirmed Bug description: This was reported in bug 163 I think it's better it tear it down into pieces. FAIL: test_082_stack_guard_kernel (__main__.KernelSecurityTest) Kernel stack guard -- Traceback (most recent call last): File "./test-kernel-security.py", line 948, in test_082_stack_guard_kernel self.assertEqual(expected, ' UND __stack_chk_fail\n' in out, '__stack_chk_fail missing from kernel (tested befs.ko)') AssertionError: __stack_chk_fail missing from kernel (tested befs.ko) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-141-generic 3.13.0-141.190 ProcVersionSignature: User Name 3.13.0-141.190-generic 3.13.11-ckt39 Uname: Linux 3.13.0-141-generic aarch64 NonfreeKernelModules: signpost 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.27 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: Error: [Errno 2] No such file or directory: 'iw' CurrentDmesg: Date: Wed Feb 7 07:08:00 2018 Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: console=ttyS0,9600n8r ro RelatedPackageVersions: linux-restricted-modules-3.13.0-141-generic N/A linux-backports-modules-3.13.0-141-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/qa-regression-testing/+bug/1747853/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1752536] Re: i915/kbl_dmc_ver1.bin failed with error -2 package 1.157.17 kernel 4.4.0-116-generic
** Tags added: i915 intel -- 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/1752536 Title: i915/kbl_dmc_ver1.bin failed with error -2 package 1.157.17 kernel 4.4.0-116-generic Status in linux-firmware package in Ubuntu: New Bug description: :~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 16.04.4 LTS Release: 16.04 Codename: xenial :~$ uname -r 4.4.0-116-generic The problem :~$ dmesg | grep i915 [0.991220] [drm:i915_dump_device_info] i915 device info: gen=9, pciid=0x5902 rev=0x04 flags=need_gfx_hws,is_kabylake,has_fbc,has_hotplug,has_llc,has_ddi,has_fpga_dbg, [0.991711] [drm:i915_gem_init_stolen] Memory reserved for graphics device: 65536K, usable: 64512K [0.992136] [drm:i915_ggtt_init_hw] GMADR size = 256M [0.992137] [drm:i915_ggtt_init_hw] GTT stolen size = 64M [0.992138] [drm:i915_ggtt_init_hw] ppgtt mode: 3 [1.001094] [drm:intel_csr_ucode_init] Loading i915/kbl_dmc_ver1.bin [1.001114] i915_bpo :00:02.0: Direct firmware load for i915/kbl_dmc_ver1.bin failed with error -2 [1.001119] i915_bpo :00:02.0: Failed to load DMC firmware [https://01.org/linuxgraphics/intel-linux-graphics-firmwares], disabling runtime power management. [1.005895] [drm:i915_gem_object_create_stolen_for_preallocated] creating preallocated stolen object: stolen_offset=0, gtt_offset=0, size=408000 [1.005897] [drm:i915_pages_create_for_stolen] offset=0x0, size=4227072 [1.006228] [drm:i915_gem_setup_global_gtt] reserving preallocated space: 0 + 408000 [1.006230] [drm:i915_gem_setup_global_gtt] clearing unused GTT space: [408000, f000] [1.007450] [drm:i915_gem_context_init] LR context support initialized [1.010861] [drm] Initialized i915_bpo 1.6.0 20160425 for :00:02.0 on minor 0 [1.857985] i915_bpo :00:02.0: fb0: inteldrmfb frame buffer device [ 11.248704] snd_hda_intel :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915_bpo]) [ 18.739304] [drm:i915_gem_open] [ 18.739408] [drm:i915_gem_open] [ 18.739484] [drm:i915_gem_open] [ 18.739524] [drm:i915_gem_open] [ 33.631792] [drm:i915_gem_open] [ 35.515257] [drm:i915_gem_open] [ 35.582793] [drm:i915_gem_open] [ 42.823681] [drm:i915_gem_open] [ 47.557725] [drm:i915_audio_component_sync_audio_rate] Not valid for port C [ 47.565183] [drm:i915_audio_component_sync_audio_rate] Not valid for port C [ 47.566992] [drm:i915_audio_component_sync_audio_rate] Not valid for port C [ 47.573099] [drm:i915_audio_component_sync_audio_rate] Not valid for port C [ 47.574721] [drm:i915_audio_component_sync_audio_rate] Not valid for port C [ 47.581074] [drm:i915_audio_component_sync_audio_rate] Not valid for port C [ 960.035670] [drm:i915_audio_component_sync_audio_rate] Not valid for port C [ 960.044499] [drm:i915_audio_component_sync_audio_rate] Not valid for port C [ 960.046373] [drm:i915_audio_component_sync_audio_rate] Not valid for port C [ 960.052451] [drm:i915_audio_component_sync_audio_rate] Not valid for port C [ 960.054246] [drm:i915_audio_component_sync_audio_rate] Not valid for port C [ 960.060454] [drm:i915_audio_component_sync_audio_rate] Not valid for port C [ 969.549771] [drm:i915_gem_open] [ 969.704665] [drm:i915_gem_context_create_ioctl] HW context 1 created [ 969.794654] [drm:i915_gem_context_destroy_ioctl] HW context 1 destroyed [ 1125.305318] [drm:i915_gem_open] [ 1125.328165] [drm:i915_gem_context_create_ioctl] HW context 1 created [ 1125.333583] [drm:i915_gem_context_destroy_ioctl] HW context 1 destroyed [ 1227.799188] [drm:i915_gem_open] [ 1227.806911] [drm:i915_gem_context_create_ioctl] HW context 1 created [ 1227.807865] [drm:i915_gem_context_destroy_ioctl] HW context 1 destroyed [ 1436.623061] [drm:i915_gem_open] [ 1436.629327] [drm:i915_gem_context_create_ioctl] HW context 1 created [ 1436.630138] [drm:i915_gem_context_destroy_ioctl] HW context 1 destroyed [ 1459.597494] [drm:i915_gem_open] [ 1459.603754] [drm:i915_gem_context_create_ioctl] HW context 1 created [ 1459.604550] [drm:i915_gem_context_destroy_ioctl] HW context 1 destroyed ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-firmware 1.157.17 ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98 Uname: Linux 4.4.0-116-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CurrentDesktop: LXDE Date: Thu Mar 1 10:30:27 2018 Dependencies: InstallationDate: Installed on 2016-11-19 (466 days ago) InstallationMedia: PackageArchitecture: all SourcePackage: linux-firmware UpgradeStatus: Upgraded to xenial on 2016-11-20 (465 days ago) To manage notifications about this bug go to: https://bugs.launch
[Kernel-packages] [Bug 1712038] Re: ubuntu_qrt_kernel_security test_060_nx should be skipped on Trusty ARM64
** Summary changed: - ubuntu_qrt_kernel_security test_060_nx failed on Trusty ARM64 + ubuntu_qrt_kernel_security test_060_nx should be skipped on Trusty ARM64 ** Description changed: - FAIL: test_060_nx (__main__.KernelSecurityTest) - NX bit is working - -- - Traceback (most recent call last): -File "./test-kernel-security.py", line 460, in test_060_nx - self.assertShellExitEquals(expected, ["./nx-test", "data"]) -File "/home/ubuntu/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/testlib.py", line 1134, in assertShellExitEquals - self.assertEqual(expected, rc, msg + result + report) - AssertionError: Got exit code -11, expected 0 - Command: './nx-test', 'data' - Output: - rodata:0x4010c0 - data: 0x4120a8 - bss: 0x4220c8 - brk: 0x20de1010 - rw:0x7f833a1000 - rwx: 0x7f833a - stack: 0x7fdd19bfd8 - Dump of /proc/self/maps: - 0040-00402000 r-xp 08:02 10096524 /home/ubuntu/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/kernel-security/nx/nx-test - 00411000-00412000 r--p 1000 08:02 10096524 /home/ubuntu/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/kernel-security/nx/nx-test - 00412000-00413000 rw-p 2000 08:02 10096524 /home/ubuntu/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/kernel-security/nx/nx-test - 00413000-00423000 rw-p 00:00 0 - 20de1000-20e03000 rw-p 00:00 0 [heap] - 7f8320c000-7f8322c000 rw-p 00:00 0 - 7f8322c000-7f8335f000 r-xp 08:02 4718846 /lib/aarch64-linux-gnu/libc-2.19.so - 7f8335f000-7f8336f000 ---p 00133000 08:02 4718846 /lib/aarch64-linux-gnu/libc-2.19.so - 7f8336f000-7f83373000 r--p 00133000 08:02 4718846 /lib/aarch64-linux-gnu/libc-2.19.so - 7f83373000-7f83375000 rw-p 00137000 08:02 4718846 /lib/aarch64-linux-gnu/libc-2.19.so - 7f83375000-7f83379000 rw-p 00:00 0 - 7f83379000-7f83395000 r-xp 08:02 4718835 /lib/aarch64-linux-gnu/ld-2.19.so - 7f83399000-7f8339b000 rw-p 00:00 0 - 7f833a-7f833a1000 rwxp 00:00 0 - 7f833a1000-7f833a2000 rw-p 00:00 0 - 7f833a2000-7f833a4000 r-xp 00:00 0 [vdso] - 7f833a4000-7f833a5000 r--p 0001b000 08:02 4718835 /lib/aarch64-linux-gnu/ld-2.19.so - 7f833a5000-7f833a7000 rw-p 0001c000 08:02 4718835 /lib/aarch64-linux-gnu/ld-2.19.so - 7fdd17c000-7fdd19d000 rw-p 00:00 0 [stack] - Attempting to execute function at 0x4120a8 - If this program seg-faults, the region was enforced as non-executable... + From the error output, this bug was marked as Failed, instead of being + skipped: + + NX bit is working ... (skipped: ARM64 older than 4.4 has + READ_IMPLIES_EXEC personality set) FAIL + + FAIL: test_060_nx (__main__.KernelSecurityTest) + NX bit is working + -- + Traceback (most recent call last): + File "./test-kernel-security.py", line 460, in test_060_nx + self.assertShellExitEquals(expected, ["./nx-test", "data"]) + File "/home/ubuntu/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/testlib.py", line 1134, in assertShellExitEquals + self.assertEqual(expected, rc, msg + result + report) + AssertionError: Got exit code -11, expected 0 + Command: './nx-test', 'data' + Output: + rodata:0x4010c0 + data: 0x4120a8 + bss: 0x4220c8 + brk: 0x20de1010 + rw:0x7f833a1000 + rwx: 0x7f833a + stack: 0x7fdd19bfd8 + Dump of /proc/self/maps: + 0040-00402000 r-xp 08:02 10096524 /home/ubuntu/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/kernel-security/nx/nx-test + 00411000-00412000 r--p 1000 08:02 10096524 /home/ubuntu/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/kernel-security/nx/nx-test + 00412000-00413000 rw-p 2000 08:02 10096524 /home/ubuntu/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/kernel-security/nx/nx-test + 00413000-00423000 rw-p 00:00 0 + 20de1000-20e03000 rw-p 00:00 0 [heap] + 7f8320c000-7f8322c000 rw-p 00:00 0 + 7f8322c000-7f8335f000 r-xp 08:02 4718846 /lib/aarch64-linux-gnu/libc-2.19.so + 7f8335f000-7f8336f000 ---p 00133000 08:02 4718846 /lib/aarch64-linux-gnu/libc-2
[Kernel-packages] [Bug 1747852] Re: test_072_strict_devmem in ubuntu_qrt_kernel_security should be skipped on Trusty ARM64
** Summary changed: - test_072_strict_devmem in ubuntu_qrt_kernel_security failed on Trusty ARM64 + test_072_strict_devmem in ubuntu_qrt_kernel_security should be skipped on Trusty ARM64 ** Description changed: This was reported in bug 163 I think it's better it tear it down into pieces. - FAIL: test_072_strict_devmem (__main__.KernelSecurityTest) - /dev/mem unreadable for kernel memory - -- - Traceback (most recent call last): -File "./test-kernel-security.py", line 766, in test_072_strict_devmem - self.assertTrue(rc in expected, 'exit code: %d (wanted %s). Output:\n%s' % (rc, ", ".join(["%d" % (x) for x in expected]), output)) - AssertionError: exit code: 7 (wanted 4). Output: -48-4000901d13 : Kernel code - 0x48 ... readable - 0x800010 ... missing (EFAULT), ran off end of physical memory? - 0x4fef98f540 ... 0xfeedface - FAIL: scanned memory without EPERMs, and can read actual values + From the error message, it looks like this test should be skipped on + Trusty 3.13 kernel: + + dev/mem unreadable for kernel memory ... (using 0x4fab5a72c0) (skipped: + only 3.16 and later for ARM64) (exit code 7) FAIL + + FAIL: test_072_strict_devmem (__main__.KernelSecurityTest) + /dev/mem unreadable for kernel memory + -- + Traceback (most recent call last): + File "./test-kernel-security.py", line 766, in test_072_strict_devmem + self.assertTrue(rc in expected, 'exit code: %d (wanted %s). Output:\n%s' % (rc, ", ".join(["%d" % (x) for x in expected]), output)) + AssertionError: exit code: 7 (wanted 4). Output: + 48-4000901d13 : Kernel code + 0x48 ... readable + 0x800010 ... missing (EFAULT), ran off end of physical memory? + 0x4fef98f540 ... 0xfeedface + FAIL: scanned memory without EPERMs, and can read actual values ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-141-generic 3.13.0-141.190 ProcVersionSignature: User Name 3.13.0-141.190-generic 3.13.11-ckt39 Uname: Linux 3.13.0-141-generic aarch64 NonfreeKernelModules: signpost 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.27 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: Error: [Errno 2] No such file or directory: 'iw' CurrentDmesg: - + Date: Wed Feb 7 07:06:33 2018 Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 PciMultimedia: - + ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash ProcFB: - + ProcKernelCmdLine: console=ttyS0,9600n8r ro RelatedPackageVersions: - linux-restricted-modules-3.13.0-141-generic N/A - linux-backports-modules-3.13.0-141-generic N/A - linux-firmware 1.127.24 + linux-restricted-modules-3.13.0-141-generic N/A + linux-backports-modules-3.13.0-141-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) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1747852 Title: test_072_strict_devmem in ubuntu_qrt_kernel_security should be skipped on Trusty ARM64 Status in QA Regression Testing: New Status in linux package in Ubuntu: Confirmed Bug description: This was reported in bug 163 I think it's better it tear it down into pieces. From the error message, it looks like this test should be skipped on Trusty 3.13 kernel: dev/mem unreadable for kernel memory ... (using 0x4fab5a72c0) (skipped: only 3.16 and later for ARM64) (exit code 7) FAIL FAIL: test_072_strict_devmem (__main__.KernelSecurityTest) /dev/mem unreadable for kernel memory -- Traceback (most recent call last): File "./test-kernel-security.py", line 766, in test_072_strict_devmem self.assertTrue(rc in expected, 'exit code: %d (wanted %s). Output:\n%s' % (rc, ", ".join(["%d" % (x) for x in expected]), output)) AssertionError: exit code: 7 (wanted 4). Output: 48-4000901d13 : Kernel code 0x48 ... readable 0x800010 ... missing (EFAULT), ran off end of physical memory? 0x4fef98f540 ... 0xfeedface FAIL: scanned memory without EPERMs, and can read actual values ProblemType: Bug Dist
[Kernel-packages] [Bug 1729674] Re: TB16 dock ethernet corrupts data with hw checksum silently failing
** Changed in: linux (Ubuntu Artful) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1729674 Title: TB16 dock ethernet corrupts data with hw checksum silently failing Status in Dell Sputnik: Triaged Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Status in linux source package in Artful: Fix Committed Status in linux source package in Bionic: Fix Released Status in linux package in Fedora: Confirmed Bug description: It looks like TCP rx and tx checksum offloading is broken on the TB16 dock's ethernet adapter. For example downloading a large file such as the Ubuntu ISO, and then running an md5sum on it yields the incorrect md5sum. This is because rx-checksumming: on tx-checksumming: on and both set to on by default. Running sudo ethtool -K tx off rx off, allows the download to complete correctly. This is very bad since this can cause very bad untrustworthy behavior. This was conducted using an Dell Precision 5520 on Ubuntu 16.04+linux- generic-hwe-16.04-edge. Thank you To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1729674/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1746988] Comment bridged from LTC Bugzilla
--- Comment From frederic.bar...@fr.ibm.com 2018-03-01 06:01 EDT--- Indeed, I can see the 13 patches on the master-next branch. So it looks like we are in shape. Great, thanks! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1746988 Title: [Ubuntu 18.04 FEAT] OpenCAPI enabling Status in The Ubuntu-power-systems project: Triaged Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: Fix Committed Bug description: [FEATURE] OpenCAPI enabling OpenCAPI is an Open Interface Architecture that allows any microprocessor to attach to * Coherent user-level accelerators and I/O devices * Advanced memories accessible via read/write or user-level DMA semantics * Agnostic to processor architecture This is a feature to enable OpenCapi on Ubuntu 18.04. This is planned to be included in 4.16 and it will need to be backported to 4.15: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1746988/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1752550] [NEW] Failed to create KVM on Trusty ppc64le, no supported architecture for os type 'hvm'
Public bug reported: Trying to use uvtool to create a KVM instance with Trusty kernel on a ppc64le system will fail with: uvt-kvm: error: libvirt: internal error: no supported architecture for os type 'hvm' Command: uvt-kvm create kvm-test release=xenial arch=ppc64el ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-142-generic 3.13.0-142.191 ProcVersionSignature: Ubuntu 3.13.0-142.191-generic 3.13.11-ckt39 Uname: Linux 3.13.0-142-generic ppc64le 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.27 Architecture: ppc64el ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CurrentDmesg: Date: Thu Mar 1 11:09:14 2018 Lsusb: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: root=UUID=36575f9a-a03d-4d21-874c-db9886a8ffbd ro console=hvc0 ProcLoadAvg: 1.18 0.67 0.28 1/1074 8837 ProcLocks: 1: POSIX ADVISORY WRITE 6459 00:11:43064 0 0 2: FLOCK ADVISORY WRITE 2334 00:11:27831 0 EOF 3: POSIX ADVISORY WRITE 2264 00:11:35027 0 EOF 4: POSIX ADVISORY WRITE 2387 00:11:35925 0 EOF ProcSwaps: Filename TypeSizeUsedPriority /swap.img file 8388544 0 -1 ProcVersion: Linux version 3.13.0-142-generic (buildd@bos02-ppc64el-009) (gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3) ) #191-Ubuntu SMP Fri Feb 2 12:12:31 UTC 2018 RelatedPackageVersions: linux-restricted-modules-3.13.0-142-generic N/A linux-backports-modules-3.13.0-142-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) cpu_cores: Number of cores present = 20 cpu_coreson: Number of cores online = 20 cpu_freq: min: 3.694 GHz (cpu 124) max: 3.694 GHz (cpu 1) avg: 3.694 GHz cpu_runmode: Could not retrieve current diagnostics mode, No firmware implementation of function cpu_smt: SMT=8 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug ppc64el trusty uec-images ** Description changed: Trying to use uvtool to create a KVM instance with Trusty kernel on a ppc64le system will fail with: uvt-kvm: error: libvirt: internal error: no supported architecture for os type 'hvm' + + Command: + uvt-kvm create kvm-test release=xenial arch=ppc64el ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-142-generic 3.13.0-142.191 ProcVersionSignature: Ubuntu 3.13.0-142.191-generic 3.13.11-ckt39 Uname: Linux 3.13.0-142-generic ppc64le 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.27 Architecture: ppc64el ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CurrentDmesg: - + Date: Thu Mar 1 11:09:14 2018 Lsusb: - Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub - Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub - Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub - Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub PciMultimedia: - + ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash ProcFB: - + ProcKernelCmdLine: root=UUID=36575f9a-a03d-4d21-874c-db9886a8ffbd ro console=hvc0 ProcLoadAvg: 1.18 0.67 0.28 1/1074 8837 ProcLocks: - 1: POSIX ADVISORY WRITE 6459 00:11:43064 0 0 - 2: FLOCK ADVISORY WRITE 2334 00:11:27831 0 EOF - 3: POSIX ADVISORY WRITE 2264 00:11:35027 0 EOF - 4: POSIX ADVISORY WRITE 2387 00:11:35925 0 EOF + 1: POSIX ADVISORY WRITE 6459 00:11:43064 0 0 + 2: FLOCK ADVISORY WRITE 2334 00:11:27831 0 EOF + 3: POSIX ADVISORY WRITE 2264 00:11:35027 0 EOF + 4: POSIX ADVISORY WRITE 2387 00:11:35925 0 EOF ProcSwaps: - Filename TypeSizeUsedPriorit
[Kernel-packages] [Bug 1743812] Re: CVE-2017-5715 [branch target injection] aka 'Spectre Variant 2'
Virtualbox is tracked in bug 1736116 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1743812 Title: CVE-2017-5715 [branch target injection] aka 'Spectre Variant 2' Status in linux package in Ubuntu: Triaged Status in linux source package in Artful: Triaged Bug description: Hello, I'm testing script: https://www.tecmint.com/check-and-patch-meltdown-cpu-vulnerability-in-linux/ :~/spectre-meltdown-checker$ sudo ./spectre-meltdown-checker.sh [sudo] password for caravena: Spectre and Meltdown mitigation detection tool v0.31 Checking for vulnerabilities against running kernel Linux 4.13.0-30-generic #33-Ubuntu SMP Mon Jan 15 19:45:48 UTC 2018 x86_64 CPU is Intel(R) Core(TM) i3-2377M CPU @ 1.50GHz CVE-2017-5753 [bounds check bypass] aka 'Spectre Variant 1' * Checking count of LFENCE opcodes in kernel: YES > STATUS: NOT VULNERABLE (114 opcodes found, which is >= 70, heuristic to be improved when official patches become available) CVE-2017-5715 [branch target injection] aka 'Spectre Variant 2' * Mitigation 1 * Hardware (CPU microcode) support for mitigation * The SPEC_CTRL MSR is available: NO * The SPEC_CTRL CPUID feature bit is set: NO * Kernel support for IBRS: YES * IBRS enabled for Kernel space: NO * IBRS enabled for User space: NO * Mitigation 2 * Kernel compiled with retpoline option: NO * Kernel compiled with a retpoline-aware compiler: NO > STATUS: VULNERABLE (IBRS hardware + kernel support OR kernel with retpoline are needed to mitigate the vulnerability) CVE-2017-5754 [rogue data cache load] aka 'Meltdown' aka 'Variant 3' * Kernel supports Page Table Isolation (PTI): YES * PTI enabled and active: YES * Checking if we're running under Xen PV (64 bits): NO > STATUS: NOT VULNERABLE (PTI mitigates the vulnerability) A false sense of security is worse than no security at all, see --disclaimer Regards, -- Cristian ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.13.0-30-generic 4.13.0-30.33 ProcVersionSignature: Ubuntu 4.13.0-30.33-generic 4.13.13 Uname: Linux 4.13.0-30-generic x86_64 ApportVersion: 2.20.8-0ubuntu6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: caravena 1689 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Jan 17 13:18:45 2018 InstallationDate: Installed on 2017-10-13 (96 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.13.0-30-generic root=UUID=707d0f89-4b1d-4432-9d50-6058dc4c1ee9 ro rootflags=subvol=@ quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-30-generic N/A linux-backports-modules-4.13.0-30-generic N/A linux-firmware 1.170 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P14AAJ dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: SAMSUNG_NP1234567890 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.family: ChiefRiver System dmi.product.name: 530U3C/530U4C dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1743812/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1752550] 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/1752550 Title: Failed to create KVM on Trusty ppc64le, no supported architecture for os type 'hvm' Status in linux package in Ubuntu: Confirmed Bug description: Trying to use uvtool to create a KVM instance with Trusty kernel on a ppc64le system will fail with: uvt-kvm: error: libvirt: internal error: no supported architecture for os type 'hvm' Command: uvt-kvm create kvm-test release=xenial arch=ppc64el ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-142-generic 3.13.0-142.191 ProcVersionSignature: Ubuntu 3.13.0-142.191-generic 3.13.11-ckt39 Uname: Linux 3.13.0-142-generic ppc64le 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.27 Architecture: ppc64el ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CurrentDmesg: Date: Thu Mar 1 11:09:14 2018 Lsusb: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: root=UUID=36575f9a-a03d-4d21-874c-db9886a8ffbd ro console=hvc0 ProcLoadAvg: 1.18 0.67 0.28 1/1074 8837 ProcLocks: 1: POSIX ADVISORY WRITE 6459 00:11:43064 0 0 2: FLOCK ADVISORY WRITE 2334 00:11:27831 0 EOF 3: POSIX ADVISORY WRITE 2264 00:11:35027 0 EOF 4: POSIX ADVISORY WRITE 2387 00:11:35925 0 EOF ProcSwaps: Filename TypeSizeUsedPriority /swap.img file 8388544 0 -1 ProcVersion: Linux version 3.13.0-142-generic (buildd@bos02-ppc64el-009) (gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3) ) #191-Ubuntu SMP Fri Feb 2 12:12:31 UTC 2018 RelatedPackageVersions: linux-restricted-modules-3.13.0-142-generic N/A linux-backports-modules-3.13.0-142-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) cpu_cores: Number of cores present = 20 cpu_coreson: Number of cores online = 20 cpu_freq: min: 3.694 GHz (cpu 124) max: 3.694 GHz (cpu 1) avg: 3.694 GHz cpu_runmode: Could not retrieve current diagnostics mode, No firmware implementation of function cpu_smt: SMT=8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752550/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1752551] [NEW] zram smoke test failed on Trusty ppc64le
Public bug reported: The zram smoke has failed with: modprobe: FATAL: Module zram not found. >From its config, there is no zram related entry, not sure if this is intended: grep -i zram /boot/config-3.13.0-142-generic (returns nothing) If this is intended, we can disable this test on ppc64le. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-142-generic 3.13.0-142.191 ProcVersionSignature: Ubuntu 3.13.0-142.191-generic 3.13.11-ckt39 Uname: Linux 3.13.0-142-generic ppc64le 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.27 Architecture: ppc64el ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CurrentDmesg: [ 890.069571] init: zram-config post-stop process (9543) terminated with status 1 Date: Thu Mar 1 11:27:11 2018 Lsusb: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: root=UUID=36575f9a-a03d-4d21-874c-db9886a8ffbd ro console=hvc0 ProcLoadAvg: 0.00 0.08 0.16 1/1059 10316 ProcLocks: 1: POSIX ADVISORY WRITE 6459 00:11:43064 0 0 2: FLOCK ADVISORY WRITE 2334 00:11:27831 0 EOF 3: POSIX ADVISORY WRITE 2264 00:11:35027 0 EOF 4: POSIX ADVISORY WRITE 2387 00:11:35925 0 EOF ProcSwaps: Filename TypeSizeUsedPriority /swap.img file 8388544 0 -1 ProcVersion: Linux version 3.13.0-142-generic (buildd@bos02-ppc64el-009) (gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3) ) #191-Ubuntu SMP Fri Feb 2 12:12:31 UTC 2018 RelatedPackageVersions: linux-restricted-modules-3.13.0-142-generic N/A linux-backports-modules-3.13.0-142-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) cpu_cores: Number of cores present = 20 cpu_coreson: Number of cores online = 20 cpu_smt: SMT=8 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug ppc64el trusty uec-images ** Description changed: The zram smoke has failed with: - modprobe: FATAL: Module zram not found. + modprobe: FATAL: Module zram not found. From its config, there is no zram related entry, not sure if this is intended: - grep -i zram /boot/config-3.13.0-142-generic + grep -i zram /boot/config-3.13.0-142-generic (returns nothing) + + If this is intended, we can disable this test on ppc64le. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-142-generic 3.13.0-142.191 ProcVersionSignature: Ubuntu 3.13.0-142.191-generic 3.13.11-ckt39 Uname: Linux 3.13.0-142-generic ppc64le 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.27 Architecture: ppc64el ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CurrentDmesg: [ 890.069571] init: zram-config post-stop process (9543) terminated with status 1 Date: Thu Mar 1 11:27:11 2018 Lsusb: - Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub - Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub - Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub - Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub PciMultimedia: - + ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash ProcFB: - + ProcKernelCmdLine: root=UUID=36575f9a-a03d-4d21-874c-db9886a8ffbd ro console=hvc0 ProcLoadAvg: 0.00 0.08 0.16 1/1059 10316 ProcLocks: - 1: POSIX ADVISORY WRITE 6459 00:11:43064 0 0 - 2: FLOCK ADVISORY WRITE 2334 00:11:27831 0 EOF - 3: POSIX ADVISORY WRITE 2264 00:11:35027 0 EOF - 4: POSIX ADVISORY WRITE 2387 00:11:35925 0 EOF + 1: POSIX ADVISORY WRITE 6459 00:11:43064 0 0 + 2: FLOCK ADVISORY WRITE 2334 00:11:27831 0 EOF + 3: POSIX ADVISORY WRITE 2264 00:11:35027 0 EOF + 4: P
[Kernel-packages] [Bug 1752551] 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/1752551 Title: zram smoke test failed on Trusty ppc64le Status in linux package in Ubuntu: Confirmed Bug description: The zram smoke has failed with: modprobe: FATAL: Module zram not found. From its config, there is no zram related entry, not sure if this is intended: grep -i zram /boot/config-3.13.0-142-generic (returns nothing) If this is intended, we can disable this test on ppc64le. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-142-generic 3.13.0-142.191 ProcVersionSignature: Ubuntu 3.13.0-142.191-generic 3.13.11-ckt39 Uname: Linux 3.13.0-142-generic ppc64le 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.27 Architecture: ppc64el ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CurrentDmesg: [ 890.069571] init: zram-config post-stop process (9543) terminated with status 1 Date: Thu Mar 1 11:27:11 2018 Lsusb: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: root=UUID=36575f9a-a03d-4d21-874c-db9886a8ffbd ro console=hvc0 ProcLoadAvg: 0.00 0.08 0.16 1/1059 10316 ProcLocks: 1: POSIX ADVISORY WRITE 6459 00:11:43064 0 0 2: FLOCK ADVISORY WRITE 2334 00:11:27831 0 EOF 3: POSIX ADVISORY WRITE 2264 00:11:35027 0 EOF 4: POSIX ADVISORY WRITE 2387 00:11:35925 0 EOF ProcSwaps: Filename TypeSizeUsedPriority /swap.img file 8388544 0 -1 ProcVersion: Linux version 3.13.0-142-generic (buildd@bos02-ppc64el-009) (gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3) ) #191-Ubuntu SMP Fri Feb 2 12:12:31 UTC 2018 RelatedPackageVersions: linux-restricted-modules-3.13.0-142-generic N/A linux-backports-modules-3.13.0-142-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) cpu_cores: Number of cores present = 20 cpu_coreson: Number of cores online = 20 cpu_smt: SMT=8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752551/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1746225] Re: [P9, Power NV][WSP][Ubuntu 1804] : "Kernel access of bad area " when grouping different pmu events using perf fuzzer . (perf:)
** Changed in: linux (Ubuntu Artful) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1746225 Title: [P9,Power NV][WSP][Ubuntu 1804] : "Kernel access of bad area " when grouping different pmu events using perf fuzzer . (perf:) Status in The Ubuntu-power-systems project: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Artful: Fix Committed Status in linux source package in Bionic: Fix Released Bug description: == SRU Justification == Due to this bug, perf fuzzer resulted in crash and system goes for a reboot and results in a call trace shown in the bug. It is due to grouping of different PMU events, which is fixed by mainline commit 5aa04b3eb6fca63d2e9827be656dcadc26d54e1 Commit 5aa04b3eb6fca63d2e9827be656dcadc26d54e11 is in mailine as of v4.15-rc5. == Fix == commit 5aa04b3eb6fca63d2e9827be656dcadc26d54e11 Author: Ravi Bangoria Date: Thu Nov 30 14:03:22 2017 +0530 powerpc/perf: Fix oops when grouping different pmu events == Regression Potential == Low. This fix is specific to powerpc. == Test Case == A test kernel was built with this patch and tested by the original bug reporter. The bug reporter states the test kernel resolved the bug. ==Original Bug Description== == Comment: #0 - Shriya R. Kulkarni - 2018-01-30 03:24:47 == Problem Description : == Perf fuzzer resulted in crash and system goes for reboot and the call trace is shown below . It is due to grouping of different PMU events. Machine details : == OS : Ubuntu 1804 uname -r : 4.13.0-25-generic system : Witherspoon + DD2.1 perf -v : perf version 4.13.13 ltc-wspoon12 login: [78592.995848] Unable to handle kernel paging request for instruction fetch [78592.995914] Faulting instruction address: 0x [78592.995950] Oops: Kernel access of bad area, sig: 11 [#1] [78592.995982] SMP NR_CPUS=2048 [78592.995985] NUMA [78592.996011] PowerNV [78592.996045] Modules linked in: vmx_crypto idt_89hpesx crct10dif_vpmsum at24 ofpart uio_pdrv_genirq uio cmdlinepart powernv_flash mtd ibmpowernv opal_prd ipmi_powernv ipmi_devintf ipmi_msghandler sch_fq_codel ip_tables x_tables autofs4 nouveau lpfc ast i2c_algo_bit crc32c_vpmsum ttm drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops drm mlx5_core nvmet_fc nvmet tg3 nvme_fc nvme_fabrics ahci nvme_core libahci mlxfw devlink scsi_transport_fc [78592.996367] CPU: 69 PID: 6010 Comm: perf_fuzzer Tainted: GW 4.13.0-25-generic #29-Ubuntu [78592.996422] task: c03f77b5b500 task.stack: c03d0b0c8000 [78592.996462] NIP: LR: c00e9b1c CTR: [78592.996509] REGS: c03d0b0cb780 TRAP: 0400 Tainted: GW (4.13.0-25-generic) [78592.996562] MSR: 900040009033 [78592.996588] CR: 48002874 XER: [78592.996642] CFAR: c00e9b18 SOFTE: 1 [78592.996642] GPR00: c00eb128 c03d0b0cba00 c15f6200 [78592.996642] GPR04: c03d0b0cbba0 c03d0b0cbc20 0002 c1596b10 [78592.996642] GPR08: 0002 c1596b10 c03fecad0028 [78592.996642] GPR12: c7a8d480 [78592.996642] GPR16: [78592.996642] GPR20: 0001 c03d0b0cbc1c c03d0b0cbc24 c03d0b0cbb98 [78592.996642] GPR24: c03d0b0cbba0 c03d0b0cbc20 1555 c03fefeb4ea0 [78592.996642] GPR28: c03d0b0cbc20 0002 3000 c03fefeb5190 [78592.997170] NIP [] (null) [78592.997208] LR [c00e9b1c] power_check_constraints+0x13c/0x5a0 [78592.997247] Call Trace: [78592.997267] [c03d0b0cba00] [c03d0b0cbaa0] 0xc03d0b0cbaa0 (unreliable) [78592.997321] [c03d0b0cbb80] [c00eb128] power_pmu_event_init+0x298/0x6a0 [78592.997373] [c03d0b0cbc70] [c029e6b4] perf_try_init_event+0xd4/0x120 [78592.997424] [c03d0b0cbcb0] [c02a1038] perf_event_alloc.part.23+0x7b8/0xb90 [78592.997475] [c03d0b0cbd30] [c02aa0dc] SyS_perf_event_open+0x69c/0xfa0 [78592.997527] [c03d0b0cbe30] [c000b184] system_call+0x58/0x6c [78592.997568] Instruction dump: [78592.997597] [78592.997664] [78592.997733] ---[ end trace 57fb7542c4083583 ]--- [78594.008780] [78594.008932] Sending IP[78773.335857584,5] OPAL: Switch to big-endian OS I to other CPUs [78594.01029 Steps to reproduce : #! /bin/bash se
[Kernel-packages] [Bug 1715519] Re: bnx2x_attn_int_deasserted3:4323 MC assert!
** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Status: New => Fix Committed ** Also affects: linux (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Trusty) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1715519 Title: bnx2x_attn_int_deasserted3:4323 MC assert! Status in linux package in Ubuntu: Fix Released Status in linux source package in Trusty: Fix Committed Status in linux source package in Xenial: Fix Committed Status in linux source package in Artful: Fix Committed Bug description: SRU Justification = A ppc64le system runs as a guest under PowerVM. This guest has a bnx2x card attached, and uses openvswitch to bridge an ibmveth interface for traffic from other LPARs. We see the following crash sometimes when running netperf: May 10 17:16:32 tuk6r1phn2 kernel: bnx2x: [bnx2x_attn_int_deasserted3:4323(enP24p1s0f2)]MC assert! May 10 17:16:32 tuk6r1phn2 kernel: bnx2x: [bnx2x_mc_assert:720(enP24p1s0f2)]XSTORM_ASSERT_LIST_INDEX 0x2 May 10 17:16:32 tuk6r1phn2 kernel: bnx2x: [bnx2x_mc_assert:736(enP24p1s0f2)]XSTORM_ASSERT_INDEX 0x0 = 0x 0x25e42a7e 0x00462a38 0x00010052 May 10 17:16:32 tuk6r1phn2 kernel: bnx2x: [bnx2x_mc_assert:750(enP24p1s0f2)]Chip Revision: everest3, FW Version: 7_13_1 May 10 17:16:32 tuk6r1phn2 kernel: bnx2x: [bnx2x_attn_int_deasserted3:4329(enP24p1s0f2)]driver assert May 10 17:16:32 tuk6r1phn2 kernel: bnx2x: [bnx2x_panic_dump:923(enP24p1s0f2)]begin crash dump - ... (dump of registers follows) ... Subsequent debugging reveals that the packets causing the issue come through the ibmveth interface - from the AIX LPAR. The veth protocol is 'special' - communication between LPARs on the same chassis can use very large (64k) frames to reduce overhead. Normal networks cannot handle such large packets, so traditionally, the VIOS partition would signal to the AIX partitions that it was 'special', and AIX would send regular, ethernet-sized packets to VIOS, which VIOS would then send out. This signalling between VIOS and AIX is done in a way that is not standards-compliant, and so was never made part of Linux. Instead, the Linux driver has always understood large frames and passed them up the network stack. In some cases (e.g. with TCP), multiple TCP segments are coalesced into one large packet. In Linux, this goes through the generic receive offload code, using a similar mechanism to GSO. These segments can be very large which presents as a very large MSS (maximum segment size) or gso_size. Normally, the large packet is simply passed to whatever network application on Linux is going to consume it, and everything is OK. However, in this case, the packets go through Open vSwitch, and are then passed to the bnx2x driver. The bnx2x driver/hardware supports TSO and GSO, but with a restriction: the maximum segment size is limited to around 9700 bytes. Normally this is more than adequate. However, if a large packet with very large (>9700 byte) TCP segments arrives through ibmveth, and is passed to bnx2x, the hardware will panic. [Impact] bnx2x card panics, requiring power cycle to restore functionality. The workaround is turning off TSO, which prevents the crash as the kernel resegments *all* packets in software, not just ones that are too big. This has a performance cost. [Fix] Test packet size in bnx2x feature check path and disable GSO if it is too large. To do this we move a function from one file to another and add another in the networking core. [Regression Potential] A/B/X: The changes to the network core are easily reviewed. The changes to behaviour are limited to the bnx2x card driver. The most likely failure case is a false-positive on the size check, which would lead to a performance regression only. T: This also involves a different change to the networking core to add the old-style GSO checking, which is more invasive. However the changes are simple and easily reviewed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1715519/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1746174] Re: Error in CPU frequency reporting when nominal and min pstates are same (cpufreq)
** Tags added: kernel-bug-break-fix ** Description changed: - == SRU Justification == Commit 09ca4c9b5958 introduced a bug in v4.8-rc2. The bug is that an error happens in CPU frequency reporting when nominal and min pstates are the same (cpufreq). Commit 3fa4680b8 fixes this issue. Commit 3fa4680b8 is in mailine as of v4.16-rc1 and has been cc'd to upstream stable. == Fix == commit 3fa4680b860bf48b437d6a2c039789c4abe202ae Author: Shilpasri G Bhat Date: Fri Jan 12 12:43:53 2018 +0530 - cpufreq: powernv: Dont assume distinct pstate values for nominal and + cpufreq: powernv: Dont assume distinct pstate values for nominal and pmin == Regression Potential == - Low. This commit been cc'd to upstream stable, so it has had additional + Low. This commit been cc'd to upstream stable, so it has had additional upstream review. == Test Case == A test kernel was built with this patch and tested by the original bug reporter. The bug reporter states the test kernel resolved the bug. - - == Comment: #0 - Shilpasri G. Bhat +++ This bug was initially created as a clone of Bug #163527 +++ ---Problem Description--- Error in CPU frequency reporting when nominal and min pstates are same The patch for this issue is accepted to linux-next as 3fa4680b860bf48b437d6a2c039789c4abe202ae cpufreq: powernv: Dont assume distinct pstate values for nominal and pmin Some OpenPOWER boxes can have same pstate values for nominal and pmin pstates. In these boxes the current code will not initialize 'powernv_pstate_info.min' variable and result in erroneous CPU frequency reporting. This patch fixes this problem. Fixes: 09ca4c9b5958 (cpufreq: powernv: Replacing pstate_id with frequency table index) Reported-by: Alvin Wang Signed-off-by: Shilpasri G Bhat Acked-by: Viresh Kumar Cc: 4.8+ # 4.8+ Signed-off-by: Rafael J. Wysocki https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux- pm.git/commit/drivers/cpufreq/powernv-cpufreq.c?h=linux- next&id=3fa4680b860bf48b437d6a2c039789c4abe202ae + + break-fix: - cf0de9a0d52ff64bcb6b20b6fa4b5d3eb4637719 + break-fix: - 3fa4680b860bf48b437d6a2c039789c4abe202ae ** Changed in: linux (Ubuntu Bionic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1746174 Title: Error in CPU frequency reporting when nominal and min pstates are same (cpufreq) Status in The Ubuntu-power-systems project: Incomplete Status in linux package in Ubuntu: Fix Committed Status in linux source package in Artful: In Progress Status in linux source package in Bionic: Fix Committed Bug description: == SRU Justification == Commit 09ca4c9b5958 introduced a bug in v4.8-rc2. The bug is that an error happens in CPU frequency reporting when nominal and min pstates are the same (cpufreq). Commit 3fa4680b8 fixes this issue. Commit 3fa4680b8 is in mailine as of v4.16-rc1 and has been cc'd to upstream stable. == Fix == commit 3fa4680b860bf48b437d6a2c039789c4abe202ae Author: Shilpasri G Bhat Date: Fri Jan 12 12:43:53 2018 +0530 cpufreq: powernv: Dont assume distinct pstate values for nominal and pmin == Regression Potential == Low. This commit been cc'd to upstream stable, so it has had additional upstream review. == Test Case == A test kernel was built with this patch and tested by the original bug reporter. The bug reporter states the test kernel resolved the bug. == Comment: #0 - Shilpasri G. Bhat +++ This bug was initially created as a clone of Bug #163527 +++ ---Problem Description--- Error in CPU frequency reporting when nominal and min pstates are same The patch for this issue is accepted to linux-next as 3fa4680b860bf48b437d6a2c039789c4abe202ae cpufreq: powernv: Dont assume distinct pstate values for nominal and pmin Some OpenPOWER boxes can have same pstate values for nominal and pmin pstates. In these boxes the current code will not initialize 'powernv_pstate_info.min' variable and result in erroneous CPU frequency reporting. This patch fixes this problem. Fixes: 09ca4c9b5958 (cpufreq: powernv: Replacing pstate_id with frequency table index) Reported-by: Alvin Wang Signed-off-by: Shilpasri G Bhat Acked-by: Viresh Kumar Cc: 4.8+ # 4.8+ Signed-off-by: Rafael J. Wysocki https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux- pm.git/commit/drivers/cpufreq/powernv-cpufreq.c?h=linux- next&id=3fa4680b860bf48b437d6a2c039789c4abe202ae break-fix: - cf0de9a0d52ff64bcb6b20b6fa4b5d3eb4637719 break-fix: - 3fa4680b860bf48b437d6a2c039789c4abe202ae To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1746174/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kerne
[Kernel-packages] [Bug 1752574] [NEW] Thunderbolt NULL pointer dereference in linux 4.15
Public bug reported: [0.994565] thunderbolt :09:00.0: enabling device ( -> 0002) [0.994957] thunderbolt :09:00.0: NHI initialized, starting thunderbolt [0.994961] thunderbolt :09:00.0: allocating TX ring 0 of size 10 [0.994983] thunderbolt :09:00.0: allocating RX ring 0 of size 10 [0.994999] thunderbolt :09:00.0: control channel created [0.994999] thunderbolt :09:00.0: control channel starting... [0.995000] thunderbolt :09:00.0: starting TX ring 0 [0.995018] thunderbolt :09:00.0: enabling interrupt at register 0x38200 bit 0 (0x0 -> 0x1) [0.995018] thunderbolt :09:00.0: starting RX ring 0 [0.995033] thunderbolt :09:00.0: enabling interrupt at register 0x38200 bit 12 (0x1 -> 0x1001) [0.995046] thunderbolt :09:00.0: starting ICM firmware [0.995060] BUG: unable to handle kernel NULL pointer dereference at 0980 [0.995065] IP: pci_write_config_dword+0x5/0x30 [0.995066] PGD 0 P4D 0 [0.995068] Oops: [#1] SMP PTI [0.995069] Modules linked in: thunderbolt(+) ahci(+) ipmi_devintf libahci ipmi_msghandler video fjes(-) [0.995074] CPU: 6 PID: 214 Comm: systemd-udevd Not tainted 4.15.0-10-generic #11-Ubuntu [0.995075] Hardware name: Gigabyte Technology Co., Ltd. Z170X-UD5 TH/Z170X-UD5 TH-CF, BIOS F22d 12/01/2017 [0.995077] RIP: 0010:pci_write_config_dword+0x5/0x30 [0.995078] RSP: 0018:9e58839779e0 EFLAGS: 00010296 [0.995079] RAX: 4126 RBX: RCX: 0050 [0.995080] RDX: 0200 RSI: 0034 RDI: [0.995081] RBP: 9e5883977a18 R08: 0200 R09: 0330 [0.995082] R10: 2000 R11: R12: [0.995083] R13: 0050 R14: 92354e146f28 R15: [0.995084] FS: 7f86f2204440() GS:92357ed8() knlGS: [0.995085] CS: 0010 DS: ES: CR0: 80050033 [0.995086] CR2: 0980 CR3: 00080d1ce004 CR4: 003606e0 [0.995087] DR0: DR1: DR2: [0.995088] DR3: DR6: fffe0ff0 DR7: 0400 [0.995089] Call Trace: [0.995094] ? pcie2cio_write+0x40/0x80 [thunderbolt] [0.995098] icm_driver_ready+0x178/0x270 [thunderbolt] [0.995101] ? tb_ctl_start+0x50/0x90 [thunderbolt] [0.995105] tb_domain_add+0x79/0x100 [thunderbolt] [0.995108] nhi_probe+0x186/0x300 [thunderbolt] [0.995110] local_pci_probe+0x47/0xa0 [0.995111] pci_device_probe+0x145/0x1b0 [0.995114] driver_probe_device+0x31e/0x490 [0.995116] __driver_attach+0xa7/0xf0 [0.995118] ? driver_probe_device+0x490/0x490 [0.995119] bus_for_each_dev+0x70/0xc0 [0.995121] driver_attach+0x1e/0x20 [0.995123] bus_add_driver+0x1c7/0x270 [0.995124] ? 0xc03a9000 [0.995125] driver_register+0x60/0xe0 [0.995126] ? 0xc03a9000 [0.995128] __pci_register_driver+0x5a/0x60 [0.995131] nhi_init+0x2d/0x1000 [thunderbolt] [0.995133] do_one_initcall+0x52/0x1a0 [0.995135] ? _cond_resched+0x19/0x40 [0.995138] ? kmem_cache_alloc_trace+0xa6/0x1b0 [0.995140] ? do_init_module+0x27/0x209 [0.995141] do_init_module+0x5f/0x209 [0.995143] load_module+0x191e/0x1f10 [0.995146] ? ima_post_read_file+0x96/0xa0 [0.995148] SYSC_finit_module+0xfc/0x120 [0.995149] ? SYSC_finit_module+0xfc/0x120 [0.995151] SyS_finit_module+0xe/0x10 [0.995152] do_syscall_64+0x76/0x130 [0.995154] entry_SYSCALL_64_after_hwframe+0x21/0x86 [0.995155] RIP: 0033:0x7f86f1af3a49 [0.995156] RSP: 002b:7ffdedfa4478 EFLAGS: 0246 ORIG_RAX: 0139 [0.995157] RAX: ffda RBX: 559d3ffde790 RCX: 7f86f1af3a49 [0.995158] RDX: RSI: 7f86f17df0e5 RDI: 0005 [0.995159] RBP: 7f86f17df0e5 R08: R09: 7ffdedfa4590 [0.995160] R10: 0005 R11: 0246 R12: [0.995161] R13: 559d3ffedbf0 R14: 0002 R15: 559d3ffde790 [0.995162] Code: 87 c0 00 00 00 b9 04 00 00 00 48 89 e5 48 8b 40 20 e8 d0 45 72 00 5d c3 b8 87 00 00 00 c3 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 <48> 8b 8f 80 09 00 00 83 e1 01 75 0b 55 48 89 e5 e8 a6 ff ff ff [0.995182] RIP: pci_write_config_dword+0x5/0x30 RSP: 9e58839779e0 [0.995182] CR2: 0980 [0.995184] ---[ end trace 501c09dbb95a731e ]--- ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-10-generic 4.15.0-10.11 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC4D0', '/dev/snd/pcmC4D9p', '/dev
[Kernel-packages] [Bug 1742563] Re: [Feature] Mehlow:RAID mode PCI ID
I built a Bionic test kernel with commit f919dde0772a894c693a1eeabc77df69d6a9b937. The test kernel can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1742563 Can you test this kernel and see if it resolves this bug? Note, to test this kernel, you need to install both the linux-image and linux-image-extra .deb packages. Thanks in advance! ** Information type changed from Proprietary to Public ** Changed in: intel Assignee: (unassigned) => Joseph Salisbury (jsalisbury) ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => In Progress ** Changed in: intel Status: Triaged => In Progress ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) ** Also affects: linux (Ubuntu Bionic) Importance: Medium Assignee: Joseph Salisbury (jsalisbury) Status: In Progress ** Information type changed from Public to Private -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1742563 Title: [Feature] Mehlow:RAID mode PCI ID Status in intel: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: Description: RAIP PCI IDs 0xA356 Dell has requested to upstream this device ID Target Release: 18.04 Target kernel: 4.16 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1742563/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1750245] Re: i915 kbl_guc_ver9_14.bin does not load
Which release are you running, and what version of linux-firmware do you have installed? As far as I can tell the only two releases which contain that file (artful/bionic) have the exact same file as the one at the link you provided. -- 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/1750245 Title: i915 kbl_guc_ver9_14.bin does not load Status in linux-firmware package in Ubuntu: Confirmed Bug description: The provided i915/kbl_guc_ver9_14.bin does not load when configured to do so . If the file is replaced by manually installing with the included script from 01.org, it loads properly: https://01.org/linuxgraphics/downloads/kabylake-guc-9.14 Before: GuC firmware status: path: i915/kbl_guc_ver9_14.bin fetch: FAIL load: NONE version wanted: 9.14 version found: 0.0 header: offset is 0; size = 0 uCode: offset is 0; size = 0 RSA: offset is 0; size = 0 After: GuC firmware status: path: i915/kbl_guc_ver9_14.bin fetch: SUCCESS load: SUCCESS version wanted: 9.14 version found: 9.14 header: offset is 0; size = 128 uCode: offset is 128; size = 142272 RSA: offset is 142400; size = 256 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1750245/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1752574] 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/1752574 Title: Thunderbolt NULL pointer dereference in linux 4.15 Status in linux package in Ubuntu: Confirmed Bug description: [0.994565] thunderbolt :09:00.0: enabling device ( -> 0002) [0.994957] thunderbolt :09:00.0: NHI initialized, starting thunderbolt [0.994961] thunderbolt :09:00.0: allocating TX ring 0 of size 10 [0.994983] thunderbolt :09:00.0: allocating RX ring 0 of size 10 [0.994999] thunderbolt :09:00.0: control channel created [0.994999] thunderbolt :09:00.0: control channel starting... [0.995000] thunderbolt :09:00.0: starting TX ring 0 [0.995018] thunderbolt :09:00.0: enabling interrupt at register 0x38200 bit 0 (0x0 -> 0x1) [0.995018] thunderbolt :09:00.0: starting RX ring 0 [0.995033] thunderbolt :09:00.0: enabling interrupt at register 0x38200 bit 12 (0x1 -> 0x1001) [0.995046] thunderbolt :09:00.0: starting ICM firmware [0.995060] BUG: unable to handle kernel NULL pointer dereference at 0980 [0.995065] IP: pci_write_config_dword+0x5/0x30 [0.995066] PGD 0 P4D 0 [0.995068] Oops: [#1] SMP PTI [0.995069] Modules linked in: thunderbolt(+) ahci(+) ipmi_devintf libahci ipmi_msghandler video fjes(-) [0.995074] CPU: 6 PID: 214 Comm: systemd-udevd Not tainted 4.15.0-10-generic #11-Ubuntu [0.995075] Hardware name: Gigabyte Technology Co., Ltd. Z170X-UD5 TH/Z170X-UD5 TH-CF, BIOS F22d 12/01/2017 [0.995077] RIP: 0010:pci_write_config_dword+0x5/0x30 [0.995078] RSP: 0018:9e58839779e0 EFLAGS: 00010296 [0.995079] RAX: 4126 RBX: RCX: 0050 [0.995080] RDX: 0200 RSI: 0034 RDI: [0.995081] RBP: 9e5883977a18 R08: 0200 R09: 0330 [0.995082] R10: 2000 R11: R12: [0.995083] R13: 0050 R14: 92354e146f28 R15: [0.995084] FS: 7f86f2204440() GS:92357ed8() knlGS: [0.995085] CS: 0010 DS: ES: CR0: 80050033 [0.995086] CR2: 0980 CR3: 00080d1ce004 CR4: 003606e0 [0.995087] DR0: DR1: DR2: [0.995088] DR3: DR6: fffe0ff0 DR7: 0400 [0.995089] Call Trace: [0.995094] ? pcie2cio_write+0x40/0x80 [thunderbolt] [0.995098] icm_driver_ready+0x178/0x270 [thunderbolt] [0.995101] ? tb_ctl_start+0x50/0x90 [thunderbolt] [0.995105] tb_domain_add+0x79/0x100 [thunderbolt] [0.995108] nhi_probe+0x186/0x300 [thunderbolt] [0.995110] local_pci_probe+0x47/0xa0 [0.995111] pci_device_probe+0x145/0x1b0 [0.995114] driver_probe_device+0x31e/0x490 [0.995116] __driver_attach+0xa7/0xf0 [0.995118] ? driver_probe_device+0x490/0x490 [0.995119] bus_for_each_dev+0x70/0xc0 [0.995121] driver_attach+0x1e/0x20 [0.995123] bus_add_driver+0x1c7/0x270 [0.995124] ? 0xc03a9000 [0.995125] driver_register+0x60/0xe0 [0.995126] ? 0xc03a9000 [0.995128] __pci_register_driver+0x5a/0x60 [0.995131] nhi_init+0x2d/0x1000 [thunderbolt] [0.995133] do_one_initcall+0x52/0x1a0 [0.995135] ? _cond_resched+0x19/0x40 [0.995138] ? kmem_cache_alloc_trace+0xa6/0x1b0 [0.995140] ? do_init_module+0x27/0x209 [0.995141] do_init_module+0x5f/0x209 [0.995143] load_module+0x191e/0x1f10 [0.995146] ? ima_post_read_file+0x96/0xa0 [0.995148] SYSC_finit_module+0xfc/0x120 [0.995149] ? SYSC_finit_module+0xfc/0x120 [0.995151] SyS_finit_module+0xe/0x10 [0.995152] do_syscall_64+0x76/0x130 [0.995154] entry_SYSCALL_64_after_hwframe+0x21/0x86 [0.995155] RIP: 0033:0x7f86f1af3a49 [0.995156] RSP: 002b:7ffdedfa4478 EFLAGS: 0246 ORIG_RAX: 0139 [0.995157] RAX: ffda RBX: 559d3ffde790 RCX: 7f86f1af3a49 [0.995158] RDX: RSI: 7f86f17df0e5 RDI: 0005 [0.995159] RBP: 7f86f17df0e5 R08: R09: 7ffdedfa4590 [0.995160] R10: 0005 R11: 0246 R12: [0.995161] R13: 559d3ffedbf0 R14: 0002 R15: 559d3ffde790 [0.995162] Code: 87 c0 00 00 00 b9 04 00 00 00 48 89 e5 48 8b 40 20 e8 d0 45 72 00 5d c3 b8 87 00 00 00 c3 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 <48> 8b 8f 80 09 00 00 83 e1 01 75 0b 55 48 89 e5 e8 a6 ff ff ff [0.995182] RIP: pci_write_c
[Kernel-packages] [Bug 1751021] Re: retpoline abi files are empty on i386
** Changed in: linux (Ubuntu Xenial) Status: New => Fix Committed ** Changed in: linux (Ubuntu Artful) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1751021 Title: retpoline abi files are empty on i386 Status in linux package in Ubuntu: In Progress Status in linux source package in Trusty: Fix Committed Status in linux source package in Xenial: Fix Committed Status in linux source package in Artful: Fix Committed Bug description: The .retpoline files in the current abi are actually blank. This is due to incorrect handling in retpoline-extract. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1751021/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1746174] Re: Error in CPU frequency reporting when nominal and min pstates are same (cpufreq)
** Changed in: linux (Ubuntu Artful) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1746174 Title: Error in CPU frequency reporting when nominal and min pstates are same (cpufreq) Status in The Ubuntu-power-systems project: Incomplete Status in linux package in Ubuntu: Fix Committed Status in linux source package in Artful: Fix Committed Status in linux source package in Bionic: Fix Committed Bug description: == SRU Justification == Commit 09ca4c9b5958 introduced a bug in v4.8-rc2. The bug is that an error happens in CPU frequency reporting when nominal and min pstates are the same (cpufreq). Commit 3fa4680b8 fixes this issue. Commit 3fa4680b8 is in mailine as of v4.16-rc1 and has been cc'd to upstream stable. == Fix == commit 3fa4680b860bf48b437d6a2c039789c4abe202ae Author: Shilpasri G Bhat Date: Fri Jan 12 12:43:53 2018 +0530 cpufreq: powernv: Dont assume distinct pstate values for nominal and pmin == Regression Potential == Low. This commit been cc'd to upstream stable, so it has had additional upstream review. == Test Case == A test kernel was built with this patch and tested by the original bug reporter. The bug reporter states the test kernel resolved the bug. == Comment: #0 - Shilpasri G. Bhat +++ This bug was initially created as a clone of Bug #163527 +++ ---Problem Description--- Error in CPU frequency reporting when nominal and min pstates are same The patch for this issue is accepted to linux-next as 3fa4680b860bf48b437d6a2c039789c4abe202ae cpufreq: powernv: Dont assume distinct pstate values for nominal and pmin Some OpenPOWER boxes can have same pstate values for nominal and pmin pstates. In these boxes the current code will not initialize 'powernv_pstate_info.min' variable and result in erroneous CPU frequency reporting. This patch fixes this problem. Fixes: 09ca4c9b5958 (cpufreq: powernv: Replacing pstate_id with frequency table index) Reported-by: Alvin Wang Signed-off-by: Shilpasri G Bhat Acked-by: Viresh Kumar Cc: 4.8+ # 4.8+ Signed-off-by: Rafael J. Wysocki https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux- pm.git/commit/drivers/cpufreq/powernv-cpufreq.c?h=linux- next&id=3fa4680b860bf48b437d6a2c039789c4abe202ae break-fix: - cf0de9a0d52ff64bcb6b20b6fa4b5d3eb4637719 break-fix: - 3fa4680b860bf48b437d6a2c039789c4abe202ae To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1746174/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1747769] Re: Cherry pick c96f5471ce7d for delayacct fix
** Changed in: linux (Ubuntu Artful)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1747769
Title:
Cherry pick c96f5471ce7d for delayacct fix
Status in linux package in Ubuntu:
Fix Committed
Status in linux source package in Artful:
Fix Committed
Status in linux source package in Bionic:
Fix Committed
Bug description:
== SRU Justification ==
Mainline commit e33a9bba85a8 introduced a regression in v4.11-rc1. This
regression
caused delayacct_blkio_end() to be called by try_to_wake_up().
However, the call was made before we have context-switched. This patch is now
correct, in that
the delay accounting ends when the I/O is complete.
Commit c96f5471ce7 is in mainline as fo v4.15-rc9.
== Fix ==
commit c96f5471ce7d2aefd0dda560cc23f08ab00bc65d
Author: Josh Snyder
Date: Mon Dec 18 16:15:10 2017 +
delayacct: Account blkio completion on the correct task
== Regression Potential ==
Low. This commit has also been cc'd to stable, so it has had additional
upstream
review.
== Test Case ==
A test kernel was built with this patch and tested by the original bug
reporter.
The bug reporter states the test kernel resolved the bug.
Please cherry pick upstream commit c96f5471ce7d ("delayacct: Account
blkio completion on the correct task") into the Ubuntu 4.13 kernel. It
has also been accepted into the Linux stable branch as 4.14.15.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1747769/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1748922] Re: linux-tools: perf incorrectly linking libbfd
** Changed in: linux (Ubuntu Xenial) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Artful) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1748922 Title: linux-tools: perf incorrectly linking libbfd Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Status in linux source package in Artful: Fix Committed Bug description: Under bug #783660 we switched away from linking libbfd and switched to using libiberty to demangle C++ names. Somewhere between precise and development upstream changed the order in which the tests are performed and triggered us to start linking against it again. = SRU Justification (for Artful/Xenial) = Impact: Linking perf (part of the linux-tools package) against libbfd prevents users to have linux-tools of different kernel versions installed in parallel. Which makes debugging hard. Fix: As stated above this had been fixed before but upstream changes of the kernel between 3.2 and 4.4 voided those fixes. Unfortunately without causing build failures but causing libbfd to be used again. This has already been fixed up in Bionic. The first of the two patches needs a backport for Xenial to make up for a file rename. The second can be picked into both releases. Testcase: Extracting ./usr/lib/linux-tools-*/perf from the generated linux-tools package and inspecting it with ldd. Old builds will have a reference to libbfd, the test builds did no longer. Risk of regression: low (change of build option which has been done before and also for some time in Bionic). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1748922/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1747746] Re: [Artful/Bionic] [Config] enable EDAC_GHES for ARM64
** Changed in: linux (Ubuntu Artful) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1747746 Title: [Artful/Bionic] [Config] enable EDAC_GHES for ARM64 Status in linux package in Ubuntu: Fix Released Status in linux source package in Artful: Fix Committed Status in linux source package in Bionic: Fix Released Bug description: [Impact] Enable CONFIG_EDAC_GHES option for ARM64, so that the memory errors are processed and reported to the user space. [Test] Test kernel is available in the PPA: https://launchpad.net/~centriq-team/+archive/ubuntu/lp1747746 Tested on QDF2400 platform with Artful user-space and Bionic 4.14 kernel. Please see comment #2 for results. [Regression Potential] None. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1747746/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1746019] Re: [Artful SRU] Fix capsule update regression
** Changed in: linux (Ubuntu Artful)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1746019
Title:
[Artful SRU] Fix capsule update regression
Status in linux package in Ubuntu:
Incomplete
Status in linux source package in Artful:
Fix Committed
Bug description:
[IMPACT]
Commit 82c3768b8d68 ("efi/capsule-loader: Use a cached copy of the
capsule header") refactored the capsule loading code that maps the
capsule header, to avoid having to map it several times. However,
as it turns out, the vmap() call we ended up removing did not just
map the header, but the entire capsule image, and dropping this
virtual mapping breaks capsules that are processed by the firmware
immediately (i.e., without a reboot).
[FIX]
The following patch fixes the issue
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/firmware/efi/capsule-loader.c?id=f24c4d478013d82bd1b943df566fff3561d52864
[TEST]
Please see comments below for testing information and details.
[REGRESSION POTENTIAL]
This patch fixes a regression in 4.13 and onward.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746019/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1745032] Re: AC adapter status not detected on Asus ZenBook UX410UAK
** Changed in: linux (Ubuntu) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1745032 Title: AC adapter status not detected on Asus ZenBook UX410UAK Status in linux package in Ubuntu: Fix Committed Bug description: === SRU Justification === [Impact] Some Asus laptops report "discharging" when the battery is full and AC is plugged [Test] Charge battery to full, the issue appears. Users report with the patch the behaviour is correct. [Fix] The discharge rate is 0 on those machines. Use that to detect the wrong status report. [Regression Potential] Low. The quirk uses strict DMI to match affected systems. === Original Bug Report === The AC adapter status is incorrectly reported when the battery is fully charged. It always shows as if the adapter is not plugged in. If the battery is drained for a while, the adapter status is shown correctly (both connects and disconnects are shown). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-31-generic 4.13.0-31.34 ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13 Uname: Linux 4.13.0-31-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: abarto 1388 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Jan 23 18:26:18 2018 InstallationDate: Installed on 2018-01-23 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 04f2:b57a Chicony Electronics Co., Ltd Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX410UAK ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed root=UUID=58ea0561-3f74-4566-9332-5e7021275160 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-31-generic N/A linux-backports-modules-4.13.0-31-generic N/A linux-firmware 1.169.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX410UAK.306 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX410UAK 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.:bvrUX410UAK.306:bd08/08/2017:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX410UAK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1745032/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1738334] Re: hisilicon hibmc regression due to ea642c3216cb ("drm/ttm: add io_mem_pfn callback")
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Assignee: Daniel Axtens (daxtens)
Status: Confirmed
** Changed in: linux (Ubuntu Bionic)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1738334
Title:
hisilicon hibmc regression due to ea642c3216cb ("drm/ttm: add
io_mem_pfn callback")
Status in Linux:
New
Status in linux package in Ubuntu:
Fix Committed
Status in linux source package in Artful:
Fix Released
Status in linux source package in Bionic:
Fix Committed
Bug description:
[SRU Justification]
[Impact]
On Artful and Bionic kernels, X fails to start and a kernel splat is printed.
This is cbecause ea642c3216cb ("drm/ttm: add io_mem_pfn callback") is
incomplete: the hisilicon hibmc driver does not contain the callback
and so the kernel tries to execute code at NULL.
[Fix]
Bionic: There is a generic fix in 4.16 at
c67fa6edc8b11afe22c88a23963170bf5f151acf. It is part of a series that
applies this generic fix and does a bunch of cleanups; we can safely
just pick up the generic fix.
Artful: Rather than a generic fix, I have submitted a very very
minimal fix that only touches hibmc.
[Regression Potential]
Artful: Minimal - fix only touches hibmc driver. Tested on D05 board.
Bionic: fix is to generic drm code, but is small and easily reviewable.
[Testcase]
Install patched kernel, try to start X. If it succeeds, the fix works. If
there's a kernel splat, the fix does not work.
[Notes]
Artful: HiSilicon would really like this fix in Artful in such time so that
when the next 16.04 point release ships, the HWE kernel will work with Xorg.
Bionic: no extra notes.
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1738334/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1661876] Re: [Asus UX360UA] battery status in unity-panel is not changing when battery is being charged
** Changed in: linux (Ubuntu) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1661876 Title: [Asus UX360UA] battery status in unity-panel is not changing when battery is being charged Status in linux package in Ubuntu: Fix Committed Bug description: === SRU Justification === [Impact] Some Asus laptops report "discharging" when the battery is full and AC is plugged [Test] Charge battery to full, the issue appears. Users report with the patch the behaviour is correct. [Fix] The discharge rate is 0 on those machines. Use that to detect the wrong status report. [Regression Potential] Low. The quirk uses strict DMI to match affected systems. === Original Bug Report === I've just installed Ubuntu 16.04.1 in dualboot on top of an Asus UX360UA, alongside with Windows 10. I've already installed the updates meanwhile. When I start charging my computer the battery icon on the unity-panel is not changing (it stays in the 98% complete). This is strange because this is a fresh installation so I didn't change any configuration yet. Also, when I tried this ubuntu in the live pen, I noticed that the icon changed when I started charging the laptop. That's why I think it is a bug. --- ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tjiagom1806 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=0eaf9255-c29a-41b7-8449-1eb52f637933 InstallationDate: Installed on 2017-02-04 (0 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 04f2:b56b Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX360UA Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-62-generic.efi.signed root=UUID=6ca1f963-632a-401d-80db-610ef37f1f26 ro quiet splash ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40 RelatedPackageVersions: linux-restricted-modules-4.4.0-62-generic N/A linux-backports-modules-4.4.0-62-generic N/A linux-firmware1.157.6 Tags: xenial Uname: Linux 4.4.0-62-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/17/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX360UA.300 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX360UA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX360UA.300:bd06/17/2016:svnASUSTeKCOMPUTERINC.:pnUX360UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX360UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: UX360UA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1661876/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1482390] Re: ASUS UX305LA - Battery state not detected correctly
** Changed in: linux (Ubuntu) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1482390 Title: ASUS UX305LA - Battery state not detected correctly Status in linux package in Ubuntu: Fix Committed Bug description: === SRU Justification === [Impact] Some Asus laptops report "discharging" when the battery is full and AC is plugged [Test] Charge battery to full, the issue appears. Users report with the patch the behaviour is correct. [Fix] The discharge rate is 0 on those machines. Use that to detect the wrong status report. [Regression Potential] Low. The quirk uses strict DMI to match affected systems. === Original Bug Report === Whether the AC adapter is connected or not, the battery is always detected as discharging: When AC adapter is present: $ sudo acpitool -a -b Battery #1 : Discharging, 100.0% AC adapter : online $ sudo acpitool -B Battery #1 : present Remaining capacity : 54027 mWh, 100.0% Design capacity: 56041 mWh Last full capacity : 53507 mWh, 95.48% of design capacity Capacity loss : 4.522% Present rate : 0 mW Charging state : Discharging Battery type : Li-ion Model number : ASUS When AC adapter is not present: $ sudo acpitool -a -b Battery #1 : Discharging, 100.0%, 04:19:49 AC adapter : off-line $ sudo acpitool -B Battery #1 : present Remaining capacity : 54005 mWh, 100.0%, 04:28:31 Design capacity: 56041 mWh Last full capacity : 53507 mWh, 95.48% of design capacity Capacity loss : 4.522% Present rate : 12067 mW Charging state : Discharging Battery type : Li-ion Model number : ASUS System information: $ sudo dmidecode # dmidecode 2.12 # SMBIOS entry point at 0xace2a898 SMBIOS 2.8 present. 27 structures occupying 2154 bytes. Table at 0xAC7C6000. Handle 0x, DMI type 0, 24 bytes BIOS Information Vendor: American Megatrends Inc. Version: UX305LA.202 Release Date: 04/16/2015 Address: 0xF Runtime Size: 64 kB ROM Size: 6464 kB Characteristics: PCI is supported BIOS is upgradeable BIOS shadowing is allowed Boot from CD is supported Selectable boot is supported BIOS ROM is socketed EDD is supported 5.25"/1.2 MB floppy services are supported (int 13h) 3.5"/720 kB floppy services are supported (int 13h) 3.5"/2.88 MB floppy services are supported (int 13h) Print screen service is supported (int 5h) 8042 keyboard services are supported (int 9h) Serial services are supported (int 14h) Printer services are supported (int 17h) ACPI is supported USB legacy is supported Smart battery is supported BIOS boot specification is supported Targeted content distribution is supported UEFI is supported BIOS Revision: 5.6 Handle 0x0001, DMI type 1, 27 bytes System Information Manufacturer: ASUSTeK COMPUTER INC. Product Name: UX305LA Version: 1.0 Serial Number: xxx UUID: xxx Wake-up Type: Power Switch SKU Number: ASUS-NotebookSKU Family: UX Handle 0x0002, DMI type 2, 15 bytes Base Board Information Manufacturer: ASUSTeK COMPUTER INC. Product Name: UX305LA Version: 1.0 Serial Number: xxx Asset Tag: xxx Features: Board is a hosting board Board is replaceable Location In Chassis: MIDDLE Chassis Handle: 0x0003 Type: Motherboard Contained Object Handles: 0 Handle 0x0003, DMI type 3, 25 bytes Chassis Information Manufacturer: ASUSTeK COMPUTER INC. Type: Notebook Lock: Not Present Version: 1.0 Serial Number: xxx Asset Tag: xxx Boot-up State: Safe Power Supply State: Safe Thermal State: Safe Security Status: None OEM Information: 0x Height: Unspecified Number Of Power Cords: 1 Contained Elements: 1 (0) SKU Number: To be filled by O.E.M. Handle 0x0004, DMI type 10, 26 bytes On Board Device 1 Information Type: Video Status: Enabled Description: VGA On Board Device 2 Information Type: Ethernet Status: Enabled Description: GLAN On Board Device 3 Information Type: Ethernet Status: Enabled Description: WLAN On Board Device 4 Information Type: Sound Status: Enabled Description: Audio CODEC On Board Device 5 Information Type: SATA Controller Status: Enabled Description: SATA Controller On Board Device 6 Information Type: Other Status: Enabled Description: USB 2.0 Controller On Board Device 7 Information Type: Other Status: Enabled Description: USB 3.0 Controller On Board Device 8 Information Type: Other Status: Enabled Description: SMBus Controller On Board Device 9 Info
[Kernel-packages] [Bug 1748567] Re: ethtool -p fails to light NIC LED on HiSilicon D05 systems
** Changed in: linux (Ubuntu Artful) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1748567 Title: ethtool -p fails to light NIC LED on HiSilicon D05 systems Status in linux package in Ubuntu: Fix Released Status in linux source package in Artful: Fix Committed Status in linux source package in Bionic: Fix Released Bug description: [Impact] ethtool -p doesn't work for HiSilicon D05 onboard 10G NICs. From ethtool(8): -%<--- -p --identify Initiates adapter-specific action intended to enable an operator to easily identify the adapter by sight. Typically this involves blinking one or more LEDs on the spe‐ cific network port. -%<--- [Test Case] Run "ethtool -p " for one of the impacted NIC interfaces. Watch for blinky light. [Regression Risk] Fix is local to a specific driver for onboard NICs, and a clean upstream cherry-pick. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1748567/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1742892] Re: [Power 9] ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3: Unable to start the guest with more than 1 thread on ubuntu1804 KVM host machine.
** 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/1742892 Title: [Power 9] ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3: Unable to start the guest with more than 1 thread on ubuntu1804 KVM host machine. Status in The Ubuntu-power-systems project: Fix Released Status in linux package in Ubuntu: Incomplete Status in qemu package in Ubuntu: Fix Released Bug description: == Comment: #0 - INDIRA P. JOGA - 2018-01-07 13:18:32 == Problem Description: === Not able to start the ubutnu1804 guest with more than 1 thread on ubuntu1804 KVM host machine Steps to re-create: == > Installed Ubuntu1804 on boslcp3 host. root@boslcp3:/home# uname -a Linux boslcp3 4.13.0-17-generic #20-Ubuntu SMP Mon Nov 6 10:03:08 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux root@boslcp3:/home# uname -r 4.13.0-17-generic > Installed qemu-kvm libvirt-bin ubuntu-vm-builder bridge-utils packages root@boslcp3:/home# virsh version Compiled against library: libvirt 3.6.0 Using library: libvirt 3.6.0 Using API: QEMU 3.6.0 Running hypervisor: QEMU 2.10.1 > root@boslcp3:~# ppc64_cpu --smt SMT is off > Defined the guest boslcp3g1 from host machine root@boslcp3:/home# virsh list --all IdName State - boslcp3g1 shut off Please cherry pick commit 45c940ba490df28cb87b993981a5f63df6bbb8db Author: Paul Mackerras Date: Fri Nov 18 17:43:30 2016 +1100 KVM: PPC: Book3S HV: Treat POWER9 CPU threads as independent subcores > Started the guest and it fails with the error root@boslcp3:~# virsh start --console boslcp3g1 error: Failed to start domain boslcp3g1 error: internal error: process exited while connecting to monitor: 2018-01-05T02:54:37.762120Z qemu-system-ppc64: -chardev pty,id=charserial0: char device redirected to /dev/pts/3 (label charserial0) 2018-01-05T02:54:37.829236Z qemu-system-ppc64: Cannot support more than 1 threads on PPC with KVM > Unable to start the guest with more than 1 Thread from Ubuntu1804 KVM host machine. XML: root@boslcp3:/home# virsh dumpxml boslcp3g1 boslcp3g1 95374879-0ed3-4562-a00f-e47d9aaf285c 10485760 6291456 6291456 32 /machine hvm power9 destroy restart coredump-restart /usr/bin/qemu-system-ppc64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1742892/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1751994] Re: ppc64el: Support firmware disable of RFI flush
Can we increase the priority of this bug from medium to high, please? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1751994 Title: ppc64el: Support firmware disable of RFI flush Status in The Ubuntu-power-systems project: Triaged Status in linux package in Ubuntu: New Bug description: == Comment: #0 - Breno Leitao - 2018-02-26 13:59:55 == Hi Canonical, We still need some changes regarding spectre and meltdown. We need to backport the following commit to all supported kernel. I undertand that the backport for kernel 4.XX should be trivial. Not sure about kernel 3.13 yet. https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=582605a429e20ae68fd0b041b2e840af296edd08 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=eb0a2d2620ae431c543963c8c7f08f597366fc60 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1751994/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1751266] Re: Missing firmware in linux-image-4.15.0-10-generic
Just installed today's (1st March 2018) daily server CD image on a Dell server with Broadcom BCM5716 chips and have had the same issue with the bnx2 firmware missing, it failed on both the network configuration and after install. -- 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/1751266 Title: Missing firmware in linux-image-4.15.0-10-generic Status in linux package in Ubuntu: Invalid Status in linux-firmware package in Ubuntu: Triaged Status in linux source package in Bionic: Invalid Status in linux-firmware source package in Bionic: Triaged Bug description: linux-image-4.15.0-10-generic doesn't have the firmware that linux- image-4.13.0-32-generic has. It doesn't have any of the files that are present in 4.13 in /lib/firmware/4.13.0-32-generic/. For me, this means i can boot 4.15, but my network wont work because of: kernel: [ 13.468996] bnx2 :0b:00.0: Direct firmware load for bnx2/bnx2-mips-09-6.2.1b.fw failed with error -2 kernel: [ 13.468998] bnx2: Can't load firmware file "bnx2/bnx2-mips-09-6.2.1b.fw" ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-10-generic 4.15.0-10.11 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 feb 23 13:12 seq crw-rw 1 root audio 116, 33 feb 23 13:12 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.8-0ubuntu10 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: Date: Fri Feb 23 13:50:38 2018 InstallationDate: Installed on 2018-02-14 (9 days ago) InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180212) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: IBM System x3550 M3 -[7944S77]- PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed root=UUID=4a958e16-f948-4619-bad5-51d238213cc5 ro RelatedPackageVersions: linux-restricted-modules-4.13.0-32-generic N/A linux-backports-modules-4.13.0-32-generic N/A linux-firmware 1.171 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/26/2012 dmi.bios.vendor: IBM Corp. dmi.bios.version: -[D6E158AUS-1.16]- dmi.board.asset.tag: (none) dmi.board.name: 00D4062 dmi.board.vendor: IBM dmi.board.version: (none) dmi.chassis.asset.tag: none dmi.chassis.type: 23 dmi.chassis.vendor: IBM dmi.chassis.version: none dmi.modalias: dmi:bvnIBMCorp.:bvr-[D6E158AUS-1.16]-:bd11/26/2012:svnIBM:pnSystemx3550M3-[7944S77]-:pvr00:rvnIBM:rn00D4062:rvr(none):cvnIBM:ct23:cvrnone: dmi.product.family: System x dmi.product.name: System x3550 M3 -[7944S77]- dmi.product.version: 00 dmi.sys.vendor: IBM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1751266/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1739498] Re: Ubuntu 17.10 crashes on vmalloc.c
** Changed in: linux (Ubuntu Artful)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1739498
Title:
Ubuntu 17.10 crashes on vmalloc.c
Status in The Ubuntu-power-systems project:
In Progress
Status in linux package in Ubuntu:
Fix Committed
Status in linux source package in Artful:
Fix Committed
Status in linux source package in Bionic:
Fix Committed
Bug description:
== SRU Justification ==
IBM is seeing a crash on Power9 when running on Artful.
This issue happens only when disabling RPT ("disable_radix"), which is not
the default in Artful.
These fixes are already in Bionic master-next, so they are only being
requested
in Artful.
== Fixes ==
63ee9b2ff9d3 ("powerpc/mm/book3s64: Make KERN_IO_START a variable")
b5048de04b32 ("powerpc/mm/slb: Move comment next to the code it's")
21a0e8c14bf6 ("powerpc/mm/hash64: Make vmalloc 56T on hash")
== Regression Potential ==
These commits are specific to powerpc and fix a crash.
== 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.
== Comment: #0 - Breno Leitao - 2017-12-19 09:48:10 ==
When running Ubuntu 17.10 on POWER9, I got the following error:
[409038.118908] WARNING: CPU: 47 PID: 294 at
/build/linux-LIHoWc/linux-4.13.0/mm/vmalloc.c:2527 pcpu_get_vm_areas+0x62c/0x660
[409038.118909] Modules linked in: xt_CHECKSUM iptable_mangle ipt_MASQUERADE
nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4
nf_defrag_ipv4 xt_conntrack nf_conntrack libcrc32c ipt_REJECT nf_reject_ipv4
xt_tcpudp bridge stp llc ebtable_filter ebtables ip6table_filter ip6_tables
iptable_filter kvm_hv kvm at24 ofpart ipmi_powernv ipmi_devintf ipmi_msghandler
cmdlinepart powernv_flash uio_pdrv_genirq uio mtd vmx_crypto ibmpowernv
crct10dif_vpmsum opal_prd binfmt_misc ip_tables x_tables autofs4 crc32c_vpmsum
ast i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops
ttm drm tg3 ahci libahci
[409038.118933] CPU: 47 PID: 294 Comm: kworker/47:0 Tainted: GW
4.13.0-12-generic #13-Ubuntu
[409038.118934] Workqueue: events pcpu_balance_workfn
[409038.118936] task: c03fe3cdcc00 task.stack: c03fe3be
[409038.118937] NIP: c032c1fc LR: c02f5fd4 CTR:
[409038.118937] REGS: c03fe3be3810 TRAP: 0700 Tainted: GW
(4.13.0-12-generic)
[409038.118938] MSR: 9282b033
[409038.118944] CR: 24024828 XER: 2004
[409038.118944] CFAR: c032bdb8 SOFTE: 1
GPR00: 2df0 c03fe3be3a90 c15e3000
c000203fff6b6880
GPR04: c000203fff223608 0008 c000203fff6b6888
GPR08: 2df0 0800 0160
c000203fff6b6888
GPR12: 0002 cfaded80 c0f6c050
c03fe3be3bc0
GPR16: 0010 c189daf8
c000203fff223608
GPR20: 2f50 c000203fff2235f8 c000203fff223600
GPR24: c000203fff6b6888 0001
2f50
GPR28: 0002 000f d800
d000
[409038.118963] NIP [c032c1fc] pcpu_get_vm_areas+0x62c/0x660
[409038.118964] LR [c02f5fd4] pcpu_create_chunk+0xb4/0x1b0
[409038.118965] Call Trace:
[409038.118966] [c03fe3be3a90] [c03fe3be3ad0] 0xc03fe3be3ad0
(unreliable)
[409038.118968] [c03fe3be3b60] [c02f5fd4]
pcpu_create_chunk+0xb4/0x1b0
[409038.118970] [c03fe3be3ba0] [c02f7890]
pcpu_balance_workfn+0x600/0x960
[409038.118972] [c03fe3be3ca0] [c01205d8]
process_one_work+0x298/0x5a0
[409038.118975] [c03fe3be3d30] [c0120968] worker_thread+0x88/0x620
[409038.118977] [c03fe3be3dc0] [c012980c] kthread+0x1ac/0x1c0
[409038.118979] [c03fe3be3e30] [c000b4e8]
ret_from_kernel_thread+0x5c/0x74
[409038.118980] Instruction dump:
[409038.118981] eae3 4191fad0 7ed3b378 e9210030 7efbbb78 7c791b78
3b40 e953
---uname output---
4.13.0-12-generic
== Comment: #3 - ANEESH K. K V - 2017-12-20 05:59:13 ==
https://lkml.kernel.org/r/1501583364-14909-1-git-send-email-...@ellerman.id.au
The above may be related?
Related discussions
https://lkml.kernel.org/r/20170724134240.gl25...@dhcp22.suse.cz
-aneesh
== Comment: #4 - Breno Leitao - 2017-12-20 09:48:07 ==
I just tested with kernel 4.15.0-041500rc4 and I didn't see a problem so far.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1739498/+subscriptions
--
Mailing list: https
[Kernel-packages] [Bug 1746970] Re: lpfc.ko module doesn't work
** Changed in: linux (Ubuntu Artful) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1746970 Title: lpfc.ko module doesn't work Status in linux package in Ubuntu: Fix Committed Status in linux source package in Artful: Fix Committed Status in linux source package in Bionic: Fix Committed Bug description: == SRU Justification == The bug reporter stated that the HBA Emulex LPe12000 Fibre channel adapter does not see the disk on direct attach. Broadcom support confirmed that bug and suggested to update module. It was found that commit 2877cbf is the fix for this bug. Commit 2877cbf is in mainline as of v4.14-rc1. == Fix == commit 2877cbffb79ed121a6bcc5edbe629d3aba36cd29 Author: Dick Kennedy Date: Wed Aug 23 16:55:31 2017 -0700 scsi: lpfc: Fix loop mode target discovery == Regression Potential == Low. Clean cherry pick and only adds a new check for loop mode. == Test Case == A test kernel was built with this patch and tested by the original bug reporter. The bug reporter states the test kernel resolved the bug. == Original Bug Description == Hi. I have problem with HBA Emulex LPe12000 Fibre channel adapter. It doesn't see disk on direct attach. [4.015493] lpfc :04:00.0: 0:1303 Link Up Event x1 received Data: x1 x1 x10 x2 x0 x0 0 [4.015570] lpfc :04:00.0: 0:1309 Link Up Event npiv not supported in loop topology [4.016671] lpfc :04:00.0: 0:(0):2858 FLOGI failure Status:x3/x18 TMO:x0 Data x1000 x0 [4.017627] lpfc :04:00.0: 0:(0):2858 FLOGI failure Status:x3/x18 TMO:x0 Data x1000 x0 [4.018561] lpfc :04:00.0: 0:(0):2858 FLOGI failure Status:x3/x18 TMO:x0 Data x1000 x0 [4.018636] lpfc :04:00.0: 0:(0):0100 FLOGI failure Status:x3/x18 TMO:x0 [4.019713] lpfc :04:00.0: 0:(0):0266 Issue NameServer Req x117 err 1 Data: x8 x0 I have made a little investigation. Ubuntu 16.04.3 LTS, kernel 4.10.0-28, lpfc 11.2.0.2 - no problem. Ubuntu 17.10.1, kernel 4.13.0-21, lpfc 11.4.0.1 - problem. Debian 9.3, kernel 4.9.0-4, lpfc 11.2.0.0 - no problem. Fedora 27, kernel 4.13.9-300, lpfc 11.4.0.1 - problem. Proxmox 5.0, kernel 4.10.15-1, lpfc 11.2.0.2 - no problem. Proxmox 5.1, kernel 4.13.13-5, lpfc 11.4.0.1 - problem. Another user with this problem said that if fiber switch is added between the server and the storage it's working as expected. I think problem is in lpfc.ko 11.4.0.1. Any kernel (4.13 now) that has this module version is affected. Broadcom support confirmed that bug and suggested to update module. But Broadcom supports only RHEL and SLES. I tried to compile, but no luck. Please, could you update lpfc.ko module in linux-image-generic package? There are version 11.4.142.21 for SLES 12 and 11.4.204.11 for RHEL 6 and 7 on Broadcom site. Thanks. --- 04:00.0 Fibre Channel [0c04]: Emulex Corporation Saturn-X: LightPulse Fibre Channel Host Adapter [10df:f100] (rev 03) Subsystem: Emulex Corporation Saturn-X: LightPulse Fibre Channel Host Adapter [10df:f100] Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR+ FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel modules: lpfc --- ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperVersion: 1.387 DistroRelease: Ubuntu 17.10 LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) MachineType: HP ProLiant DL160 G6 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcFB: 0 mgadrmfb ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd.lz quiet splash --- debian-installer/language=ru keyboard-configuration/layoutcode?=ru ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13 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.13.0-21-generic N/A linux-backports-modules-4.13.0-21-generic N/A linux-firmware 1.169.1 RfKill: Tags: artful Uname: Linux 4.13.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 05/19/2010 dmi.bios.vendor: HP dmi.bios.version: O33 dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrO33:bd05/19/2010:svnHP:pnProLiantDL160G6:pvr:cvnHP:ct23:cvr: dmi.product.name: ProLiant DL160 G6 dmi.sys.vendor: HP To
[Kernel-packages] [Bug 1752026] Re: Ubuntu18.04:POWER9:DD2.2 - Unable to start a KVM guest with default machine type(pseries-bionic) complaining "KVM implementation does not support Transactional Memo
Status changed to 'Confirmed' because the bug affects multiple users. ** 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/1752026 Title: Ubuntu18.04:POWER9:DD2.2 - Unable to start a KVM guest with default machine type(pseries-bionic) complaining "KVM implementation does not support Transactional Memory, try cap-htm=off" (kvm) Status in The Ubuntu-power-systems project: Incomplete Status in linux package in Ubuntu: Confirmed Status in qemu package in Ubuntu: Incomplete Bug description: == Comment: #0 - Satheesh Rajendran - 2018-02-23 08:31:06 == ---Problem Description--- libvirt unable to start a KVM guest complaining about cap-htm machine property to be off Host Env: # lscpu Architecture:ppc64le Byte Order: Little Endian CPU(s): 160 On-line CPU(s) list: 0-159 Thread(s) per core: 4 Core(s) per socket: 20 Socket(s): 2 NUMA node(s):2 Model: 2.2 (pvr 004e 1202) Model name: POWER9 (raw), altivec supported CPU max MHz: 3800. CPU min MHz: 2166. L1d cache: 32K L1i cache: 32K L2 cache:512K L3 cache:10240K NUMA node0 CPU(s): 0-79 NUMA node8 CPU(s): 80-159 ii qemu-kvm 1:2.11+dfsg-1ubuntu2 ppc64el QEMU Full virtualization on x86 hardware ii libvirt-bin 4.0.0-1ubuntu3 ppc64el programs for the libvirt library # lsmcode Version of System Firmware : Product Name : OpenPOWER Firmware Product Version : open-power-SUPERMICRO-P9DSU-V1.03-20180205-imp Product Extra : occ-577915f Product Extra : skiboot-v5.9-240-g081882690163-pcbedce4 Product Extra : petitboot-v1.6.6-p019c87e Product Extra : sbe-095e608 Product Extra : machine-xml-fb5f933 Product Extra : hostboot-9bfb201 Product Extra : linux-4.14.13-openpower1-p78d7eee Contact Information = sathe...@in.ibm.com ---uname output--- 4.15.0-10-generic Machine Type = power9 boston 2.2 (pvr 004e 1202) ---Debugger--- A debugger is not configured ---Steps to Reproduce--- 1. Boot a guest from libvirt with default pseries machine type or pseries-bionic /usr/bin/virt-install --connect=qemu:///system --hvm --accelerate --name 'virt-tests-vm1' --machine pseries --memory=32768 --vcpu=32,sockets=1,cores=32,threads=1 --import --nographics --serial pty --memballoon model=virtio --controller type=scsi,model=virtio-scsi --disk path=/var/lib/libvirt/images/workspace/runAvocadoFVTTest/avocado-fvt-wrapper/data/avocado-vt/images/ubuntu-18.04-ppc64le.qcow2,bus=scsi,size=10,format=qcow2 --network=bridge=virbr0,model=virtio,mac=52:54:00:77:78:79 --noautoconsole WARNING No operating system detected, VM performance may suffer. Specify an OS with --os-variant for optimal results. Starting install... ERRORinternal error: process exited while connecting to monitor: ,id=scsi0-0-0-0,bootindex=1 -netdev tap,fd=24,id=hostnet0,vhost=on,vhostfd=26 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:77:78:79,bus=pci.0,addr=0x1 -chardev pty,id=charserial0 -device spapr-vty,chardev=charserial0,id=serial0,reg=0x3000 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x4 -msg timestamp=on 2018-02-23T14:21:11.081809Z qemu-system-ppc64: KVM implementation does not support Transactional Memory, try cap-htm=off Domain installation does not appear to have been successful. If it was, you can restart your domain by running: virsh --connect qemu:///system start virt-tests-vm1 otherwise, please restart your installation. 2. Fails to boot.. Note: if we specify machine type as pseries=2.12 it boots fine like below /usr/bin/virt-install --connect=qemu:///system --hvm --accelerate --name 'virt-tests-vm1' --machine pseries-2.12 --memory=32768 --vcpu=32,sockets=1,cores=32,threads=1 --import --nographics --serial pty --memballoon model=virtio --controller type=scsi,model=virtio-scsi --disk path=/var/lib/libvirt/images/workspace/runAvocadoFVTTest/avocado-fvt-wrapper/data/avocado-vt/images/ubuntu-18.04-ppc64le.qcow2,bus=scsi,size=10,format=qcow2 --network=bridge=virbr0,model=virtio,mac=52:54:00:77:78:79 --noautoconsole WARNING No operating system detected, VM performance may suffer. Specify an OS with --os-variant for optimal results. qemu-cmd line: libvirt+ 4283 1 99 09:26 ?00:00:38 qemu-system-ppc64 -enable-kvm -name guest=virt-tests-vm1,debug-threads=on -S -object secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-4 -virt-tests-vm1/master-key.aes -machine pseries-2.12,accel=kvm
[Kernel-packages] [Bug 1747523] Re: support thunderx2 vendor pmu events
** Changed in: linux (Ubuntu Artful) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1747523 Title: support thunderx2 vendor pmu events Status in linux package in Ubuntu: Fix Released Status in linux source package in Artful: Fix Committed Status in linux source package in Bionic: Fix Released Bug description: [Impact] ThunderX2 vendor pmu events are not supported. [Test Case] Successful output: $ sudo perf list | grep thunderx2 thunderx2 imp def: $ [Regression Risk] The code changes are restricted to the perf utility, so there's negligible risk to the kernel itself. All patches are clean cherry-picks except 1 where a hunk is dropped that was updating an API in code that didn't exist yet. I've tested on Cavium Sabre (a thunderx2 system), and smoke tested perf commands for regression on x86 (Dell XPS13 9350). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1747523/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1751994] Re: ppc64el: Support firmware disable of RFI flush
Certainly. Priority bumped. ** Changed in: ubuntu-power-systems Importance: Medium => High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1751994 Title: ppc64el: Support firmware disable of RFI flush Status in The Ubuntu-power-systems project: Triaged Status in linux package in Ubuntu: New Bug description: == Comment: #0 - Breno Leitao - 2018-02-26 13:59:55 == Hi Canonical, We still need some changes regarding spectre and meltdown. We need to backport the following commit to all supported kernel. I undertand that the backport for kernel 4.XX should be trivial. Not sure about kernel 3.13 yet. https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=582605a429e20ae68fd0b041b2e840af296edd08 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=eb0a2d2620ae431c543963c8c7f08f597366fc60 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1751994/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1747572] [NEW] CIFS SMB2/SMB3 does not work for domain based DFS
You have been subscribed to a public bug: There is upstream bug report: https://bugzilla.samba.org/show_bug.cgi?id=12917 "Fix was merged upstream and should be in the next kernel update. Ask your distribution maintainers to backport it." Aurélien Aptel It looks like the following patches should be backported: [v3,3/3] CIFS: dump IPC tcon in debug proc file [v3,2/3] CIFS: use tcon_ipc instead of use_ipc parameter of SMB2_ioctl [v3,1/3] CIFS: make IPC a regular tcon Link to patchwork: https://patchwork.kernel.org/project/cifs- client/list/?submitter=146481 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.13.0-32-generic 4.13.0-32.35~16.04.1 ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Tue Feb 6 09:50:57 2018 SourcePackage: linux-hwe UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: cifs-utils Importance: Unknown Status: Unknown ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- CIFS SMB2/SMB3 does not work for domain based DFS https://bugs.launchpad.net/bugs/1747572 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1751266] Re: Missing firmware in linux-image-4.15.0-10-generic
Quick, very temporary, and very dirty hack, copy the Debian firmware-bnx2 package to the machine and dpkg -i it: https://packages.debian.org/buster/all/firmware-bnx2/download netplan apply then brings the network up immediately, and only the firmware for bnx2 was copied. Obviously the Ubuntu linux-firmware package ought to have it in before Bionic's release, but it's a quick workaround. -- 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/1751266 Title: Missing firmware in linux-image-4.15.0-10-generic Status in linux package in Ubuntu: Invalid Status in linux-firmware package in Ubuntu: Triaged Status in linux source package in Bionic: Invalid Status in linux-firmware source package in Bionic: Triaged Bug description: linux-image-4.15.0-10-generic doesn't have the firmware that linux- image-4.13.0-32-generic has. It doesn't have any of the files that are present in 4.13 in /lib/firmware/4.13.0-32-generic/. For me, this means i can boot 4.15, but my network wont work because of: kernel: [ 13.468996] bnx2 :0b:00.0: Direct firmware load for bnx2/bnx2-mips-09-6.2.1b.fw failed with error -2 kernel: [ 13.468998] bnx2: Can't load firmware file "bnx2/bnx2-mips-09-6.2.1b.fw" ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-10-generic 4.15.0-10.11 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 feb 23 13:12 seq crw-rw 1 root audio 116, 33 feb 23 13:12 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.8-0ubuntu10 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: Date: Fri Feb 23 13:50:38 2018 InstallationDate: Installed on 2018-02-14 (9 days ago) InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180212) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: IBM System x3550 M3 -[7944S77]- PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed root=UUID=4a958e16-f948-4619-bad5-51d238213cc5 ro RelatedPackageVersions: linux-restricted-modules-4.13.0-32-generic N/A linux-backports-modules-4.13.0-32-generic N/A linux-firmware 1.171 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/26/2012 dmi.bios.vendor: IBM Corp. dmi.bios.version: -[D6E158AUS-1.16]- dmi.board.asset.tag: (none) dmi.board.name: 00D4062 dmi.board.vendor: IBM dmi.board.version: (none) dmi.chassis.asset.tag: none dmi.chassis.type: 23 dmi.chassis.vendor: IBM dmi.chassis.version: none dmi.modalias: dmi:bvnIBMCorp.:bvr-[D6E158AUS-1.16]-:bd11/26/2012:svnIBM:pnSystemx3550M3-[7944S77]-:pvr00:rvnIBM:rn00D4062:rvr(none):cvnIBM:ct23:cvrnone: dmi.product.family: System x dmi.product.name: System x3550 M3 -[7944S77]- dmi.product.version: 00 dmi.sys.vendor: IBM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1751266/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1747572] Re: CIFS SMB2/SMB3 does not work for domain based DFS
** Package changed: linux-hwe (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: Confirmed => New ** Tags added: kernel-da-key ** Also affects: linux (Ubuntu Artful) 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/1747572 Title: CIFS SMB2/SMB3 does not work for domain based DFS Status in cifs-utils: Unknown Status in linux package in Ubuntu: Triaged Status in linux source package in Artful: Triaged Bug description: There is upstream bug report: https://bugzilla.samba.org/show_bug.cgi?id=12917 "Fix was merged upstream and should be in the next kernel update. Ask your distribution maintainers to backport it." Aurélien Aptel It looks like the following patches should be backported: [v3,3/3] CIFS: dump IPC tcon in debug proc file [v3,2/3] CIFS: use tcon_ipc instead of use_ipc parameter of SMB2_ioctl [v3,1/3] CIFS: make IPC a regular tcon Link to patchwork: https://patchwork.kernel.org/project/cifs- client/list/?submitter=146481 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.13.0-32-generic 4.13.0-32.35~16.04.1 ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Tue Feb 6 09:50:57 2018 SourcePackage: linux-hwe UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/cifs-utils/+bug/1747572/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1749040] Re: KPTI support for arm64 systems
I see 5 failures marked as blocker there: 4 couldn't complete due to the test environment, and 1[*], apparently, is a CONFIG issue (so something that predates this patchset). Let's see what the other boards report. 1: https://launchpadlibrarian.net/359043692/submission_2018-03-01T05.58.16.640032.html#7-10-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/1749040 Title: KPTI support for arm64 systems Status in linux package in Ubuntu: Incomplete Status in linux source package in Artful: In Progress Status in linux source package in Bionic: Incomplete Bug description: While regression testing the current linux-hwe proposed kernel (4.13.0-33.36~16.04.1), I found that it fails to boot on a Cavium ThunderX CRB. I've rebooted twice since upgrading from the current -updates kernel, and it's failed to boot both times, with different failure modes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1749040/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1751994] Re: ppc64el: Support firmware disable of RFI flush
** Information type changed from Public to Public Security -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1751994 Title: ppc64el: Support firmware disable of RFI flush Status in The Ubuntu-power-systems project: Triaged Status in linux package in Ubuntu: New Bug description: == Comment: #0 - Breno Leitao - 2018-02-26 13:59:55 == Hi Canonical, We still need some changes regarding spectre and meltdown. We need to backport the following commit to all supported kernel. I undertand that the backport for kernel 4.XX should be trivial. Not sure about kernel 3.13 yet. https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=582605a429e20ae68fd0b041b2e840af296edd08 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=eb0a2d2620ae431c543963c8c7f08f597366fc60 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1751994/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1747572] Re: CIFS SMB2/SMB3 does not work for domain based DFS
** Changed in: linux (Ubuntu Artful) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: New => Triaged ** Changed in: linux (Ubuntu Artful) Status: New => Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1747572 Title: CIFS SMB2/SMB3 does not work for domain based DFS Status in cifs-utils: Unknown Status in linux package in Ubuntu: Triaged Status in linux source package in Artful: Triaged Bug description: There is upstream bug report: https://bugzilla.samba.org/show_bug.cgi?id=12917 "Fix was merged upstream and should be in the next kernel update. Ask your distribution maintainers to backport it." Aurélien Aptel It looks like the following patches should be backported: [v3,3/3] CIFS: dump IPC tcon in debug proc file [v3,2/3] CIFS: use tcon_ipc instead of use_ipc parameter of SMB2_ioctl [v3,1/3] CIFS: make IPC a regular tcon Link to patchwork: https://patchwork.kernel.org/project/cifs- client/list/?submitter=146481 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.13.0-32-generic 4.13.0-32.35~16.04.1 ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Tue Feb 6 09:50:57 2018 SourcePackage: linux-hwe UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/cifs-utils/+bug/1747572/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1752026] Comment bridged from LTC Bugzilla
--- Comment From s...@us.ibm.com 2018-03-01 10:42 EDT--- @paelzer yes, that is us agreeing with your plan >A) We switch the default to HTM=off in qemu "now" (as soon as you ack this) to >be safe >B) If you get the kernel fixes upstream fast enough for the kernel Team to >pick up in time: >... Sorry for the delay. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1752026 Title: Ubuntu18.04:POWER9:DD2.2 - Unable to start a KVM guest with default machine type(pseries-bionic) complaining "KVM implementation does not support Transactional Memory, try cap-htm=off" (kvm) Status in The Ubuntu-power-systems project: Incomplete Status in linux package in Ubuntu: Confirmed Status in qemu package in Ubuntu: Incomplete Bug description: == Comment: #0 - Satheesh Rajendran - 2018-02-23 08:31:06 == ---Problem Description--- libvirt unable to start a KVM guest complaining about cap-htm machine property to be off Host Env: # lscpu Architecture:ppc64le Byte Order: Little Endian CPU(s): 160 On-line CPU(s) list: 0-159 Thread(s) per core: 4 Core(s) per socket: 20 Socket(s): 2 NUMA node(s):2 Model: 2.2 (pvr 004e 1202) Model name: POWER9 (raw), altivec supported CPU max MHz: 3800. CPU min MHz: 2166. L1d cache: 32K L1i cache: 32K L2 cache:512K L3 cache:10240K NUMA node0 CPU(s): 0-79 NUMA node8 CPU(s): 80-159 ii qemu-kvm 1:2.11+dfsg-1ubuntu2 ppc64el QEMU Full virtualization on x86 hardware ii libvirt-bin 4.0.0-1ubuntu3 ppc64el programs for the libvirt library # lsmcode Version of System Firmware : Product Name : OpenPOWER Firmware Product Version : open-power-SUPERMICRO-P9DSU-V1.03-20180205-imp Product Extra : occ-577915f Product Extra : skiboot-v5.9-240-g081882690163-pcbedce4 Product Extra : petitboot-v1.6.6-p019c87e Product Extra : sbe-095e608 Product Extra : machine-xml-fb5f933 Product Extra : hostboot-9bfb201 Product Extra : linux-4.14.13-openpower1-p78d7eee Contact Information = sathe...@in.ibm.com ---uname output--- 4.15.0-10-generic Machine Type = power9 boston 2.2 (pvr 004e 1202) ---Debugger--- A debugger is not configured ---Steps to Reproduce--- 1. Boot a guest from libvirt with default pseries machine type or pseries-bionic /usr/bin/virt-install --connect=qemu:///system --hvm --accelerate --name 'virt-tests-vm1' --machine pseries --memory=32768 --vcpu=32,sockets=1,cores=32,threads=1 --import --nographics --serial pty --memballoon model=virtio --controller type=scsi,model=virtio-scsi --disk path=/var/lib/libvirt/images/workspace/runAvocadoFVTTest/avocado-fvt-wrapper/data/avocado-vt/images/ubuntu-18.04-ppc64le.qcow2,bus=scsi,size=10,format=qcow2 --network=bridge=virbr0,model=virtio,mac=52:54:00:77:78:79 --noautoconsole WARNING No operating system detected, VM performance may suffer. Specify an OS with --os-variant for optimal results. Starting install... ERRORinternal error: process exited while connecting to monitor: ,id=scsi0-0-0-0,bootindex=1 -netdev tap,fd=24,id=hostnet0,vhost=on,vhostfd=26 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:77:78:79,bus=pci.0,addr=0x1 -chardev pty,id=charserial0 -device spapr-vty,chardev=charserial0,id=serial0,reg=0x3000 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x4 -msg timestamp=on 2018-02-23T14:21:11.081809Z qemu-system-ppc64: KVM implementation does not support Transactional Memory, try cap-htm=off Domain installation does not appear to have been successful. If it was, you can restart your domain by running: virsh --connect qemu:///system start virt-tests-vm1 otherwise, please restart your installation. 2. Fails to boot.. Note: if we specify machine type as pseries=2.12 it boots fine like below /usr/bin/virt-install --connect=qemu:///system --hvm --accelerate --name 'virt-tests-vm1' --machine pseries-2.12 --memory=32768 --vcpu=32,sockets=1,cores=32,threads=1 --import --nographics --serial pty --memballoon model=virtio --controller type=scsi,model=virtio-scsi --disk path=/var/lib/libvirt/images/workspace/runAvocadoFVTTest/avocado-fvt-wrapper/data/avocado-vt/images/ubuntu-18.04-ppc64le.qcow2,bus=scsi,size=10,format=qcow2 --network=bridge=virbr0,model=virtio,mac=52:54:00:77:78:79 --noautoconsole WARNING No operating system detected, VM performance may suffer. Specify an OS with --os-variant for optimal results. qemu-cmd line: libvirt+ 4283 1 99 09:26 ?00:00:38 qemu-system-ppc64 -enable-
[Kernel-packages] [Bug 1752621] Re: BUG: unable to handle kernel paging request at ffffded5330000a0
** 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/1752621 Title: BUG: unable to handle kernel paging request at ded533a0 Status in linux package in Ubuntu: Confirmed Bug description: [ 155.111268] BUG: unable to handle kernel paging request at ded533a0 [ 155.111335] IP: kfree+0x53/0x160 [ 155.111357] PGD 0 [ 155.111358] P4D 0 [ 155.111401] Oops: [#1] SMP PTI [ 155.111424] Modules linked in: gpio_ich intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel snd_hda_codec_hdmi kvm snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel irqbypass snd_hda_codec snd_hda_core crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc aesni_intel snd_hwdep aes_x86_64 crypto_simd snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi joydev input_leds glue_helper snd_seq snd_seq_device cryptd snd_timer intel_cstate intel_rapl_perf mei_me shpchp snd mei soundcore lpc_ich mac_hid serio_raw parport_pc ppdev lp parport ip_tables x_tables autofs4 hid_generic usbhid hid i915 video i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt ahci fb_sys_fops r8169 libahci drm mii [ 155.111809] CPU: 0 PID: 1587 Comm: postgres Not tainted 4.13.0-36-generic #40-Ubuntu [ 155.111853] Hardware name: Gigabyte Technology Co., Ltd. H67A-USB3-B3/H67A-USB3-B3, BIOS F7 03/27/2012 [ 155.111906] task: 8e971b4845c0 task.stack: 9c1bc2e7c000 [ 155.111942] RIP: 0010:kfree+0x53/0x160 [ 155.111966] RSP: 0018:9c1bc2e7fce8 EFLAGS: 00010282 [ 155.111998] RAX: RBX: 00102aa3 RCX: 0003 [ 155.112039] RDX: 2d8460201cf0 RSI: 00010080 RDI: 716c4000 [ 155.112080] RBP: 9c1bc2e7fd00 R08: 00025d80 R09: bafc6a19 [ 155.112121] R10: ded53380 R11: R12: 8e974abe7800 [ 155.112162] R13: baba74d4 R14: R15: 8e9714f4d3c0 [ 155.112204] FS: () GS:8e975fa0() knlGS: [ 155.112250] CS: 0010 DS: ES: CR0: 80050033 [ 155.112285] CR2: ded533a0 CR3: 00022c20a001 CR4: 000606f0 [ 155.112326] Call Trace: [ 155.112349] security_sk_free+0x44/0x60 [ 155.112377] __sk_destruct+0x10b/0x190 [ 155.112403] sk_destruct+0x20/0x30 [ 155.112427] __sk_free+0x82/0xa0 [ 155.112451] sk_free+0x19/0x20 [ 155.112472] tcp_close+0x238/0x3f0 [ 155.112498] inet_release+0x42/0x70 [ 155.112522] sock_release+0x25/0x80 [ 155.112546] sock_close+0x12/0x20 [ 155.114960] __fput+0xea/0x230 [ 155.117332] fput+0xe/0x10 [ 155.119604] task_work_run+0x7c/0xa0 [ 155.121861] do_exit+0x2d2/0xae0 [ 155.124100] ? entry_SYSCALL_64_after_hwframe+0xd4/0x139 [ 155.126330] ? entry_SYSCALL_64_after_hwframe+0xc6/0x139 [ 155.128524] ? entry_SYSCALL_64_after_hwframe+0xbf/0x139 [ 155.130674] ? entry_SYSCALL_64_after_hwframe+0xb8/0x139 [ 155.132757] ? entry_SYSCALL_64_after_hwframe+0xb1/0x139 [ 155.134769] do_group_exit+0x43/0xb0 [ 155.136307] SyS_exit_group+0x14/0x20 [ 155.138219] entry_SYSCALL_64_fastpath+0x24/0xab [ 155.140110] RIP: 0033:0x7fe7b4851fd8 [ 155.141984] RSP: 002b:7ffe7f1d1e88 EFLAGS: 0246 ORIG_RAX: 00e7 [ 155.143882] RAX: ffda RBX: 563529f04030 RCX: 7fe7b4851fd8 [ 155.145590] RDX: RSI: 003c RDI: [ 155.147316] RBP: 7ffe7f1d1e80 R08: 00e7 R09: fef8 [ 155.148956] R10: 7fe7acf95148 R11: 0246 R12: 7fe7acf94d90 [ 155.150230] R13: 0036 R14: R15: 7ffe7f1d1c10 [ 155.151492] Code: 00 80 49 01 da 0f 82 1f 01 00 00 48 c7 c7 00 00 00 80 48 2b 3d 4f b2 01 01 49 01 fa 49 c1 ea 0c 49 c1 e2 06 4c 03 15 2d b2 01 01 <49> 8b 42 20 48 8d 50 ff a8 01 4c 0f 45 d2 49 8b 52 20 48 8d 42 [ 155.152892] RIP: kfree+0x53/0x160 RSP: 9c1bc2e7fce8 [ 155.154283] CR2: ded533a0 [ 155.167949] ---[ end trace 28ca6dd18121abd3 ]--- ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-36-generic 4.13.0-36.40 ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 1058 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Mar 1 20:51:56 2018 HibernationDevice: RESUME=UUID=dcaa0aaf-ec9b-4eec-962b-498d547772f5 InstallationDate: Installed on 2018-02-23 (5 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) IwConfig: enp3s0no wireless extensions. lono wireless ex
[Kernel-packages] [Bug 1752621] Status changed to Confirmed
This change was made by a bot. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1752621 Title: BUG: unable to handle kernel paging request at ded533a0 Status in linux package in Ubuntu: Confirmed Bug description: [ 155.111268] BUG: unable to handle kernel paging request at ded533a0 [ 155.111335] IP: kfree+0x53/0x160 [ 155.111357] PGD 0 [ 155.111358] P4D 0 [ 155.111401] Oops: [#1] SMP PTI [ 155.111424] Modules linked in: gpio_ich intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel snd_hda_codec_hdmi kvm snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel irqbypass snd_hda_codec snd_hda_core crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc aesni_intel snd_hwdep aes_x86_64 crypto_simd snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi joydev input_leds glue_helper snd_seq snd_seq_device cryptd snd_timer intel_cstate intel_rapl_perf mei_me shpchp snd mei soundcore lpc_ich mac_hid serio_raw parport_pc ppdev lp parport ip_tables x_tables autofs4 hid_generic usbhid hid i915 video i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt ahci fb_sys_fops r8169 libahci drm mii [ 155.111809] CPU: 0 PID: 1587 Comm: postgres Not tainted 4.13.0-36-generic #40-Ubuntu [ 155.111853] Hardware name: Gigabyte Technology Co., Ltd. H67A-USB3-B3/H67A-USB3-B3, BIOS F7 03/27/2012 [ 155.111906] task: 8e971b4845c0 task.stack: 9c1bc2e7c000 [ 155.111942] RIP: 0010:kfree+0x53/0x160 [ 155.111966] RSP: 0018:9c1bc2e7fce8 EFLAGS: 00010282 [ 155.111998] RAX: RBX: 00102aa3 RCX: 0003 [ 155.112039] RDX: 2d8460201cf0 RSI: 00010080 RDI: 716c4000 [ 155.112080] RBP: 9c1bc2e7fd00 R08: 00025d80 R09: bafc6a19 [ 155.112121] R10: ded53380 R11: R12: 8e974abe7800 [ 155.112162] R13: baba74d4 R14: R15: 8e9714f4d3c0 [ 155.112204] FS: () GS:8e975fa0() knlGS: [ 155.112250] CS: 0010 DS: ES: CR0: 80050033 [ 155.112285] CR2: ded533a0 CR3: 00022c20a001 CR4: 000606f0 [ 155.112326] Call Trace: [ 155.112349] security_sk_free+0x44/0x60 [ 155.112377] __sk_destruct+0x10b/0x190 [ 155.112403] sk_destruct+0x20/0x30 [ 155.112427] __sk_free+0x82/0xa0 [ 155.112451] sk_free+0x19/0x20 [ 155.112472] tcp_close+0x238/0x3f0 [ 155.112498] inet_release+0x42/0x70 [ 155.112522] sock_release+0x25/0x80 [ 155.112546] sock_close+0x12/0x20 [ 155.114960] __fput+0xea/0x230 [ 155.117332] fput+0xe/0x10 [ 155.119604] task_work_run+0x7c/0xa0 [ 155.121861] do_exit+0x2d2/0xae0 [ 155.124100] ? entry_SYSCALL_64_after_hwframe+0xd4/0x139 [ 155.126330] ? entry_SYSCALL_64_after_hwframe+0xc6/0x139 [ 155.128524] ? entry_SYSCALL_64_after_hwframe+0xbf/0x139 [ 155.130674] ? entry_SYSCALL_64_after_hwframe+0xb8/0x139 [ 155.132757] ? entry_SYSCALL_64_after_hwframe+0xb1/0x139 [ 155.134769] do_group_exit+0x43/0xb0 [ 155.136307] SyS_exit_group+0x14/0x20 [ 155.138219] entry_SYSCALL_64_fastpath+0x24/0xab [ 155.140110] RIP: 0033:0x7fe7b4851fd8 [ 155.141984] RSP: 002b:7ffe7f1d1e88 EFLAGS: 0246 ORIG_RAX: 00e7 [ 155.143882] RAX: ffda RBX: 563529f04030 RCX: 7fe7b4851fd8 [ 155.145590] RDX: RSI: 003c RDI: [ 155.147316] RBP: 7ffe7f1d1e80 R08: 00e7 R09: fef8 [ 155.148956] R10: 7fe7acf95148 R11: 0246 R12: 7fe7acf94d90 [ 155.150230] R13: 0036 R14: R15: 7ffe7f1d1c10 [ 155.151492] Code: 00 80 49 01 da 0f 82 1f 01 00 00 48 c7 c7 00 00 00 80 48 2b 3d 4f b2 01 01 49 01 fa 49 c1 ea 0c 49 c1 e2 06 4c 03 15 2d b2 01 01 <49> 8b 42 20 48 8d 50 ff a8 01 4c 0f 45 d2 49 8b 52 20 48 8d 42 [ 155.152892] RIP: kfree+0x53/0x160 RSP: 9c1bc2e7fce8 [ 155.154283] CR2: ded533a0 [ 155.167949] ---[ end trace 28ca6dd18121abd3 ]--- ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-36-generic 4.13.0-36.40 ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 1058 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Mar 1 20:51:56 2018 HibernationDevice: RESUME=UUID=dcaa0aaf-ec9b-4eec-962b-498d547772f5 InstallationDate: Installed on 2018-02-23 (5 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) IwConfig: enp3s0no wireless extensions. lono wireless extensions. MachineType: Gigaby
[Kernel-packages] [Bug 1752621] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1752621/+attachment/5066172/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1752621 Title: BUG: unable to handle kernel paging request at ded533a0 Status in linux package in Ubuntu: Confirmed Bug description: [ 155.111268] BUG: unable to handle kernel paging request at ded533a0 [ 155.111335] IP: kfree+0x53/0x160 [ 155.111357] PGD 0 [ 155.111358] P4D 0 [ 155.111401] Oops: [#1] SMP PTI [ 155.111424] Modules linked in: gpio_ich intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel snd_hda_codec_hdmi kvm snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel irqbypass snd_hda_codec snd_hda_core crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc aesni_intel snd_hwdep aes_x86_64 crypto_simd snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi joydev input_leds glue_helper snd_seq snd_seq_device cryptd snd_timer intel_cstate intel_rapl_perf mei_me shpchp snd mei soundcore lpc_ich mac_hid serio_raw parport_pc ppdev lp parport ip_tables x_tables autofs4 hid_generic usbhid hid i915 video i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt ahci fb_sys_fops r8169 libahci drm mii [ 155.111809] CPU: 0 PID: 1587 Comm: postgres Not tainted 4.13.0-36-generic #40-Ubuntu [ 155.111853] Hardware name: Gigabyte Technology Co., Ltd. H67A-USB3-B3/H67A-USB3-B3, BIOS F7 03/27/2012 [ 155.111906] task: 8e971b4845c0 task.stack: 9c1bc2e7c000 [ 155.111942] RIP: 0010:kfree+0x53/0x160 [ 155.111966] RSP: 0018:9c1bc2e7fce8 EFLAGS: 00010282 [ 155.111998] RAX: RBX: 00102aa3 RCX: 0003 [ 155.112039] RDX: 2d8460201cf0 RSI: 00010080 RDI: 716c4000 [ 155.112080] RBP: 9c1bc2e7fd00 R08: 00025d80 R09: bafc6a19 [ 155.112121] R10: ded53380 R11: R12: 8e974abe7800 [ 155.112162] R13: baba74d4 R14: R15: 8e9714f4d3c0 [ 155.112204] FS: () GS:8e975fa0() knlGS: [ 155.112250] CS: 0010 DS: ES: CR0: 80050033 [ 155.112285] CR2: ded533a0 CR3: 00022c20a001 CR4: 000606f0 [ 155.112326] Call Trace: [ 155.112349] security_sk_free+0x44/0x60 [ 155.112377] __sk_destruct+0x10b/0x190 [ 155.112403] sk_destruct+0x20/0x30 [ 155.112427] __sk_free+0x82/0xa0 [ 155.112451] sk_free+0x19/0x20 [ 155.112472] tcp_close+0x238/0x3f0 [ 155.112498] inet_release+0x42/0x70 [ 155.112522] sock_release+0x25/0x80 [ 155.112546] sock_close+0x12/0x20 [ 155.114960] __fput+0xea/0x230 [ 155.117332] fput+0xe/0x10 [ 155.119604] task_work_run+0x7c/0xa0 [ 155.121861] do_exit+0x2d2/0xae0 [ 155.124100] ? entry_SYSCALL_64_after_hwframe+0xd4/0x139 [ 155.126330] ? entry_SYSCALL_64_after_hwframe+0xc6/0x139 [ 155.128524] ? entry_SYSCALL_64_after_hwframe+0xbf/0x139 [ 155.130674] ? entry_SYSCALL_64_after_hwframe+0xb8/0x139 [ 155.132757] ? entry_SYSCALL_64_after_hwframe+0xb1/0x139 [ 155.134769] do_group_exit+0x43/0xb0 [ 155.136307] SyS_exit_group+0x14/0x20 [ 155.138219] entry_SYSCALL_64_fastpath+0x24/0xab [ 155.140110] RIP: 0033:0x7fe7b4851fd8 [ 155.141984] RSP: 002b:7ffe7f1d1e88 EFLAGS: 0246 ORIG_RAX: 00e7 [ 155.143882] RAX: ffda RBX: 563529f04030 RCX: 7fe7b4851fd8 [ 155.145590] RDX: RSI: 003c RDI: [ 155.147316] RBP: 7ffe7f1d1e80 R08: 00e7 R09: fef8 [ 155.148956] R10: 7fe7acf95148 R11: 0246 R12: 7fe7acf94d90 [ 155.150230] R13: 0036 R14: R15: 7ffe7f1d1c10 [ 155.151492] Code: 00 80 49 01 da 0f 82 1f 01 00 00 48 c7 c7 00 00 00 80 48 2b 3d 4f b2 01 01 49 01 fa 49 c1 ea 0c 49 c1 e2 06 4c 03 15 2d b2 01 01 <49> 8b 42 20 48 8d 50 ff a8 01 4c 0f 45 d2 49 8b 52 20 48 8d 42 [ 155.152892] RIP: kfree+0x53/0x160 RSP: 9c1bc2e7fce8 [ 155.154283] CR2: ded533a0 [ 155.167949] ---[ end trace 28ca6dd18121abd3 ]--- ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-36-generic 4.13.0-36.40 ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 1058 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Mar 1 20:51:56 2018 HibernationDevice: RESUME=UUID=dcaa0aaf-ec9b-4eec-962b-498d547772f5 InstallationDate: Installed on 2018-02-23 (5 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105
[Kernel-packages] [Bug 1752621] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1752621/+attachment/5066177/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1752621 Title: BUG: unable to handle kernel paging request at ded533a0 Status in linux package in Ubuntu: Confirmed Bug description: [ 155.111268] BUG: unable to handle kernel paging request at ded533a0 [ 155.111335] IP: kfree+0x53/0x160 [ 155.111357] PGD 0 [ 155.111358] P4D 0 [ 155.111401] Oops: [#1] SMP PTI [ 155.111424] Modules linked in: gpio_ich intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel snd_hda_codec_hdmi kvm snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel irqbypass snd_hda_codec snd_hda_core crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc aesni_intel snd_hwdep aes_x86_64 crypto_simd snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi joydev input_leds glue_helper snd_seq snd_seq_device cryptd snd_timer intel_cstate intel_rapl_perf mei_me shpchp snd mei soundcore lpc_ich mac_hid serio_raw parport_pc ppdev lp parport ip_tables x_tables autofs4 hid_generic usbhid hid i915 video i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt ahci fb_sys_fops r8169 libahci drm mii [ 155.111809] CPU: 0 PID: 1587 Comm: postgres Not tainted 4.13.0-36-generic #40-Ubuntu [ 155.111853] Hardware name: Gigabyte Technology Co., Ltd. H67A-USB3-B3/H67A-USB3-B3, BIOS F7 03/27/2012 [ 155.111906] task: 8e971b4845c0 task.stack: 9c1bc2e7c000 [ 155.111942] RIP: 0010:kfree+0x53/0x160 [ 155.111966] RSP: 0018:9c1bc2e7fce8 EFLAGS: 00010282 [ 155.111998] RAX: RBX: 00102aa3 RCX: 0003 [ 155.112039] RDX: 2d8460201cf0 RSI: 00010080 RDI: 716c4000 [ 155.112080] RBP: 9c1bc2e7fd00 R08: 00025d80 R09: bafc6a19 [ 155.112121] R10: ded53380 R11: R12: 8e974abe7800 [ 155.112162] R13: baba74d4 R14: R15: 8e9714f4d3c0 [ 155.112204] FS: () GS:8e975fa0() knlGS: [ 155.112250] CS: 0010 DS: ES: CR0: 80050033 [ 155.112285] CR2: ded533a0 CR3: 00022c20a001 CR4: 000606f0 [ 155.112326] Call Trace: [ 155.112349] security_sk_free+0x44/0x60 [ 155.112377] __sk_destruct+0x10b/0x190 [ 155.112403] sk_destruct+0x20/0x30 [ 155.112427] __sk_free+0x82/0xa0 [ 155.112451] sk_free+0x19/0x20 [ 155.112472] tcp_close+0x238/0x3f0 [ 155.112498] inet_release+0x42/0x70 [ 155.112522] sock_release+0x25/0x80 [ 155.112546] sock_close+0x12/0x20 [ 155.114960] __fput+0xea/0x230 [ 155.117332] fput+0xe/0x10 [ 155.119604] task_work_run+0x7c/0xa0 [ 155.121861] do_exit+0x2d2/0xae0 [ 155.124100] ? entry_SYSCALL_64_after_hwframe+0xd4/0x139 [ 155.126330] ? entry_SYSCALL_64_after_hwframe+0xc6/0x139 [ 155.128524] ? entry_SYSCALL_64_after_hwframe+0xbf/0x139 [ 155.130674] ? entry_SYSCALL_64_after_hwframe+0xb8/0x139 [ 155.132757] ? entry_SYSCALL_64_after_hwframe+0xb1/0x139 [ 155.134769] do_group_exit+0x43/0xb0 [ 155.136307] SyS_exit_group+0x14/0x20 [ 155.138219] entry_SYSCALL_64_fastpath+0x24/0xab [ 155.140110] RIP: 0033:0x7fe7b4851fd8 [ 155.141984] RSP: 002b:7ffe7f1d1e88 EFLAGS: 0246 ORIG_RAX: 00e7 [ 155.143882] RAX: ffda RBX: 563529f04030 RCX: 7fe7b4851fd8 [ 155.145590] RDX: RSI: 003c RDI: [ 155.147316] RBP: 7ffe7f1d1e80 R08: 00e7 R09: fef8 [ 155.148956] R10: 7fe7acf95148 R11: 0246 R12: 7fe7acf94d90 [ 155.150230] R13: 0036 R14: R15: 7ffe7f1d1c10 [ 155.151492] Code: 00 80 49 01 da 0f 82 1f 01 00 00 48 c7 c7 00 00 00 80 48 2b 3d 4f b2 01 01 49 01 fa 49 c1 ea 0c 49 c1 e2 06 4c 03 15 2d b2 01 01 <49> 8b 42 20 48 8d 50 ff a8 01 4c 0f 45 d2 49 8b 52 20 48 8d 42 [ 155.152892] RIP: kfree+0x53/0x160 RSP: 9c1bc2e7fce8 [ 155.154283] CR2: ded533a0 [ 155.167949] ---[ end trace 28ca6dd18121abd3 ]--- ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-36-generic 4.13.0-36.40 ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 1058 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Mar 1 20:51:56 2018 HibernationDevice: RESUME=UUID=dcaa0aaf-ec9b-4eec-962b-498d547772f5 InstallationDate: Installed on 2018-02-23 (5 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1
[Kernel-packages] [Bug 1752621] [NEW] BUG: unable to handle kernel paging request at ffffded5330000a0
Public bug reported: [ 155.111268] BUG: unable to handle kernel paging request at ded533a0 [ 155.111335] IP: kfree+0x53/0x160 [ 155.111357] PGD 0 [ 155.111358] P4D 0 [ 155.111401] Oops: [#1] SMP PTI [ 155.111424] Modules linked in: gpio_ich intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel snd_hda_codec_hdmi kvm snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel irqbypass snd_hda_codec snd_hda_core crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc aesni_intel snd_hwdep aes_x86_64 crypto_simd snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi joydev input_leds glue_helper snd_seq snd_seq_device cryptd snd_timer intel_cstate intel_rapl_perf mei_me shpchp snd mei soundcore lpc_ich mac_hid serio_raw parport_pc ppdev lp parport ip_tables x_tables autofs4 hid_generic usbhid hid i915 video i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt ahci fb_sys_fops r8169 libahci drm mii [ 155.111809] CPU: 0 PID: 1587 Comm: postgres Not tainted 4.13.0-36-generic #40-Ubuntu [ 155.111853] Hardware name: Gigabyte Technology Co., Ltd. H67A-USB3-B3/H67A-USB3-B3, BIOS F7 03/27/2012 [ 155.111906] task: 8e971b4845c0 task.stack: 9c1bc2e7c000 [ 155.111942] RIP: 0010:kfree+0x53/0x160 [ 155.111966] RSP: 0018:9c1bc2e7fce8 EFLAGS: 00010282 [ 155.111998] RAX: RBX: 00102aa3 RCX: 0003 [ 155.112039] RDX: 2d8460201cf0 RSI: 00010080 RDI: 716c4000 [ 155.112080] RBP: 9c1bc2e7fd00 R08: 00025d80 R09: bafc6a19 [ 155.112121] R10: ded53380 R11: R12: 8e974abe7800 [ 155.112162] R13: baba74d4 R14: R15: 8e9714f4d3c0 [ 155.112204] FS: () GS:8e975fa0() knlGS: [ 155.112250] CS: 0010 DS: ES: CR0: 80050033 [ 155.112285] CR2: ded533a0 CR3: 00022c20a001 CR4: 000606f0 [ 155.112326] Call Trace: [ 155.112349] security_sk_free+0x44/0x60 [ 155.112377] __sk_destruct+0x10b/0x190 [ 155.112403] sk_destruct+0x20/0x30 [ 155.112427] __sk_free+0x82/0xa0 [ 155.112451] sk_free+0x19/0x20 [ 155.112472] tcp_close+0x238/0x3f0 [ 155.112498] inet_release+0x42/0x70 [ 155.112522] sock_release+0x25/0x80 [ 155.112546] sock_close+0x12/0x20 [ 155.114960] __fput+0xea/0x230 [ 155.117332] fput+0xe/0x10 [ 155.119604] task_work_run+0x7c/0xa0 [ 155.121861] do_exit+0x2d2/0xae0 [ 155.124100] ? entry_SYSCALL_64_after_hwframe+0xd4/0x139 [ 155.126330] ? entry_SYSCALL_64_after_hwframe+0xc6/0x139 [ 155.128524] ? entry_SYSCALL_64_after_hwframe+0xbf/0x139 [ 155.130674] ? entry_SYSCALL_64_after_hwframe+0xb8/0x139 [ 155.132757] ? entry_SYSCALL_64_after_hwframe+0xb1/0x139 [ 155.134769] do_group_exit+0x43/0xb0 [ 155.136307] SyS_exit_group+0x14/0x20 [ 155.138219] entry_SYSCALL_64_fastpath+0x24/0xab [ 155.140110] RIP: 0033:0x7fe7b4851fd8 [ 155.141984] RSP: 002b:7ffe7f1d1e88 EFLAGS: 0246 ORIG_RAX: 00e7 [ 155.143882] RAX: ffda RBX: 563529f04030 RCX: 7fe7b4851fd8 [ 155.145590] RDX: RSI: 003c RDI: [ 155.147316] RBP: 7ffe7f1d1e80 R08: 00e7 R09: fef8 [ 155.148956] R10: 7fe7acf95148 R11: 0246 R12: 7fe7acf94d90 [ 155.150230] R13: 0036 R14: R15: 7ffe7f1d1c10 [ 155.151492] Code: 00 80 49 01 da 0f 82 1f 01 00 00 48 c7 c7 00 00 00 80 48 2b 3d 4f b2 01 01 49 01 fa 49 c1 ea 0c 49 c1 e2 06 4c 03 15 2d b2 01 01 <49> 8b 42 20 48 8d 50 ff a8 01 4c 0f 45 d2 49 8b 52 20 48 8d 42 [ 155.152892] RIP: kfree+0x53/0x160 RSP: 9c1bc2e7fce8 [ 155.154283] CR2: ded533a0 [ 155.167949] ---[ end trace 28ca6dd18121abd3 ]--- ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-36-generic 4.13.0-36.40 ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 1058 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Mar 1 20:51:56 2018 HibernationDevice: RESUME=UUID=dcaa0aaf-ec9b-4eec-962b-498d547772f5 InstallationDate: Installed on 2018-02-23 (5 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) IwConfig: enp3s0no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. H67A-USB3-B3 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-36-generic root=UUID=ba2be4fc-6747-48d1-bf78-a29f03282a95 ro quiet splash apparmor=0 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-36-generic N/A linux-backports-modules-4.13.0-36-generic N/A linux-firmware 1.169.3 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh ins
[Kernel-packages] [Bug 1752621] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1752621/+attachment/5066175/+files/PulseList.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1752621 Title: BUG: unable to handle kernel paging request at ded533a0 Status in linux package in Ubuntu: Confirmed Bug description: [ 155.111268] BUG: unable to handle kernel paging request at ded533a0 [ 155.111335] IP: kfree+0x53/0x160 [ 155.111357] PGD 0 [ 155.111358] P4D 0 [ 155.111401] Oops: [#1] SMP PTI [ 155.111424] Modules linked in: gpio_ich intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel snd_hda_codec_hdmi kvm snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel irqbypass snd_hda_codec snd_hda_core crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc aesni_intel snd_hwdep aes_x86_64 crypto_simd snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi joydev input_leds glue_helper snd_seq snd_seq_device cryptd snd_timer intel_cstate intel_rapl_perf mei_me shpchp snd mei soundcore lpc_ich mac_hid serio_raw parport_pc ppdev lp parport ip_tables x_tables autofs4 hid_generic usbhid hid i915 video i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt ahci fb_sys_fops r8169 libahci drm mii [ 155.111809] CPU: 0 PID: 1587 Comm: postgres Not tainted 4.13.0-36-generic #40-Ubuntu [ 155.111853] Hardware name: Gigabyte Technology Co., Ltd. H67A-USB3-B3/H67A-USB3-B3, BIOS F7 03/27/2012 [ 155.111906] task: 8e971b4845c0 task.stack: 9c1bc2e7c000 [ 155.111942] RIP: 0010:kfree+0x53/0x160 [ 155.111966] RSP: 0018:9c1bc2e7fce8 EFLAGS: 00010282 [ 155.111998] RAX: RBX: 00102aa3 RCX: 0003 [ 155.112039] RDX: 2d8460201cf0 RSI: 00010080 RDI: 716c4000 [ 155.112080] RBP: 9c1bc2e7fd00 R08: 00025d80 R09: bafc6a19 [ 155.112121] R10: ded53380 R11: R12: 8e974abe7800 [ 155.112162] R13: baba74d4 R14: R15: 8e9714f4d3c0 [ 155.112204] FS: () GS:8e975fa0() knlGS: [ 155.112250] CS: 0010 DS: ES: CR0: 80050033 [ 155.112285] CR2: ded533a0 CR3: 00022c20a001 CR4: 000606f0 [ 155.112326] Call Trace: [ 155.112349] security_sk_free+0x44/0x60 [ 155.112377] __sk_destruct+0x10b/0x190 [ 155.112403] sk_destruct+0x20/0x30 [ 155.112427] __sk_free+0x82/0xa0 [ 155.112451] sk_free+0x19/0x20 [ 155.112472] tcp_close+0x238/0x3f0 [ 155.112498] inet_release+0x42/0x70 [ 155.112522] sock_release+0x25/0x80 [ 155.112546] sock_close+0x12/0x20 [ 155.114960] __fput+0xea/0x230 [ 155.117332] fput+0xe/0x10 [ 155.119604] task_work_run+0x7c/0xa0 [ 155.121861] do_exit+0x2d2/0xae0 [ 155.124100] ? entry_SYSCALL_64_after_hwframe+0xd4/0x139 [ 155.126330] ? entry_SYSCALL_64_after_hwframe+0xc6/0x139 [ 155.128524] ? entry_SYSCALL_64_after_hwframe+0xbf/0x139 [ 155.130674] ? entry_SYSCALL_64_after_hwframe+0xb8/0x139 [ 155.132757] ? entry_SYSCALL_64_after_hwframe+0xb1/0x139 [ 155.134769] do_group_exit+0x43/0xb0 [ 155.136307] SyS_exit_group+0x14/0x20 [ 155.138219] entry_SYSCALL_64_fastpath+0x24/0xab [ 155.140110] RIP: 0033:0x7fe7b4851fd8 [ 155.141984] RSP: 002b:7ffe7f1d1e88 EFLAGS: 0246 ORIG_RAX: 00e7 [ 155.143882] RAX: ffda RBX: 563529f04030 RCX: 7fe7b4851fd8 [ 155.145590] RDX: RSI: 003c RDI: [ 155.147316] RBP: 7ffe7f1d1e80 R08: 00e7 R09: fef8 [ 155.148956] R10: 7fe7acf95148 R11: 0246 R12: 7fe7acf94d90 [ 155.150230] R13: 0036 R14: R15: 7ffe7f1d1c10 [ 155.151492] Code: 00 80 49 01 da 0f 82 1f 01 00 00 48 c7 c7 00 00 00 80 48 2b 3d 4f b2 01 01 49 01 fa 49 c1 ea 0c 49 c1 e2 06 4c 03 15 2d b2 01 01 <49> 8b 42 20 48 8d 50 ff a8 01 4c 0f 45 d2 49 8b 52 20 48 8d 42 [ 155.152892] RIP: kfree+0x53/0x160 RSP: 9c1bc2e7fce8 [ 155.154283] CR2: ded533a0 [ 155.167949] ---[ end trace 28ca6dd18121abd3 ]--- ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-36-generic 4.13.0-36.40 ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 1058 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Mar 1 20:51:56 2018 HibernationDevice: RESUME=UUID=dcaa0aaf-ec9b-4eec-962b-498d547772f5 InstallationDate: Installed on 2018-02-23 (5 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
[Kernel-packages] [Bug 1752621] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1752621/+attachment/5066176/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1752621 Title: BUG: unable to handle kernel paging request at ded533a0 Status in linux package in Ubuntu: Confirmed Bug description: [ 155.111268] BUG: unable to handle kernel paging request at ded533a0 [ 155.111335] IP: kfree+0x53/0x160 [ 155.111357] PGD 0 [ 155.111358] P4D 0 [ 155.111401] Oops: [#1] SMP PTI [ 155.111424] Modules linked in: gpio_ich intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel snd_hda_codec_hdmi kvm snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel irqbypass snd_hda_codec snd_hda_core crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc aesni_intel snd_hwdep aes_x86_64 crypto_simd snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi joydev input_leds glue_helper snd_seq snd_seq_device cryptd snd_timer intel_cstate intel_rapl_perf mei_me shpchp snd mei soundcore lpc_ich mac_hid serio_raw parport_pc ppdev lp parport ip_tables x_tables autofs4 hid_generic usbhid hid i915 video i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt ahci fb_sys_fops r8169 libahci drm mii [ 155.111809] CPU: 0 PID: 1587 Comm: postgres Not tainted 4.13.0-36-generic #40-Ubuntu [ 155.111853] Hardware name: Gigabyte Technology Co., Ltd. H67A-USB3-B3/H67A-USB3-B3, BIOS F7 03/27/2012 [ 155.111906] task: 8e971b4845c0 task.stack: 9c1bc2e7c000 [ 155.111942] RIP: 0010:kfree+0x53/0x160 [ 155.111966] RSP: 0018:9c1bc2e7fce8 EFLAGS: 00010282 [ 155.111998] RAX: RBX: 00102aa3 RCX: 0003 [ 155.112039] RDX: 2d8460201cf0 RSI: 00010080 RDI: 716c4000 [ 155.112080] RBP: 9c1bc2e7fd00 R08: 00025d80 R09: bafc6a19 [ 155.112121] R10: ded53380 R11: R12: 8e974abe7800 [ 155.112162] R13: baba74d4 R14: R15: 8e9714f4d3c0 [ 155.112204] FS: () GS:8e975fa0() knlGS: [ 155.112250] CS: 0010 DS: ES: CR0: 80050033 [ 155.112285] CR2: ded533a0 CR3: 00022c20a001 CR4: 000606f0 [ 155.112326] Call Trace: [ 155.112349] security_sk_free+0x44/0x60 [ 155.112377] __sk_destruct+0x10b/0x190 [ 155.112403] sk_destruct+0x20/0x30 [ 155.112427] __sk_free+0x82/0xa0 [ 155.112451] sk_free+0x19/0x20 [ 155.112472] tcp_close+0x238/0x3f0 [ 155.112498] inet_release+0x42/0x70 [ 155.112522] sock_release+0x25/0x80 [ 155.112546] sock_close+0x12/0x20 [ 155.114960] __fput+0xea/0x230 [ 155.117332] fput+0xe/0x10 [ 155.119604] task_work_run+0x7c/0xa0 [ 155.121861] do_exit+0x2d2/0xae0 [ 155.124100] ? entry_SYSCALL_64_after_hwframe+0xd4/0x139 [ 155.126330] ? entry_SYSCALL_64_after_hwframe+0xc6/0x139 [ 155.128524] ? entry_SYSCALL_64_after_hwframe+0xbf/0x139 [ 155.130674] ? entry_SYSCALL_64_after_hwframe+0xb8/0x139 [ 155.132757] ? entry_SYSCALL_64_after_hwframe+0xb1/0x139 [ 155.134769] do_group_exit+0x43/0xb0 [ 155.136307] SyS_exit_group+0x14/0x20 [ 155.138219] entry_SYSCALL_64_fastpath+0x24/0xab [ 155.140110] RIP: 0033:0x7fe7b4851fd8 [ 155.141984] RSP: 002b:7ffe7f1d1e88 EFLAGS: 0246 ORIG_RAX: 00e7 [ 155.143882] RAX: ffda RBX: 563529f04030 RCX: 7fe7b4851fd8 [ 155.145590] RDX: RSI: 003c RDI: [ 155.147316] RBP: 7ffe7f1d1e80 R08: 00e7 R09: fef8 [ 155.148956] R10: 7fe7acf95148 R11: 0246 R12: 7fe7acf94d90 [ 155.150230] R13: 0036 R14: R15: 7ffe7f1d1c10 [ 155.151492] Code: 00 80 49 01 da 0f 82 1f 01 00 00 48 c7 c7 00 00 00 80 48 2b 3d 4f b2 01 01 49 01 fa 49 c1 ea 0c 49 c1 e2 06 4c 03 15 2d b2 01 01 <49> 8b 42 20 48 8d 50 ff a8 01 4c 0f 45 d2 49 8b 52 20 48 8d 42 [ 155.152892] RIP: kfree+0x53/0x160 RSP: 9c1bc2e7fce8 [ 155.154283] CR2: ded533a0 [ 155.167949] ---[ end trace 28ca6dd18121abd3 ]--- ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-36-generic 4.13.0-36.40 ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 1058 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Mar 1 20:51:56 2018 HibernationDevice: RESUME=UUID=dcaa0aaf-ec9b-4eec-962b-498d547772f5 InstallationDate: Installed on 2018-02-23 (5 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) IwCon
[Kernel-packages] [Bug 1752621] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1752621/+attachment/5066174/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1752621 Title: BUG: unable to handle kernel paging request at ded533a0 Status in linux package in Ubuntu: Confirmed Bug description: [ 155.111268] BUG: unable to handle kernel paging request at ded533a0 [ 155.111335] IP: kfree+0x53/0x160 [ 155.111357] PGD 0 [ 155.111358] P4D 0 [ 155.111401] Oops: [#1] SMP PTI [ 155.111424] Modules linked in: gpio_ich intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel snd_hda_codec_hdmi kvm snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel irqbypass snd_hda_codec snd_hda_core crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc aesni_intel snd_hwdep aes_x86_64 crypto_simd snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi joydev input_leds glue_helper snd_seq snd_seq_device cryptd snd_timer intel_cstate intel_rapl_perf mei_me shpchp snd mei soundcore lpc_ich mac_hid serio_raw parport_pc ppdev lp parport ip_tables x_tables autofs4 hid_generic usbhid hid i915 video i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt ahci fb_sys_fops r8169 libahci drm mii [ 155.111809] CPU: 0 PID: 1587 Comm: postgres Not tainted 4.13.0-36-generic #40-Ubuntu [ 155.111853] Hardware name: Gigabyte Technology Co., Ltd. H67A-USB3-B3/H67A-USB3-B3, BIOS F7 03/27/2012 [ 155.111906] task: 8e971b4845c0 task.stack: 9c1bc2e7c000 [ 155.111942] RIP: 0010:kfree+0x53/0x160 [ 155.111966] RSP: 0018:9c1bc2e7fce8 EFLAGS: 00010282 [ 155.111998] RAX: RBX: 00102aa3 RCX: 0003 [ 155.112039] RDX: 2d8460201cf0 RSI: 00010080 RDI: 716c4000 [ 155.112080] RBP: 9c1bc2e7fd00 R08: 00025d80 R09: bafc6a19 [ 155.112121] R10: ded53380 R11: R12: 8e974abe7800 [ 155.112162] R13: baba74d4 R14: R15: 8e9714f4d3c0 [ 155.112204] FS: () GS:8e975fa0() knlGS: [ 155.112250] CS: 0010 DS: ES: CR0: 80050033 [ 155.112285] CR2: ded533a0 CR3: 00022c20a001 CR4: 000606f0 [ 155.112326] Call Trace: [ 155.112349] security_sk_free+0x44/0x60 [ 155.112377] __sk_destruct+0x10b/0x190 [ 155.112403] sk_destruct+0x20/0x30 [ 155.112427] __sk_free+0x82/0xa0 [ 155.112451] sk_free+0x19/0x20 [ 155.112472] tcp_close+0x238/0x3f0 [ 155.112498] inet_release+0x42/0x70 [ 155.112522] sock_release+0x25/0x80 [ 155.112546] sock_close+0x12/0x20 [ 155.114960] __fput+0xea/0x230 [ 155.117332] fput+0xe/0x10 [ 155.119604] task_work_run+0x7c/0xa0 [ 155.121861] do_exit+0x2d2/0xae0 [ 155.124100] ? entry_SYSCALL_64_after_hwframe+0xd4/0x139 [ 155.126330] ? entry_SYSCALL_64_after_hwframe+0xc6/0x139 [ 155.128524] ? entry_SYSCALL_64_after_hwframe+0xbf/0x139 [ 155.130674] ? entry_SYSCALL_64_after_hwframe+0xb8/0x139 [ 155.132757] ? entry_SYSCALL_64_after_hwframe+0xb1/0x139 [ 155.134769] do_group_exit+0x43/0xb0 [ 155.136307] SyS_exit_group+0x14/0x20 [ 155.138219] entry_SYSCALL_64_fastpath+0x24/0xab [ 155.140110] RIP: 0033:0x7fe7b4851fd8 [ 155.141984] RSP: 002b:7ffe7f1d1e88 EFLAGS: 0246 ORIG_RAX: 00e7 [ 155.143882] RAX: ffda RBX: 563529f04030 RCX: 7fe7b4851fd8 [ 155.145590] RDX: RSI: 003c RDI: [ 155.147316] RBP: 7ffe7f1d1e80 R08: 00e7 R09: fef8 [ 155.148956] R10: 7fe7acf95148 R11: 0246 R12: 7fe7acf94d90 [ 155.150230] R13: 0036 R14: R15: 7ffe7f1d1c10 [ 155.151492] Code: 00 80 49 01 da 0f 82 1f 01 00 00 48 c7 c7 00 00 00 80 48 2b 3d 4f b2 01 01 49 01 fa 49 c1 ea 0c 49 c1 e2 06 4c 03 15 2d b2 01 01 <49> 8b 42 20 48 8d 50 ff a8 01 4c 0f 45 d2 49 8b 52 20 48 8d 42 [ 155.152892] RIP: kfree+0x53/0x160 RSP: 9c1bc2e7fce8 [ 155.154283] CR2: ded533a0 [ 155.167949] ---[ end trace 28ca6dd18121abd3 ]--- ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-36-generic 4.13.0-36.40 ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 1058 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Mar 1 20:51:56 2018 HibernationDevice: RESUME=UUID=dcaa0aaf-ec9b-4eec-962b-498d547772f5 InstallationDate: Installed on 2018-02-23 (5 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105
[Kernel-packages] [Bug 1752621] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1752621/+attachment/5066168/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1752621 Title: BUG: unable to handle kernel paging request at ded533a0 Status in linux package in Ubuntu: Confirmed Bug description: [ 155.111268] BUG: unable to handle kernel paging request at ded533a0 [ 155.111335] IP: kfree+0x53/0x160 [ 155.111357] PGD 0 [ 155.111358] P4D 0 [ 155.111401] Oops: [#1] SMP PTI [ 155.111424] Modules linked in: gpio_ich intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel snd_hda_codec_hdmi kvm snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel irqbypass snd_hda_codec snd_hda_core crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc aesni_intel snd_hwdep aes_x86_64 crypto_simd snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi joydev input_leds glue_helper snd_seq snd_seq_device cryptd snd_timer intel_cstate intel_rapl_perf mei_me shpchp snd mei soundcore lpc_ich mac_hid serio_raw parport_pc ppdev lp parport ip_tables x_tables autofs4 hid_generic usbhid hid i915 video i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt ahci fb_sys_fops r8169 libahci drm mii [ 155.111809] CPU: 0 PID: 1587 Comm: postgres Not tainted 4.13.0-36-generic #40-Ubuntu [ 155.111853] Hardware name: Gigabyte Technology Co., Ltd. H67A-USB3-B3/H67A-USB3-B3, BIOS F7 03/27/2012 [ 155.111906] task: 8e971b4845c0 task.stack: 9c1bc2e7c000 [ 155.111942] RIP: 0010:kfree+0x53/0x160 [ 155.111966] RSP: 0018:9c1bc2e7fce8 EFLAGS: 00010282 [ 155.111998] RAX: RBX: 00102aa3 RCX: 0003 [ 155.112039] RDX: 2d8460201cf0 RSI: 00010080 RDI: 716c4000 [ 155.112080] RBP: 9c1bc2e7fd00 R08: 00025d80 R09: bafc6a19 [ 155.112121] R10: ded53380 R11: R12: 8e974abe7800 [ 155.112162] R13: baba74d4 R14: R15: 8e9714f4d3c0 [ 155.112204] FS: () GS:8e975fa0() knlGS: [ 155.112250] CS: 0010 DS: ES: CR0: 80050033 [ 155.112285] CR2: ded533a0 CR3: 00022c20a001 CR4: 000606f0 [ 155.112326] Call Trace: [ 155.112349] security_sk_free+0x44/0x60 [ 155.112377] __sk_destruct+0x10b/0x190 [ 155.112403] sk_destruct+0x20/0x30 [ 155.112427] __sk_free+0x82/0xa0 [ 155.112451] sk_free+0x19/0x20 [ 155.112472] tcp_close+0x238/0x3f0 [ 155.112498] inet_release+0x42/0x70 [ 155.112522] sock_release+0x25/0x80 [ 155.112546] sock_close+0x12/0x20 [ 155.114960] __fput+0xea/0x230 [ 155.117332] fput+0xe/0x10 [ 155.119604] task_work_run+0x7c/0xa0 [ 155.121861] do_exit+0x2d2/0xae0 [ 155.124100] ? entry_SYSCALL_64_after_hwframe+0xd4/0x139 [ 155.126330] ? entry_SYSCALL_64_after_hwframe+0xc6/0x139 [ 155.128524] ? entry_SYSCALL_64_after_hwframe+0xbf/0x139 [ 155.130674] ? entry_SYSCALL_64_after_hwframe+0xb8/0x139 [ 155.132757] ? entry_SYSCALL_64_after_hwframe+0xb1/0x139 [ 155.134769] do_group_exit+0x43/0xb0 [ 155.136307] SyS_exit_group+0x14/0x20 [ 155.138219] entry_SYSCALL_64_fastpath+0x24/0xab [ 155.140110] RIP: 0033:0x7fe7b4851fd8 [ 155.141984] RSP: 002b:7ffe7f1d1e88 EFLAGS: 0246 ORIG_RAX: 00e7 [ 155.143882] RAX: ffda RBX: 563529f04030 RCX: 7fe7b4851fd8 [ 155.145590] RDX: RSI: 003c RDI: [ 155.147316] RBP: 7ffe7f1d1e80 R08: 00e7 R09: fef8 [ 155.148956] R10: 7fe7acf95148 R11: 0246 R12: 7fe7acf94d90 [ 155.150230] R13: 0036 R14: R15: 7ffe7f1d1c10 [ 155.151492] Code: 00 80 49 01 da 0f 82 1f 01 00 00 48 c7 c7 00 00 00 80 48 2b 3d 4f b2 01 01 49 01 fa 49 c1 ea 0c 49 c1 e2 06 4c 03 15 2d b2 01 01 <49> 8b 42 20 48 8d 50 ff a8 01 4c 0f 45 d2 49 8b 52 20 48 8d 42 [ 155.152892] RIP: kfree+0x53/0x160 RSP: 9c1bc2e7fce8 [ 155.154283] CR2: ded533a0 [ 155.167949] ---[ end trace 28ca6dd18121abd3 ]--- ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-36-generic 4.13.0-36.40 ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 1058 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Mar 1 20:51:56 2018 HibernationDevice: RESUME=UUID=dcaa0aaf-ec9b-4eec-962b-498d547772f5 InstallationDate: Installed on 2018-02-23 (5 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) IwConfi
[Kernel-packages] [Bug 1752621] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1752621/+attachment/5066166/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1752621 Title: BUG: unable to handle kernel paging request at ded533a0 Status in linux package in Ubuntu: Confirmed Bug description: [ 155.111268] BUG: unable to handle kernel paging request at ded533a0 [ 155.111335] IP: kfree+0x53/0x160 [ 155.111357] PGD 0 [ 155.111358] P4D 0 [ 155.111401] Oops: [#1] SMP PTI [ 155.111424] Modules linked in: gpio_ich intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel snd_hda_codec_hdmi kvm snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel irqbypass snd_hda_codec snd_hda_core crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc aesni_intel snd_hwdep aes_x86_64 crypto_simd snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi joydev input_leds glue_helper snd_seq snd_seq_device cryptd snd_timer intel_cstate intel_rapl_perf mei_me shpchp snd mei soundcore lpc_ich mac_hid serio_raw parport_pc ppdev lp parport ip_tables x_tables autofs4 hid_generic usbhid hid i915 video i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt ahci fb_sys_fops r8169 libahci drm mii [ 155.111809] CPU: 0 PID: 1587 Comm: postgres Not tainted 4.13.0-36-generic #40-Ubuntu [ 155.111853] Hardware name: Gigabyte Technology Co., Ltd. H67A-USB3-B3/H67A-USB3-B3, BIOS F7 03/27/2012 [ 155.111906] task: 8e971b4845c0 task.stack: 9c1bc2e7c000 [ 155.111942] RIP: 0010:kfree+0x53/0x160 [ 155.111966] RSP: 0018:9c1bc2e7fce8 EFLAGS: 00010282 [ 155.111998] RAX: RBX: 00102aa3 RCX: 0003 [ 155.112039] RDX: 2d8460201cf0 RSI: 00010080 RDI: 716c4000 [ 155.112080] RBP: 9c1bc2e7fd00 R08: 00025d80 R09: bafc6a19 [ 155.112121] R10: ded53380 R11: R12: 8e974abe7800 [ 155.112162] R13: baba74d4 R14: R15: 8e9714f4d3c0 [ 155.112204] FS: () GS:8e975fa0() knlGS: [ 155.112250] CS: 0010 DS: ES: CR0: 80050033 [ 155.112285] CR2: ded533a0 CR3: 00022c20a001 CR4: 000606f0 [ 155.112326] Call Trace: [ 155.112349] security_sk_free+0x44/0x60 [ 155.112377] __sk_destruct+0x10b/0x190 [ 155.112403] sk_destruct+0x20/0x30 [ 155.112427] __sk_free+0x82/0xa0 [ 155.112451] sk_free+0x19/0x20 [ 155.112472] tcp_close+0x238/0x3f0 [ 155.112498] inet_release+0x42/0x70 [ 155.112522] sock_release+0x25/0x80 [ 155.112546] sock_close+0x12/0x20 [ 155.114960] __fput+0xea/0x230 [ 155.117332] fput+0xe/0x10 [ 155.119604] task_work_run+0x7c/0xa0 [ 155.121861] do_exit+0x2d2/0xae0 [ 155.124100] ? entry_SYSCALL_64_after_hwframe+0xd4/0x139 [ 155.126330] ? entry_SYSCALL_64_after_hwframe+0xc6/0x139 [ 155.128524] ? entry_SYSCALL_64_after_hwframe+0xbf/0x139 [ 155.130674] ? entry_SYSCALL_64_after_hwframe+0xb8/0x139 [ 155.132757] ? entry_SYSCALL_64_after_hwframe+0xb1/0x139 [ 155.134769] do_group_exit+0x43/0xb0 [ 155.136307] SyS_exit_group+0x14/0x20 [ 155.138219] entry_SYSCALL_64_fastpath+0x24/0xab [ 155.140110] RIP: 0033:0x7fe7b4851fd8 [ 155.141984] RSP: 002b:7ffe7f1d1e88 EFLAGS: 0246 ORIG_RAX: 00e7 [ 155.143882] RAX: ffda RBX: 563529f04030 RCX: 7fe7b4851fd8 [ 155.145590] RDX: RSI: 003c RDI: [ 155.147316] RBP: 7ffe7f1d1e80 R08: 00e7 R09: fef8 [ 155.148956] R10: 7fe7acf95148 R11: 0246 R12: 7fe7acf94d90 [ 155.150230] R13: 0036 R14: R15: 7ffe7f1d1c10 [ 155.151492] Code: 00 80 49 01 da 0f 82 1f 01 00 00 48 c7 c7 00 00 00 80 48 2b 3d 4f b2 01 01 49 01 fa 49 c1 ea 0c 49 c1 e2 06 4c 03 15 2d b2 01 01 <49> 8b 42 20 48 8d 50 ff a8 01 4c 0f 45 d2 49 8b 52 20 48 8d 42 [ 155.152892] RIP: kfree+0x53/0x160 RSP: 9c1bc2e7fce8 [ 155.154283] CR2: ded533a0 [ 155.167949] ---[ end trace 28ca6dd18121abd3 ]--- ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-36-generic 4.13.0-36.40 ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 1058 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Mar 1 20:51:56 2018 HibernationDevice: RESUME=UUID=dcaa0aaf-ec9b-4eec-962b-498d547772f5 InstallationDate: Installed on 2018-02-23 (5 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (201801
[Kernel-packages] [Bug 1752621] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1752621/+attachment/5066171/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1752621 Title: BUG: unable to handle kernel paging request at ded533a0 Status in linux package in Ubuntu: Confirmed Bug description: [ 155.111268] BUG: unable to handle kernel paging request at ded533a0 [ 155.111335] IP: kfree+0x53/0x160 [ 155.111357] PGD 0 [ 155.111358] P4D 0 [ 155.111401] Oops: [#1] SMP PTI [ 155.111424] Modules linked in: gpio_ich intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel snd_hda_codec_hdmi kvm snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel irqbypass snd_hda_codec snd_hda_core crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc aesni_intel snd_hwdep aes_x86_64 crypto_simd snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi joydev input_leds glue_helper snd_seq snd_seq_device cryptd snd_timer intel_cstate intel_rapl_perf mei_me shpchp snd mei soundcore lpc_ich mac_hid serio_raw parport_pc ppdev lp parport ip_tables x_tables autofs4 hid_generic usbhid hid i915 video i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt ahci fb_sys_fops r8169 libahci drm mii [ 155.111809] CPU: 0 PID: 1587 Comm: postgres Not tainted 4.13.0-36-generic #40-Ubuntu [ 155.111853] Hardware name: Gigabyte Technology Co., Ltd. H67A-USB3-B3/H67A-USB3-B3, BIOS F7 03/27/2012 [ 155.111906] task: 8e971b4845c0 task.stack: 9c1bc2e7c000 [ 155.111942] RIP: 0010:kfree+0x53/0x160 [ 155.111966] RSP: 0018:9c1bc2e7fce8 EFLAGS: 00010282 [ 155.111998] RAX: RBX: 00102aa3 RCX: 0003 [ 155.112039] RDX: 2d8460201cf0 RSI: 00010080 RDI: 716c4000 [ 155.112080] RBP: 9c1bc2e7fd00 R08: 00025d80 R09: bafc6a19 [ 155.112121] R10: ded53380 R11: R12: 8e974abe7800 [ 155.112162] R13: baba74d4 R14: R15: 8e9714f4d3c0 [ 155.112204] FS: () GS:8e975fa0() knlGS: [ 155.112250] CS: 0010 DS: ES: CR0: 80050033 [ 155.112285] CR2: ded533a0 CR3: 00022c20a001 CR4: 000606f0 [ 155.112326] Call Trace: [ 155.112349] security_sk_free+0x44/0x60 [ 155.112377] __sk_destruct+0x10b/0x190 [ 155.112403] sk_destruct+0x20/0x30 [ 155.112427] __sk_free+0x82/0xa0 [ 155.112451] sk_free+0x19/0x20 [ 155.112472] tcp_close+0x238/0x3f0 [ 155.112498] inet_release+0x42/0x70 [ 155.112522] sock_release+0x25/0x80 [ 155.112546] sock_close+0x12/0x20 [ 155.114960] __fput+0xea/0x230 [ 155.117332] fput+0xe/0x10 [ 155.119604] task_work_run+0x7c/0xa0 [ 155.121861] do_exit+0x2d2/0xae0 [ 155.124100] ? entry_SYSCALL_64_after_hwframe+0xd4/0x139 [ 155.126330] ? entry_SYSCALL_64_after_hwframe+0xc6/0x139 [ 155.128524] ? entry_SYSCALL_64_after_hwframe+0xbf/0x139 [ 155.130674] ? entry_SYSCALL_64_after_hwframe+0xb8/0x139 [ 155.132757] ? entry_SYSCALL_64_after_hwframe+0xb1/0x139 [ 155.134769] do_group_exit+0x43/0xb0 [ 155.136307] SyS_exit_group+0x14/0x20 [ 155.138219] entry_SYSCALL_64_fastpath+0x24/0xab [ 155.140110] RIP: 0033:0x7fe7b4851fd8 [ 155.141984] RSP: 002b:7ffe7f1d1e88 EFLAGS: 0246 ORIG_RAX: 00e7 [ 155.143882] RAX: ffda RBX: 563529f04030 RCX: 7fe7b4851fd8 [ 155.145590] RDX: RSI: 003c RDI: [ 155.147316] RBP: 7ffe7f1d1e80 R08: 00e7 R09: fef8 [ 155.148956] R10: 7fe7acf95148 R11: 0246 R12: 7fe7acf94d90 [ 155.150230] R13: 0036 R14: R15: 7ffe7f1d1c10 [ 155.151492] Code: 00 80 49 01 da 0f 82 1f 01 00 00 48 c7 c7 00 00 00 80 48 2b 3d 4f b2 01 01 49 01 fa 49 c1 ea 0c 49 c1 e2 06 4c 03 15 2d b2 01 01 <49> 8b 42 20 48 8d 50 ff a8 01 4c 0f 45 d2 49 8b 52 20 48 8d 42 [ 155.152892] RIP: kfree+0x53/0x160 RSP: 9c1bc2e7fce8 [ 155.154283] CR2: ded533a0 [ 155.167949] ---[ end trace 28ca6dd18121abd3 ]--- ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-36-generic 4.13.0-36.40 ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 1058 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Mar 1 20:51:56 2018 HibernationDevice: RESUME=UUID=dcaa0aaf-ec9b-4eec-962b-498d547772f5 InstallationDate: Installed on 2018-02-23 (5 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release a
[Kernel-packages] [Bug 1752621] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1752621/+attachment/5066173/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1752621 Title: BUG: unable to handle kernel paging request at ded533a0 Status in linux package in Ubuntu: Confirmed Bug description: [ 155.111268] BUG: unable to handle kernel paging request at ded533a0 [ 155.111335] IP: kfree+0x53/0x160 [ 155.111357] PGD 0 [ 155.111358] P4D 0 [ 155.111401] Oops: [#1] SMP PTI [ 155.111424] Modules linked in: gpio_ich intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel snd_hda_codec_hdmi kvm snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel irqbypass snd_hda_codec snd_hda_core crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc aesni_intel snd_hwdep aes_x86_64 crypto_simd snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi joydev input_leds glue_helper snd_seq snd_seq_device cryptd snd_timer intel_cstate intel_rapl_perf mei_me shpchp snd mei soundcore lpc_ich mac_hid serio_raw parport_pc ppdev lp parport ip_tables x_tables autofs4 hid_generic usbhid hid i915 video i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt ahci fb_sys_fops r8169 libahci drm mii [ 155.111809] CPU: 0 PID: 1587 Comm: postgres Not tainted 4.13.0-36-generic #40-Ubuntu [ 155.111853] Hardware name: Gigabyte Technology Co., Ltd. H67A-USB3-B3/H67A-USB3-B3, BIOS F7 03/27/2012 [ 155.111906] task: 8e971b4845c0 task.stack: 9c1bc2e7c000 [ 155.111942] RIP: 0010:kfree+0x53/0x160 [ 155.111966] RSP: 0018:9c1bc2e7fce8 EFLAGS: 00010282 [ 155.111998] RAX: RBX: 00102aa3 RCX: 0003 [ 155.112039] RDX: 2d8460201cf0 RSI: 00010080 RDI: 716c4000 [ 155.112080] RBP: 9c1bc2e7fd00 R08: 00025d80 R09: bafc6a19 [ 155.112121] R10: ded53380 R11: R12: 8e974abe7800 [ 155.112162] R13: baba74d4 R14: R15: 8e9714f4d3c0 [ 155.112204] FS: () GS:8e975fa0() knlGS: [ 155.112250] CS: 0010 DS: ES: CR0: 80050033 [ 155.112285] CR2: ded533a0 CR3: 00022c20a001 CR4: 000606f0 [ 155.112326] Call Trace: [ 155.112349] security_sk_free+0x44/0x60 [ 155.112377] __sk_destruct+0x10b/0x190 [ 155.112403] sk_destruct+0x20/0x30 [ 155.112427] __sk_free+0x82/0xa0 [ 155.112451] sk_free+0x19/0x20 [ 155.112472] tcp_close+0x238/0x3f0 [ 155.112498] inet_release+0x42/0x70 [ 155.112522] sock_release+0x25/0x80 [ 155.112546] sock_close+0x12/0x20 [ 155.114960] __fput+0xea/0x230 [ 155.117332] fput+0xe/0x10 [ 155.119604] task_work_run+0x7c/0xa0 [ 155.121861] do_exit+0x2d2/0xae0 [ 155.124100] ? entry_SYSCALL_64_after_hwframe+0xd4/0x139 [ 155.126330] ? entry_SYSCALL_64_after_hwframe+0xc6/0x139 [ 155.128524] ? entry_SYSCALL_64_after_hwframe+0xbf/0x139 [ 155.130674] ? entry_SYSCALL_64_after_hwframe+0xb8/0x139 [ 155.132757] ? entry_SYSCALL_64_after_hwframe+0xb1/0x139 [ 155.134769] do_group_exit+0x43/0xb0 [ 155.136307] SyS_exit_group+0x14/0x20 [ 155.138219] entry_SYSCALL_64_fastpath+0x24/0xab [ 155.140110] RIP: 0033:0x7fe7b4851fd8 [ 155.141984] RSP: 002b:7ffe7f1d1e88 EFLAGS: 0246 ORIG_RAX: 00e7 [ 155.143882] RAX: ffda RBX: 563529f04030 RCX: 7fe7b4851fd8 [ 155.145590] RDX: RSI: 003c RDI: [ 155.147316] RBP: 7ffe7f1d1e80 R08: 00e7 R09: fef8 [ 155.148956] R10: 7fe7acf95148 R11: 0246 R12: 7fe7acf94d90 [ 155.150230] R13: 0036 R14: R15: 7ffe7f1d1c10 [ 155.151492] Code: 00 80 49 01 da 0f 82 1f 01 00 00 48 c7 c7 00 00 00 80 48 2b 3d 4f b2 01 01 49 01 fa 49 c1 ea 0c 49 c1 e2 06 4c 03 15 2d b2 01 01 <49> 8b 42 20 48 8d 50 ff a8 01 4c 0f 45 d2 49 8b 52 20 48 8d 42 [ 155.152892] RIP: kfree+0x53/0x160 RSP: 9c1bc2e7fce8 [ 155.154283] CR2: ded533a0 [ 155.167949] ---[ end trace 28ca6dd18121abd3 ]--- ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-36-generic 4.13.0-36.40 ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 1058 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Mar 1 20:51:56 2018 HibernationDevice: RESUME=UUID=dcaa0aaf-ec9b-4eec-962b-498d547772f5 InstallationDate: Installed on 2018-02-23 (5 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20
[Kernel-packages] [Bug 1752621] JournalErrors.txt
apport information ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1752621/+attachment/5066167/+files/JournalErrors.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1752621 Title: BUG: unable to handle kernel paging request at ded533a0 Status in linux package in Ubuntu: Confirmed Bug description: [ 155.111268] BUG: unable to handle kernel paging request at ded533a0 [ 155.111335] IP: kfree+0x53/0x160 [ 155.111357] PGD 0 [ 155.111358] P4D 0 [ 155.111401] Oops: [#1] SMP PTI [ 155.111424] Modules linked in: gpio_ich intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel snd_hda_codec_hdmi kvm snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel irqbypass snd_hda_codec snd_hda_core crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc aesni_intel snd_hwdep aes_x86_64 crypto_simd snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi joydev input_leds glue_helper snd_seq snd_seq_device cryptd snd_timer intel_cstate intel_rapl_perf mei_me shpchp snd mei soundcore lpc_ich mac_hid serio_raw parport_pc ppdev lp parport ip_tables x_tables autofs4 hid_generic usbhid hid i915 video i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt ahci fb_sys_fops r8169 libahci drm mii [ 155.111809] CPU: 0 PID: 1587 Comm: postgres Not tainted 4.13.0-36-generic #40-Ubuntu [ 155.111853] Hardware name: Gigabyte Technology Co., Ltd. H67A-USB3-B3/H67A-USB3-B3, BIOS F7 03/27/2012 [ 155.111906] task: 8e971b4845c0 task.stack: 9c1bc2e7c000 [ 155.111942] RIP: 0010:kfree+0x53/0x160 [ 155.111966] RSP: 0018:9c1bc2e7fce8 EFLAGS: 00010282 [ 155.111998] RAX: RBX: 00102aa3 RCX: 0003 [ 155.112039] RDX: 2d8460201cf0 RSI: 00010080 RDI: 716c4000 [ 155.112080] RBP: 9c1bc2e7fd00 R08: 00025d80 R09: bafc6a19 [ 155.112121] R10: ded53380 R11: R12: 8e974abe7800 [ 155.112162] R13: baba74d4 R14: R15: 8e9714f4d3c0 [ 155.112204] FS: () GS:8e975fa0() knlGS: [ 155.112250] CS: 0010 DS: ES: CR0: 80050033 [ 155.112285] CR2: ded533a0 CR3: 00022c20a001 CR4: 000606f0 [ 155.112326] Call Trace: [ 155.112349] security_sk_free+0x44/0x60 [ 155.112377] __sk_destruct+0x10b/0x190 [ 155.112403] sk_destruct+0x20/0x30 [ 155.112427] __sk_free+0x82/0xa0 [ 155.112451] sk_free+0x19/0x20 [ 155.112472] tcp_close+0x238/0x3f0 [ 155.112498] inet_release+0x42/0x70 [ 155.112522] sock_release+0x25/0x80 [ 155.112546] sock_close+0x12/0x20 [ 155.114960] __fput+0xea/0x230 [ 155.117332] fput+0xe/0x10 [ 155.119604] task_work_run+0x7c/0xa0 [ 155.121861] do_exit+0x2d2/0xae0 [ 155.124100] ? entry_SYSCALL_64_after_hwframe+0xd4/0x139 [ 155.126330] ? entry_SYSCALL_64_after_hwframe+0xc6/0x139 [ 155.128524] ? entry_SYSCALL_64_after_hwframe+0xbf/0x139 [ 155.130674] ? entry_SYSCALL_64_after_hwframe+0xb8/0x139 [ 155.132757] ? entry_SYSCALL_64_after_hwframe+0xb1/0x139 [ 155.134769] do_group_exit+0x43/0xb0 [ 155.136307] SyS_exit_group+0x14/0x20 [ 155.138219] entry_SYSCALL_64_fastpath+0x24/0xab [ 155.140110] RIP: 0033:0x7fe7b4851fd8 [ 155.141984] RSP: 002b:7ffe7f1d1e88 EFLAGS: 0246 ORIG_RAX: 00e7 [ 155.143882] RAX: ffda RBX: 563529f04030 RCX: 7fe7b4851fd8 [ 155.145590] RDX: RSI: 003c RDI: [ 155.147316] RBP: 7ffe7f1d1e80 R08: 00e7 R09: fef8 [ 155.148956] R10: 7fe7acf95148 R11: 0246 R12: 7fe7acf94d90 [ 155.150230] R13: 0036 R14: R15: 7ffe7f1d1c10 [ 155.151492] Code: 00 80 49 01 da 0f 82 1f 01 00 00 48 c7 c7 00 00 00 80 48 2b 3d 4f b2 01 01 49 01 fa 49 c1 ea 0c 49 c1 e2 06 4c 03 15 2d b2 01 01 <49> 8b 42 20 48 8d 50 ff a8 01 4c 0f 45 d2 49 8b 52 20 48 8d 42 [ 155.152892] RIP: kfree+0x53/0x160 RSP: 9c1bc2e7fce8 [ 155.154283] CR2: ded533a0 [ 155.167949] ---[ end trace 28ca6dd18121abd3 ]--- ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-36-generic 4.13.0-36.40 ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 1058 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Mar 1 20:51:56 2018 HibernationDevice: RESUME=UUID=dcaa0aaf-ec9b-4eec-962b-498d547772f5 InstallationDate: Installed on 2018-02-23 (5 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (2018
[Kernel-packages] [Bug 1752621] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1752621/+attachment/5066165/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1752621 Title: BUG: unable to handle kernel paging request at ded533a0 Status in linux package in Ubuntu: Confirmed Bug description: [ 155.111268] BUG: unable to handle kernel paging request at ded533a0 [ 155.111335] IP: kfree+0x53/0x160 [ 155.111357] PGD 0 [ 155.111358] P4D 0 [ 155.111401] Oops: [#1] SMP PTI [ 155.111424] Modules linked in: gpio_ich intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel snd_hda_codec_hdmi kvm snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel irqbypass snd_hda_codec snd_hda_core crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc aesni_intel snd_hwdep aes_x86_64 crypto_simd snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi joydev input_leds glue_helper snd_seq snd_seq_device cryptd snd_timer intel_cstate intel_rapl_perf mei_me shpchp snd mei soundcore lpc_ich mac_hid serio_raw parport_pc ppdev lp parport ip_tables x_tables autofs4 hid_generic usbhid hid i915 video i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt ahci fb_sys_fops r8169 libahci drm mii [ 155.111809] CPU: 0 PID: 1587 Comm: postgres Not tainted 4.13.0-36-generic #40-Ubuntu [ 155.111853] Hardware name: Gigabyte Technology Co., Ltd. H67A-USB3-B3/H67A-USB3-B3, BIOS F7 03/27/2012 [ 155.111906] task: 8e971b4845c0 task.stack: 9c1bc2e7c000 [ 155.111942] RIP: 0010:kfree+0x53/0x160 [ 155.111966] RSP: 0018:9c1bc2e7fce8 EFLAGS: 00010282 [ 155.111998] RAX: RBX: 00102aa3 RCX: 0003 [ 155.112039] RDX: 2d8460201cf0 RSI: 00010080 RDI: 716c4000 [ 155.112080] RBP: 9c1bc2e7fd00 R08: 00025d80 R09: bafc6a19 [ 155.112121] R10: ded53380 R11: R12: 8e974abe7800 [ 155.112162] R13: baba74d4 R14: R15: 8e9714f4d3c0 [ 155.112204] FS: () GS:8e975fa0() knlGS: [ 155.112250] CS: 0010 DS: ES: CR0: 80050033 [ 155.112285] CR2: ded533a0 CR3: 00022c20a001 CR4: 000606f0 [ 155.112326] Call Trace: [ 155.112349] security_sk_free+0x44/0x60 [ 155.112377] __sk_destruct+0x10b/0x190 [ 155.112403] sk_destruct+0x20/0x30 [ 155.112427] __sk_free+0x82/0xa0 [ 155.112451] sk_free+0x19/0x20 [ 155.112472] tcp_close+0x238/0x3f0 [ 155.112498] inet_release+0x42/0x70 [ 155.112522] sock_release+0x25/0x80 [ 155.112546] sock_close+0x12/0x20 [ 155.114960] __fput+0xea/0x230 [ 155.117332] fput+0xe/0x10 [ 155.119604] task_work_run+0x7c/0xa0 [ 155.121861] do_exit+0x2d2/0xae0 [ 155.124100] ? entry_SYSCALL_64_after_hwframe+0xd4/0x139 [ 155.126330] ? entry_SYSCALL_64_after_hwframe+0xc6/0x139 [ 155.128524] ? entry_SYSCALL_64_after_hwframe+0xbf/0x139 [ 155.130674] ? entry_SYSCALL_64_after_hwframe+0xb8/0x139 [ 155.132757] ? entry_SYSCALL_64_after_hwframe+0xb1/0x139 [ 155.134769] do_group_exit+0x43/0xb0 [ 155.136307] SyS_exit_group+0x14/0x20 [ 155.138219] entry_SYSCALL_64_fastpath+0x24/0xab [ 155.140110] RIP: 0033:0x7fe7b4851fd8 [ 155.141984] RSP: 002b:7ffe7f1d1e88 EFLAGS: 0246 ORIG_RAX: 00e7 [ 155.143882] RAX: ffda RBX: 563529f04030 RCX: 7fe7b4851fd8 [ 155.145590] RDX: RSI: 003c RDI: [ 155.147316] RBP: 7ffe7f1d1e80 R08: 00e7 R09: fef8 [ 155.148956] R10: 7fe7acf95148 R11: 0246 R12: 7fe7acf94d90 [ 155.150230] R13: 0036 R14: R15: 7ffe7f1d1c10 [ 155.151492] Code: 00 80 49 01 da 0f 82 1f 01 00 00 48 c7 c7 00 00 00 80 48 2b 3d 4f b2 01 01 49 01 fa 49 c1 ea 0c 49 c1 e2 06 4c 03 15 2d b2 01 01 <49> 8b 42 20 48 8d 50 ff a8 01 4c 0f 45 d2 49 8b 52 20 48 8d 42 [ 155.152892] RIP: kfree+0x53/0x160 RSP: 9c1bc2e7fce8 [ 155.154283] CR2: ded533a0 [ 155.167949] ---[ end trace 28ca6dd18121abd3 ]--- ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-36-generic 4.13.0-36.40 ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 1058 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Mar 1 20:51:56 2018 HibernationDevice: RESUME=UUID=dcaa0aaf-ec9b-4eec-962b-498d547772f5 InstallationDate: Installed on 2018-02-23 (5 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) IwConfig:
[Kernel-packages] [Bug 1752621] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1752621/+attachment/5066170/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1752621 Title: BUG: unable to handle kernel paging request at ded533a0 Status in linux package in Ubuntu: Confirmed Bug description: [ 155.111268] BUG: unable to handle kernel paging request at ded533a0 [ 155.111335] IP: kfree+0x53/0x160 [ 155.111357] PGD 0 [ 155.111358] P4D 0 [ 155.111401] Oops: [#1] SMP PTI [ 155.111424] Modules linked in: gpio_ich intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel snd_hda_codec_hdmi kvm snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel irqbypass snd_hda_codec snd_hda_core crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc aesni_intel snd_hwdep aes_x86_64 crypto_simd snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi joydev input_leds glue_helper snd_seq snd_seq_device cryptd snd_timer intel_cstate intel_rapl_perf mei_me shpchp snd mei soundcore lpc_ich mac_hid serio_raw parport_pc ppdev lp parport ip_tables x_tables autofs4 hid_generic usbhid hid i915 video i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt ahci fb_sys_fops r8169 libahci drm mii [ 155.111809] CPU: 0 PID: 1587 Comm: postgres Not tainted 4.13.0-36-generic #40-Ubuntu [ 155.111853] Hardware name: Gigabyte Technology Co., Ltd. H67A-USB3-B3/H67A-USB3-B3, BIOS F7 03/27/2012 [ 155.111906] task: 8e971b4845c0 task.stack: 9c1bc2e7c000 [ 155.111942] RIP: 0010:kfree+0x53/0x160 [ 155.111966] RSP: 0018:9c1bc2e7fce8 EFLAGS: 00010282 [ 155.111998] RAX: RBX: 00102aa3 RCX: 0003 [ 155.112039] RDX: 2d8460201cf0 RSI: 00010080 RDI: 716c4000 [ 155.112080] RBP: 9c1bc2e7fd00 R08: 00025d80 R09: bafc6a19 [ 155.112121] R10: ded53380 R11: R12: 8e974abe7800 [ 155.112162] R13: baba74d4 R14: R15: 8e9714f4d3c0 [ 155.112204] FS: () GS:8e975fa0() knlGS: [ 155.112250] CS: 0010 DS: ES: CR0: 80050033 [ 155.112285] CR2: ded533a0 CR3: 00022c20a001 CR4: 000606f0 [ 155.112326] Call Trace: [ 155.112349] security_sk_free+0x44/0x60 [ 155.112377] __sk_destruct+0x10b/0x190 [ 155.112403] sk_destruct+0x20/0x30 [ 155.112427] __sk_free+0x82/0xa0 [ 155.112451] sk_free+0x19/0x20 [ 155.112472] tcp_close+0x238/0x3f0 [ 155.112498] inet_release+0x42/0x70 [ 155.112522] sock_release+0x25/0x80 [ 155.112546] sock_close+0x12/0x20 [ 155.114960] __fput+0xea/0x230 [ 155.117332] fput+0xe/0x10 [ 155.119604] task_work_run+0x7c/0xa0 [ 155.121861] do_exit+0x2d2/0xae0 [ 155.124100] ? entry_SYSCALL_64_after_hwframe+0xd4/0x139 [ 155.126330] ? entry_SYSCALL_64_after_hwframe+0xc6/0x139 [ 155.128524] ? entry_SYSCALL_64_after_hwframe+0xbf/0x139 [ 155.130674] ? entry_SYSCALL_64_after_hwframe+0xb8/0x139 [ 155.132757] ? entry_SYSCALL_64_after_hwframe+0xb1/0x139 [ 155.134769] do_group_exit+0x43/0xb0 [ 155.136307] SyS_exit_group+0x14/0x20 [ 155.138219] entry_SYSCALL_64_fastpath+0x24/0xab [ 155.140110] RIP: 0033:0x7fe7b4851fd8 [ 155.141984] RSP: 002b:7ffe7f1d1e88 EFLAGS: 0246 ORIG_RAX: 00e7 [ 155.143882] RAX: ffda RBX: 563529f04030 RCX: 7fe7b4851fd8 [ 155.145590] RDX: RSI: 003c RDI: [ 155.147316] RBP: 7ffe7f1d1e80 R08: 00e7 R09: fef8 [ 155.148956] R10: 7fe7acf95148 R11: 0246 R12: 7fe7acf94d90 [ 155.150230] R13: 0036 R14: R15: 7ffe7f1d1c10 [ 155.151492] Code: 00 80 49 01 da 0f 82 1f 01 00 00 48 c7 c7 00 00 00 80 48 2b 3d 4f b2 01 01 49 01 fa 49 c1 ea 0c 49 c1 e2 06 4c 03 15 2d b2 01 01 <49> 8b 42 20 48 8d 50 ff a8 01 4c 0f 45 d2 49 8b 52 20 48 8d 42 [ 155.152892] RIP: kfree+0x53/0x160 RSP: 9c1bc2e7fce8 [ 155.154283] CR2: ded533a0 [ 155.167949] ---[ end trace 28ca6dd18121abd3 ]--- ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-36-generic 4.13.0-36.40 ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 1058 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Mar 1 20:51:56 2018 HibernationDevice: RESUME=UUID=dcaa0aaf-ec9b-4eec-962b-498d547772f5 InstallationDate: Installed on 2018-02-23 (5 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105
[Kernel-packages] [Bug 1752621] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1752621/+attachment/5066169/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1752621 Title: BUG: unable to handle kernel paging request at ded533a0 Status in linux package in Ubuntu: Confirmed Bug description: [ 155.111268] BUG: unable to handle kernel paging request at ded533a0 [ 155.111335] IP: kfree+0x53/0x160 [ 155.111357] PGD 0 [ 155.111358] P4D 0 [ 155.111401] Oops: [#1] SMP PTI [ 155.111424] Modules linked in: gpio_ich intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel snd_hda_codec_hdmi kvm snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel irqbypass snd_hda_codec snd_hda_core crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc aesni_intel snd_hwdep aes_x86_64 crypto_simd snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi joydev input_leds glue_helper snd_seq snd_seq_device cryptd snd_timer intel_cstate intel_rapl_perf mei_me shpchp snd mei soundcore lpc_ich mac_hid serio_raw parport_pc ppdev lp parport ip_tables x_tables autofs4 hid_generic usbhid hid i915 video i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt ahci fb_sys_fops r8169 libahci drm mii [ 155.111809] CPU: 0 PID: 1587 Comm: postgres Not tainted 4.13.0-36-generic #40-Ubuntu [ 155.111853] Hardware name: Gigabyte Technology Co., Ltd. H67A-USB3-B3/H67A-USB3-B3, BIOS F7 03/27/2012 [ 155.111906] task: 8e971b4845c0 task.stack: 9c1bc2e7c000 [ 155.111942] RIP: 0010:kfree+0x53/0x160 [ 155.111966] RSP: 0018:9c1bc2e7fce8 EFLAGS: 00010282 [ 155.111998] RAX: RBX: 00102aa3 RCX: 0003 [ 155.112039] RDX: 2d8460201cf0 RSI: 00010080 RDI: 716c4000 [ 155.112080] RBP: 9c1bc2e7fd00 R08: 00025d80 R09: bafc6a19 [ 155.112121] R10: ded53380 R11: R12: 8e974abe7800 [ 155.112162] R13: baba74d4 R14: R15: 8e9714f4d3c0 [ 155.112204] FS: () GS:8e975fa0() knlGS: [ 155.112250] CS: 0010 DS: ES: CR0: 80050033 [ 155.112285] CR2: ded533a0 CR3: 00022c20a001 CR4: 000606f0 [ 155.112326] Call Trace: [ 155.112349] security_sk_free+0x44/0x60 [ 155.112377] __sk_destruct+0x10b/0x190 [ 155.112403] sk_destruct+0x20/0x30 [ 155.112427] __sk_free+0x82/0xa0 [ 155.112451] sk_free+0x19/0x20 [ 155.112472] tcp_close+0x238/0x3f0 [ 155.112498] inet_release+0x42/0x70 [ 155.112522] sock_release+0x25/0x80 [ 155.112546] sock_close+0x12/0x20 [ 155.114960] __fput+0xea/0x230 [ 155.117332] fput+0xe/0x10 [ 155.119604] task_work_run+0x7c/0xa0 [ 155.121861] do_exit+0x2d2/0xae0 [ 155.124100] ? entry_SYSCALL_64_after_hwframe+0xd4/0x139 [ 155.126330] ? entry_SYSCALL_64_after_hwframe+0xc6/0x139 [ 155.128524] ? entry_SYSCALL_64_after_hwframe+0xbf/0x139 [ 155.130674] ? entry_SYSCALL_64_after_hwframe+0xb8/0x139 [ 155.132757] ? entry_SYSCALL_64_after_hwframe+0xb1/0x139 [ 155.134769] do_group_exit+0x43/0xb0 [ 155.136307] SyS_exit_group+0x14/0x20 [ 155.138219] entry_SYSCALL_64_fastpath+0x24/0xab [ 155.140110] RIP: 0033:0x7fe7b4851fd8 [ 155.141984] RSP: 002b:7ffe7f1d1e88 EFLAGS: 0246 ORIG_RAX: 00e7 [ 155.143882] RAX: ffda RBX: 563529f04030 RCX: 7fe7b4851fd8 [ 155.145590] RDX: RSI: 003c RDI: [ 155.147316] RBP: 7ffe7f1d1e80 R08: 00e7 R09: fef8 [ 155.148956] R10: 7fe7acf95148 R11: 0246 R12: 7fe7acf94d90 [ 155.150230] R13: 0036 R14: R15: 7ffe7f1d1c10 [ 155.151492] Code: 00 80 49 01 da 0f 82 1f 01 00 00 48 c7 c7 00 00 00 80 48 2b 3d 4f b2 01 01 49 01 fa 49 c1 ea 0c 49 c1 e2 06 4c 03 15 2d b2 01 01 <49> 8b 42 20 48 8d 50 ff a8 01 4c 0f 45 d2 49 8b 52 20 48 8d 42 [ 155.152892] RIP: kfree+0x53/0x160 RSP: 9c1bc2e7fce8 [ 155.154283] CR2: ded533a0 [ 155.167949] ---[ end trace 28ca6dd18121abd3 ]--- ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-36-generic 4.13.0-36.40 ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 1058 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Mar 1 20:51:56 2018 HibernationDevice: RESUME=UUID=dcaa0aaf-ec9b-4eec-962b-498d547772f5 InstallationDate: Installed on 2018-02-23 (5 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) IwConfi
[Kernel-packages] [Bug 1752621] AlsaInfo.txt
apport information ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1752621/+attachment/5066164/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1752621 Title: BUG: unable to handle kernel paging request at ded533a0 Status in linux package in Ubuntu: Confirmed Bug description: [ 155.111268] BUG: unable to handle kernel paging request at ded533a0 [ 155.111335] IP: kfree+0x53/0x160 [ 155.111357] PGD 0 [ 155.111358] P4D 0 [ 155.111401] Oops: [#1] SMP PTI [ 155.111424] Modules linked in: gpio_ich intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel snd_hda_codec_hdmi kvm snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel irqbypass snd_hda_codec snd_hda_core crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc aesni_intel snd_hwdep aes_x86_64 crypto_simd snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi joydev input_leds glue_helper snd_seq snd_seq_device cryptd snd_timer intel_cstate intel_rapl_perf mei_me shpchp snd mei soundcore lpc_ich mac_hid serio_raw parport_pc ppdev lp parport ip_tables x_tables autofs4 hid_generic usbhid hid i915 video i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt ahci fb_sys_fops r8169 libahci drm mii [ 155.111809] CPU: 0 PID: 1587 Comm: postgres Not tainted 4.13.0-36-generic #40-Ubuntu [ 155.111853] Hardware name: Gigabyte Technology Co., Ltd. H67A-USB3-B3/H67A-USB3-B3, BIOS F7 03/27/2012 [ 155.111906] task: 8e971b4845c0 task.stack: 9c1bc2e7c000 [ 155.111942] RIP: 0010:kfree+0x53/0x160 [ 155.111966] RSP: 0018:9c1bc2e7fce8 EFLAGS: 00010282 [ 155.111998] RAX: RBX: 00102aa3 RCX: 0003 [ 155.112039] RDX: 2d8460201cf0 RSI: 00010080 RDI: 716c4000 [ 155.112080] RBP: 9c1bc2e7fd00 R08: 00025d80 R09: bafc6a19 [ 155.112121] R10: ded53380 R11: R12: 8e974abe7800 [ 155.112162] R13: baba74d4 R14: R15: 8e9714f4d3c0 [ 155.112204] FS: () GS:8e975fa0() knlGS: [ 155.112250] CS: 0010 DS: ES: CR0: 80050033 [ 155.112285] CR2: ded533a0 CR3: 00022c20a001 CR4: 000606f0 [ 155.112326] Call Trace: [ 155.112349] security_sk_free+0x44/0x60 [ 155.112377] __sk_destruct+0x10b/0x190 [ 155.112403] sk_destruct+0x20/0x30 [ 155.112427] __sk_free+0x82/0xa0 [ 155.112451] sk_free+0x19/0x20 [ 155.112472] tcp_close+0x238/0x3f0 [ 155.112498] inet_release+0x42/0x70 [ 155.112522] sock_release+0x25/0x80 [ 155.112546] sock_close+0x12/0x20 [ 155.114960] __fput+0xea/0x230 [ 155.117332] fput+0xe/0x10 [ 155.119604] task_work_run+0x7c/0xa0 [ 155.121861] do_exit+0x2d2/0xae0 [ 155.124100] ? entry_SYSCALL_64_after_hwframe+0xd4/0x139 [ 155.126330] ? entry_SYSCALL_64_after_hwframe+0xc6/0x139 [ 155.128524] ? entry_SYSCALL_64_after_hwframe+0xbf/0x139 [ 155.130674] ? entry_SYSCALL_64_after_hwframe+0xb8/0x139 [ 155.132757] ? entry_SYSCALL_64_after_hwframe+0xb1/0x139 [ 155.134769] do_group_exit+0x43/0xb0 [ 155.136307] SyS_exit_group+0x14/0x20 [ 155.138219] entry_SYSCALL_64_fastpath+0x24/0xab [ 155.140110] RIP: 0033:0x7fe7b4851fd8 [ 155.141984] RSP: 002b:7ffe7f1d1e88 EFLAGS: 0246 ORIG_RAX: 00e7 [ 155.143882] RAX: ffda RBX: 563529f04030 RCX: 7fe7b4851fd8 [ 155.145590] RDX: RSI: 003c RDI: [ 155.147316] RBP: 7ffe7f1d1e80 R08: 00e7 R09: fef8 [ 155.148956] R10: 7fe7acf95148 R11: 0246 R12: 7fe7acf94d90 [ 155.150230] R13: 0036 R14: R15: 7ffe7f1d1c10 [ 155.151492] Code: 00 80 49 01 da 0f 82 1f 01 00 00 48 c7 c7 00 00 00 80 48 2b 3d 4f b2 01 01 49 01 fa 49 c1 ea 0c 49 c1 e2 06 4c 03 15 2d b2 01 01 <49> 8b 42 20 48 8d 50 ff a8 01 4c 0f 45 d2 49 8b 52 20 48 8d 42 [ 155.152892] RIP: kfree+0x53/0x160 RSP: 9c1bc2e7fce8 [ 155.154283] CR2: ded533a0 [ 155.167949] ---[ end trace 28ca6dd18121abd3 ]--- ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-36-generic 4.13.0-36.40 ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 1058 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Mar 1 20:51:56 2018 HibernationDevice: RESUME=UUID=dcaa0aaf-ec9b-4eec-962b-498d547772f5 InstallationDate: Installed on 2018-02-23 (5 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
[Kernel-packages] [Bug 1752026] Re: Ubuntu18.04:POWER9:DD2.2 - Unable to start a KVM guest with default machine type(pseries-bionic) complaining "KVM implementation does not support Transactional Memo
** Changed in: ubuntu-power-systems 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/1752026 Title: Ubuntu18.04:POWER9:DD2.2 - Unable to start a KVM guest with default machine type(pseries-bionic) complaining "KVM implementation does not support Transactional Memory, try cap-htm=off" (kvm) Status in The Ubuntu-power-systems project: Confirmed Status in linux package in Ubuntu: Confirmed Status in qemu package in Ubuntu: Incomplete Bug description: == Comment: #0 - Satheesh Rajendran - 2018-02-23 08:31:06 == ---Problem Description--- libvirt unable to start a KVM guest complaining about cap-htm machine property to be off Host Env: # lscpu Architecture:ppc64le Byte Order: Little Endian CPU(s): 160 On-line CPU(s) list: 0-159 Thread(s) per core: 4 Core(s) per socket: 20 Socket(s): 2 NUMA node(s):2 Model: 2.2 (pvr 004e 1202) Model name: POWER9 (raw), altivec supported CPU max MHz: 3800. CPU min MHz: 2166. L1d cache: 32K L1i cache: 32K L2 cache:512K L3 cache:10240K NUMA node0 CPU(s): 0-79 NUMA node8 CPU(s): 80-159 ii qemu-kvm 1:2.11+dfsg-1ubuntu2 ppc64el QEMU Full virtualization on x86 hardware ii libvirt-bin 4.0.0-1ubuntu3 ppc64el programs for the libvirt library # lsmcode Version of System Firmware : Product Name : OpenPOWER Firmware Product Version : open-power-SUPERMICRO-P9DSU-V1.03-20180205-imp Product Extra : occ-577915f Product Extra : skiboot-v5.9-240-g081882690163-pcbedce4 Product Extra : petitboot-v1.6.6-p019c87e Product Extra : sbe-095e608 Product Extra : machine-xml-fb5f933 Product Extra : hostboot-9bfb201 Product Extra : linux-4.14.13-openpower1-p78d7eee Contact Information = sathe...@in.ibm.com ---uname output--- 4.15.0-10-generic Machine Type = power9 boston 2.2 (pvr 004e 1202) ---Debugger--- A debugger is not configured ---Steps to Reproduce--- 1. Boot a guest from libvirt with default pseries machine type or pseries-bionic /usr/bin/virt-install --connect=qemu:///system --hvm --accelerate --name 'virt-tests-vm1' --machine pseries --memory=32768 --vcpu=32,sockets=1,cores=32,threads=1 --import --nographics --serial pty --memballoon model=virtio --controller type=scsi,model=virtio-scsi --disk path=/var/lib/libvirt/images/workspace/runAvocadoFVTTest/avocado-fvt-wrapper/data/avocado-vt/images/ubuntu-18.04-ppc64le.qcow2,bus=scsi,size=10,format=qcow2 --network=bridge=virbr0,model=virtio,mac=52:54:00:77:78:79 --noautoconsole WARNING No operating system detected, VM performance may suffer. Specify an OS with --os-variant for optimal results. Starting install... ERRORinternal error: process exited while connecting to monitor: ,id=scsi0-0-0-0,bootindex=1 -netdev tap,fd=24,id=hostnet0,vhost=on,vhostfd=26 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:77:78:79,bus=pci.0,addr=0x1 -chardev pty,id=charserial0 -device spapr-vty,chardev=charserial0,id=serial0,reg=0x3000 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x4 -msg timestamp=on 2018-02-23T14:21:11.081809Z qemu-system-ppc64: KVM implementation does not support Transactional Memory, try cap-htm=off Domain installation does not appear to have been successful. If it was, you can restart your domain by running: virsh --connect qemu:///system start virt-tests-vm1 otherwise, please restart your installation. 2. Fails to boot.. Note: if we specify machine type as pseries=2.12 it boots fine like below /usr/bin/virt-install --connect=qemu:///system --hvm --accelerate --name 'virt-tests-vm1' --machine pseries-2.12 --memory=32768 --vcpu=32,sockets=1,cores=32,threads=1 --import --nographics --serial pty --memballoon model=virtio --controller type=scsi,model=virtio-scsi --disk path=/var/lib/libvirt/images/workspace/runAvocadoFVTTest/avocado-fvt-wrapper/data/avocado-vt/images/ubuntu-18.04-ppc64le.qcow2,bus=scsi,size=10,format=qcow2 --network=bridge=virbr0,model=virtio,mac=52:54:00:77:78:79 --noautoconsole WARNING No operating system detected, VM performance may suffer. Specify an OS with --os-variant for optimal results. qemu-cmd line: libvirt+ 4283 1 99 09:26 ?00:00:38 qemu-system-ppc64 -enable-kvm -name guest=virt-tests-vm1,debug-threads=on -S -object secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-4 -virt-tests-vm1/master-key.aes -machine pseries-2.12,accel=kvm,usb=off ,dump-guest-core=off -m 32768 -realtime mlock=of
[Kernel-packages] [Bug 1749040] Re: KPTI support for arm64 systems
cert testing on QDF2400 ** Attachment added: "cert testing on QDF2400" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1749040/+attachment/5066200/+files/submission_2018-03-01T15.40.44.388832.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1749040 Title: KPTI support for arm64 systems Status in linux package in Ubuntu: Incomplete Status in linux source package in Artful: In Progress Status in linux source package in Bionic: Incomplete Bug description: While regression testing the current linux-hwe proposed kernel (4.13.0-33.36~16.04.1), I found that it fails to boot on a Cavium ThunderX CRB. I've rebooted twice since upgrading from the current -updates kernel, and it's failed to boot both times, with different failure modes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1749040/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1749040] Re: KPTI support for arm64 systems
Hisilicon D05-0 testing. ** Attachment added: "cert testing on Hisilicon" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1749040/+attachment/5066199/+files/submission_2018-03-01T15.37.19.324054.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1749040 Title: KPTI support for arm64 systems Status in linux package in Ubuntu: Incomplete Status in linux source package in Artful: In Progress Status in linux source package in Bionic: Incomplete Bug description: While regression testing the current linux-hwe proposed kernel (4.13.0-33.36~16.04.1), I found that it fails to boot on a Cavium ThunderX CRB. I've rebooted twice since upgrading from the current -updates kernel, and it's failed to boot both times, with different failure modes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1749040/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1751994] Re: ppc64el: Support firmware disable of RFI flush
** Changed in: linux (Ubuntu) Status: New => Triaged ** Changed in: linux (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1751994 Title: ppc64el: Support firmware disable of RFI flush Status in The Ubuntu-power-systems project: Triaged Status in linux package in Ubuntu: Triaged Bug description: == Comment: #0 - Breno Leitao - 2018-02-26 13:59:55 == Hi Canonical, We still need some changes regarding spectre and meltdown. We need to backport the following commit to all supported kernel. I undertand that the backport for kernel 4.XX should be trivial. Not sure about kernel 3.13 yet. https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=582605a429e20ae68fd0b041b2e840af296edd08 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=eb0a2d2620ae431c543963c8c7f08f597366fc60 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1751994/+subscriptions -- Mailing list: https://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 1749040] Re: KPTI support for arm64 systems
On Thu, Mar 1, 2018 at 8:50 AM, Paolo Pisati <1749...@bugs.launchpad.net> wrote: > I see 5 failures marked as blocker there: 4 couldn't complete due to the > test environment, and 1[*], apparently, is a CONFIG issue (so something > that predates this patchset). Sorry - I didn't have time to analyze it last night when I posted. All 5 are expected: - disk/disk_stress_ng_sda is a test bug (LP: #1751167) - ethernet/multi_iperf3_* requires a client/server setup we don't have in place - miscellanea/bmc_info - this system doesn't have a conventional BMC - miscellanea/efi_boot_mode - this system boots w/ u-boot - miscellanea/ipmi_test - this system doesn't have a conventional BMC -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1749040 Title: KPTI support for arm64 systems Status in linux package in Ubuntu: Incomplete Status in linux source package in Artful: In Progress Status in linux source package in Bionic: Incomplete Bug description: While regression testing the current linux-hwe proposed kernel (4.13.0-33.36~16.04.1), I found that it fails to boot on a Cavium ThunderX CRB. I've rebooted twice since upgrading from the current -updates kernel, and it's failed to boot both times, with different failure modes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1749040/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1751098] Re: Ubuntu hangs shortly after booting with kernel 4.13.0-36
** Changed in: linux (Ubuntu Artful) Status: In Progress => Incomplete ** Changed in: linux (Ubuntu) Status: In Progress => 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/1751098 Title: Ubuntu hangs shortly after booting with kernel 4.13.0-36 Status in linux package in Ubuntu: Incomplete Status in linux source package in Artful: Incomplete Bug description: After upgrading to linux 4.13.0-36 my laptop hangs shortly after booting, even before logging in to the desktop. It starts with the interface being unresponsive but the mouse cursor moving, and shortly after that the mouse cursor also hangs intermittently and then permanently. Linux 4.13.0-32 works fine. My laptop is a Dell XPS 13 9360 with an Core i5 7200u. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-36-generic 4.13.0-36.40 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USUARIOORDEN DE ACCESO PID /dev/snd/controlC0: nicolas2111 F pulseaudio CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME Date: Thu Feb 22 10:56:06 2018 InstallationDate: Installed on 2018-02-02 (20 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0c45:670c Microdia Bus 001 Device 002: ID 0cf3:e301 Atheros Communications, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9360 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed root=UUID=452f690d-29d8-46b1-88a4-4262b6d20734 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-32-generic N/A linux-backports-modules-4.13.0-32-generic N/A linux-firmware 1.169.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/21/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.4.2 dmi.board.name: 05HM5Y dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.4.2:bd11/21/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn05HM5Y:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9360 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1751098/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1752655] [NEW] retpoline: ignore %cs:0xNNN constant indirections
Public bug reported: These are paravirt style indirections and can be ignored. ** Affects: linux (Ubuntu) Importance: High Assignee: Andy Whitcroft (apw) Status: In Progress ** Affects: linux (Ubuntu Trusty) Importance: Undecided Status: New ** Affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Affects: linux (Ubuntu Artful) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => In Progress ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Andy Whitcroft (apw) ** Also affects: linux (Ubuntu Artful) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Xenial) 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/1752655 Title: retpoline: ignore %cs:0xNNN constant indirections Status in linux package in Ubuntu: In Progress Status in linux source package in Trusty: New Status in linux source package in Xenial: New Status in linux source package in Artful: New Bug description: These are paravirt style indirections and can be ignored. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752655/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1747896] Re: OOM and High CPU utilization in update_blocked_averages because of too many cfs_rqs in rq->leaf_cfs_rq_list
** Changed in: linux (Ubuntu Xenial) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1747896 Title: OOM and High CPU utilization in update_blocked_averages because of too many cfs_rqs in rq->leaf_cfs_rq_list Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Bug description: [Impact] The CPU utilization keeps high and the flamegraph[1] shows that the CPU is busy updating the load average in the for loop inside update_blocked_averages() function. Also, the OOM happens because of the decayed cfs_rqs are not released. [Fix] commit a9e7f6544b9cebdae54d29f87a7ba2a83c0471b5 Author: Tejun Heo Date: Tue Apr 25 17:43:50 2017 -0700 sched/fair: Fix O(nr_cgroups) in load balance path Currently, rq->leaf_cfs_rq_list is a traversal ordered list of all live cfs_rqs which have ever been active on the CPU; unfortunately, this makes update_blocked_averages() O(# total cgroups) which isn't scalable at all. This shows up as a small CPU consumption and scheduling latency increase in the load balancing path in systems with CPU controller enabled across most cgroups. In an edge case where temporary cgroups were leaking, this caused the kernel to consume good several tens of percents of CPU cycles running update_blocked_averages(), each run taking multiple millisecs. This patch fixes the issue by taking empty and fully decayed cfs_rqs off the rq->leaf_cfs_rq_list. [Test] 1). Running the script #/bin/bash for i in $(seq 1 10); do ( for j in $(seq 1 3000); do ssh -S none u@localhost date;done; echo "done $i" ) & done 2). Observe the cfs_rqs $ watch -n1 "grep cfs_rq /proc/sched_debug| wc -l" 3). Observe the CPU utilization rate $ sudo htop The patched kernel[2] shows that the CPU utilization rate is normal, the cfs_rqs is decreased periodically, and the memory can be limited. [Reference] [1]. http://kernel.ubuntu.com/~gavinguo/168887/2018-01-31_07-38-45.perf.data.svg [2]. https://launchpad.net/~mimi0213kimo/+archive/ubuntu/cfs-rq-clean To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1747896/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1745032] Re: AC adapter status not detected on Asus ZenBook UX410UAK
** Also affects: linux (Ubuntu Artful) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Artful) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1745032 Title: AC adapter status not detected on Asus ZenBook UX410UAK Status in linux package in Ubuntu: Fix Committed Status in linux source package in Artful: Fix Committed Bug description: === SRU Justification === [Impact] Some Asus laptops report "discharging" when the battery is full and AC is plugged [Test] Charge battery to full, the issue appears. Users report with the patch the behaviour is correct. [Fix] The discharge rate is 0 on those machines. Use that to detect the wrong status report. [Regression Potential] Low. The quirk uses strict DMI to match affected systems. === Original Bug Report === The AC adapter status is incorrectly reported when the battery is fully charged. It always shows as if the adapter is not plugged in. If the battery is drained for a while, the adapter status is shown correctly (both connects and disconnects are shown). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-31-generic 4.13.0-31.34 ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13 Uname: Linux 4.13.0-31-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: abarto 1388 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Jan 23 18:26:18 2018 InstallationDate: Installed on 2018-01-23 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 04f2:b57a Chicony Electronics Co., Ltd Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX410UAK ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed root=UUID=58ea0561-3f74-4566-9332-5e7021275160 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-31-generic N/A linux-backports-modules-4.13.0-31-generic N/A linux-firmware 1.169.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX410UAK.306 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX410UAK 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.:bvrUX410UAK.306:bd08/08/2017:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX410UAK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1745032/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1661876] Re: [Asus UX360UA] battery status in unity-panel is not changing when battery is being charged
** Also affects: linux (Ubuntu Artful) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Artful) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1661876 Title: [Asus UX360UA] battery status in unity-panel is not changing when battery is being charged Status in linux package in Ubuntu: Fix Committed Status in linux source package in Artful: Fix Committed Bug description: === SRU Justification === [Impact] Some Asus laptops report "discharging" when the battery is full and AC is plugged [Test] Charge battery to full, the issue appears. Users report with the patch the behaviour is correct. [Fix] The discharge rate is 0 on those machines. Use that to detect the wrong status report. [Regression Potential] Low. The quirk uses strict DMI to match affected systems. === Original Bug Report === I've just installed Ubuntu 16.04.1 in dualboot on top of an Asus UX360UA, alongside with Windows 10. I've already installed the updates meanwhile. When I start charging my computer the battery icon on the unity-panel is not changing (it stays in the 98% complete). This is strange because this is a fresh installation so I didn't change any configuration yet. Also, when I tried this ubuntu in the live pen, I noticed that the icon changed when I started charging the laptop. That's why I think it is a bug. --- ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tjiagom1806 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=0eaf9255-c29a-41b7-8449-1eb52f637933 InstallationDate: Installed on 2017-02-04 (0 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 04f2:b56b Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX360UA Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-62-generic.efi.signed root=UUID=6ca1f963-632a-401d-80db-610ef37f1f26 ro quiet splash ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40 RelatedPackageVersions: linux-restricted-modules-4.4.0-62-generic N/A linux-backports-modules-4.4.0-62-generic N/A linux-firmware1.157.6 Tags: xenial Uname: Linux 4.4.0-62-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/17/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX360UA.300 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX360UA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX360UA.300:bd06/17/2016:svnASUSTeKCOMPUTERINC.:pnUX360UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX360UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: UX360UA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1661876/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1482390] Re: ASUS UX305LA - Battery state not detected correctly
** Also affects: linux (Ubuntu Artful) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Artful) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1482390 Title: ASUS UX305LA - Battery state not detected correctly Status in linux package in Ubuntu: Fix Committed Status in linux source package in Artful: Fix Committed Bug description: === SRU Justification === [Impact] Some Asus laptops report "discharging" when the battery is full and AC is plugged [Test] Charge battery to full, the issue appears. Users report with the patch the behaviour is correct. [Fix] The discharge rate is 0 on those machines. Use that to detect the wrong status report. [Regression Potential] Low. The quirk uses strict DMI to match affected systems. === Original Bug Report === Whether the AC adapter is connected or not, the battery is always detected as discharging: When AC adapter is present: $ sudo acpitool -a -b Battery #1 : Discharging, 100.0% AC adapter : online $ sudo acpitool -B Battery #1 : present Remaining capacity : 54027 mWh, 100.0% Design capacity: 56041 mWh Last full capacity : 53507 mWh, 95.48% of design capacity Capacity loss : 4.522% Present rate : 0 mW Charging state : Discharging Battery type : Li-ion Model number : ASUS When AC adapter is not present: $ sudo acpitool -a -b Battery #1 : Discharging, 100.0%, 04:19:49 AC adapter : off-line $ sudo acpitool -B Battery #1 : present Remaining capacity : 54005 mWh, 100.0%, 04:28:31 Design capacity: 56041 mWh Last full capacity : 53507 mWh, 95.48% of design capacity Capacity loss : 4.522% Present rate : 12067 mW Charging state : Discharging Battery type : Li-ion Model number : ASUS System information: $ sudo dmidecode # dmidecode 2.12 # SMBIOS entry point at 0xace2a898 SMBIOS 2.8 present. 27 structures occupying 2154 bytes. Table at 0xAC7C6000. Handle 0x, DMI type 0, 24 bytes BIOS Information Vendor: American Megatrends Inc. Version: UX305LA.202 Release Date: 04/16/2015 Address: 0xF Runtime Size: 64 kB ROM Size: 6464 kB Characteristics: PCI is supported BIOS is upgradeable BIOS shadowing is allowed Boot from CD is supported Selectable boot is supported BIOS ROM is socketed EDD is supported 5.25"/1.2 MB floppy services are supported (int 13h) 3.5"/720 kB floppy services are supported (int 13h) 3.5"/2.88 MB floppy services are supported (int 13h) Print screen service is supported (int 5h) 8042 keyboard services are supported (int 9h) Serial services are supported (int 14h) Printer services are supported (int 17h) ACPI is supported USB legacy is supported Smart battery is supported BIOS boot specification is supported Targeted content distribution is supported UEFI is supported BIOS Revision: 5.6 Handle 0x0001, DMI type 1, 27 bytes System Information Manufacturer: ASUSTeK COMPUTER INC. Product Name: UX305LA Version: 1.0 Serial Number: xxx UUID: xxx Wake-up Type: Power Switch SKU Number: ASUS-NotebookSKU Family: UX Handle 0x0002, DMI type 2, 15 bytes Base Board Information Manufacturer: ASUSTeK COMPUTER INC. Product Name: UX305LA Version: 1.0 Serial Number: xxx Asset Tag: xxx Features: Board is a hosting board Board is replaceable Location In Chassis: MIDDLE Chassis Handle: 0x0003 Type: Motherboard Contained Object Handles: 0 Handle 0x0003, DMI type 3, 25 bytes Chassis Information Manufacturer: ASUSTeK COMPUTER INC. Type: Notebook Lock: Not Present Version: 1.0 Serial Number: xxx Asset Tag: xxx Boot-up State: Safe Power Supply State: Safe Thermal State: Safe Security Status: None OEM Information: 0x Height: Unspecified Number Of Power Cords: 1 Contained Elements: 1 (0) SKU Number: To be filled by O.E.M. Handle 0x0004, DMI type 10, 26 bytes On Board Device 1 Information Type: Video Status: Enabled Description: VGA On Board Device 2 Information Type: Ethernet Status: Enabled Description: GLAN On Board Device 3 Information Type: Ethernet Status: Enabled Description: WLAN On Board Device 4 Information Type: Sound Status: Enabled Description: Audio CODEC On Board Device 5 Information Type: SATA Controller Status: Enabled Description: SATA Controller On Board Device 6 Information Type: Other Status: Enabled Description: USB 2.0 Controller On Board Device 7 Information Type: Other Status: Enabled Description:
[Kernel-packages] [Bug 1748157] Re: [MIR] thunderbolt-tools
** Changed in: thunderbolt-tools (Ubuntu) Importance: High => Critical -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thunderbolt-tools in Ubuntu. Matching subscriptions: Kernel Packages https://bugs.launchpad.net/bugs/1748157 Title: [MIR] thunderbolt-tools Status in thunderbolt-tools package in Ubuntu: Confirmed Bug description: == Overview == Intel Thunderbolt userspace components provides components for using Intel Thunderbolt controllers with security level features. Thunderbolt™ technology is a transformational high-speed, dual protocol I/O that provides unmatched performance with up to 40Gbps bi- directional transfer speeds. It provides flexibility and simplicity by supporting both data (PCIe, USB3.1) and video (DisplayPort) on a single cable connection that can daisy-chain up to six devices. [ See https://github.com/intel/thunderbolt-software-user-space ] == Answers to UbuntuMainInclusionRequirements == = Requirements = 1. Availability Package is in universe: https://launchpad.net/ubuntu/+source/thunderbolt-tools 2. Rationale Package a device enabler for users with Thunderbolt technology 3. Security: No security issues exposed so far. However, the tools have only been in Ubuntu since 2017-12-09, so this currently is less than the 90 days threshold. 4. Quality assurance: * Manual is provided * No debconf questions higher than medium * No major outstanding bugs. I'm also helping Intel fix issues that I'm finding with static analysis tools such as scan-build, cppcheck and CoverityScan Bugs outstanding: #883857 please backport for stretch-backports #882525 thunderbolt-tools: FTBFS on kFreeBSD: _ZN5boost6system15system_categoryEv undefined - I can fix this, but it makes no sense to run on kFreeBSD * Exotic Hardware: Only Thunderbolt supported H/W is required, this is an industry standard and the support for the tools are in the 4.13+ kernels * No Test Suite shipped with the package * Does not rely on obsolete or demoted packages 5. UI standards: * This is a CLI tool. Tool has normal CLI style short help and man pages * No desktop file required as it is a CLI tool. 6. Binary Dependencies: libboost-dev(main) libboost-filesystem-dev (main) libboost-program-options-dev(main) udev(main) 7. Standards compliance: lintian clean and meets the FHS + Debian Policy standards to the best of my knowledge 8. Maintenance * Package owning team: The Ubuntu Kernel Team * Debian package maintained by Colin Ian King (myself from the Kernel Team) 9. Background Information The user-space components implement device approval support: a. Easier interaction with the kernel module for approving connected devices. b. ACL for auto-approving devices white-listed by the user. Tools provided by this package: tbtacl - triggered by udev (see the udev rules in tbtacl.rules). It auto-approves devices that are found in ACL. tbtadm - user-facing CLI tool. It provides operations for device approval, handling the ACL and more. The user-space components operate in coordination with the upstream Thunderbolt kernel driver (found in v4.13) to provide the Thunderbolt functionalities. These components are NOT compatible with the old out-of-tree Thunderbolt kernel module. = Security checks = http://cve.mitre.org/cve/cve.html: Search in the National Vulnerability Database using the package as a keyword * No CVEs found http://secunia.com/advisories/search/: search for the package as a keyword * No security advisories found Ubuntu CVE Tracker http://people.ubuntu.com/~ubuntu-security/cve/main.html * No http://people.ubuntu.com/~ubuntu-security/cve/universe.html * No http://people.ubuntu.com/~ubuntu-security/cve/partner.html * No Check for security relevant binaries. If any are present, this requires a more in-depth security review. Executables which have the suid or sgid bit set. * Not applicable Executables in /sbin, /usr/sbin. * None in these paths Packages which install daemons (/etc/init.d/*) * No Packages which open privileged ports (ports < 1024). * No Add-ons and plugins to security-sensitive software (filters, scanners, UI skins, etc) * This does exec tbtacl from udev with new udev rules, so this needs security checking To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbolt-tools/+bug/1748157/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launc
[Kernel-packages] [Bug 1750385] Re: Poor wifi signal with RTL8723BE and 4.13.0-32 kernel
I have the bluetooth adapter powered off in Manjaro but I also have it powered off in Mint (I did not check the bluetooth state in the live ubuntu-image on the USB though). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1750385 Title: Poor wifi signal with RTL8723BE and 4.13.0-32 kernel Status in linux package in Ubuntu: Confirmed Bug description: When using Linux Mint 18.3 alongside with the 4.13.0-32 kernel the wifi signal is really really poor (while almost sitting on the respective router) whereas with the 4.10.0-38 it works like charm. I had to use a configuration file for getting the wifi to work properly (/etc/modprobe.d/rtl8723be.conf: options rtl8723be fwlps=0 ips=0 ant_sel=1) but chaning the antenna from 1 to 0 did not change anything with the 4.13 kernel. I am also running Manjaro Linux with the 4.14 kernel on my machine where the wifi is also working just fine (with antenna 0 though). cat /proc/version_signature: Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17 (I tried using ubuntu-bug linux but it didn't work [The report belongs to a package that is not installed.]) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1750385/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1752672] [NEW] CAPI Flash (cxlflash) update
You have been subscribed to a public bug: This is a feature for capi flash (cxlflash) inside the kernel. We have upstreamed the below 38 patches but they are not in the maintainers tree yet. I anticipate them to be available by Friday this week. I dont want to miss the boat for 18.04 feature code cutoff. Can you please suggest if I should submit these patches as SAUCE patches or can it be pulled from mainstream once maintainer pulls it in ? 8d34234b7e44caa489bb7e684ead1f13b74faf72 cxlflash: Preserve number of interrupts for master contexts 8f20948fde0a06a283b39c3646c8060b62319875 cxlflash: Avoid clobbering context control register value 44569c367471bd57916798a701ad1c7250ec93fb cxlflash: Add argument identifier names 9e63cdb74178a02fa76c3896c2e38479148e60bf cxlflash: Introduce OCXL backend 0aa60ffb7ca4ce3f5cb33231d9358ab9f0ae9ec4 cxlflash: Hardware AFU for OCXL f9e6817464036867a6994732c3b8b873b6fdc530 cxlflash: Read host function configuration f1718592638ef1e3486ded07ba9aebf784b03db3 cxlflash: Setup function acTag range 77ece8688ed48e693bbdfef7b856ed146dac5838 cxlflash: Read host AFU configuration 6491b3338076c8a71f70c326aeacf7ecde139124 cxlflash: Setup AFU acTag range 90fbea09364d3a32b6b2b0fbbd56c4fbaabe5400 cxlflash: Setup AFU PASID 16e8be014d2efa0f7e713d5e7cfae9348eaab6fd cxlflash: Adapter context support for OCXL 2d431a892b91f9f004a8b6413d990c55dac6ac16 cxlflash: Use IDR to manage adapter contexts d0dd47f71da4a9f37cfd2eced36f85c2751fcdf5 cxlflash: Support adapter file descriptors for OCXL 1719110f42503bcac6962daf4492cec3c16c325f cxlflash: Support adapter context discovery e9ff19884da98139427e23c8ce3bed7614427fed cxlflash: Support image reload policy modification 5706f2a40306b2fe5ffae6fa1eacc81afed3fa11 cxlflash: MMIO map the AFU 99b7d36979c67708851f8058c9fb6e412d32577b cxlflash: Support starting an adapter context d8e72cf527fed71641dd011dff13fbd1e5fad2da cxlflash: Support process specific mappings 8cc796025b082c13c1ec3db620e9f23f6082726a cxlflash: Support AFU state toggling 9e0d9716935bdf9e2c24d3c27ae8be1756eff46e cxlflash: Support reading adapter VPD data b37e0fdd868e47221e706be4d51c66e5e9224f20 cxlflash: Setup function OCXL link 099858c80b956752693e0d3bb8f01618a11d48dc cxlflash: Setup OCXL transaction layer 5b1a1f3d49ee4b41778e41bf8147febc885df381 cxlflash: Support process element lifecycle 0e3e9fbfada4506620610497cdc6ce0a0b3cdff2 cxlflash: Support AFU interrupt management ff7388a91f3739c5420b16f20d74644f5da9b03a cxlflash: Support AFU interrupt mapping and registration cfa71c77fd9e440b1d8f105151eaf30aff5f3241 cxlflash: Support starting user contexts 270a401d0901eeb736b1da4fd728006ae4d40145 cxlflash: Support adapter context polling 302ce17cba275e295803a2a2aad83debfd02cf5d cxlflash: Support adapter context reading cc8640bac30541ddc453834d5956ced223ed0020 cxlflash: Support adapter context mmap and release a071c05a8cab915a3a7d11a87b06da00bc5bc7d5 cxlflash: Support file descriptor mapping eb01b23138c73967c17c04e79ab4c5df4649984e cxlflash: Introduce object handle fop c6a2e3b15bd5a6f85472eac54fede0cffcd6d4e5 cxlflash: Setup LISNs for user contexts bbfdb7e4d852d213b3b474185918a94aabecad7f cxlflash: Setup LISNs for master contexts e8d361505cef408ec3afb5f0cf1e4c3fd7f6150b cxlflash: Update synchronous interrupt status bits dc8e5211cbd6457f618bc49df7e769895b6996bc cxlflash: Introduce OCXL context state machine 9c5567f5e9c92a9f94f7790b2dd905235bc9842c cxlflash: Register for translation errors 96cacd8347f27d258bae75d796cc1f523724a37a cxlflash: Support AFU reset 966a6e64ddd9624999d895fffab190c7d2f96c85 cxlflash: Enable OCXL operations <<< The above is from my local git tree but it has been already sent to linux-scsi mailing list >>> ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) Status: New ** Tags: architecture-ppc64le bugnameltc-163818 severity-medium targetmilestone-inin1804 -- CAPI Flash (cxlflash) update https://bugs.launchpad.net/bugs/1752672 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
