From owner-freebsd-isdn  Sun May 19  8:36:30 2002
Delivered-To: freebsd-isdn@freebsd.org
Received: from clever.eusc.inter.net (clever.eusc.inter.net [213.73.101.4])
	by hub.freebsd.org (Postfix) with ESMTP id 27C2B37B405
	for <freebsd-isdn@freebsd.org>; Sun, 19 May 2002 08:36:25 -0700 (PDT)
Received: from tc09-n66-229.de.inter.net ([213.73.66.229] helo=there)
	by clever.eusc.inter.net with smtp (Exim 3.36 #1)
	id 179SjP-0002Qp-00
	for freebsd-isdn@FreeBSD.ORG; Sun, 19 May 2002 17:36:23 +0200
Content-Type: text/plain;
  charset="iso-8859-1"
From: Matthias Schuendehuette <msch@snafu.de>
Reply-To: msch@snafu.de
Organization: Micro$oft-free Zone
To: freebsd-isdn@FreeBSD.ORG
Subject: i4b on -current
Date: Sun, 19 May 2002 17:36:23 +0200
X-Mailer: KMail [version 1.3.1]
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Message-Id: <E179SjP-0002Qp-00@clever.eusc.inter.net>
Sender: owner-freebsd-isdn@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-isdn.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-isdn>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-isdn>
X-Loop: FreeBSD.org

Hi you all,

I'm tracking -current for informational purposes and found, that i4b 
has nearly no transfer rate anymore. I see transfer stalls of 45sec and 
more and average transfer rates *below* 1KB/s. I see this behaviour for 
about 2 month now (under -current)...

Of course I checked all available debugging and loggin features of i4b, 
but a least I myself can't see anything abnormal - I'm using i4b under 
-stable for several years now and I'm totally commited to i4b since 
then.

BTW: The mentioned stalls occur with isp-Interfaces as well as with 
ipr-Interfaces, so I don't think that sppp is of any concern here. I'm 
using a Teles 16.3 ISA-Card without PnP and I reserved the IRQ 10 of 
that card in the BIOS-Setup... anyway, it's working flawlessly on the 
same hardware under -stable.

So - any hints from the ISDN-Gurus? Known behaviour? Reasons? 
Workarounds (other than using -stable :-)?
-- 
Ciao/BSD - Matthias

Matthias Schuendehuette	<msch@snafu.de>, Berlin (Germany)
Powered by FreeBSD 4.6-RC

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-isdn" in the body of the message