From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-oi0-f66.google.com ([209.85.218.66]:33124 "EHLO mail-oi0-f66.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752740AbdBMVon (ORCPT ); Mon, 13 Feb 2017 16:44:43 -0500 Received: by mail-oi0-f66.google.com with SMTP id j15so1009038oih.0 for ; Mon, 13 Feb 2017 13:44:43 -0800 (PST) MIME-Version: 1.0 In-Reply-To: References: <20170212211228.iycyl76o4auxk2jy@pd.tnic> <20170213003804.7gt2edclorjlx52p@pd.tnic> <1486953115.5912.4.camel@gmx.de> <20170213204324.mdipw72ueirrkxob@pd.tnic> From: Linus Torvalds Date: Mon, 13 Feb 2017 13:44:42 -0800 Message-ID: Subject: Re: Linux 4.9.6 ( Restore IO-APIC irq_chip retrigger callback , breaks my box ) To: Thomas Gleixner Cc: Borislav Petkov , Steven Rostedt , Gabriel C , Mike Galbraith , Greg Kroah-Hartman , stable , Andrew Morton , Ruslan Ruslichenko , Jiri Slaby Content-Type: text/plain; charset=UTF-8 Sender: stable-owner@vger.kernel.org List-ID: On Mon, Feb 13, 2017 at 1:35 PM, Thomas Gleixner wrote: > > > arch/x86/platform/goldfish/goldfish.c > > static int __init goldfish_init(void) > { > platform_device_register_simple("goldfish_pdev_bus", -1, > goldfish_pdev_bus_resources, 2); > return 0; > } > device_initcall(goldfish_init); > > So it unconditionallyt registers that platform device, which has IRQ 4 as > irq resource and the driver happily matches on the platform devices. > > Wonderful crap, isn't it? It should be made 'depend on BROKEN'. Ugh. Yeah, that's crazy. Random hardcoded interfaces that get enabled by people by mistake. And yeah, it's not just the irq. It just randomly sets up memory addresses too. That thing needs to be disabled some way. Maybe not marked "broken", but there needs to be something that actually enables it at runtime (like a kernel command line option or something like that). That said - that code was presumably enabled before too, so why would this break something? And if this is the cause, we need to figure out what it is that it then triggers.. Linus