Re: [9fans] High interruptload on cpu server

[David Presotto <presotto@closedmind.org>]

[-- Attachment #1: Type: text/plain, Size: 403 bytes --]

It's quite odd.  The listener doesn't do anything while waiting for a call,
i.e., sshserve doesn't get started until the call is made.  No matter how
badly you misconfigured it, it won't do anything until you connect to
the port.  It sounds more like your interrupts stop when you have something
to run.

What hardware are you doing this on?  What does /dev/sysstat show
about the interrupt load?

[-- Attachment #2: Type: message/rfc822, Size: 2937 bytes --]

From: Matthias Teege <matthias-9fans@mteege.de>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] High interruptload on cpu server
Date: Tue, 25 Nov 2003 16:35:19 +0100
Message-ID: <86znek1mwi.fsf@gic.mteege.de>

David Presotto <presotto@closedmind.org> writes:

> Could you just probe one service at a time and see what's fixing
> your interrupt load?

Yes, it is port 22 ssh. If I connect to 22 via telnet,ssh, or nmap
the interrupt load goes down for a while. There must be somthing
wrong in my configuration because I can't connect via ssh. I only
get

debug1: ssh_connect: needpriv 0
debug1: Connecting to coco.mteege.de [192.168.153.21] port 22.
debug1: Connection established.
ssh_exchange_identification: Connection closed by remote host
debug1: Calling cleanup 0x804c158(0x0)

Bis dann
Matthias