From owner-freebsd-current@FreeBSD.ORG Thu Oct 21 06:45:52 2004 Return-Path: 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 32BF116A4CE for ; Thu, 21 Oct 2004 06:45:52 +0000 (GMT) Received: from anduin.net (anduin.net [212.12.46.226]) by mx1.FreeBSD.org (Postfix) with ESMTP id E90EA43D39 for ; Thu, 21 Oct 2004 06:45:51 +0000 (GMT) (envelope-from ltning@anduin.net) Received: from mailnull by anduin.net with dspam-scanned (Exim 4.43 (FreeBSD)) id 1CKWet-000PBu-A5 for current@freebsd.org; Thu, 21 Oct 2004 08:42:47 +0200 Received: from mailnull by anduin.net with spamassassin-scanned (Exim 4.43 (FreeBSD)) id 1CKWeq-000PBn-8y for current@freebsd.org; Thu, 21 Oct 2004 08:42:47 +0200 Received: from eirik.unicore.no ([213.225.74.166]) by anduin.net with esmtp (Exim 4.43 (FreeBSD)) id 1CKWeq-000PBk-4U for current@freebsd.org; Thu, 21 Oct 2004 08:42:44 +0200 From: Eirik Oeverby To: current@freebsd.org Content-Type: text/plain Date: Thu, 21 Oct 2004 08:46:19 +0200 Message-Id: <1098341179.52186.7.camel@eirik.unicore.no> Mime-Version: 1.0 X-Mailer: Evolution 2.0.1FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit X-Spam-Checker-Version: SpamAssassin 2.64 (2004-01-11) on anduin.net X-Spam-Level: X-Spam-Status: No, hits=-4.5 required=7.5 tests=AWL,BAYES_00 autolearn=ham version=2.64 Subject: Weirdness in RELENG_5 on amd64 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Oct 2004 06:45:52 -0000 Hi, my dual Opteron server is experiencing strange problems; the same I've been seeing since I installed it back in May. After a bit of uptime (varies between 1-2 days and a month or two, depending on the kernel release I am running) it will start acting up (if I'm lucky) or simply panic. I have no panic message dump, since the box is very far away and last time it paniced I had no serial console. However yesterday it started acting up again: I was no longer able to log in via SSH. Whenever I tried, the SSH client bailed out with the message: ssh_exchange_identification: Connection closed by remote host On my serial console I have syslog set to spew *.* on the console, but there was absolutely no messages from sshd or any other source whatsoever. Running /etc/rc.d/sshd restart solved the problem - for now - but I'm worried that this might be indicative of a more serious problem. I will not be surprised if the box panics sometime in the next few hours or days. Anyone got any idea? This is a 12 day old build. A related question: How do I make absolutely sure that kernel messages are output on the serial console? I'm currently not sure this is the case, so I don't know if I can even do anything when it crashes next time. I've scanned through the handbook etc, but couldn't find any info. Might have missed it, anyone care to enlighten me? Thanks, /Eirik