Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753015AbbGMTgW (ORCPT ); Mon, 13 Jul 2015 15:36:22 -0400 Received: from youngberry.canonical.com ([91.189.89.112]:53517 "EHLO youngberry.canonical.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752968AbbGMTgV convert rfc822-to-8bit (ORCPT ); Mon, 13 Jul 2015 15:36:21 -0400 Message-ID: <55A4132B.4030801@canonical.com> Date: Mon, 13 Jul 2015 15:36:11 -0400 From: Joseph Salisbury User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: jiang.liu@linux.intel.com CC: konrad.wilk@oracle.com, tony.luck@intel.com, joro@8bytes.org, Greg KH , Benjamin Herrenschmidt , "Rafael J. Wysocki" , Bjorn Helgaas , rdunlap@infradead.org, Yinghai Lu , bp@alien8.de, len.brown@intel.com, pavel@ucw.cz, Thomas Gleixner , LKML , "Rafael J. Wysocki" , pavel@ucw.cz, mingo@redhat.com, hpa@zytor.com, x86@kernel.org, linux-pm@vger.kernel.org Subject: Subject: [v3.19 Regression] x86, irq, acpi: Get rid of special handling of GSI for ACPI SCI Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8BIT Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 876 Lines: 30 Hello Jiang, A kernel bug report was opened against Ubuntu [0]. It was found that reverting the following commit resolves this bug: commit cd68f6bd53cf89d1d5ed889b8af65e9c3574a079 Author: Jiang Liu Date: Mon Oct 27 16:11:52 2014 +0800 x86, irq, acpi: Get rid of special handling of GSI for ACPI SCI The regression was introduced as of v3.19-rc1. I was hoping to get your feedback, since you are the patch author. Do you think gathering any additional data will help diagnose this issue, or would it be best to submit a revert request? Thanks, Joe [0] http://pad.lv/1440072 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/