From owner-freebsd-current@FreeBSD.ORG Thu Oct 27 01:34:46 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2E69F16A41F for ; Thu, 27 Oct 2005 01:34:46 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7507343D49 for ; Thu, 27 Oct 2005 01:34:44 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.204] ([192.168.254.204]) (authenticated bits=0) by pooker.samsco.org (8.13.4/8.13.4) with ESMTP id j9R1Yhtk090141; Wed, 26 Oct 2005 19:34:43 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <43602EB4.10106@samsco.org> Date: Wed, 26 Oct 2005 19:34:44 -0600 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.8) Gecko/20050615 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Peter Losher References: <200510260029.47683.Peter_Losher@isc.org> In-Reply-To: <200510260029.47683.Peter_Losher@isc.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.4 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on pooker.samsco.org Cc: freebsd-current@freebsd.org Subject: Re: Unhandled Event Notify Frame in mpt driver... X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Oct 2005 01:34:46 -0000 Peter Losher wrote: > Saw this on a freshly installed 6.0-RC1 system that has two onboard > LSILogic SCSI controllers - should I be concerned? > > -=- > mpt0: port 0x3000-0x30ff mem > 0xf3310000-0xf331ffff,0xf3300000-0xf330ffff irq 29 at device 1.0 on > pci14 > mpt0: [GIANT-LOCKED] > mpt0: MPI Version=1.2.12.0 > mpt0: Unhandled Event Notify Frame. Event 0xa. > mpt1: port 0x3400-0x34ff mem > 0xf3330000-0xf333ffff,0xf3320000-0xf332ffff irq 30 at device 1.1 on > pci14 > mpt1: [GIANT-LOCKED] > mpt1: MPI Version=1.2.12.0 > mpt1: Unhandled Event Notify Frame. Event 0xa. > -=- > > Best WIshes - Peter It's ok to ignore it. It's an artifact of the modular nature of the driver and is something that will likely be fixed in the near future. Scott