From: Ingo Molnar <mingo@elte.hu>
To: Andi Kleen <andi@firstfloor.org>
Cc: Sami Farin <safari-kernel@safari.iki.fi>,
Linux kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.22.6 + oprofile oops
Date: Mon, 1 Oct 2007 16:47:33 +0200 [thread overview]
Message-ID: <20071001144733.GA5975@elte.hu> (raw)
In-Reply-To: <p73ejgf6sch.fsf@bingen.suse.de>
* Andi Kleen <andi@firstfloor.org> wrote:
> > 2007-09-22 13:53:32.527330808 <4>[ 3372.390363] Pid: 7, comm:
> > events/0 Not tainted 2.6.22.6-cfs-v20.5-64-2 #7
^^^^^^^^^^^
>
> Can you reproduce it with a non tainted kernel without any patches
> like CFS applied?
the kernel is not tainted, as indicated in the log message above.
> The oops happens because oprofile tries to reference a NULL task in
> its event buffer for a context switch, which might well be a minor
> merging mistake or similar in the CFS backport.
CFS does not change that aspect of the oprofile code.
Ingo
prev parent reply other threads:[~2007-10-01 14:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-22 11:23 2.6.22.6 + oprofile oops Sami Farin
2007-09-29 17:05 ` Sami Farin
2007-10-11 14:36 ` Philippe Elie
2007-10-11 18:09 ` Sami Farin
2007-10-01 10:29 ` Andi Kleen
2007-10-01 13:22 ` Sami Farin
2007-10-01 14:47 ` Ingo Molnar [this message]
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=20071001144733.GA5975@elte.hu \
--to=mingo@elte.hu \
--cc=andi@firstfloor.org \
--cc=linux-kernel@vger.kernel.org \
--cc=safari-kernel@safari.iki.fi \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox