From: Eric Dumazet <dada1@cosmosbay.com>
To: Andrew Morton <akpm@osdl.org>
Cc: ak@suse.de, linux-kernel@vger.kernel.org
Subject: Re: Something very strange on x86_64 2.6.X kernels
Date: Thu, 20 Jan 2005 22:19:40 +0100 [thread overview]
Message-ID: <41F0206C.5040605@cosmosbay.com> (raw)
In-Reply-To: <20050120130848.14a92990.akpm@osdl.org>
Andrew Morton wrote:
> Eric Dumazet <dada1@cosmosbay.com> 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
next prev parent reply other threads:[~2005-01-20 21:19 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-19 23:13 COMMAND_LINE_SIZE increasing in 2.6.11-rc1-bk6 Janos Farkas
2005-01-20 4:21 ` Chris Bruner
2005-01-20 16:28 ` Adrian Bunk
2005-01-20 16:40 ` Linus Torvalds
2005-01-20 16:48 ` Andi Kleen
2005-01-20 20:53 ` Something very strange on x86_64 2.6.X kernels Eric Dumazet
2005-01-20 21:08 ` Andrew Morton
2005-01-20 21:19 ` Eric Dumazet [this message]
2005-01-21 16:26 ` Petr Vandrovec
2005-01-21 16:49 ` Eric Dumazet
2005-01-21 18:30 ` Petr Vandrovec
2005-01-22 1:54 ` Andi Kleen
2005-01-22 2:14 ` Linus Torvalds
2005-01-21 6:58 ` COMMAND_LINE_SIZE increasing in 2.6.11-rc1-bk6 Catalin(ux aka Dino) BOIE
2005-01-21 7:11 ` Andi Kleen
2005-01-21 17:46 ` Matt Domsch
2005-01-21 19:05 ` H. Peter Anvin
2005-02-07 6:57 ` Werner Almesberger
2005-02-12 13:54 ` Eric W. Biederman
2005-02-12 14:51 ` Werner Almesberger
2005-02-12 15:17 ` Eric W. Biederman
2005-02-14 5:49 ` Werner Almesberger
2005-02-14 7:36 ` Eric W. Biederman
2005-02-14 6:15 ` Adam Sulmicki
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=41F0206C.5040605@cosmosbay.com \
--to=dada1@cosmosbay.com \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox