From owner-freebsd-bugs  Fri Aug 21 05:59:04 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id FAA29758
          for freebsd-bugs-outgoing; Fri, 21 Aug 1998 05:59:04 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from mie.mrit.co.jp (mie.mrit.co.jp [210.128.138.3])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA29740
          for <freebsd-bugs@freebsd.org>; Fri, 21 Aug 1998 05:58:59 -0700 (PDT)
          (envelope-from yasu@codec.mrit.mei.co.jp)
Received: by mie.mrit.co.jp (8.8.4/mrit980615) from mrit [133.185.23.3] with ESMTP
	id VAA13569; Fri, 21 Aug 1998 21:57:59 +0900 (JST)
Received: by mrit.mei.co.jp (8.8.4/mrit980615) with ESMTP
	id VAA22050; Fri, 21 Aug 1998 21:57:58 +0900 from [133.185.25.71];
Received: from waltz.codec.mrit.mei.co.jp by waltz.codec.mrit.mei.co.jp (8.9.1/codec-FreeBSD9703)
	id VAA03447; Fri, 21 Aug 1998 21:57:57 +0900 (JST)
Message-Id: <199808211257.VAA03447@waltz.codec.mrit.mei.co.jp>
To: Bruce Evans <bde@zeta.org.au>, freebsd-bugs@FreeBSD.ORG
Subject: Re: kern/7658: (1) rlogin from some host to the FreeBSD host with very
	 slow link. (ping reports around 200ms - 500ms delay) 
In-reply-to: Your message of "Tue, 18 Aug 1998 16:40:00 MST."
             <199808182340.QAA16570@freefall.freebsd.org> 
Mime-Version: 1.0 (generated by tm-edit 7.108)
Content-Type: text/plain; charset=US-ASCII
Date: Fri, 21 Aug 1998 21:57:57 +0900
From: =?ISO-2022-JP?B?GyRCRU9KVRsoQiAbJEJCWUknGyhC?= (WATANABE Yasuhiko) <yasu@codec.mrit.mei.co.jp>
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

  >  The following reply was made to PR kern/7658; it has been noted by GNATS.
...
  >   >procedure listed in `how to repeat the problem' part.
  >   >Here is the back trace got form a crash dump.
  >   >....
  >   >#10 0xf01417dd in fsync (p=0xf5b49a80, uap=0xf5bdcf84)
  >   >    at ../../kern/vfs_syscalls.c:2425
  >   
  >   Here is a possible fix for the panic.
...

I applied the patch and kerenel continues to work (does not panic) 
after the procedure reported before(below).
  >  (1) rlogin from some host to the FreeBSD host with very slow link.
  >      (ping reports around 200ms - 500ms delay)
  >  (2) run xemacs(20.4 with mule extention) and suspend(^Z) the xemacs.
  >  (3) type ^C several times. (At this point the terminal stops to accept
  >      any keys.)
  >  (4) login to the FreeBSD host again(using new terminal)
  >  (5) kill -HUP -1 (with normal user privilage)
  >      and kernel panic occurs.

But terminal hungs up after the procedure (1),(2),(3).
After the several trial, I found terminal freeze does not
depend on running xemacs or not.

The following procedure still cause to hung terminal:
  >  (1) rlogin from some host to the FreeBSD host with very slow link.
  >      (ping reports around 200ms - 500ms delay)
  >  (2') type ^C several times. (At this point the terminal stops to accept
  >      any keys.)

I did not mentioned but I rlogined 3 times.
      rlogin            rlogin              rlogin
Host A ----> Host B -----------------> Host C -----> Host D
FreeBSD      SunOS      slow link     Solaris       FreeBSD

After I rlogined from Host A to Host D, if I type ^C several times,
then terminal seems to become frozen.


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message