From: Martin Peres <martin.peres@linux.intel.com>
To: jeffy.chen@rock-chips.com, Thomas Gleixner <tglx@linutronix.de>,
"Sarvela, Tomi P" <tomi.p.sarvela@intel.com>
Cc: linux-kernel@vger.kernel.org
Subject: Suspend-resume failure on Intel Eagle Lake Core2Duo
Date: Mon, 24 Jul 2017 16:45:55 +0300 [thread overview]
Message-ID: <4d6b511a-61d5-3c5e-a406-9f71d83670b6@linux.intel.com> (raw)
Hello,
I am contacting you because your patch "bf22ff45b genirq: Avoid
unnecessary low level irq function calls" broke suspend/resume on an old
Intel platform.
This was not caught in linux-next and only got introduced in linux 4.13-rc1.
Here is the current place where the bug has been reported[0] but I can
move it to bugzilla.kernel.org if you would want that.
Here are the kernel logs[1]. What information would you need?
Thanks in advance,
Martin
[0] https://bugs.freedesktop.org/show_bug.cgi?id=101838
[1]
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_2845/fi-elk-e7500/dmesg-before.log
next reply other threads:[~2017-07-24 13:46 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-24 13:45 Martin Peres [this message]
2017-07-24 15:28 ` Thomas Gleixner
2017-07-24 15:41 ` Martin Peres
2017-07-24 16:35 ` Thomas Gleixner
2017-07-24 16:37 ` Martin Peres
2017-07-25 7:01 ` Tomi Sarvela
2017-07-26 13:47 ` Martin Peres
2017-07-26 14:26 ` Thomas Gleixner
2017-07-27 7:36 ` Tomi Sarvela
2017-07-27 7:42 ` Thomas Gleixner
2017-07-27 8:12 ` Tomi Sarvela
2017-07-27 19:42 ` Thomas Gleixner
2017-07-27 20:13 ` Thomas Gleixner
2017-07-27 21:08 ` Thomas Gleixner
2017-07-28 12:29 ` Tomi Sarvela
2017-07-28 12:42 ` Thomas Gleixner
2017-07-28 13:15 ` Thomas Gleixner
2017-07-28 13:25 ` Tomi Sarvela
2017-07-28 14:13 ` Thomas Gleixner
2017-07-28 14:46 ` Tomi Sarvela
2017-07-28 14:50 ` Thomas Gleixner
2017-07-28 14:55 ` Tomi Sarvela
2017-07-28 16:26 ` Thomas Gleixner
2017-07-31 7:21 ` Tomi Sarvela
2017-07-31 7:45 ` Thomas Gleixner
2017-07-31 7:55 ` Tomi Sarvela
2017-07-31 8:29 ` Thomas Gleixner
2017-07-31 8:41 ` Tomi Sarvela
2017-07-31 14:04 ` Thomas Gleixner
2017-07-31 14:13 ` Tomi Sarvela
2017-07-31 15:06 ` Thomas Gleixner
2017-07-31 15:44 ` Tomi Sarvela
2017-07-31 15:55 ` Thomas Gleixner
2017-08-03 7:32 ` Masahiro Yamada
2017-08-03 8:23 ` Peter Zijlstra
2017-08-03 8:41 ` Marc Zyngier
2017-08-03 12:52 ` Masahiro Yamada
2017-08-03 13:30 ` Marc Zyngier
2017-08-07 4:45 ` Masahiro Yamada
2017-08-07 8:17 ` Marc Zyngier
2017-08-08 1:30 ` Masahiro Yamada
2017-08-08 7:39 ` Marc Zyngier
2017-08-09 4:03 ` Masahiro Yamada
2017-07-31 8:35 ` Thomas Gleixner
2017-07-28 12:34 ` Martin Peres
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=4d6b511a-61d5-3c5e-a406-9f71d83670b6@linux.intel.com \
--to=martin.peres@linux.intel.com \
--cc=jeffy.chen@rock-chips.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=tomi.p.sarvela@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
Powered by JetHome