[DB] BIOS - ACPI - collecte d'infos

Ce qui ne concerne ni le forum ni des problèmes
lecbee
Hankyu
Messages : 17
Inscription : dim. 03 juil. 2011, 17:35

[DB] BIOS - ACPI - collecte d'infos

Message par lecbee »

Bonjour,

Je viens juste de m'inscrire simplement pour faire l'écho d'un post que j'ai initialement envoyé sur le forum de Fedora. En fait cela de rapport avec aucune distribution particulière, cela concerne le problème des BIOS dont vous avez sûrement entendu parler via Phoronix... bref, pour faire simple voici le topo.
***********************
Beaucoup d’entre nous ici on sûrement suivi les "régressions" du noyau Linux qu'a soulevé Phoronix depuis quelques semaines. Je ne vais pas répéter tout ce qu'il a été dit depuis, si ce n'est que les véritables coupables dans toute cette histoire sont les BIOS mal programmés. Pas mal d'informations à ce sujet peuvent être collectés sur linuxfr.org ( https://linuxfr.org/users/zezinho/journ ... ifi%C3%A9e ), sur LWN.net (pour le moment le contenu est uniquement accessible aux personnes ayant souscris ) ( https://lwn.net/Articles/449448/ ) et sûrement ailleurs.

La plupart du temps le BIOS est programmé en assembleur. Comme partout en informatique, il est important d'avoir un BIOS qui respecte des normes, notamment l'ACPI. Les tables ACPI ( http://fr.wikipedia.org/wiki/ACPI#Tables_ACPI ) sont "compilées" (le terme n'est peut-être pas adéquat) avec un compilateur. Plusieurs éditeurs en proposent. Par exemple : Microsoft, Intel, Award, etc. Certains compilateurs semblent être plus à cheval sur les bonnes pratiques, ce qui semble être le cas du compilateur Intel, iasl (Intel ACPI Source Language compiler/decompiler). D'ailleurs, Intel fournit une implémentation ACPI de référence nommée ACPICA ( http://www.acpica.org/ ) qui est intégrée dans Linux. Pour informations, la norme ACPI est co-développée par Intel, Microsoft, Toshiba, HP, Poenix et peut-être d'autres. Ceci dit, cela ne signifie pas qu'ils implémentent eux-mêmes correctement cette norme. Microsoft fait bien partie du W3C et pourtant on voit son support du HTML, CSS, etc.

D'après ce que j'ai pu retenir de ces derniers évènements, c'est que Microsoft (via son compilateur ACPI) laisse passer plus facilement des "erreurs" tout en sachant qu'il saura les traiter ou les contourner dans son OS Windows. Évidemment, cela peut résulter en des BIOS plus ou moins bugués qui pénalisent les autres OS. Les fabricants de cartes mères (de BIOS plus précisément) ont la possibilité d'utiliser le compilateur ACPI de leur choix. Avez-vous déjà constater sur de nombreux sites de constructeurs des logo "XXX recommande Windows". Personnellement je ne trouve pas cela attirant et justement je me pose des questions sur le bon support de Linux. Est-ce que les BIOS sont testés uniquement en conjonction avec Windows ?

C'est pour cela que je souhaite collecter ici (ce même sujet est également posté sur Fedora-fr.org, Debian-fr.org et Ubuntu-fr.org afin de collecter plus d'informations) des informations sur les BIOS : avec quel compilateur les constructeurs ont assemblé leurs tables ACPI. Pour le savoir, c'est très simple :

1ÈRE ÉTAPE
Il faut d'abord installer le paquet "pmtools". Étant donné que je n'ai jamais utilisé ArchLinux, si quelqu'un avait la commande et/ou le nom des programmes exactes :wink:
ensuite :
# acpidump > acpi
# acpixtract -l acpi


Postez le résultat ici, en indiquant votre carte mère (vous pouvez obtenir cette info avec 'dmidecode') et la version du BIOS. Je me chargerais de mettre à jour le tableau ici en première page. J'ai moi-même testé plusieurs cartes mères.

2ÈME ÉTAPE
Intel a fournit un Linux Firmware Kit, disponible en LiveCD (79 Mo) ( http://linuxfirmwarekit.org/download/firmwarekit-r3.iso ). Il suffit de lancer le LiveCD, d'attendre 1 à 2 minutes, et cela vous indique les résultats portant sur différentes thématiques. Vous aurez le nombre de tests "Fail", "Warn" et "Pass". Ce Linux Firmware Kit ne semble plus être développé mais je trouve qu'il permet de ce rendre compte de la bonne programmation des BIOS, et par conséquent d'avoir une idée de la fiabilité des BIOS.

RÉSULTATS
Lorsque la case est vide, c'est que la table n'existe pas.
Lorsqu'il y a marqué '--' c'est que rien n'est indiqué.

Afin d'avoir une mise en forme du tableau correcte je l'ai uploadé sur Google Docs, j'espère que la mise en forme n'est pas trop merdique.
https://spreadsheets.google.com/spreads ... utput=html

* Pour une signification des tables : http://fr.wikipedia.org/wiki/ACPI#Tables_ACPI
* Code des compilateurs :
MSFT : Microsoft
INTL : Intel
GBTU : Gigabyte Technology ?
AWRD : AwardBIOS ?
BG : ?
TASM : Toshiba Assembleur ?

Personnellement, j'aimerais bien avoir un retour d'informations avec des cartes mères Intel, Super Micro et Tyan.

Il est bon de noter également que certaines marques indiquent la compatibilité de leurs cartes pour certains types de systèmes d'exploitations, par exemple :
http://fr.asus.com/Static_WebPage/Compa ... loitation/
http://www.tyan.com/tech/OS_Support_AMDFedora.aspx
http://keynux.com/default_zone/fr/html/Prod_Linux.php
Dernière modification par lecbee le mer. 19 oct. 2011, 19:42, modifié 4 fois.
vgib
Hankyu
Messages : 49
Inscription : mar. 29 janv. 2008, 19:52

Re: [DB] BIOS - ACPI - collecte d'infos

Message par vgib »

Je répond en premier visiblement.

Carte mère MSI P965 Neo

bios:

Code : Tout sélectionner

        Vendor: Phoenix Technologies, LTD
        Version: 6.00 PG
        Release Date: 08/18/2006
Base board information:

Code : Tout sélectionner

Base Board Information
        Manufacturer: MICRO-STAR INTERNATIONAL CO., LTD
        Product Name: MS-7235
        Version: REV:1.1
        Serial Number:  

Code : Tout sélectionner

Signature Length Revision  OemId     OemTableId   OemRevision CompilerId CompilerRevision                                                                                          
                                                                                                                                                                                   
    DSDT   18244     01    "INTELR"  "AWRDACPI"    00001000    "MSFT"     0100000E                                                                                                 
    FACS      64                                                                                                                                                                   
    FACP     116     01    "IntelR"  "AWRDACPI"    42302E31    "AWRD"     00000000                                                                                                 
    MCFG      60     01    "IntelR"  "AWRDACPI"    42302E31    "AWRD"     00000000                                                                                                 
    APIC     132     01    "IntelR"  "AWRDACPI"    42302E31    "AWRD"     00000000                                                                                                 
    SSDT     348     01    "PmRef "  "Cpu0Ist "    00003000    "INTL"     20041203                                                                                                 
    SSDT     753     01    "PmRef "  "CpuPm   "    00003000    "INTL"     20040311                                                                                                 
    RSDT      56     01    "IntelR"  "AWRDACPI"    42302E31    "AWRD"     00000000                                                                                                 
    RSDP                   "IntelR"                                                                                                                                                
                                                                                                                                                                                   
Found 9 ACPI tables [20110225]  
Voilà

VGib
Dernière modification par vgib le dim. 03 juil. 2011, 18:49, modifié 2 fois.
lecbee
Hankyu
Messages : 17
Inscription : dim. 03 juil. 2011, 17:35

Re: [DB] BIOS - ACPI - collecte d'infos

Message par lecbee »

Effectivement tu es rapide ! Je viens juste de lancer le sujet. Chez Ubuntu-fr j'ai lancé le sujet hier et j'ai aucune participation...

Bref, si tu pouvais aussi lancer le Linux Firmware Kit ça serait vraiment cool. Je sais que c'est chiant de devoir télécharger et graver un LiveCD pour ça, mais ce sont vraiment les résultats les plus intéressants.

Sinon, quelle version du BIOS tu as ? (pour avoir un tableau le plus complet possible).
vgib
Hankyu
Messages : 49
Inscription : mar. 29 janv. 2008, 19:52

Re: [DB] BIOS - ACPI - collecte d'infos

Message par vgib »

J'ai édité le premier message pour donner la version du bios. Pour le second test, quand je redémarrerais mon PC :)
Avatar de l’utilisateur
malangot
newbie
Messages : 8
Inscription : lun. 27 juin 2011, 11:19

Re: [DB] BIOS - ACPI - collecte d'infos

Message par malangot »

Mon pc eeepc 1005HAG

Bios :

Code : Tout sélectionner

BIOS Information
	Vendor: American Megatrends Inc.
	Version: 0202   
	Release Date: 10/23/2009

Code : Tout sélectionner

Signature Length Revision  OemId     OemTableId   OemRevision CompilerId CompilerRevision

    DSDT   32883     01    "A1397 "  "A1397000"    00000000    "INTL"     20051117
    FACS      64
    FACP     132     02    "A_M_I_"  "OEMFACP "    10000923    "MSFT"     00000097
    APIC      92     01    "A_M_I_"  "OEMAPIC "    10000923    "MSFT"     00000097
    MCFG      60     01    "A_M_I_"  "OEMMCFG "    10000923    "MSFT"     00000097
    OEMB      97     01    "A_M_I_"  "AMI_OEM "    10000923    "MSFT"     00000097
    HPET      56     01    "A_M_I_"  "OEMHPET "    10000923    "MSFT"     00000097
    SSDT    1264     01    "PmRef "  "CpuPm   "    00003000    "INTL"     20051117
    RSDT      60     01    "A_M_I_"  "OEMRSDT "    10000923    "MSFT"     00000097
    RSDP                   "ACPIAM"

Found 10 ACPI tables [20110225]
----------------------------------------------
Deuxième pc
----------------------------------------------

Carte Mère : A7V600

Code : Tout sélectionner

BIOS Information
	Vendor: Award Software, Inc.
	Version: ASUS A7V600 ACPI BIOS Revision 1006 Beta 004
	Release Date: 10/06/2003

Code : Tout sélectionner

Signature Length Revision  OemId     OemTableId   OemRevision CompilerId CompilerRevision

    DSDT   11343     01    "ASUS  "  "A7V600  "    00001000    "MSFT"     0100000B
    FACS      64
    FACP     116     01    "ASUS  "  "A7V600  "    42302E31    "MSFT"     31313031
    BOOT      40     01    "ASUS  "  "A7V600  "    42302E31    "MSFT"     31313031
    APIC      90     01    "ASUS  "  "A7V600  "    42302E31    "MSFT"     31313031
    RSDT      48     01    "ASUS  "  "A7V600  "    42302E31    "MSFT"     31313031
    RSDP                   "ASUS  "

Found 7 ACPI tables [20110225]

Je ferai le test du livecd plus tard ;)
Dernière modification par malangot le dim. 03 juil. 2011, 18:35, modifié 1 fois.
Blog Personnel : http://www.malangot.fr
lecbee
Hankyu
Messages : 17
Inscription : dim. 03 juil. 2011, 17:35

Re: [DB] BIOS - ACPI - collecte d'infos

Message par lecbee »

vgib a écrit :J'ai édité le premier message pour donner la version du bios.
C'est pas la version exacte de BIOS en fait. Regarde plutôt dans la section "Base Board Information".
vgib a écrit :Pour le second test, quand je redémarrerais mon PC :)
Ça me rassure pas tellement :D
lecbee
Hankyu
Messages : 17
Inscription : dim. 03 juil. 2011, 17:35

Re: [DB] BIOS - ACPI - collecte d'infos

Message par lecbee »

malangot a écrit :Je ferai le test du livecd plus tard ;)
Merci.
C'est mis à jour.
Avatar de l’utilisateur
malangot
newbie
Messages : 8
Inscription : lun. 27 juin 2011, 11:19

Re: [DB] BIOS - ACPI - collecte d'infos

Message par malangot »

Je viens d'éditer pour une A7V600
Blog Personnel : http://www.malangot.fr
vgib
Hankyu
Messages : 49
Inscription : mar. 29 janv. 2008, 19:52

Re: [DB] BIOS - ACPI - collecte d'infos

Message par vgib »

C'est pas la version exacte de BIOS en fait. Regarde plutôt dans la section "Base Board Information".
OK c'est bon.
lecbee
Hankyu
Messages : 17
Inscription : dim. 03 juil. 2011, 17:35

Re: [DB] BIOS - ACPI - collecte d'infos

Message par lecbee »

Mis à jour.
Avatar de l’utilisateur
hansi
Elfe
Messages : 508
Inscription : ven. 08 oct. 2010, 21:11

Re: [DB] BIOS - ACPI - collecte d'infos

Message par hansi »

Salut,

Alors pour un Thinkpad X201 ça donne :

# acpidump > acpi : rien.
# acpixtract -l acpi :

Code : Tout sélectionner

Signature Length Revision  OemId     OemTableId   OemRevision CompilerId CompilerRevision

    DSDT   56857     01    "LENOVO"  "TP-6Q   "    00001340    "MSFT"     03000001
    FACS      64
    FACP     244     04    "LENOVO"  "TP-6Q   "    00001340    "LNVO"     00000001
    SSDT     439     01    "LENOVO"  "TP-6Q   "    00001340    "MSFT"     03000001
    ECDT      82     01    "LENOVO"  "TP-6Q   "    00001340    "LNVO"     00000001
    APIC     132     01    "LENOVO"  "TP-6Q   "    00001340    "LNVO"     00000001
    MCFG      60     01    "LENOVO"  "TP-6Q   "    00001340    "LNVO"     00000001
    HPET      56     01    "LENOVO"  "TP-6Q   "    00001340    "LNVO"     00000001
    ASF!     164     10    "LENOVO"  "TP-6Q   "    00001340    "PTL "     00000001
    SLIC     374     01    "LENOVO"  "TP-6Q   "    00001340    " LTP"     00000000
    BOOT      40     01    "LENOVO"  "TP-6Q   "    00001340    " LTP"     00000001
    SSDT    2139     01    "LENOVO"  "TP-6Q   "    00001340    "INTL"     20050513
    TCPA      50     02    "PTL   "  " CRESTLN"    06040000    " LOH"     00005A52
    DMAR     184     01    "INTEL "  "CP_DALE "    00000001    "INTL"     00000001
    SSDT    2545     01    "PmRef "  "CpuPm   "    00003000    "INTL"     20050513
    SSDT     601     01    "PmRef "  "Cpu0Tst "    00003000    "INTL"     20050513
    SSDT    1183     01    "PmRef "  "ApTst   "    00003000    "INTL"     20050513
    XSDT     156     01    "LENOVO"  "TP-6Q   "    00001340    " LTP"     00000000
    RSDP                   "LENOVO"

Found 19 ACPI tables [20110225]
# dmidecode :

Code : Tout sélectionner

# dmidecode 2.11
SMBIOS 2.6 present.
78 structures occupying 2855 bytes.
Table at 0x000E0010.

Handle 0x0000, DMI type 0, 24 bytes
BIOS Information
	Vendor: LENOVO
	Version: 6QET64WW (1.34 )
	Release Date: 02/24/2011
	Address: 0xE0000
	Runtime Size: 128 kB
	ROM Size: 8192 kB
	Characteristics:
		PCI is supported
		PC Card (PCMCIA) is supported
		PNP is supported
		BIOS is upgradeable
		BIOS shadowing is allowed
		ESCD support is available
		Boot from CD is supported
		Selectable boot is supported
		EDD is supported
		3.5"/720 kB floppy services are supported (int 13h)
		Print screen service is supported (int 5h)
		8042 keyboard services are supported (int 9h)
		Serial services are supported (int 14h)
		Printer services are supported (int 17h)
		CGA/mono video services are supported (int 10h)
		ACPI is supported
		USB legacy is supported
		BIOS boot specification is supported
		Targeted content distribution is supported
	BIOS Revision: 1.52
	Firmware Revision: 1.19

Handle 0x0001, DMI type 1, 27 bytes
System Information
	Manufacturer: LENOVO
	Product Name: 36801B8
	Version: ThinkPad X201
	Serial Number: R9AAC2E
	UUID: A0C081EC-8B13-E011-8D0D-A838201D3BF9
	Wake-up Type: Power Switch
	SKU Number: Not Specified
	Family: ThinkPad X201

Handle 0x0002, DMI type 2, 15 bytes
Base Board Information
	Manufacturer: LENOVO
	Product Name: 36801B8
	Version: Not Available
	Serial Number: 1ZHYX0CS2N7
	Asset Tag: Not Specified
	Features: None
	Location In Chassis: Not Specified
	Chassis Handle: 0xFFFF
	Type: Unknown
	Contained Object Handles: 0

