From owner-freebsd-alpha Sun Feb 11 6:28:28 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from radicalmedia.com (radicalmedia.com [204.254.246.2]) by hub.freebsd.org (Postfix) with ESMTP id B30C437B503 for ; Sun, 11 Feb 2001 06:28:26 -0800 (PST) Received: (from phiber@localhost) by radicalmedia.com (8.9.3/8.9.3) id JAA10450 for alpha@freebsd.org; Sun, 11 Feb 2001 09:28:21 -0500 Date: Sun, 11 Feb 2001 09:28:21 -0500 From: Mark Abene To: alpha@freebsd.org Subject: symbios card... Message-ID: <20010211092821.F1040@mail.radicalmedia.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/1.0.1i Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Would anyone care to comment on whether the Symbios 53C825 (NOT 825A) is supported by FreeBSD? I saw mention of the 825A in the hardware list, but not a plain 825. Thanks, -Mark To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sun Feb 11 8:47:46 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from front9.grolier.fr (front9.grolier.fr [194.158.96.59]) by hub.freebsd.org (Postfix) with ESMTP id 9AFDB37B401 for ; Sun, 11 Feb 2001 08:47:43 -0800 (PST) Received: from nas2-219.mea.club-internet.fr (nas2-219.mea.club-internet.fr [195.36.200.219]) by front9.grolier.fr (8.9.3/No_Relay+No_Spam_MGC990224) with ESMTP id RAA07937; Sun, 11 Feb 2001 17:47:34 +0100 (MET) Date: Sun, 11 Feb 2001 16:46:34 +0100 (CET) From: =?ISO-8859-1?Q?G=E9rard_Roudier?= X-Sender: groudier@linux.local To: Mark Abene Cc: alpha@FreeBSD.ORG Subject: Re: symbios card... In-Reply-To: <20010211092821.F1040@mail.radicalmedia.com> 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 Sun, 11 Feb 2001, Mark Abene wrote: > Would anyone care to comment on whether the Symbios 53C825 (NOT 825A) is > supported by FreeBSD? I saw mention of the 825A in the hardware list, bu= t > not a plain 825. The NCR53C825 is supported by FreeBSD since at least 6 years. :) (Was a NCR product at this time) Anyway, the hardware list needs to be updated for newer chips (i.e. I should have updated it). At the moment and at least for RELENG4: - The SYM driver supports all 53C8XX A and not-A chips and also the 53C1010-33, 53C1010-66, 53C1010R, 53C1000 and 53C1000R Ultra3 controllers. - The NCR driver supports all 53C8XX A and not-A chips, may-be excepted=20 the 53C875A. (Adding the 53C875A chip description will make it support the chip). For Ultra3 controllers under RELENG3, I would suggest to use an updated SYM driver, as the sym-2.1.6 available from http://people.freebsd.org/~groudier/ G=E9rard. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sun Feb 11 8:57:28 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from radicalmedia.com (radicalmedia.com [204.254.246.2]) by hub.freebsd.org (Postfix) with ESMTP id 0779137B401 for ; Sun, 11 Feb 2001 08:57:26 -0800 (PST) Received: (from phiber@localhost) by radicalmedia.com (8.9.3/8.9.3) id LAA10988; Sun, 11 Feb 2001 11:57:23 -0500 Date: Sun, 11 Feb 2001 11:57:23 -0500 From: Mark Abene To: =?iso-8859-1?Q?G=E9rard_Roudier?= Cc: alpha@FreeBSD.ORG Subject: Re: symbios card... Message-ID: <20010211115723.G1040@mail.radicalmedia.com> References: <20010211092821.F1040@mail.radicalmedia.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.0.1i In-Reply-To: ; from groudier@club-internet.fr on Sun, Feb 11, 2001 at 04:46:34PM +0100 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Thanks! What are the pros/cons of using the newer sym driver versus the older ncr driver? Which would you recommend with a 53C825? Does it matter? Cheers, -Mark On Sun, Feb 11, 2001 at 04:46:34PM +0100, Gérard Roudier wrote: > > On Sun, 11 Feb 2001, Mark Abene wrote: > > > Would anyone care to comment on whether the Symbios 53C825 (NOT 825A) is > > supported by FreeBSD? I saw mention of the 825A in the hardware list, but > > not a plain 825. > > The NCR53C825 is supported by FreeBSD since at least 6 years. :) > (Was a NCR product at this time) > > Anyway, the hardware list needs to be updated for newer chips (i.e. I > should have updated it). > > At the moment and at least for RELENG4: > > - The SYM driver supports all 53C8XX A and not-A chips and also the > 53C1010-33, 53C1010-66, 53C1010R, 53C1000 and 53C1000R > Ultra3 controllers. > > - The NCR driver supports all 53C8XX A and not-A chips, may-be excepted > the 53C875A. > (Adding the 53C875A chip description will make it support the chip). > > For Ultra3 controllers under RELENG3, I would suggest to use an updated > SYM driver, as the sym-2.1.6 available from > http://people.freebsd.org/~groudier/ > > Gérard. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sun Feb 11 9:48:36 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 A7E3037B401 for ; Sun, 11 Feb 2001 09:48:33 -0800 (PST) Received: from [212.238.54.101] (helo=freebie.demon.nl) by post.mail.nl.demon.net with smtp (Exim 3.14 #2) id 14S0bv-0007HB-00; Sun, 11 Feb 2001 17:48:31 +0000 Received: (from wkb@localhost) by freebie.demon.nl (8.11.1/8.11.1) id f1BHp8320042; Sun, 11 Feb 2001 18:51:08 +0100 (CET) (envelope-from wkb) Date: Sun, 11 Feb 2001 18:51:08 +0100 From: Wilko Bulte To: =?iso-8859-1?Q?G=E9rard_Roudier?= Cc: Mark Abene , alpha@freebsd.org Subject: Re: symbios card... Message-ID: <20010211185108.A20022@freebie.demon.nl> References: <20010211092821.F1040@mail.radicalmedia.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from groudier@club-internet.fr on Sun, Feb 11, 2001 at 04:46:34PM +0100 X-OS: FreeBSD 4.2-STABLE X-PGP: finger wilko@freebsd.org Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by freebie.demon.nl id f1BHp8320042 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sun, Feb 11, 2001 at 04:46:34PM +0100, G=E9rard Roudier wrote: >=20 > On Sun, 11 Feb 2001, Mark Abene wrote: >=20 > > Would anyone care to comment on whether the Symbios 53C825 (NOT 825A)= is > > supported by FreeBSD? I saw mention of the 825A in the hardware list= , but > > not a plain 825. >=20 > The NCR53C825 is supported by FreeBSD since at least 6 years. :) > (Was a NCR product at this time) >=20 > Anyway, the hardware list needs to be updated for newer chips (i.e. I > should have updated it). Gerard,=20 I think (as this was asked on -alpha) that the question is mainly aimed at what the alpha SRM console code will recognise (??). W/ --=20 | / 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 Feb 11 11:11: 2 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from front1m.grolier.fr (front1m.grolier.fr [195.36.216.51]) by hub.freebsd.org (Postfix) with ESMTP id 6669B37B401 for ; Sun, 11 Feb 2001 11:10:58 -0800 (PST) Received: from nas1-227.cgy.club-internet.fr (nas1-227.cgy.club-internet.fr [195.36.197.227]) by front1m.grolier.fr (8.9.3/No_Relay+No_Spam_MGC990224) with ESMTP id UAA25789; Sun, 11 Feb 2001 20:10:52 +0100 (MET) Date: Sun, 11 Feb 2001 19:09:53 +0100 (CET) From: =?ISO-8859-1?Q?G=E9rard_Roudier?= X-Sender: groudier@linux.local To: Mark Abene Cc: alpha@FreeBSD.ORG Subject: Re: symbios card... In-Reply-To: <20010211115723.G1040@mail.radicalmedia.com> 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 Sun, 11 Feb 2001, Mark Abene wrote: > Thanks! What are the pros/cons of using the newer sym driver versus the > older ncr driver? Which would you recommend with a 53C825? Does it matt= er? For a 53C825 I would simply suggest to use a driver that works for you. :) But I would prefer SYM to be tried first. I have currently a portable beta driver based on SYM (and named SYM-2) and this will be lot of time spare for me to have a single driver to maintain rather that four (2 Under FreeBSD and 2 under Linux) or even more. My testing did show that SYM has less latency than NCR for small IOs using a 53C810 (non-A) and a 53C895. For the 895 I tried both the NCR-generic SCRIPTS and the LOAD/STORE based SCRIPTS. But the difference should not be significant for real work performed with a 825, IMO. For chips that support hardware phase mismatch (896 and later chips), the SYM handles the context from SCRIPTS and ensures that no more than 1 interrupt per IO will be delivered to the CPU and that the SCSI SCRIPTS=20 never stalls waiting for CPU intervention (excepted on error recovery). Also SYM does not scan lists either from CPU or SCRIPTS processor and uses= =20 a completion queue to interface with the C code. This makes it full scalable regarding the number of outstanding IOs. In other words, SYM runs O(1) in normal situations (i.e. excepted for error recovery). SYM is currently configured for 448 outstanding IOs per initiator, but is= =20 in fact not so limited. I just wanted not to allocate more than 1 page at a time for the start and completion queues that use 8 bytes per entry. And allocating the queues contiguously is simple. Btw, the queues could=20 be allocated in several chunks but the additionnal complexity is not=20 yet worthwhile. (Btw, with 8K pages, a simple define change will increase the queue size to 1022 entries, without any other software changes) G=E9rard. > Cheers, > -Mark >=20 > On Sun, Feb 11, 2001 at 04:46:34PM +0100, G=E9rard Roudier wrote: > >=20 > > On Sun, 11 Feb 2001, Mark Abene wrote: > >=20 > > > Would anyone care to comment on whether the Symbios 53C825 (NOT 825A)= is > > > supported by FreeBSD? I saw mention of the 825A in the hardware list= , but > > > not a plain 825. > >=20 > > The NCR53C825 is supported by FreeBSD since at least 6 years. :) > > (Was a NCR product at this time) > >=20 > > Anyway, the hardware list needs to be updated for newer chips (i.e. I > > should have updated it). > >=20 > > At the moment and at least for RELENG4: > >=20 > > - The SYM driver supports all 53C8XX A and not-A chips and also the > > 53C1010-33, 53C1010-66, 53C1010R, 53C1000 and 53C1000R > > Ultra3 controllers. > >=20 > > - The NCR driver supports all 53C8XX A and not-A chips, may-be excepted= =20 > > the 53C875A. > > (Adding the 53C875A chip description will make it support the chip). > >=20 > > For Ultra3 controllers under RELENG3, I would suggest to use an updated > > SYM driver, as the sym-2.1.6 available from > > http://people.freebsd.org/~groudier/ > >=20 > > G=E9rard. >=20 >=20 > 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 Sun Feb 11 13:25: 8 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from front9.grolier.fr (front9.grolier.fr [194.158.96.59]) by hub.freebsd.org (Postfix) with ESMTP id 8EB9737B401 for ; Sun, 11 Feb 2001 13:25:05 -0800 (PST) Received: from nas2-61.mea.club-internet.fr (nas2-61.mea.club-internet.fr [195.36.200.61]) by front9.grolier.fr (8.9.3/No_Relay+No_Spam_MGC990224) with ESMTP id WAA04622; Sun, 11 Feb 2001 22:25:00 +0100 (MET) Date: Sun, 11 Feb 2001 21:24:01 +0100 (CET) From: =?ISO-8859-1?Q?G=E9rard_Roudier?= X-Sender: groudier@linux.local To: Wilko Bulte Cc: Mark Abene , alpha@freebsd.org Subject: Re: symbios card... In-Reply-To: <20010211185108.A20022@freebie.demon.nl> 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 Sun, 11 Feb 2001, Wilko Bulte wrote: > On Sun, Feb 11, 2001 at 04:46:34PM +0100, G=E9rard Roudier wrote: > >=20 > > On Sun, 11 Feb 2001, Mark Abene wrote: > >=20 > > > Would anyone care to comment on whether the Symbios 53C825 (NOT 825A)= is > > > supported by FreeBSD? I saw mention of the 825A in the hardware list= , but > > > not a plain 825. > >=20 > > The NCR53C825 is supported by FreeBSD since at least 6 years. :) > > (Was a NCR product at this time) > >=20 > > Anyway, the hardware list needs to be updated for newer chips (i.e. I > > should have updated it). >=20 > Gerard,=20 >=20 > I think (as this was asked on -alpha) that the question is mainly aimed > at what the alpha SRM console code will recognise (??). May-be. But I donnot think so. (Or Mark didn't read alpha/HARDWARE.TXT). The 53C825A was mentionned in src/release/texts/HARDWARE.TXT but not the plain 53C825. Btw, the 53C820 was mentionned but I removed it. The 53C820 should be so rare, that the 6 bytes to name it can be spared, IMO. And this gave me the opportunity to speak about newer Symbios chips and their support by FreeBSD at the alpha list. :) G=E9rard. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sun Feb 11 13:28:35 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from peorth.iteration.net (peorth.iteration.net [208.190.180.178]) by hub.freebsd.org (Postfix) with ESMTP id BE12837B401 for ; Sun, 11 Feb 2001 13:28:32 -0800 (PST) Received: by peorth.iteration.net (Postfix, from userid 1001) id 96BA857650; Sun, 11 Feb 2001 15:28:35 -0600 (CST) Date: Sun, 11 Feb 2001 15:28:35 -0600 From: "Michael C . Wu" To: =?big5?Q?G=E9rard_Roudier?= Cc: Mark Abene , alpha@FreeBSD.ORG Subject: Re: symbios card... Message-ID: <20010211152835.C19845@peorth.iteration.net> Reply-To: "Michael C . Wu" References: <20010211092821.F1040@mail.radicalmedia.com> Mime-Version: 1.0 Content-Type: text/plain; charset=big5 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.2.5i In-Reply-To: ; from groudier@club-internet.fr on Sun, Feb 11, 2001 at 04:46:34PM +0100 X-PGP-Fingerprint: 5025 F691 F943 8128 48A8 5025 77CE 29C5 8FA1 2E20 X-PGP-Key-ID: 0x8FA12E20 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sun, Feb 11, 2001 at 04:46:34PM +0100, Gérard Roudier scribbled: | On Sun, 11 Feb 2001, Mark Abene wrote: | > Would anyone care to comment on whether the Symbios 53C825 (NOT 825A) is | > supported by FreeBSD? I saw mention of the 825A in the hardware list, but | SYM driver, as the sym-2.1.6 available from | http://people.freebsd.org/~groudier/ I have been using the SYM U160 driver on both Alpha and i386 with no problem. (And many people agree with me on that sym driver/chipset >> Adaptec * However, is there a reason why the driver is different from the one in the base system? i.e. Why do you keep two copies of the driver? :) -- +------------------------------------------------------------------+ | keichii@peorth.iteration.net | keichii@bsdconspiracy.net | | http://peorth.iteration.net/~keichii | Yes, BSD is a conspiracy. | +------------------------------------------------------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sun Feb 11 16:28:29 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from cr66388-a.rchrd1.on.wave.home.com (cr66388-a.rchrd1.on.wave.home.com [24.114.165.24]) by hub.freebsd.org (Postfix) with ESMTP id 1762337B401 for ; Sun, 11 Feb 2001 16:28:26 -0800 (PST) Received: from cr66388-a.rchrd1.on.wave.home.c (localhost [127.0.0.1]) by cr66388-a.rchrd1.on.wave.home.com (Postfix) with ESMTP id 84796BABD for ; Sun, 11 Feb 2001 19:28:20 -0500 (EST) X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.3 To: freebsd-alpha@freebsd.org Subject: HEADS UP Re: cvs commit: src/sys/alpha/alpha trap.c src/sys/dev/acpica/Osd OsdSchedule.c src/sys/i386/i386 genassym.c swtch.s trap.c src/sys/ia64/ia64 trap.c src/sys/kern init_main.c kern_condvar.c kern_idle.c kern_intr.c kern_mib.c kern_mutex.c kern_proc.c ... In-Reply-To: Message from Jake Burkholder of "Sun, 11 Feb 2001 16:20:08 PST." <200102120020.f1C0K8N72721@freefall.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 11 Feb 2001 19:28:20 -0500 From: Jake Burkholder Message-Id: <20010212002820.84796BABD@cr66388-a.rchrd1.on.wave.home.com> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > jake 2001/02/11 16:20:08 PST > > Modified files: > sys/alpha/alpha trap.c > sys/dev/acpica/Osd OsdSchedule.c > sys/i386/i386 genassym.c swtch.s trap.c > sys/ia64/ia64 trap.c > sys/kern init_main.c kern_condvar.c kern_idle.c > kern_intr.c kern_mib.c kern_mutex.c > kern_proc.c kern_resource.c kern_sig.c > kern_subr.c kern_switch.c kern_synch.c > sys/posix4 ksched.c > sys/sys ktr.h param.h proc.h rtprio.h systm.h > tty.h user.h > sys/ufs/ffs ffs_snapshot.c > sys/vm vm_glue.c vm_meter.c > Added files: > sys/sys priority.h runq.h > Log: > Implement a unified run queue and adjust priority levels accordingly. I made sure that this compiles for the alpha. One problem is that propogate_priority() uses the p_oncpu field of struct proc, which isn't set by alpha's cpu_switch(). I don't know enough alpha asm to do it or I would have. This shouldn't be that a big of a deal for UP at least. What needs to happen is that when switching out of a process, the p_oncpu field should be set to 0xff, and the p_oncpu field of the new process should be set to the cpuid of the new cpu (always zero for UP). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sun Feb 11 16:31: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 5967037B401 for ; Sun, 11 Feb 2001 16:31:24 -0800 (PST) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id QAA00133; Sun, 11 Feb 2001 16:31:25 -0800 Date: Sun, 11 Feb 2001 16:31:22 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Jake Burkholder Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: HEADS UP Re: cvs commit: src/sys/alpha/alpha trap.c src/sys/dev/acpica/Osd OsdSchedule.c src/sys/i386/i386 genassym.c swtch.s trap.c src/sys/ia64/ia64 trap.c src/sys/kern init_main.c kern_condvar.c kern_idle.c kern_intr.c kern_mib.c kern_mutex.c kern_proc.c ... In-Reply-To: <20010212002820.84796BABD@cr66388-a.rchrd1.on.wave.home.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 > > jake 2001/02/11 16:20:08 PST > > > > Modified files: > > sys/alpha/alpha trap.c > > sys/dev/acpica/Osd OsdSchedule.c > > sys/i386/i386 genassym.c swtch.s trap.c > > sys/ia64/ia64 trap.c > > sys/kern init_main.c kern_condvar.c kern_idle.c > > kern_intr.c kern_mib.c kern_mutex.c > > kern_proc.c kern_resource.c kern_sig.c > > kern_subr.c kern_switch.c kern_synch.c > > sys/posix4 ksched.c > > sys/sys ktr.h param.h proc.h rtprio.h systm.h > > tty.h user.h > > sys/ufs/ffs ffs_snapshot.c > > sys/vm vm_glue.c vm_meter.c > > Added files: > > sys/sys priority.h runq.h > > Log: > > Implement a unified run queue and adjust priority levels accordingly. > > I made sure that this compiles for the alpha. One problem is that > propogate_priority() uses the p_oncpu field of struct proc, which > isn't set by alpha's cpu_switch(). I don't know enough alpha asm > to do it or I would have. This shouldn't be that a big of a deal > for UP at least. > > What needs to happen is that when switching out of a process, the > p_oncpu field should be set to 0xff, and the p_oncpu field of the > new process should be set to the cpuid of the new cpu (always > zero for UP). 'kay- thanks.. one of us will field this. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Feb 12 9:52:31 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from www.kjkoster.org (a213-84-15-12.adsl.xs4all.nl [213.84.15.12]) by hub.freebsd.org (Postfix) with ESMTP id 5F11637B503 for ; Mon, 12 Feb 2001 09:52:26 -0800 (PST) Received: from kjkoster.org (LikeEver [192.168.0.1]) by www.kjkoster.org (8.11.2/8.11.0) with ESMTP id f1CHqTI16077 for ; Mon, 12 Feb 2001 18:52:30 +0100 (CET) (envelope-from kjkoster@kjkoster.org) Message-ID: <3A8822DE.CB44223B@kjkoster.org> Date: Mon, 12 Feb 2001 18:52:30 +0100 From: Kees Jan Koster X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 4.2-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-alpha@freebsd.org Subject: /usr/obj required space Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Dear All, I'm trying to get my little Alpha to build the world. Due to my disks dying of old age I have only limited diskspace left, so I mounted 500Mb on /usr/obj for the buildworld. Alas, too small. This seems funny, since on my x86 box the same tree is only ~330Mb in size. How come Alpha needs 200Mb more? How much space do I need? Yours, Kees Jan ---------------------------------------------------------- Kees Jan Koster e-mail: kjkoster "at" kjkoster.org www: http://www.kjkoster.org/ ---------------------------------------------------------- Piglet: You're invited too! Eeyore: Hmpf, that must be a mistake. I'll go, but don't blame me if it rains. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Feb 12 10: 6: 1 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 02DE337B491 for ; Mon, 12 Feb 2001 10:05:58 -0800 (PST) Received: from [212.238.54.101] (helo=freebie.demon.nl) by post.mail.nl.demon.net with smtp (Exim 3.14 #2) id 14SNMK-0007Xw-00; Mon, 12 Feb 2001 18:05:56 +0000 Received: (from wkb@localhost) by freebie.demon.nl (8.11.1/8.11.1) id f1CI8c307894; Mon, 12 Feb 2001 19:08:38 +0100 (CET) (envelope-from wkb) Date: Mon, 12 Feb 2001 19:08:38 +0100 From: Wilko Bulte To: Kees Jan Koster Cc: freebsd-alpha@freebsd.org Subject: Re: /usr/obj required space Message-ID: <20010212190838.A7251@freebie.demon.nl> References: <3A8822DE.CB44223B@kjkoster.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <3A8822DE.CB44223B@kjkoster.org>; from kjkoster@kjkoster.org on Mon, Feb 12, 2001 at 06:52:30PM +0100 X-OS: FreeBSD 4.2-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, Feb 12, 2001 at 06:52:30PM +0100, Kees Jan Koster wrote: mx5#du -ks * 768419 usr Yesterday's -current on a Miata > Dear All, > > I'm trying to get my little Alpha to build the world. Due to my > disks dying of old age I have only limited diskspace left, so I > mounted 500Mb on /usr/obj for the buildworld. Alas, too small. > > This seems funny, since on my x86 box the same tree is only > ~330Mb in size. How come Alpha needs 200Mb more? > > How much space do I need? > > Yours, > Kees Jan > > ---------------------------------------------------------- > Kees Jan Koster e-mail: kjkoster "at" kjkoster.org > www: http://www.kjkoster.org/ > ---------------------------------------------------------- > Piglet: You're invited too! > Eeyore: Hmpf, that must be a mistake. I'll go, but don't > blame me if it rains. > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-alpha" in the body of the message ---end of quoted text--- -- | / 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 Mon Feb 12 10: 8: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 4B88637B491 for ; Mon, 12 Feb 2001 10:08:55 -0800 (PST) Received: from [212.238.54.101] (helo=freebie.demon.nl) by post.mail.nl.demon.net with smtp (Exim 3.14 #2) id 14SNPB-0007dX-00; Mon, 12 Feb 2001 18:08:53 +0000 Received: (from wkb@localhost) by freebie.demon.nl (8.11.1/8.11.1) id f1CIBZj12072; Mon, 12 Feb 2001 19:11:35 +0100 (CET) (envelope-from wkb) Date: Mon, 12 Feb 2001 19:11:35 +0100 From: Wilko Bulte To: Kees Jan Koster Cc: freebsd-alpha@freebsd.org Subject: Re: /usr/obj required space Message-ID: <20010212191135.A11096@freebie.demon.nl> References: <3A8822DE.CB44223B@kjkoster.org> <20010212190838.A7251@freebie.demon.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20010212190838.A7251@freebie.demon.nl>; from wkb@freebie.demon.nl on Mon, Feb 12, 2001 at 07:08:38PM +0100 X-OS: FreeBSD 4.2-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, Feb 12, 2001 at 07:08:38PM +0100, Wilko Bulte wrote: > On Mon, Feb 12, 2001 at 06:52:30PM +0100, Kees Jan Koster wrote: Where 'pwd' is /usr/obj of course, sorry for the confusion. > > mx5#du -ks * > 768419 usr > > Yesterday's -current on a Miata > > > Dear All, > > > > I'm trying to get my little Alpha to build the world. Due to my > > disks dying of old age I have only limited diskspace left, so I > > mounted 500Mb on /usr/obj for the buildworld. Alas, too small. > > > > This seems funny, since on my x86 box the same tree is only > > ~330Mb in size. How come Alpha needs 200Mb more? > > > > How much space do I need? > > > > Yours, > > Kees Jan > > > > ---------------------------------------------------------- > > Kees Jan Koster e-mail: kjkoster "at" kjkoster.org > > www: http://www.kjkoster.org/ > > ---------------------------------------------------------- > > Piglet: You're invited too! > > Eeyore: Hmpf, that must be a mistake. I'll go, but don't > > blame me if it rains. > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-alpha" in the body of the message > ---end of quoted text--- > > -- > | / 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 ---end of quoted text--- -- | / 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 Mon Feb 12 11:52:48 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 B0DBB37B491; Mon, 12 Feb 2001 11:52:46 -0800 (PST) Received: (from wilko@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f1CJqiZ28333; Mon, 12 Feb 2001 11:52:44 -0800 (PST) (envelope-from wilko) Date: Mon, 12 Feb 2001 11:52:44 -0800 (PST) From: Message-Id: <200102121952.f1CJqiZ28333@freefall.freebsd.org> To: Jan@online.be, wilko@FreeBSD.org, freebsd-alpha@freebsd.org Subject: Re: alpha/13653: panic: pmap_remove_all: pv_table for 90b60000 is inconsistent Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Synopsis: panic: pmap_remove_all: pv_table for 90b60000 is inconsistent State-Changed-From-To: open->closed State-Changed-By: wilko State-Changed-When: Mon Feb 12 11:51:35 PST 2001 State-Changed-Why: No reply received from originator after suggesting a test with 4-stable. http://www.freebsd.org/cgi/query-pr.cgi?pr=13653 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Feb 12 11:53:22 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 A34D737B491; Mon, 12 Feb 2001 11:53:21 -0800 (PST) Received: (from wilko@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f1CJrLN28423; Mon, 12 Feb 2001 11:53:21 -0800 (PST) (envelope-from wilko) Date: Mon, 12 Feb 2001 11:53:21 -0800 (PST) From: Message-Id: <200102121953.f1CJrLN28423@freefall.freebsd.org> To: Jan@online.be, wilko@FreeBSD.org, freebsd-alpha@freebsd.org Subject: Re: alpha/13338: panic: pmap_remove_all: pv_table for 162b0000 is inconsistent Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Synopsis: panic: pmap_remove_all: pv_table for 162b0000 is inconsistent State-Changed-From-To: open->closed State-Changed-By: wilko State-Changed-When: Mon Feb 12 11:53:04 PST 2001 State-Changed-Why: No reply received from originator after suggesting a test with 4-stable. http://www.freebsd.org/cgi/query-pr.cgi?pr=13338 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Feb 12 11:59:52 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from front4m.grolier.fr (front4m.grolier.fr [195.36.216.54]) by hub.freebsd.org (Postfix) with ESMTP id D24D637B491 for ; Mon, 12 Feb 2001 11:59:48 -0800 (PST) Received: from nas1-185.mea.club-internet.fr (nas1-185.mea.club-internet.fr [195.36.139.185]) by front4m.grolier.fr (8.9.3/No_Relay+No_Spam_MGC990224) with ESMTP id UAA11557; Mon, 12 Feb 2001 20:59:07 +0100 (MET) Date: Mon, 12 Feb 2001 19:58:31 +0100 (CET) From: =?ISO-8859-1?Q?G=E9rard_Roudier?= X-Sender: groudier@linux.local To: "Michael C . Wu" Cc: Mark Abene , alpha@FreeBSD.ORG Subject: Re: symbios card... In-Reply-To: <20010211152835.C19845@peorth.iteration.net> 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 Sun, 11 Feb 2001, Michael C . Wu wrote: > On Sun, Feb 11, 2001 at 04:46:34PM +0100, G=E9rard Roudier scribbled: > | On Sun, 11 Feb 2001, Mark Abene wrote: > | > Would anyone care to comment on whether the Symbios 53C825 (NOT 825A)= is > | > supported by FreeBSD? I saw mention of the 825A in the hardware list= , but > | SYM driver, as the sym-2.1.6 available from > | http://people.freebsd.org/~groudier/ >=20 > I have been using the SYM U160 driver on both Alpha and i386 with no prob= lem. > (And many people agree with me on that sym driver/chipset >> Adaptec * Thanks. I want to believe you :) (Btw, I haven't any Adaptec controller to perform the comparison:) ) > However, is there a reason why the driver is different from the one > in the base system? i.e. Why do you keep two copies of the driver? :) If fact there are 3 copies: :) - sym-1.6.x series in the base systems. Is the same (modulo a couple=20 of diffs due to kernel changes and latest commit not yet MFCed) in RELENG4 and TRUNK - sym-1.7.x in which I did dangerous changes I planned for sym-2 This driver series is withdrawn now that sym-2 exists. - sym-2 (current is sym-2.1.6) For now sym-2 is still beta status. It may well be at least as good than=20 latest sym-1.6.x for FreeBSD, but it is still beta for Linux. If I commit it to the FreeBSD repository, then it will go to production systems and large changes will get critical to apply to this sym-2. Or, in the _worst_ case, I will have to fork it, and as a result I will have=20 StillAnotherDifferentSymbiosDriverToMaintain.:) Btw, I planned to have sym-2 ok before 2001, and as we can see I am late for sym-2. Software development almost always takes more time than expected and sym-2 does fall in this category. :) For this reason, I have decided to maintain sym-1.6.x until sym-2 will be ready. If you follow the committers list, you will see that I am currently committings minimal changes to stock sym driver in order to maintain it at the same level as sym-2. MFCs happen 1 week later since they are not critical fixes. In my opinion, users will not see any difference between stock sym drivers and sym-2.1.6 under FreeBSD-4.x and 5.x. I just recommend sym-2.1.6 for RELENG3 for the following simple reasons: - sym driver in RELENG3 is an old version. - I have checked that sym-2.1.x does compile and work with RELENG3. - I am not sure that moving RELENG4 sym driver source to RELENG3 still compiles. Regards, G=E9rard. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Feb 12 17:58:40 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id CBA2037B503; Mon, 12 Feb 2001 17:58:34 -0800 (PST) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id CAA92793; Tue, 13 Feb 2001 02:58:34 +0100 (CET) (envelope-from des@ofug.org) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: freebsd-alpha@FreeBSD.ORG Cc: freebsd-arch@FreeBSD.ORG Subject: Re: Proposal on shared libs version values. References: <20010212174828.Q3038@dragon.nuxi.com> From: Dag-Erling Smorgrav Date: 13 Feb 2001 02:58:33 +0100 In-Reply-To: "David O'Brien"'s message of "Mon, 12 Feb 2001 17:48:28 -0800" Message-ID: Lines: 5 User-Agent: Gnus/5.0802 (Gnus v5.8.2) Emacs/20.4 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Please follow up on -arch, not on -alpha... DES -- Dag-Erling Smorgrav - des@ofug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Feb 13 0:44:45 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from io.rchrd1.on.wave.home.com (cr66388-a.rchrd1.on.wave.home.com [24.114.165.24]) by hub.freebsd.org (Postfix) with ESMTP id 9DC7E37B503; Tue, 13 Feb 2001 00:44:41 -0800 (PST) Received: from io.rchrd1.on.wave.home.com (localhost [127.0.0.1]) by io.rchrd1.on.wave.home.com (Postfix) with ESMTP id B335DBABD; Tue, 13 Feb 2001 01:43:02 -0500 (EST) X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.3 To: freebsd-alpha@FreeBSD.ORG Cc: freebsd-ia64@freebsd.org Subject: new runq code was Re: HEADS UP ... In-Reply-To: Your message of "Sun, 11 Feb 2001 19:28:20 EST." <20010212002820.84796BABD@cr66388-a.rchrd1.on.wave.home.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 13 Feb 2001 01:43:02 -0500 From: Jake Burkholder Message-Id: <20010213064302.B335DBABD@io.rchrd1.on.wave.home.com> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Another thing I forgot to mention about this is that I tried to allow for using a 64 bit status word for keeping track of the run queues. The way it works is that we have some power of 2 number of run queues, and bit array to keep track of which has processes on it; a set bit means non-empty. (same as the old run queue code, just generalized) If its better for some archs it should be possible to have a machine/runq.h which uses some number of 64 bit words for the bit array, rather than 32 bits. The rqb_word_t type would be u_int64_t, there's a RQB_FFS() macro that can be defined to ffs64() etc. Might be worth thinking about if you're looking to optimize. Jake To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Feb 13 2:46:55 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 4568A37B4EC for ; Tue, 13 Feb 2001 02:46:52 -0800 (PST) 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 <01K026RJQ2PQ00053M@research.kpn.com> for freebsd-alpha@FreeBSD.ORG; Tue, 13 Feb 2001 11:46:46 +0100 Received: by l04.research.kpn.com with Internet Mail Service (5.5.2653.19) id ; Tue, 13 Feb 2001 11:46:43 +0100 Content-return: allowed Date: Tue, 13 Feb 2001 11:46:38 +0100 From: "Koster, K.J." Subject: RE: /usr/obj required space To: 'Wilko Bulte' Cc: freebsd-alpha@FreeBSD.ORG Message-id: <59063B5B4D98D311BC0D0001FA7E4522026D7BFA@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 > > > I'm trying to get my little Alpha to build the world. Due to my > > disks dying of old age I have only limited diskspace left, so I > > mounted 500Mb on /usr/obj for the buildworld. Alas, too small. > > > > This seems funny, since on my x86 box the same tree is only > > ~330Mb in size. How come Alpha needs 200Mb more? > > mx5#du -ks * > 768419 usr > > Yesterday's -current on a Miata > Thanks Wilko, time to reshuffle the disks in the box. *sigh* On my PeeCee: LikeEver# cd /usr/obj LikeEver# du -ks * 330241 usr LikeEver# I knew that gcc wasn't terribly efficient on Alpha, but this is silly. More than twice the required disk space for a world build? 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 Tue Feb 13 6:25:29 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 59A3F37B491 for ; Tue, 13 Feb 2001 06:25:27 -0800 (PST) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.2/8.11.1) id f1DEOxg72183; Tue, 13 Feb 2001 06:24:59 -0800 (PST) (envelope-from obrien) Date: Tue, 13 Feb 2001 06:24:58 -0800 From: "David O'Brien" To: "Koster, K.J." Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: /usr/obj required space Message-ID: <20010213062458.A72052@dragon.nuxi.com> Reply-To: freebsd-alpha@FreeBSD.ORG References: <59063B5B4D98D311BC0D0001FA7E4522026D7BFA@l04.research.kpn.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <59063B5B4D98D311BC0D0001FA7E4522026D7BFA@l04.research.kpn.com>; from K.J.Koster@kpn.com on Tue, Feb 13, 2001 at 11:46:38AM +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, Feb 13, 2001 at 11:46:38AM +0100, Koster, K.J. wrote: > I knew that gcc wasn't terribly efficient on Alpha, but this is silly. More > than twice the required disk space for a world build? Don't blame it all on GCC. Don't forget your data segments are twice as big for int's. Pointers are twice as big, etc.. This is a 64bit vs. 32bit issue. Plus you don't get perfect allocation on the disk -- ie, you have fragmentation. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Feb 13 10: 8:24 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from post.mail.nl.demon.net (post-11.mail.nl.demon.net [194.159.73.21]) by hub.freebsd.org (Postfix) with ESMTP id DC9A637B491 for ; Tue, 13 Feb 2001 10:08:20 -0800 (PST) Received: from [212.238.54.101] (helo=freebie.demon.nl) by post.mail.nl.demon.net with smtp (Exim 3.14 #4) id 14SjsB-000OgV-00; Tue, 13 Feb 2001 18:08:19 +0000 Received: (from wkb@localhost) by freebie.demon.nl (8.11.1/8.11.1) id f1DIB3i20044; Tue, 13 Feb 2001 19:11:03 +0100 (CET) (envelope-from wkb) Date: Tue, 13 Feb 2001 19:11:03 +0100 From: "'Wilko Bulte'" To: "Koster, K.J." Cc: freebsd-alpha@freebsd.org Subject: Re: /usr/obj required space Message-ID: <20010213191103.A19426@freebie.demon.nl> References: <59063B5B4D98D311BC0D0001FA7E4522026D7BFA@l04.research.kpn.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <59063B5B4D98D311BC0D0001FA7E4522026D7BFA@l04.research.kpn.com>; from K.J.Koster@kpn.com on Tue, Feb 13, 2001 at 11:46:38AM +0100 X-OS: FreeBSD 4.2-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, Feb 13, 2001 at 11:46:38AM +0100, Koster, K.J. wrote: > > > > > I'm trying to get my little Alpha to build the world. Due to my > > > disks dying of old age I have only limited diskspace left, so I > > > mounted 500Mb on /usr/obj for the buildworld. Alas, too small. > > > > > > This seems funny, since on my x86 box the same tree is only > > > ~330Mb in size. How come Alpha needs 200Mb more? > > > > mx5#du -ks * > > 768419 usr > > > > Yesterday's -current on a Miata > > > Thanks Wilko, time to reshuffle the disks in the box. *sigh* > > On my PeeCee: > LikeEver# cd /usr/obj > LikeEver# du -ks * > 330241 usr > LikeEver# > > I knew that gcc wasn't terribly efficient on Alpha, but this is silly. More > than twice the required disk space for a world build? Alphas like alignment on 64 bit, so I would not blame it all on gcc. -- | / 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 Wed Feb 14 6:26: 8 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from madeline.boneyard.lawrence.ks.us (madeline.boneyard.lawrence.ks.us [24.124.26.25]) by hub.freebsd.org (Postfix) with ESMTP id 578D837B491 for ; Wed, 14 Feb 2001 06:26:06 -0800 (PST) Received: from madeline.boneyard.lawrence.ks.us (madeline.boneyard.lawrence.ks.us [24.124.26.25]) by madeline.boneyard.lawrence.ks.us (8.11.1/8.11.1) with ESMTP id f1EEOQT16445; Wed, 14 Feb 2001 08:24:27 -0600 (CST) (envelope-from bsd-alpha@boneyard.lawrence.ks.us) Date: Wed, 14 Feb 2001 08:24:26 -0600 (CST) From: "Stephen D. Spencer" To: "'Wilko Bulte'" Cc: "Koster, K.J." , freebsd-alpha@FreeBSD.ORG Subject: Re: /usr/obj required space In-Reply-To: <20010213191103.A19426@freebie.demon.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, 13 Feb 2001, 'Wilko Bulte' wrote: > On Tue, Feb 13, 2001 at 11:46:38AM +0100, Koster, K.J. wrote: > > > > This seems funny, since on my x86 box the same tree is only > > > > ~330Mb in size. How come Alpha needs 200Mb more? Another factor in the Alpha's binary size is that it is a RISC. If you take a look at the data sheet for the 21164, it has a rather small instruction set consisting of relatively primitive instructions. Though I have not yet read this document carefully, RISC instructions historically tend to execute in no more the 4 clock cycles vs the more complex instructions associated with CISC technology that can take over 100 clock cycles to complete. In a nut shell, RISC chips require more instructions to accomplish common tasks. More instructions will yield larger binaries as well as the buffer and word size issues that have already been mentioned. If you know any hard-core Macintosh users, ask them what happened to the size of binaries and disk space/memory requirements during the transition from the 68x000 -> PowerPC. -- Stephen Spencer UNIX Systems Administrator Electrical Engineering and Computer Science Dept. University of Kansas To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Feb 14 7:36:10 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from altrade.nijmegen.inter.nl.net (altrade.nijmegen.inter.nl.net [193.67.237.6]) by hub.freebsd.org (Postfix) with ESMTP id 0306B37B4EC for ; Wed, 14 Feb 2001 07:36:07 -0800 (PST) Received: from lent.nijmegen.inter.nl.net by altrade.nijmegen.inter.nl.net via lent.nijmegen.inter.nl.net [193.67.237.17] with ESMTP for id QAA03471 (8.8.8/1.3); Wed, 14 Feb 2001 16:36:06 +0100 (MET) Message-Id: <200102141536.QAA03471@altrade.nijmegen.inter.nl.net> Content-Transfer-Encoding: binary Content-Type: multipart/mixed; boundary="_----------=_982164965179410" MIME-Version: 1.0 X-Mailer: MIME::Lite 2.102 (B2.11; Q2.03) Date: Wed, 14 Feb 2001 15:36:05 UT From: Peter.Blok@inter.NL.net To: freebsd-alpha@freebsd.org Subject: unaligned access Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This is a multi-part message in MIME format. --_----------=_982164965179410 Content-Disposition: inline Content-Length: 567 Content-Transfer-Encoding: binary Content-Type: text/plain Hi, I am trying to port mpd-netgraph to alpha, but i'm getting a lot of uac's. I am trying to use gdb, but I am not used to gdb. When I try to lookup the address it tells me it is outside the map. Is it possible to make it core dump instead of this warning? It would be nice if you can say: run this command and core dump on uac. Are tools available to determine in which function the uac takes place? I can make something myself with perl and nm, but if there is already something out there? Which compiler options bring this up at compile time? Peter --_----------=_982164965179410-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Feb 14 9: 4:17 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 C2E0237B491 for ; Wed, 14 Feb 2001 09:04:14 -0800 (PST) Received: by mail.interchange.ca (Fastmailer, from userid 555) id A00702124; Wed, 14 Feb 2001 12:03:53 -0500 (EST) MIME-Version: 1.0 Message-Id: <3A8ABA79.00007D.61555@frodo.searchcanada.ca> Content-Type: Multipart/Mixed; boundary="------------Boundary-00=_HEBRWKR4GSJNTT4D7TH0" To: freebsd-alpha@freebsd.org Subject: Problems booting an AS1200 From: "Michael Richards" X-Fastmail-IP: 24.156.176.65 Date: Wed, 14 Feb 2001 12:03:53 -0500 (EST) Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org --------------Boundary-00=_HEBRWKR4GSJNTT4D7TH0 Content-Type: Text/Plain Content-Transfer-Encoding: 7bit Hi everyone. I can't seem to get this AS1200 machine to boot. It's a dual 533mhz with 256mb of RAM. It has an Adaptec 2940UW controller in it and a SCSI CD-ROM on the internal (symbios???) controller. So far I've tried 4.2 and 5.0-CURRENT Jan 26th snapshot. Here is a sample of what I get: FreeBSD/alpha SRM disk boot, Revision 1.1 (jkh@beast.freebsd.org, Fre Jan 26 17:54:36 GMT 2001) Memory: 262144 k / cb_open: failed DVA 0 1000 0 0 0 8086 002 dva0.0.0.1000.0 I get similar results with 4.2 booting from a CD. Any ideas? -Michael _________________________________________________________________ http://fastmail.ca/ - Fast Free Web Email for Canadians --------------Boundary-00=_HEBRWKR4GSJNTT4D7TH0-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Feb 14 10:42: 0 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 C4BC337B401 for ; Wed, 14 Feb 2001 10:41:56 -0800 (PST) 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 NAA29106; Wed, 14 Feb 2001 13:41:55 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.1/8.9.1) id f1EIfCI54156; Wed, 14 Feb 2001 13:41: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: <14986.53576.335104.667232@grasshopper.cs.duke.edu> Date: Wed, 14 Feb 2001 13:41:12 -0500 (EST) To: "Michael Richards" Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: Problems booting an AS1200 In-Reply-To: <3A8ABA79.00007D.61555@frodo.searchcanada.ca> References: <3A8ABA79.00007D.61555@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: > Hi everyone. > > I can't seem to get this AS1200 machine to boot. > It's a dual 533mhz with 256mb of RAM. It has an Adaptec 2940UW > controller in it and a SCSI CD-ROM on the internal (symbios???) > controller. > > So far I've tried 4.2 and 5.0-CURRENT Jan 26th snapshot. Here is a > sample of what I get: > FreeBSD/alpha SRM disk boot, Revision 1.1 > (jkh@beast.freebsd.org, Fre Jan 26 17:54:36 GMT 2001) > Memory: 262144 k > / > cb_open: failed DVA 0 1000 0 0 0 8086 002 dva0.0.0.1000.0 > > I get similar results with 4.2 booting from a CD. > > Any ideas? > The 1200 is part of the "rawhide" family of machines. Our bootloader provokes bugs in the console firmware of the rawhide (or vice versa) and prevents the machine from booting FreeBSD via floppy or CD-ROM devices. One workaround is to dd the contents of the boot.flp (2.8MB) floppy to a scsi disk and boot from that. Another option is to install FreeBSD using a different type of alpha and move the disk after the installation. Your situation is slightly more complex because you have an Adaptec 2940 SCSI controller. I don't think the SRM console will boot from that device (though FreeBSD supports it). It will only boot from drives listed by the ">>>show dev" command. Controllers which should work include Qlogic and NCR/LSI/SYMbios controllers. See http://www.freebsd.org/cgi/cvsweb.cgi/src/release/texts/alpha/HARDWARE.TXT?rev=1.22.2.43&content-type=text/x-cvsweb-markup for more details. I strongly suggest you do not run 5.0 on this box right now. Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Feb 14 10:51:23 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 4A0B737B401 for ; Wed, 14 Feb 2001 10:51:20 -0800 (PST) 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 NAA29294; Wed, 14 Feb 2001 13:51:19 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.1/8.9.1) id f1EIoaB54228; Wed, 14 Feb 2001 13:50:36 -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: <14986.54140.54832.224655@grasshopper.cs.duke.edu> Date: Wed, 14 Feb 2001 13:50:36 -0500 (EST) To: Peter.Blok@inter.NL.net Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: unaligned access In-Reply-To: <200102141536.QAA03471@altrade.nijmegen.inter.nl.net> References: <200102141536.QAA03471@altrade.nijmegen.inter.nl.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 Peter.Blok@inter.NL.net writes: > Hi, > > I am trying to port mpd-netgraph to alpha, but i'm getting a lot of uac's. I am trying to use gdb, but I am not used to gdb. When I try to lookup the address it tells me it is outside the map. > > Is it possible to make it core dump instead of this warning? It would be nice if you can say: run this command and core dump on uac. > > Are tools available to determine in which function the uac takes place? I can make something myself with perl and nm, but if there is already something out there? > > Which compiler options bring this up at compile time? > > Peter I don't know what mpd netgraph is. Can you elaborate further? Is the kernel crashing, or is it a userland app? If it is a userland app, try running uap -s prior to invoking gdb. Then run gdb on the app. You should get a SIGBUS at the PC of the unaligned access. If gdb misbehaves, try increasing the size of the heuristic-fence-post. Eg: (gdb) set heuristic-fence-post 0xffffffffffffffff Hope this 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 Feb 14 10:58:21 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from post.mail.nl.demon.net (post-11.mail.nl.demon.net [194.159.73.21]) by hub.freebsd.org (Postfix) with ESMTP id CC62437B4EC for ; Wed, 14 Feb 2001 10:58:17 -0800 (PST) Received: from [212.238.54.101] (helo=freebie.demon.nl) by post.mail.nl.demon.net with smtp (Exim 3.14 #4) id 14T77x-000A8W-00; Wed, 14 Feb 2001 18:58:10 +0000 Received: (from wkb@localhost) by freebie.demon.nl (8.11.1/8.11.1) id f1EJ0w401166; Wed, 14 Feb 2001 20:00:58 +0100 (CET) (envelope-from wkb) Date: Wed, 14 Feb 2001 20:00:58 +0100 From: Wilko Bulte To: Andrew Gallatin Cc: Michael Richards , freebsd-alpha@freebsd.org Subject: Re: Problems booting an AS1200 Message-ID: <20010214200058.A1114@freebie.demon.nl> References: <3A8ABA79.00007D.61555@frodo.searchcanada.ca> <14986.53576.335104.667232@grasshopper.cs.duke.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <14986.53576.335104.667232@grasshopper.cs.duke.edu>; from gallatin@cs.duke.edu on Wed, Feb 14, 2001 at 01:41:12PM -0500 X-OS: FreeBSD 4.2-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, Feb 14, 2001 at 01:41:12PM -0500, Andrew Gallatin wrote: > > cb_open: failed DVA 0 1000 0 0 0 8086 002 dva0.0.0.1000.0 > > > > I get similar results with 4.2 booting from a CD. > > > > Any ideas? > > > > The 1200 is part of the "rawhide" family of machines. Our bootloader > provokes bugs in the console firmware of the rawhide (or vice versa) > and prevents the machine from booting FreeBSD via floppy or CD-ROM > devices. > > One workaround is to dd the contents of the boot.flp (2.8MB) floppy to > a scsi disk and boot from that. Another option is to install FreeBSD > using a different type of alpha and move the disk after the > installation. > > Your situation is slightly more complex because you have an Adaptec > 2940 SCSI controller. I don't think the SRM console will boot from > that device (though FreeBSD supports it). It will only boot from No, SRM does not boot from the Adaptec. -- | / 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 Wed Feb 14 12: 1:21 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 389BD37B4EC for ; Wed, 14 Feb 2001 12:01:19 -0800 (PST) Received: by mail.interchange.ca (Fastmailer, from userid 555) id 20791209A; Wed, 14 Feb 2001 15:00:59 -0500 (EST) MIME-Version: 1.0 Message-Id: <3A8AE3FB.00005F.92120@frodo.searchcanada.ca> Content-Type: Multipart/Mixed; boundary="------------Boundary-00=_NLJR2PC3LIFNTT4D7TH0" To: gallatin@cs.duke.edu Subject: Re: Problems booting an AS1200 Cc: freebsd-alpha@FreeBSD.ORG From: "Michael Richards" X-Fastmail-IP: 24.156.176.65 Date: Wed, 14 Feb 2001 15:00:59 -0500 (EST) Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org --------------Boundary-00=_NLJR2PC3LIFNTT4D7TH0 Content-Type: Text/Plain Content-Transfer-Encoding: 7bit > The 1200 is part of the "rawhide" family of machines. Our > bootloader provokes bugs in the console firmware of the rawhide > (or vice versa) and prevents the machine from booting FreeBSD via > floppy or CD-ROM devices. Has anyone narrowed these bugs down so we know exactly what the problem is? Is it reasonable to expect a workaround, or is this simply not possible? > One workaround is to dd the contents of the boot.flp (2.8MB) > floppy to a scsi disk and boot from that. If I do this, can I actually install over that drive, or is it not loaded into a memory disk? > Your situation is slightly more complex because you have an > Adaptec 2940 SCSI controller. I don't think the SRM console will > boot from that device (though FreeBSD supports it). It will only > boot from drives listed by the ">>>show dev" command. Controllers > which should work include Qlogic and NCR/LSI/SYMbios controllers. So I see. I guess I will switch it around so the hard drives run from the onboard controller and the CD-Rom runs from the adaptec. I don't know why they set it up this way... > I strongly suggest you do not run 5.0 on this box right now. Why is that and what is wrong with 5.0? -Michael _________________________________________________________________ http://fastmail.ca/ - Fast Free Web Email for Canadians --------------Boundary-00=_NLJR2PC3LIFNTT4D7TH0-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Feb 14 12: 8: 3 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 02E7C37B4EC for ; Wed, 14 Feb 2001 12:07:59 -0800 (PST) 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 PAA01211; Wed, 14 Feb 2001 15:07:57 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.1/8.9.1) id f1EK7Ev54739; Wed, 14 Feb 2001 15:07:14 -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: <14986.58738.419137.472927@grasshopper.cs.duke.edu> Date: Wed, 14 Feb 2001 15:07:14 -0500 (EST) To: "Michael Richards" Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: Problems booting an AS1200 In-Reply-To: <3A8AE3FB.00005F.92120@frodo.searchcanada.ca> References: <3A8AE3FB.00005F.92120@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: > > The 1200 is part of the "rawhide" family of machines. Our > > bootloader provokes bugs in the console firmware of the rawhide > > (or vice versa) and prevents the machine from booting FreeBSD via > > floppy or CD-ROM devices. > > Has anyone narrowed these bugs down so we know exactly what the > problem is? Is it reasonable to expect a workaround, or is this > simply not possible? The rawhide maintainer has looked into it, but he doesn't know what the problem is. I would not expect a fix any time soon. > > One workaround is to dd the contents of the boot.flp (2.8MB) > > floppy to a scsi disk and boot from that. > > If I do this, can I actually install over that drive, or is it not > loaded into a memory disk? Yes, I think you can install over the drive. Another option might be netbooting the install kernel from that floppy. That process is not documented and is very time consuming to explain. > > Your situation is slightly more complex because you have an > > Adaptec 2940 SCSI controller. I don't think the SRM console will > > boot from that device (though FreeBSD supports it). It will only > > boot from drives listed by the ">>>show dev" command. Controllers > > which should work include Qlogic and NCR/LSI/SYMbios controllers. > > So I see. I guess I will switch it around so the hard drives run from > the onboard controller and the CD-Rom runs from the adaptec. I don't > know why they set it up this way... > > > I strongly suggest you do not run 5.0 on this box right now. > > Why is that and what is wrong with 5.0? FreeBSD 5.0 does not boot reliably on rawhide & hasn't since SMPng hit the tree. The problem has apparently been tracked down and should be fixed shortly. Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Feb 14 12: 9:52 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 56B2F37B65D for ; Wed, 14 Feb 2001 12:09:47 -0800 (PST) Received: from [212.238.54.101] (helo=freebie.demon.nl) by post.mail.nl.demon.net with smtp (Exim 3.14 #2) id 14T8FF-0000NK-00; Wed, 14 Feb 2001 20:09:45 +0000 Received: (from wkb@localhost) by freebie.demon.nl (8.11.1/8.11.1) id f1EKCYw01751; Wed, 14 Feb 2001 21:12:34 +0100 (CET) (envelope-from wkb) Date: Wed, 14 Feb 2001 21:12:34 +0100 From: Wilko Bulte To: Michael Richards Cc: gallatin@cs.duke.edu, freebsd-alpha@freebsd.org Subject: Re: Problems booting an AS1200 Message-ID: <20010214211234.A1737@freebie.demon.nl> References: <3A8AE3FB.00005F.92120@frodo.searchcanada.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <3A8AE3FB.00005F.92120@frodo.searchcanada.ca>; from michael@fastmail.ca on Wed, Feb 14, 2001 at 03:00:59PM -0500 X-OS: FreeBSD 4.2-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, Feb 14, 2001 at 03:00:59PM -0500, Michael Richards wrote: > > The 1200 is part of the "rawhide" family of machines. Our > > bootloader provokes bugs in the console firmware of the rawhide > > (or vice versa) and prevents the machine from booting FreeBSD via > > floppy or CD-ROM devices. > > Has anyone narrowed these bugs down so we know exactly what the > problem is? Is it reasonable to expect a workaround, or is this Not that I know. So if you can investigate more please do so. > simply not possible? As Tru64 & VMS can boot from CD on these boxes it definitely can be made to work ;) > So I see. I guess I will switch it around so the hard drives run from > the onboard controller and the CD-Rom runs from the adaptec. I don't > know why they set it up this way... > > > I strongly suggest you do not run 5.0 on this box right now. > > Why is that and what is wrong with 5.0? -current is not the place to be at the moment (starting as of Feb 10 or so). Some library compatibility hassles have been introduced :-( Stick to releng_4 for this debugging work, once you know what is wrong it will most likely apply to -current as well. W/ -- | / 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 Wed Feb 14 13: 7:44 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from altrade.nijmegen.inter.nl.net (altrade.nijmegen.inter.nl.net [193.67.237.6]) by hub.freebsd.org (Postfix) with ESMTP id A3B5D37B4EC for ; Wed, 14 Feb 2001 13:07:40 -0800 (PST) Received: from ntpc by altrade.nijmegen.inter.nl.net via 1Cust207.tnt26.rtm1.nl.uu.net [213.116.146.207] with SMTP id WAA02951 (8.8.8/1.3); Wed, 14 Feb 2001 22:07:34 +0100 (MET) Reply-To: From: "Peter Blok" To: "'Andrew Gallatin'" , Cc: Subject: RE: unaligned access Date: Wed, 14 Feb 2001 21:11:44 +0100 Message-ID: <000101c096c2$5a901df0$8a02a8c0@ntpc> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2910.0) In-Reply-To: <14986.54140.54832.224655@grasshopper.cs.duke.edu> X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Importance: Normal Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Drew, mpd-netgraph is the multi-link ppp netgraph daemon. It uses the kernel netgraph functionality, to connect communication end-points in the kernel. I am using it to setup a pptp connection to my internet provider. All the handshaking stuff is done at user space, the comms are done in the kernel. With pppd I was only able to do 55KB/s, with netgraph it is running at 100KB/s which is the providers limit. The user level part breaks. I haven't reached the kernel part yet. Thanks for the tips, Peter -----Original Message----- From: Andrew Gallatin [mailto:gallatin@cs.duke.edu] Sent: Wednesday, February 14, 2001 19:51 To: Peter.Blok@inter.NL.net Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: unaligned access Peter.Blok@inter.NL.net writes: > Hi, > > I am trying to port mpd-netgraph to alpha, but i'm getting a lot of uac's. I am trying to use gdb, but I am not used to gdb. When I try to lookup the address it tells me it is outside the map. > > Is it possible to make it core dump instead of this warning? It would be nice if you can say: run this command and core dump on uac. > > Are tools available to determine in which function the uac takes place? I can make something myself with perl and nm, but if there is already something out there? > > Which compiler options bring this up at compile time? > > Peter I don't know what mpd netgraph is. Can you elaborate further? Is the kernel crashing, or is it a userland app? If it is a userland app, try running uap -s prior to invoking gdb. Then run gdb on the app. You should get a SIGBUS at the PC of the unaligned access. If gdb misbehaves, try increasing the size of the heuristic-fence-post. Eg: (gdb) set heuristic-fence-post 0xffffffffffffffff Hope this 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 Feb 14 16:24:45 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from smtp03.primenet.com (smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (Postfix) with ESMTP id 77F6C37B401 for ; Wed, 14 Feb 2001 16:24:43 -0800 (PST) Received: (from daemon@localhost) by smtp03.primenet.com (8.9.3/8.9.3) id RAA03660; Wed, 14 Feb 2001 17:21:36 -0700 (MST) Received: from usr08.primenet.com(206.165.6.208) via SMTP by smtp03.primenet.com, id smtpdAAA3Oaqch; Wed Feb 14 17:21:28 2001 Received: (from tlambert@localhost) by usr08.primenet.com (8.8.5/8.8.5) id RAA09608; Wed, 14 Feb 2001 17:24:26 -0700 (MST) From: Terry Lambert Message-Id: <200102150024.RAA09608@usr08.primenet.com> Subject: Re: /usr/obj required space To: bsd-alpha@boneyard.lawrence.ks.us (Stephen D. Spencer) Date: Thu, 15 Feb 2001 00:24:21 +0000 (GMT) Cc: wkb@freebie.demon.nl ('Wilko Bulte'), K.J.Koster@kpn.com (Koster K.J.), freebsd-alpha@FreeBSD.ORG In-Reply-To: from "Stephen D. Spencer" at Feb 14, 2001 08:24:26 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 > Another factor in the Alpha's binary size is that it is a RISC. If you > take a look at the data sheet for the 21164, it has a rather small > instruction set consisting of relatively primitive instructions. > Though I have not yet read this document carefully, RISC instructions > historically tend to execute in no more the 4 clock cycles vs the more > complex instructions associated with CISC technology that can take > over 100 clock cycles to complete. In a nut shell, RISC chips require > more instructions to accomplish common tasks. More instructions will > yield larger binaries as well as the buffer and word size issues > that have already been mentioned. > > If you know any hard-core Macintosh users, ask them what happened to > the size of binaries and disk space/memory requirements during the > transition from the 68x000 -> PowerPC. Many binaries during that transition had CODE resources for both the PPC and the 68k, so that the program would run on the 68k, but run faster on the PPC (and not require 68k emulation: still faster, but slower than native code). For the Alpha, there's a significant amout of work compilers, particularly the Compaq compiler, go to, in order to ensure instructions are padded to alignment boundaries and are reordered in the pipeline, which can result in significant code bloat. This is really expected, since the trade off is to build code where some instructions take more than a single bus cycle to fetch (because they span such a boundary). This is one of the reasons the Compaq compiler produces code that is both somewhat larger, yet significantly faster, than the GCC generated code for the same source. Prefetch only works for branches that don't exceed an L1 cache entry in distance. 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 Wed Feb 14 16:46:42 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from smtp03.primenet.com (smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (Postfix) with ESMTP id 93E9A37B401 for ; Wed, 14 Feb 2001 16:46:38 -0800 (PST) Received: (from daemon@localhost) by smtp03.primenet.com (8.9.3/8.9.3) id RAA11695; Wed, 14 Feb 2001 17:43:31 -0700 (MST) Received: from usr08.primenet.com(206.165.6.208) via SMTP by smtp03.primenet.com, id smtpdAAA.saGKw; Wed Feb 14 17:43:13 2001 Received: (from tlambert@localhost) by usr08.primenet.com (8.8.5/8.8.5) id RAA10115; Wed, 14 Feb 2001 17:46:10 -0700 (MST) From: Terry Lambert Message-Id: <200102150046.RAA10115@usr08.primenet.com> Subject: Re: unaligned access To: gallatin@cs.duke.edu (Andrew Gallatin) Date: Thu, 15 Feb 2001 00:46:04 +0000 (GMT) Cc: Peter.Blok@inter.NL.net, freebsd-alpha@FreeBSD.ORG In-Reply-To: <14986.54140.54832.224655@grasshopper.cs.duke.edu> from "Andrew Gallatin" at Feb 14, 2001 01:50:36 PM 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 > > I am trying to port mpd-netgraph to alpha, but i'm getting a > > lot of uac's. I am trying to use gdb, but I am not used to > > gdb. When I try to lookup the address it tells me it is > > outside the map. > > > > Is it possible to make it core dump instead of this warning? > > It would be nice if you can say: run this command and core > > dump on uac. > > > > Are tools available to determine in which function the uac > > takes place? I can make something myself with perl and nm, > > but if there is already something out there? > > > > Which compiler options bring this up at compile time? > > I don't know what mpd netgraph is. Can you elaborate further? Is the > kernel crashing, or is it a userland app? > > If it is a userland app, try running uap -s prior to invoking gdb. > Then run gdb on the app. You should get a SIGBUS at the PC of the > unaligned access. If gdb misbehaves, try increasing the size of the > heuristic-fence-post. Eg: > > (gdb) set heuristic-fence-post 0xffffffffffffffff The mpd program is Archie's multiplink PPP daemon; I'm pretty sure he had a pure kernel version released before he left Whistle, didn't he? It has to be the user space stuff, or it would be a panic, and he probably would be unable to use gdb. The "uap -s" program will work. It is a single instance overrride for the command argument. Without the gdb involved, it will core dump (which I've always found a lot more useful than stepping through with gdb, for all but one problem, over the years). There is also a sysctl, which will turn off the unaligned access trap fixup, and crash the program; I don't know why fixup is the default these days. Apparently, mpd hates the fixup process, since you'd expect it to work. Since the Alpha has x86 byte order, I'd suggest that the structure where data is having its unaligned dereference is probably a structure element dereference off a pointer cast from a character buffer. Look for your bug to go away if you use a "#pragma pack(1)" around the structure declarations used by the program. If the data is naturally aligned, and it's just the character buffer that's being cast that's the problem (been too long since I've had to read entrails in the PPP code, sorry), then you should be able to get away with creating an aligned buffer to which you copy the character buf data, prior to dereference. Even if you change the packing, and rely on the fixup, or you use an aligned buffer that you copy data into from an unaligned one, I suspect that you will still end up with unaligned fixups (I can't believe the PPP designers thought that far ahead). Getting rid of the unaligned fixups will probably end up being a bear. This may already be there, since I'm running rather old Alpha code (multia didn't work again until recently, and SMP work means "Stable Machine Precluded" to me), but it might be useful to add a "uap" argument that will suppress the printing of the meessages on a per process basis (sort of the opposite of the "cause a segmentation fault" flag). This would let the console be usable for things like CVSup of new code, when the process that provides yor connection to the network is faulting all over the place, and you need to download new code for it. 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 Wed Feb 14 17:43: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 747D937B401 for ; Wed, 14 Feb 2001 17:43:25 -0800 (PST) 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 UAA07214; Wed, 14 Feb 2001 20:43:17 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.1/8.9.1) id f1F1gXl55945; Wed, 14 Feb 2001 20:42:33 -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: <14987.13321.676098.108958@grasshopper.cs.duke.edu> Date: Wed, 14 Feb 2001 20:42:33 -0500 (EST) To: Terry Lambert Cc: gallatin@cs.duke.edu (Andrew Gallatin), Peter.Blok@inter.NL.net, freebsd-alpha@FreeBSD.ORG Subject: Re: unaligned access In-Reply-To: <200102150046.RAA10115@usr08.primenet.com> References: <14986.54140.54832.224655@grasshopper.cs.duke.edu> <200102150046.RAA10115@usr08.primenet.com> 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 Terry Lambert writes: > This may already be there, since I'm running rather old Alpha > code (multia didn't work again until recently, and SMP work > means "Stable Machine Precluded" to me), but it might be useful > to add a "uap" argument that will suppress the printing of the > meessages on a per process basis (sort of the opposite of the > "cause a segmentation fault" flag). This would let the console > be usable for things like CVSup of new code, when the process > that provides yor connection to the network is faulting all over > the place, and you need to download new code for it. See the uac man page. Specifically, the -p arg: UAC(1) FreeBSD General Commands Manual UAC(1) NAME uac - Unaligned Access Message Control SYNOPSIS uac [-fprs] <...> -p Unaligned access errors are not printed for the parent and its future descendants. Cheers, Drew ------------------------------------------------------------------------------ Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin Duke University Email: gallatin@cs.duke.edu Department of Computer Science Phone: (919) 660-6590 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Feb 14 18: 0:17 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 BDE4D37B4EC for ; Wed, 14 Feb 2001 18:00:14 -0800 (PST) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.1/8.11.1) with ESMTP id f1F20ei02223; Wed, 14 Feb 2001 18:00:40 -0800 (PST) (envelope-from msmith@mass.dis.org) Message-Id: <200102150200.f1F20ei02223@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Peter Jeremy Cc: alpha@freebsd.org Subject: Re: Accessing a PCI device by `physical' address In-reply-to: Your message of "Thu, 15 Feb 2001 12:40:01 +1100." <20010215124001.A71053@gsmx07.alcatel.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 14 Feb 2001 18:00:40 -0800 From: Mike Smith Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org (should have been posted to -alpha) This actually poses quite a problem. The way that the PCI code is architected now means that you can't actually talk to any of the PCI hardware until after the root bridge has been discovered. However, I think that you're not in such a bad position as you think. From my understanding of the Alpha, you don't actually need to init the TGA to become console in the "early" console phase at all; you can keep using the SRM console vectors until the driver "really" probes/attaches. Thinking about it some more, though, this probably doesn't integrate well with syscons. 8( I'm kinda stumped, here. I don't think there's a clean way to do this, which is bad. We probably need to fix this. Thoughts? > I'm trying to port an Alpha video driver (TGA) from -stable to > -current and have run into a problem converting some calls to > pci_cfgread() and pci_cfgwrite(). > > The Alpha firmware reports the location of the console video card as a > physical hose, bus type, bus, slot value. In -stable, the card can be > accessed by calling pci_cfg{read,write}() with this information. > > In -current, pci_cfg{read,write}() have been replaced by > pci_{read,write}_config(), but the latter function needs a device_t > structure that defines both the device and it's parent. > Unfortunately, I don't have the relevant device_t available. In any > case, based on my reading of the code, I need to access the PCI config > registers before the video card has been probed/attached via the > normal bus/device scan. > > Luckily, there's only one point at which I need this `physical' access. > The call backtrace is: > pci_cfg{read,write}() > tga_configure() > vid_configure() > scvidprobe() > sccnattach() > <>_cons_init() > alpha_init() > ... > > Does anyone have any useful suggestions?[1] Is there an `approved' > mechanism to bypass the bus abstraction layers? Is is practical to > hand-craft a device_t that will satisfy pci_{read,write}_config()? > > [1] I don't count "throw out the TGA" as a useful suggestion. > > Peter > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- ... 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 Wed Feb 14 18:25:23 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 0B36937B4EC; Wed, 14 Feb 2001 18:25:19 -0800 (PST) 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 VAA07668; Wed, 14 Feb 2001 21:25:07 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.1/8.9.1) id f1F2OOS56012; Wed, 14 Feb 2001 21:24:24 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14987.15832.39211.2856@grasshopper.cs.duke.edu> Date: Wed, 14 Feb 2001 21:24:24 -0500 (EST) To: Mike Smith Cc: Peter Jeremy , alpha@FreeBSD.ORG Subject: Re: Accessing a PCI device by `physical' address In-Reply-To: <200102150200.f1F20ei02223@mass.dis.org> References: <20010215124001.A71053@gsmx07.alcatel.com.au> <200102150200.f1F20ei02223@mass.dis.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 Mike Smith writes: > > Thinking about it some more, though, this probably doesn't integrate well > with syscons. 8( Exactly. Syscons has an easy time of it running early because it knows VGA adapters will be at certain magic I/O ports. Ick. > I'm kinda stumped, here. I don't think there's a clean way to do this, > which is bad. We probably need to fix this. Thoughts? Kinda gross, but you could add pcib_{read,write}_config() fields to the platform struct & init them in the various chipset init functions. Most platforms don't use the first arg (device_t). Those that do (tsunami, mcpcia) could probably be hacked to treat a null device_t as if it were the 0th hose. I don't think SRM supports console devices anywhere but the 0th hose anyway. I assume you're forward-porting Andrew Miklic's driver? Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Feb 14 23:51:12 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 0854337B503 for ; Wed, 14 Feb 2001 23:51:10 -0800 (PST) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.2/8.11.1) id f1F7okY66619; Wed, 14 Feb 2001 23:50:46 -0800 (PST) (envelope-from obrien) Date: Wed, 14 Feb 2001 23:50:46 -0800 From: "David O'Brien" To: Michael Richards Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: Problems booting an AS1200 Message-ID: <20010214235046.E65907@dragon.nuxi.com> Reply-To: freebsd-alpha@FreeBSD.ORG References: <3A8AE3FB.00005F.92120@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: <3A8AE3FB.00005F.92120@frodo.searchcanada.ca>; from michael@fastmail.ca on Wed, Feb 14, 2001 at 03:00:59PM -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, Feb 14, 2001 at 03:00:59PM -0500, Michael Richards wrote: > > The 1200 is part of the "rawhide" family of machines. Our > > bootloader provokes bugs in the console firmware of the rawhide > > (or vice versa) and prevents the machine from booting FreeBSD via > > floppy or CD-ROM devices. > > Has anyone narrowed these bugs down so we know exactly what the > problem is? Is it reasonable to expect a workaround, or is this > simply not possible? No one has spent any real time on this. I set myself up to trudge thru it, if Matt Jacobs (who did the Rawhide support) had time to work on it. But that hasn't happened. > So I see. I guess I will switch it around so the hard drives run from > the onboard controller and the CD-Rom runs from the adaptec. Then you could not boot from CDROM (once the loader is fixed). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Feb 15 1:15: 9 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 B3AD437B491 for ; Thu, 15 Feb 2001 01:15:07 -0800 (PST) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.2/8.11.1) id f1F9ElM68601; Thu, 15 Feb 2001 01:14:47 -0800 (PST) (envelope-from obrien) Date: Thu, 15 Feb 2001 01:14:47 -0800 From: "David O'Brien" To: Peter.Blok@inter.NL.net, freebsd-alpha@FreeBSD.ORG Subject: Re: unaligned access Message-ID: <20010215011447.A66813@dragon.nuxi.com> Reply-To: freebsd-alpha@FreeBSD.ORG References: <14986.54140.54832.224655@grasshopper.cs.duke.edu> <200102150046.RAA10115@usr08.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200102150046.RAA10115@usr08.primenet.com>; from tlambert@primenet.com on Thu, Feb 15, 2001 at 12:46:04AM +0000 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, Feb 15, 2001 at 12:46:04AM +0000, Terry Lambert wrote: > The "uap -s" program will work. ^^^ uac To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Feb 15 4: 1:12 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from altrade.nijmegen.inter.nl.net (altrade.nijmegen.inter.nl.net [193.67.237.6]) by hub.freebsd.org (Postfix) with ESMTP id 999C237B491 for ; Thu, 15 Feb 2001 04:01:06 -0800 (PST) Received: from ntpc by altrade.nijmegen.inter.nl.net via 1Cust34.tnt18.rtm1.nl.uu.net [213.116.130.34] with SMTP id NAA20203 (8.8.8/1.3); Thu, 15 Feb 2001 13:01:00 +0100 (MET) Reply-To: From: "Peter Blok" To: "'Terry Lambert'" , "'Andrew Gallatin'" Cc: , Subject: RE: unaligned access Date: Thu, 15 Feb 2001 12:59:00 +0100 Message-ID: <000001c09746$af96e2a0$8a02a8c0@ntpc> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2910.0) In-Reply-To: <200102150046.RAA10115@usr08.primenet.com> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Terry, and others. Thanks for the hints. One big cause was the embedded alloc routines, that doesn't do aligning. The next buffer allocated was unaligned, because the previous size was unaligned. I haven't looked closely enough to the structures. I also had one unaligned access in a varargs construction. Haven't found the cause yet. Peter -----Original Message----- From: Terry Lambert [mailto:tlambert@primenet.com] Sent: Thursday, February 15, 2001 01:46 To: Andrew Gallatin Cc: Peter.Blok@inter.NL.net; freebsd-alpha@FreeBSD.ORG Subject: Re: unaligned access > > I am trying to port mpd-netgraph to alpha, but i'm getting a > > lot of uac's. I am trying to use gdb, but I am not used to > > gdb. When I try to lookup the address it tells me it is > > outside the map. > > > > Is it possible to make it core dump instead of this warning? > > It would be nice if you can say: run this command and core > > dump on uac. > > > > Are tools available to determine in which function the uac > > takes place? I can make something myself with perl and nm, > > but if there is already something out there? > > > > Which compiler options bring this up at compile time? > > I don't know what mpd netgraph is. Can you elaborate further? Is the > kernel crashing, or is it a userland app? > > If it is a userland app, try running uap -s prior to invoking gdb. > Then run gdb on the app. You should get a SIGBUS at the PC of the > unaligned access. If gdb misbehaves, try increasing the size of the > heuristic-fence-post. Eg: > > (gdb) set heuristic-fence-post 0xffffffffffffffff The mpd program is Archie's multiplink PPP daemon; I'm pretty sure he had a pure kernel version released before he left Whistle, didn't he? It has to be the user space stuff, or it would be a panic, and he probably would be unable to use gdb. The "uap -s" program will work. It is a single instance overrride for the command argument. Without the gdb involved, it will core dump (which I've always found a lot more useful than stepping through with gdb, for all but one problem, over the years). There is also a sysctl, which will turn off the unaligned access trap fixup, and crash the program; I don't know why fixup is the default these days. Apparently, mpd hates the fixup process, since you'd expect it to work. Since the Alpha has x86 byte order, I'd suggest that the structure where data is having its unaligned dereference is probably a structure element dereference off a pointer cast from a character buffer. Look for your bug to go away if you use a "#pragma pack(1)" around the structure declarations used by the program. If the data is naturally aligned, and it's just the character buffer that's being cast that's the problem (been too long since I've had to read entrails in the PPP code, sorry), then you should be able to get away with creating an aligned buffer to which you copy the character buf data, prior to dereference. Even if you change the packing, and rely on the fixup, or you use an aligned buffer that you copy data into from an unaligned one, I suspect that you will still end up with unaligned fixups (I can't believe the PPP designers thought that far ahead). Getting rid of the unaligned fixups will probably end up being a bear. This may already be there, since I'm running rather old Alpha code (multia didn't work again until recently, and SMP work means "Stable Machine Precluded" to me), but it might be useful to add a "uap" argument that will suppress the printing of the meessages on a per process basis (sort of the opposite of the "cause a segmentation fault" flag). This would let the console be usable for things like CVSup of new code, when the process that provides yor connection to the network is faulting all over the place, and you need to download new code for it. 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 Thu Feb 15 6:31:41 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from 1upmc-msx1.isdip.upmc.edu (1upmc-msx1.isdip.upmc.edu [128.147.16.38]) by hub.freebsd.org (Postfix) with ESMTP id 3B4F637B401 for ; Thu, 15 Feb 2001 06:31:37 -0800 (PST) Received: by 1upmc-msx1.isdip.upmc.edu with Internet Mail Service (5.5.2650.21) id <1CSFPJHW>; Thu, 15 Feb 2001 09:31:01 -0500 Message-ID: From: "Person, Roderick" To: 'Alpha FreeBSD' Subject: Finally after 6 months..... Date: Thu, 15 Feb 2001 09:30:54 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C0975B.EB350534" Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01C0975B.EB350534 Content-Type: text/plain; charset="iso-8859-1" Finally, after 6 months I have got my home built Alpha AXPpci to boot install FreeBSD and not get machine errors. So for fair warning this being my first Alpha ever, I my ask stupid questions so please bear with me. My first question is, where is the Linux_base package for Alpha. I have search ftp.freebsd.org and ftp2.freebsd.org and no luck, I went to the web site found the link and it say the package does not exist. I know some packages are arch independent, but I would not assume that Linux_base would be one. That is a correct assumption, is it not? Well any help would be appreciated. TIA Roderick P. Person Programmer II personrp@ccbh.com "To hell with the public! I'm here to represent the people!" - A New Jersey state senator ------_=_NextPart_001_01C0975B.EB350534 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Finally after 6 months.....

