Messages in this thread | | | Date | Fri, 9 May 1997 12:17:43 +0100 | From | Andy Mortimer <> | Subject | known Cyrix problem/fix (paging request at 00000004)? |
| |
Having upgraded my CPU/mboard to some Cyrix (I'm not sure exactly what, but I can find out if necessary), I've started seeing oopses like the following:
May 8 16:07:32 asm21 kernel: Unable to handle kernel paging request at virtual address 00000004 May 8 16:07:32 asm21 kernel: current->tss.cr3 = 00313000, Lr3 = 00313000 May 8 16:07:32 asm21 kernel: *pde = 00000000 May 8 16:07:32 asm21 kernel: Oops: 0002 May 8 16:07:32 asm21 kernel: CPU: 0 May 8 16:07:32 asm21 kernel: EIP: 0010:[<0013190f>] May 8 16:07:32 asm21 kernel: EFLAGS: 00010202 May 8 16:07:32 asm21 kernel: eax: 40006188 ebx: 00000e78 ecx: 00000e78 edx: 40006189 May 8 16:07:32 asm21 kernel: esi: 40006188 edi: 004eddac ebp: 40006188 esp: 004edca8 May 8 16:07:32 asm21 kernel: ds: 0018 es: 0018 fs: 002b gs: 002b ss: 0018 May 8 16:07:32 asm21 kernel: Process clear (pid: 30120, process nr: 11, stackpage=004ed000) May 8 16:07:32 asm21 kernel: Stack: 00093df8 00006018 00131e16 40006188 00000004 080004f0 00000002 000007b8 May 8 16:07:32 asm21 kernel: 00090d84 00000003 00000812 400061a8 00000004 00000001 40000000 00093d98 May 8 16:07:32 asm21 kernel: 00083940 001327b6 004eddac 00eefba0 004edd78 fffffff8 004ede6c 0052c000 May 8 16:07:32 asm21 kernel: Call Trace: [<00131e16>] [<001327b6>] [<00131500>] [<00130014>] [<0012c7bf>] [<0012ca25>] [<0012ca4a>] May 8 16:07:32 asm21 kernel: [<00109f62>] [<0010a855>] May 8 16:07:32 asm21 kernel: Code: 64 c6 00 00 4b 75 f6 5b 5e c3 8d b4 26 00 00 00 00 83 ec 0c
(sorry about the long lines; also, for the non-disassembly of the code: it comes up traced on the console, but apparrently not in the logfiles. I shall have to sort that one out.)
I assumed it was some problem with the memory, and---due mostly to laziness on my part---thought no more of it until recently, when I noticed that the virtual address was *always* 00000004. So I had a look on the web and in the list archives, and all I could find was that it appeared to be a known problem, but no solution was ever suggested.
So: is there a solution already known for this problem?
If not, how many people are being affected by it? I would be more than happy to have a go at finding the problem, but I would need a fair amount of help with it, as although my C is reasonable I have very little assembler or kernel experience; I can certainly supply logs of oodles of the things if anyone wants them!
(I am using kernel 2.0.29, if this matters).
Thankyou for your time,
Andy
-- Andy Mortimer, andy.mortimer@poboxes.com http://www.netforward.com/poboxes/?andy.mortimer Finger asm21@asm21.emma.cam.ac.uk for PGP public key -- I found myself alone, alone above a raging sea That stole the only girl I loved and drowned her deep inside of me.
| |