[Kernel-packages] [Bug 1830175] Re: Add support to Comet Lake LPSS
** Changed in: linux (Ubuntu Bionic) Status: Incomplete => Fix Committed ** Changed in: linux (Ubuntu Cosmic) Status: Incomplete => Fix Committed ** Changed in: linux (Ubuntu Disco) Status: Incomplete => 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/1830175 Title: Add support to Comet Lake LPSS Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-oem-osp1 package in Ubuntu: New Status in linux source package in Bionic: Fix Committed Status in linux-oem-osp1 source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Committed Status in linux-oem-osp1 source package in Cosmic: Invalid Status in linux source package in Disco: Fix Committed Status in linux-oem-osp1 source package in Disco: Invalid Bug description: [Impact] I2C touchpad doesn't work when it's connected to Comet Lake LPSS, which isn't supported. [Fix] Add CML LPSS PCI IDs to intel-lpss module. [Test] The I2C touchpad connected to CML LPSS works after applying the patch. [Regression Potential] None. It's a new device enablement. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1830175/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822133] Re: Azure Instance never recovered during series of instance reboots.
This bit me tonight on a few days old 18.04 VM with stock kernel. So far I can not get back in with reboot or redeploy to upgrade the kernel. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1822133 Title: Azure Instance never recovered during series of instance reboots. Status in linux-azure package in Ubuntu: In Progress Bug description: Description: During SRU Testing of various Azure Instances, there will be some cases where the instance will not respond following a system reboot. SRU Testing only restarts a giving instance once, after it preps all of the necessary files to-be-tested. Series: Disco Instance Size: Basic_A3 Region: (Default) US-WEST-2 Kernel Version: 4.18.0-1013-azure #13-Ubuntu SMP Thu Feb 28 22:54:16 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux I initiated a series of tests which rebooted Azure Cloud instances 50 times. During the 49th Reboot, an Instance failed to return from a reboot.. Upon grabbing the console output the following was seen scrolling endlessly. I have seen this failure in cases where the instance only restarted a handful of times >5 [84.247704]hyperv_fb: unable to send packet via vmbus [84.247704]hyperv_fb: unable to send packet via vmbus [84.247704]hyperv_fb: unable to send packet via vmbus [84.247704]hyperv_fb: unable to send packet via vmbus [84.247704]hyperv_fb: unable to send packet via vmbus [84.247704]hyperv_fb: unable to send packet via vmbus [84.247704]hyperv_fb: unable to send packet via vmbus [84.247704]hyperv_fb: unable to send packet via vmbus In another test attempt I saw the following failure: ERROR ExtHandler /proc/net/route contains no routes ERROR ExtHandler /proc/net/route contains no routes ERROR ExtHandler /proc/net/route contains no routes ERROR ExtHandler /proc/net/route contains no routes ERROR ExtHandler /proc/net/route contains no routes ERROR ExtHandler /proc/net/route contains no routes ERROR ExtHandler /proc/net/route contains no routes Both of these failures broke networking, Both of these failures were seen at least twice to three times, thus may explain why in some cases we never recover from an instance reboot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1822133/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1830587] Re: Reduce NAPI weight in hns driver from 256 to 64
** Changed in: linux (Ubuntu Bionic) Status: Incomplete => Fix Committed ** Changed in: linux (Ubuntu Cosmic) Status: Incomplete => Fix Committed ** Changed in: linux (Ubuntu Disco) Status: Incomplete => 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/1830587 Title: Reduce NAPI weight in hns driver from 256 to 64 Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Committed Status in linux source package in Disco: Fix Committed Status in linux source package in Eoan: Incomplete Bug description: [Impact] We have a warning[1] in dmesg shows hns register napi as weight 256 but not recommended. According to this commit[2] we shall use weight 64 as suggested. [1] netif_napi_add() called with weight 256 [2] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=82dc3c63c692b1e1d59378ecee948ac88e034aad [Test Case] dmesg | grep netif_napi_add [Fix] commit acb1ce15a61154aa501891d67ebf79bc9ea26818 Author: Yonglong Liu Date: Thu Apr 4 16:46:43 2019 +0800 net: hns: Use NAPI_POLL_WEIGHT for hns driver When the HNS driver loaded, always have an error print: "netif_napi_add() called with weight 256" This is because the kernel checks the NAPI polling weights requested by drivers and it prints an error message if a driver requests a weight bigger than 64. So use NAPI_POLL_WEIGHT to fix it. Signed-off-by: Yonglong Liu Signed-off-by: Peng Li Signed-off-by: David S. Miller [Regression Risk] Only weight for NAPI changed. Lowest regression risk. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1830587/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829195] Re: linux-kvm: 4.4.0-1047.53 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1830941 phase: Testing phase-changed: Monday, 20. May 2019 11:54 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED - regression-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1829195 Title: linux-kvm: 4.4.0-1047.53 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1830941 phase: Testing phase-changed: Monday, 20. May 2019 11:54 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1829195/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829195] Re: linux-kvm: 4.4.0-1047.53 -proposed tracker
4.4.0-1047.53 - kvm Regression test CMPL, RTB. Issue to note in amd64: ubuntu_fan_smoke_test - ubuntu_fan_smoke_test failed on 4.4 X-kvm kernel (bug 1763323) ubuntu_kernel_selftests - psock_tpacket in net failed (bug 1812176) test_bpf in net (bug 1812189) test_user_copy return code in user (bug 1812352) ubuntu_kvm_unit_tests - proxy issue for Intel Cloud (bug 1828786) ubuntu_ltp_syscalls - proxy issue for Intel Cloud (bug 1828786) ubuntu_lxc - ERROR: Unable to fetch GPG key from keyserver. proxy issue for Intel Cloud (bug 1828786) ubuntu_qrt_apparmor - apparmor issue (bug 1830802) ubuntu_qrt_kernel_security - SCHED_STACK_END_CHECK should be enabled (bug 1812159) ubuntu_quota_smoke_test - failed with KVM kernel (bug 1784535) ubuntu_ramfs_stress - proxy issue for Intel Cloud (bug 1828786) ubuntu_stress_smoke_test - proxy issue for Intel Cloud (bug 1828786) ubuntu_unionmount_overlayfs_suite - proxy issue for Intel Cloud (bug 1828786) ubuntu_vfat_stress - proxy issue for Intel Cloud (bug 1828786) Skipped / blacklisted: * ubuntu_blktrace_smoke_test * ubuntu_ftrace_smoke_test * ubuntu_lttng_smoke_test * ubuntu_seccomp * ubuntu_sysdig_smoke_test ** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Assignee: Canonical Kernel Team (canonical-kernel-team) => Po-Hsu Lin (cypressyew) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1829195 Title: linux-kvm: 4.4.0-1047.53 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1830941 phase: Testing phase-changed: Monday, 20. May 2019 11:54 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1829195/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829621] Re: [HP Laptop 14-ma0xxx] No sound after suspend (kernels 5.0.0 and 5.1.5 faulty, but not 5.0.1)
I installed your kernel and commented out the previous manual configuration. All is working fine and the speakers are working after suspend, too. So the bug can't be reproduced. 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/1829621 Title: [HP Laptop 14-ma0xxx] No sound after suspend (kernels 5.0.0 and 5.1.5 faulty, but not 5.0.1) Status in linux package in Ubuntu: Incomplete Bug description: On my Laptop sound is working only after a fresh reboot. Every time I suspend the laptop, I can no longer use the internal speakers or any headphones. I tried a lot of solutions suggested online none of them working for me. Since this problem is very annoying I would really appreciate if a fix would be available. Thanks a lot :) Additional information: Laptop: HP 14-ma0307ng Ubuntu 19.04 Audio: sudo lspci -v | grep -A7 -i "audio" 00:0e.0 Audio device: Intel Corporation Device 3198 (rev 03) Subsystem: Hewlett-Packard Company Device 84b6 Flags: bus master, fast devsel, latency 0, IRQ 25 Memory at a131 (64-bit, non-prefetchable) [size=16K] Memory at a100 (64-bit, non-prefetchable) [size=1M] Capabilities: [50] Power Management version 3 Capabilities: [80] Vendor Specific Information: Len=14 Capabilities: [60] MSI: Enable- Count=1/1 Maskable- 64bit+ ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 Uname: Linux 5.0.0-15-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: harry 5835 F pulseaudio /dev/snd/pcmC0D0c: harry 5835 F...m pulseaudio /dev/snd/pcmC0D0p: harry 5835 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat May 18 19:12:01 2019 InstallationDate: Installed on 2019-04-30 (18 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/09/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.05 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 84B6 dmi.board.vendor: HP dmi.board.version: KBC Version 76.17 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.05:bd04/09/2018:svnHP:pnHPLaptop14-ma0xxx:pvrType1ProductConfigId:rvnHP:rn84B6:rvrKBCVersion76.17:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 14-ma0xxx dmi.product.sku: 4DL72EA#ABD dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829621/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1830941] Re: linux: 4.4.0-150.176 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed ** Tags added: block-proposed-xenial ** Tags added: block-proposed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1829205 (trusty/linux-aws), bug 1830947 (trusty/linux-lts-xenial) derivatives: bug 1829193 (linux-aws), bug 1829195 (linux-kvm), bug 1829198 (linux-raspi2), bug 1829201 (linux-snapdragon), bug 1829203 (linux-fips) -- swm properties -- - phase: Holding before Promote to Proposed - phase-changed: Wednesday, 29. May 2019 19:32 UTC + boot-testing-requested: true + phase: Ready for Promote to Proposed + phase-changed: Thursday, 30. May 2019 03:32 UTC reason: - promote-to-proposed: Pending -- builds not complete in ppa meta:building + promote-to-proposed: Pending -- ready for review -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1830941 Title: linux: 4.4.0-150.176 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-certification-testing series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1829205 (trusty/linux-aws), bug 1830947 (trusty/linux-lts-xenial) derivatives: bug 1829193 (linux-aws), bug 1829195 (linux-kvm), bug 1829198 (linux-raspi2), bug 1829201 (linux-snapdragon), bug 1829203 (linux-fips) -- swm properties -- boot-testing-requested: true phase: Ready for Promote to Proposed phase-changed: Thursday, 30. May 2019 03:32 UTC reason: promote-to-proposed: Pending -- ready for review To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1830941/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829209] Re: linux: 4.4.0-149.175 -proposed tracker
*** This bug is a duplicate of bug 1830941 *** https://bugs.launchpad.net/bugs/1830941 4.4.0-149.175 - generic Regression test CMPL, RTB. 53 / 54 tests were run, missing: xfstests Issue to note in amd64: ubuntu_kvm_unit_tests - apic timeouted (bug 1748103) debug (bug 1821906) ubuntu_ltp_syscalls - inotify07 (bug 1774387) inotify08 (bug 1775784) fanotify07/fanotify08 timeouted (bug 1775165) fanotify09 timeouted (bug 1775153) fanotify10 timeouted (bug 1802454) fanotify11 timeouted (bug 1808107) fanotify12 timeouted (bug 1828813) sync_file_range02 (bug 1819116) ubuntu_qrt_apparmor - apparmor issue (bug 1830802) ubuntu_ramfs_stress - proxy issue for Intel Cloud (bug 1828786) 48 / 49 tests were run, missing: xfstests Issue to note in arm64: hwclock - issue for HP m400 (bug 1716603) ubuntu_kernel_selftests - cpu-hotplug failed on moonshot (bug 1809701) ubuntu_kvm_smoke_test - unable to create KVM with uvtool (bug 1749427) ubuntu_kvm_unit_tests - pmu on ms10-34-mcdivittB0-kernel (bug 1751000) gicv2-mmio on X-ARM64 (bug 1828165) gicv2 related test failed on ThunderX (bug 1828153) ubuntu_ltp_syscalls - inotify07 (bug 1774387) inotify08 (bug 1775784) fanotify07/fanotify08 timeouted (bug 1775165) fanotify09 timeouted (bug 1775153) fanotify10 timeouted (bug 1802454) fanotify11 timeouted (bug 1808107) fanotify12 timeouted (bug 1828813) sync_file_range02 (bug 1819116) ubuntu_qrt_apparmor - apparmor issue (bug 1830802) Issue to note in i386: ubuntu_kvm_smoke_test - timed out waiting for dnsmasq lease (bug 1802056) ubuntu_kvm_unit_tests - unable to build on X/T i386 (bug 1798007) ubuntu_ltp_syscalls - inotify07 (bug 1774387) inotify08 (bug 1775784) fanotify07/fanotify08 timeouted (bug 1775165) fanotify09 timeouted (bug 1775153) fanotify10 timeouted (bug 1802454) fanotify11 timeouted (bug 1808107) fanotify12 timeouted (bug 1828813) sync_file_range02 (bug 1819116) ubuntu_qrt_apparmor - apparmor issue (bug 1830802) xfstests - xfs generic/308 timed out (bug 1738152) Issue to note in ppc64le (P8): ubuntu_btrfs_kernel_fixes - Unable to mount a btrfs filesystem smaller than 320M on Xenial P8 (bug 1813863) ubuntu_ltp_syscalls - fallocate05, fsetxattr01, fgetxattr01, fsync01, preadv03, preadv03_64, pwritev03, pwritev03_64, setxattr01 (bug 1785198) inotify07 (bug 1774387) inotify08 (bug 1775784) fanotify07/fanotify08 timeouted (bug 1775165) fanotify09 timeouted (bug 1775153) fanotify10 timeouted (bug 1802454) fanotify11 timeouted (bug 1808107) fanotify12 timeouted (bug 1828813) ubuntu_qrt_apparmor - apparmor issue (bug 1830802) xfstests - btrfs generic/176 timed out Issue to note in s390x (KVM): libhugetlbfs - failed 11 killed by signal 7 bad config 1 ubuntu_bpf_jit - 4 failures reported for X s390x (bug 1768452) ubuntu_kernel_selftests - test_bpf in net (bug 1768452) ubuntu_kvm_smoke_test - uvtool issue (bug 1729854) ubuntu_kvm_unit_tests - All tests failed on s390x KVM (bug 1822542) ubuntu_ltp_syscalls - inotify07 (bug 1774387) inotify08 (bug 1775784) fanotify07/fanotify08 timeouted (bug 1775165) fanotify09 timeouted (bug 1775153) fanotify10 timeouted (bug 1802454) fanotify11 timeouted (bug 1808107) fanotify12 timeouted (bug 1828813) sync_file_range02 (bug 1819116) ubuntu_qrt_apparmor - apparmor issue (bug 1830802) ubuntu_qrt_kernel_security - SECURITY_SELINUX_DISABLE option should be enable on X s390x (bug 1813721) 47 / 48 tests were run, missing: ubuntu_boot Issue to note in s390x (Ubuntu on LPAR): libhugetlbfs - failed 11 killed by signal 7 bad config 1 ubuntu_bpf_jit - 4 failures reported for X s390x (bug 1768452) ubuntu_kernel_selftests - test_bpf in net (bug 1768452) ubuntu_kvm_smoke_test - uvtool issue (bug 1729854) ubuntu_ltp_syscalls - inotify07 (bug 1774387) inotify08 (bug 1775784) fanotify07/fanotify08 timeouted (bug 1775165) fanotify09 timeouted (bug 1775153) fanotify10 timeouted (bug 1802454) fanotify11 timeouted (bug 1808107) fanotify12 timeouted (bug 1828813) sync_file_range02 (bug 1819116) ubuntu_qrt_apparmor - apparmor issue (bug 1830802) ubuntu_qrt_kernel_security - SECURITY_SELINUX_DISABLE option should be enable on X s390x (bug 1813721) 47 / 48 tests were run, missing: ubuntu_boot Issue to note in s390x (zVM): libhugetlbfs - failed 11 killed by signal 7 bad config 1 ubuntu_bpf_jit - 4 failures reported for X s390x (bug 1768452) ubuntu_kernel_selftests - test_bpf in net (bug 1768452) ubuntu_kvm_smoke_test - uvtool issue (bug 1729854) ubuntu_kvm_unit_tests - skey failed on zVM (bug 1778705) ubuntu_ltp_syscalls - inotify07 (bug 1774387) inotify08 (bug 1775784) fanotify07/fanotify08 timeouted (bug 1775165) fanotify09 timeouted (bug 1775153) fanotify10 timeouted (bug 1802454) fanotify11 timeouted (bug 1808107) fanotify12 timeouted (bug 1828813) sync_file_range02 (bug 1819116) ubuntu_qrt_apparmor - apparmor issue (bug 1830802) ubuntu_qrt_kernel_security - SECURITY_SELINUX_DISABLE option should
[Kernel-packages] [Bug 1619679] Re: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu0.1: bcmwl kernel module failed to build [error: ‘STATION_INFO_TX_BITRATE’ undeclared]
** Tags added: xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1619679 Title: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu0.1: bcmwl kernel module failed to build [error: ‘STATION_INFO_TX_BITRATE’ undeclared] Status in bcmwl package in Ubuntu: Confirmed Bug description: DKMS 4.4.0-36_generic Latest kernel 4.4, Ubuntu was Launched with kernel 3.19.066 when bug was occurred. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu0.1 ProcVersionSignature: Ubuntu 3.19.0-66.74~14.04.1-generic 3.19.8-ckt22 Uname: Linux 3.19.0-66-generic x86_64 NonfreeKernelModules: wl nvidia ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 DKMSKernelVersion: 4.4.0-36-generic Date: Fri Sep 2 10:13:50 2016 DuplicateSignature: dkms:bcmwl-kernel-source:6.30.223.248+bdcom-0ubuntu0.1:/var/lib/dkms/bcmwl/6.30.223.248+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:1444:20: error: ‘STATION_INFO_TX_BITRATE’ undeclared (first use in this function) InstallationDate: Installed on 2015-11-07 (299 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) PackageVersion: 6.30.223.248+bdcom-0ubuntu0.1 RelatedPackageVersions: dpkg 1.17.5ubuntu5.7 apt 1.0.1ubuntu2.14 SourcePackage: bcmwl Title: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu0.1: bcmwl kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1619679/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1830582] Re: nvidia-384 384.130-0ubuntu0.16.04.2: nvidia-384 kernel module failed to build [arch/x86/Makefile:245: *** You are building kernel with non-retpoline compiler, pleas
We tell build failure bugs apart according to their error messages. So the error message should go in the title. In this case it suggests you have an unusual C compiler installed as the default compiler. Can you check what this command tells you? cc --version -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-384 in Ubuntu. https://bugs.launchpad.net/bugs/1830582 Title: nvidia-384 384.130-0ubuntu0.16.04.2: nvidia-384 kernel module failed to build [arch/x86/Makefile:245: *** You are building kernel with non- retpoline compiler, please update your compiler.. Stop.] Status in nvidia-graphics-drivers-384 package in Ubuntu: New Bug description: not sure what tickled it. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: nvidia-384 384.130-0ubuntu0.16.04.2 ProcVersionSignature: Ubuntu 4.15.0-47.50~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-47-generic x86_64 NonfreeKernelModules: nvidia_uvm wl nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 DKMSKernelVersion: 4.15.0-50-generic Date: Sun May 26 22:48:29 2019 InstallationDate: Installed on 2017-09-29 (604 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageVersion: 384.130-0ubuntu0.16.04.2 RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.31 SourcePackage: nvidia-graphics-drivers-384 Title: nvidia-384 384.130-0ubuntu0.16.04.2: nvidia-384 kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-384/+bug/1830582/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1830861] Re: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu0.0.2: bcmwl kernel module failed to build [error: ‘STATION_INFO_TX_BITRATE’ undeclared (first use in this function)]
*** This bug is a duplicate of bug 1619679 *** https://bugs.launchpad.net/bugs/1619679 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1619679, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** Summary changed: - bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu0.0.2: bcmwl kernel module failed to build + bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu0.0.2: bcmwl kernel module failed to build [error: ‘STATION_INFO_TX_BITRATE’ undeclared (first use in this function)] ** This bug has been marked a duplicate of bug 1619679 bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu0.1: bcmwl kernel module failed to build [error: ‘STATION_INFO_TX_BITRATE’ undeclared] -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1830861 Title: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu0.0.2: bcmwl kernel module failed to build [error: ‘STATION_INFO_TX_BITRATE’ undeclared (first use in this function)] Status in bcmwl package in Ubuntu: New Bug description: it appears almost everytime i start my system ProblemType: Package DistroRelease: Ubuntu 16.04 Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu0.0.2 ProcVersionSignature: Ubuntu 4.15.0-50.54~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-50-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 DKMSKernelVersion: 4.4.0-148-generic Date: Mon May 27 09:37:19 2019 DuplicateSignature: dkms:bcmwl-kernel-source:6.30.223.248+bdcom-0ubuntu0.0.2:/var/lib/dkms/bcmwl/6.30.223.248+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:1444:20: error: ‘STATION_INFO_TX_BITRATE’ undeclared (first use in this function) InstallationDate: Installed on 2017-05-17 (741 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) PackageVersion: 6.30.223.248+bdcom-0ubuntu0.0.2 RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.29ubuntu0.1 SourcePackage: bcmwl Title: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu0.0.2: bcmwl kernel module failed to build UpgradeStatus: Upgraded to xenial on 2018-08-28 (274 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1830861/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1597201] Re: 16.04 LTS NFS4 Client hangs when copying large files
I can confirm the same issue in Xubuntu 18.04. (Should I submit my logs or open a new issue?) 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/1597201 Title: 16.04 LTS NFS4 Client hangs when copying large files Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: When doing simple copy-jobs with large files (f.ex. Partition Images > 4 GByte filesize)the file transfer allways stall after about 16 GByte has passed to the Client. No Problems using kernel-versions up to kernel 4.2 (Ubuntu 14.04 up to 15.10). Verified with new installations of 16.04 LTS as well as upgraded (previous working) 15.10 workstations to 16.04 LTS. Autonegotiated NFS-values are still the same: Working 15.10 version: server:/informatik/ab on /informatik/ab type nfs4 (rw,relatime,vers=4.0,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,port=0,timeo=600,retrans=2,sec=krb5,clientaddr=134.100.9.19,local_lock=none,addr=XXX.XXX.XXX.XXX) Failing 16.04 LTS Version: server:/informatik/ab on /informatik/ab type nfs4 (rw,relatime,vers=4.0,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,port=0,timeo=600,retrans=2,sec=krb5,clientaddr=134.100.9.19,local_lock=none,addr=XXX.XXX.XXX.XXX) --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=cd090c32-9f7e-4bd7-8c80-a4db905603a6 InstallationDate: Installed on 2016-03-30 (90 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) IwConfig: lono wireless extensions. eth0 no wireless extensions. Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Microsoft Corporation Virtual Machine Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 hyperv_fb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-24-generic root=UUID=1339be3a-6951-42eb-b098-3f21cb2aeb60 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 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.4.0-24-generic N/A linux-backports-modules-4.4.0-24-generic N/A linux-firmware1.157 RfKill: Tags: xenial Uname: Linux 4.4.0-24-generic x86_64 UpgradeStatus: Upgraded to xenial on 2016-06-23 (5 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 05/23/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 090006 dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: 7.0 dmi.chassis.asset.tag: 6366-7166-8325-4285-5123-7124-57 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: 7.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr090006:bd05/23/2012:svnMicrosoftCorporation:pnVirtualMachine:pvr7.0:rvnMicrosoftCorporation:rnVirtualMachine:rvr7.0:cvnMicrosoftCorporation:ct3:cvr7.0: dmi.product.name: Virtual Machine dmi.product.version: 7.0 dmi.sys.vendor: Microsoft Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1597201/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1830792] Re: Rotated display is overscaled and overdrawn
I am seeing a lot of crashes in the i915 kernel driver in your kernel log like: May 28 15:54:36 nix-us2ua34705wc kernel: Call Trace: May 28 15:54:36 nix-us2ua34705wc kernel: intel_atomic_commit+0x2b8/0x2f0 [i915] May 28 15:54:36 nix-us2ua34705wc kernel: drm_atomic_commit+0x4a/0x50 [drm] May 28 15:54:36 nix-us2ua34705wc kernel: drm_mode_atomic_ioctl+0x8e9/0xa00 [drm] This suggests it might be a kernel bug. But I also know the atomic API is only used by the Xorg modesetting driver. You might be able to avoid the problem then by logging into "Ubuntu on Wayland". Does that work? ** Also affects: xorg-server (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Rotated display is overscaled and overdrawn + [i915] Rotated display is overscaled and overdrawn ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Changed in: mutter (Ubuntu) Status: New => Incomplete ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1830792 Title: [i915] Rotated display is overscaled and overdrawn Status in gnome-shell package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: On my system I have two display: one in landscape, and one in portrait. The landscape display is fine, but the portrait display is corrupted. If I unplug the display from the computer for some time and then plug it back in it will occasionally fix the problem. Once the problem is fixed, the display works perfectly fine, indefinitely. However, as soon as I reboot the computer the display will come up corrupted again and never recovers without many rounds of plug/unplug turn off/turn on. It's extremely frustrating. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.32.0+git20190410-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 Uname: Linux 5.0.0-15-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue May 28 15:57:02 2019 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'command-history' redacted by apport b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/fish SourcePackage: gnome-shell UpgradeStatus: Upgraded to disco on 2019-04-22 (36 days ago) modified.conffile..etc.logrotate.d.apport: [modified] mtime.conffile..etc.logrotate.d.apport: 2019-01-12T15:50:59.090583 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1830792/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1830941] Re: linux: 4.4.0-150.176 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1829205 (trusty/linux-aws), bug 1830947 (trusty/linux-lts-xenial) derivatives: bug 1829193 (linux-aws), bug 1829195 (linux-kvm), bug 1829198 (linux-raspi2), bug 1829201 (linux-snapdragon), bug 1829203 (linux-fips) -- swm properties -- phase: Holding before Promote to Proposed phase-changed: Wednesday, 29. May 2019 19:32 UTC reason: - promote-to-proposed: Pending -- builds not complete in ppa meta:building,main:building + promote-to-proposed: Pending -- builds not complete in ppa meta:building -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1830941 Title: linux: 4.4.0-150.176 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-certification-testing series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1829205 (trusty/linux-aws), bug 1830947 (trusty/linux-lts-xenial) derivatives: bug 1829193 (linux-aws), bug 1829195 (linux-kvm), bug 1829198 (linux-raspi2), bug 1829201 (linux-snapdragon), bug 1829203 (linux-fips) -- swm properties -- phase: Holding before Promote to Proposed phase-changed: Wednesday, 29. May 2019 19:32 UTC reason: promote-to-proposed: Pending -- builds not complete in ppa meta:building To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1830941/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822133] Re: Azure Instance never recovered during series of instance reboots.
It's glad to see the issue can not repro with the 5.0.0-1007.7 kernel. @sfeole: The line "[ 84.247704]hyperv_fb: unable to send packet via vmbus" usually means the VM has panicked. Do you happen to still keep the full serial log containing this line of error? It would be good to understand this error for the 4.18.0-1013-azure kernel. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1822133 Title: Azure Instance never recovered during series of instance reboots. Status in linux-azure package in Ubuntu: In Progress Bug description: Description: During SRU Testing of various Azure Instances, there will be some cases where the instance will not respond following a system reboot. SRU Testing only restarts a giving instance once, after it preps all of the necessary files to-be-tested. Series: Disco Instance Size: Basic_A3 Region: (Default) US-WEST-2 Kernel Version: 4.18.0-1013-azure #13-Ubuntu SMP Thu Feb 28 22:54:16 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux I initiated a series of tests which rebooted Azure Cloud instances 50 times. During the 49th Reboot, an Instance failed to return from a reboot.. Upon grabbing the console output the following was seen scrolling endlessly. I have seen this failure in cases where the instance only restarted a handful of times >5 [84.247704]hyperv_fb: unable to send packet via vmbus [84.247704]hyperv_fb: unable to send packet via vmbus [84.247704]hyperv_fb: unable to send packet via vmbus [84.247704]hyperv_fb: unable to send packet via vmbus [84.247704]hyperv_fb: unable to send packet via vmbus [84.247704]hyperv_fb: unable to send packet via vmbus [84.247704]hyperv_fb: unable to send packet via vmbus [84.247704]hyperv_fb: unable to send packet via vmbus In another test attempt I saw the following failure: ERROR ExtHandler /proc/net/route contains no routes ERROR ExtHandler /proc/net/route contains no routes ERROR ExtHandler /proc/net/route contains no routes ERROR ExtHandler /proc/net/route contains no routes ERROR ExtHandler /proc/net/route contains no routes ERROR ExtHandler /proc/net/route contains no routes ERROR ExtHandler /proc/net/route contains no routes Both of these failures broke networking, Both of these failures were seen at least twice to three times, thus may explain why in some cases we never recover from an instance reboot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1822133/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1830941] Re: linux: 4.4.0-150.176 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1829205 (trusty/linux-aws), bug 1830947 (trusty/linux-lts-xenial) derivatives: bug 1829193 (linux-aws), bug 1829195 (linux-kvm), bug 1829198 (linux-raspi2), bug 1829201 (linux-snapdragon), bug 1829203 (linux-fips) -- swm properties -- phase: Holding before Promote to Proposed phase-changed: Wednesday, 29. May 2019 19:32 UTC reason: - promote-to-proposed: Pending -- builds not complete in ppa main:building,meta:building + promote-to-proposed: Pending -- builds not complete in ppa meta:building,main:building -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1830941 Title: linux: 4.4.0-150.176 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-certification-testing series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1829205 (trusty/linux-aws), bug 1830947 (trusty/linux-lts-xenial) derivatives: bug 1829193 (linux-aws), bug 1829195 (linux-kvm), bug 1829198 (linux-raspi2), bug 1829201 (linux-snapdragon), bug 1829203 (linux-fips) -- swm properties -- phase: Holding before Promote to Proposed phase-changed: Wednesday, 29. May 2019 19:32 UTC reason: promote-to-proposed: Pending -- builds not complete in ppa meta:building,main:building To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1830941/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822133] Re: Azure Instance never recovered during series of instance reboots.
Test Parameters for comment #4 Series: Disco Regions: westus2 & westus Instance: Basic_A3 Kernel: 5.0.0-1007.7 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1822133 Title: Azure Instance never recovered during series of instance reboots. Status in linux-azure package in Ubuntu: In Progress Bug description: Description: During SRU Testing of various Azure Instances, there will be some cases where the instance will not respond following a system reboot. SRU Testing only restarts a giving instance once, after it preps all of the necessary files to-be-tested. Series: Disco Instance Size: Basic_A3 Region: (Default) US-WEST-2 Kernel Version: 4.18.0-1013-azure #13-Ubuntu SMP Thu Feb 28 22:54:16 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux I initiated a series of tests which rebooted Azure Cloud instances 50 times. During the 49th Reboot, an Instance failed to return from a reboot.. Upon grabbing the console output the following was seen scrolling endlessly. I have seen this failure in cases where the instance only restarted a handful of times >5 [84.247704]hyperv_fb: unable to send packet via vmbus [84.247704]hyperv_fb: unable to send packet via vmbus [84.247704]hyperv_fb: unable to send packet via vmbus [84.247704]hyperv_fb: unable to send packet via vmbus [84.247704]hyperv_fb: unable to send packet via vmbus [84.247704]hyperv_fb: unable to send packet via vmbus [84.247704]hyperv_fb: unable to send packet via vmbus [84.247704]hyperv_fb: unable to send packet via vmbus In another test attempt I saw the following failure: ERROR ExtHandler /proc/net/route contains no routes ERROR ExtHandler /proc/net/route contains no routes ERROR ExtHandler /proc/net/route contains no routes ERROR ExtHandler /proc/net/route contains no routes ERROR ExtHandler /proc/net/route contains no routes ERROR ExtHandler /proc/net/route contains no routes ERROR ExtHandler /proc/net/route contains no routes Both of these failures broke networking, Both of these failures were seen at least twice to three times, thus may explain why in some cases we never recover from an instance reboot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1822133/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822133] Re: Azure Instance never recovered during series of instance reboots.
I revisited this particular problem today. I ran a series of restart tests across westus2 and westus, utilizing the same instance and series, but with the latest kernel in -proposed. I was unable to reproduce this problem as originally reported in the bug. I also have not seen any of our SRU testing stall due to problems of this nature, where the instance fails to respond after a restart. I think it's safe to say we can close this bug and mark it resolved for the time being. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1822133 Title: Azure Instance never recovered during series of instance reboots. Status in linux-azure package in Ubuntu: In Progress Bug description: Description: During SRU Testing of various Azure Instances, there will be some cases where the instance will not respond following a system reboot. SRU Testing only restarts a giving instance once, after it preps all of the necessary files to-be-tested. Series: Disco Instance Size: Basic_A3 Region: (Default) US-WEST-2 Kernel Version: 4.18.0-1013-azure #13-Ubuntu SMP Thu Feb 28 22:54:16 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux I initiated a series of tests which rebooted Azure Cloud instances 50 times. During the 49th Reboot, an Instance failed to return from a reboot.. Upon grabbing the console output the following was seen scrolling endlessly. I have seen this failure in cases where the instance only restarted a handful of times >5 [84.247704]hyperv_fb: unable to send packet via vmbus [84.247704]hyperv_fb: unable to send packet via vmbus [84.247704]hyperv_fb: unable to send packet via vmbus [84.247704]hyperv_fb: unable to send packet via vmbus [84.247704]hyperv_fb: unable to send packet via vmbus [84.247704]hyperv_fb: unable to send packet via vmbus [84.247704]hyperv_fb: unable to send packet via vmbus [84.247704]hyperv_fb: unable to send packet via vmbus In another test attempt I saw the following failure: ERROR ExtHandler /proc/net/route contains no routes ERROR ExtHandler /proc/net/route contains no routes ERROR ExtHandler /proc/net/route contains no routes ERROR ExtHandler /proc/net/route contains no routes ERROR ExtHandler /proc/net/route contains no routes ERROR ExtHandler /proc/net/route contains no routes ERROR ExtHandler /proc/net/route contains no routes Both of these failures broke networking, Both of these failures were seen at least twice to three times, thus may explain why in some cases we never recover from an instance reboot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1822133/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1830941] Re: linux: 4.4.0-150.176 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1829205 (trusty/linux-aws), bug 1830947 (trusty/linux-lts-xenial) derivatives: bug 1829193 (linux-aws), bug 1829195 (linux-kvm), bug 1829198 (linux-raspi2), bug 1829201 (linux-snapdragon), bug 1829203 (linux-fips) -- swm properties -- phase: Holding before Promote to Proposed phase-changed: Wednesday, 29. May 2019 19:32 UTC reason: - promote-to-proposed: Pending -- builds not complete in ppa meta:building,main:building + promote-to-proposed: Pending -- builds not complete in ppa main:building,meta:building -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1830941 Title: linux: 4.4.0-150.176 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-certification-testing series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1829205 (trusty/linux-aws), bug 1830947 (trusty/linux-lts-xenial) derivatives: bug 1829193 (linux-aws), bug 1829195 (linux-kvm), bug 1829198 (linux-raspi2), bug 1829201 (linux-snapdragon), bug 1829203 (linux-fips) -- swm properties -- phase: Holding before Promote to Proposed phase-changed: Wednesday, 29. May 2019 19:32 UTC reason: promote-to-proposed: Pending -- builds not complete in ppa main:building,meta:building To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1830941/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1830984] [NEW] apparmor fs does not reflect 4.4 backport of mmap perms change
Public bug reported: The upstream commit 9f834ec18defc369d73ccf9e87a2790bfa05bf46 was backported to the 4.4.x xenial kernel series to address CVE-2019-11190. However, the change introduces subtle changes to apparmor policy, including in the apparmor regression tests. A sysfs entry was added in later kernels to indicate this; 34c426acb75cc21bdf84685e106db0c1a3565057 upstream; this should be backported to the 4.4 kernels. ** Affects: linux (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1830984 Title: apparmor fs does not reflect 4.4 backport of mmap perms change Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: New Bug description: The upstream commit 9f834ec18defc369d73ccf9e87a2790bfa05bf46 was backported to the 4.4.x xenial kernel series to address CVE-2019-11190. However, the change introduces subtle changes to apparmor policy, including in the apparmor regression tests. A sysfs entry was added in later kernels to indicate this; 34c426acb75cc21bdf84685e106db0c1a3565057 upstream; this should be backported to the 4.4 kernels. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1830984/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1830941] Re: linux: 4.4.0-150.176 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1829205 (trusty/linux-aws), bug 1830947 (trusty/linux-lts-xenial) derivatives: bug 1829193 (linux-aws), bug 1829195 (linux-kvm), bug 1829198 (linux-raspi2), bug 1829201 (linux-snapdragon), bug 1829203 (linux-fips) -- swm properties -- phase: Holding before Promote to Proposed phase-changed: Wednesday, 29. May 2019 19:32 UTC reason: - promote-to-proposed: Pending -- builds not complete in ppa signed:building,main:building,meta:building + promote-to-proposed: Pending -- builds not complete in ppa meta:building,main:building -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1830941 Title: linux: 4.4.0-150.176 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-certification-testing series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1829205 (trusty/linux-aws), bug 1830947 (trusty/linux-lts-xenial) derivatives: bug 1829193 (linux-aws), bug 1829195 (linux-kvm), bug 1829198 (linux-raspi2), bug 1829201 (linux-snapdragon), bug 1829203 (linux-fips) -- swm properties -- phase: Holding before Promote to Proposed phase-changed: Wednesday, 29. May 2019 19:32 UTC reason: promote-to-proposed: Pending -- builds not complete in ppa meta:building,main:building To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1830941/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1830941] Re: linux: 4.4.0-150.176 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1829205 (trusty/linux-aws), bug 1830947 (trusty/linux-lts-xenial) derivatives: bug 1829193 (linux-aws), bug 1829195 (linux-kvm), bug 1829198 (linux-raspi2), bug 1829201 (linux-snapdragon), bug 1829203 (linux-fips) -- swm properties -- phase: Holding before Promote to Proposed phase-changed: Wednesday, 29. May 2019 19:32 UTC reason: - promote-to-proposed: Pending -- builds not complete in ppa meta:building,main:building,signed:building + promote-to-proposed: Pending -- builds not complete in ppa signed:building,main:building,meta:building -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1830941 Title: linux: 4.4.0-150.176 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-certification-testing series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1829205 (trusty/linux-aws), bug 1830947 (trusty/linux-lts-xenial) derivatives: bug 1829193 (linux-aws), bug 1829195 (linux-kvm), bug 1829198 (linux-raspi2), bug 1829201 (linux-snapdragon), bug 1829203 (linux-fips) -- swm properties -- phase: Holding before Promote to Proposed phase-changed: Wednesday, 29. May 2019 19:32 UTC reason: promote-to-proposed: Pending -- builds not complete in ppa signed:building,main:building,meta:building To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1830941/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1826868] Re: Sound device not detected after resume from hibernate
Hi Hui, I can confirm that the new kernel fixes the issue. And yes I did remove the extra parameter from the alsa-base.conf. Thanks for your efforts. Cheers, Rob -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1826868 Title: Sound device not detected after resume from hibernate Status in linux package in Ubuntu: Confirmed Bug description: When I close my laptop, it goes to sleep. When I wake it up, it switches to " headphones ". Then, if I go to " sound device ", my main speaker does not show. There's only the headphones that are here. I can't get my speakers back... I had to reboot the computer to get my device back. dmesg -w shows the following: snd_hda_codec_realtek hdaudioC0D0: out of range cmd 0:20:400: snd_hda_codec_realtek hdaudioC0D0: Unable to sync register 0x2b8000. -5 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-13-generic 5.0.0-13.14 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rob1551 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Apr 29 21:22:18 2019 InstallationDate: Installed on 2019-04-24 (4 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 05c8:022a Cheng Uei Precision Industry Co., Ltd (Foxlink) Bus 001 Device 002: ID 0bda:b00b Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Stream x360 Convertible 11-ag1XX ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=e0182eac-9bb3-45c5-b4e9-3b21715dbc95 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.0.0-13-generic N/A linux-backports-modules-5.0.0-13-generic N/A linux-firmware1.178 SourcePackage: linux StagingDrivers: r8822be UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/22/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.10 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8501 dmi.board.vendor: HP dmi.board.version: 05.21 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.10:bd05/22/2018:svnHP:pnHPStreamx360Convertible11-ag1XX:pvrType1ProductConfigId:rvnHP:rn8501:rvr05.21:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Stream x360 Convertible 11-ag1XX dmi.product.sku: 4RV86PA#ABG dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1826868/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1830941] Re: linux: 4.4.0-150.176 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1829205 (trusty/linux-aws), bug 1830947 (trusty/linux-lts-xenial) derivatives: bug 1829193 (linux-aws), bug 1829195 (linux-kvm), bug 1829198 (linux-raspi2), bug 1829201 (linux-snapdragon), bug 1829203 (linux-fips) -- swm properties -- phase: Holding before Promote to Proposed phase-changed: Wednesday, 29. May 2019 19:32 UTC reason: - promote-to-proposed: Pending -- builds not complete in ppa signed:building,main:building,meta:building + promote-to-proposed: Pending -- builds not complete in ppa meta:building,main:building,signed:building -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1830941 Title: linux: 4.4.0-150.176 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-certification-testing series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1829205 (trusty/linux-aws), bug 1830947 (trusty/linux-lts-xenial) derivatives: bug 1829193 (linux-aws), bug 1829195 (linux-kvm), bug 1829198 (linux-raspi2), bug 1829201 (linux-snapdragon), bug 1829203 (linux-fips) -- swm properties -- phase: Holding before Promote to Proposed phase-changed: Wednesday, 29. May 2019 19:32 UTC reason: promote-to-proposed: Pending -- builds not complete in ppa meta:building,main:building,signed:building To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1830941/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1830975] [NEW] Old style NVIDIA package installs configuration snippet to an unusual location
Public bug reported: The old-style NVIDIA package (used prior to Bionic) installs an X configuration snippet to: /usr/share/X11/xorg.conf.d/50-nvidia-drm-outputclass.conf/nvidia-drm- outputclass.conf The purpose of this configuration snippet is to configure DRM OutputClass-based driver matching so that the NVIDIA driver can be loaded without needing to explicitly configure it. Due to its location, however, it ends up not being read by the X server. This isn't a problem in distros before Bionic, since up until Artful, the X server was patched to add "nvidia" to the X server's own auto- detected driver list, so the OutputClass-based matching was redundant. However, if a system running Bionic or newer has an NVIDIA driver package from Artful or earlier installed, the location of this file is problematic, as the NVIDIA driver can no longer be autoconfigured from either the X server's internal driver list nor the OutputClass-based matching. Normally, a user wouldn't end up with an old-style driver package on a newer distro, but one possible scenario which could lead to this condition is if an NVIDIA driver package is installed via an external repository (for example, the NVIDIA CUDA repositories) on an Ubuntu version that uses the older packaging format, then the system is upgraded to a newer version that uses the newer packaging format. Third party repositories are disabled as part of the do-release-upgrade process, and the NVIDIA driver package does not get updated. The packages continue to function, but the placement of the nvidia-drm- outputclass.conf file prevents X from selecting the NVIDIA X driver without explicit configuration. I have confirmed that moving this file one level up, so that its parent directory is /usr/share/X11/xorg.conf.d allows the OutputClass-based matching to function as expected. ** Affects: nvidia-graphics-drivers-384 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-384 in Ubuntu. https://bugs.launchpad.net/bugs/1830975 Title: Old style NVIDIA package installs configuration snippet to an unusual location Status in nvidia-graphics-drivers-384 package in Ubuntu: New Bug description: The old-style NVIDIA package (used prior to Bionic) installs an X configuration snippet to: /usr/share/X11/xorg.conf.d/50-nvidia-drm-outputclass.conf/nvidia-drm- outputclass.conf The purpose of this configuration snippet is to configure DRM OutputClass-based driver matching so that the NVIDIA driver can be loaded without needing to explicitly configure it. Due to its location, however, it ends up not being read by the X server. This isn't a problem in distros before Bionic, since up until Artful, the X server was patched to add "nvidia" to the X server's own auto- detected driver list, so the OutputClass-based matching was redundant. However, if a system running Bionic or newer has an NVIDIA driver package from Artful or earlier installed, the location of this file is problematic, as the NVIDIA driver can no longer be autoconfigured from either the X server's internal driver list nor the OutputClass-based matching. Normally, a user wouldn't end up with an old-style driver package on a newer distro, but one possible scenario which could lead to this condition is if an NVIDIA driver package is installed via an external repository (for example, the NVIDIA CUDA repositories) on an Ubuntu version that uses the older packaging format, then the system is upgraded to a newer version that uses the newer packaging format. Third party repositories are disabled as part of the do-release- upgrade process, and the NVIDIA driver package does not get updated. The packages continue to function, but the placement of the nvidia- drm-outputclass.conf file prevents X from selecting the NVIDIA X driver without explicit configuration. I have confirmed that moving this file one level up, so that its parent directory is /usr/share/X11/xorg.conf.d allows the OutputClass- based matching to function as expected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-384/+bug/1830975/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1830941] Re: linux: 4.4.0-150.176 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1829205 (trusty/linux-aws), bug 1830947 (trusty/linux-lts-xenial) derivatives: bug 1829193 (linux-aws), bug 1829195 (linux-kvm), bug 1829198 (linux-raspi2), bug 1829201 (linux-snapdragon), bug 1829203 (linux-fips) -- swm properties -- phase: Holding before Promote to Proposed phase-changed: Wednesday, 29. May 2019 19:32 UTC reason: - promote-to-proposed: Pending -- builds not complete in ppa main:building,meta:building,signed:building + promote-to-proposed: Pending -- builds not complete in ppa signed:building,main:building,meta:building -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1830941 Title: linux: 4.4.0-150.176 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-certification-testing series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1829205 (trusty/linux-aws), bug 1830947 (trusty/linux-lts-xenial) derivatives: bug 1829193 (linux-aws), bug 1829195 (linux-kvm), bug 1829198 (linux-raspi2), bug 1829201 (linux-snapdragon), bug 1829203 (linux-fips) -- swm properties -- phase: Holding before Promote to Proposed phase-changed: Wednesday, 29. May 2019 19:32 UTC reason: promote-to-proposed: Pending -- builds not complete in ppa signed:building,main:building,meta:building To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1830941/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829620] Re: intel-microcode on ASUS makes kernel stuck during loading initramfs on bionic-updates, bionic-security
@TJ, we got a new employee these days who had a slightly different model of our laptop, and he got the purple screen hangup you're describing and the workaround of pinning the intel-microcode version fixed the issue. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1829620 Title: intel-microcode on ASUS makes kernel stuck during loading initramfs on bionic-updates, bionic-security Status in intel-microcode package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux-hwe package in Ubuntu: Confirmed Status in linux-hwe-edge package in Ubuntu: Confirmed Bug description: Description: - my system gets stuck at "Booting, Loading initramfs" (the first 2 lines of booting, after grub) - does not even show the enter cryptsetup passphrase - affected kernels: # apt list --installed |grep linux-signed WARNING: apt does not have a stable CLI interface. Use with caution in scripts. linux-signed-generic/bionic-security,bionic-updates,now 4.15.0.50.52 amd64 [installed] linux-signed-generic-hwe-18.04/bionic-security,bionic-updates,now 4.18.0.20.70 amd64 [installed] linux-signed-generic-hwe-18.04-edge/bionic-security,bionic-updates,now 5.0.0.15.71 amd64 [installed] - the setup is not new, has been working perfectly before (about 7 days since my last restart?) System: - HW: ASUS Zenbook 14 UX433FN - Ubuntu 18.04, runing latest HWE, fully updated - grub(-pc), cryptsetup (crypttab entries for custom encrypted LUKS setup), Suspected/possible cause?: - recent intel-microcode package update - recent kernel package updates Steps taken: - tried to remove "splash quiet" from grub/kernel cmd line (also tried adding nosplash, noplymouth) - completely removed nvidia drivers (apt purge *nvidia*) - completely purged and reinstalled grub (grup-pc) - completely purged and reinstalled all kernels (headers, modules, image, ..) - toggle BIOS "fastboot" (now using OFF) - toggle UEFI SecureBoot (now using ON) - remove plymouth (apt remove *plymouth* , but the workaround is working with plymouth installed) Workaround: - so far, I'm only able to boot with non-Ubuntu kernel! (linux-image-liquorix-amd64) - which needs "splash" option ON - reinstall cryptsetup & update-grub (as suggested in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829620/comments/10 ) I am not sure how to get you more debug info, as this setup has been working before, and it's a very eary boot-process bug, so I can't even access dmesg etc. EDIT: Hypothesis: Only affects ASUS with i7-8565U Whiskey Lake Intel CPU Upstream Bug Report: https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/issues/1 WORKAROUND 1: disable intel microcode updates during boot From this bug: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1759920 1/ add the boot parameter: dis_ucode_ldr to /etc/default/grub 2/ update-grub WORKAROUND 2: downgrade (and hold) intel-microcode to older version from bionic/main apt install --reinstall intel-microcode=3.20180312.0~ubuntu18.04.1 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: KDE DistroRelease: KDE neon 18.04 InstallationDate: Installed on 2012-12-23 (2337 days ago) InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1) Package: linux-hwe-edge (not installed) Tags: bionic wayland-session Uname: Linux 5.0.0-17.1-liquorix-amd64 x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm libvirtd lpadmin netdev plugdev sudo vboxusers video _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: KDE DistroRelease: KDE neon 18.04 InstallationDate: Installed on 2012-12-23 (2339 days ago) InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1) Package: linux-hwe-edge PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.0.0-15.16~18.04.1-generic 5.0.6 Tags: third-party-packages bionic wayland-session Uname: Linux 5.0.0-15-generic x86_64 UnreportableReason: Toto není oficiální KDE balík. Prosíme odstraňte všechny balíky třetích stran a zkuste to znovu. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm libvirtd lpadmin netdev plugdev sudo video _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1829620/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1830815] Re: Hi1620 driver updates from upstream 5.2 merge window
** Description changed: [Impact] Sync up the hns drivers with the 5.2 merge window. (Cut & paste from bug 1819535) Drivers for the HiSilicon Hi1620 SoC continue to be under active development, including both hardware enablement and bug fix patches. With the amount of flux involved, identifying and cherry-picking individual patches would be more error prone then re-syncing with current upstream. [Test Case] - Validated by testing on the Hi1620-based D06 systems. These changes were staged in a PPA kernel that underwent testing w/ the Ubuntu certification test suite. In addition, perftest was used to verify RDMA functionality and iperf was used to verify networking performance. - + Validated by testing on the Hi1620-based D06 systems. These changes were staged in a PPA kernel that underwent testing w/ the Ubuntu certification test suite (Ubuntu certification is targeted for 18.04.3 HWE kernel). In addition, perftest was used to verify RDMA functionality and iperf was used to verify networking performance. [Regression Risk] Changes are restricted to drivers specific to the Hi1620 SoC, and tested on the same. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1830815 Title: Hi1620 driver updates from upstream 5.2 merge window Status in linux package in Ubuntu: In Progress Status in linux source package in Disco: In Progress Status in linux source package in Eoan: In Progress Bug description: [Impact] Sync up the hns drivers with the 5.2 merge window. (Cut & paste from bug 1819535) Drivers for the HiSilicon Hi1620 SoC continue to be under active development, including both hardware enablement and bug fix patches. With the amount of flux involved, identifying and cherry-picking individual patches would be more error prone then re-syncing with current upstream. [Test Case] Validated by testing on the Hi1620-based D06 systems. These changes were staged in a PPA kernel that underwent testing w/ the Ubuntu certification test suite (Ubuntu certification is targeted for 18.04.3 HWE kernel). In addition, perftest was used to verify RDMA functionality and iperf was used to verify networking performance. [Regression Risk] Changes are restricted to drivers specific to the Hi1620 SoC, and tested on the same. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1830815/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1830941] Re: linux: 4.4.0-150.176 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1829205 (trusty/linux-aws), bug 1830947 (trusty/linux-lts-xenial) derivatives: bug 1829193 (linux-aws), bug 1829195 (linux-kvm), bug 1829198 (linux-raspi2), bug 1829201 (linux-snapdragon), bug 1829203 (linux-fips) -- swm properties -- phase: Holding before Promote to Proposed phase-changed: Wednesday, 29. May 2019 19:32 UTC reason: - promote-to-proposed: Pending -- builds not complete in ppa meta:building,signed:building,main:building + promote-to-proposed: Pending -- builds not complete in ppa main:building,meta:building,signed:building -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1830941 Title: linux: 4.4.0-150.176 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-certification-testing series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1829205 (trusty/linux-aws), bug 1830947 (trusty/linux-lts-xenial) derivatives: bug 1829193 (linux-aws), bug 1829195 (linux-kvm), bug 1829198 (linux-raspi2), bug 1829201 (linux-snapdragon), bug 1829203 (linux-fips) -- swm properties -- phase: Holding before Promote to Proposed phase-changed: Wednesday, 29. May 2019 19:32 UTC reason: promote-to-proposed: Pending -- builds not complete in ppa main:building,meta:building,signed:building To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1830941/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1830941] Re: linux: 4.4.0-150.176 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1829205 (trusty/linux-aws), bug 1830947 (trusty/linux-lts-xenial) derivatives: bug 1829193 (linux-aws), bug 1829195 (linux-kvm), bug 1829198 (linux-raspi2), bug 1829201 (linux-snapdragon), bug 1829203 (linux-fips) -- swm properties -- phase: Holding before Promote to Proposed phase-changed: Wednesday, 29. May 2019 19:32 UTC reason: - promote-to-proposed: Pending -- builds not complete in ppa meta:building,main:building,signed:building + promote-to-proposed: Pending -- builds not complete in ppa meta:building,signed:building,main:building -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1830941 Title: linux: 4.4.0-150.176 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-certification-testing series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1829205 (trusty/linux-aws), bug 1830947 (trusty/linux-lts-xenial) derivatives: bug 1829193 (linux-aws), bug 1829195 (linux-kvm), bug 1829198 (linux-raspi2), bug 1829201 (linux-snapdragon), bug 1829203 (linux-fips) -- swm properties -- phase: Holding before Promote to Proposed phase-changed: Wednesday, 29. May 2019 19:32 UTC reason: promote-to-proposed: Pending -- builds not complete in ppa meta:building,signed:building,main:building To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1830941/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1830815] Re: Hi1620 driver updates from upstream 5.2 merge window
** Description changed: [Impact] - TBD + Sync up the hns drivers with the 5.2 merge window. + + (Cut & paste from bug 1819535) + Drivers for the HiSilicon Hi1620 SoC continue to be under active development, including both hardware enablement and bug fix patches. With the amount of flux involved, identifying and cherry-picking individual patches would be more error prone then re-syncing with current upstream. [Test Case] - TBD + Validated by testing on the Hi1620-based D06 systems. These changes were staged in a PPA kernel that underwent testing w/ the Ubuntu certification test suite. In addition, perftest was used to verify RDMA functionality and iperf was used to verify networking performance. - [Fix] - TBD [Regression Risk] - TBD + Changes are restricted to drivers specific to the Hi1620 SoC, and tested on the same. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1830815 Title: Hi1620 driver updates from upstream 5.2 merge window Status in linux package in Ubuntu: In Progress Status in linux source package in Disco: In Progress Status in linux source package in Eoan: In Progress Bug description: [Impact] Sync up the hns drivers with the 5.2 merge window. (Cut & paste from bug 1819535) Drivers for the HiSilicon Hi1620 SoC continue to be under active development, including both hardware enablement and bug fix patches. With the amount of flux involved, identifying and cherry-picking individual patches would be more error prone then re-syncing with current upstream. [Test Case] Validated by testing on the Hi1620-based D06 systems. These changes were staged in a PPA kernel that underwent testing w/ the Ubuntu certification test suite. In addition, perftest was used to verify RDMA functionality and iperf was used to verify networking performance. [Regression Risk] Changes are restricted to drivers specific to the Hi1620 SoC, and tested on the same. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1830815/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1830941] Re: linux: 4.4.0-150.176 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1829205 (trusty/linux-aws), bug 1830947 (trusty/linux-lts-xenial) derivatives: bug 1829193 (linux-aws), bug 1829195 (linux-kvm), bug 1829198 (linux-raspi2), bug 1829201 (linux-snapdragon), bug 1829203 (linux-fips) -- swm properties -- phase: Holding before Promote to Proposed phase-changed: Wednesday, 29. May 2019 19:32 UTC reason: - promote-to-proposed: Pending -- builds not complete in ppa signed:building,main:building,meta:building + promote-to-proposed: Pending -- builds not complete in ppa meta:building,main:building,signed:building -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1830941 Title: linux: 4.4.0-150.176 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-certification-testing series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1829205 (trusty/linux-aws), bug 1830947 (trusty/linux-lts-xenial) derivatives: bug 1829193 (linux-aws), bug 1829195 (linux-kvm), bug 1829198 (linux-raspi2), bug 1829201 (linux-snapdragon), bug 1829203 (linux-fips) -- swm properties -- phase: Holding before Promote to Proposed phase-changed: Wednesday, 29. May 2019 19:32 UTC reason: promote-to-proposed: Pending -- builds not complete in ppa meta:building,main:building,signed:building To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1830941/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1830941] Re: linux: 4.4.0-150.176 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-signed Status: In Progress => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1829205 (trusty/linux-aws), bug 1830947 (trusty/linux-lts-xenial) derivatives: bug 1829193 (linux-aws), bug 1829195 (linux-kvm), bug 1829198 (linux-raspi2), bug 1829201 (linux-snapdragon), bug 1829203 (linux-fips) -- swm properties -- - phase: Packaging - phase-changed: Wednesday, 29. May 2019 18:31 UTC + phase: Holding before Promote to Proposed + phase-changed: Wednesday, 29. May 2019 19:32 UTC reason: - prepare-package: Pending -- package not yet uploaded - prepare-package-meta: Pending -- package not yet uploaded - prepare-package-signed: Pending -- package not yet uploaded + promote-to-proposed: Pending -- builds not complete in ppa signed:building,main:building,meta:building -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1830941 Title: linux: 4.4.0-150.176 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-certification-testing series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1829205 (trusty/linux-aws), bug 1830947 (trusty/linux-lts-xenial) derivatives: bug 1829193 (linux-aws), bug 1829195 (linux-kvm), bug 1829198 (linux-raspi2), bug 1829201 (linux-snapdragon), bug 1829203 (linux-fips) -- swm properties -- phase: Holding before Promote to Proposed phase-changed: Wednesday, 29. May 2019 19:32 UTC reason: promote-to-proposed: Pending -- builds not complete in ppa signed:building,main:building,meta:building To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1830941/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1778932] Re: rsync can trigger system crash
Ah, this time it actually reported a bug: [Wed May 29 11:49:24 2019] perf: interrupt took too long (2544 > 2500), lowering kernel.perf_event_max_sample_rate to 78500 [Wed May 29 11:58:41 2019] mlx5_core :01:00.0 ib0: "orted" wants to know my dev_id. Should it look at dev_port instead? See Documentation/ABI/testing/sysfs-class-net for more info. [Wed May 29 11:58:41 2019] hugetlbfs: pkdgrav.mpi (21099): Using mlock ulimits for SHM_HUGETLB is deprecated [Wed May 29 12:04:45 2019] [ cut here ] [Wed May 29 12:04:45 2019] kernel BUG at /build/linux-hwe-edge-SPwCNK/linux-hwe-edge-5.0.0/mm/slub.c:305! [Wed May 29 12:04:45 2019] invalid opcode: [#1] SMP PTI [Wed May 29 12:04:45 2019] CPU: 18 PID: 0 Comm: swapper/18 Not tainted 5.0.0-15-generic #16~18.04.1-Ubuntu [Wed May 29 12:04:45 2019] Hardware name: Intel Corporation S2600TPFR/S2600TPFR, BIOS SE5C610.86B.01.01.0014.121820151719 12/18/2015 [Wed May 29 12:04:45 2019] RIP: 0010:__slab_free+0x188/0x330 [Wed May 29 12:04:45 2019] Code: 00 48 89 c7 fa 66 0f 1f 44 00 00 f0 49 0f ba 2c 24 00 72 68 4d 3b 6c 24 20 74 11 49 0f ba 34 24 00 57 9d 0f 1f 44 00 00 eb a9 <0f> 0b 49 3b 5c 24 28 75 e8 48 8b 45 88 49 89 4c 24 28 49 89 44 24 [Wed May 29 12:04:45 2019] RSP: 0018:890f9fa83cd0 EFLAGS: 00010246 [Wed May 29 12:04:45 2019] RAX: 89159e919000 RBX: 00080007 RCX: 89159e919000 [Wed May 29 12:04:45 2019] RDX: 89159e919000 RSI: c5e9b97a4600 RDI: 890f9f406b80 [Wed May 29 12:04:45 2019] RBP: 890f9fa83d70 R08: 0001 R09: 96898b4e [Wed May 29 12:04:45 2019] R10: 0001 R11: 890f8ef3e9b0 R12: c5e9b97a4600 [Wed May 29 12:04:45 2019] R13: 89159e919000 R14: 890f9f406b80 R15: 89159e919000 [Wed May 29 12:04:45 2019] FS: () GS:890f9fa8() knlGS: [Wed May 29 12:04:45 2019] CS: 0010 DS: ES: CR0: 80050033 [Wed May 29 12:04:45 2019] CR2: 7fad281ca670 CR3: 000d0120e006 CR4: 001606e0 [Wed May 29 12:04:45 2019] Call Trace: [Wed May 29 12:04:45 2019] [Wed May 29 12:04:45 2019] ? sched_clock_cpu+0x11/0xb0 [Wed May 29 12:04:45 2019] ? sched_clock_idle_sleep_event+0x10/0x20 [Wed May 29 12:04:45 2019] ? tick_nohz_irq_exit+0x31/0x40 [Wed May 29 12:04:45 2019] ? irq_exit+0xbe/0xd0 [Wed May 29 12:04:45 2019] ? skb_free_head+0x1e/0x30 [Wed May 29 12:04:45 2019] kfree+0x169/0x180 [Wed May 29 12:04:45 2019] ? kfree+0x169/0x180 [Wed May 29 12:04:45 2019] skb_free_head+0x1e/0x30 [Wed May 29 12:04:45 2019] skb_release_data+0x111/0x170 [Wed May 29 12:04:45 2019] skb_release_all+0x24/0x30 [Wed May 29 12:04:45 2019] consume_skb+0x2c/0x90 [Wed May 29 12:04:45 2019] __dev_kfree_skb_any+0x2f/0x40 [Wed May 29 12:04:45 2019] ipoib_ib_handle_tx_wc+0x75/0x1b0 [ib_ipoib] [Wed May 29 12:04:45 2019] ipoib_tx_poll+0x8f/0x100 [ib_ipoib] [Wed May 29 12:04:45 2019] net_rx_action+0x140/0x3a0 [Wed May 29 12:04:45 2019] __do_softirq+0xe4/0x2f3 [Wed May 29 12:04:45 2019] irq_exit+0xc5/0xd0 [Wed May 29 12:04:45 2019] do_IRQ+0x8a/0xe0 [Wed May 29 12:04:45 2019] common_interrupt+0xf/0xf [Wed May 29 12:04:45 2019] [Wed May 29 12:04:45 2019] RIP: 0010:cpuidle_enter_state+0xbc/0x440 [Wed May 29 12:04:45 2019] Code: ff e8 88 56 87 ff 80 7d d3 00 74 17 9c 58 0f 1f 44 00 00 f6 c4 02 0f 85 54 03 00 00 31 ff e8 bb 8f 8d ff fb 66 0f 1f 44 00 00 <45> 85 f6 0f 88 1a 03 00 00 4c 2b 6d c8 48 ba cf f7 53 e3 a5 9b c4 [Wed May 29 12:04:45 2019] RSP: 0018:9ae106483e60 EFLAGS: 0246 ORIG_RAX: ffd9 [Wed May 29 12:04:45 2019] RAX: 890f9faa2d80 RBX: 97753c80 RCX: 001f [Wed May 29 12:04:45 2019] RDX: 3be742691ce0 RSI: 35750802 RDI: [Wed May 29 12:04:45 2019] RBP: 9ae106483ea0 R08: 0002 R09: 00022640 [Wed May 29 12:04:45 2019] R10: 9ae106483e30 R11: 0002 R12: bad8ffc81100 [Wed May 29 12:04:45 2019] R13: 3be742691ce0 R14: 0004 R15: 97753e00 [Wed May 29 12:04:45 2019] cpuidle_enter+0x17/0x20 [Wed May 29 12:04:45 2019] call_cpuidle+0x23/0x40 [Wed May 29 12:04:45 2019] do_idle+0x204/0x280 [Wed May 29 12:04:45 2019] cpu_startup_entry+0x1d/0x20 [Wed May 29 12:04:45 2019] start_secondary+0x1ab/0x200 [Wed May 29 12:04:45 2019] secondary_startup_64+0xa4/0xb0 [Wed May 29 12:04:45 2019] Modules linked in: ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs auth_rpcgss nfsv4 nfs lockd grace fscache xt_tcpudp ipt_MASQUERADE iptable_nat nf_nat_ipv4 nf_nat xt_conntrack nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 ip6table_filter ip6_tables iptable_filter bpfilter intel_rapl sb_edac x86_pkg_temp_thermal intel_powerclamp coretemp kvm joydev input_leds irqbypass ioatdma mei_me ipmi_si ipmi_devintf intel_cstate mei ipmi_msghandler intel_rapl_perf lpc_ich acpi_power_meter acpi_pad mac_hid sch_fq_codel ib_iser iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi 8021q garp mrp stp llc
[Kernel-packages] [Bug 1829737] Re: Bluetooth: hci0: request failed to create LE connection: status 0x0c (Intel 9462/9560)
** Description changed: + SRU Justification + + [Impact] + The firmware blob for Intel Bluetooth 9560/9462 is versioned 20.30.0.1 is not compatible with kernel version >= 4.19 and will cause failure to pair BT 4.0 devices. + + [Fix] + 29a536a02cad linux-firmware: Update firmware file for Intel Bluetooth 9560 + + Above upstream change contains latest firmware file for Intel Bluetooth + 9560 that fixes HID pairing in recent kernel versions. + + [Test Case] + Copy ibt-17-16-1.sfi blob to /lib/firmware/intel and do a cold boot to reload firmware. One should find following message in dmesg: + + Bluetooth: hci0: Bootloader revision 0.1 build 42 week 52 2015 + + This indicates firmware reload has been activated. For further warm + boots, kernel would dump updated revision: + + Bluetooth: hci0: Firmware revision 0.1 build 184 week 15 2019 + + And perform BT 4.0 device pairing for functional tests. + + Tested blob against following kernel versions: + + * 5.0.0-1004-oem-osp1 + * 5.0.0-15-generic + * 4.18.0-20-generic + * 4.15.0-1038-oem + * 4.15.0-50-generic + + [Regression Risk] + Low. This affects only Intel JeffersonPeak Bluetooth chip series, namely 9461/9462/9560, which are the hardware variants to be fixed. + + --- + For kernel version >= 4.19, it fails to pair with BT4.0 HID devices and leave error messages in syslog: Bluetooth: hci0: request failed to create LE connection: status 0x0c Which can be detailed by btmon: < HCI Command: LE Extended Create Connection (0x08|0x0043) plen 26 #800 [hci0] 30.895622 Filter policy: White list is not used (0x00) Own address type: Public (0x00) Peer address type: Random (0x01) Peer address: DB:DD:51:2D:1C:CC (Static) Initiating PHYs: 0x01 Entry 0: LE 1M Scan interval: 60.000 msec (0x0060) Scan window: 60.000 msec (0x0060) Min connection interval: 30.00 msec (0x0018) Max connection interval: 50.00 msec (0x0028) Connection latency: 0 (0x) Supervision timeout: 420 msec (0x002a) Min connection length: 0.000 msec (0x) Max connection length: 0.000 msec (0x) > HCI Event: Command Status (0x0f) plen 4 #801 [hci0] 30.896453 LE Extended Create Connection (0x08|0x0043) ncmd 1 Status: Command Disallowed (0x0c) Indicating this is actually a firmware problem. Verified this has been fixed at least in upstream linux-firmware commit 29a536a02cadb75b84c6c0b5d7af22d34d278563, firmware release version 21.10.0.6. With that firmware blob placed under /lib/firmware/intel and a cold boot, dmesg gives updated revision and device pairing works as expected: Firmware revision 0.1 build 184 week 15 2019 ** Changed in: linux-firmware (Ubuntu Bionic) Status: In Progress => Fix Committed ** Changed in: linux-firmware (Ubuntu) Status: In Progress => Fix Released -- 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/1829737 Title: Bluetooth: hci0: request failed to create LE connection: status 0x0c (Intel 9462/9560) Status in HWE Next: New Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Bionic: Fix Committed Bug description: SRU Justification [Impact] The firmware blob for Intel Bluetooth 9560/9462 is versioned 20.30.0.1 is not compatible with kernel version >= 4.19 and will cause failure to pair BT 4.0 devices. [Fix] 29a536a02cad linux-firmware: Update firmware file for Intel Bluetooth 9560 Above upstream change contains latest firmware file for Intel Bluetooth 9560 that fixes HID pairing in recent kernel versions. [Test Case] Copy ibt-17-16-1.sfi blob to /lib/firmware/intel and do a cold boot to reload firmware. One should find following message in dmesg: Bluetooth: hci0: Bootloader revision 0.1 build 42 week 52 2015 This indicates firmware reload has been activated. For further warm boots, kernel would dump updated revision: Bluetooth: hci0: Firmware revision 0.1 build 184 week 15 2019 And perform BT 4.0 device pairing for functional tests. Tested blob against following kernel versions: * 5.0.0-1004-oem-osp1 * 5.0.0-15-generic * 4.18.0-20-generic * 4.15.0-1038-oem * 4.15.0-50-generic [Regression Risk] Low. This affects only Intel JeffersonPeak Bluetooth chip series, namely 9461/9462/9560, which are the hardware variants to be fixed. --- For kernel version >= 4.19, it fails to pair with BT4.0 HID devices and leave error messages in syslog: Bluetooth: hci0: request failed to create LE connection: status 0x0c Which can be detailed by btmon: < HCI Command: LE Extended Create Connection (0x08|0x0043) plen 26 #800 [hci0] 30.895622 Filter policy: White list is not used
[Kernel-packages] [Bug 1830941] Re: linux: 4.4.0-150.176 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1829205 (trusty/linux-aws), bug 1830947 (trusty/linux-lts-xenial) derivatives: bug 1829193 (linux-aws), bug 1829195 (linux-kvm), bug 1829198 (linux-raspi2), bug 1829201 (linux-snapdragon), bug 1829203 (linux-fips) -- swm properties -- - phase: Ready for Packaging - phase-changed: Wednesday, 29. May 2019 17:15 UTC + phase: Packaging + phase-changed: Wednesday, 29. May 2019 18:31 UTC reason: - prepare-package: Pending -- version not specified + prepare-package: Pending -- package not yet uploaded + prepare-package-meta: Pending -- package not yet uploaded + prepare-package-signed: Pending -- package not yet uploaded -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1830941 Title: linux: 4.4.0-150.176 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-certification-testing series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1829205 (trusty/linux-aws), bug 1830947 (trusty/linux-lts-xenial) derivatives: bug 1829193 (linux-aws), bug 1829195 (linux-kvm), bug 1829198 (linux-raspi2), bug 1829201 (linux-snapdragon), bug 1829203 (linux-fips) -- swm properties -- phase: Packaging phase-changed: Wednesday, 29. May 2019 18:31 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded prepare-package-signed: Pending -- package not yet uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1830941/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1830941] Re: linux: 4.4.0-150.176 -proposed tracker
** Summary changed: - linux: -proposed tracker + linux: 4.4.0-150.176 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El Mously (kmously) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El Mously (kmously) ** Changed in: kernel-sru-workflow/prepare-package-signed Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El Mously (kmously) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1830941 Title: linux: 4.4.0-150.176 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-certification-testing series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1829205 (trusty/linux-aws), bug 1830947 (trusty/linux-lts-xenial) derivatives: bug 1829193 (linux-aws), bug 1829195 (linux-kvm), bug 1829198 (linux-raspi2), bug 1829201 (linux-snapdragon), bug 1829203 (linux-fips) -- swm properties -- phase: Ready for Packaging phase-changed: Wednesday, 29. May 2019 17:15 UTC reason: prepare-package: Pending -- version not specified To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1830941/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1830930] Re: USB 3 devices are not detected on thunderbolt 3
BIOS update didn't change anything, I guess maybe it's not even a Linux problem it's an HP problem. I could install windows to test if it work there as crosscheck with hardware vs software. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1830930 Title: USB 3 devices are not detected on thunderbolt 3 Status in linux package in Ubuntu: Confirmed Bug description: I found a strange problem when trying to connect my Samsung T5 SSD. If I connect it to the Thunderbolt port on my HP EliteDesk Mini G4, with Thunderbolt at boot then the SSD is detected without issues. If I unplug it and reconnect then it's not detected. If I force the thunderbolt controller on (boltctl power -t 1) then I can see the new USB host created in lsusb but the attached device is not added. No additional events are shown in dmesg. If I connect the device using another cable then it also doesn't work I have a USB-C cable only rated to USB 2.0 speed then the device is recognized without any issues. Ubuntu 19.04, 5.0.0-15-generic 04:00.0 System peripheral: Intel Corporation JHL7540 Thunderbolt 3 NHI [Titan Ridge 2C 2018] (rev 06) 3a:00.0 USB controller: Intel Corporation JHL7540 Thunderbolt 3 USB Controller [Titan Ridge 2C 2018] (rev 06) --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: toby 1495 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-04-27 (31 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP EliteDesk 800 G4 DM 65W Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-15-generic root=UUID=86b0f677-7a3e-4ea6-9d5c-fd7c57d1f964 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 RelatedPackageVersions: linux-restricted-modules-5.0.0-15-generic N/A linux-backports-modules-5.0.0-15-generic N/A linux-firmware1.178.1 Tags: disco Uname: Linux 5.0.0-15-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-05-26 (2 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/15/2019 dmi.bios.vendor: HP dmi.bios.version: Q21 Ver. 02.06.03 dmi.board.name: 845A dmi.board.vendor: HP dmi.board.version: KBC Version 07.D2.00 dmi.chassis.asset.tag: 8CC84321CJ dmi.chassis.type: 6 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrQ21Ver.02.06.03:bd02/15/2019:svnHP:pnHPEliteDesk800G4DM65W:pvr:rvnHP:rn845A:rvrKBCVersion07.D2.00:cvnHP:ct6:cvr: dmi.product.family: 103C_53307F HP EliteDesk dmi.product.name: HP EliteDesk 800 G4 DM 65W dmi.product.sku: 5BA07US#ABA dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1830930/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1830242] Re: [linux-azure] Commits Requested in 16.04 for the Azure Kernel
https://lists.ubuntu.com/archives/kernel-team/2019-May/100967.html
https://lists.ubuntu.com/archives/kernel-team/2019-May/100968.html
https://lists.ubuntu.com/archives/kernel-team/2019-May/100969.html
https://lists.ubuntu.com/archives/kernel-team/2019-May/100970.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1830242
Title:
[linux-azure] Commits Requested in 16.04 for the Azure Kernel
Status in linux-azure package in Ubuntu:
New
Status in linux-azure source package in Xenial:
In Progress
Bug description:
The 4.15 kernel require three patches for NVMe, those patches are
required to get to the target number of IOPS.
The commits are:
7ac257b862f2c (“blk-mq: remove the request_list usage”)
f9dde187fa921 ("nvme-pci: remove cq check after submission")
1ab0cd6966fc4 ("nvme-pci: split the nvme queue lock into submission and
completion locks")
Please include these commits in the 4.15 based kernel.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1830242/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1814373] Re: storage / luks / dmsetup regressed (or got better) on ppc64le
** Changed in: systemd (Ubuntu Eoan) 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/1814373 Title: storage / luks / dmsetup regressed (or got better) on ppc64le Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Fix Committed Status in udisks2 package in Ubuntu: Invalid Status in linux source package in Bionic: New Status in systemd source package in Bionic: In Progress Status in udisks2 source package in Bionic: Invalid Status in linux source package in Cosmic: New Status in systemd source package in Cosmic: In Progress Status in udisks2 source package in Cosmic: Invalid Status in linux source package in Disco: New Status in systemd source package in Disco: In Progress Status in udisks2 source package in Disco: Invalid Status in linux source package in Eoan: Confirmed Status in systemd source package in Eoan: Fix Committed Status in udisks2 source package in Eoan: Invalid Status in systemd package in Debian: Unknown Bug description: in disco proposed with new systemd and v4.19 kernel it appears that dmsetup / cryptsetup storage either got better or worse. Devices take very long to activate, and sometimes remain in use during test clean up. This leads to udisks autopkgtest failing on ppc64le and systemd's "storage" autopkgtest is also failing. I've tried to make ppc64le test more resilient, but it's still odd that it became unstable in disco, and used to be rock solid on ppc64le. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814373/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1830930] 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/1830930 Title: USB 3 devices are not detected on thunderbolt 3 Status in linux package in Ubuntu: Confirmed Bug description: I found a strange problem when trying to connect my Samsung T5 SSD. If I connect it to the Thunderbolt port on my HP EliteDesk Mini G4, with Thunderbolt at boot then the SSD is detected without issues. If I unplug it and reconnect then it's not detected. If I force the thunderbolt controller on (boltctl power -t 1) then I can see the new USB host created in lsusb but the attached device is not added. No additional events are shown in dmesg. If I connect the device using another cable then it also doesn't work I have a USB-C cable only rated to USB 2.0 speed then the device is recognized without any issues. Ubuntu 19.04, 5.0.0-15-generic 04:00.0 System peripheral: Intel Corporation JHL7540 Thunderbolt 3 NHI [Titan Ridge 2C 2018] (rev 06) 3a:00.0 USB controller: Intel Corporation JHL7540 Thunderbolt 3 USB Controller [Titan Ridge 2C 2018] (rev 06) --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: toby 1495 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-04-27 (31 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP EliteDesk 800 G4 DM 65W Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-15-generic root=UUID=86b0f677-7a3e-4ea6-9d5c-fd7c57d1f964 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 RelatedPackageVersions: linux-restricted-modules-5.0.0-15-generic N/A linux-backports-modules-5.0.0-15-generic N/A linux-firmware1.178.1 Tags: disco Uname: Linux 5.0.0-15-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-05-26 (2 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/15/2019 dmi.bios.vendor: HP dmi.bios.version: Q21 Ver. 02.06.03 dmi.board.name: 845A dmi.board.vendor: HP dmi.board.version: KBC Version 07.D2.00 dmi.chassis.asset.tag: 8CC84321CJ dmi.chassis.type: 6 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrQ21Ver.02.06.03:bd02/15/2019:svnHP:pnHPEliteDesk800G4DM65W:pvr:rvnHP:rn845A:rvrKBCVersion07.D2.00:cvnHP:ct6:cvr: dmi.product.family: 103C_53307F HP EliteDesk dmi.product.name: HP EliteDesk 800 G4 DM 65W dmi.product.sku: 5BA07US#ABA dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1830930/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1818134] Re: modprobe: ERROR: could not insert 'wl': Package not installed ubuntu14.04.5LTS kernel 3.13.0-165-generic
Just want to add that this exact same issue affects Veeam Agent for Linux when dkms builds the veeamsnap module, and @Lurchman's solution works to solve it. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1818134 Title: modprobe: ERROR: could not insert 'wl': Package not installed ubuntu14.04.5LTS kernel 3.13.0-165-generic Status in bcmwl package in Ubuntu: Confirmed Status in linux package in Ubuntu: Incomplete Status in shim-signed package in Ubuntu: Incomplete Bug description: when installing bcmwl-kernel-source to build wl.ko package version: 6.30.223.248+bdcom-0ubuntu0.2 Expected behavior: kernel module wl.ko loads. What happened: finit_module returns ENOPKG My device is: BCM4352 [14e4:43b1] (rev 03) Happened after latest OS update, downgrading kernel to 164 did not fix, downgrading package did not work. secure boot mode is off. A few others are having this issue https://ubuntuforums.org/showthread.php?t=2413303 There is a possibility it is a modaliases problem -- 2015 chagelog states that there was a capitalization problem, but I don't know how to check this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1818134/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1830951] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1830951/+attachment/5267470/+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/1830951 Title: kernel panic: stack corrupted in efivar_ssdt_iter+0xd3/0xe8 Status in linux package in Ubuntu: Confirmed Bug description: We have a few 2010 mac pro running 1604 LTS that are just upgraded to Ubuntu 1804 LTS. While they all worked fine with the 1604 LTS and 4.4 kernel, they can no longer boot with the 4.15.0-50 kernel installed with 1804. We tried various kernel flags without luck, and installed latest 4.18.0-20 from HWE and got the same result. Unfortunately, no logs are created in /var/logs when the issue happens, and we could only boot with the old 4.4 kernel. We had to enable earlyprintk=efi to get a backtrace in a photo. The issue happens consistently, i.e. the backtrace looks always the same just happens on different cores. Attached the boot-info output and the picture taken at the end of the kernel loading. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: steventang 2047 F pulseaudio /dev/snd/controlC0: steventang 2047 F pulseaudio /dev/snd/controlC1: steventang 2047 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=a7ceb7f0-6040-4236-ad7d-35780a1dc870 InstallationDate: Installed on 2019-05-28 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Apple Inc. MacPro5,1 NonfreeKernelModules: wl Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-148-generic root=UUID=8d18bfd8-303b-4397-9216-a0e48cb6ef54 ro quiet splash ProcVersionSignature: Ubuntu 4.4.0-148.174-generic 4.4.177 RelatedPackageVersions: linux-restricted-modules-4.4.0-148-generic N/A linux-backports-modules-4.4.0-148-generic N/A linux-firmware 1.173.6 Tags: bionic Uname: Linux 4.4.0-148-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/08/17 dmi.bios.vendor: Apple Inc. dmi.bios.version: MP51.88Z.0084.B00.1708080528 dmi.board.asset.tag: 0 dmi.board.name: Mac-F221BEC8 dmi.board.vendor: Apple Inc. dmi.chassis.type: 7 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F221BEC8 dmi.modalias: dmi:bvnAppleInc.:bvrMP51.88Z.0084.B00.1708080528:bd08/08/17:svnAppleInc.:pnMacPro5,1:pvr0.0:rvnAppleInc.:rnMac-F221BEC8:rvr:cvnAppleInc.:ct7:cvrMac-F221BEC8: dmi.product.name: MacPro5,1 dmi.product.version: 0.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1830951/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1830951] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1830951/+attachment/5267471/+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/1830951 Title: kernel panic: stack corrupted in efivar_ssdt_iter+0xd3/0xe8 Status in linux package in Ubuntu: Confirmed Bug description: We have a few 2010 mac pro running 1604 LTS that are just upgraded to Ubuntu 1804 LTS. While they all worked fine with the 1604 LTS and 4.4 kernel, they can no longer boot with the 4.15.0-50 kernel installed with 1804. We tried various kernel flags without luck, and installed latest 4.18.0-20 from HWE and got the same result. Unfortunately, no logs are created in /var/logs when the issue happens, and we could only boot with the old 4.4 kernel. We had to enable earlyprintk=efi to get a backtrace in a photo. The issue happens consistently, i.e. the backtrace looks always the same just happens on different cores. Attached the boot-info output and the picture taken at the end of the kernel loading. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: steventang 2047 F pulseaudio /dev/snd/controlC0: steventang 2047 F pulseaudio /dev/snd/controlC1: steventang 2047 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=a7ceb7f0-6040-4236-ad7d-35780a1dc870 InstallationDate: Installed on 2019-05-28 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Apple Inc. MacPro5,1 NonfreeKernelModules: wl Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-148-generic root=UUID=8d18bfd8-303b-4397-9216-a0e48cb6ef54 ro quiet splash ProcVersionSignature: Ubuntu 4.4.0-148.174-generic 4.4.177 RelatedPackageVersions: linux-restricted-modules-4.4.0-148-generic N/A linux-backports-modules-4.4.0-148-generic N/A linux-firmware 1.173.6 Tags: bionic Uname: Linux 4.4.0-148-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/08/17 dmi.bios.vendor: Apple Inc. dmi.bios.version: MP51.88Z.0084.B00.1708080528 dmi.board.asset.tag: 0 dmi.board.name: Mac-F221BEC8 dmi.board.vendor: Apple Inc. dmi.chassis.type: 7 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F221BEC8 dmi.modalias: dmi:bvnAppleInc.:bvrMP51.88Z.0084.B00.1708080528:bd08/08/17:svnAppleInc.:pnMacPro5,1:pvr0.0:rvnAppleInc.:rnMac-F221BEC8:rvr:cvnAppleInc.:ct7:cvrMac-F221BEC8: dmi.product.name: MacPro5,1 dmi.product.version: 0.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1830951/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1830930] Re: USB 3 devices are not detected on thunderbolt 3
I'll give it a go and move it ** Package changed: thunderbolt-tools (Ubuntu) => linux (Ubuntu) -- 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/1830930 Title: USB 3 devices are not detected on thunderbolt 3 Status in linux package in Ubuntu: New Bug description: I found a strange problem when trying to connect my Samsung T5 SSD. If I connect it to the Thunderbolt port on my HP EliteDesk Mini G4, with Thunderbolt at boot then the SSD is detected without issues. If I unplug it and reconnect then it's not detected. If I force the thunderbolt controller on (boltctl power -t 1) then I can see the new USB host created in lsusb but the attached device is not added. No additional events are shown in dmesg. If I connect the device using another cable then it also doesn't work I have a USB-C cable only rated to USB 2.0 speed then the device is recognized without any issues. Ubuntu 19.04, 5.0.0-15-generic 04:00.0 System peripheral: Intel Corporation JHL7540 Thunderbolt 3 NHI [Titan Ridge 2C 2018] (rev 06) 3a:00.0 USB controller: Intel Corporation JHL7540 Thunderbolt 3 USB Controller [Titan Ridge 2C 2018] (rev 06) --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: toby 1495 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-04-27 (31 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP EliteDesk 800 G4 DM 65W Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-15-generic root=UUID=86b0f677-7a3e-4ea6-9d5c-fd7c57d1f964 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 RelatedPackageVersions: linux-restricted-modules-5.0.0-15-generic N/A linux-backports-modules-5.0.0-15-generic N/A linux-firmware1.178.1 Tags: disco Uname: Linux 5.0.0-15-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-05-26 (2 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/15/2019 dmi.bios.vendor: HP dmi.bios.version: Q21 Ver. 02.06.03 dmi.board.name: 845A dmi.board.vendor: HP dmi.board.version: KBC Version 07.D2.00 dmi.chassis.asset.tag: 8CC84321CJ dmi.chassis.type: 6 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrQ21Ver.02.06.03:bd02/15/2019:svnHP:pnHPEliteDesk800G4DM65W:pvr:rvnHP:rn845A:rvrKBCVersion07.D2.00:cvnHP:ct6:cvr: dmi.product.family: 103C_53307F HP EliteDesk dmi.product.name: HP EliteDesk 800 G4 DM 65W dmi.product.sku: 5BA07US#ABA dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1830930/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1830951] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1830951/+attachment/5267472/+files/WifiSyslog.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1830951 Title: kernel panic: stack corrupted in efivar_ssdt_iter+0xd3/0xe8 Status in linux package in Ubuntu: Confirmed Bug description: We have a few 2010 mac pro running 1604 LTS that are just upgraded to Ubuntu 1804 LTS. While they all worked fine with the 1604 LTS and 4.4 kernel, they can no longer boot with the 4.15.0-50 kernel installed with 1804. We tried various kernel flags without luck, and installed latest 4.18.0-20 from HWE and got the same result. Unfortunately, no logs are created in /var/logs when the issue happens, and we could only boot with the old 4.4 kernel. We had to enable earlyprintk=efi to get a backtrace in a photo. The issue happens consistently, i.e. the backtrace looks always the same just happens on different cores. Attached the boot-info output and the picture taken at the end of the kernel loading. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: steventang 2047 F pulseaudio /dev/snd/controlC0: steventang 2047 F pulseaudio /dev/snd/controlC1: steventang 2047 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=a7ceb7f0-6040-4236-ad7d-35780a1dc870 InstallationDate: Installed on 2019-05-28 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Apple Inc. MacPro5,1 NonfreeKernelModules: wl Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-148-generic root=UUID=8d18bfd8-303b-4397-9216-a0e48cb6ef54 ro quiet splash ProcVersionSignature: Ubuntu 4.4.0-148.174-generic 4.4.177 RelatedPackageVersions: linux-restricted-modules-4.4.0-148-generic N/A linux-backports-modules-4.4.0-148-generic N/A linux-firmware 1.173.6 Tags: bionic Uname: Linux 4.4.0-148-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/08/17 dmi.bios.vendor: Apple Inc. dmi.bios.version: MP51.88Z.0084.B00.1708080528 dmi.board.asset.tag: 0 dmi.board.name: Mac-F221BEC8 dmi.board.vendor: Apple Inc. dmi.chassis.type: 7 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F221BEC8 dmi.modalias: dmi:bvnAppleInc.:bvrMP51.88Z.0084.B00.1708080528:bd08/08/17:svnAppleInc.:pnMacPro5,1:pvr0.0:rvnAppleInc.:rnMac-F221BEC8:rvr:cvnAppleInc.:ct7:cvrMac-F221BEC8: dmi.product.name: MacPro5,1 dmi.product.version: 0.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1830951/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1830951] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1830951/+attachment/5267468/+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/1830951 Title: kernel panic: stack corrupted in efivar_ssdt_iter+0xd3/0xe8 Status in linux package in Ubuntu: Confirmed Bug description: We have a few 2010 mac pro running 1604 LTS that are just upgraded to Ubuntu 1804 LTS. While they all worked fine with the 1604 LTS and 4.4 kernel, they can no longer boot with the 4.15.0-50 kernel installed with 1804. We tried various kernel flags without luck, and installed latest 4.18.0-20 from HWE and got the same result. Unfortunately, no logs are created in /var/logs when the issue happens, and we could only boot with the old 4.4 kernel. We had to enable earlyprintk=efi to get a backtrace in a photo. The issue happens consistently, i.e. the backtrace looks always the same just happens on different cores. Attached the boot-info output and the picture taken at the end of the kernel loading. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: steventang 2047 F pulseaudio /dev/snd/controlC0: steventang 2047 F pulseaudio /dev/snd/controlC1: steventang 2047 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=a7ceb7f0-6040-4236-ad7d-35780a1dc870 InstallationDate: Installed on 2019-05-28 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Apple Inc. MacPro5,1 NonfreeKernelModules: wl Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-148-generic root=UUID=8d18bfd8-303b-4397-9216-a0e48cb6ef54 ro quiet splash ProcVersionSignature: Ubuntu 4.4.0-148.174-generic 4.4.177 RelatedPackageVersions: linux-restricted-modules-4.4.0-148-generic N/A linux-backports-modules-4.4.0-148-generic N/A linux-firmware 1.173.6 Tags: bionic Uname: Linux 4.4.0-148-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/08/17 dmi.bios.vendor: Apple Inc. dmi.bios.version: MP51.88Z.0084.B00.1708080528 dmi.board.asset.tag: 0 dmi.board.name: Mac-F221BEC8 dmi.board.vendor: Apple Inc. dmi.chassis.type: 7 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F221BEC8 dmi.modalias: dmi:bvnAppleInc.:bvrMP51.88Z.0084.B00.1708080528:bd08/08/17:svnAppleInc.:pnMacPro5,1:pvr0.0:rvnAppleInc.:rnMac-F221BEC8:rvr:cvnAppleInc.:ct7:cvrMac-F221BEC8: dmi.product.name: MacPro5,1 dmi.product.version: 0.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1830951/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1830951] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1830951/+attachment/5267469/+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/1830951 Title: kernel panic: stack corrupted in efivar_ssdt_iter+0xd3/0xe8 Status in linux package in Ubuntu: Confirmed Bug description: We have a few 2010 mac pro running 1604 LTS that are just upgraded to Ubuntu 1804 LTS. While they all worked fine with the 1604 LTS and 4.4 kernel, they can no longer boot with the 4.15.0-50 kernel installed with 1804. We tried various kernel flags without luck, and installed latest 4.18.0-20 from HWE and got the same result. Unfortunately, no logs are created in /var/logs when the issue happens, and we could only boot with the old 4.4 kernel. We had to enable earlyprintk=efi to get a backtrace in a photo. The issue happens consistently, i.e. the backtrace looks always the same just happens on different cores. Attached the boot-info output and the picture taken at the end of the kernel loading. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: steventang 2047 F pulseaudio /dev/snd/controlC0: steventang 2047 F pulseaudio /dev/snd/controlC1: steventang 2047 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=a7ceb7f0-6040-4236-ad7d-35780a1dc870 InstallationDate: Installed on 2019-05-28 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Apple Inc. MacPro5,1 NonfreeKernelModules: wl Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-148-generic root=UUID=8d18bfd8-303b-4397-9216-a0e48cb6ef54 ro quiet splash ProcVersionSignature: Ubuntu 4.4.0-148.174-generic 4.4.177 RelatedPackageVersions: linux-restricted-modules-4.4.0-148-generic N/A linux-backports-modules-4.4.0-148-generic N/A linux-firmware 1.173.6 Tags: bionic Uname: Linux 4.4.0-148-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/08/17 dmi.bios.vendor: Apple Inc. dmi.bios.version: MP51.88Z.0084.B00.1708080528 dmi.board.asset.tag: 0 dmi.board.name: Mac-F221BEC8 dmi.board.vendor: Apple Inc. dmi.chassis.type: 7 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F221BEC8 dmi.modalias: dmi:bvnAppleInc.:bvrMP51.88Z.0084.B00.1708080528:bd08/08/17:svnAppleInc.:pnMacPro5,1:pvr0.0:rvnAppleInc.:rnMac-F221BEC8:rvr:cvnAppleInc.:ct7:cvrMac-F221BEC8: dmi.product.name: MacPro5,1 dmi.product.version: 0.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1830951/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1830951] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1830951/+attachment/5267466/+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/1830951 Title: kernel panic: stack corrupted in efivar_ssdt_iter+0xd3/0xe8 Status in linux package in Ubuntu: Confirmed Bug description: We have a few 2010 mac pro running 1604 LTS that are just upgraded to Ubuntu 1804 LTS. While they all worked fine with the 1604 LTS and 4.4 kernel, they can no longer boot with the 4.15.0-50 kernel installed with 1804. We tried various kernel flags without luck, and installed latest 4.18.0-20 from HWE and got the same result. Unfortunately, no logs are created in /var/logs when the issue happens, and we could only boot with the old 4.4 kernel. We had to enable earlyprintk=efi to get a backtrace in a photo. The issue happens consistently, i.e. the backtrace looks always the same just happens on different cores. Attached the boot-info output and the picture taken at the end of the kernel loading. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: steventang 2047 F pulseaudio /dev/snd/controlC0: steventang 2047 F pulseaudio /dev/snd/controlC1: steventang 2047 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=a7ceb7f0-6040-4236-ad7d-35780a1dc870 InstallationDate: Installed on 2019-05-28 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Apple Inc. MacPro5,1 NonfreeKernelModules: wl Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-148-generic root=UUID=8d18bfd8-303b-4397-9216-a0e48cb6ef54 ro quiet splash ProcVersionSignature: Ubuntu 4.4.0-148.174-generic 4.4.177 RelatedPackageVersions: linux-restricted-modules-4.4.0-148-generic N/A linux-backports-modules-4.4.0-148-generic N/A linux-firmware 1.173.6 Tags: bionic Uname: Linux 4.4.0-148-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/08/17 dmi.bios.vendor: Apple Inc. dmi.bios.version: MP51.88Z.0084.B00.1708080528 dmi.board.asset.tag: 0 dmi.board.name: Mac-F221BEC8 dmi.board.vendor: Apple Inc. dmi.chassis.type: 7 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F221BEC8 dmi.modalias: dmi:bvnAppleInc.:bvrMP51.88Z.0084.B00.1708080528:bd08/08/17:svnAppleInc.:pnMacPro5,1:pvr0.0:rvnAppleInc.:rnMac-F221BEC8:rvr:cvnAppleInc.:ct7:cvrMac-F221BEC8: dmi.product.name: MacPro5,1 dmi.product.version: 0.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1830951/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1830951] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1830951/+attachment/5267467/+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/1830951 Title: kernel panic: stack corrupted in efivar_ssdt_iter+0xd3/0xe8 Status in linux package in Ubuntu: Confirmed Bug description: We have a few 2010 mac pro running 1604 LTS that are just upgraded to Ubuntu 1804 LTS. While they all worked fine with the 1604 LTS and 4.4 kernel, they can no longer boot with the 4.15.0-50 kernel installed with 1804. We tried various kernel flags without luck, and installed latest 4.18.0-20 from HWE and got the same result. Unfortunately, no logs are created in /var/logs when the issue happens, and we could only boot with the old 4.4 kernel. We had to enable earlyprintk=efi to get a backtrace in a photo. The issue happens consistently, i.e. the backtrace looks always the same just happens on different cores. Attached the boot-info output and the picture taken at the end of the kernel loading. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: steventang 2047 F pulseaudio /dev/snd/controlC0: steventang 2047 F pulseaudio /dev/snd/controlC1: steventang 2047 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=a7ceb7f0-6040-4236-ad7d-35780a1dc870 InstallationDate: Installed on 2019-05-28 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Apple Inc. MacPro5,1 NonfreeKernelModules: wl Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-148-generic root=UUID=8d18bfd8-303b-4397-9216-a0e48cb6ef54 ro quiet splash ProcVersionSignature: Ubuntu 4.4.0-148.174-generic 4.4.177 RelatedPackageVersions: linux-restricted-modules-4.4.0-148-generic N/A linux-backports-modules-4.4.0-148-generic N/A linux-firmware 1.173.6 Tags: bionic Uname: Linux 4.4.0-148-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/08/17 dmi.bios.vendor: Apple Inc. dmi.bios.version: MP51.88Z.0084.B00.1708080528 dmi.board.asset.tag: 0 dmi.board.name: Mac-F221BEC8 dmi.board.vendor: Apple Inc. dmi.chassis.type: 7 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F221BEC8 dmi.modalias: dmi:bvnAppleInc.:bvrMP51.88Z.0084.B00.1708080528:bd08/08/17:svnAppleInc.:pnMacPro5,1:pvr0.0:rvnAppleInc.:rnMac-F221BEC8:rvr:cvnAppleInc.:ct7:cvrMac-F221BEC8: dmi.product.name: MacPro5,1 dmi.product.version: 0.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1830951/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1830951] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1830951/+attachment/5267465/+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/1830951 Title: kernel panic: stack corrupted in efivar_ssdt_iter+0xd3/0xe8 Status in linux package in Ubuntu: Confirmed Bug description: We have a few 2010 mac pro running 1604 LTS that are just upgraded to Ubuntu 1804 LTS. While they all worked fine with the 1604 LTS and 4.4 kernel, they can no longer boot with the 4.15.0-50 kernel installed with 1804. We tried various kernel flags without luck, and installed latest 4.18.0-20 from HWE and got the same result. Unfortunately, no logs are created in /var/logs when the issue happens, and we could only boot with the old 4.4 kernel. We had to enable earlyprintk=efi to get a backtrace in a photo. The issue happens consistently, i.e. the backtrace looks always the same just happens on different cores. Attached the boot-info output and the picture taken at the end of the kernel loading. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: steventang 2047 F pulseaudio /dev/snd/controlC0: steventang 2047 F pulseaudio /dev/snd/controlC1: steventang 2047 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=a7ceb7f0-6040-4236-ad7d-35780a1dc870 InstallationDate: Installed on 2019-05-28 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Apple Inc. MacPro5,1 NonfreeKernelModules: wl Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-148-generic root=UUID=8d18bfd8-303b-4397-9216-a0e48cb6ef54 ro quiet splash ProcVersionSignature: Ubuntu 4.4.0-148.174-generic 4.4.177 RelatedPackageVersions: linux-restricted-modules-4.4.0-148-generic N/A linux-backports-modules-4.4.0-148-generic N/A linux-firmware 1.173.6 Tags: bionic Uname: Linux 4.4.0-148-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/08/17 dmi.bios.vendor: Apple Inc. dmi.bios.version: MP51.88Z.0084.B00.1708080528 dmi.board.asset.tag: 0 dmi.board.name: Mac-F221BEC8 dmi.board.vendor: Apple Inc. dmi.chassis.type: 7 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F221BEC8 dmi.modalias: dmi:bvnAppleInc.:bvrMP51.88Z.0084.B00.1708080528:bd08/08/17:svnAppleInc.:pnMacPro5,1:pvr0.0:rvnAppleInc.:rnMac-F221BEC8:rvr:cvnAppleInc.:ct7:cvrMac-F221BEC8: dmi.product.name: MacPro5,1 dmi.product.version: 0.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1830951/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1830951] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1830951/+attachment/5267463/+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/1830951 Title: kernel panic: stack corrupted in efivar_ssdt_iter+0xd3/0xe8 Status in linux package in Ubuntu: Confirmed Bug description: We have a few 2010 mac pro running 1604 LTS that are just upgraded to Ubuntu 1804 LTS. While they all worked fine with the 1604 LTS and 4.4 kernel, they can no longer boot with the 4.15.0-50 kernel installed with 1804. We tried various kernel flags without luck, and installed latest 4.18.0-20 from HWE and got the same result. Unfortunately, no logs are created in /var/logs when the issue happens, and we could only boot with the old 4.4 kernel. We had to enable earlyprintk=efi to get a backtrace in a photo. The issue happens consistently, i.e. the backtrace looks always the same just happens on different cores. Attached the boot-info output and the picture taken at the end of the kernel loading. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: steventang 2047 F pulseaudio /dev/snd/controlC0: steventang 2047 F pulseaudio /dev/snd/controlC1: steventang 2047 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=a7ceb7f0-6040-4236-ad7d-35780a1dc870 InstallationDate: Installed on 2019-05-28 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Apple Inc. MacPro5,1 NonfreeKernelModules: wl Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-148-generic root=UUID=8d18bfd8-303b-4397-9216-a0e48cb6ef54 ro quiet splash ProcVersionSignature: Ubuntu 4.4.0-148.174-generic 4.4.177 RelatedPackageVersions: linux-restricted-modules-4.4.0-148-generic N/A linux-backports-modules-4.4.0-148-generic N/A linux-firmware 1.173.6 Tags: bionic Uname: Linux 4.4.0-148-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/08/17 dmi.bios.vendor: Apple Inc. dmi.bios.version: MP51.88Z.0084.B00.1708080528 dmi.board.asset.tag: 0 dmi.board.name: Mac-F221BEC8 dmi.board.vendor: Apple Inc. dmi.chassis.type: 7 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F221BEC8 dmi.modalias: dmi:bvnAppleInc.:bvrMP51.88Z.0084.B00.1708080528:bd08/08/17:svnAppleInc.:pnMacPro5,1:pvr0.0:rvnAppleInc.:rnMac-F221BEC8:rvr:cvnAppleInc.:ct7:cvrMac-F221BEC8: dmi.product.name: MacPro5,1 dmi.product.version: 0.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1830951/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1830951] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1830951/+attachment/5267462/+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/1830951 Title: kernel panic: stack corrupted in efivar_ssdt_iter+0xd3/0xe8 Status in linux package in Ubuntu: Confirmed Bug description: We have a few 2010 mac pro running 1604 LTS that are just upgraded to Ubuntu 1804 LTS. While they all worked fine with the 1604 LTS and 4.4 kernel, they can no longer boot with the 4.15.0-50 kernel installed with 1804. We tried various kernel flags without luck, and installed latest 4.18.0-20 from HWE and got the same result. Unfortunately, no logs are created in /var/logs when the issue happens, and we could only boot with the old 4.4 kernel. We had to enable earlyprintk=efi to get a backtrace in a photo. The issue happens consistently, i.e. the backtrace looks always the same just happens on different cores. Attached the boot-info output and the picture taken at the end of the kernel loading. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: steventang 2047 F pulseaudio /dev/snd/controlC0: steventang 2047 F pulseaudio /dev/snd/controlC1: steventang 2047 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=a7ceb7f0-6040-4236-ad7d-35780a1dc870 InstallationDate: Installed on 2019-05-28 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Apple Inc. MacPro5,1 NonfreeKernelModules: wl Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-148-generic root=UUID=8d18bfd8-303b-4397-9216-a0e48cb6ef54 ro quiet splash ProcVersionSignature: Ubuntu 4.4.0-148.174-generic 4.4.177 RelatedPackageVersions: linux-restricted-modules-4.4.0-148-generic N/A linux-backports-modules-4.4.0-148-generic N/A linux-firmware 1.173.6 Tags: bionic Uname: Linux 4.4.0-148-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/08/17 dmi.bios.vendor: Apple Inc. dmi.bios.version: MP51.88Z.0084.B00.1708080528 dmi.board.asset.tag: 0 dmi.board.name: Mac-F221BEC8 dmi.board.vendor: Apple Inc. dmi.chassis.type: 7 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F221BEC8 dmi.modalias: dmi:bvnAppleInc.:bvrMP51.88Z.0084.B00.1708080528:bd08/08/17:svnAppleInc.:pnMacPro5,1:pvr0.0:rvnAppleInc.:rnMac-F221BEC8:rvr:cvnAppleInc.:ct7:cvrMac-F221BEC8: dmi.product.name: MacPro5,1 dmi.product.version: 0.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1830951/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1830951] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1830951/+attachment/5267461/+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/1830951 Title: kernel panic: stack corrupted in efivar_ssdt_iter+0xd3/0xe8 Status in linux package in Ubuntu: Confirmed Bug description: We have a few 2010 mac pro running 1604 LTS that are just upgraded to Ubuntu 1804 LTS. While they all worked fine with the 1604 LTS and 4.4 kernel, they can no longer boot with the 4.15.0-50 kernel installed with 1804. We tried various kernel flags without luck, and installed latest 4.18.0-20 from HWE and got the same result. Unfortunately, no logs are created in /var/logs when the issue happens, and we could only boot with the old 4.4 kernel. We had to enable earlyprintk=efi to get a backtrace in a photo. The issue happens consistently, i.e. the backtrace looks always the same just happens on different cores. Attached the boot-info output and the picture taken at the end of the kernel loading. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: steventang 2047 F pulseaudio /dev/snd/controlC0: steventang 2047 F pulseaudio /dev/snd/controlC1: steventang 2047 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=a7ceb7f0-6040-4236-ad7d-35780a1dc870 InstallationDate: Installed on 2019-05-28 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Apple Inc. MacPro5,1 NonfreeKernelModules: wl Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-148-generic root=UUID=8d18bfd8-303b-4397-9216-a0e48cb6ef54 ro quiet splash ProcVersionSignature: Ubuntu 4.4.0-148.174-generic 4.4.177 RelatedPackageVersions: linux-restricted-modules-4.4.0-148-generic N/A linux-backports-modules-4.4.0-148-generic N/A linux-firmware 1.173.6 Tags: bionic Uname: Linux 4.4.0-148-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/08/17 dmi.bios.vendor: Apple Inc. dmi.bios.version: MP51.88Z.0084.B00.1708080528 dmi.board.asset.tag: 0 dmi.board.name: Mac-F221BEC8 dmi.board.vendor: Apple Inc. dmi.chassis.type: 7 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F221BEC8 dmi.modalias: dmi:bvnAppleInc.:bvrMP51.88Z.0084.B00.1708080528:bd08/08/17:svnAppleInc.:pnMacPro5,1:pvr0.0:rvnAppleInc.:rnMac-F221BEC8:rvr:cvnAppleInc.:ct7:cvrMac-F221BEC8: dmi.product.name: MacPro5,1 dmi.product.version: 0.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1830951/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1830951] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1830951/+attachment/5267464/+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/1830951 Title: kernel panic: stack corrupted in efivar_ssdt_iter+0xd3/0xe8 Status in linux package in Ubuntu: Confirmed Bug description: We have a few 2010 mac pro running 1604 LTS that are just upgraded to Ubuntu 1804 LTS. While they all worked fine with the 1604 LTS and 4.4 kernel, they can no longer boot with the 4.15.0-50 kernel installed with 1804. We tried various kernel flags without luck, and installed latest 4.18.0-20 from HWE and got the same result. Unfortunately, no logs are created in /var/logs when the issue happens, and we could only boot with the old 4.4 kernel. We had to enable earlyprintk=efi to get a backtrace in a photo. The issue happens consistently, i.e. the backtrace looks always the same just happens on different cores. Attached the boot-info output and the picture taken at the end of the kernel loading. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: steventang 2047 F pulseaudio /dev/snd/controlC0: steventang 2047 F pulseaudio /dev/snd/controlC1: steventang 2047 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=a7ceb7f0-6040-4236-ad7d-35780a1dc870 InstallationDate: Installed on 2019-05-28 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Apple Inc. MacPro5,1 NonfreeKernelModules: wl Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-148-generic root=UUID=8d18bfd8-303b-4397-9216-a0e48cb6ef54 ro quiet splash ProcVersionSignature: Ubuntu 4.4.0-148.174-generic 4.4.177 RelatedPackageVersions: linux-restricted-modules-4.4.0-148-generic N/A linux-backports-modules-4.4.0-148-generic N/A linux-firmware 1.173.6 Tags: bionic Uname: Linux 4.4.0-148-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/08/17 dmi.bios.vendor: Apple Inc. dmi.bios.version: MP51.88Z.0084.B00.1708080528 dmi.board.asset.tag: 0 dmi.board.name: Mac-F221BEC8 dmi.board.vendor: Apple Inc. dmi.chassis.type: 7 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F221BEC8 dmi.modalias: dmi:bvnAppleInc.:bvrMP51.88Z.0084.B00.1708080528:bd08/08/17:svnAppleInc.:pnMacPro5,1:pvr0.0:rvnAppleInc.:rnMac-F221BEC8:rvr:cvnAppleInc.:ct7:cvrMac-F221BEC8: dmi.product.name: MacPro5,1 dmi.product.version: 0.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1830951/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1830951] Re: kernel panic: stack corrupted in efivar_ssdt_iter+0xd3/0xe8
** Attachment added: "lspci-vvnn" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1830951/+attachment/5267456/+files/lspci-vvnn.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/1830951 Title: kernel panic: stack corrupted in efivar_ssdt_iter+0xd3/0xe8 Status in linux package in Ubuntu: Confirmed Bug description: We have a few 2010 mac pro running 1604 LTS that are just upgraded to Ubuntu 1804 LTS. While they all worked fine with the 1604 LTS and 4.4 kernel, they can no longer boot with the 4.15.0-50 kernel installed with 1804. We tried various kernel flags without luck, and installed latest 4.18.0-20 from HWE and got the same result. Unfortunately, no logs are created in /var/logs when the issue happens, and we could only boot with the old 4.4 kernel. We had to enable earlyprintk=efi to get a backtrace in a photo. The issue happens consistently, i.e. the backtrace looks always the same just happens on different cores. Attached the boot-info output and the picture taken at the end of the kernel loading. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: steventang 2047 F pulseaudio /dev/snd/controlC0: steventang 2047 F pulseaudio /dev/snd/controlC1: steventang 2047 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=a7ceb7f0-6040-4236-ad7d-35780a1dc870 InstallationDate: Installed on 2019-05-28 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Apple Inc. MacPro5,1 NonfreeKernelModules: wl Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-148-generic root=UUID=8d18bfd8-303b-4397-9216-a0e48cb6ef54 ro quiet splash ProcVersionSignature: Ubuntu 4.4.0-148.174-generic 4.4.177 RelatedPackageVersions: linux-restricted-modules-4.4.0-148-generic N/A linux-backports-modules-4.4.0-148-generic N/A linux-firmware 1.173.6 Tags: bionic Uname: Linux 4.4.0-148-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/08/17 dmi.bios.vendor: Apple Inc. dmi.bios.version: MP51.88Z.0084.B00.1708080528 dmi.board.asset.tag: 0 dmi.board.name: Mac-F221BEC8 dmi.board.vendor: Apple Inc. dmi.chassis.type: 7 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F221BEC8 dmi.modalias: dmi:bvnAppleInc.:bvrMP51.88Z.0084.B00.1708080528:bd08/08/17:svnAppleInc.:pnMacPro5,1:pvr0.0:rvnAppleInc.:rnMac-F221BEC8:rvr:cvnAppleInc.:ct7:cvrMac-F221BEC8: dmi.product.name: MacPro5,1 dmi.product.version: 0.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1830951/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1830951] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1830951/+attachment/5267460/+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/1830951 Title: kernel panic: stack corrupted in efivar_ssdt_iter+0xd3/0xe8 Status in linux package in Ubuntu: Confirmed Bug description: We have a few 2010 mac pro running 1604 LTS that are just upgraded to Ubuntu 1804 LTS. While they all worked fine with the 1604 LTS and 4.4 kernel, they can no longer boot with the 4.15.0-50 kernel installed with 1804. We tried various kernel flags without luck, and installed latest 4.18.0-20 from HWE and got the same result. Unfortunately, no logs are created in /var/logs when the issue happens, and we could only boot with the old 4.4 kernel. We had to enable earlyprintk=efi to get a backtrace in a photo. The issue happens consistently, i.e. the backtrace looks always the same just happens on different cores. Attached the boot-info output and the picture taken at the end of the kernel loading. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: steventang 2047 F pulseaudio /dev/snd/controlC0: steventang 2047 F pulseaudio /dev/snd/controlC1: steventang 2047 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=a7ceb7f0-6040-4236-ad7d-35780a1dc870 InstallationDate: Installed on 2019-05-28 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Apple Inc. MacPro5,1 NonfreeKernelModules: wl Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-148-generic root=UUID=8d18bfd8-303b-4397-9216-a0e48cb6ef54 ro quiet splash ProcVersionSignature: Ubuntu 4.4.0-148.174-generic 4.4.177 RelatedPackageVersions: linux-restricted-modules-4.4.0-148-generic N/A linux-backports-modules-4.4.0-148-generic N/A linux-firmware 1.173.6 Tags: bionic Uname: Linux 4.4.0-148-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/08/17 dmi.bios.vendor: Apple Inc. dmi.bios.version: MP51.88Z.0084.B00.1708080528 dmi.board.asset.tag: 0 dmi.board.name: Mac-F221BEC8 dmi.board.vendor: Apple Inc. dmi.chassis.type: 7 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F221BEC8 dmi.modalias: dmi:bvnAppleInc.:bvrMP51.88Z.0084.B00.1708080528:bd08/08/17:svnAppleInc.:pnMacPro5,1:pvr0.0:rvnAppleInc.:rnMac-F221BEC8:rvr:cvnAppleInc.:ct7:cvrMac-F221BEC8: dmi.product.name: MacPro5,1 dmi.product.version: 0.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1830951/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1830951] Re: kernel panic: stack corrupted in efivar_ssdt_iter+0xd3/0xe8
** Attachment added: "version captured with kernel 4.4" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1830951/+attachment/5267454/+files/version.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1830951 Title: kernel panic: stack corrupted in efivar_ssdt_iter+0xd3/0xe8 Status in linux package in Ubuntu: Confirmed Bug description: We have a few 2010 mac pro running 1604 LTS that are just upgraded to Ubuntu 1804 LTS. While they all worked fine with the 1604 LTS and 4.4 kernel, they can no longer boot with the 4.15.0-50 kernel installed with 1804. We tried various kernel flags without luck, and installed latest 4.18.0-20 from HWE and got the same result. Unfortunately, no logs are created in /var/logs when the issue happens, and we could only boot with the old 4.4 kernel. We had to enable earlyprintk=efi to get a backtrace in a photo. The issue happens consistently, i.e. the backtrace looks always the same just happens on different cores. Attached the boot-info output and the picture taken at the end of the kernel loading. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: steventang 2047 F pulseaudio /dev/snd/controlC0: steventang 2047 F pulseaudio /dev/snd/controlC1: steventang 2047 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=a7ceb7f0-6040-4236-ad7d-35780a1dc870 InstallationDate: Installed on 2019-05-28 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Apple Inc. MacPro5,1 NonfreeKernelModules: wl Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-148-generic root=UUID=8d18bfd8-303b-4397-9216-a0e48cb6ef54 ro quiet splash ProcVersionSignature: Ubuntu 4.4.0-148.174-generic 4.4.177 RelatedPackageVersions: linux-restricted-modules-4.4.0-148-generic N/A linux-backports-modules-4.4.0-148-generic N/A linux-firmware 1.173.6 Tags: bionic Uname: Linux 4.4.0-148-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/08/17 dmi.bios.vendor: Apple Inc. dmi.bios.version: MP51.88Z.0084.B00.1708080528 dmi.board.asset.tag: 0 dmi.board.name: Mac-F221BEC8 dmi.board.vendor: Apple Inc. dmi.chassis.type: 7 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F221BEC8 dmi.modalias: dmi:bvnAppleInc.:bvrMP51.88Z.0084.B00.1708080528:bd08/08/17:svnAppleInc.:pnMacPro5,1:pvr0.0:rvnAppleInc.:rnMac-F221BEC8:rvr:cvnAppleInc.:ct7:cvrMac-F221BEC8: dmi.product.name: MacPro5,1 dmi.product.version: 0.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1830951/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1830951] Re: kernel panic: stack corrupted in efivar_ssdt_iter+0xd3/0xe8
We cannot find any logs in var/log related to the failed boots, tried grepping the kernel version, journalctl --list-boots ** Attachment added: "dmesg after booted with 4.4" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1830951/+attachment/5267457/+files/dmesg.log ** Tags added: apport-collected bionic ** Description changed: We have a few 2010 mac pro running 1604 LTS that are just upgraded to Ubuntu 1804 LTS. While they all worked fine with the 1604 LTS and 4.4 kernel, they can no longer boot with the 4.15.0-50 kernel installed with 1804. We tried various kernel flags without luck, and installed latest 4.18.0-20 from HWE and got the same result. Unfortunately, no logs are created in /var/logs when the issue happens, and we could only boot with the old 4.4 kernel. We had to enable earlyprintk=efi to get a backtrace in a photo. The issue happens consistently, i.e. the backtrace looks always the same just happens on different cores. Attached the boot-info output and the picture taken at the end of the kernel loading. + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.6 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC2: steventang 2047 F pulseaudio + /dev/snd/controlC0: steventang 2047 F pulseaudio + /dev/snd/controlC1: steventang 2047 F pulseaudio + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 18.04 + HibernationDevice: RESUME=UUID=a7ceb7f0-6040-4236-ad7d-35780a1dc870 + InstallationDate: Installed on 2019-05-28 (0 days ago) + InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) + MachineType: Apple Inc. MacPro5,1 + NonfreeKernelModules: wl + Package: linux (not installed) + ProcFB: 0 radeondrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-148-generic root=UUID=8d18bfd8-303b-4397-9216-a0e48cb6ef54 ro quiet splash + ProcVersionSignature: Ubuntu 4.4.0-148.174-generic 4.4.177 + RelatedPackageVersions: + linux-restricted-modules-4.4.0-148-generic N/A + linux-backports-modules-4.4.0-148-generic N/A + linux-firmware 1.173.6 + Tags: bionic + Uname: Linux 4.4.0-148-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 08/08/17 + dmi.bios.vendor: Apple Inc. + dmi.bios.version: MP51.88Z.0084.B00.1708080528 + dmi.board.asset.tag: 0 + dmi.board.name: Mac-F221BEC8 + dmi.board.vendor: Apple Inc. + dmi.chassis.type: 7 + dmi.chassis.vendor: Apple Inc. + dmi.chassis.version: Mac-F221BEC8 + dmi.modalias: dmi:bvnAppleInc.:bvrMP51.88Z.0084.B00.1708080528:bd08/08/17:svnAppleInc.:pnMacPro5,1:pvr0.0:rvnAppleInc.:rnMac-F221BEC8:rvr:cvnAppleInc.:ct7:cvrMac-F221BEC8: + dmi.product.name: MacPro5,1 + dmi.product.version: 0.0 + dmi.sys.vendor: Apple Inc. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1830951 Title: kernel panic: stack corrupted in efivar_ssdt_iter+0xd3/0xe8 Status in linux package in Ubuntu: Confirmed Bug description: We have a few 2010 mac pro running 1604 LTS that are just upgraded to Ubuntu 1804 LTS. While they all worked fine with the 1604 LTS and 4.4 kernel, they can no longer boot with the 4.15.0-50 kernel installed with 1804. We tried various kernel flags without luck, and installed latest 4.18.0-20 from HWE and got the same result. Unfortunately, no logs are created in /var/logs when the issue happens, and we could only boot with the old 4.4 kernel. We had to enable earlyprintk=efi to get a backtrace in a photo. The issue happens consistently, i.e. the backtrace looks always the same just happens on different cores. Attached the boot-info output and the picture taken at the end of the kernel loading. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: steventang 2047 F pulseaudio /dev/snd/controlC0: steventang 2047 F pulseaudio /dev/snd/controlC1: steventang 2047 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=a7ceb7f0-6040-4236-ad7d-35780a1dc870 InstallationDate: Installed on 2019-05-28 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Apple Inc. MacPro5,1 NonfreeKernelModules: wl Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-148-generic root=UUID=8d18bfd8-303b-4397-9216-a0e48cb6ef54 ro quiet splash ProcVersionSignature: Ubuntu 4.4.0-148.174-generic 4.4.177 RelatedPackageVersions: linux-restricted-modules-4.4.0-148-generic N/A linux-backports-modules-4.4.0-148-generic N/A linux-firmware 1.173.6 Tags:
[Kernel-packages] [Bug 1830951] Re: kernel panic: stack corrupted in efivar_ssdt_iter+0xd3/0xe8
** Attachment added: "uname-a" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1830951/+attachment/5267455/+files/uname-a.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/1830951 Title: kernel panic: stack corrupted in efivar_ssdt_iter+0xd3/0xe8 Status in linux package in Ubuntu: Confirmed Bug description: We have a few 2010 mac pro running 1604 LTS that are just upgraded to Ubuntu 1804 LTS. While they all worked fine with the 1604 LTS and 4.4 kernel, they can no longer boot with the 4.15.0-50 kernel installed with 1804. We tried various kernel flags without luck, and installed latest 4.18.0-20 from HWE and got the same result. Unfortunately, no logs are created in /var/logs when the issue happens, and we could only boot with the old 4.4 kernel. We had to enable earlyprintk=efi to get a backtrace in a photo. The issue happens consistently, i.e. the backtrace looks always the same just happens on different cores. Attached the boot-info output and the picture taken at the end of the kernel loading. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: steventang 2047 F pulseaudio /dev/snd/controlC0: steventang 2047 F pulseaudio /dev/snd/controlC1: steventang 2047 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=a7ceb7f0-6040-4236-ad7d-35780a1dc870 InstallationDate: Installed on 2019-05-28 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Apple Inc. MacPro5,1 NonfreeKernelModules: wl Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-148-generic root=UUID=8d18bfd8-303b-4397-9216-a0e48cb6ef54 ro quiet splash ProcVersionSignature: Ubuntu 4.4.0-148.174-generic 4.4.177 RelatedPackageVersions: linux-restricted-modules-4.4.0-148-generic N/A linux-backports-modules-4.4.0-148-generic N/A linux-firmware 1.173.6 Tags: bionic Uname: Linux 4.4.0-148-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/08/17 dmi.bios.vendor: Apple Inc. dmi.bios.version: MP51.88Z.0084.B00.1708080528 dmi.board.asset.tag: 0 dmi.board.name: Mac-F221BEC8 dmi.board.vendor: Apple Inc. dmi.chassis.type: 7 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F221BEC8 dmi.modalias: dmi:bvnAppleInc.:bvrMP51.88Z.0084.B00.1708080528:bd08/08/17:svnAppleInc.:pnMacPro5,1:pvr0.0:rvnAppleInc.:rnMac-F221BEC8:rvr:cvnAppleInc.:ct7:cvrMac-F221BEC8: dmi.product.name: MacPro5,1 dmi.product.version: 0.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1830951/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1830951] AlsaInfo.txt
apport information ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1830951/+attachment/5267458/+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/1830951 Title: kernel panic: stack corrupted in efivar_ssdt_iter+0xd3/0xe8 Status in linux package in Ubuntu: Confirmed Bug description: We have a few 2010 mac pro running 1604 LTS that are just upgraded to Ubuntu 1804 LTS. While they all worked fine with the 1604 LTS and 4.4 kernel, they can no longer boot with the 4.15.0-50 kernel installed with 1804. We tried various kernel flags without luck, and installed latest 4.18.0-20 from HWE and got the same result. Unfortunately, no logs are created in /var/logs when the issue happens, and we could only boot with the old 4.4 kernel. We had to enable earlyprintk=efi to get a backtrace in a photo. The issue happens consistently, i.e. the backtrace looks always the same just happens on different cores. Attached the boot-info output and the picture taken at the end of the kernel loading. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: steventang 2047 F pulseaudio /dev/snd/controlC0: steventang 2047 F pulseaudio /dev/snd/controlC1: steventang 2047 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=a7ceb7f0-6040-4236-ad7d-35780a1dc870 InstallationDate: Installed on 2019-05-28 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Apple Inc. MacPro5,1 NonfreeKernelModules: wl Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-148-generic root=UUID=8d18bfd8-303b-4397-9216-a0e48cb6ef54 ro quiet splash ProcVersionSignature: Ubuntu 4.4.0-148.174-generic 4.4.177 RelatedPackageVersions: linux-restricted-modules-4.4.0-148-generic N/A linux-backports-modules-4.4.0-148-generic N/A linux-firmware 1.173.6 Tags: bionic Uname: Linux 4.4.0-148-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/08/17 dmi.bios.vendor: Apple Inc. dmi.bios.version: MP51.88Z.0084.B00.1708080528 dmi.board.asset.tag: 0 dmi.board.name: Mac-F221BEC8 dmi.board.vendor: Apple Inc. dmi.chassis.type: 7 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F221BEC8 dmi.modalias: dmi:bvnAppleInc.:bvrMP51.88Z.0084.B00.1708080528:bd08/08/17:svnAppleInc.:pnMacPro5,1:pvr0.0:rvnAppleInc.:rnMac-F221BEC8:rvr:cvnAppleInc.:ct7:cvrMac-F221BEC8: dmi.product.name: MacPro5,1 dmi.product.version: 0.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1830951/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1830951] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1830951/+attachment/5267459/+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/1830951 Title: kernel panic: stack corrupted in efivar_ssdt_iter+0xd3/0xe8 Status in linux package in Ubuntu: Confirmed Bug description: We have a few 2010 mac pro running 1604 LTS that are just upgraded to Ubuntu 1804 LTS. While they all worked fine with the 1604 LTS and 4.4 kernel, they can no longer boot with the 4.15.0-50 kernel installed with 1804. We tried various kernel flags without luck, and installed latest 4.18.0-20 from HWE and got the same result. Unfortunately, no logs are created in /var/logs when the issue happens, and we could only boot with the old 4.4 kernel. We had to enable earlyprintk=efi to get a backtrace in a photo. The issue happens consistently, i.e. the backtrace looks always the same just happens on different cores. Attached the boot-info output and the picture taken at the end of the kernel loading. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: steventang 2047 F pulseaudio /dev/snd/controlC0: steventang 2047 F pulseaudio /dev/snd/controlC1: steventang 2047 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=a7ceb7f0-6040-4236-ad7d-35780a1dc870 InstallationDate: Installed on 2019-05-28 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Apple Inc. MacPro5,1 NonfreeKernelModules: wl Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-148-generic root=UUID=8d18bfd8-303b-4397-9216-a0e48cb6ef54 ro quiet splash ProcVersionSignature: Ubuntu 4.4.0-148.174-generic 4.4.177 RelatedPackageVersions: linux-restricted-modules-4.4.0-148-generic N/A linux-backports-modules-4.4.0-148-generic N/A linux-firmware 1.173.6 Tags: bionic Uname: Linux 4.4.0-148-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/08/17 dmi.bios.vendor: Apple Inc. dmi.bios.version: MP51.88Z.0084.B00.1708080528 dmi.board.asset.tag: 0 dmi.board.name: Mac-F221BEC8 dmi.board.vendor: Apple Inc. dmi.chassis.type: 7 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F221BEC8 dmi.modalias: dmi:bvnAppleInc.:bvrMP51.88Z.0084.B00.1708080528:bd08/08/17:svnAppleInc.:pnMacPro5,1:pvr0.0:rvnAppleInc.:rnMac-F221BEC8:rvr:cvnAppleInc.:ct7:cvrMac-F221BEC8: dmi.product.name: MacPro5,1 dmi.product.version: 0.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1830951/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1830951] Re: kernel panic: stack corrupted in efivar_ssdt_iter+0xd3/0xe8
** Attachment added: "Boot-info output" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1830951/+attachment/5267453/+files/Boot-Info_20190529_1257.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/1830951 Title: kernel panic: stack corrupted in efivar_ssdt_iter+0xd3/0xe8 Status in linux package in Ubuntu: Confirmed Bug description: We have a few 2010 mac pro running 1604 LTS that are just upgraded to Ubuntu 1804 LTS. While they all worked fine with the 1604 LTS and 4.4 kernel, they can no longer boot with the 4.15.0-50 kernel installed with 1804. We tried various kernel flags without luck, and installed latest 4.18.0-20 from HWE and got the same result. Unfortunately, no logs are created in /var/logs when the issue happens, and we could only boot with the old 4.4 kernel. We had to enable earlyprintk=efi to get a backtrace in a photo. The issue happens consistently, i.e. the backtrace looks always the same just happens on different cores. Attached the boot-info output and the picture taken at the end of the kernel loading. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: steventang 2047 F pulseaudio /dev/snd/controlC0: steventang 2047 F pulseaudio /dev/snd/controlC1: steventang 2047 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=a7ceb7f0-6040-4236-ad7d-35780a1dc870 InstallationDate: Installed on 2019-05-28 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Apple Inc. MacPro5,1 NonfreeKernelModules: wl Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-148-generic root=UUID=8d18bfd8-303b-4397-9216-a0e48cb6ef54 ro quiet splash ProcVersionSignature: Ubuntu 4.4.0-148.174-generic 4.4.177 RelatedPackageVersions: linux-restricted-modules-4.4.0-148-generic N/A linux-backports-modules-4.4.0-148-generic N/A linux-firmware 1.173.6 Tags: bionic Uname: Linux 4.4.0-148-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/08/17 dmi.bios.vendor: Apple Inc. dmi.bios.version: MP51.88Z.0084.B00.1708080528 dmi.board.asset.tag: 0 dmi.board.name: Mac-F221BEC8 dmi.board.vendor: Apple Inc. dmi.chassis.type: 7 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F221BEC8 dmi.modalias: dmi:bvnAppleInc.:bvrMP51.88Z.0084.B00.1708080528:bd08/08/17:svnAppleInc.:pnMacPro5,1:pvr0.0:rvnAppleInc.:rnMac-F221BEC8:rvr:cvnAppleInc.:ct7:cvrMac-F221BEC8: dmi.product.name: MacPro5,1 dmi.product.version: 0.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1830951/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1830890] Re: glibc 2.23-0ubuntu11 ADT test failure with linux 4.4.0-149.175
** Changed in: linux (Ubuntu Xenial) 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/1830890 Title: glibc 2.23-0ubuntu11 ADT test failure with linux 4.4.0-149.175 Status in glibc package in Ubuntu: Invalid Status in linux package in Ubuntu: Invalid Status in glibc source package in Xenial: Invalid Status in linux source package in Xenial: Fix Committed Bug description: [Impact] Some glibc testcases are regressing on i386 after the following commit was applied to xenial/linux as part of upstream stable update 4.4.179: commit 379d98ddf41344273d9718556f761420f4dc80b3 Author: Alistair Strachan Date: Fri Aug 3 10:39:31 2018 -0700 x86: vdso: Use $LD instead of $CC to link which accidentally broke unwinding from userspace, because ld would strip the .eh_frame sections when linking. Test logs: i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/g/glibc/20190528_085308_d03ca@/log.gz [Fix] The following commit fixes the issue: commit cd01544a268ad8ee5b1dfe42c4393f1095f86879 Author: Alistair Strachan Date: Fri Dec 14 14:36:37 2018 -0800 x86/vdso: Pass --eh-frame-hdr to the linker It was applied to 4.4.180, but we need to apply it before otherwise xenial/linux will be released with a regression. [Test] ADT tests for glibc. [Regression Potential] Low. One line patch to Makefile which fixes a known regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1830890/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1830951] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1830951 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1830951 Title: kernel panic: stack corrupted in efivar_ssdt_iter+0xd3/0xe8 Status in linux package in Ubuntu: Confirmed Bug description: We have a few 2010 mac pro running 1604 LTS that are just upgraded to Ubuntu 1804 LTS. While they all worked fine with the 1604 LTS and 4.4 kernel, they can no longer boot with the 4.15.0-50 kernel installed with 1804. We tried various kernel flags without luck, and installed latest 4.18.0-20 from HWE and got the same result. Unfortunately, no logs are created in /var/logs when the issue happens, and we could only boot with the old 4.4 kernel. We had to enable earlyprintk=efi to get a backtrace in a photo. The issue happens consistently, i.e. the backtrace looks always the same just happens on different cores. Attached the boot-info output and the picture taken at the end of the kernel loading. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: steventang 2047 F pulseaudio /dev/snd/controlC0: steventang 2047 F pulseaudio /dev/snd/controlC1: steventang 2047 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=a7ceb7f0-6040-4236-ad7d-35780a1dc870 InstallationDate: Installed on 2019-05-28 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Apple Inc. MacPro5,1 NonfreeKernelModules: wl Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-148-generic root=UUID=8d18bfd8-303b-4397-9216-a0e48cb6ef54 ro quiet splash ProcVersionSignature: Ubuntu 4.4.0-148.174-generic 4.4.177 RelatedPackageVersions: linux-restricted-modules-4.4.0-148-generic N/A linux-backports-modules-4.4.0-148-generic N/A linux-firmware 1.173.6 Tags: bionic Uname: Linux 4.4.0-148-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/08/17 dmi.bios.vendor: Apple Inc. dmi.bios.version: MP51.88Z.0084.B00.1708080528 dmi.board.asset.tag: 0 dmi.board.name: Mac-F221BEC8 dmi.board.vendor: Apple Inc. dmi.chassis.type: 7 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F221BEC8 dmi.modalias: dmi:bvnAppleInc.:bvrMP51.88Z.0084.B00.1708080528:bd08/08/17:svnAppleInc.:pnMacPro5,1:pvr0.0:rvnAppleInc.:rnMac-F221BEC8:rvr:cvnAppleInc.:ct7:cvrMac-F221BEC8: dmi.product.name: MacPro5,1 dmi.product.version: 0.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1830951/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1830930] Re: USB 3 devices are not detected on thunderbolt 3
I guess it worth updating your BIOS to the latest version. According to the details above you have Ver. 02.06.03, while in HP site I can find Ver 02.07.00 The release notes there mention several fixes for the handling of USB-C ports. (I hope there is an easy way to do so on Linux. Hopefully it's available from fwupd :) ) https://support.hp.com/us-en/drivers/selfservice/hp-elitedesk-800-65w-g4 -desktop-mini-pc/21353734 -- 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/1830930 Title: USB 3 devices are not detected on thunderbolt 3 Status in linux package in Ubuntu: New Bug description: I found a strange problem when trying to connect my Samsung T5 SSD. If I connect it to the Thunderbolt port on my HP EliteDesk Mini G4, with Thunderbolt at boot then the SSD is detected without issues. If I unplug it and reconnect then it's not detected. If I force the thunderbolt controller on (boltctl power -t 1) then I can see the new USB host created in lsusb but the attached device is not added. No additional events are shown in dmesg. If I connect the device using another cable then it also doesn't work I have a USB-C cable only rated to USB 2.0 speed then the device is recognized without any issues. Ubuntu 19.04, 5.0.0-15-generic 04:00.0 System peripheral: Intel Corporation JHL7540 Thunderbolt 3 NHI [Titan Ridge 2C 2018] (rev 06) 3a:00.0 USB controller: Intel Corporation JHL7540 Thunderbolt 3 USB Controller [Titan Ridge 2C 2018] (rev 06) --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: toby 1495 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-04-27 (31 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP EliteDesk 800 G4 DM 65W Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-15-generic root=UUID=86b0f677-7a3e-4ea6-9d5c-fd7c57d1f964 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 RelatedPackageVersions: linux-restricted-modules-5.0.0-15-generic N/A linux-backports-modules-5.0.0-15-generic N/A linux-firmware1.178.1 Tags: disco Uname: Linux 5.0.0-15-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-05-26 (2 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/15/2019 dmi.bios.vendor: HP dmi.bios.version: Q21 Ver. 02.06.03 dmi.board.name: 845A dmi.board.vendor: HP dmi.board.version: KBC Version 07.D2.00 dmi.chassis.asset.tag: 8CC84321CJ dmi.chassis.type: 6 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrQ21Ver.02.06.03:bd02/15/2019:svnHP:pnHPEliteDesk800G4DM65W:pvr:rvnHP:rn845A:rvrKBCVersion07.D2.00:cvnHP:ct6:cvr: dmi.product.family: 103C_53307F HP EliteDesk dmi.product.name: HP EliteDesk 800 G4 DM 65W dmi.product.sku: 5BA07US#ABA dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1830930/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1830951] Re: kernel panic: stack corrupted in efivar_ssdt_iter+0xd3/0xe8
** Attachment added: "screen capture of the kernel panic backtrace" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1830951/+attachment/5267449/+files/IMG_0004.JPG ** Attachment removed: "boot-info output" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1830951/+attachment/5267448/+files/Boot-Info_20190529_1257.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/1830951 Title: kernel panic: stack corrupted in efivar_ssdt_iter+0xd3/0xe8 Status in linux package in Ubuntu: Confirmed Bug description: We have a few 2010 mac pro running 1604 LTS that are just upgraded to Ubuntu 1804 LTS. While they all worked fine with the 1604 LTS and 4.4 kernel, they can no longer boot with the 4.15.0-50 kernel installed with 1804. We tried various kernel flags without luck, and installed latest 4.18.0-20 from HWE and got the same result. Unfortunately, no logs are created in /var/logs when the issue happens, and we could only boot with the old 4.4 kernel. We had to enable earlyprintk=efi to get a backtrace in a photo. The issue happens consistently, i.e. the backtrace looks always the same just happens on different cores. Attached the boot-info output and the picture taken at the end of the kernel loading. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: steventang 2047 F pulseaudio /dev/snd/controlC0: steventang 2047 F pulseaudio /dev/snd/controlC1: steventang 2047 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=a7ceb7f0-6040-4236-ad7d-35780a1dc870 InstallationDate: Installed on 2019-05-28 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Apple Inc. MacPro5,1 NonfreeKernelModules: wl Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-148-generic root=UUID=8d18bfd8-303b-4397-9216-a0e48cb6ef54 ro quiet splash ProcVersionSignature: Ubuntu 4.4.0-148.174-generic 4.4.177 RelatedPackageVersions: linux-restricted-modules-4.4.0-148-generic N/A linux-backports-modules-4.4.0-148-generic N/A linux-firmware 1.173.6 Tags: bionic Uname: Linux 4.4.0-148-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/08/17 dmi.bios.vendor: Apple Inc. dmi.bios.version: MP51.88Z.0084.B00.1708080528 dmi.board.asset.tag: 0 dmi.board.name: Mac-F221BEC8 dmi.board.vendor: Apple Inc. dmi.chassis.type: 7 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F221BEC8 dmi.modalias: dmi:bvnAppleInc.:bvrMP51.88Z.0084.B00.1708080528:bd08/08/17:svnAppleInc.:pnMacPro5,1:pvr0.0:rvnAppleInc.:rnMac-F221BEC8:rvr:cvnAppleInc.:ct7:cvrMac-F221BEC8: dmi.product.name: MacPro5,1 dmi.product.version: 0.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1830951/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1830930] Re: USB 3 devices are not detected on thunderbolt 3
I set the BIOS to no security and still have the same effect. A USB device on thunderbolt bus should not need authorization? On windows I never saw that and also in Linux with the USB 2 cable there was no need to authorize. The Thunderbolt controller is authorized though. I'm not sure the correct place is under thunderbolt, it's seems more like a hardware detection bug? -- 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/1830930 Title: USB 3 devices are not detected on thunderbolt 3 Status in thunderbolt-tools package in Ubuntu: New Bug description: I found a strange problem when trying to connect my Samsung T5 SSD. If I connect it to the Thunderbolt port on my HP EliteDesk Mini G4, with Thunderbolt at boot then the SSD is detected without issues. If I unplug it and reconnect then it's not detected. If I force the thunderbolt controller on (boltctl power -t 1) then I can see the new USB host created in lsusb but the attached device is not added. No additional events are shown in dmesg. If I connect the device using another cable then it also doesn't work I have a USB-C cable only rated to USB 2.0 speed then the device is recognized without any issues. Ubuntu 19.04, 5.0.0-15-generic 04:00.0 System peripheral: Intel Corporation JHL7540 Thunderbolt 3 NHI [Titan Ridge 2C 2018] (rev 06) 3a:00.0 USB controller: Intel Corporation JHL7540 Thunderbolt 3 USB Controller [Titan Ridge 2C 2018] (rev 06) --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: toby 1495 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-04-27 (31 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP EliteDesk 800 G4 DM 65W Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-15-generic root=UUID=86b0f677-7a3e-4ea6-9d5c-fd7c57d1f964 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 RelatedPackageVersions: linux-restricted-modules-5.0.0-15-generic N/A linux-backports-modules-5.0.0-15-generic N/A linux-firmware1.178.1 Tags: disco Uname: Linux 5.0.0-15-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-05-26 (2 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/15/2019 dmi.bios.vendor: HP dmi.bios.version: Q21 Ver. 02.06.03 dmi.board.name: 845A dmi.board.vendor: HP dmi.board.version: KBC Version 07.D2.00 dmi.chassis.asset.tag: 8CC84321CJ dmi.chassis.type: 6 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrQ21Ver.02.06.03:bd02/15/2019:svnHP:pnHPEliteDesk800G4DM65W:pvr:rvnHP:rn845A:rvrKBCVersion07.D2.00:cvnHP:ct6:cvr: dmi.product.family: 103C_53307F HP EliteDesk dmi.product.name: HP EliteDesk 800 G4 DM 65W dmi.product.sku: 5BA07US#ABA dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbolt-tools/+bug/1830930/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1830930] Re: USB 3 devices are not detected on thunderbolt 3
From https://www.samsung.com/semiconductor/minisite/ssd/product/portable/t5/ I learn this is a USB 3.1 Gen2 device, not a Thunderbolt device, so authorization isn't relevant (and thunderbolt-tools isn't the relevant package). Still, the fact that you had to force power the controller even when a device is connected (and especially as it works when it's connected on boot) suggests there is some sort of issue between the BIOS / port controller / cable / maybe other parts in the system that take part in the HW detection. -- 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/1830930 Title: USB 3 devices are not detected on thunderbolt 3 Status in thunderbolt-tools package in Ubuntu: New Bug description: I found a strange problem when trying to connect my Samsung T5 SSD. If I connect it to the Thunderbolt port on my HP EliteDesk Mini G4, with Thunderbolt at boot then the SSD is detected without issues. If I unplug it and reconnect then it's not detected. If I force the thunderbolt controller on (boltctl power -t 1) then I can see the new USB host created in lsusb but the attached device is not added. No additional events are shown in dmesg. If I connect the device using another cable then it also doesn't work I have a USB-C cable only rated to USB 2.0 speed then the device is recognized without any issues. Ubuntu 19.04, 5.0.0-15-generic 04:00.0 System peripheral: Intel Corporation JHL7540 Thunderbolt 3 NHI [Titan Ridge 2C 2018] (rev 06) 3a:00.0 USB controller: Intel Corporation JHL7540 Thunderbolt 3 USB Controller [Titan Ridge 2C 2018] (rev 06) --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: toby 1495 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-04-27 (31 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP EliteDesk 800 G4 DM 65W Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-15-generic root=UUID=86b0f677-7a3e-4ea6-9d5c-fd7c57d1f964 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 RelatedPackageVersions: linux-restricted-modules-5.0.0-15-generic N/A linux-backports-modules-5.0.0-15-generic N/A linux-firmware1.178.1 Tags: disco Uname: Linux 5.0.0-15-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-05-26 (2 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/15/2019 dmi.bios.vendor: HP dmi.bios.version: Q21 Ver. 02.06.03 dmi.board.name: 845A dmi.board.vendor: HP dmi.board.version: KBC Version 07.D2.00 dmi.chassis.asset.tag: 8CC84321CJ dmi.chassis.type: 6 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrQ21Ver.02.06.03:bd02/15/2019:svnHP:pnHPEliteDesk800G4DM65W:pvr:rvnHP:rn845A:rvrKBCVersion07.D2.00:cvnHP:ct6:cvr: dmi.product.family: 103C_53307F HP EliteDesk dmi.product.name: HP EliteDesk 800 G4 DM 65W dmi.product.sku: 5BA07US#ABA dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbolt-tools/+bug/1830930/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1830941] Re: linux: -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: New => Confirmed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1829205 (trusty/linux-aws), bug 1830947 (trusty/linux-lts-xenial) derivatives: bug 1829193 (linux-aws), bug 1829195 (linux-kvm), bug 1829198 (linux-raspi2), bug 1829201 (linux-snapdragon), bug 1829203 (linux-fips) -- swm properties -- + phase: Ready for Packaging + phase-changed: Wednesday, 29. May 2019 17:15 UTC + reason: + prepare-package: Pending -- version not specified -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1830941 Title: linux: -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Confirmed Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow prepare-package-signed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-certification-testing series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1829205 (trusty/linux-aws), bug 1830947 (trusty/linux-lts-xenial) derivatives: bug 1829193 (linux-aws), bug 1829195 (linux-kvm), bug 1829198 (linux-raspi2), bug 1829201 (linux-snapdragon), bug 1829203 (linux-fips) -- swm properties -- phase: Ready for Packaging phase-changed: Wednesday, 29. May 2019 17:15 UTC reason: prepare-package: Pending -- version not specified To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1830941/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1830951] [NEW] kernel panic: stack corrupted in efivar_ssdt_iter+0xd3/0xe8
Public bug reported: We have a few 2010 mac pro running 1604 LTS that are just upgraded to Ubuntu 1804 LTS. While they all worked fine with the 1604 LTS and 4.4 kernel, they can no longer boot with the 4.15.0-50 kernel installed with 1804. We tried various kernel flags without luck, and installed latest 4.18.0-20 from HWE and got the same result. Unfortunately, no logs are created in /var/logs when the issue happens, and we could only boot with the old 4.4 kernel. We had to enable earlyprintk=efi to get a backtrace in a photo. The issue happens consistently, i.e. the backtrace looks always the same just happens on different cores. Attached the boot-info output and the picture taken at the end of the kernel loading. ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Attachment added: "boot-info output" https://bugs.launchpad.net/bugs/1830951/+attachment/5267448/+files/Boot-Info_20190529_1257.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/1830951 Title: kernel panic: stack corrupted in efivar_ssdt_iter+0xd3/0xe8 Status in linux package in Ubuntu: Incomplete Bug description: We have a few 2010 mac pro running 1604 LTS that are just upgraded to Ubuntu 1804 LTS. While they all worked fine with the 1604 LTS and 4.4 kernel, they can no longer boot with the 4.15.0-50 kernel installed with 1804. We tried various kernel flags without luck, and installed latest 4.18.0-20 from HWE and got the same result. Unfortunately, no logs are created in /var/logs when the issue happens, and we could only boot with the old 4.4 kernel. We had to enable earlyprintk=efi to get a backtrace in a photo. The issue happens consistently, i.e. the backtrace looks always the same just happens on different cores. Attached the boot-info output and the picture taken at the end of the kernel loading. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1830951/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1766201] Re: CTAUTO:DevOps:860.50:devops4fp1:Error occurred during LINUX Dmesg error Checking for all LINUX clients for devops4p10
ubuntu@lewis:~$ uname -a Linux lewis 4.18.0-21-generic #22-Ubuntu SMP Wed May 15 13:12:45 UTC 2019 ppc64le ppc64le ppc64le GNU/Linux ubuntu@lewis:~$ apt policy linux-image-generic linux-image-generic: Installed: 4.18.0.21.22 Candidate: 4.18.0.21.22 Version table: *** 4.18.0.21.22 500 500 http://ports.ubuntu.com/ubuntu-ports cosmic-proposed/main ppc64el Packages 100 /var/lib/dpkg/status 4.18.0.20.21 500 500 http://ports.ubuntu.com/ubuntu-ports cosmic-updates/main ppc64el Packages 500 http://ports.ubuntu.com/ubuntu-ports cosmic-security/main ppc64el Packages 4.18.0.10.11 500 500 http://ports.ubuntu.com/ubuntu-ports cosmic/main ppc64el Packages ubuntu@lewis:~$ ubuntu@lewis:~$ dmesg -xT -l emerg,alert,crit,err | grep "integrity: Unable to open file" ubuntu@lewis:~$ ** Tags removed: verification-needed-cosmic ** Tags added: verification-done-cosmic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1766201 Title: CTAUTO:DevOps:860.50:devops4fp1:Error occurred during LINUX Dmesg error Checking for all LINUX clients for devops4p10 Status in The Ubuntu-power-systems project: Fix Committed Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Committed Status in linux source package in Disco: Fix Committed Bug description: [Impact] The integrity subsystem is still reporting error messages like this at boot: integrity: Unable to open file: /etc/keys/x509_evm.der (-2) In a previous commit we have downgraded this error to warning: https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/bionic/commit/?h=master- next=58441dc86d7b066a2c02079829a96035587a7066 (this fix is applied everywhere, not only in bionic) But there's another place (security/integrity/digsig.c) that reports the same error message that should be also downgraded to warning for consistency. [Test Case] No special test case is required, errors are reported at boot if an integrity policy is enabled. [Fix] Downgrade also this error message to a warning. [Regression Potential] It is a one-liner that changes a printk() error message, regression potential is minimal. [Original bug report] == Comment: #0 - Application Cdeadmin - 2018-04-20 05:56:03 == == Comment: #1 - Application Cdeadmin - 2018-04-20 05:56:05 == State: Open by: stccdenv on 18 April 2018 06:27:28 This defect was opened automatically using defect_template with only logs. Please refer to 2nd seq for the problem description. ==Automatic entries== Full Log: http://w3.austin.ibm.com/afs/awd.austin.ibm.com/u/stccdenv/logs/devops4fp1_defect_template_20180418060138 Contact: Thirukumaran V T (thirukuma...@in.ibm.com), Tommy Adams(tnad...@us.ibm.com) Backup: Atit Patel (a...@us.ibm.com) System Name: devops4fp1 FSP IP: 9.3.136.192 (devops4fp1.aus.stglabs.ibm.com) System Firmware Level: Current Side Driver:.fips861/b0413a_1816.861 Non-Current Side Driver:.fips861/b0410a_1816.861 Lpar Access: Please refer https://pcajet.aus.stglabs.ibm.com/ for the lab password. (The Lab Test Passwords are now accessible only through the auto or manual install web apps. For example, from the manual install web app, enter your email address, check the Lab Passwords checkbox and then click on Submit.) (To access the Lpars in 10.33.x.x network, login to any LCB or HMC then ssh/telnet to 10.33.x.x lpars) --- HMC IP: 9.3.118.110 (vhmccloudtst100.aus.stglabs.ibm.com) HMC Version: "version= Version: 9 Release: 1 Service Pack: 910 HMC Build level 1803052221 ","base_version=V9R1 " --- =Logs SNAP : devops4p02: /tmp/ibmsupt/snap.pax.Z.devops4p02.180418060149 and also @ (NFS)9.41.164.242:/fspmount/hmc_dumps/snap.pax.Z.devops4p02.180418060149 /tmp/IBM.DRM.180418060149.tar.gz and also @ (NFS)9.41.164.242:/fspmount/hmc_dumps/IBM.DRM.180418060149.tar.gz.devops4p02 /tmp/htx.180418060149.tar.gz and also @ (NFS)9.41.164.242:/fspmount/hmc_dumps/htx.180418060149.tar.gz.devops4p02 devops4p03: /tmp/ibmsupt/snap.pax.Z.devops4p03.180418060149 and also @ (NFS)9.41.164.242:/fspmount/hmc_dumps/snap.pax.Z.devops4p03.180418060149 /tmp/IBM.DRM.180418060149.tar.gz and also @ (NFS)9.41.164.242:/fspmount/hmc_dumps/IBM.DRM.180418060149.tar.gz.devops4p03 /tmp/htx.180418060149.tar.gz and also @ (NFS)9.41.164.242:/fspmount/hmc_dumps/htx.180418060149.tar.gz.devops4p03 devops4p04: /tmp/ibmsupt/snap.pax.Z.devops4p04.180418060148 and also @
[Kernel-packages] [Bug 1830930] Re: USB 3 devices are not detected on thunderbolt 3
With most machines they have a security level set in BIOS. The default security level means you need to authorize the thunderbolt device using bolt or thunderbolt-tools, did you do that? -- 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/1830930 Title: USB 3 devices are not detected on thunderbolt 3 Status in thunderbolt-tools package in Ubuntu: New Bug description: I found a strange problem when trying to connect my Samsung T5 SSD. If I connect it to the Thunderbolt port on my HP EliteDesk Mini G4, with Thunderbolt at boot then the SSD is detected without issues. If I unplug it and reconnect then it's not detected. If I force the thunderbolt controller on (boltctl power -t 1) then I can see the new USB host created in lsusb but the attached device is not added. No additional events are shown in dmesg. If I connect the device using another cable then it also doesn't work I have a USB-C cable only rated to USB 2.0 speed then the device is recognized without any issues. Ubuntu 19.04, 5.0.0-15-generic 04:00.0 System peripheral: Intel Corporation JHL7540 Thunderbolt 3 NHI [Titan Ridge 2C 2018] (rev 06) 3a:00.0 USB controller: Intel Corporation JHL7540 Thunderbolt 3 USB Controller [Titan Ridge 2C 2018] (rev 06) --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: toby 1495 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-04-27 (31 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP EliteDesk 800 G4 DM 65W Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-15-generic root=UUID=86b0f677-7a3e-4ea6-9d5c-fd7c57d1f964 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 RelatedPackageVersions: linux-restricted-modules-5.0.0-15-generic N/A linux-backports-modules-5.0.0-15-generic N/A linux-firmware1.178.1 Tags: disco Uname: Linux 5.0.0-15-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-05-26 (2 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/15/2019 dmi.bios.vendor: HP dmi.bios.version: Q21 Ver. 02.06.03 dmi.board.name: 845A dmi.board.vendor: HP dmi.board.version: KBC Version 07.D2.00 dmi.chassis.asset.tag: 8CC84321CJ dmi.chassis.type: 6 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrQ21Ver.02.06.03:bd02/15/2019:svnHP:pnHPEliteDesk800G4DM65W:pvr:rvnHP:rn845A:rvrKBCVersion07.D2.00:cvnHP:ct6:cvr: dmi.product.family: 103C_53307F HP EliteDesk dmi.product.name: HP EliteDesk 800 G4 DM 65W dmi.product.sku: 5BA07US#ABA dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbolt-tools/+bug/1830930/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1830941] Re: linux: -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow - backports: bug 1829205 (trusty/linux-aws), bug 1829207 (trusty/linux-lts-xenial) + backports: bug 1829205 (trusty/linux-aws) derivatives: bug 1829193 (linux-aws), bug 1829195 (linux-kvm), bug 1829198 (linux-raspi2), bug 1829201 (linux-snapdragon), bug 1829203 (linux-fips) -- swm properties -- ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow - backports: bug 1829205 (trusty/linux-aws) + backports: bug 1829205 (trusty/linux-aws), bug 1830947 (trusty/linux-lts-xenial) derivatives: bug 1829193 (linux-aws), bug 1829195 (linux-kvm), bug 1829198 (linux-raspi2), bug 1829201 (linux-snapdragon), bug 1829203 (linux-fips) -- swm properties -- -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1830941 Title: linux: -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: New Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow prepare-package-signed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-certification-testing series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1829205 (trusty/linux-aws), bug 1830947 (trusty/linux-lts-xenial) derivatives: bug 1829193 (linux-aws), bug 1829195 (linux-kvm), bug 1829198 (linux-raspi2), bug 1829201 (linux-snapdragon), bug 1829203 (linux-fips) -- swm properties -- To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1830941/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1830890] Re: glibc 2.23-0ubuntu11 ADT test failure with linux 4.4.0-149.175
** Description changed: - Testing failed on: - i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/g/glibc/20190528_085308_d03ca@/log.gz + [Impact] + Some glibc testcases are regressing on i386 after the following commit was applied to xenial/linux as part of upstream stable update 4.4.179: + + commit 379d98ddf41344273d9718556f761420f4dc80b3 + Author: Alistair Strachan + Date: Fri Aug 3 10:39:31 2018 -0700 + + x86: vdso: Use $LD instead of $CC to link + + which accidentally broke unwinding from userspace, because ld would + strip the .eh_frame sections when linking. + + Test logs: + i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/g/glibc/20190528_085308_d03ca@/log.gz + + [Fix] + The following commit fixes the issue: + + commit cd01544a268ad8ee5b1dfe42c4393f1095f86879 + Author: Alistair Strachan + Date: Fri Dec 14 14:36:37 2018 -0800 + + x86/vdso: Pass --eh-frame-hdr to the linker + + It was applied to 4.4.180, but we need to apply it before otherwise + xenial/linux will be released with a regression. + + [Test] + ADT tests for glibc. + + [Regression Potential] + Low. One line patch to Makefile which fixes a known regression. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1830890 Title: glibc 2.23-0ubuntu11 ADT test failure with linux 4.4.0-149.175 Status in glibc package in Ubuntu: Invalid Status in linux package in Ubuntu: Invalid Status in glibc source package in Xenial: Invalid Status in linux source package in Xenial: Confirmed Bug description: [Impact] Some glibc testcases are regressing on i386 after the following commit was applied to xenial/linux as part of upstream stable update 4.4.179: commit 379d98ddf41344273d9718556f761420f4dc80b3 Author: Alistair Strachan Date: Fri Aug 3 10:39:31 2018 -0700 x86: vdso: Use $LD instead of $CC to link which accidentally broke unwinding from userspace, because ld would strip the .eh_frame sections when linking. Test logs: i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/g/glibc/20190528_085308_d03ca@/log.gz [Fix] The following commit fixes the issue: commit cd01544a268ad8ee5b1dfe42c4393f1095f86879 Author: Alistair Strachan Date: Fri Dec 14 14:36:37 2018 -0800 x86/vdso: Pass --eh-frame-hdr to the linker It was applied to 4.4.180, but we need to apply it before otherwise xenial/linux will be released with a regression. [Test] ADT tests for glibc. [Regression Potential] Low. One line patch to Makefile which fixes a known regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1830890/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1681909] Re: [FEAT 18.10] dump is not captured in remote host when kdump over ssh is configured on firestone.
** Changed in: makedumpfile (Ubuntu) Assignee: Canonical Kernel Team (canonical-kernel-team) => (unassigned) ** Changed in: ubuntu-power-systems Assignee: Canonical Kernel Team (canonical-kernel-team) => (unassigned) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1681909 Title: [FEAT 18.10] dump is not captured in remote host when kdump over ssh is configured on firestone. Status in The Ubuntu-power-systems project: Incomplete Status in makedumpfile package in Ubuntu: New Bug description: == Comment: #0 - PAVITHRA R. PRAKASH - 2017-03-07 05:00:29 == ---Problem Description--- Ubuntu 17.04: dump is not captured in remote host when kdump over ssh is configured on firestone. ---Steps to Reproduce--- 1. Configure kdump. 2. Check whether kdump is operational using ?# kdump-config show?. 3. Install ?kernel-debuginfo? and ?kernel-debuginfo-common? rpms. 4. Setup password less ssh connection, generate rsa key. # ssh-keygen -t rsa 5. verify id_rsa and id_rsa.pub are created under /root/.ssh/ 6. Edit /etc/default/kdump-tools and add below entries. SSH="ubuntu@9.114.15.239" SSH_KEY=/root/.ssh/id_rsa 7. Propagate RSA key. # kdump-config propagate 8. Restart kdump service. # kdump-config load 9. Trigger Crash using below commands. # echo "1" > /proc/sys/kernel/sysrq # echo "c" > /proc/sysrq-trigger 10. Verify dump is available in remote server in configured path. Machine details === $ ipmitool -I lanplus -H 9.47.70.3 -U ADMIN -P admin sol activate $ ssh ubuntu@9.47.70.29 PW: shriya101 Attaching logs == Comment: #1 - PAVITHRA R. PRAKASH - 2017-03-07 05:01:42 == == Comment: #5 - PAVITHRA R. PRAKASH - 2017-03-07 23:19:46 == Hi, Attaching the logs. Network info: root@ltc-firep3:~# hwinfo --network 36: None 00.0: 10700 Loopback [Created at net.126] Unique ID: ZsBS.GQNx7L4uPNA SysFS ID: /class/net/lo Hardware Class: network interface Model: "Loopback network interface" Device File: lo Link detected: yes Config Status: cfg=new, avail=yes, need=no, active=unknown 37: None 00.0: 10701 Ethernet [Created at net.126] Unique ID: 2lHw.ndpeucax6V1 Parent ID: mIXc.aXC4wIvegH8 SysFS ID: /class/net/enP33p3s0f2 SysFS Device Link: /devices/pci0021:00/0021:00:00.0/0021:01:00.0/0021:02:01.0/0021:03:00.2 Hardware Class: network interface Model: "Ethernet network interface" Driver: "tg3" Driver Modules: "tg3" Device File: enP33p3s0f2 HW Address: 98:be:94:03:18:4a Permanent HW Address: 98:be:94:03:18:4a Link detected: no Config Status: cfg=new, avail=yes, need=no, active=unknown Attached to: #15 (Ethernet controller) 38: None 00.0: 10701 Ethernet [Created at net.126] Unique ID: 7Onn.ndpeucax6V1 Parent ID: sx0U.aXC4wIvegH8 SysFS ID: /class/net/enP33p3s0f0 SysFS Device Link: /devices/pci0021:00/0021:00:00.0/0021:01:00.0/0021:02:01.0/0021:03:00.0 Hardware Class: network interface Model: "Ethernet network interface" Driver: "tg3" Driver Modules: "tg3" Device File: enP33p3s0f0 HW Address: 98:be:94:03:18:48 Permanent HW Address: 98:be:94:03:18:48 Link detected: yes Config Status: cfg=new, avail=yes, need=no, active=unknown Attached to: #16 (Ethernet controller) 39: None 00.0: 10701 Ethernet [Created at net.126] Unique ID: VwX_.ndpeucax6V1 Parent ID: DUng.aXC4wIvegH8 SysFS ID: /class/net/enP33p3s0f3 SysFS Device Link: /devices/pci0021:00/0021:00:00.0/0021:01:00.0/0021:02:01.0/0021:03:00.3 Hardware Class: network interface Model: "Ethernet network interface" Driver: "tg3" Driver Modules: "tg3" Device File: enP33p3s0f3 HW Address: 98:be:94:03:18:4b Permanent HW Address: 98:be:94:03:18:4b Link detected: no Config Status: cfg=new, avail=yes, need=no, active=unknown Attached to: #25 (Ethernet controller) 40: None 00.0: 10701 Ethernet [Created at net.126] Unique ID: bZ1s.ndpeucax6V1 Parent ID: J7HY.aXC4wIvegH8 SysFS ID: /class/net/enP33p3s0f1 SysFS Device Link: /devices/pci0021:00/0021:00:00.0/0021:01:00.0/0021:02:01.0/0021:03:00.1 Hardware Class: network interface Model: "Ethernet network interface" Driver: "tg3" Driver Modules: "tg3" Device File: enP33p3s0f1 HW Address: 98:be:94:03:18:49 Permanent HW Address: 98:be:94:03:18:49 Link detected: no Config Status: cfg=new, avail=yes, need=no, active=unknown Attached to: #4 (Ethernet controller) root@ltc-firep3:~# Thanks, Pavithra == Comment: #6 - PAVITHRA R. PRAKASH - 2017-03-07 23:20:47 == == Comment: #7 - PAVITHRA R. PRAKASH - 2017-03-07 23:21:27 == == Comment: #8 - Urvashi Jawere - 2017-03-08 02:48:15 == I am able to
[Kernel-packages] [Bug 1830934] Re: Disco update: 5.0.12 upstream stable release
All patches did apply, however one stable patch makes CONFIG_AXIS_FIFO depend on CONFIG_OF which effectively turns of build for amd64/i386. This needs updates to the abi files and in turn the start-new-release commit should be rebased to the start of the new cycle and hope git moved those modifications to the new abi. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1830934 Title: Disco update: 5.0.12 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Disco: In Progress Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: 5.0.12 upstream stable release from git://git.kernel.org/ The following patches were applied: * selinux: use kernel linux/socket.h for genheaders and mdp * Revert "ACPICA: Clear status of GPEs before enabling them" * drm/i915: Do not enable FEC without DSC * mm: make page ref count overflow check tighter and more explicit * mm: add 'try_get_page()' helper function * mm: prevent get_user_pages() from overflowing page refcount * fs: prevent page refcount overflow in pipe_buf_get * arm64: dts: renesas: r8a77990: Fix SCIF5 DMA channels * ARM: dts: bcm283x: Fix hdmi hpd gpio pull * s390: limit brk randomization to 32MB * mt76x02: fix hdr pointer in write txwi for USB * mt76: mt76x2: fix external LNA gain settings * mt76: mt76x2: fix 2.4 GHz channel gain settings * net: ieee802154: fix a potential NULL pointer dereference * ieee802154: hwsim: propagate genlmsg_reply return code * Btrfs: fix file corruption after snapshotting due to mix of buffered/DIO writes * net: stmmac: don't set own bit too early for jumbo frames * net: stmmac: fix jumbo frame sending with non-linear skbs * qlcnic: Avoid potential NULL pointer dereference * xsk: fix umem memory leak on cleanup * staging: axis-fifo: add CONFIG_OF dependency * staging, mt7621-pci: fix build without pci support * netfilter: nft_set_rbtree: check for inactive element after flag mismatch * netfilter: bridge: set skb transport_header before entering NF_INET_PRE_ROUTING * netfilter: fix NETFILTER_XT_TARGET_TEE dependencies * netfilter: ip6t_srh: fix NULL pointer dereferences * s390/qeth: fix race when initializing the IP address table * ARM: imx51: fix a leaked reference by adding missing of_node_put * sc16is7xx: missing unregister/delete driver on error in sc16is7xx_init() * serial: ar933x_uart: Fix build failure with disabled console * KVM: arm64: Reset the PMU in preemptible context * arm64: KVM: Always set ICH_HCR_EL2.EN if GICv4 is enabled * KVM: arm/arm64: vgic-its: Take the srcu lock when writing to guest memory * KVM: arm/arm64: vgic-its: Take the srcu lock when parsing the memslots * usb: dwc3: pci: add support for Comet Lake PCH ID * usb: gadget: net2280: Fix overrun of OUT messages * usb: gadget: net2280: Fix net2280_dequeue() * usb: gadget: net2272: Fix net2272_dequeue() * ARM: dts: pfla02: increase phy reset duration * i2c: i801: Add support for Intel Comet Lake * KVM: arm/arm64: Fix handling of stage2 huge mappings * net: ks8851: Dequeue RX packets explicitly * net: ks8851: Reassert reset pin if chip ID check fails * net: ks8851: Delay requesting IRQ until opened * net: ks8851: Set initial carrier state to down * staging: rtl8188eu: Fix potential NULL pointer dereference of kcalloc * staging: rtlwifi: rtl8822b: fix to avoid potential NULL pointer dereference * staging: rtl8712: uninitialized memory in read_bbreg_hdl() * staging: rtlwifi: Fix potential NULL pointer dereference of kzalloc * net: phy: Add DP83825I to the DP83822 driver * net: macb: Add null check for PCLK and HCLK * net/sched: don't dereference a->goto_chain to read the chain index * ARM: dts: imx6qdl: Fix typo in imx6qdl-icore-rqs.dtsi * drm/tegra: hub: Fix dereference before check * NFS: Fix a typo in nfs_init_timeout_values() * net: xilinx: fix possible object reference leak * net: ibm: fix possible object reference leak * net: ethernet: ti: fix possible object reference leak * drm: Fix drm_release() and device unplug * gpio: aspeed: fix a potential NULL pointer dereference * drm/meson: Fix invalid pointer in meson_drv_unbind() * drm/meson: Uninstall IRQ handler * ARM: davinci: fix build failure with allnoconfig * sbitmap: order READ/WRITE freed instance and setting clear bit * staging: vc04_services: Fix an error code in
[Kernel-packages] [Bug 1830930] Re: USB 3 devices are not detected on thunderbolt 3
** Package changed: linux (Ubuntu) => thunderbolt-tools (Ubuntu) -- 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/1830930 Title: USB 3 devices are not detected on thunderbolt 3 Status in thunderbolt-tools package in Ubuntu: New Bug description: I found a strange problem when trying to connect my Samsung T5 SSD. If I connect it to the Thunderbolt port on my HP EliteDesk Mini G4, with Thunderbolt at boot then the SSD is detected without issues. If I unplug it and reconnect then it's not detected. If I force the thunderbolt controller on (boltctl power -t 1) then I can see the new USB host created in lsusb but the attached device is not added. No additional events are shown in dmesg. If I connect the device using another cable then it also doesn't work I have a USB-C cable only rated to USB 2.0 speed then the device is recognized without any issues. Ubuntu 19.04, 5.0.0-15-generic 04:00.0 System peripheral: Intel Corporation JHL7540 Thunderbolt 3 NHI [Titan Ridge 2C 2018] (rev 06) 3a:00.0 USB controller: Intel Corporation JHL7540 Thunderbolt 3 USB Controller [Titan Ridge 2C 2018] (rev 06) --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: toby 1495 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-04-27 (31 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP EliteDesk 800 G4 DM 65W Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-15-generic root=UUID=86b0f677-7a3e-4ea6-9d5c-fd7c57d1f964 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 RelatedPackageVersions: linux-restricted-modules-5.0.0-15-generic N/A linux-backports-modules-5.0.0-15-generic N/A linux-firmware1.178.1 Tags: disco Uname: Linux 5.0.0-15-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-05-26 (2 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/15/2019 dmi.bios.vendor: HP dmi.bios.version: Q21 Ver. 02.06.03 dmi.board.name: 845A dmi.board.vendor: HP dmi.board.version: KBC Version 07.D2.00 dmi.chassis.asset.tag: 8CC84321CJ dmi.chassis.type: 6 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrQ21Ver.02.06.03:bd02/15/2019:svnHP:pnHPEliteDesk800G4DM65W:pvr:rvnHP:rn845A:rvrKBCVersion07.D2.00:cvnHP:ct6:cvr: dmi.product.family: 103C_53307F HP EliteDesk dmi.product.name: HP EliteDesk 800 G4 DM 65W dmi.product.sku: 5BA07US#ABA dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbolt-tools/+bug/1830930/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829209] Re: linux: 4.4.0-149.175 -proposed tracker
*** This bug is a duplicate of bug 1830941 *** https://bugs.launchpad.net/bugs/1830941 ** This bug has been marked a duplicate of bug 1830941 linux: -proposed tracker -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1829209 Title: linux: 4.4.0-149.175 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: In Progress Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow snap-certification-testing series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Fix Released Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1829205 (trusty/linux-aws), bug 1829207 (trusty/linux-lts-xenial) derivatives: bug 1829193 (linux-aws), bug 1829195 (linux-kvm), bug 1829198 (linux-raspi2), bug 1829201 (linux-snapdragon), bug 1829203 (linux-fips) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Testing phase-changed: Thursday, 16. May 2019 13:02 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1829209/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1802233] Re: hwclock test failed on Power9 due to 0.x sec differences / time out waiting for time change
Changing owner to "bugproxy" as the next steps are with IBM on the
Witherspoon and Boston firmware.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1802233
Title:
hwclock test failed on Power9 due to 0.x sec differences / time out
waiting for time change
Status in ubuntu-kernel-tests:
New
Status in The Ubuntu-power-systems project:
Incomplete
Status in linux package in Ubuntu:
Incomplete
Bug description:
The hwclock test will fail on the Power9 system "baltar" due to a
<0.02 second difference.
Traceback (most recent call last):
File "/home/ubuntu/autotest/client/shared/test.py", line 411, in _exec
_call_test_function(self.execute, *p_args, **p_dargs)
File "/home/ubuntu/autotest/client/shared/test.py", line 823, in
_call_test_function
return func(*args, **dargs)
File "/home/ubuntu/autotest/client/shared/test.py", line 291, in execute
postprocess_profiled_run, args, dargs)
File "/home/ubuntu/autotest/client/shared/test.py", line 212, in
_call_run_once
self.run_once(*args, **dargs)
File "/home/ubuntu/autotest/client/tests/hwclock/hwclock.py", line 50, in
run_once
raise error.TestFail("Failed to set hwclock back to Warthog's birthday.
Output of hwclock is '%s'" % date)
TestFail: Failed to set hwclock back to Warthog's birthday. Output of hwclock
is '2004-10-20 04:09:59.582146+'
Didn't see this on Power8 boxes
Sometimes it will fail because "time out waiting for time change" on the same
node:
$ sudo /sbin/hwclock --set --date "2004/10/20 04:10:00"; sudo /sbin/hwclock
hwclock: Timed out waiting for time change.
Workaround for these is to add "sleep 1".
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-38-generic 4.15.0-38.41
ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
Uname: Linux 4.15.0-38-generic ppc64le
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Nov 8 03:45 seq
crw-rw 1 root audio 116, 33 Nov 8 03:45 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: ppc64el
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord':
'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
CurrentDmesg:
Date: Thu Nov 8 06:03:54 2018
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 0451:80ff Texas Instruments, Inc.
Bus 001 Device 004: ID 0557:2419 ATEN International Co., Ltd
Bus 001 Device 002: ID 0557:7000 ATEN International Co., Ltd Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
PciMultimedia:
ProcFB: 0 astdrmfb
ProcKernelCmdLine: root=UUID=acd1a0d7-f6fc-4130-928c-c8b11ad6e4be ro
console=hvc0
ProcLoadAvg: 0.31 0.11 0.03 1/1392 5654
ProcLocks:
1: POSIX ADVISORY WRITE 3544 00:17:582 0 EOF
2: POSIX ADVISORY WRITE 1798 00:17:338 0 EOF
3: POSIX ADVISORY WRITE 3603 00:17:576 0 EOF
4: FLOCK ADVISORY WRITE 3535 00:17:564 0 EOF
5: FLOCK ADVISORY WRITE 4081 00:17:481 0 EOF
ProcSwaps:
Filename TypeSizeUsedPriority
/swap.img file 8388544 0 -2
ProcVersion: Linux version 4.15.0-38-generic (buildd@bos02-ppc64el-018) (gcc
version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #41-Ubuntu SMP Wed Oct 10 10:57:45 UTC
2018
RelatedPackageVersions:
linux-restricted-modules-4.15.0-38-generic N/A
linux-backports-modules-4.15.0-38-generic N/A
linux-firmware 1.173.1
RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
VarLogDump_list: total 0
cpu_cores: Number of cores present = 40
cpu_coreson: Number of cores online = 40
cpu_dscr: DSCR is 16
cpu_freq:
min: 2.862 GHz (cpu 159)
max: 2.862 GHz (cpu 1)
avg: 2.862 GHz
cpu_runmode:
Could not retrieve current diagnostics mode,
No kernel interface to firmware
cpu_smt: SMT=4
-- Firmware information on Baltar --
pnor: P9DSU20190404_IBM_prod_sign.pnor
bmc: SMT_P9_206.bin
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1802233/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829193] Re: linux-aws: 4.4.0-1084.94 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true - kernel-stable-master-bug: 1829209 + kernel-stable-master-bug: 1830941 phase: Ready for Testing phase-changed: Wednesday, 29. May 2019 00:06 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress ** Tags removed: kernel-sru-derivative-of-1829209 ** Tags added: kernel-sru-derivative-of-1830941 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1829193 Title: linux-aws: 4.4.0-1084.94 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Fix Released Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1830941 phase: Ready for Testing phase-changed: Wednesday, 29. May 2019 00:06 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1829193/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829203] Re: linux-fips: 4.4.0-1011.14 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true - kernel-stable-master-bug: 1829209 + kernel-stable-master-bug: 1830941 phase: Ready for Testing phase-changed: Tuesday, 21. May 2019 22:08 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress ** Tags removed: kernel-sru-derivative-of-1829209 ** Tags added: kernel-sru-derivative-of-1830941 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1829203 Title: linux-fips: 4.4.0-1011.14 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Confirmed Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1830941 phase: Ready for Testing phase-changed: Tuesday, 21. May 2019 22:08 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1829203/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1830930] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1830930/+attachment/5267434/+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/1830930 Title: USB 3 devices are not detected on thunderbolt 3 Status in linux package in Ubuntu: New Bug description: I found a strange problem when trying to connect my Samsung T5 SSD. If I connect it to the Thunderbolt port on my HP EliteDesk Mini G4, with Thunderbolt at boot then the SSD is detected without issues. If I unplug it and reconnect then it's not detected. If I force the thunderbolt controller on (boltctl power -t 1) then I can see the new USB host created in lsusb but the attached device is not added. No additional events are shown in dmesg. If I connect the device using another cable then it also doesn't work I have a USB-C cable only rated to USB 2.0 speed then the device is recognized without any issues. Ubuntu 19.04, 5.0.0-15-generic 04:00.0 System peripheral: Intel Corporation JHL7540 Thunderbolt 3 NHI [Titan Ridge 2C 2018] (rev 06) 3a:00.0 USB controller: Intel Corporation JHL7540 Thunderbolt 3 USB Controller [Titan Ridge 2C 2018] (rev 06) --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: toby 1495 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-04-27 (31 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP EliteDesk 800 G4 DM 65W Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-15-generic root=UUID=86b0f677-7a3e-4ea6-9d5c-fd7c57d1f964 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 RelatedPackageVersions: linux-restricted-modules-5.0.0-15-generic N/A linux-backports-modules-5.0.0-15-generic N/A linux-firmware1.178.1 Tags: disco Uname: Linux 5.0.0-15-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-05-26 (2 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/15/2019 dmi.bios.vendor: HP dmi.bios.version: Q21 Ver. 02.06.03 dmi.board.name: 845A dmi.board.vendor: HP dmi.board.version: KBC Version 07.D2.00 dmi.chassis.asset.tag: 8CC84321CJ dmi.chassis.type: 6 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrQ21Ver.02.06.03:bd02/15/2019:svnHP:pnHPEliteDesk800G4DM65W:pvr:rvnHP:rn845A:rvrKBCVersion07.D2.00:cvnHP:ct6:cvr: dmi.product.family: 103C_53307F HP EliteDesk dmi.product.name: HP EliteDesk 800 G4 DM 65W dmi.product.sku: 5BA07US#ABA dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1830930/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829205] Re: linux-aws: 4.4.0-1045.48 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true - kernel-stable-master-bug: 1829209 + kernel-stable-master-bug: 1830941 phase: Ready for Testing phase-changed: Tuesday, 28. May 2019 23:37 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress ** Tags removed: kernel-sru-backport-of-1829209 ** Tags added: kernel-sru-backport-of-1830941 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1829205 Title: linux-aws: 4.4.0-1045.48 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Trusty: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1830941 phase: Ready for Testing phase-changed: Tuesday, 28. May 2019 23:37 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1829205/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1830930] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1830930/+attachment/5267430/+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/1830930 Title: USB 3 devices are not detected on thunderbolt 3 Status in linux package in Ubuntu: New Bug description: I found a strange problem when trying to connect my Samsung T5 SSD. If I connect it to the Thunderbolt port on my HP EliteDesk Mini G4, with Thunderbolt at boot then the SSD is detected without issues. If I unplug it and reconnect then it's not detected. If I force the thunderbolt controller on (boltctl power -t 1) then I can see the new USB host created in lsusb but the attached device is not added. No additional events are shown in dmesg. If I connect the device using another cable then it also doesn't work I have a USB-C cable only rated to USB 2.0 speed then the device is recognized without any issues. Ubuntu 19.04, 5.0.0-15-generic 04:00.0 System peripheral: Intel Corporation JHL7540 Thunderbolt 3 NHI [Titan Ridge 2C 2018] (rev 06) 3a:00.0 USB controller: Intel Corporation JHL7540 Thunderbolt 3 USB Controller [Titan Ridge 2C 2018] (rev 06) --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: toby 1495 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-04-27 (31 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP EliteDesk 800 G4 DM 65W Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-15-generic root=UUID=86b0f677-7a3e-4ea6-9d5c-fd7c57d1f964 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 RelatedPackageVersions: linux-restricted-modules-5.0.0-15-generic N/A linux-backports-modules-5.0.0-15-generic N/A linux-firmware1.178.1 Tags: disco Uname: Linux 5.0.0-15-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-05-26 (2 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/15/2019 dmi.bios.vendor: HP dmi.bios.version: Q21 Ver. 02.06.03 dmi.board.name: 845A dmi.board.vendor: HP dmi.board.version: KBC Version 07.D2.00 dmi.chassis.asset.tag: 8CC84321CJ dmi.chassis.type: 6 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrQ21Ver.02.06.03:bd02/15/2019:svnHP:pnHPEliteDesk800G4DM65W:pvr:rvnHP:rn845A:rvrKBCVersion07.D2.00:cvnHP:ct6:cvr: dmi.product.family: 103C_53307F HP EliteDesk dmi.product.name: HP EliteDesk 800 G4 DM 65W dmi.product.sku: 5BA07US#ABA dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1830930/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829195] Re: linux-kvm: 4.4.0-1047.53 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true - kernel-stable-master-bug: 1829209 + kernel-stable-master-bug: 1830941 phase: Testing phase-changed: Monday, 20. May 2019 11:54 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED regression-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress ** Tags removed: kernel-sru-derivative-of-1829209 ** Tags added: kernel-sru-derivative-of-1830941 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1829195 Title: linux-kvm: 4.4.0-1047.53 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1830941 phase: Testing phase-changed: Monday, 20. May 2019 11:54 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED regression-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1829195/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1830930] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1830930/+attachment/5267433/+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/1830930 Title: USB 3 devices are not detected on thunderbolt 3 Status in linux package in Ubuntu: New Bug description: I found a strange problem when trying to connect my Samsung T5 SSD. If I connect it to the Thunderbolt port on my HP EliteDesk Mini G4, with Thunderbolt at boot then the SSD is detected without issues. If I unplug it and reconnect then it's not detected. If I force the thunderbolt controller on (boltctl power -t 1) then I can see the new USB host created in lsusb but the attached device is not added. No additional events are shown in dmesg. If I connect the device using another cable then it also doesn't work I have a USB-C cable only rated to USB 2.0 speed then the device is recognized without any issues. Ubuntu 19.04, 5.0.0-15-generic 04:00.0 System peripheral: Intel Corporation JHL7540 Thunderbolt 3 NHI [Titan Ridge 2C 2018] (rev 06) 3a:00.0 USB controller: Intel Corporation JHL7540 Thunderbolt 3 USB Controller [Titan Ridge 2C 2018] (rev 06) --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: toby 1495 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-04-27 (31 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP EliteDesk 800 G4 DM 65W Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-15-generic root=UUID=86b0f677-7a3e-4ea6-9d5c-fd7c57d1f964 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 RelatedPackageVersions: linux-restricted-modules-5.0.0-15-generic N/A linux-backports-modules-5.0.0-15-generic N/A linux-firmware1.178.1 Tags: disco Uname: Linux 5.0.0-15-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-05-26 (2 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/15/2019 dmi.bios.vendor: HP dmi.bios.version: Q21 Ver. 02.06.03 dmi.board.name: 845A dmi.board.vendor: HP dmi.board.version: KBC Version 07.D2.00 dmi.chassis.asset.tag: 8CC84321CJ dmi.chassis.type: 6 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrQ21Ver.02.06.03:bd02/15/2019:svnHP:pnHPEliteDesk800G4DM65W:pvr:rvnHP:rn845A:rvrKBCVersion07.D2.00:cvnHP:ct6:cvr: dmi.product.family: 103C_53307F HP EliteDesk dmi.product.name: HP EliteDesk 800 G4 DM 65W dmi.product.sku: 5BA07US#ABA dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1830930/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1830930] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1830930/+attachment/5267429/+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/1830930 Title: USB 3 devices are not detected on thunderbolt 3 Status in linux package in Ubuntu: New Bug description: I found a strange problem when trying to connect my Samsung T5 SSD. If I connect it to the Thunderbolt port on my HP EliteDesk Mini G4, with Thunderbolt at boot then the SSD is detected without issues. If I unplug it and reconnect then it's not detected. If I force the thunderbolt controller on (boltctl power -t 1) then I can see the new USB host created in lsusb but the attached device is not added. No additional events are shown in dmesg. If I connect the device using another cable then it also doesn't work I have a USB-C cable only rated to USB 2.0 speed then the device is recognized without any issues. Ubuntu 19.04, 5.0.0-15-generic 04:00.0 System peripheral: Intel Corporation JHL7540 Thunderbolt 3 NHI [Titan Ridge 2C 2018] (rev 06) 3a:00.0 USB controller: Intel Corporation JHL7540 Thunderbolt 3 USB Controller [Titan Ridge 2C 2018] (rev 06) --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: toby 1495 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-04-27 (31 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP EliteDesk 800 G4 DM 65W Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-15-generic root=UUID=86b0f677-7a3e-4ea6-9d5c-fd7c57d1f964 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 RelatedPackageVersions: linux-restricted-modules-5.0.0-15-generic N/A linux-backports-modules-5.0.0-15-generic N/A linux-firmware1.178.1 Tags: disco Uname: Linux 5.0.0-15-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-05-26 (2 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/15/2019 dmi.bios.vendor: HP dmi.bios.version: Q21 Ver. 02.06.03 dmi.board.name: 845A dmi.board.vendor: HP dmi.board.version: KBC Version 07.D2.00 dmi.chassis.asset.tag: 8CC84321CJ dmi.chassis.type: 6 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrQ21Ver.02.06.03:bd02/15/2019:svnHP:pnHPEliteDesk800G4DM65W:pvr:rvnHP:rn845A:rvrKBCVersion07.D2.00:cvnHP:ct6:cvr: dmi.product.family: 103C_53307F HP EliteDesk dmi.product.name: HP EliteDesk 800 G4 DM 65W dmi.product.sku: 5BA07US#ABA dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1830930/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1802233] Re: hwclock test failed on Power9 due to 0.x sec differences / time out waiting for time change
** Changed in: ubuntu-power-systems
Assignee: Canonical Kernel Team (canonical-kernel-team) => bugproxy
(bugproxy)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1802233
Title:
hwclock test failed on Power9 due to 0.x sec differences / time out
waiting for time change
Status in ubuntu-kernel-tests:
New
Status in The Ubuntu-power-systems project:
Incomplete
Status in linux package in Ubuntu:
Incomplete
Bug description:
The hwclock test will fail on the Power9 system "baltar" due to a
<0.02 second difference.
Traceback (most recent call last):
File "/home/ubuntu/autotest/client/shared/test.py", line 411, in _exec
_call_test_function(self.execute, *p_args, **p_dargs)
File "/home/ubuntu/autotest/client/shared/test.py", line 823, in
_call_test_function
return func(*args, **dargs)
File "/home/ubuntu/autotest/client/shared/test.py", line 291, in execute
postprocess_profiled_run, args, dargs)
File "/home/ubuntu/autotest/client/shared/test.py", line 212, in
_call_run_once
self.run_once(*args, **dargs)
File "/home/ubuntu/autotest/client/tests/hwclock/hwclock.py", line 50, in
run_once
raise error.TestFail("Failed to set hwclock back to Warthog's birthday.
Output of hwclock is '%s'" % date)
TestFail: Failed to set hwclock back to Warthog's birthday. Output of hwclock
is '2004-10-20 04:09:59.582146+'
Didn't see this on Power8 boxes
Sometimes it will fail because "time out waiting for time change" on the same
node:
$ sudo /sbin/hwclock --set --date "2004/10/20 04:10:00"; sudo /sbin/hwclock
hwclock: Timed out waiting for time change.
Workaround for these is to add "sleep 1".
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-38-generic 4.15.0-38.41
ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
Uname: Linux 4.15.0-38-generic ppc64le
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Nov 8 03:45 seq
crw-rw 1 root audio 116, 33 Nov 8 03:45 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: ppc64el
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord':
'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
CurrentDmesg:
Date: Thu Nov 8 06:03:54 2018
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 0451:80ff Texas Instruments, Inc.
Bus 001 Device 004: ID 0557:2419 ATEN International Co., Ltd
Bus 001 Device 002: ID 0557:7000 ATEN International Co., Ltd Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
PciMultimedia:
ProcFB: 0 astdrmfb
ProcKernelCmdLine: root=UUID=acd1a0d7-f6fc-4130-928c-c8b11ad6e4be ro
console=hvc0
ProcLoadAvg: 0.31 0.11 0.03 1/1392 5654
ProcLocks:
1: POSIX ADVISORY WRITE 3544 00:17:582 0 EOF
2: POSIX ADVISORY WRITE 1798 00:17:338 0 EOF
3: POSIX ADVISORY WRITE 3603 00:17:576 0 EOF
4: FLOCK ADVISORY WRITE 3535 00:17:564 0 EOF
5: FLOCK ADVISORY WRITE 4081 00:17:481 0 EOF
ProcSwaps:
Filename TypeSizeUsedPriority
/swap.img file 8388544 0 -2
ProcVersion: Linux version 4.15.0-38-generic (buildd@bos02-ppc64el-018) (gcc
version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #41-Ubuntu SMP Wed Oct 10 10:57:45 UTC
2018
RelatedPackageVersions:
linux-restricted-modules-4.15.0-38-generic N/A
linux-backports-modules-4.15.0-38-generic N/A
linux-firmware 1.173.1
RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
VarLogDump_list: total 0
cpu_cores: Number of cores present = 40
cpu_coreson: Number of cores online = 40
cpu_dscr: DSCR is 16
cpu_freq:
min: 2.862 GHz (cpu 159)
max: 2.862 GHz (cpu 1)
avg: 2.862 GHz
cpu_runmode:
Could not retrieve current diagnostics mode,
No kernel interface to firmware
cpu_smt: SMT=4
-- Firmware information on Baltar --
pnor: P9DSU20190404_IBM_prod_sign.pnor
bmc: SMT_P9_206.bin
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1802233/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829201] Re: linux-snapdragon: 4.4.0-1114.119 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: - https://wiki.ubuntu.com/Kernel/kernel-sru-workflow + https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true - kernel-stable-master-bug: 1829209 + kernel-stable-master-bug: 1830941 phase: Ready for Testing phase-changed: Wednesday, 29. May 2019 14:06 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: verification-testing: Ongoing -- testing in progress ** Tags removed: kernel-sru-derivative-of-1829209 ** Tags added: kernel-sru-derivative-of-1830941 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-snapdragon in Ubuntu. https://bugs.launchpad.net/bugs/1829201 Title: linux-snapdragon: 4.4.0-1114.119 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow snap-certification-testing series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Fix Released Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-snapdragon package in Ubuntu: Invalid Status in linux-snapdragon source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1830941 phase: Ready for Testing phase-changed: Wednesday, 29. May 2019 14:06 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1829201/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829198] Re: linux-raspi2: 4.4.0-1110.118 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true - kernel-stable-master-bug: 1829209 + kernel-stable-master-bug: 1830941 phase: Ready for Testing phase-changed: Wednesday, 29. May 2019 07:36 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: snap-certification-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress ** Tags removed: kernel-sru-derivative-of-1829209 ** Tags added: kernel-sru-derivative-of-1830941 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1829198 Title: linux-raspi2: 4.4.0-1110.118 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow snap-certification-testing series: Confirmed Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1830941 phase: Ready for Testing phase-changed: Wednesday, 29. May 2019 07:36 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: snap-certification-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1829198/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1830930] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1830930/+attachment/5267431/+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/1830930 Title: USB 3 devices are not detected on thunderbolt 3 Status in linux package in Ubuntu: New Bug description: I found a strange problem when trying to connect my Samsung T5 SSD. If I connect it to the Thunderbolt port on my HP EliteDesk Mini G4, with Thunderbolt at boot then the SSD is detected without issues. If I unplug it and reconnect then it's not detected. If I force the thunderbolt controller on (boltctl power -t 1) then I can see the new USB host created in lsusb but the attached device is not added. No additional events are shown in dmesg. If I connect the device using another cable then it also doesn't work I have a USB-C cable only rated to USB 2.0 speed then the device is recognized without any issues. Ubuntu 19.04, 5.0.0-15-generic 04:00.0 System peripheral: Intel Corporation JHL7540 Thunderbolt 3 NHI [Titan Ridge 2C 2018] (rev 06) 3a:00.0 USB controller: Intel Corporation JHL7540 Thunderbolt 3 USB Controller [Titan Ridge 2C 2018] (rev 06) --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: toby 1495 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-04-27 (31 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP EliteDesk 800 G4 DM 65W Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-15-generic root=UUID=86b0f677-7a3e-4ea6-9d5c-fd7c57d1f964 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 RelatedPackageVersions: linux-restricted-modules-5.0.0-15-generic N/A linux-backports-modules-5.0.0-15-generic N/A linux-firmware1.178.1 Tags: disco Uname: Linux 5.0.0-15-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-05-26 (2 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/15/2019 dmi.bios.vendor: HP dmi.bios.version: Q21 Ver. 02.06.03 dmi.board.name: 845A dmi.board.vendor: HP dmi.board.version: KBC Version 07.D2.00 dmi.chassis.asset.tag: 8CC84321CJ dmi.chassis.type: 6 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrQ21Ver.02.06.03:bd02/15/2019:svnHP:pnHPEliteDesk800G4DM65W:pvr:rvnHP:rn845A:rvrKBCVersion07.D2.00:cvnHP:ct6:cvr: dmi.product.family: 103C_53307F HP EliteDesk dmi.product.name: HP EliteDesk 800 G4 DM 65W dmi.product.sku: 5BA07US#ABA dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1830930/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1830930] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1830930/+attachment/5267432/+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/1830930 Title: USB 3 devices are not detected on thunderbolt 3 Status in linux package in Ubuntu: New Bug description: I found a strange problem when trying to connect my Samsung T5 SSD. If I connect it to the Thunderbolt port on my HP EliteDesk Mini G4, with Thunderbolt at boot then the SSD is detected without issues. If I unplug it and reconnect then it's not detected. If I force the thunderbolt controller on (boltctl power -t 1) then I can see the new USB host created in lsusb but the attached device is not added. No additional events are shown in dmesg. If I connect the device using another cable then it also doesn't work I have a USB-C cable only rated to USB 2.0 speed then the device is recognized without any issues. Ubuntu 19.04, 5.0.0-15-generic 04:00.0 System peripheral: Intel Corporation JHL7540 Thunderbolt 3 NHI [Titan Ridge 2C 2018] (rev 06) 3a:00.0 USB controller: Intel Corporation JHL7540 Thunderbolt 3 USB Controller [Titan Ridge 2C 2018] (rev 06) --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: toby 1495 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-04-27 (31 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP EliteDesk 800 G4 DM 65W Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-15-generic root=UUID=86b0f677-7a3e-4ea6-9d5c-fd7c57d1f964 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 RelatedPackageVersions: linux-restricted-modules-5.0.0-15-generic N/A linux-backports-modules-5.0.0-15-generic N/A linux-firmware1.178.1 Tags: disco Uname: Linux 5.0.0-15-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-05-26 (2 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/15/2019 dmi.bios.vendor: HP dmi.bios.version: Q21 Ver. 02.06.03 dmi.board.name: 845A dmi.board.vendor: HP dmi.board.version: KBC Version 07.D2.00 dmi.chassis.asset.tag: 8CC84321CJ dmi.chassis.type: 6 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrQ21Ver.02.06.03:bd02/15/2019:svnHP:pnHPEliteDesk800G4DM65W:pvr:rvnHP:rn845A:rvrKBCVersion07.D2.00:cvnHP:ct6:cvr: dmi.product.family: 103C_53307F HP EliteDesk dmi.product.name: HP EliteDesk 800 G4 DM 65W dmi.product.sku: 5BA07US#ABA dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1830930/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1830930] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1830930/+attachment/5267427/+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/1830930 Title: USB 3 devices are not detected on thunderbolt 3 Status in linux package in Ubuntu: New Bug description: I found a strange problem when trying to connect my Samsung T5 SSD. If I connect it to the Thunderbolt port on my HP EliteDesk Mini G4, with Thunderbolt at boot then the SSD is detected without issues. If I unplug it and reconnect then it's not detected. If I force the thunderbolt controller on (boltctl power -t 1) then I can see the new USB host created in lsusb but the attached device is not added. No additional events are shown in dmesg. If I connect the device using another cable then it also doesn't work I have a USB-C cable only rated to USB 2.0 speed then the device is recognized without any issues. Ubuntu 19.04, 5.0.0-15-generic 04:00.0 System peripheral: Intel Corporation JHL7540 Thunderbolt 3 NHI [Titan Ridge 2C 2018] (rev 06) 3a:00.0 USB controller: Intel Corporation JHL7540 Thunderbolt 3 USB Controller [Titan Ridge 2C 2018] (rev 06) --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: toby 1495 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-04-27 (31 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP EliteDesk 800 G4 DM 65W Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-15-generic root=UUID=86b0f677-7a3e-4ea6-9d5c-fd7c57d1f964 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 RelatedPackageVersions: linux-restricted-modules-5.0.0-15-generic N/A linux-backports-modules-5.0.0-15-generic N/A linux-firmware1.178.1 Tags: disco Uname: Linux 5.0.0-15-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-05-26 (2 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/15/2019 dmi.bios.vendor: HP dmi.bios.version: Q21 Ver. 02.06.03 dmi.board.name: 845A dmi.board.vendor: HP dmi.board.version: KBC Version 07.D2.00 dmi.chassis.asset.tag: 8CC84321CJ dmi.chassis.type: 6 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrQ21Ver.02.06.03:bd02/15/2019:svnHP:pnHPEliteDesk800G4DM65W:pvr:rvnHP:rn845A:rvrKBCVersion07.D2.00:cvnHP:ct6:cvr: dmi.product.family: 103C_53307F HP EliteDesk dmi.product.name: HP EliteDesk 800 G4 DM 65W dmi.product.sku: 5BA07US#ABA dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1830930/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1830930] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1830930/+attachment/5267425/+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/1830930 Title: USB 3 devices are not detected on thunderbolt 3 Status in linux package in Ubuntu: New Bug description: I found a strange problem when trying to connect my Samsung T5 SSD. If I connect it to the Thunderbolt port on my HP EliteDesk Mini G4, with Thunderbolt at boot then the SSD is detected without issues. If I unplug it and reconnect then it's not detected. If I force the thunderbolt controller on (boltctl power -t 1) then I can see the new USB host created in lsusb but the attached device is not added. No additional events are shown in dmesg. If I connect the device using another cable then it also doesn't work I have a USB-C cable only rated to USB 2.0 speed then the device is recognized without any issues. Ubuntu 19.04, 5.0.0-15-generic 04:00.0 System peripheral: Intel Corporation JHL7540 Thunderbolt 3 NHI [Titan Ridge 2C 2018] (rev 06) 3a:00.0 USB controller: Intel Corporation JHL7540 Thunderbolt 3 USB Controller [Titan Ridge 2C 2018] (rev 06) --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: toby 1495 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-04-27 (31 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP EliteDesk 800 G4 DM 65W Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-15-generic root=UUID=86b0f677-7a3e-4ea6-9d5c-fd7c57d1f964 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 RelatedPackageVersions: linux-restricted-modules-5.0.0-15-generic N/A linux-backports-modules-5.0.0-15-generic N/A linux-firmware1.178.1 Tags: disco Uname: Linux 5.0.0-15-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-05-26 (2 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/15/2019 dmi.bios.vendor: HP dmi.bios.version: Q21 Ver. 02.06.03 dmi.board.name: 845A dmi.board.vendor: HP dmi.board.version: KBC Version 07.D2.00 dmi.chassis.asset.tag: 8CC84321CJ dmi.chassis.type: 6 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrQ21Ver.02.06.03:bd02/15/2019:svnHP:pnHPEliteDesk800G4DM65W:pvr:rvnHP:rn845A:rvrKBCVersion07.D2.00:cvnHP:ct6:cvr: dmi.product.family: 103C_53307F HP EliteDesk dmi.product.name: HP EliteDesk 800 G4 DM 65W dmi.product.sku: 5BA07US#ABA dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1830930/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1830930] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1830930/+attachment/5267426/+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/1830930 Title: USB 3 devices are not detected on thunderbolt 3 Status in linux package in Ubuntu: New Bug description: I found a strange problem when trying to connect my Samsung T5 SSD. If I connect it to the Thunderbolt port on my HP EliteDesk Mini G4, with Thunderbolt at boot then the SSD is detected without issues. If I unplug it and reconnect then it's not detected. If I force the thunderbolt controller on (boltctl power -t 1) then I can see the new USB host created in lsusb but the attached device is not added. No additional events are shown in dmesg. If I connect the device using another cable then it also doesn't work I have a USB-C cable only rated to USB 2.0 speed then the device is recognized without any issues. Ubuntu 19.04, 5.0.0-15-generic 04:00.0 System peripheral: Intel Corporation JHL7540 Thunderbolt 3 NHI [Titan Ridge 2C 2018] (rev 06) 3a:00.0 USB controller: Intel Corporation JHL7540 Thunderbolt 3 USB Controller [Titan Ridge 2C 2018] (rev 06) --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: toby 1495 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-04-27 (31 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP EliteDesk 800 G4 DM 65W Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-15-generic root=UUID=86b0f677-7a3e-4ea6-9d5c-fd7c57d1f964 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 RelatedPackageVersions: linux-restricted-modules-5.0.0-15-generic N/A linux-backports-modules-5.0.0-15-generic N/A linux-firmware1.178.1 Tags: disco Uname: Linux 5.0.0-15-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-05-26 (2 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/15/2019 dmi.bios.vendor: HP dmi.bios.version: Q21 Ver. 02.06.03 dmi.board.name: 845A dmi.board.vendor: HP dmi.board.version: KBC Version 07.D2.00 dmi.chassis.asset.tag: 8CC84321CJ dmi.chassis.type: 6 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrQ21Ver.02.06.03:bd02/15/2019:svnHP:pnHPEliteDesk800G4DM65W:pvr:rvnHP:rn845A:rvrKBCVersion07.D2.00:cvnHP:ct6:cvr: dmi.product.family: 103C_53307F HP EliteDesk dmi.product.name: HP EliteDesk 800 G4 DM 65W dmi.product.sku: 5BA07US#ABA dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1830930/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1830941] [NEW] linux: -proposed tracker
Public bug reported: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1829205 (trusty/linux-aws), bug 1829207 (trusty/linux-lts-xenial) derivatives: bug 1829193 (linux-aws), bug 1829195 (linux-kvm), bug 1829198 (linux-raspi2), bug 1829201 (linux-snapdragon), bug 1829203 (linux-fips) -- swm properties -- ** Affects: kernel-sru-workflow Importance: Medium Status: In Progress ** Affects: kernel-sru-workflow/automated-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/certification-testing Importance: Medium Assignee: Canonical Hardware Certification (canonical-hw-cert) Status: New ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-signed Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-security Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-updates Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/security-signoff Importance: Medium Assignee: Canonical Security Team (canonical-security) Status: New ** Affects: kernel-sru-workflow/snap-certification-testing Importance: Medium Assignee: Canonical Hardware Certification (canonical-hw-cert) Status: New ** Affects: kernel-sru-workflow/snap-release-to-beta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/snap-release-to-candidate Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/snap-release-to-edge Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/snap-release-to-stable Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/verification-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Xenial) Importance: Medium Status: New ** Tags: kernel-release-tracking-bug kernel-release-tracking-bug-live kernel-sru-cycle-2019.05.13-3 xenial ** Also affects: kernel-sru-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/certification-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-signed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-security Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-updates Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/security-signoff Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/snap-certification-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/snap-release-to-beta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/snap-release-to-candidate Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/snap-release-to-edge Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/snap-release-to-stable Importance: Undecided Status: New ** Also affects:
[Kernel-packages] [Bug 1830930] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1830930/+attachment/5267424/+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/1830930 Title: USB 3 devices are not detected on thunderbolt 3 Status in linux package in Ubuntu: New Bug description: I found a strange problem when trying to connect my Samsung T5 SSD. If I connect it to the Thunderbolt port on my HP EliteDesk Mini G4, with Thunderbolt at boot then the SSD is detected without issues. If I unplug it and reconnect then it's not detected. If I force the thunderbolt controller on (boltctl power -t 1) then I can see the new USB host created in lsusb but the attached device is not added. No additional events are shown in dmesg. If I connect the device using another cable then it also doesn't work I have a USB-C cable only rated to USB 2.0 speed then the device is recognized without any issues. Ubuntu 19.04, 5.0.0-15-generic 04:00.0 System peripheral: Intel Corporation JHL7540 Thunderbolt 3 NHI [Titan Ridge 2C 2018] (rev 06) 3a:00.0 USB controller: Intel Corporation JHL7540 Thunderbolt 3 USB Controller [Titan Ridge 2C 2018] (rev 06) --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: toby 1495 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-04-27 (31 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP EliteDesk 800 G4 DM 65W Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-15-generic root=UUID=86b0f677-7a3e-4ea6-9d5c-fd7c57d1f964 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 RelatedPackageVersions: linux-restricted-modules-5.0.0-15-generic N/A linux-backports-modules-5.0.0-15-generic N/A linux-firmware1.178.1 Tags: disco Uname: Linux 5.0.0-15-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-05-26 (2 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/15/2019 dmi.bios.vendor: HP dmi.bios.version: Q21 Ver. 02.06.03 dmi.board.name: 845A dmi.board.vendor: HP dmi.board.version: KBC Version 07.D2.00 dmi.chassis.asset.tag: 8CC84321CJ dmi.chassis.type: 6 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrQ21Ver.02.06.03:bd02/15/2019:svnHP:pnHPEliteDesk800G4DM65W:pvr:rvnHP:rn845A:rvrKBCVersion07.D2.00:cvnHP:ct6:cvr: dmi.product.family: 103C_53307F HP EliteDesk dmi.product.name: HP EliteDesk 800 G4 DM 65W dmi.product.sku: 5BA07US#ABA dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1830930/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1830930] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1830930/+attachment/5267428/+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/1830930 Title: USB 3 devices are not detected on thunderbolt 3 Status in linux package in Ubuntu: New Bug description: I found a strange problem when trying to connect my Samsung T5 SSD. If I connect it to the Thunderbolt port on my HP EliteDesk Mini G4, with Thunderbolt at boot then the SSD is detected without issues. If I unplug it and reconnect then it's not detected. If I force the thunderbolt controller on (boltctl power -t 1) then I can see the new USB host created in lsusb but the attached device is not added. No additional events are shown in dmesg. If I connect the device using another cable then it also doesn't work I have a USB-C cable only rated to USB 2.0 speed then the device is recognized without any issues. Ubuntu 19.04, 5.0.0-15-generic 04:00.0 System peripheral: Intel Corporation JHL7540 Thunderbolt 3 NHI [Titan Ridge 2C 2018] (rev 06) 3a:00.0 USB controller: Intel Corporation JHL7540 Thunderbolt 3 USB Controller [Titan Ridge 2C 2018] (rev 06) --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: toby 1495 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-04-27 (31 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP EliteDesk 800 G4 DM 65W Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-15-generic root=UUID=86b0f677-7a3e-4ea6-9d5c-fd7c57d1f964 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 RelatedPackageVersions: linux-restricted-modules-5.0.0-15-generic N/A linux-backports-modules-5.0.0-15-generic N/A linux-firmware1.178.1 Tags: disco Uname: Linux 5.0.0-15-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-05-26 (2 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/15/2019 dmi.bios.vendor: HP dmi.bios.version: Q21 Ver. 02.06.03 dmi.board.name: 845A dmi.board.vendor: HP dmi.board.version: KBC Version 07.D2.00 dmi.chassis.asset.tag: 8CC84321CJ dmi.chassis.type: 6 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrQ21Ver.02.06.03:bd02/15/2019:svnHP:pnHPEliteDesk800G4DM65W:pvr:rvnHP:rn845A:rvrKBCVersion07.D2.00:cvnHP:ct6:cvr: dmi.product.family: 103C_53307F HP EliteDesk dmi.product.name: HP EliteDesk 800 G4 DM 65W dmi.product.sku: 5BA07US#ABA dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1830930/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1830930] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1830930/+attachment/5267423/+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/1830930 Title: USB 3 devices are not detected on thunderbolt 3 Status in linux package in Ubuntu: New Bug description: I found a strange problem when trying to connect my Samsung T5 SSD. If I connect it to the Thunderbolt port on my HP EliteDesk Mini G4, with Thunderbolt at boot then the SSD is detected without issues. If I unplug it and reconnect then it's not detected. If I force the thunderbolt controller on (boltctl power -t 1) then I can see the new USB host created in lsusb but the attached device is not added. No additional events are shown in dmesg. If I connect the device using another cable then it also doesn't work I have a USB-C cable only rated to USB 2.0 speed then the device is recognized without any issues. Ubuntu 19.04, 5.0.0-15-generic 04:00.0 System peripheral: Intel Corporation JHL7540 Thunderbolt 3 NHI [Titan Ridge 2C 2018] (rev 06) 3a:00.0 USB controller: Intel Corporation JHL7540 Thunderbolt 3 USB Controller [Titan Ridge 2C 2018] (rev 06) --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: toby 1495 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-04-27 (31 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP EliteDesk 800 G4 DM 65W Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-15-generic root=UUID=86b0f677-7a3e-4ea6-9d5c-fd7c57d1f964 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 RelatedPackageVersions: linux-restricted-modules-5.0.0-15-generic N/A linux-backports-modules-5.0.0-15-generic N/A linux-firmware1.178.1 Tags: disco Uname: Linux 5.0.0-15-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-05-26 (2 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/15/2019 dmi.bios.vendor: HP dmi.bios.version: Q21 Ver. 02.06.03 dmi.board.name: 845A dmi.board.vendor: HP dmi.board.version: KBC Version 07.D2.00 dmi.chassis.asset.tag: 8CC84321CJ dmi.chassis.type: 6 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrQ21Ver.02.06.03:bd02/15/2019:svnHP:pnHPEliteDesk800G4DM65W:pvr:rvnHP:rn845A:rvrKBCVersion07.D2.00:cvnHP:ct6:cvr: dmi.product.family: 103C_53307F HP EliteDesk dmi.product.name: HP EliteDesk 800 G4 DM 65W dmi.product.sku: 5BA07US#ABA dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1830930/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
