On Thu, Apr 01, 2010 at 01:09:03AM -0700, David Miller wrote:
quoted text
> From: Frederic Weisbecker <fweisbec@gmail.com>
> Date: Thu, 1 Apr 2010 11:06:11 +0200
> 
> > I actually can't. It works well on a backup 2.6.31-rc6 kernel
> > but when I build a new one of this same version, the problem
> > happens again. And I don't have the config of the one that works
> > (and no /proc/config.gz as well).
> > 
> > So I suspect this is something that happens with some specific
> > configs only.
> > 
> > Anyway, once I get more clues about this, I'll tell you.
> 
> I was going to ask you if any of your compiler tools changed
> recently...
> 
> Check the gcc version printed by the working kernel at the top of the
> dmesg logs and compare to what you end up using now.


They are exactly the same :)

gcc version 4.3.2 (Debian 4.3.2-1.1)

Really I think I need to dig further as I don't have useful
clues to provide. I need to check if the segfault always happen
in the same place, etc...

It seems to happen with ld as well btw (not sure this is related
though):

[ 3366.005962] ld[19041]: segfault at 10 ip 000000007010248c (rpc 00000000701023f8) sp 00000000ffda87c8 error 30001 
in libbfd-2.18.0.20080103.so[700d8000+a0000]

--
unsubscribe notice
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/