Lenovo 3000 N100 i8042 problems

Lenovo 3000 N100 i8042 problems

[Daniel Barkalow]

In 2.6.25.10, I'm finding that my i8042 seems to die after a while. In the 
middle of using the keyboard and mouse, generally before some key release 
is handled, it stops taking any input.

This seems to be due to 2a2dcd65e232eafd9fb6da1250f83adb57787b42; it works 
fine with that reverted. Perhaps that quirk is being applied too widely? 
Perhaps the workaround doesn't actually work on my computer? I couldn't 
find the bug report that led to that patch, so I'm not sure if I've been 
having whatever problem it was for all along and I never noticed, or if my 
3000 N100 is just different (Lenovo seems to have given a 
specific-sounding number to some very different hardware).

	-Daniel
*This .sig left intentionally blank*

Re: Lenovo 3000 N100 i8042 problems

[Jiri Kosina]

On Mon, 1 Sep 2008, Daniel Barkalow wrote:

> In 2.6.25.10, I'm finding that my i8042 seems to die after a while. In the 
> middle of using the keyboard and mouse, generally before some key release 
> is handled, it stops taking any input.
> This seems to be due to 2a2dcd65e232eafd9fb6da1250f83adb57787b42; it works 
> fine with that reverted. Perhaps that quirk is being applied too widely? 

Hi Daniel,

thanks for tracking down the commit. Also, please don't forget to CC the 
commit author in such cases :)

Could you please send a dmidecode output from your system, so that we can 
compare it to the one provided by Christopher, as he as the system that 
apparently needs the nomux quirk to work correctly? It's indeed possible 
that there are various systems out there, and the DMI match has to be made 
more strict.

Thanks,

-- 
Jiri Kosina
SUSE Labs

Re: Lenovo 3000 N100 i8042 problems

[Daniel Barkalow]

[-- Attachment #1: Type: TEXT/PLAIN, Size: 1043 bytes --]

On Tue, 2 Sep 2008, Jiri Kosina wrote:

> On Mon, 1 Sep 2008, Daniel Barkalow wrote:
> 
> > In 2.6.25.10, I'm finding that my i8042 seems to die after a while. In the 
> > middle of using the keyboard and mouse, generally before some key release 
> > is handled, it stops taking any input.
> > This seems to be due to 2a2dcd65e232eafd9fb6da1250f83adb57787b42; it works 
> > fine with that reverted. Perhaps that quirk is being applied too widely? 
> 
> Hi Daniel,
> 
> thanks for tracking down the commit. Also, please don't forget to CC the 
> commit author in such cases :)

Oh, right, the Author field. I confused myself by finding you as the 
middle sign-off.

> Could you please send a dmidecode output from your system, so that we can 
> compare it to the one provided by Christopher, as he as the system that 
> apparently needs the nomux quirk to work correctly? It's indeed possible 
> that there are various systems out there, and the DMI match has to be made 
> more strict.

Attached.

	-Daniel
*This .sig left intentionally blank*

