On Jan 14 19:10:32, kolip...@exoticsilicon.com wrote: > On Fri, Jan 14, 2022 at 10:41:52PM +0100, Jan Stary wrote: > > I suspect it's com1; I have yet to try commenting out just tty01. > > But commenting out both makes it boot OK. > > > > com0 at acpi0 COMA addr 0x3f8/0x8 irq 4: ns16550a, 16 byte fifo > > com1 at acpi0 COMB addr 0x2f8/0x8 irq 3: ti16750, 64 byte fifo > > > > Are these known to misbehave under ttyflags? > > > > I realize a lot has changed since then, but it's a production machine, > > and while I would love nothing more than go through the releases one > > by one, this machine has to run now. > > Well there were recently changes to make com attach via acpi, and now > you have a com port that you didn't have before.
Yes. > My suspicion would be that the new com1 > either does not really exist in hardware, That confuses me: what would "ti16750" (Texas Instruments?) mean for something that does not exist? > or that it's mis-configured. > Does the BIOS mention it? Can it be disabled there? I will have a look once I am at the machine. This seems to be an old problem: https://marc.info/?l=openbsd-bugs&m=105086880922041&w=2 Jan
