[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.1.10.0902171537260.26625@asgard.lang.hm>
Date: Tue, 17 Feb 2009 15:37:56 -0800 (PST)
From: david@...g.hm
To: Yinghai Lu <yinghai@...nel.org>
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
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.
David Lang
View attachment "lspci-vv" of type "TEXT/PLAIN" (37854 bytes)
View attachment "boot.log" of type "TEXT/PLAIN" (29658 bytes)
Powered by blists - more mailing lists