[-- Attachment #2: Type: TEXT/PLAIN, Size: 9745 bytes --]

# dmidecode 2.9
SMBIOS 2.4 present.
39 structures occupying 1326 bytes.
Table at 0x000DC010.

Handle 0x0000, DMI type 0, 24 bytes
BIOS Information
	Vendor: LENOVO
	Version: 61ET20WW
	Release Date: 07/05/06
	Address: 0xE6F90
	Runtime Size: 102512 bytes
	ROM Size: 1024 kB
	Characteristics:
		ISA is supported
		PCI is supported
		PC Card (PCMCIA) is supported
		PNP is supported
		APM is supported
		BIOS is upgradeable
		BIOS shadowing is allowed
		ESCD support is available
		Boot from CD is supported
		ACPI is supported
		USB legacy is supported
		AGP is supported
		BIOS boot specification is supported

Handle 0x0001, DMI type 1, 27 bytes
System Information
	Manufacturer: LENOVO
	Product Name: 076836U
	Version: 3000 N100                       
	Serial Number: L3H0536                                                  
	UUID: 6747DA31-D471-11DA-901B-000FB0C9A0C9
	Wake-up Type: Power Switch
	SKU Number: Not Specified
	Family: Not Specified

Handle 0x0002, DMI type 2, 8 bytes
Base Board Information
	Manufacturer: LENOVO
	Product Name: MPAD-MSAE Customer Reference Boards
	Version: Not Applicable
	Serial Number: 41W1220Z1ZBUA6551DK                                             

Handle 0x0003, DMI type 3, 17 bytes
Chassis Information
	Manufacturer: No Enclosure
	Type: Notebook
	Lock: Not Present
	Version: N/A
	Serial Number: None
	Asset Tag:                     
	Boot-up State: Safe
	Power Supply State: Safe
	Thermal State: Safe
	Security Status: None
	OEM Information: 0x00001234

Handle 0x0004, DMI type 4, 35 bytes
Processor Information
	Socket Designation: U2E1
	Type: Central Processor
	Family: Other
	Manufacturer: Intel
	ID: E8 06 00 00 FF FB E9 BF
	Version: Genuine Intel(R) CPU           T2
	Voltage: 3.3 V
	External Clock: Unknown
	Max Speed: 2048 MHz
	Current Speed: 1660 MHz
	Status: Populated, Enabled
	Upgrade: ZIF Socket
	L1 Cache Handle: 0x0005
	L2 Cache Handle: 0x0006
	L3 Cache Handle: Not Provided
	Serial Number: Not Specified
	Asset Tag: Not Specified
	Part Number: Not Specified

Handle 0x0005, DMI type 7, 19 bytes
Cache Information
	Socket Designation: L1 Cache
	Configuration: Enabled, Socketed, Level 1
	Operational Mode: Write Back
	Location: Internal
	Installed Size: 16 KB
	Maximum Size: 16 KB
	Supported SRAM Types:
		Burst
		Pipeline Burst
		Asynchronous
	Installed SRAM Type: Asynchronous
	Speed: Unknown
	Error Correction Type: Unknown
	System Type: Unknown
	Associativity: Unknown

Handle 0x0006, DMI type 7, 19 bytes
Cache Information
	Socket Designation: L2 Cache
	Configuration: Enabled, Socketed, Level 2
	Operational Mode: Write Back
	Location: External
	Installed Size: 2048 KB
	Maximum Size: 512 KB
	Supported SRAM Types:
		Burst
		Pipeline Burst
		Asynchronous
	Installed SRAM Type: Burst
	Speed: Unknown
	Error Correction Type: Unknown
	System Type: Unknown
	Associativity: Unknown

Handle 0x0007, DMI type 8, 9 bytes
Port Connector Information
	Internal Reference Designator: J19
	Internal Connector Type: 9 Pin Dual Inline (pin 10 cut)
	External Reference Designator: COM 1
	External Connector Type: DB-9 male
	Port Type: Serial Port 16550A Compatible

Handle 0x0008, DMI type 8, 9 bytes
Port Connector Information
	Internal Reference Designator: J23
	Internal Connector Type: 25 Pin Dual Inline (pin 26 cut)
	External Reference Designator: Parallel
	External Connector Type: DB-25 female
	Port Type: Parallel Port ECP/EPP

Handle 0x0009, DMI type 8, 9 bytes
Port Connector Information
	Internal Reference Designator: J11
	Internal Connector Type: None
	External Reference Designator: Keyboard
	External Connector Type: Circular DIN-8 male
	Port Type: Keyboard Port

Handle 0x000A, DMI type 8, 9 bytes
Port Connector Information
	Internal Reference Designator: J12
	Internal Connector Type: None
	External Reference Designator: PS/2 Mouse
	External Connector Type: Circular DIN-8 male
	Port Type: Keyboard Port

Handle 0x000B, DMI type 9, 13 bytes
System Slot Information
	Designation: PCI Slot J11
	Type: 32-bit PCI
	Current Usage: Unknown
	Length: Long
	ID: 0
	Characteristics:
		5.0 V is provided
		3.3 V is provided

Handle 0x000C, DMI type 9, 13 bytes
System Slot Information
	Designation: PCI Slot J12
	Type: 32-bit PCI
	Current Usage: Unknown
	Length: Long
	ID: 0
	Characteristics:
		5.0 V is provided
		3.3 V is provided

Handle 0x000D, DMI type 9, 13 bytes
System Slot Information
	Designation: PCI Slot J13
	Type: 32-bit PCI
	Current Usage: Unknown
	Length: Long
	ID: 0
	Characteristics:
		5.0 V is provided
		3.3 V is provided

Handle 0x000E, DMI type 10, 6 bytes
On Board Device Information
	Type: Sound
	Status: Disabled
	Description: HD-Audio

Handle 0x000F, DMI type 11, 5 bytes
OEM Strings
	String 1: This is the Intel Calistoga
	String 2: Chipset CRB Platform

Handle 0x0010, DMI type 12, 5 bytes
System Configuration Options
	Option 1: Jumper settings can be described here.

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

Handle 0x0012, DMI type 17, 27 bytes
Memory Device
	Array Handle: 0x0011
	Error Information Handle: No Error
	Total Width: 32 bits
	Data Width: 32 bits
	Size: 1024 MB
	Form Factor: SODIMM
	Set: 1
	Locator: M1
	Bank Locator: Bank 0
	Type: DDR
	Type Detail: Synchronous
	Speed: Unknown
	Manufacturer: Not Specified
	Serial Number: Not Specified
	Asset Tag: Not Specified
	Part Number: Not Specified

Handle 0x0013, DMI type 17, 27 bytes
Memory Device
	Array Handle: 0x0011
	Error Information Handle: No Error
	Total Width: 32 bits
	Data Width: 32 bits
	Size: 1024 MB
	Form Factor: SODIMM
	Set: 1
	Locator: M2
	Bank Locator: Bank 1
	Type: DDR
	Type Detail: Synchronous
	Speed: Unknown
	Manufacturer: Not Specified
	Serial Number: Not Specified
	Asset Tag: Not Specified
	Part Number: Not Specified

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

Handle 0x0015, DMI type 20, 19 bytes
Memory Device Mapped Address
	Starting Address: 0x00000000000
	Ending Address: 0x0003FFFFFFF
	Range Size: 1 GB
	Physical Device Handle: 0x0012
	Memory Array Mapped Address Handle: 0x0014
	Partition Row Position: Unknown
	Interleave Position: Unknown
	Interleaved Data Depth: Unknown

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

Handle 0x0017, DMI type 23, 13 bytes
System Reset
	Status: Enabled
	Watchdog Timer: Present
	Boot Option: Do Not Reboot
	Boot Option On Limit: Do Not Reboot
	Reset Count: Unknown
	Reset Limit: Unknown
	Timer Interval: Unknown
	Timeout: Unknown

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

Handle 0x0019, DMI type 25, 9 bytes
	System Power Controls
	Next Scheduled Power-on: 12-31 23:59:59

Handle 0x001A, DMI type 26, 20 bytes
Voltage Probe
	Description: Voltage Probe
	Location: Processor
	Status: OK
	Maximum Value: Unknown
	Minimum Value: Unknown
	Resolution: Unknown
	Tolerance: Unknown
	Accuracy: Unknown
	OEM-specific Information: 0x00000000

Handle 0x001B, DMI type 27, 12 bytes
Cooling Device
	Temperature Probe Handle: 0x001C
	Type: Fan
	Status: OK
	OEM-specific Information: 0x00000000

Handle 0x001C, DMI type 28, 20 bytes
Temperature Probe
	Description: Temperature Probe
	Location: Processor
	Status: OK
	Maximum Value: Unknown
	Minimum Value Unknown
	Resolution: Unknown
	Tolerance: Unknown
	Accuracy: Unknown
	OEM-specific Information: 0x00000000

Handle 0x001D, DMI type 29, 20 bytes
Electrical Current Probe
	Description: Electrical Current Probe
	Location: Processor
	Status: OK
	Maximum Value: Unknown
	Minimum Value: Unknown
	Resolution: Unknown
	Tolerance: Unknown
	Accuracy: Unknown
	OEM-specific Information: 0x00000000

Handle 0x001E, DMI type 30, 6 bytes
Out-of-band Remote Access
	Manufacturer Name: Intel
	Inbound Connection: Enabled
	Outbound Connection: Disabled

Handle 0x001F, DMI type 32, 20 bytes
System Boot Information
	Status: <OUT OF SPEC>

Handle 0x0020, DMI type 129, 16 bytes
OEM-specific Type
	Header and Data:
		81 10 20 00 01 01 02 01 00 00 00 01 06 01 00 01
	Strings:
		Intel_ASF_001
		Intel_ASF_001

Handle 0x0021, DMI type 136, 5 bytes
OEM-specific Type
	Header and Data:
		88 05 21 00 5A
	Strings:
		Z

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

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

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

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

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

Re: Lenovo 3000 N100 i8042 problems

[Jiri Kosina]

On Mon, 1 Sep 2008, Daniel Barkalow wrote:

> > Could you please send a dmidecode output from your system, so that we can 
> > compare it to the one provided by Christopher, as he as the system that 
> > apparently needs the nomux quirk to work correctly? It's indeed possible 
> > that there are various systems out there, and the DMI match has to be made 
> > more strict.
> Attached.

Hmm, so you have

Handle 0x0001, DMI type 1, 27 bytes
System Information
        Manufacturer: LENOVO
        Product Name: 076836U
        Version: 3000 N100
        Serial Number: L3H0536
        UUID: 6747DA31-D471-11DA-901B-000FB0C9A0C9
        Wake-up Type: Power Switch
        SKU Number: Not Specified
        Family: Not Specified

Handle 0x0002, DMI type 2, 8 bytes
Base Board Information
        Manufacturer: LENOVO
        Product Name: MPAD-MSAE Customer Reference Boards
        Version: Not Applicable
        Serial Number: 41W1220Z1ZBUA6551DK

and the system on which Christopher reported originally this bug to me was

Handle 0x0001, DMI type 1, 27 bytes
System Information
        Manufacturer: LENOVO
        Product Name: 076804U
        Version: 3000 N100
        Serial Number: L3HX754
        UUID: DA02FA2F-A0AC-11DB-A093-000FB0D2560C
        Wake-up Type: Power Switch
        SKU Number: Intel
        Family: Lenovo

Handle 0x0002, DMI type 2, 8 bytes
Base Board Information
        Manufacturer: LENOVO
        Product Name: CAPELL VALLEY(NAPA) CRB
        Version: Not Applicable
        Serial Number: 41W8025Z1ZCZ971N36R                                      


so the product name both of System and Base Board are different, and 
apparently the systems differ. Dmitry, what fields would you propose to be 
put in the DMI matching here? I will do the patch then.

Thanks,

-- 
Jiri Kosina
SUSE Labs

Re: Lenovo 3000 N100 i8042 problems

[Henrique de Moraes Holschuh]

On Tue, 02 Sep 2008, Jiri Kosina wrote:
> so the product name both of System and Base Board are different, and 
> apparently the systems differ. Dmitry, what fields would you propose to be 
> put in the DMI matching here? I will do the patch then.

Are you sure you shouldn't be looking at BIOS version, instead? I don't know
how the Lenovo N100 series is, but chances are their i8042 is emulated
inside the ACPI EC, i.e. a firmware upgrade can change the i8042 behaviour.

I'd check BIOS versions, and ask people to upgrade to the latest, to see if
the problem goes away (or changes).  Then you will know for sure the best
approach.

-- 
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh

Re: Lenovo 3000 N100 i8042 problems

[Dmitry Torokhov]

On Tue, Sep 02, 2008 at 09:43:13AM -0300, Henrique de Moraes Holschuh wrote:
> On Tue, 02 Sep 2008, Jiri Kosina wrote:
> > so the product name both of System and Base Board are different, and 
> > apparently the systems differ. Dmitry, what fields would you propose to be 
> > put in the DMI matching here? I will do the patch then.
> 
> Are you sure you shouldn't be looking at BIOS version, instead?

Unfortunately we can't do "less than" type of comparison on DMI data,
otherwise it would be great solution.

> I don't know
> how the Lenovo N100 series is, but chances are their i8042 is emulated
> inside the ACPI EC, i.e. a firmware upgrade can change the i8042 behaviour.
>

I think this is true for all boxes manufactured in the last 8 years.

> I'd check BIOS versions, and ask people to upgrade to the latest, to see if
> the problem goes away (or changes).  Then you will know for sure the best
> approach.
>

Keeping compatibility with the other OS is the safest way so unless
Vista started using active MUX there is probably update to the BIOS
fixing legacy mux mode.

-- 
Dmitry

Re: Lenovo 3000 N100 i8042 problems

[Dmitry Torokhov]

On Tue, Sep 02, 2008 at 11:23:25AM +0200, Jiri Kosina wrote:
> 
> so the product name both of System and Base Board are different, and 
> apparently the systems differ. Dmitry, what fields would you propose to be 
> put in the DMI matching here? I will do the patch then.
> 

I guess we could use System's product name to differentiate between
Cristopher's and Daniel's boards. Although I must admit it is the very
first time when I see a box that behaves better with active mux. DOes
Vista use active mux nowadays? Because if it is not then I bet there
is (or shortly will be) a BIOS update fixing legacy mode on Daniel's
box.

-- 
Dmitry

Re: Lenovo 3000 N100 i8042 problems

[Daniel Barkalow]

On Tue, 2 Sep 2008, Dmitry Torokhov wrote:

> On Tue, Sep 02, 2008 at 11:23:25AM +0200, Jiri Kosina wrote:
> > 
> > so the product name both of System and Base Board are different, and 
> > apparently the systems differ. Dmitry, what fields would you propose to be 
> > put in the DMI matching here? I will do the patch then.
> > 
> 
> I guess we could use System's product name to differentiate between
> Cristopher's and Daniel's boards. Although I must admit it is the very
> first time when I see a box that behaves better with active mux. DOes
> Vista use active mux nowadays? Because if it is not then I bet there
> is (or shortly will be) a BIOS update fixing legacy mode on Daniel's
> box.

Mine's actually old (came with XP). It's still got the original BIOS 
(because I haven't found a way to upgrade the BIOS without reformatting my 
hard drive to include Windows), and I remember there being an upgrade 
available, but I don't think it had anything to do with keyboard/trackpad 
stuff.

In what way does active mux usually behave badly? It's possible that 
legacy mode only has a bug that doesn't matter to Windows, and active mux 
may have some of the usual problems but nothing I particularly noticed.

I noticed that, when my i8042 would stop working, it would generally have 
just delivered one mouse interrupt to CPU1 after never previously doing 
so. Perhaps there's some sort of deadlock in the Linux i8042 driver when 
both cores are unexpectedly getting interrupts from the two devices at 
once? I could understand there being a Linux bug only triggered by quirky 
hardware that only applies to legacy mode, which was just uncovered by 
this patch.

	-Daniel
*This .sig left intentionally blank*

Re: Lenovo 3000 N100 i8042 problems

[Dmitry Torokhov]

On Tue, Sep 02, 2008 at 12:16:15PM -0400, Daniel Barkalow wrote:
> On Tue, 2 Sep 2008, Dmitry Torokhov wrote:
> 
> > On Tue, Sep 02, 2008 at 11:23:25AM +0200, Jiri Kosina wrote:
> > > 
> > > so the product name both of System and Base Board are different, and 
> > > apparently the systems differ. Dmitry, what fields would you propose to be 
> > > put in the DMI matching here? I will do the patch then.
> > > 
> > 
> > I guess we could use System's product name to differentiate between
> > Cristopher's and Daniel's boards. Although I must admit it is the very
> > first time when I see a box that behaves better with active mux. DOes
> > Vista use active mux nowadays? Because if it is not then I bet there
> > is (or shortly will be) a BIOS update fixing legacy mode on Daniel's
> > box.
> 
> Mine's actually old (came with XP). It's still got the original BIOS 
> (because I haven't found a way to upgrade the BIOS without reformatting my 
> hard drive to include Windows), and I remember there being an upgrade 
> available, but I don't think it had anything to do with keyboard/trackpad 
> stuff.
> 
> In what way does active mux usually behave badly? It's possible that 

It usually manifests with a touchpad/mouse missing because they don't
responf to kernel's queries. Quite a few Fujitsus exibit this
behavior.

> legacy mode only has a bug that doesn't matter to Windows, and active mux 
> may have some of the usual problems but nothing I particularly noticed.
> 
> I noticed that, when my i8042 would stop working, it would generally have 
> just delivered one mouse interrupt to CPU1 after never previously doing 
> so. Perhaps there's some sort of deadlock in the Linux i8042 driver when 
> both cores are unexpectedly getting interrupts from the two devices at 
> once? I could understand there being a Linux bug only triggered by quirky 
> hardware that only applies to legacy mode, which was just uncovered by 
> this patch.
>

I am not sure, internally we the kernel still deals with 2 interrupt
sources (KBD and AUX) regardless whether it is in legacy or active
multiplexing mode...

Does it take long to trigger the bug? You coudl try doing "echo 1 >
/sys/modules/i8042/parameters/debug" and thend me dmesg or
/var/log/messages after the bug was triggered - I might see something
there. But please be aware that if you send me such a log I can decode
everything that you have been typing...

-- 
Dmitry

Re: Lenovo 3000 N100 i8042 problems

[Daniel Barkalow]

On Wed, 3 Sep 2008, Dmitry Torokhov wrote:

> On Tue, Sep 02, 2008 at 12:16:15PM -0400, Daniel Barkalow wrote:
> > On Tue, 2 Sep 2008, Dmitry Torokhov wrote:
> > 
> > > On Tue, Sep 02, 2008 at 11:23:25AM +0200, Jiri Kosina wrote:
> > > > 
> > > > so the product name both of System and Base Board are different, and 
> > > > apparently the systems differ. Dmitry, what fields would you propose to be 
> > > > put in the DMI matching here? I will do the patch then.
> > > > 
> > > 
> > > I guess we could use System's product name to differentiate between
> > > Cristopher's and Daniel's boards. Although I must admit it is the very
> > > first time when I see a box that behaves better with active mux. DOes
> > > Vista use active mux nowadays? Because if it is not then I bet there
> > > is (or shortly will be) a BIOS update fixing legacy mode on Daniel's
> > > box.
> > 
> > Mine's actually old (came with XP). It's still got the original BIOS 
> > (because I haven't found a way to upgrade the BIOS without reformatting my 
> > hard drive to include Windows), and I remember there being an upgrade 
> > available, but I don't think it had anything to do with keyboard/trackpad 
> > stuff.
> > 
> > In what way does active mux usually behave badly? It's possible that 
> 
> It usually manifests with a touchpad/mouse missing because they don't
> responf to kernel's queries. Quite a few Fujitsus exibit this
> behavior.

Right from the beginning? I'm not seeing that on any kernel with this 
hardware. I don't suppose the kernel could detect that it's using active 
mux and one of the devices isn't responding, and use legacy mode in that 
case, and only use quirks for systems where the active mux does something 
particularly weird?

> > legacy mode only has a bug that doesn't matter to Windows, and active mux 
> > may have some of the usual problems but nothing I particularly noticed.
> > 
> > I noticed that, when my i8042 would stop working, it would generally have 
> > just delivered one mouse interrupt to CPU1 after never previously doing 
> > so. Perhaps there's some sort of deadlock in the Linux i8042 driver when 
> > both cores are unexpectedly getting interrupts from the two devices at 
> > once? I could understand there being a Linux bug only triggered by quirky 
> > hardware that only applies to legacy mode, which was just uncovered by 
> > this patch.
> >
> 
> I am not sure, internally we the kernel still deals with 2 interrupt
> sources (KBD and AUX) regardless whether it is in legacy or active
> multiplexing mode...
> 
> Does it take long to trigger the bug? You coudl try doing "echo 1 >
> /sys/modules/i8042/parameters/debug" and thend me dmesg or
> /var/log/messages after the bug was triggered - I might see something
> there. But please be aware that if you send me such a log I can decode
> everything that you have been typing...

It's usually within an hour of the right usage pattern. I'll try to 
trigger it with debugging on while not typing anything secret Thursday 
evening.

The other thing that might be useful, if there's some way to find out, is 
whether the kernel lost an interrupt somehow, since this feels like the 
hardware is waiting patiently for a lost interrupt to get serviced. Also, 
is there some way to get the kernel to re-initialize the i8042? It might 
be useful to see if the firmware has really stopped working or if the 
kernel is just failing to do anything further with it. I can unbind the 
driver, but I don't seem to be able to bind it again.

	-Daniel
*This .sig left intentionally blank*

Re: Lenovo 3000 N100 i8042 problems

[Dmitry Torokhov]

On Wed, Sep 03, 2008 at 01:16:59PM -0400, Daniel Barkalow wrote:
> On Wed, 3 Sep 2008, Dmitry Torokhov wrote:
> 
> > On Tue, Sep 02, 2008 at 12:16:15PM -0400, Daniel Barkalow wrote:
> > > On Tue, 2 Sep 2008, Dmitry Torokhov wrote:
> > > 
> > > > On Tue, Sep 02, 2008 at 11:23:25AM +0200, Jiri Kosina wrote:
> > > > > 
> > > > > so the product name both of System and Base Board are different, and 
> > > > > apparently the systems differ. Dmitry, what fields would you propose to be 
> > > > > put in the DMI matching here? I will do the patch then.
> > > > > 
> > > > 
> > > > I guess we could use System's product name to differentiate between
> > > > Cristopher's and Daniel's boards. Although I must admit it is the very
> > > > first time when I see a box that behaves better with active mux. DOes
> > > > Vista use active mux nowadays? Because if it is not then I bet there
> > > > is (or shortly will be) a BIOS update fixing legacy mode on Daniel's
> > > > box.
> > > 
> > > Mine's actually old (came with XP). It's still got the original BIOS 
> > > (because I haven't found a way to upgrade the BIOS without reformatting my 
> > > hard drive to include Windows), and I remember there being an upgrade 
> > > available, but I don't think it had anything to do with keyboard/trackpad 
> > > stuff.
> > > 
> > > In what way does active mux usually behave badly? It's possible that 
> > 
> > It usually manifests with a touchpad/mouse missing because they don't
> > responf to kernel's queries. Quite a few Fujitsus exibit this
> > behavior.
> 
> Right from the beginning? 

Yes.

> I'm not seeing that on any kernel with this 
> hardware.

I understand. Jiri, how did active MUX problem manifest on
Cristopher's box?

> I don't suppose the kernel could detect that it's using active 
> mux and one of the devices isn't responding, and use legacy mode in that 
> case, and only use quirks for systems where the active mux does something 
> particularly weird?

Well, we need a device to respond to our queries to figure out if it
is present or not ;) The box may not have any devices attached but
still have perfectly working active MUX implementation.

