From owner-freebsd-alpha Sun Mar 25 0:57:48 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from femail11.sdc1.sfba.home.com (femail11.sdc1.sfba.home.com [24.0.95.107]) by hub.freebsd.org (Postfix) with ESMTP id 4DC9537B71E for ; Sun, 25 Mar 2001 00:57:45 -0800 (PST) (envelope-from craig-burgess@home.net) Received: from tiger ([24.0.178.21]) by femail11.sdc1.sfba.home.com (InterMail vM.4.01.03.20 201-229-121-120-20010223) with SMTP id <20010325085744.GODE26203.femail11.sdc1.sfba.home.com@tiger>; Sun, 25 Mar 2001 00:57:44 -0800 From: "Craig Burgess" To: Cc: Subject: RE: consoles... Date: Sun, 25 Mar 2001 00:58:27 -0800 Message-ID: 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 IMO, Build 9.0.2416 (9.0.2911.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 In-Reply-To: Importance: Normal Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Actually it (console, getty) does not work fine in 4.2 - that is when i stumbled across the anomaly on PC164 and tried to get help for "a problem." Apparently that wasn't enough to raise the alsrm. I lack the expertise to know when i've created a problem for myself and when it really ain't my fault. sorry. craig burgess -----Original Message----- From: owner-freebsd-alpha@FreeBSD.ORG [mailto:owner-freebsd-alpha@FreeBSD.ORG]On Behalf Of Matthew Jacob Sent: Saturday, March 24, 2001 5:53 PM To: Mike Smith Cc: David O'Brien; Andrew Gallatin; alpha@FreeBSD.ORG Subject: Re: consoles... On Sat, 24 Mar 2001, Mike Smith wrote: > > > > # If console is marked "insecure", then init will ask for the root password > > # when going to single-user mode. > > console none unknown off secure > > > > I sure wish I knew what happened here, but at some point past 4.2, > > /dev/console got broken for Alpha 8200s. > ... > > What really pisses me off about this is that I worked goddamned hard to fix > > this back in 4.1. > > Actually, what you did back then was fuck up everyone that wasn't using > zs0. Actually, no, that's not quite true. I did get things working for /dev/console properly. See below... If I 'fucked it up' I sure don't recall hearing from you about it. > > Does anyone have a notion as to what complete dufus managed to break this for > > 4.3? > > Whoever took the zs0 entry out of /etc/ttys. Please read my mail, Mike. It works fine in 4.2: ----- FreeBSD/alpha (ray.nas.nasa.gov) (console) login: ---- In order for it to work now in 4,3, we'll have to add back a zs0- which at this stage in the release is probably an okay workaround (albeit disappointing). -matt 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 Mar 25 5:22:53 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 E3C5B37B719; Sun, 25 Mar 2001 05:22:50 -0800 (PST) (envelope-from wkb@freebie.demon.nl) Received: from [212.238.54.101] (helo=freebie.demon.nl) by post.mail.nl.demon.net with smtp (Exim 3.14 #4) id 14hATp-0002zb-00; Sun, 25 Mar 2001 13:22:49 +0000 Received: (from wkb@localhost) by freebie.demon.nl (8.11.3/8.11.2) id f2PDPRG95493; Sun, 25 Mar 2001 15:25:27 +0200 (CEST) (envelope-from wkb) Date: Sun, 25 Mar 2001 15:25:27 +0200 From: Wilko Bulte To: "David O'Brien" Cc: Matthew Jacob , alpha@freebsd.org Subject: Re: consoles... Message-ID: <20010325152527.D95252@freebie.demon.nl> References: <20010324180411.A7556@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20010324180411.A7556@dragon.nuxi.com>; from obrien@freebsd.org on Sat, Mar 24, 2001 at 06:04:11PM -0800 X-OS: FreeBSD 4.3-BETA X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sat, Mar 24, 2001 at 06:04:11PM -0800, David O'Brien wrote: > On Sat, Mar 24, 2001 at 05:39:57PM -0800, Matthew Jacob wrote: > > I sure wish I knew what happened here, but at some point past 4.2, > > /dev/console got broken for Alpha 8200s. > > This past week, I committed a change that removed the getty off of the > console device, and put one on ttyd0. This was due to people saying they > were getting garbage on their consoles. I never saw this on my > Miata-MX5, or AS250. But others said they did. Andrew (and Mike Smith) I saw that on Multia, MX5 and DS20. Don't shoot me.. -- | / o / / _ Arnhem, The Netherlands email: wilko@freebsd.org |/|/ / / /( (_) Bulte http://www.freebsd.org http://www.nlfug.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sun Mar 25 5:26:28 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 EB4FF37B71B; Sun, 25 Mar 2001 05:26:25 -0800 (PST) (envelope-from wkb@freebie.demon.nl) Received: from [212.238.54.101] (helo=freebie.demon.nl) by post.mail.nl.demon.net with smtp (Exim 3.14 #2) id 14hAWr-000711-00; Sun, 25 Mar 2001 13:25:57 +0000 Received: (from wkb@localhost) by freebie.demon.nl (8.11.3/8.11.2) id f2PDSYP95509; Sun, 25 Mar 2001 15:28:34 +0200 (CEST) (envelope-from wkb) Date: Sun, 25 Mar 2001 15:28:34 +0200 From: Wilko Bulte To: Matthew Jacob Cc: Mike Smith , obrien@freebsd.org, Andrew Gallatin , alpha@freebsd.org Subject: Re: consoles... Message-ID: <20010325152833.E95252@freebie.demon.nl> References: <200103250211.f2P2BSA02821@mass.dis.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from mjacob@feral.com on Sat, Mar 24, 2001 at 07:25:41PM -0800 X-OS: FreeBSD 4.3-BETA X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sat, Mar 24, 2001 at 07:25:41PM -0800, Matthew Jacob wrote: > It'd be really nice to 'fix' this for 4.3, but I would totally understand that > this is not something to delay the release for- it's an easy RTF to fix this > from single user after having installed an 8200 (like, is there anyone *else* > out there who has 8200s to try other than me or Wilko?). And 'my' 8400 has yet to run FreeBSD in the first place. It seems to be a bit too different from the Ames boxes. I will throw the 4.3beta CD in it to see what happens. Hopefully tomorrow. Wilko -- | / o / / _ Arnhem, The Netherlands email: wilko@freebsd.org |/|/ / / /( (_) Bulte http://www.freebsd.org http://www.nlfug.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sun Mar 25 8: 2: 1 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 84B8A37B71A for ; Sun, 25 Mar 2001 08:01:55 -0800 (PST) (envelope-from michael@fastmail.ca) Received: by mail.interchange.ca (Fastmailer, from userid 555) id A030120B9; Sun, 25 Mar 2001 11:01:05 -0500 (EST) MIME-Version: 1.0 Message-Id: <3ABE1641.0001E1.51316@frodo.searchcanada.ca> Content-Type: Multipart/Mixed; boundary="------------Boundary-00=_THGRGHCR9K5OO49D7TH0" To: freebsd-alpha@FreeBSD.ORG Subject: What is src/sys/boot/arc/loader? From: "Michael Richards" X-Fastmail-IP: 24.43.130.237 Date: Sun, 25 Mar 2001 11:01:05 -0500 (EST) Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org --------------Boundary-00=_THGRGHCR9K5OO49D7TH0 Content-Type: Text/Plain Content-Transfer-Encoding: 7bit I'm working on narrowing down the problem with the loader and I came across something in the source. When I built it, I noticed that there was a loader.exe file built in: src/sys/boot/arc/loader/loader.exe file loader.exe loader.exe: MS Windows COFF Alpha object file It's a windows file... This strikes me odd. Does this mean that FreeBSD can be booted using AlphaBIOS (which incidentally supports the Adaptec SCSI card that the non-boot disks are on)? -Michael _________________________________________________________________ http://fastmail.ca/ - Fast Free Web Email for Canadians --------------Boundary-00=_THGRGHCR9K5OO49D7TH0-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sun Mar 25 8:15:44 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from mail.inka.de (quechua.inka.de [212.227.14.2]) by hub.freebsd.org (Postfix) with ESMTP id 8917437B71A for ; Sun, 25 Mar 2001 08:15:39 -0800 (PST) (envelope-from daemon@mips.inka.de) Received: from kemoauc.mips.inka.de (uucp@) by mail.inka.de with local-bsmtp id 14hDB3-0003SB-00; Sun, 25 Mar 2001 18:15:37 +0200 Received: (from daemon@localhost) by kemoauc.mips.inka.de (8.11.3/8.11.1) id f2PFbGH01153 for freebsd-alpha@freebsd.org; Sun, 25 Mar 2001 17:37:16 +0200 (CEST) (envelope-from daemon) From: naddy@mips.inka.de (Christian Weisgerber) Subject: Re: Unaligned access in vfs_object_create() Date: Sun, 25 Mar 2001 15:37:15 +0000 (UTC) Message-ID: <99l3bb$12f$1@kemoauc.mips.inka.de> References: <20010311164308.A3774@kemoauc.mips.inka.de> Originator: naddy@mips.inka.de (Christian Weisgerber) To: freebsd-alpha@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Christian Weisgerber wrote: > Top of the tree, ca. March 10. March 24. > My custom kernel suffers an unaligned access fault in vfs_object_create() > at the end of kernel startup--presumably when attempting to mount > the root or devfs filesystem. > > The GENERIC kernel does not have this problem. -- Christian "naddy" Weisgerber naddy@mips.inka.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sun Mar 25 9:43:23 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 5E1A637B719 for ; Sun, 25 Mar 2001 09:43:20 -0800 (PST) (envelope-from wkb@freebie.demon.nl) Received: from [212.238.54.101] (helo=freebie.demon.nl) by post.mail.nl.demon.net with smtp (Exim 3.14 #4) id 14hEXu-0007b0-00; Sun, 25 Mar 2001 17:43:19 +0000 Received: (from wkb@localhost) by freebie.demon.nl (8.11.3/8.11.2) id f2PHjeG09385; Sun, 25 Mar 2001 19:45:40 +0200 (CEST) (envelope-from wkb) Date: Sun, 25 Mar 2001 19:45:40 +0200 From: Wilko Bulte To: Michael Richards Cc: freebsd-alpha@freebsd.org Subject: Re: What is src/sys/boot/arc/loader? Message-ID: <20010325194540.A9351@freebie.demon.nl> References: <3ABE1641.0001E1.51316@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: <3ABE1641.0001E1.51316@frodo.searchcanada.ca>; from michael@fastmail.ca on Sun, Mar 25, 2001 at 11:01:05AM -0500 X-OS: FreeBSD 4.3-BETA X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sun, Mar 25, 2001 at 11:01:05AM -0500, Michael Richards wrote: > I'm working on narrowing down the problem with the loader and I came > across something in the source. When I built it, I noticed that there > was a loader.exe file built in: src/sys/boot/arc/loader/loader.exe > > file loader.exe > loader.exe: MS Windows COFF Alpha object file > > It's a windows file... > > This strikes me odd. Does this mean that FreeBSD can be booted using > AlphaBIOS (which incidentally supports the Adaptec SCSI card that the > non-boot disks are on)? No. This is a work-in-progress thingy. There is still a lot missing, not in the last place the PAL-code issue. See the mailing list archives. 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 Sun Mar 25 10:14:40 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 9D4CB37B719 for ; Sun, 25 Mar 2001 10:14:38 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.3/8.11.1) id f2PIEc859009 for freebsd-alpha@freebsd.org; Sun, 25 Mar 2001 10:14:38 -0800 (PST) (envelope-from obrien) Date: Sun, 25 Mar 2001 10:14:37 -0800 From: "David O'Brien" To: freebsd-alpha@freebsd.org Subject: Re: What is src/sys/boot/arc/loader? Message-ID: <20010325101437.A58992@dragon.nuxi.com> Reply-To: obrien@freebsd.org References: <3ABE1641.0001E1.51316@frodo.searchcanada.ca> <20010325194540.A9351@freebie.demon.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010325194540.A9351@freebie.demon.nl>; from wkb@freebie.demon.nl on Sun, Mar 25, 2001 at 07:45:40PM +0200 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sun, Mar 25, 2001 at 07:45:40PM +0200, Wilko Bulte wrote: > > This strikes me odd. Does this mean that FreeBSD can be booted using > > AlphaBIOS (which incidentally supports the Adaptec SCSI card that the > > non-boot disks are on)? > > No. This is a work-in-progress thingy. There is still a lot missing, not in > the last place the PAL-code issue. See the mailing list archives. Would anyone mind if I take this out of the build? -- -- David (obrien@FreeBSD.org) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sun Mar 25 11: 5: 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 98D7A37B719; Sun, 25 Mar 2001 11:04:57 -0800 (PST) (envelope-from wkb@freebie.demon.nl) Received: from [212.238.54.101] (helo=freebie.demon.nl) by post.mail.nl.demon.net with smtp (Exim 3.14 #2) id 14hFor-0001Um-00; Sun, 25 Mar 2001 19:04:53 +0000 Received: (from wkb@localhost) by freebie.demon.nl (8.11.3/8.11.2) id f2PJ7IK10067; Sun, 25 Mar 2001 21:07:18 +0200 (CEST) (envelope-from wkb) Date: Sun, 25 Mar 2001 21:07:18 +0200 From: Wilko Bulte To: "David O'Brien" Cc: freebsd-alpha@freebsd.org Subject: Re: What is src/sys/boot/arc/loader? Message-ID: <20010325210718.C9840@freebie.demon.nl> References: <3ABE1641.0001E1.51316@frodo.searchcanada.ca> <20010325194540.A9351@freebie.demon.nl> <20010325101437.A58992@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20010325101437.A58992@dragon.nuxi.com>; from obrien@freebsd.org on Sun, Mar 25, 2001 at 10:14:37AM -0800 X-OS: FreeBSD 4.3-BETA X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sun, Mar 25, 2001 at 10:14:37AM -0800, David O'Brien wrote: > On Sun, Mar 25, 2001 at 07:45:40PM +0200, Wilko Bulte wrote: > > > This strikes me odd. Does this mean that FreeBSD can be booted using > > > AlphaBIOS (which incidentally supports the Adaptec SCSI card that the > > > non-boot disks are on)? > > > > No. This is a work-in-progress thingy. There is still a lot missing, not in > > the last place the PAL-code issue. See the mailing list archives. > > Would anyone mind if I take this out of the build? Please do. It only generates confusion/FAQs etc... -- | / o / / _ Arnhem, The Netherlands email: wilko@freebsd.org |/|/ / / /( (_) Bulte http://www.freebsd.org http://www.nlfug.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sun Mar 25 15:24:12 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 2C41937B71B for ; Sun, 25 Mar 2001 15:24:10 -0800 (PST) (envelope-from michael@fastmail.ca) Received: by mail.interchange.ca (Fastmailer, from userid 555) id 07E3320DA; Sun, 25 Mar 2001 18:23:18 -0500 (EST) MIME-Version: 1.0 Message-Id: <3ABE7DE5.0000ED.48828@frodo.searchcanada.ca> Content-Type: Multipart/Mixed; boundary="------------Boundary-00=_TY0SCKICC5GNTT4D7TH0" To: freebsd-alpha@freebsd.org Subject: Boot Loader Progress... From: "Michael Richards" X-Fastmail-IP: 24.43.130.237 Date: Sun, 25 Mar 2001 18:23:18 -0500 (EST) Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org --------------Boundary-00=_TY0SCKICC5GNTT4D7TH0 Content-Type: Text/Plain Content-Transfer-Encoding: 7bit Hi. Just wanted to report a small amount of progress on the boot loader issues for my AS1200. I'm working with a hacked up boot loader that has debugging added to it so I can see where the loader is failing. I have been taking my compiled version of the boot loader and copying it onto a boot floppy and booting from that. Here is what I found so far... The loader fails when it calls the "include" function to load the file: /boot/loader.rc I originally thought it was a problem with reading the data, but now I believe the call to "open" in the include function in common/interp.c is never returning. I am going to descent into the depths of libstand to insert debugging and see if I can locate the exact point of failure. Does anyone have documentation on how to interface with the alpha bios to perform low level things such as reading blocks of data? I would like to verify that calls are being made properly. Finally, assuming that I do get this problem fixed, is there anyone specifically that I should be sending patches to? -Michael _________________________________________________________________ http://fastmail.ca/ - Fast Free Web Email for Canadians --------------Boundary-00=_TY0SCKICC5GNTT4D7TH0-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sun Mar 25 15:41:26 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 5FFFE37B719 for ; Sun, 25 Mar 2001 15:41:24 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.3/8.11.1) id f2PNepf68880; Sun, 25 Mar 2001 15:40:51 -0800 (PST) (envelope-from obrien) Date: Sun, 25 Mar 2001 15:40:50 -0800 From: "David O'Brien" To: Michael Richards Cc: freebsd-alpha@freebsd.org Subject: Re: Boot Loader Progress... Message-ID: <20010325154050.A68860@dragon.nuxi.com> Reply-To: obrien@freebsd.org References: <3ABE7DE5.0000ED.48828@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: <3ABE7DE5.0000ED.48828@frodo.searchcanada.ca>; from michael@fastmail.ca on Sun, Mar 25, 2001 at 06:23:18PM -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 Sun, Mar 25, 2001 at 06:23:18PM -0500, Michael Richards wrote: > Finally, assuming that I do get this problem fixed, is there anyone > specifically that I should be sending patches to? Yes, freebsd-alpha@freebsd.org -- TRUST ME, many of us will try them and get them committed if they help the situation. -- -- David (obrien@FreeBSD.org) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sun Mar 25 16:34: 9 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 D975537B71B; Sun, 25 Mar 2001 16:34:06 -0800 (PST) (envelope-from michael@fastmail.ca) Received: by mail.interchange.ca (Fastmailer, from userid 555) id 08AF520C6; Sun, 25 Mar 2001 19:33:14 -0500 (EST) MIME-Version: 1.0 Message-Id: <3ABE8E49.000033.08638@frodo.searchcanada.ca> Content-Type: Multipart/Mixed; boundary="------------Boundary-00=_D74S6RB00M3NTT4D7TH0" To: obrien@freebsd.org Subject: Re: Boot Loader Progress... Cc: freebsd-alpha@freebsd.org From: "Michael Richards" X-Fastmail-IP: 24.43.130.237 Date: Sun, 25 Mar 2001 19:33:14 -0500 (EST) Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org --------------Boundary-00=_D74S6RB00M3NTT4D7TH0 Content-Type: Text/Plain Content-Transfer-Encoding: 7bit > Yes, freebsd-alpha@freebsd.org -- TRUST ME, many of us will try > them and get them committed if they help the situation Any ideas on the history of this bug? Has the loader always been broken? Does it work on any platform or just not my AS1200? It must work on some platforms, otherwise nobody would have a booting version of FreeBSD. Since I dd'd the 2.88mb floppy to the hard drive and it still won't work, I assume that I'm an unlucky one. Since open is not working, it may be in the low level block read code for the filesystem, or it might be some mis-ported ufs code. Has anyone been able to get this loader to use the tftp loader to net- boot? -Michael _________________________________________________________________ http://fastmail.ca/ - Fast Free Web Email for Canadians --------------Boundary-00=_D74S6RB00M3NTT4D7TH0-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sun Mar 25 17: 6:27 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from wantadilla.lemis.com (wantadilla.lemis.com [192.109.197.80]) by hub.freebsd.org (Postfix) with ESMTP id BE83937B718; Sun, 25 Mar 2001 17:06:24 -0800 (PST) (envelope-from grog@lemis.com) Received: by wantadilla.lemis.com (Postfix, from userid 1004) id 5ADE56A90D; Mon, 26 Mar 2001 10:36:22 +0930 (CST) Date: Mon, 26 Mar 2001 10:36:22 +0930 From: Greg Lehey To: John Baldwin Cc: Mike Smith , freebsd-alpha@FreeBSD.org, leclercn@videotron.ca Subject: Re: dev_t size mismatch kernel / userland Message-ID: <20010326103622.H40349@wantadilla.lemis.com> References: <200103240509.f2O59L900618@mass.dis.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from jhb@FreeBSD.org on Fri, Mar 23, 2001 at 09:45:12PM -0800 Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Friday, 23 March 2001 at 21:45:12 -0800, John Baldwin wrote: > > On 24-Mar-01 Mike Smith wrote: >>> Already tried vinum, works fine after modification of dev_t to >>> u_int64_t. I'll change it to uintptr_t tough (cleaner). Hope this gets >>> fixed! >> >> This is wrong. In the kernel or in a module, dev_t is an opaque type. >> In userspace, you use udev_t, not dev_t. >> >> It sounds like vinum is failing to perform the required conversions when >> exchanging a dev_t with userland, and the correct fix is going to be to >> add these. > > struct drive, struct plex, etc. are shared between userland and the kernel. It > looks like they need to use a udev_t, and the kernel will always have to do > udev2dev() before using them. Either that or don't export the structures to > userland. I already had code under way to export expurgated versions of these structs. But that's a separate issue. It seems to me that if dev_t is even visible in userland header files, it should be correct. We should either fix it or remove it. Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sun Mar 25 17:47:58 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 40C7137B718 for ; Sun, 25 Mar 2001 17:47:52 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id UAA05254; Sun, 25 Mar 2001 20:47:51 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.3/8.9.1) id f2Q1lLr66017; Sun, 25 Mar 2001 20:47:21 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15038.40872.853207.953809@grasshopper.cs.duke.edu> Date: Sun, 25 Mar 2001 20:47:20 -0500 (EST) To: "Michael Richards" Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: Boot Loader Progress... In-Reply-To: <3ABE7DE5.0000ED.48828@frodo.searchcanada.ca> References: <3ABE7DE5.0000ED.48828@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: > > Does anyone have documentation on how to interface with the alpha > bios to perform low level things such as reading blocks of data? I > would like to verify that calls are being made properly. 'Alpha Architecture Reference Manual, Third Edition' By Sites, Richard L. / Witek, Richard T. I think the calls are correct, but we may be making them in a way that tickles bugs on this platform's SRM console implementation. Eg, we do something which is technically legal, but which no other bootloader does, so it happens not to work. > Finally, assuming that I do get this problem fixed, is there anyone > specifically that I should be sending patches to? I'm sure if you mailed them to this list, all of us comitters on this list would be falling all over each other to commit them. ;-) Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sun Mar 25 17:53:45 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 22DB737B719 for ; Sun, 25 Mar 2001 17:53:43 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id UAA05304; Sun, 25 Mar 2001 20:53:42 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.3/8.9.1) id f2Q1rCZ66026; Sun, 25 Mar 2001 20:53: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: <15038.41224.595755.369957@grasshopper.cs.duke.edu> Date: Sun, 25 Mar 2001 20:53:12 -0500 (EST) To: "Michael Richards" Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: Boot Loader Progress... In-Reply-To: <3ABE8E49.000033.08638@frodo.searchcanada.ca> References: <3ABE8E49.000033.08638@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: > > Yes, freebsd-alpha@freebsd.org -- TRUST ME, many of us will try > > them and get them committed if they help the situation > > Any ideas on the history of this bug? > Has the loader always been broken? > Does it work on any platform or just not my AS1200? It's always worked on all platforms except the rawhide (AS1200, AS4000, AS4100 and the "ultimate workstation" & whitebox versions of the former). Well, maybe that's too generous; the loader has had serious bugs before.. Let's just say that _this_ bug has never been seen on any other platform and has always been seen on this platform. <...> > for the filesystem, or it might be some mis-ported ufs code. Has > anyone been able to get this loader to use the tftp loader to net- > boot? Yes, that's how most new platforms get support. I can't imagine creating boot floppies for each boot attempt on a brand new platform that I don't have proper documentation for. Ugh. Diskless booting is how I do most of my installs here too. I'm not sure if anybody has netbooted a rawhide though... Matt? Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Mar 26 2: 0:51 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 6D3C137B719 for ; Mon, 26 Mar 2001 02:00:49 -0800 (PST) (envelope-from postmaster@freebie.demon.nl) Received: from [195.11.243.26] (helo=Debug) by post.mail.nl.demon.net with smtp (Exim 3.14 #4) id 14hTns-0001rJ-00 for freebsd-alpha@freebsd.org; Mon, 26 Mar 2001 10:00:48 +0000 To: freebsd-alpha@freebsd.org From: postmaster@freebie.demon.nl Subject: Lynx (AS2100A) is a go on 4.3 Date: Mon, 26 Mar 2001 10:00:48 GMT X-Mailer: www.webmail.nl.demon.net X-Sender: postmaster@wkb@freebie.demon.nl X-Originating-IP: 161.114.88.76 Message-Id: Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org FYI: Just completed a successful install on a AS2100A (dual CPU; 256MB) with the 19032001BETA CD. As an added bonus the OS was installed on a RAID5 Mylex 960 (RAIDarray230 in DEC-speak) which appears to work OK as well. Wilko To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Mar 26 2: 4:48 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from grafin.fujimori.cache.waseda.ac.jp (grafin.fujimori.cache.waseda.ac.jp [133.9.152.154]) by hub.freebsd.org (Postfix) with ESMTP id 380FE37B71B for ; Mon, 26 Mar 2001 02:04:46 -0800 (PST) (envelope-from fujimori@grafin.fujimori.cache.waseda.ac.jp) Received: from grafin.fujimori.cache.waseda.ac.jp (fujimori@localhost [127.0.0.1]) by grafin.fujimori.cache.waseda.ac.jp (8.9.3/3.7W) with ESMTP id TAA15070; Mon, 26 Mar 2001 19:04:30 +0900 Message-Id: <200103261004.TAA15070@grafin.fujimori.cache.waseda.ac.jp> To: postmaster@freebie.demon.nl Cc: freebsd-alpha@freebsd.org Subject: Re: Lynx (AS2100A) is a go on 4.3 In-reply-to: Your message of "Mon, 26 Mar 2001 10:00:48 GMT." Date: Mon, 26 Mar 2001 19:04:30 +0000 From: Yoriaki FUJIMORI Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Oh! Do you mean dual CPUs are working fine? Yoriaki Fujimori To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Mar 26 3: 9: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 313F037B71A for ; Mon, 26 Mar 2001 03:09:07 -0800 (PST) (envelope-from msmith@mass.dis.org) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.2/8.11.2) with ESMTP id f2Q7cY601365; Sun, 25 Mar 2001 23:38:35 -0800 (PST) (envelope-from msmith@mass.dis.org) Message-Id: <200103260738.f2Q7cY601365@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: "Michael Richards" Cc: freebsd-alpha@freebsd.org Subject: Re: Boot Loader Progress... In-reply-to: Your message of "Sun, 25 Mar 2001 18:23:18 EST." <3ABE7DE5.0000ED.48828@frodo.searchcanada.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 25 Mar 2001 23:38:33 -0800 From: Mike Smith Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > The loader fails when it calls the "include" function to load the > file: /boot/loader.rc > I originally thought it was a problem with reading the data, but now > I believe the call to "open" in the include function in > common/interp.c is never returning. I am going to descent into the > depths of libstand to insert debugging and see if I can locate the > exact point of failure. Don't bother with libstand, go straight to the libalpha code and see if we're actually calling the SRM 'open' function more than once. I suspect that SRM may have issues with that. > Does anyone have documentation on how to interface with the alpha > bios to perform low level things such as reading blocks of data? I > would like to verify that calls are being made properly. The SRM ("bios") implementations typically have issues that are interpretation; they comply with the specification, but fail in areas outside it (since it's pretty vague about some of the assumptions that one can or can't make). > Finally, assuming that I do get this problem fixed, is there anyone > specifically that I should be sending patches to? As was previously mentioned, the freebsd-alpha list is probably the best place. -- ... 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 Mon Mar 26 3:33:11 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from mass.dis.org (mass.dis.org [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id 9B57737B71A for ; Mon, 26 Mar 2001 03:33:09 -0800 (PST) (envelope-from msmith@mass.dis.org) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.2/8.11.2) with ESMTP id f2QBWTh03139; Mon, 26 Mar 2001 03:32:29 -0800 (PST) (envelope-from msmith@mass.dis.org) Message-Id: <200103261132.f2QBWTh03139@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: postmaster@freebie.demon.nl Cc: freebsd-alpha@freebsd.org Subject: Re: Lynx (AS2100A) is a go on 4.3 In-reply-to: Your message of "Mon, 26 Mar 2001 10:00:48 GMT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 26 Mar 2001 03:32:29 -0800 From: Mike Smith Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > ... As an added bonus the OS was installed on a RAID5 > Mylex 960 (RAIDarray230 in DEC-speak) which appears to work OK as well. Thanks for the status report here. -- ... 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 Mon Mar 26 3:51:54 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 768CF37B718 for ; Mon, 26 Mar 2001 03:51:52 -0800 (PST) (envelope-from wkb@freebie.demon.nl) Received: from [195.11.243.26] (helo=Debug) by post.mail.nl.demon.net with smtp (Exim 3.14 #4) id 14hVXI-0007eZ-00; Mon, 26 Mar 2001 11:51:48 +0000 To: Yoriaki FUJIMORI , postmaster@freebie.demon.nl, freebsd-alpha@freebsd.org From: wkb@freebie.demon.nl Subject: Re: Lynx (AS2100A) is a go on 4.3 Date: Mon, 26 Mar 2001 11:51:48 GMT X-Mailer: www.webmail.nl.demon.net X-Sender: postmaster@wkb@freebie.demon.nl X-Originating-IP: 161.114.88.73 Message-Id: Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Oh! > Do you mean dual CPUs are working fine? No, that is not what I mean. SMP is currently not available on Alpha. I just listed my hardware config. Wilko > > Yoriaki Fujimori > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-alpha" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Mar 26 3:56:28 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 7CE4D37B719; Mon, 26 Mar 2001 03:56:26 -0800 (PST) (envelope-from wkb@freebie.demon.nl) Received: from [195.11.243.26] (helo=Debug) by post.mail.nl.demon.net with smtp (Exim 3.14 #4) id 14hVbl-0007u2-00; Mon, 26 Mar 2001 11:56:25 +0000 To: Mike Smith , postmaster@freebie.demon.nl, freebsd-alpha@freebsd.org From: wkb@freebie.demon.nl Subject: Re: Lynx (AS2100A) is a go on 4.3 Date: Mon, 26 Mar 2001 11:56:25 GMT X-Mailer: www.webmail.nl.demon.net X-Sender: postmaster@wkb@freebie.demon.nl X-Originating-IP: 161.114.88.73 Message-Id: Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > ... As an added bonus the OS was installed on a RAID5 > > Mylex 960 (RAIDarray230 in DEC-speak) which appears to work OK as well. > > Thanks for the status report here. To be exact, this is what I have running: mlx0: port 0x5400-0x547f irq 48 at device 6.0 o n pci2 mlx0: DAC960P/PD, 3 channels, firmware 2.42-0-00, 4MB RAM mlxd0: on mlx0 mlxd0: 4014MB (8220672 sectors) RAID 5 (online) It is doing a buildworld now BTW Wilko To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Mar 26 6:16: 9 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 F0DE137B718 for ; Mon, 26 Mar 2001 06:16:06 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id JAA14273; Mon, 26 Mar 2001 09:16:06 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.3/8.9.1) id f2QEFac67287; Mon, 26 Mar 2001 09:15: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: <15039.20232.348803.150449@grasshopper.cs.duke.edu> Date: Mon, 26 Mar 2001 09:15:36 -0500 (EST) To: wkb@freebie.demon.nl Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: Lynx (AS2100A) is a go on 4.3 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 postmaster@freebie.demon.nl writes: > FYI: > > Just completed a successful install on a AS2100A (dual CPU; 256MB) > with the 19032001BETA CD. As an added bonus the OS was installed on a RAID5 > Mylex 960 (RAIDarray230 in DEC-speak) which appears to work OK as well. Woo-hoo! Glad to hear somebody finally tested my MFC of the lynx code ;) Let's everybody thank Clem Cole & Compaq for getting me the docs I needed to get the Lynx working. Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Mar 26 6:41: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 7AD5437B718 for ; Mon, 26 Mar 2001 06:41:19 -0800 (PST) (envelope-from wkb@freebie.demon.nl) Received: from [195.11.243.26] (helo=Debug) by post.mail.nl.demon.net with smtp (Exim 3.14 #4) id 14hYBH-000IRC-00 for freebsd-alpha@freebsd.org; Mon, 26 Mar 2001 14:41:15 +0000 To: freebsd-alpha@freebsd.org From: wkb@freebie.demon.nl Subject: Tlaser/8400 no go on 4.3beta Date: Mon, 26 Mar 2001 14:41:15 GMT X-Mailer: www.webmail.nl.demon.net X-Sender: postmaster@wkb@freebie.demon.nl X-Originating-IP: 161.114.88.73 Message-Id: Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org FYI: 'My' particular AS8400 Tlaser does not boot the 20010319beta CD. It dies when starting the kernel (without any message). The 'Booting the kernel in xx seconds' message is displayed but that is about it unfortunately. I downgraded it from 12GB to 256MB but I guess the single KFTHA that drives the 4 DWLPB PCI-boxes is something that makes FreeBSD choke. At least, that is a guess based on Matt's experiences with the AS8200s at Nasa Ames. cheers, Wilko To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Mar 26 7:32:10 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 85AC437B718; Mon, 26 Mar 2001 07:32:04 -0800 (PST) (envelope-from michael@fastmail.ca) Received: by mail.interchange.ca (Fastmailer, from userid 555) id 6DB0420DE; Mon, 26 Mar 2001 10:32:01 -0500 (EST) MIME-Version: 1.0 Message-Id: <3ABF60F1.0000D7.05943@frodo.searchcanada.ca> Content-Type: Multipart/Mixed; boundary="------------Boundary-00=_DT9TE30AMK8NTT4D7TH0" To: msmith@freebsd.org Subject: Re: Boot Loader Progress... Cc: freebsd-alpha@freebsd.org From: "Michael Richards" X-Fastmail-IP: 24.43.130.237 Date: Mon, 26 Mar 2001 10:32:01 -0500 (EST) Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org --------------Boundary-00=_DT9TE30AMK8NTT4D7TH0 Content-Type: Text/Plain Content-Transfer-Encoding: 7bit Hi. > Don't bother with libstand, go straight to the libalpha code and > see if we're actually calling the SRM 'open' function more than > once. I suspect that SRM may have issues with that. Indeed we are calling prom_open multiple times. Here is some serial output that shows some debugging. (boot dva0.0.0.1000.0 -flags 0) block 0 of dva0.0.0.1000.0 is a valid boot block reading 15 blocks from dva0.0.0.1000.0 bootstrap code read in Building FRU table base = 200000, image_start = 0, image_bytes = 1e00 initializing HWRPB at 2000 initializing page table at 1f2000 initializing machine state setting affinity to the primary CPU jumping to bootstrap code Loading /boot/loader Console: SRM firmware console VMS PAL rev: 0x4000200010115 OSF PAL rev: 0x4000200020117 Switch to OSF PAL code succeeded. FreeBSD/alpha SRM disk boot, Revision 1.1 (michael@marconi.eecs.ukans.edu, Mon Mar 26 09:21:03 CST 2001) Memory: 262144 k Opening the boot device...Call to prom_open: DVA 0 1000 0 0 0 8086 0002 returning 1195680 from prom_open Done. Call to prom_open: DVA 0 1000 0 0 0 8086 0002 returning 1196480 from prom_open Call to prom_open: DVA 0 1000 0 0 0 8086 0002 returning 1201504 from prom_open Open called on file (/boot/loader.rc) Call to prom_open: DVA 0 1000 0 0 0 8086 0002 ... Code apparently never returns from here ... I will work to eliminate the extra prom_open calls later today (provided nothing major takes up all my time) and see if that fixes the problems. It would seem to me that an open call would be required if we were loading via tftp, but not from disk. Perhaps this is the origin of the problem. We're calling prom_open multiple times on the same and already open device. Perhaps it is running out of resources or something in this version of SRM. -Michael _________________________________________________________________ http://fastmail.ca/ - Fast Free Web Email for Canadians --------------Boundary-00=_DT9TE30AMK8NTT4D7TH0-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Mar 26 8:40:29 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from chuggalug.clues.com (chuggalug.clues.com [194.159.1.85]) by hub.freebsd.org (Postfix) with ESMTP id 72B1D37B719 for ; Mon, 26 Mar 2001 08:40:27 -0800 (PST) (envelope-from geoffb@chuggalug.clues.com) Received: (from geoffb@localhost) by chuggalug.clues.com (8.9.3/8.9.3) id RAA39838 for alpha@freebsd.org; Mon, 26 Mar 2001 17:40:26 +0100 (BST) (envelope-from geoffb) Date: Mon, 26 Mar 2001 17:40:26 +0100 From: Geoff Buckingham To: alpha@freebsd.org Subject: fxp + 4.3beta + AXPpci33 Message-ID: <20010326174026.A39789@chuggalug.clues.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Trying to install 4.3beta on an AXPpci33 from the network using a compaq badged fxp the install hangs when it tries to bring up the ethernet interface. The console has an error along the lines of 'unknown PHY' (one day I will learn I don't remember stuff as well as I think I will) Finally did a 4.2 install on a SMC/tulip card that even the SRM is happy with. Is their any fix as I have a number of othermachines all with fxps. PS I am currently on 'Garden Leave' so have a reasonable amount of time, but no relevent expertise to offer towards a fix. -- GeoffB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Mar 26 9:24:57 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 50E4637B71A for ; Mon, 26 Mar 2001 09:24:54 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id MAA18589; Mon, 26 Mar 2001 12:24:52 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.3/8.9.1) id f2QHOM867497; Mon, 26 Mar 2001 12:24:22 -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: <15039.31558.847388.40287@grasshopper.cs.duke.edu> Date: Mon, 26 Mar 2001 12:24:22 -0500 (EST) To: wkb@freebie.demon.nl Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: Tlaser/8400 no go on 4.3beta 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 wkb@freebie.demon.nl writes: > FYI: > > 'My' particular AS8400 Tlaser does not boot the 20010319beta CD. > It dies when starting the kernel (without any message). The 'Booting > the kernel in xx seconds' message is displayed but that is about it > unfortunately. Hmm.. Sounds like the same failure mode (loader problems) as the rawhide series. Did it actaully load the kernel? Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Mar 26 9:58:31 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from mail.interchange.ca (ns.interchange.ca [216.126.79.2]) by hub.freebsd.org (Postfix) with ESMTP id 727EE37B719 for ; Mon, 26 Mar 2001 09:58:27 -0800 (PST) (envelope-from michael@fastmail.ca) Received: by mail.interchange.ca (Fastmailer, from userid 555) id BC56D20FE; Mon, 26 Mar 2001 12:58:23 -0500 (EST) MIME-Version: 1.0 Message-Id: <3ABF833F.00018D.48828@frodo.searchcanada.ca> Content-Type: Multipart/Mixed; boundary="------------Boundary-00=_BLGT4PRMY3LOO49D7TH0" To: freebsd-alpha@freebsd.org Subject: Coding Conventions From: "Michael Richards" X-Fastmail-IP: 24.43.130.237 Date: Mon, 26 Mar 2001 12:58:23 -0500 (EST) Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org --------------Boundary-00=_BLGT4PRMY3LOO49D7TH0 Content-Type: Text/Plain Content-Transfer-Encoding: 7bit Just a quick question as I get down to a testable fix on the boot loader problem: I've been hacking up the code adding things like: #ifdef DEBUG printf("returning from prom_open\n"); #endif Should these be left in for future debugging or should the patch only contain the real code changes? IE, if someone else needs to debug, let them go in and add their own printf's... One unfortunate side effect is that the boot loader will no longer fit on a single floppy with the kernel. I deleted the kernel because it dies before getting that far. -Michael _________________________________________________________________ http://fastmail.ca/ - Fast Free Web Email for Canadians --------------Boundary-00=_BLGT4PRMY3LOO49D7TH0-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Mar 26 10:23: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 F2C9D37B719 for ; Mon, 26 Mar 2001 10:23:18 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id NAA20251; Mon, 26 Mar 2001 13:23:17 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.3/8.9.1) id f2QIMlL67664; Mon, 26 Mar 2001 13:22:47 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15039.35063.539812.824792@grasshopper.cs.duke.edu> Date: Mon, 26 Mar 2001 13:22:47 -0500 (EST) To: "Michael Richards" Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: Coding Conventions In-Reply-To: <3ABF833F.00018D.48828@frodo.searchcanada.ca> References: <3ABF833F.00018D.48828@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: > Just a quick question as I get down to a testable fix on the boot > loader problem: I've been hacking up the code adding things like: > #ifdef DEBUG > printf("returning from prom_open\n"); > #endif If I'm going to be using a lot of debugging printfs, then I tend to prefer something like this, rather than having an #ifdef/endif pair for every printf, but its a question of personal style.. #ifdef DEBUG #define DPRINTF(x) printf x #else #define DPRINTF(x) #endif <...> DPRINTF(("Debugging something\n")) > Should these be left in for future debugging or should the patch only > contain the real code changes? IE, if someone else needs to debug, > let them go in and add their own printf's... One unfortunate side I think it would be better to submit 2 patches -- 1 with just the fix, and one with the debugging statements. Don't let this opinion get in your way though, if you fix it, we'll take what we can get ;) > effect is that the boot loader will no longer fit on a single floppy > with the kernel. I deleted the kernel because it dies before getting > that far. Heh. Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Mar 26 10:59:11 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id 8FE8C37B71A; Mon, 26 Mar 2001 10:59:08 -0800 (PST) (envelope-from jhb@FreeBSD.org) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.2/8.11.2) with ESMTP id f2QIwKG21801; Mon, 26 Mar 2001 10:58:28 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20010326103622.H40349@wantadilla.lemis.com> Date: Mon, 26 Mar 2001 10:57:55 -0800 (PST) From: John Baldwin To: Greg Lehey Subject: Re: dev_t size mismatch kernel / userland Cc: leclercn@videotron.ca, freebsd-alpha@FreeBSD.org, Mike Smith , phk@FreeBSD.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 26-Mar-01 Greg Lehey wrote: > On Friday, 23 March 2001 at 21:45:12 -0800, John Baldwin wrote: >> >> On 24-Mar-01 Mike Smith wrote: >>>> Already tried vinum, works fine after modification of dev_t to >>>> u_int64_t. I'll change it to uintptr_t tough (cleaner). Hope this gets >>>> fixed! >>> >>> This is wrong. In the kernel or in a module, dev_t is an opaque type. >>> In userspace, you use udev_t, not dev_t. >>> >>> It sounds like vinum is failing to perform the required conversions when >>> exchanging a dev_t with userland, and the correct fix is going to be to >>> add these. >> >> struct drive, struct plex, etc. are shared between userland and the kernel. >> It >> looks like they need to use a udev_t, and the kernel will always have to do >> udev2dev() before using them. Either that or don't export the structures to >> userland. > > I already had code under way to export expurgated versions of these > structs. But that's a separate issue. It seems to me that if dev_t > is even visible in userland header files, it should be correct. We > should either fix it or remove it. This will probably make Poul's head spin, but one idea might be to have a kdev_t type. :-P In the kernel kdev_t == dev_t, and in userland, kdev_t is a void *. This would work in this case I think because you never use the dev_t's while in userland. I do like exporting trimmed down structures, however. Please don't export mutexes while you are at it. :-P -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Mar 26 11:31:35 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by hub.freebsd.org (Postfix) with ESMTP id A39A937B71A; Mon, 26 Mar 2001 11:31:31 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.3/8.11.3) with ESMTP id f2QJVV366687; Mon, 26 Mar 2001 21:31:31 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: John Baldwin Cc: Greg Lehey , leclercn@videotron.ca, freebsd-alpha@FreeBSD.org, Mike Smith Subject: Re: dev_t size mismatch kernel / userland In-Reply-To: Your message of "Mon, 26 Mar 2001 10:57:55 -0800." Date: Mon, 26 Mar 2001 21:31:31 +0200 Message-ID: <66685.985635091@critter> From: Poul-Henning Kamp Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message , John Baldwin writes: >This will probably make Poul's head spin, but one idea might be to have a >kdev_t type. :-P In the kernel kdev_t == dev_t, and in userland, kdev_t is a >void *. This would work in this case I think because you never use the dev_t's >while in userland. I do like exporting trimmed down structures, however. >Please don't export mutexes while you are at it. :-P Guys, I'm net to this subject, so please fill me in: just what in the (kernel) dev_t do you want to export to userland ? Background: I retained the dev_t name in the kernel to avoid a massive scale source code incompatibility there. In userland dev_t is defined in all sorts of standards as an "arithmetic type", and code would break left right and center if it wasn't one, so I maintained the "minor/major" integer. To give access to the userland view of things in the kernel, the type "udev_t" was introduced, but to avoid polluting things I hid the definition of that type from userland. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Mar 26 13: 1:14 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 8770137B718; Mon, 26 Mar 2001 13:01:12 -0800 (PST) (envelope-from msmith@mass.dis.org) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.2/8.11.2) with ESMTP id f2QL0WE01189; Mon, 26 Mar 2001 13:00:33 -0800 (PST) (envelope-from msmith@mass.dis.org) Message-Id: <200103262100.f2QL0WE01189@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Poul-Henning Kamp Cc: John Baldwin , Greg Lehey , leclercn@videotron.ca, freebsd-alpha@FreeBSD.org Subject: Re: dev_t size mismatch kernel / userland In-reply-to: Your message of "Mon, 26 Mar 2001 21:31:31 +0200." <66685.985635091@critter> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 26 Mar 2001 13:00:32 -0800 From: Mike Smith Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > >This will probably make Poul's head spin, but one idea might be to have a > >kdev_t type. :-P In the kernel kdev_t == dev_t, and in userland, kdev_t is a > >void *. This would work in this case I think because you never use the dev_t's > >while in userland. I do like exporting trimmed down structures, however. > >Please don't export mutexes while you are at it. :-P > > Guys, > > I'm new to this subject, so please fill me in: just what in the > (kernel) dev_t do you want to export to userland ? Nothing. Greg just leaks a dev_t in a structure exchanged between userland and the kernel, and this bit because dev_t is a different size between the two on the Alpha; the right fix is simply to not abuse this structure like this. -- ... 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 Mon Mar 26 13: 1:48 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by hub.freebsd.org (Postfix) with ESMTP id 4F48D37B71B; Mon, 26 Mar 2001 13:01:45 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.3/8.11.3) with ESMTP id f2QL1j368231; Mon, 26 Mar 2001 23:01:45 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Mike Smith Cc: John Baldwin , Greg Lehey , leclercn@videotron.ca, freebsd-alpha@FreeBSD.org Subject: Re: dev_t size mismatch kernel / userland In-Reply-To: Your message of "Mon, 26 Mar 2001 13:00:32 -0800." <200103262100.f2QL0WE01189@mass.dis.org> Date: Mon, 26 Mar 2001 23:01:45 +0200 Message-ID: <68229.985640505@critter> From: Poul-Henning Kamp Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message <200103262100.f2QL0WE01189@mass.dis.org>, Mike Smith writes: >> >This will probably make Poul's head spin, but one idea might be to have a >> >kdev_t type. :-P In the kernel kdev_t == dev_t, and in userland, kdev_t is a >> >void *. This would work in this case I think because you never use the dev_t's >> >while in userland. I do like exporting trimmed down structures, however. >> >Please don't export mutexes while you are at it. :-P >> >> Guys, >> >> I'm new to this subject, so please fill me in: just what in the >> (kernel) dev_t do you want to export to userland ? > >Nothing. Greg just leaks a dev_t in a structure exchanged between >userland and the kernel, and this bit because dev_t is a different size >between the two on the Alpha; the right fix is simply to not abuse this >structure like this. Right, I agree. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Mar 26 13:20:58 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 DDBB337B719 for ; Mon, 26 Mar 2001 13:20:55 -0800 (PST) (envelope-from wkb@freebie.demon.nl) Received: from [212.238.54.101] (helo=freebie.demon.nl) by post.mail.nl.demon.net with smtp (Exim 3.14 #4) id 14heQ2-0009oT-00; Mon, 26 Mar 2001 21:20:54 +0000 Received: (from wkb@localhost) by freebie.demon.nl (8.11.3/8.11.2) id f2QLNYK02264; Mon, 26 Mar 2001 23:23:35 +0200 (CEST) (envelope-from wkb) Date: Mon, 26 Mar 2001 23:23:34 +0200 From: Wilko Bulte To: Andrew Gallatin Cc: freebsd-alpha@freebsd.org Subject: Re: Tlaser/8400 no go on 4.3beta Message-ID: <20010326232334.B2221@freebie.demon.nl> References: <15039.31558.847388.40287@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: <15039.31558.847388.40287@grasshopper.cs.duke.edu>; from gallatin@cs.duke.edu on Mon, Mar 26, 2001 at 12:24:22PM -0500 X-OS: FreeBSD 4.3-RC X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, Mar 26, 2001 at 12:24:22PM -0500, Andrew Gallatin wrote: > > wkb@freebie.demon.nl writes: > > FYI: > > > > 'My' particular AS8400 Tlaser does not boot the 20010319beta CD. > > It dies when starting the kernel (without any message). The 'Booting > > the kernel in xx seconds' message is displayed but that is about it > > unfortunately. > > Hmm.. Sounds like the same failure mode (loader problems) as the rawhide > series. Did it actaully load the kernel? I hope to have time to supply you with a captured console transcript tomorrow. 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 Mon Mar 26 16: 3:38 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from wantadilla.lemis.com (wantadilla.lemis.com [192.109.197.80]) by hub.freebsd.org (Postfix) with ESMTP id 5036637B719; Mon, 26 Mar 2001 16:03:30 -0800 (PST) (envelope-from grog@lemis.com) Received: by wantadilla.lemis.com (Postfix, from userid 1004) id 488AF6A918; Tue, 27 Mar 2001 09:33:27 +0930 (CST) Date: Tue, 27 Mar 2001 09:33:27 +0930 From: Greg Lehey To: Mike Smith Cc: Poul-Henning Kamp , John Baldwin , leclercn@videotron.ca, freebsd-alpha@FreeBSD.org Subject: Re: dev_t size mismatch kernel / userland Message-ID: <20010327093327.A40349@wantadilla.lemis.com> References: <66685.985635091@critter> <200103262100.f2QL0WE01189@mass.dis.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200103262100.f2QL0WE01189@mass.dis.org>; from msmith@freebsd.org on Mon, Mar 26, 2001 at 01:00:32PM -0800 Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Monday, 26 March 2001 at 13:00:32 -0800, Mike Smith wrote: >>> This will probably make Poul's head spin, but one idea might be to have a >>> kdev_t type. :-P In the kernel kdev_t == dev_t, and in userland, kdev_t is a >>> void *. This would work in this case I think because you never use the dev_t's >>> while in userland. I do like exporting trimmed down structures, however. >>> Please don't export mutexes while you are at it. :-P >> >> Guys, >> >> I'm new to this subject, so please fill me in: just what in the >> (kernel) dev_t do you want to export to userland ? > > Nothing. Greg just leaks a dev_t in a structure exchanged between > userland and the kernel, and this bit because dev_t is a different > size between the two on the Alpha; the right fix is simply to not > abuse this structure like this. You're missing a number of things here. If a dev_t is defined in userland, it should be the same size as in the kernel. The current situation is obviously a bug. It's certainly open to discussion whether the dev_t definition in userland gets removed or fixed. The other issue is that exporting expurgated versions of kernel structures is expensive. We've been exporting the unexpurgated versions for years elsewhere, for example--see the proc size mismatch messages from ps(1). That got fixed, not because it was "unclean", but because it was a bloody nuisance. Yes, it's "clean" not to export mutexes and dev_ts and friends, but it requires a fair amount of code to do it, and it requires two structures which need to be kept in sync. Exporting them doesn't do any harm that I can see. I don't think that it's self-evident that you need to go to this much trouble. Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Mar 26 16: 9:38 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 95EC637B719; Mon, 26 Mar 2001 16:09:35 -0800 (PST) (envelope-from msmith@mass.dis.org) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.2/8.11.2) with ESMTP id f2R08vE02662; Mon, 26 Mar 2001 16:08:57 -0800 (PST) (envelope-from msmith@mass.dis.org) Message-Id: <200103270008.f2R08vE02662@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Greg Lehey Cc: Poul-Henning Kamp , John Baldwin , leclercn@videotron.ca, freebsd-alpha@FreeBSD.org Subject: Re: dev_t size mismatch kernel / userland In-reply-to: Your message of "Tue, 27 Mar 2001 09:33:27 +0930." <20010327093327.A40349@wantadilla.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 26 Mar 2001 16:08:57 -0800 From: Mike Smith Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > >> I'm new to this subject, so please fill me in: just what in the > >> (kernel) dev_t do you want to export to userland ? > > > > Nothing. Greg just leaks a dev_t in a structure exchanged between > > userland and the kernel, and this bit because dev_t is a different > > size between the two on the Alpha; the right fix is simply to not > > abuse this structure like this. > > You're missing a number of things here. If a dev_t is defined in > userland, it should be the same size as in the kernel. The current > situation is obviously a bug. It's certainly open to discussion > whether the dev_t definition in userland gets removed or fixed. Er, no, it's not a bug. dev_t is expected to be one thing in userland, and quite another in the kernel; the assumption used to be that the two were the same; now they are not. > The other issue is that exporting expurgated versions of kernel > structures is expensive. We've been exporting the unexpurgated > versions for years elsewhere, for example--see the proc size mismatch > messages from ps(1). That got fixed, not because it was "unclean", > but because it was a bloody nuisance. Yes, it's "clean" not to export > mutexes and dev_ts and friends, but it requires a fair amount of code > to do it, and it requires two structures which need to be kept in > sync. Exporting them doesn't do any harm that I can see. I don't > think that it's self-evident that you need to go to this much trouble. You basically shoot your own argument dead here. Don't export private data structures to userland. End of story. 8) -- ... 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 Mon Mar 26 16:35:56 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from wantadilla.lemis.com (wantadilla.lemis.com [192.109.197.80]) by hub.freebsd.org (Postfix) with ESMTP id 97BD337B71D; Mon, 26 Mar 2001 16:35:51 -0800 (PST) (envelope-from grog@lemis.com) Received: by wantadilla.lemis.com (Postfix, from userid 1004) id F05516A90D; Tue, 27 Mar 2001 10:05:48 +0930 (CST) Date: Tue, 27 Mar 2001 10:05:48 +0930 From: Greg Lehey To: Mike Smith Cc: Poul-Henning Kamp , John Baldwin , leclercn@videotron.ca, freebsd-alpha@FreeBSD.org Subject: Re: dev_t size mismatch kernel / userland Message-ID: <20010327100548.D40349@wantadilla.lemis.com> References: <20010327093327.A40349@wantadilla.lemis.com> <200103270008.f2R08vE02662@mass.dis.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200103270008.f2R08vE02662@mass.dis.org>; from msmith@freebsd.org on Mon, Mar 26, 2001 at 04:08:57PM -0800 Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Monday, 26 March 2001 at 16:08:57 -0800, Mike Smith wrote: >>>> I'm new to this subject, so please fill me in: just what in the >>>> (kernel) dev_t do you want to export to userland ? >>> >>> Nothing. Greg just leaks a dev_t in a structure exchanged between >>> userland and the kernel, and this bit because dev_t is a different >>> size between the two on the Alpha; the right fix is simply to not >>> abuse this structure like this. >> >> You're missing a number of things here. If a dev_t is defined in >> userland, it should be the same size as in the kernel. The current >> situation is obviously a bug. It's certainly open to discussion >> whether the dev_t definition in userland gets removed or fixed. > > Er, no, it's not a bug. dev_t is expected to be one thing in userland, > and quite another in the kernel; the assumption used to be that the two > were the same; now they are not. Would you care to explain? >> The other issue is that exporting expurgated versions of kernel >> structures is expensive. We've been exporting the unexpurgated >> versions for years elsewhere, for example--see the proc size mismatch >> messages from ps(1). That got fixed, not because it was "unclean", >> but because it was a bloody nuisance. Yes, it's "clean" not to export >> mutexes and dev_ts and friends, but it requires a fair amount of code >> to do it, and it requires two structures which need to be kept in >> sync. Exporting them doesn't do any harm that I can see. I don't >> think that it's self-evident that you need to go to this much trouble. > > You basically shoot your own argument dead here. Your unsubstantiated claim. > Don't export private data structures to userland. End of story. 8) No, categorical statements prove nothing. Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Mar 26 17: 2:56 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 0996837B71A for ; Mon, 26 Mar 2001 17:02:55 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.3/8.11.1) id f2R12sX45541 for alpha@freebsd.org; Mon, 26 Mar 2001 17:02:54 -0800 (PST) (envelope-from obrien) Date: Mon, 26 Mar 2001 17:02:54 -0800 From: "David O'Brien" To: alpha@freebsd.org Subject: dump(8) Message-ID: <20010326170253.A45531@dragon.nuxi.com> Reply-To: obrien@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i X-Operating-System: FreeBSD 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 This broken dump(8) situation *must* get fixed. It is time to back out commits. Does anyone have any idea what commit(s) broke dump? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Mar 26 17: 5:21 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 1995D37B71B; Mon, 26 Mar 2001 17:05:18 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id UAA29245; Mon, 26 Mar 2001 20:05:16 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.3/8.9.1) id f2R14kv68429; Mon, 26 Mar 2001 20:04:46 -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: <15039.59182.857539.804159@grasshopper.cs.duke.edu> Date: Mon, 26 Mar 2001 20:04:46 -0500 (EST) To: obrien@FreeBSD.ORG Cc: alpha@FreeBSD.ORG Subject: Re: dump(8) In-Reply-To: <20010326170253.A45531@dragon.nuxi.com> References: <20010326170253.A45531@dragon.nuxi.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 David O'Brien writes: > This broken dump(8) situation *must* get fixed. It is time to back out > commits. Does anyone have any idea what commit(s) broke dump? Nope. Its almost certainly related to the linuxthreads problem I was talking about last week where a userland app dies on an instruction fault with a PC somwhere in witness_exit(). I haven't been able to figure it out yet.. Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Mar 26 17:25:48 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id 0941E37B718; Mon, 26 Mar 2001 17:25:45 -0800 (PST) (envelope-from jhb@FreeBSD.org) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.2/8.11.2) with ESMTP id f2R1P0G32932; Mon, 26 Mar 2001 17:25:00 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <15039.59182.857539.804159@grasshopper.cs.duke.edu> Date: Mon, 26 Mar 2001 17:24:39 -0800 (PST) From: John Baldwin To: Andrew Gallatin Subject: Re: dump(8) Cc: alpha@FreeBSD.org, obrien@FreeBSD.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 27-Mar-01 Andrew Gallatin wrote: > > David O'Brien writes: > > This broken dump(8) situation *must* get fixed. It is time to back out > > commits. Does anyone have any idea what commit(s) broke dump? > > Nope. > > Its almost certainly related to the linuxthreads problem I was talking > about last week where a userland app dies on an instruction fault > with a PC somwhere in witness_exit(). > > I haven't been able to figure it out yet.. Try turning preemption off (i.e. remove it from the kernel config). On the x86 side we've seen that non-preemption safe code can blow up in very bad ways. :( FWIW, I've tracked down the vfs_object_create() panic some more after adding in printf's to VOP_CREATEVOBJECT() as so: static __inline int VOP_CREATEVOBJECT( struct vnode *vp, struct ucred *cred, struct proc *p) { struct vop_createvobject_args a; int rc; a.a_desc = VDESC(vop_createvobject); a.a_vp = vp; a.a_cred = cred; a.a_p = p; printf("%s: a = %p, a.a_desc = %p\n", __func__, &a, a.a_desc); printf("vnop %s, offset %d, flags = %d\n", a.a_desc->vdesc_name, a.a_desc->vdesc_offset, a.a_desc->vdesc_flags); printf("vp->v_op = %p, VOFFSET(vop_createvobject) = %d\n", vp->v_op, VOFFSET(vop_createvobject)); printf("vnop to call = %p\n", vp->v_op[VOFFSET(vop_createvobject)]); rc = VCALL(vp, VOFFSET(vop_createvobject), &a); return (rc); } I get the following output prior to the panic: VOP_CREATEVOBJECT: a = 0xfffffe000917da88, a.a_desc = 0xfffffc00006421c0 vnop vop_createvobject, offset 44, flags = 0 vp->v_op = 0xfffffe00006e7600, VOFFSET(vop_createvobject) = 44 vnop to call = 0xfffffc0000541d80 VOP_CREATEVOBJECT: a = 0xfffffe000917d8a8, a.a_desc = 0xfffffc00006421c0 vnop vop_createvobject, offset 44, flags = 0 vp->v_op = 0xfffffe00006e7600, VOFFSET(vop_createvobject) = 44 vnop to call = 0xfffffc0000541d80 VOP_CREATEVOBJECT: a = 0xfffffe000917d788, a.a_desc = 0xfffffc00006421c0 vnop vop_createvobject, offset 44, flags = 0 vp->v_op = 0xfffffe00006e7600, VOFFSET(vop_createvobject) = 44 vnop to call = 0xfffffc0000541d80 VOP_CREATEVOBJECT: a = 0xfffffe000917da28, a.a_desc = 0xfffffc00006421c0 vnop vop_createvobject, offset 44, flags = 0 vp->v_op = 0x8441fd6f7a07947c, VOFFSET(vop_createvobject) = 44 fatal kernel trap: trap entry = 0x4 (unaligned access fault) a0 = 0x8441fd6f7a07947c a1 = 0x29 a2 = 0x11 etc. So it looks like the pointer to the vop function table is getting spammed. I'm not sure if the whole vp is spammed or not. :( > Drew -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Mar 26 17:49:28 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 09E1B37B718 for ; Mon, 26 Mar 2001 17:49:25 -0800 (PST) (envelope-from mjacob@feral.com) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id RAA00794; Mon, 26 Mar 2001 17:49:07 -0800 Date: Mon, 26 Mar 2001 17:49:02 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Wilko Bulte Cc: Andrew Gallatin , freebsd-alpha@FreeBSD.ORG Subject: Re: Tlaser/8400 no go on 4.3beta In-Reply-To: <20010326232334.B2221@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 My 8200s boot a buildworld'ed machine. Let me have the console output. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Mar 26 17:56:44 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id C0D1F37B71A; Mon, 26 Mar 2001 17:56:41 -0800 (PST) (envelope-from jhb@FreeBSD.org) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.2/8.11.2) with ESMTP id f2R1uWG33772; Mon, 26 Mar 2001 17:56:32 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Mon, 26 Mar 2001 17:56:11 -0800 (PST) From: John Baldwin To: John Baldwin Subject: Re: dump(8) Cc: obrien@FreeBSD.org, alpha@FreeBSD.org, Andrew Gallatin Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 27-Mar-01 John Baldwin wrote: > > On 27-Mar-01 Andrew Gallatin wrote: >> >> David O'Brien writes: >> > This broken dump(8) situation *must* get fixed. It is time to back out >> > commits. Does anyone have any idea what commit(s) broke dump? >> >> Nope. >> >> Its almost certainly related to the linuxthreads problem I was talking >> about last week where a userland app dies on an instruction fault >> with a PC somwhere in witness_exit(). >> >> I haven't been able to figure it out yet.. > > Try turning preemption off (i.e. remove it from the kernel config). On the > x86 > side we've seen that non-preemption safe code can blow up in very bad ways. >:( Well, I turned preemption off and the only difference it made was in the value spammed into vp->v_op: vp->v_op = 0x79e4f100df39ba4e It's not even an obvious value such as a string, but looks like pure garbage. :( Hmm, in ddb it seems that the rest of the vnode is fine, so it's just the vnode op table pointer that is hosed. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Mar 26 22: 4:11 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by hub.freebsd.org (Postfix) with ESMTP id CF3FE37B718; Mon, 26 Mar 2001 22:04:07 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.3/8.11.3) with ESMTP id f2R642373389; Tue, 27 Mar 2001 08:04:02 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Greg Lehey Cc: Mike Smith , John Baldwin , leclercn@videotron.ca, freebsd-alpha@freebsd.org Subject: Re: dev_t size mismatch kernel / userland In-Reply-To: Your message of "Tue, 27 Mar 2001 09:33:27 +0930." <20010327093327.A40349@wantadilla.lemis.com> Date: Tue, 27 Mar 2001 08:04:01 +0200 Message-ID: <73387.985673041@critter> From: Poul-Henning Kamp Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message <20010327093327.A40349@wantadilla.lemis.com>, Greg Lehey writes: >On Monday, 26 March 2001 at 13:00:32 -0800, Mike Smith wrote: >>>> This will probably make Poul's head spin, but one idea might be to have a >>>> kdev_t type. :-P In the kernel kdev_t == dev_t, and in userland, kdev_t is a >>>> void *. This would work in this case I think because you never use the dev_t's >>>> while in userland. I do like exporting trimmed down structures, however. >>>> Please don't export mutexes while you are at it. :-P >>> >>> Guys, >>> >>> I'm new to this subject, so please fill me in: just what in the >>> (kernel) dev_t do you want to export to userland ? >> >> Nothing. Greg just leaks a dev_t in a structure exchanged between >> userland and the kernel, and this bit because dev_t is a different >> size between the two on the Alpha; the right fix is simply to not >> abuse this structure like this. > >You're missing a number of things here. If a dev_t is defined in >userland, it should be the same size as in the kernel. The current >situation is obviously a bug. The current situation is the best compromise between breaking POSIX compliance for userland or source-code compatibility for the kernel. >It's certainly open to discussion >whether the dev_t definition in userland gets removed or fixed. The userland definition of dev_t is not changeable without breaking POSIX compliance. If you ratify on arch@ that "dev_t" gets renamed in the kernel, then I'll do the work. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Mar 27 2: 5:23 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from finch-post-12.mail.demon.net (finch-post-12.mail.demon.net [194.217.242.41]) by hub.freebsd.org (Postfix) with ESMTP id AB79037B718; Tue, 27 Mar 2001 02:05:19 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from [62.49.251.130] (helo=herring.nlsystems.com) by finch-post-12.mail.demon.net with esmtp (Exim 2.12 #1) id 14hqLi-0001jK-0C; Tue, 27 Mar 2001 10:05:15 +0000 Received: from herring (herring [10.0.0.2]) by herring.nlsystems.com (8.11.2/8.11.2) with ESMTP id f2RA3x433434; Tue, 27 Mar 2001 11:03:59 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Tue, 27 Mar 2001 11:03:59 +0100 (BST) From: Doug Rabson To: Greg Lehey Cc: Mike Smith , Poul-Henning Kamp , John Baldwin , , Subject: Re: dev_t size mismatch kernel / userland In-Reply-To: <20010327100548.D40349@wantadilla.lemis.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, 27 Mar 2001, Greg Lehey wrote: > >> The other issue is that exporting expurgated versions of kernel > >> structures is expensive. We've been exporting the unexpurgated > >> versions for years elsewhere, for example--see the proc size mismatch > >> messages from ps(1). That got fixed, not because it was "unclean", > >> but because it was a bloody nuisance. Yes, it's "clean" not to export > >> mutexes and dev_ts and friends, but it requires a fair amount of code > >> to do it, and it requires two structures which need to be kept in > >> sync. Exporting them doesn't do any harm that I can see. I don't > >> think that it's self-evident that you need to go to this much trouble. > > > > You basically shoot your own argument dead here. > > Your unsubstantiated claim. > > > Don't export private data structures to userland. End of story. 8) > > No, categorical statements prove nothing. The point is that this structure is part of the ABI between kernel and user parts of vinum. By exposing implementation details in the ABI, you are inevitable making the ABI more fragile, with potential knock-on problems when kernel and user parts get out of sync. In my opinion, all APIs should be defined as clearly as possible without emdedding any implementation details if at all possible. Structures in APIs should be designed carefully and used sparingly since they are the single largest cause of ABI breakage. Efficiency concerns are only relavent if the API must be particularly fast - I don't think this is the case here. -- Doug Rabson Mail: dfr@nlsystems.com Phone: +44 20 8348 6160 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Mar 27 2: 6: 6 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 7F4A637B718 for ; Tue, 27 Mar 2001 02:06:01 -0800 (PST) (envelope-from wkb@freebie.demon.nl) Received: from [195.11.243.26] (helo=Debug) by post.mail.nl.demon.net with smtp (Exim 3.14 #4) id 14hqMS-0006ny-00 for freebsd-alpha@freebsd.org; Tue, 27 Mar 2001 10:06:00 +0000 To: freebsd-alpha@freebsd.org From: wkb@freebie.demon.nl Subject: TLaser8400 take 2 / logfile Date: Tue, 27 Mar 2001 10:06:00 GMT X-Mailer: www.webmail.nl.demon.net X-Sender: postmaster@wkb@freebie.demon.nl X-Originating-IP: 161.114.88.76 Message-Id: Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Tlaser enthousiasts ;-) here is the boot transcript of the 20010319beta CDROM boot. To simplify the machine I have disconnected hoses 1-3 from the KFTHA After the 'booting kernel' messages the CDROM drive's LED stays lit for a considerable time, subsequently followed by the 'drive no longer valid' message. IMO it could well be the same/ similar problem like AS4[01]00 and 1200 have while booting the CD. Wilko P00>>>sho conf Name Type Ext Rev Mnemonic TLSB 0++ KN7CF-AB 8014 0 0000 kn7cf-ab0 1++ KN7CF-AB 8014 0 0000 kn7cf-ab1 2++ KN7CF-AB 8014 0 0000 kn7cf-ab2 3++ KN7CF-AB 8014 0 0000 kn7cf-ab3 5+ MS7CC 5000 0 0000 ms7cc0 8+ KFTHA 2000 0 0000 kftha0 C0 PCI connected to kftha0 pci0 0+ DEC PCI MC 181011 0 0022 mc0 3+ QLogic ISP1040B 10201077 0 0005 isp0 6+ KZPAA 11000 0 0002 kzpaa0 7+ QLogic ISP1040B 10201077 0 0005 isp1 8+ DECchip 21140-AA 91011 500A1011 0022 tulip0 P00>>>sho dev polling for units on isp0, slot 3, bus 0, hose0... pka.7.0.3.0 pka term on Bus ID 7 5.57 polling for units on kzpaa0, slot 6, bus 0, hose0... pkb.7.0.6.0 pkb Bus ID 7 dkb600.6.0.6.0 DKB600 RRD47 1206 polling for units on isp1, slot 7, bus 0, hose0... pkc.7.0.7.0 pkc term on Bus ID 7 5.57 P00>>>sho mem Set Node Size Base Address Intlv Position --- ---- ---- -------- -------- ----- -------- A 5 256 Mb 00000000 00000000 2-Way 0 P00>>>boot dkb600 Initializing... ff.fe.fd.fc.fb.fa.f9.f8.f7.f6.f5.f4.f4.f3.f2.f1.f0. ef.ee.ed.f4. ff.fe.fd.fc.fb.fa.f9.f8.f7.f6.f5.f4.f4.f3.f2.f1.f0. ef.ee.ed.a2.a4.a5.a7.a8.a9.f4.ec.eb.eb.ea.e9.e8.e7.e6.e5.e3. F E D C B A 9 8 7 6 5 4 3 2 1 0 NODE # A . . M . P P P P TYP o . . + . ++ ++ ++ ++ ST1 . . . . . EE EE EE EB BPD o . . + . ++ ++ ++ ++ ST2 . . . . . EE EE EE EB BPD c3.e2.e0.ce.cd.cb.de.ca.c9.c8. c7.c5.c4.c3.dd.dc.db.da.d9. + . . + . ++ ++ ++ ++ ST3 . . . . . EE EE EE EB BPD d8.d7.d6.d5.d4. . . . + + + . . + . . + C0 PCI + . . . . . . . . . . . . . . . C1 . . . . . . . . . . . . . . . C2 . . . . . . . . . . . . . . . C3 . . . A0 . . . . . ILV . . . 256 . . . . . 256MB AlphaServer 8400 8-5/625/4, Console V5.8-2 21-JUL-2000 16:30:31 SROM V3.1, OpenVMS PALcode V1.21-1, Tru64 UNIX PALcode V1.23-1 System Serial = AY60323611, OS = UNIX, 8:31:51 March 27, 2001 Configuring I/O adapters... isp0, slot 3, bus 0, hose0 kzpaa0, slot 6, bus 0, hose0 isp1, slot 7, bus 0, hose0 tulip0, slot 8, bus 0, hose0 Configuration completed Checking system information CPU 0 booting (boot dkb600.6.0.6.0 -flags a) SRM boot identifier: scsi 0 6 0 6 600 ef00 11000 boot adapter: kzpaa0 rev 2 in bus slot 6 off of kftha0 in TLSB slot 8 block 0 of dkb600.6.0.6.0 is a valid boot block reading 356 blocks from dkb600.6.0.6.0 bootstrap code read in Building FRU table....... FRU table size = 306b(12395) base = 200000, image_start = 0, image_bytes = 2c800 initializing HWRPB at 2000 initializing page table at 1f0000 initializing machine state setting affinity to the primary CPU jumping to bootstrap code Console: SRM firmware console VMS PAL rev: 0x10000100010115 OSF PAL rev: 0x10000100020117 Switch to OSF PAL code succeeded. FreeBSD/alpha SRM CD9660 boot, Revision 0.1 (jkh@beast.freebsd.org, Mon Mar 20 21:08:56 GMT 2000) Memory: 262144 k |/-^H\^H|^H/^H-^H\^H|^H/^H-^H\^H|^H/^H-^H\^H|^H/^H-^H\^H|^H/^H-^H\^H|^H/^H-^H\^H |^H/^H-^H> echo \007\007 ^G^G > autoboot 10 Hit [Enter] to boot immediately, or any other key for command prompt. Booting [kernel] in 9 seconds... Booting [kernel] in 8 seconds... Booting [kerne l] in 7 seconds... Booting [kernel] in 6 seconds... Booting [kernel] in 5 second s... Booting [kernel] in 4 seconds... Booting [kernel] in 3 seconds... Booting [ kernel] in 2 seconds... Booting [kernel] in 1 second... Booting [kernel]... failed to send Read to dkb600.6.0.6.0 device dkb600.6.0.6.0 no longer valid device dkb600.6.0.6.0 no longer valid device dkb600.6.0.6.0 no longer valid device dkb600.6.0.6.0 no longer valid device dkb600.6.0.6.0 no longer valid To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Mar 27 4:47:58 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id C365337B719; Tue, 27 Mar 2001 04:47:52 -0800 (PST) (envelope-from dwmalone@maths.tcd.ie) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 27 Mar 2001 13:47:51 +0100 (BST) To: freebsd-hackers@freebsd.org, freebsd-alpha@freebsd.org Cc: wpaul@freebsd.org, brian@freebsd.org Subject: Control messages. X-Request-Do: Date: Tue, 27 Mar 2001 13:47:51 +0100 From: David Malone Message-ID: <200103271347.aa40230@salmon.maths.tcd.ie> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I was looking at our implimention of passing descriptors and credentials over unix domain sockets (I want to add the ability to pass more than one message at a time). According to Steven's book you should use the CMSG_DATA macro to find the data in associated with a struct cmsghdr. We define this macro as: #define CMSG_DATA(cmsg) ((u_char *)(cmsg) + \ _ALIGN(sizeof(struct cmsghdr))) However, the kernel seems to get the address of the data by looking at (void *)(&cmsg[1]). Some applications either find the data either using the kernel's method or by using: struct blah { struct cmsghdr header; sturct wibble data; }; and taking the address of "data". Fortunately all these methods are the same on the i386 'cos the sizeof(sizeof(struct cmsghdr)) is a multiple of the alighment size. However on the alpha the alignment requirement is 8 bytes and so: CMSG_DATA(cmsg) != (&cmsg[1]) If you use the struct method then offset of "data" will line up with one or the other of these depending on the alignment requirements of data. I'd like to change the code to always use the CMSG_DATA method, which will change the ABI on the alpha. This shouldn't cause too much disruption as descriptor and credential passing is rarely used. (I think ppp and maybe some rpc stuff use it - not much else does). (As far as I can tell descriptor passing for a large number of descriptors will panic an alpha running FreeBSD too. If anyone can give access to an alpha that it's OK for me to crash I can test this). David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Mar 27 6: 8:31 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 313B737B71B for ; Tue, 27 Mar 2001 06:08:29 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id JAA09361; Tue, 27 Mar 2001 09:08:28 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.3/8.9.1) id f2RE7wJ69893; Tue, 27 Mar 2001 09:07:58 -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: <15040.40638.570371.452219@grasshopper.cs.duke.edu> Date: Tue, 27 Mar 2001 09:07:58 -0500 (EST) To: wkb@freebie.demon.nl Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: TLaser8400 take 2 / logfile 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 wkb@freebie.demon.nl writes: > > autoboot 10 > Hit [Enter] to boot immediately, or any other key for command prompt. > Booting [kernel] in 9 seconds... Booting [kernel] in 8 seconds... Booting [kerne > l] in 7 seconds... Booting [kernel] in 6 seconds... Booting [kernel] in 5 second > s... Booting [kernel] in 4 seconds... Booting [kernel] in 3 seconds... Booting [ > kernel] in 2 seconds... Booting [kernel] in 1 second... Booting [kernel]... > > failed to send Read to dkb600.6.0.6.0 > device dkb600.6.0.6.0 no longer valid > device dkb600.6.0.6.0 no longer valid > device dkb600.6.0.6.0 no longer valid > device dkb600.6.0.6.0 no longer valid > device dkb600.6.0.6.0 no longer valid Looks like the same failure as on rawhides. Perhaps the same workaround would work as well. Michael Richards has been working on this; hopefully he will fix it... Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Mar 27 8:10:20 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 337D737B718 for ; Tue, 27 Mar 2001 08:10:19 -0800 (PST) (envelope-from mjacob@feral.com) Received: from beppo (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id IAA03601; Tue, 27 Mar 2001 08:10:20 -0800 Date: Tue, 27 Mar 2001 08:10:15 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: wkb@freebie.demon.nl Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: TLaser8400 take 2 / logfile In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Yuck. Boot block again. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Mar 27 9:53:20 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from l04.research.kpn.com (l04.research.kpn.com [139.63.192.204]) by hub.freebsd.org (Postfix) with ESMTP id AACE537B718 for ; Tue, 27 Mar 2001 09:53:18 -0800 (PST) (envelope-from K.J.Koster@kpn.com) Received: by l04.research.kpn.com with Internet Mail Service (5.5.2653.19) id ; Tue, 27 Mar 2001 19:53:17 +0100 Message-ID: <59063B5B4D98D311BC0D0001FA7E452205FD9AB2@l04.research.kpn.com> From: "Koster, K.J." To: 'Geoff Buckingham' Cc: alpha@FreeBSD.ORG Subject: RE: fxp + 4.3beta + AXPpci33 Date: Tue, 27 Mar 2001 19:53:16 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Dear Geoff, > > The console has an error along the lines of 'unknown PHY' > Have a dig in the -hackers archives and look for that precise term. There are quite some heated discussions on this problem. 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 Mar 27 11:57:13 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id 1D51B37B719; Tue, 27 Mar 2001 11:57:09 -0800 (PST) (envelope-from jhb@FreeBSD.org) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.2/8.11.2) with ESMTP id f2RJv3G61755; Tue, 27 Mar 2001 11:57:03 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Tue, 27 Mar 2001 11:56:39 -0800 (PST) From: John Baldwin To: John Baldwin Subject: Re: dump(8) (vfs_object_create() panics: found the problem) Cc: obrien@FreeBSD.org, alpha@FreeBSD.org, Andrew Gallatin , markm@FreeBSD.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 27-Mar-01 John Baldwin wrote: > > On 27-Mar-01 Andrew Gallatin wrote: >> >> David O'Brien writes: >> > This broken dump(8) situation *must* get fixed. It is time to back out >> > commits. Does anyone have any idea what commit(s) broke dump? >> >> Nope. >> >> Its almost certainly related to the linuxthreads problem I was talking >> about last week where a userland app dies on an instruction fault >> with a PC somwhere in witness_exit(). >> >> I haven't been able to figure it out yet.. > > Try turning preemption off (i.e. remove it from the kernel config). On the > x86 > side we've seen that non-preemption safe code can blow up in very bad ways. >:( > > FWIW, I've tracked down the vfs_object_create() panic some more after adding > in > printf's to VOP_CREATEVOBJECT() as so: > > static __inline int VOP_CREATEVOBJECT( > struct vnode *vp, > struct ucred *cred, > struct proc *p) > { > struct vop_createvobject_args a; > int rc; > a.a_desc = VDESC(vop_createvobject); > a.a_vp = vp; > a.a_cred = cred; > a.a_p = p; > printf("%s: a = %p, a.a_desc = %p\n", __func__, &a, a.a_desc); > printf("vnop %s, offset %d, flags = %d\n", a.a_desc->vdesc_name, > a.a_desc->vdesc_offset, a.a_desc->vdesc_flags); > printf("vp->v_op = %p, VOFFSET(vop_createvobject) = %d\n", vp->v_op, > VOFFSET(vop_createvobject)); > printf("vnop to call = %p\n", vp->v_op[VOFFSET(vop_createvobject)]); > rc = VCALL(vp, VOFFSET(vop_createvobject), &a); > return (rc); > } > > I get the following output prior to the panic: > > VOP_CREATEVOBJECT: a = 0xfffffe000917da88, a.a_desc = 0xfffffc00006421c0 > vnop vop_createvobject, offset 44, flags = 0 > vp->v_op = 0xfffffe00006e7600, VOFFSET(vop_createvobject) = 44 > vnop to call = 0xfffffc0000541d80 > VOP_CREATEVOBJECT: a = 0xfffffe000917d8a8, a.a_desc = 0xfffffc00006421c0 > vnop vop_createvobject, offset 44, flags = 0 > vp->v_op = 0xfffffe00006e7600, VOFFSET(vop_createvobject) = 44 > vnop to call = 0xfffffc0000541d80 > VOP_CREATEVOBJECT: a = 0xfffffe000917d788, a.a_desc = 0xfffffc00006421c0 > vnop vop_createvobject, offset 44, flags = 0 > vp->v_op = 0xfffffe00006e7600, VOFFSET(vop_createvobject) = 44 > vnop to call = 0xfffffc0000541d80 > VOP_CREATEVOBJECT: a = 0xfffffe000917da28, a.a_desc = 0xfffffc00006421c0 > vnop vop_createvobject, offset 44, flags = 0 > vp->v_op = 0x8441fd6f7a07947c, VOFFSET(vop_createvobject) = 44 > > fatal kernel trap: > > trap entry = 0x4 (unaligned access fault) > a0 = 0x8441fd6f7a07947c > a1 = 0x29 > a2 = 0x11 > > etc. > > So it looks like the pointer to the vop function table is getting spammed. > I'm not sure if the whole vp is spammed or not. :( Ok, as I said earlier, only the pointer to the vnop function table is spammed, the rest of the vnode is ok. I tracked this down to the big /dev/random overhaul commits of March 11. Removing 'device random' from my kernel gets rid of the panic but breaks ssh. :( A kernel just before the Mar 11 /dev/random commits boots fine, and one just after panics. :( Hopefully Mark can trace down where the data corruption is coming from. I'm willing to test any patches. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Mar 27 12: 0:39 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from smtp04.primenet.com (smtp04.primenet.com [206.165.6.134]) by hub.freebsd.org (Postfix) with ESMTP id CD5DE37B71A; Tue, 27 Mar 2001 12:00:37 -0800 (PST) (envelope-from tlambert@usr05.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.9.3/8.9.3) id NAA08217; Tue, 27 Mar 2001 13:00:30 -0700 (MST) Received: from usr05.primenet.com(206.165.6.205) via SMTP by smtp04.primenet.com, id smtpdAAAc2ai8p; Tue Mar 27 13:00:19 2001 Received: (from tlambert@localhost) by usr05.primenet.com (8.8.5/8.8.5) id NAA14143; Tue, 27 Mar 2001 13:00:23 -0700 (MST) From: Terry Lambert Message-Id: <200103272000.NAA14143@usr05.primenet.com> Subject: Re: dump(8) (vfs_object_create() panics: found the problem) To: jhb@FreeBSD.ORG (John Baldwin) Date: Tue, 27 Mar 2001 20:00:23 +0000 (GMT) Cc: jhb@FreeBSD.ORG (John Baldwin), obrien@FreeBSD.ORG, alpha@FreeBSD.ORG, gallatin@cs.duke.edu (Andrew Gallatin), markm@FreeBSD.ORG In-Reply-To: from "John Baldwin" at Mar 27, 2001 11:56:39 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 > Ok, as I said earlier, only the pointer to the vnop function table is spammed, > the rest of the vnode is ok. I tracked this down to the big /dev/random > overhaul commits of March 11. "When we SAY ``random'', we MEAN ``random''!" 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 Tue Mar 27 12:26:42 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from gratis.grondar.za (grouter.grondar.za [196.7.18.65]) by hub.freebsd.org (Postfix) with ESMTP id 47C3837B719; Tue, 27 Mar 2001 12:26:36 -0800 (PST) (envelope-from mark@grondar.za) Received: from grondar.za (root@gratis.grondar.za [196.7.18.133]) by gratis.grondar.za (8.11.1/8.11.1) with ESMTP id f2RKQTf80723; Tue, 27 Mar 2001 22:26:32 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <200103272026.f2RKQTf80723@gratis.grondar.za> To: John Baldwin Cc: obrien@FreeBSD.org, alpha@FreeBSD.org, Andrew Gallatin Subject: Re: dump(8) (vfs_object_create() panics: found the problem) References: In-Reply-To: ; from John Baldwin "Tue, 27 Mar 2001 11:56:39 PST." Date: Tue, 27 Mar 2001 22:27:40 +0200 From: Mark Murray Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Ok, as I said earlier, only the pointer to the vnop function table is > spammed, the rest of the vnode is ok. I tracked this down to the big > /dev/random overhaul commits of March 11. Removing 'device random' > from my kernel gets rid of the panic but breaks ssh. :( A kernel just > before the Mar 11 /dev/random commits boots fine, and one just after > panics. :( Hopefully Mark can trace down where the data corruption is > coming from. I'm willing to test any patches. Very weird. Please comment out all the *rijndael* function calls in hash.c and see if that fixes anything? (I'm suspecting a stack-smash in the rijndael encryption routines). M -- Mark Murray Warning: this .sig is umop ap!sdn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Mar 27 12:48:31 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 5391337B718; Tue, 27 Mar 2001 12:48:26 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id PAA18263; Tue, 27 Mar 2001 15:48:25 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.3/8.9.1) id f2RKltk70596; Tue, 27 Mar 2001 15:47:55 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15040.64635.737475.157879@grasshopper.cs.duke.edu> Date: Tue, 27 Mar 2001 15:47:55 -0500 (EST) To: John Baldwin Cc: obrien@FreeBSD.ORG, alpha@FreeBSD.ORG, markm@FreeBSD.ORG Subject: Re: dump(8) (vfs_object_create() panics: found the problem) 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 John Baldwin writes: > overhaul commits of March 11. Removing 'device random' from my kernel gets rid > of the panic but breaks ssh. :( A kernel just before the Mar 11 /dev/random > commits boots fine, and one just after panics. :( Hopefully Mark can trace > down where the data corruption is coming from. I'm willing to test any patches. Removing the random device from the kernel does not fix the signal (dump, etc) segv problems. Darn. Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Mar 27 13: 9:22 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 0142637B718; Tue, 27 Mar 2001 13:09:18 -0800 (PST) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: from mfg1.cim.alcatel.com.au (mfg1.cim.alcatel.com.au [139.188.23.1]) by netau1.alcanet.com.au (8.9.3 (PHNE_22672)/8.9.3) with ESMTP id HAA06037; Wed, 28 Mar 2001 07:08:37 +1000 (EST) Received: from gsmx07.alcatel.com.au by cim.alcatel.com.au (PMDF V5.2-32 #37645) with ESMTP id <01K1PZKI7NQ8S3CYQU@cim.alcatel.com.au>; Wed, 28 Mar 2001 07:08:34 +1100 Received: (from jeremyp@localhost) by gsmx07.alcatel.com.au (8.11.1/8.11.1) id f2RL8WR46094; Wed, 28 Mar 2001 07:08:32 +1000 (EST envelope-from jeremyp) Content-return: prohibited Date: Wed, 28 Mar 2001 07:08:32 +1000 From: Peter Jeremy Subject: Re: dump(8) (vfs_object_create() panics: found the problem) In-reply-to: ; from jhb@FreeBSD.ORG on Tue, Mar 27, 2001 at 11:56:39AM -0800 To: John Baldwin Cc: obrien@FreeBSD.ORG, alpha@FreeBSD.ORG, Andrew Gallatin , markm@FreeBSD.ORG Mail-Followup-To: John Baldwin , obrien@FreeBSD.ORG, alpha@FreeBSD.ORG, Andrew Gallatin , markm@FreeBSD.ORG Message-id: <20010328070832.U26138@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: Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 2001-Mar-27 11:56:39 -0800, John Baldwin wrote: >Ok, as I said earlier, only the pointer to the vnop function table is >spammed, the rest of the vnode is ok. I tracked this down to the big >/dev/random overhaul commits of March 11. Removing 'device random' >from my kernel gets rid of the panic but breaks ssh. :( A kernel just >before the Mar 11 /dev/random commits boots fine, and one just after >panics. :( This isn't the signal-related problem that Drew and I are seeing: I'm still running a kernel from before the /dev/random overhaul. It's possible that the real problem is elsewhere and the changes to /dev/random just made it more visible. Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Mar 27 14: 8:46 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from imul.math.uni.lodz.pl (imul.math.uni.lodz.pl [212.191.65.2]) by hub.freebsd.org (Postfix) with ESMTP id E940437B71D for ; Tue, 27 Mar 2001 14:08:38 -0800 (PST) (envelope-from dagoon@math.uni.lodz.pl) Received: by imul.math.uni.lodz.pl (Mail Transport Agent, from userid 1168) id 4E0CC1F42; Wed, 28 Mar 2001 00:08:12 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by imul.math.uni.lodz.pl (Mail Transport Agent) with ESMTP id 40E2D1742E for ; Wed, 28 Mar 2001 00:08:12 +0200 (CEST) Date: Wed, 28 Mar 2001 00:08:12 +0200 (CEST) From: Marcin Gryszkalis To: alpha@freebsd.org Subject: gperf segfail on 4.3b Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org hello Wile making world (lates srcs) got the following: ===> cc_tools gperf -p -j1 -i 1 -g -o -t -G -N is_reserved_word -k1,3,$ /usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc/c-parse.gperf > c-gperf.h Segmentation fault - core dumped *** Error code 139 system is FreeBSD 4.3-BETA (march 13), alpha station 500 greetings marcin -- .d$$$$b, $d$$$$b. .d$$$$b, Marcin Gryszkalis $$' `"" $$' `"' $$' `$$ $$. .ss $$ $$ $$ (...) QED. (QED translates from the Latin `"8$$8"' 88 88 88 as "So what?") To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Mar 27 14:18: 1 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 EF87737B718 for ; Tue, 27 Mar 2001 14:17:56 -0800 (PST) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: from mfg1.cim.alcatel.com.au (mfg1.cim.alcatel.com.au [139.188.23.1]) by netau1.alcanet.com.au (8.9.3 (PHNE_22672)/8.9.3) with ESMTP id IAA12698 for ; Wed, 28 Mar 2001 08:17:55 +1000 (EST) Received: from gsmx07.alcatel.com.au by cim.alcatel.com.au (PMDF V5.2-32 #37645) with ESMTP id <01K1Q20FN5AOS4LUGY@cim.alcatel.com.au> for freebsd-alpha@FreeBSD.ORG; Wed, 28 Mar 2001 08:17:53 +1100 Received: (from jeremyp@localhost) by gsmx07.alcatel.com.au (8.11.1/8.11.1) id f2RMHpR47317 for freebsd-alpha@FreeBSD.ORG; Wed, 28 Mar 2001 08:17:51 +1000 (EST envelope-from jeremyp) Content-return: prohibited Date: Wed, 28 Mar 2001 08:16:31 +1000 From: Peter Jeremy Subject: Re: dump(8) In-reply-to: <15039.62193.909968.858131@grasshopper.cs.duke.edu>; from gallatin@cs.duke.edu on Mon, Mar 26, 2001 at 08:54:57PM -0500 To: Andrew Gallatin Cc: John Baldwin , obrien@FreeBSD.ORG Message-id: <20010328081631.V26138@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: <15039.59182.857539.804159@grasshopper.cs.duke.edu> <15039.62193.909968.858131@grasshopper.cs.duke.edu> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 2001-Mar-26 20:54:57 -0500, Andrew Gallatin wrote: > >John Baldwin writes: > > > I haven't been able to figure it out yet.. > > > > Try turning preemption off (i.e. remove it from the kernel config). On the x86 > > side we've seen that non-preemption safe code can blow up in very bad ways. :( > >Heh. I've never been brave enough to turn it on in the first place. ;-) Same here. >0xfffffe0006823360 is in witness_exit(). And I think the RA is >probably in the sigcode. So my guess about signals seem to be right on >track, as does Peter Jeremy's guess about t12 getting clobbered: My initial investigations (without WITNESS) showed that the offending code had just executed "_mtx_exit(..., &Giant)". I might see if I can add some code near exception.s:Lnohae to trap to ddb if t12 points into the kernel rather than userland - there might still be enough evidence left to find where Giant was being released. >Its looking more and more like a stack smash somewhere scribbling over >p->p_md.md_tf, but I'm damned if I know where. It would be enough to set FRAME_FLAGS_SYSCALL in p->p_md.md_tf->tf_regs[FRAME_FLAGS] - but I can't see how that could occur either. If it is stack smashing, adding a chunk of dead space below the trapframe should remove the corruption (ie decrement sp by (say) 1024 in each XentFOO just before CALL(FOO)). This would mean boosting the size of the kernel stack as well. It's not consistent, so it smells to me like an interrupt window - but I can't see anything wrong in the exception entry code either. How about the following scenario: Returning from a normal syscall, after XentSys1, FRAME_FLAGS indicates only a short register restore is necessary. The code then calls ast() which finds a pending signal and sets up a return via the userland signal trampoline - saving the relevant address in p->p_md.md_tf->tf_regs[FRAME_T12] and clearing p->p_md.md_tf->tf_regs[FRAME_FLAGS]. When the code returns back into exception.s, it's committed to a short restore, leaving t12 pointing to the Giant unlock at the end of ast(). I haven't looked through this in detail so I may have missed the code which prevents this scenario. Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Mar 27 14:53:17 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id 0699B37B718 for ; Tue, 27 Mar 2001 14:53:15 -0800 (PST) (envelope-from jhb@FreeBSD.org) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.2/8.11.2) with ESMTP id f2RMr7G67114 for ; Tue, 27 Mar 2001 14:53:07 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Tue, 27 Mar 2001 14:52:45 -0800 (PST) From: John Baldwin To: alpha@FreeBSD.org Subject: exception_return broken? Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org While browsing sys/alpha/alpha/exception.s I had a little epiphany that might explain the problems we are seeing with signals. First some quotes from : /* * LEAF * Declare a global leaf function. * A leaf function does not call other functions AND does not * use any register that is callee-saved AND does not modify * the stack pointer. */ ... /* * NESTED * Declare a (global) nested function * A nested function calls other functions and needs * therefore stack space to save/restore registers. */ Now look at exception_return in exception.s: /* * exception_return: return from trap, exception, or syscall */ LEAF(exception_return, 1) /* XXX should be NESTED */ br pv, Ler1 Ler1: LDGP(pv) ... /* Handle any AST's or resched's. */ mov sp, a0 /* only arg is frame */ CALL(ast) Lrestoreregs: /* set the hae register if this process has specified a value */ ldq t0, GD_CURPROC(globalp) beq t0, Lnohae ldq t1, P_MD_FLAGS(t0) and t1, MDP_HAEUSED beq t1, Lnohae ldq a0, P_MD_HAE(t0) ldq pv, chipset + CHIPSET_WRITE_HAE CALL((pv)) I think we should definitely make exception_return NESTED() as the XXX comment indicates, but I'm not sure how to to easily do that, as NESTED() requires a number of arguments for things like the frame size and bitmasks of used registers. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Mar 27 14:58:22 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id 3428337B718; Tue, 27 Mar 2001 14:58:20 -0800 (PST) (envelope-from jhb@FreeBSD.org) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.2/8.11.2) with ESMTP id f2RMwCG67307; Tue, 27 Mar 2001 14:58:12 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Tue, 27 Mar 2001 14:57:51 -0800 (PST) From: John Baldwin To: John Baldwin Subject: RE: exception_return broken? Cc: alpha@FreeBSD.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 27-Mar-01 John Baldwin wrote: > While browsing sys/alpha/alpha/exception.s I had a little epiphany that might > explain the problems we are seeing with signals. First some quotes from > : Another note to think about that just occured to me: exception_return() isn't a real function. It's just the back half of an exception, and the exception has already saved the registers, so making it NESTED wouldn't be right as we would screw up the frame. So basically disregard this whole message. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Mar 27 15:49:39 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from Awfulhak.org (awfulhak.demon.co.uk [194.222.196.252]) by hub.freebsd.org (Postfix) with ESMTP id 5B6F437B719; Tue, 27 Mar 2001 15:49:15 -0800 (PST) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (root@hak.lan.Awfulhak.org [172.16.0.12]) by Awfulhak.org (8.11.3/8.11.3) with ESMTP id f2RNnbT64833; Wed, 28 Mar 2001 00:49:37 +0100 (BST) (envelope-from brian@lan.Awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost [127.0.0.1]) by hak.lan.Awfulhak.org (8.11.3/8.11.3) with ESMTP id f2RGfJL00975; Tue, 27 Mar 2001 17:41:19 +0100 (BST) (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200103271641.f2RGfJL00975@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.3.1 01/18/2001 with nmh-1.0.4 To: David Malone Cc: freebsd-hackers@freebsd.org, freebsd-alpha@freebsd.org, wpaul@freebsd.org, brian@freebsd.org, brian@Awfulhak.org Subject: Re: Control messages. In-Reply-To: Message from David Malone of "Tue, 27 Mar 2001 13:47:51 BST." <200103271347.aa40230@salmon.maths.tcd.ie> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 27 Mar 2001 17:41:19 +0100 From: Brian Somers Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I can't see where in the kernel we're *not* using CMSG_DATA(). This was fixed a while ago and tested ok on beast (for 3 descriptors AFAIR). Are we looking at the same code (I'm looking in /sys/kern) ? The only dodgy thing I see in there is the COMPAT_OLDSOCK stuff in uipc_syscalls.c, and that has a very nice disclaimer: /* * We assume that old recvmsg calls won't receive access * rights and other control info, esp. as control info * is always optional and those options didn't exist in 4.3. * If we receive rights, trim the cmsghdr; anything else * is tossed. */ > I was looking at our implimention of passing descriptors and > credentials over unix domain sockets (I want to add the ability to > pass more than one message at a time). According to Steven's book > you should use the CMSG_DATA macro to find the data in associated > with a struct cmsghdr. We define this macro as: > > #define CMSG_DATA(cmsg) ((u_char *)(cmsg) + \ > _ALIGN(sizeof(struct cmsghdr))) > > However, the kernel seems to get the address of the data by looking > at (void *)(&cmsg[1]). Some applications either find the data either > using the kernel's method or by using: > > struct blah { > struct cmsghdr header; > sturct wibble data; > }; > > and taking the address of "data". Fortunately all these methods are > the same on the i386 'cos the sizeof(sizeof(struct cmsghdr)) is a > multiple of the alighment size. However on the alpha the alignment > requirement is 8 bytes and so: > > CMSG_DATA(cmsg) != (&cmsg[1]) > > If you use the struct method then offset of "data" will line up > with one or the other of these depending on the alignment requirements > of data. > > I'd like to change the code to always use the CMSG_DATA method, > which will change the ABI on the alpha. This shouldn't cause too > much disruption as descriptor and credential passing is rarely > used. (I think ppp and maybe some rpc stuff use it - not much > else does). > > (As far as I can tell descriptor passing for a large number of > descriptors will panic an alpha running FreeBSD too. If anyone can > give access to an alpha that it's OK for me to crash I can test > this). > > David. -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Mar 27 16:50:21 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 E0E4837B718 for ; Tue, 27 Mar 2001 16:50:11 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.3/8.11.1) id f2S0nqb29049; Tue, 27 Mar 2001 16:49:52 -0800 (PST) (envelope-from obrien) Date: Tue, 27 Mar 2001 16:49:51 -0800 From: "David O'Brien" To: Marcin Gryszkalis Cc: freebsd-alpha@freebsd.org Subject: Re: gperf segfail on 4.3b Message-ID: <20010327164951.B18676@dragon.nuxi.com> Reply-To: freebsd-alpha@freebsd.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from dagoon@math.uni.lodz.pl on Wed, Mar 28, 2001 at 12:08:12AM +0200 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, Mar 28, 2001 at 12:08:12AM +0200, Marcin Gryszkalis wrote: > ===> cc_tools > gperf -p -j1 -i 1 -g -o -t -G -N is_reserved_word -k1,3,$ > /usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc/c-parse.gperf > > c-gperf.h > Segmentation fault - core dumped > *** Error code 139 I am about to upgrade a DS20 from from 4.2-RELEASE to 4.3-RC. So I'll test this. I can also update an early 4.3-BETA ev4 machine (which IIRC is what yours is), but I really doubt there is a software problem. I believe you either have /usr/src corruption, or a hardware problem. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Mar 27 16:59:48 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id 5C27137B718; Tue, 27 Mar 2001 16:59:46 -0800 (PST) (envelope-from jhb@FreeBSD.org) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.2/8.11.2) with ESMTP id f2S0wpG70858; Tue, 27 Mar 2001 16:58:51 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <200103272026.f2RKQTf80723@gratis.grondar.za> Date: Tue, 27 Mar 2001 16:58:30 -0800 (PST) From: John Baldwin To: Mark Murray Subject: Re: dump(8) (vfs_object_create() panics: found the problem) Cc: Andrew Gallatin , alpha@FreeBSD.org, obrien@FreeBSD.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 27-Mar-01 Mark Murray wrote: >> Ok, as I said earlier, only the pointer to the vnop function table is >> spammed, the rest of the vnode is ok. I tracked this down to the big >> /dev/random overhaul commits of March 11. Removing 'device random' >> from my kernel gets rid of the panic but breaks ssh. :( A kernel just >> before the Mar 11 /dev/random commits boots fine, and one just after >> panics. :( Hopefully Mark can trace down where the data corruption is >> coming from. I'm willing to test any patches. > > Very weird. > > Please comment out all the *rijndael* function calls in hash.c and > see if that fixes anything? (I'm suspecting a stack-smash in the > rijndael encryption routines). I've narrowed it down to the rijndael_blockEncrypt() in yarrow_encrypt(). Probably it is a buffer overflow of the d_out buffer passed in to that function. Now I'm off to check all the callers of yarrow_encrypt(). -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Mar 27 17:39: 4 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 E0AB237B718 for ; Tue, 27 Mar 2001 17:39:02 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id UAA23919; Tue, 27 Mar 2001 20:39:01 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.3/8.9.1) id f2S1cVU71184; Tue, 27 Mar 2001 20:38:31 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15041.16535.812993.790021@grasshopper.cs.duke.edu> Date: Tue, 27 Mar 2001 20:38:31 -0500 (EST) To: Christian Weisgerber Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: Dump segv w/devfs In-Reply-To: <20010306225139.A38325@kemoauc.mips.inka.de> References: <9806fj$1si$1@kemoauc.mips.inka.de> <15011.59405.333814.964428@grasshopper.cs.duke.edu> <98328r$f38$1@kemoauc.mips.inka.de> <15013.11144.757425.205222@grasshopper.cs.duke.edu> <20010306210654.A25183@kemoauc.mips.inka.de> <15013.19478.880920.81093@grasshopper.cs.duke.edu> <20010306225139.A38325@kemoauc.mips.inka.de> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I think I may have finally fixed this. Try rev 1.7 of sys/alpha/alpha/exception.s Hats off to Peter Jeremy for a very good catch in finding the failing scenario. Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Mar 27 18: 3: 1 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from mail.idsi.net (mail.idsi.net [216.91.16.14]) by hub.freebsd.org (Postfix) with ESMTP id C749137B71A; Tue, 27 Mar 2001 18:02:47 -0800 (PST) (envelope-from bcook@idsi.net) Received: from mystique2k (admintoo.idsi.net [216.91.16.31]) by mail.idsi.net (8.11.3/8.11.3) with SMTP id f2S22oe04831; Tue, 27 Mar 2001 21:02:50 -0500 (EST) (envelope-from bcook@idsi.net) Message-ID: <000801c0b72b$54198810$0b01a8c0@mystique2k> From: "B. Cook" To: Cc: Subject: Hello :) Date: Tue, 27 Mar 2001 21:03:45 -0500 Organization: Infinity Data Systems (845) 454.6421 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0005_01C0B701.69717F30" 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_0005_01C0B701.69717F30 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hello,=20 I just upgraded to 4.3-RC on Monday. =20 FreeBSD admintoo.idsi.net 4.3-RC FreeBSD 4.3-RC #0: Mon Mar 26 = 12:20:24 EST 2001 = root@admintoo.idsi.net:/usr/obj/usr/src/sys/Admintoo alpha Digital AlphaPC 164LX 533 MHz, 531MHz 8192 byte page size, 1 processor. CPU: EV56 (21164A) major=3D7 minor=3D2 extensions=3D0x1 real memory =3D 132046848 (128952K bytes) avail memory =3D 122814464 (119936K bytes) and well, when it was building the 'world' and kernel I noticed the = -mcpu=3Dev4 option being passed to gcc. Well, I thought this would have = been a ev56. =20 Anyway, when I try and build apache13-modssl, it installs just fine = (with ev4 passed) but when I go to start it, it dumps core. Same with = apache13. The ports are updated, and when I put CPUTYPE=3Dev56 in = /etc/make.conf it does the build with -mcpu=3Dev4 and -mcpu-ev56. my make.conf looks like this: CFLAGS=3D -O -pipe CPUTYPE=3D ev56 and i was just wondering if there is something that I can do to get = apache13-modssl to work on this machine :)=20 would php be too much to ask for as well? I appreciate anyone that has taken the time to read this, and look = forward to any comments that might help. Brian D. Cook Systems Administrator Infinity Data Systems btw, I got the first email off of the /alpha/alpha.html page and someone = on openprojects.net in #freebsd said that kris would also be interested = to know this. If this is wrong I am sorry. ------=_NextPart_000_0005_01C0B701.69717F30 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hello,
 
    I just upgraded to = 4.3-RC on=20 Monday. 
 
        FreeBSD=20 admintoo.idsi.net 4.3-RC FreeBSD 4.3-RC #0: Mon Mar 26 12:20:24 EST=20 2001     root= @admintoo.idsi.net:/usr/obj/usr/src/sys/Admintoo =20 alpha
Digital AlphaPC 164LX 533 MHz, = 531MHz
8192 byte=20 page size, 1 processor.
CPU: EV56 (21164A) major=3D7 minor=3D2=20 extensions=3D0x1<BWX>
real memory  =3D 132046848 (128952K=20 bytes)
avail memory =3D 122814464 (119936K = bytes)

 
and well, when it was building the = 'world' and=20 kernel I noticed the -mcpu=3Dev4 option being passed to gcc.  Well, = I thought=20 this would have been a ev56. 
 
Anyway, when I try and build = apache13-modssl, it=20 installs just fine (with ev4 passed) but when I go to start it, it dumps = core.  Same with apache13.  The ports are updated, and when I = put=20 CPUTYPE=3Dev56 in /etc/make.conf it does the build with -mcpu=3Dev4 and=20 -mcpu-ev56.
 
my make.conf looks like = this:
 
CFLAGS=3D -O -pipe
CPUTYPE=3D ev56
 
and i was just wondering if there is = something that=20 I can do to get apache13-modssl to work on this machine :)
 
