Messages in this thread |  | | Date | Mon, 2 Dec 1996 09:23:35 -0500 (EST) | From | Nathan Bryant <> | Subject | Re: OOPS in 2.0.25 |
| |
I realized something after I posted this message: Since I ran ksymoops on a different machine than the one that actually OOPSes (because when I tried to compile ksymoops on that machine I got signal 11), wouldn't that invalidate the disassembler output?
On Sun, 1 Dec 1996, Nathan Bryant wrote:
> Sendmail caused this OOPS on a machine running 2.0.25: > > Unable to handle kernel paging request at virtual address e0764b19 > current->tss.cr3 = 0067d000, > *pde = 00000000 > Oops: 0000 > CPU: 0 > EIP: 0010:[<0014a47b>] > EFLAGS: 00010246 > eax: 00000000 ebx: 00764a04 ecx: 0100007f edx: 00010001 > esi: 001ff560 edi: 00bdff0c ebp: 00000010 esp: 00bdfed4 > ds: 0018 es: 0018 fs: 002b gs: 002b ss: 0018 > Process sendmail (pid: 7765, process nr: 29, stackpage=00bdf000) > Stack: 001ff4d8 001ff560 080391b8 00000010 00134434 001ff560 00bdff0c > 00000010 > 00000002 bfffb260 00000002 00000000 bfffb504 0074b080 35000002 > 0100007f > 00000000 00000000 00000003 00149da8 00000000 003d80e4 40039000 > 008db818 > Call Trace: [<00134434>] [<00149da8>] [<00118d6b>] [<00118def>] > [<00118c68>] [<00149da8>] [<00135072>] > [<0010a602>] > Code: 8a 83 15 01 00 20 3c 05 76 1f 83 7e 04 02 75 19 c7 46 04 01 > > Here's the ksymoops output: > > >>EIP: 14a47b <inet_connect+f3/1dc> > Trace: 134434 <sys_connect+104/124> > Trace: 149da8 <inet_create> > Trace: 118d6b <do_no_page+103/328> > Trace: 118def <do_no_page+187/328> > Trace: 118def <do_no_page+187/328> > Trace: 149da8 <inet_create> > Trace: 135072 <sys_socketcall+12a/2dc> > Trace: 10a602 <system_call+52/80> > > Code: 14a47b <inet_connect+f3/1dc> movb 0x20000115(%ebx),%al > Code: 14a481 <inet_connect+f9/1dc> cmpb $0x5,%al > Code: 14a483 <inet_connect+fb/1dc> jbe 14a4a4 <inet_connect+11c/1dc> > Code: 14a485 <inet_connect+fd/1dc> cmpl $0x2,0x4(%esi) > Code: 14a489 <inet_connect+101/1dc> jne 14a4a4 <inet_connect+11c/1dc> > Code: 14a48b <inet_connect+103/1dc> movl $0x90900001,0x4(%esi) > Code: 14a492 <inet_connect+10a/1dc> nop > > I'm thinking that this is probably caused by bad hardware, since the > system ran fine for a couple months until a bunch of problems started > cropping up. I figured I'd post this to the list anyway though, in cause > somebody has other ideas. My first step is going to be to replace the RAM > in the box. > > By the way, this is a pentium with stepping=5. I have not yet tried the > mem=nopentium option. > > +-----------------------+----------------------------------+ > | Nathan Bryant | Resident Unix Geek | > | nathan@burgessinc.com | Burgess Business Solutions, Inc. | > +-----------------------+----------------------------------+ > >
+-----------------------+----------------------------------+ | Nathan Bryant | Resident Unix Geek | | nathan@burgessinc.com | Burgess Business Solutions, Inc. | +-----------------------+----------------------------------+
|  |