> 
> > > legacy mode only has a bug that doesn't matter to Windows, and active mux 
> > > may have some of the usual problems but nothing I particularly noticed.
> > > 
> > > I noticed that, when my i8042 would stop working, it would generally have 
> > > just delivered one mouse interrupt to CPU1 after never previously doing 
> > > so. Perhaps there's some sort of deadlock in the Linux i8042 driver when 
> > > both cores are unexpectedly getting interrupts from the two devices at 
> > > once? I could understand there being a Linux bug only triggered by quirky 
> > > hardware that only applies to legacy mode, which was just uncovered by 
> > > this patch.
> > >
> > 
> > I am not sure, internally we the kernel still deals with 2 interrupt
> > sources (KBD and AUX) regardless whether it is in legacy or active
> > multiplexing mode...
> > 
> > Does it take long to trigger the bug? You coudl try doing "echo 1 >
> > /sys/modules/i8042/parameters/debug" and thend me dmesg or
> > /var/log/messages after the bug was triggered - I might see something
> > there. But please be aware that if you send me such a log I can decode
> > everything that you have been typing...
> 
> It's usually within an hour of the right usage pattern. I'll try to 
> trigger it with debugging on while not typing anything secret Thursday 
> evening.
> 

Coo, thanks.

> The other thing that might be useful, if there's some way to find out, is 
> whether the kernel lost an interrupt somehow, since this feels like the 
> hardware is waiting patiently for a lost interrupt to get serviced. Also, 
> is there some way to get the kernel to re-initialize the i8042? It might 
> be useful to see if the firmware has really stopped working or if the 
> kernel is just failing to do anything further with it. I can unbind the 
> driver, but I don't seem to be able to bind it again.

This is as close as it gets. Biding should cause the controller to be
flushed of any pending data and start afresh.

-- 
Dmitry

Re: Lenovo 3000 N100 i8042 problems

[Jiri Kosina]

On Wed, 3 Sep 2008, Dmitry Torokhov wrote:

> > I'm not seeing that on any kernel with this hardware.
> I understand. Jiri, how did active MUX problem manifest on
> Cristopher's box?

If Christopher doesn't respond himself, I will dig it out from my 
archives, it has been quite some time already since this has been 
originally reported.

If I remember correctly, when 'nomux' wasn't used, psmouse used to 
complain a lot about losing synchronization and then the mouse pointer 
either went crazy or froze completely.

Christoph?

Thanks,

-- 
Jiri Kosina
SUSE Labs

Re: Lenovo 3000 N100 i8042 problems

[Daniel Barkalow]

On Wed, 3 Sep 2008, Daniel Barkalow wrote:

> On Wed, 3 Sep 2008, Dmitry Torokhov wrote:
> 
> > On Tue, Sep 02, 2008 at 12:16:15PM -0400, Daniel Barkalow wrote:
> > > legacy mode only has a bug that doesn't matter to Windows, and active mux 
> > > may have some of the usual problems but nothing I particularly noticed.
> > > 
> > > I noticed that, when my i8042 would stop working, it would generally have 
> > > just delivered one mouse interrupt to CPU1 after never previously doing 
> > > so. Perhaps there's some sort of deadlock in the Linux i8042 driver when 
> > > both cores are unexpectedly getting interrupts from the two devices at 
> > > once? I could understand there being a Linux bug only triggered by quirky 
> > > hardware that only applies to legacy mode, which was just uncovered by 
> > > this patch.
> > >
> > 
> > I am not sure, internally we the kernel still deals with 2 interrupt
> > sources (KBD and AUX) regardless whether it is in legacy or active
> > multiplexing mode...
> > 
> > Does it take long to trigger the bug? You coudl try doing "echo 1 >
> > /sys/modules/i8042/parameters/debug" and thend me dmesg or
> > /var/log/messages after the bug was triggered - I might see something
> > there. But please be aware that if you send me such a log I can decode
> > everything that you have been typing...
> 
> It's usually within an hour of the right usage pattern. I'll try to 
> trigger it with debugging on while not typing anything secret Thursday 
> evening.

Attached. This has me typing some unimportant stuff, and then it sticks, 
then I plug in a USB keyboard, then I tried unbinding the i8042 and 
binding it again; the audio stuttered briefly, and recovered, and I did it 
again, and then saved this log.

	-Daniel
*This .sig left intentionally blank*

Re: Lenovo 3000 N100 i8042 problems

[Dmitry Torokhov]

On Thursday 04 September 2008, Daniel Barkalow wrote:
> On Wed, 3 Sep 2008, Daniel Barkalow wrote:
> 
> > On Wed, 3 Sep 2008, Dmitry Torokhov wrote:
> > 
> > > On Tue, Sep 02, 2008 at 12:16:15PM -0400, Daniel Barkalow wrote:
> > > > legacy mode only has a bug that doesn't matter to Windows, and active mux 
> > > > may have some of the usual problems but nothing I particularly noticed.
> > > > 
> > > > I noticed that, when my i8042 would stop working, it would generally have 
> > > > just delivered one mouse interrupt to CPU1 after never previously doing 
> > > > so. Perhaps there's some sort of deadlock in the Linux i8042 driver when 
> > > > both cores are unexpectedly getting interrupts from the two devices at 
> > > > once? I could understand there being a Linux bug only triggered by quirky 
> > > > hardware that only applies to legacy mode, which was just uncovered by 
> > > > this patch.
> > > >
> > > 
> > > I am not sure, internally we the kernel still deals with 2 interrupt
> > > sources (KBD and AUX) regardless whether it is in legacy or active
> > > multiplexing mode...
> > > 
> > > Does it take long to trigger the bug? You coudl try doing "echo 1 >
> > > /sys/modules/i8042/parameters/debug" and thend me dmesg or
> > > /var/log/messages after the bug was triggered - I might see something
> > > there. But please be aware that if you send me such a log I can decode
> > > everything that you have been typing...
> > 
> > It's usually within an hour of the right usage pattern. I'll try to 
> > trigger it with debugging on while not typing anything secret Thursday 
> > evening.
> 
> Attached. 

That is untruth :))

-- 
Dmitry

Re: Lenovo 3000 N100 i8042 problems

[Daniel Barkalow]