Handle 0x0003, DMI type 3, 21 bytes
Chassis Information
	Manufacturer: LENOVO
	Type: Notebook
	Lock: Not Present
	Version: Not Available
	Serial Number: R9AAC2E
	Asset Tag: 100010205105
	Boot-up State: Unknown
	Power Supply State: Unknown
	Thermal State: Unknown
	Security Status: Unknown
	OEM Information: 0x00000000
	Height: Unspecified
	Number Of Power Cords: Unspecified
	Contained Elements: 0

Handle 0x0004, DMI type 126, 21 bytes
Inactive

Handle 0x0005, DMI type 126, 21 bytes
Inactive

Handle 0x0006, DMI type 4, 42 bytes
Processor Information
	Socket Designation: None
	Type: Central Processor
	Family: Other
	Manufacturer: GenuineIntel
	ID: 55 06 02 00 FF FB EB BF
	Version: Intel(R) Core(TM) i5 CPU       M 560  @ 2.67GHz
	Voltage: 1.3 V
	External Clock: 133 MHz
	Max Speed: 2660 MHz
	Current Speed: 2660 MHz
	Status: Populated, Enabled
	Upgrade: None
	L1 Cache Handle: 0x000A
	L2 Cache Handle: 0x000B
	L3 Cache Handle: 0x000C
	Serial Number: Not Specified
	Asset Tag: Not Specified
	Part Number: Not Specified
	Core Count: 2
	Core Enabled: 2
	Thread Count: 4
	Characteristics: None

Handle 0x0007, DMI type 5, 20 bytes
Memory Controller Information
	Error Detecting Method: None
	Error Correcting Capabilities:
		None
	Supported Interleave: One-way Interleave
	Current Interleave: One-way Interleave
	Maximum Memory Module Size: 4096 MB
	Maximum Total Memory Size: 8192 MB
	Supported Speeds:
		Other
	Supported Memory Types:
		DIMM
		SDRAM
	Memory Module Voltage: 2.9 V
	Associated Memory Slots: 2
		0x0008
		0x0009
	Enabled Error Correcting Capabilities:
		Unknown

Handle 0x0008, DMI type 6, 12 bytes
Memory Module Information
	Socket Designation: DIMM Slot 1
	Bank Connections: 0 1
	Current Speed: 43 ns
	Type: DIMM SDRAM
	Installed Size: 4096 MB (Double-bank Connection)
	Enabled Size: 4096 MB (Double-bank Connection)
	Error Status: OK

Handle 0x0009, DMI type 6, 12 bytes
Memory Module Information
	Socket Designation: DIMM Slot 2
	Bank Connections: 2 3
	Current Speed: 43 ns
	Type: DIMM SDRAM
	Installed Size: 4096 MB (Double-bank Connection)
	Enabled Size: 4096 MB (Double-bank Connection)
	Error Status: OK

Handle 0x000A, DMI type 7, 19 bytes
Cache Information
	Socket Designation: Internal L1 Cache
	Configuration: Enabled, Socketed, Level 1
	Operational Mode: Write Through
	Location: Internal
	Installed Size: 32 kB
	Maximum Size: 32 kB
	Supported SRAM Types:
		Burst
		Pipeline Burst
		Asynchronous
	Installed SRAM Type: Asynchronous
	Speed: Unknown
	Error Correction Type: Single-bit ECC
	System Type: Data
	Associativity: 8-way Set-associative

Handle 0x000B, DMI type 7, 19 bytes
Cache Information
	Socket Designation: Internal L2 Cache
	Configuration: Enabled, Socketed, Level 2
	Operational Mode: Write Through
	Location: Internal
	Installed Size: 256 kB
	Maximum Size: 256 kB
	Supported SRAM Types:
		Burst
		Pipeline Burst
		Asynchronous
	Installed SRAM Type: Burst
	Speed: Unknown
	Error Correction Type: Single-bit ECC
	System Type: Unified
	Associativity: 8-way Set-associative

Handle 0x000C, DMI type 7, 19 bytes
Cache Information
	Socket Designation: Internal L3 Cache
	Configuration: Enabled, Socketed, Level 3
	Operational Mode: Write Back
	Location: Internal
	Installed Size: 3072 kB
	Maximum Size: 8192 kB
	Supported SRAM Types:
		Burst
		Pipeline Burst
		Asynchronous
	Installed SRAM Type: Burst
	Speed: Unknown
	Error Correction Type: Unknown
	System Type: Unknown
	Associativity: Unknown

Handle 0x000D, DMI type 8, 9 bytes
Port Connector Information
	Internal Reference Designator: Not Available
	Internal Connector Type: None
	External Reference Designator: External Monitor
	External Connector Type: DB-15 female
	Port Type: Video Port

Handle 0x000E, DMI type 8, 9 bytes
Port Connector Information
	Internal Reference Designator: Not Available
	Internal Connector Type: None
	External Reference Designator: DisplayPort
	External Connector Type: Other
	Port Type: Video Port

Handle 0x000F, DMI type 126, 9 bytes
Inactive

Handle 0x0010, DMI type 126, 9 bytes
Inactive

Handle 0x0011, DMI type 8, 9 bytes
Port Connector Information
	Internal Reference Designator: Not Available
	Internal Connector Type: None
	External Reference Designator: Headphone/Microphone Combo Jack
	External Connector Type: Mini Jack (headphones)
	Port Type: Audio Port

Handle 0x0012, DMI type 126, 9 bytes
Inactive

Handle 0x0013, DMI type 126, 9 bytes
Inactive

Handle 0x0014, DMI type 8, 9 bytes
Port Connector Information
	Internal Reference Designator: Not Available
	Internal Connector Type: None
	External Reference Designator: Ethernet
	External Connector Type: RJ-45
	Port Type: Network Port

Handle 0x0015, DMI type 8, 9 bytes
Port Connector Information
	Internal Reference Designator: Not Available
	Internal Connector Type: None
	External Reference Designator: Modem
	External Connector Type: RJ-11
	Port Type: Modem Port

Handle 0x0016, DMI type 8, 9 bytes
Port Connector Information
	Internal Reference Designator: Not Available
	Internal Connector Type: None
	External Reference Designator: USB 1
	External Connector Type: Access Bus (USB)
	Port Type: USB

Handle 0x0017, DMI type 8, 9 bytes
Port Connector Information
	Internal Reference Designator: Not Available
	Internal Connector Type: None
	External Reference Designator: USB 2
	External Connector Type: Access Bus (USB)
	Port Type: USB

Handle 0x0018, DMI type 8, 9 bytes
Port Connector Information
	Internal Reference Designator: Not Available
	Internal Connector Type: None
	External Reference Designator: USB 3
	External Connector Type: Access Bus (USB)
	Port Type: USB

Handle 0x0019, DMI type 8, 9 bytes
Port Connector Information
	Internal Reference Designator: Not Available
	Internal Connector Type: None
	External Reference Designator: USB 4
	External Connector Type: Access Bus (USB)
	Port Type: USB

Handle 0x001A, DMI type 126, 9 bytes
Inactive

Handle 0x001B, DMI type 126, 9 bytes
Inactive

Handle 0x001C, DMI type 126, 9 bytes
Inactive

Handle 0x001D, DMI type 126, 9 bytes
Inactive

Handle 0x001E, DMI type 126, 9 bytes
Inactive

Handle 0x001F, DMI type 126, 9 bytes
Inactive

Handle 0x0020, DMI type 8, 9 bytes
Port Connector Information
	Internal Reference Designator: Not Available
	Internal Connector Type: None
	External Reference Designator: IEEE1394
	External Connector Type: IEEE 1394
	Port Type: Firewire (IEEE P1394)

Handle 0x0021, DMI type 8, 9 bytes
Port Connector Information
	Internal Reference Designator: Not Available
	Internal Connector Type: None
	External Reference Designator: eSATA 1
	External Connector Type: SAS/SATA Plug Receptacle
	Port Type: SATA

Handle 0x0022, DMI type 126, 9 bytes
Inactive

Handle 0x0023, DMI type 9, 17 bytes
System Slot Information
	Designation: ExpressCard Slot
	Type: x1 PCI Express
	Current Usage: Available
	Length: Other
	ID: 0
	Characteristics:
		Hot-plug devices are supported
	Bus Address: 00ff:ff:1f.7

Handle 0x0024, DMI type 126, 17 bytes
Inactive

Handle 0x0025, DMI type 9, 17 bytes
System Slot Information
	Designation: SmartCard Slot
	Type: Other
	Current Usage: Available
	Length: Other
	Characteristics:
		Hot-plug devices are supported
	Bus Address: 00ff:ff:1f.7

Handle 0x0026, DMI type 10, 6 bytes
On Board Device Information
	Type: Other
	Status: Enabled
	Description: IBM Embedded Security hardware

Handle 0x0027, DMI type 11, 5 bytes
OEM Strings
	String 1: IBM ThinkPad Embedded Controller -[6QHT32WW-1.13    ]-

Handle 0x0028, DMI type 13, 22 bytes
BIOS Language Information
	Language Description Format: Abbreviated
	Installable Languages: 1
		enUS
	Currently Installed Language: enUS

Handle 0x0029, DMI type 15, 25 bytes
System Event Log
	Area Length: 0 bytes
	Header Start Offset: 0x0000
	Header Length: 16 bytes
	Data Start Offset: 0x0010
	Access Method: General-purpose non-volatile data functions
	Access Address: 0x0000
	Status: Valid, Full
	Change Token: 0x000000AE
	Header Format: Type 1
	Supported Log Type Descriptors: 1
	Descriptor 1: POST error
	Data Format 1: POST results bitmap

Handle 0x002A, DMI type 16, 15 bytes
Physical Memory Array
	Location: System Board Or Motherboard
	Use: System Memory
	Error Correction Type: None
	Maximum Capacity: 8 GB
	Error Information Handle: Not Provided
	Number Of Devices: 2

Handle 0x002B, DMI type 17, 28 bytes
Memory Device
	Array Handle: 0x002A
	Error Information Handle: No Error
	Total Width: 64 bits
	Data Width: 64 bits
	Size: 4096 MB
	Form Factor: SODIMM
	Set: None
	Locator: DIMM 1
	Bank Locator: Bank 0/1
	Type: DDR3
	Type Detail: Synchronous
	Speed: 1066 MHz
	Manufacturer: 04CD            
	Serial Number: 00000000        
	Asset Tag: 0000
	Part Number: F3-8500CL7-4GBSQ  
	Rank: Unknown

Handle 0x002C, DMI type 17, 28 bytes
Memory Device
	Array Handle: 0x002A
	Error Information Handle: No Error
	Total Width: 64 bits
	Data Width: 64 bits
	Size: 4096 MB
	Form Factor: SODIMM
	Set: None
	Locator: DIMM 2
	Bank Locator: Bank 2/3
	Type: DDR3
	Type Detail: Synchronous
	Speed: 1066 MHz
	Manufacturer: 04CD            
	Serial Number: 00000000        
	Asset Tag: 0000
	Part Number: F3-8500CL7-4GBSQ  
	Rank: Unknown

Handle 0x002D, DMI type 18, 23 bytes
32-bit Memory Error Information
	Type: OK
	Granularity: Unknown
	Operation: Unknown
	Vendor Syndrome: Unknown
	Memory Array Address: Unknown
	Device Address: Unknown
	Resolution: Unknown

Handle 0x002E, DMI type 19, 15 bytes
Memory Array Mapped Address
	Starting Address: 0x00000000000
	Ending Address: 0x001FFFFFFFF
	Range Size: 8 GB
	Physical Array Handle: 0x002A
	Partition Width: 2

Handle 0x002F, DMI type 20, 19 bytes
Memory Device Mapped Address
	Starting Address: 0x00000000000
	Ending Address: 0x000FFFFFFFF
	Range Size: 4 GB
	Physical Device Handle: 0x002B
	Memory Array Mapped Address Handle: 0x002E
	Partition Row Position: 1

Handle 0x0030, DMI type 20, 19 bytes
Memory Device Mapped Address
	Starting Address: 0x00100000000
	Ending Address: 0x001FFFFFFFF
	Range Size: 4 GB
	Physical Device Handle: 0x002C
	Memory Array Mapped Address Handle: 0x002E
	Partition Row Position: 1

Handle 0x0031, DMI type 21, 7 bytes
Built-in Pointing Device
	Type: Track Point
	Interface: PS/2
	Buttons: 3

Handle 0x0032, DMI type 21, 7 bytes
Built-in Pointing Device
	Type: Touch Pad
	Interface: PS/2
	Buttons: 0

Handle 0x0033, DMI type 22, 26 bytes
Portable Battery
	Location: Rear
	Manufacturer: SANYO
	Name: 42T4646
	Design Capacity: 28800 mWh
	Design Voltage: 14400 mV
	SBDS Version: 03.01
	Maximum Error: Unknown
	SBDS Serial Number: 0A41
	SBDS Manufacture Date: 2010-12-20
	SBDS Chemistry: LION
	OEM-specific Information: 0x00000000

Handle 0x0034, DMI type 126, 26 bytes
Inactive

Handle 0x0035, DMI type 24, 5 bytes
Hardware Security
	Power-On Password Status: Disabled
	Keyboard Password Status: Disabled
	Administrator Password Status: Enabled
	Front Panel Reset Status: Unknown

Handle 0x0036, DMI type 32, 11 bytes
System Boot Information
	Status: No errors detected

Handle 0x0037, DMI type 131, 17 bytes
OEM-specific Type
	Header and Data:
		83 11 37 00 01 02 03 FF FF 1F 00 00 00 00 00 03
		00
	Strings:
		BOOTINF 20h
		BOOTDEV 21h
		KEYPTRS 23h

Handle 0x0038, DMI type 131, 22 bytes
OEM-specific Type
	Header and Data:
		83 16 38 00 01 00 00 00 00 00 00 00 00 00 00 00
		00 00 00 00 00 01
	Strings:
		TVT-Enablement

Handle 0x0039, DMI type 132, 7 bytes
OEM-specific Type
	Header and Data:
		84 07 39 00 02 D8 36

Handle 0x003A, DMI type 133, 5 bytes
OEM-specific Type
	Header and Data:
		85 05 3A 00 01
	Strings:
		KHOIHGIUCCHHII

Handle 0x003B, DMI type 134, 13 bytes
OEM-specific Type
	Header and Data:
		86 0D 3B 00 29 12 10 20 00 00 00 00 00

Handle 0x003C, DMI type 134, 16 bytes
OEM-specific Type
	Header and Data:
		86 10 3C 00 00 53 54 4D 20 01 01 00 00 03 01 02
	Strings:
		TPM INFO
		System Reserved

Handle 0x003D, DMI type 135, 13 bytes
OEM-specific Type
	Header and Data:
		87 0D 3D 00 54 50 07 00 01 00 00 00 00

Handle 0x003E, DMI type 135, 18 bytes
OEM-specific Type
	Header and Data:
		87 12 3E 00 54 50 07 01 01 C2 00 00 00 00 00 00
		00 00

Handle 0x003F, DMI type 135, 58 bytes
OEM-specific Type
	Header and Data:
		87 3A 3F 00 54 50 07 02 42 41 59 20 49 2F 4F 20
		02 00 04 FF 00 00 00 00 00 00 00 FF 00 00 00 00
		00 00 00 FF 00 00 00 00 00 00 00 FF 00 00 00 00
		00 00 00 06 00 02 FF FF 03 03

Handle 0x0040, DMI type 135, 30 bytes
OEM-specific Type
	Header and Data:
		87 1E 40 00 54 50 07 04 01 05 01 01 02 00 02 01
		02 00 03 01 02 00 05 01 02 00 06 01 02 00

Handle 0x0041, DMI type 135, 10 bytes
OEM-specific Type
	Header and Data:
		87 0A 41 00 54 50 07 03 01 01

Handle 0x0042, DMI type 136, 6 bytes
OEM-specific Type
	Header and Data:
		88 06 42 00 5A 5A

Handle 0x0043, DMI type 140, 67 bytes
OEM-specific Type
	Header and Data:
		8C 43 43 00 4C 45 4E 4F 56 4F 0B 00 01 50 DF 96
		AB 09 89 F3 42 AD 74 C2 2A 63 9D 24 C9 01 00 00
		00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
		00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
		00 00 00

Handle 0x0044, DMI type 140, 47 bytes
OEM-specific Type
	Header and Data:
		8C 2F 44 00 4C 45 4E 4F 56 4F 0B 01 01 09 00 F8
		08 A2 79 5C 63 E7 03 39 A2 6D 94 42 65 B8 A8 04
		00 01 00 10 00 10 00 10 01 D0 00 20 01 00 01

Handle 0x0045, DMI type 140, 63 bytes
OEM-specific Type
	Header and Data:
		8C 3F 45 00 4C 45 4E 4F 56 4F 0B 02 01 00 00 00
		00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
		00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
		00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

Handle 0x0046, DMI type 140, 17 bytes
OEM-specific Type
	Header and Data:
		8C 11 46 00 4C 45 4E 4F 56 4F 0B 03 01 00 00 00
		00

Handle 0x0047, DMI type 140, 19 bytes
OEM-specific Type
	Header and Data:
		8C 13 47 00 4C 45 4E 4F 56 4F 0B 04 01 B2 00 53
		4D 20 00

