From: Arjan van de Ven <arjan@infradead.org>
To: Tomasz Torcz <zdzichu@irc.pl>
Cc: bert hubert <bert.hubert@netherlabs.nl>,
linux-kernel@vger.kernel.org, zwane@arm.linux.org.uk
Subject: Re: 2.6.18 regression: cpufreq broken since 2.6.18-rc1 on pentium4
Date: Sun, 30 Jul 2006 21:46:51 +0200 [thread overview]
Message-ID: <1154288811.2941.45.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <20060730160738.GB13377@irc.pl>
On Sun, 2006-07-30 at 18:07 +0200, Tomasz Torcz wrote:
> On Sun, Jul 30, 2006 at 02:08:44PM +0200, bert hubert wrote:
> > Hi everybody,
> >
> > Since 2.6.18-rc1, up to and including -rc3, cpufreq has died on me. It
> > worked fine in 2.6.16.9.
> >
> > # modprobe p4_clockmod
> > FATAL: Error inserting p4_clockmod
> > (/lib/modules/2.6.18-rc3/kernel/arch/i386/kernel/cpu/cpufreq/p4-clockmod.ko):
> > Device or resource busy
> >
as a side note ... you realize that clockmod doesn't actually save you
any power right? ;)
next prev parent reply other threads:[~2006-07-30 19:47 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-30 12:08 bert hubert
2006-07-30 16:07 ` Tomasz Torcz
2006-07-30 16:51 ` 2.6.17 -> " bert hubert
2006-07-30 18:07 ` Alexey Starikovskiy
2006-07-30 18:44 ` bert hubert
2006-07-30 19:01 ` Dave Jones
2006-07-30 19:19 ` bert hubert
2006-07-31 7:08 ` bert hubert
2006-07-31 16:20 ` Dave Jones
2006-07-31 18:57 ` bert hubert
2006-07-31 20:38 ` Dave Jones
2006-07-30 17:45 ` Zwane Mwaikambo
2006-07-31 5:56 ` Tomasz Torcz
2006-07-31 14:04 ` Zwane Mwaikambo
2006-07-31 15:22 ` Tomasz Torcz
2006-07-30 19:46 ` Arjan van de Ven [this message]
2006-07-30 19:53 ` bert hubert
2006-07-31 7:50 ` David Rees
2006-07-31 8:12 ` bert hubert
[not found] <fa.I17h4UhBWCsvus2I0Myp7dcrW/c@ifi.uio.no>
[not found] ` <fa.+Nle/k4hS56BZtGd2LF1VOaLvRg@ifi.uio.no>
2006-07-31 19:14 ` Robert Hancock
2006-07-31 19:35 ` bert hubert
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=1154288811.2941.45.camel@laptopd505.fenrus.org \
--to=arjan@infradead.org \
--cc=bert.hubert@netherlabs.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=zdzichu@irc.pl \
--cc=zwane@arm.linux.org.uk \
/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®