[-- Attachment #1: Type: TEXT/PLAIN, Size: 1930 bytes --]

On Thu, 4 Sep 2008, Dmitry Torokhov wrote:

> On Thursday 04 September 2008, Daniel Barkalow wrote:
> > On Wed, 3 Sep 2008, Daniel Barkalow wrote:
> > 
> > > On Wed, 3 Sep 2008, Dmitry Torokhov wrote:
> > > 
> > > > On Tue, Sep 02, 2008 at 12:16:15PM -0400, Daniel Barkalow wrote:
> > > > > legacy mode only has a bug that doesn't matter to Windows, and active mux 
> > > > > may have some of the usual problems but nothing I particularly noticed.
> > > > > 
> > > > > I noticed that, when my i8042 would stop working, it would generally have 
> > > > > just delivered one mouse interrupt to CPU1 after never previously doing 
> > > > > so. Perhaps there's some sort of deadlock in the Linux i8042 driver when 
> > > > > both cores are unexpectedly getting interrupts from the two devices at 
> > > > > once? I could understand there being a Linux bug only triggered by quirky 
> > > > > hardware that only applies to legacy mode, which was just uncovered by 
> > > > > this patch.
> > > > >
> > > > 
> > > > I am not sure, internally we the kernel still deals with 2 interrupt
> > > > sources (KBD and AUX) regardless whether it is in legacy or active
> > > > multiplexing mode...
> > > > 
> > > > Does it take long to trigger the bug? You coudl try doing "echo 1 >
> > > > /sys/modules/i8042/parameters/debug" and thend me dmesg or
> > > > /var/log/messages after the bug was triggered - I might see something
> > > > there. But please be aware that if you send me such a log I can decode
> > > > everything that you have been typing...
> > > 
> > > It's usually within an hour of the right usage pattern. I'll try to 
> > > trigger it with debugging on while not typing anything secret Thursday 
> > > evening.
> > 
> > Attached. 
> 
> That is untruth :))

Can I blame my keyboard? No, probably not, I sent that with the keyboard 
working. In any case, now it's attached for real.

	-Daniel
*This .sig left intentionally blank*

[-- Attachment #2: Type: TEXT/PLAIN, Size: 32123 bytes --]

.25-gentoo-r7/drivers/input/serio/i8042.c: b1 <- i8042 (interrupt, 1, 12) [234972]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 50 <- i8042 (interrupt, 1, 12) [234972]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: d0 <- i8042 (interrupt, 1, 12) [234972]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 55 <- i8042 (interrupt, 1, 12) [234973]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: f9 <- i8042 (interrupt, 1, 12) [234973]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 90 <- i8042 (interrupt, 1, 12) [234973]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: b1 <- i8042 (interrupt, 1, 12) [234973]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 50 <- i8042 (interrupt, 1, 12) [234974]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: d0 <- i8042 (interrupt, 1, 12) [234974]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 5c <- i8042 (interrupt, 1, 12) [234974]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: e7 <- i8042 (interrupt, 1, 12) [234974]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 90 <- i8042 (interrupt, 1, 12) [234974]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: b1 <- i8042 (interrupt, 1, 12) [234974]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 50 <- i8042 (interrupt, 1, 12) [234974]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: d0 <- i8042 (interrupt, 1, 12) [234975]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 62 <- i8042 (interrupt, 1, 12) [234975]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: d6 <- i8042 (interrupt, 1, 12) [234975]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 90 <- i8042 (interrupt, 1, 12) [234976]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: b1 <- i8042 (interrupt, 1, 12) [234976]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 50 <- i8042 (interrupt, 1, 12) [234976]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: d0 <- i8042 (interrupt, 1, 12) [234976]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 66 <- i8042 (interrupt, 1, 12) [234976]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: c6 <- i8042 (interrupt, 1, 12) [234976]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 90 <- i8042 (interrupt, 1, 12) [234977]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: b1 <- i8042 (interrupt, 1, 12) [234977]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 50 <- i8042 (interrupt, 1, 12) [234977]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: d0 <- i8042 (interrupt, 1, 12) [234977]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 6c <- i8042 (interrupt, 1, 12) [234978]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: b7 <- i8042 (interrupt, 1, 12) [234978]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 90 <- i8042 (interrupt, 1, 12) [234978]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: b1 <- i8042 (interrupt, 1, 12) [234978]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 50 <- i8042 (interrupt, 1, 12) [234978]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: d0 <- i8042 (interrupt, 1, 12) [234978]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 72 <- i8042 (interrupt, 1, 12) [234978]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: aa <- i8042 (interrupt, 1, 12) [234979]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 90 <- i8042 (interrupt, 1, 12) [234979]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: b1 <- i8042 (interrupt, 1, 12) [234979]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 50 <- i8042 (interrupt, 1, 12) [234980]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: d0 <- i8042 (interrupt, 1, 12) [234980]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 76 <- i8042 (interrupt, 1, 12) [234980]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: a6 <- i8042 (interrupt, 1, 12) [234980]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 90 <- i8042 (interrupt, 1, 12) [234981]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: b1 <- i8042 (interrupt, 1, 12) [234981]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 50 <- i8042 (interrupt, 1, 12) [234981]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: d0 <- i8042 (interrupt, 1, 12) [234981]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 7a <- i8042 (interrupt, 1, 12) [234981]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: ae <- i8042 (interrupt, 1, 12) [234981]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 90 <- i8042 (interrupt, 1, 12) [234982]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: b1 <- i8042 (interrupt, 1, 12) [234982]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 32 <- i8042 (interrupt, 1, 12) [234982]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: d0 <- i8042 (interrupt, 1, 12) [234982]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 89 <- i8042 (interrupt, 1, 12) [234982]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: ad <- i8042 (interrupt, 1, 12) [234983]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 80 <- i8042 (interrupt, 1, 12) [234983]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: b1 <- i8042 (interrupt, 1, 12) [234983]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 03 <- i8042 (interrupt, 1, 12) [234983]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: d0 <- i8042 (interrupt, 1, 12) [234983]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 89 <- i8042 (interrupt, 1, 12) [234984]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: ad <- i8042 (interrupt, 1, 12) [234984]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 80 <- i8042 (interrupt, 1, 12) [234984]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 1, 12) [234984]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 1, 12) [234984]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: c0 <- i8042 (interrupt, 1, 12) [234985]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 1, 12) [234985]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 1, 12) [234985]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 80 <- i8042 (interrupt, 1, 12) [234985]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 1, 12) [234985]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 1, 12) [234986]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: c0 <- i8042 (interrupt, 1, 12) [234986]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 1, 12) [234986]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 1, 12) [234986]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 80 <- i8042 (interrupt, 1, 12) [234986]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 1, 12) [234987]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 1, 12) [234987]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: c0 <- i8042 (interrupt, 1, 12) [234987]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 1, 12) [234987]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 1, 12) [234987]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 80 <- i8042 (interrupt, 1, 12) [234988]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 1, 12) [234988]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 1, 12) [234988]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: c0 <- i8042 (interrupt, 1, 12) [234988]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 1, 12) [234988]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 1, 12) [234988]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 80 <- i8042 (interrupt, 1, 12) [234989]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 1, 12) [234989]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 1, 12) [234989]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: c0 <- i8042 (interrupt, 1, 12) [234989]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 1, 12) [234989]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 1, 12) [234989]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 80 <- i8042 (interrupt, 1, 12) [234990]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 1, 12) [234990]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 1, 12) [234990]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: c0 <- i8042 (interrupt, 1, 12) [234990]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 1, 12) [234991]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 1, 12) [234991]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 80 <- i8042 (interrupt, 1, 12) [234991]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 1, 12) [234991]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 1, 12) [234992]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: c0 <- i8042 (interrupt, 1, 12) [234992]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 1, 12) [234992]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 1, 12) [234992]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 80 <- i8042 (interrupt, 1, 12) [234993]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 1, 12) [234993]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 1, 12) [234993]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: c0 <- i8042 (interrupt, 1, 12) [234993]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 1, 12) [234993]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 1, 12) [234993]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 80 <- i8042 (interrupt, 1, 12) [234994]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 1, 12) [234994]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 1, 12) [234994]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: c0 <- i8042 (interrupt, 1, 12) [234994]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 1, 12) [234994]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 1, 12) [234995]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 80 <- i8042 (interrupt, 1, 12) [234995]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 1, 12) [234995]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 1, 12) [234995]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: c0 <- i8042 (interrupt, 1, 12) [234995]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 1, 12) [234996]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 1, 12) [234996]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 80 <- i8042 (interrupt, 1, 12) [234996]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 1, 12) [234996]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 1, 12) [234996]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: c0 <- i8042 (interrupt, 1, 12) [234997]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 1, 12) [234997]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 1, 12) [234997]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 80 <- i8042 (interrupt, 1, 12) [234997]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 1, 12) [234997]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 1, 12) [234998]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: c0 <- i8042 (interrupt, 1, 12) [234998]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 1, 12) [234998]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 1, 12) [234998]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 80 <- i8042 (interrupt, 1, 12) [234999]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 1, 12) [234999]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 1, 12) [234999]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: c0 <- i8042 (interrupt, 1, 12) [234999]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 1, 12) [234999]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 1, 12) [234999]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 80 <- i8042 (interrupt, 1, 12) [235000]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 1, 12) [235000]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 1, 12) [235000]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: c0 <- i8042 (interrupt, 1, 12) [235000]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 1, 12) [235001]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 1, 12) [235001]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 82 <- i8042 (interrupt, 1, 12) [235001]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 1, 12) [235001]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 1, 12) [235001]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: c2 <- i8042 (interrupt, 1, 12) [235001]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 1, 12) [235002]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 1, 12) [235002]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 82 <- i8042 (interrupt, 1, 12) [235002]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 1, 12) [235002]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 1, 12) [235003]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: c2 <- i8042 (interrupt, 1, 12) [235003]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 1, 12) [235003]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 1, 12) [235003]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 82 <- i8042 (interrupt, 1, 12) [235003]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 1, 12) [235004]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 1, 12) [235004]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: c2 <- i8042 (interrupt, 1, 12) [235004]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 1, 12) [235004]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 1, 12) [235004]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 82 <- i8042 (interrupt, 1, 12) [235005]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 1, 12) [235005]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 1, 12) [235005]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: c2 <- i8042 (interrupt, 1, 12) [235005]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 1, 12) [235005]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 1, 12) [235006]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 82 <- i8042 (interrupt, 1, 12) [235006]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 1, 12) [235006]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 1, 12) [235006]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: c2 <- i8042 (interrupt, 1, 12) [235006]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 1, 12) [235006]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 1, 12) [235007]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 82 <- i8042 (interrupt, 1, 12) [235007]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 1, 12) [235007]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 1, 12) [235007]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: c2 <- i8042 (interrupt, 1, 12) [235008]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 1, 12) [235008]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 1, 12) [235008]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 82 <- i8042 (interrupt, 1, 12) [235008]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 1, 12) [235008]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 1, 12) [235009]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: c2 <- i8042 (interrupt, 1, 12) [235009]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 1, 12) [235009]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 1, 12) [235009]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 82 <- i8042 (interrupt, 1, 12) [235010]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 1, 12) [235010]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 1, 12) [235010]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: c2 <- i8042 (interrupt, 1, 12) [235010]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 1, 12) [235010]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 1, 12) [235010]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 82 <- i8042 (interrupt, 1, 12) [235010]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 1, 12) [235011]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 1, 12) [235011]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: c2 <- i8042 (interrupt, 1, 12) [235011]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 1, 12) [235011]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 1, 12) [235012]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 82 <- i8042 (interrupt, 1, 12) [235012]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 1, 12) [235012]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 1, 12) [235012]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: c2 <- i8042 (interrupt, 1, 12) [235012]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 1, 12) [235012]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 1, 12) [235013]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 82 <- i8042 (interrupt, 1, 12) [235013]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 1, 12) [235013]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 1, 12) [235013]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: c2 <- i8042 (interrupt, 1, 12) [235014]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 1, 12) [235014]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 1, 12) [235014]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 82 <- i8042 (interrupt, 1, 12) [235014]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 1, 12) [235015]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 1, 12) [235015]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: c2 <- i8042 (interrupt, 1, 12) [235015]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 1, 12) [235015]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 1, 12) [235015]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 82 <- i8042 (interrupt, 1, 12) [235016]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 1, 12) [235016]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 1, 12) [235016]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: c2 <- i8042 (interrupt, 1, 12) [235016]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 1, 12) [235016]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 1, 12) [235016]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 80 <- i8042 (interrupt, 1, 12) [235017]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 1, 12) [235017]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 1, 12) [235017]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: c0 <- i8042 (interrupt, 1, 12) [235017]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 1, 12) [235017]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 1, 12) [235018]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 80 <- i8042 (interrupt, 1, 12) [235018]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 1, 12) [235018]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 1, 12) [235018]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: c0 <- i8042 (interrupt, 1, 12) [235018]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 1, 12) [235019]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 1, 12) [235019]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 03 <- i8042 (interrupt, 0, 1) [235019]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 80 <- i8042 (interrupt, 1, 12) [235019]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 1, 12) [235020]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 1, 12) [235020]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: c0 <- i8042 (interrupt, 1, 12) [235020]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 1, 12) [235020]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 1, 12) [235020]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 80 <- i8042 (interrupt, 1, 12) [235020]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 1, 12) [235021]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 1, 12) [235021]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: c0 <- i8042 (interrupt, 1, 12) [235021]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 1, 12) [235021]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 1, 12) [235021]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 80 <- i8042 (interrupt, 1, 12) [235022]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 1, 12) [235022]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 1, 12) [235022]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: c0 <- i8042 (interrupt, 1, 12) [235022]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 1, 12) [235023]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 1, 12) [235023]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 80 <- i8042 (interrupt, 1, 12) [235023]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 1, 12) [235023]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 1, 12) [235023]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: c0 <- i8042 (interrupt, 1, 12) [235023]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 1, 12) [235024]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 1, 12) [235024]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 80 <- i8042 (interrupt, 1, 12) [235024]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 1, 12) [235024]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 1, 12) [235024]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: c0 <- i8042 (interrupt, 1, 12) [235025]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 1, 12) [235025]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 1, 12) [235025]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 80 <- i8042 (interrupt, 1, 12) [235025]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 1, 12) [235026]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 1, 12) [235026]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: c0 <- i8042 (interrupt, 1, 12) [235026]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 1, 12) [235026]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 1, 12) [235026]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 80 <- i8042 (interrupt, 1, 12) [235027]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 1, 12) [235027]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 1, 12) [235027]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: c0 <- i8042 (interrupt, 1, 12) [235027]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 1, 12) [235027]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 1, 12) [235027]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 80 <- i8042 (interrupt, 1, 12) [235028]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 1, 12) [235028]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 1, 12) [235028]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: c0 <- i8042 (interrupt, 1, 12) [235028]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 1, 12) [235028]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 1, 12) [235028]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 80 <- i8042 (interrupt, 1, 12) [235029]
hub 1-0:1.0: unable to enumerate USB device on port 7
usb 5-1: new low speed USB device using uhci_hcd and address 2
usb 5-1: configuration #1 chosen from 1 choice
input: USBPS2 as /class/input/input5
input: USB HID v1.00 Keyboard [USBPS2] on usb-0000:00:1d.3-1
input: USBPS2 as /class/input/input6
input: USB HID v1.00 Mouse [USBPS2] on usb-0000:00:1d.3-1
usbcore: registered new interface driver usbhid
/usr/src/linux-2.6.25-gentoo-r7/drivers/hid/usbhid/hid-core.c: v2.6:USB HID core driver
wireless: switched to short barker preamble (BSSID=00:11:24:02:69:f1)
wireless: switched to long barker preamble (BSSID=00:11:24:02:69:f1)
wireless: switched to short barker preamble (BSSID=00:11:24:02:69:f1)
wireless: switched to long barker preamble (BSSID=00:11:24:02:69:f1)
wireless: switched to short barker preamble (BSSID=00:11:24:02:69:f1)
wireless: switched to long barker preamble (BSSID=00:11:24:02:69:f1)
wireless: switched to short barker preamble (BSSID=00:11:24:02:69:f1)
wireless: switched to long barker preamble (BSSID=00:11:24:02:69:f1)
wireless: switched to short barker preamble (BSSID=00:11:24:02:69:f1)
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: d4 -> i8042 (command) [297819]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: e6 -> i8042 (parameter) [297819]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: fe <- i8042 (interrupt, 1, 12) [297819]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 1e <- i8042 (interrupt, 1, 12) [297819]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 83 <- i8042 (interrupt, 0, 1) [297819]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 60 -> i8042 (command) [297820]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 47 -> i8042 (parameter) [297820]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 20 -> i8042 (command) [299574]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 47 <- i8042 (return) [299574]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 60 -> i8042 (command) [299574]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 56 -> i8042 (parameter) [299574]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: d3 -> i8042 (command) [299574]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 5a -> i8042 (parameter) [299574]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 80 <- i8042 (return) [299575]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: a9 -> i8042 (command) [299575]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 5a <- i8042 (return) [299575]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 60 -> i8042 (command) [299575]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 47 -> i8042 (parameter) [299575]
serio: i8042 KBD port at 0x60,0x64 irq 1
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: f2 -> i8042 (kbd-data) [299575]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 0, 1) [299575]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: 83 <- i8042 (interrupt, 0, 1) [299575]
/usr/src/linux-2.6.25-gentoo-r7/drivers/input/serio/i8042.c: ed -> i8042 (kbd-data) [299628]

