mpt fails to find disks on LSILogic 1068

[John Baldwin]

On 3/22/12 7:05 PM, Marius Strobl wrote:
> On Thu, Mar 22, 2012 at 11:09:38PM +0400, Dmitry Sivachenko wrote:
>> On 3/22/12 2:01 PM, Marius Strobl wrote:
>>> On Thu, Mar 22, 2012 at 09:15:52AM +0400, Dmitry Sivachenko wrote:
>>>> Hello!
>>>>
>>>> I have a server with LSILogic 1068-IR Controller with 2 disks connected.
>>>> This system was running FreeBSD-7.3 without a problem and recently I tried
>>>> to upgrade to 9-STABLE (build on 15 of February).
>>>>
>>>> New version of FreeBSD fails to initialize this controller:
>>>>
>>>> mpt0:<LSILogic SAS/SATA Adapter>  port 0xd000-0xd0ff irq 26 at device 3.0
>>>> on pci6
>>>> pcib3: attempting to grow memory window for (0-0xffffffff,0x100000)
>>>>         front candidate range: 0xfdd00000-0xfddfffff
>>>>         back candidate range: 0cfe000000-0xfe0fffff
>>>> pcib7: failed to allocate initial memory window (0-0xffffffff,0x100000)
>>>> mpt0: 0x4000 bytes of rid 0x14 res 3 failed (0, 0xffffffffffffffff).
>>>> mpt0: Unable to memory map registers.
>>>> mpt0: Giving Up.

Can you get a full log from a verbose boot?  The root problem is
probably earlier when mpt's BARs are first examined and probably has to
do with an issue with the decoding windows on pcib7.

>>>> Is it a known problem?
>>>> Any ideas how to fix that?
>>>>
>>> This appaears to be an issue with pci(4) rather than mpt(4). What are
>>> the relevant bits of a verbose 7.3 boot?
>>>
>>> Marius
>>>
>>
>> Here it is:
>>
>> mpt0: <LSILogic SAS/SATA Adapter> port 0xd000-0xd0ff mem 
>> 0xfdefc000-0xfdefffff,0xfdee0000-0xfdeeffff irq 26 at device 3.0 on pci6
>> mpt0: Reserved 0x100 bytes for rid 0x10 type 4 at 0xd000
>> mpt0: Reserved 0x4000 bytes for rid 0x14 type 3 at 0xfdefc000
>> ioapic1: routing intpin 2 (PCI IRQ 26) to vector 51
>> mpt0: [MPSAFE]
>> mpt0: [ITHREAD]
>> mpt0: MPI Version=1.5.16.0
>> mpt0: No Handlers For Any Event Notify Frames. Event 0xa (ACK not required).
>> mpt0: No Handlers For Any Event Notify Frames. Event 0x16 (ACK not 
>> required).
>> mpt0: No Handlers For Any Event Notify Frames. Event 0x16 (ACK not 
>> required).
>> mpt0: No Handlers For Any Event Notify Frames. Event 0x16 (ACK not 
>> required).
>> mpt0: No Handlers For Any Event Notify Frames. Event 0x12 (ACK not 
>> required).
>> mpt0: No Handlers For Any Event Notify Frames. Event 0x16 (ACK not 
>> required).
>> mpt0: No Handlers For Any Event Notify Frames. Event 0x16 (ACK not 
>> required).
>> mpt0: No Handlers For Any Event Notify Frames. Event 0x12 (ACK not 
>> required).
>> mpt0: No Handlers For Any Event Notify Frames. Event 0x16 (ACK not 
>> required).
>> mpt0: No Handlers For Any Event Notify Frames. Event 0x16 (ACK not 
>> required).
>> mpt0: No Handlers For Any Event Notify Frames. Event 0x16 (ACK not 
>> required).
>> mpt0: No Handlers For Any Event Notify Frames. Event 0xf (ACK required).
>> mpt0: No Handlers For Any Event Notify Frames. Event 0xf (ACK required).
>> mpt0: Capabilities: ( RAID-0 RAID-1E RAID-1 )
>> mpt0: 0 Active Volumes (2 Max)
>> mpt0: 0 Hidden Drive Members (14 Max)
>> mpt0: No Handlers For Any Event Notify Frames. Event 0xa (ACK not required).
> 
> John, do you have an idea what could have caused the memory BAR to
> disappear?
> 
> Marius
> 


-- 
John Baldwin