Hi, We are using "VScom PCI-200L" and "Moxa Technologies, C168H/PCI" -cards for serial ports. After installing 7.0 the ports or the connection to the port hang after a while. A "while" could be half-a-day or 10 minutes. There is no error message to be seen anywhere. Not all ports hang at the same time, it could be just one or two of them. Earlier versions (6.2-RELEASE) work just fine. The ports have different devicenames after 7.0, in 6.2 they were /dev/cuad4-7, now they are /dev/cuau0-3 (uart?) dmesg-output considering the card: puc0: <VScom PCI-200L> port 0xbc00-0xbc07,0xb800-0xb807,0xb400-0xb407,0xb000-0xb007 mem 0xfe5ffc00-0xfe5ffc3f irq 21 at device 0.0 on pci1 puc0: [FILTER] uart0: <16550 or compatible> on puc0 uart0: [FILTER] uart1: <16550 or compatible> on puc0 uart1: [FILTER] the same in 6.2: puc0: <VScom PCI-200L> port 0xbc00-0xbc07,0xb800-0xb807,0xb400-0xb407,0xb000- 0xb007 mem 0xfe5ffc00-0xfe5ffc3f irq 21 at device 0.0 on pci1 sio4: <VScom PCI-200L> on puc0 sio4: type 16550A sio4: unable to activate interrupt in fast mode - using normal mode sio5: <VScom PCI-200L> on puc0 sio5: type 16550A sio5: unable to activate interrupt in fast mode - using normal mode We have over 20 installations, now two of them have been upgraded to 7.0 with mentioned side effects. Yours, Timo Rikkonen
On Mon, 26.01.2009 at 15:00:11 +0200, Timo Rikkonen wrote:> Hi, > > We are using "VScom PCI-200L" and "Moxa Technologies, C168H/PCI" > -cards for serial ports. After installing 7.0 the ports or the > connection to the port hang after a while. A "while" could be > half-a-day or 10 minutes. There is no error message to be seen > anywhere.What exactly do you mean by "hang"? I discovered something odd, when I upgraded my 6.3 box to 7.1, namely, that the serial console (no matter if it's sio or uart) will not echo anything, once I "hang up" the line for the first time. To make this clear: I reboot with serial console attached, I see kernel console, then getty/login prompt. I can login fine, and do stuff. Once I exit tip(1) on the terminal, the port is "mostly" dead on the server. I say mostly, because I can still blindly enter the root login and confirm via separate ssh login, that I'm logged in to the machine on the serial getty port. So it seems to me, whenever sio/uart receive the first device close event, they get b0rked and receive only input, but can no longer send any output.> Not all ports hang at the same time, it could be just one or two of > them. Earlier versions (6.2-RELEASE) work just fine. The ports have > different devicenames after 7.0, in 6.2 they were /dev/cuad4-7, now > they are /dev/cuau0-3 (uart?)Try rebuilding a kernel without uart and see if they come up as sio ports again (and work?)> We have over 20 installations, now two of them have been upgraded to 7.0 with mentioned side effects.Is this identical hardware? Cheers, Ulrich Sp?rlein -- None are more hopelessly enslaved than those who falsely believe they are free -- Johann Wolfgang von Goethe
At 08:00 AM 1/26/2009, Timo Rikkonen wrote:>Hi, > >We are using "VScom PCI-200L" and "Moxa Technologies, C168H/PCI" >-cards for serial ports. After installing 7.0 the ports or the >connection to the port hang after a while. A "while" could be >half-a-day or 10 minutes. >There is no error message to be seen anywhere. > >Not all ports hang at the same time, it could be just one or two of >them. Earlier versions (6.2-RELEASE) work just fine. >The ports have different devicenames after 7.0, in 6.2 they were >/dev/cuad4-7, now they are /dev/cuau0-3 (uart?)Is the application fairly low speed (e.g. 9600bps or slower) ? If so, try with 7.1R, not 7 and add hint.uart.0.flags="0x100" hint.uart.1.flags="0x100" to /boot/device.hints http://www.freebsd.org/cgi/query-pr.cgi?pr=121421 has details ---Mike