Latest 3.13 kernel update (3.13.0-46) is causing kernel panics related to IPv6
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| linux (Ubuntu) |
Critical
|
Andy Whitcroft | |||
| Trusty |
Critical
|
Andy Whitcroft | |||
Bug Description
Hello,
Pretty similar to what happened with https:/
I've been getting about daily kernel panics (three times so far).
Screenshot attached. Another user also commented in bug 1404558 about the bug being back, though I'm assuming it's a different albeit very similar one.
| tags: | added: kernel-key |
| Changed in linux (Ubuntu Trusty): | |
| status: | New → Triaged |
| importance: | Undecided → Critical |
| tags: | added: trusty |
| Changed in linux (Ubuntu): | |
| assignee: | nobody → Andy Whitcroft (apw) |
| Changed in linux (Ubuntu Trusty): | |
| assignee: | nobody → Andy Whitcroft (apw) |
| Andy Whitcroft (apw) wrote : | #2 |
| Andy Whitcroft (apw) wrote : | #3 |
Ok on investigation it seems git am is broken in the sense it is quite happy to apply a fix backwards without any warning:
$ git checkout -b TEST Ubuntu-3.13.0-45.74
$ git format-patch -1 f34c7de1e2df67a
0001-
$ git am 0001-ipv6-
Applying: ipv6: fix swapped ipv4/ipv6 mtu_reduced callbacks
$
Wrong, wrong, wrong, wrong wrong.
| Changed in linux (Ubuntu): | |
| status: | Triaged → Invalid |
From the looks of things, when v3.13.11-ckt14 was applied which also contains the fix for the original issue, somehow the fix got applied reversed and undid the fix!