From: Steven Rostedt <rostedt@goodmis.org>
To: "H. Peter Anvin" <hpa@linux.intel.com>
Cc: Dave Jones <davej@redhat.com>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
Ingo Molnar <mingo@redhat.com>, Andi Kleen <ak@linux.intel.com>
Subject: Re: tracing ring_buffer_resize oops.
Date: Thu, 24 May 2012 21:41:46 -0400 [thread overview]
Message-ID: <1337910106.13348.234.camel@gandalf.stny.rr.com> (raw)
In-Reply-To: <1337909963.13348.232.camel@gandalf.stny.rr.com>
On Thu, 2012-05-24 at 21:39 -0400, Steven Rostedt wrote:
> > Specifically, note that the value of R12 is the same
> > value; R12 is a preserved register and may have been pushed onto the
> > stack by something that wants to save it.
>
> I don't see R12 as the same value:
>
> RIP: <ffff88014630a000>
> GS: ffff880148000000
> R12: ffff880145cc0000
>
> Close but not quite. Even R13 and R15 are close:
>
> R13: ffff880148008eb8
> R15: ffff88014780cb40
>
> But this probably does show that the stack is screwed up and did a bad
> iret.
>
Here's the stack of the first time I saw this crash:
RIP: 92dc:[<ffff88007dc042a0>] [<ffff88007dc042a0>] 0xffff88007dc0429f
RSP: 0018:0000000000000576 EFLAGS: 00000575
RAX: 0000000000000001 RBX: ffffffff812b4e6e RCX: ffff88007e209e00
RDX: 0000000000005495 RSI: ffffffff826165b0 RDI: ffff88007e209eb8
RBP: ffff88007e209ed8 R08: 0000000000000000 R09: 0000000000000000
R10: ffff880078d6fa00 R11: ffff880078d6fa00 R12: ffff880078c3dfa0
R13: ffffffff810b92dc R14: 00000000000000e6 R15: 00000000000000e8
FS: 0000000000000000(0000) GS:ffff88007e200000(0000)
knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
CR2: ffff88007dc042a0 CR3: 0000000069ec4000 CR4: 00000000000007f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
RCX, RDI, RBP, R10, R11, and R12 are all like GS and RIP.
-- Steve
next prev parent reply other threads:[~2012-05-25 1:41 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-24 16:01 Dave Jones
2012-05-24 16:19 ` Steven Rostedt
2012-05-24 17:22 ` Dave Jones
2012-05-24 17:35 ` Steven Rostedt
2012-05-24 18:47 ` Dave Jones
2012-05-24 18:54 ` Steven Rostedt
2012-05-24 19:11 ` Dave Jones
2012-05-24 19:24 ` Steven Rostedt
2012-05-24 20:05 ` Dave Jones
2012-05-24 20:18 ` Steven Rostedt
2012-05-24 20:33 ` Steven Rostedt
2012-05-24 21:15 ` Dave Jones
2012-05-24 21:25 ` Steven Rostedt
2012-05-24 22:49 ` Steven Rostedt
2012-05-24 22:57 ` Dave Jones
2012-05-24 23:40 ` Steven Rostedt
2012-05-24 23:53 ` H. Peter Anvin
2012-05-25 1:32 ` Steven Rostedt
2012-05-25 1:39 ` Steven Rostedt
2012-05-25 1:41 ` Steven Rostedt [this message]
2012-05-25 14:31 ` BUG - function tracing with breakpoints (was: Re: tracing ring_buffer_resize oops.) Steven Rostedt
2012-05-25 15:29 ` Steven Rostedt
2012-05-25 17:40 ` BUG - function tracing with breakpoints H. Peter Anvin
2012-05-25 18:46 ` Steven Rostedt
2012-05-25 20:51 ` Steven Rostedt
2012-05-26 1:36 ` Steven Rostedt
2012-05-29 11:37 ` Steven Rostedt
2012-05-29 13:26 ` Steven Rostedt
2012-05-25 0:14 ` tracing ring_buffer_resize oops Andi Kleen
2012-05-25 1:31 ` Steven Rostedt
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=1337910106.13348.234.camel@gandalf.stny.rr.com \
--to=rostedt@goodmis.org \
--cc=ak@linux.intel.com \
--cc=davej@redhat.com \
--cc=fweisbec@gmail.com \
--cc=hpa@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®