[prev in list] [next in list] [prev in thread] [next in thread] 

List:       netbsd-current-users
Subject:    Re: pckbport: command timeout
From:       Adam Hoka <adam.hoka () gmail ! com>
Date:       2009-08-27 21:12:08
Message-ID: Pine.NEB.4.64.0908272111180.29105 () mail ! netbsd ! org
[Download RAW message or body]

On Wed, 26 Aug 2009, David Young wrote:

> Date: Wed, 26 Aug 2009 18:13:14 -0500
> From: David Young <dyoung@pobox.com>
> Reply-To: current-users@netbsd.org
> To: current-users@netbsd.org
> Subject: pckbport: command timeout
> 
> Maybe somebody recognizes this problem with pckbport in -current, and
> knows what the cause is?
>
> On my workstation, I have a USB keyboard, a USB mouse, and a PC keyboard
> attached.  Starting X makes the system hang a few times, each time for a
> few seconds.  The kernel logs this:
>
> Aug 26 11:56:19 elmendorf /netbsd: pckbport: command timeout
> Aug 26 11:56:19 elmendorf /netbsd: pms_enable: command error 35
> Aug 26 11:56:31 elmendorf /netbsd: pckbport: command timeout
> Aug 26 11:56:31 elmendorf /netbsd: pms_disable: command error
>
> Thanks to a tip from Jared McNeill, I found that tapping Num Lock lets
> the system run for a little while before it hangs again.  Once X has
> started, the hangs stop.  Quitting X causes the system to hang, and
> to log pckbport errors, at least once more before things are back to
> normal.
>
> Dave
>
> -- 
> David Young             OJC Technologies
> dyoung@ojctech.com      Urbana, IL * (217) 278-3933
>


Hmm I saw that too. I had a bogus (as in nonexistent) wsmouse0 at pms0
attached during boot and it obviously failed every attempt to
enable or disable. I thought its a hardware issue, but now it seems its
some kind of kernel bug?

-- 
Adam Hoka <Adam.Hoka@Gmail.com>
Adam Hoka <ahoka@NetBSD.org>
Adam Hoka <ahoka@MirBSD.de>

[prev in list] [next in list] [prev in thread] [next in thread]