Messages

1

24.7 Production Series / Re: Update to 24.7.2 results in kernel panic

« on: August 29, 2024, 03:31:53 pm »

The secret has been revealed. 

Of course I mean 24.7.3.


Cheers,
Franco

Hi All,

Update below...

Hardware: Watchguard XTM505. 3GB DDR2 using single SATA Samsung 870 EVO 256GB SSD.

I clean installed 24.7 using serial image and chose ZFS. Configured for connectivity only. Upgraded to 24.7.3 using web GUI without any issues and rebooted normally.

Happy to test anything if anyone needs anything additional

Cheers and thank you to Franco, and the OPNsense team.

2

24.7 Production Series / Re: Update to 24.7.2 results in kernel panic

« on: August 23, 2024, 03:31:38 pm »

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

Hi. I'm running serial image. I'll be happy to test whatever tonight with whatever links and reinstalls and happy to report back

3

24.7 Production Series / Re: Update to 24.7.2 results in kernel panic

« on: August 23, 2024, 02:09:39 am »

Just wanted to add additional information. Screenshot attached as well

Pasting 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.

Hardware: WatchGuard XTM505. Xeon L5420. 3GB DDR2. Samsung 870 EVO 256GB.

Posting in serial console output. This was a clean install of 24.7 using ZFS. Nothing configured other than for pure connectivity and tried to update to 24.7.2. I'll be happy to help further if I can.

Code: [Select]

Mounting filesystems...


Fatal trap 12: page fault while in kernel mode
cpuid = 3; apic id = 03
fault virtual address   = 0x0
fault code              = supervisor read data, page not present
instruction pointer     = 0x20:0xffffffff804d7de7
stack pointer           = 0x28:0xfffffe00594aeb20
frame pointer           = 0x28:0xfffffe00594aeb40
code segment            = base 0x0, limit 0xfffff, type 0x1b
                        = DPL 0, pres 1, long 1, def32 0, gran 1
processor eflags        = interrupt enabled, resume, IOPL = 0
current process         = 29 (zpool)
rdi: fffff8000383b500 rsi: 0000000000020005 rdx: 000000000000000b
rcx: fffff800037ff780  r8: 0000000000000001  r9: 0000000000000000
rax: 0000000000000000 rbx: fffff8000383b500 rbp: fffffe00594aeb40
r10: 0000000000000016 r11: fffff80003817c60 r12: 0000000000002000
r13: 0000000000020005 r14: fffff8000383a700 r15: fffff8000383a600
trap number             = 12
panic: page fault
cpuid = 3
time = 1724369812
KDB: stack backtrace:
db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfffffe00594ae810
vpanic() at vpanic+0x131/frame 0xfffffe00594ae940
panic() at panic+0x43/frame 0xfffffe00594ae9a0
trap_fatal() at trap_fatal+0x40b/frame 0xfffffe00594aea00
trap_pfault() at trap_pfault+0x46/frame 0xfffffe00594aea50
calltrap() at calltrap+0x8/frame 0xfffffe00594aea50
--- trap 0xc, rip = 0xffffffff804d7de7, rsp = 0xfffffe00594aeb20, rbp = 0xfffffe00594aeb40 ---
agp_close() at agp_close+0x57/frame 0xfffffe00594aeb40
giant_close() at giant_close+0x68/frame 0xfffffe00594aeb90
devfs_close() at devfs_close+0x4b3/frame 0xfffffe00594aec00
VOP_CLOSE_APV() at VOP_CLOSE_APV+0x1d/frame 0xfffffe00594aec20
vn_close1() at vn_close1+0x14c/frame 0xfffffe00594aec90
vn_closefile() at vn_closefile+0x3d/frame 0xfffffe00594aece0
devfs_close_f() at devfs_close_f+0x2a/frame 0xfffffe00594aed10
_fdrop() at _fdrop+0x11/frame 0xfffffe00594aed30
closef() at closef+0x24a/frame 0xfffffe00594aedc0
closefp_impl() at closefp_impl+0x58/frame 0xfffffe00594aee00
amd64_syscall() at amd64_syscall+0x100/frame 0xfffffe00594aef30
fast_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>



4

24.7 Production Series / Re: Update to 24.7.2 results in kernel panic

« on: August 22, 2024, 05:39:14 pm »

Just wanted to add additional information. Screenshot attached as well

Pasting 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.

5

24.7 Production Series / Re: Update to 24.7.2 results in kernel panic

« on: August 22, 2024, 05:25:36 pm »

Hi,

I have a Watchguard XTM505. 3GB DDR2 using single SATA Samsung 870 EVO 256GB SSD.

This is happening on my hardware as well and no previous issues any other OPNsense versions.

Nothing additional added or configured in OPNsense after installation.

24.7 clean install works

24.7.1 worked

24.7.2 upgrade from 24 then same issue as OP.

Just wanted to add additional information. Screenshot attached as well