From: Gerald Schaefer <gerald.schaefer@de.ibm.com>
To: Nishanth Aravamudan <nacc@us.ibm.com>
Cc: schwidefsky@de.ibm.com, LKML <linux-kernel@vger.kernel.org>,
agl@us.ibm.com
Subject: Re: s390 hugetlb oops with libhugetlbfs test-suite
Date: Tue, 05 Aug 2008 17:49:32 +0200 [thread overview]
Message-ID: <1217951372.5032.21.camel@localhost.localdomain> (raw)
In-Reply-To: <20080729214638.GA20641@us.ibm.com>
On Tue, 2008-07-29 at 14:46 -0700, Nishanth Aravamudan wrote:
> Beyond the counters case, I saw one other issue on s390 (haven't
> confirmed if it happens anywhere else), the icache-hygiene test, when
> run manually a few times, will fail every so often claiming that one of
> the mmap()s returned ENOMEM. I haven't had time to track that down yet,
> but it might be because of the address space layout and the size of the
> hugepage on s390.
I have posted a patch that will fix the counters oops. So far, I could
not reproduce the icache-hygiene problem, did you use hardware large page
support or software emulation? But I probably noticed a similar one:
map_high_truncate_2 (32): FAIL mmap() 1: Cannot allocate memory
That one should be because of the 31-bit address space layout on s390,
as it tries to mmap too much (1.5GB).
I also noticed that task-size-overrun (64) seems to hang up on my system,
I can only continue after ctrl+c, can you verify that?
Thanks,
Gerald
next prev parent reply other threads:[~2008-08-05 15:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-25 21:10 s390 hugetlb oops with libhugetlbfs test-suite Nishanth Aravamudan
2008-07-26 3:32 ` Nishanth Aravamudan
2008-07-26 3:41 ` Nishanth Aravamudan
2008-07-29 17:22 ` Gerald Schaefer
2008-07-29 21:46 ` Nishanth Aravamudan
2008-08-05 15:49 ` Gerald Schaefer [this message]
2008-08-05 16:14 ` Nishanth Aravamudan
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=1217951372.5032.21.camel@localhost.localdomain \
--to=gerald.schaefer@de.ibm.com \
--cc=agl@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nacc@us.ibm.com \
--cc=schwidefsky@de.ibm.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.