run ksymoops on it
--- In [email protected], "xfingerfox32" <[EMAIL PROTECTED]> wrote:
>
> Sorry, here is the message:
>
> # IRP: c00b37f2 SRP: c00b3a76 DCCR: 00000484 USP: 00000000 MOF:
> 000000cf
> r0: c04dac80 r1: 00000045 r2: 00000001 r3: 00000001
> r4: 00000000 r5: c048a4dc r6: 00000001 r7: c04da740
> r8: 00000010 r9: 00000000 r10: 00000045 r11: 00000001
> r12: 00000000 r13: 00000000 oR10: 00000045 sp: c01b3d7c
> R_MMU_CAUSE: 00001011
> Process swapper (pid: 0, stackpage=c01946b8)
>
> Stack from c01b3c88:
> c00060ac c01b3d7c c00046b0 c0005e08 c01b3d7c 000000cf c01b3d7c
> c01946b8
> c0167188 00000000 c01b3d7c c00047ca 00000000 00001011 00000000
> c00055d2
> 00000001 c048a4dc 00000000 00000010 c07fe000 00001011 00000000
> 00000000
> Call Trace: [<c00060ac>] [<c00046b0>] [<c0005e08>] [<c00047ca>]
> [<c00055d2>] [<c002b0f0>] [<c00098ca>]
> [<c0005be8>] [<c00b3a76>] [<c00b37f2>] [<c00b3a76>]
> [<c0104e88>] [<c00fda78>] [<c00f7fd4>] [<c00f822e>]
> [<c00f82f0>] [<c00f837a>] [<c00e5b8a>] [<c00f1aca>]
> [<c00f486e>] [<c002630c>] [<c00263e4>] [<c0004926>]
> [<c000689a>] [<c0006934>] [<c00045e8>] [<c010870e>]
> [<c00045e8>] [<c00045e8>]
> Code: 24 f7 19 c0 64 4a 5f 4d b1 00 62 2a (0e) 30 6d 66 5f 2d 72 09
> 6d 9e 04 20
> <0>Kernel panic - not syncing: Aiee, killing interrupt handler!
>
>
>
> --- In [email protected], "xfingerfox32" <xfinger@> wrote:
> >
> > Hi,
> >
> > After configuring the kernel for the mini-keypad any keystroke
> > generates a kernel panic. It seems (from my litle knowledge) that
> > linux axis does not yet handle keyboard. My last hope is to try to
> > force the HID interface to use the usbkbd Handler instead of kbd.
> > Have no idea how to load the usbkbd driver into the kernel, or if
> it
> > is already there, how to force usbkbd driver to claim that
> interface.
> > I have another embedded device (arm920) with kernel 2.4.25 and that
> > handles this keypad as it should, but i dont have the sources and
> the
> > kernel 2.4 is does not look similar when looking at /proc/bus.
> >
> > here is all the information in a hope that somebody could help find
> > where the offending code is?
> >
> > Cheers
> >
> > cat /proc/devices
> > Character devices:
> > 1 mem
> > 2 pty
> > 3 ttyp
> > 4 /dev/vc/0
> > 4 tty
> > 4 ttyS
> > 4 ttyS
> > 5 /dev/tty
> > 5 /dev/console
> > 5 /dev/ptmx
> > 7 vcs
> > 10 misc
> > 13 input
> > 90 mtd
> > 108 ppp
> > 120 etrax gpio
> > 121 ds1302
> > 123 i2c
> > 128 ptm
> > 136 pts
> > 180 usb
> > 188 ttyUSB
> > 189 usb_device
> >
> > Block devices:
> > 1 ramdisk
> > 8 sd
> > 31 mtdblock
> > 65 sd
> > 66 sd
> > 67 sd
> > 68 sd
> > 69 sd
> > 70 sd
> > 71 sd
> > 128 sd
> > 129 sd
> > 130 sd
> > 131 sd
> > 132 sd
> > 133 sd
> > 134 sd
> > 135 sd
> >
> >
> > cat devices
> > I: Bus=0003 Vendor=05a4 Product=9840 Version=0110
> > N: Name="USB Compliant Keypad"
> > P: Phys=usb-hc-crisv10.0-1/input0
> > S: Sysfs=/class/input/input-1
> > H: Handlers=kbd
> > B: EV=120003
> > B: KEY=10000 7 ff87207a c14057ff febeffdf ffefffff ffffffff
> fffffffe
> > B: LED=1f
> >
> > # cat handlers
> > N: Number=0 Name=kbd
> >
> > T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2
> > B: Alloc=118/900 us (13%), #Int= 1, #Iso= 0
> > D: Ver= 1.10 Cls=09(hub ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
> > P: Vendor=0000 ProdID=0000 Rev= 2.06
> > S: Manufacturer=Linux 2.6.15 hc-crisv10
> > S: Product=ETRAX 100LX USB Host Controller
> > S: SerialNumber=hc-crisv10.0
> > C:* #Ifs= 1 Cfg#= 1 Atr=c0 MxPwr= 0mA
> > I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
> > E: Ad=81(I) Atr=03(Int.) MxPS= 2 Ivl=255ms
> >
> > T: Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 2 Spd=1.5 MxCh= 0
> > D: Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
> > P: Vendor=05a4 ProdID=9840 Rev= 1.10
> > S: Product=USB Compliant Keypad
> > C:* #Ifs= 1 Cfg#= 1 Atr=a0 MxPwr= 48mA
> > I: If#= 0 Alt= 0 #EPs= 1 Cls=03(HID ) Sub=01 Prot=01 Driver=usbhid
> > E: Ad=81(I) Atr=03(Int.) MxPS= 8 Ivl=13ms
> >
>