Re: Lenovo 3000 N100 i8042 problems

[Jiri Kosina]

On Tue, 2 Sep 2008, Dmitry Torokhov wrote:

> I guess we could use System's product name to differentiate between 
> Cristopher's and Daniel's boards. Although I must admit it is the very 
> first time when I see a box that behaves better with active mux. DOes 
> Vista use active mux nowadays? Because if it is not then I bet there is 
> (or shortly will be) a BIOS update fixing legacy mode on Daniel's box.

I guess so, yes.

On the other hand, this might also be viewed as regression (we made 
Daniel's hardware behave worse with recent kernel than it did before), so 
I think we still would like to have this fixed. What about the patch 
below, adding the match on System's product name, as you suggested? 
Thanks.


From: Jiri Kosina <jkosina@suse.cz>
Subject: [PATCH] Input: i8042 - make Lenovo 3000 N100 blacklist entry more specific

Apparently, there are more different versions of Lenovo 3000 N100, some
of them working properly with active mux, and some of them requiring it
being switched off.

This patch applies 'nomux' only to the specific product name that is
reported to behave badly unless 'nomux' is specified.

Signed-off-by: Jiri Kosina <jkosina@suse.cz>
---
 drivers/input/serio/i8042-x86ia64io.h |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/drivers/input/serio/i8042-x86ia64io.h b/drivers/input/serio/i8042-x86ia64io.h
index 3282b74..5aafe24 100644
--- a/drivers/input/serio/i8042-x86ia64io.h
+++ b/drivers/input/serio/i8042-x86ia64io.h
@@ -305,7 +305,7 @@ static struct dmi_system_id __initdata i8042_dmi_nomux_table[] = {
 		.ident = "Lenovo 3000 n100",
 		.matches = {
 			DMI_MATCH(DMI_SYS_VENDOR, "LENOVO"),
-			DMI_MATCH(DMI_PRODUCT_VERSION, "3000 N100"),
+			DMI_MATCH(DMI_PRODUCT_NAME, "076804U"),
 		},
 	},
 	{
-- 
1.5.4.5

Re: Lenovo 3000 N100 i8042 problems

[Dmitry Torokhov]

On Wed, Sep 03, 2008 at 01:50:35PM +0200, Jiri Kosina wrote:
> On Tue, 2 Sep 2008, Dmitry Torokhov wrote:
> 
> > I guess we could use System's product name to differentiate between 
> > Cristopher's and Daniel's boards. Although I must admit it is the very 
> > first time when I see a box that behaves better with active mux. DOes 
> > Vista use active mux nowadays? Because if it is not then I bet there is 
> > (or shortly will be) a BIOS update fixing legacy mode on Daniel's box.
> 
> I guess so, yes.
> 
> On the other hand, this might also be viewed as regression (we made 
> Daniel's hardware behave worse with recent kernel than it did before), so 
> I think we still would like to have this fixed. What about the patch 
> below, adding the match on System's product name, as you suggested? 
> Thanks.
> 

I agree. Daniel, could you please try the patch to make sure it
restores the previous behavior for you and I will push it through.

Thanks!

-- 
Dmitry

Re: Lenovo 3000 N100 i8042 problems

[Daniel Barkalow]

On Wed, 3 Sep 2008, Dmitry Torokhov wrote:

> On Wed, Sep 03, 2008 at 01:50:35PM +0200, Jiri Kosina wrote:
> > On Tue, 2 Sep 2008, Dmitry Torokhov wrote:
> > 
> > > I guess we could use System's product name to differentiate between 
> > > Cristopher's and Daniel's boards. Although I must admit it is the very 
> > > first time when I see a box that behaves better with active mux. DOes 
> > > Vista use active mux nowadays? Because if it is not then I bet there is 
> > > (or shortly will be) a BIOS update fixing legacy mode on Daniel's box.
> > 
> > I guess so, yes.
> > 
> > On the other hand, this might also be viewed as regression (we made 
> > Daniel's hardware behave worse with recent kernel than it did before), so 
> > I think we still would like to have this fixed. What about the patch 
> > below, adding the match on System's product name, as you suggested? 
> > Thanks.
> > 
> 
> I agree. Daniel, could you please try the patch to make sure it
> restores the previous behavior for you and I will push it through.
> 
> Thanks!

I'll test that Thursday as well; is there some quick way to determine 
whether you're using active mux or not?

	-Daniel
*This .sig left intentionally blank*

Re: Lenovo 3000 N100 i8042 problems

[Dmitry Torokhov]

On Wed, Sep 03, 2008 at 01:18:23PM -0400, Daniel Barkalow wrote:
> On Wed, 3 Sep 2008, Dmitry Torokhov wrote:
> 
> > On Wed, Sep 03, 2008 at 01:50:35PM +0200, Jiri Kosina wrote:
> > > On Tue, 2 Sep 2008, Dmitry Torokhov wrote:
> > > 
> > > > I guess we could use System's product name to differentiate between 
> > > > Cristopher's and Daniel's boards. Although I must admit it is the very 
> > > > first time when I see a box that behaves better with active mux. DOes 
> > > > Vista use active mux nowadays? Because if it is not then I bet there is 
> > > > (or shortly will be) a BIOS update fixing legacy mode on Daniel's box.
> > > 
> > > I guess so, yes.
> > > 
> > > On the other hand, this might also be viewed as regression (we made 
> > > Daniel's hardware behave worse with recent kernel than it did before), so 
> > > I think we still would like to have this fixed. What about the patch 
> > > below, adding the match on System's product name, as you suggested? 
> > > Thanks.
> > > 
> > 
> > I agree. Daniel, could you please try the patch to make sure it
> > restores the previous behavior for you and I will push it through.
> > 
> > Thanks!
> 
> I'll test that Thursday as well; is there some quick way to determine 
> whether you're using active mux or not?

Do "dmesg | grep serio".. If you see 4 AUX ports being created then
KBC is in active multiplexing mode.

-- 
Dmitry

Re: Lenovo 3000 N100 i8042 problems

[Daniel Barkalow]

On Wed, 3 Sep 2008, Daniel Barkalow wrote:

> On Wed, 3 Sep 2008, Dmitry Torokhov wrote:
> 
> > On Wed, Sep 03, 2008 at 01:50:35PM +0200, Jiri Kosina wrote:
> > > On Tue, 2 Sep 2008, Dmitry Torokhov wrote:
> > > 
> > > > I guess we could use System's product name to differentiate between 
> > > > Cristopher's and Daniel's boards. Although I must admit it is the very 
> > > > first time when I see a box that behaves better with active mux. DOes 
> > > > Vista use active mux nowadays? Because if it is not then I bet there is 
> > > > (or shortly will be) a BIOS update fixing legacy mode on Daniel's box.
> > > 
> > > I guess so, yes.
> > > 
> > > On the other hand, this might also be viewed as regression (we made 
> > > Daniel's hardware behave worse with recent kernel than it did before), so 
> > > I think we still would like to have this fixed. What about the patch 
> > > below, adding the match on System's product name, as you suggested? 
> > > Thanks.
> > > 
> > 
> > I agree. Daniel, could you please try the patch to make sure it
> > restores the previous behavior for you and I will push it through.
> > 
> > Thanks!
> 
> I'll test that Thursday as well; is there some quick way to determine 
> whether you're using active mux or not?

That patch, on top of 2.6.25.10 does give me 4 AUX ports, so I think it is 
getting the previous behavior as expected.

	-Daniel
*This .sig left intentionally blank*

Re: Lenovo 3000 N100 i8042 problems

[Henrique de Moraes Holschuh]

On Wed, 03 Sep 2008, Dmitry Torokhov wrote:
> On Wed, Sep 03, 2008 at 01:50:35PM +0200, Jiri Kosina wrote:
> > On Tue, 2 Sep 2008, Dmitry Torokhov wrote:
> > > I guess we could use System's product name to differentiate between 
> > > Cristopher's and Daniel's boards. Although I must admit it is the very 
> > > first time when I see a box that behaves better with active mux. DOes 
> > > Vista use active mux nowadays? Because if it is not then I bet there is 
> > > (or shortly will be) a BIOS update fixing legacy mode on Daniel's box.
> > 
> > I guess so, yes.
> > 
> > On the other hand, this might also be viewed as regression (we made 
> > Daniel's hardware behave worse with recent kernel than it did before), so 
> > I think we still would like to have this fixed. What about the patch 
> > below, adding the match on System's product name, as you suggested? 
> > Thanks.
> > 
> 
> I agree. Daniel, could you please try the patch to make sure it
> restores the previous behavior for you and I will push it through.

I fell I need to warn you guys that you are likely breaking machines that
match that DMI info but have a newer BIOS, unless they use different BIOSes
(not enough data without a full dmidecode output from the other machine).

But I really don't care either way, since this is not about ThinkPads :)

-- 
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh

Re: Lenovo 3000 N100 i8042 problems

[Jiri Kosina]

On Wed, 3 Sep 2008, Henrique de Moraes Holschuh wrote:

> I fell I need to warn you guys that you are likely breaking machines 
> that match that DMI info but have a newer BIOS, unless they use 
> different BIOSes (not enough data without a full dmidecode output from 
> the other machine).

I would dare to say "breaking". Just using 'nomux' shouldn't really 
_break_ anything, unless the BIOS is somehow seriously hosed.

-- 
Jiri Kosina
SUSE Labs

Re: Lenovo 3000 N100 i8042 problems

[Daniel Barkalow]

On Wed, 3 Sep 2008, Henrique de Moraes Holschuh wrote:

> On Wed, 03 Sep 2008, Dmitry Torokhov wrote:
> > On Wed, Sep 03, 2008 at 01:50:35PM +0200, Jiri Kosina wrote:
> > > On Tue, 2 Sep 2008, Dmitry Torokhov wrote:
> > > > I guess we could use System's product name to differentiate between 
> > > > Cristopher's and Daniel's boards. Although I must admit it is the very 
> > > > first time when I see a box that behaves better with active mux. DOes 
> > > > Vista use active mux nowadays? Because if it is not then I bet there is 
> > > > (or shortly will be) a BIOS update fixing legacy mode on Daniel's box.
> > > 
> > > I guess so, yes.
> > > 
> > > On the other hand, this might also be viewed as regression (we made 
> > > Daniel's hardware behave worse with recent kernel than it did before), so 
> > > I think we still would like to have this fixed. What about the patch 
> > > below, adding the match on System's product name, as you suggested? 
> > > Thanks.
> > > 
> > 
> > I agree. Daniel, could you please try the patch to make sure it
> > restores the previous behavior for you and I will push it through.
> 
> I fell I need to warn you guys that you are likely breaking machines that
> match that DMI info but have a newer BIOS, unless they use different BIOSes
> (not enough data without a full dmidecode output from the other machine).

The patch under consideration is to restore pre-2.6.25 behavior (i.e., 
active mux) for machines other than the one in a particular bug report, 
while 2.6.25 broke my machine. So this will probably rebreak machines that 
were broken until 2.6.25 (and can't break anything else). I think it would 
actually be better if we could apply the quirk to all models of 3000 N100 
except for mine (but I don't think quirk-matching supports that); my 
model is the only one we know of which came with a BIOS that has issues 
with legacy mode. I still think it's weird that Lenovo managed to break 
active mux when they'd had it working before, but who knows what's going 
on in their firmware development process.

In any case, I suspect that the legacy behavior on my machine is strange 
but manageable (given that Windows doesn't seem to have had problems using 
legacy mode even on my hardware, so far as I can tell), and we should be 
able to cope with it in general.

	-Daniel
*This .sig left intentionally blank*

Re: Lenovo 3000 N100 i8042 problems

[Renato S. Yamane]

[-- Attachment #1: Type: text/plain, Size: 424 bytes --]

Henrique de Moraes Holschuh wrote:
> I fell I need to warn you guys that you are likely breaking machines that
> match that DMI info but have a newer BIOS, unless they use different BIOSes
> (not enough data without a full dmidecode output from the other machine).

dmidecode just from 3000-N100?
Attached a dmidecode from a Lenovo Thinkpad T61.
I have a Lenovo 3000-V200 too. You want a dmidecode from it?

Regards,
Renato

[-- Attachment #2: dmidecode.txt --]
[-- Type: text/plain, Size: 14150 bytes --]

# dmidecode 2.9
SMBIOS 2.4 present.
73 structures occupying 2436 bytes.
Table at 0x000E0010.

Handle 0x0000, DMI type 0, 24 bytes
BIOS Information
	Vendor: LENOVO
	Version: 7LETC1WW (2.21 )
	Release Date: 07/01/2008
	Address: 0xE0000
	Runtime Size: 128 kB
	ROM Size: 4096 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
		BIOS ROM is socketed
		EDD is supported
		ACPI is supported
		USB legacy is supported
		BIOS boot specification is supported
		Targeted content distribution is supported
	BIOS Revision: 2.33
	Firmware Revision: 1.8

Handle 0x0001, DMI type 1, 27 bytes
System Information
	Manufacturer: LENOVO
	Product Name: 6457BB5
	Version: ThinkPad T61
	Serial Number: L3R2406
	UUID: E01A1C81-4975-11CB-8382-B82531DB6AF1
	Wake-up Type: Power Switch
	SKU Number: Not Specified
	Family: ThinkPad T61

Handle 0x0002, DMI type 2, 8 bytes
Base Board Information
	Manufacturer: LENOVO
	Product Name: 6457BB5
	Version: Not Available
	Serial Number: VF1A981M2DE

Handle 0x0003, DMI type 3, 13 bytes
Chassis Information
	Manufacturer: LENOVO
	Type: Notebook
	Lock: Not Present
	Version: Not Available
	Serial Number: Not Available
	Asset Tag: No Asset Information
	Boot-up State: Unknown
	Power Supply State: Unknown
	Thermal State: Unknown
	Security Status: Unknown

Handle 0x0004, DMI type 126, 13 bytes
Inactive

Handle 0x0005, DMI type 126, 13 bytes
Inactive

Handle 0x0006, DMI type 4, 35 bytes
Processor Information
	Socket Designation: None
	Type: Central Processor
	Family: Other
	Manufacturer: GenuineIntel
	ID: FB 06 00 00 FF FB EB BF
	Version: Intel(R) Core(TM)2 Duo CPU     T7500  @ 2.20GHz
	Voltage: 1.4 V
	External Clock: 200 MHz
	Max Speed: 2200 MHz
	Current Speed: 2200 MHz
	Status: Populated, Enabled
	Upgrade: None
	L1 Cache Handle: 0x000A
	L2 Cache Handle: 0x000C
	L3 Cache Handle: Not Provided
	Serial Number: Not Specified
	Asset Tag: Not Specified
	Part Number: Not Specified

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: 155 ns
	Type: DIMM SDRAM
	Installed Size: 1024 MB (Double-bank Connection)
	Enabled Size: 1024 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: 155 ns
	Type: DIMM SDRAM
	Installed Size: 1024 MB (Double-bank Connection)
	Enabled Size: 1024 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 Back
	Location: Internal
	Installed Size: 64 KB
	Maximum Size: 64 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 0x000B, DMI type 7, 19 bytes
Cache Information
	Socket Designation: Internal L1 Cache
	Configuration: Enabled, Socketed, Level 1
	Operational Mode: Write Back
	Location: Internal
	Installed Size: 64 KB
	Maximum Size: 64 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 0x000C, DMI type 7, 19 bytes
Cache Information
	Socket Designation: Internal L2 Cache
	Configuration: Enabled, Socketed, Level 2
	Operational Mode: Write Back
	Location: Internal
	Installed Size: 4096 KB
	Maximum Size: 4096 KB
	Supported SRAM Types:
		Burst
	Installed SRAM Type: Burst
	Speed: Unknown
	Error Correction Type: Single-bit ECC
	System Type: Unified
	Associativity: 8-way Set-associative

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: Microphone Jack
	External Connector Type: Mini Jack (headphones)
	Port Type: Audio Port

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

Handle 0x0010, DMI type 126, 9 bytes
Inactive

Handle 0x0011, DMI type 126, 9 bytes
Inactive

Handle 0x0012, 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 0x0013, 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 0x0014, 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 0x0015, 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 0x0016, 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 0x0017, DMI type 126, 9 bytes
Inactive

Handle 0x0018, DMI type 126, 9 bytes
Inactive

Handle 0x0019, DMI type 126, 9 bytes
Inactive

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 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 0x0020, DMI type 9, 13 bytes
System Slot Information
	Designation: ExpressCard Slot 1
	Type: x1 PCI Express
	Current Usage: Available
	Length: Other
	ID: 0
	Characteristics:
		Hot-plug devices are supported

Handle 0x0021, DMI type 9, 13 bytes
System Slot Information
	Designation: CardBus Slot 1
	Type: 32-bit PC Card (PCMCIA)
	Current Usage: Available
	Length: Other
	ID: Adapter 1, Socket 0
	Characteristics:
		5.0 V is provided
		3.3 V is provided
		PC Card-16 is supported
		Cardbus is supported
		Zoom Video is supported
		Modem ring resume is supported
		PME signal is supported
		Hot-plug devices are supported

Handle 0x0022, DMI type 126, 13 bytes
Inactive

Handle 0x0023, DMI type 126, 13 bytes
Inactive

Handle 0x0024, DMI type 9, 13 bytes
System Slot Information
	Designation: Media Card Slot 1
	Type: Other
	Current Usage: Available
	Length: Other
	Characteristics:
		Hot-plug devices are supported

Handle 0x0025, DMI type 126, 13 bytes
Inactive

Handle 0x0026, DMI type 126, 13 bytes
Inactive

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

Handle 0x0028, DMI type 11, 5 bytes
OEM Strings
	String 1: IBM ThinkPad Embedded Controller -[7KHT24WW-1.08    ]-

Handle 0x0029, DMI type 13, 22 bytes
BIOS Language Information
	Installable Languages: 1
		enUS
	Currently Installed Language: enUS

Handle 0x002A, 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, Not Full
	Change Token: 0x00000080
	Header Format: Type 1
	Supported Log Type Descriptors: 1
	Descriptor 1: POST error
	Data Format 1: POST results bitmap

Handle 0x002B, 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 0x002C, DMI type 17, 27 bytes
Memory Device
	Array Handle: 0x002B
	Error Information Handle: 0xFF01
	Total Width: 64 bits
	Data Width: 64 bits
	Size: 1024 MB
	Form Factor: SODIMM
	Set: None
	Locator: DIMM 1
	Bank Locator: Bank 0/1
	Type: DDR2
	Type Detail: Synchronous
	Speed: 667 MHz (1.5 ns)
	Manufacturer: Not Specified
	Serial Number: Not Specified
	Asset Tag: Not Specified
	Part Number: Not Specified

Handle 0x002D, DMI type 17, 27 bytes
Memory Device
	Array Handle: 0x002B
	Error Information Handle: 0xFF01
	Total Width: 64 bits
	Data Width: 64 bits
	Size: 1024 MB
	Form Factor: SODIMM
	Set: None
	Locator: DIMM 2
	Bank Locator: Bank 2/3
	Type: DDR2
	Type Detail: Synchronous
	Speed: 667 MHz (1.5 ns)
	Manufacturer: Not Specified
	Serial Number: Not Specified
	Asset Tag: Not Specified
	Part Number: Not Specified

Handle 0x002E, 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 0x002F, DMI type 19, 15 bytes
Memory Array Mapped Address
	Starting Address: 0x00000000000
	Ending Address: 0x0007FFFFFFF
	Range Size: 2 GB
	Physical Array Handle: 0x002B
	Partition Width: 0

Handle 0x0030, DMI type 20, 19 bytes
Memory Device Mapped Address
	Starting Address: 0x00000000000
	Ending Address: 0x0003FFFFFFF
	Range Size: 1 GB
	Physical Device Handle: 0x002C
	Memory Array Mapped Address Handle: 0x002F
	Partition Row Position: 1

Handle 0x0031, DMI type 20, 19 bytes
Memory Device Mapped Address
	Starting Address: 0x00040000000
	Ending Address: 0x0007FFFFFFF
	Range Size: 1 GB
	Physical Device Handle: 0x002D
	Memory Array Mapped Address Handle: 0x002F
	Partition Row Position: 1

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

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

Handle 0x0034, DMI type 22, 26 bytes
Portable Battery
	Location: Rear
	Manufacturer: Panasonic
	Name: 92P1133
	Design Capacity: 84240 mWh
	Design Voltage: 10800 mV
	SBDS Version: 03.01
	Maximum Error: Unknown
	SBDS Serial Number: 0072
	SBDS Manufacture Date: 2008-02-29
	SBDS Chemistry: LION
	OEM-specific Information: 0x00000000

Handle 0x0035, DMI type 126, 26 bytes
Inactive

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

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

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

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

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

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

Handle 0x003C, DMI type 134, 13 bytes
OEM-specific Type
	Header and Data:
		86 0D 3C 00 11 03 08 20 00 00 00 00 00

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

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

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

Handle 0x0040, DMI type 135, 35 bytes
OEM-specific Type
	Header and Data:
		87 23 40 00 54 50 07 02 42 41 59 20 49 2F 4F 20
		01 00 02 00 00 0A 00 48 1C 1E 1C 02 00 0E 00 F0
		01 F6 03

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

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

Handle 0x0043, DMI type 137, 28 bytes
OEM-specific Type
	Header and Data:
		89 1C 43 00 0C 02 00 01 01 00 00 01 50 57 4D 53
		20 49 6E 66 6F 72 6D 61 74 69 6F 6E

Handle 0x0044, DMI type 138, 40 bytes
OEM-specific Type
	Header and Data:
		8A 28 44 00 14 01 02 01 40 02 01 40 02 01 40 02
		01 40 01 40 42 49 4F 53 20 50 61 73 73 77 6F 72
		64 20 46 6F 72 6D 61 74

Handle 0x0045, DMI type 139, 37 bytes
OEM-specific Type
	Header and Data:
		8B 25 45 00 11 01 0A 00 00 00 00 00 00 00 00 00
		00 50 57 4D 53 20 4B 65 79 20 49 6E 66 6F 72 6D
		61 74 69 6F 6E

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

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

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

Re: Lenovo 3000 N100 i8042 problems

[Daniel Barkalow]

On Mon, 8 Sep 2008, Renato S. Yamane wrote:

> Henrique de Moraes Holschuh wrote:
> > I fell I need to warn you guys that you are likely breaking machines that
> > match that DMI info but have a newer BIOS, unless they use different BIOSes
> > (not enough data without a full dmidecode output from the other machine).
> 
> dmidecode just from 3000-N100?
> Attached a dmidecode from a Lenovo Thinkpad T61.
> I have a Lenovo 3000-V200 too. You want a dmidecode from it?

It's almost certainly only 3000 series that's interesting; I think they 
test the Thinkpads with Linux and wouldn't ship with a quirky BIOS there. 
The 3000 series only officially supports Windows, and so there can be 
problems (evidently, mine does something odd with the legacy mux, and 
newer ones do something odd with the active mux).

You might want to poke at the quirk in the patch in this thread and see if 
one or the other mode works better, or if they're the same on your 
machines. In any case, neither the patch that got into 2.6.25 nor the 
narrowing patch in this thread would affect either of your machines.

	-Daniel
*This .sig left intentionally blank*

Re: Lenovo 3000 N100 i8042 problems

[Renato S. Yamane]

[-- Attachment #1: Type: text/plain, Size: 773 bytes --]

Daniel Barkalow wrote:
> Renato S. Yamane wrote:
>> Henrique de Moraes Holschuh wrote:
>>> I fell I need to warn you guys that you are likely breaking machines that
>>> match that DMI info but have a newer BIOS, unless they use different BIOSes
>>> (not enough data without a full dmidecode output from the other machine).
>>
>> dmidecode just from 3000-N100?
>> Attached a dmidecode from a Lenovo Thinkpad T61.
>> I have a Lenovo 3000-V200 too. You want a dmidecode from it?
> 
> It's almost certainly only 3000 series that's interesting; I think they 
> test the Thinkpads with Linux and wouldn't ship with a quirky BIOS there.

Here is the dmidecode from a Lenovo 3000-V200.
I hope this help something.
Let me know if you need more info.

Best regards,
Renato S. Yamane

[-- Attachment #2: dmidecode_lenovo_3000-v200.txt --]
[-- Type: text/plain, Size: 10744 bytes --]

# dmidecode 2.9
SMBIOS 2.4 present.
45 structures occupying 1366 bytes.
Table at 0x000DC010.

Handle 0x0000, DMI type 0, 24 bytes
BIOS Information
	Vendor: LENOVO
	Version: 65ET59WW (0.10 )
	Release Date: 03/28/2008
	Address: 0xE6B90
	Runtime Size: 103536 bytes
	ROM Size: 1024 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
		ACPI is supported
		USB legacy is supported
		BIOS boot specification is supported
		Targeted content distribution is supported
	BIOS Revision: 0.10

Handle 0x0001, DMI type 1, 27 bytes
System Information
	Manufacturer: LENOVO
	Product Name: 076426P
	Version: LENOVO3000 V200
	Serial Number: LVB14P5
	UUID: 511F85E0-BFB8-11DC-8862-F2CB945B3A80
	Wake-up Type: Power Switch
	SKU Number: Not Specified
	Family: Not Specified

Handle 0x0002, DMI type 2, 8 bytes
Base Board Information
	Manufacturer: LENOVO
	Product Name: INVALID
	Version: Not Applicable
	Serial Number: 47AZ12Z

Handle 0x0003, DMI type 3, 17 bytes
Chassis Information
	Manufacturer: LENOVO
	Type: Notebook
	Lock: Not Present
	Version: N/A
	Serial Number: INVALID
	Asset Tag: No Asset Tag
	Boot-up State: Safe
	Power Supply State: Safe
	Thermal State: Safe
	Security Status: None
	OEM Information: 0x00001234

Handle 0x0004, DMI type 4, 35 bytes
Processor Information
	Socket Designation: U2E1
	Type: Central Processor
	Family: <OUT OF SPEC>
	Manufacturer: Intel
	ID: FD 06 00 00 FF FB EB BF
	Version: A0
	Voltage: 3.3 V
	External Clock: Unknown
	Max Speed: 2048 MHz
	Current Speed: 1800 MHz
	Status: Populated, Enabled
	Upgrade: ZIF Socket
	L1 Cache Handle: 0x0005
	L2 Cache Handle: 0x0006
	L3 Cache Handle: Not Provided
	Serial Number: Not Specified
	Asset Tag: Not Specified
	Part Number: Not Specified

Handle 0x0005, DMI type 7, 19 bytes
Cache Information
	Socket Designation: L1 Cache
	Configuration: Enabled, Socketed, Level 1
	Operational Mode: Write Back
	Location: Internal
	Installed Size: 64 KB
	Maximum Size: 64 KB
	Supported SRAM Types:
		Burst
		Pipeline Burst
		Asynchronous
	Installed SRAM Type: Asynchronous
	Speed: Unknown
	Error Correction Type: Unknown
	System Type: Unknown
	Associativity: Unknown

Handle 0x0006, DMI type 7, 19 bytes
Cache Information
	Socket Designation: L2 Cache
	Configuration: Enabled, Socketed, Level 2
	Operational Mode: Write Back
	Location: External
	Installed Size: 2048 KB
	Maximum Size: 4096 KB
	Supported SRAM Types:
		Burst
		Pipeline Burst
		Asynchronous
	Installed SRAM Type: Burst
	Speed: Unknown
	Error Correction Type: Unknown
	System Type: Unknown
	Associativity: Unknown

Handle 0x0007, DMI type 8, 9 bytes
Port Connector Information
	Internal Reference Designator: J19
	Internal Connector Type: 9 Pin Dual Inline (pin 10 cut)
	External Reference Designator: COM 1
	External Connector Type: DB-9 male
	Port Type: Serial Port 16550A Compatible

Handle 0x0008, DMI type 8, 9 bytes
Port Connector Information
	Internal Reference Designator: J1A1
	Internal Connector Type: None
	External Reference Designator: Keyboard
	External Connector Type: Circular DIN-8 male
	Port Type: Keyboard Port

Handle 0x0009, DMI type 8, 9 bytes
Port Connector Information
	Internal Reference Designator: J1A1
	Internal Connector Type: None
	External Reference Designator: PS/2 Mouse
	External Connector Type: Circular DIN-8 male
	Port Type: Mouse Port

Handle 0x000A, DMI type 9, 13 bytes
System Slot Information
	Designation: PCI Slot J8B3
	Type: 32-bit PCI
	Current Usage: Unknown
	Length: Long
	ID: 0
	Characteristics:
		5.0 V is provided
		3.3 V is provided

Handle 0x000B, DMI type 9, 13 bytes
System Slot Information
	Designation: PCI Slot S9B1
	Type: 32-bit PCI
	Current Usage: Unknown
	Length: Long
	ID: 0
	Characteristics:
		5.0 V is provided
		3.3 V is provided

Handle 0x000C, DMI type 9, 13 bytes
System Slot Information
	Designation: PEG Slot J6B2
	Type: 32-bit PCI Express
	Current Usage: Available
	Length: Long
	ID: 6
	Characteristics:
		5.0 V is provided
		3.3 V is provided

Handle 0x000D, DMI type 9, 13 bytes
System Slot Information
	Designation: PCI Express Slot J6B1
	Type: 32-bit PCI Express
	Current Usage: Available
	Length: Long
	ID: 7
	Characteristics:
		5.0 V is provided
		3.3 V is provided

Handle 0x000E, DMI type 9, 13 bytes
System Slot Information
	Designation: PCI Express Slot J6D1
	Type: 32-bit PCI Express
	Current Usage: In Use
	Length: Long
	ID: 8
	Characteristics:
		5.0 V is provided
		3.3 V is provided

Handle 0x000F, DMI type 9, 13 bytes
System Slot Information
	Designation: PCI Express Slot J8B4
	Type: 32-bit PCI Express
	Current Usage: In Use
	Length: Long
	ID: 9
	Characteristics:
		5.0 V is provided
		3.3 V is provided

Handle 0x0010, DMI type 9, 13 bytes
System Slot Information
	Designation: PCI Express Slot J8D1
	Type: 32-bit PCI Express
	Current Usage: Unknown
	Length: Long
	ID: 0
	Characteristics:
		5.0 V is provided
		3.3 V is provided

Handle 0x0011, DMI type 9, 13 bytes
System Slot Information
	Designation: PCI Express Slot J7B1
	Type: 32-bit PCI Express
	Current Usage: Unknown
	Length: Long
	ID: 0
	Characteristics:
		5.0 V is provided
		3.3 V is provided

Handle 0x0012, DMI type 10, 6 bytes
On Board Device Information
	Type: Sound
	Status: Disabled
	Description: HD-Audio

Handle 0x0013, DMI type 11, 5 bytes
OEM Strings
	String 1: This is the Intel Crestline
	String 2: Chipset CRB Platform

Handle 0x0014, DMI type 12, 5 bytes
System Configuration Options
	Option 1: Jumper settings can be described here.

Handle 0x0015, DMI type 15, 29 bytes
System Event Log
	Area Length: 16 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, Not Full
	Change Token: 0x00000002
	Header Format: Type 1
	Supported Log Type Descriptors: 3
	Descriptor 1: POST error
	Data Format 1: POST results bitmap
	Descriptor 2: Single-bit ECC memory error
	Data Format 2: Multiple-event
	Descriptor 3: Multi-bit ECC memory error
	Data Format 3: Multiple-event

Handle 0x0016, 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 0x0017, DMI type 17, 27 bytes
Memory Device
	Array Handle: 0x0016
	Error Information Handle: No Error
	Total Width: 32 bits
	Data Width: 32 bits
	Size: 512 MB
	Form Factor: SODIMM
	Set: 1
	Locator: M1
	Bank Locator: Bank 0
	Type: DDR2
	Type Detail: Synchronous
	Speed: 667 MHz (1.5 ns)
	Manufacturer: Not Specified
	Serial Number: Not Specified
	Asset Tag: Not Specified
	Part Number: Not Specified

Handle 0x0018, DMI type 17, 27 bytes
Memory Device
	Array Handle: 0x0016
	Error Information Handle: No Error
	Total Width: 32 bits
	Data Width: 32 bits
	Size: 512 MB
	Form Factor: SODIMM
	Set: 1
	Locator: M2
	Bank Locator: Bank 1
	Type: DDR2
	Type Detail: Synchronous
	Speed: 667 MHz (1.5 ns)
	Manufacturer: Not Specified
	Serial Number: Not Specified
	Asset Tag: Not Specified
	Part Number: Not Specified

Handle 0x0019, DMI type 19, 15 bytes
Memory Array Mapped Address
	Starting Address: 0x00000000000
	Ending Address: 0x0003FFFFFFF
	Range Size: 1 GB
	Physical Array Handle: 0x0016
	Partition Width: 0

Handle 0x001A, DMI type 20, 19 bytes
Memory Device Mapped Address
	Starting Address: 0x00000000000
	Ending Address: 0x0001FFFFFFF
	Range Size: 512 MB
	Physical Device Handle: 0x0017
	Memory Array Mapped Address Handle: 0x0019
	Partition Row Position: Unknown
	Interleave Position: Unknown
	Interleaved Data Depth: Unknown

Handle 0x001B, DMI type 20, 19 bytes
Memory Device Mapped Address
	Starting Address: 0x00020000000
	Ending Address: 0x0003FFFFFFF
	Range Size: 512 MB
	Physical Device Handle: 0x0018
	Memory Array Mapped Address Handle: 0x0019
	Partition Row Position: Unknown
	Interleave Position: Unknown
	Interleaved Data Depth: Unknown

Handle 0x001C, DMI type 23, 13 bytes
System Reset
	Status: Enabled
	Watchdog Timer: Present
	Boot Option: Do Not Reboot
	Boot Option On Limit: Do Not Reboot
	Reset Count: Unknown
	Reset Limit: Unknown
	Timer Interval: Unknown
	Timeout: Unknown

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

Handle 0x001E, DMI type 25, 9 bytes
	System Power Controls
	Next Scheduled Power-on: 12-31 23:59:59

Handle 0x001F, DMI type 26, 20 bytes
Voltage Probe
	Description: Voltage Probe
	Location: Processor
	Status: OK
	Maximum Value: Unknown
	Minimum Value: Unknown
	Resolution: Unknown
	Tolerance: Unknown
	Accuracy: Unknown
	OEM-specific Information: 0x00000000

Handle 0x0020, DMI type 27, 12 bytes
Cooling Device
	Temperature Probe Handle: 0x0021
	Type: Fan
	Status: OK
	OEM-specific Information: 0x00000000

Handle 0x0021, DMI type 28, 20 bytes
Temperature Probe
	Description: Temperature Probe
	Location: Processor
	Status: OK
	Maximum Value: Unknown
	Minimum Value Unknown
	Resolution: Unknown
	Tolerance: Unknown
	Accuracy: Unknown
	OEM-specific Information: 0x00000000

Handle 0x0022, DMI type 29, 20 bytes
Electrical Current Probe
	Description: Electrical Current Probe
	Location: Processor
	Status: OK
	Maximum Value: Unknown
	Minimum Value: Unknown
	Resolution: Unknown
	Tolerance: Unknown
	Accuracy: Unknown
	OEM-specific Information: 0x00000000

Handle 0x0023, DMI type 30, 6 bytes
Out-of-band Remote Access
	Manufacturer Name: Intel
	Inbound Connection: Enabled
	Outbound Connection: Disabled

Handle 0x0024, DMI type 32, 20 bytes
System Boot Information
	Status: <OUT OF SPEC>

Handle 0x0025, DMI type 129, 16 bytes
OEM-specific Type
	Header and Data:
		81 10 25 00 01 01 02 01 00 00 00 01 00 00 08 01
	Strings:
		Intel_ASF_001
		Intel_ASF_001

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

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

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

Handle 0x0029, DMI type 136, 6 bytes
OEM-specific Type
	Header and Data:
		88 06 29 00 FF FF

Handle 0x002A, DMI type 150, 14 bytes
OEM-specific Type
	Header and Data:
		96 0E 2A 00 01 01 00 00 00 00 00 00 00 00
	Strings:
		ABSOLUTE(PHOENIX) CLM

Handle 0x002B, DMI type 200, 7 bytes
OEM-specific Type
	Header and Data:
		C8 07 2B 00 01 02 03
	Strings:
		17C0
		             
		0001

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

Re: Lenovo 3000 N100 i8042 problems

[Henrique de Moraes Holschuh]

On Tue, 09 Sep 2008, Renato S. Yamane wrote:
> Daniel Barkalow wrote:
>> Renato S. Yamane wrote:
>>> Henrique de Moraes Holschuh wrote:
>>>> I fell I need to warn you guys that you are likely breaking machines that
>>>> match that DMI info but have a newer BIOS, unless they use different BIOSes
>>>> (not enough data without a full dmidecode output from the other machine).
>>>
>>> dmidecode just from 3000-N100?
>>> Attached a dmidecode from a Lenovo Thinkpad T61.
>>> I have a Lenovo 3000-V200 too. You want a dmidecode from it?
>>
>> It's almost certainly only 3000 series that's interesting; I think they 
>> test the Thinkpads with Linux and wouldn't ship with a quirky BIOS 
>> there.
>
> Here is the dmidecode from a Lenovo 3000-V200.
> I hope this help something.
> Let me know if you need more info.

Well, does that box suffer either of the issues (breaks either with the
patch or without the patch)?


-- 
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh

Re: Lenovo 3000 N100 i8042 problems

[Renato S. Yamane]

Henrique de Moraes Holschuh wrote:
> Renato S. Yamane wrote:
>> Daniel Barkalow wrote:
>>> Renato S. Yamane wrote:
>>>> Attached a dmidecode from a Lenovo Thinkpad T61.
>>>> I have a Lenovo 3000-V200 too. You want a dmidecode from it?
>>>
>>> It's almost certainly only 3000 series that's interesting; I think they 
>>> test the Thinkpads with Linux and wouldn't ship with a quirky BIOS 
>>> there.
>>
>> Here is the dmidecode from a Lenovo 3000-V200.
>> I hope this help something.
>> Let me know if you need more info.
> 
> Well, does that box suffer either of the issues (breaks either with the
> patch or without the patch)?

I use 2.6.26 Kernel available in Debian Lenny and don't have any problem.

Best regards,
Renato

Re: Lenovo 3000 N100 i8042 problems

[Henrique de Moraes Holschuh]

On Mon, 08 Sep 2008, Renato S. Yamane wrote:
> Henrique de Moraes Holschuh wrote:
> > I fell I need to warn you guys that you are likely breaking machines that
> > match that DMI info but have a newer BIOS, unless they use different BIOSes
> > (not enough data without a full dmidecode output from the other machine).
> 
> dmidecode just from 3000-N100?

No, we'd need the dmidecode output of the two *specific* 3000-N100
machines involved in the issue, so that we can know the specific BIOS
version they are running.

-- 
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh