NetBSD Problem Report #25208

Received: (qmail 28550 invoked by uid 605); 17 Apr 2004 11:54:41 -0000
Message-Id: <20040417115405.937EE19B01@dmath5.geometrie.tuwien.ac.at>
Date: Sat, 17 Apr 2004 13:54:05 +0200 (CEST)
From: wiz@NetBSD.org
Sender: gnats-bugs-owner@NetBSD.org
Reply-To: wiz@NetBSD.org
To: gnats-bugs@gnats.netbsd.org
Subject: pckbc0: unable to establish interrupt for aux slot
X-Send-Pr-Version: 3.95

>Number:         25208
>Category:       kern
>Synopsis:       pckbc0: unable to establish interrupt for aux slot
>Confidential:   no
>Severity:       critical
>Priority:       medium
>Responsible:    joerg
>State:          analyzed
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sat Apr 17 11:55:00 +0000 2004
>Closed-Date:    
>Last-Modified:  Sun Jun 22 11:10:02 +0000 2008
>Originator:     Thomas Klausner
>Release:        NetBSD 2.0C/2004-04-15
>Organization:

>Environment:


Architecture: i386
Machine: i386
>Description:
After a motherboard change, whenever I start X, the keyboard stops
working with:
pckbport: command timeout
pms_disable: command error

In the dmesg, I also see:
pckbc0: unable to establish interrupt for aux slot
Don't know if this is related.

For testing, I booted an 1.6ZE kernel I had lying around, from 20031104;
starting X with that does _not_ make the keyboard hang.

The differences in dmesg are:
ACPI version (20031029 vs 20040211)
Error messages come from a different device, and
there's one more with 2.0C:
1.6ZE:
pckbc: command timeout
pms_enable: command error 35
pckbc: command timeout
pckbc: command timeout
pms_disable: command error
pckbc: command timeout
pms_enable: command error 35
2.0C:
pckbport: command timeout
pms_enable: command error 35
pckbport: command timeout
pckbport: command timeout
pms_disable: command error
pckbport: command timeout
pms_enable: command error 35
pckbport: command timeout
pms_disable: command error

(now closed) PR 22457 makes me consider it might be an ACPI problem.
The changed error messages indicate that it might be a pckbport
problem.

>How-To-Repeat:
Boot. Start X.

dmesg extract:

NetBSD 2.0C (HIRO) #0: Sun Apr 18 13:17:47 CEST 2004
	wiz@hiro:/usr/src/sys/arch/i386/compile/HIRO
total memory = 511 MB
avail memory = 496 MB
BIOS32 rev. 0 found at 0xf1940
mainbus0 (root)
cpu0 at mainbus0: (uniprocessor)
cpu0: AMD Athlon XP 2400+ (686-class), 1990.32 MHz, id 0x6a0
cpu0: features c3c3fbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR>
cpu0: features c3c3fbff<PGE,MCA,CMOV,PAT,PSE36,MMXX,MMX>
cpu0: features c3c3fbff<FXSR,SSE,3DNOW2,3DNOW>
cpu0: I-cache 64 KB 64b/line 2-way, D-cache 64 KB 64b/line 2-way
cpu0: L2 cache 256 KB 64b/line 16-way
cpu0: ITLB 16 4 KB entries fully associative, 8 4 MB entries fully associative
cpu0: DTLB 32 4 KB entries fully associative, 8 4 MB entries 4-way
cpu0: 8 page colors
acpi0 at mainbus0
acpi0: using Intel ACPI CA subsystem version 20040211
acpi0: X/RSDT: OemId <ASUS  ,A7V600-X,42302e31>, AslId <MSFT,31313031>
acpi0: SCI interrupting at int 9
acpi0: fixed-feature power button present
ACPI Object Type 'Processor' (0x0c) at acpi0 not configured
acpibut0 at acpi0 (PNP0C0C): ACPI Power Button
PNP0C01 [System Board] at acpi0 not configured
PNP0C0F [PCI interrupt link device] at acpi0 not configured
PNP0C0F [PCI interrupt link device] at acpi0 not configured
PNP0C0F [PCI interrupt link device] at acpi0 not configured
PNP0C0F [PCI interrupt link device] at acpi0 not configured
PNP0C0F [PCI interrupt link device] at acpi0 not configured
PNP0A03 [PCI Bus] at acpi0 not configured
PNP0C02 [Plug and Play motherboard register resources] at acpi0 not configured
PNP0C02 [Plug and Play motherboard register resources] at acpi0 not configured
PNP0000 [AT Interrupt Controller] at acpi0 not configured
PNP0200 [AT DMA Controller] at acpi0 not configured
PNP0100 [AT Timer] at acpi0 not configured
PNP0B00 [AT Real-Time Clock] at acpi0 not configured
PNP0800 [AT-style speaker sound] at acpi0 not configured
npx0 at acpi0 (PNP0C04)
npx0: io 0xf0-0xff irq 13
npx0: using exception 16
fdc0 at acpi0 (PNP0700)
fdc0: io 0x3f2-0x3f5,0x3f7 irq 6 drq 2
lpt0 at acpi0 (PNP0401)
lpt0: io 0x378-0x37f,0x778-0x77b irq 7 drq 3
com0 at acpi0 (PNP0501-1)
com0: io 0x3f8-0x3ff irq 4
com0: ns16550a, working fifo
pckbc0 at acpi0 (PNP0303): kbd port
pckbc0: io 0x60,0x64 irq 1
PNPB02F [Joystick/Game port] at acpi0 not configured
PNP0C02 [Plug and Play motherboard register resources] at acpi0 not configured
pckbd0 at pckbc0 (kbd slot)
pckbc0: using irq 1 for kbd slot
wskbd0 at pckbd0: console keyboard
pms0 at pckbc0 (aux slot)
pckbc0: unable to establish interrupt for aux slot
wsmouse0 at pms0 mux 0
pci0 at mainbus0 bus 0: configuration mode 1
pci0: i/o space, memory space enabled, rd/line, rd/mult, wr/inv ok
pchb0 at pci0 dev 0 function 0
pchb0: VIA Technologies VT8377 Apollo KT400 CPU to PCI Bridge (rev. 0x80)
agp0 at pchb0: aperture at 0xf8000000, size 0xf100000
ppb0 at pci0 dev 1 function 0: VIA Technologies VT8377CE CPU-AGP Bridge (KT600) (rev. 0x00)
pci1 at ppb0 bus 1
pci1: i/o space, memory space enabled
vga0 at pci1 dev 0 function 0: ATI Technologies Radeon 9700/9500 Series (rev. 0x00)
wsdisplay0 at vga0 kbdmux 1: console (80x25, vt100 emulation), using wskbd0
wsmux1: connecting to wsdisplay0
....
pckbport: command timeout
pms_enable: command error 35
pckbport: command timeout
pckbport: command timeout
pms_disable: command error
pckbport: command timeout
pms_enable: command error 35
pckbport: command timeout
pms_disable: command error
>Fix:
No idea.
>Release-Note:
>Audit-Trail:

