Kernel panic on 10v when down arrow pressed or held in web browser

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Use the netbook in os x as your daily web browser.
2. Not sure of the browser matters, but I think I've reproduced it in Firefox 
and Chrome.
3. Use the down arrow key to scroll down web pages. Try both pressing and 
holding the down arrow.

Usually this panic happens to me about once a day, but I've had it happen twice 
in an hour too.

What netbook are you using this on?
Dell Inspiron Mini 10v, 1gb ram, bluetooth: not sure. Triple boot setup: xp, 
osx 10.6.4, ubuntu unr lucid.

What is the expected output? What do you see instead?

No kernel panic expected. Panic dump below.

What version of the product are you using? On what operating system?

I'm using the unofficial 0.8.4rc1 patched version from the mydellmini.com 
official thread on 10.6.4 updating (post #67). I'm 99% sure I had this panic 
happen with the official 0.8.4rc1 also. OS X Snow Leopard 10.6.4

Panic dump (may be a typo here; I have photos):
panic(cpu 0 caller 0x2269f0): "thread_invoke: preemption_level -1, possible 
cause: unlocking an unlocked mutex or 
spinlock"@/SourceCache/xnu/xnu-1504.7/osfmk/kern/sched_prim.c:1476
Debugger called: <panic>
Backtrace (CPU 0), Frame : Return Address (4 potential args on stack)
0x3376be18 : 0x21b455 (0x5cf328 0x3376be4c 0x2238b1 0x0)
0x3376be68 : 0x2269f0 (0x58712c 0xffffffff 0x5870c4 0x2262b4)
0x3376bee8 : 0x2270f6 (0x54cb7c4 0x0 0x3fc4f00 0x1)
0x3376bf58 : 0x227161 (0x22fa9b 0x863ea0 0x0 0x2a1591)
0x3376bf78 : 0x22fc35 (0x22fa9b 0x863ea0 0x0 0x0)
0x3376bfc8 : 0x29e6cc (0x863ea0 0x0 0x4 0x38254c8)

BSD process name corresponding to current thread: kernel_task

Mac OS version:
10F569

Kernel Version:
Darwin Kernel Version 10.4.0: Fri Apr 23 1828:53 PDT 2010; 
root:xnu-1504.7.4~1/RELEASE_I386
System model name: Inspiron 1011

System uptime in nanoseconds: 24258257451580

Original issue reported on code.google.com by car...@gmail.com on 1 Jul 2010 at 8:39

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Unfortunately I have never run into this issue myself, however I am planing on 
rewriting the ps2 drivers + cleaning them up quite a bit. I'd expect that to 
help  fix the prob.

Original comment by Meklort@gmail.com on 24 Nov 2010 at 11:04