Re: Server Crash

[Florian Lohoff <flo@rfc822.org>]

On Wed, Nov 03, 1999 at 10:49:43AM -0500, Fraser Campbell wrote:
> This was on the screen of one computer when I plugged in a monitor. 
> Interestingly enough the computer was still running but ssh wouldn't accept
> connections at all.  I even restarted ssh and it still would not accept
> connections.
> 
> current->tss.cr3 = 00101000, %cr3 = 00101000
> *pde = 00000000
> Oops: 0000
> CPU:    0
> EIP:    0010:[<0011d2fc>]
> EFLAGS: 00010202
> eax: 00000010   ebx: 21887898   ecx: 01887850   edx: 01887000
> esi: 0157f718   edi: 21887898   ebp: 01bc7f38   esp: 01bc7eb0
> ds: 0018   es: 0018   fs: 002b   gs: 002b   ss: 0018
> Process sshd (pid: 129, process nr: 19, stackpage=01bc7000)
> Stack: 0157f718 00000014 01bc8000 00118436 0157f718 0000002b 00000014
> 01bc8000
>        01bc7f38 0010b130 0000000b 00219edf 00000000 e1887898 00000000
> 01957414
>        00000000 02800000 02000000 00210018 00112dc6 0021b014 01bc7f38
> 00000000
> Call Trace: [<00118436>] [<0010b130>] [<02800000>] [<02000000>]
> [<00210018>] [<00112dc6>] [<00112afc>]
>        [<0010ad78>] [<00114dc1>] [<0013afd2>] [<0010a349>] [<0010ac15>]
> Code: 8b 7b 1c 8b 43 28 85 c0 74 27 8b 48 08 85 c9 74 10 8b 53 04
> 

Please push this through ksymoops - Otherwise noone will be able to
help you .... You need the correct System.map for it.

BTW: Which kernel ?

Flo
PS: If this is still an 2.0 kernel - Please try one of the later 2.2.x kernels,
    a lot of bugs have been eliminated during the long phase of 2.1 ....
-- 
Florian Lohoff		flo@rfc822.org		      	+49-5241-470566
  ...  The failure can be random; however, when it does occur, it is
  catastrophic and is repeatable  ...             Cisco Field Notice