All of lore.kernel.org
 help / color / mirror / Atom feed
From: Randy Dunlap <randy.dunlap@oracle.com>
To: Nish Aravamudan <nish.aravamudan@gmail.com>
Cc: linux-mm@kvack.org
Subject: Re: hugepage test failures
Date: Mon, 23 Jul 2007 13:30:08 -0700	[thread overview]
Message-ID: <46A50FD0.2020001@oracle.com> (raw)
In-Reply-To: <29495f1d0707231318n5e76d141t5f81431ead007b53@mail.gmail.com>

Nish Aravamudan wrote:
> On 7/23/07, Randy Dunlap <randy.dunlap@oracle.com> wrote:
>> Hi,
>>
>> I'm a few hundred linux-mm emails behind, so maybe this has been
>> addressed already.  I hope so.
>>
>> I run hugepage-mmap and hugepage-shm tests (from Doc/vm/hugetlbpage.txt)
>> on a regular basis.  Lately they have been failing, usually with -ENOMEM,
>> but sometimes the mmap() succeeds and hugepage-mmap gets a SIGBUS:
> 
> Would it be possible for you instead to run the libhugetlbfs tests?

OK, I'm downloading that now.

> They are kept uptodate, at least.

You mean that the Doc/ tree is not kept up to date?  ;(

But this represents an R*word (regression).
These tests ran successfully until recently (I can't say when).

>> open("/mnt/hugetlbfs/hugepagefile", O_RDWR|O_CREAT, 0755) = 3
>> mmap(NULL, 268435456, PROT_READ|PROT_WRITE, MAP_SHARED, 3, 0) = 
>> 0x2af31d2c3000
>> fstat(1, {st_mode=S_IFCHR|0620, st_rdev=makedev(136, 1), ...}) = 0
>> mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 
>> 0) = 0x2af32d2c3000
>> write(1, "Returned address is 0x2af31d2c30"..., 35) = 35
>> --- SIGBUS (Bus error) @ 0 (0) ---
>> +++ killed by SIGBUS +++
>>
>>
>> and:
>>
>> # ./hugepage-shm
>> shmget: Cannot allocate memory
>>
>>
>> I added printk()s in many mm/mmap.c and mm/hugetlb.c error return
>> locations and got this:
>>
>> hugetlb_reserve_pages: -ENOMEM
>>
>> which comes from mm/hugetlb.c::hugetlb_reserve_pages():
>>
>>         if (chg > cpuset_mems_nr(free_huge_pages_node)) {
>>                 printk(KERN_DEBUG "%s: -ENOMEM\n", __func__);
>>                 return -ENOMEM;
>>         }
>>
>> I had CONFIG_CPUSETS=y so I disabled it, but the same error
>> still happens.
> 
> As in the same cpusets_mems_nr() check fails?
> 
>> Suggestions?  Fixex?
> 
> Which kernel is this?

Ah, sorry, 2.6.23-rc1.


-- 
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2007-07-23 20:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-23 19:04 hugepage test failures Randy Dunlap
2007-07-23 20:18 ` Nish Aravamudan
2007-07-23 20:30   ` Randy Dunlap [this message]
2007-07-23 20:29     ` Nish Aravamudan
2007-07-23 20:45       ` Randy Dunlap
2007-07-24  0:23     ` Ken Chen
2007-07-24  0:02 ` Ken Chen

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=46A50FD0.2020001@oracle.com \
    --to=randy.dunlap@oracle.com \
    --cc=linux-mm@kvack.org \
    --cc=nish.aravamudan@gmail.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.