lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CA+icZUVHO-7SXq3+qz1Gh3yrWtT+R15iiRG0DCLbcKn2PchVHA@mail.gmail.com>
Date:	Thu, 26 Apr 2012 00:06:39 +0200
From:	Sedat Dilek <sedat.dilek@...glemail.com>
To:	Bjorn Helgaas <bhelgaas@...gle.com>
Cc:	"Moore, Robert" <robert.moore@...el.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 11:57 PM, Bjorn Helgaas <bhelgaas@...gle.com> wrote:
> 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

Here we go:

$ sudo grep . /sys/bus/pnp/devices/*/id
/sys/bus/pnp/devices/00:00/id:PNP0a08
/sys/bus/pnp/devices/00:00/id:PNP0a03
/sys/bus/pnp/devices/00:01/id:PNP0200
/sys/bus/pnp/devices/00:02/id:INT0800
/sys/bus/pnp/devices/00:03/id:PNP0103
/sys/bus/pnp/devices/00:04/id:PNP0c04
/sys/bus/pnp/devices/00:05/id:PNP0c02
/sys/bus/pnp/devices/00:06/id:PNP0b00
/sys/bus/pnp/devices/00:07/id:INT3f0d
/sys/bus/pnp/devices/00:07/id:PNP0c02
/sys/bus/pnp/devices/00:08/id:PNP0303
/sys/bus/pnp/devices/00:09/id:ETD0b00
/sys/bus/pnp/devices/00:09/id:SYN0002
/sys/bus/pnp/devices/00:09/id:PNP0f13
/sys/bus/pnp/devices/00:0a/id:PNP0c02
/sys/bus/pnp/devices/00:0b/id:PNP0c01

- Sedat -
--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