mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mike Galbraith <efault@gmx.de>
To: Tejun Heo <tj@kernel.org>
Cc: Ingo Molnar <mingo@elte.hu>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: x86-tip: cpufreq breakage - bisection	fingers	89c9215165ca609096e845926d9a18f1306176a4
Date: Wed, 04 Mar 2009 13:13:29 +0100	[thread overview]
Message-ID: <1236168809.14171.9.camel@marge.simson.net> (raw)
In-Reply-To: <49AE4C26.4040104@kernel.org>

On Wed, 2009-03-04 at 18:38 +0900, Tejun Heo wrote:

> I wonder what is going on.  I'll try again with
> 89c9215165ca609096e845926d9a18f1306176a4.  Argh... weird.

marge:/ # modprobe processor
FATAL: Error inserting processor (/lib/modules/2.6.29-tip-smp/kernel/drivers/acpi/processor.ko): Invalid module format

I've got 80 _other_ modules loaded/working just fine, only the cpufreq
stuff won't play ball.

I re-installed binutils/gcc/modutils, checked my repo via git fsck and
rebuilt from scratch, and the problem remains.  That very same module
loads and cpufreq works just peachy with the hacklet I posted.

Yup, pretty weird.

	-Mike


      parent reply	other threads:[~2009-03-04 12:13 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-03 13:07 Mike Galbraith
2009-03-03 14:31 ` Ingo Molnar
2009-03-03 16:38   ` Mike Galbraith
2009-03-04  1:59     ` Tejun Heo
2009-03-04  3:43       ` Mike Galbraith
2009-03-04  6:14         ` Mike Galbraith
2009-03-04  6:31           ` Tejun Heo
2009-03-04  9:38             ` Tejun Heo
2009-03-04  9:43               ` Tejun Heo
2009-03-04 10:44                 ` Mike Galbraith
2009-03-04 13:58                   ` Tejun Heo
2009-03-04 14:35                     ` Mike Galbraith
2009-03-04 14:40                       ` Mike Galbraith
2009-03-04 17:08                       ` Ingo Molnar
2009-03-05  4:36                       ` Tejun Heo
2009-03-04 12:13               ` Mike Galbraith [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=1236168809.14171.9.camel@marge.simson.net \
    --to=efault@gmx.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=tj@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

Powered by JetHome