public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Lin Ming <ming.m.lin@intel.com>
To: "Luck, Tony" <tony.luck@intel.com>
Cc: Bjorn Helgaas <bjorn.helgaas@hp.com>, Len Brown <lenb@kernel.org>,
	linux-acpi <linux-acpi@vger.kernel.org>
Subject: RE: [PATCH] acpi: fix early DSDT dmi check warnings on ia64
Date: Thu, 06 May 2010 09:58:39 +0800	[thread overview]
Message-ID: <1273111119.9950.41.camel@minggr.sh.intel.com> (raw)
In-Reply-To: <987664A83D2D224EAE907B061CE93D53B91F9656@orsmsx505.amr.corp.intel.com>

On Fri, 2010-04-30 at 06:12 +0800, Luck, Tony wrote:
> >There is not clue in the commit that added this to ia64 as to why
> >dmi_scan_machine() was added as an initcall.  I just tried to move
> >it into setup_arch() - immediately after the efi_init() call as in
> >x86 - and my system hung without printing anything in boot.
> >
> >Agreed this would be a better fix.  I'll see if I can figure out
> >what this call depends on, and so whether I can move is a bit later,
> >but still early enough to be available for Ming's code to work.
> 
> At a random mid-point in setup_arch() I got a lot of errors from
> slub about not being able to allocate memory.  At the very end of
> setup_arch() (after paging_init()) it still failed - with a deref
> NULL inside kmem_alloc().
> 
> So it seems to be non-trivial to just move dmi_scan_machine()
> earlier on ia64 :-(

Sorry for late response, I'm just back from holiday.

Len, 
Can you apply the patch since dmi_available check is needed for ia64?

Thanks,
Lin Ming


  reply	other threads:[~2010-05-06  1:58 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-29  1:42 [PATCH] acpi: fix early DSDT dmi check warnings on ia64 Lin Ming
2010-04-29 14:42 ` Len Brown
2010-04-29 15:56 ` Bjorn Helgaas
2010-04-29 18:12   ` Luck, Tony
2010-04-29 22:12   ` Luck, Tony
2010-05-06  1:58     ` Lin Ming [this message]
2010-05-11  2:09       ` Lin Ming
2010-05-11 23:01         ` Luck, Tony
2010-05-12  1:26           ` Lin Ming
2010-05-20  3:56             ` Len Brown

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=1273111119.9950.41.camel@minggr.sh.intel.com \
    --to=ming.m.lin@intel.com \
    --cc=bjorn.helgaas@hp.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=tony.luck@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