Andrew Morton wrote:
Eric Dumazet <[EMAIL PROTECTED]> wrote:
Every time the crash occurs when one thread is using some ram located at virtual address 0xffffe6xx
What does "using" mean? Is the program executing from that location?
No, the program text is located between 0x00100000 and 0x001c6000 (no shared libs)
0xffffe6xx is READ|WRITE data, mapped on Hugetlb fs
extract from /proc/pid/maps
ff400000-100400000 rw-s 82000000 00:0b 12960938 /huge/file
Interesting. IIRC, opterons will very occasionally (and incorrectly) take a fault when performing a prefetch against a dud pointer. The kernel will fix that up. At a guess, I'd say tha the fixup code isn't doing the right thing when the faulting EIP is in the vsyscall page.
Maybe, but I want to say that in this case, the address 'prefetched' is valid (ie mapped read/write by the program, on a huge page too)
Thanks Eric Dumazet
- 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.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/