From: Yinghai Lu <yinghai@kernel.org>
To: "Li, Sibai" <sibai.li@intel.com>
Cc: Jason Gao <pkill.2012@gmail.com>,
"bhelgaas@google.com" <bhelgaas@google.com>,
"Rose, Gregory V" <gregory.v.rose@intel.com>,
"ddutile@redhat.com" <ddutile@redhat.com>,
"Kirsher, Jeffrey T" <jeffrey.t.kirsher@intel.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
netdev <netdev@vger.kernel.org>, kvm <kvm@vger.kernel.org>,
"e1000-devel@lists.sourceforge.net"
<e1000-devel@lists.sourceforge.net>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>
Subject: Re: SR-IOV problem with Intel 82599EB (not enough MMIO resources for SR-IOV)
Date: Tue, 13 Nov 2012 10:29:28 -0800 [thread overview]
Message-ID: <CAE9FiQXTCjpSbAi_DAhQomDo3F1MBECUK48eMnUsyso3a_sayQ@mail.gmail.com> (raw)
In-Reply-To: <A3A921390EAE4044940E99EBF13D97321AE21FBB@FMSMSX104.amr.corp.intel.com>
On Tue, Nov 13, 2012 at 10:25 AM, Li, Sibai <sibai.li@intel.com> wrote:
>
> Never append "pci=realloc" for both kernel 2.6.32.279 and kernel 3.5.0 above.
well, can you both post boot log with "debug ignore_loglevel" ?
prev parent reply other threads:[~2012-11-13 18:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <201211081915083774239@gmail.com>
[not found] ` <509B962C.6070002@gmail.com>
[not found] ` <C5551D9AAB213A418B7FD5E4A6F30A072D565E76@ORSMSX106.amr.corp.intel.com>
[not found] ` <CANmqhJDJXcbUxyt6YD6ktxZCDJ=VqiwhGXP+fLMukQr0o-XwxQ@mail.gmail.com>
2012-11-09 15:26 ` SR-IOV problem with Intel 82599EB (not enough MMIO resources for SR-IOV) Bjorn Helgaas
2012-11-09 16:56 ` Yinghai Lu
2012-11-12 19:46 ` Don Dutile
2012-11-13 13:38 ` Jason Gao
2012-11-13 16:04 ` Li, Sibai
2012-11-13 16:40 ` Don Dutile
2012-11-13 18:16 ` Yinghai Lu
2012-11-13 18:25 ` Li, Sibai
2012-11-13 18:29 ` Yinghai Lu [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=CAE9FiQXTCjpSbAi_DAhQomDo3F1MBECUK48eMnUsyso3a_sayQ@mail.gmail.com \
--to=yinghai@kernel.org \
--cc=bhelgaas@google.com \
--cc=ddutile@redhat.com \
--cc=e1000-devel@lists.sourceforge.net \
--cc=gregory.v.rose@intel.com \
--cc=jeffrey.t.kirsher@intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pkill.2012@gmail.com \
--cc=sibai.li@intel.com \
/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;
as well as URLs for NNTP newsgroup(s).