Date: Thu, 24 Mar 2005 16:53:39 +0800 From: Mars Trading <marstrade@gmail.com> To: Rene Ladan <r.c.ladan@student.tue.nl> Cc: freebsd-stable@freebsd.org Subject: Re: naming of usb tty device Message-ID: <200503241653.40142.marstrade@gmail.com> In-Reply-To: <20050324075119.GA7404@82-168-75-155-bbxl.xdsl.tiscali.nl> References: <200503241515.59257.marstrade@gmail.com> <20050324075119.GA7404@82-168-75-155-bbxl.xdsl.tiscali.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200503241653.40142.marstrade>