Matt, please open a new bug report. As your problem neither does seem to
be unexpected complete hangs or crashes, nor isolated to 3.13.0-64.104
this unlikely is the same issue. Ideally run "ubuntu-bug linux" from an
affected machine. Note also that 3.13.0-64.104 never left the proposed
stage. So
Ever since we started picking up the 3.13.0-65 kernel in the openstack
CI system on 9/29 we've been seeing lots of random failures across 3
branches (juno/kilo/master) with ebtables, details are in:
https://bugs.launchpad.net/nova/+bug/1501558
An example failure:
This bug was fixed in the package linux - 3.19.0-30.33
---
linux (3.19.0-30.33) vivid; urgency=low
[ Brad Figg ]
* Release Tracking Bug
- LP: #1498065
* Revert "[Config]
MFD_INTEL_LPSS/MFD_INTEL_LPSS_ACPI/MFD_INTEL_LPSS_PCI=m"
- LP: #1498137
* [Config] Disable
This bug was fixed in the package linux - 3.13.0-65.105
---
linux (3.13.0-65.105) trusty; urgency=low
[ Brad Figg ]
* Release Tracking Bug
- LP: #1498108
[ Upstream Kernel Changes ]
* net: Fix skb_set_peeked use-after-free bug
- LP: #1497184
linux
Hello. I updated with the proposed updates my ununtu 14.04 and installed
the 3.13.0-64.104 kernel on the 24 of september. I got a first kernel
panic after many hours of work and after reboot even after about an
hour. I removed this kernel and installed the 3.13.0-65.-generic which
was in the
** Changed in: linux (Ubuntu Vivid)
Status: Confirmed => Fix Committed
** Changed in: linux (Ubuntu Trusty)
Status: Confirmed => Fix Committed
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of
Hi henrix - I'm trying your patched kernel, will update soon with results.
I too get the kernel panics in 3.13.0-64, but not in -63.
In -64 they are very frequent, so it shouldn't take long to see one again it
re-occurs anyway with your patch in place.
--
You received this bug notification
henrix.
Now I'm using you kerenel. It made 24 hours uptime. So your patch is
working.
--
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/1497184
Title:
Kernel-panic with 3.13.0-64.104
@Arjen -- this package has not been released into the LTS it is only in
-proposed for testing. This is exactly why we build and publish these
kernels into -proposed and why they sit there for some time before being
released into -updates. In this case the kernel carries a regression,
one which
@apw / @henrix - ah, that's good. No worries.
That explains why only my laptop has had the issue, as indeed I do pull in
updates from proposed there and that's fine - happy to help catch stuff early.
So, all is as it should be! awesome. thanks!
--
You received this bug notification because you
I concur with loann, although mine has only been up for 2h20. With the
unpatched kernel it would've long panicked.
--
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/1497184
Title:
henrix - just a note, probably pointing out the obvious
I find it a tad frustrating that this situation happened with an LTS release,
by the looks of it through a mistake of pulling in an incomplete or untested
kernel patch.
I'd rather not see that happen in LTS, it's causing a bit of grief
Hi. Got panic again. New panic messages are in attach.
It was direct while router updated my IP address.
** Attachment added: "panic.tar.gz"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1497184/+attachment/4469190/+files/panic.tar.gz
--
You received this bug notification because you
** Tags added: bios-outdated-3.50
--
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/1497184
Title:
Kernel-panic with 3.13.0-64.104 generic kernel (BUG at
net/core/skbuff:1290)
Status in
** Also affects: linux (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Vivid)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Trusty)
Status: New => Confirmed
** Changed in: linux (Ubuntu Vivid)
Status: New =>
I suspect the issue is related with commit
commit 738ac1ebb96d02e0d23bc320302a6ea94c612dec
Author: Herbert Xu
Date: Mon Jul 13 16:04:13 2015 +0800
net: Clone skb before setting peeked flag
This commit was included in Trusty 3.13.0-64.104, and introduces a
16 matches
Mail list logo