Panic on GENERIC @ 6481b4
- Reply: Shawn Webb : "Re: Panic on GENERIC @ 6481b4"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Tue, 13 Aug 2024 21:45:54 UTC
Hello, Compiling freebsd-current/generic at head commit 6481b4 on freebsd-current/generic from July 11th after a `make cleanworld` panics on bare metal boot on a thinkpad x230. It doesn't have a swap, so I don't have a dump. Here is the trace: db> bt Tracing pid 21935 tid 100228 td 0xfffff90006d0e000 kdb_enter() at kdb_enter+0x33/ frame 0xfffffe00d70541d0 panic() at panic+0x43/frame 0xfffffe00d7054230 malloc_init() at malloc_init+0xf7/frame 0xfffffe00d7054560 linker_load_module() at linker_load_module+0xc23/ frame 0xfffffe00d7054560 linker_load_dependencies() at linker_load_dependencies+0x139/frame 0xfffffe00d7054560 link_elf_load_file() at link_elf_load_file+0x11a0/frame 0xfffffe00d7054670 linker_load_module() at linker_load_module+0x9da/ frame 0xfffffe00d7054970 linker_load_dependencies() at linker_load_dependencies+0x139/frame 0xfffffe00d70549c0 link_elf_load_file() at link_elf_load_file+0x11a0/frame 0xfffffe00d7054a80 linker_load_module() at linker_load_module+0x9da/frame 0xfffffe00d7054d80 kern_kldload() at kern_kldload+0x16e/frame 0xfffffe00d7054dd0 sys_kldload() at sys_kldload+0x5c/frame 0xfffffe00d7054e00 amd64_syscall() at amd64_syscall+0x158/frame 0xfffffe00d7054f30 fast_syscall_common() at fast_syscall_common+0xf8/ frame xfffffe00d7054f30 --- syscall (304, FreeBSD ELF64, kldload), rip = 0x28e41 f6a7da, rsp = 0x28e3f19e1f8, rbp = 0x28e3f19e770 --- Is this helpful, or should I not do this again? If it is, how can I write this type of mail to be the most useful? I would be happy to send a patch adding that information if provided to handbook/cutting-edge. My kernel.old and loader.efi is working just fine. I'm setting up a new freebsd laptop which has enough storage for swap, so I will be able to provide dumps in the future. Thanks! Alex