Re: Warning: pnp 00:0b: can't evaluate _CRS: 12311

From: Bjorn Helgaas
Date: Mon Apr 23 2012 - 18:04:48 EST

On Mon, Apr 23, 2012 at 6:03 AM, Sedat Dilek <sedat.dilek@xxxxxxxxxxxxxx> wrote:
> On Mon, Apr 23, 2012 at 11:48 AM, Sedat Dilek
> <sedat.dilek@xxxxxxxxxxxxxx> wrote:
>> [ Please CC me I am not subscribed to this ML ]
>> Hi,
>> with a self-compiled linux-3.4-rc4 I am seeing this bugs/failures/warnings:
>> [    0.241572] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
>> [    0.279385]  pci0000:00: ACPI _OSC request failed (AE_ERROR),
>> returned control mask: 0x1d
>> [    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
>> The same outputs I have seen also with an unsupported drm-intel-next
>> kernel from Ubuntu/PPA archives [1].
>> What does ist mean? Is it harmless? Buggy firmware/bios?
>> Do you need more background infos (dmesg, kernel-config, etc.)?
>> Regards,
>> - Sedat -
>> [1]
> I have upgraded this Samsung series-5 notebook from BIOS version 05XK
> to 06XK, but the pnp/_CRS warning still remains.

Resource type 0 is "reserved" per the ACPI spec, so this is likely a
BIOS defect. However, we might be able to handle it better than we
currently do.

I would expect all versions of Linux would report this error -- can
you confirm that or identify a version that didn't complain? Also,
can you collect an acpidump (see

In acpi_ut_validate_resource(), we return AE_AML_INVALID_RESOURCE_TYPE
(0x3017 == 12311), which explains the messages you see. The comments
in acpi_ut_walk_aml_resources() suggest that we can't continue because
the length may be bogus if the type is invalid. But I suspect that if
we just treat it as a zero-length descriptor and ignore it, things
will probably work, and that's likely what Windows does.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at