Handle 0x0048, DMI type 140, 19 bytes
OEM-specific Type
	Header and Data:
		8C 13 48 00 4C 45 4E 4F 56 4F 0B 05 01 07 00 00
		00 53 55

Handle 0x0049, DMI type 140, 23 bytes
OEM-specific Type
	Header and Data:
		8C 17 49 00 4C 45 4E 4F 56 4F 0B 06 01 7E 14 00
		00 00 00 00 00 00 00

Handle 0x004A, DMI type 129, 8 bytes
OEM-specific Type
	Header and Data:
		81 08 4A 00 01 01 02 01
	Strings:
		Intel_ASF
		Intel_ASF_001

Handle 0x004B, DMI type 130, 20 bytes
OEM-specific Type
	Header and Data:
		82 14 4B 00 24 41 4D 54 01 01 01 01 01 A5 8B 02
		00 00 01 00

Handle 0x004C, DMI type 131, 64 bytes
OEM-specific Type
	Header and Data:
		83 40 4C 00 35 00 00 00 00 00 00 00 00 00 00 00
		F8 00 07 3B 00 00 00 00 09 41 6C 06 01 00 06 00
		34 04 20 00 03 00 01 02 C8 00 EA 10 00 00 00 00
		00 00 00 00 3E 00 00 00 76 50 72 6F 00 00 00 00

Handle 0x004D, DMI type 127, 4 bytes
End Of Table
Je ferais le LiveCD ce soir mais à mon avis il y aura pas mal de Fail. Je tiens tout juste 1 heure sur batterie avec cpufreq comme il faut, en powersave, etc etc... Grrr :(

Edit

Voilà pour le résultat de l'iso :

Code : Tout sélectionner

-------------------------------------------------
  Date: Wed Jul 13 14:45:33 2011                                       
*                                               *
* Firmwarekit (release 3)                       *
* http://www.linuxfirmwarekit.org               *
*                                               *
*                                               *
* For more information on test descriptions     *
* and details on what the PASS/INFO/WARN/FAIL   *
* results mean, go to: Documentation/TestsInfo. *
*                                               *
-------------------------------------------------

KERNEL VERSION: Linux testmachine 2.6.22.9 #1 SMP Mon Oct 1 15:17:15 PDT 2007 i686 i686 i386 GNU/Linux


SUMMARY:  5 Fails, 3 Warns, 11 Pass, 19 Total

=================================================
* Plugin name: pciresource
* Result: FAIL

* Title: Validate assigned PCI resources
* Description: This test is currently a placeholder and just checks the kernel log for complaints about PCI resource errors. In the future the idea is to actually perform a validation step on all PCI resources against a certain rule-set.
================================================

[FAIL]-HPET resources incorrect

hpet_resources: 0xfed00000 is busy

=================================================
* Plugin name: thermal_trip
* Result: FAIL

* Title: ACPI passive thermal trip points
* Description: This test determines if the passive trip point works as expected.
================================================

[FAIL]-Changing passive trip point seems uneffective in Zone THM0.

=================================================
* Plugin name: cpufreq
* Result: FAIL

* Title: CPU frequency scaling tests (1-2 mins)
* Description: For each processor in the system, this test steps through the various frequency states (P-states) that the BIOS advertises for the processor. For each processor/frequency combination, a quick performance value is measured. The test then validates that: 
  1) Each processor has the same number of frequency states
  2) Higher advertised frequencies have a higher performance
  3) No duplicate frequency values are reported by the BIOS
  4) Is BIOS wrongly doing Sw_All P-state coordination across cores
  5) Is BIOS wrongly doing Sw_Any P-state coordination across cores

================================================

[INFO]-13 CPU frequency steps supported

 Frequency | Speed 
-----------+---------
  2.72 Ghz | 100.0 %
  2.72 Ghz |  90.9 %
  2.58 Ghz |  86.4 %
  2.45 Ghz |  81.8 %
  2.32 Ghz |  77.3 %
  2.18 Ghz |  72.7 %
  2.05 Ghz |  68.2 %
  1.92 Ghz |  63.6 %
  1.78 Ghz |  59.1 %
  1.65 Ghz |  54.5 %
  1466 Mhz |  50.0 %
  1333 Mhz |  45.5 %
  1199 Mhz |  40.9 %


[FAIL]-Processors are set to SW_ANY

[FAIL]-Firmware not implementing hardware coordination cleanly. Firmware using SW_ALL instead?


[FAIL]-Firmware not implementing hardware coordination cleanly. Firmware using SW_ANY instead?


=================================================
* Plugin name: chk_hpet
* Result: FAIL

* Title: HPET configuration test
* Description: This test checks the HPET PCI BAR for each timer block in the timer.The base address is passed by the firmware via an ACPI table.IRQ routing and initialization is also verified by the test.
================================================

[WARN]-HPET driver in the kernel is enabled, inaccurate results follow.

[FAIL]-Mismatched HPET base between DSDT and the kernel

Mismatched HPET base between DSDT (fed00000) and the kernel 0)

[FAIL]-Mismatched HPET base between DSDT and the kernel

Mismatched HPET base between DSDT (fed00000) and the kernel f)

[FAIL]-Mismatched HPET base between DSDT and the kernel

Mismatched HPET base between DSDT (fed00000) and the kernel 0)

[INFO]-HPET found, VendorID is: 8086

=================================================
* Plugin name: dmi
* Result: FAIL

* Title: DMI information check
* Description: This test checks the DMI/SMBIOS tables for common errors.
================================================

[FAIL]-No SMBIOS nor DMI entry point found.

[FAIL]-No SMBIOS nor DMI entry point found.

[FAIL]-No SMBIOS nor DMI entry point found.

[FAIL]-No SMBIOS nor DMI entry point found.

=================================================
* Plugin name: maxreadreq
* Result: WARN

* Title: PCI Express MaxReadReq tuning
* Description: This test checks if the firmware has set MaxReadReq to a higher value on non-montherboard devices
================================================

[WARN]-MaxReadReq for device pci://00:00:1b.0 is low (128)

[WARN]-MaxReadReq for device pci://00:02:00.0 is low (128)

=================================================
* Plugin name: edd
* Result: WARN

* Title: EDD Boot disk hinting
* Description: This test verifies if the BIOS directs the operating system on which storage device to use for booting (EDD information). This is important for systems that (can) have multiple disks. Linux distributions increasingly depend on this info to find out on which device to install the bootloader.
================================================

[INFO]-device 80: The system boots from device 0000:00:1f.2 channel: 0 device: 0 


[WARN]-device 80: No matching MBR signature (0x00000000) found for the boot disk

Device sda - signature 0x0


[INFO]-device 81 is provided by device 0000:00:1f.2 channel: 1 device: 0 


[WARN]-device 81: No matching MBR signature (0x00000000) found for this disk

Device sda - signature 0x0


[INFO]-device 82 is provided by device 0000:00:1a.0 channel: 0 serial_number: cb6f3b9865450930 


[WARN]-device 82: No matching MBR signature (0x00000000) found for this disk

Device sda - signature 0x0


=================================================
* Plugin name: fan
* Result: WARN

* Title: Fan tests
* Description: This test reports how many fans there are in the system. It also checks for the current status of the fan(s).
================================================

[WARN]-No fan information present

=================================================
* Plugin name: battery
* Result: INFO

* Title: Battery tests
* Description: This test reports which (if any) batteries there are in the system. In addition, for charging or discharging batteries, the test validates that the reported 'current capacity' properly increments/decrements in line with the charge/discharge state. 

This test also stresses the entire battery state reporting codepath in the ACPI BIOS, and any warnings given by the ACPI interpreter will be reported.
================================================

[INFO]-Battery BAT0 is model 42T4646 and is currently charged

=================================================
* Plugin name: acpiinfo
* Result: INFO

* Title: General ACPI information
* Description: This test checks the output of the in-kernel ACPI CA against common error messages that indicate a bad interaction with the bios, including those that point at AML syntax errors.
================================================

[INFO]-DSDT was compiled by the Microsoft AML compiler

ACPI: DSDT BB7F0D6B, DE19 (r1 LENOVO TP-6Q        1340 MSFT  3000001)

=================================================
* Plugin name: mtrr
* Result: PASS

* Title: MTRR validation
* Description: This test validates the MTRR setup against the memory map to detect any inconsistencies in cachability.
================================================

=================================================
* Plugin name: acpicompile
* Result: PASS

* Title: DSDT AML verification
* Description: This test first disassembles the DSDT of the BIOS, and then uses the IASL compiler from Intel to recompile the code. The IASL copiler is much stricter in detecting deviations from the ACPI specification and can find numerous defects that other AML compilers cannot find. Fixing these defects increases the probability that the BIOS will operate well with a variety of operating systems.
================================================

=================================================
* Plugin name: SUN
* Result: PASS

* Title: SUN duplicate test
* Description: This makes sure that each SUN (Slot Unique Number) that is called in the DSDT through the Name() method is unique, no duplicates should be found.
================================================

[PASS]-Tested _SUN ids, successfully found no duplicates

=================================================
* Plugin name: virt
* Result: PASS

* Title: VT/VMX Virtualization extensions
* Description: This test checks if VT/VMX is set up correctly
================================================

=================================================
* Plugin name: DMAR
* Result: PASS

* Title: (experimental) DMA Remapping (VT-d) test
* Description: Verify if DMA remapping is sane.
================================================

[PASS]-DMAR ACPI table is ok

=================================================
* Plugin name: os2gap
* Result: PASS

* Title: OS/2 memory hole test
* Description: This test checks if the OS/2 15Mb memory hole is absent
================================================

[PASS]-Successfully found no 15mb memory hole

=================================================
* Plugin name: ethernet
* Result: PASS

* Title: Ethernet functionality
* Description: This test is currently a placeholder for a more advanced ethernet test. Currently the only check performed is that a link is acquired within 45 seconds of enabling the interface. 45 seconds is close to the value most Linux distributions use as timeout value.

In the future the plan is to also perform actual data transfer tests as part of the ethernet test, to validate interrupt routing and other per-NIC behaviors.
================================================

=================================================
* Plugin name: apicedge
* Result: PASS

* Title: (experimental) APIC Edge/Level check
* Description: This test checks if legacy interrupts are edge and PCI interrupts are level
================================================

=================================================
* Plugin name: microcode
* Result: PASS

* Title: Processor microcode update
* Description: This test verifies if the firmware has put a recent version of the microcode into the processor at boot time. Recent microcode is important to have all the required features and errata updates for the processor.
================================================

Puis sur un Asus

# acpixtract -l acpi

Code : Tout sélectionner

Signature Length Revision  OemId     OemTableId   OemRevision CompilerId CompilerRevision

    DSDT   31686     01    "A6JC0 "  "A6JC0220"    00000220    "INTL"     02002026
    FACS      64
    FACP     132     02    "AMI   "  "OEMFACP "    10000604    "MSFT"     00000097
    APIC      92     01    "AMI   "  "OEMAPIC "    10000604    "MSFT"     00000097
    MCFG      60     01    "AMI   "  "OEMMCFG "    10000604    "MSFT"     00000097
    BOOT      40     01    "AMI   "  "OEMBOOT "    10000604    "MSFT"     00000097
    OEMB      70     01    "AMI   "  "AMI_OEM "    10000604    "MSFT"     00000097
    RSDT      56     01    "AMI   "  "OEMRSDT "    10000604    "MSFT"     00000097
    RSDP                   "ACPIAM"

Found 9 ACPI tables [20110225]
le résultat de l'iso

Code : Tout sélectionner

-------------------------------------------------
  Date: Wed Jul 13 13:04:40 2011                                       
*                                               *
* Firmwarekit (release 3)                       *
* http://www.linuxfirmwarekit.org               *
*                                               *
*                                               *
* For more information on test descriptions     *
* and details on what the PASS/INFO/WARN/FAIL   *
* results mean, go to: Documentation/TestsInfo. *
*                                               *
-------------------------------------------------

KERNEL VERSION: Linux testmachine 2.6.22.9 #1 SMP Mon Oct 1 15:17:15 PDT 2007 i686 i686 i386 GNU/Linux


SUMMARY:  5 Fails, 3 Warns, 12 Pass, 20 Total

=================================================
* Plugin name: thermal_trip
* Result: FAIL

* Title: ACPI passive thermal trip points
* Description: This test determines if the passive trip point works as expected.
================================================

[FAIL]-Changing passive trip point seems uneffective in Zone THRM.

=================================================
* Plugin name: cpufreq
* Result: FAIL

* Title: CPU frequency scaling tests (1-2 mins)
* Description: For each processor in the system, this test steps through the various frequency states (P-states) that the BIOS advertises for the processor. For each processor/frequency combination, a quick performance value is measured. The test then validates that: 
  1) Each processor has the same number of frequency states
  2) Higher advertised frequencies have a higher performance
  3) No duplicate frequency values are reported by the BIOS
  4) Is BIOS wrongly doing Sw_All P-state coordination across cores
  5) Is BIOS wrongly doing Sw_Any P-state coordination across cores

================================================

[INFO]-10 CPU frequency steps supported

 Frequency | Speed 
-----------+---------
  1.72 Ghz | 100.0 %
  1.72 Ghz | 100.0 %
  1.72 Ghz | 100.0 %
  1.71 Ghz | 100.0 %
  1.71 Ghz | 100.0 %
  1.71 Ghz | 100.0 %
  1.71 Ghz | 100.0 %
  1.71 Ghz | 100.0 %
  1328 Mhz |  80.0 %
   996 Mhz |  60.1 %


[FAIL]-Processors are set to SW_ANY

[FAIL]-Firmware not implementing hardware coordination cleanly. Firmware using SW_ALL instead?


[FAIL]-Firmware not implementing hardware coordination cleanly. Firmware using SW_ANY instead?


=================================================
* Plugin name: chk_hpet
* Result: FAIL

* Title: HPET configuration test
* Description: This test checks the HPET PCI BAR for each timer block in the timer.The base address is passed by the firmware via an ACPI table.IRQ routing and initialization is also verified by the test.
================================================

[WARN]-HPET driver in the kernel is enabled, inaccurate results follow.

[FAIL]-Failed to locate HPET base

The firmware AML code doesn't advertize the HPET base.
HPET might be disabled in the bios settings, or not supported by the platform.

=================================================
* Plugin name: dmi
* Result: FAIL

* Title: DMI information check
* Description: This test checks the DMI/SMBIOS tables for common errors.
================================================

[FAIL]-No SMBIOS nor DMI entry point found.

[FAIL]-No SMBIOS nor DMI entry point found.

[FAIL]-No SMBIOS nor DMI entry point found.

[FAIL]-No SMBIOS nor DMI entry point found.

[FAIL]-No SMBIOS nor DMI entry point found.

[FAIL]-No SMBIOS nor DMI entry point found.

[FAIL]-No SMBIOS nor DMI entry point found.

=================================================
* Plugin name: microcode
* Result: FAIL

* Title: Processor microcode update
* Description: This test verifies if the firmware has put a recent version of the microcode into the processor at boot time. Recent microcode is important to have all the required features and errata updates for the processor.
================================================

[FAIL]-Cpu cpu1 has outdated microcode (version 48 while version c7 is available)

[FAIL]-Cpu cpu0 has outdated microcode (version 48 while version c7 is available)

=================================================
* Plugin name: acpicompile
* Result: WARN

* Title: DSDT AML verification
* Description: This test first disassembles the DSDT of the BIOS, and then uses the IASL compiler from Intel to recompile the code. The IASL copiler is much stricter in detecting deviations from the ACPI specification and can find numerous defects that other AML compilers cannot find. Fixing these defects increases the probability that the BIOS will operate well with a variety of operating systems.
================================================

[WARN]-Unknown reserved name (_T01)

