From: Martin Peres <martin.peres@linux.intel.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: jeffy.chen@rock-chips.com, "Sarvela,
Tomi P" <tomi.p.sarvela@intel.com>,
linux-kernel@vger.kernel.org
Subject: Re: Suspend-resume failure on Intel Eagle Lake Core2Duo
Date: Mon, 24 Jul 2017 19:37:37 +0300 [thread overview]
Message-ID: <2ecc8ffd-e041-2d53-6f33-e91b3ec701eb@linux.intel.com> (raw)
In-Reply-To: <alpine.DEB.2.20.1707241833270.1988@nanos>
On 24/07/17 19:35, Thomas Gleixner wrote:
> On Mon, 24 Jul 2017, Martin Peres wrote:
>> On 24/07/17 18:28, Thomas Gleixner wrote:
>>> Output of 'cat /proc/interrupts' and a description what kind of 'old' Intel
>>> platform that is.
>>
>> Sorry, I should have repeated the name outside of just the subject of the
>> email. It is an Intel Eagle Lake Core2Duo.
>
> I hoped you would give me a little bit more details, but I Gurgled it
> now. I try to find such a beast and look what's wrong there. If I can't
> find one, I'll come back with some debug patches.
Ha, sorry!
Here is all the info I have:
- Hardware: HP Compaq 8000
- CPU: Eagle Lake Core2Duo E7500
I hope this helps!
Martin
next prev parent reply other threads:[~2017-07-24 16:38 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-24 13:45 Suspend-resume failure on Intel Eagle Lake Core2Duo Martin Peres
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 [this message]
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=2ecc8ffd-e041-2d53-6f33-e91b3ec701eb@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 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.