From owner-freebsd-current@freebsd.org Tue Feb 9 14:41:15 2021 Return-Path: Delivered-To: freebsd-current@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 709A9540A5D for ; Tue, 9 Feb 2021 14:41:15 +0000 (UTC) (envelope-from asomers@gmail.com) Received: from mailman.nyi.freebsd.org (mailman.nyi.freebsd.org [IPv6:2610:1c1:1:606c::50:13]) by mx1.freebsd.org (Postfix) with ESMTP id 4DZlvH1TdPz55ll for ; Tue, 9 Feb 2021 14:41:15 +0000 (UTC) (envelope-from asomers@gmail.com) Received: by mailman.nyi.freebsd.org (Postfix) id 32C7B540A5C; Tue, 9 Feb 2021 14:41:15 +0000 (UTC) Delivered-To: current@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 328E9540CF9 for ; Tue, 9 Feb 2021 14:41:15 +0000 (UTC) (envelope-from asomers@gmail.com) Received: from mail-oi1-f172.google.com (mail-oi1-f172.google.com [209.85.167.172]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4DZlvH0npSz55ZG for ; Tue, 9 Feb 2021 14:41:14 +0000 (UTC) (envelope-from asomers@gmail.com) Received: by mail-oi1-f172.google.com with SMTP id k204so18068380oih.3 for ; Tue, 09 Feb 2021 06:41:14 -0800 (PST) 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=UFj2JYgz/k1+CEbvs9XSp21pXR0qBk3jwwvs5Q0LypI=; b=j73iwq2qEIn1Qj1nCyoYj3dprF7BygutAJqFaZfu7rqgCdGH45eT+bzrjluaTfg8oF osjlfmIMnqXHlWwGyoMGr19xyCCMmpykQjX3pwTRi8XyC7erBoL/TY2TeP1XkSpLIVBM tzew+xiYtqUkAg9pzR6tA9/OXKh0PIrIQKICnPPWd/DXgMgA8hY82gw2u+TZk7NqUPXj 7sWHnC1JnQuOnHDCcpiLbjdZTN+x6Lrfv1fL4YvugYZQnSHCmm2yZl+9uQSblFjjPVrM RMniOlNzdrRpZbfZmEULHO/LRdeqZtkg8Z4Bd/MLib6pd2DFDqmLxdfdnYExhzQlS5cW q41g== X-Gm-Message-State: AOAM533yDvVvQO+3SPvladDO8qQqdyssiF2XWsMogSICPAM+ft/7Ige9 kAY/hfCYn+ZggUpmQjZkX7/XbC2UYuyHKID5oRh3ZbFtN7E= X-Google-Smtp-Source: ABdhPJzA4tWIohG0V3Wex4UHjGChRs8NvdsnvIqTQ6ZgjXpovag1EPITyBPYgcRxkzRDYZndx2TcncMVJVf3Wa0PAcY= X-Received: by 2002:aca:dd08:: with SMTP id u8mr2716733oig.55.1612881674229; Tue, 09 Feb 2021 06:41:14 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Alan Somers Date: Tue, 9 Feb 2021 07:41:03 -0700 Message-ID: Subject: Re: Current - kernel dump while plasma loading. To: Santiago Martinez Cc: FreeBSD Current X-Rspamd-Queue-Id: 4DZlvH0npSz55ZG X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.34 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 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: Tue, 09 Feb 2021 14:41:15 -0000 On Tue, Feb 9, 2021 at 3:52 AM Santiago Martinez wrote: > Hi there, this morning i did the usual git pull and make.. > > After reboot and loading the desktop (while starting plasma with drm), i > get a kernel dump. > > This was ok until this morning... > > This is the info: > > root@tucho:/var/crash # cat info.last > Dump header from device: /dev/ada0p2 > Architecture: amd64 > Architecture Version: 2 > Dump Length: 1381969920 > Blocksize: 512 > Compression: none > Dumptime: 2021-02-09 10:24:21 +0000 > Hostname: tucho > Magic: FreeBSD Kernel Dump > Version String: FreeBSD 14.0-CURRENT #5 main-n244705-504ebd612ec6: Tue > Feb 9 10:20:32 GMT 2021 > root@tucho:/usr/obj/usr/src/amd64.amd64/sys/TUCHO > Panic String: VERIFY(avl_find(tree, new_node, &where) == NULL) failed > > Dump Parity: 2603051126 > Bounds: 6 > Dump Status: good > > > Best regards. > > Santi > I can tell you why it was "fine" until this morning. It's because ZFS assertions weren't actually enabled until last night. So this isn't a newly introduced ZFS bug, just a newly noticed one. Could you please post the full stack trace? -Alan