would php be too much to ask for as=20 well?
 
I appreciate anyone that has taken the = time to read=20 this, and look forward to any comments that might help.
 
Brian D. Cook
Systems Administrator
Infinity Data Systems
 
btw, I got the first email off of the=20 /alpha/alpha.html page and someone on openprojects.net in #freebsd said = that=20 kris would also be interested to know this.  If this is wrong I am=20 sorry.
 
------=_NextPart_000_0005_01C0B701.69717F30-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Mar 27 18:11: 3 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id 60E4137B719; Tue, 27 Mar 2001 18:11:00 -0800 (PST) (envelope-from jhb@FreeBSD.org) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.2/8.11.2) with ESMTP id f2S2AoG72706; Tue, 27 Mar 2001 18:10:50 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Tue, 27 Mar 2001 18:10:30 -0800 (PST) From: John Baldwin To: John Baldwin Subject: Re: dump(8) (vfs_object_create() panics: found the problem) Cc: obrien@FreeBSD.org, alpha@FreeBSD.org, Andrew Gallatin , Mark Murray Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 28-Mar-01 John Baldwin wrote: > > On 27-Mar-01 Mark Murray wrote: >>> Ok, as I said earlier, only the pointer to the vnop function table is >>> spammed, the rest of the vnode is ok. I tracked this down to the big >>> /dev/random overhaul commits of March 11. Removing 'device random' >>> from my kernel gets rid of the panic but breaks ssh. :( A kernel just >>> before the Mar 11 /dev/random commits boots fine, and one just after >>> panics. :( Hopefully Mark can trace down where the data corruption is >>> coming from. I'm willing to test any patches. >> >> Very weird. >> >> Please comment out all the *rijndael* function calls in hash.c and >> see if that fixes anything? (I'm suspecting a stack-smash in the >> rijndael encryption routines). > > I've narrowed it down to the rijndael_blockEncrypt() in yarrow_encrypt(). > Probably it is a buffer overflow of the d_out buffer passed in to that > function. Now I'm off to check all the callers of yarrow_encrypt(). Ok, looking at the calls to yarrow_encrypt(), all the ones that use &genval are probably bogus. genval is only a 64bit integer, but yarrow_encrypt() assumes that it has KEYSIZE bytes to work with. From looking at the Rijndael code, KEYSIZE needs to be at least 16 bytes before it does anything, and checking the headers it is in fact 32 bytes long, or about 24 bytes longer than genval :(. Since genval is static, it's in the data segment, and when you overflow it you end up spewing random data into other variables. At least you can have comfort in knowing that the faulting address was rather random. Patch included below: Index: yarrow.c =================================================================== RCS file: /usr/cvs/src/sys/dev/random/yarrow.c,v retrieving revision 1.33 diff -u -r1.33 yarrow.c --- yarrow.c 2001/03/10 12:51:55 1.33 +++ yarrow.c 2001/03/28 01:04:18 @@ -255,7 +255,7 @@ u_int read_random_real(void *buf, u_int count) { - static u_int64_t genval; + static char genval[KEYSIZE]; static int cur = 0; static int gate = 1; u_int i; @@ -302,8 +302,7 @@ else { retval = cur < count ? cur : count; memcpy(buf, - (char *)&genval + - (sizeof(random_state.counter) - cur), + &genval[(sizeof(random_state.counter) - cur)], retval); cur -= retval; } The second hunk is mostly a style change (I hate pointer arith), you could probably get away with just removing the now unneeded (char *) cast. With this my alpha is back to working, and now I can get back to breaking current with more SMPng commits. This probably causes some kind of data corruption on x86, too. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Mar 27 18:20:39 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 402C137B71B for ; Tue, 27 Mar 2001 18:20:37 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id VAA24395; Tue, 27 Mar 2001 21:20:36 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.3/8.9.1) id f2S2K6k71289; Tue, 27 Mar 2001 21:20:06 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15041.19030.575231.665223@grasshopper.cs.duke.edu> Date: Tue, 27 Mar 2001 21:20:06 -0500 (EST) To: "B. Cook" Cc: freebsd-alpha@freebsd.org Subject: Re: Hello :) In-Reply-To: <000801c0b72b$54198810$0b01a8c0@mystique2k> References: <000801c0b72b$54198810$0b01a8c0@mystique2k> 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 B. Cook writes: > > > and well, when it was building the 'world' and kernel I noticed the -mcpu=ev4 option being passed to gcc. Well, I thought this would have been a ev56. It is. -mcpu=ev4 is the conservative "works for everybody" flag. Otherwise gcc will end up producing binaries that don't run on older alphas when the compile is done on a newer alpha. The -mcpu-ev56 vs -mcpu-ev4 cpu is almost certainly a red herring. How about building it with -g and running gdb on it and the core dump to find out where its crashing? Drew PS: Please just post text to these mailing lists. No need to duplicate things in html. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Mar 27 18:37:40 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 C947537B71D; Tue, 27 Mar 2001 18:37:37 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id VAA24655; Tue, 27 Mar 2001 21:37:37 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.3/8.9.1) id f2S2b7871346; Tue, 27 Mar 2001 21:37:07 -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: <15041.20051.191604.824890@grasshopper.cs.duke.edu> Date: Tue, 27 Mar 2001 21:37:07 -0500 (EST) To: John Baldwin Cc: alpha@FreeBSD.org Subject: Re: dump(8) (vfs_object_create() panics: found the problem) 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 Nice job. Two of the biggest bugs plaguing FreeBSD/alpha getting fixed in in one day is pretty cool. Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Mar 27 19:20:50 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id AA14C37B71B for ; Tue, 27 Mar 2001 19:20:48 -0800 (PST) (envelope-from jhb@FreeBSD.org) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.2/8.11.2) with ESMTP id f2S3K6G74417; Tue, 27 Mar 2001 19:20:06 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <15041.20051.191604.824890@grasshopper.cs.duke.edu> Date: Tue, 27 Mar 2001 19:19:46 -0800 (PST) From: John Baldwin To: Andrew Gallatin Subject: Re: dump(8) (vfs_object_create() panics: found the problem) Cc: alpha@FreeBSD.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 28-Mar-01 Andrew Gallatin wrote: > > Nice job. Two of the biggest bugs plaguing FreeBSD/alpha getting > fixed in in one day is pretty cool. This one took all day. :-P But, yes, it's been a good day for FreeBSD/alpha. > Drew -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Mar 27 20:22:29 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 7FD6037B71C; Tue, 27 Mar 2001 20:22:26 -0800 (PST) (envelope-from mjacob@feral.com) Received: from beppo (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id UAA06595; Tue, 27 Mar 2001 20:22:31 -0800 Date: Tue, 27 Mar 2001 20:22:25 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: John Baldwin Cc: Andrew Gallatin , alpha@FreeBSD.ORG Subject: Re: dump(8) (vfs_object_create() panics: found the problem) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Yeah. I third this! On Tue, 27 Mar 2001, John Baldwin wrote: > > On 28-Mar-01 Andrew Gallatin wrote: > > > > Nice job. Two of the biggest bugs plaguing FreeBSD/alpha getting > > fixed in in one day is pretty cool. > > This one took all day. :-P But, yes, it's been a good day for > FreeBSD/alpha. > > > Drew > > -- > > John Baldwin -- http://www.FreeBSD.org/~jhb/ > PGP Key: http://www.baldwin.cx/~john/pgpkey.asc > "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-alpha" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Mar 27 23:35:13 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id 1440537B71C; Tue, 27 Mar 2001 23:35:01 -0800 (PST) (envelope-from dwmalone@maths.tcd.ie) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 28 Mar 2001 08:35:00 +0100 (BST) To: Brian Somers Cc: David Malone , freebsd-hackers@freebsd.org, freebsd-alpha@freebsd.org, wpaul@freebsd.org Subject: Re: Control messages. In-reply-to: Your message of "Tue, 27 Mar 2001 17:41:19 BST." <200103271641.f2RGfJL00975@hak.lan.Awfulhak.org> X-Request-Do: Date: Wed, 28 Mar 2001 08:34:53 +0100 From: David Malone Message-ID: <200103280835.aa82064@salmon.maths.tcd.ie> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > I can't see where in the kernel we're *not* using CMSG_DATA(). This > was fixed a while ago and tested ok on beast (for 3 descriptors > AFAIR). Are we looking at the same code (I'm looking in /sys/kern) ? Have a look in uipc_usrreq.c:unp_internalize(), it uses (cm+1) to find where the data is to be written out in the CREDS case and uses (cm+1) to find where the descriptors start in the RIGHTS case. The reallocation code seems to be broken (it attaches a cluster to a mbuf it is still using, currupting the data in the mbuf). If I enable it on the 386, where it is unnecessaey usually, and pass about 50 discriptors I get a panic. I've had a look at what other people have done about this issue. The NetBSD people seem to have taken the fix I'm proposing. Solaris and BSD/OS don't provide the required alignment and just define CMSG_DATA(cm) to be (cm+1). David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Mar 28 0: 9:58 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [209.152.133.57]) by hub.freebsd.org (Postfix) with ESMTP id 9316D37B719 for ; Wed, 28 Mar 2001 00:09:55 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.3/8.11.1) id f2S89tr40378 for alpha@freebsd.org; Wed, 28 Mar 2001 00:09:55 -0800 (PST) (envelope-from obrien) Date: Wed, 28 Mar 2001 00:09:54 -0800 From: "David O'Brien" To: alpha@freebsd.org Subject: Is `ccd' broken on Alpha? Message-ID: <20010328000954.C18676@dragon.nuxi.com> Reply-To: obrien@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i X-Operating-System: FreeBSD 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 I've tried this with both 4.2-RELEASE, and 5-CURRENT and get the same result. When I newfs a ccd partition, it runs *very* quickly -- at the speed of ``newfs -n''. It doesn't seem to write anything to disk, as fsck fails. Any body have any ideas? # disklabel da0 |grep e: e: 13421524 4352000 4.2BSD 1024 8192 22 # (Cyl. 270*- 1106*) # disklabel da1 |grep e: e: 13421524 4352000 4.2BSD 1024 8192 22 # (Cyl. 270*- 1106*) # ccdconfig -C # disklabel ccd0 c: 26842880 0 unused 0 0 # (Cyl. 0 - 13106*) e: 26842880 0 4.2BSD 0 0 0 # (Cyl. 0 - 13106*) # newfs /dev/ccd0e /dev/ccd0e: 26842880 sectors in 6554 cylinders of 1 tracks, 4096 sectors 13106.9MB in 410 cyl groups (16 c/g, 32.00MB/g, 7936 i/g) super-block backups (for fsck -b #) at: 32, 65568, 131104, 196640, 262176, 327712, 393248, 458784, 524320, 589856, ..snip.. # fsck /dev/ccd0e ** /dev/ccd0e BAD SUPER BLOCK: MAGIC NUMBER WRONG ..snip.. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Mar 28 0:46:19 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id 3C6D337B718; Wed, 28 Mar 2001 00:46:15 -0800 (PST) (envelope-from dwmalone@maths.tcd.ie) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 28 Mar 2001 09:46:14 +0100 (BST) Date: Wed, 28 Mar 2001 09:46:07 +0100 From: David Malone To: Brian Somers Cc: freebsd-hackers@freebsd.org, freebsd-alpha@freebsd.org, wpaul@freebsd.org Subject: Re: Control messages. Message-ID: <20010328094607.A92096@walton.maths.tcd.ie> References: <200103271641.f2RGfJL00975@hak.lan.Awfulhak.org> <200103280835.aa82064@salmon.maths.tcd.ie> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200103280835.aa82064@salmon.maths.tcd.ie>; from dwmalone@maths.tcd.ie on Wed, Mar 28, 2001 at 08:34:53AM +0100 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, Mar 28, 2001 at 08:34:53AM +0100, David Malone wrote: > I've had a look at what other people have done about this issue. > The NetBSD people seem to have taken the fix I'm proposing. Solaris > and BSD/OS don't provide the required alignment and just define > CMSG_DATA(cm) to be (cm+1). Actually - I had only looked at the BSD/OS 4.1 and smp-ng sources. Someone pointed out to me that in 4.2 they do align the data. I'm not sure what kernel changes they made corrisponding to this change though. Maybe someone with access to BSD/OS 4.2 kernel sources could have a look and see. David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Mar 28 1:26:35 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from imul.math.uni.lodz.pl (imul.math.uni.lodz.pl [212.191.65.2]) by hub.freebsd.org (Postfix) with ESMTP id 12B2837B718 for ; Wed, 28 Mar 2001 01:26:28 -0800 (PST) (envelope-from dagoon@math.uni.lodz.pl) Received: by imul.math.uni.lodz.pl (Mail Transport Agent, from userid 1168) id 57E861F42; Wed, 28 Mar 2001 11:26:00 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by imul.math.uni.lodz.pl (Mail Transport Agent) with ESMTP id 451A41742E for ; Wed, 28 Mar 2001 11:26:00 +0200 (CEST) Date: Wed, 28 Mar 2001 11:26:00 +0200 (CEST) From: Marcin Gryszkalis To: freebsd-alpha@freebsd.org Subject: Re: gperf segfail on 4.3b In-Reply-To: <20010327164951.B18676@dragon.nuxi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Yesterday David O'Brien wrote: > > ===> cc_tools > > gperf -p -j1 -i 1 -g -o -t -G -N is_reserved_word -k1,3,$ > > /usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc/c-parse.gperf > > > c-gperf.h > > Segmentation fault - core dumped > > *** Error code 139 > I am about to upgrade a DS20 from from 4.2-RELEASE to 4.3-RC. So I'll > test this. I can also update an early 4.3-BETA ev4 machine (which IIRC > is what yours is), but I really doubt there is a software problem. I > believe you either have /usr/src corruption, or a hardware problem. Ok, please write after upgrading how it was. I guess it's not /usr/src problem because I cleaned whole tree but it didn't helped. I believe it's not hardware prob. too (I used to buildworld every week and everything was ok) greetings m. -- .d$$$$b, $d$$$$b. .d$$$$b, Marcin Gryszkalis $$' `"" $$' `"' $$' `$$ $$. .ss $$ $$ $$ (...) QED. (QED translates from the Latin `"8$$8"' 88 88 88 as "So what?") To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Mar 28 3:44:29 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from smtp04.primenet.com (smtp04.primenet.com [206.165.6.134]) by hub.freebsd.org (Postfix) with ESMTP id E8FD537B719 for ; Wed, 28 Mar 2001 03:44:27 -0800 (PST) (envelope-from tlambert@usr05.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.9.3/8.9.3) id EAA07542; Wed, 28 Mar 2001 04:44:14 -0700 (MST) Received: from usr05.primenet.com(206.165.6.205) via SMTP by smtp04.primenet.com, id smtpdAAAWYaiSo; Wed Mar 28 04:44:10 2001 Received: (from tlambert@localhost) by usr05.primenet.com (8.8.5/8.8.5) id EAA02986; Wed, 28 Mar 2001 04:44:13 -0700 (MST) From: Terry Lambert Message-Id: <200103281144.EAA02986@usr05.primenet.com> Subject: Re: gperf segfail on 4.3b To: dagoon@math.uni.lodz.pl (Marcin Gryszkalis) Date: Wed, 28 Mar 2001 11:44:13 +0000 (GMT) Cc: freebsd-alpha@FreeBSD.ORG In-Reply-To: from "Marcin Gryszkalis" at Mar 28, 2001 11:26:00 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 > .d$$$$b, $d$$$$b. .d$$$$b, Marcin Gryszkalis > $$' `"" $$' `"' $$' `$$ > $$. .ss $$ $$ $$ (...) QED. (QED translates from the Latin > `"8$$8"' 88 88 88 as "So what?") Actualy, QED stands for "Quod Erat Demonstradum". The English translation is "And the answer is on the lower right hand side of the whiteboard...". 8-p 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 Mar 28 7:30:51 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from mail.inka.de (quechua.inka.de [212.227.14.2]) by hub.freebsd.org (Postfix) with ESMTP id 6BB9E37B720 for ; Wed, 28 Mar 2001 07:30:48 -0800 (PST) (envelope-from daemon@mips.inka.de) Received: from kemoauc.mips.inka.de (uucp@) by mail.inka.de with local-bsmtp id 14iHuF-0006b0-03; Wed, 28 Mar 2001 17:30:43 +0200 Received: (from daemon@localhost) by kemoauc.mips.inka.de (8.11.3/8.11.1) id f2SFCsF00852 for freebsd-alpha@freebsd.org; Wed, 28 Mar 2001 17:12:54 +0200 (CEST) (envelope-from daemon) From: naddy@mips.inka.de (Christian Weisgerber) Subject: Re: Dump segv w/devfs Date: Wed, 28 Mar 2001 15:12:54 +0000 (UTC) Message-ID: <99sv1m$nb$1@kemoauc.mips.inka.de> References: <9806fj$1si$1@kemoauc.mips.inka.de> <15013.19478.880920.81093@grasshopper.cs.duke.edu> <20010306225139.A38325@kemoauc.mips.inka.de> <15041.16535.812993.790021@grasshopper.cs.duke.edu> Originator: naddy@mips.inka.de (Christian Weisgerber) To: freebsd-alpha@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Andrew Gallatin wrote: > I think I may have finally fixed this. Try rev 1.7 of > sys/alpha/alpha/exception.s Yes! Now switching my backup script from star to dump again... -- Christian "naddy" Weisgerber naddy@mips.inka.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Mar 28 9:37:25 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 6582337B718; Wed, 28 Mar 2001 09:37:24 -0800 (PST) (envelope-from phk@FreeBSD.org) Received: (from phk@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f2SHbON32765; Wed, 28 Mar 2001 09:37:24 -0800 (PST) (envelope-from phk) Date: Wed, 28 Mar 2001 09:37:24 -0800 (PST) From: Message-Id: <200103281737.f2SHbON32765@freefall.freebsd.org> To: leclercn@videotron.ca, phk@FreeBSD.org, freebsd-alpha@freebsd.org Subject: Re: alpha/26042: dev_t size mismatch for DEC Alpha CPUs - kernel / userland Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Synopsis: dev_t size mismatch for DEC Alpha CPUs - kernel / userland State-Changed-From-To: open->closed State-Changed-By: phk State-Changed-When: Wed Mar 28 09:36:05 PST 2001 State-Changed-Why: The proposed change is wrong in every significant aspect. The bug is vinum bogusly exporting dev_t to the kernel. For a potential way to fix vinum, see . http://www.freebsd.org/cgi/query-pr.cgi?pr=26042 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Mar 28 10: 0:48 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from smtp.poklib.org (poklib.org [216.91.16.129]) by hub.freebsd.org (Postfix) with ESMTP id 01D4137B71C for ; Wed, 28 Mar 2001 10:00:21 -0800 (PST) (envelope-from bcook@idsi.net) Received: from mystique2k (sebridge.poklib.org [206.112.128.252] (may be forged)) by smtp.poklib.org (8.9.3/8.9.3) with SMTP id MAA32193; Wed, 28 Mar 2001 12:58:35 -0500 (EST) (envelope-from bcook@idsi.net) From: "B. Cook" To: "Andrew Gallatin" Cc: Subject: RE: Hello :) Date: Wed, 28 Mar 2001 12:59:02 -0500 Message-ID: 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 IMO, Build 9.0.2416 (9.0.2911.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Importance: Normal In-Reply-To: <15042.8078.590071.836889@grasshopper.cs.duke.edu> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I haven't done anything really special... # pwd /usr/ports/www/apache13 [root@admintoo apache13]# make clean distclean ===> Cleaning for apache-1.3.19 ===> Deleting distfiles for apache-1.3.19 # pkg_info | grep apache [root@admintoo apache13]# pkg_info autoconf-2.13 Automatically configure source code on many Un*x platforms automake-1.4 GNU Standards-compliant Makefile generator bash-2.04 The GNU Borne Again Shell bind-9.1.0 The Berkeley Internet Name Daemon, an implementation of DNS bzip2-1.0.1 A block-sorting file compressor cclient-2000c Mark Crispen's C-client mail access routines cvsup-bin-16.1 A general network file distribution system optimized for CV epic4-0.9.16 The (E)nhanced (P)rogrammable (I)RC-II (C)lient expat-1.2 XML 1.0 parser written in C freetype-1.3.1_1 A free and portable TrueType font rendering engine freetype2-2.0.1 A free and portable TrueType font rendering engine gd-1.8.4_1 A graphics library for fast PNG creation gettext-0.10.35 GNU gettext package glib-1.2.8 Some useful routines of C programming gmake-3.79.1 GNU version of 'make' utility h2n-1.29 Translate host table to name server file format ident2-1.0 An RFC1413 identification server which also supports random jpeg-6b IJG's jpeg compression utilities libtool-1.3.4_2 Generic shared library support script logcheck-1.1.1 Auditing tool for system logs on Unix boxes lynx-2.8.3.1 A non-graphical, text-based World-Wide Web client m4-1.4 GNU's m4 mm-1.1.3 Shared memory library for applications with pre-forked proc mrtg-2.9.7 The multi-router traffic grapher mysql-client-3.23.35 Multithreaded SQL database (client) ncftp3-3.0.2 FTP replacement with advanced user interface nmap-2.54.b22 Port scanning utility for large networks osf1_base-4.0f The base set of libraries needed in OSF/1 (Tru64) mode png-1.0.9_1 Library for manipulating PNG images popt-1.5.1 A getopt(3) like library with a number of enhancements, fro python-1.5.2_1 An interpreted object-oriented programming language radiusniff-0.2 Sniffer for RADIUS traffic rdate-1.0 Sets the clock of the local host to the time of another hos rinetd-0.61 A simple TCP port redirector samba-2.0.7 A free SMB and CIFS client and server for UNIX scanssh-1.5 Scanssh scans a subnet and reports the version of SSH insta skill-4.0_1 SuperKILL, kill or renice processes by pid, name, tty or ui stat-1.3 Print inode contents sudo-1.6.3.6 Allow others to run commands as root ucd-snmp-4.2 An extendable SNMP implimentation unrar-2.50 Extract, view & test RAR archives wget-1.6_2 Retrieve files from the 'net via HTTP and FTP # pwd /usr/ports/www/apache13 [root@admintoo apache13]# make install >> apache_1.3.19.tar.gz doesn't seem to exist in /usr/ports/distfiles/. Extracting... >> Checksum OK for apache_1.3.19.tar.gz. + using installation path layout: FreeBSD (/usr/ports/www/apache13/files/FreeBSD.layout) Creating Makefile Creating Configuration.apaci in src + enabling mod_so for DSO support Creating Makefile in src + configured for FreeBSD 4.3 platform + setting C pre-processor to cc -E + checking for system header files + adding selected modules and the build happens... one example to show the ev4 option... ===> src/support cc -c -I../os/unix -I../include -DHARD_SERVER_LIMIT=512 -DDOCUMENT_LOCATI ON=\"/usr/local/www/data/\" -DDEFAULT_PATH=\"/bin:/usr/bin:/usr/local/bin\" -DACCEPT_FILTER_NAME=\"httpready\" -funsigned-char -DUSE_EXPAT -I../lib/ex pat-lite -O -pipe -g -mcpu=ev4 `../apaci` htpasswd.c cc -DHARD_SERVER_LIMIT=512 -DDOCUMENT_LOCATION=\"/usr/local/www/data/\" -D DEFAULT_PATH=\"/bin:/usr/bin:/usr/local/bin\" -DACCEPT_FILTER_NAME=\"httpre ady\" -funsigned-char -DUSE_EXPAT -I../lib/expat-lite -O -pipe -g -mcpu=ev4 `../apaci` -o htpasswd -L../os/unix -L../ap htpasswd.o -lap -los -lcrypt htpasswd.o: In function `main': +--------------------------------------------------------+ | You now have successfully built and installed the | | Apache 1.3 HTTP server. To verify that Apache actually | | works correctly you now should first check the | | (initially created or preserved) configuration files | | | | /usr/local/etc/apache/httpd.conf | | | and then you should be able to immediately fire up | | Apache the first time by running: | | | | /usr/local/sbin/apachectl start | | | Thanks for using Apache. The Apache Group | | http://www.apache.org/ | +--------------------------------------------------------+ ===> Generating temporary packing list Installing /usr/local/etc/rc.d/apache.sh startup file. ===> Compressing manual pages for apache-1.3.19 ===> Registering installation for apache-1.3.19 ===> SECURITY NOTE: This port has installed the following startup scripts which may cause network services to be started at boot time. /usr/local/etc/rc.d/apache.sh tada.. # cd [root@admintoo /root]# pwd /root [root@admintoo /root]# rm -rf httpd.core [root@admintoo /root]# pwd /root # apachectl start Segmentation fault - core dumped /usr/local/sbin/apachectl start: httpd could not be started ]# gdb /usr/local/sbin/httpd GNU gdb 4.18 Copyright 1998 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "alpha-unknown-freebsd"... (gdb) run Starting program: /usr/local/sbin/httpd Program received signal SIGSEGV, Segmentation fault. ap_get_local_host (a=0x120080018) at util.c:2051 2051 if (p->h_addr_list[0]) { (gdb) And this is where I am. Any suggestions? I don't think I'm doing anything 'out of the ordinary' and can't think of any other 'way' to do it :) # uname -a FreeBSD admintoo.idsi.net 4.3-RC FreeBSD 4.3-RC #0: Mon Mar 26 12:20:24 EST 2001 root@admintoo:/usr/obj/usr/src/sys/Admintoo alpha # gcc -v Using builtin specs. gcc version 2.95.2 19991024 (release) # ls -al `which gcc` -r-xr-xr-x 2 root wheel 101072 Mar 26 11:53 /usr/bin/gcc # ls -al `which cc` -r-xr-xr-x 2 root wheel 101072 Mar 26 11:53 /usr/bin/cc I can't think of any other relivant information; Thanks in advance again... Brian -----Original Message----- From: Andrew Gallatin [mailto:gallatin@cs.duke.edu] Sent: Wednesday, March 28, 2001 12:30 PM To: B. Cook Subject: RE: Hello :) FWIW, I just built & installed apache-1.3.19 from ports and it seems to work OK. Can you explain further what, exactly, you did? And CC it to the list, please I know nothing about apache. Thanks, Drew B. Cook writes: > any special options you want from the gbd? this is > # gdb -v > GNU gdb 4.18 > This GDB was configured as "alpha-unknown-freebsd". > > # gdb -core=httpd.core > This GDB was configured as "alpha-unknown-freebsd". > Core was generated by `httpd'. > Program terminated with signal 11, Segmentation fault. > > warning: Hit heuristic-fence-post without finding > > warning: enclosing function for address 0x12002de00 > This warning occurs if you are debugging a function without any symbols > (for example, in a stripped executable). In that case, you may wish to > increase the size of the search with the `set heuristic-fence-post' command. > > Otherwise, you told GDB there was a function where there isn't one, or > (more likely) you have encountered a bug in GDB. > #0 0x12002de00 in ?? () > > > Next Output: > # gdb /usr/local/sbin/httpd > GNU gdb 4.18 > Copyright 1998 Free Software Foundation, Inc. > GDB is free software, covered by the GNU General Public License, and you are > welcome to change it and/or distribute copies of it under certain > conditions. > Type "show copying" to see the conditions. > There is absolutely no warranty for GDB. Type "show warranty" for details. > This GDB was configured as "alpha-unknown-freebsd"... > (gdb) run > Starting program: /usr/local/sbin/httpd > > Program received signal SIGSEGV, Segmentation fault. > ap_get_local_host (a=0x120080018) at util.c:2051 > 2051 if (p->h_addr_list[0]) { > (gdb) > > signal 11 usually means bad ram.. but it can't be bad ram.. this box ran > fbsd 4.1-release, 4.2-release, 4.2-stable, 4.3-RC and did buildworld, and > installworld just fine for all this time. The box doesn't dump on anything > except new things that I build, since I've cvsup'd to 4.3-RC. What else can > I look at? > > (and did I send that last message w/html?, if I did I'm sorry.) > > Thanks in advance. > > Brian > -----Original Message----- > From: Andrew Gallatin [mailto:gallatin@cs.duke.edu] > Sent: Tuesday, March 27, 2001 9:20 PM > To: B. Cook > Cc: freebsd-alpha@freebsd.org > Subject: Re: Hello :) > > > > B. Cook writes: > > > > > > and well, when it was building the 'world' and kernel I noticed > the -mcpu=ev4 option being passed to gcc. Well, I thought this would have > been a ev56. > > It is. -mcpu=ev4 is the conservative "works for everybody" flag. > Otherwise gcc will end up producing binaries that don't run on older > alphas when the compile is done on a newer alpha. > > The -mcpu-ev56 vs -mcpu-ev4 cpu is almost certainly a red herring. > > How about building it with -g and running gdb on it and the core dump > to find out where its crashing? > > Drew > > PS: Please just post text to these mailing lists. No need to > duplicate things in html. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Mar 28 11:46:38 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from ernie.sesamestreet.net (p3EE3916F.dip.t-dialin.net [62.227.145.111]) by hub.freebsd.org (Postfix) with SMTP id 5CA6437B725 for ; Wed, 28 Mar 2001 11:46:35 -0800 (PST) (envelope-from lehmann@ans-netz.de) Received: (qmail 86025 invoked by uid 83); 28 Mar 2001 19:46:15 -0000 Received: from unknown (HELO sina.sesamestreet.net) (192.168.168.200) by ernie.sesamestreet.net with SMTP; 28 Mar 2001 19:46:15 -0000 Date: Wed, 28 Mar 2001 21:50:21 +0200 From: Oliver Lehmann To: "B. Cook" Cc: gallatin@cs.duke.edu, freebsd-alpha@freebsd.org Subject: Re: Hello :) Message-Id: <20010328215021.4ace8e6f.lehmann@ans-netz.de> In-Reply-To: References: <15042.8078.590071.836889@grasshopper.cs.duke.edu> X-Mailer: Sylpheed version 0.4.63cvs6 (GTK+ 1.2.8; i386-unknown-freebsdelf4.2) 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 On Wed, 28 Mar 2001 12:59:02 -0500 "B. Cook" wrote: > # apachectl start > Segmentation fault - core dumped > /usr/local/sbin/apachectl start: httpd could not be started yeah, i've got the same. put ur ip domain in ur /etc/hosts and it will work ;-) Olli To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Mar 28 14: 3:25 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 AF5AD37B725 for ; Wed, 28 Mar 2001 14:03:23 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.3/8.11.1) id f2SM3JI86429; Wed, 28 Mar 2001 14:03:19 -0800 (PST) (envelope-from obrien) Date: Wed, 28 Mar 2001 14:03:19 -0800 From: "David O'Brien" To: Marcin Gryszkalis Cc: freebsd-alpha@freebsd.org Subject: Re: gperf segfail on 4.3b Message-ID: <20010328140318.A86241@dragon.nuxi.com> Reply-To: obrien@freebsd.org References: <20010327164951.B18676@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from dagoon@math.uni.lodz.pl on Wed, Mar 28, 2001 at 11:26:00AM +0200 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, Mar 28, 2001 at 11:26:00AM +0200, Marcin Gryszkalis wrote: > > > ===> cc_tools > > > gperf -p -j1 -i 1 -g -o -t -G -N is_reserved_word -k1,3,$ > > > /usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc/c-parse.gperf > > > > c-gperf.h > > > Segmentation fault - core dumped > > > *** Error code 139 > > I am about to upgrade a DS20 from from 4.2-RELEASE to 4.3-RC. My DS-20 RELENG_4 (ie, 4.3-RC) `make world' completed just fine. I'm about to start one on an AS250 (EV45 system). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Mar 28 14: 7:35 2001 Delivered-To: freebsd-alpha@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 664) id 571CC37B728; Wed, 28 Mar 2001 14:07:33 -0800 (PST) Date: Wed, 28 Mar 2001 14:07:33 -0800 From: David O'Brien To: alpha@freebsd.org Subject: Re: Is `ccd' broken on Alpha? Message-ID: <20010328140733.A11037@hub.freebsd.org> Reply-To: obrien@freebsd.org References: <20010328000954.C18676@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010328000954.C18676@dragon.nuxi.com>; from obrien@freebsd.org on Wed, Mar 28, 2001 at 12:09:54AM -0800 X-Operating-System: FreeBSD 4.2-STABLE Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, Mar 28, 2001 at 12:09:54AM -0800, David O'Brien wrote: > I've tried this with both 4.2-RELEASE, and 5-CURRENT and get the same I just used this this same procedure/settings on an x86 and the `ccd' creation went fine. I then tried a different Alpha (ev45) and set of disks to see if the problem was just with the 1st Alpha I tried this one. I got the same results -- newfs(8) runs as if "-N" as given, and the FFS file system is never written to the `ccd'. At this point I'd like to hear from anyone that has created a `ccd' on an Alpha recently. Otherwise, I'll ask Wilko to note that the `ccd' driver is broken in the 4.3/AXP notes. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Mar 28 14:12:59 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 DB52837B724; Wed, 28 Mar 2001 14:12:55 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id RAA14812; Wed, 28 Mar 2001 17:12:54 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.3/8.9.1) id f2SMCOW79420; Wed, 28 Mar 2001 17:12: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: <15042.25032.738824.665036@grasshopper.cs.duke.edu> Date: Wed, 28 Mar 2001 17:12:24 -0500 (EST) To: obrien@FreeBSD.ORG Cc: alpha@FreeBSD.ORG Subject: Re: Is `ccd' broken on Alpha? In-Reply-To: <20010328140733.A11037@hub.freebsd.org> References: <20010328000954.C18676@dragon.nuxi.com> <20010328140733.A11037@hub.freebsd.org> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org David O'Brien writes: > On Wed, Mar 28, 2001 at 12:09:54AM -0800, David O'Brien wrote: > > I've tried this with both 4.2-RELEASE, and 5-CURRENT and get the same > > I just used this this same procedure/settings on an x86 and the `ccd' > creation went fine. I then tried a different Alpha (ev45) and set of > disks to see if the problem was just with the 1st Alpha I tried this one. > > I got the same results -- newfs(8) runs as if "-N" as given, and the > FFS file system is never written to the `ccd'. > > At this point I'd like to hear from anyone that has created a `ccd' on an > Alpha recently. Otherwise, I'll ask Wilko to note that the `ccd' driver > is broken in the 4.3/AXP notes. Given that vinum is broken on alpha & Greg refuses to fix it, fixing ccd would probably be a better option... I'll plug up some spare drives to my UP1000 and play w/it tonight. No promises, though. Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Mar 28 14:39:34 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 34FFF37B71A; Wed, 28 Mar 2001 14:39:32 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id RAA15447; Wed, 28 Mar 2001 17:39:24 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.3/8.9.1) id f2SMcsR79458; Wed, 28 Mar 2001 17:38:54 -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: <15042.26622.569822.680444@grasshopper.cs.duke.edu> Date: Wed, 28 Mar 2001 17:38:54 -0500 (EST) To: obrien@FreeBSD.ORG Cc: Marcin Gryszkalis , freebsd-alpha@FreeBSD.ORG Subject: Re: gperf segfail on 4.3b In-Reply-To: <20010328140318.A86241@dragon.nuxi.com> References: <20010327164951.B18676@dragon.nuxi.com> <20010328140318.A86241@dragon.nuxi.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 David O'Brien writes: > On Wed, Mar 28, 2001 at 11:26:00AM +0200, Marcin Gryszkalis wrote: > > > > ===> cc_tools > > > > gperf -p -j1 -i 1 -g -o -t -G -N is_reserved_word -k1,3,$ > > > > /usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc/c-parse.gperf > > > > > c-gperf.h > > > > Segmentation fault - core dumped > > > > *** Error code 139 > > > I am about to upgrade a DS20 from from 4.2-RELEASE to 4.3-RC. > > My DS-20 RELENG_4 (ie, 4.3-RC) `make world' completed just fine. > I'm about to start one on an AS250 (EV45 system). Could this be a limits problem? Does gperf take a lot of RAM to run? Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Mar 28 14:47:38 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 47FBA37B71E for ; Wed, 28 Mar 2001 14:47:36 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.3/8.11.1) id f2SMlWw88268; Wed, 28 Mar 2001 14:47:32 -0800 (PST) (envelope-from obrien) Date: Wed, 28 Mar 2001 14:47:32 -0800 From: "David O'Brien" To: Marcin Gryszkalis , freebsd-alpha@FreeBSD.ORG Subject: Re: gperf segfail on 4.3b Message-ID: <20010328144732.A88252@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <20010327164951.B18676@dragon.nuxi.com> <20010328140318.A86241@dragon.nuxi.com> <15042.26622.569822.680444@grasshopper.cs.duke.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <15042.26622.569822.680444@grasshopper.cs.duke.edu>; from gallatin@cs.duke.edu on Wed, Mar 28, 2001 at 05:38:54PM -0500 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, Mar 28, 2001 at 05:38:54PM -0500, Andrew Gallatin wrote: > > On Wed, Mar 28, 2001 at 11:26:00AM +0200, Marcin Gryszkalis wrote: > > > > > ===> cc_tools > > > > > gperf -p -j1 -i 1 -g -o -t -G -N is_reserved_word -k1,3,$ > > > > > /usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc/c-parse.gperf > > > > > > c-gperf.h > > > > > Segmentation fault - core dumped > > > > > *** Error code 139 > > Could this be a limits problem? Does gperf take a lot of RAM to run? Don't think so. IIRC the process would be killed, not caused to segfault. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Mar 28 14:48:53 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 3513B37B71B for ; Wed, 28 Mar 2001 14:48:51 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.3/8.11.1) id f2SMmi088295; Wed, 28 Mar 2001 14:48:44 -0800 (PST) (envelope-from obrien) Date: Wed, 28 Mar 2001 14:48:44 -0800 From: "David O'Brien" To: Andrew Gallatin Cc: alpha@FreeBSD.ORG Subject: Re: Is `ccd' broken on Alpha? Message-ID: <20010328144844.B88252@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <20010328000954.C18676@dragon.nuxi.com> <20010328140733.A11037@hub.freebsd.org> <15042.25032.738824.665036@grasshopper.cs.duke.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <15042.25032.738824.665036@grasshopper.cs.duke.edu>; from gallatin@cs.duke.edu on Wed, Mar 28, 2001 at 05:12:24PM -0500 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, Mar 28, 2001 at 05:12:24PM -0500, Andrew Gallatin wrote: > Given that vinum is broken on alpha & Greg refuses to fix it, Yes, that is very annoying. It is just about time to commit a fix in the name of Alpha platform support. -- -- David (obrien@FreeBSD.org) Disclaimer: Not speaking for FreeBSD, just expressing my own opinion. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Mar 28 15: 6:57 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from srv1.cosmo-project.de (srv1.cosmo-project.de [213.83.6.106]) by hub.freebsd.org (Postfix) with ESMTP id 354A137B728; Wed, 28 Mar 2001 15:06:54 -0800 (PST) (envelope-from ticso@mail.cicely.de) Received: from mail.cicely.de (cicely20 [10.1.1.22]) by srv1.cosmo-project.de (8.11.0/8.11.0) with ESMTP id f2SN6qK95173; Thu, 29 Mar 2001 01:06:52 +0200 (CEST) Received: (from ticso@localhost) by mail.cicely.de (8.11.0/8.11.0) id f2SN7BM26274; Thu, 29 Mar 2001 01:07:11 +0200 (CEST) Date: Thu, 29 Mar 2001 01:07:10 +0200 From: Bernd Walter To: "David O'Brien" Cc: Andrew Gallatin , alpha@FreeBSD.ORG Subject: Re: Is `ccd' broken on Alpha? Message-ID: <20010329010710.C25815@cicely20.cicely.de> References: <20010328000954.C18676@dragon.nuxi.com> <20010328140733.A11037@hub.freebsd.org> <15042.25032.738824.665036@grasshopper.cs.duke.edu> <20010328144844.B88252@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010328144844.B88252@dragon.nuxi.com>; from obrien@FreeBSD.ORG on Wed, Mar 28, 2001 at 02:48:44PM -0800 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, Mar 28, 2001 at 02:48:44PM -0800, David O'Brien wrote: > On Wed, Mar 28, 2001 at 05:12:24PM -0500, Andrew Gallatin wrote: > > Given that vinum is broken on alpha & Greg refuses to fix it, > > Yes, that is very annoying. It is just about time to commit a fix in the > name of Alpha platform support. Does anyone know what functionality of vinum this problem bites? I'm running vinum on alpha for more than a year now and today with a -current (4.1-RELEASE on another machine) from jan 2001: ticso@cicely9:/# mount /dev/da0a on / (ufs, NFS exported, local, soft-updates) mfs:47 on /tmp (mfs, asynchronous, local) /dev/ad0a on /var/d2 (ufs, NFS exported, local, noatime, soft-updates) /dev/vinum/d6 on /var/d6 (ufs, NFS exported, local, noatime, soft-updates) /dev/vinum/d7 on /var/d7 (ufs, NFS exported, local, noatime, soft-updates) /dev/vinum/d8 on /var/d8 (ufs, NFS exported, local, noatime, soft-updates) procfs on /proc (procfs, local) pid205@cicely9:/vol on /vol (nfs) 10.1.1.22:/var/d22 on /net/10.1.1.22/var/d22 (nfs) 10.1.5.7:/var/d1 on /net/10.1.5.7/var/d1 (nfs) 10.1.5.7:/var/d0 on /net/10.1.5.7/var/d0 (nfs) ticso@cicely9:/# uname -a FreeBSD cicely9.cicely.de 5.0-CURRENT FreeBSD 5.0-CURRENT #3: Sun Jan 28 10:09:35 CET 2001 ticso@cicely9.cicely.de:/var/d8/src-2001-01-26/src/sys/compile/CICELY9 alpha Is the problem triggered later or is it only because I did not changed my config since months? I wan't to update to a recent -current and there like to know if there are some concerns. -- B.Walter COSMO-Project http://www.cosmo-project.de ticso@cicely.de Usergroup info@cosmo-project.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Mar 28 15: 9:58 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 2100037B72D; Wed, 28 Mar 2001 15:09:56 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id SAA15901; Wed, 28 Mar 2001 18:09:55 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.3/8.9.1) id f2SN9PI79522; Wed, 28 Mar 2001 18:09:25 -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: <15042.28453.158495.901316@grasshopper.cs.duke.edu> Date: Wed, 28 Mar 2001 18:09:25 -0500 (EST) To: obrien@FreeBSD.ORG Cc: alpha@FreeBSD.ORG Subject: Re: Is `ccd' broken on Alpha? In-Reply-To: <20010328000954.C18676@dragon.nuxi.com> References: <20010328000954.C18676@dragon.nuxi.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 David O'Brien writes: > I've tried this with both 4.2-RELEASE, and 5-CURRENT and get the same > result. When I newfs a ccd partition, it runs *very* quickly -- at the > speed of ``newfs -n''. It doesn't seem to write anything to disk, as > fsck fails. Any body have any ideas? > > > # disklabel da0 |grep e: > e: 13421524 4352000 4.2BSD 1024 8192 22 # (Cyl. 270*- 1106*) > # disklabel da1 |grep e: > e: 13421524 4352000 4.2BSD 1024 8192 22 # (Cyl. 270*- 1106*) > # ccdconfig -C > # disklabel ccd0 > c: 26842880 0 unused 0 0 # (Cyl. 0 - 13106*) > e: 26842880 0 4.2BSD 0 0 0 # (Cyl. 0 - 13106*) > # newfs /dev/ccd0e > /dev/ccd0e: 26842880 sectors in 6554 cylinders of 1 tracks, 4096 sectors > 13106.9MB in 410 cyl groups (16 c/g, 32.00MB/g, 7936 i/g) > super-block backups (for fsck -b #) at: > 32, 65568, 131104, 196640, 262176, 327712, 393248, 458784, 524320, 589856, > ..snip.. > # fsck /dev/ccd0e > ** /dev/ccd0e > BAD SUPER BLOCK: MAGIC NUMBER WRONG > ..snip.. Pilot error of some type? It works fine for me using 'c' paritions. What's the magic incantation to our diskabel to get a reasonably complete set of default paritions onto a disk? Dillon was pushing something a few months ago that turned into a flame fest. Did it ever happen? Or was that for slices in fdisk? Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Mar 28 15:15:15 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 7A27037B731 for ; Wed, 28 Mar 2001 15:15:13 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.3/8.11.1) id f2SNF7k89001; Wed, 28 Mar 2001 15:15:07 -0800 (PST) (envelope-from obrien) Date: Wed, 28 Mar 2001 15:15:03 -0800 From: "David O'Brien" To: Andrew Gallatin Cc: alpha@FreeBSD.ORG Subject: Re: Is `ccd' broken on Alpha? Message-ID: <20010328151503.A88970@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <20010328000954.C18676@dragon.nuxi.com> <15042.28453.158495.901316@grasshopper.cs.duke.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <15042.28453.158495.901316@grasshopper.cs.duke.edu>; from gallatin@cs.duke.edu on Wed, Mar 28, 2001 at 06:09:25PM -0500 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, Mar 28, 2001 at 06:09:25PM -0500, Andrew Gallatin wrote: > Pilot error of some type? Maybe, but the same piloting works on i386. So something is being treated differently between the two platforms. > It works fine for me using 'c' paritions. In general one should not use the `c' partition. Aren't you also seeing disklabel complain that your `c' partition type isn't "unused"? > What's the magic incantation to our disklabel to get a reasonably > complete set of default paritions onto a disk? I didn't realize there was one. ``disklabel -Brw foo99 auto'' is the only one I know of. -- -- David (obrien@FreeBSD.org) Disclaimer: Not speaking for FreeBSD, just expressing my own opinion. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Mar 28 15:17:16 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 DB54537B718 for ; Wed, 28 Mar 2001 15:17:14 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.3/8.11.1) id f2SNH4S89048; Wed, 28 Mar 2001 15:17:04 -0800 (PST) (envelope-from obrien) Date: Wed, 28 Mar 2001 15:17:04 -0800 From: "David O'Brien" To: Andrew Gallatin Cc: alpha@FreeBSD.ORG Subject: Re: Is `ccd' broken on Alpha? Message-ID: <20010328151704.A89023@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <20010328000954.C18676@dragon.nuxi.com> <15042.28453.158495.901316@grasshopper.cs.duke.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <15042.28453.158495.901316@grasshopper.cs.duke.edu>; from gallatin@cs.duke.edu on Wed, Mar 28, 2001 at 06:09:25PM -0500 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, Mar 28, 2001 at 06:09:25PM -0500, Andrew Gallatin wrote: > Pilot error of some type? It works fine for me using 'c' paritions. By `c' partition, you mean for on the `da' devices making up the `ccd', or the `ccd' device? The da disks have `a' and `b' partitions on them, so I can't use `c' on those. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Mar 28 15:24:55 2001 Delivered-To: freebsd-alpha@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 664) id A869437B720; Wed, 28 Mar 2001 15:24:53 -0800 (PST) Date: Wed, 28 Mar 2001 15:24:53 -0800 From: David O'Brien To: alpha@FreeBSD.ORG Subject: Re: Is `ccd' broken on Alpha? Message-ID: <20010328152453.A15677@hub.freebsd.org> Reply-To: obrien@freebsd.org References: <20010328000954.C18676@dragon.nuxi.com> <15042.28453.158495.901316@grasshopper.cs.duke.edu> <20010328151503.A88970@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010328151503.A88970@dragon.nuxi.com>; from obrien@FreeBSD.ORG on Wed, Mar 28, 2001 at 03:15:03PM -0800 X-Operating-System: FreeBSD 4.2-STABLE Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, Mar 28, 2001 at 03:15:03PM -0800, David O'Brien wrote: > On Wed, Mar 28, 2001 at 06:09:25PM -0500, Andrew Gallatin wrote: > > Pilot error of some type? > > Maybe, but the same piloting works on i386. So something is being > treated differently between the two platforms. > > > It works fine for me using 'c' paritions. > > In general one should not use the `c' partition. Aren't you also seeing > disklabel complain that your `c' partition type isn't "unused"? Sigh. Using `c' rather than `e' (or [abd-h]) as the ccd partition works. So there is definitely something being treated differently on the Alpha than the i386 platform. Wilko (bmah?), something for the notes. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Mar 28 17:47:47 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 9C65637B718; Wed, 28 Mar 2001 17:47:44 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id UAA18530; Wed, 28 Mar 2001 20:47:44 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.3/8.9.1) id f2T1lEP79708; Wed, 28 Mar 2001 20:47: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: <15042.37922.136513.58056@grasshopper.cs.duke.edu> Date: Wed, 28 Mar 2001 20:47:14 -0500 (EST) To: obrien@FreeBSD.ORG Cc: alpha@FreeBSD.ORG Subject: Re: Is `ccd' broken on Alpha? In-Reply-To: <20010328151704.A89023@dragon.nuxi.com> References: <20010328000954.C18676@dragon.nuxi.com> <15042.28453.158495.901316@grasshopper.cs.duke.edu> <20010328151704.A89023@dragon.nuxi.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 David O'Brien writes: > On Wed, Mar 28, 2001 at 06:09:25PM -0500, Andrew Gallatin wrote: > > Pilot error of some type? It works fine for me using 'c' paritions. > > By `c' partition, you mean for on the `da' devices making up the `ccd', > or the `ccd' device? The da disks have `a' and `b' partitions on them, > so I can't use `c' on those. Yes, to both. I'll try to make up a fake disklabel and use the 'e' partition to see if that works. I've never, ever used anything but 'c' though on any platform. Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Mar 28 18: 7:25 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 440C937B71D; Wed, 28 Mar 2001 18:07:14 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id VAA18873; Wed, 28 Mar 2001 21:07:13 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.3/8.9.1) id f2T26h679738; Wed, 28 Mar 2001 21:06:43 -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: <15042.39091.263461.18565@grasshopper.cs.duke.edu> Date: Wed, 28 Mar 2001 21:06:43 -0500 (EST) To: Andrew Gallatin Cc: obrien@freebsd.org, freebsd-alpha@freebsd.org Subject: Re: Is `ccd' broken on Alpha? In-Reply-To: <15042.37922.136513.58056@grasshopper.cs.duke.edu> References: <20010328000954.C18676@dragon.nuxi.com> <15042.28453.158495.901316@grasshopper.cs.duke.edu> <20010328151704.A89023@dragon.nuxi.com> <15042.37922.136513.58056@grasshopper.cs.duke.edu> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Andrew Gallatin writes: > > David O'Brien writes: > > On Wed, Mar 28, 2001 at 06:09:25PM -0500, Andrew Gallatin wrote: > > > Pilot error of some type? It works fine for me using 'c' paritions. > > > > By `c' partition, you mean for on the `da' devices making up the `ccd', > > or the `ccd' device? The da disks have `a' and `b' partitions on them, > > so I can't use `c' on those. > > Yes, to both. I'll try to make up a fake disklabel and use the 'e' > partition to see if that works. I've never, ever used anything but > 'c' though on any platform. It works again on da1e/da2e for me. I'm running the top of the tree; world built this afternoon. Here's what I did: <8:54pm>thunder/root:~#cat /tmp/foo # /dev/da1c: type: SCSI disk: SEAGATE label: flags: bytes/sector: 512 sectors/track: 63 tracks/cylinder: 255 sectors/cylinder: 16065 cylinders: 261 sectors/unit: 4194058 rpm: 3600 interleave: 1 trackskew: 0 cylinderskew: 0 headswitch: 0 # milliseconds track-to-track seek: 0 # milliseconds drivedata: 0 8 partitions: # size offset fstype [fsize bsize bps/cpg] a: 196608 0 unused 0 0 # (Cyl. 0 - 12*) b: 1310720 196608 unused 0 0 # (Cyl. 12*- 93*) c: 4194058 0 unused 0 0 # (Cyl. 0 - 261*) e: 1310720 1507328 unused 0 0 # (Cyl. 93*- 175*) f: 1376010 2818048 unused 0 0 # (Cyl. 175*- 261*) <8:55pm>thunder/root:~#disklabel -Rr da1 /tmp/foo <8:55pm>thunder/root:~#disklabel -Rr da2 /tmp/foo <8:55pm>thunder/root:~#cat /etc/ccd.conf ccd0 256 0 /dev/da1e /dev/da2e <8:55pm>thunder/root:~##ccdconfig -Cv ccdconfig: ioctl (CCDIOCSET): /dev/ccd0c: Inappropriate file type or format <8:56pm>thunder/root:~#newfs /dev/da1e /dev/da1e: 1310720 sectors in 320 cylinders of 1 tracks, 4096 sectors 640.0MB in 15 cyl groups (22 c/g, 44.00MB/g, 10624 i/g) super-block backups (for fsck -b #) at: 32, 90144, 180256, 270368, 360480, 450592, 540704, 630816, 720928, 811040, 901152, 991264, 1081376, 1171488, 1261600 <8:56pm>thunder/root:~#newfs /dev/da2e /dev/da2e: 1310720 sectors in 320 cylinders of 1 tracks, 4096 sectors 640.0MB in 15 cyl groups (22 c/g, 44.00MB/g, 10624 i/g) super-block backups (for fsck -b #) at: 32, 90144, 180256, 270368, 360480, 450592, 540704, 630816, 720928, 811040, 901152, 991264, 1081376, 1171488, 1261600 <8:57pm>thunder/root:~#ccdconfig -Cv ccd0: 2 components (da1e, da2e), 2620928 blocks interleaved at 256 blocks <8:57pm>thunder/root:~#newfs /dev/ccd0c Warning: 512 sector(s) in last cylinder unallocated /dev/ccd0c: 2620928 sectors in 640 cylinders of 1 tracks, 4096 sectors 1279.8MB in 30 cyl groups (22 c/g, 44.00MB/g, 10624 i/g) super-block backups (for fsck -b #) at: 32, 90144, 180256, 270368, 360480, 450592, 540704, 630816, 720928, 811040, 901152, 991264, 1081376, 1171488, 1261600, 1351712, 1441824, 1531936, 1622048, 1712160, 1802272, 1892384, 1982496, 2072608, 2162720, 2252832, 2342944, 2433056, 2523168, 2613280 newfs: ioctl (WDINFO): No such process newfs: /dev/ccd0c: can't rewrite disk label <8:57pm>thunder/root:~#fsck /dev/ccd0c ** /dev/ccd0c ** Last Mounted on ** Phase 1 - Check Blocks and Sizes ** Phase 2 - Check Pathnames ** Phase 3 - Check Connectivity ** Phase 4 - Check Reference Counts ** Phase 5 - Check Cyl groups 1 files, 1 used, 1270126 free (14 frags, 158764 blocks, 0.0% fragmentation) <...> Are you sure the device nodes you're passing to newfs actually exist? Do you see a ccdX device show up in, say, systat when you do your ccdconfig? I'm confused. Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Mar 28 19:42:40 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id B30AC37B71F for ; Wed, 28 Mar 2001 19:42:37 -0800 (PST) (envelope-from jdp@wall.polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.11.1/8.11.1) with ESMTP id f2T3gbV13310 for ; Wed, 28 Mar 2001 19:42:37 -0800 (PST) (envelope-from jdp@wall.polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.11.3/8.11.0) id f2T3gae08020; Wed, 28 Mar 2001 19:42:36 -0800 (PST) (envelope-from jdp) Date: Wed, 28 Mar 2001 19:42:36 -0800 (PST) Message-Id: <200103290342.f2T3gae08020@vashon.polstra.com> To: alpha@freebsd.org From: John Polstra Reply-To: alpha@freebsd.org Subject: Re: Is `ccd' broken on Alpha? In-Reply-To: <20010328152453.A15677@hub.freebsd.org> References: <20010328000954.C18676@dragon.nuxi.com> <15042.28453.158495.901316@grasshopper.cs.duke.edu> <20010328151503.A88970@dragon.nuxi.com> <20010328152453.A15677@hub.freebsd.org> Organization: Polstra & Co., Seattle, WA Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In article <20010328152453.A15677@hub.freebsd.org>, David O'Brien wrote: > On Wed, Mar 28, 2001 at 03:15:03PM -0800, David O'Brien wrote: > > On Wed, Mar 28, 2001 at 06:09:25PM -0500, Andrew Gallatin wrote: > > > > > It works fine for me using 'c' paritions. > > > > In general one should not use the `c' partition. Aren't you also seeing > > disklabel complain that your `c' partition type isn't "unused"? > > Sigh. Using `c' rather than `e' (or [abd-h]) as the ccd partition works. > So there is definitely something being treated differently on the Alpha > than the i386 platform. Could it be simply that there are no slices on the alpha? So the `c' partition really represents the whole disk on that platform. But on the i386 it would just represent the slice, which in general won't be the same as the whole disk. Warning: every time I think I understand the differences between da0, da0c, da0s1, and da0s1c I find a counter-example. So I might be completely off track here (no pun intended). John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Mar 28 20:34:48 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 BE92437B71F for ; Wed, 28 Mar 2001 20:34:45 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.3/8.11.1) id f2T4YhU91859; Wed, 28 Mar 2001 20:34:43 -0800 (PST) (envelope-from obrien) Date: Wed, 28 Mar 2001 20:34:37 -0800 From: "David O'Brien" To: Andrew Gallatin Cc: freebsd-alpha@freebsd.org Subject: Re: Is `ccd' broken on Alpha? Message-ID: <20010328203437.A91793@dragon.nuxi.com> Reply-To: obrien@freebsd.org References: <20010328000954.C18676@dragon.nuxi.com> <15042.28453.158495.901316@grasshopper.cs.duke.edu> <20010328151704.A89023@dragon.nuxi.com> <15042.37922.136513.58056@grasshopper.cs.duke.edu> <15042.39091.263461.18565@grasshopper.cs.duke.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <15042.39091.263461.18565@grasshopper.cs.duke.edu>; from gallatin@cs.duke.edu on Wed, Mar 28, 2001 at 09:06:43PM -0500 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, Mar 28, 2001 at 09:06:43PM -0500, Andrew Gallatin wrote: > It works again on da1e/da2e for me. I'm running the top of the tree; > world built this afternoon. That actually isn't the issue. :-) Can you repeat this, but use ccd0e rather than ccd0c? Warning you may need to do this: ccdconfig -C disklabel ccd0 >/tmp/foo disklabel -Rr ccd0 /tmp/foo disklabel -e ccd0 # change the 3 partitions to 8, and duplicate `c' to `e' then: newfs /dev/ccd0e fsck /dev/ccd0e To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Mar 29 8:53:50 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 02A5637B71A for ; Thu, 29 Mar 2001 08:53:48 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.3/8.11.1) id f2TGrlB32274 for alpha@freebsd.org; Thu, 29 Mar 2001 08:53:47 -0800 (PST) (envelope-from obrien) Date: Thu, 29 Mar 2001 08:53:47 -0800 From: "David O'Brien" To: alpha@freebsd.org Subject: Re: Is `ccd' broken on Alpha? Message-ID: <20010329085347.A32246@dragon.nuxi.com> Reply-To: alpha@freebsd.org References: <20010328000954.C18676@dragon.nuxi.com> <15042.28453.158495.901316@grasshopper.cs.duke.edu> <20010328151503.A88970@dragon.nuxi.com> <20010328152453.A15677@hub.freebsd.org> <200103290342.f2T3gae08020@vashon.polstra.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200103290342.f2T3gae08020@vashon.polstra.com>; from jdp@polstra.com on Wed, Mar 28, 2001 at 07:42:36PM -0800 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, Mar 28, 2001 at 07:42:36PM -0800, John Polstra wrote: > > Could it be simply that there are no slices on the alpha? So the `c' > partition really represents the whole disk on that platform. But on > the i386 it would just represent the slice, which in general won't be > the same as the whole disk. It is possible it has something to do with the slice code. When I tested it yesterday on on an i386 box, I used ``disklabel -rw daX auto'' before ccdconfig'ing them. So they should have been dangeriously/truely dedicated. But we do know there is weird label differences between Alpha and i386.... -- -- David (obrien@FreeBSD.org) Disclaimer: Not speaking for FreeBSD, just expressing my own opinion. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Mar 29 10:46:25 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 93A9A37B71F for ; Thu, 29 Mar 2001 10:46:20 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.11.1/8.11.1) with ESMTP id f2TIkKV17025; Thu, 29 Mar 2001 10:46:20 -0800 (PST) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Thu, 29 Mar 2001 10:46:19 -0800 (PST) Organization: Polstra & Co., Inc. From: John Polstra To: alpha@freebsd.org Subject: RC1 looks OK on AlphaPC 164LX Cc: Wilko Bulte Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Wilko asked me to try 4.3-RC1 on my AlphaPC 164LX. I don't have the bandwidth to try the ISO image, but I upgraded via make world. It all seems to work fine. I made boot floppies from the latest floppy images on ftp.freebsd.org. Note, these are not RC1 images -- they are BETAs from March 13. They booted fine and got me into what appeared to be a functional installer. If I knew how to make a bootable alpha CD, I'd try that. El Torito doesn't work. I know this machine can boot from CD, because that's how I installed Tru64 on the other hard drive. On startup, amd is causing one unaligned access message. That has been going on for quite a long time, and it doesn't appear to cause any problems. The dmesg output is appended to this mail. It is from my custom kernel, not from GENERIC. John Copyright (c) 1992-2001 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 4.3-RC #0: Wed Mar 28 16:28:44 PST 2001 jdp@alpha.polstra.com:/usr/src/sys/compile/ALPHA EB164 Digital AlphaPC 164LX 533 MHz, 531MHz 8192 byte page size, 1 processor. CPU: EV56 (21164A) major=7 minor=2 extensions=0x1 OSF PAL rev: 0x1000200020117 real memory = 132046848 (128952K bytes) avail memory = 123224064 (120336K bytes) Preloaded elf kernel "kernel" at 0xfffffc0000676000. cia0: Pyxis, pass 1 cia0: extended capabilities: 1 pcib0: <2117x PCI host bus adapter> on cia0 pci0: on pcib0 dc0: port 0x1100-0x117f mem 0x82271100-0x8227117f irq 0 at device 6.0 on pci0 dc0: interrupting at CIA irq 0 dc0: Ethernet address: 08:00:2b:c5:3b:2d miibus0: on dc0 dcphy0: on miibus0 dcphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto sym0: <875> port 0x1000-0x10ff mem 0x82270000-0x82270fff,0x82271000-0x822710ff irq 1 at device 7.0 on pci0 sym0: Symbios NVRAM, ID 7, Fast-20, SE, parity checking sym0: open drain IRQ line driver, using on-chip SRAM sym0: using LOAD/STORE-based firmware. sym0: interrupting at CIA irq 1 isab0: at device 8.0 on pci0 isa0: on isab0 pci0: at 9.0 irq 3 pci0: at 11.0 irq 5 mcclock0: at port 0x70-0x71 on isa0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: irq 1 on atkbdc0 atkbd0: interrupting at ISA irq 1 psm0: irq 12 on atkbdc0 psm0: interrupting at ISA irq 12 psm0: model Generic PS/2 mouse, device ID 0 vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: interrupting at ISA irq 6 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 sio0 at port 0x3f8-0x3ff irq 4 on isa0 sio0: type 16550A sio0: interrupting at ISA irq 4 sio1: reserved for low-level i/o Timecounter "alpha" frequency 533177024 Hz IPsec: Initialized Security Association Processing. Waiting 2 seconds for SCSI devices to settle (noperiph:sym0:0:-1:-1): SCSI BUS reset delivered. Mounting root from ufs:/dev/da0f cd0 at sym0 bus 0 target 5 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 20.000MB/s transfers (20.000MHz, offset 16) cd0: Attempt to query device size failed: NOT READY, Medium not present da1 at sym0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-3 device da1: 40.000MB/s transfers (20.000MHz, offset 16, 16bit), Tagged Queueing Enabled da1: 8748MB (17916240 512 byte sectors: 255H 63S/T 1115C) da0 at sym0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing Enabled da0: 8715MB (17850000 512 byte sectors: 255H 63S/T 1111C) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Mar 29 11:51:59 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from winston.osd.bsdi.com (winston.osd.bsdi.com [204.216.27.229]) by hub.freebsd.org (Postfix) with ESMTP id 5E16437B71A for ; Thu, 29 Mar 2001 11:51:57 -0800 (PST) (envelope-from jkh@osd.bsdi.com) Received: from localhost (jkh@localhost [127.0.0.1]) by winston.osd.bsdi.com (8.11.3/8.11.2) with ESMTP id f2TJpcg92765; Thu, 29 Mar 2001 11:51:38 -0800 (PST) (envelope-from jkh@osd.bsdi.com) To: jdp@polstra.com Cc: alpha@FreeBSD.ORG, wkb@freebie.demon.nl Subject: Re: RC1 looks OK on AlphaPC 164LX In-Reply-To: References: X-Mailer: Mew version 1.94.1 on Emacs 20.7 / Mule 4.0 (HANANOEN) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20010329115138R.jkh@osd.bsdi.com> Date: Thu, 29 Mar 2001 11:51:38 -0800 From: Jordan Hubbard X-Dispatcher: imput version 20000228(IM140) Lines: 7 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > If I knew how to make a bootable alpha CD, I'd try that. El Torito > doesn't work. I know this machine can boot from CD, because that's > how I installed Tru64 on the other hard drive. You can use setcdboot from ports/sysutils/setcdboot. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Mar 29 11:58:48 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 92D1937B71A for ; Thu, 29 Mar 2001 11:58:41 -0800 (PST) (envelope-from jdp@wall.polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.11.1/8.11.1) with ESMTP id f2TJwdV17563; Thu, 29 Mar 2001 11:58:39 -0800 (PST) (envelope-from jdp@wall.polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.11.3/8.11.0) id f2TJwdw09697; Thu, 29 Mar 2001 11:58:39 -0800 (PST) (envelope-from jdp) Date: Thu, 29 Mar 2001 11:58:39 -0800 (PST) Message-Id: <200103291958.f2TJwdw09697@vashon.polstra.com> To: alpha@freebsd.org From: John Polstra Cc: jkh@osd.bsdi.com Subject: Re: RC1 looks OK on AlphaPC 164LX In-Reply-To: <20010329115138R.jkh@osd.bsdi.com> References: <20010329115138R.jkh@osd.bsdi.com> Organization: Polstra & Co., Seattle, WA Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In article <20010329115138R.jkh@osd.bsdi.com>, Jordan Hubbard wrote: > > If I knew how to make a bootable alpha CD, I'd try that. El Torito > > doesn't work. I know this machine can boot from CD, because that's > > how I installed Tru64 on the other hard drive. > > You can use setcdboot from ports/sysutils/setcdboot. Thanks! So when I run setcdboot, I point it at /boot/loader inside the ISO filesystem? John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Mar 29 11:59:38 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 486D637B71F; Thu, 29 Mar 2001 11:59:34 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id OAA05581; Thu, 29 Mar 2001 14:59:33 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.3/8.9.1) id f2TJx3r81733; Thu, 29 Mar 2001 14:59: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: <15043.37894.906784.213672@grasshopper.cs.duke.edu> Date: Thu, 29 Mar 2001 14:59:02 -0500 (EST) To: obrien@FreeBSD.ORG Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: Is `ccd' broken on Alpha? In-Reply-To: <20010328203437.A91793@dragon.nuxi.com> References: <20010328000954.C18676@dragon.nuxi.com> <15042.28453.158495.901316@grasshopper.cs.duke.edu> <20010328151704.A89023@dragon.nuxi.com> <15042.37922.136513.58056@grasshopper.cs.duke.edu> <15042.39091.263461.18565@grasshopper.cs.duke.edu> <20010328203437.A91793@dragon.nuxi.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 David O'Brien writes: > On Wed, Mar 28, 2001 at 09:06:43PM -0500, Andrew Gallatin wrote: > > It works again on da1e/da2e for me. I'm running the top of the tree; > > world built this afternoon. > > That actually isn't the issue. :-) > Can you repeat this, but use ccd0e rather than ccd0c? Do'h. Ok, I see the problem. bounds_check_with_label() is basically commented out and always returns -1 on alpha (without marking an error in the buf). I think ccd is the only caller of bounds_check_with_label() (vinum has its own version). Uncommenting it seems to fix the problem. Try the appended patch... I'm not really sure I understand why it was commented out in the first place; but I don't know a lot about disklabel handling. Assuming you have a label that looks like this on a pc: 8 partitions: # size offset fstype [fsize bsize bps/cpg] c: 2620928 0 unused 0 0 # (Cyl. 0 - 1279*) e: 2620928 0 4.2BSD 1024 8192 22 # (Cyl. 0 - 1279*) What happens if you do dd if=/dev/zero of=/dev/ccd0e count=1 ? On the alpha, it blows away the label and leaves me with this: 3 partitions: # size offset fstype [fsize bsize bps/cpg] c: 2620928 0 4.2BSD 0 0 0 # (Cyl. 0 - 1279*) Warning, partition c is not marked as unused! Warning, An incorrect partition c may cause problems for standard system utilities Cheers, Drew Index: alpha/alpha/machdep.c =================================================================== RCS file: /home/ncvs/src/sys/alpha/alpha/machdep.c,v retrieving revision 1.119 diff -u -r1.119 machdep.c --- alpha/alpha/machdep.c 2001/03/28 09:03:19 1.119 +++ alpha/alpha/machdep.c 2001/03/29 19:38:25 @@ -2020,7 +2020,6 @@ int bounds_check_with_label(struct bio *bp, struct disklabel *lp, int wlabel) { -#if 0 struct partition *p = lp->d_partitions + dkpart(bp->bio_dev); int labelsect = lp->d_partitions[0].p_offset; int maxsz = p->p_size, @@ -2067,7 +2066,7 @@ bad: bp->bio_flags |= BIO_ERROR; -#endif + return(-1); } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Mar 29 12: 2: 2 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from winston.osd.bsdi.com (winston.osd.bsdi.com [204.216.27.229]) by hub.freebsd.org (Postfix) with ESMTP id A61A937B71D for ; Thu, 29 Mar 2001 12:01:59 -0800 (PST) (envelope-from jkh@osd.bsdi.com) Received: from localhost (jkh@localhost [127.0.0.1]) by winston.osd.bsdi.com (8.11.3/8.11.2) with ESMTP id f2TK1sg92867; Thu, 29 Mar 2001 12:01:54 -0800 (PST) (envelope-from jkh@osd.bsdi.com) To: jdp@polstra.com Cc: alpha@freebsd.org Subject: Re: RC1 looks OK on AlphaPC 164LX In-Reply-To: <200103291958.f2TJwdw09697@vashon.polstra.com> References: <20010329115138R.jkh@osd.bsdi.com> <200103291958.f2TJwdw09697@vashon.polstra.com> X-Mailer: Mew version 1.94.1 on Emacs 20.7 / Mule 4.0 (HANANOEN) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20010329120153C.jkh@osd.bsdi.com> Date: Thu, 29 Mar 2001 12:01:53 -0800 From: Jordan Hubbard X-Dispatcher: imput version 20000228(IM140) Lines: 6 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Thanks! So when I run setcdboot, I point it at /boot/loader inside > the ISO filesystem? /boot/cdboot actually, but yes. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Mar 29 12: 9:23 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 E813837B719 for ; Thu, 29 Mar 2001 12:09:20 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.3/8.11.1) id f2TK95A34553; Thu, 29 Mar 2001 12:09:05 -0800 (PST) (envelope-from obrien) Date: Thu, 29 Mar 2001 12:09:05 -0800 From: "David O'Brien" To: Andrew Gallatin Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: Is `ccd' broken on Alpha? Message-ID: <20010329120905.A33788@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <20010328000954.C18676@dragon.nuxi.com> <15042.28453.158495.901316@grasshopper.cs.duke.edu> <20010328151704.A89023@dragon.nuxi.com> <15042.37922.136513.58056@grasshopper.cs.duke.edu> <15042.39091.263461.18565@grasshopper.cs.duke.edu> <20010328203437.A91793@dragon.nuxi.com> <15043.37894.906784.213672@grasshopper.cs.duke.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <15043.37894.906784.213672@grasshopper.cs.duke.edu>; from gallatin@cs.duke.edu on Thu, Mar 29, 2001 at 02:59:02PM -0500 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, Mar 29, 2001 at 02:59:02PM -0500, Andrew Gallatin wrote: > Do'h. Ok, I see the problem. bounds_check_with_label() is basically *Sigh*. Of course there is no rev 1.1 or 1.2 (and their log message wasn't saved when those revs were diked out) to help explain _why_. Crap like this is really irritating on the Alpha... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Mar 29 12:15:48 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 0CA2A37B71B; Thu, 29 Mar 2001 12:15:45 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id PAA06104; Thu, 29 Mar 2001 15:15:43 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.3/8.9.1) id f2TKFDn81797; Thu, 29 Mar 2001 15:15:13 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15043.38865.445922.245686@grasshopper.cs.duke.edu> Date: Thu, 29 Mar 2001 15:15:13 -0500 (EST) To: obrien@FreeBSD.ORG Cc: freebsd-alpha@FreeBSD.ORG, dfr@nlsystems.com Subject: bounds_check_with_label() on alpha In-Reply-To: <20010329120905.A33788@dragon.nuxi.com> References: <20010328000954.C18676@dragon.nuxi.com> <15042.28453.158495.901316@grasshopper.cs.duke.edu> <20010328151704.A89023@dragon.nuxi.com> <15042.37922.136513.58056@grasshopper.cs.duke.edu> <15042.39091.263461.18565@grasshopper.cs.duke.edu> <20010328203437.A91793@dragon.nuxi.com> <15043.37894.906784.213672@grasshopper.cs.duke.edu> <20010329120905.A33788@dragon.nuxi.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 David O'Brien writes: > On Thu, Mar 29, 2001 at 02:59:02PM -0500, Andrew Gallatin wrote: > > Do'h. Ok, I see the problem. bounds_check_with_label() is basically > > *Sigh*. Of course there is no rev 1.1 or 1.2 (and their log message > wasn't saved when those revs were diked out) to help explain _why_. I think it was commented out in the original merged netbsd/alpha freebsd/i386 machdep.c. It was probably commented out because alpha didn't have enough infastructure to allow it to compile & Doug wanted to just keep moving until he got something booting on SimOs & then it was forgotten. I don't blame him. Doug? > Crap like this is really irritating on the Alpha... Yes. But as more people use it, it happens less & less often. Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Mar 29 12:19:32 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from srv1.cosmo-project.de (srv1.cosmo-project.de [213.83.6.106]) by hub.freebsd.org (Postfix) with ESMTP id 2501437B71B for ; Thu, 29 Mar 2001 12:19:26 -0800 (PST) (envelope-from ticso@mail.cicely.de) Received: from mail.cicely.de (cicely20 [10.1.1.22]) by srv1.cosmo-project.de (8.11.0/8.11.0) with ESMTP id f2TKJNK01613 for ; Thu, 29 Mar 2001 22:19:24 +0200 (CEST) Received: (from ticso@localhost) by mail.cicely.de (8.11.0/8.11.0) id f2TKJh229799 for freebsd-alpha@freebsd.org; Thu, 29 Mar 2001 22:19:43 +0200 (CEST) Date: Thu, 29 Mar 2001 22:19:42 +0200 From: Bernd Walter To: freebsd-alpha@freebsd.org Subject: -current boot panic Message-ID: <20010329221942.A29139@cicely20.cicely.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Source is from yesterday on a PC164 ok boot -v Entering kernel at 0xfffffc000032a940... sio1: gdb debugging port Unrecognized boot flag '0'. Copyright (c) 1992-2001 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. Setting atkbd 0 at to atkbdc (string) Setting atkbd 0 irq to 1 (int) Setting atkbdc 0 at to isa (string) Setting atkbdc 0 port to 96 (int) Setting fd 0 at to fdc0 (string) Setting fd 0 drive to 0 (int) Setting fdc 0 at to isa (string) Setting fdc 0 drq to 2 (int) Setting fdc 0 irq to 6 (int) Setting fdc 0 port to 1008 (int) Setting mcclock 0 at to isa (string) Setting mcclock 0 port to 112 (int) Setting ppc 0 at to isa (string) Setting ppc 0 irq to 7 (int) Setting psm 0 at to atkbdc (string) Setting psm 0 irq to 12 (int) Setting sc 0 at to isa (string) Setting sio 0 at to isa (string) Setting sio 0 irq to 4 (int) Setting sio 0 port to 1016 (int) Setting sio 1 at to isa (string) Setting sio 1 flags to 80 (int) Setting sio 1 irq to 3 (int) Setting sio 1 port to 760 (int) Setting vga 0 at to isa (string) fatal kernel trap: trap entry = 0x2 (memory management fault) a0 = 0x28 a1 = 0x1 a2 = 0x1 pc = 0xfffffc00003f53d0 ra = 0xfffffc00003f53cc curproc = 0xfffffc0000687080 pid = 0, comm = Stopped at 0xfffffc00003f53d0: stq s4,0x28(s2) <0x28> db> trace (null)() at 0xfffffc00003f53d0 machine alpha cpu EV5 ident "CICELY9" maxusers 32 #hints "GENERIC.hints" makeoptions DEBUG=-g #Build kernel with gdb(1) debug symbols options NSWAPDEV=20 #options MAXDSIZ="137438953472L" # 128G #options DFLDSIZ="137438953472L" # 128G options DDB options BREAK_TO_DEBUGGER #a BREAK on a comconsole goes to options DEC_EB164 # EB164, PC164, PC164LX, PC164SX options INET #InterNETworking options INET6 #IPv6 communications protocols #options KTR #options KTR_EXTEND #options KTR_ENTRIES=1024 #options KTR_COMPILE=0x3fffff #options KTR_MASK=0x201208 #options KTR_CPUMASK=0x3 #options KTR_VERBOSE #options MUTEX_DEBUG options WITNESS #options WITNESS_DDB options WITNESS_SKIPSPIN #options DIAGNOSTIC options INVARIANTS options INVARIANT_SUPPORT options SOFTUPDATES options DEVFS options FFS options NFS options PROCFS options COMPAT_43 options SCSI_DELAY=15000 options UCONSOLE options KTRACE options SYSVSHM options SYSVMSG options SYSVSEM options P1003_1B options _KPOSIX_PRIORITY_SCHEDULING device random device isa device pci device fdc device ata device atadisk device sym device scbus device da device sa device cd device pass device mcclock device sio device miibus device xl device dc device loop device ether device pty device bpf device md -- B.Walter COSMO-Project http://www.cosmo-project.de ticso@cicely.de Usergroup info@cosmo-project.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Mar 29 12:26:25 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 A235D37B756 for ; Thu, 29 Mar 2001 12:26:16 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id PAA06521; Thu, 29 Mar 2001 15:26:15 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.3/8.9.1) id f2TKPjn81816; Thu, 29 Mar 2001 15:25:45 -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: <15043.39496.927622.874793@grasshopper.cs.duke.edu> Date: Thu, 29 Mar 2001 15:25:44 -0500 (EST) To: Bernd Walter Cc: freebsd-alpha@freebsd.org Subject: Re: -current boot panic In-Reply-To: <20010329221942.A29139@cicely20.cicely.de> References: <20010329221942.A29139@cicely20.cicely.de> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Bernd Walter writes: > > trap entry = 0x2 (memory management fault) > a0 = 0x28 > a1 = 0x1 > a2 = 0x1 > pc = 0xfffffc00003f53d0 > ra = 0xfffffc00003f53cc > curproc = 0xfffffc0000687080 > pid = 0, comm = > > Stopped at 0xfffffc00003f53d0: stq s4,0x28(s2) <0x28> How about running gdb on the kernel (with symbols) and mapping 0xfffffc00003f53d0 to a function & line number? FWIW, yesterday's -current works fine here. Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Mar 29 12:41:17 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 EA5A637B71F for ; Thu, 29 Mar 2001 12:41:15 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.3/8.11.1) id f2TKf8a35034; Thu, 29 Mar 2001 12:41:08 -0800 (PST) (envelope-from obrien) Date: Thu, 29 Mar 2001 12:41:08 -0800 From: "David O'Brien" To: John Polstra Cc: alpha@freebsd.org Subject: Re: RC1 looks OK on AlphaPC 164LX Message-ID: <20010329124107.A35008@dragon.nuxi.com> Reply-To: alpha@freebsd.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from jdp@polstra.com on Thu, Mar 29, 2001 at 10:46:19AM -0800 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, Mar 29, 2001 at 10:46:19AM -0800, John Polstra wrote: > If I knew how to make a bootable alpha CD, I'd try that. Here is how I made the 4.3-BETA ISOs: #! /bin/sh -x ISO=/release/43.iso RELNAME=4.3-BETA-20010319 ISOROOT=/release/${RELNAME}/R/cdrom/disc1 ISOTITLE="FreeBSD/AXP_${RELNAME}" sh -x /usr/share/examples/worm/makecdfs.sh ${ISOTITLE} ${ISOROOT} ${ISO} "(c)2001 BSDi " setcdboot ${ISO} /boot/cdboot To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Mar 29 13: 0:18 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from srv1.cosmo-project.de (srv1.cosmo-project.de [213.83.6.106]) by hub.freebsd.org (Postfix) with ESMTP id ACE6937B71A for ; Thu, 29 Mar 2001 13:00:10 -0800 (PST) (envelope-from ticso@mail.cicely.de) Received: from mail.cicely.de (cicely20 [10.1.1.22]) by srv1.cosmo-project.de (8.11.0/8.11.0) with ESMTP id f2TL07K01929; Thu, 29 Mar 2001 23:00:07 +0200 (CEST) Received: (from ticso@localhost) by mail.cicely.de (8.11.0/8.11.0) id f2TL0N029995; Thu, 29 Mar 2001 23:00:23 +0200 (CEST) Date: Thu, 29 Mar 2001 23:00:23 +0200 From: Bernd Walter To: Andrew Gallatin Cc: Bernd Walter , freebsd-alpha@FreeBSD.ORG Subject: Re: -current boot panic Message-ID: <20010329230022.B29139@cicely20.cicely.de> References: <20010329221942.A29139@cicely20.cicely.de> <15043.39496.927622.874793@grasshopper.cs.duke.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <15043.39496.927622.874793@grasshopper.cs.duke.edu>; from gallatin@cs.duke.edu on Thu, Mar 29, 2001 at 03:25:44PM -0500 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, Mar 29, 2001 at 03:25:44PM -0500, Andrew Gallatin wrote: > > Bernd Walter writes: > > > > trap entry = 0x2 (memory management fault) > > a0 = 0x28 > > a1 = 0x1 > > a2 = 0x1 > > pc = 0xfffffc00003f53d0 > > ra = 0xfffffc00003f53cc > > curproc = 0xfffffc0000687080 > > pid = 0, comm = > > > > Stopped at 0xfffffc00003f53d0: stq s4,0x28(s2) <0x28> > > How about running gdb on the kernel (with symbols) and mapping > 0xfffffc00003f53d0 to a function & line number? Mmm - yes - sounds logical. I don't know how to do with gdb here is the relevant objdump -S output: /* * The WITNESS-enabled diagnostic code. */ static void witness_initialize(void *dummy __unused) { struct lock_object *lock; struct witness_order_list_entry *order; struct witness *w, *w1; int i; /* * We have to release Giant before initializing its witness * structure so that WITNESS doesn't get confused. */ mtx_unlock(&Giant); fffffc00003f51e4: 40 00 28 a4 ldq t0,64(t7) fffffc00003f51e8: 09 00 20 f4 bne t0,fffffc00003f5210 fffffc00003f51ec: 80 15 1d a6 ldq a0,5504(gp) fffffc00003f51f0: 78 15 3d a6 ldq a1,5496(gp) fffffc00003f51f4: 70 15 5d a6 ldq a2,5488(gp) fffffc00003f51f8: 1c 01 7f 22 lda a3,284(zero) fffffc00003f51fc: f0 ac 7d a7 ldq t12,-21264(gp) fffffc00003f5200: c7 4a 5b 6b jsr ra,(t12),fffffc00003f7d20 fffffc00003f5204: 23 00 ba 27 ldah gp,35(ra) fffffc00003f5208: c4 e6 bd 23 lda gp,-6460(gp) fffffc00003f520c: 00 00 e0 2f unop fffffc00003f5210: 20 c5 3d a5 ldq s0,-15072(gp) fffffc00003f5214: 70 15 5d a5 ldq s1,5488(gp) fffffc00003f5218: 10 04 e9 47 mov s0,a0 fffffc00003f521c: 01 00 3f 22 lda a1,1(zero) fffffc00003f5220: 12 04 ea 47 mov s1,a2 fffffc00003f5224: 1c 01 7f 22 lda a3,284(zero) fffffc00003f5228: b0 a9 7d a7 ldq t12,-22096(gp) fffffc00003f522c: 74 60 5b 6b jsr ra,(t12),fffffc00003ed400 fffffc00003f5230: 23 00 ba 27 ldah gp,35(ra) fffffc00003f5234: 98 e6 bd 23 lda gp,-6504(gp) fffffc00003f5238: 10 04 e9 47 mov s0,a0 fffffc00003f523c: 11 04 ff 47 clr a1 fffffc00003f5240: 50 c0 7d a7 ldq t12,-16304(gp) fffffc00003f5244: 36 60 5b 6b jsr ra,(t12),fffffc00003ed320 fffffc00003f5248: 23 00 ba 27 ldah gp,35(ra) fffffc00003f524c: 80 e6 bd 23 lda gp,-6528(gp) fffffc00003f5250: 10 04 e9 47 mov s0,a0 fffffc00003f5254: 11 04 ff 47 clr a1 fffffc00003f5258: 12 04 ea 47 mov s1,a2 fffffc00003f525c: 1c 01 7f 22 lda a3,284(zero) fffffc00003f5260: b8 a1 7d a7 ldq t12,-24136(gp) fffffc00003f5264: 3e 46 5b 6b jsr ra,(t12),fffffc00003f6b60 fffffc00003f5268: 23 00 ba 27 ldah gp,35(ra) fffffc00003f526c: 60 e6 bd 23 lda gp,-6560(gp) } static __inline int atomic_cmpset_rel_ptr(volatile void *dst, void *exp, void *src) { fffffc00003f5270: 40 00 28 a4 ldq t0,64(t7) fffffc00003f5274: 04 00 5f 20 lda t1,4(zero) fffffc00003f5278: 30 00 69 ac ldq_l t2,48(s0) fffffc00003f527c: a3 05 61 40 cmpeq t2,t0,t2 fffffc00003f5280: 03 00 60 e4 beq t2,fffffc00003f5290 fffffc00003f5284: 03 04 e2 47 mov t1,t2 fffffc00003f5288: 30 00 69 bc stq_c t2,48(s0) fffffc00003f528c: f9 30 67 e4 beq t2,fffffc00005c1674 fffffc00003f5290: 01 04 e3 47 mov t2,t0 * XXX dfr: NetBSD originally had mb instead of wmb for * alpha_wmb(). I'm not sure why so I'm leaving it alone. I * think it should be safe to use wmb though. */ __asm__ __volatile__ ("mb"); fffffc00003f5294: 00 40 00 60 mb atomic_cmpset_rel_ptr(volatile void *dst, void *exp, void *src) { return (atomic_cmpset_rel_long((volatile u_long *)dst, (u_long)exp, (u_long)src)); fffffc00003f5298: 01 00 3f 40 addl t0,zero,t0 fffffc00003f529c: 08 00 20 f4 bne t0,fffffc00003f52c0 fffffc00003f52a0: 10 04 e9 47 mov s0,a0 fffffc00003f52a4: 11 04 ff 47 clr a1 fffffc00003f52a8: 12 04 ea 47 mov s1,a2 fffffc00003f52ac: 1c 01 7f 22 lda a3,284(zero) fffffc00003f52b0: 80 b6 7d a7 ldq t12,-18816(gp) fffffc00003f52b4: 1a 5f 5b 6b jsr ra,(t12),fffffc00003fcf20 fffffc00003f52b8: 23 00 ba 27 ldah gp,35(ra) fffffc00003f52bc: 10 e6 bd 23 lda gp,-6640(gp) mtx_assert(&Giant, MA_NOTOWNED); fffffc00003f52c0: 20 c5 1d a6 ldq a0,-15072(gp) fffffc00003f52c4: 02 00 3f 22 lda a1,2(zero) fffffc00003f52c8: 70 15 5d a6 ldq a2,5488(gp) fffffc00003f52cc: 1d 01 7f 22 lda a3,285(zero) fffffc00003f52d0: b0 a9 7d a7 ldq t12,-22096(gp) fffffc00003f52d4: 4a 60 5b 6b jsr ra,(t12),fffffc00003ed400 fffffc00003f52d8: 23 00 ba 27 ldah gp,35(ra) fffffc00003f52dc: f0 e5 bd 23 lda gp,-6672(gp) STAILQ_INSERT_HEAD(&all_locks, &all_mtx.mtx_object, lo_list); fffffc00003f52e0: 48 13 5d a4 ldq t1,4936(gp) fffffc00003f52e4: 60 a7 7d a4 ldq t2,-22688(gp) fffffc00003f52e8: 00 00 23 a4 ldq t0,0(t2) fffffc00003f52ec: 20 00 22 b4 stq t0,32(t1) fffffc00003f52f0: 03 00 20 f4 bne t0,fffffc00003f5300 fffffc00003f52f4: 01 14 44 40 addq t1,0x20,t0 fffffc00003f52f8: 08 00 23 b4 stq t0,8(t2) fffffc00003f52fc: 00 00 e0 2f unop fffffc00003f5300: 60 a7 5d a4 ldq t1,-22688(gp) fffffc00003f5304: 48 13 3d a4 ldq t0,4936(gp) fffffc00003f5308: 00 00 22 b4 stq t0,0(t1) mtx_init(&w_mtx, "witness lock", MTX_SPIN | MTX_QUIET | MTX_NOWITNESS); fffffc00003f530c: 70 13 1d a6 ldq a0,4976(gp) fffffc00003f5310: 68 15 3d a6 ldq a1,5480(gp) fffffc00003f5314: 0b 00 5f 22 lda a2,11(zero) fffffc00003f5318: 10 97 7d a7 ldq t12,-26864(gp) fffffc00003f531c: 80 60 5b 6b jsr ra,(t12),fffffc00003ed520 fffffc00003f5320: 23 00 ba 27 ldah gp,35(ra) fffffc00003f5324: a8 e5 bd 23 lda gp,-6744(gp) for (i = 0; i < WITNESS_COUNT; i++) fffffc00003f5328: 09 04 ff 47 clr s0 fffffc00003f532c: 68 13 5d a5 ldq s1,4968(gp) witness_free(&w_data[i]); fffffc00003f5330: 30 d7 20 49 sll s0,0x6,a0 fffffc00003f5334: 10 04 0a 42 addq a0,s1,a0 fffffc00003f5338: 9b 0a 40 d3 bsr ra,fffffc00003f7da8 fffffc00003f533c: 09 30 20 41 addl s0,0x1,s0 fffffc00003f5340: a1 fd 38 41 cmple s0,0xc7,t0 fffffc00003f5344: fa ff 3f f4 bne t0,fffffc00003f5330 for (i = 0; i < WITNESS_CHILDCOUNT; i++) fffffc00003f5348: 09 04 ff 47 clr s0 fffffc00003f534c: 60 13 7d a5 ldq s2,4960(gp) fffffc00003f5350: 1f 03 5f 21 lda s1,799(zero) fffffc00003f5354: 00 00 e0 2f unop fffffc00003f5358: 1f 04 ff 47 nop fffffc00003f535c: 00 00 e0 2f unop witness_child_free(&w_childdata[i]); fffffc00003f5360: 30 d7 20 49 sll s0,0x6,a0 fffffc00003f5364: 10 04 0b 42 addq a0,s2,a0 fffffc00003f5368: f7 0a 40 d3 bsr ra,fffffc00003f7f48 fffffc00003f536c: 09 30 20 41 addl s0,0x1,s0 fffffc00003f5370: a1 0d 2a 41 cmple s0,s1,t0 fffffc00003f5374: fa ff 3f f4 bne t0,fffffc00003f5360 for (i = 0; i < LOCK_CHILDCOUNT; i++) fffffc00003f5378: 09 04 ff 47 clr s0 fffffc00003f537c: 58 13 7d a5 ldq s2,4952(gp) fffffc00003f5380: 01 08 5f 21 lda s1,2049(zero) fffffc00003f5384: 00 00 e0 2f unop fffffc00003f5388: 1f 04 ff 47 nop fffffc00003f538c: 00 00 e0 2f unop witness_lock_list_free(&w_locklistdata[i]); fffffc00003f5390: 30 d7 20 49 sll s0,0x6,a0 fffffc00003f5394: 10 04 0b 42 addq a0,s2,a0 fffffc00003f5398: bb 0b 40 d3 bsr ra,fffffc00003f8288 fffffc00003f539c: 09 30 20 41 addl s0,0x1,s0 fffffc00003f53a0: a1 0d 2a 41 cmple s0,s1,t0 fffffc00003f53a4: fa ff 3f f4 bne t0,fffffc00003f5390 /* First add in all the specified order lists. */ for (order = order_lists; order->w_name != NULL; order++) { fffffc00003f53a8: 40 13 5d a5 ldq s1,4928(gp) fffffc00003f53ac: 00 00 2a a4 ldq t0,0(s1) fffffc00003f53b0: 1e 00 20 e4 beq t0,fffffc00003f542c fffffc00003f53b4: 60 15 bd a5 ldq s4,5472(gp) fffffc00003f53b8: 1f 04 ff 47 nop fffffc00003f53bc: 00 00 e0 2f unop w = enroll(order->w_name, order->w_class); fffffc00003f53c0: 00 00 0a a6 ldq a0,0(s1) fffffc00003f53c4: 08 00 2a a6 ldq a1,8(s1) fffffc00003f53c8: df 06 40 d3 bsr ra,fffffc00003f6f48 fffffc00003f53cc: 0b 04 e0 47 mov v0,s2 w->w_file = "order list"; fffffc00003f53d0: 28 00 ab b5 stq s4,40(s2) for (order++; order->w_name != NULL; order++) { fffffc00003f53d4: 0a 14 42 41 addq s1,0x10,s1 fffffc00003f53d8: 00 00 2a a4 ldq t0,0(s1) fffffc00003f53dc: 10 00 20 e4 beq t0,fffffc00003f5420 fffffc00003f53e0: 60 15 9d a5 ldq s3,5472(gp) fffffc00003f53e4: 00 00 e0 2f unop fffffc00003f53e8: 1f 04 ff 47 nop fffffc00003f53ec: 00 00 e0 2f unop -- B.Walter COSMO-Project http://www.cosmo-project.de ticso@cicely.de Usergroup info@cosmo-project.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Mar 29 13:11: 5 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 44C9137B71D for ; Thu, 29 Mar 2001 13:11:02 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id QAA07774; Thu, 29 Mar 2001 16:11:01 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.3/8.9.1) id f2TLAV382008; Thu, 29 Mar 2001 16:10:31 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15043.42183.306906.990732@grasshopper.cs.duke.edu> Date: Thu, 29 Mar 2001 16:10:31 -0500 (EST) To: Bernd Walter Cc: freebsd-alpha@freebsd.org Subject: Re: -current boot panic In-Reply-To: <20010329230022.B29139@cicely20.cicely.de> References: <20010329221942.A29139@cicely20.cicely.de> <15043.39496.927622.874793@grasshopper.cs.duke.edu> <20010329230022.B29139@cicely20.cicely.de> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Bernd Walter writes: > > How about running gdb on the kernel (with symbols) and mapping > > 0xfffffc00003f53d0 to a function & line number? > > Mmm - yes - sounds logical. > I don't know how to do with gdb here is the relevant objdump -S output: gdb kernel.debug GNU gdb 4.18 Copyright 1998 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "alpha-unknown-freebsd"... (gdb) l *0xfffffc00003f53d0 > /* > * The WITNESS-enabled diagnostic code. > */ > static void > witness_initialize(void *dummy __unused) > { > struct lock_object *lock; > struct witness_order_list_entry *order; > struct witness *w, *w1; > int i; Sounds like a problem with the witness code. I'd suggest grabbing today's -current before going any further (you might have grabbed your sources when jhb was in the middle of changing all the mutex/witness code around). If that doesn't help, try disabling the WITNESS option & seeing if that helps. Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Mar 29 13:21:52 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from srv1.cosmo-project.de (srv1.cosmo-project.de [213.83.6.106]) by hub.freebsd.org (Postfix) with ESMTP id 0B4A737B724 for ; Thu, 29 Mar 2001 13:21:50 -0800 (PST) (envelope-from ticso@mail.cicely.de) Received: from mail.cicely.de (cicely20 [10.1.1.22]) by srv1.cosmo-project.de (8.11.0/8.11.0) with ESMTP id f2TLLmK02058; Thu, 29 Mar 2001 23:21:48 +0200 (CEST) Received: (from ticso@localhost) by mail.cicely.de (8.11.0/8.11.0) id f2TLM4i00175; Thu, 29 Mar 2001 23:22:04 +0200 (CEST) Date: Thu, 29 Mar 2001 23:22:03 +0200 From: Bernd Walter To: Andrew Gallatin Cc: Bernd Walter , freebsd-alpha@FreeBSD.ORG Subject: Re: -current boot panic Message-ID: <20010329232203.C29139@cicely20.cicely.de> References: <20010329221942.A29139@cicely20.cicely.de> <15043.39496.927622.874793@grasshopper.cs.duke.edu> <20010329230022.B29139@cicely20.cicely.de> <15043.42183.306906.990732@grasshopper.cs.duke.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <15043.42183.306906.990732@grasshopper.cs.duke.edu>; from gallatin@cs.duke.edu on Thu, Mar 29, 2001 at 04:10:31PM -0500 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, Mar 29, 2001 at 04:10:31PM -0500, Andrew Gallatin wrote: > Sounds like a problem with the witness code. I'd suggest grabbing > today's -current before going any further (you might have grabbed your > sources when jhb was in the middle of changing all the mutex/witness > code around). If that doesn't help, try disabling the WITNESS option > & seeing if that helps. My source contains jhb's latest change from yesterday. All that is missing is yours to autoconf.c, but this doesn't bite me. I'm now compiling without WITNESS. -- B.Walter COSMO-Project http://www.cosmo-project.de ticso@cicely.de Usergroup info@cosmo-project.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Mar 29 20: 0:49 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from kelly.sercomtel.com.br (kelly.sercomtel.com.br [200.250.19.8]) by hub.freebsd.org (Postfix) with ESMTP id 543E237B719 for ; Thu, 29 Mar 2001 20:00:42 -0800 (PST) (envelope-from lhguimaraes@ineparnet.com.br) Received: from verde.onda.com.br (pophost.onda.com.br [200.250.19.90]) by kelly.sercomtel.com.br (8.9.3+Sun/8.9.3) with ESMTP id BAA25324 for ; Fri, 30 Mar 2001 01:00:25 -0300 (EST) Received: from impact (ascta012p240.onda.com.br [200.195.211.240]) by verde.onda.com.br (8.8.8/8.8.8) with SMTP id BAA08763 for ; Fri, 30 Mar 2001 01:00:31 -0300 (EST) Message-ID: <003501c0b8ce$0c206fc0$f0d3c3c8@impact> From: "Luiz Henrique" To: Date: Fri, 30 Mar 2001 00:57:27 -0300 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit 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 subscribe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Mar 29 20:11:26 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 A87D537B71B for ; Thu, 29 Mar 2001 20:11:22 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id XAA13972 for ; Thu, 29 Mar 2001 23:11:22 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.3/8.9.1) id f2U4Aq682577; Thu, 29 Mar 2001 23:10:52 -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: <15044.1867.943183.224703@grasshopper.cs.duke.edu> Date: Thu, 29 Mar 2001 23:10:51 -0500 (EST) To: freebsd-alpha@freebsd.org Subject: do we care about performance yet? 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 FWIW, I ran a make buildworld this evening on my UP1000 under iprobe, as well as with the receive side of a netperf tcp stream. (for anybody who doesn't know what iprobe is, check out http://www.cs.duke.edu/ari/iprobe) For the buildworld, the system spent about 40% of its time in kernel. Roughly 50% of that was in various states of idleness. I've left full reports at: http://www.cs.duke.edu/~gallatin/iprobe_current/ The "???NOT_FOUND" is userland code I didn't tell iprobe about. The top few functions were: Sample Image Total Name Count Pct Pct ---- ----- --- --- /boot/kernel/kernel 1411352 39.3 runq_check 283261 20.1 7.9 procrunnable 268553 19.0 7.5 idle_proc 161822 11.5 4.5 bzero 92338 6.5 2.6 bcopy_samealign_lp 71123 5.0 2.0 lockmgr 58602 4.2 1.6 vm_fault 21086 1.5 0.6 trap 20039 1.4 0.6 syscall 17980 1.3 0.5 userret 15674 1.1 0.4 zalloc 11792 0.8 0.3 ast 11128 0.8 0.3 interrupt 10629 0.8 0.3 CURSIG 9933 0.7 0.3 cache_lookup 8934 0.6 0.2 gbincore 7589 0.5 0.2 ufs_vnoperate 7569 0.5 0.2 ithread_loop 7561 0.5 0.2 atomic_set_16 7291 0.5 0.2 pmap_prefault 7159 0.5 0.2 pmap_enter 6913 0.5 0.2 atomic_clear_16 6802 0.5 0.2 vget 6383 0.5 0.2 lookup 6183 0.4 0.2 hardclock 6129 0.4 0.2 zfree 6059 0.4 0.2 vm_page_alloc 5914 0.4 0.2 pmap_remove_pages 5583 0.4 0.2 Lcopystr1 5151 0.4 0.1 vm_page_lookup 5087 0.4 0.1 pmap_enter_quick 4717 0.3 0.1 vrele 4680 0.3 0.1 vfs_cache_lookup 4556 0.3 0.1 pmap_invalidate_page 4359 0.3 0.1 XentInt 4264 0.3 0.1 XentMM 4037 0.3 0.1 vm_map_lookup 3696 0.3 0.1 vn_lock 3625 0.3 0.1 pmap_emulate_reference 3344 0.2 0.1 Cheers, Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Mar 29 22:17:54 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 BA52B37B719 for ; Thu, 29 Mar 2001 22:17:52 -0800 (PST) (envelope-from mjacob@feral.com) Received: from beppo (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id WAA16452; Thu, 29 Mar 2001 22:17:50 -0800 Date: Thu, 29 Mar 2001 22:17:44 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Andrew Gallatin Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: do we care about performance yet? In-Reply-To: <15044.1867.943183.224703@grasshopper.cs.duke.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Isn't this just basically saying you're i/o bound? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Mar 29 23:58:33 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from srv1.cosmo-project.de (srv1.cosmo-project.de [213.83.6.106]) by hub.freebsd.org (Postfix) with ESMTP id 2296937B719 for ; Thu, 29 Mar 2001 23:58:30 -0800 (PST) (envelope-from ticso@mail.cicely.de) Received: from mail.cicely.de (cicely20 [10.1.1.22]) by srv1.cosmo-project.de (8.11.0/8.11.0) with ESMTP id f2U7wRK05127; Fri, 30 Mar 2001 09:58:28 +0200 (CEST) Received: (from ticso@localhost) by mail.cicely.de (8.11.0/8.11.0) id f2U7wiY01812; Fri, 30 Mar 2001 09:58:44 +0200 (CEST) Date: Fri, 30 Mar 2001 09:58:43 +0200 From: Bernd Walter To: Andrew Gallatin Cc: Bernd Walter , freebsd-alpha@FreeBSD.ORG Subject: Re: -current boot panic Message-ID: <20010330095843.A1808@cicely20.cicely.de> References: <20010329221942.A29139@cicely20.cicely.de> <15043.39496.927622.874793@grasshopper.cs.duke.edu> <20010329230022.B29139@cicely20.cicely.de> <15043.42183.306906.990732@grasshopper.cs.duke.edu> <20010329232203.C29139@cicely20.cicely.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010329232203.C29139@cicely20.cicely.de>; from ticso on Thu, Mar 29, 2001 at 11:22:03PM +0200 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, Mar 29, 2001 at 11:22:03PM +0200, Bernd Walter wrote: > On Thu, Mar 29, 2001 at 04:10:31PM -0500, Andrew Gallatin wrote: > > Sounds like a problem with the witness code. I'd suggest grabbing > > today's -current before going any further (you might have grabbed your > > sources when jhb was in the middle of changing all the mutex/witness > > code around). If that doesn't help, try disabling the WITNESS option > > & seeing if that helps. > > My source contains jhb's latest change from yesterday. > All that is missing is yours to autoconf.c, but this doesn't bite me. > I'm now compiling without WITNESS. OK it's booting fine without WITNESS -- B.Walter COSMO-Project http://www.cosmo-project.de ticso@cicely.de Usergroup info@cosmo-project.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Mar 30 2:33:33 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from finch-post-10.mail.demon.net (finch-post-10.mail.demon.net [194.217.242.38]) by hub.freebsd.org (Postfix) with ESMTP id AA84C37B71B; Fri, 30 Mar 2001 02:33:30 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from [62.49.251.130] (helo=herring.nlsystems.com) by finch-post-10.mail.demon.net with esmtp (Exim 2.12 #1) id 14iwDh-000LRB-0A; Fri, 30 Mar 2001 10:33:29 +0000 Received: from herring (herring [10.0.0.2]) by herring.nlsystems.com (8.11.2/8.11.2) with ESMTP id f2UAWD456646; Fri, 30 Mar 2001 11:32:14 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Fri, 30 Mar 2001 11:32:13 +0100 (BST) From: Doug Rabson To: Andrew Gallatin Cc: , Subject: Re: bounds_check_with_label() on alpha In-Reply-To: <15043.38865.445922.245686@grasshopper.cs.duke.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, 29 Mar 2001, Andrew Gallatin wrote: > > David O'Brien writes: > > On Thu, Mar 29, 2001 at 02:59:02PM -0500, Andrew Gallatin wrote: > > > Do'h. Ok, I see the problem. bounds_check_with_label() is basically > > > > *Sigh*. Of course there is no rev 1.1 or 1.2 (and their log message > > wasn't saved when those revs were diked out) to help explain _why_. > > I think it was commented out in the original merged netbsd/alpha > freebsd/i386 machdep.c. It was probably commented out because alpha > didn't have enough infastructure to allow it to compile & Doug wanted > to just keep moving until he got something booting on SimOs & then it > was forgotten. I don't blame him. Doug? It was probably something like that. I don't actually remember but I can believe that I just diked it out while I was trying to get the thing to mount its root filesystem. > > > Crap like this is really irritating on the Alpha... > > Yes. But as more people use it, it happens less & less often. Hopefully. -- Doug Rabson Mail: dfr@nlsystems.com Phone: +44 20 8348 6160 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Mar 30 2:35:25 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from anchor-post-34.mail.demon.net (anchor-post-34.mail.demon.net [194.217.242.92]) by hub.freebsd.org (Postfix) with ESMTP id DE9A537B726 for ; Fri, 30 Mar 2001 02:35:21 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from [62.49.251.130] (helo=herring.nlsystems.com) by anchor-post-34.mail.demon.net with esmtp (Exim 2.12 #1) id 14iwFU-0004Nq-0Y; Fri, 30 Mar 2001 11:35:20 +0100 Received: from herring (herring [10.0.0.2]) by herring.nlsystems.com (8.11.2/8.11.2) with ESMTP id f2UAY5456654; Fri, 30 Mar 2001 11:34:05 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Fri, 30 Mar 2001 11:34:05 +0100 (BST) From: Doug Rabson To: Andrew Gallatin Cc: Subject: Re: do we care about performance yet? In-Reply-To: <15044.1867.943183.224703@grasshopper.cs.duke.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, 29 Mar 2001, Andrew Gallatin wrote: > > FWIW, I ran a make buildworld this evening on my UP1000 under iprobe, > as well as with the receive side of a netperf tcp stream. > > (for anybody who doesn't know what iprobe is, check out > http://www.cs.duke.edu/ari/iprobe) > > For the buildworld, the system spent about 40% of its time in kernel. > Roughly 50% of that was in various states of idleness. I've left full > reports at: > > http://www.cs.duke.edu/~gallatin/iprobe_current/ > > The "???NOT_FOUND" is userland code I didn't tell iprobe about. I think this is just showing a lot of contention for the Giant mutex (and probably some i/o waiting). Since we don't halt on idle, the cpu will spend a lot of time buzzlooping on runq_check. -- Doug Rabson Mail: dfr@nlsystems.com Phone: +44 20 8348 6160 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Mar 30 6:48:11 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 9451237B726 for ; Fri, 30 Mar 2001 06:48:01 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id JAA22723; Fri, 30 Mar 2001 09:48:00 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.3/8.9.1) id f2UElUS83683; Fri, 30 Mar 2001 09:47:30 -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: <15044.40066.746054.729549@grasshopper.cs.duke.edu> Date: Fri, 30 Mar 2001 09:47:30 -0500 (EST) To: mjacob@feral.com Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: do we care about performance yet? In-Reply-To: References: <15044.1867.943183.224703@grasshopper.cs.duke.edu> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Matthew Jacob writes: > > Isn't this just basically saying you're i/o bound? Sorta. And user-space CPU bound as well. The lockmgr was a somewhat surprising standout (1.5% of the time doing a buildworld is spent in lockmgr). I'm thinking it would be interesting for people to occasionally profile the kernel after major infastructure changes & want to showcase what Iprobe can do (at less than 5% overhead, probably more like 1%). I profiled a buildworld because that's the "benchmark" people seem to care about. The netperf TCP streams are much more interesting. In the non witness case (http://www.cs.duke.edu/~gallatin/iprobe_current/netperf.120sec), ithread_loop() is at nearly 7% for a 100Mb TCP stream. Nearly all of that is assigned to the mtx_unlock_spin(&sched_lock) line at the bottom of the code. I haven't disassembled it, but I suspect that its just an effect of cache misses as we reschedule into the ithread loop. In the witness case, (http://www.cs.duke.edu/~gallatin/iprobe_current/netperf.witness.120sec) we see how expensive the witness functionality really is... Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Mar 30 6:53: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 C9AAC37B72E for ; Fri, 30 Mar 2001 06:53:20 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id JAA22803; Fri, 30 Mar 2001 09:53:20 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.3/8.9.1) id f2UEqoh83701; Fri, 30 Mar 2001 09:52:50 -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: <15044.40385.937863.333900@grasshopper.cs.duke.edu> Date: Fri, 30 Mar 2001 09:52:49 -0500 (EST) To: Doug Rabson Cc: Subject: Re: do we care about performance yet? In-Reply-To: References: <15044.1867.943183.224703@grasshopper.cs.duke.edu> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Doug Rabson writes: > On Thu, 29 Mar 2001, Andrew Gallatin wrote: > > > > > FWIW, I ran a make buildworld this evening on my UP1000 under iprobe, > > as well as with the receive side of a netperf tcp stream. > > > > (for anybody who doesn't know what iprobe is, check out > > http://www.cs.duke.edu/ari/iprobe) > > > > For the buildworld, the system spent about 40% of its time in kernel. > > Roughly 50% of that was in various states of idleness. I've left full > > reports at: > > > > http://www.cs.duke.edu/~gallatin/iprobe_current/ > > > > The "???NOT_FOUND" is userland code I didn't tell iprobe about. > > I think this is just showing a lot of contention for the Giant mutex (and > probably some i/o waiting). Since we don't halt on idle, the cpu will > spend a lot of time buzzlooping on runq_check. > Yes, certainly. And using lots of power too ;-( Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Mar 30 8:34:46 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 0A7C537B718 for ; Fri, 30 Mar 2001 08:34:45 -0800 (PST) (envelope-from mjacob@feral.com) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id IAA18135; Fri, 30 Mar 2001 08:34:48 -0800 Date: Fri, 30 Mar 2001 08:34:42 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Andrew Gallatin Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: do we care about performance yet? In-Reply-To: <15044.40066.746054.729549@grasshopper.cs.duke.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org BTW- how do you build the iprobe stuff? I'd like to start using it... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Mar 30 8:35:34 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 0B59937B71A for ; Fri, 30 Mar 2001 08:35:31 -0800 (PST) (envelope-from mjacob@feral.com) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id IAA18145; Fri, 30 Mar 2001 08:35:24 -0800 Date: Fri, 30 Mar 2001 08:35:18 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Doug Rabson Cc: Andrew Gallatin , freebsd-alpha@FreeBSD.ORG Subject: Re: do we care about performance yet? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, 30 Mar 2001, Doug Rabson wrote: > On Thu, 29 Mar 2001, Andrew Gallatin wrote: > > > > > FWIW, I ran a make buildworld this evening on my UP1000 under iprobe, > > as well as with the receive side of a netperf tcp stream. > > > > (for anybody who doesn't know what iprobe is, check out > > http://www.cs.duke.edu/ari/iprobe) > > > > For the buildworld, the system spent about 40% of its time in kernel. > > Roughly 50% of that was in various states of idleness. I've left full > > reports at: > > > > http://www.cs.duke.edu/~gallatin/iprobe_current/ > > > > The "???NOT_FOUND" is userland code I didn't tell iprobe about. > > I think this is just showing a lot of contention for the Giant mutex (and > probably some i/o waiting). Since we don't halt on idle, the cpu will > spend a lot of time buzzlooping on runq_check. That's what I mean about I/O bound- I looked at runq_check and yes, that's really 'idle'. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Mar 30 8:38: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 98F9537B719 for ; Fri, 30 Mar 2001 08:38:23 -0800 (PST) (envelope-from mjacob@feral.com) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id IAA18154; Fri, 30 Mar 2001 08:38:07 -0800 Date: Fri, 30 Mar 2001 08:38:01 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Andrew Gallatin Cc: Doug Rabson , freebsd-alpha@FreeBSD.ORG Subject: Re: do we care about performance yet? In-Reply-To: <15044.40385.937863.333900@grasshopper.cs.duke.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > Yes, certainly. And using lots of power too ;-( How about adding alpha_pal_wtint? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Mar 30 8:40:14 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 1FE0337B71A for ; Fri, 30 Mar 2001 08:40:12 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id LAA25001; Fri, 30 Mar 2001 11:40:09 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.3/8.9.1) id f2UGdcc84144; Fri, 30 Mar 2001 11:39:38 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15044.46794.874044.815327@grasshopper.cs.duke.edu> Date: Fri, 30 Mar 2001 11:39:38 -0500 (EST) To: mjacob@feral.com Cc: Doug Rabson , freebsd-alpha@FreeBSD.ORG Subject: Re: do we care about performance yet? In-Reply-To: References: <15044.40385.937863.333900@grasshopper.cs.duke.edu> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Matthew Jacob writes: > > > > > Yes, certainly. And using lots of power too ;-( > > How about adding alpha_pal_wtint? Does that actually work these days? When we first got miatas and were running tru64, I remember them going to sleep and never waking up. Maybe it was due to palcode bugs? Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Mar 30 8:48:31 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from imul.math.uni.lodz.pl (imul.math.uni.lodz.pl [212.191.65.2]) by hub.freebsd.org (Postfix) with ESMTP id 1FB1637B719; Fri, 30 Mar 2001 08:48:29 -0800 (PST) (envelope-from dagoon@math.uni.lodz.pl) Received: by imul.math.uni.lodz.pl (Mail Transport Agent, from userid 1168) id 940891F42; Fri, 30 Mar 2001 18:47:54 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by imul.math.uni.lodz.pl (Mail Transport Agent) with ESMTP id 84D3E1742E; Fri, 30 Mar 2001 18:47:54 +0200 (CEST) Date: Fri, 30 Mar 2001 18:47:54 +0200 (CEST) From: Marcin Gryszkalis To: David O'Brien Cc: alpha@freebsd.org Subject: Re: gperf segfail on 4.3b In-Reply-To: <20010328144732.A88252@dragon.nuxi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I don't know if that have anything in common, but something looking similar happened to debian/sparc : www.geocrawler.com/archives/3/237/1997/9/0/1222257/ m. -- .d$$$$b, $d$$$$b. .d$$$$b, Marcin Gryszkalis $$' `"" $$' `"' $$' `$$ $$. .ss $$ $$ $$ (...) QED. (QED translates from the Latin `"8$$8"' 88 88 88 as "So what?") To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Mar 30 9: 6:52 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 5F8AC37B719 for ; Fri, 30 Mar 2001 09:06:49 -0800 (PST) (envelope-from mjacob@feral.com) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id JAA18308; Fri, 30 Mar 2001 09:06:51 -0800 Date: Fri, 30 Mar 2001 09:06:45 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Andrew Gallatin Cc: Doug Rabson , freebsd-alpha@FreeBSD.ORG Subject: Re: do we care about performance yet? In-Reply-To: <15044.46794.874044.815327@grasshopper.cs.duke.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, 30 Mar 2001, Andrew Gallatin wrote: > > Matthew Jacob writes: > > > > > > > > Yes, certainly. And using lots of power too ;-( > > > > How about adding alpha_pal_wtint? > > Does that actually work these days? When we first got miatas and were > running tru64, I remember them going to sleep and never waking up. > Maybe it was due to palcode bugs? Uhh... maybe not a good idea then... :-).. Reminds me of 68020 'stop' instruction...... Because I would not stop for death, Death stopped for me..... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Mar 30 10: 6: 2 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 7ECEC37B71B for ; Fri, 30 Mar 2001 10:05:57 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id NAA26860; Fri, 30 Mar 2001 13:05:56 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.3/8.9.1) id f2UI5Q584301; Fri, 30 Mar 2001 13:05:26 -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: <15044.51942.139936.871471@grasshopper.cs.duke.edu> Date: Fri, 30 Mar 2001 13:05:26 -0500 (EST) To: mjacob@feral.com Cc: freebsd-alpha@freebsd.org Subject: Re: do we care about performance yet? In-Reply-To: References: <15044.40066.746054.729549@grasshopper.cs.duke.edu> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Matthew Jacob writes: > > BTW- how do you build the iprobe stuff? I'd like to start using it... Err. Uhh.. "Very Carefully" I just rolled a new tarball that should work with -current. Get it at ftp://ftp.cs.duke.edu/pub/gallatin/freebsd_iprobe/freebsd_iprobe_current.tar.gz There's going to be a "gotcha" when building rep -- it needs binutils. You need to stash libbfd.a and libiberty.a from a binutils build someplace (like /usr/obj) and point BINUTILSLIBS at it. Edit iprobe/makefile is search for " Ick!" This is why its not a port. Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Mar 30 10:14:57 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 C27B237B718 for ; Fri, 30 Mar 2001 10:14:55 -0800 (PST) (envelope-from mjacob@feral.com) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id KAA18667; Fri, 30 Mar 2001 10:14:59 -0800 Date: Fri, 30 Mar 2001 10:14:53 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Andrew Gallatin Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: do we care about performance yet? In-Reply-To: <15044.51942.139936.871471@grasshopper.cs.duke.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org thanks! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Mar 30 14:21:45 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from smtp05.primenet.com (smtp05.primenet.com [206.165.6.135]) by hub.freebsd.org (Postfix) with ESMTP id A034A37B719 for ; Fri, 30 Mar 2001 14:21:43 -0800 (PST) (envelope-from tlambert@usr09.primenet.com) Received: (from daemon@localhost) by smtp05.primenet.com (8.9.3/8.9.3) id PAA29203; Fri, 30 Mar 2001 15:15:53 -0700 (MST) Received: from usr09.primenet.com(206.165.6.209) via SMTP by smtp05.primenet.com, id smtpdAAASia4_4; Fri Mar 30 15:15:50 2001 Received: (from tlambert@localhost) by usr09.primenet.com (8.8.5/8.8.5) id PAA08297; Fri, 30 Mar 2001 15:21:38 -0700 (MST) From: Terry Lambert Message-Id: <200103302221.PAA08297@usr09.primenet.com> Subject: Re: do we care about performance yet? To: gallatin@cs.duke.edu (Andrew Gallatin) Date: Fri, 30 Mar 2001 22:21:37 +0000 (GMT) Cc: mjacob@feral.com, freebsd-alpha@FreeBSD.ORG In-Reply-To: <15044.40066.746054.729549@grasshopper.cs.duke.edu> from "Andrew Gallatin" at Mar 30, 2001 09:47:30 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 > Sorta. And user-space CPU bound as well. The lockmgr was a somewhat > surprising standout (1.5% of the time doing a buildworld is spent in > lockmgr). This is not surprising. Benchmarking is why I didn't want to use it as if it were generally useful. 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 Mar 30 15: 2: 1 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id 3B6B037B718 for ; Fri, 30 Mar 2001 15:01:53 -0800 (PST) (envelope-from jhb@FreeBSD.org) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.2/8.11.2) with ESMTP id f2UN1iG78504; Fri, 30 Mar 2001 15:01:44 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Fri, 30 Mar 2001 15:01:21 -0800 (PST) From: John Baldwin To: Matthew Jacob Subject: Re: do we care about performance yet? Cc: freebsd-alpha@FreeBSD.org, Doug Rabson , Andrew Gallatin Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 30-Mar-01 Matthew Jacob wrote: > >> >> Yes, certainly. And using lots of power too ;-( > > How about adding alpha_pal_wtint? I have thought about it. Not SMP safe yet. Doug's comment later seems to suggest that it should be something that defaults to off (maybe a sysctl and loader tunable?) -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Mar 30 15: 2:28 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id 129B337B719 for ; Fri, 30 Mar 2001 15:02:26 -0800 (PST) (envelope-from jhb@FreeBSD.org) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.2/8.11.2) with ESMTP id f2UN1iG78496; Fri, 30 Mar 2001 15:01:44 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <15044.1867.943183.224703@grasshopper.cs.duke.edu> Date: Fri, 30 Mar 2001 15:01:20 -0800 (PST) From: John Baldwin To: Andrew Gallatin Subject: RE: do we care about performance yet? Cc: freebsd-alpha@FreeBSD.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 30-Mar-01 Andrew Gallatin wrote: > > FWIW, I ran a make buildworld this evening on my UP1000 under iprobe, > as well as with the receive side of a netperf tcp stream. > > (for anybody who doesn't know what iprobe is, check out > http://www.cs.duke.edu/ari/iprobe) > > For the buildworld, the system spent about 40% of its time in kernel. > Roughly 50% of that was in various states of idleness. I've left full > reports at: > > http://www.cs.duke.edu/~gallatin/iprobe_current/ > > The "???NOT_FOUND" is userland code I didn't tell iprobe about. > > The top few functions were: > Sample Image Total > Name Count Pct Pct > ---- ----- --- --- > /boot/kernel/kernel 1411352 39.3 > runq_check 283261 20.1 7.9 > procrunnable 268553 19.0 7.5 > idle_proc 161822 11.5 4.5 These 3 are only used when we are sitting idle in the idle proces because there are no runnable proceses. We can't really optimize these away. :-/ -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Mar 30 15: 2:34 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id C592437B71B for ; Fri, 30 Mar 2001 15:02:30 -0800 (PST) (envelope-from jhb@FreeBSD.org) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.2/8.11.2) with ESMTP id f2UN1iG78500; Fri, 30 Mar 2001 15:01:44 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <15044.40066.746054.729549@grasshopper.cs.duke.edu> Date: Fri, 30 Mar 2001 15:01:21 -0800 (PST) From: John Baldwin To: Andrew Gallatin Subject: Re: do we care about performance yet? Cc: freebsd-alpha@FreeBSD.org, mjacob@feral.com Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 30-Mar-01 Andrew Gallatin wrote: > > Matthew Jacob writes: > > > > Isn't this just basically saying you're i/o bound? > > Sorta. And user-space CPU bound as well. The lockmgr was a somewhat > surprising standout (1.5% of the time doing a buildworld is spent in > lockmgr). Remember that VFS uses lockmgr all over the place, as does the buffer cache, so anything I/O bound is going to be using lockmgr() a lot. > I'm thinking it would be interesting for people to occasionally > profile the kernel after major infastructure changes & want to > showcase what Iprobe can do (at less than 5% overhead, probably more > like 1%). I profiled a buildworld because that's the "benchmark" > people seem to care about. > > The netperf TCP streams are much more interesting. In the non witness > case (http://www.cs.duke.edu/~gallatin/iprobe_current/netperf.120sec), > ithread_loop() is at nearly 7% for a 100Mb TCP stream. Nearly all of > that is assigned to the mtx_unlock_spin(&sched_lock) line at the > bottom of the code. I haven't disassembled it, but I suspect that its > just an effect of cache misses as we reschedule into the ithread loop. That is quite possible, as the mutex exit is the first thing we do after returning from mi_switch, and mi_switch() doesn't do much after returning from cpu_switch(), not to mention that mi_switch() might still be cached by a read-ahead style cache since we were just in it when we switched out. > In the witness case, > (http://www.cs.duke.edu/~gallatin/iprobe_current/netperf.witness.120sec) > we see how expensive the witness functionality really is... Yes, it is not cheap. The recent changes to it also made it more expensive in the spinlock case. The witness_lock_list_{get,free} functions manage the static pool of struct lock_list_entry's that are used to build the per-cpu list of spinlocks and per-process list of sleeplocks, hence they are rather high on the list. > Drew -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Mar 30 18: 2:13 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from mail.hiwaay.net (fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (Postfix) with ESMTP id 9715D37B71E; Fri, 30 Mar 2001 18:02:08 -0800 (PST) (envelope-from steve@havk.org) Received: from bsd.havk.org (user-24-214-88-8.knology.net [24.214.88.8]) by mail.hiwaay.net (8.11.3/8.11.3) with ESMTP id f2V226524764; Fri, 30 Mar 2001 20:02:07 -0600 (CST) Received: by bsd.havk.org (Postfix, from userid 1001) id F2E071A7C7; Fri, 30 Mar 2001 20:02:04 -0600 (CST) Date: Fri, 30 Mar 2001 20:02:04 -0600 From: Steve Price To: ports@freebsd.org Subject: update on Alpha package building cluster Message-ID: <20010330200204.A73299@bsd.havk.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i X-Operating-System: FreeBSD 4.2-STABLE i386 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi all, I think I've finally got the Alpha build cluster going. It will be running 4-stable builds for awhile (at least until the 4.3 release is out the door). The error logs can be found here. http://beta.freebsd.org/ Specifically you'll want to take a look here because the rest of the links are somewhat broken because the first build is happening now. http://beta.freebsd.org/errorlogs/4-latest/ Many thanks to Asami-san, Mr. O'Brien, and everyone else that made all of this possible. Everyone with an Alpha machine dig in and fix some ports so we'll have an awesome 4.3 release for the Alpha as well as ia32. Enjoy! -steve PS: Having 3 machines working on the builds is pretty darned awesome compared to the 1 machine that I had been doing the builds on. In the last couple of hours these machines have been able to build ~400 packages! Imagine what it could do if I were to get access to the other 3 or 4 machines. :) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sat Mar 31 8:53:33 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 53AC237B719; Sat, 31 Mar 2001 08:53:30 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id LAA12972; Sat, 31 Mar 2001 11:53:29 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.3/8.9.1) id f2VGqxl89123; Sat, 31 Mar 2001 11:52:59 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15046.2923.571297.353243@grasshopper.cs.duke.edu> Date: Sat, 31 Mar 2001 11:52:59 -0500 (EST) To: John Baldwin Cc: freebsd-alpha@FreeBSD.org Subject: RE: do we care about performance yet? In-Reply-To: References: <15044.1867.943183.224703@grasshopper.cs.duke.edu> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org John Baldwin writes: > > For the buildworld, the system spent about 40% of its time in kernel. > > Roughly 50% of that was in various states of idleness. I've left full > > reports at: <..> > > Name Count Pct Pct > > ---- ----- --- --- > > /boot/kernel/kernel 1411352 39.3 > > runq_check 283261 20.1 7.9 > > procrunnable 268553 19.0 7.5 > > idle_proc 161822 11.5 4.5 > > These 3 are only used when we are sitting idle in the idle proces because there > are no runnable proceses. We can't really optimize these away. :-/ Yes, I realize this. This is the "Roughly 50% of that was in various states of idleness" I mentioned above. Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sat Mar 31 11:43:23 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 1356637B718 for ; Sat, 31 Mar 2001 11:43:22 -0800 (PST) (envelope-from wkb@freebie.demon.nl) Received: from [212.238.54.101] (helo=freebie.demon.nl) by post.mail.nl.demon.net with smtp (Exim 3.22 #1) id 14jRHM-00057u-00 for freebsd-alpha@freebsd.org; Sat, 31 Mar 2001 19:43:20 +0000 Received: (from wkb@localhost) by freebie.demon.nl (8.11.3/8.11.2) id f2VJkB317558 for freebsd-alpha@freebsd.org; Sat, 31 Mar 2001 21:46:11 +0200 (CEST) (envelope-from wkb) Date: Sat, 31 Mar 2001 21:46:11 +0200 From: Wilko Bulte To: freebsd-alpha@freebsd.org Subject: Out of town.. Message-ID: <20010331214611.A17484@freebie.demon.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i X-OS: FreeBSD 4.3-RC X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I'll be out of town, and mostly out of email, due to a business trip to Asia the coming 2 weeks. Please don't let this stop you testing the 4.3RC on the Alpha machines ;-) cheers, -- | / 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 Sat Mar 31 12:30:58 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from lysimachus.hosting.swbell.net (lysimachus.hosting.swbell.net [216.100.98.6]) by hub.freebsd.org (Postfix) with ESMTP id 1360937B71B for ; Sat, 31 Mar 2001 12:30:57 -0800 (PST) (envelope-from alc@imimic.com) Received: from imimic.com (adsl-216-63-78-19.dsl.hstntx.swbell.net [216.63.78.19]) by lysimachus.hosting.swbell.net id PAA18557; Sat, 31 Mar 2001 15:30:36 -0500 (EST) [ConcentricHost SMTP Relay 1.7] Message-ID: <3AC63E6B.3D30B2B6@imimic.com> Date: Sat, 31 Mar 2001 14:30:36 -0600 From: "Alan L. Cox" Organization: iMimic Networking, Inc. X-Mailer: Mozilla 4.75 [en] (X11; U; FreeBSD 4.2-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: Andrew Gallatin Cc: freebsd-alpha@freebsd.org Subject: Re: do we care about performance yet? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > bzero 92338 6.5 2.6 > bcopy_samealign_lp 71123 5.0 2.0 I built a kernel last year using Compaq's implementation of these routines. A lot can be gained by using 21264-optimized implementations. (Unfortunately, the code I was given by Compaq was under NDA.) Alpha Processor (now API Networks) has, however, released optimized implementations for Linux. There are patches on their web site. Having talked to one hybrid business/technical person there, I doubt that they would balk at dual-licensing these patches under a BSD and GPL license. Alan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sat Mar 31 18:28:17 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 55DBF37B71A; Sat, 31 Mar 2001 18:28:12 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.3/8.11.1) id f312SCX76520; Sat, 31 Mar 2001 18:28:12 -0800 (PST) (envelope-from obrien) Date: Sat, 31 Mar 2001 18:28:11 -0800 From: "David O'Brien" To: stable@freebsd.org, alpha@freebsd.org Subject: Re: 4.3 Release candidate #2 now ready Message-ID: <20010331182811.A76490@dragon.nuxi.com> Reply-To: obrien@freebsd.org References: <20010330093118B.jkh@osd.bsdi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010330093118B.jkh@osd.bsdi.com>; from jkh@osd.bsdi.com on Fri, Mar 30, 2001 at 09:31:18AM -0800 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, Mar 30, 2001 at 09:31:18AM -0800, Jordan Hubbard wrote: > Due to the recent security fixes which went into the tree, along with > the fact that I'll be following a very large moving truck on Monday > and will be somewhat busy, I'm releasing the second release candidate > image today instead of monday. Please find the relevent Alpha/AXP bits at: ftp://ftp.freebsd.org/pub/FreeBSD/releases/alpha/ISO-IMAGES/4.3rc2-install.iso ftp://ftp.freebsd.org/pub/FreeBSD/releases/alpha/4.3-RC2/ If you have an Alpha and the bandwidth, testing the ISO would be a *big* help. For this ISO I built a new XFree86 3.3.6 containing the latest patches and security fixes. Enjoy! -- -- David (obrien@FreeBSD.org) Alpha Powered To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message