Finally, after 6 months I have got my home built = Alpha AXPpci to boot install FreeBSD and not get machine errors.

So for fair warning this being my first Alpha ever, I = my ask stupid questions so please bear with me. My first question is, = where is the Linux_base package for Alpha. I have search = ftp.freebsd.org and ftp2.freebsd.org and no luck, I went to the web = site found the link and it say the package does not exist. I know some = packages are arch independent, but I would not assume that Linux_base = would be one. That is a correct assumption, is it not? Well any help = would be appreciated.

TIA

Roderick P. Person
Programmer II
personrp@ccbh.com


"To hell with the public! I'm here to represent = the people!"

     - A New Jersey state senator =

------_=_NextPart_001_01C0975B.EB350534-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Feb 15 6:36: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 4A08C37B6A3 for ; Thu, 15 Feb 2001 06:36:51 -0800 (PST) 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 JAA16327; Thu, 15 Feb 2001 09:36:48 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.1/8.9.1) id f1FEa3t57364; Thu, 15 Feb 2001 09:36:03 -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: <14987.59731.793186.82251@grasshopper.cs.duke.edu> Date: Thu, 15 Feb 2001 09:36:03 -0500 (EST) To: "Person, Roderick" Cc: freebsd-alpha@freebsd.org Subject: Re: Finally after 6 months..... In-Reply-To: References: 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 Person, Roderick writes: > Finally, after 6 months I have got my home built Alpha AXPpci to boot > install FreeBSD and not get machine errors. > > So for fair warning this being my first Alpha ever, I my ask stupid > questions so please bear with me. My first question is, where is the > Linux_base package for Alpha. I have search ftp.freebsd.org and > ftp2.freebsd.org and no luck, I went to the web site found the link and it > say the package does not exist. I know some packages are arch independent, > but I would not assume that Linux_base would be one. That is a correct > assumption, is it not? Well any help would be appreciated. Extract the ports tarball, or obtain it via cvsup. Then cd /usr/ports/emulators/linux_base/ && make && make install Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Feb 15 8:56:34 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 C47F837B491 for ; Thu, 15 Feb 2001 08:56:32 -0800 (PST) Received: by mail.interchange.ca (Fastmailer, from userid 555) id E84D220CB; Thu, 15 Feb 2001 11:55:59 -0500 (EST) MIME-Version: 1.0 Message-Id: <3A8C0A1F.000187.61555@frodo.searchcanada.ca> Content-Type: Multipart/Mixed; boundary="------------Boundary-00=_BP5TYY2L3THOO49D7TH0" To: freebsd-alpha@freebsd.org Subject: Supported Controllers From: "Michael Richards" X-Fastmail-IP: 24.156.176.65 Date: Thu, 15 Feb 2001 11:55:59 -0500 (EST) Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org --------------Boundary-00=_BP5TYY2L3THOO49D7TH0 Content-Type: Text/Plain Content-Transfer-Encoding: 7bit >> So I see. I guess I will switch it around so the hard drives run >> from the onboard controller and the CD-Rom runs from the adaptec. > > Then you could not boot from CDROM (once the loader is fixed). Believe it or not, but of the 15-20 machines I've installed FreeBSD on, this was the first time I actually tried booting from the CD-ROM. In fact this is one of the first servers that actually has one. I think I'm going to put the boot hard drive on that controller and pull a DPT RAID controller off the shelf for the data drives. This brings up a short question, is anyone running a DPT controller? If so, how did you establish the array without any FreeBSD native support? Also, the problem I was describing before that prevented a rawhide boot from disk. Are we positive that this problem is with the boot loader? What would be the best idea for debugging this? Pepper it with a pile of debugging "printf" statements? -Michael _________________________________________________________________ http://fastmail.ca/ - Fast Free Web Email for Canadians --------------Boundary-00=_BP5TYY2L3THOO49D7TH0-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Feb 15 16:13:59 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from smtp03.primenet.com (smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (Postfix) with ESMTP id B8EEA37B491 for ; Thu, 15 Feb 2001 16:13:57 -0800 (PST) Received: (from daemon@localhost) by smtp03.primenet.com (8.9.3/8.9.3) id RAA25278; Thu, 15 Feb 2001 17:10:55 -0700 (MST) Received: from usr08.primenet.com(206.165.6.208) via SMTP by smtp03.primenet.com, id smtpdAAA3.aGmX; Thu Feb 15 17:10:44 2001 Received: (from tlambert@localhost) by usr08.primenet.com (8.8.5/8.8.5) id RAA10748; Thu, 15 Feb 2001 17:13:39 -0700 (MST) From: Terry Lambert Message-Id: <200102160013.RAA10748@usr08.primenet.com> Subject: Re: unaligned access To: Peter.Blok@inter.NL.net Date: Fri, 16 Feb 2001 00:13:39 +0000 (GMT) Cc: tlambert@primenet.com ('Terry Lambert'), gallatin@cs.duke.edu ('Andrew Gallatin'), freebsd-alpha@FreeBSD.ORG In-Reply-To: <000001c09746$af96e2a0$8a02a8c0@ntpc> from "Peter Blok" at Feb 15, 2001 12:59:00 PM 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 > Thanks for the hints. One big cause was the embedded alloc routines, that > doesn't do aligning. The next buffer allocated was unaligned, because the > previous size was unaligned. I haven't looked closely enough to the > structures. I also had one unaligned access in a varargs construction. > Haven't found the cause yet. Andrew is the "big guns" when it comes to Alpha work; I'm just someone on the sidelines. But remember that your problem is not the fixups themselves, but that the code does not operate in the presence of fixups, which it should. This implies the operational problem has nothing to do with the fixups, and is instead related to some other problem. My money is still on structure packing in the user space code; if you ensure that it isn't a problem by using "#pragma pack(1)", then I suspect your code will work, even though the console will still whine about unaligned access errors. 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 Thu Feb 15 16:42:58 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 CE7B737B491 for ; Thu, 15 Feb 2001 16:42:53 -0800 (PST) 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 LAA15265; Fri, 16 Feb 2001 11:42:49 +1100 (EDT) Received: from gsmx07.alcatel.com.au by cim.alcatel.com.au (PMDF V5.2-32 #37645) with ESMTP id <01K06DHJICMOO2JK4Y@cim.alcatel.com.au>; Fri, 16 Feb 2001 11:42:41 +1100 Received: (from jeremyp@localhost) by gsmx07.alcatel.com.au (8.11.1/8.11.1) id f1G0gj069192; Fri, 16 Feb 2001 11:42:45 +1100 (EST envelope-from jeremyp) Content-return: prohibited Date: Fri, 16 Feb 2001 11:42:44 +1100 From: Peter Jeremy Subject: Re: unaligned access In-reply-to: <200102160013.RAA10748@usr08.primenet.com>; from tlambert@primenet.com on Fri, Feb 16, 2001 at 12:13:39AM +0000 To: Terry Lambert Cc: Peter.Blok@inter.NL.net, freebsd-alpha@FreeBSD.ORG Mail-followup-to: Terry Lambert , Peter.Blok@inter.NL.net, freebsd-alpha@FreeBSD.ORG Message-id: <20010216114244.G90937@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: <000001c09746$af96e2a0$8a02a8c0@ntpc> <200102160013.RAA10748@usr08.primenet.com> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 2001-Feb-16 00:13:39 +0000, Terry Lambert wrote: >> Thanks for the hints. One big cause was the embedded alloc routines, that >> doesn't do aligning. The next buffer allocated was unaligned, because the >> previous size was unaligned. I haven't looked closely enough to the >> structures. I also had one unaligned access in a varargs construction. >> Haven't found the cause yet. > >But remember that your problem is not the fixups themselves, >but that the code does not operate in the presence of fixups, >which it should. That assumes that the code is not time critical and is not trying to perform atomic operations on non-aligned objects. Each fixup implies a trap to kernel mode and then emulating the instruction - this is at least 2 orders of magnitude slower than if the reference was aligned. If unaligned accesses are printed, that probably adds another couple more orders of magnitude slowdown (even graphical console I/O is glacial compared to instruction issue rates). Atomic accesses are inherently incompatible with non-aligned objects. I didn't keep the head of the this thread, but I've also found that "all the world's a VAX" (or at least an i386) is still alive and healthy in the freeware world. There's a _lot_ of code that assumes that ints, longs and pointers are all 32 bits and you can safely store a pointer in an int. Most of these assumptions are likely to lead to segmentation violations. Compiling your code with lots of warnings enabled can be very enlightening. Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Feb 15 17:12: 7 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from smtp03.primenet.com (smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (Postfix) with ESMTP id 2183037B4EC for ; Thu, 15 Feb 2001 17:12:04 -0800 (PST) Received: (from daemon@localhost) by smtp03.primenet.com (8.9.3/8.9.3) id SAA16110; Thu, 15 Feb 2001 18:09:01 -0700 (MST) Received: from usr08.primenet.com(206.165.6.208) via SMTP by smtp03.primenet.com, id smtpdAAAbyaOvF; Thu Feb 15 18:08:51 2001 Received: (from tlambert@localhost) by usr08.primenet.com (8.8.5/8.8.5) id SAA12619; Thu, 15 Feb 2001 18:11:48 -0700 (MST) From: Terry Lambert Message-Id: <200102160111.SAA12619@usr08.primenet.com> Subject: Re: unaligned access To: peter.jeremy@alcatel.com.au (Peter Jeremy) Date: Fri, 16 Feb 2001 01:10:40 +0000 (GMT) Cc: tlambert@primenet.com (Terry Lambert), Peter.Blok@inter.NL.net, freebsd-alpha@FreeBSD.ORG In-Reply-To: <20010216114244.G90937@gsmx07.alcatel.com.au> from "Peter Jeremy" at Feb 16, 2001 11:42:44 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 > >But remember that your problem is not the fixups themselves, > >but that the code does not operate in the presence of fixups, > >which it should. > > That assumes that the code is not time critical and is not trying to > perform atomic operations on non-aligned objects. Each fixup implies > a trap to kernel mode and then emulating the instruction - this is at > least 2 orders of magnitude slower than if the reference was aligned. > If unaligned accesses are printed, that probably adds another couple > more orders of magnitude slowdown (even graphical console I/O is > glacial compared to instruction issue rates). I've run PPP on a 7.14 MHz Amiga, so I'm going to guess that time criticality is not wht's breaking you. 8-). > Atomic accesses are inherently incompatible with non-aligned objects. Yes; but as PPP is a stream protocol, I'm also going to guess that it's no unlocked access that's shooting you. 8-). -- Both of the above said, I think that unaligned accesses in the code need to be fixed, if only so that the code is a godd example of correct architecture independent coding. But even if it weren't, and you rely on the fixup handler, the code _should_ be able to run correctly, if slowly. > I didn't keep the head of the this thread, but I've also found that > "all the world's a VAX" (or at least an i386) is still alive and > healthy in the freeware world. There's a _lot_ of code that assumes > that ints, longs and pointers are all 32 bits and you can safely > store a pointer in an int. Most of these assumptions are likely to > lead to segmentation violations. Compiling your code with lots of > warnings enabled can be very enlightening. Well, the alpha byte order makes that a correct assumption for originally x86 code running on an Alpha. I agree that byte order assumptions could make the code non-portable to other architectures (SPARC, 68k, MIPS, PPC [latter two, if processor is set to use that order]). As for object size, that could be your problem, too. I _know_ that packing could be an issue, since it was for me on some code (I didn't write it!) which I had to port to an Alpha, but it could be that object size is biting you. I think that we've so far punteded on dealing with the old sizeof(char)<=sizeof(short)<=sizeof(int)<=sizeof(long). That should leave only packing. There's a nice tricky array packing issue as well, which I've never been able to get a satisfactory answer as to what is done with it with "#pragma pack(1)", which I think only affects structure packing, and not array boundary packing. You can see this by: struct foo *foop; foop = NULL; printf( "a foo is this big: %d\n", sizeof(*foop)); printf( "a foo slot is this big: %d\n", &foop[1] - &foop[0]); MIPS was famous for packing these non-adjacently, and starting foop[1] on the next alignment boundary. I suspect that your PPP code doesn't have this, unless it's using a structure index of a header structure and doing an array reference instead of a sizeof() addition to the original char pointer, in order to get the next thing in the buffer, and cast it to the next type. The only thing I have left to say on this subject is that it you get to the point where you have data and a serial dump, and need help reconciling it, I can help put you into contact with the author of the mpd code; realize that it was developed on x86, so be sure you deal with the architectural issues before you ask for his help. 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 Fri Feb 16 9:14:49 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from atlrel2.hp.com (atlrel2.hp.com [156.153.255.202]) by hub.freebsd.org (Postfix) with ESMTP id 5664137B401 for ; Fri, 16 Feb 2001 09:14:41 -0800 (PST) Received: from udlkern.fc.hp.com (udlkern.fc.hp.com [15.1.52.48]) by atlrel2.hp.com (Postfix) with ESMTP id AE16B16FB for ; Fri, 16 Feb 2001 12:14:40 -0500 (EST) Received: from erdos (erdos.fc.hp.com [15.1.54.169]) by udlkern.fc.hp.com with SMTP (8.8.6 (PHNE_14041)/8.7.3 SMKit7.0) id KAA15169 for ; Fri, 16 Feb 2001 10:14:40 -0700 (MST) From: "Andrew M. Miklic" To: Subject: TGA driver available Date: Fri, 16 Feb 2001 10:14:39 -0700 Message-ID: <01c0983b$f195e980$0f0136a9@erdos.fc.hp.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_00B9_01C09801.45371180" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express Unix 5.00.2013.1312 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2013.1312 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This is a multi-part message in MIME format. ------=_NextPart_000_00B9_01C09801.45371180 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable All, I've managed to complete a somewhat-functional TGA driver, with the = help of Drew Gallatin and Thomas Crimi. I'm posting the location of the = tarball to this list for testing/perousal/comments/suggestions: = http://people.freebsd.org/~gallatin/TGA/tga.tar.gz The files are against 4.2R.... The card is known to work for BT485-based TGA step B and C cards = (both 8-, and somewhat less recently, 32-bit) in 640x480 and 1280x1024 = (any resolution _should_ work; there is also code to support the BT463, = but it is wholly untested). There is also code to support TGA2-based = cards, but it is also wholly untested aside from the probe and attach = routines (it still can be used in VGA mode for a console, however, and = mostly just needs a suitable X server to be useful)... The following are known functional deficiencies: 1) Color scheme for text is "off" -- for things like sysinstall, = text will look more "gangrene" than the "livid" that most people are = accustomed to... 2) Mouse does not work -- code is in place for it, and = vidcontrol and moused do not complain, but still no mouse pointer... 3) Font loading does not work -- again, code is in place, but = vidcontrol complains about /dev/ttyv0 not being configured... 4) X-vty switching -- X works, but switching between X and ttys = causes problems (like keyboard lockups)... In order of priority, I am looking at the above in reverse order, = but they will likely be completed in order as that is the ordering of = complexity for the tasks--any feedback on this prioritization would be = welcome... Thanks, Andrew Miklic ------=_NextPart_000_00B9_01C09801.45371180 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
All,
 
    I've managed to = complete a=20 somewhat-functional TGA driver, with the help of Drew Gallatin and = Thomas=20 Crimi.  I'm posting the location of the tarball to this list for=20 testing/perousal/comments/suggestions: http://= people.freebsd.org/~gallatin/TGA/tga.tar.gz
