Date: Wed, 05 Jan 2000 00:55:26 +0900 From: Jun Kuriyama <kuriyama@sky.rim.or.jp> To: bmilekic@dsuper.net Cc: current@FreeBSD.ORG Subject: Re: panic at kern/uipc_socket2.c Message-ID: <14450.6126.709759.19547O@localhost.sky.rim.or.jp> In-Reply-To: In your message of "Sat, 1 Jan 2000 23:03:39 -0500 (EST)" <Pine.OSF.4.05.10001012256280.28369-100000@oracle.dsuper.net> References: <14446.48302.292419.80479F@localhost.sky.rim.or.jp> <Pine.OSF.4.05.10001012256280.28369-100000@oracle.dsuper.net>
next in thread | previous in thread | raw e-mail | index | archive | help
From: Bosko Milekic <bmilekic@dsuper.net>
> You don't happen to have a backtrace?
I don't have it. When my box gives no reaction, I've hit some keys,
keys, keys...and rebooted automatically. At that time, I could not
switch to VT1 from X with [Ctrl]+[Alt]+[F1].
> Was anything particular happening at the time of the crash? Do you
> have any way to not necessarily directly reproduce the panic but rather
> "force" it to happen (e.g. as a consequence of execution of something or,
> even as a result of some external "trigger")?
I think I used XEmacs, Netscape Communicator and many console works
with ssh'ed remote login. I have no idea which one made this.
Jun Kuriyama // kuriyama@sky.rim.or.jp
// kuriyama@FreeBSD.org
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?14450.6126.709759.19547O>