From: Timothy Pearson <tpearson@raptorengineeringinc.com>
To: Yinghai Lu <yinghai@kernel.org>
Cc: Sreekanth Reddy <sreekanth.reddy@avagotech.com>,
James Bottomley <jejb@kernel.org>,
martin.petersen@oracle.com,
Linux-Scsi <linux-scsi@vger.kernel.org>,
"James E.J. Bottomley" <JBottomley@parallels.com>,
Sathya.Prakash@avagotech.com,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Christoph Hellwig <hch@infradead.org>,
Bjorn Helgaas <bhelgaas@google.com>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>
Subject: Re: [PATCH v3] [SCSI] mpt2sas, mpt3sas: Abort initialization if no memory I/O resources detected
Date: Wed, 15 Jul 2015 13:46:33 -0500 [thread overview]
Message-ID: <55A6AA89.60202@raptorengineeringinc.com> (raw)
In-Reply-To: <CAE9FiQXtxWHr0j5zFeAS2LxjqwMfecP_aeQDh93CUni+GbQxWw@mail.gmail.com>
On 07/15/2015 01:28 PM, Yinghai Lu wrote:
> On Wed, Jul 15, 2015 at 6:52 AM, Timothy Pearson
> <tpearson@raptorengineeringinc.com> 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 "unable to handle
>>> kernel NULL pointer dereference" kernel panic if no Memory Resource
>>> available in the PCI subsystem. So agreed to the Timothy proposal of
>>> aborting the driver initialization if it doesn't detect any Memory
>>> resource instead of whole system get into panic state.
>>>
>> 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
>> unaware the device only has partial resources assigned.
>>
>
> Would be great if you can post boot log so we can figure about why those
> BARs are not assigned.
>
> Yinghai
Unfortunately the systems exhibiting the issue were upgraded to a later
BIOS that does not have this problem; it might be possible to set up a
test system in the future but that probably won't happen for some time.
--
Timothy Pearson
Raptor Engineering
+1 (415) 727-8645
http://www.raptorengineeringinc.com
next prev parent reply other threads:[~2015-07-15 18:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-15 4:49 Sreekanth Reddy
2015-07-15 5:36 ` Yinghai Lu
2015-07-15 6:24 ` Sreekanth Reddy
2015-07-15 13:52 ` Timothy Pearson
2015-07-15 14:59 ` Bjorn Helgaas
2015-07-15 18:28 ` Yinghai Lu
2015-07-15 18:46 ` Timothy Pearson [this message]
2015-07-15 20:59 ` Bjorn Helgaas
2015-07-27 8:19 ` Hannes Reinecke
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=55A6AA89.60202@raptorengineeringinc.com \
--to=tpearson@raptorengineeringinc.com \
--cc=JBottomley@parallels.com \
--cc=Sathya.Prakash@avagotech.com \
--cc=bhelgaas@google.com \
--cc=hch@infradead.org \
--cc=jejb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=sreekanth.reddy@avagotech.com \
--cc=yinghai@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
Powered by JetHome