<div>Hello,</div>
<div> </div>
<div>It is resolved now (!). I tried to solve one issue but I created another one. I had a problem with "modprobe loop" under 2.6.20-1.2944.fc6 therefore</div>
<div>(as a part of the troubleshooting) I added below line into /etc/modprobe.conf trying to force it to load at start:</div>
<div>install loop /sbin/modprobe loop; /bin/true</div>
<div><br>Becuase I used the same name (loop) twice in above line, I created the loop...</div>
<div> </div>
<div>However once I commented this line all if fine now.</div>
<div> </div>
<div>Chuck - thank you for pointing me in the right direction.</div>
<div> </div>
<div>I'm sorry for any confusion caused,</div>
<div> </div>
<div>Jan<br> </div>
<div><span class="gmail_quote">2007/6/1, Chuck Ebbert <<a href="mailto:cebbert@redhat.com">cebbert@redhat.com</a>>:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">On 06/01/2007 02:58 PM, Jan Andrejkovic wrote:<br>> Hello,<br>><br>> I have FC6 with default latest kernel and I configured encrypted swap
<br>> (using<br>> /etc/crypttab). Now when I need to use losetup to "mount" floppy disk image<br>> as a loop device,<br>> I should have module loop loaded first.<br>><br>> When I try "modprobe loop" modprobe hangs and starts to spawn its
<br>> copies, and then I see more and more modprobe processes eating all my<br>> CPU time and swap space.<br>> The only thing which saves my system from crash is to cancel the<br>> modprobe or if I do "killall modprobe".
<br><br>You need to file a bug for this. And include the contents of<br>/etc/modprobe.conf in the report.<br></blockquote></div><br>