From owner-freebsd-questions@FreeBSD.ORG Thu Feb 28 11:57:23 2008 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C42F0106567B for ; Thu, 28 Feb 2008 11:57:23 +0000 (UTC) (envelope-from kris@FreeBSD.org) Received: from weak.local (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 099E18FC2A; Thu, 28 Feb 2008 11:57:22 +0000 (UTC) (envelope-from kris@FreeBSD.org) Message-ID: <47C6A1A1.6000903@FreeBSD.org> Date: Thu, 28 Feb 2008 12:57:21 +0100 From: Kris Kennaway User-Agent: Thunderbird 2.0.0.12 (Macintosh/20080213) MIME-Version: 1.0 To: Dale Shaw References: <3329cbb40802280321o646e802bk97da4279adb3c525@mail.gmail.com> In-Reply-To: <3329cbb40802280321o646e802bk97da4279adb3c525@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-questions@freebsd.org Subject: Re: FreeBSD 6.0-REL, system lockup, recovers when keyboard pressed X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Feb 2008 11:57:23 -0000 Dale Shaw wrote: > Hi all, > > I'm sorry if this is a FAQ. I searched but couldn't find a direct > match yada yada.. > > I have a vanilla 6.0-RELEASE system running a bunch of network > management type tools like RANCID, nfcapd, cacti and so on. > > After a few days of normal operation, the system (locked away in a > data centre) falls off the network. Can't SSH to it, can't ping it. No > ARP -- gone! I have no OOB access to this machine (it's a test > box/play pen). > > Strangely, when I drive out and visit the machine (a HP DL320) in > person and press enter a couple of times on the keyboard, it springs > back to life like nothing ever happened. I literally see (for example) > log entries dated "Feb 07" immediately followed by entries dated "Feb > 28". Some processes lose the plot and need to be restarted, but others > just continue on their merry way. > > In my searching I have found a couple of references to dodgy keyboard > drivers, problems with systems on KVM switches (like this one is), and > power management issues. > > Any clues? Unfortunately tracking -STABLE is not really an option for > me on this box, but I'm more than happy to update and build a new > kernel on a once-off basis if someone says it's a known bug/problem > sorted out in a post-6.0-RELEASE fix. I have a vague memory of something like this but cannot point to a specific commit that resolved it. Kris