Hi Joshua,
I will touched base with Gavin to compare our trees. My test kernel is the
current Azure kernel with two commits applied: d633198088bd9 and
eb4c2382272ae7. Commit eb4c2382272ae7 being the patch from
Dennis Krein in linux-next:
eb4c2382272a ("srcu: Lock srcu_data structure in
** Changed in: linux (Ubuntu)
Importance: Critical => Medium
** Changed in: linux (Ubuntu Bionic)
Importance: Critical => Medium
** Changed in: linux (Ubuntu Cosmic)
Importance: Critical => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Changed in: linux (Ubuntu)
Status: In Progress => Incomplete
** Changed in: linux (Ubuntu Xenial)
Status: In Progress => Incomplete
** Changed in: linux (Ubuntu Bionic)
Status: In Progress => Incomplete
** Changed in: linux (Ubuntu Cosmic)
Status: In Progress =>
A 18.04(Bionic) test kernel is built as well. The list of commits in
this kernel is:
4.18-rc1 - 7bf7bb37f16a ("hv_netvsc: fix network namespace issues with VF
support")
4.18-rc4 - 3ffe64f1a641 ("hv_netvsc: split sub-channel setup into async and
sync")
4.19-rc1 - 50229128727f ("Drivers: hv:
The Cosmic test kernel built without issue and only required commits
37c2578c0c40 and e04e7a7bbd4b.
It is available from:
http://kernel.ubuntu.com/~jsalisbury/lp1807757/cosmic/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: linux (Ubuntu Cosmic)
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/1807757
Title:
Drivers: hv: vmbus: Offload the handling of channels to two
** Description changed:
== SRU Justification ==
Microsoft has identified a multiple-NIC-deadlock issue on Hyper-V VMs. This
bug is fixed by the following commit, which is in mainline as of v4.20-rc6:
37c2578c0c40 ("Drivers: hv: vmbus: Offload the handling of channels to two
** Description changed:
+ == SRU Justification ==
+
Microsoft has identified a multiple-NIC-deadlock issue on Hyper-V VMs. This
bug is fixed by the following commit, which is in mainline as of v4.20-rc6:
37c2578c0c40 ("Drivers: hv: vmbus: Offload the handling of channels to two
w
** No longer affects: linux-azure (Ubuntu Xenial)
** No longer affects: linux-azure (Ubuntu Bionic)
** No longer affects: linux-azure (Ubuntu Cosmic)
** No longer affects: linux-azure (Ubuntu Disco)
** Changed in: linux-azure (Ubuntu)
Status: New => Triaged
** Changed in: linux-a
** Description changed:
Microsoft has identified a multiple-NIC-deadlock issue on Hyper-V VMs. This
bug is fixed by the following commit, which is in mainline as of v4.20-rc6:
37c2578c0c40 ("Drivers: hv: vmbus: Offload the handling of channels to two
workqueues")
-
A second commit is
values for uninitalized channels")
** Affects: linux (Ubuntu)
Importance: Medium
Assignee: Joseph Salisbury (jsalisbury)
Status: Triaged
** Affects: linux (Ubuntu Xenial)
Importance: Medium
Assignee: Joseph Salisbury (jsalisbury)
Status: Triaged
** Aff
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
Does this issue 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/1805527
Title:
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/
** Changed in: linux (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs,
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
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1805151
Title:
** 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/1805655
Title:
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
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Changed in: linux (Ubuntu)
Status: Incomplete => Triaged
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Bionic)
Status: New => Triaged
** Changed in:
I built a test kernel with commit eb4c2382272ae7 from linux-next. This
commit relies on commit d633198088bd9 for the definition of
spin_lock_rcu_node and it's corresponding unlock. That commit was added
to mainline in v4.16-rc1
The test kernel can be downloaded from:
** Changed in: linux-azure (Ubuntu)
Assignee: (unassigned) => Joseph Salisbury (jsalisbury)
** Changed in: linux-azure (Ubuntu)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I started a kernel bisect between Ubuntu 4.15.0-20 and Ubuntu 4.15.0-34. The
kernel bisect will require testing of about 7-10 test kernels.
I built the first test kernel, up to the following commit:
9dcfef9fe59a2b4931f58b18fba731d00a4531bd
The test kernel can be downloaded from:
Is this pull request for our development release(Disco/19.04)? If so,
not a big issue. However, these amount of changes would require a
justification to get into a stable release.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
In bug 1782085 it looks like the bug stopped happening after upgrading
to version 4.15.0-23. Do you know if that is still the case with that
older system, or has the bug come back after upgrading to a newer kernel
version?
--
You received this bug notification because you are a member of Ubuntu
I built Bionic, Cosmic and Disco test kernel with commit
9a764c1e59684c0358e16ccaafd870629f2cfe67. The test kernel can be downloaded
from:
http://kernel.ubuntu.com/~jsalisbury/lp1805802
Can you test this kernel and see if it resolves this bug?
Note about installing test kernels:
• If the test
** Changed in: linux (Ubuntu)
Assignee: Skipper Bug Screeners (skipper-screen-team) => Canonical Kernel
Team (canonical-kernel-team)
** Also affects: linux (Ubuntu Disco)
Importance: Medium
Assignee: Canonical Kernel Team (canonical-kernel-team)
Status: In Progress
--
You
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Changed in: linux (Ubuntu)
Status: New => In Progress
** Changed in: linux (Ubuntu)
Assignee: Skipper Bug Screeners (skipper-screen-team) => Joseph Salisbury
(jsalisbury)
** Also affects: linux (Ubun
** 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/1806115
Title:
cannot set hmcdrv cachesize to 1GB
To manage notifications about this bug go to:
Thanks for retesting. Can you test v4.17 final? It is available from:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.17/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752961
Title:
With
I built a disco test kernel with the requested config options enabled.
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1799467
Can you test this kernel and see if it resolves this bug?
Note about installing test kernels:
• If the test kernel is prior to
I built Bionic, Cosmic and Disco test kernels with commit
104f708fd1241b22f808bdf066ab67dc5a051de5. The test kernel can be downloaded
from:
http://kernel.ubuntu.com/~jsalisbury/lp1805414
Can you test this kernel and see if it resolves this bug?
Note about installing test kernels:
• If the
d => High
** Changed in: linux (Ubuntu Bionic)
Importance: Undecided => High
** Changed in: linux (Ubuntu Bionic)
Assignee: (unassigned) => Joseph Salisbury (jsalisbury)
** Changed in: linux (Ubuntu Cosmic)
Assignee: (unassigned) => Joseph Salisbury (jsalisbury)
** Chan
** Tags added: kernel-da-key kernel-hyper-v
** Also affects: linux-azure (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-azure (Ubuntu)
Status: New => Triaged
** Changed in: linux (Ubuntu)
Status: Confirmed => Triaged
** Changed in: linux (Ubuntu)
It looks like the following commit is a prereq:
f1b0a4343c418 ("s390/zcrypt: Integrate ap_asm.h into include/asm/ap.h")
This would define ap_zapq, which is used in commit 104f708fd1241b. Can
you confirm this?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
I'll continue to debug this further.
--
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| Enable virtio-gpu for s390x
To manage notifications about this bug go to:
There are some errors due to the annotations file:
check-config:
/home/jsalisbury/bugs/lp1799467/ubuntu-cosmic/debian/build/build-generic/.config:
loading config
check-config:
/home/jsalisbury/bugs/lp1799467/ubuntu-cosmic/debian.master/config/annotations
loading annotations
check-config: FAIL
** Changed in: linux (Ubuntu)
Status: New => Triaged
** Changed in: linux (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1805414
Title:
[Ubuntu]
Can you confirm that v4.15-rc6 does not exhibit the bug? That will
ensure I'm reviewing the correct commits:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15-rc6/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I built a new Bionic test kernel. The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1784665
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
Can you also test the following mainline kernels to confirm if this is
due to a SAUCE patch or not:
4.15.18: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15.18/
4.16 Final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.16/
--
You received this bug notification because you are a member of
Also, just to confirm to test this kernel you need to install the linux-
modules, linux-modules-extra and linux-image-unsigned .deb packages in
that order.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Can you test the following kernel? It appears this bug may have been
introduced by a SAUCE patch:
-34:
https://launchpad.net/~canonical-kernel-
team/+archive/ubuntu/ppa/+build/15307305
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
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
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
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
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
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
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
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
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
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
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
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Also affects: linux (Ubuntu Disco)
Importance: Medium
Status: Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Status: Incomplete => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1804360
Title:
** 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/1805018
Title:
Need activate more hardening option
To manage notifications about this
** 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/1804991
Title:
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
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
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
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
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
** 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/1805099
Title:
nvidia: module verification failed: signature and/or required key
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
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Status: Confirmed => Triaged
** Also affects: linux (Ubuntu Disco)
Importance: Medium
Status: Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs,
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
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"
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
**
I've been unable to get a kernel to build using the config options
posted in the description. Have you been able to build a kernel on
you're side? It is possible that other options are needed as well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
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
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
** 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:
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
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
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
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.
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
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
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
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?
--
** 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
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:
** 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
** 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.
** 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
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
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)
**
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:
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.
--
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
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
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
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
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
** 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:
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
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
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
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
** 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
** 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
301 - 400 of 30240 matches
Mail list logo