The=20 files are against 4.2R....
 
    The card is = known to work=20 for BT485-based TGA step B and C cards (both 8-, and somewhat less = recently,=20 32-bit) in 640x480 and 1280x1024 (any resolution _should_ work; there is = also=20 code to support the BT463, but it is wholly untested).  There is = also code=20 to support TGA2-based cards, but it is also wholly untested aside from = the probe=20 and attach routines (it still can be used in VGA mode for a console, = however,=20 and mostly just needs a suitable X server to be useful)...
 
    The following = are known=20 functional deficiencies:
 
    =     1) Color=20 scheme for text is "off" -- for things like sysinstall, text will look = more=20 "gangrene" than the "livid" that most people are accustomed = to...
 
    =     2) Mouse=20 does not work -- code is in place for it, and vidcontrol and moused do = not=20 complain, but still no mouse pointer...
 
    =     3) Font=20 loading does not work -- again, code is in place, but vidcontrol = complains about=20 /dev/ttyv0 not being configured...
 
    =     4) X-vty=20 switching -- X works, but switching between X and ttys causes problems = (like=20 keyboard lockups)...
 
    In order of = priority, I am=20 looking at the above in reverse order, but they will likely be completed = in=20 order as that is the ordering of complexity for the tasks--any feedback = on this=20 prioritization would be welcome...
 
Thanks,
Andrew=20 Miklic
------=_NextPart_000_00B9_01C09801.45371180-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Feb 16 12:45:19 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from altrade.nijmegen.inter.nl.net (altrade.nijmegen.inter.nl.net [193.67.237.6]) by hub.freebsd.org (Postfix) with ESMTP id 8A5C637B491 for ; Fri, 16 Feb 2001 12:45:14 -0800 (PST) Received: from ntpc by altrade.nijmegen.inter.nl.net via 1Cust33.tnt5.rtm1.nl.uu.net [213.116.104.33] with SMTP id VAA26837 (8.8.8/1.3); Fri, 16 Feb 2001 21:45:03 +0100 (MET) Reply-To: From: "Peter Blok" To: "'Terry Lambert'" Cc: "'Andrew Gallatin'" , Subject: RE: unaligned access Date: Fri, 16 Feb 2001 21:43:10 +0100 Message-ID: <000d01c09859$1383a600$8a02a8c0@ntpc> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2910.0) In-Reply-To: <200102160013.RAA10748@usr08.primenet.com> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Just an update. I have found two problems. 1) mpd-netgraph has its own alloc routine that doesn't roundup the size to a 64 bit boundary. Easy to fix. 2) The other one was in the byte swapping area. That one puzzled me for a while. It turns out to be a compiler issue. When you allocate a pointer to a 33 bit long locally on the stack, it is not always aligned. The allocation was not done in the scope of the function, but within another scope under a case statement. I have removed the definition to the scope of the function, to check its value with gdb and it suddenly worked! I'm not getting any errors any more, but it still doesn't work yet. The next problem looks related to the select system-call. Any know problems with it? Peter -----Original Message----- From: owner-freebsd-alpha@FreeBSD.ORG [mailto:owner-freebsd-alpha@FreeBSD.ORG]On Behalf Of Terry Lambert Sent: Friday, February 16, 2001 01:14 To: Peter.Blok@inter.NL.net Cc: 'Terry Lambert'; 'Andrew Gallatin'; freebsd-alpha@FreeBSD.ORG Subject: Re: unaligned access > Thanks for the hints. One big cause was the embedded alloc routines, that > doesn't do aligning. The next buffer allocated was unaligned, because the > previous size was unaligned. I haven't looked closely enough to the > structures. I also had one unaligned access in a varargs construction. > Haven't found the cause yet. Andrew is the "big guns" when it comes to Alpha work; I'm just someone on the sidelines. But remember that your problem is not the fixups themselves, but that the code does not operate in the presence of fixups, which it should. This implies the operational problem has nothing to do with the fixups, and is instead related to some other problem. My money is still on structure packing in the user space code; if you ensure that it isn't a problem by using "#pragma pack(1)", then I suspect your code will work, even though the console will still whine about unaligned access errors. 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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Feb 16 14:13:14 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from cicero2.cybercity.dk (cicero2.cybercity.dk [212.242.40.53]) by hub.freebsd.org (Postfix) with ESMTP id A51B037B491 for ; Fri, 16 Feb 2001 14:13:06 -0800 (PST) Received: from store07.cybercity.dk (store07.cybercity.dk [212.242.40.71]) by cicero2.cybercity.dk (Postfix) with ESMTP id 65895FFF32 for ; Fri, 16 Feb 2001 23:13:04 +0100 (CET) Received: from terminal1 (port14.ds1-amb.adsl.cybercity.dk [212.242.61.15]) by store07.cybercity.dk (8.9.3/8.9.3) with SMTP id XAA69761 for ; Fri, 16 Feb 2001 23:13:10 +0100 (CET) Message-ID: <000a01c09865$907c54c0$0200000a@terminal1> From: "Anders Rimmer" To: Subject: Installing FreeBSD 4.2 on my AlphaServer 1000 hangs... Date: Fri, 16 Feb 2001 23:12:33 +0100 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0007_01C0986D.F16C55C0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This is a multi-part message in MIME format. ------=_NextPart_000_0007_01C0986D.F16C55C0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi Everyone! I have recently purchased an AlphaServer 1000 5/300 with a total of 256 = megs of ram and 4x4.3 GB UW disks, CDROM-drive and a tape streamer. Now, I wanted only the best, so I decided to install FreeBSD 4.2 on the = beast, also 'coz I am purchasing another Alpha (600au) soon, which also = needs some installing. Well, the problem is, that when I type "boot dka600" in the srm console = (where dka600 is my scsi cdrom), FreeBSD boots, only to hang at "waiting = 15 seconds for scsi devices to settle"... What the h*** is going on? The scsi controllers are the 53c810 embedded on the mobo, where the = cdrom and tape streamer are installed, as scsi device 6 and 4 = respectively. Also, I have purchased a Symbios 53c875e pci card, and = some evedently matching cables from compaq, facilitating UW support on = the backpane (suposedly). I have no clue as to wheather this is a problem due to dual scsi = controllers, the cables from compaq not matching, the UW disks, my brain = or something completly third. System at a glance (for the visualy impared *S*): AlphaServer 1000 5/300 (not 1000a!) 256 megs of EDO ram (non ecc, 16x16meg modules) 4x4.3 UW rz29 disks Toshiba scsi cdrom IBM/Archive DAT DDS2 streamer Symbios 53x810 (embedded) Symbios 53x875e pci UW please advice, as I am somewhat frustrated over the whole she'bang! best regards, Anders Rimmer, Denmark PS. Please include email reply, as I am not yet a regular subscriber to = this list. ------=_NextPart_000_0007_01C0986D.F16C55C0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hi Everyone!
 
I have recently purchased an = AlphaServer 1000 5/300=20 with a total of 256 megs of ram and 4x4.3 GB UW disks, CDROM-drive and a = tape=20 streamer.
 
Now, I wanted only the best, so I = decided to=20 install FreeBSD 4.2 on the beast, also 'coz I am purchasing another = Alpha=20 (600au) soon, which also needs some installing.
 
Well, the problem is, that when I type = "boot=20 dka600" in the srm console (where dka600 is my scsi cdrom), FreeBSD = boots, only=20 to hang at "waiting 15 seconds for scsi devices to = settle"...
 
What the h*** is going on?
 
The scsi controllers are the 53c810 = embedded on the=20 mobo, where the cdrom and tape streamer are installed, as scsi device 6 = and 4=20 respectively. Also, I have purchased a Symbios 53c875e pci card, and = some=20 evedently matching cables from compaq, facilitating UW support on the = backpane=20 (suposedly).
 
I have no clue as to wheather this is a = problem due=20 to dual scsi controllers, the cables from compaq not matching, the = UW=20 disks, my brain or something completly third.
 
System at a glance (for the visualy = impared=20 *S*):
 
AlphaServer 1000 5/300 (not = 1000a!)
256 megs of EDO ram (non ecc, 16x16meg=20 modules)
4x4.3 UW rz29 disks
Toshiba scsi cdrom
IBM/Archive DAT DDS2 = streamer
Symbios 53x810 (embedded)
Symbios 53x875e pci UW
 
