From owner-freebsd-hardware@FreeBSD.ORG Tue Apr 17 19:08:58 2007 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id AB1F016A406 for ; Tue, 17 Apr 2007 19:08:58 +0000 (UTC) (envelope-from viper@fx-services.com) Received: from mamata.fx-services.com (mamata.fx-services.com [217.25.36.100]) by mx1.freebsd.org (Postfix) with ESMTP id 6624D13C465 for ; Tue, 17 Apr 2007 19:08:58 +0000 (UTC) (envelope-from viper@fx-services.com) Received: from 81-231-109-115-no49.tbcn.telia.com ([81.231.109.115] helo=[192.168.2.160]) by mamata.fx-services.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.66 (FreeBSD)) (envelope-from ) id 1Hdt36-000Ck2-AV; Tue, 17 Apr 2007 21:09:09 +0200 Message-ID: <46252A32.2060209@fx-services.com> Date: Tue, 17 Apr 2007 22:12:34 +0200 From: Robin Vley User-Agent: Thunderbird 2.0.0.0pre (X11/20070329) MIME-Version: 1.0 To: "FBSD Hardware" References: <4614F070.2000302@fx-services.com> <200704111013.28425.jhb@freebsd.org> In-Reply-To: <200704111013.28425.jhb@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Antivirus-Scanner: Mail is Virus Free, FXS MailGateway X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - mamata.fx-services.com X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [0 0] / [26 6] X-AntiAbuse: Sender Address Domain - fx-services.com X-Source: X-Source-Args: X-Source-Dir: Cc: Subject: Re: SMP crashes / reboots 5.4 with CPanel X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Apr 2007 19:08:58 -0000 John Baldwin wrote: >> #8 0xc05eee46 in procfs_doprocfile (td=0xc439b900, p=0xc9068830, >> pn=0xc35f3900, sb=0x4, uio=0x0) at /usr/src/sys/fs/procfs/procfs.c:73 >> #9 0xc05f3f5b in pfs_readlink (va=0x4) at pcpu.h:162 > > So a bug in procfs. I would try 6.2. I do know of one procfs/vnode > locking bug fixed in 6.x after 6.2, btw. I'm running 6.2 on a testbed now, see if it stays up. So far 12 days, so not much to say yet. Could it be an idea to comment out pseudofs and procfs from the 5.4 machine? As I understand the handbook, it's not technically needed. I can't find much more on the actuall problem in procfs, I wonder why not more people have had this problem. I found a thread on freebsd-hackers, someone with the same hardware and the same version (well, 5.5 instead of 5.4) who has the same random crashes. He upgraded to 6.1. I'll contact him to check what he found out. Thanks for the tip! -- Robin Vley F/X Services Managed Hosting http://www.fx-services.com