From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mika Westerberg Subject: Re: [REGRESSION? v4.8] i2c-core: acpi_i2c_get_info() touches non-existent devices Date: Mon, 19 Sep 2016 11:48:07 +0300 Message-ID: <20160919084807.GC1811@lahna.fi.intel.com> References: <87a8f4kfhe.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <87a8f4kfhe.fsf@gmail.com> Sender: linux-kernel-owner@vger.kernel.org To: Nicolai Stange Cc: Wolfram Sang , Octavian Purdila , "Rafael J. Wysocki" , linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org List-Id: linux-i2c@vger.kernel.org On Mon, Sep 19, 2016 at 12:30:53AM +0200, Nicolai Stange wrote: > Hi, > > I'm encountering the following: > > [ 10.409490] ERROR: Unable to locate IOAPIC for GSI 37 > > Note that the system works fine, so it's a "cosmetic" regression, I think. > > > I added a dump_stack() right below the printk() in question and it reads > as > > [ 10.410290] CPU: 6 PID: 710 Comm: systemd-udevd Not tainted 4.7.0-rc4+ #348 > [ 10.410962] Hardware name: Dell Inc. Latitude E6540/0725FP, BIOS A10 06/26/2014 > [ 10.411772] 0000000000000286 00000000b9050627 ffff8800c2e5f590 ffffffffa54161e7 > [ 10.412569] 0000000000000025 0000000000000001 ffff8800c2e5f5a0 ffffffffa50465df > [ 10.413292] ffff8800c2e5f5d0 ffffffffa5046ffd 0000000000000000 0000000000000025 > [ 10.414016] Call Trace: > [ 10.414713] [] dump_stack+0x68/0xa1 > [ 10.415406] [] mp_find_ioapic+0x4f/0x60 > [ 10.416131] [] mp_map_gsi_to_irq+0x1d/0xc0 > [ 10.416806] [] acpi_register_gsi_ioapic+0x7b/0x170 > [ 10.417494] [] acpi_register_gsi+0xf/0x20 > [ 10.418217] [] acpi_dev_get_irqresource.part.3+0xd7/0x11d > [ 10.418871] [] ? acpi_dev_resource_address_space+0x31/0x67 > [ 10.419655] [] acpi_dev_resource_interrupt+0x9b/0xab > [ 10.420408] [] acpi_dev_process_resource+0xbc/0xf7 > [ 10.421070] [] ? acpi_dev_resource_memory+0x7c/0x7c > [ 10.421732] [] acpi_walk_resource_buffer+0x4d/0x85 > [ 10.422399] [] ? acpi_dev_resource_memory+0x7c/0x7c > [ 10.423158] [] acpi_walk_resources+0x83/0xb6 > [ 10.423831] [] acpi_dev_get_resources+0x96/0xd7 > [ 10.424505] [] acpi_i2c_get_info+0xe4/0x1a0 > [ 10.425181] [] acpi_i2c_add_device+0x56/0xa0 > [ 10.425856] [] acpi_ns_walk_namespace+0xe8/0x19d > [ 10.426564] [] ? acpi_i2c_register_device+0x70/0x70 > [ 10.427418] [] ? acpi_i2c_register_device+0x70/0x70 > [ 10.428179] [] acpi_walk_namespace+0xa0/0xd5 > [ 10.428858] [] i2c_register_adapter+0x369/0x500 > [ 10.429499] [] i2c_add_adapter+0x5c/0x70 > [ 10.430125] [] i801_probe+0x2bd/0x6a0 [i2c_i801] > [ 10.431159] [] ? trace_hardirqs_on+0xd/0x10 > [ 10.432196] [] local_pci_probe+0x42/0xa0 > [ 10.432826] [] ? pci_match_device+0xca/0x110 > [ 10.433460] [] pci_device_probe+0x103/0x150 > [ 10.434083] [] driver_probe_device+0x22c/0x440 > [ 10.434712] [] __driver_attach+0xd5/0x100 > [ 10.435341] [] ? driver_probe_device+0x440/0x440 > [ 10.435963] [] bus_for_each_dev+0x73/0xc0 > [ 10.436676] [] driver_attach+0x1e/0x20 > [ 10.437356] [] bus_add_driver+0x1c6/0x290 > [ 10.437978] [] ? 0xffffffffc07e5000 > [ 10.438699] [] driver_register+0x60/0xe0 > [ 10.439502] [] ? 0xffffffffc07e5000 > [ 10.440310] [] __pci_register_driver+0x5d/0x60 > [ 10.440313] [] i2c_i801_init+0xaf/0x1000 [i2c_i801] > [ 10.440314] [] ? 0xffffffffc07e5000 > [ 10.440316] [] do_one_initcall+0x50/0x180 > [ 10.440319] [] ? rcu_read_lock_sched_held+0x45/0x80 > [ 10.440322] [] ? kmem_cache_alloc_trace+0x2d5/0x340 > [ 10.440325] [] do_init_module+0x5f/0x1da > [ 10.440329] [] load_module+0x2195/0x2950 > [ 10.440331] [] ? __symbol_put+0x70/0x70 > [ 10.440334] [] ? vfs_read+0x11b/0x130 > [ 10.440337] [] SYSC_finit_module+0xe6/0x120 > [ 10.440339] [] SyS_finit_module+0xe/0x10 > [ 10.440340] [] do_syscall_64+0x61/0x170 > [ 10.440343] [] entry_SYSCALL64_slow_path+0x25/0x25 > > > I bisected this to commit 525e6fabeae2 ("i2c / ACPI: add support for > ACPI reconfigure notifications"). > > The reason for the above message seems to be that acpi_i2c_get_info() > configures the IRQs for any ACPI devices that have got some > I2cSerialBus() resource, regardless of the actual adapter those are > attached to. This behaviour is different from before that commit. > > My ACPI DSDT has got a PCI I2C adapter that isn't physically present, it > seems. No clue why. > > That non-existent PCI I2C adapter is in turn I2cSerialBus()-referenced > by some ACPI device that has got exactly this interrupt 37 assigned. > > So it looks like an attempt is made to configure this non-existent, > ACPI-listed I2C slave's IRQs when an actually existing I2C adapter (i801 > SMBus) gets probed. > > > Let me know if I can provide you with any additional information, Can you send me acpidump from that that machine?