Received-SPF: pass (google.com: domain of linux-kernel+bounces-127053-linux.lists.archive=gmail.com@vger.kernel.org designates 139.178.88.99 as permitted sender) client-ip=139.178.88.99;
Precedence: bulk
MIME-Version: 1.0
References: <CALaQ_hrVM0dMaFqLshW5NTkkomGSvGnpyLOPx8E0QpniewyxUA@mail.gmail.com>
 <20240329194603.ed67a334f75ba3c933cc8876@linux-foundation.org>
In-Reply-To: <20240329194603.ed67a334f75ba3c933cc8876@linux-foundation.org>
From: Nathan Royce <nroycea+kernel@gmail.com>
Date: Mon, 1 Apr 2024 15:46:52 -0500
Message-ID: <CALaQ_hqHwBKFBFPyantgr59SDpfZHwJFyWimLAZROdDsvA6rwQ@mail.gmail.com>
Subject: Re: Allmodconfig - logic_outb - Boot Panic
To: Andrew Morton <akpm@linux-foundation.org>
Cc: LKML <linux-kernel@vger.kernel.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Yup. I just figured linux would gracefully handle these sorts of
issues (eg. notify the caller, for them to handle, or just do
nothing).
"ISAPNP" was one of the small handful of things I had to disable from
"allmodconfig" before I could get it to boot.
The latest (and last) was "DEBUG_TEST_DRIVER_REMOVE". I had to add
"dump_stack()" in "__kernfs_remove"" in "fs/kernfs/dir.c" because I
couldn't understand why I was getting other hardware panics for
hardware that DID exist.
So while I wanted "everything under the sun", which "allmodconfig"
delivered, it also delivered things that simply made booting
impossible.
One other requirement for "allmodconfig" is making sure the FS that
root exists on is enabled ('Y', not 'M') for it (common-sense mention
for anyone searching for "allmodconfig" issues).

On Fri, Mar 29, 2024 at 9:46=E2=80=AFPM Andrew Morton <akpm@linux-foundatio=
n.org> wrote:
> Could be that the logic_pio driver is crashing when the hardware isn't th=
ere.