[Kernel-packages] [Bug 1851350] Re: bionic/linux-aws-5.3: 5.3.0-1006.6~18.04.1 -proposed tracker
5.3.0-1006.6~18.04.1 - aws Regression test CMPL, RTB. Issue to note in arm64 (aws): ubuntu_kernel_selftests - test_blackhole_dev in net (bug 1851619) ubuntu_ltp - proc01 (bug 1829849) fs_fill (bug 1842266) cpuacct_100_100 (bug 1829978) memcg_max_usage_in_bytes (bug 1829979) memcg_stat (bug 1829983) memcg_use_hierarchy (bug 1829989) memcg_usage_in_bytes (bug 1829984) memcg_stat_rss (bug 1837035) cgroup_fj_* failure caused by memcg_test_3 (bug 1836694) hugemmap01 (bug 1851777) getaddrinfo_01 (bug 1829995) ubuntu_ltp_syscalls - msgstress03 on some nodes (bug 1783881) ubuntu_lttng_smoke_test - failed to build lttng module on 5.3 Bionic (bug 1844764) ubuntu_qrt_kernel_security - test_140_kernel_modules_not_tainted (bug 1850888) Skipped / blacklisted: * iosched_bugs * libhugetlbfs * tsc * ubuntu_32_on_64 * ubuntu_seccomp * ubuntu_sysdig_smoke_test Issue to note in x86_64 (aws): tsc - failed on i3.metal (bug 1851607) ubuntu_kernel_selftests - test_blackhole_dev in net (bug 1851619) ubuntu_kvm_unit_tests - vmx on i3.metal (1821394) vmx_apicv_test on i3.metal (bug 1827866) ubuntu_ltp - proc01 (bug 1829849) fs_fill (bug 1842266) vma05 (bug 1845863) cpuacct_100_100 (bug 1829978) cpuset_hotplug (bug 1834006) memcg_max_usage_in_bytes (bug 1829979) memcg_stat (bug 1829983) memcg_use_hierarchy (bug 1829989) memcg_usage_in_bytes (bug 1829984) getaddrinfo_01 (bug 1829995) crypto_user02 (bug 1837543) ltp_acpi (bug 1829982) ubuntu_ltp_syscalls - msgstress03 on some nodes (bug 1783881) ubuntu_lttng_smoke_test - failed to build lttng module on 5.3 Bionic (bug 1844764) ubuntu_qrt_kernel_security - test_140_kernel_modules_not_tainted (bug 1850888) ubuntu_sysdig_smoke_test - failed to build sysdig DKMS with 5.3 kernel (bug 1844766) Skipped / blacklisted: * libhugetlbfs ** Changed in: kernel-sru-workflow/regression-testing Status: In Progress => 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 in Ubuntu. https://bugs.launchpad.net/bugs/1851350 Title: bionic/linux-aws-5.3: 5.3.0-1006.6~18.04.1 -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-lrm 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: 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: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid 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: 1850477 packages: lrm: linux-restricted-modules-aws-5.3 main: linux-aws-5.3 meta: linux-meta-aws-5.3 phase: Testing phase-changed: Thursday, 07. November 2019 10:26 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1851350/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1851350] Re: bionic/linux-aws-5.3: 5.3.0-1006.6~18.04.1 -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: 1850477 packages: lrm: linux-restricted-modules-aws-5.3 main: linux-aws-5.3 meta: linux-meta-aws-5.3 phase: Testing phase-changed: Thursday, 07. November 2019 10:26 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED - regression-testing: Ongoing -- testing in progress variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1851350 Title: bionic/linux-aws-5.3: 5.3.0-1006.6~18.04.1 -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-lrm 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: 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: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid 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: 1850477 packages: lrm: linux-restricted-modules-aws-5.3 main: linux-aws-5.3 meta: linux-meta-aws-5.3 phase: Testing phase-changed: Thursday, 07. November 2019 10:26 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1851350/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1845863] Re: vma05 in mm from ubuntu_ltp failed on B-hwe-edge 5.3
Found on B-AWS-5.3 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1845863 Title: vma05 in mm from ubuntu_ltp failed on B-hwe-edge 5.3 Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Bug description: Test failed with: tag=vma05 stime=1568998082 dur=0 exit=exited stat=1 core=no cu=23 cs=4 Need to check if it has something to do with AppArmor startup='Fri Sep 20 16:48:02 2019' vma05 1 TINFO: timeout per run is 0h 5m 0s vma05 1 TFAIL: [vsyscall] reporting wrong vma05 1 TPASS: [vdso] backtrace complete vma05 2 TINFO: AppArmor enabled, this may affect test results vma05 2 TINFO: it can be disabled with TST_DISABLE_APPARMOR=1 (requires super/root) vma05 2 TINFO: loaded AppArmor profiles: none Summary: passed 1 failed 1 skipped 0 warnings 0 tag=vma05 stime=1568998082 dur=0 exit=exited stat=1 core=no cu=23 cs=4 startup='Fri Sep 20 16:48:02 2019' vma05 1 TINFO: timeout per run is 0h 5m 0s vma05 1 TFAIL: [vsyscall] reporting wrong vma05 1 TPASS: [vdso] backtrace complete vma05 2 TINFO: AppArmor enabled, this may affect test results vma05 2 TINFO: it can be disabled with TST_DISABLE_APPARMOR=1 (requires super/root) vma05 2 TINFO: loaded AppArmor profiles: none Summary: passed 1 failed 1 skipped 0 warnings 0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1845863/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1851350] Re: bionic/linux-aws-5.3: 5.3.0-1006.6~18.04.1 -proposed tracker
** Tags added: regression-testing-passed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1851350 Title: bionic/linux-aws-5.3: 5.3.0-1006.6~18.04.1 -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-lrm 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: 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: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid 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: 1850477 packages: lrm: linux-restricted-modules-aws-5.3 main: linux-aws-5.3 meta: linux-meta-aws-5.3 phase: Testing phase-changed: Thursday, 07. November 2019 10:26 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1851350/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1849720] Re: Running VM with Virtual NIC Crashes Host OS
Zach, thanks for the feedback. Since we still struggle to recreate this on our side is there a chance that you could test kernels from [1] to help spotting which version bump exactly it was? Going further we might even need to bisect things, but one step at a time. I'd not want to put this on you (or the others), but if it continues not to trigger for us we might have to. It is now clear that multiple people see this dependent on the kernel, adding a kernel task for it. Maybe they have heard about similar issue on other bugs? [1]: https://kernel.ubuntu.com/~kernel-ppa/mainline/ ** Tags added: bot-stop-nagging ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Running VM with Virtual NIC Crashes Host OS + KVM with e1000e and WinGuest Host OS on kernel 5.3 (ok with 5.0) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1849720 Title: KVM with e1000e and WinGuest Host OS on kernel 5.3 (ok with 5.0) Status in linux package in Ubuntu: New Status in qemu package in Ubuntu: In Progress Bug description: After upgrading to Ubuntu 19.10 I noticed that all of my Windows Servers VMs would cause a hard crash on the Host OS shortly after starting up the VM. I tracked it down to the Guest OS attempting to use the Network Connection, and if I disabled the virtual NIC for the VM, everything runs OK (albeit without a working network connection for the Guest OS). Note that I'm just using the built in virtual network called "default" that get's installed by default and uses NAT forwarding. I believe the problem is related to AppArmor, as I noticed some errors present in various log files. Unfortunately, due to a time critical project I had to roll back to Ubuntu 19.04 and didn't capture any of the log files. I did, however, find another user on Reddit with the exact same problems that I encountered and he agreed to let me post the log files. Here are what are think are the relevant pieces from the log files: === Oct 22 22:59:23 brian-pc dnsmasq[2178]: exiting on receipt of SIGTERM Oct 22 22:59:23 brian-pc kernel: [ 67.001284] device virbr0-nic left promiscuous mode Oct 22 22:59:23 brian-pc kernel: [ 67.001298] virbr0: port 1(virbr0-nic) entered disabled state Oct 22 22:59:23 brian-pc NetworkManager[3557]: [1571799563.3862] device (virbr0-nic): released from master device virbr0 Oct 22 22:59:23 brian-pc gnome-shell[4401]: Removing a network device that was not added Oct 22 22:59:23 brian-pc gnome-shell[2463]: Removing a network device that was not added Oct 22 22:59:23 brian-pc avahi-daemon[1621]: Interface virbr0.IPv4 no longer relevant for mDNS. Oct 22 22:59:23 brian-pc avahi-daemon[1621]: Leaving mDNS multicast group on interface virbr0.IPv4 with address 192.168.122.1. Oct 22 22:59:23 brian-pc avahi-daemon[1621]: Withdrawing address record for 192.168.122.1 on virbr0. Oct 22 22:59:23 brian-pc NetworkManager[3557]: [1571799563.6859] device (virbr0): state change: activated -> unmanaged (reason 'unmanaged', sys-iface-state: 'removed') Oct 22 22:59:23 brian-pc gnome-shell[2463]: Removing a network device that was not added Oct 22 22:59:23 brian-pc gnome-shell[4401]: Removing a network device that was not added Oct 22 22:59:23 brian-pc dbus-daemon[1610]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.192' (uid=0 pid=3557 comm="/usr/sbin/NetworkManager --no-daemon " label="unconfined") Oct 22 22:59:23 brian-pc systemd[1]: Starting Network Manager Script Dispatcher Service... Oct 22 22:59:23 brian-pc gnome-shell[2463]: Object NM.ActiveConnection (0x55ccfb376e50), has been already deallocated — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Oct 22 22:59:23 brian-pc gnome-shell[2463]: == Stack trace for context 0x55ccfb8d15f0 == Oct 22 22:59:23 brian-pc gnome-shell[2463]: #0 55ccfbc736c0 i resource:///org/gnome/shell/ui/status/network.js:1329 (7f52226be550 @ 56) Oct 22 22:59:23 brian-pc gnome-shell[2463]: #1 55ccfbc73628 i resource:///org/gnome/shell/ui/status/network.js:1346 (7f52226be5e0 @ 113) Oct 22 22:59:23 brian-pc gnome-shell[2463]: #2 55ccfbc73588 i resource:///org/gnome/shell/ui/status/network.js:2049 (7f52226c1940 @ 216) Oct 22 22:59:23 brian-pc gnome-shell[2463]: #3 55ccfbc734f0 i resource:///org/gnome/shell/ui/status/network.js:1853 (7f52226bfee0 @ 134) Oct 22 22:59:23 brian-pc gnome-shell[2463]: #4 55ccfbc73430 i self-hosted:979 (7f522262dee0 @ 440) Oct 22 22:59:23 brian-pc gnome-shell[2463]: JS ERROR: TypeError: connection.get_s
Re: [Kernel-packages] [Bug 1520874] Re: [MacBook8, 1] keyboard does not work
>From 3 years ago? No sorry I've given up on ubuntu entirely after the 18.04+netplan+liveservercloudstupid installer nonsense and have opted for more sane distros. On Fri, 8 Nov 2019 at 04:05, Tijmen Wildervanck wrote: > @anomaly256: Could you please give a link to the bug report you filled? > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1520874 > > Title: > [MacBook8,1] keyboard does not work > > Status in linux package in Ubuntu: > Invalid > > Bug description: > 4.2.0-18-generic and upstream 4.4-rc2 both have no input after grub. > The touchpad also doesn't work and I would guess they are related > since both devices show up as children of the GSPI and LPSS > controllers in OS X. > > ProblemType: Bug > DistroRelease: Ubuntu 15.10 > Package: linux-image-4.2.0-18-generic 4.2.0-18.22 > ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3 > Uname: Linux 4.2.0-18-generic x86_64 > ApportVersion: 2.19.1-0ubuntu5 > Architecture: amd64 > AudioDevicesInUse: >USERPID ACCESS COMMAND >/dev/snd/controlC0: nell 1355 F pulseaudio >/dev/snd/controlC1: nell 1355 F pulseaudio > CurrentDesktop: Unity > Date: Sat Nov 28 19:58:26 2015 > IwConfig: >enx00249b07662f no wireless extensions. > >lono wireless extensions. > MachineType: Apple Inc. MacBook8,1 > ProcFB: 0 inteldrmfb > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-18-generic.efi.signed > root=UUID=cda41380-82fb-4b7d-850e-c742811e2f45 ro > RelatedPackageVersions: >linux-restricted-modules-4.2.0-18-generic N/A >linux-backports-modules-4.2.0-18-generic N/A >linux-firmware1.153 > RfKill: > > SourcePackage: linux > UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 07/31/2015 > dmi.bios.vendor: Apple Inc. > dmi.bios.version: MB81.88Z.0164.B08.1507311433 > dmi.board.asset.tag: Base Board Asset Tag# > dmi.board.name: Mac-BE0E8AC46FE800CC > dmi.board.vendor: Apple Inc. > dmi.board.version: MacBook8,1 > dmi.chassis.asset.tag: Chassis Board Asset Tag# > dmi.chassis.type: 9 > dmi.chassis.vendor: Apple Inc. > dmi.chassis.version: Mac-BE0E8AC46FE800CC > dmi.modalias: > dmi:bvnAppleInc.:bvrMB81.88Z.0164.B08.1507311433:bd07/31/2015:svnAppleInc.:pnMacBook8,1:pvr1.0:rvnAppleInc.:rnMac-BE0E8AC46FE800CC:rvrMacBook8,1:cvnAppleInc.:ct9:cvrMac-BE0E8AC46FE800CC: > dmi.product.name: MacBook8,1 > dmi.product.version: 1.0 > dmi.sys.vendor: Apple Inc. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1520874/+subscriptions > -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1520874 Title: [MacBook8,1] keyboard does not work Status in linux package in Ubuntu: Invalid Bug description: 4.2.0-18-generic and upstream 4.4-rc2 both have no input after grub. The touchpad also doesn't work and I would guess they are related since both devices show up as children of the GSPI and LPSS controllers in OS X. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-18-generic 4.2.0-18.22 ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3 Uname: Linux 4.2.0-18-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nell 1355 F pulseaudio /dev/snd/controlC1: nell 1355 F pulseaudio CurrentDesktop: Unity Date: Sat Nov 28 19:58:26 2015 IwConfig: enx00249b07662f no wireless extensions. lono wireless extensions. MachineType: Apple Inc. MacBook8,1 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-18-generic.efi.signed root=UUID=cda41380-82fb-4b7d-850e-c742811e2f45 ro RelatedPackageVersions: linux-restricted-modules-4.2.0-18-generic N/A linux-backports-modules-4.2.0-18-generic N/A linux-firmware1.153 RfKill: SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/31/2015 dmi.bios.vendor: Apple Inc. dmi.bios.version: MB81.88Z.0164.B08.1507311433 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-BE0E8AC46FE800CC dmi.board.vendor: Apple Inc. dmi.board.version: MacBook8,1 dmi.chassis.asset.tag: Chassis Board Asset Tag# dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-BE0E8AC46FE800CC dmi.modalias: dmi:bvnAppleInc.:bvrMB81.88Z.0164.B08.1507311433:bd07/31/2015:svnAppleInc.:pnMacBook8,1:pvr1.0:rvnAppleInc.:rnMac-BE0E8AC46FE800CC:rvrMacBook8,1:cvnAppleInc.:ct9:cvrMac-
[Kernel-packages] [Bug 1849720] 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 1849720 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/1849720 Title: KVM with e1000e and WinGuest Host OS on kernel 5.3 (ok with 5.0) Status in linux package in Ubuntu: Incomplete Status in qemu package in Ubuntu: In Progress Bug description: After upgrading to Ubuntu 19.10 I noticed that all of my Windows Servers VMs would cause a hard crash on the Host OS shortly after starting up the VM. I tracked it down to the Guest OS attempting to use the Network Connection, and if I disabled the virtual NIC for the VM, everything runs OK (albeit without a working network connection for the Guest OS). Note that I'm just using the built in virtual network called "default" that get's installed by default and uses NAT forwarding. I believe the problem is related to AppArmor, as I noticed some errors present in various log files. Unfortunately, due to a time critical project I had to roll back to Ubuntu 19.04 and didn't capture any of the log files. I did, however, find another user on Reddit with the exact same problems that I encountered and he agreed to let me post the log files. Here are what are think are the relevant pieces from the log files: === Oct 22 22:59:23 brian-pc dnsmasq[2178]: exiting on receipt of SIGTERM Oct 22 22:59:23 brian-pc kernel: [ 67.001284] device virbr0-nic left promiscuous mode Oct 22 22:59:23 brian-pc kernel: [ 67.001298] virbr0: port 1(virbr0-nic) entered disabled state Oct 22 22:59:23 brian-pc NetworkManager[3557]: [1571799563.3862] device (virbr0-nic): released from master device virbr0 Oct 22 22:59:23 brian-pc gnome-shell[4401]: Removing a network device that was not added Oct 22 22:59:23 brian-pc gnome-shell[2463]: Removing a network device that was not added Oct 22 22:59:23 brian-pc avahi-daemon[1621]: Interface virbr0.IPv4 no longer relevant for mDNS. Oct 22 22:59:23 brian-pc avahi-daemon[1621]: Leaving mDNS multicast group on interface virbr0.IPv4 with address 192.168.122.1. Oct 22 22:59:23 brian-pc avahi-daemon[1621]: Withdrawing address record for 192.168.122.1 on virbr0. Oct 22 22:59:23 brian-pc NetworkManager[3557]: [1571799563.6859] device (virbr0): state change: activated -> unmanaged (reason 'unmanaged', sys-iface-state: 'removed') Oct 22 22:59:23 brian-pc gnome-shell[2463]: Removing a network device that was not added Oct 22 22:59:23 brian-pc gnome-shell[4401]: Removing a network device that was not added Oct 22 22:59:23 brian-pc dbus-daemon[1610]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.192' (uid=0 pid=3557 comm="/usr/sbin/NetworkManager --no-daemon " label="unconfined") Oct 22 22:59:23 brian-pc systemd[1]: Starting Network Manager Script Dispatcher Service... Oct 22 22:59:23 brian-pc gnome-shell[2463]: Object NM.ActiveConnection (0x55ccfb376e50), has been already deallocated — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Oct 22 22:59:23 brian-pc gnome-shell[2463]: == Stack trace for context 0x55ccfb8d15f0 == Oct 22 22:59:23 brian-pc gnome-shell[2463]: #0 55ccfbc736c0 i resource:///org/gnome/shell/ui/status/network.js:1329 (7f52226be550 @ 56) Oct 22 22:59:23 brian-pc gnome-shell[2463]: #1 55ccfbc73628 i resource:///org/gnome/shell/ui/status/network.js:1346 (7f52226be5e0 @ 113) Oct 22 22:59:23 brian-pc gnome-shell[2463]: #2 55ccfbc73588 i resource:///org/gnome/shell/ui/status/network.js:2049 (7f52226c1940 @ 216) Oct 22 22:59:23 brian-pc gnome-shell[2463]: #3 55ccfbc734f0 i resource:///org/gnome/shell/ui/status/network.js:1853 (7f52226bfee0 @ 134) Oct 22 22:59:23 brian-pc gnome-shell[2463]: #4 55ccfbc73430 i self-hosted:979 (7f522262dee0 @ 440) Oct 22 22:59:23 brian-pc gnome-shell[2463]: JS ERROR: TypeError: connection.get_setting_ip4_config is not a function#012_isHotSpotMaster@resource:///org/gnome/shell/ui/status/network.js:1333:25#012getIndicatorIcon@resource:///org/gnome/shell/ui/status/network.js:1346:13#012_updateIcon@resource:///org/gn
[Kernel-packages] [Bug 1851014] Re: WiFi (inbuilt) and Bluetooth not detected
Errored with: Kernel preparation unnecessary for this kernel. Skipping... applying patch 0002-Makefile.patch...patching file Makefile Hunk #1 succeeded at 113 with fuzz 1. Hunk #2 succeeded at 132 with fuzz 2 (offset 1 line). applying patch 0003-Make-up-for-missing-init_MUTEX.patch...patching file src/wl/sys/wl_linux.c Hunk #1 succeeded at 111 with fuzz 2 (offset 12 lines). applying patch 0010-change-the-network-interface-name-from-eth-to-wlan.patch...patching file src/wl/sys/wl_linux.c Hunk #1 succeeded at 221 (offset -14 lines). applying patch 0013-gcc.patch...patching file Makefile applying patch 0019-broadcom-sta-6.30.223.248-3.18-null-pointer-fix.patch...patching file src/wl/sys/wl_linux.c Hunk #1 succeeded at 2169 (offset 12 lines). applying patch 0020-add-support-for-linux-4.3.patch...patching file src/shared/linux_osl.c applying patch 0021-add-support-for-Linux-4.7.patch...patching file src/wl/sys/wl_cfg80211_hybrid.c applying patch 0022-add-support-for-Linux-4.8.patch...patching file src/wl/sys/wl_cfg80211_hybrid.c Hunk #1 succeeded at 2391 (offset 3 lines). Hunk #2 succeeded at 2501 (offset 3 lines). Hunk #3 succeeded at 2933 (offset 9 lines). applying patch 0023-add-support-for-Linux-4.11.patch...patching file src/include/linuxver.h patching file src/wl/sys/wl_linux.c Hunk #1 succeeded at 2919 (offset 4 lines). applying patch 0024-add-support-for-Linux-4.12.patch...patching file src/wl/sys/wl_cfg80211_hybrid.c Hunk #1 succeeded at 55 (offset 5 lines). Hunk #2 succeeded at 472 (offset 5 lines). Hunk #3 succeeded at 2371 (offset 5 lines). Hunk #4 succeeded at 2388 (offset 5 lines). applying patch 0025-add-support-for-Linux-4.14.patch...patching file src/shared/linux_osl.c Hunk #1 succeeded at 1080 (offset 4 lines). applying patch 0026-add-support-for-Linux-4.15.patch...patching file src/wl/sys/wl_linux.c Hunk #2 succeeded at 2306 (offset 4 lines). Hunk #3 succeeded at 2368 (offset 4 lines). Building module: cleaning build area... make -j4 KERNELRELEASE=5.3.0-19-generic -C /lib/modules/5.3.0-19-generic/build M=/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build...(bad exit status: 2) ERROR (dkms apport): kernel package linux-headers-5.3.0-19-generic is not supported Error! Bad return status for module build on kernel: 5.3.0-19-generic (x86_64) Consult /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/make.log for more information. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1851014 Title: WiFi (inbuilt) and Bluetooth not detected Status in linux package in Ubuntu: Confirmed Bug description: Mint 19.2 laptop:XPS 13 9343 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: alan 5186 F pulseaudio /dev/snd/controlC1: alan 5186 F pulseaudio /dev/snd/controlC0: alan 5186 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.2 InstallationDate: Installed on 2018-07-24 (466 days ago) InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180717 IwConfig: lono wireless extensions. enx803f5d083b2a no wireless extensions. MachineType: Dell Inc. XPS 13 9343 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic root=UUID=7c3f7872-75bd-4816-9eeb-e5ac1d8cddda ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-19.20~18.04.2-generic 5.3.1 RelatedPackageVersions: linux-restricted-modules-5.3.0-19-generic N/A linux-backports-modules-5.3.0-19-generic N/A linux-firmware1.173.9 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: tina Uname: Linux 5.3.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 01/23/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A15 dmi.board.name: 0310JH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA15:bd01/23/2018:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn0310JH:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9343 dmi.product.sku: 0665 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851014/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1849720] Re: KVM with e1000e and WinGuest Host OS on kernel 5.3 (ok with 5.0)
This doesn't need kernel logs at this state of the bug, bot pleas stop spamming :-) ** 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/1849720 Title: KVM with e1000e and WinGuest Host OS on kernel 5.3 (ok with 5.0) Status in linux package in Ubuntu: Confirmed Status in qemu package in Ubuntu: In Progress Bug description: After upgrading to Ubuntu 19.10 I noticed that all of my Windows Servers VMs would cause a hard crash on the Host OS shortly after starting up the VM. I tracked it down to the Guest OS attempting to use the Network Connection, and if I disabled the virtual NIC for the VM, everything runs OK (albeit without a working network connection for the Guest OS). Note that I'm just using the built in virtual network called "default" that get's installed by default and uses NAT forwarding. I believe the problem is related to AppArmor, as I noticed some errors present in various log files. Unfortunately, due to a time critical project I had to roll back to Ubuntu 19.04 and didn't capture any of the log files. I did, however, find another user on Reddit with the exact same problems that I encountered and he agreed to let me post the log files. Here are what are think are the relevant pieces from the log files: === Oct 22 22:59:23 brian-pc dnsmasq[2178]: exiting on receipt of SIGTERM Oct 22 22:59:23 brian-pc kernel: [ 67.001284] device virbr0-nic left promiscuous mode Oct 22 22:59:23 brian-pc kernel: [ 67.001298] virbr0: port 1(virbr0-nic) entered disabled state Oct 22 22:59:23 brian-pc NetworkManager[3557]: [1571799563.3862] device (virbr0-nic): released from master device virbr0 Oct 22 22:59:23 brian-pc gnome-shell[4401]: Removing a network device that was not added Oct 22 22:59:23 brian-pc gnome-shell[2463]: Removing a network device that was not added Oct 22 22:59:23 brian-pc avahi-daemon[1621]: Interface virbr0.IPv4 no longer relevant for mDNS. Oct 22 22:59:23 brian-pc avahi-daemon[1621]: Leaving mDNS multicast group on interface virbr0.IPv4 with address 192.168.122.1. Oct 22 22:59:23 brian-pc avahi-daemon[1621]: Withdrawing address record for 192.168.122.1 on virbr0. Oct 22 22:59:23 brian-pc NetworkManager[3557]: [1571799563.6859] device (virbr0): state change: activated -> unmanaged (reason 'unmanaged', sys-iface-state: 'removed') Oct 22 22:59:23 brian-pc gnome-shell[2463]: Removing a network device that was not added Oct 22 22:59:23 brian-pc gnome-shell[4401]: Removing a network device that was not added Oct 22 22:59:23 brian-pc dbus-daemon[1610]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.192' (uid=0 pid=3557 comm="/usr/sbin/NetworkManager --no-daemon " label="unconfined") Oct 22 22:59:23 brian-pc systemd[1]: Starting Network Manager Script Dispatcher Service... Oct 22 22:59:23 brian-pc gnome-shell[2463]: Object NM.ActiveConnection (0x55ccfb376e50), has been already deallocated — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Oct 22 22:59:23 brian-pc gnome-shell[2463]: == Stack trace for context 0x55ccfb8d15f0 == Oct 22 22:59:23 brian-pc gnome-shell[2463]: #0 55ccfbc736c0 i resource:///org/gnome/shell/ui/status/network.js:1329 (7f52226be550 @ 56) Oct 22 22:59:23 brian-pc gnome-shell[2463]: #1 55ccfbc73628 i resource:///org/gnome/shell/ui/status/network.js:1346 (7f52226be5e0 @ 113) Oct 22 22:59:23 brian-pc gnome-shell[2463]: #2 55ccfbc73588 i resource:///org/gnome/shell/ui/status/network.js:2049 (7f52226c1940 @ 216) Oct 22 22:59:23 brian-pc gnome-shell[2463]: #3 55ccfbc734f0 i resource:///org/gnome/shell/ui/status/network.js:1853 (7f52226bfee0 @ 134) Oct 22 22:59:23 brian-pc gnome-shell[2463]: #4 55ccfbc73430 i self-hosted:979 (7f522262dee0 @ 440) Oct 22 22:59:23 brian-pc gnome-shell[2463]: JS ERROR: TypeError: connection.get_setting_ip4_config is not a function#012_isHotSpotMaster@resource:///org/gnome/shell/ui/status/network.js:1333:25#012getIndicatorIcon@resource:///org/gnome/shell/ui/status/network.js:1346:13#012_updateIcon@resource:///org/gnome/shell/ui/status/network.js:2049:52#012_syncVpnConnections@resource:///org/gnome/shell/ui/status/network.js:1853:9 Oct 22 22:59:23 brian-pc gnome-shell[2463]: JS ERROR: TypeError: connectionSettings is null#012_updateConnection@resource:///org/gnome/shell/ui/status/network.js:1922:9 Oct 22 22:59:23 brian-pc gnome-shell[4401]: JS ERROR: TypeError: connectionSettings is null#012_updateConnection@resource:///org/gnome/shell/ui/status/networ
[Kernel-packages] [Bug 1748103] Re: apic test in kvm-unit-test failed
Passed with B-Azure-5.0 Standard_F32s_v2 -- 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/1748103 Title: apic test in kvm-unit-test failed Status in ubuntu-kernel-tests: Confirmed Status in linux package in Ubuntu: Incomplete Status in linux-azure package in Ubuntu: New Status in linux-azure-edge package in Ubuntu: New Status in linux source package in Xenial: New Status in linux-azure source package in Xenial: New Status in linux-azure-edge source package in Xenial: New Status in linux source package in Cosmic: New Status in linux-azure source package in Cosmic: New Status in linux-azure-edge source package in Cosmic: New Bug description: With Joshua's comment in bug 1719524: "Nested KVM can only be tried on instance sizes with nested Hypervisor support: Ev3 and Dv3.", although the instance name is E4v3 here but I can start a KVM on it. Test apic will timeout on it. Steps: 1. git clone --depth=1 https://git.kernel.org/pub/scm/virt/kvm/kvm-unit-tests.git 2. cd kvm-unit-tests; ./configure; make 3. Run the apic test as root: # TESTNAME=apic TIMEOUT=30 ACCEL= ./x86/run x86/apic.flat -smp 2 -cpu qemu64,+x2apic,+tsc-deadline timeout -k 1s --foreground 30 /usr/bin/qemu-system-x86_64 -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel x86/apic.flat -smp 2 -cpu qemu64,+x2apic,+tsc-deadline # -initrd /tmp/tmp.onXtr5JVp7 enabling apic enabling apic paging enabled cr0 = 80010011 cr3 = 459000 cr4 = 20 apic version: 1050014 PASS: apic existence PASS: xapic id matches cpuid PASS: writeable xapic id PASS: non-writeable x2apic id PASS: sane x2apic id FAIL: x2apic id matches cpuid PASS: correct xapic id after reset PASS: apic_disable: Local apic enabled PASS: apic_disable: CPUID.1H:EDX.APIC[bit 9] is set PASS: apic_disable: Local apic disabled PASS: apic_disable: CPUID.1H:EDX.APIC[bit 9] is clear PASS: apic_disable: Local apic enabled PASS: apic_disable: CPUID.1H:EDX.APIC[bit 9] is set x2apic enabled PASS: x2apic enabled to invalid state PASS: x2apic enabled to apic enabled PASS: disabled to invalid state PASS: disabled to x2apic enabled PASS: apic enabled to invalid state PASS: apicbase: relocate apic PASS: apicbase: reserved physaddr bits PASS: apicbase: reserved low bits PASS: self ipi starting broadcast (x2apic) PASS: APIC physical broadcast address PASS: APIC physical broadcast shorthand PASS: nmi-after-sti qemu-system-x86_64: terminating on signal 15 from pid 7246 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.14.0-1004-azure-edge 4.14.0-1004.4 ProcVersionSignature: User Name 4.14.0-1004.4-username-edge 4.14.14 Uname: Linux 4.14.0-1004-azure-edge x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Thu Feb 8 06:00:55 2018 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-azure-edge UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 DistroRelease: Ubuntu 16.04 Package: linux-azure-edge PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: User Name 4.13.0-1009.12-username 4.13.13 Tags: xenial uec-images Uname: Linux 4.13.0-1009-azure x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy libvirtd lxd netdev plugdev sudo video _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1748103/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1848987] Re: bionic/linux-azure: 5.0.0-1024.25~18.04.1 -proposed tracker
5.0.0-1024.25~18.04.1 - azure Regression test CMPL, RTB. Issue to note in x86_64 (azure): ubuntu_kernel_selftests - cpu-hotplug (bug 1814232) test_bpf in net (bug 1812189) msg_zerocopy in net (bug 1812620) trace_printk in ftrace (bug 1830084) ubuntu_kvm_unit_tests - ept (bug 1824228) memory (bug 1831449) vmx (bug 1821394) on Standard_F32s_v2 ubuntu_ltp - proc01 (bug 1829849) fs_fill (bug 1842266) cpuset_hotplug (bug 1834006) memcg_max_usage_in_bytes (bug 1829979) memcg_stat (bug 1829983) memcg_subgroup_charge (bug 1847982) memcg_usage_in_bytes (bug 1829984) memcg_use_hierarchy (bug 1829989) cpuhotplug02 (bug 1836166) cpuhotplug03 (bug 1836167) cpuhotplug04 (bug 1836169) cpuhotplug06 (bug 1836170) getaddrinfo_01 (bug 1829995) crypto_user02 (bug 1837543) ubuntu_ltp_syscalls - msgstress03 (bug 1797341) msgstress04 (bug 1797348) ubuntu_lxc - lxc-test-no-new-privs (failed to fetch package) on Standard_DS15_v2, Standard_DS5_v2 (bug 1821152), passed on the rest ubuntu_qrt_apparmor - failed because git time out Skipped / blacklisted: * libhugetlbfs ** Changed in: kernel-sru-workflow/regression-testing Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Assignee: Canonical Kernel Team (canonical-kernel-team) => Po-Hsu Lin (cypressyew) ** Tags added: regression-testing-passed -- 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/1848987 Title: bionic/linux-azure: 5.0.0-1024.25~18.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm 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: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow stakeholder-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Bionic: Confirmed 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: 1848989 packages: lrm: linux-restricted-modules-azure main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Thursday, 24. October 2019 14:12 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: verification-testing: Ongoing -- testing in progress trackers: bionic/linux-azure-edge: bug 1848986 bionic/linux-azure/azure-kernel: bug 1848985 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1848987/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1851014] Re: WiFi (inbuilt) and Bluetooth not detected
contents of make.log:
DKMS make.log for bcmwl-6.30.223.271+bdcom for kernel 5.3.0-19-generic (x86_64)
Fri 8 Nov 09:13:36 GMT 2019
make: Entering directory '/usr/src/linux-headers-5.3.0-19-generic'
CFG80211 API is prefered for this kernel version
Using CFG80211 API
CC [M] /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.o
CC [M] /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.o
CC [M] /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_iw.o
CC [M]
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.o
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c: In function
‘wl_pci_probe’:
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:780:2:
warning: this ‘if’ clause does not guard... [-Wmisleading-indentation]
if ((val & 0xff00) != 0)
^~
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:782:3: note:
...this statement, but the latter is misleadingly indented as if it were
guarded by the ‘if’
bar1_size = pci_resource_len(pdev, 2);
^
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:
In function ‘wl_dev_ioctl’:
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:462:9:
error: implicit declaration of function ‘get_ds’; did you mean ‘get_fs’?
[-Werror=implicit-function-declaration]
set_fs(get_ds());
^~
get_fs
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:462:9:
error: incompatible type for argument 1 of ‘set_fs’
In file included from ./include/linux/uaccess.h:11:0,
from ./arch/x86/include/asm/fpu/xstate.h:5,
from ./arch/x86/include/asm/pgtable.h:26,
from ./include/linux/mm.h:99,
from
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/include/linuxver.h:65,
from
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:26:
./arch/x86/include/asm/uaccess.h:29:20: note: expected ‘mm_segment_t {aka
struct }’ but argument is of type ‘int’
static inline void set_fs(mm_segment_t fs)
^~
In file included from
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:40:0:
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:
In function ‘wl_set_auth_type’:
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.h:52:5:
warning: this statement may fall through [-Wimplicit-fallthrough=]
if (wl_dbg_level & WL_DBG_DBG) { \
^
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:816:3:
note: in expansion of macro ‘WL_DBG’
WL_DBG(("network eap\n"));
^~
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:817:2:
note: here
default:
^~~
cc1: some warnings being treated as errors
scripts/Makefile.build:288: recipe for target
'/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.o'
failed
make[1]: ***
[/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.o]
Error 1
make[1]: *** Waiting for unfinished jobs
Makefile:1653: recipe for target
'_module_/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build' failed
make: *** [_module_/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build] Error 2
make: Leaving directory '/usr/src/linux-headers-5.3.0-19-generic'
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1851014
Title:
WiFi (inbuilt) and Bluetooth not detected
Status in linux package in Ubuntu:
Confirmed
Bug description:
Mint 19.2 laptop:XPS 13 9343
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.8
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: alan 5186 F pulseaudio
/dev/snd/controlC1: alan 5186 F pulseaudio
/dev/snd/controlC0: alan 5186 F pulseaudio
CurrentDesktop: X-Cinnamon
DistroRelease: Linux Mint 19.2
InstallationDate: Installed on 2018-07-24 (466 days ago)
InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180717
IwConfig:
lono wireless extensions.
enx803f5d083b2a no wireless extensions.
MachineType: Dell Inc. XPS 13 9343
Package: linux (not installed)
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic
root=UUID=7c3f7872-75bd-4816-9eeb-e5ac1d8cddda ro quiet splash vt.handoff=1
ProcVersionSignature: Ubuntu 5.3.0-19.20~18.04.2-generic 5.3.1
RelatedPackageVersions:
linux-restricted-modules-5.3.0-19-generic N/A
linux-backports-modules-5.3.0-19-generic N/A
linux-firmware1.173.9
RfKill:
0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
Tags: tina
Uname: Linux 5.3.0-19-generic x86_64
UpgradeStatus: No upgrade log pre
[Kernel-packages] [Bug 1848987] Re: bionic/linux-azure: 5.0.0-1024.25~18.04.1 -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: 1848989 packages: lrm: linux-restricted-modules-azure main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Thursday, 24. October 2019 14:12 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - regression-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress trackers: bionic/linux-azure-edge: bug 1848986 bionic/linux-azure/azure-kernel: bug 1848985 variant: debs -- 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/1848987 Title: bionic/linux-azure: 5.0.0-1024.25~18.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm 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: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow stakeholder-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Bionic: Confirmed 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: 1848989 packages: lrm: linux-restricted-modules-azure main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Thursday, 24. October 2019 14:12 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: verification-testing: Ongoing -- testing in progress trackers: bionic/linux-azure-edge: bug 1848986 bionic/linux-azure/azure-kernel: bug 1848985 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1848987/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1850986] Re: many problems:
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 1850986 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. Please note: `ubuntu-bug`, `apport` & bug reporting tools are provided with Ubuntu by default, many require manual addition for some releases of downstream OSes based on Ubuntu (eg. Linux Mint). You should check with your distribution first. ** Changed in: apport (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/1850986 Title: many problems: Status in apport package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: 1st Neither ubuntu-bug linux nor sudo ubuntu-bug linux sudo cat /proc/version_signature > version.log sudo lspci -vnvn > lspci-vnvn.log work! 2 Bug reporting is so hard! 3 Cannot find bug reporting section for Linuxmint so as to empart to Ubuntu that the problem is with the Kernels and not the drivers. 4. The bug is with 4K monitors and the Linuxmint OS is continuously trying to load drivers for the screen. Constantly failing. I would gladly report the bug properly if I knew how to. As information is so vague I can't help. Remember that if a novice can't find what he is looking for to fix a bug then there is a guarantee that the novice will never use that system again. Not all users are able to understand all commands if they are not in use every day. That is the case with me. Sadly, I want to use the system but the system is failing it's novices. It's not the fault of the novice if he/she cannot find the relevant information as there is seriously way too much information on any given subject out there. Deciphering it is a minefield of displeasure. Pity ain't it! That is why people are giving up computers. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.2 InstallationDate: Installed on 2019-11-03 (4 days ago) InstallationMedia: Linux Mint 19.2 "Tina" - Release amd64 20190729 NonfreeKernelModules: nvidia_modeset nvidia Package: linux PackageArchitecture: all ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Tags: third-party-packages tina Uname: Linux 5.0.0-32-generic x86_64 UnreportableReason: This is not an official Linux package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.2 InstallationDate: Installed on 2019-11-03 (4 days ago) InstallationMedia: Linux Mint 19.2 "Tina" - Release amd64 20190729 NonfreeKernelModules: nvidia_modeset nvidia Package: linux PackageArchitecture: all ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Tags: third-party-packages tina Uname: Linux 5.0.0-32-generic x86_64 UnreportableReason: This is not an official Linux package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1850986/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1850574] Re: disco/linux: 5.0.0-34.36 -proposed tracker
Kernel deb testing completes, no regressions found. Ready for Updates. Results here: https://trello.com/c/KUzCy34J/227-disco-linux- image-500-34-generic-500-3436 ** Changed in: kernel-sru-workflow/certification-testing Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1850574 Title: disco/linux: 5.0.0-34.36 -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-lrm 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: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Disco: Confirmed 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 bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Wednesday, 30. October 2019 18:14 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: verification-testing: Ongoing -- testing in progress trackers: bionic/linux-bluefield: bug 1849002 bionic/linux-hwe: bug 1850587 bionic/linux-oem-osp1: bug 1849001 disco/linux-aws: bug 1848984 disco/linux-azure: bug 1848989 disco/linux-gcp: bug 1848995 disco/linux-kvm: bug 1848996 disco/linux-oracle: bug 1848998 disco/linux-raspi2: bug 1848981 disco/linux-snapdragon: bug 1848999 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1850574/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1850574] Re: disco/linux: 5.0.0-34.36 -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 bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Wednesday, 30. October 2019 18:14 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - certification-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress trackers: bionic/linux-bluefield: bug 1849002 bionic/linux-hwe: bug 1850587 bionic/linux-oem-osp1: bug 1849001 disco/linux-aws: bug 1848984 disco/linux-azure: bug 1848989 disco/linux-gcp: bug 1848995 disco/linux-kvm: bug 1848996 disco/linux-oracle: bug 1848998 disco/linux-raspi2: bug 1848981 disco/linux-snapdragon: bug 1848999 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1850574 Title: disco/linux: 5.0.0-34.36 -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-lrm 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: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Disco: Confirmed 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 bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Wednesday, 30. October 2019 18:14 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: verification-testing: Ongoing -- testing in progress trackers: bionic/linux-bluefield: bug 1849002 bionic/linux-hwe: bug 1850587 bionic/linux-oem-osp1: bug 1849001 disco/linux-aws: bug 1848984 disco/linux-azure: bug 1848989 disco/linux-gcp: bug 1848995 disco/linux-kvm: bug 1848996 disco/linux-oracle: bug 1848998 disco/linux-raspi2: bug 1848981 disco/linux-snapdragon: bug 1848999 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1850574/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1850986] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1850986/+attachment/5303815/+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/1850986 Title: many problems: Status in apport package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: 1st Neither ubuntu-bug linux nor sudo ubuntu-bug linux sudo cat /proc/version_signature > version.log sudo lspci -vnvn > lspci-vnvn.log work! 2 Bug reporting is so hard! 3 Cannot find bug reporting section for Linuxmint so as to empart to Ubuntu that the problem is with the Kernels and not the drivers. 4. The bug is with 4K monitors and the Linuxmint OS is continuously trying to load drivers for the screen. Constantly failing. I would gladly report the bug properly if I knew how to. As information is so vague I can't help. Remember that if a novice can't find what he is looking for to fix a bug then there is a guarantee that the novice will never use that system again. Not all users are able to understand all commands if they are not in use every day. That is the case with me. Sadly, I want to use the system but the system is failing it's novices. It's not the fault of the novice if he/she cannot find the relevant information as there is seriously way too much information on any given subject out there. Deciphering it is a minefield of displeasure. Pity ain't it! That is why people are giving up computers. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.2 InstallationDate: Installed on 2019-11-03 (4 days ago) InstallationMedia: Linux Mint 19.2 "Tina" - Release amd64 20190729 NonfreeKernelModules: nvidia_modeset nvidia Package: linux PackageArchitecture: all ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Tags: third-party-packages tina Uname: Linux 5.0.0-32-generic x86_64 UnreportableReason: This is not an official Linux package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.2 InstallationDate: Installed on 2019-11-03 (4 days ago) InstallationMedia: Linux Mint 19.2 "Tina" - Release amd64 20190729 NonfreeKernelModules: nvidia_modeset nvidia Package: linux PackageArchitecture: all ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Tags: third-party-packages tina Uname: Linux 5.0.0-32-generic x86_64 UnreportableReason: This is not an official Linux package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.2 InstallationDate: Installed on 2019-11-03 (4 days ago) InstallationMedia: Linux Mint 19.2 "Tina" - Release amd64 20190729 NonfreeKernelModules: nvidia_modeset nvidia Package: linux PackageArchitecture: all ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Tags: third-party-packages tina Uname: Linux 5.0.0-32-generic x86_64 UnreportableReason: This is not an official Linux package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1850986/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1850986] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1850986/+attachment/5303816/+files/ProcEnviron.txt ** Description changed: 1st Neither ubuntu-bug linux nor sudo ubuntu-bug linux sudo cat /proc/version_signature > version.log sudo lspci -vnvn > lspci-vnvn.log work! 2 Bug reporting is so hard! 3 Cannot find bug reporting section for Linuxmint so as to empart to Ubuntu that the problem is with the Kernels and not the drivers. 4. The bug is with 4K monitors and the Linuxmint OS is continuously trying to load drivers for the screen. Constantly failing. I would gladly report the bug properly if I knew how to. As information is so vague I can't help. Remember that if a novice can't find what he is looking for to fix a bug then there is a guarantee that the novice will never use that system again. Not all users are able to understand all commands if they are not in use every day. That is the case with me. Sadly, I want to use the system but the system is failing it's novices. It's not the fault of the novice if he/she cannot find the relevant information as there is seriously way too much information on any given subject out there. Deciphering it is a minefield of displeasure. Pity ain't it! That is why people are giving up computers. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.2 InstallationDate: Installed on 2019-11-03 (4 days ago) InstallationMedia: Linux Mint 19.2 "Tina" - Release amd64 20190729 NonfreeKernelModules: nvidia_modeset nvidia Package: linux PackageArchitecture: all ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Tags: third-party-packages tina Uname: Linux 5.0.0-32-generic x86_64 UnreportableReason: This is not an official Linux package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.9 + Architecture: amd64 + CurrentDesktop: X-Cinnamon + DistroRelease: Linux Mint 19.2 + InstallationDate: Installed on 2019-11-03 (4 days ago) + InstallationMedia: Linux Mint 19.2 "Tina" - Release amd64 20190729 + NonfreeKernelModules: nvidia_modeset nvidia + Package: linux + PackageArchitecture: all + ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 + Tags: third-party-packages tina + Uname: Linux 5.0.0-32-generic x86_64 + UnreportableReason: This is not an official Linux package. Please remove any third party package and try again. + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1850986 Title: many problems: Status in apport package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: 1st Neither ubuntu-bug linux nor sudo ubuntu-bug linux sudo cat /proc/version_signature > version.log sudo lspci -vnvn > lspci-vnvn.log work! 2 Bug reporting is so hard! 3 Cannot find bug reporting section for Linuxmint so as to empart to Ubuntu that the problem is with the Kernels and not the drivers. 4. The bug is with 4K monitors and the Linuxmint OS is continuously trying to load drivers for the screen. Constantly failing. I would gladly report the bug properly if I knew how to. As information is so vague I can't help. Remember that if a novice can't find what he is looking for to fix a bug then there is a guarantee that the novice will never use that system again. Not all users are able to understand all commands if they are not in use every day. That is the case with me. Sadly, I want to use the system but the system is failing it's novices. It's not the fault of the novice if he/she cannot find the relevant information as there is seriously way too much information on any given subject out there. Deciphering it is a minefield of displeasure. Pity ain't it! That is why people are giving up computers. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.2 InstallationDate: Installed on 2019-11-03 (4 days ago) InstallationMedia: Linux Mint 19.2 "Tina" - Release amd64 20190729 NonfreeKernelModules: nvidia_modeset nvidia Package: linux PackageArchitecture: all ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Tags: third-party-packages tina Uname: Linux 5.0.0-32-generic x86_64 UnreportableReason: This is not an official Linux package. Please remove any third party package and try again. UpgradeStatus: No upgrade log pr
[Kernel-packages] [Bug 1851811] [NEW] ftrace in ubuntu_kernel_selftests failed on B-Azure-5.3
Public bug reported: There are 8 failures reported: # # of passed: 74 # # of failed: 8 # # of unresolved: 3 # # of untested: 0 # # of unsupported: 1 # # of xfailed: 1 # # of undefined(test bug): 0 # [53] event trigger - test field variable support [FAIL] # [55] event trigger - test inter-event histogram trigger onchange action [FAIL] # [56] event trigger - test inter-event histogram trigger onmatch action [FAIL] # [57] event trigger - test inter-event histogram trigger onmatch-onmax action [FAIL] # [58] event trigger - test inter-event histogram trigger onmax action [FAIL] # [59] event trigger - test inter-event histogram trigger snapshot action [FAIL] # [61] event trigger - test inter-event histogram trigger trace action [FAIL] # [82] (instance) ftrace - test for function traceon/off triggers [FAIL] ** Affects: ubuntu-kernel-tests Importance: Undecided Status: New ** Affects: linux-azure (Ubuntu) Importance: Undecided Status: New ** Tags: 5.3 azure bionic sru-20191021 ubuntu-kernel-selftests ** Also affects: linux-azure (Ubuntu) Importance: Undecided Status: New ** Tags added: 5.3 azure bionic ubuntu-kernel-selftests ** Tags added: sru-20191021 -- 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/1851811 Title: ftrace in ubuntu_kernel_selftests failed on B-Azure-5.3 Status in ubuntu-kernel-tests: New Status in linux-azure package in Ubuntu: New Bug description: There are 8 failures reported: # # of passed: 74 # # of failed: 8 # # of unresolved: 3 # # of untested: 0 # # of unsupported: 1 # # of xfailed: 1 # # of undefined(test bug): 0 # [53] event trigger - test field variable support [FAIL] # [55] event trigger - test inter-event histogram trigger onchange action [FAIL] # [56] event trigger - test inter-event histogram trigger onmatch action [FAIL] # [57] event trigger - test inter-event histogram trigger onmatch-onmax action [FAIL] # [58] event trigger - test inter-event histogram trigger onmax action [FAIL] # [59] event trigger - test inter-event histogram trigger snapshot action [FAIL] # [61] event trigger - test inter-event histogram trigger trace action [FAIL] # [82] (instance) ftrace - test for function traceon/off triggers [FAIL] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1851811/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1850986] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1850986/+attachment/5303817/+files/Dependencies.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/1850986 Title: many problems: Status in apport package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: 1st Neither ubuntu-bug linux nor sudo ubuntu-bug linux sudo cat /proc/version_signature > version.log sudo lspci -vnvn > lspci-vnvn.log work! 2 Bug reporting is so hard! 3 Cannot find bug reporting section for Linuxmint so as to empart to Ubuntu that the problem is with the Kernels and not the drivers. 4. The bug is with 4K monitors and the Linuxmint OS is continuously trying to load drivers for the screen. Constantly failing. I would gladly report the bug properly if I knew how to. As information is so vague I can't help. Remember that if a novice can't find what he is looking for to fix a bug then there is a guarantee that the novice will never use that system again. Not all users are able to understand all commands if they are not in use every day. That is the case with me. Sadly, I want to use the system but the system is failing it's novices. It's not the fault of the novice if he/she cannot find the relevant information as there is seriously way too much information on any given subject out there. Deciphering it is a minefield of displeasure. Pity ain't it! That is why people are giving up computers. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.2 InstallationDate: Installed on 2019-11-03 (4 days ago) InstallationMedia: Linux Mint 19.2 "Tina" - Release amd64 20190729 NonfreeKernelModules: nvidia_modeset nvidia Package: linux PackageArchitecture: all ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Tags: third-party-packages tina Uname: Linux 5.0.0-32-generic x86_64 UnreportableReason: This is not an official Linux package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.2 InstallationDate: Installed on 2019-11-03 (4 days ago) InstallationMedia: Linux Mint 19.2 "Tina" - Release amd64 20190729 NonfreeKernelModules: nvidia_modeset nvidia Package: linux PackageArchitecture: all ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Tags: third-party-packages tina Uname: Linux 5.0.0-32-generic x86_64 UnreportableReason: This is not an official Linux package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.2 InstallationDate: Installed on 2019-11-03 (4 days ago) InstallationMedia: Linux Mint 19.2 "Tina" - Release amd64 20190729 NonfreeKernelModules: nvidia_modeset nvidia Package: linux PackageArchitecture: all ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Tags: third-party-packages tina Uname: Linux 5.0.0-32-generic x86_64 UnreportableReason: This is not an official Linux package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1850986/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1850986] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1850986/+attachment/5303818/+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/1850986 Title: many problems: Status in apport package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: 1st Neither ubuntu-bug linux nor sudo ubuntu-bug linux sudo cat /proc/version_signature > version.log sudo lspci -vnvn > lspci-vnvn.log work! 2 Bug reporting is so hard! 3 Cannot find bug reporting section for Linuxmint so as to empart to Ubuntu that the problem is with the Kernels and not the drivers. 4. The bug is with 4K monitors and the Linuxmint OS is continuously trying to load drivers for the screen. Constantly failing. I would gladly report the bug properly if I knew how to. As information is so vague I can't help. Remember that if a novice can't find what he is looking for to fix a bug then there is a guarantee that the novice will never use that system again. Not all users are able to understand all commands if they are not in use every day. That is the case with me. Sadly, I want to use the system but the system is failing it's novices. It's not the fault of the novice if he/she cannot find the relevant information as there is seriously way too much information on any given subject out there. Deciphering it is a minefield of displeasure. Pity ain't it! That is why people are giving up computers. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.2 InstallationDate: Installed on 2019-11-03 (4 days ago) InstallationMedia: Linux Mint 19.2 "Tina" - Release amd64 20190729 NonfreeKernelModules: nvidia_modeset nvidia Package: linux PackageArchitecture: all ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Tags: third-party-packages tina Uname: Linux 5.0.0-32-generic x86_64 UnreportableReason: This is not an official Linux package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.2 InstallationDate: Installed on 2019-11-03 (4 days ago) InstallationMedia: Linux Mint 19.2 "Tina" - Release amd64 20190729 NonfreeKernelModules: nvidia_modeset nvidia Package: linux PackageArchitecture: all ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Tags: third-party-packages tina Uname: Linux 5.0.0-32-generic x86_64 UnreportableReason: This is not an official Linux package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.2 InstallationDate: Installed on 2019-11-03 (4 days ago) InstallationMedia: Linux Mint 19.2 "Tina" - Release amd64 20190729 NonfreeKernelModules: nvidia_modeset nvidia Package: linux PackageArchitecture: all ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Tags: third-party-packages tina Uname: Linux 5.0.0-32-generic x86_64 UnreportableReason: This is not an official Linux package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1850986/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1850986] Re: many problems:
apport information ** Tags added: apport-collected third-party-packages tina ** Description changed: 1st Neither ubuntu-bug linux nor sudo ubuntu-bug linux sudo cat /proc/version_signature > version.log sudo lspci -vnvn > lspci-vnvn.log work! 2 Bug reporting is so hard! 3 Cannot find bug reporting section for Linuxmint so as to empart to Ubuntu that the problem is with the Kernels and not the drivers. 4. The bug is with 4K monitors and the Linuxmint OS is continuously trying to load drivers for the screen. Constantly failing. I would gladly report the bug properly if I knew how to. As information is so vague I can't help. Remember that if a novice can't find what he is looking for to fix a bug then there is a guarantee that the novice will never use that system again. Not all users are able to understand all commands if they are not in use every day. That is the case with me. Sadly, I want to use the system but the system is failing it's novices. It's not the fault of the novice if he/she cannot find the relevant information as there is seriously way too much information on any given subject out there. Deciphering it is a minefield of displeasure. Pity ain't it! That is why people are giving up computers. + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.9 + Architecture: amd64 + CurrentDesktop: X-Cinnamon + DistroRelease: Linux Mint 19.2 + InstallationDate: Installed on 2019-11-03 (4 days ago) + InstallationMedia: Linux Mint 19.2 "Tina" - Release amd64 20190729 + NonfreeKernelModules: nvidia_modeset nvidia + Package: linux + PackageArchitecture: all + ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 + Tags: third-party-packages tina + Uname: Linux 5.0.0-32-generic x86_64 + UnreportableReason: This is not an official Linux package. Please remove any third party package and try again. + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1850986/+attachment/5303814/+files/Dependencies.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/1850986 Title: many problems: Status in apport package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: 1st Neither ubuntu-bug linux nor sudo ubuntu-bug linux sudo cat /proc/version_signature > version.log sudo lspci -vnvn > lspci-vnvn.log work! 2 Bug reporting is so hard! 3 Cannot find bug reporting section for Linuxmint so as to empart to Ubuntu that the problem is with the Kernels and not the drivers. 4. The bug is with 4K monitors and the Linuxmint OS is continuously trying to load drivers for the screen. Constantly failing. I would gladly report the bug properly if I knew how to. As information is so vague I can't help. Remember that if a novice can't find what he is looking for to fix a bug then there is a guarantee that the novice will never use that system again. Not all users are able to understand all commands if they are not in use every day. That is the case with me. Sadly, I want to use the system but the system is failing it's novices. It's not the fault of the novice if he/she cannot find the relevant information as there is seriously way too much information on any given subject out there. Deciphering it is a minefield of displeasure. Pity ain't it! That is why people are giving up computers. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.2 InstallationDate: Installed on 2019-11-03 (4 days ago) InstallationMedia: Linux Mint 19.2 "Tina" - Release amd64 20190729 NonfreeKernelModules: nvidia_modeset nvidia Package: linux PackageArchitecture: all ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Tags: third-party-packages tina Uname: Linux 5.0.0-32-generic x86_64 UnreportableReason: This is not an official Linux package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.2 InstallationDate: Installed on 2019-11-03 (4 days ago) InstallationMedia: Linux Mint 19.2 "Tina" - Release amd64 20190729 NonfreeKernelModules: nvidia_modeset nvidia Package: linux PackageArchitecture: all ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Tags: third-party-packages tina Uname: Linux 5.0.0-32-generic x86_64 UnreportableReason: This is not an official Linux package. Please remove any third pa
[Kernel-packages] [Bug 1850986] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1850986/+attachment/5303819/+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/1850986 Title: many problems: Status in apport package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: 1st Neither ubuntu-bug linux nor sudo ubuntu-bug linux sudo cat /proc/version_signature > version.log sudo lspci -vnvn > lspci-vnvn.log work! 2 Bug reporting is so hard! 3 Cannot find bug reporting section for Linuxmint so as to empart to Ubuntu that the problem is with the Kernels and not the drivers. 4. The bug is with 4K monitors and the Linuxmint OS is continuously trying to load drivers for the screen. Constantly failing. I would gladly report the bug properly if I knew how to. As information is so vague I can't help. Remember that if a novice can't find what he is looking for to fix a bug then there is a guarantee that the novice will never use that system again. Not all users are able to understand all commands if they are not in use every day. That is the case with me. Sadly, I want to use the system but the system is failing it's novices. It's not the fault of the novice if he/she cannot find the relevant information as there is seriously way too much information on any given subject out there. Deciphering it is a minefield of displeasure. Pity ain't it! That is why people are giving up computers. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.2 InstallationDate: Installed on 2019-11-03 (4 days ago) InstallationMedia: Linux Mint 19.2 "Tina" - Release amd64 20190729 NonfreeKernelModules: nvidia_modeset nvidia Package: linux PackageArchitecture: all ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Tags: third-party-packages tina Uname: Linux 5.0.0-32-generic x86_64 UnreportableReason: This is not an official Linux package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.2 InstallationDate: Installed on 2019-11-03 (4 days ago) InstallationMedia: Linux Mint 19.2 "Tina" - Release amd64 20190729 NonfreeKernelModules: nvidia_modeset nvidia Package: linux PackageArchitecture: all ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Tags: third-party-packages tina Uname: Linux 5.0.0-32-generic x86_64 UnreportableReason: This is not an official Linux package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.2 InstallationDate: Installed on 2019-11-03 (4 days ago) InstallationMedia: Linux Mint 19.2 "Tina" - Release amd64 20190729 NonfreeKernelModules: nvidia_modeset nvidia Package: linux PackageArchitecture: all ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Tags: third-party-packages tina Uname: Linux 5.0.0-32-generic x86_64 UnreportableReason: This is not an official Linux package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1850986/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1850986] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1850986/+attachment/5303820/+files/Dependencies.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/1850986 Title: many problems: Status in apport package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: 1st Neither ubuntu-bug linux nor sudo ubuntu-bug linux sudo cat /proc/version_signature > version.log sudo lspci -vnvn > lspci-vnvn.log work! 2 Bug reporting is so hard! 3 Cannot find bug reporting section for Linuxmint so as to empart to Ubuntu that the problem is with the Kernels and not the drivers. 4. The bug is with 4K monitors and the Linuxmint OS is continuously trying to load drivers for the screen. Constantly failing. I would gladly report the bug properly if I knew how to. As information is so vague I can't help. Remember that if a novice can't find what he is looking for to fix a bug then there is a guarantee that the novice will never use that system again. Not all users are able to understand all commands if they are not in use every day. That is the case with me. Sadly, I want to use the system but the system is failing it's novices. It's not the fault of the novice if he/she cannot find the relevant information as there is seriously way too much information on any given subject out there. Deciphering it is a minefield of displeasure. Pity ain't it! That is why people are giving up computers. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.2 InstallationDate: Installed on 2019-11-03 (4 days ago) InstallationMedia: Linux Mint 19.2 "Tina" - Release amd64 20190729 NonfreeKernelModules: nvidia_modeset nvidia Package: linux PackageArchitecture: all ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Tags: third-party-packages tina Uname: Linux 5.0.0-32-generic x86_64 UnreportableReason: This is not an official Linux package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.2 InstallationDate: Installed on 2019-11-03 (4 days ago) InstallationMedia: Linux Mint 19.2 "Tina" - Release amd64 20190729 NonfreeKernelModules: nvidia_modeset nvidia Package: linux PackageArchitecture: all ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Tags: third-party-packages tina Uname: Linux 5.0.0-32-generic x86_64 UnreportableReason: This is not an official Linux package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.2 InstallationDate: Installed on 2019-11-03 (4 days ago) InstallationMedia: Linux Mint 19.2 "Tina" - Release amd64 20190729 NonfreeKernelModules: nvidia_modeset nvidia Package: linux PackageArchitecture: all ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Tags: third-party-packages tina Uname: Linux 5.0.0-32-generic x86_64 UnreportableReason: This is not an official Linux package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1850986/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1850986] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1850986/+attachment/5303822/+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/1850986 Title: many problems: Status in apport package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: 1st Neither ubuntu-bug linux nor sudo ubuntu-bug linux sudo cat /proc/version_signature > version.log sudo lspci -vnvn > lspci-vnvn.log work! 2 Bug reporting is so hard! 3 Cannot find bug reporting section for Linuxmint so as to empart to Ubuntu that the problem is with the Kernels and not the drivers. 4. The bug is with 4K monitors and the Linuxmint OS is continuously trying to load drivers for the screen. Constantly failing. I would gladly report the bug properly if I knew how to. As information is so vague I can't help. Remember that if a novice can't find what he is looking for to fix a bug then there is a guarantee that the novice will never use that system again. Not all users are able to understand all commands if they are not in use every day. That is the case with me. Sadly, I want to use the system but the system is failing it's novices. It's not the fault of the novice if he/she cannot find the relevant information as there is seriously way too much information on any given subject out there. Deciphering it is a minefield of displeasure. Pity ain't it! That is why people are giving up computers. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.2 InstallationDate: Installed on 2019-11-03 (4 days ago) InstallationMedia: Linux Mint 19.2 "Tina" - Release amd64 20190729 NonfreeKernelModules: nvidia_modeset nvidia Package: linux PackageArchitecture: all ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Tags: third-party-packages tina Uname: Linux 5.0.0-32-generic x86_64 UnreportableReason: This is not an official Linux package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.2 InstallationDate: Installed on 2019-11-03 (4 days ago) InstallationMedia: Linux Mint 19.2 "Tina" - Release amd64 20190729 NonfreeKernelModules: nvidia_modeset nvidia Package: linux PackageArchitecture: all ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Tags: third-party-packages tina Uname: Linux 5.0.0-32-generic x86_64 UnreportableReason: This is not an official Linux package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.2 InstallationDate: Installed on 2019-11-03 (4 days ago) InstallationMedia: Linux Mint 19.2 "Tina" - Release amd64 20190729 NonfreeKernelModules: nvidia_modeset nvidia Package: linux PackageArchitecture: all ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Tags: third-party-packages tina Uname: Linux 5.0.0-32-generic x86_64 UnreportableReason: This is not an official Linux package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1850986/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1850986] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1850986/+attachment/5303821/+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/1850986 Title: many problems: Status in apport package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: 1st Neither ubuntu-bug linux nor sudo ubuntu-bug linux sudo cat /proc/version_signature > version.log sudo lspci -vnvn > lspci-vnvn.log work! 2 Bug reporting is so hard! 3 Cannot find bug reporting section for Linuxmint so as to empart to Ubuntu that the problem is with the Kernels and not the drivers. 4. The bug is with 4K monitors and the Linuxmint OS is continuously trying to load drivers for the screen. Constantly failing. I would gladly report the bug properly if I knew how to. As information is so vague I can't help. Remember that if a novice can't find what he is looking for to fix a bug then there is a guarantee that the novice will never use that system again. Not all users are able to understand all commands if they are not in use every day. That is the case with me. Sadly, I want to use the system but the system is failing it's novices. It's not the fault of the novice if he/she cannot find the relevant information as there is seriously way too much information on any given subject out there. Deciphering it is a minefield of displeasure. Pity ain't it! That is why people are giving up computers. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.2 InstallationDate: Installed on 2019-11-03 (4 days ago) InstallationMedia: Linux Mint 19.2 "Tina" - Release amd64 20190729 NonfreeKernelModules: nvidia_modeset nvidia Package: linux PackageArchitecture: all ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Tags: third-party-packages tina Uname: Linux 5.0.0-32-generic x86_64 UnreportableReason: This is not an official Linux package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.2 InstallationDate: Installed on 2019-11-03 (4 days ago) InstallationMedia: Linux Mint 19.2 "Tina" - Release amd64 20190729 NonfreeKernelModules: nvidia_modeset nvidia Package: linux PackageArchitecture: all ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Tags: third-party-packages tina Uname: Linux 5.0.0-32-generic x86_64 UnreportableReason: This is not an official Linux package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.2 InstallationDate: Installed on 2019-11-03 (4 days ago) InstallationMedia: Linux Mint 19.2 "Tina" - Release amd64 20190729 NonfreeKernelModules: nvidia_modeset nvidia Package: linux PackageArchitecture: all ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Tags: third-party-packages tina Uname: Linux 5.0.0-32-generic x86_64 UnreportableReason: This is not an official Linux package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1850986/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1850986] Re: many problems:
Problem occurs when using 5 Port HDMI switcher by Amazon. Works well with everything else except PC. On another note I cannot get my motherboard HDMI or Displayport sockets to work. Why is this? ** Attachment removed: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850986/+attachment/5303815/+files/ProcCpuinfoMinimal.txt ** Attachment removed: "ProcEnviron.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850986/+attachment/5303816/+files/ProcEnviron.txt ** Attachment removed: "Dependencies.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850986/+attachment/5303817/+files/Dependencies.txt ** Attachment removed: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850986/+attachment/5303818/+files/ProcCpuinfoMinimal.txt ** Attachment removed: "ProcEnviron.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850986/+attachment/5303819/+files/ProcEnviron.txt ** Attachment removed: "Dependencies.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850986/+attachment/5303814/+files/Dependencies.txt ** Description changed: 1st Neither ubuntu-bug linux nor sudo ubuntu-bug linux sudo cat /proc/version_signature > version.log sudo lspci -vnvn > lspci-vnvn.log work! 2 Bug reporting is so hard! 3 Cannot find bug reporting section for Linuxmint so as to empart to Ubuntu that the problem is with the Kernels and not the drivers. 4. The bug is with 4K monitors and the Linuxmint OS is continuously trying to load drivers for the screen. Constantly failing. I would gladly report the bug properly if I knew how to. As information is so vague I can't help. Remember that if a novice can't find what he is looking for to fix a bug then there is a guarantee that the novice will never use that system again. Not all users are able to understand all commands if they are not in use every day. That is the case with me. Sadly, I want to use the system but the system is failing it's novices. It's not the fault of the novice if he/she cannot find the relevant information as there is seriously way too much information on any given subject out there. Deciphering it is a minefield of displeasure. Pity ain't it! That is why people are giving up computers. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.2 InstallationDate: Installed on 2019-11-03 (4 days ago) InstallationMedia: Linux Mint 19.2 "Tina" - Release amd64 20190729 NonfreeKernelModules: nvidia_modeset nvidia Package: linux PackageArchitecture: all ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Tags: third-party-packages tina Uname: Linux 5.0.0-32-generic x86_64 UnreportableReason: This is not an official Linux package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.2 InstallationDate: Installed on 2019-11-03 (4 days ago) InstallationMedia: Linux Mint 19.2 "Tina" - Release amd64 20190729 NonfreeKernelModules: nvidia_modeset nvidia Package: linux PackageArchitecture: all ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Tags: third-party-packages tina Uname: Linux 5.0.0-32-generic x86_64 UnreportableReason: This is not an official Linux package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.9 + Architecture: amd64 + CurrentDesktop: X-Cinnamon + DistroRelease: Linux Mint 19.2 + InstallationDate: Installed on 2019-11-03 (4 days ago) + InstallationMedia: Linux Mint 19.2 "Tina" - Release amd64 20190729 + NonfreeKernelModules: nvidia_modeset nvidia + Package: linux + PackageArchitecture: all + ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 + Tags: third-party-packages tina + Uname: Linux 5.0.0-32-generic x86_64 + UnreportableReason: This is not an official Linux package. Please remove any third party package and try again. + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1850986 Title: many problems: Status in apport package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: 1st Neither ubuntu-bug linux nor sudo ubuntu-bug linux sudo c
[Kernel-packages] [Bug 1769792] Re: Keyboard and Touchpad do not work after suspend/resume
Similar here. Touchpad freezes totally after suspend. I'm not sure about the keyboard, as I stay in the graphic environment - I suspect it doesn't quite work either. As for others, only a complete turn off - turn on helps, reboot does not. I have Fujitsu Lifebook E744, this happens with both openSuse Leap 15 and now Kubuntu 19.10, so this isn't distro specific. I have seen recommendation for sudo apt-get install --reinstall xserver-xorg-input-all but it did not solve this issue. Operating System: Kubuntu 19.10 KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.62.0 Qt Version: 5.12.4 Kernel Version: 5.3.0-19-generic OS Type: 64-bit -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1769792 Title: Keyboard and Touchpad do not work after suspend/resume Status in linux package in Ubuntu: Confirmed Bug description: My laptop is a Toshiba Satellite C850D with updated 18.04 installed. When resuming from suspend, I have no keyboard and touchpad. dmesg shows "i8042: Can't reactivate KBD port" This looks like a recurring problem, and is just like these: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1014240 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1142118 Here's the dmesg output from before and after suspending. https://paste.ubuntu.com/p/rsFX9Yw7Xh/ This post also talks about this bit failing for a lot of people! http://lightrush.ndoytchev.com/random-1/i8042quirkoptions Some of the function keys work, such as changing the screen brightness, but the key (fn+F5) does not turn the touchpad back on. I have not yet tried any of the suggested options, as results have been mixed, but I will. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-20-generic 4.15.0-20.21 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon May 7 22:01:26 2018 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1769792/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1851810] [NEW] Some EFI systems fail to boot in efi_init() when booted via maas
Public bug reported: [Impact] Cirtain EFI systems will no longer boot with updated versions of maas. They will still boot in BIOS compatibility mode where available. [Test Case] Affected systems have already been tested with this fix applied and now boot successfully in EFI mode. The key test is does any EFI based system boot with this applied. [Regression Potential] The change increased the headroom by a very small amount, an additional 8 slots. This is very unlikely to lead to additional failures. === When booting via newer versions of maas we use grub extensions to load additional files. This leads the kernel to panic in efi_main(): exit_boot() failed! efi_main() failed! This occurs because the EFI memory map is more fragmented. When we exit boot services that returns an updated memory map in a buffer we supply. This has to be large enough to contain the updated map. If the exit fails because of lack of map space we are dead in the water because the call to allocate memory is lost to us. We therefore add some headroom in the allocation to allow for any expansion during close. This headroom is insufficient. ** Affects: linux (Ubuntu) Importance: High Assignee: Andy Whitcroft (apw) Status: In Progress ** Affects: linux (Ubuntu Bionic) Importance: High Assignee: Andy Whitcroft (apw) Status: In Progress ** Affects: linux (Ubuntu Disco) Importance: High Assignee: Andy Whitcroft (apw) Status: In Progress ** Affects: linux (Ubuntu Eoan) Importance: High Assignee: Andy Whitcroft (apw) Status: In Progress ** Affects: linux (Ubuntu Focal) Importance: High Assignee: Andy Whitcroft (apw) Status: In Progress ** Changed in: linux (Ubuntu) Status: New => In Progress ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Andy Whitcroft (apw) ** Description changed: + [Impact] + + Cirtain EFI systems will no longer boot with updated versions of maas. + They will still boot in BIOS compatibility mode where available. + + [Test Case] + + Affected systems have already been tested with this fix applied and now + boot successfully in EFI mode. The key test is does any EFI based + system boot with this applied. + + [Regression Potential] + + The change increased the headroom by a very small amount, an additional + 8 slots. This is very unlikely to lead to additional failures. + + === + When booting via newer versions of maas we use grub extensions to load additional files. This leads the kernel to panic in efi_main(): - exit_boot() failed! - efi_main() failed! + exit_boot() failed! + efi_main() failed! This occurs because the EFI memory map is more fragmented. When we exit boot services that returns an updated memory map in a buffer we supply. This has to be large enough to contain the updated map. If the exit fails because of lack of map space we are dead in the water because the call to allocate memory is lost to us. We therefore add some headroom in the allocation to allow for any expansion during close. This headroom is insufficient. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1851810 Title: Some EFI systems fail to boot in efi_init() when booted via maas Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Status in linux source package in Disco: In Progress Status in linux source package in Eoan: In Progress Status in linux source package in Focal: In Progress Bug description: [Impact] Cirtain EFI systems will no longer boot with updated versions of maas. They will still boot in BIOS compatibility mode where available. [Test Case] Affected systems have already been tested with this fix applied and now boot successfully in EFI mode. The key test is does any EFI based system boot with this applied. [Regression Potential] The change increased the headroom by a very small amount, an additional 8 slots. This is very unlikely to lead to additional failures. === When booting via newer versions of maas we use grub extensions to load additional files. This leads the kernel to panic in efi_main(): exit_boot() failed! efi_main() failed! This occurs because the EFI memory map is more fragmented. When we exit boot services that returns an updated memory map in a buffer we supply. This has to be large enough to contain the updated map. If the exit fails because of lack of map space we are dead in the water because the call to allocat
[Kernel-packages] [Bug 1851810] Re: Some EFI systems fail to boot in efi_init() when booted via maas
** Also affects: linux (Ubuntu Focal) Importance: High Assignee: Andy Whitcroft (apw) Status: In Progress ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Eoan) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Eoan) Status: New => In Progress ** Changed in: linux (Ubuntu Disco) Status: New => In Progress ** Changed in: linux (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => High ** Changed in: linux (Ubuntu Disco) Importance: Undecided => Critical ** Changed in: linux (Ubuntu Disco) Importance: Critical => High ** Changed in: linux (Ubuntu Eoan) Importance: Undecided => High ** Changed in: linux (Ubuntu Eoan) Assignee: (unassigned) => Andy Whitcroft (apw) ** Changed in: linux (Ubuntu Disco) Assignee: (unassigned) => Andy Whitcroft (apw) ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Andy Whitcroft (apw) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1851810 Title: Some EFI systems fail to boot in efi_init() when booted via maas Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Status in linux source package in Disco: In Progress Status in linux source package in Eoan: In Progress Status in linux source package in Focal: In Progress Bug description: [Impact] Cirtain EFI systems will no longer boot with updated versions of maas. They will still boot in BIOS compatibility mode where available. [Test Case] Affected systems have already been tested with this fix applied and now boot successfully in EFI mode. The key test is does any EFI based system boot with this applied. [Regression Potential] The change increased the headroom by a very small amount, an additional 8 slots. This is very unlikely to lead to additional failures. === When booting via newer versions of maas we use grub extensions to load additional files. This leads the kernel to panic in efi_main(): exit_boot() failed! efi_main() failed! This occurs because the EFI memory map is more fragmented. When we exit boot services that returns an updated memory map in a buffer we supply. This has to be large enough to contain the updated map. If the exit fails because of lack of map space we are dead in the water because the call to allocate memory is lost to us. We therefore add some headroom in the allocation to allow for any expansion during close. This headroom is insufficient. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851810/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1851464] Re: Unable to install X-hwe-edge meta package
** Changed in: ubuntu-kernel-tests 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/1851464 Title: Unable to install X-hwe-edge meta package Status in ubuntu-kernel-tests: Fix Released Status in linux-meta package in Ubuntu: Fix Released Status in linux-meta source package in Xenial: Fix Released Bug description: It works 4 days ago, but now when you try to install the meta package, it will fail with: $ sudo apt install linux-lowlatency-hwe-16.04-edge Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: linux-lowlatency-hwe-16.04-edge : Depends: linux-image-lowlatency-hwe-16.04-edge (= 4.15.0.67.84) but it is not going to be installed Depends: linux-headers-lowlatency-hwe-16.04-edge (= 4.15.0.67.84) but it is not going to be installed E: Unable to correct problems, you have held broken packages. $ sudo apt install linux-generic-hwe-16.04-edge Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: linux-generic-hwe-16.04-edge : Depends: linux-image-generic-hwe-16.04-edge (= 4.15.0.67.84) but it is not going to be installed Depends: linux-headers-generic-hwe-16.04-edge (= 4.15.0.67.84) but it is not going to be installed E: Unable to correct problems, you have held broken packages. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-167-generic 4.4.0-167.196 ProcVersionSignature: User Name 4.4.0-167.196-generic 4.4.197 Uname: Linux 4.4.0-167-generic i686 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 6 06:03 seq crw-rw 1 root audio 116, 33 Nov 6 06:03 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.21 Architecture: i386 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Wed Nov 6 06:38:39 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Dell Inc. PowerEdge R320 PciMultimedia: ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-167-generic root=UUID=7e417b15-9c42-401c-b706-06eb693e6d19 ro RelatedPackageVersions: linux-restricted-modules-4.4.0-167-generic N/A linux-backports-modules-4.4.0-167-generic N/A linux-firmware 1.157.22 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/11/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.4 dmi.board.name: 0DY523 dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.4:bd05/11/2012:svnDellInc.:pnPowerEdgeR320:pvr:rvnDellInc.:rn0DY523:rvrA03:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R320 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1851464/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1850965] Re: bionic/linux-azure-5.3: 5.3.0-1006.6~18.04.1 -proposed tracker
5.3.0-1006.6~18.04.1 - azure Regression test CMPL, RTB. Issue to note in x86_64 (azure): ubuntu_kernel_selftests - cpu-hotplug (bug 1814232) test_bpf in net (bug 1812189) test_blackhole_dev in net (bug 1851619) trace_printk in ftrace (bug 1830084) ftrace failures (bug 1851811) posix_timers (bug 1851805) ubuntu_kvm_unit_tests - ept (bug 1824228) memory (bug 1831449) vmx (bug 1821394) on Standard_F32s_v2 ubuntu_ltp - proc01 (bug 1829849) fs_fill (bug 1842266) ksm06* in mm (bug 1830316) cpuset_hotplug (bug 1834006) memcg_max_usage_in_bytes (bug 1829979) memcg_stat (bug 1829983) memcg_subgroup_charge (bug 1847982) memcg_usage_in_bytes (bug 1829984) memcg_use_hierarchy (bug 1829989) cpuhotplug02 (bug 1836166) cpuhotplug03 (bug 1836167) cpuhotplug04 (bug 1836169) cpuhotplug06 (bug 1836170) getaddrinfo_01 (bug 1829995) cve-2017-17053 (bug 1830011) crypto_user02 (bug 1837543) ubuntu_ltp_syscalls - msgstress03 (bug 1797341) msgstress04 (bug 1797348) ubuntu_lttng_smoke_test - module failed to build on B-5.3 (bug 1844764) ubuntu_lxc - lxc-test-no-new-privs (failed to fetch package) on Standard_DS15_v2, Standard_DS5_v2 (bug 1821152), passed on the rest ubuntu_qrt_kernel_security - test_140_kernel_modules_not_tainted (bug 1850888) ubuntu_sysdig_smoke_test - failed to build sysdig DKMS with 5.3 kernel (bug 1844766) Skipped / blacklisted: * libhugetlbfs ** Changed in: kernel-sru-workflow/regression-testing Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Assignee: Canonical Kernel Team (canonical-kernel-team) => Po-Hsu Lin (cypressyew) ** Tags added: regression-testing-passed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1850965 Title: bionic/linux-azure-5.3: 5.3.0-1006.6~18.04.1 -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-lrm 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: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid 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: 1850480 packages: lrm: linux-restricted-modules-azure-5.3 main: linux-azure-5.3 meta: linux-meta-azure-5.3 signed: linux-signed-azure-5.3 phase: Testing phase-changed: Tuesday, 05. November 2019 23:31 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED stakeholder-signoff: Stalled -- waiting for signoff variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1850965/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1851464] Re: Unable to install X-hwe-edge meta package
** Package changed: linux (Ubuntu) => linux-meta (Ubuntu) ** Changed in: linux-meta (Ubuntu) Status: Confirmed => Fix Released ** Changed in: linux-meta (Ubuntu Xenial) Status: Confirmed => Fix Released ** Changed in: linux-meta (Ubuntu) Assignee: (unassigned) => Kleber Sacilotto de Souza (kleber-souza) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/1851464 Title: Unable to install X-hwe-edge meta package Status in ubuntu-kernel-tests: Fix Released Status in linux-meta package in Ubuntu: Fix Released Status in linux-meta source package in Xenial: Fix Released Bug description: It works 4 days ago, but now when you try to install the meta package, it will fail with: $ sudo apt install linux-lowlatency-hwe-16.04-edge Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: linux-lowlatency-hwe-16.04-edge : Depends: linux-image-lowlatency-hwe-16.04-edge (= 4.15.0.67.84) but it is not going to be installed Depends: linux-headers-lowlatency-hwe-16.04-edge (= 4.15.0.67.84) but it is not going to be installed E: Unable to correct problems, you have held broken packages. $ sudo apt install linux-generic-hwe-16.04-edge Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: linux-generic-hwe-16.04-edge : Depends: linux-image-generic-hwe-16.04-edge (= 4.15.0.67.84) but it is not going to be installed Depends: linux-headers-generic-hwe-16.04-edge (= 4.15.0.67.84) but it is not going to be installed E: Unable to correct problems, you have held broken packages. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-167-generic 4.4.0-167.196 ProcVersionSignature: User Name 4.4.0-167.196-generic 4.4.197 Uname: Linux 4.4.0-167-generic i686 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 6 06:03 seq crw-rw 1 root audio 116, 33 Nov 6 06:03 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.21 Architecture: i386 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Wed Nov 6 06:38:39 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Dell Inc. PowerEdge R320 PciMultimedia: ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-167-generic root=UUID=7e417b15-9c42-401c-b706-06eb693e6d19 ro RelatedPackageVersions: linux-restricted-modules-4.4.0-167-generic N/A linux-backports-modules-4.4.0-167-generic N/A linux-firmware 1.157.22 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/11/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.4 dmi.board.name: 0DY523 dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.4:bd05/11/2012:svnDellInc.:pnPowerEdgeR320:pvr:rvnDellInc.:rn0DY523:rvrA03:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R320 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1851464/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1850965] Re: bionic/linux-azure-5.3: 5.3.0-1006.6~18.04.1 -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: 1850480 packages: lrm: linux-restricted-modules-azure-5.3 main: linux-azure-5.3 meta: linux-meta-azure-5.3 signed: linux-signed-azure-5.3 phase: Testing phase-changed: Tuesday, 05. November 2019 23:31 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED - regression-testing: Ongoing -- testing in progress stakeholder-signoff: Stalled -- waiting for signoff variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1850965 Title: bionic/linux-azure-5.3: 5.3.0-1006.6~18.04.1 -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-lrm 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: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid 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: 1850480 packages: lrm: linux-restricted-modules-azure-5.3 main: linux-azure-5.3 meta: linux-meta-azure-5.3 signed: linux-signed-azure-5.3 phase: Testing phase-changed: Tuesday, 05. November 2019 23:31 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED stakeholder-signoff: Stalled -- waiting for signoff variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1850965/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838610] Re: The 3.13 kernel for Precise ESM does not provide the expected version number
** Also affects: linux (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Precise) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Precise) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Trusty) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1838610 Title: The 3.13 kernel for Precise ESM does not provide the expected version number Status in ubuntu-kernel-tests: Fix Released Status in linux package in Ubuntu: Confirmed Status in linux source package in Precise: New Status in linux source package in Trusty: New Bug description: The linux-generic-lts-trusty meta package on Precise will give you: linux-base linux-headers-3.13.0-172 linux-headers-3.13.0-172-generic linux-headers-generic-lts-trusty linux-image-3.13.0-172-generic linux-image-generic-lts-trusty linux-modules-3.13.0-172-generic And the kernel version returned from uname -a shows: Linux precise-testing 3.13.0-172-generic #1-Ubuntu SMP Sat Jul 6 10:46:56 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux This is breaking the automation as we're expecting the kernel version: 3.13.0-172.223~12.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1838610/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1849855] Re: bionic/linux: 4.15.0-68.77 -proposed tracker
Kernel deb testing completes, no regressions found. Ready for Updates. Results here: https://trello.com/c/bO6FlHQj/225-bionic-linux- image-4150-68-generic-4150-6877 ** Changed in: kernel-sru-workflow/certification-testing Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1849855 Title: bionic/linux: 4.15.0-68.77 -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-lrm 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: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed 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 bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Tuesday, 29. October 2019 13:37 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: verification-testing: Ongoing -- testing in progress trackers: bionic/linux-aws: bug 1849016 bionic/linux-fips: bug 1849023 bionic/linux-gke-4.15: bug 1849018 bionic/linux-ibm-gt: bug 1849020 bionic/linux-kvm: bug 1849019 bionic/linux-oem: bug 1851507 bionic/linux-oracle: bug 1849022 bionic/linux-raspi2: bug 1849008 bionic/linux-snapdragon: bug 1849011 bionic/linux/pc-kernel: bug 1849852 bionic/linux/pc-lowlatency-kernel: bug 1849853 unknown/unknown: bug 1849854 xenial/linux-azure: bug 1849027 xenial/linux-gcp: bug 1849031 xenial/linux-hwe: bug 1849854 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1849855/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1849855] Re: bionic/linux: 4.15.0-68.77 -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 bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Tuesday, 29. October 2019 13:37 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - certification-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress trackers: bionic/linux-aws: bug 1849016 bionic/linux-fips: bug 1849023 bionic/linux-gke-4.15: bug 1849018 bionic/linux-ibm-gt: bug 1849020 bionic/linux-kvm: bug 1849019 bionic/linux-oem: bug 1851507 bionic/linux-oracle: bug 1849022 bionic/linux-raspi2: bug 1849008 bionic/linux-snapdragon: bug 1849011 bionic/linux/pc-kernel: bug 1849852 bionic/linux/pc-lowlatency-kernel: bug 1849853 unknown/unknown: bug 1849854 xenial/linux-azure: bug 1849027 xenial/linux-gcp: bug 1849031 xenial/linux-hwe: bug 1849854 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1849855 Title: bionic/linux: 4.15.0-68.77 -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-lrm 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: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed 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 bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Tuesday, 29. October 2019 13:37 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: verification-testing: Ongoing -- testing in progress trackers: bionic/linux-aws: bug 1849016 bionic/linux-fips: bug 1849023 bionic/linux-gke-4.15: bug 1849018 bionic/linux-ibm-gt: bug 1849020 bionic/linux-kvm: bug 1849019 bionic/linux-oem: bug 1851507 bionic/linux-oracle: bug 1849022 bionic/linux-raspi2: bug 1849008 bionic/linux-snapdragon: bug 1849011 bionic/linux/pc-kernel: bug 1849852 bionic/linux/pc-lowlatency-kernel: bug 1849853 unknown/unknown: bug 1849854 xenial/linux-azure: bug 1849027 xenial/linux-gcp: bug 1849031 xenial/linux-hwe: bug 1849854 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1849855/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1851829] Re: kernel trace found with ubuntu_bpf test on Eoan s390x LPAR
This can be reproduced with 5.3.0-20 on the same node as well: WARNING: CPU: 1 PID: 2799 at mm/page_alloc.c:4702 __alloc_pages_nodemask+0x25e/0x318 Modules linked in: xt_conntrack ipt_REJECT nf_reject_ipv4 ip6table_mangle ip6table_nat nf_tables nfnetlink ip6table_filter ip6_tables iptable_mangle xt_CHECKSUM iptable_nat xt_MASQUERADE xt_tcpudp bridge iptable_filter bpfilter aufs overlay 8021q garp stp mrp llc openvswitch nsh nf_conncount nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 binfmt_misc zfs(PO) zunicode(PO) zavl(PO) icp(PO) zlua(PO) zcommon(PO) znvpair(PO) spl(O) genwqe_card crc_itu_t chsc_sch eadm_sch ctcm fsm vfio_ccw vfio_mdev mdev vfio_iommu_type1 vfio sch_fq_codel nfsd auth_rpcgss nfs_acl lockd grace sunrpc ip_tables x_tables btrfs zstd_compress zlib_deflate raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 linear dm_service_time pkey zcrypt crc32_vx_s390 ghash_s390 prng aes_s390 mlx4_ib ib_uverbs mlx4_en qeth_l2 des_s390 des_generic ptp pps_core ib_core sha512_s390 sha256_s390 sha1_s390 sha_common mlx4_core zfcp scsi_transport_fc qeth qdio ccwgroup dasd_eckd_mod dasd_mod scsi_dh_emc scsi_dh_rdac scsi_dh_alua dm_multipath CPU: 1 PID: 2799 Comm: test_verifier Tainted: P O 5.3.0-20-generic #21-Ubuntu Hardware name: IBM 2964 N63 400 (LPAR) Krnl PSW : 0704c0018000 0002ec206c9e (__alloc_pages_nodemask+0x25e/0x318) R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:0 PM:0 RI:0 EA:3 Krnl GPRS: da15f4fd64a5a47d 00040dc0 00040dc0 000a 000a 0002ec00c6b8 003d0900 0dc0 03e00a16b000 03e00a16b000 0003a6c2 02aa09e798e0 03e00279bb28 03e00279baa8 Krnl Code: 0002ec206c92: a7212000 tmll%r2,8192 0002ec206c96: a774ff87 brc 7,2ec206ba4 #0002ec206c9a: a7f40001 brc 15,2ec206c9c >0002ec206c9e: a789 lghi%r8,0 0002ec206ca2: a7f4ff83 brc 15,2ec206ba8 0002ec206ca6: a718 lhi %r1,0 0002ec206caa: a7f4ff1b brc 15,2ec206ae0 0002ec206cae: e3100344 lg %r1,832 Call Trace: ([<03e00279bb88>] 0x3e00279bb88) [<0002ec1d33a0>] kmalloc_order_trace+0x40/0x100 [<0002ec00c6b8>] bpf_int_jit_compile+0x70/0x240 [<0002ec1568ce>] bpf_prog_select_runtime+0x13e/0x190 [<0002ec15a14c>] bpf_prog_load+0x2dc/0x6a8 [<0002ec15aca6>] __do_sys_bpf+0x78e/0x10c0 [<0002ec856228>] system_call+0xdc/0x2c8 Last Breaking-Event-Address: [<0002ec206c9a>] __alloc_pages_nodemask+0x25a/0x318 ---[ end trace d7b63e2466552ed4 ]--- ** Tags added: 5.3 eoan s390x sru-20191021 ubuntu-bpf ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Eoan) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1851829 Title: kernel trace found with ubuntu_bpf test on Eoan s390x LPAR Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: New Status in linux source package in Eoan: New Bug description: This trace can be seen right after you started the test on s390x LPAR. ** ** NOTICE NOTICE NOTICE NOTICE NOTICE NOTICE NOTICE ** ** ** ** trace_printk() being used. Allocating extra memory. ** ** ** ** This means that this is a DEBUG kernel and it is ** ** unsafe for production use. ** ** ** ** If you see this message and you are not debugging** ** the kernel, report this immediately to your vendor! ** ** ** ** NOTICE NOTICE NOTICE NOTICE NOTICE NOTICE NOTICE ** ** WARNING: CPU: 0 PID: 3159 at mm/page_alloc.c:4702 __alloc_pages_nodemask+0x25e/0x318 Modules linked in: xt_conntrack ipt_REJECT nf_reject_ipv4 ip6table_mangle ip6table_nat nf_tables nfnetlink ip6table_filter ip6_tables iptable_mangle xt_CHECKSUM iptable_nat xt_MASQUERADE xt_tcpudp bridge iptable_filter bpfilter aufs overlay 8021q garp stp mrp llc openvswitch nsh nf_conncount nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 binfmt_misc zfs(PO) zunicode(PO) zavl(PO) icp(PO) zlua(PO) zcommon(PO) znvpair(PO) spl(O) genwqe_card crc_itu_t chsc_sch eadm_sch ctcm fsm vfio_ccw vfio_mdev mdev vfio_iommu_type1 vfio sch_fq_codel nfsd auth_rpcgss
[Kernel-packages] [Bug 1850486] Re: eoan/linux: 5.3.0-21.22 -proposed tracker
5.3.0-21.22 - generic Regression test CMPL, RTB. Issue to note in amd64: ubuntu_kernel_selftests - seccomp build issue (bug 1849844) ubuntu_kvm_unit_tests - realmode failed (bug 1850653) ubuntu_ltp - proc01 (bug 1829849) fs_fill (bug 1842266) memcg_max_usage_in_bytes (bug 1829979) memcg_stat (bug 1829983) memcg_use_hierarchy (bug 1829989) memcg_usage_in_bytes (bug 1829984) cpuset_hotplug (bug 1834006) getaddrinfo_01 (bug 1829995) crypto_user02 (bug 1837543) ubuntu_ltp_syscalls - fallocate04, fallocate05, fdatasync03, fremovexattr01, fremovexattr02, fsync01, fsync04, msync04, preadv03, preadv03_64, preadv203, preadv203_64, pwritev03, pwritev03_64, sync03, syncfs01, sync_file_range02, copy_file_range01, statx04 (bug 1842266) fsetxattr01, fgetxattr01, fanotify13, fanotify14, lremovexattr01, setxattr01 (bug 1842266) ubuntu_sysdig_smoke_test - test failed on Eoan (bug 1844493) ubuntu_xfstests_btrfs - generic/166 time out ubuntu_xfstests_ext4 - generic/476 time out ubuntu_xfstests_xfs - generic/438 time out 51 / 54 tests were run, missing: ubuntu_xfstests_btrfs, ubuntu_xfstests_ext4, ubuntu_xfstests_xfs Issue to note in arm64: hwclock - issue for HP m400 (bug 1716603) ubuntu_bpf - Failed sockmap unexpected timeout on ARM64 (bug 1805806) ubuntu_kvm_unit_tests - gicv2-mmio-up and gicv2-mmio-3p failed on Moonshot ARM64 (bug 1802492) ubuntu_ltp - proc01 (bug 1829849) fs_fill (bug 1842266) memcg_stat (bug 1829983) memcg_use_hierarchy (bug 1829989) cpuhotplug03 (bug 1836167) cpuhotplug04 (bug 1836169) cpuhotplug06 (bug 1836170) crypto_user02 (bug 1837543) ubuntu_ltp_syscalls - fallocate04, fallocate05, fdatasync03, fremovexattr01, fremovexattr02, fsync01, fsync04, msync04, preadv03, preadv03_64, preadv203, preadv203_64, pwritev03, pwritev03_64, sync03, syncfs01, sync_file_range02, copy_file_range01, statx04 (bug 1842266) fsetxattr01, fgetxattr01, fanotify13, fanotify14, lremovexattr01, setxattr01 (bug 1842266) 53 / 56 tests were run, missing: ubuntu_xfstests_btrfs, ubuntu_xfstests_ext4, ubuntu_xfstests_xfs Issue to note in ppc64le (P9): hwclock - hwclock test failed on Power9 due to 0.x sec differences / time out waiting for time change (bug 1802233) ubuntu_ltp - proc01 (bug 1829849) ksm06* in mm (bug 1830316) memcg_stat (bug 1829983) memcg_use_hierarchy (bug 1829989) cpuset_base_ops cpuset_exclusive cpuset_hierarchy cpuset_hotplug cpuset_inherit cpuset_load_balance cpuset_memory cpuset_memory_pressure cpuset_memory_spread cpuset_sched_domains cpuset_syscall in controller (bug 1836188) crypto_user02 (bug 1837543) ubuntu_ltp_syscalls - fallocate04, fallocate05, fdatasync03, fremovexattr01, fremovexattr02, fsync01, fsync04, msync04, preadv03, preadv03_64, preadv203, preadv203_64, pwritev03, pwritev03_64, sync03, syncfs01, sync_file_range02, copy_file_range01, statx04 (bug 1842266) fallocate05 (bug 1783880) fsetxattr01, fgetxattr01, fanotify13, fanotify14, lremovexattr01, setxattr01 (bug 1842266) stime (bug 1845620) ubuntu_lxc - Failed to download image index (bug 1839835) ubuntu_sysdig_smoke_test - test failed on Eoan (bug 1844493) 51 / 52 tests were run, missing: ubuntu_ltp_syscalls Issue to note in s390x (KVM): ubuntu_bpf - test_verifier failed with 'Failed to load prog' on D s390x (bug 1812176) ubuntu_ltp - proc01 (bug 1829849) fs_fill (bug 1842266) memcg_stat (bug 1829983) memcg_use_hierarchy (bug 1829989) cpuacct_100_100 (bug 1829978) cpuset_hotplug (bug 1834006) getaddrinfo_01 (bug 1829995) ubuntu_sysdig_smoke_test - test failed on Eoan (bug 1844493) 49 / 52 tests were run, missing: ubuntu_bpf, ubuntu_kvm_unit_tests, ubuntu_vfat_stress Issue to note in s390x (Ubuntu on LPAR): ubuntu_bpf - kernel traces found with the test (bug 1851829) ubuntu_ltp - proc01 (bug 1829849) fs_fill (bug 1842266) memcg_stat (bug 1829983) memcg_use_hierarchy (bug 1829989) cpuset_inherit (bug 1849825) cpuset_hotplug (bug 1834006) getaddrinfo_01 (bug 1829995) ubuntu_qrt_kernel_security - test_140_kernel_modules_not_tainted (bug 1850888) ubuntu_sysdig_smoke_test - Failed on 5.3 (bug 1844493) Issue to note in s390x (zVM): ubuntu_bpf - test_verifier failed with 'Failed to load prog' on D s390x (bug 1812176) ubuntu_kvm_unit_tests - skey failed (bug 1778705) ubuntu_ltp - proc01 (bug 1829849) memcg_max_usage_in_bytes (bug 1829979) memcg_stat (bug 1829983) memcg_use_hierarchy (bug 1829989) cpuacct_100_100 (bug 1829978) cpuset_inherit (bug 1849825) cpuset_hotplug (bug 1834006) ubuntu_ltp_syscalls - fsetxattr01, fgetxattr01, fanotify13, fanotify14, lremovexattr01, setxattr01 (bug 1842266) ubuntu_lxc - Container "reboot" is defined (bug 1788574) ubuntu_qrt_kernel_security - test_140_kernel_modules_not_tainted (bug 1850888) ubuntu_sysdig_smoke_test - Failed on 5.3 (bug 1844493) * Note: missing P8 test result in this cycle, but it's okay as wel still have another PowerPC fully tested (P9) * Note: s390x LPAR test result incomplete due to bug 18
[Kernel-packages] [Bug 1850486] Re: eoan/linux: 5.3.0-21.22 -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 bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Wednesday, 30. October 2019 18:13 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress - regression-testing: Ongoing -- testing in progress trackers: bionic/linux-hwe-edge: bug 1850485 eoan/linux-aws: bug 1850477 eoan/linux-azure: bug 1850480 eoan/linux-gcp: bug 1850481 eoan/linux-kvm: bug 1850482 eoan/linux-oracle: bug 1850483 eoan/linux-raspi2: bug 1850896 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1850486 Title: eoan/linux: 5.3.0-21.22 -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: In Progress Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm 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: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Eoan: Confirmed 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 bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Wednesday, 30. October 2019 18:13 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress trackers: bionic/linux-hwe-edge: bug 1850485 eoan/linux-aws: bug 1850477 eoan/linux-azure: bug 1850480 eoan/linux-gcp: bug 1850481 eoan/linux-kvm: bug 1850482 eoan/linux-oracle: bug 1850483 eoan/linux-raspi2: bug 1850896 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1850486/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1851829] 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 1851829
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.
** Changed in: linux (Ubuntu)
Status: New => Incomplete
** Changed in: linux (Ubuntu Eoan)
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/1851829
Title:
kernel trace found with ubuntu_bpf test on Eoan s390x LPAR
Status in ubuntu-kernel-tests:
New
Status in linux package in Ubuntu:
Incomplete
Status in linux source package in Eoan:
Incomplete
Bug description:
This trace can be seen right after you started the test on s390x LPAR.
**
** NOTICE NOTICE NOTICE NOTICE NOTICE NOTICE NOTICE **
** **
** trace_printk() being used. Allocating extra memory. **
** **
** This means that this is a DEBUG kernel and it is **
** unsafe for production use. **
** **
** If you see this message and you are not debugging**
** the kernel, report this immediately to your vendor! **
** **
** NOTICE NOTICE NOTICE NOTICE NOTICE NOTICE NOTICE **
**
WARNING: CPU: 0 PID: 3159 at mm/page_alloc.c:4702
__alloc_pages_nodemask+0x25e/0x318
Modules linked in: xt_conntrack ipt_REJECT nf_reject_ipv4 ip6table_mangle
ip6table_nat nf_tables nfnetlink ip6table_filter ip6_tables iptable_mangle
xt_CHECKSUM iptable_nat xt_MASQUERADE xt_tcpudp bridge iptable_filter bpfilter
aufs overlay 8021q garp stp mrp llc openvswitch nsh nf_conncount nf_nat
nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 binfmt_misc zfs(PO) zunicode(PO)
zavl(PO) icp(PO) zlua(PO) zcommon(PO) znvpair(PO) spl(O) genwqe_card crc_itu_t
chsc_sch eadm_sch ctcm fsm vfio_ccw vfio_mdev mdev vfio_iommu_type1 vfio
sch_fq_codel nfsd auth_rpcgss nfs_acl lockd grace sunrpc ip_tables x_tables
btrfs zstd_compress zlib_deflate raid10 raid456 async_raid6_recov async_memcpy
async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 linear
dm_service_time pkey zcrypt crc32_vx_s390 ghash_s390 prng mlx4_en mlx4_ib
ib_uverbs aes_s390 ib_core ptp pps_core qeth_l2 des_s390 des_generic
sha512_s390 sha256_s390 sha1_s390 sha_common mlx4_core zfcp scsi_transport_fc
qeth qdio ccwgroup
dasd_eckd_mod dasd_mod scsi_dh_emc scsi_dh_rdac scsi_dh_alua dm_multipath
CPU: 0 PID: 3159 Comm: test_verifier Tainted: P O
5.3.0-21-generic #22-Ubuntu
Hardware name: IBM 2964 N63 400 (LPAR)
Krnl PSW : 0704c0018000 0002fb832c9e
(__alloc_pages_nodemask+0x25e/0x318)
R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:0 PM:0 RI:0 EA:3
Krnl GPRS: 0003b7efcac0 00040dc0 00040dc0
000a
000a
0002fb6386b8
003d0900 0dc0 03e00b067000
03e00b067000
0003a57a8000 02aa0d1b28e0 03e002b6bb28
03e002b6baa8
Krnl Code: 0002fb832c92: a7212000tmll%r2,8192
0002fb832c96: a774ff87brc 7,2fb832ba4
#0002fb832c9a: a7f40001brc 15,2fb832c9c
>0002fb832c9e: a789lghi%r8,0
0002fb832ca2: a7f4ff83brc 15,2fb832ba8
0002fb832ca6: a718lhi %r1,0
0002fb832caa: a7f4ff1bbrc 15,2fb832ae0
0002fb832cae: e3100344lg %r1,832
Call Trace:
([<03e002b6bb88>] 0x3e002b6bb88)
[<0002fb7ff3a0>] kmalloc_order_trace+0x40/0x100
[<0002fb6386b8>] bpf_int_jit_compile+0x70/0x240
[<0002fb7828ce>] bpf_prog_select_runtime+0x13e/0x190
[<0002fb78614c>] bpf_prog_load+0x2dc/0x6a8
[<0002fb786ca6>] __do_sys_bpf+0x78e/0x10c0
[<0002fbe82228>] system_call+0xdc/0x2c8
Last Breaking-Event-Address:
[<0002fb832c9a>] __alloc_pages_nodemask+0x25a/0x318
---[ end trace 1d8b7179967b64ff ]---
The test itself will get killed with oom-killer later, thus generating
a return code 137 for the test.
All the following tests in this
[Kernel-packages] [Bug 1841955] Re: Can't upgrade kernel on raspberry pi3a+
This bug was fixed in the package flash-kernel - 3.98ubuntu6 --- flash-kernel (3.98ubuntu6) focal; urgency=medium * Remove redundant DTB-Kernel-Version field * Remove redundant copying of boot dtb * Fix mkimage_kernel tests * Add "pi" value for the "Method" field which copies all dtbs and overlays to the boot partition and provides defaults for the boot paths of the kernel, initrd, and u-boot script. This fixes upgrades to support the Pi 4 on Bionic (LP: #1850678) * Update pi bootscript to support all flash-kernel vars, including calculated devtype and partition for future USB boot support * Add entry for Raspberry Pi 3A+ (LP: #1841955) -- Dave Jones Thu, 07 Nov 2019 14:02:26 + ** Changed in: flash-kernel (Ubuntu) Status: In Progress => Fix Released -- 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/1841955 Title: Can't upgrade kernel on raspberry pi3a+ Status in flash-kernel package in Ubuntu: Fix Released Status in linux-raspi2 package in Ubuntu: New Status in flash-kernel source package in Bionic: New Status in linux-raspi2 source package in Bionic: New Bug description: Can't upgrade kernel on raspberry pi3b+ [Steps to Reproduce] 1. dd the image in an SD card: http://cdimage.ubuntu.com/ubuntu/releases/18.04/release/ubuntu-18.04.3-preinstalled-server-armhf+raspi3.img.xz 2. Boot rpi3a+ with the sd card 3. Upgrade the kernel using following command: sudo apt update sudo apt install linux-raspi2 4. Check output message [Expected Result] Current stable kernel(4.15.0-1043-raspi2) is installed. [Actual Result] Error shows up during the installation, and the kernel is still the original one after reboot. [Additional Info] Command output: ubuntu@ubuntu:~$ sudo apt install linux-raspi2 Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: linux-headers-4.15.0-1043-raspi2 linux-headers-raspi2 linux-image-4.15.0-1043-raspi2 linux-image-raspi2 linux-modules-4.15.0-1043-raspi2 linux-raspi2-headers-4.15.0-1043 Suggested packages: fdutils linux-raspi2-doc-4.15.0 | linux-raspi2-source-4.15.0 linux-raspi2-tools The following NEW packages will be installed: linux-headers-4.15.0-1043-raspi2 linux-image-4.15.0-1043-raspi2 linux-modules-4.15.0-1043-raspi2 linux-raspi2-headers-4.15.0-1043 The following packages will be upgraded: linux-headers-raspi2 linux-image-raspi2 linux-raspi2 3 upgraded, 4 newly installed, 0 to remove and 16 not upgraded. Need to get 45.1 MB of archives. After this operation, 214 MB of additional disk space will be used. Do you want to continue? [Y/n] Get:1 http://ports.ubuntu.com/ubuntu-ports bionic-updates/universe armhf linux-raspi2-headers-4.15.0-1043 armhf 4.15.0-1043.46 [11.0 MB] Get:2 http://ports.ubuntu.com/ubuntu-ports bionic-updates/universe armhf linux-headers-4.15.0-1043-raspi2 armhf 4.15.0-1043.46 [852 kB] Get:3 http://ports.ubuntu.com/ubuntu-ports bionic-updates/universe armhf linux-modules-4.15.0-1043-raspi2 armhf 4.15.0-1043.46 [26.5 MB] Get:4 http://ports.ubuntu.com/ubuntu-ports bionic-updates/universe armhf linux-image-4.15.0-1043-raspi2 armhf 4.15.0-1043.46 [6,751 kB] Get:5 http://ports.ubuntu.com/ubuntu-ports bionic-updates/universe armhf linux-raspi2 armhf 4.15.0.1043.41 [1,884 B] Get:6 http://ports.ubuntu.com/ubuntu-ports bionic-updates/universe armhf linux-image-raspi2 armhf 4.15.0.1043.41 [2,524 B] Get:7 http://ports.ubuntu.com/ubuntu-ports bionic-updates/universe armhf linux-headers-raspi2 armhf 4.15.0.1043.41 [2,512 B] Fetched 45.1 MB in 19s (2,363 kB/s) Selecting previously unselected package linux-raspi2-headers-4.15.0-1043. (Reading database ... 62492 files and directories currently installed.) Preparing to unpack .../0-linux-raspi2-headers-4.15.0-1043_4.15.0-1043.46_armhf.deb ... Unpacking linux-raspi2-headers-4.15.0-1043 (4.15.0-1043.46) ... Selecting previously unselected package linux-headers-4.15.0-1043-raspi2. Preparing to unpack .../1-linux-headers-4.15.0-1043-raspi2_4.15.0-1043.46_armhf.deb ... Unpacking linux-headers-4.15.0-1043-raspi2 (4.15.0-1043.46) ... Selecting previously unselected package linux-modules-4.15.0-1043-raspi2. Preparing to unpack .../2-linux-modules-4.15.0-1043-raspi2_4.15.0-1043.46_armhf.deb ... Unpacking linux-modules-4.15.0-1043-raspi2 (4.15.0-1043.46) ... Selecting previously unselected package linux-image-4.15.0-1043-raspi2. Preparing to unpack .../3-linux-image-4.15.0-1043-raspi2_4.15.0-1043.46_armhf.deb ... Unpacking linux-image-4.15.0-1043-raspi2 (4.15.0-1043.46) ... Preparing to unpack .../4-linux-raspi2_4.15.0.1043.41_armhf.deb ... Unpacking linux-raspi2 (4.15.0.1043.41) over (4.15.0.1041.39) ... Preparing to unpack .../5
[Kernel-packages] [Bug 1833905] Re: settimeofday01 in ubuntu_ltp_syscalls failed on KVM kernels
I tried different combinations of host/guest kernels, but I don't see this issue. Are "KVM node" and "KVM host" referred in comment #5 different? -- 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/1833905 Title: settimeofday01 in ubuntu_ltp_syscalls failed on KVM kernels Status in ubuntu-kernel-tests: New Status in linux-kvm package in Ubuntu: New Bug description: Issue found on C-KVM, from the test case content, these two tests are: * Call settimeofday and verify the time was changed. * Call settimeofday with invalid Args and verify that the call fails. <<>> tag=settimeofday01 stime=1561358482 cmdline="settimeofday01" contacts="" analysis=exit <<>> settimeofday011 TFAIL : settimeofday01.c:124: Test condition 1 failed settimeofday012 TPASS : Test condition 2 successful <<>> initiation_status="ok" duration=0 termination_type=exited termination_id=1 corefile=no cutime=0 cstime=0 <<>> ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-1015-kvm 4.18.0-1015.15 ProcVersionSignature: User Name 4.18.0-1015.15-kvm 4.18.20 Uname: Linux 4.18.0-1015-kvm x86_64 ApportVersion: 2.20.10-0ubuntu13.3 Architecture: amd64 Date: Mon Jun 24 06:41:26 2019 SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1833905/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1850738] Re: Intel Bluetooth AX201 HarrisonPeak (HrP) firmware causes system hang in deep suspend
Hello You-Sheng, or anyone else affected, Accepted linux-firmware into disco-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux- firmware/1.178.6 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-disco to verification-done-disco. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-disco. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: linux-firmware (Ubuntu Disco) Status: In Progress => Fix Committed -- 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/1850738 Title: Intel Bluetooth AX201 HarrisonPeak (HrP) firmware causes system hang in deep suspend Status in OEM Priority Project: Confirmed Status in linux-firmware package in Ubuntu: New Status in linux-firmware source package in Bionic: Fix Committed Status in linux-firmware source package in Disco: Fix Committed Bug description: When system has been paired with BLE devices, bluetooth firmware may fail to suspend, or even hangs the whole system that it can only be rebooted with SysRq keys. [Reproduce steps]: 1. pair with BLE devices. They doesn't have to stay connected/powered on during the test. 2. make sure Bluetooth is now receiving LE ADV broadcats, which should leave messages in dmesg like: Bluetooth: hci0: advertising data len corrected 3. suspend the system a few times. With 5.0.0-1025-oem-osp1 kernel, symptoms would usually appear in <= 5 times. [Results] 1. one may observed following errors in between the suspend messages: PM: pci_pm_suspend(): hcd_pci_suspend+0x0/0x30 returns -16 PM: dpm_run_callback(): pci_pm_suspend+0x0/0x150 returns -16 PM: Device :00:14.0 failed to suspend async: error -16 PM: Some devices failed to suspend, or early wake event detected where :00:14.0 is the xHCI Usb hub. 2. with or without above error messages appear first, system may hang and leave only "PM: suspend entry (deep)" in the syslog. [Notes] * kernels newer than v5.2.1, inclusive of latest v5.4-rc5, still have those PM suspend errors, but they doesn't seem to cause system block. Instead, they may resume immediately. * this was found on one platform with Intel Dual Band Wireless AC 9462 [8086:02f0] subsystem id [8086:42a4], linux-firmware 1.173.11 with intel/ibt-19-0-0.sfi REL0282. However, it's not reproducible on another platform with same hw/fw/kernel configuration. kernel: [ 78.136285] PM: suspend entry (deep) kernel: [ 78.139836] Filesystems sync: 0.003 seconds kernel: [ 78.140461] Freezing user space processes ... (elapsed 0.002 seconds) done. kernel: [ 78.142669] OOM killer disabled. kernel: [ 78.142669] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. kernel: [ 78.143875] printk: Suspending console(s) (use no_console_suspend to debug) kernel: [ 78.335256] sof-audio-pci :00:1f.3: error: no reply expected, received 0x0 kernel: [ 78.457675] sof-audio-pci :00:1f.3: firmware boot complete kernel: [ 78.460486] PM: pci_pm_suspend(): hcd_pci_suspend+0x0/0x30 returns -16 kernel: [ 78.460494] PM: dpm_run_callback(): pci_pm_suspend+0x0/0x150 returns -16 kernel: [ 78.460497] PM: Device :00:14.0 failed to suspend async: error -16 kernel: [ 78.567263] PM: Some devices failed to suspend, or early wake event detected kernel: [ 78.580871] sof-audio-pci :00:1f.3: error: no reply expected, received 0x0 kernel: [ 78.713018] sof-audio-pci :00:1f.3: firmware boot complete kernel: [ 78.733982] Bluetooth: hci0: advertising data len corrected kernel: [ 78.792707] nvme nvme0: Shutdown timeout set to 8 seconds kernel: [ 78.841602] nvme nvme0: 8/0/0 default/read/poll queues kernel: [ 78.859328] usb 1-4: reset high-speed USB device number 12 using xhci_hcd kernel: [ 79.113113] Bluetooth: hci0: advertising data len corrected kernel: [ 79.331948] usb 1-4.4: reset high-speed USB device number 14 using xhci_hcd kernel: [ 79.432122] Blueto
[Kernel-packages] [Bug 1849779] Re: System will auto resume from sleep on receiving LE ADV after paired with BT LE devices
Hello You-Sheng, or anyone else affected, Accepted linux-firmware into disco-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux- firmware/1.178.6 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-disco to verification-done-disco. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-disco. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: linux-firmware (Ubuntu Disco) Status: In Progress => Fix Committed -- 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/1849779 Title: System will auto resume from sleep on receiving LE ADV after paired with BT LE devices Status in HWE Next: New Status in linux-firmware package in Ubuntu: New Status in linux-firmware source package in Bionic: In Progress Status in linux-firmware source package in Disco: Fix Committed Bug description: System, with Intel 9260 Bluetooth fw ver < REL0472, deep suspend will be interrupted and resume automatically once it has been paired with a BLE device. The device doesn't have to remain connected, as long as there are BLE devices near by broadcasting LE ADV. Known affected fw versions are: |commit|fw rev/kernel|4.15.0-66-generic|series| |-|-|-|-| |c2d8f1b7f820|0329|waked up|bionic| |ae90c3bce108|0386|waked up| | |046d1085b19e|0420|waked up|disco| |1e8253bbaafb|0450|waked up| | |7444ca40083a|0472|ok| | |fe48882708de|0482|ok|eoan| This doesn't seem to apply to all platform with 9260, as there are some platforms with identical chip and fw version but are immune from this issue. Steps to reproduce: 1. pair with BLE device and turn off the device. It should be listed as Disconnected in System Bluetooth settings. Close the settings app as well. 2. run `sudo btmon -t` in the background, make sure LE ADV packets pop up. 3. run `sudo btmon -t` on another host to make sure there are LE ADV packets during the suspend period. 3. trigger system deep suspend (S3) on DUT. 4. wait for around 1 minutes (depending on the surrounding environment) and see if the DUT is resumed unsolicitedly. Expects: DUT only resumes when power button pressed or on other explicit requests. Actual: DUT resumes unsolicitedly within 1 minutes. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-firmware 1.173.9 ProcVersionSignature: Ubuntu 4.15.0-58.64-generic 4.15.18 Uname: Linux 4.15.0-58-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 25 06:50:31 2019 Dependencies: PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1849779/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1850739] Re: Revert the firmware update for sound/sof
Hello Hui, or anyone else affected, Accepted linux-firmware into disco-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux- firmware/1.178.6 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-disco to verification-done-disco. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-disco. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: linux-firmware (Ubuntu Disco) Status: New => Fix Committed -- 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/1850739 Title: Revert the firmware update for sound/sof Status in linux-firmware package in Ubuntu: Confirmed Status in linux-firmware source package in Bionic: New Status in linux-firmware source package in Disco: Fix Committed Status in linux-firmware source package in Eoan: Fix Committed Bug description: SRU Justification Impact: An update to the sound sof firmware does not set the PV bit for cometlake, and thus will not load. This is a regression on cometlake platforms. Fix: Revert the update. Test Case: Check that the firmware will load on affected platforms. Regression Potential: This fixes a regression on cometlake paltforms, but will regress the platforms fixed by the patch being reverted. --- I submitted a firmware update for sound/sof, the tracking bug number is: https://bugs.launchpad.net/bugs/1847250 Recently we found this update introduced one problem for cometlake platforms, cometlake need to check PV bit when loading the firmware, but this update doesn't set the PV bit for cometlake, as a result, on cometlake platforms, it always fails to load the firmware. So we should revert this update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1850739/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1849598] Re: [SRU][B/OEM-B/OEM-OSP1/D/E] Add RTL8822cu bluetooth support
Hello AaronMa, or anyone else affected, Accepted linux-firmware into disco-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux- firmware/1.178.6 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-disco to verification-done-disco. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-disco. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: linux-firmware (Ubuntu Disco) Status: New => Fix Committed -- 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/1849598 Title: [SRU][B/OEM-B/OEM-OSP1/D/E] Add RTL8822cu bluetooth support Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-firmware package in Ubuntu: New Status in linux-oem package in Ubuntu: New Status in linux source package in Bionic: New Status in linux-firmware source package in Bionic: New Status in linux-oem source package in Bionic: Fix Committed Status in linux source package in Disco: New Status in linux-firmware source package in Disco: Fix Committed Status in linux-oem source package in Disco: New Status in linux source package in Eoan: New Status in linux-firmware source package in Eoan: Fix Committed Status in linux-oem source package in Eoan: New Bug description: SRU justification: [Impact] Current kernel and firmware lack support of rtl8822cu Bluetooth. [Fix] Add and update the Bluetooth driver and firmware of rtl8822cu. [Test] Verified on hardware. Tests results are good. [Regression Potential] Low. Add new bt chip ID; Add the new firmware and config to enable new bt chip. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1849598/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1849033] Re: xenial/linux-deeplens: 4.15.0-1011.11 -proposed tracker
Hardware Certification have completed testing this -proposed kernel. No regressions were observed, results are available here: http://people.canonical.com/~hwcert/sru-testing/deeplens/4.15.0-1011.11 /deeplens-proposed-published.html ** Tags added: certification-testing-passed ** Changed in: kernel-sru-workflow/certification-testing Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1849033 Title: xenial/linux-deeplens: 4.15.0-1011.11 -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: 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: Invalid 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: Invalid Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Invalid 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: 1849854 packages: main: linux-deeplens meta: linux-meta-deeplens phase: Testing phase-changed: Tuesday, 29. October 2019 13:46 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1849033/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1780590] Re: Add support for Realtek 8723DE wireless adapter
Hello manuel, or anyone else affected, Accepted linux-firmware into disco-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux- firmware/1.178.6 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-disco to verification-done-disco. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-disco. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: linux-firmware (Ubuntu Disco) Status: New => Fix Committed -- 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/1780590 Title: Add support for Realtek 8723DE wireless adapter Status in linux package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: New Status in linux-oem-osp1 package in Ubuntu: New Status in linux source package in Bionic: Won't Fix Status in linux-firmware source package in Bionic: Fix Committed Status in linux-oem-osp1 source package in Bionic: New Status in linux source package in Disco: Won't Fix Status in linux-firmware source package in Disco: Fix Committed Status in linux-oem-osp1 source package in Disco: Won't Fix Status in linux source package in Eoan: Won't Fix Status in linux-firmware source package in Eoan: Fix Committed Status in linux-oem-osp1 source package in Eoan: Won't Fix Status in linux source package in Focal: Confirmed Status in linux-firmware source package in Focal: New Status in linux-oem-osp1 source package in Focal: Won't Fix Bug description: === SRU Justification === [Impact] There's no in-kernel support for Realtek 8723DE, so users need to use out-of-tree DKMS which is not from Ubuntu archive. This has security implication and should be avoided. Also this provides pretty bad user experience. [Fix] Add support to Realtek 8723DE. All commits are cherry-picked from Realtek maintained repo: https://github.com/rtlwifi-linux/rtw88_8723de [Test] With the patch series applied, 8723DE can scan and connect to APs succesfully. Also did some S3 smoke test, it continues to work. [Regression Potential] Low. The device in question was never supported, and if there's any regression, we can count on Realtek Wireless team, thy are now pretty responsive on upstream mailing list. === Original Bug Report === recently I just installed ubuntu 18.04 lts in dual bot next to windows 10. Everything in the installation was fine until the moment to start session. The problem is that the wireless network card does not detect me and when entering the configuration I simply get an error message saying that no wireless adapter was found. I have already followed all the tutorials I found on the web. and update the driver of a github repository, and install how much program they told me to install and I still can not connect via wifi. I just do not know what to do. I have a laptop hp 14-bs004 came with windows 10 installed. The information on the network card is as follows: Network controller [0280]: Realtek Semiconductor Co., Ltd. Device [10ec: d723] Subsystem: Hewlett-Packard Company Device [103c: 8319] Control: I / O + Mem + BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap + 66MHz- UDF- FastB2B- ParErr- DEVSEL = fast> TAbort- SERR- Kernel modules: wl already install the most recent kernel, already intale driver driver realtek rtl8723be according to the instructions of the git repository. and nothing has worked. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Jul 7 22:57:40 2018 InstallationDate: Installed on 2018-07-08 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_MX.UTF
[Kernel-packages] [Bug 1836467] Please test proposed package
Hello Warren, or anyone else affected, Accepted linux-firmware into disco-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux- firmware/1.178.6 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-disco to verification-done-disco. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-disco. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- 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/1836467 Title: Bluetooth fails with "Bluetooth: hci0: request failed to create LE connection: status 0x0c" message with Kernel 4.20 and up [9df0:0034] Status in linux-firmware package in Ubuntu: Fix Committed Status in linux-firmware source package in Bionic: Fix Committed Status in linux-firmware source package in Cosmic: Won't Fix Status in linux-firmware source package in Disco: Fix Committed Bug description: SRU Justification: [Impact] Bluetooth for Intel Wireless-AC 9560 variant 9df0:0034 still fails to pair BT LE HID devices on recent (>= 4.19) kernel. [Fix] Bluetooth firmware REL0450 or newer is required to fix this issue. [Test Case] Install new firmware blob to /lib/firmware/intel, shutdown the machine completely and wait for a couple minutes to trigger firmware reloading at the next boot. Then perform Bluetooth LE HID devices pairing to verify if the proposed fw fixes this issue. [Regression Risk] Low. This affects only sub models of Intel JeffersonPeak Bluetooth chip series using these firmware blobs. == Original Bug Description == This is similar to https://bugs.launchpad.net/bugs/1829737 - however the issue was not fixed by linux-firmware 1.173.8 so I was advised to log a new bug. I have an ASUS ZenBook 14 - UX433FA - which based on this - https://www.notebookcheck.net/ASUS-ZenBook-14-UX433FA-Core-i5-8265U-SSD-FHD-Laptop-Review.403541.0.html - I believe has an Intel 9560 chipset (I am not sure how to independently verify this). With kernels older than 4.20 I can successfully pair my bluetooth mouse (Logitech MX Master) - but with newer kernels I get "Bluetooth: hci0: request failed to create LE connection: status 0x0c" messages. I'm running Linux Mint 19.1 I tried installing linux-firmware 1.173.8, and it didn't seem to help - I also downloaded 1.173.9 proposed from here: https://launchpad.net/ubuntu/bionic/amd64/linux-firmware/1.173.9 and that also didn't seem to help. Both after a cold reboot and a warm reboot I see [ 14.724438] Bluetooth: hci0: Firmware revision 0.1 build 201 week 49 2017 in my dmesg output. Bluetooth works just fine with earlier kernels (however other aspects of the laptop like suspend don't work as well, which is why I'm trying the newer kernel. Linux warren-ZenBook 5.1.16-050116-generic #201907031232 SMP Wed Jul 3 12:35:21 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux dmesg | egrep -i 'blue|firm' [ [0.180273] Spectre V2 : Enabling Restricted Speculation for firmware calls [0.004526] [Firmware Bug]: TSC ADJUST differs within socket(s), fixing all errors [1.417663] [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_04.bin (v1.4) [ 14.641146] iwlwifi :00:14.3: Direct firmware load for iwlwifi-9000-pu-b0-jf-b0-46.ucode failed with error -2 [ 14.642377] iwlwifi :00:14.3: Direct firmware load for iwlwifi-9000-pu-b0-jf-b0-45.ucode failed with error -2 [ 14.642392] iwlwifi :00:14.3: Direct firmware load for iwlwifi-9000-pu-b0-jf-b0-44.ucode failed with error -2 [ 14.652301] iwlwifi :00:14.3: loaded firmware version 43.95eb4e97.0 op_mode iwlmvm [ 14.675356] Bluetooth: Core ver 2.22 [ 14.675374] Bluetooth: HCI device and connection manager initialized [ 14.675377] Bluetooth: HCI socket layer initialized [ 14.675379] Bluetooth: L2CAP socket layer initialized [ 14.675382] Bluetooth: SCO socket layer initialized [ 14.724438] Bluetooth: hci0: Firmware revision 0.1 build 201 week 49 2017 [ 15.207800] Bluetooth: BNEP (Ethernet Emulatio
[Kernel-packages] [Bug 1835879] Please test proposed package
Hello You-Sheng, or anyone else affected, Accepted linux-firmware into disco-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux- firmware/1.178.6 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-disco to verification-done-disco. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-disco. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- 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/1835879 Title: Intel Wireless-AC 9462/9560 not supported on ICL Status in HWE Next: New Status in linux package in Ubuntu: Won't Fix Status in linux-firmware package in Ubuntu: Fix Committed Status in linux-oem-osp1 package in Ubuntu: Fix Released Status in linux source package in Bionic: Won't Fix Status in linux-firmware source package in Bionic: Fix Committed Status in linux-oem-osp1 source package in Bionic: Fix Released Status in linux source package in Cosmic: Won't Fix Status in linux-firmware source package in Cosmic: Won't Fix Status in linux-oem-osp1 source package in Cosmic: Won't Fix Status in linux source package in Disco: Won't Fix Status in linux-firmware source package in Disco: Fix Committed Status in linux-oem-osp1 source package in Disco: Fix Released Bug description: [Impact] Intel Wireless-AC 9560/9462 is not correctly enabled on IceLake platforms. [Fix] Two changes from Intel maintained backport-iwlwifi repository are necessary to add device ID/configs to iwlwifi driver. [Test] Verified on hardware 9462/9560 on IceLake/CometLake platforms. [Regression Potential] Low. These changes are part of the series to enable 9462/9560 on CometLake/IceLake platforms that don't have the support originally. = Original Bug Description = Intel Wireless-AC 9462/9560 on CML was previously enabled via bug 1833065, bug 1834415 and bug 1834464. However on ICL, it fails to startup with following error messages with kernel v5.2-rc7: iwlwifi :00:14.3: loaded firmware version 48.13675109.0 op_mode iwlmvm iwlwifi :00:14.3: Detected Intel(R) Wireless-AC 9560, REV=0x338 iwlwifi :00:14.3: Loaded firmware version: 48.13675109.0 iwlwifi :00:14.3: SecBoot CPU1 Status: 0x5c97, CPU2 Status: 0x3 iwlwifi :00:14.3: Failed to start RT ucode: -5 iwlwifi :00:14.3: Collecting data: trigger 16 fired. iwlwifi :00:14.3: Firmware not running - cannot dump error iwlwifi :00:14.3: Failed to run INIT ucode: -5 Also tried backport-iwlwifi out-of-tree driver revision 7858 (HEAD at the moment) with no luck. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1835879/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1847250] Please test proposed package
Hello Hui, or anyone else affected, Accepted linux-firmware into disco-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux- firmware/1.178.6 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-disco to verification-done-disco. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-disco. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- 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/1847250 Title: update firmware for sound sof driver to fix the hang issue on several Dell machines Status in HWE Next: New Status in OEM Priority Project: Confirmed Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Bionic: Fix Committed Status in linux-firmware source package in Disco: Fix Committed Status in linux-firmware source package in Eoan: Fix Released Bug description: We expect this firmware update could be released with 19.10 [Impact] We have a couple of Dell machines, after installing the system, it will hang randomly, and this issue was reported by factory, they met this issue a couple of times. Then we tried to reproduce this issue, finally reproduced it. [Fix] Intel debugged this issue as well, and they provided 4 kernel patches and a new firmware, we tested them, they really can fix the issue. And the patches were sent the SRU already, now it is time to update firmware. [Test Case] Install the system repeatedly and there is no hang issue anymore. [Regression Risk] Low, Intel told us there is no ABI change for the firmware, so it is safe to run this firmware both with the old driver (not applied those 4 patches) and the new driver (applied those 4 patches). To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1847250/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1849033] Re: xenial/linux-deeplens: 4.15.0-1011.11 -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: 1849854 packages: main: linux-deeplens meta: linux-meta-deeplens phase: Testing phase-changed: Tuesday, 29. October 2019 13:46 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - certification-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1849033 Title: xenial/linux-deeplens: 4.15.0-1011.11 -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: 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: Invalid 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: Invalid Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Invalid 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: 1849854 packages: main: linux-deeplens meta: linux-meta-deeplens phase: Testing phase-changed: Tuesday, 29. October 2019 13:46 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1849033/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836983] Please test proposed package
Hello AceLan, or anyone else affected, Accepted linux-firmware into disco-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux- firmware/1.178.6 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-disco to verification-done-disco. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-disco. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- 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/1836983 Title: [Intel CyclonePeak] Pairing new BT mouse fails sometimes Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Bionic: Fix Committed Status in linux-firmware source package in Disco: Fix Committed Bug description: [Impact] After update the BT firmware, it requires to pair twice to pair a new device. There should be a "SMP: Pairing Request" send from hci0, but it doesn't be submitted in the first time. [Fix] The new firmware fix this issue. [Test] Verified on Dell platforms with BT Designer Mouse(DF:29:ED:BD:82:95) [Regression Potential] Low, the firmware is newly added for new Cyclone Peak wifi/bt, and it won't affect the devices on the market currently. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1836983/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1842893] Please test proposed package
Hello You-Sheng, or anyone else affected, Accepted linux-firmware into disco-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux- firmware/1.178.6 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-disco to verification-done-disco. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-disco. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- 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/1842893 Title: Intel Bluetooth AX201, aka HarrisonPeak (HrP), not supported Status in HWE Next: New Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Bionic: Fix Committed Status in linux-firmware source package in Disco: Fix Committed Status in linux-firmware source package in Eoan: Fix Released Bug description: [5.950346] Bluetooth: hci0: Bootloader revision 0.4 build 0 week 11 2017 [5.951318] Bluetooth: hci0: Device revision is 2 [5.951319] Bluetooth: hci0: Secure boot is enabled [5.951320] Bluetooth: hci0: OTP lock is enabled [5.951320] Bluetooth: hci0: API lock is enabled [5.951321] Bluetooth: hci0: Debug lock is disabled [5.951322] Bluetooth: hci0: Minimum firmware build 1 week 10 2014 [5.952242] bluetooth hci0: Direct firmware load for intel/ibt-19-32-4.sfi failed with error -2 [5.952244] Bluetooth: hci0: Failed to load Intel firmware file (-2) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-melisa+X16 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-08-13 (23 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 Package: linux (not installed) Tags: bionic Uname: Linux 5.3.0-050300rc4-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1842893/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1849779] Re: System will auto resume from sleep on receiving LE ADV after paired with BT LE devices
Hello You-Sheng, or anyone else affected, Accepted linux-firmware into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux- firmware/1.173.12 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: linux-firmware (Ubuntu Bionic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1849779 Title: System will auto resume from sleep on receiving LE ADV after paired with BT LE devices Status in HWE Next: New Status in linux-firmware package in Ubuntu: New Status in linux-firmware source package in Bionic: Fix Committed Status in linux-firmware source package in Disco: Fix Committed Bug description: System, with Intel 9260 Bluetooth fw ver < REL0472, deep suspend will be interrupted and resume automatically once it has been paired with a BLE device. The device doesn't have to remain connected, as long as there are BLE devices near by broadcasting LE ADV. Known affected fw versions are: |commit|fw rev/kernel|4.15.0-66-generic|series| |-|-|-|-| |c2d8f1b7f820|0329|waked up|bionic| |ae90c3bce108|0386|waked up| | |046d1085b19e|0420|waked up|disco| |1e8253bbaafb|0450|waked up| | |7444ca40083a|0472|ok| | |fe48882708de|0482|ok|eoan| This doesn't seem to apply to all platform with 9260, as there are some platforms with identical chip and fw version but are immune from this issue. Steps to reproduce: 1. pair with BLE device and turn off the device. It should be listed as Disconnected in System Bluetooth settings. Close the settings app as well. 2. run `sudo btmon -t` in the background, make sure LE ADV packets pop up. 3. run `sudo btmon -t` on another host to make sure there are LE ADV packets during the suspend period. 3. trigger system deep suspend (S3) on DUT. 4. wait for around 1 minutes (depending on the surrounding environment) and see if the DUT is resumed unsolicitedly. Expects: DUT only resumes when power button pressed or on other explicit requests. Actual: DUT resumes unsolicitedly within 1 minutes. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-firmware 1.173.9 ProcVersionSignature: Ubuntu 4.15.0-58.64-generic 4.15.18 Uname: Linux 4.15.0-58-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 25 06:50:31 2019 Dependencies: PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1849779/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1850738] Please test proposed package
Hello You-Sheng, or anyone else affected, Accepted linux-firmware into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux- firmware/1.173.12 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- 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/1850738 Title: Intel Bluetooth AX201 HarrisonPeak (HrP) firmware causes system hang in deep suspend Status in OEM Priority Project: Confirmed Status in linux-firmware package in Ubuntu: New Status in linux-firmware source package in Bionic: Fix Committed Status in linux-firmware source package in Disco: Fix Committed Bug description: When system has been paired with BLE devices, bluetooth firmware may fail to suspend, or even hangs the whole system that it can only be rebooted with SysRq keys. [Reproduce steps]: 1. pair with BLE devices. They doesn't have to stay connected/powered on during the test. 2. make sure Bluetooth is now receiving LE ADV broadcats, which should leave messages in dmesg like: Bluetooth: hci0: advertising data len corrected 3. suspend the system a few times. With 5.0.0-1025-oem-osp1 kernel, symptoms would usually appear in <= 5 times. [Results] 1. one may observed following errors in between the suspend messages: PM: pci_pm_suspend(): hcd_pci_suspend+0x0/0x30 returns -16 PM: dpm_run_callback(): pci_pm_suspend+0x0/0x150 returns -16 PM: Device :00:14.0 failed to suspend async: error -16 PM: Some devices failed to suspend, or early wake event detected where :00:14.0 is the xHCI Usb hub. 2. with or without above error messages appear first, system may hang and leave only "PM: suspend entry (deep)" in the syslog. [Notes] * kernels newer than v5.2.1, inclusive of latest v5.4-rc5, still have those PM suspend errors, but they doesn't seem to cause system block. Instead, they may resume immediately. * this was found on one platform with Intel Dual Band Wireless AC 9462 [8086:02f0] subsystem id [8086:42a4], linux-firmware 1.173.11 with intel/ibt-19-0-0.sfi REL0282. However, it's not reproducible on another platform with same hw/fw/kernel configuration. kernel: [ 78.136285] PM: suspend entry (deep) kernel: [ 78.139836] Filesystems sync: 0.003 seconds kernel: [ 78.140461] Freezing user space processes ... (elapsed 0.002 seconds) done. kernel: [ 78.142669] OOM killer disabled. kernel: [ 78.142669] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. kernel: [ 78.143875] printk: Suspending console(s) (use no_console_suspend to debug) kernel: [ 78.335256] sof-audio-pci :00:1f.3: error: no reply expected, received 0x0 kernel: [ 78.457675] sof-audio-pci :00:1f.3: firmware boot complete kernel: [ 78.460486] PM: pci_pm_suspend(): hcd_pci_suspend+0x0/0x30 returns -16 kernel: [ 78.460494] PM: dpm_run_callback(): pci_pm_suspend+0x0/0x150 returns -16 kernel: [ 78.460497] PM: Device :00:14.0 failed to suspend async: error -16 kernel: [ 78.567263] PM: Some devices failed to suspend, or early wake event detected kernel: [ 78.580871] sof-audio-pci :00:1f.3: error: no reply expected, received 0x0 kernel: [ 78.713018] sof-audio-pci :00:1f.3: firmware boot complete kernel: [ 78.733982] Bluetooth: hci0: advertising data len corrected kernel: [ 78.792707] nvme nvme0: Shutdown timeout set to 8 seconds kernel: [ 78.841602] nvme nvme0: 8/0/0 default/read/poll queues kernel: [ 78.859328] usb 1-4: reset high-speed USB device number 12 using xhci_hcd kernel: [ 79.113113] Bluetooth: hci0: advertising data len corrected kernel: [ 79.331948] usb 1-4.4: reset high-speed USB device number 14 using xhci_hcd kernel: [ 79.432122] Bluetooth: hci0: advertising data len corrected kernel: [ 79.559747] usb 1-4.1: reset f
[Kernel-packages] [Bug 1850739] Re: Revert the firmware update for sound/sof
Hello Hui, or anyone else affected, Accepted linux-firmware into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux- firmware/1.173.12 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: linux-firmware (Ubuntu Bionic) Status: New => Fix Committed -- 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/1850739 Title: Revert the firmware update for sound/sof Status in linux-firmware package in Ubuntu: Confirmed Status in linux-firmware source package in Bionic: Fix Committed Status in linux-firmware source package in Disco: Fix Committed Status in linux-firmware source package in Eoan: Fix Committed Bug description: SRU Justification Impact: An update to the sound sof firmware does not set the PV bit for cometlake, and thus will not load. This is a regression on cometlake platforms. Fix: Revert the update. Test Case: Check that the firmware will load on affected platforms. Regression Potential: This fixes a regression on cometlake paltforms, but will regress the platforms fixed by the patch being reverted. --- I submitted a firmware update for sound/sof, the tracking bug number is: https://bugs.launchpad.net/bugs/1847250 Recently we found this update introduced one problem for cometlake platforms, cometlake need to check PV bit when loading the firmware, but this update doesn't set the PV bit for cometlake, as a result, on cometlake platforms, it always fails to load the firmware. So we should revert this update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1850739/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1850654] Re: update-initramfs complains of missing amdgpu firmware files
Hello Seth, or anyone else affected, Accepted linux-firmware into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux- firmware/1.173.12 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: linux-firmware (Ubuntu Bionic) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1850654 Title: update-initramfs complains of missing amdgpu firmware files Status in linux package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: New Status in linux source package in Bionic: Invalid Status in linux-firmware source package in Bionic: Fix Committed Status in linux source package in Eoan: Confirmed Status in linux-firmware source package in Eoan: Fix Committed Bug description: SRU Justification Impact: With 5.3 update-initramfs reports several missing amdgpu firmware files: update-initramfs: Generating /boot/initrd.img-5.3.0-19-generic W: Possible missing firmware /lib/firmware/amdgpu/vega20_ta.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/raven_kicker_rlc.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/navi10_mes.bin for module amdgpu Of these, only raven_kicker_rlc.bin has been added to upstream linux- firmware. Fix: Add raven_kicker_rlc.bin to linux firmware, and remove the other files from modinfo for amdgpu. Test Case: Once fixed, the warnings from update-initramfs should be gone. Regression Potential: Adding a missing firmware is unlikely to break any working hardware. Removing the other missing files from modinfo will not cause regressions either, however if the firmware is added later update-initramfs will not add the files to the initramfs until the firmware is added back to modinfo. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850654/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1849598] Re: [SRU][B/OEM-B/OEM-OSP1/D/E] Add RTL8822cu bluetooth support
Hello AaronMa, or anyone else affected, Accepted linux-firmware into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux- firmware/1.173.12 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: linux-firmware (Ubuntu Bionic) Status: New => Fix Committed -- 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/1849598 Title: [SRU][B/OEM-B/OEM-OSP1/D/E] Add RTL8822cu bluetooth support Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-firmware package in Ubuntu: New Status in linux-oem package in Ubuntu: New Status in linux source package in Bionic: New Status in linux-firmware source package in Bionic: Fix Committed Status in linux-oem source package in Bionic: Fix Committed Status in linux source package in Disco: New Status in linux-firmware source package in Disco: Fix Committed Status in linux-oem source package in Disco: New Status in linux source package in Eoan: New Status in linux-firmware source package in Eoan: Fix Committed Status in linux-oem source package in Eoan: New Bug description: SRU justification: [Impact] Current kernel and firmware lack support of rtl8822cu Bluetooth. [Fix] Add and update the Bluetooth driver and firmware of rtl8822cu. [Test] Verified on hardware. Tests results are good. [Regression Potential] Low. Add new bt chip ID; Add the new firmware and config to enable new bt chip. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1849598/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1842893] Please test proposed package
Hello You-Sheng, or anyone else affected, Accepted linux-firmware into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux- firmware/1.173.12 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- 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/1842893 Title: Intel Bluetooth AX201, aka HarrisonPeak (HrP), not supported Status in HWE Next: New Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Bionic: Fix Committed Status in linux-firmware source package in Disco: Fix Committed Status in linux-firmware source package in Eoan: Fix Released Bug description: [5.950346] Bluetooth: hci0: Bootloader revision 0.4 build 0 week 11 2017 [5.951318] Bluetooth: hci0: Device revision is 2 [5.951319] Bluetooth: hci0: Secure boot is enabled [5.951320] Bluetooth: hci0: OTP lock is enabled [5.951320] Bluetooth: hci0: API lock is enabled [5.951321] Bluetooth: hci0: Debug lock is disabled [5.951322] Bluetooth: hci0: Minimum firmware build 1 week 10 2014 [5.952242] bluetooth hci0: Direct firmware load for intel/ibt-19-32-4.sfi failed with error -2 [5.952244] Bluetooth: hci0: Failed to load Intel firmware file (-2) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-melisa+X16 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-08-13 (23 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 Package: linux (not installed) Tags: bionic Uname: Linux 5.3.0-050300rc4-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1842893/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1848848] Re: Firmware for Radeon RX5700 (navi10) missing / boot failure
Hello Christian, or anyone else affected, Accepted linux-firmware into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux- firmware/1.173.12 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: linux-firmware (Ubuntu Bionic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1848848 Title: Firmware for Radeon RX5700 (navi10) missing / boot failure Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Bionic: Fix Committed Status in linux-firmware source package in Eoan: Fix Released Bug description: As an owner of a Radeon RX5700 GPU, I was really looking forward to the Eoan release which includes the Linux Kernel 5.3 and Mesa 19.2 - both with finally Radeon RX5700 (navi10) support. However, upgrading my system from Kubuntu 18.10 (working) via 19.04 (does not boot) to 19.10 resulted in a boot failure. Last message shown on the screen is: fb0: switching to amdgpudrmfb from EFI VGA After some research I found that the package linux-firmware does not include the necessary files /lib/firmware/amdgpu/navi10_*. After I manually copied the missing files from the repository git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux- firmware.git, I was able to boot normally. Please update the package linux-firmware and add the needed firmware. $ lsb_release -rd Description:Ubuntu 19.10 Release:19.10 $ apt-cache policy linux-firmware linux-firmware: Installiert: 1.183 Installationskandidat: 1.183 Versionstabelle: *** 1.183 500 500 http://de.archive.ubuntu.com/ubuntu eoan/main amd64 Packages 500 http://de.archive.ubuntu.com/ubuntu eoan/main i386 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1848848/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1847250] Please test proposed package
Hello Hui, or anyone else affected, Accepted linux-firmware into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux- firmware/1.173.12 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- 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/1847250 Title: update firmware for sound sof driver to fix the hang issue on several Dell machines Status in HWE Next: New Status in OEM Priority Project: Confirmed Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Bionic: Fix Committed Status in linux-firmware source package in Disco: Fix Committed Status in linux-firmware source package in Eoan: Fix Released Bug description: We expect this firmware update could be released with 19.10 [Impact] We have a couple of Dell machines, after installing the system, it will hang randomly, and this issue was reported by factory, they met this issue a couple of times. Then we tried to reproduce this issue, finally reproduced it. [Fix] Intel debugged this issue as well, and they provided 4 kernel patches and a new firmware, we tested them, they really can fix the issue. And the patches were sent the SRU already, now it is time to update firmware. [Test Case] Install the system repeatedly and there is no hang issue anymore. [Regression Risk] Low, Intel told us there is no ABI change for the firmware, so it is safe to run this firmware both with the old driver (not applied those 4 patches) and the new driver (applied those 4 patches). To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1847250/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835879] Please test proposed package
Hello You-Sheng, or anyone else affected, Accepted linux-firmware into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux- firmware/1.173.12 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- 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/1835879 Title: Intel Wireless-AC 9462/9560 not supported on ICL Status in HWE Next: New Status in linux package in Ubuntu: Won't Fix Status in linux-firmware package in Ubuntu: Fix Committed Status in linux-oem-osp1 package in Ubuntu: Fix Released Status in linux source package in Bionic: Won't Fix Status in linux-firmware source package in Bionic: Fix Committed Status in linux-oem-osp1 source package in Bionic: Fix Released Status in linux source package in Cosmic: Won't Fix Status in linux-firmware source package in Cosmic: Won't Fix Status in linux-oem-osp1 source package in Cosmic: Won't Fix Status in linux source package in Disco: Won't Fix Status in linux-firmware source package in Disco: Fix Committed Status in linux-oem-osp1 source package in Disco: Fix Released Bug description: [Impact] Intel Wireless-AC 9560/9462 is not correctly enabled on IceLake platforms. [Fix] Two changes from Intel maintained backport-iwlwifi repository are necessary to add device ID/configs to iwlwifi driver. [Test] Verified on hardware 9462/9560 on IceLake/CometLake platforms. [Regression Potential] Low. These changes are part of the series to enable 9462/9560 on CometLake/IceLake platforms that don't have the support originally. = Original Bug Description = Intel Wireless-AC 9462/9560 on CML was previously enabled via bug 1833065, bug 1834415 and bug 1834464. However on ICL, it fails to startup with following error messages with kernel v5.2-rc7: iwlwifi :00:14.3: loaded firmware version 48.13675109.0 op_mode iwlmvm iwlwifi :00:14.3: Detected Intel(R) Wireless-AC 9560, REV=0x338 iwlwifi :00:14.3: Loaded firmware version: 48.13675109.0 iwlwifi :00:14.3: SecBoot CPU1 Status: 0x5c97, CPU2 Status: 0x3 iwlwifi :00:14.3: Failed to start RT ucode: -5 iwlwifi :00:14.3: Collecting data: trigger 16 fired. iwlwifi :00:14.3: Firmware not running - cannot dump error iwlwifi :00:14.3: Failed to run INIT ucode: -5 Also tried backport-iwlwifi out-of-tree driver revision 7858 (HEAD at the moment) with no luck. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1835879/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836983] Please test proposed package
Hello AceLan, or anyone else affected, Accepted linux-firmware into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux- firmware/1.173.12 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- 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/1836983 Title: [Intel CyclonePeak] Pairing new BT mouse fails sometimes Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Bionic: Fix Committed Status in linux-firmware source package in Disco: Fix Committed Bug description: [Impact] After update the BT firmware, it requires to pair twice to pair a new device. There should be a "SMP: Pairing Request" send from hci0, but it doesn't be submitted in the first time. [Fix] The new firmware fix this issue. [Test] Verified on Dell platforms with BT Designer Mouse(DF:29:ED:BD:82:95) [Regression Potential] Low, the firmware is newly added for new Cyclone Peak wifi/bt, and it won't affect the devices on the market currently. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1836983/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1780590] Re: Add support for Realtek 8723DE wireless adapter
Hello manuel, or anyone else affected, Accepted linux-firmware into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux- firmware/1.173.12 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: linux-firmware (Ubuntu Bionic) Status: New => Fix Committed -- 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/1780590 Title: Add support for Realtek 8723DE wireless adapter Status in linux package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: New Status in linux-oem-osp1 package in Ubuntu: New Status in linux source package in Bionic: Won't Fix Status in linux-firmware source package in Bionic: Fix Committed Status in linux-oem-osp1 source package in Bionic: New Status in linux source package in Disco: Won't Fix Status in linux-firmware source package in Disco: Fix Committed Status in linux-oem-osp1 source package in Disco: Won't Fix Status in linux source package in Eoan: Won't Fix Status in linux-firmware source package in Eoan: Fix Committed Status in linux-oem-osp1 source package in Eoan: Won't Fix Status in linux source package in Focal: Confirmed Status in linux-firmware source package in Focal: New Status in linux-oem-osp1 source package in Focal: Won't Fix Bug description: === SRU Justification === [Impact] There's no in-kernel support for Realtek 8723DE, so users need to use out-of-tree DKMS which is not from Ubuntu archive. This has security implication and should be avoided. Also this provides pretty bad user experience. [Fix] Add support to Realtek 8723DE. All commits are cherry-picked from Realtek maintained repo: https://github.com/rtlwifi-linux/rtw88_8723de [Test] With the patch series applied, 8723DE can scan and connect to APs succesfully. Also did some S3 smoke test, it continues to work. [Regression Potential] Low. The device in question was never supported, and if there's any regression, we can count on Realtek Wireless team, thy are now pretty responsive on upstream mailing list. === Original Bug Report === recently I just installed ubuntu 18.04 lts in dual bot next to windows 10. Everything in the installation was fine until the moment to start session. The problem is that the wireless network card does not detect me and when entering the configuration I simply get an error message saying that no wireless adapter was found. I have already followed all the tutorials I found on the web. and update the driver of a github repository, and install how much program they told me to install and I still can not connect via wifi. I just do not know what to do. I have a laptop hp 14-bs004 came with windows 10 installed. The information on the network card is as follows: Network controller [0280]: Realtek Semiconductor Co., Ltd. Device [10ec: d723] Subsystem: Hewlett-Packard Company Device [103c: 8319] Control: I / O + Mem + BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap + 66MHz- UDF- FastB2B- ParErr- DEVSEL = fast> TAbort- SERR- Kernel modules: wl already install the most recent kernel, already intale driver driver realtek rtl8723be according to the instructions of the git repository. and nothing has worked. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Jul 7 22:57:40 2018 InstallationDate: Installed on 2018-07-08 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_
[Kernel-packages] [Bug 1836467] Please test proposed package
Hello Warren, or anyone else affected, Accepted linux-firmware into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux- firmware/1.173.12 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- 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/1836467 Title: Bluetooth fails with "Bluetooth: hci0: request failed to create LE connection: status 0x0c" message with Kernel 4.20 and up [9df0:0034] Status in linux-firmware package in Ubuntu: Fix Committed Status in linux-firmware source package in Bionic: Fix Committed Status in linux-firmware source package in Cosmic: Won't Fix Status in linux-firmware source package in Disco: Fix Committed Bug description: SRU Justification: [Impact] Bluetooth for Intel Wireless-AC 9560 variant 9df0:0034 still fails to pair BT LE HID devices on recent (>= 4.19) kernel. [Fix] Bluetooth firmware REL0450 or newer is required to fix this issue. [Test Case] Install new firmware blob to /lib/firmware/intel, shutdown the machine completely and wait for a couple minutes to trigger firmware reloading at the next boot. Then perform Bluetooth LE HID devices pairing to verify if the proposed fw fixes this issue. [Regression Risk] Low. This affects only sub models of Intel JeffersonPeak Bluetooth chip series using these firmware blobs. == Original Bug Description == This is similar to https://bugs.launchpad.net/bugs/1829737 - however the issue was not fixed by linux-firmware 1.173.8 so I was advised to log a new bug. I have an ASUS ZenBook 14 - UX433FA - which based on this - https://www.notebookcheck.net/ASUS-ZenBook-14-UX433FA-Core-i5-8265U-SSD-FHD-Laptop-Review.403541.0.html - I believe has an Intel 9560 chipset (I am not sure how to independently verify this). With kernels older than 4.20 I can successfully pair my bluetooth mouse (Logitech MX Master) - but with newer kernels I get "Bluetooth: hci0: request failed to create LE connection: status 0x0c" messages. I'm running Linux Mint 19.1 I tried installing linux-firmware 1.173.8, and it didn't seem to help - I also downloaded 1.173.9 proposed from here: https://launchpad.net/ubuntu/bionic/amd64/linux-firmware/1.173.9 and that also didn't seem to help. Both after a cold reboot and a warm reboot I see [ 14.724438] Bluetooth: hci0: Firmware revision 0.1 build 201 week 49 2017 in my dmesg output. Bluetooth works just fine with earlier kernels (however other aspects of the laptop like suspend don't work as well, which is why I'm trying the newer kernel. Linux warren-ZenBook 5.1.16-050116-generic #201907031232 SMP Wed Jul 3 12:35:21 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux dmesg | egrep -i 'blue|firm' [ [0.180273] Spectre V2 : Enabling Restricted Speculation for firmware calls [0.004526] [Firmware Bug]: TSC ADJUST differs within socket(s), fixing all errors [1.417663] [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_04.bin (v1.4) [ 14.641146] iwlwifi :00:14.3: Direct firmware load for iwlwifi-9000-pu-b0-jf-b0-46.ucode failed with error -2 [ 14.642377] iwlwifi :00:14.3: Direct firmware load for iwlwifi-9000-pu-b0-jf-b0-45.ucode failed with error -2 [ 14.642392] iwlwifi :00:14.3: Direct firmware load for iwlwifi-9000-pu-b0-jf-b0-44.ucode failed with error -2 [ 14.652301] iwlwifi :00:14.3: loaded firmware version 43.95eb4e97.0 op_mode iwlmvm [ 14.675356] Bluetooth: Core ver 2.22 [ 14.675374] Bluetooth: HCI device and connection manager initialized [ 14.675377] Bluetooth: HCI socket layer initialized [ 14.675379] Bluetooth: L2CAP socket layer initialized [ 14.675382] Bluetooth: SCO socket layer initialized [ 14.724438] Bluetooth: hci0: Firmware revision 0.1 build 201 week 49 2017 [ 15.207800] Bluetooth: BNEP (Ethernet Emu
[Kernel-packages] [Bug 1849682] Re: [REGRESSION] md/raid0: cannot assemble multi-zone RAID0 with default_layout setting
= Verification = I see 2 pieces to this: 1) The original report, in Comment #1, where the offending patch caused an issue on a system where it shouldn't have - i.e., a raid0 w/ homogenous member sizes. We were never able to reproduce this in subsequent tests w/ the patch applied. I know sfeole was able to perform the same MAAS install/upgrade w/ the current -proposed kernel (I saw a test report from it), so I think we can confidently say it is not reproducible in that build either. 2) In configs where this patch *should* prevent a raid0 from assembling (heterogenous sizes), I've verified that if I create such an array on an older kernel, then upgrade to the current -proposed kernel, it starts automatically. Now, of course, I continue to be susceptible to corruption, but that's known and tracked in bug 1850540. $ cat /proc/version Linux version 4.15.0-66-generic (buildd@lgw01-amd64-044) (gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1)) #75-Ubuntu SMP Tue Oct 1 05:24:09 UTC 2019 $ sudo mdadm --create /dev/md0 --run --metadata=default --homehost=akis --level=0 --raid-devices=2 /dev/vdb1 /dev/vdc1 mdadm: /dev/vdb1 appears to be part of a raid array: level=raid0 devices=2 ctime=Thu Oct 31 21:53:40 2019 mdadm: /dev/vdc1 appears to be part of a raid array: level=raid0 devices=2 ctime=Thu Oct 31 21:53:40 2019 mdadm: array /dev/md0 started. $ sudo reboot $ cat /proc/version Linux version 4.15.0-68-generic (buildd@lgw01-amd64-037) (gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1)) #77-Ubuntu SMP Sun Oct 27 06:02:23 UTC 2019 $ cat /proc/mdstat Personalities : [raid0] [linear] [multipath] [raid1] [raid6] [raid5] [raid4] [raid10] md127 : active raid0 vdc1[1] vdb1[0] 1567744 blocks super 1.2 512k chunks unused devices: -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1849682 Title: [REGRESSION] md/raid0: cannot assemble multi-zone RAID0 with default_layout setting Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Fix Committed Status in linux source package in Disco: Incomplete Status in linux source package in Eoan: Incomplete Status in linux source package in Focal: Incomplete Bug description: This bug tracks the temporary revert of the upstream fix for a corruption issue. Bug 1850540 tracks the re-application of that fix once we have a full solution. Users of RAID0 arrays are susceptible to a corruption issue if: - The members of the RAID array are not all the same size[*] - Data has been written to the array while running kernels < 3.14 *and* >= 3.14. This is because of an change in v3.14 that accidentally changed how data was written - as described in the upstream commit message: https://github.com/torvalds/linux/commit/c84a1372df929033cb1a0441fb57bd3932f39ac9 To summarize, upstream is dealing with this by adding a versioned layout in v5.4, and that is being backported to stable kernels - which is why we're now seeing it. Layout version 1 is the pre-3.14 layout, version 2 is post 3.14. Mixing version 1 & version 2 layouts can cause corruption. However, unless a layout-version-aware kernel *created* the array, there's no way for the kernel to know which version(s) was used to write the existing data. This undefined mode is considered "Version 0", and the kernel will now refuse to start these arrays w/o user intervention. The user experience is pretty awful here. A user upgrades to the next SRU and all of a sudden their system stops at an (initramfs) prompt. A clueful user can spot something like the following in dmesg: Here's the message which , as you can see from the log in Comment #1, is hidden in a ton of other messages: [ 72.720232] md/raid0:md0: cannot assemble multi-zone RAID0 with default_layout setting [ 72.728149] md/raid0: please set raid.default_layout to 1 or 2 [ 72.733979] md: pers->run() failed ... mdadm: failed to start array /dev/md0: Unknown error 524 What that is trying to say is that you should determine if your data - specifically the data toward the end of your array - was most likely written with a pre-3.14 or post-3.14 kernel. Based on that, reboot with the kernel parameter raid0.default_layout=1 or raid0.default_layout=2 on the kernel command line. And note it should be *raid0.default_layout* not *raid.default_layout* as the message says - a fix for that message is now queued for stable: https://github.com/torvalds/linux/commit/3874d73e06c9b9dc15de0b7382fc223986d75571) IMHO, we should work with upstream to create a web page that clearly walks the user through this process, and update the error message to point to that page. I'd also like to see if we can detect this problem *before* the user reboots (debconf?) and help the user fix things. e.g. "We detected that you have RAID0 arrays tha
[Kernel-packages] [Bug 1851749] Re: Frequently getting thermal warnings and cpu throttling messages in syslog
** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Colin Ian King (colin-king) ** Changed in: linux (Ubuntu) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1851749 Title: Frequently getting thermal warnings and cpu throttling messages in syslog Status in linux package in Ubuntu: In Progress Bug description: Nov 6 11:34:26 fog kernel: [1129655.443564] mce: CPU0: Core temperature above threshold, cpu clock throttled (total events = 50300) Nov 6 11:34:26 fog kernel: [1129655.443565] mce: CPU2: Core temperature above threshold, cpu clock throttled (total events = 50300) Nov 6 11:34:26 fog kernel: [1129655.443567] mce: CPU1: Package temperature above threshold, cpu clock throttled (total events = 58637) Nov 6 11:34:26 fog kernel: [1129655.443568] mce: CPU3: Package temperature above threshold, cpu clock throttled (total events = 58637) Nov 6 11:34:26 fog kernel: [1129655.443569] mce: CPU2: Package temperature above threshold, cpu clock throttled (total events = 58637) Nov 6 11:34:26 fog kernel: [1129655.443570] mce: CPU0: Package temperature above threshold, cpu clock throttled (total events = 58637) Nov 6 11:34:26 fog kernel: [1129655.446528] mce: CPU2: Core temperature/speed normal Nov 6 11:34:26 fog kernel: [1129655.446529] mce: CPU0: Core temperature/speed normal Nov 6 11:34:26 fog kernel: [1129655.446530] mce: CPU1: Package temperature/speed normal Nov 6 11:34:26 fog kernel: [1129655.446531] mce: CPU3: Package temperature/speed normal Nov 6 11:34:26 fog kernel: [1129655.446531] mce: CPU0: Package temperature/speed normal Nov 6 11:34:26 fog kernel: [1129655.446532] mce: CPU2: Package temperature/speed normal Nov 6 11:40:35 fog kernel: [1130024.427390] mce: CPU0: Core temperature above threshold, cpu clock throttled (total events = 50316) Nov 6 11:40:35 fog kernel: [1130024.427391] mce: CPU2: Core temperature above threshold, cpu clock throttled (total events = 50316)
[Kernel-packages] [Bug 1826125] Re: Dell XPS 13 9380 flickering (Whiskey Lake)
I saw a flickering maybe once.. with the new kernel, but I can confirm it's not happening often. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1826125 Title: Dell XPS 13 9380 flickering (Whiskey Lake) Status in Linux: In Progress Status in linux package in Ubuntu: Confirmed Bug description: A brand new Dell XPS 13 9380 preinstalled with Ubuntu 18.04 flickers to the point of being totally unusable. I have upgraded since to 18.10 and 19.04 with no changes. I have tried several combinations of the i915 parameters fastboot, enable_rc6 and enable_fbc to no avail. Examples of flickering are here: https://photos.app.goo.gl/1PkL2HrjMBP41aML9 https://photos.app.goo.gl/CMzmMwrCPH5wh8aw6 --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1430 F pulseaudio DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+italia-whl+X31 DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-04-13 (10 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 MachineType: Dell Inc. XPS 13 9380 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1035-oem root=UUID=252898e9-6e96-4705-a709-2db930b7c4c7 ro quiet splash i915.fastboot=1 i915.enable_rc6=0 vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-1035.40-oem 4.15.18 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.15.0-1035-oem N/A linux-backports-modules-4.15.0-1035-oem N/A linux-firmware 1.178 Tags: disco Uname: Linux 4.15.0-1035-oem x86_64 UpgradeStatus: Upgraded to disco on 2019-04-24 (0 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 02/14/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.1 dmi.board.name: 0KTW76 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.1:bd02/14/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn0KTW76:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9380 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1826125/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1826125] Re: Dell XPS 13 9380 flickering (Whiskey Lake)
Correction, I just got a flicker, don't know why exactly what is triggering it, but it's not often. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1826125 Title: Dell XPS 13 9380 flickering (Whiskey Lake) Status in Linux: In Progress Status in linux package in Ubuntu: Confirmed Bug description: A brand new Dell XPS 13 9380 preinstalled with Ubuntu 18.04 flickers to the point of being totally unusable. I have upgraded since to 18.10 and 19.04 with no changes. I have tried several combinations of the i915 parameters fastboot, enable_rc6 and enable_fbc to no avail. Examples of flickering are here: https://photos.app.goo.gl/1PkL2HrjMBP41aML9 https://photos.app.goo.gl/CMzmMwrCPH5wh8aw6 --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1430 F pulseaudio DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+italia-whl+X31 DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-04-13 (10 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 MachineType: Dell Inc. XPS 13 9380 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1035-oem root=UUID=252898e9-6e96-4705-a709-2db930b7c4c7 ro quiet splash i915.fastboot=1 i915.enable_rc6=0 vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-1035.40-oem 4.15.18 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.15.0-1035-oem N/A linux-backports-modules-4.15.0-1035-oem N/A linux-firmware 1.178 Tags: disco Uname: Linux 4.15.0-1035-oem x86_64 UpgradeStatus: Upgraded to disco on 2019-04-24 (0 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 02/14/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.1 dmi.board.name: 0KTW76 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.1:bd02/14/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn0KTW76:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9380 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1826125/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1851749] Re: Frequently getting thermal warnings and cpu throttling messages in syslog
Glad to see this filed, I have the same issue. Note there is a good discussion of the issue here: https://www.reddit.com/r/thinkpad/comments/870u0a/t480s_linux_throttling_bug/ And the User made a github repo to address the problem in testing: https://github.com/erpalma/throttled I can clearly see the effect of the change using s-tui and monitoring cpu freq. Before the change, the throttle will limit me to around 1.5-1.7 GHZ under load, after the change, it's at 2.7GHZ consistent without the constant throttle messages in syslog/journalctl. I don't have enough depth in this area to understand the technical tradeoffs, but I did want to point out the research that I have used thus far. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1851749 Title: Frequently getting thermal warnings and cpu throttling messages in syslog Status in linux package in Ubuntu: In Progress Bug description: Nov 6 11:34:26 fog kernel: [1129655.443564] mce: CPU0: Core temperature above threshold, cpu clock throttled (total events = 50300) Nov 6 11:34:26 fog kernel: [1129655.443565] mce: CPU2: Core temperature above threshold, cpu clock throttled (total events = 50300) Nov 6 11:34:26 fog kernel: [1129655.443567] mce: CPU1: Package temperature above threshold, cpu clock throttled (total events = 58637) Nov 6 11:34:26 fog kernel: [1129655.443568] mce: CPU3: Package temperature above threshold, cpu clock throttled (total events = 58637) Nov 6 11:34:26 fog kernel: [1129655.443569] mce: CPU2: Package temperature above threshold, cpu clock throttled (total events = 58637) Nov 6 11:34:26 fog kernel: [1129655.443570] mce: CPU0: Package temperature above threshold, cpu clock throttled (total events = 58637) Nov 6 11:34:26 fog kernel: [1129655.446528] mce: CPU2: Core temperature/speed normal Nov 6 11:34:26 fog kernel: [1129655.446529] mce: CPU0: Core temperature/speed normal Nov 6 11:34:26 fog kernel: [1129655.446530] mce: CPU1: Package temperature/speed normal Nov 6 11:34:26 fog kernel: [1129655.446531] mce: CPU3: Package temperature/speed normal Nov 6 11:34:26 fog kernel: [1129655.446531] mce: CPU0: Package temperature/speed normal Nov 6 11:34:26 fog kernel: [1129655.446532] mce: CPU2: Package temperature/speed normal Nov 6 11:40:35 fog kernel: [1130024.427390] mce: CPU0: Core temperature above
[Kernel-packages] [Bug 1849281] Re: seccomp: fix SECCOMP_USER_NOTIF_FLAG_CONTINUE test
** Changed in: linux (Ubuntu Disco) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1849281 Title: seccomp: fix SECCOMP_USER_NOTIF_FLAG_CONTINUE test Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Fix Committed Status in linux source package in Disco: In Progress Status in linux source package in Eoan: In Progress Bug description: SRU Justification Impact: We recently backported SECCOMP_USER_NOTIF_FLAG_CONTINUE in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1847744. On a kernel that supports SECCOMP_FILTER_FLAG_NEW_LISTENER but not SECCOMP_USER_NOTIF_FLAG_CONTINUE the selftests currently fail to compile. The reason is that the ifndef for SECCOMP_USER_NOTIF_FLAG_CONTINUE is placed under the ifndef for SECCOMP_FILTER_FLAG_NEW_LISTENER. Fix: The ifndef for SECCOMP_USER_NOTIF_FLAG_CONTINUE was placed under the ifndef for the SECCOMP_FILTER_FLAG_NEW_LISTENER feature. This will not work on systems that do support SECCOMP_FILTER_FLAG_NEW_LISTENER but do not support SECCOMP_USER_NOTIF_FLAG_CONTINUE. So move the latter ifndef out of the former ifndef's scope. Regression Potential: Limited to seccomp selftests. Test Case: Compile the selftests on a kernel that supports SECCOMP_FILTER_FLAG_NEW_LISTENER but does not support SECCOMP_USER_NOTIF_FLAG_CONTINUE and see that compilations succeeds. Target Kernels: All current LTS kernels with access to a 5.0 kernel. Patches: https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git/commit/?h=for-next/seccomp&id=2aa8d8d04ca29c3269154e1d48855e498be8882f To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1849281/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1848848] Re: Firmware for Radeon RX5700 (navi10) missing / boot failure
I'm afraid I won't be able to test the Bionic version before the end of the year. I don't have a Bionic installation on my machine, and the next free weekend for installing a new system and doing tests like that would be in 2020... Anybody else, who could give it a try? -- 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/1848848 Title: Firmware for Radeon RX5700 (navi10) missing / boot failure Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Bionic: Fix Committed Status in linux-firmware source package in Eoan: Fix Released Bug description: As an owner of a Radeon RX5700 GPU, I was really looking forward to the Eoan release which includes the Linux Kernel 5.3 and Mesa 19.2 - both with finally Radeon RX5700 (navi10) support. However, upgrading my system from Kubuntu 18.10 (working) via 19.04 (does not boot) to 19.10 resulted in a boot failure. Last message shown on the screen is: fb0: switching to amdgpudrmfb from EFI VGA After some research I found that the package linux-firmware does not include the necessary files /lib/firmware/amdgpu/navi10_*. After I manually copied the missing files from the repository git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux- firmware.git, I was able to boot normally. Please update the package linux-firmware and add the needed firmware. $ lsb_release -rd Description:Ubuntu 19.10 Release:19.10 $ apt-cache policy linux-firmware linux-firmware: Installiert: 1.183 Installationskandidat: 1.183 Versionstabelle: *** 1.183 500 500 http://de.archive.ubuntu.com/ubuntu eoan/main amd64 Packages 500 http://de.archive.ubuntu.com/ubuntu eoan/main i386 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1848848/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1776887] Re: Critical upstream bugfix missing in Ubuntu 18.04 - frequent Xorg crash after suspend
I'd like to report a bug:
Ubuntu 18.04 (bionic), Gnome 3.28.2
The frequency is typically more than once per day-
shakespeare@RYZEN:~$ uname -r
5.0.0-33-generic
I am using a 4K ROG-1060 display with NVIDIA driver metapackage from
nvidia-driver-435 (proprietary, tested)
AMD Ryzen 7 1700X Eight-Core Processor with 16 CPUs at 1879.982 MHz family(23)
model(1) stepping(1)
I have 32GB of physical RAM (94% free) with swap 15GB (100% free).
NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1776887
Title:
Critical upstream bugfix missing in Ubuntu 18.04 - frequent Xorg crash
after suspend
Status in linux package in Ubuntu:
Triaged
Status in linux source package in Bionic:
Fix Committed
Bug description:
== SRU Justification ==
This upstream bug has been confirmed to affect Ubuntu users[1]. As
per the fix commit (below), the most frequent symptom is a crash of
Xorg/Xwayland, i.e. killing the entire GUI, when a laptop is woken
from system sleep. Frequency of the bug is described as once every
few days[2].
[1] E.g. this user confirms the bug & very specific workaround:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1760450/comments/11
[2] E.g. this log of crashes:
https://bugzilla.redhat.com/show_bug.cgi?id=1553979#c23
This is a bug in blk-core.c. It is not specific to any one hardware
driver. Technically the suspend bug is triggered by the SCSI core -
which is used by *all SATA devices*.
The commit also includes a test which quickly and reliably proves the
existence of a horrifying bug.
I guess you might avoid this bug only if you have root on NVMe. The
other way to not hit the Xorg crash is if you don't use all your RAM,
so there's no pressure that leads to cold pages of Xorg being swapped.
Also, you won't reproduce the Xorg crash if you suspend+resume
immediately. (This frustrated my tests at one point, it only
triggered after left the system suspended over lunch :).
Fix: "block: do not use interruptible wait anywhere"
in kernel 4.17:
https://github.com/torvalds/linux/commit/1dc3039bc87ae7d19a990c3ee71cfd8a9068f428
in kernel 4.16.8:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-
stable.git/commit/?h=linux-4.16.y&id=7859056bc73dea2c3714b00c83b253d4c22bf7b6
lack of fix in 4.15.0-24.26 (ubuntu 18.04): https://git.launchpad.net
/~ubuntu-kernel/ubuntu/+source/linux/+git/bionic/tree/block/blk-
core.c?id=Ubuntu-4.15.0-24.26#n856
I.e., this bug is still present in Ubuntu source package
linux-4.15.0-24.26 (and 4.15.0-23.25). I attach hardware details
(lspci-vnvn.log) of a system where this bug is known to happen.
Regards
Alan
WORKAROUND: Use kernel parameter:
scsi_mod.scan=sync
== Fix ==
1dc3039bc87a ("block: do not use interruptible wait anywhere")
== Regression Potential ==
Low. This patch has been sent to stable, so it has had additional
upstream review.
== Test Case ==
A test kernel was built with this patch and tested by the original bug
reporter.
The bug reporter states the test kernel resolved the bug.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776887/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1841955] Re: Can't upgrade kernel on raspberry pi3a+
** Description changed: - Can't upgrade kernel on raspberry pi3b+ + [Impact] - [Steps to Reproduce] + Can't upgrade kernel on raspberry pi3a+. Without this, users can be + stuck with old kernels. + + [Test Case] + 1. dd the image in an SD card: http://cdimage.ubuntu.com/ubuntu/releases/18.04/release/ubuntu-18.04.3-preinstalled-server-armhf+raspi3.img.xz 2. Boot rpi3a+ with the sd card 3. Upgrade the kernel using following command: sudo apt update sudo apt install linux-raspi2 4. Check output message - [Expected Result] + Expected Result Current stable kernel(4.15.0-1043-raspi2) is installed. - [Actual Result] + Actual Result Error shows up during the installation, and the kernel is still the original one after reboot. + [Regression Potential] + + None. The bugfix for this change is only adding the missing db/all.db + Pi3A+ entry to flash-kernel. + [Additional Info] + Command output: ubuntu@ubuntu:~$ sudo apt install linux-raspi2 Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: linux-headers-4.15.0-1043-raspi2 linux-headers-raspi2 linux-image-4.15.0-1043-raspi2 linux-image-raspi2 linux-modules-4.15.0-1043-raspi2 linux-raspi2-headers-4.15.0-1043 Suggested packages: fdutils linux-raspi2-doc-4.15.0 | linux-raspi2-source-4.15.0 linux-raspi2-tools The following NEW packages will be installed: linux-headers-4.15.0-1043-raspi2 linux-image-4.15.0-1043-raspi2 linux-modules-4.15.0-1043-raspi2 linux-raspi2-headers-4.15.0-1043 The following packages will be upgraded: linux-headers-raspi2 linux-image-raspi2 linux-raspi2 3 upgraded, 4 newly installed, 0 to remove and 16 not upgraded. Need to get 45.1 MB of archives. After this operation, 214 MB of additional disk space will be used. Do you want to continue? [Y/n] Get:1 http://ports.ubuntu.com/ubuntu-ports bionic-updates/universe armhf linux-raspi2-headers-4.15.0-1043 armhf 4.15.0-1043.46 [11.0 MB] Get:2 http://ports.ubuntu.com/ubuntu-ports bionic-updates/universe armhf linux-headers-4.15.0-1043-raspi2 armhf 4.15.0-1043.46 [852 kB] Get:3 http://ports.ubuntu.com/ubuntu-ports bionic-updates/universe armhf linux-modules-4.15.0-1043-raspi2 armhf 4.15.0-1043.46 [26.5 MB] Get:4 http://ports.ubuntu.com/ubuntu-ports bionic-updates/universe armhf linux-image-4.15.0-1043-raspi2 armhf 4.15.0-1043.46 [6,751 kB] Get:5 http://ports.ubuntu.com/ubuntu-ports bionic-updates/universe armhf linux-raspi2 armhf 4.15.0.1043.41 [1,884 B] Get:6 http://ports.ubuntu.com/ubuntu-ports bionic-updates/universe armhf linux-image-raspi2 armhf 4.15.0.1043.41 [2,524 B] Get:7 http://ports.ubuntu.com/ubuntu-ports bionic-updates/universe armhf linux-headers-raspi2 armhf 4.15.0.1043.41 [2,512 B] Fetched 45.1 MB in 19s (2,363 kB/s) Selecting previously unselected package linux-raspi2-headers-4.15.0-1043. (Reading database ... 62492 files and directories currently installed.) Preparing to unpack .../0-linux-raspi2-headers-4.15.0-1043_4.15.0-1043.46_armhf.deb ... Unpacking linux-raspi2-headers-4.15.0-1043 (4.15.0-1043.46) ... Selecting previously unselected package linux-headers-4.15.0-1043-raspi2. Preparing to unpack .../1-linux-headers-4.15.0-1043-raspi2_4.15.0-1043.46_armhf.deb ... Unpacking linux-headers-4.15.0-1043-raspi2 (4.15.0-1043.46) ... Selecting previously unselected package linux-modules-4.15.0-1043-raspi2. Preparing to unpack .../2-linux-modules-4.15.0-1043-raspi2_4.15.0-1043.46_armhf.deb ... Unpacking linux-modules-4.15.0-1043-raspi2 (4.15.0-1043.46) ... Selecting previously unselected package linux-image-4.15.0-1043-raspi2. Preparing to unpack .../3-linux-image-4.15.0-1043-raspi2_4.15.0-1043.46_armhf.deb ... Unpacking linux-image-4.15.0-1043-raspi2 (4.15.0-1043.46) ... Preparing to unpack .../4-linux-raspi2_4.15.0.1043.41_armhf.deb ... Unpacking linux-raspi2 (4.15.0.1043.41) over (4.15.0.1041.39) ... Preparing to unpack .../5-linux-image-raspi2_4.15.0.1043.41_armhf.deb ... Unpacking linux-image-raspi2 (4.15.0.1043.41) over (4.15.0.1041.39) ... Preparing to unpack .../6-linux-headers-raspi2_4.15.0.1043.41_armhf.deb ... Unpacking linux-headers-raspi2 (4.15.0.1043.41) over (4.15.0.1041.39) ... Setting up linux-raspi2-headers-4.15.0-1043 (4.15.0-1043.46) ... Setting up linux-modules-4.15.0-1043-raspi2 (4.15.0-1043.46) ... Setting up linux-image-4.15.0-1043-raspi2 (4.15.0-1043.46) ... I: /boot/vmlinuz is now a symlink to vmlinuz-4.15.0-1043-raspi2 I: /boot/initrd.img is now a symlink to initrd.img-4.15.0-1043-raspi2 Setting up linux-headers-4.15.0-1043-raspi2 (4.15.0-1043.46) ... Setting up linux-image-raspi2 (4.15.0.1043.41) ... Setting up linux-headers-raspi2 (4.15.0.1043.41) ... Setting up linux-raspi2 (4.15.0.1043.41) ... Processing triggers for linux-image-4.15.0-1043-raspi2 (4.15.0-1043.46) ... /etc/kernel/postinst.d/in
[Kernel-packages] [Bug 1848848] Re: Firmware for Radeon RX5700 (navi10) missing / boot failure
I've confirmed that the new files are present with 1.173.12. In combination with the verification for eoan I think this should be sufficient. ** Tags added: verification-done-bionic -- 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/1848848 Title: Firmware for Radeon RX5700 (navi10) missing / boot failure Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Bionic: Fix Committed Status in linux-firmware source package in Eoan: Fix Released Bug description: As an owner of a Radeon RX5700 GPU, I was really looking forward to the Eoan release which includes the Linux Kernel 5.3 and Mesa 19.2 - both with finally Radeon RX5700 (navi10) support. However, upgrading my system from Kubuntu 18.10 (working) via 19.04 (does not boot) to 19.10 resulted in a boot failure. Last message shown on the screen is: fb0: switching to amdgpudrmfb from EFI VGA After some research I found that the package linux-firmware does not include the necessary files /lib/firmware/amdgpu/navi10_*. After I manually copied the missing files from the repository git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux- firmware.git, I was able to boot normally. Please update the package linux-firmware and add the needed firmware. $ lsb_release -rd Description:Ubuntu 19.10 Release:19.10 $ apt-cache policy linux-firmware linux-firmware: Installiert: 1.183 Installationskandidat: 1.183 Versionstabelle: *** 1.183 500 500 http://de.archive.ubuntu.com/ubuntu eoan/main amd64 Packages 500 http://de.archive.ubuntu.com/ubuntu eoan/main i386 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1848848/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1851676] Re: dmidecode decodes /sys/class/dmi/id/product_serial incorrectly
This has been fixed upstream in release 3.2[1] of dmidecode. So I guess we just need a backport? Bionic currently has 3.1[2] [1]: https://github.com/mirror/dmidecode/commit/7a9fc6d3cba86ec9c517b8ec314e099c5cb433b9 [2]: https://packages.ubuntu.com/bionic/dmidecode -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dmidecode in Ubuntu. https://bugs.launchpad.net/bugs/1851676 Title: dmidecode decodes /sys/class/dmi/id/product_serial incorrectly Status in dmidecode package in Ubuntu: New Bug description: Hi, On VMWare 6.5 and higher (HW version 13 and higher) when decoding /sys/class/dmi/id/product_serial dmidecode produces an output whereby the first 16 characters have been reversed in comparison to /sys/class/dmi/id/product_uuid. This manifests itself by breaking provisioning in Kubernetes and could cause other issues down the line. Other OS such as redhat have already patched this in their releases. A demonstration of the issue can be found in this pastebin: https://pastebin.canonical.com/p/qRfrpHXwGs/ VMWare Issue: https://kb.vmware.com/s/article/53609 Cheers! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dmidecode/+bug/1851676/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1850654] Re: update-initramfs complains of missing amdgpu firmware files
Confirmed that raven_kicker_rlc.bin is present in both 1.173.12 and 1.183.2. ** Tags added: verification-done-bionic verification-done-eoan -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1850654 Title: update-initramfs complains of missing amdgpu firmware files Status in linux package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: New Status in linux source package in Bionic: Invalid Status in linux-firmware source package in Bionic: Fix Committed Status in linux source package in Eoan: Confirmed Status in linux-firmware source package in Eoan: Fix Committed Bug description: SRU Justification Impact: With 5.3 update-initramfs reports several missing amdgpu firmware files: update-initramfs: Generating /boot/initrd.img-5.3.0-19-generic W: Possible missing firmware /lib/firmware/amdgpu/vega20_ta.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/raven_kicker_rlc.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/navi10_mes.bin for module amdgpu Of these, only raven_kicker_rlc.bin has been added to upstream linux- firmware. Fix: Add raven_kicker_rlc.bin to linux firmware, and remove the other files from modinfo for amdgpu. Test Case: Once fixed, the warnings from update-initramfs should be gone. Regression Potential: Adding a missing firmware is unlikely to break any working hardware. Removing the other missing files from modinfo will not cause regressions either, however if the firmware is added later update-initramfs will not add the files to the initramfs until the firmware is added back to modinfo. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850654/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1850896] Re: eoan/linux-raspi2: 5.3.0-1011.12 -proposed tracker
We have been notified this kernel will be re-spin, so we'll skip this one. ** Changed in: kernel-sru-workflow/certification-testing Status: In Progress => Incomplete -- 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/1850896 Title: eoan/linux-raspi2: 5.3.0-1011.12 -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: Incomplete 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 verification-testing series: Fix Released Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 source package in Eoan: Confirmed 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: 1850486 packages: main: linux-raspi2 meta: linux-meta-raspi2 phase: Testing phase-changed: Friday, 01. November 2019 15:21 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Stalled -- testing FAILED variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1850896/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1851676] Re: dmidecode does not byte-swap for SMBIOS >= 2.6
** Summary changed: - dmidecode decodes /sys/class/dmi/id/product_serial incorrectly + dmidecode does not byte-swap for SMBIOS >= 2.6 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dmidecode in Ubuntu. https://bugs.launchpad.net/bugs/1851676 Title: dmidecode does not byte-swap for SMBIOS >= 2.6 Status in dmidecode package in Ubuntu: New Bug description: Hi, On VMWare 6.5 and higher (HW version 13 and higher) when decoding /sys/class/dmi/id/product_serial dmidecode produces an output whereby the first 16 characters have been reversed in comparison to /sys/class/dmi/id/product_uuid. This manifests itself by breaking provisioning in Kubernetes and could cause other issues down the line. Other OS such as redhat have already patched this in their releases. A demonstration of the issue can be found in this pastebin: https://pastebin.canonical.com/p/qRfrpHXwGs/ VMWare Issue: https://kb.vmware.com/s/article/53609 Cheers! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dmidecode/+bug/1851676/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1847250] Re: update firmware for sound sof driver to fix the hang issue on several Dell machines
Hui: Can you confirm that the proper firmware is present, then mark both this and bug 1850739 as verified? Thanks! ** Tags removed: block-proposed ** Tags removed: verification-failed-bionic verification-failed-disco -- 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/1847250 Title: update firmware for sound sof driver to fix the hang issue on several Dell machines Status in HWE Next: New Status in OEM Priority Project: Confirmed Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Bionic: Fix Committed Status in linux-firmware source package in Disco: Fix Committed Status in linux-firmware source package in Eoan: Fix Released Bug description: We expect this firmware update could be released with 19.10 [Impact] We have a couple of Dell machines, after installing the system, it will hang randomly, and this issue was reported by factory, they met this issue a couple of times. Then we tried to reproduce this issue, finally reproduced it. [Fix] Intel debugged this issue as well, and they provided 4 kernel patches and a new firmware, we tested them, they really can fix the issue. And the patches were sent the SRU already, now it is time to update firmware. [Test Case] Install the system repeatedly and there is no hang issue anymore. [Regression Risk] Low, Intel told us there is no ABI change for the firmware, so it is safe to run this firmware both with the old driver (not applied those 4 patches) and the new driver (applied those 4 patches). To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1847250/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1850896] Re: eoan/linux-raspi2: 5.3.0-1011.12 -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: 1850486 packages: main: linux-raspi2 meta: linux-meta-raspi2 phase: Testing phase-changed: Friday, 01. November 2019 15:21 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - certification-testing: Ongoing -- testing in progress + certification-testing: Stalled -- testing FAILED variant: debs -- 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/1850896 Title: eoan/linux-raspi2: 5.3.0-1011.12 -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: Incomplete 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 verification-testing series: Fix Released Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 source package in Eoan: Confirmed 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: 1850486 packages: main: linux-raspi2 meta: linux-meta-raspi2 phase: Testing phase-changed: Friday, 01. November 2019 15:21 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Stalled -- testing FAILED variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1850896/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1850486] Re: eoan/linux: 5.3.0-21.22 -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 bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed - phase: Testing - phase-changed: Wednesday, 30. October 2019 18:13 UTC + phase: Holding before Promote to Updates + phase-changed: Friday, 08. November 2019 17:10 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - certification-testing: Ongoing -- testing in progress + promote-to-updates: Holding -- cycle not ready to release trackers: bionic/linux-hwe-edge: bug 1850485 eoan/linux-aws: bug 1850477 eoan/linux-azure: bug 1850480 eoan/linux-gcp: bug 1850481 eoan/linux-kvm: bug 1850482 eoan/linux-oracle: bug 1850483 eoan/linux-raspi2: bug 1850896 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1850486 Title: eoan/linux: 5.3.0-21.22 -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-lrm 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: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Eoan: Confirmed 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 bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Holding before Promote to Updates phase-changed: Friday, 08. November 2019 17:10 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Holding -- cycle not ready to release trackers: bionic/linux-hwe-edge: bug 1850485 eoan/linux-aws: bug 1850477 eoan/linux-azure: bug 1850480 eoan/linux-gcp: bug 1850481 eoan/linux-kvm: bug 1850482 eoan/linux-oracle: bug 1850483 eoan/linux-raspi2: bug 1850896 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1850486/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1850486] Re: eoan/linux: 5.3.0-21.22 -proposed tracker
Hardware Certification have completed testing this -proposed kernel. No regressions were observed, results are available here: http://people.canonical.com/~hwcert/sru-testing/eoan/5.3.0-21.22/eoan- proposed-published.html ** Tags added: certification-testing-passed ** Changed in: kernel-sru-workflow/certification-testing Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1850486 Title: eoan/linux: 5.3.0-21.22 -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-lrm 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: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Eoan: Confirmed 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 bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Holding before Promote to Updates phase-changed: Friday, 08. November 2019 17:10 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Holding -- cycle not ready to release trackers: bionic/linux-hwe-edge: bug 1850485 eoan/linux-aws: bug 1850477 eoan/linux-azure: bug 1850480 eoan/linux-gcp: bug 1850481 eoan/linux-kvm: bug 1850482 eoan/linux-oracle: bug 1850483 eoan/linux-raspi2: bug 1850896 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1850486/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1850572] Re: AMD Prairie Falcon platform failed to boot up
** Changed in: linux (Ubuntu Bionic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1850572 Title: AMD Prairie Falcon platform failed to boot up Status in HWE Next: New Status in linux package in Ubuntu: Invalid Status in linux-oem package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Committed Status in linux-oem source package in Bionic: Fix Committed Bug description: [Impact] AMD Prairie Falcon is the AME Embedded variant of Stoney. It fails to boot up without disable its CGCG feature. Set 'amdgpu.cg_mask=0xfffb' kernel parameter to disable CGCG [Fix] Suggestion from AMD that we have to cherry pick this commit which is included in v4.16 fb4bbba27753 drm/amdgpu: re-enable CGCG on CZ and disable on ST [Test] Verified on AMD Prairie Falcon platform, system boots up normally. [Regression Potential] Low, this commit has been included for more than one and a half year in the upstream, should be pretty safe to include it. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1850572/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1843487] Re: UIO: mutex used in interrupt handler causes crash
** Changed in: linux (Ubuntu Bionic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1843487 Title: UIO: mutex used in interrupt handler causes crash Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: Fix Committed Bug description: Running: Bionic Beaver Ubuntu 4.15.0-62.69-generic 4.15.18 Problem since: Ubuntu-4.15.0-59.66 In commit 725bbc87 on 2/13/2019 in uio.c a mutex_lock was added to uio_interrupt. This results in a "scheduling while atomic" error if someone else owns the mutex at the time it is invoked. The following commit in the kernel mainline appears to fix this issue: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=3d27c4de8d4fb2d4099ff324671792aa2578c6f9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1843487/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1850600] Re: Suppress "hid_field_extract() called with n (192) > 32!" message floods
** Changed in: linux (Ubuntu Bionic) Status: Confirmed => Fix Committed ** Changed in: linux (Ubuntu Disco) Status: Confirmed => Fix Committed ** Changed in: linux (Ubuntu Eoan) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1850600 Title: Suppress "hid_field_extract() called with n (192) > 32!" message floods Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem package in Ubuntu: Confirmed Status in linux-oem-osp1 package in Ubuntu: Confirmed Status in linux source package in Bionic: Fix Committed Status in linux-oem source package in Bionic: Fix Committed Status in linux-oem-osp1 source package in Bionic: Confirmed Status in linux source package in Disco: Fix Committed Status in linux-oem-osp1 source package in Disco: Won't Fix Status in linux source package in Eoan: Fix Committed Status in linux-oem-osp1 source package in Eoan: Won't Fix Bug description: [Impact] Intel Sensor Hub floods dmesg with "hid_field_extract() called with n (192) > 32!". [Fix] Use warn_once to workaround the issue. [Test] After applying these patches, there's only one warning message in dmesg. [Regression Potential] Low. It only changes printk macros for HID, no actual functional change. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1850600/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1849682] Re: [REGRESSION] md/raid0: cannot assemble multi-zone RAID0 with default_layout setting
The disco story is not so pretty: [0.00] Linux version 5.0.0-34-generic (buildd@lgw01-amd64-051) (gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1)) #36~18.04.1-Ubuntu SMP Wed Oct 30 08:08:56 UTC 2019 (Ubuntu 5.0.0-34.36~18.04.1-generic 5.0.21) [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-5.0.0-34-generic root=UUID=e3626652-82d8-4e95-a6d7-e4920d7941b6 ro console=tty1 console=ttyS0 [0.00] KERNEL supported cpus: [0.00] Intel GenuineIntel [0.00] AMD AuthenticAMD [0.00] Hygon HygonGenuine [0.00] Centaur CentaurHauls [0.00] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers' [0.00] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers' [0.00] x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers' [0.00] x86/fpu: xstate_offset[2]: 576, xstate_sizes[2]: 256 [0.00] x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, using 'standard' format. [0.00] BIOS-provided physical RAM map: [0.00] BIOS-e820: [mem 0x-0x0009fbff] usable [0.00] BIOS-e820: [mem 0x0009fc00-0x0009] reserved [0.00] BIOS-e820: [mem 0x000f-0x000f] reserved [0.00] BIOS-e820: [mem 0x0010-0x1ffd7fff] usable [0.00] BIOS-e820: [mem 0x1ffd8000-0x1fff] reserved [0.00] BIOS-e820: [mem 0xfeffc000-0xfeff] reserved [0.00] BIOS-e820: [mem 0xfffc-0x] reserved [0.00] NX (Execute Disable) protection: active [0.00] SMBIOS 2.8 present. [0.00] DMI: OpenStack Foundation OpenStack Nova, BIOS 1.10.2-1ubuntu1 04/01/2014 [0.00] Hypervisor detected: KVM [0.00] kvm-clock: Using msrs 4b564d01 and 4b564d00 [0.00] kvm-clock: cpu 0, msr e601001, primary cpu clock [0.00] kvm-clock: using sched offset of 79214193145 cycles [0.02] clocksource: kvm-clock: mask: 0x max_cycles: 0x1cd42e4dffb, max_idle_ns: 881590591483 ns [0.04] tsc: Detected 2298.666 MHz processor [0.002336] last_pfn = 0x1ffd8 max_arch_pfn = 0x4 [0.002446] x86/PAT: Configuration [0-7]: WB WC UC- UC WB WP UC- WT [0.008265] found SMP MP-table at [mem 0x000f6a60-0x000f6a6f] [0.008362] check: Scanning 1 areas for low memory corruption [0.008413] Using GB pages for direct mapping [0.008561] RAMDISK: [mem 0x1d8fb000-0x1ecacfff] [0.008579] ACPI: Early table checksum verification disabled [0.008637] ACPI: RSDP 0x000F6860 14 (v00 BOCHS ) [0.008640] ACPI: RSDT 0x1FFE1505 2C (v01 BOCHS BXPCRSDT 0001 BXPC 0001) [0.008646] ACPI: FACP 0x1FFE1419 74 (v01 BOCHS BXPCFACP 0001 BXPC 0001) [0.008654] ACPI: DSDT 0x1FFE0040 0013D9 (v01 BOCHS BXPCDSDT 0001 BXPC 0001) [0.008657] ACPI: FACS 0x1FFE 40 [0.008660] ACPI: APIC 0x1FFE148D 78 (v01 BOCHS BXPCAPIC 0001 BXPC 0001) [0.009155] No NUMA configuration found [0.009157] Faking a node at [mem 0x-0x1ffd7fff] [0.009167] NODE_DATA(0) allocated [mem 0x1ffad000-0x1ffd7fff] [0.009417] Zone ranges: [0.009418] DMA [mem 0x1000-0x00ff] [0.009420] DMA32[mem 0x0100-0x1ffd7fff] [0.009421] Normal empty [0.009422] Device empty [0.009423] Movable zone start for each node [0.009427] Early memory node ranges [0.009428] node 0: [mem 0x1000-0x0009efff] [0.009429] node 0: [mem 0x0010-0x1ffd7fff] [0.009433] Zeroed struct page in unavailable ranges: 98 pages [0.009434] Initmem setup node 0 [mem 0x1000-0x1ffd7fff] [0.013701] ACPI: PM-Timer IO Port: 0x608 [0.013719] ACPI: LAPIC_NMI (acpi_id[0xff] dfl dfl lint[0x1]) [0.013776] IOAPIC[0]: apic_id 0, version 17, address 0xfec0, GSI 0-23 [0.013778] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) [0.013780] ACPI: INT_SRC_OVR (bus 0 bus_irq 5 global_irq 5 high level) [0.013781] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) [0.013783] ACPI: INT_SRC_OVR (bus 0 bus_irq 10 global_irq 10 high level) [0.013784] ACPI: INT_SRC_OVR (bus 0 bus_irq 11 global_irq 11 high level) [0.013789] Using ACPI (MADT) for SMP configuration information [0.013792] smpboot: Allowing 1 CPUs, 0 hotplug CPUs [0.013814] PM: Registered nosave memory: [mem 0x-0x0fff] [0.013815] PM: Registered nosave memory: [mem 0x0009f000-0x0009] [0.013816] PM: Registered nosave memory: [mem 0x000a-0x000e] [0.013817] PM: Registered nosave memory: [mem 0x000f-0x000f] [0.013819] [mem 0x2000-0xfeffbfff] available for PCI devices [0.013820] Booting paravirtualized ke
[Kernel-packages] [Bug 1828978] Re: NFSv4.1: Interrupted connections cause high bandwidth RPC ping-pong between client and server
** Changed in: linux (Ubuntu Disco) 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/1828978 Title: NFSv4.1: Interrupted connections cause high bandwidth RPC ping-pong between client and server Status in linux package in Ubuntu: Fix Released Status in linux source package in Disco: Fix Committed Bug description: BugLink: https://bugs.launchpad.net/bugs/1828978 [Impact] There is a bug in NFS v4.1 that causes a large amount of RPC calls between a client and server when a previous RPC call is interrupted. This uses a large amount of bandwidth and can saturate the network. The symptoms are so: * On NFS clients: Attempts to access mounted NFS shares associated with the affected server block indefinitely. * On the network: A storm of repeated RPCs between NFS client and server uses a lot of bandwidth. Each RPC is acknoledged by the server with an NFS4ERR_SEQ_MISORDERED error. * Other NFS clients connected to the same NFS server: Performance drops dramatically. This occurs during a "false retry", when a client attempts to make a new RPC call using a slot+sequence number that references an older, cached call. This happens when a user process interrupts an RPC call that is in progress. [Fix] This was fixed in 5.1 upstream with the below commit: commit 3453d5708b33efe76f40eca1c0ed60923094b971 Author: Trond Myklebust Date: Wed Jun 20 17:53:34 2018 -0400 Subject: NFSv4.1: Avoid false retries when RPC calls are interrupted The fix is to pre-emptively increment the sequence number if an RPC call is interrupted, and to address corner cases we interpret the NFS4ERR_SEQ_MISORDERED error as a sign we need to locate an approperiate sequence number between the value we sent, and the last successfully acked SEQUENCE call. Commit 3453d5708b33efe76f40eca1c0ed60923094b971 is a clean cherry-pick to disco. [Testcase] This is difficult to reproduce on test systems, and has instead been verified on a production NFS v4.1 system in a customer environment. This server is heavily trafficked and has a large number of different NFS clients connected to it. I have built a test kernel that contains the above patch, and also patches for Bug 1842037. It is available here: https://launchpad.net/~mruffell/+archive/ubuntu/sf241068-test Note that the above kernel is for bionic HWE, and not explicitly disco. Discussion about the patch validation can be found at the bottom of Bug 1842037. On unpatched kernels, expect to see the symptoms mentioned in Impact, and on patched systems, everything working as intended. [Regression Potential] The changes are localised to NFS v4.1 only, and other versions of NFS are not affected. If a regression occurs, users can downgrade NFS versions to v4.0 or v3.x until a fix is made. The changes only impact when connections are interrupted, and under typical blue sky scenarios would not be invoked. There have been no fixup commits or commits near the requested commit in newer kernels, which points to this commit fixing the issue, and adopted by the community. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1828978/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1842037] Re: SUNRPC: Use after free when GSSD credentials are invalid causes oops
** Changed in: linux (Ubuntu Disco) 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/1842037 Title: SUNRPC: Use after free when GSSD credentials are invalid causes oops Status in linux package in Ubuntu: Fix Released Status in linux source package in Disco: Fix Committed Bug description: BugLink: https://bugs.launchpad.net/bugs/1842037 [Impact] There is a use after free which normally causes a null pointer dereference when NFS clients send invalid credentials via GSSD to a NFS server which has shares protected by kerberos krb5* security. The call trace is below: BUG: unable to handle kernel NULL pointer dereference at 0098 Call Trace: rpc_check_timeout+0x22/0xe0 [sunrpc] call_decode+0x12c/0x190 [sunrpc] __rpc_execute+0x7a/0x340 [sunrpc] rpc_execute+0xa3/0xb0 [sunrpc] rpc_run_task+0xf7/0x140 [sunrpc] nfs4_proc_get_lease_time+0xf3/0x130 [nfsv4] nfs41_setup_state_renewal+0x3d/0x90 [nfsv4] ? nfs4_realloc_slot_table+0x5b/0x130 [nfsv4] ? nfs4_setup_session_slot_tables+0x77/0xc0 [nfsv4] nfs41_finish_session_reset+0x26/0x30 [nfsv4] nfs41_init_clientid+0x44/0x70 [nfsv4] nfs4_establish_lease+0x61/0xa0 [nfsv4] ? nfs4_handle_reclaim_lease_error+0x108/0x130 [nfsv4] nfs4_state_manager+0x1b1/0x750 [nfsv4] ? kernel_sigaction+0x43/0xe0 nfs4_run_state_manager+0x24/0x40 [nfsv4] kthread+0x120/0x140 ? nfs4_state_manager+0x750/0x750 [nfsv4] ? __kthread_parkme+0x70/0x70 ret_from_fork+0x35/0x40 This then causes outages on a heavily trafficked NFS server and no one can access their shares until the server is rebooted. [Fix] The fix comes in the following two commits: commit cea57789e4081870ac3498fbefabbbd0d0fd8434 Author: Trond Myklebust Date: Sat Mar 9 16:06:47 2019 -0500 Subject: SUNRPC: Clean up commit 7987b694ade8cc465ce10fb3dceaa614f13ceaf3 Author: Trond Myklebust Date: Wed May 29 12:49:52 2019 -0400 Subject: SUNRPC: Fix a use after free when a server rejects the RPCSEC_GSS credential There is a small subtlety to be addressed here. 7987b694ade8cc465ce10fb3dceaa614f13ceaf3 is marked as "Fixes" cea57789e4081870ac3498fbefabbbd0d0fd8434, and cea57789e4081870ac3498fbefabbbd0d0fd8434 is not present in the disco kernel. The code path which triggers the use after free can still be reached without cea57789e4081870ac3498fbefabbbd0d0fd8434 being present, and applying both commits resolves the problem, while still maintaining as little backporting as necessary. Please note, both commits have been backported. cea57789e4081870ac3498fbefabbbd0d0fd8434 required a small change to the final comment, as well as some minor context adjustments in the final hunk. 7987b694ade8cc465ce10fb3dceaa614f13ceaf3 required medium to heavy backporting. The upstream patch uses a switch statement based on error codes, while the disco kernel uses a goto and label type architecture. The commits in the middle were numerous and completely unrelated, so I backported the commit to use goto and labels. Please review this backport a little more closely than you normally do, but it has been tested, and I believe the code to be sound. cea57789e4081870ac3498fbefabbbd0d0fd8434 landed in 5.1 upstream. 7987b694ade8cc465ce10fb3dceaa614f13ceaf3 landed in 5.2 upstream. 7987b694ade8cc465ce10fb3dceaa614f13ceaf3 was also selected for upstream -stable, in 5.1.9, and was omitted from disco stable updates process, probably because of the patch not cleanly applying and requiring the backport and infrastructure provided in cea57789e4081870ac3498fbefabbbd0d0fd8434. [Testcase] This is difficult to reproduce on test systems, and has instead been verified on a production NFS v4.1 system in a customer environment. This server is heavily trafficked and has a large number of different NFS clients connected to it. I have built a test kernel that contains the above patch, and also patches for Bug 1828978. It is available here: https://launchpad.net/~mruffell/+archive/ubuntu/sf241068-test Note that the above kernel is for bionic HWE, and not explicitly disco. Discussion about the patch validation can be found at the bottom of Bug 1842037. On unpatched kernels, expect to see the symptoms mentioned in Impact, and on patched systems, everything working as intended. [Regression Potential] The changes are limited to users of sunrpc and the change itself is limited to cases where the RPCSEC_GSS credential is rejected. Under blue skies scenarios, the code should only be triggered when misbehaving clients do not keep their authentication tickets up to date. In case of regression, misbehaving clients may cause outages on services which use sunrpc. In which case, the server administrator would
[Kernel-packages] [Bug 1848555] Re: Add Intel Comet Lake ethernet support
** Changed in: linux (Ubuntu Bionic) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1848555 Title: Add Intel Comet Lake ethernet support Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: Fix Committed Status in linux-oem package in Ubuntu: New Status in linux-oem-osp1 package in Ubuntu: New Status in linux source package in Bionic: Fix Committed Status in linux-oem source package in Bionic: New Status in linux-oem-osp1 source package in Bionic: Fix Committed Status in linux source package in Disco: Incomplete Status in linux-oem source package in Disco: Won't Fix Status in linux-oem-osp1 source package in Disco: Won't Fix Status in linux source package in Eoan: Incomplete Status in linux-oem source package in Eoan: Won't Fix Status in linux-oem-osp1 source package in Eoan: Won't Fix Bug description: [Impact] e1000e.ko doesn't load for Intel CML ethernet. [Fix] Add missing ID for the device. [Test] The driver loads and works once the ID is added. [Regression Potential] Minimal. Only adds some IDs, no functional change at all. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1848555/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1849682] Re: [REGRESSION] md/raid0: cannot assemble multi-zone RAID0 with default_layout setting
I can 100% reproduce this on 5.0.0-34, but not at all on 5.0.0-32, so marking verification-failed. ** Tags removed: verification-needed-disco ** Tags added: verification-failed-disco -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1849682 Title: [REGRESSION] md/raid0: cannot assemble multi-zone RAID0 with default_layout setting Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Fix Committed Status in linux source package in Disco: Incomplete Status in linux source package in Eoan: Incomplete Status in linux source package in Focal: Incomplete Bug description: This bug tracks the temporary revert of the upstream fix for a corruption issue. Bug 1850540 tracks the re-application of that fix once we have a full solution. Users of RAID0 arrays are susceptible to a corruption issue if: - The members of the RAID array are not all the same size[*] - Data has been written to the array while running kernels < 3.14 *and* >= 3.14. This is because of an change in v3.14 that accidentally changed how data was written - as described in the upstream commit message: https://github.com/torvalds/linux/commit/c84a1372df929033cb1a0441fb57bd3932f39ac9 To summarize, upstream is dealing with this by adding a versioned layout in v5.4, and that is being backported to stable kernels - which is why we're now seeing it. Layout version 1 is the pre-3.14 layout, version 2 is post 3.14. Mixing version 1 & version 2 layouts can cause corruption. However, unless a layout-version-aware kernel *created* the array, there's no way for the kernel to know which version(s) was used to write the existing data. This undefined mode is considered "Version 0", and the kernel will now refuse to start these arrays w/o user intervention. The user experience is pretty awful here. A user upgrades to the next SRU and all of a sudden their system stops at an (initramfs) prompt. A clueful user can spot something like the following in dmesg: Here's the message which , as you can see from the log in Comment #1, is hidden in a ton of other messages: [ 72.720232] md/raid0:md0: cannot assemble multi-zone RAID0 with default_layout setting [ 72.728149] md/raid0: please set raid.default_layout to 1 or 2 [ 72.733979] md: pers->run() failed ... mdadm: failed to start array /dev/md0: Unknown error 524 What that is trying to say is that you should determine if your data - specifically the data toward the end of your array - was most likely written with a pre-3.14 or post-3.14 kernel. Based on that, reboot with the kernel parameter raid0.default_layout=1 or raid0.default_layout=2 on the kernel command line. And note it should be *raid0.default_layout* not *raid.default_layout* as the message says - a fix for that message is now queued for stable: https://github.com/torvalds/linux/commit/3874d73e06c9b9dc15de0b7382fc223986d75571) IMHO, we should work with upstream to create a web page that clearly walks the user through this process, and update the error message to point to that page. I'd also like to see if we can detect this problem *before* the user reboots (debconf?) and help the user fix things. e.g. "We detected that you have RAID0 arrays that maybe susceptible to a corruption problem", guide the user to choosing a layout, and update the mdadm initramfs hook to poke the answer in via sysfs before starting the array on reboot. Note that it also seems like we should investigate backporting this to < 3.14 kernels. Imagine a user switching between the trusty HWE kernel and the GA kernel. References from users of other distros: https://blog.icod.de/2019/10/10/caution-kernel-5-3-4-and-raid0-default_layout/ https://www.linuxquestions.org/questions/linux-general-1/raid-arrays-not-assembling-4175662774/ [*] Which surprisingly is not the case reported in this bug - the user here had a raid0 of 8 identically-sized devices. I suspect there's a bug in the detection code somewhere. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849682/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1849720] Re: KVM with e1000e and WinGuest Host OS on kernel 5.3 (ok with 5.0)
@Christian, I'll try some more kernels over the weekend and let you know the results. I can confirm that switching my NIC to "virtio" from "e1e" allows me to run my vm on kernel 5.3.0-20-generic. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1849720 Title: KVM with e1000e and WinGuest Host OS on kernel 5.3 (ok with 5.0) Status in linux package in Ubuntu: Confirmed Status in qemu package in Ubuntu: In Progress Bug description: After upgrading to Ubuntu 19.10 I noticed that all of my Windows Servers VMs would cause a hard crash on the Host OS shortly after starting up the VM. I tracked it down to the Guest OS attempting to use the Network Connection, and if I disabled the virtual NIC for the VM, everything runs OK (albeit without a working network connection for the Guest OS). Note that I'm just using the built in virtual network called "default" that get's installed by default and uses NAT forwarding. I believe the problem is related to AppArmor, as I noticed some errors present in various log files. Unfortunately, due to a time critical project I had to roll back to Ubuntu 19.04 and didn't capture any of the log files. I did, however, find another user on Reddit with the exact same problems that I encountered and he agreed to let me post the log files. Here are what are think are the relevant pieces from the log files: === Oct 22 22:59:23 brian-pc dnsmasq[2178]: exiting on receipt of SIGTERM Oct 22 22:59:23 brian-pc kernel: [ 67.001284] device virbr0-nic left promiscuous mode Oct 22 22:59:23 brian-pc kernel: [ 67.001298] virbr0: port 1(virbr0-nic) entered disabled state Oct 22 22:59:23 brian-pc NetworkManager[3557]: [1571799563.3862] device (virbr0-nic): released from master device virbr0 Oct 22 22:59:23 brian-pc gnome-shell[4401]: Removing a network device that was not added Oct 22 22:59:23 brian-pc gnome-shell[2463]: Removing a network device that was not added Oct 22 22:59:23 brian-pc avahi-daemon[1621]: Interface virbr0.IPv4 no longer relevant for mDNS. Oct 22 22:59:23 brian-pc avahi-daemon[1621]: Leaving mDNS multicast group on interface virbr0.IPv4 with address 192.168.122.1. Oct 22 22:59:23 brian-pc avahi-daemon[1621]: Withdrawing address record for 192.168.122.1 on virbr0. Oct 22 22:59:23 brian-pc NetworkManager[3557]: [1571799563.6859] device (virbr0): state change: activated -> unmanaged (reason 'unmanaged', sys-iface-state: 'removed') Oct 22 22:59:23 brian-pc gnome-shell[2463]: Removing a network device that was not added Oct 22 22:59:23 brian-pc gnome-shell[4401]: Removing a network device that was not added Oct 22 22:59:23 brian-pc dbus-daemon[1610]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.192' (uid=0 pid=3557 comm="/usr/sbin/NetworkManager --no-daemon " label="unconfined") Oct 22 22:59:23 brian-pc systemd[1]: Starting Network Manager Script Dispatcher Service... Oct 22 22:59:23 brian-pc gnome-shell[2463]: Object NM.ActiveConnection (0x55ccfb376e50), has been already deallocated — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Oct 22 22:59:23 brian-pc gnome-shell[2463]: == Stack trace for context 0x55ccfb8d15f0 == Oct 22 22:59:23 brian-pc gnome-shell[2463]: #0 55ccfbc736c0 i resource:///org/gnome/shell/ui/status/network.js:1329 (7f52226be550 @ 56) Oct 22 22:59:23 brian-pc gnome-shell[2463]: #1 55ccfbc73628 i resource:///org/gnome/shell/ui/status/network.js:1346 (7f52226be5e0 @ 113) Oct 22 22:59:23 brian-pc gnome-shell[2463]: #2 55ccfbc73588 i resource:///org/gnome/shell/ui/status/network.js:2049 (7f52226c1940 @ 216) Oct 22 22:59:23 brian-pc gnome-shell[2463]: #3 55ccfbc734f0 i resource:///org/gnome/shell/ui/status/network.js:1853 (7f52226bfee0 @ 134) Oct 22 22:59:23 brian-pc gnome-shell[2463]: #4 55ccfbc73430 i self-hosted:979 (7f522262dee0 @ 440) Oct 22 22:59:23 brian-pc gnome-shell[2463]: JS ERROR: TypeError: connection.get_setting_ip4_config is not a function#012_isHotSpotMaster@resource:///org/gnome/shell/ui/status/network.js:1333:25#012getIndicatorIcon@resource:///org/gnome/shell/ui/status/network.js:1346:13#012_updateIcon@resource:///org/gnome/shell/ui/status/network.js:2049:52#012_syncVpnConnections@resource:///org/gnome/shell/ui/status/network.js:1853:9 Oct 22 22:59:23 brian-pc gnome-shell[2463]: JS ERROR: TypeError: connectionSettings is null#012_updateConnection@resource:///org/gnome/shell/ui/status/network.js:1922:9 Oct 22 22:59:23 brian-pc gnome-shell[4401]: JS ERROR: TypeError: connectionSettings is null#012_updateConnecti
[Kernel-packages] [Bug 1847969] Re: [Packaging] Support building Flattened Image Tree (FIT) kernels
** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1847969 Title: [Packaging] Support building Flattened Image Tree (FIT) kernels Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Fix Committed Status in linux source package in Bionic: Fix Committed Bug description: [Impact] Flexible and powerful format based on Flattened Image Tree -- FIT (similar to Flattened Device Tree). It allows the use of images with multiple components (several kernels, ramdisks, etc.), with contents protected by SHA1, MD5 or CRC32, etc. More details: https://gitlab.denx.de/u-boot/u-boot/blob/master/doc/uImage.FIT/howto.txt The packaging changes will add support for building a FIT kernel binary blob which can be subsequently signed. These FIT-signed kernels will be consumed by snapcraft recipes to build kernel snaps for platforms with U-Boot bootloader enforcing secure boot. [Regression Potential] Minimal. This bug is for tracking purposes only, do not triage. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1847969/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1851507] Re: bionic/linux-oem: 4.15.0-1062.71 -proposed tracker
Kernel deb testing completes, no regressions found. Ready for Updates. Results here: https://trello.com/c/9I46ywkj/238-oem-linux- image-4150-1062-oem-4150-106271 ** Changed in: kernel-sru-workflow/certification-testing Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1851507 Title: bionic/linux-oem: 4.15.0-1062.71 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress 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-lrm 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: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-oem package in Ubuntu: Invalid Status in linux-oem source package in Bionic: Confirmed 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: 1849855 packages: lrm: linux-restricted-modules-oem main: linux-oem meta: linux-meta-oem signed: linux-signed-oem phase: Testing phase-changed: Thursday, 07. November 2019 17:46 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1851507/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1851507] Re: bionic/linux-oem: 4.15.0-1062.71 -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: 1849855 packages: lrm: linux-restricted-modules-oem main: linux-oem meta: linux-meta-oem signed: linux-signed-oem phase: Testing phase-changed: Thursday, 07. November 2019 17:46 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress - certification-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1851507 Title: bionic/linux-oem: 4.15.0-1062.71 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress 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-lrm 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: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-oem package in Ubuntu: Invalid Status in linux-oem source package in Bionic: Confirmed 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: 1849855 packages: lrm: linux-restricted-modules-oem main: linux-oem meta: linux-meta-oem signed: linux-signed-oem phase: Testing phase-changed: Thursday, 07. November 2019 17:46 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1851507/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838245] Re: dkms script is missing function find_module
Hello Alex, or anyone else affected,
Accepted dkms into eoan-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/dkms/2.7.1-4ubuntu2.1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed. Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-eoan to verification-done-eoan. If it does not fix
the bug for you, please add a comment stating that, and change the tag
to verification-failed-eoan. In either case, without details of your
testing we will not be able to proceed.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance for helping!
N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.
** Changed in: dkms (Ubuntu Eoan)
Status: Triaged => Fix Committed
** Tags added: verification-needed verification-needed-eoan
** Changed in: dkms (Ubuntu Focal)
Status: Triaged => Fix Released
** Changed in: dkms (Ubuntu Disco)
Status: New => Fix Committed
** Tags added: verification-needed-disco
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dkms in Ubuntu.
https://bugs.launchpad.net/bugs/1838245
Title:
dkms script is missing function find_module
Status in DKMS:
Confirmed
Status in dkms package in Ubuntu:
Fix Released
Status in dkms source package in Bionic:
Fix Released
Status in dkms source package in Disco:
Fix Committed
Status in dkms source package in Eoan:
Fix Committed
Status in dkms source package in Focal:
Fix Released
Bug description:
update for SRU process:
[Impact]
1. dkms script is missing function find_module
2. priority of OBSOLETE_BY should higher than "force". #89
https://github.com/dell/dkms/issues/89
[Test case]
install the dkms which already patched (also can be found in my ppa[1])
1. install a dkms which for a kernel module system already installed.
e.g. ath10k of my testing ppa : [1]
1.1. the dkms can be installed well.
2. install a dkms which has OBSOLETE_BY and FORCE
e.g.ath10k of my testing ppa : [1] (source code in [2])
- the target dkms defined OBSOLETE_BY and FORCE
- user install dkms on a system which installed kernel version less than
OBSOLETE_BY and another kernel higher than OBSOLETE_BY
- the dkms can be installed well.
[Regression potential]
medium as it touched the version sanity. This change correct the code logic
and land one more change from upstream as well.
The logic has been verified by #5 and me.
Building a kernel module using dkms in Linux Mint 19.1 shows the following
error:
Running module version sanity check.
/usr/sbin/dkms: Zeile 784: find_module: Befehl nicht gefunden
modinfo: ERROR: missing module or filename.
Checking the file the function is indeed missing and another user
confirmed, that it was removed at some point:
https://github.com/linuxmint/linuxmint/issues/142
Possible solution: Readd
find_module()
{
# tree = $1
# module = $2
find "$1" -name "$2$module_uncompressed_suffix" -o -name
"$2$module_suffix" -type f
return $?
}
as found in https://github.com/dell/dkms/blob/master/dkms
To manage notifications about this bug go to:
https://bugs.launchpad.net/dkms/+bug/1838245/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1849051] Re: xenial/linux: 4.4.0-167.196 -proposed tracker
Kernel deb testing completes, no regressions found. Ready for Updates. Results here: https://trello.com/c/z1d2HQyX/222-xenial-linux- image-440-167-generic-440-167196 ** Changed in: kernel-sru-workflow/certification-testing Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1849051 Title: xenial/linux: 4.4.0-167.196 -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 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: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed 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 bugs-spammed: true packages: main: linux meta: linux-meta signed: linux-signed phase: Holding before Promote to Updates phase-changed: Friday, 08. November 2019 19:20 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Holding -- cycle not ready to release trackers: trusty/linux-aws: bug 1849048 trusty/linux-lts-xenial: bug 1849049 xenial/linux-aws: bug 1849041 xenial/linux-fips: bug 1849047 xenial/linux-kvm: bug 1849042 xenial/linux-raspi2: bug 1849044 xenial/linux-snapdragon: bug 1849046 xenial/linux/caracalla-kernel: bug 1849036 xenial/linux/pc-kernel: bug 1849037 xenial/linux/stlouis-kernel: bug 1849038 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1849051/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1851876] [NEW] Bionic update: upstream stable patchset 2019-11-08
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from a mainline/stable Linux tree or
a minimally backported form of that patch. The following upstream
stable patches should be included in the Ubuntu kernel:
upstream stable patchset 2019-11-08
Ported from the following upstream stable releases:
v4.14.151, v4.19.81
from git://git.kernel.org/
scsi: ufs: skip shutdown if hba is not powered
scsi: megaraid: disable device when probe failed after enabled device
scsi: qla2xxx: Fix unbound sleep in fcport delete path.
ARM: OMAP2+: Fix missing reset done flag for am3 and am43
ieee802154: ca8210: prevent memory leak
ARM: dts: am4372: Set memory bandwidth limit for DISPC
net: dsa: qca8k: Use up to 7 ports for all operations
MIPS: dts: ar9331: fix interrupt-controller size
xen/efi: Set nonblocking callbacks
nl80211: fix null pointer dereference
mac80211: fix txq null pointer dereference
mips: Loongson: Fix the link time qualifier of 'serial_exit()'
net: hisilicon: Fix usage of uninitialized variable in function
mdio_sc_cfg_reg_write()
namespace: fix namespace.pl script to support relative paths
Revert "drm/radeon: Fix EEH during kexec"
ocfs2: fix panic due to ocfs2_wq is null
ipv4: Return -ENETUNREACH if we can't create route but saddr is valid
net: bcmgenet: Fix RGMII_MODE_EN value for GENET v1/2/3
net: bcmgenet: Set phydev->dev_flags only for internal PHYs
net: i82596: fix dma_alloc_attr for sni_82596
net: stmmac: disable/enable ptp_ref_clk in suspend/resume flow
sctp: change sctp_prot .no_autobind with true
net: avoid potential infinite loop in tc_ctl_action()
memfd: Fix locking when tagging pins
USB: legousbtower: fix memleak on disconnect
ALSA: hda/realtek - Add support for ALC711
usb: udc: lpc32xx: fix bad bit shift operation
USB: serial: ti_usb_3410_5052: fix port-close races
USB: ldusb: fix memleak on disconnect
USB: usblp: fix use-after-free on disconnect
USB: ldusb: fix read info leaks
arm64: v8.4: Support for new floating point multiplication instructions
arm64: Documentation: cpu-feature-registers: Remove RES0 fields
arm64: Expose Arm v8.4 features
arm64: move SCTLR_EL{1,2} assertions to
arm64: add PSR_AA32_* definitions
arm64: Introduce sysreg_clear_set()
arm64: capabilities: Update prototype for enable call back
arm64: capabilities: Move errata work around check on boot CPU
arm64: capabilities: Move errata processing code
arm64: capabilities: Prepare for fine grained capabilities
arm64: capabilities: Add flags to handle the conflicts on late CPU
arm64: capabilities: Unify the verification
arm64: capabilities: Filter the entries based on a given mask
arm64: capabilities: Prepare for grouping features and errata work arounds
arm64: capabilities: Split the processing of errata work arounds
arm64: capabilities: Allow features based on local CPU scope
arm64: capabilities: Group handling of features and errata workarounds
arm64: capabilities: Introduce weak features based on local CPU
arm64: capabilities: Restrict KPTI detection to boot-time CPUs
arm64: capabilities: Add support for features enabled early
arm64: capabilities: Change scope of VHE to Boot CPU feature
arm64: capabilities: Clean up midr range helpers
arm64: Add helpers for checking CPU MIDR against a range
arm64: Add MIDR encoding for Arm Cortex-A55 and Cortex-A35
arm64: capabilities: Add support for checks based on a list of MIDRs
arm64: KVM: Use SMCCC_ARCH_WORKAROUND_1 for Falkor BP hardening
arm64: don't zero DIT on signal return
arm64: Get rid of __smccc_workaround_1_hvc_*
arm64: cpufeature: Detect SSBS and advertise to userspace
arm64: ssbd: Add support for PSTATE.SSBS rather than trapping to EL3
KVM: arm64: Set SCTLR_EL2.DSSBS if SSBD is forcefully disabled and !vhe
arm64: fix SSBS sanitization
arm64: Add sysfs vulnerability show for spectre-v1
arm64: add sysfs vulnerability show for meltdown
arm64: enable generic CPU vulnerabilites support
arm64: Always enable ssb vulnerability detection
arm64: Provide a command line to disable spectre_v2 mitigation
arm64: Advertise mitigation of Spectre-v2, or lack thereof
arm64: Always enable spectre-v2 vulnerability detection
arm64: add sysfs vulnerability show for spectre-v2
arm64: add sysfs vulnerability show for speculative store bypass
arm64: ssbs: Don't treat CPUs with SSBS as unaffected by SSB
arm64: Force SSBS on context switch
arm64: Use firmware to detect CPUs that are not affected by Spectre-v2
arm64/speculation: Support 'mitigations=' cmdline option
MIPS: tlbex: Fix build_restore_pagemask KScratch restore
staging: wlan-ng: fix exit return when sme->key_idx >= NUM_WEPKEYS
scsi: sd: Ignore a failure to sync cache due to lack of authorization
scsi: core: save/restore command resid for e
