From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 26241C433F5 for ; Wed, 20 Oct 2021 01:10:15 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id EC142610FC for ; Wed, 20 Oct 2021 01:10:14 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229910AbhJTBM1 (ORCPT ); Tue, 19 Oct 2021 21:12:27 -0400 Received: from eu-shark1.inbox.eu ([195.216.236.81]:43230 "EHLO eu-shark1.inbox.eu" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229741AbhJTBM0 (ORCPT ); Tue, 19 Oct 2021 21:12:26 -0400 Received: from eu-shark1.inbox.eu (localhost [127.0.0.1]) by eu-shark1-out.inbox.eu (Postfix) with ESMTP id 122BD6C007F0; Wed, 20 Oct 2021 04:10:12 +0300 (EEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=inbox.eu; s=20140211; t=1634692212; bh=tDh42Yu82z1BtKImxfA0ZJprj6XGNUNgtvu/86I/Ht4=; h=References:From:To:Cc:Subject:Date:In-reply-to; b=GX0WJlA54aqFfKTC1pvznsoDli3bOsZIuePzNlVikuGR6CqWeWooj/utbRRQLvk0D p3M8Y1AQIn2mmSTz0azCm1V/lCIkkXvTRua9hE/dEnR3QLLbDmERTs8YmBVMyI4vMu 4Zmp1RqEaBZCPs8dPTx8OTWBgCDoMDpgzRi60F5M= Received: from localhost (localhost [127.0.0.1]) by eu-shark1-in.inbox.eu (Postfix) with ESMTP id 00BE06C007EA; Wed, 20 Oct 2021 04:10:12 +0300 (EEST) Received: from eu-shark1.inbox.eu ([127.0.0.1]) by localhost (eu-shark1.inbox.eu [127.0.0.1]) (spamfilter, port 35) with ESMTP id j9_o5FQVtuqj; Wed, 20 Oct 2021 04:10:11 +0300 (EEST) Received: from mail.inbox.eu (eu-pop1 [127.0.0.1]) by eu-shark1-in.inbox.eu (Postfix) with ESMTP id C58F36C007DC; Wed, 20 Oct 2021 04:10:11 +0300 (EEST) Received: from nas (unknown [121.237.227.114]) (Authenticated sender: l@damenly.su) by mail.inbox.eu (Postfix) with ESMTPA id CE1471BE01C4; Wed, 20 Oct 2021 04:10:09 +0300 (EEST) References: <9b153cca-2d9a-e217-a83f-1a8e663fc587@suse.com> <7de9iylb.fsf@damenly.su> User-agent: mu4e 1.7.0; emacs 27.2 From: Su Yue To: Chris Murphy Cc: Qu Wenruo , Nikolay Borisov , Qu Wenruo , Btrfs BTRFS Subject: Re: 5.14.9 aarch64 OOPS Workqueue: btrfs-delalloc btrfs_work_helper Date: Wed, 20 Oct 2021 07:42:00 +0800 In-reply-to: Message-ID: <35owijrm.fsf@damenly.su> MIME-Version: 1.0 Content-Type: text/plain; format=flowed X-Virus-Scanned: OK X-ESPOL: +dBm1NUOBkfEh1+jQmXcBgEprShOQuzk//vYoxBcgBmOPC+CfkkPWBO2mWpqPg+1zUEX Precedence: bulk List-ID: X-Mailing-List: linux-btrfs@vger.kernel.org On Tue 19 Oct 2021 at 14:26, Chris Murphy wrote: > Still working on the kernel core dump and should have something > soon > (I blew up the VM and had to start over); should I run the > 'crash' > command on it afterward? Or upload the dump file to e.g. google > drive? > Dump file and vmlinu[zx] kernel file are needed. > Also, I came across this ext4 issue happening on aarch64 > (openstack > too), but I have no idea if it's related. And if so, whether it > means > there's a common problem outside of btrfs? > https://github.com/coreos/fedora-coreos-tracker/issues/965 > Already noticed the thing. Let's wait for the vmcore. Any idea, Qu? -- Su > I mentioned this bug report up thread: > https://bugzilla.redhat.com/show_bug.cgi?id=1949334 > but to summarize: it has the same btrfs call trace we've been > looking > at in this email thread, but it's NOT on openstack, but actual > hardware (amberwing).