Fatal trap 12: page fault while in kernel mode - during rsync

Fatal trap 12: page fault while in kernel mode - during rsync


output of 'uname -a'
FreeBSD newmail.function.com 4.9-RELEASE FreeBSD 4.9 RELEASE #0: Mon Oct 27 17:09 GMT 2003 root@freebsd-stable.sentex.ca:/usr/obj/usr/src/sys/GENERIC i386


Hardware - Intel P4 2.4GHz 1533
Harddisk - IDE Seagate 120GB
rsync-2.5.6.1

I ran rsync on machine to pull some data (home directories, huge 23 GB) from another machine (running linux) - via SSH on a remote computer. Rsync hanged after 1 GB of data was transferred. Tried a second time. Rsync hanged after 10 GB of data was transferred. Also tried running rsync on linux machine to push data to Freebsd machine.


Error message after rsync ran for a while
-------------------
rsync: error writing 16385 unbuffered bytes - exiting: Broken pipe
rsync error: error in rsync protocol data stream (code 12) at io.c(463)
---------------------

After this, I ran rsync on the actual machine itself to pull data from the linux machine. Seemed to be running fine, but the next morning, the system hanged - screen and keyboard freezed, had to switch machine off and on again. Error message on the screen:
--------------------------
Fatal trap 12: page fault while in kernel mode
fault virtual address = 0xa130
fault code = supervisor write, page not present
instruction pointer = 0x8:0xc034a674
stack pointer = 0x10:0xd6fdbc5c
frame pointer = 0x10:0xd6fdbc60
code segment = base 0x0, limit 0xffffff, type 0x1b = DPL0, pres 1, def32 1, gran1
processor eflags = interrupt enabled, resume, IOPL=0
current process = 216 (rsync)
interrupt mask = net tty bio cam
trap number = 12
panic : page fault
syncing disks ....

------------------
I didn't enable dump.

Can anybody advise? Thank you very much in anticipation.

cmgui

mcg222@yahoo.com

Probably broken hardware.

If only rsync was running, the PC has done the same thing for hours. This cannot cause a kernel page fault (unless your kernel is buggy, but I do not know of such a problem in recent kernels). - UNLESS you are using external USB or FireWire drives.

To check the hardware, you can compile a new kernel eg. This will put heavy load on the disks and the CPU.

Does it break again under load not related to rsync?
-> Checklist:
- are the fans dirty or loud? replace them.
- hard disks: are cables damaged or folded? everything fits firmly?
- RAMs, power supply, mainboard. Here you need some spare parts for testing.

hth,
M.