linux-kernel - run_posix_cpu_timers panic on v2.6.22-rc6

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>] [day] [month] [year] [list]

Message-ID: <20070701065726.GA20619@hostway.ca>
Date:	Sat, 30 Jun 2007 23:57:26 -0700
From:	Simon Kirby <sim@...nation.com>
To:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: run_posix_cpu_timers panic on v2.6.22-rc6

Having recently upgraded our Asterisk server, I figured it would be a
good time to try a NO_HZ kernel.  Everything was running well, until...
it decided to panic.

All I have is a fuzzy picture of the console to work from.  The panic
was a fatal exception in interrupt, with EIP within run_posix_cpu_timers.
I can't quite read the offsets, but the stack backtrace was:

	run_rebalance_domains
	scheduler_tick
	tick_periodic
	tick_handle_periodic
	smp_apic_timer_interrupt
	apic_timer_interrupt
	default_idle
	default_idle
	cpu_idle
	start_kernel

Seeing as this is all new code and the box has been otherwise stable for
the past 3 years, there is probably a problem stil lurking in the NO_HZ
code somewhere.  But, it looks like I don't have any other info.  I'll
try to get a better shot of the Oops next time...

Simon-
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/