From owner-freebsd-scsi@FreeBSD.ORG Thu Oct 15 12:53:08 2009 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 503A61065784; Thu, 15 Oct 2009 12:53:08 +0000 (UTC) (envelope-from pluknet@gmail.com) Received: from mail-fx0-f222.google.com (mail-fx0-f222.google.com [209.85.220.222]) by mx1.freebsd.org (Postfix) with ESMTP id 6B64B8FC0C; Thu, 15 Oct 2009 12:53:06 +0000 (UTC) Received: by fxm22 with SMTP id 22so1044229fxm.36 for ; Thu, 15 Oct 2009 05:53:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=YsvGJWg7CPQERBef2IBEaYx+2ScJ3dl3rcPkAcLCK+E=; b=msrB7Hcyn0x7C1DgqkSusR4lnvHBqc1kdqZFqPp3Lm/Xf8hoTsBkzKbsRO6OwDgGn9 nfjHDUnXop2uyapRdc8EI8DbQEwy/+EV3ZOdbwE3IvJG4VQCFkGgWkxBHoAUoDvE/FS+ fkw4l+M8Esp9dfCor5ZMrlKYGCiMsVlSYXMf0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=a721UL4s6uAmaVqbOuxJLAMKzMeBmkbTZLMulsWZWxMWnbSA22NGyvQRrPhuu5wOnZ esN6KSvsFVmmB13bHFDbH8pXIMPY9z/kWv6NSq036O4rKfdviPPHa7Zr4nJGsaG98mBL lrMVIyuBQH5VgEJrnRoNd0QfOIlQx61ov6gO4= MIME-Version: 1.0 Received: by 10.204.32.213 with SMTP id e21mr23813bkd.34.1255611184791; Thu, 15 Oct 2009 05:53:04 -0700 (PDT) In-Reply-To: References: Date: Thu, 15 Oct 2009 16:53:04 +0400 Message-ID: From: pluknet To: freebsd-stable , freebsd-scsi Content-Type: text/plain; charset=ISO-8859-1 Cc: Subject: Re: mfi(4) endless loop kernel output on attach X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Oct 2009 12:53:08 -0000 >> >> This is 7.2-R. Seen on IBM x3650M2. >> >> During the boot I get those endless looping kernel messages while on >> mfi(4) attach phase. >> It's getting more odd since 7.2 booted and worked fine on exactly this >> server model >> months ago (on different box though).. Any hints? >> > > After the looked endless loop the kernel eventually finished > the mfi(4) initialization and continued its booting. > Is it expected to do so long initialization? > Replying to myself. As someone pointed out in the private email, that's due to the large log contained on non-volatile memory in the controller. MegaCli -AdpEventLog -GetEventLogInfo -aAll cleaned up 'em all. Sorry for noise. -- wbr, pluknet