[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <499B6BF7.9090300@kernel.org>
Date: Tue, 17 Feb 2009 18:01:27 -0800
From: Yinghai Lu <yinghai@...nel.org>
To: david@...g.hm
CC: Matthew Wilcox <matthew@....cx>,
linux-kernel <linux-kernel@...r.kernel.org>,
linux-scsi@...r.kernel.org, DL-MPTFusionLinux@....com
Subject: Re: mpt fusion broken sometime since 2.6.24
david@...g.hm wrote:
> On Tue, 17 Feb 2009, Yinghai Lu wrote:
>
>> david@...g.hm wrote:
>>> On Tue, 17 Feb 2009, Yinghai Lu wrote:
>>>
>>>> Subject: Re: mpt fusion broken sometime since 2.6.24
>>>>
>>>> On Tue, Feb 17, 2009 at 3:07 PM, <david@...g.hm> wrote:
>>>>> On Tue, 17 Feb 2009, Matthew Wilcox wrote:
>>>>>
>>>>>> On Tue, Feb 17, 2009 at 01:44:55PM -0800, david@...g.hm wrote:
>>>>>>>
>>>>>>> I got a picture of the failed boot at
>>>>>>> http://linux.lang.hm/linux/IMG00052.jpg
>>>>>>
>>>>>> The PCI-MSI line is probably indicative. Can you try booting with:
>>>>>>
>>>>>> mptbase.mpt_msi_enable_sas=0
>>>>>>
>>>>>> and also send us an lspci -v so we can update the blacklist?
>>>>>
>>>>> is that disabling SAS for this system? if so, that's the wrong thing
>>>>> to do
>>>>> (the drives are SAS)
>>>>>
>>>> it only disable MSI with that mptsas.
>>>> and mptsas will use ioapic routing.
>>>>
>>>> can you post whole bootlog?
>>>
>>> unfortunantly it's booting from CD and the only drives in the system are
>>> the ones that are not being accessed.
>>
>> i mean with kernel before 2.6.24..
>
> Ok, attached.
>
so your lsi 1068 is under 8132... need to double check if that chip really support MSI.
YH
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists