public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: "Brown, Len" <len.brown@intel.com>
Cc: linux-acpi@vger.kernel.org, linux-scsi@vger.kernel.org, willy@debian.org
Subject: Re: git-acpi breakage, sym2
Date: Fri, 12 May 2006 00:35:18 -0700	[thread overview]
Message-ID: <20060512003518.276420bc.akpm@osdl.org> (raw)
In-Reply-To: <CFF307C98FEABE47A452B27C06B85BB66D5565@hdsmsx411.amr.corp.intel.com>

"Brown, Len" <len.brown@intel.com> wrote:
>
> >The latest
> >git+ssh://master.kernel.org/pub/scm/linux/kernel/git/lenb/linux
> >-acpi-2.6.git#test
> >kills my very vanilla P4 box.
> 
> hmmm, killed my p4 box too in a similar way.
> 
> booting with "acpi=off" made it work,
> so I expect the failures after ACPI refuses to start
> are due to ACPI and not do to something outside ACPI.
> 

Yeah.  Turns out I'm basically unable to drop the acpi tree because I have
so much other stuff dependent upon it.  So it's debugging time.

By the time we get to IO_APIC_get_PCI_irq_vector(), mp_bus_id_to_pci_bus[]
is still all -1's.

Because MP_bus_info() hasn't been called yet.

get_smp_config() is being called, but bales because

	 if (acpi_lapic && acpi_ioapic) {

returns true.

However that all appears to be normal.  Am still poking at it.

git-bisect came up with garbage.

  reply	other threads:[~2006-05-12  7:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-12  7:26 git-acpi breakage, sym2 Brown, Len
2006-05-12  7:35 ` Andrew Morton [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-05-12  6:10 Andrew Morton
2006-05-12 11:23 ` Matthew Wilcox
2006-05-12 11:25   ` Andrew Morton
2006-05-12 11:40     ` Matthew Wilcox

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=20060512003518.276420bc.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=len.brown@intel.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=willy@debian.org \
    /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