Date: Fri, 21 Aug 1998 21:57:57 +0900 From: =?ISO-2022-JP?B?GyRCRU9KVRsoQiAbJEJCWUknGyhC?= (WATANABE Yasuhiko) <yasu@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) Message-ID: <199808211257.VAA03447@waltz.codec.mrit.mei.co.jp> In-Reply-To: Your message of "Tue, 18 Aug 1998 16:40:00 MST." <199808182340.QAA16570@freefall.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199808211257.VAA03447>