Setup is 486dx50 (not dx2, dx) 4 meg/scsi/SMC ultra network card.
Kernel is mostly bare + module ability + kerneld (but not running)
So looks like something stomped on the process table real hard.
Just before this, something tried to kfree non kmalloced mermory,
on the order of 119 meg. (this is a 4 meg machine)
kfree of non-kmalloced memory: 000583d0, next= 07790774, order=119539497
Unable to handle kernel paging request at virtual address c7200728
current->tss.cr3 = 00360000,
*pde = 00000000
Oops: 0000
CPU: 0
EIP: 0010:[<0011ebf8>] swap_out_process + 0x58
EFLAGS: 00010202
eax: 07200720 ebx: 00232018 ecx: 00058158 edx: 00000000
esi: 00232018 edi: 00000001 ebp: ffffffff esp: 002f7ee0
ds: 0018 es: 0018 fs: 002b gs: 002b ss: 0018
Process testproc (pid: 17966, process nr: 16, stackpage=002f7000)
Stack: 00232018 00000000 00000001 ffffffff 0011ed90 00232018 ffffffff
00000001
00000005 ffffffff 00000001 00000293 0011ee48 00000005 ffffffff
00000001
00000003 00000010 002f7fbc 0011f633 00000003 ffffffff 00000001
0041b958
Call Trace: [<0011ed90>] [<0011ee48>] [<0011f633>] [<00119456>]
[<0010ff0e>] [<0010fda0>] [<0010a7ab>]
Code: 39 50 08 76 13 39 50 04 76 de 89 c1 8b 40 14 eb eb 90 90 90
0011ed80: swap_out
0011ee48: try_to_free_page
0011f633: kswapd
00119456: clear_page_tables
0010ff0e: do_page_fault
0010fda0: si_meminfo
0010a7ab: error_code
Looks ugly... Like the error wanted memory causing a page-fault
but the handler got stepped on.
All the others are the same.
Ideas?
--Dan