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-next>] [day] [month] [year] [list]
Date:	Tue, 13 Jan 2009 13:24:55 +0100
From:	Michal Hocko <mhocko@...e.cz>
To:	LKML <linux-kernel@...r.kernel.org>
Cc:	Ingo Molnar <mingo@...e.hu>, Nick Piggin <nickpiggin@...oo.com.au>,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>
Subject: WARNING: at kernel/sched.c:4440 sub_preempt_count+0x81/0x95()

Hi,
I am not sure whether someone has already reported this, but 
I can see the following early boot WARNING with the 2.6.29-rc1 kernel in
the serial console output:

------------[ cut here ]------------
WARNING: at kernel/sched.c:4440 sub_preempt_count+0x81/0x95()
Hardware name: LIFEBOOK S7110
Modules linked in:
Pid: 0, comm: swapper Not tainted 2.6.29-rc1 #5
Call Trace:
 [<c0125735>] warn_slowpath+0x71/0xa8
 [<c013f0e1>] ? tick_check_oneshot_change+0x3c/0xf0
 [<c0137f96>] ? hrtimer_run_pending+0x33/0xac
 [<c03fde85>] ? _spin_unlock_irq+0x10/0x24
 [<c012d110>] ? run_timer_softirq+0x198/0x1a0
 [<c04001e0>] sub_preempt_count+0x81/0x95
 [<c0129fe6>] _local_bh_enable+0x6c/0x6e
 [<c012a0de>] __do_softirq+0xf6/0x100
 [<c0129fe8>] ? __do_softirq+0x0/0x100
 <IRQ>  [<c014f444>] ? handle_level_irq+0x0/0xc6
 [<c0129db7>] ? irq_exit+0x3a/0x77
 [<c01046ac>] ? do_IRQ+0xf1/0x107
 [<c0103527>] ? common_interrupt+0x27/0x2c
 [<c01400d8>] ? timer_stats_update_stats+0x1f6/0x1fe
 [<c03fdea0>] ? _spin_unlock_irqrestore+0x7/0x25
 [<c014eabf>] ? __setup_irq+0x17e/0x1cb
 [<c014ebe7>] ? setup_irq+0x19/0x1d
 [<c05d6786>] ? time_init_hook+0x2b/0x2d
 [<c05ca6f6>] ? hpet_time_init+0x16/0x18
 [<c05c575a>] ? start_kernel+0x224/0x292
 [<c05c5085>] ? __init_begin+0x85/0x8d
---[ end trace 4eaa2a86a8e2da22 ]---

Full boot log is attached as well as config.
Should I try to bisect down the cause? (Any hints which commits to try
before that?)

[I wasn't sure who should be in CC]

Thanks in advance
and
Best regards.
-- 
Michal Hocko
L3 team 
SUSE LINUX s.r.o.
Lihovarska 1060/12
190 00 Praha 9    
Czech Republic

View attachment "boot.log" of type "text/plain" (67694 bytes)

View attachment "config-2.6.29-rc1" of type "text/plain" (60756 bytes)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