hey. another way to stop modules from loading is the blacklist file. it
should be in /etc/modproble or something(i forgot the exact location). look
for the module blacklist file on google. u put the name f the module you
dont waqnt to load anymjore in there, and it doesnt load it.

On Thu, Dec 18, 2008 at 11:06 AM, Dustin J. Mitchell <[email protected]>wrote:

> On Thu, Dec 18, 2008 at 10:56 AM, Ed Kohlwey <[email protected]> wrote:
> > Another major offender on my powertop list is the wired ethernet module
> > (accounting for 50%+ of the cpu wakeups on an idle system). Does anyone
> > know how to identify which kernel module is assigned what interrupt (or
> > some other way to determine what module is being used by a network
> > interface)?
>
> cat /proc/interrupts may give you what you need, and lspci may help.
>
> But I think you can safely assume that it's the kernel module for your
> ethernet interface that's talking to the hardware.  I assume you're
> seeing these wakeups when you're not using a wired connection?
> Unloading the module, or disabling it entirely (/etc/modules.conf) may
> help, then.
>
> Dustin
>
> --
> Storage Software Engineer
> http://www.zmanda.com
>



-- 
Neil Sikka

Reply via email to