Received-SPF: softfail (google.com: domain of transitioning linux-kernel-owner@vger.kernel.org does not designate 23.128.96.19 as permitted sender) client-ip=23.128.96.19;
Message-ID: <f7ca02c3-c632-7141-02f6-4b2055621e34@siemens.com>
Date:   Fri, 11 Mar 2022 14:11:13 +0100
MIME-Version: 1.0
Subject: Re: [PATCH] scsi: hpsa: prevent hpsa to severly delay boot
Content-Language: en-US
To:     Corentin Labbe <clabbe@baylibre.com>, don.brace@microchip.com,
        jejb@linux.ibm.com, martin.petersen@oracle.com
Cc:     linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org,
        storagedev@microchip.com
References: <20220204131247.1684875-1-clabbe@baylibre.com>
From:   Raphael Lisicki <raphael.lisicki@siemens.com>
In-Reply-To: <20220204131247.1684875-1-clabbe@baylibre.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Feedback-ID: 519:519-7517:519-21489:flowmailer
Precedence: bulk


On 04.02.22 14:12, Corentin Labbe wrote:
> On my HPE Proliant microserver gen 10+, modprobing hpsa lead to:
> hpsa 0000:01:00.7: unrecognized board ID: 0x00e41590
> hpsa 0000:01:00.7: unrecognized board ID: 0x00e41590
> hpsa 0000:01:00.7: can't disable ASPM; OS doesnt't have ASPM control
> hpsa 0000:01:00.7: board not ready, timed ou >
> And the boot is severly delayed until the timeout.

The same happens with ProLiant DL360 Gen10.


> 
> The controller is HPE Smart Array S100i SR Gen10
> 
> I have tried to add (naivly) to struct board_type products:
> 	{0x00e41590, "Smart Array S100i SR Gen10", &SA5_access},
> but the board still time out.
> 
> With further search, I found that the S100i seems to be a fake SW RAID controller usefull for windows only.
> 
> So I use the following patch to fix the boot stuck.


Also confirmed on ProLiant DL360 Gen10 as working, but not sure about 
the general approach.