From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040510 Description of problem: Starting nfs as 'service nfs start' would freeze the whole system after almost 3 minutes or less. I can confirm that i'm using Fedora Core 2 for almost 10 days and never had this issue at all. I'm running FC2 on my laptop which is a Toshiba Satellite 2450-S203 with 1GB of RAM/2.8Ghz/nVidia. I couldn't reproduce the same on another machine (desktop). I repeated starting the service three times, and it always freezes the whole system. Version-Release number of selected component (if applicable): nfs-utils-1.0.6-22 How reproducible: Always Steps to Reproduce: 1. issue 'service nfs start' 2. wait for 3 minutes Actual Results: I get an error on rpc/quota of nfs, but still works as you see in the screenshot. After less than 3 minutes, the whole system freezes. Expected Results: Not Freeze! Additional info: This is a clean install on my laptop that I always used since RH9. Never had this issue before on any linux I used. Also, if I don't start the service I won't get this problem at all.
Created attachment 100707 [details] Screenshot of terminal starting nfs and output of it
Created attachment 100708 [details] output of 'service --status-all'
Created attachment 100709 [details] dmesg output
Created attachment 100710 [details] lspci output
The fact that all of nfs daemons died with "Connection Refused" tells me its probably a firwall issue... Try service iptables stop to see if that helps
iptables weren't running at all when I used that. Still the problem exists. Is there any more output/diagnostics I need to provide?
Can you turn on the AltSysReq keys (by echo 1 > /proc/sys/kernel/sysrq) then typing Alt-SysReq-P to see what the processor is doing?
As soon as I press SysReq key (with Alt ofcourse) I get a screenshot of my desktop. Sorry, don't know how/if this can be disabled.
Red Hate -> Preferences -> Keyboard shortcuts. Then delete the option for "Take a screen shot of a window". Doug
Does this still happen with more recent FC2 or FC3 kernels?
Fedora Core 2 has now reached end of life, and no further updates will be provided by Red Hat. The Fedora legacy project will be producing further kernel updates for security problems only. If this bug has not been fixed in the latest Fedora Core 2 update kernel, please try to reproduce it under Fedora Core 3, and reopen if necessary, changing the product version accordingly. Thank you.