On 2017/08/04 09:06, Jesper Wallin wrote:
> After applying the latest errata patches for 6.1 yesterday (logged
> on via ssh), I rebooted our apu2 acting as a gateway. The machine
> stopped responding (the ssh session hung) and this morning I logged
> on via serial console to learn it was stuck at the ddb{3} prompt.
To clarify: you ran syspatch, and after fetching the patches (but still
on the old kernel) you attempted to reboot, and it stopped responding
at that point - is that correct?
Which kernel was it running previously? If you're not sure, "zgrep OpenBSD
/var/log/messages*" might still have the kernel timestamp from when it booted.
Here's a list of kernels from syspatch to match up.
61-002_vmmfpu: OpenBSD 6.1 (GENERIC.MP) #20: Sat Apr 1 13:45:56 MDT
2017
61-004_softraid_concat: OpenBSD 6.1 (GENERIC.MP) #1: Tue May 2 10:47:59 CEST
2017
61-005_pf_src_tracking: OpenBSD 6.1 (GENERIC.MP) #2: Tue May 2 12:58:57 CEST
2017
61-008_exec_subr: OpenBSD 6.1 (GENERIC.MP) #4: Sat May 6 09:33:37 CEST
2017
61-009_icmp_opts: OpenBSD 6.1 (GENERIC.MP) #5: Thu May 18 22:22:32 CEST
2017
61-012_wsmux: OpenBSD 6.1 (GENERIC.MP) #6: Mon May 22 20:34:30 CEST
2017
61-013_icmp6_linklocal: OpenBSD 6.1 (GENERIC.MP) #7: Mon Jun 12 20:41:01 CEST
2017
61-015_sigio: OpenBSD 6.1 (GENERIC.MP) #8: Tue Jun 27 08:50:26 CEST
2017
61-016_sendsyslog: OpenBSD 6.1 (GENERIC.MP) #9: Thu Aug 3 12:03:39 CEST
2017
61-017_fuse: OpenBSD 6.1 (GENERIC.MP) #10: Thu Aug 3 12:24:00 CEST
2017
61-018_recv: OpenBSD 6.1 (GENERIC.MP) #11: Thu Aug 3 12:36:28 CEST
2017
61-019_tcp_usrreq: OpenBSD 6.1 (GENERIC.MP) #12: Thu Aug 3 12:50:41 CEST
2017
61-020_sockaddr: OpenBSD 6.1 (GENERIC.MP) #13: Thu Aug 3 13:08:51 CEST
2017
61-021_ptrace: OpenBSD 6.1 (GENERIC.MP) #14: Thu Aug 3 13:27:01 CEST
2017
61-022_fcntl: OpenBSD 6.1 (GENERIC.MP) #15: Thu Aug 3 13:45:26 CEST
2017
61-023_wsdisplay: OpenBSD 6.1 (GENERIC.MP) #16: Thu Aug 3 14:04:03 CEST
2017
61-024_sosplice: OpenBSD 6.1 (GENERIC.MP) #17: Thu Aug 3 14:22:19 CEST
2017
61-025_ieee80211: OpenBSD 6.1 (GENERIC.MP) #18: Thu Aug 3 14:40:44 CEST
2017
If it happens again, post the panic message - if you don't have
anything logging the serial at the time you can repeat it with "show
panic". Also the process listing ("ps" in DDB) - this occurred when
a process was exiting and it would be useful to know which one.
Information about config of the machine might help too. Which PF
features are you using? Any source tracking? What daemons are you
using? (ftp-proxy? relayd? etc.)
