From owner-freebsd-stable@FreeBSD.ORG Thu Mar 24 08:53:45 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 1B61116A4CE for ; Thu, 24 Mar 2005 08:53:45 +0000 (GMT) Received: from smtp4.info.com.ph (smtp4.info.com.ph [202.57.96.77]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5E10243D48 for ; Thu, 24 Mar 2005 08:53:44 +0000 (GMT) (envelope-from marstrade@gmail.com) Received: from smtp2.info.com.ph (smtp2.info.com.ph [202.57.96.78]) by smtp4.info.com.ph (8.12.11/8.12.11) with ESMTP id j2O8pLs6007985; Thu, 24 Mar 2005 16:51:21 +0800 Received: from 210.213.216.238.pldt.net (loopback.epldt.net [127.0.0.1] (may be forged)) by smtp2.info.com.ph (8.12.11/8.12.11) with ESMTP id j2O8jXsE029333; Thu, 24 Mar 2005 16:45:34 +0800 From: Mars Trading To: Rene Ladan Date: Thu, 24 Mar 2005 16:53:39 +0800 User-Agent: KMail/1.7.2 References: <200503241515.59257.marstrade@gmail.com> <20050324075119.GA7404@82-168-75-155-bbxl.xdsl.tiscali.nl> In-Reply-To: <20050324075119.GA7404@82-168-75-155-bbxl.xdsl.tiscali.nl> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200503241653.40142.marstrade@gmail.com> cc: freebsd-stable@freebsd.org Subject: Re: naming of usb tty device 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: Thu, 24 Mar 2005 08:53:45 -0000 Hello Rene, On Thursday 24 March 2005 15:51, you wrote: > On Thu, Mar 24, 2005 at 03:15:58PM +0800, Mars Trading wrote: > > Hello, > > > > I heard that tty usb devices would be renamed to /dev/cuaU# > > replacing /dev/ucom#. Is this going to happen in 5.4-RELEASE? > > I > > This is true for 6.0 (CURRENT), in which it has already happened, > but it is highly unlikely that it will be MFC'd to RELENG_5 (and > thus 5.4-RELEASE) as it breaks POLA. You should contact phk for > this stuff. > > > hope so; I'm still having problems using uplcom+ucom. Maybe > > the renaming thing would help? > > What kind of problems? uplcom works fine on my 5-STABLE box, > where I use the uplcom device to talk to my mobile phone. > The problem is similar to that mentioned in PR usb/77294 which states: >I get reproducable panic()s that look like a NULL pointer >dereference. >What I saw on the console: >putc to a clist with no reserved blocks >putc to a clist with no reserved blocks >putc to a clist with no reserved blocks >putc to a clist with no reserved blocks >putc to a clist with no reserved blocks >putc to a clist with no reserved blocks >putc to a clist with no reserved blocks >putc to a clist with no reserved blocks >putc to a clist with no reserved blocks >putc to a clist with no reserved blocks >putc to a clist with no reserved blocks >putc to a clist with no reserved blocks >putc to a clist with no reserved blocks >putc to a clist with no reserved blocks >ucom1: read start failed >fatal trap 12 in kernel mode >fault virtual address = 0x4c >[ ... ] >current process = getty >stopped at usb_transfer_complete+0xd2: movl 0x4c(%eax),%eax The person who wrote the PR was using getty; I'm using mgetty and I get kernel panics "every now and then" usually after 12-24hrs., sometimes less. What I did was to take sys/dev/usb/uplcom.c from -current and used it on -stable (crazy, I know). I still get a lot of those "putc to a clist with no reserved cblocks' but the machine stayed up for over 7 days. Though I hear -current is quite usable, I'm too chicken to try it out. Dennis -- Mars Trading 9620 Kamagong St., Makati, Manila, Philippines Phone: (632) 8952241 FAX: (632) 8996124 email: marstrade@gmail.com