Linux-NVME Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: keith.busch@intel.com (Keith Busch)
Subject: kernel BUG at nvme/host/pci.c
Date: Mon, 10 Jul 2017 15:08:19 -0400	[thread overview]
Message-ID: <20170710190818.GA13671@localhost.localdomain> (raw)
In-Reply-To: <28fcb21a-35b6-61c1-29e0-9adcc954c98c@pse-consulting.de>

On Mon, Jul 10, 2017@08:03:16PM +0200, Andreas Pflug wrote:
> I'm running a patched (see below) debian 4.9.30 kernel with xen4.8.1 on
> Debian9. Starting a specific virtual machine, very soon the kernel will emit
> 
>     kernel BUG at /usr/src/kernel/linux-4.9.30/drivers/nvme/host/pci.c:495!
> 
> via netconsole to my logging host, and become unstable until hard reset.
> Hardware is dual E5-2620v4 on Supermicro 10DRI-T with two SAMSUNG
> MZQLW960HMJP-00003 NVME disks (mdadm RAID-1) backing the vhds (os on
> separate SSD).
> 
> The bug was reported to debian as https://bugs.debian.org/866511 . According
> to Ben Hutchings' advice, I patched the standard kernel with
> 0001-swiotlb-ensure-that-page-sized-mappings-are-page-ali.patch since its
> description sounded promising, but the bug remains.

The BUG_ON means the nvme driver was given a scatter list that is invalid
for the constraints the NVMe device was registered with. There have been
issues in the past when NVMe is used with stacking devices like RAID,
but I think they are all resolved. Would you happen to know if this
is successful with the 4.12 kernel? If so, I might be able to find the
patch(es) for 4.9-stable, otherwise we'll need to fix it there first.

  reply	other threads:[~2017-07-10 19:08 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-10 18:03 kernel BUG at nvme/host/pci.c Andreas Pflug
2017-07-10 19:08 ` Keith Busch [this message]
2017-07-11  7:44   ` Andreas Pflug
2017-07-11 19:45     ` Keith Busch
2017-07-11 19:44       ` Scott Bauer
2017-07-12  6:06       ` Andreas Pflug
2017-07-12 19:50         ` Keith Busch
2017-07-13  8:46           ` Andreas Pflug
2017-07-13  9:00             ` Sagi Grimberg
2017-07-13 13:47             ` Keith Busch
2017-07-14 16:47               ` Andreas Pflug
2017-07-14 17:08                 ` Keith Busch
2017-07-15  8:51                   ` Christoph Hellwig
2017-07-15 13:34                     ` Andreas Pflug

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=20170710190818.GA13671@localhost.localdomain \
    --to=keith.busch@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