From owner-freebsd-stable@freebsd.org Tue Oct 23 14:54:37 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 15C75FE59E2 for ; Tue, 23 Oct 2018 14:54:37 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-vk1-xa30.google.com (mail-vk1-xa30.google.com [IPv6:2607:f8b0:4864:20::a30]) (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 8FF1C8074D for ; Tue, 23 Oct 2018 14:54:36 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-vk1-xa30.google.com with SMTP id d141so407258vke.3 for ; Tue, 23 Oct 2018 07:54:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=vvQxqfuWBQciKwhpIarGU400W90ZCuhktLB/QJwN7Bo=; b=XWwAXSVSJyIsk6tvdcJQYMvSdEQbEQz7xtgbTY6N1UnlSexZcmk438mp/P22nIU4Sz 9P/qX3XVLQaWaYZFsI3thQRrQDIzpfNbSNKjGMfmj2MSNI6vcFeutarvsCfC9rAtw+VN iMmI59JhDF/cdFeXVDdHFYbp20BB61JVkT8RaLWmZxDUwXI18VqwQS3y7LxM1eE68/Wv /Ct89RXUcO6fritj0DMwmxBrg5jz8kgkqCwC3odNVfGlZQgOieGtRUJqsh/aLKriCHY/ haSf5yeVWTasm/2a05VM31OTglq7XRKHS9hmjV5lvBFYBpxdXwr0Wty1NsDDxqF//e8A 9mug== 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; bh=vvQxqfuWBQciKwhpIarGU400W90ZCuhktLB/QJwN7Bo=; b=aHRebYYMtbkX3VzJOFLR5XY8y1B6y+pjNElY/9Y0WlusAmoNeI3YsR9RP5gl9utsae GgYpdUtlPp8yJ8WPlADUk16GU2/hFX8APu/nrnyedCWbeA9nnOezqZdgJ7394lnerzCk jChtHTvsbiIv3137dY5j7H4ZcPt7zQhsHxTmI5TvxkUi1E82f6Oz7EC3BH9ZOhAOG4n5 md7KYdthN2ej92bp3UzQga7knK0C3nQ7Lym0qh8RmjrU6gz0rrGIli1QMz6cMvnyZFQo gsHcmdb76ij+vmouQv60JTZwSQVo5bI0XTxTx0ttCOznmbmSquZRE+/9zXcP7D48Wqsi pAeg== X-Gm-Message-State: ABuFfojR2jQGplluf3+nD4f5pC3cUWdW5HcU1o3b6QwL58TPw3yw8fb/ 10GuWSlJAV/mRvCEI8Ve0yxreRrNreLJYJRj5nm79w== X-Google-Smtp-Source: ACcGV62WIfXVRIeoF3Ehkz2Q79a25KWE+L4hiGGvb5ChnhpXW7XtiikUoi7X7tzmC2YoIHsj4OlrThwPOLSZ3/FDu70= X-Received: by 2002:a1f:2d07:: with SMTP id t7mr12662343vkt.45.1540306475850; Tue, 23 Oct 2018 07:54:35 -0700 (PDT) MIME-Version: 1.0 References: <79973E2B-F5C4-4E7C-B92B-1C8D4441C7D1@yahoo.com> <3CA4C94F-A062-44FE-B507-948A6F88C83D@me.com> <18e270f6-c811-3f5e-bf65-76c895782c8f@FreeBSD.org> <7B44DEC3-9E79-46E0-BC02-E6C95680BF77@me.com> In-Reply-To: <7B44DEC3-9E79-46E0-BC02-E6C95680BF77@me.com> From: Warner Losh Date: Tue, 23 Oct 2018 08:54:24 -0600 Message-ID: Subject: Re: loader lsdev crashes loader (Was: head -r338804 boots threadripper 1950X fine; head -r338810+ do not; -r338807 seems implicated) To: Toomas Soome Cc: Lev Serebryakov , Mark Millard , Konstantin Belousov , FreeBSD Current , FreeBSD-STABLE Mailing List Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Oct 2018 14:54:37 -0000 On Tue, Oct 23, 2018 at 5:54 AM Toomas Soome wrote: > > > On 23 Oct 2018, at 13:53, Lev Serebryakov wrote: > > > > On 22.10.2018 12:27, Toomas Soome wrote: > > > >> It would help to get output from loader lsdev -v command. > > current loader crashes on "lsdev" for me: > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D232483 (it is not > > threadripper-related, my hardware is Intel Atom). > > > > -- > > // Lev Serebryakov > > > > That error means something is corrupting the memory, it is hard to guess > what exactly and debugging it is nasty - it means we would need to track > down what was allocated before this memory block (guard1 is marker insert= ed > in front of the allocated memory block). > > Fortunately the code to print the partition table is in > stand/common/disk.c and the partition code is just next to it and so it > should be relatively easy to find the guilty one=E2=80=A6 I will try to s= ee if I > can replicate the issue. > We've had reports of other systems mysteriously hanging on boot with the new boot loader, but not older ones. It isn't limited to new AMD boxes, but it's been seen on other Intel boxes of various flavors. When we crash, it seems like we don't have a good recovery like we do with BTX. Maybe they are related? Warner