From owner-freebsd-current@FreeBSD.ORG Fri Jan 17 07:47:32 2014 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 685AAD17 for ; Fri, 17 Jan 2014 07:47:32 +0000 (UTC) Received: from mail-la0-f53.google.com (mail-la0-f53.google.com [209.85.215.53]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id DBD9D17C6 for ; Fri, 17 Jan 2014 07:47:31 +0000 (UTC) Received: by mail-la0-f53.google.com with SMTP id e16so3281669lan.26 for ; Thu, 16 Jan 2014 23:47:23 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=ixW1mHYGOSoWEgU7fPGCezZ0tX8H8y7IO2ysomFPpjI=; b=lUGNaDuhGROBZtO5LHgHsi/BQZtx5zZLysp1ISODMy7tderdNgkbtClBJxZvktXxoi Xq3hW5Oc07AMAAXBHzt428ee8yQxK23+NZfz1ygoTh2jRgx/lXwI/c+CYHi9KKlGjarU DsF1ISLovklC6+R+1h7L6VbHguT0vSUaxYAepPo2pBm5qPqn1wF6h+OsZYMbeOTsHF0w gr/0NCwPKwZRkM2b8Tj8n7twI4hlIJ96XwDXJPBaTOngYlYfQmV8fTjOouWRA4QUSrjC VZYpsZKj5S3+4S6lU67T2xTTr5n9UMwhXxMDmWhYI6fYepLyhV+4qMkuD5zIVnlz6s3i g46w== X-Gm-Message-State: ALoCoQnzd+l6TrXcGK8BUMP8MjySRYi8uN3KZAcC4n4r0GE28+ZOf+4Yt3L7JrBMaW83CQrS8iTV X-Received: by 10.112.64.227 with SMTP id r3mr251441lbs.24.1389944843610; Thu, 16 Jan 2014 23:47:23 -0800 (PST) Received: from [192.168.1.2] ([89.169.173.68]) by mx.google.com with ESMTPSA id gi5sm2746914lbc.4.2014.01.16.23.47.22 for (version=TLSv1.2 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 16 Jan 2014 23:47:23 -0800 (PST) Message-ID: <52D8E00A.6060907@freebsd.org> Date: Fri, 17 Jan 2014 11:47:22 +0400 From: Andrey Chernov User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: Alexander , current@FreeBSD.org Subject: Re: SCHED_ULE bug (was Re: cpuminer mines only on one core regardless of "--threads" option) References: <399751389704518@web9j.yandex.ru> <52D541E7.3040305@gmail.com> <5101389708996@web13m.yandex.ru> <52D55B24.8080102@freebsd.org> <113571389724340@web5g.yandex.ru> <37721389856823@web8h.yandex.ru> In-Reply-To: <37721389856823@web8h.yandex.ru> X-Enigmail-Version: 1.7a1pre Content-Type: text/plain; charset=KOI8-R Content-Transfer-Encoding: 7bit Cc: "stable@freebsd.org" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Jan 2014 07:47:32 -0000 On 16.01.2014 11:20, Alexander wrote: > > > 14.01.2014, 22:32, "Alexander" : >> 14.01.2014, 20:14, "Subbsd" : >> >>> On Tue, Jan 14, 2014 at 7:43 PM, Andrey Chernov wrote: >>>> On 14.01.2014 17:01, Alexander wrote: >>>>> on Freebsd 9.2 x64 on 5 different PCs I installed net-p2p/cpuminer >>>>> from ports and by "pkg install" - result is the same - minerd mines >>>>> only on one core regardless of "--threads" option. >>>> ... >>>>> # top -P >>>>> CPU 0: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle >>>>> CPU 1: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle >>>>> CPU 2: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle >>>>> CPU 3: 0.0% user, 100% nice, 0.0% system, 0.0% interrupt, 0.0% idle >>>> This is SCHED_ULE bug, I see _all_ processes (not minerd only in >>>> particular) stuck to the last CPU too (top's 'C' column is equal to the >>>> last CPU and never changes), latest -stable i386. It disappears for me >>>> switching to SCHED_4BSD. >>>> >> >> reboot didn't help (try on 3 different PCs) > ... > minerd was started from cron after reboot immediately and broke SMP, so when I disable minerd from cron and reboot - SMP works fine. > I think Andrey Chernov said here the reason http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/163585#reply3 > So this bug is alive - on 9.1 and 9.2 x64 releases. > I didn't try SCHED_4BSD yet, cause don't wont to use not-generic kernel because of mining only, but for interest I'll try it on one machine on this weekends. I just try it on latest x64 -current, result is exact the same: the bug exist with SCHED_ULE and not with SCHED_4BSD. Something is very wrong in SCHED_ULE+cpuset_setaffinity chain.