Re: modprobe using ~100% of cpu?

• To: fedora <fedora-list@xxxxxxxxxx>
• Subject: Re: modprobe using ~100% of cpu?
• From: Marius Andreiana <malists@xxxxxxx>
• Date: Fri, 04 Mar 2005 08:41:32 +0200
• In-reply-to: <[email protected]>
• List-archive: <https://www.redhat.com/archives/fedora-list>
• List-help: <mailto:[email protected]?subject=help>
• List-id: For users of Fedora Core releases <fedora-list.redhat.com>
• List-post: <mailto:[email protected]>
• List-subscribe: <http://www.redhat.com/mailman/listinfo/fedora-list>, <mailto:[email protected]?subject=subscribe>
• List-unsubscribe: <http://www.redhat.com/mailman/listinfo/fedora-list>, <mailto:[email protected]?subject=unsubscribe>
• References: <[email protected]> <[email protected]>
• Reply-to: For users of Fedora Core releases <fedora-list@xxxxxxxxxx>

On Thu, 2005-03-03 at 19:19 -0500, Christopher K. Johnson wrote:
> Scot L. Harris wrote:
> I hit a similar problem upon trying to restart iptables yesterday.
Same here on a laptop. I haven't tried restarting NetworkManager while
iptables was waiting for modprobe to finish.


-- 
Marius Andreiana
Epon Business Applications
http://www.epon.ro

• References:
  • modprobe using ~100% of cpu?
    • From: Scot L. Harris
  • Re: modprobe using ~100% of cpu?
    • From: Christopher K. Johnson

• Prev by Date: Re: Spamassassin 3.0.2 autolearn=ham/spam/no
• Next by Date: HA package for loadbalancing and failover
• Previous by thread: Re: modprobe using ~100% of cpu?
• Next by thread: FC2 -DELL 8400 Integrated Ethernet gigabit controller problem
• Index(es):
  • Date
  • Thread