From mboxrd@z Thu Jan  1 00:00:00 1970
From: compudj@krystal.dyndns.org (Mathieu Desnoyers)
Date: Tue, 9 Feb 2010 13:11:37 -0500
Subject: [ltt-dev] kernel panic
In-Reply-To: <4B703231.7080407@polymtl.ca>
References: <4B66FE92.7070608@polymtl.ca> <20100201165235.GA12946@Krystal>
	<4B673EC4.3090204@polymtl.ca> <20100202220928.GD656@Krystal>
	<4B698E79.9010803@polymtl.ca> <20100206175514.GA1726@Krystal>
	<4B703231.7080407@polymtl.ca>
Message-ID: <20100209181137.GA21812@Krystal>

* 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