So what's the symptom of kernel hang, and core dump file? By the way, have you tried just with oprofile-viewer and oprofile-server instead of through eclipse plug-in, does it hang as well?  "But without Oprofile, the issue disappears", what exactly does this mean, you stop oprofile-server or not doing oprofile at all?

I have a feeling it may not related to ADT but Oprofile itself.

It's should be a bug in oprofile itself, not ADT. By saying "But without Oprofile, the issue disappears", it means doing the copy operation without oprofile at all.

In most cases, the NAS just hang silently without any core dump or any out output on the screen. How ever we noticed a kernel panic once and by reading the panic output on the screen, we found an oprofile related function in kernel named something like "xxx_oprofile_add_sample_xxx" was in the call stack back trace.

The procedures to reproduce are: 

$opcontrol --start-daemon --separate=lib -c 6
$opcontrol --start

Then on a client, copying a 4GB file from NAS, NAS system will hang. Without Oprofile, the error has never happened.

Please provide the text of the kernel panic.

It seems we can no longer reproduce the kernel panic, but the system just hang silently without any output on screen. Here is a script which could trigger the hang on NAS/blacksand:

#!/bin/sh
opcontrol --init
opcontrol --start-daemon --no-vmlinux --separate=lib -c 6
opcontrol --start
rm -f testfile
dd if=/dev/zero of=./testfile bs=1G count=4

How long do you allow the command to run?

Normally, it will hang the system in less then 3 minutes.

Per today's bug triage, decide to re-assign the bug back to PRC since they have the HW setup to further investigate the issue and come up a clear context on the issue and then seek help from Darren...

Hi Jessica,
Is there any update regarding the bug? Do you know if it's still reproducing?

Thanks,
Alex.

Since we no longer have the setup and lack of info on how to reproduce it