From owner-freebsd-alpha Sat Apr 10 10:34:21 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 21E0D15023 for ; Sat, 10 Apr 1999 10:31:33 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id SAA36800; Sat, 10 Apr 1999 18:31:42 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Sat, 10 Apr 1999 18:31:42 +0100 (BST) From: Doug Rabson To: "Gooderum, Mark" Cc: freebsd-alpha@freebsd.org Subject: Re: FreeBSD on Alpha Multia ( In-Reply-To: <50C732FEDE87D211954300A024786203A69A@archeron.good.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, 9 Apr 1999, Gooderum, Mark wrote: > I've got a DEC Multia up reasonably well minus a few problems. I'm > generally running a the late March SNAPSHOT with a 3.1 Release userland. > > Issue 1 - 4.x Kernel (any snapshot from February through 3/26 and CURRENT) > doesn't read the keyboard. 3.1-RELEASE/GENERIC kernel does. The console > isn't locked because output to /dev/console works. Obviously the getty is > on /dev/console and not /dev/ttyvN on the Multia. Any pointers for Keyboard > parameters to play with? I've tried doing a diff of 3.1-RELEASE versus 4.x > but the keyboard code has changed a lot. Note that NumLock/CapsLock toggle > on and off, just no input. Other wierdnesses are that the load program sees > KB input, upper and lower case, but ? comes through as / and some other > similar wierdness. Possibly you need to change your kernel config file. The 4.0 kernels use the new syscons and keyboard drivers and they have slightly different config requirements. Check the contents of GENERIC for details. > > Issue 2 - Random crashes. With 3.1-RELEASE the system will randomly just > restart without any messages from the kernel or a core dump. It's pretty > consistently related to lots of disk activity especially with more than one > process. With the latest 4.x SNAPSHOT things are much more stable and it's > only done that once. I'm not too sure what to suggest. Has anyone else noticed this on 3.1? > > Issue 3 - Are kernel coredumps supposed to work on the Alpha port yet? I've > never had one occur on a crash. Crashdumps are now supported in 4.0 (fairly recently). To interpret them, you will need some gdb patches from Andrew Gallatin. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message