From owner-freebsd-stable@freebsd.org Wed Jun 3 16:11:58 2020 Return-Path: Delivered-To: freebsd-stable@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id D8F1033AB57 for ; Wed, 3 Jun 2020 16:11:58 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 49cYnp5V7yz3Tfd for ; Wed, 3 Jun 2020 16:11:58 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: from mail-qk1-f175.google.com (mail-qk1-f175.google.com [209.85.222.175]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) (Authenticated sender: kevans) by smtp.freebsd.org (Postfix) with ESMTPSA id B235427007 for ; Wed, 3 Jun 2020 16:11:58 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: by mail-qk1-f175.google.com with SMTP id c185so2689544qke.7 for ; Wed, 03 Jun 2020 09:11:58 -0700 (PDT) X-Gm-Message-State: AOAM533sO0ryvk6goJHT5c6JFdKZP656qpgBrxCce4bLyo6n/Uiw6wT5 pC5ekJDMdgKpzdABsK74yX7pCHDY1fmPeCiL+Ng= X-Google-Smtp-Source: ABdhPJyXCN4PTicM+nitEESQtT36w89uY1ZM4XW7vhb7UAKdWUv2naGtpUL2OarFunft4ikUeZyRYLDJgLD0Pj0JJEw= X-Received: by 2002:a37:5b47:: with SMTP id p68mr425267qkb.120.1591200718282; Wed, 03 Jun 2020 09:11:58 -0700 (PDT) MIME-Version: 1.0 References: <9c5739d4-c10c-74a0-0f69-6b4cdc3e0dd7@studiokaraoke.co.id> <9497bb24-39e3-0c2f-4218-aaa7643b1e7f@studiokaraoke.co.id> In-Reply-To: <9497bb24-39e3-0c2f-4218-aaa7643b1e7f@studiokaraoke.co.id> From: Kyle Evans Date: Wed, 3 Jun 2020 11:11:45 -0500 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: LUA ERROR: memory allocation error: block too big To: Budi Janto Cc: FreeBSD-STABLE Mailing List Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Jun 2020 16:11:58 -0000 On Wed, Jun 3, 2020 at 11:06 AM Budi Janto wrote: > > > > On 6/3/20 6:50 PM, Kyle Evans wrote: > > Can you post a sample of your /boot/lodaer.conf, please? Though, the > > efipart_readwrite error smack dab in the middle leaves me a bit > > worried; status=7 looks like EFI_DEVICE_ERROR, which is a bit > > sinister. > > # cat /boot/loader.conf > autoboot_delay="5" # Delay in seconds before autobooting. > vfs.zfs.arc_max="5G" # Limit ZFS memory usage. > coretemp_load="YES" # Intel CPU temperature. > Thanks for confirming - this is relatively harmless, and the problem is indeed later. > > > Believe it or not, issues with underlying media can cause problems > > with 4thloader as well. > > Could be, I' will replace as soon as possible SSD for system (My > prediction SSD too old). I'am sorry, this's remote machine, so I can not > give you more information (I can not access that machine anymore). > Remote worker just send me two photo. > > First booting: https://ibb.co/NWbszqR > After restart: https://ibb.co/dDsH0RD > *nod* This isn't my domain, but I think the CAM errors after restart tend to support the theory of aging/dying SSD or perhaps bad cable at a minimum. Thanks, Kyle Evans