linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Zwane Mwaikambo <zwane@arm.linux.org.uk>
To: "Robert L. Harris" <Robert.L.Harris@rdlg.net>
Cc: Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: Re: FINALLY caught a panic
Date: Tue, 5 Aug 2003 10:08:22 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.53.0308051003070.7244@montezuma.mastecende.com> (raw)
In-Reply-To: <20030805135046.GO13456@rdlg.net>

On Tue, 5 Aug 2003, Robert L. Harris wrote:

> Code:  Bad EIP value.
> 
> >>EIP; 8011c560 Before first symbol   <=====
> Trace; c011c47d <tasklet_hi_action+5d/90>
> Trace; c011c1ff <do_softirq+6f/d0>
> Trace; c0108bdb <do_IRQ+db/f0>
> Trace; c0105400 <default_idle+0/40>
> Trace; c0105400 <default_idle+0/40>
> Trace; c010ae78 <call_do_IRQ+5/d>
> Trace; c0105400 <default_idle+0/40>
> Trace; c0105400 <default_idle+0/40>
> Trace; c010542c <default_idle+2c/40>
> Trace; c01054a2 <cpu_idle+42/60>
> Trace; c0117e7f <release_console_sem+8f/a0>
> Trace; c0117d8e <printk+11e/140>
> 
>  <0>Kernel panic: Aiee, killing interrupt handler!

It looks like someone freed a tasklet without removing it. But considering 
your kernel cocktail (imported i2c code) it makes it harder for us to 
debug, perhaps if you could try on a newer kernel (i know it'd be hard to 
do if it's production)

-- 
function.linuxpower.ca

  reply	other threads:[~2003-08-05 14:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-05 12:23 FINALLY caught a panic Robert L. Harris
2003-08-05 12:25 ` Zwane Mwaikambo
2003-08-05 13:39   ` Robert L. Harris
2003-08-05 13:50   ` Robert L. Harris
2003-08-05 14:08     ` Zwane Mwaikambo [this message]
2003-08-05 14:22       ` Robert L. Harris
2003-08-05 15:29       ` Krzysztof Halasa
2003-08-05 12:31 ` Matti Aarnio
2003-08-05 12:35 ` Denis Vlasenko

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=Pine.LNX.4.53.0308051003070.7244@montezuma.mastecende.com \
    --to=zwane@arm.linux.org.uk \
    --cc=Robert.L.Harris@rdlg.net \
    --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;
as well as URLs for NNTP newsgroup(s).