All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lin Ming <ming.m.lin@intel.com>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: "wallak@free.fr" <wallak@free.fr>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>
Subject: Re: ACPI "_PDC" - acpi_processor_set_pdc()- execution regression - Linux-3.x
Date: Thu, 08 Dec 2011 15:40:57 +0800	[thread overview]
Message-ID: <1323330057.27764.14.camel@minggr> (raw)
In-Reply-To: <CAErSpo7Dcxn7tsecDUXe6AQeRAchsU9tQjL7=-WPpPmDj2OUfw@mail.gmail.com>

On Thu, 2011-12-08 at 13:01 +0800, Bjorn Helgaas wrote:
> [+cc linux-acpi and Lin Ming]
> 
> On Wed, Dec 7, 2011 at 3:38 PM,  <wallak@free.fr> wrote:
> > We have a regression on the ACPI stack of the last linux kernel line 3.x (3.1.4,
> > 3.2-rc4...). The ACPI "_PDC" chunk is not executed on some computers (e.g. Dell
> > X300; the function acpi_processor_set_pdc() is not called). This issue yield to
> > an uninitialized state of some ACPI variables.
> >
> > A patch is available below. This patch come back to the previous linux behavior,
> > and works fine.

Hi, Wallak

Please attach the acpidump output and kernel .config file.
And also the output of "cat /proc/cpuinfo"

(You can send these files to me offline in case they are too big for
mail list)

Thanks,
Lin Ming

> >
> > Best Regards,
> > Wallak.
> >
> > --- linux-3.1.4-mdf/drivers/acpi/processor_core.c.orig  2011-12-07
> > 23:12:57.000000000 +0100
> > +++ linux-3.1.4-mdf/drivers/acpi/processor_core.c       2011-12-07
> > 23:13:39.000000000 +0100
> > @@ -223,8 +223,8 @@
> >        type = (acpi_type == ACPI_TYPE_DEVICE) ? 1 : 0;
> >        cpuid = acpi_get_cpuid(handle, type, acpi_id);
> >
> > -       if (cpuid == -1)
> > -               return false;
> > +       if ((cpuid == -1) && (num_possible_cpus() > 1))
> > +               return false;
> >
> >        return true;
> >  }
> > --
> > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at  http://vger.kernel.org/majordomo-info.html
> > Please read the FAQ at  http://www.tux.org/lkml/



  reply	other threads:[~2011-12-08  7:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-07 22:38 ACPI "_PDC" - acpi_processor_set_pdc()- execution regression - Linux-3.x wallak
2011-12-08  5:01 ` Bjorn Helgaas
2011-12-08  5:01   ` Bjorn Helgaas
2011-12-08  7:40   ` Lin Ming [this message]
     [not found] ` <CAF1ivSZX37HRyxJX_rdkZ4pVrxjCZeM39mAs4ZKcqWCYShxaxQ@mail.gmail.com>
2011-12-12  2:38   ` Lin Ming
2011-12-12 21:59     ` Wallak

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=1323330057.27764.14.camel@minggr \
    --to=ming.m.lin@intel.com \
    --cc=bhelgaas@google.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=wallak@free.fr \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.