On Sat, 17 Jul 1999, fusty LePeR wrote:
:
:i sent this msg lomg time ago .
:
:at boot time i get this long msg
:
:
:-----------------------------------
:
:general protection: 0000
:
:CPU: 0
:
:EIP: 0010:[<0012bb2b>]
:
:EFLAGS: 00010286
:
:eax: ea21f000 ebx: bfffdc90 ecx: 080abb98 edx: 00000006
:
:esi: bfffdd00 edi: 080abb98 ebp: bfffdcd0 esp: 00a05f78
:
:ds: 0018 es: 0018 fs: 002b gs: 002b ss: 0018
:
:Process S91smb (pid: 248, process nr: 8, stackpage=00a05000)
:
:Stack: bfffdc90 bfffdd00 bfffe044 bfffdcd0 bfffdc90 bfffdd00 0012c152 080abb98
:
:00a05fa0 bfffdc90 0012a262 0012a277 080abb98 00a05fb4 01f91810 0029bf00
:
:0010abc5 080abb98 bfffdc90 400ab6cc bfffdd00 bfffe044 bfffdcd0 ffffffda
:
:Call Trace: [<0012c152>] [<0012a262>] [<0012a277>] [<0010abc5>]
:
:Code: 39 48 08 76 0c 89 c2 39 4a 04 76 0d 8b 42 14 eb eb 8b 40 18
:
:kfree of non-kmalloced memory: 0001fe58, next= 00b93000, order=1
:
:-----------------------------------------------
:
:im using i586 233mmx
:64M RAM
:kerenel version 2.0.36
:RedHat 5.2
:
well, this is called Oops. Read "Oops-tracing" in Documentation directory
under the source tree of kernel (your version is required). Then,,, using
info you read from it, check which function is doing so bad.
Then you have following posibilities:
Check the problem by yourself (sometimes it works:)
Send a message to kernel people.
check your memory timings,, try to underclock your machine. If the last
one works, well, get better cooling for CPU, or change your memory chips
(if multiple) to one. I had rather bad days when upgrading memory to 128
MB, this issue can be quite insidious.
Omer Mussaev tel: 051308214 | finger for public key
=================================================================
To unsubscribe, send mail to [EMAIL PROTECTED] with
the word "unsubscribe" in the message body, e.g., run the command
echo unsubscribe | mail [EMAIL PROTECTED]
