From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757699Ab3FGXKV (ORCPT ); Fri, 7 Jun 2013 19:10:21 -0400 Received: from hydra.sisk.pl ([212.160.235.94]:59709 "EHLO hydra.sisk.pl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756680Ab3FGXKS (ORCPT ); Fri, 7 Jun 2013 19:10:18 -0400 From: "Rafael J. Wysocki" To: Tony Luck Cc: Aaron Lu , Linus Torvalds , LKML , Linux PM list , ACPI Devel Maling List Subject: Re: [GIT PULL] Power management and ACPI fixes for v3.10-rc5 Date: Sat, 08 Jun 2013 01:19:23 +0200 Message-ID: <5684767.k0MV6s4nnb@vostro.rjw.lan> User-Agent: KMail/4.9.5 (Linux/3.10.0-rc4+; KDE/4.9.5; x86_64; ; ) In-Reply-To: References: <3863425.93Oeg2bhJF@vostro.rjw.lan> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="utf-8" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Friday, June 07, 2013 04:02:11 PM Tony Luck wrote: > On Fri, Jun 7, 2013 at 3:23 PM, Tony Luck wrote: > > So please don't pull. > > Bother. I see I was a few hours late finding this, and commit 9f29ab11ddb > is already in Linus' tree. > > That's what happens when I get busy and skip a couple of days testing > linux-next :-( > > So my problem comes from > arch/ia64/hp/common/sba_iommu.c > > where the code in sba_init() says: > > acpi_bus_register_driver(&acpi_sba_ioc_driver); > if (!ioc_list) { > > but because of this change we never managed to call ioc_init() > so ioc_list doesn't get set up, and we die. > Before this commit, the call chain looked like this: > > [] ioc_init+0x40/0xd00 > [] acpi_sba_ioc_add+0x190/0x1c0 > [] acpi_device_probe+0xa0/0x280 > [] really_probe+0xe0/0x520 > [] driver_probe_device+0x30/0x60 > [] __driver_attach+0x110/0x160 > [] bus_for_each_dev+0x110/0x180 > [] driver_attach+0x40/0x60 > [] bus_add_driver+0x230/0x580 > [] driver_register+0xf0/0x400 > [] acpi_bus_register_driver+0x50/0x80 > [] sba_init+0x30/0x2d0 > > Is my problem that this driver has (or attaches) a "scan handler" > where it shouldn't ... and I just need to stop it doing that? Looking into that. Thanks, Rafael