Re: Something very strange on x86_64 2.6.X kernels

2005-01-21 Thread Linus Torvalds
On Sat, 22 Jan 2005, Andi Kleen wrote: > > I applied the patch to my tree. I already applied it as obvious ;) Linus - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel

Re: Something very strange on x86_64 2.6.X kernels

2005-01-21 Thread Andi Kleen
On Fri, Jan 21, 2005 at 05:26:01PM +0100, Petr Vandrovec wrote: > On Thu, Jan 20, 2005 at 09:53:36PM +0100, Eric Dumazet wrote: > > > > Examining linux sources, I found that 0xe000 is 'special' (ia 32 > > vsyscall) and 0xe600 is about sigreturn subsection of this special area. > > > > Is

Re: Something very strange on x86_64 2.6.X kernels

2005-01-21 Thread Petr Vandrovec
On Fri, Jan 21, 2005 at 05:49:25PM +0100, Eric Dumazet wrote: > Petr Vandrovec wrote: > > > > >Maybe I already missed answer, but try patch below. It is definitely bad > >to mark syscall page as global one... > > > > Hi Petr > > If I follow you, any 64 bits program is corrupted as soon one 32bi

Re: Something very strange on x86_64 2.6.X kernels

2005-01-21 Thread Eric Dumazet
Petr Vandrovec wrote: Maybe I already missed answer, but try patch below. It is definitely bad to mark syscall page as global one... Hi Petr If I follow you, any 64 bits program is corrupted as soon one 32bits program using sysenter starts ? Thank you for the patch, I will try it as soon as poss

Re: Something very strange on x86_64 2.6.X kernels

2005-01-21 Thread Petr Vandrovec
On Thu, Jan 20, 2005 at 09:53:36PM +0100, Eric Dumazet wrote: > > Examining linux sources, I found that 0xe000 is 'special' (ia 32 > vsyscall) and 0xe600 is about sigreturn subsection of this special area. > > Is it possible some vm trick just kicks in and corrupts my true 64bits > prog

Re: Something very strange on x86_64 2.6.X kernels

2005-01-20 Thread Eric Dumazet
Andrew Morton wrote: Eric Dumazet <[EMAIL PROTECTED]> wrote: Every time the crash occurs when one thread is using some ram located at virtual address 0xe6xx What does "using" mean? Is the program executing from that location? No, the program text is located between 0x0010 and 0x001c6000

Re: Something very strange on x86_64 2.6.X kernels

2005-01-20 Thread Andrew Morton
Eric Dumazet <[EMAIL PROTECTED]> wrote: > > Hi Andi > > I have very strange coredumps happening on a big 64bits program. > > Some background : > - This program is multi-threaded > - Machine is a dual Opteron 248 machine, 12GB ram. > - Kernel 2.6.6 (tried 2.6.10 too but problems too) > - The prog

Something very strange on x86_64 2.6.X kernels

2005-01-20 Thread Eric Dumazet
Hi Andi I have very strange coredumps happening on a big 64bits program. Some background : - This program is multi-threaded - Machine is a dual Opteron 248 machine, 12GB ram. - Kernel 2.6.6 (tried 2.6.10 too but problems too) - The program uses hugetlb pages. - The program uses prefetchnta - The p