From owner-freebsd-stable@FreeBSD.ORG Wed May 25 09:19:39 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C0DAB16A41C for ; Wed, 25 May 2005 09:19:39 +0000 (GMT) (envelope-from filip@sdf.lonestar.org) Received: from sdf.lonestar.org (mx.freeshell.org [192.94.73.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7946843D49 for ; Wed, 25 May 2005 09:19:39 +0000 (GMT) (envelope-from filip@sdf.lonestar.org) Received: from sdf.lonestar.org (IDENT:filip@sdf.lonestar.org [192.94.73.1]) by sdf.lonestar.org (8.13.1/8.12.10) with ESMTP id j4P9J0Dh012951; Wed, 25 May 2005 09:19:00 GMT Received: (from filip@localhost) by sdf.lonestar.org (8.13.1/8.12.8/Submit) id j4P9J0vH018419; Wed, 25 May 2005 09:19:00 GMT Date: Wed, 25 May 2005 09:19:00 +0000 (UTC) From: Filip Lenaerts X-X-Sender: filip@sdf.lonestar.org To: Kris Kennaway In-Reply-To: <20050525072122.GA7569@xor.obsecurity.org> Message-ID: References: <20050525072122.GA7569@xor.obsecurity.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-stable@freebsd.org Subject: Re: RELENG_5_4 panic X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 May 2005 09:19:39 -0000 On Wed, 25 May 2005, Kris Kennaway wrote: >> >> i've been experiencing kernel panics for over a year, but the frequency of >> >> it seems like everytime there is a small high cpu usage peak, the system >> panics. im totally unsure what is going on, and hopefully someone can >> problem in the code or probably something else (hardware failure?). > > Sounds exactly like hardware failure to me. It's too bad you waited a > year to investigate this :-) hi all, tnx very much for reply, kris, stefan and thomas. i was also thinking/fearing for a hardware error. the reason why i didn't investigate sooner is that over the past two years i was running 5.0-RC2 and after that followed current. i always assumed that that could be the reason, but when i reverted a month ago to 5.4-RELEASE and now RELENG_5_4 aka stable, the problem stayed ... plus my kernel debugging skills are very limited - hence learned again :) so HW failure. now the only thing to do is convince our IT dep that it is broken and ask a new one. the problem is that they only support windows and they go frantic when they see linux, let alone BSD :) so the probably want to put the blame on the OS iso the HW. wish me luck :) tnx again guys! filip > > Kris ---- http://filip.freeshell.org mailto:filip@freeshell.org ---- SDF Public Access UNIX System - http://sdf.lonestar.org