Sure, here it is.
2011/9/7 joeyli <jlee@xxxxxxxx>:
> Hi AceLan,
>
> I am tracing a issue related to hotkey define.
> Could you please share dmidecode to me on your machine?
>
>
> Thank's a lot!
> Joey Lee
>
> 於 四，2011-08-11 於 15:45 +0800，AceLan Kao 提到：
>> Dear Joey,
>>
>> Good, that looks more reasonable to me.
>>
>> Yes, my machine has wifi module on it, but the wifi hotkey event is
>> handled by BIOS, so the wifi toggle works as expected.
>> I still got the failed message, but we can take it as a BIOS bug and
>> leave it there.
>>
>> BTW, your patches work well on my machine, thanks for your hard work.
>> You can have my signature on your patches.
>> Tested-by: AceLan Kao <acelan.kao@xxxxxxxxxxxxx>
>>
>> Best regards,
>> AceLan Kao.
>>
>> 2011/8/11 Joey Lee <jlee@xxxxxxxxxx>:
>> > 於 四，2011-08-11 於 03:30 +0000，joeyli(Joey Lee) 提到：
>> >> 於 四，2011-08-11 於 10:48 +0800，AceLan Kao 提到：
>> >> > Dear Joey,
>> >> >
>> >> > This is the dmesg log.
>> >> > [ 9010.944053] acer_wmi: Acer Laptop ACPI-WMI Extras
>> >> > [ 9010.944071] acer_wmi: Function bitmap for Communication Button: 0x1
>> >
>> > Per this log, the 0x1 means your machine have wifi hardware module and
>> > BIOS detected it then write information to SMBIOS area.
>> >
>> >> > [ 9010.944075] acer_wmi: Brightness must be controlled by generic video driver
>> >> > [ 9010.944996] input: Acer WMI hotkeys as /devices/virtual/input/input21
>> >> > [ 9010.947095] acer_wmi: Set Device Status failed: 0xe2 - 0x0
>> >> >
>> >
>> > But,
>> > here have problem when acer-wmi driver try to set the state by
>> > WMID_GUID3 method, the wmi function response 0xe2.
>> >
>> >> > And after adding my quirk, the set device status still failed, but
>> >> > except that, everything works well.
>> >> >
>> >>
>> >> So, you machine have wifi hardware module or not?
>> >>
>> >> > The "failed" comes from acer_rfkill_init(), it'll call
>> >> > acer_rfkill_register() with ACER_CAP_WIRELESS parameter without
>> >> > checking the capability.
>> >> > I don't know why only wifi doesn't check the capability and call
>> >> > acer_rfkill_register() directly, but it doesn't hurt the system.
>> >> >
>> >> > ===
>> >> > static int acer_rfkill_init(struct device *dev)
>> >> > {
>> >> > wireless_rfkill = acer_rfkill_register(dev, RFKILL_TYPE_WLAN,
>> >> > "acer-wireless", ACER_CAP_WIRELESS);
>> >> > if (IS_ERR(wireless_rfkill))
>> >> > return PTR_ERR(wireless_rfkill);
>> >> > ===
>> >> >
>> >> > Best regards,
>> >> > AceLan Kao.
>> >> >
>> >>
>> >> I checked the history, looks like it's just a original design in old
>> >> patch.
>> >>
>> >> Yes, you are right, add ACER_CAP_WIRELESS check is better. I am doing
>> >> generate a patch to add ACER_CAP_WIRELESS check.
>> >> Will attached patch on mail.
>> >>
>> >>
>> >> Thank's
>> >> Joey Lee
>> >>
>> >
>> > Please let me know does there have any wifi module in your machine when
>> > you test?
>> > If yes, then you need contact with BIOS team for why the WMID_GUID3
>> > method response 0xe2 when set device state, because this function works
>> > find on my TravelMate 8572 machine.
>> >
>> > On the other hand,
>> > The following is patch to check the ACER_CAP_WIRELESS before generate
>> > wireless rfkill.
>> >
>> >
>> > Thank's
>> > Joey Lee
>> >
>> > >From 18c20f2b40bc64ec72b52ae2e4d994237173f982 Mon Sep 17 00:00:00 2001
>> > From: Lee, Chun-Yi <jlee@xxxxxxxx>
>> > Date: Thu, 11 Aug 2011 12:49:53 +0800
>> > Subject: [PATCH] acer-wmi: check wireless capability flag before register rfkill
>> >
>> > There will be better to check the wireless capability flag
>> > (ACER_CAP_WIRELESS) before register wireless rfkill because maybe
>> > the machine doesn't have wifi module or the module removed by user.
>> >
>> > Signed-off-by: Lee, Chun-Yi <jlee@xxxxxxxx>
>> > ---
>> > drivers/platform/x86/acer-wmi.c | 64 +++++++++++++++++++++++++-------------
>> > 1 files changed, 42 insertions(+), 22 deletions(-)
>> >
>> > diff --git a/drivers/platform/x86/acer-wmi.c b/drivers/platform/x86/acer-wmi.c
>> > index 712a505..b4078c4 100644
>> > --- a/drivers/platform/x86/acer-wmi.c
>> > +++ b/drivers/platform/x86/acer-wmi.c
>> > @@ -1289,12 +1289,13 @@ static void acer_rfkill_update(struct work_struct *ignored)
>> > u32 state;
>> > acpi_status status;
>> >
>> > - status = get_u32(&state, ACER_CAP_WIRELESS);
>> > - if (ACPI_SUCCESS(status)) {
>> > - if (quirks->wireless == 3) {
>> > - rfkill_set_hw_state(wireless_rfkill, !state);
>> > - } else {
>> > - rfkill_set_sw_state(wireless_rfkill, !state);
>> > + if (has_cap(ACER_CAP_WIRELESS)) {
>> > + status = get_u32(&state, ACER_CAP_WIRELESS);
>> > + if (ACPI_SUCCESS(status)) {
>> > + if (quirks->wireless == 3)
>> > + rfkill_set_hw_state(wireless_rfkill, !state);
>> > + else
>> > + rfkill_set_sw_state(wireless_rfkill, !state);
>> > }
>> > }
>> >
>> > @@ -1362,19 +1363,24 @@ static struct rfkill *acer_rfkill_register(struct device *dev,
>> >
>> > static int acer_rfkill_init(struct device *dev)
>> > {
>> > - wireless_rfkill = acer_rfkill_register(dev, RFKILL_TYPE_WLAN,
>> > - "acer-wireless", ACER_CAP_WIRELESS);
>> > - if (IS_ERR(wireless_rfkill))
>> > - return PTR_ERR(wireless_rfkill);
>> > + int err;
>> > +
>> > + if (has_cap(ACER_CAP_WIRELESS)) {
>> > + wireless_rfkill = acer_rfkill_register(dev, RFKILL_TYPE_WLAN,
>> > + "acer-wireless", ACER_CAP_WIRELESS);
>> > + if (IS_ERR(wireless_rfkill)) {
>> > + err = PTR_ERR(wireless_rfkill);
>> > + goto error_wireless;
>> > + }
>> > + }
>> >
>> > if (has_cap(ACER_CAP_BLUETOOTH)) {
>> > bluetooth_rfkill = acer_rfkill_register(dev,
>> > RFKILL_TYPE_BLUETOOTH, "acer-bluetooth",
>> > ACER_CAP_BLUETOOTH);
>> > if (IS_ERR(bluetooth_rfkill)) {
>> > - rfkill_unregister(wireless_rfkill);
>> > - rfkill_destroy(wireless_rfkill);
>> > - return PTR_ERR(bluetooth_rfkill);
>> > + err = PTR_ERR(bluetooth_rfkill);
>> > + goto error_bluetooth;
>> > }
>> > }
>> >
>> > @@ -1383,30 +1389,44 @@ static int acer_rfkill_init(struct device *dev)
>> > RFKILL_TYPE_WWAN, "acer-threeg",
>> > ACER_CAP_THREEG);
>> > if (IS_ERR(threeg_rfkill)) {
>> > - rfkill_unregister(wireless_rfkill);
>> > - rfkill_destroy(wireless_rfkill);
>> > - rfkill_unregister(bluetooth_rfkill);
>> > - rfkill_destroy(bluetooth_rfkill);
>> > - return PTR_ERR(threeg_rfkill);
>> > + err = PTR_ERR(threeg_rfkill);
>> > + goto error_threeg;
>> > }
>> > }
>> >
>> > rfkill_inited = true;
>> >
>> > - if (ec_raw_mode || !wmi_has_guid(ACERWMID_EVENT_GUID))
>> > + if ((ec_raw_mode || !wmi_has_guid(ACERWMID_EVENT_GUID)) &&
>> > + has_cap(ACER_CAP_WIRELESS | ACER_CAP_BLUETOOTH | ACER_CAP_THREEG))
>> > schedule_delayed_work(&acer_rfkill_work,
>> > round_jiffies_relative(HZ));
>> >
>> > return 0;
>> > +
>> > +error_threeg:
>> > + if (has_cap(ACER_CAP_BLUETOOTH)) {
>> > + rfkill_unregister(bluetooth_rfkill);
>> > + rfkill_destroy(bluetooth_rfkill);
>> > + }
>> > +error_bluetooth:
>> > + if (has_cap(ACER_CAP_WIRELESS)) {
>> > + rfkill_unregister(wireless_rfkill);
>> > + rfkill_destroy(wireless_rfkill);
>> > + }
>> > +error_wireless:
>> > + return err;
>> > }
>> >
>> > static void acer_rfkill_exit(void)
>> > {
>> > - if (ec_raw_mode || !wmi_has_guid(ACERWMID_EVENT_GUID))
>> > + if ((ec_raw_mode || !wmi_has_guid(ACERWMID_EVENT_GUID)) &&
>> > + has_cap(ACER_CAP_WIRELESS | ACER_CAP_BLUETOOTH | ACER_CAP_THREEG))
>> > cancel_delayed_work_sync(&acer_rfkill_work);
>> >
>> > - rfkill_unregister(wireless_rfkill);
>> > - rfkill_destroy(wireless_rfkill);
>> > + if (has_cap(ACER_CAP_WIRELESS)) {
>> > + rfkill_unregister(wireless_rfkill);
>> > + rfkill_destroy(wireless_rfkill);
>> > + }
>> >
>> > if (has_cap(ACER_CAP_BLUETOOTH)) {
>> > rfkill_unregister(bluetooth_rfkill);
>> > --
>> > 1.6.0.2
>> >
>> >
>> >
>> >
>>
>>
>>
>> --
>> Chia-Lin Kao(AceLan)
>> http://blog.acelan.idv.tw/
>> E-Mail: acelan.kaoATcanonical.com (s/AT/@/)
>> --
>> To unsubscribe from this list: send the line "unsubscribe platform-driver-x86" in
>> the body of a message to majordomo@xxxxxxxxxxxxxxx
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
>
--
Chia-Lin Kao(AceLan)
http://blog.acelan.idv.tw/
E-Mail: acelan.kaoATcanonical.com (s/AT/@/)
# dmidecode 2.9
SMBIOS 2.6 present.
51 structures occupying 2384 bytes.
Table at 0x000E9AE0.
Handle 0x0000, DMI type 0, 24 bytes
BIOS Information
Vendor: INSYDE
Version: V1.05TD
Release Date: 07/25/2011
ROM Size: 2048 kB
Characteristics:
PCI is supported
BIOS is upgradeable
BIOS shadowing is allowed
Boot from CD is supported
Selectable boot is supported
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
BIOS boot specification is supported
Targeted content distribution is supported
BIOS Revision: 5.152
Handle 0x0001, DMI type 1, 27 bytes
System Information
Manufacturer: eMachines
Product Name: AS4739Z
Version: V1.05TD
Serial Number: S2RK302002110078222500
UUID: BBAFC2DE-DA16-4E63-A218-60EB69E6F69B
Wake-up Type: Power Switch
SKU Number: Calpella_CRB
Family: Intel_Mobile
Handle 0x0002, DMI type 2, 16 bytes
Base Board Information
Manufacturer: eMachines
Product Name: HMA_CP
Version: Base Board Version
Serial Number: 110FCECMBQT00007
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, 23 bytes
Chassis Information
Manufacturer: Chassis Manufacturer
Type: Notebook
Lock: Not Present
Version: Chassis Version
Serial Number: Chassis Serial Number
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
Handle 0x0004, DMI type 9, 17 bytes
System Slot Information
Designation: J5C1
Type: x16 <OUT OF SPEC>
Current Usage: Available
Length: Other
Characteristics:
PME signal is supported
Hot-plug devices are supported
Handle 0x0005, DMI type 9, 17 bytes
System Slot Information
Designation: J6C1
Type: x1 <OUT OF SPEC>
Current Usage: Available
Length: Other
Characteristics:
PME signal is supported
Hot-plug devices are supported
Handle 0x0006, DMI type 9, 17 bytes
System Slot Information
Designation: J6C2
Type: x1 <OUT OF SPEC>
Current Usage: Available
Length: Other
Characteristics:
PME signal is supported
Hot-plug devices are supported
Handle 0x0007, DMI type 9, 17 bytes
System Slot Information
Designation: J6D2
Type: x1 <OUT OF SPEC>
Current Usage: Available
Length: Other
Characteristics:
PME signal is supported
Hot-plug devices are supported
Handle 0x0008, DMI type 9, 17 bytes
System Slot Information
Designation: J7C1
Type: x1 <OUT OF SPEC>
Current Usage: Available
Length: Other
Characteristics:
PME signal is supported
Hot-plug devices are supported
Handle 0x0009, DMI type 9, 17 bytes
System Slot Information
Designation: J7D2
Type: x1 <OUT OF SPEC>
Current Usage: Available
Length: Other
Characteristics:
PME signal is supported
Hot-plug devices are supported
Handle 0x000A, DMI type 9, 17 bytes
System Slot Information
Designation: J8C2
Type: x16 <OUT OF SPEC>
Current Usage: Available
Length: Other
Characteristics:
PME signal is supported
Hot-plug devices are supported
Handle 0x000B, DMI type 9, 17 bytes
System Slot Information
Designation: J8C1
Type: x1 <OUT OF SPEC>
Current Usage: Available
Length: Other
Characteristics:
PME signal is supported
Hot-plug devices are supported
Handle 0x000C, 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 0x000D, DMI type 12, 5 bytes
System Configuration Options
Option 1:
Option 2: String2 for Type12 Equipment Manufacturer
Option 3: String3 for Type12 Equipment Manufacturer
Option 4: String4 for Type12 Equipment Manufacturer
Handle 0x000E, DMI type 21, 7 bytes
Built-in Pointing Device
Type: Touch Pad
Interface: PS/2
Buttons: 4
Handle 0x000F, DMI type 27, 15 bytes
Cooling Device
Type: Fan
Status: OK
OEM-specific Information: 0x00000000
Nominal Speed: 2000 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_Define3
Asset Tag: OEM_Define4
Model Part Number: OEM_Define5
Revision: OEM_Define6
Max Power Capacity: 0.075 W
Status: Present, OK
Type: Regulator
Input Voltage Range Switching: Auto-switch
Plugged: No
Hot Replaceable: No
Cooling Device Handle: 0x000F
Handle 0x0012, DMI type 40, 18 bytes
Unknown Type
Header and Data:
28 12 12 00 02 06 04 00 05 01 AA 07 00 00 05 02
DC 05
Strings:
PCIExpressx16
Compiler Version: VC 9.0
Handle 0x0013, DMI type 41, 11 bytes
Unknown Type
Header and Data:
29 0B 13 00 01 85 01 00 00 00 01
Strings:
Hanksville Gbe Lan Connection
Handle 0x0014, DMI type 22, 26 bytes
Portable Battery
Location: Fake
Manufacturer: -Virtual Battery 0-
Manufacture Date: 10/12/2007
Serial Number: Battery 0
Name: CRB Battery 0
Chemistry: Lithium Ion
Design Capacity: Unknown
Design Voltage: Unknown
SBDS Version: Not Specified
Maximum Error: Unknown
OEM-specific Information: 0x00000000
Handle 0x0015, DMI type 136, 6 bytes
OEM-specific Type
Header and Data:
88 06 15 00 5A 5A
Handle 0x0016, DMI type 129, 8 bytes
OEM-specific Type
Header and Data:
81 08 16 00 01 01 02 01
Strings:
Intel_ASF
Intel_ASF_001
Handle 0x0017, DMI type 130, 20 bytes
OEM-specific Type
Header and Data:
82 14 17 00 24 41 4D 54 01 01 01 01 01 A5 1F 02
00 00 00 00
Handle 0x0018, DMI type 16, 23 bytes
Physical Memory Array
Location: System Board Or Motherboard
Use: System Memory
Error Correction Type: None
Maximum Capacity: 16 GB
Error Information Handle: No Error
Number Of Devices: 2
Handle 0x0019, DMI type 17, 34 bytes
Memory Device
Array Handle: 0x0018
Error Information Handle: 0x001B
Total Width: 64 bits
Data Width: 64 bits
Size: 1024 MB
Form Factor: SODIMM
Set: None
Locator: DIMM0
Bank Locator: BANK 0
Type: <OUT OF SPEC>
Type Detail: Synchronous
Speed: 1067 MHz (0.9 ns)
Manufacturer: Not Specified
Serial Number: ED015413
Asset Tag: Unknown
Part Number: NT1GC64BH4B0PS-CG
Handle 0x001A, DMI type 6, 12 bytes
Memory Module Information
Socket Designation: DIMM0
Bank Connections: None
Current Speed: Unknown
Type: DIMM
Installed Size: 1024 MB (Single-bank Connection)
Enabled Size: 1024 MB (Single-bank Connection)
Error Status: OK
Handle 0x001B, 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 0x001C, DMI type 20, 35 bytes
Memory Device Mapped Address
Starting Address: 0x00000000000
Ending Address: 0x0003FFFFFFF
Range Size: 1 GB
Physical Device Handle: 0x0019
Memory Array Mapped Address Handle: 0x0028
Partition Row Position: Unknown
Interleave Position: 1
Interleaved Data Depth: 1
Handle 0x001D, DMI type 17, 34 bytes
Memory Device
Array Handle: 0x0018
Error Information Handle: Not Provided
Total Width: 8 bits
Data Width: 8 bits
Size: No Module Installed
Form Factor: DIMM
Set: None
Locator: DIMM1
Bank Locator: BANK 1
Type: <OUT OF SPEC>
Type Detail: Synchronous
Speed: 1067 MHz (0.9 ns)
Manufacturer: Not Specified
Serial Number: 00000000
Asset Tag: Unknown
Part Number: Not Specified
Handle 0x001E, DMI type 6, 12 bytes
Memory Module Information
Socket Designation: DIMM1
Bank Connections: None
Current Speed: Unknown
Type: DIMM
Installed Size: Not Installed
Enabled Size: Not Installed
Error Status: OK
Handle 0x001F, 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 0x0020, DMI type 17, 34 bytes
Memory Device
Array Handle: 0x0018
Error Information Handle: 0x0022
Total Width: 64 bits
Data Width: 64 bits
Size: 1024 MB
Form Factor: SODIMM
Set: None
Locator: DIMM1
Bank Locator: BANK 2
Type: <OUT OF SPEC>
Type Detail: Synchronous
Speed: 1067 MHz (0.9 ns)
Manufacturer: Not Specified
Serial Number: AB40D41A
Asset Tag: Unknown
Part Number: NT1GC64BH4B0PS-CG
Handle 0x0021, DMI type 6, 12 bytes
Memory Module Information
Socket Designation: DIMM1
Bank Connections: None
Current Speed: Unknown
Type: DIMM
Installed Size: 1024 MB (Single-bank Connection)
Enabled Size: 1024 MB (Single-bank Connection)
Error Status: OK
Handle 0x0022, 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 0x0023, DMI type 20, 35 bytes
Memory Device Mapped Address
Starting Address: 0x00000000000
Ending Address: 0x0003FFFFFFF
Range Size: 1 GB
Physical Device Handle: 0x0020
Memory Array Mapped Address Handle: 0x0028
Partition Row Position: Unknown
Interleave Position: 2
Interleaved Data Depth: 1
Handle 0x0024, DMI type 17, 34 bytes
Memory Device
Array Handle: 0x0018
Error Information Handle: Not Provided
Total Width: 8 bits
Data Width: 8 bits
Size: No Module Installed
Form Factor: DIMM
Set: None
Locator: DIMM3
Bank Locator: BANK 3
Type: <OUT OF SPEC>
Type Detail: Synchronous
Speed: 1067 MHz (0.9 ns)
Manufacturer: Not Specified
Serial Number: 00000000
Asset Tag: Unknown
Part Number: Not Specified
Handle 0x0025, DMI type 6, 12 bytes
Memory Module Information
Socket Designation: DIMM3
Bank Connections: None
Current Speed: Unknown
Type: DIMM
Installed Size: Not Installed
Enabled Size: Not Installed
Error Status: OK
Handle 0x0026, 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 0x0027, 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 0x0028, DMI type 19, 31 bytes
Memory Array Mapped Address
Starting Address: 0x00000000000
Ending Address: 0x0007FFFFFFF
Range Size: 2 GB
Physical Array Handle: 0x0018
Partition Width: 0
Handle 0x0029, DMI type 5, 20 bytes
Memory Controller Information
Error Detecting Method: None
Error Correcting Capabilities:
Unknown
None
Supported Interleave: One-way Interleave
Current Interleave: One-way Interleave
Maximum Memory Module Size: 8192 MB
Maximum Total Memory Size: 16384 MB
Supported Speeds:
Other
Supported Memory Types:
Other
Memory Module Voltage: Unknown
Associated Memory Slots: 2
0x001A
0x0021
Enabled Error Correcting Capabilities:
None
Handle 0x002A, DMI type 4, 42 bytes
Processor Information
Socket Designation: CPU
Type: Central Processor
Family: <OUT OF SPEC>
Manufacturer: Intel(R) Corporation
ID: 55 06 02 00 FF FB EB BF
Version: Intel(R) Pentium(R) CPU P6200 @ 2.13GHz
Voltage: 0.0 V
External Clock: 1066 MHz
Max Speed: 2133 MHz
Current Speed: 2131 MHz
Status: Populated, Enabled
Upgrade: ZIF Socket
L1 Cache Handle: 0x002E
L2 Cache Handle: 0x002D
L3 Cache Handle: 0x002B
Serial Number: Not Specified
Asset Tag: FFFF
Part Number: Not Specified
Core Count: 2
Core Enabled: 2
Thread Count: 2
Characteristics:
64-bit capable
Handle 0x002B, DMI type 7, 19 bytes
Cache Information
Socket Designation: L3 Cache
Configuration: Enabled, Not Socketed, Level 3
Operational Mode: Write Through
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: Other
Handle 0x002C, DMI type 7, 19 bytes
Cache Information
Socket Designation: L1 Cache
Configuration: Enabled, Not Socketed, Level 1
Operational Mode: Write Through
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 0x002D, DMI type 7, 19 bytes
Cache Information
Socket Designation: L2 Cache
Configuration: Enabled, Not Socketed, Level 2
Operational Mode: Write Through
Location: Internal
Installed Size: 256 KB
Maximum Size: 256 KB
Supported SRAM Types:
Synchronous
Installed SRAM Type: Synchronous
Speed: Unknown
Error Correction Type: Single-bit ECC
System Type: Unified
Associativity: 8-way Set-associative
Handle 0x002E, DMI type 7, 19 bytes
Cache Information
Socket Designation: L1 Cache
Configuration: Enabled, Not Socketed, Level 1
Operational Mode: Write Through
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: 4-way Set-associative
Handle 0x002F, DMI type 170, 106 bytes
OEM-specific Type
Header and Data:
AA 6A 2F 00 01 00 00 00 7F 00 0F 00 06 00 01 02
01 00 41 02 04 00 42 02 08 00 43 02 10 00 44 02
20 00 45 02 40 00 46 02 01 00 47 02 02 00 61 02
08 00 62 02 04 00 63 02 01 00 64 02 02 00 81 02
04 00 82 02 02 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 0x0030, DMI type 171, 24 bytes
OEM-specific Type
Header and Data:
AB 18 30 00 02 69 19 62 20 04 02 04 75 76 05 86
80 56 3B 07 8C 16 32 00
Handle 0x0031, DMI type 172, 6 bytes
OEM-specific Type
Header and Data:
AC 06 31 00 02 04
Handle 0x0032, DMI type 127, 4 bytes
End Of Table
