From owner-freebsd-alpha Sun Mar 4 3: 7:58 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from post.mail.nl.demon.net (post-10.mail.nl.demon.net [194.159.73.20]) by hub.freebsd.org (Postfix) with ESMTP id 67F7F37B71A for ; Sun, 4 Mar 2001 03:07:49 -0800 (PST) (envelope-from wkb@freebie.demon.nl) Received: from [212.238.54.101] (helo=freebie.demon.nl) by post.mail.nl.demon.net with smtp (Exim 3.14 #2) id 14ZWMd-0003Vf-00; Sun, 04 Mar 2001 11:07:47 +0000 Received: (from wkb@localhost) by freebie.demon.nl (8.11.2/8.11.2) id f24B9OY17099; Sun, 4 Mar 2001 12:09:24 +0100 (CET) (envelope-from wkb) Date: Sun, 4 Mar 2001 12:09:24 +0100 From: Wilko Bulte To: freebsd-alpha@freebsd.org Cc: peter.petrakis@api-networks.com Subject: Away for a while / 4.3RC testing Message-ID: <20010304120924.A17078@freebie.demon.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i X-OS: FreeBSD 4.2-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org All, I will be on a business trip to Spain starting this afternoon. Email access will be unpredictable at best. For obvious reasons I will not be able to test 4.3RC bits this week. Please check http://www.freebsd.org/~wilko for an overview of the alpha hardware models to be tested. I will update this page on my return, Saturday March 10 with any email input received. regds Wilko -- | / o / / _ Arnhem, The Netherlands email: wilko@freebsd.org |/|/ / / /( (_) Bulte http://www.freebsd.org http://www.nlfug.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sun Mar 4 11: 7: 9 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id C15A237B718; Sun, 4 Mar 2001 11:07:05 -0800 (PST) (envelope-from mjacob@feral.com) Received: from beppo (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id LAA31446; Sun, 4 Mar 2001 11:07:06 -0800 Date: Sun, 4 Mar 2001 11:07:04 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: sos@freebsd.org Cc: alpha@freebsd.org Subject: 4.3 might have broken ATA for 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 Did you make changes recently that might have done this on alpha for -stable? ata0-master: ata_command: timeout waiting for intr ata0-master: identify failed To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sun Mar 4 11:52: 0 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id A501C37B718; Sun, 4 Mar 2001 11:51:57 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id UAA82055; Sun, 4 Mar 2001 20:51:53 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200103041951.UAA82055@freebsd.dk> Subject: Re: 4.3 might have broken ATA for alpha... In-Reply-To: from Matthew Jacob at "Mar 4, 2001 11:07:04 am" To: mjacob@feral.com Date: Sun, 4 Mar 2001 20:51:52 +0100 (CET) Cc: sos@freebsd.org, alpha@freebsd.org X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org It seems Matthew Jacob wrote: > > Did you make changes recently that might have done this on alpha for -stable? Not that I now of.... > ata0-master: ata_command: timeout waiting for intr > ata0-master: identify failed -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sun Mar 4 12:14:13 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 17BCF37B718 for ; Sun, 4 Mar 2001 12:14:10 -0800 (PST) (envelope-from mjacob@feral.com) Received: from beppo (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id MAA31655; Sun, 4 Mar 2001 12:13:47 -0800 Date: Sun, 4 Mar 2001 12:13:45 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Soren Schmidt Cc: alpha@FreeBSD.ORG Subject: Re: 4.3 might have broken ATA for alpha... In-Reply-To: <200103041951.UAA82055@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 ---------------------------- revision 1.50.2.16 date: 2001/02/25 21:35:19; author: sos; state: Exp; lines: +15 -12 MFC: Get the ata drive in sync with -current to the following versions: ata-all.c 1.102 (minus 1.100) ata-all.h 1.37 ata-disk.c 1.92 ata-disk.h 1.31 ata-dma.c 1.57 ata-raid.c 1.10 ata-raid.h 1.4 atapi-all.c 1.63 (minus 1.62) atapi-all.h 1.32 atapi-cd.c 1.76 (minus progress stuff) atapi-cd.h 1.22 (minus progress stuff) atapi-fd.c 1.57 atapi-fd.h 1.13 atapi-tape.c 1.49 atapi-tape.h 1.14 ----------- So, you MFC'd the entire lot- did you have anybody run this on alpha? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sun Mar 4 12:17:39 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 57FC737B719 for ; Sun, 4 Mar 2001 12:17:37 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id VAA88475; Sun, 4 Mar 2001 21:17:33 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200103042017.VAA88475@freebsd.dk> Subject: Re: 4.3 might have broken ATA for alpha... In-Reply-To: from Matthew Jacob at "Mar 4, 2001 12:13:45 pm" To: mjacob@feral.com Date: Sun, 4 Mar 2001 21:17:33 +0100 (CET) Cc: alpha@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org It seems Matthew Jacob wrote: > > So, you MFC'd the entire lot- did you have anybody run this on alpha? It works on -current so it should on -stable too... Anyhow there is no biggies among those, but since I dont have any alpha HW to test on I cant tell for sure, but I'll gladly help to get this solved of cause, but I dont have anything to go by.... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sun Mar 4 12:20:12 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 86F0237B719 for ; Sun, 4 Mar 2001 12:20:10 -0800 (PST) (envelope-from mjacob@feral.com) Received: from beppo (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id MAA31691; Sun, 4 Mar 2001 12:20:00 -0800 Date: Sun, 4 Mar 2001 12:19:58 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Soren Schmidt Cc: alpha@FreeBSD.ORG Subject: Never Mind...Re: 4.3 might have broken ATA for 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 >It seems Matthew Jacob wrote: >> >> So, you MFC'd the entire lot- did you have anybody run this on alpha? > >It works on -current so it should on -stable too... > >Anyhow there is no biggies among those, but since I dont have any >alpha HW to test on I cant tell for sure, but I'll gladly help >to get this solved of cause, but I dont have anything to go by.... Thanks for the offer! well, it sort of seems to work now..... whew... wouldn't want to have had to sort this out right now.... had a bad fright there...... -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sun Mar 4 12:22:49 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id F08F037B718 for ; Sun, 4 Mar 2001 12:22:46 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id VAA89746; Sun, 4 Mar 2001 21:22:43 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200103042022.VAA89746@freebsd.dk> Subject: Re: Never Mind...Re: 4.3 might have broken ATA for alpha... In-Reply-To: from Matthew Jacob at "Mar 4, 2001 12:19:58 pm" To: mjacob@feral.com Date: Sun, 4 Mar 2001 21:22:43 +0100 (CET) Cc: alpha@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org It seems Matthew Jacob wrote: > > >It seems Matthew Jacob wrote: > >> > >> So, you MFC'd the entire lot- did you have anybody run this on alpha? > > > >It works on -current so it should on -stable too... > > > >Anyhow there is no biggies among those, but since I dont have any > >alpha HW to test on I cant tell for sure, but I'll gladly help > >to get this solved of cause, but I dont have anything to go by.... > > Thanks for the offer! > > well, it sort of seems to work now..... whew... wouldn't want to have > had to sort this out right now.... had a bad fright there...... OK :) just shout if there are any problems, I want this to work too... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sun Mar 4 12:39:21 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 79FCD37B719 for ; Sun, 4 Mar 2001 12:39:18 -0800 (PST) (envelope-from mjacob@feral.com) Received: from beppo (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id MAA31780; Sun, 4 Mar 2001 12:39:16 -0800 Date: Sun, 4 Mar 2001 12:39:14 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Soren Schmidt Cc: alpha@FreeBSD.ORG Subject: Ah! Source of ATA-alpha wierdness solved... 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 This happens after a panic which had reset the ad device to be PIO4... the reboot that followed probed: ... ata0: iobase=0x01f0 altiobase=0x03f6 bmaddr=0x10280 ata0: mask=03 status0=50 status1=00 ata0: mask=03 ostat0=50 ostat2=00 ata0-master: ATAPI probe a=00 b=00 ata0-slave: ATAPI probe a=00 b=00 ata0: mask=03 status0=50 status1=00 ata0-master: ATA probe a=01 b=a5 ata0: devices=01 ata0: at 0x1f0 irq 14 on atapci0 ata1: iobase=0x0170 altiobase=0x0376 bmaddr=0x10288 ata1: mask=00 status0=ff status1=ff ata1: probe allocation failed Trying Read_Port at 203 .... but got ata0-master: ata_command: timeout waiting for intr ata0-master: identify failed instead of the expected: ata0-master: success setting WDMA2 on CMD chip Creating DISK ad0 Creating DISK wd0 ad0: ATA-4 disk at ata0-master ad0: 3098MB (6346368 sectors), 6296 cyls, 16 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 1 depth queue, WDMA2 ad0: piomode=4 dmamode=2 udmamode=2 cblid=0 ad0: 3098MB [6296/16/63] at ata0-master WDMA2 which, ho ho ho, caused the root filesystem to be mounted from da0 instead of ad0 so things look 'almost' okay (but I'm now running my -current instead of -stable system...) *sputter*.... Then doing an 'init' at the PROM hung, so I needed to power cycle. *more sputter*... Would you consider this an 'alpha' problem? Or would it be reasonable after doing the reset for dumping that a shutdown hook for resetting completely would be reasonable? -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sun Mar 4 12:44:21 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id AC38637B718 for ; Sun, 4 Mar 2001 12:44:18 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id VAA94995; Sun, 4 Mar 2001 21:44:15 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200103042044.VAA94995@freebsd.dk> Subject: Re: Ah! Source of ATA-alpha wierdness solved... In-Reply-To: from Matthew Jacob at "Mar 4, 2001 12:39:14 pm" To: mjacob@feral.com Date: Sun, 4 Mar 2001 21:44:15 +0100 (CET) Cc: alpha@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org It seems Matthew Jacob wrote: > > Then doing an 'init' at the PROM hung, so I needed to power cycle. > *more sputter*... > > Would you consider this an 'alpha' problem? Or would it be reasonable > after doing the reset for dumping that a shutdown hook for resetting > completely would be reasonable? The ata driver does a reset of all ata/atapi device on boot, so there is not much more I can do here, the alpha BIOS should have reset/cleared the chip too shouldn't it ? -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sun Mar 4 12:53:12 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 2C97E37B718 for ; Sun, 4 Mar 2001 12:53:09 -0800 (PST) (envelope-from mjacob@feral.com) Received: from beppo (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id MAA31822; Sun, 4 Mar 2001 12:53:03 -0800 Date: Sun, 4 Mar 2001 12:53:01 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Soren Schmidt Cc: alpha@FreeBSD.ORG Subject: Re: Ah! Source of ATA-alpha wierdness solved... In-Reply-To: <200103042044.VAA94995@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 On Sun, 4 Mar 2001, Soren Schmidt wrote: > It seems Matthew Jacob wrote: > > > > Then doing an 'init' at the PROM hung, so I needed to power cycle. > > *more sputter*... > > > > Would you consider this an 'alpha' problem? Or would it be reasonable > > after doing the reset for dumping that a shutdown hook for resetting > > completely would be reasonable? > > The ata driver does a reset of all ata/atapi device on boot, so there > is not much more I can do here, the alpha BIOS should have reset/cleared > the chip too shouldn't it ? One would think- boot 'reboot' is considered different than 'boot'. There's some kind of low-level issue here. -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sun Mar 4 12:57:38 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 2655237B726 for ; Sun, 4 Mar 2001 12:57:35 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id VAA98240; Sun, 4 Mar 2001 21:57:30 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200103042057.VAA98240@freebsd.dk> Subject: Re: Ah! Source of ATA-alpha wierdness solved... In-Reply-To: from Matthew Jacob at "Mar 4, 2001 12:53:01 pm" To: mjacob@feral.com Date: Sun, 4 Mar 2001 21:57:30 +0100 (CET) Cc: alpha@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org It seems Matthew Jacob wrote: > > > Then doing an 'init' at the PROM hung, so I needed to power cycle. > > > *more sputter*... > > > > > > Would you consider this an 'alpha' problem? Or would it be reasonable > > > after doing the reset for dumping that a shutdown hook for resetting > > > completely would be reasonable? > > > > The ata driver does a reset of all ata/atapi device on boot, so there > > is not much more I can do here, the alpha BIOS should have reset/cleared > > the chip too shouldn't it ? > > One would think- boot 'reboot' is considered different than 'boot'. There's > some kind of low-level issue here. I'm not sure I parse that sentence correctly, but there is not much I can do from the driver if the device hasn't been setup correctly by the BIOS, be it soft of hard reset.. -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sun Mar 4 13: 1:43 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 6698537B718 for ; Sun, 4 Mar 2001 13:01:42 -0800 (PST) (envelope-from mjacob@feral.com) Received: from beppo (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id NAA31878; Sun, 4 Mar 2001 13:01:41 -0800 Date: Sun, 4 Mar 2001 13:01:39 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Soren Schmidt Cc: alpha@FreeBSD.ORG Subject: Re: Ah! Source of ATA-alpha wierdness solved... In-Reply-To: <200103042057.VAA98240@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 > I'm not sure I parse that sentence correctly, but there is not much > I can do from the driver if the device hasn't been setup correctly > by the BIOS, be it soft of hard reset.. Well, no- for dumping you do this reset away from normal... can you do another reset back to normal when dumping is done? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sun Mar 4 13:30: 8 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id B7F9837B718; Sun, 4 Mar 2001 13:30:03 -0800 (PST) (envelope-from mjacob@feral.com) Received: from beppo (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id NAA31982; Sun, 4 Mar 2001 13:30:05 -0800 Date: Sun, 4 Mar 2001 13:30:03 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: "David O'Brien" Cc: alpha@freebsd.org Subject: current problems in buildworld -stable 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 I last buildworld/installworld'ed one alpha -stable system on Feb 11. With a fresh /usr/src and clean /usr/obj, I now repeatedly get (below). I didn't see anything in UPDATING. Is there something I'm missing? I'm asking you because you know a whole lot things wrt CC and the tool chain... is this a bootstrap issue? .bin/gperf/../../../contrib/gperf/lib/getopt1.c cc -O -pipe -mcpu=ev4 -I/usr/obj/usr/src/alpha/usr/include -o gperf bool-arra y.o gen-perf.o hash-table.o iterator.o key-list.o list-node.o main.o new.o optio ns.o read-line.o trace.o vectors.o version.o hash.o getopt.o getopt1.o gen-perf.o: In function `Gen_Perf::Gen_Perf(void)': gen-perf.cc(.text+0x50): undefined reference to `__get_eh_context' gen-perf.cc(.text+0x54): undefined reference to `__get_eh_context' gen-perf.cc(.text+0x464): undefined reference to `__sjthrow' gen-perf.cc(.text+0x468): undefined reference to `__sjthrow' gen-perf.cc(.text+0x4f0): undefined reference to `__sjthrow' gen-perf.cc(.text+0x4f4): undefined reference to `__sjthrow' gen-perf.cc(.text+0x500): undefined reference to `__terminate' gen-perf.cc(.text+0x504): undefined reference to `__terminate' gen-perf.cc(.text+0x510): undefined reference to `__terminate' gen-perf.cc(.text+0x514): undefined reference to `__terminate' key-list.o: In function `parse_line(char const *, char const *)': key-list.cc(.text+0x774): undefined reference to `__get_eh_context' key-list.cc(.text+0x778): undefined reference to `__get_eh_context' key-list.cc(.text+0xeb4): undefined reference to `__sjthrow' key-list.cc(.text+0xeb8): undefined reference to `__sjthrow' key-list.cc(.text+0xf44): undefined reference to `__sjthrow' key-list.cc(.text+0xf48): undefined reference to `__sjthrow' key-list.cc(.text+0xf60): undefined reference to `__terminate' key-list.cc(.text+0xf64): undefined reference to `__terminate' key-list.cc(.text+0xf70): undefined reference to `__terminate' key-list.cc(.text+0xf74): undefined reference to `__terminate' key-list.o: In function `Key_List::read_keys(void)': key-list.cc(.text+0x1018): undefined reference to `__get_eh_context' key-list.cc(.text+0x101c): undefined reference to `__get_eh_context' key-list.o: In function `Key_List::output_lookup_function_body(Output_Compare co nst &)': key-list.cc(.text+0x4434): undefined reference to `__get_eh_context' key-list.cc(.text+0x4438): undefined reference to `__get_eh_context' key-list.o: In function `Key_List::output_lookup_function(void)': key-list.cc(.text+0x5660): undefined reference to `__get_eh_context' key-list.o(.text+0x5664):key-list.cc: more undefined references to `__get_eh_con text' follow key-list.o: In function `Output_Constants type_info function': key-list.cc(.text+0x6200): undefined reference to `__rtti_user' key-list.cc(.text+0x6204): undefined reference to `__rtti_user' key-list.o: In function `Output_Defines type_info function': key-list.cc(.text+0x628c): undefined reference to `__rtti_user' key-list.cc(.text+0x6290): undefined reference to `__rtti_user' key-list.cc(.text+0x62a8): undefined reference to `__rtti_si' key-list.cc(.text+0x62ac): undefined reference to `__rtti_si' key-list.o: In function `Output_Defines::Output_Defines(void)': key-list.cc(.text+0x6330): undefined reference to `__get_eh_context' key-list.cc(.text+0x6334): undefined reference to `__get_eh_context' key-list.o: In function `Output_Enum type_info function': key-list.cc(.text+0x644c): undefined reference to `__rtti_user' key-list.cc(.text+0x6450): undefined reference to `__rtti_user' key-list.cc(.text+0x6468): undefined reference to `__rtti_si' key-list.cc(.text+0x646c): undefined reference to `__rtti_si' key-list.o: In function `Output_Enum::Output_Enum(char const *)': key-list.cc(.text+0x64f4): undefined reference to `__get_eh_context' key-list.cc(.text+0x64f8): undefined reference to `__get_eh_context' key-list.o: In function `Output_Expr type_info function': key-list.cc(.text+0x6620): undefined reference to `__rtti_user' 85% To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sun Mar 4 13:40:16 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 870D237B718 for ; Sun, 4 Mar 2001 13:40:14 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id WAA08963; Sun, 4 Mar 2001 22:40:10 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200103042140.WAA08963@freebsd.dk> Subject: Re: Ah! Source of ATA-alpha wierdness solved... In-Reply-To: from Matthew Jacob at "Mar 4, 2001 01:01:39 pm" To: mjacob@feral.com Date: Sun, 4 Mar 2001 22:40:10 +0100 (CET) Cc: alpha@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org It seems Matthew Jacob wrote: > > I'm not sure I parse that sentence correctly, but there is not much > > I can do from the driver if the device hasn't been setup correctly > > by the BIOS, be it soft of hard reset.. > > Well, no- for dumping you do this reset away from normal... can you do another > reset back to normal when dumping is done? Uhm, I only stop using DMA and go to PIO, I dont do anything to the chipset really... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sun Mar 4 13:46:12 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id DE8FC37B719 for ; Sun, 4 Mar 2001 13:46:10 -0800 (PST) (envelope-from mjacob@feral.com) Received: from beppo (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id NAA32063; Sun, 4 Mar 2001 13:46:00 -0800 Date: Sun, 4 Mar 2001 13:45:58 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Soren Schmidt Cc: alpha@FreeBSD.ORG Subject: Re: Ah! Source of ATA-alpha wierdness solved... In-Reply-To: <200103042140.WAA08963@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 > It seems Matthew Jacob wrote: > > > I'm not sure I parse that sentence correctly, but there is not much > > > I can do from the driver if the device hasn't been setup correctly > > > by the BIOS, be it soft of hard reset.. > > > > Well, no- for dumping you do this reset away from normal... can you do another > > reset back to normal when dumping is done? > > Uhm, I only stop using DMA and go to PIO, I dont do anything to the > chipset really... Sigh..... -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sun Mar 4 16:50: 8 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 8C57837B719 for ; Sun, 4 Mar 2001 16:50:03 -0800 (PST) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f250o3Q82550; Sun, 4 Mar 2001 16:50:03 -0800 (PST) (envelope-from gnats) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 902AB37B71A for ; Sun, 4 Mar 2001 16:41:25 -0800 (PST) (envelope-from nobody@FreeBSD.org) Received: (from nobody@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f250fP281920; Sun, 4 Mar 2001 16:41:25 -0800 (PST) (envelope-from nobody) Message-Id: <200103050041.f250fP281920@freefall.freebsd.org> Date: Sun, 4 Mar 2001 16:41:25 -0800 (PST) From: raymond@one.com.au To: freebsd-gnats-submit@freebsd.org X-Send-Pr-Version: www-1.0 Subject: alpha/25535: unaligned access crash on stq Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Number: 25535 >Category: alpha >Synopsis: unaligned access crash on stq >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-alpha >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Sun Mar 04 16:50:03 PST 2001 >Closed-Date: >Last-Modified: >Originator: Ray Newman >Release: FreeBSD 4.2-RELEASE alpha >Organization: One Management Australia >Environment: FreeBSD alpha.local 4.2-RELEASE FreeBSD 4.2-RELEASE #0: Tue Nov 21 09:42:09 GMT 2000 jkh@rawhide.osd.bsdi.com:/usr/src/sys/compile/GENERIC alpha >Description: unaligned access crash on stq occurs where address MOD 8 equals 4. >How-To-Repeat: // crash.c // // Reproduce crash - do the following: // // cc -g -o crash crash.c // ./crash // lockstart = 0x12001404c // pid 1804 (crash): unaligned access: va=0x12001404c pc=0x12000096c // ra=0x120000934 op=stq // #include // always include #include // these two #include // for u_char def typedef unsigned long long u_int64; // unix unsigned quadword typedef u_int64 chr_q; // our quadword special typedef union VAR_U // get at this two ways { chr_q var_qu; // variable name (quadword) u_char var_cu[8]; // variable name (as char[]) } var_u; // variable name union typedef struct LOCKTAB // internal lock tables { struct LOCKTAB *fwd_link; // point at next one int size; // how many bytes short job; // int job (-1 = free) short lock_count; // how many times locked by job short byte_count; // size of following reference u_char vol; // vol number u_char uci; // uci number (255 = local) var_u name; // var name u_char key[256]; // and the key } locktab; // define locktab typedef struct SYSTAB // system tables { void *jobtab; // address of jobtab int maxjob; // maximum jobs permitted int sem_id; // GBD semaphore id int historic; // Enn, tag+off, $NEXT etc int max_tt; // max TRANTAB used int start_user; // he's priv too void *lockstart; // head of lock table int locksize; // how many bytes locktab *lockhead; // head of used locks locktab *lockfree; // head of lock free space void *vol[1]; // array of vol ptrs u_int last_blk_used[1]; // actually setup for real jobs } systab_struct; // end of systab int main(int argc,char **argv) // main entry point { int c = 8192; // for case struct SYSTAB *systab; // for test systab = malloc(sizeof(struct SYSTAB) + c); bzero(systab, sizeof(struct SYSTAB) + c); systab->lockstart = ((char *) systab->last_blk_used + 4); printf("lockstart = %p\n", systab->lockstart); systab->locksize = c; // the size systab->lockhead = NULL; // no locks currently systab->lockfree = (locktab *) systab->lockstart; // free space systab->lockfree->fwd_link = NULL; // only one systab->lockfree->size = c; c = 0; exit (0); } >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 Sun Mar 4 17: 0: 7 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 235EF37B718 for ; Sun, 4 Mar 2001 17:00:06 -0800 (PST) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f25106b83438; Sun, 4 Mar 2001 17:00:06 -0800 (PST) (envelope-from gnats) Date: Sun, 4 Mar 2001 17:00:06 -0800 (PST) Message-Id: <200103050100.f25106b83438@freefall.freebsd.org> To: freebsd-alpha@freebsd.org Cc: From: Matthew Jacob Subject: Re: alpha/25535: unaligned access crash on stq Reply-To: Matthew Jacob Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR alpha/25535; it has been noted by GNATS. From: Matthew Jacob To: raymond@one.com.au Cc: freebsd-gnats-submit@FreeBSD.ORG Subject: Re: alpha/25535: unaligned access crash on stq Date: Sun, 4 Mar 2001 16:54:48 -0800 (PST) How is this a bug? If you try and access unaligned values you'll get unaligned traps. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sun Mar 4 17: 3: 4 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 39EAE37B718; Sun, 4 Mar 2001 17:03:03 -0800 (PST) (envelope-from mjacob@FreeBSD.org) Received: (from mjacob@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f25133i83655; Sun, 4 Mar 2001 17:03:03 -0800 (PST) (envelope-from mjacob) Date: Sun, 4 Mar 2001 17:03:03 -0800 (PST) From: Message-Id: <200103050103.f25133i83655@freefall.freebsd.org> To: raymond@one.com.au, mjacob@FreeBSD.org, freebsd-alpha@freebsd.org Subject: Re: alpha/25535: unaligned access crash on stq Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Synopsis: unaligned access crash on stq State-Changed-From-To: open->closed State-Changed-By: mjacob State-Changed-When: Sun Mar 4 17:02:42 PST 2001 State-Changed-Why: Not a bug. See audit trail in email. http://www.freebsd.org/cgi/query-pr.cgi?pr=25535 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sun Mar 4 17:10:15 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 5EFD337B71A for ; Sun, 4 Mar 2001 17:10:02 -0800 (PST) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f251A2T86680; Sun, 4 Mar 2001 17:10:02 -0800 (PST) (envelope-from gnats) Date: Sun, 4 Mar 2001 17:10:02 -0800 (PST) Message-Id: <200103050110.f251A2T86680@freefall.freebsd.org> To: freebsd-alpha@freebsd.org Cc: From: Matthew Jacob Subject: Re: alpha/25535: unaligned access crash on stq Reply-To: Matthew Jacob Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR alpha/25535; it has been noted by GNATS. From: Matthew Jacob To: User Raymond Cc: freebsd-gnats-submit@FreeBSD.ORG Subject: Re: alpha/25535: unaligned access crash on stq Date: Sun, 4 Mar 2001 17:02:21 -0800 (PST) (let's keep the audit trail in the PR) On Mon, 5 Mar 2001, User Raymond wrote: > Subj: alpha/25535: unaligned access crash on stq > To: mjacob@feral.com > From: raymond@one.com.au > > > > How is this a bug? If you try and access unaligned values you'll get > > unaligned traps. > > Sorry - I didn't explain myself at all well did I? > > The example was the only way I could force that to happen and I don't > know whether the OS is supposed to trap that and fix it on the fly. > > The original is in a much larger piece of code that ends up with a structure > unalligned and I can't work out how to get around it. I am porting the > code from the x86 platform and not having much luck. > > Any pointers would be appreciated. > > Ray Newman > Pointers indeed! :-) farrago.feral.com > uname -a FreeBSD farrago.feral.com 4.2-STABLE FreeBSD 4.2-STABLE #6: Sun Mar 4 13:33:54 PST 2001 mjacob@farrago.feral.com:/tstsys/compile/GPLUS alpha farrago.feral.com > sysctl -a|grep alig vfs.nfs.realign_test: 20065 vfs.nfs.realign_count: 0 machdep.unaligned_print: 1 machdep.unaligned_fix: 1 machdep.unaligned_sigbus: 0 If you set machdep.unaligned_fix to 0, it will stop fixups. The default is to do the fixup. If you set machdep.unaligned_print to 0, it won't print. You might consider how to get the structure aligned as it's much more than just alpha that has this issue. -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sun Mar 4 17:34:33 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id A5D9637B719; Sun, 4 Mar 2001 17:34:32 -0800 (PST) (envelope-from mjacob@FreeBSD.org) Received: (from mjacob@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f251YW588335; Sun, 4 Mar 2001 17:34:32 -0800 (PST) (envelope-from mjacob) Date: Sun, 4 Mar 2001 17:34:32 -0800 (PST) From: Message-Id: <200103050134.f251YW588335@freefall.freebsd.org> To: raymond@one.com.au, mjacob@FreeBSD.org, freebsd-alpha@freebsd.org Subject: Re: alpha/25535: unaligned access crash on stq Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Synopsis: unaligned access crash on stq State-Changed-From-To: closed->open State-Changed-By: mjacob State-Changed-When: Sun Mar 4 17:32:37 PST 2001 State-Changed-Why: I re-opened this because, in fact, a SIGBUS is being delivered even when this should be a recoverable, if noice trap. http://www.freebsd.org/cgi/query-pr.cgi?pr=25535 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sun Mar 4 17:40: 5 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id EA07137B719 for ; Sun, 4 Mar 2001 17:40:02 -0800 (PST) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f251e2v88770; Sun, 4 Mar 2001 17:40:02 -0800 (PST) (envelope-from gnats) Date: Sun, 4 Mar 2001 17:40:02 -0800 (PST) Message-Id: <200103050140.f251e2v88770@freefall.freebsd.org> To: freebsd-alpha@freebsd.org Cc: From: Matthew Jacob Subject: Re: alpha/25535: unaligned access crash on stq Reply-To: Matthew Jacob Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR alpha/25535; it has been noted by GNATS. From: Matthew Jacob To: User Raymond Cc: freebsd-gnats-submit@FreeBSD.ORG Subject: Re: alpha/25535: unaligned access crash on stq Date: Sun, 4 Mar 2001 17:34:28 -0800 (PST) Hmm. You're right. It's not recovering. We'll have to look into why. On Mon, 5 Mar 2001, User Raymond wrote: > Subj: alpha/25535: unaligned access crash on stq > To: mjacob@feral.com > From: raymond@one.com.au > > > If you set machdep.unaligned_fix to 0, it will stop fixups. The default is to > > do the fixup. If you set machdep.unaligned_print to 0, it won't print. > > %uname -a > FreeBSD alpha.local 4.2-RELEASE FreeBSD 4.2-RELEASE #0: Tue Nov 21 09:42:09 GMT > 2000 jkh@rawhide.osd.bsdi.com:/usr/src/sys/compile/GENERIC alpha > %sysctl -a|grep alig > vfs.nfs.realign_test: 0 > vfs.nfs.realign_count: 0 > machdep.unaligned_print: 1 > machdep.unaligned_fix: 1 > machdep.unaligned_sigbus: 0 > % > > I really must be doing something wrong as machdep.unaligned_fix is set. > > Ray Newman > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sun Mar 4 19:22:33 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [209.152.133.57]) by hub.freebsd.org (Postfix) with ESMTP id E5BC337B71A; Sun, 4 Mar 2001 19:22:30 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.2/8.11.1) id f253MNk64386; Sun, 4 Mar 2001 19:22:23 -0800 (PST) (envelope-from obrien) Date: Sun, 4 Mar 2001 19:22:22 -0800 From: "David O'Brien" To: Matthew Jacob Cc: sos@freebsd.org, alpha@freebsd.org Subject: Re: 4.3 might have broken ATA for alpha... Message-ID: <20010304192222.A58979@dragon.nuxi.com> Reply-To: obrien@freebsd.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from mjacob@feral.com on Sun, Mar 04, 2001 at 11:07:04AM -0800 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sun, Mar 04, 2001 at 11:07:04AM -0800, Matthew Jacob wrote: > Did you make changes recently that might have done this on alpha for -stable? > > ata0-master: ata_command: timeout waiting for intr > ata0-master: identify failed I get that on Mar 1st x86 -CURRENT too. -- -- David (obrien@FreeBSD.org) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sun Mar 4 22:36:43 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [209.152.133.57]) by hub.freebsd.org (Postfix) with ESMTP id B50BB37B71B for ; Sun, 4 Mar 2001 22:36:41 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.3/8.11.1) id f256adP76640; Sun, 4 Mar 2001 22:36:39 -0800 (PST) (envelope-from obrien) Date: Sun, 4 Mar 2001 22:36:38 -0800 From: "David O'Brien" To: Matthew Jacob Cc: alpha@freebsd.org Subject: Re: current problems in buildworld -stable alpha? Message-ID: <20010304223638.A76607@dragon.nuxi.com> Reply-To: obrien@freebsd.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from mjacob@feral.com on Sun, Mar 04, 2001 at 01:30:03PM -0800 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sun, Mar 04, 2001 at 01:30:03PM -0800, Matthew Jacob wrote: > I last buildworld/installworld'ed one alpha -stable system on Feb 11. > With a fresh /usr/src and clean /usr/obj, I now repeatedly get (below). > I didn't see anything in UPDATING. Is there something I'm missing? Not that I know of. I just updated a 4.2-BETA alpha to latest RELENG_4 with no problems. -- -- David (obrien@FreeBSD.org) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sun Mar 4 22:37:11 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 41E3B37B71A; Sun, 4 Mar 2001 22:37:09 -0800 (PST) (envelope-from mjacob@feral.com) Received: from beppo (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id WAA00806; Sun, 4 Mar 2001 22:37:10 -0800 Date: Sun, 4 Mar 2001 22:37:08 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: "David O'Brien" Cc: alpha@freebsd.org Subject: Re: current problems in buildworld -stable alpha? In-Reply-To: <20010304223638.A76607@dragon.nuxi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Okay. I'll try again. On Sun, 4 Mar 2001, David O'Brien wrote: > On Sun, Mar 04, 2001 at 01:30:03PM -0800, Matthew Jacob wrote: > > I last buildworld/installworld'ed one alpha -stable system on Feb 11. > > With a fresh /usr/src and clean /usr/obj, I now repeatedly get (below). > > I didn't see anything in UPDATING. Is there something I'm missing? > > Not that I know of. > > I just updated a 4.2-BETA alpha to latest RELENG_4 with no problems. > > -- > -- David (obrien@FreeBSD.org) > GNU is Not Unix / Linux Is Not UniX > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Mar 5 6:31:27 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from mail.inka.de (quechua.inka.de [212.227.14.2]) by hub.freebsd.org (Postfix) with ESMTP id D994737B71A for ; Mon, 5 Mar 2001 06:31:22 -0800 (PST) (envelope-from daemon@mips.inka.de) Received: from kemoauc.mips.inka.de (uucp@) by mail.inka.de with local-bsmtp id 14Zw1B-0007HW-00; Mon, 5 Mar 2001 15:31:21 +0100 Received: (from daemon@localhost) by kemoauc.mips.inka.de (8.11.3/8.11.1) id f25E5dX01947 for freebsd-alpha@freebsd.org; Mon, 5 Mar 2001 15:05:39 +0100 (CET) (envelope-from daemon) From: naddy@mips.inka.de (Christian Weisgerber) Subject: My list of -CURRENT problems Date: Mon, 5 Mar 2001 14:05:39 +0000 (UTC) Message-ID: <9806fj$1si$1@kemoauc.mips.inka.de> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Originator: naddy@mips.inka.de (Christian Weisgerber) To: freebsd-alpha@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I rebuilt my box from yesterdays' tree. Here's my list of annoying problems: * [new] Installing ports/lang/compaq-cc panics the machine. Actually, I think executing a Linux binary through the linuxulator triggers this. * [new] If sysvipc is loaded as modules, the linuxulator module fails to load with "link_elf: symbol shmctl undefined". This doesn't happen if sysvipc is compiled statically into the kernel. I reported this a couple of days ago on freebsd-emulation, but didn't get any affirmation or useful response. I wouldn't expect this to be specific to alpha, but I don't know. * [old] bin/25361 dump(8) segfaults. After some miscommunication with Matt Jacob the PR ended up in category bin, although the bug is supposedly alpha-only. * [old] alpha/25284. With a graphics console, reboot(8) fails on PC164. * [old] The PC164 realtime clock is still in 2000. -- Christian "naddy" Weisgerber naddy@mips.inka.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Mar 5 8:19: 6 2001 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 4EA5237B718 for ; Mon, 5 Mar 2001 08:19: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 LAA11921; Mon, 5 Mar 2001 11:18:59 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.2/8.9.1) id f25GITI15947; Mon, 5 Mar 2001 11:18:29 -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 Message-ID: <15011.48213.655850.515898@grasshopper.cs.duke.edu> Date: Mon, 5 Mar 2001 11:18:29 -0500 (EST) To: raymond@one.com.au Cc: freebsd-alpha@freebsd.org Subject: Re: alpha/25535: unaligned access crash on stq In-Reply-To: <200103050041.f250fP281920@freefall.freebsd.org> References: <200103050041.f250fP281920@freefall.freebsd.org> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org raymond@one.com.au writes: > systab->lockfree->fwd_link = NULL; // only one The problem is that our unaligned access handling code has a bug in that it does not handle storing unaligned zeros. This is because it does not handle storing from register R31. The following patch should fix it: Index: trap.c =================================================================== RCS file: /home/ncvs/src/sys/alpha/alpha/trap.c,v retrieving revision 1.26.2.2 diff -u -r1.26.2.2 trap.c --- trap.c 2000/05/24 14:20:57 1.26.2.2 +++ trap.c 2001/03/05 16:04:23 @@ -777,8 +777,9 @@ #define unaligned_store(storage, ptrf, mod) \ if ((regptr = ptrf(p, reg)) == NULL) \ - break; \ - (storage) = mod (*regptr); \ + (storage) = 0; \ + else \ + (storage) = mod (*regptr); \ if (copyout(&(storage), (caddr_t)va, sizeof (storage)) == 0) \ signal = 0; \ else \ I've just comitted this to -current. Excellent problem report, BTW. Had that null not been staring me in the face, I wouldn't have been able to figure this out. You really should fix your code, if you can. Unaligned stores are horribly expensive, as each load or store involves a trap into the kernel. Cheers, Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Mar 5 8:57:44 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id ACE1837B719; Mon, 5 Mar 2001 08:57:42 -0800 (PST) (envelope-from gallatin@FreeBSD.org) Received: (from gallatin@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f25GvgX35955; Mon, 5 Mar 2001 08:57:42 -0800 (PST) (envelope-from gallatin) Date: Mon, 5 Mar 2001 08:57:42 -0800 (PST) From: Message-Id: <200103051657.f25GvgX35955@freefall.freebsd.org> To: raymond@one.com.au, gallatin@FreeBSD.org, freebsd-alpha@freebsd.org Subject: Re: alpha/25535: unaligned access crash on stq Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Synopsis: unaligned access crash on stq State-Changed-From-To: open->closed State-Changed-By: gallatin State-Changed-When: Mon Mar 5 08:56:46 PST 2001 State-Changed-Why: fixed in -stable and -current with rev 1.51 and 1.15.2.3 of alpha/alpha/trap.c http://www.freebsd.org/cgi/query-pr.cgi?pr=25535 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Mar 5 9: 8:12 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id D47A437B719 for ; Mon, 5 Mar 2001 09:08:09 -0800 (PST) (envelope-from mjacob@feral.com) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id JAA03024; Mon, 5 Mar 2001 09:07:59 -0800 Date: Mon, 5 Mar 2001 09:07:57 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Andrew Gallatin Cc: raymond@one.com.au, freebsd-alpha@FreeBSD.ORG Subject: Re: alpha/25535: unaligned access crash on stq In-Reply-To: <15011.48213.655850.515898@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 Thanks Drew- I had just gone to pull my Brown Book to follow up on this and just figured out that the register was r31... > > raymond@one.com.au writes: > > systab->lockfree->fwd_link = NULL; // only one > > > The problem is that our unaligned access handling code has a bug in > that it does not handle storing unaligned zeros. This is because it > does not handle storing from register R31. The following patch should > fix it: > > Index: trap.c > =================================================================== > RCS file: /home/ncvs/src/sys/alpha/alpha/trap.c,v > retrieving revision 1.26.2.2 > diff -u -r1.26.2.2 trap.c > --- trap.c 2000/05/24 14:20:57 1.26.2.2 > +++ trap.c 2001/03/05 16:04:23 > @@ -777,8 +777,9 @@ > > #define unaligned_store(storage, ptrf, mod) \ > if ((regptr = ptrf(p, reg)) == NULL) \ > - break; \ > - (storage) = mod (*regptr); \ > + (storage) = 0; \ > + else \ > + (storage) = mod (*regptr); \ > if (copyout(&(storage), (caddr_t)va, sizeof (storage)) == 0) \ > signal = 0; \ > else \ > > I've just comitted this to -current. > > Excellent problem report, BTW. Had that null not been staring me in the > face, I wouldn't have been able to figure this out. > > You really should fix your code, if you can. Unaligned stores are > horribly expensive, as each load or store involves a trap into the > kernel. > > Cheers, > > Drew > > > 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 Mar 5 9:47:29 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id AF74137B718 for ; Mon, 5 Mar 2001 09:47:26 -0800 (PST) (envelope-from mjacob@feral.com) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id JAA03346; Mon, 5 Mar 2001 09:47:21 -0800 Date: Mon, 5 Mar 2001 09:47:19 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Christian Weisgerber Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: My list of -CURRENT problems In-Reply-To: <9806fj$1si$1@kemoauc.mips.inka.de> 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, 5 Mar 2001, Christian Weisgerber wrote: > I rebuilt my box from yesterdays' tree. Here's my list of annoying > problems: > > * [new] > Installing ports/lang/compaq-cc panics the machine. Actually, > I think executing a Linux binary through the linuxulator triggers > this. > > * [new] > If sysvipc is loaded as modules, the linuxulator module fails to > load with "link_elf: symbol shmctl undefined". This doesn't > happen if sysvipc is compiled statically into the kernel. > I reported this a couple of days ago on freebsd-emulation, but > didn't get any affirmation or useful response. > I wouldn't expect this to be specific to alpha, but I don't know. > > * [old] bin/25361 > dump(8) segfaults. After some miscommunication with Matt Jacob > the PR ended up in category bin, although the bug is supposedly > alpha-only. Miscommunication? You got peeved at me... oh well :-)! Yes, it's on my list. > > * [old] alpha/25284. > With a graphics console, reboot(8) fails on PC164. > > * [old] > The PC164 realtime clock is still in 2000. This is also on my list. It's only for some PC164s. You also filed: alpha/25284: PC164 won't reboot with graphics console -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Mar 5 9:50:54 2001 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 4D08F37B719 for ; Mon, 5 Mar 2001 09:50:50 -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 MAA13851; Mon, 5 Mar 2001 12:50:48 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.2/8.9.1) id f25HoIe16718; Mon, 5 Mar 2001 12:50: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 Message-ID: <15011.53722.757140.878738@grasshopper.cs.duke.edu> Date: Mon, 5 Mar 2001 12:50:18 -0500 (EST) To: naddy@mips.inka.de (Christian Weisgerber) Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: My list of -CURRENT problems In-Reply-To: <9806fj$1si$1@kemoauc.mips.inka.de> References: <9806fj$1si$1@kemoauc.mips.inka.de> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Christian Weisgerber writes: > I rebuilt my box from yesterdays' tree. Here's my list of annoying > problems: > > * [new] > Installing ports/lang/compaq-cc panics the machine. Actually, > I think executing a Linux binary through the linuxulator triggers > this. > > * [new] > If sysvipc is loaded as modules, the linuxulator module fails to > load with "link_elf: symbol shmctl undefined". This doesn't > happen if sysvipc is compiled statically into the kernel. > I reported this a couple of days ago on freebsd-emulation, but > didn't get any affirmation or useful response. > I wouldn't expect this to be specific to alpha, but I don't know. > I'm looking at these 2. This fixes the second, but leaves me mystified, because the code should be loaded, as the osfulator needs it too, and the linux module won't load even after the sysV modules are loaded (!): Drew Index: alpha/linux/linux_sysvec.c =================================================================== RCS file: /home/ncvs/src/sys/alpha/linux/linux_sysvec.c,v retrieving revision 1.72 diff -u -r1.72 linux_sysvec.c --- alpha/linux/linux_sysvec.c 2001/01/24 10:26:13 1.72 +++ alpha/linux/linux_sysvec.c 2001/03/05 17:43:17 @@ -61,6 +61,9 @@ MODULE_VERSION(linux, 1); MODULE_DEPEND(linux, osf1, 1, 1, 1); +MODULE_DEPEND(linux, sysvmsg, 1, 1, 1); +MODULE_DEPEND(linux, sysvsem, 1, 1, 1); +MODULE_DEPEND(linux, sysvshm, 1, 1, 1); MALLOC_DEFINE(M_LINUX, "linux", "Linux mode structures"); To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Mar 5 10: 2:47 2001 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 9688837B718 for ; Mon, 5 Mar 2001 10:02: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 NAA14094; Mon, 5 Mar 2001 13:02:42 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.2/8.9.1) id f25I2CT16793; Mon, 5 Mar 2001 13:02:12 -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 Message-ID: <15011.54436.155555.663570@grasshopper.cs.duke.edu> Date: Mon, 5 Mar 2001 13:02:12 -0500 (EST) To: naddy@mips.inka.de (Christian Weisgerber) Cc: freebsd-alpha@freebsd.org Subject: Re: My list of -CURRENT problems In-Reply-To: <9806fj$1si$1@kemoauc.mips.inka.de> References: <9806fj$1si$1@kemoauc.mips.inka.de> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Christian Weisgerber writes: > I rebuilt my box from yesterdays' tree. Here's my list of annoying > problems: > > * [new] > Installing ports/lang/compaq-cc panics the machine. Actually, > I think executing a Linux binary through the linuxulator triggers > this. > > * [new] > If sysvipc is loaded as modules, the linuxulator module fails to > load with "link_elf: symbol shmctl undefined". This doesn't > happen if sysvipc is compiled statically into the kernel. > I reported this a couple of days ago on freebsd-emulation, but > didn't get any affirmation or useful response. > I wouldn't expect this to be specific to alpha, but I don't know. > I think I've fixed both of these now. The panic was due to the brandinfo struct changing and nobody updating the linux/alpha code to match the state of the world. Grab 1.74 of alpha/linux_sysvec.c and you should be OK. BTW, sorry for not responding sooner. I don't read emulation (tho I probably should, given that I maintain 1.25 emulators..). Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Mar 5 10:23:57 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from baron.fujimori.cache.waseda.ac.jp (baron.fujimori.cache.waseda.ac.jp [133.9.152.155]) by hub.freebsd.org (Postfix) with ESMTP id E837E37B718 for ; Mon, 5 Mar 2001 10:23:55 -0800 (PST) (envelope-from fujimori@baron.fujimori.cache.waseda.ac.jp) Received: from baron.fujimori.cache.waseda.ac.jp (localhost [127.0.0.1]) by baron.fujimori.cache.waseda.ac.jp (8.11.1/8.11.1) with ESMTP id f25INdT38459; Tue, 6 Mar 2001 03:23:43 +0900 (JST) (envelope-from fujimori@baron.fujimori.cache.waseda.ac.jp) Message-Id: <200103051823.f25INdT38459@baron.fujimori.cache.waseda.ac.jp> To: mjacob@feral.com Cc: freebsd-alpha@freebsd.org Subject: Re: My list of -CURRENT problems In-Reply-To: Your message of "Mon, 05 Mar 2001 09:47:19 PST." Date: Mon, 05 Mar 2001 18:23:39 +0000 From: Yoriaki FUJIMORI Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org As for a realtime clock problem, it should persist on many alphapc164, pc164lx and up1100. At least in my lab, they all suffer from this. It was a fun to see `Feb 29, 2000' on all of them. (;_;) I guess FreeBSD/Alpha alone makes use of mcclock.c. I could not find its counterpart in FreeBSD/i386. Yoriaki Fujimori To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Mar 5 10:30:21 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 4ABDF37B719 for ; Mon, 5 Mar 2001 10:30:19 -0800 (PST) (envelope-from mjacob@feral.com) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id KAA03603; Mon, 5 Mar 2001 10:30:17 -0800 Date: Mon, 5 Mar 2001 10:30:15 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Yoriaki FUJIMORI Cc: freebsd-alpha@freebsd.org Subject: Re: My list of -CURRENT problems In-Reply-To: <200103051823.f25INdT38459@baron.fujimori.cache.waseda.ac.jp> 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 > > As for a realtime clock problem, it should persist on many alphapc164, > pc164lx and up1100. At least in my lab, they all suffer from this. > It was a fun to see `Feb 29, 2000' on all of them. (;_;) > > I guess FreeBSD/Alpha alone makes use of mcclock.c. I could not find > its counterpart in FreeBSD/i386. that's correct. it's a non-Y2K compliant chip that is only on digital machines To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Mar 5 11:25:36 2001 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 3723737B718 for ; Mon, 5 Mar 2001 11:25:34 -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 OAA15974; Mon, 5 Mar 2001 14:25:31 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.2/8.9.1) id f25JP1c17089; Mon, 5 Mar 2001 14:25:01 -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 Message-ID: <15011.59405.333814.964428@grasshopper.cs.duke.edu> Date: Mon, 5 Mar 2001 14:25:01 -0500 (EST) To: Christian Weisgerber Cc: mjacob@feral.com, freebsd-alpha@FreeBSD.ORG Subject: Re: My list of -CURRENT problems In-Reply-To: References: <9806fj$1si$1@kemoauc.mips.inka.de> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Matthew Jacob writes: > > > > * [old] bin/25361 > > dump(8) segfaults. After some miscommunication with Matt Jacob > > the PR ended up in category bin, although the bug is supposedly > > alpha-only. > > Miscommunication? You got peeved at me... oh well :-)! > Yes, it's on my list. FWIW, I cannot reproduce this on my UP1000, either using a scsi disk (sym driver), or using a ide disk. Perhaps it is scsi-controller specific? What type of scsi controller is in this machine? Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Mar 5 11:27:49 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id B302237B718 for ; Mon, 5 Mar 2001 11:27:46 -0800 (PST) (envelope-from mjacob@feral.com) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id LAA03878; Mon, 5 Mar 2001 11:27:44 -0800 Date: Mon, 5 Mar 2001 11:27:42 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Andrew Gallatin Cc: Christian Weisgerber , freebsd-alpha@FreeBSD.ORG Subject: Re: My list of -CURRENT problems In-Reply-To: <15011.59405.333814.964428@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 No- it's a pipe output issue. There is no tape drive involved. > > Matthew Jacob writes: > > > > > > * [old] bin/25361 > > > dump(8) segfaults. After some miscommunication with Matt Jacob > > > the PR ended up in category bin, although the bug is supposedly > > > alpha-only. > > > > Miscommunication? You got peeved at me... oh well :-)! > > Yes, it's on my list. > > FWIW, I cannot reproduce this on my UP1000, either using a scsi disk > (sym driver), or using a ide disk. > > Perhaps it is scsi-controller specific? What type of scsi controller > is in this machine? > > Drew > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Mar 5 11:29: 1 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 393A737B718 for ; Mon, 5 Mar 2001 11:28:59 -0800 (PST) (envelope-from mjacob@feral.com) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id LAA03894; Mon, 5 Mar 2001 11:28:46 -0800 Date: Mon, 5 Mar 2001 11:28:44 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Andrew Gallatin Cc: alpha@FreeBSD.ORG Subject: Re: dump(8) segfaults In-Reply-To: <97b59k$220u$1@kemoauc.mips.inka.de> 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 Sun, 25 Feb 2001, Christian Weisgerber wrote: > This is on alpha--does anybody see this on i386 as well? > > naddy@kemoauc[~] dump 0af /dev/null /dev/da0a > DUMP: Date of this level 0 dump: Sun Feb 25 15:33:49 2001 > DUMP: Date of last level 0 dump: the epoch > DUMP: Dumping /dev/da0a (/) to /dev/null > DUMP: mapping (Pass I) [regular files] > DUMP: mapping (Pass II) [directories] > DUMP: estimated 67655 tape blocks. > DUMP: dumping (Pass III) [directories] > DUMP: dumping (Pass IV) [regular files] > DUMP: SIGSEGV: ABORTING! > DUMP: SIGSEGV: ABORTING! > DUMP: SIGSEGV: ABORTING! > DUMP: SIGSEGV: ABORTING! > DUMP: SIGSEGV: ABORTING! > Segmentation fault > > -current as of Feb 20. > > Sorry- not pipe output, but just output of /dev/null... I haven't checked it myself in a couple of days. -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Mar 5 11:30:49 2001 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 3F2F437B718 for ; Mon, 5 Mar 2001 11:30:46 -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 OAA16121; Mon, 5 Mar 2001 14:30:39 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.2/8.9.1) id f25JU9717105; Mon, 5 Mar 2001 14:30:09 -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 Message-ID: <15011.59713.825545.837185@grasshopper.cs.duke.edu> Date: Mon, 5 Mar 2001 14:30:09 -0500 (EST) To: mjacob@feral.com Cc: Christian Weisgerber , freebsd-alpha@FreeBSD.ORG Subject: Re: My list of -CURRENT problems In-Reply-To: References: <15011.59405.333814.964428@grasshopper.cs.duke.edu> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Matthew Jacob writes: > > No- it's a pipe output issue. There is no tape drive involved. > Can you elaborate further? I cannot reproduce it. I'm running a kernel from today and a world from Feb 26th: # dump 0af /dev/null / DUMP: Date of this level 0 dump: Mon Mar 5 14:09:58 2001 DUMP: Date of last level 0 dump: the epoch DUMP: Dumping /dev/da0a (/) to /dev/null DUMP: mapping (Pass I) [regular files] DUMP: mapping (Pass II) [directories] DUMP: estimated 69061 tape blocks. DUMP: dumping (Pass III) [directories] DUMP: dumping (Pass IV) [regular files] DUMP: DUMP: 69078 tape blocks on 1 volume DUMP: finished in 124 seconds, throughput 557 KBytes/sec DUMP: Closing /dev/null DUMP: DUMP IS DONE # dump 0af /dev/null /dev/ad0a DUMP: Date of this level 0 dump: Mon Mar 5 14:13:12 2001 DUMP: Date of last level 0 dump: the epoch DUMP: Dumping /dev/ad0a to /dev/null DUMP: mapping (Pass I) [regular files] DUMP: mapping (Pass II) [directories] DUMP: estimated 75176 tape blocks. DUMP: dumping (Pass III) [directories] DUMP: dumping (Pass IV) [regular files] DUMP: DUMP: 75194 tape blocks on 1 volume DUMP: finished in 29 seconds, throughput 2592 KBytes/sec DUMP: Closing /dev/null DUMP: DUMP IS DONE #ls -l /sbin/dump -r-xr-sr-x 2 root tty 448360 Feb 26 13:38 /sbin/dump Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Mar 5 11:46: 1 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 5F30B37B718 for ; Mon, 5 Mar 2001 11:45:57 -0800 (PST) (envelope-from mjacob@feral.com) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id LAA03954; Mon, 5 Mar 2001 11:45:46 -0800 Date: Mon, 5 Mar 2001 11:45:39 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Andrew Gallatin Cc: Christian Weisgerber , freebsd-alpha@FreeBSD.ORG Subject: Re: My list of -CURRENT problems In-Reply-To: <15011.59713.825545.837185@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. Maybe it got fixed. I sure was able to reproduce it. Lemme see what I get. > > Matthew Jacob writes: > > > > No- it's a pipe output issue. There is no tape drive involved. > > > > Can you elaborate further? I cannot reproduce it. I'm running a > kernel from today and a world from Feb 26th: > > > # dump 0af /dev/null / > DUMP: Date of this level 0 dump: Mon Mar 5 14:09:58 2001 > DUMP: Date of last level 0 dump: the epoch > DUMP: Dumping /dev/da0a (/) to /dev/null > DUMP: mapping (Pass I) [regular files] > DUMP: mapping (Pass II) [directories] > DUMP: estimated 69061 tape blocks. > DUMP: dumping (Pass III) [directories] > DUMP: dumping (Pass IV) [regular files] > DUMP: DUMP: 69078 tape blocks on 1 volume > DUMP: finished in 124 seconds, throughput 557 KBytes/sec > DUMP: Closing /dev/null > DUMP: DUMP IS DONE > # dump 0af /dev/null /dev/ad0a > DUMP: Date of this level 0 dump: Mon Mar 5 14:13:12 2001 > DUMP: Date of last level 0 dump: the epoch > DUMP: Dumping /dev/ad0a to /dev/null > DUMP: mapping (Pass I) [regular files] > DUMP: mapping (Pass II) [directories] > DUMP: estimated 75176 tape blocks. > DUMP: dumping (Pass III) [directories] > DUMP: dumping (Pass IV) [regular files] > DUMP: DUMP: 75194 tape blocks on 1 volume > DUMP: finished in 29 seconds, throughput 2592 KBytes/sec > DUMP: Closing /dev/null > DUMP: DUMP IS DONE > #ls -l /sbin/dump > -r-xr-sr-x 2 root tty 448360 Feb 26 13:38 /sbin/dump > > > Drew > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Mar 5 13:27:42 2001 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 B936537B718; Mon, 5 Mar 2001 13:27:39 -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 QAA19059; Mon, 5 Mar 2001 16:27:39 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.2/8.9.1) id f25LR9E17372; Mon, 5 Mar 2001 16:27:09 -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 Message-ID: <15012.1197.216891.412601@grasshopper.cs.duke.edu> Date: Mon, 5 Mar 2001 16:27:09 -0500 (EST) To: jhb@freebsd.org Cc: freebsd-alpha@freebsd.org Subject: http://people.freebsd.org/~jhb/patches/scterm.patch X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org John, Can you committ your syscons patch for alpha? It would be nice to have the sysinstall colors right for 4.3-RELEASE... Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Mar 5 13:36:18 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from winston.osd.bsdi.com (winston.osd.bsdi.com [204.216.27.229]) by hub.freebsd.org (Postfix) with ESMTP id B656437B71A; Mon, 5 Mar 2001 13:36:16 -0800 (PST) (envelope-from jkh@osd.bsdi.com) Received: from localhost (jkh@localhost [127.0.0.1]) by winston.osd.bsdi.com (8.11.2/8.11.1) with ESMTP id f25LZUH24338; Mon, 5 Mar 2001 13:35:30 -0800 (PST) (envelope-from jkh@osd.bsdi.com) To: gallatin@cs.duke.edu Cc: jhb@FreeBSD.ORG, freebsd-alpha@FreeBSD.ORG Subject: Re: http://people.freebsd.org/~jhb/patches/scterm.patch In-Reply-To: <15012.1197.216891.412601@grasshopper.cs.duke.edu> References: <15012.1197.216891.412601@grasshopper.cs.duke.edu> X-Mailer: Mew version 1.94.1 on Emacs 20.7 / Mule 4.0 (HANANOEN) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20010305133530U.jkh@osd.bsdi.com> Date: Mon, 05 Mar 2001 13:35:30 -0800 From: Jordan Hubbard X-Dispatcher: imput version 20000228(IM140) Lines: 10 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >It would be nice to have the sysinstall colors right for >4.3-RELEASE... Hear hear! Though I have to say... I was starting to rely on this "feature" as a way of quickly telling the alpha test box from the x86 test box on our console switch. ;-) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Mar 5 13:47:37 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from dove.angel.org (dsl-64-194-138-85.telocity.com [64.194.138.85]) by hub.freebsd.org (Postfix) with ESMTP id 61ECE37B71B for ; Mon, 5 Mar 2001 13:47:34 -0800 (PST) (envelope-from dp@penix.org) Received: from penix.org (Toronto-ppp221235.sympatico.ca [64.228.106.52]) by dove.angel.org (8.11.1/8.11.1) with ESMTP id f25LkiG24726; Mon, 5 Mar 2001 16:46:45 -0500 (EST) (envelope-from dp@penix.org) Message-ID: <3AA40C0B.315C2E86@penix.org> Date: Mon, 05 Mar 2001 16:58:35 -0500 From: Paul Halliday X-Mailer: Mozilla 4.76 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Jordan Hubbard Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: http://people.freebsd.org/~jhb/patches/scterm.patch References: <15012.1197.216891.412601@grasshopper.cs.duke.edu> <20010305133530U.jkh@osd.bsdi.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org You are not seriously thinking of correcting this are you? Jordan Hubbard wrote: > > >It would be nice to have the sysinstall colors right for > >4.3-RELEASE... > > Hear hear! > > Though I have to say... I was starting to rely on this "feature" as a > way of quickly telling the alpha test box from the x86 test box on our > console switch. ;-) As I rely on it for the same purposes. > > - Jordan > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-alpha" in the body of the message -- Paul H. ============================================================================ Don't underestimate the power of stupid people in large groups. Brute force is the last resort of the incompetent. GPG Key fingerprint: 2D7C A7E2 DB1F EA5F 8C6F D5EC 3D39 F274 4AA3 E8B9 Web: http://www3.sympatico.ca/transmogrify Public Key available here: http://www3.sympatico.ca/transmogrify/dp.txt ============================================================================ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Mar 5 14:20:51 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id BCC6337B719 for ; Mon, 5 Mar 2001 14:20:41 -0800 (PST) (envelope-from jhb@FreeBSD.org) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.2/8.11.2) with ESMTP id f25MKTA12074; Mon, 5 Mar 2001 14:20:29 -0800 (PST) (envelope-from jhb@FreeBSD.org) 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 In-Reply-To: <3AA40C0B.315C2E86@penix.org> Date: Mon, 05 Mar 2001 14:20:14 -0800 (PST) From: John Baldwin To: Paul Halliday Subject: Re: http://people.freebsd.org/~jhb/patches/scterm.patch Cc: freebsd-alpha@FreeBSD.org, Jordan Hubbard Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 05-Mar-01 Paul Halliday wrote: > > You are not seriously thinking of correcting this are you? As I said earlier, it's not the 100% correct fix, but it is better than nothing. :) FreeBSD strives to look the same on all platforms, and this is an actual "feature" of SRM in that it screws up the VGA palette. If someone wishes to hack libdialog to use different colors on the alpha explicitly, that is another ball of wax. > Jordan Hubbard wrote: >> >> >It would be nice to have the sysinstall colors right for >> >4.3-RELEASE... >> >> Hear hear! >> >> Though I have to say... I was starting to rely on this "feature" as a >> way of quickly telling the alpha test box from the x86 test box on our >> console switch. ;-) > > As I rely on it for the same purposes. > >> >> - Jordan >> >> To Unsubscribe: send mail to majordomo@FreeBSD.org >> with "unsubscribe freebsd-alpha" in the body of the message > > -- > Paul H. > ============================================================================ > Don't underestimate the power of stupid people in large groups. > Brute force is the last resort of the incompetent. > GPG Key fingerprint: 2D7C A7E2 DB1F EA5F 8C6F D5EC 3D39 F274 4AA3 E8B9 > Web: http://www3.sympatico.ca/transmogrify > Public Key available here: http://www3.sympatico.ca/transmogrify/dp.txt > ============================================================================ > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-alpha" in the body of the message -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - 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 Mon Mar 5 14:21: 6 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id 3C87F37B71A for ; Mon, 5 Mar 2001 14:21:05 -0800 (PST) (envelope-from jhb@FreeBSD.org) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.2/8.11.2) with ESMTP id f25MKSA12070; Mon, 5 Mar 2001 14:20:28 -0800 (PST) (envelope-from jhb@FreeBSD.org) 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 In-Reply-To: <15012.1197.216891.412601@grasshopper.cs.duke.edu> Date: Mon, 05 Mar 2001 14:20:13 -0800 (PST) From: John Baldwin To: Andrew Gallatin Subject: RE: http://people.freebsd.org/~jhb/patches/scterm.patch Cc: freebsd-alpha@FreeBSD.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 05-Mar-01 Andrew Gallatin wrote: > > John, > > Can you committ your syscons patch for alpha? > > It would be nice to have the sysinstall colors right for > 4.3-RELEASE... Well, it's not quite the right fix (screen savers, etc. are still wrong) but ok. The real fix would be to "fix" the palette on boot either by swapping all the red and blue attributes or just writing a default palette out to the VGA controller. > Drew -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - 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 Mon Mar 5 15:40: 7 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id D302037B71A for ; Mon, 5 Mar 2001 15:40:01 -0800 (PST) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f25Ne1709842; Mon, 5 Mar 2001 15:40:01 -0800 (PST) (envelope-from gnats) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 01AD337B718 for ; Mon, 5 Mar 2001 15:39:23 -0800 (PST) (envelope-from nobody@FreeBSD.org) Received: (from nobody@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f25NdMH09772; Mon, 5 Mar 2001 15:39:22 -0800 (PST) (envelope-from nobody) Message-Id: <200103052339.f25NdMH09772@freefall.freebsd.org> Date: Mon, 5 Mar 2001 15:39:22 -0800 (PST) From: raymond@one.com.au To: freebsd-gnats-submit@freebsd.org X-Send-Pr-Version: www-1.0 Subject: alpha/25564: Port ups-debug doesn't build on the alpha Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Number: 25564 >Category: alpha >Synopsis: Port ups-debug doesn't build on the alpha >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-alpha >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Mon Mar 05 15:40:01 PST 2001 >Closed-Date: >Last-Modified: >Originator: Ray Newman >Release: 4.2-RELEASE alpha >Organization: One Management Australia >Environment: FreeBSD alpha.local 4.2-RELEASE FreeBSD 4.2-RELEASE #0: Sat Mar 3 07:27:14 EST 2001 raymond@alpha.local:/usr/src/sys/compile/AS200 alpha >Description: Port ups-debug doesn't build on the alpha - the following are extracts from the log. ... gmake[1]: Entering directory `/usr/ports/devel/ups-debug/work/ups-3.35-beta13/ups' ... cc -c -pipe -O -pipe -DHAVE_CONFIG_H -I. -I/usr/X11R6/include -Idevelhdrs ./ao_target.c ./ao_target.c: In function `ao_tswap': ./ao_target.c:704: `BPT' undeclared (first use in this function) ./ao_target.c:704: (Each undeclared identifier is reported only once ./ao_target.c:704: for each function it appears in.) ./ao_target.c: In function `ao_call_func': ./ao_target.c:1212: `orig_regs' undeclared (first use in this function) gmake[1]: *** [ao_target.o] Error 1 gmake[1]: Leaving directory `/usr/ports/devel/ups-debug/work/ups-3.35-beta13/ups' gmake: *** [ups] Error 2 *** Error code 2 Stop in /usr/ports/devel/ups-debug. *** Error code 1 >How-To-Repeat: Attempt to build ups-debug on the alpha >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 Mon Mar 5 18:47:25 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from gw.one.com.au (gw.one.com.au [203.18.85.1]) by hub.freebsd.org (Postfix) with ESMTP id 3914437B718 for ; Mon, 5 Mar 2001 18:47:20 -0800 (PST) (envelope-from raymond@one.com.au) Received: from one.com.au (pmo.local [10.18.85.2]) by gw.one.com.au (8.9.2/8.9.2) with SMTP id NAA24010 for freebsd-alpha@FreeBSD.org; Tue, 6 Mar 2001 13:01:32 +1000 (EST) (envelope-from raymond@one.com.au) Date: Tue, 6 Mar 2001 13:01:32 +1000 (EST) From: User Raymond Message-Id: <200103060301.NAA24010@gw.one.com.au> Subject: Strange results from compiled alpha code To: freebsd-alpha@FreeBSD.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Subj: Strange results from compiled alpha code To: freebsd-alpha@FreeBSD.org From: raymond@one.com.au This refers to FreeBSD 4.2-RELEASE alpha running on an AS200. Sorry for the size of this post - I have attempted to create a small demonstration program but can't seem to. ...anyway, consider the following piece of c source code: typedef struct CSTRING // our string type { short len; // length of it u_char buf[32768]; // and the content } cstring; // end counted string extern u_char *mumpspc; // mumps prog pointer mumpspc = mumpspc + ((cstring *)mumpspc)->len + sizeof(short) + 1; // point past the string and the following gdb output: 975 mumpspc = mumpspc + (gdb) p mumpspc $1 = (u_char *) 0x120096c7f "\002" (gdb) p mumpspc + ((cstring *)mumpspc)->len + sizeof(short) + 1 $2 = (u_char *) 0x120096c84 "<\001" (gdb) set mumpspc = mumpspc + ((cstring *)mumpspc)->len + sizeof(short) + 1 (gdb) p mumpspc $3 = (u_char *) 0x120096c84 "<\001" (gdb) set mumpspc = 0x120096c7f (gdb) p mumpspc $4 = (u_char *) 0x120096c7f "\002" (gdb) s 978 break; (gdb) p mumpspc $5 = (u_char *) 0x12009a982 "" (gdb) set mumpspc = 0x120096c7f (gdb) p mumpspc[0] $6 = 2 '\002' (gdb) p mumpspc[1] $7 = 0 '\000' (gdb) p mumpspc[2] $8 = 52 '4' (gdb) p mumpspc[3] $9 = 50 '2' (gdb) p mumpspc[4] $10 = 0 '\000' (gdb) p mumpspc[5] $11 = 60 '<' It appears that the "set" is ok when interpreted by gdb but the compiled code gives the wrong answer - it seems to ignore the '\000' at mumpspc[1]. This code works OK on the x86 architecture (FreeBSD and linux); doesn't work with linux alpha either and (yes) I know it's horrible code. but - any ideas? Ray Newman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Mar 5 21: 5:42 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id 8C0A537B719; Mon, 5 Mar 2001 21:05:35 -0800 (PST) (envelope-from jhb@FreeBSD.org) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.2/8.11.2) with ESMTP id f2655QA23808; Mon, 5 Mar 2001 21:05:26 -0800 (PST) (envelope-from jhb@FreeBSD.org) 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 In-Reply-To: <200103060252.f262q8V37395@freefall.freebsd.org> Date: Mon, 05 Mar 2001 21:05:15 -0800 (PST) From: John Baldwin To: alpha@FreeBSD.org Subject: RE: cvs commit: src/sys/alpha/alpha busdma_machdep.c Cc: cvs-all@FreeBSD.org, cvs-committers@FreeBSD.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 06-Mar-01 John Baldwin wrote: > jhb 2001/03/05 18:52:08 PST > > Modified files: > sys/alpha/alpha busdma_machdep.c > Log: > Quiet a warning due to bus_size_t being a long on the alpha. Should this use '%p' instead of '0x%lx' perhaps? -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - 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 Mon Mar 5 22: 9:52 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from diablo.OntheNet.com.au (diablo.OntheNet.com.au [203.10.89.2]) by hub.freebsd.org (Postfix) with ESMTP id 2841037B71A for ; Mon, 5 Mar 2001 22:09:48 -0800 (PST) (envelope-from tonyg@OntheNet.com.au) Received: from lancia.OntheNet.com.au (lancia.OntheNet.com.au [203.13.70.41]) by diablo.OntheNet.com.au (8.9.3/8.9.3) with ESMTP id QAA91904; Tue, 6 Mar 2001 16:09:41 +1000 (EST) Date: Tue, 6 Mar 2001 16:09:41 +1000 (EST) From: Tony Griffiths To: User Raymond Cc: Subject: Re: Strange results from compiled alpha code In-Reply-To: <200103060301.NAA24010@gw.one.com.au> 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 Ray, My quess is that you are running into an alignment problem! In the case you give below, the 'short len' is misaligned on an odd byte boundary. This might be the cause of the problem... I know that with DEC/Compaq cc there is a #pragma and also a compiler switch to assume_unaligned pointers for cases like this. The code that is generated is awfull but the end result is the correct value loaded into the register. I don't know that the [g]cc equivalent switch is but presume that there is one! Alternatively, change the code slightly to ensure that the 'mumpspc' pointer is always incremented by an even number of bytes. eg. mumpspc += ( ((cstring*)mumpspc)->len + sizeof(short) + 2 ) & ~1; /* bump pc and round up */ Tony ----------------------------------------------------------------- On Tue, 6 Mar 2001, User Raymond wrote: > Subj: Strange results from compiled alpha code > To: freebsd-alpha@FreeBSD.org > From: raymond@one.com.au > > This refers to FreeBSD 4.2-RELEASE alpha running on an AS200. > > Sorry for the size of this post - I have attempted to create a small > demonstration program but can't seem to. > > ...anyway, consider the following piece of c source code: > > > typedef struct CSTRING // our string type > { short len; // length of it > u_char buf[32768]; // and the content > } cstring; // end counted string > > extern u_char *mumpspc; // mumps prog pointer > > mumpspc = mumpspc + > ((cstring *)mumpspc)->len + > sizeof(short) + 1; // point past the string > > and the following gdb output: > > 975 mumpspc = mumpspc + > (gdb) p mumpspc > $1 = (u_char *) 0x120096c7f "\002" > (gdb) p mumpspc + ((cstring *)mumpspc)->len + sizeof(short) + 1 > $2 = (u_char *) 0x120096c84 "<\001" > (gdb) set mumpspc = mumpspc + ((cstring *)mumpspc)->len + sizeof(short) + 1 > (gdb) p mumpspc > $3 = (u_char *) 0x120096c84 "<\001" > (gdb) set mumpspc = 0x120096c7f > (gdb) p mumpspc > $4 = (u_char *) 0x120096c7f "\002" > (gdb) s > 978 break; > (gdb) p mumpspc > $5 = (u_char *) 0x12009a982 "" > (gdb) set mumpspc = 0x120096c7f > (gdb) p mumpspc[0] > $6 = 2 '\002' > (gdb) p mumpspc[1] > $7 = 0 '\000' > (gdb) p mumpspc[2] > $8 = 52 '4' > (gdb) p mumpspc[3] > $9 = 50 '2' > (gdb) p mumpspc[4] > $10 = 0 '\000' > (gdb) p mumpspc[5] > $11 = 60 '<' > > > It appears that the "set" is ok when interpreted by gdb but the compiled > code gives the wrong answer - it seems to ignore the '\000' at mumpspc[1]. > > This code works OK on the x86 architecture (FreeBSD and linux); doesn't > work with linux alpha either and (yes) I know it's horrible code. > > but - any ideas? > > Ray Newman > > 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 Mar 5 22:12:45 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id EA67137B718; Mon, 5 Mar 2001 22:12:38 -0800 (PST) (envelope-from mjacob@feral.com) Received: from beppo (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id WAA06438; Mon, 5 Mar 2001 22:12:40 -0800 Date: Mon, 5 Mar 2001 22:12:38 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: John Baldwin Cc: alpha@FreeBSD.org, cvs-all@FreeBSD.org, cvs-committers@FreeBSD.org Subject: RE: cvs commit: src/sys/alpha/alpha busdma_machdep.c 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, 5 Mar 2001, John Baldwin wrote: > > On 06-Mar-01 John Baldwin wrote: > > jhb 2001/03/05 18:52:08 PST > > > > Modified files: > > sys/alpha/alpha busdma_machdep.c > > Log: > > Quiet a warning due to bus_size_t being a long on the alpha. > > Should this use '%p' instead of '0x%lx' perhaps? No. Possibly %q instead of %lx though. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Mar 5 22:29:20 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 4B93937B71A for ; Mon, 5 Mar 2001 22:29:16 -0800 (PST) (envelope-from mjacob@feral.com) Received: from beppo (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id WAA06499; Mon, 5 Mar 2001 22:29:10 -0800 Date: Mon, 5 Mar 2001 22:29:08 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: User Raymond Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: Strange results from compiled alpha code In-Reply-To: <200103060301.NAA24010@gw.one.com.au> 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 Oh, god.... not MUMPS? Aieee! Run! Run! Run!!! The Medical Database from Hell...But if it is indeed mumps, it darn well is supposed to work on Alphas 'coz I believe that Adac Labs switched from Alpha/Vaxen to Alpha/Alpha quite a while back. Generally, this is not really the best forum for this issue as this is not specifically a list for help in porting applications to Alpha. In your specific case you need to really spend more time with the assembly output. In particular if this in general also has problems with Linux/Alpha, it'll have problems here, and we probably can't spend a lot of time helping you in this case. You haven't given enough info, but you, or somebody, is assuming that a char array is mapping sensibly to to the structure you're trying to pun it with. You don't really know how the alpha compiler is possibly padding the short below. On Tue, 6 Mar 2001, User Raymond wrote: > Subj: Strange results from compiled alpha code > To: freebsd-alpha@FreeBSD.org > From: raymond@one.com.au > > This refers to FreeBSD 4.2-RELEASE alpha running on an AS200. > > Sorry for the size of this post - I have attempted to create a small > demonstration program but can't seem to. > > ...anyway, consider the following piece of c source code: > > > typedef struct CSTRING // our string type > { short len; // length of it > u_char buf[32768]; // and the content > } cstring; // end counted string > > extern u_char *mumpspc; // mumps prog pointer > > mumpspc = mumpspc + > ((cstring *)mumpspc)->len + > sizeof(short) + 1; // point past the string > > and the following gdb output: > > 975 mumpspc = mumpspc + > (gdb) p mumpspc > $1 = (u_char *) 0x120096c7f "\002" > (gdb) p mumpspc + ((cstring *)mumpspc)->len + sizeof(short) + 1 > $2 = (u_char *) 0x120096c84 "<\001" > (gdb) set mumpspc = mumpspc + ((cstring *)mumpspc)->len + sizeof(short) + 1 > (gdb) p mumpspc > $3 = (u_char *) 0x120096c84 "<\001" > (gdb) set mumpspc = 0x120096c7f > (gdb) p mumpspc > $4 = (u_char *) 0x120096c7f "\002" > (gdb) s > 978 break; > (gdb) p mumpspc > $5 = (u_char *) 0x12009a982 "" > (gdb) set mumpspc = 0x120096c7f > (gdb) p mumpspc[0] > $6 = 2 '\002' > (gdb) p mumpspc[1] > $7 = 0 '\000' > (gdb) p mumpspc[2] > $8 = 52 '4' > (gdb) p mumpspc[3] > $9 = 50 '2' > (gdb) p mumpspc[4] > $10 = 0 '\000' > (gdb) p mumpspc[5] > $11 = 60 '<' > > > It appears that the "set" is ok when interpreted by gdb but the compiled > code gives the wrong answer - it seems to ignore the '\000' at mumpspc[1]. > > This code works OK on the x86 architecture (FreeBSD and linux); doesn't > work with linux alpha either and (yes) I know it's horrible code. > > but - any ideas? > > Ray Newman > > 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 Tue Mar 6 1:56:52 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from gw.one.com.au (gw.one.com.au [203.18.85.1]) by hub.freebsd.org (Postfix) with ESMTP id 8BE6937B718 for ; Tue, 6 Mar 2001 01:56:46 -0800 (PST) (envelope-from raymond@one.com.au) Received: from one.com.au (pmo.local [10.18.85.2]) by gw.one.com.au (8.9.2/8.9.2) with SMTP id UAA24786 for freebsd-alpha@FreeBSD.ORG; Tue, 6 Mar 2001 20:11:00 +1000 (EST) (envelope-from raymond@one.com.au) Date: Tue, 6 Mar 2001 20:11:00 +1000 (EST) From: User Raymond Message-Id: <200103061011.UAA24786@gw.one.com.au> Subject: Strange results from compiled alpha code To: freebsd-alpha@FreeBSD.ORG Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Subj: Strange results from compiled alpha code From: raymond@one.com.au To: freebsd-alpha@FreeBSD.ORG Tony Griffiths wrote: > Ray, > > My quess is that you are running into an alignment problem! > > In the case you give below, the 'short len' is misaligned on an odd byte > boundary. This might be the cause of the problem... > > I know that with DEC/Compaq cc there is a #pragma and also a compiler switch > to assume_unaligned pointers for cases like this. The code that is > generated is > awfull but the end result is the correct value loaded into the register. I > don't know that the [g]cc equivalent switch is but presume that there is one! > > Alternatively, change the code slightly to ensure that the 'mumpspc' pointer > is always incremented by an even number of bytes. eg. > > mumpspc += ( ((cstring*)mumpspc)->len + sizeof(short) + 2 ) & ~1; /* bump pc > > Tony Matthew Jacob wrote: > Oh, god.... not MUMPS? Aieee! Run! Run! Run!!! The Medical Database from > Hell...But if it is indeed mumps, it darn well is supposed to work on Alphas > 'coz I believe that Adac Labs switched from Alpha/Vaxen to Alpha/Alpha quite > a while back. > > Generally, this is not really the best forum for this issue as this is not > specifically a list for help in porting applications to Alpha. In your > specific case you need to really spend more time with the assembly output. In > particular if this in general also has problems with Linux/Alpha, it'll have > problems here, and we probably can't spend a lot of time helping you in this > case. > > You haven't given enough info, but you, or somebody, is assuming that a char > array is mapping sensibly to to the structure you're trying to pun it with. > You don't really know how the alpha compiler is possibly padding the short > below. I guess that as my mumps implementation uses structures to address byte strings as a major design factor, it will never be ported to alpha or any other risc architecture - tough about that as I have a few spare alphas and my customers have more of them. They are all going to have to upgrade to cisc machines. Ray Newman --- Original message from Ray Newman dated 6 Mar 2001 --- This refers to FreeBSD 4.2-RELEASE alpha running on an AS200. Sorry for the size of this post - I have attempted to create a small demonstration program but can't seem to. ...anyway, consider the following piece of c source code: typedef struct CSTRING // our string type { short len; // length of it u_char buf[32768]; // and the content } cstring; // end counted string extern u_char *mumpspc; // mumps prog pointer mumpspc = mumpspc + ((cstring *)mumpspc)->len + sizeof(short) + 1; // point past the string and the following gdb output: 975 mumpspc = mumpspc + (gdb) p mumpspc $1 = (u_char *) 0x120096c7f "\002" (gdb) p mumpspc + ((cstring *)mumpspc)->len + sizeof(short) + 1 $2 = (u_char *) 0x120096c84 "<\001" (gdb) set mumpspc = mumpspc + ((cstring *)mumpspc)->len + sizeof(short) + 1 (gdb) p mumpspc $3 = (u_char *) 0x120096c84 "<\001" (gdb) set mumpspc = 0x120096c7f (gdb) p mumpspc $4 = (u_char *) 0x120096c7f "\002" (gdb) s 978 break; (gdb) p mumpspc $5 = (u_char *) 0x12009a982 "" (gdb) set mumpspc = 0x120096c7f (gdb) p mumpspc[0] $6 = 2 '\002' (gdb) p mumpspc[1] $7 = 0 '\000' (gdb) p mumpspc[2] $8 = 52 '4' (gdb) p mumpspc[3] $9 = 50 '2' (gdb) p mumpspc[4] $10 = 0 '\000' (gdb) p mumpspc[5] $11 = 60 '<' It appears that the "set" is ok when interpreted by gdb but the compiled code gives the wrong answer - it seems to ignore the '\000' at mumpspc[1]. This code works OK on the x86 architecture (FreeBSD and linux); doesn't work with linux alpha either and (yes) I know it's horrible code. but - any ideas? Ray Newman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Mar 6 1:59: 7 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [209.152.133.57]) by hub.freebsd.org (Postfix) with ESMTP id E766A37B719 for ; Tue, 6 Mar 2001 01:59:05 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.3/8.11.1) id f269x5w31044 for freebsd-alpha@FreeBSD.ORG; Tue, 6 Mar 2001 01:59:05 -0800 (PST) (envelope-from obrien) Date: Tue, 6 Mar 2001 01:59:04 -0800 From: "David O'Brien" To: freebsd-alpha@FreeBSD.ORG Subject: Re: http://people.freebsd.org/~jhb/patches/scterm.patch Message-ID: <20010306015904.A31024@dragon.nuxi.com> Reply-To: freebsd-alpha@FreeBSD.ORG References: <15012.1197.216891.412601@grasshopper.cs.duke.edu> <20010305133530U.jkh@osd.bsdi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010305133530U.jkh@osd.bsdi.com>; from jkh@osd.bsdi.com on Mon, Mar 05, 2001 at 01:35:30PM -0800 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, Mar 05, 2001 at 01:35:30PM -0800, Jordan Hubbard wrote: > Though I have to say... I was starting to rely on this "feature" as a > way of quickly telling the alpha test box from the x86 test box on our > console switch. ;-) Agreed. I quite liked the red color. I've got 1/2 a mind to make it that way on purpose. (we can use yellow on the IA-64, green for PowerPC, etc..) :-))) -- -- David (obrien@FreeBSD.org) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Mar 6 2:14:41 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id 91AB037B718; Tue, 6 Mar 2001 02:14:35 -0800 (PST) (envelope-from bde@zeta.org.au) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id VAA07524; Tue, 6 Mar 2001 21:14:32 +1100 Date: Tue, 6 Mar 2001 21:14:20 +1100 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: John Baldwin Cc: alpha@FreeBSD.org, cvs-committers@FreeBSD.org Subject: RE: cvs commit: src/sys/alpha/alpha busdma_machdep.c 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, 5 Mar 2001, John Baldwin wrote: > On 06-Mar-01 John Baldwin wrote: > > jhb 2001/03/05 18:52:08 PST > > > > Modified files: > > sys/alpha/alpha busdma_machdep.c > > Log: > > Quiet a warning due to bus_size_t being a long on the alpha. > > Should this use '%p' instead of '0x%lx' perhaps? No. bus_size_t happens to be an (unsigned) integral type and probably should be documented as such (I think bus sizes tend to be small, so there will never be problems representing them as integers, at least if there is a 64-bit integral type). Printing bus_addr_t's correctly is harder. Bus addresses might need to be represented by arrays or structs. 0x%lx format should never be used. Use %#lx instead. Only give the 0x prefix explicitly if you really want small values to be harder to read. I think you would only want this tables with %0*x formats. Perhaps %#llx format should be used. bus_size_t is opaque, but you have to know that it is no larger than long to print it using %#lx format. Perhaps the value should be cast to the type that matches the format. bus_size_t is opaque, but you have to know that it is u_long to print it using %#lx format. The advantage of this is that it will keep working without warnings if bus_size_t or u_long is changed, provided the values that actually occur can be represented by both bus_size_t and u_long. The disadvantage of this is that it breaks compile-time checking that the arg type matches the format. I usually print typedefed types by converting to [unsigned] long and print using an [unsigned] long format, but machine-dependent code can reasonably know the typedef. When C99 becomes normal, I will usually convert to [u]intmax_t and print using a %j format. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Mar 6 5:31:25 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from mail.inka.de (quechua.inka.de [212.227.14.2]) by hub.freebsd.org (Postfix) with ESMTP id 8BCDB37B718 for ; Tue, 6 Mar 2001 05:31:22 -0800 (PST) (envelope-from daemon@mips.inka.de) Received: from kemoauc.mips.inka.de (uucp@) by mail.inka.de with local-bsmtp id 14aHYf-0001nS-00; Tue, 6 Mar 2001 14:31:21 +0100 Received: (from daemon@localhost) by kemoauc.mips.inka.de (8.11.3/8.11.1) id f26D5Xc04826 for freebsd-alpha@freebsd.org; Tue, 6 Mar 2001 14:05:33 +0100 (CET) (envelope-from daemon) From: naddy@mips.inka.de (Christian Weisgerber) Subject: Re: My list of -CURRENT problems Date: Tue, 6 Mar 2001 13:05:33 +0000 (UTC) Message-ID: <982nat$4ce$1@kemoauc.mips.inka.de> References: <9806fj$1si$1@kemoauc.mips.inka.de> <15011.54436.155555.663570@grasshopper.cs.duke.edu> Originator: naddy@mips.inka.de (Christian Weisgerber) To: freebsd-alpha@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Andrew Gallatin wrote: > Grab 1.74 of alpha/linux_sysvec.c and you should be OK. Yes, I confirm that this is fixed. Thanks Drew! -- Christian "naddy" Weisgerber naddy@mips.inka.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Mar 6 8:31:20 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from mail.inka.de (quechua.inka.de [212.227.14.2]) by hub.freebsd.org (Postfix) with ESMTP id B683B37B718 for ; Tue, 6 Mar 2001 08:31:16 -0800 (PST) (envelope-from daemon@mips.inka.de) Received: from kemoauc.mips.inka.de (uucp@) by mail.inka.de with local-bsmtp id 14aKMl-0000Sy-01; Tue, 6 Mar 2001 17:31:15 +0100 Received: (from daemon@localhost) by kemoauc.mips.inka.de (8.11.3/8.11.1) id f26GCBE15566 for freebsd-alpha@freebsd.org; Tue, 6 Mar 2001 17:12:11 +0100 (CET) (envelope-from daemon) From: naddy@mips.inka.de (Christian Weisgerber) Subject: Re: My list of -CURRENT problems Date: Tue, 6 Mar 2001 16:12:11 +0000 (UTC) Message-ID: <98328r$f38$1@kemoauc.mips.inka.de> References: <9806fj$1si$1@kemoauc.mips.inka.de> <15011.59405.333814.964428@grasshopper.cs.duke.edu> Originator: naddy@mips.inka.de (Christian Weisgerber) To: freebsd-alpha@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Andrew Gallatin wrote: > Perhaps it is scsi-controller specific? What type of scsi controller > is in this machine? sym(4), although I can't imagine this making a difference. There seems to be some variation in the symptoms: naddy@kemoauc[~] dump 0af /dev/null /holding DUMP: Date of this level 0 dump: Tue Mar 6 17:05:02 2001 DUMP: Date of last level 0 dump: the epoch DUMP: Dumping /dev/da1e (/holding) to /dev/null DUMP: mapping (Pass I) [regular files] DUMP: mapping (Pass II) [directories] DUMP: estimated 3831 tape blocks. DUMP: slave couldn't reopen disk: Interrupted system call DUMP: The ENTIRE dump is aborted. (Or maybe this is entirely unrelated.) -- Christian "naddy" Weisgerber naddy@mips.inka.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Mar 6 10:25:48 2001 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 4A61F37B718; Tue, 6 Mar 2001 10:25:44 -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 NAA09322; Tue, 6 Mar 2001 13:25:43 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.2/8.9.1) id f26IPDM20186; Tue, 6 Mar 2001 13:25:13 -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 Message-ID: <15013.11144.757425.205222@grasshopper.cs.duke.edu> Date: Tue, 6 Mar 2001 13:25:12 -0500 (EST) To: naddy@mips.inka.de (Christian Weisgerber) Cc: freebsd-alpha@FreeBSD.ORG, phk@FreeBSD.ORG Subject: Dump segv w/devfs (was Re: My list of -CURRENT problems) In-Reply-To: <98328r$f38$1@kemoauc.mips.inka.de> References: <9806fj$1si$1@kemoauc.mips.inka.de> <15011.59405.333814.964428@grasshopper.cs.duke.edu> <98328r$f38$1@kemoauc.mips.inka.de> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Christian Weisgerber writes: > Andrew Gallatin wrote: > > > Perhaps it is scsi-controller specific? What type of scsi controller > > is in this machine? > > sym(4), although I can't imagine this making a difference. <...> OK, it seems to be related to devfs. Dumping with /dev/null as a file crashes. Dumping to a normal file elsewhere works. Dumping through a redirect to /dev/null (tcsh) seems to work as well. /dev/null as a "file" works just fine w/o devfs. Eg: dump 0af - / > /dev/null - works dump 0af /usr/tmp/foo / - works dump 0af /dev/null / - SEGV w/devfs, works with normal /dev Anybody have some ideas? Does this happen only on alphas? ( I don't have a -current PC). FWIW, cat'ting the resulting /usr/tmp/foo to /dev/null works just dandy.. 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 Tue Mar 6 10:28:20 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from critter.freebsd.dk (flutter.freebsd.dk [212.242.40.147]) by hub.freebsd.org (Postfix) with ESMTP id 38BF237B719 for ; Tue, 6 Mar 2001 10:28:17 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.1/8.11.1) with ESMTP id f26ISWB10100; Tue, 6 Mar 2001 19:28:32 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Andrew Gallatin Cc: naddy@mips.inka.de (Christian Weisgerber), freebsd-alpha@FreeBSD.ORG Subject: Re: Dump segv w/devfs (was Re: My list of -CURRENT problems) In-Reply-To: Your message of "Tue, 06 Mar 2001 13:25:12 EST." <15013.11144.757425.205222@grasshopper.cs.duke.edu> Date: Tue, 06 Mar 2001 19:28:32 +0100 Message-ID: <10098.983903312@critter> From: Poul-Henning Kamp Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message <15013.11144.757425.205222@grasshopper.cs.duke.edu>, Andrew Gallatin writes: > >Christian Weisgerber writes: > > Andrew Gallatin wrote: > > > > > Perhaps it is scsi-controller specific? What type of scsi controller > > > is in this machine? > > > > sym(4), although I can't imagine this making a difference. ><...> > >OK, it seems to be related to devfs. Dumping with /dev/null as a file >crashes. Dumping to a normal file elsewhere works. Dumping through a >redirect to /dev/null (tcsh) seems to work as well. > >/dev/null as a "file" works just fine w/o devfs. > >Eg: > >dump 0af - / > /dev/null - works >dump 0af /usr/tmp/foo / - works >dump 0af /dev/null / - SEGV w/devfs, works with normal /dev How about running dump under a debugger and try to find out where it SEGV's ? -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Mar 6 10:53:33 2001 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 C22CA37B718 for ; Tue, 6 Mar 2001 10:53:30 -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 NAA10112; Tue, 6 Mar 2001 13:53:29 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.2/8.9.1) id f26IqxQ20238; Tue, 6 Mar 2001 13:52: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 Message-ID: <15013.12810.999432.661437@grasshopper.cs.duke.edu> Date: Tue, 6 Mar 2001 13:52:58 -0500 (EST) To: Poul-Henning Kamp Cc: naddy@mips.inka.de (Christian Weisgerber), freebsd-alpha@FreeBSD.ORG Subject: Re: Dump segv w/devfs (was Re: My list of -CURRENT problems) In-Reply-To: <10098.983903312@critter> References: <15013.11144.757425.205222@grasshopper.cs.duke.edu> <10098.983903312@critter> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Poul-Henning Kamp writes: > >dump 0af - / > /dev/null - works > >dump 0af /usr/tmp/foo / - works > >dump 0af /dev/null / - SEGV w/devfs, works with normal /dev > > How about running dump under a debugger and try to find out where > it SEGV's ? Too simple? ;-) Now that I'm _trying_ to get it to segv, I can't. So I take back what I said about devfs now that I can't reproduce it anymore.. I've got it sitting in a while 1 loop, with coredumps enabled now... 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 6 11: 0:21 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from mx0.gmx.net (mx0.gmx.de [213.165.64.100]) by hub.freebsd.org (Postfix) with SMTP id A859C37B71A for ; Tue, 6 Mar 2001 11:00:17 -0800 (PST) (envelope-from Kai_Allard_Liao@gmx.de) Received: (qmail 6889 invoked by uid 0); 6 Mar 2001 19:00:15 -0000 Date: Tue, 6 Mar 2001 20:00:15 +0100 (MET) From: Oliver Lehmann To: freebsd-alpha@freebsd.org MIME-Version: 1.0 Subject: Create a Bootdisk X-Priority: 3 (Normal) X-Authenticated-Sender: #0001579535@gmx.net X-Authenticated-IP: [62.227.155.220] Message-ID: <26099.983905215@www21.gmx.net> X-Mailer: WWW-Mail 1.5 (Global Message Exchange) X-Flags: 0001 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi again, now, i have installed FreeBSD sucessfully on this AlphaPC 164Lx machine. but i need a bootdisk to boot it. So i try: fdformat fd0 disklabel -B -r -w fd0 fd1440 newfs /dev/rfd0a mount /dev/fd0a /mnt echo '0:da(0,a)/boot/loader' >/mnt/boot.config But when the machine boots with the created floppy it tells me: Can't open /boot/loader Can it be, that i must put the kernel bootloader and so on to the disk too? How can i doo this? Actually i must reinstall the system for each failed boot prograss. its not verry fine :-( Olli -- Sent through GMX FreeMail - http://www.gmx.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Mar 6 12:31:53 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from mail.inka.de (quechua.inka.de [212.227.14.2]) by hub.freebsd.org (Postfix) with ESMTP id 8D85B37B71A; Tue, 6 Mar 2001 12:31:47 -0800 (PST) (envelope-from naddy@mips.inka.de) Received: from kemoauc.mips.inka.de (uucp@) by mail.inka.de with local-bsmtp id 14aO7W-0003LC-00; Tue, 6 Mar 2001 21:31:46 +0100 Received: (from naddy@localhost) by kemoauc.mips.inka.de (8.11.3/8.11.1) id f26K6sO25868; Tue, 6 Mar 2001 21:06:54 +0100 (CET) (envelope-from naddy) Date: Tue, 6 Mar 2001 21:06:54 +0100 From: Christian Weisgerber To: Andrew Gallatin Cc: freebsd-alpha@FreeBSD.ORG, phk@FreeBSD.ORG Subject: Re: Dump segv w/devfs Message-ID: <20010306210654.A25183@kemoauc.mips.inka.de> References: <9806fj$1si$1@kemoauc.mips.inka.de> <15011.59405.333814.964428@grasshopper.cs.duke.edu> <98328r$f38$1@kemoauc.mips.inka.de> <15013.11144.757425.205222@grasshopper.cs.duke.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <15013.11144.757425.205222@grasshopper.cs.duke.edu>; from gallatin@cs.duke.edu on Tue, Mar 06, 2001 at 01:25:12PM -0500 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Andrew Gallatin: > OK, it seems to be related to devfs. Dumping with /dev/null as a file > crashes. Dumping to a normal file elsewhere works. No, it doesn't. I originally noticed the problem when my backup script, which runs dump 0af /holding/disk $filesystem failed. And this problem still persists. (/holding/disk is just a normal file on an FFS. Different disk, same SCSI adapter.) Dumping to /dev/null is merely another convenient way to reproduce this. > Dumping through a redirect to /dev/null (tcsh) seems to work as > well. Fails as well. -- Christian "naddy" Weisgerber naddy@mips.inka.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Mar 6 12:44:45 2001 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 C041B37B71A; Tue, 6 Mar 2001 12:44:37 -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 PAA12808; Tue, 6 Mar 2001 15:44:36 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.2/8.9.1) id f26Ki6C20679; Tue, 6 Mar 2001 15:44:06 -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 Message-ID: <15013.19478.880920.81093@grasshopper.cs.duke.edu> Date: Tue, 6 Mar 2001 15:44:06 -0500 (EST) To: Christian Weisgerber Cc: freebsd-alpha@FreeBSD.ORG, phk@FreeBSD.ORG Subject: Re: Dump segv w/devfs In-Reply-To: <20010306210654.A25183@kemoauc.mips.inka.de> References: <9806fj$1si$1@kemoauc.mips.inka.de> <15011.59405.333814.964428@grasshopper.cs.duke.edu> <98328r$f38$1@kemoauc.mips.inka.de> <15013.11144.757425.205222@grasshopper.cs.duke.edu> <20010306210654.A25183@kemoauc.mips.inka.de> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Christian Weisgerber writes: > Andrew Gallatin: > > > OK, it seems to be related to devfs. Dumping with /dev/null as a file > > crashes. Dumping to a normal file elsewhere works. > > No, it doesn't. > I originally noticed the problem when my backup script, which runs > > dump 0af /holding/disk $filesystem > > failed. And this problem still persists. > (/holding/disk is just a normal file on an FFS. Different disk, > same SCSI adapter.) > > Dumping to /dev/null is merely another convenient way to reproduce > this. > > > Dumping through a redirect to /dev/null (tcsh) seems to work as > > well. > > Fails as well. I've only seen it once & cannot make it happen again. I've had dump in a while 1 loop for 2 hours. I can't get it to crash. Since nobody else can reliably reproduce this but you, can you please build dump with symbols and get a coredump, or run it under gdb? 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 6 14:31:27 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from mail.inka.de (quechua.inka.de [212.227.14.2]) by hub.freebsd.org (Postfix) with ESMTP id 349B437B719 for ; Tue, 6 Mar 2001 14:31:24 -0800 (PST) (envelope-from naddy@mips.inka.de) Received: from kemoauc.mips.inka.de (uucp@) by mail.inka.de with local-bsmtp id 14aPzH-0000IR-01; Tue, 6 Mar 2001 23:31:23 +0100 Received: (from naddy@localhost) by kemoauc.mips.inka.de (8.11.3/8.11.1) id f26Lpdi38683; Tue, 6 Mar 2001 22:51:39 +0100 (CET) (envelope-from naddy) Date: Tue, 6 Mar 2001 22:51:39 +0100 From: Christian Weisgerber To: Andrew Gallatin Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: Dump segv w/devfs Message-ID: <20010306225139.A38325@kemoauc.mips.inka.de> References: <9806fj$1si$1@kemoauc.mips.inka.de> <15011.59405.333814.964428@grasshopper.cs.duke.edu> <98328r$f38$1@kemoauc.mips.inka.de> <15013.11144.757425.205222@grasshopper.cs.duke.edu> <20010306210654.A25183@kemoauc.mips.inka.de> <15013.19478.880920.81093@grasshopper.cs.duke.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <15013.19478.880920.81093@grasshopper.cs.duke.edu>; from gallatin@cs.duke.edu on Tue, Mar 06, 2001 at 03:44:06PM -0500 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Andrew Gallatin: > Since nobody else can reliably reproduce this but you, can you please > build dump with symbols and get a coredump, or run it under gdb? dump forks into five processes (tty handler, master, three slaves). I don't see how I could reasonably run this under gdb. Backtrace from the core dump: (gdb) bt #0 0x1600bc228 in read () from /usr/lib/libc.so.5 #1 0x12000c394 in bread (blkno=536909936, buf=0x11ffb4e8 "\024\223", size=1) at traverse.c:602 #2 0x120009c30 in doslave (cmd=536999504, slave_number=8) at tape.c:783 #3 0x120009870 in enslave () at tape.c:719 #4 0x120009314 in startnewtape (top=301971080) at tape.c:623 #5 0x120004264 in main (argc=0, argv=0x0) at main.c:417 That blkno looks absurd. -- Christian "naddy" Weisgerber naddy@mips.inka.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Mar 6 16: 9: 1 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id 6882E37B718 for ; Tue, 6 Mar 2001 16:08:59 -0800 (PST) (envelope-from jhb@FreeBSD.org) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.2/8.11.2) with ESMTP id f2708rA56144 for ; Tue, 6 Mar 2001 16:08:53 -0800 (PST) (envelope-from jhb@FreeBSD.org) 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 In-Reply-To: <20010306015904.A31024@dragon.nuxi.com> Date: Tue, 06 Mar 2001 16:08:39 -0800 (PST) From: John Baldwin To: freebsd-alpha@FreeBSD.org Subject: Re: http://people.freebsd.org/~jhb/patches/scterm.patch Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 06-Mar-01 David O'Brien wrote: > On Mon, Mar 05, 2001 at 01:35:30PM -0800, Jordan Hubbard wrote: >> Though I have to say... I was starting to rely on this "feature" as a >> way of quickly telling the alpha test box from the x86 test box on our >> console switch. ;-) > > Agreed. I quite liked the red color. > I've got 1/2 a mind to make it that way on purpose. > (we can use yellow on the IA-64, green for PowerPC, etc..) :-))) Hmm, just change libdialog's background color then. :) The rest of the colors I would keep the same however. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - 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 6 18: 4:58 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [209.152.133.57]) by hub.freebsd.org (Postfix) with ESMTP id 6BDC137B718 for ; Tue, 6 Mar 2001 18:04:56 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.3/8.11.1) id f2724p115293; Tue, 6 Mar 2001 18:04:51 -0800 (PST) (envelope-from obrien) Date: Tue, 6 Mar 2001 18:04:51 -0800 From: "David O'Brien" To: Oliver Lehmann Cc: freebsd-alpha@freebsd.org Subject: Re: Create a Bootdisk Message-ID: <20010306180451.A15226@dragon.nuxi.com> Reply-To: freebsd-alpha@freebsd.org References: <26099.983905215@www21.gmx.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <26099.983905215@www21.gmx.net>; from Kai_Allard_Liao@gmx.de on Tue, Mar 06, 2001 at 08:00:15PM +0100 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, Mar 06, 2001 at 08:00:15PM +0100, Oliver Lehmann wrote: > now, i have installed FreeBSD sucessfully on this AlphaPC 164Lx > machine. but i need a bootdisk to boot it. So i try: Why? -- -- David (obrien@FreeBSD.org) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Mar 6 18:18:33 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from mx0.gmx.net (mx0.gmx.de [213.165.64.100]) by hub.freebsd.org (Postfix) with SMTP id C837E37B718 for ; Tue, 6 Mar 2001 18:18:30 -0800 (PST) (envelope-from Kai_Allard_Liao@gmx.de) Received: (qmail 22502 invoked by uid 0); 7 Mar 2001 02:18:28 -0000 Date: Wed, 7 Mar 2001 03:18:28 +0100 (MET) From: Oliver Lehmann To: freebsd-alpha@freebsd.org MIME-Version: 1.0 Subject: Re: Create a Bootdisk X-Priority: 3 (Normal) X-Authenticated-Sender: #0001579535@gmx.net X-Authenticated-IP: [62.227.155.220] Message-ID: <23783.983931508@www16.gmx.net> X-Mailer: WWW-Mail 1.5 (Global Message Exchange) X-Flags: 0001 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, 6 Mar 2001 18:04:51 -0800 "David O'Brien" wrote: > On Tue, Mar 06, 2001 at 08:00:15PM +0100, Oliver Lehmann wrote: > > now, i have installed FreeBSD sucessfully on this AlphaPC 164Lx > > machine. but i need a bootdisk to boot it. So i try: > > Why? The SRM Bios does not detect My Netstorm 885 (Symbios 885) SCSI Controller, and no attached hard disks. but i think i've found an Solution. I can't use "set rootdev=" on the bootloader, because i can only use bios-detected harddisks at these moment. But - I think i can use: # # The root device and filesystem type can be compiled in; # this provides a fallback option if the root device cannot # be correctly guessed by the bootstrap code, or an override if # the RB_DFLTROOT flag (-r) is specified when booting the kernel. # options ROOTDEVNAME=\"ufs:da0s1a\" in the kernel configuration file. Ok, i try it... tomorrow (better later today ;-). Olli -- Sent through GMX FreeMail - http://www.gmx.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Mar 6 18:55:21 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from mx0.gmx.net (mx0.gmx.net [213.165.64.100]) by hub.freebsd.org (Postfix) with SMTP id 4E27837B719 for ; Tue, 6 Mar 2001 18:55:19 -0800 (PST) (envelope-from Kai_Allard_Liao@gmx.de) Received: (qmail 8464 invoked by uid 0); 7 Mar 2001 02:55:18 -0000 Date: Wed, 7 Mar 2001 03:55:18 +0100 (MET) From: Oliver Lehmann To: freebsd-alpha@freebsd.org MIME-Version: 1.0 Subject: X-Priority: 3 (Normal) X-Authenticated-Sender: #0001579535@gmx.net X-Authenticated-IP: [62.227.155.220] Message-ID: <16906.983933718@www9.gmx.net> X-Mailer: WWW-Mail 1.5 (Global Message Exchange) X-Flags: 0001 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, 7 Mar 2001 03:18:28 +0100 (MET) Oliver Lehmann wrote: > options ROOTDEVNAME=\"ufs:da0s1a\" i've tryed this on my i386 system at home wit ad0s1a but that does not work, why? i've create a "boot.config" at my disk wit -r inside and reboot. but the kernel trys to mount fd0c but WHY ? i dont understand it.. i've spcified the ROOTDEVNAME in the kernel staticly... Olli -- Sent through GMX FreeMail - http://www.gmx.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Mar 6 19:14:11 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from mass.dis.org (mass.dis.org [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id 1B70D37B718 for ; Tue, 6 Mar 2001 19:14:09 -0800 (PST) (envelope-from msmith@mass.dis.org) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.2/8.11.2) with ESMTP id f273GCL04322; Tue, 6 Mar 2001 19:16:12 -0800 (PST) (envelope-from msmith@mass.dis.org) Message-Id: <200103070316.f273GCL04322@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Oliver Lehmann Cc: freebsd-alpha@freebsd.org Subject: Re: In-reply-to: Your message of "Wed, 07 Mar 2001 03:55:18 +0100." <16906.983933718@www9.gmx.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 06 Mar 2001 19:16:12 -0800 From: Mike Smith Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > On Wed, 7 Mar 2001 03:18:28 +0100 (MET) > Oliver Lehmann wrote: > > > options ROOTDEVNAME=\"ufs:da0s1a\" > > i've tryed this on my i386 system at home wit ad0s1a but that does not work, > why? i've create a "boot.config" at my disk wit -r inside and reboot. but > the kernel trys to mount fd0c but WHY ? i dont understand it.. i've spcified > the ROOTDEVNAME in the kernel staticly... ROOTDEVNAME is an ultimate fallback unless you boot with the '-r' flag. ie. 'boot -r' will always use the compiled-in ROOTDEVNAME. If you don't specify '-r', ROOTDEVNAME is only used if both the /etc/fstab check and the fallbacks (determined by where the kernel was booted from, etc.) all fail. In your case, you have a UFS filesystem on fd0, so one of the fallbacks is succeeding. This wouldn't be the case on an Alpha, since the SRM disk interface is all weird and stuff. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Mar 6 22: 2:36 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from grafin.fujimori.cache.waseda.ac.jp (grafin.fujimori.cache.waseda.ac.jp [133.9.152.154]) by hub.freebsd.org (Postfix) with ESMTP id 049C537B719 for ; Tue, 6 Mar 2001 22:02:33 -0800 (PST) (envelope-from fujimori@grafin.fujimori.cache.waseda.ac.jp) Received: from grafin.fujimori.cache.waseda.ac.jp (fujimori@localhost [127.0.0.1]) by grafin.fujimori.cache.waseda.ac.jp (8.9.3/3.7W) with ESMTP id PAA04748 for ; Wed, 7 Mar 2001 15:02:31 +0900 Message-Id: <200103070602.PAA04748@grafin.fujimori.cache.waseda.ac.jp> To: freebsd-alpha@freebsd.org Subject: Sym driver, instable(?) Date: Wed, 07 Mar 2001 15:02:31 +0000 From: Yoriaki FUJIMORI Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Folks, I have been testing several scsi (u2w) cards on up1100. Cards are tekram 390F/u2b, noname 4306LVD, iti3400 (uw) etc. They are all driven by a sym driver. In the meantime, often I see a kernel warning: Warning: received processor correctable error. This occurs when I run compilers. At first, I igonored this, but later I noticed this may lead to scsi bus reset ... blahblah ... or even a system freeze, if I invoke heavy disk access, like % make clean in /usr/ports. I checked the overheat problem of scsi chips, but it was not the case. These cards work just fine on pc164lx- and alphapc164-based boxes. So, I guess sym driver may have some timing problem or others on PC100-based up1100. # I have not yet tested Adaptec. Best wishes, Yoriaki Fujimori To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Mar 6 22:33:32 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 528C237B719 for ; Tue, 6 Mar 2001 22:33:30 -0800 (PST) (envelope-from mjacob@feral.com) Received: from beppo (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id WAA10993; Tue, 6 Mar 2001 22:33:14 -0800 Date: Tue, 6 Mar 2001 22:33:11 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Yoriaki FUJIMORI Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: Sym driver, instable(?) In-Reply-To: <200103070602.PAA04748@grafin.fujimori.cache.waseda.ac.jp> 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 Wed, 7 Mar 2001, Yoriaki FUJIMORI wrote: > Folks, > I have been testing several scsi (u2w) cards on up1100. > Cards are tekram 390F/u2b, noname 4306LVD, iti3400 (uw) etc. > They are all driven by a sym driver. > In the meantime, often I see a kernel warning: > Warning: received processor correctable error. Flakey memory. > This occurs when I run compilers. > > At first, I igonored this, but later I noticed this may lead to > scsi bus reset ... blahblah ... > or even a system freeze, if I invoke heavy disk access, like > % make clean > in /usr/ports. > > I checked the overheat problem of scsi chips, but it was not the case. > These cards work just fine on pc164lx- and alphapc164-based boxes. > So, I guess sym driver may have some timing problem or others on > PC100-based up1100. > # I have not yet tested Adaptec. > > Best wishes, > Yoriaki Fujimori > > 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 Tue Mar 6 22:58: 8 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from grafin.fujimori.cache.waseda.ac.jp (grafin.fujimori.cache.waseda.ac.jp [133.9.152.154]) by hub.freebsd.org (Postfix) with ESMTP id 5619D37B719 for ; Tue, 6 Mar 2001 22:58:04 -0800 (PST) (envelope-from fujimori@grafin.fujimori.cache.waseda.ac.jp) Received: from grafin.fujimori.cache.waseda.ac.jp (fujimori@localhost [127.0.0.1]) by grafin.fujimori.cache.waseda.ac.jp (8.9.3/3.7W) with ESMTP id PAA04852; Wed, 7 Mar 2001 15:58:01 +0900 Message-Id: <200103070658.PAA04852@grafin.fujimori.cache.waseda.ac.jp> To: mjacob@feral.com Cc: freebsd-alpha@freebsd.org Subject: Re: Sym driver, instable(?) In-reply-to: Your message of "Tue, 06 Mar 2001 22:33:11 PST." Date: Wed, 07 Mar 2001 15:58:01 +0000 From: Yoriaki FUJIMORI Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I should have written this before: I thought that memory DIMMs had got some problems, and tried several DIMMs. The result was the same. If I run the system without scsi cards I mentioned, I do not see the error. I do not say that the sym driver seems to be unstable on all types of alpha boxes. My experience is just on up1100. Yoriaki Fujimori To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Mar 6 22:59:36 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 8660237B718 for ; Tue, 6 Mar 2001 22:59:34 -0800 (PST) (envelope-from mjacob@feral.com) Received: from beppo (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id WAA11055; Tue, 6 Mar 2001 22:59:33 -0800 Date: Tue, 6 Mar 2001 22:59:30 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Yoriaki FUJIMORI Cc: freebsd-alpha@freebsd.org Subject: Re: Sym driver, instable(?) In-Reply-To: <200103070658.PAA04852@grafin.fujimori.cache.waseda.ac.jp> 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 Wed, 7 Mar 2001, Yoriaki FUJIMORI wrote: > > I should have written this before: > I thought that memory DIMMs had got some problems, and tried several DIMMs. > The result was the same. > If I run the system without scsi cards I mentioned, I do not see the error. > > I do not say that the sym driver seems to be unstable on all types of > alpha boxes. My experience is just on up1100. Well, I'll let the SYM author comment (he's also very knowledgeable about systems). Buf you're seeing "processor error corrected" messages, you're seeing corrected memory errors. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Mar 7 0:18:57 2001 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 BA01B37B71A for ; Wed, 7 Mar 2001 00:18:53 -0800 (PST) (envelope-from ticso@mail.cicely.de) Received: from mail.cicely.de (cicely.de [194.231.9.142]) by mail.du.gtn.com (8.11.0.Beta3/8.11.0.Beta3) with ESMTP id f278Ipe07572; Wed, 7 Mar 2001 09:18:51 +0100 (MET) Received: (from ticso@localhost) by mail.cicely.de (8.11.0/8.11.0) id f278JAA14533; Wed, 7 Mar 2001 09:19:10 +0100 (CET) Date: Wed, 7 Mar 2001 09:19:09 +0100 From: Bernd Walter To: Matthew Jacob Cc: Yoriaki FUJIMORI , freebsd-alpha@FreeBSD.ORG Subject: Re: Sym driver, instable(?) Message-ID: <20010307091909.B14421@cicely20.cicely.de> References: <200103070658.PAA04852@grafin.fujimori.cache.waseda.ac.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from mjacob@feral.com on Tue, Mar 06, 2001 at 10:59:30PM -0800 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, Mar 06, 2001 at 10:59:30PM -0800, Matthew Jacob wrote: > > > On Wed, 7 Mar 2001, Yoriaki FUJIMORI wrote: > > > > > I should have written this before: > > I thought that memory DIMMs had got some problems, and tried several DIMMs. > > The result was the same. > > If I run the system without scsi cards I mentioned, I do not see the error. > > > > I do not say that the sym driver seems to be unstable on all types of > > alpha boxes. My experience is just on up1100. > > Well, I'll let the SYM author comment (he's also very knowledgeable about > systems). Buf you're seeing "processor error corrected" messages, you're > seeing corrected memory errors. I can speak from expirience that they are capable to hang your system. Usually they are corrected very well but in some rare cases the system hangs - maybe if the correcting routine is having a ram fault as well. That doesn't seem to be a FreeBSD problem as even the SRM may hang because of this. As it was a new module I already exchanged it. -- 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 Wed Mar 7 0:34:52 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from mx0.gmx.net (mx0.gmx.net [213.165.64.100]) by hub.freebsd.org (Postfix) with SMTP id 6DE1F37B71A for ; Wed, 7 Mar 2001 00:34:48 -0800 (PST) (envelope-from Kai_Allard_Liao@gmx.de) Received: (qmail 20569 invoked by uid 0); 7 Mar 2001 08:34:47 -0000 Date: Wed, 7 Mar 2001 09:34:47 +0100 (MET) From: Oliver Lehmann To: freebsd-alpha@freebsd.org MIME-Version: 1.0 Subject: Re: Bootdisk X-Priority: 3 (Normal) X-Authenticated-Sender: #0001579535@gmx.net X-Authenticated-IP: [62.227.155.220] Message-ID: <29453.983954087@www9.gmx.net> X-Mailer: WWW-Mail 1.5 (Global Message Exchange) X-Flags: 0001 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, 06 Mar 2001 19:16:12 -0800 Mike Smith wrote: > ROOTDEVNAME is an ultimate fallback unless you boot with the '-r' flag. ok, but why the machine takes the ROOTDEVNAME only when i type "boot -r" in the autoloader, not when i set "-r" in the boot.config file? And, when u say that does not work on the alpha machine. What can i do on this machine to bring it up? Olli -- Sent through GMX FreeMail - http://www.gmx.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Mar 7 10: 7:32 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from mail.interchange.ca (ns.interchange.ca [216.126.79.2]) by hub.freebsd.org (Postfix) with ESMTP id 905EC37B71A for ; Wed, 7 Mar 2001 10:07:29 -0800 (PST) (envelope-from michael@fastmail.ca) Received: by mail.interchange.ca (Fastmailer, from userid 555) id 6A24920AB; Wed, 7 Mar 2001 13:07:06 -0500 (EST) MIME-Version: 1.0 Message-Id: <3AA678CA.000273.49488@frodo.searchcanada.ca> Content-Type: Multipart/Mixed; boundary="------------Boundary-00=_UBAU6IZ1VJAPJEDD7TH0" To: freebsd-alpha@freebsd.org Subject: AS 1200 Install Problems From: "Michael Richards" X-Fastmail-IP: 24.43.130.237 Date: Wed, 7 Mar 2001 13:07:06 -0500 (EST) Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org --------------Boundary-00=_UBAU6IZ1VJAPJEDD7TH0 Content-Type: Text/Plain Content-Transfer-Encoding: 7bit Hi. I've got an AlphaServer 1200 with 2 533 CPUs in it. I installed the latest version of SRM and was not able to get it to boot from disk. I hear that the fdd boot does not work properly. I downloaded boot.flp (the 2.88mb version). I put the boot drive in another system and ran: dd if=boot.flp of=/dev/da1 Which should have copied the image to the disk. I put the disk back into the AS1200 and here is what it said when I tried to boot from it: AlphaServer 1200 Console V5.9-5, 8-JAN-2001 10:05:24 CPU 0 booting (boot dka600.6.0.1.1 -flags 0) block 0 of dka600.6.0.1.1 is a valid boot block reading 15 blocks from dka600.6.0.1.1 bootstrap code read in Building FRU table base = 200000, image_start = 0, image_bytes = 1e00 initializing HWRPB at 2000 initializing page table at 1f2000 initializing machine state setting affinity to the primary CPU jumping to bootstrap code Loading /boot/loader Console: SRM firmware console VMS PAL rev: 0x4000200010115 OSF PAL rev: 0x4000200020117 Switch to OSF PAL code succeeded. FreeBSD Alpha SRM boot disk, Revision 1.0 (jkh@rawhide.osd.bsdi.com, Tue Nov 21 03:14:37 GMT 2000) Memory: 262144 k failed to send read to dka600.6.0.1.1 device dka600.6.0.1.1 no longer valid Anyone have any ideas? -Michael _________________________________________________________________ http://fastmail.ca/ - Fast Free Web Email for Canadians --------------Boundary-00=_UBAU6IZ1VJAPJEDD7TH0-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Mar 7 10:10:40 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 6ACDE37B718 for ; Wed, 7 Mar 2001 10:10:36 -0800 (PST) (envelope-from mjacob@feral.com) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id KAA13390; Wed, 7 Mar 2001 10:10:21 -0800 Date: Wed, 7 Mar 2001 10:10:18 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Michael Richards Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: AS 1200 Install Problems In-Reply-To: <3AA678CA.000273.49488@frodo.searchcanada.ca> 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 Akk. This is awful. You're now expriencing symptoms that are the same as what the floppy boot has. My only suggestion on this is to see what 4.3 does for you- a change in size of bootblock heap went in and I'm *hoping* that this clears this problem up (for now good reason- we really don't know what's happening here except that SRM all of a sudden stops being able to do I/O to the device we're reading from). -matt > Hi. > > I've got an AlphaServer 1200 with 2 533 CPUs in it. I installed the > latest version of SRM and was not able to get it to boot from disk. I > hear that the fdd boot does not work properly. > > I downloaded boot.flp (the 2.88mb version). I put the boot drive in > another system and ran: > dd if=boot.flp of=/dev/da1 > Which should have copied the image to the disk. I put the disk back > into the AS1200 and here is what it said when I tried to boot from it: > > AlphaServer 1200 Console V5.9-5, 8-JAN-2001 10:05:24 > > CPU 0 booting > > (boot dka600.6.0.1.1 -flags 0) > block 0 of dka600.6.0.1.1 is a valid boot block > reading 15 blocks from dka600.6.0.1.1 > bootstrap code read in > Building FRU table > base = 200000, image_start = 0, image_bytes = 1e00 > initializing HWRPB at 2000 > initializing page table at 1f2000 > initializing machine state > setting affinity to the primary CPU > jumping to bootstrap code > Loading /boot/loader > Console: SRM firmware console > VMS PAL rev: 0x4000200010115 > OSF PAL rev: 0x4000200020117 > Switch to OSF PAL code succeeded. > > FreeBSD Alpha SRM boot disk, Revision 1.0 > (jkh@rawhide.osd.bsdi.com, Tue Nov 21 03:14:37 GMT 2000) > Memory: 262144 k > failed to send read to dka600.6.0.1.1 > device dka600.6.0.1.1 no longer valid > > Anyone have any ideas? > > -Michael > _________________________________________________________________ > http://fastmail.ca/ - Fast Free Web Email for Canadians To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Mar 7 10:18:31 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from mail.interchange.ca (ns.interchange.ca [216.126.79.2]) by hub.freebsd.org (Postfix) with ESMTP id 14F4437B719 for ; Wed, 7 Mar 2001 10:18:28 -0800 (PST) (envelope-from michael@fastmail.ca) Received: by mail.interchange.ca (Fastmailer, from userid 555) id 4EAC320F7; Wed, 7 Mar 2001 13:18:08 -0500 (EST) MIME-Version: 1.0 Message-Id: <3AA67B60.00024F.52902@frodo.searchcanada.ca> Content-Type: Multipart/Mixed; boundary="------------Boundary-00=_8UAU6WVYANYPJEDD7TH0" To: mjacob@feral.com Subject: Re: AS 1200 Install Problems Cc: freebsd-alpha@FreeBSD.ORG From: "Michael Richards" X-Fastmail-IP: 24.43.130.237 Date: Wed, 7 Mar 2001 13:18:08 -0500 (EST) Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org --------------Boundary-00=_8UAU6WVYANYPJEDD7TH0 Content-Type: Text/Plain Content-Transfer-Encoding: 7bit If I could get it installed on this machine, it was my intention to start building debug boot floppies and find/fix the problem. Is it possible that since I'm running the very latest SRM version that I'm experiencing this problem while others are not? How long before I can get a 4.3 boot floppy image? -Michael > Akk. This is awful. You're now expriencing symptoms that are the > same as what the floppy boot has. > > My only suggestion on this is to see what 4.3 does for you- a > change in size of bootblock heap went in and I'm *hoping* that > this clears this problem up (for now good reason- we really don't > know what's happening here except that SRM all of a sudden stops > being able to do I/O to the device we're reading from). > > -matt > > > >> Hi. >> >> I've got an AlphaServer 1200 with 2 533 CPUs in it. I installed >> the latest version of SRM and was not able to get it to boot from >> disk. I hear that the fdd boot does not work properly. >> >> I downloaded boot.flp (the 2.88mb version). I put the boot drive >> in another system and ran: >> dd if=boot.flp of=/dev/da1 >> Which should have copied the image to the disk. I put the disk >> back into the AS1200 and here is what it said when I tried to >> boot from it: >> >> AlphaServer 1200 Console V5.9-5, 8-JAN-2001 10:05:24 >> >> CPU 0 booting >> >> (boot dka600.6.0.1.1 -flags 0) >> block 0 of dka600.6.0.1.1 is a valid boot block >> reading 15 blocks from dka600.6.0.1.1 >> bootstrap code read in >> Building FRU table >> base = 200000, image_start = 0, image_bytes = 1e00 >> initializing HWRPB at 2000 >> initializing page table at 1f2000 >> initializing machine state >> setting affinity to the primary CPU >> jumping to bootstrap code >> Loading /boot/loader >> Console: SRM firmware console >> VMS PAL rev: 0x4000200010115 >> OSF PAL rev: 0x4000200020117 >> Switch to OSF PAL code succeeded. >> >> FreeBSD Alpha SRM boot disk, Revision 1.0 >> (jkh@rawhide.osd.bsdi.com, Tue Nov 21 03:14:37 GMT 2000) >> Memory: 262144 k >> failed to send read to dka600.6.0.1.1 >> device dka600.6.0.1.1 no longer valid >> >> Anyone have any ideas? >> >> -Michael >> _________________________________________________________________ >> http://fastmail.ca/ - Fast Free Web Email for Canadians _________________________________________________________________ http://fastmail.ca/ - Fast Free Web Email for Canadians --------------Boundary-00=_8UAU6WVYANYPJEDD7TH0-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Mar 7 10:23:33 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 18D7237B719 for ; Wed, 7 Mar 2001 10:23:31 -0800 (PST) (envelope-from mjacob@feral.com) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id KAA13465; Wed, 7 Mar 2001 10:23:31 -0800 Date: Wed, 7 Mar 2001 10:23:29 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Michael Richards Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: AS 1200 Install Problems In-Reply-To: <3AA67B60.00024F.52902@frodo.searchcanada.ca> 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 > If I could get it installed on this machine, it was my intention to > start building debug boot floppies and find/fix the problem. Is it > possible that since I'm running the very latest SRM version that I'm > experiencing this problem while others are not? I don't know. I don't have a 1200. The 4100s I have are fairly up to date WRT SRM. It may also be memory cluster size related. We really don't know. > > How long before I can get a 4.3 boot floppy image? That's up to the release folks. Last I tried, I couldn't do a buildworld in -stable- I'm sure this is fixed now, but I haven't tried to go back and do so and produce floppies either. -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Mar 7 12:40:35 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from front7m.grolier.fr (front7m.grolier.fr [195.36.216.57]) by hub.freebsd.org (Postfix) with ESMTP id 7FEFC37B71B for ; Wed, 7 Mar 2001 12:40:32 -0800 (PST) (envelope-from groudier@club-internet.fr) Received: from nas1-92.cgy.club-internet.fr (nas1-92.cgy.club-internet.fr [195.36.197.92]) by front7m.grolier.fr (8.9.3/No_Relay+No_Spam_MGC990224) with ESMTP id VAA06420; Wed, 7 Mar 2001 21:40:12 +0100 (MET) Date: Wed, 7 Mar 2001 19:29:59 +0100 (CET) From: =?ISO-8859-1?Q?G=E9rard_Roudier?= X-Sender: groudier@linux.local To: Yoriaki FUJIMORI Cc: mjacob@feral.com, freebsd-alpha@FreeBSD.ORG Subject: Re: Sym driver, instable(?) In-Reply-To: <200103070658.PAA04852@grafin.fujimori.cache.waseda.ac.jp> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, 7 Mar 2001, Yoriaki FUJIMORI wrote: > I should have written this before: > I thought that memory DIMMs had got some problems, and tried several DIMM= s. > The result was the same. > If I run the system without scsi cards I mentioned, I do not see the erro= r. You wrote in your initial mail that your system often complaint about a "processor correctable error". Can the software trigger such an error? If it is pure hardware cause, then the SYM driver will have no means to help you here. > I do not say that the sym driver seems to be unstable on all types of > alpha boxes. My experience is just on up1100. Would be interesting, IMO, to know if things go better using another O/S or or another driver (duno about the SCSI chip of the up1100; if the ncr supports it, you may give a try with that driver too). G=E9rard. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Mar 7 13:40:14 2001 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 2DA2937B71A for ; Wed, 7 Mar 2001 13:40:11 -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 QAA11107; Wed, 7 Mar 2001 16:40:08 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.2/8.9.1) id f27Ldcp26403; Wed, 7 Mar 2001 16:39:38 -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 Message-ID: <15014.43674.685777.603431@grasshopper.cs.duke.edu> Date: Wed, 7 Mar 2001 16:39:38 -0500 (EST) To: "Michael Richards" Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: AS 1200 Install Problems In-Reply-To: <3AA678CA.000273.49488@frodo.searchcanada.ca> References: <3AA678CA.000273.49488@frodo.searchcanada.ca> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Michael Richards writes: > > FreeBSD Alpha SRM boot disk, Revision 1.0 > (jkh@rawhide.osd.bsdi.com, Tue Nov 21 03:14:37 GMT 2000) > Memory: 262144 k > failed to send read to dka600.6.0.1.1 > device dka600.6.0.1.1 no longer valid > > Anyone have any ideas? Is the disk slow? This happens with CDROMs too, so perhaps it has something to do with the speed of the media. I think it might have something to do with our loader reading config files a byte at a time (as witnessed on a netboot via tcpdump). 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 7 13:42:42 2001 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 44EE237B71A for ; Wed, 7 Mar 2001 13:42:39 -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 QAA11182; Wed, 7 Mar 2001 16:42:32 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.2/8.9.1) id f27Lg2G26417; Wed, 7 Mar 2001 16:42:02 -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 Message-ID: <15014.43818.604197.335043@grasshopper.cs.duke.edu> Date: Wed, 7 Mar 2001 16:42:02 -0500 (EST) To: "Michael Richards" Cc: mjacob@feral.com, freebsd-alpha@FreeBSD.ORG Subject: Re: AS 1200 Install Problems In-Reply-To: <3AA67B60.00024F.52902@frodo.searchcanada.ca> References: <3AA67B60.00024F.52902@frodo.searchcanada.ca> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Michael Richards writes: > If I could get it installed on this machine, it was my intention to > start building debug boot floppies and find/fix the problem. Is it Woo-hoo!! > possible that since I'm running the very latest SRM version that I'm > experiencing this problem while others are not? > > How long before I can get a 4.3 boot floppy image? No clue. But you can grab a copy of the loader and boot1 from http://www.cs.duke.edu/~gallatin/boot/ These are from yesterday's -current. Try replacing the loader and bootblocks on your floppy with these to test out Matt's theory. 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 7 13:43:37 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from netau1.alcanet.com.au (ntp.alcanet.com.au [203.62.196.27]) by hub.freebsd.org (Postfix) with ESMTP id 08D1B37B71A for ; Wed, 7 Mar 2001 13:43:33 -0800 (PST) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: from mfg1.cim.alcatel.com.au (mfg1.cim.alcatel.com.au [139.188.23.1]) by netau1.alcanet.com.au (8.9.3 (PHNE_22672)/8.9.3) with ESMTP id IAA24440; Thu, 8 Mar 2001 08:43:17 +1100 (EDT) Received: from gsmx07.alcatel.com.au by cim.alcatel.com.au (PMDF V5.2-32 #37640) with ESMTP id <01K0Y51YBDUOOZ2UCJ@cim.alcatel.com.au>; Thu, 8 Mar 2001 08:43:14 +1100 Received: (from jeremyp@localhost) by gsmx07.alcatel.com.au (8.11.1/8.11.1) id f27LhC925338; Thu, 08 Mar 2001 08:43:12 +1100 (EST envelope-from jeremyp) Content-return: prohibited Date: Thu, 08 Mar 2001 08:43:11 +1100 From: Peter Jeremy Subject: Re: Strange results from compiled alpha code In-reply-to: <200103061011.UAA24786@gw.one.com.au>; from raymond@one.com.au on Tue, Mar 06, 2001 at 08:11:00PM +1000 To: User Raymond Cc: freebsd-alpha@FreeBSD.ORG Mail-Followup-To: User Raymond , freebsd-alpha@FreeBSD.ORG Message-id: <20010308084311.A17181@gsmx07.alcatel.com.au> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-disposition: inline User-Agent: Mutt/1.2.5i References: <200103061011.UAA24786@gw.one.com.au> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 2001-Mar-06 20:11:00 +1000, User Raymond wrote: >Tony Griffiths wrote: >> In the case you give below, the 'short len' is misaligned on an odd byte >> boundary. This might be the cause of the problem... I suspect that gcc is ignoring the low bit of the address when loading the short. The Compaq CC masks the address so as to create an alignment fault in this case. >> I know that with DEC/Compaq cc there is a #pragma and also a >> compiler switch to assume_unaligned pointers for cases like this. ... >> I don't know that the [g]cc equivalent switch is but presume that >> there is one! Actually, there doesn't appear to be one. >> Alternatively, change the code slightly to ensure that the 'mumpspc' pointer >> is always incremented by an even number of bytes. eg. >> >> mumpspc += ( ((cstring*)mumpspc)->len + sizeof(short) + 2 ) & ~1; /* bump pc If you can't guarantee alignment, then your other option is to totally avoid the use of CSTRING and use code like (assuming little-endian data): short len = mumpspc[0] | (mumpspc[1] << 8); mumpspc = mumpspc + len + sizeof(short) + 1; > I have a few spare alphas and my customers have more of them. Does this mean they're now surplus and about to be disposed of? :-) Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Mar 7 13:52:35 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from mx0.gmx.net (mx0.gmx.net [213.165.64.100]) by hub.freebsd.org (Postfix) with SMTP id BB3B837B718 for ; Wed, 7 Mar 2001 13:52:32 -0800 (PST) (envelope-from Kai_Allard_Liao@gmx.de) Received: (qmail 5833 invoked by uid 0); 7 Mar 2001 21:52:31 -0000 Date: Wed, 7 Mar 2001 22:52:31 +0100 (MET) From: Oliver Lehmann To: freebsd-alpha@freebsd.org MIME-Version: 1.0 Subject: Re: Bootdisk X-Priority: 3 (Normal) X-Authenticated-Sender: #0001579535@gmx.net X-Authenticated-IP: [62.227.144.140] Message-ID: <12058.984001951@www11.gmx.net> X-Mailer: WWW-Mail 1.5 (Global Message Exchange) X-Flags: 0001 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi again. Ok, at work i've tryed several things. With the following mehtod, i can boot from disk and change the rootdevice to the scsi disk after loading the kernel: >>> boot dva0 - flags n [ booting kernel ] and after booting the kernel i must insert the rootdevice ( -n flag) ufs:da0a and he boots from my scsi drive. but the problem is, how can i automatize the boot-process? a) normaly the alpha-machin boots with "boot dva0" how can i add the flag? b) how can i set the rootdev static to da0a ? Olli -- Sent through GMX FreeMail - http://www.gmx.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Mar 7 13:52:49 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from mail.interchange.ca (ns.interchange.ca [216.126.79.2]) by hub.freebsd.org (Postfix) with ESMTP id 84F8D37B719 for ; Wed, 7 Mar 2001 13:52:47 -0800 (PST) (envelope-from michael@fastmail.ca) Received: by mail.interchange.ca (Fastmailer, from userid 555) id 95AD920CE; Wed, 7 Mar 2001 16:52:26 -0500 (EST) MIME-Version: 1.0 Message-Id: <3AA6AD9A.0002AD.49488@frodo.searchcanada.ca> Content-Type: Multipart/Mixed; boundary="------------Boundary-00=_ERKU4LL4GENPJEDD7TH0" To: gallatin@cs.duke.edu Subject: Re: AS 1200 Install Problems Cc: freebsd-alpha@FreeBSD.ORG From: "Michael Richards" X-Fastmail-IP: 24.43.130.237 Date: Wed, 7 Mar 2001 16:52:26 -0500 (EST) Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org --------------Boundary-00=_ERKU4LL4GENPJEDD7TH0 Content-Type: Text/Plain Content-Transfer-Encoding: 7bit > > Michael Richards writes: >> >> FreeBSD Alpha SRM boot disk, Revision 1.0 >> (jkh@rawhide.osd.bsdi.com, Tue Nov 21 03:14:37 GMT 2000) >> Memory: 262144 k >> failed to send read to dka600.6.0.1.1 >> device dka600.6.0.1.1 no longer valid >> >> Anyone have any ideas? > > Is the disk slow? This happens with CDROMs too, so perhaps it has > something to do with the speed of the media. I think it might > have something to do with our loader reading config files a byte > at a time (as witnessed on a netboot via tcpdump). The disk is slow, but not _that_ slow. It's an old HDD that I pulled from an AS6000 that's borked. Since I dd'd the image onto the hard drive, how can I just replace the boot loader? -Michael _________________________________________________________________ http://fastmail.ca/ - Fast Free Web Email for Canadians --------------Boundary-00=_ERKU4LL4GENPJEDD7TH0-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Mar 7 13:55:56 2001 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 0B07537B718 for ; Wed, 7 Mar 2001 13:55: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 QAA11677; Wed, 7 Mar 2001 16:55:51 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.2/8.9.1) id f27LtLe26466; Wed, 7 Mar 2001 16:55:21 -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 Message-ID: <15014.44616.990020.519057@grasshopper.cs.duke.edu> Date: Wed, 7 Mar 2001 16:55:20 -0500 (EST) To: Oliver Lehmann Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: Bootdisk In-Reply-To: <12058.984001951@www11.gmx.net> References: <12058.984001951@www11.gmx.net> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Oliver Lehmann writes: > Hi again. > > Ok, at work i've tryed several things. With the following mehtod, i can boot > from disk and change the rootdevice to the scsi disk after loading the > kernel: > > > >>> boot dva0 - flags n > > [ booting kernel ] > > and after booting the kernel i must insert the rootdevice ( -n flag) > > ufs:da0a > > and he boots from my scsi drive. > > but the problem is, how can i automatize the boot-process? > > a) normaly the alpha-machin boots with "boot dva0" how can i add the flag? set bootdefdev dva0 > b) how can i set the rootdev static to da0a ? Can't you just edit the /boot/loader.conf on the floppy and insert a line like: set vfs.root.mountfrom=ufs:/dev/da0a or something like that? 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 7 13:58:22 2001 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 9699537B718 for ; Wed, 7 Mar 2001 13:58:18 -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 QAA11724; Wed, 7 Mar 2001 16:58:17 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.2/8.9.1) id f27Lvl126471; Wed, 7 Mar 2001 16:57:47 -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 Message-ID: <15014.44763.297535.8869@grasshopper.cs.duke.edu> Date: Wed, 7 Mar 2001 16:57:47 -0500 (EST) To: "Michael Richards" Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: AS 1200 Install Problems In-Reply-To: <3AA6AD9A.0002AD.49488@frodo.searchcanada.ca> References: <3AA6AD9A.0002AD.49488@frodo.searchcanada.ca> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Michael Richards writes: > > > > Michael Richards writes: > >> > >> FreeBSD Alpha SRM boot disk, Revision 1.0 > >> (jkh@rawhide.osd.bsdi.com, Tue Nov 21 03:14:37 GMT 2000) > >> Memory: 262144 k > >> failed to send read to dka600.6.0.1.1 > >> device dka600.6.0.1.1 no longer valid > >> > >> Anyone have any ideas? > > > > Is the disk slow? This happens with CDROMs too, so perhaps it has > > something to do with the speed of the media. I think it might > > have something to do with our loader reading config files a byte > > at a time (as witnessed on a netboot via tcpdump). > > The disk is slow, but not _that_ slow. It's an old HDD that I pulled > from an AS6000 that's borked. > > Since I dd'd the image onto the hard drive, how can I just replace > the boot loader? 2 ways: a) use vnconfig to mount the floppy on a FreeBSD machine; replace the loader, unmount & unconfigure the vn device & dd the resulting image onto the disk b) mount that hard disk on a freebsd machine & replace the loader. 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 7 14:11:42 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from mx0.gmx.net (mx0.gmx.net [213.165.64.100]) by hub.freebsd.org (Postfix) with SMTP id 6C10A37B718 for ; Wed, 7 Mar 2001 14:11:39 -0800 (PST) (envelope-from Kai_Allard_Liao@gmx.de) Received: (qmail 29765 invoked by uid 0); 7 Mar 2001 22:11:38 -0000 Date: Wed, 7 Mar 2001 23:11:38 +0100 (MET) From: Oliver Lehmann To: freebsd-alpha@freebsd.org MIME-Version: 1.0 Subject: Re: Bootdisk X-Priority: 3 (Normal) X-Authenticated-Sender: #0001579535@gmx.net X-Authenticated-IP: [62.227.144.140] Message-ID: <5548.984003098@www11.gmx.net> X-Mailer: WWW-Mail 1.5 (Global Message Exchange) X-Flags: 0001 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Ok.. i've tryed this situation at home, because the aloha machine is at work. i compile the kernel on my intel machine at home with: options ROOTDEVNAME=\"ufs:ad0s1a\" then i type at bootstraploader (loader stage 4) boot -r and he change the rootdevice after loading the kernel to ad0s1a. I hope the works on my alpha machine too. I will try this tomorrow (when i am at work ;-) But, how can i change the "default" boot? when i power on my alpha its sems to be, that it oots with "boot dva0" but how can i add "-flags r" to "boot dva0"? i won't change the bootdevice, only add some options to the bootcall... Olli -- Sent through GMX FreeMail - http://www.gmx.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Mar 7 14:30:30 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from mail.interchange.ca (ns.interchange.ca [216.126.79.2]) by hub.freebsd.org (Postfix) with ESMTP id F01A637B71A for ; Wed, 7 Mar 2001 14:30:26 -0800 (PST) (envelope-from michael@fastmail.ca) Received: by mail.interchange.ca (Fastmailer, from userid 555) id 15CE82101; Wed, 7 Mar 2001 17:30:06 -0500 (EST) MIME-Version: 1.0 Message-Id: <3AA6B66E.0000DB.52387@frodo.searchcanada.ca> Content-Type: Multipart/Mixed; boundary="------------Boundary-00=_6IMUU9HAMK8NTT4D7TH0" To: gallatin@cs.duke.edu Subject: Re: AS 1200 Install Problems Cc: freebsd-alpha@FreeBSD.ORG From: "Michael Richards" X-Fastmail-IP: 24.43.130.237 Date: Wed, 7 Mar 2001 17:30:06 -0500 (EST) Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org --------------Boundary-00=_6IMUU9HAMK8NTT4D7TH0 Content-Type: Text/Plain Content-Transfer-Encoding: 7bit >> Since I dd'd the image onto the hard drive, how can I just >> replace the boot loader? > > b) mount that hard disk on a freebsd machine & replace the loader. Ok. I didn't realize this image was a complete filesystem that could be mounted. I replaced boot1 and loader. The machine does the same thing, only this time it shows up as SRM boot disk revision 1.1. Something worth noting, below the memory available it has the | that twirls a bit and stops. After it says: device dka600.6.0.1.1 no longer valid Wait about 5 minutes and it will try to boot. It give the little 10 second thing where you can hit enter to boot immediately and then tries to boot. Then it starts scrolling debug info repeatedly and I can't stop it to read. I presume it's some sort of kernel barf. It did the same thing with the other version of the boot loader (I was playing with it last night). From this I can only guess that it reads part of the image from disk and can't read any more. After the system times out, it believes it has it all and tries to boot, then fails when it hits the part it didn't read. -Michael _________________________________________________________________ http://fastmail.ca/ - Fast Free Web Email for Canadians --------------Boundary-00=_6IMUU9HAMK8NTT4D7TH0-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Mar 7 14:32:29 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from mx0.gmx.net (mx0.gmx.net [213.165.64.100]) by hub.freebsd.org (Postfix) with SMTP id 93F4037B719 for ; Wed, 7 Mar 2001 14:32:27 -0800 (PST) (envelope-from Kai_Allard_Liao@gmx.de) Received: (qmail 9306 invoked by uid 0); 7 Mar 2001 22:32:26 -0000 Date: Wed, 7 Mar 2001 23:32:26 +0100 (MET) From: Oliver Lehmann To: freebsd-alpha@freebsd.org MIME-Version: 1.0 Subject: Re: Bootdisk X-Priority: 3 (Normal) X-Authenticated-Sender: #0001579535@gmx.net X-Authenticated-IP: [62.227.144.140] Message-ID: <4233.984004346@www20.gmx.net> X-Mailer: WWW-Mail 1.5 (Global Message Exchange) X-Flags: 0001 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Ah! i try to set boot_flags tomorrow ;-) cu Olli -- Sent through GMX FreeMail - http://www.gmx.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Mar 7 14:50:29 2001 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 C2AF337B71A for ; Wed, 7 Mar 2001 14:50:24 -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 RAA12953; Wed, 7 Mar 2001 17:50:19 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.2/8.9.1) id f27MnnL26631; Wed, 7 Mar 2001 17:49:49 -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 Message-ID: <15014.47885.16314.207869@grasshopper.cs.duke.edu> Date: Wed, 7 Mar 2001 17:49:49 -0500 (EST) To: "Michael Richards" Cc: freebsd-alpha@freebsd.org Subject: Re: AS 1200 Install Problems In-Reply-To: <3AA6B66E.0000DB.52387@frodo.searchcanada.ca> References: <3AA6B66E.0000DB.52387@frodo.searchcanada.ca> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Michael Richards writes: > >> Since I dd'd the image onto the hard drive, how can I just > >> replace the boot loader? > > > > b) mount that hard disk on a freebsd machine & replace the loader. > > Ok. I didn't realize this image was a complete filesystem that could > be mounted. I replaced boot1 and loader. The machine does the same > thing, only this time it shows up as SRM boot disk revision 1.1. > > Something worth noting, below the memory available it has the | that > twirls a bit and stops. After it says: > device dka600.6.0.1.1 no longer valid > > Wait about 5 minutes and it will try to boot. It give the little 10 > second thing where you can hit enter to boot immediately and then > tries to boot. Then it starts scrolling debug info repeatedly and I > can't stop it to read. I presume it's some sort of kernel barf. It > did the same thing with the other version of the boot loader (I was > playing with it last night). > > >From this I can only guess that it reads part of the image from disk > and can't read any more. After the system times out, it believes it > has it all and tries to boot, then fails when it hits the part it > didn't read. I'd guess that the loader tried to access that disk and the srm console barfed, but it is just a guess. It is hard to say, without seeing a transcript of what happened. Maybe you should use a serial console & post the results. Can you netboot this beast to get it installed? I have an old copy of netboot sitting at www.cs.duke.edu/~gallatin/netboot.gz You need to setup a bootp server so that the (uncompressed) netboot file gets loaded when you boot the AlphaServer from the network (ewa0, probably). You then need to make a root directory NFS mountable by the bootloader and put the kernel.gz file in it from the 2.88MB image. Here's a sample dhcpd.conf stanza: group { use-host-decl-names on ; # key to netbooting Digital Unix clients always-reply-rfc1048 on ; filename "/freebsd/diskless.a/boot/netboot"; option root-path "192.168.0.30:/freebsd/diskless.a/" ; # option routers 152.3.145.61 ; option broadcast-address 152.3.145.255 ; option domain-name-servers 152.3.140.1,152.3.145.240,152.3.250.2; option domain-name "cs.duke.edu duke.edu" ; # host foobar { hardware ethernet 00:60:67:32:6b:e9 ; fixed-address foobar.cs.duke.edu ; } } So you need to have "/freebsd/diskless.a/boot/netboot" TFTP'able and you need to export "/freebsd/diskless.a/" to the alphaserver. And you need to have a "/freebsd/diskless.a/kernel.gz" file to boot, where kernel.gz is from the 2.88MB floppy. Hope that helps, 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 7 18:21: 8 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [209.152.133.57]) by hub.freebsd.org (Postfix) with ESMTP id 195CF37B718 for ; Wed, 7 Mar 2001 18:21:06 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.3/8.11.1) id f282Kbe61548; Wed, 7 Mar 2001 18:20:37 -0800 (PST) (envelope-from obrien) Date: Wed, 7 Mar 2001 18:20:37 -0800 From: "David O'Brien" To: Michael Richards Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: AS 1200 Install Problems Message-ID: <20010307182036.B61445@dragon.nuxi.com> Reply-To: freebsd-alpha@FreeBSD.ORG References: <3AA6B66E.0000DB.52387@frodo.searchcanada.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3AA6B66E.0000DB.52387@frodo.searchcanada.ca>; from michael@fastmail.ca on Wed, Mar 07, 2001 at 05:30:06PM -0500 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, Mar 07, 2001 at 05:30:06PM -0500, Michael Richards wrote: > Something worth noting, below the memory available it has the | that > twirls a bit and stops. After it says: > device dka600.6.0.1.1 no longer valid ... > tries to boot. Then it starts scrolling debug info repeatedly and I > can't stop it to read. I presume it's some sort of kernel barf. It I may have missed where you supplied this info -- if so disregard this email. We really can't do too much debugging with the output of show dev from SRM, and the full boot out put. Considering how easy Alpha's are to setup to use a serial console, can you do that and capture the boot output? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Mar 7 22:33:20 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from smtp1.knology.net (user-24-214-63-11.knology.net [24.214.63.11]) by hub.freebsd.org (Postfix) with SMTP id B4E7337B71A for ; Wed, 7 Mar 2001 22:33:17 -0800 (PST) (envelope-from steve@havk.org) Received: (qmail 12888 invoked by uid 1003); 8 Mar 2001 06:28:06 -0000 Received: from user-24-214-88-8.knology.net (HELO bsd.havk.org) (24.214.88.8) by user-24-214-63-11.knology.net with SMTP; 8 Mar 2001 06:28:06 -0000 Received: by bsd.havk.org (Postfix, from userid 1001) id E06651A7AD; Thu, 8 Mar 2001 00:33:16 -0600 (CST) Date: Thu, 8 Mar 2001 00:33:16 -0600 From: Steve Price To: ports@FreeBSD.org Subject: Alpha packages for 4.3 Message-ID: <20010308003316.D68717@bsd.havk.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i X-Operating-System: FreeBSD 4.2-STABLE i386 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I just started an Alpha package build for 4.3. The logs will be showing up here shortly for anyone that is interested. http://havk.org/alpha/ -- Steve Price To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Mar 8 9:37:14 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from hermes.research.kpn.com (hermes.research.kpn.com [139.63.192.8]) by hub.freebsd.org (Postfix) with ESMTP id 0428137B718 for ; Thu, 8 Mar 2001 09:37:08 -0800 (PST) (envelope-from K.J.Koster@kpn.com) Received: from l04.research.kpn.com (l04.research.kpn.com [139.63.192.204]) by research.kpn.com (PMDF V5.2-31 #42699) with ESMTP id <01K0YPS95G1C000EWZ@research.kpn.com> for freebsd-alpha@freebsd.org; Thu, 8 Mar 2001 18:37:05 +0100 Received: by l04.research.kpn.com with Internet Mail Service (5.5.2653.19) id ; Thu, 08 Mar 2001 18:37:04 +0100 Content-return: allowed Date: Thu, 08 Mar 2001 18:37:04 +0100 From: "Koster, K.J." Subject: make world died... To: 'FreeBSD Alpha mailing list' Message-id: <59063B5B4D98D311BC0D0001FA7E4522026D7C9B@l04.research.kpn.com> MIME-version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Dear all, Here's the last few lines of a make world of -stable as of this weekend: ===> share/doc/usd/12.vi/viapwh touch _stamp.extraobjs (cd /usr/src/share/doc/usd/12.vi/viapwh/../../../../../contrib/nvi/docs/USD.doc/ vitut; groff -mtty-char -Tascii -t -ms -o1- /usr/src/share/doc/usd/12.vi/viapwh/ ../../../../../contrib/nvi/docs/USD.doc/vitut/vi.apwh.ms) | gzip -cn > viapwh.a scii.gz groff: can't find `DESC' file groff:fatal error: invalid device `ascii' ===> share/doc/usd/12.vi/summary touch _stamp.extraobjs (cd /usr/src/share/doc/usd/12.vi/summary/../../../../../contrib/nvi/docs/USD.doc /vitut; groff -mtty-char -Tascii -t -ms -o1- /usr/src/share/doc/usd/12.vi/summar y/../../../../../contrib/nvi/docs/USD.doc/vitut/vi.summary) | gzip -cn > summar y.ascii.gz groff: can't find `DESC' file groff:fatal error: invalid device `ascii' ===> share/doc/usd/13.viref (cd /usr/src/share/doc/usd/13.viref/../../../../contrib/nvi/docs/USD.doc/vi.ref; sed -e\ 's:\(\.so[\ \ ][\ \ ]*\)\(vi.ref\)$:\1/usr/src/share/doc/usd/13.vire f/../../../../contrib/nvi/docs/USD.doc/vi.ref/\2:' -e\ 's:\(\.so[\ \ ][\ \ ]*\)\(ex.cmd.roff\)$:\1/usr/src/share/doc/usd/13.viref/../../../../contrib/n vi/d ocs/USD.doc/vi.ref/\2:' -e\ 's:\(\.so[\ \ ][\ \ ]*\)\(ref.so\)$:\1/usr/s rc/share/doc/usd/13.viref/../../../../contrib/nvi/docs/USD.doc/vi.ref/\2:' -e\ ' s:\(\.so[\ \ ][\ \ ]*\)\(set.opt.roff\)$:\1/usr/src/share/doc/usd/13.viref/ ../../../../contrib/nvi/docs/USD.doc/vi.ref/\2:' -e\ 's:\(\.so[\ \ ][\ \ ]*\)\(vi.cmd.roff\)$:\1/usr/src/share/doc/usd/13.viref/../../../../contrib/n vi/d ocs/USD.doc/vi.ref/\2:' -e 's:^\.so index.so$::' vi.ref) | groff -mtty-char -Ta scii -t -s -me -U -o1- > /dev/null groff: can't find `DESC' file groff:fatal error: invalid device `ascii' *** Error code 3 Stop in /usr/src/share/doc/usd/13.viref. *** Error code 1 Stop in /usr/src/share/doc/usd. *** Error code 1 Stop in /usr/src/share/doc. *** Error code 1 Stop in /usr/src/share. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. What am I doing wrong here? This is my NoName alpha. Kees Jan ================================================ You are only young once, but you can stay immature all your life. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Mar 8 12:45:45 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from jhuml4.jhu.edu (jhuml4.jhu.edu [128.220.2.67]) by hub.freebsd.org (Postfix) with ESMTP id BB9A137B718 for ; Thu, 8 Mar 2001 12:45:40 -0800 (PST) (envelope-from philippe@alpha.ece.jhu.edu) Received: from CONVERSION-DAEMON.jhuml4.jhu.edu by jhuml4.jhu.edu (PMDF V6.0-24 #47563) id <0G9W00101CC39O@jhuml4.jhu.edu> for freebsd-alpha@FreeBSD.ORG; Thu, 08 Mar 2001 15:45:39 -0500 (EST) Received: from alpha.ece.jhu.edu (alpha.ece.jhu.edu [128.220.1.35]) by jhuml4.jhu.edu (PMDF V6.0-24 #47563) with ESMTP id <0G9W00MQWCC2KJ@jhuml4.jhu.edu> for freebsd-alpha@FreeBSD.ORG; Thu, 08 Mar 2001 15:45:39 -0500 (EST) Received: by alpha.ece.jhu.edu (8.8.8/1.1.20.8/15Apr00-0443PM) id PAA0000024187; Thu, 08 Mar 2001 15:50:29 -0500 (EST) Date: Thu, 08 Mar 2001 15:50:29 -0500 (EST) From: "Philippe O. Pouliquen" Subject: Re: Strange results from compiled alpha code To: freebsd-alpha@FreeBSD.ORG Message-id: <200103082050.PAA0000024187@alpha.ece.jhu.edu> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I've had an e-mail exchange with Ray Newman, and have investigated the problem further. Peter Jeremy wrote: > Ray Newman wrote: >>Tony Griffiths wrote: >>> In the case you give below, the 'short len' is misaligned on an >>> odd byte boundary. This might be the cause of the problem... > I suspect that gcc is ignoring the low bit of the address when > loading the short. The Compaq CC masks the address so as to create > an alignment fault in this case. Just to clear things up here, in the C sequence: *((short *) char_pointer) The problem only occurs with GCC when the word (short in C, 16 bit) straddles a quad-word (long in C, 64 bit) boundary. The instruction sequence emitted by GCC works fine for any word completely contained in a quad-word (see end of message). In any case, the instruction sequence *never* generates an alignment trap (it uses LDQ_U) -- it just silently loads the wrong value when the straddling occurs. *This is legal ANSI C behavior.* According to the ANSI C standard, loading a short from an unaligned address results in undefined behavior. The Compaq CC is friendlier: if the word is not word aligned, an alignement trap is generated, and the proper value is loaded by the kernel. >>> I know that with DEC/Compaq cc there is a #pragma and also a >>> compiler switch to assume_unaligned pointers for cases like this. >... >>> I don't know that the [g]cc equivalent switch is but presume that >>> there is one! >Actually, there doesn't appear to be one. #pragma pack 1 only works in Compaq's CC, but causes structure to be created without internal padding. As a side effect, the compiler then assumes that pointers will be misaligned. Packing the structures in Ray's case may be a good thing, because beyond the misaligned pointer, his code assumes that the second structure member is stored two bytes after the first (that's why he has sizeof(short) in there): typedef struct CSTRING { short len; u_char buf[32768]; } cstring; mumpspc += ((cstring*)mumpspc)->len + sizeof(short) + 1; >>> Alternatively, change the code slightly to ensure that the >>> 'mumpspc' pointer is always incremented by an even number of bytes. >>> eg. >>> >>> mumpspc += ( ((cstring*)mumpspc)->len + sizeof(short) + 2 ) & ~1; > > If you can't guarantee alignment, then your other option is to > totally avoid the use of CSTRING and use code like (assuming > little-endian data): > > short len = mumpspc[0] | (mumpspc[1] << 8); > mumpspc = mumpspc + len + sizeof(short) + 1; Ray was hoping not to modify his code, as the problem occurs in many locations. In any case, the code above is not strictly correct. First, it does not properly access the structure elements, because it assumes that 'buf' (second structure member) is stored two bytes (sizeof(short)) after 'len' (first structure member). Second, 'len' is a signed (16 bit) integer, but mumpspc is a pointer to unsigned byte. (and, as mentioned by Peter, the code is endian dependent) Here is the shortest sequence that I could come up with which highlights the problem: ---------------------------------------------------------------- #include unsigned char data[16]={0x01,0x02,0x03,0x04,0x05,0x06,0x07,0x08, 0x09,0x0A,0x0B,0x0C,0x0D,0x0E,0x0F,0x10}; short get_short(unsigned char *ptr) { return(*((short *)ptr)); } main() { printf("0x%X\n",get_short(&(data[7]))); } ---------------------------------------------------------------- gcc version 2.95.2 (alpha-dec-osf4.0) prints 0x100. Comapq C V6.1-011 on Digital UNIX V5.0 (Rev. 910) generates an unaligned access trap and prints 0x908. Here is the GCC instruction sequence: (gcc -O) addq a0, 0x2, a0 // a0=a0+2 (2=sizeof(short)) ldq_u v0, -2(a0) // v0=*((long *)(a0-2)) (won't trap) extqh v0, a0, v0 // v0=v0<<((64-8*a0)&0x3F) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Mar 8 15:31:35 2001 Delivered-To: freebsd-alpha@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 664) id 9F22837B718; Thu, 8 Mar 2001 15:31:32 -0800 (PST) Date: Thu, 8 Mar 2001 15:31:32 -0800 From: David O'Brien To: stable@freebsd.org, alpha@freebsd.org Subject: Re: 4.3-BETA available for FTP Message-ID: <20010308153132.A53932@hub.freebsd.org> Reply-To: obrien@freebsd.org References: <20010308005359P.jkh@osd.bsdi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010308005359P.jkh@osd.bsdi.com>; from jkh@osd.bsdi.com on Thu, Mar 08, 2001 at 12:53:59AM -0800 X-Operating-System: FreeBSD 4.2-STABLE Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, Mar 08, 2001 at 12:53:59AM -0800, Jordan Hubbard wrote: > I don't have a set of BETA bits for the Alpha yet but those will > follow shortly. ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/alpha/4.3-BETA-20010308 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Mar 8 15:34:25 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from winston.osd.bsdi.com (winston.osd.bsdi.com [204.216.27.229]) by hub.freebsd.org (Postfix) with ESMTP id 61FD737B719; Thu, 8 Mar 2001 15:34:22 -0800 (PST) (envelope-from jkh@osd.bsdi.com) Received: from localhost (jkh@localhost [127.0.0.1]) by winston.osd.bsdi.com (8.11.2/8.11.1) with ESMTP id f28NXVH32371; Thu, 8 Mar 2001 15:33:31 -0800 (PST) (envelope-from jkh@osd.bsdi.com) To: obrien@FreeBSD.ORG Cc: stable@FreeBSD.ORG, alpha@FreeBSD.ORG Subject: Re: 4.3-BETA available for FTP In-Reply-To: <20010308153132.A53932@hub.freebsd.org> References: <20010308005359P.jkh@osd.bsdi.com> <20010308153132.A53932@hub.freebsd.org> X-Mailer: Mew version 1.94.1 on Emacs 20.7 / Mule 4.0 (HANANOEN) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20010308153331M.jkh@osd.bsdi.com> Date: Thu, 08 Mar 2001 15:33:31 -0800 From: Jordan Hubbard X-Dispatcher: imput version 20000228(IM140) Lines: 5 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Please move it under releases so that its location is orthogonal with the x86 bits. 4.3-BETA is not a snapshot anyway. Thanks. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Mar 8 15:37: 8 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [209.152.133.57]) by hub.freebsd.org (Postfix) with ESMTP id 037B837B719; Thu, 8 Mar 2001 15:37:05 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.3/8.11.1) id f28Naxn88685; Thu, 8 Mar 2001 15:36:59 -0800 (PST) (envelope-from obrien) Date: Thu, 8 Mar 2001 15:36:58 -0800 From: "David O'Brien" To: Jordan Hubbard Cc: stable@FreeBSD.ORG, alpha@FreeBSD.ORG Subject: Re: 4.3-BETA available for FTP Message-ID: <20010308153658.A88605@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <20010308005359P.jkh@osd.bsdi.com> <20010308153132.A53932@hub.freebsd.org> <20010308153331M.jkh@osd.bsdi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010308153331M.jkh@osd.bsdi.com>; from jkh@osd.bsdi.com on Thu, Mar 08, 2001 at 03:33:31PM -0800 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, Mar 08, 2001 at 03:33:31PM -0800, Jordan Hubbard wrote: > Please move it under releases so that its location is orthogonal with > the x86 bits. 4.3-BETA is not a snapshot anyway. Thanks. done. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Mar 8 19:57: 7 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from smtp2.knology.net (user-24-214-63-12.knology.net [24.214.63.12]) by hub.freebsd.org (Postfix) with SMTP id 813BE37B718 for ; Thu, 8 Mar 2001 19:57:05 -0800 (PST) (envelope-from steve@havk.org) Received: (qmail 14255 invoked by uid 1003); 9 Mar 2001 03:59:22 -0000 Received: from user-24-214-88-8.knology.net (HELO bsd.havk.org) (24.214.88.8) by user-24-214-63-12.knology.net with SMTP; 9 Mar 2001 03:59:22 -0000 Received: by bsd.havk.org (Postfix, from userid 1001) id 434A11A7A8; Thu, 8 Mar 2001 21:56:55 -0600 (CST) Date: Thu, 8 Mar 2001 21:56:55 -0600 From: Steve Price To: will@freebsd.org, obrien@freebsd.org Cc: ports@freebsd.org Subject: qt22 port for Alpha Message-ID: <20010308215655.J46327@bsd.havk.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i X-Operating-System: FreeBSD 4.2-STABLE i386 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Any chance of getting this fixed for 4.3-RELEASE? http://havk.org/alpha/qt-2.2.4.log This appears to affect the build of 52 other ports on the Alpha and is a major show-stopper to getting kde-2.1 in this release. Thanks. -- Steve Price To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Mar 8 23:35:15 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id D2CDA37B718 for ; Thu, 8 Mar 2001 23:35:11 -0800 (PST) (envelope-from jhb@FreeBSD.org) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.2/8.11.2) with ESMTP id f297ZAA50473 for ; Thu, 8 Mar 2001 23:35:10 -0800 (PST) (envelope-from jhb@FreeBSD.org) 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 In-Reply-To: <200103090724.f297OIk50706@freefall.freebsd.org> Date: Thu, 08 Mar 2001 23:34:51 -0800 (PST) From: John Baldwin To: alpha@FreeBSD.org Subject: RE: cvs commit: src/sys/alpha/include mutex.h src/sys/i386/inclu Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 09-Mar-01 John Baldwin wrote: > jhb 2001/03/08 23:24:17 PST > > Modified files: > sys/alpha/include mutex.h > sys/i386/include mutex.h > sys/ia64/include mutex.h > sys/kern kern_mutex.c kern_fork.c > sys/sys proc.h > Log: > Fix mtx_legal2block. The only time that it is bad to block on a mutex is > if we hold a spin mutex, since we can trivially get into deadlocks if we > start switching out of processes that hold spinlocks. Checking to see if > interrupts were disabled was a sort of cheap way of doing this since most > of the time interrupts were only disabled when holding a spin lock. At > least on the i386. To fix this properly, use a per-process counter > p_spinlocks that counts the number of spin locks currently held, and > instead of checking to see if interrupts are disabled in the witness code, > check to see if we hold any spin locks. Since child processes always > start up with the sched lock magically held in fork_exit(), we initialize > p_spinlocks to 1 for child processes. Note that proc0 doesn't go through > fork_exit(), so it starts with no spin locks held. > > Consulting from: cp This is actually very good for the alpha, as the mtx_legal2block() that had been in alpha/include/mutex.h was bogus. Also, with this out of the way, any plans to disable interrupts via IPL for interrupt threads are now quite feasible, as well as for any other architectures which don't allow us to disable interrupts via PIC masks but only via the CPU. However, if we can selectively disable interrupts on PICs or other controllers and allow other interrutps to trigger while we continue to run in the kernel, we need to try and do that, as it greatly improves interrupt latency. This will become more apparent when Giant becomes more split up, as currently, almost all of the kernel effectively blocks interrupts by virtue of holding Giant. So, yes, Matt, you were right in that counting on being able to disable interrupts outside of the CPU is not valid, and it was not indeed part of the original SMPng design, but was something I had read in to a cheesy mtx_legal2block() that was valid on the i386. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - 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 9 0:43:32 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 310DE37B71A for ; Fri, 9 Mar 2001 00:43:29 -0800 (PST) (envelope-from mjacob@feral.com) Received: from beppo (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id AAA21120; Fri, 9 Mar 2001 00:43:21 -0800 Date: Fri, 9 Mar 2001 00:43:19 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Yoriaki FUJIMORI Cc: freebsd-alpha@freebsd.org, Jordan Hubbard Subject: realtime clock problem solved In-Reply-To: <200103051823.f25INdT38459@baron.fujimori.cache.waseda.ac.jp> 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, 5 Mar 2001, Yoriaki FUJIMORI wrote: > > As for a realtime clock problem, it should persist on many alphapc164, > pc164lx and up1100. At least in my lab, they all suffer from this. > It was a fun to see `Feb 29, 2000' on all of them. (;_;) > > I guess FreeBSD/Alpha alone makes use of mcclock.c. I could not find > its counterpart in FreeBSD/i386. > > Yoriaki Fujimori > I think I have a fix for this- it fixed my problem. The problem here is that the clock register was being written with a > 2 digit value. The below patch could be simpler in that just the update of the regs value should come after the rolloff to 2 digits. Could you try this for your machines? Jordan? If this pans out is this still possible to get into 4.3? Index: sys/dev/dec/mcclock.c =================================================================== RCS file: /home/ncvs/src/sys/dev/dec/mcclock.c,v retrieving revision 1.5 diff -u -r1.5 mcclock.c --- sys/dev/dec/mcclock.c 2000/01/04 03:22:04 1.5 +++ sys/dev/dec/mcclock.c 2001/03/09 08:39:19 @@ -84,10 +84,7 @@ ct->day = regs[MC_DOM]; ct->mon = regs[MC_MONTH]; ct->year = regs[MC_YEAR]; - /* - * This chip is not y2k compliant, so we'll do a 10 year window fix. - */ - if (ct->year >= 0 && ct->year < 10) { + if (ct->year < 70) { ct->year += 100; } } @@ -111,15 +108,7 @@ regs[MC_DOW] = ct->dow; regs[MC_DOM] = ct->day; regs[MC_MONTH] = ct->mon; - regs[MC_YEAR] = ct->year; - /* - * This chip is not y2k compliant, so we'll do a 10 year window fix. - * It's probably okay to write more than 100, but let's not and - * and say we didn't. - */ - if (ct->year >= 100) { - ct->year -= 100; - } + regs[MC_YEAR] = ct->year % 100; s = splclock(); MC146818_PUTTOD(dev, ®s); splx(s); To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Mar 9 1:45:14 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id 07E9137B719 for ; Fri, 9 Mar 2001 01:45:13 -0800 (PST) (envelope-from jhb@FreeBSD.org) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.2/8.11.2) with ESMTP id f299j1A53259; Fri, 9 Mar 2001 01:45:01 -0800 (PST) (envelope-from jhb@FreeBSD.org) 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 In-Reply-To: Date: Fri, 09 Mar 2001 01:44:43 -0800 (PST) From: John Baldwin To: Matthew Jacob Subject: RE: realtime clock problem solved Cc: Jordan Hubbard , freebsd-alpha@FreeBSD.org, Yoriaki FUJIMORI Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 09-Mar-01 Matthew Jacob wrote: > > I think I have a fix for this- it fixed my problem. The problem here is that > the clock register was being written with a > 2 digit value. The below patch > could be simpler in that just the update of the regs value should come after > the rolloff to 2 digits. > > Could you try this for your machines? > > Jordan? If this pans out is this still possible to get into 4.3? Do you think you could leave the comments in to explain why we are dinking with the year? :) -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - 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 9 4:30:43 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from mail.inka.de (quechua.inka.de [212.227.14.2]) by hub.freebsd.org (Postfix) with ESMTP id 5CD7937B719 for ; Fri, 9 Mar 2001 04:30:41 -0800 (PST) (envelope-from daemon@mips.inka.de) Received: from kemoauc.mips.inka.de (uucp@) by mail.inka.de with local-bsmtp id 14bM2a-0007mH-00; Fri, 9 Mar 2001 13:30:40 +0100 Received: (from daemon@localhost) by kemoauc.mips.inka.de (8.11.3/8.11.1) id f29Bgii00485 for freebsd-alpha@freebsd.org; Fri, 9 Mar 2001 12:42:44 +0100 (CET) (envelope-from daemon) From: naddy@mips.inka.de (Christian Weisgerber) Subject: Re: realtime clock problem solved Date: Fri, 9 Mar 2001 11:42:44 +0000 (UTC) Message-ID: <98afjk$dm$1@kemoauc.mips.inka.de> References: <200103051823.f25INdT38459@baron.fujimori.cache.waseda.ac.jp> Originator: naddy@mips.inka.de (Christian Weisgerber) To: freebsd-alpha@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Matthew Jacob wrote: > I think I have a fix for this- it fixed my problem. Works for my PC164. -- Christian "naddy" Weisgerber naddy@mips.inka.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Mar 9 9:34:59 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 0494237B719; Fri, 9 Mar 2001 09:34:57 -0800 (PST) (envelope-from mjacob@feral.com) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id JAA22645; Fri, 9 Mar 2001 09:34:54 -0800 Date: Fri, 9 Mar 2001 09:34:51 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: John Baldwin Cc: Jordan Hubbard , freebsd-alpha@FreeBSD.org, Yoriaki FUJIMORI Subject: RE: realtime clock problem solved 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 09-Mar-01 Matthew Jacob wrote: > > > > I think I have a fix for this- it fixed my problem. The problem here is that > > the clock register was being written with a > 2 digit value. The below patch > > could be simpler in that just the update of the regs value should come after > > the rolloff to 2 digits. > > > > Could you try this for your machines? > > > > Jordan? If this pans out is this still possible to get into 4.3? > > Do you think you could leave the comments in to explain why we are dinking with > the year? :) I suppose... don't you think it's important to leave things for future generations of programmers to puzzle over? Now that I think about it, the only mammal with a shorter generation time than programmers is the Black Norway rat.... *burp*.... but my mind wanders.... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Mar 9 10:57:31 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 5B52037B718; Fri, 9 Mar 2001 10:57:26 -0800 (PST) (envelope-from mjacob@feral.com) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id KAA23071; Fri, 9 Mar 2001 10:57:28 -0800 Date: Fri, 9 Mar 2001 10:57:25 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: John Baldwin Cc: alpha@FreeBSD.ORG Subject: RE: cvs commit: src/sys/alpha/include mutex.h src/sys/i386/inclu 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 Hey! Sounds good! Now I feel better at looking at an UltraSparc port.... (as if!) > > On 09-Mar-01 John Baldwin wrote: > > jhb 2001/03/08 23:24:17 PST > > > > Modified files: > > sys/alpha/include mutex.h > > sys/i386/include mutex.h > > sys/ia64/include mutex.h > > sys/kern kern_mutex.c kern_fork.c > > sys/sys proc.h > > Log: > > Fix mtx_legal2block. The only time that it is bad to block on a mutex is > > if we hold a spin mutex, since we can trivially get into deadlocks if we > > start switching out of processes that hold spinlocks. Checking to see if > > interrupts were disabled was a sort of cheap way of doing this since most > > of the time interrupts were only disabled when holding a spin lock. At > > least on the i386. To fix this properly, use a per-process counter > > p_spinlocks that counts the number of spin locks currently held, and > > instead of checking to see if interrupts are disabled in the witness code, > > check to see if we hold any spin locks. Since child processes always > > start up with the sched lock magically held in fork_exit(), we initialize > > p_spinlocks to 1 for child processes. Note that proc0 doesn't go through > > fork_exit(), so it starts with no spin locks held. > > > > Consulting from: cp > > This is actually very good for the alpha, as the mtx_legal2block() that had > been in alpha/include/mutex.h was bogus. Also, with this out of the way, any > plans to disable interrupts via IPL for interrupt threads are now quite > feasible, as well as for any other architectures which don't allow us to disable > interrupts via PIC masks but only via the CPU. However, if we can selectively > disable interrupts on PICs or other controllers and allow other interrutps to > trigger while we continue to run in the kernel, we need to try and do that, as > it greatly improves interrupt latency. This will become more apparent when > Giant becomes more split up, as currently, almost all of the kernel effectively > blocks interrupts by virtue of holding Giant. > > So, yes, Matt, you were right in that counting on being able to disable > interrupts outside of the CPU is not valid, and it was not indeed part of the > original SMPng design, but was something I had read in to a cheesy > mtx_legal2block() that was valid on the i386. > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Mar 9 12:42: 5 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from smtp02.primenet.com (smtp02.primenet.com [206.165.6.132]) by hub.freebsd.org (Postfix) with ESMTP id DB05637B719; Fri, 9 Mar 2001 12:42:00 -0800 (PST) (envelope-from tlambert@usr05.primenet.com) Received: (from daemon@localhost) by smtp02.primenet.com (8.9.3/8.9.3) id NAA28685; Fri, 9 Mar 2001 13:35:23 -0700 (MST) Received: from usr05.primenet.com(206.165.6.205) via SMTP by smtp02.primenet.com, id smtpdAAAjWaG53; Fri Mar 9 13:35:14 2001 Received: (from tlambert@localhost) by usr05.primenet.com (8.8.5/8.8.5) id NAA03449; Fri, 9 Mar 2001 13:41:44 -0700 (MST) From: Terry Lambert Message-Id: <200103092041.NAA03449@usr05.primenet.com> Subject: Re: realtime clock problem solved To: mjacob@feral.com Date: Fri, 9 Mar 2001 20:41:43 +0000 (GMT) Cc: jhb@FreeBSD.ORG (John Baldwin), jkh@bsdi.com (Jordan Hubbard), freebsd-alpha@FreeBSD.ORG, fujimori@baron.fujimori.cache.waseda.ac.jp (Yoriaki FUJIMORI) In-Reply-To: from "Matthew Jacob" at Mar 09, 2001 09:34:51 AM X-Mailer: ELM [version 2.5 PL2] 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 > > Do you think you could leave the comments in to explain why we are > > dinking with the year? :) > > I suppose... don't you think it's important to leave things for future > generations of programmers to puzzle over? Now that I think about it, the only > mammal with a shorter generation time than programmers is the Black Norway > rat.... *burp*.... but my mind wanders.... Rattus Norwegicus. What about Rattus Rattus? Leaving documentation is much better than leaving a mystery; consider BSD drivers derived from information in Linux drivers... Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sat Mar 10 0:29:35 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from grafin.fujimori.cache.waseda.ac.jp (grafin.fujimori.cache.waseda.ac.jp [133.9.152.154]) by hub.freebsd.org (Postfix) with ESMTP id AB6CA37B71B for ; Sat, 10 Mar 2001 00:29:33 -0800 (PST) (envelope-from fujimori@grafin.fujimori.cache.waseda.ac.jp) Received: from grafin.fujimori.cache.waseda.ac.jp (fujimori@localhost [127.0.0.1]) by grafin.fujimori.cache.waseda.ac.jp (8.9.3/3.7W) with ESMTP id RAA05591; Sat, 10 Mar 2001 17:29:25 +0900 Message-Id: <200103100829.RAA05591@grafin.fujimori.cache.waseda.ac.jp> To: mjacob@feral.com Cc: freebsd-alpha@freebsd.org Subject: Re: realtime clock problem solved In-reply-to: Your message of "Fri, 09 Mar 2001 00:43:19 PST." Date: Sat, 10 Mar 2001 17:29:25 +0000 From: Yoriaki FUJIMORI Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I tested your patch on pc164lx, alphapc164 and up1100. I think your patch fixed the realtime clock problem. Best wishes, Yoriaki Fujimori To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sat Mar 10 2:34:27 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 8808D37B718 for ; Sat, 10 Mar 2001 02:34:25 -0800 (PST) (envelope-from mjacob@feral.com) Received: from beppo (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id CAA25623; Sat, 10 Mar 2001 02:34:25 -0800 Date: Sat, 10 Mar 2001 02:34:22 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Yoriaki FUJIMORI Cc: freebsd-alpha@freebsd.org Subject: Re: realtime clock problem solved In-Reply-To: <200103100829.RAA05591@grafin.fujimori.cache.waseda.ac.jp> 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 'kay, thanks! On Sat, 10 Mar 2001, Yoriaki FUJIMORI wrote: > > I tested your patch on pc164lx, alphapc164 and up1100. > I think your patch fixed the realtime clock problem. > > Best wishes, > Yoriaki Fujimori > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sat Mar 10 16: 5:26 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 4F2E837B738 for ; Sat, 10 Mar 2001 16:05:22 -0800 (PST) (envelope-from mjacob@feral.com) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id QAA28135 for ; Sat, 10 Mar 2001 16:05:24 -0800 Date: Sat, 10 Mar 2001 16:05:21 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: alpha@FreeBSD.ORG Subject: Re: Entropy harvesting? Grim reaper is more like it... (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 Moved to alpha where this belongs... ---------- Forwarded message ---------- Date: Sat, 10 Mar 2001 16:05:04 -0800 (PST) From: Matthew Jacob To: David O'Brien Cc: current@FreeBSD.org Subject: Re: Entropy harvesting? Grim reaper is more like it... > On Fri, Mar 09, 2001 at 01:39:58PM -0800, Matthew Jacob wrote: > > > Erm, just so you know. The 4100 here at WC doesn't even make it past > > > the SCSI probe due to interrupt issues. > > > > Hmm. Well, it *was* working a couple of days ago :-).... > > Uh, actually _your_ 4100 is the only I've ever known to work on > post-SMPng. The WC 4100 has *never* worked on post SMPng. I don't > believe I've heard that DFR's runs SMPng either. That's strange. After each time I've gotten this working again (and it now works on the 4100 here *AND* the ones at NASA/Ames) I've sent mail saying "Try yours again" to you! I thougt you *were* working again. > I guess I should get a `dd' of your system disk, or get you a console on > the WC box. Well, since I have *two* working systems- one of which is a four hose configuration, I don't know quite what to say... :-).... I should just bring one of my disks by..... urrmm.. Actually, one system has a DDS tape drive so I'll dd you a root disk image- it'll be da2 so you'll have to shove disks ahead of it or DTRT. -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sat Mar 10 17: 5: 7 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [209.152.133.57]) by hub.freebsd.org (Postfix) with ESMTP id A035B37B718 for ; Sat, 10 Mar 2001 17:05:05 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.3/8.11.1) id f2B153l52380; Sat, 10 Mar 2001 17:05:03 -0800 (PST) (envelope-from obrien) Date: Sat, 10 Mar 2001 17:05:02 -0800 From: "David O'Brien" To: "Philippe O. Pouliquen" Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: Strange results from compiled alpha code Message-ID: <20010310170502.B36413@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <200103082050.PAA0000024187@alpha.ece.jhu.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200103082050.PAA0000024187@alpha.ece.jhu.edu>; from philippe@alpha.ece.jhu.edu on Thu, Mar 08, 2001 at 03:50:29PM -0500 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, Mar 08, 2001 at 03:50:29PM -0500, Philippe O. Pouliquen wrote: > I've had an e-mail exchange with Ray Newman, and have investigated the > problem further. Any reason you have not posted this to the GCC list for discussion? That is the only place where you might could get GCC to do the desired thing. -- -- David (obrien@FreeBSD.org) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sat Mar 10 18:39:49 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from netau1.alcanet.com.au (ntp.alcanet.com.au [203.62.196.27]) by hub.freebsd.org (Postfix) with ESMTP id 357BF37B71A for ; Sat, 10 Mar 2001 18:39:45 -0800 (PST) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: from mfg1.cim.alcatel.com.au (mfg1.cim.alcatel.com.au [139.188.23.1]) by netau1.alcanet.com.au (8.9.3 (PHNE_22672)/8.9.3) with ESMTP id NAA02602 for ; Sun, 11 Mar 2001 13:39:41 +1100 (EDT) Received: from gsmx07.alcatel.com.au by cim.alcatel.com.au (PMDF V5.2-32 #37640) with ESMTP id <01K12MAJ890WOZ59LT@cim.alcatel.com.au> for freebsd-alpha@FreeBSD.ORG; Sun, 11 Mar 2001 13:39:41 +1100 Received: (from jeremyp@localhost) by gsmx07.alcatel.com.au (8.11.1/8.11.1) id f2B2deE27385 for freebsd-alpha@FreeBSD.ORG; Sun, 11 Mar 2001 13:39:40 +1100 (EST envelope-from jeremyp) Content-return: prohibited Date: Sun, 11 Mar 2001 13:39:39 +1100 From: Peter Jeremy Subject: Re: ppp core-dumping in kernel space? In-reply-to: <20010219074428.E70642@gsmx07.alcatel.com.au>; from peter.jeremy@alcatel.com.au on Mon, Feb 19, 2001 at 07:44:28AM +1100 To: freebsd-alpha@FreeBSD.ORG Mail-Followup-To: freebsd-alpha@FreeBSD.ORG Message-id: <20010311133939.A26976@gsmx07.alcatel.com.au> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-disposition: inline User-Agent: Mutt/1.2.5i References: <20010219074428.E70642@gsmx07.alcatel.com.au> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 2001-Feb-19 07:44:28 +1100, Peter Jeremy wrote: >I'm running -current from 8th February on a Multia and ppp is regularly >core-dumping (sigmentation violation). The core dump contents seem >consistent from the couple of different core's that I've studied. I've done some more studying. The problem is inside the sigreturn trampoline (hence the ra on the stack). The trampoline does a "jsr ra,(t12)" to invoke the user signal handler. My problem is that somehow t12 is the kernel witness_exit() function, rather than the user signal handler. (And before I had WITNESS enabled, t12 was _mtx_exit()). A kernel address is obviously invalid in usermode, so a further SIGSEGV is delivered. I notice that code in both locore.s and machdep.c includes comments implying that the handler is in a3, rather than t12, but the actual code in machdep,c has used t12 ever since dfr imported in in June 1998. In both core files I've checked, the kernel was in the process of delivering a SIGALRM. Since gcc seems to always compile function calls[1] as ldq t12,...(gp) jsr ra,(t12) this suggests that there is a window between when the user registers are restored and the actual retsys during which t12 (at least) can get clobbered. I've occasionally seen odd behaviour in other processes which seems consistent with this behaviour. Has anyone else seen this? Is this likely to have been fixed by jhb's recent locking fixes? [1] Can anyone explain the rational behind this? bsr should be preferable since the CPU can begin the instruction prefetch much earlier. Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message