Jay, That bug report sucks ass.
It seems you went out of the way to not include all the information you are required to include. It is almost impossible to file a report without including the details, so you must have chosen to delete it. Are you special enough that you believe you can get away with wasting everyone's time like that? Good luck -- you are on your own! Hitting the 'd' key now. I can assure you almost all the developers will do the same. > >Synopsis: System panics after several weeks of runtime > >Category: kernel > >Environment: > System : OpenBSD 5.9 > Details : OpenBSD 5.9 (GENERIC.MP) #1: Tue Jun 7 11:50:36 EDT > 2016 > > [email protected]:/usr/src/sys/arch/amd64/compile/GENERIC.MP > > Architecture: OpenBSD.amd64 > Machine : amd64 > >Description: > Jul 25 09:30:17 gateway1 savecore: reboot after panic: kernel diagnostic > assertion "pkt->pkt_m != NULL" failed: file "../../../../dev/pci/if_em.c", > line 2400 > Jul 25 09:30:17 gateway1 savecore: /var/crash/bounds: No such file or > directory > Jul 25 09:30:17 gateway1 savecore: writing core to /var/crash/bsd.0.core > > (gdb) file /var/crash/bsd.0 > Reading symbols from /var/crash/bsd.0...(no debugging symbols found)...done. > (gdb) target kvm /var/crash/bsd.0.core > #0 0xffffffff81322564 in dumpsys () > (gdb) where > #0 0xffffffff81322564 in dumpsys () > #1 0x000000017ea80000 in ?? () > #2 0x0000000000000006 in ?? () > #3 0xffffffff81366950 in sd_flush () > Previous frame inner to this frame (corrupt stack?) > > >How-To-Repeat: > Let the system run for a few weeks > >Fix: > Unknown - core available if needed >
