From: Lukas Hejtmanek <xhejtman@ics.muni.cz>
To: Yinghai Lu <yinghai@kernel.org>
Cc: Roland Dreier <roland@kernel.org>,
linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org
Subject: Re: mellanox mlx4_core and SR-IOV
Date: Wed, 1 Aug 2012 22:28:40 +0200 [thread overview]
Message-ID: <20120801202840.GM5470@ics.muni.cz> (raw)
In-Reply-To: <CAE9FiQUSFeBpGaFByOfENUa8qg7t89WTiUann8=4ezT7s2qmzw@mail.gmail.com>
On Wed, Aug 01, 2012 at 11:29:02AM -0700, Yinghai Lu wrote:
> On Wed, Aug 1, 2012 at 10:37 AM, Roland Dreier <roland@kernel.org> wrote:
> > On Wed, Aug 1, 2012 at 6:38 AM, Lukas Hejtmanek <xhejtman@ics.muni.cz> wrote:
> >> [ 3.558296] mlx4_core 0000:02:00.0: not enough MMIO resources for SR-IOV (nres: 0, iov->nres: 1)
> >
> > This comes from the core sriov_enable() function, not anything in mlx4.
> > (although my kernel doesn't have the print of nres in that message)
> >
> > Not sure what it means.
>
> iov bar is not assigned by BIOS, and kernel can not find range for it too.
>
> Lukas, can you post whole boot log with PCI_DEBUG enabled? That will
> tell exact why kernel does not assign them.
>
> Recent kernel from 3.4... should enable realloc when SRIOV bar is not assigned.
here is full boot log.
http://www.fi.muni.cz/~xhejtman/dmesg.log
weird with PCI_DEBUG it does not load mlx driver at all..
--
Lukáš Hejtmánek
next prev parent reply other threads:[~2012-08-01 20:30 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-01 13:38 Lukas Hejtmanek
2012-08-01 17:37 ` Roland Dreier
2012-08-01 18:29 ` Yinghai Lu
2012-08-01 20:28 ` Lukas Hejtmanek [this message]
2012-08-01 21:27 ` Yinghai Lu
2012-08-01 21:50 ` Lukas Hejtmanek
2012-08-01 20:56 ` Lukas Hejtmanek
2012-08-01 21:32 ` Yinghai Lu
2012-08-01 22:08 ` Lukas Hejtmanek
2012-08-01 23:36 ` Yinghai Lu
2012-08-03 8:33 ` Lukas Hejtmanek
2012-08-03 16:41 ` Yinghai Lu
2012-08-10 18:51 ` Chris Friesen
2012-08-10 22:34 ` Lukas Hejtmanek
2012-08-03 13:49 Konrad Wilk
2012-08-05 8:05 ` Lukas Hejtmanek
2012-08-06 14:07 ` Konrad Rzeszutek Wilk
2012-08-06 15:10 ` Lukas Hejtmanek
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=20120801202840.GM5470@ics.muni.cz \
--to=xhejtman@ics.muni.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=roland@kernel.org \
--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