I didn't pay attention to machdep.forceukbd before. My mistake! With it set to 1, as you suggested, my keyboards can now type on ddb. Thanks Jonathan!
Now I'm set to deal with the kernel panic that brought me here in the first place. On Sun, Nov 20, 2022 at 1:04 AM Jonathan Gray <[email protected]> wrote: > > On Sun, Nov 20, 2022 at 12:44:36AM -0300, Josmar Pierri wrote: > > Hi, > > > > I discovered that neither of my keyboards are capable of sending > > keystrokes to ddb after a kernel panic. > > > > Here is what I know so far: > > > > 1 - It randomly happens under 7.2 on two different Dell R440 servers, > > and also happened the same way when they were running 7.1 > > > > 2 - It also happens on my old Dell desktop that now is running the > > latest 7.2 snapshot (GENERIC.MP#845 from today) > > > > 3 - As said by man ddb, CTRL ALT ESC and CTRL ALT DEL should bring ddb > > up when machdep.kbdreset=2 and ddb.console=1 but, with my USB > > keyboards, nothing happens pressing them. > > > > 4 - When I set ddb.trigger=1 the ddb appears as expected, however I > > can't type anything on it. No keys from my USB keyboards are accepted. > > > > 5 - Unfortunately there is no PS/2 keyboard connector or serial port > > on any of these machines. > > > > I'm stuck. > > Could someone please tell me what I'm missing? > > Try machdep.forceukbd=1. This sysctl exists on amd64 and i386 and > should let you use a USB keyboard with ddb. > > Otherwise see crash(8). With ddb.panic=0 the state can be saved to > disk without needing keyboard interaction, and can be examined later.
