For the xenial/linux-hwe kernel, 4.15.0-62.69~16.04.1 with this fix has
been published. Are you seeing this issue in xenial's 4.4 kernel.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1842447
Title:
4.15.0-62.69~16.04.1 is available on -updates
https://kernel.ubuntu.com/sru/sru-report.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1842447
Title:
Kernel Panic with
Disregard. Looks like 4.15.0.1048 is installed but running uname -a
shows 4.15.0.1047 so the box just hasn't been rebooted since the update
and since it's an AWS ASG it's just reverting back to the 1047 version
from the AMI every time it panics and AWS re-creates the instance. Time
to rebuild
Hi, @uxian.
linux-aws 4.15.0-1047 has the bug, and I can reproduce it. linux-aws
4.15.0-1048, however, has the fix and should not present the bug. I can
confirm I wasn't able to reproduce the issue. Can you send any logs?
Thanks.
Cascardo.
--
You received this bug notification because you are
I'm seeing the same kernel panic on linux-aws 4.15.0.1048.47 as well
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1842447
Title:
Kernel Panic with linux-image-4.15.0-60-generic when specifying
Will this be available for xenial soon?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1842447
Title:
Kernel Panic with linux-image-4.15.0-60-generic when specifying
nameserver in docker-compose
This bug was fixed in the package linux - 4.15.0-62.69
---
linux (4.15.0-62.69) bionic; urgency=medium
* bionic/linux: 4.15.0-62.69 -proposed tracker (LP: #1842746)
* Kernel Panic with linux-image-4.15.0-60-generic when specifying nameserver
in docker-compose (LP: #1842447)
Could you please release 4.15.0-62 into the main repo? It's still in the
proposed. Thank you.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1842447
Title:
Kernel Panic with
FTR, 4.15.0-62 seems *much* better than 4.15.0-60. With 4.15.0-60 this
system was kernel panic restarting every 75-90 minutes; now it's been up
since I installed 4.15.0-62, over 5 hours ago:
-=- cut here -=-
ewen@naosr620:~$ uname -r
4.15.0-62-generic
ewen@naosr620:~$ uptime
16:09:54 up 5:26,
FTR, I think this is the fix in -62:
https://kernel.ubuntu.com/git/ubuntu/ubuntu-bionic.git/commit/?h=master-
next=b502cfeffec81be8564189e5498fd3f252b27900
and it appears to be the only change from -60 to -62:
-=- cut here -=-
ewen@naosr620:~$ zcat
I agree with Taher (in
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1842447/comments/15),
this bug seems to impact a lot of systems (my colo host was kernel panic
restarting about every 75-90 minutes, all weekend). It has a NAT
firewall on it (for the hosted VMs), but no Docker/Wireguard,
This bug has to be dealt with a higher degree of urgency. It impacts any
machine that performs any type of NAT. Is not application specific
though.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: linux (Ubuntu Bionic)
Status: Fix Released => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1842447
Title:
Kernel Panic with linux-image-4.15.0-60-generic when
The last status change happened on accident. The fix has not been
released, yet. I cannot change the status back to "Fix Committed"
though. Can anyone help with this?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: linux (Ubuntu Bionic)
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/1842447
Title:
Kernel Panic with linux-image-4.15.0-60-generic when
It's possible this same issue is responsible for this crash in
WireGuard:
https://lists.zx2c4.com/pipermail/wireguard/2019-September/004495.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1842447
We updated last night (4.15.0-60) and started having issues this
morning... issue has been fixed with update to 5.0.0.27 HWE. We’re up
and running again, but trying to figure out where the issue stems from.
Is the issue caused from a bug or an attack?
--
You received this bug notification
** Changed in: linux (Ubuntu Bionic)
Status: Fix Released => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1842447
Title:
Kernel Panic with linux-image-4.15.0-60-generic when
Oh. I was able to set the status to released? :-D Sorry. Not released
yet.
** Changed in: linux (Ubuntu Bionic)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I can also confirm that it's now working. Thanks a lot for the fast fix,
@cascardo!
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Fixed it for me (via 4.15.0-62-generic).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1842447
Title:
Kernel Panic with linux-image-4.15.0-60-generic when specifying
nameserver in docker-compose
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
Thank you for fixing this, most appreciated.
When will the fix be available on the repos? On the next kernel release?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1842447
Title:
Kernel Panic with
Thanks!!!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1842447
Title:
Kernel Panic with linux-image-4.15.0-60-generic when specifying
nameserver in docker-compose
To manage notifications about
I was affected by this (or a very similar bug), but it only happened on
the first HTTP request to a docker-compose managed docker container.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1842447
** Changed in: linux (Ubuntu Bionic)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1842447
Title:
Kernel Panic with linux-image-4.15.0-60-generic when
** Description changed:
+ [Impact]
+ Some fragmentation+NAT workloads will cause kernel BUG/Ooops.
+
+ [Test case]
+ sudo iptables -t nat -I POSTROUTING -j MASQUERADE
+ sudo hping3 192.168.122.1 -s 1000 -p 2000 -d 6
+
+ [Regression potential]
+ This could make fragmented packets stop
** Changed in: linux (Ubuntu Bionic)
Status: Confirmed => In Progress
** Changed in: linux (Ubuntu Bionic)
Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo)
** Changed in: linux (Ubuntu Bionic)
Importance: Undecided => Critical
--
You received this bug
** Changed in: linux (Ubuntu Bionic)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1842447
Title:
Kernel Panic with linux-image-4.15.0-60-generic when specifying
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1842447
Title:
Kernel Panic with linux-image-4.15.0-60-generic when
We were just affected by this bug on one of our server. I was able to
get some information from the kernel log (see attachment).
It appears to crash at net/ipv4/ip_output.c:636:
Sep 4 07:54:04 gonzo kernel: [ 145.912955] kernel BUG at
/build/linux-5mCauq/linux-4.15.0/net/ipv4/ip_output.c:636!
Tested using the docker-compose.yml with original docker-compose.yml
with every container but unbound using -dns.
Test1: Crashed (took less than 1 minutes to crash)
Fully updated ubuntu, using Scaleway's ubuntu image. (4.15.0-60-generic)
Crash:
** Also affects: linux
Importance: Undecided
Status: New
** No longer affects: linux
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1842447
Title:
Kernel Panic with
** Summary changed:
- Kernel Panic with linux-image-4.15.0-60-generic when using docker-compose
with dns setting
+ Kernel Panic with linux-image-4.15.0-60-generic when specifying nameserver in
docker-compose
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
34 matches
Mail list logo
