I can confirm this problem (vs 2.2.0) and kernel 2.6.19. It goes away if you use gcc-3.4, but it does not go away if you add -fno-stack-protector to CFLAGS.
I can confirm this problem (vs 2.2.0) and kernel 2.6.19. It goes away if you use gcc-3.4, but it does not go away if you add -fno-stack- protector to CFLAGS.