From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756433AbdGXP2b (ORCPT ); Mon, 24 Jul 2017 11:28:31 -0400 Received: from Galois.linutronix.de ([146.0.238.70]:37044 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753846AbdGXP2Z (ORCPT ); Mon, 24 Jul 2017 11:28:25 -0400 Date: Mon, 24 Jul 2017 17:28:13 +0200 (CEST) From: Thomas Gleixner To: Martin Peres cc: jeffy.chen@rock-chips.com, "Sarvela, Tomi P" , linux-kernel@vger.kernel.org Subject: Re: Suspend-resume failure on Intel Eagle Lake Core2Duo In-Reply-To: <4d6b511a-61d5-3c5e-a406-9f71d83670b6@linux.intel.com> Message-ID: References: <4d6b511a-61d5-3c5e-a406-9f71d83670b6@linux.intel.com> User-Agent: Alpine 2.20 (DEB 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 24 Jul 2017, Martin Peres wrote: > > 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. Can we please handle this per mail? > Here are the kernel logs[1]. What information would you need? Output of 'cat /proc/interrupts' and a description what kind of 'old' Intel platform that is. Thanks, tglx