From: compudj@krystal.dyndns.org (Mathieu Desnoyers)
Subject: [ltt-dev] kernel panic
Date: Tue, 9 Feb 2010 13:11:37 -0500 [thread overview]
Message-ID: <20100209181137.GA21812@Krystal> (raw)
In-Reply-To: <4B703231.7080407@polymtl.ca>
* Benjamin Poirier (benjamin.poirier at polymtl.ca) wrote:
> <snip>
> >
> > And which compiler version do you use to compile your kernel ? Did you
> > try doing a make clean, and then rebuild to see if the resulting kernel
> > (with immediate values activated) still cause this problem ?
> >
> > Thanks,
> >
> > Mathieu
> >
> >
> gcc (Debian 4.3.4-6) 4.3.4
> make clean and using 2.6.32.4-lttng-0.189
>
> The problem remains. I can reproduce it on an AMD Athlon(tm) XP 2500+
> and on a kvm virtual machine (QEMU Virtual CPU version 0.9.1) I can give
> you access to the disk image for that machine if you'd like to.
>
Yes, that could be helpful.
I'd need the output of (with CONFIG_IMMEDIATE activated):
make clean
make V=1 > outputfile.txt 2>&1
(I'd need outputfile.txt)
Basically, I want to see if traps.c is build with -DUSE_IMMEDIATE or
not.
Trying to add some printks in arch/x86/kernel/immediate.c:
imv_notifier() to figure out whether or not it is being called would
also help.
Thanks,
Mathieu
--
Mathieu Desnoyers
OpenPGP key fingerprint: 8CD5 52C3 8E3C 4140 715F BA06 3F25 A8FE 3BAE 9A68
next prev parent reply other threads:[~2010-02-09 18:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-01 16:17 Benjamin Poirier
2010-02-01 16:52 ` Mathieu Desnoyers
2010-02-01 20:51 ` Benjamin Poirier
2010-02-02 22:09 ` Mathieu Desnoyers
2010-02-03 14:55 ` Benjamin Poirier
2010-02-03 14:55 ` Benjamin Poirier
2010-02-06 17:55 ` Mathieu Desnoyers
2010-02-08 15:48 ` Benjamin Poirier
2010-02-09 18:11 ` Mathieu Desnoyers [this message]
[not found] ` <4B71AB45.8040804@polymtl.ca>
2010-02-11 14:31 ` Mathieu Desnoyers
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=20100209181137.GA21812@Krystal \
--to=compudj@krystal.dyndns.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