mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Hugo Mills <hugo-lkml@carfax.org.uk>
Cc: linux-kernel@vger.kernel.org, davej@codemonkey.org.uk,
	cpufreq@ZenII.linux.org.uk
Subject: Re: 2.6.11 cpufreq: Device or resource busy
Date: Tue, 8 Mar 2005 23:48:16 -0800	[thread overview]
Message-ID: <20050308234816.245f35b4.akpm@osdl.org> (raw)
In-Reply-To: <20050308222516.GA20370@carfax.org.uk>

Hugo Mills <hugo-lkml@carfax.org.uk> wrote:
>
>    I've just upgraded my laptop (ASUS M3000 -- see below) from 2.6.10
>  to 2.6.11. It now seems to be unable to load the acpi_cpufreq module:
> 
>  hrm@joshua:hrm $ sudo modprobe acpi-cpufreq
>  FATAL: Error inserting acpi_cpufreq (/lib/modules/2.6.11-plain/kernel/arch/i386/kernel/cpu/cpufreq/acpi-cpufreq.ko): Device or resource busy

Presumably there's already a cpufreq driver regisered when you try to load
the acpi_cpufreq module.

If you can work out how to enable cpufreq debugging, then do so.  Or apply
the below patch, see what driver is being registered.

--- 25/drivers/cpufreq/cpufreq.c~a	2005-03-08 23:45:21.000000000 -0800
+++ 25-akpm/drivers/cpufreq/cpufreq.c	2005-03-08 23:45:28.000000000 -0800
@@ -1351,7 +1351,7 @@ int cpufreq_register_driver(struct cpufr
 	    ((!driver_data->setpolicy) && (!driver_data->target)))
 		return -EINVAL;
 
-	dprintk("trying to register driver %s\n", driver_data->name);
+	printk("trying to register driver %s\n", driver_data->name);
 
 	if (driver_data->setpolicy)
 		driver_data->flags |= CPUFREQ_CONST_LOOPS;
_


      reply	other threads:[~2005-03-09  7:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-08 22:25 Hugo Mills
2005-03-09  7:48 ` Andrew Morton [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20050308234816.245f35b4.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=cpufreq@ZenII.linux.org.uk \
    --cc=davej@codemonkey.org.uk \
    --cc=hugo-lkml@carfax.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®