From: Thomas Gleixner <tglx@linutronix.de>
To: Paul Menzel <pmenzel+linux-pci@molgen.mpg.de>
Cc: Bjorn Helgaas <helgaas@kernel.org>,
Bjorn Helgaas <bhelgaas@google.com>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
Marc Zyngier <marc.zyngier@arm.com>
Subject: Re: NULL pointer dereference in msi_set_mask_bit
Date: Thu, 19 Jul 2018 15:48:31 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.21.1807191541130.1602@nanos.tec.linutronix.de> (raw)
In-Reply-To: <ed32c159-1629-68e5-26e2-b1770a43acc3@molgen.mpg.de>
Paul,
On Thu, 19 Jul 2018, Paul Menzel wrote:
> I had to copy the files, and then was able to create an archive with
> non-zero files. Please find the tar archive attached.
Thanks for providing the data. All looks normal there.
Just for clarification. Did this happen exactly once, or did it just not
happen again after you plugged in a serial cable?
One thing you might try is to disable irqbalanced when the machine is up
and then stress the affinity setter mechanism with scripting.
Something like
while true; do
for I in {0..3}; do echo $I > /proc/irq/$IRQ/smp_affinity_list; done
done
might be able to trigger it. But don't ask me which interrupt was involved,
so you have to iterate through the ones which are MSI based.
'cat /proc/interrupt | grep MSI' will tell you.
Thanks,
tglx
next prev parent reply other threads:[~2018-07-19 13:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-18 13:28 Paul Menzel
2018-07-18 14:06 ` Bjorn Helgaas
2018-07-18 15:02 ` Thomas Gleixner
2018-07-18 15:12 ` Paul Menzel
2018-07-18 15:27 ` Marc Zyngier
2018-07-18 15:39 ` Thomas Gleixner
2018-07-18 16:37 ` Paul Menzel
2018-07-18 19:00 ` Thomas Gleixner
2018-07-18 20:05 ` Paul Menzel
2018-07-19 8:55 ` Paul Menzel
2018-07-19 13:48 ` Thomas Gleixner [this message]
2018-07-19 13:56 ` Paul Menzel
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.21.1807191541130.1602@nanos.tec.linutronix.de \
--to=tglx@linutronix.de \
--cc=bhelgaas@google.com \
--cc=helgaas@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=marc.zyngier@arm.com \
--cc=pmenzel+linux-pci@molgen.mpg.de \
/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
all inboxes | Powered by JetHome®