General
cancel
Showing results for 
Search instead for 
Did you mean: 

How to found problem when system Oops?

NiCK_76
Respected Contributor

How to found problem when system Oops?

Hi expert:
How can I read Oops screen infomation to found real problem?
As Oops screen is following and sysreport is attached:
*pte=7273752f
Oops = 0000
parport_pl lp parport autofs4 audit b44 floppy sg microcode
keybdev mousedev hid input ehei-hcd usb-uhci ubcore ext3
jbd aic7xxx diskdumplib sd-mod scsi-mod
cpu : 0
EIP : 0060:[<04245c8b>] Not tainted
EFLAGS : 00010206
EIP is at Using_versions [] 0x4245c8a (2.4.21-20.ELsmp/i686)
eax : f8884720 ebx : c39f8d00 ecx : 04245c8b edx : c03a7ebc
esi : de8ca689 edi : ffffffed ebp : c3aaedc0 esp : db929f54
ds : 0068 es : 0068 53 : 0068
process updatedb (pid=6642,stackpage=db929000)
stack : co162490 de8ca680 c39f8d00 00018800 f6366000 08906e0 bfffca48 c0162378
de8cda80 c3a9edc0 00018800 db929f84 de8cda80 c3a9edc0 f6396000 c3936720
00000005 00000003 00000001 089906e0 00000005 c0162783 f6396000 00018800
Call Trace: [] dentry_open [kernel] 0x110(0xdb929f54)
[] filp_open [kernel] 0x68 (0xdb929f70)
[] sys_open [kernel] 0x53(0xdb929fa8)
Code : Bad EIP Value
Kernel panic : Fatal exception
just for fun
3 REPLIES
Ivajlo Yanakiev
Respected Contributor

Re: How to found problem when system Oops?

I raly not good with that one :)
but genearly if you have opsss you have hardware problem. check you memory CPU and so on.
Vitaly Karasik_1
Honored Contributor

Re: How to found problem when system Oops?

I recommend to start from checking CPU/RAM too:

http://www.microwerks.net/~hugo/download/download.html - It lets you test your RAM (with memtest86) and your CPU (with cpuburn and lucifer).

if your HW is OK, read this http://www.linuxdevcenter.com/pub/a/linux/2001/11/01/postmortem.html
Linux System Failure Post-Mortem
dirk dierickx
Honored Contributor

Re: How to found problem when system Oops?

take a look at the manpage of ksymoops.