From: "André-Sebastian Liebe" <andre@lianse.eu>
To: "Nandigama, Nagalakshmi" <Nagalakshmi.Nandigama@lsi.com>
Cc: "Desai, Kashyap" <Kashyap.Desai@lsi.com>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"Thakkar, Vishal" <Vishal.Thakkar@lsi.com>
Subject: Re: [PATCH] mpt2sas: New feature - Fast Load Support - scsi_mod.scan=sync drops drive
Date: Tue, 17 Jan 2012 13:52:21 +0100 [thread overview]
Message-ID: <4F156F05.7010506@lianse.eu> (raw)
In-Reply-To: <A6888A6805518E4EA4AF7072A28264A60481F52CC4@inbmail02.lsi.com>
[-- Attachment #1: Type: text/plain, Size: 3930 bytes --]
Hey Kashyap,
works for me (against 3.2.1).
-andre
On 17.01.2012 10:26, Nandigama, Nagalakshmi wrote:
> Andre,
> Request you to apply the attached patch to 3.2 kernel and test.
>
> Regards,
> Nagalakshmi
>
>
> -----Original Message-----
> From: André-Sebastian Liebe [mailto:andre@lianse.eu]
> Sent: Monday, January 16, 2012 1:36 PM
> To: Desai, Kashyap
> Cc: linux-scsi@vger.kernel.org; Nandigama, Nagalakshmi; Thakkar, Vishal
> Subject: Re: [PATCH] mpt2sas: New feature - Fast Load Support - scsi_mod.scan=sync drops drive
>
> Hi guys,
>
> sorry for the late reply, I haven't had the chance to reboot the system earlier. But here are the logs for both scan types.
>
> -andre
>
> On 12.01.2012 07:30, Desai, Kashyap wrote:
>> Andre,
>>
>> Can you enable mpt2sas driver log level to 0x38c and re-send the
>> driver logs in case of "scsi_mod.scan=sync"
>>
>> You need to pass boot time parameter mpt2sas.logging_level=0x38c
>>
>> ` Kashyap
>>
>>> -----Original Message-----
>>> From: André-Sebastian Liebe [mailto:andre@lianse.eu]
>>> Sent: Wednesday, January 11, 2012 2:17 PM
>>> To: Desai, Kashyap
>>> Cc: linux-scsi@vger.kernel.org
>>> Subject: Re: [PATCH] mpt2sas: New feature - Fast Load Support -
>>> scsi_mod.scan=sync drops drive
>>>
>>> Tanks for your suggestion Kashyap!
>>>
>>> I've tried it out but ran directly into an other problem. With
>>> scsi_mod.scan=sync the hba reported all 4 drives correctly but
>>> dropped one of it instantaneously. So I'm either stuck with kernel
>>> 3.1 and all booting up correctly or using 3.2 and manually mounting
>>> the drives behind the hba and starting the services depending on them thereafter.
>>>
>>> I've attached parts of the kernel log with scsi_mod.sync parameter
>>> set to sync/async
>>>
>>> -andre
>>>
>>>
>>> On 10.01.2012 11:53, Desai, Kashyap wrote:
>>>> There is a some scsi_mod parameter called "scan".
>>>> If you pass those parameter at boot time you can change the behavior.
>>>> (see below description)
>>>>
>>>> scsi_mod.scan= [SCSI] sync (default) scans SCSI busses as they
>>> are
>>>> discovered. Async scans them in kernel threads, allowing
>>> boot to proceed.
>>>> none ignores them, expecting user space to do the scan.
>>>>
>>>> ~ Kashyap
>>>>
>>>>> -----Original Message-----
>>>>> From: linux-scsi-owner@vger.kernel.org [mailto:linux-scsi-
>>>>> owner@vger.kernel.org] On Behalf Of André-Sebastian Liebe
>>>>> Sent: Tuesday, January 10, 2012 2:18 PM
>>>>> To: linux-scsi@vger.kernel.org
>>>>> Subject: Re: [PATCH] mpt2sas: New feature - Fast Load Support
>>>>>
>>>> Hi guys,
>>>>
>>>> I've run into problems with the all new shiny 3.2 kernel. My system
>>>> broke badly as it's depending on some devices which are attached to
>>>> my LSI SAS 2008 hba.
>>>> The mount scripts of my gentoo/openrc setup get triggered right
>>>> after udev has settled. But with the new fast load support udev
>>>> settles before my drives appear to the system, so mount fails for
>>>> all those drives and of cause all subsequent services depending on them.
>>>> Is there any switch to revert back to the old behavior of blocking
>>>> until all ports scans are done?
>>>>
>>>> Thanks in advance
>>>> André-Sebastian Liebe
>>>>
>>>>> --
>>>>> To unsubscribe from this list: send the line "unsubscribe linux-scsi"
>>>>> in the body of a message to majordomo@vger.kernel.org More
>>>>> majordomo info at http://vger.kernel.org/majordomo-info.html
>>>
>>> --
>>> gpg key AA1E1F66 @ gpg-keyserver.de: André-Sebastian Liebe
>>> <andre@lianse.eu> Key fingerprint = 5436 5358 172C EB7D E414 C6DE
>>> 6664 89BF AA1E 1F66
>
>
> --
> gpg key AA1E1F66 @ gpg-keyserver.de: André-Sebastian Liebe <andre@lianse.eu> Key fingerprint = 5436 5358 172C EB7D E414 C6DE 6664 89BF AA1E 1F66
--
gpg key AA1E1F66 @ gpg-keyserver.de: André-Sebastian Liebe <andre@lianse.eu>
Key fingerprint = 5436 5358 172C EB7D E414 C6DE 6664 89BF AA1E 1F66
[-- Attachment #2: mpt2sas_patched.txt.tar.gz --]
[-- Type: application/x-gzip, Size: 21792 bytes --]
prev parent reply other threads:[~2012-01-17 12:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-10 8:48 [PATCH] mpt2sas: New feature - Fast Load Support André-Sebastian Liebe
2012-01-10 10:53 ` Desai, Kashyap
2012-01-11 8:46 ` [PATCH] mpt2sas: New feature - Fast Load Support - scsi_mod.scan=sync drops drive André-Sebastian Liebe
2012-01-12 6:30 ` Desai, Kashyap
2012-01-16 8:06 ` André-Sebastian Liebe
2012-01-17 9:26 ` Nandigama, Nagalakshmi
2012-01-17 12:52 ` André-Sebastian Liebe [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4F156F05.7010506@lianse.eu \
--to=andre@lianse.eu \
--cc=Kashyap.Desai@lsi.com \
--cc=Nagalakshmi.Nandigama@lsi.com \
--cc=Vishal.Thakkar@lsi.com \
--cc=linux-scsi@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox