From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner+w=401wt.eu-S1755771AbZBQXXW@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1755771AbZBQXXW (ORCPT <rfc822;w@1wt.eu>);
	Tue, 17 Feb 2009 18:23:22 -0500
Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752793AbZBQXXJ
	(ORCPT <rfc822;linux-kernel-outgoing>);
	Tue, 17 Feb 2009 18:23:09 -0500
Received: from hera.kernel.org ([140.211.167.34]:44192 "EHLO hera.kernel.org"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1752874AbZBQXXI (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
	Tue, 17 Feb 2009 18:23:08 -0500
Message-ID: <499B46B2.5040601@kernel.org>
Date: Tue, 17 Feb 2009 15:22:26 -0800
From: Yinghai Lu <yinghai@kernel.org>
User-Agent: Thunderbird 2.0.0.19 (X11/20081227)
MIME-Version: 1.0
To: david@lang.hm
CC: Matthew Wilcox <matthew@wil.cx>,
       linux-kernel <linux-kernel@vger.kernel.org>, linux-scsi@vger.kernel.org,
       DL-MPTFusionLinux@lsi.com
Subject: Re: mpt fusion broken sometime since 2.6.24
References: <alpine.DEB.1.10.0902171419000.26625@asgard.lang.hm>  <alpine.DEB.1.10.0902171343280.26625@asgard.lang.hm>  <20090217230050.GG16841@parisc-linux.org>  <alpine.DEB.1.10.0902171506500.26625@asgard.lang.hm> <86802c440902171511s1abcc0eao560df4b8fcea0e7c@mail.gmail.com> <alpine.DEB.1.10.0902171514120.26625@asgard.lang.hm>
In-Reply-To: <alpine.DEB.1.10.0902171514120.26625@asgard.lang.hm>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

david@lang.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@lang.hm> wrote:
>>> On Tue, 17 Feb 2009, Matthew Wilcox wrote:
>>>
>>>> On Tue, Feb 17, 2009 at 01:44:55PM -0800, david@lang.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..

YH