Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 15 Oct 2009 16:53:04 +0400
From:      pluknet <pluknet@gmail.com>
To:        freebsd-stable <freebsd-stable@freebsd.org>, freebsd-scsi <freebsd-scsi@freebsd.org>
Subject:   Re: mfi(4) endless loop kernel output on attach
Message-ID:  <a31046fc0910150553v6a02993fqd960374f14ae1a90@mail.gmail.com>
In-Reply-To: <a31046fc0910150338l5bab52e2g8627e0dc598dcffe@mail.gmail.com>
References:  <a31046fc0910150251q727ea426jca72be60ed29d513@mail.gmail.com> <a31046fc0910150338l5bab52e2g8627e0dc598dcffe@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
>>
>> 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



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?a31046fc0910150553v6a02993fqd960374f14ae1a90>