Re: PR 252541: Early kernel panic on RPi4B (Too many early devmatch mappings)

Gordon Bergling <[email protected]>
Newsgroups gmane.os.freebsd.devel.arm
Message-ID <X/1f/sj5LuKh//[email protected]>
On Tue, Jan 12, 2021 at 12:16:30AM -0800, Mark Millard via freebsd-arm wrote:
> On 2021-Jan-11, at 23:13, Klaus Küchemann <maciphone2 at googlemail.com> wrote:
> >> Am 12.01.2021 um 07:42 schrieb Mark Millard via freebsd-arm <[email protected]>:
> >> 
> >> Also, my context was a amd64->aarch64 cross-build
> >> instead of being an aarch64 native build.…….src.conf like file, make.conf …...
> > 
> > I have compiled directly on the RPI with nonexistent src.conf/make.conf & standard kernconfs,
> > no problems .
> 
> Good to know what you used for such files and the build machine.
> 
> We do not have builds of the same source version yet. I will not
> get to it tonight, but I will hopefully later try to build the
> version that you identified and see what I get for different
> variations in how to build that source version to produce debug
> kernel builds. (I might include the two printf's that report
> the figures that the KASSERT is based on.)
> 
> ===
> Mark Millard
> marklmi at yahoo.com
> ( dsl-only.net went
> away in early 2018-Mar)

Hi Mark,

thanks for your work on that issue. I have some spare time today and will try some combinations
about NO INVARIANTS and so on. My src.conf is the following,

---------------------------
WITH_MALLOC_PRODUCTION=1
WITH_EXTRA_TCP_STACKS=1
WITH_BEARSSL=1
WITH_PIE=1
WITH_RETPOLINE=1
WITHOUT_CLEAN=1
---------------------------

I know that the change itselfs doesn't seems to be significant, but it was the
first that has triggered the panic. Maybe it is also the u-boot.bin, I haven't
updated them since the July.

I'll keep you posted.

--Gordon
_______________________________________________
[email protected] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-arm
To unsubscribe, send any mail to "[email protected]"
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.