I am having the same problem described here and have a bit of information to
add... I also am using a SuperMicro motherboard (mine is the dual-processor
P6DLF) with a single P2-266 processor. I have tried building with SMP both
in and out, and this does not make a difference.
The "controller jammed (0xFF)." message from pc_keyb.c started showing up in
2.3.30 (2.3.29 worked fine), but pc_keyb.c wasn't patched significantly
until 2.3.33. This however, is insignificant, because the patches in that
file have no effect on this condition.
My current guess is that it has something to do with the keyboard spinlock,
IRQ handling, or semaphore changes that occurred in 2.3.30. I'll report
anything new that I come up with, but we could certainly use some help on
this one. It must have something to do with this family of motherboards,
but I assumed that PC I/O and IRQ handling from one PC motherboard to the
next would be fairly consistent!
Bill
>
> Hi!
>
> I have been unable to boot kernels since 2.3.33, I always get
> about 1000 "pc_keyb: controller jammed (0xFF)." messages
> and then a
> NMI Watchdog detected LOCKUP on CPU0, registers:
> (see below)
> console shuts up ...
>
> And now nothing much happens, I had a working 2.3.25 kernel but did not
> try all the kernels in between so I dont know if this is the exact
> place for the introduction of this behavior. But I do have a suspect:
> http://www.kernelnotes.org/v23patch/patch-2.3.33/linux_drivers_cha
> r_pc_keyb.
> c.html
>
> I have not seen any references to this problem so I decided to try my
> luck here. I must admitt that I have not done any kernel hacking yet
> but I believe that this problem might affect others, so it should get
> reported.
>
> I downgraded my gcc to 2.7.2.3 and tried different kernels, with no
> succcess. I even tried two keyboards. And the last thing was to
> download a fresh copy of the kernel.
>
>
> My machine is a dual Pentium II 266 Mhz Supermicro 6DSL MB
> cat /proc/cpuinfo
> processor : 0
> vendor_id : GenuineIntel
> cpu family : 6
> model : 3
> model name : Pentium II (Klamath)
> stepping : 4
> cpu MHz : 265.544670
> cache size : 512 KB
> fdiv_bug : no
> hlt_bug : no
> sep_bug : no
> f00f_bug : no
> coma_bug : no
> fpu : yes
> fpu_exception : yes
> cpuid level : 2
> wp : yes
> flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca
> cmov mmx
> bogomips : 264.60
>
> processor : 1
> vendor_id : GenuineIntel
> cpu family : 6
> model : 3
> model name : Pentium II (Klamath)
> stepping : 3
> cpu MHz : 265.544670
> cache size : 512 KB
> fdiv_bug : no
> hlt_bug : no
> sep_bug : no
> f00f_bug : no
> coma_bug : no
> fpu : yes
> fpu_exception : yes
> cpuid level : 2
> wp : yes
> flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca
> cmov mmx
> bogomips : 265.42
>
>
>
> here is a ksymoops
> ksymoops 2.3.3 on i686 2.3.25. Options used
> -v /usr/src/linux/vmlinux (specified)
> -K (specified)
> -L (specified)
> -o /lib/modules/2.3.25/ (default)
> -m /usr/src/linux/System.map (default)
>
> No modules in ksyms, skipping objects
> Reading Oops report from the terminal
> NMI Watchdog detected LOCKUP on CPU0, registers:
> EIP: 0010:[<c01f5855>]
> Using defaults from ksymoops -t elf32-i386 -a i386
> EFLAGS: 00000086
> eax: ffffffff ebx: 000000ff ecx: 000204ff edx: 000204af
> esi: 00000d21 edi: 00000000 ebp: 00001000 esp: c1575f80
> ds: 0018 es: 0018 ss: 0018
> Process swapper (pid: 1, stackpage=c1575000)
> Stack: c01f5567 c01f5559 0000000a c02ce99b c02ecd80 c035ed08 c035ef3c
> c02cea36
> c035ef3c c02ce91a c02ce27c c02ecd80 c02ce57e c02c1fc8 c0105000
> c02ce5c6
> c02cbd7d c02ca05b c02ecd80 c02c1fc8 c02c2b10 00000f00 c02c2b4a
> c01070f6
> Call Trace: [<c01f5567>] [<c01f5559>] [<c0105000>] [<c01070f6>]
> [<c010b5cf>]
> Code: 88 c3 4e 0f 85 0c ff ff ff 0f b6 c3 50 68 27 d3 27 c0 e8 28
>
> >>EIP; c01f5855 <handle_kbd_event+f9/11c> <=====
> Trace; c01f5567 <kb_wait+1b/30>
> Trace; c01f5559 <kb_wait+d/30>
> Trace; c0105000 <empty_bad_page+0/1000>
> Trace; c01070f6 <init+66/21c>
> Trace; c010b5cf <kernel_thread+23/30>
> Code; c01f5855 <handle_kbd_event+f9/11c>
> 00000000 <_EIP>:
> Code; c01f5855 <handle_kbd_event+f9/11c> <=====
> 0: 88 c3 mov %al,%bl <=====
> Code; c01f5857 <handle_kbd_event+fb/11c>
> 2: 4e dec %esi
> Code; c01f5858 <handle_kbd_event+fc/11c>
> 3: 0f 85 0c ff ff ff jne ffffff15
> <_EIP+0xffffff15> c01f576a
> <ha
> ndle_kbd_event+e/11c>
> Code; c01f585e <handle_kbd_event+102/11c>
> 9: 0f b6 c3 movzbl %bl,%eax
> Code; c01f5861 <handle_kbd_event+105/11c>
> c: 50 push %eax
> Code; c01f5862 <handle_kbd_event+106/11c>
> d: 68 27 d3 27 c0 push $0xc027d327
> Code; c01f5867 <handle_kbd_event+10b/11c>
> 12: e8 28 00 00 00 call 3f <_EIP+0x3f> c01f5894
> <keyboard_inter
> rupt+1c/a4>
>
>
> Regards
> Yngvi
> --
> First they ignore you. Then they laugh at you. Then they fight you.
> Then you win. --Gandhi
>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sun Jan 23 2000 - 21:00:15 EST