All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Keith Busch <keith.busch@intel.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: [BUG 4.15-rc7] IRQ matrix management errors
Date: Mon, 15 Jan 2018 10:13:29 +0100 (CET)	[thread overview]
Message-ID: <alpine.DEB.2.20.1801151012230.1810@nanos> (raw)
In-Reply-To: <20180115030255.GA13921@localhost.localdomain>

On Sun, 14 Jan 2018, Keith Busch wrote:

> I hoped to have a better report before the weekend, but I've run out of
> time and without my machine till next week, so sending what I have and
> praying someone more in the know will have a better clue.
> 
> I've a few NVMe drives and occasionally the IRQ teardown and bring-up
> is failing. Resetting the controllers to re-run interrupt allocation
> results in device interrupts from not occuring at all.
> 
> It appears I need at least 2 NVMe drives for the problem. The NVMe
> driver initializes controllers in parallel, and multiple threads calling
> pci_alloc_irq_vectors and/or pci_free_vectors at about the same time
> seems required to trigger the issue.
> 
> Here are the relavent warnings. I also have trace events from irq_matrix
> and irq_vectors, but from a different run that won't match up to the
> timestamps below, but can send if that's helpful.

The dmesg is not that interesting. The traces definitely are if you can
identify the point where it goes into lala land.

Thanks,

	tglx

  reply	other threads:[~2018-01-15  9:13 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20180115025759.GG13580@localhost.localdomain>
2018-01-15  3:02 ` [BUG 4.15-rc7] IRQ matrix management errors Keith Busch
2018-01-15  9:13   ` Thomas Gleixner [this message]
2018-01-16  6:16     ` Keith Busch
2018-01-16  7:11       ` Keith Busch
2018-01-16 10:33         ` Thomas Gleixner
2018-01-16 11:20           ` Thomas Gleixner
2018-01-16 14:26             ` Keith Busch
2018-01-17  2:25             ` Keith Busch
2018-01-17  7:34               ` Thomas Gleixner
2018-01-17  7:55                 ` Keith Busch
2018-01-17  9:24                   ` Thomas Gleixner
2018-01-17  9:32                     ` Thomas Gleixner
2018-01-17 14:24                       ` Keith Busch
2018-01-17 15:01                         ` Thomas Gleixner
2018-01-18  2:37                           ` Keith Busch
2018-01-18  8:10                             ` Thomas Gleixner
2018-01-18  8:48                               ` Keith Busch
2018-01-18  9:06                                 ` Thomas Gleixner
2018-01-18 10:43                           ` [tip:irq/urgent] irq/matrix: Spread interrupts on allocation tip-bot for Thomas Gleixner
2018-01-17 11:15             ` [tip:x86/urgent] x86/apic/vector: Fix off by one in error path tip-bot for Thomas Gleixner

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=alpine.DEB.2.20.1801151012230.1810@nanos \
    --to=tglx@linutronix.de \
    --cc=keith.busch@intel.com \
    --cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.