public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Jonathan Larmour <jlarmour@redhat.com>
To: AshCan@aol.com
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] ARM - out of MBUFS - allowing FIQ's in splimp
Date: Thu, 14 Sep 2000 13:45:00 -0000	[thread overview]
Message-ID: <39C138F4.4EC96366@redhat.com> (raw)
In-Reply-To: <47.cd12ad.26f29141@aol.com>

AshCan@aol.com wrote:
> 
> Is it possible this panic condition has been caused by my allowing DAC FIQ's?
> 
> Are there any other possible reasons for this panic condition?

Which sources are you using? I believe the sources in the net EPK on the
web are susceptible to this, but that this has since be fixed in anonymous
CVS. So if you're not already using anon CVS, try that and see if it makes
a difference.

Jifl
-- 
Red Hat, 35 Cambridge Place, Cambridge, UK. CB2 1NS  Tel: +44 (1223) 728762
"Plan to be spontaneous tomorrow."  ||  These opinions are all my own fault

  reply	other threads:[~2000-09-14 13:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-09-14 13:39 AshCan
2000-09-14 13:45 ` Jonathan Larmour [this message]
2000-09-14 16:11 AshCan
2000-09-15 10:37 ` Jonathan Larmour

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=39C138F4.4EC96366@redhat.com \
    --to=jlarmour@redhat.com \
    --cc=AshCan@aol.com \
    --cc=ecos-discuss@sources.redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).