From: Bjorn Helgaas <bhelgaas@google.com>
To: liaohengquan1986 <liaohengquan1986@163.com>
Cc: Learner Study <learner.study@gmail.com>,
"Mayes, Barrett N" <barrett.n.mayes@intel.com>,
"Busch, Keith" <keith.busch@intel.com>,
linux-nvme <linux-nvme@lists.infradead.org>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>
Subject: Re: Wheather the NVMe driver has been tried on the IBM or Lenovo server?
Date: Tue, 22 Apr 2014 09:57:31 -0600 [thread overview]
Message-ID: <CAErSpo526WATQKU9DZ4YjTTL9ot_1soGnjcs=ipgyqt2XNQ-fA@mail.gmail.com> (raw)
In-Reply-To: <7174f4a8.23ad7.14589360cb2.Coremail.liaohengquan1986@163.com>
On Tue, Apr 22, 2014 at 5:33 AM, liaohengquan1986
<liaohengquan1986@163.com> wrote:
>
> Hi, everyone,
> I want to ask that weather the NVMe driver has been tried on the
> IBM or Lenovo server?
> I use it on IBM(Lenovo) server with suse 11 SP3, but the MSI-X
> irq is always could not be got by cpu(may be it is masked).
> Has anyone got this kind of problem?
I think your original email contained non-plain text, so it won't
appear on the mailing list, and some recipients may auto-discard it as
well. See http://vger.kernel.org/majordomo-info.html
If you can reproduce the problem with an upstream kernel, this is the
right place to debug it. We'd need a complete dmesg log and "lspci
-vv" output to start with.
If the problem only happens with SUSE, then you'd want to work with
SUSE to figure it out.
Bjorn
next prev parent reply other threads:[~2014-04-22 15:57 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-08 23:42 [PATCH 1/2] PCI: Device driver function reset notification Keith Busch
2014-04-08 23:42 ` [PATCH 2/2] NVMe: Implement PCI-e reset notification callback Keith Busch
2014-04-22 1:34 ` Learner Study
2014-04-22 1:57 ` Keith Busch
2014-04-22 2:45 ` Learner
2014-04-22 3:34 ` Learner Study
2014-04-22 5:02 ` Mayes, Barrett N
2014-04-22 10:07 ` Learner Study
[not found] ` <7174f4a8.23ad7.14589360cb2.Coremail.liaohengquan1986@163.com>
2014-04-22 15:57 ` Bjorn Helgaas [this message]
2014-04-22 16:08 ` Wheather the NVMe driver has been tried on the IBM or Lenovo server? Learner Study
2014-04-22 14:22 ` [PATCH 2/2] NVMe: Implement PCI-e reset notification callback Keith Busch
2014-04-22 15:00 ` Learner Study
2014-04-30 22:46 ` [PATCH 1/2] PCI: Device driver function reset notification Bjorn Helgaas
2014-05-01 19:57 ` Keith Busch
2014-05-01 20:10 ` Bjorn Helgaas
2014-05-01 20:20 ` Keith Busch
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='CAErSpo526WATQKU9DZ4YjTTL9ot_1soGnjcs=ipgyqt2XNQ-fA@mail.gmail.com' \
--to=bhelgaas@google.com \
--cc=barrett.n.mayes@intel.com \
--cc=keith.busch@intel.com \
--cc=learner.study@gmail.com \
--cc=liaohengquan1986@163.com \
--cc=linux-nvme@lists.infradead.org \
--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;
as well as URLs for NNTP newsgroup(s).