Date: Mon, 26 Jan 2009 11:10:46 GMT From: Timo Rikkonen <timo.rikkonen@syncrontech.com> To: freebsd-gnats-submit@FreeBSD.org Subject: i386/131006: /dev/cuau* ports hang after a while Message-ID: <200901261110.n0QBAkSK040599@www.freebsd.org> Resent-Message-ID: <200901261120.n0QBK1MW035762@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 131006 >Category: i386 >Synopsis: /dev/cuau* ports hang after a while >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-i386 >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Mon Jan 26 11:20:00 UTC 2009 >Closed-Date: >Last-Modified: >Originator: Timo Rikkonen >Release: 7.0 RELEASE / 7.1-RELEASE-p2 >Organization: Syncron Tech Oy >Environment: FreeBSD connect38.dyndns.syncrontech.net 7.1-RELEASE-p2 FreeBSD 7.1-RELEASE-p2 #0: Mon Jan 26 09:38:26 EET 2009 st@connect38.dyndns.syncrontech.net:/usr/src/sys/i386/compile/GENERIC i386 >Description: 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 >How-To-Repeat: >Fix: In our case we restart the web server, under which all the connection-progams run. >Release-Note: >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200901261110.n0QBAkSK040599>