From owner-freebsd-stable@freebsd.org Thu Oct 4 10:57:44 2018 Return-Path: Delivered-To: freebsd-stable@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 AC18310C85B2 for ; Thu, 4 Oct 2018 10:57:44 +0000 (UTC) (envelope-from meowthink@gmail.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 33F208F7FA for ; Thu, 4 Oct 2018 10:57:44 +0000 (UTC) (envelope-from meowthink@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id ED3EC10C85AE; Thu, 4 Oct 2018 10:57:43 +0000 (UTC) Delivered-To: stable@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 CB76010C85AD for ; Thu, 4 Oct 2018 10:57:43 +0000 (UTC) (envelope-from meowthink@gmail.com) Received: from mail-ot1-x32f.google.com (mail-ot1-x32f.google.com [IPv6:2607:f8b0:4864:20::32f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 5E0B48F7F7 for ; Thu, 4 Oct 2018 10:57:43 +0000 (UTC) (envelope-from meowthink@gmail.com) Received: by mail-ot1-x32f.google.com with SMTP id c18-v6so8721983otm.3 for ; Thu, 04 Oct 2018 03:57:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=78co82TNNh+fpuuZLLttqnuE9hU6Pr/4AcXwlbZPNDY=; b=gIbuUiewIUC01C3fmBgPFQaA9JMqEEEEOaEQUlUyHW5WAJXwLFY+gVBkb4w+tOyMKb 6n4R9+4SDRvkzucgJ1CG/kaGTaMxcfJi9/m6/hbB/HDvd4gSgaiEYU97hgGTSbltf+tN 8GkcuS6lhUsAJbZV50623aMhhS9CghhtcKGEbe+PMngLJ5K8i7jjcwlNMcOdZR3oXnrc VNawbKZgDnfUMVn46fypCjpKWiZLlkPVRL8VaTCeuWwAXqfl30XZ2qyVvP95uKBoXews JZmzioEkiOIudDYnp/MFN86GLdRwsnQPciIilQJMsrhfG+YB6CnKtoPVuj9WqH1nf25l ui5g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=78co82TNNh+fpuuZLLttqnuE9hU6Pr/4AcXwlbZPNDY=; b=jy5JaAMgZvL4T/nDuncRZWGeks+lnPA0/BBZ3WlFdUh3hzv4IUfowJuczB6PnA16mB dkPHerEYyci8VzthejUDt78lXNiPiOo9nYzKohb8uqajjsSQp8YItJGc4Y5oVZ6+2UJK lP12LXOzJ63zrcNO6g9mFjZcHJkwdhA0EsqPU624bOd/RwFoQ8n2O6T6RKwUCH08ji+x zkfhYLh6Pw9B5fjgTR9y4dQv2wjHx6XS6/d8B5OZThehJma1sU5IzqxeUgzGEJVnGyjo mbkr+fNkRVfh0JbzrwE+R+aTPev8PwOH7PH6q6LV4S96PxPajSITvDvqfjtkz4aKw2Y/ mtng== X-Gm-Message-State: ABuFfohEdwcSL8mHsJ/11KUmZfynmRHnBU+CjIDu2C2iPx+CSc+n8AzX Wp6L8Y3kZxiwFWbN49xa4Kmen1pSi/eK95nc0u6jw/zZXbU= X-Google-Smtp-Source: ACcGV6082O6ysatXmmTdmeO9+0WxHTwfaoQikkCPcPG9Y2WqwgIrGD1SCSdP3JrW/M1R0m5C+oTRi3kmfFcjUBuARYI= X-Received: by 2002:a9d:43a3:: with SMTP id t35mr3597208ote.40.1538650662765; Thu, 04 Oct 2018 03:57:42 -0700 (PDT) MIME-Version: 1.0 References: <7b8edb650b9d50a03e60335ebc13ada8@ultra-secure.de> <6B1BFE46-1ABF-436C-9E85-74DDFCD2BB24@alogis.com> In-Reply-To: From: Meowthink Date: Thu, 4 Oct 2018 18:57:30 +0800 Message-ID: Subject: Re: 11.2-RELEASE panics with a bit of load To: rainer@ultra-secure.de Cc: stable@freebsd.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Oct 2018 10:57:44 -0000 Hi Rainer, I do noticed that the default vfs.zfs.arc_max seems too aggressive, as it will cause tings like rsync swapping in and out, esp. on configs having 32GB RAM, and smaller. So if a reduced arc_max works, I'd suggest you check your swap device. Some SSDs are known to have issues under huge IO workload, like high latency thus abort host commands and force the system reties on read. Regards, meowthink On Thu, Oct 4, 2018 at 3:06 PM wrote: > > Am 2018-10-04 05:53, schrieb Holger Kipp: > > Dear Rainer, > > > > if no one else is experiencing these errors, then it is probably a > > hardware error. > > I had once encountered problems with incompatible memory (combination > > of memory (ok with other boards) and board (ok with other memory) did > > not work properly). The issue could be triggered with a simple > > buildworld within minutes. However memtest86 could run for hours > > without finding a thing. > > Please don=E2=80=98t rely on memtest86 if it does not report any proble= ms. > > > > To be sure: check / adjust memory timings, remove and/or replace > > memory modules and try to trigger the error again. > > > > Best regards, > > Holger Kipp > > > > I have this problem on two machines, actually. > It would be highly unlikely for both to have hardware problems. > Though possible, of course. > > Reducing ARC seems to help, though, and I assume that is the problem the > machine ran into because I still have 29GB out of 32GB wired now, with > an ARC limited to 60% of kmem_size. > > > _______________________________________________ > freebsd-stable@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"