From owner-freebsd-bugs Tue Jan 11 1:30: 7 2000 Delivered-To: freebsd-bugs@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id EB0FC15418 for ; Tue, 11 Jan 2000 01:30:03 -0800 (PST) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id BAA92193; Tue, 11 Jan 2000 01:30:03 -0800 (PST) (envelope-from gnats@FreeBSD.org) Date: Tue, 11 Jan 2000 01:30:03 -0800 (PST) Message-Id: <200001110930.BAA92193@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: "Martin-Legene, Robert" Subject: Re: misc/16026: /stand/sysinstall segmentation fault when invokin g Distributions Reply-To: "Martin-Legene, Robert" Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR misc/16026; it has been noted by GNATS. From: "Martin-Legene, Robert" To: "'freebsd-gnats-submit@FreeBSD.org'" , "'support@thinserver.net'" Cc: Subject: Re: misc/16026: /stand/sysinstall segmentation fault when invokin g Distributions Date: Tue, 11 Jan 2000 01:20:32 -0800 I got the same yesterday trying to install 3.4 an old Pentium. The = machine used to be a windows machine so maybe it's still trying to recover from that... But anyway, I spent 4 hours trying to debug this but had to give up. I installed several times and managed to get a minimal system running = without entering the Distributions. Running sysinstall over and over again = yielded the same result. ktrace/kdump doesn't show too much really. After going there it just = seems to get a SIGSEGV out of the blue... but sysinstall is stripped (and = some other good excuses) so gdb didn't tell me anything. The problem you have with the shell not echoing your commands is = because the tty has been told not to. "stty sane" bring this back to normal. > -- Robert Martin-Leg=E8ne > The opinions expressed herein is solely my own and not Intel's.. = etcetc >=20 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message