WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

[Xen-users] Re: 3.0.0-rc2: Xen: powernow-k8: Kernel panic - not syncing:

To: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>, xen-users@xxxxxxxxxxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx
Subject: [Xen-users] Re: 3.0.0-rc2: Xen: powernow-k8: Kernel panic - not syncing: Attempted to kill init!
From: Tobias Diedrich <ranma+xen@xxxxxxxxxxxx>
Date: Tue, 14 Jun 2011 02:13:33 +0200
Cc:
Delivery-date: Mon, 13 Jun 2011 17:15:46 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20110613235221.GA7417@xxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Mail-followup-to: Tobias Diedrich <ranma+xen@xxxxxxxxxxxx>, Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>, xen-users@xxxxxxxxxxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx
References: <20110613202622.GC20616@xxxxxxxxxxxxxxxxx> <20110613215123.GA19117@xxxxxxxxxxxx> <20110613235221.GA7417@xxxxxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.20 (2009-06-14)
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);

-- 
Tobias                                          PGP: http://8ef7ddba.uguu.de

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users