On Sun, Nov 24, 2013 at 12:16:52AM -0800, Paul B. Henson wrote: > com2 at isa0 port 0x3e8/8 irq 5: ns16550a, 16 byte fifo > com2: console > [...] > root on rd0a swap on rd0b dump on rd0b > erase ^?, werase > > Every time, it wedges up at this spot. The console still works for > kernel messages though, if I unplug the ipmi virtual cd, I see that: [...] > It looks like as soon as userspace touches the console, it freezes up.
Well, it turns out the IPMI SOL com2 uses irq 10 for whatever reason rather than irq 5. Both linux and freebsd successfully detect this: [ 2.324044] 00:0e: ttyS2 at I/O 0x3e8 (irq = 10) is a 16550A uart2: <16550 or compatible> port 0x3.8-0x3ef irq 10 on acpi0 However, openbsd tries to use irq 5, which doesn't turn out so well. I'm guessing the kernel doesn't use the irq, which is why those messages still work, but userspace craps out when it tries to use the wrong irq. I tweaked the kernel with config -e to change the irq for com2 to 10, and it now works fine: com2 at isa0 port 0x3e8/8 irq 10: ns16550a, 16 byte fifo com2: console [...] root on sd2a (b158108c15640a28.a) swap on sd2b dump on sd2b Automatic boot in progress: starting file system checks. setting tty flags pf enabled I suppose the installer kernel could be fixed the same way, but at least for this initial install it's not worth it, I'll just install with the kvm head, fix the installed kernel, and then go serial from there. Is there any particular reason openbsd can't dynamically detect the irq?
