public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Simon Kirby <sim@netnation.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: run_posix_cpu_timers panic on v2.6.22-rc6
Date: Sat, 30 Jun 2007 23:57:26 -0700	[thread overview]
Message-ID: <20070701065726.GA20619@hostway.ca> (raw)

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-

                 reply	other threads:[~2007-07-01  7:41 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20070701065726.GA20619@hostway.ca \
    --to=sim@netnation.com \
    --cc=linux-kernel@vger.kernel.org \
    /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