On Wed, Nov 06, 2013 at 04:30:05PM -0800, David Rientjes wrote:
> On Mon, 4 Nov 2013, Mel Gorman wrote:
>
> > This maybe?
> >
> > ---8<---
> > mm: memcontrol: Release css_set_lock when aborting an OOM scan
> >
> > css_task_iter_start acquires the css_set_lock and it must be released with
> > a c
On Mon, 4 Nov 2013, Mel Gorman wrote:
> This maybe?
>
> ---8<---
> mm: memcontrol: Release css_set_lock when aborting an OOM scan
>
> css_task_iter_start acquires the css_set_lock and it must be released with
> a call to css_task_iter_end. Commmit 9cbb78bb (mm, memcg: introduce own
> oom handler
On 11/04/2013 12:04 PM, Mel Gorman wrote:
> On Tue, Oct 22, 2013 at 01:29:22PM -0400, Don Morris wrote:
>> Greetings, all.
>>
>> Just wanted to drop this out there to see if it rang any bells.
>> I've been getting a soft lockup (numad thread stuck on a cpu
>> while attempting to attach a task to a
On Tue, Oct 22, 2013 at 01:29:22PM -0400, Don Morris wrote:
> Greetings, all.
>
> Just wanted to drop this out there to see if it rang any bells.
> I've been getting a soft lockup (numad thread stuck on a cpu
> while attempting to attach a task to a cgroup) for a while now,
> but I thought it was
ns and was unable to
reproduce the problem. numad is certainly runnign because I can see
its effect.
> /var/log/messages output attached, trimmed to just one boot+instance
> of the problem.
>
> Oct 22 11:05:10 hornet2 kernel: BUG: soft lockup - CPU#8 stuck for 22s!
> [numad:27384]
>
5 matches
Mail list logo
