I could see this patch d90a10e2444ba5a351fa695917258ff4c5709fa5 has
landed in GCP Eoan, and generic kernels.
Therefore I will just mark this as fix-released, please feel free re-
open it if you think this is incorrect.
** Changed in: linux-gcp (Ubuntu)
Status: Confirmed => Fix Released
** Tags added: cscc
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-gcp in Ubuntu.
https://bugs.launchpad.net/bugs/1771075
Title:
General Protection fault in inotify (fixed upstream)
Status in linux package in Ubuntu:
** Changed in: linux (Ubuntu Cosmic)
Status: In Progress => Confirmed
** Changed in: linux (Ubuntu)
Status: In Progress => Confirmed
** Changed in: linux (Ubuntu)
Assignee: Joseph Salisbury (jsalisbury) => (unassigned)
** Changed in: linux (Ubuntu Cosmic)
Assignee:
Thanks, much appreciated!
--
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/1771075
Title:
General Protection fault in inotify (fixed upstream)
Status in linux package in Ubuntu:
In
Thanks for the heads up, Joshua!
No need to open a separate bug for linux-gcp. I added that package to
this bug. bug 1765564 does not have cosmic or linux-gcp, so we can use
this bug for those two.
** Also affects: linux-gcp (Ubuntu)
Importance: Undecided
Status: New
** No longer
Yup, I think this is a dupe of that. I noticed that bug was filed
against linux-azure; do I need to file a corresponding bug against
linux-gcp to get the patch sent there as well?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
Looks like a duplicate of https://bugs.launchpad.net/ubuntu/+source
/linux-azure/+bug/1765564
--
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/1771075
Title:
General Protection fault in
The commit to fix this bug was added to Artful and Bionic via bug
1765564, so I'll remove those bug tasks. I did, however, submit a
request to have this commit added to Cosmic.
** Changed in: linux (Ubuntu Artful)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu Cosmic)
** Changed in: linux (Ubuntu Cosmic)
Status: In Progress => Fix Committed
** 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.
Any fix that goes into Artful is also applied to the 4.13 HWE kernel in
Xenial. The fix will get into the HWE kernel that way.
--
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/1771075
Cool! I noticed you've marked the bug as affecting Artful, Bionic and
Cosmic but it also affects Xenial with the 4.13 HWE kernels; should that
be marked here as well?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
I will submit an SRU request to have that commit included in the
affected Ubuntu kernels. Then the fix will be available in the next set
of kernel updates.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Good news - I got the chance to test this in our production environment
today for about 7 hours and no issues whatsoever. Given that this
workload was triggering the issue pretty reliably within about half an
hour before, I think this fix has done the trick. Thanks a bunch for
your help!
What are
To install the kernel, just use dpkg like you said. Instead of changing
GRUB_DEFAULT, you could also manually select the test kernel from the
GRUB menu on boot. The grub menu can be accessed by holding the SHIFT
key on boot up, after the BIOS information is displayed.
--
You received this bug
Awesome, thanks for getting back to me so quickly! Unfortunately we're
in a change freeze at the moment - I'll try and get an exemption
approved to test this but I may have to wait until Monday to try it out.
Is there anything special I have to do to boot your test kernels on
Xenial other than
I built Artful and Bionic test kernels with commit
d90a10e2444ba5a351fa695917258ff4c5709fa5. The test kernel can be downloaded
from:
http://kernel.ubuntu.com/~jsalisbury/lp1771075
Can you test this kernel and see if it resolves this bug?
Note about installing test kernels:
• If the test
** Also affects: linux (Ubuntu Artful)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Artful)
Status: New => Triaged
** Changed in: linux (Ubuntu Artful)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
**
I've upload the apport information from a host that had the issue but
note that I had to downgrade the kernel back to 4.10 due to this issue,
so that's what is included in the apport information.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug
apport information
** Tags added: apport-collected
** Description changed:
We've run into some issues where upgrading the kernel from a 4.10 series
to a 4.13 series on Ubuntu 16.04 hosts that make heavy use of inotify
causes panics and lockups in the kernel in inotify-related code. Our
** Attachment added: "Dmesg output after general protection fault"
https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/1771075/+attachment/5139125/+files/protection_fault.log
** Package changed: linux-gcp (Ubuntu) => linux (Ubuntu)
--
You received this bug notification because you are
20 matches
Mail list logo
