[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAErSpo7Yj6_QZCSeNKXksiYayV53gkUubVBTnRRu8z1pyWeMQQ@mail.gmail.com>
Date: Wed, 25 Apr 2012 15:57:27 -0600
From: Bjorn Helgaas <bhelgaas@...gle.com>
To: "Moore, Robert" <robert.moore@...el.com>
Cc: "sedat.dilek@...il.com" <sedat.dilek@...il.com>,
"linux-acpi@...r.kernel.org" <linux-acpi@...r.kernel.org>,
Len Brown <lenb@...nel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"Lin, Ming M" <ming.m.lin@...el.com>
Subject: Re: Warning: pnp 00:0b: can't evaluate _CRS: 12311
On Wed, Apr 25, 2012 at 3:39 PM, Moore, Robert <robert.moore@...el.com> wrote:
> This disassembly might make more sense. From the looks of the ASL, several of the address base and length fields are being updated dynamically. I don't see anything that would corrupt a resource descriptor, however.
>
>
> Are we certain that the ACPI Error and pnp messages are directly related to the PNP0C02 device ID?
>
> [ 0.293699] system 00:0a: Plug and Play ACPI device, IDs PNP0c02 (active)
> [ 0.294032] ACPI Error: Invalid/unsupported resource descriptor: Type 0x00 (20120320/utresrc-650)
> [ 0.294037] pnp 00:0b: can't evaluate _CRS: 12311
Oh, I'm sorry, I just wasted your time. I didn't notice the 0a/0b
mismatch. You're right, the _CRS error is on 00:0b, and we don't know
what the path is or the PNP ID for 00:0b.
Sedat, can you run "grep . /sys/bus/pnp/devices/*/id" please? That
will at least show us the PNP ID of device 00:0b.
Bjorn
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists