From: Mark Gillespie <email@markgillespie.co.uk>
To: Cpufreq@www.linux.org.uk
Subject: Re: 2.6 kernel crashes - cpufreq
Date: Sat, 20 Dec 2003 19:52:19 +0000 [thread overview]
Message-ID: <3FE4A873.3040606@markgillespie.co.uk> (raw)
I don't have a entry for CONFIG_X86_ACPI_CPUFREQ in my kernel .config
file...
Here is the call stack.... (aploigies if there are errors, as it's
reproduced from a notepad scribble...)
__CPUFREQ_GOVERNOR
__CPUFREQ_SET_POLICY
CPUFREQ_SET_POLICY
CPUFREQ_ADD_DEV
UPDATE_PROCESS_TIMES
REMOVE_VM_AREA
SYSDEV_DRIVER_REGISTER
CPUFREQ_DRIVER_REGISTER
LONGHAUL_INIT
DO_INITCALLS
INIT
INIT
KERNEL_THREAD_HELPER
Dominik Brodowski wrote:
> On Sat, Dec 20, 2003 at 05:43:12PM +0000, Mark Gillespie wrote:
>
>>well, I decided to have a go at putting a 2.6 kernel together for my
>>eden miniIITX system (currently running 2.4.23). I compiled the kernel,
>>and rebooted, but the kernel panics and does a stack dump. It CPUFreq
>>and the userspace governer seems to be the falling over point.
>>
>>Is this a know problem? Anything I can do to work around it?
>
>
> I think it might be an ACPI problem again... can you do the following,
> please?
> a) write down the call trace [function names are enough]
> b) disable CONFIG_X86_ACPI_CPUFREQ and try again
>
> Thanks, and happy holidays,
> Dominik
next reply other threads:[~2003-12-20 19:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-20 19:52 Mark Gillespie [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-12-20 17:43 2.6 kernel crashes - cpufreq Mark Gillespie
2003-12-20 18:35 ` Dominik Brodowski
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=3FE4A873.3040606@markgillespie.co.uk \
--to=email@markgillespie.co.uk \
--cc=Cpufreq@www.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.