linux-kernel - Next 17 : warn_slowpath() / powernowk8_cpu

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <499AD63B.5040608@in.ibm.com>
Date:	Tue, 17 Feb 2009 20:52:35 +0530
From:	"Sachin P. Sant" <sachinp@...ibm.com>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
CC:	linux-next@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>,
	Mel Gorman <mel@....ul.ie>
Subject: Next 17 : warn_slowpath() / powernowk8_cpu_init

While booting next 17 kernel on a x86_64 box noticed the following

powernow-k8: Found 1 Dual-Core AMD Opteron(tm) Processor 2218 processors (4 cpu cores) (version 2.20.00)
------------[ cut here ]------------
WARNING: at arch/x86/kernel/cpu/cpufreq/powernow-k8.c:1255 powernowk8_cpu_init+0x493/0xd22()
Hardware name: BladeCenter LS21 -[79716AA]-
[Firmware Bug]: powernow-k8: Your BIOS does not provide ACPI _PSS objects in a way that Linux understands. Please report this to the Linux ACPI maintainers and complain to your BIOS vendor.
Modules linked in:

Pid: 1, comm: swapper Not tainted 2.6.29-rc5-autotest-next-20090217 #1

Call Trace:
 [<ffffffff80240744>] warn_slowpath+0xd3/0xf2
 [<ffffffff80257ab3>] ? up+0x34/0x39
 [<ffffffff802606a9>] ? mark_held_locks+0x49/0x69
 [<ffffffff80527038>] ? __mutex_unlock_slowpath+0x117/0x123
 [<ffffffff802607fd>] ? trace_hardirqs_on_caller+0x134/0x15f
 [<ffffffff80260835>] ? trace_hardirqs_on+0xd/0xf
 [<ffffffff8052704d>] ? mutex_unlock+0x9/0xb
 [<ffffffff803f26f0>] ? acpi_processor_register_performance+0x3a9/0x3da
 [<ffffffff802bffd2>] ? kmem_cache_alloc+0xcc/0xfa
 [<ffffffff802607fd>] ? trace_hardirqs_on_caller+0x134/0x15f
 [<ffffffff8039be94>] ? __bitmap_weight+0x78/0x8d
 [<ffffffff8051eed2>] powernowk8_cpu_init+0x493/0xd22
 [<ffffffff8025f25a>] ? lockdep_init_map+0x9c/0x467
 [<ffffffff8047dadc>] ? lock_policy_rwsem_write+0x46/0xaf
 [<ffffffff8047dec5>] cpufreq_add_dev+0x1c6/0x7af
 [<ffffffff80262e82>] ? __lock_acquire+0x773/0x7de
 [<ffffffff802606a9>] ? mark_held_locks+0x49/0x69
 [<ffffffff8052774f>] ? mutex_lock_nested+0x29b/0x2b4
 [<ffffffff802607fd>] ? trace_hardirqs_on_caller+0x134/0x15f
 [<ffffffff8025e753>] ? debug_mutex_free_waiter+0x53/0x57
 [<ffffffff8052775b>] ? mutex_lock_nested+0x2a7/0x2b4
 [<ffffffff80425df0>] ? sysdev_driver_register+0x75/0x10d
 [<ffffffff80425e2a>] sysdev_driver_register+0xaf/0x10d
 [<ffffffff8047cb95>] cpufreq_register_driver+0xc7/0x1f6
 [<ffffffff8051ea33>] powernowk8_init+0xc5/0xd1
 [<ffffffff8051e96e>] ? powernowk8_init+0x0/0xd1
 [<ffffffff8020905c>] do_one_initcall+0x56/0x130
 [<ffffffff80282dc4>] ? register_irq_proc+0xae/0xca
 [<ffffffff80300000>] ? writenote+0x8b/0xb8
 [<ffffffff808b193a>] kernel_init+0x1a2/0x1f9
 [<ffffffff8020ceda>] child_rip+0xa/0x20
 [<ffffffff8020c8fc>] ? restore_args+0x0/0x30
 [<ffffffff80257a8e>] ? up+0xf/0x39
 [<ffffffff808b1798>] ? kernel_init+0x0/0x1f9
 [<ffffffff8020ced0>] ? child_rip+0x0/0x20

---[ end trace dd3dd2a755e71b32 ]---

Should i be worried ? 

I also see few more traces with __debug_object_init().
Will send a separate mail with details for that problem.

Complete dmesg attached.

Thanks
-Sachin


-- 

---------------------------------
Sachin Sant
IBM Linux Technology Center
India Systems and Technology Labs
Bangalore, India
---------------------------------


View attachment "dmesg_x86_64_next17" of type "text/plain" (48127 bytes)