From: Thomas Gleixner <tglx@linutronix.de>
To: Maarten Lankhorst <dev@mblankhorst.nl>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@kernel.org>, "H. Peter Anvin" <hpa@zytor.com>,
Borislav Petkov <bp@alien8.de>,
Peter Zijlstra <peterz@infradead.org>,
Jani Nikula <jani.nikula@linux.intel.com>,
Intel Graphics Development <intel-gfx@lists.freedesktop.org>
Subject: Re: [GIT pull] x86 APIC updates for 4.15
Date: Thu, 30 Nov 2017 10:18:10 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.20.1711301005530.1925@nanos> (raw)
In-Reply-To: <7c1dd011-0b7b-7c57-71ed-bfab8a52c888@mblankhorst.nl>
Maarten,
On Wed, 29 Nov 2017, Maarten Lankhorst wrote:
> The changes to interrupts bring down our CI during hibernate, see:
>
> https://bugs.freedesktop.org/show_bug.cgi?id=103712
>
> I created a bug report at https://bugzilla.kernel.org/show_bug.cgi?id=198033
>
> Short reproducer:
>
> Create a swapfile on a snb 2600, attempt to hibernate to it with echo
> disk > /sys/power/state, this will fail in the end, but will go through
> most of the steps.
>
> After the almost complete hibernate, i915 will not receive irqs any more,
> which kills our entire integration testing.
>
> Kernel config is available at
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3402/kernel.config.bz2
> Results with pull request reverted at
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_7333/shards.html
>
> First bad commit:
>
> commit fdba46ffb4c203b6e6794163493fd310f98bb4be (HEAD, refs/bisect/bad)
> Author: Thomas Gleixner <tglx@linutronix.de>
> Date: Wed Sep 13 23:29:27 2017 +0200
>
> x86/apic: Get rid of multi CPU affinity
>
< SNIP >
>
> Could you have a look at it please?
I had a look at it. Do I need to do anything else? :)
Seriously. Can you please do the following:
1) Enable CONFIG_GENERIC_IRQ_DEBUGFS
2) mount debugfs
3) Before suspend collect information from there
cat /sys/kernel/debug/irq/domains/*
and
cat /sys/kernel/debug/irq/irqs/$N
where $N is the interrupt which does not fire anymore
4) suspend/resume
5) Collect the same data as in #3
Thanks,
tglx
next prev parent reply other threads:[~2017-11-30 9:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-13 12:05 Thomas Gleixner
2017-11-29 13:27 ` Maarten Lankhorst
2017-11-30 9:18 ` Thomas Gleixner [this message]
2017-11-30 12:04 ` Maarten Lankhorst
2017-11-30 22:47 ` Thomas Gleixner
2017-12-06 11:13 ` Maarten Lankhorst
2017-12-11 10:02 ` [Intel-gfx] " Daniel Vetter
2017-12-11 10:57 ` Thomas Gleixner
2017-12-11 11:06 ` Thomas Gleixner
2017-12-11 17:31 ` Maarten Lankhorst
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.1711301005530.1925@nanos \
--to=tglx@linutronix.de \
--cc=bp@alien8.de \
--cc=dev@mblankhorst.nl \
--cc=hpa@zytor.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®