public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Len Brown <lenb@kernel.org>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: linux-acpi@vger.kernel.org,
	linux-kernel <linux-kernel@vger.kernel.org>,
	linux-pci@vger.kernel.org, "Barnes,
	Jesse" <jesse.barnes@intel.com>,
	Kenji Kaneshige <kaneshige.kenji@jp.fujitsu.com>,
	shaohua.li@intel.com
Subject: Re: ACPI hotplug panic with current git head
Date: Thu, 15 Jan 2009 14:22:35 -0500 (EST)	[thread overview]
Message-ID: <alpine.LFD.2.00.0901151421110.4737@localhost.localdomain> (raw)
In-Reply-To: <1232046108.5966.57.camel@localhost.localdomain>

On Thu, 15 Jan 2009, James Bottomley wrote:

> On Mon, 2009-01-12 at 18:48 -0600, James Bottomley wrote:
> > On Mon, 2009-01-12 at 16:16 -0500, Len Brown wrote:
> > > > This is on an IBM Maia system with the calgary IOMMU enabled. It's a
> > > > fatal boot up panic.
> > > > 
> > > 
> > > James,
> > > A guided bisect...
> > > Please let me know which of these fail
> > > 
> > > a3a798c88a14b35e5d4ca30716dbc9eb9a1ddfe2 is 2.6.29 at ACPI merge
> > > efcb3cf7f00c3c424db012380a8a974c2676a3c8 is 2.6.29 before ACPI merge
> > 
> > Didn't try these (being after the failure)
> > 
> > > ec9f168fcc344d2ffec1c8c822076bf22dab5c33 is 2.6.28 with most ACPI
> > 
> > This is the failing one.
> > 
> > > e8443c358c34f3fe65236e24147ddf0cd0e61b08 is 2.6.28 plus just ACPICA
> > 
> > This one boots fine.
> > 
> > > Please test the "2.6.28+ACPICA" one first.
> > > If it fails, we are close so you can skip the others above
> > > and bisect between that and 2.6.28.
> > 
> > I'll try bisecting between ec9f168fcc344d2ffec1c8c822076bf22dab5c33 and
> > e8443c358c34f3fe65236e24147ddf0cd0e61b08.
> 
> OK, bisection complete.  It's not actually coming from the ACPI tree but
> from the PCI one (appropriate CC's added).
> 
> The commit causing the boot panic is:
> 
> commit e8c331e963c58b83db24b7d0e39e8c07f687dbc6
> Author: Kenji Kaneshige <kaneshige.kenji@jp.fujitsu.com>
> Date:   Wed Dec 17 12:09:12 2008 +0900
> 
>     PCI hotplug: introduce functions for ACPI slot detection
> 
> I'm still not sure why, though

Nothing jumped out at me in the patch.
Does reverting e8c331e963c58b83db24b7d0e39e8c07f687dbc6
make the boot crash go away?

thanks,
Len Brown, Intel Open Source Technology Center

  reply	other threads:[~2009-01-15 19:22 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-10 16:17 ACPI hotplug panic with current git head James Bottomley
2009-01-12 21:16 ` Len Brown
2009-01-13  0:48   ` James Bottomley
2009-01-13  3:40     ` Len Brown
2009-01-15 19:01     ` James Bottomley
2009-01-15 19:22       ` Len Brown [this message]
2009-01-15 19:54         ` James Bottomley
2009-01-15 20:12           ` James Bottomley
2009-01-16  6:07             ` Kenji Kaneshige
2009-01-16 14:19               ` James Bottomley
2009-01-19  1:10                 ` Kenji Kaneshige
2009-01-19  1:23                   ` James Bottomley
2009-01-19  3:11                     ` Kenji Kaneshige
2009-01-21 17:26                       ` James Bottomley
2009-01-26  2:11                         ` Kenji Kaneshige
2009-01-26  6:21                           ` Grant Grundler
2009-01-26 12:27                             ` Kenji Kaneshige
2009-01-28 11:47                           ` Kenji Kaneshige
2009-01-28 11:48                             ` [PATCH 1/8] PCI/ACPI: fix wrong assumption in acpi_pci_get_bridge_handle Kenji Kaneshige
2009-01-28 11:50                             ` [PATCH 2/8] PCI/ACPI: fix wrong assumption in acpi_find_root_bridge_handle Kenji Kaneshige
2009-01-28 11:51                             ` [PATCH 3/8] PCI hotplug: fix wrong assumption in acpi_get_hp_params_from_firmware Kenji Kaneshige
2009-01-28 11:55                             ` [PATCH 4/8] PCI hotplug: fix wrong assumption in acpi_get_hp_hw_control_from_firmware Kenji Kaneshige
2009-01-28 11:56                             ` [PATCH 5/8] PCI: fix wrong assumption in pci_find_upstream_pcie_bridge Kenji Kaneshige
2009-01-28 11:57                             ` [PATCH 6/8] PCI: fix wrong assumption in pci_read_bridge_bases Kenji Kaneshige
2009-01-28 11:58                             ` [PATCH 7/8] PCI: fix wrong assumption in pci_get_interrupt_pin Kenji Kaneshige
2009-01-28 11:59                             ` [PATCH 8/8] PCI: fix wrong assumption in pci_common_swizzle Kenji Kaneshige
2009-01-28 12:05                             ` ACPI hotplug panic with current git head Kenji Kaneshige
2009-02-14  0:30                             ` Jesse Barnes
2009-01-16 20:08               ` Len Brown
2009-01-16 20:22                 ` Jesse Barnes
2009-01-19  1:15                 ` Kenji Kaneshige

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=alpine.LFD.2.00.0901151421110.4737@localhost.localdomain \
    --to=lenb@kernel.org \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=jesse.barnes@intel.com \
    --cc=kaneshige.kenji@jp.fujitsu.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=shaohua.li@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox