From owner-freebsd-stable@FreeBSD.ORG Thu Nov 19 14:29:02 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2DA5A106566B for ; Thu, 19 Nov 2009 14:29:02 +0000 (UTC) (envelope-from karl@denninger.net) Received: from FS.denninger.net (wsip-70-169-168-7.pn.at.cox.net [70.169.168.7]) by mx1.freebsd.org (Postfix) with ESMTP id CA83F8FC24 for ; Thu, 19 Nov 2009 14:29:01 +0000 (UTC) Received: from [127.0.0.1] (localhost [127.0.0.1]) by FS.denninger.net (8.14.3/8.13.1) with SMTP id nAJET1ew002602 for ; Thu, 19 Nov 2009 08:29:02 -0600 (CST) (envelope-from karl@denninger.net) Received: from [127.0.0.1] [192.168.1.40] by Spamblock-sys (LOCAL); Thu Nov 19 08:29:02 2009 Message-ID: <4B0555CD.8050704@denninger.net> Date: Thu, 19 Nov 2009 08:27:25 -0600 From: Karl Denninger User-Agent: Thunderbird 2.0.0.23 (Windows/20090812) MIME-Version: 1.0 To: Mike Tancsa References: <4B0552B2.2020000@denninger.net> <200911191427.nAJERSl6095906@lava.sentex.ca> In-Reply-To: <200911191427.nAJERSl6095906@lava.sentex.ca> X-Enigmail-Version: 0.96.0 Content-Type: multipart/mixed; boundary="------------010707060401080708000805" X-Antivirus: avast! (VPS 091119-0, 11/19/2009), Outbound message X-Antivirus-Status: Clean X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-stable@freebsd.org Subject: Re: V8.x-PRE2 Serious PUC problem - Heads Up! X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 19 Nov 2009 14:29:02 -0000 This is a multi-part message in MIME format. --------------010707060401080708000805 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Mike Tancsa wrote: > At 09:14 AM 11/19/2009, Karl Denninger wrote: > > >> Mike Tancsa wrote: >> > At 09:00 AM 11/19/2009, Karl Denninger wrote: >> >> Well ok then the uart driver is BROKEN. >> >> >> >> It simply locks up on the port after some period of time, returning >> >> nothing. I have found no way to reset the port other than a reboot >> >> either. That's a "surprise" that people running fax servers and >> other >> >> similar things are going to be very unhappy about. >> > >> > Which serial card are you using ? I have a number of PCI cards (lava >> > for example) that are working quite well with the puc and uart driver >> > combo. Perhaps you could post some details about the hardware used >> > thats having issues. >> > >> > ---Mike >> puc0: port >> 0x4060-0x407f,0x4040-0x405f mem >> 0x94503000-0x94503fff,0x94502000-0x94502fff irq 16 at device 0.0 on pci3 >> puc0: [FILTER] >> uart2: <16550 or compatible> on puc0 >> uart2: [FILTER] >> uart3: <16550 or compatible> on puc0 >> uart3: [FILTER] >> uart4: <16550 or compatible> on puc0 >> uart4: [FILTER] >> uart5: <16550 or compatible> on puc0 >> uart5: [FILTER] >> >> It's a generic board with four ports sitting on the PCI bus. Nothing > > > If you serial app is low speed (e.g 9600), try adding > > hint.uart.2.flags="0x100" > hint.uart.3.flags="0x100" > hint.uart.4.flags="0x100" > hint.uart.5.flags="0x100" > > to /boot/device.hints and reboot > > ---Mike It's not. What does that do? (The ports run 38400 or 57600 - higher preferred, 38.4k is the minimum for it to work) -- Karl --------------010707060401080708000805--