Hi John,
ksymoops says something about atkbd_event(), and i had some printk
inside it but does not show up on terminal, or just the oops clear it
all. dont know how to debug this.
Without the atkbd driver no other driver claims the keypad, need to
fix it to get the keypad working.
I had a printk after the first instruction on atkbd_event() and
ksymoops does not show it was executed (i think...), perhaps is a
NULL pointer? dev is null or invalid address?
Anyway, if you have already fixed this i can wait if not, just in
case below is the print.
Thank you
r0: c000dfd2 r1: 0000001c r2: 0000001c r3: 00000001
r4: 00000000 r5: 00000006 r6: 000000ff r7: c074d040
r8: 00000010 r9: 00000000 r10: 0000001c r11: 00000001
r12: 00000000 r13: 00000000 oR10: 0000001c sp: c01a9d88
Warning (Oops_set_i370_regs): garbage 'oR10: 0000001c sp: c01a9d88'
at end of i370 register line ignored
Process swapper (pid: 0, stackpage=c018ce98)
Stack from c01a9c94:
c000624c c01a9d88 c0004850 c0005fa8 c01a9d88 00000120 c01a9d88
c018ce98
c016420c 00000000 c01a9d88 c000496a 00000000 00001001 00000000
c0005772
000000ff 00000006 00000000 00000020 c0842000 00001001 00000000
c01bc04b
Call Trace: [<c000624c>] [<c0004850>] [<c0005fa8>] [<c000496a>]
[<c0005772>] [<c000a04e>] [<c000e412>]
[<c000df0c>] [<c0009a6a>] [<c000dfd2>] [<c0005d88>]
[<c000dfd2>] [<c00b46cc>] [<c00b4428>] [<c000dfd2>]
[<c00b46cc>] [<c0105288>] [<c00fbb4e>] [<c00f82c6>]
[<c00f84fa>] [<c00f85a8>] [<c00f8632>] [<c00e6458>]
[<c00f1dca>] [<c00f4b6e>] [<c00265ac>] [<c0026684>]
[<c0004ac6>] [<c0006a3a>] [<c0004788>] [<c0107260>]
[<c0004788>] [<c0004788>]
Code: 60 80 19 c0 64 4a 5f 4d b1 00 62 2a (0e) 30 6d 66 5f 2d 72 09
6d 9e 04 20
Using defaults from ksymoops -t elf32-i386 -a i386
>>r0 ; c000dfd2 <printk+0/26>
>>r7 ; c074d040 <_end+4f08a0/da3860>
Trace; c000624c <raw_printk+0/74>
Trace; c0004850 <show_stack+0/9c>
Trace; c0005fa8 <show_registers+d4/150>
Trace; c000496a <die_if_kernel+34/46>
Trace; c0005772 <do_page_fault+1f6/2bc>
Trace; c000a04e <try_to_wake_up+ca/d4>
Trace; c000e412 <release_console_sem+ba/ea>
Trace; c000df0c <emit_log_char+0/5e>
Trace; c0009a6a <handle_mmu_bus_fault+4a/a4>
Trace; c000dfd2 <printk+0/26>
Trace; c0005d88 <mmu_bus_fault+92/9a>
Trace; c000dfd2 <printk+0/26>
Trace; c00b46cc <kbd_event+44/80>
Trace; c00b4428 <kbd_keycode+24/284>
Trace; c000dfd2 <printk+0/26>
Trace; c00b46cc <kbd_event+44/80>
Trace; c0105288 <input_event+3e8/3fe>
Trace; c00fbb4e <hidinput_hid_event+202/22a>
Trace; c00f82c6 <hid_process_event+1e/22>
Trace; c00f84fa <hid_input_field+230/264>
Trace; c00f85a8 <hid_input_report+7a/a6>
Trace; c00f8632 <hid_irq_in+5e/c0>
Trace; c00e6458 <usb_hcd_giveback_urb+8e/c4>
Trace; c00f1dca <tc_finish_urb+2d0/2e6>
Trace; c00f4b6e <tc_dma_rx_interrupt+40a/460>
Trace; c00265ac <handle_IRQ_event+26/4c>
Trace; c0026684 <__do_IRQ+b2/112>
Trace; c0004ac6 <do_IRQ+50/5a>
Trace; c0006a3a <IRQ25_interrupt+36/4c>
Trace; c0004788 <cpu_idle+2c/4a>
Trace; c0107260 <atkbd_event+6c/88>
Trace; c0004788 <cpu_idle+2c/4a>
Trace; c0004788 <cpu_idle+2c/4a>
Code; fffffff4 <END_OF_CODE+3efffff4/????>
00000000 <_EIP>:
Code; fffffff4 <END_OF_CODE+3efffff4/????>
0: 60 pusha
Code; fffffff5 <END_OF_CODE+3efffff5/????>
1: 80 19 c0 sbbb $0xc0,(%ecx)
Code; fffffff8 <END_OF_CODE+3efffff8/????>
4: 64 fs
Code; fffffff9 <END_OF_CODE+3efffff9/????>
5: 4a dec %edx
Code; fffffffa <END_OF_CODE+3efffffa/????>
6: 5f pop %edi
Code; fffffffb <END_OF_CODE+3efffffb/????>
7: 4d dec %ebp
Code; fffffffc <END_OF_CODE+3efffffc/????>
8: b1 00 mov $0x0,%cl
Code; fffffffe <END_OF_CODE+3efffffe/????>
a: 62 2a bound %ebp,(%edx)
Code; 00000000 Before first symbol
c: 0e push %cs
Code; 00000001 Before first symbol
d: 30 6d 66 xor %ch,0x66(%ebp)
Code; 00000004 Before first symbol
10: 5f pop %edi
Code; 00000005 Before first symbol
11: 2d 72 09 6d 9e sub $0x9e6d0972,%eax
Code; 0000000a Before first symbol
16: 04 20 add $0x20,%al
<0>Kernel panic - not syncing: Aiee, killing interrupt handler!
1 warning and 1 error issued. Results may not be reliable.
--- In [email protected], "blogic79" <[EMAIL PROTECTED]> wrote:
>
> --- In [email protected], "xfingerfox32" <xfinger@> wrote:
> >
> > Are you sure ksymoops is available on foxboard?
> > Does not seem logic to run it from another architecture.
> you run it on a ix86 host, just need to point it to the corrert
> system.map of the axis kernel
>
>
>
> Ok, the problem is the ATKB controller... it is initialised by
default
> i had the same problem with the keyboard when using it for fox-vhdl
> i fixed it in the phrozen_patch and can check up later, where the
> problem was and let you know. dont out of my head just now. might be
> this file, that i changed ->
>
http://dev.acmesystems.it:8080/trac/browser/trunk/phrozen_patch/code/o
s/linux-2.6-tag--devboard-R2_01-1/drivers/input/keyboard
> where i commented out lines 18-21. that should disable the superio
> support.
>
> John
>
