From owner-freebsd-stable@FreeBSD.ORG Mon Feb 28 00:45:02 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 91C1D16A4CE for ; Mon, 28 Feb 2005 00:45:02 +0000 (GMT) Received: from sccrmhc11.comcast.net (sccrmhc14.comcast.net [204.127.202.59]) by mx1.FreeBSD.org (Postfix) with ESMTP id F341243D31 for ; Mon, 28 Feb 2005 00:45:01 +0000 (GMT) (envelope-from bfoz@bfoz.net) Received: from [192.168.0.5] (c-67-161-34-150.client.comcast.net[67.161.34.150]) by comcast.net (sccrmhc14) with ESMTP id <2005022800450001400s74vfe>; Mon, 28 Feb 2005 00:45:01 +0000 Message-ID: <4222698B.6000609@bfoz.net> Date: Sun, 27 Feb 2005 16:44:59 -0800 From: Brandon Fosdick User-Agent: Mozilla Thunderbird 0.9 (X11/20041111) X-Accept-Language: en-us, en MIME-Version: 1.0 To: stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: putc to a clist with no reserved cblocks X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Feb 2005 00:45:02 -0000 I'm working on a small app that talks to a device with a FTDI USB to 232 chip in it. ucom and uftdi seem to detect it just fine. But calls to read() hang and I'm getting messages like "putc to a clist with no reserved cblocks" in my kernel logs. Any idea what this is? In a previous post (subject: ucom and sio) I asked about a similar problem with read() hanging on prolific chips. The fix involved ignoring modem control lines with CLOCAL, but that doesn't appear to do the trick here. Oddly, the exact same software/hardware works fine on my powerbook. What am I missing? I can send code if its needed. Thanks