From: Arjan van de Ven <arjan@linux.intel.com>
To: Vegard Nossum <vegard.nossum@gmail.com>
Cc: Ingo Molnar <mingo@elte.hu>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Error in save_stack_trace() on x86_64?
Date: Sun, 11 May 2008 12:58:42 -0700 [thread overview]
Message-ID: <48274FF2.8040202@linux.intel.com> (raw)
In-Reply-To: <19f34abd0805111256q29055475leb329179034df20c@mail.gmail.com>
Vegard Nossum wrote: in userspace this trace looks correct.
>
> No, it is happening from kernel code. As you can see from the original
> backtrace, the regs->ip (RIP) (regs taken from the very same
> do_page_fault()) points at add_uevent_var, which is a kernel function.
>
>> if it happens in kernel space... I wonder if the separate exception stack
>> thing
>> is hurting us with the stacks not being properly connected...
>> (but oopses and the like seem to come out just fine so I kinda doubt you're
>> hitting that)
>>
>
> Thanks for looking into this.
>
do you happen to have something that I maybe can reproduce?
(if you have that it would save me a ton of time in reproducing)
>
> Vegard
>
next prev parent reply other threads:[~2008-05-11 19:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-11 13:09 Error in save_stack_trace() on x86_64? Vegard Nossum
2008-05-11 19:44 ` Arjan van de Ven
2008-05-11 19:56 ` Vegard Nossum
2008-05-11 19:58 ` Arjan van de Ven [this message]
2008-05-18 17:13 ` Vegard Nossum
2008-05-18 18:31 ` Vegard Nossum
2008-05-18 18:52 ` Arjan van de Ven
2008-05-18 20:23 ` Vegard Nossum
-- strict thread matches above, loose matches on Subject: below --
2008-05-11 20:46 Vegard Nossum
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=48274FF2.8040202@linux.intel.com \
--to=arjan@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=vegard.nossum@gmail.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