From owner-freebsd-alpha Sun Mar 26 10:13:48 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from sable.cc.vt.edu (sable.cc.vt.edu [128.173.16.30]) by hub.freebsd.org (Postfix) with ESMTP id A7C9B37B6A6 for ; Sun, 26 Mar 2000 10:13:42 -0800 (PST) (envelope-from nmanisca@vt.edu) Received: from mail.vt.edu (gkar.cc.vt.edu [128.173.16.40]) by sable.cc.vt.edu (8.9.3/8.9.3) with ESMTP id NAA27479 for ; Sun, 26 Mar 2000 13:13:37 -0500 (EST) Received: from dog ([198.82.106.223]) by gkar.cc.vt.edu (Sun Internet Mail Server sims.3.5.1999.05.24.18.28.p7) with SMTP id <0FS100IJEJYOIW@gkar.cc.vt.edu> for freebsd-alpha@freebsd.org; Sun, 26 Mar 2000 13:13:37 -0500 (EST) Date: Sun, 26 Mar 2000 13:12:49 -0500 From: nm Subject: g++ problems? X-Sender: nmanisca@mail.vt.edu To: freebsd-alpha@freebsd.org Message-id: <3.0.32.20000326131248.03413770@mail.vt.edu> MIME-version: 1.0 X-Mailer: Windows Eudora Pro Version 3.0 (32) Content-type: text/plain; charset=us-ascii Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Are there problems with g++ on 4.0-RELEASE? I tried a simple hello world program, but I get unaligned access's out the wazoo. Thanks, Nick Maniscalco nmanisca@vt.edu fb@anomaly:~$ cat > test.cc #include int main() { cout << "Hello World!" << endl; return 1; } fb@anomaly:~$ g++ test.cc fb@anomaly:~$ ./a.out pid 10125 (a.out): unaligned access: va=0x1600b9484 pc=0x160020af4 ra=0x160020c6 0 op=ldq pid 10125 (a.out): unaligned access: va=0x1600b9484 pc=0x160020b00 ra=0x160020c6 0 op=stq pid 10125 (a.out): unaligned access: va=0x1600ba914 pc=0x160020af4 ra=0x160020c6 0 op=ldq pid 10125 (a.out): unaligned access: va=0x1600ba914 pc=0x160020b00 ra=0x160020c6 0 op=stq pid 10125 (a.out): unaligned access: va=0x1600bab74 pc=0x160020af4 ra=0x160020c6 0 op=ldq pid 10125 (a.out): unaligned access: va=0x1600bab74 pc=0x160020b00 ra=0x160020c6 0 op=stq pid 10125 (a.out): unaligned access: va=0x1600baf84 pc=0x160020af4 ra=0x160020c6 0 op=ldq pid 10125 (a.out): unaligned access: va=0x1600baf84 pc=0x160020b00 ra=0x160020c6 0 op=stq pid 10125 (a.out): unaligned access: va=0x1600bb0bc pc=0x160020af4 ra=0x160020c6 0 op=ldq pid 10125 (a.out): unaligned access: va=0x1600bb0bc pc=0x160020b00 ra=0x160020c6 0 op=stq pid 10125 (a.out): unaligned access: va=0x1600bbbec pc=0x160020af4 ra=0x160020c6 0 op=ldq pid 10125 (a.out): unaligned access: va=0x1600bbbec pc=0x160020b00 ra=0x160020c6 0 op=stq pid 10125 (a.out): unaligned access: va=0x1600bc224 pc=0x160020af4 ra=0x160020c6 0 op=ldq pid 10125 (a.out): unaligned access: va=0x1600bc224 pc=0x160020b00 ra=0x160020c6 0 op=stq pid 10125 (a.out): unaligned access: va=0x1600bc3dc pc=0x160020af4 ra=0x160020c6 0 op=ldq pid 10125 (a.out): unaligned access: va=0x1600bc3dc pc=0x160020b00 ra=0x160020c6 0 op=stq pid 10125 (a.out): unaligned access: va=0x1600bc964 pc=0x160020af4 ra=0x160020c6 0 op=ldq pid 10125 (a.out): unaligned access: va=0x1600bc964 pc=0x160020b00 ra=0x160020c6 0 op=stq pid 10125 (a.out): unaligned access: va=0x1600bcf44 pc=0x160020af4 ra=0x160020c6 0 op=ldq pid 10125 (a.out): unaligned access: va=0x1600bcf44 pc=0x160020b00 ra=0x160020c6 0 op=stq pid 10125 (a.out): unaligned access: va=0x1600bd61c pc=0x160020af4 ra=0x160020c6 0 op=ldq pid 10125 (a.out): unaligned access: va=0x1600bd61c pc=0x160020b00 ra=0x160020c6 0 op=stq pid 10125 (a.out): unaligned access: va=0x1600bd73c pc=0x160020af4 ra=0x160020c6 0 op=ldq pid 10125 (a.out): unaligned access: va=0x1600bd73c pc=0x160020b00 ra=0x160020c6 0 op=stq pid 10125 (a.out): unaligned access: va=0x1600bff74 pc=0x160020af4 ra=0x160020c6 0 op=ldq pid 10125 (a.out): unaligned access: va=0x1600bff74 pc=0x160020b00 ra=0x160020c6 0 op=stq Hello World! fb@anomaly:~$ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sun Mar 26 11:16:40 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from pinacolada.net (196-28-51-12.prtc.net [196.28.51.12]) by hub.freebsd.org (Postfix) with ESMTP id 18A9337B7F0 for ; Sun, 26 Mar 2000 11:16:32 -0800 (PST) (envelope-from dmuran@pinacolada.net) Received: from acrys [10.196.2.175] by pinacolada.net with ESMTP (SMTPD32-6.00) id A184F41B00F4; Sun, 26 Mar 2000 15:22:28 -0500 Reply-To: From: "D.A. Muran-de Assereto" To: Subject: Random lockups with 4.0 and serial IO Date: Sun, 26 Mar 2000 15:13:24 -0400 Message-ID: <002c01bf9757$5c878f00$0101a8c0@tuad.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2910.0) X-Mimeole: Produced By Microsoft MimeOLE V5.00.2314.1300 Importance: Normal Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Saw a comment the other day to the effect that this problem had been fixed under 4.0(some_current_date). I CVSUP'ed and built yesterday, and am still seeing the same behavior; to wit: PC164/433, latest SRM runs fine as long as I do not try to use it for serial IO, namely multilink PPP via sio1 & 2. As soon as I do, the machine WILL freeze completely in a random (short) amount of of time. Config: PC164/433, 128MB, booting off IDE. FreeBSD 4.0-STABLE#12, cvsup'ed 000326. Using serial console on sio0, built in serial port with external modem on sio1, ISA modem on sio2. Linksys Ethernet card. This behavior replicates exactly on an Alphastation 400 4/233 using SCSI, same CVSUP, so it's not caused by the hardware config on either machine; the only things they have in common are the CPU type and the two modems I am using. I successfully use FreeBSD 3.4 stable on Intel with the same two modems to accomplish the same task. Any ideas? Dave Muran-de Assereto *** Aude Sapere *** To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sun Mar 26 11:20: 8 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from calis.blacksun.org (calis.blacksun.org [168.100.186.40]) by hub.freebsd.org (Postfix) with ESMTP id 89ECC37BF72 for ; Sun, 26 Mar 2000 11:19:59 -0800 (PST) (envelope-from don@calis.blacksun.org) Received: by calis.blacksun.org (Postfix, from userid 1000) id 8114876; Sun, 26 Mar 2000 14:25:40 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by calis.blacksun.org (Postfix) with ESMTP id 7BD2249F4; Sun, 26 Mar 2000 14:25:40 -0500 (EST) Date: Sun, 26 Mar 2000 14:25:40 -0500 (EST) From: Don To: "D.A. Muran-de Assereto" Cc: freebsd-alpha@freebsd.org Subject: Re: Random lockups with 4.0 and serial IO In-Reply-To: <002c01bf9757$5c878f00$0101a8c0@tuad.org> 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 > PC164/433, latest SRM runs fine as long as I do not try to use it for serial > IO, namely multilink PPP via sio1 & 2. > As soon as I do, the machine WILL freeze completely in a random (short) > amount of of time. I was under the impression that the Alphas used one of the serial ports for internal housekeeping or something and that you couldn't use it for ppp. I haven't seen a message that says otherwise or that says that this was fixed, but I have not been keeping up the way I should. -don To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sun Mar 26 12:29:11 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 0C67437B86A for ; Sun, 26 Mar 2000 12:29:08 -0800 (PST) (envelope-from obrien@NUXI.ucdavis.edu) Received: from dragon.nuxi.com (root@d60-024.leach.ucdavis.edu [169.237.60.24]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id MAA81564; Sun, 26 Mar 2000 12:29:04 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id MAA86789; Sun, 26 Mar 2000 12:29:02 -0800 (PST) (envelope-from obrien) Date: Sun, 26 Mar 2000 12:29:02 -0800 From: "David O'Brien" To: "D.A. Muran-de Assereto" , freebsd-alpha@freebsd.org Subject: Re: Random lockups with 4.0 and serial IO Message-ID: <20000326122901.B86753@dragon.nuxi.com> Reply-To: obrien@freebsd.org References: <002c01bf9757$5c878f00$0101a8c0@tuad.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: ; from don@calis.blacksun.org on Sun, Mar 26, 2000 at 02:25:40PM -0500 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sun, Mar 26, 2000 at 02:25:40PM -0500, Don wrote: > I was under the impression that the Alphas used one of the serial ports > for internal housekeeping or something and that you couldn't use it for > ppp. In GENERIC, sio1 (COMM2) has "flags 0x50". 0x00010 device is potential system console 0x00040 device is reserved for low-level IO (e. g. for remote kernel debugging) Possbily that is causing a problem? -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sun Mar 26 12:34:43 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 5446437B824 for ; Sun, 26 Mar 2000 12:34:41 -0800 (PST) (envelope-from obrien@NUXI.ucdavis.edu) Received: from dragon.nuxi.com (root@d60-024.leach.ucdavis.edu [169.237.60.24]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id MAA81588; Sun, 26 Mar 2000 12:34:40 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id MAA86805; Sun, 26 Mar 2000 12:34:40 -0800 (PST) (envelope-from obrien) Date: Sun, 26 Mar 2000 12:34:39 -0800 From: "David O'Brien" To: nm Cc: freebsd-alpha@freebsd.org Subject: Re: g++ problems? Message-ID: <20000326123439.C86753@dragon.nuxi.com> Reply-To: obrien@freebsd.org References: <3.0.32.20000326131248.03413770@mail.vt.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <3.0.32.20000326131248.03413770@mail.vt.edu>; from nmanisca@vt.edu on Sun, Mar 26, 2000 at 01:12:49PM -0500 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sun, Mar 26, 2000 at 01:12:49PM -0500, nm wrote: > Are there problems with g++ on 4.0-RELEASE? > I tried a simple hello world program, but I get > unaligned access's out the wazoo. This has happened for as long as I've tired hello.cxx on 4-CURRENT (which hasn't been very long that I've done this test). Do you know if there was some point in the past where this wasn't happening? Using printf() instead of I/O streams w/G++ gives the same. Using gcc on the same hello.c doesn't. -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sun Mar 26 13: 0:46 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from sable.cc.vt.edu (sable.cc.vt.edu [128.173.16.30]) by hub.freebsd.org (Postfix) with ESMTP id 50EAF37B7F5; Sun, 26 Mar 2000 13:00:43 -0800 (PST) (envelope-from nmanisca@vt.edu) Received: from mail.vt.edu (gkar.cc.vt.edu [128.173.16.40]) by sable.cc.vt.edu (8.9.3/8.9.3) with ESMTP id QAA12161; Sun, 26 Mar 2000 16:00:39 -0500 (EST) Received: from dog ([198.82.106.223]) by gkar.cc.vt.edu (Sun Internet Mail Server sims.3.5.1999.05.24.18.28.p7) with SMTP id <0FS1004FKRP3UN@gkar.cc.vt.edu>; Sun, 26 Mar 2000 16:00:39 -0500 (EST) Date: Sun, 26 Mar 2000 15:59:51 -0500 From: nm Subject: Re: g++ problems? X-Sender: nmanisca@mail.vt.edu To: obrien@freebsd.org Cc: freebsd-alpha@freebsd.org Message-id: <3.0.32.20000326155951.0341b260@mail.vt.edu> MIME-version: 1.0 X-Mailer: Windows Eudora Pro Version 3.0 (32) Content-type: text/plain; charset=us-ascii Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org At 12:34 PM 3/26/00 -0800, David O'Brien wrote: >On Sun, Mar 26, 2000 at 01:12:49PM -0500, nm wrote: >> Are there problems with g++ on 4.0-RELEASE? >> I tried a simple hello world program, but I get >> unaligned access's out the wazoo. > >This has happened for as long as I've tired hello.cxx on 4-CURRENT (which >hasn't been very long that I've done this test). Do you know if there >was some point in the past where this wasn't happening? I really have no idea. I am quite new to FreeBSD. >Using printf() instead of I/O streams w/G++ gives the same. Using gcc on >the same hello.c doesn't. > >-- >-- David (obrien@NUXI.com) Do you think that this will lead to problems with my c++ programs? Or are the unaligned accesses just going to affect the speed of the code? Nick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sun Mar 26 13:26:49 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id E1CEF37B9FB for ; Sun, 26 Mar 2000 13:26:46 -0800 (PST) (envelope-from obrien@NUXI.ucdavis.edu) Received: from dragon.nuxi.com (root@d60-024.leach.ucdavis.edu [169.237.60.24]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id NAA81792; Sun, 26 Mar 2000 13:26:46 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id NAA87306; Sun, 26 Mar 2000 13:26:46 -0800 (PST) (envelope-from obrien) Date: Sun, 26 Mar 2000 13:26:46 -0800 From: "David O'Brien" To: nm Cc: freebsd-alpha@freebsd.org Subject: Re: g++ problems? Message-ID: <20000326132645.A87193@dragon.nuxi.com> Reply-To: obrien@NUXI.ucdavis.edu References: <3.0.32.20000326155951.0341b260@mail.vt.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <3.0.32.20000326155951.0341b260@mail.vt.edu>; from nmanisca@vt.edu on Sun, Mar 26, 2000 at 03:59:51PM -0500 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sun, Mar 26, 2000 at 03:59:51PM -0500, nm wrote: > Or are the unaligned accesses just going to affect the speed of the > code? Yes. You can also use the `uac' program to change the behavior of handling the unaligned access. When I've got some time, I'll track down the problem with hello.cxx. -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sun Mar 26 19:23:30 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 7EF7A37BAC8; Sun, 26 Mar 2000 19:23:27 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id WAA18104; Sun, 26 Mar 2000 22:23:25 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id WAA21599; Sun, 26 Mar 2000 22:22:55 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Sun, 26 Mar 2000 22:22:55 -0500 (EST) To: obrien@FreeBSD.ORG Cc: nm , freebsd-alpha@FreeBSD.ORG, jdp@FreeBSD.ORG Subject: Re: g++ problems? In-Reply-To: <20000326123439.C86753@dragon.nuxi.com> References: <3.0.32.20000326131248.03413770@mail.vt.edu> <20000326123439.C86753@dragon.nuxi.com> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14558.54055.418869.734754@grasshopper.cs.duke.edu> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org David O'Brien writes: > On Sun, Mar 26, 2000 at 01:12:49PM -0500, nm wrote: > > Are there problems with g++ on 4.0-RELEASE? > > I tried a simple hello world program, but I get > > unaligned access's out the wazoo. > > This has happened for as long as I've tired hello.cxx on 4-CURRENT (which > hasn't been very long that I've done this test). Do you know if there > was some point in the past where this wasn't happening? > > Using printf() instead of I/O streams w/G++ gives the same. Using gcc on > the same hello.c doesn't. I suspect this has something to do with the rtld process, as the addresses (0x1600baf84...) are in the range which is typically used by ld-elf. Also, if one links binaries statically (-static), the problem seems to go away. Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sun Mar 26 22:17:50 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from mail.calyx.net (mail.calyx.net [208.132.136.19]) by hub.freebsd.org (Postfix) with SMTP id 37F8637BB56 for ; Sun, 26 Mar 2000 22:17:45 -0800 (PST) (envelope-from lists@mojo.calyx.net) Received: (qmail 10600 invoked from network); 27 Mar 2000 06:17:43 -0000 Received: from mojo.calyx.net (HELO mojo) (o9m7hupgk7odmqtatwp9@208.132.136.2) by mail.calyx.net with SMTP; 27 Mar 2000 06:17:43 -0000 Date: Mon, 27 Mar 2000 01:17:42 -0500 (EST) From: Nicholas Merrill To: alpha@freebsd.org Subject: problems compiling kernel with bktr0 support: barf @ 'linking kernel' stage 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 Hey all I am running 4.0-CURRENT on a 164sx 533mhz board. I am trying to compile a kernel with bt848 (bktr0) support. I first took my working, custom kernel config file, and added the lines: device bktr0 device iicbus0 device iicbb0 device smbus0 Next I tried to compile the kernel. I got a complaint of two missing files named ioctl_bt848.h and ioctl_meteor.h. So I copied those over from the proper i386 include directory to the alpha dir. Then that error stopped, and the compile seemed to almost finish. But near the end, when it gets to 'linking kernel' it barfed. Has anyone got any clue what I'm doing wrong? I found no mention of this in any recent mailing list traffic. Here is my dmesg output, and then the output of the kernel 'make' --------------------BEGIN DMESG-------------------- Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #1: Thu Mar 16 07:43:57 EST 2000 root@hostname.domain.com:/usr/src/sys/compile/HOSTNAME EB164 Digital AlphaPC 164SX 533 MHz, 531MHz 8192 byte page size, 1 processor. CPU: PCA56 (21164PC) major=9 minor=2 extensions=0x1 OSF PAL rev: 0x1000600020116 real memory = 266485760 (260240K bytes) avail memory = 255598592 (249608K bytes) Preloaded elf kernel "kernel" at 0xfffffc00005ae000. cia0: Pyxis, pass 1 cia0: extended capabilities: 1 pcib0: <2117x PCI host bus adapter> on cia0 pci0: on pcib0 pci0: (vendor=0x109e, dev=0x0350) at 5.0 irq 9 pci0: at 6.0 irq 11 de0: port 0x10100-0x1017f mem 0x82871100-0x8287117f irq 10 at device 7.0 on pci0 de0: interrupting at CIA irq 10 de0: 21140A [10-100Mb/s] pass 2.2 de0: address 00:c0:f0:1f:77:5d de0: enabling 100baseTX port de0: driver is using old-style compatability shims isab0: at device 8.0 on pci0 isa0: on isab0 atapci0: port 0x10180-0x1018f,0x3f4-0x3f7,0x1f0-0x1f7 at device 8.1 on pci0 atapci1: port 0x374-0x377,0x170-0x177 at device 8.2 on pci0 atapci1: Busmastering DMA not supported pci0: at 8.3 sym0: <810a> port 0x10000-0x100ff mem 0x82871000-0x828710ff irq 8 at device 9.0 on pci0 sym0: Symbios NVRAM, ID 7, Fast-10, SE, parity checking sym0: open drain IRQ line driver sym0: interrupting at CIA irq 8 fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: interrupting at ISA irq 6 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: at port 0x60-0x6f on isa0 atkbd0: irq 1 on atkbdc0 atkbd0: interrupting at ISA irq 1 vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> mcclock0: at port 0x70-0x71 on isa0 sio0 at port 0x3f8-0x3ff irq 4 on isa0 sio0: type 16550A sio0: interrupting at ISA irq 4 sio1: reserved for low-level i/o Timecounter "alpha" frequency 533171008 Hz IP Filter: initialized. Default = pass all, Logging = enabled IP Filter: v3.3.8 Waiting 15 seconds for SCSI devices to settle (noperiph:sym0:0:-1:-1): SCSI BUS reset delivered. Mounting root from ufs:/dev/da0a da0 at sym0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 10.000MB/s transfers (10.000MHz, offset 8), Tagged Queueing Enabled da0: 2050MB (4199760 512 byte sectors: 255H 63S/T 261C) de0: enabling 10baseT port de0: enabling Full Duplex 10baseT port IP Filter: already initialized --------------------END OF DMESG-------------------- --------------------BEGIN KERNEL 'MAKE' OUTPUT-------------------- touch hack.c cc -elf -shared -nostdlib hack.c -o hack.So rm -f hack.c building __divqu.S from ../../alpha/alpha/divrem.m4 cc -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I/usr/include -D_KERNEL -include opt_global.h -elf -mno-fp-regs -Wa,-mev56 -c __divqu.S building __divq.S from ../../alpha/alpha/divrem.m4 cc -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I/usr/include -D_KERNEL -include opt_global.h -elf -mno-fp-regs -Wa,-mev56 -c __divq.S building __divlu.S from ../../alpha/alpha/divrem.m4 cc -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I/usr/include -D_KERNEL -include opt_global.h -elf -mno-fp-regs -Wa,-mev56 -c __divlu.S building __divl.S from ../../alpha/alpha/divrem.m4 cc -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I/usr/include -D_KERNEL -include opt_global.h -elf -mno-fp-regs -Wa,-mev56 -c __divl.S building __remqu.S from ../../alpha/alpha/divrem.m4 cc -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I/usr/include -D_KERNEL -include opt_global.h -elf -mno-fp-regs -Wa,-mev56 -c __remqu.S building __remq.S from ../../alpha/alpha/divrem.m4 cc -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I/usr/include -D_KERNEL -include opt_global.h -elf -mno-fp-regs -Wa,-mev56 -c __remq.S building __remlu.S from ../../alpha/alpha/divrem.m4 cc -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I/usr/include -D_KERNEL -include opt_global.h -elf -mno-fp-regs -Wa,-mev56 -c __remlu.S building __reml.S from ../../alpha/alpha/divrem.m4 cc -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I/usr/include -D_KERNEL -include opt_global.h -elf -mno-fp-regs -Wa,-mev56 -c __reml.S sh ../../conf/newvers.sh GENERIC cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I/usr/include -D_KERNEL -include opt_global.h -elf -mno-fp-regs -Wa,-mev56 vers.c linking kernel bktr_core.o: In function `common_ioctl': bktr_core.c(.text+0x38d0): undefined reference to `disable_intr' bktr_core.c(.text+0x38d4): undefined reference to `disable_intr' bktr_core.c(.text+0x38ec): undefined reference to `enable_intr' bktr_core.c(.text+0x38f0): undefined reference to `enable_intr' bktr_os.o: In function `bktr_mmap': bktr_os.c(.text+0x1044): undefined reference to `i386_btop' bktr_os.c(.text+0x1048): undefined reference to `i386_btop' bktr_os.o: In function `bktr_poll': bktr_os.c(.text+0x10f0): undefined reference to `disable_intr' bktr_os.c(.text+0x10f4): undefined reference to `disable_intr' bktr_os.c(.text+0x1158): undefined reference to `enable_intr' bktr_os.c(.text+0x115c): undefined reference to `enable_intr' *** Error code 1 Stop in /usr/src/sys/compile/HOSTNAME. [root@hostname HOSTNAME]# --------------------END KERNEL 'MAKE' OUTPUT-------------------- Thanks! ---------------------------------------------------------------------------- Nicholas Merrill http://www.calyx.net Voice: 212-966-1900 President / CEO http://www.calyx.nl Fax : 212-966-3965 Calyx Internet Access 13 Laight St. NYC, NY 10013 Email: nick@calyx.net ---------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sun Mar 26 22:18:39 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from mail.calyx.net (mail.calyx.net [208.132.136.19]) by hub.freebsd.org (Postfix) with SMTP id A643337B920 for ; Sun, 26 Mar 2000 22:18:34 -0800 (PST) (envelope-from lists@mojo.calyx.net) Received: (qmail 7306 invoked from network); 27 Mar 2000 06:18:34 -0000 Received: from mojo.calyx.net (HELO mojo) (o2csqpydhse5euh53ya7@208.132.136.2) by mail.calyx.net with SMTP; 27 Mar 2000 06:18:34 -0000 Date: Mon, 27 Mar 2000 01:18:33 -0500 (EST) From: Nicholas Merrill To: freebsd-alpha@freebsd.org Subject: problems compiling kernel with bktr0 support: barf @ 'linking kernel' stage 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 Hey all I am running 4.0-CURRENT on a 164sx 533mhz board. I am trying to compile a kernel with bt848 (bktr0) support. I first took my working, custom kernel config file, and added the lines: device bktr0 device iicbus0 device iicbb0 device smbus0 Next I tried to compile the kernel. I got a complaint of two missing files named ioctl_bt848.h and ioctl_meteor.h. So I copied those over from the proper i386 include directory to the alpha dir. Then that error stopped, and the compile seemed to almost finish. But near the end, when it gets to 'linking kernel' it barfed. Has anyone got any clue what I'm doing wrong? I found no mention of this in any recent mailing list traffic. Here is my dmesg output, and then the output of the kernel 'make' --------------------BEGIN DMESG-------------------- Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #1: Thu Mar 16 07:43:57 EST 2000 root@hostname.domain.com:/usr/src/sys/compile/HOSTNAME EB164 Digital AlphaPC 164SX 533 MHz, 531MHz 8192 byte page size, 1 processor. CPU: PCA56 (21164PC) major=9 minor=2 extensions=0x1 OSF PAL rev: 0x1000600020116 real memory = 266485760 (260240K bytes) avail memory = 255598592 (249608K bytes) Preloaded elf kernel "kernel" at 0xfffffc00005ae000. cia0: Pyxis, pass 1 cia0: extended capabilities: 1 pcib0: <2117x PCI host bus adapter> on cia0 pci0: on pcib0 pci0: (vendor=0x109e, dev=0x0350) at 5.0 irq 9 pci0: at 6.0 irq 11 de0: port 0x10100-0x1017f mem 0x82871100-0x8287117f irq 10 at device 7.0 on pci0 de0: interrupting at CIA irq 10 de0: 21140A [10-100Mb/s] pass 2.2 de0: address 00:c0:f0:1f:77:5d de0: enabling 100baseTX port de0: driver is using old-style compatability shims isab0: at device 8.0 on pci0 isa0: on isab0 atapci0: port 0x10180-0x1018f,0x3f4-0x3f7,0x1f0-0x1f7 at device 8.1 on pci0 atapci1: port 0x374-0x377,0x170-0x177 at device 8.2 on pci0 atapci1: Busmastering DMA not supported pci0: at 8.3 sym0: <810a> port 0x10000-0x100ff mem 0x82871000-0x828710ff irq 8 at device 9.0 on pci0 sym0: Symbios NVRAM, ID 7, Fast-10, SE, parity checking sym0: open drain IRQ line driver sym0: interrupting at CIA irq 8 fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: interrupting at ISA irq 6 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: at port 0x60-0x6f on isa0 atkbd0: irq 1 on atkbdc0 atkbd0: interrupting at ISA irq 1 vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> mcclock0: at port 0x70-0x71 on isa0 sio0 at port 0x3f8-0x3ff irq 4 on isa0 sio0: type 16550A sio0: interrupting at ISA irq 4 sio1: reserved for low-level i/o Timecounter "alpha" frequency 533171008 Hz IP Filter: initialized. Default = pass all, Logging = enabled IP Filter: v3.3.8 Waiting 15 seconds for SCSI devices to settle (noperiph:sym0:0:-1:-1): SCSI BUS reset delivered. Mounting root from ufs:/dev/da0a da0 at sym0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 10.000MB/s transfers (10.000MHz, offset 8), Tagged Queueing Enabled da0: 2050MB (4199760 512 byte sectors: 255H 63S/T 261C) de0: enabling 10baseT port de0: enabling Full Duplex 10baseT port IP Filter: already initialized --------------------END OF DMESG-------------------- --------------------BEGIN KERNEL 'MAKE' OUTPUT-------------------- touch hack.c cc -elf -shared -nostdlib hack.c -o hack.So rm -f hack.c building __divqu.S from ../../alpha/alpha/divrem.m4 cc -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I/usr/include -D_KERNEL -include opt_global.h -elf -mno-fp-regs -Wa,-mev56 -c __divqu.S building __divq.S from ../../alpha/alpha/divrem.m4 cc -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I/usr/include -D_KERNEL -include opt_global.h -elf -mno-fp-regs -Wa,-mev56 -c __divq.S building __divlu.S from ../../alpha/alpha/divrem.m4 cc -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I/usr/include -D_KERNEL -include opt_global.h -elf -mno-fp-regs -Wa,-mev56 -c __divlu.S building __divl.S from ../../alpha/alpha/divrem.m4 cc -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I/usr/include -D_KERNEL -include opt_global.h -elf -mno-fp-regs -Wa,-mev56 -c __divl.S building __remqu.S from ../../alpha/alpha/divrem.m4 cc -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I/usr/include -D_KERNEL -include opt_global.h -elf -mno-fp-regs -Wa,-mev56 -c __remqu.S building __remq.S from ../../alpha/alpha/divrem.m4 cc -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I/usr/include -D_KERNEL -include opt_global.h -elf -mno-fp-regs -Wa,-mev56 -c __remq.S building __remlu.S from ../../alpha/alpha/divrem.m4 cc -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I/usr/include -D_KERNEL -include opt_global.h -elf -mno-fp-regs -Wa,-mev56 -c __remlu.S building __reml.S from ../../alpha/alpha/divrem.m4 cc -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I/usr/include -D_KERNEL -include opt_global.h -elf -mno-fp-regs -Wa,-mev56 -c __reml.S sh ../../conf/newvers.sh GENERIC cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I/usr/include -D_KERNEL -include opt_global.h -elf -mno-fp-regs -Wa,-mev56 vers.c linking kernel bktr_core.o: In function `common_ioctl': bktr_core.c(.text+0x38d0): undefined reference to `disable_intr' bktr_core.c(.text+0x38d4): undefined reference to `disable_intr' bktr_core.c(.text+0x38ec): undefined reference to `enable_intr' bktr_core.c(.text+0x38f0): undefined reference to `enable_intr' bktr_os.o: In function `bktr_mmap': bktr_os.c(.text+0x1044): undefined reference to `i386_btop' bktr_os.c(.text+0x1048): undefined reference to `i386_btop' bktr_os.o: In function `bktr_poll': bktr_os.c(.text+0x10f0): undefined reference to `disable_intr' bktr_os.c(.text+0x10f4): undefined reference to `disable_intr' bktr_os.c(.text+0x1158): undefined reference to `enable_intr' bktr_os.c(.text+0x115c): undefined reference to `enable_intr' *** Error code 1 Stop in /usr/src/sys/compile/HOSTNAME. [root@hostname HOSTNAME]# --------------------END KERNEL 'MAKE' OUTPUT-------------------- Thanks! ---------------------------------------------------------------------------- Nicholas Merrill http://www.calyx.net Voice: 212-966-1900 President / CEO http://www.calyx.nl Fax : 212-966-3965 Calyx Internet Access 13 Laight St. NYC, NY 10013 Email: nick@calyx.net ---------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Mar 27 8:16: 9 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from brak.fuzzfactor.com (cc922847-b.hwrd1.md.home.com [24.13.114.72]) by hub.freebsd.org (Postfix) with ESMTP id A1A3237B7C9 for ; Mon, 27 Mar 2000 08:16:03 -0800 (PST) (envelope-from rharris@brak.fuzzfactor.com) Received: from localhost (localhost [[UNIX: localhost]]) by brak.fuzzfactor.com (8.8.8/8.8.8) with ESMTP id LAA04005 for ; Mon, 27 Mar 2000 11:16:01 -0500 (EST) Date: Mon, 27 Mar 2000 11:16:01 -0500 (EST) From: Rob Harris To: freebsd-alpha@freebsd.org Subject: FD_SET resolved in 4.0? 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 Was the 64-bit FD_SET problem (raised in an email from marian@bile.skycache.com roughly around 18 Feb) ever resolved in the release of 4.0? -=[ Rob ]=- _____________________________________________________________________________ "Tax dollars and miracles can let the wierdest people date." --Blues Traveler To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Mar 27 12:37:46 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from mail.cybcon.com (mail.cybcon.com [216.190.188.5]) by hub.freebsd.org (Postfix) with ESMTP id DBD8537BA2D; Mon, 27 Mar 2000 12:37:38 -0800 (PST) (envelope-from wwoods@cybcon.com) Received: from laptop.cybcon.com (william@tc1-16.cybcon.com [63.163.56.17]) by mail.cybcon.com (8.9.3/8.9.3) with ESMTP id MAA17701; Mon, 27 Mar 2000 12:38:36 -0800 (PST) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Mon, 27 Mar 2000 12:37:27 -0800 (PST) Reply-To: bwoods2@uswest.net From: William Woods To: freebsd-questions@freebsd.org, freebsd-alpha@freebsd.org Subject: Mke World Dies on 4.0-stable... Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Doing a make world on a DEC Alpha 200 4/233 running FreeBSD 4.0-STABLE #2: Sat Mar 25 08:43:15 PST 2000 , this is whatr I get: ____________________________________ mkdep -f .depend -a -nostdinc -D_KERNEL -DKLD_MODULE -I- -I. -I@ -I@/../include -I/usr/obj/usr/src/alpha/usr/include /usr/src/sys/modules/joy/../../isa/joy.c ===> sys/modules/kernfs @ -> /usr/src/sys machine -> /usr/src/sys/alpha/include perl @/kern/vnode_if.pl -h @/kern/vnode_if.src rm -f .depend mkdep -f .depend -a -nostdinc -D_KERNEL -DKLD_MODULE -I- -I. -I@ -I@/../include -I/usr/obj/usr/src/alpha/usr/include /usr/src/sys/modules/kernfs/../../miscfs/kernfs/kernfs_vfsops.c /usr/src/sys/modules/kernfs/../../miscfs/kernfs/kernfs_vnops.c ===> sys/modules/kue @ -> /usr/src/sys machine -> /usr/src/sys/alpha/include touch opt_bdg.h touch opt_usb.h perl @/kern/makedevops.pl -h @/kern/device_if.m perl @/kern/makedevops.pl -h @/kern/bus_if.m perl @/kern/makedevops.pl -h @/dev/mii/miibus_if.m rm -f .depend mkdep -f .depend -a -nostdinc -D_KERNEL -DKLD_MODULE -I- -I. -I@ -I@/../include -I/usr/obj/usr/src/alpha/usr/include /usr/src/sys/modules/kue/../../dev/usb/if_kue.c ===> sys/modules/linprocfs @ -> /usr/src/sys machine -> /usr/src/sys/alpha/include perl @/kern/vnode_if.pl -h @/kern/vnode_if.src rm -f .depend mkdep -f .depend -a -nostdinc -DLINPROCFS -D_KERNEL -DKLD_MODULE -I- -I. -I@ -I@/../include -I/usr/obj/usr/src/alpha/usr/include /usr/src/sys/modules/linprocfs/../../miscfs/linprocfs/linprocfs_misc.c /usr/src/sys/modules/linprocfs/../../miscfs/linprocfs/linprocfs_subr.c /usr/src/sys/modules/linprocfs/../../miscfs/linprocfs/linprocfs_vfsops.c /usr/src/sys/modules/linprocfs/../../miscfs/linprocfs/linprocfs_vnops.c /usr/src/sys/modules/linprocfs/../../miscfs/linprocfs/linprocfs_misc.c:61: machine/cputypes.h: No such file or directory mkdep: compile failed *** Error code 1 Stop in /usr/src/sys/modules/linprocfs. *** Error code 1 Stop in /usr/src/sys/modules. *** Error code 1 Stop in /usr/src/sys. *** Error code 1 Stop in /usr/src. *** Error code 1 --------------------------- any ideas for me here? ---------------------------------- E-Mail: bwoods2@uswest.net Date: 27-Mar-00 Time: 12:34:56l ---------------------------------- NOTICE TO BULK E-MAILERS: Pursuant to US Code, Title 47, Chapter 5, Subchapter II, 227, and all unsolicited commercial e-mail sent to this address is subject to a download and archival fee in the amount of $500 US To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Mar 27 14:16:50 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from finch-post-11.mail.demon.net (finch-post-11.mail.demon.net [194.217.242.39]) by hub.freebsd.org (Postfix) with ESMTP id 27AC337B5F0 for ; Mon, 27 Mar 2000 14:16:41 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from nlsys.demon.co.uk ([158.152.125.33] helo=herring.nlsystems.com) by finch-post-11.mail.demon.net with esmtp (Exim 2.12 #1) id 12Zhms-0003et-0B; Mon, 27 Mar 2000 22:15:06 +0000 Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id XAA29786; Mon, 27 Mar 2000 23:18:25 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Mon, 27 Mar 2000 23:21:56 +0100 (BST) From: Doug Rabson To: Rob Harris Cc: freebsd-alpha@freebsd.org Subject: Re: FD_SET resolved in 4.0? In-Reply-To: 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 Mon, 27 Mar 2000, Rob Harris wrote: > > Was the 64-bit FD_SET problem (raised in an email from > marian@bile.skycache.com roughly around 18 Feb) ever resolved in the > release of 4.0? Yes it was. The bug should be fixed in 4.0-RELEASE. -- 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 From owner-freebsd-alpha Mon Mar 27 21:29: 0 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 01E8C37B9BE; Mon, 27 Mar 2000 21:28:58 -0800 (PST) (envelope-from jkoshy@FreeBSD.org) Received: (from jkoshy@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id VAA39537; Mon, 27 Mar 2000 21:28:57 -0800 (PST) (envelope-from jkoshy@FreeBSD.org) Date: Mon, 27 Mar 2000 21:28:57 -0800 (PST) From: Message-Id: <200003280528.VAA39537@freefall.freebsd.org> X-Mailer: exmh version 2.0.2 2/24/98 To: alpha@FreeBSD.org Cc: obrien@FreeBSD.org (GCC maintainer) Subject: Cross building Alpha on an i386 Mime-Version: 1.0 Content-Type: text/plain Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I can't seem to find a prior message in the mailing lists about this problem. A cross build with MACHINE_ARCH=alpha on a FreeBSD/x86 system fails: foobar# make MACHINE_ARCH=alpha buildworld [output elided] cc -O -pipe -I/home/src-current/lib/libmd -I/home/obj-current/alpha/home/s rc-current/i386/usr/include -c /home/src-current/lib/libmd/md2c.c -o md2c.o /home/src-current/lib/libmd/md2c.c: In function `MD2Final': /home/src-current/lib/libmd/md2c.c:167: internal error--unrecognizable ins n: (insn 26 24 28 (set (reg:DI 79) (and:DI (plus:DI (reg/v:DI 69) (const_int 586267588705834800 [0x822d7440822d730])) (const_int -8 [0xfffffffffffffff8]))) -1 (insn_list 4 (nil)) (nil)) *** Error code 1 Building with -O0 goes further, but not far enough: cc -pipe -Wall -DLIBC_SCCS -I/home/src-current/lib/libutil -I/home/src-cur rent/lib/libutil/../../sys -DINET6 -I/home/obj-current/alpha/home/src-current/i3 86/usr/include -c /home/src-current/lib/libutil/pty.c -o pty.o^M /home/src-current/lib/libutil/pty.c: In function `openpty':^M /home/src-current/lib/libutil/pty.c:63: Internal compiler error in `alpha_ expand_unaligned_load', at config/alpha/alpha.c:1617^M Please submit a full bug report.^M See for instructions.^M *** Error code 1^M ^M The offending line in "libutil/pty.c" has the following code: char line[] = "/dev/ptyXX"; In fact, the following 1 liner program demonstrates the problem too. foobar% cat /tmp/a.c int main() { char line[] = "/dev/ptyXX"; } And here is the compiler `cc -v' output: ob47191% /home/obj-current/alpha/home/src-current/i386/usr/bin/cc -v -B/home/obj-current/alpha/home/src-current/i386/usr/libexec/ /tmp/a.c Using builtin specs. gcc version 2.95.2 19991024 (release) /home/obj-current/alpha/home/src-current/i386/usr/libexec/cpp -lang-c -v -isystem /home/obj-current/alpha/home/src-current/i386/usr/libexec/include -D__GNUC__=2 -D__GNUC_MINOR__=95 -D__alpha__ -D__alpha -Dunix -D__FreeBSD__=5 -D__FreeBSD_cc_version=500001 -D__alpha__ -D__alpha -D__unix__ -D__FreeBSD__=5 -D__FreeBSD_cc_version=500001 -D__unix -Acpu(alpha) -Amachine(alpha) -Asystem(unix) -Asystem(FreeBSD) -Acpu(alpha) -Amachine(alpha) -D__alpha -D__alpha__ -D__alpha_ev4__ -Acpu(ev4) -D__ELF__ /tmp/a.c /tmp/ccTyb436.i GNU CPP version 2.95.2 19991024 (release) (FreeBSD/Alpha ELF) #include "..." search starts here: #include <...> search starts here: /home/obj-current/alpha/home/src-current/i386/usr/include /home/obj-current/alpha/home/src-current/i386/usr/include End of search list. The following default directories have been omitted from the search path: /home/obj-current/alpha/home/src-current/i386/usr/include/g++ End of omitted list. /home/obj-current/alpha/home/src-current/i386/usr/libexec/cc1 /tmp/ccTyb436.i -quiet -dumpbase a.c -version -o /tmp/ccfZO436.s GNU C version 2.95.2 19991024 (release) (alpha-unknown-freebsd) compiled by GNU C version 2.7.2.3. /tmp/a.c: In function `main': /tmp/a.c:1: Internal compiler error in `alpha_expand_unaligned_load', at config/alpha/alpha.c:1617 Please submit a full bug report. See for instructions. The source tree being built is -current as of yesterday. Any suggestions on getting a cross world build to work? Koshy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Mar 28 4:40: 5 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 55FEF37BFDE for ; Tue, 28 Mar 2000 04:40:01 -0800 (PST) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id EAA22330; Tue, 28 Mar 2000 04:40:01 -0800 (PST) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 04D7137B6BA for ; Tue, 28 Mar 2000 04:30:30 -0800 (PST) (envelope-from nobody@FreeBSD.org) Received: (from nobody@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id EAA20843; Tue, 28 Mar 2000 04:30:29 -0800 (PST) (envelope-from nobody@FreeBSD.org) Message-Id: <200003281230.EAA20843@freefall.freebsd.org> Date: Tue, 28 Mar 2000 04:30:29 -0800 (PST) From: lindroos@nls.fi To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-1.0 Subject: alpha/17637: misconfigured syscons bell causes panic on alpha Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Number: 17637 >Category: alpha >Synopsis: misconfigured syscons bell causes panic on alpha >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-alpha >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Tue Mar 28 04:40:00 PST 2000 >Closed-Date: >Last-Modified: >Originator: Dennis Lindroos >Release: FreeBSD 4.0-RELEASE >Organization: >Environment: FreeBSD bag.nls.fi 4.0-RELEASE FreeBSD 4.0-RELEASE #0: Thu Mar 23 21:36:50 EET 2000 root@bag.nls.fi:/usr/src/sys/compile/NLS alpha >Description: If the syscons bell pitch is set to zero, then any terminal bell will cause a system panic. >How-To-Repeat: kbdcontrol -b 0.0 perl -e 'print chr(7)' >Fix: >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Mar 28 9: 0: 6 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 52F9F37BFC9 for ; Tue, 28 Mar 2000 09:00:03 -0800 (PST) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id JAA29364; Tue, 28 Mar 2000 09:00:02 -0800 (PST) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 84E2C37BFDE for ; Tue, 28 Mar 2000 08:52:05 -0800 (PST) (envelope-from nobody@FreeBSD.org) Received: (from nobody@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id IAA28357; Tue, 28 Mar 2000 08:52:05 -0800 (PST) (envelope-from nobody@FreeBSD.org) Message-Id: <200003281652.IAA28357@freefall.freebsd.org> Date: Tue, 28 Mar 2000 08:52:05 -0800 (PST) From: dkleinh@phy.ucsf.edu To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-1.0 Subject: alpha/17642: FreeBSD/alpha 4.0 RELEASE installation fails with cant find init Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Number: 17642 >Category: alpha >Synopsis: FreeBSD/alpha 4.0 RELEASE installation fails with cant find init >Confidential: no >Severity: critical >Priority: high >Responsible: freebsd-alpha >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Tue Mar 28 09:00:01 PST 2000 >Closed-Date: >Last-Modified: >Originator: Dirk Kleinhesselink >Release: 4.0 RELEASE >Organization: >Environment: NA >Description: 4.0/alpha RELEASE fails at install after kernel load/mfsroot load with the error: can't find my init, going nowhere CPU panic >How-To-Repeat: Try to install the OS, either by booting the CD or with the two install floppies. >Fix: >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Mar 28 9:20: 5 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id A4E8937C058 for ; Tue, 28 Mar 2000 09:20:03 -0800 (PST) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id JAA32270; Tue, 28 Mar 2000 09:20:03 -0800 (PST) (envelope-from gnats@FreeBSD.org) Date: Tue, 28 Mar 2000 09:20:03 -0800 (PST) Message-Id: <200003281720.JAA32270@freefall.freebsd.org> To: freebsd-alpha@freebsd.org Cc: From: Bosko Milekic Subject: Re: alpha/17637: misconfigured syscons bell causes panic on alpha Reply-To: Bosko Milekic Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR alpha/17637; it has been noted by GNATS. From: Bosko Milekic To: lindroos@nls.fi Cc: FreeBSD-gnats-submit@FreeBSD.ORG Subject: Re: alpha/17637: misconfigured syscons bell causes panic on alpha Date: Tue, 28 Mar 2000 12:19:23 -0500 (EST) Hi, It appears that the alpha's sysbeep() does a TIMER_DIV() on the given pitch, which could cause problems if the pitch is 0. Please try the following patch and let me know if it works: http://pages.infinit.net/bmilekic/code/diffs/alpha.beep.patch .......................................................................... Bosko Milekic * bmilekic@dsuper.net * http://pages.infinit.net/bmilekic/ Montreal, Quebec, Canada. * Technokratis: http://www.technokratis.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Mar 28 11:51:11 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from ef.egroups.com (ef.egroups.com [207.138.41.172]) by hub.freebsd.org (Postfix) with SMTP id E2C1637BF60 for ; Tue, 28 Mar 2000 11:50:46 -0800 (PST) (envelope-from kmail@dolphinsearch.com) X-eGroups-Return: kmail@dolphinsearch.com Received: from [10.1.2.26] by ef.egroups.com with NNFMP; 28 Mar 2000 19:50:28 -0000 Date: Tue, 28 Mar 2000 11:50:25 -0800 From: "Kelly" To: freebsd-alpha@freebsd.org Subject: Install Prolem Message-ID: <8br2e1$dcgi@eGroups.com> User-Agent: eGroups-EW/0.82 Content-Length: 448 X-Mailer: eGroups Message Poster Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Ok. I download the ISO Image of version 4.0 for alpha, burned the disk, and then installed the software. The install works fine. Once the install is done, I select "Exit Install," takes me back to SRM console. Then type boot dka0, but once the system come backup it takes me right back to the install application, and not to a logon. I have tried the install from ftp with the same problem. I am tring to install on a DS10. Any Help? Kelly To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Mar 28 12: 8:30 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from mail.cybcon.com (mail.cybcon.com [216.190.188.5]) by hub.freebsd.org (Postfix) with ESMTP id 7AA1137C050 for ; Tue, 28 Mar 2000 12:08:26 -0800 (PST) (envelope-from wwoods@cybcon.com) Received: from laptop.cybcon.com (william@tc2-38.cybcon.com [63.163.56.103]) by mail.cybcon.com (8.9.3/8.9.3) with ESMTP id MAA29383 for ; Tue, 28 Mar 2000 12:09:30 -0800 (PST) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Tue, 28 Mar 2000 12:08:21 -0800 (PST) Reply-To: bwoods2@uswest.net From: William Woods To: freebsd-alpha@freebsd.org Subject: Alpha make world dies at /usr/src/sys/modules/linprocfs. Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Running FreeBSD 4.0-STABLE #2: Sat Mar 25 08:43:15 PST 2000 on a DEC Alpha 200 4/233, doing a make world with todays cvsup I get: ---------------------------------- @ -> /usr/src/sys machine -> /usr/src/sys/alpha/include perl @/kern/vnode_if.pl -h @/kern/vnode_if.src rm -f .depend mkdep -f .depend -a -nostdinc -D_KERNEL -DKLD_MODULE -I- -I. -I@ -I@/../include -I/usr/obj/usr/src/alpha/usr/include /usr/src/sys/modules/kernfs/../../miscfs/kernfs/kernfs_vfsops.c /usr/src/sys/modules/kernfs/../../miscfs/kernfs/kernfs_vnops.c ===> sys/modules/kue @ -> /usr/src/sys machine -> /usr/src/sys/alpha/include touch opt_bdg.h touch opt_usb.h perl @/kern/makedevops.pl -h @/kern/device_if.m perl @/kern/makedevops.pl -h @/kern/bus_if.m perl @/kern/makedevops.pl -h @/dev/mii/miibus_if.m rm -f .depend mkdep -f .depend -a -nostdinc -D_KERNEL -DKLD_MODULE -I- -I. -I@ -I@/../include -I/usr/obj/usr/src/alpha/usr/include /usr/src/sys/modules/kue/../../dev/usb/if_kue.c ===> sys/modules/linprocfs @ -> /usr/src/sys machine -> /usr/src/sys/alpha/include perl @/kern/vnode_if.pl -h @/kern/vnode_if.src rm -f .depend mkdep -f .depend -a -nostdinc -DLINPROCFS -D_KERNEL -DKLD_MODULE -I- -I. -I@ -I@/../include -I/usr/obj/usr/src/alpha/usr/include /usr/src/sys/modules/linprocfs/../../miscfs/linprocfs/linprocfs_misc.c /usr/src/sys/modules/linprocfs/../../miscfs/linprocfs/linprocfs_subr.c /usr/src/sys/modules/linprocfs/../../miscfs/linprocfs/linprocfs_vfsops.c /usr/src/sys/modules/linprocfs/../../miscfs/linprocfs/linprocfs_vnops.c /usr/src/sys/modules/linprocfs/../../miscfs/linprocfs/linprocfs_misc.c:61: machine/cputypes.h: No such file or directory mkdep: compile failed *** Error code 1 Stop in /usr/src/sys/modules/linprocfs. *** Error code 1 Stop in /usr/src/sys/modules. *** Error code 1 Stop in /usr/src/sys. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 ---------------------------------------------------- Ideas or fixes for me? ---------------------------------- E-Mail: bwoods2@uswest.net Date: 28-Mar-00 Time: 12:04:04l ---------------------------------- NOTICE TO BULK E-MAILERS: Pursuant to US Code, Title 47, Chapter 5, Subchapter II, 227, and all unsolicited commercial e-mail sent to this address is subject to a download and archival fee in the amount of $500 US To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Mar 28 15:30:35 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id B01C537B507 for ; Tue, 28 Mar 2000 15:30:32 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id SAA22914; Tue, 28 Mar 2000 18:30:29 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id SAA25199; Tue, 28 Mar 2000 18:29:59 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Tue, 28 Mar 2000 18:29:59 -0500 (EST) To: "Kelly" Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: Install Prolem In-Reply-To: <8br2e1$dcgi@eGroups.com> References: <8br2e1$dcgi@eGroups.com> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14561.16371.543191.7615@grasshopper.cs.duke.edu> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Kelly writes: > Ok. I download the ISO Image of version 4.0 for alpha, burned the > disk, and then installed the software. The install works fine. Once > the install is done, I select "Exit Install," takes me back to SRM > console. Then type boot dka0, but once the system come backup it takes > me right back to the install application, and not to a logon. > > I have tried the install from ftp with the same problem. I am tring to > install on a DS10. I think I saw something like this on my AS200. I think the previous boot device may be sticking in the SRM console & you're booting from the CD again. Try this: When you exit from sysinstall, type 'init' at the srm console prompt (>>>), then boot. (or powercycle the box). Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Mar 28 16:44: 2 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from ptldpop1.ptld.uswest.net (ptldpop1.ptld.uswest.net [198.36.160.1]) by hub.freebsd.org (Postfix) with SMTP id E84C137BAF0 for ; Tue, 28 Mar 2000 16:43:54 -0800 (PST) (envelope-from wwoods@cybcon.com) Received: (qmail 29489 invoked by alias); 29 Mar 2000 00:43:52 -0000 Delivered-To: fixup-freebsd-alpha@freebsd.org@fixme Received: (qmail 29478 invoked by uid 0); 29 Mar 2000 00:43:51 -0000 Received: from unknown (HELO laptop.cybcon.com) (63.227.213.90) by ptldpop1.ptld.uswest.net with SMTP; 29 Mar 2000 00:43:51 -0000 Content-Length: 2359 Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Tue, 28 Mar 2000 16:43:50 -0800 (PST) Reply-To: bwoods2@uswest.net From: William Woods To: freebsd-alpha@freebsd.org Subject: Alpha make world dies at /usr/src/sys/modules/linprocfs. Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Running FreeBSD 4.0-STABLE #2: Sat Mar 25 08:43:15 PST 2000 on a DEC Alpha 200 4/233, doing a make world with todays cvsup I get: ---------------------------------- @ -> /usr/src/sys machine -> /usr/src/sys/alpha/include perl @/kern/vnode_if.pl -h @/kern/vnode_if.src rm -f .depend mkdep -f .depend -a -nostdinc -D_KERNEL -DKLD_MODULE -I- -I. -I@ -I@/../include -I/usr/obj/usr/src/alpha/usr/include /usr/src/sys/modules/kernfs/../../miscfs/kernfs/kernfs_vfsops.c /usr/src/sys/modules/kernfs/../../miscfs/kernfs/kernfs_vnops.c ===> sys/modules/kue @ -> /usr/src/sys machine -> /usr/src/sys/alpha/include touch opt_bdg.h touch opt_usb.h perl @/kern/makedevops.pl -h @/kern/device_if.m perl @/kern/makedevops.pl -h @/kern/bus_if.m perl @/kern/makedevops.pl -h @/dev/mii/miibus_if.m rm -f .depend mkdep -f .depend -a -nostdinc -D_KERNEL -DKLD_MODULE -I- -I. -I@ -I@/../include -I/usr/obj/usr/src/alpha/usr/include /usr/src/sys/modules/kue/../../dev/usb/if_kue.c ===> sys/modules/linprocfs @ -> /usr/src/sys machine -> /usr/src/sys/alpha/include perl @/kern/vnode_if.pl -h @/kern/vnode_if.src rm -f .depend mkdep -f .depend -a -nostdinc -DLINPROCFS -D_KERNEL -DKLD_MODULE -I- -I. -I@ -I@/../include -I/usr/obj/usr/src/alpha/usr/include /usr/src/sys/modules/linprocfs/../../miscfs/linprocfs/linprocfs_misc.c /usr/src/sys/modules/linprocfs/../../miscfs/linprocfs/linprocfs_subr.c /usr/src/sys/modules/linprocfs/../../miscfs/linprocfs/linprocfs_vfsops.c /usr/src/sys/modules/linprocfs/../../miscfs/linprocfs/linprocfs_vnops.c /usr/src/sys/modules/linprocfs/../../miscfs/linprocfs/linprocfs_misc.c:61: machine/cputypes.h: No such file or directory mkdep: compile failed *** Error code 1 Stop in /usr/src/sys/modules/linprocfs. *** Error code 1 Stop in /usr/src/sys/modules. *** Error code 1 Stop in /usr/src/sys. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 ---------------------------------------------------- Ideas or fixes for me? ---------------------------------- E-Mail: bwoods2@uswest.net Date: 28-Mar-00 Time: 12:04:04l ---------------------------------- NOTICE TO BULK E-MAILERS: Pursuant to US Code, Title 47, Chapter 5, Subchapter II, 227, and all unsolicited commercial e-mail sent to this address is subject to a download and archival fee in the amount of $500 US To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Mar 28 19:41:48 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 4EED537B8F8 for ; Tue, 28 Mar 2000 19:41:46 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id TAA12121 for ; Tue, 28 Mar 2000 19:41:45 -0800 (PST) (envelope-from jdp@polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id TAA04823 for alpha@freebsd.org; Tue, 28 Mar 2000 19:41:45 -0800 (PST) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Tue, 28 Mar 2000 19:41:45 -0800 (PST) Organization: Polstra & Co., Inc. From: John Polstra To: alpha@freebsd.org Subject: Dual boot FreeBSD + OSF1? Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Is it feasible to set up an Alpha box for dual boot with FreeBSD and OSF1? And if so, what does it take to get a licensed copy of OSF1? Big $$ or little $$? I am looking for a way to generate OSF1 binaries for CVSup locally. John --- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Mar 28 19:47:39 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 24C0537C1B5 for ; Tue, 28 Mar 2000 19:47:34 -0800 (PST) (envelope-from mjacob@feral.com) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id TAA08827; Tue, 28 Mar 2000 19:46:59 -0800 Date: Tue, 28 Mar 2000 19:47:11 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: John Polstra Cc: alpha@FreeBSD.ORG Subject: Re: Dual boot FreeBSD + OSF1? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, 28 Mar 2000, John Polstra wrote: > Is it feasible to set up an Alpha box for dual boot with FreeBSD and > OSF1? Sure, but I'm not sure if the same disk is easily feasible. > And if so, what does it take to get a licensed copy of OSF1? > Big $$ or little $$? It's 99$ for a non-commercial Tru64 licence. >=20 > I am looking for a way to generate OSF1 binaries for CVSup locally. >=20 > John > --- > John Polstra jdp@polstra.= com > John D. Polstra & Co., Inc. Seattle, Washington = USA > "Disappointment is a good sign of basic intelligence." -- Ch=F6gyam Tr= ungpa >=20 >=20 >=20 > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-alpha" in the body of the message >=20 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Mar 28 19:50:56 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from mail4.nycap.rr.com (mail4-1.nyroc.rr.com [24.92.33.20]) by hub.freebsd.org (Postfix) with ESMTP id D23BD37BFDC for ; Tue, 28 Mar 2000 19:50:52 -0800 (PST) (envelope-from morrildl@nycap.rr.com) Received: from cm-24-29-69-57.nycap.rr.com ([24.29.69.57]) by mail4.nycap.rr.com (Post.Office MTA v3.5.3 release 223 ID# 0-59787U250000L250000S0V35) with ESMTP id com for ; Tue, 28 Mar 2000 22:53:35 -0500 Date: Tue, 28 Mar 2000 22:50:12 -0500 (EST) From: Cc: alpha@FreeBSD.ORG Subject: Re: Cross building Alpha on an i386 In-Reply-To: <200003280528.VAA39537@freefall.freebsd.org> 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 Mon, 27 Mar 2000 jkoshy@FreeBSD.ORG wrote: > I can't seem to find a prior message in the mailing lists about this > problem. A cross build with MACHINE_ARCH=alpha on a FreeBSD/x86 system > fails: In the Linux world, the gurus say that you can't cross-build for the Alpha from a 32-bit system with gcc. IIRC (which is unlikely :) it's got something to do with gas not being equipped to deal with 64-bit pointers and instructions on a system with 32-bit registers. (Doing a cross from 64-bit to 32-bit archs works.) My understanding is that this is a gcc/gas thing, and not a Linux thing, so that may be your problem. On the other hand, I'd expect that they built Linux on the Itanium as a cross from IA32, so maybe gcc's been fixed and I'm wrong. Just a possibility... Dan Morrill ...standing ready to be corrected by those who know more. :) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Mar 28 19:59:43 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from mail.rdc1.sdca.home.com (ha1.rdc1.sdca.home.com [24.0.3.66]) by hub.freebsd.org (Postfix) with ESMTP id F04B637B8F8 for ; Tue, 28 Mar 2000 19:59:38 -0800 (PST) (envelope-from craig-burgess@home.net) Received: from home.net ([24.0.178.21]) by mail.rdc1.sdca.home.com (InterMail v4.01.01.00 201-229-111) with ESMTP id <20000329035938.YDDW17125.mail.rdc1.sdca.home.com@home.net>; Tue, 28 Mar 2000 19:59:38 -0800 Message-ID: <38E1809F.5CBA9037@home.net> Date: Tue, 28 Mar 2000 20:03:43 -0800 From: Craig Burgess X-Mailer: Mozilla 4.7 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: morrildl@nycap.rr.com Cc: alpha@FreeBSD.ORG Subject: Re: Cross building Alpha on an i386 References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Would not big-endian / little-endian be of great significance (and a serious hurdle)? Craig in perpetual learning mode -- ... mind like a steel trap: things wander in and get mangled ... morrildl@nycap.rr.com wrote: > > On Mon, 27 Mar 2000 jkoshy@FreeBSD.ORG wrote: > > > I can't seem to find a prior message in the mailing lists about this > > problem. A cross build with MACHINE_ARCH=alpha on a FreeBSD/x86 system > > fails: > > In the Linux world, the gurus say that you can't cross-build for the Alpha > from a 32-bit system with gcc. IIRC (which is unlikely :) it's got something > to do with gas not being equipped to deal with 64-bit pointers and > instructions on a system with 32-bit registers. (Doing a cross from 64-bit > to 32-bit archs works.) > > My understanding is that this is a gcc/gas thing, and not a Linux thing, > so that may be your problem. On the other hand, I'd expect that they built > Linux on the Itanium as a cross from IA32, so maybe gcc's been fixed and > I'm wrong. > > Just a possibility... > > Dan Morrill > ...standing ready to be corrected by those who know more. :) > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Mar 28 22: 3:46 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 5334237BA68 for ; Tue, 28 Mar 2000 22:03:43 -0800 (PST) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id XAA87983; Tue, 28 Mar 2000 23:03:18 -0700 (MST) (envelope-from ken) Date: Tue, 28 Mar 2000 23:03:17 -0700 From: "Kenneth D. Merry" To: Matthew Jacob Cc: John Polstra , alpha@FreeBSD.ORG Subject: Re: Dual boot FreeBSD + OSF1? Message-ID: <20000328230317.A87935@panzer.kdm.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from mjacob@feral.com on Tue, Mar 28, 2000 at 07:47:11PM -0800 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, Mar 28, 2000 at 19:47:11 -0800, Matthew Jacob wrote: > On Tue, 28 Mar 2000, John Polstra wrote: > > > Is it feasible to set up an Alpha box for dual boot with FreeBSD and > > OSF1? > > Sure, but I'm not sure if the same disk is easily feasible. FWIW, it works fine when you have separate disks. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Mar 28 22: 6:41 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 05E9A37B59A for ; Tue, 28 Mar 2000 22:06:40 -0800 (PST) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.9.3/8.9.3) with ESMTP id WAA09278; Tue, 28 Mar 2000 22:06:20 -0800 Date: Tue, 28 Mar 2000 22:06:29 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: "Kenneth D. Merry" Cc: John Polstra , alpha@FreeBSD.ORG Subject: Re: Dual boot FreeBSD + OSF1? In-Reply-To: <20000328230317.A87935@panzer.kdm.org> 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 Uh, sure. On Tue, 28 Mar 2000, Kenneth D. Merry wrote: > On Tue, Mar 28, 2000 at 19:47:11 -0800, Matthew Jacob wrote: > > On Tue, 28 Mar 2000, John Polstra wrote: > > > > > Is it feasible to set up an Alpha box for dual boot with FreeBSD and > > > OSF1? > > > > Sure, but I'm not sure if the same disk is easily feasible. > > FWIW, it works fine when you have separate disks. > > Ken > -- > Kenneth Merry > ken@kdm.org > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Mar 28 22:26: 2 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 0BC8637B5CD for ; Tue, 28 Mar 2000 22:25:59 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id IAA05722; Wed, 29 Mar 2000 08:12:27 +0200 (MET DST) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id HAA56882; Wed, 29 Mar 2000 07:59:26 +0200 (CEST) (envelope-from wilko) Date: Wed, 29 Mar 2000 07:59:25 +0200 From: Wilko Bulte To: John Polstra Cc: alpha@FreeBSD.ORG Subject: Re: Dual boot FreeBSD + OSF1? Message-ID: <20000329075925.A56808@yedi.iaf.nl> Reply-To: wilko@FreeBSD.ORG References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: ; from jdp@polstra.com on Tue, Mar 28, 2000 at 07:41:45PM -0800 X-OS: FreeBSD 3.4-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, Mar 28, 2000 at 07:41:45PM -0800, John Polstra wrote: > Is it feasible to set up an Alpha box for dual boot with FreeBSD and > OSF1? And if so, what does it take to get a licensed copy of OSF1? On 2 seperate disks that works fine. I had one of my Alphas configured this way. Just >>> boot dka0 or >>> boot dka100 to select the right os. > Big $$ or little $$? I think Compaq has a hobbyist license for Tru64 (OSF/1) these days. -- Wilko Bulte Arnhem, The Netherlands http://www.tcja.nl The FreeBSD Project: http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Mar 28 23:20: 5 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id DEADE37C031 for ; Tue, 28 Mar 2000 23:20:02 -0800 (PST) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id XAA02228; Tue, 28 Mar 2000 23:20:02 -0800 (PST) (envelope-from gnats@FreeBSD.org) Date: Tue, 28 Mar 2000 23:20:02 -0800 (PST) Message-Id: <200003290720.XAA02228@freefall.freebsd.org> To: freebsd-alpha@freebsd.org Cc: From: Dennis Lindroos Subject: Re: alpha/17637: misconfigured syscons bell causes panic on alpha Reply-To: Dennis Lindroos Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR alpha/17637; it has been noted by GNATS. From: Dennis Lindroos To: Bosko Milekic Cc: FreeBSD-gnats-submit@FreeBSD.ORG Subject: Re: alpha/17637: misconfigured syscons bell causes panic on alpha Date: Wed, 29 Mar 2000 10:15:35 +0300 (EET DST) Hi On Tue, 28 Mar 2000, Bosko Milekic wrote: > It appears that the alpha's sysbeep() does a TIMER_DIV() on the given > pitch, which could cause problems if the pitch is 0. > Please try the following patch and let me know if it works: > > http://pages.infinit.net/bmilekic/code/diffs/alpha.beep.patch > > > .......................................................................... > Bosko Milekic * bmilekic@dsuper.net * http://pages.infinit.net/bmilekic/ > Montreal, Quebec, Canada. * Technokratis: http://www.technokratis.com/ > Yes. It works, but to turn the bell off completely (without a short tick) i added "if (pitch)" before the "outb(IO_PPI, inb(IO_PPI) | 3);" line. (I know i should use the visual bell instead.. :) Btw. The hardware is an Avanti (AlphaServer 400 4/166). Dennis Lindroos lindroos@nls.fi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Mar 28 23:40: 5 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 40ACD37B6E7 for ; Tue, 28 Mar 2000 23:40:04 -0800 (PST) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id XAA08493; Tue, 28 Mar 2000 23:40:02 -0800 (PST) (envelope-from gnats@FreeBSD.org) Date: Tue, 28 Mar 2000 23:40:02 -0800 (PST) Message-Id: <200003290740.XAA08493@freefall.freebsd.org> To: freebsd-alpha@freebsd.org Cc: From: "Jordan K. Hubbard" Subject: Re: alpha/17642: FreeBSD/alpha 4.0 RELEASE installation fails with cant find init Reply-To: "Jordan K. Hubbard" Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR alpha/17642; it has been noted by GNATS. From: "Jordan K. Hubbard" To: dkleinh@phy.ucsf.edu Cc: freebsd-gnats-submit@FreeBSD.ORG Subject: Re: alpha/17642: FreeBSD/alpha 4.0 RELEASE installation fails with cant find init Date: Tue, 28 Mar 2000 23:39:32 -0800 I can't reproduce this on any of our alpha machines; can you tell me a bit more about the configuration? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Mar 29 4:22:14 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from minmei.iqm.unicamp.br (minmei.iqm.unicamp.br [143.106.51.239]) by hub.freebsd.org (Postfix) with ESMTP id 913BA37BE55 for ; Wed, 29 Mar 2000 04:22:09 -0800 (PST) (envelope-from picapau@minmei.iqm.unicamp.br) Received: by minmei.iqm.unicamp.br (Postfix, from userid 1001) id 6282D133A5; Wed, 29 Mar 2000 09:21:58 -0300 (EST) Date: Wed, 29 Mar 2000 09:21:58 -0300 From: Andre Severo To: Andrew Gallatin Cc: alpha@FreeBSD.ORG Subject: Re: AlphaServer 1000 freezing during installation Message-ID: <20000329092158.A96147@minmei.iqm.unicamp.br> Reply-To: picapau@minmei.iqm.unicamp.br References: <20000325181342.A88910@minmei.iqm.unicamp.br> <14557.27001.718759.711008@grasshopper.cs.duke.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <14557.27001.718759.711008@grasshopper.cs.duke.edu>; from gallatin@cs.duke.edu on Sat, Mar 25, 2000 at 08:37:41PM -0500 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org At Sat, Mar 25, 2000 at 08:37:41PM -0500, Andrew Gallatin claimed that: |> |> Andre Severo writes: |> > Hi, |> > |> > I'm running into some trouble trying to install release 4.0 on |> > an Alpha Server 1000 (SRM V4.8-65): |> > |> > #1. Sometimes the bootstrapping sequence fails to |> > assess the size of some of my hard disks (da1 & da2), |> > sometimes missing all three of them; |> > |> > 2. When I get to the installantion program i can't get past |> > network setup screen: my box freezes and has to be rebooted |> > (i'm installing via NFS) |> |> I'm afraid I cannot help with the disk problem, but I believe there |> may be issues with either the Intel Pro100B or its driver on the |> alphei Do you have another PCI network card you could use? Thanks for the advice. You were right, the Intel Pro100B (or its drivers) seem to have caused the problem - I just put back the old DEC network and now things were running smoothly. The disk problem persists, though - i have to exerc them or else they are taken to be offline. Regards, Andre picapau@minmei.iqm.unicamp.br |> |> Drew |> ------------------------------------------------------------------------------ |> Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin |> Duke University Email: gallatin@cs.duke.edu |> Department of Computer Science Phone: (919) 660-6590 |> To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Mar 29 5:51:45 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 1D4C037C158 for ; Wed, 29 Mar 2000 05:51:43 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id IAA16436; Wed, 29 Mar 2000 08:51:40 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id IAA26427; Wed, 29 Mar 2000 08:51:10 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Wed, 29 Mar 2000 08:51:10 -0500 (EST) To: picapau@minmei.iqm.unicamp.br Cc: alpha@FreeBSD.ORG Subject: Re: AlphaServer 1000 freezing during installation In-Reply-To: <20000329092158.A96147@minmei.iqm.unicamp.br> References: <20000325181342.A88910@minmei.iqm.unicamp.br> <14557.27001.718759.711008@grasshopper.cs.duke.edu> <20000329092158.A96147@minmei.iqm.unicamp.br> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14562.2571.201291.426577@grasshopper.cs.duke.edu> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Andre Severo writes: > > The disk problem persists, though - i have to exerc them or else they > are taken to be offline. I didn't understand that last bit -- can you explain what you mean by "have to exerc them or else they are taken to be offline" ? Thanks, Drew ------------------------------------------------------------------------------ Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin Duke University Email: gallatin@cs.duke.edu Department of Computer Science Phone: (919) 660-6590 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Mar 29 6:18:50 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from minmei.iqm.unicamp.br (minmei.iqm.unicamp.br [143.106.51.239]) by hub.freebsd.org (Postfix) with ESMTP id D202A37B539 for ; Wed, 29 Mar 2000 06:18:46 -0800 (PST) (envelope-from picapau@minmei.iqm.unicamp.br) Received: by minmei.iqm.unicamp.br (Postfix, from userid 1001) id 9F035133A5; Wed, 29 Mar 2000 11:18:36 -0300 (EST) Date: Wed, 29 Mar 2000 11:18:36 -0300 From: Andre Severo To: Andrew Gallatin Cc: alpha@FreeBSD.ORG Subject: Re: AlphaServer 1000 freezing during installation Message-ID: <20000329111836.A10213@minmei.iqm.unicamp.br> Reply-To: picapau@minmei.iqm.unicamp.br References: <20000325181342.A88910@minmei.iqm.unicamp.br> <14557.27001.718759.711008@grasshopper.cs.duke.edu> <20000329092158.A96147@minmei.iqm.unicamp.br> <14562.2571.201291.426577@grasshopper.cs.duke.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <14562.2571.201291.426577@grasshopper.cs.duke.edu>; from gallatin@cs.duke.edu on Wed, Mar 29, 2000 at 08:51:10AM -0500 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org At Wed, Mar 29, 2000 at 08:51:10AM -0500, Andrew Gallatin claimed that: |> |> Andre Severo writes: |> > |> > The disk problem persists, though - i have to exerc them or else they |> > are taken to be offline. |> |> I didn't understand that last bit -- can you explain what you mean by |> "have to exerc them or else they are taken to be offline" ? |> My apologies for such an obscure sentence =) What I meant by that was that I had to use the command "exerc" on the srm monitor prior to the boot procedure to sort of "warm up" the disks. Without this "warm up exercise" for a few seconds the disks are detected but their size is not assessed (this failure is what I meant by "taken to be offline"). I hope that helps. Regards, Andre picapau@minmei.iqm.unicamp.br |> Thanks, |> |> Drew |> |> ------------------------------------------------------------------------------ |> Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin |> Duke University Email: gallatin@cs.duke.edu |> Department of Computer Science Phone: (919) 660-6590 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Mar 29 6:33:11 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 40FE637C1A6; Wed, 29 Mar 2000 06:32:55 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id JAA17667; Wed, 29 Mar 2000 09:32:54 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id JAA26479; Wed, 29 Mar 2000 09:32:24 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Wed, 29 Mar 2000 09:32:24 -0500 (EST) To: picapau@minmei.iqm.unicamp.br Cc: alpha@FreeBSD.ORG, scsi@FreeBSD.ORG Subject: SCSI disk problems on AS1000 In-Reply-To: <20000329111836.A10213@minmei.iqm.unicamp.br> References: <20000325181342.A88910@minmei.iqm.unicamp.br> <14557.27001.718759.711008@grasshopper.cs.duke.edu> <20000329092158.A96147@minmei.iqm.unicamp.br> <14562.2571.201291.426577@grasshopper.cs.duke.edu> <20000329111836.A10213@minmei.iqm.unicamp.br> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14562.4832.203053.753476@grasshopper.cs.duke.edu> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Andre Severo writes: > > My apologies for such an obscure sentence =) > > What I meant by that was that I had to use the command "exerc" > on the srm monitor prior to the boot procedure to sort of > "warm up" the disks. > > Without this "warm up exercise" for a few seconds the disks are detected but > their size is not assessed (this failure is what I meant by > "taken to be offline"). Hmm.. Older DEC disks tend to not spin up when they're powered on. I'd assumed that the FreeBSD CAM system would take care of spinning up such disks. Can a SCSI guru out there confirm this? Bear in mind that he's using the ncr driver, so some bets are off... Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Mar 29 8:35:36 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 2F6CD37B5CD for ; Wed, 29 Mar 2000 08:35:32 -0800 (PST) (envelope-from mjacob@feral.com) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id IAA11147; Wed, 29 Mar 2000 08:34:57 -0800 Date: Wed, 29 Mar 2000 08:35:12 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Andre Severo Cc: Andrew Gallatin , alpha@FreeBSD.ORG Subject: Re: AlphaServer 1000 freezing during installation In-Reply-To: <20000329111836.A10213@minmei.iqm.unicamp.br> 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 Hmm. I wonder if this is what Michael Waite saw a couple of months ago. Do you have some console messages about this and the internal h/w configuration and layout? On Wed, 29 Mar 2000, Andre Severo wrote: > At Wed, Mar 29, 2000 at 08:51:10AM -0500, Andrew Gallatin claimed that: > |> > |> Andre Severo writes: > |> > > |> > The disk problem persists, though - i have to exerc them or else they > |> > are taken to be offline. > |> > |> I didn't understand that last bit -- can you explain what you mean by > |> "have to exerc them or else they are taken to be offline" ? > |> > > My apologies for such an obscure sentence =) > > What I meant by that was that I had to use the command "exerc" > on the srm monitor prior to the boot procedure to sort of > "warm up" the disks. > > Without this "warm up exercise" for a few seconds the disks are detected but > their size is not assessed (this failure is what I meant by > "taken to be offline"). > > I hope that helps. > > Regards, > > Andre > picapau@minmei.iqm.unicamp.br > > |> Thanks, > |> > |> Drew > |> > |> ------------------------------------------------------------------------------ > |> Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin > |> Duke University Email: gallatin@cs.duke.edu > |> Department of Computer Science Phone: (919) 660-6590 > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-alpha" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Mar 29 8:44:19 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id BB69337C0D1; Wed, 29 Mar 2000 08:44:16 -0800 (PST) (envelope-from mjacob@feral.com) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id IAA11160; Wed, 29 Mar 2000 08:43:48 -0800 Date: Wed, 29 Mar 2000 08:44:04 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Andrew Gallatin Cc: picapau@minmei.iqm.unicamp.br, alpha@FreeBSD.ORG, scsi@FreeBSD.ORG Subject: Re: SCSI disk problems on AS1000 In-Reply-To: <14562.4832.203053.753476@grasshopper.cs.duke.edu> 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 > > Hmm.. Older DEC disks tend to not spin up when they're powered on. > I'd assumed that the FreeBSD CAM system would take care of spinning up > such disks. Can a SCSI guru out there confirm this? Bear in mind > that he's using the ncr driver, so some bets are off... > The cam_periph_error code does issue a START UNIT command, but only if scsi_error_action returns an error_action for this, which is then contingent upon what kind of error the disk returns. Frankly, this whole area of CAM is a bit too labyrynthine to state unequivocally that a START UNIT would be sent here. Sigh. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Mar 29 9:10: 5 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 2C30337B6D0 for ; Wed, 29 Mar 2000 09:10:03 -0800 (PST) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id JAA03977; Wed, 29 Mar 2000 09:10:02 -0800 (PST) (envelope-from gnats@FreeBSD.org) Date: Wed, 29 Mar 2000 09:10:02 -0800 (PST) Message-Id: <200003291710.JAA03977@freefall.freebsd.org> To: freebsd-alpha@freebsd.org Cc: From: Dirk Kleinhesselink Subject: Re: alpha/17642: FreeBSD/alpha 4.0 RELEASE installation fails with cant find init Reply-To: Dirk Kleinhesselink Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR alpha/17642; it has been noted by GNATS. From: Dirk Kleinhesselink To: "Jordan K. Hubbard" Cc: freebsd-gnats-submit@FreeBSD.ORG Subject: Re: alpha/17642: FreeBSD/alpha 4.0 RELEASE installation fails with cant find init Date: Wed, 29 Mar 2000 09:01:09 -0800 (PST) On Tue, 28 Mar 2000, Jordan K. Hubbard wrote: > I can't reproduce this on any of our alpha machines; can you tell me a > bit more about the configuration? > Sure -- I actually realized after I hit the send button that my hardware configuration wasn't specified: AlphaPC164 366MHz, 128MB RAM, SRM v. 5.5 (I think -- I upgraded several months ago with the firmware CD included with Tru64 5.0). The system has 2 IDE disks on ata0, the master has NT, the slave has Redhat 6.1 -- these disks are seen by SRM, ata1 has a CD-ROM drive, not seen by SRM. I put an ELSA Gloria Synergy video card in the system. It has a SCSI/Ethernet PCI combo card that was originally in an AlphaStation 600 5/266. The combo card has 2 Qlogic ISP 1020 UW SCSI channels and a DEC 21040-AA 10MB ethernet. The card has a 21050 bridge (?) chip on it. On SCSI channel A I have an IBM 18GB UW disk and on SCSI channel B I have a Toshiba SCSI CD-ROM. This card works with Linux, Tru64 and OpenVMS (I haven't tried NetBSD or switched to ARC and tried NT). If I try to boot FreeBSD either from CD-ROM or floppies, it will give me a machine check panic when it queries the SCSI controllers. I had posted this to the FreeBSD/alpha group when trying to run with the release candidate and I ended up loaning the card to Matthew Jacob. He told me he got it to work with his AlphaPC164 system and that I needed to either interrupt the boot after the kernel and mfsroot load and give the boot loader: set isp_mem_map=0xff or else build a custom kernel with: SCSI_ISP_PREFER_MEM_MAP=1 I obviously can't build a kernel if I can't install. If I interrupt the boot and give the boot loader the set isp_mem_map=0xff, it will get past the PCI device probe when it hits the SCSI controllers and it looks like it correctly identifies the system hardware but come to think of it, I never recall it reporting the devices on the SCSI channels -- it gets to the "waiting 15 seconds for SCSI devices to settle" and then the screen flashes to the red installation background and it immediately gives me the going nowhere can't find my init message and reboots. But I guess the installation is supposed to find a memory filesystem and so it shouldn't matter initially whether or not there are devices on the SCSI channels. It sounds to me like it can't find the memory filesystem. It certainly reports the ethernet, both scsi channels, both ide channels, the 2 ide disks and the ide cdrom. I also think I tried to boot from floppies with the 4.0 CD in the IDE cdrom drive and still got the panic and reboot. Dirk To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Mar 29 9:28:23 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 9A7E537B5FF; Wed, 29 Mar 2000 09:28:15 -0800 (PST) (envelope-from mjacob@feral.com) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id JAA11346; Wed, 29 Mar 2000 09:27:52 -0800 Date: Wed, 29 Mar 2000 09:28:08 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Dirk Kleinhesselink Cc: freebsd-gnats-submit@FreeBSD.ORG, freebsd-alpha@FreeBSD.ORG Subject: Re: alpha/17642: FreeBSD/alpha 4.0 RELEASE installation fails with cant find init In-Reply-To: <200003291710.JAA03977@freefall.freebsd.org> 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 Dirk, uh, was this the board I borrowed from you? It certainly did work for me when I did the isp_mem_map=0xff and it saw disks and I booted what was very close to the FreeBSD-4.0 kernel. No- I didn't boot the INSTALL kernel- it wasn't readily available to me at the time. I have the same basic system. Dirk- I'll clone you a disk to get you going if you like- I'm really not quite sure what the problem here is. (I also offered you On Wed, 29 Mar 2000, Dirk Kleinhesselink wrote: > The following reply was made to PR alpha/17642; it has been noted by GNATS. > > From: Dirk Kleinhesselink > To: "Jordan K. Hubbard" > Cc: freebsd-gnats-submit@FreeBSD.ORG > Subject: Re: alpha/17642: FreeBSD/alpha 4.0 RELEASE installation fails with cant find init > Date: Wed, 29 Mar 2000 09:01:09 -0800 (PST) > > On Tue, 28 Mar 2000, Jordan K. Hubbard wrote: > > > I can't reproduce this on any of our alpha machines; can you tell me a > > bit more about the configuration? > > > Sure -- I actually realized after I hit the send button that my hardware > configuration wasn't specified: > > AlphaPC164 366MHz, 128MB RAM, SRM v. 5.5 (I think -- I upgraded several > months ago with the firmware CD included with Tru64 5.0). The system has > 2 IDE disks on ata0, the master has NT, the slave has Redhat 6.1 -- these > disks are seen by SRM, ata1 has a CD-ROM drive, not seen by SRM. I put an > ELSA Gloria Synergy video card in the system. It has a SCSI/Ethernet PCI > combo card that was originally in an AlphaStation 600 5/266. The combo > card has 2 Qlogic ISP 1020 UW SCSI channels and a DEC 21040-AA 10MB > ethernet. The card has a 21050 bridge (?) chip on it. On SCSI channel A > I have an IBM 18GB UW disk and on SCSI channel B I have a Toshiba SCSI > CD-ROM. This card works with Linux, Tru64 and OpenVMS (I haven't tried > NetBSD or switched to ARC and tried NT). > > If I try to boot FreeBSD either from CD-ROM or floppies, it will give me a > machine check panic when it queries the SCSI controllers. I had posted > this to the FreeBSD/alpha group when trying to run with the release > candidate and I ended up loaning the card to Matthew Jacob. He told me he > got it to work with his AlphaPC164 system and that I needed to either > interrupt the boot after the kernel and mfsroot load and give the boot > loader: set isp_mem_map=0xff or else build a custom kernel with: > SCSI_ISP_PREFER_MEM_MAP=1 > > I obviously can't build a kernel if I can't install. If I interrupt the > boot and give the boot loader the set isp_mem_map=0xff, it will get past > the PCI device probe when it hits the SCSI controllers and it looks like > it correctly identifies the system hardware but come to think of it, I > never recall it reporting the devices on the SCSI channels -- it gets to > the "waiting 15 seconds for SCSI devices to settle" and then the screen > flashes to the red installation background and it immediately gives me the > going nowhere can't find my init message and reboots. > > But I guess the installation is supposed to find a memory filesystem and > so it shouldn't matter initially whether or not there are devices on the > SCSI channels. It sounds to me like it can't find the memory filesystem. > It certainly reports the ethernet, both scsi channels, both ide channels, > the 2 ide disks and the ide cdrom. I also think I tried to boot from > floppies with the 4.0 CD in the IDE cdrom drive and still got the panic > and reboot. > > Dirk > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-alpha" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Mar 29 9:30:12 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id C005737B5FF for ; Wed, 29 Mar 2000 09:30:09 -0800 (PST) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id JAA08064; Wed, 29 Mar 2000 09:30:08 -0800 (PST) (envelope-from gnats@FreeBSD.org) Date: Wed, 29 Mar 2000 09:30:08 -0800 (PST) Message-Id: <200003291730.JAA08064@freefall.freebsd.org> To: freebsd-alpha@freebsd.org Cc: From: Matthew Jacob Subject: Re: alpha/17642: FreeBSD/alpha 4.0 RELEASE installation fails with cant find init Reply-To: Matthew Jacob Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR alpha/17642; it has been noted by GNATS. From: Matthew Jacob To: Dirk Kleinhesselink Cc: freebsd-gnats-submit@FreeBSD.ORG, freebsd-alpha@FreeBSD.ORG Subject: Re: alpha/17642: FreeBSD/alpha 4.0 RELEASE installation fails with cant find init Date: Wed, 29 Mar 2000 09:28:08 -0800 (PST) Dirk, uh, was this the board I borrowed from you? It certainly did work for me when I did the isp_mem_map=0xff and it saw disks and I booted what was very close to the FreeBSD-4.0 kernel. No- I didn't boot the INSTALL kernel- it wasn't readily available to me at the time. I have the same basic system. Dirk- I'll clone you a disk to get you going if you like- I'm really not quite sure what the problem here is. (I also offered you On Wed, 29 Mar 2000, Dirk Kleinhesselink wrote: > The following reply was made to PR alpha/17642; it has been noted by GNATS. > > From: Dirk Kleinhesselink > To: "Jordan K. Hubbard" > Cc: freebsd-gnats-submit@FreeBSD.ORG > Subject: Re: alpha/17642: FreeBSD/alpha 4.0 RELEASE installation fails with cant find init > Date: Wed, 29 Mar 2000 09:01:09 -0800 (PST) > > On Tue, 28 Mar 2000, Jordan K. Hubbard wrote: > > > I can't reproduce this on any of our alpha machines; can you tell me a > > bit more about the configuration? > > > Sure -- I actually realized after I hit the send button that my hardware > configuration wasn't specified: > > AlphaPC164 366MHz, 128MB RAM, SRM v. 5.5 (I think -- I upgraded several > months ago with the firmware CD included with Tru64 5.0). The system has > 2 IDE disks on ata0, the master has NT, the slave has Redhat 6.1 -- these > disks are seen by SRM, ata1 has a CD-ROM drive, not seen by SRM. I put an > ELSA Gloria Synergy video card in the system. It has a SCSI/Ethernet PCI > combo card that was originally in an AlphaStation 600 5/266. The combo > card has 2 Qlogic ISP 1020 UW SCSI channels and a DEC 21040-AA 10MB > ethernet. The card has a 21050 bridge (?) chip on it. On SCSI channel A > I have an IBM 18GB UW disk and on SCSI channel B I have a Toshiba SCSI > CD-ROM. This card works with Linux, Tru64 and OpenVMS (I haven't tried > NetBSD or switched to ARC and tried NT). > > If I try to boot FreeBSD either from CD-ROM or floppies, it will give me a > machine check panic when it queries the SCSI controllers. I had posted > this to the FreeBSD/alpha group when trying to run with the release > candidate and I ended up loaning the card to Matthew Jacob. He told me he > got it to work with his AlphaPC164 system and that I needed to either > interrupt the boot after the kernel and mfsroot load and give the boot > loader: set isp_mem_map=0xff or else build a custom kernel with: > SCSI_ISP_PREFER_MEM_MAP=1 > > I obviously can't build a kernel if I can't install. If I interrupt the > boot and give the boot loader the set isp_mem_map=0xff, it will get past > the PCI device probe when it hits the SCSI controllers and it looks like > it correctly identifies the system hardware but come to think of it, I > never recall it reporting the devices on the SCSI channels -- it gets to > the "waiting 15 seconds for SCSI devices to settle" and then the screen > flashes to the red installation background and it immediately gives me the > going nowhere can't find my init message and reboots. > > But I guess the installation is supposed to find a memory filesystem and > so it shouldn't matter initially whether or not there are devices on the > SCSI channels. It sounds to me like it can't find the memory filesystem. > It certainly reports the ethernet, both scsi channels, both ide channels, > the 2 ide disks and the ide cdrom. I also think I tried to boot from > floppies with the 4.0 CD in the IDE cdrom drive and still got the panic > and reboot. > > Dirk > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-alpha" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Mar 29 10: 5:34 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id E5B2637C110; Wed, 29 Mar 2000 10:05:13 -0800 (PST) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id LAA91931; Wed, 29 Mar 2000 11:04:39 -0700 (MST) (envelope-from ken) Date: Wed, 29 Mar 2000 11:04:38 -0700 From: "Kenneth D. Merry" To: Matthew Jacob Cc: Andrew Gallatin , picapau@minmei.iqm.unicamp.br, alpha@FreeBSD.ORG, scsi@FreeBSD.ORG Subject: Re: SCSI disk problems on AS1000 Message-ID: <20000329110438.A91800@panzer.kdm.org> References: <14562.4832.203053.753476@grasshopper.cs.duke.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from mjacob@feral.com on Wed, Mar 29, 2000 at 08:44:04AM -0800 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, Mar 29, 2000 at 08:44:04 -0800, Matthew Jacob wrote: > > > > Hmm.. Older DEC disks tend to not spin up when they're powered on. > > I'd assumed that the FreeBSD CAM system would take care of spinning up > > such disks. Can a SCSI guru out there confirm this? Bear in mind > > that he's using the ncr driver, so some bets are off... > > > > The cam_periph_error code does issue a START UNIT command, but only if > scsi_error_action returns an error_action for this, which is then contingent > upon what kind of error the disk returns. Frankly, this whole area of CAM is a > bit too labyrynthine to state unequivocally that a START UNIT would be sent > here. Sigh. Yes, it is one of the most complicated pieces of the CAM code. Error recovery in general is complicated. That code is being rewritten, though. In any case, yes, you will get a start unit if the error is 0x04,0x02, or "Logical unit not ready, initializing cmd. required". You will also get a start unit if you have a Quantum Fireball ST and it returns 0x04,0x0b. Since the boot disk in the machine in question must be spinning in order for any OS to boot, you should be able to get dmesg output from the machine, and we can see what sort of error the disks are returning. If you just want to kludge around it, you can do things like: camcontrol start da1 in /etc/rc before the disks are mounted. If these disks are returning a non-standard sense code, we can probably quirk them so they'll get started. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Mar 29 10: 6: 7 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from b05.egroups.com (b05.egroups.com [207.138.41.189]) by hub.freebsd.org (Postfix) with SMTP id D658237B6D0 for ; Wed, 29 Mar 2000 10:02:27 -0800 (PST) (envelope-from kmail@dolphinsearch.com) X-eGroups-Return: kmail@dolphinsearch.com Received: from [10.1.2.121] by b05.egroups.com with NNFMP; 29 Mar 2000 18:02:10 -0000 Date: Wed, 29 Mar 2000 10:02:04 -0800 From: "Kelly" To: freebsd-alpha@freebsd.org Subject: Install Problem Message-ID: <8btges$4em0@eGroups.com> User-Agent: eGroups-EW/0.82 Content-Length: 890 X-Mailer: eGroups Message Poster Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Kelly writes: > Ok. I download the ISO Image of version 4.0 for alpha, burned the > disk, and then installed the software. The install works fine. Once > the install is done, I select "Exit Install," takes me back to SRM > console. Then type boot dka0, but once the system come backup it takes > me right back to the install application, and not to a logon. > > I have tried the install from ftp with the same problem. I am tring to > install on a DS10. >I think I saw something like this on my AS200. I think the previous >boot device may be sticking in the SRM console & you're booting from >the CD again. >Try this: When you exit from sysinstall, type 'init' at the srm >console prompt (>>>), then boot. (or powercycle the box). >Drew I know that this is not the problem, because I have the same problem when I install from a ftp download. any more Ideas. Kelly To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Mar 29 10:44:59 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 2E7FB37B9BD for ; Wed, 29 Mar 2000 10:44:51 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id NAA26815; Wed, 29 Mar 2000 13:44:49 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id NAA00450; Wed, 29 Mar 2000 13:44:19 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Wed, 29 Mar 2000 13:44:18 -0500 (EST) To: "Kelly" Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: Install Problem In-Reply-To: <8btges$4em0@eGroups.com> References: <8btges$4em0@eGroups.com> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14562.19812.773470.275558@grasshopper.cs.duke.edu> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Kelly writes: > > I know that this is not the problem, because I have the same problem > when I install from a ftp download. And you're certain you've removed the CDROM & floppies? > any more Ideas. Yes, boot verbosely (boot -fl v from SRM, or boot -v from the boot loader), then scroll up & see what start_init() is saying about the init path. You might see something like: init: not found in path /sbin/init Also, report what it says about where it is mounting root from. It will be something like: Mounting root from ufs:/dev/da1a Cheers, Drew PS: In syscons, you can scroll up by toggling scroll lock & using pgup/pgdown. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Mar 29 11:35:25 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from news-ma.rhein-neckar.de (news-ma.rhein-neckar.de [193.197.90.3]) by hub.freebsd.org (Postfix) with ESMTP id CFDB637B97C for ; Wed, 29 Mar 2000 11:32:18 -0800 (PST) (envelope-from daemon@bigeye.rhein-neckar.de) Received: from bigeye.rhein-neckar.de (uucp@localhost) by news-ma.rhein-neckar.de (8.8.8/8.8.8) with bsmtp id VAA21289 for freebsd-alpha@freebsd.org; Wed, 29 Mar 2000 21:32:16 +0200 (CEST) (envelope-from daemon@bigeye.rhein-neckar.de) Received: (from daemon@localhost) by bigeye.rhein-neckar.de (8.9.3/8.9.3) id VAA52231 for freebsd-alpha@freebsd.org; Wed, 29 Mar 2000 21:18:42 +0200 (CEST) (envelope-from daemon) From: naddy@mips.rhein-neckar.de (Christian Weisgerber) Subject: Re: Cross building Alpha on an i386 Date: 29 Mar 2000 21:18:41 +0200 Message-ID: <8btkuh$1ivu$1@bigeye.rhein-neckar.de> References: <38E1809F.5CBA9037@home.net> To: freebsd-alpha@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Craig Burgess wrote: > Would not big-endian / little-endian be of great significance (and a > serious hurdle)? i386 and alpha are both little-endian. -- Christian "naddy" Weisgerber naddy@mips.rhein-neckar.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Mar 29 12:45:58 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 8428D37C187; Wed, 29 Mar 2000 12:45:31 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id WAA18951; Wed, 29 Mar 2000 22:29:42 +0200 (MET DST) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id UAA02201; Wed, 29 Mar 2000 20:52:37 +0200 (CEST) (envelope-from wilko) Date: Wed, 29 Mar 2000 20:52:37 +0200 From: Wilko Bulte To: Andrew Gallatin Cc: picapau@minmei.iqm.unicamp.br, alpha@freebsd.org, scsi@freebsd.org Subject: Re: SCSI disk problems on AS1000 Message-ID: <20000329205237.E2044@yedi.iaf.nl> Reply-To: wilko@freebsd.org References: <20000325181342.A88910@minmei.iqm.unicamp.br> <14557.27001.718759.711008@grasshopper.cs.duke.edu> <20000329092158.A96147@minmei.iqm.unicamp.br> <14562.2571.201291.426577@grasshopper.cs.duke.edu> <20000329111836.A10213@minmei.iqm.unicamp.br> <14562.4832.203053.753476@grasshopper.cs.duke.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <14562.4832.203053.753476@grasshopper.cs.duke.edu>; from gallatin@cs.duke.edu on Wed, Mar 29, 2000 at 09:32:24AM -0500 X-OS: FreeBSD 3.4-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, Mar 29, 2000 at 09:32:24AM -0500, Andrew Gallatin wrote: > > Andre Severo writes: > > > > My apologies for such an obscure sentence =) > > > > What I meant by that was that I had to use the command "exerc" > > on the srm monitor prior to the boot procedure to sort of > > "warm up" the disks. > > > > Without this "warm up exercise" for a few seconds the disks are detected but > > their size is not assessed (this failure is what I meant by > > "taken to be offline"). > > > Hmm.. Older DEC disks tend to not spin up when they're powered on. These are the older RZxx disks. The 'multivendor variant' of the same drives (SWX*-*) are set for staggered spinup (spin up delay based on SCSI target ID). W/ -- Wilko Bulte Arnhem, The Netherlands http://www.tcja.nl The FreeBSD Project: http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Mar 29 12:46: 2 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 0CBD237C110; Wed, 29 Mar 2000 12:45:41 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id WAA18950; Wed, 29 Mar 2000 22:29:41 +0200 (MET DST) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id UAA02190; Wed, 29 Mar 2000 20:51:08 +0200 (CEST) (envelope-from wilko) Date: Wed, 29 Mar 2000 20:51:08 +0200 From: Wilko Bulte To: Andrew Gallatin Cc: picapau@minmei.iqm.unicamp.br, alpha@freebsd.org, scsi@freebsd.org Subject: Re: SCSI disk problems on AS1000 Message-ID: <20000329205108.D2044@yedi.iaf.nl> Reply-To: wilko@freebsd.org References: <20000325181342.A88910@minmei.iqm.unicamp.br> <14557.27001.718759.711008@grasshopper.cs.duke.edu> <20000329092158.A96147@minmei.iqm.unicamp.br> <14562.2571.201291.426577@grasshopper.cs.duke.edu> <20000329111836.A10213@minmei.iqm.unicamp.br> <14562.4832.203053.753476@grasshopper.cs.duke.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <14562.4832.203053.753476@grasshopper.cs.duke.edu>; from gallatin@cs.duke.edu on Wed, Mar 29, 2000 at 09:32:24AM -0500 X-OS: FreeBSD 3.4-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, Mar 29, 2000 at 09:32:24AM -0500, Andrew Gallatin wrote: > > Andre Severo writes: > > > > My apologies for such an obscure sentence =) > > > > What I meant by that was that I had to use the command "exerc" > > on the srm monitor prior to the boot procedure to sort of > > "warm up" the disks. > > > > Without this "warm up exercise" for a few seconds the disks are detected but > > their size is not assessed (this failure is what I meant by > > "taken to be offline"). > > > Hmm.. Older DEC disks tend to not spin up when they're powered on. > I'd assumed that the FreeBSD CAM system would take care of spinning up > such disks. Can a SCSI guru out there confirm this? Bear in mind Yes it does. But a SHOW DEVICES on SRM also does it if I remember correctly. I had no troubles when I tested one of the 4.0-RC on our 1000A. I no longer have a 1000 available. This was using DEC RZxx disks. -- Wilko Bulte Arnhem, The Netherlands http://www.tcja.nl The FreeBSD Project: http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Mar 29 14:37:59 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id C64F837BC38; Wed, 29 Mar 2000 14:37:37 -0800 (PST) (envelope-from billf@FreeBSD.org) Received: (from billf@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id OAA65314; Wed, 29 Mar 2000 14:37:37 -0800 (PST) (envelope-from billf@FreeBSD.org) Date: Wed, 29 Mar 2000 14:37:37 -0800 (PST) From: Message-Id: <200003292237.OAA65314@freefall.freebsd.org> To: billf@FreeBSD.org, freebsd-alpha@FreeBSD.org, billf@FreeBSD.org Subject: Re: alpha/17637: misconfigured syscons bell causes panic on alpha Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Synopsis: misconfigured syscons bell causes panic on alpha Responsible-Changed-From-To: freebsd-alpha->billf Responsible-Changed-By: billf Responsible-Changed-When: Wed Mar 29 14:35:43 PST 2000 Responsible-Changed-Why: I'm working on this and as soon as I can get a kernel to compile on beast, I'll commit it. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Mar 29 18:57:55 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from ptldpop1.ptld.uswest.net (ptldpop1.ptld.uswest.net [198.36.160.1]) by hub.freebsd.org (Postfix) with SMTP id 31E1F37BB11 for ; Wed, 29 Mar 2000 18:57:52 -0800 (PST) (envelope-from wwoods@cybcon.com) Received: (qmail 19826 invoked by alias); 30 Mar 2000 02:41:19 -0000 Delivered-To: fixup-freebsd-alpha@freebsd.org@fixme Received: (qmail 26331 invoked by uid 0); 30 Mar 2000 02:18:43 -0000 Received: from unknown (HELO laptop.cybcon.com) (63.227.213.90) by ptldpop1.ptld.uswest.net with SMTP; 30 Mar 2000 02:18:43 -0000 Content-Length: 2334 Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Wed, 29 Mar 2000 18:18:41 -0800 (PST) Reply-To: bwoods2@uswest.net From: William Woods To: freebsd-alpha@freebsd.org Subject: Make Worls Dies... Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Running 4.0-stable on a DEC Alpha, doing a make world I get: ------------------------- mkdep -f .depend -a -nostdinc -D_KERNEL -DKLD_MODULE -I- -I. -I@ -I@/../include -I/usr/obj/usr/src/alpha/usr/include /usr/src/sys/modules/joy/../../isa/joy.c ===> sys/modules/kernfs @ -> /usr/src/sys machine -> /usr/src/sys/alpha/include perl @/kern/vnode_if.pl -h @/kern/vnode_if.src rm -f .depend mkdep -f .depend -a -nostdinc -D_KERNEL -DKLD_MODULE -I- -I. -I@ -I@/../include -I/usr/obj/usr/src/alpha/usr/include /usr/src/sys/modules/kernfs/../../miscfs/kernfs/kernfs_vfsops.c /usr/src/sys/modules/kernfs/../../miscfs/kernfs/kernfs_vnops.c ===> sys/modules/kue @ -> /usr/src/sys machine -> /usr/src/sys/alpha/include touch opt_bdg.h touch opt_usb.h perl @/kern/makedevops.pl -h @/kern/device_if.m perl @/kern/makedevops.pl -h @/kern/bus_if.m perl @/kern/makedevops.pl -h @/dev/mii/miibus_if.m rm -f .depend mkdep -f .depend -a -nostdinc -D_KERNEL -DKLD_MODULE -I- -I. -I@ -I@/../include -I/usr/obj/usr/src/alpha/usr/include /usr/src/sys/modules/kue/../../dev/usb/if_kue.c ===> sys/modules/linprocfs @ -> /usr/src/sys machine -> /usr/src/sys/alpha/include perl @/kern/vnode_if.pl -h @/kern/vnode_if.src rm -f .depend mkdep -f .depend -a -nostdinc -DLINPROCFS -D_KERNEL -DKLD_MODULE -I- -I. -I@ -I@/../include -I/usr/obj/usr/src/alpha/usr/include /usr/src/sys/modules/linprocfs/../../miscfs/linprocfs/linprocfs_misc.c /usr/src/sys/modules/linprocfs/../../miscfs/linprocfs/linprocfs_subr.c /usr/src/sys/modules/linprocfs/../../miscfs/linprocfs/linprocfs_vfsops.c /usr/src/sys/modules/linprocfs/../../miscfs/linprocfs/linprocfs_vnops.c /usr/src/sys/modules/linprocfs/../../miscfs/linprocfs/linprocfs_misc.c:61: machine/cputypes.h: No such file or directory mkdep: compile failed *** Error code 1 Stop in /usr/src/sys/modules/linprocfs. *** Error code 1 Stop in /usr/src/sys/modules. *** Error code 1 Stop in /usr/src/sys. *** Error code 1 ----------------------------- Ideas? ---------------------------------- E-Mail: bwoods2@uswest.net Date: 29-Mar-00 Time: 18:18:04l ---------------------------------- NOTICE TO BULK E-MAILERS: Pursuant to US Code, Title 47, Chapter 5, Subchapter II, 227, and all unsolicited commercial e-mail sent to this address is subject to a download and archival fee in the amount of $500 US To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Mar 29 21:50:51 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from europa.engg.ksu.edu (Europa.engg.ksu.edu [129.130.81.112]) by hub.freebsd.org (Postfix) with ESMTP id 7E25E37B7DD for ; Wed, 29 Mar 2000 21:50:48 -0800 (PST) (envelope-from dave@europa.engg.ksu.edu) Received: from phobos.engg.ksu.edu (phobos.engg.ksu.edu [129.130.81.133]) by europa.engg.ksu.edu (8.9.3/8.9.3) with ESMTP id XAA17034 for ; Wed, 29 Mar 2000 23:50:47 -0600 (CST) Received: from localhost (dave@localhost) by phobos.engg.ksu.edu (8.9.3+Sun/8.9.1) with SMTP id XAA21781 for ; Wed, 29 Mar 2000 23:58:32 -0600 (CST) Date: Wed, 29 Mar 2000 23:58:31 -0600 (CST) From: Dave Haney To: freebsd-alpha@freebsd.org Subject: Unexpected machine check 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 Hello, I have an AlphaStation 200 4/233 running FreeBSD 4.0-RELEASE, XFree86 version 3.3.6 with a Diamond Stealth 3D 3000 Pro 4MB PCI card for video, and otherwise stock hardware. When I compile, then run XFree86_SVGA on it and kill X from the console I started it on with ^C, the machine instantly crashes with the following error: unexpected machine check: mces = 0x1 vector = 0x660 param = 0xfffffc0000006000 pc = 0x1200bac54 ra = 0x1200bac24 cuproc = 0xfffffe0004379d80 pid = 1328, comm = XF86_SVGA panic: machine check syncing disks... done Uptime: 1d7h25m5s * This problem did not occur when I was running FreeBSD 4.0-CURRENT. What's more, I have not changed any hardware configurations since then. * Tried the machine and found the problems to be reproduceable with both the GENERIC kernel, and any kernel I choose to build. * I tried downloading and re-installing FreeBSD 4.0-RELEASE twice, but to no avail. This problem is perfectly reproduceable. * The "pc =" and "ra =" "curproc =" and "pid =" parameters change between crashes. * While X is running, windows are not drawn properly. For example, xmms will only come up as a large, black rectangle. TWM will not properly draw menus. * After swapping out the Stealth for a STB Velocity 3D, the problems persisted, with the same symptoms. This may not be a telling factor, though, as the same chipset is used on both boards. * As long as XWindows is not running, the machine seems perfectly stable. I've compiled several kernels on it which seem to run fine. * the SRM variable pci_parity is set to off. * If I switch to the S3V server, then the machine will safely exit XWindows, but if I switch between virtural consoles (while X is still running), the machine will hard lock, and a few seconds later, the screen turns blue, and says "CPU HALT CODE = 5" and reboots. * While using the S3V server, windows seem to be drawn and re-drawn properly. Any ideas? Thanks, Dave Haney To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Mar 29 21:55: 6 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id D38AB37BCC4 for ; Wed, 29 Mar 2000 21:55:03 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id VAA18821 for ; Wed, 29 Mar 2000 21:55:02 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id VAA06253; Wed, 29 Mar 2000 21:55:02 -0800 (PST) (envelope-from jdp@polstra.com) Date: Wed, 29 Mar 2000 21:55:02 -0800 (PST) Message-Id: <200003300555.VAA06253@vashon.polstra.com> To: alpha@freebsd.org Subject: Re: Dual boot FreeBSD + OSF1? In-Reply-To: <20000329075925.A56808@yedi.iaf.nl> References: <20000329075925.A56808@yedi.iaf.nl> Organization: Polstra & Co., Seattle, WA Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In article <20000329075925.A56808@yedi.iaf.nl>, Wilko Bulte wrote: > On Tue, Mar 28, 2000 at 07:41:45PM -0800, John Polstra wrote: > > Is it feasible to set up an Alpha box for dual boot with FreeBSD and > > OSF1? And if so, what does it take to get a licensed copy of OSF1? > > On 2 seperate disks that works fine. I had one of my Alphas configured this > way. Just >>> boot dka0 or >>> boot dka100 to select the right os. > > > Big $$ or little $$? > > I think Compaq has a hobbyist license for Tru64 (OSF/1) these days. Thanks for the info, everybody. This is much better than I thought. I'm planning to go ahead and install a 2nd disk and shell out the $99 to Compaq for the license. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Mar 30 6:24:58 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 84A9537BCE0 for ; Thu, 30 Mar 2000 06:24:55 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id JAA23901; Thu, 30 Mar 2000 09:24:54 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id JAA02639; Thu, 30 Mar 2000 09:24:24 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Thu, 30 Mar 2000 09:24:24 -0500 (EST) To: bwoods2@uswest.net Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: Make Worls Dies... In-Reply-To: References: X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14563.24676.673104.221474@grasshopper.cs.duke.edu> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org William Woods writes: > > Running 4.0-stable on a DEC Alpha, doing a make world I get: I've just committed a fix for that (mfc of sys/modules/Makefile 1.113. Linprocfs was mfc'ed much too quickly. Drew ------------------------------------------------------------------------------ Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin Duke University Email: gallatin@cs.duke.edu Department of Computer Science Phone: (919) 660-6590 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Mar 30 8:26:47 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id B43A637B554; Thu, 30 Mar 2000 08:26:45 -0800 (PST) (envelope-from obrien@NUXI.ucdavis.edu) Received: from dragon.nuxi.com (root@d60-024.leach.ucdavis.edu [169.237.60.24]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id IAA15041; Thu, 30 Mar 2000 08:26:45 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id IAA56485; Thu, 30 Mar 2000 08:26:45 -0800 (PST) (envelope-from obrien) Date: Thu, 30 Mar 2000 08:26:45 -0800 From: "David O'Brien" To: jkoshy@FreeBSD.org Cc: alpha@FreeBSD.org Subject: Re: Cross building Alpha on an i386 Message-ID: <20000330082645.B56425@dragon.nuxi.com> Reply-To: obrien@FreeBSD.org References: <200003280528.VAA39537@freefall.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <200003280528.VAA39537@freefall.freebsd.org>; from jkoshy@FreeBSD.org on Mon, Mar 27, 2000 at 09:28:57PM -0800 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, Mar 27, 2000 at 09:28:57PM -0800, jkoshy@FreeBSD.org wrote: > I can't seem to find a prior message in the mailing lists about this > problem. A cross build with MACHINE_ARCH=alpha on a FreeBSD/x86 system > fails: > > foobar# make MACHINE_ARCH=alpha buildworld What's ``uname -a'' on this box? Is the compiler before I did the major moving of configuration information from config/{i386,alpha}/freebsd.h to config/freebsd.h? -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Mar 30 9: 2:39 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from mail.cybcon.com (mail.cybcon.com [216.190.188.5]) by hub.freebsd.org (Postfix) with ESMTP id B075837B53D for ; Thu, 30 Mar 2000 09:02:33 -0800 (PST) (envelope-from wwoods@cybcon.com) Received: from laptop.cybcon.com (william@tc1-11.cybcon.com [63.163.56.12]) by mail.cybcon.com (8.9.3/8.9.3) with ESMTP id JAA20918 for ; Thu, 30 Mar 2000 09:03:37 -0800 (PST) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Thu, 30 Mar 2000 09:02:27 -0800 (PST) Reply-To: bwoods2@uswest.net From: William Woods To: freebsd-alpha@freebsd.org Subject: makmake world dies here.... Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Running 4.0-stable, cvsup today, on a DEC Alpha 200 4/233 I get this running make world: ------------------------------------- /../cc_tools -I/usr/src/gnu/usr.bin/cc/cccp/../../../../contrib/gcc -I/usr/src/gnu/usr.bin/cc/cccp/../../../../contrib/gcc/config -I/usr/obj/usr/src/alpha/usr/include -c cexp.c cc -O -pipe -DFREEBSD_NATIVE -DIN_GCC -DHAVE_CONFIG_H -DDEFAULT_TARGET_VERSION=\"2.95.2\" -DDEFAULT_TARGET_MACHINE=\"alpha-unknown-freebsd\" -DPREFIX=\"/usr/obj/usr/src/alpha/usr\" -DHAIFA -I/usr/obj/usr/src/alpha/usr/src/gnu/usr.bin/cc/cccp/../cc_tools -I/usr/src/gnu/usr.bin/cc/cccp/../cc_tools -I/usr/src/gnu/usr.bin/cc/cccp/../../../../contrib/gcc -I/usr/src/gnu/usr.bin/cc/cccp/../../../../contrib/gcc/config -I/usr/obj/usr/src/alpha/usr/include -c /usr/src/gnu/usr.bin/cc/cccp/../../../../contrib/gcc/obstack.c cc -O -pipe -DFREEBSD_NATIVE -DIN_GCC -DHAVE_CONFIG_H -DDEFAULT_TARGET_VERSION=\"2.95.2\" -DDEFAULT_TARGET_MACHINE=\"alpha-unknown-freebsd\" -DPREFIX=\"/usr/obj/usr/src/alpha/usr\" -DHAIFA -I/usr/obj/usr/src/alpha/usr/src/gnu/usr.bin/cc/cccp/../cc_tools -I/usr/src/gnu/usr.bin/cc/cccp/../cc_tools -I/usr/src/gnu/usr.bin/cc/cccp/../../../../contrib/gcc -I/usr/src/gnu/usr.bin/cc/cccp/../../../../contrib/gcc/config -I/usr/obj/usr/src/alpha/usr/include -c /usr/src/gnu/usr.bin/cc/cccp/../../../../contrib/gcc/prefix.c cc -O -pipe -DFREEBSD_NATIVE -DIN_GCC -DHAVE_CONFIG_H -DDEFAULT_TARGET_VERSION=\"2.95.2\" -DDEFAULT_TARGET_MACHINE=\"alpha-unknown-freebsd\" -DPREFIX=\"/usr/obj/usr/src/alpha/usr\" -DHAIFA -I/usr/obj/usr/src/alpha/usr/src/gnu/usr.bin/cc/cccp/../cc_tools -I/usr/src/gnu/usr.bin/cc/cccp/../cc_tools -I/usr/src/gnu/usr.bin/cc/cccp/../../../../contrib/gcc -I/usr/src/gnu/usr.bin/cc/cccp/../../../../contrib/gcc/config -I/usr/obj/usr/src/alpha/usr/include -c /usr/src/gnu/usr.bin/cc/cccp/../../../../contrib/gcc/version.c cc -O -pipe -DFREEBSD_NATIVE -DIN_GCC -DHAVE_CONFIG_H -DDEFAULT_TARGET_VERSION=\"2.95.2\" -DDEFAULT_TARGET_MACHINE=\"alpha-unknown-freebsd\" -DPREFIX=\"/usr/obj/usr/src/alpha/usr\" -DHAIFA -I/usr/obj/usr/src/alpha/usr/src/gnu/usr.bin/cc/cccp/../cc_tools -I/usr/src/gnu/usr.bin/cc/cccp/../cc_tools -I/usr/src/gnu/usr.bin/cc/cccp/../../../../contrib/gcc -I/usr/src/gnu/usr.bin/cc/cccp/../../../../contrib/gcc/config -I/usr/obj/usr/src/alpha/usr/include -o cpp cccp.o cexp.o obstack.o prefix.o version.o ===> cpp cc -O -pipe -DFREEBSD_NATIVE -DIN_GCC -DHAVE_CONFIG_H -DDEFAULT_TARGET_VERSION=\"2.95.2\" -DDEFAULT_TARGET_MACHINE=\"alpha-unknown-freebsd\" -DPREFIX=\"/usr/obj/usr/src/alpha/usr\" -DHAIFA -I/usr/obj/usr/src/alpha/usr/src/gnu/usr.bin/cc/cpp/../cc_tools -I/usr/src/gnu/usr.bin/cc/cpp/../cc_tools -I/usr/src/gnu/usr.bin/cc/cpp/../../../../contrib/gcc -I/usr/src/gnu/usr.bin/cc/cpp/../../../../contrib/gcc/config -I/usr/obj/usr/src/alpha/usr/include -c /usr/src/gnu/usr.bin/cc/cpp/../../../../contrib/gcc/gcc.c cc -O -pipe -DFREEBSD_NATIVE -DIN_GCC -DHAVE_CONFIG_H -DDEFAULT_TARGET_VERSION=\"2.95.2\" -DDEFAULT_TARGET_MACHINE=\"alpha-unknown-freebsd\" -DPREFIX=\"/usr/obj/usr/src/alpha/usr\" -DHAIFA -I/usr/obj/usr/src/alpha/usr/src/gnu/usr.bin/cc/cpp/../cc_tools -I/usr/src/gnu/usr.bin/cc/cpp/../cc_tools -I/usr/src/gnu/usr.bin/cc/cpp/../../../../contrib/gcc -I/usr/src/gnu/usr.bin/cc/cpp/../../../../contrib/gcc/config -I/usr/obj/usr/src/alpha/usr/include -c /usr/src/gnu/usr.bin/cc/cpp/../../../../contrib/gcc/cppspec.c cc -O -pipe -DFREEBSD_NATIVE -DIN_GCC -DHAVE_CONFIG_H -DDEFAULT_TARGET_VERSION=\"2.95.2\" -DDEFAULT_TARGET_MACHINE=\"alpha-unknown-freebsd\" -DPREFIX=\"/usr/obj/usr/src/alpha/usr\" -DHAIFA -I/usr/obj/usr/src/alpha/usr/src/gnu/usr.bin/cc/cpp/../cc_tools -I/usr/src/gnu/usr.bin/cc/cpp/../cc_tools -I/usr/src/gnu/usr.bin/cc/cpp/../../../../contrib/gcc -I/usr/src/gnu/usr.bin/cc/cpp/../../../../contrib/gcc/config -I/usr/obj/usr/src/alpha/usr/include -o cpp gcc.o cppspec.o /usr/obj/usr/src/alpha/usr/src/gnu/usr.bin/cc/cpp/../cc_int/libcc_int.a /usr/obj/usr/src/alpha/usr/src/gnu/usr.bin/cc/cpp/../cc_fbsd/libcc_fbsd.a /usr/obj/usr/src/alpha/usr/src/gnu/usr.bin/cc/cpp/../cc_fbsd/libcc_fbsd.a: could not read symbols: Archive has no index; run ranlib to add one*** Error code 1 Stop in /usr/src/gnu/usr.bin/cc/cpp. *** Error code 1 Stop in /usr/src/gnu/usr.bin/cc. *** Error code 1 Stop in /usr/src. *** Error code 1 ---------------------------------- ideas, options?? ---------------------------------- E-Mail: bwoods2@uswest.net Date: 30-Mar-00 Time: 09:00:45l ---------------------------------- NOTICE TO BULK E-MAILERS: Pursuant to US Code, Title 47, Chapter 5, Subchapter II, 227, and all unsolicited commercial e-mail sent to this address is subject to a download and archival fee in the amount of $500 US To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Mar 30 9:25:13 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id C2CF337B73E for ; Thu, 30 Mar 2000 09:25:09 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id JAA21953; Thu, 30 Mar 2000 09:25:06 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id JAA07284; Thu, 30 Mar 2000 09:25:06 -0800 (PST) (envelope-from jdp@polstra.com) Date: Thu, 30 Mar 2000 09:25:06 -0800 (PST) Message-Id: <200003301725.JAA07284@vashon.polstra.com> To: morrildl@nycap.rr.com Subject: Re: Cross building Alpha on an i386 In-Reply-To: References: Organization: Polstra & Co., Seattle, WA Cc: alpha@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In article , wrote: > > In the Linux world, the gurus say that you can't cross-build for the Alpha > from a 32-bit system with gcc. IIRC (which is unlikely :) it's got something > to do with gas not being equipped to deal with 64-bit pointers and > instructions on a system with 32-bit registers. (Doing a cross from 64-bit > to 32-bit archs works.) Actually I think you may have that backwards. My experience is that a 32 -> 64 bit cross build works fine, but a 64 -> 32 bit cross build fails. (Yes, I realize that is counter-intuitive.) Aside from my personal experience, I've read in several places that the "64x32 cross" is broken. By the way, the Modula-3 system uses a slightly modified GCC backend to generate code. Building Alpha executables on an i386 definitely works in that case. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Mar 30 10:29:11 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 66D9C37B843 for ; Thu, 30 Mar 2000 10:29:07 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id UAA13701; Thu, 30 Mar 2000 20:26:54 +0200 (MET DST) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id UAA01865; Thu, 30 Mar 2000 20:15:13 +0200 (CEST) (envelope-from wilko) Date: Thu, 30 Mar 2000 20:15:13 +0200 From: Wilko Bulte To: Dave Haney Cc: freebsd-alpha@freebsd.org Subject: Re: Unexpected machine check Message-ID: <20000330201513.A1750@yedi.iaf.nl> Reply-To: wilko@freebsd.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: ; from dave@engg.ksu.edu on Wed, Mar 29, 2000 at 11:58:31PM -0600 X-OS: FreeBSD 3.4-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, Mar 29, 2000 at 11:58:31PM -0600, Dave Haney wrote: > I have an AlphaStation 200 4/233 running FreeBSD 4.0-RELEASE, XFree86 > version 3.3.6 with a Diamond Stealth 3D 3000 Pro 4MB PCI card for video, > and otherwise stock hardware. When I compile, then run XFree86_SVGA on it > and kill X from the console I started it on with ^C, the machine instantly > crashes with the following error: ... > * After swapping out the Stealth for a STB Velocity 3D, the problems > persisted, with the same symptoms. This may not be a telling factor, > though, as the same chipset is used on both boards. > > * As long as XWindows is not running, the machine seems perfectly stable. > I've compiled several kernels on it which seem to run fine. Yep.. similar experience here on multiple Miata machines (MX5 and GL). Used S3 based cards, as well as Mach64 > * If I switch to the S3V server, then the machine will safely exit > XWindows, but if I switch between virtural consoles (while X is still > running), the machine will hard lock, and a few seconds later, the screen > turns blue, and says "CPU HALT CODE = 5" and reboots. There is definitely a bogon somewhere as far as X on Alpha goes. The problem seems to be core logic chipset related, people fortunate enough to own Tsunami based systems do not seem to have these problems. Also the type of VGA chip seems to matter. Wilko -- Wilko Bulte Arnhem, The Netherlands http://www.tcja.nl The FreeBSD Project: http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Mar 30 10:35:19 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 4001A37B56F for ; Thu, 30 Mar 2000 10:34:35 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id UAA13708; Thu, 30 Mar 2000 20:26:59 +0200 (MET DST) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id UAA01969; Thu, 30 Mar 2000 20:23:54 +0200 (CEST) (envelope-from wilko) Date: Thu, 30 Mar 2000 20:23:54 +0200 From: Wilko Bulte To: Andrew Gallatin Cc: nm , freebsd-alpha@freebsd.org Subject: Re: X Success With MGA and Sound Question Message-ID: <20000330202354.D1750@yedi.iaf.nl> Reply-To: wilko@freebsd.org References: <3.0.32.20000321153404.04d1cea0@mail.vt.edu> <14551.56679.73796.388364@grasshopper.cs.duke.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <14551.56679.73796.388364@grasshopper.cs.duke.edu>; from gallatin@cs.duke.edu on Tue, Mar 21, 2000 at 03:38:27PM -0500 X-OS: FreeBSD 3.4-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, Mar 21, 2000 at 03:38:27PM -0500, Andrew Gallatin wrote: > > Next up is getting the onboard audio on my AS200 to > > work. I assume I need to compile this into the kernel? > > > > Is the AS200's audio hardware supported? > > Yes, use this line in your config file: > > device pcm0 at isa? port 0x530 irq 9 drq 0 flags 0x10011 Right.. I just put this in HARDWARE.TXT because that one still said it did not work. > This worked just prior to 4.0-RELEASE, I haven't checked -RELEASE yet > on an AS200. My miata at home even runs xmms just fine ;-) Does this mean sound on both Miata MX5 and GL now works? Any specifics on the necessary kernel config entry? So that I can update HARDWARE.TXT Wilko -- Wilko Bulte Arnhem, The Netherlands http://www.tcja.nl The FreeBSD Project: http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Mar 30 10:39: 3 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 821F237B7FD; Thu, 30 Mar 2000 10:38:51 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id NAA04587; Thu, 30 Mar 2000 13:38:50 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id NAA02095; Thu, 30 Mar 2000 13:38:20 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Thu, 30 Mar 2000 13:38:19 -0500 (EST) To: wilko@freebsd.org Cc: freebsd-alpha@freebsd.org Subject: Re: X Success With MGA and Sound Question In-Reply-To: <20000330202354.D1750@yedi.iaf.nl> References: <3.0.32.20000321153404.04d1cea0@mail.vt.edu> <14551.56679.73796.388364@grasshopper.cs.duke.edu> <20000330202354.D1750@yedi.iaf.nl> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14563.40645.153010.202679@grasshopper.cs.duke.edu> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Wilko Bulte writes: > > This worked just prior to 4.0-RELEASE, I haven't checked -RELEASE yet > > on an AS200. My miata at home even runs xmms just fine ;-) > > Does this mean sound on both Miata MX5 and GL now works? Any > specifics on the necessary kernel config entry? So that I can update > HARDWARE.TXT They both have a soundblaster at the standard location. So you don't need to specify any ports, flags, etc. It Just Works. Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Mar 30 10:48:22 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 632D537BF8D; Thu, 30 Mar 2000 10:48:16 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id NAA04941; Thu, 30 Mar 2000 13:48:11 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id NAA02113; Thu, 30 Mar 2000 13:47:41 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Thu, 30 Mar 2000 13:47:41 -0500 (EST) To: wilko@FreeBSD.ORG Cc: Dave Haney , freebsd-alpha@FreeBSD.ORG Subject: Re: Unexpected machine check In-Reply-To: <20000330201513.A1750@yedi.iaf.nl> References: <20000330201513.A1750@yedi.iaf.nl> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14563.40742.553401.107502@grasshopper.cs.duke.edu> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Wilko Bulte writes: > > There is definitely a bogon somewhere as far as X on Alpha goes. The problem > seems to be core logic chipset related, people fortunate enough to own > Tsunami based systems do not seem to have these problems. Also the type of > VGA chip seems to matter. I suspect the real problem is bugs in the X server & that's why some cards (Matrox, 3DLabs Permedia) work and others don't. The Tsunami chipset itself just masks bugs. Like a PC, writes to invalid I/O ports, etc are ignored & reads return -1. Such accesses will cause machine checks on all other alphas. If somebody was to go through the effort of building one of these failing X servers with symbols, the PC mentioned in the machine check would likely be the PC of the offending instruction. Or close to it. In fact, I wonder if we couldn't hack up a kernel to send a sigbus to the offending X server & get a core dump rather than panicing. Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Mar 30 12:59: 7 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 3C3DA37B70E; Thu, 30 Mar 2000 12:59:02 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id WAA21478; Thu, 30 Mar 2000 22:53:05 +0200 (MET DST) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id WAA03729; Thu, 30 Mar 2000 22:22:45 +0200 (CEST) (envelope-from wilko) Date: Thu, 30 Mar 2000 22:22:45 +0200 From: Wilko Bulte To: Andrew Gallatin Cc: wilko@freebsd.org, freebsd-alpha@freebsd.org Subject: Re: X Success With MGA and Sound Question Message-ID: <20000330222244.D3560@yedi.iaf.nl> Reply-To: wilko@freebsd.org References: <3.0.32.20000321153404.04d1cea0@mail.vt.edu> <14551.56679.73796.388364@grasshopper.cs.duke.edu> <20000330202354.D1750@yedi.iaf.nl> <14563.40645.153010.202679@grasshopper.cs.duke.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <14563.40645.153010.202679@grasshopper.cs.duke.edu>; from gallatin@cs.duke.edu on Thu, Mar 30, 2000 at 01:38:19PM -0500 X-OS: FreeBSD 3.4-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, Mar 30, 2000 at 01:38:19PM -0500, Andrew Gallatin wrote: > > Wilko Bulte writes: > > > > This worked just prior to 4.0-RELEASE, I haven't checked -RELEASE yet > > > on an AS200. My miata at home even runs xmms just fine ;-) > > > > Does this mean sound on both Miata MX5 and GL now works? Any > > specifics on the necessary kernel config entry? So that I can update > > HARDWARE.TXT > > They both have a soundblaster at the standard location. So you > don't need to specify any ports, flags, etc. It Just Works. Could you please give me the line you have in your config file? I (for one.. ;-) am a bit confused by the soundcard world and I'd like to avoid aggravating that situation. A sample in HARDWARE.TXT would help I think (not having an alpha/conf/LINT) Wilko -- Wilko Bulte Arnhem, The Netherlands http://www.tcja.nl The FreeBSD Project: http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Mar 30 12:59:21 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id E7E6837B8D9; Thu, 30 Mar 2000 12:59:15 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id WAA21479; Thu, 30 Mar 2000 22:53:07 +0200 (MET DST) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id WAA04115; Thu, 30 Mar 2000 22:52:48 +0200 (CEST) (envelope-from wilko) Date: Thu, 30 Mar 2000 22:52:47 +0200 From: Wilko Bulte To: Andrew Gallatin Cc: wilko@freebsd.org, Dave Haney , freebsd-alpha@freebsd.org Subject: Re: Unexpected machine check Message-ID: <20000330225247.C3785@yedi.iaf.nl> Reply-To: wilko@freebsd.org References: <20000330201513.A1750@yedi.iaf.nl> <14563.40742.553401.107502@grasshopper.cs.duke.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <14563.40742.553401.107502@grasshopper.cs.duke.edu>; from gallatin@cs.duke.edu on Thu, Mar 30, 2000 at 01:47:41PM -0500 X-OS: FreeBSD 3.4-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, Mar 30, 2000 at 01:47:41PM -0500, Andrew Gallatin wrote: > Wilko Bulte writes: > > > > There is definitely a bogon somewhere as far as X on Alpha goes. The problem > > seems to be core logic chipset related, people fortunate enough to own > > Tsunami based systems do not seem to have these problems. Also the type of > > VGA chip seems to matter. > > I suspect the real problem is bugs in the X server & that's why some > cards (Matrox, 3DLabs Permedia) work and others don't. The Tsunami > chipset itself just masks bugs. Like a PC, writes to invalid I/O > ports, etc are ignored & reads return -1. Such accesses will cause > machine checks on all other alphas. > > If somebody was to go through the effort of building one of these > failing X servers with symbols, the PC mentioned in the machine check I'll try doing that next week. Is there anything special to do when building the port? > would likely be the PC of the offending instruction. Or close to it. Would that be back-traceable to if it is the X server or the kernel? > In fact, I wonder if we couldn't hack up a kernel to send a sigbus to > the offending X server & get a core dump rather than panicing. Sounds reasonable.. a panic is a bit drastic ;) -- Wilko Bulte Arnhem, The Netherlands http://www.tcja.nl The FreeBSD Project: http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Mar 30 13: 8:16 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id C02D137BF22; Thu, 30 Mar 2000 13:08:12 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id QAA10447; Thu, 30 Mar 2000 16:08:10 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id QAA02474; Thu, 30 Mar 2000 16:07:40 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Thu, 30 Mar 2000 16:07:40 -0500 (EST) To: wilko@freebsd.org Cc: Dave Haney , freebsd-alpha@freebsd.org Subject: Re: Unexpected machine check In-Reply-To: <20000330225247.C3785@yedi.iaf.nl> References: <20000330201513.A1750@yedi.iaf.nl> <14563.40742.553401.107502@grasshopper.cs.duke.edu> <20000330225247.C3785@yedi.iaf.nl> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14563.49235.18765.586441@grasshopper.cs.duke.edu> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Wilko Bulte writes: > > I'll try doing that next week. Is there anything special to do when > building the port? You'll need to mess with cflags to switch -O for -g. You do that in one of the xc/config/cf files. I'm not terribly good at building X, so I don't want to lead you astray by suggesting a particular file & being wrong. > > would likely be the PC of the offending instruction. Or close to it. > > Would that be back-traceable to if it is the X server or the kernel? Its the X server; running X doesn't change the kernel's behaviour very much. The X server is what's groping around in device memory. > > In fact, I wonder if we couldn't hack up a kernel to send a sigbus to > > the offending X server & get a core dump rather than panicing. > > Sounds reasonable.. a panic is a bit drastic ;) No, a panic is the correct behaviour. A unexpected, uncorrectable machine check is a sign that something very, very, very bad has happened. In 99.44% of the cases, you want the machine to panic on a machine check. I'm just suggesting a temporary, never-to-be-committed hack to allow you to debug the X server. Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Mar 30 16:58: 9 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 396AC37B528; Thu, 30 Mar 2000 16:58:02 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id TAA19210; Thu, 30 Mar 2000 19:58:01 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id TAA02967; Thu, 30 Mar 2000 19:57:31 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Thu, 30 Mar 2000 19:57:31 -0500 (EST) To: wilko@freebsd.org Cc: freebsd-alpha@freebsd.org Subject: Re: X Success With MGA and Sound Question In-Reply-To: <20000330222244.D3560@yedi.iaf.nl> References: <3.0.32.20000321153404.04d1cea0@mail.vt.edu> <14551.56679.73796.388364@grasshopper.cs.duke.edu> <20000330202354.D1750@yedi.iaf.nl> <14563.40645.153010.202679@grasshopper.cs.duke.edu> <20000330222244.D3560@yedi.iaf.nl> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14563.63272.683748.470595@grasshopper.cs.duke.edu> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Wilko Bulte writes: > On Thu, Mar 30, 2000 at 01:38:19PM -0500, Andrew Gallatin wrote: > > > They both have a soundblaster at the standard location. So you > > don't need to specify any ports, flags, etc. It Just Works. > > Could you please give me the line you have in your config file? I (for one.. > ;-) am a bit confused by the soundcard world and I'd like to avoid > aggravating that situation. A sample in HARDWARE.TXT would help I think > (not having an alpha/conf/LINT) My home machine (a GL running RC3) has the following in its config file: device pcm0 device sbc0 This probes as: sbc0: at port 0x220-0x22f irq 5 drq 1 on isa0 sbc0: interrupting at ISA irq 5 pcm0: on sbc0 % cat /dev/sndstat FreeBSD Audio Driver (newpcm) Mar 11 2000 00:21:46 Installed devices: pcm0: at io 0x220 irq 5 drq 1 (1p/1r channels) % ls -lF /dev/dsp lrwxrwxrwx 1 root wheel 4 Mar 11 20:56 /dev/dsp@ -> dsp0 This should be unchanged on 4.0-RELEASE Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Mar 30 23:28:23 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 632C537B957; Thu, 30 Mar 2000 23:28:21 -0800 (PST) (envelope-from jkoshy@FreeBSD.org) Received: (from jkoshy@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id XAA35578; Thu, 30 Mar 2000 23:28:21 -0800 (PST) (envelope-from jkoshy@FreeBSD.org) Date: Thu, 30 Mar 2000 23:28:21 -0800 (PST) From: Message-Id: <200003310728.XAA35578@freefall.freebsd.org> X-Mailer: exmh version 2.0.2 2/24/98 To: obrien@FreeBSD.org Cc: alpha@freebsd.org Subject: Re: Cross building Alpha on an i386 In-Reply-To: Your message of "Thu, 30 Mar 2000 08:26:45 PST." <20000330082645.B56425@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org d> What's ``uname -a'' on this box? Is the compiler before I did the major d> moving of configuration information from config/{i386,alpha}/freebsd.h to d> config/freebsd.h? It was a -current system of a few days ago. Anyhow I upgraded freshly and repeated the run with identical symptoms. foobar# uname -a FreeBSD foobar 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Fri Mar 31 12:30:27 GMT 2000 root@foobar:/home/src-current/sys/compile/OB47191-C i386 cc -O -pipe -I/home/src-current/lib/libmd -I/usr/obj/alpha/home/src-current/i386 /usr/include -c /home/src-current/lib/libmd/md2c.c -o md2c.o /home/src-current/lib/libmd/md2c.c: In function `MD2Final': /home/src-current/lib/libmd/md2c.c:167: internal error--unrecognizable insn: (insn 26 24 28 (set (reg:DI 79) (and:DI (plus:DI (reg/v:DI 69) (const_int 586461102752368432 [0x823874408238730])) (const_int -8 [0xfffffffffffffff8]))) -1 (insn_list 4 (nil)) (nil)) Regards, Koshy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Mar 30 23:36:10 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 5470837B986; Thu, 30 Mar 2000 23:36:07 -0800 (PST) (envelope-from obrien@NUXI.ucdavis.edu) Received: from dragon.nuxi.com (root@d60-024.leach.ucdavis.edu [169.237.60.24]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id XAA24089; Thu, 30 Mar 2000 23:36:06 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id XAA61139; Thu, 30 Mar 2000 23:36:06 -0800 (PST) (envelope-from obrien) Date: Thu, 30 Mar 2000 23:36:06 -0800 From: "David O'Brien" To: jkoshy@FreeBSD.org Cc: alpha@FreeBSD.org Subject: Re: Cross building Alpha on an i386 Message-ID: <20000330233606.A61105@dragon.nuxi.com> Reply-To: obrien@FreeBSD.org References: <20000330082645.B56425@dragon.nuxi.com> <200003310728.XAA35578@freefall.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <200003310728.XAA35578@freefall.freebsd.org>; from jkoshy@FreeBSD.org on Thu, Mar 30, 2000 at 11:28:21PM -0800 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, Mar 30, 2000 at 11:28:21PM -0800, jkoshy@FreeBSD.org wrote: > foobar# uname -a > FreeBSD foobar 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Fri Mar 31 12:30:27 GMT 2000 root@foobar:/home/src-current/sys/compile/OB47191-C i386 Can you back out my 23-March-2000 changes and see if you still have a problem? Specifically you want: Revision Path 1.48 src/gnu/usr.bin/cc/cc_tools/Makefile 1.31 src/gnu/lib/libgcc/Makefile 1.26 src/contrib/gcc/config/freebsd.h 1.34 src/contrib/gcc/config/i386/freebsd.h 1.9 src/contrib/gcc/config/alpha/freebsd.h To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Mar 31 8:34:38 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id B627937BB1D; Fri, 31 Mar 2000 08:34:30 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id SAA09150; Fri, 31 Mar 2000 18:24:18 +0200 (MET DST) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id SAA01617; Fri, 31 Mar 2000 18:19:46 +0200 (CEST) (envelope-from wilko) Date: Fri, 31 Mar 2000 18:19:46 +0200 From: Wilko Bulte To: Andrew Gallatin Cc: wilko@freebsd.org, Dave Haney , freebsd-alpha@freebsd.org Subject: Re: Unexpected machine check Message-ID: <20000331181946.D1351@yedi.iaf.nl> Reply-To: wilko@freebsd.org References: <20000330201513.A1750@yedi.iaf.nl> <14563.40742.553401.107502@grasshopper.cs.duke.edu> <20000330225247.C3785@yedi.iaf.nl> <14563.49235.18765.586441@grasshopper.cs.duke.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <14563.49235.18765.586441@grasshopper.cs.duke.edu>; from gallatin@cs.duke.edu on Thu, Mar 30, 2000 at 04:07:40PM -0500 X-OS: FreeBSD 3.4-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, Mar 30, 2000 at 04:07:40PM -0500, Andrew Gallatin wrote: > Wilko Bulte writes: > > > > I'll try doing that next week. Is there anything special to do when > > building the port? > > You'll need to mess with cflags to switch -O for -g. You do that in > one of the xc/config/cf files. I'm not terribly good at building X, > so I don't want to lead you astray by suggesting a particular file & > being wrong. OK, I'll see if I can make some time to mess around. > > Would that be back-traceable to if it is the X server or the kernel? > > Its the X server; running X doesn't change the kernel's behaviour very > much. The X server is what's groping around in device memory. OK. > > > In fact, I wonder if we couldn't hack up a kernel to send a sigbus to > > > the offending X server & get a core dump rather than panicing. > > > > Sounds reasonable.. a panic is a bit drastic ;) > > No, a panic is the correct behaviour. A unexpected, uncorrectable > machine check is a sign that something very, very, very bad has Let me clarify: drastic from the average user's perspective. If there is a way to nuke the offending process without taking down the machine with it (??? here) than that would be preferable. I have no idea if one can selectively do this, and if it is worth doing in the first place. X servers are 'special' in the sense that they are very intimate with the hardware (right?). > happened. In 99.44% of the cases, you want the machine to panic on a > machine check. I'm just suggesting a temporary, never-to-be-committed > hack to allow you to debug the X server. Sure. -- Wilko Bulte Arnhem, The Netherlands http://www.tcja.nl The FreeBSD Project: http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Mar 31 8:56:56 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 4C62B37B919; Fri, 31 Mar 2000 08:56:53 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id LAA16275; Fri, 31 Mar 2000 11:56:49 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id LAA04508; Fri, 31 Mar 2000 11:56:18 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Fri, 31 Mar 2000 11:56:18 -0500 (EST) To: wilko@FreeBSD.ORG Cc: Andrew Gallatin , Dave Haney , freebsd-alpha@FreeBSD.ORG Subject: Re: Unexpected machine check In-Reply-To: <20000331181946.D1351@yedi.iaf.nl> References: <20000330201513.A1750@yedi.iaf.nl> <14563.40742.553401.107502@grasshopper.cs.duke.edu> <20000330225247.C3785@yedi.iaf.nl> <14563.49235.18765.586441@grasshopper.cs.duke.edu> <20000331181946.D1351@yedi.iaf.nl> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14564.55164.916097.475755@grasshopper.cs.duke.edu> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Wilko Bulte writes: > > No, a panic is the correct behaviour. A unexpected, uncorrectable > > machine check is a sign that something very, very, very bad has > > Let me clarify: drastic from the average user's perspective. If there is a > way to nuke the offending process without taking down the machine with it > (??? here) than that would be preferable. I have no idea if one can > selectively do this, and if it is worth doing in the first place. X servers > are 'special' in the sense that they are very intimate with the hardware > (right?). The problem is that machine checks can be asynchronous & may be caused by devices going insane, so, in general, the fact that a user process was running doesn't mean much. Combined with the fact that you may not know what caused a machine check, its pretty hard to be selective. A developer debugging an X server is a very special case. Cheers, Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message