From: Tomasz Torcz <zdzichu@irc.pl>
To: linux-kernel@vger.kernel.org
Subject: lost cpufreq (Re: Linux v2.6.18-rc1)
Date: Fri, 7 Jul 2006 19:52:39 +0200 [thread overview]
Message-ID: <20060707175239.GB7648@irc.pl> (raw)
In-Reply-To: <Pine.LNX.4.64.0607052115210.12404@g5.osdl.org>
[-- Attachment #1: Type: text/plain, Size: 1174 bytes --]
On Wed, Jul 05, 2006 at 09:26:35PM -0700, Linus Torvalds wrote:
>
> Ok,
> the merge window for 2.6.18 is closed, and -rc1 is out there
... and cpufreq-nforce2.ko fails to work. Module can't be loaded:
FATAL: Error inserting cpufreq_nforce2
(/lib/modules/2.6.18-rc1/kernel/arch/i386/kernel/cpu/cpufreq/cpufreq-nforce2.ko):
Device or resource busy
Here's relevant difference between dmesg of 2.6.17 and 2.6.18-rc1:
@@ -244,7 +240,6 @@
lp: driver loaded but no devices found
cpufreq: Detected nForce2 chipset revision C1
cpufreq: FSB changing is maybe unstable and can lead to crashes and data loss.
-cpufreq: FSB currently at 165 MHz, FID 10.5
usbcore: registered new driver usbfs
usbcore: registered new driver hub
Motherboard is Abit, NF7,NF7-V (nVidia-nForce2), Version: 2.X,1.0,
(according to dmidecode).
Also alsactl restore didn't restore PCM volume and mute state. Some
mixer elements changed name? Module is snd_intel8x0, chip is integrated
in above mentioned motherboard.
--
Tomasz Torcz "Funeral in the morning, IDE hacking
zdzichu@irc.-nie.spam-.pl in the afternoon and evening." - Alan Cox
[-- Attachment #2: Type: application/pgp-signature, Size: 229 bytes --]
next prev parent reply other threads:[~2006-07-07 17:52 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-06 4:26 Linux v2.6.18-rc1 Linus Torvalds
2006-07-06 9:44 ` Matt Keenan
2006-07-06 12:49 ` Jonathan Corbet
2006-07-06 16:22 ` Linus Torvalds
2006-07-06 12:34 ` Alistair John Strachan
2006-07-07 0:11 ` Andrew Morton
2006-07-06 12:44 ` Nigel Cunningham
2006-07-06 19:44 ` David R
2006-07-06 22:17 ` Greg KH
2006-07-07 21:11 ` David R
2006-07-08 8:14 ` Borislav Petkov
2006-07-08 14:19 ` Kay Sievers
2006-07-08 14:44 ` Andi Kleen
2006-07-08 14:44 ` Andi Kleen
2006-07-08 16:02 ` Greg KH
2006-07-09 23:17 ` Andi Kleen
2006-07-09 23:36 ` Greg KH
2006-07-07 1:05 ` Hervé Fache
2006-07-07 15:41 ` Steve Fox
2006-07-09 10:34 ` Benjamin Herrenschmidt
2006-07-10 13:21 ` Will Schmidt
2006-07-10 14:40 ` Alan Cox
2006-07-10 21:17 ` Benjamin Herrenschmidt
2006-07-11 17:00 ` Steve Fox
2006-07-10 21:16 ` Benjamin Herrenschmidt
2006-07-10 16:38 ` Steve Fox
2006-07-10 18:30 ` Steve Fox
2006-07-07 17:52 ` Tomasz Torcz [this message]
2006-07-07 19:07 ` lost cpufreq (Re: Linux v2.6.18-rc1) Dave Jones
2006-07-07 20:27 ` Tomasz Torcz
2006-07-07 20:35 ` Dave Jones
2006-07-10 10:03 ` Takashi Iwai
2006-07-08 14:09 ` [patchset 0/3 -2.6.18-rc1] pc8736x_gpio: fix re-modprobe errors Jim Cromie
2006-07-08 14:16 ` [patchset 1/3 -2.6.18-rc1] pc8736x_gpio: fix re-modprobe errors - define and use constants Jim Cromie
2006-07-08 14:29 ` [patchset 2/3 -2.6.18-rc1] pc8736x_gpio: fix re-modprobe errors - undo region reservation Jim Cromie
2006-07-08 14:34 ` [patchset 3/3 -2.6.18-rc1] pc8736x_gpio: fix re-modprobe errors - fix/finish cdev-init Jim Cromie
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=20060707175239.GB7648@irc.pl \
--to=zdzichu@irc.pl \
--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