Re: Issues detecting i8042 AUX port

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, 29 Oct 2009, Peter Urbanec wrote:

> > On Wed, 7 Oct 2009, Peter Urbanec wrote:
> > > 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:

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,

-- 
Jiri Kosina
SUSE Labs, Novell Inc.
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Media Devel]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [Linux Wireless Networking]     [Linux Omap]

  Powered by Linux