** Changed in: linux (Ubuntu Xenial)
Status: Confirmed => New
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: linux (Ubuntu Xenial)
Status: New => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux (Ubuntu Xenial)
Status: New => Confirmed
--
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/b
** 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/1802021
Title:
[Hyper-V] srcu: Lock srcu_data structure in srcu_gp_start()
Status in linux package in Ubuntu:
This bug was fixed in the package linux - 4.15.0-47.50
---
linux (4.15.0-47.50) bionic; urgency=medium
* linux: 4.15.0-47.50 -proposed tracker (LP: #1819716)
* Packaging resync (LP: #1786013)
- [Packaging] resync getabis
- [Packaging] update helper scripts
- [Packagin
This bug was fixed in the package linux - 4.18.0-17.18
---
linux (4.18.0-17.18) cosmic; urgency=medium
* linux: 4.18.0-17.18 -proposed tracker (LP: #1819624)
* Packaging resync (LP: #1786013)
- [Packaging] resync getabis
- [Packaging] update helper scripts
* C++ demang
Updating bug tags to verification done.
As mentioned by users in this LP bug, the verification period of 5 days
is _usually_ not enough to reproduce this problem, however, we have some
datapoints that support the fix is good.
1) The fix has been first delivery in linux-azure, 3 weeks ago, and has
I was experiencing a situation with moby dockerd entering a state
similar to comment 0 here, running kubernetes and linux kernel
4.15.0-1037-azure. This was an 8 node cluster. Observed with
combinations:
kubernetes 1.11.5 + moby runtime 3.0.1 + Ubuntu 16.04.5
kubernetes 1.11.7 + moby runtime 3.0.4
As Marius mentioned we already deployed this patch on several instances and now
we are monitoring them to see if this still happens. At least 2 of them were
affected by the bug before patching so we had to reboot them.
If the above information (previous post) is correct and considering the time
@mfo
Just to confirm that we installed the right proposed version of the kernel as
this doesn't have any steps to reproduce. It only reproduces randomly after a
certain amount of time.
These are the steps we followed to install
echo 'deb http://archive.ubuntu.com/ubuntu/ xenial-proposed restric
Thanks Mauricio! @mfo
Will begin deploying this and let you guys know as soon as possible.
--
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/1802021
Title:
[Hyper-V] srcu: Lock srcu_
Hi Marius @lazamarius1,
Per the kernel.ubuntu.com schedule, the version for Bionic/linux ->
Xenial/linux-hwe should land soon.
You can verify the version/timestamps for each package/release at the bottom of
these pages
(the linux-hwe version comes a bit after the corresponding linux version)
ht
@lazamarius1,
Actually linux-hwe for Bionic with this fix has just been uploaded.
See in https://launchpad.net/ubuntu/+source/linux-hwe
Changelog
linux-hwe (4.15.0-47.50~16.04.1) xenial; urgency=medium
...
* [Hyper-V] srcu: Lock srcu_data structure in srcu_gp_start() (LP: #1802021)
- srcu
Hi Brad @brad-figg,
5 days are not enough to test this bug.
Citing David:
"@overlord: AFAIK, there is no simple reproducer test case for this issue. The
ideal testing scenario for a bug and fix like this one would be for each user
who reported this issue to use a test kernel with the fix in thei
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-
cosmic' to 'verification-done-cosmic'. If the problem still exists,
change the tag 'verifica
This bug was fixed in the package linux-azure - 4.15.0-1040.44
---
linux-azure (4.15.0-1040.44) xenial; urgency=medium
* linux-azure: 4.15.0-1040.44 -proposed tracker (LP: #1817038)
* Packaging resync (LP: #1786013)
- [Packaging] resync retpoline extraction
* CONFIG_SECURI
This bug was fixed in the package linux-azure - 4.15.0-1040.44
---
linux-azure (4.15.0-1040.44) xenial; urgency=medium
* linux-azure: 4.15.0-1040.44 -proposed tracker (LP: #1817038)
* Packaging resync (LP: #1786013)
- [Packaging] resync retpoline extraction
* CONFIG_SECURI
Andrei, I will discuss with engineering to confirm availability and get
back to you
--
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/1802021
Title:
[Hyper-V] srcu: Lock srcu_data str
Do you know when a fix for linux-xenial will be available? Looks like
that's the only one remaining.
--
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/1802021
Title:
[Hyper-V] srcu: L
This is the final reminder to please verify that the kernel in -proposed
resolves the issue for which you've filed this bug report. Canonical
is planning to release these kernels early next week. Thank you in
advance!
--
You received this bug notification because you are a member of Kernel
Pa
** Changed in: linux (Ubuntu Bionic)
Status: Confirmed => Fix Committed
** Changed in: linux (Ubuntu Cosmic)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://b
This bug was fixed in the package linux-azure - 4.18.0-1011.11
---
linux-azure (4.18.0-1011.11) cosmic; urgency=medium
* linux-azure: 4.18.0-1011.11 -proposed tracker (LP: #1816081)
* 4.15.0-1037 does not see all PCI devices on GPU VMs (LP: #1816106)
- Revert "PCI: hv: Make s
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: linux-azure (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: linux-azure (Ubuntu Xenial)
Status: New => Fix Committed
--
You received this bug notification becaus
This bug was fixed in the package linux-azure - 4.18.0-1011.11
---
linux-azure (4.18.0-1011.11) cosmic; urgency=medium
* linux-azure: 4.18.0-1011.11 -proposed tracker (LP: #1816081)
* 4.15.0-1037 does not see all PCI devices on GPU VMs (LP: #1816106)
- Revert "PCI: hv: Make s
This bug was fixed in the package linux-azure - 4.18.0-1011.11
---
linux-azure (4.18.0-1011.11) cosmic; urgency=medium
* linux-azure: 4.18.0-1011.11 -proposed tracker (LP: #1816081)
* 4.15.0-1037 does not see all PCI devices on GPU VMs (LP: #1816106)
- Revert "PCI: hv: Make s
@lazamarius1: Just to clarify, the fix is scheduled to go in the 4.15
kernel in Bionic which is the same kernel as the Xenial HWE kernel. So
there's no need to add anything to the Affects section. You will see a
new linux-hwe 4.15 kernel in xenial-proposed once this is ready to test.
Thanks!
--
Y
Hi @lazamarius1,
The fix for linux generic should be applied in the next kernel SRU cycle.
The current cycle ends on late February [1].
[1] https://kernel.ubuntu.com/
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
Hi @brad-figg,
Can we get a proposed fix for Xenial linux(-generic) package?
Or that is planned after the bionic one?
--
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/1802021
Title:
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
Hi Marcelo (@mhcerri),
We have another user who confirmed the 2 patches submitted for linux-
azure also fix the problem on linux(-generic).
srcu: Prohibit call_srcu() use under raw spinlocks
srcu: Lock srcu_data structure in srcu_gp_start()
Could they be submitted for linux as well?
Thank
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Changed in: linux (Ubuntu Bionic)
Status: Incomplete => Confirmed
** Changed in: linux (Ubuntu Cosmic)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
P
** No longer affects: linux-hwe (Ubuntu)
** No longer affects: linux-hwe (Ubuntu Bionic)
** No longer affects: linux-hwe (Ubuntu Cosmic)
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: linux-azure (Ubuntu Bionic)
** No longer affects: linux-azu
You can clone the ubuntu-xenial kernel:
git clone git://kernel.ubuntu.com/ubuntu/ubuntu-xenial.git
And then grep for the commit you're looking for. There's a few different
ways to do it, I do:
git log --oneline | grep "Expose SMT control init function"
--
You received this bug notification bec
Thanks David, that was my intention to patch the systems and wait for it to
reproduce (usually we get the issue back in 3-8 days or so...)
Also thanks for the pointers for checking the release notes for certain
releases.
Is there a connection between the changes listed in the second link and th
Hi overlord. An easy way to check the updates included in released
kernels is to look at the "-changes" mailing list for your Ubuntu
release.
In this situation it would be https://lists.ubuntu.com/archives/xenial-
changes/
And you can find that new kernel here:
https://lists.ubuntu.com/archives/
Mauricio @mfo, is there a way to reproduce the issue easily in order to test
it? I was not able to find it.
The only way I can tell the issue is there or not is to apply the patch and
wait for the servers to "hit" the problem (could take days or weeks...), and
when that happens, in my case, doc
@overlord: AFAIK, there is no simple reproducer test case for this
issue. The ideal testing scenario for a bug and fix like this one would
be for each user who reported this issue to use a test kernel with the
fix in their environment and report back if the issue still manifests or
not after some t
Thanks Marcelo! However I still see the unassigned package is linux-hwe, and I
can't add Xenial tag.
I also notices I received an update today from 4.15.0-43-generic to
4.15.0-45-generic but I cannot tell if this update has the fix from this bug.
Could you help me with some directions on this?
Marcelo @mhcerri,
Would you be able to provide a test kernel for bionic/linux-hwe so that
@lazamarius1 can provide test results for -generic?
I'll be happy to do that as well if you're short on time right now.
(I guess the patchset is the same you posted for linux-azure.)
Thanks,
Mauricio
--
Y
Hi, @overlord.
I changed it to "linux" instead because xenial/linux-hwe is simply a
backport of bionic/linux, so we need to apply the fix to bionic/linux
first and that will be include to xenial/linux-hwe automatically.
--
You received this bug notification because you are a member of Kernel
Pac
Hey guys, I am not sure how to do this but can you also make a patch for
Xenial, 4.15.0-generic, for linux-hwe package? We have the same problem
and we can't upgrade the boxes to a newer release so this would really
help us.
** Package changed: linux (Ubuntu) => linux-hwe (Ubuntu)
** Changed in:
Can't run the logs collection tool since the system is stuck in D state
and times out. (Also the tool is not installed on the systems). We just
need this fix back-ported on 4.15.0-generic for Xenial on linux-hwe
package (we don't use linux-azure)
** Changed in: linux-hwe (Ubuntu Cosmic)
St
Can't run the logs collection tool since the system is stuck in D state
and times out. (Also the tool is not installed on the systems). We just
need this fix back-ported on 4.15.0-generic for Xenial on linux-hwe
package (we don't use linux-azure)
** Changed in: linux-hwe (Ubuntu Bionic)
St
https://lists.ubuntu.com/archives/kernel-team/2019-February/098264.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1802021
Title:
[Hyper-V] srcu: Lock srcu_data structure in sr
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: linux-azure (Ubuntu Bionic)
** No longer affects: linux-azure (Ubuntu Cosmic)
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: linux-azure (Ubuntu
** No longer affects: linux-meta-hwe (Ubuntu)
** No longer affects: linux-meta-hwe (Ubuntu Bionic)
** No longer affects: linux-meta-hwe (Ubuntu Cosmic)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.l
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-meta-hwe (Ubuntu Cosmic)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launch
** Package changed: linux-hwe (Ubuntu) => linux-meta-hwe (Ubuntu)
--
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/1802021
Title:
[Hyper-V] srcu: Lock srcu_data structure in srcu_gp_
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-meta-hwe (Ubuntu Bionic)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launch
** Changed in: linux-hwe (Ubuntu)
Status: New => Confirmed
--
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/1802021
Title:
[Hyper-V] srcu: Lock srcu_data structure in srcu_gp_
** Also affects: linux-hwe (Ubuntu)
Importance: Undecided
Status: New
--
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/1802021
Title:
[Hyper-V] srcu: Lock srcu_data structu
** Also affects: linux-azure (Ubuntu Cosmic)
Importance: Undecided
Status: New
** Also affects: linux-azure (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: linux-azure (Ubuntu Bionic)
Assignee: (unassigned) => Marcelo Cerri (mhcerri)
** Changed in: linux
Yes, please, per comment #8
--
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/1802021
Title:
[Hyper-V] srcu: Lock srcu_data structure in srcu_gp_start()
Status in linux-azure package
Hi, Josh. Should we apply the fixes for the 4.15 and 4.18 linux-azure
kernel then?
--
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/1802021
Title:
[Hyper-V] srcu: Lock srcu_data stru
The fix was picked up for upstream stable 4.19.15 and 4.20.2. I would
expect the generic kernels to eventually pick up this fix.
--
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/1802021
Using Ubuntu 16.04.5 LTS btw.
--
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/1802021
Title:
[Hyper-V] srcu: Lock srcu_data structure in srcu_gp_start()
Status in linux-azure packa
Will this fix be available for Linux 4.15.0-generic x86_64, or is it
available already?
I am currently on Linux 4.15.0-43-generic x86_64 and on some servers I
have this issue, others are fine, I am not sure what triggers the
problem but when it triggers kworker, dockerd, systemd, go in
uninterrupt
No new instances of the problem on the test cluster for many weeks.
Let's move forward with this change.
--
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/1802021
Title:
[Hyper-V] src
Hi, Josh.
Did you have any feedback from the customer regarding the test kernel?
How do you want to proceed with that?
--
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/1802021
Title:
** Changed in: linux-azure (Ubuntu)
Assignee: Joseph Salisbury (jsalisbury) => Marcelo Cerri (mhcerri)
** Changed in: linux-azure (Ubuntu)
Status: In Progress => Triaged
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-az
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 srcu_
Hi Joshua,
I just reviewed the commit Joseph provided in the launchpad. It's the
same as the two patches I backported.
eb4c2382272a srcu: Lock srcu_data structure in srcu_gp_start()
d633198088bd srcu: Prohibit call_srcu() use under raw spinlocks
The commit id eb4c2382272a is the latest linux-nex
Joe, is your kernel different than the one Gavin Guo built for us here?
https://launchpad.net/~mimi0213kimo/+archive/ubuntu/sf00204509-rcu-
backport
We have enabled extra debugging and given that kernel to our internal
customer who attempting to repro. Since the repro takes a very long time
it is
** Tags added: bjf
** Tags removed: bjf
** Tags added: bjf-tracking
--
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/1802021
Title:
[Hyper-V] srcu: Lock srcu_data structure in srcu
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:
http://kernel.ubuntu.com/~j
** 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 Kernel
Packages, which is subscribed to linux-azure in Ubun
It's a heavy database workload from a online site, so it is difficult to
make a simple repro for.
--
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/1802021
Title:
[Hyper-V] srcu: Lock
Hi, Josh. Do you have an specific workload that triggers that issue?
--
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/1802021
Title:
[Hyper-V] srcu: Lock srcu_data structure in srcu_
** Tags added: kernel-da-key kernel-hyper-v
** Changed in: linux-azure (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux-azure (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to li
68 matches
Mail list logo
