From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.6) Gecko/20050224 Firefox/1.0.1 Fedora/1.0.1-1.3.1
Description of problem:
While scping large .iso files from this machine to another, system locks up hard, requiring reset button or power cycling.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Boot the 770_FC3 kernel
2. scp large files
3. Watch as system locks up hard after ~100 MB transferred.
Actual Results: Hard lock.
Expected Results: Should have worked.
766_FC3 works fine. noacpi didn't help.
Created attachment 111633 [details]
lspci -vvv of same machine running 766_FC3
Can now confirm that the same thing happens on a dual Opteron under FC3 kernel
770 under x86_64.
Has done the same up through 2.6.11-1.27_FC3smp. UP kernels don't exhibit this
An update has been released for Fedora Core 3 (kernel-2.6.12-1.1372_FC3) which
may contain a fix for your problem. Please update to this new kernel, and
report whether or not it fixes your problem.
If you have updated to Fedora Core 4 since this bug was opened, and the problem
still occurs with the latest updates for that release, please change the version
field of this bug to 'fc4'.
Still occurs on this platform with every FC3 and FC4 kernel to date.
Mass update to all FC4 bugs:
An update has been released (2.6.13-1.1526_FC4) which rebases to a new upstream
kernel (184.108.40.206). As there were ~3500 changes upstream between this and the
previous kernel, it's possible your bug has been fixed already.
Please retest with this update, and update this bug if necessary.
2.6.14-1.1637_FC4 has been released as an update for FC4.
Please retest with this update, as a large amount of code has been changed in
this release, which may have fixed your problem.
This bug has been mass-closed along with other bugs that have been in NEEDINFO
state for several months.
Due to the large volume of inactive bugs in bugzilla, this is the only method we
have of cleaning out stale bug reports where the reporter has disappeared.
If you can reproduce this bug after installing all the current updates, please
reopen this bug.
If you are not the reporter, you can add a comment requesting it be reopened,
and someone will get to it asap.