Re: modprobe using ~100% of cpu?

From: Christopher K. Johnson (ckjohnson_at_gwi.net)
Date: 03/04/05

  • Next message: Johnathan Bailes: "Re: name resolution problem when using wired connection for VPN" 
    Date: Thu, 03 Mar 2005 19:19:43 -0500
To: For users of Fedora Core releases <fedora-list@redhat.com>

    Scot L. Harris wrote:

    >FC3 system, tecra M2.
    >
    >
    >While trouble shooting a problem with name resolution I switched back
    >and forth between the wired and wireless connections a couple of times.
    >
    >I noticed after doing this that the CPU was running at 100% load. top
    >indicates it is modprobe using 99.3% of the CPU.
    >
    >It does not appear that this will stop short of a reboot.
    >
    >Does anyone know if this is a known problem?
    >
    >
    >
    >
    I hit a similar problem upon trying to restart iptables yesterday.
    It cleared up when I stopped the NetworkManager service, which I then
    started again.

    I've not taken the time to search bugzilla yet. Just thought I would
    add my anecdotal evidence of a modprobe/NetworkManager problem. If it
    occurs again you might try 'service NetworkManager restart' as root to
    see if it is the same or a different issue.

    Chris 

    -- 
   "Spend less!  Do more!  Go Open Source..." -- Dirigo.net
   Chris Johnson, RHCE #807000448202021
-- 
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list
  • Next message: Johnathan Bailes: "Re: name resolution problem when using wired connection for VPN"