Messages in this thread | | | Date | Mon, 10 May 1999 17:31:26 +0200 | From | Peter Gervai <> | Subject | GP fault 0000; 2.0.36: get_hash_table (ext2 problem?)\ |
| |
Hello.
I have this dump which was followed by several others, rendering the server rather useless requiring a reboot. There were ugly errors on an ext2 filesystem which were repaired by several fsck's and some ext2debug a week ago, all seemed normal afterwards. When I got this one the machine ran the usual server processes (like that squid one got the dump). Maybe this is not important, then discard my info; maybe it is.
kernel: CPU: 0 kernel: EIP: 0010:[get_hash_table+52/172] kernel: EFLAGS: 00010282 kernel: eax: fdf000e9 ebx: 039b1602 ecx: 0103e000 edx: 00000002 kernel: esi: 00001602 edi: 0047b600 ebp: 00000400 esp: 00b0eecc kernel: ds: 0018 es: 0018 fs: 002b gs: 002b ss: 0018 kernel: Process unlinkd (pid: 716, process nr: 50, stackpage=00b0e000) kernel: Stack: 039b5814 00000000 0047b600 00000005 07569d18 00000002 0015f901 00001602 kernel: 0047b600 00000400 01038000 0103e000 00000000 00000008 fffffff4 00000002 kernel: 00000100 00000000 00000001 0047b5ff 07569918 0015fee7 0103e000 0000000c kernel: Call Trace: [trunc_indirect+257/712] [ext2_truncate+91/360] [ext2_put_inode+66/104] [ext2_put_inode+88/104] [iput+205/400] [ext2_unlink+528/548] [do_unlink+260/296] kernel: [sys_unlink+38/60] [system_call+85/124] kernel: Code: 39 38 75 24 66 39 58 04 75 1e 39 68 20 74 22 56 e8 17 f9 ff
squid[685]: diskHandleWrite: FD 17: disk write error: (32) Broken pipe squid[685]: storeDirWriteCleanLogs: Starting...
kernel: Unable to handle kernel paging request at virtual address dc363254 kernel: current->tss.cr3 = 007fe000, %cr3 = 007fe000 kernel: *pde = 00000000 kernel: Oops: 0000 kernel: CPU: 0 kernel: EIP: 0010:[find_candidate+42/228] kernel: EFLAGS: 00010202 kernel: eax: 1c363234 ebx: 0106e398 ecx: 00000400 edx: 000015fd kernel: esi: 00000001 edi: 00000007 ebp: 007fcdb8 esp: 007fcdac kernel: ds: 0018 es: 0018 fs: 002b gs: 002b ss: 0018 kernel: Process squid (pid: 685, process nr: 36, stackpage=007fc000) kernel: Stack: 0106e398 00000001 00000400 0000dc00 00125d07 1c363234 007fcde8 00000400 kernel: 002ab316 007f1602 00000400 002ab316 00000009 0000015e 000007be 000015fd kernel: 00000000 016e9f18 0106e398 00000000 0012615f 00000400 002ab316 007fcef4 kernel: Call Trace: [refill_freelist+891/1144] [getblk+859/956] [ext2_alloc_block+128/412] [block_getblk+348/612] [ext2_getblk+385/556] [ext2_file_write+389/1116] [serial:register_serial+-94348/332] kernel: [udp_v4_mcast_deliver+224/556] [ip_rcv+1211/1576] [serial:register_serial+-94348/332] [def_callback2+38/44] [sys_write+339/396] [do_bottom_half+59/96] [system_call+85/124] kernel: Code: 39 48 20 74 21 6a 01 8d 55 08 52 50 e8 19 18 00 00 83 c4 0c
bye, grin
ps: as usual, please cc to my email any possible replies. I would appreciate an "okay this is just a problem won't hapen again, don't worry", or similar answer as well, just to deactivate my worrying modules. thx.
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
| |