I've just started experimenting with serial consoles, so maybe I've
got something set up incorrectly.

What I've done is installed the serial console bootblocks.  I hadn't
originally had /dev/console on in /etc/ttys, had to ssh in to do that.
At the display, ttyE1's login prompt appears, and if I control-alt-F#,
when I switch back to the window with the serial console, I'm here:

kernel: page fault trap, code=0
Stopped at      wsdisplay_switch+0x19:  cmpl    $0,         0(%eax,%ecx,4)
db> t
wsdisplay_switch(0,0,0,c0a12a00,c3b6edcc) at wsdisplay_switch+0x19
internal_command(c0a12a00,c3b6edd8,f400,3b,c0a13dc0) at internal_command+0x171
wskbd_translate(c0a13d40,2,3b,c0a13d80,c0a13dc0) at wskbd_translate+0xd8
wskbd_input(c0a12a00,2,3b,3b,2) at wskbd_input+0x53
pckbd_input(c0a13d80,3b) at pckbd_input+0x4e
pckbcintr(c0a04d00) at pckbcintr+0xfe
Xintr1() at Xintr1+0x6c
- --- interrupt ---
idle(c3b35658) at idle+0x1c
bpendtsleep(c3b61010,128,c0296603,0,0) at bpendtsleep
sigsuspend1(c3b35658,c3b6ef30,c3b6ef88,0,0) at sigsuspend1+0xfb
sys___sigsuspend14(c3b35658,c3b6ef88,c3b6ef80,0,0) at sys___sigsuspend14+0x36
syscall() at syscall+0x1d8
- --- syscall (number 294) ---
0x480eb40f:

When it boots it says:
Mar  7 22:39:32 crunch getty[196]: /dev/ttyE0: Device not configured
(on the serial console)

This is what is currently on in /etc/ttys:
console "/usr/libexec/getty Pc"         pc3     on secure
ttyE0   "/usr/libexec/getty Pc"         vt220   on secure
ttyE1   "/usr/libexec/getty Pc"         vt220   on secure
ttyE2   "/usr/libexec/getty Pc"         vt220   on secure
ttyE3   "/usr/libexec/getty Pc"         vt220   on secure

Right now it's running a 1.5.1_ALPHA from about February 7th.  The
userland isn't up to that yet, I keep getting uvm panics when I
try to update the userland.  The userland is from a freshly installed
1.5.  I've commented out things I don't have from GENERIC to create
the kernel, but I don't believe anything I commented out should affect
console.  It did work fine before I set up serial console.

I did something wrong, or missed something, but it attempting to
switch virtual consoles should probably not panic the machine.

Suggestions, pointers, help?

Tracy J. Di Marco White
Project Vincent Systems Manager
gendalia@iastate.edu