The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release
** Changed in: linux (Ubuntu Precise)
Status: In Progress => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Changed in: linux (Ubuntu)
Assignee: (unassigned) = Jay Vosburgh (jvosburgh)
** Changed in: linux (Ubuntu Precise)
Assignee: (unassigned) = Jay Vosburgh (jvosburgh)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
** Changed in: linux (Ubuntu Precise)
Assignee: Chris J Arges (arges) = (unassigned)
--
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/1233175
Title:
Kernel panic : mempolicy
I will not be able to provide a reproducer of this immediately. If you
agree, please keep this open until I can have it or someone comes here
with his/her reproducer.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Unfortunately, we don't have a repro case yet. Do you really need a
repro case to proceed this?
--
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/1233175
Title:
Kernel panic : mempolicy
** Changed in: linux (Ubuntu Precise)
Assignee: Louis Bouchard (louis-bouchard) = Chris J Arges (arges)
** Changed in: linux (Ubuntu)
Assignee: Louis Bouchard (louis-bouchard) = (unassigned)
--
You received this bug notification because you are a member of Kernel
Packages, which is
Can those affected by this issue test this build with the patch identified by
@kamatam?
http://people.canonical.com/~arges/lp1233175/
Thanks!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Hi Chris,
Does anyone of you have a repro case? Although the patch itself is
really straightforward, I don't have a reliable repro case of this race
unfortunately.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
A similar case is here:
http://www.mail-archive.com/linux-kernel@vger.kernel.org/msg351591.html
It seems like using NUMA with high load MongoDB workloads are factors in
causing this crash.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Hi,
We also have experienced this issue with 3.2.0-57-generic. Thanks to the
core dump analysis by Louis Bouchard, I could notice that accessing
current-mempolicy in interrupt context is totally bad idea, and then
found the following commit.
Gentlemen, so far, both the custom patched kernel and 3.8.0-30-generic
have been stable. We will keep one server on this kernel, and a number
of servers on 3.2.0-55-generic and on .57, so you'll have data to
compare.
--
You received this bug notification because you are a member of Kernel
@christopher,
Lois was provided with a custom kernel that includes a patch to be
tested. The patch comes from apw, following a kernel dump analysis that
I did. From what we could gather, a possible race condition could be
responsible for the panics.
So far, I have yet to get the confirmation
Louis Bouchard, this bug was reported a while ago and there hasn't been
any activity in it recently. We were wondering if this is still an
issue? If so, could you please test for this with the latest development
release of Ubuntu? ISO images are available from
I have one server, previously affected by the bug, that has been stable
for 8 days on 3.8.0-30-generic.
We also just provisioned 24 servers with 3.2.0-57-generic (not yet in
production).
If I can provide any information to you that would help, please let me
know through the ticket.
--
You
lois garcia, thank you for your comments. It would be most helpful if
this could be fully reverse commit bisected from 3.2.0-38-generic to
3.8.0-30-generic in order to identify the fix commit. Could you please
do this following https://wiki.ubuntu.com/Kernel/KernelBisection ?
--
You received
** Changed in: linux (Ubuntu Precise)
Status: Triaged = In Progress
--
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/1233175
Title:
Kernel panic : mempolicy potential
Here is an analysis of the kernel core dump captured for this issue :
crash sys
KERNEL: vmlinux-3.2.0-38-generic
DUMPFILE: VmCore
CPUS: 24
DATE: Wed Sep 18 22:34:35 2013
UPTIME: 1 days, 11:33:14
LOAD AVERAGE: 2.04, 2.09, 2.16
TASKS: 6656
NODENAME:
** Also affects: linux (Ubuntu Precise)
Importance: Undecided
Status: New
--
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/1233175
Title:
Kernel panic : mempolicy potential
** Changed in: linux (Ubuntu Precise)
Status: New = Triaged
** Changed in: linux (Ubuntu Precise)
Assignee: (unassigned) = Louis Bouchard (louis-bouchard)
** Changed in: linux (Ubuntu Precise)
Importance: Undecided = High
--
You received this bug notification because you are a
19 matches
Mail list logo
