Linux PCI subsystem development
 help / color / mirror / Atom feed
From: Peio <peio@azkarate.eu>
To: linux-pci@vger.kernel.org
Subject: Re: PCI rescan : can't assign mem [SOLVED]
Date: Fri, 4 Sep 2015 05:32:11 +0000 (UTC)	[thread overview]
Message-ID: <loom.20150904T072156-908@post.gmane.org> (raw)
In-Reply-To: CAErSpo6KYCM99H5J0JvYymNmbn-O1NfVwo4Lp7B=2cXCFQwnOw@mail.gmail.com

Bjorn Helgaas <bhelgaas <at> google.com> writes:

> This is a workaround, not a solution.  It is not safe to use
> "pci=nocrs" in general because it can break things related to resource
> assignment, including hot-add of new devices.
> 
> I haven't looked at the problem in detail, but if the BIOS gives us a
> _CRS with host bridge windows that are too small to accommodate all
> your devices, there's really nothing the kernel can do about it.  You
> just have to regard it as a limitation of that platform.
> 
> Bjorn
> 
I'm sure itsn't a platform limitation, a BIOS issue assigning resources 
instead.

Anyway, It's a closed system, without hot-add or not own devices.

I suspect this workaround is fine to me. 




  reply	other threads:[~2015-09-04  5:32 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-31  7:47 PCI rescan : can't assign mem Peio
2015-08-31 23:21 ` Yinghai Lu
2015-09-01  9:01   ` Peio
2015-09-01 16:57     ` Yinghai Lu
2015-09-02  7:01       ` Peio
2015-09-03  1:03         ` Yinghai Lu
2015-09-03  6:03           ` Peio
2015-09-03  9:45             ` PCI rescan : can't assign mem [SOLVED] Peio
2015-09-03 14:52               ` Bjorn Helgaas
2015-09-04  5:32                 ` Peio [this message]
2015-09-04 15:41                   ` Bjorn Helgaas
2015-09-07  6:32                     ` Peio

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=loom.20150904T072156-908@post.gmane.org \
    --to=peio@azkarate.eu \
    --cc=linux-pci@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