oops in 1.3.27 right after login..

Breakdown (genie@america.com)
Sat, 16 Sep 1995 03:01:24 -0400 (EDT)

Hi. I logged into my 1.3.27 box and after I typed the first command which
happened to be 'w' at this time, I got the following Oops message(it
didn't completely crash, just oopsed on me):

Oops: 0000
EIP: 0010:00127355
EFLAGS: 00010202
eax: 00000000 ebx: 00aeaa50 ecx: 00973700 edx: 001b70a4
esi: 00000000 edi: 00a4b000 ebp: bffffba8 esp: 00ecaf80
ds: 0018 es: 0018 fs: 002b gs: 002b ss: 0018
Process w (pid: 453, process nr: 26, stackpage=00eca000)
Stack: 0011d20c 00973700 00000000 40083404 00000002 00973700 0011d322
00000002 40083404 0075ec0c 400832a4 00000001 00a4b000 0010a3f9
00000002 40083404 400832a4 00000001 bffffba8 ffffffda 4000002b
Call Trace: 0011d20c 0011d322 0010a3f9
Code: 8b 40 3c 85 c0 74 1b 39 48 30 75 0f f6 40 11 08 74 09 b8 e6
Segmentation fault

nm vmlinux yields:
00127320 T get_write_access
00127390 T put_write_access

And from system.map the closest I've got to the offending calls is:

0011d170 T do_open
0011d2f0 T sys_open <---
0011d350 T sys_creat <---
0011d370 T close_fp
... and
0010a390 t reschedule
0010a3a0 T system_call <---
0010a440 T ret_from_sys_call

I have a gateway 2000 486dx2, 16 megs, and I do have tcsh as my login
shell if that is of any relevancy in here('cause I saw you've been having
some minor probs with it or something in the kernel pertaining to its
use). I am not sure how to reproduce it but I do know that it never
happened with 1.2.13 which I also run... Thank you.


p.s. I hope I sent the right info. If I haven't someone please let me
know as to what I should include next time or what did I do wrong. I love
Linux so I want to help as best as possible.