From: John Levon <levon@movementarian.org>
To: Dave Hansen <haveblue@us.ibm.com>
Cc: oprofile-list@lists.sourceforge.net,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Oops running oprofile in 2.5.62
Date: Thu, 27 Feb 2003 17:37:04 +0000 [thread overview]
Message-ID: <20030227173704.GA76419@compsoc.man.ac.uk> (raw)
In-Reply-To: <3E5DB057.60503@us.ibm.com>
On Wed, Feb 26, 2003 at 10:29:43PM -0800, Dave Hansen wrote:
> I'm pretty sure it happened on this line in oprofile_add_sample():
> cpu_buf->buffer[cpu_buf->pos].eip = eip;
>
> Unable to handle kernel paging request at virtual address f8c3c000
Odd. UP or SMP ? Were you shutting down oprofile at the time (or did the
daemon crash ? check /var/lib/oprofile/oprofiled.log)
The only thing I can think is that the buffer got freed then we got an
NMI afterwards (which obviously isn't supposed to happen...)
UP oprofile in current linus is still totally broken, but I can't
imagine it causing the above.
regards
john
next prev parent reply other threads:[~2003-02-27 17:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-27 6:29 Oops running oprofile in 2.5.62 Dave Hansen
2003-02-27 17:37 ` John Levon [this message]
2003-02-27 17:54 ` Dave Hansen
2003-03-05 20:15 ` Philippe Elie
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=20030227173704.GA76419@compsoc.man.ac.uk \
--to=levon@movementarian.org \
--cc=haveblue@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oprofile-list@lists.sourceforge.net \
/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