From: Jens Axboe <axboe@suse.de>
To: Dave Jones <davej@redhat.com>, linux-kernel@vger.kernel.org
Subject: Re: 2.6.17-git broke suspend!
Date: Wed, 28 Jun 2006 10:05:19 +0200 [thread overview]
Message-ID: <20060628080519.GN32115@suse.de> (raw)
In-Reply-To: <20060627191125.GH7914@redhat.com>
On Tue, Jun 27 2006, Dave Jones wrote:
> On Tue, Jun 27, 2006 at 08:55:33PM +0200, Jens Axboe wrote:
>
> > > I don't see any cpufreq stuff in your dmesg at all.
> > > Is it definitly on in the config ?
> >
> > Strangely, now /sys/devices/system/cpu/cpu0 also seems to be empty on
> > this kernel. Wonder what is going on here...
> >
> > CONFIG_CPU_FREQ=y
> > CONFIG_CPU_FREQ_TABLE=y
> > # CONFIG_CPU_FREQ_DEBUG is not set
> > CONFIG_CPU_FREQ_STAT=y
> > # CONFIG_CPU_FREQ_STAT_DETAILS is not set
> > CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE=y
> > # CONFIG_CPU_FREQ_DEFAULT_GOV_USERSPACE is not set
> > CONFIG_CPU_FREQ_GOV_PERFORMANCE=y
> > CONFIG_CPU_FREQ_GOV_POWERSAVE=m
> > CONFIG_CPU_FREQ_GOV_USERSPACE=m
> > CONFIG_CPU_FREQ_GOV_ONDEMAND=m
> > CONFIG_CPU_FREQ_GOV_CONSERVATIVE=m
>
> CONFIG_X86_SPEEDSTEP_CENTRINO too ?
>
> booting with cpufreq.debug=7 should show _some_ info.
> Give that a shot
Ok, foudn the problem, it was indeed a missing .config setting. I had
acpi processor as =m, and apparently some of the later kernels then
don't allow CPU_FREQ_ACPI_TABLES=y and just helpfully deleted the
option. Fixing that up makes everything work again!
--
Jens Axboe
next prev parent reply other threads:[~2006-06-28 8:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-27 18:10 2.6.17-git broke suspend! Jens Axboe
2006-06-27 18:20 ` Dave Jones
2006-06-27 18:26 ` Jens Axboe
2006-06-27 18:31 ` Jens Axboe
2006-06-27 18:39 ` Dave Jones
2006-06-27 18:55 ` Jens Axboe
2006-06-27 19:11 ` Dave Jones
2006-06-27 19:13 ` Dave Jones
2006-06-27 21:27 ` Jens Axboe
2006-06-28 8:05 ` Jens Axboe [this message]
2006-06-28 17:15 ` Dave Jones
2006-06-28 21:19 ` Pavel Machek
2006-06-29 4:55 ` Jens Axboe
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=20060628080519.GN32115@suse.de \
--to=axboe@suse.de \
--cc=davej@redhat.com \
--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