Groups
Groups
Conversations
All groups and messages
Send feedback to Google
Help
Training
Sign in
Groups
Groups
ml-freebsd-questions
Conversations
About
panic: pmap_growkernel: no memory to grow kernel
0 views
Skip to first unread message
Andrea Venturoli
unread,
Jun 4, 2025, 2:32:33 AM
Jun 4
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to freebsd-...@freebsd.org
Hello.
This night a 14.2-RELEASE-p3/amd64 server of mine rebooted itself.
Unfortunately I got no core, but I have the following in the logs:
> Jun 4 03:06:19 xxxxxx kernel: panic: pmap_growkernel: no memory to grow kernel
> Jun 4 03:06:19 xxxxxx kernel: cpuid = 4
> Jun 4 03:06:19 xxxxxx kernel: time = 1748999063
> Jun 4 03:06:19 xxxxxx kernel: KDB: stack backtrace:
> Jun 4 03:06:19 xxxxxx kernel: #0 0xffffffff8063243d at kdb_backtrace+0x5d
> Jun 4 03:06:19 xxxxxx kernel: #1 0xffffffff805e8ad1 at vpanic+0x131
> Jun 4 03:06:19 xxxxxx kernel: #2 0xffffffff805e8993 at panic+0x43
> Jun 4 03:06:19 xxxxxx kernel: #3 0xffffffff808f7803 at pmap_growkernel+0x2a3
> Jun 4 03:06:19 xxxxxx kernel: #4 0xffffffff8086e8e4 at vm_map_insert1+0x254
> Jun 4 03:06:19 xxxxxx kernel: #5 0xffffffff8087024c at vm_map_find_locked+0x50c
> Jun 4 03:06:19 xxxxxx kernel: #6 0xffffffff8086fc2f at vm_map_find+0xaf
> Jun 4 03:06:19 xxxxxx kernel: #7 0xffffffff8086cd66 at kva_import+0x36
> Jun 4 03:06:19 xxxxxx kernel: #8 0xffffffff8064fa7e at vmem_try_fetch+0xce
> Jun 4 03:06:19 xxxxxx kernel: #9 0xffffffff8064f3e8 at vmem_xalloc+0x578
> Jun 4 03:06:19 xxxxxx kernel: #10 0xffffffff8086cdb5 at kva_import_domain+0x25
> Jun 4 03:06:19 xxxxxx kernel: #11 0xffffffff8064fa7e at vmem_try_fetch+0xce
> Jun 4 03:06:19 xxxxxx kernel: #12 0xffffffff8064f3e8 at vmem_xalloc+0x578
> Jun 4 03:06:19 xxxxxx kernel: #13 0xffffffff8064ee17 at vmem_alloc+0x37
> Jun 4 03:06:19 xxxxxx kernel: #14 0xffffffff8086c3f5 at kmem_malloc_domainset+0x95
> Jun 4 03:06:19 xxxxxx kernel: #15 0xffffffff8086295d at keg_alloc_slab+0xad
> Jun 4 03:06:19 xxxxxx kernel: #16 0xffffffff80864780 at zone_import+0xe0
> Jun 4 03:06:19 xxxxxx kernel: #17 0xffffffff80860d92 at zone_alloc_item+0x72
Any idea?
What does this mean? Where to look for further info?
Is this a known problem?
bye & Thanks
av.
Reply all
Reply to author
Forward
0 new messages