From owner-freebsd-alpha Sun Sep 26 11: 7:43 1999 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 72B51152C7; Sun, 26 Sep 1999 11:07:41 -0700 (PDT) (envelope-from wwoods@cybcon.com) Received: from freebsd.cybcon.com (pm3a-25.cybcon.com [205.147.75.154]) by mail.cybcon.com (8.9.0/8.9.0) with SMTP id LAA25022; Sun, 26 Sep 1999 11:07:32 -0700 (PDT) From: william woods Reply-To: wwoods@cybcon.com To: Mike Smith , wwoods@cybcon.com Subject: Re: NFS Problems.... Date: Sat, 25 Sep 1999 22:34:34 -0700 X-Mailer: KMail [version 1.0.28] Content-Type: text/plain Cc: freebsd-question@freebsd.org, freebsd-alpha@freebsd.org References: <199909251838.LAA06870@dingo.cdrom.com> In-Reply-To: <199909251838.LAA06870@dingo.cdrom.com> MIME-Version: 1.0 Message-Id: <99092522350400.00333@freebsd.cybcon.com> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hmmm....I can ping either system from the other though...how can it be busted? On Sat, 25 Sep 1999, Mike Smith wrote: > > I am trying to set up a client and server with NFS mounting.....here are the > > pertenant parts of rc.conf for each. The ptroblem I am haveing is that the > > rpc.lockd and rpc.statd hang the server system on boot.... > > Your name resolution setup is busted. You probably want some seed > entries in /etc/hosts and a tweak to host.conf. > > -- > \\ The mind's the standard \\ Mike Smith > \\ of the man. \\ msmith@freebsd.org > \\ -- Joseph Merrick \\ msmith@cdrom.com -- William Woods FreeBSD 3.3-Stable -----BEGIN GEEK CODE BLOCK----- Version: 3.1 GIT d++ s+:+ a C+++ UB+++ P+ L++ E- W++ N+ o+ K- w O- M-- V PS-- PE++ Y+ PGP t+ 5+ X R- tv- b++ DI+ D G e++ h---- r+++ y++++ ------END GEEK CODE BLOCK------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Sep 27 6:41: 8 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from metzelkueche.tabu.uni-bonn.de (metzelkueche.tabu.uni-bonn.de [131.220.159.242]) by hub.freebsd.org (Postfix) with ESMTP id 8BD3D14A20 for ; Mon, 27 Sep 1999 06:40:44 -0700 (PDT) (envelope-from armin@metzelkueche.tabu.uni-bonn.de) Received: from localhost (localhost [127.0.0.1]) by metzelkueche.tabu.uni-bonn.de (8.9.3/8.9.3) with ESMTP id PAA18883; Mon, 27 Sep 1999 15:40:05 +0200 Date: Mon, 27 Sep 1999 15:40:05 +0200 (MEST) From: Armin Ollig X-Sender: armin@metzelkueche.tabu.uni-bonn.de To: Oliver.Kowalke@freudenberg.de Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: Linux + FreeBSD on alpha (lx164) 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 oliver, afaik SRM cannot boot from ide devices. Either boot from floppy or get a cheap NCR53810. I had to try several cards. The ASUS board with the 53810 chip does **NOT** work. I finally found one board which does work. I think its made by symbios. It has little dolphins on the board :-) and works well. best regards, --armin -- "To save energy the light at the end of the tunnel will temporarily be switched off." On Thu, 23 Sep 1999 Oliver.Kowalke@freudenberg.de wrote: > Hi, > > is it possible to run Linux and Freebsd on the same IDE harddisk (srm > console supports booting from IDE drive!) ? Is a bootloader available which > will to that? > What's with the PAL code > > thx!, > Oliver > > > 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 Mon Sep 27 10:42:24 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from helmholtz.salk.edu (helmholtz.salk.edu [198.202.70.34]) by hub.freebsd.org (Postfix) with ESMTP id B770F15717 for ; Mon, 27 Sep 1999 10:41:03 -0700 (PDT) (envelope-from bartol@salk.edu) Received: from eccles.salk.edu (eccles [198.202.70.120]) by helmholtz.salk.edu (8.7.5/8.7.3) with ESMTP id KAA17042; Mon, 27 Sep 1999 10:41:01 -0700 (PDT) Date: Mon, 27 Sep 1999 10:41:03 -0700 (PDT) From: Tom Bartol To: freebsd-alpha@freebsd.org Cc: Jack Wathey Subject: Status of XFree86 on Alpha? 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 Hi, I've been trying to build and run Xfree86 on FreeBSD-current for the Alpha and have run into several problems I'd like to report and compare notes on. Please CC me and wathey@salk.edu on your responses directly as we aren't (yet) subscribed to freebsd-alpha. We are running FreeBSD-current for Alpha as of 19990923 and have cvsupped our ports tree on that date as well. The machine is a 533MHz PC164LX with 64MB RAM and a Matrox Millenium II with 4MB. Problems/Observations: 1) We could "make" XFree86 but a "make install" failed due to a missing /usr/include/sys/pci_ioctl.h. We noticed that patch-4 for for /usr/port/x11/XFree86 includes a patch to "#include " however this file does not exist in /usr/include/sys on our system. "make world" in /usr/src does not install this file. We found the file in /usr/src/sys/pci and copied it by hand to /usr/include/sys. After this a "make install" for XFree86 succeeded. FreeBSD for Intel does not have this file in /usr/include/sys and XFree86 does not require it on Intel. 2) SuperProbe segfaults. gdb doesn't like the core file so we have no clue about the problem here. 3) We configured X to run the X_SVGA server for our Matrox Millenium II. The server starts up fine but some windows are filled with black and menus pop up empty until you run the mouse cursor over the locations where the text should be. Can anyone tell us if this is normal for the current status of XFree86 for FreeBSD-current on the Alpha. I scanned the freebsd-alpha mail archive but could glean any insights into this matter. Is there some miss configuration on our system causing pci_ioctl.h to be skipped during a "make world"? Should we be using a different brand of video card? Thanks for your help, Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Sep 27 11:23:56 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from mail.HiWAAY.net (fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (Postfix) with ESMTP id E5F7114C02 for ; Mon, 27 Sep 1999 11:23:51 -0700 (PDT) (envelope-from sprice@hiwaay.net) Received: from localhost (sprice@localhost) by mail.HiWAAY.net (8.9.1a/8.9.0) with ESMTP id NAA21759; Mon, 27 Sep 1999 13:23:46 -0500 (CDT) Date: Mon, 27 Sep 1999 13:23:46 -0500 (CDT) From: Steve Price To: Tom Bartol Cc: freebsd-alpha@FreeBSD.ORG, Jack Wathey Subject: Re: Status of XFree86 on Alpha? 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 Sep 1999, Tom Bartol wrote: # Problems/Observations: # # 1) We could "make" XFree86 but a "make install" failed due to a missing # /usr/include/sys/pci_ioctl.h. We noticed that patch-4 for for # /usr/port/x11/XFree86 includes a patch to "#include " # however this file does not exist in /usr/include/sys on our system. # "make world" in /usr/src does not install this file. We found the file in # /usr/src/sys/pci and copied it by hand to /usr/include/sys. After this a # "make install" for XFree86 succeeded. FreeBSD for Intel does not have # this file in /usr/include/sys and XFree86 does not require it on Intel. Hmm... I'll look into this tonight. I'm pretty sure I did a 'make -DCLOBBER world' last time, but maybe I didn't. # 2) SuperProbe segfaults. gdb doesn't like the core file so we have no # clue about the problem here. This is a known problem. Just a matter of porting the VGA16 server to FreeBSD/Alpha. Any volunteers? :) # 3) We configured X to run the X_SVGA server for our Matrox Millenium II. # The server starts up fine but some windows are filled with black and # menus pop up empty until you run the mouse cursor over the locations where # the text should be. This one is new to me. I don't have a head on my Alpha box at home, but it sounds like I need free up a monitor so I can look into this and a couple of other problems I've been seeing. # Can anyone tell us if this is normal for the current status of XFree86 for # FreeBSD-current on the Alpha. I scanned the freebsd-alpha mail archive # but could glean any insights into this matter. Is there some miss # configuration on our system causing pci_ioctl.h to be skipped during a # "make world"? Should we be using a different brand of video card? This could be caused by bogus definitions in pci_ioctl.h. Give me some time later tonight and I'll see what I can do about getting the port to build without pci_ioctl.h. -steve # Thanks for your help, # # Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Sep 27 13:10:50 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from helmholtz.salk.edu (helmholtz.salk.edu [198.202.70.34]) by hub.freebsd.org (Postfix) with ESMTP id C037215597 for ; Mon, 27 Sep 1999 13:10:46 -0700 (PDT) (envelope-from bartol@salk.edu) Received: from eccles.salk.edu (eccles [198.202.70.120]) by helmholtz.salk.edu (8.7.5/8.7.3) with ESMTP id NAA19607; Mon, 27 Sep 1999 13:10:37 -0700 (PDT) Date: Mon, 27 Sep 1999 13:10:39 -0700 (PDT) From: Tom Bartol To: Steve Price Cc: freebsd-alpha@FreeBSD.ORG, Jack Wathey Subject: Re: Status of XFree86 on Alpha? 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 Steve, Thank you for the very rapid response! On Mon, 27 Sep 1999, Steve Price wrote: > On Mon, 27 Sep 1999, Tom Bartol wrote: > > # Problems/Observations: > # > # 1) We could "make" XFree86 but a "make install" failed due to a missing > # /usr/include/sys/pci_ioctl.h. We noticed that patch-4 for for > # /usr/port/x11/XFree86 includes a patch to "#include " > # however this file does not exist in /usr/include/sys on our system. > # "make world" in /usr/src does not install this file. We found the file in > # /usr/src/sys/pci and copied it by hand to /usr/include/sys. After this a > # "make install" for XFree86 succeeded. FreeBSD for Intel does not have > # this file in /usr/include/sys and XFree86 does not require it on Intel. > > Hmm... I'll look into this tonight. I'm pretty sure I did a > 'make -DCLOBBER world' last time, but maybe I didn't. > Yeah, I suspected something like this might be the explanation. > # 2) SuperProbe segfaults. gdb doesn't like the core file so we have no > # clue about the problem here. > > This is a known problem. Just a matter of porting the VGA16 > server to FreeBSD/Alpha. Any volunteers? :) > O.K. I wish I weren't so bogged down with my "Real Job". > # 3) We configured X to run the X_SVGA server for our Matrox Millenium II. > # The server starts up fine but some windows are filled with black and > # menus pop up empty until you run the mouse cursor over the locations where > # the text should be. > > This one is new to me. I don't have a head on my Alpha box > at home, but it sounds like I need free up a monitor so I can > look into this and a couple of other problems I've been seeing. > > # Can anyone tell us if this is normal for the current status of XFree86 for > # FreeBSD-current on the Alpha. I scanned the freebsd-alpha mail archive > # but could glean any insights into this matter. Is there some miss > # configuration on our system causing pci_ioctl.h to be skipped during a > # "make world"? Should we be using a different brand of video card? > > This could be caused by bogus definitions in pci_ioctl.h. Give > me some time later tonight and I'll see what I can do about getting > the port to build without pci_ioctl.h. > O.K. We'll wait to hear from you. Thanks a million! > -steve > > # Thanks for your help, > # > # Tom > > Many thanks, Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Sep 27 13:13:25 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from maile.telia.com (maile.telia.com [194.22.190.16]) by hub.freebsd.org (Postfix) with ESMTP id 8326A15660 for ; Mon, 27 Sep 1999 13:12:41 -0700 (PDT) (envelope-from khaled@mailbox.telia.net) Received: from mailbox.telia.net (khaled@mailbox.telia.net [194.237.170.234]) by maile.telia.com (8.8.5/8.8.8) with ESMTP id WAA16403; Mon, 27 Sep 1999 22:12:32 +0200 (CEST) Received: from localhost (khaled@localhost) by mailbox.telia.net (8.9.1/8.8.5) with SMTP id WAA11906; Mon, 27 Sep 1999 22:12:39 +0200 (CEST) Date: Mon, 27 Sep 1999 22:12:38 +0200 (CEST) From: Khaled Daham To: Steve Price Cc: Tom Bartol , freebsd-alpha@FreeBSD.ORG, Jack Wathey Subject: Re: Status of XFree86 on Alpha? 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 Sep 1999, Steve Price wrote: > On Mon, 27 Sep 1999, Tom Bartol wrote: > > # 3) We configured X to run the X_SVGA server for our Matrox Millenium II. > # The server starts up fine but some windows are filled with black and > # menus pop up empty until you run the mouse cursor over the locations where > # the text should be. > > This one is new to me. I don't have a head on my Alpha box > at home, but it sounds like I need free up a monitor so I can > look into this and a couple of other problems I've been seeing. I have used matrox mill II and g200 cards (both 8MB) since the 1999-02-xy snap , as of now I use Sep 16 world and XFree3.3.5 , Ive never seen these problems.I use 1280x1024@85Hz,16bpp and windowmaker ( fvwm2 doesnt really work that well ) /Khaled, Telia Network Services Mail: khaled@telia.net Cell: 070-6785492 Work: 08-4567281 :hacker: /n./ [originally, someone who makes furniture with an axe] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Sep 27 13:19:11 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from helmholtz.salk.edu (helmholtz.salk.edu [198.202.70.34]) by hub.freebsd.org (Postfix) with ESMTP id 1EF881557C for ; Mon, 27 Sep 1999 13:19:07 -0700 (PDT) (envelope-from bartol@salk.edu) Received: from eccles.salk.edu (eccles [198.202.70.120]) by helmholtz.salk.edu (8.7.5/8.7.3) with ESMTP id NAA19758; Mon, 27 Sep 1999 13:19:00 -0700 (PDT) Date: Mon, 27 Sep 1999 13:19:02 -0700 (PDT) From: Tom Bartol To: Khaled Daham Cc: Steve Price , freebsd-alpha@FreeBSD.ORG, Jack Wathey Subject: Re: Status of XFree86 on Alpha? 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 Khaled, Thanks for the data point! Tom On Mon, 27 Sep 1999, Khaled Daham wrote: > On Mon, 27 Sep 1999, Steve Price wrote: > > > On Mon, 27 Sep 1999, Tom Bartol wrote: > > > > # 3) We configured X to run the X_SVGA server for our Matrox Millenium II. > > # The server starts up fine but some windows are filled with black and > > # menus pop up empty until you run the mouse cursor over the locations where > > # the text should be. > > > > This one is new to me. I don't have a head on my Alpha box > > at home, but it sounds like I need free up a monitor so I can > > look into this and a couple of other problems I've been seeing. > > I have used matrox mill II and g200 cards (both 8MB) since the 1999-02-xy > snap , as of now I use Sep 16 world and XFree3.3.5 , Ive never seen these > problems.I use 1280x1024@85Hz,16bpp and windowmaker ( fvwm2 doesnt really > work that well ) > > /Khaled, Telia Network Services > > Mail: khaled@telia.net > Cell: 070-6785492 > Work: 08-4567281 > > :hacker: /n./ [originally, someone who makes furniture with an axe] > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Sep 27 16:30:49 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from friley-160-236.res.iastate.edu (friley-160-236.res.iastate.edu [129.186.160.236]) by hub.freebsd.org (Postfix) with ESMTP id 0057814A2D for ; Mon, 27 Sep 1999 16:30:47 -0700 (PDT) (envelope-from cc@137.org) Received: from ameslab.gov (friley-160-235.res.iastate.edu [129.186.160.235]) by friley-160-236.res.iastate.edu (Postfix) with ESMTP id 9466D119; Mon, 27 Sep 1999 18:30:44 -0500 (CDT) Message-ID: <37EFFE24.9D632BEC@ameslab.gov> Date: Mon, 27 Sep 1999 18:30:44 -0500 From: Chris Csanady X-Mailer: Mozilla 4.61 [en] (X11; U; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en, ru, ja, ko MIME-Version: 1.0 To: Armin Ollig Cc: Oliver.Kowalke@freudenberg.de, freebsd-alpha@FreeBSD.ORG Subject: Re: Linux + FreeBSD on alpha (lx164) References: Content-Type: text/plain; charset=iso-2022-jp Content-Transfer-Encoding: 7bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Armin Ollig wrote: > > oliver, > > afaik SRM cannot boot from ide devices. > Either boot from floppy or get a cheap NCR53810. > I had to try several cards. The ASUS board with the 53810 chip does > **NOT** work. I finally found one board which does work. I think its > made by symbios. It has little dolphins on the board :-) > and works well. As early as v5.1, the SRM console will boot IDE devices. I ran NetBSD/alpha on an lx164 a long long time ago. :) Also, I have found that the Tekram cards based on the 53c875 work fine as well. Chris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Sep 27 18:55:25 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from mail.HiWAAY.net (fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (Postfix) with ESMTP id A55A514DDF; Mon, 27 Sep 1999 18:55:03 -0700 (PDT) (envelope-from sprice@hiwaay.net) Received: from localhost (sprice@localhost) by mail.HiWAAY.net (8.9.1a/8.9.0) with ESMTP id UAA31957; Mon, 27 Sep 1999 20:55:02 -0500 (CDT) Date: Mon, 27 Sep 1999 20:55:02 -0500 (CDT) From: Steve Price To: freebsd-alpha@freebsd.org Cc: phk@freebsd.org Subject: Alpha kernel builds falling over 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 Hi all, Anyone mind if I commit the following patch? The removal of "NBPF conditionality" seems to have left kernel builds falling over. The last 3 hunks accomodate interface changes in the bpf* routines. -steve Index: am7990.c =================================================================== RCS file: /home/ncvs/src/sys/alpha/tc/am7990.c,v retrieving revision 1.6 diff -u -r1.6 am7990.c --- am7990.c 1999/09/25 12:05:44 1.6 +++ am7990.c 1999/09/28 01:34:49 @@ -78,7 +78,6 @@ */ #include "opt_inet.h" -#include #include #include #include @@ -103,6 +102,7 @@ #ifdef INET #include #endif +#include #include #include @@ -226,7 +226,7 @@ if_attach(ifp); ether_ifattach(ifp); - bpfattach(&ifp->if_bpf, ifp, DLT_EN10MB, sizeof(struct ether_header)); + bpfattach(ifp, DLT_EN10MB, sizeof(struct ether_header)); switch (sc->sc_memsize) { case 8192: @@ -563,7 +563,7 @@ * If so, hand off the raw packet to BPF. */ if (ifp->if_bpf) { - bpf_mtap(ifp->if_bpf, m); + bpf_mtap(ifp, m); #ifndef LANCE_REVC_BUG /* @@ -919,7 +919,7 @@ * before we commit it to the wire. */ if (ifp->if_bpf) - bpf_mtap(ifp->if_bpf, m); + bpf_mtap(ifp, m); /* * Copy the mbuf chain into the transmit buffer. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Sep 27 22:48:35 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from mail.du.gtn.com (mail.du.gtn.com [194.77.9.57]) by hub.freebsd.org (Postfix) with ESMTP id 8BDDE14F0E for ; Mon, 27 Sep 1999 22:48:32 -0700 (PDT) (envelope-from ticso@cicely8.cicely.de) Received: from mail.cicely.de (cicely.de [194.231.9.142]) by mail.du.gtn.com (8.9.3/8.9.3) with ESMTP id HAA22243 for ; Tue, 28 Sep 1999 07:44:49 +0200 (MET DST) Received: from cicely8.cicely.de (cicely8.cicely.de [10.1.2.10]) by mail.cicely.de (8.9.0/8.9.0) with ESMTP id HAA30200 for ; Tue, 28 Sep 1999 07:49:03 +0200 (CEST) Received: (from ticso@localhost) by cicely8.cicely.de (8.9.3/8.9.2) id HAA82300 for freebsd-alpha@freebsd.org; Tue, 28 Sep 1999 07:49:08 +0200 (CEST) (envelope-from ticso) Date: Tue, 28 Sep 1999 07:49:07 +0200 From: Bernd Walter To: freebsd-alpha@freebsd.org Subject: buildworld failure: Unsupported relocation type 0 in non-PLT relocations Message-ID: <19990928074907.A82227@cicely8.cicely.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org During buildworld I got the following error in several places: /usr/libexec/ld-elf.so.1: /usr/obj/usr/src-1999-09-26/src/tmp/usr/lib/libc.so.3: Unsupported relocation type 0 in non-PLT relocations The system I wanted to compile it on is running current from 9th juli -- B.Walter COSMO-Project http://www.cosmo-project.de ticso@cicely.de Usergroup info@cosmo-project.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Sep 27 23:41:39 1999 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 F413414F2A for ; Mon, 27 Sep 1999 23:41:37 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id AAA00862; Tue, 28 Sep 1999 00:41:31 -0600 (MDT) (envelope-from ken) Message-Id: <199909280641.AAA00862@panzer.kdm.org> Subject: Re: buildworld failure: Unsupported relocation type 0 in non-PLT relocations In-Reply-To: <19990928074907.A82227@cicely8.cicely.de> from Bernd Walter at "Sep 28, 1999 07:49:07 am" To: ticso@cicely.de (Bernd Walter) Date: Tue, 28 Sep 1999 00:41:31 -0600 (MDT) Cc: freebsd-alpha@FreeBSD.ORG From: "Kenneth D. Merry" X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Bernd Walter wrote... > > > During buildworld I got the following error in several places: > /usr/libexec/ld-elf.so.1: /usr/obj/usr/src-1999-09-26/src/tmp/usr/lib/libc.so.3: Unsupported relocation type 0 in non-PLT relocations > The system I wanted to compile it on is running current from 9th juli You need to manually reinstall ld-elf.so.1 and then continue your buildworld. (it's located in src/libexec/rtld-elf) 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 Sep 28 1:54: 2 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 9365F15540 for ; Tue, 28 Sep 1999 01:53:57 -0700 (PDT) (envelope-from dfr@nlsystems.com) 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 JAA08463; Tue, 28 Sep 1999 09:56:39 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Tue, 28 Sep 1999 09:56:39 +0100 (BST) From: Doug Rabson To: Chris Csanady Cc: Armin Ollig , Oliver.Kowalke@freudenberg.de, freebsd-alpha@freebsd.org Subject: Re: Linux + FreeBSD on alpha (lx164) In-Reply-To: <37EFFE24.9D632BEC@ameslab.gov> 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 Sep 1999, Chris Csanady wrote: > Armin Ollig wrote: > > > > oliver, > > > > afaik SRM cannot boot from ide devices. > > Either boot from floppy or get a cheap NCR53810. > > I had to try several cards. The ASUS board with the 53810 chip does > > **NOT** work. I finally found one board which does work. I think its > > made by symbios. It has little dolphins on the board :-) > > and works well. > > As early as v5.1, the SRM console will boot IDE devices. I ran > NetBSD/alpha on an lx164 a long long time ago. :) Also, I have found > that the Tekram cards based on the 53c875 work fine as well. I'm pretty sure it boots IDE disks but I can't get my Miata to boot from an IDE cdrom though. -- 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 Tue Sep 28 7:53:22 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from fuzzy.helloworld.org (adsl-216-62-132-139.dsl.hstntx.swbell.net [216.62.132.139]) by hub.freebsd.org (Postfix) with ESMTP id 21B781550F for ; Tue, 28 Sep 1999 07:53:15 -0700 (PDT) (envelope-from jon@fuzzy.helloworld.org) Received: from adsl-216-62-132-139.dsl.hstntx.swbell.net (adsl-216-62-132-139.dsl.hstntx.swbell.net [216.62.132.139]) by fuzzy.helloworld.org (8.9.1b+Sun/8.9.1) with ESMTP id JAA03646 for ; Tue, 28 Sep 1999 09:54:03 -0500 (CDT) Date: Tue, 28 Sep 1999 09:54:03 -0500 (CDT) From: Jon To: freebsd-alpha@FreeBSD.ORG Subject: linking and X11 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 I am trying to compile X11R6.4 on 4.0-19990915-CURRENT. I have an alpha server 400/233 (Avanti). The compile is actually going okay but the linking is not. The linker is not behaving the way I expect it to. The compile creates a SO that is libXt.so.6.0 but when I try to link against it with -lXt I get "unknown object" or whatever the error message is when it can't find a shared object. Only when I create a symlink to it that is libXt.so will it find the shared object. Do I just need to give gcc/ld more options or what? Thanx for any help you can give. Jon Rowell To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Sep 28 9:46:33 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from out4.prserv.net (out4.prserv.net [165.87.194.239]) by hub.freebsd.org (Postfix) with ESMTP id 3E92E15798 for ; Tue, 28 Sep 1999 09:46:23 -0700 (PDT) (envelope-from dermot@mcnally.de) Received: from TIGGER ([139.92.4.192]) by out4.prserv.net (/) with ESMTP id QAA33002; Tue, 28 Sep 1999 16:46:15 GMT Message-Id: <4.2.0.58.19990928183931.00ac7270@tim> X-Sender: dermot@tim X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 Date: Tue, 28 Sep 1999 18:42:09 +0200 To: Tom Bartol From: Dermot McNally Subject: Re: Status of XFree86 on Alpha? Cc: freebsd-alpha@FreeBSD.ORG In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Just to add my experience to the picture: At 10:41 27/09/99 -0700, Tom Bartol wrote: >1) We could "make" XFree86 but a "make install" failed due to a missing >/usr/include/sys/pci_ioctl.h. We noticed that patch-4 for for >/usr/port/x11/XFree86 includes a patch to "#include " >however this file does not exist in /usr/include/sys on our system. >"make world" in /usr/src does not install this file. We found the file in >/usr/src/sys/pci and copied it by hand to /usr/include/sys. After this a >"make install" for XFree86 succeeded. FreeBSD for Intel does not have >this file in /usr/include/sys and XFree86 does not require it on Intel. Yup, same here, and the same solution. >3) We configured X to run the X_SVGA server for our Matrox Millenium II. >The server starts up fine but some windows are filled with black and >menus pop up empty until you run the mouse cursor over the locations where >the text should be. Exactly the same symptoms here. It's a 2 Meg Matrox Millenium, and the box, FWIW, is a DEC Personal Workstation 433. Cheers, Dermot To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Sep 28 10:37:45 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 6F96F1556C for ; Tue, 28 Sep 1999 10:37:42 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.8.7/8.8.7) with ESMTP id KAA04645; Tue, 28 Sep 1999 10:36:15 -0700 Date: Tue, 28 Sep 1999 10:36:15 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Doug Rabson Cc: Chris Csanady , Armin Ollig , Oliver.Kowalke@freudenberg.de, freebsd-alpha@FreeBSD.ORG Subject: Re: Linux + FreeBSD on alpha (lx164) 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 > > > > > > oliver, > > > > > > afaik SRM cannot boot from ide devices. > > > Either boot from floppy or get a cheap NCR53810. > > > I had to try several cards. The ASUS board with the 53810 chip does > > > **NOT** work. I finally found one board which does work. I think its > > > made by symbios. It has little dolphins on the board :-) > > > and works well. > > > > As early as v5.1, the SRM console will boot IDE devices. I ran > > NetBSD/alpha on an lx164 a long long time ago. :) Also, I have found > > that the Tekram cards based on the 53c875 work fine as well. > > I'm pretty sure it boots IDE disks but I can't get my Miata to boot from > an IDE cdrom though. boots dqa0 for me on my pc164.. haven'd tried cdrom either To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Sep 28 11:43:24 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from helmholtz.salk.edu (helmholtz.salk.edu [198.202.70.34]) by hub.freebsd.org (Postfix) with ESMTP id CEDFD14EBB for ; Tue, 28 Sep 1999 11:43:18 -0700 (PDT) (envelope-from bartol@salk.edu) Received: from eccles.salk.edu (eccles [198.202.70.120]) by helmholtz.salk.edu (8.7.5/8.7.3) with ESMTP id LAA06346; Tue, 28 Sep 1999 11:43:16 -0700 (PDT) Date: Tue, 28 Sep 1999 11:43:18 -0700 (PDT) From: Tom Bartol To: Dermot McNally Cc: freebsd-alpha@FreeBSD.ORG, Jack Wathey Subject: Re: Status of XFree86 on Alpha? In-Reply-To: <4.2.0.58.19990928183931.00ac7270@tim> 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 Thanks for the feedback! Tom On Tue, 28 Sep 1999, Dermot McNally wrote: > Just to add my experience to the picture: > > At 10:41 27/09/99 -0700, Tom Bartol wrote: > > > >1) We could "make" XFree86 but a "make install" failed due to a missing > >/usr/include/sys/pci_ioctl.h. We noticed that patch-4 for for > >/usr/port/x11/XFree86 includes a patch to "#include " > >however this file does not exist in /usr/include/sys on our system. > >"make world" in /usr/src does not install this file. We found the file in > >/usr/src/sys/pci and copied it by hand to /usr/include/sys. After this a > >"make install" for XFree86 succeeded. FreeBSD for Intel does not have > >this file in /usr/include/sys and XFree86 does not require it on Intel. > > Yup, same here, and the same solution. > > > >3) We configured X to run the X_SVGA server for our Matrox Millenium II. > >The server starts up fine but some windows are filled with black and > >menus pop up empty until you run the mouse cursor over the locations where > >the text should be. > > Exactly the same symptoms here. It's a 2 Meg Matrox Millenium, and the box, > FWIW, is a DEC Personal Workstation 433. > > Cheers, > Dermot > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Sep 28 16:51:29 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from netscape.com (h-205-217-237-47.netscape.com [205.217.237.47]) by hub.freebsd.org (Postfix) with ESMTP id A8CED14D01 for ; Tue, 28 Sep 1999 16:51:27 -0700 (PDT) (envelope-from rose@netscape.com) Received: from mail.npec.netscape.com (arches.npec.netscape.com [205.217.234.197]) by netscape.com (8.8.5/8.8.5) with ESMTP id QAA27072 for ; Tue, 28 Sep 1999 16:51:26 -0700 (PDT) Received: from mihoshi.npec.netscape.com ([205.217.236.202]) by mail.npec.netscape.com (Netscape Messaging Server 3.01) with ESMTP id AAA5676 for ; Tue, 28 Sep 1999 16:51:26 -0700 Date: Tue, 28 Sep 1999 16:50:36 -0700 (PDT) From: Steve Rose X-Sender: rose@mihoshi.npec.netscape.com To: freebsd-alpha@FreeBSD.ORG Subject: Well, FreeBSD succumbed to Tinderbox as well.... (fwd) 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 We've just installed 3.3 Release on an Alphastation 200 for continuous Mozilla builds. Does this suggest known problem? Failing that, are there any suggestions on how to gather more information about this? Steve Rose ---------- Forwarded message ---------- Date: Tue, 28 Sep 1999 15:31:43 -0700 (PDT) From: Brian Ostrom To: rose@netscape.com Cc: briano@netscape.com Subject: Well, FreeBSD succumbed to Tinderbox as well.... Damn..., it was looking so good, too. Almost 24 hours without a problem. Oh well. Here's all the crash data I have: Sep 28 15:28:24 sniper /kernel: panic: pmap_remove_all: pv_table for 1acc000 is inconsistent Sep 28 15:28:24 sniper /kernel: Sep 28 15:28:24 sniper /kernel: syncing disks... 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 giving up Sep 28 15:28:24 sniper /kernel: Automatic reboot in 15 seconds - press a key on the console to abort Sep 28 15:28:24 sniper /kernel: Rebooting... All it was doing was trying to compile mozilla. briano. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Sep 29 1:18:14 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 33874155A7 for ; Wed, 29 Sep 1999 01:17:47 -0700 (PDT) (envelope-from dfr@nlsystems.com) 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 JAA46779; Wed, 29 Sep 1999 09:20:54 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Wed, 29 Sep 1999 09:20:54 +0100 (BST) From: Doug Rabson To: Steve Rose Cc: freebsd-alpha@freebsd.org Subject: Re: Well, FreeBSD succumbed to Tinderbox as well.... (fwd) 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 Tue, 28 Sep 1999, Steve Rose wrote: > We've just installed 3.3 Release on an Alphastation 200 for continuous > Mozilla builds. Does this suggest known problem? Failing that, are there > any suggestions on how to gather more information about this? I think this was fixed in current a while ago. I'm trying to track down exactly what the problem was so that I can back-port the fix to 3.3. -- 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 Thu Sep 30 18:39:59 1999 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 CD34C14EA9 for ; Thu, 30 Sep 1999 18:39:51 -0700 (PDT) (envelope-from don@calis.blacksun.org) Received: from localhost (don@localhost) by calis.blacksun.org (8.9.3/8.9.2) with ESMTP id VAA00671 for ; Thu, 30 Sep 1999 21:40:37 -0400 (EDT) (envelope-from don@calis.blacksun.org) Date: Thu, 30 Sep 1999 21:40:37 -0400 (EDT) From: Don To: alpha@freebsd.org Subject: Supported ethernet cards 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 Quick question: Do we have a supported hardware list yet? Specifically I am interested in ethernet cards. Also: I am looking to make an AS200 into a firewall running ipf*. Has anyone done this and had any success or failure attempting to do so? -Don To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Oct 1 1:55: 3 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id C63F315208 for ; Fri, 1 Oct 1999 01:54:57 -0700 (PDT) (envelope-from dfr@nlsystems.com) 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 JAA48355; Fri, 1 Oct 1999 09:58:25 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Fri, 1 Oct 1999 09:58:25 +0100 (BST) From: Doug Rabson To: Don Cc: alpha@freebsd.org Subject: Re: Supported ethernet cards 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 Thu, 30 Sep 1999, Don wrote: > Quick question: Do we have a supported hardware list yet? Specifically I > am interested in ethernet cards. > > Also: I am looking to make an AS200 into a firewall running ipf*. Has > anyone done this and had any success or failure attempting to do so? I think virtually all the ethernet cards supported on i386 are also supported on alpha as well. Most of this support is in both -current and -stable. -- 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 Fri Oct 1 10:43: 7 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 9C96314C30; Fri, 1 Oct 1999 10:43:05 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.8.7/8.8.7) with ESMTP id KAA17079; Fri, 1 Oct 1999 10:43:05 -0700 Date: Fri, 1 Oct 1999 10:42:56 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: sos@freebsd.org Cc: alpha@freebsd.org Subject: atapidisk on alpha 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 FYI, just thought I'd see what it would do: ata0-master: ad_timeout: lost disk contact - resetting ata0: resetting devices .. fatal kernel trap: trap entry = 0x2 (memory management fault) a0 = 0x10 a1 = 0x1 a2 = 0x0 pc = 0xfffffc00004cef18 ra = 0xfffffc00004cd108 curproc = 0 ddbprinttrap from 0xfffffc00004cef18 ddbprinttrap(0x10, 0x1, 0x0, 0x2) panic: trap panic Stopped at Debugger+0x2c: ldq ra,0(sp) <0xfffffe000be41490> db> t Debugger() at Debugger+0x2c panic() at panic+0xf4 trap() at trap+0x5c8 XentMM() at XentMM+0x20 ata_reinit() at ata_reinit+0xa8 (null)() at 0x1 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Oct 1 11:12:50 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 2561115AAF; Fri, 1 Oct 1999 11:12:29 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id UAA64033; Fri, 1 Oct 1999 20:11:54 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <199910011811.UAA64033@freebsd.dk> Subject: Re: atapidisk on alpha In-Reply-To: from Matthew Jacob at "Oct 1, 1999 10:42:56 am" To: mjacob@feral.com Date: Fri, 1 Oct 1999 20:11:54 +0200 (CEST) Cc: sos@freebsd.org, alpha@freebsd.org X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org It seems Matthew Jacob wrote: Well, what can I say... Oops... Actually I have no idea how/if this should work on the alpha, but I'm all ears to suggestions. I have no access to an Alpha around here, so I'm not in a position to do much about it... > FYI, just thought I'd see what it would do: > > ata0-master: ad_timeout: lost disk contact - resetting > ata0: resetting devices .. > fatal kernel trap: > > trap entry = 0x2 (memory management fault) > a0 = 0x10 > a1 = 0x1 > a2 = 0x0 > pc = 0xfffffc00004cef18 > ra = 0xfffffc00004cd108 > curproc = 0 > > ddbprinttrap from 0xfffffc00004cef18 > ddbprinttrap(0x10, 0x1, 0x0, 0x2) > panic: trap > panic > Stopped at Debugger+0x2c: ldq ra,0(sp) <0xfffffe000be41490> > > db> t > Debugger() at Debugger+0x2c > panic() at panic+0xf4 > trap() at trap+0x5c8 > XentMM() at XentMM+0x20 > ata_reinit() at ata_reinit+0xa8 > (null)() at 0x1 > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Oct 1 11:25:46 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id CF5D8152CD; Fri, 1 Oct 1999 11:25:25 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.8.7/8.8.7) with ESMTP id LAA17241; Fri, 1 Oct 1999 11:25:08 -0700 Date: Fri, 1 Oct 1999 11:24:59 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Soren Schmidt Cc: sos@freebsd.org, alpha@freebsd.org, "Jordan K. Hubbard" , Mike Smith Subject: Re: atapidisk on alpha In-Reply-To: <199910011811.UAA64033@freebsd.dk> 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 > > Well, what can I say... Oops... > Actually I have no idea how/if this should work on the alpha, but > I'm all ears to suggestions. > I have no access to an Alpha around here, so I'm not in a position > to do much about it... Well, the onboard Alphas are all CMD646 I believe...... Let me ponder this a bit... This machine of mine is under heavy usage, but I could probably devote a day to letting you slogin to feral and debug it via serial console if that would help... > > > FYI, just thought I'd see what it would do: > > > > ata0-master: ad_timeout: lost disk contact - resetting > > ata0: resetting devices .. > > fatal kernel trap: > > > > trap entry = 0x2 (memory management fault) > > a0 = 0x10 > > a1 = 0x1 > > a2 = 0x0 > > pc = 0xfffffc00004cef18 > > ra = 0xfffffc00004cd108 > > curproc = 0 > > > > ddbprinttrap from 0xfffffc00004cef18 > > ddbprinttrap(0x10, 0x1, 0x0, 0x2) > > panic: trap > > panic > > Stopped at Debugger+0x2c: ldq ra,0(sp) <0xfffffe000be41490> > > > > db> t > > Debugger() at Debugger+0x2c > > panic() at panic+0xf4 > > trap() at trap+0x5c8 > > XentMM() at XentMM+0x20 > > ata_reinit() at ata_reinit+0xa8 > > (null)() at 0x1 > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Oct 1 11:46:45 1999 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 91D0114EF9; Fri, 1 Oct 1999 11:46:38 -0700 (PDT) (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.1/8.9.1) with ESMTP id OAA13585; Fri, 1 Oct 1999 14:46:34 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id OAA00779; Fri, 1 Oct 1999 14:46:03 -0400 (EDT) (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, 1 Oct 1999 14:46:03 -0400 (EDT) To: mjacob@feral.com Cc: Soren Schmidt , sos@FreeBSD.ORG, alpha@FreeBSD.ORG, "Jordan K. Hubbard" , Mike Smith Subject: Re: atapidisk on alpha In-Reply-To: References: <199910011811.UAA64033@freebsd.dk> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14325.148.616350.910831@grasshopper.cs.duke.edu> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Matthew Jacob writes: > > > > Well, what can I say... Oops... > > Actually I have no idea how/if this should work on the alpha, but > > I'm all ears to suggestions. > > I have no access to an Alpha around here, so I'm not in a position > > to do much about it... > > Well, the onboard Alphas are all CMD646 I believe...... Let me ponder this > a bit... This machine of mine is under heavy usage, but I could probably > devote a day to letting you slogin to feral and debug it via serial > console if that would help... Was your crash during actual usage, or during boot? This worked at one time on the on-board Cypress 82C693 IDE controller on newer miatas. My miatas boot fine w/the IDE cdrom, but I haven't used the CDROM in ages. I'm kinda swamped here, but I'll try hook a disk up & see what happens at some point soon. 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 Fri Oct 1 11:51:54 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 4FA7415190; Fri, 1 Oct 1999 11:51:51 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.8.7/8.8.7) with ESMTP id LAA17301; Fri, 1 Oct 1999 11:51:14 -0700 Date: Fri, 1 Oct 1999 11:51:04 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Andrew Gallatin Cc: Soren Schmidt , sos@FreeBSD.ORG, alpha@FreeBSD.ORG, "Jordan K. Hubbard" , Mike Smith Subject: Re: atapidisk on alpha In-Reply-To: <14325.148.616350.910831@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 On Fri, 1 Oct 1999, Andrew Gallatin wrote: > > Matthew Jacob writes: > > > > > > Well, what can I say... Oops... > > > Actually I have no idea how/if this should work on the alpha, but > > > I'm all ears to suggestions. > > > I have no access to an Alpha around here, so I'm not in a position > > > to do much about it... > > > > Well, the onboard Alphas are all CMD646 I believe...... Let me ponder this > > a bit... This machine of mine is under heavy usage, but I could probably > > devote a day to letting you slogin to feral and debug it via serial > > console if that would help... > > Was your crash during actual usage, or during boot? After boot. It came up, said "creating wd0, ad0..."... I loggged in and did a "disklabel ad0" after making the device nodes.... > > This worked at one time on the on-board Cypress 82C693 IDE controller > on newer miatas. > > My miatas boot fine w/the IDE cdrom, but I haven't used the CDROM in > ages. I'm kinda swamped here, but I'll try hook a disk up & see what > happens at some point soon. > Well, things didn't even compile yesterday until I updated files.alpha to make a apm.h.... so the breakage is likely recent.... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Oct 1 21:19:27 1999 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 AEB4514C2A for ; Fri, 1 Oct 1999 21:19:24 -0700 (PDT) (envelope-from don@calis.blacksun.org) Received: from localhost (don@localhost) by calis.blacksun.org (8.9.3/8.9.2) with ESMTP id AAA02667 for ; Sat, 2 Oct 1999 00:20:14 -0400 (EDT) (envelope-from don@calis.blacksun.org) Date: Sat, 2 Oct 1999 00:20:14 -0400 (EDT) From: Don To: alpha@freebsd.org Subject: Problem with NCR driver 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 Ok here is the situation. I have an alphastation 200 4/233 with 96 megs of ram. I just installed this system today. I cvsup'd new source and went to compile a custom kernel using a configuration I use on two other identical systems. The problem is that when I attempt to boot this system the ncr driver "discarded data" and after 6 or so discards it announces that it cannot read block 16. I immediately booted with generic and it worked fine. Is there a known issue with this driver? I have had similar problems with the ncr's in my other systems. Those systems are running current from about 3 weeks ago. If I change the SCSI Delay in the kernel config and then reboot without powering off, the system will hang at the ncr driver. Basically I have had this problem on 3 different ncr's with 4 different hard disks. If anyone has any information about this please let me know. -don To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Oct 1 21:30:59 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id 6A19814CD1 for ; Fri, 1 Oct 1999 21:30:55 -0700 (PDT) (envelope-from chuckr@picnic.mat.net) Received: from localhost (localhost [127.0.0.1]) by picnic.mat.net (8.9.3/8.9.3) with ESMTP id AAA01920; Sat, 2 Oct 1999 00:31:20 -0400 (EDT) (envelope-from chuckr@picnic.mat.net) Date: Sat, 2 Oct 1999 00:31:19 -0400 (EDT) From: Chuck Robey To: Don Cc: alpha@FreeBSD.ORG Subject: Re: Problem with NCR driver 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 Sat, 2 Oct 1999, Don wrote: > Ok here is the situation. I have an alphastation 200 4/233 with 96 megs of > ram. I just installed this system today. I cvsup'd new source and went to > compile a custom kernel using a configuration I use on two other identical > systems. The problem is that when I attempt to boot this system the ncr > driver "discarded data" and after 6 or so discards it announces that it > cannot read block 16. I immediately booted with generic and it worked > fine. Is there a known issue with this driver? > > I have had similar problems with the ncr's in my other systems. Those > systems are running current from about 3 weeks ago. If I change the SCSI > Delay in the kernel config and then reboot without powering off, the > system will hang at the ncr driver. > > Basically I have had this problem on 3 different ncr's with 4 different > hard disks. If anyone has any information about this please let me know. Seeing as the NCR controller is used pretty widely on the Alpha, and many of us haven't any problems with it at all, you maybe should give much more information, like the model of the controller, the kind of cable (describe thoroughly, what's terminating, how many connectors, drives, etc) and how the relevant portions of your dmesg and config file. I'll bet it's something to do with cabling or terminations. Too many of us think they're pretty solid controllers. > > -don > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-alpha" in the body of the message > ---------------------------------------------------------------------------- Chuck Robey | Interests include C programming, Electronics, 213 Lakeside Dr. Apt. T-1 | communications, and signal processing. Greenbelt, MD 20770 | I run picnic.mat.net: FreeBSD-current(i386) and (301) 220-2114 | jaunt.mat.net : FreeBSD-current(Alpha) ---------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Oct 1 21:45:48 1999 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 C436114CD1 for ; Fri, 1 Oct 1999 21:45:37 -0700 (PDT) (envelope-from don@calis.blacksun.org) Received: from localhost (don@localhost) by calis.blacksun.org (8.9.3/8.9.2) with ESMTP id AAA02732; Sat, 2 Oct 1999 00:46:21 -0400 (EDT) (envelope-from don@calis.blacksun.org) Date: Sat, 2 Oct 1999 00:46:21 -0400 (EDT) From: Don To: Chuck Robey Cc: alpha@FreeBSD.ORG Subject: Re: Problem with NCR driver 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 > Seeing as the NCR controller is used pretty widely on the Alpha, and many > of us haven't any problems with it at all, you maybe should give much more > information, like the model of the controller, the kind of cable (describe > thoroughly, what's terminating, how many connectors, drives, etc) and how > the relevant portions of your dmesg and config file. > > I'll bet it's something to do with cabling or terminations. Too many of > us think they're pretty solid controllers. Well given that these controllers perform flawlessly with the snapshot kernels and the fact that they performed flawlessly when these systems were running NetBSD I can honestly say that I dont think the cabling or the termination is the issue. For clarity the cabling is the default cabling that comes with the AS200's and the termination is handled by the drive which is the only one on the chain. The relevant dmesg output is: ncr0: irq 11 at device 6.0 on pci0 ncr0: interrupting at ISA irq 11 da0 at ncr0 bus 0 target 6 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 10.000MB/s transfers (10.000MHz, offset 8), Tagged Queueing Enabled da0: 3090MB (6328861 512 byte sectors: 255H 63S/T 393C) The error was: (da0:ncr0:0:6:0): extraneous data discarded. (da0:ncr0:0:6:0): COMMAND FAILED (9 0) @0xfffffe000057a000. (da0:ncr0:0:6:0): extraneous data discarded. (da0:ncr0:0:6:0): COMMAND FAILED (9 0) @0xfffffe000057a000. (da0:ncr0:0:6:0): extraneous data discarded. (da0:ncr0:0:6:0): COMMAND FAILED (9 0) @0xfffffe000057a000. (da0:ncr0:0:6:0): extraneous data discarded. (da0:ncr0:0:6:0): COMMAND FAILED (9 0) @0xfffffe000057a000. (da0:ncr0:0:6:0): extraneous data discarded. (da0:ncr0:0:6:0): COMMAND FAILED (9 0) @0xfffffe000057a000. ... could not fsck /dev/da0a ... syncing disks... done Actually I am not sure whether this is da issue or an ncr issue although I said ncr due to the problems I had a few weeks ago with having to cold boot the system after making SCSI changes. -Don To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sat Oct 2 10:58:15 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 2BFFA14FD7 for ; Sat, 2 Oct 1999 10:58:01 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.8.7/8.8.7) with ESMTP id KAA20108; Sat, 2 Oct 1999 10:57:05 -0700 Date: Sat, 2 Oct 1999 10:56:54 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Don Cc: Chuck Robey , alpha@FreeBSD.ORG Subject: Re: Problem with NCR driver 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 I would make a CAMDEBUG kernel to print out the commands being sent and/or otherwise hack it so the CDB *and* the dma length is printed out. I'm wondering whether this is related to the problems that seem to have surfaced in the last day or so in -current. Unfortunately, this is not one of the cards the Gerard's driver supports so you can't do a crosscheck to eliminate the sim driver. On Sat, 2 Oct 1999, Don wrote: > > Seeing as the NCR controller is used pretty widely on the Alpha, and many > > of us haven't any problems with it at all, you maybe should give much more > > information, like the model of the controller, the kind of cable (describe > > thoroughly, what's terminating, how many connectors, drives, etc) and how > > the relevant portions of your dmesg and config file. > > > > I'll bet it's something to do with cabling or terminations. Too many of > > us think they're pretty solid controllers. > Well given that these controllers perform flawlessly with the snapshot > kernels and the fact that they performed flawlessly when these systems > were running NetBSD I can honestly say that I dont think the cabling or > the termination is the issue. For clarity the cabling is the default > cabling that comes with the AS200's and the termination is handled by the > drive which is the only one on the chain. > > The relevant dmesg output is: > ncr0: irq 11 at device 6.0 on pci0 > ncr0: interrupting at ISA irq 11 > da0 at ncr0 bus 0 target 6 lun 0 > da0: Fixed Direct Access SCSI-2 device > da0: 10.000MB/s transfers (10.000MHz, offset 8), Tagged Queueing Enabled > da0: 3090MB (6328861 512 byte sectors: 255H 63S/T 393C) > > The error was: > (da0:ncr0:0:6:0): extraneous data discarded. > (da0:ncr0:0:6:0): COMMAND FAILED (9 0) @0xfffffe000057a000. > (da0:ncr0:0:6:0): extraneous data discarded. > (da0:ncr0:0:6:0): COMMAND FAILED (9 0) @0xfffffe000057a000. > (da0:ncr0:0:6:0): extraneous data discarded. > (da0:ncr0:0:6:0): COMMAND FAILED (9 0) @0xfffffe000057a000. > (da0:ncr0:0:6:0): extraneous data discarded. > (da0:ncr0:0:6:0): COMMAND FAILED (9 0) @0xfffffe000057a000. > (da0:ncr0:0:6:0): extraneous data discarded. > (da0:ncr0:0:6:0): COMMAND FAILED (9 0) @0xfffffe000057a000. > > ... > could not fsck /dev/da0a > ... > > syncing disks... done > > Actually I am not sure whether this is da issue or an ncr issue although I > said ncr due to the problems I had a few weeks ago with having to cold > boot the system after making SCSI changes. > > -Don > > > > 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 Sat Oct 2 21:31: 8 1999 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 EEA1D14E9C for ; Sat, 2 Oct 1999 21:31:04 -0700 (PDT) (envelope-from don@calis.blacksun.org) Received: from localhost (don@localhost) by calis.blacksun.org (8.9.3/8.9.2) with ESMTP id AAA07388 for ; Sun, 3 Oct 1999 00:31:57 -0400 (EDT) (envelope-from don@calis.blacksun.org) Date: Sun, 3 Oct 1999 00:31:57 -0400 (EDT) From: Don To: alpha@freebsd.org Subject: NCR Problem 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 Well here is some more information. This appears to be the relevant dmesg output although I do not know if this will be of any help: xpt_setup_ccb (da0:ncr0:0:6:0): xpt_action (da0:ncr0:0:6:0): READ(06). CDB: 8 0 0 0 1 0 (da0:ncr0:0:6:0): xpt_done (da0:ncr0:0:6:0): camisr(da0:ncr0:0:6:0): xpt_schedule (da0:ncr0:0:6:0): xpt_setup_ccb (da0:ncr0:0:6:0): xpt_action (da0:ncr0:0:6:0): READ(06). CDB: 8 0 0 0 1 0 (da0:ncr0:0:6:0): xpt_done (da0:ncr0:0:6:0): camisr(da0:ncr0:0:6:0): xpt_schedule (da0:ncr0:0:6:0): xpt_setup_ccb (da0:ncr0:0:6:0): xpt_action (da0:ncr0:0:6:0): READ(06). CDB: 8 1 8 80 20 0 (da0:ncr0:0:6:0): xpt_done (da0:ncr0:0:6:0): camisr(da0:ncr0:0:6:0): xpt_schedule (da0:ncr0:0:6:0): xpt_setup_ccb (da0:ncr0:0:6:0): xpt_action (da0:ncr0:0:6:0): READ(06). CDB: 8 0 0 10 0 0 (da0:ncr0:0:6:0): extraneous data discarded. (da0:ncr0:0:6:0): COMMAND FAILED (9 0) @0xfffffe000057a000. (da0:ncr0:0:6:0): xpt_done (da0:ncr0:0:6:0): camisr(da0:ncr0:0:6:0): xpt_action (da0:ncr0:0:6:0): READ(06). CDB: 8 0 0 10 0 0 (da0:ncr0:0:6:0): xpt_setup_ccb (da0:ncr0:0:6:0): xpt_action (da0:ncr0:0:6:0): extraneous data discarded. (da0:ncr0:0:6:0): COMMAND FAILED (9 0) @0xfffffe000057a000. This eventually results in an inability to read block 16 and a boot failure. I am not a programmer but I will do what I can to help anyone who wants or needs more information to figure out what is going on here. -Don To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message