From owner-freebsd-current  Fri May  4  7:35:34 2001
Delivered-To: freebsd-current@freebsd.org
Received: from mail.zilium.de (plattgetrampelt.von.zilium.de [195.88.176.132])
	by hub.freebsd.org (Postfix) with ESMTP id 24C5637B424
	for <freebsd-current@freebsd.org>; Fri,  4 May 2001 07:35:30 -0700 (PDT)
	(envelope-from joerg@zilium.de)
Received: by mail.zilium.de (Postfix, from userid 1003)
	id E77B3F855; Fri,  4 May 2001 16:35:30 +0200 (CEST)
Date: Fri, 4 May 2001 16:35:30 +0200
From: Joerg Bornschein <joerg@plattwurst.zilium.de>
To: freebsd-current@freebsd.org
Subject: Re: isdn stops working when load increases
Message-ID: <20010504163530.A41236@plattwurst.zilium.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Wed, May 02, 2001 at 09:03:26PM +0200, Jens Schweikhardt wrote:
  
Hello,
  
> I've seen some recent mails related to rtprio oddity which seemed
> to also affect the isdnd. My -current is cvsupped May 1st (and  
> survived; I've still got a fully populated root fs :-)
>
> However, as soon as I do a find / or buildworld or some other
> commands increasing the load significantly (about 1 or more),
> isdnd seems to take a nap. No more packets transmitted. If I
> suspend the running programs, isdnd awakes and continues.
> Is anybody else observing the same behavior?
  
I'm having similar problems:
  
Some minutes/hours (depends on the workload) after each boot 'top'
reports about 12% of my CPU time are used for interrupt processing.
The interrupt time stays at about 10% even when there's nothing to
do (no disk io, no network traffic, no sound).
  
Running FBSD 4.2 on the same box reports about 0.2-1% interrupt usage;
the same value which is shown on CURRENT just after a reboot.
  
At the same time the packet loss rate of my isdn interface raises to   
about 70% while transfering files. (a simple ping does *not* trigger
this problem).
  
This behavior seems not related to rtprio oddity since i first noticed
it on Apr 9th. (the date this box switched to CURRENT)
  
  joerg
  


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