Sorry I got the SKU wrong - its a BMF220ahttps://servers4less.com/bmf220a-barracuda-im-firewall-220-1-x-vga-1-x-keyboard-1-x-10-100base-tx/?srsltid=AfmBOooz7IMXsHzVaYZvXeeg0x6_VUo4LlyN17G3oL46h4fffM9uepXL
Just wanted to add additional information. Screenshot attached as well
Quote from: benkill15 on August 22, 2024, 05:25:36 pmJust wanted to add additional information. Screenshot attached as wellPasting the serial console output would be a whole lot better than the screenshot.
24.7 clean install works24.7.1 worked24.7.2 upgrade from 24 then same issue as OP.
bump: I had the same issue.
Quote from: doktornotor on August 22, 2024, 05:26:47 pmQuote from: benkill15 on August 22, 2024, 05:25:36 pmJust wanted to add additional information. Screenshot attached as wellPasting the serial console output would be a whole lot better than the screenshot.Hi, understood and agreed. It was what I had at the time so will get home later tonight and post full output.
Mounting filesystems...Fatal trap 12: page fault while in kernel modecpuid = 3; apic id = 03fault virtual address = 0x0fault code = supervisor read data, page not presentinstruction pointer = 0x20:0xffffffff804d7de7stack pointer = 0x28:0xfffffe00594aeb20frame pointer = 0x28:0xfffffe00594aeb40code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1processor eflags = interrupt enabled, resume, IOPL = 0current process = 29 (zpool)rdi: fffff8000383b500 rsi: 0000000000020005 rdx: 000000000000000brcx: fffff800037ff780 r8: 0000000000000001 r9: 0000000000000000rax: 0000000000000000 rbx: fffff8000383b500 rbp: fffffe00594aeb40r10: 0000000000000016 r11: fffff80003817c60 r12: 0000000000002000r13: 0000000000020005 r14: fffff8000383a700 r15: fffff8000383a600trap number = 12panic: page faultcpuid = 3time = 1724369812KDB: stack backtrace:db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfffffe00594ae810vpanic() at vpanic+0x131/frame 0xfffffe00594ae940panic() at panic+0x43/frame 0xfffffe00594ae9a0trap_fatal() at trap_fatal+0x40b/frame 0xfffffe00594aea00trap_pfault() at trap_pfault+0x46/frame 0xfffffe00594aea50calltrap() at calltrap+0x8/frame 0xfffffe00594aea50--- trap 0xc, rip = 0xffffffff804d7de7, rsp = 0xfffffe00594aeb20, rbp = 0xfffffe00594aeb40 ---agp_close() at agp_close+0x57/frame 0xfffffe00594aeb40giant_close() at giant_close+0x68/frame 0xfffffe00594aeb90devfs_close() at devfs_close+0x4b3/frame 0xfffffe00594aec00VOP_CLOSE_APV() at VOP_CLOSE_APV+0x1d/frame 0xfffffe00594aec20vn_close1() at vn_close1+0x14c/frame 0xfffffe00594aec90vn_closefile() at vn_closefile+0x3d/frame 0xfffffe00594aece0devfs_close_f() at devfs_close_f+0x2a/frame 0xfffffe00594aed10_fdrop() at _fdrop+0x11/frame 0xfffffe00594aed30closef() at closef+0x24a/frame 0xfffffe00594aedc0closefp_impl() at closefp_impl+0x58/frame 0xfffffe00594aee00amd64_syscall() at amd64_syscall+0x100/frame 0xfffffe00594aef30fast_syscall_common() at fast_syscall_common+0xf8/frame 0xfffffe00594aef30--- syscall (6, FreeBSD ELF64, close), rip = 0x1805a05842ba, rsp = 0x1805a7b73d88, rbp = 0x1805a7b73da0 ---KDB: enter: panic[ thread pid 29 tid 100230 ]Stopped at kdb_enter+0x33: movq $0,0xfd9962(%rip)db>
Let's bring a bit of structure in these unclear +1 posts.Are you using ZFS? How old is the hardware you are using or is it a VM? Does this panic occur due to the 24.7.2 kernel or 24.7.2 core package? I know it's difficult with the panic but we need more data points than "24.7.2 is not working" now.
Tracing pid 31panic() at panic+0x43/frame 0xfffffe007a3169a0trap_fatal() at trap_fatal+0x40b/frame 0xfffffe007a326a00trap_pfault() at trap_pfault+0x46/frame 0xfffffe007a316a50calltrap() at calltrap+0x8/frame 0xfffffe007a316a50--- trap 0xc, rip = 0xffffffff804d7de7, rsp = 0xfffffe007a316b20, rbp = 0xfffff007a316b40 ---agp_close() at agp_close+0x57/frame 0xfffffe007a316b40giant_close() ...devfs_close() ...VOP_CLOSE_APV() ...vn_close1() ...vn_closefile() ...etc.
I've been thinking how to approach this. Would someone care to test two images of 24.7.2 -- one with the actual 24.7.2 state and one with the environment var commit reverted?I think we should do 24.7.3 next week so we need to move this along. We need a way to confirm this precisely and I guess that is the safest way.Cheers,Franco