Created attachment 11691 [details]
complete dmesg with the warnings

Created attachment 11692 [details]
acpidump

There is such statement in your DSDT, describing address for cpufreq table.
FFFF means cpufreq feature is turned off in BIOS.
            OperationRegion (STBL, SystemMemory, 0xFFFF0000, 0xFFFF)
Len, I think we should explicitly check for 0xffff length and don't rely on the
fact that this area could not be accessed by memmap.

In case this helps...
The warning I report below:

<4>ACPI Warning (tbfadt-0360): Ignoring BIOS FADT r2 C-state control [20070126]

seems to have gone in 2.6.22 (kernel.org).  

I changed a few .config settings from the openSUSE 10.2 .config.  If you want these details let me know and I'll upload the .config file (don't have it at hand right now)

[/var/log/messages] (partial)

Inspecting /boot/System.map-2.6.21.5-opteron
Loaded 25074 symbols from /boot/System.map-2.6.21.5-opteron.
Symbols match kernel version 2.6.21.
No module symbols loaded - kernel modules not enabled.

klogd 1.4.1, log source = ksyslog started.
<5>Linux version 2.6.21.5-opteron (root@frontend) (gcc version 4.1.2 20061115 (prerelease) (SUSE Linux)) #1 SMP Wed Jun 27 19:06:46 EST 2007
<6>Command line: root=/dev/vg_system/root vga=0x317 resume=/dev/vg_system/swap maxcpus=4 report_lost_ticks mce=bootlog apic=debug
<6>BIOS-provided physical RAM map:
<4> BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
<4> BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
<4> BIOS-e820: 00000000000e8000 - 0000000000100000 (reserved)
<4> BIOS-e820: 0000000000100000 - 00000000bfff0000 (usable)
<4> BIOS-e820: 00000000bfff0000 - 00000000bfffe000 (ACPI data)
<4> BIOS-e820: 00000000bfffe000 - 00000000c0000000 (ACPI NVS)
<4> BIOS-e820: 00000000e0000000 - 00000000f0000000 (reserved)
<4> BIOS-e820: 00000000fec00000 - 00000000fec01000 (reserved)
<4> BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved)
<4> BIOS-e820: 00000000ff700000 - 0000000100000000 (reserved)
<4> BIOS-e820: 0000000100000000 - 0000000238000000 (usable)
<7>Entering add_active_range(0, 0, 159) 0 entries of 3200 used
<7>Entering add_active_range(0, 256, 786416) 1 entries of 3200 used
<7>Entering add_active_range(0, 1048576, 2326528) 2 entries of 3200 used
<4>end_pfn_map = 2326528
<6>DMI 2.3 present.
<4>ACPI: RSDP 000FA1B0, 0014 (r0 ACPIAM)
<4>ACPI: RSDT BFFF0000, 0030 (r1 A M I  OEMRSDT   4000710 MSFT       97)
<4>ACPI: FACP BFFF0200, 0084 (r2 A M I  OEMFACP   4000710 MSFT       97)
<4>ACPI Warning (tbfadt-0360): Ignoring BIOS FADT r2 C-state control [20070126]
<4>ACPI: DSDT BFFF0340, 566B (r1  1HQC8 1HQC8003        3 INTL  2002026)
<4>ACPI: FACS BFFFE000, 0040
<4>ACPI: APIC BFFF0290, 00A4 (r1 A M I  OEMAPIC   4000710 MSFT       97)
<4>ACPI: OEMB BFFFE040, 0081 (r1 A M I  AMI_OEM   4000710 MSFT       97)
<6>Scanning NUMA topology in Northbridge 24
<6>Number of nodes 4
<3>Node 0 using interleaving mode 3/0
<6>No NUMA configuration found
<6>Faking a node at 0000000000000000-0000000238000000
<7>Entering add_active_range(0, 0, 159) 0 entries of 3200 used
<7>Entering add_active_range(0, 256, 786416) 1 entries of 3200 used
<7>Entering add_active_range(0, 1048576, 2326528) 2 entries of 3200 used
<6>Bootmem setup node 0 0000000000000000-0000000238000000
<4>Zone PFN ranges:
<4>  DMA             0 ->     4096
<4>  DMA32        4096 ->  1048576
<4>  Normal    1048576 ->  2326528
<4>early_node_map[3] active PFN ranges
<4>    0:        0 ->      159
<4>    0:      256 ->   786416
<4>    0:  1048576 ->  2326528
<7>On node 0 totalpages: 2064271
<7>  DMA zone: 56 pages used for memmap
<7>  DMA zone: 1171 pages reserved
<7>  DMA zone: 2772 pages, LIFO batch:0
<7>  DMA32 zone: 14280 pages used for memmap
<7>  DMA32 zone: 768040 pages, LIFO batch:31
<7>  Normal zone: 17472 pages used for memmap
<7>  Normal zone: 1260480 pages, LIFO batch:31
<6>Nvidia board detected. Ignoring ACPI timer override.
<6>If you got timer trouble try acpi_use_timer_override
<6>ACPI: PM-Timer IO Port: 0x4008
<7>ACPI: Local APIC address 0xfee00000
<6>ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
<6>Processor #0 (Bootup-CPU)
<6>ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled)
<6>Processor #1
<6>ACPI: LAPIC (acpi_id[0x03] lapic_id[0x02] enabled)
<6>Processor #2
<6>ACPI: LAPIC (acpi_id[0x04] lapic_id[0x03] enabled)
<6>Processor #3
<6>ACPI: LAPIC (acpi_id[0x05] lapic_id[0x84] disabled)
<6>ACPI: LAPIC (acpi_id[0x06] lapic_id[0x85] disabled)
<6>ACPI: LAPIC (acpi_id[0x07] lapic_id[0x86] disabled)
<6>ACPI: LAPIC (acpi_id[0x08] lapic_id[0x87] disabled)
<6>ACPI: IOAPIC (id[0x04] address[0xfec00000] gsi_base[0])
<6>IOAPIC[0]: apic_id 4, address 0xfec00000, GSI 0-23
<6>ACPI: IOAPIC (id[0x09] address[0xdfefe000] gsi_base[40])
<6>IOAPIC[1]: apic_id 9, address 0xdfefe000, GSI 40-46
<6>ACPI: IOAPIC (id[0x0a] address[0xdfeff000] gsi_base[47])
<6>IOAPIC[2]: apic_id 10, address 0xdfeff000, GSI 47-53
<6>ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
<4>ACPI: BIOS IRQ0 pin2 override ignored.
<6>ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
<7>ACPI: IRQ9 used by override.
<6>Setting APIC routing to flat
<6>Using ACPI (MADT) for SMP configuration information
<4>mapped APIC to ffffffffff5fd000 (        fee00000)
<4>mapped IOAPIC to ffffffffff5fc000 (00000000fec00000)
<4>mapped IOAPIC to ffffffffff5fb000 (00000000dfefe000)
<4>mapped IOAPIC to ffffffffff5fa000 (00000000dfeff000)