please advice, as I am somewhat = frustrated over the=20 whole she'bang!
 
best regards,
 
Anders Rimmer, Denmark
 
PS. Please include email reply, as I am = not yet a=20 regular subscriber to this list.
 
------=_NextPart_000_0007_01C0986D.F16C55C0-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Feb 16 14:17:15 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from cicero0.cybercity.dk (cicero0.cybercity.dk [212.242.40.52]) by hub.freebsd.org (Postfix) with ESMTP id DD25137B401 for ; Fri, 16 Feb 2001 14:17:13 -0800 (PST) Received: from store07.cybercity.dk (store07.cybercity.dk [212.242.40.71]) by cicero0.cybercity.dk (Postfix) with ESMTP id 7AAEE1029B1 for ; Fri, 16 Feb 2001 23:17:12 +0100 (CET) Received: from terminal1 (port14.ds1-amb.adsl.cybercity.dk [212.242.61.15]) by store07.cybercity.dk (8.9.3/8.9.3) with SMTP id XAA69843 for ; Fri, 16 Feb 2001 23:17:18 +0100 (CET) Message-ID: <001301c09866$24648ef0$0200000a@terminal1> From: "Anders Rimmer" To: Subject: subscribe Date: Fri, 16 Feb 2001 23:16:41 +0100 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0010_01C0986E.855DB7B0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This is a multi-part message in MIME format. ------=_NextPart_000_0010_01C0986E.855DB7B0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable ------=_NextPart_000_0010_01C0986E.855DB7B0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
 
