linux-rt-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Robin Gareus <robin@gareus.org>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Gregory Haskins <ghaskins@novell.com>, linux-rt-users@vger.kernel.org
Subject: Re: 2.6.29-rt1+ irqbalance = OOPS
Date: Sat, 28 Mar 2009 16:57:49 +0100	[thread overview]
Message-ID: <49CE48FD.5040506@gareus.org> (raw)
In-Reply-To: <alpine.LFD.2.00.0903281536420.3397@localhost.localdomain>

Thomas Gleixner wrote:
> On Fri, 27 Mar 2009, Robin Gareus wrote:
>> Gregory Haskins wrote:
>>> Robin Gareus wrote:
>>>> 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
>>> This in of itself might be part of the problem.  I didn't think the
>>> timer was supposed to be threaded.  Thomas?
>> OOPS ;) my bad. IRQ-0 is the timer and it's indeed not threaded.
>>
>> IRQ-1 is i8042
>>
>> The OOPS can be triggered by launching irqbalance. then pressing any key.
>> For whatever reason the OOPS also takes place after a random amount of
>> time without pressing any key..
> 
> Hmm. Works fine here. Can you please provide the output of
> 
> # cat /proc/interrupts
           CPU0       CPU1
  0:    2592396          0   IO-APIC-edge      timer
  1:      31901          0   IO-APIC-edge      i8042
  8:         79          0   IO-APIC-edge      rtc0
  9:     294004          0   IO-APIC-fasteoi   acpi
 12:      55544          0   IO-APIC-edge      i8042
 14:      28478          0   IO-APIC-edge      ata_piix
 15:          0          0   IO-APIC-edge      ata_piix
 16:          0          0   IO-APIC-fasteoi   uhci_hcd:usb1, yenta,
i915@pci:0000:00:02.0
 17:        166          0   IO-APIC-fasteoi   uhci_hcd:usb2, HDA Intel,
ohci1394
 18:          0          0   IO-APIC-fasteoi   uhci_hcd:usb4, mmc0
 19:         66          0   IO-APIC-fasteoi   ehci_hcd:usb3, uhci_hcd:usb5
 28:       1504          0   PCI-MSI-edge      iwl3945
NMI:          0          0   Non-maskable interrupts
LOC:     398393    1538764   Local timer interrupts
SPU:          0          0   Spurious interrupts
CNT:          0          0   Performance counter interrupts
RES:     120526     181396   Rescheduling interrupts
CAL:      42459      30754   Function call interrupts
TLB:        839       1056   TLB shootdowns
TRM:          0          0   Thermal event interrupts
ERR:          0
MIS:          0

The corresponding .config is available at
http://rg42.org/_media/wiki/kernel/config-2.6.29-rt1.txt

I just tested Fernando's CCRMA 2.6.29-rt1 kernel which is x686 plus
generic x86-compat (mine is MCORE2) and irqbalance does not produce an
OOPS there.

I'll see if can get a dump of the OOPS on Monday using netconsole.

HTH,
robin

  reply	other threads:[~2009-03-28 15:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-27 16:16 2.6.29-rt1+ irqbalance = OOPS Robin Gareus
2009-03-27 16:49 ` Gregory Haskins
2009-03-27 17:24   ` Robin Gareus
2009-03-28 14:37     ` Thomas Gleixner
2009-03-28 15:57       ` Robin Gareus [this message]
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=49CE48FD.5040506@gareus.org \
    --to=robin@gareus.org \
    --cc=ghaskins@novell.com \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=tglx@linutronix.de \
    /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;
as well as URLs for NNTP newsgroup(s).