> Does it drop to ddb out of the blue without a clear reason? I don't know, maybe there was some output before the ddb prompt...
> Someone posted similar issue some time ago and it turned out to be a > noise on the serial line resulting in spuriou "break into debugger" > sequence. Do you mean https://marc.info/?l=openbsd-bugs&m=173671607503431&w=2 ? > What your ddb.console sysctl? ddb.console=0 The console cable wasn't connected. The console speed was set to 115200, I have already switched to 9600. I don't understand why I can see the booting process on 9600 now but I need to reconnect with 115200 to log in to the system. It seemed to me that the whole system would be available at 9600 (stty com0 9600). Radek On Sun, 18 May 2025 12:16:03 +0100 Chris Narkiewicz <he...@ezaquarii.com> wrote: > On Sun, May 18, 2025 at 12:09:27PM +0200, Radek wrote: > > ddb{1}> show panic > > the kernel did not panic > > Does it drop to ddb out of the blue without a clear reason? > > Someone posted similar issue some time ago and it turned out to be a > noise on the serial line resulting in spuriou "break into debugger" > sequence. > > What your ddb.console sysctl? > > Best regards, > Chris Narkiewicz > --
