*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: [<c0162490>] dentry_open [kernel] 0x110(0xdb929f54) [<c0162378>] filp_open [kernel] 0x68 (0xdb929f70) [<c0162783>] sys_open [kernel] 0x53(0xdb929fa8) Code : Bad EIP Value Kernel panic : Fatal exception
What was going on that caused this? What is the hardware of machine in question, and is the problem reproducible?
Created attachment 109307 [details] sysreport result
hi,Suzanne Hillman. Comment #2 is sysreport result. The problem occurs once a day or 2 days or 3 days.
This crash appears to be caused by a corrupt fops struct in dentry_open(). dentry_open()------------------------ f->f_op = fops_get(inode->i_fop); ... if (f->f_op && f->f_op->open) { error = f->f_op->open(inode,f); ... ------------------------------------- Can you reproduce this with the RHEL3-U4 kernel? We did fix corruption problems in that kernel.
7273752f => "/vsr". Not something one would expect to find in page table... Care to post other oopsen of the same sort?
This bug is filed against RHEL 3, which is in maintenance phase. During the maintenance phase, only security errata and select mission critical bug fixes will be released for enterprise products. Since this bug does not meet that criteria, it is now being closed. For more information of the RHEL errata support policy, please visit: http://www.redhat.com/security/updates/errata/ If you feel this bug is indeed mission critical, please contact your support representative. You may be asked to provide detailed information on how this bug is affecting you.