On Thu, 2005-03-03 at 19:19, Christopher K. Johnson wrote: > 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. > Very interesting. The other problem I am working on looks like it may trace back to NetworkManager also. This is not looking good for NetworkManager. Thanks for the input on this. -- Scot L. Harris webid@xxxxxxxxxx History is on our side (as long as we can control the historians).
