Fresh install of RH 7.2, having a issue with segment faults and corrupted tar files. I would like to ask if anyone has any ideas of what may be causing this, if its software or in fact hardware, what would i look at if hardware?


Processor Info
-----------------------
Dual Pentium III 1 Ghz

Memory Information
-----------------------
1 gig ram

System Information
-----------------------
Linux 2.4.7-10smp #1 SMP
(before fresh install, i also used 2.4.17)

Problem
-----------------------
During a file transfer from any server (local (ie: transfering from another server on the same switch) or remote) i get the following

164400K .......... .......... .......... .......... .......... 26% @ 1.09 MB/s
164450K .......... .......... .......... .......... .......... 26% @ 1.14 MB/s
164500K .........Segmentation fault

Logs show:

Jan 24 21:05:18 sandy kernel: Unable to handle kernel paging request at virtual address 2140f800
Jan 24 21:05:18 sandy kernel: printing eip:
Jan 24 21:05:18 sandy kernel: c013d2af
Jan 24 21:05:18 sandy kernel: *pde = 00000000
Jan 24 21:05:18 sandy kernel: Oops: 0000
Jan 24 21:05:18 sandy kernel: CPU: 0
Jan 24 21:05:18 sandy kernel: EIP: 0010:[fput+15/224]
Jan 24 21:05:18 sandy kernel: EIP: 0010:[<c013d2af>]
Jan 24 21:05:18 sandy kernel: EFLAGS: 00010282
Jan 24 21:05:18 sandy kernel: eax: c5551786 ebx: c5551786 ecx: e8866894 edx: e88668c4
Jan 24 21:05:18 sandy kernel: esi: 0002c027 edi: d7b4c008 ebp: 2140f7f8 esp: ccb77f04
Jan 24 21:05:18 sandy kernel: ds: 0018 es: 0018 ss: 0018
Jan 24 21:05:18 sandy kernel: Process wget (pid: 18236, stackpage=ccb77000)
Jan 24 21:05:18 sandy kernel: Stack: ccb77f0c ccb77f0c 00000000 00000000 d7b4c008 d7b4c000 d7b4c008 00000001
Jan 24 21:05:18 sandy kernel: c014ce75 00000000 00000000 00000020 c014d21e ccb77f54 ccb77f54 00000145
Jan 24 21:05:18 sandy kernel: ccb76000 00015f90 00000006 00000000 00000000 d7b4c000 00000001 bfffe334
Jan 24 21:05:18 sandy kernel: Call Trace: [poll_freewait+53/80] [do_select+542/576] [sys_select+825/1152] [system_call+51/56]
Jan 24 21:05:18 sandy kernel: Call Trace: [<c014ce75>] [<c014d21e>] [<c014d5a9>] [<c010716b>]
Jan 24 21:05:18 sandy kernel:
Jan 24 21:05:18 sandy kernel: Code: 8b 7d 08 f0 ff 4b 14 0f 94 c0 84 c0 0f 84 a8 00 00 00 53 e8

I'm about 90% sure it is hardware related. Try moving the data to another machine, and see if the problem disappears.

I should have added

We did transfer the data to another server, untarred it and it worked fine, the tar itself is about 500 to 600 mb in size

I will go ahead and call the company i got the server from since they reside in the same city as my Data Center :)

(BTW: Its Amax Corporation, out of the 6 servers I got from them, this is the last one we decided on getting from them, bad choice (because 1 other server was DOA as well......InterPro Microsystems, which is a company that also resides in Fremont is where we been getting our latest servers now and their great :)