Skip to contentSkip to conversation

Issues detecting i8042 AUX port

DISCUSSION Peter Urbanec 3 participants 6 messages Oct 6, 2009 – Nov 8, 2009 HID

lore
Share & tools
lore
#0 lore raw

I have come across an issue that appears to be either timing sensitive or possibly a race condition when it comes to detecting i8042 AUX port.

The full story is at http://bugs.gentoo.org/show_bug.cgi?id=287019
including attachments that contain the results of dmesg output with i8042.debug turned on.

In a nutshell, I can run the same kernel on the same hardware and on some boots the AUX port will not be detected and on other boots it will come up fine. So far the only suspicion I have is that the initialisation of USB ports and/or SATA disks may cause some kind of delay that interferes with the i8042 detection of the AUX port.

It was suggested that I try adding my machine's DMI information to the noloop exception table. I do not believe that doing so makes much sense, since this is an intermittent problem, not an outright inability to raise the AUX IRQ.

Any ideas?

#1 lore raw
Quoted 13 lines · Peter Urbanec

I have come across an issue that appears to be either timing sensitive or possibly a race condition when it comes to detecting i8042 AUX port.

The full story is at http://bugs.gentoo.org/show_bug.cgi?id=287019
including attachments that contain the results of dmesg output with i8042.debug turned on.

In a nutshell, I can run the same kernel on the same hardware and on some boots the AUX port will not be detected and on other boots it will come up fine. So far the only suspicion I have is that the initialisation of USB ports and/or SATA disks may cause some kind of delay that interferes with the i8042 detection of the AUX port.

Quoted 6 lines

It was suggested that I try adding my machine's DMI information to the noloop exception table. I do not believe that doing so makes much sense, since this is an intermittent problem, not an outright inability to raise the AUX IRQ.

Any ideas?

Does booting with 'i8042.noloop' improve the situation?

Signature · 2 lines
Jiri Kosina
SUSE Labs, Novell Inc.
#2 lore raw
Quoted 6 lines · Jiri Kosina
Quoted 3 lines · Peter Urbanec

In a nutshell, I can run the same kernel on the same hardware and on some boots the AUX port will not be detected and on other boots it will come up fine.

Does booting with 'i8042.noloop' improve the situation?

Jirko,

Thanks for the suggestion. I have been testing the i8042.noloop workaround for a few weeks now. So far I have not not experienced any problems when booting with that option. I would say that the workaround can be declared as being effective.

I also applied Dmitry's patch to log the timeout condition when detecting the AUX port. Without the i8042.noloop option, the AUX port detection fails intermittently, but when it does, it causes an aux irq test timeout, which coincides with uhci_hcd USB hub initialisation. Perhaps the USB code somehow causes the loss of this interrupt.

Adding the DMI info for the machine to the i8042_dmi_noloop_table is perhaps not the most correct fix for the underlying problem, but it does get results.

Here is the relevant dmidecode data for the laptop:

Handle 0x0001, DMI type 1, 27 bytes

	Header and Data:
		01 1B 01 00 01 02 03 04 43 4E 46 37 33 38 35 30
		51 44 00 1B 24 AC 45 81 06 05 06
	Strings:
		48 65 77 6C 65 74 74 2D 50 61 63 6B 61 72 64 00
		"Hewlett-Packard"
		48 50 20 50 61 76 69 6C 69 6F 6E 20 64 76 39 35
		30 30 20 4E 6F 74 65 62 6F 6F 6B 20 50 43 20 20
		20 20 00
		"HP Pavilion dv9500 Notebook PC    "
		52 65 76 20 31 00
		"Rev 1"
		43 4E 46 37 33 38 35 30 51 44 00
		"CNF73850QD"
		47 53 37 34 38 55 41 23 41 42 41 20 00
		"GS748UA#ABA "
		31 30 33 43 5F 35 33 33 35 4B 56 00
		"103C_5335KV"

Best regards,

Peter Urbanec

#3 lore raw
Quoted 21 lines · Peter Urbanec
Quoted 6 lines · Jiri Kosina
Quoted 3 lines · Peter Urbanec

In a nutshell, I can run the same kernel on the same hardware and on some boots the AUX port will not be detected and on other boots it will come up fine.

Does booting with 'i8042.noloop' improve the situation?

Jirko,

Thanks for the suggestion. I have been testing the i8042.noloop workaround for a few weeks now. So far I have not not experienced any problems when booting with that option. I would say that the workaround can be declared as being effective.

I also applied Dmitry's patch to log the timeout condition when detecting the AUX port. Without the i8042.noloop option, the AUX port detection fails intermittently, but when it does, it causes an aux irq test timeout, which coincides with uhci_hcd USB hub initialisation. Perhaps the USB code somehow causes the loss of this interrupt.

Quoted 4 lines

Adding the DMI info for the machine to the i8042_dmi_noloop_table is perhaps not the most correct fix for the underlying problem, but it does get results.

I ended up just disabling aux irq delivery test in 2.6.32 on all laptops and portables (as long as they have sane PNP data)... There are just too many failures and the vast majority of them use PS/2 touchpads/trackpoints.

Signature · 1 line
Dmitry
#4 lore raw
In reply to Peter Urbanec
Quoted 20 lines · Peter Urbanec
Quoted 6 lines · Peter Urbanec
Quoted 3 lines

In a nutshell, I can run the same kernel on the same hardware and on some boots the AUX port will not be detected and on other boots it will come up fine.

Does booting with 'i8042.noloop' improve the situation?

Jirko,

Thanks for the suggestion. I have been testing the i8042.noloop workaround for a few weeks now. So far I have not not experienced any problems when booting with that option. I would say that the workaround can be declared as being effective.

I also applied Dmitry's patch to log the timeout condition when detecting the AUX port. Without the i8042.noloop option, the AUX port detection fails intermittently, but when it does, it causes an aux irq test timeout, which coincides with uhci_hcd USB hub initialisation. Perhaps the USB code somehow causes the loss of this interrupt.

Quoted 4 lines

Adding the DMI info for the machine to the i8042_dmi_noloop_table is perhaps not the most correct fix for the underlying problem, but it does get results.

Here is the relevant dmidecode data for the laptop:

Thanks for providing the data.

Does 2.6.32 work out of the box without any modifications? Dmitry added generic blacklist entry for all notebook chasis types, so 2.6.32 should have solved it for you.

Thanks,

Signature · 2 lines
Jiri Kosina
SUSE Labs, Novell Inc.
#5 lore raw
Quoted 1 line · Jiri Kosina

Does 2.6.32 work out of the box without any modifications? Dmitry added generic blacklist entry for all notebook chasis types, so 2.6.32 should have solved it for you.

I currently don't have the resources to do much testing, but once 2.6.32 is released and available as a Gentoo package, I'll re-test without the i8042.noloop option.

I expect that Dmitry's fix will be effective, but if there are any issues, I'll be back with more info.

Thanks.

Peter Urbanec