From: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>
To: Mel Gorman <mgorman@suse.de>
Cc: "linux-mm@kvack.org" <linux-mm@kvack.org>,
srikar@linux.vnet.ibm.com, aarcange@redhat.com, mingo@kernel.org,
riel@redhat.com
Subject: Re: NUMA Autobalancing Kernel 3.8
Date: Mon, 08 Apr 2013 11:14:10 +0200 [thread overview]
Message-ID: <51628A62.1050507@profihost.ag> (raw)
In-Reply-To: <20130408081316.GB2623@suse.de>
Am 08.04.2013 10:13, schrieb Mel Gorman:
> On Fri, Apr 05, 2013 at 02:10:32PM +0200, Stefan Priebe - Profihost AG wrote:
>> Am 05.04.2013 14:00, schrieb Mel Gorman:
>>> On Wed, Apr 03, 2013 at 04:11:24PM +0200, Stefan Priebe - Profihost AG wrote:
>>>> Am 03.04.2013 16:03, schrieb Mel Gorman:
>>>>>> I've now tested 3.9-rc5 this gaves me a slightly different kernel log:
>>>>>> [ 197.236518] pigz[2908]: segfault at 0 ip (null) sp
>>>>>> 00007f347bffed00 error 14
>>>>>> [ 197.237632] traps: pigz[2915] general protection ip:7f3482dbce2d
>>>>>> sp:7f3473ffec10 error:0 in libz.so.1.2.3.4[7f3482db7000+17000]
>>>>>> [ 197.330615] in pigz[400000+10000]
>>>>>>
>>>>>> With 3.8 it is the same as with 3.8.4 or 3.8.5.
>>>>>>
>>>>>
>>>>> Ok. Are there NUMA machines were you do *not* see this problem?
>>>> Sadly no.
>>>>
>>>> I can really fast reproduce it with this one:
>>>> 1.) Machine with only 16GB Mem
>>>> 2.) compressing two 60GB Files in parallel with pigz consuming all cores
>>>>
>>>
>>> Ok, I'm dealing with this slower than I'd like due to an unfortunate
>>> abundance of bugs right now. I am putting together a reproduction case but
>>> I still can't trigger it unfortunately. Can you post your .config in case
>>> it's my kernel config that is the reason I can't see the problem please?
>>
>> no problem. Attaches is my kernel config.
>>
>
> It does indeed appear that the kernel configuration is a factor. Can you
> try applying the following to your .config please?
>
> --- config-bad 2013-04-07 21:08:02.213112445 +0100
> +++ .config 2013-04-07 23:28:09.275973625 +0100
> @@ -2518,8 +2518,8 @@
> CONFIG_TMPFS=y
> CONFIG_TMPFS_POSIX_ACL=y
> CONFIG_TMPFS_XATTR=y
> -# CONFIG_HUGETLBFS is not set
> -# CONFIG_HUGETLB_PAGE is not set
> +CONFIG_HUGETLBFS=y
> +CONFIG_HUGETLB_PAGE=y
> CONFIG_CONFIGFS_FS=y
> CONFIG_MISC_FILESYSTEMS=y
> # CONFIG_ADFS_FS is not set
Yes this works!
Stefan
--
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>
prev parent reply other threads:[~2013-04-08 9:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-02 7:24 NUMA Autobalancing Kernel 3.8 Stefan Priebe - Profihost AG
2013-04-02 10:48 ` Mel Gorman
2013-04-02 11:41 ` Stefan Priebe - Profihost AG
2013-04-02 12:54 ` Mel Gorman
2013-04-02 14:34 ` Stefan Priebe - Profihost AG
2013-04-03 14:03 ` Mel Gorman
2013-04-03 14:11 ` Stefan Priebe - Profihost AG
2013-04-05 12:00 ` Mel Gorman
2013-04-05 12:10 ` Stefan Priebe - Profihost AG
2013-04-08 8:13 ` Mel Gorman
2013-04-08 9:14 ` Stefan Priebe - Profihost AG [this message]
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=51628A62.1050507@profihost.ag \
--to=s.priebe@profihost.ag \
--cc=aarcange@redhat.com \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=mingo@kernel.org \
--cc=riel@redhat.com \
--cc=srikar@linux.vnet.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.