From owner-freebsd-bugs@FreeBSD.ORG Sun Jun 17 17:58:10 2007 Return-Path: X-Original-To: freebsd-bugs@freebsd.org Delivered-To: freebsd-bugs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 73FCB16A400 for ; Sun, 17 Jun 2007 17:58:10 +0000 (UTC) (envelope-from jnaughto@jnaughton.com) Received: from trooper.jnaughton.com (206-248-137-184.dsl.teksavvy.com [206.248.137.184]) by mx1.freebsd.org (Postfix) with ESMTP id 1E34013C45B for ; Sun, 17 Jun 2007 17:58:09 +0000 (UTC) (envelope-from jnaughto@jnaughton.com) Received: from webmail.jnaughton.com (localhost [127.0.0.1]) by trooper.jnaughton.com (8.13.8/8.13.8) with ESMTP id l5HHrZu3084429; Sun, 17 Jun 2007 13:53:36 -0400 (EDT) (envelope-from jnaughto@jnaughton.com) Received: from 192.168.1.2 (SquirrelMail authenticated user jnaughto) by webmail.jnaughton.com with HTTP; Sun, 17 Jun 2007 13:53:36 -0400 (EDT) Message-ID: <58245.192.168.1.2.1182102816.squirrel@webmail.jnaughton.com> In-Reply-To: <20070617132956.GE32385@egr.msu.edu> References: <59240.192.168.1.2.1182049207.squirrel@webmail.jnaughton.com> <20070617132956.GE32385@egr.msu.edu> Date: Sun, 17 Jun 2007 13:53:36 -0400 (EDT) From: jnaughto@jnaughton.com To: "Adam McDougall" User-Agent: SquirrelMail/1.4.9a MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit Cc: freebsd-bugs@freebsd.org Subject: Re: Freebsd RELENG6 panics X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 17 Jun 2007 17:58:10 -0000 Hi Adam, > I currently have two servers still sitting in DDB incase someone has more > questions about things I could check in DDB. I cannot reproduce it > without putting the servers into production, waiting for crash, then > dealing with lots of unhappy users for the rest of the day. This is the EXACT same problem. I had setup a test bed with the system and I couldn't bring it down even if I wanted to. Yet put it into production and I'm getting reboots (3 times today alone) at random times. While RELENG4 worked like a charm on the exact same hardware for 2 years and is continuing to as we speak on the twin brother system that I have. I ruled out broken hardware issues as I purchased 2 twin systems about 5 years back. I ran 4.11 on one system without any concerns. When I thought I had to migrate to RELENG6 I started the install on the 2nd system. Once the system was up and running the panics started. Both systems hard drives are front loading. So what I did was to shut both systems down take the system that was working fine with RELENG4.11 for the past 2 years, and swap drives. The system that was crashing all the time became rock solid again, and the system that was rock solid, now running RELENG6 starts to exhibit panics.... Both systems exhibit the same problems but work fully fine under 4.11... Cheers Jason Naughton