Unknown reserved name (_T01)
At line #20 of DSDT.dsl:

 |   *     Creator ID       "INTL"
 |   *     Creator Revision 0x02002026 (33562662)
 |   */
 |  DefinitionBlock ("DSDT.aml", "DSDT", 1, "A6JC0", "A6JC0220", 0x00000220)
 |  {
>>>     Name (_T01, 0x00)
 |      Name (_T00, 0x00)
 |      Scope (\_SB)
 |      {
 |          Name (ATKP, Zero)


[WARN]-Unknown reserved name (_T00)

Unknown reserved name (_T00)
At line #21 of DSDT.dsl:

 |   *     Creator Revision 0x02002026 (33562662)
 |   */
 |  DefinitionBlock ("DSDT.aml", "DSDT", 1, "A6JC0", "A6JC0220", 0x00000220)
 |  {
 |      Name (_T01, 0x00)
>>>     Name (_T00, 0x00)
 |      Scope (\_SB)
 |      {
 |          Name (ATKP, Zero)
 |          Device (ATKD)


[WARN]-Statement is unreachable

Statement is unreachable
At line #1715 of DSDT.dsl:

 |                          }
 |  
 |                          ISMI (0xA0)
 |                          Store (\SETD, NXTD)
 |                          Return (\SETD)
>>>                         Return (NXTD)
 |                      }
 |  
 |                      Method (NATK, 0, NotSerialized)
 |                      {


[WARN]-Possible operator timeout is ignored

Possible operator timeout is ignored
At line #4978 of DSDT.dsl:

 |  Name (XSST, 0x1A)
 |  Name (XRCT, 0x1C)
 |  Mutex (MUTE, 0x00)
 |  Method (RBPE, 1, NotSerialized)
 |  {
>>>     Acquire (MUTE, 0x03E8)
 |      Add (Arg0, \PCIB, Local0)
 |      OperationRegion (PCFG, SystemMemory, Local0, 0x01)
 |      Field (PCFG, ByteAcc, NoLock, Preserve)
 |      {


[WARN]-Possible operator timeout is ignored

Possible operator timeout is ignored
At line #4992 of DSDT.dsl:

 |              Return (XCFG)
 |          }
 |  
 |          Method (RWPE, 1, NotSerialized)
 |          {
>>>             Acquire (MUTE, 0x03E8)
 |              And (Arg0, 0xFFFFFFFE, Arg0)
 |              Add (Arg0, \PCIB, Local0)
 |              OperationRegion (PCFG, SystemMemory, Local0, 0x02)
 |              Field (PCFG, WordAcc, NoLock, Preserve)


[WARN]-Possible operator timeout is ignored

Possible operator timeout is ignored
At line #5007 of DSDT.dsl:

 |              Return (XCFG)
 |          }
 |  
 |          Method (RDPE, 1, NotSerialized)
 |          {
>>>             Acquire (MUTE, 0x03E8)
 |              And (Arg0, 0xFFFFFFFC, Arg0)
 |              Add (Arg0, \PCIB, Local0)
 |              OperationRegion (PCFG, SystemMemory, Local0, 0x04)
 |              Field (PCFG, DWordAcc, NoLock, Preserve)


[WARN]-Possible operator timeout is ignored

Possible operator timeout is ignored
At line #5022 of DSDT.dsl:

 |              Return (XCFG)
 |          }
 |  
 |          Method (WBPE, 2, NotSerialized)
 |          {
>>>             Acquire (MUTE, 0x0FFF)
 |              Add (Arg0, \PCIB, Local0)
 |              OperationRegion (PCFG, SystemMemory, Local0, 0x01)
 |              Field (PCFG, ByteAcc, NoLock, Preserve)
 |              {


[WARN]-Possible operator timeout is ignored

Possible operator timeout is ignored
At line #5036 of DSDT.dsl:

 |              Release (MUTE)
 |          }
 |  
 |          Method (WWPE, 2, NotSerialized)
 |          {
>>>             Acquire (MUTE, 0x03E8)
 |              And (Arg0, 0xFFFFFFFE, Arg0)
 |              Add (Arg0, \PCIB, Local0)
 |              OperationRegion (PCFG, SystemMemory, Local0, 0x02)
 |              Field (PCFG, WordAcc, NoLock, Preserve)


[WARN]-Possible operator timeout is ignored

Possible operator timeout is ignored
At line #5051 of DSDT.dsl:

 |              Release (MUTE)
 |          }
 |  
 |          Method (WDPE, 2, NotSerialized)
 |          {
>>>             Acquire (MUTE, 0x03E8)
 |              And (Arg0, 0xFFFFFFFC, Arg0)
 |              Add (Arg0, \PCIB, Local0)
 |              OperationRegion (PCFG, SystemMemory, Local0, 0x04)
 |              Field (PCFG, DWordAcc, NoLock, Preserve)


[WARN]-Possible operator timeout is ignored

Possible operator timeout is ignored
At line #5066 of DSDT.dsl:

 |              Release (MUTE)
 |          }
 |  
 |          Method (RWDP, 3, NotSerialized)
 |          {
>>>             Acquire (MUTE, 0x03E8)
 |              And (Arg0, 0xFFFFFFFC, Arg0)
 |              Add (Arg0, \PCIB, Local0)
 |              OperationRegion (PCFG, SystemMemory, Local0, 0x04)
 |              Field (PCFG, DWordAcc, NoLock, Preserve)


[WARN]-Statement is unreachable

Statement is unreachable
At line #7262 of DSDT.dsl:

 |              {
 |                  Store (0x01, Local1)
 |              }
 |  
 |              Return (Local1)
>>>             Return (0x00)
 |          }
 |  
 |          Method (BCFC, 0, NotSerialized)
 |          {


[PASS]-Tested table DSDT.dsl

[INFO]-The IASL compiler from Intel would save 1815 bytes of space.

The existing code takes 31686 bytes
The IASL compiler from Intel uses 29871 bytes
This is a saving of 1815 bytes.


=================================================
* Plugin name: maxreadreq
* Result: WARN

* Title: PCI Express MaxReadReq tuning
* Description: This test checks if the firmware has set MaxReadReq to a higher value on non-montherboard devices
================================================

[WARN]-MaxReadReq for device pci://00:00:1b.0 is low (128)

[WARN]-MaxReadReq for device pci://00:03:00.0 is low (128)

=================================================
* Plugin name: edd
* Result: WARN

* Title: EDD Boot disk hinting
* Description: This test verifies if the BIOS directs the operating system on which storage device to use for booting (EDD information). This is important for systems that (can) have multiple disks. Linux distributions increasingly depend on this info to find out on which device to install the bootloader.
================================================

[INFO]-device 80: The system boots from device 0000:00:1f.1 channel: 0 device: 0 


[WARN]-device 80: No matching MBR signature (0x00041399) found for the boot disk

Device hdb - signature 0x0
Device hda - signature 0x41399


=================================================
* Plugin name: battery
* Result: INFO

* Title: Battery tests
* Description: This test reports which (if any) batteries there are in the system. In addition, for charging or discharging batteries, the test validates that the reported 'current capacity' properly increments/decrements in line with the charge/discharge state. 

This test also stresses the entire battery state reporting codepath in the ACPI BIOS, and any warnings given by the ACPI interpreter will be reported.
================================================

[INFO]-Battery BAT0 is model A6-4224 and is currently charged

=================================================
* Plugin name: acpiinfo
* Result: INFO

* Title: General ACPI information
* Description: This test checks the output of the in-kernel ACPI CA against common error messages that indicate a bad interaction with the bios, including those that point at AML syntax errors.
================================================

[INFO]-DSDT was compiled by the Intel AML compiler

ACPI: DSDT B7FD0460, 7BC6 (r1  A6JC0 A6JC0220      220 INTL  2002026)

=================================================
* Plugin name: virt
* Result: INFO

* Title: VT/VMX Virtualization extensions
* Description: This test checks if VT/VMX is set up correctly
================================================

[INFO]-Processor does not support Virtualization extensions

=================================================
* Plugin name: DMAR
* Result: INFO

* Title: (experimental) DMA Remapping (VT-d) test
* Description: Verify if DMA remapping is sane.
================================================

[INFO]-No DMAR ACPI table found.

=================================================
* Plugin name: mtrr
* Result: PASS

* Title: MTRR validation
* Description: This test validates the MTRR setup against the memory map to detect any inconsistencies in cachability.
================================================

=================================================
* Plugin name: pciresource
* Result: PASS

* Title: Validate assigned PCI resources
* Description: This test is currently a placeholder and just checks the kernel log for complaints about PCI resource errors. In the future the idea is to actually perform a validation step on all PCI resources against a certain rule-set.
================================================

=================================================
* Plugin name: SUN
* Result: PASS

* Title: SUN duplicate test
* Description: This makes sure that each SUN (Slot Unique Number) that is called in the DSDT through the Name() method is unique, no duplicates should be found.
================================================

[PASS]-Tested _SUN ids, successfully found no duplicates

=================================================
* Plugin name: fan
* Result: PASS

* Title: Fan tests
* Description: This test reports how many fans there are in the system. It also checks for the current status of the fan(s).
================================================

[PASS]-Fan FN00 status is: on

=================================================
* Plugin name: ebda
* Result: PASS

* Title: EBDA region
* Description: This test validates if the EBDA region is mapped and reserved in the E820 table.
================================================

[PASS]-EBDA region is correctly reserved in the E820 table.

=================================================
* Plugin name: os2gap
* Result: PASS

* Title: OS/2 memory hole test
* Description: This test checks if the OS/2 15Mb memory hole is absent
================================================

[PASS]-Successfully found no 15mb memory hole

=================================================
* Plugin name: ethernet
* Result: PASS

* Title: Ethernet functionality
* Description: This test is currently a placeholder for a more advanced ethernet test. Currently the only check performed is that a link is acquired within 45 seconds of enabling the interface. 45 seconds is close to the value most Linux distributions use as timeout value.

In the future the plan is to also perform actual data transfer tests as part of the ethernet test, to validate interrupt routing and other per-NIC behaviors.
================================================

=================================================
* Plugin name: apicedge
* Result: PASS

* Title: (experimental) APIC Edge/Level check
* Description: This test checks if legacy interrupts are edge and PCI interrupts are level
================================================

Dernière modification par hansi le mer. 13 juil. 2011, 20:52, modifié 1 fois.
Combattu souvent, battu parfois, abattu jamais ! (François de Charette)
lecbee
Hankyu
Messages : 17
Inscription : dim. 03 juil. 2011, 17:35

Re: [DB] BIOS - ACPI - collecte d'infos

Message par lecbee »

Cool pour le LiveCD.
C'est mis à jour.
Avatar de l’utilisateur
Distag
yeomen
Messages : 272
Inscription : dim. 03 avr. 2011, 15:58

Re: [DB] BIOS - ACPI - collecte d'infos

Message par Distag »

Pour un laptop AIRIS ( je ne sais plus quel model, si vous connaissez une commande qui le donne n'hésitez pas)

Code : Tout sélectionner

~ $ sudo acpidump > acpi
~ $ sudo acpixtract -l acpi

Signature Length Revision  OemId     OemTableId   OemRevision CompilerId CompilerRevision

    DSDT   40966     01    "QUANTA"  "WTW8    "    00000001    "MSFT"     01000013
    FACS      64
    FACP     244     04    "QUANTA"  "WTW8    "    00000001    "MSFT"     01000013
    HPET      56     01    "QUANTA"  "WTW8    "    00000001    "MSFT"     01000013
    APIC     108     01    "QUANTA"  "WTW8    "    00000001    "MSFT"     01000013
    MCFG      60     01    "QUANTA"  "WTW8    "    00000001    "MSFT"     01000013
    ASF!     165     20    "QUANTA"  "WTW8    "    00000001    "MSFT"     01000013
    SLIC     374     01    "QUANTA"  "WTW8    "    06040000    "MSFT"     01000013
    BOOT      40     01    "QUANTA"  "WTW8    "    00000001    "MSFT"     01000013
    SSDT    1621     01    "QUANTA"  "WTW8    "    00003000    "INTL"     20060317
    XSDT     100     01    "QUANTA"  "WTW8    "    00000001    "    "     01000013
    RSDP                   "QUANTA"

Found 12 ACPI tables [20110225]

dmidecode

Code : Tout sélectionner

# dmidecode 2.11
SMBIOS 2.4 present.
35 structures occupying 1676 bytes.
Table at 0x000E5130.

Handle 0x0000, DMI type 0, 24 bytes
BIOS Information
	Vendor: INSYDE
	Version: Q3C85
	Release Date: 03/19/2009
	ROM Size: 1024 kB
	Characteristics:
		PCI is supported
		BIOS is upgradeable
		BIOS shadowing is allowed
		Boot from CD is supported
		Selectable boot is supported
		BIOS ROM is socketed
		EDD is supported
		Japanese floppy for NEC 9800 1.2 MB is supported (int 13h)
		Japanese floppy for Toshiba 1.2 MB is supported (int 13h)
		5.25"/360 kB floppy services are supported (int 13h)
		5.25"/1.2 MB floppy services are supported (int 13h)
		3.5"/720 kB floppy services are supported (int 13h)
		3.5"/2.88 MB floppy services are supported (int 13h)
		8042 keyboard services are supported (int 9h)
		CGA/mono video services are supported (int 10h)
		ACPI is supported
		USB legacy is supported
		Targeted content distribution is supported

Handle 0x0001, DMI type 1, 27 bytes
System Information
	Manufacturer: Quanta
	Product Name: TW8/SW8/DW8
	Version: 03
	Serial Number: TW8TFCSE09191DDB
	UUID: 36F97A69-1E0F-2CD7-BB46-D6A99C5EF1A9
	Wake-up Type: Power Switch
	SKU Number: Montevina_Fab
	Family: Intel_Mobile

Handle 0x0002, DMI type 2, 16 bytes
Base Board Information
	Manufacturer: Quanta
	Product Name: TW8/SW8/DW8
	Version: TBD
	Serial Number: QTF5QQ91900097
	Asset Tag: Base Board Asset Tag
	Features:
		Board is a hosting board
		Board is replaceable
	Location In Chassis: Base Board Chassis Location
	Chassis Handle: 0x0003
	Type: Motherboard
	Contained Object Handles: 0

Handle 0x0003, DMI type 3, 22 bytes
Chassis Information
	Manufacturer: Quanta
	Type: Other
	Lock: Not Present
	Version: UK
	Serial Number: 00238BC577B3
	Asset Tag: Chassis Asset Tag
	Boot-up State: Safe
	Power Supply State: Safe
	Thermal State: Safe
	Security Status: None
	OEM Information: 0x00000000
	Height: Unspecified
	Number Of Power Cords: 1
	Contained Elements: 0
	SKU Number: Not Specified

Handle 0x0004, DMI type 5, 20 bytes
Memory Controller Information
	Error Detecting Method: None
	Error Correcting Capabilities:
		None
	Supported Interleave: One-way Interleave
	Current Interleave: One-way Interleave
	Maximum Memory Module Size: 4096 MB
	Maximum Total Memory Size: 8192 MB
	Supported Speeds:
		Other
	Supported Memory Types:
		Other
	Memory Module Voltage: Unknown
	Associated Memory Slots: 2
		0x0000
		0x0000
	Enabled Error Correcting Capabilities:
		None

Handle 0x0005, DMI type 9, 13 bytes
System Slot Information
	Designation: J6B2
	Type: x16 PCI Express
	Current Usage: Available
	Length: Other
	ID: 0
	Characteristics:
		PME signal is supported
		Hot-plug devices are supported

Handle 0x0006, DMI type 9, 13 bytes
System Slot Information
	Designation: J6B1
	Type: x1 PCI Express
	Current Usage: Available
	Length: Other
	ID: 0
	Characteristics:
		PME signal is supported
		Hot-plug devices are supported

Handle 0x0007, DMI type 9, 13 bytes
System Slot Information
	Designation: J6C2
	Type: x1 PCI Express
	Current Usage: Available
	Length: Other
	ID: 1
	Characteristics:
		PME signal is supported
		Hot-plug devices are supported

Handle 0x0008, DMI type 9, 13 bytes
System Slot Information
	Designation: J7B1
	Type: x1 PCI Express
	Current Usage: Available
	Length: Other
	ID: 2
	Characteristics:
		PME signal is supported
		Hot-plug devices are supported

Handle 0x0009, DMI type 9, 13 bytes
System Slot Information
	Designation: J8B3
	Type: x1 PCI Express
	Current Usage: Available
	Length: Other
	ID: 3
	Characteristics:
		PME signal is supported
		Hot-plug devices are supported

Handle 0x000A, DMI type 9, 13 bytes
System Slot Information
	Designation: J8D1
	Type: x1 PCI Express
	Current Usage: Available
	Length: Other
	ID: 4
	Characteristics:
		PME signal is supported
		Hot-plug devices are supported

Handle 0x000B, DMI type 11, 5 bytes
OEM Strings
	String 1: String1 for Original Equipment Manufacturer
	String 2: String2 for Original Equipment Manufacturer
	String 3: String3 for Original Equipment Manufacturer
	String 4: String4 for Original Equipment Manufacturer
	String 5: String5 for Original Equipment Manufacturer

Handle 0x000C, DMI type 12, 5 bytes
System Configuration Options
	Option 1: String1 for Type12 Equipment Manufacturer
	Option 2: String2 for Type12 Equipment Manufacturer
	Option 3: String3 for Type12 Equipment Manufacturer
	Option 4: String4 for Type12 Equipment Manufacturer

Handle 0x000D, DMI type 15, 29 bytes
System Event Log
	Area Length: 32672 bytes
	Header Start Offset: 0x0000
	Data Start Offset: 0x0000
	Access Method: General-purpose non-volatile data functions
	Access Address: 0x0000
	Status: Valid, Not Full
	Change Token: 0x12345678
	Header Format: OEM-specific
	Supported Log Type Descriptors: 3
	Descriptor 1: POST memory resize
	Data Format 1: None
	Descriptor 2: POST error
	Data Format 2: POST results bitmap
	Descriptor 3: Log area reset/cleared
	Data Format 3: None

Handle 0x000E, DMI type 21, 7 bytes
Built-in Pointing Device
	Type: Touch Pad
	Interface: PS/2
	Buttons: 4

Handle 0x000F, DMI type 27, 14 bytes
Cooling Device
	Type: Fan
	Status: OK
	OEM-specific Information: 0x00000000
	Nominal Speed: 43690 rpm

Handle 0x0010, DMI type 32, 20 bytes
System Boot Information
	Status: No errors detected

Handle 0x0011, DMI type 39, 22 bytes
System Power Supply
	Location: OEM_Define0
	Name: OEM_Define1
	Manufacturer: OEM_Define2
	Serial Number: OEM_Define2
	Asset Tag: OEM_Define3
	Model Part Number: OEM_Define4
	Revision: OEM_Define5
	Max Power Capacity: 75 W
	Status: Present, OK
	Type: Regulator
	Input Voltage Range Switching: Auto-switch
	Plugged: No
	Hot Replaceable: No

Handle 0x0012, DMI type 129, 5 bytes
OEM-specific Type
	Header and Data:
		81 05 12 00 4F
	Strings:
		em Test 1
		Oem Test 2

Handle 0x0013, DMI type 4, 35 bytes
Processor Information
	Socket Designation: CPU
	Type: Central Processor
	Family: Pentium M
	Manufacturer: Intel(R) Corporation
	ID: 76 06 01 00 FF FB EB BF
	Signature: Type 0, Family 6, Model 23, Stepping 6
	Flags:
		FPU (Floating-point unit on-chip)
		VME (Virtual mode extension)
		DE (Debugging extension)
		PSE (Page size extension)
		TSC (Time stamp counter)
		MSR (Model specific registers)
		PAE (Physical address extension)
		MCE (Machine check exception)
		CX8 (CMPXCHG8 instruction supported)
		APIC (On-chip APIC hardware supported)
		SEP (Fast system call)
		MTRR (Memory type range registers)
		PGE (Page global enable)
		MCA (Machine check architecture)
		CMOV (Conditional move instruction supported)
		PAT (Page attribute table)
		PSE-36 (36-bit page size extension)
		CLFSH (CLFLUSH instruction supported)
		DS (Debug store)
		ACPI (ACPI supported)
		MMX (MMX technology supported)
		FXSR (FXSAVE and FXSTOR instructions supported)
		SSE (Streaming SIMD extensions)
		SSE2 (Streaming SIMD extensions 2)
		SS (Self-snoop)
		HTT (Multi-threading)
		TM (Thermal monitor supported)
		PBE (Pending break enabled)
	Version: Intel(R) Core(TM)2 Duo CPU     P8400  @ 2.26GHz
	Voltage: 1.6 V
	External Clock: 1066 MHz
	Max Speed: 2266 MHz
	Current Speed: 1600 MHz
	Status: Populated, Enabled
	Upgrade: <OUT OF SPEC>
	L1 Cache Handle: 0x0016
	L2 Cache Handle: 0x0014
	L3 Cache Handle: Not Provided
	Serial Number: Not Specified
	Asset Tag: FFFF
	Part Number: Not Specified

Handle 0x0014, DMI type 7, 19 bytes
Cache Information
	Socket Designation: Unknown
	Configuration: Enabled, Not Socketed, Level 2
	Operational Mode: Write Back
	Location: Internal
	Installed Size: 3072 kB
	Maximum Size: 3072 kB
	Supported SRAM Types:
		Synchronous
	Installed SRAM Type: Synchronous
	Speed: Unknown
	Error Correction Type: Single-bit ECC
	System Type: Unified
	Associativity: 24-way Set-associative

Handle 0x0015, DMI type 7, 19 bytes
Cache Information
	Socket Designation: Unknown
	Configuration: Enabled, Not Socketed, Level 1
	Operational Mode: Write Back
	Location: Internal
	Installed Size: 32 kB
	Maximum Size: 32 kB
	Supported SRAM Types:
		Synchronous
	Installed SRAM Type: Synchronous
	Speed: Unknown
	Error Correction Type: Single-bit ECC
	System Type: Instruction
	Associativity: 8-way Set-associative

Handle 0x0016, DMI type 7, 19 bytes
Cache Information
	Socket Designation: Unknown
	Configuration: Enabled, Not Socketed, Level 1
	Operational Mode: Write Back
	Location: Internal
	Installed Size: 32 kB
	Maximum Size: 32 kB
	Supported SRAM Types:
		Synchronous
	Installed SRAM Type: Synchronous
	Speed: Unknown
	Error Correction Type: Single-bit ECC
	System Type: Data
	Associativity: 8-way Set-associative

Handle 0x0017, DMI type 16, 15 bytes
Physical Memory Array
	Location: System Board Or Motherboard
	Use: System Memory
	Error Correction Type: None
	Maximum Capacity: 8 GB
	Error Information Handle: No Error
	Number Of Devices: 2

Handle 0x0018, DMI type 6, 12 bytes
Memory Module Information
	Socket Designation: DIMM0
	Bank Connections: 0 0
	Current Speed: 1 ns
	Type: None
	Installed Size: 2048 MB (Single-bank Connection)
	Enabled Size: 2048 MB (Single-bank Connection)
	Error Status: OK

Handle 0x0019, DMI type 17, 27 bytes
Memory Device
	Array Handle: 0x0017
	Error Information Handle: 0x001A
	Total Width: 64 bits
	Data Width: 64 bits
	Size: 2048 MB
	Form Factor: SODIMM
	Set: None
	Locator: DIMM0
	Bank Locator: BANK 0
	Type: DDR2
	Type Detail: Synchronous
	Speed: 667 MHz
	Manufacturer: FFFFFFFFFFFFFFFF
	Serial Number: FFFFFFFF
	Asset Tag: Unknown
	Part Number: FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF

Handle 0x001A, DMI type 18, 23 bytes
32-bit Memory Error Information
	Type: OK
	Granularity: Unknown
	Operation: Unknown
	Vendor Syndrome: Unknown
	Memory Array Address: Unknown
	Device Address: Unknown
	Resolution: Unknown

Handle 0x001B, DMI type 20, 19 bytes
Memory Device Mapped Address
	Starting Address: 0x00000000000
	Ending Address: 0x0007FFFFFFF
	Range Size: 2 GB
	Physical Device Handle: 0x0019
	Memory Array Mapped Address Handle: 0x0021
	Partition Row Position: Unknown
	Interleave Position: 1
	Interleaved Data Depth: 1

Handle 0x001C, DMI type 6, 12 bytes
Memory Module Information
	Socket Designation: DIMM2
	Bank Connections: 0 0
	Current Speed: 1 ns
	Type: None
	Installed Size: 2048 MB (Single-bank Connection)
	Enabled Size: 2048 MB (Single-bank Connection)
	Error Status: OK

Handle 0x001D, DMI type 17, 27 bytes
Memory Device
	Array Handle: 0x0017
	Error Information Handle: 0x001E
	Total Width: 64 bits
	Data Width: 64 bits
	Size: 2048 MB
	Form Factor: SODIMM
	Set: None
	Locator: DIMM2
	Bank Locator: BANK 2
	Type: DDR2
	Type Detail: Synchronous
	Speed: 667 MHz
	Manufacturer: FFFFFFFFFFFFFFFF
	Serial Number: FFFFFFFF
	Asset Tag: Unknown
	Part Number: FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF

Handle 0x001E, DMI type 18, 23 bytes
32-bit Memory Error Information
	Type: OK
	Granularity: Unknown
	Operation: Unknown
	Vendor Syndrome: Unknown
	Memory Array Address: Unknown
	Device Address: Unknown
	Resolution: Unknown

Handle 0x001F, DMI type 20, 19 bytes
Memory Device Mapped Address
	Starting Address: 0x00000000000
	Ending Address: 0x0007FFFFFFF
	Range Size: 2 GB
	Physical Device Handle: 0x001D
	Memory Array Mapped Address Handle: 0x0021
	Partition Row Position: Unknown
	Interleave Position: 2
	Interleaved Data Depth: 1

Handle 0x0020, DMI type 18, 23 bytes
32-bit Memory Error Information
	Type: OK
	Granularity: Unknown
	Operation: Unknown
	Vendor Syndrome: Unknown
	Memory Array Address: Unknown
	Device Address: Unknown
	Resolution: Unknown

Handle 0x0021, DMI type 19, 15 bytes
Memory Array Mapped Address
	Starting Address: 0x00000000000
	Ending Address: 0x000FFFFFFFF
	Range Size: 4 GB
	Physical Array Handle: 0x0017
	Partition Width: 2

Handle 0x0022, DMI type 127, 4 bytes
End Of Table
Linux Firmware Kit

Code : Tout sélectionner

-------------------------------------------------
  Date: Wed Jul 13 11:16:43 2011                                       
*                                               *
* Firmwarekit (release 3)                       *
* http://www.linuxfirmwarekit.org               *
*                                               *
*                                               *
* For more information on test descriptions     *
* and details on what the PASS/INFO/WARN/FAIL   *
* results mean, go to: Documentation/TestsInfo. *
*                                               *
-------------------------------------------------

KERNEL VERSION: Linux testmachine 2.6.22.9 #1 SMP Mon Oct 1 15:17:15 PDT 2007 i686 i686 i386 GNU/Linux


SUMMARY:  5 Fails, 5 Warns, 10 Pass, 20 Total

=================================================
* Plugin name: acpicompile
* Result: FAIL

* Title: DSDT AML verification
* Description: This test first disassembles the DSDT of the BIOS, and then uses the IASL compiler from Intel to recompile the code. The IASL copiler is much stricter in detecting deviations from the ACPI specification and can find numerous defects that other AML compilers cannot find. Fixing these defects increases the probability that the BIOS will operate well with a variety of operating systems.
================================================

[FAIL]-Use of reserved word (_T_0)

Use of reserved word (_T_0)
At line #6972 of DSDT.dsl:

 |                          Return (0x0F)
 |                      }
 |  
 |                      Method (HINF, 3, NotSerialized)
 |                      {
>>>                         Name (_T_0, Zero)
 |                          Store (Arg1, _T_0)
 |                          If (LEqual (_T_0, Zero))
 |                          {
 |                              Return (Buffer (One)


[FAIL]-Use of reserved word (_T_0)

Use of reserved word (_T_0)
At line #7014 of DSDT.dsl:

 |                          Return (Buffer (Zero) {})
 |                      }
 |  
 |                      Method (TPPI, 3, NotSerialized)
 |                      {
>>>                         Name (_T_0, Zero)
 |                          Store (Arg1, _T_0)
 |                          If (LEqual (_T_0, Zero))
 |                          {
 |                              Return (Buffer (One)


[WARN]-Not all control paths return a value (_GTM)

Not all control paths return a value (_GTM)
At line #9249 of DSDT.dsl:

 |                  }
 |  
 |                  Device (PRID)
 |                  {
 |                      Name (_ADR, Zero)
>>>                     Method (_GTM, 0, NotSerialized)
 |                      {
 |                          If (LEqual (SCFG, Zero))
 |                          {
 |                              Name (PBUF, Buffer (0x14)


[WARN]-Reserved method must return a value (_GTM)

Reserved method must return a value (_GTM)
At line #9249 of DSDT.dsl:

 |                  }
 |  
 |                  Device (PRID)
 |                  {
 |                      Name (_ADR, Zero)
>>>                     Method (_GTM, 0, NotSerialized)
 |                      {
 |                          If (LEqual (SCFG, Zero))
 |                          {
 |                              Name (PBUF, Buffer (0x14)


[WARN]-Not all control paths return a value (_GTF)

Not all control paths return a value (_GTF)
At line #9409 of DSDT.dsl:

 |                      }
 |  
 |                      Device (P_D0)
 |                      {
 |                          Name (_ADR, Zero)
>>>                         Method (_GTF, 0, NotSerialized)
 |                          {
 |                              If (LEqual (SCFG, Zero))
 |                              {
 |                                  Name (PIB0, Buffer (0x0E)


[WARN]-Reserved method must return a value (_GTF)

Reserved method must return a value (_GTF)
At line #9409 of DSDT.dsl:

 |                      }
 |  
 |                      Device (P_D0)
 |                      {
 |                          Name (_ADR, Zero)
>>>                         Method (_GTF, 0, NotSerialized)
 |                          {
 |                              If (LEqual (SCFG, Zero))
 |                              {
 |                                  Name (PIB0, Buffer (0x0E)


[WARN]-Not all control paths return a value (_GTF)

Not all control paths return a value (_GTF)
At line #9477 of DSDT.dsl:

 |                      }
 |  
 |                      Device (P_D1)
 |                      {
 |                          Name (_ADR, One)
>>>                         Method (_GTF, 0, NotSerialized)
 |                          {
 |                              If (LEqual (SCFG, Zero))
 |                              {
 |                                  Name (PIB1, Buffer (0x0E)


[WARN]-Reserved method must return a value (_GTF)

Reserved method must return a value (_GTF)
At line #9477 of DSDT.dsl:

 |                      }
 |  
 |                      Device (P_D1)
 |                      {
 |                          Name (_ADR, One)
>>>                         Method (_GTF, 0, NotSerialized)
 |                          {
 |                              If (LEqual (SCFG, Zero))
 |                              {
 |                                  Name (PIB1, Buffer (0x0E)


[WARN]-Not all control paths return a value (_GTM)

Not all control paths return a value (_GTM)
At line #9550 of DSDT.dsl:

 |                  }
 |  
 |                  Device (SECD)
 |                  {
 |                      Name (_ADR, One)
>>>                     Method (_GTM, 0, NotSerialized)
 |                      {
 |                          If (LEqual (SCFG, Zero))
 |                          {
 |                              Name (SBUF, Buffer (0x14)


[WARN]-Reserved method must return a value (_GTM)

Reserved method must return a value (_GTM)
At line #9550 of DSDT.dsl:

 |                  }
 |  
 |                  Device (SECD)
 |                  {
 |                      Name (_ADR, One)
>>>                     Method (_GTM, 0, NotSerialized)
 |                      {
 |                          If (LEqual (SCFG, Zero))
 |                          {
 |                              Name (SBUF, Buffer (0x14)


[WARN]-Not all control paths return a value (_GTF)

Not all control paths return a value (_GTF)
At line #9710 of DSDT.dsl:

 |                      }
 |  
 |                      Device (S_D0)
 |                      {
 |                          Name (_ADR, Zero)
>>>                         Method (_GTF, 0, NotSerialized)
 |                          {
 |                              If (LEqual (SCFG, Zero))
 |                              {
 |                                  Name (SIB0, Buffer (0x0E)


[WARN]-Reserved method must return a value (_GTF)

Reserved method must return a value (_GTF)
At line #9710 of DSDT.dsl:

 |                      }
 |  
 |                      Device (S_D0)
 |                      {
 |                          Name (_ADR, Zero)
>>>                         Method (_GTF, 0, NotSerialized)
 |                          {
 |                              If (LEqual (SCFG, Zero))
 |                              {
 |                                  Name (SIB0, Buffer (0x0E)


[WARN]-Not all control paths return a value (_GTF)

Not all control paths return a value (_GTF)
At line #9778 of DSDT.dsl:

 |                      }
 |  
 |                      Device (S_D1)
 |                      {
 |                          Name (_ADR, One)
>>>                         Method (_GTF, 0, NotSerialized)
 |                          {
 |                              If (LEqual (SCFG, Zero))
 |                              {
 |                                  Name (SIB1, Buffer (0x0E)


[WARN]-Reserved method must return a value (_GTF)

Reserved method must return a value (_GTF)
At line #9778 of DSDT.dsl:

 |                      }
 |  
 |                      Device (S_D1)
 |                      {
 |                          Name (_ADR, One)
>>>                         Method (_GTF, 0, NotSerialized)
 |                          {
 |                              If (LEqual (SCFG, Zero))
 |                              {
 |                                  Name (SIB1, Buffer (0x0E)


[WARN]-Not all control paths return a value (_GTM)

Not all control paths return a value (_GTM)
At line #9910 of DSDT.dsl:

 |                  }
 |  
 |                  Device (PRID)
 |                  {
 |                      Name (_ADR, Zero)
>>>                     Method (_GTM, 0, NotSerialized)
 |                      {
 |                          If (LEqual (SCFG, Zero))
 |                          {
 |                              Name (PBUF, Buffer (0x14)


[WARN]-Reserved method must return a value (_GTM)

Reserved method must return a value (_GTM)
At line #9910 of DSDT.dsl:

 |                  }
 |  
 |                  Device (PRID)
 |                  {
 |                      Name (_ADR, Zero)
>>>                     Method (_GTM, 0, NotSerialized)
 |                      {
 |                          If (LEqual (SCFG, Zero))
 |                          {
 |                              Name (PBUF, Buffer (0x14)


[WARN]-Not all control paths return a value (_GTF)

Not all control paths return a value (_GTF)
At line #10070 of DSDT.dsl:

 |                      }
 |  
 |                      Device (P_D0)
 |                      {
 |                          Name (_ADR, Zero)
>>>                         Method (_GTF, 0, NotSerialized)
 |                          {
 |                              If (LEqual (SCFG, Zero))
 |                              {
 |                                  Name (PIB0, Buffer (0x0E)


[WARN]-Reserved method must return a value (_GTF)

Reserved method must return a value (_GTF)
At line #10070 of DSDT.dsl:

 |                      }
 |  
 |                      Device (P_D0)
 |                      {
 |                          Name (_ADR, Zero)
>>>                         Method (_GTF, 0, NotSerialized)
 |                          {
 |                              If (LEqual (SCFG, Zero))
 |                              {
 |                                  Name (PIB0, Buffer (0x0E)


[WARN]-Not all control paths return a value (_GTF)

Not all control paths return a value (_GTF)
At line #10138 of DSDT.dsl:

 |                      }
 |  
 |                      Device (P_D1)
 |                      {
 |                          Name (_ADR, One)
>>>                         Method (_GTF, 0, NotSerialized)
 |                          {
 |                              If (LEqual (SCFG, Zero))
 |                              {
 |                                  Name (PIB1, Buffer (0x0E)


[WARN]-Reserved method must return a value (_GTF)

Reserved method must return a value (_GTF)
At line #10138 of DSDT.dsl:

 |                      }
 |  
 |                      Device (P_D1)
 |                      {
 |                          Name (_ADR, One)
>>>                         Method (_GTF, 0, NotSerialized)
 |                          {
 |                              If (LEqual (SCFG, Zero))
 |                              {
 |                                  Name (PIB1, Buffer (0x0E)


[WARN]-Not all control paths return a value (_GTM)

Not all control paths return a value (_GTM)
At line #10211 of DSDT.dsl:

 |                  }
 |  
 |                  Device (SECD)
 |                  {
 |                      Name (_ADR, One)
>>>                     Method (_GTM, 0, NotSerialized)
 |                      {
 |                          If (LEqual (SCFG, Zero))
 |                          {
 |                              Name (SBUF, Buffer (0x14)


[WARN]-Reserved method must return a value (_GTM)

Reserved method must return a value (_GTM)
At line #10211 of DSDT.dsl:

 |                  }
 |  
 |                  Device (SECD)
 |                  {
 |                      Name (_ADR, One)
>>>                     Method (_GTM, 0, NotSerialized)
 |                      {
 |                          If (LEqual (SCFG, Zero))
 |                          {
 |                              Name (SBUF, Buffer (0x14)


[WARN]-Not all control paths return a value (_GTF)

Not all control paths return a value (_GTF)
At line #10371 of DSDT.dsl:

 |                      }
 |  
 |                      Device (S_D0)
 |                      {
 |                          Name (_ADR, Zero)
>>>                         Method (_GTF, 0, NotSerialized)
 |                          {
 |                              If (LEqual (SCFG, Zero))
 |                              {
 |                                  Name (SIB0, Buffer (0x0E)


[WARN]-Reserved method must return a value (_GTF)

Reserved method must return a value (_GTF)
At line #10371 of DSDT.dsl:

 |                      }
 |  
 |                      Device (S_D0)
 |                      {
 |                          Name (_ADR, Zero)
>>>                         Method (_GTF, 0, NotSerialized)
 |                          {
 |                              If (LEqual (SCFG, Zero))
 |                              {
 |                                  Name (SIB0, Buffer (0x0E)


[WARN]-Not all control paths return a value (_GTF)

Not all control paths return a value (_GTF)
At line #10439 of DSDT.dsl:

 |                      }
 |  
 |                      Device (S_D1)
 |                      {
 |                          Name (_ADR, One)
>>>                         Method (_GTF, 0, NotSerialized)
 |                          {
 |                              If (LEqual (SCFG, Zero))
 |                              {
 |                                  Name (SIB1, Buffer (0x0E)


[WARN]-Reserved method must return a value (_GTF)

Reserved method must return a value (_GTF)
At line #10439 of DSDT.dsl:

 |                      }
 |  
 |                      Device (S_D1)
 |                      {
 |                          Name (_ADR, One)
>>>                         Method (_GTF, 0, NotSerialized)
 |                          {
 |                              If (LEqual (SCFG, Zero))
 |                              {
 |                                  Name (SIB1, Buffer (0x0E)


[PASS]-Tested table DSDT.dsl

[PASS]-Tested table SSDT.dsl

=================================================
* Plugin name: pciresource
* Result: FAIL

* Title: Validate assigned PCI resources
* Description: This test is currently a placeholder and just checks the kernel log for complaints about PCI resource errors. In the future the idea is to actually perform a validation step on all PCI resources against a certain rule-set.
================================================

[FAIL]-HPET resources incorrect

hpet_resources: 0xfed00000 is busy

=================================================
* Plugin name: thermal_trip
* Result: FAIL

* Title: ACPI passive thermal trip points
* Description: This test determines if the passive trip point works as expected.
================================================

[FAIL]-Changing passive trip point seems uneffective in Zone TZ01.

=================================================
* Plugin name: cpufreq
* Result: FAIL

* Title: CPU frequency scaling tests (1-2 mins)
* Description: For each processor in the system, this test steps through the various frequency states (P-states) that the BIOS advertises for the processor. For each processor/frequency combination, a quick performance value is measured. The test then validates that: 
  1) Each processor has the same number of frequency states
  2) Higher advertised frequencies have a higher performance
  3) No duplicate frequency values are reported by the BIOS
  4) Is BIOS wrongly doing Sw_All P-state coordination across cores
  5) Is BIOS wrongly doing Sw_Any P-state coordination across cores

================================================

[INFO]-4 CPU frequency steps supported

 Frequency | Speed 
-----------+---------
  2.32 Ghz | 100.0 %
  2.32 Ghz |  94.8 %
  1.65 Ghz |  67.4 %
   800 Mhz |  34.0 %


[FAIL]-Processors are set to SW_ANY

[FAIL]-Firmware not implementing hardware coordination cleanly. Firmware using SW_ALL instead?


[FAIL]-Firmware not implementing hardware coordination cleanly. Firmware using SW_ANY instead?


=================================================
* Plugin name: dmi
* Result: FAIL

* Title: DMI information check
* Description: This test checks the DMI/SMBIOS tables for common errors.
================================================

[FAIL]-No SMBIOS nor DMI entry point found.

[FAIL]-No SMBIOS nor DMI entry point found.

=================================================
* Plugin name: maxreadreq
* Result: WARN

* Title: PCI Express MaxReadReq tuning
* Description: This test checks if the firmware has set MaxReadReq to a higher value on non-montherboard devices
================================================

[WARN]-MaxReadReq for device pci://00:00:1b.0 is low (128)

=================================================
* Plugin name: edd
* Result: WARN

* Title: EDD Boot disk hinting
* Description: This test verifies if the BIOS directs the operating system on which storage device to use for booting (EDD information). This is important for systems that (can) have multiple disks. Linux distributions increasingly depend on this info to find out on which device to install the bootloader.
================================================

[INFO]-device 80: The system boots from device 0000:00:1d.7 channel: 128 serial_number: 303037301e5013fe 


[WARN]-device 80: No matching MBR signature (0x00078c14) found for the boot disk

Device sdb - signature 0x78c14


[INFO]-device 81 is provided by device 0000:00:1f.2 channel: 0 device: 0 


[WARN]-device 81: No matching MBR signature (0x00098e56) found for this disk

Device sdb - signature 0x78c14


=================================================
* Plugin name: battery
* Result: WARN

* Title: Battery tests
* Description: This test reports which (if any) batteries there are in the system. In addition, for charging or discharging batteries, the test validates that the reported 'current capacity' properly increments/decrements in line with the charge/discharge state. 

This test also stresses the entire battery state reporting codepath in the ACPI BIOS, and any warnings given by the ACPI interpreter will be reported.
================================================

[WARN]-Battery present but name or state unsupported

/proc/acpi/battery/BAT0/info

=================================================
* Plugin name: fan
* Result: WARN

* Title: Fan tests
* Description: This test reports how many fans there are in the system. It also checks for the current status of the fan(s).
================================================

[WARN]-No fan information present

=================================================
* Plugin name: chk_hpet
* Result: WARN

* Title: HPET configuration test
* Description: This test checks the HPET PCI BAR for each timer block in the timer.The base address is passed by the firmware via an ACPI table.IRQ routing and initialization is also verified by the test.
================================================

[WARN]-HPET driver in the kernel is enabled, inaccurate results follow.

[INFO]-HPET found, VendorID is: 8086

=================================================
* Plugin name: acpiinfo
* Result: INFO

* Title: General ACPI information
* Description: This test checks the output of the in-kernel ACPI CA against common error messages that indicate a bad interaction with the bios, including those that point at AML syntax errors.
================================================

[INFO]-DSDT was compiled by the Microsoft AML compiler

ACPI: DSDT B9FEE000, A006 (r1 QUANTA WTW8            1 MSFT  1000013)

=================================================
* Plugin name: DMAR
* Result: INFO

* Title: (experimental) DMA Remapping (VT-d) test
* Description: Verify if DMA remapping is sane.
================================================

[INFO]-No DMAR ACPI table found.

=================================================
* Plugin name: mtrr
* Result: PASS

* Title: MTRR validation
* Description: This test validates the MTRR setup against the memory map to detect any inconsistencies in cachability.
================================================

=================================================
* Plugin name: SUN
* Result: PASS

* Title: SUN duplicate test
* Description: This makes sure that each SUN (Slot Unique Number) that is called in the DSDT through the Name() method is unique, no duplicates should be found.
================================================

[PASS]-Tested _SUN ids, successfully found no duplicates

=================================================
* Plugin name: virt
* Result: PASS

* Title: VT/VMX Virtualization extensions
* Description: This test checks if VT/VMX is set up correctly
================================================

=================================================
* Plugin name: ebda
* Result: PASS

* Title: EBDA region
* Description: This test validates if the EBDA region is mapped and reserved in the E820 table.
================================================

[PASS]-EBDA region is correctly reserved in the E820 table.

=================================================
* Plugin name: os2gap
* Result: PASS

* Title: OS/2 memory hole test
* Description: This test checks if the OS/2 15Mb memory hole is absent
================================================

[PASS]-Successfully found no 15mb memory hole

=================================================
* Plugin name: ethernet
* Result: PASS

* Title: Ethernet functionality
* Description: This test is currently a placeholder for a more advanced ethernet test. Currently the only check performed is that a link is acquired within 45 seconds of enabling the interface. 45 seconds is close to the value most Linux distributions use as timeout value.

In the future the plan is to also perform actual data transfer tests as part of the ethernet test, to validate interrupt routing and other per-NIC behaviors.
================================================

=================================================
* Plugin name: apicedge
* Result: PASS

* Title: (experimental) APIC Edge/Level check
* Description: This test checks if legacy interrupts are edge and PCI interrupts are level
================================================

=================================================
* Plugin name: microcode
* Result: PASS

* Title: Processor microcode update
* Description: This test verifies if the firmware has put a recent version of the microcode into the processor at boot time. Recent microcode is important to have all the required features and errata updates for the processor.
================================================
J'espere que c'est bien ce que tu souhaites avoir comme information?
x86_64 | KDE | Clavier Bépo
lecbee
Hankyu
Messages : 17
Inscription : dim. 03 juil. 2011, 17:35

Re: [DB] BIOS - ACPI - collecte d'infos

Message par lecbee »

Distag a écrit :J'espere que c'est bien ce que tu souhaites avoir comme information?
Impeccable !
Avatar de l’utilisateur
G4l
Hankyu
Messages : 19
Inscription : lun. 13 sept. 2010, 13:54

Re: [DB] BIOS - ACPI - collecte d'infos

Message par G4l »

Bonjour, une tour monter soi-même (Carte mère : ASRock G31M-(G)S) :

Code : Tout sélectionner

sudo acpixtract -l acpi

Could not open acpi
(Code de retour bizzard...)

Code : Tout sélectionner

sudo dmidecode

# dmidecode 2.11
SMBIOS 2.4 present.
22 structures occupying 1127 bytes.
Table at 0x000FC200.

Handle 0x0000, DMI type 0, 24 bytes
BIOS Information
	Vendor: American Megatrends Inc.
	Version: P1.60
	Release Date: 07/08/2009
	Address: 0xF0000
	Runtime Size: 64 kB
	ROM Size: 512 kB
	Characteristics:
		PCI is supported
		BIOS is upgradeable
		BIOS shadowing is allowed
		Boot from CD is supported
		Selectable boot is supported
		BIOS ROM is socketed
		EDD is supported
		5.25"/1.2 MB floppy services are supported (int 13h)
		3.5"/720 kB floppy services are supported (int 13h)
		3.5"/2.88 MB floppy services are supported (int 13h)
		Print screen service is supported (int 5h)
		8042 keyboard services are supported (int 9h)
		Serial services are supported (int 14h)
		Printer services are supported (int 17h)
		CGA/mono video services are supported (int 10h)
		ACPI is supported
		USB legacy is supported
		LS-120 boot is supported
		ATAPI Zip drive boot is supported
		BIOS boot specification is supported
		Function key-initiated network boot is supported
		Targeted content distribution is supported
	BIOS Revision: 8.14

Handle 0x0001, DMI type 1, 27 bytes
System Information
	Manufacturer: To Be Filled By O.E.M.
	Product Name: To Be Filled By O.E.M.
	Version: To Be Filled By O.E.M.
	Serial Number: To Be Filled By O.E.M.
	UUID: 00020003-0004-0005-0006-000700080009
	Wake-up Type: Power Switch
	SKU Number: To Be Filled By O.E.M.
	Family: To Be Filled By O.E.M.

Handle 0x0002, DMI type 2, 15 bytes
Base Board Information
	Manufacturer: ASRock
	Product Name: G31M-GS   
	Version:                       
	Serial Number:                       
	Asset Tag:                       
	Features:
		Board is a hosting board
		Board is replaceable
	Location In Chassis:                       
	Chassis Handle: 0x0003
	Type: Motherboard
	Contained Object Handles: 0

Handle 0x0003, DMI type 3, 21 bytes
Chassis Information
	Manufacturer: To Be Filled By O.E.M.
	Type: Desktop
	Lock: Not Present
	Version: To Be Filled By O.E.M.
	Serial Number: To Be Filled By O.E.M.
	Asset Tag: To Be Filled By O.E.M.
	Boot-up State: Safe
	Power Supply State: Safe
	Thermal State: Safe
	Security Status: None
	OEM Information: 0x00000000
	Height: Unspecified
	Number Of Power Cords: 1
	Contained Elements: 0

Handle 0x0004, DMI type 4, 35 bytes
Processor Information
	Socket Designation: CPUSocket
	Type: Central Processor
	Family: Quad-Core Xeon 3200
	Manufacturer: Intel            
	ID: 7A 06 01 00 FF FB EB BF
	Signature: Type 0, Family 6, Model 23, Stepping 10
	Flags:
		FPU (Floating-point unit on-chip)
		VME (Virtual mode extension)
		DE (Debugging extension)
		PSE (Page size extension)
		TSC (Time stamp counter)
		MSR (Model specific registers)
		PAE (Physical address extension)
		MCE (Machine check exception)
		CX8 (CMPXCHG8 instruction supported)
		APIC (On-chip APIC hardware supported)
		SEP (Fast system call)
		MTRR (Memory type range registers)
		PGE (Page global enable)
		MCA (Machine check architecture)
		CMOV (Conditional move instruction supported)
		PAT (Page attribute table)
		PSE-36 (36-bit page size extension)
		CLFSH (CLFLUSH instruction supported)
		DS (Debug store)
		ACPI (ACPI supported)
		MMX (MMX technology supported)
		FXSR (FXSAVE and FXSTOR instructions supported)
		SSE (Streaming SIMD extensions)
		SSE2 (Streaming SIMD extensions 2)
		SS (Self-snoop)
		HTT (Multi-threading)
		TM (Thermal monitor supported)
		PBE (Pending break enabled)
	Version: Intel(R) Celeron(R) CPU        E3200  @ 2.40GHz     
	Voltage: 1.3 V
	External Clock: 200 MHz
	Max Speed: 2400 MHz
	Current Speed: 2400 MHz
	Status: Populated, Enabled
	Upgrade: Other
	L1 Cache Handle: 0x0005
	L2 Cache Handle: 0x0006
	L3 Cache Handle: Not Provided
	Serial Number: To Be Filled By O.E.M.
	Asset Tag: To Be Filled By O.E.M.
	Part Number: To Be Filled By O.E.M.

Handle 0x0005, DMI type 7, 19 bytes
Cache Information
	Socket Designation: L1-Cache
	Configuration: Enabled, Not Socketed, Level 1
	Operational Mode: Write Back
	Location: Internal
	Installed Size: 64 kB
	Maximum Size: 64 kB
	Supported SRAM Types:
		Other
	Installed SRAM Type: Other
	Speed: Unknown
	Error Correction Type: Parity
	System Type: Data
	Associativity: 8-way Set-associative

Handle 0x0006, DMI type 7, 19 bytes
Cache Information
	Socket Designation: L2-Cache
	Configuration: Enabled, Not Socketed, Level 2
	Operational Mode: Write Back
	Location: Internal
	Installed Size: 1024 kB
	Maximum Size: 1024 kB
	Supported SRAM Types:
		Other
	Installed SRAM Type: Other
	Speed: Unknown
	Error Correction Type: Single-bit ECC
	System Type: Unified
	Associativity: 4-way Set-associative

Handle 0x0007, DMI type 5, 20 bytes
Memory Controller Information
	Error Detecting Method: 64-bit ECC
	Error Correcting Capabilities:
		None
	Supported Interleave: One-way Interleave
	Current Interleave: One-way Interleave
	Maximum Memory Module Size: 4096 MB
	Maximum Total Memory Size: 8192 MB
	Supported Speeds:
		Other
	Supported Memory Types:
		DIMM
		SDRAM
	Memory Module Voltage: 3.3 V
	Associated Memory Slots: 2
		0x0008
		0x0009
	Enabled Error Correcting Capabilities:
		None

Handle 0x0008, DMI type 6, 12 bytes
Memory Module Information
	Socket Designation: DIMM0
	Bank Connections: 0 1
	Current Speed: Unknown
	Type: DIMM SDRAM
	Installed Size: 1024 MB (Single-bank Connection)
	Enabled Size: 1024 MB (Single-bank Connection)
	Error Status: OK

Handle 0x0009, DMI type 6, 12 bytes
Memory Module Information
	Socket Designation: DIMM1
	Bank Connections: 4 5
	Current Speed: Unknown
	Type: DIMM SDRAM
	Installed Size: 1024 MB (Single-bank Connection)
	Enabled Size: 1024 MB (Single-bank Connection)
	Error Status: OK

Handle 0x000A, DMI type 9, 13 bytes
System Slot Information
	Designation: PCI1
	Type: 32-bit PCI
	Current Usage: Available
	Length: Short
	ID: 1
	Characteristics:
		3.3 V is provided
		Opening is shared
		PME signal is supported

Handle 0x000B, DMI type 9, 13 bytes
System Slot Information
	Designation: PCI2
	Type: 32-bit PCI
	Current Usage: Available
	Length: Short
	ID: 2
	Characteristics:
		3.3 V is provided
		Opening is shared
		PME signal is supported

Handle 0x000C, DMI type 9, 13 bytes
System Slot Information
	Designation: PCIE1
	Type: x16 PCI Express
	Current Usage: Available
	Length: Short
	ID: 17
	Characteristics:
		3.3 V is provided
		Opening is shared
		PME signal is supported

Handle 0x000D, DMI type 9, 13 bytes
System Slot Information
	Designation: PCIE2
	Type: x1 PCI Express
	Current Usage: In Use
	Length: Short
	ID: 18
	Characteristics:
		3.3 V is provided
		Opening is shared
		PME signal is supported

Handle 0x000E, DMI type 16, 15 bytes
Physical Memory Array
	Location: System Board Or Motherboard
	Use: System Memory
	Error Correction Type: None
	Maximum Capacity: 4 GB
	Error Information Handle: Not Provided
	Number Of Devices: 2

Handle 0x000F, DMI type 19, 15 bytes
Memory Array Mapped Address
	Starting Address: 0x00000000000
	Ending Address: 0x0007FFFFFFF
	Range Size: 2 GB
	Physical Array Handle: 0x000E
	Partition Width: 4

Handle 0x0010, DMI type 17, 27 bytes
Memory Device
	Array Handle: 0x000E
	Error Information Handle: Not Provided
	Total Width: 64 bits
	Data Width: 64 bits
	Size: 1024 MB
	Form Factor: DIMM
	Set: None
	Locator: DIMM0
	Bank Locator: BANK0
	Type: SDRAM
	Type Detail: Synchronous
	Speed: Unknown
	Manufacturer: Manufacturer0
	Serial Number: SerNum0
	Asset Tag: AssetTagNum0
	Part Number: PartNum0

Handle 0x0011, DMI type 20, 19 bytes
Memory Device Mapped Address
	Starting Address: 0x00000000000
	Ending Address: 0x0003FFFFFFF
	Range Size: 1 GB
	Physical Device Handle: 0x0010
	Memory Array Mapped Address Handle: 0x000F
	Partition Row Position: 1
	Interleaved Data Depth: 1

Handle 0x0012, DMI type 17, 27 bytes
Memory Device
	Array Handle: 0x000E
	Error Information Handle: Not Provided
	Total Width: 64 bits
	Data Width: 64 bits
	Size: 1024 MB
	Form Factor: DIMM
	Set: None
	Locator: DIMM1
	Bank Locator: BANK1
	Type: SDRAM
	Type Detail: Synchronous
	Speed: Unknown
	Manufacturer: Manufacturer1
	Serial Number: SerNum1
	Asset Tag: AssetTagNum1
	Part Number: PartNum1

Handle 0x0013, DMI type 20, 19 bytes
Memory Device Mapped Address
	Starting Address: 0x00040000000
	Ending Address: 0x0007FFFFFFF
	Range Size: 1 GB
	Physical Device Handle: 0x0012
	Memory Array Mapped Address Handle: 0x000F
	Partition Row Position: 1
	Interleaved Data Depth: 1

Handle 0x0014, DMI type 32, 20 bytes
System Boot Information
	Status: No errors detected

Handle 0x0015, DMI type 127, 4 bytes
End Of Table


Et le test Live

Code : Tout sélectionner

-------------------------------------------------
  Date: Thu Jul 14 10:52:51 2011                                       
*                                               *
* Firmwarekit (release 3)                       *
* http://www.linuxfirmwarekit.org               *
*                                               *
*                                               *
* For more information on test descriptions     *
* and details on what the PASS/INFO/WARN/FAIL   *
* results mean, go to: Documentation/TestsInfo. *
*                                               *
-------------------------------------------------

KERNEL VERSION: Linux testmachine 2.6.18-1.2798.fc6 #1 SMP Mon Oct 16 14:37:32 EDT 2006 i686 i686 i386 GNU/Linux


SUMMARY:  4 Fails, 5 Warns, 11 Pass, 20 Total

=================================================
* Plugin name: pciresource
* Result: FAIL

* Title: Validate assigned PCI resources
* Description: This test is currently a placeholder and just checks the kernel log for complaints about PCI resource errors. In the future the idea is to actually perform a validation step on all PCI resources against a certain rule-set.
================================================

[FAIL]-HPET resources incorrect

hpet_resources: 0xfed00000 is busy

=================================================
* Plugin name: edd
* Result: FAIL

* Title: EDD Boot disk hinting
* Description: This test verifies if the BIOS directs the operating system on which storage device to use for booting (EDD information). This is important for systems that (can) have multiple disks. Linux distributions increasingly depend on this info to find out on which device to install the bootloader.
================================================

[FAIL]-Boot device 0x80 does not support EDD


=================================================
* Plugin name: cpufreq
* Result: FAIL

* Title: CPU frequency scaling tests (1-2 mins)
* Description: For each processor in the system, this test steps through the various frequency states (P-states) that the BIOS advertises for the processor. For each processor/frequency combination, a quick performance value is measured. The test then validates that: 
  1) Each processor has the same number of frequency states
  2) Higher advertised frequencies have a higher performance
  3) No duplicate frequency values are reported by the BIOS
  4) Is BIOS wrongly doing Sw_All P-state coordination across cores
  5) Is BIOS wrongly doing Sw_Any P-state coordination across cores

================================================

[INFO]-4 CPU frequency steps supported

 Frequency | Speed 
-----------+---------
  2.45 Ghz | 100.0 %
  2.05 Ghz |  83.3 %
  1.65 Ghz |  66.7 %
  1203 Mhz |  50.0 %


[PASS]-P-state coordination done by Harware

[FAIL]-Firmware not implementing hardware coordination cleanly. Firmware using SW_ALL instead?


[FAIL]-Firmware not implementing hardware coordination cleanly. Firmware using SW_ANY instead?


=================================================
* Plugin name: dmi
* Result: FAIL

* Title: DMI information check
* Description: This test checks the DMI/SMBIOS tables for common errors.
================================================

[FAIL]-No SMBIOS nor DMI entry point found.

[FAIL]-No SMBIOS nor DMI entry point found.

[FAIL]-No SMBIOS nor DMI entry point found.

[FAIL]-No SMBIOS nor DMI entry point found.

[FAIL]-No SMBIOS nor DMI entry point found.

[FAIL]-No SMBIOS nor DMI entry point found.

[FAIL]-No SMBIOS nor DMI entry point found.

[FAIL]-No SMBIOS nor DMI entry point found.

[FAIL]-No SMBIOS nor DMI entry point found.

[FAIL]-No SMBIOS nor DMI entry point found.

[FAIL]-No SMBIOS nor DMI entry point found.

[FAIL]-No SMBIOS nor DMI entry point found.

[FAIL]-No SMBIOS nor DMI entry point found.

[FAIL]-No SMBIOS nor DMI entry point found.

=================================================
* Plugin name: acpicompile
* Result: WARN

* Title: DSDT AML verification
* Description: This test first disassembles the DSDT of the BIOS, and then uses the IASL compiler from Intel to recompile the code. The IASL copiler is much stricter in detecting deviations from the ACPI specification and can find numerous defects that other AML compilers cannot find. Fixing these defects increases the probability that the BIOS will operate well with a variety of operating systems.
================================================

[WARN]-Possible operator timeout is ignored

Possible operator timeout is ignored
At line #5424 of DSDT.dsl:

 |  Name (XSST, 0x1A)
 |  Name (XRCT, 0x1C)
 |  Mutex (MUTE, 0x00)
 |  Method (RBPE, 1, NotSerialized)
 |  {
>>>     Acquire (MUTE, 0x03E8)
 |      Add (Arg0, PCIB, Local0)
 |      OperationRegion (PCFG, SystemMemory, Local0, One)
 |      Field (PCFG, ByteAcc, NoLock, Preserve)
 |      {


[WARN]-Possible operator timeout is ignored

Possible operator timeout is ignored
At line #5438 of DSDT.dsl:

 |              Return (XCFG)
 |          }
 |  
 |          Method (RWPE, 1, NotSerialized)
 |          {
>>>             Acquire (MUTE, 0x03E8)
 |              And (Arg0, 0xFFFFFFFE, Arg0)
 |              Add (Arg0, PCIB, Local0)
 |              OperationRegion (PCFG, SystemMemory, Local0, 0x02)
 |              Field (PCFG, WordAcc, NoLock, Preserve)


[WARN]-Possible operator timeout is ignored

Possible operator timeout is ignored
At line #5453 of DSDT.dsl:

 |              Return (XCFG)
 |          }
 |  
 |          Method (RDPE, 1, NotSerialized)
 |          {
>>>             Acquire (MUTE, 0x03E8)
 |              And (Arg0, 0xFFFFFFFC, Arg0)
 |              Add (Arg0, PCIB, Local0)
 |              OperationRegion (PCFG, SystemMemory, Local0, 0x04)
 |              Field (PCFG, DWordAcc, NoLock, Preserve)


[WARN]-Possible operator timeout is ignored

Possible operator timeout is ignored
At line #5468 of DSDT.dsl:

 |              Return (XCFG)
 |          }
 |  
 |          Method (WBPE, 2, NotSerialized)
 |          {
>>>             Acquire (MUTE, 0x0FFF)
 |              Add (Arg0, PCIB, Local0)
 |              OperationRegion (PCFG, SystemMemory, Local0, One)
 |              Field (PCFG, ByteAcc, NoLock, Preserve)
 |              {


[WARN]-Possible operator timeout is ignored

Possible operator timeout is ignored
At line #5482 of DSDT.dsl:

 |              Release (MUTE)
 |          }
 |  
 |          Method (WWPE, 2, NotSerialized)
 |          {
>>>             Acquire (MUTE, 0x03E8)
 |              And (Arg0, 0xFFFFFFFE, Arg0)
 |              Add (Arg0, PCIB, Local0)
 |              OperationRegion (PCFG, SystemMemory, Local0, 0x02)
 |              Field (PCFG, WordAcc, NoLock, Preserve)


[WARN]-Possible operator timeout is ignored

Possible operator timeout is ignored
At line #5497 of DSDT.dsl:

 |              Release (MUTE)
 |          }
 |  
 |          Method (WDPE, 2, NotSerialized)
 |          {
>>>             Acquire (MUTE, 0x03E8)
 |              And (Arg0, 0xFFFFFFFC, Arg0)
 |              Add (Arg0, PCIB, Local0)
 |              OperationRegion (PCFG, SystemMemory, Local0, 0x04)
 |              Field (PCFG, DWordAcc, NoLock, Preserve)


[WARN]-Possible operator timeout is ignored

Possible operator timeout is ignored
At line #5512 of DSDT.dsl:

 |              Release (MUTE)
 |          }
 |  
 |          Method (RWDP, 3, NotSerialized)
 |          {
>>>             Acquire (MUTE, 0x03E8)
 |              And (Arg0, 0xFFFFFFFC, Arg0)
 |              Add (Arg0, PCIB, Local0)
 |              OperationRegion (PCFG, SystemMemory, Local0, 0x04)
 |              Field (PCFG, DWordAcc, NoLock, Preserve)


[PASS]-Tested table DSDT.dsl

[PASS]-Tested table SSDT.dsl

=================================================
* Plugin name: maxreadreq
* Result: WARN

* Title: PCI Express MaxReadReq tuning
* Description: This test checks if the firmware has set MaxReadReq to a higher value on non-montherboard devices
================================================

[WARN]-MaxReadReq for device pci://00:00:1b.0 is low (128)

[WARN]-MaxReadReq for device pci://00:04:00.0 is low (128)

[WARN]-MaxReadReq for device pci://00:04:00.1 is low (128)

=================================================
* Plugin name: thermal_trip
* Result: WARN

* Title: ACPI passive thermal trip points
* Description: This test determines if the passive trip point works as expected.
================================================

[WARN]-No thermal zones found.

=================================================
* Plugin name: fan
* Result: WARN

* Title: Fan tests
* Description: This test reports how many fans there are in the system. It also checks for the current status of the fan(s).
================================================

[WARN]-No fan information present

=================================================
* Plugin name: chk_hpet
* Result: WARN

* Title: HPET configuration test
* Description: This test checks the HPET PCI BAR for each timer block in the timer.The base address is passed by the firmware via an ACPI table.IRQ routing and initialization is also verified by the test.
================================================

[WARN]-HPET driver in the kernel is enabled, inaccurate results follow.

[INFO]-HPET found, VendorID is: 8086

=================================================
* Plugin name: battery
* Result: INFO

* Title: Battery tests
* Description: This test reports which (if any) batteries there are in the system. In addition, for charging or discharging batteries, the test validates that the reported 'current capacity' properly increments/decrements in line with the charge/discharge state. 

This test also stresses the entire battery state reporting codepath in the ACPI BIOS, and any warnings given by the ACPI interpreter will be reported.
================================================

[INFO]-No battery information present

=================================================
* Plugin name: acpiinfo
* Result: INFO

* Title: General ACPI information
* Description: This test checks the output of the in-kernel ACPI CA against common error messages that indicate a bad interaction with the bios, including those that point at AML syntax errors.
================================================

[INFO]-DSDT was compiled by the Intel AML compiler

ACPI: DSDT (v001  AS166 AS166151 0x00000151 INTL 0x20051117) @ 0x00000000

=================================================
* Plugin name: DMAR
* Result: INFO

* Title: (experimental) DMA Remapping (VT-d) test
* Description: Verify if DMA remapping is sane.
================================================

[INFO]-No DMAR ACPI table found.

=================================================
* Plugin name: microcode
* Result: INFO

* Title: Processor microcode update
* Description: This test verifies if the firmware has put a recent version of the microcode into the processor at boot time. Recent microcode is important to have all the required features and errata updates for the processor.
================================================

[INFO]-Kernel too old; the kernel does not export microcode version

This test needs a 2.6.19-rc1 kernel or later to function

[INFO]-Kernel too old; the kernel does not export microcode version

This test needs a 2.6.19-rc1 kernel or later to function

=================================================
* Plugin name: mtrr
* Result: PASS

* Title: MTRR validation
* Description: This test validates the MTRR setup against the memory map to detect any inconsistencies in cachability.
================================================

=================================================
* Plugin name: SUN
* Result: PASS

* Title: SUN duplicate test
* Description: This makes sure that each SUN (Slot Unique Number) that is called in the DSDT through the Name() method is unique, no duplicates should be found.
================================================

[PASS]-Tested _SUN ids, successfully found no duplicates

=================================================
* Plugin name: virt
* Result: PASS

* Title: VT/VMX Virtualization extensions
* Description: This test checks if VT/VMX is set up correctly
================================================

=================================================
* Plugin name: ebda
* Result: PASS

* Title: EBDA region
* Description: This test validates if the EBDA region is mapped and reserved in the E820 table.
================================================

[PASS]-EBDA region is correctly reserved in the E820 table.

=================================================
* Plugin name: os2gap
* Result: PASS

* Title: OS/2 memory hole test
* Description: This test checks if the OS/2 15Mb memory hole is absent
================================================

[PASS]-Successfully found no 15mb memory hole

=================================================
* Plugin name: ethernet
* Result: PASS

* Title: Ethernet functionality
* Description: This test is currently a placeholder for a more advanced ethernet test. Currently the only check performed is that a link is acquired within 45 seconds of enabling the interface. 45 seconds is close to the value most Linux distributions use as timeout value.

In the future the plan is to also perform actual data transfer tests as part of the ethernet test, to validate interrupt routing and other per-NIC behaviors.
================================================

=================================================
* Plugin name: apicedge
* Result: PASS

* Title: (experimental) APIC Edge/Level check
* Description: This test checks if legacy interrupts are edge and PCI interrupts are level
================================================


Voilà, en espèrant que ça t'aidera

Edit : Je ne peut pas poster le acpidump, trop de caractère XD
lecbee
Hankyu
Messages : 17
Inscription : dim. 03 juil. 2011, 17:35

Re: [DB] BIOS - ACPI - collecte d'infos

Message par lecbee »

Merci !
G4l a écrit : (Code de retour bizzard...)
[...]
Edit : Je ne peut pas poster le acpidump, trop de caractère XD
La première commande "acpidump" envoi tout dans le fichier "acpi". La 2ème commande n'extrait que les infos utiles de ce fichier. Ça doit faire une dizaine de ligne.
Avatar de l’utilisateur
G4l
Hankyu
Messages : 19
Inscription : lun. 13 sept. 2010, 13:54

Re: [DB] BIOS - ACPI - collecte d'infos

Message par G4l »

Ah ! Ok, pas compris la relation XD

Voilà :

Code : Tout sélectionner

acpixtract -l acpi.dump 

Signature Length Revision  OemId     OemTableId   OemRevision CompilerId CompilerRevision

    DSDT   22081     01    "AS166 "  "AS166151"    00000151    "INTL"     20051117
    FACS      64
    FACP     132     01    "A_M_I "  "OEMFACP "    12000601    "MSFT"     00000097
    APIC     108     01    "070809"  "APIC1512"    20090708    "MSFT"     00000097
    MCFG      60     01    "070809"  "OEMMCFG "    20090708    "MSFT"     00000097
    OEMB     113     01    "070809"  "OEMB1512"    20090708    "MSFT"     00000097
    AAFT      39     01    "070809"  "OEMAAFT "    20090708    "MSFT"     00000097
    HPET      56     01    "070809"  "OEMHPET "    20090708    "MSFT"     00000097
    GSCI    8228     01    "070809"  "GMCHSCI "    20090708    "MSFT"     00000097
    SSDT    2684     01    "DpgPmm"  "CpuPm   "    00000012    "INTL"     20051117
    RSDT      68     01    "070809"  "RSDT1512"    20090708    "MSFT"     00000097
    RSDP                   "ACPIAM"

Found 12 ACPI tables [20110225]
lecbee
Hankyu
Messages : 17
Inscription : dim. 03 juil. 2011, 17:35

Re: [DB] BIOS - ACPI - collecte d'infos

Message par lecbee »

Voilà.
lecbee
Hankyu
Messages : 17
Inscription : dim. 03 juil. 2011, 17:35

Re: [DB] BIOS - ACPI - collecte d'infos

Message par lecbee »

Super, j'ai de plus en plus de données du Linux-ready Firmware Kit, ça devient intéressant.

Pour info, ta carte mère est supportée par flashrom ( http://www.flashrom.org/Supported_hardware ).
Tu pourras mettre à jour ton BIOS depuis Linux aussi simplement que ça :
# flashrom --write le_nouveau_bios.rom

:D
Avatar de l’utilisateur
la_poigne
yeomen
Messages : 215
Inscription : dim. 22 févr. 2009, 09:20

Re: [DB] BIOS - ACPI - collecte d'infos

Message par la_poigne »

Bonjour,

voici mes resultats sur une carte mère MSI MS-7255

# acpidump > acpi : Wrong checksum for generic table!
# acpixtract -l acpi :

Code : Tout sélectionner

Signature Length Revision  OemId     OemTableId   OemRevision CompilerId CompilerRevision

    DSDT   20960     01    "A7255 "  "A725500D"    0000000D    "INTL"     02002026
    FACS      64
    FACP     132     02    "A M I "  "OEMFACP "    05000710    "MSFT"     00000097
    APIC     120     01    "A M I "  "OEMAPIC "    05000710    "MSFT"     00000097
    MCFG      60     01    "A M I "  "OEMMCFG "    05000710    "MSFT"     00000097
    OEMB      96     01    "A M I "  "AMI_OEM "    05000710    "MSFT"     00000097
    HPET      56     01    "A M I "  "VT-8237A"    05000710    "MSFT"     00000097
    RSDT      56     01    "A M I "  "OEMRSDT "    05000710    "MSFT"     00000097
    RSDP                   "ACPIAM"

Found 9 ACPI tables [20110225]
# dmidecode :

Code : Tout sélectionner

#Base Board Information
	Manufacturer: Micro-Star
	Product Name: MS-7255 V2.0
	Version: 2.0
#linuxfirmwarekit:

Code : Tout sélectionner

-------------------------------------------------
  Date: Fri Jul 15 04:07:08 2011                                       
*                                               *
* Firmwarekit (release 3)                       *
* http://www.linuxfirmwarekit.org               *
*                                               *
*                                               *
* For more information on test descriptions     *
* and details on what the PASS/INFO/WARN/FAIL   *
* results mean, go to: Documentation/TestsInfo. *
*                                               *
-------------------------------------------------

KERNEL VERSION: Linux testmachine 2.6.22.9 #1 SMP Mon Oct 1 15:17:15 PDT 2007 i686 i686 i386 GNU/Linux


SUMMARY:  3 Fails, 6 Warns, 11 Pass, 20 Total

=================================================
* Plugin name: chk_hpet
* Result: FAIL

* Title: HPET configuration test
* Description: This test checks the HPET PCI BAR for each timer block in the timer.The base address is passed by the firmware via an ACPI table.IRQ routing and initialization is also verified by the test.
================================================

[WARN]-HPET driver in the kernel is enabled, inaccurate results follow.

[FAIL]-Mismatched HPET base between DSDT and the kernel

Mismatched HPET base between DSDT (fed00000) and the kernel f)

[FAIL]-Mismatched HPET base between DSDT and the kernel

Mismatched HPET base between DSDT (fed00000) and the kernel 400)

[FAIL]-Mismatched HPET base between DSDT and the kernel

Mismatched HPET base between DSDT (fed00000) and the kernel 88)

2000 lignes du même FAIL .....

[INFO]-HPET found, VendorID is: 1106

=================================================
* Plugin name: dmi
* Result: FAIL

* Title: DMI information check
* Description: This test checks the DMI/SMBIOS tables for common errors.
================================================

[FAIL]-No SMBIOS nor DMI entry point found.

[FAIL]-No SMBIOS nor DMI entry point found.

[FAIL]-No SMBIOS nor DMI entry point found.

[FAIL]-No SMBIOS nor DMI entry point found.

[FAIL]-No SMBIOS nor DMI entry point found.

[FAIL]-No SMBIOS nor DMI entry point found.

[FAIL]-No SMBIOS nor DMI entry point found.

[FAIL]-No SMBIOS nor DMI entry point found.

[FAIL]-No SMBIOS nor DMI entry point found.

[FAIL]-No SMBIOS nor DMI entry point found.

[FAIL]-No SMBIOS nor DMI entry point found.

[FAIL]-No SMBIOS nor DMI entry point found.

[FAIL]-No SMBIOS nor DMI entry point found.

[FAIL]-No SMBIOS nor DMI entry point found.

=================================================
* Plugin name: microcode
* Result: FAIL

* Title: Processor microcode update
* Description: This test verifies if the firmware has put a recent version of the microcode into the processor at boot time. Recent microcode is important to have all the required features and errata updates for the processor.
================================================

[FAIL]-Cpu cpu1 has outdated microcode (version 9 while version b is available)

[FAIL]-Cpu cpu0 has outdated microcode (version 9 while version b is available)

=================================================
* Plugin name: acpicompile
* Result: WARN

* Title: DSDT AML verification
* Description: This test first disassembles the DSDT of the BIOS, and then uses the IASL compiler from Intel to recompile the code. The IASL copiler is much stricter in detecting deviations from the ACPI specification and can find numerous defects that other AML compilers cannot find. Fixing these defects increases the probability that the BIOS will operate well with a variety of operating systems.
================================================

[WARN]-Possible operator timeout is ignored

Possible operator timeout is ignored
At line #4417 of DSDT.dsl:

 |  Name (XSST, 0x1A)
 |  Name (XRCT, 0x1C)
 |  Mutex (MUTE, 0x00)
 |  Method (RBPE, 1, NotSerialized)
 |  {
>>>     Acquire (MUTE, 0x03E8)
 |      Add (Arg0, \PCIB, Local0)
 |      OperationRegion (PCFG, SystemMemory, Local0, 0x01)
 |      Field (PCFG, ByteAcc, NoLock, Preserve)
 |      {


[WARN]-Possible operator timeout is ignored

Possible operator timeout is ignored
At line #4431 of DSDT.dsl:

 |              Return (XCFG)
 |          }
 |  
 |          Method (RWPE, 1, NotSerialized)
 |          {
>>>             Acquire (MUTE, 0x03E8)
 |              And (Arg0, 0xFFFFFFFE, Arg0)
 |              Add (Arg0, \PCIB, Local0)
 |              OperationRegion (PCFG, SystemMemory, Local0, 0x02)
 |              Field (PCFG, WordAcc, NoLock, Preserve)


[WARN]-Possible operator timeout is ignored

Possible operator timeout is ignored
At line #4446 of DSDT.dsl:

 |              Return (XCFG)
 |          }
 |  
 |          Method (RDPE, 1, NotSerialized)
 |          {
>>>             Acquire (MUTE, 0x03E8)
 |              And (Arg0, 0xFFFFFFFC, Arg0)
 |              Add (Arg0, \PCIB, Local0)
 |              OperationRegion (PCFG, SystemMemory, Local0, 0x04)
 |              Field (PCFG, DWordAcc, NoLock, Preserve)


[WARN]-Possible operator timeout is ignored

Possible operator timeout is ignored
At line #4461 of DSDT.dsl:

 |              Return (XCFG)
 |          }
 |  
 |          Method (WBPE, 2, NotSerialized)
 |          {
>>>             Acquire (MUTE, 0x0FFF)
 |              Add (Arg0, \PCIB, Local0)
 |              OperationRegion (PCFG, SystemMemory, Local0, 0x01)
 |              Field (PCFG, ByteAcc, NoLock, Preserve)
 |              {


[WARN]-Possible operator timeout is ignored

Possible operator timeout is ignored
At line #4475 of DSDT.dsl:

 |              Release (MUTE)
 |          }
 |  
 |          Method (WWPE, 2, NotSerialized)
 |          {
>>>             Acquire (MUTE, 0x03E8)
 |              And (Arg0, 0xFFFFFFFE, Arg0)
 |              Add (Arg0, \PCIB, Local0)
 |              OperationRegion (PCFG, SystemMemory, Local0, 0x02)
 |              Field (PCFG, WordAcc, NoLock, Preserve)


[WARN]-Possible operator timeout is ignored

Possible operator timeout is ignored
At line #4490 of DSDT.dsl:

 |              Release (MUTE)
 |          }
 |  
 |          Method (WDPE, 2, NotSerialized)
 |          {
>>>             Acquire (MUTE, 0x03E8)
 |              And (Arg0, 0xFFFFFFFC, Arg0)
 |              Add (Arg0, \PCIB, Local0)
 |              OperationRegion (PCFG, SystemMemory, Local0, 0x04)
 |              Field (PCFG, DWordAcc, NoLock, Preserve)


[WARN]-Possible operator timeout is ignored

Possible operator timeout is ignored
At line #4505 of DSDT.dsl:

 |              Release (MUTE)
 |          }
 |  
 |          Method (RWDP, 3, NotSerialized)
 |          {
>>>             Acquire (MUTE, 0x03E8)
 |              And (Arg0, 0xFFFFFFFC, Arg0)
 |              Add (Arg0, \PCIB, Local0)
 |              OperationRegion (PCFG, SystemMemory, Local0, 0x04)
 |              Field (PCFG, DWordAcc, NoLock, Preserve)


[PASS]-Tested table DSDT.dsl

[INFO]-The IASL compiler from Intel would save 900 bytes of space.

The existing code takes 20960 bytes
The IASL compiler from Intel uses 20060 bytes
This is a saving of 900 bytes.


=================================================
* Plugin name: maxreadreq
* Result: WARN

* Title: PCI Express MaxReadReq tuning
* Description: This test checks if the firmware has set MaxReadReq to a higher value on non-montherboard devices
================================================

[WARN]-MaxReadReq for device pci://00:80:01.0 is low (128)

=================================================
* Plugin name: edd
* Result: WARN

* Title: EDD Boot disk hinting
* Description: This test verifies if the BIOS directs the operating system on which storage device to use for booting (EDD information). This is important for systems that (can) have multiple disks. Linux distributions increasingly depend on this info to find out on which device to install the bootloader.
================================================

[INFO]-device 80: The system boots from device 0000:00:00.0 channel: 0 serial_number: 0 


[WARN]-device 80: No matching MBR signature (0x000c3efb) found for the boot disk

Device sdb - signature 0xc3efb
Device hdb - signature 0xdcd6d18d


[INFO]-device 81 is provided by device 0000:00:0f.0 channel: 0 device: 0 


[WARN]-device 81: No matching MBR signature (0x9fe59fe5) found for this disk

Device sdb - signature 0xc3efb
Device hdb - signature 0xdcd6d18d


[INFO]-device 82 is provided by device 0000:00:0f.1 channel: 0 device: 1 


[INFO]-device 82: This disk has Linux device name /dev/hdb

=================================================
* Plugin name: thermal_trip
* Result: WARN

* Title: ACPI passive thermal trip points
* Description: This test determines if the passive trip point works as expected.
================================================

[WARN]-No thermal zones found.

=================================================
* Plugin name: fan
* Result: WARN

* Title: Fan tests
* Description: This test reports how many fans there are in the system. It also checks for the current status of the fan(s).
================================================

[WARN]-No fan information present

=================================================
* Plugin name: cpufreq
* Result: WARN

* Title: CPU frequency scaling tests (1-2 mins)
* Description: For each processor in the system, this test steps through the various frequency states (P-states) that the BIOS advertises for the processor. For each processor/frequency combination, a quick performance value is measured. The test then validates that: 
  1) Each processor has the same number of frequency states
  2) Higher advertised frequencies have a higher performance
  3) No duplicate frequency values are reported by the BIOS
  4) Is BIOS wrongly doing Sw_All P-state coordination across cores
  5) Is BIOS wrongly doing Sw_Any P-state coordination across cores

================================================

[WARN]-Frequency scaling not supported

=================================================
* Plugin name: battery
* Result: INFO

* Title: Battery tests
* Description: This test reports which (if any) batteries there are in the system. In addition, for charging or discharging batteries, the test validates that the reported 'current capacity' properly increments/decrements in line with the charge/discharge state. 

This test also stresses the entire battery state reporting codepath in the ACPI BIOS, and any warnings given by the ACPI interpreter will be reported.
================================================

[INFO]-No battery information present

=================================================
* Plugin name: acpiinfo
* Result: INFO

* Title: General ACPI information
* Description: This test checks the output of the in-kernel ACPI CA against common error messages that indicate a bad interaction with the bios, including those that point at AML syntax errors.
================================================

[INFO]-DSDT was compiled by the Intel AML compiler

ACPI: DSDT BFED0450, 51E0 (r1  A7255 A725500D        D INTL  2002026)

=================================================
* Plugin name: virt
* Result: INFO

* Title: VT/VMX Virtualization extensions
* Description: This test checks if VT/VMX is set up correctly
================================================

[INFO]-Processor does not support Virtualization extensions

=================================================
* Plugin name: DMAR
* Result: INFO

* Title: (experimental) DMA Remapping (VT-d) test
* Description: Verify if DMA remapping is sane.
================================================

[INFO]-No DMAR ACPI table found.

=================================================
* Plugin name: mtrr
* Result: PASS

* Title: MTRR validation
* Description: This test validates the MTRR setup against the memory map to detect any inconsistencies in cachability.
================================================

=================================================
* Plugin name: pciresource
* Result: PASS

* Title: Validate assigned PCI resources
* Description: This test is currently a placeholder and just checks the kernel log for complaints about PCI resource errors. In the future the idea is to actually perform a validation step on all PCI resources against a certain rule-set.
================================================

=================================================
* Plugin name: SUN
* Result: PASS

* Title: SUN duplicate test
* Description: This makes sure that each SUN (Slot Unique Number) that is called in the DSDT through the Name() method is unique, no duplicates should be found.
================================================

[PASS]-Tested _SUN ids, successfully found no duplicates

=================================================
* Plugin name: ebda
* Result: PASS

* Title: EBDA region
* Description: This test validates if the EBDA region is mapped and reserved in the E820 table.
================================================

[PASS]-EBDA region is correctly reserved in the E820 table.

=================================================
* Plugin name: os2gap
* Result: PASS

* Title: OS/2 memory hole test
* Description: This test checks if the OS/2 15Mb memory hole is absent
================================================

[PASS]-Successfully found no 15mb memory hole

=================================================
* Plugin name: ethernet
* Result: PASS

* Title: Ethernet functionality
* Description: This test is currently a placeholder for a more advanced ethernet test. Currently the only check performed is that a link is acquired within 45 seconds of enabling the interface. 45 seconds is close to the value most Linux distributions use as timeout value.

In the future the plan is to also perform actual data transfer tests as part of the ethernet test, to validate interrupt routing and other per-NIC behaviors.
================================================

=================================================
* Plugin name: apicedge
* Result: PASS

* Title: (experimental) APIC Edge/Level check
* Description: This test checks if legacy interrupts are edge and PCI interrupts are level
================================================

Répondre