Bug 4213

Summary:	i8042.c, keyboard not working since 2.6.10
Product:	Drivers	Reporter:	oleksiy (oleksiy)
Component:	Input Devices	Assignee:	Dmitry Torokhov (dmitry.torokhov)
Status:	REJECTED INSUFFICIENT_DATA
Severity:	high	CC:	protasnb, vojtech
Priority:	P2
Hardware:	i386
OS:	Linux
Kernel Version:	2.6.11-rcХ	Subsystem:
Regression:	Yes	Bisected commit-id:
Attachments:	kernel boot log, 2.6.11-rc4, keyboard is not detected

Description oleksiy 2005-02-14 14:37:29 UTC

Distribution:
Slackware 10.0

Hardware Environment:
Dell Inspiron 1100, notebook

Software Environment:
Problem Description:
Keyboard just don't work on any 2.6.11-rc. All other things work ok. With next
log-record at boot time:
kernel: i8042.c: Can't read CTR while initializing i8042.

While usual record is:
kernel: i8042.c: Warning: Keylock active.
kernel: serio: i8042 AUX port at 0x60,0x64 irq 12
kernel: serio: i8042 KBD port at 0x60,0x64 irq 1

Steps to reproduce:

Comment 1 oleksiy 2005-02-14 14:48:29 UTC

i8042.noacpi boot option helps, keyboard is detected.

Comment 2 Dmitry Torokhov 2005-02-14 14:52:53 UTC

Ok, the acpi probing is gone in Vojtech's tree (replaced by PNP driver)...

Comment 3 Vojtech Pavlik 2005-02-14 23:38:21 UTC

Does 'usb-handoff' on the kernel command line help?

Comment 4 Vojtech Pavlik 2005-02-14 23:39:29 UTC

Ahh, I see. It works without ACPI. Can you provide the full dmesg?
It's probably that ACPI reported wrong port numbers. We'll need to
add some sanity checks into that probe routine.

Comment 5 oleksiy 2005-02-15 01:51:15 UTC

Created attachment 4548 [details]
kernel boot log, 2.6.11-rc4, keyboard is not detected

kernel boot log, 2.6.11-rc4, keyboard is not detected

thanks for helping.

Comment 6 Vojtech Pavlik 2005-02-15 02:34:32 UTC

Feb 15 00:23:13 voodoo-1100 kernel: ACPI: PS/2 Keyboard Controller [KBC] at I/O
0x60, 0x66, irq 1
Feb 15 00:23:13 voodoo-1100 kernel: ACPI: PS/2 Mouse Controller [PS2M] at irq 12
Feb 15 00:23:13 voodoo-1100 kernel: i8042.c: Can't read CTR while initializing
i8042.

It's exactly what I thought. ACPI reports ports 0x60, 0x66 where the correct
numbers are 0x60,0x64.

In my current tree we're not using ACPI directly, rather than that we're using
ACPIPnP, but I suppose the information will be equally wrong here.

I'll implement a sanity check in the code to take care of that.

Until then, please use i8042.noacpi=1.

Comment 7 Dmitry Torokhov 2005-12-20 14:29:12 UTC

Oleksiy,

Could you please verify that keyboard is properly detected even without 
i8042.noacpi with later kernels (for example 2.6.14)?

Thanks!

Comment 8 tauwasser 2006-06-20 12:33:59 UTC

Hi,

I use Ubuntu Dapper Drake 6.06 and got the same problem with kernel
2.6.15-25-686, so I dare say it can be confirmed as 'not fixed' up until that
kernel. I'm not sure about 2.6.17.1 though, as I'm new to linux and unwilling to
compile a whole kernel.

Regards,

Tauwasser

Comment 9 Natalie Protasevich 2007-09-22 22:51:51 UTC

Oleksiy, tauwasser, can you confirm if the problem still present in current kernel? Maybe a different problem this time in #8.
Thanks.

Comment 10 Natalie Protasevich 2007-11-29 22:53:46 UTC

I think we can close this bug until someone claims the problem still exists.
Please reopen if the problem still there.