All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Sasha Levin <sasha.levin@oracle.com>
Cc: Ingo Molnar <mingo@kernel.org>, Mel Gorman <mgorman@suse.de>,
	LKML <linux-kernel@vger.kernel.org>,
	Dave Jones <davej@redhat.com>
Subject: Re: sched,numa: invalid memory access in account_entity_dequeue
Date: Tue, 6 May 2014 15:40:16 +0200	[thread overview]
Message-ID: <20140506134016.GL11096@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <5368D43D.5050601@oracle.com>

[-- Attachment #1: Type: text/plain, Size: 819 bytes --]

On Tue, May 06, 2014 at 08:23:25AM -0400, Sasha Levin wrote:
> > I suppose you've scripted this addr2line -ie vmlinux for all addresses in this splat?
> 
> Yeah, I'm trying to get that script upstream (https://lkml.org/lkml/2014/3/29/1)
> since it seems to simplify looking at stack traces.

Seems like a nice addition to scripts/ indeed. Although Linus doesn't
seem to like it much:

  http://marc.info/?l=linux-kernel&m=139862933908922


> > Could you maybe also do the same with the Code? -- that is, script an auto-decode for it?

> Sure, I can look into that.

Thanks!

> > la-la-la..
> > 
> 
> I haven't seen it happening again, so maybe an unrelated memory corruption?

Yeah, just the thing we need :/ In any case, let me know if you do hit
it again this side of the Sun burning up.



[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2014-05-06 13:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-03 13:16 sched,numa: invalid memory access in account_entity_dequeue Sasha Levin
2014-05-06 11:08 ` Peter Zijlstra
2014-05-06 12:23   ` Sasha Levin
2014-05-06 13:40     ` Peter Zijlstra [this message]
2014-05-06 14:20       ` Sasha Levin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20140506134016.GL11096@twins.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --cc=davej@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mgorman@suse.de \
    --cc=mingo@kernel.org \
    --cc=sasha.levin@oracle.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.