From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Tobias Diedrich <ranma+xen@tdiedrich.de>,
xen-users@lists.xensource.com, linux-kernel@vger.kernel.org
Subject: Re: 3.0.0-rc2: Xen: powernow-k8: Kernel panic - not syncing: Attempted to kill init!
Date: Mon, 13 Jun 2011 21:34:58 -0400 [thread overview]
Message-ID: <20110614013457.GB414@dumpdata.com> (raw)
In-Reply-To: <20110614001333.GC7417@yumi.tdiedrich.de>
On Tue, Jun 14, 2011 at 02:13:33AM +0200, Tobias Diedrich wrote:
> Tobias Diedrich wrote:
> > Konrad Rzeszutek Wilk wrote:
> > > > [ 5.523199] rtc_cmos 00:05: setting system clock to 2011-06-13 20:20:00 UTC (1307996400)
> > > > [ 5.523400] powernow-k8: Found 1 AMD Athlon(tm) 64 Processor 3700+ (1 cpu cores) (version 2.20.00)
> > > > [ 5.530956] powernow-k8: fid 0x2 (1000 MHz), vid 0x12
> > > > [ 5.531072] powernow-k8: fid 0xa (1800 MHz), vid 0xa
> > > > [ 5.531187] powernow-k8: fid 0xc (2000 MHz), vid 0x8
> > > > [ 5.531301] powernow-k8: fid 0xe (2200 MHz), vid 0x8
> > > > [ 5.531460] Marking TSC unstable due to cpufreq changes
> > > > [ 5.531680] powernow-k8: fid trans failed, fid 0x2, curr 0x0
> > > > [ 5.531802] BUG: unable to handle kernel paging request at ffff880807e07b78
> > > > [ 5.531982] IP: [<ffffffff81479163>] cpufreq_stats_update+0x46/0x5b
> > >
> > > For this one, you will have to fire out gdb and disassemble the code to
> > > figure out where it failed. Look for 'gdb vmlinux' and 'disassembly' on this
> > > mailing list - that should provide some hints.
> >
> > Probably because of the 'fid trans failed' stat->last_index is -1
>
> It's set to -1 in cpufreq_stats_create_table(), the second call to
> freq_table_get_index() doesn't check against -1 (expecting the call
> to always succeed):
>
> stat->last_time = get_jiffies_64();
> stat->last_index = freq_table_get_index(stat, policy->cur);
What is policy->cur? Is is 800000 ? If so, does this fix your problem:
diff --git a/drivers/cpufreq/powernow-k8.c b/drivers/cpufreq/powernow-k8.c
index 83479b6..9be00d9 100644
--- a/drivers/cpufreq/powernow-k8.c
+++ b/drivers/cpufreq/powernow-k8.c
@@ -1079,7 +1079,8 @@ static int transition_frequency_fidvid(struct powernow_k8_data *data,
}
res = transition_fid_vid(data, fid, vid);
- freqs.new = find_khz_freq_from_fid(data->currfid);
+ if (!res)
+ freqs.new = find_khz_freq_from_fid(data->currfid);
for_each_cpu(i, data->available_cores) {
freqs.cpu = i;
next prev parent reply other threads:[~2011-06-14 1:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-13 20:26 3.0.0-rc2: Xen: powernow-k8: Kernel panic - not syncing: Attempted to kill init! Tobias Diedrich
2011-06-13 21:51 ` Konrad Rzeszutek Wilk
2011-06-13 23:52 ` Tobias Diedrich
2011-06-14 0:13 ` Tobias Diedrich
2011-06-14 1:34 ` Konrad Rzeszutek Wilk [this message]
2011-06-14 13:46 ` Tobias Diedrich
2011-06-14 17:59 ` Konrad Rzeszutek Wilk
2011-06-14 21:28 ` Tobias Diedrich
2011-06-15 12:38 ` Konrad Rzeszutek Wilk
2011-06-15 14:16 ` Tobias Diedrich
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=20110614013457.GB414@dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ranma+xen@tdiedrich.de \
--cc=xen-users@lists.xensource.com \
/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