Success stories, disappearing Oopses and ps/2 keyboard
Hi there!
Well, that masterpeiece of Software, the 2.5.7x series is now running on all computers I got my hands on (all i386 and physically accessable, the others will be treated later) :)
I must say, it runs great, especially on servers that thing does not crash more often than 2.4.x. Well indeed I saw an Oops on my Server with 2.4.x which I did not debug, I put 2.5.72-mm2 onto it :)
These Kernels (2.5.7x-mmx) did not give an Oops too me and died if running (lvm1 -> lvm2 and such things). Simultaniously switching to devfs was no Problem...
I got some freezes with 2.5.70-mm9 and 2.5.71-mmx which seem to have disappeared, lets see...
However, there is only one Problem left for me, before this one can be called 2.6.0: The keys on my PS/2 IBM Keyboard are bouncing very often! I switched from an USB Logitech Keyboard back to my old school, clicking PC-102 IBM Keyboard ATM and the Key bouncing was back immmediatly :(
Over ssh connections it is even more extreme, I don't know why.
Are there any approaches to debug or whatsoever that thing? I saw many changes to the input layer on this mailing list since 2.5.70 so I gave this one Kernel here another chance :) (see signature). I just wanted to say, the Problem hasn't gone yet, not more, and keep on hacking this great mastepiece of Kernel :-)
Regards, Konsti
Signature · 5 lines
2.5.73-mm1 Konstantin Kletschke <[email protected]>, <[email protected]> GPG KeyID EF62FCEF Fingerprint: 13C9 B16B 9844 EC15 CC2E A080 1E69 3FDA EF62 FCEF keulator.homelinux.org up 1:38, 18 users
medium Oops on 2.5.73-mm1
This evening 2.5.73-mm1 "crashed" two times. The " because of that: this time it did not freeze completely, it disabled keyboard and mouse buttons, mouse movements where working still! I was running X...
I enabled debugging in kernel, do you need the raw output or the ksymoopsed one?
last lines raw:
agetty S E9DC2000 5027 1 4994 (NOTLB)ea767e1c 00000082 00000082 e9dc2000 ea767e34 c0339260 00000246 c0339260
c03db160 eaa23000 c03db160 00000001 00000008 7fffffff 00000000
eb175974
c0130393 c03db160 00000292 eb175000 7fffffff 00100100 00200200
00000246
Call Trace:
[<c0130393>] schedule_timeout+0xe5/0xe7
[<c024847a>] uart_write+0x18a/0x4be
[<c02361d8>] read_chan+0x2d8/0x100e
[<c0237094>] write_chan+0x186/0x272
[<c011ecd7>] default_wake_function+0x0/0x2e
[<c011ecd7>] default_wake_function+0x0/0x2e
[<c0235f00>] read_chan+0x0/0x100e
[<c022f4e3>] tty_read+0x24b/0x2ce
[<c012ac52>] tasklet_action+0x40/0x61
[<c0171c26>] vfs_read+0xbc/0x127
[<c0171edd>] sys_read+0x42/0x63
[<c010a067>] syscall_call+0x7/0xbfull at http://www.ludenkalle.de/capture.log.2003-06-24
and ksymoopsed:
Quoted 1 line
Quoted 1 line
EIP;
e5cf1e6c<_end+25909b9c/3fc15d30> <=====
Trace; c0130341 <schedule_timeout+93/e7>
Trace; c01302a5 <process_timeout+0/9>
Trace; c018d5b4 <do_select+29e/474>
Trace; c018d171 <__pollwait+0/c4>
Trace; c018dab0 <sys_select+301/53d>
Trace; c0137455 <sys_rt_sigaction+a1/115>
Trace; c010a067 <syscall_call+7/b>
Proc; agetty
Quoted 1 line
Quoted 1 line
EIP;
e9dc2000<_end+299d9d30/3fc15d30> <=====
Trace; c0130393 <schedule_timeout+e5/e7>
Trace; c024847a <uart_write+18a/4be>
Trace; c02361d8 <read_chan+2d8/100e>
Trace; c0237094 <write_chan+186/272>
Trace; c011ecd7 <default_wake_function+0/2e>
Trace; c011ecd7 <default_wake_function+0/2e>
Trace; c0235f00 <read_chan+0/100e>
Trace; c022f4e3 <tty_read+24b/2ce>
Trace; c012ac52 <tasklet_action+40/61>
Trace; c0171c26 <vfs_read+bc/127>
Trace; c0171edd <sys_read+42/63>
Trace; c010a067 <syscall_call+7/b>
2 warnings and 1 error issued. Results may not be reliable.
full at http://www.ludenkalle.de/C
Signature · 5 lines
2.5.73-mm1 Konstantin Kletschke <[email protected]>, <[email protected]> GPG KeyID EF62FCEF Fingerprint: 13C9 B16B 9844 EC15 CC2E A080 1E69 3FDA EF62 FCEF keulator.homelinux.org up 7 min,
Re: medium Oops on 2.5.73-mm1
Quoted 4 lines · Konstantin Kletschke
This evening 2.5.73-mm1 "crashed" two times. The " because of that: this time it did not freeze completely, it disabled keyboard and mouse buttons, mouse movements where working still! I was running X...
Please see if it is repeatable without the nVidia driver loaded.
Re: medium Oops on 2.5.73-mm1
Quoted 2 lines · Andrew Morton
Please see if it is repeatable without the nVidia driver loaded.
Yes, there is no way around that, actually running X with nv driver, and its hard to use only one Monitor instead of them both :(
But, lets see what is happening without this nvidia.ko module...
Konsti
PS.: Sorry Andrew, again I typed r instead of L so you got an personal mail from me, this was not intentional!
Signature · 5 lines
2.5.73-mm1 Konstantin Kletschke <[email protected]>, <[email protected]> GPG KeyID EF62FCEF Fingerprint: 13C9 B16B 9844 EC15 CC2E A080 1E69 3FDA EF62 FCEF keulator.homelinux.org up 6 min,
Quoted 5 lines · Konstantin Kletschke
However, there is only one Problem left for me, before this one can be called 2.6.0: The keys on my PS/2 IBM Keyboard are bouncing very often! I switched from an USB Logitech Keyboard back to my old school, clicking PC-102 IBM Keyboard ATM and the Key bouncing was back immmediatly :(
Quoted 7 lines
Over ssh connections it is even more extreme, I don't know why.
Are there any approaches to debug or whatsoever that thing? I saw many changes to the input layer on this mailing list since 2.5.70 so I gave this one Kernel here another chance :) (see signature). I just wanted to say, the Problem hasn't gone yet, not more, and keep on hacking this great mastepiece of Kernel :-)
Could you further explain what you mean by key "bouncing"? Do you mean the keyboard repeat rate is too fast? If so, could you let me know more details about the system? Also could you try booting w/ "clock=pit" and let me know if the problem persists?
thanks
-john
Good Morning :-)
Quoted 2 lines · john stultz
Could you further explain what you mean by key "bouncing"?
Well, it should become a correct translation of german "prellen" (Wie geht das in Englisch?).
Quoted 1 line
Do you mean the keyboard repeat rate is too fast? If so, could you let
No, that would be no Problem. Often, if I browse in mutt and press Arrow Keys, it is autorepeated suddenly but I only pressed the Key shortly! The Kernel does not realize it is released since ages. Pressing again the kernel stops repeating. That happens with all keys and when with arrow or PageUp/Down keys in slrn it drives me mad!
See also:
http://marc.theaimsgroup.com/?l=linux-kernel&m=105447074931080&w=2
This happens with 2 PS/2 Keyboards plugged into a SIS7xx and an intel 845PE Board. Using USB Keyboards works like a charme...
Quoted 2 lines
me know more details about the system? Also could you try booting w/ "clock=pit" and let me know if the problem persists?
Yes, curious what that means, will know more this evening :)
Happy hacking!
Konsti
Signature · 5 lines
2.5.73-mm1 Konstantin Kletschke <[email protected]>, <[email protected]> GPG KeyID EF62FCEF Fingerprint: 13C9 B16B 9844 EC15 CC2E A080 1E69 3FDA EF62 FCEF keulator.homelinux.org up 46 min,
Quoted 5 lines · Konstantin Kletschke
No, that would be no Problem. Often, if I browse in mutt and press Arrow Keys, it is autorepeated suddenly but I only pressed the Key shortly! The Kernel does not realize it is released since ages. Pressing again the kernel stops repeating. That happens with all keys and when with arrow or PageUp/Down keys in slrn it drives me mad!
I have seen this problem ever since I started using 2.5 on my laptop. I can easily recreate it by pressing two keys at the same time, it seems that then something gets screwed up and he repeats one of the two keys 20-30 times when it stops.
I'll test with that clock=pit option later, when I have the chance to reboot.
Jan
Signature · 2 lines
Q: How did you get into artificial intelligence? A: Seemed logical -- I didn't have any real intelligence.
Quoted 2 lines · Jan De Luyck
I'll test with that clock=pit option later, when I have the chance to reboot.
I tested it now and with pit the IO-APIC is not getting alog with it at boot time, is it worth to write down the error message?
It resultet in something like "clock not usable" or something. Hell wait, I can capture it at serial console :-)
Konsti
Signature · 5 lines
2.5.73-mm1 Konstantin Kletschke <[email protected]>, <[email protected]> GPG KeyID EF62FCEF Fingerprint: 13C9 B16B 9844 EC15 CC2E A080 1E69 3FDA EF62 FCEF keulator.homelinux.org up 18 min,
Quoted 1 line · Konstantin Kletschke
wait, I can capture it at serial console :-)
Linux version 2.5.73-mm1 ([email protected]) (gcc version 3.2.3 20030422 (Gentoo Linux 1.4 3.2.3-r1, propolice)) #2 Tue Jun 24 22:24:45 CEST 2003
Video mode to be used for restore is f00
BIOS-provided physical RAM map:
BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
BIOS-e820: 0000000000100000 - 000000002fff0000 (usable)
BIOS-e820: 000000002fff0000 - 000000002fff8000 (ACPI data)
BIOS-e820: 000000002fff8000 - 0000000030000000 (ACPI NVS)
BIOS-e820: 00000000fec00000 - 00000000fec01000 (reserved)
BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved)
BIOS-e820: 00000000fff00000 - 0000000100000000 (reserved)
767MB LOWMEM available.
found SMP MP-table at 000fba20
hm, page 000fb000 reserved twice.
hm, page 000fc000 reserved twice.
hm, page 000f5000 reserved twice.
hm, page 000f6000 reserved twice.
On node 0 totalpages: 196592
DMA zone: 4096 pages, LIFO batch:1
Normal zone: 192496 pages, LIFO batch:16
HighMem zone: 0 pages, LIFO batch:1
ACPI: RSDP (v000 AMI ) @ 0x000fa160
ACPI: RSDT (v001 AMIINT INTEL845 00000.00016) @ 0x2fff0000
ACPI: FADT (v001 AMIINT INTEL845 00000.00017) @ 0x2fff0030
ACPI: MADT (v001 AMIINT INTEL845 00000.00009) @ 0x2fff00c0
ACPI: DSDT (v001 INTEL BROKDLEG 00000.04096) @ 0x00000000
ACPI: BIOS passes blacklist
ACPI: Local APIC address 0xfee00000
ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
Processor #0 15:2 APIC version 20
ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] disabled)
ACPI: IOAPIC (id[0x02] address[0xfec00000] global_irq_base[0x0]) IOAPIC[0]: Assigned apic_id 2
IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, IRQ 0-23
ACPI: INT_SRC_OVR (bus[0] irq[0x0] global_irq[0x2] polarity[0x0] trigger[0x0])
ACPI: INT_SRC_OVR (bus[0] irq[0x9] global_irq[0x9] polarity[0x1] trigger[0x3])
Enabling APIC mode: Flat. Using 1 I/O APICs
Using ACPI (MADT) for SMP configuration information
Building zonelist for node : 0
Kernel command line: console=ttyS0,115200 console=tty0 root=/dev/hda1 clock=pit
Initializing CPU#0
PID hash table entries: 4096 (order 12: 32768 bytes)
Console: colour VGA+ 80x25
Calibrating delay loop... 1199.30 BogoMIPS
Memory: 773944k/786368k available (1988k kernel code, 11656k reserved, 537k data, 312k init, 0k highmem)
Checking if this processor honours the WP bit even in supervisor mode... Ok.
Dentry cache hash table entries: 131072 (order: 7, 524288 bytes) Inode-cache hash table entries: 65536 (order: 6, 262144 bytes) Mount-cache hash table entries: 512 (order: 0, 4096 bytes) -> /dev
-> /dev/console
-> /root
CPU: Trace cache: 12K uops, L1 D cache: 8K
CPU: L2 cache: 512K
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.
CPU#0: Intel P4/Xeon Extended MCE MSRs (12) available
CPU#0: Thermal monitoring enabled
CPU: Intel(R) Pentium(R) 4 CPU 2.40GHz stepping 07
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done. Checking 'hlt' instruction... OK.
POSIX conformance testing by UNIFIX
enabled ExtINT on CPU#0
ESR value before enabling vector: 00000000
ESR value after enabling vector: 00000000
ENABLING IO-APIC IRQs
..TIMER: vector=0x31 pin1=2 pin2=-1
..MP-BIOS bug: 8254 timer not connected to IO-APIC
...trying to set up timer (IRQ0) through the 8259A ... failed. ...trying to set up timer as Virtual Wire IRQ... failed. ...trying to set up timer as ExtINT IRQ... failed :(.
Kernel panic: IO-APIC + timer doesn't work! pester [email protected]
Signature · 5 lines
2.5.73-mm1 Konstantin Kletschke <[email protected]>, <[email protected]> GPG KeyID EF62FCEF Fingerprint: 13C9 B16B 9844 EC15 CC2E A080 1E69 3FDA EF62 FCEF keulator.homelinux.org up 3 min,
Quoted 4 lines · Konstantin Kletschke
However, there is only one Problem left for me, before this one can be called 2.6.0: The keys on my PS/2 IBM Keyboard are bouncing very often! I switched from an USB Logitech Keyboard back to my old school, clicking PC-102 IBM Keyboard ATM and the Key bouncing was back immmediatly :(
It might be that you have a similar problem as Joern Engel:
[email protected]
Robert
Signature · 5 lines
Dipl.-Ing. Robert Schwebel | http://www.pengutronix.de
Pengutronix - Linux Solutions for Science and Industry
Braunschweiger Str. 79, 31134 Hildesheim, Germany
Handelsregister: Amtsgericht Hildesheim, HRA 2686
Phone: +49-5121-28619-0 | Fax: +49-5121-28619-4