Is this still an issue?
Please attach the dmesg from a recent kernel, such as 2.6.22.stable.

(In reply to comment #2)
> Created an attachment (id=11692) [details]
> acpidump 
> 
There is such definition in the DSDT, which is uncorrect.
     OperationRegion (STBL, SystemMemory, 0xFFFF0000, 0xFFFF)
The memory regision is reserved for BIOS PROM. 
Please check whether there is the option for CPU frequency in BIOS.
Please attach the dmesg and acpidump from recent stable kernel, such as 2.6.22 and 2.6.23.
Thanks.

Created attachment 12747 [details]
complete dmesg from kernel 2.6.22.4

still warnings there , but computer works fine

Created attachment 12748 [details]
acpidump.out with pmtools-20070511 on kernel-2.6.22.4

well the acpidump.out is equal to the other !

Created attachment 12750 [details]
dmidecode

dmidecode have CPU information , 
I don't understand what you mean with "Please check whether there is the option for CPU frequency in BIOS." !?

Thanks for the info.
But the acpidump has on change. The error still exists.
     OperationRegion (STBL, SystemMemory, 0xFFFF0000, 0xFFFF)
Anyway please dump some info using the follwoing command.
./acpidump --addr 0xffff0000 --length 0xffff -o ssdt2
Thanks.

Created attachment 12823 [details]
root@monteirov:/home/sergio/pmtools-20070511#acpidump/acpidump --addr 0xffff0000 --length 0xffff -o ssdt2

Thanks for your info.
The error info in dmesg is caused by the BIOS bug. 
There are such statements in the DSDT table.
  1.OperationRegion (STBL, SystemMemory, 0xFFFF0000, 0xFFFF)
  2.Method (_PDC, 1, NotSerialized)
            {.....
               If (LEqual (TBLD, 0x00))
                {
                    Load (STBL, HNDL)
                    Store (0x01, TBLD)
                }
            }
The above two statements are uncorrect.
The region from 0xffff0000 to 0xffffffff is reserved for BIOS, which should not be accessed.
The method of PDC will load table from the STBL dynamically.But unforunately there is no valid table in the defined region. So the system reports the error information.

Hi, Sergio,

>OperationRegion (STBL, SystemMemory, 0xFFFF0000, 0xFFFF)
Both the base address(0xFFFF0000) and the length(0xFFFF) of the table
that may contain the CPU p-state support are invalid.

Are there any bios options for cpu p-state control?
If the answer is yes, please make sure they are enabled. :)

Hi welcome, I hope that can help.
Yesterday in home I checked BIOS and just saw CPU Thermal Throttling. which is enabled. Disabling it don't changed nothing. 
Thanks,

Should we report this bug BIOS to asrock ? 

http://www.asrock.com/mb/overview.asp?Model=775Dual-880Pro

Hi, Sergio
From the comment #14 it seems that there is no option for cpu p-state control. The CPU thermal throtting is not for cpu p-state control.
So this is a bios Bug and please report it to asrock.
Thanks.