From: "Jörg Sommer" <joerg@alea.gnuu.de>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Frederic Weisbecker <fweisbec@gmail.com>,
Ingo Molnar <mingo@redhat.com>,
linux-kernel@vger.kernel.org, linuxppc-dev@ozlabs.org
Subject: Re: Oops in trace_hardirqs_on (powerpc)
Date: Mon, 27 Sep 2010 14:50:37 +0200 [thread overview]
Message-ID: <20100927125037.GA4497@alea.gnuu.de> (raw)
In-Reply-To: <1285184671.26872.127.camel@gandalf.stny.rr.com>
[-- Attachment #1: Type: text/plain, Size: 720 bytes --]
Hello Steven,
Steven Rostedt hat am Wed 22. Sep, 15:44 (-0400) geschrieben:
> Sorry for the late reply, but I was on vacation when you sent this, and
> I missed it while going through email.
>
> Do you still have this issue?
No. I've rebuild my kernel without TRACE_IRQFLAGS and the problem
vanished, as expected. The problem is, that in some cases the stack is
only two frames deep, which causes the macro CALLER_ADDR1 makes an
invalid access. Someone told me, there a workaround for the problem on
i386, too.
% sed -n 2p arch/x86/lib/thunk_32.S
* Trampoline to trace irqs off. (otherwise CALLER_ADDR1 might crash)
Bye, Jörg.
--
Angenehme Worte sind nie wahr,
wahre Worte sind nie angenehm.
[-- Attachment #2: Digital signature http://en.wikipedia.org/wiki/OpenPGP --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2010-09-27 14:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20100806233157.GA7117@alea.gnuu.de>
2010-09-22 19:44 ` Oops in trace_hardirqs_on (powerpc) Steven Rostedt
2010-09-27 12:50 ` Jörg Sommer [this message]
2010-09-28 1:58 ` Steven Rostedt
2010-12-19 13:27 ` Jörg Sommer
2010-12-20 20:43 ` Steven Rostedt
2010-12-20 21:12 ` Steven Rostedt
2010-12-23 2:42 ` Steven Rostedt
2010-12-26 0:30 ` Jörg Sommer
2011-01-21 0:46 ` 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=20100927125037.GA4497@alea.gnuu.de \
--to=joerg@alea.gnuu.de \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=mingo@redhat.com \
--cc=rostedt@goodmis.org \
/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;
as well as URLs for NNTP newsgroup(s).