public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: "Teuling, Sieme" <Sieme.Teuling@echostar.com>
Cc: "'linux-mtd@lists.infradead.org'" <linux-mtd@lists.infradead.org>
Subject: Re: Kernel BUG
Date: Tue, 06 Jul 2004 22:21:31 +0200	[thread overview]
Message-ID: <1089145290.26880.9.camel@thomas.tec.linutronix.de> (raw)
In-Reply-To: <C86A9402F6A07E47B2F50A302DFA9BAE044CBF@alm-exch.europe.echostar.com>

On Tue, 2004-07-06 at 17:06, Teuling, Sieme wrote:
> Hi anyone,
> 
> I'm currently using the 2.4.21 kernel with mtd-snapshot-20040621 and a 2.4.
> ilookup patch (included below) on an embedded conexant platform. I sometimes
> run into the error below at the startup of the platform (a short time after
> the mount). Does anybody know where this comes from and if it is possible to
> fix it for the 2.4.21 kernel?

Yes, upgrade to a less ancient kernel. 

> Backtrace: no frame pointer
> Code: 1b00179a e59f0014 eb001798 e3a03000 (e5833000)

The backtrace is meaningless as we do not have much experience in
clairvoyance. Read linux/Documentation/oops-tracing.txt


Thomas

      reply	other threads:[~2004-07-06 20:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-06 15:06 Kernel BUG Teuling, Sieme
2004-07-06 20:21 ` Thomas Gleixner [this message]

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=1089145290.26880.9.camel@thomas.tec.linutronix.de \
    --to=tglx@linutronix.de \
    --cc=Sieme.Teuling@echostar.com \
    --cc=linux-mtd@lists.infradead.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