On Fri, May 22 2015 at 35:19, mxb wrote:
> Hey,
Hello,
> got a panic as of todays ‘cvs up’
> trace below
I got nearly the same panic stopping a 5.7 host
> panic: vmxnet3_rxintr: NULL ring->m[44]
> Stopped at Debugger+0x9: leave
> RUN AT LEAST 'trace' AND 'ps' AND INCLUDE OUTPUT WHEN REPORTING THIS PANIC!
> IF RUNNING SMP, USE 'mach ddbcpu <#>' AND 'trace' ON OTHER PROCESSORS, TOO.
> DO NOT EVEN BOTHER REPORTING THIS WITHOUT INCLUDING THAT INFORMATION!
> ddb{0}> Debugger() at Debugger+0x9
> panic() at panic+0xfe
> vmxnet3_rxintr() at vmxnet3_rxintr+0x284
> vmxnet3_intr() at vmxnet3_intr+0x4a
> intr_handler() at intr_handler+0x67
> Xintr_ioapic_level10() at Xintr_ioapic_level10+0xcd
> --- interrupt ---
> Xspllower() at Xspllower+0xe
> if_downall() at if_downall+0x9b
> boot() at boot+0xe4
> reboot() at reboot+0x26
> sys_reboot() at sys_reboot+0x5e
> syscall() at syscall+0x297
> --- syscall (number 55) ---
> end of kernel
> end trace frame: 0x7f7ffffd5858, count: -12
> 0x184f48704eda:
> ddb{0}> rebooting...
> OpenBSD 5.7-current (GENERIC.MP) #0: Fri May 22 16:30:54 CEST 2015
bsd1:/usr # reboot
syncing discks... done
panic: vmxnet3_rxintr: NULL ring->m[3]
Stopped at Debugger+0x9: leave
RUN AT LEAST 'trace' AND 'ps' AND INCLUDE OUTPUT WHEN REPORTING THIS PANIC!
DO NOT EVEN BOTHER REPORTING THIS WITHOUT INCLUDING THAT INFORMATION!
ddb> trace
Debugger() at Debugger+0x9
panic() at panic+0xfe
vmxnet3_rxintr() at vmxnet3_rxintr+0x284
vmxnet4_intr() at vmxnet3_intr+0x4a
intr_handler() at intr_handler+0x28
Xintrioapic_level10() at Xintr_ioapic_level10+0xe1
--- interrupt ---
Bad frame pointer: 0xffff80000e5e0cd8
end trace frame: 0xffff80000e5e0cd8, count: -6
Xspllower+0xe:
ddb>
bsd1:~ # uname -a
OpenBSD bsd1.primaire-bench.local 5.7 GENERIC#825 amd64
I'll try the patch from mike and report.
Claer
