From: john stultz <johnstul@us.ibm.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>,
mingo@redhat.com, lkml <linux-kernel@vger.kernel.org>
Subject: Re: [-rt BUG] scheduling with irqs disabled: swapper
Date: Sat, 27 May 2006 17:13:52 -0700 [thread overview]
Message-ID: <1148775233.30211.1.camel@leatherman> (raw)
In-Reply-To: <1148692456.5381.7.camel@localhost.localdomain>
On Fri, 2006-05-26 at 21:14 -0400, Steven Rostedt wrote:
> On Fri, 2006-05-26 at 15:53 -0700, john stultz wrote:
> > Hey Ingo, All,
> > We had the following bug reported on bootup on one of our boxes (it
> > was a 4way I believe) running -rt22. So far it seems to be a one-off
> > but I figured I'd post it to see if anyone had a clue.
>
> I'm assuming this is a i386. Also I'm assuming that frame pointers was
> not compiled in since the stack is a little suspicious.
>
> Anyway, could you show the /proc/interrupts of this machine. I'm
> curious if the i8042 isn't sharing an interrupt with something with
> NODELAY in it.
Here ya go:
CPU0 CPU1 CPU2 CPU3
0: 8796 3868607 275 531673 IO-APIC-edge [........N/ 0] pit
2: 0 0 0 0 XT-PIC [........N/ 0] cascade
3: 5 620 2 229 IO-APIC-edge [........./ 63] serial
8: 0 1 0 0 IO-APIC-edge [........./ 0] rtc
11: 0 0 0 0 IO-APIC-edge [........./ 0] acpi
19: 120 0 0 1 IO-APIC-level [........./ 0] ohci_hcd:usb1, ohci_hcd:usb2
24: 57 9 5 46795 IO-APIC-level [........./ 0] eth0
26: 1396 14537 0 702 IO-APIC-level [........./ 0] ioc0
NMI: 0 0 0 0
LOC: 6907796 4419008 4415669 4413513
ERR: 0
MIS: 0
thanks
-john
next prev parent reply other threads:[~2006-05-28 0:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-26 22:53 [-rt BUG] scheduling with irqs disabled: swapper john stultz
2006-05-27 1:14 ` Steven Rostedt
2006-05-28 0:13 ` john stultz [this message]
2006-05-28 1:13 ` Steven Rostedt
2006-05-28 6:40 ` Ingo Molnar
2006-05-29 21:03 ` john stultz
2006-05-30 6:16 ` Ingo Molnar
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=1148775233.30211.1.camel@leatherman \
--to=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mingo@redhat.com \
--cc=rostedt@goodmis.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 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.