Date: Fri, 5 Apr 2019 21:49:18 -0700 From: Riccardo Veraldi <riccardo.veraldi@gmail.com> To: =?utf-8?Q?=D0=90=D0=BB=D0=B5=D0=BA=D1=81=D0=B5=D0=B9_=D0=9F=D1=80=D0=BE=D0=BA=D0=BE=D0=BF=D1=87=D1=83=D0=BA?= <alexpro.ewr@gmail.com> Cc: Freebsd-Sparc64 <freebsd-sparc64@freebsd.org> Subject: Re: Question about RSS limit Message-ID: <899b0854-9941-437f-ad3c-8baa8334be59@Rs-iPhone> In-Reply-To: <3d08b630-5c05-3d35-cfab-57d0243ba997@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Are you sure you don’t have a memory problem ? Did you run a hardware test on your Sun Fire ?
>
> On Apr 5, 2019 at 3:31 PM, <Алексей Прокопчук (mailto:alexpro.ewr@gmail.com)> wrote:
>
>
>
> Greetings!
>
> My English is not very good, excuse me if I said something wrong.
>
> I trying to build packages for FreeBSD sparc64 and faced some problems.
>
> I have Sun Fire V120 with installed FreeBSD-11.2 GENERIC downloaded from
> official location.
>
> There were problems with package building (for example - perl and gcc7),
> make fails sometime with "internal compiler error" or "segmentation
> fault". But building continues when I repeat make after error. After
> all, I was able to build gcc7 and perl which are dependency for most
> packages. Now I have problem with using git: I trying to clone FreeBSD
> source from github and git always fails with segmentation fault. I
> monitored clone process with top and discover that RES memory for any
> process never exceeds 32800K, and SIZE never exceeds approx. 600M. I
> tried to increase limits by setting kern.maxdsiz parameter, but no
> success, git fails with segfault anyway, and RES never exceeds 32800K. I
> tested same git clone on amd64 and RES grows to 500M during operation.
>
> Same with gcc7 and perl building. Build fails when compile big and
> complex file, and SIZE of c1plusplus process grows about 600M, but RES
> has always max. value 32800K.
>
> On amd64 kern.maxdsiz has default value 32G, on sparc64 - 1G. When I
> tried to grow it to 2G, absolutely all processes crashes with
> segmentation fault (include init on boot). With value 1.5G system works
> fine but git fails anyway. The only difference - SIZE of git process
> grows up to 928M before crash, RES retains 32800K.
>
> There is some limit for process memory in sparc64? I can't find anything
> about such limits, and stuck. I understand that my hardware very old and
> slow, but I don't have another one unfortunately...
>
> Thanks in advance, with best regards, Alexey Prokopchuk.
>
>
> _______________________________________________
> freebsd-sparc64@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-sparc64
> To unsubscribe, send any mail to "freebsd-sparc64-unsubscribe@freebsd.org"
>
From owner-freebsd-sparc64@freebsd.org Sat Apr 6 08:06:03 2019
Return-Path: <owner-freebsd-sparc64@freebsd.org>
Delivered-To: freebsd-sparc64@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1])
by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6546715798E2
for <freebsd-sparc64@mailman.ysv.freebsd.org>;
Sat, 6 Apr 2019 08:06:03 +0000 (UTC)
(envelope-from alexpro.ewr@gmail.com)
Received: from mail-lf1-x143.google.com (mail-lf1-x143.google.com
[IPv6:2a00:1450:4864:20::143])
(using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
(Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK))
by mx1.freebsd.org (Postfix) with ESMTPS id 45B7E6E051
for <freebsd-sparc64@freebsd.org>; Sat, 6 Apr 2019 08:06:02 +0000 (UTC)
(envelope-from alexpro.ewr@gmail.com)
Received: by mail-lf1-x143.google.com with SMTP id v14so6049864lfi.0
for <freebsd-sparc64@freebsd.org>; Sat, 06 Apr 2019 01:06:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s 161025;
h=subject:references:to:from:message-id:date:user-agent:mime-version
:in-reply-to:content-language;
bh=JHZlveyr5JxfVSW9uIjKTSl4Vn4edGzyLmUUgolzZDQ=;
b=j82S0RYwWreJEhLeabllxGNMo81OrYVTewj4gaTG9OG1LHv6DXWj8pz/zPvSClQg9X
fCdgcdmsrBmf19ZGNo0FcX5Horz0mJgV/nmLJFW5ARG20x93GwfcwaeVqQ7sCxJCfUei
5Pf6aEqnMZqewebQdlD+5Ojmp9cy/XdhE4BBDAnxrn8vsiDSrNbL/jVQwfkE7Izm9R4u
nv+c5yIpNUFRuOmPf1+e4G2mm5G1LrJnbrXkb+nRhfKF9zJQYHMoWAEN1TFniPjHAcvZ
sg0PtBRHHOFcvUDOO3TtcesdgEZxFUx2elUyet4jgb5WYzmj6O0Ag+k+83Dz5C2WJ2/x
MTJg=X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d 100.net; s 161025;
h=x-gm-message-state:subject:references:to:from:message-id:date
:user-agent:mime-version:in-reply-to:content-language;
bh=JHZlveyr5JxfVSW9uIjKTSl4Vn4edGzyLmUUgolzZDQ=;
b=LDDMBTSoryXhO9BOPMX34J95VbxEi0PvXHAkGV8I9GpH6Ry/tcw9b+d5rb7oiKq3iv
ar2ZrHtycL7/+CggH9KruDtXmDauUoq3nen4dpd9flWXy+O1vve4/G2r66wadsFAffXb
uusYsvql6laDL6B/usOCEFoEH62EW6yj0Pa8Pf4SPfZp/8om92lgdmYSDApbYmaq5F4v
yE0+8a1o+8qxmX0hQQKP0K2q4HvO/qnYaZ5ck7k2QDkT5j5UYw1klZfaiUBleTmkSPXa
B8R8mK8NQk0Tdr3hOMskzQZzoeGVnXw3RAFCAoXL8MC5rb65+ZDNfOjgRVqSMe/UhymB
Patg=X-Gm-Message-State: APjAAAUoBGnKiWufs4PYE0xx6FedMSIR645a+jMIAKEXRCjMRklWltQF
tHWvb8hMxla5zVBrnZwcTgIVZZks
X-Google-Smtp-Source: APXvYqyc8GqGxVFApaHC/Fg0cH8Gn8JUBg7f7C7aYXC0H6XHQAdeYtdlZ9h2kZzKWvrsygIhNJITHg=X-Received: by 2002:ac2:5204:: with SMTP id a4mr8917130lfl.149.1554537960512;
Sat, 06 Apr 2019 01:06:00 -0700 (PDT)
Received: from [192.168.200.55] (city-gw.homelan.lg.ua. [194.0.206.33])
by smtp.googlemail.com with ESMTPSA id m19sm5220111lji.70.2019.04.06.01.05.59
for <freebsd-sparc64@freebsd.org>
(version=TLS1_2 cipherDHE-RSA-AES128-GCM-SHA256 bits8/128);
Sat, 06 Apr 2019 01:05:59 -0700 (PDT)
Subject: Re: Question about RSS limit
References: <225b64ec-fceb-e0f3-a363-3673b96ec6d3@gmail.com>
To: freebsd-sparc64@freebsd.org
From: =?UTF-8?B?0JDQu9C10LrRgdC10Lkg0J/RgNC+0LrQvtC/0YfRg9C6? <alexpro.ewr@gmail.com>
X-Forwarded-Message-Id: <225b64ec-fceb-e0f3-a363-3673b96ec6d3@gmail.com>
Message-ID: <bddcba91-a4a8-f8a7-ca66-73e5633d1f8a@gmail.com>
Date: Sat, 6 Apr 2019 11:05:58 +0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101
Thunderbird/52.3.0
MIME-Version: 1.0
In-Reply-To: <225b64ec-fceb-e0f3-a363-3673b96ec6d3@gmail.com>
Content-Language: ru-RU
X-Rspamd-Queue-Id: 45B7E6E051
X-Spamd-Bar: ----
Authentication-Results: mx1.freebsd.org;
dkim=pass header.d=gmail.com header.s 161025 header.b=j82S0RYw;
dmarc=pass (policy=none) header.from=gmail.com;
spf=pass (mx1.freebsd.org: domain of alexproewr@gmail.com designates
2a00:1450:4864:20::143 as permitted sender)
smtp.mailfrom=alexproewr@gmail.com
X-Spamd-Result: default: False [-4.44 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[];
R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36];
FREEMAIL_FROM(0.00)[gmail.com]; TO_DN_NONE(0.00)[];
RCVD_COUNT_THREE(0.00)[3]; DKIM_TRACE(0.00)[gmail.com:+];
DMARC_POLICY_ALLOW(-0.50)[gmail.com,none];
MX_GOOD(-0.01)[cached: alt3.gmail-smtp-in.l.google.com];
NEURAL_HAM_SHORT(-0.94)[-0.943,0]; FROM_EQ_ENVFROM(0.00)[];
RCVD_TLS_LAST(0.00)[]; MIME_TRACE(0.00)[0:+,1:+];
FREEMAIL_ENVFROM(0.00)[gmail.com];
ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US];
TAGGED_FROM(0.00)[];
DWL_DNSWL_NONE(0.00)[gmail.com.dwl.dnswl.org : 127.0.5.0];
ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0];
R_DKIM_ALLOW(-0.20)[gmail.com:s 161025];
MID_RHS_MATCH_FROM(0.00)[]; FROM_HAS_DN(0.00)[];
TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0];
MIME_GOOD(-0.10)[multipart/alternative,text/plain];
PREVIOUSLY_DELIVERED(0.00)[freebsd-sparc64@freebsd.org];
RCPT_COUNT_ONE(0.00)[1];
IP_SCORE(-0.49)[ip: (2.17), ipnet: 2a00:1450::/32(-2.38), asn: 15169(-2.17),
country: US(-0.06)];
RCVD_IN_DNSWL_NONE(0.00)[3.4.1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.5.4.1.0.0.a.2.list.dnswl.org
: 127.0.5.0]
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
X-Content-Filtered-By: Mailman/MimeDel 2.1.29
X-BeenThere: freebsd-sparc64@freebsd.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Porting FreeBSD to the Sparc <freebsd-sparc64.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-sparc64>,
<mailto:freebsd-sparc64-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-sparc64/>;
List-Post: <mailto:freebsd-sparc64@freebsd.org>
List-Help: <mailto:freebsd-sparc64-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-sparc64>,
<mailto:freebsd-sparc64-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 06 Apr 2019 08:06:03 -0000
Yes, I did. No errors detected. I think, I never would have been able to
successful build gcc with broken memory. And I absolutely don't
understand why RSS of any process does not exceed 32800K... On amd64 RSS
of the same task 10 times bigger than on sparc64.
06.04.2019 07:49, Riccardo Veraldi пишет:
> Are you sure you don’t have a memory problem ? Did you run a hardware
> test on your Sun Fire ?
>
>
>> On Apr 5, 2019 at 3:31 PM, <Алексей Прокопчук
>> <mailto:alexpro.ewr@gmail.com>> wrote:
>>
>> Greetings!
>>
>>
>>
>> My English is not very good, excuse me if I said something wrong.
>>
>>
>>
>> I trying to build packages for FreeBSD sparc64 and faced some problems.
>>
>>
>>
>> I have Sun Fire V120 with installed FreeBSD-11.2 GENERIC downloaded from
>>
>> official location.
>>
>>
>>
>> There were problems with package building (for example - perl and gcc7),
>>
>> make fails sometime with "internal compiler error" or "segmentation
>>
>> fault". But building continues when I repeat make after error. After
>>
>> all, I was able to build gcc7 and perl which are dependency for most
>>
>> packages. Now I have problem with using git: I trying to clone FreeBSD
>>
>> source from github and git always fails with segmentation fault. I
>>
>> monitored clone process with top and discover that RES memory for any
>>
>> process never exceeds 32800K, and SIZE never exceeds approx. 600M. I
>>
>> tried to increase limits by setting kern.maxdsiz parameter, but no
>>
>> success, git fails with segfault anyway, and RES never exceeds 32800K. I
>>
>> tested same git clone on amd64 and RES grows to 500M during operation.
>>
>>
>>
>> Same with gcc7 and perl building. Build fails when compile big and
>>
>> complex file, and SIZE of c1plusplus process grows about 600M, but RES
>>
>> has always max. value 32800K.
>>
>>
>>
>> On amd64 kern.maxdsiz has default value 32G, on sparc64 - 1G. When I
>>
>> tried to grow it to 2G, absolutely all processes crashes with
>>
>> segmentation fault (include init on boot). With value 1.5G system works
>>
>> fine but git fails anyway. The only difference - SIZE of git process
>>
>> grows up to 928M before crash, RES retains 32800K.
>>
>>
>>
>> There is some limit for process memory in sparc64? I can't find anything
>>
>> about such limits, and stuck. I understand that my hardware very old and
>>
>> slow, but I don't have another one unfortunately...
>>
>>
>>
>> Thanks in advance, with best regards, Alexey Prokopchuk.
>>
>>
>>
>>
>>
>> _______________________________________________
>>
>> freebsd-sparc64@freebsd.org mailing list
>>
>> https://lists.freebsd.org/mailman/listinfo/freebsd-sparc64
>>
>> To unsubscribe, send any mail to "freebsd-sparc64-unsubscribe@freebsd.org"
>>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?899b0854-9941-437f-ad3c-8baa8334be59>