From: Tobias Diedrich <ranma+xen@tdiedrich.de>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: 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: Tue, 14 Jun 2011 01:52:21 +0200 [thread overview]
Message-ID: <20110613235221.GA7417@yumi.tdiedrich.de> (raw)
In-Reply-To: <20110613215123.GA19117@dumpdata.com>
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
(or 0xffffffff because it's really an unsigned int):
[ 5.721794] powernow-k8: fid trans failed, fid 0xa, curr 0x0
[ 5.721909] cpufreq_stats_update: cpu=0
[ 5.721945] max_state=4 last_index=-1
[ 5.722191] ------------[ cut here ]------------
[ 5.722305] kernel BUG at drivers/cpufreq/cpufreq_stats.c:71!
I added the BUG() there:
if (stat->last_index > stat->max_state * stat->max_state) BUG();
Index: linux-3.0-rc2-xen/drivers/cpufreq/cpufreq_stats.c
===================================================================
--- linux-3.0-rc2-xen.orig/drivers/cpufreq/cpufreq_stats.c 2011-06-14 01:24:10.639010391 +0200
+++ linux-3.0-rc2-xen/drivers/cpufreq/cpufreq_stats.c 2011-06-14 01:32:32.743101791 +0200
@@ -56,9 +56,20 @@
struct cpufreq_stats *stat;
unsigned long long cur_time;
+ printk(KERN_WARNING "cpufreq_stats_update: cpu=%d ", cpu);
+
+ if (cpu != 0) // only got one cpu in this particular system
+ BUG();
+
cur_time = get_jiffies_64();
spin_lock(&cpufreq_stats_lock);
stat = per_cpu(cpufreq_stats_table, cpu);
+
+ printk(KERN_WARNING " max_state=%d last_index=%d\n", stat->max_state, stat->last_index);
+
+ if (stat->last_index > stat->max_state * stat->max_state)
+ BUG();
+
if (stat->time_in_state)
stat->time_in_state[stat->last_index] =
cputime64_add(stat->time_in_state[stat->last_index],
--
Tobias PGP: http://8ef7ddba.uguu.de
next prev parent reply other threads:[~2011-06-13 23:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-13 20:26 Tobias Diedrich
2011-06-13 21:51 ` Konrad Rzeszutek Wilk
2011-06-13 23:52 ` Tobias Diedrich [this message]
2011-06-14 0:13 ` Tobias Diedrich
2011-06-14 1:34 ` Konrad Rzeszutek Wilk
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=20110613235221.GA7417@yumi.tdiedrich.de \
--to=ranma+xen@tdiedrich.de \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®