mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Paul Menzel <pmenzel+linux-pci@molgen.mpg.de>
To: Thomas Gleixner <tglx@linutronix.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:56:09 +0200	[thread overview]
Message-ID: <d8a4e146-4c9f-6849-ef0e-d7382ddd147b@molgen.mpg.de> (raw)
In-Reply-To: <alpine.DEB.2.21.1807191541130.1602@nanos.tec.linutronix.de>

[-- Attachment #1: Type: text/plain, Size: 1414 bytes --]

Dear Thomas,


On 07/19/18 15:48, Thomas Gleixner wrote:

> 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.

Thank you for verifying that.

> Just for clarification. Did this happen exactly once, or did it just not
> happen again after you plugged in a serial cable?

The kernel also panics sometimes when loading the amdgpu module [1]. Before
using the serial console it crashed often, but I do *not* know the reason.

After connecting the serial console, the problem only happened exactly
once.

> 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.

Thank you. I guess I’ll use the machine for some time, and observe if the
problem shows up again.

Thank you very much for your awesome help.


Kind regards,

Paul


[1]: https://bugs.freedesktop.org/show_bug.cgi?id=105684


[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 5174 bytes --]

      reply	other threads:[~2018-07-19 13:56 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
2018-07-19 13:56                   ` Paul Menzel [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=d8a4e146-4c9f-6849-ef0e-d7382ddd147b@molgen.mpg.de \
    --to=pmenzel+linux-pci@molgen.mpg.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=tglx@linutronix.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®