Re: Panic after kldload i915kms at main-n280058-e7a04a110724

Reply: David Wolfskill : "Re: Panic after kldload i915kms at main-n280058-e7a04a110724"
In reply to: David Wolfskill : "Panic after kldload i915kms at main-n280058-e7a04a110724"
Go to: [ bottom of page ] [ top of archives ] [ this month ]

From: Juraj Lutter <otis_at_FreeBSD.org>
Date: Thu, 04 Sep 2025 12:39:45 UTC


> On 4 Sep 2025, at 14:20, David Wolfskill <david@catwhisker.org> wrote:
> 
> Yesterday's (source-based) update was to main-n280031-11f1dd193af5,
> and I saw no issues.  Today's was to main-n280058-e7a04a110724.
> 
> My (headless) build machine (which does not attempt to either build
> or load the module), and uses the GENERIC kernel, had no issues.
> 
> I note that the machines that load the modules also build them
> whenever the kernel is built.  All machines mentioned here are
> amd64.
> 
> The ports tree is at main-n717402-cd0318d52939.  (Yesterday, it was at
> main-n717309-326381de144d.)  Installed ports are updated daily.

Out of curiosity, does the problem go away when you revert commit a2f08d0ddc29e4da15f614bdb6a5072b3fd6332c ?

It is the most recent one that touched pseudofs subsystem.


—
Juraj Lutter
otis@FreeBSD.org