All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: "Pasi Kärkkäinen" <pasik@iki.fi>
Cc: David Vrabel <david.vrabel@citrix.com>, xen-devel@lists.xen.org
Subject: Re: Linux 3.4 dom0 kernel error loading xen-acpi-processor: Input/output error
Date: Fri, 15 Mar 2013 17:15:18 -0400	[thread overview]
Message-ID: <20130315211518.GA32252@phenom.dumpdata.com> (raw)
In-Reply-To: <20130315193706.GA8912@reaktio.net>

On Fri, Mar 15, 2013 at 09:37:06PM +0200, Pasi Kärkkäinen wrote:
> On Fri, Mar 15, 2013 at 05:19:34PM +0200, Pasi Kärkkäinen wrote:
> > 
> > > I need to look back at my notes on how the _PCT, _PSS, _Pwhatevername
> > > work.
> > >
> > 
> > Yep. Does xen-acpi-processor driver load OK on your servers? 
> > 
> 
> I just tried Linux 3.8.3 as dom0 on the Xeon 5600 CPU and xen-acpi-processor fails 
> in the same way as it fails with Linux 3.4.
> 
> I also tested on my Ivy Bridge i7 desktop, and there xen-acpi-processor driver loads OK..

And when I add some extra printks in working box I see that these calls:

	acpi_get_handle(pr->handle, "_PCT", &handle);
	acpi_get_handle(pr->handle, "_PSD", &handle);
	acpi_get_handle(pr->handle, "_PSS", &handle);

work, yet in the SSDT and DSDT those strings don't show up? I think this
requires some deep ACPI sorcery to figure out. On the AMD boxes they
nicely show up.

  reply	other threads:[~2013-03-15 21:15 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-21  9:24 Linux 3.4 dom0 kernel error loading xen-acpi-processor: Input/output error Pasi Kärkkäinen
2013-02-21 12:29 ` Konrad Rzeszutek Wilk
2013-02-21 12:42   ` Pasi Kärkkäinen
2013-02-25 17:03     ` Konrad Rzeszutek Wilk
2013-02-25 19:08       ` Pasi Kärkkäinen
2013-02-24 22:05   ` Pasi Kärkkäinen
2013-03-03 18:53     ` Pasi Kärkkäinen
2013-03-05 17:45       ` Konrad Rzeszutek Wilk
2013-03-06 20:41         ` Pasi Kärkkäinen
2013-03-06 21:01           ` Pasi Kärkkäinen
2013-03-06 21:21             ` Pasi Kärkkäinen
2013-03-07  0:29               ` Konrad Rzeszutek Wilk
2013-03-07  7:48                 ` Pasi Kärkkäinen
2013-03-08 20:24                   ` Konrad Rzeszutek Wilk
2013-03-08 22:18                     ` Pasi Kärkkäinen
2013-03-12 20:51                       ` Pasi Kärkkäinen
2013-03-15 15:05                         ` Konrad Rzeszutek Wilk
2013-03-15 15:19                           ` Pasi Kärkkäinen
2013-03-15 19:37                             ` Pasi Kärkkäinen
2013-03-15 21:15                               ` Konrad Rzeszutek Wilk [this message]
2013-03-15 21:32                                 ` Pasi Kärkkäinen
2013-03-17 17:00                                   ` Konrad Rzeszutek Wilk
2013-03-18 13:06                                     ` Konrad Rzeszutek Wilk
2013-03-18 17:02                                       ` Pasi Kärkkäinen
2013-03-18 20:20                                         ` Konrad Rzeszutek Wilk
2013-05-12 16:51                                           ` Pasi Kärkkäinen
2013-05-13 13:46                                             ` Konrad Rzeszutek Wilk
2013-05-13 15:03                                               ` Pasi Kärkkäinen

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=20130315211518.GA32252@phenom.dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=david.vrabel@citrix.com \
    --cc=pasik@iki.fi \
    --cc=xen-devel@lists.xen.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 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.