From: Matthew Wilcox <willy-8fiUuRrzOP0dnm+yROfE0A@public.gmane.org>
To: Jens Haug <haug-X6ztD3ggwzuBAmxm6OvjtTjhTm2NLCe8@public.gmane.org>
Cc: acpi-devel-pyega4qmqnRoyOMFzWx49A@public.gmane.org
Subject: Re: Invalid PBLK length
Date: Wed, 18 Dec 2002 14:00:19 +0000 [thread overview]
Message-ID: <20021218140019.H9994@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <200212181326.gBIDQ5D08026-sBhUd1W9t4xfrO0PeCDDO4ECbGbo6+O1OOFObY0sJ7w@public.gmane.org>; from haug-X6ztD3ggwzuBAmxm6OvjtTjhTm2NLCe8@public.gmane.org on Wed, Dec 18, 2002 at 02:26:05PM +0100
On Wed, Dec 18, 2002 at 02:26:05PM +0100, Jens Haug wrote:
> I'm trying to find out why C2/C3 and throttling is not supported
> on my Asus L2000D (aka Medion 9688).
>
> In dmesg, acpi tells me about an invalid PBLK length of 5 and
> an unsupoprted address space of 127.
That's two ...
http://sourceforge.net/mailarchive/message.php?msg_id=2138093
OK, the other one's an ASUS too, but seems to be a different model (S1300A).
> BTW, how can I make my FADT human readable? It isn't shown by
> acpidmp, and I'd like to be able to check some values myself.
Use the iasl compiler/decompiler.
BTW, Andy, any chance the precompiled one could be compiled against glibc
2.2 instead of 2.3? Not everybody likes to be quite so bleeding-edge ;-)
> I also see in dmesg that there's an unsupported address space
> of 127 in acpi_processor_get_performance_control because
> reg->space_id != ACPI_ADR_SPACE_SYSTEM_IO. But I don't know
> enough C to understand where this comes from. Could somebody
> please give me a hint?
ACPI tells you which address space a given address is in:
#define ACPI_ADR_SPACE_SYSTEM_MEMORY (ACPI_ADR_SPACE_TYPE) 0
#define ACPI_ADR_SPACE_SYSTEM_IO (ACPI_ADR_SPACE_TYPE) 1
#define ACPI_ADR_SPACE_PCI_CONFIG (ACPI_ADR_SPACE_TYPE) 2
#define ACPI_ADR_SPACE_EC (ACPI_ADR_SPACE_TYPE) 3
#define ACPI_ADR_SPACE_SMBUS (ACPI_ADR_SPACE_TYPE) 4
#define ACPI_ADR_SPACE_CMOS (ACPI_ADR_SPACE_TYPE) 5
#define ACPI_ADR_SPACE_PCI_BAR_TARGET (ACPI_ADR_SPACE_TYPE) 6
#define ACPI_ADR_SPACE_DATA_TABLE (ACPI_ADR_SPACE_TYPE) 7
processor.c is telling you it only handles ioport (inb/outb) address
spaces. But 127 is not a valid address space value, so you're going
to have to get an updated BIOS from your vendor. There's really no
reasonable way to fix this.
On the other hand, I do think it's worth incorporating my suggestion
to fill in C2 if we have it. Maybe under the CONFIG_ACPI_BROKEN_AML or
whatever it was going to be called.
--
"It's not Hollywood. War is real, war is primarily not about defeat or
victory, it is about death. I've seen thousands and thousands of dead bodies.
Do you think I want to have an academic debate on this subject?" -- Robert Fisk
-------------------------------------------------------
This sf.net email is sponsored by:
With Great Power, Comes Great Responsibility
Learn to use your power at OSDN's High Performance Computing Channel
http://hpc.devchannel.org/
next prev parent reply other threads:[~2002-12-18 14:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-18 13:26 Invalid PBLK length Jens Haug
[not found] ` <200212181326.gBIDQ5D08026-sBhUd1W9t4xfrO0PeCDDO4ECbGbo6+O1OOFObY0sJ7w@public.gmane.org>
2002-12-18 14:00 ` Matthew Wilcox [this message]
[not found] ` <20021218140019.H9994-+pPCBgu9SkPzIGdyhVEDUDl5KyyQGfY2kSSpQ9I8OhVaa/9Udqfwiw@public.gmane.org>
2002-12-18 15:32 ` Adachi, Kenichi
-- strict thread matches above, loose matches on Subject: below --
2002-12-18 15:17 Adachi, Kenichi
[not found] ` <4e353e0091944930a0$NiftyInterway-fFkzxiWP14B3+QwDJ9on6Q@public.gmane.org>
2002-12-18 15:29 ` Matthew Wilcox
2002-12-18 15:36 Jens Haug
[not found] ` <200212181536.gBIFabD09402-sBhUd1W9t4xfrO0PeCDDO4ECbGbo6+O1OOFObY0sJ7w@public.gmane.org>
2002-12-18 16:00 ` Ducrot Bruno
2002-12-18 16:08 Jens Haug
2002-12-18 21:28 Grover, Andrew
2002-12-19 8:13 Jens Haug
2003-01-20 23:58 Axel Müller
2003-01-21 8:38 Jens Haug
2003-01-21 22:15 Grover, Andrew
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=20021218140019.H9994@parcelfarce.linux.theplanet.co.uk \
--to=willy-8fiuurrzop0dnm+yrofe0a@public.gmane.org \
--cc=acpi-devel-pyega4qmqnRoyOMFzWx49A@public.gmane.org \
--cc=haug-X6ztD3ggwzuBAmxm6OvjtTjhTm2NLCe8@public.gmane.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.