Bug 7286

Summary:	acpi_processor-0742 [00] processor_preregister_: Error while parsing _PSD domain information. Assuming no coordination
Product:	ACPI	Reporter:	Martin Mokrejs (mmokrejs)
Component:	Config-Processors	Assignee:	Venkatesh Pallipadi (venki)
Status:	CLOSED CODE_FIX
Severity:	normal	CC:	acpi-bugzilla
Priority:	P2
Hardware:	i386
OS:	Linux
Kernel Version:	2.6.18	Subsystem:
Regression:	---	Bisected commit-id:
Attachments:	dmesg acpidump dmesg-2.6.20-rc4-git2 config-2.6.20-rc4-git2.gz

Description Martin Mokrejs 2006-10-08 13:57:01 UTC

Most recent kernel where this bug did not occur: 2.6.17.11
Distribution: Gentoo
Hardware Environment: ASUS L3C/S laptop
Software Environment:
Problem Description:

I googled out this has been reported in -mm kernel series, but that was some
kernel panic. I don't get panic, the machine "works" but I have observed this
message in the logs.

acpi_processor-0742 [00] processor_preregister_: Error while parsing _PSD domain
information. Assuming no coordination
acpi-cpufreq: CPU0 - ACPI performance management activated.


Steps to reproduce:

Comment 1 Martin Mokrejs 2006-10-08 13:57:52 UTC

Created attachment 9184 [details]
dmesg

Comment 2 Martin Mokrejs 2006-10-08 13:58:40 UTC

Created attachment 9185 [details]
acpidump

Comment 3 Robert Moore 2006-10-11 10:50:51 UTC

Looks like there is no _PSD in the DSDT, causing this message from 
processor_perflib.c

Probably overkill to emit this message for the no _PSD case?

Comment 4 Venkatesh Pallipadi 2006-10-11 14:33:33 UTC

Yes. This message is a false alarm and should be removed in no _PSD case.

Will send a patch to remove this.

Comment 5 Martin Mokrejs 2006-11-28 09:35:53 UTC

Still appears with linux-2.6.19-rc6-git10

Comment 6 Zhang Rui 2006-12-13 23:16:50 UTC

Hi, Venki
Is it OK to be a ACPI_DB_INFO when no _PSD available?
And others remain the same.
I'll generate a patch after -rc1 comes out :)

Comment 7 Venkatesh Pallipadi 2006-12-14 04:47:59 UTC

Rui,
Just y'day I sent a patch to Len to  remove this message altogether :).

Comment 8 Venkatesh Pallipadi 2007-01-03 18:30:35 UTC

This should be fixed in latest 2.6.20-rc release. Closing.

Comment 9 Martin Mokrejs 2007-01-10 02:05:48 UTC

I still see the message with 2.6.20-rc4-git2. :(

Comment 10 Martin Mokrejs 2007-01-10 02:06:51 UTC

Created attachment 10045 [details]
dmesg-2.6.20-rc4-git2

Comment 11 Martin Mokrejs 2007-01-10 02:11:22 UTC

Created attachment 10046 [details]
config-2.6.20-rc4-git2.gz

Comment 12 Len Brown 2007-01-10 20:06:57 UTC

offending message deleted in acpi-test

Comment 13 Len Brown 2007-03-08 00:56:43 UTC

patch d6637b28ffb38f207015c990e481fde5bba233d7
shipped in linux-2.6.20-rc5

closed.