From: Jonathan Larmour <jlarmour@redhat.com>
To: David Geng <deli.geng@ncl.ac.uk>
Cc: ecos-discuss@sourceware.cygnus.com
Subject: Re: [ECOS] Network dead after abnormal break
Date: Fri, 05 Jan 2001 15:14:00 -0000 [thread overview]
Message-ID: <3A565551.77EA8D3E@redhat.com> (raw)
In-Reply-To: <000f01c07416$6fbe0300$5210f080@ncl.ac.uk>
David Geng wrote:
>
> Hi, there,
>
> The network will die, if a TCP connect is broken abnormally, for example by
> Ctrl-C at host. I don't know if it is the problem of TCP/IP stack or my
> CS8900A driver porting. eCos seems still working, for I can use GDB to stop
> it and do some single steps. Maybe the interrupt response is lost.
If it's of any help to know, we've had it working with other drivers, so it
may be that driver in particular.
Jifl
--
Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062
Un cheval, pas du glue. Pas du cheval, beaucoup du glue. || Opinions==mine
next prev parent reply other threads:[~2001-01-05 15:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-01 9:17 David Geng
2001-01-05 15:14 ` Jonathan Larmour [this message]
[not found] ` <000801c077cc$27eab1e0$020a0a0a@ncl.ac.uk>
2001-01-08 3:54 ` 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=3A565551.77EA8D3E@redhat.com \
--to=jlarmour@redhat.com \
--cc=deli.geng@ncl.ac.uk \
--cc=ecos-discuss@sourceware.cygnus.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).