warning if no memory I/O
resources are found.
Signed-off-by: Timothy Pearson
Tested-by: Timothy Pearson
---
drivers/scsi/mpt2sas/mpt2sas_base.c |9 +
1 file changed, 9 insertions(+)
diff --git a/drivers/scsi/mpt2sas/mpt2sas_base.c
b/drivers/scsi/mpt2sas/mpt2sas_base.c
index
On 06/12/2015 05:05 PM, Timothy Pearson wrote:
The mpt2sas driver crashes if the BIOS does not set up at least one
memory I/O resource. This failure can happen if the device is too
slow to respond during POST and is missed by the BIOS, but Linux
then detects the device later in the boot process
On 06/16/2015 12:42 PM, Joe Lawrence wrote:
On 06/16/2015 12:28 PM, Timothy Pearson wrote:
On 06/12/2015 05:05 PM, Timothy Pearson wrote:
The mpt2sas driver crashes if the BIOS does not set up at least one
memory I/O resource. This failure can happen if the device is too
slow to respond during
On 06/16/2015 01:49 PM, Timothy Pearson wrote:
On 06/16/2015 12:42 PM, Joe Lawrence wrote:
On 06/16/2015 12:28 PM, Timothy Pearson wrote:
On 06/12/2015 05:05 PM, Timothy Pearson wrote:
The mpt2sas driver crashes if the BIOS does not set up at least one
memory I/O resource. This failure can
:24 AM, Joe Lawrence wrote:
On 06/21/2015 02:46 PM, Timothy Pearson wrote:
On 06/16/2015 01:49 PM, Timothy Pearson wrote:
On 06/16/2015 12:42 PM, Joe Lawrence wrote:
On 06/16/2015 12:28 PM, Timothy Pearson wrote:
On 06/12/2015 05:05 PM, Timothy Pearson wrote:
The mpt2sas driver crashes if the
On 06/23/2015 12:45 PM, James Bottomley wrote:
On Tue, 2015-06-23 at 12:33 -0500, Timothy Pearson wrote:
On 06/23/2015 08:35 AM, James Bottomley wrote:
On Tue, 2015-06-23 at 18:06 +0530, Sreekanth Reddy wrote:
Hi,
Upstream contributor should not add copyright to this driver code.
I can&#
On 06/23/2015 12:56 PM, James Bottomley wrote:
On Tue, 2015-06-23 at 12:47 -0500, Timothy Pearson wrote:
On 06/23/2015 12:45 PM, James Bottomley wrote:
On Tue, 2015-06-23 at 12:33 -0500, Timothy Pearson wrote:
On 06/23/2015 08:35 AM, James Bottomley wrote:
On Tue, 2015-06-23 at 18:06 +0530
The mpt2sas driver crashes if the BIOS does not set up at least one
memory I/O resource. This failure can happen if the device is too
slow to respond during POST and is missed by the BIOS, but Linux
then detects the device later in the boot process.
Signed-off-by: Timothy Pearson
Tested-by
The mpt3sas driver crashes if the BIOS does not set up at least one
memory I/O resource. This failure can happen if the device is too
slow to respond during POST and is missed by the BIOS, but Linux
then detects the device later in the boot process.
Signed-off-by: Timothy Pearson
---
drivers
On 06/23/2015 02:28 PM, Timothy Pearson wrote:
The mpt2sas driver crashes if the BIOS does not set up at least one
memory I/O resource. This failure can happen if the device is too
slow to respond during POST and is missed by the BIOS, but Linux
then detects the device later in the boot process
nto panic state.
>
>>
>> Thanks
>>
>> Yinghai
On some systems Linux is unable / unwilling to assign a BAR if the BIOS
does not assign one at startup. I didn't look into the Linux allocator
side of things in much detail, but it is quite possible that Linux is
unawa
On 07/15/2015 01:28 PM, Yinghai Lu wrote:
> On Wed, Jul 15, 2015 at 6:52 AM, Timothy Pearson
> wrote:
>>> I have just kept the same description provide by Timothy in his
>>> initial patch.
>>>
>>> But I observe that their may be chance of getting
12 matches
Mail list logo
