Another one?

Cristian Candet (ccris@romus.ro)
Tue, 7 Oct 1997 15:14:55 +0300 (EET DST)


Hi guys.

On my P166 machine running 2.0.30, I started a flood ping to one of
the workstations on my net. When I launched a second flood ping on another
workstation I got the following error:

general protection: 0000
CPU: 0
EIP: 0010:[<0014b522>]
EFLAGS: 00010206
eax: 827d07c2 ebx: 02d06be8 ecx: 02d06be0 edx: 037cd188
esi: 02276018 edi: 2b49e6c1 ebp: 02276018 esp: 03028f28
ds: 0018 es: 0018 fs: 002b gs: 002b ss: 0018
Process ping (pid: 12791, process nr: 45, stackpage=03028000)
Stack: 00d17c0c 02be2e1c 02be2e7c 00140c4d 02276018 02d06be8 001e9160
2b49e6c1
0149e6c1 00000000 02be2e7c 001dfd60 00200008 02d06be8 00000001
00000000
00000000 00000001 ffffff00 00000001 0149e6c1 0805ba40 00000246
0013994c
Call Trace: [<00140c4d>] [<0013994c>] [<001178af>] [<0010a57b>]
Code: 66 8b 40 02 86 c4 25 ff ff 00 00 50 57 8b 42 24 0f b7 40 0c
Aiee, killing interrupt handler

The machine did not freeze and apparently everything seemed to be normal
after this message. Anyway it's the second time when under this
circumstances (2 flood pings) I get an error message. Do you find any
meaning for this?

----------------------------------------------
Cristian Candet
Network Administrator
----------------------------------------------
E-mail: ccris@romus.ro
Alternate e-mail: ccris@lbi.ro
Ripe Handle: CC58-RIPE
Internic Handle: CC2501
----------------------------------------------
"If you want to call yourself a good shooter,
first shoot and then call whatever you hit
the TARGET..."
----------------------------------------------