From: Martin Husemann <martin@duskware.de>
To: wiz@NetBSD.org
Cc: gnats-bugs@gnats.netbsd.org
Subject: Re: kern/25208: pckbc0: unable to establish interrupt for aux slot
Date: Sat, 17 Apr 2004 14:03:35 +0200

 On Sat, Apr 17, 2004 at 01:54:05PM +0200, wiz@NetBSD.org wrote:
 > pckbc0 at acpi0 (PNP0303): kbd port
 > pckbc0: io 0x60,0x64 irq 1
 > pckbd0 at pckbc0 (kbd slot)
 > pckbc0: using irq 1 for kbd slot
 > wskbd0 at pckbd0: console keyboard
 > pms0 at pckbc0 (aux slot)
 > pckbc0: unable to establish interrupt for aux slot

 This looks like a ACPI problem to me. This is how it looks on my machine:

 pckbc0 at acpi0 (PNP0F13): aux port
 pckbc0: irq 12
 pckbc1 at acpi0 (PNP0303): kbd port
 pckbc1: io 0x60,0x64 irq 1
 pckbd0 at pckbc1 (kbd slot)
 pckbc1: using irq 1 for kbd slot
 wskbd0 at pckbd0: console keyboard
 pms0 at pckbc1 (aux slot)
 pckbc1: using irq 12 for aux slot
 wsmouse0 at pms0 mux 0

 Maybe you have the mouse disabled in the bios setup (or irq 12 assigned 
 otherwise)?

 Martin

From: Thomas Klausner <wiz@NetBSD.org>
To: Martin Husemann <martin@duskware.de>
Cc: gnats-bugs@gnats.netbsd.org
Subject: Re: kern/25208: pckbc0: unable to establish interrupt for aux slot
Date: Sat, 17 Apr 2004 14:05:15 +0200

 On Sat, Apr 17, 2004 at 02:03:35PM +0200, Martin Husemann wrote:
 > On Sat, Apr 17, 2004 at 01:54:05PM +0200, wiz@NetBSD.org wrote:
 > > pckbc0 at acpi0 (PNP0303): kbd port
 > > pckbc0: io 0x60,0x64 irq 1
 > > pckbd0 at pckbc0 (kbd slot)
 > > pckbc0: using irq 1 for kbd slot
 > > wskbd0 at pckbd0: console keyboard
 > > pms0 at pckbc0 (aux slot)
 > > pckbc0: unable to establish interrupt for aux slot
 > 
 > This looks like a ACPI problem to me. This is how it looks on my machine:
 > 
 > pckbc0 at acpi0 (PNP0F13): aux port
 > pckbc0: irq 12
 > pckbc1 at acpi0 (PNP0303): kbd port
 > pckbc1: io 0x60,0x64 irq 1
 > pckbd0 at pckbc1 (kbd slot)
 > pckbc1: using irq 1 for kbd slot
 > wskbd0 at pckbd0: console keyboard
 > pms0 at pckbc1 (aux slot)
 > pckbc1: using irq 12 for aux slot
 > wsmouse0 at pms0 mux 0
 > 
 > Maybe you have the mouse disabled in the bios setup (or irq 12 assigned 
 > otherwise)?

 There is no mouse attached to there; I'm using a USB mouse.
 So does that mean that's not really a problem?
  Thomas

From: Thomas Klausner <wiz@NetBSD.org>
To: gnats-bugs@NetBSD.org
Cc:  
Subject: kern/25208
Date: Sat, 17 Apr 2004 14:19:13 +0200

 I made a new kernel config with
 #pckbc*         at acpi?                # PC keyboard controller
 isa0    at pcib?
 pckbc0          at isa?                 # pc keyboard controller
 pckbd*          at pckbc?               # PC keyboard

 That results in:
 isa0 at pcib0
 pckbc0 at isa0 port 0x60-0x64
 pcppi0 at isa0 port 0x61

 and the keyboard works again under X too.
  Thomas

From: Martin Husemann <martin@duskware.de>
To: gnats-bugs@NetBSD.org
Cc:  
Subject: Re: kern/25208
Date: Sat, 17 Apr 2004 14:58:03 +0200

 Actually the problem is that the pckbc @ acpi attachment eroneously allows
 the pms* @ pckbc? to attach, even if the "aux slot" part of its acpi
 part has not attached.

 Martin
Responsible-Changed-From-To: kern-bug-people->joerg
Responsible-Changed-By: joerg@NetBSD.org
Responsible-Changed-When: Thu, 22 May 2008 20:24:00 +0000
Responsible-Changed-Why:
I'll see this through.


