From owner-freebsd-current Fri Nov 22 19:33:48 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5428837B401 for ; Fri, 22 Nov 2002 19:33:47 -0800 (PST) Received: from scl8owa02.int.exodus.net (scl8out02.exodus.net [66.35.230.242]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8866F43E9C for ; Fri, 22 Nov 2002 19:33:43 -0800 (PST) (envelope-from Maksim.Yevmenkin@cw.com) Received: from SJDCEX01.int.exodus.net ([165.193.27.80]) by scl8owa02.int.exodus.net with Microsoft SMTPSVC(5.0.2195.5329); Fri, 22 Nov 2002 19:33:43 -0800 X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable Subject: RE: Bluetooth questions Date: Fri, 22 Nov 2002 19:33:43 -0800 Message-ID: <45258A4365C6B24A9832BFE224837D552B1265@sjdcex01.int.exodus.net> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Bluetooth questions Thread-Index: AcKSnOLq1IMnK7thQN6rls8RwNPKzQAAmbTl From: "Maksim Yevmenkin" To: "M. Warner Losh" Cc: , , X-OriginalArrivalTime: 23 Nov 2002 03:33:43.0417 (UTC) FILETIME=[1F692690:01C292A1] Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > In message: = <45258A4365C6B24A9832BFE224837D552B1264@sjdcex01.int.exodus.net> > "Maksim Yevmenkin" writes: > : I see a lot of "silo overflow" errors under moderate load. > : As a result bytes get dropped on the floor. The Bluetooth > : spec defines extremely simple serial protocol (H4). It simply > : cannot tolerate UARTs that drop bytes. If at least one byte > : gets dropped the entire HCI frame is lost. If HCI frame gets > : dropped then "out of sync" condition exist and all bets are > : off. The only way to get back "in sync" is to send Reset to > : the device. After Reset device goes into standby state and > : all operational state is lost.=20 >=20 > OK. That makes sense. Part of the problem even with even fast > interrupt handlers is that interrupts are masked for way way too much > code in -current, as compared to -stable. What baud rate are you > running at? I'm running at 56k, which isn't the full datarate for > 115200 baud that could be used. Even with a fast interrupt, you'd get > SIO overflows in current, at least according to some reports. everything is set to 115200, but i think the hardware does=20 something funny with the divisor and internal rate is much higher. with OLDCARD i managed to run Xircom card with fast interrupts and acually got about 50 KBytes/sec. USB devices give me about 60KBytes/sec. > Hmmm, maybe I should get one of these cards, or one a normal sio > cards and run them at 115200 baud. good idea. thanks, max To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message