From owner-freebsd-stable@FreeBSD.ORG Tue Feb 3 22:13:39 2004 Return-Path: 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 4228916A4CF for ; Tue, 3 Feb 2004 22:13:39 -0800 (PST) Received: from butler.cc.tut.fi (butler.cc.tut.fi [130.230.102.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8269C43D3F for ; Tue, 3 Feb 2004 22:13:36 -0800 (PST) (envelope-from mjs@cc.tut.fi) Received: from butler.cc.tut.fi (mjs@localhost [127.0.0.1]) by butler.cc.tut.fi (8.12.10/8.12.5) with ESMTP id i146DZxL018305; Wed, 4 Feb 2004 08:13:35 +0200 (EET) Received: (from mjs@localhost) by butler.cc.tut.fi (8.12.10/8.12.5/Submit) id i146DYxe018302; Wed, 4 Feb 2004 08:13:34 +0200 (EET) X-Authentication-Warning: butler.cc.tut.fi: mjs set sender to mjs@cc.tut.fi using -f To: Doug White References: <20040202144607.V75850@carver.gumbysoft.com> From: Matti Saarinen Date: Wed, 04 Feb 2004 08:13:34 +0200 In-Reply-To: <20040202144607.V75850@carver.gumbysoft.com> (Doug White's message of "Mon, 2 Feb 2004 14:49:51 -0800 (PST)") Message-ID: User-Agent: Gnus/5.1002 (Gnus v5.10.2) Emacs/21.3 (usg-unix-v) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii cc: freebsd-stable@freebsd.org Subject: Re: RELENG_4: Problems with mpt driver X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 04 Feb 2004 06:13:39 -0000 Doug White writes: >> I have IBM x345 which has integrated LSI 1030 raid controller. >> [...] >> mpt0: EvtLogData: Event Data:mpt0: 05020012mpt0: >> mpt0: EvtLogData: IOCLogInfo: 0x110a0000 >> mpt0: EvtLogData: Event Data:mpt0: 05020012mpt0: >> mpt0: EvtLogData: IOCLogInfo: 0x110a0000 > > but it does appear that you have the mpt driver's debugging enabled. > Have you been booting with -v, or have the mpt_debug kernel > environment variable set in loader.conf, or setting something in > sysctl.conf? No, I haven't. I just rebooted the box. I haven't touched any sysctl variables. The problem has been solved and it was hardware related. There was one disk on mpt0 with SCSI ID 3 that was broken. I was possible to write to the disk and also read from it. The problems started when resetting the SCSI bus (which happens when the system boots or goes down, right?). The disk is now replaced and the problem has disappeared. Cheers, -- - Matti -