From owner-freebsd-questions@FreeBSD.ORG Mon Oct 13 09:08:03 2003 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8A07A16A4B3 for ; Mon, 13 Oct 2003 09:08:03 -0700 (PDT) Received: from main.gmane.org (main.gmane.org [80.91.224.249]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2A8A443FAF for ; Mon, 13 Oct 2003 09:08:01 -0700 (PDT) (envelope-from freebsd-questions@m.gmane.org) Received: from list by main.gmane.org with local (Exim 3.35 #1 (Debian)) id 1A95El-0005Of-00 for ; Mon, 13 Oct 2003 18:07:59 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-questions@freebsd.org Received: from sea.gmane.org ([80.91.224.252]) by main.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 1A95Ej-0005OV-00 for ; Mon, 13 Oct 2003 18:07:57 +0200 Received: from news by sea.gmane.org with local (Exim 3.35 #1 (Debian)) id 1A95Ej-0004af-00 for ; Mon, 13 Oct 2003 18:07:57 +0200 From: Jesse Guardiani Date: Mon, 13 Oct 2003 12:07:55 -0400 Organization: WingNET Lines: 64 Message-ID: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7Bit X-Complaints-To: usenet@sea.gmane.org User-Agent: KNode/0.7.2 X-Mail-Copies-To: never Sender: news Subject: sio3 (COM4) problems on FreeBSD 4.8-RELEASE X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: jesse@wingnet.net List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Oct 2003 16:08:03 -0000 Howdy list, I'm having trouble with my sio3 (/dev/cuaa3) port on one of my servers (with an SMP kernel). When I try to `tip com4` to a cisco switch using this port, I get only partial data, and this appears in the logs: messages:Oct 10 17:18:37 billmax /kernel: sio3 at port 0x2e8-0x2ef irq 9 on isa0 messages:Oct 10 17:18:38 billmax /kernel: sio3: type 16550A messages:Oct 10 17:20:16 billmax /kernel: sio3: 1 more silo overflow (total 1) messages:Oct 10 17:20:18 billmax /kernel: sio3: 1 more silo overflow (total 2) messages:Oct 10 17:20:21 billmax /kernel: sio3: 1 more silo overflow (total 3) messages:Oct 10 17:20:22 billmax /kernel: sio3: 1 more silo overflow (total 4) messages:Oct 10 17:20:23 billmax /kernel: sio3: 1 more silo overflow (total 5) messages:Oct 10 17:20:27 billmax /kernel: sio3: 1 more silo overflow (total 6) messages:Oct 10 17:20:36 billmax /kernel: sio3: 1 more silo overflow (total 7) messages:Oct 10 17:20:38 billmax /kernel: sio3: 1 more silo overflow (total 8) messages:Oct 10 17:20:45 billmax /kernel: sio3: 1 more silo overflow (total 9) messages:Oct 10 17:20:48 billmax /kernel: sio3: 1 more silo overflow (total 10) messages:Oct 10 17:21:04 billmax /kernel: sio3: 1 more silo overflow (total 11) messages:Oct 10 17:22:15 billmax /kernel: sio3: 1 more silo overflow (total 12) messages:Oct 10 17:40:07 billmax /kernel: sio3: 1 more silo overflow (total 13) messages:Oct 10 17:46:29 billmax /kernel: sio3: 1 more silo overflow (total 14) If I move the console cable from com4 to com1 on the server and keep the console cable in the same switch, then `tip com1`, it works fine. It's just the sio3 port that I'm having trouble with. Note that this machine only has sio1 and sio3. Here's my sio kernel config: # Serial (COM) ports device sio0 at isa? port IO_COM1 flags 0x10 irq 4 device sio1 at isa? port IO_COM2 irq 3 device sio2 at isa? disable port IO_COM3 irq 5 device sio3 at isa? port IO_COM4 flags 0x10 irq 9 Also, I've tried it with AND without the 0x10 flag (which I know just allows the com device to be used as a serial console). AND I've tried it with the "do not use FIFO" flag (0x00002) on COM4, like this: # Serial (COM) ports device sio0 at isa? port IO_COM1 flags 0x10 irq 4 device sio1 at isa? disable port IO_COM2 irq 3 device sio2 at isa? disable port IO_COM3 irq 5 device sio3 at isa? port IO_COM4 flags 0x00002 irq 9 I get the same error in the log either way. Port speed is set to 9600 in all tests. I get the same problem under conserver, so it's not directly related to the `tip` command, but the device. Is there some magic voodoo flag that I need to pass to this port to get it working? Thanks! -- Jesse Guardiani, Systems Administrator WingNET Internet Services, P.O. Box 2605 // Cleveland, TN 37320-2605 423-559-LINK (v) 423-559-5145 (f) http://www.wingnet.net