Date: Sun, 30 Jan 2011 15:24:43 +0000 (UTC) From: "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net> To: Damien Fleuriot <ml@my.gd> Cc: freebsd-hackers@freebsd.org, freebsd-stable@freebsd.org Subject: Re: KERN - mfi driver for Dell raid h200 on r210 servers Message-ID: <20110130152315.P39951@maildrop.int.zabbadoz.net> In-Reply-To: <AANLkTikkLXKqPNqJYtSNmqGGAPSav0TwSkwK=Vzt2zz9@mail.gmail.com> References: <AANLkTikfZ_ba4w975Y9pB4inY2xWae2i0253SM=ie-G0@mail.gmail.com> <20110129222400.R39951@maildrop.int.zabbadoz.net> <AANLkTikkLXKqPNqJYtSNmqGGAPSav0TwSkwK=Vzt2zz9@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 30 Jan 2011, Damien Fleuriot wrote:
> Ok I've loaded the newly patched mfi.ko and booted a MFS image.
> Here's the relevant snip from dmesg.run :
> at
> mfi0: <Dell PERC H200 Integrated> port 0xfc00-0xfcff mem
> 0xdf2b0000-0xdf2bffff,0xdf2c0000-0xdf2fffff irq 16 at device 0.0 on
> pci1
> mfi0: Megaraid SAS driver Ver 3.00
> mfi0: firmware stuck in state 0
> mfi0: Firmware not in READY state, error 6
>
>
> I'll have to try mps then, unless someone has an idea about this
> "stuck in state 0" thing.
it means that you should ask Dell for the information as the mfi(4)
driver needs some special handling to support that exact chip.
Probably needs some special initialization and a couple of if ()s, as
usual.
LSI/Dell are the people to talk to.
/bz
--
Bjoern A. Zeeb You have to have visions!
<ks> Going to jail sucks -- <bz> All my daemons like it!
http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/jails.html
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20110130152315.P39951>