Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 21 Dec 2012 07:02:26 -0800
From:      Josh Paetzel <josh@tcbug.org>
To:        ipluta@wp.pl
Cc:        freebsd-hardware@freebsd.org
Subject:   Re: Supermicro X9DRD-iF
Message-ID:  <50D47A02.70507@tcbug.org>
In-Reply-To: <50D44E1F.8080404@wp.pl>
References:  <50AA595E.4010302@wp.pl> <935195778.2057818.1353341932216.JavaMail.open-xchange@com4.strato.de> <50D44E1F.8080404@wp.pl>

next in thread | previous in thread | raw e-mail | index | archive | help
On 12/21/2012 03:55, Ireneusz Pluta wrote:
> OK. I got the configuration as advised. The raid controller is MegaRAID
> SAS 9266-4i.
> 
> But 9.0-RELEASE does not seem to boot. It stops with messages like
> (rewritten manually):
> 
> mpt0: <LSILogic SAS/SATA adapter> ... on pci131
> mpt0: soft/hard reset failed: device not running
> mpt0: mpt_reset: failed hard reset (0:0)
> mpt0: mpt_reset: failed hard reset (0:1)
> 
> why the mpt device shows up - is it mfi misrecognized?
> 
> 9.1-RCx (image which is available today) seems to start and reporting:
> 
> mfi0: <ThunderBolt>  ... on pci131
> 
> Why 9.0 has a problem? I initially suspected that mpt was some onboard
> device of the motherboard, but the same pci location in both cases
> indicates that it is just the 9266-4i.
> 
> Is there a way to get 9.0 running? I would like to get the hardware into
> production and I am OK with 9.0 for now, while 9.1 is still RC.
> 
> Thanks
> Irek.
> 

The mpt driver in 9.0 ignores a bit in the PCI ID and decides it should
attach to the megaraid when it shouldn't.  This was fixed in 9.1.

You can make 9.0 work by compiling a kernel that doesn't have the mpt
driver in it.

Thanks,

Josh Paetzel




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