All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robin Gareus <robin@gareus.org>
To: linux-rt-users@vger.kernel.org
Subject: 2.6.29-rt1+ irqbalance = OOPS
Date: Fri, 27 Mar 2009 17:16:10 +0100	[thread overview]
Message-ID: <49CCFBCA.6050702@gareus.org> (raw)

Hello,

Starting the irqbalance daemon ( http://www.irqbalance.org/ ) on
2.6.29-rt1 causes the system to OOPS and freeze. irqbalance works fine
with previous realtime kernels (2.6.24.7-rt27).

The OOPS seems to be caused by the PID of the [timer] IRQ-1. However the
OOPS message is too long and I can't read the beginning lines on the
terminal. The system hangs so I can't scroll back and it's not written
to any log. SysRq does also not work after the OOPS.

A bit off topic, but how can I capture those OOPSes?

I could get a larger screen and a digital camera ;) The lkcd.sf.net
patch does not apply to 2.6.29. Running a realtime kernel in qemu does
not make much sense, although it may be sufficient to reproduce this OOPS.
Is there a way to use USB as serial console using a hub and two
computers? I guess I'll need a dongle or sth. Besides would a printk()
to a serial port work even if some IRQ handler hangs?

Any ideas? links?
robin

             reply	other threads:[~2009-03-27 16:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-27 16:16 Robin Gareus [this message]
2009-03-27 16:49 ` 2.6.29-rt1+ irqbalance = OOPS Gregory Haskins
2009-03-27 17:24   ` Robin Gareus
2009-03-28 14:37     ` Thomas Gleixner
2009-03-28 15:57       ` Robin Gareus
2009-03-30 13:43         ` Robin Gareus
2009-04-01  6:43           ` Thomas Gleixner
2009-04-04 11:20             ` Robin Gareus

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=49CCFBCA.6050702@gareus.org \
    --to=robin@gareus.org \
    --cc=linux-rt-users@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.