On Tue, Aug 30, 2011 at 10:18 PM, Matthew Dillon (via DragonFly issue
tracker) <bugs@crater.dragonflybsd.org> wrote:
>
> Matthew Dillon <dillon@apollo.backplane.com> added the comment:
>
> It looks like the USB driver is having trouble with the keyboard,
> ꀠ漤ossibly an indication that the USB interrupt is not working.
>
I am using a PS2 keyboard now but has the same effect though in a
reduced intensity.
There are no messages in /var/log/messages how ever when I use the PS2 keyboard.
> ꀠ糍ry plugging the USB keyboard into a different USB port.
>
> ꀠꀭ-
>
Changing ports does not work :-(
> ꀠ啱f that doesn't help, then emergency interrupt polling can be enabled
> ꀠ乸nd you can try bumping the frequency up as a workaround.
>
> ꀠ澵ysctl kern.emergency_intr_enable=1
> ꀠ澵ysctl kern.emergency_intr_freq=50
>
I tried all these combinations and did not help :-(
blk-build# sysctl kern.emergency_intr_enable=1
kern.emergency_intr_enable: 0 -> 1
blk-build# sysctl kern.emergency_intr_freq=50
kern.emergency_intr_freq: 10 -> 50
blk-build# sysctl kern.emergency_intr_freq=100
kern.emergency_intr_freq: 50 -> 100
blk-build# sysctl kern.emergency_intr_freq=1000
kern.emergency_intr_freq: 100 -> 1000
blk-build# sysctl kern.emergency_intr_freq=5
kern.emergency_intr_freq: 1000 -> 5
Also I note that this problem exists only when I start Xorg before
that the system is just fine.
But once Xorg is started using 'startx' this problem surfaces and
persists in the console too even afterwards it is killed.
Only reboot solves the problem.
Thanks
--Siju