Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: "Ilya A. Volynets-Evenbakh" <ilya@theIlya.com>
To: "Steven J. Hill" <sjhill@realitydiluted.com>
Cc: "Young Chul Park (Patrick)" <pypark@nayna.com>,
	"'linux-mips@linux-mips.org'" <linux-mips@linux-mips.org>
Subject: Re: Linux 2.4.18 MIPS (5KC) Crash after rc.sysinit
Date: Thu, 22 Jan 2004 08:33:41 -0800	[thread overview]
Message-ID: <1074789220.6096.104.camel@iluxa.qarbon.com> (raw)
In-Reply-To: <400FF736.9070305@realitydiluted.com>

Should we add this runt to Oops output?
;-)
On Thu, 2004-01-22 at 08:15, Steven J. Hill wrote:
> PLEASE! Provide the symbols for your crash dump!!! We cannot
> help you if you just give us plain hex values!!!
> 
> -Steve
> 
-- 
Ilya Volynets
Total Knowledge
Chief Technology Officer
http://www.total-knowledge.com

      reply	other threads:[~2004-01-22 16:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-21 22:19 Linux 2.4.18 MIPS (5KC) Crash after rc.sysinit Young Chul Park (Patrick)
2004-01-22 16:15 ` Steven J. Hill
2004-01-22 16:33   ` Ilya A. Volynets-Evenbakh [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=1074789220.6096.104.camel@iluxa.qarbon.com \
    --to=ilya@theilya.com \
    --cc=linux-mips@linux-mips.org \
    --cc=pypark@nayna.com \
    --cc=sjhill@realitydiluted.com \
    /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