kern/183397: Kernel panic at first incoming ssh
Torbjorn Granlund
tg at gmplib.org
Sun Dec 1 14:40:02 UTC 2013
The following reply was made to PR kern/183397; it has been noted by GNATS.
From: Torbjorn Granlund <tg at gmplib.org>
To: bug-followup at FreeBSD.org
Cc:
Subject: kern/183397: Kernel panic at first incoming ssh
Date: Sun, 01 Dec 2013 15:29:45 +0100
I spent a lot of time to supply needed information. Then silence.
One month later, two BETA releases later.
I didn't try the BETA from 2013-11-30, but since I've not gotten any
indication of that the xn problem has been addressed, I might not be too
pessimistic to assume that FreeBSD 10 still runs as poorly as indicated
by my recent testing:
http://gmplib.org/~tege/virt.html
OK, you're in good company, only NetBSD and older FreeBSD runs well.
The other BSDes work as poorly as or worse than FreeBSD 10.
(No, I haven't reported the "filesystem malfunctions" problem which
happens for 32-bit x86 under both Xen and Linux' KVM. It takes a lot of
time to make good bug reports and to follow up timely, and my last few
experiences of FreeBSD reporting has not encouraged me. To be fair, the
filesystem malfunctions problem might have been fixed.)
It's ironic that I cannot use FreeBSD now, since the virtualisation
problems and the ignored bin/166994 makes no FreeBSD release or
pre-rellease work on newer hardware for what I do. The next major GMP
release will happen in a few weeks and that release will not work on
FreeBSD as things stand now. (It might run on bare metal, but your
bundled clang miscompiled GMP under x86-32 last time I tested...)
FreeBSD surely doesn't look like it used to. I've been a user since
FreeBSD 1.1. I've never seen such a mound of show-stopper bugs as I do
now.
Torbj=C3=B6rn
Please encrypt, key id 0xC8601622
More information about the freebsd-bugs
mailing list