------=_NextPart_000_0010_01C0986E.855DB7B0-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Feb 16 16: 5: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 07E7D37B491 for ; Fri, 16 Feb 2001 16:05:16 -0800 (PST) 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 TAA21996; Fri, 16 Feb 2001 19:05:11 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.2/8.9.1) id f1H04eY05031; Fri, 16 Feb 2001 19:04:40 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14989.49176.140334.190306@grasshopper.cs.duke.edu> Date: Fri, 16 Feb 2001 19:04:40 -0500 (EST) To: "Anders Rimmer" Cc: Subject: Re: Installing FreeBSD 4.2 on my AlphaServer 1000 hangs... In-Reply-To: <000a01c09865$907c54c0$0200000a@terminal1> References: <000a01c09865$907c54c0$0200000a@terminal1> 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 Anders Rimmer writes: > Hi Everyone! > > I have recently purchased an AlphaServer 1000 5/300 with a total of 256 megs of ram and 4x4.3 GB UW disks, CDROM-drive and a tape streamer. > > Now, I wanted only the best, so I decided to install FreeBSD 4.2 on the beast, also 'coz I am purchasing another Alpha (600au) soon, which also needs some installing. > > Well, the problem is, that when I type "boot dka600" in the srm console (where dka600 is my scsi cdrom), FreeBSD boots, only to hang at "waiting 15 seconds for scsi devices to settle"... > > What the h*** is going on? I wrote the platform support code for the AS1000 series & there's a serious bug in it which I corrected around DEC 6th (post 4.2-RELEASE). This bug affects AS1000 with ev5 cpus and AS1000A with ev4 cpus (I'd assumed that AS1000 was always ev4 and AS1000A was always ev5; this is not true). This bug would result in the behavour you are seeing. I suggest installing using http://people.freebsd.org/~gallatin/4.2.kern.flp and then upgrading to a very recent -stable after you've installed (I just MFC'ed the fix). Remember, the kernel that you're extracting from media during the install will be broken, so you need to mount the kern.flp floppy and copy off the working kernel after you install. Sorry! 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 Sat Feb 17 10:14: 2 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from 1upmc-msx1.isdip.upmc.edu (1upmc-msx1.isdip.upmc.edu [128.147.16.38]) by hub.freebsd.org (Postfix) with ESMTP id 03A2437B4EC for ; Sat, 17 Feb 2001 10:14:00 -0800 (PST) Received: by 1upmc-msx1.isdip.upmc.edu with Internet Mail Service (5.5.2650.21) id <1CSFQV3F>; Sat, 17 Feb 2001 13:13:17 -0500 Message-ID: From: "Person, Roderick" To: "'freebsd-alpha@FreeBSD.ORG'" Subject: Alpha AXPpci external modem problems Date: Sat, 17 Feb 2001 13:13:10 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C0990D.4C8E07D8" Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01C0990D.4C8E07D8 Content-Type: text/plain I can get my external modem to dial on my alpha. I get a the terminal ready and clear to send light to light but no dial tone. If have it set on com 1. when I use com 2 I get delink errors. I've read the mail archives and see that this is some what common, but aside for rebuilding the kernel I don't see any answers. are there? I have built countless kernals on i386 freebsd but i'm not sure if i'm read to do so on the alpha, being i don't know the hardware as well, being I have only worked with them for a week now. ------_=_NextPart_001_01C0990D.4C8E07D8 Content-Type: text/html Content-Transfer-Encoding: quoted-printable Alpha AXPpci external modem problems

I can get my external modem to dial on my alpha. I = get a the terminal ready and clear to send light to light but no dial = tone. If have it set on com 1. when I use com 2 I get delink errors. = I've read the mail archives and see that this is some what common, but = aside for rebuilding the kernel I don't see any answers. are there? I = have built countless kernals on i386 freebsd but i'm not sure if i'm = read to do so on the alpha, being i don't know the hardware as well, = being I have only worked with them for a week now.

------_=_NextPart_001_01C0990D.4C8E07D8-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message