From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755255Ab3EMWEx (ORCPT ); Mon, 13 May 2013 18:04:53 -0400 Received: from mx1.redhat.com ([209.132.183.28]:63934 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755158Ab3EMWEv (ORCPT ); Mon, 13 May 2013 18:04:51 -0400 Date: Mon, 13 May 2013 18:04:44 -0400 From: Dave Jones To: luto@amacapital.net Cc: Linux Kernel , Fedora Kernel Team Subject: irq remapping warnings on macbook pro. Message-ID: <20130513220444.GA22440@redhat.com> Mail-Followup-To: Dave Jones , luto@amacapital.net, Linux Kernel , Fedora Kernel Team MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Andy, since commit af8d102f999a41c0189bd2cce488bac2ee88c29b, we've had reports from users getting this backtrace.. WARNING: at drivers/iommu/intel_irq_remapping.c:658 intel_enable_irq_remapping+0x295/0x2a4() Hardware name: MacBookPro10,1 Failed to enable irq remapping. You are vulnerable to irq-injection attacks. Modules linked in: Pid: 1, comm: swapper/0 Not tainted 3.9.1-301.fc19.x86_64 #1 Call Trace: [] ? intel_enable_irq_remapping+0x295/0x2a4 [] warn_slowpath_common+0x66/0x80 [] warn_slowpath_fmt+0x4c/0x50 [] intel_enable_irq_remapping+0x295/0x2a4 [] irq_remapping_enable+0x1b/0x7b [] enable_IR+0x59/0x60 [] enable_IR_x2apic+0x8d/0x13f [] default_setup_apic_routing+0x11/0x69 [] native_smp_prepare_cpus+0x2c0/0x3c2 [] kernel_init_freeable+0xba/0x1fa [] ? rest_init+0x80/0x80 [] kernel_init+0xe/0x190 [] ret_from_fork+0x7c/0xb0 [] ? rest_init+0x80/0x80 examples at: https://bugzilla.redhat.com/show_bug.cgi?id=962356 https://bugzilla.redhat.com/show_bug.cgi?id=948262 https://bugzilla.redhat.com/show_bug.cgi?id=954068 Given the unlikelyhood of Apple releasing a firmware fix to appease Linux, can we downgrade this to just a printk ? That would at least stop it getting picked up as a kernel bug by abrt and similar tools. Dave