https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246638
Mark Johnston changed:
What|Removed |Added
Status|New |In Progress
Assignee|b..
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246638
--- Comment #12 from Mark Johnston ---
(In reply to Conrad Meyer from comment #11)
Ah, it'll be the code which registers vm_phys segments for preloaded data and
the kernel page tables. It hard-codes domain 0. Maybe we can defer the
regist
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246638
Mark Linimon changed:
What|Removed |Added
Keywords||panic, regression
--
You are recei
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246638
--- Comment #11 from Conrad Meyer ---
Hm, so this must be us synthesizing a bogus 0-domain:
SRAT: Found memory domain 1 addr 0x0 len 0xa: enabled
SRAT: Found memory domain 1 addr 0x10 len 0xbff0: enabled
SRAT: Found memory doma
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246638
--- Comment #10 from Rafael Kitover ---
I set this variable at the loader prompt, and my full dmesg.boot for
12.1-STABLE is attached.
--
You are receiving this mail because:
You are the assignee for the bug.
__
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246638
--- Comment #9 from Rafael Kitover ---
Created attachment 214737
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=214737&action=edit
12.1-STABLE /var/run/dmesg.boot
--
You are receiving this mail because:
You are the assignee for
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246638
--- Comment #8 from Conrad Meyer ---
(In reply to Rafael Kitover from comment #7)
Probably the 34MB is wrongly carved from some other domain to not have an
unpopulated domain 0. Is it possible the DIMMS are installed in an order not
recomm
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246638
--- Comment #7 from Rafael Kitover ---
Just a guess, but could the 34MB be the video memory of the crappy video chip
on my server motherboard? Or something like that anyway.
Here is a photo of the panic by the way:
https://photos.app.goo.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246638
--- Comment #6 from Conrad Meyer ---
So yep, we have 5 domains but only 4 DIMMS.
Domain 2 has exactly 32GB, domain 4 ditto. Domain 7's got ~28GB, and domain 1
has ~32 GB.
Domain 0 has only ~34 MB. That one seems problematic.
--
You ar
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246638
--- Comment #5 from Rafael Kitover ---
Here you go:
vm.phys_segs:
SEGMENT 0:
start: 0x1
end: 0x9f000
domain:1
free list: 0x81f0a170
SEGMENT 1:
start: 0x10
end: 0x20
domain:1
free list: 0x
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246638
--- Comment #4 from Conrad Meyer ---
(In reply to Mark Johnston from comment #3)
Might be the e820 or EFI metadata is somewhat erroneous? Just speculating at
this point. phys_segs should help.
@Rafael, bootverbose mode should print out t
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246638
--- Comment #3 from Mark Johnston ---
(In reply to Conrad Meyer from comment #1)
Hmm. In the one place where this function is used, we are allocating memory to
back the vm page array. The selected domain is that of the corresponding page
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246638
--- Comment #2 from Rafael Kitover ---
Just tried booting a 12.1-STABLE stick, and that booted fine!
--
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@fr
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246638
Conrad Meyer changed:
What|Removed |Added
CC||c...@freebsd.org,
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246638
Bug ID: 246638
Summary: panic on boot: "cannot find a large enough size"
Product: Base System
Version: CURRENT
Hardware: amd64
OS: Any
Status: New
S
15 matches
Mail list logo
