From nobody Sun Nov 13 23:37:56 2022 X-Original-To: hackers@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4N9TQK1lGgz4hSWr for ; Sun, 13 Nov 2022 23:38:01 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: from mail-il1-x129.google.com (mail-il1-x129.google.com [IPv6:2607:f8b0:4864:20::129]) (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 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4N9TQJ6kvLz3kP1 for ; Sun, 13 Nov 2022 23:38:00 +0000 (UTC) (envelope-from markjdb@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-il1-x129.google.com with SMTP id o13so4998218ilc.7 for ; Sun, 13 Nov 2022 15:38:00 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=in-reply-to:content-transfer-encoding:content-disposition :mime-version:references:message-id:subject:cc:to:from:date:sender :from:to:cc:subject:date:message-id:reply-to; bh=rQVM+tC/j0+dqCMxz39isNw4X4TXWAhDMdrfAbFXLLE=; b=AkJ+qwqxgZ0HfvK8pauEWeOw+mVVIkYNMwBSy7RR9n7rXatYLJB86wNf8l+7PVnaDM fsSTh5qYJGdMm0w+Db+D2zeeKgaihs8EV4d1JkJ9U6j/hYZEzSh6D7oDRdsui/qD46Wo jFnVhqDcsSW5nHeEkMydtm92ciBkUq0kNG0xrOTmqLaKxgXM2+Yscq/tw8ozjb0KBvxy rmHSEP/qJKaM5XJ+2g59PDzlPbBh8hjXb9dgskZ6q+DkXehuAXc5KVnhHXUDuPRN3dom v4AVToDHO2aTQFM3VBa4Fr5MEAVTEvS/RQ/vAEbKOjjPnHlGbWaADaQiGNxDFgoKABZS g5nA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=in-reply-to:content-transfer-encoding:content-disposition :mime-version:references:message-id:subject:cc:to:from:date:sender :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=rQVM+tC/j0+dqCMxz39isNw4X4TXWAhDMdrfAbFXLLE=; b=biDIIJI9UCElEiA3BS7/pha64D24BQUk1DgVLNTDLS28m5ZgZ/OHNxMUHJPhA68OVn ujhs6/V9eJUDmmytTTHkfduakbTW2orVLokzt7Y7N7hAGZt00Xk2Mzk2DdRGI94Jwcye 0Vu48zKhNpgksWqKBkTbN007JCDUk6Ko3KtAZ1tYauUosDQ5VFRb5a5hmWjkFk6g55WB EOKvzNSTa3NFuR7kl5j5JjJvxU8jp3nMyqEzQt6gEpln3fp3+O9DKqJblciAxWo8A7jw ybaEHAoyxjYbewJ5NTWLVHGhd2EIeQhPVz9qB24zgHVLqeLslEVGGurxgxAEKUVx6w6E ec0A== X-Gm-Message-State: ANoB5pnrYZu1GUha08gGr83WpmPj1/gQF3VQzL2OLRcCkAu/uwJmbok6 MkxDOmpCFDuB8goSc07q55Y= X-Google-Smtp-Source: AA0mqf6Y+M5BHVgl7e3I1c9YFpieCvCUD9bd2NvRVSmMVxXE5WgVrxLVizpOXLsqmLP6AHM3pMhOMQ== X-Received: by 2002:a92:de4e:0:b0:300:9b70:1954 with SMTP id e14-20020a92de4e000000b003009b701954mr5096042ilr.52.1668382679408; Sun, 13 Nov 2022 15:37:59 -0800 (PST) Received: from nuc (192-0-220-237.cpe.teksavvy.com. [192.0.220.237]) by smtp.gmail.com with ESMTPSA id c3-20020a92d3c3000000b003024b62725dsm2034784ilh.22.2022.11.13.15.37.58 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sun, 13 Nov 2022 15:37:58 -0800 (PST) Date: Sun, 13 Nov 2022 18:37:56 -0500 From: Mark Johnston To: Christopher Bowman Cc: hackers@freebsd.org Subject: Re: I could use some help Message-ID: References: <5C07A058-977C-4F2E-8B41-01EBAB4FF24B@chrisbowman.com> List-Id: Technical discussions relating to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-hackers List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-hackers@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <5C07A058-977C-4F2E-8B41-01EBAB4FF24B@chrisbowman.com> X-Rspamd-Queue-Id: 4N9TQJ6kvLz3kP1 X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N On Sun, Nov 13, 2022 at 02:48:02PM -0800, Christopher Bowman wrote: > > > > On Nov 13, 2022, at 11:20 AM, Mark Johnston wrote: > > It's indeed a bit hard to see why commit > > ce9c3848ff369467749f59fd24f8b9f1241e725c might cause an sdhci command > > timeout. I suspect the commit itself is innocent, but happens to > > uncover a problem elsewhere by changing the order in which page > > allocations are distributed to different consumers. At the time of the > > command timeouts, the kernel is still running on a single CPU so the > > order in which pages are allocated should be fairly deterministic and > > thus consistent across multiple boots. > > > > One thing you can try is to take a releng/13.1 tree and revert just > > ce9c3848ff369467749f59fd24f8b9f1241e725c, and/or take releng/13.0 and > > apply just that commit. It would be useful to know whether either of > > the resulting kernels can boot successfully. > > > > Could you also please post your kernel configuration (ARTYZ7) somewhere, > > together with a dmesg of a successful boot? > > Mark, > If I checkout release/13.1.0 and revert the commit in question then my kernel boots. I wasn’t able to checkout releng/13.1 as I get the following: > > crb@eclipse:142> git checkout releng/13.1 > M sys/vm/uma_core.c > Already on 'releng/13.1' > Your branch is up to date with 'origin/releng/13.1’. > > I think that’s just me being incompetent with git. It's because sys/vm/uma_core.c is modified in your local copy, and to check out releng/13.1 needs to modify uma_core.c. You can remove that local modification with "git checkout -f sys/vm/uma_core.c && git checkout releng/13.1", or just "git checkout -f releng/13.1", though the latter will discard any other uncommitted modifications you might have in your tree. I'm not sure what release/13.1.0 is though, that branch doesn't appear to exist in the official git repo. If it points to the same commit as releng/13.1, then ok. > I can add the commit to release/13.1.0 if you would still like > > My kernel is essentially identical to the in-tree ZEDBOARD config > with the name changed. I can post it if truly desired. > > Please find the dmesg output for 13.1 release below. > Thanks > Christopher Ok, nothing really stands out to me. It looks like mmcsd_attach() is running, but before it can discover any partitions it issues a command that times out, so we'll have to dig in a bit more. Could you please try booting a problematic kernel with the hw.mmc.debug and hw.sdhci.debug tunables set to "3", and share the resulting output up until the hang? It might be pretty verbose. Separately, I wonder if you could try booting a problematic kernel with the kern.maxphys tunable set to 131072. Does it change anything?