State-Changed-From-To: open->feedback
State-Changed-By: joerg@NetBSD.org
State-Changed-When: Thu, 22 May 2008 20:24:00 +0000
State-Changed-Why:
Does this problem still exist? The interrupt code, the
ACPI kbd attachment and some other areas involved changed
a lot.


From: Thomas Klausner <wiz@NetBSD.org>
To: gnats-bugs@NetBSD.org
Cc: 
Subject: Re: kern/25208 (pckbc0: unable to establish interrupt for aux slot)
Date: Fri, 30 May 2008 14:53:36 +0200

 On Thu, May 22, 2008 at 08:24:00PM +0000, joerg@NetBSD.org wrote:
 > Synopsis: pckbc0: unable to establish interrupt for aux slot
 >
 > Does this problem still exist? The interrupt code, the
 > ACPI kbd attachment and some other areas involved changed
 > a lot.

 When I remove pckbc at isa from my kernel config, leaving:
 pckbc*          at acpi?                # PC keyboard controller
 #pckbc0         at isa?                 # pc keyboard controller
 pckbd*          at pckbc?               # PC keyboard
 pms*            at pckbc?               # PS/2 mouse for wsmouse

 I lose
 -pckbc0 at isa0 port 0x60-0x64
 -pckbd0 at pckbc0 (kbd slot)
 -pckbc0: using irq 1 for kbd slot
 -wskbd0 at pckbd0: console keyboard, using wsdisplay0
 from my dmesg.

 So no, I don't get the error message, but I also don't get pckbc at
 all.
 Is this a different bug? :)
  Thomas

From: Joerg Sonnenberger <joerg@britannica.bec.de>
To: gnats-bugs@NetBSD.org
Cc: 
Subject: Re: kern/25208 (pckbc0: unable to establish interrupt for aux slot)
Date: Sat, 31 May 2008 19:22:46 +0200

 On Fri, May 30, 2008 at 12:55:04PM +0000, Thomas Klausner wrote:
 >  When I remove pckbc at isa from my kernel config, leaving:
 >  pckbc*          at acpi?                # PC keyboard controller
 >  #pckbc0         at isa?                 # pc keyboard controller
 >  pckbd*          at pckbc?               # PC keyboard
 >  pms*            at pckbc?               # PS/2 mouse for wsmouse

 OK, please provide the DSDT so that we can figure if it is just missing
 the entries or using wrong PNP IDs.

 Joerg

State-Changed-From-To: feedback->analyzed
State-Changed-By: wiz@NetBSD.org
State-Changed-When: Sun, 22 Jun 2008 11:07:59 +0000
State-Changed-Why:
Feedback mail will arrive shortly :)


From: Thomas Klausner <wiz@NetBSD.org>
To: gnats-bugs@NetBSD.org
Cc: 
Subject: Re: kern/25208 (pckbc0: unable to establish interrupt for aux slot)
Date: Sun, 22 Jun 2008 13:07:23 +0200

 Some more offline debugging with Joerg led to this analysis:

 With ACPI_EXTRA_DEBUG defined,
 > acpi0: HID PNP0F13 found in scope \_SB_ level 2
 >        STA 0x00000000
 (the AUX-port) and
 > acpi0: HID PNP0303 found in scope \_SB_ level 2
 >        STA 0x00000000
 (the KBD-port) are found.
 When adding ACPI_ACTIVATE_DEV and plugging in a keyboard and mouse
 (!), NetBSD finds the devices:
 pckbc0 at acpi0 (PS2M, PNP0F13): aux port
 pckbc0: irq 12
 pckbc1 at acpi0 (PS2K, PNP0303): kbd port
 pckbc1: io 0x60,0x64 irq 1
 and they even work.

 Cheers,
  Thomas

>Unformatted:

Home	PR Database Search