Re: How to enter ddb on recent NetBSD/amd64 current

[Patrick Welche <prlw1%cam.ac.uk@localhost>]

On Mon, Jul 13, 2015 at 12:57:52PM +0100, Patrick Welche wrote:
> On Sat, Jan 04, 2014 at 10:27:55AM +0900, Ryo ONODERA wrote:
> > From: Ryo ONODERA <ryo_on%yk.rim.or.jp@localhost>, Date: Sat, 04 Jan 2014 10:21:28 +0900 (JST)
> > 
> > > Hi,
> > > 
> > > From: Paul Goyette <paul%whooppee.com@localhost>, Date: Fri, 3 Jan 2014 17:11:41 -0800 (PST)
> > > 
> > >> It works for me (I'm running amd64 6.99.28), but ONLY if you have
> > >> 'wsconscfg -s 1' (ie, you need to select the real console).
> > > 
> > > Hmm...
> > > I am in first virtual terminal.
> > > 
> > > And I have setup another NetBSD/amd64 6.99.28 machine with external USB
> > > keyboard, <Ctrl>-<Alt>-<Esc> works as expected.
> > > 
> > > I will use older kernel, and try again.
> > 
> > Hi,
> > 
> > With the older kernel that is not effected with PR kern/48494 and external USB
> > keyboard, <Ctrl>-<Alt>-<Esc> does not work.
> > 
> > How to debug this problem?
> > Any clue?
> 
> No and I just saw the same thing on 7.99.20 GENERIC/amd64.
> After a boot -2vx, w tells me I'm root on console.
> <Ctrl>-<Alt>-<Esc> does not get me into ddb.
> I tried changing hw.cnmagic to 0xb, and hitting <Ctrl>-K also does nothing.
> boot -2vxd does get me into ddb
> Note the -2 which switches off ACPI and suggests that this isn't PR 48494...

There may be some console confusion as I see (still without ACPI):

pckbc0 at isa0 port 0x60-0x64
pckbd0 at pckbc0 (kbd slot)
pckbc0: using irq 1 for kbd slot
wskbd0 at pckbd0: console keyboard, using wsdisplay0
...
uhidev0 at uhub2 port 1 configuration 1 interface 0
uhidev0: NOVATEK USB Keyboard, rev 1.10/1.12, addr 3, iclass 3/1
ukbd0 at uhidev0: 8 modifier keys, 6 key codes
wskbd1 at ukbd0 mux 1
wskbd1: connecting to wsdisplay0
uhidev1 at uhub2 port 1 configuration 1 interface 1
uhidev1: NOVATEK USB Keyboard, rev 1.10/1.12, addr 3, iclass 3/0
uhidev1: 4 report ids
uhid0 at uhidev1 reportid 2: input=1, output=0, feature=0
uhid1 at uhidev1 reportid 3: input=3, output=0, feature=0
uhid2 at uhidev1 reportid 4: input=2, output=0, feature=0

I suspect that the first wskbd0 is some sort of management console
module which isn't present. There are no PS/2 keyboard connectors,
so the only keyboard is the USB one, but

   wskbd1 at ukbd0 mux 1

there is a lack of "console" in this line


I tried disabling pckbc

uc> diskable pckbc
[125] pckbc0 disabled

but no change:

wsdisplay0 at vga0 kbdmux 1: console (80x25, vt100 emulation)
wsmux1: connecting to wsdisplay0
ukbd0 at uhidev0: 8 modifier keys, 6 key codes
wskbd0 at ukbd0 mux 1
wskbd0: connecting to wsdisplay0

So can lack of "console" be the reason I can't break into ddb?

Cheers,

Patrick