** Tags added: cscc
--
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/1760876
Title:
DKMS driver builds fail with: Cannot use CONFIG_STACK_VALIDATION=y,
please install libelf-dev, l
This bug was erroneously marked for verification in bionic; verification
is not required and verification-needed-bionic is being removed.
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure
** Tags removed: verification-needed-bionic
** Tags added: kernel-fixup-verification-needed-bionic
--
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/1760876
Title:
DKMS driver builds
Hey Brad,
I confirmed the fix on 2018-04-09 (but didn't add a tag). Is the
current fix the same? I don't have the same hardware to recreate now.
Thanks
Jeff
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https:/
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag 'verifica
Still occurring in bug 1810406..!?
--
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/1760876
Title:
DKMS driver builds fail with: Cannot use CONFIG_STACK_VALIDATION=y,
please instal
This bug was fixed in the package linux-azure-edge -
4.18.0-1006.6~16.04.2
---
linux-azure-edge (4.18.0-1006.6~16.04.2) xenial; urgency=medium
* linux-azure-edge: 4.18.0-1006.6~16.04.2 -proposed tracker (LP:
#1805865)
[ Ubuntu: 4.18.0-1006.6 ]
* linux-azure: 4.18.0-1006.6 -pro
This bug was fixed in the package linux-azure-edge -
4.18.0-1006.6~16.04.2
---
linux-azure-edge (4.18.0-1006.6~16.04.2) xenial; urgency=medium
* linux-azure-edge: 4.18.0-1006.6~16.04.2 -proposed tracker (LP:
#1805865)
[ Ubuntu: 4.18.0-1006.6 ]
* linux-azure: 4.18.0-1006.6 -pro
Hello,
I am getting the same error while installing the 'display-link' in Ubuntu 16.04
LTS, which I installed on Lenovo Thinkpad Carbon 6th.
Here is the output of the run command [1]. What one need to do to fix this
error?
Best Regards,
[1]
**
pooja@X1-Carbon-6:~/Downloads
My Ubuntu 18.04 is no longer affected.
I was able to get past "Cannot use CONFIG_STACK_VALIDATION=y" with some
cleanup - removing all nvidia drivers, manually blacklisting nouveau,
updating initramfs, and rebooting - before installing nvidia drivers and
dkms again.
--
You received this bug notif
issue seems to persist in bionic linux-generic 4.15.0.19.20 amd64.
$ sudo apt install --reinstall nvidia-dkms-390
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded.
Need to ge
This bug was fixed in the package linux-azure - 4.13.0-1014.17
---
linux-azure (4.13.0-1014.17) xenial; urgency=medium
* linux-azure: 4.13.0-1014.17 -proposed tracker (LP: #1761459)
* retpoline hints: primary infrastructure and initial hints (LP: #1758856)
- [Config] retpolin
This bug was fixed in the package linux - 4.13.0-39.44
---
linux (4.13.0-39.44) artful; urgency=medium
* linux: 4.13.0-39.44 -proposed tracker (LP: #1761456)
* intel-microcode 3.20180312.0 causes lockup at login screen(w/ linux-
image-4.13.0-37-generic) (LP: #1759920) // CVE-
This bug was fixed in the package linux - 3.13.0-145.194
---
linux (3.13.0-145.194) trusty; urgency=medium
* linux: 3.13.0-145.194 -proposed tracker (LP: #1761430)
* intel-microcode 3.20180312.0 causes lockup at login screen(w/ linux-
image-4.13.0-37-generic) (LP: #1759920) /
This bug was fixed in the package linux - 4.4.0-121.145
---
linux (4.4.0-121.145) xenial; urgency=medium
* linux: 4.4.0-121.145 -proposed tracker (LP: #1763687)
* Ubuntu-4.4.0-120.144 fails to boot on arm64* hardware (LP: #1763644)
- [Config] arm64: disable BPF_JIT_ALWAYS_ON
Confirmed dkms builds are successful with Xenial kernel
4.4.0-121-generic (tested with fwts-efi-runtime-dkms).
** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribe
Confirmed dkms builds are successful with Artful kernel
4.13.0-39-generic (tested with fwts-efi-runtime-dkms).
** Tags removed: verification-needed-artful
** Tags added: verification-done-artful
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribe
Confirmed dkms builds are successful with Trusty kernel
3.13.0-145-generic (tested with fwts-efi-runtime-dkms).
** Tags removed: verification-needed-trusty
** Tags added: verification-done-trusty
--
You received this bug notification because you are a member of Kernel
Packages, which is subscrib
This bug was fixed in the package linux - 4.15.0-15.16
---
linux (4.15.0-15.16) bionic; urgency=medium
* linux: 4.15.0-15.16 -proposed tracker (LP: #1761177)
* FFe: Enable configuring resume offset via sysfs (LP: #1760106)
- PM / hibernate: Make passing hibernate offsets more
This bug was fixed in the package linux-azure - 4.15.0-1004.4
---
linux-azure (4.15.0-1004.4) bionic; urgency=medium
* linux-azure: 4.15.0-1004.4 -proposed tracker (LP: #1761181)
* [Hyper-V] hv_netvsc: enable multicast if necessary (LP: #1759885)
- hv_netvsc: fix filter flags
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
artful' to 'verification-done-artful'. If the problem still exists,
change the tag 'verifica
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag 'verifica
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-azure-edge (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bug
I can confirm the last kernel update from Bionic's " -proposed" last week
did not present this issue.
Thanks!
Jeff
On Mon, Apr 9, 2018, 16:45 Kleber Sacilotto de Souza <
kleber.so...@canonical.com> wrote:
> This bug is awaiting verification that the kernel in -proposed solves
> the problem. Plea
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
trusty' to 'verification-done-trusty'. If the problem still exists,
change the tag 'verifica
** Also affects: linux-azure (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-azure (Ubuntu Bionic)
Status: New => Fix Committed
** Changed in: linux-azure (Ubuntu Xenial)
Status: New => Fix Committed
** Also affects: linux-azure-edge (Ubuntu)
Importance
This also affects linux-azure and linux-azure-edge.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1760876
Title:
DKMS driver builds fail with: Cannot use CONFIG_STACK_VALIDATION=y,
pl
The problem is solved in my Ubuntu 18.04
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1760876
Title:
DKMS driver builds fail with: Cannot use CONFIG_STACK_VALIDATION=y,
please instal
** Changed in: linux (Ubuntu Trusty)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1760876
Title:
DKMS driver builds fail with: Cannot use CONFIG_STA
** Also affects: linux (Ubuntu Bionic)
Importance: High
Assignee: Andy Whitcroft (apw)
Status: Fix Committed
** Also affects: linux (Ubuntu Artful)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Trusty)
Importance: Undecided
Status: New
** Als
Tested the reinstall of fwts on 4.15.0-15, and the previous dkms issue
is now gone
** No longer affects: fwts (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1760876
Title:
DKMS
A fix is in bionic proposed as of 12 hours ago:
https://launchpad.net/ubuntu/+source/linux/4.15.0-15.16
Although I suspect the changelog text is wrong there. I've now
deduplicated a bunch of bug reports from various different DKMS drivers
to point to this one.
** Summary changed:
- fwts-efi-run
32 matches
Mail list logo
