* [2.6.22] i8042, ACPI, ipw2100 and issues reported by psmouse.c atkbd.c
@ 2007-09-30 21:42 legolas558
2007-10-11 8:04 ` Laptop keyboard unusable when ACPI is active was " legolas558
0 siblings, 1 reply; 13+ messages in thread
From: legolas558 @ 2007-09-30 21:42 UTC (permalink / raw)
To: linux-kernel
[-- Attachment #1: Type: text/plain, Size: 2678 bytes --]
Kernel: 2.6.22-r5
Kernel option: i8042.nomux=1
See attached full dmesg for more.
I have recently updated my kernel to 2.6.22 and - in the same occasion -
changed various options in the kernel .config; I cannot state that the
problem have arisen since kernel 2.6.22 but more probably since I
enabled ACPI.
My recent configuration changes have been also to xorg.conf (regarding
GLX and AIGLX), but I have no real clue about what is causing the
troubles. It must be a particular combination of kernel options which
triggers this faulty scenario.
The first problem I had to solve was about the mouse, not working properly:
-----
psmouse.c: TouchPad at isa0060/serio2/input0 lost sync at byte 1
psmouse.c: TouchPad at isa0060/serio2/input0 lost sync at byte 1
psmouse.c: TouchPad at isa0060/serio2/input0 lost sync at byte 1
psmouse.c: TouchPad at isa0060/serio2/input0 lost sync at byte 1
psmouse.c: TouchPad at isa0060/serio2/input0 lost sync at byte 1
psmouse.c: TouchPad at isa0060/serio2/input0 - driver resynched.
psmouse.c: TouchPad at isa0060/serio2/input0 lost sync at byte 4
psmouse.c: TouchPad at isa0060/serio2/input0 lost sync at byte 1
psmouse.c: TouchPad at isa0060/serio2/input0 - driver resynched.
-----
I fixed it adding i8042.nomux=1 in the kernel options.
The problem which still remains, and I can't fix or work it around, is
witnessed by the below dmesg lines:
-----
atkbd.c: Unknown key released (translated set 2, code 0xe0 on
isa0060/serio0).
atkbd.c: Use 'setkeycodes e060 <keycode>' to make it known.
atkbd.c: Unknown key released (translated set 2, code 0xe0 on
isa0060/serio0).
atkbd.c: Use 'setkeycodes e060 <keycode>' to make it known.
atkbd.c: Unknown key released (translated set 2, code 0xe0 on
isa0060/serio0).
atkbd.c: Use 'setkeycodes e060 <keycode>' to make it known.
-----
The release event for some keys is never caught, so all sorts of
troubles happen if for example I use the Del key and it stucks, or if I
use the Ctrl key and it never gets released...pushing again the stuck
key brings back the key in the proper status.
I could not find a pattern for the verification of the problem, it seems
to happen at random.
I /feel/ that this is still an i8042/ACPI chipset issue (note that I
have ipw2100 active when the problem happens; the mouse problem did not
happen when ipw2100 was disabled and I think the psmouse.c lines and
atkbd.c are someway related).
Can somebody please give me some clues about this issue, and possible
solutions? I have been searching the web for a couple of weeks and seems
like it is a common trouble of notebook users, but nobody has yet
published a solution.
Thanks,
--
Daniele C.
[-- Attachment #2: dmesg --]
[-- Type: text/plain, Size: 18490 bytes --]
Linux version 2.6.22-gentoo-r5 (root@machina) (gcc version 4.1.2 (Gentoo 4.1.2 p1.0.1)) #4 SMP Wed Sep 12 19:07:11 CEST 2007
BIOS-provided physical RAM map:
BIOS-e820: 0000000000000000 - 000000000009f800 (usable)
BIOS-e820: 000000000009f800 - 00000000000a0000 (reserved)
BIOS-e820: 00000000000ce000 - 00000000000d0000 (reserved)
BIOS-e820: 00000000000d8000 - 0000000000100000 (reserved)
BIOS-e820: 0000000000100000 - 000000001f6e0000 (usable)
BIOS-e820: 000000001f6e0000 - 000000001f6eb000 (ACPI data)
BIOS-e820: 000000001f6eb000 - 000000001f700000 (ACPI NVS)
BIOS-e820: 000000001f700000 - 0000000020000000 (reserved)
BIOS-e820: 00000000fec10000 - 00000000fec20000 (reserved)
BIOS-e820: 00000000ff800000 - 00000000ffc00000 (reserved)
BIOS-e820: 00000000fffffc00 - 0000000100000000 (reserved)
0MB HIGHMEM available.
502MB LOWMEM available.
Entering add_active_range(0, 0, 128736) 0 entries of 256 used
Zone PFN ranges:
DMA 0 -> 4096
Normal 4096 -> 128736
HighMem 128736 -> 128736
early_node_map[1] active PFN ranges
0: 0 -> 128736
On node 0 totalpages: 128736
DMA zone: 32 pages used for memmap
DMA zone: 0 pages reserved
DMA zone: 4064 pages, LIFO batch:0
Normal zone: 973 pages used for memmap
Normal zone: 123667 pages, LIFO batch:31
HighMem zone: 0 pages used for memmap
DMI present.
ACPI: RSDP 000F6700, 0014 (r0 PTLTD )
ACPI: RSDT 1F6E6557, 0030 (r1 PTLTD Montara 6040000 LTP 0)
ACPI: FACP 1F6EAED2, 0074 (r1 INTEL MONTARAG 6040000 PTL 50)
ACPI: DSDT 1F6E6A68, 446A (r1 INTEL MONTARAG 6040000 MSFT 100000E)
ACPI: FACS 1F6FBFC0, 0040
ACPI: BOOT 1F6EAFD8, 0028 (r1 PTLTD $SBFTBL$ 6040000 LTP 1)
ACPI: SSDT 1F6E6587, 04D9 (r1 INTEL GV3Ref 1001 MSFT 100000E)
ACPI: PM-Timer IO Port: 0x1008
Allocating PCI resources starting at 30000000 (gap: 20000000:dec10000)
Built 1 zonelists. Total pages: 127731
Kernel command line: root=/dev/hda3 vga=0x318 i8042.nomux=1 console=tty1
Local APIC disabled by BIOS -- you can enable it with "lapic"
mapped APIC to ffffd000 (013fd000)
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Initializing CPU#0
CPU 0 irqstacks, hard=c0558000 soft=c0538000
PID hash table entries: 2048 (order: 11, 8192 bytes)
Detected 1599.891 MHz processor.
Console: colour dummy device 80x25
Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
Memory: 502360k/514944k available (3172k kernel code, 11944k reserved, 828k data, 272k init, 0k highmem)
virtual kernel memory layout:
fixmap : 0xffe17000 - 0xfffff000 (1952 kB)
pkmap : 0xff800000 - 0xffc00000 (4096 kB)
vmalloc : 0xe0000000 - 0xff7fe000 ( 503 MB)
lowmem : 0xc0000000 - 0xdf6e0000 ( 502 MB)
.init : 0xc04ef000 - 0xc0533000 ( 272 kB)
.data : 0xc0419202 - 0xc04e8384 ( 828 kB)
.text : 0xc0100000 - 0xc0419202 (3172 kB)
Checking if this processor honours the WP bit even in supervisor mode... Ok.
Calibrating delay using timer specific routine.. 3201.27 BogoMIPS (lpj=16006380)
Mount-cache hash table entries: 512
CPU: After generic identify, caps: a7e9f9bf 00000000 00000000 00000000 00000180 00000000 00000000
CPU: L1 I cache: 32K, L1 D cache: 32K
CPU: L2 cache: 1024K
CPU: After all inits, caps: a7e9f9bf 00000000 00000000 00002040 00000180 00000000 00000000
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.
Compat vDSO mapped to ffffe000.
Checking 'hlt' instruction... OK.
SMP alternatives: switching to UP code
Freeing SMP alternatives: 16k freed
ACPI: Core revision 20070126
ACPI: setting ELCR to 0200 (from 0c00)
CPU0: Intel(R) Pentium(R) M processor 1600MHz stepping 05
SMP motherboard not detected.
Local APIC not detected. Using dummy APIC emulation.
Brought up 1 CPUs
NET: Registered protocol family 16
ACPI: bus type pci registered
PCI: PCI BIOS revision 2.10 entry at 0xfd6c4, last bus=3
PCI: Using configuration type 1
Setting up standard PCI resources
ACPI: Interpreter enabled
ACPI: (supports S0 S3 S4 S5)
ACPI: Using PIC for interrupt routing
ACPI: PCI Root Bridge [PCI0] (0000:00)
PCI: Probing PCI hardware (bus 00)
PCI quirk: region 1000-107f claimed by ICH4 ACPI/GPIO/TCO
PCI quirk: region 1180-11bf claimed by ICH4 GPIO
PCI: Transparent bridge - 0000:00:1e.0
PCI: Bus #03 (-#06) is hidden behind transparent bridge #02 (-#02) (try 'pci=assign-busses')
Please report the result to linux-kernel to fix this permanently
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PCIB._PRT]
ACPI: PCI Interrupt Link [LNKA] (IRQs 10 *11)
ACPI: PCI Interrupt Link [LNKB] (IRQs *10 11)
ACPI: PCI Interrupt Link [LNKC] (IRQs 10 *11)
ACPI: PCI Interrupt Link [LNKD] (IRQs *11)
ACPI: PCI Interrupt Link [LNKE] (IRQs *10 11)
ACPI: PCI Interrupt Link [LNKF] (IRQs *10 11)
ACPI: PCI Interrupt Link [LNKG] (IRQs *10 11)
ACPI: PCI Interrupt Link [LNKH] (IRQs 10 *11)
Linux Plug and Play Support v0.97 (c) Adam Belay
pnp: PnP ACPI init
ACPI: bus type pnp registered
pnp: PnP ACPI: found 12 devices
ACPI: ACPI bus type pnp unregistered
SCSI subsystem initialized
PCI: Using ACPI for IRQ routing
PCI: If a device doesn't work, try "pci=routeirq". If it helps, post a report
pnp: 00:04: ioport range 0x600-0x60f has been reserved
pnp: 00:04: iomem range 0xfec10000-0xfec1ffff could not be reserved
Time: tsc clocksource has been installed.
PCI: Bus 3, cardbus bridge: 0000:02:09.0
IO window: 00002000-000020ff
IO window: 00002400-000024ff
PREFETCH window: 30000000-33ffffff
MEM window: 38000000-3bffffff
PCI: Bridge: 0000:00:1e.0
IO window: 2000-2fff
MEM window: e0200000-e02fffff
PREFETCH window: 30000000-35ffffff
PCI: Enabling device 0000:00:1e.0 (0005 -> 0007)
PCI: Setting latency timer of device 0000:00:1e.0 to 64
ACPI: PCI Interrupt Link [LNKF] enabled at IRQ 10
PCI: setting IRQ 10 as level-triggered
ACPI: PCI Interrupt 0000:02:09.0[A] -> Link [LNKF] -> GSI 10 (level, low) -> IRQ 10
NET: Registered protocol family 2
IP route cache hash table entries: 4096 (order: 2, 16384 bytes)
TCP established hash table entries: 16384 (order: 5, 196608 bytes)
TCP bind hash table entries: 16384 (order: 5, 131072 bytes)
TCP: Hash tables configured (established 16384 bind 16384)
TCP reno registered
checking if image is initramfs... it is
Freeing initrd memory: 2425k freed
Simple Boot Flag at 0x36 set to 0x1
Machine check exception polling timer started.
audit: initializing netlink socket (disabled)
audit(1191186020.860:1): initialized
squashfs: version 3.2-r2 (2007/01/15) Phillip Lougher
SGI XFS with ACLs, security attributes, realtime, large block numbers, no debug enabled
SGI XFS Quota Management subsystem
OCFS2 1.3.3
OCFS2 Node Manager 1.3.3
OCFS2 DLM 1.3.3
OCFS2 DLMFS 1.3.3
OCFS2 User DLM kernel interface loaded
GFS2 (built Sep 12 2007 18:16:13) installed
Lock_Nolock (built Sep 12 2007 18:16:27) installed
io scheduler noop registered
io scheduler anticipatory registered (default)
io scheduler deadline registered
io scheduler cfq registered
Boot video device is 0000:00:02.0
intel_rng: FWH not detected
vesafb: framebuffer at 0xe8000000, mapped to 0xe0080000, using 6144k, total 8000k
vesafb: mode is 1024x768x32, linelength=4096, pages=1
vesafb: protected mode interface info at 00ff:44f0
vesafb: scrolling: redraw
vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Console: switching to colour frame buffer device 128x48
fb0: VESA VGA frame buffer device
ACPI: AC Adapter [AC] (on-line)
ACPI: Battery Slot [BAT0] (battery absent)
input: Power Button (FF) as /class/input/input0
ACPI: Power Button (FF) [PWRF]
input: Lid Switch as /class/input/input1
ACPI: Lid Switch [LID]
input: Sleep Button (CM) as /class/input/input2
ACPI: Sleep Button (CM) [SLP2]
isapnp: Scanning for PnP cards...
isapnp: No Plug & Play device found
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing enabled
RAMDISK driver initialized: 16 RAM disks of 8192K size 1024 blocksize
loop: module loaded
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
ICH4: IDE controller at PCI slot 0000:00:1f.1
PCI: Enabling device 0000:00:1f.1 (0005 -> 0007)
ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 11
PCI: setting IRQ 11 as level-triggered
ACPI: PCI Interrupt 0000:00:1f.1[A] -> Link [LNKC] -> GSI 11 (level, low) -> IRQ 11
ICH4: chipset revision 3
ICH4: not 100% native mode: will probe irqs later
ide0: BM-DMA at 0x1810-0x1817, BIOS settings: hda:DMA, hdb:pio
ide1: BM-DMA at 0x1818-0x181f, BIOS settings: hdc:DMA, hdd:pio
Probing IDE interface ide0...
hda: FUJITSU MHT2040AT, ATA DISK drive
hda: selected mode 0x45
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Probing IDE interface ide1...
hdc: QSI CD-RW/DVD-ROM SBW-242, ATAPI CD/DVD-ROM drive
hdc: selected mode 0x42
ide1 at 0x170-0x177,0x376 on irq 15
hda: max request size: 128KiB
hda: 78140160 sectors (40007 MB) w/2048KiB Cache, CHS=65535/16/63, UDMA(100)
hda: cache flushes supported
hda: hda1 hda2 hda3 hda4 < hda5 hda6 >
hdc: ATAPI 24X DVD-ROM CD-R/RW drive, 2048kB Cache, UDMA(33)
Uniform CD-ROM driver Revision: 3.20
PNP: PS/2 Controller [PNP0303:PS2K,PNP0f13:PS2M] at 0x60,0x64 irq 1,12
serio: i8042 KBD port at 0x60,0x64 irq 1
serio: i8042 AUX port at 0x60,0x64 irq 12
mice: PS/2 mouse device common for all mice
inport.c: Didn't find InPort mouse at 0x23c
logibm.c: Didn't find Logitech busmouse at 0x23c
input: AT Translated Set 2 keyboard as /class/input/input3
TCP cubic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
ieee80211: 802.11 data/management/control stack, git-1.1.13
ieee80211: Copyright (C) 2004-2005 Intel Corporation <jketreno@linux.intel.com>
ieee80211_crypt: registered algorithm 'NULL'
Using IPI No-Shortcut mode
Freeing unused kernel memory: 272k freed
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
ACPI: PCI Interrupt Link [LNKH] enabled at IRQ 11
ACPI: PCI Interrupt 0000:00:1d.7[D] -> Link [LNKH] -> GSI 11 (level, low) -> IRQ 11
PCI: Setting latency timer of device 0000:00:1d.7 to 64
ehci_hcd 0000:00:1d.7: EHCI Host Controller
ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 1
ehci_hcd 0000:00:1d.7: debug port 1
PCI: cache line size of 32 is not supported by device 0000:00:1d.7
ehci_hcd 0000:00:1d.7: irq 11, io mem 0xe0100000
ehci_hcd 0000:00:1d.7: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 6 ports detected
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
USB Universal Host Controller Interface driver v3.0
ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 11
ACPI: PCI Interrupt 0000:00:1d.0[A] -> Link [LNKA] -> GSI 11 (level, low) -> IRQ 11
PCI: Setting latency timer of device 0000:00:1d.0 to 64
uhci_hcd 0000:00:1d.0: UHCI Host Controller
uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 2
uhci_hcd 0000:00:1d.0: irq 11, io base 0x00001820
usb usb2: configuration #1 chosen from 1 choice
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 2 ports detected
ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 11
ACPI: PCI Interrupt 0000:00:1d.1[B] -> Link [LNKD] -> GSI 11 (level, low) -> IRQ 11
PCI: Setting latency timer of device 0000:00:1d.1 to 64
uhci_hcd 0000:00:1d.1: UHCI Host Controller
uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 3
uhci_hcd 0000:00:1d.1: irq 11, io base 0x00001840
usb usb3: configuration #1 chosen from 1 choice
hub 3-0:1.0: USB hub found
hub 3-0:1.0: 2 ports detected
ACPI: PCI Interrupt 0000:00:1d.2[C] -> Link [LNKC] -> GSI 11 (level, low) -> IRQ 11
PCI: Setting latency timer of device 0000:00:1d.2 to 64
uhci_hcd 0000:00:1d.2: UHCI Host Controller
uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 4
uhci_hcd 0000:00:1d.2: irq 11, io base 0x00001860
usb usb4: configuration #1 chosen from 1 choice
hub 4-0:1.0: USB hub found
hub 4-0:1.0: 2 ports detected
Synaptics Touchpad, model: 1, fw: 5.8, id: 0x9248b1, caps: 0x904713/0x4000
input: SynPS/2 Synaptics TouchPad as /class/input/input4
ohci_hcd: 2006 August 04 USB 1.1 'Open' Host Controller (OHCI) Driver
usbcore: registered new interface driver hiddev
usbcore: registered new interface driver usbhid
drivers/hid/usbhid/hid-core.c: v2.6:USB HID core driver
sl811: driver sl811-hcd, 19 May 2005
ACPI: PCI Interrupt 0000:02:03.0[A] -> Link [LNKF] -> GSI 10 (level, low) -> IRQ 10
ohci1394: fw-host0: OHCI-1394 1.0 (PCI): IRQ=[10] MMIO=[e0202000-e02027ff] Max Packet=[2048] IR/IT contexts=[8/8]
device-mapper: ioctl: 4.11.0-ioctl (2006-10-12) initialised: dm-devel@redhat.com
JFS: nTxBlock = 3947, nTxLock = 31583
Intel(R) PRO/1000 Network Driver - version 7.3.20-k2
Copyright (c) 1999-2006 Intel Corporation.
ieee1394: Host added: ID:BUS[0-00:1023] GUID[03e40a009c002042]
ReiserFS: hda3: found reiserfs format "3.6" with standard journal
ReiserFS: hda3: using ordered data mode
ReiserFS: hda3: journal params: device hda3, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
ReiserFS: hda3: checking transaction log (hda3)
ReiserFS: hda3: Using r5 hash to sort names
Linux agpgart interface v0.102 (c) Dave Jones
agpgart: Detected an Intel 855GM Chipset.
agpgart: Detected 8060K stolen memory.
agpgart: AGP aperture is 128M @ 0xe8000000
ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 10
ACPI: PCI Interrupt 0000:00:1f.3[B] -> Link [LNKB] -> GSI 10 (level, low) -> IRQ 10
ipw2100: Intel(R) PRO/Wireless 2100 Network Driver, git-1.2.2
ipw2100: Copyright(c) 2003-2006 Intel Corporation
ACPI: PCI Interrupt Link [LNKG] enabled at IRQ 10
ACPI: PCI Interrupt 0000:02:06.0[A] -> Link [LNKG] -> GSI 10 (level, low) -> IRQ 10
ipw2100: Detected Intel PRO/Wireless 2100 Network Connection
Real Time Clock Driver v1.12ac
wbsd: Winbond W83L51xD SD/MMC card interface driver
wbsd: Copyright(c) Pierre Ossman
mmc0: W83L51xD id 7112 at 0x820 irq 6 FIFO PnP
parport_pc 00:08: reported by Plug and Play ACPI
parport0: PC-style at 0x378, irq 7 [PCSPP,TRISTATE]
NET: Registered protocol family 23
nsc-ircc, chip->init
nsc-ircc, Found chip at base=0x02e
nsc-ircc, driver loaded (Dag Brattli)
eth0: Radio is disabled by RF switch.
b44.c:v1.01 (Jun 16, 2006)
ACPI: PCI Interrupt Link [LNKE] enabled at IRQ 10
ACPI: PCI Interrupt 0000:02:05.0[A] -> Link [LNKE] -> GSI 10 (level, low) -> IRQ 10
eth1: Broadcom 4400 10/100BaseT Ethernet 00:0a:e4:21:a0:f0
Yenta: CardBus bridge found at 0000:02:09.0 [17c0:3003]
Yenta: Using CSCINT to route CSC interrupts to PCI
Yenta: Routing CardBus interrupts to PCI
Yenta TI: socket 0000:02:09.0, mfunc 0x01001002, devctl 0x64
IrDA: Registered device irda0
nsc-ircc, Found dongle: Sharp RY5HD01
udev: renamed network interface eth0 to eth2
Yenta: ISA IRQ mask 0x0010, PCI irq 10
Socket status: 30000007
Yenta: Raising subordinate bus# of parent bus (#02) from #02 to #06
pcmcia: parent PCI bridge I/O window: 0x2000 - 0x2fff
cs: IO port probe 0x2000-0x2fff: clean.
pcmcia: parent PCI bridge Memory window: 0xe0200000 - 0xe02fffff
pcmcia: parent PCI bridge Memory window: 0x30000000 - 0x35ffffff
ACPI: PCI Interrupt 0000:00:1f.5[B] -> Link [LNKB] -> GSI 10 (level, low) -> IRQ 10
PCI: Setting latency timer of device 0000:00:1f.5 to 64
intel8x0_measure_ac97_clock: measured 59549 usecs
intel8x0: clocking to 48000
EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended
ReiserFS: hda5: found reiserfs format "3.6" with standard journal
ReiserFS: hda5: using ordered data mode
ReiserFS: hda5: journal params: device hda5, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
ReiserFS: hda5: checking transaction log (hda5)
ReiserFS: hda5: Using r5 hash to sort names
Adding 977248k swap on /dev/hda2. Priority:-1 extents:1 across:977248k
fsam7400: SW RF kill switch for Fujitsu Siemens Amilo M 7400, v0.5.0
fsam7400: Copyright(c) 2004 zwobbl ;)
WARNING: at arch/i386/kernel/smp.c:559 native_smp_call_function_mask()
[<c0112a24>] [<c0112808>] [<c0112808>] [<c0112808>] [<c0113c26>] [<c01257be>] [<e0b63000>] [<c01126b1>] [<c015d38d>] [<e0b63000>] [<c015d3e9>] [<c013c694>] [<c012fc5c>] [<c0103c7e>] [<c0410000>] =======================
ieee80211_crypt: registered algorithm 'WEP'
[drm] Initialized drm 1.1.0 20060810
ACPI: PCI Interrupt 0000:00:02.0[A] -> Link [LNKA] -> GSI 11 (level, low) -> IRQ 11
[drm] Initialized i915 1.6.0 20060119 on minor 0
[drm] Initialized i915 1.6.0 20060119 on minor 1
NET: Registered protocol family 10
lo: Disabled Privacy Extensions
eth2: no IPv6 routers present
atkbd.c: Unknown key released (translated set 2, code 0xe0 on isa0060/serio0).
atkbd.c: Use 'setkeycodes e060 <keycode>' to make it known.
atkbd.c: Unknown key released (translated set 2, code 0xe0 on isa0060/serio0).
atkbd.c: Use 'setkeycodes e060 <keycode>' to make it known.
atkbd.c: Unknown key released (translated set 2, code 0xe0 on isa0060/serio0).
atkbd.c: Use 'setkeycodes e060 <keycode>' to make it known.
atkbd.c: Unknown key released (translated set 2, code 0xe0 on isa0060/serio0).
atkbd.c: Use 'setkeycodes e060 <keycode>' to make it known.
atkbd.c: Unknown key released (translated set 2, code 0xe0 on isa0060/serio0).
atkbd.c: Use 'setkeycodes e060 <keycode>' to make it known.
atkbd.c: Unknown key released (translated set 2, code 0xe0 on isa0060/serio0).
atkbd.c: Use 'setkeycodes e060 <keycode>' to make it known.
atkbd.c: Unknown key released (translated set 2, code 0xe0 on isa0060/serio0).
atkbd.c: Use 'setkeycodes e060 <keycode>' to make it known.
atkbd.c: Unknown key released (translated set 2, code 0xe0 on isa0060/serio0).
atkbd.c: Use 'setkeycodes e060 <keycode>' to make it known.
atkbd.c: Unknown key released (translated set 2, code 0xe0 on isa0060/serio0).
atkbd.c: Use 'setkeycodes e060 <keycode>' to make it known.
atkbd.c: Unknown key released (translated set 2, code 0xe0 on isa0060/serio0).
atkbd.c: Use 'setkeycodes e060 <keycode>' to make it known.
atkbd.c: Unknown key released (translated set 2, code 0xe0 on isa0060/serio0).
atkbd.c: Use 'setkeycodes e060 <keycode>' to make it known.
atkbd.c: Unknown key released (translated set 2, code 0xe0 on isa0060/serio0).
atkbd.c: Use 'setkeycodes e060 <keycode>' to make it known.
^ permalink raw reply [flat|nested] 13+ messages in thread
* Laptop keyboard unusable when ACPI is active was Re: [2.6.22] i8042, ACPI, ipw2100 and issues reported by psmouse.c atkbd.c
2007-09-30 21:42 [2.6.22] i8042, ACPI, ipw2100 and issues reported by psmouse.c atkbd.c legolas558
@ 2007-10-11 8:04 ` legolas558
2007-10-12 11:52 ` Laptop keyboard unusable when ACPI is active legolas558
2007-10-18 19:52 ` Laptop keyboard unusable when ACPI is active was Re: [2.6.22] i8042, ACPI, ipw2100 and issues reported by psmouse.c atkbd.c Pavel Machek
0 siblings, 2 replies; 13+ messages in thread
From: legolas558 @ 2007-10-11 8:04 UTC (permalink / raw)
To: linux-kernel
legolas558@users.sourceforge.net ha scritto:
> Kernel: 2.6.22-r5
> Kernel option: i8042.nomux=1
I am now using kernel 2.6.22-r8 (Gentoo) and the following kernel options:
i8042.nomux=1 acpi=off
I have tried kernel 2.6.23-rc9 but the problem is still there.
> The problem which still remains, and I can't fix or work it around, is
> witnessed by the below dmesg lines:
> -----
> atkbd.c: Unknown key released (translated set 2, code 0xe0 on
> isa0060/serio0).
> atkbd.c: Use 'setkeycodes e060 <keycode>' to make it known.
> atkbd.c: Unknown key released (translated set 2, code 0xe0 on
> isa0060/serio0).
> atkbd.c: Use 'setkeycodes e060 <keycode>' to make it known.
> atkbd.c: Unknown key released (translated set 2, code 0xe0 on
> isa0060/serio0).
> atkbd.c: Use 'setkeycodes e060 <keycode>' to make it known.
> -----
> The release event for some keys is never caught, so all sorts of
> troubles happen if for example I use the Del key and it stucks, or if
> I use the Ctrl key and it never gets released...pushing again the
> stuck key brings back the key in the proper status.
With acpi=off the problem is totally worked around.
> Can somebody please give me some clues about this issue, and possible
> solutions? I have been searching the web for a couple of weeks and
> seems like it is a common trouble of notebook users, but nobody has
> yet published a solution.
I am trying to find a path myself in this issue - which dates back to at
least 2005 and has never been resolved.
I would now try some other kernel parameter in order to preserve ACPI
functionality and possibly prevent ACPI from messing up the keyboard IRQs.
Can somebody please give me istructions regarding the correct tests
(regarding kernel parameters and/or anything else) to perform in order
to better isolate the issue?
Related Gentoo bug tracker item:
http://bugs.gentoo.org/show_bug.cgi?id=194781
Other messages about the same kernel bug (many more can be found
googling around, and no solution yet):
https://lists.linux-foundation.org/pipermail/bugme-new/2005-January/011736.html
http://dev.laptop.org/ticket/2401
Regards,
--
Daniele C.
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: Laptop keyboard unusable when ACPI is active
2007-10-11 8:04 ` Laptop keyboard unusable when ACPI is active was " legolas558
@ 2007-10-12 11:52 ` legolas558
2007-11-22 7:24 ` legolas558
2007-10-18 19:52 ` Laptop keyboard unusable when ACPI is active was Re: [2.6.22] i8042, ACPI, ipw2100 and issues reported by psmouse.c atkbd.c Pavel Machek
1 sibling, 1 reply; 13+ messages in thread
From: legolas558 @ 2007-10-12 11:52 UTC (permalink / raw)
To: linux-kernel
I am posting this message just to say that this bug is being addressed
on the bug tracker:
http://bugzilla.kernel.org/show_bug.cgi?id=9147
Regards,
--
Daniele C.
legolas558@users.sourceforge.net ha scritto:
> legolas558@users.sourceforge.net ha scritto:
>
>> Kernel: 2.6.22-r5
>> Kernel option: i8042.nomux=1
>>
> I am now using kernel 2.6.22-r8 (Gentoo) and the following kernel options:
>
> i8042.nomux=1 acpi=off
>
> I have tried kernel 2.6.23-rc9 but the problem is still there.
>
>
>> The problem which still remains, and I can't fix or work it around, is
>> witnessed by the below dmesg lines:
>> -----
>> atkbd.c: Unknown key released (translated set 2, code 0xe0 on
>> isa0060/serio0).
>> atkbd.c: Use 'setkeycodes e060 <keycode>' to make it known.
>> atkbd.c: Unknown key released (translated set 2, code 0xe0 on
>> isa0060/serio0).
>> atkbd.c: Use 'setkeycodes e060 <keycode>' to make it known.
>> atkbd.c: Unknown key released (translated set 2, code 0xe0 on
>> isa0060/serio0).
>> atkbd.c: Use 'setkeycodes e060 <keycode>' to make it known.
>> -----
>> The release event for some keys is never caught, so all sorts of
>> troubles happen if for example I use the Del key and it stucks, or if
>> I use the Ctrl key and it never gets released...pushing again the
>> stuck key brings back the key in the proper status.
>>
> With acpi=off the problem is totally worked around.
>
>
>> Can somebody please give me some clues about this issue, and possible
>> solutions? I have been searching the web for a couple of weeks and
>> seems like it is a common trouble of notebook users, but nobody has
>> yet published a solution.
>>
> I am trying to find a path myself in this issue - which dates back to at
> least 2005 and has never been resolved.
>
> I would now try some other kernel parameter in order to preserve ACPI
> functionality and possibly prevent ACPI from messing up the keyboard IRQs.
> Can somebody please give me istructions regarding the correct tests
> (regarding kernel parameters and/or anything else) to perform in order
> to better isolate the issue?
>
> Related Gentoo bug tracker item:
> http://bugs.gentoo.org/show_bug.cgi?id=194781
>
> Other messages about the same kernel bug (many more can be found
> googling around, and no solution yet):
> https://lists.linux-foundation.org/pipermail/bugme-new/2005-January/011736.html
> http://dev.laptop.org/ticket/2401
>
> Regards,
> --
> Daniele C.
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
>
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: Laptop keyboard unusable when ACPI is active was Re: [2.6.22] i8042, ACPI, ipw2100 and issues reported by psmouse.c atkbd.c
2007-10-11 8:04 ` Laptop keyboard unusable when ACPI is active was " legolas558
2007-10-12 11:52 ` Laptop keyboard unusable when ACPI is active legolas558
@ 2007-10-18 19:52 ` Pavel Machek
2007-10-20 11:47 ` legolas558
2007-10-21 11:07 ` legolas558
1 sibling, 2 replies; 13+ messages in thread
From: Pavel Machek @ 2007-10-18 19:52 UTC (permalink / raw)
To: legolas558; +Cc: linux-kernel
Hi!
> legolas558@users.sourceforge.net ha scritto:
> > Kernel: 2.6.22-r5
> > Kernel option: i8042.nomux=1
> I am now using kernel 2.6.22-r8 (Gentoo) and the following kernel options:
>
> i8042.nomux=1 acpi=off
>
> I have tried kernel 2.6.23-rc9 but the problem is still there.
Try usb keyboard.
Are you experiencing unusually high latencies in acpi mode?
Any unusual activity on top?
Try disabling lm_sensors.
Try disabling acpi embedded controller.
Is it smp box?
Try watching keyboard interrupts. Are they lost?
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: Laptop keyboard unusable when ACPI is active was Re: [2.6.22] i8042, ACPI, ipw2100 and issues reported by psmouse.c atkbd.c
2007-10-18 19:52 ` Laptop keyboard unusable when ACPI is active was Re: [2.6.22] i8042, ACPI, ipw2100 and issues reported by psmouse.c atkbd.c Pavel Machek
@ 2007-10-20 11:47 ` legolas558
2007-10-20 18:33 ` Pavel Machek
2007-10-21 11:07 ` legolas558
1 sibling, 1 reply; 13+ messages in thread
From: legolas558 @ 2007-10-20 11:47 UTC (permalink / raw)
To: Pavel Machek; +Cc: linux-kernel
Pavel Machek ha scritto:
> Hi!
>
Hi! Finally an answer, thank you.
>> legolas558@users.sourceforge.net ha scritto:
>>
>>> Kernel: 2.6.22-r5
>>> Kernel option: i8042.nomux=1
>>>
>> I am now using kernel 2.6.22-r8 (Gentoo) and the following kernel options:
>>
>> i8042.nomux=1 acpi=off
>>
>> I have tried kernel 2.6.23-rc9 but the problem is still there.
>>
>
> Try usb keyboard.
>
I will get one within 24 hours.
> Are you experiencing unusually high latencies in acpi mode?
>
Yes.
> Any unusual activity on top?
>
Xorg with XFCE4 - it even happens opening up a mousepad and typing
something in it. I do not have particular services running, I have
apache, mysql and samba. I have installed it on July, so it's a pretty
new system - the problem didn't happen before the most recent kernels.
> Try disabling lm_sensors.
>
I will and report here.
> Try disabling acpi embedded controller.
>
How can I accomplish this? Are you referring to the i8042?
> Is it smp box?
>
It is a laptop (Maxdata Pro 7000 DX) with an Intel Centrino 1.6 GhZ
(pentium-m), so it is not.
> Try watching keyboard interrupts. Are they lost?
>
I am pretty sure they are. I think that ACPI pauses interrupts for a
while (100ms?) and so some keyboard interrupts are lost.
See also http://bugzilla.kernel.org/show_bug.cgi?id=9147
I will come up with a test for lm_sensors and the USB keyboard as soon
as possible.
Thank you very much
--
Daniele
> Pavel
>
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: Laptop keyboard unusable when ACPI is active was Re: [2.6.22] i8042, ACPI, ipw2100 and issues reported by psmouse.c atkbd.c
2007-10-20 11:47 ` legolas558
@ 2007-10-20 18:33 ` Pavel Machek
2007-10-21 9:43 ` legolas558
0 siblings, 1 reply; 13+ messages in thread
From: Pavel Machek @ 2007-10-20 18:33 UTC (permalink / raw)
To: legolas558; +Cc: linux-kernel
Hi!
> > Try disabling acpi embedded controller.
> >
> How can I accomplish this? Are you referring to the i8042?
rmmod acpi_ec or how is it called. But I'm not sure how easy this is.
> > Try watching keyboard interrupts. Are they lost?
> >
> I am pretty sure they are. I think that ACPI pauses interrupts for a
> while (100ms?) and so some keyboard interrupts are lost.
input layer can poll keyboard on its own, perhaps that helps?
Can you try to measure the interrupt latencies?
Does this happen in init=/bin/bash?
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: Laptop keyboard unusable when ACPI is active was Re: [2.6.22] i8042, ACPI, ipw2100 and issues reported by psmouse.c atkbd.c
2007-10-20 18:33 ` Pavel Machek
@ 2007-10-21 9:43 ` legolas558
2007-11-24 4:27 ` Len Brown
0 siblings, 1 reply; 13+ messages in thread
From: legolas558 @ 2007-10-21 9:43 UTC (permalink / raw)
To: Pavel Machek; +Cc: linux-kernel
[-- Attachment #1: Type: text/plain, Size: 1660 bytes --]
Pavel Machek ha scritto:
> Hi!
Hi!
>>> Try disabling acpi embedded controller.
>>>
>>>
>> How can I accomplish this? Are you referring to the i8042?
>>
>
> rmmod acpi_ec or how is it called. But I'm not sure how easy this is.
>
My lsmod doesn't list any acpi module - but I have kacpid, kacpi_listen
and hald-addon-acpi processes running.
I have compiled the kernel with embedded ACPI support, not modular -
maybe that's what you are talking about?
>
>>> Try watching keyboard interrupts. Are they lost?
>>>
>>>
>> I am pretty sure they are. I think that ACPI pauses interrupts for a
>> while (100ms?) and so some keyboard interrupts are lost.
>>
> input layer can poll keyboard on its own, perhaps that helps?
>
I am not yet very good at kernel hacking - however yes, it gives me more
clues about identifying the issue (see also below link).
> Can you try to measure the interrupt latencies?
>
I will try to do it myself, however somebody else the same problem of
mine has already made the tests, please see
http://dev.laptop.org/ticket/2401
> Does this happen in init=/bin/bash?
>
I will perform a test, however the problem rarely verifies in a VT
console. I have tried both the kbd and keyboard drivers of X, without
any difference. The keyboard problem happens a lot more when plugging in
the battery (more ACPI traffic?).
I have emerged lm_sensors but can't get it running - it keeps saying "No
sensors found!" and complaining about kernel drivers not properly setup.
I have attached the output of sensors-detect, from which it seems that
the kernel is OK.
Thank you,
--
Daniele
> Pavel
>
>
[-- Attachment #2: sensors-detect.log --]
[-- Type: text/x-log, Size: 5738 bytes --]
# sensors-detect revision 4171 (2006-09-24 03:37:01 -0700)
This program will help you determine which kernel modules you need
to load to use lm_sensors most effectively. It is generally safe
and recommended to accept the default answers to all questions,
unless you know what you're doing.
We can start with probing for (PCI) I2C or SMBus adapters.
Do you want to probe now? (YES/no): Y
Probing for PCI bus adapters...
Use driver `i2c-i801' for device 0000:00:1f.3: Intel 82801DB ICH4
We will now try to load each adapter module in turn.
Module `i2c-i801' already loaded.
If you have undetectable or unsupported adapters, you can have them
scanned by manually loading the modules before running this script.
We are now going to do the I2C/SMBus adapter probings. Some chips may
be double detected; we choose the one with the highest confidence
value in that case.
If you found that the adapter hung after probing a certain address,
you can specify that address to remain unprobed.
Next adapter: SMBus I801 adapter at 1880
Do you want to scan it? (YES/no/selectively): Y
Client found at address 0x08
Client found at address 0x1a
Probing for `Analog Devices ADM1021'... No
Probing for `Analog Devices ADM1021A/ADM1023'... No
Probing for `Maxim MAX1617'... No
Probing for `Maxim MAX1617A'... No
Probing for `TI THMC10'... No
Probing for `National Semiconductor LM84'... No
Probing for `Genesys Logic GL523SM'... No
Probing for `Onsemi MC1066'... No
Probing for `Maxim MAX1619'... No
Probing for `National Semiconductor LM82/LM83'... No
Probing for `Philips Semiconductors PCA9556'... No
Client found at address 0x44
Probing for `Maxim MAX6633/MAX6634/MAX6635'... No
Client found at address 0x51
Handled by driver `eeprom' (already loaded), chip type `eeprom'
Client found at address 0x57
Handled by driver `eeprom' (already loaded), chip type `eeprom'
Client found at address 0x69
Some chips are also accessible through the ISA I/O ports. We have to
write to arbitrary I/O ports to probe them. This is usually safe though.
Yes, you do have ISA I/O ports even if you do not have any ISA slots!
Do you want to scan the ISA I/O ports? (YES/no): Y
Probing for `National Semiconductor LM78' at 0x290... No
Probing for `National Semiconductor LM78-J' at 0x290... No
Probing for `National Semiconductor LM79' at 0x290... No
Probing for `Winbond W83781D' at 0x290... No
Probing for `Winbond W83782D' at 0x290... No
Probing for `Winbond W83627HF' at 0x290... No
Probing for `Silicon Integrated Systems SIS5595'... No
Probing for `VIA VT82C686 Integrated Sensors'... No
Probing for `VIA VT8231 Integrated Sensors'... No
Probing for `AMD K8 thermal sensors'... No
Probing for `IPMI BMC KCS' at 0xca0... No
Probing for `IPMI BMC SMIC' at 0xca8... No
Some Super I/O chips may also contain sensors. We have to write to
standard I/O ports to probe them. This is usually safe.
Do you want to scan for Super I/O sensors? (YES/no): Y
Probing for Super-I/O at 0x2e/0x2f
Trying family `ITE'... Yes
Found unknown chip with ID 0xea11
Trying family `National Semiconductor'... Yes
Found `Nat. Semi. PC8739x Super IO'
(no hardware monitoring capabilities)
Trying family `SMSC'... Yes
Found unknown chip with ID 0xea11
Trying family `VIA/Winbond/Fintek'... Yes
Found unknown chip with ID 0xea11
Probing for Super-I/O at 0x4e/0x4f
Trying family `ITE'... No
Trying family `National Semiconductor'... No
Trying family `SMSC'... No
Trying family `VIA/Winbond/Fintek'... No
Now follows a summary of the probes I have just done.
Just press ENTER to continue:
Driver `eeprom' (should be inserted):
Detects correctly:
* Bus `SMBus I801 adapter at 1880'
Busdriver `i2c-i801', I2C address 0x51
Chip `eeprom' (confidence: 6)
* Bus `SMBus I801 adapter at 1880'
Busdriver `i2c-i801', I2C address 0x57
Chip `eeprom' (confidence: 6)
EEPROMs are *NOT* sensors! They are data storage chips commonly
found on memory modules (SPD), in monitors (EDID), or in some
laptops, for example.
I will now generate the commands needed to load the required modules.
Just press ENTER to continue:
If you want to load the modules at startup, generate a config file
below and make sure lm_sensors gets started at boot time; e.g
$ rc-update add lm_sensors default
To make the sensors modules behave correctly, add these lines to
/etc/modules.d/lm_sensors and run modules-update:
#----cut here----
# I2C module options
alias char-major-89 i2c-dev
#----cut here----
If you have some drivers built into your kernel, the list above will
contain too many modules. Skip the appropriate ones! You really
should try these commands right now to make sure everything is
working properly. Monitoring programs won't work until the needed
modules are loaded.
To load everything that is needed, execute the commands below...
#----cut here----
# I2C adapter drivers
modprobe i2c-i801
# Chip drivers
modprobe eeprom
# sleep 2 # optional
/usr/bin/sensors -s # recommended
#----end cut here----
Do you want to overwrite /etc/conf.d/lm_sensors? Enter s to specify other file name?
(yes/NO/s): Y
Done.
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: Laptop keyboard unusable when ACPI is active was Re: [2.6.22] i8042, ACPI, ipw2100 and issues reported by psmouse.c atkbd.c
2007-10-18 19:52 ` Laptop keyboard unusable when ACPI is active was Re: [2.6.22] i8042, ACPI, ipw2100 and issues reported by psmouse.c atkbd.c Pavel Machek
2007-10-20 11:47 ` legolas558
@ 2007-10-21 11:07 ` legolas558
1 sibling, 0 replies; 13+ messages in thread
From: legolas558 @ 2007-10-21 11:07 UTC (permalink / raw)
To: Pavel Machek; +Cc: linux-kernel
Pavel Machek ha scritto:
> Hi!
>> egolas558@users.sourceforge.net ha scritto:
>>
>>> Kernel: 2.6.22-r5
>>> Kernel option: i8042.nomux=1
>>>
>> I am now using kernel 2.6.22-r8 (Gentoo) and the following kernel options:
>>
>> i8042.nomux=1 acpi=off
>>
>> I have tried kernel 2.6.23-rc9 but the problem is still there.
>>
> Try usb keyboard.
>
The USB keyboard is not affected by the problem, and more importantly it
has not the latencies in ACPI mode which the embedded PS2 keyboard has.
> Try disabling lm_sensors.
>
lm_sensors was not installed at all. I have now enabled HWMON and other
CONFIG_I2C_* kernel config parameters to use lm_sensors (without success).
> Is it smp box?
>
It is not but from the sensors-detect's log seems like the motherboard
supports it.
Best regards,
--
Daniele
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: Laptop keyboard unusable when ACPI is active
2007-10-12 11:52 ` Laptop keyboard unusable when ACPI is active legolas558
@ 2007-11-22 7:24 ` legolas558
2007-11-24 4:21 ` Len Brown
0 siblings, 1 reply; 13+ messages in thread
From: legolas558 @ 2007-11-22 7:24 UTC (permalink / raw)
To: linux-kernel; +Cc: Pavel Machek, mnowak, shaohua.li
Hi all,
some upates about this issue (see also bug 9147
http://bugzilla.kernel.org/show_bug.cgi?id=9147 ).
The 'ac', 'battery' and 'thermal' modules (compiled as stand-alone) do
cause the bug; it suffices that one of them (or any set of them) is
loaded to trigger the bug either immediately or after some time.
If none of them is loaded into memory, the bug does not happen.
Also, the 'battery' module does not generate system messages although
the problem is equally verified.
The 'thermal' module instead, when loaded with 'modprobe thermal',
causes the enter key pressed to execute the command to be indefinitively
repeated into any terminal. This is currently a perfectly reproducible
testcase for bug 9147.
The bug has been confirmed by at least another user (with different
hardware configuration); please reply for either bug addressing or
confirmation.
The current known best workaround to this bug is to compile all the
above mentioned ACPI modules as stand-alone and to not (auto)load them
(loosing their vital functionalities, since we are talking about laptops
here, see http://gentoo-wiki.com/HARDWARE_Maxdata_Pro_7000_DX for an
example of affected hardware).
It is also important to note that this bug always comes with bug 8740
http://bugzilla.kernel.org/show_bug.cgi?id=8740 (also confirmed and also
an ACPI issue).
Best regards,
--
Daniele C.
legolas558@users.sourceforge.net ha scritto:
> I am posting this message just to say that this bug is being addressed
> on the bug tracker:
> http://bugzilla.kernel.org/show_bug.cgi?id=9147
>
> Regards,
> --
> Daniele C.
>
>
> legolas558@users.sourceforge.net ha scritto:
>
>> legolas558@users.sourceforge.net ha scritto:
>>
>>
>>> Kernel: 2.6.22-r5
>>> Kernel option: i8042.nomux=1
>>>
>>>
>> I am now using kernel 2.6.22-r8 (Gentoo) and the following kernel options:
>>
>> i8042.nomux=1 acpi=off
>>
>> I have tried kernel 2.6.23-rc9 but the problem is still there.
>>
>>
>>
>>> The problem which still remains, and I can't fix or work it around, is
>>> witnessed by the below dmesg lines:
>>> -----
>>> atkbd.c: Unknown key released (translated set 2, code 0xe0 on
>>> isa0060/serio0).
>>> atkbd.c: Use 'setkeycodes e060 <keycode>' to make it known.
>>> atkbd.c: Unknown key released (translated set 2, code 0xe0 on
>>> isa0060/serio0).
>>> atkbd.c: Use 'setkeycodes e060 <keycode>' to make it known.
>>> atkbd.c: Unknown key released (translated set 2, code 0xe0 on
>>> isa0060/serio0).
>>> atkbd.c: Use 'setkeycodes e060 <keycode>' to make it known.
>>> -----
>>> The release event for some keys is never caught, so all sorts of
>>> troubles happen if for example I use the Del key and it stucks, or if
>>> I use the Ctrl key and it never gets released...pushing again the
>>> stuck key brings back the key in the proper status.
>>>
>>>
>> With acpi=off the problem is totally worked around.
>>
>>
>>
>>> Can somebody please give me some clues about this issue, and possible
>>> solutions? I have been searching the web for a couple of weeks and
>>> seems like it is a common trouble of notebook users, but nobody has
>>> yet published a solution.
>>>
>>>
>> I am trying to find a path myself in this issue - which dates back to at
>> least 2005 and has never been resolved.
>>
>> I would now try some other kernel parameter in order to preserve ACPI
>> functionality and possibly prevent ACPI from messing up the keyboard IRQs.
>> Can somebody please give me istructions regarding the correct tests
>> (regarding kernel parameters and/or anything else) to perform in order
>> to better isolate the issue?
>>
>> Related Gentoo bug tracker item:
>> http://bugs.gentoo.org/show_bug.cgi?id=194781
>>
>> Other messages about the same kernel bug (many more can be found
>> googling around, and no solution yet):
>> https://lists.linux-foundation.org/pipermail/bugme-new/2005-January/011736.html
>> http://dev.laptop.org/ticket/2401
>>
>> Regards,
>> --
>> Daniele C.
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: Laptop keyboard unusable when ACPI is active
2007-11-22 7:24 ` legolas558
@ 2007-11-24 4:21 ` Len Brown
2007-11-24 19:08 ` legolas558
0 siblings, 1 reply; 13+ messages in thread
From: Len Brown @ 2007-11-24 4:21 UTC (permalink / raw)
To: legolas558; +Cc: linux-kernel, Pavel Machek, mnowak, shaohua.li
On Thursday 22 November 2007 02:24, legolas558@users.sourceforge.net wrote:
> It is also important to note that this bug always comes with bug 8740
> http://bugzilla.kernel.org/show_bug.cgi?id=8740 (also confirmed and also
> an ACPI issue).
No, 8740 is not an ACPI issue.
http://bugzilla.kernel.org/show_bug.cgi?id=8740#c2
-Len
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: Laptop keyboard unusable when ACPI is active was Re: [2.6.22] i8042, ACPI, ipw2100 and issues reported by psmouse.c atkbd.c
2007-10-21 9:43 ` legolas558
@ 2007-11-24 4:27 ` Len Brown
2007-11-24 19:14 ` legolas558
0 siblings, 1 reply; 13+ messages in thread
From: Len Brown @ 2007-11-24 4:27 UTC (permalink / raw)
To: legolas558; +Cc: Pavel Machek, linux-kernel
On Sunday 21 October 2007 05:43, legolas558@users.sourceforge.net wrote:
> I have emerged lm_sensors but can't get it running - it keeps saying "No
> sensors found!" and complaining about kernel drivers not properly setup.
> I have attached the output of sensors-detect, from which it seems that
> the kernel is OK.
In this case, getting sensors installed is the opposite of what you want to do.
The idea is to simplify the system until it works, then figure out what
simplification made it work.
ie. disable sensors entirely by building a kernel with CONFIG_HWMON=n
If that makes things work, then it is a clue.
If that was disabled already, then just keep it disabled.
cheers,
-Len
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: Laptop keyboard unusable when ACPI is active
2007-11-24 4:21 ` Len Brown
@ 2007-11-24 19:08 ` legolas558
0 siblings, 0 replies; 13+ messages in thread
From: legolas558 @ 2007-11-24 19:08 UTC (permalink / raw)
To: linux-kernel; +Cc: Len Brown
Len Brown ha scritto:
> On Thursday 22 November 2007 02:24, legolas558@users.sourceforge.net wrote:
>> It is also important to note that this bug always comes with bug 8740
>> http://bugzilla.kernel.org/show_bug.cgi?id=8740 (also confirmed and also
>> an ACPI issue).
>>
> No, 8740 is not an ACPI issue.
> http://bugzilla.kernel.org/show_bug.cgi?id=8740#c2
>
Sorry for the misleading statement; I no more think that it is an ACPI
issue.
Although I am still curious about the reason of these bugs happening
together even on different hardware configurations; maybe a side effect
of the same kernel bug? No idea.
Best regards,
--
Daniele C.
> -Len
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
>
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: Laptop keyboard unusable when ACPI is active was Re: [2.6.22] i8042, ACPI, ipw2100 and issues reported by psmouse.c atkbd.c
2007-11-24 4:27 ` Len Brown
@ 2007-11-24 19:14 ` legolas558
0 siblings, 0 replies; 13+ messages in thread
From: legolas558 @ 2007-11-24 19:14 UTC (permalink / raw)
To: linux-kernel; +Cc: Len Brown
Len Brown ha scritto:
> On Sunday 21 October 2007 05:43, legolas558@users.sourceforge.net wrote:
>> have emerged lm_sensors but can't get it running - it keeps saying "No
>> sensors found!" and complaining about kernel drivers not properly setup.
>> I have attached the output of sensors-detect, from which it seems that
>> the kernel is OK.
>>
> In this case, getting sensors installed is the opposite of what you want to do.
> The idea is to simplify the system until it works, then figure out what
> simplification made it work.
>
> ie. disable sensors entirely by building a kernel with CONFIG_HWMON=n
>
> If that makes things work, then it is a clue.
> If that was disabled already, then just keep it disabled.
>
It is disabled since when I abandoned the lm_sensors approach; I
remember that I did some more testing with lm_sensors and got almost all
chips identified, although didn't know how to use lm_sensors to generate
some useful logs.
I agree with you that we have to simplify the system down.
Note: when I built kernel 2.6.24-rc3 to see if it is still affected by
bug #9147, CONFIG_HWMON was enabled instead (and the problem was
verified anyway). I don't recall how that setting got enabled, however I
did not enable it manually and I was not enabling lm_sensors support.
Best regards,
--
Daniele C.
> cheers,
> -Len
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
>
^ permalink raw reply [flat|nested] 13+ messages in thread
end of thread, other threads:[~2007-11-24 19:11 UTC | newest]
Thread overview: 13+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2007-09-30 21:42 [2.6.22] i8042, ACPI, ipw2100 and issues reported by psmouse.c atkbd.c legolas558
2007-10-11 8:04 ` Laptop keyboard unusable when ACPI is active was " legolas558
2007-10-12 11:52 ` Laptop keyboard unusable when ACPI is active legolas558
2007-11-22 7:24 ` legolas558
2007-11-24 4:21 ` Len Brown
2007-11-24 19:08 ` legolas558
2007-10-18 19:52 ` Laptop keyboard unusable when ACPI is active was Re: [2.6.22] i8042, ACPI, ipw2100 and issues reported by psmouse.c atkbd.c Pavel Machek
2007-10-20 11:47 ` legolas558
2007-10-20 18:33 ` Pavel Machek
2007-10-21 9:43 ` legolas558
2007-11-24 4:27 ` Len Brown
2007-11-24 19:14 ` legolas558
2007-10-21 11:07 ` legolas558
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).