VanLUG Email Archive
Matthew Ashton (mashton@bigfoot.com)
Thu, 9 Sep 1999 00:29:56 -0700
I recently had a kernel Oops (my first ever). But I'm
not really sure what to do about it. My system had been
running for 8 days, so heat may have been a factor.
I was untaring netscape 4.61 when it happened, but my system
was still functional after that. The system load crept up to
about 4.5 before I decided to reboot.
Is there anything I should do about this? I'm running 2.2.12.
Is it likely this is a real bug, or just a hardware glitch?
kernel: Unable to handle kernel paging request at virtual address 00800000
kernel: current->tss.cr3 = 01cba000, %cr3 = 01cba000
kernel: *pde = 00000000
kernel: Oops: 0000
kernel: CPU: 0
kernel: EIP: 0010:[find_buffer+40/76]
kernel: EFLAGS: 00010206
kernel: eax: 00800000 ebx: 00495fc0 ecx: 00001601 edx: 00800000
kernel: esi: 00000400 edi: 00495fc0 ebp: 00001601 esp: c1045d74
kernel: ds: 0018 es: 0018 ss: 0018
kernel: Process tar (pid: 11409, process nr: 63, stackpage=c1045000)
kernel: Stack: c0125893 00001601 00495fc0 00000400 c0125afa 00001601 00495fc0 00000400
kernel: 00000400 c5fba600 00495fc0 c1045e1c c203b980 c01379cc 00001601 00495fc0
kernel: 00000400 00495fc0 c1045f08 c0676990 00000400 c4b9e000 00001601 00000008
kernel: Call Trace: [get_hash_table+23/36] [getblk+30/324] [ext2_new_block+1904/2304] [ext2_alloc_block+316/328] [block_getblk+305/624] [ext2_getblk+367/524] [ext2_file_write+1308/1584]
kernel: [common_interrupt+24/32] [schedule+339/640] [wake_up_process+58/68] [__wake_up+59/72] [pipe_read+327/376] [sys_write+219/256] [ext2_file_write+0/1584] [system_call+52/56]
kernel: Code: 8b 00 39 5a 04 75 11 39 72 08 75 0c 66 39 4a 0c 75 06 89 d0
--- Matthew
This archive was generated by hypermail 2.0b3 on Thu 09 Sep 1999 - 08:17:19