From owner-freebsd-mobile@FreeBSD.ORG Thu Dec 18 06:56:49 2003 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A0C2F16A4CE for ; Thu, 18 Dec 2003 06:56:49 -0800 (PST) Received: from mailhost.nmc.kpn.net (mailhost.nmc.kpn.net [194.151.95.5]) by mx1.FreeBSD.org (Postfix) with SMTP id 1737243D48 for ; Thu, 18 Dec 2003 06:56:46 -0800 (PST) (envelope-from HeinH@nmc.kpn.net) Received: (qmail 24333 invoked from network); 18 Dec 2003 14:56:44 -0000 Received: from (HELO NMCRD01V3.nmcrd.nmcgv) (@) by mailhost.nmc.kpn.net with SMTP; 18 Dec 2003 14:56:44 -0000 Received: by NMCRD01V3.nmcrd.nmcgv with Internet Mail Service (5.5.2653.19) id ; Thu, 18 Dec 2003 15:56:44 +0100 Message-ID: <8EB4F34946036E499CAE93F5DF40DE870421C49D@NMCRD01V3.nmcrd.nmcgv> From: "Hermans, Hein" To: "'freebsd-mobile@freebsd.org'" Date: Thu, 18 Dec 2003 15:56:43 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Subject: Slow keyboard response, IRQ routing problems ? X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Dec 2003 14:56:49 -0000 Some while ago, I posted the below message... >Hi there, > >Last week I installed FreeBSD 4.5 (though I noticed the same problem on 4.3 and 5.1) on a Presario 1230 laptop. > >During installation and afterwards I noticed a slow keyboard response on the console. Scrolling of >long output (cat big_file.txt) works perfect or comparable to a Linux installation. Only when >typing (no system load) I notice a minimal time lap >between pressing the key and the showing up >of the character on the screen. The effect is the same as when remotely logged into a slow machine >or via a slow / busy connection. > >Unfortunately the problem isn't related to the key repeat rate (thanks anyway Nathan) so a > >$ kbdcontrol -r normal/fast/slow > >doesn't fix the problem Since then I have made some progress; - Installed version 5.1 again - I noticed in the kernel logging, that the PCCARD was using IRQ1 (???) ---dmesg-snip--- Using $PIR table, 5 entries at 0xc00fdf70 pcib0: at pcibus 0 on motherboard pci0: on pcib0 cbb0: at device 17.0 on pci0 cardbus0: on cbb0 pccard0: <16-bit PCCard bus> on cbb0 pci_cfgintr: 0:17 INTA routed to irq 1 cbb1: at device 17.1 on pci0 cardbus1: on cbb1 pccard1: <16-bit PCCard bus> on cbb1 pci_cfgintr: 0:17 INTA routed to irq 1 ---snip--- atkbdc0: at port 0x64,0x60 on isa0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 ---snip--- - Recompiled the kernel without any pccard support This solved most of my problems; the keyboard was functioning as normal now, but I don't have any functioning pccard anymore. As soon as I insert the driver (as a module now) the driver gets IRQ1 assigned :( --- cbb0: at device 17.0 on pci0 pci_cfgintr: 0:17 INTA routed to irq 1 cbb1: at device 17.1 on pci0 pci_cfgintr: 0:17 INTA routed to irq --- My question now is, how is it possible that the driver (cbb) gets (via the pci-bus) a reserved IRQ1 assigned, which is allready (rightfully) in use by the keyboard driver. I have taken a look in /dev/pccbb.c and accompanying files... but allas I'm not a programer... Kind regards (and sory for such a long post), Hein Hermans p.s. below, some more loging ===================== pciconf -lv hostb0@pci0:0:0: class=0x060000 card=0x00000000 chip=0x00011078 rev=0x00 hdr=0x00 vendor = 'Cyrix Corp (Now owned by VIA)' device = 'MediaGXm MMX Cyrix Integrated CPU' class = bridge subclass = HOST-PCI none0@pci0:17:0: class=0x060700 card=0xac190e11 chip=0xac19104c rev=0x00 hdr=0x02 vendor = 'Texas Instruments (TI)' device = 'PCI1221 PC card CardBus Controller' class = bridge subclass = PCI-CardBus none1@pci0:17:1: class=0x060700 card=0xac190e11 chip=0xac19104c rev=0x00 hdr=0x02 vendor = 'Texas Instruments (TI)' device = 'PCI1221 PC card CardBus Controller' class = bridge subclass = PCI-CardBus isab0@pci0:18:0: class=0x060100 card=0x00000000 chip=0x00021078 rev=0x00 hdr=0x00 vendor = 'Cyrix Corp (Now owned by VIA)' device = 'Cx5520 ISA Bridge Rev.1' class = bridge subclass = PCI-ISA ohci0@pci0:19:0: class=0x0c0310 card=0xa0f80e11 chip=0xa0f80e11 rev=0x04 hdr=0x00 vendor = 'Compaq Computer Corp (Now owned by Hewlett-Packard)' device = 'ZFMicro USB Open Host Controller' class = serial bus subclass = USB none2@pci0:20:0: class=0x030000 card=0xb0be0e11 chip=0x008310c8 rev=0x01 hdr=0x00 vendor = 'Neomagic Corporation' device = 'NM2097 Graphic Controller NeoMagic MagicGraph128ZV+' class = display subclass = VGA ######################################## Copyright (c) 1992-2003 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.1-RELEASE #1: Sun Dec 14 05:24:21 CET 2003 root@:/usr/src/sys/i386/compile/DEMON Preloaded elf kernel "/boot/kernel/kernel" at 0xc03e7000. Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 28419972 Hz CPU: Cyrix GXm (28.42-MHz 586-class CPU) Origin = "CyrixInstead" Id = 0x540 DIR=0x3346 Stepping=3 Revision=3 real memory = 33554432 (32 MB) avail memory = 28483584 (27 MB) VESA: v2.0, 1024k memory, flags:0x0, mode table:0xc037e182 (1000022) VESA: MagicGraph 128 V/ZV+ 32K VGA BIOS npx0: on motherboard npx0: INT 16 interface pcibios: BIOS version 2.10 Using $PIR table, 5 entries at 0xc00fdf70 pcib0: at pcibus 0 on motherboard pci0: on pcib0 pci0: at device 17.0 (no driver attached) pci0: at device 17.1 (no driver attached) isab0: port 0x5000-0x500f,0x4000-0x401f,0x3000-0x307f mem 0x40010000-0x40010fff at device 18.0 on pci0 isa0: on isab0 ohci0: mem 0xfedfe000-0xfedfefff irq 9 at device 19.0 on pci0 usb0: OHCI version 1.0, legacy support usb0: on ohci0 usb0: USB revision 1.0 uhub0: (0x0e11) OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhub0: device problem, disabling port 1 pci0: at device 20.0 (no driver attached) orm0: