On Sun, 1 Jan 2012, Radoslaw Kujawa wrote:
On 1 sty 2012, at 20:44, Iain Hibbert wrote:
On Sat, 31 Dec 2011, Radoslaw Kujawa wrote:
Module Name: src
Committed By: rkujawa
Date: Sat Dec 31 01:16:09 UTC 2011
Modified Files:
src/sys/dev/bluetooth:
Module Name: src
Committed By:rkujawa
Date:Sat Dec 31 01:16:09 UTC 2011
Modified Files:
src/sys/dev/bluetooth: bthidev.c btkbd.c
Log Message:
Fix panic triggered by pressing the caps lock key:
http://c0ff33.net/drop/bt_caps_panic.jpg
this
On Mon, 2 Jan 2012, Iain Hibbert wrote:
Also, what kernel options do you have? I am using i386 and have always
used DIAGNOSTIC (built in now) and I have run with LOCKDEBUG in the past
though am not at the moment
booting a LOCKDEBUG kernel shows the same problem here btw
iain
On Mon, 2 Jan 2012, matthew green wrote:
Just dropping the lock and reaquiring it around the sc_input/sc_feature
call is probably not exactly the right thing to do though (as the stack
will not be aware that that might have happened and data structures could
have changed), it really
Hi.
On 2 sty 2012, at 11:00, Iain Hibbert wrote:
On Sun, 1 Jan 2012, Radoslaw Kujawa wrote:
I can easily reproduce this problem with Apple Wireless Keyboard
(version without numeric keypad) on NetBSD/amd64 HEAD. If this patch is
not applied, pressing caps lock always results in panic, as
On Mon, Dec 05, 2011 at 12:29:25AM +, Mindaugas Rasiukevicius wrote:
Chuck Silvers c...@netbsd.org wrote:
Module Name:src
Committed By: chs
Date: Sun Dec 4 16:24:13 UTC 2011
Modified Files:
src/sys/arch/amd64/amd64: locore.S machdep.c