Status: Confirmed => In Progress
** Changed in: linux (Ubuntu Bionic)
Assignee: (unassigned) => Joseph Salisbury (jsalisbury)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1803392
Title:
Nothing sticks out in that range of commits. There is nothing atheros
related. Before starting a bisect, can you confirm -proposed does not
already fix the bug?
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed.
Thank you in advance!
--
You r
I also started a kernel bisect between Ubuntu-4.15.0-38 and
Ubuntu-4.15.0-39. The kernel bisect will require testing of about 7-10
test kernels.
I built the first test kernel, up to the following commit:
125291b1852e43501135f787adf03fa590e33f59
The test kernel can be downloaded from:
http://kerne
This bug has not had any activity in a while, can any update be
provided?
** Changed in: linux (Ubuntu Bionic)
Importance: High => Medium
** Changed in: linux (Ubuntu)
Importance: High => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
There hasn't been an update in quite some time. Do you happen to know
if this bug is still valid?
** Changed in: linux (Ubuntu Xenial)
Assignee: (unassigned) => Joseph Salisbury (jsalisbury)
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Joseph Salisbury
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Also affects: linux (Ubuntu Cosmic)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status: Incomplete => Triaged
** Changed in: linux (Ubuntu Cosmic)
Status: New => Triaged
** Changed in:
*** This bug is a duplicate of bug 1803816 ***
https://bugs.launchpad.net/bugs/1803816
** This bug has been marked a duplicate of bug 1803816
Linux Kernel USB 3 drivers problem
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ht
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.20 kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel does not fix t
*** This bug is a duplicate of bug 1803816 ***
https://bugs.launchpad.net/bugs/1803816
** This bug has been marked a duplicate of bug 1803816
Linux Kernel USB 3 drivers problem
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ht
Does this bug go away if you boot back into the prior kernel version?
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1803982
Title:
r
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Status: Confirmed => Triaged
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Bionic)
Status: New => Triaged
** Changed in:
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.20 kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel does not fix t
Can you see if this issue also happens with the latest daily image? It
can be downloaded from:
Desktop:
http://cdimage.ubuntu.com/daily-live/current/
Server:
http://cdimage.ubuntu.com/ubuntu-server/daily/current/
** Changed in: linux (Ubuntu)
Importance: Undecided => High
--
You received th
You may need to run the following from a terminal:
sudo apt-get install -f
sudo apt-get clean
sudo apt-get update
Then re-install the package or updates.
If that does not resolve your issue, please mark the bug as "Confirmed"
** Package changed: linux-hwe (Ubuntu) => linux (Ubuntu)
** Changed
Would it be possible for you to test the proposed kernel and post back if it
resolves this bug?
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.
Thank you in advance!
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Also a
Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.20 kernel[
Did this issue start happening after an update/upgrade? Was there a prior
kernel version where you were not having this particular problem?
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.20 kerne
Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.20 kernel[
Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.20 kernel[
Do you have a way to test some kernels out? If so, we could perform a
kernel bisect to narrow down the commit that introduced this.
** Tags removed: kernel-da-key
** Tags added: kernel-key
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
That is good news, that might indicate this bug is now fixed. Can you
apply all the latest updates and the latest kernel to see if the bug
still exists?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1
That is if this is a regression. Was this working on a prior kernel
version?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1794477
Title:
Accelerated networking (SR-IOV VF) broken in 18.10 daily
T
** Tags removed: kernel-key
** Tags added: kernel-da-key
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1797367
Title:
Ubuntu 18.04.1 - [s390x] Kernel panic while stressing network bonding
To manage
** Tags removed: kernel-key
** Tags added: kernel-da-key
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1787405
Title:
[FEAT] Guest-dedicated Crypto Adapters
To manage notifications about this bug g
** Tags removed: kernel-key
** Tags added: kernel-da-key
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1799497
Title:
4.15 kernel hard lockup about once a week
To manage notifications about this bu
t; Medium
** Changed in: linux (Ubuntu Bionic)
Assignee: (unassigned) => Joseph Salisbury (jsalisbury)
** Changed in: linux (Ubuntu)
Assignee: Canonical Kernel Team (canonical-kernel-team) => Joseph
Salisbury (jsalisbury)
--
You received this bug notification because you are a m
Hmm, OK, thanks for the feedback. Let me review the bisect results and
see if we went astray at some point.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1792100
Title:
Boot hangs at "loading initi
I built a test kernel with commit f9652d5cae0. The test kernel can be
downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1719545
Can you test this kernel and see if it resolves this bug?
Note about installing test kernels:
* If the test kernel is prior to 4.15(Bionic) you need to install t
kernels:
4.15.0-29:
https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/ppa/+build/15137612
4.17.0-4:
https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/bootstrap/+build/15068818
** Changed in: linux (Ubuntu Cosmic)
Assignee: Marcelo Cerri (mhcerri) => Joseph Salisb
** Package changed: linux (Ubuntu) => linux-azure (Ubuntu)
** Changed in: linux-azure (Ubuntu)
Status: Confirmed => New
** Tags added: kernel-da-key kernel-hyper-v
** Changed in: linux-azure (Ubuntu)
Status: New => Triaged
** Changed in: linux-azure (Ubuntu)
Importance: Undecid
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.20 kernel[0].
[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.20-rc3
--
You received this bug notification because you are a member of Ubuntu
B
The 4.20 kernel is now available. Can you give v4.20-rc3 a test:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.20-rc3
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1784665
Title:
mkfs.ext4 over
Regarding my comment #9, I read your comment #7 incorrectly. I
literally read you don't know how a bisect would work. I understand
clearly now.
We still should be able to bisect using the azure tree. I'll review the
commits between 4.15 and 4.18 and see if anything sticks out.
--
You received
Also, the Ubuntu kernel trees are located at:
4.15: git://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/bionic/
4.18: git://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/cosmic/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
Just to confirm, the 4.18 kernel you see this bug in is the standard
Ubuntu kernel?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1794477
Title:
Accelerated networking (SR-IOV VF) broken in 18.10 da
For 4.18 based azure images, there are two repos:
lp:~canonical-kernel/ubuntu/+source/linux-azure/+git/cosmic
or the azure-edge-next branch in the bionic azure tree.
I'm going to review both to see if the commits going from 4.15 to 4.18
are linear. If they are, we may be able to bisect.
--
Yo
Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?
Would it be possible for you to test the latest upstream kernel to see
if the bug exists there as well? That kernel is available from:
http://kernel.ubuntu.
If that is the case, we are better off performing a "Reverse" bisect to
identify the fix in mainline versus investigating what went wrong in the
first regular bisect.
The steps for a reverse bisect are similar, but we first need to find
the last "Bad" kernel and the first "Good" kernel. Can you t
You may need to run the following from a terminal:
sudo apt-get install -f
sudo apt-get clean
sudo apt-get update
Then re-install the package or updates.
If that does not resolve your issue, please mark the bug as "Confirmed"
** Package changed: linux-signed (Ubuntu) => linux (Ubuntu)
** Chan
** Changed in: linux-azure (Ubuntu)
Importance: High => Critical
** Changed in: linux (Ubuntu Cosmic)
Importance: High => Critical
** Changed in: linux (Ubuntu)
Importance: High => Critical
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscrib
** Changed in: linux (Ubuntu Cosmic)
Status: Confirmed => In Progress
** Changed in: linux (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1794477
** Changed in: linux (Ubuntu Xenial)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1790832
Title:
crypto/vmx - Backport of Fix sleep-in-atomic bugs patch
Thanks for testing. That's interesting because both of those kernels
are not the custom azure kernel and you say you don't see this bug on
the 4.15 azure kernel. However, it is seen on the non-azure 4.15
kernel.
Can you see if this kernel exhibits the bug:
https://launchpad.net/ubuntu/+source/li
** Changed in: linux (Ubuntu)
Status: New => Triaged
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1799467
Title:
[19.04 FEAT
Hi David,
Before starting a bisect, we can try to narrow down the exact versions
first. To start, I built a 4.17 kernel based on the azure tree.
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1794477
Can you test this kernel and see if it exhibits this bug?
--
For this particular bug, the tools packages are probably not needed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1794477
Title:
Accelerated networking (SR-IOV VF) broken in 18.10 daily
To manage
You at least need to install the linux-modules, linux-modules-extra and
linux-image-unsigned .deb packages in that order. You should be able to
do that with 'sudo dpkg -i package_name.deb'
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubunt
Thanks for testing, David. That means this regression was introduced in
4.18 and narrows down the number of commits we need to bisect through.
Can you next test the first 4.18 based kernel in the azure tree:
http://kernel.ubuntu.com/~jsalisbury/lp1794477
Install the .debs in the same order as be
To try and speed up the kernel build time, I already built 4.18.0-1002
as well. There are now two 4.18 kernels available for testing:
4.18.0-1001: http://kernel.ubuntu.com/~jsalisbury/lp1794477/4.18.0-1001/
4.18.0-1002: http://kernel.ubuntu.com/~jsalisbury/lp1794477/4.18.0-1002/
--
You received
I built the 4.18.0-1003 kernel, which can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1794477/4.18.0-1003
Can you give this one a test?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/17
I built the 4.18.0-1004 kernel, which can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1794477/4.18.0-1004
Can you give this one a test?
If this kernel does not exhibit the bug, I'll start using the bionic azure-edge
tree. These prior test kernels are with the azure cosmic tree,
I built the 4.18.0-1004 kernel, but this time using the bionic tree and
azure-edge-next branch.
This kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1794477/bionic-tree/4.18.0-1004
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
I built one more 1004 kernel from the bionic tree, but this time
including all of the packages. This kernel can also be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1794477/bionic-tree/4.18.0-1004
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Changed in: linux-azure (Ubuntu)
Status: Confirmed => In Progress
** Changed in: linux (Ubuntu)
Importance: Critical => High
** Changed in: linux (Ubuntu Cosmic)
Importance: Critical => High
** Changed in: linux-azure (Ubuntu)
Importance: Critical => High
** Changed in: linux
Can you test 4.18 final:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.18/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1792100
Title:
Boot hangs at "loading initial ramdisk..."
To manage notif
Were you able to test the mainline kernel to see if this bug still
exists there?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1804149
Title:
Kernel panic,Oops: 0004 ilc:3 [#1] SMP, iscsi_q_20 iscs
** Also affects: linux (Ubuntu Cosmic)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Bionic)
Status: New => Triaged
** Changed in: linux (Ubuntu Cosmic)
Status: New => Tria
signed) => Joseph Salisbury (jsalisbury)
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Joseph Salisbury (jsalisbury)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1798208
Title:
smar
SRU Request submitted:
https://lists.ubuntu.com/archives/kernel-team/2018-November/096402.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1798208
Title:
smartpqi updates for ubuntu 18.04.2
To ma
The following five commits are the only patches needed, since 18.04.2
will be based on the upstream 4.18 kernel, which already contains the
other requested commits:
957c5ab108c7 ("scsi: smartpqi: improve handling for sync requests")
26b390aba2a8 ("scsi: smartpqi: improve error checking for sync re
I built a test kernel with the five commits posed in comment #5. The test
kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1798208
Can you test this kernel and see if it resolves this bug?
Note about installing test kernels:
• If the test kernel is prior to 4.15(Bionic) you
What's interesting is the test kernel in comment #28 was tested as good.
That was built with commit 19e56be2af5 as the tip of the tree. That
commit is only one commit behind 22df1539aed9, which is the version tag.
However, the bug exists when commit 22df1539aed9 is the tip.
I built a v2 version o
** Changed in: linux-azure (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1800702
Title:
upgrading from 4.4.0-116-generic to latest linux-azure automatical
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1801108
Title:
on resume from suspend I am logged out
To manage notifications about th
** Package changed: linux-signed (Ubuntu) => linux (Ubuntu)
** Also affects: linux (Ubuntu Disco)
Importance: Low
Status: Confirmed
** Changed in: linux (Ubuntu Disco)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, wh
You may need to run the following from a terminal:
sudo apt-get install -f
sudo apt-get clean
sudo apt-get update
Then re-install the package or updates.
If that does not resolve your issue, please mark the bug as "Confirmed"
** Package changed: linux-hwe (Ubuntu) => linux (Ubuntu)
** Changed
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Status: Confirmed => Triaged
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Bionic)
Status: New => Triaged
** Changed in:
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.19 kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel does not fix t
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.19 kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel does not fix t
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.19 kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel does not fix t
Does this issue go away if you boot back into the prior kernel version?
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
** Tags added: kernel-da-key
--
You received this bug notification because you are a mem
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Status: Confirmed => Triaged
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Bionic)
Status: New => Triaged
** Changed in:
Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.19 kernel[
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.19 kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel does not fix t
** Changed in: linux (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1800887
Title:
launchpad is claiming my report has one error, but is not flagging
what t
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1800859
Title:
Fa
I tried to apply the first two commits listed in comment #23. Neither
apply cleanly and need to be backported. Would it be possible for IBM
to provide a backport of any commits that don't apply cleanly?
This bug will be discussed on Monday in the kernel teams work items
meeting, due to the numbe
Thanks for the backports! Were you able to get a kernel to build with
these commits? I applied the 40 commits to a Bionic tree, but it fails
to build.
I'll see if I can figure out why my build failed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
Yeah, it looks like it's failing due to that config option:
IOMMU Hardware Support (IOMMU_SUPPORT) [Y/?] y
S390 CCW IOMMU Support (S390_CCW_IOMMU) [Y/n/?] y
S390 AP IOMMU Support (S390_AP_IOMMU) [N/y/?] (NEW) aborted!
Console input/output is redirected. Run 'make oldconfig' to update
configura
I built a test kernel with those two config options enabled and the 40 commits.
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1787405
Can you test this kernel and see if it resolves this bug?
Note about installing test kernels:
• If the test kernel is prior to 4
** Tags added: kernel-da-key kernel-hyper-v
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1802358
Title:
[Hyper-V] Fix IRQ spreading on NVMe devices with lower numbers of
channels
To manage notif
: Undecided
Status: Incomplete
** Also affects: libvirt (Ubuntu Disco)
Importance: Undecided
Status: Confirmed
** Also affects: linux (Ubuntu Disco)
Importance: High
Assignee: Joseph Salisbury (jsalisbury)
Status: In Progress
** Also affects: qemu (Ubuntu Bionic
** Changed in: linux (Ubuntu Bionic)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1787405
Title:
[19.04 FEAT] Guest-dedicated Crypto Adapters
To manage notifi
** Changed in: linux (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1789131
Title:
Probable regression with EXT3 file systems and CVE-2018-1093 pat
** Changed in: linux (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1744300
Title:
bt_iter() crash due to NULL pointer
To manage notifications abou
** Changed in: linux (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1729637
Title:
Samba mount/umount in docker container triggers kernel Oops
To
There is a 32bit kernel now posted to:
http://kernel.ubuntu.com/~jsalisbury/lp1736390
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1736390
Title:
openvswitch: kernel oops destroying interfaces on i
I'll ping upstream and the author of the patch that was reverted.
However, before doing so, we should test the latest mainline kernel to
see if the bug is already fixed upstream.
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds
I started a kernel bisect between commit v4.14 final and v4.15-rc1. The
kernel bisect will require testing of about 13 test kernels.
I built the first test kernel, up to the following commit:
1be2172e96e33bfa22a5c7a651f768ef30ce3984
The test kernel can be downloaded from:
http://kernel.ubuntu.com
I built a 4.15.0-35 test kernel.
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1792100
Can you test this kernel and see if it resolves this bug?
Note about installing test kernels:
• If the test kernel is prior to 4.15(Bionic) you need to install the
linux-image
Would it be possible for you to test the proposed kernel and post back if it
resolves this bug?
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.
Thank you in advance!
--
You received this bug notification because you are a member of Ubuntu
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.19 kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel does not fix t
I built a test kernel with NO_JVMTI disabled in
tools/perf/Makefile.config.
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1761379
Can you test this kernel and see if it resolves this bug?
Note about installing test kernels:
• If the test kernel is prior to 4.15(B
** Tags added: kernel-da-key
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
Did this issue start happening after an update/upgrade? Was there a prior
kernel version where you were not having this particular problem?
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.19 kerne
You may need to run the following from a terminal:
sudo apt-get install -f
sudo apt-get clean
sudo apt-get update
Then re-install the package or updates.
If that does not resolve your issue, please mark the bug as "Confirmed"
** Package changed: linux-hwe (Ubuntu) => linux (Ubuntu)
** Changed
Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.19 kernel[
Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.19 kernel[
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.19 kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel does not fix t
Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.19 kernel[
801 - 900 of 30106 matches
Mail list logo
